DWM1000 error in CLKPLL_LL_BIT

Hi:
I have been trying to make this code work on an Arduino Mini PRO 3.3 8Mhz like the one in the testbed ( receiver) and an arduino Mega 2560 ( transmitter).  The Tx works Ok, or at least i think so, but the RX doesn't receive anything.  If i artificially make the interrupt go i see the package is corrupted in the receive buffer and the CLKPLL_LL_BIT is set, although this doesn't generate the interruption by itself.  Do you have any insight on this error? Is there an specific reason why the CLKPLL_LL_BIT is checked in your code.
Best regards.

Hi there,
from the user manual on CLKPLL_LL: "Clock PLL Losing Lock. This event status bit is set to indicate that the system’s digital clock PLL is having locking issues. This should not happen in healthy devices operating in their normal range. Its occurrence may indicate a bad configuration, a faulty part or a problem in the power or clock inputs to the device."
I learned from my early breadboard, protoboard tests that everytime I received corrupted packages, at the same time as I observed a clock-losing-lock event. In most cases it was a loose wire or a low-level misconfiguration (which I hope it is not! :-)).
CLKPLL_LL is never present in the interrupt mask, so yes, this cannot be the source of interruption. Still interrupting artificially (while one device is constantly sending packets, right?) will likely never give you good packets - I guess. So for now, I'm sorry, but don't have a single solution to your problem.
Maybe you have some additional information on your setup and device configurations? Let me know if there's anything else I can help with.
Cheers,
Thomas

Hi, thanks for your answer.   I am using the same configuration that it is
described in the github repository, with the adapter board and a protoboard
with an arduino mini pro.   What do you mean with low-level
misconfiguration? Tuning Failure? OTP or LDE failure?
Best regards.
José
2015-09-17 4:39 GMT-03:00 Thomas Trojer<EMAIL_ADDRESS>
Hi there,
from the user manual on CLKPLL_LL: "Clock PLL Losing Lock. This event
status bit is set to indicate that the system’s digital clock PLL is having
locking issues. This should not happen in healthy devices operating in
their normal range. Its occurrence may indicate a bad configuration, a
faulty part or a problem in the power or clock inputs to the device."
I learned from my early breadboard, protoboard tests that everytime I
received corrupted packages, at the same time as I observed a
clock-losing-lock event. In most cases it was a loose wire or a low-level
misconfiguration (which I hope it is not! :-)).
CLKPLL_LL is never present in the interrupt mask, so yes, this cannot be
the source of interruption. Still interrupting artificially (while one
device is constantly sending packets, right?) will likely never give you
good packets - I guess. So for now, I'm sorry, but don't have a single
solution to your problem.
Maybe you have some additional information on your setup and device
configurations? Let me know if there's anything else I can help with.
Cheers,
Thomas
—
Reply to this email directly or view it on GitHub
https://github.com/thotro/arduino-dw1000/issues/42#issuecomment-140993383
.

Hi José,
yes, that's basically what I meant - maybe not an LDE error, but a tuning or OTP problem. Did you try with the default configuration (Channel 5, 16 MHz, ..., e.g. by not setting any mode explicitly) or even with other ones as well?
Which Arduino sketches do you use for testing? BasicSender/-Receiver?

I am using Basic sender/receiver, with default settings.  When i change
setings the chips behave differently, it triggers receive  interruptions
when i intentionally configure different baud rates between receiver and
sender ( same channel and PRF, different baud rate and preamble legth) . i
haven tested what happen when i do not pass any settings to the chip, but
it will be my next test. Thanks.
2015-09-17 9:51 GMT-03:00 Thomas Trojer<EMAIL_ADDRESS>
Hi José,
yes, that's basically what I meant - maybe not an LDE error, but a tuning
or OTP problem. Did you try with the default configuration (Channel 5, 16
MHz, ..., e.g. by not setting any mode explicitly) or even with other ones
as well?
Which Arduino sketches do you use for testing? BasicSender/-Receiver?
—
Reply to this email directly or view it on GitHub
https://github.com/thotro/arduino-dw1000/issues/42#issuecomment-141071653
.

I'm having a similar problem with the receiver using the adapters with the same setup.
Using leonardo for both sender and receiver.
Receiving corrupted data every 1-2 minutes.
Output from receiver:
Error receiving a message
Error data is ... Helll�
�y�y>i�P.�i�{�
Is this a hw issue? I might have weak connections from soldering...not sure though.

I have the same problem.
I have used Arduino Uno to BasicSender and ArduinoEthernet to BasicReceive.
I have modified the library to print the specific bit.
In praticular:
**when i send i print TXFRS_BIT and it's equal to 1 (it's ok, it means send done).
**when i receive i print LDEERR, RXFCE, RXPHE, RXRFSL and all are equal to 0 (no error) but the CLKPLL_LL is always equal to one.
Do you have any insight on this error?

Do you get to solve your problem? I have the same issue it's seems that the transmitter it's working well, but i can't recieve any data in the receiver module, i'm using Two arduino promini 16MHz @ 5V with level shifter.

+1 on this issue. I have the exact same problem than @nevercy89, @Joshua-Thompson, @maxicastle and @jesp007. My configuration is actually using a Teensy 3.2, it sends data without any problem, the BasicConnectivityTest is also working good, but I always receive corrupted data with BasicSender/BasicReceiver sketchs due to a CLKPLL_LL_BIT error.
Do you guys have any updates on this subject ?


1.2.0.CR1

With scss support

This needs to wait for the Windows fix: https://github.com/mvnpm/esbuild-java/pull/91


Support # for list definition

At the moment you have to do in (list) list, I'm just wondering if adding #(list) to define the list would be an issue?

I'd much rather utilize the # to add tags. Tags & smart lists are definitely the way to go imo

Agreed with @rkabrick! Tagging support would be great, and # is the most obvious way to go there.

I'll keep an eye on that

+1 for tag support. I tried it instinctively and was disappoint :(

+1 for tag support. Like previous commenter, also used it instinctively and also... :)

I agree this would be a great feature, but as far as I can tell Apple has not provided any way to manage tags on reminders through applescript. If anyone can prove me wrong, now or in the future, I'd happily look into it!


RUMM-2754: Create implementation of InternalLogger

What does this PR do?
Simple implementation of InternalLogger interface which forwards logs according to the target specified.
Task RUMM-2764 created to start using it in the codebase, not a part of SDK v2 goals.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1155 (cf0fddb) into feature/sdkv2 (d451d7e) will increase coverage by 0.03%.
The diff coverage is 92.59%.

@@                Coverage Diff                @@
##           feature/sdkv2    #1155      +/-   ##
=================================================
+ Coverage          82.28%   82.31%   +0.03%
=================================================
  Files                353      354       +1
  Lines              11796    11822      +26
  Branches            2007     2012       +5
=================================================
+ Hits                9706     9731      +25
- Misses              1465     1468       +3
+ Partials             625      623       -2

Impacted Files
Coverage Δ

...otlin/com/datadog/android/v2/api/InternalLogger.kt
100.00% <ø> (ø)

...n/com/datadog/android/v2/core/SdkInternalLogger.kt
92.31% <92.31%> (ø)

...in/com/datadog/android/core/internal/SdkFeature.kt
89.09% <100.00%> (ø)

...android/log/internal/logger/TelemetryLogHandler.kt
85.71% <0.00%> (-14.29%)
:arrow_down:

...src/main/kotlin/com/datadog/android/DatadogSite.kt
83.33% <0.00%> (-3.33%)
:arrow_down:

...android/log/internal/domain/DatadogLogGenerator.kt
94.59% <0.00%> (-0.68%)
:arrow_down:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
92.78% <0.00%> (-0.56%)
:arrow_down:

.../android/rum/internal/domain/scope/RumViewScope.kt
95.24% <0.00%> (ø)

...android/v2/core/internal/DatadogContextProvider.kt
81.54% <0.00%> (ø)

...droid/rum/tracking/FragmentViewTrackingStrategy.kt
75.00% <0.00%> (ø)

... and 2 more


Task - Can't mark as done task that user set to "Assigned to me"

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition: Login as user A on Web and user B on other environment (e.g. Desktop app or different browser);
Users A & B are members of same group DM.

Open http://staging.new.expensify.com/
As user B send a task into group DM without assignee
As user A open the same chat
Click on the same task
Click on Task header
Click on "Assign to me" user profile
Click on "Mark as Done"
As user B open same task report

Expected Result:
At step 7 Assigned task is successfully marked as done
At step 8 user B can see that this task is now assigned to user A
Actual Result:
At step 7 Assigned task is not "marked as done"
At step 8 user B still see that the task doesn't have an assignee
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/9c9a5447-1915-4cdf-9f9b-1cd8bb759238
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

@thienlnam Do we have anything like a clean up milestone for polish/bugs related to the tasks feature?

I've just been adding it to the Expensify Tasks project to keep track of bugs
Though this issue looks like a dupe of this https://github.com/Expensify/App/issues/20542
We essentially need the onyx failure to set an error on the reportAction


make  member of att.responsibility

From<EMAIL_ADDRESS>on May 15, 2012 11:07:06
The documentation for <change> mentions the @resp attribute, but the element isn't a member of att.responsibility, which contains @-resp.  This is a bug that should be fixed in the 2012 release.
Original issue: http://code.google.com/p/music-encoding/issues/detail?id=67

From<EMAIL_ADDRESS>on May 15, 2012 08:31:53
This doesn't have to be fixed for the next release, but the documentation definitely should be.  <change> should also be made a member of att.datable.  This, in turn, brings up issues with re: to att.datable.  It should contain an "isodate" (or similarly named) attribute, which replaces @-reg defined on <date>.  "@when" (as in TEI) is not a good name, since "when" is used for alignment purposes.

From<EMAIL_ADDRESS>on May 15, 2012 08:32:27
Labels: -Priority-High Priority-Medium

From<EMAIL_ADDRESS>on June 21, 2012 05:41:50
Labels: -Type-Enhancement -Priority-Medium Type-Bug Priority-High

From<EMAIL_ADDRESS>on June 22, 2012 10:51:57
Status: Started

From<EMAIL_ADDRESS>on June 27, 2012 11:35:35
This issue was closed by revision r577 .
Status: Fixed


python-ftputil: 3.3.0-3 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository python-ftputil to 3.3.0-3:

