MADLIB-1118. Change tolerance to 1e-2 (from 1e-6)

This changes the execution elapsed time to 2252 milliseconds from
10171 milliseconds on mac with Postgre 9.6

For future reference, this is how I reviewed the elastic_net install-check execution:

Update the following file:<local git repo>/src/ports/postgres/modules/elastic_net/test/elastic_net_install_check.sql_in

Added \timing to top of the file.
Added SELECT ASSERT (FALSE, 'Deliberately forced failure'); to the bottom of the file to force a failure condition. This will allowed me to review the timing information in the log files from the test execution.

From build directory run make install to push updated install-check file to installation directory
Run only the elastic_net test suite (using Postgres): `/usr/local/madlib/bin/madpack -s madlib -p postgres install-check -t elastic_net

I updated the elastic_net_train tolerance values with varying values and reran the repeated the scenario reviewing the recorded Time: values.

LGTM, since we anyway don't assert on relative_error on log_likelihood in elastic_net.

The change looks good.
Few comments:

An alternative to changing the threshold is to reduce the max number of iterations. Even with the lower threshold, we're not necessarily guaranteed quicker completion.
The log file can be accessed even with the test passing by adding -vl option to the madpack install-check command. The options indicate -v: Verbose and -l: Keep logs.
The install-check itself also provides the run time for execution of the whole file. However, \timing is needed if run time for individual queries is desired.

@njayaram2 Any idea why the asserts on log_likelihood are commented out?

@iyerr3 - Thanks for the review. Very much appreciated. Additionally, I should have reviewed the install-check options. Thanks for the info.

Jenkins please retest.

@iyerr3 Not sure why they are commented out.

Jenkins ok to test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/148/


Set client info on ruby provider startup

Addresses https://github.com/neovim/neovim-ruby/issues/60

Nice! Does this also set "basic" info for the non-host client? Or is the ruby client always a "host"? (The python client is not always in "host" mode, so in https://github.com/neovim/pynvim/pull/399 I changed it to send client info for that case as well.

You can manually attach a client in your own Ruby process, so I'll try to set different client info in that case.


[Promise] check the argc of builtin resolve/reject handler

Fix issue: #1996
JerryScript-DCO-1.0-Signed-off-by: Zidong Jiang<EMAIL_ADDRESS>

LGTM


Missed class after upgrade to Cloud SDK 5

Hello,
we want to upgrade to Cloud SDK 5 and also followed the steps described in this guide:
https://sap.github.io/cloud-sdk/docs/java/guides/5.0-upgrade-steps
But after that we get the error that the following class could not be found anymore:
com.sap.cloud.sdk.datamodel.odata.client.request.ODataRequestResultGeneric;

We use this class after reading an at designtime unknown OData service.
During runtime we use the class to get the result from the OData service.
Could you please advise how to replace this class?
We had also problem with this class after upgrade to version 4 of the cloud SDK.
So what can we do to avoid such problems in the future?
Best regards
André

Hello André,
This class and module stayed unchanged from v4 to v5.
There might be some leftover v4 dependencies. Please send us your dependency tree:
mvn dependency:tree

If you find Cloud SDK modules on version 4, please only define v5 on the sdk-bom and no other module.

Hello @CharlesDuboisSAP ,
the mentioned class in included in module  com.sap.cloud.sdk.datamodel:odata-client.
After adding the bom this module is not included anymore.
I can also not find this modul in our artifactory, there only version 4.9.0

Here is the dependency tree:
dependency_tree.txt
Regards
André

Hi André,
the module is present on maven central and should be mirrored by the Artifactory (latest once you try to download it from there).
And it is indeed present here.

Hi @MatKuhr ,
you are right it is working now, no idea why I got an dependency error before.
But no I needed to add the dependency for the odata-client manually in our pom which was before this included somewhere.
I did it and get now no syntax errors anymore.
We need to check now if the functionality works or also other dependencies are missing.
I close the issue for now.
Regards
André


Refactor useDatasetStore into hooks that use local load state, and a global cache outside the React lifecycle

This fixes a bug where resources were loaded multiple times, and prepares for more complex caching scenarios. It also makes it so the UI correctness is not dependent on the details of the cache.

ooo the performance gains on the storybook site are great :D :D
Are you thinking you'll try to do these TODOs for 20%? If not it may be worth talking this over with the next cohort

I'm planning on doing the caching/performance/data loading related ones. Not sure which specific ones you're referring to, let me know if there's any in particular you think I should make sure to do.

ooo the performance gains on the storybook site are great :D :D
Are you thinking you'll try to do these TODOs for 20%? If not it may be worth talking this over with the next cohort

I'm planning on doing the caching/performance/data loading related ones. Not sure which specific ones you're referring to, let me know if there's any in particular you think I should make sure to do.


mark docs_publish bringup true

Publishing docs on master is breaking because CI is downloading an ARM64 firebase binary on x64: https://github.com/flutter/flutter/issues/134319
Mark this bringup to unblock the tree over the weekend.

rslgtm. Does bringup simply ignore the failure or it skips the target entirely?

runs it but does not block the tree on the failures. these targets show up on the build dashboard on the far left side, as a square that is NOT filled in.

ok, gonna close this PR since a re-run passed https://ci.chromium.org/p/flutter/builders/prod/Linux docs_publish/11999? and I now consistently get an x64 binary when I curl https://firebase.tools/bin/linux/latest, so it seems this was a server bug that was fixed?


fix #712: allow filters on options expression of v-model

+1!

Updated and rebased -- Sorry about the slop! :/

Looking good - thanks!


Compiling bridge-app demo on Raspberry Pi 4b error

Compiling bridge-app demo on Raspberry Pi 4b error
System environment: Ubuntu 20.10
commit：e5fb65262951717adc964f880bdcdcfab471e780
The error is as follows:
Checking the environment:
20210323 11:18:06 INF Environment passes all checks!
Environment looks good, you are ready to go!
Done. Made 74 targets from 78 files in 449ms
ninja: Entering directory `out/debug'
[268/378] c++ obj/third_party/connectedhomeip/src/messaging/libMessagingLayer.ExchangeMgr.cpp.o
FAILED: obj/third_party/connectedhomeip/src/messaging/libMessagingLayer.ExchangeMgr.cpp.o
g++ -MMD -MF obj/third_party/connectedhomeip/src/messaging/libMessagingLayer.ExchangeMgr.cpp.o.d -Wconversion -O0 -g2 -fno-common -ffunction-sections -fdata-sections -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -Wall -Wextra -Wshadow -Wunreachable-code -Werror -Wno-deprecated-declarations -Wno-unknown-warning-option -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wno-cast-function-type -fdiagnostics-color -fno-strict-aliasing -D_REENTRANT -isystem../../third_party/connectedhomeip/third_party/ot-br-posix/repo/src -isystem../../third_party/connectedhomeip/third_party/ot-br-posix/repo/include -I/usr/include/dbus-1.0 -I/usr/lib/aarch64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -std=gnu++14 -fno-rtti -Wnon-virtual-dtor -DCHIP_HAVE_CONFIG_H=1 -DLWIP_IPV4=1 -DLWIP_IPV6=1 -DLWIP_API=1 -DLWIP_ETHERNET=1 -DLWIP_SLIP=0 -DLWIP_6LOWPAN=1 -DLWIP_PPP=1 -I../../third_party/connectedhomeip/src/include -I../../third_party/connectedhomeip/src -Igen/include -I../../third_party/connectedhomeip/src/lib -I../../third_party/connectedhomeip/config/standalone -I../../third_party/connectedhomeip/third_party/nlassert/repo/include -I../../third_party/connectedhomeip/third_party/nlio/repo/include -I../../third_party/connectedhomeip/src/lwip/standalone -I../../third_party/connectedhomeip/third_party/lwip/repo/lwip/src/include -I../../third_party/connectedhomeip/src/lwip/include -I../../third_party/connectedhomeip/src/setup_payload -Igen -Igen -I../../third_party/connectedhomeip/third_party/inipp/repo/inipp -c ../../third_party/connectedhomeip/src/messaging/ExchangeMgr.cpp -o obj/third_party/connectedhomeip/src/messaging/libMessagingLayer.ExchangeMgr.cpp.o
../../third_party/connectedhomeip/src/messaging/ExchangeMgr.cpp: In member function ‘CHIP_ERROR chip::Messaging::ExchangeManager::Init(chip::NodeId, chip::TransportMgrBase*, chip::SecureSessionMgr*)’:
../../third_party/connectedhomeip/src/messaging/ExchangeMgr.cpp:83:51: error: ‘void* memset(void*, int, size_t)’ clearing an object of non-trivial type ‘struct chip::Messaging::ExchangeManager::UnsolicitedMessageHandler’; use assignment or value-initialization instead [-Werror=class-memaccess]
83 |     memset(UMHandlerPool, 0, sizeof(UMHandlerPool));
|                                                   ^
In file included from ../../third_party/connectedhomeip/src/messaging/ExchangeMgr.cpp:39:
../../third_party/connectedhomeip/src/messaging/ExchangeMgr.h:232:12: note: ‘struct chip::Messaging::ExchangeManager::UnsolicitedMessageHandler’ declared here
232 |     struct UnsolicitedMessageHandler
|            ^~~~~~~~~~~~~~~~~~~~~~~~~
At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-unknown-warning-option’ may have been intended to silence earlier diagnostics
cc1plus: all warnings being treated as errors
[273/378] c++ obj/third_party/connectedhomeip/src/messaging/libMessagingLayer.Channel.cpp.o
ninja: build stopped: subcommand failed.


Docker Trojan Horse in Redis Container

Info:

Docker version ($ docker --version):
Laradock commit ($ git rev-parse HEAD):
System info (Mac, PC, Linux):
System info disto/version:

Issue:
I recently found that after a rebuild, the redis container would shut down after exactly 24 hr. After looking through the log, I found that after 24hr, redis would run the following command:
redis_1                | sh: 1: killall: not found
redis_1                | ./xmrig-notls: unrecognized option '--max-cpu-usage'

Expected behavior:
Expected it to work

Reproduce:
That's the tricky part. I didn't have this kind of issue until last week. Maybe the horse is from official docker redis container (possibly not) or maybe an intrusion into my system, but I only found xmrig under overlay2:
/var/lib/docker/overlay2/f0d664c7954a158354876e11b8c89bd3c323d49ddc59c5531750b5ac639f9c6e/merged/tmp/xmrig-2.99.0-beta/xmrig
/var/lib/docker/overlay2/f0d664c7954a158354876e11b8c89bd3c323d49ddc59c5531750b5ac639f9c6e/diff/tmp/xmrig-2.99.0-beta/xmrig
So it's more likely a container problem.

Relevant Code:
// place a code sample here

@zimo-xiao This happened because you didn't secure your Redis container (even though you think you did!) I know because this exact situation happened to me before :o)
If your docker-compose.yml file contains this redis configuration:
services:
  redis:
    ..
    ports:
      - 6379:6379

.. then Docker will override your iptables.  This doesn't show in ufw status because it wasn't configured there.
This situation is explained in more detail here.
The solution is to change 6379:6379 to <IP_ADDRESS>:6379:6379, and create a secure password for Redis.

