Update cluster evac

transit removed
transit was remade into cluster evac
change cluster evac to the new one

pretty epic id just make the table extend across the entire wooded section tho

You may want to check that it FTLs in the orientation you expect. It looks like you may have mapped it sideways. That's not the end of the world, it just might look funny.
You can color the pipenets with

colornetwork [entid] Pipe [hex color]

The distro and waste colors are #0055cc and #990000.
Probably want to map a few air alarms now too since the change to air vents requires them to be set to fill through the alarms in the event of a spacing.
You missed some grilles under the windows at the cell.

You may want to check that it FTLs in the orientation you expect. It looks like you may have mapped it sideways. That's not the end of the world, it just might look funny.

i didnt map it from zero, just removed what i need from the old one so the rotation is fine
also i will the othet issues later, thanks for noticing

test fail


Suppress verbose build output

Issue: #1872
What I did
This is bit of a stab in the dark to address the output noice in Storybook.
Added --quiet to the CLI command list, so we can conditionally load the webpack.ProgressPlugin.
How to test
yarn test --cli

The circleci errors seem unrelated to this PR »Bad credentials

I've changed the PR base to master because we need to apply this change to mithril app as well. But it’s probably easier to open a new one than to resolve the conflicts
Please also document this option
https://github.com/storybooks/storybook/blob/master/docs/src/pages/configurations/cli-options/index.md

Please update config for app/mithril

Was this only applied to the start-storybook command? The docs don't have the --quiet option for build-storybook and the CLI is not accepting it. How hard would it be to get it done there too?

It should work for both in V5 I think! Can you help us test?


arch: arc: use top of isr stack as exception stack and bug fixes

re-use top of isr stack as exception stack
bug fixes in irq offload's implementation, this bug will cause irq_offload work wrongly.
improve kernel oops implementation

This PR may fixes #8292

Codecov Report

Merging #8297 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8297   +/-   ##
=======================================
  Coverage   64.53%   64.53%
=======================================
  Files         420      420
  Lines       40122    40122
  Branches     6763     6763
=======================================
  Hits        25892    25892
  Misses      11110    11110
  Partials     3120     3120

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 bf1e019...f0579cf. Read the comment docs.

This change fixes numerous bugs in 1.12.0-rc3, should be considered for 1.12

with this patch applied I am getting the following failures on emsk:
https://file.io/mgbtwK
on quark_se_c1000_ss_devboard:
https://file.io/q31plz

failures on EMSK with this patch:
http://kyza.ca/stuff/misc//em_starterkit_em7d_v22.xml.html
on Quark SE, we have no failures anymore:
http://kyza.ca/stuff/misc//quark_se_c1000_ss_devboard.xml.html

The remaining failures in tests/kernel/mem_protect/userspace and in tests/kernel/pipe/pipe pass if we increase CONFIG_PRIVILEGED_STACK_SIZE to 512

Nice to no failures on Quark SE
For emsk, there are some known issues which will be fixed in 1.13
******** KNOWN ISSUES **********
em_starterkit_em7d        tests/kernel/fatal/kernel.common.stack_protection  FAILED: failed
ANALYSIS: no Secure mode stack checking
Fixes: will be added and tested in 1.13

em_starterkit_em7d        tests/kernel/mem_protect/mem_protect/kernel.memory_protection FAILED: timeout
see: sanity-out/em_starterkit_em7d/tests/kernel/mem_protect/mem_protect/kernel.memory_protection/handler.log
ANALYSIS: overlapping MPU entries, the MPUv3 of ARC does not support MPU overlap
Fixes:  see the discussion in #7885

em_starterkit_em7d_v22    tests/kernel/mem_protect/stack_random/kernel.memory_protection.stack_random FAILED: failed
see: sanity-out/em_starterkit_em7d_v22/tests/kernel/mem_protect/stack_random/kernel.memory_protection.stack_random/handler.log
ANALYSIS: MPU alignment undoes randomization, the strong address alignment requirement of MPUv2 makes the stack random fail.
Fixes:  because the hardware limitation, it needs more time to find a fix, or  difficult to fix.

em_starterkit_em7d_v22    tests/kernel/sched/schedule_api/kernel.sched       FAILED: handler_crash
see: sanity-out/em_starterkit_em7d_v22/tests/kernel/sched/schedule_api/kernel.sched/build.log
ANALYSIS: build error, DCCM overflow, in MPUv2, because the address alignment requirement,
a thread stack requires more memory ( >= 2048 bytes and must be power of 2).
SO, it’s easy to run out of memory if there are a lot of thread.
Fixes: optimize the memory usage for the case of MPUv2
From: Anas Nashif<EMAIL_ADDRESS>Sent: 2018年6月10日 0:08
To: zephyrproject-rtos/zephyr<EMAIL_ADDRESS>Cc: Wayne Ren<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [zephyrproject-rtos/zephyr] arch: arc: use top of isr stack as exception stack and bug fixes (#8297)
failures on EMSK with this patch:
http://kyza.ca/stuff/misc//em_starterkit_em7d_v22.xml.htmlhttps://urldefense.proofpoint.com/v2/url?u=http-3A__kyza.ca_stuff_misc__em-5Fstarterkit-5Fem7d-5Fv22.xml.html&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=jMO1VGM8oAAtdFoK-SHwFGoGohk6ff_-Hz2RBH9Rrpc&s=bB2rX3RWF0QTzoVdlMhLZMtgJcnh5OWUzvQGL8FjTSc&e=
on Quark SE, we have no failures anymore:
http://kyza.ca/stuff/misc//quark_se_c1000_ss_devboard.xml.htmlhttps://urldefense.proofpoint.com/v2/url?u=http-3A__kyza.ca_stuff_misc__quark-5Fse-5Fc1000-5Fss-5Fdevboard.xml.html&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=jMO1VGM8oAAtdFoK-SHwFGoGohk6ff_-Hz2RBH9Rrpc&s=f_FTp84gpwCD7zoUgt4l288t5fk1eJ-DbogodDTrqlM&e=
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zephyrproject-2Drtos_zephyr_pull_8297-23issuecomment-2D395980345&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=jMO1VGM8oAAtdFoK-SHwFGoGohk6ff_-Hz2RBH9Rrpc&s=qWq-NQE26CZQ7aNDoVOwWS-BfCxl_tWNYyQbhncxtEs&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AFB9O8rE-5FpqhoT8C9RMqx6FYGIc7QCdFks5t6-5FLrgaJpZM4UhWos&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=jMO1VGM8oAAtdFoK-SHwFGoGohk6ff_-Hz2RBH9Rrpc&s=ni95sYGrgShJ13VqF8iU297NZSxPI3Rh0cp6Q_zxRks&e=.

@MaureenHelm: I hadn't signed off on #8246 for a reason, regression tests were not clean yet. This one is, please include in 1.12 release.


HF Phi3-mini-128k returns very different gradients than reference

🐛 Bug
When testing HF phi3 the gradients differ by several order of magnitudes from reference:
>       torch.testing.assert_close(grads_ref, grads_compiled, rtol=1e-2, atol=1e-2)
E       AssertionError: Tensor-likes are not close!
E
E       Mismatched elements: 39 / 128 (30.5%)
E       Greatest absolute difference: 0.0810546875 at index (0, 12) (up to 0.01 allowed)
E       Greatest relative difference: 8.125 at index (1, 3) (up to 0.01 allowed)
E
E       The failure occurred for item [0]

thunder/tests/test_networks.py:508: AssertionError

To Reproduce
Steps to reproduce the behavior:

Go to test-hf-phi3 branch
Run pytest thunder/tests/test_networks.py -k phi3
Wait for the error

Environment
Container 20241114 with Thunder at test-phi3@4c71eaa4f15028f94910e365ce6c3894769578a5
Additional context
This is part of #1278.
cc @apaz-cli

This seems to have been addressed in transformers 4.46.2, which is bumped in #1439

Closing since #1439 has been merged and the test passes now.


[FEATURE] Update gateway.turtlenetwork.eu url

Update the gateway.turtlenetwork.eu url to the new format
tngw.turtlenetwork.eu

should be fixed


Improve internal variable names

JSHint's "scopeManager" utility was initially implemented to refer to ECMAScript bindings using the term "label." Because ECMAScript uses the term "label" to describe a completely different language feature, this choice of names was somewhat confusing.
Modify all references to "JSHint labels" to use the more accurate term, "binding." Shorten the term "break label" to simply "label."

Coverage remained the same at 100.0% when pulling d049c995ed91723722db66cc42dbf3b6b2088e66 on jugglinmike:labels-to-bindings into 02f20b23bafb1aacbde41bfcdafe23e419c955d3 on jshint:master.


Fix spacing in recipes from old example

suicide fuel

Yeah it didn't appear obvious on my machine due to how my browser displays the emoji so I didn't notice.


Update documentation code examples.

In documentation code examples you specifying React component properties as type Props = Unit. I faced with issues at compilation time and I think this is too wide for scala compilator when it try to compile code with implicit types. Better specify components without props with case class like case class Props().

Hi! Could you share the compilation errors you get with the original code? I'd prefer fixing the errors themselves over telling users to not use something that intuitively should work.

Build log is here https://gist.github.com/viktorchukhantsev/1832af9765fee622dcd662558a20c0f9
I think this is cause Scala try to resolve implicit type with Any and it's too much.

Closing as outdated, this does not appear in the latest version of Slinky. Please reopen if you see this issue pop up again!


chore(master): release 0.0.19

:robot: I have created a release beep boop
0.0.19 (2023-07-20)
Bug Fixes | 修复

修复 onStop 无法等待逻辑执行完成的问题 (037c9b7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kercylan98/minotaur/releases/tag/v0.0.19 :sunflower:


"Use an obstacle during training?" does not always work

On choosing the "GameObject/Create Easy ML Arena and Agent" menu item, a dialog appears, asking: "Use an obstacle during training?"   Pressing the "Yes" button is supposed to add to the scene a gray wall, about the size of the ramp.
It does not seem that reliable, though: answering "Yes" sometimes produces no obstacle.  Sometimes it works to choose the "GameObject/Create Easy ML Arena and Agent" menu item again, and answer "Yes" to the dialog again.

Fixed by this pull request: https://github.com/JohnsonLabJanelia/FetchGamePhysicsTraining/pull/8


Added final report and updated link in README.

I've added the final report, please check it before merging :)

Indeed it does, but the naming of the file (draft) was FinalReport(BlueTurtle). If you look at the new file names, it should be clear what I was trying to do with the links.
I will update the text for the draft.

Final report looking good! We all already looked at it before uploading it here, so everything should be fine.

Alright, I will merge this then.


[CR-66] Add empty file check into test to determine the test result.

Work item: https://cockroachlabs.atlassian.net/browse/CR-66
Release note: none

Tested with tpcc and cpu. @ZhouXing19 You could give it a try for network test and report any issue.

When I get some cycle, will explore more to see if I could get a consistent repro, if so will either file a bug on roachprod and/or provide a fix on roachprod.
TFTR!


improve robustness for approvalrule.pp

The proposed changes will improve the robustness of the approvalrule.pp manifest. With the original code, I ran into the issue that if the WSUS server is low on memory, sometimes Get-WsusServer fails to complete. This will trip up the unless rule and make Puppet think it needs to re-apply the approval rule. This results in multiple identical copies of the same rule, which trips up other code that isn't expecting >1 result for a specific rule query.
The new code switches to onlyif to account for the occasional failure in Get-WsusServer and not have it result in duplicate rules.

Hey,
Sorry for getting back to this so late.  I will give this a review by tommorow!

Thanks @TraGicCode !

Thanks! Can you republish the module on the Forge too?
That way everybody can enjoy it :-)
Kevin Reeuwijk
Principal Sales Engineer, NEMEA
mobile: +31 6 272 33 55 1
<EMAIL_ADDRESS><EMAIL_ADDRESS>| @KevinReeuwijk
Puppet http://www.puppet.com. The shortest path to better software.
On Sat, Jul 27, 2019 at 12:22 PM Michael Fyffe<EMAIL_ADDRESS>wrote:

Merged #29 https://github.com/TraGicCode/tragiccode-wsusserver/pull/29
into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TraGicCode/tragiccode-wsusserver/pull/29?email_source=notifications&email_token=AGNBUR2FDLCJKBNEKYX4CQDQBQOUXA5CNFSM4H7NN2M2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSXNVB2Y#event-2514178283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGNBUR3FTJIEP6OIJDQBRN3QBQOUXANCNFSM4H7NN2MQ
.

Hi Michael,
I've published a blogpost
https://puppet.com/blog/how-automate-windows-patching-puppet on the
puppet.com website that uses your wsusserver module.
The example code in the blogpost uses the product_families attribute which
is in v1.1.1 of your module. But that module isn't published on the Forge
yet.
Could you please publish this version?
Thank you!
Kevin Reeuwijk
Principal Sales Engineer, NEMEA
mobile: +31 6 272 33 55 1
<EMAIL_ADDRESS><EMAIL_ADDRESS>| @KevinReeuwijk
Puppet http://www.puppet.com. The shortest path to better software.
Join us for Puppetize PDX http://www.puppet.com/puppetize 9-10 October.
On Tue, Jul 30, 2019 at 9:59 AM Kevin Reeuwijk<EMAIL_ADDRESS>wrote:

Thanks! Can you republish the module on the Forge too?
That way everybody can enjoy it :-)
Kevin Reeuwijk
Principal Sales Engineer, NEMEA
mobile: +31 6 272 33 55 1
<EMAIL_ADDRESS><EMAIL_ADDRESS>| @KevinReeuwijk
Puppet http://www.puppet.com. The shortest path to better software.
On Sat, Jul 27, 2019 at 12:22 PM Michael Fyffe<EMAIL_ADDRESS>wrote:

