GoAccess Dockerfile

Just found this tool, looks brilliant!
I was hoping to use this along with Caddy to watch the access logs in my docker-compose stack. I found there was a couple very outdated third party implementations.
https://github.com/diyan/goaccess-docker
https://github.com/joelchen/goaccess
Both of these are pre-1.0.0. I was hoping for an official Docker image with support for running and watching the Caddy logs in realtime.
Thanks

I did build myself a Dockerfile which works fine for just processing one-off files for now, but I can't get realtime working. I'm not sure how to make the goaccess command run in the foreground.
FROM alpine:3.4

MAINTAINER Francis Lavoie<EMAIL_ADDRESS>
ENV goaccess_version=1.0.2
ENV build_deps='go build-base ncurses-dev'

RUN set -x && \
    apk add --update ncurses $build_deps && \
    wget -O /tmp/goaccess.tar.gz http://tar.goaccess.io/goaccess-$goaccess_version.tar.gz && \
    tar -xzvf /tmp/goaccess.tar.gz -C /tmp && \
    cd /tmp/goaccess-$goaccess_version && \
    ./configure --enable-utf8 && \
    make && \
    make install && \
    apk del $build_deps && \
    rm -rf /var/cache/apk/* /tmp/goaccess*

ADD ./goaccess.conf /usr/local/etc/goaccess.conf

EXPOSE 7890

ENTRYPOINT ["goaccess"]

Usage:
Make sure you have a goaccess.conf file in the same dir, it gets copied into the container.
Build with $ docker build -t goaccess .
Do stuff $ cat access.log | docker run -i goaccess > access.html

Thanks for sharing this! Were you able to get the real-time report working?

Yeah - see the edit at the bottom. Problem is though, I need to generate
the HTML somewhere on the host first right now with this setup. I'll
probably expand on it and make a repo with Caddy to serve the HTML and
proxy the websockets.
On Sep 17, 2016 11:53 AM, "Gerardo O."<EMAIL_ADDRESS>wrote:

Thanks for sharing this! Were you able to get the real-time report working?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allinurl/goaccess/issues/520#issuecomment-247784048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACA41W10EPGppZBZIaT_GG6pQqYUo4Ppks5qrAzbgaJpZM4J_SKC
.

One of the things I need to do is to daemonize a process so it won't stick to a TTY as it is right now.
I'll play with the docketfile you posted here. Also, I didn't know about Caddy, look pretty interesting :+1:

@allinurl or @francislavoie: Any progress on this, or need any help testing? I've got a Docker-Compose stack as well that I'd like to include GoAccess with 😃

@allinurl or @francislavoie: Any progress on this, or need any help testing? I've got a Docker-Compose stack as well that I'd like to include GoAccess with 😃

@brandon099 are you asking about the docker file? I have not had the chance to look at daemonizing a process, but I can bump this up in the to-do list, it shouldn't be to bad though. Any help is always welcome :)

I haven't touched this since either, I ended up just setting up netdata and not doing anything with my logs for this project. Still interested in a proper solution but I don't have much time to allocate to it.

Yeah I was asking about the Dockerfile. If you could bump up the daemonized process functionality on the to-do list, I can certainly work on the Dockerfile piece when that's done!
Thanks for your work on this, it's an awesome project!

@brandon099 I just added --daemonize command line option to run goaccess as a daemon (if --real-time-html enabled). It will be shipped in the upcoming version.


WIP: Corrected booking interfaces

Shouldn't this be Experience instead of Subject?
What is being booked is an escape room experience of a time Slot in the Room, not the room itself. We could use both Subject & Experience, but I don't think the Bookings package really needs to know about the Subject of the Experience.


interface downwards compatibility / versioning

this is a general go issue.
e.g. commit bf5a8edb790005 removed AddCommentFrame from the public API. This breaks the API.
How do you intend to handle such cases in the future?
P.S.: The solution proposed in http://stackoverflow.com/questions/24855081/how-do-i-import-a-specific-version-of-a-package-using-go-get#comment51770955_26546559 does not work if there are subpackages, because they contain the repository name of the 'parent' package.

ID3v2 is in beta version. Until version 1.0 the API will change.
After this version the existing API won't change. But there will be adding new
features.
Instead of tag.AddPictureFrame(frame), you should use tag.AddFrame(tag.ID("Attached picture"), frame).

I will necessarily add it to README

tag.AddFrame(tag.ID("Attached picture"), frame)

grrr, are you serious? This makes field name typos runtime errors instead of compiletime errors.
What's the roadmap to 1.0?

Yes, you are right. In 0.8 I will return Add(Picture/Comment/UnsynchronisedLyricsText)Frame functions.
The main properties of 1.0 should be stability and convenient API.

I retuned these functions in https://github.com/bogem/id3v2/commit/7b84e16ca945c04c749c0bfa9bd6765b160fc7b9. If you'll have more offers to improve id3v2 library, I will glad to hear them :)

Tag.Flush was replaced by Save, right? IMO Flush was the more precise name, what made you change it to Save? See https://travis-ci.org/mro/internet-radio-recorder/jobs/155643729#L342

I was inspired by taglib, when I did this change. I like Save more, because It's simplier, friendlier and more understa than Flush.

ic, I wasn't aware Flush closes. I know flush from C where it operates on a stream. Save really may be more appropriate for a data-structure.

And as tag is a data structure, I chose Save as a name for this function


Is the robot not included in the social force model?

When I added a turtlebot to the gazebo world generated by pedsim_ros, I found that these people were not able to see the robot and collide with the robot. The pedsim_simulator has known the position of the robot in the gazebo world.

Hi @zzuxzt! I just discover how to include the robot in the social force model. You must change the "robot_mode" param by "0" in the launcher.
In addition to that, pedsim_simulator uses the TF Tree to know the position of the robot in the global_frame.

@jginesclavero Thank you for you help. I've solved it.

Hi there.
I too would like to add Turtlebot3 to Gazebo.
If you don't mind, could you give me some specifics on how to do that?


thread_setaffinity: Allow affinity param to have a length less than cpumask_size()

Instead of enforcing that the table length is >= cpumask_size(), any missing CPU numbers get assigned an affinity of false. This makes this API a bit more user-friendly, since users no longer have to initialize a table of length cpumask_size() before setting the particular  affinities they actually want.
As an example, before this commit, you'd have to do something like:
local affinity = {}
for i=1,uv.cpumask_size() do
  affinity[i] = false
end
affinity[3] = true
affinity[5] = true

But after this commit, this table:
local affinity = { [3] = true, [5] = true }

will now be accepted and all the missing keys up to uv_cpumask_size() will be treated as false in the thread_setaffinity call.

Not seeing your comments

From 415 line
  int min_mask_size = uv_cpumask_size();
  if (min_mask_size < 0) {
    return luv_error(L, min_mask_size);
  }
  int mask_size = lua_rawlen(L, 2);
  if (mask_size < min_mask_size) {
    mask_size = min_mask_size;
  }
  char* cpumask = malloc(mask_size);

can be simplify to
  int mask_size = uv_cpumask_size();
  if (mask_size < 0) {
    return luv_error(L, mask_size);
  }
  char* cpumask = malloc(mask_size);

LGTM.


.Net: nodebook sample for 1.0.0-beta

Please add notebook samples for dotnet 1.0.0-beta. That still using the preview and there are several code doesn't work as it is.

@kenakamu Thanks for reporting. All notebook samples for dotnet 1.0.0-beta will be updated today.

@kenakamu Meanwhile, you can check our syntax examples, they are aligned with new version 1.0.0-beta1:
https://github.com/microsoft/semantic-kernel/tree/main/dotnet/samples/KernelSyntaxExamples


Revert "fix(deps): update dependency chemicaltools to v1.2.11"

Reverts njzjz/chemicaltools-web#720

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The content server has unexpectedly rejected the request with: InternalServerError

Describe the bug
I have a SWA that has been running actions/builds successfully. Starting yesterday evening the builds have all been failing.
They run on a schedule via:
on:
  push:
    branches:
      - master
  pull_request:
    types: [opened, synchronize, reopened, closed]
    branches:
      - master
  schedule:
    - cron: "*/60 * * * *"

I found this morning if I make a change and push to cause a build manually, it does succeed. So it seems it might be related to the schedule/cron trigger.
Another difference I notice in the logs is that the cron triggered builds have a line (both on the successful & failed builds) that I do not see in the builds that ran from a push. Since it shows in both the successful and failed builds I can't say for sure if it's related, but it might be a clue.
This is what I see in the failed cron triggered action/build:
Failed to parse GitHub Event Json (/github/workflow/event.json). Proceeding
Could not get event info. Proceeding
The content server has unexpectedly rejected the request with: InternalServerError

This is what I see in the successful cron triggered action/build:
Failed to parse GitHub Event Json (/github/workflow/event.json). Proceeding
Could not get event info. Proceeding
Starting to build app with Oryx
Azure Static Web Apps utilizes Oryx to build both static applications and Azure Functions. You can find more details on Oryx here: https://github.com/microsoft/Oryx
Oryx will build app with the following custom override command: yarn run build
---Oryx build logs---
continues...

These lines are NOT in the logs on the builds triggered from a push (and they succeed):
Failed to parse GitHub Event Json (/github/workflow/event.json). Proceeding
Could not get event info. Proceeding

