Randomly getting stuck after waking up from Deep Sleep (IDFGH-3846)

Development Kit:      [none] It is a custom board designed with the ESP32 WROOM 32 Module
Module or chip used:  [ESP32-WROOM-32]
IDF version (run git describe --tags to find it): v3.3.2-14-g6c9c253ed
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it): 1.22.0-80-g6c4433a5
Operating System:     [Windows]
(Windows only) environment type: [ESP Command Prompt].
Using an IDE?: [Yes (Visual Studio Code]
Power Supply:         [external 3.3V]

Problem Description
Sorry for the long explanation.
We were using Arduino and our code involves interfacing with the two sensors, BME680 and TCS. We wake up every 5 minutes from deep sleep take readings, send them via esp now and go back to deep sleep. Issue was that after a random amount of wakeups the esp32 would just get stuck after waking up and not produce any error and be halted. Here is the Arduino issue, still not been resolved. https://github.com/espressif/arduino-esp32/issues/796
Seeing as how we never had this issue with ESP-IDF we decided to switch to ESP-IDf. Now it feels like the issue persists. It would get stuck and not wake up. The worst of it is that when we turn on verbose logging to get further information we have further complications. We had to change the partition offset from 0x8000 to 0x10000. When we did so, a line in our code esp_light_sleep_start() started giving us abort issues in regards to the lock.c file. Trying to do verbose with 0x8000 offset, causes issues. So we are unable to see the logs for when it gets stuck in deep sleep reset.
Expected Behavior
It should not get stuck after deep sleep reset.
Actual Behavior
After a random number of cycles it gets stuck in deep sleep reset.
Code to reproduce this issue
This is the main.c file
#include "nvs_flash.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"

extern void sensorBeginRun();

void sensorBegin(void *pvParameter)
{
    sensorBeginRun();
    vTaskDelete( NULL );
}

void app_main()
{
    esp_err_t err = nvs_flash_init();
    if (err == ESP_ERR_NVS_NO_FREE_PAGES || err == ESP_ERR_NVS_NEW_VERSION_FOUND) {
        // NVS partition was truncated and needs to be erased
        // Retry nvs_flash_init
        ESP_ERROR_CHECK(nvs_flash_erase());
        err = nvs_flash_init();
    }
    ESP_ERROR_CHECK( err );

    xTaskCreatePinnedToCore(sensorBegin, "sensorBegin",  5*1024, NULL, 5, NULL, 0);
}

This is the sensor begin file
#include <time.h>
#include <string.h>
#include <esp_log.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "freertos/event_groups.h"
#include <fastmath.h>
#include <driver/i2c.h>
#include <bsec_integration.h>
#include <bsec_serialized_configurations_iaq.h>
#include "tcs.h"
#include "driver/rtc_io.h"
#include "esp_event_loop.h"
#include "nvs_flash.h"
#include "nvs.h"

const char* TAG = "Spacr";
static const char* sensor_binary = "sensor_blob";
uint16_t r, g, b, c, colorTemp, lux;
xTaskHandle xHandle = NULL;
int timeToSleep = 300*1000000;

void gotoSleep() {
    rtc_gpio_isolate(GPIO_NUM_0);
    rtc_gpio_isolate(GPIO_NUM_2);
    rtc_gpio_isolate(GPIO_NUM_5);
    rtc_gpio_isolate(GPIO_NUM_12);
    rtc_gpio_isolate(GPIO_NUM_15);
    esp_sleep_pd_config(ESP_PD_DOMAIN_RTC_PERIPH, ESP_PD_OPTION_OFF);
    rtc_gpio_isolate(GPIO_NUM_16);
    rtc_gpio_isolate(GPIO_NUM_13);
    ESP_LOGI(TAG, "Entering Deep Sleep...");
    esp_sleep_enable_timer_wakeup(timeToSleep);
    esp_deep_sleep_start();
}

int8_t bus_write(uint8_t dev_addr, uint8_t reg_addr, uint8_t *reg_data_ptr, uint16_t data_len)
{
    i2c_cmd_handle_t cmd = i2c_cmd_link_create();
    assert(data_len > 0 && reg_data_ptr != NULL); // Safeguarding the assumptions
    i2c_master_start(cmd);
    i2c_master_write_byte(cmd, (dev_addr << 1) | I2C_MASTER_WRITE, true);
    i2c_master_write_byte(cmd, reg_addr, true);
    i2c_master_write(cmd, reg_data_ptr, data_len, true);
    i2c_master_stop(cmd);
    esp_err_t ret = i2c_master_cmd_begin(I2C_NUM_0, cmd, pdMS_TO_TICKS(1000));
    i2c_cmd_link_delete(cmd);
    // ESP_OK matches with the function success code (0)
    return (int8_t)ret;
}

int8_t bus_read(uint8_t dev_addr, uint8_t reg_addr, uint8_t *reg_data_ptr, uint16_t data_len)
{
    i2c_cmd_handle_t cmd = i2c_cmd_link_create();

    assert(data_len > 0 && reg_data_ptr != NULL); // Safeguarding the assumptions
    i2c_master_start(cmd);
    i2c_master_write_byte(cmd, (dev_addr << 1) | I2C_MASTER_WRITE, true);
    i2c_master_write_byte(cmd, reg_addr, true);
    i2c_master_start(cmd);
    i2c_master_write_byte(cmd, (dev_addr << 1) | I2C_MASTER_READ, true);
    if (data_len > 1) {
        i2c_master_read(cmd, reg_data_ptr, data_len - 1, I2C_MASTER_ACK);
    }
    i2c_master_read_byte(cmd, reg_data_ptr + data_len - 1, I2C_MASTER_NACK);
    i2c_master_stop(cmd);
    esp_err_t ret = i2c_master_cmd_begin(I2C_NUM_0, cmd, pdMS_TO_TICKS(1000));
    i2c_cmd_link_delete(cmd);
    return (int8_t)ret;
}

static void bme680_sleep(uint32_t t_ms)
{
    printf("Delay time %d\n", t_ms);
    if(t_ms > 1000 && count <3){
        printf("Count here\n");
        esp_sleep_enable_timer_wakeup(t_ms*1000);
        esp_light_sleep_start();

    }else if (t_ms > 1000 && count == 3){
        printf("Initialising tcs\n");
        esp_sleep_enable_timer_wakeup((t_ms-350)*1000);
        esp_light_sleep_start();

        begin();
        getRawData(&r, &g, &b, &c);
        colorTemp = calculateColorTemperature_dn40(r, g, b, c);
        lux = calculateLux(r, g, b, c);
        disable();
        printf("TCS Done\n");
        printf("LUX/4: %f\n", lux/4.0);

    }else{
        vTaskDelay(pdMS_TO_TICKS(t_ms));
    }
}

void output_ready(int64_t timestamp, float iaq, uint8_t iaq_accuracy, float temperature, float humidity,
     float pressure, float raw_temperature, float raw_humidity, float gas, bsec_library_return_t bsec_status,
     float static_iaq, float co2_equivalent, float breath_voc_equivalent)
{
    //prepare the data

}

uint32_t state_load(uint8_t *state_buffer, uint32_t n_buffer)
{

    nvs_handle my_handle;
    esp_err_t err = nvs_open("state", NVS_READWRITE, &my_handle);
    ESP_ERROR_CHECK( err );
    err = nvs_get_blob(my_handle, sensor_binary, state_buffer, &n_buffer);
    nvs_close(my_handle);
    if (err == ESP_OK){
        return n_buffer;
    }
    ESP_LOGW(TAG, "loading sensor binary blob failed with code %d", err);
    return 0;
}

void state_save(const uint8_t *state_buffer, uint32_t length)
{

    nvs_handle my_handle;
    esp_err_t err = nvs_open("state", NVS_READWRITE, &my_handle);
    ESP_ERROR_CHECK( err );

    err = nvs_set_blob(my_handle, sensor_binary, state_buffer, length);
    ESP_ERROR_CHECK( err );
    err = nvs_commit(my_handle);
    ESP_ERROR_CHECK(err);
    nvs_close(my_handle);
}

uint32_t config_load(uint8_t *config_buffer, uint32_t n_buffer)
{
    ESP_LOGI(TAG, "Loading configuration: buffer-size %d  config size %d", n_buffer, sizeof(bsec_config_iaq));
    assert(n_buffer >= sizeof(bsec_config_iaq));
    memcpy(config_buffer, bsec_config_iaq, sizeof(bsec_config_iaq));

    return sizeof(bsec_config_iaq);
}

int64_t GetTimestamp() {
  struct timeval tv;
  gettimeofday(&tv, NULL);
  int64_t tm = ((tv.tv_sec * 1000000LL) + tv.tv_usec);
  printf("The timestamp is %llu\n", tm);
  return tm;
}

void bsec_iot_loop(sleep_fct sleep, get_timestamp_us_fct get_timestamp_us, output_ready_fct output_ready,
                    state_save_fct state_save, uint32_t save_intvl)
{
//do some stuff
gotoSleep();
}

void sensorBeginRun() {
    rtc_gpio_hold_dis(GPIO_NUM_16);
    rtc_gpio_hold_dis(GPIO_NUM_13);
    i2c_init(I2C_NUM_0, GPIO_NUM_16, GPIO_NUM_13, 400000);
    printf("Initialised I2c\n");
    return_values_init ret;
    ret = bsec_iot_init(BSEC_SAMPLE_RATE_ULP, 0.0f, bus_write, bus_read, bme680_sleep, state_load, config_load);
    if (ret.bme680_status || ret.bsec_status)
    {
        printf("Could not initialise BME\n");
        esp_restart();
    }
    bsec_iot_loop(bme680_sleep, GetTimestamp, output_ready, state_save, 0);
}

Any help will be greatly appreciated.
It is also very hard to reproduce because it gets stuck sporadically and not after the same number of cycles.

Thanks for reporting.

@sagar448 Thanks for reporting, would you please help provide simple working example to reproduce this issue? Thanks.

@Alvin1Zhang I think we had the same issue but not exactly in the ESP-IDF. We are using Arduino with the leatest versions (for the board and for the Arduino env itself).
We investigated that this issue is only happened when we are on battery power (3.3V). I do not want to falme this thread, so here is the link where I wrote the symptomps: https://github.com/espressif/arduino-esp32/issues/796#issuecomment-678757960
If I can try or check anything for you to help solving the problem please let me know. Thanks.

@zonehun stop hijacking my post please. Post your issue in the arduino section.
@Alvin1Zhang I cannot provide an example because its very random. But I think we have solved this issue.
For anyone experiencing the same, we essentially stripped down the esp32 form the menuconfig. Disabling features we did not need.


Feature: shell-like combinators for conditional computation and sending several commands to server in a single batch

Currently it's impossible to consume stdout and exit codes of commands in toml config. One has to use exec-and-forget
alt-w = 'exec-and-forget aerospace workspace W --fail-if-noop || aerospace workspace-back-and-forth'
atl-tab = 'exec-and-forget aerospace list-workspaces --all | aerospace workspace next'

It's slow. Communicating with the server back and forth from CLI client can take additional 100ms which becomes noticeable. Even if we fix the slowness somehow, annoying flickering will still remain an issue
It'd be cool if AeroSpace supported basic shell combinators (||, &&, ;, ( ))
alt-w = 'workspace W || workspace-back-and-forth'
atl-tab = 'list-workspaces --all | workspace next'

That's a big feature that lays the foundation for a lot of things (basically the combinators allow programming custom logic):

It becomes possible to send a batch of commands from CLI to server at once, resulting in reduced flickering (because server already implements "double buffering" to reduce flickering)
https://nikitabobko.github.io/AeroSpace/goodness#use-trackpad-gestures-to-switch-workspacesaerospace eval 'list-workspaces --monitor mouse --visible | xargs workspace; aerospace workspace next'

Or alternatively without xargs:aerospace eval 'list-workspaces --monitor mouse --visible | workspace -; workspace next'

It fixes the ugliness of on-window-detected TOML callback. The new syntax is much more compact and powerful. It remains readable for people familiar with shell:on-window-detected = '''
    test %{app-bundle-id} == com.jetbrains.intellij && move-workspace-to-monitor I
        || test %{app-bundle-id} == com.google.Chrome && move-node-to-workspace W
        || test %{app-bundle-id} == com.apple.dt.Xcode && (move-node-to-workspace X; exec-async 'echo hi!')
'''

It opens up a possibility for even more powerful conditional gaps #60:[gaps]
outer.left = 'test %{workspace-tiling-windows-count} --lessThan 2 && echo 100'
outer.right = 'test %{workspace-tiling-windows-count} --lessThan 2 && echo 100'

It makes everything more universal and reusable. E.g. there won't be need to fix #107 if config command allows to query on-window-detected command:aerospace eval 'config --get on-window-detected | eval -'

Other subcommands that AeroSpace has to implement to make the feature complete:

test similar to GNU test but with possibility to interpolate AeroSpace special variables like %{window-title}, %{window-name}, %{app-bundle-id}, %{workspace-tiling-windows-count}, etc #150
xargs similar to GNU xargs UPD: stop turning it into a programming language
echo similar to GNU echo
exec-async as a replacement for exec-and-forget. The problem with exec-and-forget that it's not parsed as real CLI command, making it impossible to use the command with combinators
eval to evaluate "AeroSpace script" from argv[1]

Overall a lot issues can be fixed: #264 #60 #54 #174 (partially) #104 (partially) #107 (kinda) #150
Open question: doesn't it open a pandora box of own script programming language? It kinda does. I hope that people will never ask for loops

Draft:
on-window-detected = '''
if test %{app-bundle-id} == com.jetbrains.intellij.ce || test %{app-bundle-id} == com.jetbrains.intellij do
    move-workspace-to-monitor I
elif test %{app-bundle-id} == com.google.Chrome do
    move-node-to-workspace W
elif test %{app-bundle-id} == com.apple.dt.Xcode do
    move-node-to-workspace X; exec-async 'echo hi!'
end
'''

Since it's a custom language, it'd be good to be able to print AST for better discoverability and debugging
$ aerospace eval --print-ast-and-exit '
if test %{app-bundle-id} == com.jetbrains.intellij.ce do
    move-workspace-to-monitor I
end

echo 'hi!'
'

IfBlock
    IfCondition
        Command
            ['test', '%{app-bundle-id}', '==', 'com.jetbrains.intellij.ce']
    IfThenBlock
        Command
            ['move-workspace-to-monitor', 'I']
Command
    ['echo', 'hi!']

I think this sounds like it would be an incredible addition to the project.
Have you thought about using existing embeddable scripting languages such as lua? I think this would be great for several reasons: (I'll use lua as an example here, but there other options)

Users can leverage existing tooling, such as:

text editor syntax highlighting
language server clients (With type def comments, in the case of lua lsp)
package managers for plugins/extensibility

No need to maintain a custom language/interpreter/vm.

A good example of this is neovim with lua vs vim with vimscript. The vim project spends a significant amount of time implementing and maintaining vimscript, whereas neovim is able to iterate quickly and use a tried and tested scripting language with its own maintainers and development cycle.

No need to embed scripts as strings in a toml file
Things like callbacks can use an event handler pattern:aerospace.on('window-detected', function(window) print(window.app_bundle_id) end)

This of course would come with some cons, too:

You miss out on the fun of building your own language 😄
There doesn't seem to be any actively maintained swift bindings for lua specifically
Overhead. Using a general scripting language vs something lean and bespoke could increase build sizes and potentially impact performance. (Although luajit is fast)
It could be off putting to new users. Keeping a toml file that's easy to configure, with the option of extending by adding scripts as multiline strings is a good compromise to cater to newcomers and power users alike.

Have you thought about using existing embeddable scripting languages such as lua?

There is also a sketchybar lua plugin 🙂
https://github.com/FelixKratz/SbarLua

Just wanted up this
I currently use the following shortcuts, and the delay due to exec-and-forget feels significant
alt-p = 'exec-and-forget aerospace list-workspaces --monitor focused --empty no | aerospace workspace prev'
alt-n = 'exec-and-forget aerospace list-workspaces --monitor focused --empty no | aerospace workspace next'

As far as I've read here and in https://github.com/nikitabobko/AeroSpace/issues/264, this is supposed to help with that, no?

+1 to the lua idea and just adding something (possibly obvious) but several very powerful tiling wms in the linux space (i3 and awesomewm) have
I was around in the pre-lua awesome wm days and the syntax included shelling things out as described here - it was hairy stuff.
Lua's syntax for a basic aerospace config would be arguably simple than the current toml.

Hi there, noob question: Why not give the user opportunity to write a swift function instead?
I guess, one obvious cons would be that not many people know swift, but still, if you want badly enough some feature, you will be able to stitch together a function.

@karadnik-flutterint you can already do this by creating a fork


Az command changes in documentation and in E2E scripts

What I did

[x] Change docs from az deployment create to az deployment sub create (implicit deprecation)
[x] Change docs from az deployment group to az group deployment (implicit deprecation)
[x] Change e2e and devtools scripts to reflect documented azure commands

What this changes
Documentation and scripts that were using the commands that are implicitly deprecated.  Issue #326
Release Notes
NONE
Resolves issue #326

/azp run e2e


feat(kit): support customization for rating component

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Code style update
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #3547
What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

@vladimirpotekhin updated


fuel.addAsset is not a function

What version of Wallet are you using?
0.0.1
What is happening?
https://wallet.fuel.network/docs/how-to-use/
Click on "Add Asset button"
get "R.addAsset is not a function" error
open browser console, try to type:
asset = ('0x566012155ae253353c7df01f36c8f6249c94131a69a3484bdb0234e3822b5d90', 'BTC', 'btc', 'https://upload.wikimedia.org/wikipedia/commons/thumb/4/46/Bitcoin.svg/1200px-Bitcoin.svg.png')
fuel.addAsset(asset)
get Uncaught TypeError: fuel.addAsset is not a function
at :1:6
steps to reproduce
https://wallet.fuel.network/docs/how-to-use/
Click on "Add Asset button"
get "R.addAsset is not a function" error
How it should behave?
Request for adding new asset
What os are you seeing the problem on?
Windows Desktop
What browser?
Chrome
What is your browser version?
109

same with
const assets = await fuel.assets();
console.debug("Assets ", assets);

Ah, i see, you still have 0.0.1 in your zip on site


Segmentation fault on certain invalid URLs

Certain messages with invalid URLs result in a segmentation fault:
Example message to reproduce:
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Logs:
2021/01/24 22:18:02.242994 handlers.go:69: Message [105609928126824448/374491861823520769/105608094721028096]: RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
2021/01/24 22:18:02.248536 handlers.go:105: > FILE: https://%{HTTP_HOST}%{REQUEST_URI}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0xa55d57]
goroutine 4934 [running]:
main.tryDownload(0xc000606013, 0x22, 0x0, 0x0, 0xc00007ced0, 0x2b, 0xc0001231e0, 0x9d5b340, 0xed79fe91a, 0x10ceb20, ...)
	/discord-downloader-go/downloads.go:461 +0x4f7
main.startDownload(0xc000606013, 0x22, 0x0, 0x0, 0xc00007c9f0, 0x2a, 0xc0001231e0, 0x9d5b340, 0xed79fe91a, 0x10ceb20, ...)
	/discord-downloader-go/downloads.go:390 +0x195
main.handleMessage(0xc0001231e0, 0xc000704200)
	/discord-downloader-go/handlers.go:107 +0x5dd
main.messageCreate(0xc00010e240, 0xc00000ebb0)
	/discord-downloader-go/handlers.go:31 +0x33
github.com/bwmarrin/discordgo.messageCreateEventHandler.Handle(0xc3aae0, 0xc00010e240, 0xb30700, 0xc00000ebb0)
	/go/pkg/mod/github.com/bwmarrin/discordgo@v0.22.0/eventhandlers.go:497 +0x4b
created by github.com/bwmarrin/discordgo.(*Session).handle
	/go/pkg/mod/github.com/bwmarrin/discordgo@v0.22.0/event.go:171 +0x111

Running on Docker (custom alpine-based image) but most likely reproducible in all other environments too.
This happens on both newly posted messages as well as when downloading history (history download will not be able to go past that message unless it is deleted).

@blay09 Thanks for catching this and giving such an apt description, made it very quick to fix.
https://github.com/get-got/discord-downloader-go/commit/fe53f143150a0308a7a7a9f2a14f0a38f6409199

@blay09 Thanks for catching this and giving such an apt description, made it very quick to fix.
https://github.com/get-got/discord-downloader-go/commit/fe53f143150a0308a7a7a9f2a14f0a38f6409199


Optimize FSI dictionary conversion

Let's wait arrow 2.0 to test changes

@Garra1980 I think this issue might be outdated. Since there are no details here, I'll close it. Please reopen if needed.


[v3.3.2] Hard-code Crafty package version

#52  👈
dev

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

Join @GoodM4ven and the rest of your teammates on  Graphite


Need help in resolving error : Could not target platform: 'Java SE 9' using tool chain: 'JDK 8 (1.8)'.

When I try to run 'gradlew clean headless allTests', this error shows up, does anyone know how I can resolve it? I have set my Project SDK to Java 9 already. The project can build and run normally as well. Can anyone help? Thank you

Project SDK is not the same as what can be seen by the system (command prompt). You need to fix the path variable.

'gradlew clean headless allTests' is now working, thank you! @okkhoy Just wondering if it is normal to receive 15 errors when running all tests using Junit because 'gradlew clean headless allTests' can run without error.

@Shengkok  Try: https://github.com/nusCS2113-AY1819S2/forum/issues/7 may be related?


Move scalar function metadata to the registry

Move is-deterministic and default-null-behavior flags to the registry to allow
fetching these without instantiating an executable function.
Added two flags to the existing VectorFunctionMetadata struct. Removed VectorFunction::isDeterministic and VectorFunction::isDefaultNullBehavior APIs.
Extracted VectorFunctionMetadata from VectorFunction.h into FunctionMetadata.h.
Most of the changes are in non-deafult-null-behavior and non-deterministic
functions to remove isDefaultNullBehavior() and isDeterministic() methods and
update registration calls.
Material changes are in the following files:
velox/core/SimpleFunctionMetadata.h

velox/exec/AggregateCompanionAdapter.cpp
velox/exec/AggregateCompanionAdapter.h

velox/expression/Expr.cpp
velox/expression/Expr.h
velox/expression/ExprCompiler.cpp
velox/expression/FunctionMetadata.h
velox/expression/SimpleFunctionAdapter.h
velox/expression/SimpleFunctionRegistry.h
velox/expression/VectorFunction.cpp
velox/expression/VectorFunction.h

velox/expression/tests/ExpressionFuzzer.cpp

@pramodsatya : PTAL.

Thanks @mbasmanova, @aditi-pandit.


fuse: panic in handler for Rename - assignment to entry in nil map

Hi Good,

What is your rclone version (eg output from rclone -V)
rclone v1.36-DEV

Which OS you are using and how many bits (eg Windows 7, 64 bit)
Linux Debian 9.0 (64 bit)

Which cloud storage system are you using? (eg Google Drive)
Google Drive

Same problem as for ACD :

fuse: panic in handler for Rename #973
https://github.com/ncw/rclone/issues/973

And

Rename Panic #1226
https://github.com/ncw/rclone/issues/1226

But i'm using GSuite (Google), and the last version in developpment for the test(s)
Please let me know..
Regards,

Can you paste in the actual panic message please?

Note that this is probably the same problem as #1533

I'm going to close this now as I'm 99% sure it is fixed in 1.37 - if not please re-open.
Thanks
Nick


Add ssh-agent support

Best reviewed commit-by-commit.

[ ] Manually test changes to radicle-ssh to make sure it still works
[ ] Manually test RAD_PASSPHRASE and node run

Otherwise :+1:


Add fun center() to geometry instead of always using the first vertex

Towards #1736

@gino-m  PTAL?

/gcbrun


Onboard the H₂ command line sample to the samples browser.

One minor question: will it be clear to the reader where to look for simulation.sln (since it's several directories up)?

That's a good point, it looks like the *.sln files up a folder aren't getting included by the ZIP files on the samples browser. For instance, downloading the Qrng sample code gives me everything I need to run except the sln file:

At a minimum, it looks like we need to adapt the instructions. Thanks for catching that, @tcNickolas!

It looks like Visual Studio 2019's "anycode" (Open Folder) mode works, let me modify the instructions accordingly.


Kinetic official support of meta-ros

Hey guys,
What is the official kinetic release of the meta-ros? Would it be https://github.com/bulwahn/meta-ros/tree/kinetic-experimental?

There is no official release of kinetic yet, but I am working on that. I currently have a kinetic branch that is almost ready for being announced official. If you would like to help me with the last few task, let me know.

By the way, I am currently on vacation. Once I am back in a week, I can share the current state of my branch with you.

Hi! I am also quite interested on getting kinetic up and running on our oe-build, and would be happy to help.

Help is greatly appreciated. You can find my current state of work at this personal experimental branch:
https://github.com/bulwahn/meta-ros/tree/kinetic-experimental-v4-work-in-progress-v1
As a first step, please try to build it with bitbake core-image-ros-world -k
There are currently two open topics:

the bullet recipe does not work correctly yet, and hence, map-server does not build.
the whole branch is based on a before-sdk-support baseline, we would need to rebase that to master, i.e., I would need to know which patches shall be dropped and which patches are the new ones. If you want to do this, let me know and I will provide details. I tried already once and failed to do this and aborted it. Now I have a better idea what to do.

It might be that you need to cherry-pick some recent commit from master for gcc8 support.
I will probably a work-in-progress-v2 branch on the weekend, look out and be prepared for a new version of this branch.

Thanks @bulwahn. Yes, we found the hard way that we had to update the versions :laughing: the commit is not in the fork yet and we only changed the few packages we use versions, thanks for pin pointing.
I do have interest in having a full ROS deployed soon, instead of only Core. Then your branch will be the way to go. I hope we get the opportunity to test most of packages from your Kinetic branch soon, with the sdk too.
Best.

It has been 6 Months since the last update on this issue.  Is the ongoing or been shelved?

This is what we have running in our setup:
We forked meta-ros and merged the sdk support branch,
Then we did a quick and dirty settings to convert the fork to kinetic
Finally we bumped down the versions of the packages we use (core, msgs, and other considerable close to core packsges) (it is not in the fork)
If u’d like I can merge the missing parts of my fork so you could use the same setup. But it is faaaaaar from a full support. (And bumped versions are already outdated, ketics krep evolving on main ppas)
Best

@bulwahn Gentil Ping about this, can you provide the remaining work to do ? what are the packages not building yet ? I'm quite sure this can be done collaborately

How is this development going?

I would really like to move to Kinetic on it since Indigo is quickly approaching EOL. I will be happy to help with testing and working on the Kinetic branch once you get it released.

We are planning to support melodic, at least at first, as it's listed as the recommended ROS 1 distro by http://wiki.ros.org/Distributions. (See https://github.com/ros/meta-ros/wiki/Superflore-OE-Recipe-Generation-Scheme#milestones for our plans.) But if the community would rather have kinetic be supported ahead of melodic, we can certain change our plans.

Definitely melodic if we can move straight to that! I did not know of this new development work, very glad to see continued effort for ros/ros 2 in oe.

@flplv < Can this issue be closed?

I believe you can close the issue @herb-kuta-lge, regardless I am aware you are doing what is possible to release the official kinetic or melodic with sdk support.
Note to future readers: Supporting full ROS can be a big endeavourer due to the amount of packages existent in the whole ROS ecosystem, my recommendation to those who want to have ROS at Yocto level is to try to reduce the amount of packages to cross build and deploy. On my experience we can already have a pretty stable build with SDK support to the core packages, even though the official release is not there yet.

my recommendation to those who want to have ROS at Yocto level is to try to reduce the amount of packages to cross build and deploy.

FYI, we're handling this by generating recipes for all the packages in the index -- see https://github.com/ros/meta-ros/wiki/Superflore-OE-Recipe-Generation-Scheme .


fix(docs/guide/component): wrong $componentController usage

#14091

I signed it!

@ptgamr, thx ! Could you, please,  address my comment and ping me ?

@ptgamr, I see you tried to use the correct commit message format :+1:
If you want to go the extra mile, you can change it to something like:
docs(guide/component): fix `$componentController` usage

Fixes #14091

(Adding Fixes/Closes #XYZ at the end, closes the related issues automatically when merging the PR.)

@gkalpak I've updated the PR. Thanks for your comment!

Backported to v1.5.x as 2dda75b.
Thx @ptgamr !

Thanks @gkalpak  :+1:


Program crashes when invoked in cmd.exe

The program just crashes when attempting to run via cmd.exe. Hence I couldn't test if the CLI interface is still available for this fork.

@mfaizsyahmi how to reproduce this error?

run cmd.exe
enter bpsguy.exe path
press enter

works, starting GUI without map.

@mfaizsyahmi in latest build this issue is fixed.


Determine syntax for installing app on all nodes

where do args go for each?

added using all tag


version bump to 2.0.0-rc6, and updating to use pallet_contracts

[ ] Are the audience and objective of the document clear? E.g. a document for developers that should teach them about transaction fees.
[ ] Is the writing:

[ ] Clear: No jargon.
[ ] Precise: No ambiguous meanings.
[ ] Concise: Free of superfluous detail.

[ ] Does it follow our style guide?
[ ] If this is a new page, does the PR include the appropriate infrastructure, e.g. adding the page to a sidebar?
[ ] Build the page ($ cd website && yarn start). Does it render properly? E.g. no funny lists or formatting.
[ ] Do links go to rustdocs or devhub articles rather than code?
[ ] If this PR addresses an issue in the queue, have you referenced it in the description?

in doing a bump, noticed the Cargo.toml file should be updated to use the correct syntax for the pallet crates as well 😁

Think that's got it. 🤞🏼
Glad to see you here as well, @JoshOrndorff ! Been a long time coming from ETHDenver days and your epic workshop! Finally getting into learning substrate 😁

Think that's got it. 🤞🏼
Glad to see you here as well, @JoshOrndorff ! Been a long time coming from ETHDenver days and your epic workshop! Finally getting into learning substrate

welcome to the repo @NukeManDan -- we are excited to see your contributions! come hang at the riot if you're around :+1:

updated to 2.0.0 🎉
But - there are hangnging 0.8.0-rc6 tags/versions of packages here, not sure if those are/need to be updated.

updated to 2.0.0
But - there are hangnging 0.8.0-rc6 tags/versions of packages here, not sure if those are/need to be updated.

yes all can be updated and CI ran to ensure no broken links


[Suggestion] REST API

I'd like to use this software in my project but am not really experienced with the language.
Please consider making a REST API of this project for us who want to use it from another language :)

This project is for educational purposes only. It should be self-hosted for personal devices only. Not intended for online deployment and multiple devices. Hence, we should not create an API for this.

I think having a (simple) REST API would be cool :-)
Although this will be quite a lot of work, so it would be out of scope for this project:

API controller, which handles all http requests
database
background processing/worker for outgoing webhooks
wrapper and selenium controller, with docker remote control for scaling
status, heartbeat
attachment store
...

@mukulhase Said that He never wants this project to have a REST-API since
this would encourage spamming.
Also I think it is okay to drop support for Python 2.
I am not quite sure about Chrome, nur definitly against dropping Support
for Windows, this will make the repo less attractive for educational
purposes (this is the reason behind this project).
I think instead of this the documentation on how to set it up should be
improved.
And also docker should be adverted and stabilized more - since this would
make up for most troubles
Christian Ott<EMAIL_ADDRESS>schrieb am Mo., 4. Juni 2018,
09:42:

I think having a (simple) REST API would be cool :-)
Although this will be quite a lot of work, so it would be out of scope for
this project:

API controller, which handles all http requests
database
background processing/worker for outgoing webhooks
wrapper and selenium controller, with docker remote control for
scaling
status, heartbeat
attachment store
...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mukulhase/WebWhatsapp-Wrapper/issues/225#issuecomment-394263063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGhecTCBHoa45GhGMkkuqfbwMvKGmxtGks5t5OTxgaJpZM4UPSRb
.

Hi @chriso0710 any advance about this ? You need help to start ?

You can use api-messenger.com, but it is charged.

@modcastro Building an API for this project was more an idea/concept rather than a real plan :-)
I moved to Twilio Whatsapp. Still in beta, not free, but very easy to use and the (sandboxed) API works great!