Additionally, Laradock doesn't have an env option for setting the redis password, so you will need to   run sed on the redis.conf file.
In .env:
REDIS_PASSWORD=supersecret

In ./laradock/redis/redis.conf:
requirepass __REDIS_PASSWORD__

In ./laradock/redis/Dockerfile
FROM redis:latest

ARG REDIS_PASSWORD=secret

RUN mkdir -p /usr/local/etc/redis
COPY redis.conf /usr/local/etc/redis/redis.conf
RUN sed -i "s/__REDIS_PASSWORD__/${REDIS_PASSWORD}/g" /usr/local/etc/redis/redis.conf

VOLUME /data

EXPOSE 6379

CMD ["redis-server", "/usr/local/etc/redis/redis.conf"]

Darn cryptojackers.

I'm having the same issue, after trying to set a password, laravel won't connect to redis no matter what, is there any step missing from what is mentioned above?

@javierrivarola Couple of things to check:

Are you able to connect to Redis via redis-cli, type auth, enter password, and run ping?

$ docker-compose exec redis redis-cli
<IP_ADDRESS>:6379> auth {{your_password}}
<IP_ADDRESS>:6379> ping
pong

Check that you have set your REDIS_PASSWORD in the .env file used by Laravel.

Check config/database.php and make sure that the default redis driver includes a password field that pulls from env('REDIS_PASSWORD', null).

Failing that, it could be a build-cache issue, where you've set the files but it hasn't updated in the container.
$ docker-compose down && docker-compose up -d --build

Yes i can auth from the redis-cli but no matter what i do, laravel gets "Connection refused [tcp://redis:6379]", already tried to re build workspace container but nothing

I also get that error message when starting my containers for the first time for about 10-30 seconds while Redis is getting started.
After all containers are running, check to see if this works:
$ docker-compose exec workspace bash
$ art tinker
> cache(['foo' => 'bar'], 10);
> cache('foo')

Laravel just won't connect

my .env

Can you post the redis service from your docker-compose.yml file?

and this is my laradock .env

Thanks @javierrivarola, I've updated my answer above to include adding REDIS_PASSWORD as a build argument, which was missing in your service.

i'm not seeing any edited answer about adding REDIS_PASSWORD in ./laradock/docker-compose.yml, can you clarify?

do i need to rebuild everything? still not working

Yep, need to rebuild so that the argument gets used.  You can run docker-compose down then docker-compose up -d --build to trigger a build with only new changes.

The same issue after rebuilding everything :S

We got this :)
Can you post ./laradock/redis/Dockerfile?

Thanks for your patience and efforts to help me! this is really driving me nuts

No worries, just one last sanity check - do you have __REDIS_PASSWORD__ in redis.conf?

yes! if i login into the container i can auth to redis

Ok, so the password is definetely being set :+1:
Are your workspace/php-fpm instances connected to the backend network?

yeah, if i remove the password everything works

Shout out to @cwilby who helped me resolve this issue!! He is the real MVP guys!
The last step missing for me was removing the bind directive in redis.conf file, and everything worked!

Hi
I want to add up one reason behind "Connection refused to Redis server" is your Laravel app may still caching .env configuration file so it is good to remove all config cache by running php artisan cache:clear and php artisan config:clear to reflect new .env file with REDIS_PASSWORD set :)

When experiencing strange issues with Laravel it is always a good idea to consider clearing caches, especially for config and views.

Should probably put this somewhere else, but here's my modification of workspace/docker-entrypoint.sh that helps me avoid cache during dev.
#!/bin/bash
set -e

while ! mysqladmin ping -h"${DB_HOST}" -u"root" -p"${ROOT_PASSWORD}" --silent; do
  sleep 1
done

pushd /var/www
  if [ "${APP_ENV}" = "production" ]; then
    sed -i 's|APP_DEBUG=true|APP_DEBUG=false|g' /var/www/.env
    composer install --no-plugins --no-scripts --no-dev
  else
    composer install --no-plugins --no-scripts
  fi

  [ -z "${APP_KEY}" ] && php artisan key:generate --force
  [ -z "${JWT_SECRET}" ] && php artisan jwt:secret --force

  php artisan migrate --force
  php artisan db:seed --force

  if [ "${APP_ENV}" = "production" ]; then
    php artisan clear-compiled
    php artisan cache:clear
    php artisan config:clear
    php artisan clockwork:clean
    php artisan event:clear
    php artisan optimize:clear
    php artisan route:clear
    php artisan view:clear

    php artisan config:cache
    php artisan event:cache
    php artisan route:cache
    php artisan view:cache
  fi

popd

/sbin/my_init

@cwilby That is really helpful, thanks alot! :+1:

Shout out to @cwilby who helped me resolve this issue!! He is the real MVP guys!
The last step missing for me was removing the bind directive in redis.conf file, and everything worked!

This step should be added in the documentation.

bind

can you detailed the solution ?

@dabarto
In redis.conf comment out line 69:
# bind <IP_ADDRESS>

bind <IP_ADDRESS>

after i comment the bind <IP_ADDRESS>
please help

@dabarto make sure:

[x] .env has REDIS_PASSWORD
[ ] ./laradock/redis/redis.conf has lines bind <IP_ADDRESS> and requirepass __REDIS_PASSWORD
[ ] ./laradock/redis/Dockerfile has ARG REDIS_PASSWORD and sed invocation
[ ] docker-compose.yml has REDIS_PASSWORD build args

in docker-compose you can bind redis to localhost so it can't get accessed from outside
ports:
    - "<IP_ADDRESS>:27017:27017"


Correcting gradient accumulation in the training section

Putting the forward pass within the no_sync() context along with the backward pass; otherwise gradients will still be synchronized. For details, check this from the PyTorch repo: https://github.com/pytorch/pytorch/blob/main/torch/nn/parallel/distributed.py#L1427

this might be slightly slower due to moving next_batch after the backward. not sure will have to check

You're right. I have check that. Just putting that back before the backward.


fix NPE when use ctas to create table

Proposed changes
This is caused by expr in  orderbyelements is not analyzed.
Problem summary
Describe your changes.
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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.96 seconds
stream load tsv:          445 seconds loaded<PHONE_NUMBER>9 Bytes, about 160 MB/s
stream load json:         24 seconds loaded<PHONE_NUMBER> Bytes, about 93 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230424063623_clickbench_pr_133826.html


Fixed return type for functions in kubevirt_test_utils.go

Signed-off-by: Pratik Shah<EMAIL_ADDRESS>
What this PR does / why we need it:
Functions GetMockKubevirtClientFromClientConfig and GetInvalidKubevirtClientFromClientConfig has return type KubevirtClient but return variable has type MockKubevirtClient. This fails with latest k8s.io versions.
In this PR, we have fixed return type of above mentioned functions. This enables compiling kubevirt/client-go library with latest versions of k8s.io.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test all

/ok-to-test

@shahpratikr looks like you are going to have to do something about calls to kubecli.MockKubevirtClientInstance.EXPECT().

@shahpratikr looks like you are going to have to do something about calls to kubecli.MockKubevirtClientInstance.EXPECT().

any suggestions? looks like we cannot directly implement or modify this function with KubevirtClient struct

@shahpratikr looks like you are going to have to do something about calls to kubecli.MockKubevirtClientInstance.EXPECT().

@mhenriks any suggestions? looks like we cannot directly implement or modify this function with KubevirtClient struct

Off the top of my head, maybe you can add a function to kubecli package that casts MockKubevirtClientInstance to *MockKubevirtClient calls EXPECT and returns the result?


0744 -  Find Smallest Letter Greater Than Target

Description of the Problem
Find Smallest Letter Greater Than Target
Code
Given a list of sorted characters letters containing only lowercase letters, and given a target letter target, find the smallest element in the list that is larger than the given target.
Letters also wrap around. For example, if the target is target = 'z' and letters = ['a', 'b'], the answer is 'a'.
Examples:
Input:
letters = ["c", "f", "j"]
target = "a"
Output: "c"
Input:
letters = ["c", "f", "j"]
target = "c"
Output: "f"
Code

## Link To The LeetCode Problem
https://leetcode.com/problems/find-smallest-letter-greater-than-target/

Please assign me this issue

@jindalsachin
Waiting for your PR 😸


any ideas how to fix ?

i have a linking system with a booster id role heres the code
function boosterKeys():
set {_role} to guild boost role of guild with id "Booster role"
make embed:
set embed color of embed to red
set title of embed to "BOOSTER REWARDS"
set footer of embed to "Happens every 2 days"
set description of embed to "You have been rewarded with a GEAR and 2 CASINO KEYS!%nl%%nl%Claim your keys in-game using the command:%nl%| /claimbooster |"
post last embed to text channel with id "booster channel"
post mention tag of {_role} to text channel with id "mentions the booster role"
loop indexes of {linkedGeneral::}:
set {_m} to member with id loop-value from guild with id "server id"
if {_m} is a member:
if {_m} has discord role {_role}:
execute console command "lp user %{_linkedGeneral::%loop-value%::}% parent addtemp booster 2d"
Heres the error from console when i do /link in the discord it checks if am boosting the server but it doesn't execute the command i get this error
19:50:00 INFO: [!] DiSky Internal Error (version: 4.12.1)
19:50:00 INFO: [!] Error type: ErrorResponseException
19:50:00 INFO: [!]
19:50:00 INFO: [!] 10062: Unknown interaction
19:50:00 INFO: [!]
19:50:00 INFO: [!] Full Stacktrace:
19:50:00 INFO: [!]
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.api.exceptions.ErrorResponseException.create(ErrorResponseException.java:185)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.api.requests.Request.onFailure(Request.java:143)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.RestActionImpl.handleResponse(RestActionImpl.java:281)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.restaction.interactions.InteractionCallbackImpl.handleResponse(InteractionCallbackImpl.java:109)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.api.requests.Request.handleResponse(Request.java:288)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester$WorkTask.handleResponse(Requester.java:414)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester$WorkTask.access$300(Requester.java:350)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester.execute(Requester.java:233)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester.execute(Requester.java:145)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester.execute(Requester.java:128)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.internal.requests.Requester$WorkTask.execute(Requester.java:378)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.api.requests.SequentialRestRateLimiter$Bucket.execute(SequentialRestRateLimiter.java:446)
19:50:00 INFO: [!] DiSky 4.12.1.jar//net.dv8tion.jda.api.requests.SequentialRestRateLimiter$Bucket.run(SequentialRestRateLimiter.java:490)
19:50:00 INFO: [!] java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
19:50:00 INFO: [!] java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
19:50:00 INFO: [!] java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
19:50:00 INFO: [!] java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
19:50:00 INFO: [!] java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
19:50:00 INFO: [!] java.base/java.lang.Thread.run(Thread.java:840)
19:50:00 INFO: [!]
19:50:00 INFO: [!] READ THE ERROR CAREFULLY, and if you are sure about it,
19:50:00 INFO: [!] you can report the error with the whole stacktrace on the GitHub repository:
19:50:00 INFO: [!] https://github.com/DiSkyOrg/DiSky/issues/new
19:50:00 INFO: [!]
19:50:00 INFO: [!]

it sends the error even if the player doesn't have the role

Is this still happening? Does the error occur every time you're executing the command?
How do you handle the command registration? (global or guild)


