capybara-webkit servers hangs indefinitly

We have a spec that does the following:
    visit "/customers"
    within("#customer-1") do
      find('a').click
    end

    expect(page).to have_css('tr.myclass', count: 1)

The spec finishes successfully but the capybara_webkit process never finishes.
This is reproducible with this single spec, we can't figure out the reason though.
When killing the process manually rspec will also complete. So as workaround we added to rspec:
config.after :suite do
    if Capybara.app
      pid = Capybara.current_session.driver.instance_variable_get("@options")[:server].pid
      Process.kill('TERM', pid)
    end
end

We are using capybara-webkit 1.11.1 (qt 5.6.1-1) and capybara 2.7.1 with ruby 2.3.1. The spec tests a React page, but it does not occur in other specs for the same React page. This happens on both Mac OSX 10.11.5 and Ubuntu 14.04 LTS. Please let me know if you need more information.
Debug output
Finished "EnableLogging()" with response "Success()"
Wrote response true ""
Received "SetUnknownUrlMode(block)"
Started "SetUnknownUrlMode(block)"
Finished "SetUnknownUrlMode(block)" with response "Success()"
Wrote response true ""
Received "SetTimeout(-1)"
Started "SetTimeout(-1)"
Finished "SetTimeout(-1)" with response "Success()"
Wrote response true ""
Received "GetWindowHandle()"
Started "GetWindowHandle()"
Finished "GetWindowHandle()" with response "Success({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde})"
Wrote response true "{c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}"
Received "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)"
Started "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)"
Finished "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)" with response "Success()"
Wrote response true ""
Received "ClearCookies()"
Started "ClearCookies()"
Finished "ClearCookies()" with response "Success()"
Wrote response true ""
Received "GetWindowHandle()"
Started "GetWindowHandle()"
Finished "GetWindowHandle()" with response "Success({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde})"
Wrote response true "{c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}"
Received "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)"
Started "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)"
Finished "WindowResize({c0719c54-d5dc-4bbd-95fb-bd7fbe2effde}, 1280, 1024)" with response "Success()"
Wrote response true ""
Received "ClearCookies()"
Started "ClearCookies()"
Finished "ClearCookies()" with response "Success()"
Wrote response true ""
Received "Visit(http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679)"
Started "Visit(http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679)"
Load started
"Visit(http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679)" started page load
Started request to "http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679"
Finished "Visit(http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679)" with response "Success()"
Started request to "http://<IP_ADDRESS>:50281/assets/application-8513c6cbd1e8a5c32a595710e2e1967b.css"
Started request to "http://<IP_ADDRESS>:50281/css/font-awesome-4.4.0.min.css"
Started request to "http://<IP_ADDRESS>:50281/assets/application-webpack-1aea4f6afccb988db918f391580d3ef2.js"
Received 200 from "http://<IP_ADDRESS>:50281/customers?id=7a79d770-e4b8-4015-af75-9d4693ad5679"
Received 200 from "http://<IP_ADDRESS>:50281/css/font-awesome-4.4.0.min.css"
Received 200 from "http://<IP_ADDRESS>:50281/assets/application-8513c6cbd1e8a5c32a595710e2e1967b.css"
Received 200 from "http://<IP_ADDRESS>:50281/assets/application-webpack-1aea4f6afccb988db918f391580d3ef2.js"
Started request to "http://<IP_ADDRESS>:50281/js/go"
Page finished with true
Load finished
Page load from command finished
Wrote response true ""
Received "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Started "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Finished "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)" with response "Success()"
Wrote response true ""
Received "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Started "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Finished "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)" with response "Success()"
Wrote response true ""
Received 200 from "http://<IP_ADDRESS>:50281/js/go"
Started request to "http://<IP_ADDRESS>:50281/img/icon-menu-search.svg"
Received 200 from "http://<IP_ADDRESS>:50281/img/icon-menu-search.svg"
Received "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Started "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)"
Finished "FindCss(#customer-7a79d770-e4b8-4015-af75-9d4693ad5679)" with response "Success(1)"
Wrote response true "1"
Received "Node.visible"
Started "Node.visible"
Finished "Node.visible" with response "Success(true)"
Wrote response true "true"
Received "Node.findCssWithin"
Started "Node.findCssWithin"
Finished "Node.findCssWithin" with response "Success(2)"
Wrote response true "2"
Received "Node.visible"
Started "Node.visible"
Finished "Node.visible" with response "Success(true)"
Wrote response true "true"
Received "Node.leftClick"
Started "Node.leftClick"
Started request to "http://<IP_ADDRESS>:50281/js/go"
Received 0 from "http://<IP_ADDRESS>:50281/js/go"
Load started
"Node.leftClick" started page load
Started request to "http://<IP_ADDRESS>:50281/invoices/status/all/period/all?filter_customer=7a79d770-e4b8-4015-af75-9d4693ad5679"
Finished "Node.leftClick" with response "Success()"
Started request to "http://<IP_ADDRESS>:50281/assets/application-8513c6cbd1e8a5c32a595710e2e1967b.css"
Started request to "http://<IP_ADDRESS>:50281/css/disable-transitions.css"
Started request to "http://<IP_ADDRESS>:50281/assets/application-d121393ce63fc07a2bb840d9a25a74e2.js"
Started request to "http://<IP_ADDRESS>:50281/assets/application-webpack-1aea4f6afccb988db918f391580d3ef2.js"
Received 200 from "http://<IP_ADDRESS>:50281/invoices/status/all/period/all?filter_customer=7a79d770-e4b8-4015-af75-9d4693ad5679"
Received 304 from "http://<IP_ADDRESS>:50281/assets/application-8513c6cbd1e8a5c32a595710e2e1967b.css"
Received 200 from "http://<IP_ADDRESS>:50281/css/disable-transitions.css"
Received 304 from "http://<IP_ADDRESS>:50281/assets/application-webpack-1aea4f6afccb988db918f391580d3ef2.js"
Received 200 from "http://<IP_ADDRESS>:50281/assets/application-d121393ce63fc07a2bb840d9a25a74e2.js"
Page finished with true
Load finished
Page load from command finished
Wrote response true ""
Received "FindCss(tr.invoice-record)"
Started "FindCss(tr.invoice-record)"
Finished "FindCss(tr.invoice-record)" with response "Success(1)"
Wrote response true "1"
Received "Node.visible"
Started "Node.visible"
Finished "Node.visible" with response "Success(true)"
Wrote response true "true"
Received "Reset()"
Started "Reset()"
Finished "Reset()" with response "Success()"
Wrote response true ""
Received "EnableLogging()"
Started "EnableLogging()"
Finished "EnableLogging()" with response "Success()"
Wrote response true ""
Received "SetUnknownUrlMode(block)"
Started "SetUnknownUrlMode(block)"
Finished "SetUnknownUrlMode(block)" with response "Success()"
Wrote response true ""
Received "SetTimeout(-1)"
Started "SetTimeout(-1)"
Finished "SetTimeout(-1)" with response "Success()"
Wrote response true ""
Received "GetWindowHandle()"
Started "GetWindowHandle()"
Finished "GetWindowHandle()" with response "Success({e4b1dee7-1fdd-4980-92f6-25dbd354bd21})"
Wrote response true "{e4b1dee7-1fdd-4980-92f6-25dbd354bd21}"
Received "WindowResize({e4b1dee7-1fdd-4980-92f6-25dbd354bd21}, 1280, 1024)"
Started "WindowResize({e4b1dee7-1fdd-4980-92f6-25dbd354bd21}, 1280, 1024)"
Finished "WindowResize({e4b1dee7-1fdd-4980-92f6-25dbd354bd21}, 1280, 1024)" with response "Success()"
Wrote response true ""
Received "ClearCookies()"
Started "ClearCookies()"
Finished "ClearCookies()" with response "Success()"
Wrote response true ""

Ivonk, did you find any solution to this? I believe I am having the same issue.

Hi @pmatsinopoulos,
No real solution, but the workaround I mentioned above works for us.

Closing due to age - If this is still an issue with the latest release we can reopen when a means to replicate is provided.


prepared release of version 1.7.1

Proposed changes:
Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@wochinge Travis is failing (pkg_resources.ContextualVersionConflict: (cloudpickle 1.3.0 (/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages), Requirement.parse('cloudpickle~=1.2.0'), {'gym'})). However, locally everything is working and the branch 1.7.x is green as well. What should I do? Seems to be a problem with travis.

@tabergma This has to be resolved first. Running the rasa cli doesn't work otherwise.


Kma 161770415 update rate engine shipmentlineitem

Description
This modifies the rate engine's ComputeShipment so that it returns not just the fee with the cost but the rate (with discount rate applied) and then saves it to the shipment_line_items table with the other values.  It also modifies the "ComputeShipmentLineItemCharge" so that it returns the discounted rate as well.  This rate gets  saved to shipment_line_items when the pre-approvals are saved.
Reviewer Notes
Are there any missing tests or error handling?
Note that the linehaul rate should have a value of zero (since it represents a total of multiple fees, not a value based on one rate)
Setup
To test in the app, you will need to get a shipment to the "in transit" state, making sure the shipment has a net weight and an actual pickup date. You should be able to populate your DB with the db_populate_e2e script, then do a local login to the TSP interface with<EMAIL_ADDRESS>Go to the "in transit" shipments in the queue, then pick the shipment with locator ENTDEL. Click the Deliver button and submit a delivery date. You should now see applied rates for records in the ShipmentLineItem table.
Changes value of applied_rate in shipment_line_items table to be in millicents
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

I realized I need to add some code after Patrick's PR lands in order to make sure the applied_rate gets saved in the tables for the accessorials, so changing this to WIP.

No longer WIP

applied_rate is now represented as millicents in order to represent the accuracy of 'Full Unpack' whose rate is providedin millicents