STORM-188: Allow user to specifiy full configuration path when running storm command

We can use system config "storm.conf.file" to specify a custom config file.
Before this patch, we will only try to lookup this file on jvm classpath.
This patch will give us the ability to specify full/relative filesystem path as configuration file path, thus will give us more flexibility, while we still are able to look it up on jvm classpath.
Now we are able to submit storm topology like this:
storm jar job.jar --config /tmp/dynamic-configuration-path.yaml

We don't need to add /tmp into our classpath(also inappropriate).

@clockfly any update on this?  I just had the one minor comment, and I am happy to do it myself in a follow up JIRA if you want.  Just curious if this is still on your radar.

@revans,
Feel free to do what you want, change it, or replace it.:)

guys, any updates on issue ?

@clockfly , It seems this pull request was superseded by #495, and STORM-188 has been resolved.  Would you close this pull request?

Sure.


Need some method to navigate back to "home"

Appears that once you drill into a section, there isn't a quick method to return "home"

Could add some sort of Home/Back/Main Menu/etc... link to the following lines:

https://github.com/BenLubar/weblegends/blob/f0d8bd948cb231d6afc986e53d837cf2cf83c534/render_list.cpp#L68
https://github.com/BenLubar/weblegends/blob/413fe3b64cb9a9913a3659dce547e828638bf04c/helpers.cpp#L801