TBRM YAML test scripts

Add yaml test script for TBRM
This PR relies on Karsten's PR which should be merged first.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This looks good, but please have a look at and resolve the test failures.

These scripts were all included in #34864, closing stale PR.


IP Assignment for new VM (VM to VM ASR within Azure)

Hello,
I guess the highlighted section needs to be updated/re worded.

When performing a Test Failover,  when the Target Network chosen is NOT the same as previously configured failover VNet, article says:
-Target IP address will be static with the same IP address.
-If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.
But,if the Target Network has range <IP_ADDRESS>/16 and the source VM had IP of <IP_ADDRESS> ,I dont think the new target VM would still get <IP_ADDRESS>. Maybe it gets the LAST free address in <IP_ADDRESS>/16?
Perhaps the paragraph should read(and add the above example)
-Target IP address will be static with the same IP address, if possible to belong to the target vnet IP addressing.
-If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.
==================================
Moving to a second query,
I think we need the highlighted line between the 2 sections:

Regards,
Aditya Garg

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

ID: dbc136fa-e90c-108a-fada-68e8621e6b3e
Version Independent ID: 605b1a94-8bef-f7f3-5eaa-ec8b5bb8fc4a
Content: Map virtual networks between two regions in Azure Site Recovery - Azure Site Recovery
Content Source: articles/site-recovery/azure-to-azure-network-mapping.md
Service: site-recovery
GitHub Login: @v-pgaddala
Microsoft Alias: v-pgaddala

@adi-garg  Thanks for the feedback! We are currently investigating and will update you shortly.

@v-pgaddala Please review and take appropriate action.

@adi-garg
The updates are done, and the info is live.

#please-close


gh-113 adding bm25 and hybrid argument builders

Hi @shreyanshshah27,
thank you for your second contribution :)
I only noticed this PR after releasing a new version, but it will be in the next one!


[Bug] Reference. setCheck (false) and consumer:Check: False is set to false, but when the project starts, it still prompts for connection failure

Pre-check

[X] I am sure that all the content I provide is in English.

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
dubbo.version 3.2.10
spring-boot.version 2.7.10
jdk: 21

Steps to reproduce this issue
null
What you expected to happen
null
Anything else
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The check happens after the connection to the provider is established and invoker is generated, depending on your Boolean value. As you can see from the screenshot in the Dingtalk group, your exception is due to the connection to the provider.

You can do consumer development first as I said with mock.


Fix prompts not opening page in edit mode when used in sucession

The following changes are implemented
TODO: Summary
Changes in the user interface:
TODO: Add screenshots, recordings or remove this section
Checklist when submitting a final (!draft) PR

[ ] Commits are tidied up, squashed if needed and follow guidelines in CONTRIBUTING.md
[ ] Code builds
[ ] All existing tests pass
[ ] All new critical code is covered by tests
[ ] PR is linked to the relevant issue(s)
[ ] Rebased with the target branch

Wf is executed correctly. Just a small thingy when saving the record


Searching your name in the /nameusage gettop gives wrong results

If you click the "Find my name" button and submit a name, it sends you to a page that is likely 2x the page you wanna be on.
page 3 -> 6
page 5 -> 10 (yeah..)
page 10 -> 20 (ok that's certain now)
It also doesn't store the new page into the message, so when you press next/previous, it will use the page number that it had before searching the name.

4 -> 7 (?)
5 -> 9 (?)
So left column returns odd numbers, and right column returns even numbers. (I might need the ceil(of the column number+1))
It also seems I forgot to set the value of the modal back from 'failure' to 'success' so it never overwrote the page number.

Fixed in v<IP_ADDRESS>


Support for introducing custom tags to gRPC/HTTP metrics

Consider the example of a server that serves results either from database or a cache. One important dimension you might want to capture as part of all your HTTP/gRPC metrics is whether a particular request was served from cache or not.
Currently it isn't possible to augment the set of tags applied to the stats.Record call made by ocgrpc or ochttp. In OpenCensus Java I believe it is possible to accomplish this by changing the thread-local tags in the thread processing of the request but in Go, Context is immutable so a similar approach is not possible.

I don't understand how the context immutability is an issue, you can pass along a context with your own set of keys (for example you can make your own handler which wraps ochttp.Handler and passes along a context to it),
still though it isn't possible (yet?) to pass mutators for to the relevant handler.

Consider the caching example above. You only know the correct value of the "was_cached" tag after the request has finished processing. How do you pass this up from inside your HandlerFunc to the ochttp.Handler that wraps it?

could the oc handler take a custom finalizer callback as an option?

Another use of this would be for HTTP responses that are logically errors but that return a 200 OK code for compatibility reasons. It would be interesting for the user to be able to add an "error" tag which could be used to break out errors, otherwise they would have no way to tell error responses from OK responses.

I like the functions that Go-Kit provides that enable you to instrument the HTTP handler.
// RequestFunc may take information from an HTTP request and put it into a
// request context. In Servers, RequestFuncs are executed prior to invoking the
// endpoint. In Clients, RequestFuncs are executed after creating the request
// but prior to invoking the HTTP client.
type RequestFunc func(context.Context, *http.Request) context.Context

// ServerFinalizerFunc can be used to perform work at the end of an HTTP
// request, after the response has been written to the client. The principal
// intended use is for request logging. In addition to the response code
// provided in the function signature, additional response parameters are
// provided in the context under keys with the ContextKeyResponse prefix.
type ServerFinalizerFunc func(ctx context.Context, code int, r *http.Request)

so the request func can be use to Populate a context which is then used in the finalizer.

So you would install something internally mutable (like a pointer to a struct) into the context in RequestFunc, mutate it in your handler/endpoint and then read it back in ServerFinalizerFunc?

"was_cached" is a dimension you want to collect at the handler that does caching or not, not at the client.

This is again a cross-language proposal and needs to be discussed at the specs repo.


Example Fails with EnglishV3Slim PaddleOCR Model

@sdcb I tried with this code:
FullOcrModel model = await OnlineFullModels.EnglishV3Slim.DownloadAsync();

and it always raises this exception:
Sdcb.OpenVINO.OpenVINOException
  HResult=0x80131500
  Message=general error(-1) in file "C:\Users\ZhouJie\source\repos\OpenVINO.NET\src\Sdcb.OpenVINO\OVCore.cs" member "ReadModel" at line 210 when calling "ov_core_read_model_unicode((ov_core*)Handle, modelPathPtr, binPathPtr, &model)"
  Source=Sdcb.OpenVINO
  StackTrace:
   at Sdcb.OpenVINO.OpenVINOException.ThrowIfFailed(ov_status_e e, String message, String callerMemberName, String callerExpression, String callerFilePath, Nullable`1 callerLineNumber) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\src\Sdcb.OpenVINO\OpenVINOException.cs:line 51
   at Sdcb.OpenVINO.OVCore.ReadModel(String modelPath, String binPath) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\src\Sdcb.OpenVINO\OVCore.cs:line 210
   at Sdcb.OpenVINO.PaddleOCR.PaddleOVCoreExtensions.ReadDirectoryPaddleModel(OVCore core, String directoryPath, String modelFileName) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\projects\PaddleOCR\Sdcb.OpenVINO.PaddleOCR\PaddleOVCoreExtensions.cs:line 22
   at Sdcb.OpenVINO.PaddleOCR.Models.Details.FileDetectionModel.CreateOVModel(OVCore core) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\projects\PaddleOCR\Sdcb.OpenVINO.PaddleOCR\Models\Details\FileDetectionModel.cs:line 30
   at Sdcb.OpenVINO.BaseModel.CreateCompiledModel(DeviceOptions options, Action`1 afterReadModel, Action`2 prePostProcessing, Action`1 afterBuildModel, Action`1 afterCompiledModel) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\src\Sdcb.OpenVINO\BaseModel.cs:line 46
   at Sdcb.OpenVINO.PaddleOCR.PaddleOcrDetector..ctor(DetectionModel model, DeviceOptions options, Nullable`1 staticShapeSize) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\projects\PaddleOCR\Sdcb.OpenVINO.PaddleOCR\PaddleOcrDetector.cs:line 79
   at Sdcb.OpenVINO.PaddleOCR.PaddleOcrAll..ctor(FullOcrModel model, PaddleOcrOptions options) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\projects\PaddleOCR\Sdcb.OpenVINO.PaddleOCR\PaddleOcrAll.cs:line 54
   at Sdcb.OpenVINO.PaddleOCR.PaddleOcrAll..ctor(FullOcrModel model, DeviceOptions device) in C:\Users\ZhouJie\source\repos\OpenVINO.NET\projects\PaddleOCR\Sdcb.OpenVINO.PaddleOCR\PaddleOcrAll.cs:line 45
   at Program.<<Main>$>d__0.MoveNext() in C:\Users\WolfgangRichter\Development\Experiments\Experiments\mini-openvino-paddleocr\mini-openvino-paddleocr\Program.cs:line 13
   at Program.<Main>(String[] args)

I did notice in my cache it properly downloaded the V3 slim model.

It seems have some problem with EnglishV3Slim, can you try with EnglishV3 or EnglishV4 instead?

@sdcb I also saw it have a problem with ChineseV3Slim.  Both Slim models.
I got it working with EnglishV3 and also EnglishV4.
But they use more RAM than I am allowed.
I was really hoping to test with slim models and see if they use much less RAM :-)

I believe it's an issue that upstream openvino does not supports slim models.

Should we make a C++ program to see the error in more detail?  I am trying to understand the exact error, to know if it's fixable or not.

@sdcb do any of your other projects support Paddle slim models?  I am trying to cut down memory usage.
@sdcb I think OpenVino doesn't support some operators used by the slim Paddle models.
Here's what I got from Python:
>>> import openvino as ov
>>> core = ov.Core()
>>> device = 'AUTO'
>>> det_model_file_path = r"C:\Users\WolfgangRichter\AppData\Roaming\paddleocr-models\en_PP-OCRv3_det_slim\inference.pdmodel"
>>> det_model = core.read_model(model=det_model_file_path)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\WolfgangRichter\Development\venvs\vinopaddletest\lib\site-packages\openvino\runtime\ie_api.py", line 507, in read_model
    return Model(super().read_model(model))
RuntimeError: Exception from src\inference\src\core.cpp:99:
Check 'creator_it != CREATORS_MAP.end()' failed at src\frontends\paddle\src\frontend.cpp:55:
FrontEnd API failed with OpConversionFailure:
No creator found for fake_quantize_dequantize_moving_average_abs_max node

Oh, Wow, thanks for you to check this deeply detailed, can you try create a ticket in openvino? I believe paddlepaddle have some cooperation with OpenVINO project, OpenVINO.NET is just a C API wrapper of OpenVINO.

I wants to highlight that in coming 2023.2 version, OpenVINO supports provide detailed error information in C API according to my this issue:

https://github.com/openvinotoolkit/openvino/issues/20536

I already added support in coming release.

@sdcb your work is really nice, and I care a lot about getting low RAM OCR :-p so I am investigating all angles!

Can you try lower the inference thread count, that should able to getting lower RAM, like this:
using PaddleOcrAll all = new(model, new PaddleOcrOptions(new DeviceOptions("CPU")
{
	InferenceNumThreads = 1, // This should able to lower the RAM usage but also slower
	//NumStreams = 1,
})
{
})
{
	Enable180Classification = true,
	AllowRotateDetection = true,
};