Incase its needed (but it looks like it doesn't get this far), the build does this:
node build/build.js && hugo --ignoreCache && yarn run clean
The node script grabs a bit of data from an api and writes file that hugo uses.

Hey @smakinson thanks for bringing this up, we will take a look!

Hi @smakinson we just deployed a fix for this. Can you please check if your deployments are succeeding now?
Also linking related issue #582.

@joslinmicrosoft I see they have been succeeding since about 16 hours ago. Thank you for the quick fix!!


Add steps to setup, install and run deployment environment.

We would also need to add the step to run setup.py file on developers' machines: python setup.py install

We need to break this issue in multiple small issues


Add abstraction for private symbols

Add the following runtime functions:

getPrivate
setPrivate
hasPrivate
deletePrivate

(These are all own property)
The motivation is that we can then use a WeakMap if it is natively
supported.

@johnjbarton Just the last commit... There are already PRs for the previous commits.


Correct spec examples of subroutine definitions

Summary
The specification still had the old form of subroutine definitions
listed, where qubit arguments were specified separately to the classical
ones.  This was outdated by commit cc9bbc7, and this commit brings the
spec in line with both the grammar and the paper.

Details and comments
Judging by Steven's comment in #217 (https://github.com/Qiskit/openqasm/pull/217#issuecomment-852476827), this change happened last-minute as the paper went out the door, and that's presumably how the discrepancy arose.
Related to #284.

@steleman I am not entirely sure I understand that statement regarding the analysis becoming context dependent; implementation details aside, if the type system is expressive enough to clearly distinguish which types are classical and which ones are quantum, I don't believe any context information would be required to make the split automatically. To me, the syntax distinction to me feels like moving something part of what I would usually expect to be reflected in the type system into the grammar. Am I misunderstanding your comment, or am I missing something about the implementation or future evolution of the type system?


Making onKeyDown of slate-lists more customizable

I'd like to propose making onKeyDown event handler of slate-lists package more customizable.
For example, in my app, I would like to:

Only enable Tab shortcut if the selection is already in a list
Disable "Escape" key blurring the editor

Two approaches that I see:

Adding an argument like hotkeys, which would be a Record of hotkeys and handlers. The currently implemented hotkey handlers would be the default config, and the user-provided hotkey handlers would override the defaults when provided.
Exporting more of the slate-lists package to allow users to build their own onKeyDown handlers more easily. The normalizations directory is already exported, so maybe exporting transformations and lib would also be ok?

I'd be happy to open a PR for this, if you agree with one of these options, or if you propose a different approach for customization.

Hey @hejtful!
Sorry for the delayed response.
I'm going to work through the reported issues this week and most definitely will take a look at this one.
👨💻


Use ==/!= to compare str, bytes, and int literals

Output: https://travis-ci.org/3b1b/manim/builds/522690304#L252

I've really been slacking on getting real tests working, so this should suffice while until I get around to it.


wallet-ext: improve gas estimations for nft and coin transfers

wallet-ext: fix crypto mock in test setup

it breaks the tests since now crypto seems to be defined

ts-sdk: adds method to estimate gas cost and suggested budget to signer
also fixes some edge cases with pay txs (take into account that only the first coin is used for gas)
wallet-ext: improve gas estimations for nft transfer

fixes edge cases and uses new method from signer
use Alert component for errors

wallet-ext: improve token transfer gas budget estimations

uses new method from signer to estimate gasCost and suggested gasBudget
updates token validation to include more cases
uses Alert for errors in send tokens form

closes APPS-149

Thanks for the review @gegaowp, I think I addressed the comments, let me know if there is anything else!

all changes except those that are related to gas estimation using dryRun were split to other PRs https://github.com/MystenLabs/sui/pull/6695, https://github.com/MystenLabs/sui/pull/6701, https://github.com/MystenLabs/sui/pull/6703, https://github.com/MystenLabs/sui/pull/6706. Gas estimation is blocked until gasBudget and gas cost can be ignored.


Scan Results Page: Code Update

Need to look into updating how the CSS is written for the scan results page, more specifically the overview panel on the right hand side. On smaller screens the way things are coded with calc and position: fixed and static, the menu is not accessible and you cannot close the menu via keyboard input.

Mobile category menu needs to be updated anyway because it's not accessible via keyboard and there is no way to close or exit the menu.
Melanie has some code from a separate project that will keep the functionality we have for the categories menu on a mobile screen the same + is accessible.

[ ] Make mobile category menu fully accessible
[x] Go through scan results page CSS. I noticed some unnecessary styling being applied in places.
[x] Edit "Expand/Close Button" height. Seeing a cropping issue in Chrome, Edge. FF:

Just making some notes here after investigating this further. For the mobile category menu, the accessibility issue we have is that when you've opened the menu via keyboard and navigate to one of the anchor links, when you hit enter, the category menu doesn't disappear and focus moves to the page underneath it, to the category you navigated to, and so you can't escape the category menu to get to the results content.

This is going to take two PRs split across the hint and webhintio repo.

@sarvaje I just met with Melanie to talk about what's happening on the mobile view for the scan results page.
When a user has the categories expanded like this:

And is using the keyboard to tab through the the categories, if they hit "enter" to tab into a section, the categories menu is not closing when enter is being pressed. This is only happening via the keyboard, if someone is using a mouse to click the categories, a click event is happening. So we need an event for focusing and hitting enter that then closes the category menu.
Let me know if that makes sense and @molant let me know if I should open a separate issue for next sprint that focuses on the JavaScript.

@ststimac it makes sense :)

let me know if I should open a separate issue for next sprint that focuses on the JavaScript.

If you have more tasks than this one then open a new task so we can track it accordingly. If it is just this one then don't think it's worth it.
Thanks!

@molant I have finished the other two tasks that were a part of this overall issue so I will create a new one.


Compute color to Var

fixes #274

Material nodes now have Var<Float32> or Var<Vector4> input pins -> VarToComputeX node can be deleted
ShaderFX graphs can be properly cached -> instant load once compiled, also after restart
Factory node pins use a compiled delegate expression instead of reflection to write to pins -> about 50x faster
Added factory node pins that can convert between types

Changes:

ValueMap and ColorMap are now implemented with ShaderFX
Material nodes moved into ShaderFX document because they now depend on it
Forward of Var is in Rendering document because it forwards the nodes from the factory which has this type as pin type

Review and ToDo:

[ ] Find proper name for Var<T>, e.g. GPUValue<T> and how are functions called? GPUFunc<A, B>? Anything shorter?
[ ] help @texone to update his ShaderFX nodes, the type rename could wait for that
[ ] @antongit check current help patches with Material nodes
[ ] @antongit can we remove DiffuseMap, EmissiveMap, ... nodes?

I expected LiveComputeFloat and LiveComputeColor to be gone?

Yep, they are deleted now:  https://github.com/vvvv/VL.Stride/pull/347/commits/3fd25dc0c0d74042efb79b4b782516cf02e53b40


new image: gomplate

New Image Pull Request Template
Related: #2497

[x] The Image is smaller in size than its common public counterpart.
[ ] The Image is larger in size than its common public counterpart (please explain in the notes).

Notes:
Image Vulnerabilities

[ ] The Grype vulnerability scan returned 0 CVE(s).
[ ] The Grype vulnerability scan returned > 0 CVE(s) (please explain in the notes).

Notes:
Image Tagging

[ ] The image is not tagged with version tags.
[ ] The image is tagged with :latest
[ ] The image is not tagged with :latest (please explain in the notes).

Notes:
Basic Testing - K8s cluster

[ ] The container image was successfully loaded into a kind cluster.
[ ] The container image could not be loaded into a kind cluster (please explain in the notes).

Notes:
Basic Testing - Package/Application

[ ] The application is accessible to the user/cluster/etc. after start-up.
[ ] The application is not accessible to the user/cluster/etc. after start-up. (please explain in the notes).

Notes:
Helm

[ ] A Helm chart has been provided and the container image can be used with the chart.  If needed, please add a -compat package to close any gaps with the public helm chart.
[ ] A Helm chart has been provided and the container image is not working with the chart (please explain in the notes).
[ ] A Helm chart was not provided.

Notes:
Processor Architectures

[ ] The image was built and tested for x86_64.
[ ] The image could not be built for x86_64 (please explain in the notes).
[ ] The image was built and tested for aarch64.
[ ] The image could not be built for aarch64. (please explain in the notes).

Notes:
Functional Testing + Documentation

[ ] Functional tests have been included and the tests are passing.  All tests have been documnted in the notes section.

Notes:
Environment Testing + Documentation

[ ] There has not been a request and/or there is no indication that this image needs tested on a public cloud provider.
[ ] The container image has been tested successfully on a public cloud provider (AWS, GCP, Azure).
[ ] The container image has not been tested successfully on a public cloud provider (AWS, GCP, Azure) (please explain in the notes).

Notes:
Version

[ ] The package version is the latest version of the package.  The latest tag points to this version.
[ ] The package version is the not the latest version of the package (please explain in the notes).

Notes:
Dev Tag Availability

[ ] There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')
[ ] There is not a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base') (please explain in the notes).

Notes:
Access Control + Authentication

[ ] The image runs as nonroot and GID/UID are set to 65532 or upstream default
[ ] Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres
[ ] The image requires a non-standard username or non-standard GID/UID (please explain in the notes).

ENTRYPOINT

[ ] applications/servers/utilities set to call main program with no arguments e.g. [redis-server]
[ ] applications/servers/utilities not set to call main program with no arguments e.g. [redis-server] (please explain in the notes)
[ ] base images leave empty.
[ ] base image and not empty (please explain in the notes).
[ ] dev variants is set to entrypoint script that falls back to system.
[ ] dev variants is not set to entrypoint script that falls back to system (please explain in the notes).

CMD

[ ] For server applications give arguments to start in daemon mode (may be empty)
[ ] For utilities/tooling bring up help e.g. –help
[ ] For base images with a shell, call it e.g. [/bin/sh]

Environment Variables

[ ] Environment variables added.
[ ] Environment variables not added and not required.

SIGTERM

[ ] The image responds to SIGTERM (e.g., docker kill $(docker run -d --rm cgr.dev/chainguard/nginx))

Logs

[ ] Error logs write to stderr and normal logs to stdout. Logs DO NOT write to file.

Documentation - README

[x] A README file has been provided and it follows the README template.

Error

terraform apply
var.target_repository
  The docker repo into which the image and attestations should be published.

  Enter a value: cgr.dev/chainguard/gomplate

module.latest-config.data.apko_config.this: Reading...
module.latest-config.data.apko_config.this: Still reading... [10s elapsed]

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: computing package locks
│
│   with module.latest-config.data.apko_config.this,
│   on config/main.tf line 12, in data "apko_config" "this":
│   12: data "apko_config" "this" {
│
│ resolving apk packages: for arch "loong64": error getting repository indexes: reading index
│ https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz: fetching https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz:
│ GET https://packages.wolfi.dev/os/loongarch64/APKINDEX.tar.gz (Range: bytes=0-): unexpected status code: 404
│ for arch "s390x": error getting repository indexes: reading index https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz: fetching
│ https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/s390x/APKINDEX.tar.gz (Range: bytes=0-):
│ unexpected status code: 404
│ for arch "386": error getting repository indexes: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):
│ unexpected status code: 404
│ for arch "riscv64": error getting repository indexes: reading index https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/riscv64/APKINDEX.tar.gz
│ (Range: bytes=0-): unexpected status code: 404
│ for arch "arm/v7": error getting repository indexes: reading index https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/armv7/APKINDEX.tar.gz (Range:
│ bytes=0-): unexpected status code: 404
│ for arch "ppc64le": error getting repository indexes: reading index https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/ppc64le/APKINDEX.tar.gz
│ (Range: bytes=0-): unexpected status code: 404
│ for arch "arm/v6": error getting repository indexes: reading index https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz:
│ fetching https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/armhf/APKINDEX.tar.gz (Range:
│ bytes=0-): unexpected status code: 404
│ for arch "amd64": getting indexes for "386" sibling: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):
│ unexpected status code: 404
│ for arch "arm64": getting indexes for "386" sibling: reading index https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: fetching
│ https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz: GET https://packages.wolfi.dev/os/x86/APKINDEX.tar.gz (Range: bytes=0-):
│ unexpected status code: 404
╵
╷
│ Error: Invalid function argument
│
│   on ../../tflib/publisher/chainguard.tf line 43, in resource "chainguard_image_repo" "repo":
│   43:   readme    = file(local.readme_filepath)
│     ├────────────────
│     │ while calling file(path)
│     │ local.readme_filepath is "images/./README.md"
│
│ Invalid value for "path" parameter: no file exists at "images/./README.md"; this function works only with files that are
│ distributed as part of the configuration source code, so if this file will be created by a resource in this configuration you
│ must instead obtain this result from an attribute of that resource.

