Boot fail: could not load 'app.dep': command failed (126)

Hello there,
I'm trying to use you container on a asustor AS3102T v2, i'm able to run other containers fine, also i have tried to run on a ubuntu VM and it did work fine... but every time i try to run it on the NAS it fails to start... I don't have a lot to go on.

I have tried different versions... the error is always the same... I have also changed the debug to 1, the info is the same... am I missing something?

How did you created the container, or what are the container settings ?

I used:
docker run -d --name=jdownloader2 \ -p 3129:3129 \ -p 5800:5800 \ -p 5900:5900 \ -e TZ=Europe/Lisbon \ -v /volume1/Docker/jdownload2/config:/config:rw \ -v /volume1/Docker/jdownload2/output:/output:rw \ --restart always \ jlesage/jdownloader-2

Looks like the content of the container is wrong.  app.dep is a file from the Docker image that doesn't have execute permission.  In you case, the file seems that have it...
Did you try the delete the container and image and re-create them ?

Yap... i tried also a couple of params from the documentation... changed some values but the result is the same... as i said on an ubuntu VM it woked "out of the box"...

How do you create the container on the Asustor ?

It has docker running on it... so i just use the cmd I posted above... I have other containers running fine on the Asustor... to do a GUI management I use portainer... thats it

Ok, could you provide the output of:
docker inspect <container name>

[     {         "Id": "c44d03cdef95203563e9a6a348e0367bfc99bb4b678f2defd9f5697dcdd22820",         "Created": "2023-01-06T21:54:09.230849537Z",         "Path": "/init",         "Args": [],         "State": {             "Status": "restarting",             "Running": true,             "Paused": false,             "Restarting": true,             "OOMKilled": false,             "Dead": false,             "Pid": 0,             "ExitCode": 1,             "Error": "",             "StartedAt": "2023-01-06T21:54:42.438177425Z",             "FinishedAt": "2023-01-06T21:54:43.180534637Z"         },         "Image": "sha256:717805b0e624b5e8db46749770984db77e52f175a34903f387f6fed3915f55f0",         "ResolvConfPath"<EMAIL_ADDRESS>        "HostnamePath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/c44d03cdef95203563e9a6a348e0367bfc99bb4b678f2defd9f5697dcdd22820/hostname",         "HostsPath": "/volume1/.@plugins/AppCentral/docker-ce/docker_lib/containers/c44d03cdef95203563e9a6a348e0367bfc99bb4b678f2defd9f5697dcdd22820/hosts",         "LogPath"<EMAIL_ADDRESS>        "Name": "/jdownloader2",         "RestartCount": 5,         "Driver": "btrfs",         "Platform": "linux",         "MountLabel": "",         "ProcessLabel": "",         "AppArmorProfile": "",         "ExecIDs": null,         "HostConfig": {             "Binds": [                 "/volume1/Docker/jdownload2/config:/config:rw",                 "/volume1/Docker/jdownload2/output:/output:rw"             ],             "ContainerIDFile": "",             "LogConfig": {                 "Type": "json-file",                 "Config": {}             },             "NetworkMode": "default",             "PortBindings": {                 "3129/tcp": [                     {                         "HostIp": "",                         "HostPort": "3129"                     }                 ],                 "5800/tcp": [                     {                         "HostIp": "",                         "HostPort": "5800"                     }                 ],                 "5900/tcp": [                     {                         "HostIp": "",                         "HostPort": "5900"                     }                 ]             },             "RestartPolicy": {                 "Name": "always",                 "MaximumRetryCount": 0             },             "AutoRemove": false,             "VolumeDriver": "",             "VolumesFrom": null,             "CapAdd": null,             "CapDrop": null,             "CgroupnsMode": "host",             "Dns": [],             "DnsOptions": [],             "DnsSearch": [],             "ExtraHosts": null,             "GroupAdd": null,             "IpcMode": "private",             "Cgroup": "",             "Links": null,             "OomScoreAdj": 0,             "PidMode": "",             "Privileged": false,             "PublishAllPorts": false,             "ReadonlyRootfs": false,             "SecurityOpt": null,             "UTSMode": "",             "UsernsMode": "",             "ShmSize": 67108864,             "Runtime": "runc",             "ConsoleSize": [                 0,                 0             ],             "Isolation": "",             "CpuShares": 0,             "Memory": 0,             "NanoCpus": 0,             "CgroupParent": "",             "BlkioWeight": 0,             "BlkioWeightDevice": [],             "BlkioDeviceReadBps": null,             "BlkioDeviceWriteBps": null,             "BlkioDeviceReadIOps": null,             "BlkioDeviceWriteIOps": null,             "CpuPeriod": 0,             "CpuQuota": 0,             "CpuRealtimePeriod": 0,             "CpuRealtimeRuntime": 0,             "CpusetCpus": "",             "CpusetMems": "",             "Devices": [],             "DeviceCgroupRules": null,             "DeviceRequests": null,             "KernelMemory": 0,             "KernelMemoryTCP": 0,             "MemoryReservation": 0,             "MemorySwap": 0,             "MemorySwappiness": null,             "OomKillDisable": false,             "PidsLimit": null,             "Ulimits": null,             "CpuCount": 0,             "CpuPercent": 0,             "IOMaximumIOps": 0,             "IOMaximumBandwidth": 0,             "MaskedPaths": [                 "/proc/asound",                 "/proc/acpi",                 "/proc/kcore",                 "/proc/keys",                 "/proc/latency_stats",                 "/proc/timer_list",                 "/proc/timer_stats",                 "/proc/sched_debug",                 "/proc/scsi",                 "/sys/firmware"             ],             "ReadonlyPaths": [                 "/proc/bus",                 "/proc/fs",                 "/proc/irq",                 "/proc/sys",                 "/proc/sysrq-trigger"             ]         },         "GraphDriver": {             "Data": null,             "Name": "btrfs"         },         "Mounts": [             {                 "Type": "bind",                 "Source": "/volume1/Docker/jdownload2/config",                 "Destination": "/config",                 "Mode": "rw",                 "RW": true,                 "Propagation": "rprivate"             },             {                 "Type": "bind",                 "Source": "/volume1/Docker/jdownload2/output",                 "Destination": "/output",                 "Mode": "rw",                 "RW": true,                 "Propagation": "rprivate"             }         ],         "Config": {             "Hostname": "c44d03cdef95",             "Domainname": "",             "User": "",             "AttachStdin": false,             "AttachStdout": false,             "AttachStderr": false,             "ExposedPorts": {                 "3129/tcp": {},                 "5800/tcp": {},                 "5900/tcp": {}             },             "Tty": false,             "OpenStdin": false,             "StdinOnce": false,             "Env": [                 "PUID=1000",                 "PGID=100",                 "GROUP_ID=100",                 "TZ=Europe/Lisbon",                 "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/base/sbin:/opt/base/bin",                 "ENV=/root/.docker_rc",                 "USER_ID=1000",                 "SUP_GROUP_IDS=",                 "UMASK=0022",                 "LANG=en_US.UTF-8",                 "KEEP_APP_RUNNING=0",                 "APP_NICENESS=0",                 "INSTALL_PACKAGES=",                 "CONTAINER_DEBUG=0",                 "DISPLAY_WIDTH=1920",                 "DISPLAY_HEIGHT=1080",                 "DARK_MODE=0",                 "SECURE_CONNECTION=0",                 "SECURE_CONNECTION_VNC_METHOD=SSL",                 "SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60",                 "WEB_LISTENING_PORT=5800",                 "VNC_LISTENING_PORT=5900",                 "VNC_PASSWORD=",                 "ENABLE_CJK_FONT=0"             ],             "Cmd": [                 "/init"             ],             "Image": "jlesage/jdownloader-2",             "Volumes": {                 "/config": {},                 "/output": {}             },             "WorkingDir": "/tmp",             "Entrypoint": null,             "OnBuild": null,             "Labels": {                 "org.label-schema.description": "Docker container for JDownloader 2",                 "org.label-schema.name": "jdownloader-2",                 "org.label-schema.schema-version": "1.0",                 "org.label-schema.vcs-url": "https://github.com/jlesage/docker-jdownloader-2",                 "org.label-schema.version": "22.12.1"             }         },         "NetworkSettings": {             "Bridge": "",             "SandboxID": "61676b47c90dacc2e8a20722ea00ba34e8c4335ca4979f264e2a81060ea16bcc",             "HairpinMode": false,             "LinkLocalIPv6Address": "",             "LinkLocalIPv6PrefixLen": 0,             "Ports": {},             "SandboxKey": "/var/run/docker/netns/61676b47c90d",             "SecondaryIPAddresses": null,             "SecondaryIPv6Addresses": null,             "EndpointID": "",             "Gateway": "",             "GlobalIPv6Address": "",             "GlobalIPv6PrefixLen": 0,             "IPAddress": "",             "IPPrefixLen": 0,             "IPv6Gateway": "",             "MacAddress": "",             "Networks": {                 "bridge": {                     "IPAMConfig": null,                     "Links": null,                     "Aliases": null,                     "NetworkID": "2b53d3131b3299bd11a0b4342a3d773faaaaa114e962f429d3b626c4b0a153e3",                     "EndpointID": "",                     "Gateway": "",                     "IPAddress": "",                     "IPPrefixLen": 0,                     "IPv6Gateway": "",                     "GlobalIPv6Address": "",                     "GlobalIPv6PrefixLen": 0,                     "MacAddress": "",                     "DriverOpts": null                 }             }         }
Sure, thanks for your help!

Could you provide the output of:
docker run --rm jlesage/jdownloader-2 ls -l /etc/services.d/default

Could you do another test by running the following commands ?
echo '#!/bin/sh' > /tmp/test.sh
echo 'ls -l /etc/services.d/*/' >> /tmp/test.sh
chmod +x /tmp/test.sh

docker run --rm -v /tmp/test.sh:/etc/cont-init.d/88-test.sh jlesage/jdownloader-2

Please then share the output.

log.txt
I have attached the log...
Thanks for the help

Can you try the latest image to see if it's better ?

Issue still there... tried your latest commands... the log result is attached.
Thanks for your effort!
log.txt


cmd: do not use non-constant formatting strings in printf-like calls

Do not use non-constant formatting strings in calls to printf-like functions in src/cmd. These fail the new printf vet check (#60529).
cc @adonovan

Related Issues and Documentation

cmd/vet: report printf calls with non-const format and no args #60529 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

The required work is a subset of the work for #68796. Closing this as a duplicate.


Exploration: Enter PIN code from email

Description
Design exploration for replacing the email link verification with a PIN code entry.
User Story
As a user, I want to securely authenticate my account using a PIN code sent to my email, so that I can easily access my account on any device and avoid a fragmented user experience.
Acceptance Criteria

A 6-digit PIN code is sent to the user's email immediately after they enter their email address.
The PIN code expires and resets 5 minutes after being sent.
Users can enter the PIN on any device to complete authentication.
Upon successful PIN entry, users are directed to their desired action (e.g., sign in, account creation).
An error message is displayed for an incorrect or expired PIN, with an option to resend a new PIN.

Should we consider using an alpha-numeric PIN code instead for additional security?


Support for multiple Ensime projects in a single atom instance?

I'm hoping to be able to support multiple projects in a single atom window.
Looking at the code, this would require storing a set of clients, instead of the one client that is currently stored (simple). Small changes to util.coffee, ensime-startup.coffee and ensime.coffee allow the client to be selected by the project containing the current buffer rather than the single global client.  Since client.coffee is already a class we can instantiate multiple clients.
The issue I'm running into (other than not knowing the atom api or ever having written/read coffee script before today) is whether or not I can attach a second client to the same ensime-server instance or if I need to start a second instance etc.
Second issue is modifying the code to deal with multiple ensime/scala versions would still be a bit of a hassle (at least for me right now).
I was thinking of tying this feature into Project Manager since that stores all the paths rather nicely and then the start command could be something like Ensime: Start <project>
Any thoughts? Did I miss anything fundamental?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23086233-support-for-multiple-ensime-projects-in-a-single-atom-instance?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github).

I think it's definitely doable. I have run many ensimes (client + server) in Atom, but I have always had them in different windows.
Thoughts:

One server per project, that's how it is.
Need file area for every project portfile and .ensime_cache (logs and stuff that server needs)
Might need a bit of view-logic added. Everything is a bit crude right now. I mean, you will need to listen to which text-editor is focused and swap everything if you change to a file of different project (right now only the panel with errors, but there might be more)
Don't think multiple ensime/scala-versions should be an issue. Scala-version is from .ensime anyways, and ensime server version is just a setting now. Could be overriding in a project setting if you find a way. But I don't think you really want to do that. You would typically always wanna run latest and greatest ensime server version.

Actually, looking at the code I don't think the panel is going to prove to be too difficult.  Its just a single instance after all and every time a new event occurs all the data is rewritten.

Yeah, that's the thing - it's really simple now but this what I will start working on pretty soon. I want tabs for "all errors"/"errors on current buffer" + log/messages. So stuff got to stay somewhere, but probably could just have two panels and switch between them when switching project.
And then markers in the text buffers + gutters, what happens if you have two projects and do atom.open? I mean from the error messages, if you click an error that file opens, but it need to be attached to the correct project, right? I'm not really sure how multiple projects works I realize. You need to know which project an editor belongs to to do the right thing when events occur on that editor.
I definitely think it's doable but not trivial. But please pursue!

A short term (inefficient fix) could use something like atom.getCurrentWindow().getRepresentedFilename() to get the calling project name and then define ensime:reset to stop+start the server if the project is different from the current project.  The reset would be called manually, but it allows fast-ish switching.  To make it more reasonable, we should store the time of the last ensime:update so we can limit the number of updates.

@mrmechko Is this still something you're craving? I'm thinking it would be nice to abstract correctly before we have too much code to maintain. I haven't even understood how I can open two projects in the same window, can you walk me through?

Ah, ok "open project folder". Never done that until now :)

Yeah, ok, I reckon we should fix this before stuff get's messier. So the offending line is here:
https://github.com/hedefalk/ensime-atom/blob/master/lib/utils.coffee#L47
I just want to point out that I didn't do that [0] when I started out - there was no abstraction for multiple projects at the time. It was later that Atom started supporting multiple projects and then I just had to do that to that to make the plugin compliant with latest version of Atom. I just didn't have the time to look any deeper at the time. Excuses, excuses :)
I think we only need an API call "projectOfCurrentTextEditor" kindof. Can't find it though.
There's:
https://atom.io/docs/api/v1.1.0/Project#instance-onDidChangePaths
Which we'll use as keys in a map against possible ensime clients I guess.
So we can write our own O(n) on # of folders when finding ensime client of a file. Probably totally fine.
I don't know what the correct starting point is: When doing ensime:start, should we use current active text editor or always ask for which folder to run it?