@sdcb not a huge difference for me, still 500-600 MB used, and I'd like it to be 250-300 MB of RAM.
Thanks though!  I'm very curious how much RAM the slim models would take, and how to get them running in C#.

Hi @theonewolf , I upgraded into 2023.2, now OpenVINO.NET supports reflects errors from OpenVINO C API, in this case, it shows following error:
general error(-1) Exception from src\inference\src\core.cpp:94:
Check 'creator_it != CREATORS_MAP.end()' failed at src\frontends\paddle\src\frontend.cpp:55:
FrontEnd API failed with OpConversionFailure:
No creator found for fake_quantize_dequantize_moving_average_abs_max node.

 in file "C:\Users\sdfly\source\repos\OpenVINO.NET\src\Sdcb.OpenVINO\OVCore.cs" member "ReadModel" at line 213 when calling "ov_core_read_model_unicode((ov_core*)Handle, modelPathPtr, binPathPtr, &model)

Stack trace:
   at Sdcb.OpenVINO.OpenVINOException.ThrowIfFailed(ov_status_e e, String message, String callerMemberName, String callerExpression, String callerFilePath, Nullable`1 callerLineNumber)
   at Sdcb.OpenVINO.OVCore.ReadModel(String modelPath, String binPath)
   at Sdcb.OpenVINO.PaddleOCR.PaddleOVCoreExtensions.ReadDirectoryPaddleModel(OVCore core, String directoryPath, String modelFileName)
   at Sdcb.OpenVINO.PaddleOCR.Models.Details.FileDetectionModel.CreateOVModel(OVCore core)
   at Sdcb.OpenVINO.BaseModel.CreateCompiledModel(DeviceOptions options, Action`1 afterReadModel, Action`2 prePostProcessing, Action`1 afterBuildModel, Action`1 afterCompiledModel)
   at Sdcb.OpenVINO.PaddleOCR.PaddleOcrDetector..ctor(DetectionModel model, DeviceOptions options, Nullable`1 staticShapeSize)
   at Sdcb.OpenVINO.PaddleOCR.PaddleOcrAll..ctor(FullOcrModel model, PaddleOcrOptions options)
   at UserQuery.Main(), line 15

Now C# API also let you know it's caused by fake_quantize_dequantize_moving_average_abs_max now.


FLUME-3243 hdfs.callTimeout deafault increased and deprecated

The default hdfs.callTimeout used by the HDFS sink was too low only 10 seconds that can cause problems on a busy system.
The new default is 30 sec.
I think this parameter should be deprecated and some new more error tolerant solution should be used. To enable the future change I indicated this in the code and in the Users Guide.
Tested only with the unit tests.

Thanks @turcsanyip. I have no idea, how I could miss that.


Build and packaging updates

(This time from the right source repo :-))

Update to the latest Serilog org Build.ps1 and appveyor.yml (incl. finds tests in tests/)
Fresh NuGet.org publishing key
Use <VersionPrefix> so that dev packages can be built
Run tests on currently-supported .NET/core versions

This should get dev happy, which will enable other updates/fixes to be re-targeted to dev, and then published via Serilog.Sinks.ApplicationInsights-dev-* NuGet packages. We should make dev the default branch, so that incoming PRs don't land straight on master.

(dev is now back up-to-date with master BTW! :-))

Wow time flies! Didn't notice that 12 days have zipped by. I'll push ahead and get things "green"; it looks like some updates are needed to keep this usable with AI - seems like we should either move ahead or consider archiving this repo.
I'll take the leap, and try to get obvious maintenance PRs merged to a dev version, but jump in anytime @serilog/reviewers-application-insights if I'm off course :-)


Compatibility with preact-cli?

Hello! Great work with the library, I love it! It's beautiful.
However, I'm trying to use it with preact-cli, but it's giving me this error:
Module build failed: Error: composition is only allowed when selector is single :local class name not in ".raised", ".raised" is weird
After some research, I've realized that this error has something to do with webpack, but I'm not able to fix it. I tried hacking together some of the solutions in #1278 and #1359, but none work.
The steps to reproduce are:

preact create example-app
yarn add react-toolbox
Add import { Button } from 'react-toolbox/lib/button'; to the file, and try to use the component in render().

I'd appreciate if someone gave me some directions to fix this, as I'm interested in using the library. Let me know if you need more info!

Hey @Pablo-Merino,
I am also using Preact on top of my React.
If you look here: https://github.com/developit/preact-compat
Preact actually gives you an option to use react based libraries for preact. I dont know if this helps you but check it out. If it does, then great!

See this note for using it with Create React App https://github.com/react-toolbox/react-toolbox#basic-usage

Hi @Pablo-Merino,
to use Preact CLI with react-toolbox you'd have to create preact.config.js and configure it as follows:
import path from 'path'

const reactToolboxPath = path.resolve('./node_modules', 'react-toolbox')

export default (config, env, helpers) => {
  const rules = helpers.getLoadersByName(config, 'postcss-loader')
  const cssModulesRule = rules[0].rule
  cssModulesRule.include.push(reactToolboxPath) // this enables css modules for react-toolbox
  const globalCssRule = rules[1].rule
  globalCssRule.exclude.push(reactToolboxPath) // exclude react-toolbox from global css
}

See readme for further info. If you encounter any problem feel free to open an issue at Preact CLI

@rkostrzewski This seems to work!
Maybe you should add this example to the Config Recipes.
Thanks a lot anyway :-)

Yep! @rkostrzewski's snippet works just fine! Thanks! I'm closing this issue.

I'm unable to get color functions (color(#000 a(25%))) to work using the base config, which leaves the components half-styled :-/
Has anyone solved that last problem? @Pablo-Merino could you re-open the issue?

Ok, my bad, I didn't follow the latest install instructions from react-toolbox. I needed to
npm install --save-dev postcss-loader postcss-cssnext
and add a postcss.config.css file at the root of my project:
module.exports = {
	plugins: {
		'postcss-cssnext': {},
	},
};

Now it seems everything works fine :-)


make it easier to spot and select invite code

currently the user has to scroll back through a bunch of cryptosoup to find the invite url, e.g.
..............................................ready!
invite code: https://www.uproxy.org/invite/ewogICJuZXR3
kNsb3VkIiwKICAibmV0d29ya0RhdGEiOiJZVVoMVIwdGFjWE56YWxFd1
ptTlVkbTR3TlFwbFlUTjBkbmRHTUVSeGVuSlRWemR3YVdOQ2VtTkNR
VzVaZG1KTmNrNTFWbmxKVUZvMkx6ZDNXRTEzWVVSb0x6WnFTalp
VVjBSTFZIZ3lTRTkwYVhkbkNsZFZaRFJVZVZGVFNWcDRZVkZrY1ZK
Q1UyMWlVMUl6VVd4TGRVeHZRbGRuZUdONU5XNUpjM2xQYlZvclZY
Wk9SbWh3YkZWWFRsSkhUbTlrYzJaUVpXY0tVREJMVTBST1YxQkxV
...

This change attempts to make it easier to spot and select the invite.
Might even be worth printing the URL in green or something, if that would still work with PuTTY?

Cool, thanks for this. Agree it makes the URL easier to identify. I do plan to dramatically reduce the amount of output from the various scripts so let's hold off on colour coding for now which might make the install code trickier to write.
:+1:


DBT Power User no python interpreter installed

Expected behavior
I have installed python and have been using the extension for a while but recently I get an error saying python interpreter not installed. This blocks me from running dbt commands via the extension when previously this worked fine. Lineage however still works.
Actual behavior
Whenever I try to run any build or other commands dbt power user is not able to find my existing python interpreter
Steps To Reproduce
Open vs code and open a dbt sql file and run the build command.
Log output/Screenshots

Operating System
Windows
dbt version
1.7
dbt Adapter
1.7
dbt Power User version
0.27
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Hi Apologies for the slow reply. I was able to get it working again but required me to setup a venv instead

No problem. I'm trying to determine what may have caused the issue. Do you happen to use conda?


Add an options table so we can choose to return a default

@kyazdani42 this PR changes the way we handle the default icon, it adds in a 3rd optional argument to get_icon which are options. For now the only option is default = boolean if true then the get icon will return the default icon if none if found. This way a user can still opt not to return a default.
so usage will be
-- No default
require'nvim-web-devicons'.get_icon("filename.js", "js")

-- Or with default
require'nvim-web-devicons'.get_icon("filename.js", "js", { default = true })

I think this is preferable to just removing it and adding the default to exports because by removing it it means you won't be able to get the highlight name for the default icon. The default icon's name is Default but the highlight group is added when get_highlight_name is called so it's actually DefaultDevIcon which someone won't know unless they check the code. If they do hard code this though then if we change the way names are created people using this will have to change their plugins to match the new name.
Also in bufferline.lua it means I have to do nil checks manually then add and highlight the default icon and group as well

Right thanks :)
we need to write some docs for this plugin ^^


trying to run a simple aggregate query Times out every time

Repro steps:

Action: cosmosDB.executeAllMongoCommands
Error type: string
Error Message: Timed out executing MongoDB command "db.ingestion_queue.aggregate([{$match:{date_time:{$gte:ISODate("2018-08-09")}}},{$group:{_id:{provider:"$provider_name",file_type:"$file_type"},total:{$sum:"$file_size_bytes"}}}],{maxTimeMS:0});"
Version: 0.8.0
OS: darwin

No problem, happy to help.  As far as reproducing it, there isn't much to report, just connecting to a mongo instance in VS Code and trying to run the query makes it happen.  I can run the same query without issue when executing via the mongo shell.  Let me know if you need anything else to dig further.

Other info worth noting.  I'm connecting to the primary node in a replicaSet thru a local port forward, so the local port (9204) is forwarded to the 27017 port of the primary node.  I'm able to execute the same query via Robo 3T.

Ah, I missed the ISODate. :)
#769 is a log of that.
We are looking into fixing that.
As a workaround, we support using $date from EJSON .
Hope that helps.

I'm guessing the "timed out" is an incorrect error message, we should fix that.  Unfortunately requires a rewrite of one of our classes.

Would you mind quickly trying an experimental version that may report better errors? It's easy to uninstall afterwards via the extensions view in vs code.  See instructions here: https://github.com/Microsoft/vscode-cosmosdb/issues/852#issuecomment-479734886.
Thanks!
Stephen

Closing, as the error no longer occurs.


404 Error when too many sensors

