Crashes when distance 5 and see through walls on

crashes with:
When config set as title
java.lang.IllegalStateException: Pose stack not empty  at net.minecraft.class_761.method_22979(class_761.java:1558)  at net.minecraft.class_761.method_22710(class_761.java:1321)  at net.minecraft.class_757.method_3188(class_757.java:1039)  at net.minecraft.class_757.method_3192(class_757.java:816)  at net.minecraft.class_310.method_1523(class_310.java:1177)  at net.minecraft.class_310.method_1514(class_310.java:768)  at net.minecraft.client.main.Main.method_44604(Main.java:244)  at net.minecraft.client.main.Main.main(Main.java:51)  at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:462)  at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)  at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)

what mod version / minecraft version
did you try with only the mod installed in case it's a conflict

1.19.2 it was the newest so 2.1.0
Yes, all player's were crashing with these config settings when they got too close to another player

Yea idk. It works after I downgraded my modpack then went mod by mod and it fixed itself


Distance tax - Distance rate with non-zero tax rate shows 0% rate when submitting next expense

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

Version Number: 1.4-79-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/42909
Action Performed:
Precondition:

Track Tax distance is enabled on Old Dot
Workspace has a few distance rates and the distance rates are associated with tax rates

Go to staging.new.expensify.com
Go to workspace chat
Submit a distance expense with distance rate that has non-zero tax rate (so that this distance rate will be the default one when creating the next distance expense)
Go to workspace chat
Go to + > Submit expense > Distance
Enter waypoints > Next
Note that the tax rate for the distance in Step 3 becomes tax exempt (0%)
Change to another distance rate and change again back to the same distance rate in Step 8
Note that the distance rate only shows the correct tax rate after reselecting distance rate

Expected Result:
In Step 7, the selected distance rate should show the correct tax rate when creating another distance expense
Actual Result:
In Step 7, the selected distance rate should show the incorrect tax rate (it shows tax exempt 0%) when creating another distance expense
It only shows the correct tax rate when reselecting the distance rate (Step 8)
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/a4aebacb-5d47-44b1-b613-7fcefac28269
View all open jobs on GitHub

@joekaufmanexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
The distance tax rate isn't set automatically.
What is the root cause of that problem?
When we select a distance rate, we also update the tax rate here.
https://github.com/Expensify/App/blob/90dee7accae79c49debf30354c160cab6c52c423/src/pages/iou/request/step/IOURequestStepDistanceRate.tsx#L80-L89
But we don't do the same when initializing it. The app will currently only initialize the distance rate.
https://github.com/Expensify/App/blob/90dee7accae79c49debf30354c160cab6c52c423/src/components/MoneyRequestConfirmationList.tsx#L241-L249
So the tax rate will always be the default one.
What changes do you think we should make in order to solve the problem?

Initialize the tax rate too when the page is initialized.
useEffect(() => {
    if (!customUnitRateID) {
        return;
    }
    const distanceUnit = PolicyUtils.getCustomUnit(policy);
    const customUnitID = distanceUnit?.customUnitID;
    if (policy?.customUnits && customUnitID && shouldShowTax) {
        const policyCustomUnitRate = policy?.customUnits[customUnitID].rates[customUnitRateID];
        const taxRateExternalID = policyCustomUnitRate.attributes?.taxRateExternalID ?? '';
        const taxAmount = CurrencyUtils.convertToBackendAmount(DistanceRequestUtils.calculateTaxAmount(policy, transaction, customUnitRateID));
        IOU.setMoneyRequestTaxAmount(transactionID, taxAmount, true);
        IOU.setMoneyRequestTaxRate(transactionID, taxRateExternalID);
    }
}, [customUnitRateID, isPolicyExpenseChat, policy, isDistanceRequest, transaction, transactionID]);

maybwe weh should move it to a util function

I followed the reproduction steps above, and can't reproduce this. We are using the correct tax rate when I create the second expense, rather than defaulting to $0.
https://github.com/Expensify/App/assets/54866469/1c746cbc-fbc0-49df-af32-4e056d17bead

Gonna close this out for now since it doesn't appear to be reproducible, but LMK if there is some other way to reproduce this, and happy to take another look


Ensure non-zero return code on test failures

If we don't return results back to jest then jest will return a zero return code indicating that no errors have occured. This is problematic because it makes it impossible to know if the tests failed in CI systems and act accordingly (e.g. break a CI pipeline).
This commit ensures jest is made aware of the errors and returns a non-zero return code if a test fails. This makes it possible to utilise the jest return code in a CI system.

Just encountered this today since it breaks jest --watch mode with the following error
TypeError: Cannot read property 'snapshot' of undefined
    at results (/home/chornsby/eniram/ocp/ocp/node_modules/jest-cli/build/watch.js:117:37)
    at source.getTestPaths.then.then.then.runResults (/home/chornsby/eniram/ocp/ocp/node_modules/jest-cli/build/runJest.js:130:28)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Here the variable is undefined because the results object is not returned.

+1

👍


Refactor minimum recording length handling

Move timer reset to ensure minimum recording length is measured from the moment input is accepted
Related to #107
Related to #110
Also reported by a Neon user on Matrix that no input was accepted after WW confirmation sound was played

#76 and #73 added these Timers and tests, but I don't see why we wouldn't wait for the confirmation or playback before proceeding with recording which is what appears to happen now.
@JarbasAl @emphasize am I missing something with the Timer implementation?

replaced by #125


Deploy in wechat4u

Added deploy in wechat4u

Linked to issue #896

@vasvi-sood and @abhishek-iiit pls solve the merging conflict, and help yourself in merging the PR

Merging PR with no conflicts and 4 approvals :)


Cleaned up issue templates + added PR templates

The issue templates were overwhelming so majority of users just skip them.
Plus there was no "question" template.
As @tsira also suggested, it might be nice to have some PR templates. I never receive PRs but hey, doesn't hurt to give myself some templates so I follow some kind of unified format :)
Changes

Simplified issue templates & added question template
Added PR templates
Moved .remarkrc up a folder in .github

Closes #57

Those errors tossed by Codacy should not be occurring.

Screenshot from Codacy

I did experience something similar before where it did not register my config files.
My .remarkrc in both the repo root and in .github folder does clearly state to use the preset-lint-markdown-style-guide, which sets the heading-style to atx, and not setext.
Running remark-lint locally does not produce any warnings

Screenshot from my local terminal

Here's to hoping there's some caching that will self-invalidate if I wait for a day or something and then tell the analyser to run again.

Those errors tossed by Codacy should not be occurring.

Screenshot from Codacy

I did experience something similar before where it did not register my config files.
My .remarkrc in both the repo root and in .github folder does clearly state to use the preset-lint-markdown-style-guide, which sets the heading-style to atx, and not setext.
Running remark-lint locally does not produce any warnings

Screenshot from my local terminal

Here's to hoping there's some caching that will self-invalidate if I wait for a day or something and then tell the analyser to run again.

Seems to have had the repo misconfigured in Codacy

Up until now I had it on "Tool pattern list". I changed to "Configuration file" and then it worked fine.


'Token' object has no attribute 'get_ctnrs'

When you're not a superuser and you look at your user detail page, this error comes up.
'Token' object has no attribute 'get_ctnrs'

dupe


Ignores the host parameter

Locust tries to start the web interface on an invalid address and it ignores the host parameter.
I tried the following command
locust --host http://<IP_ADDRESS>:8089
And I get the following error:
<hostname/INFO/locust.main: Starting web interface at http://:8089
....
TypeError: code() takes at least 14 arguments (13 given)

Hi! —host/-H is for specifying your target (system under test)
As for why you’re getting that error, maybe you have set LOCUST_WEB_HOST env var accidentally?
See https://docs.locust.io/en/stable/configuration.html#all-available-configuration-options

Actually the error occurred because Werkzeug's version was old. For some reason, pip install locust wasn't updating the dependency.


Custom Error Message When Submitting Arrest Report

What version of Node.js are you using?
16.13.1
What version of npm are you using?
Latest
What operating system are you using?
Windows Server 2019
What version of SnailyCAD are you currently using?
Latest
Describe the Bug

At the moment if someone makes an arrest report but forgets to select an offense and only selects the category of offense they will just get a BAD REQUEST error. If we can add an error popup that says "Must add offence and fine or jail time amount to submit arrest report." or something that would be good.
Expected Behavior
A better detailed error message.
To Reproduce
Try to submit an arrest report with no offence or fines.

Are you able to provide the error message from that error? Or send the entire object here @ViolentMinds

THAT???
{
"DEBUG": {
"message": "Request failed with status code 400",
"status": 400,
"response": {
"data": {
"name": "BAD_REQUEST",
"message": "fine_invalidDataReceived",
"status": 400,
"errors": []
},
"status": 400,
"statusText": "Bad Request",
"headers": {
"content-length": "84",
"content-type": "application/json; charset=utf-8"
},
"config": {
"transitional": {
"silentJSONParsing": true,
"forcedJSONParsing": true,
"clarifyTimeoutError": false
},
"transformRequest": [
null
],
"transformResponse": [
null
],
"timeout": 0,
"xsrfCookieName": "XSRF-TOKEN",
"xsrfHeaderName": "X-XSRF-TOKEN",
"maxContentLength": -1,
"maxBodyLength": -1,
"headers": {
"Accept": "application/json, text/plain, /",
"Content-Type": "application/json",
"Session": "snaily-cad-session=undefined",
"is-from-dispatch": "false"
},
"url": "https://api.enemyofthestaterp.com/v1/records",
"method": "post",
"data": "{"type":"TICKET","citizenId":"cl1wxrsca71402xwtmano84k7g","citizenName":"John harris 111","violations":[{"penalCodeId":"cky5nfkzk5560d4tmych4sv0v","bail":null,"jailTime":null,"fine":231}],"postal":"2341","notes":"","seizedItems":[]}",
"withCredentials": true
},
"request": {}
},
"method": "post",
"data": "{"type":"TICKET","citizenId":"cl1wxrsca71402xwtmano84k7g","citizenName":"John harris 111","violations":[{"penalCodeId":"cky5nfkzk5560d4tmych4sv0v","bail":null,"jailTime":null,"fine":231}],"postal":"2341","notes":"","seizedItems":[]}",
"url": "https://api.enemyofthestaterp.com/v1/records"
}
}

yup, works. Thanks!

Alright, got this working 🎉. Will be released soon!


[BUG BOUNTY] Can't remove style on paragraphs that are separated by a new line