[GSSoC'23] Updating readme file of Music Guess Game

PR Description 📜
Updating the Title of the Readme file of Music Guess Game.

Thank you soo much for contributing to our repository 💗

Thank you @Avdhesh-Varshney ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @Avdhesh-Varshney,
Please make sure to link the relevant issue using the appropriate syntax, such as "#issueNumber" 👀.
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @Avdhesh-Varshney , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Add release it tooling and config

@pbredenberg please rebase this on origin/master. When doing so, you can fix the spelling of "grammer" in 9ee9acb

@jthomerson what have you got against my Grammer? She's a sweet old thing (and actually she died).

Looking good @pbredenberg. One other comment, and at this point I really hate to mention: there seems to be 69 commits in this MR. Is that because there really are 69 distinct pieces to this MR, or is it because the approach changed over time and the changes were committed on top of existing code? IOW, could some of those commits be squashed for a cleaner history?
Thanks!

@yokuze Condensed down to 39 commits. Lots of commits are intermingled with additions/removals of dependencies, so I think this is as far as I can condense it. I will try to be a little less granular with commits in the future.


BrokenProcessPool encountered when passing logging configuration to spawn subprocess on linux (hashtag1160)

I am attempting to get loguru working for spawned subprocesses and have been running into a concurrent.futures.process.BrokenProcessPool crash after attempting to follow the advice in issues such as  and as illustrated in this PR:
This crash only happens on Linux, the issue is not reproducible on macOS.
I am hoping for some guidance on what might be wrong here and if this is something that could be fixed within loguru, or that I can change on my end.
This is a program that reproduces the issue:
import multiprocessing
import sys
from concurrent.futures import ProcessPoolExecutor, as_completed

from loguru import logger

def _processpool_initializer(parent_logger):
    logger._core = parent_logger._core  hashtag type: ignore

    print("before failure", flush=True)
    logger.info("BOOM")
    print("after failure", flush=True)

def upper(v):
    return str(v).upper()

def main():
    logger.remove()
    logger.add(sys.stdout, enqueue=True)

    executor = ProcessPoolExecutor(
        max_workers=1,
        initializer=_processpool_initializer,
        initargs=(logger,),
        mp_context=multiprocessing.get_context("spawn"),
    )

    futures = {}
    for input in ["a", "b", "c"]:
        futures[executor.submit(upper, input)] = input

    for future in as_completed(futures):
        input = futures[future]
        r = future.result()
        print(f"Result: {r}", flush=True)

if __name__ == "__main__":
    main()

This is the output of the above program:
before failure
Traceback (most recent call last):
  File "/workspaces/plus/python/pdf-anonymizer/scripts/tmp/processpool-loguru.py", line 42, in <module>
    main()
  File "/workspaces/plus/python/pdf-anonymizer/scripts/tmp/processpool-loguru.py", line 37, in main
    r = future.result()
        ^^^^^^^^^^^^^^^
  File "/home/vscode/.rye/py/cpython line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.rye/py/cpython line 401, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

I am on version:
loguru==0.7.2

With a bit of debugging into loguru, I was able to determine that the subprocesses seems to be crashing on this line:
)

to fix your trouble check this fix, i see it in another issue,
https://github.com/Jostino/RimWorld-it/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Constant occ fix

Implemented a filter to ensure a 48-row window

@ian-r-rose i am having trouble debugging the test case we identified because my dev data is a smaller set and it is not in there. any recs?

@ian-r-rose i am having trouble debugging the test case we identified because my dev data is a smaller set and it is not in there. any recs?

Now that the nightly build has run, you should be able to use deferral and point to the prod version of the five-minute data.

For the constant occupancy model, you can temporarily adjust the time frame in the initial CTE to make it look at the specific date you are interested in


Make docker events less reactive

On the system with many containers running any container's state change will trigger the event and cause the list's reloading. In some cases, this can be completely unnecessary, for example, if state change occurred in one of the containers we don't care about (excluded directly or indirectly).

related to #14


Move generate of context into background as it takes a bit of time...

great job!
please publish to linqpad web site!
http://www.linqpad.net/richclient/datacontextdrivers.aspx
when adding json from web it takes quite a while to generate classes for this sample rest api:
http://northwind.servicestack.net/

Thanks!
Yes, I did notice that part of the work does appear to block the UI when testing a few apis myself recently. I'm surprised that I let that sneak into the design but I'll review the code when I get a chance and see if I can sort it out. Also adding POST support is overdue. With those changes I think it will be in a reasonable place to submit to the official drivers list :)


fix: 🎨 make build/dev work OTB under powershell

Where does craco get installed? Should it be a dev dependency in package.json?


chore(next): exports initPage utility

Description
Exports the initPage utility for use outside of the admin panel, i.e. consuming apps that may want to authenticate server-side (among other things). Also ensures this function can be used outside of admin-only routes, i.e. a consuming app's homepage.

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Related: #6127


vue3+scss /* px-to-viewport-ignore */ not work

it looks like not work.
(vue3+scss+vite)

try Px/PX/pX which will not be transformed

try Px/PX/pX which will not be transformed

Thank you for your reply，but vscode plugin volar will transform Px/PX/pX  to px.

try try
@use "sass:string";
.class{
 font-size: string.unquote("16px");
}


about Sepformer，why two FeedForward？

Hi @rijalsankalp  @VoidCU
I found that the Sepformer you implemented is somewhat different from speechbrain and Zhongyang-debug/Attention-Is-All-You-Need-In-Speech-Separation, but yours is closer to the original paper description? But your Sepformer has two FFW,  why?  Also what are your test results?
thanks！

No this is not the implementation of the original paper, but an attempt to implement a different kind of transformer model, which reduces quadratic complexity problem of the original transformer architecture. We have tried to use the transformer architecture suggested in Perceiver: General Perception with Iterative Attention.
For the case of two FFW, they are  being used to scale the latent array (it has less dims than the input data) to the original shape before decoding the separated audio.
No test results as of now, we're still training our model and it may need several changes.


Request for correlating container pids to host pids

Debugging resource hog processes in containers becomes complex due to pid namespace.
Looking for a /proc way to convert container pids from container pid namespace to host pids.
Best way I've come up with so far is to search host level /proc/*/cmdline looking for "lxd monitor", then scan pid tree of each monitor looking for systemd, then adjust container pids by the difference of host level systemd pid number by container systemd pid == 1.
Surely there must be a better + more robust/correct way to do this.
Let me know if there's a standard approach/solution to doing this.
Many thanks.

There is no concept of container as far as the kernel is concerned, so there's no super easy way to do so.
It's also made more complicated by the fact that the container itself can be using the pid namespace.
Very recent kernels do let you see the PID at every level of the namespace tree, but that's still not very useful as there is no way to say "give me the host pid for pid X in container Y".
You can get the list of all "pid X" but it won't tell you in what container that is:
stgraber@castiana:~$ lxc exec ups-monitor ps faux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      5231  0.0  0.0  37764  2092 ?        Rs+  23:55   0:00 ps faux
root      4289  0.0  0.0  21628  2636 ?        Ss   23:40   0:00 bash
root      4299  0.0  0.0   4512  1188 ?        S+   23:40   0:00  \_ sh ups.sh
root      5230  0.0  0.0   7720   592 ?        S+   23:55   0:00      \_ sleep 5
root         1  0.0  0.0  37392  3872 ?        Ss   Jul01   0:00 /sbin/init
root        57  0.0  0.0  41768  1828 ?        Ss   Jul01   0:00 /lib/systemd/systemd-udevd
root        58  0.0  0.0  35280  4852 ?        Ss   Jul01   0:00 /lib/systemd/systemd-journald
root       261  0.0  0.0  16124  1944 ?        Ss   Jul01   0:00 /sbin/dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df
message+   334  0.0  0.0  42908  2160 ?        Ss   Jul01   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
daemon     340  0.0  0.0  26048  1308 ?        Ss   Jul01   0:00 /usr/sbin/atd -f
syslog     341  0.0  0.0 186904  1780 ?        Ssl  Jul01   0:00 /usr/sbin/rsyslogd -n
root       344  0.0  0.1<PHONE_NUMBER>4 ?        Ssl  Jul01   0:10 /usr/lib/snapd/snapd
root       347  0.0  0.0  20104  1700 ?        Ss   Jul01   0:00 /lib/systemd/systemd-logind
root       350  0.0  0.0 274492  3280 ?        Ssl  Jul01   0:02 /usr/lib/accountsservice/accounts-daemon
root       352  0.0  0.0  65524  2832 ?        Ss   Jul01   0:00 /usr/sbin/sshd -D
root       353  0.0  0.0  27732  1564 ?        Ss   Jul01   0:00 /usr/sbin/cron -f
root       388  0.0  0.0 277188  3892 ?        Ssl  Jul01   0:00 /usr/lib/policykit-1/polkitd --no-debug
root       633  0.0  0.0  14480  1160 console  Ss+  Jul01   0:00 /sbin/agetty --noclear --keep-baud console<PHONE_NUMBER>0 9600 linux

stgraber@castiana:~$ grep NSpid.*633$ /proc/*/status
/proc/8754/status:NSpid:	8754	633

In this example, I got lucky, when looking from the host, it only found a single host process that's mapped as "pid 633" in a container. But that could well have returned dozens of results.
For example, looking for PID 1:
stgraber@castiana:~$ grep "NSpid.*      1$" /proc/*/status
/proc/10393/status:NSpid:	10393	5321	1
/proc/11630/status:NSpid:	11630	31521	1
/proc/11654/status:NSpid:	11654	31535	3	1
/proc/12184/status:NSpid:	12184	5786	1
/proc/12188/status:NSpid:	12188	2084	1
/proc/12221/status:NSpid:	12221	2107	1
/proc/12297/status:NSpid:	12297	2150	1
/proc/12401/status:NSpid:	12401	2169	1
/proc/17627/status:NSpid:	17627	32351	1
/proc/17648/status:NSpid:	17648	32368	11	1
/proc/18426/status:NSpid:	18426	7307	1
/proc/1/status:NSpid:	1
/proc/23240/status:NSpid:	23240	8418	1
/proc/24140/status:NSpid:	24140	27491	1
/proc/24949/status:NSpid:	24949	1
/proc/24950/status:NSpid:	24950	2	1
/proc/25114/status:NSpid:	25114	27	1
/proc/25119/status:NSpid:	25119	32	1
/proc/25130/status:NSpid:	25130	43	1
/proc/25138/status:NSpid:	25138	51	1
/proc/25142/status:NSpid:	25142	55	1
/proc/25157/status:NSpid:	25157	70	1
/proc/25174/status:NSpid:	25174	87	1
/proc/25220/status:NSpid:	25220	133	1
/proc/25285/status:NSpid:	25285	194	1
/proc/25465/status:NSpid:	25465	8720	1
/proc/25486/status:NSpid:	25486	8738	1
/proc/25748/status:NSpid:	25748	8865	1
/proc/28404/status:NSpid:	28404	9387	1
/proc/28424/status:NSpid:	28424	9405	1
/proc/29141/status:NSpid:	29141	1
/proc/4960/status:NSpid:	4960	3564	1
/proc/7699/status:NSpid:	7699	1
/proc/8399/status:NSpid:	8399	30263	1
/proc/8759/status:NSpid:	8759	4802	1