Getting a 404 error, which I suspect is caused by a too-long URL.  My system has 96 devices, resulting in a very long GET statement.  Here is the error message received:
[3/10/2021, 06:55:16] [Security System] Error: GET https://www.alarm.com/web/api/devices/sensors?ids[]=100167024-95&ids[]=100167024-91&ids[]=100167024-81&ids[]=100167024-80&ids[]=100167024-79&ids[]=100167024-16&ids[]=100167024-17&ids[]=100167024-18&ids[]=100167024-19&ids[]=100167024-20&ids[]=100167024-21&ids[]=100167024-5&ids[]=100167024-77&ids[]=100167024-78&ids[]=100167024-96&ids[]=100167024-4&ids[]=100167024-73&ids[]=100167024-39&ids[]=100167024-40&ids[]=100167024-41&ids[]=100167024-42&ids[]=100167024-43&ids[]=100167024-44&ids[]=100167024-75&ids[]=100167024-84&ids[]=100167024-49&ids[]=100167024-1&ids[]=100167024-76&ids[]=100167024-8&ids[]=100167024-9&ids[]=100167024-10&ids[]=100167024-11&ids[]=100167024-12&ids[]=100167024-13&ids[]=100167024-14&ids[]=100167024-15&ids[]=100167024-3&ids[]=100167024-72&ids[]=100167024-87&ids[]=100167024-32&ids[]=100167024-33&ids[]=100167024-34&ids[]=100167024-35&ids[]=100167024-36&ids[]=100167024-37&ids[]=100167024-38&ids[]=100167024-68&ids[]=100167024-7&ids[]=100167024-83&ids[]=100167024-65&ids[]=100167024-67&ids[]=100167024-58&ids[]=100167024-66&ids[]=100167024-55&ids[]=100167024-57&ids[]=100167024-2&ids[]=100167024-45&ids[]=100167024-70&ids[]=100167024-23&ids[]=100167024-24&ids[]=100167024-25&ids[]=100167024-26&ids[]=100167024-27&ids[]=100167024-28&ids[]=100167024-69&ids[]=100167024-85&ids[]=100167024-22&ids[]=100167024-90&ids[]=100167024-86&ids[]=100167024-71&ids[]=100167024-74&ids[]=100167024-29&ids[]=100167024-30&ids[]=100167024-31&ids[]=100167024-64&ids[]=100167024-54&ids[]=100167024-63&ids[]=100167024-89&ids[]=100167024-53&ids[]=100167024-93&ids[]=100167024-6&ids[]=100167024-82&ids[]=100167024-62&ids[]=100167024-92&ids[]=100167024-88&ids[]=100167024-51&ids[]=100167024-60&ids[]=100167024-56&ids[]=100167024-61&ids[]=100167024-50&ids[]=100167024-59&ids[]=100167024-52&ids[]=100167024-94&ids[]=100167024-46&ids[]=100167024-47 failed: 404
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:470:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 1)
at async Promise.all (index 0)

Same here:
Error: GET https://www.alarm.com/web/api/systems/systems/4483115 failed: request to https://www.alarm.com/web/api/systems/systems/4483115 failed, reason: read ECONNRESET
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:466:15
at processTicksAndRejections (internal/process/task_queues.js:93:5)

these sound like different errors from the original and shouldn't be considered part of this issue thread. a 404 error typically means page not found.  my guess is that is the correct error message, but I'm trying to understand why.  My first guess was that the URL formed is too long.  Another guess is that sensor 48 in my system has been disabled at the panel due to an issue with the physical sensor itself.  I don't see that sensor number in the list created by the URL.  It's clear that homebridge-node-alarm-dot-com logs in successfully, it must do some sort of poll/pull of the sensors (the IDs are formed correctly) but then encounters something it is not expecting.  Hoping someone can debug or suggest workaround.  Thanks,

Hi, I'm still having the same errors as I initially posted.  It's not the same as the ECONNECT errors that others weighed in with.  I get the 404 error that I originally posted.  Could this have anything to do with having so many sensors (96)?  I started adding them all to the ignoredDevices list, including the ones that are listed in the error message, but I still get the same error message.  My guess is the the initial GET communicates with the the alarm.com service and pulls all registered sensors...then filters them out so that the ignoredDevices isn't helpful.  Hoping to get some help troubleshooting if anyone can assist.  Thanks,

What version are you using, v1.7.1 or v1.7.2-beta.9? Although the beta version supports 2 factor authorization it can be used without. Benefit is that cached sensors are handled correctly and reduces communication with Alarm.com startup accordingly. May address the 404 error in the process.
I have submitted a pull request for a sampling error in beta-9 but has not been acknowledged by the author as of yet.

I am a "new" user of this accessory, although I've been using HomeBridge for about 5 years, and have never had this accessory working.  I originally installed alarm-dot-com using 1.7.1 a few months ago.  I got the error in my original post.  After reading about the ECONNECT errors everyone was having (I didn't have that error message), I went to 1.7.2-beta--and received the same error.  I recently read on the ECONNECT MEGATHREAD about downgrading, so went down to 1.6.5--again, same error message.  That's when I decided to re-activate this issue.
I only mention the 96 sensors since when I activated the system (AlarmGrid), they were kinda surprised by the number of sensors I had. So I have it in my head that 96 is alot.  Perhaps it's not.  I had read that a 404 error can be thrown by some servers when the GET is too long...and I made the connection that the URL that gets formed for a 96-sensor system may be the issue.
Would it be worth trying to disable some of the sensors at the panel as a way to reduce the size of the initial GET URL?

Thanks @DMBlakeley.
I just deleted the last 11 zones at the panel, so now there are 85 zones.  Unfortunately I get the same error message:
UNHANDLED ERROR: Error: GET https://www.alarm.com/web/api/devices/sensors?ids[]=100167024-95&ids[]=100167024-91&ids[]=100167024-81&ids[]=100167024-80&ids[]=100167024-79&ids[]=100167024-16&ids[]=100167024-17&ids[]=100167024-18&ids[]=100167024-19&ids[]=100167024-20&ids[]=100167024-21&ids[]=100167024-5&ids[]=100167024-77&ids[]=100167024-78&ids[]=100167024-4&ids[]=100167024-73&ids[]=100167024-39&ids[]=100167024-40&ids[]=100167024-41&ids[]=100167024-42&ids[]=100167024-43&ids[]=100167024-44&ids[]=100167024-75&ids[]=100167024-84&ids[]=100167024-49&ids[]=100167024-96&ids[]=100167024-1&ids[]=100167024-76&ids[]=100167024-8&ids[]=100167024-9&ids[]=100167024-10&ids[]=100167024-11&ids[]=100167024-12&ids[]=100167024-13&ids[]=100167024-14&ids[]=100167024-15&ids[]=100167024-3&ids[]=100167024-72&ids[]=100167024-87&ids[]=100167024-32&ids[]=100167024-33&ids[]=100167024-34&ids[]=100167024-35&ids[]=100167024-36&ids[]=100167024-37&ids[]=100167024-68&ids[]=100167024-7&ids[]=100167024-83&ids[]=100167024-65&ids[]=100167024-67&ids[]=100167024-58&ids[]=100167024-66&ids[]=100167024-55&ids[]=100167024-57&ids[]=100167024-2&ids[]=100167024-45&ids[]=100167024-70&ids[]=100167024-23&ids[]=100167024-24&ids[]=100167024-25&ids[]=100167024-26&ids[]=100167024-27&ids[]=100167024-28&ids[]=100167024-69&ids[]=100167024-85&ids[]=100167024-22&ids[]=100167024-90&ids[]=100167024-86&ids[]=100167024-71&ids[]=100167024-74&ids[]=100167024-29&ids[]=100167024-30&ids[]=100167024-31&ids[]=100167024-64&ids[]=100167024-54&ids[]=100167024-63&ids[]=100167024-89&ids[]=100167024-53&ids[]=100167024-93&ids[]=100167024-6&ids[]=100167024-82&ids[]=100167024-62&ids[]=100167024-92&ids[]=100167024-88&ids[]=100167024-51&ids[]=100167024-60&ids[]=100167024-56&ids[]=100167024-61&ids[]=100167024-50&ids[]=100167024-59&ids[]=100167024-52&ids[]=100167024-94&ids[]=100167024-46&ids[]=100167024-47&ids[]=100167024-48 failed: 404
at get (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:463:15)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at authenticatedGet (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:421:17)
at Object.getCurrentState (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:144:35)
at async Promise.all (index 0)
at ADCPlatform.listDevices (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:305:26)
It feels like it can't handle creating a GET that's longer than that shown.  It chokes on/about the 48th zone.  Is there a max length to the URL formed?

Scratch that.  I rebooted the Pi and now am getting further.  Hang on...

Yup, that did it!  To recap: I deleted 11 (96 down to 85) sensors in my panel.  Now (after a Pi reboot) the accessory loads correctly (and shows up in my Home app).  I am getting some messages in the Homebridge log that a number of the sensors/accessories are being ignored.  They seem to be windows, but will review documentation to learn about what sensors are supported.
Thanks a bunch.  It sounds like there's a potential fix in an upcoming release (multiple calls) which will enable me to re-enable the 11 sensors I deleted, so I'll wait for that.
Here's the output from the log file/console (edited):
[20/08/2021, 15:48:24] [Security System] Logged into Alarm.com as<EMAIL_ADDRESS>[20/08/2021, 15:48:42] [Security System] Received 1 partitions from Alarm.com
[20/08/2021, 15:48:42] [Security System] Restoring accessory with ID xxxxx-127
[20/08/2021, 15:48:42] [Security System] Received 83 sensors from Alarm.com
[20/08/2021, 15:48:42] [Security System] Restoring accessory with ID xxxxx-81
[20/08/2021, 15:48:42] [Security System] Ignored sensor Covered Terrace Window 2 (xxxxx-40)
and so on, with various sensors with different IDs "restored" and other sensors ignored.

Glad to hear that you were able to get up and running. As an FYI, I have generally found that a second reboot of the pi especially after setting devices to ignore is required. The first removes the device from the cache and then the second is a clean reboot.
Hopefully @chase9 will be able to add some batch code that will allow you to use all of your sensors. As of the end of the month I will not longer have access to Alarm.com due to a move.

I have the same GET 404 errors and a >90 sensor system -- bumping the thread for any updates

Hoping this will be resolved in an upcoming release.  Any thoughts @chase9 ?  Many thanks.

This issue should be resolved in the latest beta (1.8.1-beta.2), please test and let me know.

Chase9--apologies for not checking in sooner.  Just saw your update today, downloaded the 1.8.1-beta.2 version and am happy to say it all works!!!  thanks much for everything.  now I need to put some logical names to my sensors so I know which sensor is what.  THANKS again.

So glad to hear that it worked!


[CHANGED] Client Accept error log level

This is an error users should know about. Thus, the log level should be
error.
Fixes #583
@nats-io/core @ripienaar

Coverage decreased (-0.3%) to 91.641% when pulling 4a6fd4317a53ad78a669a37e4380ed71a032763e on accept_error_level into 0c3d4ce7fa0f8d5367d7844a3b3f4539ce4c034e on master.

LGTM


Text is not drawn correctly

The lower part of drawn text is cut off, but for some reason it is drawn correctly on a redraw.

Drastically improved with 63118be92e6ba75b8a67f5264e986f7f0d143188.
Still not perfect (the bottom of the letter 'g' is still cut off in some places).


Add faster Normal implementation

Distributions in PreliZ are wrappers around SciPy distributions. This is fine for many situations, but when iterative operations are required like in optimization we could benefit from faster implementations.
This could also be used to avoid duplication of code and efforts, for instance in Kulprit we also need fast logpdf evaluations.

Codecov Report
Attention: Patch coverage is 88.39779% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 86.25%. Comparing base (f0a63bc) to head (9fc1336).

Files
Patch %
Lines

preliz/distributions/normal.py
85.36%
12 Missing :warning:

preliz/distributions/distributions.py
86.04%
6 Missing :warning:

preliz/internal/distribution_helper.py
77.77%
2 Missing :warning:

preliz/tests/test_dist_scipy.py
97.14%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #344      +/-   ##
==========================================
- Coverage   86.70%   86.25%   -0.46%
==========================================
  Files          38       40       +2
  Lines        4303     4424     +121
==========================================
+ Hits         3731     3816      +85
- Misses        572      608      +36

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Tracking: User-Defined Function(UDF) Support

This issue tracks the progress of UDF support in RisingWave kernel.
We plan to support UDF in 3 kinds of languages:

SQL
External process which implements Apache Arrow Flight protocol (Python UDF, Java UDF)
Embedded execution in WASM

Any ideas and suggestions are welcome!
Progress
Frontend:

[x] #7265

SQL UDF:

[ ] Not started

Python UDF:

[x] #6394
[x] #7178
[ ] Python UDF SDK

WASM UDF:

[ ] Investigate WASM execution

What is the interface for WASM? :) We can probably leverage arrow SDK too?

What is the interface for WASM? :) We can probably leverage arrow SDK too?

Yeah, the data exchange format will be arrow too. But the specific user interface has not been decided yet. For example, we may allow user to upload a compiled wasm object file, or we can help user compile their Python/JS code to wasm. The latter sounds more convenience.

https://github.com/risingwavelabs/risingwave/issues/7410 Seems like a good case.
My concern with WASM kernel is

whether we will embed the VM into the compute node
how we will handle errors, including the VM errors like out of bounds

It seems that if we do not do 1., it is as good as an external function. Because if we do 1., then we get errors directly from the WASM VM.

Not sure how the user-defined errors can be propagated, however. I believe we should implement a wrapper type for such errors? So the response from external UDFs and response for WASM UDFs will be wrapped in this error type.

Sure. No matter whether we embed the VM or put it as an external function, there will be a lot kinds of errors to deal with. And I don't think there is anything we can do other than report them directly to users.
For question 1., I think it should be embedded to the compute node, because we can take advantage of the VM to avoid communication latency between nodes.

Do we intend to support implicit cast of arguments or require explicit cast? For example, given a builtin sind(double precision) -> double precision, we can write sind(30). But if that was a udf we have to write sind_udf(30::double precision) right now.

Do we intend to support implicit cast of arguments or require explicit cast?

Yes, we should support implicit cast for UDF as postgres does. This is not yet implemented and I'll create an issue to track it.


🐞 Auto change theme is not working properly

Description
hi, there seems to be something wrong with the auto change theme mode, it keeps putting dark mode when i have light mode enabled, i have to manually turn it off and on again for it to detect light mode.
To Reproduce
I'm not sure how you can reproduce this
Expected Behavior
To detect my systems preffered theme mode when I start up the app
Version Information
CodeEdit: Version 0.1.0-alpha (38)
macOS: 14.5 (23F79)
Additional Context
No response
Screenshots
https://github.com/CodeEditApp/CodeEdit/assets/146845123/e921e5f3-6020-4c48-b3c7-ed8efd46f206

i am on windows so i can not fix it but if someone else has a branch and uses macOS i might be able to  get in contact about this issue.

im up to it if you know what do (because I have no idea), might be fun for me to watch you do it as i might learn something.

is it a setting?
so i don't see anything in the themes folder if its a setting that might connect to a config folder so... tell me if its a setting in the meanwhile i will look through some more files.

the "automatically change theme based on system appearance" is a setting, if that's what you're asking for.

Should find something at CodeEdit/Features/Settings/ThemeSettings

It's very hard to reproduce though, just ran a clean build of code edit and the editor pane and the terminal pane was light mode while the rest was dark mode, the detect system appearance option was enabled, I reenabled it and it solved it. I quit Xcode, cleaned the build directory, and ran a clean build again but this time it worked.

https://github.com/CodeEditApp/CodeEdit/tree/main/CodeEdit/Features/Settings/Pages/ThemeSettings
found it! i dont see ANYTHING that has to do with automation yet but i am looking!

here: looking for bugs now!
https://github.com/CodeEditApp/CodeEdit/blob/main/CodeEdit/Features/Settings/Pages/ThemeSettings/Models/ThemeSettings.swift

i only found a few things to fix here but i do not know if anything here is what matches your bug, but this:
/// Use the system background that matches the appearance setting         var useThemeBackground: Bool = true
that is the only thing that controls this other then the SYSTEM FILE that controls the exact same thing. so something may be wrong with that i may fork this to fix my new script that should fix some errors but not necessarily the bug you are looking to fix.

here is my fixed

here is my fixed version:
https://github.com/webbrowser11/CodeEditbugfix/blob/main/CodeEdit/Features/Settings/Pages/ThemeSettings/Models/ThemeSettings.swift

i am not sure if that is what you were looking to fix so i am NOT making a pull request


Use overloads when both protocol method and convenience method are new

SDK change: https://github.com/Azure/azure-sdk-for-net/pull/35724
Fix https://github.com/Azure/autorest.csharp/issues/2887
To resolve #2887, there need three steps:

We should have the ability to know the latest GA tag. https://github.com/Azure/azure-sdk-for-net/pull/35001. This is .net specific.
We should have a common script to download the latest code with the latest GA tag. https://github.com/Azure/azure-sdk-tools/pull/5587
And the .net generator for the specifc usage in this PR.

hello @pshao25  would you please also add a test which use AppendValue ambiguity-handling-option, make sure the code and the diagnostics Scope are correct in that option?

hello @pshao25 would you please also add a test which use AppendValue ambiguity-handling-option, make sure the code and the diagnostics Scope are correct in that option?

Yes, cadl-ranch "hello" is for that purpose.


QOL - When hiding model folders (c00/c01/etc), also change the eye icon to closed

When hiding model folders (c00/c01/etc), also change the eye icon to closed. Current functionality leaves it open, leading to potential confusion when more than 2 model files are loaded

Yes


Remove internal UDS option and tests from client

Upcoming engines dropped support for UDS.

uds is currently "documented" here, and we should post an update and close it as well when done
https://github.com/prisma/prisma/issues/5533


with navigation bar transparent and UIRectEdgeAll, gif header view is not hidden

Any clue?

header.automaticallyChangeAlpha = YES;


VR View Info Gone - Replaced by GoogleVR Mobile only?

Clicking on the "i" button in VR views embedded in web pages takes me to an updated web page that no longer mentions website-based VR View, only GoogleVR for mobile platforms.
No information remains for web site usage?

Looks like it's been moved to the Concepts subsection.
https://developers.google.com/vr/concepts/vrview

Thank you.


Use module name in logging

https://github.com/DataONEorg/hashstore/blob/294b4fe9168edb7fa9f44fe9d285bf4be4f33f01/src/hashstore/filehashstore.py#L87
Logging using the module name can assist with clear logging by labeling messages with module name and providing the ability to set log level per module (helpful for downstream users). Suggest using something like:
def getLogger():
    return logging.getLogger(__name__)

Then using getLogger() within the code to get a logger instance per class or when needed. e.g.:
def foo():
    L = getLogger()
    L.debug("foo message")

This has been completed via Feature-140: Logging Enhancement


Basic shell script with Git dependency

This shell script should only run if the user has Git. If it does run, it simply forces a pull to ensure proper behavior.

For the record I had considered this approach but I thought it would violate a dependency rule (AKA don't make people install shit they don't need) but I've since long retracted that opinion from the EN Patch because of additional features the other bat files including the almost-malware behavior of dropping a VBS script on the startup folder :)