Error details
1. Package Resolution Errors
The error message mentions that Terraform is unable to fetch the APKINDEX files for various architectures from the specified URLs, resulting in 404 errors.
unexpected status code: 404

2. Invalid File Path for README
This error relates to an invalid file path:
Invalid value for "path" parameter: no file exists at "images/./README.md"

Please take a look and let me know how I should approach the issue!


Transaction Type - BORROW and REPAY LOAN

I was also wondering whether we would also need transaction type - BORROW and REPAY LOAN for margin trading. (related issue https://github.com/eprbell/rp2/issues/46)
scenario 1) Borrow 1 BTC at $20000, Pay back 1 BTC at $15000 without any trading. This results in zero profit (for simplicity, there is zero margin loan interest)
scenario 2) Borrow 1 BTC at $20000 and sell it on spot at $20000. Buy back 1 BTC at $15000 and pay back. This results in $5000 profit.
I tried to map margin trading and I think it requires keeping track of current balance vs loan amount to actually compute profit/loss of margin trading.
if current balance (including loan) >= loan amount, margin trading cannot contribute any profit/loss. However, when current balance (including loan) < loan amount, that is when margin trading starts to affect your profit / loss
for scenario 1) current balance : 1 BTC >= loan amount: 1 BTC during the whole process so it does not affect profit/loss
for scenario 2) once you sell the borrowed BTC, current balance: 0 BTC < loan amount 1 BTC and it starts to affect profit / loss.
Also, you can notice that your borrow price and pay back price don't really matter. What matters are the trade prices when current balance < loan amount
ex ) Borrow 1 BTC at $20000. Sell 1 BTC at $25000. Buy 1 BTC at $15000. Pay back 1 BTC at $22000. This results in $10000 ($25000 - $15000).
Even for scenarios where you hold assets along with borrowed assets, current balance vs loan amount is all it matters.
scenario 3) Buy 2 BTC at $ 20000. Borrow 1 BTC at $ 20000. Sell 2 BTC at $ 15000. Pay back 1 BTC at $40000.
Initially, current balance: 2 BTC >= 0 BTC loan amount. Then it becomes  3 BTC >= 1 BTC. Next 1 BTC >= 1 BTC (after selling 2 BTC).
In this case margin trading doesn't contribute any profit/loss. And you lose ($20000 - $15000) x 2 from trading your wholly owned BTC assets.
So I think with BORROW and REPAY LOAN transaction types, we can keep track of loan amount. Also, I think rp2 would need additional calculations that incorporate the above logic to compute margin trading profit/loss

Thanks for starting the discussion on this (I haven't spent much time thinking about margin).
Initially I thought there may be a simpler way of representing margin in RP2:

add BORROW and REPAY types as you suggested
BORROW is an in-transaction type and REPAY is an out-transaction type
BORROW and REPAY transactions affect the in/out coin flow (including accounting method calculations) and the final balance
BORROW and REPAY transactions they are not taxable events (unlike in-transactions like EARN or out-transactions like SELL)
everything else stays the same. If you sell some coins, it just gets taxes according to the user-selected accounting method. With this approach we need to add the two types and make sure RP2 doesn't treat them as taxable: no other changes are needed.

However I then realized that borrowed and repaid coins affect accounting in a way that's not clear to me tax-wise.
For example, let's say we're using FIFO with the above example:

buy 1 BTC at $10000
borrow 1 BTC at $20000
sell 0.5 BTC at $30000
repay 1 BTC at $40000
sell 0.5 BTC at $30000

The question I have is: does the repaid coin come out of the FIFO queue or is there special / separate accounting for borrowed coins?
If the answer is FIFO queue:

0.5 repaid BTC has cost basis $10000 and the other 0.5 comes out of the borrowed coin at $20000
the last sell has cost basis $20000

If the answer is separate accounting for borrowed coins:

1 repaid BTC is the same BTC that was borrowed at $20000
the last sell has cost basis $10000

I don't know which way is correct according to tax law.

I don't know about tax law, but my guess would be to follow the second case (separate accounting). if we do FIFO, there are cases where things become problematic.
ex)

borrow 1 BTC at $ 10000
buy 1 BTC at $ 20000
sell 1 BTC at $ 15000
repay 1 BTC at $ 30000

Let's say we use FIFO to compute the above case. Then our first sell is $ 5000 profit. Then we REPAY and as REPAY is non-taxable there is no profit / loss *. So my overall profit / loss is + $ 5000 gain. However, in reality, I have invested $ 20000, but left with only $ 15000 and my overall profit / loss is - $ 5000 loss.

*BORROW and REPAY should be non-taxable events as you have mentioned and my

scenario 1) Borrow 1 BTC at $ 20000, Pay back 1 BTC at $ 15000 without any trading.

This scenario also validates that BORROW and REPAY should be considered as non-taxable events. If we start considering BORROW and REPAY as taxable events, then this scenario becomes $ 5000 profit / loss depending on how you perceive it, but clearly, no profit / loss has been made.

My conclusion is that borrow and repay prices don't contribute to cost basis. Only trade prices should be considered for tax computation, which is validated by one of the examples from my original post
ex ) Borrow 1 BTC at $20000. Sell 1 BTC at $25000. Buy 1 BTC at $15000. Pay back 1 BTC at $22000. This results in $10000 ($25000 - $15000).
We can change the borrow and repay prices to any numbers and the overall profit / loss wouldn't change. It will still be ($25000 - $15000) gain.
So if borrow and repay prices don't contribute to cost basis, they shouldn't be queued with other FIFO transactions like buy or sell. So having a separate accounting seems most appropriate.

Also, maybe this belongs to another issue, but transaction type - LEND might be also necessary for lending crypto.
So along with https://github.com/eprbell/dali-rp2/issues/96, currently 4 transaction types

REFUND
BORROW
REPAY
LEND

would need to added.

I agree with your criticism of option 1 (single queue), but there is also a problem with going with option 2 (separate accounting). Let me use your example to explain what I mean:

borrow 1 BTC at $20000
sell 1 BTC at $25000
buy 1 BTC at $15000
repay 1 BTC at $22000

You suggested this should result in $10000 ($25000 - $15000), which is reasonable, but to obtain this result you would have to sell a lot you don't have (the buy is after the sale). See this discussion for more details on this: https://ttlc.intuit.com/community/investments-and-rental-properties/discussion/using-lifo-method-for-cryptocurrency-or-even-stock-cost-basis/00/1433542

Forgot to mention we would also need a transaction type that is the opposite of LEND, which would be named something like RECOVER. (couldn't think of a better terminology)
Now, I was thinking about transactions that would involve LEND and RECOVER.
ex)

buy 1 BTC at $ 20000
buy 1 BTC at $ 30000
lend 1 BTC
sell 1 BTC at $ 25000
recover 1 BTC
sell 1 BTC $ 30000

I am guessing that for LEND and RECOVER, we do need to follow the FIFO principle.

the first lent 1 BTC will have cost basis of $ 20000
the first sell has cost basis $ 30000. So a loss of $ 5000 is recorded.
the second sell has cost basis $ 20000 as we are selling the recovered BTC. so this results in $ 10000 profit.

This led me to think about whether we also need to add transaction type - COLLATERAL(IZE) when doing margin trading.
ex)

buy 20 ETH at $ 1400 (spot price)
buy 20 ETH at $ 1500
collaterize 20 ETH and borrow 1 BTC  at $ 19000
sell 1 BTC at $ 20000 and buy 10 ETH at $ 2000
sell 20 ETH at $ 2400
sell 10 ETH at $ 2400
buy 1 BTC at $ 22000
repay 1 BTC at $ 24000
uncollaterize 20 ETH

If we do a cost basis analysis of the above example,

we are collaterizing 20 ETH with cost basis 20 x $ 1400.
the first sell of 1 BTC (loan) utilizes separate accounting method. So no profit / loss for the initial sell, but cost basis of $ 20000 is recorded for 1 BTC for margin trading.
the 20 sell of ETH at $ 2400 has cost basis 20 x $ 1500. So a gain of (20 x $ 2400) - (20 x $ 1500) = $ 18000 is recorded.
the 10 sell of ETH at $ 2400 has cost basis of 10 x $ 2000 as we are selling the 10 ETH that were bought using the money from selling the loaned 1 BTC. A gain of $ 4000 is recorded.
we are repaying with BTC that has cost basis $ 22000. So a loss of ($ 20000 - $ 22000) = $ 2000 is recorded.
uncollaterize 20 ETH with cost basis 20 x $ 1400.

I think the numbers all add up right.
So to summarize, I think we need the follow transaction types

REFUND
BORROW
REPAY
LEND
RECOVER
COLLATERIZE
UNCOLLATERIZE

You suggested this should result in $10000 ($25000 - $15000), which is reasonable, but to obtain this result you would have to sell a lot you don't have (the buy is after the sale)

It is just my personal opinion, but for margin trading accounting, things are opposite. For usual trades, cost basis is recorded when you buy. However, for margin trading, cost basis is recorded when you sell. So it makes sense for sell to come before buy. This is illustrated from the example that I have stated right above. I'll post a quote from my above cost basis analysis

the first sell of 1 BTC (loan) utilizes separate accounting method. So no profit / loss for the initial sell, but cost basis of $ 20000 is recorded for 1 BTC for margin trading.

For margin trading, your buy back transaction is the conclusive action. For usual trading, you selling transaction is the conclusive action.  This is just like for regular non-margin trading, when you buy and don't sell, you don't pay taxes. Moreover, selling initiates margin trading, while buying initiates regular trading.
Also, I hope my example from my previous post makes things clearer as it captures the essence of margin trading

ex)

buy 20 ETH at $ 1400 (spot price)
buy 20 ETH at $ 1500
collaterize 20 ETH and borrow 1 BTC at $ 19000
sell 1 BTC at $ 20000 and buy 10 ETH at $ 2000
sell 20 ETH at $ 2400
sell 10 ETH at $ 2400
buy 1 BTC at $ 22000
repay 1 BTC at $ 24000
uncollaterize 20 ETH