We need to listen for active text editor to change out the bottom status bar with errors and stuff for the correct ensime client. Can't find any good method. There's:
https://atom.io/docs/api/v1.1.0/Workspace#instance-onDidChangeActivePane
which probably is usable but I would like something like:
https://atom.io/docs/api/v1.1.0/Workspace#instance-getActiveTextEditor
but as events.

https://discuss.atom.io/t/observe-currentlyactivetexteditor/22471

Ok, so https://atom.io/docs/api/v1.1.0/Workspace#instance-onDidStopChangingActivePaneItem seems to do the trick.

Ok, so just catch up to discussion in the beginning:
I'm going to work on trying to support multiple Ensime project folders in ONE atom window/project. Still gonna use .ensime_cache in the same folder as the .ensime per project and so forth. But just not have globals for client socket and stuff. And be able to switch out ui depending on active buffer.

@hedefalk FYI, Sublime does this by having a cached relationship between tab and project data.  So that all of the windows in the same proiject refer to an object containing the connection etc.

@hedefalk sorry for the late response.  In the context of your last post, we're still starting an ensime server for each project, right?

@mrmechko Depends on what you mean by project. One .ensime and one server per ensime project, that's just how ensime works. This is just to allow multiple ensime projects within one Atom window (which is also called project in Atom). This was what you were looking for, right?

@rorygraves Yeah, cool. I think we'll be able to do something similar. At the init of each TextEditor pane we might need to do a lookup of O(#open ensime projects) to find which project it belongs to, but then we can cache it. Doesn't seem to be any "getProjectOfFile" in Atom so need to do our own substring comparison…

@rorygraves Question: How do you handle commands and stuff? Is everything in the context of the currently active text buffer? I mean "typecheck all" and stuff like that?

@rorygraves In some cases you might not even have an open text buffer… Hm.

@rorygraves I'm trying out ensime-sublime for reference, but I can't seem to understand if you really have support for multiple ensime projects in one window? I use "Add folder to project" in ST3 after starting Ensime on one project, I open up a file from the second project and the menus are in "started state" still. It seems to me you're in the same boat as ensime-atom or do I misunderstand?

So in the screenshot above I have already started Ensime when I had only ensime-test-project open, and then I added kostbevakningen and tried to fire up another one, but I can't seem to understand how?

Fixed since 0.32


Update avatarlegends.html (Folder : AvatarLegendsMagpie)

More translations for Universal Technique

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.

Hey again @akibi90: same story as in your Root PR: I'll need you to change the line endings on this file before we can continue with this review.

new pull request #12416


[2.x] Refactor the internals of the new table of contents generator

Make some refactors to the internals of the new generator added in https://github.com/hydephp/develop/pull/2045
It does add about 100 lines of code (doubling the class), but given how much more readable the class is now I think that's acceptable. The public API still remains the same as it's just internal refactors.
Also updates some docs.

ChatGPT 4o Code Review
The decision to merge the PR depends on the trade-offs between code readability, maintainability, and complexity:
Pros:

Improved Readability: Extracting helper methods makes each part of the logic more focused and easier to understand in isolation.
Reusability: Helper methods can potentially be reused in other contexts.
Testability: Smaller methods are often easier to unit test.
Separation of Concerns: Clearer boundaries between different parts of the functionality (e.g., parsing ATX vs. Setext headers).

Cons:

Increased Code Size: Doubling the code length could make navigation more cumbersome.
Complex Method Dependencies: Breaking logic into smaller parts introduces additional method calls and dependencies, which can make debugging harder.
Context Switching: When following the flow of execution, developers might need to jump between methods more often, which can slow down comprehension.

Evaluating This Case:

The extraction is done well, with descriptive method names and clear separation of logic.
The added lines appear to contribute meaningfully to making the code modular and easier to follow.
If the original class is expected to evolve further, having this structure will likely pay off by simplifying future modifications.
If the project prioritizes strict simplicity and the original code was working fine, the refactor might not justify the added complexity.

Final Verdict:
If the project values maintainability and readability over minimalism and the refactor aligns with the project's coding standards, merging the PR is justified. On the other hand, if simplicity and concise code are critical in your project, consider leaving the class as it was or only making partial refactors.


Cleanup 34

Fixes puppetlabs/puppetlabs-dhcp#34

Merging my own since it's just cleaning up commit history for a PR.


'nil' signal handler crashes the app