Merged #29 https://github.com/TraGicCode/tragiccode-wsusserver/pull/29
into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TraGicCode/tragiccode-wsusserver/pull/29?email_source=notifications&email_token=AGNBUR2FDLCJKBNEKYX4CQDQBQOUXA5CNFSM4H7NN2M2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSXNVB2Y#event-2514178283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGNBUR3FTJIEP6OIJDQBRN3QBQOUXANCNFSM4H7NN2MQ
.


This plugin invalidates cordova's Entitlements-Debug.plist and Entitlements-Release.plist

Hello I created a few issues related to the CLI for this plugin, we are having quite a few issues with the way the hooks modify the project files and hopefully you guys can address these.  Thanks a lot for your prompt replies by the way, I really appreciate it.
This issue is focused on the CODE_SIGN_ENTITLEMENTS property set within your xcodePreferences.js hook.  As of Cordova ios 4.3.0, Cordova sets this property in platforms/ios/cordova/build.xcconfig to point to the platforms/ios/{appName}/Entitlements-Debug.plist and Entitlements-Release.plist files...
Heres the property in build.xcconfig
CODE_SIGN_ENTITLEMENTS = $(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist

This works with the Automatic code singing features from Xcode8, where the CLI will inject capabilities such as aps-environment etc.. so since your plugin modifies this path to the Resources folder, release builds will fail because they need to validate that the provisioning profile associated with config in build.json, matches the entitlements in the file, which it cant locate because of the change to CODE_SIGN_ENTITLEMENTS.  You can also see this in Xcode if you do a debug build and go to Xcode capabilities pane, you will see that your capabilities are all disabled..
This impacts anyone using Cordova CLI and automatic singing for cordova-ios version 4.3.0, which is the best practice.
I would recommend checking first for the CODE_SIGN_ENTITLEMENTS and if its set, merging your domains with the appropriate plist file (debug or release, or both?), otherwise maybe keep the Resources/{appName}.entitlements file.  Although honestly I would even recommend moving in the direction cordova did with the new entitlements location.
feel free to contact me regarding some of these issues, I may be able to help out since there are some other issues with the hooks wiping out manifest intent-filters that are not even associated with the branch plugin.. (put an issue in for that which got closed and still unresolved)

Hello Devin,
I have pushed #300 to fix the issue of overwriting intent filters within the AndroidManifest.xml. As for the Entitlements issue, I am currently researching the best solution to this problem.
I will reach out as soon as I have more information, or if I need further information from you.
Thank you for your patience,

Nice @ethanneff thanks!

Hello again,
I was able to get Release Schemes working but it wasn't pretty. I had to do multiple attempts such as:

[fails] pointing the .xcodeproj to Entitlements-Debug.plist and Entitlements-Release.plist
[fails] updating the build.json with "codeSignIdentity": "iPhone Developer" for release
[fails] removing the modification of Entitlements-Debug.plist and Entitlements-Release.plist
[fails] relocating /Resources/{app-name}.entitlements to ./{app-name}.entitlements
[works] hardcorded CODE_SIGN_IDENTITY = 'iPhone Developer' for .xcodeproj

I understand this is not the ideal solution as it will prevent release codeSignIdentity modifications within the user's build.json configuration. However, I do have multiple apps in the App Store with Code Signing Identity set to iOS Developer.  Having this hard-coded should, hopefully, not be a problem.

I noticed you were looking for solutions elsewhere, but their code base was very similar to ours so I wasn't able to gain much insight. I think I'm going to push version 2.5.16 of the Cordova Branch SDK with the hard-coded change included. Wait and see to see if it work for other developers.
Thanks,


Upgrade pylint-django (and pylint)

This stops pylint complaining about some dynamic methods on BaseCommand.style e.g. here:
https://github.com/IATI/preview-website/blob/38d0107927e94cc435101dae320dcdf09988ba21/iati/home/management/commands/importnews.py#L46

$ make pylint
Your code has been rated at 8.74/10 (previous run: 8.14/10, +0.60)


RFC: Pre-transpile apm packages

Poking around in apm and npm's internals again sparked this idea. This is a proposal for what I think is the simplest possible way to support pre-transpiled apm packages.
:sparkles: 🖨rendered :printer: :sparkles:

Another alternative might be setting up a custom private npm registry instead of (ab)using the public npm one?

This idea was tossed around early in Atom's life, actually. I believe we didn't go that direction because we lacked the resources to admin and do ops on a CouchDB database properly?
We could always re-evaluate, but offhand, it feels like going the private registry direction is a much larger delta from what we have today. I was trying to write this up as a "quick fix" I could implement in a fairly short amount of time.

We could always re-evaluate, but offhand, it feels like going the private registry direction is a much larger delta from what we have today. I was trying to write this up as a "quick fix" I could implement in a fairly short amount of time.

Makes perfect sense! I just thought of it as an alternative and thought I would bring it up 😉.


HDDS-9199. Snapshot chain corruption should not fail OM restart

What changes were proposed in this pull request?
Currently, OM restart fails and leaves the OM in unstable (which can't be stabilized without manual effort) if there is any kind of failure in snapshot chain reconstruction. Previous issues (HDDS-7689, HDDS-8530, HDDS-8832 and HDDS-9073) where OM restart failed and left it in unstable state.
In this change, it is proposed to keep the snapshot chain state and let the OM start without any snapshot/chain related issues. Snapshot chain corrupted state is used to block all the snapshot's write operations like create, delete and purge snapshot if snapshot chain is corrupted.
A new parameter, snapshotChainCorrupted, is added to SnapshotChainManager to keep the state if chain is loaded successfully or not. It is used in access methods addSnapshot() to chain, deleteSnapshot() from chain and others before returning response to the caller. In case of chain corruption, addSnapshot(), deleteSnapshot() will throw IllegalStateException and fail snapshot write operations.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9199
How was this patch tested?
Updated unit and integration tests.

@swamirishi Could you also please take a look at it?

I guess we can just disable snapshots all together in case of snapshot corruption. OzoneManager#isFilesystemSnapshotEnabled(). Since snapdiff & deep clean should also not run.

OzoneManager#isFilesystemSnapshotEnabled() is based on ozone config. I don't think it is a good idea to leverage it for snapshot chain corruption. We can add something else but it would be similar to SnapshotChainManager#snapshotChainCorrupted.

Any operation relying on SnapshotChainManager should fail and would fail. If I'm not wrong, snapDiff, snapshot read and snapshot list don't rely on SnapshotChainManager. So I think it is OK to let them go. Regarding deep clean (or create snapshot), depends on  SnapshotChainManager because it is used to move keys around and cause snapshot corruption is wrong keys are moved. Deep clean will fail here: https://github.com/apache/ozone/blob/master/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/service/KeyDeletingService.java#L228 and similar for creation.

Thanks @smengcl and @swamirishi for the review.


BUG: /stats counts words instead of messages

Both commands show the # of words
/stats should give the # of messages

removed a duplicate help text, maybe related
https://github.com/br0-space/bot/pull/133


Add function to check if environment variables are configured corretly, fixes #7

This PR adds basic functionality in the crate to check whether the OpenSSL environment variables are configured and valid. This allows basic checking
The function has_ssl_cert_env_vars() has been added to determine whether any certificates will be found by OpenSSL through some basic environment variable checking.
The function init_ssl_cert_env_vars() now returns a bool to indicate whether any certificates were found while probing.
I've created constants for the environment variable keys to minimize duplication.
Note though, that these basic checks should be run before initializing OpenSSL, and that they are simple directory checks. It does currently not seem possible to actually check whehter the openssl crate is properly using these certificates, as it does not provide an interface for that.
Fixes #7
What do you think?

Looks good to me, thanks!


404 Error when trying to access Source Edit Chants view of a Source with no chants

When a user (logged-in, with edit access for a source) clicks on the "Edit chants (fulltext & volpiano editor)" button on a Source Detail page, if that source has no chants, a 404 error results. See, for example, http://<IP_ADDRESS>/source/710897 -> http://<IP_ADDRESS>/edit-chants/710897 (404)
I'm pretty sure this is because our Source Edit Chants view only works if there is at least one folio specified among the chants in the source (and since folios are properties of chants, if there are no chants, there will be no folios).
This occurs both on test sources that lack both chants and sequences, and on sources in the Bower segment that contain only sequences and no chants.
When you take a source with 0 chants and add a chant, the link/page work as expected.
We should be able to fix this by hiding this link in the template if the source has no chants.

This Issue has been resolved in #635, closing


URL change: dustpancake -> fjebaker

I renamed my GitHub account from dustpancake to fjebaker: updating the URL.

Hello @fjebaker. The requested change is now in progress.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests and closes those PRs when that is done. If you are subscribed to the associated PR https://github.com/arduino/library-registry/pull/474, you'll get a notification at that time.


Add JAX to speeding up section

I have to admit I haven't really much used JAX so far, my knowledge of it is based mostly on the SciPy 2020 talk and hearing people talk about it being one of the new cool things out there. But it's on my TODO-list, seems quite popular (it's google-backed after all) and production-ready and I think physicists could profit from it. Since JAX also offers a JIT, I put it into the speeding-up section.I'm no expert here so feel free to discuss this PR or reject it, it's just a suggestion.
The JIT is according to the talk (this part) less sophisticated than the one of numba, since it uses tracers and doesn't transpile python bytecode directly to LLVM.
Also the vectorization sounds like it might speed up things even on a single core, though I'm not sure how it compares to the other packages that offer the same feature (e.g. numexpr or I think numba as well).
The greatest advantage and spead-up potential is the ease of running numpy-like code on the GPU without needing tensorflow. But I'm not sure if this section includes speed-up via parallelization or running on GPU's, that could almost warrant it's own section, though there's a strong overlap with the Machinelearning table. I almost think this package could fit to machinelearning, since it is what it was originally meant for.
The coolest feature imo is the automatic analytic gradient calculation via jax.grad and I've already heard of people successfully using it, but that goes much beyond mere "speed-up"

Thanks for this PR. Yes, it makes complete sense to add it here.
@HDembinski is a person I know has used JAX, and had a positive feeling about it - if I'm not mistaken. He may be able to comment.


Control pipelines creation (IEC104)

Is your feature request related to a problem? Please describe.
Control pipelines are required in order to perform conversion of Commands sent by north service to south service.
The creation of those pipelines can be added to the importModules.sh script so that they are already defined at launch.
Describe the solution you'd like
Update importModules.sh to add the creation of the required control pipelines between the desired pairs of services:

iec104north_c1 > iec104_pivot_filter > iec104_pivot_filter > iec104south_s1
iec104north_c2 > iec104_pivot_filter > iec104_pivot_filter > iec104south_s2

Describe alternatives you've considered
N/A
Additional context
Currently the following Fledge issue prevent the configuration of control pipeline filters after their creation: https://github.com/fledge-iot/fledge-service-dispatcher/issues/61
Meaning that even with the above configuration, it will not be possible to update the exchanged_data configuration of the filters in the pipelines created above at runtime.
As a workaround until this ticket is fixed, it is still possible to recreate the control pipeline completely, with the expected filter configuration present from the start.

No need for control pipelines in the UC 104 to 104. As a general rule, the code of each deployment package shall be kept as lean as possible regarding the UC it is supposed to implement.


astronomer-providers not pinning airflow version (updating current setup)

Describe the bug
Installing Astronomer providers on an Airflow image downloads the last version of airflow it has pinned (>=2.2.0)
To Reproduce
Steps to reproduce the behavior:

install Airflow < last version
Install Airflow providers on the same environment

Expected behavior
Airflow needs to be installed to install astronomer-providers, so avoid installing Airflow, and issue a warning that Airflow >=2.2.0 needs to be present.
Desktop (please complete the following information):

Currently using official 2.7.0 Python 3.10 image

Hey @alejandrofm I have published some constraints file https://github.com/astronomer/astronomer-providers/releases/tag/constraints-1.18.0 can you please try to use it.

Hi, @pankajastro will look at the constraints, we are installing with poetry at this moment, and the thing that makes me raise this issue is: if Astronomer is a provider for Airflow, why does it install Airflow? it should not try to install the main package.
If I'm trying to install an add-on for an app I don't have, it should not install the full app but, at most, warn me about it.
For example Amazon-providers:
https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/index.html
that states the minimum version, but will not update the current Airflow release.
Also, it makes it easier to not make mistakes.
In my current install schema (not the best, I know) I have to pin the airflow version on the toml for astronomer-providers to make sure that it does not try to update Airflow.

The Astronomer provider depends on the Airflow providers, which, in turn, has Airflow as a dependency. Therefore, even if we remove it from our configuration, it will still get installed due to the upstream dependency.
We also leverage certain core features of Airflow within the providers, and I believe this is the primary reason

We have just released 1.19.0  which has pin the minimum Airflow, Python and upstream providers version.
I'll close this issue for now but feel free to open a new one if still face any issues. thank you!


prepended/appended text ignores HTML content

according to the docs, one should be able to include HTML (icons etc) in a prepended/appended text if an input. It's possible in bootstrap3 what I saw, and missing in BS5 component here.
So I added the |safe filters  - please check it. But it should be safe ;-)

When specifying the text can you make it a SafeString? I would expect this to work. The other thing could be that we're missing a mark_safe somewhere in the render "chain".
Afaik that's the recommended approach, as the many |safe filters in previous template packs are not advised, see previous discussion at https://github.com/django-crispy-forms/django-crispy-forms/issues/296.
I suspect in the coming period of time we'll be looking to remove the |safe filters from the Bootstrap3/4 template packs so more feedback and discussion is welcomed.


Would be possible implement zk-Snarks in Nano?

A lot of people are talking in Discord about implement privacy in Nano. I think that the best way to do it is through zk-Snarks.
Nano doesn't need to be private, but he could offer it like a optional feature because, certainly, a shielded transaction wouldn't be instantaneous.
This is a library that implements zk-Snarks in C++ the same language of Nano, so, It would facilitate the work: https://github.com/scipr-lab/libsnark

A significant problem with implementing privacy is how to handle representative weights. Simply having private accounts not stake their balance may result in a much lower amount of staked nano.

One option for this could be to treat all "private accounts" has being represented by a single representative.  How that representative is selected and maintained represents at least different problems.

@rkeene It sounds good, but I think that it could generate a centralization

I think that a anom transaction could happen between 2 accounts that have the same representative. So, the weight of the representative would be the same, the difference would be that we don't know how is distributed the coins between the accounts.

That's an extremely interesting idea, though I'll have to think about how limiting it would be (and if that could be enforced).

As said in the first post, it's important to note ZK-Snarks takes intense computational power, so it really impacts the 'instant' claim of Nano (for senders). It should be opt-in only.
If accounts are forced to have the same representative, we can also have the representative facilitate the TX (for a fee). Sort of like how Dash handles PrivateSend...

In general, the most privacy features takes an elevate computational power. This is the motive that it anom should be an optional feature. For me, It is not possible a currency private, instant, feeless, secure and light exists.

In general, the most privacy features takes an elevate computational power. This is the motive that it anom should be an optional feature. For me, It is not possible a currency private, instant, feeless, secure and light exists.

It's not an issue for senders, but it does raise a concern for validators.

To be clear, you said in your post that you were discussing different anonymity options. What other options are there besides from zk-snarks that are opt-in?

@brunoerg While heralded at the time as a breakthrough, the use of zk-snarks has room for improvement. For one, there’s the fact that there’s no way to tell with any real certainty that the elaborate procedure used to set up the cryptocurrency wasn’t in some way compromised. A year after the launch, the zcash team is still putting out audits on the matter. Yet as critics point out, their results, while helpful in mitigating doubts, can’t ever be conclusive.
ZK-SNARKs have a few underlying issues that will lead to reduced adoption for leveraging zero-knowledge cryptography in blockchains and other potential implementations as well:

The trusted setup phase can be compromised (there is an underlying assumption that when using a ZK-SNARK system, the trusted setup phase is secure)
Scalability of ZK-SNARKs can be improved, as run-time increases, the time needed to generate and especially verify proofs needs to be improved
ZK-SNARK cryptography is vulnerable to attacks from quantum computers

@asdfghjz Another option would be: ZK-STARKs
There are some important advantages of ZK-STARKs over ZK-SNARKs.

One is their transparency, which avoids the need for trust between the participants when the system is setup. This is usually anathema to the cryptocurrency communities.
Another important advantage is the assumptions underlying the system. ZK-SNARKs are based on Elliptic-Curve Cryptography, which is susceptible to advances in Quantum-Computers. Zk-STARKs, on the other hand, are Post-Quantum systems, meaning that even if Quantum-Computers become powerful and ubiquitous they will not have an advantage, compared to classical computers, in breaking ZK-STARKs (at least with our current knowledge of Quantum algorithms).
Finally, ZK-STARKs have yet another advantage, which is that the Verification process is simpler and faster than in ZK-SNARKs.

There is a downside to ZK-STARKs, however, in that the proof size is some orders of magnitude larger than for ZK-SNARKs. This means the use of one or the other technique is not immediately a no-brainer. But research will certainly go on, and may yet find ways to reduce the proof size, which will make ZK-STARKs even more appealing than they already are. The maths also seems to be easier, so I’m favouring them instead of ZK-SNARKs.
Finally, if the topic is on privacy, other options would be using the three different privacy technologies of Monero: ring signatures, ring confidential transactions (RingCT), and stealth addresses. These hide the sender, amount, and receiver in the transaction, respectively.
Background information links
https://www.coindesk.com/zk-starks-new-take-on-zcash-tech-could-power-truly-private-blockchains
https://medium.com/coinmonks/zk-starks-create-verifiable-trust-even-against-quantum-computers-dd9c6a2bb13d
https://ethereum.stackexchange.com/questions/59145/zk-snarks-vs-zk-starks-vs-bulletproofs-updated
https://zkp.science/


Statusbar flicker during transition w/ UINavController

Hi,
Love the library - appreciate your work on this.
I discovered when you're using a VC like a UICollectionViewController that fills the full screen and you use a UINavigationController, you get a flash or flicker from under the status bar during the transition.   This happens with light or dark status bars.   Is there a way to eliminate this short of redoing the view?
Here's an example - look at the status bar during the transitions.

Thanks again for the library!

This happens in my Application is well.
Author, Please help us out.

I got the same problem, any ideas to solve?

No solution yet.
I have temporarily removed this library from my project, until any solution would come out.

@Rashesh-Bosamiya @quochuyngo Sorry. We will resolve this error soon.

Is this fixed yet? Would love to use this lib since the other ones seem a bit bloated :)


Update StackOverflow tag name

Feature or Bugfix

Fixes broken link in README

Detail

The [awswrangler] tag is unused, the active tag now seems to be [aws-data-wrangler].

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks @gmarmstrong however as you may have noticed the library has been renamed to AWS SDK for pandas. So the tag name can be aws-sdk-pandas or awswrangler (i.e. the name of the library at import)


Tone is not toxicity

The PerspectiveAPI model largely identifies comments with a negative tone. This is of course correlated with toxicity, but it is not the same thing. This was identified as a problem as early as the day of PerspectiveAPI's launch, by Caroline Sinders: https://medium.com/@carolinesinders/toxicity-and-tone-are-not-the-same-thing-analyzing-the-new-google-api-on-toxicity-perspectiveapi-14abe4e728b3
Is there a plan to distinguish tone and toxicity? Is the underlying model even sufficient to distinguish them?

While I appreciate her expression of support working on this problem, it looks to me like the thesis in that post, namely that the toxicity data and model is actually identifying tone, is wrong. You can easily verify this yourself by testing examples on Watson's Tone Analyser here: https://www.ibm.com/watson/services/tone-analyzer/
The 'Tone' scores generally don't correlate strongly with toxicity from our API. I haven't been able to find their Tone dataset (maybe its not public) so I don't know about the underlying training data. In particular, many threats are tone neutral but are clearly toxic. Similarly, curse words are often considered rude, and so according to the toxicity dataset (which is public and available on figshare: https://figshare.com/articles/Wikipedia_Talk_Labels_Toxicity/4563973), even positive expressions with curse words are often considered toxic, although not severely so (see the distinction between severe and mild toxicity in the dataset), even when they are positive in tone.
When you look at the underlying nature of the data and questionnaire, it's actually quite easy to see why also. The questionnaire that we used to define toxicity is here: https://meta.wikimedia.org/wiki/Research:Detox
It's not a sentiment/question about the emotional tone of the text.
So, while there is certainly some correlation between sentiment, tone and toxicity; and you can certainly find some examples where scores are similar, there's also some big differences that you might not see if you only look at selected examples. I suggest instead, for example, scoring the Wikipedia dataset with tone models and looking at the results.


find rocm components individually

Required for spack since all the rocm components are located in different paths

retest Ubuntu-GPU-multi please
retest Ubuntu-CPU please

retest Ubuntu-CPU please
retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

I'm not able to reproduce the ci build failure for Ubuntu-GPU-single on my local machine, any ideas what the issue might be?

retest Ubuntu-GPU-single please

I'm not able to reproduce the ci build failure for Ubuntu-GPU-single on my local machine, any ideas what the issue might be?

I think it is landing on a node where the rocm driver is not stable which causes the tests to fail. If you can add the logs to your local run, here we can disregard the CI failure and merge this change.

retest Ubuntu-GPU-single please

retest Ubuntu-GPU-single please

Here's a log of my test run on mi100. There are only 2 test failures, one of which is that the test failed to allocate enough memory on the device. The errors I was getting on the ci are not present in the local run.
mi100_command.log

retest Ubuntu-GPU-single please

Here's a log of my test run on mi100. There are only 2 test failures, one of which is that the test failed to allocate enough memory on the device. The errors I was getting on the ci are not present in the local run. mi100_command.log

Yes, it wouldn't have any problem because I can see gpu-pycpp is green

Now that the pr is merged, this change needs to be backported to the r2.14-rocm-enhanced-spack branch. Also another branch called r2.16-rocm-enhanced-spack should be created with this change and https://github.com/ROCm/tensorflow-upstream/commit/f4f4e8698b90755b0b5ea2d9da1933b0b988b111

https://github.com/ROCm/tensorflow-upstream/commit/f4f4e8698b90755b0b5ea2d9da1933b0b988b111
Instead of creating a new branch w can we just use that as patch and apply it during spack tf installtion? That way we can use the rocm-2.xx-enhanced along with the patch.

f4f4e86 Instead of creating a new branch w can we just use that as patch and apply it during spack tf installtion? That way we can use the rocm-2.xx-enhanced along with the patch.

Sounds good, I'll try that out.


Bug in v. 1.6.1 on iOS14.2: Takes a long time to resolve codes

App version 1.6.1
IOS 14.2
IPhone XS
Upon opening app, it gets seems to stuck resolving the codes. This can go on for 10-12 minutes. Didn't used to take more than a 1 or 2 minutes.
I don't leave the house more than once a week now.

@melancholyaeon
So is this bug new with iOS 14.2 or with the App Version 1.6.1?

@heinzen could you transfer this Issue to the iOS Repo?


Problem installing xgboost on python 3.5

Hi
I'm trying to install xgboost-0.6a2 on my python 3.5 (over Anaconda), which runs on win 8.1 64 bit. The installation method is the traditional PIP, which is directed to the PyPI repository.
Here is the error message i'm getting:

C:\Users\Yaron\Documents\Data_Science\Intsights_Assignment_python_35>pip install xgboost
Collecting xgboost
Using cached xgboost-0.6a2.tar.gz
No files/directories in c:\users\yaron\appdata\local\temp\pip-build-qsfrwo\xgboost\pip-egg-info (from PKG-INFO)

I guess a preliminary process is required, but i'm not sure what it is...
Please help : )