Traceback (most recent call last):
File "./run_glue_prune.py", line 394, in
main()
File "./run_glue_prune.py", line 385, in main
trainer.train()
File "/bit_share//LLM/Fitune_LLM/model_pruning/CoFiPruning/trainer/trainer.py", line 285, in train
loss_terms = self.training_step(model, inputs)
File "/bit_share/zhangxiaolei/LLM/Fitune_LLM/model_pruning/CoFiPruning/trainer/trainer.py", line 704, in training_step
loss.backward()
File "/data03//anaconda3/envs/llmprune/lib/python3.8/site-packages/torch/_tensor.py", line 307, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "/data03//anaconda3/envs/llmprune/lib/python3.8/site-packages/torch/autograd/init.py", line 154, in backward
Variable._execution_engine.run_backward(
RuntimeError: CUDA error: device-side assert triggered

Hi it seems mostly like a data issue. Could you check that the input_ids are all within the vocabulary size?


qt re-implementation of manage names

This is a merge and partial re-write of "manage names" tab from namecoin legacy on top of namecoin-core. I used the RPC functions, internally, to do the heavy lifting. The previous QT UI duplicated much of the code. I also moved the manage names UI from a separate popup to a tab in the main UI.
I tried to keep the patch footprint as small as possible. If anyone sees room to make it even smaller, please comment. A major goal here was to minimize the probability of conflicts in the future.
Some of the code you see here is directly merged from the legacy names page UI. Please let me know if you see problems in it.
Some areas that warrant extra consideration:

The changes in src/qt/transactionrecord.cpp were 100% taken from legacy. They might not be necessary.
The changes in walletdb.cpp are very important and should have code review.
Testing using different QT/GUI config settings would be helpful

FYI, namecoin/namecoin-core is a fork of this repo, so PR redirects to here, although I meant to submit to namecoin/namecoin-core


1.999.0 is still in the repo

Hi. Referencing #75639 and #74915. The tag is back again and automated system like this keep offering the upgrade. I started writing exclude rules to prevent it, but it'd be great if this could be stopped with some git hook...

I deleted the tag. Unfortunately there's no way to enforce that someone does not accidentally push it back up again (https://github.com/github/feedback/discussions/5529), but I have advised our team to delete it locally. If it is a persistent problem we could probably have a bot to delete the tag, but hopefully the advisory solves the issue 🙂


Consider dropping candidates that have parse errors for resolution instead of failing the installation

I have  really weird issue with latest uv (0.1.28) and I think there is an issue with how errors is parsing candidate metadata might cause the whole build to fail.
In some cases of uv pip install - some old releases of some transitive dependencies with broken metadata might cause the whole installation to fail - even if there are other candidates that are perfectly fine.
This one is pretty similar to one which I opened in the past and closed (#2411) - but this time, I think the way how uv fails is a bit too "panicky".
One of the steps of our CI is building PROD images and while doing it in release branch, we are buding the released airflow from sources to wheel and install it with 'PROD' image extras - which will pull provider packages and a number of transitive dependencies from PyPI.
The command to run is:
uv pip install 'apache-airflow[aiobotocore,amazon,async,celery,cncf-kubernetes,common-io,docker,elasticsearch,ftp,google,google-auth,graphviz,grpc,hashicorp,http,ldap,microsoft-azure,mysql,odbc,openlineage,pandas,postgres,redis,sendgrid,sftp,slack,snowflake,ssh,statsd,uv,virtualenv] @ file:///docker-context-files/apache_airflow-2.9.0-py3-none-any.whl'

This nicely work for Python 3.8 - 3.10 and 3.12, but for Python 3.11 (and only for Python 3.11) it fails with this error:
#64 6.287 error: Failed to download: google-cloud-bigquery==1.28.2
  #64 6.287   Caused by: Couldn't parse metadata of google_cloud_bigquery-1.28.2-py2.py3-none-any.whl from https://files.pythonhosted.org/packages/ce/af/89ccb3dd70a86516cb408dd7b7484d2fdd073bdce6405f722f75e6058e66/google_cloud_bigquery-1.28.2-py2.py3-none-any.whl.metadata
  #64 6.287   Caused by: after parsing 2.0, found "de" after it, which is not part of a valid version
  #64 6.287 pyarrow (<2.0de,>=1.0.0) ; (python_version >= "3.5") and extra == 'all'
  #64 6.287          ^^^^^^

Of course - it's obvious what the problem is with the google-cloud-bigquery package - but this is a REALLLY old version of the package (4 years) and it's not the one that the installation should resolve to. All the previous resolutions correctly resolved it to google-cloud-bigquery==3.20.1  - which is latest version released on 1st of April (not an April's fool joke). But the PROD image installation somehow fails the whole uv pip install fails - because of that wrong metadata, in package version that should not even be considered.
I am attempting to battle this in two ways:

add a more direct dependency to the future provider (and lower-bind it) https://github.com/apache/airflow/pull/38753
switch back to pip for "Release" PROD builds when we do PROD image building using pip rather than locally build providers (which we use in main : https://github.com/apache/airflow/pull/38749 and https://github.com/apache/airflow/pull/38752

I  am not sure if 1. will help, 2. should help for sure - (and for now we anyhow use pip to install airflow in "real" PROD image - so that is going to stay likely (release branches should be as close to "production" releases as possible) - but it would be cool to investigate and see why such a metadata issue in an old version that is not really even going to be used is causing the whole installation to fail.  It does not seem too robust if someone could release (or have released in the past) an old, broken version of the package that would break new installation for new versions of the same package (being transitive dependency)
Link to show thee failure (logs will disappear in 30 days or so) : https://github.com/apache/airflow/actions/runs/8555464849/job/23446007205#step:10:3693 - and you can see that it's only Python 3.11 that fails (which is even stranger).

Thanks for all the details! I'm not sure why we're backtracking so far here, but you can see some more information about the general problem at https://github.com/astral-sh/uv/issues/1398
Reasonable lower bounds are definitely a good solution to help a resolver in a situation like this.
I'm not sure about dropping the candidates vs failing — cc @konstin.

This looks similar to https://github.com/astral-sh/uv/issues/1800.

I think we should be skipping invalid candidates...

We do this in some cases already though. I'm trying to remember when.

I can do this tomorrow as a fun thing, it seems interesting.


Support Avro Schemas and Schema Registry

Describe the feature request
When using Springwolf with Avro Models:

the generated example is generated with a lot of field that should've been ignored.
the yaml file is not parsable by the AsyncAPI studio
the UI doesn't display information about the schema registry
The documentation is not clear on how to publish messages using a Schema Registry

The example message should be:
{
  "someString" : "text",
  "someLong" : 0
}

Github Repository with project:
https://github.com/raphaeldelio/demo-springwolf
AsyncAPI Studio:

Springwolf UI:

Hi @raphaeldelio
Thank you for the report, the suggestion and the linked demo repo.
Regarding the questions:

We do not have native support for avro yet.
True, the refs on payload level are not resolved in the asyncapi UI. This will be resolved when the 3.0 spec is released, which has been postponed.

Schema registries are also not supported yet. Shall we move that to a different enhancement?

Feel free to improve the support as there are likely more people who use avro.
We are happy to assist and connect on Discord.

@timonback Thank you! I will test it when the snapshot is available.

Hi @raphaeldelio,
the SNAPSHOT version is available now

@timonback just tested it and it works! I tested it with an Avro Model that has nested records as well. Thank you for this. When is this planned to be released?

Awesome.
We plan to release a new version at the end of each month, so the next one is at the end of February

Thank you very much for the shoutout on LinkedIn!
Just to clarify, Avro is supported as of the current release.
AsyncAPI 3 including the fix for the schema will will be part of the February release.
As the February release will contain breaking changes, it can still make sense to wait for that release.

@timonback I found two bugs. One when dealing with nested avro models and another that always throws exceptions.
https://github.com/springwolf/springwolf-core/pull/582

Great that you provide a fix for it right away!
I/We will have a look on Friday


Update CHANGELOG

For releases 1.0.1, 0.13.2, 0.12.3 and 0.11.4

Codecov Report

Merging #2148 (5f40380) into main (2dda55c) will decrease coverage by 19.88%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #2148       +/-   ##
===========================================
- Coverage   61.22%   41.34%   -19.89%
===========================================
  Files         270      132      -138
  Lines       20478    16531     -3947
===========================================
- Hits        12538     6835     -5703
- Misses       6643     9109     +2466
+ Partials     1297      587      -710

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Travelling wave example seems broken

The traveling wave example does not work for me. It produces a video but there is no bleu line. Note that I have tweaked time() to mytime() and linspace() to range() and changed the file path. Does anybody have an idea of what is wrong?
using Makie

scene = Scene()
mytime = Node(0.0)
f(v, t) = sin(v + t)
scene = lines!(
    scene,
    lift(t -> f.(0:50:2pi, t), mytime),
    color = :blue)
p1 = scene[end];
N = 100
record(scene, "travelling_wave.mp4", range(0, stop = 4pi, length = N)) do i
    mytime[] = i
end

Thanks!

julia> 0:50:2pi |> length
1

You should use something like (0:0.01:2pi) - like in the example :P

Yep, that would do it! Thanks!


Documentation on New Cmdlets

I would love to see any documentation on the new cmdlets, especially New-CMRequirementRuleOUValue. I have been waiting YEARS for this one!

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

ID: 83b95889-e52a-5cc6-eebf-630d9abb3522
Version Independent ID: 73e4b737-e9f9-27ee-6ee5-0ad0ef1afddd
Content: Version 1810 release notes - Configuration Manager
Content Source: docs-conceptual/1810-release-notes.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @pfurches for the feedback. This content is mostly auto generated from what's in the module, but what's currently published is out of date. I have a pending update to bring it up to the latest version.


Errors prerendering page

These kind of errors are preventing a Vercel build at the moment:

Error occurred prerendering page "/programs". Read more: https://nextjs.org/docs/messages/prerender-error
Error occurred prerendering page "/posts". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Unable to fetch, please see our FAQ for more information: https://tina.io/docs/errors/faq/
Errors:
Error querying file content/program/Sonntag---Workshops.mdx from collection program. Please run "tinacms audit" or add the --verbose option  for more info
at TinaClient.request

I ran a yarn tinacms audit - but no errors were detected:
Checking post collection. 11 Documents
Checking program collection. 9 Documents
Checking global collection. 1 Documents
Checking author collection. 4 Documents
Checking page collection. 9 Documents
✅ Audit passed
Done in 22.32s.

Please check what the problem could be with content/program/Sonntag---Workshops.mdx

They had created Sonntag---Workshops.mdx file to times. I did some changes [here:] (https://playbern.ch/admin#/~ ) but github still same and my changes does not reflected to playbern.ch. When I turn back to edit mode, the changes are still there.

It looks like it only affects the main branch, the identical code builds fine from dev.
We should signal this to Tina, and see if there's a way to rebuild the graph in the cloud console. I already tried clicking all the Advanced Options to no avail.

Solved by resetting the account.
See also https://github.com/tinacms/tinacms/issues/4176


Allow setting/using machine_use_priv

Closes #48
Adds tool setting machine_use_priv that is checked if fake player is using tool.
Fake player is allowed to use tool if machine_use_priv is set and fake player has machine_use_priv.
Added default machine_use_priv privilege for luatool: server.
Privilege can be configured using metatool configuration file, for example to allow moderators to use luatool with machines add this to configuration file:
metatool:luatool:machine_use_priv = ban

Similar configuration should work for any other tool but none of other tools have been tested with machines.

@SwissalpS @jessicara might be interested in this.


Process data in photon-counting mode

Produce 2D images in photo-counting mode (L2b images) that can then be fed into the regular astrometry and PSF subtraction codes

This requires simulating detector data at sufficiently high frame rates
Implement a photon counting threshold (do we also need to figure out this threshold eventaully)
Account for photon-counting photometric corrections
Dark subtraction in photon-counting mode

If we create error extensions (which I'm a fan of), we'll need to adjust them to account for the added EM Gain noise.

Note the separate, but related issue #21, which is related to calibrating the EM Gain

This may have already been discussed, but just wanted to document:  https://github.com/roman-corgi/PhotonCount does these things (selects a threshold, accounts for photometric corrections, etc).


fix(portal): fix logo download links

📥 Proposed changes
Fikser lenkene for nedlasting av logo (ble lastet ned som tekstfiler med filnavnet).
☑ Submission checklist

[x] I have read the CONTRIBUTING doc
[x] yarn build works locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

💬 Further comments
affects: @fremtind/portal

Ser at den feiler - skal jeg godkjenne likevel?


[Tree Taxonomy - Design] List View

From the tree taxonomy search, looking at multiple views to display a list of trees. Mobile may have a better use for a list than desktop.

Having multiple displays for the tree taxonomy search. The table is currently already in use, but for mobile I am thinking this has potential similar to a table.
The layout of text per component is WIP, but I am trying to figure out what could change into a pill badge etc for all displays.
@zoobot do you like this view for the tree taxonomy or should we just stick with the two views?

Updated the design to match the other views and use the dormancy type badge.

this design may not be used as it was a prototype to see if it is viable. This design will potentially be used for events, community, teams, organization as a display view


better icons

I do not like the icons of toolbars, seems a bit date.
is there a way I can use modern flat icons like the one in the github toolbar above^?

You can replace the icons. See here in the last example.


Question: why don't use type embedding to load custom type collection records (when using pocketbase as framework)

Hello dear mainainers !
Question
Pocketbase can be used as a framework so I am wondering why there is no support for using the golang types in the dao api ? It would allow to benefits from the internal record API and other related hooks.
Using string to get,set fields seems really annoying and error prone.
What I would like to have
Can we imagine something like :
type CustomRecord struct {
	*models.Record
	DiscordUsername string `db:"discord_username" json:"discord_username"`
}
var record CustomRecord
record, err := e.App.Dao().FindCustomRecordById("users", "80larfsmyukud28", &record)
if err != nil {
	return fmt.Errorf("unable to find article: %w", err)
}
record.DiscordUsername = "aaa"
e.App.Dao().Save(record)

We could simplify this when generics will allors type parameter on methods to have :
rec, err := e.App.Dao().FindRecordById[CustomRecord]("users", "80larfsmyukud28")
Current  workaround (not working)
Currently I was imagining a workaround with that solution :
type CustomRecord struct {
	*models.Record
	DiscordUsername string `db:"discord_username" json:"discord_username"`
}
var record CustomRecord
collection, err := dao.FindCollectionByNameOrId("users")
if err != nil {
	return err
}
query := dao.RecordQuery(collection).AndWhere(dbx.HashExp{collection.Name + ".id": "80larfsmyukud28"})
if err := query.Limit(1).One(&record); err != nil {
	return err
}

// record.DiscordUsername is loaded as expected !

record.DiscordUsername = "test"

// now try to update it
// then print with the getter method
fmt.Println(record.Get("discord_username")) // it panics here

err = dao.Save(&record)
if err != nil {
	return err
}

It seems like data are not loaded into the record object, but the data are loaded from the tags structs.
Do you have any insight why 🤔 ?

This might be a lightest alternatives and cheaper (in term of code factorisation) to https://github.com/pocketbase/pocketbase/discussions/2697#discussioncomment-6154067

This might be a lightest alternatives and cheaper (in term of code factorisation) to #2697 (reply in thread)

But if it's not the case I can maybe implement a start of a codegen for what it's described in the discussion


The partner instant exchange SimpleSwap.io

Hi,
I am Nicolas, the manager at SimpleSwap.io, an instant cryptocurrency exchange.
We present a simple and easy-to-use platform that works without registration and limits and allows users to make swaps in just two clicks.
We successfully support BCH on our service for a long time and we have been exchanging BCH for more than 200 coins to our customers. I tried to find contact with your team but without results.
I'm sorry that I invaded here, but maybe you can tell me where I can turn. I would like to make contact so we can have an interaction.

Hi Nicolas, thank you for your interest in Bitcoin Cash and BitcoinCash.org!
You can reach out to me using handle @merc1er on Telegram or other social media, I will guide you through the process of adding a listing to the website.

Hi Nicolas, thank you for your interest in Bitcoin Cash and BitcoinCash.org!
You can reach out to me using my handle @merc1er on Telegram or other social media, I will guide you through the process of adding a listing to the website :)


Modification doesn't get synced/stored

OrientDB Version, operating system, or hardware.

[x] v2.2

Operating System

[x] MacOSX

Expected behavior and actual behavior
I need some advice on how to figure out the following problem. I have an empty db (noTx) using the following configuration:
factory.setUseLightweightEdges(true);
factory.setUseClassForEdgeLabel(false);
factory.setUseClassForVertexLabel(false);
factory.setKeepInMemoryReferences(false);
factory.setAutoStartTx(false);

graph = factory.getNoTx();

I do some modification on the database, add, lookup, update, and removed vertices and edges. After a while I print out the current state with:
graph.getVertices().forEach(v -> {
    final ORecord rec = graph.getRawGraph().getRecord(OIdentifiable.class.cast(v.getId()));
    System.out.println("----> " + rec.getIdentity());
    v.getEdges(Direction.IN).forEach(e -> {
        System.out.println("   - IN: " + e);
    });
    v.getEdges(Direction.OUT).forEach(e -> {
        System.out.println("   - OUT: " + e);
    });
});

and receive:
----> #65:0
   - IN: e[#105:0->#65:0][#105:0-EDGEA->#65:0]
----> #66:0
   - IN: e[#145:0->#66:0][#145:0-EDGEB->#66:0]
----> #67:0
   - IN: e[#145:0->#67:0][#145:0-EDGEA->#67:0]
----> #105:0
   - OUT: e[#105:0->#145:0][#105:0-EDGEC->#145:0]
   - OUT: e[#105:0->#65:0][#105:0-EDGEA->#65:0]
----> #145:0
   - IN: e[#105:0->#145:0][#105:0-EDGEC->#145:0]
   - OUT: e[#145:0->#67:0][#145:0-EDGEA->#67:0]
   - OUT: e[#145:0->#66:0][#145:0-EDGEB->#66:0]

everything is ok like that, but if I look at the running database using the UI or if I start the output aside in a different thread the result is:
----> #65:0
   - IN: e[#105:0->#65:0][#105:0-EDGEA->#65:0]
----> #66:0
   - IN: e[#145:0->#66:0][#145:0-EDGEB->#66:0]
----> #67:0
   - IN: e[#145:0->#67:0][#145:0-EDGEA->#67:0]
----> #105:0
   - OUT: e[#105:0->#145:0][#105:0-EDGEC->#145:0]
   - OUT: e[#105:0->#65:0][#105:0-EDGEA->#65:0]
----> #145:0
   - IN: e[#105:0->#145:0][#105:0-EDGEC->#145:0]
   - OUT: e[#145:0->#66:0][#145:0-EDGEB->#66:0]

You may notice, that the last edge (#145:0 is missing an OUT edge, the IN edge is there #67:0). This addEdge is the last statement I fire utilizing the Java API, if I add more edges or remove some the operations (I only tested a couple) are "synced" across the UIs and threads, just the one addEdge is somehow broken.
----> #145:0
   - OUT: e[#145:0->#67:0][#145:0-EDGEA->#67:0]

Can anybody point me in any direction what the problem could be (storage?, do I have to commit sometimes, even using noTx, ....)? How can I debug the problem (I'm using Java)? How can I see what the underlying problem may be? Why is the edge not being synced? Where does the sync with whatever happen? I'm just utilizing the Java API nothing special.
Thanks!
PS: I'm using a locally running OrientDB server (creating a plocal database)
PPS: All the operations I do are single-threaded, so no multi-threading involved, the only operation I run in a different thread (with a different database instance) is the sout, which runs only once after all other operations are applied.

I did some further investigation and I'm pretty sure that may be a bug (or a possible miss-usage which should throw an exception). The record behind the #145:0 is not getting saved, it just gets modified (the version does not change). The reason for that is, that the record is not marked as updated by the OTransactionNoTx::saveRecord implementation:
ODirtyManager dirtyManager = ORecordInternal.getDirtyManager(iRecord);
Set<ORecord> newRecord = dirtyManager.getNewRecords();
Set<ORecord> updatedRecord = dirtyManager.getUpdateRecords();

I couldn't figure out why the dirtyManager returns null in that specific case. I'll investigate further and keep the post updated!

Ok further things I found. It looks like that the vertex is not marked as updated, because the following happens in OrientVertex:

The following lines are executed for the specified vertex (#145:0), which sets the out = null

} else if (found instanceof ORidBag) {
  // ADD THE LINK TO THE COLLECTION
  out = null;
  ((ORidBag) found).add(iTo);
}

The overwrite is not executed, which normally ensures that the setDirty() is executed

if (out != null)
  // OVERWRITE IT
  iFromVertex.field(iFieldName, out, outType);

The vertex is modified in the "cache", but not written to the database.

So it looks like it is a bug... any information?

Last finding, if I manipulate a property of vertex #145:0, the dirty flag gets set, and the data (including the edge information) is correctly synced. So now I would call this a bug for sure, please confirm.
final OrientEdge edge = graph.addEdge(null, sourceVertex, targetVertex, label);
sourceVertex.setProperty("RND", new Random().nextInt());

hi @pmeisen,
Nice detailed investigation, yes if you change a property on the record would make it dirty and persist it, in any case also when ((ORidBag) found).add(iTo); happen there should be a callback inside that put the record in a status of "dirty" or  "dirty not changed" and make it finish inside the "updatedRecord" Set, and we have a lot of tests around this, but i think you may found a conbination of flags that create some problem, do you have a sequence of operation that can reproduce the problem ?
Thank you

hi @pmeisen,
We could reproduce this problem with another user that provided the test case, we fixed it and will be released in 2.2.13.
Bye

fixed and released, closing


change how hf is configured

I feel like I'm missing something..

this branch has been re-worked, please review

good 2 go


Define a last CI job which set's the whole pipeline exit status.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@98020fe). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage        ?   80.62%
=======================================
  Files           ?       41
  Lines           ?     1564
  Branches        ?      196
=======================================
  Hits            ?     1261
  Misses          ?      254
  Partials        ?       49

Flag
Coverage Δ

Linux
80.49% <0.00%> (?)

src
74.27% <0.00%> (?)

tests
90.60% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Documentation for items not 100% correct

The documentation for the items option states:

Num of items to display in gallery. Accepted values [0-12]

However this limit is only true for users. Tags can have many more than 12 (at least 70 according to Example 4).

Fixed, thanks for your feedback :)


Replace gatsby-plugin-google-analytics for gatsby-plugin-google-gtag

The old gatsby-plugin-google-analytics is not working on google analytics. I can submit a PR for it if you want.
Thanks for this amazing template

Hello, @abeledovictor  ! How are you? I hope you're well! Your contribution would be most welcome. Thanks!


Prepare release for Azure.ResourceManager.LoadTestService

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.LoadTestService

LGTM, but just double confirm, is this namespace already approved?

Good question, but other languages were already released,


bump to kube v1.7.8

@mrunalp PTAL
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

/test all

LGTM


azure: more accurate messages for resources created

Addresses #3250. We now print 'Configuring' instead of 'Creating' for upsert operations.

LGTM

:+1:


[Phoenix] Improve pomodoro, add short and long break timers

Please remember the Contributing Guidelines :heart:
:star2: What does this PR do?

Adds support for configurable short and long breaks between pomodoro sessions
:bug: Recommendations for testing
All changes should be tested across Chrome and Firefox.

TBD

:memo: Links to relevant issues or information

Closes #1569

Closing for now, will revive if we do another project

@shantanuraj why was this PR closed?


Add chatExport endpoint & tests

Rel PR to Jetbrains: https://github.com/sourcegraph/jetbrains/pull/1096
Test plan

tests
run the export action from the jetbrains IDE

hello @dominiccooney 👋 thank you for your review! I do not feel very confident in this area so I really appreciate your input
I agree with your points - I got some sleep, took a look at your comments, and managed to improve my solution.
Please, revisit my PR, close comments that you consider as fixed now, suggest me whatever you think makes more sense 🙏


Dbeaver: reading data in any table (bug)

Hey guys,
does anyone experiences the same problem as I do? Since update to 5.3.0 I can't read data in any table due to the same error:
Reason:
SQL Error [42P01]: ERROR: relation "xxx" does not exist
Position: 571
The problem is that it was working fine yesterday, but it doesn't today.

it is worthwhile to mention that I've restarted my laptop already :)

I assume that you are using PostgreSQL.
Do you read data in SQL editor? Try to switch active database:

SQL editor uses active database to run queries.

Oh, it works. Thank you! ;)


Replace the "completed" checkbox with something like PrioritySelector.

This'll allow changing status to cancelled/in-progress/etc via the UI (currently, some statuses are only possible via the cli interface).

Generally I would recommend against implementing each peculiarity of iCalendar... boolean "completed" value is the 80% usecase.

Yeah, that makes sense. TBH, I wanted CLI/UI parity, but if nobody needs it, I'll skip that.
I will however, hide the completed checkbox when running todo new, since it doesn't make sense to create a completed todo.


Autorun feature for missions

Currently, the autorun feature is limited to the playground. I think some missions will benefit from autorun.
I suggest that for now, we add the same autorun button to the frontend display of missions as the one we have for the playground. The frontend will remember the autorun setting in a global variable. This maximizes exposure of the feature, in order to gather views and feedback.

#466


Lineage registration fix headless mode

Fiji with mastodon-tomancak installed would fail during startup when executed in headless mode.
The LineageRegistrationControlService caused this problem. It is initialized during the startup of Fiji, and it tried to create a JFrame, which fails in headless mode. And as a consequence causes Fiji to crash.
This is now fixed by the lazily initialition of the JFrame in the LineageRegistrationControlService.showDialog() method.
There is also I unit test which should detect similar problems in the future.

Hint to myself the bug could be provoked by running ImageJ-win64.exe --headless --console