Basically, the above is an example of margin trading that longs ETH against BTC. As ETH price appreciates faster (% 20  price appreciation) than BTC (% 10 price appreciation), margin trading will generate 10% overall profit (gain from ETH - loss from BTC) using the borrowed money.

I understand your point (thanks for the examples) however I have a few thoughts:

before finalizing the spec we would have to get an official confirmation of the semantics of these operations (in other words we need to make sure we are spec'ing what the law says) and we would have to understand all corner cases (see example below)
if your interpretation is correct and we allow future cost bases, this will have major ramifications on the RP2 code base (especially the accounting engine): currently future cost basis is flagged as an error in RP2.
I'm still unclear how you would mix and match accounting styles. E.g. consider the following, using FIFO:

buy 2 BTC
sell 1 BTC
borrow 1 BTC
sell 1 BTC
Does the last sell come out of the bought lot or the borrowed lot and why?

Im no tax law expert, but I will post quotes from a few articles from tax services.

It’s expected that the profits and losses generated from margin trading are reportable as capital gains and losses, similar to other cryptocurrency disposals.

link: https://coinledger.io/blog/crypto-margin-trades-taxes

Thus, margin trading in and of itself is not taxable because borrowing crypto is not a taxable event. However, if you earn proceeds from margin trading or lending, it is most likely taxable.

link: https://tokentax.co/blog/taxes-on-crypto-margin-trading
These all seem to match our conclusions made from examples and cost basis analysis.

BORROW and REPAY are non-taxable events
We should only consider trade prices of margin loan assets as that is when one starts to accrue capital gain / loss

if your interpretation is correct and we allow future cost bases, this will have major ramifications on the RP2 code base (especially the accounting engine): currently future cost basis is flagged as an error in RP2.

While you could think from that perspective, another way to think of this is to use the basically the same RP2 code with the following modifications.

When we are trading margin loan assets, we assign to a tax lot when we sell them. Cost basis becomes the sell price
We remove them from the assigned tax lot when we either buy them back or deposit (receive gift, income, wages etc) the same asset.
We have capital gain if cost basis of sell  > cost basis of buy / deposit. Capital loss if cost basis of sell < cost basis of buy / deposit

So basically reverse process everything. These will still require some major changes, but the logic still stays pretty much the same, so these are relatively low stress changes rather than high stress changes. I will come back to these point with more concise examples when defining the formal spec requirements.

buy 2 BTC
sell 1 BTC
borrow 1 BTC
sell 1 BTC
Does the last sell come out of the bought lot or the borrowed lot and why?

I think you were meaning something like the following instead

borrow 1 BTC
buy 1 BTC
sell 1 BTC

I would say the sell comes out from the bought lot and not the borrowed lot even though buying comes later than borrowing.
I will give my reasonings using the below example
ex)

borrow 1 BTC at $ 20000
buy 1 BTC at $ 21000
sell 1 BTC at $ 22000
repay 1 BTC at $ 23000

let's assume the sell comes out from the borrowed instead (which I consider to be wrong).

Our first sell assigns cost basis of $ 22000 of and assigns to a separate accounting tax lot for margin trading.
Now we have to repay. However, we still haven't cleared out tax lot for margin trading.

One could argue that we could use the buy to clear the tax lot and the numbers come out right too.

use the buy to clear the margin accounting tax lot. cost basis of sell $ 22000 > cost basis of buy $ 21000. Gain of $ 1000

Indeed we have gained $ 1000 from the above example.
However, the logic order doesn't make sense. I have shown from various examples that for margin trading

selling margin asset initiates margin trading.
buying back concludes the margin trading.

the above example has selling coming after buying, not before, and this basically contradicts the principles of margin trading.
So the correct way to compute cost basis analysis for the above example would be

increment current balance and margin loan balance. Current balance: 1 BTC. Margin loan balance 1 BTC
add buy to regular trading tax lot with cost basis $ 21000. Current balance: 2 BTC. Margin loan balance 1 BTC
sell removes from regular trading tax lot. ($ 22000 - $ 21000) gain made. Current balance: 1 BTC. Margin loan balance 1 BTC
repay. Current Balance 0 BTC. Margin loan balance 0 BTC

Example Cases
ex 1)

Borrow 1 BTC at $20000
Pay back 1 BTC at $15000

Cost basis analysis

Current balance: 1 BTC. Margin loan balance:  1 BTC
Current balance: 0 BTC. Margin loan balance: 0 BTC

Total gain / loss: 0

ex 2)

Borrow 1 BTC at $20000
Sell 1 BTC at $20000
Buy 1 BTC at $15000

Cost basis analysis

Current balance: 1 BTC. Margin loan balance: 1 BTC
Selling results in current balance < margin loan balance. Margin trading triggered. Sell assigned to margin trading tax lot with cost basis $ 20000. Current balance 0 BTC. Margin loan balance: 1 BTC.
Cost basis of sell $ 20000 > Cost basis of buy $ 15000. Gain of ($ 20000 - $ 15000) = $ 5000 made. tax lot cleared. Current balance: 1 BTC Margin loan balance: 1 BTC

Total gain / loss : $ 5000

ex 3)

Borrow 1 BTC at $20000
Sell 1 BTC at $25000
Buy 1 BTC at $15000
Pay back 1 BTC at $22000

Cost basis analysis

Current balance: 1 BTC. Margin loan balance: 1 BTC
Selling results in current balance < margin loan balance. Margin trading triggered. Sell assigned to margin trading tax lot with cost basis $ 25000. Current balance 0 BTC. Margin loan balance: 1 BTC.
Cost basis of sell $ 50000 > Cost basis of buy $ 15000. Gain of ($ 25000 - $ 15000) = $ 10000 made. tax lot cleared. Current balance: 1 BTC. Margin loan balance: 1 BTC
Current balance: 0 BTC. Margin loan balance: 0 BTC

Total gain / loss: $ 10000

ex 4)

Buy 20 ETH at $ 1400 (spot price)
Buy 20 ETH at $ 1500
Collaterize 20 ETH and borrow 1 BTC at $ 19000
Sell 1 BTC at $ 20000 and buy 10 ETH at $ 2000
Sell 20 ETH at $ 2400
Sell 10 ETH at $ 2400
Buy 1 BTC at $ 22000
Repay 1 BTC at $ 24000
Uncollaterize 20 ETH

Cost basis analysis

Buy assigned to a regular tax lot with cost basis 20 x $ 1400. Current balance: 20 ETH. Margin loan balance: 0 ETH.
Buy assigned to a regular tax lot with cost basis 20 x $ 1500. ETH: Current balance: 40 ETH. Margin loan balance: 0 ETH.
20 ETH with cost basis 20 x $ 1400 removed from the FIFO queue and reassigned to a ETH collateral lot (hash map). ETH: Current balance: 40 ETH. Margin loan balance: 0 ETH.  BTC:  Current balance: 1 BTC. Margin loan balance: 1 BTC.
Selling results in current balance < margin loan balance. Margin trading triggered. Sell assigned to a margin tax lot with cost basis 1 x $ 20000. BTC: Current balance: 0 BTC Margin loan balance: 1 BTC.  Buy assigned to regular tax lot with cost basis 10 x $ 2000.  ETH: Current balance: 50 ETH Margin loan balance: 0 ETH.
Sell removes 20 ETH with cost basis 20 x $ 1500 from the regular tax FIFO queue. Gain of (20 x $ 2400 - 20 x $ 1500) = $ 18000. ETH: Current balance: 30 ETH. Margin loan balance: 0 ETH.
Sell removes 10 ETH with cost basis 10 x $ 2000 from the regular tax FIFO queue. Gain of (10 x $ 2400 - 10 x $ 2000) = $ 4000. ETH: Current balance: 20 ETH. Margin loan balance: 0 ETH.
Buy clears margin tax lots. Loss of (cost basis of sell $ 20000 - cost basis of buy $ 22000) = - $ 2000. BTC: Current balance: 1 BTC. Margin loan balance: 1 BTC
Current balance 0 BTC. Margin loan balance: 0 BTC
remove 20 ETH with cost basis 20 x $ 1400 from the collateral lot and queue back into the regular FIFO queue. ETH: Current balance 20 ETH. Margin loan balance: 0 ETH

Total gain / loss: Steps 5,6,7 generated gain / loss $ 18000 + $ 4000 - $ 2000 = $ 20000


Setting up Battlefield 2142 Reclamation

Opening a new issue to see if I can get the setup of the old Battlefield 2142 game automated on here, then added to Steam as a game shortcut.
Here's a general breakdown of what I would have to do.

Have Lutris Installed
Install Wine-GE
Download prerequisite files for Battlefield 2142 Lutris runner
Install Battlefield 2142 via Lutris, with Reclamation Project patches
Make a note in the script or add-on script that a reboot and then opening of the game in game mode will fire off the proper scripts to connect to the unofficial servers

Note that I will most likely get on this once the GPD Win Mini testing has completed.

Required parts for the Lutris runner:

BF2142 Hub
1.51 patch
archive.org bf2142 cd for installer

The Lutris runner has these added. Closing for now.


High CPU usage

I am using the module in polybar. This is the module config:
[module/layout]
type = custom/script
exec = xmonad-dbus
interval = 5
tail = true

and this is parts of my xmonad.hs:
myLogHook :: DC.Client -> PP
myLogHook dbus = def {
    ppOutput = D.send dbus

-- Print icons based on the layout
  , ppLayout =
        \layout -> case layout of
          "Spacing ResizableTall"        -> "\985629 "
          "Spacing Mirror ResizableTall" -> "\986732 "
          "Spacing Full"                 -> "\986719 "
          _                              -> "\985629 "

  -- Disable Everything apart from layout
  , ppTitle   = const ""
  , ppCurrent = const ""
  , ppVisible = const ""
  , ppHidden  = const ""
}

While idling it's taking up 15% CPU

strange, are you sure that xmonad-dbus is the culprit, does your cpu usage goes down if you stop using it, it works following way, xmonad sends dbus messages via xmonad-dbus library, and there is separate process that reads those messages from dbus called xmonad-dbus which is used by polybar, could you please stop polybar or reconfigure so it's not used anymore to see which of the side causes high cpu usage, it seems like xmonad is generating too many messages which causes this cpu usage spike

yeah if i stop using it, my cpu usage drops down to 2-3%. This is irrelevant, but is there any way to log everything to a file say at /tmp/xmlog?