upstream repository: http://hg.sschwarzer.net/ftputil
release repository: https://github.com/asmodehn/ftputil-rosrelease.git
distro file: indigo/distribution.yaml
bloom version: 0.5.26
previous version for package: null

Just renaming ftputil -> python-ftputil to have the same name as kinetic and make the upgrade easy.
Not sure if I should also remove the old ftputil entry here ?


Celery configuration when configurations have been split over multiple files.

Hi
I've hit a wall attempting to get Celery (3.1.14) to operate with Django 1.7 and django-configurations (0.8) when the configuration classes have been split across multiple files.
By way of example, the https://github.com/pydanny/cookiecutter-django/tree/master/{{cookiecutter.repo_name}}/{{cookiecutter.repo_name}} repo has split the project structure as below:
project_name/
    config/
        __init__.py
        common.py
        local.py
    manage.py

I've put a file celery.py in the config directory per the Celery and django-configuration instructions.
However, no matter what combination of settings/paths/locations for the celery.py or import statements I try -- I constantly get an ImportError saying it's ImproperlyConfigured.
The only time I don't get that error is if I place the from .celery import app as celery_app above the common and local import lines in the config/__init__.py directory in which case the error regards not having a SECRET_KEY which indicates Celery is not loading the configuration/settings properly.
The environment variables in this case are: DJANGO_SETTINGS_ENVIRONMENT=config and DJANGO_CONFIGURATION=Local.
A Gist with summary file info & the error is available here: https://gist.github.com/gciding/6935ee400f903ffd4bdc
Do you have any ideas on what the issue could be or where I should look to fix it (without having to put the files back into a single settings.py file again)?
Cheers
Goran

This is unrelated to django-configurations, the way the cookiecutter template imports the configurations classes inside the config/__init__.py was part of the template ever since the settings were refactored. See https://github.com/pydanny/cookiecutter-django/commit/81576069f86087198ef2b6fb87c5f6f1f1e09cee#diff-1 for the original commit that changed it and that it matches what @alb3rto wrote above.


added info about openSUSE package installation and added listing of output zip file

as $Subject says. only updated the readme

now added support to only list the filename of the zip that would be created.
pkg2zip -l package.pkg

Thanks!


vmwgfx resizing doesn't work

Running Virtualbox 6.1 with VMSVGA driver, I am unable to resize the guest window and have wlroots resize. This happens in Cage, but I have confirmed that Cage never gets a notification on the resize, so I think this is wlroots responsibility.
Note that wlroots already gets the DRM size correctly if you resize the window and restart the wlroots client. This means that I think we just aren't getting the notification of when resize happens.
wlroots should be able to listen to the VMW_UPDATE_LAYOUT and set the preferred mode based off of that. It should work similarly to how X11 resizing works and I think this is how GNOME/KDE wayland implementations handle it.

Sorry, we don't add support for driver-specific features.


Todo:

I want to do the last task

[ ] 5. Possibility to make the ticket names to ticket-ASCENDING_NUMBER
https://github.com/elbkr/ticket-bot/blob/97f51af779be4bcae49584e2af5f8cf7b699b0ba/todo#L5

Lmk if anyone have already started?

Hi, no one did it yet. Thanks ^^

I'm a bit busy because of my college exam I'll try tomorrow.
Ig I only need to change here or anywhere else too?
https://github.com/elbkr/ticket-bot/blob/97f51af779be4bcae49584e2af5f8cf7b699b0ba/src/events/interactions/buttonPress.js#L34

Also what about using winston instead of chalk

I'm a bit busy because of my college exam I'll try tomorrow.
Ig I only need to change here or anywhere else too?
https://github.com/elbkr/ticket-bot/blob/97f51af779be4bcae49584e2af5f8cf7b699b0ba/src/events/interactions/buttonPress.js#L34

Yes, but you have to get the guild tickets count, and also make a command to set the type: ascending numbers or username

Also what about using winston instead of chalk

I’ll check it later

I'm a bit busy because of my college exam I'll try tomorrow.
Ig I only need to change here or anywhere else too?
https://github.com/elbkr/ticket-bot/blob/97f51af779be4bcae49584e2af5f8cf7b699b0ba/src/events/interactions/buttonPress.js#L34

Yes, but you have to get the guild tickets count, and also make a command to set the type: ascending numbers or username

Ok sure

but you have to get the guild tickets count,

Will be doing it by checking only active tickets, or should I consider closed tickets also?

Consider all tickets

If we consider all tickets then we need to save the current highest ticket number in database also if there is no active ticket channels all previous were closed then making a new channel named eg. Ticket-100 doesn't makes sense. I prefer considering only opened tickets but if u want me to consider all then np I'll do it.
Need some time and due to clg and exam I'm not getting much time.

No need to, we can just grt the current tickets count before creating the new doc and new ticket.

Also what about using winston instead of chalk

Winston is for logging, I use chalk for the text colors

Also what about using winston instead of chalk

Winston is for logging, I use chalk for the text colors

winston will do all by itself you just need to assign a color to respective log like
Logger.debug should show white
Logger.info blue like this


[Typo] [docs]  Modify README.md
Change ‘kafka_default_offset’ to ‘kafka_default_offsets’.

Proposed changes
Issue Number: close #xxx

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


Stage industry-facing virtual sites example

Description
@lilyminium here's what I promised a while back. I'm not sure this this land in the repo long-term.
Is there a better way to present this than showing what XML files condense out from each SMILES string?

I lost track of the wording, but yesterday @j-wags suggested it's better to have this merged in than not. I'm going to kick the tires on this and aim to merge it more or less as-is, shipping the notebook and XMLs.

Oh, it's actually already online in some form 🫠 https://docs.openforcefield.org/en/latest/examples/openforcefield/openff-interchange/virtual_sites/virtual_sites.html

A consequence of https://github.com/openforcefield/openff-interchange/pull/947 is that the water molecule with this OFFXML gets both 4- and 5-site parameters. (That makes sense, there isn't otherwise a way to distinguish which water model should be applied.) Previously, only 4-site parameters were applied by nature of them showing up earlier in the force field.
I've removed the 5-site parameters from the notebook, which was already getting around this problem by loading 5-site water externally (ForceField("tip5p.offxml")).


neon: implemenation of dot_lane

This one was pretty straightforward, it's based on the vdot implementation.
(CC @tlively @ngzhian)

Nice, thanks :)


Make JsonPatch netstandard2.0

Fixes https://github.com/aspnet/AspNetCore/issues/9812

Merging this in manually, as the tests have actually passed but the GitHub UI shows that they haven't:


Return empty string instead of nil for missing thumbnail

Fixes https://github.com/rt2zz/react-native-contacts/issues/15

cc @morenoh149
I am not sure why @trabianmatt was getting this error, but if this solves it I am happy with change

It's objective-c so I figured @rt2zz would handle it. I'm happy to merge it if it solves @trabianmatt concerns. This is so that it properly conforms to the api (readme)?

Ok so I glanced over this too quickly before. A potentially better approach would be to actually not set the object at all, but nbd. +1 Thanks @trabianmatt


Question

For those of us that can't get alt-1 to work, do you have a web-based solution that can show the crowdsourced VOS instead? That would be nice... (Or a FC in game...)

Not currently. I've been trying to get the RS.Wiki involved and several Discord channels (mostly their bots) to bring back role pings for specific hours and to let people check the wiki for the current VoS since we've had data for the large majority of hours within the first few minutes of each hour for a few weeks now. That way people can do a quick /wiki voice of seren to check.
When we hit a large enough scale I can make some changes so that visiting https://nadyanayme.github.io/VoiceOfSeren/dist/index.html will work without erroring out if Alt1 isn't found. But if everyone uses that instead of the app the app becomes less reliable so it's a balancing act of being sure enough people are contributing before providing an easier avenue to not contribute but still benefit.

I've created a bot with a few commands and have quickly written something to incorporate this into my bot. I could add a message to the bot to encourage users to download your alt1 extension to enable better crowd sourcing. Are you on board with that idea?

If you're making use of the API - yes - please encourage users to actually install/use the plugin as well. While we absolutely want people to be able to benefit from it via Discord bots - it does mean an increase in leechers and a potential decline of contributors which makes the app less reliable for everyone.
I still make an effort to update the VoS when it isn't a total inconvenience for me but since I refuse to add analytics I'm not sure how many other contributors there are currently.

Base Alt 1 has a D&D notification that can be viewed without the app here. Would you be willing to work with them to try to get the crowdsourced VoS integrated into it? (One of its strengths is being able to display the current VoS directly in the titlebar)

Base Alt 1 has a D&D notification that can be viewed without the app here. Would you be willing to work with them to try to get the crowdsourced VoS integrated into it? (One of its strengths is being able to display the current VoS directly in the titlebar)

Statusdaemon support is being purposefully left out. Apps are capable of updating the titlebar when closed - but due to how data is gathered requires the app to be open forcing people to either choose between opening+closing the app constantly or just minifying it and leaving it open is an intentional decision meant to increase the number of contributors. If you leave the app open the current VoS will display directly in the titlebar. It's only if you close the app that it will stop receiving updates.
Skillbert is always free to consume the crowdsourced API for the D&D notifications app if he so wishes but I think the unreliability of it not coming from Jagex makes him a bit adverse to it as anytime it is wrong people would bug him instead of bugging me about it when he has no control over things.


Add TWC3 support for Tesla vehicles

This is an experiment.
Ich habe ihm evcc auf einem Pi installier. Wie Upgrade ich denn da am besten auf den PR? Kann ich bei apt --only-upgrade install -y evcc den PR als Version irgendwie mitgeben, oder muss ich die geänderten Dateien irgendwo hinkopieren?

Hi!
I installed a Raspberry Pi to test it now. Have done a nightly installation but how do I add the TWC? I added the following:
chargers:

type: tesla
uri: http://<IP_ADDRESS>

You need to compile the PR. Its not in the nightly.