I'll take care of this


Having extra meta and different tags on my html head section

How can I go about having the code below in my 'master' template? It is not clearly indicated in the docs and I believe the package uses a special tag for hooking the components onto the body tag.
<head>
	<meta http-equiv="content-type" content="text/html;charset=UTF-8"/>
	<meta charset="utf-8"/>
	<title>Meteor Admin</title>
	<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"/>
	<link rel="apple-touch-icon" href="/ico/60.png">
	<link rel="apple-touch-icon" sizes="76x76" href="/ico/76.png">
	<link rel="apple-touch-icon" sizes="120x120" href="/ico/120.png">
	<link rel="apple-touch-icon" sizes="152x152" href="/ico/152.png">
	<link rel="icon" type="image/x-icon" href="favicon.ico"/>
	<meta name="apple-mobile-web-app-capable" content="yes">
	<meta name="apple-touch-fullscreen" content="yes">
	<meta name="apple-mobile-web-app-status-bar-style" content="default">
	<meta content="" name="description"/>
	<meta content="" name="author"/>
</head>

<body class="fixed-header ">
</body>

Do I simply have it in any page or there is a meteor way of ensuring that this file gets used as the main body holder?

You can create a simple .html package with these if these are static. Or use our DocHead project.

How does DocHead work with  descriptions like <link rel="apple-touch-icon" sizes="152x152" href="/ico/152.png">?