(I'm using lgi 0.9.1, the package provided with Ubuntu 16.10. Maybe the bug got fixed since then.)
When you install nil as a signal handler, the app crashes when it gets invoked. Here's an example:
#! /usr/bin/env lua

local lgi = require 'lgi'
local Gtk = lgi.Gtk

local w = Gtk.Window {
  title = "If you click the button, I'll crash",
  Gtk.Button { label = "click me!", id = "btn" },
  on_destroy = Gtk.main_quit,
}

local btn = w.child.btn
btn.on_clicked = nil    -- crash when clicked!

w:show_all()
Gtk.main()

(The bug is not specific to GtkButton, nor to on_clicked.)
BTW, I know there's no sense in assigning nil to a signal, as assignment adds a handler, not removes the previous one installed. I triggered the bug when I misspelled a function name. This kind of bugs (misspellings) can be hard to find (luacheck and strict.lua cannot always help).

The crash is because GObject ends up with a NULL pointer for a callback. A possible fix might be the following (why does the code already have a suitable if to check if no target is provided? That seems fishy. Is that behaviour needed for something?):
diff --git a/lgi/override/GObject-Closure.lua b/lgi/override/GObject-Closure.lua
index 577f64f..02c532b 100644
--- a/lgi/override/GObject-Closure.lua
+++ b/lgi/override/GObject-Closure.lua
@@ -288,6 +288,8 @@ function Closure:_new(target, callback_info)
         end
       end
       core.marshal.closure_set_marshal(closure, marshaller)
+   else
+      error("Trying to construct Closure for nil")
    end
    Closure.ref(closure)
    Closure.sink(closure)

No idea if the above is a good idea or not.


Exclude based on osfamily rather than rewriting the supported os hash

I'm trying to apply the following conditional rather than having to rewrite the supported block:
but for some reason this doesn't seem to be working as Ubuntu is still trying to run, I'm sure I'm doing something wrong:
metadata.json
  "operatingsystem_support": [
    {
      "operatingsystem": "CentOS",
      "operatingsystemrelease": [
        "5",
        "6",
        "7"
      ]
    },
    {
      "operatingsystem": "Ubuntu",
      "operatingsystemrelease": [
        "12.04",
        "14.04",
        "16.04"
      ]
    }
  ],

require 'spec_helper'
describe 'profile_base::el' do
  context 'supported operating systems' do
    on_supported_os.each do |os, facts|
      context "on #{os}" do
        let(:facts) do
          facts.merge({
            puppetversion: Puppet.version,
            sudoversion: '1.7.10p9'
          })
        end
        if (:osfamily != "Debian") then
          context "profile_base::el class without any parameters" do
            %w(profile_base::el profile_base::linux
               profile_base::nix).each do |puppet_class|
              it { should contain_class(puppet_class) }
              it { should compile.with_all_deps }
            end
          end
        end
      end
    end
  end
end

Closing as I figured out my syntax issue:
         if ((facts[:osfamily] != "Debian") && (facts[:osfamily] != "Solaris")) then


Streaming returning nonsense

@signmotion When using streaming the answer is weird -
SItara was had a always cool been autumn day passionate about, the soccer ever sun since she shining brightly in the sky as the two rival teams took was a little girl. She used to accompany her to father the field. The to the soccer matches excitement he in played the with air his was palp friends inable as their local the crowd community. erupted into cheers From that moment on, and applause. she knew This was the that soccer was highly anticipated her soccer calling match and between she the Red began training Lions rigor andously the to Blue become Tigers the, best two player powerhouse she teams could in the be. local league.TheAs she grew older Red, Lions,.
How to fix this?

I guess it is your job to figure out how you enhance and refine the API result since I don't have any access on that.
feel free tough to open issues if they are related to the package functionality.

It was my fault because I set the n value to something bigger than 1. Setting it to n=1 fixed the issue.


Copy .ruby-version file to build directory

This is a 🐞 bug fix.

[ ] I've added tests (if it's a bug, feature or enhancement)
[ ] I've adjusted the documentation (if it's a feature or enhancement)
[x] The test suite passes (run bundle exec rspec to verify this)

I did not find any tests related to the CodeBuilder class, however, happy to implement if you can point me to it.
Summary
Copy .ruby-version file to build directory to make sure to use the same ruby version as in the project.
Fix #313
Context
See #313 for details. We need to use the same ruby version in build directory /tmp as in the project directory.
Version Changes
None

Cheers 👍


Fix go test timeout flag in e2e tests README

In ./test/e2e/README.md there was a minor error in the go test timeout flag. I believe the intended timeout is 75 minutes.

/skip-all


Docs: Redux [FAQ: Organizing State] remove You Might Not Need Redux

Because this was written at 2016, the content seems like counter part for over engineering with verbosity Boilerplate.
But we are living post Redux-Toolkit,「You Might Not Need Redux」is not tell us the Author's original meant by context lost.

You might not need this blog post.
Thanks!

I... actually would prefer to leave that link in, tbh.
I know it's old, but Dan did write it, and the arguments he made about "tradeoffs" and the use cases he described are still meaningful.

@markerikson Yeah, I know that feeling. I thought it was great post at the 2017.

I know it's old, but Dan did write it, and the arguments he made about "tradeoffs" and the use cases he described are still meaningful.

I agree with you the post fundamental still correct think.
But why we could have such as opinion? Because we are veteran of Redux(actually your level is god of Redux) so,
I think this is because we can extract and evaluate the essential purpose of this article, taking into account the differences between then and now.
But it's not friendly for new leaner.
original Tradeoff


Caching font rendering?

I've noticed that if you render too much text (1000+ lines) on the screen, the framerate goes down a lot. Is there a way of caching or improving font rendering?

This is already done. It is almost impossible for 1000 lines to appear on the screen. I think you could use "line height" to draw only a portion of the text (which should appear on the screen)

It's not already done, nanovg appears to create a new atlas every text draw call.

If you see new atlas being created for every text call, then that is a bug.
For very long texts the bottleneck can be line breaking. I recommend to break the text into lines, cull the ones that are not visible. Here's example how break long text into lines:
https://github.com/memononen/nanovg/blob/master/example/demo.c#L882


Pull mock-dns-server out into separate package

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (9ca34c7) to head (0b431ed).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##              main       #53    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files            6         5     -1
  Lines         1324      1177   -147
==========================================
- Hits          1324      1177   -147

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


'data' parameter required to be a plain object

This check is annoying, because it obliges you to pass a plain Object as 'data'.
It is ok if you got this objects directly from a Mongo collection. However, if you use an object-oriented scheme, what you got is an Object with prototypes, which will not pass the check.
It is the case, for example, if you use meteor-collection-helpers.
Workaround (painful):
{{#basicForm schema=schema data=th_dataAsPlainObject action=action}}
    ...
{{/basicForm}}

Template.xxxxx.helpers({
    th_dataAsPlainObject: function() {
        return _.clone(this.data);
    }
});

Ah--I had no intention of enforcing that restriction on objects.
I wouldn't want to make it Match.Any because I'm expecting the data to be in object-form:
https://github.com/meteortemplates/forms/blob/master/templates:forms.coffee#L243
Perhaps this would work better?
Match.Where (x) ->
  return _.isObject(x)

The Underscore method seems to not be restricted to plain objects. http://underscorejs.org/#isObject
Will test later.

Will publish this with the next update.

Sounds great!

Update 1.7 has been published, check the changelog to see the latest.

Works like a charm, thanks!


test scenario who checks if token account is displayed in Eth account

📝 Description
This pr add a UI test scenario who allow to check if a token account is displayed in ETH account.
❓ Context

No impact

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/generate-screenshots

/generate-screenshots

/generate-screenshots


[NEMO-434] (WIP) Logical DAG modification for Dynamic sampling of task metrics during the execution of a stage

JIRA: NEMO-434: Logical DAG modification for Dynamic sampling of task metrics during the execution of a stage
Major changes:

Added new mechanism for launching runtime pass

For runtime passes which need to gather information by itself, use MessageGeneratorVertex and MessageAggregatorVertex
For runtime passes which need Metric information, use SignalVertex

Added SignalVertex and SignalTransform to launch runtime pass without collecting any runtime information
New Compile time pass for DTS which changes DAG
New TaskSizeSplitterVertex to distinguish and manage sampled data and the rest in vertex level(extended from LoopVertex)
Added inserting TaskSizeSplitterVertex method in IRDAG

Minor changes to note:

Changed the name of TriggerVertex to MessageGeneratorVertex. Since the combination of TriggerVertex and MAV triggers runtime pass, not trigger vertex alone, the name 'Trigger' can be misleading.
erased duplicate assignments in EmptyComponents class
new methods in LoopVertex

Tests for the changes:

IRDAGTest and SkewCompositePassTest has been modified by the class name refactoring

Other comments:

SamplingTaskSizingPass.java contains methods that are not supported in Java8. Therefore, this PR needs to be merged after #291 is merged in master

Closes #292

Thanks for the PR! I'll take a look after @wonook

Thanks @polarcoke2 for adding the tests! LGTM


Error: P4Runtime RPC error (INTERNAL): 'bf_pal_device_add(dev_id, &device_profile)' failed with error message: Unexpected error.

Hey, guys.
I wrote a p4 program and p4c-dpdk compiled it successfully. But I couldn't send binary pipeline to the dataplane.
The p4_driver.log shows as follow. It seems that there is a problem with my pipeline instructions configuration. But where can I find the "pipeline instructions configuration"?
2023-11-30 08:52:11.755315 INFO  BF_DVM bf_device_warm_init_begin:218 Entering WARM_INIT_BEGIN for device 0 with warm_init_mode 1
2023-11-30 08:52:11.755382 INFO  BF_DVM bf_device_warm_init_begin:255 Exiting WARM_INIT_BEGIN for device 0
2023-11-30 08:52:11.757741 INFO  BF_DVM bf_device_add dev id 0, is_sw_model 1
2023-11-30 08:52:11.757776 INFO  BF_LLD Entering :lld_dev_add

2023-11-30 08:52:11.757789 INFO  BF_LLD Exiting :lld_dev_add

2023-11-30 08:52:11.757799 INFO  BF_PAL Entering fixed_function_dev_add
2023-11-30 08:52:11.757809 INFO  BF_PAL Exiting fixed_function_dev_add
2023-11-30 08:52:11.757818 INFO  BF_PORT Entering port_mgr_dev_add
2023-11-30 08:52:11.757828 INFO  BF_PORT Enter port_mgr_config_import
2023-11-30 08:52:11.757837 INFO  BF_PORT port_mgr_config_import: device 0, file (null)
2023-11-30 08:52:11.757847 INFO  BF_PORT Exit port_mgr_config_import
2023-11-30 08:52:11.774894 **ERROR** BF_PIPE dal_enable_pipeline line:101 Error -22 at line 0: Pipeline instructions configuration error.

2023-11-30 08:52:11.775125 **ERROR** BF_PIPE Failed to Build Pipeline pipe
2023-11-30 08:52:11.775202 **ERROR** BF_DVM Device add handling failed for dev 0, sts Unexpected error (15), Client pipe-mgr
2023-11-30 08:52:11.775283 **ERROR** BF_DVM Device add failed for dev 0, sts Unexpected error (15)
2023-11-30 08:52:11.775414 INFO  BF_PORT Entering port_mgr_dev_remove
2023-11-30 08:52:11.775515 INFO  BF_PAL STUB fixed_function_dev_remove
2023-11-30 08:52:11.775539 INFO  BF_LLD Entering dummy STUB:lld_dev_remove

2023-11-30 08:52:11.775551 INFO  BF_LLD Exiting dummy STUB:lld_dev_remove

And the infrap4d.ERROR shows as follow.
E20231130 08:58:15.065459  8768 dpdk_sde_target.cc:170] StratumErrorSpace::ERR_INTERNAL: 'bf_pal_device_add(dev_id, &device_profile)' failed with error message: Unexpected error.
E20231130 08:58:15.065549  8768 tdi_node.cc:145] Return Error: tdi_sde_interface_->AddDevice(device_id_, tdi_config_) failed with StratumErrorSpace::ERR_INTERNAL: 'bf_pal_device_add(dev_id, &device_profile)' failed with error message: Unexpected error.
E20231130 08:58:15.065577  8768 dpdk_switch.cc:71] Return Error: tdi_node->PushForwardingPipelineConfig(config) failed with StratumErrorSpace::ERR_INTERNAL: 'bf_pal_device_add(dev_id, &device_profile)' failed with error message: Unexpected error.
E20231130 08:58:15.065608  8768 error_buffer.cc:30] (p4_service.cc:468): Failed to set forwarding pipeline config for node 1: 'bf_pal_device_add(dev_id, &device_profile)' failed with error message: Unexpected error.