Flutter Quill version
8.6.1
Steps to reproduce
The following bug is really annoying for my users. I am willing to pay 50$/€ to the person who fixes this bug in a not hacky and clean way.
Write two paragraphs (separated by a new line), select both of them (or just "select all") and apply formatting like "bold" or "italic". Then you are not able to remove the style for both paragraphs. The only way is to select each paragraph separately and then you can press the "bold" button again

Expected results
The style removal should directly work also across multiple paragraphs
Actual results
Nothing happens when two paragraphs are selected and you try to remove an already applied style

I can confirm this is happening.
I want to dive deep on the lib. If the bug is still around by the time I can fix it, I will do it on @singerdmx behalf (they get the bounty).

I'm experiencing the same problem (version 8.6.2).
That being said, if you press the clear style button, the style is removed as expected.

Hi, thank you for the report
I can confirm that the issue has nothing to do with the QuillToolbar or any of the buttons because I already tested it with a custom toolbar that was made from scratch and I still can get the issue
The bug in controller.dart
In the function
void formatText(int index, int len, Attribute? attribute)

For now, it's in line 308 but that could be changed at any time.

I can confirm the bug happened because of the way the library handles the selection in the editor and the controller
When selecting all:

When selecting only one line:

As you can see the isToggled state differs, because the icon buttons color will be filled if the isToggled is true

Hello, I'm on mobile version trying to repro this issue but i'm not able to repro, could you provide a sample json or exact step on where this is occurring? this is what i'm doing:
open the editor -> type something on the first line -> hit return to insert a blank line -> hit return again -> type something on the second line -> apply bold style, then after that i'm able to select both lines and press bold again to remove. Under what scenario are the styles not able to be removed ?

Hello, I'm on mobile version trying to repro this issue but i'm not able to repro, could you provide a sample json or exact step on where this is occurring? this is what i'm doing: open the editor -> type something on the first line -> hit return to insert a blank line -> hit return again -> type something on the second line -> apply bold style, then after that i'm able to select both lines and press bold again to remove. Under what scenario are the styles not able to be removed ?

Please take a look at my comment, the problem that the way that selection work is not working like users expected, when you select all and you have in the first line bold text, second line is empty and third also have bold text
then you will see the button selected state is false because the button is not filled

Here's the result I see on my end, i'm able to apply bold to different lines (either one by one or all at one time), then select part or all of them to remove the style and it'll remove successfully. I am seeing a different issue though, after removing the style I can't apply it back because it thinks it's already toggled.
https://github.com/singerdmx/flutter-quill/assets/46685982/ab55c43b-7078-4161-9a4d-6f7cbb580dca
https://github.com/singerdmx/flutter-quill/assets/46685982/d39c05c7-aa69-42d1-a74d-3233ebcbe02c

I think you have to add an empty line between the text, then you get the described behavior.

Like this?

and then after clicking bold again:

@li3317 so you cannot repro it?

I just tested on the latest version and can still reproduce this issue as described 👀

I just tested on the latest version and can still reproduce this issue as described 👀

Me too

@singerdmx I'm not able to. Maybe it's different platform.

I think @li3317 is on mobile and she cannot repro it

This bug is so infuriating I decided to spend 5 hours to fix it
The bug is at lib\src\models\documents\nodes\line.dart at line 364-367, it compares style.attributes[attr.key] != attr.value when it should actually compare style.attributes[attr.key]?.value != attr.value, I guess the reason some people can't repro it is because in some version of dart anything == (bool)true while in some version only (bool)true == (bool)true
Simply change lib\src\models\documents\nodes\line.dart at line 364-367 to the following
        if (!style.containsKey(attr.key) ||
            (style.attributes[attr.key]?.value != attr.value)) {
          excluded.add(attr);
        }

Some other related issue can be fixed by setting keepStyleOnNewLine to false, see #1775
I've also created a PR request, #1782

I forgot one thing, we also need to merge the result with rest, change the line 391- 394 to this
if (remaining > 0 && nextLine != null) {
      final rest = nextLine!.collectStyle(0, remaining);
      result = result.mergeAll(rest);
      handle(rest);
    }

This bug is so infuriating I decided to spend 5 hours to fix it The bug is at lib\src\models\documents\nodes\line.dart at line 364-367, it compares style.attributes[attr.key] != attr.value when it should actually compare style.attributes[attr.key]?.value != attr.value, I guess the reason some people can't repro it is because in some version of dart anything == (bool)true while in some version only (bool)true == (bool)true
Simply change lib\src\models\documents\nodes\line.dart at line 364-367 to the following
        if (!style.containsKey(attr.key) ||
            (style.attributes[attr.key]?.value != attr.value)) {
          excluded.add(attr);
        }

Some other related issue can be fixed by setting keepStyleOnNewLine to false, see #1775
I've also created a PR request, #1782

Thanks a lot for fixing the issue !


URGENT: Fix util