Input method select list position is not correct

MacOS Mojave 10.14.2
Alacritty v0.2.7

Note this is not macOS-specific, but has been reproduced on Linux in #2061.

@chrisduerr Why not update ime position after redraw?

@chrisduerr That patch does not fix the issue for me, the IME position is unchanged.
I quickly fixed it for myself by dividing nspot_x and nspot_y in update_ime_position by hidpi_factor.

Not taking DPI into account, sounds like a very likely cause for this problem! Thanks for looking into this @awused, unfortunately I'm completely unfamiliar with IME.
Would you mind sending a PR? I'll gladly help out with style or other issues if there still are some.

@chrisduerr , @awused 's PR code works fine for me


edgedb: 6.0.2 -> 6.1.0; migrate to pkgs/by-name

https://github.com/edgedb/edgedb-cli/releases/tag/v6.0.3
https://github.com/edgedb/edgedb-cli/releases/tag/v6.1.0
diff: https://github.com/edgedb/edgedb-cli/compare/v6.0.2...v6.1.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I fixed error and includes diff on commit message


Cubemap TSCN/TRES

Operating system or device - Godot version:
Debian Testing, mesa 12.0.1, godot 2.1.rc1.custom_build
Issue description (what happened, and what was expected):
Cubemaps are broken if saved as a sub-resource in a TSCN scene or as TRES resources. Looking at the very heavy generated file, it seems Godot saves the textures inside the file in text format, instead of simply referencing them! When playing the scene there is no sky. If you save the same scene as SCN or the resource as CBM there is no problem.
Steps to reproduce:
Add a world environment to a TSCN scene, new environment, set mode to cubemap, new cubemap, edit the cubemap adding the 6 required textures such as http://opengameart.org/content/sky-box-sunny-day/, save the scene, the saved .tscn file weights a lot of MBs! Run the scene and there is no sky...

Related to #4240

Is this still valid on master/3.0?

Now it works as expected, thanks! By the way, is it possible to convert an old project to Godot 3.0?

@Elinvention Yeah, don't worry, it would be an exporter in 2.1.3/2.1.4 (2.1.3 WIP preview, 2.1.4 final, I guess)


Event subscription causing errors with version 0.15.6

After upgrading to<EMAIL_ADDRESS>event callback is reporting the following warnings/errors:
(node:22444) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 701): TypeError: Cannot read property '0' of undefined
(node:22444) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 702): TypeError: Cannot read property '0' of undefined
Call of Eris DB method 'eventPoll' with parameters {
  "sub_id": "FA4F86B87B112D5422D7CBD2A9C4F944462797C87DB4425FB1693492DA6D531C"
} responded with "Subscription not active. ID: FA4F86B87B112D5422D7CBD2A9C4F944462797C87DB4425FB1693492DA6D531C".
Call of Eris DB method 'eventPoll' with parameters {
  "sub_id": "FA4F86B87B112D5422D7CBD2A9C4F944462797C87DB4425FB1693492DA6D531C"
} responded with "Subscription not active. ID: FA4F86B87B112D5422D7CBD2A9C4F944462797C87DB4425FB1693492DA6D531C".

This didn't happen with<EMAIL_ADDRESS>

https://github.com/eris-ltd/eris-db.js/issues
Same issue maybe

Which version of Eris DB are you using?

eris 0.12

Thanks, I'm asking @vkandy.

@NodeGuy As for the platform, I have:
$ eris version
Eris CLI Version: 0.11.4

As for npm modules, I have "eris-contracts": "^0.15.6"  and looks like that depends on "eris-db": "^0.15.4".

Thank you.  This bug is caused by an incompatibility between versions; you need to upgrade to version 0.12 of the CLI.

@NodeGuy I upgraded to 0.12 but it seems to happen with the latest version too:
Call of Eris DB method 'eventPoll' with parameters {
  "sub_id": "2E75567B84E57E6842F0C5650FA23F5E8B6F0AB55F0527DC4D746460F25BD6DE"
} responded with "Subscription not active. ID: 2E75567B84E57E6842F0C5650FA23F5E8B6F0AB55F0527DC4D746460F25BD6DE".
Call of Eris DB method 'eventPoll' with parameters {
  "sub_id": "BBE5375038F7689C64500A9F52428809BB3B511529448983943E8214C275365C"
} responded with "Subscription not active. ID: BBE5375038F7689C64500A9F52428809BB3B511529448983943E8214C275365C".

It happens just after this error:
{ Error: Transaction timed out. Hash: 3AA18BBD85E1079FD95356B2172298DA2273C647
    at values.next.then (/home/vkandy/.../node_modules/eris-contracts/node_modules/eris-db/node_modules/@nodeguy/json-rpc/lib/index.js:12:38)
  method: 'transactAndHold',
  params:
   [ { priv_key: '06D6...2',
       address: '8010...C',
       data: '54a12efc34383531303030304a5a31374e5747554135313000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001480bd88bd9bd50d818e77b46da23de9e829c166c5fc4525df292bfff9636f389',
       gas_limit: 1000000,
       fee: 0 } ],
  code: -32603,
  message: 'Transaction timed out. Hash: 3AA18BBD85E1079FD95356B2172298DA2273C647' }

Thank you, that looks like a different error.  I'll investigate.

Ah, the previous error Transaction timed out is an Eris DB error which may be indicating that the subscription transaction didn't succeed.  If so, that would explain why the subscription is not active.
Please report your bug to Eris DB and let that team know how to replicate it.


What is its default settings？

What is its default settings？
sql.Open("sqlite3", "users.db?_key=123456")

@fujiawei-dev  Can you add more details for your question?

@fujiawei-dev Can you add more details for your question?

Thanks for your reply. I meant its default page size, kdf algorithm etc.
sql.Open("sqlite3", "users.db?_key=123456")
But I already know:

Great. Glad you solve it.


Add Sandwichable

https://www.curseforge.com/minecraft/mc-mods/sandwichable

sub sandwich sandwich (too bad i cant make a sub sandwich sandwich sandwich)
but i did once try a sub sandwich sandwich when in SP with the bc23 pack and it did close my client (mabey a crash idk i forgot about it, mabey it was cause i stacked too tall)

Given the issue of "Promoting Food Diversity," adding an objectively best option seems unwise. Not to mention the ability to put potions inside the sandwiches, something I recall seeing in other modpacks via Create.


#Unbound-Plus - Only one DoT server possible

Describe the bug
If I try to add more than one DoT server, it is not possible to save the config.
list validation error
To Reproduce
Steps to reproduce the behavior:

Go to Services / Unbound DNS / Miscellaneous
Add more then one servers to DNS over TLS Servers
Try to save this setting

Expected behavior
The config will be accepted and saved.
Screenshots

Relevant log files
{
  "result": "failed",
  "validations": {
    "miscellaneous.dotservers": "list validation error"
  }
}

Environment
Software version used and hardware type if relevant.
e.g.:
OPNsense 20.1.5-amd64
FreeBSD 11.2-RELEASE-p18-HBSD
LibreSSL 3.0.2
AMD GX-412TC SOC (4 cores)

Having the same issue here.  I'd be happy to help test when a fix is available.


XGBoost Model Perfomance Issue

/kind bug
XGboost model server perform poorly after deployed to k8s.
What steps did you take and what happened:
I did performance test for xgbserver using provided sample model.
load.cfg:
POST http://<target>/v1/models/default:predict
@request.json

req.json:
{"instances": [[1,2,3,4]]}

Running locally (on Mac OS, 8 core machine) with vegeta
cat load.cfg | vegeta attack -duration 1m -rate 1000 | vegeta report -type=text

I am able to hit 1000 RPS with good latencies result.
Requests      [total, rate, throughput]    60000, 1000.02, 1000.00
Duration      [total, attack, wait]        1m0.000012024s, 59.999069988s, 942.036µs
Latencies     [mean, 50, 90, 95, 99, max]  1.070524ms, 946.443µs, 1.414653ms, 1.520775ms, 2.401196ms, 17.650717ms
Bytes In      [total, mean]                1320000, 22.00
Bytes Out     [total, mean]                1560000, 26.00
Success       [ratio]                      100.00%
Status Codes  [code:count]                 200:60000