not sure what you mean by logging, you can play around with source code and write all messages to file or you can write your log hook for xmonad to check how many messages it generates per second, either way something is definitely wrong with either your dbus or xmonad or something in between, it can even be underlying haskell dbus library that xmonad-dbus uses under the hood

yeah, thanks I figured it out. Also I am 90% sure that the high cpu usage wasn't caused by your dbus module but another one for Bluetooth. Again I am not sure


editor.document.save always returns true in command activate

The save step in the activate function always returns true.
If you edit a file and press activate and quickly type something immediately after, then the error comes up, the exception that is raised is caught somewhere and not raised to the command.ts file.

i do experience another issue where after clicking the activate and it does the save. Then after activate it it returns back to the "old" source. It seems to stuff up in SE24 as well. See https://im7.ezgif.com/tmp/ezgif-7-d628d733f1e8.gif
I need to do another edit in SE24 to return back to "normal" state. Not sure this is a bug in ADT or how it's called from VSCode. I see that after the save, in Eclipse it does a get for inactive version, then an unlock before it requests the activation

Never seen this. Are you maybe able to reproduce publicly (i.e. git repo or sharable code, hopefully for the trial image)?

@uxkjaer now that I look better, when you have a syntax error like that the class is never saved.
You can save one with syntax errors, but with this one the file abstraction falls apart and the backend is not able to separate it in methoids and declarations, so have no place to save it to


Should we be calling it an NLP library?

It is a general library that can be used for NLP or graph learning. Calling it an NLP library might be too restrictive. @mboratko @ssdasgupta What do you think?

Proposal: An open-source research library for NLP or graph learning, built on PyTorch & TensorFlow
Let me know if this sounds good

Sounds good. Perhaps, 'NLP and graph learning'?

Agree that NLP is too restrictive, I like the idea of NLP and graph learning.


Docker image for this Xteve version

Is your feature request related to a problem? Please describe.
No this is not really a problem but more a request for support for downloadable docker image.
Describe the solution you'd like
I wonder if there are docker images available.
Describe alternatives you've considered
You are the only one who is updating this application now with lots of fixes.

Hello 👋
TL;DR: Plan to fix a bug or two, create a new release and will try to make it and update the readme file accordingly.
I am not really familiar with docker (yet).
Wonder if it is possible to create a new, linux-comaptible docker image on my windows machine, or should I install some linux distro on top of a virtual machine...
In any case, sorry for the delay, will learn the topic and try to do this.
@SCP002 Link for myself: howto

Hello 👋 TL;DR: Plan to fix a bug or two, create a new release and will try to make it and update the readme file accordingly.
I am not really familiar with docker (yet).
Wonder if it is possible to create a new, linux-comaptible docker image on my windows machine, or should I install some linux distro on top of a virtual machine... In any case, sorry for the delay, will learn the topic and try to do this.
@SCP002 Link for myself: howto

No its already awesome you are improving the app and if the docker comes as well it would be great.
So i dont mind the delay. Im also not familiar with it sorry.
I only see alot of people using github as automation for docker i think with github actions.
Then it will build new releases everytime you update the app.

@deku-m Once again, sorry for the delay. Check it out https://github.com/SCP002/xTeVe#docker


Unable to run example caused by 'status' missing from api response

I am getting an error when running the example code. it seems like the api response is missing this status field.
$ python ./evtest.py
Traceback (most recent call last):

 ...

  File "C:\Users\Apollo\Temp\evtest.py", line 11, in run
    stations = await api.async_get_stations()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Apollo\AppData\Local\Programs\Python\Python313\Lib\site-packages\evdutyapi\evduty_api.py", line 61, in async_get_stations
    stations = [StationResponse.from_json(s) for s in json_stations]
                ~~~~~~~~~~~~~~~~~~~~~~~~~^^^
  File "C:\Users\Apollo\AppData\Local\Programs\Python\Python313\Lib\site-packages\evdutyapi\api_response\station_response.py", line 19, in from_json
    status=ChargingStatus(data['status']),
                          ~~~~^^^^^^^^^^
KeyError: 'status'

The api does returns 200 with the following payload
[
    {
        "name": "...",
        "address": {
            "street": "...",
            "city": "...",
            "postalCode": "...",
            "formattedAddress": "...",
            "state": "...",
            "taxState": "..."
        },
        "ownerId": "...",
        "latitude": 0.0,
        "longitude": 0.0,
        "initialLatitude": 0.0,
        "initialLongitude": 0.0,
        "id": "...",
        "isRoot": true,
        "isOwner": true,
        "isPartialOwner": false,
        "terminals": [],
        "hours": []
    }
]

My car was plugged in when making this request, I would have expected to find "status": "inUse" within this payload.
I found this payload from the async_get_stations method in the EVDutyApi class
    async def async_get_stations(self) -> List[Station]:
        await self.async_authenticate()
        async with self.session.get(f'{self.base_url}/v1/account/stations', headers=self.headers) as response:
+           print(response.status)
+           print(await response.json())
            await self._log("async_get_stations", response)
            await self._raise_on_get_error(response)
            json_stations = await response.json()
            stations = [StationResponse.from_json(s) for s in json_stations]
            await self._async_get_terminals(stations)
            await self._async_get_sessions(stations)
            return stations

The station.status field is a summary of the terminals statuses.
In your log, it seems like there's no charging terminals for this station.
"terminals": []
I will remove the station.status field since it can be computed from terminals statuses.

Field removed in commit
https://github.com/happydev-ca/evduty-api/commit/27b6b0dcb0a1e470c9c311de2464bdfb80f9f7d2


remove xfail from kitura 5.1

underlying issue was addressed in https://github.com/apple/swift-package-manager/pull/3713

@swift-ci test

also: https://github.com/Kitura/Kitura/issues/1559

PASS_Kitura_4.0_BuildSwiftPackage.log
PASS_Kitura_5.1_BuildSwiftPackage.log


Does not work on mobile Firefox

Device Name: Shift Phone
Device Version: 6m
Browser Name: Firefox
Browser Version: 68.0
NoSleep.js Version: v0.9.0

Expected Behavior
I expect that the live demo keeps my screen from going black when I click the button and the background turns green.
Actual Behavior
The screen goes to sleep.
How Do We Reproduce?
I don't know if you can reproduce it, I was a bit surprised that I seem to be the only one with this. It works in chrome, my firefox doesn't turn off when I am on youtube, but surprisingly it also turns the screen off when I am running this site:
https://gist.github.com/dmlap/5643609 (I added loop to the video tag and pressed play, still goes to sleep after a while).
Maybe it has something todo with the fact that I installed adblock plus there but I deactivated it and it still happened. And also it seems to work on youtube with adblock on.

I can confirm that nosleep.js does not work on firefox 68.0 on android 8.1.0.

For what it's worth, there is a webcomponent WakeLock repo here. Disclaimer: I am the author.

Hello.
I can confirm that it does not work either using Firefox Browser 68.3.0 on Android 9 Pie.
Is there any trick to make it work without using that web component?
Thanks!

@madeInLagny I could not make your solution work on the latest version of Firefox android. There must be a way as Firefox does not go to sleep when watching a video.
Has anyone found a solution?

Hi, I could fix this by commenting the line
this._addSourceToVideo(this.noSleepVideo, 'webm', webm)

Is this still a problem with the latest version 91.2.0? It seems to work for me on two different Android devices (using Android 10). For an older version I was able to reproduce the problem I think it was 89.0 but not 100% sure.
(
Be aware of caching as I initially played around with source modification too and couldn't get it working, but after clearing the caches it worked (using npm pack to create a local distribution nosleep.js-0.12.0.tgz and then npm install nosleep.js-0.12.0.tgz in my app to install it). And so I digged in code in firefox that seems to detect the audio part and decides not to lock the screen if no audio is available. See the code comment here and the comment in this repo containing no sound. See also these firefox tests indicating that this is expected behaviour. But likely they use different code for their mobile browser as it seems to be working now. Not sure.
)

Seems to intermittently be an issue on Firefox 99.2.0 on Android.

I have version 99.2.0 for Android 11 here too and nosleep is working for me. Really strange...

I suspect this could be caused on some devices by the (default?) blocking of auto-play media.
This is what I encountered on Firefox 102.0 on Ubuntu, with the browser informing me that it had blocked auto-play media.


CSS3 marquee support.

CSS3 marquee support.
http://www.w3.org/TR/css3-marquee/

This issue was imported from Google Moderator
Moderator votes: +15
Issue added by Mark T on 2013-06-19
To vote this issue up or down, simply include +1 or -1 in your comment.

-1

-1

Development of the marquee features of CSS has been abandoned.

:+1:

+1

no agree with @xtian, caniuse is support table, not a reference, an some unoff features are present in it, like http://caniuse.com/#feat=css-zoom

+1

+1

+1

Available via MDN: https://caniuse.com/?search=marquee esp. https://caniuse.com/mdn-html_elements_marquee


Migrating integration from Vacuum entity to Lawn Mower ?

Home Assistant 2023.9 introduced a new type of entity to officially support Lawn Mower with a dedicated integration.
https://www.home-assistant.io/integrations/lawn_mower/
So, it's not relevant anymore to use vacuum entity for this integration.
Are you planning to migrate to this new behavior ?

Duplicate to #541


TextArea component filename

Package
filament/forms
Package Version
v2.0
Laravel Version
v8.17
Livewire Version
No response
PHP Version
PHP 8.1
Bug description
Everything was running locally but I ran into an error on a staging server - Class "Filament\Forms\Components\TextArea" not found.
It turns out this is due to the file for the TextArea component does not have a PascalCase filename. It is Textarea.php, and this can cause issues across servers with different capitalization configuration.
I'm happy to do a pull request for this but for something so trivial I'm not sure if that's just more work on the maintainer's end.
Thanks!
Steps to reproduce
No response
Relevant log output
No response

Thank you, this will be fixed in the next version.

As on the Mozilla website - Textarea is all 1 word - https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

My bad, the fact that it worked locally on MacOS alongside the other pascal case component names threw me off. You're right. Thanks.

@iancallahan I just had the same issue. TextArea works OK locally on Win 10, fails on deployment via ubuntu docker image. Luckily your post here helped me out. Thanks.

Class names, function names etc are historically case-insensitive in PHP, although this could differ from environment to environment. Best to use PHPStan or Psalm to do these sort of checks for you.


Documentation tool chain switched to GenPackageDoc (replacement for S…

…phinx)

Hi Holger,
thank you for your pull request.
I did not review all 34 files. I will go in details, if we observe problems.
Thank you,
Thomas


deployer: build from cli image, not base

deployer base image needs to be cli as it merely copies binary from it

cc @LorbusChris


EU Frankfurt region is missing

It was added in October: http://aws.amazon.com/about-aws/whats-new/2014/10/23/announcing-the-aws-eu-frankfurt-region/