Hi!
I downloaded the source zip file and installed golfing and node. The compile goes quite well for some time and then I get the following error:
evccadmin@evcc:~/evcctwc3/evcc-feature-twc3 $ make
Version: 2022-12-15_22:58:05
go build -v -tags=release -ldflags='-X github.com/evcc-io/evcc/server.Version= -X github.com/evcc-io/evcc/server.Commit= -s -w'
main.go:4:2: package embed is not in GOROOT (/usr/lib/go-1.15/src/embed)
tools.go:6:2: import "github.com/dmarkham/enumer" is a program, not an importable package
tools.go:7:2: import "github.com/golang/mock/mockgen" is a program, not an importable package
../../go/pkg/mod/github.com/mattn/go-runewidth@v0.0.14/runewidth.go:7:2: found packages uniseg (doc.go) and main (gen_breaktest.go) in<EMAIL_ADDRESS>../../go/pkg/mod/github.com/evcc-io/eebus@v0.0.0-20221023111026-e3c9e4d1f3c8/cert/cert.go:16:2: package io/fs is not in GOROOT (/usr/lib/go-1.15/src/io/fs)
make: *** [Makefile:72: build] Error 1

Came a bit further and now when trying to configure cvcc.yaml I get the following when trying to start:
evccadmin@evcc:~/evcctwc3/evcc-feature-twc3 $ ./evcc charger
[main  ] INFO 2022/12/16 00:10:29 evcc
[main  ] INFO 2022/12/16 00:10:29 using config file: /home/evccadmin/evcctwc3/evcc-feature-twc3/evcc.yaml
[main  ] FATAL 2022/12/16 00:10:29 cannot create charger 'TWC3': cannot create charger 'tesla': missing access and/or refresh token, use evcc token to create
My entry in the yaml file for TWC3 is:
chargers:

type: tesla
uri: http://<IP_ADDRESS>
name: TWC3

I also tried adding the VIN and the two token entries from the car but that gave me an error saying not valid entries for "chargers:"

Most of the errors are not related to this PR and need be resolved first. Please use discussions.

This is the message I get from ./evcc charger:

Could you do a
 ./evcc charger --log trace

And please, format uour posts.
 You can git pull for the update.

 Auto hängt dran, aber schläft. Jetzt muss ich mal weiter schauen. Update folgt.

This is the latest start, thought I share it since it is showing warnings on charger.
evccadmin@evcc:~/evcctwc3/evcc-feature-twc3 $ ./evcc
[main  ] INFO 2022/12/16 11:30:33 evcc
[main  ] INFO 2022/12/16 11:30:33 using config file: /home/evccadmin/evcctwc3/evcc-feature-twc3/evcc.yaml
[main  ] INFO 2022/12/16 11:30:33 starting ui and api at :7070
[lp-1  ] WARN 2022/12/16 11:30:38 poll interval '10m0s' is lower than 1h0m0s and may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1  ] WARN 2022/12/16 11:30:38 Configuring soc.target at loadpoint is deprecated and must be applied per vehicle
[semp  ] WARN 2022/12/16 11:30:38 SEMP_BASE_URL unspecified, using http://<IP_ADDRESS>:7070 instead
[site  ] INFO 2022/12/16 11:30:38 site config:
[site  ] INFO 2022/12/16 11:30:38   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2022/12/16 11:30:38     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2022/12/16 11:30:38     pv 1:      power ✓ energy ✓ currents ✓
[site  ] INFO 2022/12/16 11:30:38     battery 1: power ✓ energy ✗ currents ✗ soc ✓
[site  ] INFO 2022/12/16 11:30:38   vehicles:
[site  ] INFO 2022/12/16 11:30:38     vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✗
[lp-1  ] INFO 2022/12/16 11:30:38 loadpoint 1:
[lp-1  ] INFO 2022/12/16 11:30:38   mode:        pv
[lp-1  ] INFO 2022/12/16 11:30:38   charger:     power ✗ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2022/12/16 11:30:38   meters:      charge ✗
[lp-1  ] INFO 2022/12/16 11:30:38 vehicle updated: unknown -> TM3
[site  ] WARN 2022/12/16 11:30:38 pv 0 power: -5721W is negative - check configuration if sign is correct
[lp-1  ] INFO 2022/12/16 11:30:39 car connected
[lp-1  ] INFO 2022/12/16 11:30:39 start charging ->
[lp-1  ] WARN 2022/12/16 11:30:39 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:30:48 pv 0 power: -5610W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:30:48 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:30:58 pv 0 power: -5415W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:30:58 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:31:02 pv 0 power: -5414W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:31:03 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:31:08 pv 0 power: -5291W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:31:10 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:31:18 pv 0 power: -5283W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:31:18 charger logic error: disabled but charging
[site  ] WARN 2022/12/16 11:31:28 pv 0 power: -5219W is negative - check configuration if sign is correct
[lp-1  ] WARN 2022/12/16 11:31:28 charger logic error: disabled but charging

charger logic error: disabled but charging

That part is actually implemented. Again: add logging (tesla: trace) to see why the Tesla doesn't react.

pv 0 power: -5219W is negative - check configuration if sign is correct

...and please fix your config!

Added the log trace, this is one that I captured:
[tesla ] TRACE 2022/12/16 12:13:51 GET https://owner-api.teslamotors.com/api/1/vehicles/xxxxxxxxxxxxxxxxxx/data_request/charge_state
[tesla ] TRACE 2022/12/16 12:13:51 {"response":null,"error":"vehicle unavailable: {:error=>\"vehicle unavailable:\"}","error_description":""}
[lp-1  ] ERROR 2022/12/16 12:13:51 charger: 408 Request Timeout

Regarding fixing my config. I am trying to figure it out. Just started using lvcc and trying to learn all parameters and what to have configured. Sorry

It seems the car is a sleep when I get the error above. Once I start the app on my phone and wake the car up it connects and shows values.
I then get following:
[lp-1  ] ERROR 2022/12/16 12:17:01 vehicle odometer: 408 Request Timeout

Sorted my config now :-)

Added the log trace, this is one that I captured

Could you retry running evcc with log: trace when the vehicle is not asleep?

Changed the log to trace and I do not get any errors.
I can start charging when moving to Min+PV and once I put it back to PV it stops (I have an empty battery and very little solar power today).
What I cannot do is change the target charge and sometimes the SoC on the car in the UI shows more charge than it is.

Would this TWC3 implementation work with non-Tesla vehicles?

 The car is now connected to the charger but not charging. I hope to have good solar production today since the prediction is clear blue sky.

Hi!
 It seems as if it's working in principle. I've made two small changes to reduce the number of api calls. So what's missing now?

I will install the latest version.
Since I am quite new to EVCC I can't say if anything is missing. What I don't get is that the car is set to charge limit 90% and when I change the limit in EVCC it does not change on the car. But maybe it is not supposed to and be changed somewhere else.

By the way, it just came to my mind that I don't think the refresh and access tokens are needed. Since when I opened the ,IP>/api/1/vitals link it showed me the data that is shown in the logs of EVCC.

What I don't get is that the car is set to charge limit 90% and when I change the limit in EVCC it does not change on the car. But maybe it is not supposed to

It is not supposed to, at least in VW group cars it doesn't

Just installed the new version and I now get this in the log:
ERROR 2022/12/18 12:20:43 version check failed: Malformed version:
I have log trace but nothing is coming out in the logs. It is dead quiet...

What I don't get is that the car is set to charge limit 90% and when I change the limit in EVCC it does not change on the car. But maybe it is not supposed to

It is not supposed to, at least in VW group cars it doesn't

Ah ok, thanks for letting me know. Now I don't have to think about it.

So- its working?

It seems to work apart from the log message
[main  ] ERROR 2022/12/18 12:22:19 version check failed: Malformed version:
In the UI I have this:

@andig I have to say thank you as well for the prompt actions and super fast work!! Just became a sponsor :-)

Thank you very much! Please email<EMAIL_ADDRESS>for the friends and family tokens!

Since we now have a semi-working config, we'll need to do two things:

get more testers (already asked in discussions)
rethink how to configure the Tesla

I'd suggest that for the second point we do:

rename the charger to TWC3
remove the vehicle

Instead, check the loadpoint for the active vehicle and- if that vehicle is a tesla- you that config instead.

@mbrihed you'll have to update your config like this:
chargers:
  - type: twc3
    uri: http://<twc>

Then either wait until the loadpoint recognises the Tesla connected to it or configure it as default vehicle for the loadpoint.

@mbrihed you'll have to update your config like this:
chargers:
  - type: twc3
    uri: http://<twc>

Then either wait until the loadpoint recognises the Tesla connected to it or configure it as default vehicle for the loadpoint.

@andig if I remove (hash out) the tokes, access and refresh token and VIN I get the following failure:
[main  ] INFO 2022/12/18 18:15:55 evcc
[main  ] INFO 2022/12/18 18:15:55 using config file: /home/evccadmin/evcc.yaml
[main  ] FATAL 2022/12/18 18:15:57 cannot create charger 'twc3': cannot create charger 'tesla': missing access and/or refresh token, use `evcc token` to create
[main  ] FATAL 2022/12/18 18:15:57 will attempt restart in: 5m0s

Is there a new version I should download?

Since we now have a semi-working config, we'll need to do two things:

get more testers (already asked in discussions)
rethink how to configure the Tesla

I'd suggest that for the second point we do:

rename the charger to TWC3
remove the vehicle

Instead, check the loadpoint for the active vehicle and- if that vehicle is a tesla- you that config instead.

I tend to agree, just one question; when you say remove the vehicle I assume you mean from the charger part in the config?
To me that would make sense and just have a very simple entry for the TWC3 and treat it as a dumb charger since it does not bring any smartness to it. It is mainly the Tesla Car that controls the behavior (to my knowledge).
The TWC3 when you configure it you just specify the max load and power (AMPs) and the wifi and that is kind of all you do to it. (that has to be done through a different access as well since you need to cut the power and connect to a TWC3 AP that it set up during the first 30 min.

when you say remove the vehicle I assume you mean from the charger part in the config?

Yes. As before you need to
git pull

and compile again.

Installed the latest version and changed my config to use:
chargers:
- type: twc3
  uri: http://<IP_ADDRESS>/
  name: twc3

Starts as before and so far looking good.
I am getting this message every time I start and trying to figure out where it comes from. It started on the version before this one.
[main  ] ERROR 2022/12/19 07:40:27 version check failed: Malformed version:

I've added more diagnostic for that message, but you can safely ignore it.

Thanks, I will ignore it :-)
I can post in Home Assistant forums to see if there are people there that wants to test unless there were people that are already testing.