Any ideas? Thank you.

This is apparently due to a restriction in DPDK that the number of ports must be power of 2. When this condition is not met, a generic error is returned. There was some talk of removing this restriction, but I don't know if this has been done (or if, alternatively, the code has been modified to check for this condition and return an intelligible error message).
Our resources are focused entirely on ES2K support, which means that DPDK is not being updated. We might not have pulled in the fix even if it is available.


[Feature Request] Rel canonical tags

One common SEO concern for anyone syndicating their content is that their own site gets the credited for their articles (instead of Medium, Dev.to, etc)
The common pattern on those sites is to take this from the front matter. I.e., canonical_url: https://example.com/my-article in the front matter will result in the following being in the head of the published article:
<link rel="canonical" href="https://example.com/my-article/" />

Hi there 👋
Thanks for raising this.
I'll try to implement something as soon as I've got some free time otherwise I wouldn't be opposed to a PR.

Great! Sorry about not writing one. I would if I were more familiar with
VuePress (and may yet at some point!)
Loris Leiva<EMAIL_ADDRESS>於 2019年12月18日 週三 上午1:00 寫道：

Hi there 👋
Thanks for raising this.
I'll try to implement something as soon as I've got some free time
otherwise I wouldn't be opposed to a PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lorisleiva/vuepress-plugin-seo/issues/2?email_source=notifications&email_token=AABZ2FE4EMFCSKMVL54L553QZEASLA5CNFSM4J3HNMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHDHFMY#issuecomment-566653619,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZ2FA4RJJR3SP3KGSBRDLQZEASLANCNFSM4J3HNMKQ
.

Any plan to add canonical links meta tag?
<link rel="canonical" href="https://example.com/my-article/" />

Vuepress v1.7.0 added support for canonical links.
Just add below on top of any markdown file.
---
canonical: https://google.com
---

Reference: https://github.com/vuejs/vuepress/pull/2658


Add a command to the CLI to generate types

There should be a command to generate types without having to deploy the whole app, for type checking/linting in CI, etc.

Any news on this? Right now we have to run sst dev in the CI to generate the types and run tsc. I don't like the idea of commiting the types along with the code source. It's very easy for someone to push outdated types deploy a broken version. What do you think @thdxr ?


Fixed versions

Older versions of PHPStan 0.12.x will give different output to 0.12.3.

CI needs fixing.
Use dev Rector, since it has fix for array_push: https://github.com/rectorphp/rector/pull/2566

CI needs fixing

CI was already broken (if you re-trigger master).

CI should be fixed as soon as discovered, instead of kept in false positive silence.


Convert existing CSS styles into styled-components

I have been absolutely in love with styled-components so far, and am working on my own fork of this boilerplate with all styles written in pure styled-components.
I'm really excited to use styled-components in my own apps, I was just curious if this is something that you would be interested in pulling back upstream once I have completed it?
Let me know your thoughts on this!

Unfortunately GitHub doesn't have any kind of polling so let's do this:
Add them: 👍
Don't Add them: 👎
Not sure: 😕

@garetmckinley I haven't messed around with them myself. Can you show us an example and describe how users can benefit from this?

The biggest obvious benefic is being able to keep your rules defined alongside your components. Not only reducing the amount of files needed (no css files) but also allowing you to visually grep what styles belong to what components, no need to open a css file and find a specific selector to edit.
I'm going to be implementing it to my own fork regardless, so once I convert some of it to styled-components, I'll show off some of the code here so that you can see how it would look using it.

Sounds good!

Here is how the Home.js screen would look utilizing styled-components

To do things like set the body selector for the background-color of the screen, we use an injectGlobal call inside the App.js

Doing this results in an unused expression, so I had to add /* eslint-disable no-unused-expressions */ to the top of the App.js file.

Woah. Is that even valid syntax? Is a custom syntax parser need for that?

Completely valid! 😄 No custom parsers either! It's utilizing the awesome styled-components, check it out! The babel syntax plugin for Atom has even added support for it already (that's why it's syntax highlighted for me).

@garetmckinley After all those javascript fatigue rants, I'm somewhat reluctant to add more libraries and frameworks to this project and others. I think we should wait until this kind of styling becomes more popular. For beginners who just want to mess around with this boilerplate, react/redux/electron/flow/eslint/babel/webpack might be already too much.

I definitely understand your hesitation towards it. Is it worth maybe just leaving this open to see if the request gains more backing?

Subscribing to this issue, as I'm one of the creators of styled-components. If you have any questions about implementation details, let me know! The one thing we're currently missing is syntax highlighting in all editors, but @garetmckinley has recently added support for Sublime Text, and Webstorm is also coming soon, with more on the roadmap.
In case you're wondering if this library is here to stay, the react core team are huge fans, and Dan has even publicly stated they're considering making it the "official" way of styling react apps. Thinkmill (the company I work for) has doubled down on their support, meaning not only is styled-components great right now, it'll only get better over the next weeks/months as I work on it full-time!
Again, any questions just let me know!
If you want to see what a real-world, small-ish react app built with styled-components look like that a look at the postcss.parts source!

Dan has even publicly stated they're considering making it the "official" way of styling react apps. Thinkmill (the company I work for) has doubled down on their support, meaning not only is styled-components great right now, it'll only get better over the next weeks/months as I work on it full-time!

Sounds good! I think we should add support out of the box but maybe provide styling examples later when ide/text editor integration is widespread

So I've done a bit of work on my fork of this boilerplate. Feel free to check out how I went about implementing styled-components.
I obviously have done a bit of additional work than just integrating styled-components, so I've went ahead and made another branch called styled-components-only. That way you can see how the repo would look with the css files directly translated to styled-components. I'm not finished with it yet, but it's a start.
The master branch has the common components split up into separate files for more sane management, but I didn't want to feel like I was imposing my personal configurations on the boilerplate; but still feel free to check it out if you wish 😄

@garetmckinley Initially lets provide a commented example of a styled-component in a comment. When editor configuration is widespread, lets migrate 100%.

Okay, great. I have heard back on the PR I have open with the official babel-sublime package, so we're close to widespread support :)
I'll work on it a bit later today if I have time, otherwise I'll get to it tomorrow 👍

Great! Here's what I have in mind:
/**
 * Here's an example using styled-components:
 *
 * const Title = styled.h2`
 *   color: green
 * `;
 */

Thoughts?

@garetmckinley styled-components looks great for me, but what if we have plenty of CSS code in the component file and lines per pages goes beyond thousand, then it may be little difficulty to scroll down to the JavaScript code (component logic) and comparing the styles, any thoughts about this?

then it may be little difficulty to scroll down to the JavaScript code (component logic) and comparing the styles, any thoughts about this?

You don't normally put all your components in the same file. Instead, colocate every styled component in its own file in the same folder. See the postcss.parts repo for an example: https://github.com/mxstbr/postcss.parts/tree/master/js/components/Header
This is what the file structure looks like:
Header/
├── index.js    # <-- The actual component
├── Link.js     # <-- Styled component
├── Subtitle.js # <-|
├── Title.js    # <-|
├── Wrapper.js  # <-|
└── Anchor.js   # <-|

This is what the index.js ( the actual component) looks like:
import React from 'react';
import styled from 'styled-components';

import { colors } from '../../constants';

import Wrapper from './Wrapper';
import Link from './Link';
import Title from './Title';
import Subtitle from './Subtitle';
import Anchor from './AbsoluteAnchor';

const Logo = styled(Anchor)`
  right: initial;
  left: 0;
  font-size: 1.5em;
  font-family: Georgia, Times, 'Times New Roman', serif;
`;

const Header = () => {
  return(
    <Wrapper>
      <Logo href="https://twitter.com/mxstbr"><mxstbr/></Logo>
      <Anchor href="https://github.com/himynameisdave/postcss-plugins#submitting-a-new-plugin">Add a plugin</Anchor>
      <Title><Link to="/">PostCSS.parts</Link></Title>
      <Subtitle>A searchable catalog of PostCSS plugins</Subtitle>
    </Wrapper>
  );
}

export default Header;

Not all that much code here! That's because all the styled components are colocated into the folder in separate file, like the Title:
import styled from 'styled-components';
import { colors } from '../../constants';

export default styled.h1`
  font-size: 3em;
  color: ${colors.brandColor};
  margin-bottom: 0.25em;
`;

Revisiting this issue after a couple of months. Its now pretty clear that styled-components is a proven concept. A PR for this will be welcome!

In my opinion styled-components not a good way. What is about third-party dependencies ?
Example : https://github.com/reactjs/react-tabs/issues/148
When we style some component with styled() it returns new type.
I think ccs-modules with post-css would be better solution

Example : reactjs/react-tabs#148

All styled-components does is pass in the className and wrap it in another component. That means this:
const MyButton = styled(ThirdPartyButton)`
  color: blue;
`

is the same as this (where the .abc class name applies the blue color):
<ThirdPartyButton className="abc" />

What react-tabs is doing there is a hacky workaround and not something that's advised or will happen often. (if ever) Not even the maintainer knows why that check is there ¯\_(ツ)_/¯

@mxstbr It will happen not often, but we will give people more flexibility in styling components.

but we will give people more flexibility in styling components.

People don't have to use styled-components. 😉 Also it might become the standard in the React community in the future and has a bunch of other benefits compared to a vanilla CSS setup.

Maybe the decision shouldn't be based off of one library that deviates from the standards ¯\_(ツ)_/¯
I'm sure they would welcome a PR to fix that incompatibility.

I'm shifting towards more vanilla technologies in order to lower the barrier to using this project. I think docs should be provided on how to add styled-components integration tho.

I agree, there should be instructions for using both styled-components and glamorous

This is how I did (hack-o style):
import React, { Component } from "react";
import ReactDOM from "react-dom";
import Styled from "styled-components";

const fetchStyles = () =>
  fetch(
    "https://gist.githubusercontent.com/bionicvapourboy/61d3d7a8546cb42e0e3194eb9505f48a/raw/5432218dd83320d53d1cbc2f230b81c765183585/style.css"
  ).then(response => response.text());

class App extends Component {
  state = {
    style: ""
  };

  componentDidMount() {
    fetchStyles().then(data => this.setState({ style: data }));
  }

  Wrapper = () => Styled.div`
    ${this.state.style}
  `;
  render() {
    const Wrapper = this.Wrapper();
    return (

        <Wrapper>

Styled

        </Wrapper>

Not Styled

Start editing to see some magic happen!

    );
  }
}