Same issue

+1

+1

+1

+1

This solution is simple and it worked for me http://stackoverflow.com/a/39811079

Yes, https://stackoverflow.com/a/39811079 worked for me too.

Yes it worked for me as well. Thanks for help

works for me as well! Thanks!

Thank your

please someone explain the  steps to do it.. i have an error "cannot import name XGBClassifier

+1

Pls any help to get it work for me with sealang and seasnake installation!

It really works! Thanks for help!


Bot Wont Respond

Cannot get the bot to respond. do you guys have a support server? I have it installed correctly. im trying to make a video review of all of the winning bots from the contest. and yours is the one i am using for the most realistic/useable application

Could you provide some more details? It'd help with pinpointing the issue for you. Some questions I'd ask are
Does the bot connect to the server when you run the bot?
Are you running the docker version of the bot?
What python version are you using?
Are you running the bot on Linux, Mac, or Windows?
Have you changed the bot command prefix (b! by default)?
I'll do a clean clone and setup of the bot myself in a few hours when I get the chance just to make sure there's not something causing issues there.

I tried the Mac version at first but I couldn't figure it out for the life of me. Just got a new computer lastnight but I couldn't figure out how to delete the old version of python I downloaded. So I moved to my windows pc. Tried docker version but my version of Windows 10 isn't supported. So I tried the non docked version. I input my bot token. And the bot came online. And then it kept throwing a error that said something about config. So I assume it couldn't find the token. The bot came online. But everytime I tried a command that's when the error would come up. I'm on the latest version of python as I run the ModMail bot.i run my existing python bot in a venv so that wouldn't be the issue would it?