@andig jetzt müsstest du nur noch die Arbeit von vor 1 (oder waren es schon 2) Jahre(n) vorholen und den TWC Gen 2 fertig implementieren ;-)

Hallo,
wollte auch testen, bekomme aber  folgenden Fehler :
main  ] FATAL 2022/12/31 11:14:14 cannot create charger 'test twc3': cannot create charger 'template': template not found: twc3
was mache ich falsch?

Danke füt schnelle Antwort
Jetzt kommt:
mein evcc.yaml
`chargers:

name: test twc3
type: template
template: twc3
host: 192.168.x.x
tokens:
access:
refresh:
vin: XP7YG

`
[main  ] FATAL 2022/12/31 11:47:22 cannot create charger 'test twc3': cannot create charger 'template': invalid key: tokens
tokens sind aber richtig

tokens sind aber richtig

Nein, ist es nicht: https://docs.evcc.io/docs/devices/chargers#tesla-twc3

Das habe ich erstes probiert da kommt:
main  ] FATAL 2022/12/31 15:07:47 missing loadpoints

Mach doch bitte erstmal eine ganz normale Konfiguration mit
evcc configure

Da das nix mit dem TWC zu tun hat bitte neues Thema!

Ist die Integration mittlerweile in dem neusten stable release integriert ? :)

Yes it is included in the latest stable version,

On Feb 5, 2023, at 12:57, peezy45 @.***> wrote:
Ist die Integration mittlerweile in dem neusten stable release integriert ? :)
—
Reply to this email directly, view it on GitHub https://github.com/evcc-io/evcc/pull/5341#issuecomment-1417767006, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJINVIARGA5G5ZKP3DGDG3TWV6PULANCNFSM6AAAAAASRWE2KU.
You are receiving this because you were mentioned.

Short question: Is the combination TWC3 and non Tesla car (in my case VW Hybrid) possible?

No, twc is not controllable, Tesla car is

Ok I try to understand: TWC3 is not controllable, my VW Hybrid is controllable. Is there any chance to apply this in evcc?

We won't put more functionality into undocumented vehicle Api, unfortunately no.


Timeout error after approximately 10 seconds when running on macOS

Description
I am encountering a timeout error when running the following code on macOS. The error occurs approximately 10 seconds after the request is made. I would like to know if there is a way to configure or extend the timeout setting to handle longer response times.
Code to Reproduce
import traceback
import time
from ollama import chat

t1 = time.time()
try:
    # chat = Client(timeout=60).chat
    response = chat(model='llama3', messages=[
      {
        'role': 'user',
        'content': 'why the color of sky is blue?',
      },
    ])
    print(response['message']['content'])
except Exception as e:
    print("error", e)
    traceback.print_exc()

t2 = time.time()
print("cost ", t2-t1)