But after deployed to K8S (with 4 core as CPU request and limit)
The performance deteriorates at 100 RPS
cat load-1.cfg | vegeta attack -rate 100 -duration 60s | vegeta report

Requests      [total, rate, throughput]    6000, 100.02, 89.47
Duration      [total, attack, wait]        1m7.064629048s, 59.989775627s, 7.074853421s
Latencies     [mean, 50, 90, 95, 99, max]  1.524605151s, 3.683733ms, 5.575147148s, 7.007148666s, 7.789309456s, 8.606190814s
Bytes In      [total, mean]                132000, 22.00
Bytes Out     [total, mean]                192000, 32.00
Success       [ratio]                      100.00%
Status Codes  [code:count]                 200:6000

What did you expect to happen:
The performance should not be affected too much after deployed to K8S.
Anything else you would like to add:
I suspected the issue come from nthread in xgbserver are left to default (i.e. 0).
In:
https://github.com/kubeflow/kfserving/blob/c46a0da8c0cf168dccfcee3b79f306fea135faf4/python/xgbserver/xgbserver/model.py#L36
and
https://github.com/kubeflow/kfserving/blob/c46a0da8c0cf168dccfcee3b79f306fea135faf4/python/xgbserver/xgbserver/model.py#L42
Which will leave the decision of number of thread to use to xgboost by detecting number of cpu. However, possibly due to this https://bugs.python.org/issue36054, the nthread is incorrect and causing the performance issues.
I did a test with setting nthread=1 :
class XGBoostModel(kfserving.KFModel):
    def __init__(self, name: str, model_dir: str, booster: XGBModel = None):
        super().__init__(name)
        self.name = name
        self.model_dir = model_dir
        if not booster is None:
            self._booster = booster
            self.ready = True

    def load(self):
        model_file = os.path.join(
            kfserving.Storage.download(self.model_dir), BOOSTER_FILE)
        self._booster = xgb.Booster(params={"nthread" = 1},model_file=model_file)
        self.ready = True

    def predict(self, request: Dict) -> Dict:
        try:
            # Use of list as input is deprecated see https://github.com/dmlc/xgboost/pull/3970
            dmatrix = xgb.DMatrix(request["instances"], nthread=1)
            result: xgb.DMatrix = self._booster.predict(dmatrix)
            return { "predictions": result.tolist() }
        except Exception as e:
            raise Exception("Failed to predict %s" % e)

cat load.cfg | vegeta attack -rate 1000 -duration 60s | vegeta report

and it performed much better:
Requests      [total, rate, throughput]    60000, 1000.02, 999.99
Duration      [total, attack, wait]        1m0.00064503s, 59.9988685s, 1.77653ms
Latencies     [mean, 50, 90, 95, 99, max]  1.927362ms, 1.73989ms, 1.941139ms, 2.490536ms, 5.660895ms, 56.707145ms
Bytes In      [total, mean]                1320000, 22.00
Bytes Out     [total, mean]                1920000, 32.00
Success       [ratio]                      100.00%
Status Codes  [code:count]                 200:60000

The question here is:

Is setting nthread=1 a good idea for other kind of workload?
Should this be configurable?

Environment:

Istio Version: 1.1.7
Knative Version: 0.8.1
KFServing Version: 0.2.1
Kubeflow version: NA
Minikube version: NA
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

Great find! Let me find someone who can look into this with you. Agreed that we need to find a good value for this. May also need to pass a config param.

Sure, I'll amend the PR if configuration is needed


AWS 2-6: Generate Static Tiles for Lower Zoom Levels for Other IO Datasets

In #9, we generated static tiles for zoom levels 0-8 for the Impact Observatory Global LULC 2023 dataset. Now that we've figured out the way to do it, we should do it for the other remaining datasets: 2017, 2018, 2019, 2020, 2021, and 2022.
Once ready, they should be added to the staging tile cache bucket on S3.

Static tiles from zoom levels 2 onwards have now been generated for all relevant datasets.


Allow full scheduling options for brokering jobs

What is the motivation for adding/enhancing this feature?

When scheduling brokering jobs, users often schedule or a few days ahead when taking a system live.
What are the acceptance criteria?

we should revisit the schedule brokering UI to make it more optimized for users who are scheduling in multiple days etc.

This is is handled in the new brokering page


process-template.yml - fix "with_dict expects a dict" error

What does this PR do?
Fix's an error when using this role.
Maybe specific to Ansible 2.4 but not positive.
How should this be tested?
Ansible 2.4
cicd_project_params:
  NAMESPACE: hello-world-2-cicd
  NAMESPACE_DISPLAY_NAME: Hello World 2 - CICD
  NAMESPACE_DESCRIPTION: Hello World CICD project.

openshift_cluster_content:
- object: projectrequest
  content:
  - name: Create CICD
    template: "{{ inventory_dir }}/files/templates/projectrequest.yml"
    params_from_vars: "{{ dev_project_params }}"
    action: create

Is there a relevant Issue open for this?
Provide a link to any open issues that describe the problem you are solving.
Who would you like to review this?
cc: @redhat-cop/openshift-applier

Don't see why this change is needed (in fact it is reverting some of our "standards"). Can you please provide an issue with some additional details as to why this is needed? Maybe there's something else causing it rather than this proposed change.
BTW: openshift-applier requires Ansible >=2.5.x for other reasons.

Actually, nvm - this change is probably ok, but please write up an issue so we can track the request.


enable adapter testing for your adapter!

Isn't it active? Each commit is being tested I think. Green checked symbol behind?!

me too blind :-)


video not download

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.07.18 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
france
Provide a description that is worded well enough to be understood
the video is downloaded, but the video cannot be viewed.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -vU https://prod-avod-pmd-edgecast.cdn.rakuten.tv/2/b/c/2bce8e0c66bd3cb63840d52ed6ff08c2-mc-0-144-0-0_DS2BB/video-avc1-3.ismv
[debug] Command-line config: ['-vU', 'https://prod-avod-pmd-edgecast.cdn.rakuten.tv/2/b/c/2bce8e0c66bd3cb63840d52ed6ff08c2-mc-0-144-0-0_DS2BB/video-avc1-3.ismv']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.07.18 [135f05e] (zip)
[debug] Python 3.8.10 (CPython 64bit) - Linux-5.4.0-122-generic-x86_64-with-glibc2.29 (glibc 2.31)
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 4.2.7, ffprobe 4.2.7, phantomjs 2.1.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.06.15, mutagen-1.45.1, pyxattr-0.6.1, secretstorage-2.3.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.07.18, Current version: 2022.07.18
yt-dlp is up to date (2022.07.18)
[debug] [generic] Extracting URL: https://prod-avod-pmd-edgecast.cdn.rakuten.tv/2/b/c/2bce8e0c66bd3cb63840d52ed6ff08c2-mc-0-144-0-0_DS2BB/video-avc1-3.ismv
[generic] video-avc1-3: Downloading webpage
[debug] Identified a direct video link
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] video-avc1-3: Downloading 1 format(s): fmp4
[debug] Invoking http downloader on "https://prod-avod-pmd-edgecast.cdn.rakuten.tv/2/b/c/2bce8e0c66bd3cb63840d52ed6ff08c2-mc-0-144-0-0_DS2BB/video-avc1-3.ismv"
[download] Resuming download at byte 152341901
[download] Destination: video-avc1-3 [video-avc1-3].ismv

That file is corrupt but downloads just fine. It doesn't play in browser either so I'd say yt-dlp is working as intended.


Newline and even semicolon sometimes ignored as end marker

Description
SELECT *
FROM foo
WHERE 1=1

AND bar=1

does not execute, but errors out with
SQL Error [42601]: ERROR: syntax error at or near "AND"
SELECT *
FROM foo
WHERE 1=1;

AND bar=1

yields the same error.
Doesn't happen always and not in every editor.
DBeaver Version
Version <IP_ADDRESS>404211624
Operating System
Debain/Linux
Database and driver
Postgres 15, PostgreSQL JDBC Driver, cannot find more info in DBeaver.
Steps to reproduce
No response
Additional context
No response

Thank you for bug report. It's a duplicate of #26416
We're working on fix
As a workaround, you could try switching Blank line is statement delimiter setting to Always


mps/cmake: add cmake build

Summary

mps2-an500:add mps2-an500 cmake build
mps2-an521:add mps2-an521 cmake build
mps3-an547:add mps3-an547 cmake build
fix comments

Impact
Testing

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX Requirements.
Here's why and how to fix it:
Summary:

Missing Why:  You list what boards are added but not why these boards are being added or what functionality they provide.  What problem does this solve? What new capabilities do these boards bring to NuttX?
Missing How: You mention adding CMake builds, but not how these builds are structured.  Do they use any special configurations? Are there any dependencies on other parts of the NuttX codebase?
Issues/PR References: Are there any related issues or pull requests in either the NuttX or NuttX Apps repositories? If so, provide links to them.
**Comment Fix: ** Be more specific. What comments were fixed? Why were they incorrect, and how were they improved?

Impact:

All sections are blank. You need to thoroughly address each impact category:

Feature: Are you adding a new feature or changing an existing one?
User Impact: Will users need to change their workflow or configuration? If so, how?
Build Impact:  Will the NuttX build system need any modifications? Are there new build options?
Hardware Impact: Be specific about the architectures, boards, and drivers affected.
Documentation: If this PR introduces new features or changes existing ones, you'll need to update the documentation.  State whether documentation updates are included in this PR.
Security/Compatibility: Even if there are no impacts, you should explicitly state "NO" and briefly explain why.

Testing:

Provide Details: Specify the exact build hosts (OS, CPU, compiler versions) and targets (architecture, board, configuration) you used for testing.
Include Logs: Paste the relevant portions of your testing logs both before and after the changes. The logs should demonstrate that the new boards can be built successfully and function as expected.

Additional Tips:

Conciseness: While the provided template is a good starting point, aim for a balance between conciseness and completeness.
Clarity:  Use clear and straightforward language. Avoid technical jargon that might not be familiar to all reviewers.
Correctness: Double-check all information for accuracy before submitting the PR.

By addressing these points, your PR will be more likely to be reviewed and merged quickly.


add variant endpoints to IMasterloopServerConnection

add the newly created variant methods to IMasterloopServerConnection interface
update the test project to use the IMasterloopServerConnection interface so that tests will help identify missing endpoints from interface

PR approved


fix fix unstable regression test cases found in p0

Proposed changes
Issue Number: close #xxx
Problem summary
fix below cases:

nereids_p0/sql_functions/json_function/test_query_json_object
nereids_p0/sql_functions/math_functions/test_multiply
nereids_syntax_p0/lateral_view
nereids_syntax_p0/window_function
query_p0/sql_functions/array_functions/test_array_functions_of_array_difference
query_p0/sql_functions/json_function/test_query_json_array
query_p0/sql_functions/json_function/test_query_json_object

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Be great to get this dockerized and up on docker hub