I am just trying to do a review of the hackweek bots I PERSONALLY liked and this one offers the most useful features for the application I would be using/testing the bots on. And at the end of the video. I am gonna show this one if I can figure it out. And one other bot for the best selfhosted bots for s video for my server users since I seem to get that question a lot

I'm not sure how it happened, but it appears that the bot was looking for the config in the wrong location. I have since fixed that. Please either redownload main.py and overwrite the main.py in the bot folder, or redownload the project and try running the bot fresh. Either will do.
Let me know if you still have any issues!

I've been asked to let you know that we are also working on an updated version of the bot for the coding community discord server. If you'd like to check it out, it's repository is hosted by the same person at https://github.com/FrostByte266/coding_community_bot . Some of our changes are put into the master branch, and the dev branch is currently very stable and has some new features added in for bot management, additional user verification, and more. Check it out if you get the chance :)

It's been a few days since I last heard from you, I'm assuming my fix has worked. If you have any other issues, please let us know and we'll help you get setup.

Sorry about that

I haven't fixed the issue. Well I kinda did. I was able to get it to respond but the only thing that really worked was the plot commands. Everything else kept looping

So I can just replace the main.py from the dev branch also right? Or should I just clone a fresh copy

I know you guys don't actually offer Support. But I was wondering if you had a discord server where you release the change logs and keep people updated and what not. I don't really get on here much at all only really if I am updating one of my projects. Would be easier for me to follow the bot updates via disco

Yes, replacing the main.py should do the trick, that was all I had to change.
Unfortunately, as far as I know, we don't have a dedicated discord for the bot. I'll raise the question with the maintainer of the bot though.

I don't believe there is any plans for a update release cycle for the bot on discord. I asked real quick and received back this answer.
"There are no planned updates, upgrades, new features, or known maintenance planned for the hack week bot. The intent for the hackweek bot is to keep it in stasis for people who wanted to use the hackbot in the condition it was in when it won. All known future development efforts are being placed on the coding community bot repo ( https://github.com/FrostByte266/coding_community_bot  ). The only possible reason we would do any additional push to the hack week bot is if another bug issue was opened.
Desired features are not bugs"
I just wish to note that desired features will be added to the coding community bot, which will continue to improve with time.

Okay thank you. Im gonna give it a go and let you know whats up. thanks for the quick response.

After trying to install dev branch https://hatstebin-plus.herokuapp.com/h6O6z3txDz

I'm not sure what the hastebin is supposed to show.... it's just a blinking cursor. Just te verify, you downloaded from here?
https://github.com/FrostByte266/coding_community_bot/tree/dev

I just gave the dev branch a clean clone and run, it started just fine. Is it possible that you don't have the dependencies installed?
bash pip install discord matplotlib networkx pandas prawn

I will do a clean install instead of just replacing main.py


Description for new Windows on Arm emulation settings are missing

Windows 11 provides new emulation settings for Windows on Arm that are not described in the documentation.

Technical descriptions of the following options are missing:

Hide x64 emulation capability
Additional lightweight emulation protections
Disable JIT optimization
Disable floating point optimization

Describing these options in greater detail will help developers troubleshoot compatibility issues with Windows on Arm.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: aaeae508-9f9e-0393-e223-2d9e37acc2f8
Version Independent ID: aaeae508-9f9e-0393-e223-2d9e37acc2f8
Content: Program Compatibility Troubleshooter on Arm
Content Source: landing/arm-docs/apps-on-arm-program-compat-troubleshooter.md
Service: windows
Sub-service: arm
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