This PR fixes the util.py file to use transactions.
Since some function signatures changed, I had to fix other parts of the code to make the tests to pass.
Any future PR will be based on this one, hence that is why it is urgent (the other ones will be in parallel, but they'll rely on the changes in util.py).
Some comments:

purge_filepaths is tricky. It is not used anywhere but it has the potential of leaving the DB out of sync with the FS if it is executed inside a bigger transaction. I haven't put any check on it, but one option will be to make it use it's own transaction. Since each Transaction object has it's own connection, this will not be an issue. However, I'd like to hear what others think.
get_preprocessed_params_tables was missing tests and it was incorrect.
find_repeated was not used anywhere, I removed it as we can use skbio's find_duplicates

Minor comments. Now, what about extending the idea of transactions so we only execute code once we know the transaction is done. For example, if something fails and you are using purge_filepaths do not move them until the full transaction is done. This could also be helpful for patches. Also, the codes looks fine but I think the biggest worry is not about the changes you made but about the possible missing lines that needed changing. Is there a way to verify that things that calls to any function that has SQL are actually being run in transaction?

Thanks @antgonza. Once everything is changed, a quick search in the code base for SQLConnectionHandler will tell us if there is anything executed outside a transaction.
I agree with you re executing some code once the transaction is done (e.g. moving files). This is a tricky question and it really depends on the operation performed.
For example, in purge_filepaths, if the transaction successfully completes and there is a problem removing files, it is not a big deal, as the only "bad" thing is that the file system is dirty (which is easy to write a function for cleaning it up in a cron job).
However, in move_filepaths_to_uploads_folder, the function is usually executed when unlinking files from raw data. If there is a problem moving files but the transaction is committed, those files are "lost" from the user point of view: they live under the raw data folder, but we've lost the filename and the user cannot access them. In this case, you want to rollback the operation.
The only idea that comes to my mind is this:
We add a list of tuples to the Transaction object, where each tuple is of the form [(src_path, dest_path)]. During the code we move the files w/o a problem, but we add them to this list. If the transaction at some point performs a rollback, it is in charge of moving back those files, so the DB and the filesystem are in sync.
Also, we add 2 list of strings, which will be "paths to remove on commit" and "paths to remove on rollback". In the former, the transaction will remove those files if it commits (e.g. for purge_filepaths) and in the later it will remove those files in rollback (e.g. creating a qiime_mapping_file).This way, we can make sure that all the filepaths that are in the DB are present in the filesystem, while we are allowing the filesystem to have files that they might not be in the DB (which I think is not a big deal).
What do you think @antgonza, is this a good solution?

Looks good @josenavas, just a few tiny comments and a question.

Thanks @ElDeveloper and @antgonza
I've added some functionality to the Transaction object so we can make sure that functions like purge_filepaths do not break the DB.

Thanks @ElDeveloper

The _clean_up function seems to be missing the func calls for post-rollback and post-commit (line 750).

Those calls are inside the commit and rollback functions

Ah, ok. I get the centralization logic here.

I think this looks ready ... :+1:

Ready for another review.
I've created the function exectue_fetchflatten so we can centralize in a single function the loop that we were doing in multiple places.
Given that @squirrelo felt strong about it, I end up fixing https://github.com/biocore/qiita/issues/1325. However, I did not implment @squirrelo  proposal. His proposal was hackish and not standard, so I've actually implemented a standard way of doing this.

:+1:


tracepipe logs are different from the one in the repo

My tracepipe logs are very different from the one's shared in this repo

and also only the upf_ip_entrypoint function is attached to the xdp hook of the eupf container
The other three programs never trigger as they are not attached to any hook
And also here is my eupf container logs if u need

Hi @Satyam-git-hub
I actually didn't get what's the difference in logs. Could you please clarify?

and also only the upf_ip_entrypoint function is attached to the xdp hook of the eupf container
The other three programs never trigger as they are not attached to any hook

upf_ip_entrypoint  is the only ebpf program that is attached to network interfaces at the moment. The rest programs are just stubs. You may ignore them without any doubts.

@Satyam-git-hub , from your log I see inconsistency in routing.

Please, check that the nat container is running:
sudo docker ps |grep nat

sudo docker ps |grep nat

nat logs are empty

Is it the desired output of the logs for nat?

@PapaySail

@Satyam-git-hub Hello! As I can see, you trying to use docker-compose deploy. You have session established from ueransim. I will continue investigation. Additionally, please try to ping some local node address from ueransim, i.e. ping -I uesimtun0 <IP_ADDRESS> -c1

I am able to ping local nodes

I am able to ping local nodes

Great! Seems your eupf itself working well. The issue might be in routing.

@PapaySail

I am able to ping local nodes

Great! Seems your eupf itself working well. The issue might be in routing. Check it from eupf container shell. It should looks like this:
sudo docker exec -ti eupf sh
/ # ip route s table n6if
default via <IP_ADDRESS> dev eth1

/ # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.332 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=0.223 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.223/0.277/0.332 ms

Yes its the same

Hi @pirog-spb

Hi @Satyam-git-hub
I actually didn't get what's the difference in logs. Could you please clarify?

The logs i get on the tracepipe only show FIB lookup and the ones in install.md are very detail and show
sergo@edgecom:~$ sudo cat /sys/kernel/debug/tracing/trace_pipe

          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>88: bpf_trace_printk: upf: gtp-u received
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>19: bpf_trace_printk: upf: gtp pdu [ <IP_ADDRESS> -> <IP_ADDRESS> ]
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>25: bpf_trace_printk: upf: uplink session for teid:1 far:1 headrm:0
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>28: bpf_trace_printk: upf: far:1 action:2 outer_header_creation:0
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>31: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:200000000
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>57: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: nexthop: <IP_ADDRESS>
          nr-gnb-4117277 [003] d.s11<PHONE_NUMBER>61: bpf_trace_printk: upf: bpf_redirect: if=6<PHONE_NUMBER>1770913972 -><PHONE_NUMBER>1770913978
          <idle>-0       [007] d.s.1<PHONE_NUMBER>75: bpf_trace_printk: upf: downlink session for ip:<IP_ADDRESS>  far:2 action:2
          <idle>-0       [007] dNs.1<PHONE_NUMBER>83: bpf_trace_printk: upf: qer:0 gate_status:0 mbr:0
          <idle>-0       [007] dNs.1<PHONE_NUMBER>85: bpf_trace_printk: upf: use mapping <IP_ADDRESS> -> TEID:1
          <idle>-0       [007] dNs.1<PHONE_NUMBER>87: bpf_trace_printk: upf: send gtp pdu <IP_ADDRESS> -> <IP_ADDRESS>
          <idle>-0       [007] dNs.1<PHONE_NUMBER>96: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: nexthop: <IP_ADDRESS>
          <idle>-0       [007] dNs.1<PHONE_NUMBER>98: bpf_trace_printk: upf: bpf_redirect: if=4<PHONE_NUMBER>1771765924 -><PHONE_NUMBER>1771765930

every step in detail from gtp-u received to bpf_redirect
whereas I am getting these logs
sudo cat /sys/kernel/debug/tracing/trace_pipe
          nr-gnb-936808  [006] d.s11<PHONE_NUMBER>69: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: nexthop: <IP_ADDRESS>
          <idle>-0       [009] d.s.1<PHONE_NUMBER>03: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: nexthop: <IP_ADDRESS>

@PapaySail

If it will not help, then open nat container shell and run tcpdump:
sudo docker exec -ti nat sh
/app # apk add tcpdump
/app # tcpdump -ni eth0

next switch to ueransim at another terminal and run ping -I uesimtun0 <IP_ADDRESS> -c1 The normal output of tcpdump should look like these:
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
16:22:36.289768 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
16:22:36.290084 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
16:22:36.290115 ARP, Reply <IP_ADDRESS> is-at 02:42:09:06:82:15, length 28
16:22:36.290135 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 55235, seq 1, length 64
16:22:36.295951 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 55235, seq 1, length 64

I am get this output for tcpdump
tcpdump -ni eth0
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
06:39:28.615909 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 48, seq 1, length 64
06:39:28.640999 IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 48, seq 1, length 64
06:39:33.689351 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
06:39:33.689409 ARP, Reply <IP_ADDRESS> is-at 02:42:57:85:b5:b5, length 28
06:39:33.689380 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
06:39:33.689425 ARP, Reply <IP_ADDRESS> is-at 02:42:0a:64:c8:06, length 28

IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 48, seq 1, length 64

Looks good. ICMP reqest was NATed correctly and responce received. Uplink is working, It should work in downlink too.
I just cloned repo https://github.com/edgecomllc/free5gc-compose.git, started sudo docker-compose up -d successfully.
sudo cat /sys/kernel/debug/tracing/trace_pipe
          nr-gnb-1242258 [000] d.s11 2494114.286826: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: 7
      prometheus-3616918 [005] d.s.1 2494114.293136: bpf_trace_printk: upf: bpf_fib_lookup <IP_ADDRESS> -> <IP_ADDRESS>: nexthop: <IP_ADDRESS>

I would recommend you to undeploy all,  clone repo and start from scrutch.

No any updates for far. Feel free to reopen if needed


error with baseline model

Hello,
When i setup the pipeline and try the first run with:
git push origin BASELINE_0
The SpeechTestDataCI will run.
I got an error in the step "Get the baseline model"
Error: Failed to get the latest baseline model. Possibly re-run all jobs.
Error: Process completed with exit code 1.
output is like:
SPX - Azure Speech CLI, Version 1.0
Copyright (c) 2020 Microsoft Corporation. All Rights Reserved.
csr.list.kind=models
csr.output.json.file=models.json
service.config.key=***
service.config.region=***
version=1.0.0
x.command=csr.model.list
Listing models ...
Listing models ... Done!
{
"values": []
}
Error: Failed to get the latest baseline model. Possibly re-run all jobs.
Error: Process completed with exit code 1.
I see also in the previous step (get the benchmark model)
tail: cannot open 'my.benchmark.model.url' for reading: No such file or directory
NO EXISTING CUSTOM SPEECH MODELS. TEST THE LATEST BASELINE MODEL.
Does anyone know how to solve?
Thanks in advance

Hi @jaxoftSkyDust, thanks for using the template repo. On the issue you raised, it looks like there have been some API changes to the way models are created. When I walked through for a repro, I hit the same error. I also noticed on the Speech Studio site that the model was uploaded but wasn't properly imported (the error message there points to the legacy API usage). I'll need to update the scripts to use the latest Speech CLI version, I'd guess there will be additional tinkering required after. I've filed a work item against me to track this.

I have worked around it by removing baseModel from the specific line
jq --arg LOC "$SPEECH_LOCALE" '.values[]|select(.locale==$LOC).self' models.json | tr -d " > models.txt
The issue however is now that for some reason the model.json created does not contain all models and tries to load more... this results in failing on github but works fine outside github by compiling on bash. Any reasons why this happens?
"@nextLink": "https://***.api.cognitive.microsoft.com/speechtotext/v3.0/models/base?skip=100&top=100"

Following @nextLink https://.api.cognitive.microsoft.com/speechtotext/v3.0/models/base?skip=100&top=100 ...
Following @nextLink https://.api.cognitive.microsoft.com/speechtotext/v3.0/models/base?skip=100&top=100 ... Done!
ERROR: Additional text encountered after finished reading JSON content: ***. Path '', line 1905, position 1.


fix: ignore single css chunk (close #688)

Summary
Ignore single css chunk when RequiredChunks added into HTML output during SSR.
Issue: https://github.com/gregberge/loadable-components/issues/688

There is just single one issue with test preventing merging this PR to a master branch 😭

There is just single one issue with test preventing merging this PR to a master branch 😭

There is just single one issue with test preventing merging this PR to a master branch 😭

Should I generate new __fixtures__ folder to test this case, or just modify stats.json directly? This case needs webpack5 and I think maybe shouldn't update the server-side-rendering example to webpack5.

There is just single one issue with test preventing merging this PR to a master branch 😭

Should I generate new __fixtures__ folder to test this case, or just modify stats.json directly? This case needs webpack5 and I think maybe shouldn't update the server-side-rendering example to webpack5.

There is just single one issue with test preventing merging this PR to a master branch 😭

Should I generate new __fixtures__ folder to test this case, or just modify stats.json directly? This case needs webpack5 and I think maybe I shouldn't update webpack to v5 of the server-side-rendering example.

Not sure if it's the right answer but in my (now closed 😢) I chose to modify the fixtures:
https://github.com/gregberge/loadable-components/pull/655/files#diff-7979dacf4945ebda3d5b355e934617b7bf14dbe6ec1996030bce2d413503349a
I think if your code is working but not passing the tests, it's better to edit tests if possible (tests adapt to code, not the other way).

There is just single one issue with test preventing merging this PR to a master branch 😭

Should I generate new __fixtures__ folder to test this case, or just modify stats.json directly? This case needs webpack5 and I think maybe I shouldn't update webpack to v5 of the server-side-rendering example.

Not sure if it's the right answer but in my (now closed 😢) I chose to modify the fixtures:
https://github.com/gregberge/loadable-components/pull/655/files#diff-7979dacf4945ebda3d5b355e934617b7bf14dbe6ec1996030bce2d413503349a
I think if your code is working but not passing the tests, it's better to edit tests if possible (tests adapt to code, not the other way).

merging to continue development from my side...

merging to continue development from my side...

Should I generate new fixtures folder to test this case, or just modify stats.json directly?

fixtures should be always generated from some source code, but look like that moment got lost somewhere.
After regenerating status from the expected source(examples/server-side-rendering) I have 18 broken tests....

Should I generate new fixtures folder to test this case, or just modify stats.json directly?

fixtures should be always generated from some source code, but look like that moment got lost somewhere.
After regenerating status from the expected source(examples/server-side-rendering) I have 18 broken tests....

While there is no test yet for this use case, it will be very good to double check that current version in master works and/or modify https://github.com/gregberge/loadable-components/tree/master/examples/server-side-rendering to produce the extended stats.
👉there is yet undocumented script scripts/prepare to do perform this operation.

While there is no test yet for this use case, it will be very good to double check that current version in master works and/or modify https://github.com/gregberge/loadable-components/tree/master/examples/server-side-rendering to produce the extended stats.
👉there is yet undocumented script scripts/prepare to do perform this operation.


add parameter to read out single value from channel

Add parameter to read out the digitizer channels as a simple instrument
@lukabavdaz @giulioungaretti @jenshnielsen @WilliamHPNielsen

@giulioungaretti @WilliamHPNielsen Autopep should be fixed now.

I don't have a good overview of this driver, but the changes in this PR seem fine.


Missing sources (or DLLs).  Klocman.Tools and UpdateSystem projects

Could you provide the source for KlocmanTools and UpdateSystem projects as well (see https://github.com/Klocman/Bulk-Crap-Uninstaller/blob/master/source/BulkCrapUninstaller.sln for reference)?  The project cannot be built with the source provided here.
(If you want to keep KlocmanTools and UpdateSystem projects under licence and not provide the code, that's fine too, But could you then make a release dll for those projects so that we can link to them and build Bulk Crap Uninstaller?)

Here you go.
https://github.com/Klocman/UpdateSystem
https://sourceforge.net/projects/kloctoolslibrary/


[bn] Localize horizontal-scaling.md

Signed-off-by: Nikhil Barik<EMAIL_ADDRESS>Localizes content/bn/horizontal-scaling.md to Bengali
This is an intial PR as may need some improvements!
Tracking issue: #410
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

Fixes #1866


fix: hover effect for disabled button

closes https://github.com/leather-wallet/extension/issues/5406
This fixes the hover effect for the disabled button by only enabling it relative to the same disabled condition

Summary by CodeRabbit

New Features

Enhanced Sign Out button to dynamically change background color on hover based on sign-out eligibility.

Thanks @jeeanribeiro 👍
This code LGTM. Can you please rebase your change with dev so that we have a single commit with your change? Then I can help get it merged. Thanks!

Thanks for the contribution @jeeanribeiro. This fixes this instance of the problem but overall disabled buttons should never have a hover state, so fixing it in only one place isn't a good solution


DOC-3591 add repl load metrics

Addresses: DOC-3591

Added two new metrics.

Question:

RangeStatistics is described as internal-only in the linked Eng commit, and I could not find a DB Console graph to match these new metrics. Just wanted to confirm that, for our public docs, only the two metrics added to metric-names.md is all that is required for this PR; please let me know if otherwise!! Thank you.

Staging:
metric-names.md

This change is

EDIT: Ah is it http://localhost:8080/_status/hotranges? I do see those new metrics here. If so, this is undocumented indeed.

It is these ones. They don't have a UI atm. This is also the V1 endpoint.

@kvoli TYFR!

@mikeCRL TYFR!


chore: bdd-nh-1587543575 to 0.0.1

chore: Promote bdd-nh-1587543575 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


add JUnit output format

fixes #928
The output groups violations by files in a testsuite and expresses each violation inside a file as a testcase. The files are sorted so that we have stable output during tests and each failure message contains the documentation link for a failed rule.
I'm not entirely sure whether notices should be part of the output as well. I've skipped them because most other reporters do not output them either.

Sorry, I didn't think of this before, but can yoy please update this section in the README too?
And I suppose this guide could use an update too so that GitLab users can benefit from this.

Apologies for the flaky tests, @sebhoss. We'll fix that this week, but do know it's not from your change.

OK I rebased on latest main, fixed all linting errors, and squashed all commits. Good to go from my side ^^


wip: feat/new(libsinsp): operationalize container exit events for compliance use cases

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap-engine-udig

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
Operationalize container exit events for compliance use cases, that is, Falco can be deployed on Kubernetes clusters that serve the purpose of hosting CI build containers. Typically, these containers are expected to only run for x minutes. With the new container exit event we can for example alert on violations thereof (container.duration exceeds an approx threshold).  The container exit event notification is expected to be slightly delayed compared to the true container exit since we perform the scan only every 30 sec.
CC @nigeldouglas-itcarlow
This PR is blocked by the bug reported in https://github.com/falcosecurity/libs/issues/1227
This PR breaks existing Falco rules around container enter events, we need to introduce (evt.type=container and evt.type=<) conditions.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

feat/new(libsinsp): operationalize container exit events for compliance use cases

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Discussing in that linked issue some design considerations, right now it's still not quite right in terms of completeness of container exit events fields. Plus obviously new tests are needed.

/milestone 0.14.0
since WIP

A quick note: This isn't a quick win as initially thought. Perhaps a minor container engine cleanup/refactor should even precede this PR. Will get back to it in the next dev cycle.

Note: Planning to get back to this soon, have not forgotten about it.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Quick note: I had been thinking about this PR a lot and finally have decided to drop it, as there is no elegant way right now to support container exit events, and there are still other, more important enhancements to be made to the container engines. I'm closing this for now, but we could potentially come back to it in the more distant future.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: incertum
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix(datalist): breaking changes

fix #1505

Deploy preview for pf-next ready!
Built with commit f87b14c71140f2f94359568972a35d86f5f838eb
https://deploy-preview-1506--pf-next.netlify.com


Dependabot preview not submitting pull requests

Hello.
We are using dependabot preview/v1 on https://github.com/badges/shields
We didn't get any PRs for new packages last week so I tried manually running a "bump now".
The run claims success but none of the PRs it says it was going to create in the logs were opened. For example:
updater | INFO <job_77180287> Checking if xmldom 0.5.0 needs updating
  proxy | 2021/04/19 19:50:27 [028] GET https://registry.npmjs.org:443/xmldom
  proxy | 2021/04/19 19:50:27 [028] 200 https://registry.npmjs.org:443/xmldom
  proxy | 2021/04/19 19:50:27 [030] GET https://registry.npmjs.org:443/xmldom/0.6.0
  proxy | 2021/04/19 19:50:27 [030] 200 https://registry.npmjs.org:443/xmldom/0.6.0
updater | INFO <job_77180287> Latest version is 0.6.0
  proxy | 2021/04/19 19:50:28 [032] GET https://registry.npmjs.org:443/npm
  proxy | 2021/04/19 19:50:28 [032] 304 https://registry.npmjs.org:443/npm
  proxy | 2021/04/19 19:50:29 [034] GET https://registry.npmjs.org:443/xmldom
  proxy | 2021/04/19 19:50:29 [034] 200 https://registry.npmjs.org:443/xmldom
updater | INFO <job_77180287> Requirements to unlock own
updater | INFO <job_77180287> Requirements update strategy bump_versions
updater | INFO <job_77180287> Updating xmldom from 0.5.0 to 0.6.0
  proxy | 2021/04/19 19:50:55 [036] GET https://registry.npmjs.org:443/xmldom
  proxy | 2021/04/19 19:50:55 [036] 304 https://registry.npmjs.org:443/xmldom
updater | INFO <job_77180287> Submitting xmldom pull request for creation

...we didn't get a PR bumping xmldom to 0.6.0
updater | INFO <job_77180287> Checking if concurrently 6.0.1 needs updating
  proxy | 2021/04/19 19:51:20 [052] GET https://registry.npmjs.org:443/concurrently
  proxy | 2021/04/19 19:51:20 [052] 200 https://registry.npmjs.org:443/concurrently
  proxy | 2021/04/19 19:51:20 [054] GET https://registry.npmjs.org:443/concurrently/6.0.2
  proxy | 2021/04/19 19:51:20 [054] 200 https://registry.npmjs.org:443/concurrently/6.0.2
updater | INFO <job_77180287> Latest version is 6.0.2
  proxy | 2021/04/19 19:51:22 [056] GET https://registry.npmjs.org:443/concurrently
  proxy | 2021/04/19 19:51:22 [056] 200 https://registry.npmjs.org:443/concurrently
updater | INFO <job_77180287> Requirements to unlock own
updater | INFO <job_77180287> Requirements update strategy bump_versions
updater | INFO <job_77180287> Updating concurrently from 6.0.1 to 6.0.2
  proxy | 2021/04/19 19:51:44 [058] GET https://registry.npmjs.org:443/concurrently
  proxy | 2021/04/19 19:51:44 [058] 304 https://registry.npmjs.org:443/concurrently
updater | INFO <job_77180287> Submitting concurrently pull request for creation

...no PR bumping concurrently to 6.0.2 either.
etc
The log for the run is at https://app.dependabot.com/accounts/badges/update-logs/77180287
(can paste in full if needed)
Package ecosystem
NPM
Package manager version
>=7.0.0
Language version
Node 12
Manifest location and content prior to update
https://github.com/badges/shields/blob/master/package.json
https://github.com/badges/shields/blob/master/package-lock.json
dependabot.yml content
https://github.com/badges/shields/blob/master/.dependabot/config.yml (we're using preview)
Updated dependency
N/A
What you expected to see, versus what you actually saw
PRs opened on repo for packages that needed updating
Native package manager behavior
N/A
Images of the diff or a link to the PR, issue or logs
The log for the run is at https://app.dependabot.com/accounts/badges/update-logs/77180287
🕹 Bonus points: Smallest manifest that reproduces the issue
Suspect this is N/A. The log output implies that the manifest parsing is not the problem here.

Would you mind upgrading to GitHub-native Dependabot (you can do so from https://app.dependabot.com) and trying again? Now that we're GA built in to GitHub we aren't planning on spending much time fixing issues with preview.
If you migrate and it's still broken, we can investigate further.

Hi thanks for getting back to me. In general I have migrated all of my repos away from preview and onto native.
The reason why we are sticking with preview for this specific repo is because preview allows automerged updates. This feature has been removed in native and it is valuable for us on this repo so the plan was to hold out on preview until we absolutely have to move. Last time I researched this there wasn't really a good solution or migration path for users relying on this feature although I haven't actively looked into it since https://github.com/dependabot/dependabot-core/issues/1823#issuecomment-641594279 . Is there now a clearer path forward on this or is the option still just lose access to that feature?
I have not found any documentation explicitly stating that dependabot preview is abandoned/unsupported (I did search for that before raising this issue) but if you're saying there is no avenue to getting this fixed on preview we will evaluate where we go next.
Cheers

Totally understand. I've slowly been consolidating automerge into #2268, but the short answer is that we don't plan on supporting it natively due to the potential for quick propagation of malicious packages. Using a third party app or an Action is the best solution if you're dead set on it.
As for documentation around the future of preview, it's coming shortly.

The same problem occurs in our repositories with dependabot-preview + npm.

same happening here. dependabot-preview
seems to detect correctly that a new version is available in the logs, but doesn't create any PRs.
seemed to have suddenly stopped a week ago.
updater | INFO <job_77540408> Checking if @babel/core 7.13.15 needs updating
  proxy | 2021/04/22 05:38:07 [078] GET https://registry.npmjs.org:443/@babel%2Fcore
  proxy | 2021/04/22 05:38:07 [078] 200 https://registry.npmjs.org:443/@babel%2Fcore
  proxy | 2021/04/22 05:38:07 [080] GET<EMAIL_ADDRESS>  proxy | 2021/04/22 05:38:07 [080] 200<EMAIL_ADDRESS>updater | INFO <job_77540408> Latest version is 7.13.16

Hi thanks for getting back to me. In general I have migrated all of my repos away from preview and onto native.
The reason why we are sticking with preview for this specific repo is because preview allows automerged updates. This feature has been removed in native and it is valuable for us on this repo so the plan was to hold out on preview until we absolutely have to move. Last time I researched this there wasn't really a good solution or migration path for users relying on this feature although I haven't actively looked into it since #1823 (comment) . Is there now a clearer path forward on this or is the option still just lose access to that feature?
I have not found any documentation explicitly stating that dependabot preview is abandoned/unsupported (I did search for that before raising this issue) but if you're saying there is no avenue to getting this fixed on preview we will evaluate where we go next.
Cheers

@chris48s automerge is easy to add in, take a look at how I do it with .NET Core on my CI workflows in https://github.com/Elskom/Sdk/
Yes this time I done all the research and work for you and anyone looking at this issue has permission to copy my workflows and edit it to how they want.
Also for automerge if you want to have it build the merged results, you must make a separate BOT user, add it to your orgs (if user repository add them as contributor), then make an PAT and add that as an repository secret (if user repository) or organization secret (if organization repository). After that is done you will get back everything that dependabot preview allowed.
Note: with automerge action it does not work when the user opens an pr from fork, my workflow on automerging only works from feature branches.

👋 I'm working on a fix for this, we made a change to how we parse registry details in npm/yarn and missed this change in preview.

This should be fixed now, thanks for reporting!

Cheers. I hadn't seen that one - I will add it to the list of options to look at.


Add marun domain for Marmara University

@karaca12 I am sorry, the domain marun.edu.tr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Pack at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Make detecting CUDA libraries more general

Hi,
I've built my Dockerfile from scratch, with ollama from source, also adding litellm, autogen in it.
Until now i'm successful with it, but ollama gave me headaches for it's not using nvidia GPU.
What i've found until now and after all this and I made it work.
In ./llm/llama.cpp/gen_linux.sh, CUDACXX is thought to be in /usr/local/cuda/bin/nvcc.
if [ -z "${CUDACXX}" -a -x /usr/local/cuda/bin/nvcc ]; then
    export CUDACXX=/usr/local/cuda/bin/nvcc
fi

I'm using conda to install cuda-toolkit, so nvcc it's in my miniconda3 installed dir.
Instead of hardcoding this path, maybe $(which nvcc) is a better way.
Also, in this file, after building the cpu, when trying to detect if cuda livraries are available like this:
if [ -d /usr/local/cuda/lib64/ ]; then it gives false.
I resolved my environment making symlinks:
    mkdir -p /usr/local/cuda && ln -s /opt/miniconda3/lib /usr/local/cuda/lib64
    mkdir -p /usr/lib/wsl && ln -s /usr/lib/x86_64-linux-gnu /usr/lib/wsl/lib

Without this, when starting ollama serve, it says:
 gpu.go:38: CUDA not detected: Unable to load libnvidia-ml.so library to query for Nvidia GPUs: /usr/lib/wsl/lib/libnvidia-ml.so.1: cannot open shared object file: No such file or directory
10x,
Now I'm a happy user !

Same problem here when using an nvidia/cuda base image (which is necessary for use on docker swarm).
These are the changes I needed to make:
diff --git a/gpu/gpu_info_cuda.c b/gpu/gpu_info_cuda.c
index 20055ed..5e22604 100644
--- a/gpu/gpu_info_cuda.c
+++ b/gpu/gpu_info_cuda.c
@@ -8,6 +8,7 @@
 const char *cuda_lib_paths[] = {
     "libnvidia-ml.so",
     "/usr/local/cuda/lib64/libnvidia-ml.so",
+    "/usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1",
     "/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so",
     "/usr/lib/wsl/lib/libnvidia-ml.so.1",  // TODO Maybe glob?
     NULL,
diff --git a/llm/llama.cpp/gen_linux.sh b/llm/llama.cpp/gen_linux.sh
index 3d659ff..b67aff2 100755
--- a/llm/llama.cpp/gen_linux.sh
+++ b/llm/llama.cpp/gen_linux.sh
@@ -18,7 +18,7 @@ set -o pipefail

 echo "Starting linux generate script"
 if [ -z "${CUDACXX}" -a -x /usr/local/cuda/bin/nvcc ]; then
-    export CUDACXX=/usr/local/cuda/bin/nvcc
+    export CUDACXX=$(which nvcc)
 fi
 COMMON_CMAKE_DEFS="-DCMAKE_POSITION_INDEPENDENT_CODE=on -DLLAMA_ACCELERATE=on -DLLAMA_NATIVE=off -DLLAMA_AVX=on -DLLAMA_AVX2=off -DLLAMA_AVX512=off -DLLAMA_FMA=off -DLLAMA_F16C=off"
 OLLAMA_DYN_LIB_DIR="gguf/build/lib"

In case it's helpful for others, I wanted to throw out that when working in WSL, I kept getting
CUDA not detected: nvml vram init failure: 9

until I ensured that the libnvidia-ml.so.1 path I wanted was at the front of the cuda_lib_paths array. In my case I wanted "/usr/lib/wsl/lib/libnvidia-ml.so.1", so I made the following change:
ollama/gpu/gpu_info_cuda.c
#ifndef _WIN32
const char *cuda_lib_paths[] = {
    "/usr/lib/wsl/lib/libnvidia-ml.so.1",  // Success when trying this path first
    "libnvidia-ml.so",
    "/usr/local/cuda/lib64/libnvidia-ml.so",
    "/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so",
    // Moved to the front from here "/usr/lib/wsl/lib/libnvidia-ml.so.1",  // TODO Maybe glob?
    NULL,
};
#else
const char *cuda_lib_paths[] = {
    "nvml.dll",
    "",
    NULL,
};
#endif

A side note, #ifndef _WIN32 will be true for WSL, so the change needs to be in the top definition of cuda_lib_paths. You can always simplify and replace the above conditional definition with
const char *cuda_lib_paths[] = {
  "/usr/lib/wsl/lib/libnvidia-ml.so.1",  // or whatever your libnvidia-ml.so path is
  NULL
};

Once you make the edit, you can rebuild with go build . at the base and I was in business. Important note: if this doesn't work for you, you might need to follow instructions from this comment which I tried first. Ultimately, I was able to undo the changes in it so I think the path ordering change described above is what fixed it for me. However, the mention of the NumGPU parameter in ollama/api/types.go is still helpful as I find that -1 chose a more conservative number of layers to offload to GPU than I would, and I got some improved inference speed when setting my own value (for ./ollama run mixtral I am using NumGPU: 30 on 4090 + 64GB RAM)
I haven't dug more into the why - none of the other paths exist in WSL so it feels like the loop lower down in ollama/gpu/gpu_info_cuda.c should successfully iterate till hitting the working path, but I'm rusty in C!

I am currently facing the same issue :)

I have a similar problem when trying to build v0.1.18 on arch linux with cuda.
I had to apply the following change:
diff --git a/gpu/gpu_info_cuda.c b/gpu/gpu_info_cuda.c
index 5273871..aebb779 100644
--- a/gpu/gpu_info_cuda.c
+++ b/gpu/gpu_info_cuda.c
@@ -9,6 +9,7 @@ const char *cuda_lib_paths[] = {
     "libnvidia-ml.so",
     "/usr/local/cuda/lib64/libnvidia-ml.so",
     "/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so",
+     "/usr/lib/libnvidia-ml.so",
     "/usr/lib/wsl/lib/libnvidia-ml.so.1",  // TODO Maybe glob?
     NULL,
 };

On arch linux CUDA_LIB_DIR is additionally not getting set correctly in
llm/llama.cpp/gen_linux.sh, as the cuda package is installed into /opt/cuda
instead of /usr/local/cuda. Maybe a change similar to the one below could help:
+if [ -z "${CUDA_LIB_DIR}" ]; then
+    # Try the default location in case it exists
+    CUDA_LIB_DIR=/usr/local/cuda/lib64
+fi
 if [ -d /usr/local/cuda/lib64/ ]; then
     echo "CUDA libraries detected - building dynamic CUDA library"
     init_vars
     CMAKE_DEFS="-DLLAMA_CUBLAS=on ${COMMON_CMAKE_DEFS} ${CMAKE_DEFS}"
     BUILD_DIR="gguf/build/linux/cuda"
-     CUDA_LIB_DIR=/usr/local/cuda/lib64

I'm also experiencing this issue: nvml vram init failure: 9
I can run the nvidia-smi command just fine, and can even run things like h2oGPT with no problem, so I think this is specific to ollama.

@dhiltgen It looks like everyone has honed in on the 'libnvidia-ml' loading problem. This should fix it and close out a bunch of issues. It should also work for AMD people who can't load 'librocm_smi64'.
The CUDA initialization ('cuda_init()') function is loading the wrong 'libnvidia-ml' library that does not have the symbols ollama needs. It gives up prematurely instead of trying the other libraries in the array. In my case, 'libnvidia-ml.so' was found in '/lib/x86_64-linux-gnu'. You can check this by typing:
ldconfig -p | grep libnvidia-ml

To get this to work all you really need to do is create a symbolic link:
sudo ln -s /usr/lib/wsl/lib/libnvidia-ml.so.1 /usr/lib/wsl/lib/libnvidia-ml.so
sudo ldconfig

Yeah, it's really is that simple. I wasted so much time on this!
Note: I'm not sure if this will remain 'fixed' after a nvidia driver update. There are similar fixes that you can read about here.
It would be better to address this in the code if someone would like to create a PR. Here's something that works, but it could use some clean up:
void cuda_init(cuda_init_resp_t *resp) {
  nvmlReturn_t ret;
  resp->err = NULL;
  const int buflen = 256;
  char buf[buflen + 1];
  int i;

  struct lookup {
    char *s;
    void **p;
  } l[CUDA_LOOKUP_SIZE] = {
      {"nvmlInit_v2", (void *)&resp->ch.initFn},
      {"nvmlShutdown", (void *)&resp->ch.shutdownFn},
      {"nvmlDeviceGetHandleByIndex", (void *)&resp->ch.getHandle},
      {"nvmlDeviceGetMemoryInfo", (void *)&resp->ch.getMemInfo},
      {"nvmlDeviceGetCount_v2", (void *)&resp->ch.getCount},
      {"nvmlDeviceGetCudaComputeCapability", (void *)&resp->ch.getComputeCapability},
  };

  for (i = 0; cuda_lib_paths[i] != NULL && resp->ch.handle == NULL; i++) {
    resp->ch.handle = LOAD_LIBRARY(cuda_lib_paths[i], RTLD_NOW);
	if (resp->ch.handle)
	{
	  // TODO - fix this to use a null terminated list
	  for (int symIdx = 0; symIdx < CUDA_LOOKUP_SIZE; symIdx++) {
		*l[symIdx].p = LOAD_SYMBOL(resp->ch.handle, l[symIdx].s);
		if (!l[symIdx].p) {
		  UNLOAD_LIBRARY(resp->ch.handle);
		  resp->ch.handle = NULL;
		  break;
		}
	  }

	  if (resp->ch.handle != NULL && (*resp->ch.initFn)() != NVML_SUCCESS) {
	    UNLOAD_LIBRARY(resp->ch.handle);
	    resp->ch.handle = NULL;
	  }
	}
  }

  if (!resp->ch.handle) {
    // TODO improve error message, as the LOAD_ERR will have typically have the
    // final path that was checked which might be confusing.
    char *msg = LOAD_ERR();
    snprintf(buf, buflen,
             "Unable to load %s library to query for Nvidia GPUs: %s",
             cuda_lib_paths[0], msg);
    free(msg);
    resp->err = strdup(buf);
  }
}

The same logic should be applied to rocm_init() so AMD people can be happy also. Or better yet, create a general purpose version that takes the path and symbol arrays as arguments. :-)

The runtime portion of this issue is covered by #1914 but there may still be some room to improve the build-time script logic, so I'll keep this issue open to track that.

The runtime portion of this issue is covered by #1914 but there may still be some room to improve the build-time script logic, so I'll keep this issue open to track that.

I made a pull request (#1880) for the build script logic. As long as the correct environment variables are provided this issue here should mostly be covered.


maxim onnx export

Issue Type
Others
OS
Ubuntu
OS architecture
x86_64
Programming Language
Python
Framework
ONNX
Model name and Weights/Checkpoints URL
maxim
Description
how can you export maxim model in torch to onnx.

Relevant Log Output
No response
URL or source code for simple inference testing code
No response

https://github.com/opencv/opencv_zoo


fix: checks haystack is null before using stripos()

I got a deprecated error when using bugsnag-symfony with PHP 8.1 :
stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated in vendor/bugsnag/bugsnag-symfony/Request/SymfonyRequest.php line 104

This is my first PR, so please tell me if something is not right.
Goal
Make bugsnag-symfony compatible with PHP 8.1.
Changeset
It checks that $haystack is not null before using stripos()
Testing
I ran phpunit tests

Hi @phillylovepark  - thanks for the PR! We're looking to add a static analysis tool like psalm/phpstan to bugsnag-symfony at some point in the future. This should help fix deprecated error messages such as this. We'll review this PR as part of that work when priorities allow 👍

Hey @luke-belton!
I really need this PR

hey @tarasTrujay - as this is a deprecation warning, it's not considered a critical fix for us at this time while we have other higher priority work on our backlog. I don't have an exact timescale for the static analysis changes I described in my comment above, however I will notify this thread with any updates. The deprecated change being warned about won't break until php 9.0 is released, which is still a long way off.

@luke-belton But you can merge this PR and that's it

Thanks for the PR @phillylovepark! I'm going to merge this down in https://github.com/bugsnag/bugsnag-symfony/pull/149 where I've added some unit tests for this class


Unable to copy paste screenshots and view the screenshots added in previously saved files.

Please find the screenshot:

Fixed in 13.6.9. Thanks for the report!


date: Fix -I options fail

This adds all short options for ISO date format e.g. allows date -Is or date -Imin
Closes #4744

and it needs tests in
tests/by-util/test_date.rs

I think a more algorithmic approach might be better here. So check how many words the string matches. If it's 0 then it's invalid, if it's 1 use that match, if it's more than 1 it's ambiguous.

Hmmm, it passes those tests on my computer and it works seemingly fine

@TobyJK ping ? :)

Closing this PR as it is replaced by #4977. Thanks anyway for your PR.


Failed build on Windows

@princejwesley I cannot rebuild Mancy on windows. I have errors about mime module.

@xgrommx  can you give full error here.. For me it is working good in windows7 ..

@xgrommx If you're using npm v3.x, try with v2.x instead.  This worked for me after having problems building on MacOS X.

this ticket should be renamed; "Build fails under npm v3"

@xgrommx  #43 PR helps ?

@princejwesley Looks like it's solved. Thanks

@princejwesley Another problem. After rebuild I don't have interface such on version 2.0.1. This is my result. But in dev mode it's working correctly.

@xgrommx let me try to reproduce it

@princejwesley This is not unique to windows; I have the same problem but only when running with npm v3

Same problem here. But I'm using Linux.
I can run
npm install
npm run package

with no errors. Executable is generated at dist directory. But when I launch it, Mancy has no prompt (like xgrommx screenshot). However menu works (ie "About Mancy").
By the way, I uncommented this line and it worked OK (no crash). I use latest electron-prebuilt version (0.34.3).

cursory test against master (as of this writing) under NodeJS v5.0.0 with npm v3.3.6 fails.

best guess is that the code makes some assumptions about certain packages existing in node_modules, while npm v3 puts them somewhere else.

@xgrommx Tried against node v5.0.0 and npm v3.3.12 in OSX. No issues. let me try it in linux

node v5.0.0 and npm v3.3.12 in Linux (Arch Linux).

@princejwesley did you rm -rf node_modules after switching versions?

@princejwesley I rebuild it again, doesn't work.

@boneskull No. I just gave npm install. let me try now.

@boneskull I can reproduce it. thanks.

Identified the issue. I'll fix and let you guys know

@boneskull @xgrommx @pmros npm 3 flattens the dependency structure. Fixed gulp task to handle it.

@princejwesley It work for me at Linux! So you could change note about Linux at README and add a Linux executable to next release (2.0.3). Good job! Thank you!

@pmros its not working for me (elementary OS 0.3.1 Freya). rm -rf node_modules and npm install might help. I'll try that.

This works for me:
cd dist/Mancy-linux-x64
./Mancy

But if I try to launch Mancy executable from another directory
./dist/Mancy-linux-x64/Mancy

I get a segmentation fault!

@xgrommx please confirm the fix

Closing it for now. Please feel free to open it if this issue is not resolved


Add support in pg.subplots2d() for height_ratios and width_ratios

Also automatically adjust the height and width. For every height_ratio that is 1 it should be 4 inches wide, so on

Should also add it to subplots(), just for good measure.

pretty sure this was merged into master and released in 0.4.0


Add support for latest PPT2 update

Also figured out what this mysterious update did, it removed the Intel AVX requirement.
https://steamcommunity.com/app/1259790/discussions/0/5879990700817165496

LGTM


Generic programming is missing

What do you mean? Generic programming is a very vague term. Can you give some examples?

We can stick to something like this:
Generic programming centers around the idea of abstracting from concrete, efficient algorithms to obtain generic algorithms that can be combined with different data representations to produce a wide variety of useful software.
So how well Haskell supports the generic programming? It does extremely well compared to other languages. How we can substantiate this claim? It's not very easy unfortunately because there are so many facilities in Haskell to support various generic styles.

Type system - type classes, algebraics, parametric polymorphism
Template Haskell to generate code at compile time
Data.Generic, Data.Data, Data.Typable and so on (integrated with compiler)
dozens of libraries for specific techniques (such as Scrap Your Boilerplate, Datatypes a la carte, Recursion schemes etc)
dozens of very abstract primitives (start from Typeclassopedia and go on to profunctors, lenses, conduits etc)
hundreds of unusually abstract algorithms (e.g. abstract breadth first search, abstract structural unification)
Generics category on Hackage
etc

So the question is how do we describe all of that concisely, and what is already covered elsewhere?


updated error handling for reporting.

Packages impacted by this PR
 @azure/microsoft-playwright-testing
Issues associated with this PR
Display informational messages to the user in case of errors at the end of test.
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Set BigPanda primary_property to check name

This will improve event correlation in BigPanda.

Are you going to omit the service tag in this PR or separately?

LGTM otherwise.

test comment

Are you going to omit the service tag in this PR or separately?

Okay, the service attribute is now removed.


[fmilib] Change to the github and update to fix bug of libexpat

Fix https://github.com/microsoft/vcpkg/issues/27890

Note:   The official statement has been transferred to github,  https://jmodelica.org/ so it has been changed to github download. And the problem about libexpat has been solved in the latest version 2.4.1 https://github.com/modelon-community/fmi-library/issues/18#issuecomment-1247834281

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Maybe fixing the merging of staticlib is better achieved with recent CMake's WHOLEARCHIVE:
https://cmake.org/cmake/help/v3.25/release/3.24.html?highlight=whole_archive#generator-expressions

This PR didn't fix #27890.


Add artifacts for ppc64le and s390x

This is an alternative to #124 should you not wish to go down that route yet.
Closes #95
Closes #73

cc @dmcgowan any preference of this or https://github.com/docker/distribution-library-image/pull/124 in order to enable ppc64le and s390x builds?

/cc @milosgajdos

@yselkowitz we've updated the image in the following PRs:

#129
#130
#131

The image is also already available on Hub as a multiarch official image (see here)
Would you mind if I close this PR and #124 which are basically duplicates at this point?

Thank you for that, much appreciated.  Probably not a blocker, but any idea when 2.8.0 will be stable?

Don't have exact date but we are aiming for next week or two the latest


requeue db instance while not available

After creating a new DBInstance resource, we were not setting
ConditionTypeResourceSynced on the resource nor were we asking to
requeue the resource after some time. This meant that the resource's
Status was not being updated on the Kubernetes side, even after the DB
instance's status transitioned to 'available' on the RDS side.
In this patch, we're adding two generic hook implementations for
sdk_read_many_post_set_output and sdk_create_post_set_output that will
create a ConditionTypeResourceSynced on the resource with a value of
ConditionFalse (because the resource isn't actually synced yet).  This
causes the controller to queue the resource up for a new reconciliation
loop, during which the resource's Status will be updated to the latest
observed values.
Fixes Issue aws-controllers-k8s/community#923
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.

/lgtm


Feature Request: mat-cell

feature request or proposal:
It would be nice to allow rendering custom HTML inside the table cells.

Feel free to put any custom HTML in your <mat-cell> and it will show up in your table. If you have any trouble or run into issues, ask our community on Gitter or StackOverflow.


please provide Image for TF 1.3.10

:memo:  Please provide for Image TF 1.3.10
we currently cant update our deploy Pipeline, since we rely on the TF Plugin Cache. but now we are hit by this Bug and need the newest TF 1.3.10 Version to workaround this Problem.
https://github.com/hashicorp/terraform/issues/34014#issuecomment-1751683477

Hello @gerhard-strauss-jambit !
I've created images for tf-1.3.10 just for you.

awesome, thank you 😄


BUG: Future time decoding

[x] Tests added
[x] Passes pre-commit run --all-files
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

This identifies (and hopefully soon fixes) an issue with decoding times that are way into the future. Without re-introducing a change made in #4684, the test fails (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136824754). With the change put back in, the test passes (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136892412).
@spencerkclark can I ask for your help on this one please? It seems that the removal in #4684 caused this case (which wasn't tested) to break in v0.17 and it's unclear to me where the fix should be (I'm guessing pandas from the discussions in #4684...).

If you can just add a what's new entry, I think this is ready to go!

Done, thanks!

In the meantime it occurs to me that if you (or anyone else experiencing this issue) need a workaround, you should be able to set use_cftime=True in calls to open_dataset or decode_cf, and I think things should work.

Thanks @znicholls!


Problems cloning a public repository using NPM in builder

This is on Deis 1.9 and CoreOS 647.2.0
When trying to clone a public repository via SSH during deployment (using buildpacks), we get a permission denied error.  I can reproduce this error by jumping into the builder container and running the git clone command manually:
bash-4.3# git clone git@github.com:babel/broccoli-babel-transpiler.git
Cloning into 'broccoli-babel-transpiler'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

The same command works fine locally and on the CoreOS host itself:
/tmp $ git clone https://github.com/babel/broccoli-babel-transpiler.git
Cloning into 'broccoli-babel-transpiler'...
remote: Counting objects: 403, done.
remote: Total 403 (delta 0), reused 0 (delta 0), pack-reused 403
Receiving objects: 100% (403/403), 60.93 KiB | 0 bytes/s, done.
Resolving deltas: 100% (225/225), done.
Checking connectivity... done.

Interestingly enough, using https inside the builder seems to work fine so it seems that there may be an issue with SSH inside the container:
bash-4.3# git clone https://github.com/babel/broccoli-babel-transpiler.git
Cloning into 'broccoli-babel-transpiler'...
remote: Counting objects: 403, done.
remote: Total 403 (delta 0), reused 0 (delta 0), pack-reused 403
Receiving objects: 100% (403/403), 60.93 KiB | 0 bytes/s, done.
Resolving deltas: 100% (225/225), done.
Checking connectivity... done.

Thanks

@mdolian Your first clone uses<EMAIL_ADDRESS>which will authenticate using key authentication, and will fail. You'll need to use an anonymous HTTPs clone as you did in your other examples.
I'm not sure where this is getting cloned/invoked, but you should be able to change this yourself or change the BUILDPACK_URL if this is a buildpack.

ok, so it sounds like the expected result of a git clone using the ssh url is a key authentication failure.  This isn't an issue if that is the case.  We will use the https url.


add nft_tx

This PR does three things:

Adds nft_tx API which should work identically to account_tx. The one difference is that nft_tx only responds with successful transactions at this point, since that is all we are storing in the index table.
Adds isClioOnly field to RPC handlers and marks nft_info and nft_tx as such. This will prevent these APIs from being forwarded to ripple. The benefit is not only to short circuit a forward that will not work, but also to improve error handling. In the event that someone specifies ledger_index: "current" on these APIs, and if they were to be forwarded, the resulting error just indicates that ripple doesn't know what the API command is. This is confusing. Instead, now that they are not forwarded, the error will be more sensible and indicate that the specified ledger was not found.
Fixes an issue where the returned ledger_index_min and ledger_index_max values for account_tx were not correct

Do we have any unit tests for this at the database level?

Do we have any unit tests for this at the database level?

Yup - that was included in the prior work for nft_info 🤘

NOTE - commit history is going to get full of "addressed comments" commits. I'll squash it all down prior to merge.

@ledhed2222 can you share your testing plan for this? I assume its some form of running this on nft devnet, since we have no analogous method in ripple to compare the output too. Also, we do need some unit tests for this, testing the database functions themselves.

* Fixes an issue where the returned `ledger_index_min` and `ledger_index_max` values for `account_tx` were not correct

Can you explain more what bug was fixed?

Do we have any unit tests for this at the database level?

Yup - that was included in the prior work for nft_info metal

ok great, disregard my comment about this elsewhere

NOTE - test existing behavior of account_tx WRT ledger_index_max/min on a standalone node to confirm it's the same as w reporting mode

think im leaning towards nft_txs for the name. nft_tx is a bit too confusing, does seem like it should return a single transaction about an nft. or maybe nft_history or nft_tx_history. account_tx really should be account_txs or account_tx_history.


Skip failing unit tests

Unit tests are ignored and failing. This PR makes failing test skipped.

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

Project coverage is 83.68%. Comparing base (1e00625) to head (7210c12).
Report is 14 commits behind head on stage.

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #797      +/-   ##
==========================================
- Coverage   85.79%   83.68%   -2.12%
==========================================
  Files          42       43       +1
  Lines        5464     5497      +33
==========================================
- Hits         4688     4600      -88
- Misses        776      897     +121

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


K4connect/usb description

Added support for USB description field for both Linux and Darwin

I think its still helpful to surface ID_MODEL as the description. As it is programmable in the field, it can be used to differentiate between multiple USB devices of the same time. In a control system, we often program the description field of USB serial adapters with an identifying string unique to that cable. So when we multiple on the same control system, surfacing this field lets us know which serial device is which in node.


Double check staff data at West Somerville

Check for this issue which we ran into at the Healey school (missing staff): #6.
And these issues (staff Active/Inactive status not up-to-date): https://github.com/codeforamerica/somerville-teacher-tool/issues/388.

Sent the list of West Somerville educators from X2 to Uri Harel.
Response:

You’ve got everyone there….

Sweet.
Closing this issue for now, will re-open if we find out we overlooked any issues in the WSNS staff data!


Switch product placement

Switch the product placement between Big Adopt a Hive and Small Adopt a Hive products in Products.tsx.

I’ll fix this.

I’ll fix this.

Sure, go ahead.

Please, help throw more light on this. Thanks

Please, help throw more light on this. Thanks

Of course! So in Products.tsx, the Big adopt a Hive product has to be in Small adopt a Hive's place, so you just need to switch their places. Because right now the bigger hive is first and it would be better if the smaller would come first in the list and after that the bigger hive.

Hey, sorry please reassign this to someone else. Thank you.

Hey, sorry please reassign this to someone else. Thank you.

Sure, no worries!


Revise WAI-ARIA practices urls

Recently https://www.w3.org/TR/wai-aria-practices-1.2 was updated with a note that the information had been moved, the intention now seems to be for them to provide an evergreen resource via https://www.w3.org/WAI/ARIA/apg/

This version of WAI-ARIA Authoring Practices is published to retire it from the Working Group Note track. The content continues to be updated in a format that is more useful to developers: https://www.w3.org/WAI/ARIA/apg/

The content continues to evolve in that location. The content is no longer versioned, but continuously updated. Improved code examples are also part of that resource

Honestly I think the communication around this is a bit confusing, It’s not clear when to reference the editors draft over that new AGP resource.
So I’m opening this issue to prompt the conversation. It doesn’t look like there are any plans by the WG to provide redirects so we need to update our URLs one way or the other.

The resources at w3.org/WAI/ARIA/apg are case sensitive
An example https://www.w3.org/WAI/ARIA/apg/patterns/Listbox takes you to a 404 page while https://www.w3.org/WAI/ARIA/apg/patterns/listbox takes you to the Listbox widget
I don't know if it's a bug or if that is intentional

These have been updated as we go.


Changes the source of gh-pages to FOSSASIA Summit

Fixes #1243
Changes: Reverts the source for generating gh-pages to FOSSASIA Summit
@mariobehling @aayusharora Please merge this. Thanks

Codecov Report

Merging #1244 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #1244   +/-   ##
============================================
  Coverage        65.28%   65.28%
============================================
  Files                9        9
  Lines             1515     1515
  Branches           224      224
============================================
  Hits               989      989
  Misses             526      526

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 307a6f6...cd3a723. Read the comment docs.

Thanks!!


Initial Version of Module

what

Initial Version of Module

why

Needed a way to setup AWS MSK via terraform.

I tried running a terraform init against this, and it's giving me an error w/ the AWS provider...
Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider hashicorp/aws:
no available releases match the given constraints ~> 3.0, ~> 2.0

should be fixed now

/test all

/test all

/test all

/rebuild-readme

/test all

/rebuild-readme c

/rebuild-readme

/test all

@htplbc let's ignore
lint / readme (pull_request) Failing after 1m

@3h4x can take a look at this later.

@3h4x see:

/rebuild-readme

/test all

/test all


non works with functions!!

As i think it's possible to work just with imports and requires but not with functions and so on. Anybody if you know let know me the tool which helps to debug JS code.. a lot of js code!!
..or may be some ideas how to setup dependencyGraph bind not only import and require but almost functions etc. ????

Are you looking for chrome devtools call-stack

Are you looking for chrome devtools call-stack

may be.. but like as dependencyGraph

It is possible to find out who is calling this function in the call-stack, and it is consistent with the scenario of wanting to know which functions was called by this function and visualize to get dependencyGraph. However, the issue is beyond the scope of this extension, only the general scheme is provided here.

Get the AST of the function

Parsing the AST to get the function call chain.

draw a visualization diagram

Finally, thank you very much for your support of this extension.


Ship a System bundle, for single-request SystemJS/Plunkr consumption

Some months ago, RxJS used to ship a System bundle, which could be conveniently consumed as a single HTTP request using SystemJS, and a clunker or other scenario where browser-based tooling is desirable but many small HTTP requests are not.
(This most often comes up in the context of Angular, which itself is shipped in the form of one bundle (actually several forms of bundle) for each major part of Angular. So for example it is currently usually possible to get all the parts of Angular one needs in a half dozen HTTP requests, but then require dozens more to obtain some of RxJS.)
The old SystemJS bundle went away, discussion in #1776.
I had suggested linking to an external SystemJS build in #2381, an idea rightfully panned all around. But several project members indicated openness to bring it back.
There is a related item #2335 about including a ES2015-in-ES2015 build. Although these two formats are completely different, the idea of providing several additional formats beyond CommonJS perhaps should be planned jointly?
There is a mostly orthogonal question about what package could contain these multiple formats. One idea was to retain rxjs as a legacy-ish CommonJS-only package, and have the newer @reactivex/rxjs package include all of the desirable bundle and module formats.

As I'm not SystemJS user, would like to add few high-level questions for quick elaboration.

Does SystemJS user blocked to use RxJS by not having its own package?
If not, what strong benefit by having separate systemjs package? Issue describes it as 'one http request' - is my understanding correct systemjs user does not installs package / bundle but just request to npm package when browser is loaded? if not, how does those http request helps loading module via systemjs?
2.1 Especially issue describes for single-request SystemJS/Plunkr consumption - is this case limited to plunkr usecase only?
In case of other packages doesn't provide systemjs build, how does this being resolved?

No one is blocked, but they do need to wait for extra HTTP requests.

Yes, that is correct! The target user (every user of every Plunkr Angular example) is most often loading the code from unpkg, the NPM CDN, or similar source. (There are a few narrower target users, myself included, who need a System bundle locally, and are building it locally.)

Not limited to Plunkr only, applies to all of the other similar tools. Also applies to most any other case where someone is running Angular code via SystemJS in the browser.

RxJS is unusual in how much and why this matters!

Consider ngrx/store, a popular add-on library use with Angular. Store used to have the same difficulty, Store was published only in the form of various individual files. But it now uses Rollup to provide a UMD build.
RxJS already provide something similar to that, available here:
<EMAIL_ADDRESS>However, this module format is not suitable to consume via Angular and SystemJS, because Angular code is full of references to deeper modules of RxJS, something like:
import 'rxjs/add/observable/of';

...and so on. These deep references do not work with UMD, but they do work with a System bundle. This is why RxJS is unusual - it is intended for consumption in this fine-grained deep way, it does not have its public API elevated to a flat top level façade. Putting all these ideas together, because of the shape of the RxJS API, a System bundle is the only format that makes it possible to load as a single file in this common scenario. So instead, currently is consumed as many separate requests.
It's possible that I simply care more than anyone else about the numerous extra HTTP requests and slower loading of example programs and Plunkrs that use RxJS via Angular.

So, if I understood correctly this also can be solved in other direction to let UMD bundle provides export paths as same as ngrx/store does, since Rx already uses rollup for umd build (https://github.com/ReactiveX/rxjs/blob/master/tools/make-umd-bundle.js#L12) not only solves systemjs issue but also resolves UMD users issue like https://github.com/ReactiveX/rxjs/issues/2185 ?
Is there reason to not go in those paths but need to publish separate build? Some limitation with Rx's build pipeline?

@kwonoj As far as I know, the UMD format does not support deep export paths. The various libraries package that ship effectively as UMD have a flat "façade" in which all of the functionality anyone imports is only one layer deep. For example, Angular itself earlier in development had various functionality exposed via deeper imports, but then later changed to a façade approach. Among other things this yielded compatibility with UMD.
Yes, this is the problem the user is having in #2185.

I think there's one more reason to use SystemJS bundle. Since SystemJS 0.20.* they removed the wildcard * option in paths options.
Right now the Angular2 is still using the older SystemJS 0.19.* where you can use the following to redirect all import to rxjs/* to a single bundle:
paths: {
  'rxjs*': 'node_modules/rxjs/bundles/Rx.min.js'
}

You can see that this works and loads just a single Rx.min.js file in this updated plnkr with the default Angular2 demo app (see systemjs.config.js file): https://plnkr.co/edit/tzLQmZ17ZMJHyBVrmzN9?p=preview
However this is not possible since SystemJS 0.20.* systemjs/systemjs#1039 but I think this could be solvable if RxJS was bundled as a SystemJS bundle and then imported with bundle config option. Then I could include it a via <script> tag or by predefining that for example rxjs/Observable and rxjs/Subject are both it the same bundle.
I read the problem in #2185 but to be honest I don't understand what's the issue there and maybe it's something different to my example above.

@martinsik Very interesting, I hadn't seen or used this capability of System 0.19. I've been using "bundles", with a (local) System bundle build of RxJS, something like this:
  bundles: {
    "libs:rxjs.system.js": [
      "rxjs",
      "rxjs/*",
      "rxjs/operator/*",
      "rxjs/observable/*",
      "rxjs/scheduler/*",
      "rxjs/symbol/*",
      "rxjs/add/operator/*",
      "rxjs/add/observable/*",
      "rxjs/util/*"
    ]
  },

... which should also work with .20.

@kylecordes This is exactly what I thought.
I just found out that when using bundles in SystemJS you're not limited to only system format and it works with amd modules as well (although it's not very obvious from the documentation).
The AMD bundle can be easily generated by just tsc so no SystemJS Builder is needed.
$ ln -s src rxjs
$ node node_modules/.bin/tsc -t ES5 -m amd --outFile rxjs.amd.js --rootDir . --lib es5,es2015.iterable,es2015.collection,es2015.promise,dom rxjs/Rx.ts

I had to make a symlink to rxjs directory and set --rootDir . that will generate all modules prefixed with rxjs.
I tested this with the Angular2 demo on plnkr and it works: https://plnkr.co/edit/JChO8ugk6vXh1EHlaM0y?p=preview
map: {
  'rxjs-bundle': 'rxjs.amd.js',
},
bundles: {
  'rxjs-bundle': [
    'rxjs/*',
    'rxjs/symbol/*',
    'rxjs/add/operator/*',
    'rxjs/add/observable/*'
  ]
},

So maybe this is even easier way of using the RxJS as a bundle in both 0.19 and 0.20 versions.

@martinsik Yes, that is right, AMD bundles are also easy to generate with just tsc. Incidentally, tsc can produce System bundles in the same way. I don't recall why I found using system-builder worked better for my use case.
Either way though (one-line tsc command, 10-line system-builder config), the main idea here is the benefit of RxJS shipping with one of these SystemJS-compatible formats that support deep import "in the box".

I just stumbled on this after re-visiting our situation:  since our group is all new to RxJs, it's way simpler just to import 'RxJs/Rx' and view everything, opposed to trial and error trying to figure out what operators we need.
Locally we're using SystemJS as the module loader, and as a part of the build we're generating a SystemJS bundle and referencing it via the bundles config (like in @kylecordes example).  However, just generating that bundle can take 20-30 seconds.
I was looking into options to get around that 20-30 second build, but I don't think any of them are going to be really great.  Ideally the RxJs package would come with a bundle like this ready to go

I'm going to close this, I know there are some demands around this but given complex sets of our build pipeline extending it isn't trivial at this moment. I'm trying to tackle to simplify those things a bit, to see if it allows some extendability in further but can't guarantee things at this moment.


Allow required_tags on a wand upgrade item

Hello i was wondering since there is a way to upgrade the icon of a wand but is there also a way to upgrade the inactive_icon?

I think you can simply put icon_inactive: stick{12345} on the upgrade item. It will get copied to the target wand.
The only reason there is a separate upgrade_icon property for upgrading the main icon is that icon is required to give the upgrade item itself an appearance, but you don't always wand an upgrade to replace the wand's icon.
I believe you can also do icon_inactive: "" to clear the inactive icon, but I haven't tested that myself in a while.
Hope that makes sense, please let me know if you have any trouble setting this up!

Works now thank you, I also have another question i've set auto_absorb to true but it still requires me to drop it on my wand?

That's possibly a bug, though that is a relatively new feature, is it possible you're not up to date? What does /version magic say?

It says 8.5.2-401b4ee

Thank you- apparently I was wrong though, that feature was added way back in 7.10
I'll have to try it out myself when I get a chance, could be it got broken somehow.
You're putting that right on the wand config, correct? auto_absorb: true

Oh wait, reading again- you're setting that on the upgrade item, maybe?
It only works on the wand itself, that tells the wand to automatically absorb any upgrades in your inventory when you hold the wand.

Yes its on the upgrade item

I've set it on the wand now and it works now, thank you! Last question is there also a way to limit upgrade items to certain wands?

Oh great- yes, but I think the only way to do that currently is via paths. So you can set your upgrade item to a specific path and it'll only upgrade wands on that same path. This doesn't really work out so well though.
Normally I have GUIs set up that make sure you only apply specific upgrades to specific items, usually using wand tags and the required_tags Selector option. This is how the builtin progressmenu works, for instance, so it can have different icon menus for the bow versus wands versus swords.
If that doesn't work for you though I could probably add a similar tag-matching feature to the upgrade items themselves.

Some sort of tag matching feature would be a nice thing to have

Im sorry for the amount of questions but one last question popped into my head, is there a way that you can remove deleted wands from the config by automatically removing them from the inventory or something?

Hm, good question but I don't think so.
For one, Magic generally does not scan players' inventories so anything you do would only take effect when the deleted wand is held.
Of course if you're deleted/disabled a wand then it won't work anymore in-game. But it will still appear as an item.
What I will often do in this case is create a "destroyed wand" wand item, something with an icon that has no value (maybe sulphur to represent it crumbling to dust). Then instead of deleting a wand config, I'll add migrate_to: destroyed. When held, the wand will turn to dust.
I could probably add an option so they get destroyed when held, or possibly even add inventory-scanning, but I fear both of these would be somewhat confusing to the player or lead to a lot of "my wands are disappearing" bug reports.

Yea i was thinking of some sort of migration to but it doesnt allow me to change the icon to air because then it would really be destroyed

yeah wands aren't allowed to have air icons is probably why that's not working.
But if you do need some sort of self-destruct mechanism, that could be added- but as I said, I feel like that would be very jarring to players.

Yea maybe add like a message with that feature? Like "your wand has been deleted from the configs and therefore destroyed"?


[SEC] Implement Checksums

Hi All,
For example on https://github.com/rancher/os-services/blob/master/images/20-iscsi/build.sh
You download open-iscsi using
VERSION="0.97"
| curl -sL https://github.com/open-iscsi/open-isns/archive/v${VERSION}.tar.gz > open-isns${VERSION}.tar.gz
| tar zxvf open-isns${VERSION}.tar.gz
| rm -rf /dist/isns
| mv open-isns-${VERSION}/ /dist/isns/
This poses a risk as everyone could potentially pose as https://github.com/*
By implementing a checksum we can be more certain that the binary that will compile is actually the binary that we want to compile.
Best Regards,
Guus Verbeek

Checksums are fine but solve the problem of open-iscsi being compromised and having the ${VERSION}.tar.gzartifact be replaced.
If github.com is being man-in-the-middled on your build server with a valid SSL cert you have far bigger problems, and no reason to think the checksum in the copy of this repo you downloaded from github too is legitimate.

Wouldn't it be better to implement a checksum check (ideally verified with multiple hashes to check to prevent a hash collision attack)?
It's true that if github.com is being man-in-the-middled on your build server with a valid SSL cert that you have far bigger problems. But this shouldn't be an excuse not to implement such checks. It might be even another way of figuring out as an administrator that you are currently being MitM'ed.
As the build server is a very critical component in the rancher process I believe it would be wise to add some extra checks to ensure security (besides, the version numbers seem to be hardcoded, so there wouldn't be a lot of hashes to be verified).

I'm not saying they shouldn't be added, but that they do not address the problem you describe.  This source is in github too, so if github (or communication with it) is compromised you would just have it return an altered build script that expects the hash of your altered tarball.

I agree, at least on the server level it depends on your trust for the certificates that are being included on Rancher OS.