What Zsh/Vim themes are shown in the marketing screenshots?

I love the minimal white .zsh and Vim themes I've seen on the website and in casts. Any pointers as to what setup you guys are using?

@matheuss Created this: https://github.com/zeit/zeit.zsh-theme.


[NDTensors] Use SetParameters in GPU extensions

Use SetParameters module in GPU extensions to simplify setting type parameters of different AbstractArray data backends.

@kmp5VT this made it easier to get more of the NDTensorMetal extension working, but there are still some issues with handling conversion from double to single precision in that case. For example:
julia> using ITensors

julia> using Metal

julia> NDTensors.mtl(randomITensor(Index(2)))
ERROR: Metal does not support Float64 values, try using Float32 instead
Stacktrace:
  [1] error(s::String)
    @ Base ./error.jl:35
  [2] MtlVector{Float64, Metal.MTL.MTLResourceStorageModePrivate}(#unused#::UndefInitializer, dims::Tuple{Int64})
    @ Metal ~/.julia/packages/Metal/qeZqc/src/array.jl:45
[...]

@mtfishman The double precision problem you're quoting is actually rather significant in Metal they simply do not have operations implemented for Float64 vectors so we should not even try to construct them at this point.

Yeah, seems like we should just aggressively convert to single precision in functions like adapt (like the Metal.mtl function does).

Ok, I ended up keeping adapt and related functions like NDTensors.mtl as-is (i.e. not converting automatically to single precision), but changed the tests to use single precision when the Metal backend is being tested. I now have the NDTensors tests passing locally with and without the Metal backend on my macbook using the new design based on SetParameters.
However, there is a strange issue on CI, it's complaining that  the function get_parameters isn't defined. This is a new function I introduced in the NDTensors.SetParameters module in this PR. My tests pass locally so that function is defined properly. @kmp5VT do you know what might be going on? It seems like it isn't seeing the latest NDTensors version from this PR branch, however I do see in the CI log that it is using the dev'd version of NDTensors:
  [23ae76d9] NDTensors v0.2.2 `~/.julia/dev/ITensors/NDTensors`

Maybe it's using the main branch instead of this PR branch?

@kmp5VT I noticed that the CI log shows this for ITensors:
  [9136182c] ITensors v0.3.37 `~/work/ITensors.jl/ITensors.jl`

but this for NDTensors:
  [23ae76d9] NDTensors v0.2.2 `~/.julia/dev/ITensors/NDTensors`

so it seems like maybe for ITensors it is using the PR branch while for NDTensors it's using the main branch.

Switching lines like:
Pkg.develop("NDTensors")

to:
Pkg.develop(path="./NDTensors")

seems to fix that issue and get the tests to run based on the version of NDTensors on the PR branch.
However, there's still an issue running the ITensorGPU tests on Jenkins, where it's also complaining that the get_parameters isn't defined.

[test ITensors mps]

Codecov Report

Merging #1153 (1a1e0b3) into main (4dde2e7) will decrease coverage by 6.09%.
The diff coverage is 84.09%.

:exclamation: Current head 1a1e0b3 differs from pull request most recent head 43531f9. Consider uploading reports for the commit 43531f9 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1153      +/-   ##
==========================================
- Coverage   59.65%   53.57%   -6.09%
==========================================
  Files          87       85       -2
  Lines        8326     7819     -507
==========================================
- Hits         4967     4189     -778
- Misses       3359     3630     +271

Impacted Files
Coverage Δ

src/ITensors.jl
100.00% <ø> (ø)

src/adapt.jl
0.00% <ø> (-100.00%)
:arrow_down:

src/mps/abstractmps.jl
0.83% <0.00%> (-86.26%)
:arrow_down:

src/mps/projmposum.jl
0.00% <0.00%> (-66.67%)
:arrow_down:

src/tagset.jl
88.17% <87.50%> (+7.73%)
:arrow_up:

src/global_variables.jl
100.00% <100.00%> (+54.00%)
:arrow_up:

src/itensor.jl
80.34% <100.00%> (+31.37%)
:arrow_up:

... and 72 files with indirect coverage changes


Catalog kind filter fixes & clean-up

Catalog kind filter fixes & clean-up
Various fixes:

CatalogDefaultPage cannot handle Capitalized kinds from the kind query
parameter. This breaks ownership cards and both CatalogKindHeader and
EntityKindPicker turns up empty.
There may be other places where the catalog expects to handle capitalized
Kinds. After all, the default Kinds are capitalized in the entities.

If a non existing kind is specified, CatalogKindHeader works but not
the EntityKindPicker. Well, at least as long as the non-existing kind
is not capitalized(!)

The CatalogKindHeader supports allowed kinds, but not the
EntityKindFilter. So depending on Catalog-setup they will list different
kinds.

Refactoring:

Refactored out helper functions to a util library. This ensured that
similar logic can be shared between the Kind pickers (and in turn their
behaviour is similar).

Tests:

Relevant tests added

Signed-off-by: Gustaf Lundh<EMAIL_ADDRESS>
[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

This is ready. I hope we can get this into 1.8.0. The issues are quite problematic :)

Just a gentle ping here! @GLundh

Yes. Thanks for the review. Some stuff got in the way, but I intend to fix the PR.

@freben : I know some tests you asked for are still missing, but there are some question marks that I would like to sort out before wrapping everything up. Please take a look at my comments.

I think there was just one outstanding question about the query listener right? Just checking so I don't miss anything.

@freben:  I'm happy with the code, except how to solve the API stuff. See our previous discussion:
https://github.com/backstage/backstage/pull/14366#discussion_r1036055989
In regards to the queryListener stuff. I have tried to keep this code close to the original. I really don't want larger changes in this PR. See my comment here:
https://github.com/backstage/backstage/pull/14366#discussion_r1036061898


Adjust the date field in the Cases

User story

As a facility manager
I need the date field to be adjusted in the cases
So that it is more readable and user-friendly.

Acceptance criteria

[ ] The date field in the cases is changed to a more  readable and user-friendly format.

Definition of done (DoD)

[ ] All acceptance criteria were met
[ ] Pipeline is building successfully
[ ] Unit/integration tests are passing
[ ] Code has been reviewed and merged into the primary development branch

DoD general criteria

[ ] Developers agreed to release
[ ] Product owner approved features
[ ] Feature has been fully implemented

Closed as duplicate. already implemented


Render all strings with single quotes

When I was working on https://github.com/clutchski/coffeelint/pull/346, I noticed that there were a lot of unneeded double quotes in the output. Since they have a special meaning in coffee script this could also mean unintended string interpolation.
I probably missed some edge cases, so please take a good look before merging!

+1, would love it for that same reason (coffeelint)

+1. Now that coffeelint supports transforms, this would be very helpful. Single quotes should be the default considering there are no rules forbidding them, while the no_unnecessary_double_quotes forbids double quotes.

+1, this would be great.  Are there any specific concerns blocking this PR from being merged?  Thanks!

+1 . any updates? the merge conflict looks like it just from the test output text

Apparently this is not going to happen? :/

We migrated away from coffeescript, so closing this PR. Feel free to copy/rebase the code and create your own pull request.


Allow environment variables to be specified outside the application config.

Environment variables often contain sensitive data, where as other environment variables and the rest of the configuration isn't. For example https://github.com/ClusterHQ/build.clusterhq.com has passwords to various services in the environment. It should be possible to store the sensitive information separately from the rest of the configuration.

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-706. You are welcome to file additional issues in GitHub if that's easier for you.


Pin Rust in CI

Looks like CI doesn't always pick the freshest Rust there is.
Anyway, it makes sense to keep these things reproducible.

WDYT @jonas-schievink ?

Hm, no, apparently CI does pick the latest stable, it's just that there's some default rustup with older rust installed?


Ignore messages without message_attributes

This fixes issue https://github.com/SimpleFinance/sensu-transport-snssqs/issues/9

In what case are there no message attributes?

If you get non raw messages...

I've listed in the Caveats section of the README that the "Raw" mode is required (https://github.com/SimpleFinance/sensu-transport-snssqs#caveats).
That said, I still don't know how the message attributes would be missing from messages, since the message attributes are always requested from the SQS API: https://github.com/runningman84/sensu-transport-snssqs/blob/1883bd52c332730aeb2fd1d21b3525722e109740/lib/sensu/transport/snssqs.rb#L173. Are you using the SQS queue for more than just these Sensu messages?

This pull request is obsolete. We pushed support for non raw messages and better error handling here
https://github.com/troyready/sensu-transport-snssqs-ng/pull/2


Build and test with CUDA 12.5.1

This PR updates the latest CUDA build/test version 12.2.2 to 12.5.1.
Contributes to https://github.com/rapidsai/build-planning/issues/73

/merge

Thanks Kyle and James! 🙏


Add corvid-19 survey to validate

What? and Why?

What does this pull request change/fix? Why was it necessary?

Checklist

[x] CHANGELOG.md updated? (if required)

Don't merge until it's confirmed what the survey_id is


Can not stop the sandbox properly

Hi :)
Sometimes I see issues with astop() command.
It fails with 'id' keyError during this operation:
await asyncio.gather(*(self.adelete(id) for id in list(self.sandboxs.keys())))

Am I doing this right? I init and stop each time I need to execute some code:
import datetime
import logging

from codeinterpreter.sandbox.local_jupyter.manager import LocalJupyterManager

logger = logging.getLogger(__name__)

class CodeExecutionStatus:
    OK = "ok"
    ERROR = "error"

class CodeInterpreter:
    def __init__(self):
        self.manager = LocalJupyterManager()

    async def execute_code_in_sandbox(self, code: str) -> tuple[str | None, str]:
        try:
            logger.info(f"Sandbox initiation started at {datetime.datetime.now()}")
            await self.manager.ainit()
            sandbox = await self.manager.astart()

            logger.info(f"Sandbox initiation finished at {datetime.datetime.now()}")
            sandbox_result = await sandbox.arun(code)
            logger.info(f"Code execution finished at {datetime.datetime.now()}")

            await self.manager.astop()
            logger.info(f"Sandbox deletion finished at {datetime.datetime.now()}")

            if sandbox_result.type == "error" or not sandbox_result.content:
                logger.error(f"The code execution failed: {sandbox_result}")
                return None, CodeExecutionStatus.ERROR

            return sandbox_result.content, CodeExecutionStatus.OK

        except Exception as e:
            logger.error(f"The code execution failed: {e}")
            return None, CodeExecutionStatus.ERROR