I could give this a try. I've read on Plex forum that this is not working anymore though. Is that right ?

Yeah, from what I can tell. I know it only supports o e account though, so
no matter who watches it, it marks it off on the same account. Would be
nice to be able to have it work per-user instead of per-server.
On Fri, Jun 28, 2019, 3:45 AM Nicu<EMAIL_ADDRESS>wrote:

I could give this a try. I've read on Plex forum that this is not working
anymore though. Is that right ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tvshowtime/tvshowtime-plex-scrobbler/issues/19?email_source=notifications&email_token=AD3BFUIM3CIK6BNFDX5W6ITP4W6R5A5CNFSM4FHXLEWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYZK7RA#issuecomment-506638276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD3BFUJLVALL4K6SNOWN3E3P4W6R5ANCNFSM4FHXLEWA
.


Ability to convert native engine types to JSON and back.

Implements https://github.com/godotengine/godot-proposals/issues/9510
TODO: Unit tests.

Pushed an update with some style nitpicks, but also flagging some bugs in the implementation based on a first code review.

This looks very interesting, I'll test it out and go through the code this weekend hopefully

Did some testing locally with this project, which could be used as a base for further testing and unit tests:
testjson.zip
Some issues I noticed:

As expected in https://github.com/godotengine/godot-proposals/issues/9510#issuecomment-2092488711, this doesn't guarantee proper conversion of int and float. Round float values are written without .0 and so Godot reads them as int. This is alleviated for typed properties, but for variants this is still an issue.

Null objects are serialized as e.g.

"material": {
	"__gdtype": "Object"
},

but the to_native code will currently just throw an error in this case:
ERROR: Condition "!d.has("type")" is true. Returning: Variant()
   at: to_native (./core/io/json.cpp:1167)

It needs better handling of null Objects as a valid format.

Array logic seems to crash, this in my test project causes a segfault:

@export var _array: Array = [42.0, 10, Vector2.AXIS_X

If converting an object to JSON and back with objects and scripts allowed, and the script has a class name, converting to native causes an error:

Parser Error: Class "MyNode2D" hides a global script class.

@akien-mga Ah thanks for the feedback and the fixes, I did not test the code much because I wanted to ask for implementation feedback first, then I was going to do the unit testing to ensure everything works properly.

Tested and works as expected, at a glance the code looks good too, with some cases pointed out above

I don't necessarily see anything that's needed save for the code errors that need resolving

I did some review, the entire Variant section is failing to convert. I'll probably write some unit tests.

I did some review, the entire Variant section is failing to convert

Probably the code errors reviewed above, try fixing those and see if it works then

Superseded by https://github.com/godotengine/godot/pull/92656.


Probit node ported to ReactiveMP

This pull request ports the Probit node from ForneyLab.jl to ReactiveMP.jl
This node is based on the paper:
M. Cox and B. De Vries, "Robust Expectation Propagation in Factor Graphs Involving Both Continuous and Binary Variables," 2018 26th European Signal Processing Conference (EUSIPCO), 2018, pp. 2583-2587, doi: 10.23919/EUSIPCO.2018.8553490.
available here.
Importantly, the derivations from the paper and the implementation differ slightly as the second (unnormalized!) moment of g (from the paper) has one of its signs inverted. This has been fixed in the implementation.
Additionally, the calculation of the average energy of the Probit node has been altered with respect to its implementation in ForneyLab. In the case that we have a standard Normal distribution on the continuous input of the node, the average energy of the node should return 1. See comment on StackExchange.
Furthermore this pull request includes tests for the Probit node and rules. Currently, the rules experience some type conversion issues, causing some of them to fail. I was not able to fix this myself.

Great work, @bartvanerp! Thanks for the tests! I think this PR is ready to be merged.

@bartvanerp thank you for this PR! It looks great, I fixed tests, all are green! Would it be ok for you if I wait with merging? Technically Probit works under moment matching constraint and not under Marginalisation constraint. Current implementation uses Marginalisation constraint however. I will work on MomentMatching constraint and EP algorithm in general this week and then I will merge!

Great work, @bartvanerp!


Kubernetes Components - architectural diagram

The high level overview of the kubernetes components uses a .svg file for the presentation. The content is clearly presented but some of the labels for each components are too small.
I suggest that either the labels are made bigger or a diferent logo is used for each of these components. API Server, Cloud control manager , controller manager.
Example screenshoot on Full HD screen.

/retitle Labels on cluster diagram are hard to read

These are the official icons for each component. We should continue to use the official icons.
One thing I considered when drawing this diagram, but left because its extra work: use flexbox to allow laying out the key to the diagram below if the viewport is not big enough to show it clearly.
Less effort: add a mechanism to let people click on a diagram to see it enlarged (and then click again to go back). Good implementations of this work with the History API so that the Back button also returns you to the page you were viewing.

/triage accepted
/priority backlog
/language en

I would like to do this


How to get Category

Hi
It is possible to get the  category's name of a calendar's event ?
I'm using this :
$request = new EWSType_FindItemType();
$request->Traversal = EWSType_ItemQueryTraversalType::SHALLOW;
$request->ItemShape = new EWSType_ItemResponseShapeType();
$request->ItemShape->BaseShape = EWSType_DefaultShapeNamesType::DEFAULT_PROPERTIES;

$request->CalendarView = new EWSType_CalendarViewType();
$request->CalendarView->StartDate = '2015-06-12T15:18:34+03:00';
$request->CalendarView->EndDate = '2015-10-12T15:18:34+03:00';

$request->ParentFolderIds = new EWSType_NonEmptyArrayOfBaseFolderIdsType();
$request->ParentFolderIds->DistinguishedFolderId = new EWSType_DistinguishedFolderIdType();
$request->ParentFolderIds->DistinguishedFolderId->Id = EWSType_DistinguishedFolderIdNameType::CALENDAR;
$response = $ews->FindItem($request);

if ($response->ResponseMessages->FindItemResponseMessage->RootFolder->TotalItemsInView > 0){
    $events = $response->ResponseMessages->FindItemResponseMessage->RootFolder->Items->CalendarItem;
    foreach ($events as $event){
        $id = $event->ItemId->Id;
        $change_key = $event->ItemId->ChangeKey;
        $start = $event->Start;
        $end = $event->End;
        $subject = $event->Subject;
    #not work $category = $event->Category;
        $location = $event->Location;
        echo $start."     $subject     $location<br>";
    }
}
else {
    // No items returned
    echo "nothing";
}

Thanks a lot

If you change $request->ItemShape->BaseShape to DefaultShapeNamesType::ALL_PROPERTIES, the response will include an array of categories for the item. These are also returned in the response to a GetItem request.


Update site properties and functions

Tableau server 2020.3 api version 3.9 makes available several configuration options for the site endpoint. The changes here are meant to align the site object and its functions with the api.
Linked to Issue https://github.com/tableau/server-client-python/issues/776

Got the CLA, thanks!

Got the CLA, thanks!

I believe that the changes made should cover your concerns @shinchris Let me know if there is anything else.

I believe that the changes made should cover your concerns @shinchris Let me know if there is anything else.

@shinchris Thanks for the review. Made the requested changes.


Long time for process to finish on WSL

Describe the bug

I am trying to save a very small tensor using wandb.save, but the process takes a very long time to finish.

import wandb
import torch

project="test"
name="save-tensor"

wandb.init(project=project, name=name)

x = torch.tensor([1, 2, 3])
torch.save(x, 'tensor.pt')
wandb.save('tensor.pt')

wandb.finish()

The line of the shell: / 0.006 MB of 0.009 MB uploaded (0.000 MB deduped) keeps running for 8 minutes at the end of the process.

wandb: Currently logged in as: ******. Use `wandb login --relogin` to force relogin
wandb: Tracking run with wandb version 0.14.0
wandb: Run data is saved locally in ********
wandb: Run `wandb offline` to turn off syncing.
wandb: Syncing run save-tensor
wandb: ⭐ View project at *******
wandb: 🚀 View run at ******
wandb: Waiting for W&B process to finish... (success).
wandb: / 0.006 MB of 0.009 MB uploaded (0.000 MB deduped)

The tensor.pt file is uploaded quickly on the run page on wandb.ai but the program still runs for 10 minutes before ending.
PS: There is no problem with my internet speed. I checked the same program on Windows 11 and there was no problem. It seems to be specific to WSL.
Can someone help me with this issue ? (below you will find the log files for the run)
debug.log
debug-internal.log
Additional Files
No response
Environment
WandB version: 0.14.0
OS: WSL2 on Windows 11
Python version: 3.9
Versions of relevant libraries: pytorch 1.13.1
Additional Context
No response

Hi @Jibril-Frej, thanks for reporting this! There might be some processes still running on the backend and that's why your experiment takes a long time to finish. To better understand this, could you please send debug.log and debug-internal.log? These files are under your local folder wandb/run-<date-time>-<run-id>/logs in the same directory where you’re running your code. Also, is this issue raising every time you run your code or only sometimes?

@Jibril-Frej Thanks for the detailed information. Looking at your logs it is indeed looks like we were stuck in the pooling exit state for around 8 minutes, but i'm still not clear why this is happening. I tried your script locally and it worked quickly for me. Will try to look into the code for a potential reason for this.
One question:  did you happen to try this script on other systems (i.e. not WSL) and if so did you experience the same lag?
I will keep you posted with my findings.

I tried the same script directly on Windows 11 and there was no problem/latency.
I am pretty sure it is related to WSL (I have WSL 2).

I tried the same script directly on Windows 11 and there was no problem/latency. I am pretty sure it is related to WSL (I have WSL 2).

Thank you! This is a very helpful information!

Quick update: If I run the code from docker container in WSL 2 using wandb docker-build there is no latency issue.
There is still the latency issue if I run the code directly from WSL 2.

I have a similar issue, but without WSL, on an Ubuntu machine. Process is stuck on:
wandb: \ 2213.486 MB of 2213.486 MB uploaded (0.000 MB deduped)
My debug-internal.log is too big to upload here, but there's most important part, I think:
[...]
2023-04-18 08:03:44,498 INFO    HandlerThread:192631 [interfaces.py:finish():199] Joined cpu monitor
2023-04-18 08:03:44,499 INFO    HandlerThread:192631 [interfaces.py:finish():199] Joined disk monitor
2023-04-18 08:03:44,552 INFO    HandlerThread:192631 [interfaces.py:finish():199] Joined gpu monitor
2023-04-18 08:03:44,552 INFO    HandlerThread:192631 [interfaces.py:finish():199] Joined memory monitor
2023-04-18 08:03:44,552 INFO    HandlerThread:192631 [interfaces.py:finish():199] Joined network monitor
2023-04-18 08:03:44,552 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,553 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 2
2023-04-18 08:03:44,553 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 3
2023-04-18 08:03:44,553 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:44,553 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 3
2023-04-18 08:03:44,591 DEBUG   SenderThread:192631 [sender.py:send():336] send: stats
2023-04-18 08:03:44,591 DEBUG   SenderThread:192631 [sender.py:send():336] send: history
2023-04-18 08:03:44,591 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: summary_record
2023-04-18 08:03:44,592 INFO    SenderThread:192631 [sender.py:_save_file():1332] saving file wandb-summary.json with policy end
2023-04-18 08:03:44,592 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,592 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 3
2023-04-18 08:03:44,592 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 4
2023-04-18 08:03:44,592 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:44,592 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 4
2023-04-18 08:03:44,592 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,592 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 4
2023-04-18 08:03:44,592 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 5
2023-04-18 08:03:44,592 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:44,592 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 5
2023-04-18 08:03:44,593 DEBUG   SenderThread:192631 [sender.py:send():336] send: summary
2023-04-18 08:03:44,593 INFO    SenderThread:192631 [sender.py:_save_file():1332] saving file wandb-summary.json with policy end
2023-04-18 08:03:44,593 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,593 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 5
2023-04-18 08:03:44,593 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 6
2023-04-18 08:03:44,593 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:44,593 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 6
2023-04-18 08:03:44,593 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,594 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 6
2023-04-18 08:03:44,597 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: status_report
2023-04-18 08:03:44,946 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 7
2023-04-18 08:03:44,947 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:44,947 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 7
2023-04-18 08:03:44,947 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:44,947 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 7
2023-04-18 08:03:45,338 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 8
2023-04-18 08:03:45,338 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:45,338 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 8
2023-04-18 08:03:45,339 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:45,339 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 8
2023-04-18 08:03:45,339 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 9
2023-04-18 08:03:45,339 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:45,339 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 9
2023-04-18 08:03:45,339 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:45,339 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 9
2023-04-18 08:03:45,339 INFO    SenderThread:192631 [dir_watcher.py:finish():365] shutting down directory watcher
2023-04-18 08:03:45,360 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:46,078 INFO    SenderThread:192631 [dir_watcher.py:_on_file_modified():295] file/dir modified: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/output.log
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:_on_file_modified():295] file/dir modified: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/wandb-summary.json
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:_on_file_modified():295] file/dir modified: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/config.yaml
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:finish():395] scan: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/requirements.txt requirements.txt
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/conda-environment.yaml conda-environment.yaml
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/wandb-metadata.json wandb-metadata.json
2023-04-18 08:03:46,079 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/wandb-summary.json wandb-summary.json
2023-04-18 08:03:46,080 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/config.yaml config.yaml
2023-04-18 08:03:46,080 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/output.log output.log
2023-04-18 08:03:46,094 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_48999_9844a5a58cf45c4d0aa2.png media/images/validation_48999_9844a5a58cf45c4d0aa2.png
[...]
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_25999_5a8a6c058682d043b5fa.png media/images/validation_25999_5a8a6c058682d043b5fa.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_67999_8c861195307acbdea966.png media/images/validation_67999_8c861195307acbdea966.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_24999_5d30f8e8a3626a890232.png media/images/validation_24999_5d30f8e8a3626a890232.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_2999_de23c23485a2b2497c2a.png media/images/validation_2999_de23c23485a2b2497c2a.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_47999_def1801b4ef559ba147e.png media/images/validation_47999_def1801b4ef559ba147e.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [dir_watcher.py:finish():409] scan save: /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/media/images/validation_7999_c3182eb39c45580df723.png media/images/validation_7999_c3182eb39c45580df723.png
2023-04-18 08:03:46,200 INFO    SenderThread:192631 [sender.py:transition_state():587] send defer: 10
2023-04-18 08:03:46,201 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:46,213 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: defer
2023-04-18 08:03:46,213 INFO    HandlerThread:192631 [handler.py:handle_request_defer():170] handle defer: 10
2023-04-18 08:03:46,214 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: defer
2023-04-18 08:03:46,214 INFO    SenderThread:192631 [sender.py:send_request_defer():583] handle sender defer: 10
2023-04-18 08:03:46,214 INFO    SenderThread:192631 [file_pusher.py:finish():164] shutting down file pusher
2023-04-18 08:03:46,360 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:46,360 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:46,375 ERROR   wandb-upload_6:192631 [internal_api.py:upload_file():2073] upload_file exception https://storage.googleapis.com/wandb-production.appspot.com/p4vv37/controlnet_restoration_v3/a0ybj77n/requirements.txt?Expires=1681884226&GoogleAccessId=wandb-production%40appspot.gserviceaccount.com&Signature=FWSJmPfNArCoSg5Lu%2FDpf23Z%2BFn70oS4we2Q01q2GZeUURZr2%2BIMwYOiQPMZQZi0UONRDln9TlDJbc4rir9jPSUm%2Fh%2FC3q9bbJyWRAdS1tgYQX7Vkql37SvXesCY%2BF%2BV3Lo1J84NV98yuirINcsDdn8RqOOUxdiYikH%2FWSU3HTCl2zuzSLlv01nWvOTqqRAiBDsPvy9cgG%2FR5XXwfMIGXm81VdWx37sASElYWsrfQuBdytc8lDagK3u3ZF%2FHhIcIB27zw%2BrQg%2BpsJCiHB%2BRbdTQz8ECxKvEp0AWpSkmeCeag%2BUi8yXKbviH5%2BKIeBI2WqiAfBkHxapJkoT5XecjKww%3D%3D: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2023-04-18 08:03:46,376 ERROR   wandb-upload_6:192631 [internal_api.py:upload_file():2075] upload_file request headers: {'User-Agent': 'python-requests/2.28.2', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Length': '3552'}
2023-04-18 08:03:46,376 ERROR   wandb-upload_6:192631 [internal_api.py:upload_file():2077] upload_file response body:
2023-04-18 08:03:46,390 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2073] upload_file exception https://storage.googleapis.com/wandb-production.appspot.com/p4vv37/controlnet_restoration_v3/a0ybj77n/config.yaml?Expires=1681884226&GoogleAccessId=wandb-production%40appspot.gserviceaccount.com&Signature=DeRRTWHFcQT8K%2BxYdtCYSOcNbRyZY%2FnY39EZxkeoPKMimvelLCIdWUiLBWuE21yElwv%2B72ynATaFUDmksI%2BlIIMHFOumsI2Tsga6Q8IKIR5TizHxitEhjj1Qb0IMHpwMinNCrqnSh4fqfsZZMI%2FH3TFPDyNt0KbkHmJTdp2uZZTY29r04mStDRhaUUPtMvqqaLROL51foeqYn6xdYlnt35G7rvJdQAAaAhtksuyX0PaAUuNDRCnZNeiK8ULJVGEIgVssG1LeelaArTvD36e2MgQkzV2njgeHJuYnZSc4Yvli%2BDz%2BHJ7hN8%2F%2BexL%2BkxDmC0COAtj5Yl4kAQr%2B6mTMSw%3D%3D: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2023-04-18 08:03:46,391 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2075] upload_file request headers: {'User-Agent': 'python-requests/2.28.2', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Length': '2803'}
2023-04-18 08:03:46,391 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2077] upload_file response body:
2023-04-18 08:03:46,394 ERROR   wandb-upload_25:192631 [internal_api.py:upload_file():2073] upload_file exception https://storage.googleapis.com/wandb-production.appspot.com/p4vv37/controlnet_restoration_v3/a0ybj77n/wandb-summary.json?Expires=1681884226&GoogleAccessId=wandb-production%40appspot.gserviceaccount.com&Signature=H4J1R%2Fbz8M2BwZtrpL7f7k3WR4%2BRHCB0rgdewUXbtCT4Fjz2CF3mUgMPtbySeMUc2mYgWoLcanevb8nt1SFq78516RQooEKAYLMW2IplB0xOdHbiX1PbobltPtdbnUShPOUE4vwU0RnR57DvVt%2B9jS5NDEMSwTwqNcXqT26SzasZ4YckEAOgw%2FaqLoIpcKXeaSSyayrcpByY%2FS4dQy726tgm0DlRvWWrthSAjgl%2FmCqit0RJTYunt5NQscn6p%2BNh2AHeKjp1BB03IzoFN7UPKRRp9SCYnZObojMgHb0Zyeoieq1hMT6AcyT%2FYH%2FxdnSRsHiZ3afdE0zhwcquSlNEPg%3D%3D: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2023-04-18 08:03:46,394 ERROR   wandb-upload_25:192631 [internal_api.py:upload_file():2075] upload_file request headers: {'User-Agent': 'python-requests/2.28.2', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Length': '2775'}
2023-04-18 08:03:46,394 ERROR   wandb-upload_25:192631 [internal_api.py:upload_file():2077] upload_file response body:
2023-04-18 08:03:46,760 INFO    wandb-upload_20:192631 [upload_job.py:push():138] Uploaded file /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/conda-environment.yaml
2023-04-18 08:03:47,361 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:47,361 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:47,576 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2073] upload_file exception https://storage.googleapis.com/wandb-production.appspot.com/p4vv37/controlnet_restoration_v3/a0ybj77n/config.yaml?Expires=1681884226&GoogleAccessId=wandb-production%40appspot.gserviceaccount.com&Signature=DeRRTWHFcQT8K%2BxYdtCYSOcNbRyZY%2FnY39EZxkeoPKMimvelLCIdWUiLBWuE21yElwv%2B72ynATaFUDmksI%2BlIIMHFOumsI2Tsga6Q8IKIR5TizHxitEhjj1Qb0IMHpwMinNCrqnSh4fqfsZZMI%2FH3TFPDyNt0KbkHmJTdp2uZZTY29r04mStDRhaUUPtMvqqaLROL51foeqYn6xdYlnt35G7rvJdQAAaAhtksuyX0PaAUuNDRCnZNeiK8ULJVGEIgVssG1LeelaArTvD36e2MgQkzV2njgeHJuYnZSc4Yvli%2BDz%2BHJ7hN8%2F%2BexL%2BkxDmC0COAtj5Yl4kAQr%2B6mTMSw%3D%3D: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2023-04-18 08:03:47,576 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2075] upload_file request headers: {'User-Agent': 'python-requests/2.28.2', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Length': '2803'}
2023-04-18 08:03:47,576 ERROR   wandb-upload_13:192631 [internal_api.py:upload_file():2077] upload_file response body:
2023-04-18 08:03:47,731 INFO    wandb-upload_27:192631 [upload_job.py:push():138] Uploaded file /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/output.log
2023-04-18 08:03:47,829 INFO    wandb-upload_25:192631 [upload_job.py:push():138] Uploaded file /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/wandb-summary.json
2023-04-18 08:03:47,878 INFO    wandb-upload_6:192631 [upload_job.py:push():138] Uploaded file /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/requirements.txt
2023-04-18 08:03:48,361 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:48,362 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:49,362 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:49,362 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:50,267 INFO    wandb-upload_13:192631 [upload_job.py:push():138] Uploaded file /media/linux_data/img/wandb/run-20230414_001226-a0ybj77n/files/config.yaml
2023-04-18 08:03:50,362 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:50,362 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:51,363 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:51,363 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:52,363 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:52,363 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:53,363 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:53,364 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:54,364 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:54,364 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:54,367 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: status_report
2023-04-18 08:03:55,364 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:55,365 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
2023-04-18 08:03:56,365 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:56,365 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
[...]
(loop of this:)
2023-04-18 08:03:57,365 DEBUG   HandlerThread:192631 [handler.py:handle_request():144] handle_request: poll_exit
2023-04-18 08:03:57,366 DEBUG   SenderThread:192631 [sender.py:send_request():363] send_request: poll_exit
[...]