const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);

Demo: https://codesandbox.io/s/yw7xmx6x3x


Adds missing keys to svg feature

Looks good to me. Minor: move it to line 607?

So I better understand, why is that better than grouping these with the property?

Ugh, you're right and that was my intent, but I missed it


SourceLink won't work for linking to a tfs path

This was duplicate in #222. Will keep that one open instead.


Updated docs for the bundle

Not sure if putting full config on a separate page is a good idea.

Okey, I thought the page would be too long otherwise. I move it.
I have a question about "integration with other bundles". I do not agree with what our documentation says. That will not allow a user to change client in an easy way.
I've done like this in a few projects: https://github.com/Happyr/TranslationBundle#default-configuration But Im not sure that is a good best practice either.

Well, can be a separate page, but in a deeper level then. Other integrations might be in this section as well.
integration with other bundles? Where is it?

Okey.
https://github.com/php-http/documentation/pull/93/files#diff-33b9b1161d0ce83931e73c48bf9e6900R171

What I did was a copy paste from the bundle README. Doesn't mean we cannot write better documentation. :wink:

I started https://github.com/php-http/HttplugBundle/issues/58 for this discussion.

i am +1 for having a separate configuration reference page that is not part of the documentation. the reference must list each option and its meanings. the other page should explain the common use cases. those two things are different.

cool. lets wrap this up asap and then merge.

Wow, cool thing @dbu. Wanna do the fixes yourself?

i might find a moment tomorrow if tobias does not have the time

Sorry, read your comments now. Im doing some fixes now.

This PR is ready to be merged into #93


feature(editor): set route to in progress on edit, warn about unapproved routes when exporting

Checklist