Error Message
error
cost  10.008436918258667
Traceback (most recent call last):
  File "/var/folders/lz/9_t5yfyj6cg79jmhn26qrlcr0000gn/T/ipykernel_22684/1004213980.py", line 10, in <module>
    response = chat(model='llama3', messages=[
  File "/Users/myp/miniconda3/envs/py38/lib/python3.8/site-packages/ollama/_client.py", line 180, in chat
    return self._request_stream(
  File "/Users/myp/miniconda3/envs/py38/lib/python3.8/site-packages/ollama/_client.py", line 98, in _request_stream
    return self._stream(*args, **kwargs) if stream else self._request(*args, **kwargs).json()
  File "/Users/myp/miniconda3/envs/py38/lib/python3.8/site-packages/ollama/_client.py", line 74, in _request
    raise ResponseError(e.response.text, e.response.status_code) from None
ollama._types.ResponseError

The only way to configure the timeout seems to be passing the timeout param here.
A walkaround can be initialising a new Client with a timeout param, and use the new client to call apis.
Code to Reproduce
import traceback
import time
# from ollama import chat
from ollama import Client

t1 = time.time()
try:
    chat = Client(timeout=1).chat # new client with timeout 1s
    response = chat(model='gemma2:2b', messages=[
      {
        'role': 'user',
        'content': 'why the color of sky is blue?',
      },
    ])
    print(response['message']['content'])
except Exception as e:
    print("error", e)
    traceback.print_exc()

t2 = time.time()
print("cost ", t2-t1)

Output
httpx.ReadTimeout: timed out
cost  1.0301549434661865

There’s an example in the README for Custom Client.


Game is in a Frozen Data State (There are NO FOLDERS in scripts)

Issue Description:
Note: If this bug occurs in a modpack, please report this to the modpack author. Otherwise, delete this line and add your description here. If you are using an unnofficial version of Minetweaker or Crafttweaker please report it to the person who gave you the version. Also please look at the other issues to make sure that you are not creating a duplicate.
Game is in a Frozen Data State, Causing Worlds to Not Load.
NOTE: There are NO FOLDERS in scripts.
What happens:
Game is in a Frozen Data State, Causing Worlds to Not Load.
What you expected to happen:
The Game Not to be in a Frozen Data State.
Script used (Please Pastebin or gist your script, posting an unpasted or ungist'd script will automatically close this issue):
Partial fml-client-latest.log: https://gist.githubusercontent.com/Wealthyturtle/7aaef6cf94dd44dfc7fea5ece82a2ddc/raw/13e1869b5d4c66ac795290089d58ea867964e40c/Partial%2520fml-client-latest.log
Minetweaker.log file (Please Pastebin or gist your file, posting an unpasted or ungist'd file will automatically close this issue):
Minetweaker.log: https://gist.githubusercontent.com/Wealthyturtle/a387074368895ea27d094b3c1aa501fb/raw/eb9de7191277ab2cae13aa34645a1776257023c0/Minetweaker.log
Affected Versions (Do not use "latest"):

Minecraft: 1.7.10
Forge: <IP_ADDRESS>4
Crafttweaker: 1.7.10-3.0.13

Your most recent log file where the issue was present:
latest.log:
https://gist.githubusercontent.com/Wealthyturtle/c0ba8b209e331a2c5f6cc9713974cef3/raw/852dd49d0e352efd818e62760c2406f7be1731a2/latest.log

1.7.10 is no longer supported.


feat(FX-3109): tag page

The type of this PR is: Feature
Jira ticket: FX-3109
This PR resolves []
Description

tag/:slug route render Tag page
Added artworks grid, filters modal and sticky filter bar
Added tests for the page

Demo
https://user-images.githubusercontent.com/56556580/127502537-95079861-e624-460f-85cd-20b45009fd87.mov
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Tag scene

iOS user-facing changes

Android user-facing changes

Dev changes

This PR contains the following changes:

Cross-platform user-facing changes (Tag scene)

  Generated by :no_entry_sign: dangerJS against 37736c91e11a33bd8a1f94ac467d453d01c6a704


edge-fields (foreign-key columns) do not accept default value

Hi there.
The default value don't work,  I don't know what I'm doing wrong.
Current Behavior 😯
https://github.com/wonderfate/ent-test-edges/blob/5cfbce566bdc70d00cdd0cc395bbcdb63a250e60/ent/schema/pet.go#L19
https://github.com/wonderfate/ent-test-edges/blob/5cfbce566bdc70d00cdd0cc395bbcdb63a250e60/ent/migrate/schema.go#L14

Expected Behavior 🤔

Hey @wonderfate and thanks for raising this issue.
The Default value 0 is not valid for foreign-key columns as it violates the foreign-key constraint. An improvement we can add here is to add check/report this in the codegen phase, but not sure it's really needed.

e.g.  The pets table insert some info when pets at the pet shop. Update the perts table user_id after the customer buys pet

OK. Setting this field as Optional is the way to go (NULLable in the database). This way you can query all pets with/out owners, etc.

Actually I don't want to set to NULL in the database, just want to set DEFAULT 0 NOT NULL  (It might be like you said it violates the foreign-key constraint)
Do you have any suggestions?

It looks like you want to make it optional on creation, but the edge is Required. These 2 are mutually exclusive, because 0 ID is not allowed as DEFAULT value. If it's a Required() edge it must be set on the creation with a real value, not 0 because again, it violates the foreign-key constraint.

I think we can close this. If you still need help or want to discuss this, I'm available on our Discord server for any questions.


Update chief-executive-officer-ceo.md

This PR fixes...
Remove the example below. Then, add the related issue after the hash. Lastly, tell us what problems this PR is meant to solve.
Ex: This PR fixes #999. We didn't have a unicorn, so we went to the unicorn store and got one.
What I did...
Remove the example below. Then, list out the work you have done, in bullet form.
Ex:

one
two

How to test...
In a list format, tell us how to test this PR.
Ex:

Navigate to https://example.com/cats
Click on magic button
See coolest cat

I learned...
Did you run into any interesting issues while making this PR? If you learned anything you would like to share, we'd love to know! Even if it is a fun fact or GIF!

This is looking pretty good so far, @A482677. Please be sure to fill out the pull request completely so we can know more about your changes. To edit your pull request, click the kebab menu and then the "edit" link in the grey box near your pull request (I've attached a screenshot below).

Please then edit the pull request with your changes in each section.


How to fix this backend company-tabnine error?

Company: backend company-tabnine error "Symbol’s function definition is void: comp" with args (prefix)

Already fixed, please update on next release :)
On Mon, Nov 12, 2018 at 12:04 AM Lea Forest<EMAIL_ADDRESS>wrote:

Company: backend company-tabnine error "Symbol’s function definition is
void: comp" with args (prefix)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TommyX12/company-tabnine/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHcqCoHccJviIjnSQ0Y8lhd1lgO6gCWwks5uuQFdgaJpZM4YY9u-
.

It's because I fixed it but melpa didn't build the next release yet. Wait
for that to happen (should be in a few hours) and update.
On Mon, Nov 12, 2018 at 12:27 AM Lea Forest<EMAIL_ADDRESS>wrote:

I'm glad to get your quick reply, but it doesn't seem to work for me. Is
there anything that needs attention
?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/TommyX12/company-tabnine/issues/1#issuecomment-437760904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHcqCsnr0XwQqF3kIwjAqEPQKeeTVECyks5uuQbSgaJpZM4YY9u-
.

The fix is in the latest build. Please update :)

OK，ths！


Added sigint signal handler to glcli's hsmd command.

#205

Good addition, but I wonder if it works. I thought that during FFI calls the signal handlers installed by the python runtime would not be called?

I think you might be thinking of the behavior of the replaced run_in_foreground call, which blocks the thread and doesn't return control. I changed it to run_in_thread to allow the current thread to wait for signals and close on sigint.
Instructions for testing:
-Comment out the scheduler's maybe_upgrade call since it's not relevant to this PR and would causes my glcli hsmd to crash
-Rebuild gl-client-py maturin build --strip --out ./dist
-Reinstall gl-client-py whl pip install ./dist/gl_client-0.1.9-cp37-abi3-manylinux_2_31_x86_64.whl --force-reinstall
-poetry build the cli
-Reinstall pip install dist/glcli-0.1.8-py3-none-any.whl --force-reinstall
-Call glcli hsmd

That's what I get for reviewing half asleep. Good job :+1:
ACK https://github.com/Blockstream/greenlight/pull/278/commits/c10d8631eb5641b258150909ddf5863c1174eda7


Adding a contract doesn't add to flow.json

When we use the flow accounts add-contract command we don't alter the flow.json reflecting the deployment. Which is a problem when we are doing imports as they won't get resolved due to contracts not being configured in flow.json.
This might be something we could change, but we need to think if there are any downsides.
cc @DylanTinianov

@sideninja if this functionality exists, then should there also be a ticket for remove contract?

@chasefleming very good point. If we add to flow.json then we should remove as well.

@sideninja Created a ticket for it: https://github.com/onflow/flow-cli/issues/1025


What does base_size in AnchorGenerator means?

Hi! I'm new to object detection and I'm stuck with some basic concepts. What does base_size in AnchorGenerator means? What's its relationship with the actual size of anchor boxes on the input image?  Please help me out. Thanks!

The actual size is base_size * scale, you may refer to the code.


Remove slf4j-impl (#6364)

Description
Add a description of your PR here.
Fix logging dependencies in pinot-spi #6364
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes
If you have tagged this as either backward-incompat or release-notes,
you MUST add text here that you would like to see appear in release notes of the
next release.
If you have a series of commits adding or enabling a feature, then
add this section only in final commit that marks the feature completed.
Refer to earlier release notes to see examples of text
Documentation
If you have introduced a new feature or configuration, please add it to the documentation as well.
See https://docs.pinot.apache.org/developers/developers-and-contributors/update-document

dependency tree(mvn -pl pinot-spi dependency:tree) with slf4j-api
[INFO] org.apache.pinot:pinot-spi:jar:0.7.0-SNAPSHOT
[INFO] +- commons-configuration:commons-configuration:jar:1.10:compile
[INFO] +- commons-codec:commons-codec:jar:1.6:compile
[INFO] +- commons-io:commons-io:jar:2.4:compile
[INFO] +- commons-lang:commons-lang:jar:2.6:compile
[INFO] +- commons-logging:commons-logging:jar:1.2:compile
[INFO] +- org.apache.commons:commons-lang3:jar:3.5:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- com.google.guava:guava:jar:20.0:compile
[INFO] +- com.google.code.findbugs:jsr305:jar:3.0.0:compile
[INFO] +- org.slf4j:slf4j-api:jar:1.7.25:compile
[INFO] +- com.lmax:disruptor:jar:3.3.4:compile
[INFO] +- org.apache.logging.log4j:log4j-1.2-api:jar:2.11.2:compile
[INFO] |  +- org.apache.logging.log4j:log4j-api:jar:2.11.2:compile
[INFO] |  - org.apache.logging.log4j:log4j-core:jar:2.11.2:compile
[INFO] +- joda-time:joda-time:jar:2.10.5:compile
[INFO] +- com.fasterxml.jackson.core:jackson-annotations:jar:2.10.0:compile
[INFO] +- org.yaml:snakeyaml:jar:1.16:compile
[INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.10.0:compile
[INFO] |  - com.fasterxml.jackson.core:jackson-core:jar:2.10.0:compile
[INFO] +- org.apache.avro:avro:jar:1.7.6:compile
[INFO] |  +- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile
[INFO] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile
[INFO] |  +- com.thoughtworks.paranamer:paranamer:jar:2.8:compile
[INFO] |  +- org.xerial.snappy:snappy-java:jar:<IP_ADDRESS>:compile
[INFO] |  - org.apache.commons:commons-compress:jar:1.20:compile
[INFO] +- org.codehaus.groovy:groovy-all:jar:2.4.21:compile
[INFO] +- org.testng:testng:jar:6.11:test
[INFO] |  - com.beust:jcommander:jar:1.64:test
[INFO] - org.reflections:reflections:jar:0.9.11:compile
[INFO]    - org.javassist:javassist:jar:3.19.0-GA:compile

Codecov Report

Merging #6703 (ff3b370) into master (1beaab5) will decrease coverage by 0.56%.
The diff coverage is 62.64%.

@@            Coverage Diff             @@
##           master    #6703      +/-   ##
==========================================
- Coverage   66.44%   65.87%   -0.57%
==========================================
  Files        1075     1391     +316
  Lines       54773    67583   +12810
  Branches     8168     9794    +1626
==========================================
+ Hits        36396    44523    +8127
- Misses      15700    19880    +4180
- Partials     2677     3180     +503

Flag
Coverage Δ

unittests
65.87% <62.64%> (?)

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

Impacted Files
Coverage Δ

...e/pinot/broker/api/resources/PinotBrokerDebug.java
0.00% <0.00%> (-79.32%)
:arrow_down:

...pinot/broker/api/resources/PinotClientRequest.java
0.00% <0.00%> (-27.28%)
:arrow_down:

...ot/broker/broker/AllowAllAccessControlFactory.java
71.42% <ø> (-28.58%)
:arrow_down:

.../helix/BrokerUserDefinedMessageHandlerFactory.java
33.96% <0.00%> (-32.71%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ava/org/apache/pinot/client/AbstractResultSet.java
66.66% <ø> (+9.52%)
:arrow_up:

...n/java/org/apache/pinot/client/BrokerResponse.java
100.00% <ø> (ø)

.../main/java/org/apache/pinot/client/Connection.java
35.55% <ø> (-13.29%)
:arrow_down:

...org/apache/pinot/client/DynamicBrokerSelector.java
82.85% <ø> (+10.12%)
:arrow_up:

...n/java/org/apache/pinot/client/ExecutionStats.java
68.88% <ø> (ø)

... and 1277 more

Continue to review full report at Codecov.

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

Closing this PR.

Hi @KKcorps - why was this closed? Removing direct dependencies on slf4j-impl in lower-level jars is a good thing, usually. Or did this get covered by a different PR?

@kkrugler I closed it for inactivity. I am not sure if this change is needed. Opening it again  for review.

@KKcorps - A jar that has a main() method that's used from the command line needs a logging implementation. Everything else should only be using the slf4j-api. Otherwise (e.g. with the Hadoop segment building workflow, which uses various Pinot jars) there can be logging implementation collisions. I made a run at fixing this up, but it got very complicated due to other 3rd party libraries used by Pinot pulling in their own logging implementations, which necessitates using various xxx-to-slf4j bridges. Right now it's kind of a mess....

@kkrugler - Makes sense. So what this PR does for s3 plugin has to be repeated for every other plugin as well, right?

@KKcorps - yes, exactly. Plus other (lower-level) Pinot jars that include logging implementations.


Compiler warnings with Elixir v1.17.0-rc.0

Compiling 38 files (.ex)
    warning: single-quoted strings represent charlists. Use ~c"" if you indeed want a charlist or use "" instead
    │
 75 │       handle(:hackney.request(method, url, headers, body || '', opts), opts)
    │                                                             ~
    │
    └─ lib/tesla/adapter/hackney.ex:75:61

PR welcome, but before we could even upgrade Elixir, we need to fix the CI for https://github.com/elixir-tesla/tesla/pull/623
It is related to SSL certs and testing dept. I would appreciate your support with it.

@yordis the warning was fixed in main, I think all we have left to close this one is to publish a new version to Hex.pm.

Released 🚀 💜


⚠ Bofrost.de has degraded performance

In 9f6c673, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1622 ms

Resolved: Bofrost.de performance has improved in f881725 after 21 minutes.


feat: add gene associations to four mitochondrial transport reactions

Main improvements in this PR:
Adds gene associations to four reactions (addresses issue #119).
The following gene associations are added to the model (to grRules), as well as their associated PMIDs (to rxnReferences):

Reaction
Reaction description
New gene assoc
UniProt ID
Enzyme description
PMID

HMR_5124
mitochondrial import of glycine
ENSG00000144659
Q96DW6
Mitochondrial glycine transporter
27476175

HMR_4914
mitochondrial import of COA
ENSG00000181035
Q86VD7
Mitochondrial coenzyme A transporter SLC25A42
19429682

HMR_9015
mitochondrial import of SAM
ENSG00000144741
Q70HW3
S-adenosylmethionine mitochondrial carrier protein
14674884

HMR_9020
mitochondrial import of FAD
ENSG00000164933
Q9H2D1
Mitochondrial folate transporter/carrier
32166001

Three of the genes were not previously in the model, and are therefore new:

ENSG00000144659 (SLC25A38)
ENSG00000164933 (SLC25A32)
ENSG00000181035 (SLC25A42)

I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Selected devel as a target branch

Note that this PR should not conflict with #162 (and the order of implementation does not matter), but it may be flagged as conflicting since it is changing the same file (HumanGEM.yml).


Added service management configuration option

It may be worth it to move those mcollective vars into class parameters, then reference the local class params.


[Q] The way not to use posix headers ?

Hi @isaacs
Is there any way to make tar to force not to use posix headers
I encountered an issue that some certain tar extractor module does not support posix headers properly..
So, I wonder if there is any way not to use posix headers in using this tar node module like this.
https://dev.openwrt.org/browser/trunk/tools/ipkg-utils/patches/200-force_gnu_format.patch?rev=34261

I didn't add this for the v3 rewrite because it seems like it'd only ever result in an incorrect entry.  Pax headers are not added unless something in the header cannot be properly encoded in a tar header block.
What extractor are you using?


Not run UTM 4.6.0 in my iPad Pro m1

Describe the issue
A clear and concise description of what the issue is. BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Configuration (required)

UTM Version:
OS Version:
Device Model:
Is it jailbroken (name jailbreak used)?
How did you install UTM?

Crash log
If the app crashed, you need a crash log. To get your crash log, open the Settings app and browse to Privacy -> Analytics & Improvements -> Analytics Data and find the latest entry for UTM. You should export the text and attach it here.
Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the bottom of the configuration options (or at the top of the QEMU page) is Debug Log. Turn it on and save the VM. After you experience the issue, quit the VM and re-launch UTM. Open the VM settings again and select Export Log... and attach it here.
Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since GitHub has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

UTM 4.6.0 not open and full feature in my iPad Pro m1
![IMG_0003](https://github.com/user-attachments/assets/1a134158

-9bf5-40d8-8b81-462e470d84da)

use ios 16.3.1 and lower

Please provide a crash log (as explained in the template you forgot to fill out). Once you do, we can reopen this.


Is it possible to create Azure policy to enforce budget control and prevent resource underutilization?

Wondering what are some of Azure Policy examples for cost management? For example, is it possible to use Azure Policy to limit spending at Resource Group level?

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

ID: 3a9a86fd-b0f3-8de4-0800-5124ce4f0f4a
Version Independent ID: 6337b7e3-c10b-bfc7-9ebc-c175c938c967
Content: Cost Management sample policy statements - Microsoft Cloud Adoption Framework for Azure
Content Source: docs/govern/cost-management/policy-statements.md
Service: cloud-adoption-framework
Sub-service: govern
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Great idea. This feature is currently unavailable. I'll pass along the feedback to the policy and cost management teams.


Use orderID in transaction listener

@cpacia - This is a follow-up PR to the wallet interface changes.
In the transaction listener callback, I have made changes to the fetching of the order/contract details.
When orderID is available in the TransactionInput/TransactionOutput, it will be used to fetch the details else the existing logic of using the output.Address/input.LinkedAddress will be used.

Coverage decreased (-0.02%) to 33.714% when pulling d37479201a999c1e3e1d5f3ca126384dacad70d6 on amangale:use_orderID into bcf24414845c0cc1f499f2ad56c0827afbf2b1c8 on OpenBazaar:multiwallet.

LGTM thanks @amangale


tasks waiting in the queued state may get cancelled immediately on start

On the cf-infrastructure team, we have a few tests that start many bosh tasks at once that deploy several consul deployments. Some of these tasks wait in the queued state for a fair amount of time.  Occasionally, we see that these tasks get cancelled immediately when they start.
We have a working theory that it's related to a race condition when a task goes from queued to processing.  If the task was queued for more than 90s and the status is checked before the checkpoint time is updated, it gets cancelled.
See also: thread on Slack
Here are the logs for one of the cancelled tasks:
nm+dm $ bosh task 46 --debug
Using environment 'https://<IP_ADDRESS>:25555' as client 'admin'

Task 46

I, [2017-09-07T23:13:46.853493 #2834] [0x2ad3a7ebd110]  INFO -- TaskHelper: Director Version: 262.3.0
I, [2017-09-07T23:13:46.853554 #2834] [0x2ad3a7ebd110]  INFO -- TaskHelper: Enqueuing task: 46
I, [2017-09-07 23:16:57 #7237] []  INFO -- DirectorJobRunner: Looking for task with task id 46
D, [2017-09-07 23:16:57 #7237] [] DEBUG -- DirectorJobRunner: (0.000186s) SELECT NULL
D, [2017-09-07 23:16:57 #7237] [] DEBUG -- DirectorJobRunner: (0.000229s) SELECT * FROM "tasks" WHERE "id" = 46
I, [2017-09-07 23:16:57 #7237] []  INFO -- DirectorJobRunner: Found task #<Bosh::Director::Models::Task @values={:id=>46, :state=>"timeout", :timestamp=>2017-09-07 23:13:46 UTC, :description=>"create deployment", :result=>nil, :output=>"/var/vcap/store/director/tasks/46", :checkpoint_time=>2017-09-07 23:13:46 UTC, :type=>"update_deployment", :username=>"admin", :deployment_name=>"consul-scale-down-5-to-3", :started_at=>nil, :event_output=>"", :result_output=>"", :context_id=>""}>
I, [2017-09-07 23:16:57 #7237] []  INFO -- DirectorJobRunner: Starting task: 46
I, [2017-09-07 23:16:57 #7237] [task:46]  INFO -- DirectorJobRunner: Creating job
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000108s) SELECT NULL
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000154s) SELECT * FROM "tasks" WHERE "id" = 46
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000164s) SELECT NULL
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000049s) BEGIN
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000306s) UPDATE "tasks" SET "event_output" = ("event_output" || '{"time":1504826217,"error":{"code":10001,"message":"Task 46 cancelled"}}
') WHERE ("id" = 46)
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.004252s) COMMIT
I, [2017-09-07 23:16:57 #7237] [task:46]  INFO -- DirectorJobRunner: Task 46 cancelled
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000092s) SELECT NULL
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000208s) SELECT * FROM "tasks" WHERE ("id" = 46) LIMIT 1
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000093s) SELECT NULL
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000049s) BEGIN
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.000282s) UPDATE "tasks" SET "state" = 'cancelled', "timestamp" = '2017-09-07 23:16:57.201156+0000', "description" = 'create deployment', "result" = 'task cancelled', "output" = '/var/vcap/store/director/tasks/46', "checkpoint_time" = '2017-09-07 23:13:46.846333+0000', "type" = 'update_deployment', "username" = 'admin', "deployment_name" = 'consul-scale-down-5-to-3', "started_at" = NULL, "event_output" = '{"time":1504826217,"error":{"code":10001,"message":"Task 46 cancelled"}}
', "result_output" = '', "context_id" = '' WHERE ("id" = 46)
D, [2017-09-07 23:16:57 #7237] [task:46] DEBUG -- DirectorJobRunner: (0.002927s) COMMIT
I, [2017-09-07 23:16:57 #7237] []  INFO -- DirectorJobRunner: Task took 0.01756326 seconds to process.

Task 46 cancelled

Capturing task '46' output:
  Expected task '46' to succeed but state is 'cancelled'

Exit code 1

In all cases we have examined the time between these two log lines has been at least 3 minutes:
I, [2017-09-07T23:13:46.853554 #2834] [0x2ad3a7ebd110]  INFO -- TaskHelper: Enqueuing task: 46
I, [2017-09-07 23:16:57 #7237] []  INFO -- DirectorJobRunner: Looking for task with task id 46

Some tasks that wait that long do execute fine.  In those cases, we see that the checkpoint_time is updated, for example this task worked (see the line that has UPDATE "tasks":
nm+dm $ bosh task 442 --debug | head -n 50
I, [2017-09-08T18:22:44.654271 #2834] [0x2ad3a7ebd110]  INFO -- TaskHelper: Director Version: 262.3.0
I, [2017-09-08T18:22:44.654364 #2834] [0x2ad3a7ebd110]  INFO -- TaskHelper: Enqueuing task: 442
I, [2017-09-08 18:25:40 #14416] []  INFO -- DirectorJobRunner: Looking for task with task id 442
D, [2017-09-08 18:25:40 #14416] [] DEBUG -- DirectorJobRunner: (0.000129s) SELECT NULL
D, [2017-09-08 18:25:40 #14416] [] DEBUG -- DirectorJobRunner: (0.000221s) SELECT * FROM "tasks" WHERE "id" = 442
I, [2017-09-08 18:25:40 #14416] []  INFO -- DirectorJobRunner: Found task #<Bosh::Director::Models::Task @values={:id=>442, :state=>"processing", :timestamp=>2017-09-08 18:22:44 UTC, :description=>"create deployment", :result=>nil, :output=>"/var/vcap/store/director/tasks/442", :checkpoint_time=>2017-09-08 18:22:44 UTC, :type=>"update_deployment", :username=>"admin", :deployment_name=>"consul-tls-key-rotation", :started_at=>nil, :event_output=>"", :result_output=>"", :context_id=>""}>
I, [2017-09-08 18:25:40 #14416] []  INFO -- DirectorJobRunner: Starting task: 442
I, [2017-09-08 18:25:40 #14416] [task:442]  INFO -- DirectorJobRunner: Creating job
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000094s) SELECT NULL
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000160s) SELECT * FROM "tasks" WHERE "id" = 442
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000078s) SELECT NULL
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000182s) SELECT * FROM "tasks" WHERE "id" = 442
I, [2017-09-08 18:25:40 #14416] [task:442]  INFO -- DirectorJobRunner: Performing task: #<Bosh::Director::Models::Task @values={:id=>442, :state=>"processing", :timestamp=>2017-09-08 18:22:44 UTC, :description=>"create deployment", :result=>nil, :output=>"/var/vcap/store/director/tasks/442", :checkpoint_time=>2017-09-08 18:22:44 UTC, :type=>"update_deployment", :username=>"admin", :deployment_name=>"consul-tls-key-rotation", :started_at=>nil, :event_output=>"", :result_output=>"", :context_id=>""}>
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000087s) SELECT NULL
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000049s) BEGIN
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.000313s) UPDATE "tasks" SET "state" = 'processing', "timestamp" = '2017-09-08 18:25:40.025268+0000', "description" = 'create deployment', "result" = NULL, "output" = '/var/vcap/store/director/tasks/442', "checkpoint_time" = '2017-09-08 18:25:40.025439+0000', "type" = 'update_deployment', "username" = 'admin', "deployment_name" = 'consul-tls-key-rotation', "started_at" = '2017-09-08 18:25:40.025383+0000', "event_output" = '', "result_output" = '', "context_id" = '' WHERE ("id" = 442)
D, [2017-09-08 18:25:40 #14416] [task:442] DEBUG -- DirectorJobRunner: (0.001757s) COMMIT
I, [2017-09-08 18:25:40 #14416] [task:442]  INFO -- DirectorJobRunner: Reading deployment manifest

In the cases where that task is cancelled, the checkpoint_time is never updated and remains the timestamp of when the task was queued.

Is your director under very high load when this happens, or the database locked for a period around this time?

I don't think the director was under high load in terms of RAM or CPU usage from what we could tell, but this theory from @jraqula in the slack thread seems plausible:

how's this for a theory: listing/checking a task will cause the state to be set to timeout if it's outside the 90s

Our tests poll the director to check the task status on an interval (that is 5 seconds by default).

Story #152339383


Unexpected behaviour of duplicate Publish in case of QoS 2

While using QoS 2, we are experiencing the following issue when the following steps are performed:

QoS 2 message is published by client
PubRec is sent to the client
Client gets disconnected (due to possible bad network) before it can send back PubRel
When client connects back and publishes the same message (since QoS 2 flow is not yet complete), the broker does not treat this message as a duplicate publish. All subscribers to this topic receive the duplicate message.

Environment

VerneMQ Version: latest
OS: MacOS Catalina
Erlang/OTP version (if building from source): OTP 23
Cluster size/standalone: standalone

Expected behaviour

The duplicate message published by publisher should be rejected by the broker.

Actual behaviour

When client connects back and publishes the same message (since QoS 2 flow is not yet complete), the broker does not treat this message as a duplicate publish. All subscribers to this topic receive the duplicate message.

We are ignoring waiting acks for QoS 2 here: https://github.com/vernemq/vernemq/blob/master/apps/vmq_server/src/vmq_mqtt_fsm.erl#L878
Any reason why we are doing this?

@dumbpreacher does the client set the DUP flag in the re-publish?

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@ioolkos, thanks for the quick response. Yes, we are setting DUP flag in the republish.

@dumbpreacher from your description it's unclear whether the consumers did get the message 1x or 2x. Which one is the case?
also: is this in a cluster, where the publisher is not on the same node as the consumer? (then this would be an additional place to check for issues).

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@ioolkos, the subscribers to this topic received the republishes as well. I was subscribing using a mosquitto client with qos 2.
We were using a standalone cluster (i.e. single node only)

@dumbpreacher did the subscriber get the message 1x or 2x?
You used mosquitto_sub? if yes, add -d flag to get info what the command does exactly.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@dumbpreacher dup flag 0 at the outgoing end makes sense; the dup flag is only set per one client-server session, not end-to-end.
I have one last question: does the original publisher use the same PacketID for the re-sent (and flagged as duplicate) Publish as for the original message? it should!

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

If by packet ID you mean Message Id, then yes we are using the same Message Id:
2022-03-21T12:25:43Z <9488.25674.36> MQTT RECV: CID: "swagat:889422:32675-2376-53732" PUBLISH(d0, q2, r0, m1, "chat/32675-2376-53732/client-events/0") with payload:
    testing2
2022-03-21T12:25:43Z <9488.25674.36> Calling auth_on_publish(889422,{[],
                                                                     <<"swagat:889422:32675-2376-53732">>},2,chat/32675-2376-53732/client-events/0,false) with payload:
    testing2
2022-03-21T12:25:43Z <9488.25674.36> Hook returned "ok"
2022-03-21T12:25:43Z <9488.25674.36> MQTT SEND: CID: "swagat:889422:32675-2376-53732" PUBREC(m1)
2022-03-21T12:26:50Z <9488.25674.36> Trace session for swagat:889422:32675-2376-53732 stopped
2022-03-21T12:26:57Z New session with PID <9488.26078.36> found for client "swagat:889422:32675-2376-53732"
2022-03-21T12:26:57Z <9488.26078.36> MQTT RECV: CID: "swagat:889422:32675-2376-53732" CONNECT(c: swagat:889422:32675-2376-53732, v: 4, u: 889422, p: password, cs: 0, ka: 360)
2022-03-21T12:26:57Z <9488.26078.36> Calling auth_on_register({{182,68,78,21},
                                                               42196},{[],
                                                                       <<"swagat:889422:32675-2376-53732">>},889422,password,false)
2022-03-21T12:26:57Z <9488.26078.36> Hook returned "ok"
2022-03-21T12:26:57Z <9488.26078.36> MQTT SEND: CID: "swagat:889422:32675-2376-53732" CONNACK(sp: 1, rc: 0)
2022-03-21T12:27:03Z <9488.26078.36> MQTT RECV: CID: "swagat:889422:32675-2376-53732" PUBLISH(d1, q2, r0, m1, "chat/32675-2376-53732/client-events/0") with payload:
    testing2

@dumbpreacher thanks, this looks like a Verne issue then.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@ioolkos, could you help with reviewing this PR: https://github.com/vernemq/vernemq/pull/1968

Fixed by https://github.com/vernemq/vernemq/pull/1968


Ollama support

I use Ollama as my inference server for local LLMs. Ollama is supported by many LLM frameworks, but not Guidance.
Would love to see a direct integration with Ollama via the models package.
I'm aware that LiteLLM support is available and can be used to proxy Ollama, but that adds overhead and makes the solution more complex.
Supporting Ollama would immediately enable support for all the models Ollama makes available: model library

May I ask if any updates?

See also:

https://github.com/guidance-ai/guidance/issues/648
https://github.com/guidance-ai/guidance/issues/687


Turning icons off?

Hey,
Trying to turn the new icons off - Sorry, no offence!
But adding this to user settings has no effect:
"spacegray_fileicons": false,
Am I missing something else?
Many thanks
Chris

Just tried it now and it turns my icons off just fine,
what is your sublime version?

Hey Marco,
Latest build - 3126.
I also just tried my laptop as well, still no luck.
Have tried restarting but no change.

Could you please share your Preferences.sublime-settings?

{
"always_show_minimap_viewport": true,
"auto_close_tags": true,
"auto_find_in_selection": true,
"bold_folder_labels": false,
"caret_extra_bottom": 1,
"caret_style": "phase",
"close_windows_when_empty": true,
"color_scheme": "Packages/Theme - Spacegray/base16-ocean.dark.tmTheme",
"copy_with_empty_selection": true,
"dictionary": "Packages/Language - English/en_GB.dic",
"drag_text": false,
"draw_minimap_border": true,
"ensure_newline_at_eof_on_save": true,
"folder_exclude_patterns":
[
"_notes"
],
"font_face": "consolas",
"font_options":
[
"subpixel_antialias"
],
"font_size": 10,
"highlight_line": true,
"highlight_modified_tabs": true,
"hot_exit": true,
"ignored_packages":
[
"Browser Refresh",
"Vintage"
],
"minimap_scroll_to_clicked_text": false,
"overlay_scroll_bars": "enabled",
"preview_on_click": true,
"remember_open_files": false,
"scroll_past_end": false,
"scroll_speed": 0,
"shift_tab_unindent": true,
"show_full_path": false,
"spacegray_fileicons": false,
"spell_check": false,
"theme": "Spacegray.sublime-theme",
"word_wrap": true
}

Hey there!
Despite the fact of not turning it off as mentioned above, it doesn't show properly the icons either for me. Check out the screenshot below.

By the way, looking forward for the icons. Thanks! :D
Version: 3126

I'm facing the exact same problem. Also the "unsaved changes" icon in tab bar has the same ~orange weird icon. The spacegray_fileicons setting has no effect.

Sorry guys, can't replicate the issue, let's go one step above, what is your OS?
Also any help with the debug is welcome.

I'm on Windows 10.
I'll try and re-install it over the weekend, with just ST and Spacegrey, and report back.

Mac OS latest, and Sublime Text 3 latest. Don't have time to try to reinstall for now though...

I realized that the path of icons in the .sublime-theme file was referring to Theme - Spacegray and not Spacegray. I have no idea why the rename happened. After changing it, the default old icons (arrows) worked like a charm.
I'll try to reinstall because the files doesn't reflect the master.

I can confirm that resetting this file worked for me: https://github.com/kkga/spacegray/blob/master/Spacegray Oceanic.sublime-theme

If multiple packages define file type icons via file_type_...tmPreference with different names for same scopes, ST picks up the first definition one it finds. Icon textures however must reside next to or in icons folder next to a sublime-theme file.
Hence, if another package defines different file types, which Spacegray does not provide icon textures for, no icon is visible. see: https://github.com/sublimehq/sublime_text/issues/2520.

If A File Icon is installed, it may prevent file_type icons from being hidden if spacegray_fileicons: false is set.


Suricata/Snort Tagging Plugin

It would be nice to be able to apply signature tags into the session data. Only one I could find is Pigsty but it's not able to keep up with the amount of traffic coming in.

@eoinmiller - any  news with suricata / moloch integration?

how to install suricata on moloch? , (pigsty-moloch-plugin = moloch + suricata  ??)

I think the new suricata plugin will do what you want


Add Cilium CNI plugin example

addressed with https://github.com/fujitatomoya/ros_k8s/commit/5b323df1a00d1cb78f705fd5e8a725353eea82ab


DfsLogger should use a "static named constructor" to create a new logger from a new file

Currently, DfsLogger has a constructor that does not initialize the LogEntry, and then immediately calls .open() to create a new file used as the DfsLogger's LogEntry. This results in us being unable to make the logEntry field final, and makes for some confusing reasoning inside DfsLogger about whether a logEntry has been initialized or not.
This also leaves open the possibility for some race conditions... however, from what I can tell, the constructor that does not initialize logEntry always immediately calls the open method to create one, so there is never an actual race condition that occurs. Still, it would be better to code this in a way that made it clear that this was not an opion.
A "static named constructor" is the term I'm using when you construct objects using public static methods with convenient names, rather than use an overloaded constructor for different scenarios. For example,
LogEntry entry1 = LogEntry.fromPath(path);              // vs. new LogEntry(path)
LogEntry entry2 = LogEntry.fromMetaWalEntry(metaEntry); // vs. new LogEntry(metaEntry)

This pattern is used with a private constructor called inside the static methods, after any validation checks that apply to the specific scenario (in my example, validation of a path or deserializing from the metadata entry).
This issue tracks the creation of two "static named constructors" in DfsLogger to replace the current two constructors, using names appropriate for the situations where they are called, and the creation of a private constructor that initializes all the fields, which should be able to be made final inside the DfsLogger. Further cleanup can be done throughout the class once the fields are final and we can guarantee that everything is properly initialized in the non-static methods.
This loosely relates to the work done in #4082 and #4085 to clean up uses of LogEntry and remove technical debt from the WAL code.

I can take a look at this one.


cursor glitch when repositioned before deleted separator

use this opportunity to improve another cases where positioning is affected by the new count of separators

fix with b080673


Add Headers in Docker Kong

I am trying to add HSTS header in the Kong docker-compose.yml file as env variable:
KONG_NGINX_PROXY_ADD_HEADER: 'Strict-Transport-Security: max-age=31536000'.
But I am getting CORS issue after adding this header. guess this setting is overriding 'Access-Control-Allow-Origin *'.
How can I add multiple headers in my docker-compose.yml file ?
Or is there a better way to add these headers in my dockerised Kong ?

Hey @venkin304
What you intend to do is
KONG_NGINX_PROXY_ADD_HEADER: "Strict-Transport-Security max-age=31536000"

From Nginx docs:

NGINX configuration blocks inherit add_header directives from their enclosing blocks, so you just need to place the add_header directive in the top‑level server block. There’s one important exception: if a block includes an add_header directive itself, it does not inherit headers from enclosing blocks, and you need to redeclare all add_header directives:

If you need to add more headers, I would recommend checking the post-function plugin for example -- see the docs here https://docs.konghq.com/hub/kong-inc/post-function.


fix(rowactioncell): incorrect colors

In reference to #1346
This slightly changes the fix to #1314
Summary
RowActionCell will continue to use hasIconOnly with the tooltip being positioned to the left
OverflowMenu will stay gray20 on hover instead of blue
Change List (commits, features, bugs, etc)

Fixed invalid null props in ListItem stories
Removed custom styling that was turning icons blue in row actions as it doesn't adhere to the design guidelines
Positioned the rowActionCell tooltip to the left
Made the RowActionCell button small to match the size of the OverflowMenu

Acceptance Test (how to verify the PR)

Go to Table row actions story and see that the icon is still the correct color with the tooltip to the left
Go to TableBodyRow actions stories and see that the icon is still the correct color with the tooltip to the left

@CynZhang could you take another look at this?

@tay1orjones can you take another look at this one now?

looks good. Is there a particular reason for showing the tooltip to the left of the icon instead of bottom of it?

@CynZhang when the tooltip is at the bottom, theres an extra scollbar thats added on to the table row

:tada: This PR is included in version 2.98.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Enable authors to specify SXG-only tags

For instance if the HTML contains:
<template data-sxg-only>
  <script>log("visit-from-sxg=true")</script>
</template>

then when generating an SXG, rewrite it to:
<script>log("visit-from-sxg=true")</script>

Other possible spellings include <template class=sxg-only> or <script type=text/sxg-only> or <!--[if SXG]>, but the above seems the most general and least likely to collide with existing pages. (But that should be confirmed before implementing.)
Motivation
Enable web publishers to distinguish SXG visits from unsigned visits in their analytics. This could help them track overall usage, or compare performance metrics between the two cohorts. Examples of feature requests for a similar tool (CF ASX):

"I wish the browser sent some sort of request to the server with maybe a header signifying “I visited the page with a signed exchange” so things like log analytics would still be accurate."
"...how many times requests were served through SXGs cache?"

and/or we could have a simpler API for the common use case. Something like:
<meta name=declare-sxg-var>

becomes something like:
<script>window.isSXG = true</script>

Remaining task is to implement on fastly_compute.

Implementing for fastly_compute should be easy now that process_html.rs exists.


Update howto-vm-sign-in-azure-ad-windows.md

The name is incorrect for the Enterprise Application in the Microsoft Tenant. It is now called "Azure Windows VM Sign-In" for controlling RBAC for CAPs. Please change this as it was difficult to verify since it stated it already exists in the tenant and the name was not searchable on the web Microsoft Admin Console

@MicrosoftGuyJFlo
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Owl support

It would be great to make this fully compatible with Owl. This would give a full-fledged scientific notebook environment in ocaml.
I have tried with a patched master and everything seems to work, the only missing bits are:

a backend for plplot (that can use cairo as well) or its higher level interface used in owl
support for owl multiline output (or fix for it in owl, I am not sure what's better/easier). For example a 4 by 4 matrix is shown as# Mat.uniform 4 4;;

C0       C1       C2       C3
R0 0.873982 0.799467 0.545207 0.160527
R1 0.676436 0.590859 0.744383  0.99189
R2 0.527598  0.68333 0.174403 0.330034
R3   0.1083 0.646665 0.529998 0.727835
- : Mat.mat =

but in ocaml-jupyter I see only - : Mat.mat =

Ping also @ryanrhymes that could be interested

I agree that owl and ocaml-jupyter should be more compatible. It will contribute for numerical analysis, machine learning and data science in OCaml. It's an important task, but the compatibility requires some changes of owl and plplot.
Visualization problem
plplot and owl's wrapper is not friendly with ocaml-jupyter because an OCaml binding of plplot doesn't support plotting charts in memory. plplot and owl only supports charts into image files. A simple idea is loading a plotted image file after plplot and owl draws it into the file, e.g., https://github.com/akabe/docker-ocaml-jupyter-datascience/blob/master/notebooks/owl.ipynb. However I think this is not the best solution. The best way is that plplot (and owl) can plot a chart into memory and ocaml-jupyter directly loads it. This requires that plplot and owl supports in-memory plotting. If it is accomplished, I can implement a visualization library for plplot and owl (like jupyter.archimedes package).
Matrix output
This is clearly a bug of owl. The cause of this problem is that output buffer is not flushed. Try this:
# Owl.Mat.uniform 4 4 ;; flush stdout ;;
- : Owl.Mat.mat =

         C0        C1       C2       C3
R0 0.108383  0.844251 0.727378 0.497851
R1 0.873218  0.243849 0.720696 0.544599
R2 0.838986 0.0246897 0.468628 0.625664
R3 0.614223  0.179304 0.772862 0.735753

Although Owl's output is a little strange. OCaml-style pretty printing should use #install_printer like

https://github.com/akabe/slap/blob/master/lib/install_top.ml
https://github.com/mmottl/lacaml/blob/master/src/install_printers.ml

Could you report this issue to https://github.com/ryanrhymes/owl?

Thanks. The visualization hack is the same I am using right now. I See if I can help and make it smoother adding in memory support.
Meanwhile,  I will report the printer issue to owl

Thanks for reporting the issue.
I leave this issue because maybe plplot and owl support in-memory output. It is my future work to create a library for plotting with plplot backend, like jupyter.archimedes.

There is some additional work needed for the in memory backend, namely https://github.com/hcarty/ocaml-plcairo with this one is it possible to instantiate a custom drawing context and extract it. I need to double check if there is additional plumbing needed in owl, otherwise that should be enough

Thanks. I tried the package, but I don't know how to plot an in-memory chart by plcairo and plplot. Can you show me an example program?

I need to try it, as a first test I would try copying the owl plot stream into a new plot stream and adding a cairo context to it, a sort of mixup of https://github.com/hcarty/ocaml-plcairo/blob/844f950dda8a63529dbfb4dc94f75f60d1c6b8ee/src/plcairo.ml#L276 and https://github.com/hcarty/ocaml-plcairo/blob/844f950dda8a63529dbfb4dc94f75f60d1c6b8ee/src/plcairo.ml#L203
Once you have that, you can use the cairo context directly as you do for Archimedes, and you can extract it from the new plot object with plget_context.
The fact that there is this hidden global state in PlPlot and that this is additionally wrapped in two different ways by the three libraries does not help to reason about what is going on. If we figure out how these are working, it should not be too hard to make the Owl plplot wrapper extendable with additional backends

I see, nice. I will implement a new plotting library jupyter-plplot after a function like plget_context will be added to Owl and PLplot.

Were there any updates on this matter?

@XVilka this has been solved long time ago, see this http://ocaml.xyz/chapter/interact.html
I think we can close this issue now :)

I wouldn’t close it. Having a plug-in to automatically display the image without having to create and open a file would be more ideal

@XVilka I know the solution you mentioned, but I think drawing an in-memory chart is a better way than  embedding an image file written by plplot. I keep this issue for jupyter-plplot package.

@mseri Do you have any progress on this issue? If  you cannot take enough time for the task, I think we should close for the time being, and re-open after a patch of plplot is released. I guess this issue will take very long time until close.

I don’t have the time right now. May be worth to keep it open: if some external contributor wants to help, here it is explained what needs to be done

No external contributor appears since last year. If someone opened a similar issue, I would introduce this issue. Please re-open this when you finish the task.

Related https://github.com/owlbarn/owl/issues/377


Sharing iOS app data to LVN

@bcardarella asked me to post here from the Slack channel to open this for discussion. Here is our use case:
We want to use notifications, but need to have the iOS app pass back the GUID that uniquely identifies the phone-app for notifications. So LVN needs to make some data available to the LiveView.
Could we do that in the config part of  return LiveSessionCoordinator(URL(string: "http://<IP_ADDRESS>:4000/news")!, config: config) ? Or how would we have the iOS pass info into the LVN?
For example, in our testing of notifications, we're just checking the XCode log:
let token = deviceToken.reduce("") { $0 + String(format: "%02x", $1) }
print("The token is")
print(token)

but we need a way to pass that to the Elixir backend so that we can save it and know the token to use to send the APNS message to.

You can use pushEvent to send data to a handle_event on your LiveView. The value parameter can be any JSON serializable type.

@dbii if this works for you please let us know and we can close this out

I see how pushEvent works (in the context of the toggle-favorite button in the Cats iOS-tutorial), but don't see how to setup pushEvent to be triggered on app startup/switching to app, since it needs the LiveView socket instantiated. I think what needs to happen is when the LiveSessionCoordinator makes the initial call the value gets stuck in as a key to params maybe (but I'm not sure if that can be accessed, haven't played with it)? Or maybe put into socket or session so that the LiveView mount can get it?

I realized that is where it really needs to go, so that when the user logs in, their APNS token can be linked to their account.

You can use LiveSessionConfiguration.connectParams to send the data to mount.
LiveView(
  ...,
  configuration: .init(
    connectParams: { _ in
      ["apns_token": tokenValue]
    }
  )
)

However, it may be better to send the token once when the user logs in and allows notification access.

We get an error in Xcode trying this.

@dbii Since you're passing the session in, you need to set the connectParams on the configuration of your LiveSessionCoordinator. Or if you'd prefer to use the new session-less init, you can remove the session coordinator and do something like:
var body: some View {
    LiveView(
        .automatic(development: .localhost, production: .custom(URL(string: "example.com")!)),
        configuration: .init(connectParams: { _ in ["apns_token": "tokenValue"] })
    )
}

I just tested this following @carson-katri's example and can confirm its working as expected.
@dbii Let us know if you find any other issues related to this.