Closing this old issue. The region was added a while ago


Windows on top

📝 Keep a window above other windows
Add a feature to keep a window above other windows by right-clicking on an icon and select an application running, or a keyboard shortcut. I currently use the TopMost control application that does this task and I would like it to be integrated to PowerToys.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Great idea, tracked in issue #13


onEdgeUpdate never called on automatic created edge

Versions
"react-flow-renderer": "^9.5.3"
"react": "^16.3.2"
"react-dom": "^16.3.2"

Issue
I'm creating automatically some arrow on react-flow view. I have defined an onEdgeUpdate handler following this examples https://reactflow.dev/examples/updatable-edge/.
When i'm trying to update the destination of this edge, the handle onEdgeUpdate is never called.
The strange part is that when i'm creating a new edge of the react-flow view, i can update it and all works fine.
Example of the automatically created edge
{
  arrowHeadType: "arrow"
  data: {…}
  id: "flow_20"
  source: "server_3"
  sourceHandle: "2"
  style: {strokeWidth: 1.5}
  target: "server_2"
  targetHandle: "1"
  type: "bezier"
}

I was passing props onEdgeUpdate dynamically depending on readOnly boolean and that was causing the issue.
Setting nodesConnectable to false i enough to restrict interaction on read only mode.


Implementation of Generic Timelock (fixes #239)

Fixes #239
🚀 Description
Implementation of a generic Timelock that locks ether and any tokens sent to it until after releaseTime. I put this in lifecycle cause I wasn't quite sure where it should fit.

[x] 📘 I've reviewed the OpenZeppelin Contributor Guidelines
[x] ✅ I've added tests where applicable to test my new functionality.
[x] 📖 I've made sure that my contracts are well-documented.
[x] 🎨 I've run the JS/Solidity linters and fixed any issues (npm run lint:all:fix).

Hi @nedodn, thanks for your contribution!
I noticed your code is very close to that of the Escrows, and think this is a great candidate for a ConditionalEscrow, a TimelockedEscrow could inherit from Conditional, store the releaseTime in the constructor, and implement the logic in withdrawalAllowed. Do you think you could make those changes?

After taking a closer look, I noticed this contract also supports tokens, which the Escrows currently do not. I think extending them for these kinds of purposes makes a lot of sense, I'll open an issue to discuss that so that and then resume the implementation.

Closing since we still need to figure out a good TokenEscrow model.


latest SFDX command warning issue SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.

(node:2329) Warning: Deprecated environment variable: SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.
(Use node --trace-warnings ... to show where the warning was created)
(node:2329) Warning: Deprecated environment variable: SFDX_DISABLE_AUTOUPDATE. Please use SF_DISABLE_AUTOUPDATE instead.
im getting the above warning while running the latest SFDX Commands in my pipeline which is running under the agent "ubuntu" should i be worried about this waring or i need to set any environment variables while running the command in the pipeline? please help me to resolve this issue.

Do you have that env (SFDX_AUTOUPDATE_DISABLE) set in your CI environment?  If so, you can update it like the warning says to avoid seeing the warning.
If you don't set that env, I'd be really interested in where it's coming from (and what version of the CLI your CI is using) because we removed all our uses of it.  https://github.com/search?q=org%3Asalesforcecli+SFDX_AUTOUPDATE_DISABLE++NOT+is%3Aarchived&type=code

Hi @mshanemc nope i didn't set any environment variables im just installing the latest CLI using this command "npm install --global sfdx-cli@latest-rc " after runnning this installation command in my CI CD pipeline im running the jwt login and project deploy start command so when im running those command im seeing this warning in my CI CD pipeline even though i didn't set any environmental variables.

I'm not able to replicate this with what's in RC right now sfdx-cli/7.199.7 darwin-x64 node-v18.13.0.
We did recently add the warnings about old envs, so I'm 100% sure this is coming to that change, but I can't figure out how you got to it since no CLI code refers to that variable anymore.
I do see various other people's code on github that sets it.  Maybe your CI or a plugin uses the env?  https://github.com/search?q=SFDX_AUTOUPDATE_DISABLE&type=code

In my CI CD pipeline i have two set of stages one for QA validation and another one for UAT Validation
   In QA we did added a plugin for to scan the lwc apex and aure code the plugin is Salesforce code analyzer this is the installation command which im using -->  "sfdx plugins:install @salesforce/sfdx-scanner" and we are running the scanner command to scan the code --> "sfdx scanner:run --target "**/classes/**" " and after this step we are running the Jwt login and deployment command so in that stage only where we running the sfdx scanner plugin there we getting this warning which i mentioned the earlier command

      In UAT validation where we didn't run the scanner plugin to scan the code there is no warning showing for the sfdx commands.

so the issue is with where im running sfdx scanner plugin command
sorry for not telling you the issue properly at start.

im using the latest cli only in CI CD pipeline but yeah lets see it''ll go away in future or not and thanks for your help in this issue and has you mentioned ill ignore this warning for now

(node:7284) Warning: Deprecated environment variable: SFDX_JSON_TO_STDOUT. Please use SF_JSON_TO_STDOUT instead.
(Use node --trace-warnings ... to show where the warning was created)
TypeError: this.config.getPluginsList is not a function


Extension does not load - TypeError: Cannot destructure property 'selectedModelInfo' of '(0 , a.useMemo)(...)' as it is undefined.

After installing the extension and click on the Claude Dev icon an empty window pane is all that is displayed.
There are no errors in the UI.

VSCode 1.92.2
macOS

Looking at the developer console I see a few errors from the extension:

TypeError: Cannot destructure property 'selectedModelInfo' of '(0 , a.useMemo)(...)' as it is undefined.
    at Gb (main.js:2:1373227)
    at mi (main.js:2:77627)
    at Cs (main.js:2:91853)
    at wl (main.js:2:138161)
    at vc (main.js:2:126384)
    at bc (main.js:2:126312)
    at mc (main.js:2:126175)
    at ac (main.js:2:122955)
    at rc (main.js:2:121506)
    at E (main.js:2:755529)
ds @ main.js:2
n.callback @ main.js:2
$a @ main.js:2
Sl @ main.js:2
vl @ main.js:2
yl @ main.js:2
(anonymous) @ main.js:2
kc @ main.js:2
rc @ main.js:2
E @ main.js:2
_ @ main.js:2
main.js:2 Uncaught TypeError: Cannot destructure property 'selectedModelInfo' of '(0 , a.useMemo)(...)' as it is undefined.

Did you use another branch that used a different model? This should only happen if your local state had a provider that wasn't the 3 claude dev offers. If not then I'll need to investigate further

I did! I first tried a fork to see if I could get it working with Ollama / any OpenAI compatible endpoint.
I thought removing the extension, restarting vscode would have been enough?


Add support for character device GPIO

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nastevens (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Alternative to #29

The changes generally look Ok, I had some extra concerns at first related to semver but 0.3 is not published yet so that should be OK.
Probably the main thing to consider changing here would be to do the additional conditional compilation to allow for completely dropping the sysfs gpio dep if the feature is not selected.
I question the choice to expose struct Pin with the same name for different backends.  This seems unecessary and confusing.  Instead, I feel it would be simpler (in terms of implementation and use) to expose two different structs.  Making these look the same is what the traits are for and I fear using feature flags as is done  here is primarily a recipe for confusion.  Open to thoughts on this, this is just my thinking getting to this a bit delayed.

I question the choice to expose struct Pin with the same name for different backends.

yeah this is a good point, would renaming to CdevPin and SysfsPin for the impls work for you, then the feature flag is just selecting which is re-exported as Pin (which we need for backwards compatibility)?

Probably the main thing to consider changing here would be to do the additional conditional compilation to allow for completely dropping the sysfs gpio dep if the feature is not selected.

seems reasonable to me, i guess this would look like adding a gpio_sysfs feature, then what was re-exported as Pin by default would depend on the combination of flags?
tangentially (and outside the scope of this PR), is there a point at which we want to switch people from one to the other? and, is there some way we could do this automagically at runtime instead of requiring people to compile specifically for the gpio mode? (not that support for older kernels doesn't always require a GLIBC dance anyway)

@posborne the CI issue is fixed in #31 if you have any time to quickly review that

yeah this is a good point, would renaming to CdevPin and SysfsPin for the impls work for you, then the feature flag is just selecting which is re-exported as Pin (which we need for backwards compatibility)?

I think regardless we will not be backwards compatible, right unless someone changes the features around.  Since we having a semver move to 0.3 I think it probably makes sense to introduce the breakage and avoid trying to do the rename.  The names you propose look reasonable to me.  Doing things this way also would allow enabling both features if desired (this could make sense for some people as people may want to use cdev for some new stuff but might still rely on udev rules to setup symlinks which would be used with sysfs).

tangentially (and outside the scope of this PR), is there a point at which we want to switch people from one to the other?

I think we just put the deprecation front and center and focus development on the newer stuff.  The fact of the matter is that there are a lot of engineers who may want to use rust but will be continuing to work against systems that do not have cdev even after sysfs_gpio is deprecated in upstream kernels.  Thinking specifically of 3.10 based systems.
These products should move to 4.9 LTSI but that's easier said than done depending on the SoC vendor and drivers in use.  Right now I think we focus on making sure that people can use cdev and over push them that way; the hammer can come a  bit later.

yeah this is a good point, would renaming to CdevPin and SysfsPin for the impls work for you, then the feature flag is just selecting which is re-exported as Pin (which we need for backwards compatibility)?

I think regardless we will not be backwards compatible, right unless someone changes the features around. Since we having a semver move to 0.3 I think it probably makes sense to introduce the breakage and avoid trying to do the rename. The names you propose look reasonable to me. Doing things this way also would allow enabling both features if desired (this could make sense for some people as people may want to use cdev for some new stuff but might still rely on udev rules to setup symlinks which would be used with sysfs).

IMO that make sense since we can break the backward comapibility. So I'll prepare commit that introduces SysfsPin and CdevPin enabled with different features. Does it work for you?

tangentially (and outside the scope of this PR), is there a point at which we want to switch people from one to the other?

I think we just put the deprecation front and center and focus development on the newer stuff. The fact of the matter is that there are a lot of engineers who may want to use rust but will be continuing to work against systems that do not have cdev even after sysfs_gpio is deprecated in upstream kernels. Thinking specifically of 3.10 based systems.
These products should move to 4.9 LTSI but that's easier said than done depending on the SoC vendor and drivers in use. Right now I think we focus on making sure that people can use cdev and over push them that way; the hammer can come a bit later.

IMO that make sense since we can break the backward comapibility. So I'll prepare commit that introduces SysfsPin and CdevPin enabled with different features. Does it work for you?

Sounds good to me.


Remove now-stable test from quarantine

This one has not failed in 13 days after #5445 was merged.
the PV test seems stable too, but I would like to wait longer to
be sure.
Release note:

NONE

/lgtm

/retest

/approve


package installation

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ManagedClient does not auto reconnect after wifi is reestablished

Sample ManagedClientTest (3.0.8) below does not reconnect automatically after Wifi is disabled and reenabled. Any help will be appreciated.
Update: Actually ManagedClient only recovers mqtt connection successfully under dot net platform. Under UWP or Xamarin Forms / mono platform, recovery of mqtt connection fails when reestablishing the internet connection
public static async Task RunAsync()
        {
            var ms = new ClientRetainedMessageHandler();

            var options = new ManagedMqttClientOptions
            {
                ClientOptions = new MqttClientOptions
                {
                    ClientId = "MQTTnetManagedClientTest",
                    Credentials = new RandomPassword(),
                    ChannelOptions = new MqttClientTcpOptions
                    {
                        Server = "broker.hivemq.com"
                    }
                },

                AutoReconnectDelay = TimeSpan.FromSeconds(1),
                Storage = ms
            };

            try
            {
                var managedClient = new MqttFactory().CreateManagedMqttClient();
                managedClient.ApplicationMessageReceivedHandler = new MqttApplicationMessageReceivedHandlerDelegate(e =>
                {
                    Console.WriteLine(">> RECEIVED: " + e.ApplicationMessage.Topic);
                });

                managedClient.UseConnectedHandler(e => {
                    Console.WriteLine("connected..."); // Unfortunately connected won't get called after wifi is reestablished
                });

                await managedClient.StartAsync(options);

                await managedClient.SubscribeAsync(new TopicFilter { Topic = "xyz", QualityOfServiceLevel = MqttQualityOfServiceLevel.AtMostOnce });
                await managedClient.SubscribeAsync(new TopicFilter { Topic = "abc", QualityOfServiceLevel = MqttQualityOfServiceLevel.AtMostOnce });

                await managedClient.PublishAsync(builder => builder.WithTopic("Step").WithPayload("3"));

                Console.WriteLine("Managed client started.");
                Console.ReadLine();
            }
            catch (Exception e)
            {
                Console.WriteLine(e);
            }
        }

@JanEggers You're the expert for UWP I would say :D

@SeppPenner no sry  I dont have a testenvironment for that. can you provide any logs?

no sry I dont have a testenvironment for that.

Same for me. I did use UWP some day but had to do a new setup of my computer and didn't install it anymore.

Problem still exists for me. Has anybody found a solution?

Please try version <IP_ADDRESS>0 from the myget feed and let me know if the issue is fixed.

The fix for this issue is now released.


Indent Guides Highlight Incorrect Level for Certain Indent Styles and Simple Code Blocks

Visual Examples
Allman Style Indentation

K&R Style Indentation

Simple Code Block

Whitesmiths Style Indentation

Steps to Reproduce:

Create a new JavaScript or TypeScript file.
Set the Language/Syntax Highlighting to "TypeScript".
Add the following to the file:function test()
{
    if (window !== undefined)
    {
        console.log("Allman style");
    }

    if (window !== undefined) {
        console.log("K&R style");
    }

    {
        console.log("Simple block");
    }

    if (window !== undefined)
        {
        console.log("Whitesmiths style");
        }
}

Put the cursor at the bracket on lines 4, 6, 8, and 10. Verify that the highlighted Indent Guide is NOT associated with the associated if statement, but the function statement on line 1.
Move the cursor to the bracket on line 12 or 14. Verify that the highlighted Indent Guide is Not associated with the brackets that define the block, but the encapsulating function statement on line 1.
Move the cursor to the bracket on line 13.  Verify that the highlighted Indent Guide is associated with the if statement on line 12.

Discussion
As a user who prefers the Allman indentation style I expect that placing the cursor on a bracket (both opening and closing) associated with a specific block will result in highlighting the block associated with that bracket rather than the encapsulating block. As the reproduction steps show, this also fails with the K&R style and with simple code blocks.
This does work as expected with the Whitesmiths style, the GNU, and likely with any other style that indents the brackets themselves beneath the encapsulating statement.
Environment
Does this issue occur when all extensions are disabled?: Yes

VSCode Version: <IP_ADDRESS>
OS Version: macOS 10.13.5

Duplicate of #49342

@alexandrudima you are saying everywhere this is duplicate i visited all references and in all references you are saying the same thing but not telling the solution 👎


Site build fails since its missing v8

Looks like this is a problem with alpine, since it does not have v8.
See the stack trace below,
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux-musl]
Traceback (most recent call last):
        16: from /usr/local/bundle/bin/jekyll:29:in `<main>'
        15: from /usr/local/bundle/bin/jekyll:29:in `load'
        14: from /usr/local/bundle/gems/jekyll-3.8.7/exe/jekyll:11:in `<top (required)>'
        13: from /usr/local/bundle/gems/jekyll-3.8.7/lib/jekyll/plugin_manager.rb:51:in `require_from_bundler'
        12: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler.rb:114:in `require'
        11: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:65:in `require'
        10: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:65:in `each'
         9: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:76:in `block in require'
         8: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:76:in `each'
         7: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:81:in `block (2 levels) in require'
         6: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/runtime.rb:81:in `require'
         5: from /usr/local/bundle/gems/jekyll-lunr-js-search-3.3.0/lib/jekyll-lunr-js-search.rb:2:in `<top (required)>'
         4: from /usr/local/bundle/gems/jekyll-lunr-js-search-3.3.0/lib/jekyll-lunr-js-search.rb:2:in `require'
         3: from /usr/local/bundle/gems/jekyll-lunr-js-search-3.3.0/lib/jekyll_lunr_js_search/indexer.rb:5:in `<top (required)>'
         2: from /usr/local/bundle/gems/jekyll-lunr-js-search-3.3.0/lib/jekyll_lunr_js_search/indexer.rb:5:in `require'
         1: from /usr/local/bundle/gems/therubyracer-0.12.3/lib/v8.rb:4:in `<top (required)>'
/usr/local/bundle/gems/therubyracer-0.12.3/lib/v8.rb:4:in `require': Error relocating /usr/local/bundle/gems/therubyracer-0.12.3/lib/v8/init.so: __vfprintf_chk: symbol not found - /usr/local/bundle/gems/therubyracer-0.12.3/lib/v8/init.so (LoadError)

Is there a bug here?

Not really, I can build my site on my mac, but inside docker the build fails.
I also see this in the documentation

You can install system packages by providing a file named .apk with one package per line.

I could try installing v8 myself. How do I pass this file to the docker container?

If it's included inside of your Jekyll Root we'll pick it up! On a side note there is a plan to migrate to Ubuntu eventually sometime soon, but I have to do it in a way that doesn't affect people so harshly because a lot of enterprise users rely on this image.


adapter-node build fail with  Unexpected character  error

Describe the bug
after adding houdini to the minimal SvelteKit project, adapter-node  start failing.
before adding houdini config, build is working fine.
npm run build:node

><EMAIL_ADDRESS>build:node
> cross-env ADAPTER=node npm run build

><EMAIL_ADDRESS>build
> vite build

vite v4.0.2 building for production...
🎩 Generating runtime...
📃 Unchanged: 8
transforming (1) node_modules/@sveltejs/kit/src/runtime/client/start.js8:12:59 PM [vite-plugin-svelte] /src/routes/+page.svelte:3:3 A11y: '#' is not a valid href attribute
1:
Welcome to SvelteKit

2:
Visit kit.svelte.dev to read the documentation

3: btn
      ^
4:
transforming (51) node_modules/devalue/src/utils.js
🌼 daisyUI components 2.45.0  https://daisyui.com
  ✔ Including:  base, components, 29 themes, utilities
  ❤ Support daisyUI:  https://opencollective.com/daisyui

✓ 144 modules transformed.
8:13:01 PM [vite-plugin-svelte] dom compile done.
package                 files     time     avg
svelte-starter-kit          3   35.1ms  11.7ms
@sveltejs/kit               1   21.0ms  21.0ms
[commonjs--resolver] Unexpected character '�' (Note that you need plugins to import files that are not JavaScript)
file: /Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/fsevents/fsevents.js:1:0
1: ����@�
         @�������(__TEXT��__text__TEXTF3F�__stubs__TEXT4e 4�__stub_helper__TEXTTf�Tf�__const__TEXTHHh__cstring__TEXTPh%Ph__unwind_info__TEXTx�x(__DATA�@�@__nl_symbol_ptr__DATA�0__got__DAT�1__la_symbol_ptr__DATA �� �4__mod_init_func__DATA���    __const__DATA��P��__data__DATA��H��H__LINKEDIT�@�<"�0�����H�����h
                                                                                P���3�d�A�1�>ۂ�2BEU`�$
   ^
2:
3:
   *
    h���/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
                                                                                h
                                                                                b/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
                                                                                0�/usr/lib/libc++.1.dylib
                                                                                8<
                                                                                /usr/lib/libSystem.B.dylib&@�h)��UH��]�f.�UH��]�f.�UH��]�f.�UH��SPH��H�~H�H�;1���H���H��H�[]�=f.�UH��AVSH��PI����I�FHH�5;H�U��
error during build:
RollupError: Unexpected character '�' (Note that you need plugins to import files that are not JavaScript)
    at error (file:///Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/rollup/dist/es/shared/rollup.js:2001:30)
    at Module.error (file:///Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/rollup/dist/es/shared/rollup.js:12982:16)
    at Module.tryParse (file:///Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/rollup/dist/es/shared/rollup.js:13359:25)
    at Module.setSource (file:///Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/rollup/dist/es/shared/rollup.js:13268:24)
    at ModuleLoader.addModuleSource (file:///Users/schintha/Developer/Work/SPA/aaa/svelte-starter-kit/node_modules/rollup/dist/es/shared/rollup.js:22700:20)

Severity
serious, but I can work around it
Steps to Reproduce the Bug
minimal code to reproduce issue
git clone  https://github.com/xmlking/sveltekit-houdini-issue.git
npm install
npm run build:node

Reproduction
https://github.com/xmlking/sveltekit-houdini-issue.git

to test, remove houdini() plugin in vite.config.ts
i.e., plugins: [houdini(), sveltekit()] --> 	plugins: [ sveltekit()]
then run:
npm run build:node

Output : build works without errors
><EMAIL_ADDRESS>build:node
> cross-env ADAPTER=node npm run build

><EMAIL_ADDRESS>build
> vite build

vite v4.0.2 building for production...
transforming (1) node_modules/@sveltejs/kit/src/runtime/client/start.js8:41:01 PM [vite-plugin-svelte] /src/routes/+page.svelte:3:3 A11y: '#' is not a valid href attribute
1:
Welcome to SvelteKit

2:
Visit kit.svelte.dev to read the documentation

3: btn
      ^
4:
transforming (37) node_modules/devalue/src/constants.js
🌼 daisyUI components 2.45.0  https://daisyui.com
  ✔ Including:  base, components, 29 themes, utilities
  ❤ Support daisyUI:  https://opencollective.com/daisyui

✓ 39 modules transformed.
8:41:01 PM [vite-plugin-svelte] dom compile done.
package                 files     time     avg
svelte-starter-kit          3   37.1ms  12.4ms
@sveltejs/kit               1   22.4ms  22.4ms

vite v4.0.2 building SSR bundle for production...
transforming (1) .svelte-kit/build/index.js8:41:02 PM [vite-plugin-svelte] /src/routes/+page.svelte:3:3 A11y: '#' is not a valid href attribute
1:
Welcome to SvelteKit

2:
Visit kit.svelte.dev to read the documentation

3: btn
      ^
4:
✓ 47 modules transformed.
8:41:02 PM [vite-plugin-svelte] ssr compile done.
package                 files    time     avg
svelte-starter-kit          4   8.8ms   2.2ms
Generated an empty chunk: "hooks".
.svelte-kit/output/server/vite-manifest.json                  1.13 kB
.svelte-kit/output/server/chunks/hooks.js                     0.00 kB
.svelte-kit/output/server/entries/pages/_layout.svelte.js     0.25 kB
.svelte-kit/output/server/entries/pages/_page.svelte.js       0.37 kB
.svelte-kit/output/server/entries/fallbacks/error.svelte.js   0.79 kB
.svelte-kit/output/server/chunks/index.js                     3.22 kB
.svelte-kit/output/server/index.js                           78.69 kB

Run npm run preview to preview your production build locally.
.svelte-kit/output/client/_app/version.json                                            0.03 kB
.svelte-kit/output/client/vite-manifest.json                                           2.36 kB
.svelte-kit/output/client/_app/immutable/assets/_layout-2ecff240.css                  33.49 kB │ gzip:  6.70 kB
.svelte-kit/output/client/_app/immutable/chunks/1-eb604b7f.js                          0.09 kB │ gzip:  0.10 kB
.svelte-kit/output/client/_app/immutable/chunks/2-014bf943.js                          0.10 kB │ gzip:  0.10 kB
.svelte-kit/output/client/_app/immutable/chunks/0-89ead9ea.js                          0.10 kB │ gzip:  0.10 kB
.svelte-kit/output/client/_app/immutable/components/pages/_layout.svelte-b8d1d550.js   0.55 kB │ gzip:  0.36 kB
.svelte-kit/output/client/_app/immutable/components/error.svelte-03b3ffcb.js           0.98 kB │ gzip:  0.57 kB
.svelte-kit/output/client/_app/immutable/components/pages/_page.svelte-781349e5.js     1.02 kB │ gzip:  0.56 kB
.svelte-kit/output/client/_app/immutable/chunks/singletons-c1916556.js                 2.58 kB │ gzip:  1.34 kB
.svelte-kit/output/client/_app/immutable/chunks/index-7f3551f2.js                      6.87 kB │ gzip:  2.79 kB
.svelte-kit/output/client/_app/immutable/start-ad854b67.js                            26.46 kB │ gzip: 10.36 kB

> Using @sveltejs/adapter-node
Generated an empty chunk: "hooks".
  ✔ done

Thanks for reporting this @xmlking! I'll take a look and let you know what i find

I'm pretty sure the issue is related to the houdini plugin since the generated runtime imports your config file which causes vite to bundle the vite module with the rest of your client. This clearly isn't an intended use case for vite so it's not totally surprising its not working.

May be we can try exclude vite in optimizeDeps at
https://github.com/xmlking/sveltekit-houdini-issue/blob/main/vite.config.ts#L51
I am away from computer, will try when I get back

May be we should explore using   $env/dynamic/public for houdini.config.js as well🤔

The PR i linked to will load the appropriate files for you to refer to however you want. The actual  $env alias won't work without a lot of effort since it's an alias that the kit plugin generates behind the scenes which means we'd have to run vite as part of the codegen process.

Closing this since it should be fixed in 0.19.0. let me know if the problem still persists and we can open it back up. Thanks for being patient!

thanks a lot, @AlecAivazis  I upgraded to 0.19.0 and all works fine now.
latest working code: https://github.com/xmlking/sveltekit-houdini-issue

Great to hear! Btw I don't think the default marshalers you defined are necessary - iirc, what you have there is is the default value

Do you mean  I don’t have to provide DateTime, Decimal and URL ?
I recall it was giving  warning logs  for hstore, jsonb etc.


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(scripts): update prepare@rollup -c from template

.travis.yml

chore(travis): merge from template .travis.yml

Coverage increased (+5.6%) to 96.439% when pulling 9c48d8ff04300f058e631a5ae7e4932793f84507 on template-sync-1 into cacbc2764e9837f7554de7342ee5d11cc58e569d on master.

Codecov Report

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

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
+ Coverage    90.8%   96.43%   +5.63%
==========================================
  Files          27       27
  Lines         337      337
==========================================
+ Hits          306      325      +19
+ Misses         31       12      -19

Impacted Files
Coverage Δ

src/file.js
100% <0%> (+50%)
:arrow_up:

src/npm-template-sync.js
100% <0%> (+56.25%)
:arrow_up:

Continue to review full report at Codecov.

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


[wip, fbx] vertex colors bugfix

Ignore this I'm trying to resolve a problem with a complex mesh, once it's fixed it will be the fix for #44297
Ordering is the wrong approach, maintaining the SAME insertion order is key here,
unordered hash map and hash map are not the right tool here.
Need to revert the ordering change: and make it insertion based :P

now to rebase out the bad mesh code edits.

Validated with my own test files and a 3rd party test asset.
4_vert_colors_plane.zip
Another test asset is available in the GLTF2 sample repository.

Thanks!


Fetch content from a single markdown file

Wouldn't it be great if each place had it's own markdown file? That way if the community wants to incorporate more information (review, star rating, accessibility, vegan food (?) etc.) you could do so easily. The added advantage being that you don't need to write jsx to add a new place.

Sounds like a better idea, I've been getting requests to expand the list to other locations so I think this approach would make better sense when organizing by locations

@thetronjohnson I've opened a PR for the same. :D


rhods_test_jupyterlab: test-jupyterlab-psap-simplenotebook: remove 'Clean up the files and folders we created'

This PR removes the Clean up the files and folders we created step from the simple test robot.
This steps often fails, and it isn't relevant for us (we delete the PVCs after the testing).

/test ods-jh-at-scale

/test ods-jh-on-ocp

Makes total sense to me.

good, merging :)


nixos module: do not depend on iohkNix being in provided pkgs.

bors r+

bors r-

bors r-

bors r+


IMN-213 Fix document update based on descriptor state in catalog-process

[To be merged after #180]
This pull request is for fixing the updateDocument operation. With this fix, it's no longer possible to update the prettyName of a descriptor that is not in Draft state.

In order to be consistent between Scala and the monorepo, we have to wait that https://github.com/pagopa/interop-be-catalog-process/pull/230 is approved before reviewing this.


Sorting problem when editing stars.

You've loaded some dataset. You want to edit some stars.  The stars in the dataset come up in alphabetical order, which is good, and as you page down through them, they are in alphabetical order.
But then, for some reason, you want to edit some stars that you can find by distance, or by spectral class or by something. So, then you notice that clicking on the column headings causes it to sort.  That's cool.
But then, the giant disappointment.  You click spectral class, and it appears to sort by spectral class, and then you hit "next page" or "end"... and if you hit end, you're not in the Y's and Z's... and if you hit next, suddenly you're seeing a spectral class that should be ABOVE the one I started on because the sort, only sorts THE PAGE YOU ARE ON.
So, either we need the sort to sort the data on however many pages there are, or we need to disable the sorts.
Right now, as it is, the sorts are an anti-feature.  They actually make the program worse.

It does sort the backing list according to the criteria (ascending or descending.
What I think happens is that the it tries to preserve the current page and that ends up messing things up.
What I believe I should do is put the list back at the first page after the sort happens.
@BoatrightTBC let me know if this is what you want and I will go ahead with it.

ok, I did it that way and it seems to work.


ViewPropTypes has been removed from React Native.

I got error after installing the package in my application.
ERROR  Invariant Violation: ViewPropTypes has been removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.  ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.       This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.  ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.       This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
I'm not using ViewPropTypes anywhere in my application. this error only show after installing the yarn add react-native-media-controls react-native-slider command

"react": "18.0.0"
"react-native": "0.69.5"

faced the same issue ,the package relies on react-native-slider which uses the removed ViewPropTypes ,
install @react-native-community/slider  instead of "react-native-slider"
run your project ,the console will point you to where the errors occur
,change all the import and require statement from ""react-native-slider" to "@react-native-community/slider"
THIS IS NOT A GOOD FIX!
feel free to submit a pull request

still no update.


[mgmt] containerservice preview release

https://github.com/Azure/sdk-release-request/issues/4684

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-containerservice


Add ability to track the number of times a flashcard is tested

@ChenXJ98 we will also need to integrate this into the saving of flashcard so that we can retain the times tested information across instances of QuickCache


deploy goal unable to deploy application to the apps directory with running server.

Running mvn liberty:deploy -DappsDirectory=apps with server running always deploys the application to the dropins directory.
When server is running, DeployMojo calls the deploy ant task which always deploys the application to the dropins directory.

try using just your archive name in your server.xml, like this:
<webApplication location="demo.app" ... />
instead of
<webApplication location="${server.config.dir}/apps/misc-apps.war" ... />
which the config design view will create for you.  This really should be fixed though, since WDT would create that location path as the default, at least as an enhancement.

So the plugin checks to see if the application is defined in the server.xml. If it does not find a match, then it will put the app in dropins folder.

This is only true for the 'smart' default for appsDirectory - "The default value is set to apps if the application is defined in the server configuration, otherwise it is set to dropins."
https://github.com/OpenLiberty/ci.maven/blob/master/docs/deploy.md
If the appsDirectory is set to apps in the pom or CLI and the application is not defined in the server.xml, the application configuration will be generated in configDropins/defaults/install_apps_configuration_*.xml

We'd need to update the deploy behavior to deploy to apps while the server is running. That would mean we would have to update the ant deploy task to deploy to apps/dropins, or we would need to pull the deploy logic out into DeployMojo and could leave the ant deploy task as it is now.