Thanks for raising this issue @reflectronic! I was able to connect with the PM and get some descriptions -- added them in https://github.com/MicrosoftDocs/windows-dev-docs/commit/be7a0cf7c21b9cd73876c64e4fdaff97becb22b3


SSH deploy method breaks permissions preventing Labview from deploying rtexe

When including .pcfg in deploy method from Labview development will fail with insufficient permissions if DCAF editor has ever been used to deploy .pcfg file.
problem is avoidable by not including it in RTEXE deployment, however could cause problems later.

We SSH files over using the admin account.   LabVIEW deploys files using the lvuser account.  lvuser cannot overwrite a file owned by admin.
Possible solution: set owner to lvuser on any .pcfg files after deploy as part of command line call to the SCP client.

Acceptance Criteria

Deploy first from deploy tool, deploy second from LabVIEW and the deploy works.
Put in a test to deploy an admin owned file with LabVIEW's code path


new folder icon - prisma icon

This PR is for adding new folder icon to folders using PrismaJs

Hi, thank you for the PR! Just wanted to remind you of the contribution guidelines:

When submitting a PR, please ensure you've tested the extension locally and ensure that your new icons appear correctly in the file tree view with your new file extension. Include a screenshot of your proposed icon in your PR.


Update deploy-local.sh to use ujunox as the default denom

Also updates the README to add information about the default account
and formats it so that it is more readable as plaintext.
This is needed so that tx fees can be paid properly. Without these changes accounts are given in ustake which aren't used by juno. We needed to do this in dao-dao when moving to using the juno docker container.

Sorry, only just saw this.


Switch type hints from comment style to inline style.

Signed-off-by: Alexander Xydes<EMAIL_ADDRESS>

Codecov Report

Merging #33 (7899902) into main (9717a63) will not change coverage.
The diff coverage is 90.00%.

@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   88.23%   88.23%
=======================================
  Files           2        2
  Lines          85       85
=======================================
  Hits           75       75
  Misses         10       10

Impacted Files
Coverage Δ

...tatick_md/plugins/tool/markdownlint_tool_plugin.py
83.87% <88.88%> (ø)

..._md/plugins/discovery/markdown_discovery_plugin.py
100.00% <100.00%> (ø)

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 9717a63...7899902. Read the comment docs.


Advance malicious / broken module detection

Currently our malicious/broken module detection is manual making it an experience based reporting system i.e we just let the users complain.
Proposal -
Analyze every source file (js/ts) and dependencies in the module source code as and when a new version is published.
How -
It may sound difficult to implement something like this but luckily we have swc which makes things very easy for us.

It offers an ecmascript parser that would complain when a package is broken.
With swc_ecma_visit (used by deno_lint) we can look for malicious commands that could possibly be executed with Deno.run, etc and warn users while importing.
Scanning dependencies that are imported from other registries will make it full proof. See how dependency analyzer is implmented in deno_swc

Where -
This is most likely to be a part of the Rust API but it will be available as a rust crate for other registries to implement.
Why -
No other package registry has any automatic module detection system so we would probably be the first to do this.

This could be integrated well with module scoring

analyzer is the repo for this. Converting this to a discussion.


Update log4j-slf4j2-impl to 2.22.1

About this PR
📦 Updates org.apache.logging.log4j:log4j-slf4j2-impl from 2.22.0 to 2.22.1
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.logging.log4j", artifactId = "log4j-slf4j2-impl" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.logging.log4j", artifactId = "log4j-slf4j2-impl" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Already updated.


Cranelift: ishl with i128 shift amount panics on AArch64

Steps to Reproduce
Try to compile an ishl instruction with an i128 rhs using the AArch64 backend.
Expected Results
It compiles
Actual Results
thread 'rustc' panicked at 'Multi-register value not expected', /home/runner/.cargo/git/checkouts/wasmtime-41807828cb3a7a7e/c71ad94/cranelift/codegen/src/isa/aarch64/lower.rs:297:10
stack backtrace:
[...]
   2: core::option::expect_failed
             at /rustc/6d820866a27b1949e237be79b9c8c0145fe728b7/library/core/src/option.rs:1243:5
   3: cranelift_codegen::isa::aarch64::lower_inst::lower_insn_to_regs
   4: cranelift_codegen::machinst::lower::Lower<I>::lower
   5: cranelift_codegen::machinst::compile::compile
   6: <cranelift_codegen::isa::aarch64::AArch64Backend as cranelift_codegen::machinst::MachBackend>::compile_function

Versions and Environment
Cranelift version or commit: c71ad9490e7f3e19bbcae7e28bbe50f8a0b4a5d8
Operating system: N/A
Architecture: AArch64
Extra Info
AArch64 counterpart to https://github.com/bytecodealliance/wasmtime/issues/2727

Found by https://github.com/bjorn3/rustc_codegen_cranelift/commit/11584b52966cc71bdae39ac1733ea929201c517f.

cc @afonso360

This is interesting, because we have tests for this! https://github.com/bytecodealliance/wasmtime/blob/c71ad9490e7f3e19bbcae7e28bbe50f8a0b4a5d8/cranelift/filetests/filetests/runtests/i128-arithmetic.clif#L98
I need to look into this a bit more

The lhs is i8 in this case. Maybe it only gets handled when the lhs and rhs are both i128?

I think they are both i128, lhs is obtained from iconcat v0, v1, and rhs is iconcat v4, v4.

I mean in case of the bug the lhs is i8.

Oh, right, we also have test for those: https://github.com/bytecodealliance/wasmtime/blob/c71ad9490e7f3e19bbcae7e28bbe50f8a0b4a5d8/cranelift/filetests/filetests/runtests/i128-arithmetic.clif#L76
Are you able to get a clif file from cg_clif?

That test is the opposite way around. There the lhs is i128 and the rhs is i8. In my case the lhs is i8 and the rhs is i128. I don't have a clif file at hand, but I would guess it did be:
function %ishl_i128_i8(i64, i64, i8) -> i8 {
block0(v0: i64, v1: i64, v2: i8):
    v3 = iconcat v0, v1

    v4 = ishl.i8 v2, v3

    return v4
}

Oh, sorry, got it!
Yeah i'll have a look


Portfolio page: uneven space betwen columns

The three columns on the right on the portfolio page are unevenly spaced: the "Net Worth" columns should move a bit to the right, so that the distance for the next one is similar to the other two.

I think this might just be an optical illusion.

Has to do with the net work column having to be bigger to hold the larger number

@broskoski Sorry! I meant the Leaderboard, not the portfolio... my mistake


Adding ability to show infoText if html is in prop for ButtonsList

Where

JIRA Story: https://coverwallet.atlassian.net/browse/AON-605

What
We need to have ability to put new lines, make text bold and some other formatting for the infoText(ButtonsListSelect) in AON US SHF. We need it on FirmTypes Page, all firm types are added by CW and infoText also added only by CW team. User is not allowing to save manually any data. More info in screenshot provided.
How
dangerouslySetInnerHTML={{ __html: infoText }}
Screenshots

closed as not needed


How to get it running?