[x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[x] Any modified or new methods or classes have helpful JSDoc and code is thoroughly commented
[x] The description lists all applicable issues this PR seeks to resolve
[x] The description lists any configuration setting(s) that differ from the default settings
[x] All tests and CI builds passing
[x] The description lists all relevant PRs included in this release (remove this if not merging to master)

Description
Two main changes:

When any part of a route gets edited, the progress gets set to In Progress.
In the Create Snapshot window, any in progress or pending routes will be displayed as a warning, since they will not be included in the published result.

The snapshot pane directly requests the list of routes from the backend, which requires a lock. Therefore, in the Editor Feed Source Panel, a lock is requested before opening the Snapshot pane. After closing, the lock is removed.

A few issues: Why are the tests failing? It looks like it is not related to my code.
Also, I'm having a type issue on line 78 in CreateSnapshotModal.js that shows up in VSCode.
"Cannot call fetchRouteEntities().then because property then is missing in  function [1].Flow(InferError)"

I think we finally got there in the end!


Version Information meta tag for Windows build

Application executables on Windows supports additional metadata called Version Information. The info is available in detail to the user by right clicking and choosing Properties > Details, it also shows the info under the .exe name in the Explorer and Taskbar entry and used for some System dialogs.
I can't seem to find a way to add this via the project.xml so I am requesting it.
It could be an entry like,
<meta if="windows"
	version="<IP_ADDRESS>"
	product="My AppName"
	description="My Application"
	company="My Company"
	copyright="2016 Author Name"
/>

The project.xml file is dealt with by the lime tools,
if you could reopen this issue over there https://github.com/openfl/lime/issues.


Document API endpoints

Endpoints inherited from CCF already have documentation, so there no need to rewrite them but they can be linked or attention can be drawn to important endpoints.
New scitt-ccf-ledger endpoints are not documented at all yet.

We may want to auto-generate those and also reference the public IETF spec.

The endpoints (Swagger) are visible under /app/api already.


Use Ubuntu 18.04 image for Bazel RBE

This is to update existing Bazel RBE docker image from ubuntu16.04 to ubuntu18.04 to solve UBSAN problem. (https://github.com/GoogleCloudPlatform/layer-definitions/issues/531)

@nlopezgi Can you take a look at this?

@nlopezgi Thank you for the detailed answer. Since I'm new on this topic, I'm going to dig more into this!

Shared a 1 pager with you with pointers internally.


Silence error on missing optional tools dependency

How to categorize this PR?

/kind bug
Fixes the problem described in https://github.com/gardener/gardener-extension-provider-gcp/pull/411#issuecomment-1068902051
Release note:

NONE

/assign @kon-angelo @acumino

/retest

Quickly tested this against https://github.com/gardener/gardener-extension-provider-gcp/pull/411: e.g. make revendor now works as expected without logging confusing error messages


Fix error matching bat and cmd file

https://github.com/lukesampson/scoop/blob/1836edba8857373f56a4332dab81a7030a47fe76/.editorconfig#L15
Miss symbol }.

Please rebase it to the develop branch.

Please rebase it to the develop branch.

rebase branch with tiny mistake. 😥
Do it. 👌


[Bug]: /v1/chat/completions流式的时候无法正常结束

Do you need to file an issue?

[ ] I have searched the existing issues and this bug is not already filed.
[ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[ ] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the bug
No response
Steps to reproduce
No response
Expected Behavior
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

具体在CustomSearchCallback  这个方法里面

while true 结束不了

我重写了这块代码，需要什么格式自己改改
class GraphRagLLMCallback(GlobalSearchLLMCallback, BaseLLMCallback):
"""
Contains functions to define custom callback handlers to enable the streaming of
graphrag's response via a generator function.
"""
def __init__(self, token_queue: Queue = None):
    super().__init__()
    self.q = token_queue

def on_llm_new_token(self, token: str):
    self.q.put(
        json.dumps({"done": False,"token": token, "context": None}).encode("utf-8"), block=True
    )

async def handle_stream_response(request, search, conversation_history):
future = gtypes.TypedFutureSearchResult
def stream_response():
    q = Queue()
    callback = GraphRagLLMCallback(token_queue=q)
    # 传递 `callback` 实例给搜索引擎
    search.callbacks = [callback]
    job_done = object()  # signals the processing is done

    async def run_search():
        result = await search.asearch(request.messages[-1].content, conversation_history)
        future.set_result(result)
        q.put(job_done, block=True)  # blocks until the token is consumed by the generator

    # 在一个独立的线程中运行异步任务
    loop = asyncio.new_event_loop()
    asyncio.set_event_loop(loop)
    loop.run_until_complete(run_search())
    loop.close()

    while True:
        next_item = q.get(block=True, timeout=300)  # blocks until an input is available
        if next_item is job_done:
            yield json.dumps({"done": True, "token": "结束", "context": None}).encode("utf-8")
            break
        yield next_item + b"\n"

return StreamingResponse(stream_response(), media_type="application/x-ndjson")

你是不是copy的官方的graphrag 加我的server？

@KylinMountain 我是直接 pip install graphrag 安装的，借鉴了你server的写法。互相学习

奥 那你会遇到无法停止的问题，我改了graphrag 加了end回掉了。那这个在graphrag-server中不是问题


Need search datatable with colom alias of sum/count

Summary of problem or feature request
How can I make the datatable to search field which has come from aggregate function like, SUM, COUNT, etc..
I also check this issue https://github.com/yajra/laravel-datatables/issues/219 but it did't help me and can not able to the get desired output
Code snippet of problem
Data Source (Modal file)
$data = DB::table('buyers')             ->select('buyers.id', 'buyers.username', DB::raw('COUNT(DISTINCT(' . DB::getTablePrefix() . 'accounts.id)) as total_accounts'), DB::raw('SUM(' . DB::getTablePrefix() . 'account_spend_history.amount_spend) as account_spend_total'))             ->leftJoin('accounts', 'buyers.id', '=', 'accounts.buyer_id')             ->leftJoin('account_spend_history', 'accounts.id', '=', 'account_spend_history.account_id')             ->groupBy('accounts.buyer_id'); $datatables = Datatables::of($data);         return $datatables->make(true);
My JS file
table = $('#inbox-table').DataTable({
    iDisplayLength: 100,
    aLengthMenu: [[100, 200, 300, 500], [100, 200, 300, 500]],
    processing: true,
    serverSide: true,
    scrollX: true,
    ajax: SITEURL + 'buyer/list',
    columns: [
        {
            data: 'id',
            name: 'buyers.id'
        },
        {data: 'username', name: 'buyers.username'},
        {
            data: 'total_accounts',
            name: 'total_accounts'
        },
        {
            data: 'account_spend_total',
            name: 'account_spend_total'
        },
        {
            data: 'action',
            name: 'action',
            orderable: false,
            searchable: false
            className: 'text-center'        }
    ],
    order: [[1, "desc"]],
});

Showing SQL Error
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'total_accounts' in 'where clause'
when I replace name: 'total_accounts' to name: 'accounts.id'
it is showing wrong output
System details

PHP Version : 5.6.3
Laravel Version : 5.1.40

Thanks.

See this demo for ref:
https://datatables.yajrabox.com/eloquent/advance-filter
https://datatables.yajrabox.com/eloquent/post-column-search
Try using filterColumn api and use having query.

Thanks.
I was looking for advance filter.

@yajra the server where you have the documentation is not working, please check it out.


[Bug]: Unable to open CJIT LN Channel

Describe the bug
I just tried multiple times to pay a CJIT LN invoice for 12_500 sats from Pheonix and it failed every time. Two orderIds are 1b75a644-8723-49b6-9782-2c34332600cb and cacbcf68-8f18-4e85-877e-ddf289ff7302 and BT logs show "message":"Channel capacity must be >= 20000sat.","type":"CHANNEL_REJECTED_BY_LSP"
BT error: https://synonymworkspace.slack.com/archives/C0726U60V6Y/p1716545752789479
Reproduce

With onchain funds but no LN connections
Create a 'spend instantly' cjit invoie
Attempt to pay from Pheonix (not sure if source is relevant)
Fail to spend message in Pheonix
CHANNEL_REJECTED_BY_LSP in BT logs
No spending balance in Bitkit

Screenshots / Recording
No response
Operating system
Android 13 TKQ1.221114.001
Bitkit version
v118
Log output
No response

MinChannelSize is always at least 20k sat

Fixed on BT side

Verified in v118 with the fix in BT


Bugfix/clear by tag on filesystem storage while files are already deleted

This PR fixes the behavior on the special case that file content is read while tag file is deleted
More description in #44
@marc-mabe is this kind of try...catch solution you had in mind?
Merging this PR closes #44

@skors Much thanks for this fix and unittest!
Today I had time play a little with it and was able to reduce the wait timings and removed the temporary file the tests still works (or fails) as expected.
This way the test should also fail if the process wait timings are not proper or even if something changed in the filesystem adapter which breaks the hack for delay unlink.
But I still doesn't understand why posix_kill(posix_getpid(), SIGTERM); is required.
Now it looks like the following:
    /**
     * @runInSeparateProcess
     */
    public function testClearByTagsWithoutLocking()
    {
        if (!function_exists('pcntl_fork') || !function_exists('posix_kill')) {
            $this->markTestSkipped('Missing pcntl_fork and/or posix_kill');
        }

        // create cache items
        $this->_storage->getOptions()->setDirLevel(0);
        $this->_storage->getOptions()->setFileLocking(false);
        $this->_storage->setItems([
            'a_key' => 'a_value',
            'b_key' => 'b_value',
            'other' => 'other',
        ]);
        $this->_storage->setTags('a_key', ['a_tag']);
        $this->_storage->setTags('b_key', ['a_tag']);

        $pidChild = pcntl_fork();
        if ($pidChild == -1) {
            $this->fail('pcntl_fork() failed');
        } elseif ($pidChild) {
            // The parent process
            // Slow down unlink function and start removing items.
            // Finally test if the item not matching the tag was removed by the child process.
            require __DIR__ . '/TestAsset/FilesystemDelayedUnlink.php';
            $this->_storage->clearByTags(['a_tag'], true);
            $this->assertFalse($this->_storage->hasItem('other'));
        } else {
            // The child process:
            // Wait to make sure the parent process has started determining files to unlink.
            // Than remove one of the items the parent process should remove and another item for testing.
            usleep(10000);
            $this->_storage->removeItems(['b_key', 'other']);
            posix_kill(posix_getpid(), SIGTERM);
        }
    }

    /**
     * @runInSeparateProcess
     */
    public function testClearByTagsWithLocking()
    {
        if (!function_exists('pcntl_fork') || !function_exists('posix_kill')) {
            $this->markTestSkipped('Missing pcntl_fork and/or posix_kill');
        }

        // create cache items
        $this->_storage->getOptions()->setDirLevel(0);
        $this->_storage->getOptions()->setFileLocking(true);
        $this->_storage->setItems([
            'a_key' => 'a_value',
            'b_key' => 'b_value',
            'other' => 'other',
        ]);
        $this->_storage->setTags('a_key', ['a_tag']);
        $this->_storage->setTags('b_key', ['a_tag']);

        $pidChild = pcntl_fork();
        if ($pidChild == -1) {
            $this->fail('pcntl_fork() failed');
        } elseif ($pidChild) {
            // The parent process
            // Slow down unlink function and start removing items.
            // Finally test if the item not matching the tag was removed by the child process.
            require __DIR__ . '/TestAsset/FilesystemDelayedUnlink.php';
            $this->_storage->clearByTags(['a_tag'], true);
            $this->assertFalse($this->_storage->hasItem('other'));
        } else {
            // The child process:
            // Wait to make sure the parent process has started determining files to unlink.
            // Than remove one of the items the parent process should remove and another item for testing.
            usleep(10000);
            $this->_storage->removeItems(['b_key', 'other']);
            posix_kill(posix_getpid(), SIGTERM);
        }
    }

closed by bb8a75c
Thanks!


Abdu acl

Work-in-progress
I added a lot of modifications to this merge. Briefly:

Added support to read and write the predicate defaultForNew. This is also reflected in the demo page.
Added Agent object to encapsulate the information of an agent WebID, permissions, is a list or an individual, this authorization is defaultForNew
Several bug fixes.

Remaining items:

Conforming to the new inheritance way in getPermissions and getAclResource where GET on an individual acl resource url always returns result.
Modifying the README file to reflect the most recent changes in permissions.js
Fix the bug when accessTo predicate has absolute url which doesn't work in some cases. Needs deeper investigation.

Thanks @ghanemabdo - merged into permissions branch!
Further comments / refactoring in the other PR.


Port amd64-only tests to arm64

Some tests are only built on amd64 because gated by go build flags like kprobe_amd64_test.go for example. They might be adaptable to arm64.

I have the ARM64 environment and I'm interested in it. Could you give me more information about this？

Some tests have compile flags like:
https://github.com/cilium/tetragon/blob/24e79a8ac382c8e924fdf7b51bf6a694abd03b78/pkg/sensors/tracing/kprobe_amd64_test.go#L4-L5
You can try to work on that in different steps:

list all the tests that have go build flags to only compile on amd64;
see if they can compile and run on arm64 (maybe not if they were constraints);
adapt the test to make them universal.

I was going to work on that at some point, but don't hesitate to try it out and explain what you did and what was the output here to advance on that.

Thanks, I'll try it.

One fix was trivial https://github.com/cilium/tetragon/pull/871/commits/3faf203959914b53711250aef28ff2b1a8c28996.
To search for such files in Tetragon repo:
rg "go:build amd64" -g '!**/vendor/**'

However, for the other only amd64 specific test, this is less trivial:
https://github.com/cilium/tetragon/blob/1b428756133ea6b1018ad1ba1f4964f04ff67653/pkg/sensors/tracing/kprobe_amd64_test.go#L98-L100

Lets close this we've capture the spirit of this most ARM tests are run. We need LVH fix and are blocked on that file a specific issue for that if someone cares.


Network Connectivity

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

A brief description
Impossible to update/install packges via wired connection. Only wireless.

Expected results

Actual results (with terminal output if applicable)

Your Windows build number

Steps / All commands required to reproduce the error from a brand new installation

Strace of the failing command

Required packages and commands to install

See our contributing instructions for assistance.

@rptr94 - Thanks for the post. Can you please fill up the additional fields in the above template? Especially, which Windows build you are on (you can find that out using the ver command). Also, can you paste your /etc/hosts file here?

done. now, neither wired neither wireless (i already reeinstall several times)

@rptr94 - Thanks. Still need the Windows build number. Can you please share that as well? Paste the output of the the Windows ver command.
Also, strace of a failing network access command. Example:
strace -o <trace_file> -ff curl www.microsoft.com
And share the trace_file

No problem, the build number is: Microsoft Windows [Version 10.0.14393]
the  "strace -o <trace_file> -ff curl www.microsoft.com" totally freezes.

@rptr94 - Thanks for the info. I think the command would have still generated the trace files. Anyways, see if you are running into #475? Do you have a firewall or AV software installed on your box?

i have two files but i cant upload.
Yes i have bitdefender.

See, if upgrading bitdefender helps. Or, try disabling it.

Nop, no sucess...

Just to be sure, the following sequence does not work?

disabling bitdefender
reboot
bash, wget www.microsoft.com

Please try this again on a more recent build and reopen if you still hit this issue


fix(iterator): remove unnecessary mutex

The mutex was removed in v9 in #2184 as the iterator cannot be used concurrently so I think we should also drop it in v8. Assuming v8 is still supported as it is mentioned in the installation section of the readme file

Makes sense, thanks!


Emits prioritizing the wrong type

@submit and all 'standard' events are always (payload: Event) => void | undefined even if I overwrite them inside emits option.
Reproduction:
// child
<script>
import { defineComponent } from 'vue';

export default defineComponent({
   emits: {
       sumbit: (id: number) => true
   }
});
</script>

// parent
<script>
import { defineComponent } from 'vue';
import Child from './Child';

export default defineComponent({
   components: {
      Child
   },
  setup() {
     return {
        test: (id: number) => console.log(id)
    }
  }
});
</script>

<template>
    <child @submit="test" />
</template>

This also broke vue-tsc!
Related issue: vue-tsc throws error if emits defined with array (emits: ['remove']):

Also I can't rollback to previous version (I try installing 0.1.0, which I had before, but I still have errors)

Sorry about that, I will fixed vscode-vue-languageservice version in vue-tsc to avoid vue-tsc broke with vscode-vue-languageservice update.

Thank you. Before that I rolled back to previous package-lock version and it helped (so finally I know why it exists 😆 ).

Fixed in 0.25.6 and update with vue-tsc 0.1.4.


Tag a new release

Hi there. Please would you consider tagging a new release on PyPI? The current release 0.5.0 on PyPI is from 2015 and lacks https://github.com/ludwiktrammer/django-tagging-autocomplete/commit/a34653ff67b22df79059c8fadbadf00524c557b9. Thanks!

@djjudas21 Done. Would you be able to verify that it works as expected?
Thank you for bringing my attention to the issue.

@ludwiktrammer Thanks - I will try it now

Works great - thanks :+1:


How to do inference without mmcv?

On a restricted platform, if I use mmcv, it takes me 20 minutes to compile it each time. So, is there any way to do inference without mmcv?I am testing on a restricted platform. If I use mmcv, it takes me 20 minutes to compile it each time. So, is there any way to do inference without mmcv?

Hi @likyoo This may be troublesome, because mmcv is the base dependent library. But if you export to onnx format, mmcv is not required.

thanks


Convert lib/refresh.js to use isomorphic-fetch

@rocky
Do you mean reflesh.js should use isomorphic-fetch ?
If so, i think we should use omni-fetch instead of isomorphic-fetch as I did before, since isomorphic-fetch never supports proxy.

Ok, make that omni-fetch then. Don't mind me, I don't know what I'm talking about. I just know that this pair and request are fundamentally different.

Just never use http client package which does not support proxy.
Many companies are in proxy enviroment and proxy is useful to developer and penetration tester to use local proxy tool like me.
For example, I could notice many unnecesary login requests thanks to local proxy tool.


Magenta showing up as Red in Iterm2

Am I confused or is Magenta really showing up as Red? My Ansi colors are correct as I use them all day long in scripting..

Color scheme has been updated as of 0.1.47 to mainly blue. Are you still having the same problem?


[RFC]: add constants/float32/max-base10-exponent-subnormal

Description
This RFC proposes

This RFC proposes adding the package @stdlib/constants/float32/max-base10-exponent-subnormal returning maximum base 10 exponent for a subnormal single-precision floating-point number.

var FLOAT32_MAX_BASE10_EXPONENT_SUBNORMAL = require( '@stdlib/constants/float32/max-base10-exponent-subnormal' );

console.log( FLOAT32_MAX_BASE10_EXPONENT_SUBNORMAL );
// => -38

Related Issues
No response
Questions
No.
Other
No.
Checklist

[x] I have read and understood the Code of Conduct.
[x] Searched for existing issues and pull requests.
[x] The issue name begins with RFC:.

Hey, I'll like to work on this!


Upgrade Spotless to 0.43.0 & Scala 2.12.19

Currently building off of master is broken because of:

[ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:2.30.0:check (default) on project parquet-format-structures: Execution default of goal com.diffplug.spotless:spotless-maven-plugin:2.30.0:check failed: java.lang.reflect.InvocationTargetException: 'com.sun.tools.javac.tree.JCTree com.sun.tools.javac.tree.JCTree$JCImport.getQualifiedIdentifier()' -> [Help 1]

Arrow hit the same issue: https://github.com/apache/arrow-datafusion-comet/pull/85 because of this: https://github.com/diffplug/spotless/issues/1774. Bumping spotless to fix building on master.
Reporter: Vinoo Ganesh / @vinooganesh
Assignee: Vinoo Ganesh / @vinooganesh
PRs and other links:

GitHub Pull Request #1287

Note: This issue was originally created as PARQUET-2441. Please see the migration documentation for further details.

Vinoo Ganesh / @vinooganesh:
We're also hitting this on master: https://github.com/scala/bug/issues/12783. Fixing will require an upgrade to scala 2.12.19.


delete user feature

Is the delete user feature merged with master branch and released?

@pkrishn It has not been merged in yet.


Submodules & references to other submodules

I have a monogame project with an executable and a library. I then made MonoGame and the library submodules my executable's repository. I have set up a submodule for the library. Both the executable and the library depend on MonoGame so I added references to it in both places.
When I generate the solutions and attempt to compile, the library cannot find MonoGame.
/opt/mono/lib/mono/4.5/Microsoft.Common.targets:  warning : Reference 'MonoGame.Framework' not resolved
/opt/mono/lib/mono/4.5/Microsoft.Common.targets:  warning : Reference 'MonoGame.Framework.Net' not resolved

If I move the MonoGame submodule inside the library project things work fine for both the library and the executable project.
Should submodules be able to resolve dependencies from the project they're included from? If not, what is the proper way to set up this type of project?

Modules don't resolve dependencies above or across the hierarchy; they can only see projects defined inside them or inside their submodules.  In this case, the library can't see MonoGame because it resides above it in the hierarchy.
The reason for this is that a flat hierarchy tends to lead to dependency hell; if you've ever had NuGet packages where one package depends on library A at a particular version, and then another package depends on library A at a different version, then you'll know what I mean.
I'm still quite torn on the issue; nested hierarchy has the deficiency that you have to place a dependency at the most abstract level (i.e. you need to place MonoGame under the library and not at the top level).  At the same time, it means that if someone depends on your library module, they have everything they need to use the library.  But it also means you can't use two libraries both depending on MonoGame (well, you can, but I'm not sure what the results will end up like).  So I don't have a good answer as to what the ideal architecture is here.
Suggestions are welcome, but I'm pretty sure this is an area of build systems that doesn't have a perfect solution.

I haven't spent much time with C#, I come from mostly java, so I'm mostly familiar with maven style dependencies (e.g. pulling compiled jars) and less so that of pulling source. Even then I have never really dug too deep into its internals.
I guess the main distinction would be that in this case we've got the code "in the project" vs an in external, compiled, shared copy (mavens ~/.m2 directory for example). When the project does it's dependency look up in maven it pulls the jars to that shared place and references them in the build proper.
Perhaps establishing a ~/.protobuild/ scheme or something for binary packages we could just reference a shared instance? Not sure honestly. It is still a bit wonky because I have ended up making a few tweaks to MonoGame so I really appreciate directly having the source available.
In the case of version difference, I think maven users tend to mark an exclusion. Example: http://stackoverflow.com/questions/4827335/different-versions-of-the-same-dependency-in-maven. If the two different versions don't behave in a compatible way, I'm not sure how you could build the project successfully anyway. Which version would you ship with the final binary? And now we're back to API stability -- gosh things go deep fast!
Anyway, thanks for your thought on the subject, compared to what I thought was available for building C# projects on linux Protobuild is amazingly simple and effective. For now I'm dealing with it by just copying the project definition into the parent.

Yeah I've heard Maven handles dependency management a lot better than NuGet / what we're doing here.  The problem I've noticed is that .NET is much more strict about assembly versioning, which causes all kinds of craziness when using incompatible versions.
If Maven is pulling dependencies from a shared location (like ~/.m2), what happens when you modify the source code of that dependency?  Or do you have to explicitly tell Maven you want to fork the common dependency (and then how does that work when you push your changes to a Git repository, given the dependency is likely stored externally?)

I've done some work today which should potentially clear the way for having package dependencies sit outside their normal location (i.e. in a folder in the root module or in a common area).

Typically with mavens you wouldn't have the source. The only times I have
is when using am IDE and having the source link for the debugger to use.
I've not had many occasions to make changes to the dependencies I user with
a mavens project though...
On Feb 6, 2015 7:25 AM, "James Rhodes"<EMAIL_ADDRESS>wrote:

I've done some work today which should potentially clear the way for
having package dependencies sit outside their normal location (i.e. in a
folder in the root module or in a common area).
—
Reply to this email directly or view it on GitHub
https://github.com/hach-que/Protobuild/issues/86#issuecomment-73229136.

I almost have a solution implemented for this, so this feature is on it's way (it just needs some more testing first).

Okay, so with 3cc16d6 you should now be able to set this up in a reasonable manner.  Basically add the package at all levels of your hierarchy (add the MonoGame package to both your executable module and the library submodule).  When Protobuild runs it will automatically detect the multiple references to the same package, and ensure that only a single working copy of the package is created (at the highest level, so in this case inside the executable module).  The library projects will then reference the copy in the executable's module.
I'm about to do some testing on Windows to make sure everything works there.  If you run into bugs with this new functionality please let me know.

All the tests are passing for the new functionality, so I'm going to close this issue as resolved.

Cool I'll give this a try this week!
On Feb 8, 2015 6:47 AM, "James Rhodes"<EMAIL_ADDRESS>wrote:

All the tests are passing for the new functionality, so I'm going to close
this issue as resolved.
—
Reply to this email directly or view it on GitHub
https://github.com/hach-que/Protobuild/issues/86#issuecomment-73407514.

BTW this is working well for my use case on Linux & Windows. Thanks!

Hrm, maybe I spoke to soon. A fresh checkout of my repository on Linux has this not working. Perhaps I didn't clean up properly the first time.

If you do "git clean -xdff" and then run Protobuild it should work, otherwise let me know.

I'll reopen this until we resolve any issues you might be having.

On windows (VS2013) generation & compilation works fine. On linux, using xbuild, it reports that it can't find MonoGame.Framework in the submodule. Opening the generated csproj  I see some Reference tags. I commented those out and replaced with
<ProjectReference Include="../relative/path/to/generated.csproj">
    <Project>{GUID HERE}</Project>
</ProjectReference>

and xbuild seems to run to success now. I haven't tested with msbuild on windows to compare, but it seems like it might just be an xbuild difference from VS issue at this point.

Is there a ".redirect" file in the submodule's package folder?  Basically the library submodule should have a "MonoGame" folder (where the package was registered), and it should have a .redirect file whose contents is the path to the MonoGame folder in the executable module.

The submodule doesn't have those. I'll try and package up a minimal
reproduction of the state of this thing.
On Mon, Feb 9, 2015 at 5:58 PM, James Rhodes<EMAIL_ADDRESS>wrote:

Is there a ".redirect" file in the submodule's package folder? Basically
the library submodule should have a "MonoGame" folder (where the package
was registered), and it should have a .redirect file whose contents is the
path to the MonoGame folder in the executable module.
—
Reply to this email directly or view it on GitHub
https://github.com/hach-que/Protobuild/issues/86#issuecomment-73609381.

 Lib2 depends on Lib1 and App depends on both.
Before generation:
https://dl.dropboxusercontent.com/u/282238/Dep.tar.bz2
After generation:
https://dl.dropboxusercontent.com/u/282238/Dep-generated.tar.bz2
If it matters:
Mono JIT compiler version 3.12.0 (tarball Thu Jan 15 08:07:24 UTC 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none
        Misc:          softdebug
        LLVM:          yes(3.4svn-mono-/)
        GC:            sgen

[emarcotte@localhost Dep]$ cat /etc/redhat-release
Fedora release 21 (Twenty One)

Oh, this change on a package basis; it uses package URIs to determine uniqueness of packages.
In the ZIP you've provided, you have nested submodules within (presumably) the same Git repository.  Protobuild submodules (and packages) tend to have a 1:1 relationship with Git repository URLs, that is, your submodules should either really be Git submodules (pointing to a different repository) or packages.
If you don't intend on cloning Lib1 or Lib2 independently from App, then you shouldn't put them in a separate submodule, just put them as projects in the same module.  Projects in this way will cross-reference as intended.
If you do want to clone or use Lib1 and Lib2 independently from App, you should store them in a seperate Git repository, and register the Git repository as a package on http://protobuild.org/ (you can also set up your own internal index using https://github.com/hach-que/Protobuild.Website).  Then you'd add the Lib1 and Lib2 packages to App, and add Lib1 as a package to Lib2.  When Protobuild resolves the packages it'll unify the working copies of Lib1 so that there's only one working copy of it in the module structure.

My actual app uses submodules, didn't realize it was potentially breaking
for the test tho. Will retry spitting it out tomorrow with the small test
program. Thanks again!
On Feb 9, 2015 9:42 PM, "James Rhodes"<EMAIL_ADDRESS>wrote:

Oh, this change on a package basis; it uses package URIs to determine
uniqueness of packages.
In the ZIP you've provided, you have nested submodules within (presumably)
the same Git repository. Protobuild submodules (and packages) tend to have
a 1:1 relationship with Git repository URLs, that is, your submodules
should either really be Git submodules (pointing to a different repository)
or packages.
If you don't intend on cloning Lib1 or Lib2 independently from App, then
you shouldn't put them in a separate submodule, just put them as projects
in the same module. Projects in this way will cross-reference as intended.
If you do want to clone or use Lib1 and Lib2 independently from App, you
should store them in a seperate Git repository, and register the Git
repository as a package on http://protobuild.org/ (you can also set up
your own internal index using
https://github.com/hach-que/Protobuild.Website). Then you'd add the Lib1
and Lib2 packages to App, and add Lib1 as a package to Lib2. When
Protobuild resolves the packages it'll unify the working copies of Lib1 so
that there's only one working copy of it in the module structure.
—
Reply to this email directly or view it on GitHub
https://github.com/hach-que/Protobuild/issues/86#issuecomment-73634655.

Sorry I didn't get back to this until now, but I still have trouble with actual submodules. (New archive: https://dl.dropboxusercontent.com/u/282238/Dep2.tar.bz2). Directory with 3 repos in it. Dep has submodule to the other 2 (lib1 lib2). Still results in
xbuild /v:q /nologo /p:GenerateFullPaths=true "/p:Configuration=Debug" "/p:Platform=Any CPU"
/home/emarcotte/src/Dep2/Dep/Lib1/src/Lib1.cs(3,22): warning CS1591: Missing XML comment for publicly visible type or member `Lib1.Lib1'
/home/emarcotte/src/Dep2/Dep/Lib1/src/Lib1.cs(4,22): warning CS1591: Missing XML comment for publicly visible type or member `Lib1.Lib1.DoIt()'
/opt/mono/lib/mono/4.5/Microsoft.Common.targets:  warning : Reference 'Lib1' not resolved
/home/emarcotte/src/Dep2/Dep/Lib2/src/Lib2.cs(3,8): error CS0246: The type or namespace name `Lib1' could not be found. Are you missing an assembly reference?
Makefile:20: recipe for target 'compile' failed
make: *** [compile] Error 1

Setting up a package index for this seems like overkill, so I'd like to try and stick with submodules where possible.

The reason you're having trouble with submodules is because they're managed by Git, not Protobuild.  Thus the new uniqueness detection built into Protobuild doesn't kick in because it's not actually the process cloning the library source code.  When Git clones the submodules, it doesn't pay any attention as to whether there's already a copy of the submodule higher up or elsewhere in the module hierarchy.
I just pushed a new version of Protobuild that allows you to add packages with http-git:// and https-git:// protocol URLs.  These URLs refer directly to the Git repositories that you want to add, and don't require a package index to be configured with a package.
For example, if you wanted to add a Git repository at https://github.com/emarcotte/Lib1, you would do Protobuild.exe --add https-git://github.com/emarcotte/Lib1.  This won't query any package indexes; it'll just treat it as if a package index returned with a result of "source package only at this Git URL; no binary versions available".

Oh my mistake! I think I keep mixing up terminology. I will give this
version a try. Thanks again for all the help
On Sun, Feb 15, 2015 at 7:59 PM, James Rhodes<EMAIL_ADDRESS>wrote:

The reason you're having trouble with submodules is because they're
managed by Git, not Protobuild. Thus the new uniqueness detection built
into Protobuild doesn't kick in because it's not actually the process
cloning the library source code. When Git clones the submodules, it doesn't
pay any attention as to whether there's already a copy of the submodule
higher up or elsewhere in the module hierarchy.
I just pushed a new version of Protobuild that allows you to add packages
with http-git:// and https-git:// protocol URLs. These URLs refer
directly to the Git repositories that you want to add, and don't require a
package index to be configured with a package.
For example, if you wanted to add a Git repository at
https://github.com/emarcotte/Lib1, you would do Protobuild.exe --add
https-git://github.com/emarcotte/Lib1. This won't query any package
indexes; it'll just treat it as if a package index returned with a result
of "source package only at this Git URL; no binary versions available".
—
Reply to this email directly or view it on GitHub
https://github.com/hach-que/Protobuild/issues/86#issuecomment-74447462.

Yeah there's a few different concepts here:
Protobuild Module: A module is a folder that has Protobuild.exe and Build\Module.xml.  When you have a Protobuild module inside another module (as a subdirectory), it's referred to as a submodule.
Git Submodule: These are submodules or "sub-repositories" managed by Git.  In the past before package management, Protobuild submodules had a one-to-one relationship with Git submodules.
Protobuild Package: This is the new, more preferred way of doing things.  These are very similar to Git submodules, but with additional metadata that allows Protobuild to be smarter about how Protobuild submodules exist.  This includes duplicate reference detection (where multiple Protobuild submodules use the same package, Protobuild will make sure there's only a single working copy), and support for binary / compiled versions of a package (which is entirely optional).  Both are supported when using a package managed by a package index (like the one on http://protobuild.org), but using the new http-git:// / https-git:// protocols, you can get the duplicate reference detection without registering a package anywhere.

Looks like xbuild is happier. I've added https-git://url-to-lib/ and https-git://url-to-monogame/ in my main app and https-git://url-to-monogame/ in my lib as <PackageRef>s. Running Generate runs through the projects twice, but does only generate an "empty" MonoGame directory with a .redirect in the submodule.
Will play with it some and try to get the hang of it, but this issue can probably be closed -- until I do something else bone-headed again :)

Looks like xbuild is happier. I've added https-git://url-to-lib/ and https-git://url-to-monogame/ in my main app and https-git://url-to-monogame/ in my lib as s. Running Generate runs through the projects twice, but does only generate an "empty" MonoGame directory with a .redirect in the submodule.

That's the expected result :)


add Umami component to src/index.js

Umami component was not included in index.js exports. Modified Umami attribute names as well.

Thanks!


Switch from Travis to Circle for CI testing

Copy .sample.env to .env before testing to ensure environment
variables are set correctly
Remove travis configuration file

Looks like REDIS_URL is necessary https://circleci.com/gh/thoughtbot/hound/23

Added a pre-build script to copy .sample.env to .env - that gives us a default REDIS_URL, along with all the other required environment variables.
It also forces us to keep .sample.env up to date. :smile:

Passing build!

So much red! :+1:

woohoo! Travis is still thinking about it...

How about parallelizing?
https://circleci.com/docs/parallel-manual-setup

That's a good idea - it would probably speed up the tests a bit.
I think I'll hold off for now, because a lot of other people have failing PRs that depend on this one. I'll open another PR for parallelization.


DatePicker shouldn't use DD/MM/YYYY by default.

The US date format is ambiguous for dates with day <=12 && day !== month.
05/02/2016 could be read as either May 2nd, or Feb 5th.
I'm thinking ISO8601 (YYYY-MM-DD) would be a good default as it works everywhere, and doesn't have the localisation issues that moving to a short-month-name default (e.g. "2 May 2016") would bring.
Admittedly most users will want to change the date format through the provided hook, but a sensible default would be... sensible.
Happy to create a PR.

We have also started a discussion about it here https://github.com/callemall/material-ui/pull/1658#issuecomment-145681445

I saw that issue, but it was primarily about full i18n. This would be more of a quick fix for the default date format.
It needs to be fixed regardless of the approach is chosen for i18n, as there will always be a default, so it might as well be a sensible one.


Hiding small balances doesn't work properly, continued

Sorry for creating another issue on that, but I don't know how to reopen the existing issue that has been closed without any chance for me to reply first. On top of that, I left a comment in the original issue that received no reply, so I presume there was no notification because the issue was closed.
Please forgive me for acting stupid, but I am not a frequent Github user :P
vvv my last comment from the original issue below vvv
@simcheolhwan, thanks for replying. Although I do not agree to close this issue that fast. I understand that there are reasons that some of the tokens shouldn't be hidden away in the circumstances you mentioned. But what about all the tokens with a flat out zero ("0" without even a decimal point) that currently persist to be shown (see my screenshot), those should be hidden, don't you agree?
And if not, what is the point of the whole "Hide small balances" feature at all -- it is to hide away the dust, and for sure not only LUNA and UST, don't you think?
Originally posted by @sriedel1970 in https://github.com/terra-money/station-extension/issues/10#issuecomment-1111048147

I agree that if the value is 0, it would be reasonable to be hidden.


DataType Page: Model : Add Id and Parent Id to table/domain/dao etc.

Assign default ids (not auto assign) i.e. rownum * 100

Client's are advised to delete and recreate data_types with parent id's after applying this fix.


Drop support for Shoots with Kubernetes version == 1.24

How to categorize this PR?

/kind cleanup
What this PR does / why we need it:
Drop support for Shoots, Seeds and Gardens with Kubernetes version == 1.24.
Notable changes:

Drop deploying PSP resources and handling for PSP migration
Deprecate allowPrivilegedContainers field in the Shoot API.
Adapt Seccomp profile defaulting: https://github.com/gardener/gardener/blob/master/docs/usage/default_seccomp_profile.md
Drop kubeapiserver watchdog sidecar, https://github.com/gardener/gardener/blob/5b76b2ed9066f69b8b71d9c150914d812a65879c/pkg/component/kubeapiserver/deployment.go#L400C1-L406C4
Drop workaround for kubeproxy: https://github.com/gardener/gardener/blob/5b76b2ed9066f69b8b71d9c150914d812a65879c/pkg/component/kubeproxy/resources/cleanup.sh#L9-L16

Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/8921
Special notes for your reviewer:
Please follow the dedicated commits for easy reviewing.
Release note:

⚠ Gardener does no longer support garden, seed, or shoot clusters with Kubernetes versions == 1.24. Make sure to upgrade all existing clusters before upgrading to this Gardener version.

The `spec.kubernetes.allowPrivilegedContainers` field in the Shoot API is deprecated and will be removed in a future version. This field is not relevant to Shoots with kubernetes versions >= 1.25. Please adapt your controllers accordingly.

/retest

/retest

/assign

/assign

/hold until gardener v1.89 is released.

One question - How the old secrets of ServiceAccount will be cleaned/removed from cluster? Other than that LGTM

There is this legacy-serviceaccount-token-cleaner introduced in the KCM.

/unhold
gardener v1.89 is released, we can go ahead with this PR.
PTAL, @oliver-goetz @acumino

About dropping the token-invalidator: The LegacyServiceAccountTokenNoAutoGeneration feature gate it is only GA and locked to default in 1.26. Hence, I guess we have to keep it until 1.26 is the lowest supported version?

About dropping the token-invalidator: The LegacyServiceAccountTokenNoAutoGeneration feature gate it is only GA and locked to default in 1.26. Hence, I guess we have to keep it until 1.26 is the lowest supported version?

Yeah, we can. It is beta from v1.24, so enabled by default, but if somebody has disabled it on purpose, then we need the handling, I can revert the commit.

Force-pushed to resolve the conflicts.

/lgtm

/approve
/lgtm
Nice PR @shafeeqes, kudos 🙇🏻

Force-pushed to resolve the conflicts.


[Bug] No result from testing

Describe the bug
Im running the async function from this repo and im getting no result.
To Reproduce
Steps to reproduce the behavior:
Im running the async function from this repo
import postbin
# Async app
async def main():
    url = await postbin.postAsync(f"FooBar Bazz")
    print(f"Your paste is located at {url}")

Expected behavior
I should be getting an output, but im getting literally nothing, not even an error
Screenshots & Tracebacks

Package info:

[ x ] I have checked for open issues regarding this bug
[ x ] I have checked open pull requests for fixes to this issue
[ x ] I have ensured I have updated the module
[ ] I am sure its not me being stupid

How are you calling this function?

How are you calling this function?

for some reason its working now, nothing changed it just decided to work

Nice