I guess the issue is that I used commands improperly, I came up with the new version in the end:
import datetime
import logging

from codeinterpreter.sandbox.local_jupyter.manager import LocalJupyterManager

logger = logging.getLogger(__name__)

class CodeExecutionStatus:
    OK = "ok"
    ERROR = "error"

class CodeInterpreter:
    def __init__(self):
        self.manager = LocalJupyterManager()

    async def execute_code_in_sandbox(self, code: str) -> tuple[str | None, str]:
        try:
            if not self.manager.session:
                logger.info(f"Sandbox initiation started at {datetime.datetime.now()}")
                await self.manager.ainit()

            logger.info(f"Sandbox is set to start at {datetime.datetime.now()}")
            sandbox = await self.manager.astart()
            logger.info(f"Sandbox started at {datetime.datetime.now()}")

            sandbox_result = await sandbox.arun(code)
            logger.info(f"Code execution finished at {datetime.datetime.now()}")

            if sandbox_result.type == "error" or not sandbox_result.content:
                logger.error(f"The code execution failed: {sandbox_result}")
                return None, CodeExecutionStatus.ERROR

            logger.info(f"Sandbox deletion started at {datetime.datetime.now()}")
            await self.manager.adelete(sandbox.id)
            logger.info(f"Sandbox deletion finished successfully at {datetime.datetime.now()}")

            return sandbox_result.content, CodeExecutionStatus.OK

        except Exception as e:
            logger.error(f"The code execution failed: {e}")
            return None, CodeExecutionStatus.ERROR

I do not use stop() anymore. I think delete() is enough in this case. What do you think?


Add owner and submitter metadata

This adds the owner and submitter information to the build's metadata.

I added a change to the docs.

Updated release notes draft:

Koji build metadata contains owner and submitter


Add ENV Example for easy contributions

You need to branch from main and apply your feature. We do not wanna merge all these change to main at this time.


Shim doesn't work for Ruby 3.3.0

Hello.
I have fish shell, rbenv initialization is from README:
status --is-interactive; and ~/.rbenv/bin/rbenv init - fish | source

With Ruby 3.3 something went wrong.
I was getting such warnings about PATH previously, but it worked anyway, or after rbenv rehash. Now nothing helps, including a new shell session.
> gem i solargraph
WARNING:  You don't have /home/alex/.gem/ruby/3.3.0/bin in your PATH,
	  gem executables will not run.
Successfully installed solargraph-0.50.0
Parsing documentation for solargraph-0.50.0
Done installing documentation for solargraph after 1 seconds
1 gem installed

> rbenv rehash

> solargraph -v
rbenv: solargraph: command not found

The `solargraph' command exists in these Ruby versions:
  3.0.2

> rbenv versions
  3.0.2
  3.2.2
* 3.3.0 (set by /home/alex/.rbenv/version)

> gem pristine solargraph
Restoring gems to pristine condition...
WARNING:  You don't have /home/alex/.gem/ruby/3.3.0/bin in your PATH,
	  gem executables will not run.
Restored solargraph-0.50.0

> solargraph -v
rbenv: solargraph: command not found

The `solargraph' command exists in these Ruby versions:
  3.0.2

> gem i solargraph
WARNING:  You don't have /home/alex/.gem/ruby/3.3.0/bin in your PATH,
	  gem executables will not run.
Successfully installed solargraph-0.50.0
Parsing documentation for solargraph-0.50.0
Done installing documentation for solargraph after 1 seconds
1 gem installed

> solargraph -v
rbenv: solargraph: command not found

The `solargraph' command exists in these Ruby versions:
  3.0.2

> rbenv rehash

> solargraph -v
rbenv: solargraph: command not found

The `solargraph' command exists in these Ruby versions:
  3.0.2

Hi, I am not aware of any behavior change of Rubygems starting with Ruby 3.3. It's possible that this is caused by some configuration on your system.

gem i solargraph
WARNING:  You don't have /home/alex/.gem/ruby/3.3.0/bin in your PATH,
gem executables will not run.

By looking at the output, it looks like the gem install command chose the "user" installation path, which I do not think is default behavior. I could not reproduce this with Ruby 3.3.
Could you check that you don't have a ~/.gemrc file and that the gem env command lists RBENV_ROOT/versions/3.3.0/bin as the EXECUTABLE DIRECTORY?

gem i solargraph
WARNING:  You don't have /home/alex/.gem/ruby/3.3.0/bin in your PATH,
gem executables will not run.

By looking at the output, it looks like the gem install command chose the "user" installation path, which I do not think is default behavior, and is not supported by rbenv. I could not reproduce this with Ruby 3.3.

This warning was in 3.2, 3.0, 2.7, but without further problems, so I've not reported an issue (and haven't found any similar).

Could you check that you don't have a ~/.gemrc file and that the gem env command lists RBENV_ROOT/versions/3.3.0/bin as the EXECUTABLE DIRECTORY?

Of course.
> cat ~/.gemrc
gem: --no-rdoc --no-ri # --user-install

> gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 3.5.3
  - RUBY VERSION: 3.3.0 (2023-12-25 patchlevel 0) [x86_64-linux]
  - INSTALLATION DIRECTORY: /home/alex/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0
  - USER INSTALLATION DIRECTORY: /home/alex/.gem/ruby/3.3.0
  - RUBY EXECUTABLE: /home/alex/.rbenv/versions/3.3.0/bin/ruby
  - GIT EXECUTABLE: /usr/bin/git
  - EXECUTABLE DIRECTORY: /home/alex/.rbenv/versions/3.3.0/bin
  - SPEC CACHE DIRECTORY: /home/alex/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /home/alex/.rbenv/versions/3.3.0/etc
  - RUBYGEMS PLATFORMS:
     - ruby
     - x86_64-linux
  - GEM PATHS:
     - /home/alex/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0
     - /home/alex/.gem/ruby/3.3.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => true
     - :bulk_threshold => 1000
     - "gem" => "--no-rdoc --no-ri # --user-install"
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /home/alex/.rbenv/versions/3.3.0/bin
     - /usr/lib/rbenv/libexec
     - /home/alex/.rbenv/plugins/ruby-build/bin
     - /home/alex/.local/share/pnpm
     - /home/alex/.nodenv/shims
     - /home/alex/.rbenv/shims
     - /home/alex/.pyenv/bin
     - /home/alex/bin
     - /home/alex/.nodenv/bin
     - /home/alex/go/bin
     - /usr/local/bin
     - /usr/bin
     - /usr/local/sbin
     - /usr/lib/jvm/default/bin
     - /usr/bin/site_perl
     - /usr/bin/vendor_perl
     - /usr/bin/core_perl

It's a pretty fresh rbenv installation. How can I check/fix it?

Hi @mislav! Is there any update on Ruby 3.3.0? The release was posted 12/25/2023
https://www.ruby-lang.org/en/news/2023/12/25/ruby-3-3-0-released/

This seems to be a RubyGems v3.5 bug, not a Ruby 3.3 bug. https://github.com/rubygems/rubygems/issues/7393
rbenv works with Ruby 3.3 just fine.
The temporary workaround until RubyGems fixes this is to completely remove --user-install from your gemrc, instead of just commenting it out.
Thanks for reporting!


WIP: splitting out timestamp formatting

REF: infra/operations #1778

Assigning to @jippi for review as he'll probably have thoughts here.


Add gff2tsv

Description of feature
Add a feature that parse the gff into tsv file to get annotation

Solved in #49


MQTT failure, throwing TRYING TO WRITE TO CLOSED SOCKET for every discovery subtopic