Hi,
thanks for working on this, this will be great! :-)
How do you run the current version?
I build it, but it always fails to locate files in the "contents"-folders, which is missing from the GIT repo.
Does this content need to get generated from the original game data?
How can I do this?
Also I noticed, that the "launchSettings.json" file contains a hardcoded path:
"workingDirectory": `"F:\Projects\OpenTPW"
Thanks and regards

I changed the hardcoded working directory so this should be fixed now

Sorry about that, my fault, I use VS in a VM and copied the bin folder to my main machine, that is why it missed the contents-folder!
Everthing works fine now, thanks! :)


Form for Discord Linux entry by R0X0RE0

What is your username and discriminator?
@Rox#8240
Why did you join Discord Linux?
I wanted to resolve an issue about a certain Linux website.
Where did you hear about Discord Linux?
I looked it up on Google.
What is the passphrase that was assigned to you by the bot?
Glory to the Tux? I have no idea, I wasn't sent a passphrase

From sans#8719 :
please read over the embed that the bot output when you joined the server, you'll find the passphrase that way.

thanks! in dms?

From sans#8719 :
just posting it here will be fine

where is the output

i tried to open the page and it shows me the rules

From sans#8719 :
yes, read over that. the passphrase is in there to encourage you to read the rules.

oh

let me guess - it starts with sudo?

sudo help pastebin

oh its something random

main-coach-miscarriage-situation

From sans#8719 :
alright, i've given you a temporary role so you can enter the passphrase in the welcome channel.


Sidecar upgrade needs kubectl apply not replace

Cherry pick of https://github.com/istio/istio.github.io/pull/2176

[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 approver: rcaballeromx
If they are not already assigned, you can assign the PR to them by writing /assign @rcaballeromx 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:

content/OWNERS

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

@ayj  any idea why circle is failing? Doesn't seem to be related to this change.


bug in a partial block processing

Hi Guys,
I tried NIST XTS test vectors with your code. Not all tests have passed.
The problem with the partial block processing. In particular, your code does not perform stealing of bits when data unit length is not multiple 8 bits, i.e., not a full byte.
Your current implementation assumes that the data unit length is always multiple of 8 bits, and thus it only performs bytes stealing (if needed).
For example, your code works if data unit length is 200 bits, i.e., input data length is full 25 bytes. However, size of 25 bytes is not multiple of 16, so your code will do bytes stealing in this case.
But, if data unit length is 250 bits, i.e., 31.25 bytes, where 31 bytes are full, and the last 32nd byte is not full. This last byte is padded with '0' to be full (according to NIST description of test vectors preparation). The padded bits in that particular padded byte should be replaced by applying bits stealing.
In fact, data unit lengths such as 130, 140, and 250 (all used by NIST) are not handled by your current implementation so that all such test vectors failed to pass.
According to the XTS-AES Validation System, the successful completion of the tests is required
to be validated as conforming to the XTS-AES algorithm standard.
Please, take a note of this issue.
FYI @horrorho
Thank you.

Hi. Thank you for the input.
It's not really a bug, it's just that non byte aligned data is unsupported. However I have failed to document this clearly. I'll amend this.
This project is based on the IEEE P1619 DRAFT proposals as clearly stated on the home page along with a warning to such effect. I've made no claims to any sort of NIST conformance.
That being said we can cite NIST publications:
The XTS-AES Validation System (XTSVS) : 6.2 The XTSGenAES Test
An implementation may support a data unit length that is not a multiple of 8 bits.
Recommendation for Block Cipher Modes of Operation: The XTS-AES Mode for Confidentiality on Storage Devices : 4 Conformance
...an implementation of XTS-AES may further restrict the length of the data units for any key.
So unless I'm mistaken and I admit that I've only partially skimmed the above NIST documentations, implementations that restrict data units to multiples of 8 bits are permitted.
So unless mistaken, your question revolves around:

NIST conformance.
Non-byte aligned data.

NIST conformance. Undefined. I'll make a note to this effect.
Non byte aligned data. I have no plans to support this. I'll make a note to this effect.


Legacy Dep Warning/Repo

Is your feature request related to a problem? Please describe.
Since the update to Deli that caused a split between legacy mods and the new 3.0 mods, I was having a bunch of trouble with my mod install where some were updated and some where not, which is understandable.  To remedy this, I basically just deleted all the mods, re-installed the Mod Installer and started downloading them again.
The problem I ran into was that there is no way to tell which mods use legacy deps, and which use the new ones, meaning if you download a mod with them it downloads the legacy dependencies and then everything conflicts and it's very annoying.
Describe the solution you'd like
The ideal solutions would be to either have a tag or column added that tells you if a mod has any legacy dependencies, or perhaps a separate repository entirely.
While I only know a little bit of C programming and not enough to help by adding a column, I do know that a repository can be defined in the json settings file for Mod Installer (as seen below).
A separate fork or project could be created for a legacy repository, of which the contents are what the current Mod Installer Database was right before Deli 3.0 dropped and it never needs to be updated again.  Then you could remove any mods that require the legacy version of Deli from the Mod Installer Database, and any legacy mods that get updated can be moved over.
Additional context

Apologies for late reply, but we would rather phase out legacy mods all together rather than support them

That's also fine, it's just this intermediate period where everything is getting switched over.  Will there be a cut-off date where you remove dead mods that won't be updated anymore then?

Most likely not, we may add a warning that the mod is very old, but id rather not remove mods


Allow time to be ignore in timeago format

I am dealing with a project where I need to display the records creation date with a "timeago" format. The things is, the time is always set to 00:00:00. Only the date matters.
The problem is we can't specify the element form which timeago should format.
It would be nice to have something like :

$("time.timeago").timeago({
  format_from: "day"
});

So, if we are the 25/08 at 9am, we could have 2016-08-25T00:00:00+02:00 giving today. Instead of 9 hours ago.
(Well, I concede this API is horrible and we have to discuss about it...)
I guess we will have to focus on that.
What do you think ?

we could have 2016-08-25T00:00:00+02:00 giving today

Unlikely to ever be a core feature. It violates the notion of a fuzzy timestamp. This has been covered a few times in previously (closed) issues.

(Well, I concede this API is horrible and we have to discuss about it...)

Agreed, and there is no need to add any features. You can already accomplish what you want by simply overriding some of the locale methods.  That would be very nice to have it in the documentation, since it has been ask many time already, what do you think ?

That would be very nice to have it in the documentation, since it has been ask many time already, what do you think ?

Sorry, no. I'm not going to add and support and maintain documentation for features that are not part of the library. That would be endless. Not to mention, people usually fail to read the documentation or search past issues before requesting new features anyway.
However the Wiki is open for people to add whatever documentation they think is appropriate to help future onlookers.

I was talking about the solution you gave to me, to know :
jQuery.timeago.settings.strings.seconds = "less than a day";
jQuery.timeago.settings.strings.minute  = "less than a day";
jQuery.timeago.settings.strings.minutes = "less than a day";
jQuery.timeago.settings.strings.hour    = "less than a day";
jQuery.timeago.settings.strings.hours   = "less than a day";

This is what I was talking about.


dmg: simplify distribution.xml

I can't see the intent of the current implementation.
If there is no intent, it would be better to keep it as simple as this.

It may be obvious for macOS developer, but it is good practice to mention  "why it is reasonable change".
Indicating Distribution XML Reference is one example to achive it:
https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html#//apple_ref/doc/uid/TP40005370-CH100-SW9

Sorry for my lack of explanation.

it is good practice to mention "why it is reasonable change".

Understood!
Thanks for sharing the document.
I'm not sure if this change is reasonable.
I read this document, but I didn't understand the current code meaning.
If anyone knows the intent of the current code, I would like to know.
It is OK that we don't know, so let's not change it for now.

I'm not against the effort to simplify it.

I read this document, but I didn't understand the current code meaning.

I have a concern that it may tend to repeat above situation if we didn't explain it with proper context .
(I mean that  when you can explain how we can simplify it to some extent, e.g. According to ref xxx, it should be .... and so on, it is ready to merge it)

I'm not against the effort to simplify it.

I read this document, but I didn't understand the current code meaning.

I have a concern that it may tend to repeat above situation if we didn't explain it with proper context . (I mean that when you can explain how we can simplify it to some extent, e.g. According to ref xxx, it should be .... and so on, it is ready to merge it)

Understood! I agree!
I will add information that I know about this later!
Now I noticed we set customize="never", so we can't see choice-outline in the installer.

I have a concern that it may tend to repeat above situation if we didn't explain it with proper context .

I will add information that I know about this later!

Why I thought this fix was necessary:
According to https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html#//apple_ref/doc/uid/TP40005370-CH100-SW20, I know the following points.

choices-outline contains one or more line, and line contains zero or more line. These specifies the installation-choice hierarchy.
line specifies an id of choice, which contains zero or more pkg-ref. pkg-ref specifies an identifier of a component package.

td-agent has only one component, so we don't need to customize these choices. (We set customize="never")
From the above points, it would be natural to set only one line and one choice like this fix.
However,  I'm concerned that I am not sure what the current code intends.

@kenhys @ashie Thanks for your review!


[2612] Add a new region field against trainees

Context
Changes proposed in this pull request
Guidance to review

 [M] Update HPITT script to import new region information


Response hooks.

Description
Check if it is possible to move parse response data into requests hooks.

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/57


Cant install curl while deploying models with CRD

Tried to deploy example phi model on k3s cluster with nvidia drivers, runtime and toolkit installed (also device plugin deployed)
Each node got 1 GPU with 16Gb of vram.
After successfully installing operator and CLI:
kubectl apply -f https://raw.githubusercontent.com/nekomeowww/ollama-operator/main/dist/install.yaml
go install github.com/nekomeowww/ollama-operator/cmd/kollama@latest

Tried to deploy with following CRD config:
apiVersion: ollama.ayaka.io/v1
kind: Model
metadata:
  name: phi-test
spec:
  replicas: 2
  image: phi
  imagePullPolicy: IfNotPresent
  storageClassName: local-path
  resources:
    limits:
      cpu: 4
      memory: 8Gi
      nvidia.com/gpu: 1
    requests:
      cpu: 4
      memory: 8Gi
      nvidia.com/gpu: 1

Pods start to CrashLoop with following logs:
sudo kubectl logs ollama-model-phi-test-c5d699b74-xbq87 --all-containers

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package curl

Seems like there is the problem with default image or something. Maybe adding apt update && ... will help?
Or perhaps container having trouble connecting to internet but other containers work just fine.
Also looks like container is falling at this step:
https://github.com/nekomeowww/ollama-operator/blob/2717e823f4936ff212bd7d11234f67c132741477/pkg/model/pod.go#L83C4-L83C148

Fixed, added apt update && and released as v0.10.0, but this is still a bit of hard to use. I will implement another dedicated check Job or validator to help to preload the models.

Thank you!
Curl problem got fixed:

but now I cant pull 'phi' image for some reason:

Seems like there is something wrong with models-store or with creating a Puller server idk.
Logs of model-store container (idk why it cant find GPU, but nvm):

then all logs are like that:

Also when trying to add runtimeClassName: nvidia to CRD template:
apiVersion: ollama.ayaka.io/v1
kind: Model
metadata:
  name: phi-test
spec:
  image: phi
  imagePullPolicy: IfNotPresent
  storageClassName: local-path
  RuntimeClassName: nvidia
  resources:
    limits:
      cpu: 4
      memory: 8Gi
      nvidia.com/gpu: 1
    requests:
      cpu: 4
      memory: 8Gi
      nvidia.com/gpu: 1
EOF

I am getting following error:

Error from server (BadRequest): error when creating "STDIN": Model in version "v1" cannot be handled as a Model: strict decoding error: unknown field "spec.RuntimeClassName"
Maybe CRD template got cached somehow or something, but I dont know how to update it.

Okay so the things I did:

Manually deleted everything connected to ollama (operator) from the cluster (StatefulSets, Services, Deployments, PVC, namespaces etc etc)
Deleted CRDs, rolebindings and clusterroles
Installed operator again
Changed meta: name: from phi-test to phi in model CRD yaml (I guess this is the one fixed the issue)
And its working!
Is this expected behaviour? I thought spec: image: should point to the image of the model, and meta: name: is just name of the CRD created

But still sadly cant use new specs (runtimeClassName etc), still thinking that model CRD not updating propertly but I cant figure out how to do it.

Ah thanks for pointing that out. And sorry for jamming you for a while to recreate everything, I am sorry for any of the inconveniences caused by the last release, let me check the workflow on my deployed clusters to fix it.

Thank you again! No problem you doing gods work here!
The problem with name vs image still persists, image-puller tries to pull meta:name and not the spec:image (but its not a big problem)
Sorry to bother you with this questions, but Im quite new to k8s so would greatly appreciate your help.
Do you know what should I do to make ollama-model-* pods schedule on control-plane master nodes as well?
They have no taints, and I guess I should provide custom podTemplate with:
spec:
  tolerations:
  - key: "node-role.kubernetes.io/master"
    operator: "Exists"
    effect: "NoSchedule"
  - key: "node-role.kubernetes.io/contol-panel"
    operator: "Exists"
    effect: "NoSchedule"

but Im getting error stating what I need to provide image for the template (which is expected) so I guess I need to copy full PodTemplate and paste it there with needed settings?
Actually the exact message Im getting is that there are no free nodes with 1 GPU avaliable.
I got 6 PCs each with 1 GPU 5 of which is master-nodes and 1 is agent. When Im trying to deploy 2 models second one getting this error:

Is this connected to taints / restrictions / node-selectors or to some nvidia-device-plugin not allowing to schedule / occupying master nodes?

Let me simplifies your problem:

Provisionable resources:

nvidia.com/gpu: 6, and 6 nodes have their own GPU.

5 nodes with master role (which I guess is control plane role?)
1 node with agent role (which I guess is worker role?)

For debugging resource admission issue, such as insufficient <resource name>, you will need to first get the sufficient info about nodes by running:
kubectl get nodes
kubectl describe node <your-desired-master-node-id>

Besides the debugging suggestions, it looks fine for your tolerations config, and to understand the node-role.kubernetes.io/contol-panel and node-role.kubernetes.io/master, you will need to find out your nodes role too:
kubectl get node <your-node-id> -o json | jq '.metadata.labels'

or you can test your selectors by using:
kubectl get nodes -l node-role.kubernetes.io/master
# or
kubectl get nodes -l node-role.kubernetes.io/control-plane

Hey sorry for long absence.
Basicly tried everything:

Added worker role to control-plane nodes
Added custom labels to control-plane nodes and added correct nodeselectors to podTemplate (I know they are correct because when Im adding label to 1 worker node it schedules pod on it)
Checked for taints, limits and etc - no taints, no hardware or pod limits + added tolerations on all roles to podTemplate (etcd, controle-plane, master, worker)
Checked nvidia and gpu connected labels - same as on worker node
All nodes correctly use GPU (I can confirm it in Rancher, describe node and also can start ollama container by hand with GPU working on control-plane and worker nodes

To be honest Im out of ideas. Maybe I dont understand something basic about kuber deployments.
Added labels dump and descriptions from my master and worker nodes, hope it helps.
master_labels.txt
master_desc.txt
worker_labels.txt
worker_desc.txt


How to pass (return) multiple values to js without them being glued into one string?

Hi guys and @ChrisKnott ,
Trying to pass 3 values to the js from python, and it tells me that values come as a string, check this out:
My js code:

My Python code:

I am sure that python returns them right. But eel seems to be passing it as one string argument. This is what I am getting after running the code.

P.S. I surely can split the values from a string and use them, but maybe there's something I am doing wrong while using eel? Anything helps!

When you return multiple items from Python it actually returns a single tuple.
You need to change it so your callback function takes a single argument, then index from that.
Like pts_count = ret[0] etc

Hello.
I understand what you're saying but can't understand how I am supposed to change them. Please help.

Hi @dragon-slayer875. Please feel free to open a news issue asking for help and we can take a look. Including your code will help us help you.

Sorry for the trouble @samuelhwilliams . I resolved the issue just 10 seconds after putting up the comment.
Thanks for the speedy reply and again sorry for the inconvenience.


Don't stop appending if a single append is missing

This line is why the append wasn't respected in Elixir, but was respected in the Julia repo: https://github.com/exercism/org-wide-files/blob/784d161f18fcee93c93bb28e723f2444a4f9ef4a/.github/workflows/sync-tracks.yml#L165
The exit(0) needs to be a continue.
(Writing this down now because I'm paying attention to the call atm, will fix later)

Great catch! Thanks


Default values for baryonic parameters

We need to make sure of what happens if we pass a parameter structure without baryonic parameters but with the baryons flag set to Yes.

I tried this first in C using ccl_sample_baryons. If the baryons flag is set to Yes but you don't pass any values for the baryonic parameters, default values are assumed. This choice is implemented within ccl_core.c. No-baryons cosmology parameter creation routines basically call the general ccl_params_create routine with baryonic parameters set to -1. This triggers the use of fiducial values from the BCM model.
Likewise for pyccl. If you go to the Power spectrum notebook, you will find an example at the bottom which shows that if you call the nonlinear matter power spectrum from pyccl with the baryons set to Yes, but you don't pass any baryonic parameters, you get the fiducial BCM parameters by default. This is because baryonic parameters are initialised to fiducial in core.py when the Parameters class is defined.
I think this clarified this issue, and there are no action items, so I'll close it.


Fix some angles and generalizations

Fix some voltage and current angles;
Add and fix some generalizations;
Add rich output based on future paper publication

The code is ready to merge.


how to enable additive bias for attention logits using flash attention?

How to enable additive bias for attention logits using flash attention, such as Alibi?

This is not supported in the CUDA implementation of FlashAttention.
We have an experimental implementation in Triton that supports attention bias. You can play with it (it's a self-contained python file) to see if that works for your case.

Thanks. I put the triton version to Nvidia/NeMo and run FP16 inference on V100  with bloom-560M model(alibi PE.). the result seems reasonable but it is different from pure torch version attention. Any clue about the difference please？
BTW: Is there any plan to implement it using cuda？

I'm surprised it (at least the forward pass) worked on V100, I've only tested on A100.
Regarding numerical error, you want to compare
(FlashAttention in fp16 - standard attention in fp32) vs (standard attention in fp16 - standard attention fp32).
Most of the time FlashAttention gets smaller or around the same numerical error than standard attention.
The CUDA implementation doesn't support attention bias.

OK. Finally, both training and inference worked like a charm on A100. The difference bettween triton version of flash attention and standard attention disappeared.
Thanks for your excellent effort!
One more question please: Can triton version of flash attention work with BF16 data type?

One more question please: Can triton version of flash attention work with BF16 data type?

Yes, it supports bf16. I've tested it with an older version of Triton (mentioned in the file).

does it work on my local machine or is necessary in need GPU for it to run this model?
i tried to load a model on my local machine with 15GB of ram but it's stuck model loading because of the size of the model.
There is any way to run it on the local machine? if so please guide me on what the additional parameter needs to pass
`import transformers
import torch
config = transformers.AutoConfig.from_pretrained(
'mosaicml/mpt-7b',
trust_remote_code=True
)
config.attn_config['attn_impl'] = 'triton'
model = transformers.AutoModelForCausalLM.from_pretrained(
'mosaicml/mpt-7b',
trust_remote_code=True,
config=config,
torch_dtype=torch.bfloat16
)
model.to(device='cuda:0')`


i18n(fr): add missing syncKey to various pages

Description
This PR updates the French version of the manual-setup, guides/customization, and guides/site-search pages with the changes from #2087.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/customization.mdx
Localization changed, will be marked as complete.

fr
guides/site-search.mdx
Localization changed, will be marked as complete.

fr
manual-setup.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


There is an error where the placeholder of a worker is not displayed.

Bukkit: Paperspigot 1.13.2
Plugin: Jobs Reborn 4.15.2
jobConfig: https://pastebin.com/Cmx7PLFi
Desc: There is an error where the %jobsr_total_workers%, %jobsr_totalplayers_[jname/number]% placeholder of a worker is not displayed.
Image: https://imgur.com/a/M9QT31t

Where you using this placeholder?

Where you using this placeholder?

i found reason
if i change fullname:
Example)
Woodcutter:
fullname: test
placeholder does not work.
Video: https://youtu.be/XIm50IOsIXY

Where you using this placeholder?

We also found a bug that increases the number of workers by two.

https://github.com/Zrips/Jobs/commit/7271bda0c592025959d3cc2d9343eb3ef6d98a61


Portable theme

Nord theme for Putty / Kitty portable
To use the Nord theme you must edit your session file.
The sessions files are located inside your portable folder ex: D:\Kitty\Sessions
Colour0\216,222,233\
Colour1\216,222,233\
Colour2\46,52,64\
Colour3\46,52,64\
Colour4\46,52,64\
Colour5\216,222,233\
Colour6\59,66,82\
Colour7\76,86,106\
Colour8\191,97,106\
Colour9\191,97,106\
Colour10\163,190,140\
Colour11\163,190,140\
Colour12\235,203,139\
Colour13\235,203,139\
Colour14\129,161,193\
Colour15\129,161,193\
Colour16\180,142,173\
Colour17\180,142,173\
Colour18\136,192,208\
Colour19\143,188,187\
Colour20\229,233,240\
Colour21\236,239,244\

Replace the Colour entries with the ones above.

Ho,
It's a good script you've done here.
Thank a lot.


viola-theme is not navigated

I install October with viola-theme but when I select menu item, slideshow is moved but the content is not moved at all.
http://localhost/octobercms/#about
http://localhost/octobercms/#services
http://localhost/octobercms/#offer
http://localhost/octobercms/#contact
Is-it caused by javascript code used in One Page October Theme ?
Any suggestion will be appreciated.

It seems to be broken. The partials are not getting rendered into the HTML.
Therefore the links you mention can not work :(


ISSUE: Publishing views breaks variables

Publishing views gives an error:
ErrorException (E_ERROR) Undefined variable: adminlte
I'm extending the published layout
@extends('vendor.adminlte.page')
On line 99 of page.blade.php while building menu calls a $adminlte var that is not defined in the published view.
I'm publishing to add js scripts to every page (apparently the basic page layout is not including my app.js).
Switching back to vendor layouts meanwhile.

Is the issue actual?

I have the same issue, and i looking for a solution

Did you try @extends('adminlte::page')?


Extra signer UTxO when minting

Summary
When building a transaction where we mint tokens and pay them to a pkh, at the outputs there’s a UTxO with only minAda as its value that has no reason to exist. Seeing the balance of such a transaction seems that it comes from the UTxO where the transaction deducts the fees.
Steps to reproduce the behavior
Try in the emulator an operation like
{-# INLINABLE mkPolicy #-}
mkPolicy :: () -> ScriptContext -> Bool
mkPolicy _ _ = True

coinMintingPolicy :: Scripts.MintingPolicy
coinMintingPolicy = mkMintingPolicyScript
    $$(PlutusTx.compile [|| Scripts.wrapMintingPolicy mkPolicy ||])

{-# INLINABLE coinCS #-}
coinCS :: CurrencySymbol
coinCS = scriptCurrencySymbol coinMintingPolicy

coinTokenName :: TokenName
coinTokenName = "coinToken"

mintingOperation
    :: forall w s
    .  Contract w s Text ()
mintingOperation = do
    pkh <- Contract.ownPaymentPubKeyHash

    let val = assetClassValue (Value.assetClass coinCS coinTokenName) 200

	lookups = Constraints.mintingPolicy coinMintingPolicy
        tx      = Constraints.mustMintValue val
               <> Constraints.mustPayToPubKey pkh (val <> minAda)

    ledgerTx <- submitTxConstraintsWith @Any lookups tx

That mints any amount of a coin and pays to a pkh. The outputs of a transaction like this always have an extra UTxO with only minAda that belongs to the pubkey which pays the fees.
If we paid the minted tokens to a different pkh than the one paying fees the problem remains.
Actual Result
We printed ledgerTx, a CardanoTx value that represents the above transaction. Their txOutputs and txMint fields looks like this
txOutputs = [
  TxOut {
    txOutAddress = Address {
      addressCredential = PubKeyCredential 80a4f45b56b88d1139da23bc4c3c75ec6d32943c087f250b86193ca7,
      addressStakingCredential = Nothing
    },
    txOutValue = Value (Map [(,Map [(\"\",45994238)])]),
    txOutDatumHash = Nothing
  },
  TxOut {
    txOutAddress = Address {
      addressCredential = PubKeyCredential 80a4f45b56b88d1139da23bc4c3c75ec6d32943c087f250b86193ca7,
      addressStakingCredential = Nothing
    },
    txOutValue = Value (Map [(,Map [(\"\",2000000)])]),
    txOutDatumHash = Nothing
  },
  TxOut {
    txOutAddress = Address {
      addressCredential = PubKeyCredential 80a4f45b56b88d1139da23bc4c3c75ec6d32943c087f250b86193ca7,
      addressStakingCredential = Nothing
    },
    txOutValue = Value (
      Map [
        (,Map [(\"\",2000000)]),
        (ddfaa51476c09e1534c81ad0a4c6c44276683727cacecae737e47dbb,Map [(\"coinToken\",200)])
      ]
    ),
    txOutDatumHash = Nothing}],
    txMint = Value (Map [(ddfaa51476c09e1534c81ad0a4c6c44276683727cacecae737e47dbb,Map [(\"coinToken\",200)])])

Expected Result
That UTxO with only minAda should not exist - those minAda are “inside” the UTxO that pays the fees.
Describe the approach you would take to fix this
No response
System info
OS: Ubuntu
Version: 20.04
Plutus: c330fc60d0cd174743c95de71e5c404b5008f186

It turns out part of our balancing code assumes you don't specify an output for the minted value, and that balancing will take care of it. This is a wrong assumption, and we will fix it. A short term workaround is to remove the <> Constraints.mustPayToPubKey pkh (val <> minAda) line.

But what if you need to pay (val <> minAda) to a different wallet? You need the constraint and the extra utxo of the signer will be still there.

Indeed, in that case there's no workaround. But see #267 for progress with fixing this bug.


to get unique htmls with stackexchange api

This can be achieved by getting fairly popular Qs from a specific time frame, making vids, and remembering last time frame to move on, closer to the present day


group.all_* are not shown if used in group views

Home Assistant release (hass --version): 0.55.0
Python release (python3 --version): Python 3.4.2
Component/platform: group
Description of problem:
group.all_lights, group.all_devices, group.all_automations are not shown if used in group views

Expected:
group.all_lights, group.all_devices, group.all_automations are shown as if it was on the default view
Problem-relevant configuration.yaml entries and steps to reproduce:
group:
  lights_view:
    view: yes
    icon: mdi:lightbulb
    entities:
      - group.all_lights
  info_view:
    view: yes
    icon: mdi:settings
    entities:
      - group.all_devices
      - group.all_automations

Hi,
generated groups are hidden by default. If you use them in your views, you should customize them:
customize:
  group.all_automations:
    hidden: false
  group.all_switches:
    hidden: false

I experienced this as well a few weeks back, i really think default behavior shouldn't be hidden on all but the default biew, but thats just me.

Thanks, @milanvo but is it documented anywhere?

Not found in doc, I get it from forums:
https://community.home-assistant.io/t/group-with-all-automation-items/13364/12
and also confirmed here:
#4312

Just created PR for group component doc.
https://github.com/home-assistant/home-assistant.github.io/pull/3659

#3659 was merged.


Description field added to elastalaert events

Partially fix #662

Can you resolve conflicts please :)

Can you resolve conflicts please :)


Add quoting for sync all columns

resolves #4423

Problem
When the sync_all_columns incremental option is used, the columns that are added and dropped are not quoted. This means that DBT will throw an error.
Solution
Add adapter.quote() around column names.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[ ] This PR includes type annotations for new and modified functions

@cla-bot check

Thanks for taking the time to open this PR @DTchebotarev! Since opening, we've decoupled dbt Adapters from dbt Core, and this code now lives in a separate repo: dbt-adapters.
A consequence of the decoupling is that PR can't be merged anymore as is, so we're closing it. For more context see #9171.
The linked issue has already been transferred. Please don't hesitate to re-open your proposed code changes within this PR in the dbt-adapters repo.


Add option to output transactions as a CSV

The following PR gives the ability to output the transactions command as comma separated values.
I'm afraid I haven't been able to write a suitable test as the current test suite doesn't work for me. The test_transactions test, assumes each item takes 3 lines. But if an item has a comment, it takes 4 lines.

Thank's very much for PR! I was actually thinking about adding tablib support which would allow the user to specify the format of the output file as well (yaml, csv, json, etc.)
Feel free to take a look at that (and implement it if you want ; ).
I'll take a look at the PR and failing test (definitely not your fault so don't worry about it) in the next couple of days.


No ScribbleHub novels loading

As of today, none of my Scribblehub novels are able to update. Scribblehub shows zero results in the search tab, and when I try to view the details of my Scribblehub novels, I just get this screen:

I think they added cloudflare


Update README to mention Discord secrets

Without the secrets the Worker will either do nothing or error silently, and I couldn't find them mentioned elsewhere.
Not 100% sure if there's some better way to show these two commands, and maybe we could mention the token is only required if publishing is needed? But this should do for a simple mention rather than leaving it unsaid and letting the user figure it out.
Changes are very welcome!

Oh actually it messed it up on the commit and wasn't as nice as the preview I tried, let's see if I can fix it up a bit

Oh GitHub :^)

There we go


Special characters in display name crashes App.

Issue discovered by user --
I just found one minor issue: I added a request with a display name containing a '%' sign and was able to save this request on the phone. But it wasn't sent to the Pebble. Also all changes I did afterwards (for other requests) were only saved on the phone but not sent to the Pebble. After removing the '%' all worked again as expected.

Not reproducible on emulator. Must use phone.

Updated code
Unescape is deprecated. Works in modern browsers. PebbleKitJS handles all special character handling except %.


Added TrainCatalogBase.TrainTestData xref

Added Microsoft.ML.TrainCatalogBase.TrainTestData xref for greater clarity.

Thanks, @luisquintanilla!


1.20 High Mspt

Found a critical error when having full shulkers be accessed by the mod, even 20 full shulkers connected to the connector and being viewed can cause mspt to rise from 15-75
If you have full shulkers in chests and then viewed by tom's storage it does less damage but for 250 shulkers being in chests causes Mspt to go up by 35
Is there any way to fix this? I am guessing it's due to the mod trying to sort and read what every shulker has in the system.
For now we have split our shulkers out of the storage and just manually find them.

I also have this problem in my server, whenever I access the terminal, the tps goes down and the mspt goes up
strangely, accessing the terminal in a different dimension does not appear


Update version to 1.1.88-15 on production

Update version to 1.1.88-15

:bell: @Expensify/mobile-deployers :bell: - The Update Protected Branch workflow has failed because this PR was not mergable.
If you are the deployer this week, please resolve the error and merge this PR to continue the deploy process.


including workertest in code coverage

Current coverage is 44.72%

Merging #187 into master will increase coverage by +1.78% as of 30427ab

@@            master    #187   diff @@
======================================
  Files           40      41     +1
  Stmts         3621    3931   +310
  Branches       338     365    +27
  Methods          0       0
======================================
+ Hit           1555    1758   +203
- Partial        103     113    +10
- Missed        1963    2060    +97

Review entire Coverage Diff as of 30427ab

Powered by Codecov. Updated on successful CI builds.

Only config change and no code changes. Config change validated using the code coverage results published in CodeCov site. So merging the PR without LGTM from other committers.


Unable to build example from docs page

Hello team!
When I try to run the "Getting started" example of the following page:
https://jpa.kapsi.fi/nanopb/docs/index.html
I get an error in Atollic TRUEStudio:
..\Src\main.c: In function 'main':
..\Src\main.c:80:2: error: variable 'stream' has initializer but incomplete type
  pb_ostream_t stream= pb_ostream_from_buffer(buffer, sizeof(buffer));
  ^~~~~~~~~~~~
..\Src\main.c:80:23: warning: implicit declaration of function 'pb_ostream_from_buffer' [-Wimplicit-function-declaration]
  pb_ostream_t stream= pb_ostream_from_buffer(buffer, sizeof(buffer));
                       ^~~~~~~~~~~~~~~~~~~~~~
..\Src\main.c:80:15: error: storage size of 'stream' isn't known
  pb_ostream_t stream= pb_ostream_from_buffer(buffer, sizeof(buffer));
               ^~~~~~
..\Src\main.c:81:2: warning: implicit declaration of function 'pb_encode' [-Wimplicit-function-declaration]
  pb_encode(&stream, Example_fields, &mymessage);
  ^~~~~~~~~
..\Src\main.c:80:15: warning: unused variable 'stream' [-Wunused-variable]
  pb_ostream_t stream= pb_ostream_from_buffer(buffer, sizeof(buffer));
               ^~~~~~

The compiler used is arm-atollic-eabi-gcc.
Is it related to the example being incorrect, or is Atollic not set correctly?

The example on that page does not show the #includes that are needed. I updated it now to have them also.
For a complete example, see here:
https://github.com/nanopb/nanopb/blob/master/examples/simple/simple.c

It fixed it, thanks!
One small thing though: when I use max_size option in the .proto file, i get an error:
Command.proto:7:31: Option "(nanopb)" unknown.
My .proto file:
syntax = "proto2";

message Command {
    required string name = 1 [(nanopb).max_size = 40];
}

My option file (it is in the dame folder, and has the same name):
(nanopb).max_size 		max_size:40
What do I do wrong?

Again missing includes, namely import "nanopb.proto";

I added that as well:
syntax = "proto2";

import "proto/nanopb.proto";

message Command {
    required string name = 1 [(nanopb).max_size = 40];
}

But now I get another error:
proto/nanopb.proto: Import "google/protobuf/descriptor.proto" was not found or had errors.
proto/nanopb.proto:137:8: "google.protobuf.FileOptions" is not defined.
proto/nanopb.proto:141:8: "google.protobuf.MessageOptions" is not defined.
proto/nanopb.proto:145:8: "google.protobuf.EnumOptions" is not defined.
proto/nanopb.proto:149:8: "google.protobuf.FieldOptions" is not defined.
Command.proto: Import "proto/nanopb.proto" was not found or had errors.

Yeah, you'll probably need to fix your include paths, something like -I path/to/nanopb/generator/proto should work.

Like so?
protoc --nanopb_out=. Command.proto -I.\nanopb\generator\proto\
pause

Update: with the following cmd commands:
protoc --nanopb_out=. -proto-path=d:\github\nanopb-<IP_ADDRESS>-windows-x86\nanopb-<IP_ADDRESS>-windows-x86\generator\ Command.proto
pause

I got the following error:
Unknown flag: -p

Yeah, protoc is a bit picky about include paths. Just read the error message and add -I. or something.


Update proofs after MIR changes

The proofs have to be updated now, as the IR certificate handling has changed. In particular, we do not force register any stake credentials any more. Instead, we drop any instantaneous rewards at the reward update application if the corresponding stake credentials are not registered at that time.

the proofs are: 15.1 Preservation of Value, and 15.2 Non-negative Deposit Pot