The best approach for a LXD container is probably a mix of cgroup and proc, something like:
stgraber@castiana:~$ cat find-pid.sh
#!/bin/sh
for i in $(cat /sys/fs/cgroup/freezer/lxc/$1/tasks); do
    grep -q "NSpid.*	${2}$" /proc/${i}/status && echo ${i} && exit 0
done

exit 1
stgraber@castiana:~$ sh find-pid.sh ups-monitor 633
8754

That's still not ideal though because if you use nested PID namespaces, that'd still fail.

#!/bin/sh
CTN=${1}
PID=${2}

for i in $(cat /sys/fs/cgroup/freezer/lxc/${CTN}/tasks); do
    FIELDS=$(grep "NSpid.*$" /proc/${i}/status)
    set -- ${FIELDS}

    [ "${3}" = "${PID}" ] && echo ${i} && exit 0
done

exit 1

That version should be safe as it will only look at the first level of PID namespace.

I personally just tend to use "ps fauxww" which shows me a nice tree of processes under each container monitor process and makes it pretty easy to visually get what you want. But for a scripted approach, the trick above should work fine.
Closing this issue as there's no real LXD bug here :)

This gives me a starting point.
If I come up with anything useful, I'll post it.
Thanks!

Here's a quick way to surface out some info.

iotop -P -a -d 1

<< to select sort on DISK WRITE
After a few seconds an offender will surface, pid 6105 in my case.

cat /proc/6105/cgroup | grep freezer
4:freezer:/lxc/net12-jasites

So if mysqld is the iotop offender in question, this is a quick way to determine container name.

Got motivated a few minutes ago + figured out a crude way to accomplish this.
Looks like /proc/$pid/status contains NSpid (pid namespace correlations), so my clunky... hacked together in an hour script, takes a set of host pids + appears to correctly convert them to their container name + container relative pid.
net12 # lxd-pid<PHONE_NUMBER>8 1714
host=849450 lxd:net12-jasites=253094 command=/usr/sbin/mysqld
host=24668 lxd:net12-clients=996 command=/usr/sbin/mysqld
host=1714 lxd:net12-rmt-lowres=798 command=/usr/sbin/mysqld

Code is lipstick on a pig ugly...
https://davidfavor.com/private/lxd-pid.txt is the link.
Since pid namespace lookup is fairly easy, I'll revisit writing an lxd-top using PERL's Proc::ProcessTable to give some crude information about container resource usage, somewhat similar to what lxc-top use to provide.


[Backport 2.3] Logging: AWS Elasticsearch: Cannot get new connection from pool

2.3 backport for https://github.com/rancher/rancher/issues/21744

Rancher version: v2.3-head (05/14/20) commit id: 091316568
Same results mentioned here for versions v2.4-head and master-head.

Deployed an AWS ES Domain. (Domain should have enough EBS disk capacity for a long run)
Setup cluster and project logging with flush interval to 1 second. (Cluster should have enough disk space for a long run).
In a project deploy a web workload or any other docker container to generate logs and start monitoring the logs in Kibana in the ES Domain (Kibana is deployed automatically to analyze the logs).
Left the logging running for 8+ not able to reach the connection reload issue.

cluster.conf and project.conf keys in the rancher-logging-fluentd secret had the values:
reload_connections false
reconnect_on_error true
reload_on_failure true


feat: no hoisting

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Nginx Ingress Controller - Stats by country does not work

Hi,
the latest stats by country does not work. When i go to /nginx_status page there aren't any filters by country.
Thank you.

Did you enable it? (enable-vts-status in the configmap)

Yes i enabled it @pieterlange

@nottix I'm sorry for the delay. Fix in next version.

Thank you


Sort members in elections-phragmen genesis

Elections Phragmen importantly assumes that the Member list is sorted. However, construction of the storage item in genesis did not check that it was sorted.
This fixes that and adds a test :)
(It also repairs my sanity, took me a while to find what was messing up my benchmarks!)

This is a great catch, thank you!


New BUILD_ROOT not being respected

So, the first time I started my client, I had a typo in the BUILD_ROOT variable. I fixed it, killed the current running client, and restarted a new client with the correct value of BUILD_ROOT exported. The first time the client runs my job, it's fine. When I invalidate it to try again (I'm currently debugging my setup, so I'm just invalidating a job on a PR), it's reverting back to the old, mistyped value of BUILD_ROOT.
Any suggestions? Any other information I can provide? Thanks!

I should mention, this behavior is repeatable. I.e. I can kill the running client and start a new one. First time it runs the job, it has the correct BUILD_ROOT. The next time, it uses the "old" one. Clearly it's being cached somewhere, but not sure where.

I take it you are just running client.py?
I don't think it caches BUILD_ROOT anywhere...where are you setting it? On the command line or in .bashrc? Let me know what your command line is and I can try to reproduce it.

I'm just setting it in the environment: export BUILD_ROOT=<path>
The command I use for the client is:
./client.py --url https://femputer.eng.buffalo.edu:8000 --build-key<PHONE_NUMBER> --configs linux-gnu --name pbauman_client --insecure &

Hmm, I can't seem to reproduce it.
Where are you seeing it using the wrong BUILD_ROOT?
If you are using the scripts from civet_example_recipes then it should display what it thinks the build root is in the header of each step. Is it wrong there as well? Is it right at the beginning (like when you clone/update your repository)? Or after, like when building and it is referencing bad library paths or objects files?
Any custom scripts in civet_recipes that could be the culprit?

I see it as an error in the first step of the recipe, in particular when it's calling init_script I believe.
https://femputer.eng.buffalo.edu:8000/job/3/

/tmp/tmpG7CBZ2: line 123: cd: /femptuer/pbauman/civet_build_testing_root: No such file or directory
ERROR: exiting with code 1

I grepped through the scripts and I don't see any of them setting BUILD_ROOT:

[01:06:58][pbauman@femputer:/femputer/pbauman/civet_recipes/scripts][master] $ grep BUILD_ROOT *.sh
cleanup_build_testing_dir.sh:#REQUIRED: BUILD_ROOT
cleanup_build_testing_dir.sh:SUBDIR=$BUILD_ROOT/$FEMPUTER_BUILD_DIRNAME
cleanup_build_testing_dir.sh:cd "$BUILD_ROOT"
functions.sh:# Bad things can happen if BUILD_ROOT is not set
functions.sh:if [ -z "$BUILD_ROOT" ]; then
functions.sh:  echo "You need to set BUILD_ROOT"
functions.sh:  local b="$BUILD_ROOT/"
functions.sh:  local cwd=${p/#$b/BUILD_ROOT/}
functions.sh:  printf "Build Root: $BUILD_ROOT\n"
functions.sh:  export REPO_DIR=$BUILD_ROOT/$APPLICATION_NAME
functions.sh:    cd "$BUILD_ROOT"
make_build_testing_dir.sh:#REQUIRED: BUILD_ROOT
make_build_testing_dir.sh:SUBDIR=$BUILD_ROOT/$FEMPUTER_BUILD_DIRNAME
run_cmd.sh:REPO_DIR=$BUILD_ROOT/$APPLICATION_NAME

I only have one recipe at the moment and it doesn't set BUILD_ROOT.
Could this be cached somehow on the GitHub side?

Annnnnnd now the server isn't responding. Will report back in a few mins.

OK, I guess you probably want /femputer/pbauman/civet_build_testing_root.
I am not seeing anywhere where this could be cached. The client gets it scripts from the CIVET server and the client should only be accessing BUILD_ROOT from its local environment. I guess it could get overwritten locally but it would have to be in the last step of whatever recipe you are running. Do you set BUILD_ROOT in one of your recipe .cfg files?
Could you send the results of env from the terminal where you are launching the client?

OK, I guess you probably want /femputer/pbauman/civet_build_testing_root

Correct.

I am not seeing anywhere where this could be cached. The client gets it scripts from the CIVET server and the client should only be accessing BUILD_ROOT from its local environment.

Does the server maybe cache any of the variables anywhere that would be read by the client?

I guess it could get overwritten locally but it would have to be in the last step of whatever recipe you are running. Do you set BUILD_ROOT in one of your recipe .cfg files?

No. I only have one .cfg file in recipes. (https://github.com/ubaceslab/civet_recipes/tree/master/recipes)
I've tried the following.

Killed the running client and shutdown that terminal.
Killed the running server and shutdown that server.
Started a new terminal and started a new server in that terminal.
Started a new terminal and set valid value of BUILD_ROOT. Started a new client in that terminal.
Invalidated job. It reran with correct BUILD_ROOT up to the point of failure (Configure step, still trying to figure out what's wrong with my shell script that's causing a -15 exit code, no output produced).
Made changes to script, invalidated job.
Now failing because can't cd to old BUILD_ROOT from the terminal that died in step 2 (that had been unset and reset to a valid value before that).
Invalidated again. Now getting exit -15 on Bootstrap step (this is the first time this happened)
Invalidated again. Now getting exit -15 on Build step...
Invalidated again. Now failing because of bad BUILD_ROOT (the misspelled one that should've gone away...)
Invalidated again. Now getting exit -15 on Bootstrap step.

There were no changes to recipe or scripts between steps 7, 8, 9, 10, and 11, just invalidating.

Could you send the results of env from the terminal where you are launching the client?

This is from the new terminal started in step 4.
env_new.txt

Yeah, I don't even. I'm getting random behavior with each invalidate. Any clues about what error code -15 could be?
The nuclear option is rebooting the server, wiping out the current civet install, and starting from scratch, but it would be nice to try and understand what's causing this behavior.

Nothing seems wrong with your environment.
-15 is the result of being killed by a signal (15 or SIGTERM).
A quick messy debug option would be to sprinkle your scripts to have echo $BUILD_ROOT in various spots to try to track down when it actually changes.
I am going to clone your repo and go through your scripts real quick to see if anything pops out.

I put a print statement at the top of functions.sh and it looks like BUILD_ROOT is corrupted right from the beginning:

/femptuer/pbauman/civet_build_testing_root
Date: Mon Dec 12 16:16:56 EST 2016
Machine: femputer.eng.buffalo.edu
LSB Version:	:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID:	CentOS
Description:	CentOS release 6.8 (Final)
Release:	6.8
Codename:	Final
Cannot find MOOSE Package version.
Build Root: /femptuer/pbauman/civet_build_testing_root
Trigger: Pull request
Step: Load GRINS Modules (0)

I'm using Lmod. Does Lmod do some weird caching business? Is each step in the recipe starting a new environment?

There must be something funky happening between Lmod and the shell. I'm printing out env at the top of functions.sh and it's (occasionally...) showing the bad BUILD_ROOT value.

I have seen weird Lmod caching behavior with environment variables but it is usually solved by quitting the current terminal and starting again.
I notice that you are loading modules in the scripts. I don't think that will work like you think it should. Each step is run in its own process so it shouldn't carry over (which is why I find it weird that BUILD_ROOT is getting set by a child process).
If your recipes need a certain environment then the environment should be setup to how you want it in the terminal that is going to run the client. That way the environment is inherited from the parent process (the client).
If you need multiple different environments then you can use multiple build configs but then you might want to look at our inl_client.py which is setup to handle multiple different module environments.
Not the cause here probably, but I also noticed that you don't clear out grins-devel before you start everything. You will probably want to do that since you can't rely on the cleanup step always executing.

I have seen weird Lmod caching behavior with environment variables but it is usually solved by quitting the current terminal and starting again.

Yes, this was really perplexing.

I notice that you are loading modules in the scripts. I don't think that will work like you think it should. Each step is run in its own process so it shouldn't carry over (which is why I find it weird that BUILD_ROOT is getting set by a child process).
If your recipes need a certain environment then the environment should be setup to how you want it in the terminal that is going to run the client. That way the environment is inherited from the parent process (the client).

Thanks for the info. I'd started inferring this through my trial and error. :)

If you need multiple different environments then you can use multiple build configs but then you might want to look at our inl_client.py which is setup to handle multiple different module environments.
Not the cause here probably, but I also noticed that you don't clear out grins-devel before you start everything. You will probably want to do that since you can't rely on the cleanup step always executing.

I'd planned on controlling the environment with the scripts+module system - any pointers to what I should look at in the inl_client.py?

After rebooting the node and restarting the server and client, everything seems to be working now: I've invalidated twice, I'm not getting -15 exit messages or invalid BUILD_ROOT values. Just need to fix LD_LIBRARY_PATH in one of the modules (because PETSc changed stuff again).
I guess this is good, but it would be nice to understand really what happened. Is there any chance that screen would be interfering? I was running the CIVET server and client within a screen session.

I don't see screen could have affected it but then I can't really see how Lmod screwed things up so badly. I bet it has something to do with Lmod. It seems to do some magic under the hood that I haven't gotten around to trying to figure out.
Are you going to be using multiple different module configurations? If not then you could use something like what is in civet/client/scripts/control.sh to setup the environment and run the client. We do that on a couple machines that only have one configuration.
Regardless, I will update the wiki on how to setup the inl_client.py

I don't see screen could have affected it but then I can't really see how Lmod screwed things up so badly. I bet it has something to do with Lmod. It seems to do some magic under the hood that I haven't gotten around to trying to figure out.

OK, hopefully I won't make anymore typos. :P Will report in if I ever figure it out (unlikely).

Are you going to be using multiple different module configurations?

Yes? I guess I'm not quite sure what you mean. I plan to several recipes that will build with different compiler options on the same PR, e.g. dbg vs. opt libMesh. I'll have different modules for the dbg build vs. the opt build. But I can easily just load the different modules in each of those recipes.

If not then you could use something like what is in civet/client/scripts/control.sh to setup the environment and run the client. We do that on a couple machines that only have one configuration.

OK, thanks, I'll have a look.

Regardless, I will update the wiki on how to setup the inl_client.py

Awesome, thanks!

So you have different modules for debug vs opt? We don't do that much here, we just have different compiler targets or configuration targets. Like linux-gcc, linux-clang, linux-intel, etc. Each one of those loads a different set of modules. But we build libmesh every time in dbg/opt every time.
For your case you could have a linux-gcc-opt and linux-gcc-dbg and use the inl_client.py to poll for jobs on those two configurations.
However, loading modules in an individual step should work as well. You will just need to make sure the correct modules are loaded in each step (make sure to do a purge first!). Going this route you probably wouldn't need the inl_client.py.

I updated the wiki for the INL client . Please let me know if there is something that isn't clear.

Sorry I was slow here (travel+end of semester). This is all clear for me now and my server and client are running smoothly so far. Thanks very much for the very quick and helpful comments and updates!

Great! Let us know if you run into any problems or need something added.


Fix a compile error

This patch fix following compile error.
signal.c:176:6: error: 'for' loop initial declarations are only allowed in C99 mode
for (int i = g_signal_dispatch->signal_to_eid_set->size - 1; i >= 0; i--) {

The minimum supported Ubuntu version of the SDK is 16.04. And I believe the default version of GCC for Ubuntu 16.04 should completely support C99. Is that right?

The minimum supported Ubuntu version of the SDK is 16.04. And I believe the default version of GCC for Ubuntu 16.04 should completely support C99. Is that right?

Not using ubuntu environment, but GCC is indeed a lower version 4.8.5.

lgtm. @volcano0dr ?

@uudiin thanks!  @dingelish OK,  merge this PR.


docs: Add README File

Add readme file to the repository
just like this one: click here

@soorya-u can you work on this mean while

@KushalJetty Your next task

ill work on this


Added AlpineLinux

This PR adds the support for Alpine Linux. Unfortunately currently only the edge version with the testing repository enabled can be used to install leveldb and rocksdb.
The alternative would be to build both of them manually, which might increase the disk size the docker container will use afterwards.

Looks good to me otherwise 👍

Thanks, I'll test it and merge if it succeeds.

If you use Docker than this might be quite helpful:
FROM alpine:edge

RUN apk update && apk add bash git
RUN mkdir -p /log /db /env ~/service ~/scripts/electrumx
RUN wget https://raw.githubusercontent.com/mettke/electrumx-installer/master/bootstrap.sh -O -  | bash
RUN apk add daemontools
RUN cp -R /tmp/electrumx/contrib/daemontools/* ~/scripts/electrumx
RUN mv ~/scripts/electrumx/env/* /env/
RUN rm -rf ~/scripts/electrumx/env
RUN ln -s /env ~/scripts/electrumx/env
RUN chmod +x ~/scripts/electrumx/run ~/scripts/electrumx/log/run
RUN sed -i '$d' ~/scripts/electrumx/log/run
RUN sed -i '$a\exec multilog t s500000 n10 /log' ~/scripts/electrumx/log/run
RUN ln -s ~/scripts/electrumx  ~/service/electrumx
RUN rm -Rf /tmp/*

VOLUME /db /log /env

CMD ["bash","-c","svscan ~/service"]

HEALTHCHECK CMD svstat ~/service/electrumx || exit 1

Hey @mettke
I'm currently trying to add Python 3.7 support in the python3.7 branch. Any idea how to install Python 3.7 on Alpine? Their repo doesn't seem to contain it yet.

There is the official python alpine container at https://hub.docker.com/_/python/ which contains a 3.7 container for alpine. Might be exactly what you're looking for

That doesn't really help as I don't really want to add code to compile Python from source. But thanks anyway!


support for oneOf and allOf added

This PR pertains to issue #10 ,
The following changes have been made

support for oneOF has been added. I have created a oneOFChoiceWidget, which is used to select which schema to use in case of a oneOf schema
support for allOf has been added too. I have added an allOf schema which is used to generate the schema for an allOF situation
I fixed an issue with the complile schema function. It could not compile nested $refs but that is fixed now.
added the two new widgets to the widgets index.js
added the widgets support by checking in the renderfield guessWidget method
added check of enum_titles inside options property for choiceWidget

@nacmartin Looking forward to get your reviews so as to get this code good enough for merging soon. any changes are welcome.

Thanks @gastonche! I did some changes to both of them, because the values being stored were nested in objects with key null, such as
{"null": {"null": {
   "name": "john",
   "age": 54
}}}

instead of
{
   "name": "john",
   "age": 54
}

Since oneOf and allOf can appear in different positions of the schema, there may be very well some edge cases that are still broken, but as this change affects only users of oneOf and allOf that were not supported before at all, I think that is pragmatic to merge them and improve the support later, instead of trying to break it and make small improvements for weeks before merging anything.


Inconsistency in formatting of multiline conditional statements

With respectsExistingLineBreaks set to true
let a = this ||
    that
// after formatting becomes
let a = this || that

and
let a = this
    || that
// after formatting becomes
let a =
    this
    || that

Why are newlines respected in the second case but not the first

Synced to Apple’s issue tracker as rdar://140672947


use nested folder

use nested folder

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


Update target to net8

GitHub Issue: #

Proposed Changes

Target recent sdk. Sample head removed to be rebuilt with latest structure

What is the current behavior?

What is the new behavior?

Checklist
Please check if your PR fulfills the following requirements:

[ ] Documentation has been added/updated
[ ] Automated Unit / Integration tests for the changes have been added/updated
[ ] Contains NO breaking changes
[ ] Updated the Changelog
[ ] Associated with an issue

Other information

If possible, use conventional commits


vectorize calculation of cross sections over partial wave S-matrices/scattering amplitudes

In xs.elastic module


Ensure location types fits all missions

Make sure there is no dependency on distiction of advisor & principle (their counter parts) locations. Assume the same locations can be the shared amongst them.
Automatically migrate positions to virtual & pinpoint locations

Automatically migrating location types is discussed at DSU. It is decided not to make any change at database migration file. Deployed application admins should correct their locations's type manually via sql statements if the current migration policy is not suitable for their application.


Bump dcos-metrics

High-level description
What features does this change enable? What bugs does this change fix
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-2360 Metric names can begin with numbers in dcos-metrics Prometheus endpoint
DCOS_OSS-3304 Metrics emitted by containers do not contain tags from labels
DCOS-37452 Increase the mesos agent response timeout for dcos-metrics
DCOS-37451 Filter cosmos bookkeeping tags from metrics
DCOS-38083 Statsd timers are reported incorrectly by dcos-metrics

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): [example](https://github.com/dcos/dcos-metrics/compare/fe764a8d79fdb7a606406109f2293b86e10491cd... 20b132908ffdb0985bedb25653871e0c680d2dcb)
[x] Test Results: link to CI job test results for component
[x] Code Coverage (if available): link to code coverage report

Closing this in anticipation of ✨exciting 1.12 updates ✨


add: an example on fine-tuning segformers.

Colab Notebook: https://colab.research.google.com/drive/1nJidirvsRgWZl2tNHFma1pArBCx87anQ?usp=sharing
Cc: @RocketKnight1 @amyeroberts

Looks good to me! Quick question, is ignore_mismatched_sizes=True needed because the number of segmentation classes in this task is different from the original checkpoint?

Looks good to me! Quick question, is ignore_mismatched_sizes=True needed because the number of segmentation classes in this task is different from the original checkpoint?

I assumed so, yes.

@sayakpaul LGTM! Just added two ultra nits on the descriptions

@amyeroberts thanks! You would need to sign the CLA.

@fchollet thanks!
I have applied your suggestions and have also added an architecture diagram. PTAL.

@fchollet thanks! Added the generated files.
Over to you.


[5.6][swift-stdlib-tool] Fix finding sibling directories

When used without passing --source-libraries, this tool fetches its
current path and uses that to find the directories of the swift
libraries near it.
Since https://github.com/apple/swift/pull/39216 it was searching the
nearby directories recursively, and only for files, instead of just
looking at 1 level, only for directories. Because of this it would never
discover path/to/lib/swift-5.0/... because it was only looking for
files.
This fixes this issue with a new function, and renames the previous
function to be more explicit for the other use case that does want that
behavior.
(cherry picked from commit d1eabf182c7c1abf36b28b111ec98c0ca5168efe)

Nominated in rdar://88610842
@swift-ci test

Thanks all!


ci(github-workflows): launch CI on PR & push for all branches

Before this change the only time the CI would get executed was when
a pull request was submitted against the $DEFAULT branch. After this
the CI will run for every commit and pull request that is issued against
the any branches.
The specific reason for this change is that we introduced a new branch
called dev which can be used to provide early access to pending changes
that may or may not be stuck in the review queue for longer periods of
time. Of course there's an additional overhead in maintaining this
dev branch by way of cherry picking and rebasing, but this is minor
compared to the positive effects it can bring to the community.
Fixes #434
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>

it is possible to push the code in the draft state to the branch, and it would be troublesome in such a case.

@takeutak Could you please elaborate on how does it become troublesome? Would the CI running a draft branch and failing block you somehow from doing something?

it is possible to push the code in the draft state to the branch, and it would be troublesome in such a case.

@takeutak Could you please elaborate on how does it become troublesome? Would the CI running a draft branch and failing block you somehow from doing something?

Please let me confirm one. In this suggestion, not only pull-request but also pushing codes will be targets for CI checking system, is it right?  I think I have a lot of trouble when we make a draft code which does not work at this time.
As a question, does this change increase the time required for git push? If the code check increases the time significantly, I think it is better to limit the target branch to main and dev.
If the time required for pushing does not change from the current situation, I think there is no problem.

Please let me confirm one. In this suggestion, not only pull-request but also pushing codes will be targets for CI checking system, is it right?  I think I have a lot of trouble when we make a draft code which does not work at this time.
As a question, does this change increase the time required for git push? If the code check increases the time significantly, I think it is better to limit the target branch to main and dev.
If the time required for pushing does not change from the current situation, I think there is no problem.

not only pull-request but also pushing codes will be targets for CI checking system, is it right?

@takeutak That's right. I think it's great to receive feedback about failing CI as early on as possible versus only getting it once the PR has been opened (my personal take).

As a question, does this change increase the time required for git push?

@takeutak It should not. The time your git push takes should not be affected by this change.

If the code check increases the time significantly, I think it is better to limit the target branch to main and dev.
If the time required for pushing does not change from the current situation, I think there is no problem.

@takeutak Agreed: If that were true, I would agree, myself as well regarding it being a problem. To the best of my knowledge this is not the case though. Definitely has never been the case in my workflows, ever, but I also do not want to presume that other people do the exact same things as I do so if somehow this change ends up slowing you down in any way, then please do let me know the details because that's definitely something we would need fix were it to happen.

not only pull-request but also pushing codes will be targets for CI checking system, is it right?

@takeutak That's right. I think it's great to receive feedback about failing CI as early on as possible versus only getting it once the PR has been opened (my personal take).

As a question, does this change increase the time required for git push?

@takeutak It should not. The time your git push takes should not be affected by this change.

If the code check increases the time significantly, I think it is better to limit the target branch to main and dev.
If the time required for pushing does not change from the current situation, I think there is no problem.

@takeutak Agreed: If that were true, I would agree, myself as well regarding it being a problem. To the best of my knowledge this is not the case though. Definitely has never been the case in my workflows, ever, but I also do not want to presume that other people do the exact same things as I do so if somehow this change ends up slowing you down in any way, then please do let me know the details because that's definitely something we would need fix were it to happen.


tags in headers results in unexpected behaviors in table of contents

This is really two and a half problems.
Regardless of the tag, the header id (and the hash portion of the permalink) is truncated. Either to the content of the tag, if the tag is appears before before any text, or to the text preceding the first tag.
Certain tags appear in the toc titles, like a or code tags, while others, like strong and em, don't.
Bonus potential Tera bug, striptags doesn't work to strip the appearing tags.

Any chance you can do a PR some failing tests or just pasting examples in this issue?

I'll take a look at creating a PR if time becomes available.
Regarding examples, create a page with the following markdown content.
## header with `code`
`id` will be "header-with"
`title` will be "header with code"

## [anchor](google.com) in header
`id` will be "anchor"
`title` will be (approximately) "anchor in header"

## **bold** and *italics*
`id` will be "bold"
`title` will be "bold and italics"

Additional information, and a question.
The following added to components/rendering/tests/markdown.rs in a new test
    let res = render_content(r#"
## header with `code`

## [anchor](https://duckduckgo.com/) in header

## **bold** and *italics*
    "#, &context).unwrap();

    let toc = res.toc;
    println!("{:#?}", toc);

Running cargo test -- --nocapture from components/rendering produces
[
    Header {
        level: 2,
        id: "header-with",
        title: "header with code",
        permalink: "https://mysite.com/something#header-with",
        children: []
    },
    Header {
        level: 2,
        id: "anchor",
        title: "anchor in header",
        permalink: "https://mysite.com/something#anchor",
        children: []
    },
    Header {
        level: 2,
        id: "bold",
        title: "bold and italics",
        permalink: "https://mysite.com/something#bold",
        children: []
    }
]

Clearly the permalinks are broken, but here's the question. What is the expected behavior of the title?
On further consideration retaining HTML tags might be the more sane behavior. In which case is the last example the one behaving incorrectly?

I think removing the HTML tags would be the saner options for the TOC.  For example, if you have a link wrapped in a link like the second one, it's not going to work well.

You're right about nested anchors, and although it might be reasonable for TOC links to retain header tags, it's probably much simpler to strip them, and not excessively surprising.
I'd like to try a PR to fix this issue if you haven't started working on it.
p.s. There is no Tera bug, striptags does work as expected if you first use safe.

I'd like to try a PR to fix this issue if you haven't started working on it.

Go for it! Don't forget to do the PR on the next branch.


Admission flow reject

Fix: https://github.com/kyma-project/warden/issues/71

/test all

/retest


Light/Dark Mode Toggle Button Incorrectly Positioned in Footer

The Light/Dark mode toggle button is currently placed in the footer of the website. Ideally, this button should be located in a more accessible area, such as the header or navigation bar, to enhance user experience. This change would make it easier for users to switch between themes without needing to scroll to the bottom of the page.

I would like to fix it, if you assign me under gssoc-extd

Please assign this issue to me.

@Hamza20203064 There isn't any light/dark mode toggle button implemented in my project. Could you please double-check if you might have raised the issue in the wrong repository?

Sorry for the confusion. I am going to close both issues that I had raised.


inventory weight unit conversion

The weight unit for the items in the actor's inventory aren't changing to kg (it's the standard unit for the brazilian edition) despite it being used as the default unit in the GCS sheet.

Closing.   This issue is a duplicate of https://github.com/crnormand/gurps/issues/188 (which we haven't gotten to yet)


dogecoin/docker repository

Hello guys,
While exploring GitHub, I found your repository. Just a message to let you know there is currently an initiative to provide a Docker Hub implementation at https://github.com/dogecoin/docker.
Work is still in progress, but a working Dockerfile/entrypoint to build an image manually is already available, it may facilitate your work !
It's already functional and more complete : cross architecture (Debian only), arguments as environment variables, checksum verifications, user permissions... See docs in PR https://github.com/dogecoin/docker/pull/13. We're actually working on tests, some extra work is needed to be ready for Docker Hub, but it's on the way :)
And of course, any help is welcome <3 !

Thank you for bringing this to my attention! I've added myself as a watcher to that repo, long term I'd much prefer to use the official repo instead of building our own.
I've added a notice to the readme to point to the official repo -- thanks again!


[en-GB]: missing object bytes for language en-GB

I got error with partial stacktrace below:
TypeError: Cannot read property 'binarySuffixes' of undefined
    at formatting.js:204
    at formatting.js:202
    at p (formatting.js:93)
    at Object.format (formatting.js:815)
    at e.value (numbro.js:40)

When looking a bit deeper, I dug this out: languages[en-GB].bytes is undefined

:information_source: I import and register language en-GB from numbro package:
import numbroEN from 'numbro/languages/en-GB';
...
numbro.registerLanguage(numbroEN);

Thanks! Indeed, it appears that those where implemented only in french (language used by the contributor) and en-US (language used by the tests).
I will patch it so that there are default values for every languages.

@all-contributors please add @seedy  for bug


Add ES test for CFE_ES_BackgroundWakeup

CCB:2021-08-11 APPROVED

Add call for background wakeup

Originally posted by @astrogeco in https://github.com/nasa/cFE/issues/1716#issuecomment-896980485
@skliper or @zanzaben can you flesh this out?

@nmullane - can you take this one?

Yeah, I can work on this.


feat(ui): add config slice, configuration default values

add configSlice to hold "application config"

the slice state is of type AppConfig, which is exported.
"application config" refers to things that are generally set at startup and cannot be changed. contrast with "system settings" which are user-facing.
this includes things like disabled tabs, disabled features, and generation parameter config (min, max, initial value, etc).
sensible defaults are in place for the core SD parameters.
any config provided to App via its optional config prop will be merged in over the defaults.
main SD input components are updated to handle this.

misc internal fixes surrounding this change
fixes for the shift modifier that is used to handle the fine/coarse step values of various parameters

also added delete functionality to UI


Floating point type issue when computing extract images patches gradient

I was using tf.extract_image_patches when I ran into this issue.
It seems sp_mat here becomes a 32 bit floating point number as the sparse tensor inherits the floating point type from the values argument. If one is using float64 and the gradient is float64 computing the jacobian on the next line will result in the error "TypeError: Input 'b' of 'SparseTensorDenseMatMul' Op has type float64 that does not match type float32 of argument 'a_values'".
Inheriting the floating point type from the gradient should fix the issue.

I signed the license agreement @googlebot

@kekeblom thank you for the fix!


Try changing the CORS permission of the bucket

Let's have this to be optional (default true) since it is required only for loading cross-origin assets.

I'd like to work on this issue by creating a new command line function to set the CORS configuration to the bucket. I don't think it should be a turn on/off option as we need info provided by user (domains/subdomains, http methods [that are mandatory] and allowed-headers.
Maybe add to the cdn.php config file an array with AWS CORSConfiguration structure and then allow user to choose run or not it with artisan.
any other toughts, @Mulkave @Mahmoudz ?

@filipegar sorry for the late reply, please go ahead! PRs are always welcome 😄
A separate command sounds good, though requiring the understanding of the CORSCobfiguration structure is a bit of a hassle, u less we provide a set of user-friendly methods to represent commonly used ones.
What do you think?


Should keyed v-for array refs be ordered?

Version
3.1.2
Reproduction link
vue 3
Steps to reproduce

open sandbox
open console
click reverse
see first and second refs log

What is expected?
second log should be:
[

bar
,

foo
,
]

What is actually happening?
second log still be:
[

foo
,

bar
,
]

Ref: https://v3.vuejs.org/guide/migration/array-refs.html

I would say having a function gives you the flexibility of ordering the nodes however you want but I'm not sure if this was intended

I would expect that the ordering of refs received would be stable between renders (and between Vue2 and Vue3).
Without it being stable it makes things like "focus the first ref in the list" quite difficult as the ordering will reverse after the initial render.
Here is a simplified repro example that shows that re-renders reverse the order of the refs compared to the actual rendered content.
Repro example on SFC Playground

The problem originates from the fact that patchKeyedChildren iterates in reverse-order
https://github.com/vuejs/vue-next/blob/ba89ca9ecafe86292e3adf751671ed5e9ca6e928/packages/runtime-core/src/renderer.ts#L2049-L2051
This means that any setRef calls that occur in patch that rely on the v-for : key iteration done in this loop will end up being provided to :ref="..." functions in reverse order on patch-renders compared to initial-renders.

This is actually pretty problematic for us in terms of migrating to Vue3. We have lots of accessibility functionalities that rely on being able to properly traverse our $refs for keyboard navigation, focus transferring, etc.
Without a stable, in-order sort for these refs.. we're kinda stuck.

You may be able to work around this problem via passing the intended index of the ref to your handleItemRef and using it to set the ref into the array instead of relying on .push(ref).
The follow example highlights how this could be implemented
<template>

 handleItemRef(idx, ref)">
      {{item.name}}

</template>

You can actually sort the elements yourself, may be a viable workaround for the time being:
    onUpdated(() => {
      console.log(sortElementsByPosition(itemRefs));
    });

    function sortElementsByPosition(elements) {
      return elements.slice().sort((a, b) => {
        return a.compareDocumentPosition(b) & 2 ? 1 : -1
      })
    }

Interesting. Didn't know about Node.compareDocumentPosition.

As a note, I'd be happy to PR a solution to this issue, however, given the fact that the internals of the patch system are built intentionally with reverse-order patching for optimization I've not touched the code yet as it isn't clear how the project might want to address this.
Any thoughts or guidance here would be appreciated.

Bump

You may be able to work around this problem via passing the intended index of the ref to your handleItemRef and using it to set the ref into the array instead of relying on .push(ref).
The follow example highlights how this could be implemented
<template>

 handleItemRef(idx, ref)">
      {{item.name}}

</template>

Note, this cannot be done when dealing with the Vue3 Migration Build's support of V_FOR_REF as the developer isn't dealing with the :ref="<function>" api yet.
As such, this ordering of refs for migration users will continue to be invalid.

@iendeavor @DV8FromTheWorld
Don't rely on the ordering of :ref="someFunc"
It is just something uncontrollable. (see #4646)

After reading through #4646 I don't agree to be honest.
Your problem was caused by, frankly, not properly handling the reactivity system in Vue.
The same problem would have occurred for any computed / reactive situation, it just might not have been obvious in terms of the result. Given that you aren't setting up erroneous reactive dependencies it will be fine. And if you do need access to do comparisons like that, you can sidestep the reactivity via variable._value

Bumping the question above, although after refreshing the initial reproduction it doesn't seem to be resolved.


Missing assets for escoria book

Hi!
First of all, thanks for the amazing work with Escoria. The book is just perfect to get started with point and click games and Godot :)
I'm not sure if this is right place to ask. I'm looking for the example assets that are mentioned in the escoria book, specifically in these pages:
https://fr.flossmanuals.net/creating-point-and-click-games-with-escoria/about-the-example-game/
https://fr.flossmanuals.net/creating-point-and-click-games-with-escoria/creat-your-scene/
Any idea of where they can be found?
Thanks,
Ignacio

the book assets are in the flossmanuals repo:
https://github.com/flossmanualsfr/escoria
On 3 October 2016 at 09:18, Ignacio Huerta<EMAIL_ADDRESS>wrote:

Hi!
First of all, thanks for the amazing work with Escoria. The book is just
perfect to get started with point and click games and Godot :)
I'm not sure if this is right place to ask. I'm looking for the example
assets that are mentioned in the escoria book, specifically in these pages:
https://fr.flossmanuals.net/creating-point-and-click-
games-with-escoria/about-the-example-game/
https://fr.flossmanuals.net/creating-point-and-click-
games-with-escoria/creat-your-scene/
Any idea of where they can be found?
Thanks,
Ignacio
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/escoria/issues/3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVmPWLSZmvUwR8QK8O-Wcabyqxd-9gWks5qwPKIgaJpZM4KMhFV
.

Nice, I didn't know about it. I added the link to the README: 4f36171
If it's not linked in the manual itself yet, it should probably be added.
Also, maybe the repo could be renamed to escoria-in-daiza to make it clearer that it's a full game and not just a fork of escoria?

Thanks so much, I will add the link to the book myself :)

Sorry to be a pain: I have realised that in the book two game projects are mentioned:

an example game called "first quick game"
another game called Escoria in Daïza to show some cool feature of Escoria and make us this week more fun

Then it says about the "first quick game":

To start we prepared some files for you :

the assets so that you can follow this section with the same ressources and get at the end something similar
the first quick game complete project done so that you can have a look at the files if necessary

Is that "asset package" available somewhere? If not, that's no problem, all assets can probably be found and extracted from the "Escoria in Daïza" repository. I would just like to correct the book, so future readers are not confused :).
Thanks again!

I don't remember.. someone might know in the issue tracker for that
repository..
On 3 October 2016 at 14:17, Ignacio Huerta<EMAIL_ADDRESS>wrote:

Reopened #3 https://github.com/godotengine/escoria/issues/3.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/escoria/issues/3#event-810597862, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGVmPcg31T-KlON2ldcqWqIuPj01_gzYks5qwTiOgaJpZM4KMhFV
.

Ok, I'll ask there, thanks!


[Feature] Flipping single neurons

Hi, is there an easy way to flip the neuron actor (neuron morphology loaded from an SWC file) so the soma is in the opposite hemisphere.
A way to flip any actor to the opposite hemisphere would be very much appreciated!
Alternatively, I would need to load the swc and slip it and I cannot find an easy way with morphapi to flip the morphology either.
Thanks!

Hi @CaroniLab, thank you for the suggestion!
We've implemented a new method to flip actors in brainrender v2.1.15, you can update with pip install brainrender -U.
Please see https://github.com/brainglobe/brainrender/blob/main/examples/mirror_actors.py for example usage.


Touch Sensor Interaction

Add a connection between the touch sensor, actuators (motors), and belly editing.

Added haptics support for WoZ in https://github.com/mayacakmak/emarsoftware/pull/79. Touching will also make a purr sound outside of WoZ, but the robot will tilt its head only in WoZ.
Next step would be to implement EUP functionality for haptics


support kafka as eventbus/store

I just recently learned that my approach of connecting command service and query service via rabbitMq won't allow me to use replay on query side due to the nature of the rabbitmq.
So my feature "request" would be to support kafka as an eventbus (and also store). Are there any plans so far?

see https://groups.google.com/forum/#!topic/axonframework/9QS-NO8Cdi8

I can take this issue, already started working on adding Kafka as an Event Bus .

Where are you with this one? Any plans to see Kafka Event Bus any time soon?

@petriapaf Publishing and consuming messages from Kafka is done. In upcoming days, will focus on consumer rebalancing and refactoring. Hopefully we will have it soonish

@abuijze the YouTube link appears broken. Is the rationale for "the design of Kafka doesn't seem as fit for Event Sourcing" documented elsewhere?

@caindy I can't point you to the right YouTube vid (as I'm unsure which Allard was referring too), but this read why Kafka is not for Event Sourcing is a good one to check out as well.

Hello, I still thinking kafka can be used for that. Just that „event-sourcing“ has to be interpreted as publishing Snapshot-events.
When a command handler fires an event, this event can be added to kafka by a kafka producer. The event however would contain the the status of the aggregate, as well as the original intention (command-name, command-id).
This aggregate snapshot event can then be consumed by a consumer group to persist the last status of the aggregate. We could use a DB, or Kafka Streams KTable for that.
The command handler then would load the repository object from this DB using repository.load(...).
Strictly speaking, that’s not the „event-sourcing“ definition of Axon, so maybe you would not use Event-Sourced Aggregates.
The benefit however of this approach is, that you rely on kafkas durability, and low-latency.
Just my 2 cents

Firstly I'd like to point this is not exclusively Axon's definition of Event Sourcing.
Secondly, the suggested solution is, as you point out, not really Event Sourcing either. This approach seems to use Kafka a a state storage mechanism, but rather then storing it once you are storing the entire Aggregate on each command being handled + the actual command. I'd argue that state storing the aggregate is not identical or resembles Event Sourcing, as you're now not working of of deltas/events but complete possible versions of the end product.
Taking these suggestions, that thus not make it an EventStore, but a regular aggregate Repository.
I trust in you that the solution you sketch could work as a Kafka version of an aggregate Repository.
We do agree that Kafka has very nice benefits we can and should leverage though, don't get me wrong there. That is exactly why as of Axon 3.3 (in issue #573) you can use Kafka as a StreamableMessageSource. Do note that is thus still not providing it as a Kafka version of an aggregate Repository however, but as a way to receive events in a distributed set up.

Closing this request as the PR #573 introduces Kafka as a StreamableMessageSource into Axon 3.3.

Axon 3.3 provide support for Kafka as event bus.
But adding support for Kafka as event store will be a great feature. Problem is performance to load an aggregate from its identifier as topics in Kafka should be by aggregate type and so include events of all aggregates of a topic. But to solve this problem, we can load current state of an aggregate from kafka local store : this is a king od snapshot.
Example in this article : https://dzone.com/articles/event-sourcing-with-kafka
It would be great to have complete Kafka support as it is a powerful in a microservices architecture, as detailed in this serie : https://www.confluent.io/blog/data-dichotomy-rethinking-the-way-we-treat-data-and-services/

Thank you for your input @fredgate, I can assure you we will take every suggestion serious.
We currently still remain with the stand point that Kafka is a great event bus, but not so much a great solution for event sourcing, as is for example pointed out here.
If anything within this space changes so that it makes sense to introduce an Aggregate Repository implementation like I commented earlier, we will definitely open up this ticket.

Tanks @smcvb for your reply.
I knew the article that you mentioned, but it is quite controversial and not necessarily impartial as it was written by the author of serialized.io, a potential competitor of Kafka.
The main problem with Kafka is to load current state of an aggregate from its past events. Kafka will not work well if a topic is created by aggregate, so the best solution is to create a topic by aggregate type. So to retrieve events of an aggregate, we could browse all events of all aggregates and filter these belonging to the specified aggregate. Of course its not pratical. The good alternative, that is not suggested in the article, is to build a local table from the stream of events and so to directly have current state of aggregates.
So a implementation of storage for Kafka could append events to a stream and retrieve current state (but not past events) from the local table.
Kafka has so many advantages like :

write / publish atomicity
streams : easy to add new services that can replay events
exactly one guarantee
public / private topics
schemas (avro)
services load balancing...


Does this plugin works with Rhino Compute?

I've trying to import from Grasshopper using a C# script to do it.
It works fine when using Rhino but through Rhino Compute the import comes false.
Has anybody successfully imported through Compute?
I am doing something like this
var Filepath = "/some/file/path.glb";
using( var doc = RhinoDoc.CreateHeadless(null) ){
    Boolean result = doc.Import(Filepath); // `result` comes `false` when using through compute but `true` on Rhino
}

Hi, it should work with compute. I couldn't tell you off the top of my head why it wouldn't. This repository is for glTF IO plugins that ship with Rhino 8. I'm guessing your compute instance is Rhino 7 which doesn't include these plugins.

Oh my! I didn't realize that. Yes, we are running on Rhino 7.
But how come this plugin works fine with Rhino 7 when running "headfull" instead of on Compute?
Nevertheless, thank you for the answer!

Can you paste the system info for both here?

It is an r6i.xlarge EC2 instance running the latest Windows Server they have.

I mean copy the output of the SystemInfo command in Rhino. I wanna see what plugins you have installed

Oh I see.
There you go, but it doesn't show any plugins even though I have them installed.
Rhino 7 SR34 2023-9-24 (Rhino 7, 7.34.23267.11001, Git hash:master @ a37d83041828484840f2448d5b3e3770e46694f9)
License type: (null), build 2023-09-24
License details: Cloud Zoo

Windows 10 (10.0.20348 SR0.0) (Server) or greater (Physical RAM: 31Gb)

Computer platform: DESKTOP (Hosting Remote Desktop session)

Standard graphics configuration.
  Primary display: Microsoft Remote Display Adapter (Microsoft) Memory: 0MB, Driver date: 6-21-2006 (M-D-Y).
    > Remote Desktop display device with 16 connection(s)
        - Windows Main Display using connection #0
  Primary OpenGL: GDI Generic: Microsoft Corporation. OpenGL Ver: 1.1.0
    > No graphics device is being used for OpenGL

Secondary graphics devices.
  Microsoft Basic Display Adapter (Microsoft) Memory: 0MB, Driver date: 6-21-2006 (M-D-Y).
    > External USB display device with 0 adapter port(s)
        - There are no monitors attached to this device!

OpenGL Settings
  Safe mode: Off
  Use accelerated hardware modes: On
  Redraw scene when viewports are exposed: On
  Graphics level being used: OpenGL 0.0 (primary GPU's maximum)

  Anti-alias mode: 4x
  Mip Map Filtering: Linear
  Anisotropic Filtering Mode: High

  Vendor Name: Microsoft Corporation
  Render version: 0.0
  Shading Language: Not supported
  Driver Date: (null)
  Driver Version: (null)
  Maximum Texture size: 1024 x 1024
  Z-Buffer depth: 32 bits
  Maximum Viewport size: 16384 x 16384
  Total Video Memory: n/a

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
  C:\Program Files\Rhino 7\Plug-ins\Commands.rhp	"Commands"	7.34.23267.11001
  C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp	"WebBrowser"
  C:\Program Files\Rhino 7\Plug-ins\rdk.rhp	"Renderer Development Kit"
  C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp	"RhinoScript"
  C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp	"IdleProcessor"
  C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp	"Rhino Render"	7.34.23267.11001
  C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp	"RDK_EtoUI"	7.34.23267.11001
  C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp	"Renderer Development Kit UI"
  C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp	"Snapshots"
  C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp	"Alerter"
  C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp	"RhinoCycles"	7.34.23267.11001
  C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp	"Toolbars"	7.34.23267.11001
  C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp	"3Dconnexion 3D Mouse"
  C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp	"Displacement"

@jrz371  I’m having the same exact issue when importing / exporting .glb/.gltf as well. This only happens when I’m exporting a headless RhinoDoc on HOPS / compute.rhino. It works fine in UI mode though.
I'm running Rhino 8.5.24072.13001

Hi, I think this is the issue. I plan on looking at it soon.


Add -L to oc curl to resolve redirect issues when accessing cross-cloud

Summary of Changes
This PR should resolve the issue outlined in this thread where OSCI produces this error when CURL-ing oc:
make[1]: Entering directory '/tmp/ocm-S9lcW'
make[2]: Entering directory '/tmp/ocm-S9lcW'
tar: This does not look like a tar archive
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
/bin/bash: line 3: /opt/build-harness/build-harness/vendor/oc: No such file or directory
make[2]: *** [/opt/build-harness/build-harness/../build-harness-extensions/modules/oc/Makefile:38: oc/login] Error 127
make[2]: Leaving directory '/tmp/ocm-S9lcW'
make[1]: *** [/opt/build-harness/build-harness/../build-harness-extensions/modules/clusterpool/Makefile:90: clusterpool/_init] Error 2
make[1]: Leaving directory '/tmp/ocm-S9lcW'

Duplicate of #183


Prevent comments inside CSS rules from breaking onto a new line?

Operating System (+Version): MacOS El Capitain v. 10.11.6
VS Code Version: 1.11.2
beautify Version: 1.0.2

Is there a way to not put CSS inline comment blocks on a new line?
.jsbeautifyrc
{
  "indent_size": 4,
  "indent_char": " ",
  "css": {
      "space_around_combinator": true,
      "selector_separator_newline": false,
      "newline_between_rules": false
  }
}

Action performed
Formatting CSS file with HookyQR.beautifyFile command
.foobar {
    color: red; /* comment */
}

Expected results
.foobar {
    color: red; /* comment */
}

Actual results
.foobar {
    color: red;
    /* comment */
}

Confirmed, cannot find an option to control this and is very annoying.
Similar weird formatting happens for:
Expected results
.foo {
    color: red;
}

/* This comment relates to bar */
.bar {
    color: blue;
}

Actual results
.foo {
    color: red;
}
/* This comment relates to bar */

.bar {
    color: blue;
}

Duplicate of #142


Introduce an universal newline character like \R

VSCode Version: 1.3.0-Insider (2016-07-01 build)
OS Version: Windows 7

Steps to Reproduce:

Open a new buffer;
Type three lines of text;
Open the find and replace dialogue and turn on regex;
In the Find field, input \n; in the Replace with field, input a whitespace;
Hit replace all.

The whitespace is supposed to replace the newline character entirely, but it seems the newline character is retained --- whatever is replacing \n got appended to each of the matching newline.

@zhangxiubo Are you using \r\n as the EOL sequence in your file?

In that case you'd need to search for \r\n:

@alexandrudima Thank you for your reply. Yes you are right, using \r\n works (I thought of it before but mistakenly tested \n\r perhaps). :+1: Wouldn't it be nice for VS Code to introduce an universal newline meta- like the \R in Sublime Text. :smile:

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


Rename marathon_local_address to marathon_hostname everywhere

We set the variable to /etc/conf/marathon/hostname only so it would be better renamed to what it actually is.
Needs updated in the marathon role, and in the Vagrantfile.

It has been changed by someone. I think we can close it.

Thanks, Closing


default types for destructuring function parameters should be optional

const blah({part, ...rest}) => console.log(part)
blah({});

this is valid JS and will output undefined, but is Illegal TS.
part defaults to part: any
should it not default to part?: any since it is possible for it to be optional?
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. new expression-level syntax)

That is not any different from a non-destructured parameter list:
const foo= (part, ...rest) => console.log(part)
foo();

this is valid JS code and will output undefined at runtime. yet the TypeScript compiler flags it.
the rational here, in the absence of any indicator that the parameter is optional, it is expected to be there, in other words, the compiler thinks the omission is likely an error.
you can indicates to the compiler your intention either using a default:
const foo = (part = "") => console.log(part)
foo();

const bar = ({ part = "" }) => console.log(part)
bar({});

or using an explicit type annotation:
const foo = (part?: any) => console.log(part);
foo();

const bar = ({ part }: { part?: any }) => console.log(part);
bar({});


[AIG]Added autolog description

Summary

Added autolog description

Screenshots (optional)

Documentation checklist

[ ] The documentation style guide has been adhered to.
[ ] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
[ ] Files which have changed name or location have been allocated redirects.

since i'd updated the limits page to remove the repetitive "maximum" words, will this PR have a problem merging?
do we use italics elsewhere? is that the best practice for like feature names?

we will try and see haha
We use Italics this way https://developers.cloudflare.com/style-guide/formatting/code-conventions-and-format/#italics so I don't think its necessary here


Cmake root directory

Hi, I know it's been long time since you uploaded this project, but by any chance, can you help me to solve this issue?
I'm trying to implement your project on my android device. But for some reason, it's not building.
Error:
CMake Error at CMakeLists.txt:5 (add_subdirectory):
The source directory

I tried to change the paths and rebuild, still not working.
Thank you.

OMG HI :D
Sure!
make sure you cloned recursively

I did clone it recursively, but the cpp folder was empty.
I tried to create a folder and name it dlib_android, a new error occurred.
Thank you for your time!

hmmmm!
clone this and put it in app/src/main/cpp
git clone https://github.com/mhyrzt/dlib_android.git

it's just a bunch of header files and source code of dlib library
https://github.com/mhyrzt/dlib_android
or clone the project again with this command:
git clone --recursive https://github.com/mhyrzt/Dlib-Android-Face-Landmark.git

Yes! it works now, thank you so much for your time and for your fast reply.
Happy coding =)

YW :D


Unclear where configuration module goes

Looking at https://milesj.gitbook.io/beemo/tool/events, I don't understand whetehr I make a file src/index.ts and that's it or whether I also need to run ts to create lib/index.js.

@domoritz It uses Node's require resolution, which is based on the package main field. So the file can technically be anywhere, but it needs to be JavaScript.

I see. I think the docs should clarify this since drivers can be pure typescript even in the published package (right?).

@domoritz Correct. The only way I can think of doing this is not using main.

Added file lookups and updated docs.


Addnodes

Hi, any addnodes?

addnode=<IP_ADDRESS>:20375
addnode=<IP_ADDRESS>:20375
Let me know if this doesn't fix your issue, I'll close the issue in a couple days if I don't hear from you.

Thank you


Why is JSON data cloned during load?

I have a JSON tree that loads from a database service and is used with D3 to visualize. When interacting between the jstree and the the D3 graph I'd like to be able to use the node objects, but it looks like during load the "original" attribute of the jstree nodes are set to clones of the original node objects and not the node objects themselves, which makes it hard to compare. I fixed it by adding another core settings parameter to skip the "parseJSON(stringify(...))" and "delete children" operations.
Is there a good reason to be cloning the original nodes?

Not cloning the data caused a lot of issues for developers that wanted refresh to work in a way that it always restores data to the way it was. There was also a lot of confusion when people modified the object after passing it to jstree and then wondered why the structure changed. I will however add an option for this in v.4. Also keep in mind when using a function the data is not cloned, so that is a short way to deal with this without modifying the source.
Best regards,
Ivan


Add files via upload

this is a university that is in New Taipei City, Taiwan

@ryan4javacode I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host tnu.tnu.edu.tw not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for understanding!


Internal error while creating updates: invalid argument: user data directory is already in use

I updated to 1.42 just now and ran it three times. Different errors each time. Posting here b/c of #2.

Got the error saying Chrome 97 is no longer supported, updated Chrome.
This error (attaching .log). Just re-ran without changing anything...
Different error: "Error: Internal error while creating updates: Message: invalid argument: user data directory is already in use,please specify a unique value for --user-data-dir argument,or don't use --user-data-dir"

The 3rd error I've received several times before updating to 1.42, and just waited to see if it would fix itself in the 1.42 release before reporting. I only receive it after having received a different error previously and attempting to re-run.
I've resolved this error by simply quitting and reopening MintAmazonTagger, which allowed me to continue.
I have had a successful run after receiving this error without quitting, but I had waited 30+ minutes after the error before running again. I've tried simply re-running, which doesn't work.
Log: 2022-02-07_10-16-00.log
Successful Log (after quit and reopen) FWIW:
2022-02-07_10-52-53.log

Thanks for the post @talon256. This should be fixed in 1.43 (going out shortly).


Is the 3DS hardware accessible from this?

Like capturing input from the buttons, drawing graphics, access to storage, etc?

Yes and no. It is a planned feature to extend the Python standard library that ships with 3DS.py releases by a ctru module which wraps the libctru APIs into a more idiomatic, higher-level Python API. This will allow you to do all the things you're looking for. It is designed to build upon a C module called _ctru which provides lower-level abstractions with a similar goal
However, that part of the project is currently in a very early state where only a barebones _ctru module is fleshed out.
https://github.com/vbe0201/3DS.py/blob/master/python_patches/_ctru/_ctrumodule.c#L471 is a list of functions that are currently functional within Python.
If you don't consider it a problem to eventually have to read the code of the _ctru module and the libctru docs, you could always use that as well:
import _ctru

# Bitmasks of all the keys.
A = 1 << 0
B = 1 << 1

while True:
    input = _ctru.hid_keys_down()
    if input & A == A:
        print("A pressed!")


Key_error :'INV_FREQ'

System Info / 系統信息
Getting KeyError:  'INV_FRQ' while executing the 4bit quzntized model
Who can help? / 谁可以帮助到您？
No response
Information / 问题信息

[ ] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
model = AutoModelForCausalLM.from_pretrained(
'THUDM/cogvlm-chat-hf',
torch_dtype=torch.float16,
low_cpu_mem_usage=True,
load_in_4bit=True,
trust_remote_code=True
).eval()

Expected behavior / 期待表现
Expect to execute the 4bit model

Just downgrade the transformers version to 4.37.2.

Just downgrade the transformers version to 4.37.2.

nice

Just downgrade the transformers version to 4.37.2.

Hi, curious, how did you know this was the issue!
thanks

I am trying to get the quant 4 to work with gardio "web demo", any tips ?

Just downgrade the transformers version to 4.37.2.

Hi, curious, how did you know this was the issue!
I am trying to get it to work with the "web_demo" gradio app, no luck so far, espeicaly not able to get the "with grounding" command to work for bounding boxes
thanks

Hey @emersonium
The code was working fine for me the before day, then I later checked that this issue happened after the transformer got upgrades (checked the version). So I just check the previous update and tried it worked fine.

Note installing transformers from source no longer has this issue. Only 4.38.* does.


Unlocked successes not loaded from steam

Hello all !
I am trying to get my unlocked successes from a game on steam.
Successes are loaded from steam but my unlocked success does not appear.

I tried every combinaison: public profil without and with key and private profil none is working.
In my lastest test I tried with public profil and with api key, my logs in extensions.log does not show errors:
17-12 08:29:06.057|INFO |SuccessStory#PluginDatabaseObject`4:RefreshNoLoader(One Way: The Elevator - 3e99b331-ea8d-42da-82e8-ada617d9ff81)
17-12 08:29:06.057|INFO |SuccessStory#PluginDatabaseObject`4:RefreshManual(One Way: The Elevator - 3e99b331-ea8d-42da-82e8-ada617d9ff81)
17-12 08:29:06.062|INFO |SuccessStory#SteamAchievements:GetAchievements(1347420) - IsLocal : True, IsManual : True, EnableSteamWithoutWebApi: False, SteamIsPrivate: False

Here are my settings:

I did not find a way to have more logs ?
Tell me if I can help doing tasks helping finding a way to fix this problem.

Yes, I got the same issue. See also here:
https://github.com/Lacro59/playnite-successstory-plugin/issues/412


ignore wacom devices

probesysfs uses hidinput as provider/driverfor wacom devices, which behave abnormally.  use linuxwacom provider/driver instead.

a better patch: #2


Bar chart doesn't display negative values.

I have looked at the pre-existing issues which all seem to imply that this was fixed in 1.x... However, when trying the following:
var data = {
    labels: ["January", "February", "March", "April", "May", "June", "July", "August"],
    datasets: [
        {
            label: "My First dataset",
            fillColor: "rgba(220,220,220,0.5)",
            strokeColor: "rgba(220,220,220,0.8)",
            highlightFill: "rgba(220,220,220,0.75)",
            highlightStroke: "rgba(220,220,220,1)",
            data: [65, 59, 80, 81, 56, 55, 40, -30]
        },
        {
            label: "My Second dataset",
            fillColor: "rgba(151,187,205,0.5)",
            strokeColor: "rgba(151,187,205,0.8)",
            highlightFill: "rgba(151,187,205,0.75)",
            highlightStroke: "rgba(151,187,205,1)",
            data: [28, 48, 40, 19, 86, 27, 90, -42]
        }
    ]
};

var options = {
    scaleBeginAtZero: false,
    responsive: true
};

var ctx = document.getElementById("myChart").getContext("2d");
var myBarChart = new Chart(ctx).Bar(data, options);

All bars start from -100... Am I missing an option?
Thank you,
Sam

Are you able to reproduce using the Release 1.1 version?
https://github.com/nnnick/Chart.js/tree/release/1.1
There is a zip button on the right to download.

Alternative solution is to move to v2. There are no issues with negative values in v2. The documentation for v2 is hosted at http://nnnick.github.io/Chart.js/docs-v2/


[Dropdown] Should Be Able to Set Exactly When Using API

I found two issues with the dropdown when using an API for retrieving data:

"set exactly" only works after clicking on the dropdown. If you use "set exactly" right after running the fiddle (press upper button), nothing happens.
"set exactly" does not change the value of the input

Are there any workarounds for these issues?
http://jsfiddle.net/2vdgwrty/1/#

Hi @mbbuehler,

This would be an equivalent of hitting an endpoint to retrieve some data, and then setting the value; current behavior is expected. You could either return options initially with a page, or do something like this instead of set exactly:

$('.ui.dropdown')
  .dropdown('set value', 'value')
  .dropdown('set text', 'text')

It doesn’t work, because you’re using get value incorrectly. When you initialize a dropdown on a select element, the component hides it and generates this markup with select instead of input for data storage:

  <input type="hidden" name="gender">

Gender

Male

Female

Afterwards, all methods should be called on a .ui.dropdown—not on a hidden select/input. You can also initialize a dropdown on existing markup, it’s much faster.
If you have other questions, I’ll be happy to answer them in this thread. You can use our Gitter chatroom as well.

Hi @Banandrew
Thank you very much for your reply. The functions work nicely for single selects.
But for selects with attribute multiple="multiple" it won't work like this. Is this behaviour intended? How can I set values and text for multiple selects?

@mbbuehler multiple variation uses the same HTML pattern as the one I posted above, the only difference is in the name, it’ll be .ui.multiple.selection.dropdown instead. In case of multiple dropdowns, a hidden input stores multiple values with a delimiter, e.g.: <input type="hidden" name="gender" value="male,female">. By default, the delimiter is a comma, but it can be anything you like. So, you can use set value like so:
$('.ui.dropdown')
  .dropdown('set value', 'male,female')

Instead of set text, you could use the add label method, which is undocumented, but that’s okay:
$('.ui.dropdown')
  .dropdown('add label', 'value', 'text', false)

The last parameter is a boolean, which tells the method if it should animate a label, you probably want it to be false.


Add logging

Codecov Report

Merging #90 (1ad703e) into main (63ff285) will increase coverage by 0.01%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##             main      #90      +/-   ##
==========================================
+ Coverage   64.37%   64.39%   +0.01%
==========================================
  Files          12       12
  Lines        1137     1146       +9
==========================================
+ Hits          732      738       +6
- Misses        314      317       +3
  Partials       91       91

Impacted Files
Coverage Δ

netmon.go
37.31% <0.00%> (-1.75%)
:arrow_down:

agent.go
75.75% <66.66%> (+0.60%)
:arrow_up:

dnsproxy.go
64.81% <100.00%> (+0.66%)
:arrow_up:

Continue to review full report at Codecov.

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