I found the fix to this, it's at the bottom of this report.
I've attempted to set up as instructed in the guide, but am hitting a wall with the warning TRYING TO WRITE TO CLOSED SOCKET being thrown for every topic update, except for the siac/_internal one.
Environment:
Debian 12 bookworm running Docker 25
Home assistant 2024.4.3 running in Docker
Mosquitto 2.0.18 MQTT broker running in Docker
I've tried both the 5.15 release, and the 0.6.0rc25 pre release versions of the siac-mqtt-gateway, via the docker image offered.
I've tried pulling the :latest image, and also building the image from the Dockerfile.
Logs:
2024-04-14 17:58:13,668 [  INFO  ] [CONNECTION MADE] - gmqtt.mqtt.protocol
2024-04-14 17:58:13,672 [ DEBUG  ] [CMD 0x20] b'\x00\x00' - gmqtt
2024-04-14 17:58:13,673 [ DEBUG  ] [CONNACK] flags: 0x0, result: 0x0 - gmqtt
2024-04-14 17:58:13,673 [  INFO  ] Connected to MQTT broker - publisher.mqtt_publisher
2024-04-14 17:58:13,673 [ DEBUG  ] NEW ID: 1 - gmqtt.mqtt.utils
2024-04-14 17:58:13,673 [  INFO  ] [SEND SUB] 1<EMAIL_ADDRESS>- gmqtt.mqtt.package
2024-04-14 17:58:13,673 [ DEBUG  ] NEW ID: 2 - gmqtt.mqtt.utils
2024-04-14 17:58:13,673 [  INFO  ] [SEND SUB] 2<EMAIL_ADDRESS>- gmqtt.mqtt.package
2024-04-14 17:58:13,674 [ DEBUG  ] NEW ID: 3 - gmqtt.mqtt.utils
2024-04-14 17:58:13,674 [  INFO  ] [SEND SUB] 3<EMAIL_ADDRESS>- gmqtt.mqtt.package
2024-04-14 17:58:13,674 [ DEBUG  ] NEW ID: 4 - gmqtt.mqtt.utils
2024-04-14 17:58:13,674 [  INFO  ] [SEND SUB] 4<EMAIL_ADDRESS>- gmqtt.mqtt.package
2024-04-14 17:58:13,674 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/lwt'', ... (6 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:13,679 [  INFO  ] Scheduler started - apscheduler.scheduler
2024-04-14 17:58:13,679 [  INFO  ] Logging in to SAIC API - __main__
2024-04-14 17:58:13,681 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/oauth/token/request'', ... (583 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:13,690 [ DEBUG  ] Looking for jobs to run - apscheduler.scheduler
2024-04-14 17:58:13,691 [ DEBUG  ] No jobs; waiting until a job is added - apscheduler.scheduler
2024-04-14 17:58:13,698 [ DEBUG  ] [CMD 0x90] b'\x00\x01\x00' - gmqtt
2024-04-14 17:58:13,699 [  INFO  ] [SUBACK] 1 (0,) - gmqtt
2024-04-14 17:58:13,699 [ DEBUG  ] FREE MID: 1 - gmqtt.mqtt.utils
2024-04-14 17:58:13,699 [ DEBUG  ] [CMD 0x90] b'\x00\x02\x00' - gmqtt
2024-04-14 17:58:13,699 [  INFO  ] [SUBACK] 2 (0,) - gmqtt
2024-04-14 17:58:13,699 [ DEBUG  ] FREE MID: 2 - gmqtt.mqtt.utils
2024-04-14 17:58:13,699 [ DEBUG  ] [CMD 0x90] b'\x00\x03\x00' - gmqtt
2024-04-14 17:58:13,699 [  INFO  ] [SUBACK] 3 (0,) - gmqtt
2024-04-14 17:58:13,699 [ DEBUG  ] FREE MID: 3 - gmqtt.mqtt.utils
2024-04-14 17:58:13,699 [ DEBUG  ] [CMD 0x90] b'\x00\x04\x00' - gmqtt
2024-04-14 17:58:13,699 [  INFO  ] [SUBACK] 4 (0,) - gmqtt
2024-04-14 17:58:13,700 [ DEBUG  ] FREE MID: 4 - gmqtt.mqtt.utils
2024-04-14 17:58:15,488 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/oauth/token/response'', ... (2618 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,490 [  INFO  ] Logged in as<EMAIL_ADDRESS>- __main__
2024-04-14 17:58:15,490 [  INFO  ] Fetching vehicle list - __main__
2024-04-14 17:58:15,491 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/vehicle/list/request'', ... (118 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,644 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/vehicle/list/response'', ... (4453 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,649 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/vehicle/alarmSwitch/request'', ... (589 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,732 [ DEBUG  ] Sending PUBLISH (q0), 'b'saic/_internal/api/vehicle/alarmSwitch/response'', ... (492 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,733 [  INFO  ] Registering for ['ALARM_TYPE_VEHICLE_FAULT', 'ALARM_TYPE_GEOFENCE', 'ALARM_TYPE_VEHICLE_START'] messages. vin=LSJW*********2049 - __main__
2024-04-14 17:58:15,734 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1681 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,734 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (2 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,734 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (5 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,735 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (4 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,735 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,735 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (7 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,736 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,736 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (11 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,736 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,736 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,736 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,736 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,737 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,737 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,737 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,737 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,737 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,737 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,738 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,738 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,738 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,738 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,738 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,738 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,739 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,739 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,739 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,739 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,739 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,739 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,740 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,740 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>control'', ... (1 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,740 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,740 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1 bytes) - gmqtt.mqtt.package

This continues until it hits an exception, and dumps the following stacktrace:
2024-04-14 17:58:15,865 [  INFO  ] Added job "Check for new messages" to job store "default" - apscheduler.scheduler
2024-04-14 17:58:15,866 [ DEBUG  ] Starting process for car LSJW*********2049 - __main__
2024-04-14 17:58:15,867 [WARNING ] Executing <Task cancelling name='Task-2' coro=<MqttGateway.run() running at /usr/src/app/./mqtt_gateway.py:490> wait_for=<Future pending cb=[Task.task_wakeup()] created at /usr/local/lib/python3.12/asyncio/base_events.py:449> cb=[_run_until_complete_cb() at /usr/local/lib/python3.12/asyncio/base_events.py:182] created at /usr/local/lib/python3.12/asyncio/runners.py:100> took 0.136 seconds - asyncio
2024-04-14 17:58:15,867 [WARNING ] [EXC: CONN LOST] - gmqtt.mqtt.protocol
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 1075, in write
    n = self._sock.send(data)
        ^^^^^^^^^^^^^^^^^^^^^
ConnectionResetError: [Errno 104] Connection reset by peer
2024-04-14 17:58:15,868 [ DEBUG  ] [CMD 0xe0] b'' - gmqtt
2024-04-14 17:58:15,869 [ DEBUG  ] Looking for jobs to run - apscheduler.scheduler
2024-04-14 17:58:15,869 [ DEBUG  ] Next wakeup is due at 2024-04-14 17:59:15.865299+00:00 (in 59.995849 seconds) - apscheduler.scheduler
2024-04-14 17:58:15,870 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (1681 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,870 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,870 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (2 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,870 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,870 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (5 bytes) - gmqtt.mqtt.package
2024-04-14 17:58:15,870 [WARNING ] [TRYING WRITE TO CLOSED SOCKET] - gmqtt.mqtt.protocol
2024-04-14 17:58:15,870 [ DEBUG  ] Sending PUBLISH (q0<EMAIL_ADDRESS>... (4 bytes) - gmqtt.mqtt.package

Then it continues.
Key notes:
I use a special character in my email address for the SIAC account. The + is appearing differently in the logs. At the start when publishing the SEND SUB messages, it's replaced with an underscore, yet for all subsequent messages, it displays correctly in the logs.
However, the siac/_internal topic is being published and regularly updated to MQTT, which can be verified by an explorer. It does seem to understand details about my car, it just doesn't seem to be making this auto-discoverable in Home Assistant, possibly due to the symbol in my email address?
Fix
I dove deeper into the code for this, and done some debugging.
It turns out that when doing the MQTT subscriptions, the input string is being cleaned up with the method remove_special_mqtt_characters() located in mqtt_publisher.py line 60, and the result of that cleaned up string is being placed in a variable that is then used when subscribing to topics. This seems to be an "initialise" of four topics, relating to the vehicles VIN.
However, when looking to publish this data in mqtt_gateway.py line 418 (of the 5.15 codebase, it's in a similar location in the 6.0 rc) the account_prefix variable is just taking the siac_user object key as is, and not doing any clean-up of it. I updated my own internal version of the 6.0 code base to a crude fix, and it now works, publishing the data to the broker.
mqtt_account_prefix = f'{self.configuration.saic_user}'.replace('+', '_').replace('#', '_').replace('*', '_') \
            .replace('>', '_').replace('$', '_')
            account_prefix = f'{mqtt_account_prefix}/{mqtt_topics.VEHICLES}/{vin_info.vin}'

This removed all of the TRYING TO WRITE TO CLOSED SOCKETS errors, an the data is now properly formed in the MQTT broker. I highly suggest performing this fix (and ensuring other character escaping is done in key places) before releasing 6.0.

Hi @ZionFox,
thank you for your analysis. Since email addresses can contain special characters like the plus sign (+) which has a special meaning in MQTT topics we had to introduce a method that removes those special characters.
Without this method the gateway crashes right on the start when it tries to subscribe to some topics.
Of course we have to do the same special character removal when we publish something. Unfortunately, this is still missing.
Sorry for that. This is hard to test without a SAIC user name that contains a special character.

I'm glad I can be the edge case for testing, then. I figured it was, fortunately the debug level of logging correctly showed the string being used for the requests, so I could identify the difference in character difference.
I understand MQTT requires string santiation, it just seems it was implemented when subscribing to topics, and overlooked when publishing. I'm looking forward to the patch, but if the PR has that patch I'll test it now.


Backup files naming schema

See here: https://github.com/overdodactyl/ShadowFox/issues/147
When the script runs it creates a backup of the existing css files and renames them. However, they retain the .css extension, which is causing them to be loaded by the userchrome.js extension.
Might I suggest that the files be renamed with an alternative extension? Perhaps something like
userChrome.backup.2018-03-08_10-05-27.css
Could instead be
userChrome.css.2018-03-08_10-05-27.bk
By the way, LOVE this script! Great work man :)

That is strange, because the program already backs up using the .backup extension instead of .css (for example this is how a backup i just made looks like: userChrome.css.2018-05-15-17-38-48.backup)
Are you running the latest version? What OS are you using?

@CaptaPraelium, is it possible the backups that you are referring to, and the ones causing problems, were generated with the old Windows updater?

@CaptaPraelium Any updates on this?

I've added a fork of the userChrome.js gist here:
https://gist.github.com/overdodactyl/c0c3698b7b9a635f3bf8c0ac9fcd3442
This version should only load files within the directory chrome/userjs_files, which is probably advisable for ShadowFox users anyways to prevent duplicate loading of the customization files.

 It was the old script. The file date was a dead giveaway. Sorry to have wasted your time guys :(


Inactive Tag

Meetings have started showing up at https://aasfmarin.org/find-a-meeting with an Inactive tag that SF/Marin has deleted from Airtable (see Friday At Five in screenshot). We're hoping to stop that from happening.
They disappeared after I refreshed the JSON feed.
What's happening exactly?

i don't see "Friday at Five" anymore, so perhaps you've IDed the issue?
the inactive meetings i see all look like they are online meetings without conference_urls

going to move this over to sheets since that's where the code is. TMSL UI appears to be renderng the feed correctly, but it sounds like some bad meetings are making it into the feed


fix: path to head assembly 3d parts

Fix path to head Head Assembly 3D parts and make the path a link.

LGTM


Bug : Hover Color on Links Matches Background Color on Home Page

There is an issue with the hover color for links on the home page. When users hover over the links, the color changes to match the background color, making the links invisible and negatively impacting the user experience.
Issue (example) : Hover Color Matches the background color
Please assign this issue to me so I can solve this as it makes the links invisible. @GarimaSingh0109

I can't assign you the issue. You should contact @khushi-joshi-05

I can't assign you the issue. You should contact @khushi-joshi-05

It was by mistake, I mentioned you. I wanted to mention her only.


[Bug]: Probabl custom API POST for http only with custom port not sending body

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When creating a custom api over HTTP (not https) with POST for sending a json content to OrientDB, postman may be either altering/not sending properly, resulting OrientDB reporting com.orientechnologies.orient.core.exception.OSerializationException: Error on unmarshalling JSON content: content is null, meaning it did receive an empty body.
The same setup works fine with the following sample curl : curl -X POST -u "user:pass" -d '{"transaction" : false,"operations" : [{"type" : "script","language" : "sql","script" : [ "select * from table;" ]}]}' "http://orientdb_server:2480/batch/somedatabase/"
I am sorry I know this is very specific case and can't help you access to anthe actual setup. I tested with various online tools to check appsmith is sending body or not but (it does), but not specifically on different port. May be the issue is with the destination custom port value.
Just reporting.
Steps To Reproduce
Define a new API with url POSTING to a http only connection over a custom port,  as described.
Public Sample App
No response
Version
18.1

Sorry lads, just did a wireshark capture, and seen that indeed appsmith is sending the post data for the custom port. So this is a weird situation. I will study more. For now i am closing this .

Further investigation revealed that appsmith api calls are not gziped, hence orientdb http server can not decode. Below is the scrap from orientdb logs
Error on decompressing HTTP response
java.util.zip.ZipException: Not in GZIP format
at java.base/java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:166)

This is related to #10180 (https://github.com/appsmithorg/appsmith/issues/10180#issue-1094165620)

This issue is solved by adding the following custom header into the API definiton in appsmith : accept-encoding: identity as defined in https://www.rfc-editor.org/rfc/rfc2616#section-14.3


Add charset checker tool

Many charsets (e.g., UTF-8) can have invalid bytes, while others will accept any byte (e.g., "windows-1252"). But, it would be nice, if we can, to try to read a file given a particular charset and see if we get any errors.
Would be nice to guess line endings as well.

This will be (somewhat) easy using the FileUtilities methods (readFileAsString), which allow selection of a charset.


enh: support taos_stmt2_get_stb_fields

Codecov Report
Attention: Patch coverage is 61.40351% with 22 lines in your changes missing coverage. Please review.

Project coverage is 77.39%. Comparing base (d1e1fc3) to head (187950f).

Files with missing lines
Patch %
Lines

controller/ws/ws/stmt2.go
29.41%
10 Missing and 2 partials :warning:

db/syncinterface/wrapper.go
0.00%
10 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              3.0     #363      +/-   ##
==========================================
+ Coverage   77.35%   77.39%   +0.03%
==========================================
  Files         142      142
  Lines       18069    18077       +8
==========================================
+ Hits        13977    13990      +13
+ Misses       3301     3299       -2
+ Partials      791      788       -3

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


[BUG] Some stats doesn't update if you're a client

Such values as Most Scrap Value Collected In 1 Round, Most Credits At Once and Total Times Fired doesn't update if you're a client on the server and not a host. Maybe even more values, but that's the only stats i've noticed that didn't get properly updated even though they should have been.
My team got $1172 credits, but the stats only show that Most Credits At Once is $371.
Most Scrap Value Collected In 1 Round was all the way to a thousand, but stats only show $139, because that's the value i've got in my solo, host run when i was testing the mod.
And i definitely got fired at least once when i was playing on someone's server, but the statistic only shows 0 times fired.
Here's my stats. Might get updated by the time someone reads this issue.

Thanks for letting me know, I'll take a look into why these are not firing.
The stats only send when you have completed a match somewhere that isn't the company building, so if you sell stuff and have $1000 credits, buy something and then play a match, your most credits will be the amount after buying, looking to change this though.


Add 'always-with-newlines' value to order's newlines-between option to allow newlines inside import groups

New option to allow newlines inside import groups. See #627.

Coverage increased (+0.003%) to 94.899% when pulling bfd6222e4e842d2a1a957e6ac16a25f573905090 on giodamelio:order-extra-newlines into d9605a0f2e048a903dc8e2f852f0d515bd7bb615 on benmosher:master.

Coverage increased (+0.003%) to 94.899% when pulling 42a780a88ad5b6076cb168a7979f8baf3d94d7a8 on giodamelio:order-extra-newlines into d9605a0f2e048a903dc8e2f852f0d515bd7bb615 on benmosher:master.

Coverage increased (+0.003%) to 94.899% when pulling eabec089180c78ed6a8af3cc161d9cbbabdeb49c on giodamelio:order-extra-newlines into d9605a0f2e048a903dc8e2f852f0d515bd7bb615 on benmosher:master.

@jfmengels Just wanted to ping you and check on the status of this. I would love to get it merged if everything is in order.

I just updated this to the current master, @benmosher, could you take a look at this?

Coverage increased (+0.003%) to 94.863% when pulling 5c1a3d1950e7455d3685776d0bf9a45690f2a249 on giodamelio:order-extra-newlines into bfdc2bbfa16c2d27fa24ee0665ffb41040ef696c on benmosher:master.

@giodamelio need @jfmengels to review, order is his baby 😄

Hey @giodamelio!
First of all, sorry for not replying earlier... Totally dropped the ball there.
Second of all, thanks a lot, this looks really good :)
The only thing I would like to see changed, is the new option name. In my mind, newlines-between: "always-with-newlines" means the same thing as newlines-between: "always". Maybe newlines-between: "always-and-inside-groups" would be more explicit? What do you think?
(apart for this, this LGTM, and I'll fine with merging this)

"always-and-inside-groups" sounds good to me. Fix incoming.

Coverage increased (+0.003%) to 94.912% when pulling 9507de9e20cec85ab268590dfed4d263d0a22f03 on giodamelio:order-extra-newlines into ffc020530380b78143dbc50c520bb47a725a924c on benmosher:master.

Should be all good to go.

Thanks a lot @giodamelio! :tada:

Coverage increased (+0.003%) to 94.912% when pulling 9639f2ed989e5be151f98ca5f1a4d5b577f433ea on giodamelio:order-extra-newlines into ffc020530380b78143dbc50c520bb47a725a924c on benmosher:master.

Coverage decreased (-1.3%) to 93.612% when pulling 9639f2ed989e5be151f98ca5f1a4d5b577f433ea on giodamelio:order-extra-newlines into ffc020530380b78143dbc50c520bb47a725a924c on benmosher:master.

Coverage decreased (-1.3%) to 93.612% when pulling 9639f2ed989e5be151f98ca5f1a4d5b577f433ea on giodamelio:order-extra-newlines into ffc020530380b78143dbc50c520bb47a725a924c on benmosher:master.


I am using Pycharm, but I tried to run the code the debugger failed. I tried on to different devices same issue.

If your debugger fails to attach to certain parts of the code you may try to reduce the number of data loader workers (parameter “num_workers” in the config.json file) to 0. This makes sure that all of the code runs in the same process. Otherwise PyTorch Starts processes according to the number of workers to feed the data in a parallel manner to the pipeline. This usually confuses the debugger.

Ok, I will give it a try. By the way, thanks a lot for this great and simple framework.


Address Pavlos's feedback

Collaboration with @annacarey
Addresses @pvinis 's feedback in #31

Very very cool! :D


Make defining output structure more natural and intuitive

The way to phrase and use the llm_output_adapter directive isn't super intuitive and we frequently run into cases where we confuse the LLM resulting in issues like #43 on top of that, as we add more types of output adapters it becomes a harder documentation problem where you need to remember the different names for the different adapters you want to use.
This problem is partially resolved with the generator generator in that it can usually get you the output structure you want, but it would be nice to be easier to write.
Came up with an idea the other night of changing it to something like:
# Single String
generates name: "description"

# List of named strings
generates review_summaries: [
  review: {
    movie_title: "the title of the movie",
    reviewer_name: "the name of the reviewer",
    rating: { description: "the rating given by the reviewer (out of 5 stars)", type: :integer},
    brief_comment: "a brief summary of the movie"
  }
]

Where we'd do a bunch of processing behind the scenes to map them to the different output adapters.
The benefits of going down this route are that you're able to use the symbols and literals that you're familiar with to imply the structure you want back, simply write out the names and descriptions of the variables that you want the llm to generate, and implies the perspective that you should be describing the output as: "from the perspective of the model"
The one downside I see here is that it does somewhat look like a giant blob of json, but the more complex output adapters I've been putting out feel like they're getting kind of ugly and we're reaching the end of usefulness of that design...

Spent a bunch of time exploring this path today but ran into a bit of a wall. It seems like using this syntax we'd need to make the description key required in a bunch of different places (like when you start defining a new object) and this gets kind of messy and surprising in certain cases and I haven't come up with a good solution.
For example, in that example above you'd need to add a description key to the review object and the review_summaries object and would look something like this:
generates review_summaries: [
  description: "some description",
   review: {
    description: "an individual review object",
    movie_title: "the title of the movie",
    reviewer_name: "the name of the reviewer",
    rating: { description: "the rating given by the reviewer (out of 5 stars)", type: :integer},
    brief_comment: "a brief summary of the movie"
  }
]

Part of the reason we'd be trying to build this DSL is to make it so you don't have to remember all these required fields and build out a massive structure and it feels like if we start going down this path we'll end up with a bunch more things to remember and then just end up back at writing out entire JSON schemas...so it's back to the drawing board a bit on this one...


[RFC] Multiple changes

Add axidma_get_residue()

This commit adds a new IOCTL which can be used to retrieve the residue (= how many bytes weren't transmitted/received), which can be used to calculate how many bytes were really received.
Unfortunately the Xilinx kernel is bugged at the moment and always returns 0, no matter how many bytes have been actually transmitted. As soon as I understand which is the procedure to propose kernel patches to Xilinx I'll try to get my patch merged.

Add MODULE_DEVICE_TABLE to automatically load the module when needed

If this module is built in-tree (Linux doesn't automatically load out-of-tree modules), a matching entry in the DT is enough to automatically load this module.

Add support for multiple AXI DMA devices

To accomplish this a couple of backward-incompatible changes were needed. The library interface is the same, but the IOCTLs have changed a little.
The channel_id value in the callback is now passed in the sig_info.si_errno field: this is not very clean, but it is easy to be implemented (and the si_errno field wasn't used anyways). Feel free to criticize this solution.
Tell me if you're interested in some (or all) of these commits.

Hi @corna, thanks for sharing your updates! I'm a bit busy today, but I'll take a look within the next few days.

Got it, yeah unfortunately that's a big downside with the driver is the lack of handling inter-process and inter-thread synchronization. When I first wrote the driver, I was on a tight deadline for a class project, and I decided to skip doing that.
Having a file for each AXI DMA engine is a good intermediate workaround, but long term I prefer keeping everything in one character device and uses proper synchronization to allow multiple processes to access the DMA engines.
If you don't mind I'd like to take the residue and MODULE_DEVICE_TABLE commits, but not the multi-process support commit. It's definitely very useful, but I want to maintain backward compatibility in terms of the clean interface of having a single character device. There will definitely people who will need multi-process support, so I'll add a reference to your fork in the README.

The updates to the README are in b7d2ea0.

No problem, I already knew it was a questionable big change.
I'm currently in contact with the Xilinx kernel devs, which have pointed out that the residue is supposed to be reported only when the DMA transaction is in progress
Please refer kernel-doc- include/linux/dmaengine.h
 * @residue: the remaining number of bytes left to transmit
 * on the selected transfer for states DMA_IN_PROGRESS and
 * DMA_PAUSED if this is implemented in the driver, else 0 */ struct
 dma_tx_state { dma_cookie_t last; dma_cookie_t used;
 u32 residue;
 };

We're figuring out a way to report this kind of information, so I suggest you to avoid merging the residue commit for now.
Thanks for the mention in the README btw.

Got it, yeah I guess I'll wait to merge the changes in until that issue is resolved. And no problem.

Is there are any plans to introduce the Multi-Process Support? I realy want to use AXI MCDMA with 3 tx channels in parallel thread. Can you impruve this driver with multi-channel mode? AXI MCDMA is available since 2019 in Xiilinx DMA driver in Linux, it is time to get it in operation.


Module build failed (from ./node_modules/eslint-loader/index.js):   Error: Failed to load plugin html: Cannot find module 'eslint-plugin-html'

Version
3.0.1
Reproduction link
https://github.com/acacha/vue-cli-problem-laravel
Node and OS info
node v8.10.0 npm 6.4.1 Ubuntru <IP_ADDRESS> LTS
Steps to reproduce
Clone the repo provided:
cd vue
npm install
npm run test:unit
 WEBPACK  Failed to compile with 1 error(s)

Error in ../resources/js/components/ExampleComponent.vue

  Module build failed (from ./node_modules/eslint-loader/index.js):
  Error: Failed to load plugin html: Cannot find module 'eslint-plugin-html'

 ERROR  mocha-webpack exited with code 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:unit: `vue-cli-service test:unit`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:unit script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!
No errors
What is actually happening?
Error Module build failed (from ./node_modules/eslint-loader/index.js):
Error: Failed to load plugin html: Cannot find module 'eslint-plugin-html'

I'm trying to test components outside vue-cli folder
See also issue:
https://github.com/vuejs/vue-cli/issues/2539
I followed suggestion to add file vue.config.js:
const path = require('path');
module.exports = {
    chainWebpack: config => {
        config.module
            .rule('eslint')
            .use('eslint-loader')
            .tap(options => {
                options.configFile = path.resolve(__dirname, ".eslintrc.js");
                return options;
            })
    },
    css: {
        loaderOptions: {
            postcss: {
                config:{
                    path:__dirname
                }
            }
        }
    }
}

Please note that the problem arise because test:
https://github.com/acacha/vue-cli-problem-laravel/blob/master/vue/tests/unit/ExampleComponent.spec.js
use a external component;
import ExampleComponent from '../../../resources/js/components/ExampleComponent'

What I'm trying to do is to test My Vue Laravel Components using a vue-cli project created inside Laravel

The problem is a litle bit ankward .... I created another repo to demonstrate here:
https://github.com/acacha/vue-cli-problem-laravel1
But NO error in this repo! And I don't see any differences

The problem is that you have another .eslintrc file in your project's root directory, which has conflicting configuration (and may not even be used anywhere?) - in particular, this confi tries to load eslint-plugin-html, which it can't find because it's not even a dependency of your project.

I'll close this since it seems to be related to a misconfiguration of eslint on the user's side.


Ability to change icons on files and folders

What's the Problem?
No response
Solution/Idea
You can change icons on files / folder like File Explorer

Alternatives
You can change shortcut icons on files / folders

Priorities
| Capability | Priority |
| :---------- | :------- |
| This proposal will allow developers to accomplish W | Must |
| This proposal will allow end users to accomplish X | Should |
| This proposal will allow developers to accomplish Y | Could |
| This proposal will allow end users to accomplish Z | Won't |

Files Version
v<IP_ADDRESS>
Windows Version
Windows 10 Home 21H1 19043.928
Additional comment
No response

Merging with #1015


Add: Function telemetry scope middleware

Description
Another feature used and therefore duplicated across domains is the need to handle the TelemetryDependcy's.
This PR will add the middleware FunctionTelemetryScopeMiddleware to the Energinet.DataHub.Core.App package.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@d249eef). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #101   +/-   ##
=======================================
  Coverage        ?   66.56%
=======================================
  Files           ?      134
  Lines           ?     2408
  Branches        ?      360
=======================================
  Hits            ?     1603
  Misses          ?      679
  Partials        ?      126

Flag
Coverage Δ

appcommon
20.70% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Add https auto configuration with LetsEncrypt

Ah brilliant... on the first looks it seems like it would work, I didn't remember you could explicitly specify domains

tried with another domain and it works nice, so I put the "target domain" to be ready. Later on we can add more subdomains (but it'll be also up to Wim for adding them to dns)
I talk about subdomains because it's much easier to configure traefik for a subdomain than not for a HostPath (and maybe hostpath is going to be modified by our app? we should avoid overwriting)


mac architectures build

Darwin OS builds for Preflight:  Intel Mac,  Apple Silicon Mac.
Pending - adjust the GH Actions.
Fixes #850

Coverage: 84.186%. Remained the same when pulling df75620701991dddd494ccd57d0e20f8ea55c151 on itroyano:feature/mac-build into e4eba70991b3c56c75abbe62eae47b154f3c4d89 on redhat-openshift-ecosystem:main.

/ok-to-test

/test 4.15-e2e

/test 4.15-e2e

/test 4.15-images

/test 4.15-e2e

/test 4.15-e2e

@acornett21 is this mergable or can it be merged soon? Would be handy to have.

@redhatrises I don't think this is ready for merge, and I don't think there was a consensus for the approach. Due to most of the team working on other higher priority issues, I'm not sure when this can be revisited.


Add a changeDayAtMidnight option

When enableTime is on, and the user increments/decrements the hour selector past midnight, the normal behaviour is that the date doesn't change.
This PR adds an option called changeDayAtMidnight that also increments or decrements the date when the user moves past midnight in either direction, which is the expected behaviour for a lot of applications.
I haven't added any tests but please shout if you need them and I'll try to add them in.

Coverage decreased (-0.5%) to 84.7% when pulling 9bdb8b16e5435ca68bba9222327cbbe983f31ecf on fishpercolator:changeDayAtMidnight into 810e66089444721b92f43a2162cb4505ca1fd7aa on chmln:master.

Hello,
Thank you for contributing :+1:
I actually believe that it's better to have a separation of concerns, with time choice not affecting date choice and vice versa.
I also don't think that every time a user increments time past midnight they actually aim to increment their date selection.
Its awesome that you're comfortable enough with the codebase to submit a PR.
Your code should be easily portable to a plugin.

Hi @chmln - thanks for your comment.
I agree that not everyone wants this behaviour, which is why I made it an option rather than the default.
In my application it's absolutely essential because I have an "end time" that's set based on the "start time" and users were getting very confused about why when they increased the end time past midnight the form couldn't be submitted (because the date was wrong). I can imagine other applications might have similar use cases.
I'm happy to try to port this to a plugin if you think you will accept it upstream in that case? Any documentation you have on how the plugins work when they integrate with flatpickr internals would be very helpful.


License?

I just noticed this repository has no LICENSE file.  package.json says BSD, but which type of BSD license specifically?

attn @maxogden

sorry, fixed now

Thanks!


Install Trouble

I can't install @nuxtjs/gtm
I type below,
npm install -save @nuxtjs/gtm
then, get this error message…
ENOENT: no such file or directory, rename '/path/to/my/project/node_modules/.staging/@nuxtjs/apollo-ca81020e/node_modules/apollo-link' -> '/path/to/my/project/node_modules/.staging/apollo-link-eade7497'

What is wrong?
This is my environment
$ node -v
$ v10.13.0
$ npm -v
$ 6.4.1

Sorry, that was my problem. So I'll close it.


Feature/add conda recipe

Coverage remained the same at 100.0% when pulling 0e46af5773d47416fef7f6dddbede0874ed6e660 on feature/add-conda-recipe into e2b5b4daedf9df0e7e73477b40c1b4a34c72c6d0 on develop.


There is no disable for TextInput and CountrySelect by default

With my project I need to disable component with certain conditions, but component have no this prop by default. I think, you should add prop editable for component, which disable onPress for CountryPicker and makes TextInput uneditable.
Now I can do it only with props
onPressFlag={() => false}
textProps={{ editable: false }}

for PhoneInput component, but it's crutch!

Thank you i was looking for that

Hi all,
disabled was added in v 0.2.0
thanks for your request.


Return error code for Rule insert and delete

Currently, rule_insert() and rule_delete() ofproto provider APIs donot
have return values.
There are some possible scenarios where rule insertions and deletions can
fail at runtime even though the static checks during rule_construct() had
passed previously.
Some possible scenarios for failure of rule insertions and deletions:
**) Rule insertions can fail dynamically in Hybrid mode (both Openflow and
Normal switch functioning coexist) where the CAM space could get suddenly
filled up by Normal switch functioning and Openflow gets devoid of
available space.
**) Some deployments could have separate independent layers for HW rule
insertions/deletions and application layer to interact with OVS. HW layer
could face any dynamic issue during rule handling which application could
not have predicted/captured in rule-construction phase.
This patch is the first step to introduce error reporting for rule
insertions/deletions from Client back to OVS.

This was already reviewed on the ovs-dev mailing list.


example cross account resource name

Small documentation fix.

Thanks for @mtesch-um for your pull request.
Similar changes were merged with https://github.com/brainly/terraform-provider-redshift/pull/77, so I'm closing this one.


Lengths of TTrees/TBranchElements

This is just a minor thing, so set this to the lowest priority please ;)
In uproot4, the length is now returning the number of subbranches, while in uproot3 it was the number of "items" (number of entries from fBasketEntry), basically the array lengths of the subbranches, so to say. In my uproot3 based libraries I was relying on len(f["path"]) to reflect the number of entries and used that to iterate over a branch. For uproot4, the public .num_entries attribute can be used, which is of course fine.
I already added that to the wiki, but I wanted to quickly ask about the intention behind it.
I guess the main idea was to be more close to the dict interface since the ROOTDirectory class behaves like such, where len() also returns the number of keys. I am not sure if this is really the most common use-case in the uproot-context but it's of course not a big deal.
Anyways, the only thing I find a bit confusing though is the fact that len() does not count nested entries whereas keys() lists them, so len(branch) != len(branch.keys()), as seen in the example below. So I am wondering if keys() should only show the first level entries, to be conform to the dict() interface.
Let me quickly copy the example from the Wiki here just for the sake of completeness (and in case the Wiki is later emptied after the possible doc-migration):
from skhep_testdata import data_path

import uproot as uproot3
import uproot4

branch = "E/Evt"

f3 = uproot3.open(data_path("uproot-issue431b.root"))
f3[branch]
# <TBranchElement b'Evt' at 0x00010f15f5e0>
len(f3[branch])
# 10
f3[branch]["id"].array()
# array([ 1,  2,  3,  4,  5,  6,  7,  8,  9, 10], dtype=int32)

f4 = uproot4.open(data_path("uproot-issue431b.root"))
f4[branch]
# <TBranchElement 'Evt' (22 subbranches) at 0x00010f37a2b0>

len(f4[branch])
# 22

len(f4[branch].keys())  # note that this will also count nested entries
# 118

f4[branch].keys()
# ['AAObject', 'AAObject/TObject', 'AAObject/TObject/fUniqueID', ...,
#  'mc_trks/mc_trks.hit_ids', 'mc_trks/mc_trks.error_matrix', ...]

len([k for k in f4[branch].keys() if "/" not in k])  # only top-level subbranches
# 22

f4[branch].num_entries
# 10

The __len__ method is part of the Mapping protocol, and although I don't see it written down anywhere, I think the implication is that __len__ must be the number of items that __iter__ would yield. I struggled with that in Uproot 3, but TTree in Uproot 3 didn't officially support the Mapping protocol. (It just duck-typed relatively well.)
You're right that ReadOnlyDirectory has more reason to be a Mapping than HasBranches, but these two things are more fully integrated now—you can "getitem" through directories into branches, a feature that partially worked by accident in Uproot 3, which I found out about because people used it in their examples. (That's clearly a desire path. And explicitly requested and user-contributed.) For example, we can treat branches and subbranches as though they were directories in a single string with slashes:
>>> import uproot4
>>> import skhep_testdata
>>> f = uproot4.open(skhep_testdata.data_path("uproot-nesteddirs.root"))

>>> f.keys()
['one;1', 'one/two;1', 'one/two/tree;1', 'one/tree;1', 'three;1', 'three/tree;1']

>>> f["one/two/tree"].keys()
['Int32', 'Int64', 'UInt32', 'UInt64', 'Float32', 'Float64', 'Str', 'ArrayInt32', 'ArrayInt64', 'ArrayUInt32',
 'ArrayUInt64', 'ArrayFloat32', 'ArrayFloat64', 'N', 'SliceInt32', 'SliceInt64', 'SliceUInt32', 'SliceUInt64',
 'SliceFloat32', 'SliceFloat64']

>>> f["one/two/tree/Int32"]
<TBranch 'Int32' at 0x7fa5792740a0>

Having both of these things, which are treated equivalently, both satisfy the Mapping protocol removes the friction I'd expect if one were a Mapping and the other were not. That's also why we don't have "TTree" behavior, we have "HasBranches" behavior, because a TTree with branches can be treated the same way as a branch with subbranches.
Now, it is a pain point that len(ttree) returns the number of branches, rather than the number of entries. Without any of the motivations described above, I'd expect len(ttree) to be the number of entries (which is, I guess, why that was the case in Uproot 3). But if so, then what's __iter__? I think I made __iter__ raise an exception in Uproot 3 because I know what users might be thinking, and it's not that.
We can see some of this cognitive dissonance here:
>>> events = uproot4.open(skhep_testdata.data_path("uproot-Zmumu.root"))["events"]

>>> len(events)
20
>>> events.num_entries
2304

>>> for branch in events:
...     print(branch)
...
<TBranch 'Type' at 0x7fa5791ac4c0>
<TBranch 'Run' at 0x7fa5791acc10>
<TBranch 'Event' at 0x7fa5791b0370>
<TBranch 'E1' at 0x7fa5791b0a90>
<TBranch 'px1' at 0x7fa5791b0f40>
<TBranch 'py1' at 0x7fa5791b6910>
<TBranch 'pz1' at 0x7fa5791b6dc0>
<TBranch 'pt1' at 0x7fa5791bc790>
<TBranch 'eta1' at 0x7fa5791bceb0>
<TBranch 'phi1' at 0x7fa5791c2610>
<TBranch 'Q1' at 0x7fa5791c2d30>
<TBranch 'E2' at 0x7fa5791c9490>
<TBranch 'px2' at 0x7fa5791c9bb0>
<TBranch 'py2' at 0x7fa5791ce310>
<TBranch 'pz2' at 0x7fa5791cea30>
<TBranch 'pt2' at 0x7fa5791ceee0>
<TBranch 'eta2' at 0x7fa5791d48b0>
<TBranch 'phi2' at 0x7fa5791d4fd0>
<TBranch 'Q2' at 0x7fa5791d9730>
<TBranch 'M' at 0x7fa5791d9e50>

>>> for event in events.arrays():
...     print(repr(event))
...
<Record ... phi2: -0.441, Q2: -1, M: 82.5} type='{"Type": string, "Run": int32, ...'>
<Record ... phi2: 2.74, Q2: 1, M: 83.6} type='{"Type": string, "Run": int32, "Ev...'>
<Record ... phi2: 2.74, Q2: 1, M: 83.3} type='{"Type": string, "Run": int32, "Ev...'>
<Record ... phi2: 2.74, Q2: 1, M: 82.1} type='{"Type": string, "Run": int32, "Ev...'>
<Record ... phi2: -2.71, Q2: -1, M: 90.5} type='{"Type": string, "Run": int32, "...'>
<Record ... phi2: 0.583, Q2: 1, M: 89.8} type='{"Type": string, "Run": int32, "E...'>
...

If we make len(ttree) be ttree.num_entries, then we should also make iter(ttree) be iter(ttree.arrays()), though I would not recommend the latter for performance—I certainly wouldn't want to make it easy or suggest that it's the right way to go by making it __iter__.
So what do we do if one motivation (slicing through directories) implies one design and another motivation (Pythonic length/iteration) implies another? In this case, Pythonic iteration is also something I'd recommend against, so that's why the first motivation won.
(Incidentally, in Julia, there would be nothing wrong with naive iteration over such an object. Some physical properties of the implementation—like the performance of Python—have interface consequences.)

OK, thanks for the detailed clarification, as always, it makes of course sense. I also agree with your last comment about performance subtleties dictating interface design.
Let's close this then. I will put a link to this issue into the wiki!


Adding service to search leagues by its name

Coverage decreased (-0.08%) to 34.706% when pulling c0b15163c58c707b7271ecf7ade94cce6537f0c0 on dev into a6613fd34218b92d7be7b9d2143b1c6d6fb3439e on master.


fix(README): Fix build badge

A simple commit to test the new pipeline

Coverage remained the same at 96.653% when pulling c1b83b69605eb5bce4aebde974561896cae29952 on mttrbrts-patch-1 into 4555788b4fce67e495d141455c2f04de3617d31f on master.


Zuul2 Benchmark

Where could i find the zuul2's doc about pressure test benchmark?

I'm planning to add a benchmark config to the sample app.
On Wed, Jul 4, 2018 at 2:22 AM yuanyetao<EMAIL_ADDRESS>wrote:

Where could i find the zuul2's doc about pressure test benchmark?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/zuul/issues/472, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4DnsjLqnG_A6FPM_JhyAIcoc6ee7E0ks5uDIk-gaJpZM4VCPlr
.

Added: https://github.com/Netflix/zuul/wiki/Benchmarking


Terminal terminator

Will Gogh-co work in a terminator? Is there any way to run it?  Will you support it?

The contributions to this project are made by community initiatives doing PR directly, we do not have a roadmap.
The only reference to terminator is this thread: https://github.com/Gogh-Co/Gogh/issues/1
All contributions are welcome.


adopt CSS variables for primary background and text

Part of #3017.

I think it's hard to make sure all (and only) the relevant places are updated but it should be easier figure it out later when your dark mode is implemented, and it should not break the existing style otherwise.

My reasoning as well. Also I think quite a lot of these statements could be removed in favor of inheritance in a later round.


Make status endpoint

It would be handy for people designing things that autodetect when the VPN has de-authenticated to have an easy way of getting that information.
/status would work perfectly and also be open for sharing more details about the connection

Sweet all done.


Unable to find referenced entities switch.*

Hi there,
I am using 1.2.3 version and have added Sonof Mini.
When I try to switch it on/off from HA, this is what I got in logs and the switch doesn't react.
Please help
Logger: homeassistant.helpers.service
Source: helpers/service.py:129
First occurred: 9:06:44 PM (3 occurrences)
Last logged: 9:07:04 PM

Unable to find referenced entities switch.xxxxxxxxxxx

suggest you try this
It is recommended that you upgrade to the latest version of addon.
If you have any more questions, please reopen this issues. Thank you for your reply.


[Feature request] last frame preview

So, first of all, amaizing tool ❤ , its realy usefull and well designed.
My Idea was that there is an option to enable a preview of the last frame you made. (simular to the preview of the layer beneath)
This would be realy usefull for creating more complex animations and I think is also easy to implement.
The only other thing would be a scroller to change opacity for the last frame.
If this request or feature already exists, Im sorry but I could not find anything about it.

you mean like onion skinning?

Ah, exactly. Would be really nice to have a button for this because looking it up in the key-shortcuts would be the last place where I look. Or is there one?

we have a button. Its onion icon, on the right

Ahhhhh, wow, never would have expected that this is the function of the button. Maybe put the option in the settings rather than there because I thought it would have to do something with the preview.

i think its good where it is- makes sense

Then leave it as it is, personaly I found it confusing but when nobody else has the same problem, it should be fine. But awesome tool you created there, realy enjoying it. ❤ 👍

This GitHub issue helped me find this feature! Thanks for asking, and thanks for answering!!


Data loss in influxdb due to aggregators

I am pushing data from NATS to InfluxDB using Telegraf. The data is being generated continuously, which results in multiple entries having the same timestamp. My timestamps are in nanoseconds, but in InfluxDB, the data is being aggregated, causing a loss of data points in my Grafana dashboard.
Can any one suggest how to avoid data loss.
example data.
requestsRaw,ObjectType=requestsRaw,errorMessage=noData,errorResponseBody=noData,host=server-3,nodeName=Test-Node,requestName=WebSocket\ request-response\ Sampler,responseCode=200,result=pass,runId=R_20241015-1415,samplerType=transaction,subject=nats.subject.requestsraw,testName=Test time=1728981942717004500,count=1,errorCount=0,sentBytes=1467,timeStamp=1728981940732,receivedBytes=59275,latency=0,processingTime=0,connectTime=0,responseTime=3151<PHONE_NUMBER>717004544
requestsRaw,ObjectType=requestsRaw,errorMessage=noData,errorResponseBody=noData,host=server-3,nodeName=Test-Node,requestName=WebSocket\ request-response\ Sampler,responseCode=200,result=pass,runId=R_20241015-1415,samplerType=transaction,subject=nats.subject.requestsraw,testName=Test latency=0,receivedBytes=59275,time=1728981942717004500,errorCount=0,responseTime=1276,count=1,processingTime=0,sentBytes=1467,timeStamp=1728981942619,connectTime=0<PHONE_NUMBER>717004544
Below is my telegraf configuration
[[inputs.nats_consumer]]
servers = [“nats://localhost:4222”]
subjects = [“nats.subject.requestsraw”]
data_format = “xpath_json”
xpath_native_types = true
fieldexclude = [“subjects”, “runId”, “testName”, “nodeName”, “ObjectType”, “errorMessage”, “errorResponseBody”, “requestName”, “responseCode”, “result”, “samplerType”]
[[inputs.nats_consumer.xpath]]
metric_name = “‘requestsRaw’”
metric_selection = “/"
timestamp = “time”
timestamp_format = “unix_ns”
field_selection = "”
[inputs.nats_consumer.xpath.tags]
runId = “string(/runId)”
testName = “string(/testName)”
nodeName = “string(/nodeName)”
ObjectType = “string(/ObjectType)”
errorMessage = “string(/errorMessage)”
errorResponseBody = “string(/errorResponseBody)”
requestName = “string(/requestName)”
responseCode = “string(/responseCode)”
result = “string(/result)”
samplerType = “string(/samplerType)”

I'm not sure what you mean by aggregate (could you explain?) but I believe these docs address what I think is happening to you:
https://docs.influxdata.com/influxdb/v1/write_protocols/line_protocol_tutorial/#duplicate-points


Pre-trained model

Hi, thank you so much for adding a DQN server on top of Hao Wang's work! I believe that's lots of effort.
I am still trying to understand the workflow in this set of code and I got confused about the following configs:
"trained_model": "output/dqn_models/dqn_10-100_model_174.h5",
"pca_model": "output/dqn_models/pca_10-100.pkl"
Where can I get the pre-trained model from? Do they get generated before they are used in the code? There is no such folder/file in the 'output' directory.
Thank you so much!

Thanks for the interest and question! The DQN model needs to be trained before being loaded again for testing on device selection. Therefore, the trained_model is the saved best trained DQN model. You can start the DQNTrain server by setting the config file option "server": "dqntrain" to obtain the best weights. You can refer to /dqn_noniid_2_10.json for this training setting.


Use prefixes in generated documentation

Related to #540 and #257 , also here, prefixes should be defined and used.
See e.g. here: https://www.w3.org/TR/vocab-dcat-3/#namespaces

Now prefixes are used in IRIs

But they are not defined. This should be an additional section "Used Prefixes":
e.g.

from https://semiceu.github.io/GeoDCAT-AP/930/releases/3.0.0/#used-prefixes


sslv3 error when targeting bosh directors

I have installed the latest version of the BOSH CLI gem (1.3262.0) on a computer running OS X 10.10.5 and using the system libssl (0.9.8zg). When attempting to target any bosh director (including a the latest version 1.3261.1.0), I receive the following warnings and eventual error:
[WARNING] cannot access director, trying 4 more times...
[WARNING] cannot access director, trying 3 more times...
[WARNING] cannot access director, trying 2 more times...
[WARNING] cannot access director, trying 1 more times...
cannot access director (SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: sslv3 alert handshake failure)

When I attempt to do the same using a Ruby compiled with a more-modern SSL (1.0.2d) (via brew install ruby), I am able to successfully target the bosh director.
Suggestion: If it is possible to determine which SSL versions are unsupported (via require 'openssl'; OpenSSL::OPENSSL_VERSION), provide a helpful error message guiding the user to a resolution.

You may also be able to solve this by running...
gem install httpclient

This also came up on cloudfoundry#bosh and sounded like "old ruby was the issue".

I tried that on my machine (also tried updating the Gemfile used when I set BOSH_USE_BUNDLER to use httpclient 2.7.2 and 2.8.0), and there was no change.

+1, also having this problem. Think it may be related to an old openssl version

same here.
[WARNING] cannot access director, trying 2 more times...
[WARNING] cannot access director, trying 1 more times...
cannot access director (SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: sslv3 alert handshake failure)
Connection to pcfdemo.net closed.
➜  bosh-init-test git:(master) ✗ bosh --version
BOSH 1.3262.0
but bosh cli (BOSH 1.3215.3.0) inside of opsmanager works to the same director VM.

I'm also getting the similar problem in my OS X.
bosh target <IP_ADDRESS> lite
[WARNING] cannot access director, trying 4 more times...
[WARNING] cannot access director, trying 3 more times...
[WARNING] cannot access director, trying 2 more times...
[WARNING] cannot access director, trying 1 more times...
cannot access director (SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol)
ruby --version
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin14]
bosh --version
BOSH 1.3262.0

+1. However, BOSH install docs do say to use 'a non-system ruby'.
So as a workaround:
brew install ruby
bash
gem install bosh_cli --no-ri --no-rdoc
bosh target x.y.z.a

Worked for me after facing the same issue w/system ruby.
/M

worked for me as well

+1
I found the error message "[WARNING] cannot access director, trying 4 more times..." unhelpful, in part because I didn't know a more useful message was coming later. I assumed it was a network issue and wasted a few hours debugging from that perspective.

For future readers, if the above suggestions don't work, the new BOSH CLI which is still under development handles TLS connection errors a bit more clearly if you want to give it a try and provide feedback. Link to cloudfoundry/bosh-cli repository to build and some migration notes.
Ruby CLI is mostly frozen, so it's probably not something we'll be trying to fix in favor of suggesting users switch to the new CLI.

Closing - not changing the Ruby CLI. Avoid using outdated, system Ruby versions in the meantime.


Legacy sdk

...

Idk my bot handles all these things but if the bit requested it.  It was probably for a reason.
Sent from Yahoo Mail for iPhone
On Monday, June 8, 2020, 4:58 AM, Marcin Rataj<EMAIL_ADDRESS>wrote:
@lidel requested changes on this pull request.
Hi, what is the purpose of this PR?
Was this opened by mistake?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

legacy branch is no longer maintained and is incompatible with the latest master.
if you did not choose to do this, looks like this was an error caused by your automation, I am closing this.


ImageViewerModuleLinuxFix

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #271
Description
added "gtk" dependency in opencv for Linux and ARM , now we can use ImageViewer module on Linux and ARM and can render through webcam
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
NO
Type Choose one: Feature
Screenshots (if applicable)
Checklist

[x] I have read the Contribution Guidelines
[x] I have written Unit Tests
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach

Lets try a little more on ARM before making a definitive decision


Table: Add Comparer property to support record types.

Description

Resolves #4988. This PR adds a Comparer property to support record types in tables. See additional discussion on #4938
How Has This Been Tested?

All existing tests pass and I will add some new ones. I wanted to get this PR started so discussion can occur on it.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

@henon I'm going to add a docs section along with a warning about using record types. This is otherwise an easy thing to miss.

Finally got that unit test done 😅 @henon

I see only two lines that aren't covered, one in a setter the other in a getter. I don't think it there is terribly much value in getting these two lines covered, but if you want to go all the way it is as easy as checking the comparer can be read back after setting it and setting SelectedItem to a value that equals the SelectedItem with a comparer != null.

Ok great, I am close to done with a short test that checks the Comparer value is set correctly.

@henon ready!

@henon A slight issue- I accidently missed the "Example" suffix on my new docs example and as a result the Show/Hide code button doesn't work. Is it easiest to fix this from this PR or from a new one?

Don't worry about it, I'll fix it myself


mc-image-helper fails when both WHITELIST and EXISTING_WHITELIST_FILE: SYNCHRONIZE is set

Describe the problem
If you use the following content I am handing you out in this issue, you will obtain the respective issue.
However, undefining the EXISTING_WHITELIST_FILE, the container will successfully launch with no issue.
This is contradictory to the documentation, which does say that both may be used:

See https://docker-minecraft-server.readthedocs.io/en/latest/configuration/server-properties/#whitelist-players.
Container definition
Dockerfile
FROM itzg/minecraft-server:latest

COPY assets/ /assets

Docker Compose
services:
  mc:
    build:
      context: .
      dockerfile: mc.Dockerfile
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"

    environment:
      EULA: "TRUE"
      TYPE: FABRIC
      VERSION: 1.20.6
      USE_AIKAR_FLAGS: true
      SNOOPER_ENABLED: false
      ONLINE_MODE: false

	  [...]

      # Whitelist + Server operator
      ENABLE_WHITELIST: true
      ENFORCE_WHITELIST: true
      WHITELIST: |
        843919ddeebc4932a39c7ee372c88dc7
      EXISTING_WHITELIST_FILE: SYNCHRONIZE

    volumes:
      - mc_data:/data

volumes:
  mc_data:

Container logs
mc-1  | [mc-image-helper] 20:34:17.308 INFO  : Fabric launcher for minecraft 1.20.6 loader 0.15.11 is already available
[...]
mc-1  | [init] Enabling whitelist functionality
mc-1  | [mc-image-helper] 20:34:24.074 ERROR : 'manage-users' command failed. Version is 1.39.3
mc-1  | com.fasterxml.jackson.databind.exc.MismatchedInputException: No content to map due to end-of-input
mc-1  |  at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1]
mc-1  | 	at com.fasterxml.jackson.databind.exc.MismatchedInputException.from(MismatchedInputException.java:59)
mc-1  | 	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4996)
mc-1  | 	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4898)
mc-1  | 	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3733)
mc-1  | 	at me.itzg.helpers.users.ManageUsersCommand.loadExistingJavaJson(ManageUsersCommand.java:269)
mc-1  | 	at me.itzg.helpers.users.ManageUsersCommand.processJavaUserIdList(ManageUsersCommand.java:139)
mc-1  | 	at me.itzg.helpers.users.ManageUsersCommand.call(ManageUsersCommand.java:101)
mc-1  | 	at me.itzg.helpers.users.ManageUsersCommand.call(ManageUsersCommand.java:35)
mc-1  | 	at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
mc-1  | 	at picocli.CommandLine.access$1500(CommandLine.java:148)
mc-1  | 	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
mc-1  | 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
mc-1  | 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
mc-1  | 	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
mc-1  | 	at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
mc-1  | 	at picocli.CommandLine.execute(CommandLine.java:2174)
mc-1  | 	at me.itzg.helpers.McImageHelper.main(McImageHelper.java:159)```

Your whitelist.json file must be invalid since it is unable to edit the existing content. Remove the file and let the container startup again to update.

That is correct. Apologize for the false-report. :sweat_smile:


Limbo players counter

Could be is not related to the autobuyer funcionality but players get into the limbo and would be nice to check how many are there.
if someone can share documentation of FUTAPP API to test improvements myself would be nice.
PD:Thanks for this great tool

By Limbo you mean when number of unassigned players exceeds 50?

By Limbo you mean when number of unassigned players exceeds 50?

Yes. Would be nice to know how many players are unassigned.

Yes. Would be nice to know how many players are unassigned.

Yeah sure , but for now using this method to get the count https://www.reddit.com/r/FIFA/comments/aa0km3/psa_how_to_see_how_many_unassigned_items_youve_got/

Yeah sure , but for now using this method to get the count https://www.reddit.com/r/FIFA/comments/aa0km3/psa_how_to_see_how_many_unassigned_items_youve_got/


[Refactor] WorkspaceNewRoomPage Form + Fix From nested children from class component

Details

Refactor the Workspace New Room Page form  to use Form.js.
Fix Form.js to detect nested children inside custom class component.

Fixed Issues

https://github.com/Expensify/App/issues/13524
PROPOSAL: https://github.com/Expensify/App/issues/13524#issuecomment-1352548981
Tests / QA Steps

Test 1

Choose New Room from the create menu
Fill up the form
Click Create Room
Room Created successfully

Test 2

Choose New Room from the create menu
Skip the Room Name Input
Select Workspace
An Error Appears : Please enter a room name
Click on fix the errors
Room Name Input is focused
Enter this value : Test Room (Any value with Uppercase and space)
Room Name Input's value changed to lowercase and the space   is replaced with underscore _

[x] UI looks as it did before the refactor
[x] Values can be added and edited
[x] Errors are highlighted correctly (input border)
[x] Error messages show up correctly
[ ] Draft values are saved properly
[x] Form alerts are displayed correctly
[x] Clicking the fix the errors link focuses the first input with error
[x] No duplicate submission of the form occurs (when it's already submitting)
[x] Verify that no errors appear in the JS console

Offline tests

Choose New Room from the create menu
Fill up the form
Click Create Room
Verified that the form can be submitted and the button is enabled

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

WorkspaceNewRoomPage Page - Refactored
https://user-images.githubusercontent.com/36869046/208528274-1dfa2514-1943-4dc4-90f9-bcbb01baf974.mov

ReportSettingsPage - Not Refactored
https://user-images.githubusercontent.com/36869046/208529478-7f1d1a62-3d36-4ff1-8fea-8479e7c5564d.mov

Mobile Web - Chrome

Mobile Web - Safari

Desktop
https://user-images.githubusercontent.com/36869046/208532244-8bfa86da-17bf-4eb5-90af-3e6de90e9234.mov

iOS
https://user-images.githubusercontent.com/36869046/208538124-6442eb93-4e5b-4e03-9175-1a7ec287894b.mp4

Android
https://user-images.githubusercontent.com/36869046/208544884-9a152366-3dfd-45ff-b9b7-9aff9809e013.mov

@Gonals Looks like this pr should be assigned to @puneetlath and @mollfpr

@fedirjh We should add the test description. For the example here #12766

@mollfpr thank you , tests description added

Test online and offline with the HT account working well! Just need to resolve a comment https://github.com/Expensify/App/pull/13713#discussion_r1053594878

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @puneetlath in version: 1.2.43-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @chiragsalian in version: 1.2.43-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Changing plugin logic

Plugins now register against the SolariBoard and get given a screen that they can manipulate as required. The SolariBoard will still handle the rendering of the screens.
Currently only supports the single screen and the SolariPlugin code itself is still quite crappy.
Build status will now have a single line per repository instead of a stream of failures/successes.

Oh. This also has Greg's changes for not rendering when nothing is happening.


user table issue

cursor.execute(sql_command,(user['uname']))
sqlite3.OperationalError: no such table: users
hey I m running into this issue in the register.py file,can u help me

okay, This could be due to no users table in users.db. Can you verify this.


Check select! bug in async

I suspect that this is still a bug as the select can complete on either branch of the select in a non-deterministic fashion. The right way to handle (I think) is to not fail when the sender fails to send. The send failing can indicator that the receiver is closed. See https://docs.rs/tokio/latest/tokio/sync/mpsc/struct.Sender.html
I think there's probably a second bug with this in how cancelations are handled https://docs.rs/tokio/latest/tokio/sync/mpsc/struct.Sender.html#cancel-safety
Originally posted by @joshka in https://github.com/ratatui-org/templates/pull/48#pullrequestreview-1913139384

Is this still an issue?

This is mostly a prompt to check whether this is a bug at some point. I haven't looked into it more than superficially.


Data scraping unable to complete in 30.0s

My code:
import asyncio
from tiktokapipy.async_api import AsyncTikTokAPI

async def do_something():
    async with AsyncTikTokAPI() as api:
        video = await api.user("huydao")
        print(video)

asyncio.run(do_something())

but I have error:

Anyone can fix it?

Please provide some more details such as where you're located and what version of the library you're using. There's a known issue with the user function that makes it not work in certain regions without a proxy.

Please provide some more details such as where you're located and what version of the library you're using. There's a known issue with the user function that makes it not work in certain regions without a proxy.

I am located in Viet Nam, I used the lasted version - 0.2.4. How I apply proxy to fix this problem?

Take a look at the documentation for the TikTokAPI class and for Playwright's Browser::launch() function. You can pass in browser launch args as kwargs for the TikTokAPI class. This includes proxy information.

I tried TikTokApi and TikTokPy for scraping a user's videos, and both of them ended up in an issue that would allegedly be solved by using a proxy. Since both libraries are based on playwright, what is a proxy service that works well with playwright?
I own one dedicated socks proxy with auth, but playwright fails on socks proxies with auth.

@LoliHaxxer Have you been able to figure out a proxy service that works well with playwright?

I tried TikTokApi and TikTokPy for scraping a user's videos, and both of them ended up in an issue that would allegedly be solved by using a proxy. Since both libraries are based on playwright, what is a proxy service that works well with playwright? I own one dedicated socks proxy with auth, but playwright fails on socks proxies with auth.

No I haven't, I just proceeded to scrape myself with Selenium

No I haven't, I just proceeded to scrape myself with Selenium
@LoliHaxxer
Do you mind sharing how you go about doing that? I keep getting a CAPTCHA on the first request. If you don't mind I can drop a medium to contact me. Thanks.


Backup using a PDF.

-Personal device>QR is not coming up while resharing. only the loader is loading.
-Share now buttong not responding quickly.
-PDF is not getting attached to mail on android device.
-Personal copy >"cofirm share" is not working >after scanning the QR it again shows the "Backup recovery key " module.

-Verified these issues on dev app v1.7.5(298)


Data is not being updated on the fly

For example a simple fetch after an initial init doesn't work.  If a Vue ref is used we cannot modify the binding, it just doesn't take, I've tried both composition and vue 3 setup as in your guide, so what if we don't have the data on time of render?
Thanks for any input!

Apparently this was the fix:
:key="componentKey"
incrementing the componentKey when data changes worked

Also the base data set needs to be at least 3 items, if only two:
vue3-select-option-search.js:115 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'title')
at Proxy. (vue3-select-option-search.js:115:22)
at renderComponentRoot (runtime-core.esm-bundler.js:816:16)
at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5701:46)
at ReactiveEffect.run (reactivity.esm-bundler.js:178:19)
at instance.update (runtime-core.esm-bundler.js:5814:51)
at setupRenderEffect (runtime-core.esm-bundler.js:5822:5)
at mountComponent (runtime-core.esm-bundler.js:5612:5)
at processComponent (runtime-core.esm-bundler.js:5565:9)
at patch (runtime-core.esm-bundler.js:5040:11)
at mountChildren (runtime-core.esm-bundler.js:5284:7)


fix: Change Gatsby GH URL from master to latest

Fixes #9

@MichaelCurrin good catch, thank you so much for your time and efforts !

@MichaelCurrin good catch, thank you so much for your time and efforts !

You're welcome. Thanks for quick feedback and merging.

You're welcome. Thanks for quick feedback and merging.