WandB Internal User commented:
kptkin commented:
@Jibril-Frej Thanks for the detailed information. Looking at your logs it is indeed looks like we were stuck in the pooling exit state for around 8 minutes, but i'm still not clear why this is happening. I tried your script locally and it worked quickly for me. Will try to look into the code for a potential reason for this.
One question:  did you happen to try this script on other systems (i.e. not WSL) and if so did you experience the same lag?
I will keep you posted with my findings.

Hey @Jibril-Frej, I wanted to provide an update. We have a new Go based client that improves logging reliability. You can see more about it here: https://wandb.me/wandb-core. This update includes some stability improvements that might help with the run hangs issue you encountered. You can try it out by adding upgrading wandb and adding wandb.require("core") to your scripts.
Mind letting us know if this helps?


Search by player name?

Is it possible to search player by name (as it is possible in web app)?

You need to use resourceID

yeah, I've just realized that. Thanks


Add test

Deno has built in testing.
Add a simple test to make development easier.

Add very simple test in 4903bab69ae942255b47b7588cfdc60d92066854


now not available in translations

I have
This page has been generated on {{.Now.Format "2006-01-02"}}.
in my translations.
But .Now is deprecated:
ERROR 2017/07/18 07:34:25 Page's Now is deprecated and will be removed in Hugo 0.26. Use now (the template func).
But :
This page has been generated on {{now.Format "2006-01-02"}}.
is not working:
Error: Error building site: Failed to load translations in file "en.yaml": unable to parse translation #2 because template: This page has been generated on {{now.Format "2006-01-02"}}.
:1: function "now" not defined
map[id:footer-date translation:This page has been generated on {{now.Format "2006-01-02"}}.
]

This can be closed.


Remove Server::TestOptionsImpl class in favor of OptionsImpl

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
This PR is part of a multi-PR refactor to allow for use of the envoy test framework with binaries that wrap envoy with company specific code.  The goal of this set of PRs is to maximize the code shared between integration tests and binaries.
This particular PR changes envoy test code to use OptionsImpl and removes the test-specific Server::TestOptionsImpl class.  OptionsImpl is already pretty close to a struct-like grab bag, so there isn't much gained by having an extra class, and the Google production environment needs access on the binary invocation path to the implementation class in order to mutate it.
Future CLs will add setters to MainCommon{Base} to set the values required by the envoy integration test framework, and refactor BaseIntegrationTest to allow subclasses to create their own envoy servers based on configuration from the base class.
Risk Level: Low; just a test code refactor without behavior changes.
Testing: Ran all existing tests.
Docs Changes: None.
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

Arggh, please ignore this PR--I just changed my workstation and forgot to re-enable DCO.,


Use holes instead of option in value bindings

So this breaks typechecking. Which is interesting. Evidently we aren't inferring all of our holes eagerly enough...

I think its just that holes are not handled in unification at the moment. Check unify_type.rs, I think there just need to be a case handling Type::hole there (which returns a fresh type variable).

So there is try_match and do_zip_match in unify_type.rs. Which one would I be looking at?

I tried adding these cases in try_match:
            (&Type::Hole, &Type::Hole) => Ok(Some(subs.new_var())),
            (_, &Type::Hole) => Ok(Some(l.clone())),
            (&Type::Hole, _) => Ok(Some(r.clone())),

Didn't seem to work :/

That is what I was going to suggest... :( Though that shoud work

Woops - left the generated grammar.rs from my lalrpop experiments in there. Had to rebase.

Pretty sure the remaining errors is because after the call to merge_signature in typecheck.rs the resulting type is not assigned back to the type stored in the AST. So then later on unify is called on a Type::Hole and that does not have any handling of holes (nor should it). If you get what change is necessary then please implemeent it, otherwise I can send a PR to this branch :)

Yeah, I think send a PR or push directly to this branch.

Oh yeah, I can just push directly, forgot that!

Turns out I was on the wrong track with adding Type::Hole cases to unification. The correct way (I believe) is to eagerly instantiate ``Type::Hole` to ensure that holes never enter unification in the first place. I also needed to write the type back into the AST to ensure that the type after typechecking is correct.

I can handle merging master back into this branch if you like

Yeah. Go ahead.


InkCanvas not working in XAML Controls Gallery app

InkCanvas not working in XAML Controls Gallery app
Steps to reproduce the bug
Steps to reproduce the behavior:

Go to Open the XAML Controls Gallery app
Search for InkCanvas
Click with the mouse on the canvas and nothing happens

Expected behavior
Click with the mouse on the canvas and something will be drawn
Actual behavior
Click with the mouse on the canvas and nothing happens
Screenshots
Version Info

[ ] App downloaded from Store

If so, which version? <IP_ADDRESS>

Additional context
Windows 10 version:

[ ] Insider Build (xxxxx)
[x] 21H1  Update (19043)
[ ] November 2019 Update (18363)
[ ] May 2019 Update (18362)
[ ] October 2018 Update (17763)
[ ] April 2018 Update (17134)
[ ] Fall Creators Update (16299)
[ ] Creators Update (15063)
[ ] Anniversary Update (14393)

Device form factor:

[X ] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Windows 11 it's working

Still not working on Win10 version 2004 Build 19041. Checked out from master and freshly build with Win10 version 2004 Build 19041. It work with https://github.com/microsoft/Windows-universal-samples/tree/main/Samples/SimpleInk/cs . After some investigation I have the impression the InkPresenter is not listening to the Pointer events anymore. Anyone has a rough idea where to investigate further?

How strange! I'm able to draw:

I wonder if it might be related to some underlying driver issue or something. In any case, I don't think the issue is with the Gallery itself (as the sample is very simple - just an InkCanvas) so moving this to the WinUI repo for further investigation.


Remove Pragma header in ResponseCacheGatewayFilter

Is your feature request related to a problem? Please describe.
Continuing Cache related fixes, we've seen that both Cache-Control and Pragma headers are returned.
The ResponseCacheGatewayFilter (used for both Local and Global Cache features) currently ensures the Cache-Control header is returned which as per https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma replaces Pragma, making the later not necessary.
Furthermore Pragma is deprecated and Mozilla encourage to remove it.
Describe the solution you'd like
I am exploring creating a AfterCacheExchangeMutator that will run on every call to ensure the header is removed if present.
There are implementation details that I don't fully comprehend, so final solution may change.
Describe alternatives you've considered
No alternatives were considered.
Additional context
No.

Closed via #3489


pgsql-swoole driver can not prompt errors

app/Controller/TestController.php
    #[RequestMapping(path: "create", methods: "get")]
    public function create(ResponseInterface $response)
    {
        $s = \App\Model\Session::create([
            'id' => '131',
            'store_id' => 111,
            'uuid' => 'abc',
            'visitor_id' => '321',
            'user_id' => '0',
            'fingerprint' => '11111111111',
            'client_ip' => '<IP_ADDRESS>',
        ]);
        var_dump($s);
        return $response->raw('create session');
    }

pgsql 日志
2023-04-23 13:43:37.125 CST,"track","track",46662,"<IP_ADDRESS>:36156",6444c589.b646,7,"PARSE",2023-04-23 13:43:37 CST,3/48,0,LOG,00000,"duration: 1.488 ms  parse swoole_stmt_2: insert into ""sessions"" (""id"", ""store_id"", ""uuid"", ""visitor_id"", ""user_id"", ""fingerprint"", ""client_ip"", ""updated_at_gmt"", ""created_at_gmt"") values ($1, $2, $3, $4, $5, $6, $7, $8, $9)",,,,,,,,,"","client backend",,0
2023-04-23 13:43:37.127 CST,"track","track",46662,"<IP_ADDRESS>:36156",6444c589.b646,8,"BIND",2023-04-23 13:43:37 CST,3/49,0,LOG,00000,"duration: 0.839 ms  bind swoole_stmt_2: insert into ""sessions"" (""id"", ""store_id"", ""uuid"", ""visitor_id"", ""user_id"", ""fingerprint"", ""client_ip"", ""updated_at_gmt"", ""created_at_gmt"") values ($1, $2, $3, $4, $5, $6, $7, $8, $9)","parameters: $1 = '131', $2 = '111', $3 = 'abc', $4 = '321', $5 = '0', $6 = '11111111111', $7 = '<IP_ADDRESS>', $8 = '2023-04-23 05:43:37', $9 = '2023-04-23 05:43:37'",,,,,,,,"","client backend",,0
2023-04-23 13:43:37.127 CST,"track","track",46662,"<IP_ADDRESS>:36156",6444c589.b646,9,"INSERT",2023-04-23 13:43:37 CST,3/49,0,LOG,00000,"execute swoole_stmt_2: insert into ""sessions"" (""id"", ""store_id"", ""uuid"", ""visitor_id"", ""user_id"", ""fingerprint"", ""client_ip"", ""updated_at_gmt"", ""created_at_gmt"") values ($1, $2, $3, $4, $5, $6, $7, $8, $9)","parameters: $1 = '131', $2 = '111', $3 = 'abc', $4 = '321', $5 = '0', $6 = '11111111111', $7 = '<IP_ADDRESS>', $8 = '2023-04-23 05:43:37', $9 = '2023-04-23 05:43:37'",,,,,,,,"","client backend",,0
2023-04-23 13:43:37.128 CST,"track","track",46662,"<IP_ADDRESS>:36156",6444c589.b646,10,"INSERT",2023-04-23 13:43:37 CST,3/49,1052,ERROR,23505,"duplicate key value violates unique constraint ""sessions_pkey""","Key (store_id, uuid)=(111, abc) already exists.",,,,,"insert into ""sessions"" (""id"", ""store_id"", ""uuid"", ""visitor_id"", ""user_id"", ""fingerprint"", ""client_ip"", ""updated_at_gmt"", ""created_at_gmt"") values ($1, $2, $3, $4, $5, $6, $7, $8, $9)",,,"","client backend",,0

响应结果

问题
当我的数据库驱动使用 pgsql-swoole 并使用 model 去创建新的数据时，无论写入的 SQL 在数据库里是否发生了错误。 model 总能返回一个正确的对象给我，但 pgsql 里却没有对应的数据。

Any update on this?