Time.delay (Native.Signal.delay) has no kids

The delay function creates a node in the signal graph with no kids. This means any module using delay cannot be opened in the reactor debugger, because the following code in debug.js will throw an error:
function addAllToDict(node)
	{
		nodesById[node.id] = node;
		node.kids.forEach(addAllToDict);
	}
	nodes.forEach(addAllToDict);

node.kids is undefined for an output-delay-output-n node (where n is the delay in millis).
I don't know much about the signal implementation so I don't know if the lack of kids is intentional, but if it is the debugger code should account for this. Otherwise it's impossible to use the debugger on code with delay which is a bummer.

Oh interesting. I had been wondering why the debugger stopped working for https://github.com/AlexNisnevich/kalevala after I started using delay.
I second that the debugger should account for this somehow. Or at least it should be documented somewhere that using delay breaks the debugger.

Thanks for the report! I think it may make sense to move this to the elm-reactor repo. cc @vilterp to confirm or deny :)

I am trying to be more intense about closing issues. I think the resolution here is "move the issue to this repo" so I'm just gonna commit to it. Thanks again for reporting this!

Signal.delay creates an input and an output; I think if the output gets registered as a kid of the given node the reactor will be fine. I'll submit a PR; it should be like a one line change.

I didn't see your reply Pete and posted this.
Feel free to close it if you'd like.

Replied there, thanks!

Thanks for working through this together! :D


Uncaught TypeError: Cannot read property 'top' of undefined

[Enter steps to reproduce below:]

Just launched Atom and got a msg to create the below issue
...

Atom Version: 0.166.0
System: Mac OS X 10.10.2
Thrown From: minimap package, v3.3.3
Stack Trace
Uncaught TypeError: Cannot read property 'top' of undefined
At /Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:353

TypeError: Cannot read property 'top' of undefined
  at MinimapView.module.exports.MinimapView.updateScrollY (/Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:353:64)
  at MinimapView.updateScrollY (/Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at MinimapView.module.exports.MinimapView.updateScroll (/Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:368:6)
  at MinimapView.updateScroll (/Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at /Users/jeremiah/.atom/packages/minimap/lib/minimap-view.coffee:268:8

Commands

Config
{
  "core": {
    "themes": [
      "seti-ui",
      "base16-tomorrow-dark-theme"
    ]
  }
}

Installed Packages
# User
git-tab-status, v1.3.0
minimap, v3.3.3
seti-ui, v0.3.6

# Dev
No dev packages

/cc @atom/core

Please see #195.

@abe33 sorry about that. I need to be diligent about updating the packages as opposed to only the app.
Thanks!!


Use exact mass computed with help of PSI-MOD to account for electrons and protons

Special attention to trimethylation

Done


 Radix Sort puts the elements in order by comparing the digits of the numbers.
Have you read the Contributing Guidelines on Pull Requests?
Yes

I am interested in this issue;
I can add the radix sort algorithm .

@Cruel-Crab I have created this issue as I am interested in implementing it too. :)

I would like to work on this issue under DWOC

Pls assign @atarax665 @shraddhavp . I have submitted a PR for my previous issue

assigned @KartikeySharma

I would like to work on this issue under DWOC

whcih language you want to code?

I saw just now that Radix Sort has already been implemented.
The current algo in the repository works only for non-negative numbers
I am modifying it to work for negative numbers too.

Why was this issue closed? @shraddhavp

Why was this issue closed? @shraddhavp

not closed just a bit confusion

Ok

This issue has been resolved
PR #1817

This issue has been resolved
PR #1817

I would like to work on this issue under DWOC

whcih language you want to code?

c++

I would like to work on this issue under DWOC

whcih language you want to code?

c++

Pls close this issue as this issue has been resolved @shraddhavp

Pls close this issue as this issue has been resolved @shraddhavp


publish all core and abstraction packages on their publish feed as preview

For the beta release we want all the abstraction and core packages to be
available publicly (sonatype) as a preview without
requiring sign-in from consumers.
Related #122
AB#10316

some more details:

[ ] delete the java folders (abstractions/java and others)
[ ] update the links in the table of the main readme
[ ] update the links in the module readmes (/abstractions/readme.md, and others)
[ ] update the getting started page to replace the instructions of private feed by mavenSnapshots (/docs/get-started/java.md)

ah correct, we didn't update the dotnet one when we released the preview, that's probably a task for GA. Can you log an issue in java-core repo so we track it for GA. CC @andrueastman for dotnet. I'm going to go ahead and close this since you've already done the other tings.


Spider Shows no result , waits almost 15 minutes for one metadata

How can i improve this ? It giving so slow crawling i think i am doing something wrong . People wrote minimum 100 torrent an hour , but i think i am doing something wrong . I closed firewall even , but still having same problem , Thanks

Usually internet providers tend to block traffic. Have you tried VPS?

@volknanebo See readme please.


Binder Kernel died either on or just before velocity_graph of basic tutorial

Hello,
I tried running the cellrank tutorial via binder and the kernel died. I also had some trouble getting the tutorial started (had to close after a few minutes as environment wasn't built properly and refreshing worked). Is colab a better solution for these tutorials?

Hi @adamgayoso ,
looks like you've gotten a rather small-ish machine (only 2GBs) - I got lucky (8GBs) and it worked, see the screenshot below:

I also had some trouble getting the tutorial started (had to close after a few minutes as environment wasn't built properly and refreshing worked). Is colab a better solution for these tutorials?

As for environment taking too much time, I wasn't aware of this issue (atm, there's only 1 requirement that could be removed, since it's only needed in 1 of the tutorials [the WOT package]). With colab I have no experience, so I can't tell if it would be better.

I personally think collab would be better, I've encountered similar issues to @adamgayoso using binder to load our tutorials.

Colab is nice, a little uglier than Binder, but always works... unless you have R things you need to demonstrate.

Does collab always require you to log-in into a Google account? I've tried running one notebook from scvi-tools and it always prompts me to log-in. If yes, unfortunately, this is a dealbraker for me.

Indeed it does. Is your concern privacy? For what it’s worth, many many
universities here use google to power email, etc.
On Thu, Aug 12, 2021 at 2:54 AM michalk8 @.***> wrote:

Does collab always require you to log-in into a Google account? I've tried
running one notebook from scvi-tools and it always prompts me to log-in.
If yes, unfortunately, this is a dealbraker for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/theislab/cellrank/issues/694#issuecomment-897503457,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACS3HMA6JHZEEP435OSW2MTT4OK4DANCNFSM5BWQJZRA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

At the very least, a compromise is to offer badges for both services?

At the very least, a compromise is to offer badges for both services?

You're right, as long as there's an option to choose from, I think it's fine.

There were some issues (see #707), but otherwise, the colab should be enabled on the latest (once the docs are up).


Bug: Prevent referential integrity from breaking when the user edits the json file while the application is running

We should force a rewrite of both transactionbook json and addressbook json when commands related to either books are executed. This helps to keep referential integrity just like the references in memory and overwrites potential changes written to json file by the user when the app is running.

This is currently the case:
https://github.com/AY2425S1-CS2103-F13-1/tp/blob/10cc003bfc0e497e8c46e9d3078345718371a86b/src/main/java/spleetwaise/address/logic/LogicManager.java#L64-L76

@rollingpencil Any follow-up required for this? Else, please close the issue.

No further follow up required.


Add author_email and author_phone counts to the dashboard.

Might be interesting to know how often these fields are populated.

LGTM. Merged.


inbound graceful shutdown

I am copying this from admin server shutdown, Thanks for the input. Will try to improve

my understanding:

graceful shutdown runs immediately, blocks on signaled().await
SIGTERM comes, signaled ().await completes
server starts to drain
signaled () is dropped, marking the drain as complete
ztunnel exits immediately

At no point are we waiting for the server to actually exit?
When I tested this, open connections did not block shutdown. With the tweak I mentioned it did

The above order is right.
Just we donot need oneshot channel here, because my test shows only when self.drain.signaled().await; returns, the server.await  could be unblocked

So it seems redundant, that's why i did not add it

The above order is right.
Just we donot need oneshot channel here, because my test shows only when self.drain.signaled().await; returns, the server.await  could be unblocked

But once the drain is dropped the entire app will shutdown. Nothing waits for server.await to finish.
You can try it by simply opening nc connection on ztunnel and then send SIGTERM, it closes immediately before inbound terminates

Understood your point, but with oneshot channel, curious how it can prevent the process exit.
Doesn't  drain.signaled() will trigger the process exit?

Understood your point, but with oneshot channel, curious how it can prevent the process exit.
Doesn't drain.signaled() will trigger the process exit?

No, that will return from await when the process is exited.
let x = signaled ().await // the process has started exiting..
// exit is blocked by `x`
drop(x) // process can now exit

is how it works. Note that there can be multiple copies of it, so it only fully exits once all are dropped

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
8d4063f462eea68e7381fd800ccdd851fbcc0c98
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
32e8736baff3b15f169506037aa574bef82f96b3
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
8d0a9da3f32cb705f4ee8a40a3b263d2376f850d
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
bc0e0233f82cc34675fd2868e59a2c31137ca853
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn another look

ping @howardjohn


Vendor option defaults should not show UI for attributes without xxx-supported

When you have an xxx vendor attribute without a corresponding xxx-supported value, the web interface is incorrectly defaulting to showing a text field instead of omitting the attribute.

[master 7be6928] Don't show vendor options without xxx-supported values (Issue #104)


Update to Commanders Act version 5

As a member of the analytics team I want results to be gathered with the new Commanders Act platform requiring version 5 of the SDKs to be running in mobile applications.
Acceptance criteria

The Commanders Act SDK has been updated.
Integration documentation has been updated if needed.

Tasks

[ ] Update SRG Analytics to version supporting Commanders Act version 5.

Since we discussed to [remove the environment flag[(https://github.com/SRGSSR/srganalytics-apple/issues/62) in SRG Analytics we cannot determine the corresponding flag we were sending in diagnostics report. Shouldn't we also remove it?

Question for @StaehliJ and @amtins: Do you agree we could remove the environment field we send to Snitch in diagnostics reports (see previous message)?
@pyby and I agree this is a good idea since this value has probably been never used anyway.

@defagos I am not against deleting this field, even if we use it from time to time. However, we should not forget to update the specification PerformanceReport.js#L59-L101


sfss Error: missing field bucket, line: 5, column: 1

Same issue as #12, but this time for sfss instead

panic
❯ sfss node
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error("missing field `bucket`", line: 5, column: 1)', D:\a\sfsu\sfsu\src\packages.rs:78:74
stack backtrace:
   0:     0x7ff682871f42 - git_patch_owner
   1:     0x7ff6828895eb - git_odb_object_size
   2:     0x7ff68286e41a - git_patch_owner
   3:     0x7ff682871c8b - git_patch_owner
   4:     0x7ff6828740f9 - git_patch_owner
   5:     0x7ff682873d7a - git_patch_owner
   6:     0x7ff682874981 - git_patch_owner
   7:     0x7ff68287470d - git_patch_owner
   8:     0x7ff68287296f - git_patch_owner
   9:     0x7ff6828743d0 - git_patch_owner
  10:     0x7ff68297ffb5 - git_smart_subtransport_git
  11:     0x7ff6829802c3 - git_smart_subtransport_git
  12:     0x7ff682797e4c - <unknown>
  13:     0x7ff68278d220 - <unknown>
  14:     0x7ff6827825e8 - <unknown>
  15:     0x7ff68278d3e3 - <unknown>
  16:     0x7ff682790133 - <unknown>
  17:     0x7ff68297e3ba - git_smart_subtransport_git
  18:     0x7ff682782748 - <unknown>
  19:     0x7ff68278d3e3 - <unknown>
  20:     0x7ff6827826e8 - <unknown>
  21:     0x7ff68278d3e3 - <unknown>
  22:     0x7ff6827825e8 - <unknown>
  23:     0x7ff68278d3e3 - <unknown>
  24:     0x7ff6827825e8 - <unknown>
  25:     0x7ff68278d3e3 - <unknown>
  26:     0x7ff682790133 - <unknown>
  27:     0x7ff68297e3ba - git_smart_subtransport_git
  28:     0x7ff682782748 - <unknown>
  29:     0x7ff68278d3e3 - <unknown>
  30:     0x7ff682790133 - <unknown>
  31:     0x7ff68297e3ba - git_smart_subtransport_git
  32:     0x7ff682782748 - <unknown>
  33:     0x7ff68278d3e3 - <unknown>
  34:     0x7ff6827826e8 - <unknown>
  35:     0x7ff68278d3e3 - <unknown>
  36:     0x7ff6827825e8 - <unknown>
  37:     0x7ff68278d3e3 - <unknown>
  38:     0x7ff682790133 - <unknown>
  39:     0x7ff68297e3ba - git_smart_subtransport_git
  40:     0x7ff682782114 - <unknown>
  41:     0x7ff68278db7a - <unknown>
  42:     0x7ff682791162 - <unknown>
  43:     0x7ff68297e3ba - git_smart_subtransport_git
  44:     0x7ff6828620e3 - git_patch_owner
  45:     0x7ff68285f292 - git_patch_owner
  46:     0x7ff68285f8f1 - git_patch_owner
  47:     0x7ff682878e4c - git_filter_source_repo
  48:     0x7ffa51ed117e - BaseThreadInitThunk
  49:     0x7ffa533042db - RtlUserThreadStart

scoop list
❯ scoop list | ? { $_.Name -eq 'nodejs' }
Installed apps:

Name   Version Source           Updated             Info
----   ------- ------           -------             ----
nodejs 19.0.1  <auto-generated> 2022-11-21 16:24:30 Held package

sfsl (with hooks)
❯ scoop list | ? { $_.Name -eq 'nodejs' }

Name   Version Source  Updated
----   ------- ------  -------
nodejs 19.0.1  Invalid 11/21/2022 9:24:15 PM

Could you attach which version of sfsu are you using and a list of your buckets?

1.1.5

Should be fixed in #47, if you are able to test that would be great, because I am unable to re-create the problem on my machine.


OG Images Not Displaying Correctly - Investigate and Fix Font Issue in Docker

OG images are currently not displaying correctly due to a font issue within the Docker environment. The fonts appear to be missing or not found in the Docker image, despite working fine on my local system.
Steps to Reproduce:

Generate an OG image within the Docker environment.
Observe the image and note the absence or incorrect display of fonts.

Expected Behavior: Fonts should display correctly in the OG image as they do on the local system.
Actual Behavior: Fonts are missing or incorrectly displayed in the Docker-generated OG images.
Possible Cause: The issue might be related to missing or misconfigured font files within the Docker image.
Suggested Solution:

Verify if the necessary font files are included in the Docker image.
Check the configuration paths to ensure that the application can correctly locate the fonts.

https://github.com/loftwah/linkarooie/pull/246


Feature(ci): Build image on pr for testing

Description:
Currently, the CI process does not include building a Docker image when a pull request is opened. This feature request aims to enhance the CI pipeline by automatically building a Docker image associated with the pull request.
Proposed Solution:
Create a workflow that builds a Docker image based on the pull request code. This will allow contributors and maintainers to test changes in an environment that closely mirrors the production setup.
Benefits:

Improved testing coverage: Docker image builds can catch issues specific to the image version early in the development process.
Streamlined testing for contributors: Contributors can easily verify their changes by testing the container before merging.

Additional Information:
I am willing to contribute to the implementation of this feature and can allocate time later this week to work on it. If there are specific requirements or suggestions for the implementation, please provide them, and I'll do my best to assist.

I have been meaning to setup something which will build all 3 docker containers and start them with a basic docker compose  healthcheck like
healthcheck:
test: ["CMD-SHELL", "/bin/bash set -o pipefail; curl --insecure --silent -m 2 http://localhost:8080/ | grep 'Stirling-PDF' || exit 1"]
interval: 60s
timeout: 10s
retries: 3
start_period: 40s
And run it twice, once with AUTH once without...
But never got around to it.. i 100% see the benefit of this and would appreciate the help!

While the basic health checks would help when it comes to things like #531, what comes to mind is PRs which introduce new features or extend existing ones. Pushing an image to a registry can provide maintainers and contributors with a convenient way to test the feature.
It could be perhaps pushed on a need basis, determined by specific a label to the PR . This way, image upload would be selectively triggered for PRs that may require additional testing.

I think this serves two purposes
We can have one to test the PRs and not to push
And another to push for manual testing
And have it controlled by flags?

But I wouldn't want to overload github actions and ideally Devs can test locally

I'd rather provide a script for Devs to use which will build everything locally or something


security issues as reported by 'bandit'

[main]  INFO    profile include tests: None
[main]  INFO    profile exclude tests: None
[main]  INFO    cli include tests: None
[main]  INFO    cli exclude tests: None
[main]  INFO    running on Python 3.6.3
Run started:2018-03-08 12:32:40.819211
Test results:

Issue: [B606:start_process_with_no_shell] Starting a process without a shell.
Severity: Low   Confidence: Medium
Location: sh/sh.py:1400
1399                if call_args["env"] is None:
1400                    launch = lambda: os.spawnv(os.P_WAIT, cmd[0], cmd)
1401                else:

Issue: [B606:start_process_with_no_shell] Starting a process without a shell.
Severity: Low   Confidence: Medium
Location: sh/sh.py:1402
1401                else:
1402                    launch = lambda: os.spawnve(os.P_WAIT, cmd[0], cmd, call_args["env"])
1403

Issue: [B606:start_process_with_no_shell] Starting a process without a shell.
Severity: Low   Confidence: Medium
Location: sh/sh.py:1960
1959                    if ca["env"] is None:
1960                        os.execv(cmd[0], cmd)
1961                    else:

Issue: [B606:start_process_with_no_shell] Starting a process without a shell.
Severity: Low   Confidence: Medium
Location: sh/sh.py:1962
1961                    else:
1962                        os.execve(cmd[0], cmd, ca["env"])
1963

Issue: [B102:exec_used] Use of exec detected.
Severity: Medium   Confidence: High
Location: sh/sh.py:3316
3315            try:
3316                exec(compile(line, "", "single"), env, env)
3317            except SystemExit:

Issue: [B606:start_process_with_no_shell] Starting a process without a shell.
Severity: Low   Confidence: Medium
Location: sh/sh.py:3491
3490            cmd = [py_bin, "-W", "ignore", os.path.join(THIS_DIR, "test.py")] + args[1:]
3491            launch = lambda: os.spawnve(os.P_WAIT, cmd[0], cmd, env)
3492            return_code = launch()

Issue: [B101:assert_used] Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.
Severity: Low   Confidence: High
Location: sh/test.py:212
211
212                 assert len(w) == 1
213                 assert issubclass(w[-1].category, DeprecationWarning)

Issue: [B101:assert_used] Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.
Severity: Low   Confidence: High
Location: sh/test.py:213
212                 assert len(w) == 1
213                 assert issubclass(w[-1].category, DeprecationWarning)
214

Issue: [B108:hardcoded_tmp_directory] Probable insecure usage of temp file/directory.
Severity: Medium   Confidence: Medium
Location: sh/test.py:1681
1680            from os.path import realpath
1681            self.assertEqual(str(pwd(_cwd="/tmp")), realpath("/tmp") + "\n")
1682            self.assertEqual(str(pwd(_cwd="/etc")), realpath("/etc") + "\n")

Issue: [B108:hardcoded_tmp_directory] Probable insecure usage of temp file/directory.
Severity: Medium   Confidence: Medium
Location: sh/test.py:1681
1680            from os.path import realpath
1681            self.assertEqual(str(pwd(_cwd="/tmp")), realpath("/tmp") + "\n")
1682            self.assertEqual(str(pwd(_cwd="/etc")), realpath("/etc") + "\n")

Issue: [B102:exec_used] Use of exec detected.
Severity: Medium   Confidence: High
Location: sh/test.py:2647
2646                # SyntaxError upon compilation
2647                exec("from sh import *")
2648            self.assertRaises(RuntimeError, go)

Code scanned:
Total lines of code: 4519
Total lines skipped (#nosec): 0
Run metrics:
Total issues (by severity):
Undefined: 0.0
Low: 7.0
Medium: 4.0
High: 0.0
Total issues (by confidence):
Undefined: 0.0
Low: 0.0
Medium: 7.0
High: 4.0
Files skipped (0):

Thanks for reporting, but considering the nature of this software, these all look fine


iPad/iOS 15 hardware keyboard leaves white bar at bottom of screen

OS/Web Information

Web Browser: iOS PWA
Local OS: iOS 15.0
Remote OS: macOS 11.2.1
Remote Architecture: Intel x64
code-server --version: 3.12.0

Steps to Reproduce
I've only just started using code-server so sorry if this is a known issue, the closest issue I could find was #3272, but that appears to be a different iOS version. My guess is maybe this bar was to compensate for pre-iOS 15 keyboard widget layout?

On an iPad with a keyboard connected (Magic Keyboard in this case), focus a text field.
A white bar at the bottom of the screen will appear along with the little keyboard widget.
Once deselecting the text field the bar will go away.

Expected
I would hope that the Code window would cover the whole screen. I know the keyboard widget is probably unable to be removed however; you can minimise this widget to just be a little icon in the corner which is perfectly fine.
Actual
A white banner at the bottom of the screen appears, reducing available screen area.
Logs
Doesn't seem likely to be relevant but can provide if needed.
Screenshot
https://user-images.githubusercontent.com/3835991/135344460-93af0bf1-30d1-4cc8-a89e-ef4cd0772016.mov
Notes

This issue can be reproduced in VS Code: No

Thank you for the detailed issue and the video! It makes our lives SO much easier ♥
I feel like this is an iOS level setting that may be configure somewhere in the settings (AFAIK, there's nothing inside code-server that should trigger this). I'm not sure exactly which setting it is, but here's a video of my Settings
My best guess is to turn off "Show Onscreen Keyboard" under Accessibility > Touch > AssistiveTouch
https://user-images.githubusercontent.com/3806031/135356604-745272a8-057b-483a-8f96-65d6370c799e.MP4
Let me know if that works or if you figure it out!

Unfortunately 'Show Onscreen Keyboard' was already off, I tried turning it on but that didn't help either.
I tried using the Safari web inspector from my Mac to inspect Safari on my iPad, but for some reason the inspector crashes on code-server. I'll try update Xcode to get the iOS 15 simulator and see if I have any luck there.
One observation though is on iOS 14 at least, the height on .monaco-workbench is being set to (what seems to be) window.innerHeight on change, so perhaps Safari is misreporting that value. Will come back with further results.

Bummer! I was hoping it might be that.

One observation though is on iOS 14 at least, the height on .monaco-workbench is being set to (what seems to be) window.innerHeight on change, so perhaps Safari is misreporting that value. Will come back with further results.

Interesting! I wonder if that's it. I did find this article where they say:

The hack: Set the minimum height of the document to 100% plus the height of the safe area on top. This will prevent a white bar in the bottom which gets shown since you moved the document “up”.

Do you have access to GitHub Codespaces? I wonder if that happens there as well. I did find this old issue.
Also I think I misunderstood your original question. I see two "white bars" - the big one is the one I thought you were referring to, which is why I said I think this is iOS Settings related. But, it sounds like you're talking about the skinny one, right?

In that case, it seems like this should have been fixed in 1.60.2
But code-server is only on v1.60.0 so this wouldn't be fixed until we upgrade VS Code.

No unfortunately I don't have access to Codespaces. That issue does look exactly like the issue, it was indeed about the skinny bar, rather than the larger iOS one. Great to see it's likely fixed upstream!
What's the rough update cycle like for updating the VSCode version?

What's the rough update cycle like for updating the VSCode version?

Good question! @TeffenEllis is working on updating us soon (I think) so it should be updated in the next release (but I'll let Teffen confirm).
We try to keep up with their releases as best we can.


Remove Custom Frameless Option

Looks like in the 2021.2 builds, the fixed trasparent title bars, so this is supported by the platform by default!
This is a breaking change, so I'll probably wait until 2021.2 becomes real before capping min version to this.

Lol, they removed this again in 2022.1, so I still need it in the plugin.


Search style issues

Hello!
Looks like there is a similar issue with the search container, where it has a horizontal scrollbar at the bottom, I was not able to solve it initially without breaking other stuff 😁

Also, whenever there are no result for the search, the result item is larger than the search bar.

Thanks again for quartz 😄

Hi @juaoose ! Sorry for the late response, swamped in a lot of other work right now. What browser are you using?

Hi @juaoose ! Sorry for the late response, swamped in a lot of other work right now. What browser are you using?

Hey, no worries! I'm using Chrome.

Oh hm, I can't seem to repro this. Are you on Windows? What device are you on?

Yeah I am on windows, Ive been able to reproduce it on multiple machines.
Chrome: Version 96.0.4664.93 (Official Build) (64-bit)
Win:  Edition	Windows 10 Pro
Version	20H2
Installed on	12/5/2020
OS build	19042.1348
Experience	Windows Feature Experience Pack 120.2212.3920.0

fixed by https://github.com/jackyzha0/quartz/commit/7507fd29912015a72f990b23023ae2946c6cd51b ! let me know if this is still a problem for you

Yeah the no results element width is fixed :)


refactor(concurrency): change block_state of TransactionExecutor to A…

…rc<Mutex<_>>

This change is

Codecov Report
Attention: Patch coverage is 65.71429% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 78.03%. Comparing base (9f24dd2) to head (6a24ca9).

Files
Patch %
Lines

.../blockifier/src/blockifier/transaction_executor.rs
60.71%
9 Missing and 2 partials :warning:

...es/blockifier/src/blockifier/stateful_validator.rs
85.71%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@                         Coverage Diff                          @@
##           barak/execute_chunk/commit_chunk    #1927      +/-   ##
====================================================================
- Coverage                             78.04%   78.03%   -0.02%
====================================================================
  Files                                    61       61
  Lines                                  8759     8782      +23
  Branches                               8759     8782      +23
====================================================================
+ Hits                                   6836     6853      +17
- Misses                                 1485     1491       +6
  Partials                                438      438

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

crates/blockifier/src/blockifier/transaction_executor.rs line 67 at r1 (raw file):
Previously, barak-b-starkware wrote…
The issue is the ref cells in the cached state, i.e., the (IIUC, only) alternative is to refactor the 'CachedState' and @noaov1, and I thought it's better for now to add the Arc<Mutex<_>> on the block state

Aptos have a refcell in their state struct. I haven't figured out how they do it. Try to take a look:
https://github.com/igor-aptos/aptos-core/blob/6a2fee68cce24e6bf0b8e64bf23dfb545df35bfb/aptos-move/block-executor/src/view.rs#L152-L158


Binary - Decimal - Octal - Hexadecimal Converter

Describe the project
A website to convert values among Binary, Decimal, Octal and Hexadecimal number systems.
Techologies to be used: HTML, CSS, JS
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

I have knowledge in HTML, CSS and JS, and I would also like to use my programming skills to develop a website that would convert values among the 4 different number systems.
You can check this out: https://swapnilganguly.github.io/NumberSystemConverter-WebDev/
@TusharKesarwani Please assign this issue to me, so that I can start working on this project. Thanks a lot!

Hey! I want to work on this issue

@TusharKesarwani It has been over a week since I had raised this issue. Please assign it to me.

please assign me this issue @TusharKesarwani

Empower me with the opportunity to take on this project and make a significant impact!

@TusharKesarwani It was said that all the issues will be reviewed by 20th June, and today is 21st June. Please look into the matter.

Already present in the repo


Initial Support for Fedora 24

Add support for Fedora 24.
This PR adds initial support for the Fedora distribution, starting with Fedora 24.
Until the next release of PowerShell is compiled against .NET 1.1, the Docker release image uses the CentOS 7 build, but loads in the CentOS 7 version of libicu50 via LD_LIBRARY_PATH.
Closes #1882

Hi @randomvariable, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, MSBOT;

Not added Fedora to https://github.com/PowerShell/PowerShell/blob/master/docker/launch.sh#L32 as it presumably wont work without an initial image on the Docker Hub?

OS X build has hung.

Hi @randomvariable, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Was lazily trying to get Travis to rerun tests as it hung last time ^

Tests passed. This is ready for review.

afaict, lgtm

@randomvariable for the launch.sh question, that should be able to use locally build Docker images, so I think you can add it there no problem. @daxian-dbw will need to update the Docker automated build to get updated images on the hub.

@randomvariable I imagine you did a test past of the build, and tried out the generated package too?

It's my default shell right now...

I reverted this PR because it caused a build break on Ubuntu. Details are in #2970.


[FEATURE] Bucket level monitors expose the bucket params that get stored in alerts in the ctx variable

Is your feature request related to a problem?
Currently, users cannot create alert notifications that include the bucket params configured in the monitor query.
What solution would you like?
Adding the bucket params that would be stored in the alert to the ctx variable would allow users to define alert notification messages that better call out what condition was triggered. It will be important to to not store the entire bucket contents in the ctx, just the params that were in the pipeline aggregation defined for the trigger.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
Add any other context or screenshots about the feature request here.

Hello guys, is anyone working on this?


[3.0 Provider question]: Using nested providers - provider that offloads some functionality to another provider

When implementing an OpenSSL 3.0 provider, is it valid to have one provider load another provider? For instance, I would like to implement specific functionality in my provider while offloading other functionality to the default OpenSSL provider. Do you foresee any potential issues with this design?
e.g. in myprov.c file:
// Example of how SIGNATURE_NEWCTX would be implemented
static void *myprov_sig_newctx(void *provctx, const char *propq)
{
    static OSSL_LIB_CTX *deflt_libctx;
    static OSSL_PROVIDER *deflt_prov;
    EVP_PKEY_CTX *RSActx = NULL;
    // user's provider loads the default provider to offload the actual context creation using
    // standard OpenSSL functionality
    deflt_prov = OSSL_PROVIDER_load(deflt_libctx, "default");
    RSActx = EVP_PKEY_CTX_new_from_name(deflt_libctx, "RSA", "provider=default");
    ....
}

static const OSSL_DISPATCH myprov_sig_funcs[] = {
    { OSSL_FUNC_SIGNATURE_NEWCTX, (void (*)(void))myprov_sig_newctx},
    { 0, NULL }
};
static const OSSL_ALGORITHM myprov_sig_algs[] = {
    { "RSA:rsaEncryption", "provider=myprov", myprov_sig_funcs, "Custom provider" },
    { NULL, NULL, NULL, NULL }
};

You need to ensure that your implementation is not fetched instead (that would be infinite recursion). If you use "provider=default" prop query for the fetch or if the libcontext used does not contain any other provider than default, it should be fine.

Thank you for the quick response! I appreciate your help.
I have one more question to ensure that my intended usage is reasonable. Please let me know if you identify any potential issues with the following usage (this is just an example, but it can be expanded to cover other functionalities).
        int nocache = 0;
        // retrieve signature algorithms from default OpenSSL provider
        const OSSL_ALGORITHM * algs = OSSL_PROVIDER_query_operation(deflt_prov,
                                               OSSL_OP_SIGNATURE,
                                               &nocache);
        // get RSA algorithms pointers
        OSSL_DISPATCH *dflt_funcs = algs[1].implementation;
        // get a NEWCTX function pointer
        OSSL_FUNC_signature_newctx_fn* dflt_fp = (dflt_funcs[OSSL_FUNC_SIGNATURE_NEWCTX-1].function);
        (*dflt_fp)(provctx, propq);

This is much more problematic. This usage pattern basically means all the operations above the context returned from the newctx_fn has to be also done by the default provider. You cannot assume anything about the returned context.  So this usage pattern is good only in case you do only some simple operations such as filtering calls, logging params, etc. Please also note that the key references are opaque inside a provider so you would have to use the default provider also for keymgmt, etc.

Indeed, my intention is to utilize the same approach of offloading operations to the default provider for key management and the majority of signing functions, except for possibly one or two specific signing functions. Since modifying the functionality of the default provider is not feasible, my plan is to create a "wrapper" provider that offloads most of the functionality and only focuses on implementing those specific functions.

I am not sure the approach of simply forwarding the calls is viable for such kind of provider.

Could you please elaborate on the specific challenges or limitations you foresee with this approach? It would be helpful to understand your perspective in order to evaluate alternative strategies or address any potential issues.

The problem you will run into is that the default provider and your code could easily have different internal formats for key material etc.
You would need to include a conversion layer that takes your format and packages it up into OSSL_PARAMs to send to the default provider.  The cost would be prohibitive.

I understand the point you're making. However, as I mentioned previously, my intention is to offload all functionality, including key management, to the default provider. Therefore, the workflow will be similar to that of any app using the default provider, with the exception of a few additional pre/post operations that I will incorporate in some of the functions. These operations will not introduce any new formats or modify OpenSSL formats.

The problem is the additional pre/post operations cannot have access to the key data or the context data inside the default provider. So it is unclear what these pre/post operations can be.

I think we have repeated enough times that each provider's data is completely private to that provider.  I don't see that it should make it impossible to have the proxying provider have its own structures with a pointer to the other provider's data, plus extra fields that belong with the proxying provider, and I see no problem with the proxying provider "wrapping" a produced signature by copying it to a buffer and adding a few bytes before and/or after, completely depending on what the proxying provider is supposed to provide.
I assume that's the sort of thing that you intend on doing, @alaakryeem.  Beware, though, that there may be more details to catch on the fly than you might originally think.  You will probably want to keep a keen eye on the param setters and getters.

I assume that's the sort of thing that you intend on doing, @alaakryeem.

Yes, kind of.

@alaakryeem, what exactly is your provider intending to do? Without any access to key material, you will be quite limited.
Tracing prints would be possible but doing anything cryptographic wouldn't be.

My provider is not intended to interact with or modify any cryptographic functionality or internal key material directly. Its purpose is primarily to perform a few basic operations before or after the actual cryptographic operation, similar to what was mentioned by levitte. Therefore, the focus of my provider lies outside the cryptographic domain.
I believe we have reached a clear understanding now. Thank you all for your input and assistance!

Closing since this is marked as resolved.


RLM-217 Fix MaaS Ceph monitoring

Liberty has been consuming the HEAD of rpc-maas master, changes to that
branch earlier in the month have broken MaaS Ceph monitoring and Liberty
Ceph jobs.
This commit pins to a specific SHA and enables support in rpc-maas for
Liberty Ceph deployments.
Related-bug: https://rpc-openstack.atlassian.net/browse/RLM-207
Issue: RLM-217

recheck_cit_trusty_deploy_ceph
recheck_cit_trusty_deploy_swift

👍  for not blindly tracking master


Errors in console

Image attached below

Can you provide any context information? Which call causes this? How do you initialize/configure the plugin. Have you made sure, you are passing the correct data types to the plugin?
I'm not able to reproduce the error without any further information.

Can you provide any context information? Which call causes this? How do you initialize/configure the plugin. Have you made sure, you are passing the correct data types to the plugin?
I'm not able to reproduce the error without any further information.

When i move player to any direction this error appear in console

I fear I still can't reproduce this. Which version are you using and how are you setting up the plugin? Can you maybe provide a minimum breaking example?

Sorry for late answer, i provide code soon. Very busy (

@borkowsky Any updates? If not I'll close this case on Monday.

I will close this for now.


octoprint: add override for celery and sentry-sdk, remove constraint of sarge

Motivation for this change
Fix build
Fixes #151456
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 151577 run on x86_64-linux 1

2 packages failed to build:

gns3-server
home-assistant

32 packages built:

alerta-server
cura
gns3-gui
moodle-dl
moz-phab
octoprint
python38Packages.celery
python38Packages.django-raster
python38Packages.django-rq
python38Packages.djmail
python38Packages.flower
python38Packages.sarge
python38Packages.sentry-sdk
python39Packages.celery
python39Packages.django-raster
python39Packages.django-rq
python39Packages.djmail
python39Packages.flower
python39Packages.sarge
python39Packages.sentry-sdk
sourcehut.buildsrht
sourcehut.coresrht
sourcehut.dispatchsrht
sourcehut.gitsrht
sourcehut.hgsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht
tribler

nixpkgs-review reveals no new failures, macos 10.15, nixos x86_64 & aarch64


MD parsing issue for req.secure and req.signedCookies on /5x

Repro:

Go to https://expressjs.com/en/5x/api.html
Click on signedCookies on the left navbar.  It doesn't work.
Scroll down manually to the section.  It has some markup rendering issue.

It's due to missed triple backtick in 5x/req-secure.md since this commit in July 11: https://github.com/expressjs/expressjs.com/commit/9cff646b19d9221b89005bd525674c86bd23efad#diff-6469de3e2030180ceaf0f03c2a7e7703R2

I got the PR 👆to fix this.

Ok, closing this so we can track it fix in the PR.


fp.setDate is not a function

I'm using this code:

<Flatpickr bind:value={selectedDateTime} element="#my-picker">

		<input
			type="text"
			class="my-custom-class"
			placeholder="Select Date..."
			data-input
		/>

</Flatpickr>

But I get this error:
Uncaught (in promise) TypeError: fp.setDate is not a function
    at Object.$$self.$$.update (Flatpickr.svelte? [sm]:28)
    at update (index.mjs:1053)
    at flush (index.mjs:1025)
    at update2 (index.mjs:1377)
    at index.mjs:1384

Your example works fine (except that you're using an  tag for what should really be a <button>): https://codesandbox.io/s/serene-northcutt-fgxdh?file=/App.svelte
Seems like something else in your configuration is going wrong. Please make sure you're using updated versions of all dependencies.

I understand that the problem comes when I use that component twice in another component.

Copy & paste in your example and you'll see the error.

I'm sorry I don't have codesandbox account.

On the web IDs must be unique to the page, you cannot use the same id for more than one element on the same page.
Change your IDs to make them unique.
	<Flatpickr bind:value={selectedDateTime} element="#my-picker">

      <input
        type="text"
        class="my-custom-class"
        placeholder="Select Date..."
        data-input
      />

      <button type="button" data-clear>Clear</button>

  </Flatpickr>

  <Flatpickr bind:value={selectedDateTime} element="#my-picker2">

      <input
        type="text"
        class="my-custom-class"
        placeholder="Select Date..."
        data-input
      />

      <button type="button" data-clear>Clear</button>

  </Flatpickr>

If you need to do this programmatically in a component, you can use something like gud to generate a unique ID at runtime.


Overflow Risk Mitigation in Merkle Sum Trees Using keccak256

Problem Statement
@bbresearcher has identified a potential security risk related to overflow in the Merkle sum tree.
This theoretical issue could allow a Prover to generate identical identities for different users under certain conditions, despite having unique usernames.
For example:

UserA's Identity: 0x30644e72e131a029b85045b68181585d2833e84879b9709143e1f593f0000002
UserB's Identity: 0x1

In scenarios where both users have the same currency amount, a malicious Prover could exploit this flaw to provide the same cryptographic proof to different users.
Proposed Changes
To address this vulnerability, we propose the following change, as suggested by @alxkzmn :

Use of keccak256 for Hashing Usernames: Implementing keccak256 to hash usernames significantly enhances collision resistance. This measure is crucial given the assumption of a global cryptocurrency user base of approximately $2^{30}$.

Impact on Security

By utilizing keccak256, we greatly reduce the risk of username collision. The probability of two usernames resulting in the same hash is approximately $2^{-195}$, which is exceedingly low.
This ensures that each username has a unique and secure identity within the MST.
The hashed_username utilizes the full 256 bits produced by keccak256. However, to meet the requirements of the Poseidon hash function used in subsequent cryptographic processes, this output is subjected to a modulo operation to fit within the finite field (Fp) of 254 bits.
This adjustment effectively reduces the bit length by approximately 2 bits, yet this reduction does not meaningfully impact the overall security.

Computational Feasibility
Even with a powerful hashing capability of $2^{30}$ hashes per second, the time required to encounter a duplicate hash result by chance would be about $2.7 \times 10^{21}$ years.
This is calculated using the formula:
$T = \frac{2^{127}}{2^{30}} \text{ seconds} $
where $2^{127}$ is the estimated number of attempts needed to find a collision based on the birthday paradox, highlighting the impracticality of such an event.

For the record, I was suggesting using a hash function whose output size is less than or equal to 254 bits. Therefore, I have a question: can you perform an assessment of collision after modular reduction by 2^254?

I had also considered using SHA-224, which aligns with your suggestion regarding the output size. However, I noted that some applications prefer using a truncated message from SHA-256 because it is simpler and potentially more secure if the truncation is more than 224 bits. According to NIST SP 800-107 Rev.1, Section 5.1, the collision resistance is directly related to the length of the hash output. Therefore, SHA-224 offers a collision resistance strength of 112 bits, whereas a truncated SHA-256 to 254 bits provides 127 bits of collision resistance strength.
However, in this PR, there is no truncation process applied to the hash output for usernames. Instead, we pass the untruncated hash output directly to an Fp instance, which internally applies a modulo $p$ operation. Consequently, the Poseidon hasher would use the input as keccak(username) % p.
It's important to consider that the distribution of hash values modulo $p$ might be less uniform than a directly truncated hash output. For example, the hash results are expected to fall within the range $[0, (2^{256} - 1)]$. When using modulo (p), the hash results are constrained within ranges like $[0, (p-1)]$, [(p), $(2p-1)]$, up to $[(5p), [(2^{256} - 1)]$.
The last range, $[(5p), (2^{256} - 1)]$, is smaller than the others, which contributes to a non-uniform distribution. While this range still spans 252 bits, the slight discrepancy in range sizes may impact the uniformity of hash outputs, although it might be considered negligible given the large space covered by 252 bits.
If we want to avoid this non-uniform distribution, we can use 3bits truncated hash ouput for username, which is less than modulo $p$.


Cannot precompile on v1.10.3

Seems to no longer work on the latest julia version
using StructuralIdentifiability

the error is long. This is the environment:
]Pkg
Status `~/Desktop/Julia Playground/Environment - Temporary/Project.toml`
  [220ca800] StructuralIdentifiability v0.5.7

I believe there is a fix submitted to julia base to account for this.
In the meantime, I believe there is a functionality in Project.toml to force downgrading to 1.10.2 if this package is installed.  That seems a little drastic, one could wait to see if 1.10.4 drops soon.

Hi @TorkelE , thanks for reporting that, yeah this seems to be a bug in Julia 1.10.3:
https://github.com/JuliaLang/julia/issues/54356
A fix should get into Julia 1.10.4 I think.

Seems you guys have it all under control, thanks a lot 🙂. Restricting things to 1.10.2 makes sense, I will do that


feat(grants-collaboration): expose follow for grant

Ticket #3206
Description

Adds api route to expose action for following a grant (grant_followers).
Test changes repeat approach mentioned in #3395

Screenshots / Demo Video
Testing
Automated and Unit Tests

[x] Added Unit tests

Manual tests for Reviewer

[ ] Added steps to test feature/functionality manually

Checklist

[x] Provided ticket and description
[ ] Provided screenshots/demo
[ ] Provided testing information
[x] Provided adequate test coverage for all new code
[x] Added PR reviewers

thanks for catching- updated


Check installed extension

Fixes #918.
Edit: Windows encoding for Unicode is UTF-16 so String::from_utf8 will probably fail unless Vec<u8> is already UTF-8 somehow, which I don't know for sure.

@kjeremy you are using windows, right? Could you check that this works there as well?

The check worked on my W10 machine.
However, I think we might want to output the captured stderr from the command to stderr in case of errors. If some command fails, it would make it easier to see why a command failed.
λ cargo install-lsp
  Installing ra_lsp_server v0.1.0 (\crates\ra_lsp_server)
    Finished release [optimized + debuginfo] target(s) in 1.47s
   Replacing C:\Users\vvvv\.cargo\bin\ra_lsp_server.exe
error: failed to move `C:\Users\vvvv\.cargo\bin\cargo-installCB1EtG\ra_lsp_server.exe` to `C:\Users\vvvv\.cargo\bin\ra_lsp_server.exe`

Caused by:
  Access is denied. (os error 5)

versus running install-code
λ cargo install-code
    Finished dev [unoptimized + debuginfo] target(s) in 0.89s
     Running `target\debug\tools.exe install-code`

will run: cargo install --path crates/ra_lsp_server --force
Error: ErrorMessage { msg: "`cargo install --path crates/ra_lsp_server --force` exited with exit code: 101" }
error: process didn't exit successfully: `target\debug\tools.exe install-code` (exit code: 1)

Yep works for me on windows 10.

@matklad, @kjeremy, @vipentti Thanks. I've spin up a Windows VM to also confirm that it is working.
@vipentti Is it possible to create a issue to address the stderr concern? I think the scope is broader than this PR.

@c410-f3r I think stderr should be an easy fix: passing .stderr(piped()) (https://doc.rust-lang.org/std/process/struct.Stdio.html#method.piped) should work. It's important not to hide stderr.

.stderr(piped()) is the default when calling .output(), it should be .stderr(inherit()).

Modified to match the old behaviour of the status method.

bors r+

Thanks!


Make new tags sentence case

Hey,
Three questions...

How can I make new tags sentence case automatically?

If I have a tag named "Blue" and start typing "blue " with a space at the end, it will act like it wants to create a new (lowercase) tag. Is it possible to trim this check and not switch to "blue" if it has spaces at the end?

When I open the select2 and start typing it acts like I want to create a tag, which is what I want. When that tag is added and I start to type a second time, the pre-selected option is an existing tag that time, instead of what I'm typing. Is it possible to only select a pre-existing option if it's written (case insensitive) the same as what you're typing, every time?

Thank you!

I figured out 1. Just 2-3 left. Thanks for help.
1:
function ucfirst(str) {
	str += ''
	var f = str.charAt(0)
		.toUpperCase()
	return f + str.substr(1)
}
[...]
createTag: function (params) {
	return {
		id: ucfirst(params.term),
		text: ucfirst(params.term)
	}
}

Usage/support questions like these belong on the forums.


Add the other specification of Git rev to Comparing commits

Why:
Closes #19184
Closes #19185
What's being changed (if available, include any code snippets, screenshots, or gifs):
The section describes both ancestry references https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[n/a] This pull request impacts the contribution experience

[n/a] I have added the 'writer impact' label
[n/a] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Signed-off-by: Takuya Noguchi<EMAIL_ADDRESS>

@tnir Thanks so much for opening a PR and linking it to your issue! I'll get this triaged for review :zap:

SME  👍

@cmwilson21 Any updates on this?

👋 @tnir - Just wanted to check in and see if you've have had a chance to look over these suggestions 👀


Auto set the number of max_worker_processes and max_parallel_workers

This PR introduces dynamic configuration for max_worker_processes and max_parallel_workers based on the number of vCPUs on the server:

max_worker_processes: set to the higher value between the number of vCPUs or the minimum value of 16.
max_parallel_workers: set to the higher value between half the number of vCPUs or the minimum value of 8.

This ensures optimal configuration for both small and large servers, adapting to the available resources while maintaining reasonable defaults.

Thanks @klention


Adding a page on scams and security to the accounts guide

Per issue #760 - proposed content for a new page on Scams and Security under the Accounts guide section.
Please squash and merge - apologies for the excessive commits, still getting the swing of git.

Please propose your changes through commits, not comments.  Don't be afraid of pushing hundreds of them, in the end, they'll all be  squashed into a single, nicely-commented commit.


Attach already provisioned ceph rbd/fs to containers

Addresses #6174
You can attach rbd with a command like lxc config device add c1 ceph-rbd1 disk source=ceph:my-pool/my-volume ceph.user_name=admin ceph.cluster_name=ceph path=/ceph
You can attach a fs with a command like:
 lxc config device add c1 ceph-fs1 disk source=cephfs:my-fs/some-path ceph.user_name=admin ceph.cluster_name=ceph path=/cephfs

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Some of your commits appear to be missing the needed Signed-off-by line (or lines when multiple author).
The branch also needs rebasing as it's conflicting on a number of files.
You also likely want to squash a number of those commits together to end up with the structure described in the issue.

Do we need to put the signed-off-by line for merge commits?

I am having trouble figuring out which commits to rebase and add the signed-off-by. Quite frankly, I think I've been going in circles rebasing over and over

We have tried to sign off on this one commit 527f191e which I don't even think should be there anymore, but the Jenkins continues to fail due to missing the sign off. I don't think the commit should even be there since I had squashed the commits and signed them when I first did the rebase.

Yeah, your branch needs rebasing on master, that will drop all those duplicate commits you have in here.
Normally you'd do that by running:

git remote update
git rebase origin/master
git push --force

I think we're going to start fresh with a new branch and a new set of commits since our changes were easy enough to find and reapply. Will close this PR for now


Double query

It's good that you commented on this but I don't really understand why it's necessary? What problem occurs if you don't have a double request?

This really is a thorn in my side.
I think the problem comes from Airtable being a little slow. When the user is submitting new content, we fire off a POST request to add, say, a new station and at the same time we redirect the user to the page that lists all of the stations. This page queries the database for a list of stations, but this often happens before the POST request is fully dealt with, so the rendered list of stations doesn't include the one the user just added.
We tried wrapping the componentDidMount Airtable query in setInterval -- even a 10ms delay was enough -- but this caused other, bizarre problems (3460 errors in the console, for example) so we went with this awful solution.
Do you have any suggestions for an alternative?

Are you waiting to get the POST request's response code before starting the redirect?
If you have the server return a 303 code with the location of the created resource then the user's browser will redirect to it automatically (see this SO answer). This ensures that you don't try and redirect until the right time.
If you are initiating the POST request from React/client-side JS then I think you might need to do the redirect manually. If you do it in the callback of the POST request you can check that the response code is 303 and redirect then.


Add job offers block

Pull Request
Related issue
Closes #483
What does this PR do?

Addition of a new color props to the Tag component
Creation of a new block to display the job offers list + its Storybook story

Note : ⚠ The TODO : Add tests in the code is completely normal. This will be done in an other PR
How to test
Go to the deploy branch and check the Join us! block
You can also yarn storybook and go to Storybook
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

bors merge


1/n align deserialize() to library design

1/n align deserialize() to library design
What
Exclude Previous Run Outputs when performing config.resolve(), aka, model parser .deserialize()
Why
When resolving (deserializing) a prompt, if the prompt as executed before, the output from the previous execution is currently included in the deserialized state. While this was the expected behbaiour in the past, it has become apparent that including previous outputs is counterintuitive and not user-friendly

Stack created with Sapling. Best reviewed with ReviewStack.

#371
#353
-> #352

This was discussed offline w/ @saqadri

What's an example use case of deserialize

Consider this scenario:

First Run

User Prompt: What is a good condiment for a burger? Respond with just the answer.
GPT Response: Mustard

Subsequent Run of the Same Prompt

Expected Behavior: The GPT should replicate its previous answer.
Current Behavior: The GPT adds a new response while retaining the old one.

User Prompt: What is a good condiment for a burger? Respond with just the answer.
GPT previous Response included in request: Mustard

GPT Response: Ketchup
The desired outcome is for the GPT to consistently return only the initial response (Mustard) for repeated prompts, rather than accumulating additional responses

Updated instead in #491


(RFC) Add RISC-V Support

RISC-V is an open standard ISA that's maintained by the non-profit
RISC-V orginization, which has over 100 members today.  More information
can be found at https://riscv.org/ .  Our GCC port is pretty solid as of
7.3.0 -- we recently got more packages built in our Debian port than
IA64 has, for example!
This patch adds support for the RISC-V ISA via GCC 7.3.0 and 8.1.0.
I've tested this via "make check", but I'm afraid that doesn't actually
do anything for this patch so it's not a meaningful test.
We've got a RISC-V setup running already https://cx.rv8.io/, but we'd
love to be part of the official compiler explorer site.

Note:
This is more of an RFC than an actual suggested patch, as I can't figure
out how to add RISC-V to the list of installed cross compilers on the
official site.  Our GNU toolchain is all upstream, so it should just be
a matter of adding "riscv64-unknown-linux-gnu" to a list of target
tuples somewhere.

Signed-off-by: Palmer Dabbelt<EMAIL_ADDRESS>

hi, the downloads and installation of compilers happen through our other repo (/compiler-explorer-images), specifically through this script https://github.com/mattgodbolt/compiler-explorer-image/blob/master/update_compilers/install_compilers.sh
if you could suggest changes to that to make this happen, that would be great

Hi @palmer-dabbelt
As @partouf mentioned, the builds are done by scripts in our sister repo at mattgodbolt/compiler-explorer-image. Note that if I'm not mistaken, a .config coming form crosstool-ng should also be enough given that it's properly set up. I've tried to come up with one by myself for testing pourposes, but I think that whatever you provide would porbably work better.
Let us know if you have any questions either for the .config file or the review comments which are already written.
:)

Thanks.  There's a dependency chain here (crosstool-ng needs support, then needs a release, then compiler-explorer-image needs support).  I'm writing some patches, but it'll be a bit high latency.
Do you want me to leave this open?

I'd open an issue as a reminder instead and close the PR until things are ready to go.
Maybe @mattgodbolt can work something out once he has the time too.

https://github.com/mattgodbolt/compiler-explorer/issues/965


[LLC] Add Documentaion for Input Scheama Shapes

This change adds logic to include a table in the <remarks> section
of a method documentation with information about about the input shape
of the method and gives information about the properties every object
has, if they are required or not, their types, and a description.

Looks like you need to run ./eng/Generate.ps1 for the entire repository.

I would ask for tests, but asking "do the comments exist" is kinda hard.

I can write unit tests for the schema -> doc info stuff if that's helpful.  We do have some coverage via our samples, so we can at least get some notification when the comment shapes change and understand if that was "right" or not.

I'm personally fine w\ a "just eyeball comment changes in the checked in tests/sample" here, but I want Pavel's opinion if possible.

@ellismg - I think you can land this when ready.


Include webpage screenshot in the report

Screenshots are always included in the report.
Please give more details about your use case.

If you have more details about your use case and you are sure the screenshot is included in the source JSON files from Cucumber, please open a separate issue.


Opportunity attack needs a small fix

Creatures don't provoke attack of opportunity when they are invisible or can't be seen by the attacker.
"you can make an opportunity attack when a hostile creature that you can see moves out of your reach" phb 195

Thanks for an awesome quickref btw


Use beman.iterator_interface instead of Boost.StlInterfaces

This is in preparation for this repository becoming a Beman library.
Additionally added UTF_VIEW_BUILD_TESTING and UTF_VIEW_BUILD_PAPER
CMake options with defaults optimizing for the common case.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
477

Relevant Lines:
477

💛  - Coveralls


RuntimeError: CUDA error: device-side assert triggered

Hello Otter team!
When I try to train the luodian/OTTER-9B-INIT model with SN and SD datasets using the instruction_following.py I met some problems
I can't use the SN datasets because image_ids int SN_instructions.json don't match SN.json
In SD datasets I didn't meet this problem but RuntimeError: CUDA error: device-side assert triggered occurs
I turn to stackoverfollow but most of the solutions are for classification problem QAQ
I check the vocab_size and it is correct
how i start training:
export PYTHONPATH=.

accelerate launch --config_file  ./pipeline/accelerate_configs/accelerate_config_fsdp.yaml \
instruction_following.py \
--pretrained_model_name_or_path  /tf/ckpt/OTTER-LLaMA7B-Init  \
--external_save_dir /tf/finetuned \
--mimicit_path  /tf/data/SD/SD_instructions.json \
--images_path  /tf/data/SD/SD.json \
--train_config_ic_path  /tf/data/SD/SD_train.json \
--batch_size  4 \
--num_epochs  9 \
--report_to_wandb \
--wandb_entity  ntu-slab \
--run_name  OTTER-LLaMA7B-densecaption \
--wandb_project  OTTER-LLaMA7B \
--workers  1 \
--lr_scheduler  cosine \
--learning_rate  1e-5 \
--warmup_steps_ratio  0.01

the detailed stack:
&& t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [16,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [17,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [18,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [19,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [20,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [21,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [22,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [23,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [24,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [25,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [26,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [27,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [28,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [29,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [30,0,0] Assertion `t >= 0 && t < n_classes` failed.
../aten/src/ATen/native/cuda/Loss.cu:240: nll_loss_forward_reduce_cuda_kernel_2d: block: [0,0,0], thread: [31,0,0] Assertion `t >= 0 && t < n_classes` failed.
  0%|                                                                                | 0/35982 [00:02<?, ?it/s]
Traceback (most recent call last):
  File "/tf/Otter/instruction_following.py", line 634, in <module>
    main()
  File "/tf/Otter/instruction_following.py", line 579, in main
    train_one_epoch(
  File "/tf/Otter/instruction_following.py", line 115, in train_one_epoch
    loss_mimicit = model(
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/utils/operations.py", line 581, in forward
    return model_forward(*args, **kwargs)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/utils/operations.py", line 569, in __call__
    return convert_to_fp32(self.model_forward(*args, **kwargs))
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/amp/autocast_mode.py", line 14, in decorate_autocast
    return func(*args, **kwargs)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/tf/Otter/otter/modeling_otter.py", line 921, in forward
    output = self.lang_encoder(
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/tf/Otter/otter/modeling_otter.py", line 511, in forward
    return super().forward(*input, **kwargs)  # Call the other parent's forward method
  File "/tf/Otter/xformers_model/llama.py", line 722, in forward
    loss = loss_fct(shift_logits, shift_labels)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/nn/modules/loss.py", line 1174, in forward
    return F.cross_entropy(input, target, weight=self.weight,
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/torch/nn/functional.py", line 3029, in cross_entropy
    return torch._C._nn.cross_entropy_loss(input, target, weight, _Reduction.get_enum(reduction), ignore_index, label_smoothing)
RuntimeError: CUDA error: device-side assert triggered
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

wandb: Waiting for W&B process to finish... (failed 1).
wandb: You can sync this run to the cloud by running:
wandb: wandb sync /tf/Otter/wandb/offline-run-20230720_144301-a6hakqug
wandb: Find logs at: ./wandb/offline-run-20230720_144301-a6hakqug/logs
Traceback (most recent call last):
  File "/tf/anaconda3/envs/otter/bin/accelerate", line 8, in <module>
    sys.exit(main())
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/commands/accelerate_cli.py", line 45, in main
    args.func(args)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/commands/launch.py", line 979, in launch_command
    simple_launcher(args)
  File "/tf/anaconda3/envs/otter/lib/python3.9/site-packages/accelerate/commands/launch.py", line 628, in simple_launcher
    raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['/tf/anaconda3/envs/otter/bin/python', 'instruction_following.py', '--pretrained_model_name_or_path', '/tf/ckpt/OTTER-LLaMA7B-Init', '--external_save_dir', '/tf/finetuned', '--mimicit_path', '/tf/data/SD/SD_instructions.json', '--images_path', '/tf/data/SD/SD.json', '--train_config_ic_path', '/tf/data/SD/SD_train.json', '--batch_size', '4', '--num_epochs', '9', '--report_to_wandb', '--wandb_entity', 'ntu-slab', '--run_name', 'OTTER-LLaMA7B-densecaption', '--wandb_project', 'OTTER-LLaMA7B', '--workers', '1', '--lr_scheduler', 'cosine', '--learning_rate', '1e-5', '--warmup_steps_ratio', '0.01']' returned non-zero exit status 1.

You may refer the PR #217  and checkout to the new fixed branch~

--train_config_ic_path  /tf/data/SD/SD_train.json \ should be --train_config_path  /tf/data/SD/SD_train.json \
It's our bug since we are aiming to divide the training datasets into different groups. But missing to add train_config_path.


fix: resolve utf-8 subject searching error

Proposed change

Fix utf-8 email subject searching
Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR fixes or closes issue: fixes #628

Codecov Report

Merging #630 (9c34a2e) into dev (0feea7b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev     #630   +/-   ##
=======================================
  Coverage   98.50%   98.51%
=======================================
  Files           6        6
  Lines        1340     1344    +4
=======================================
+ Hits         1320     1324    +4
  Misses         20       20

Impacted Files
Coverage Δ

custom_components/mail_and_packages/helpers.py
99.05% <100.00%> (+<0.01%)
:arrow_up:


Too many dependencies for the flatpak package

Hello Here
First of all, thanks for providing flatpak image for the Linux users
It looks there are probably too many unnecessary dependencies:
 flatpak install com.okta.developer.CLI
Looking for matches…

Found similar ref(s) for ‘com.okta.developer.CLI’ in remote ‘flathub’ (system).
Use this remote? [Y/n]: Required runtime for com.okta.developer.CLI/x86_64/stable (runtime/org.freedesktop.Platform/x86_64/19.08) found in remote flathub
Do you want to install it? [Y/n]: y

com.okta.developer.CLI permissions:
    network   file access [1]

    [1] host

        ID                                              Branch            Op           Remote            Download
 1. [✓] org.freedesktop.Platform.GL.default             19.08             i            flathub            88.6 MB / 89.1 MB
 2. [✓] org.freedesktop.Platform.Locale                 19.08             i            flathub            17.6 kB / 318.3 MB
 3. [✓] org.freedesktop.Platform.VAAPI.Intel            19.08             i            flathub             8.6 MB / 8.7 MB
 4. [✓] org.freedesktop.Platform.openh264               2.0               i            flathub           266.5 kB / 1.5 MB
 5. [✓] org.freedesktop.Platform                        19.08             i            flathub           193.9 MB / 238.5 MB
 6. [✓] com.okta.developer.CLI                          stable            i            flathub            16.5 MB / 16.5 MB

For example, does Okta CLI actually require VAAPIand openh264 (both for the video encoding). Platform.GL does look necessary for the CLI tool either

Current OS: Ubuntu 20.10
Flatpak version: 1.8.2-1(from the repo)
Okta CLI version: 0.7.1-1f9781e

Agreed, all of those deps come from org.freedesktop.Platform, but I'll see if we can reduce that.
https://github.com/flathub/com.okta.developer.CLI/pull/6

Thanks for the update!
Now I'm getting this list of dependencies

        ID                                                Branch            Op            Remote            Download
 1. [✓] org.freedesktop.LinuxAudio.Plugins.swh            20.08             u             flathub           287.1 kB / 13.6 MB
 2. [✓] org.freedesktop.Sdk.Locale                        19.08             i             flathub            17.6 kB / 322.4 MB
 3. [✓] org.freedesktop.Sdk                               19.08             i             flathub           386.3 MB / 578.9 MB
 4. [✓] com.okta.developer.CLI                            stable            u             flathub             1.2 kB / 16.5 MB
 5. [✓] org.kde.Platform.Locale                           5.15              u             flathub            17.5 kB / 341.3 MB
 6. [✓] org.kde.Platform                                  5.15              u             flathub             5.5 MB / 384.2 MB

for Okta CLI version 0.7.1
Is KDE platform nesessary for the this CLI tool?

@ruXlab Are there other runtimes that can be used, other than what is listed in the flatpak docs?

@bdemers you're right, it doesn't seem they have a CLI-only runtime.
Thank you :+1:

Thanks for following up!


Enforce numeric separator style in test configuration

https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/numeric-separators-style.md
via https://github.com/prisma/prisma/pull/12476

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


Make c-s to print stacktrace of all threads when it is getting forcefully killed, say getting SIGKILL and SIGABRT.

We have couple of cases when c-s stucks not generating any traffic and even not terminating in time.
To investigate it furthere we need to have ability to see what threads are doing.

Done by https://github.com/scylladb/cassandra-stress/pull/27

Done by https://github.com/scylladb/cassandra-stress/pull/27

cc @emdroid


cannot rename a group

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
MSI/azure-cli (2.0.20)/Microsoft Windows [Version 10.0.17035.1000]/Bash on Windows

I cannot rename a group - is there a way to dot it?

There is not.  You would have to delete that resource group and recreate it.  This is true of most (all?) Azure resources. If you deployed via an ARM template, this would be pretty easy. If not, you could try exporting your resource group, changing the name in the generated template, and redeploying it.


Added jupyter-book feature, originally suggested in #28 by dcherian.

Configuration is set to only render notebooks and not rerun them (see
_config.yml). Jupyter book is built in separate subdirectory (see
notebooks/jupyter-book) to reduce clutter. Added dummy notebook in notebooks
directory.
Note that there is an issue with first-time deployments on using GITHUB_TOKEN.
See https://github.com/peaceiris/actions-gh-pages#-first-deployment-with-github_token.

Hey. Here's the next contribution. It's based on a suggestion from issue #28 by dcherian.
I've found it useful for viewing notebooks on GitHub. In the past I was telling people to use https://nbviewer.jupyter.org/ if they couldn't view a notebook on GitHub. With jupyter-book, I don't have to do this. I just tell people to click on the gihub-pages link and the notebooks can be viewed without a problem.*
They might also be useful for issue #21 . I've been able to get some students to use Binder ('click on the binder link in the Jupyter Book') without too much difficulty. I haven't got loads of feedback from this feature, so it could be useful to get feedback from others who have more experience.
*There is an issue with the first deployment when using GITHUB_TOKEN (see https://github.com/peaceiris/actions-gh-pages#-first-deployment-with-github_token). As far as I know, this can be fixed by setting a personal access token instead. But it seems to me that setting a personal access token might require more explanation, and so using the solution at https://github.com/peaceiris/actions-gh-pages#-first-deployment-with-github_token seems fine to me. Probably best to try all of this out yourself with a dummy project, and see how easy/complicated it is.

This is awesome. Thanks @nenb. I hope I find some time this week to look into this further.
Similarly to #47, how can we make sure that this feature is completely 'opt-in'? The simplest way I could think of, is to have the workflow yaml files in another folder, and then instruct the user to copy them to .workflows. But perhaps someone has a sleeker idea?


Why do we only get python 3.8?

Which packages hinder conda from installing more recent version (e.g. 3.11 which is much faster!). Asked on SO:
https://stackoverflow.com/questions/76858353/possibility-to-track-back-which-packages-hinder-conda-from-installing-most-recen

Apparently because of pymer. Openend an issue

Issue solved by the pymer maintainers. Pymer is now availabe for python > 3.8


wip: break: Remove out-of-place repair modes

Final part of #409 , so fixes #409!

Replaced by #434 and #436


Unable to open setting for zh-Hant

Hello,
https://github.com/AlexxIT/XiaomiGateway3/blob/master/custom_components/xiaomi_gateway3/translations/zh-Hant.json#L29
line 29 has missing comma
        "data": {
          "host": "主機端",
          "token": "密鑰"
          "telnet_cmd": "開啟 Telnet 命令"
        }
log:
Logger: homeassistant.util.json
Source: util/json.py:32
First occurred: 上午12:40:21 (54 occurrences)
Last logged: 下午12:16:43
Could not parse JSON content: /config/custom_components/xiaomi_gateway3/translations/zh-Hant.json
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/util/json.py", line 32, in load_json
return json.loads(fdesc.read())  # type: ignore
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 353, in raw_decode
obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Expecting ',' delimiter: line 30 column 11 (char 907)

Created PR: https://github.com/AlexxIT/XiaomiGateway3/pull/244

Fixed in latest master


✨ AllowToFail in ContainerWithExecOpts

What are you trying to do?
In CI there are many jobs where you need to decide based on there return code  of a command (ok / not ok) how to proceed.
Simple example, upload the artefact if it is not already there If it exists, skip upload.
The current workaround is as described in your docs
https://docs.dagger.io/cookbook#continue-using-container-after-command-execution-fails
Of course, the solution is working. But I have often the case that I want decide the further based on the exit code, and the code gets polluted by writing/reading the exit code into/from files. In view of a better DX it would be great if we can move this into Dagger and hide it from the developer.
For example something like that
_, err := c.WithExec([]string{"curl -f https://example.com/file/v222"}, ContainerWithExecOpts{
		AllowToFail: true,
	})

if err != nil && !errors.Is(err, dagger.ExecNonZero){
  return err
}

Why is this important to you?

Improve the DX
Avoid boilerplate code

How are you currently working around this?
The current workaround is as described in your docs
https://docs.dagger.io/cookbook#continue-using-container-after-command-execution-fails

Of course, the solution is working. But I have often the case that I want decide the further based on the exit code, and the code gets polluted by writing/reading the exit code into/from files.

this is already the case if you want to handle the exit code yourself. This guide (https://docs.dagger.io/cookbook#continue-using-container-after-command-execution-fails) is mostly for pipelines where some command "always" return a status code != 0 and you still need your pipeline to continue.
Here's an example on how to handle status codes:
func main() {
	ctx := context.Background()
	client, err := dagger.Connect(ctx, dagger.WithLogOutput(os.Stderr))
	if err != nil {
		panic(err)
	}
	defer client.Close()

	_, err = client.Pipeline("test").
		Container().
		From("alpine").
		WithExec([]string{"sh", "-c", "exit 20"}).Sync(ctx)

	var execErr *dagger.ExecError
	if errors.As(err, &execErr) && execErr.ExitCode == 20 {
		fmt.Println("failed with 20")
	}
}

ref: #5539

That's also in the cookbook: Handle exit code and unexpected errors.

This is what I need. Close the issue

I'm gonna re-open this one, since I think we can do better here - the cookbook suggestion is fine as a workaround, but I think an option like suggested originally would be good.
It's also not impossible to do - buildkit preserves the failed result for us in ExecError: https://github.com/moby/buildkit/blob/db3aaa3cffb08ddc6707a5c7591c22186b244dfc/solver/llbsolver/errdefs/exec.go#L11-L17. We'd just need to grab the output Mounts for this, and use those instead of our normal outputs.
This might require a bit of upstream tinkering, but should be possible without it (I think).


Can't Find Item In Symbol Table.

I get the below error when I do https://github.com/David-Durst/aetherling/blob/debuggingCoreIR/tests/test_map.py#L85 even though instance inst2$inst1$inst1 is clearly in the symbol table at https://github.com/David-Durst/aetherling/blob/debuggingCoreIR/tests/test_map_flattened.json.test (Note: the file is massive, I can't really get around in it in chrome, but you can clearly see that the file contains this in its symbol table if you search for it  "inst2$inst1$inst0.out_0":["inst2$inst1$inst1","in_0_data_0"]).
This is a problem with CoreIR, right? If its in the symbol table, shouldn't it be able to find the instance?
ERROR: Cannot find instance inst2$inst1$inst1

0   libcoreir.dylib                     0x000000010e6e5302 _ZN6CoreIR9ModuleDef3selERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 818
1   libcoreir.dylib                     0x000000010e6e5559 _ZN6CoreIR9ModuleDef3selERKNSt3__15dequeINS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEENS6_IS8_EEEE + 185
2   libcoreir.dylib                     0x000000010e6e508f _ZN6CoreIR9ModuleDef3selERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 191
3   libcoreir.dylib                     0x000000010ead5e35 _ZN6CoreIR14SimulatorState8setValueERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEERKN4bsim21quad_value_bit_vectorE + 53
4   libcoreir.dylib                     0x000000010ead5dd1 _ZN6CoreIR14SimulatorState8setValueERKNSt3__16vectorINS1_12basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEENS6_IS8_EEEERKN4bsim21quad_value_bit_vectorE + 65
5   libcoreir-c.dylib                   0x000000010e4b578f CORESimSetValue + 207
6   libffi.6.dylib                      0x000000010cba5884 ffi_call_unix64 + 76
7   ???                                 0x00007ffee44f0fa0 0x0 +<PHONE_NUMBER>07328

@dillonhuff can you look at this?

The line in the testbench link is just a comment. Could you send an up to date link to the line where the crash happens?

Is the value you are setting during the crash a port of the top level module under test? Setting a wire value that is not an input is pointless (and therefor not allowed) because the set value will be erased on the next evaluate call anyway.

The behavior of the testbench itself was illegal. You cannot set internal wires in the simulator since that would make the internal state of the circuit inconsistent. I have added a more precise error message than the one that was there before.


Test PR

/test

/ok-to-test

/test istio-presubmit

/test istio-presubmit

/test all

/test all

/test all

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
704f2c6a8581729fb199fd536025175236f6016b
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
f84351d2283140b39b660653981a10454a69310c
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
aa9b18b856d99a14714939867d11905ae117d7d5
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
aa9b18b856d99a14714939867d11905ae117d7d5
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
aa9b18b856d99a14714939867d11905ae117d7d5
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@BenPope: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
aa9b18b856d99a14714939867d11905ae117d7d5
link
/test istio-presubmit

Full PR test history

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@BenPope WDYT to the changes I've made to this repo to get the builds working? Happy to merge this in? Can squash to make things easier later

@JoelSpeed looks fantastic - please do squash

/test all


Cleaning up after the interviews

Need to be deleted

[ ] Qualtrics data (location and email-address)
[x] Email conversations with participants
[x] Interview schedule excel file (including location, email-address)

Chris, please comment on whether you agree with the division regarding deletion or putting on stick.
And feel free to add things that come to your mind.

Any updates on this @Janto91?

As many asked for an update with the results, shall we send an email whose email address we should keep for emailing them the final paper?

We have to send the results to all invited participants anyway (i.e., in the sampling frame; tell you more about it during lunch) so no need to keep these separately.

Feel free to close this once you've deleted the Qualtrics project (added the Qualtrics files in commit 4b6a4225eb7db35861f7809a20df1b9cf21bc393)


Error: Value of type undefined not recognized

Environment details

OS: CoreOS
Node.js version: v8.9.4
npm version: v6.0.0
@google-cloud/spanner version: v1.4.1

Steps to reproduce
(not sure if this will reproduce it but this is what causes it for me)

Setup database with interleaved tables
Run a select to get 50 interleaved records (from multiple different parent tables)
Attempt to delete these cross-parent records using a deleteRows call within a runTransaction block (causes error)

The full error stack is as follows:
Error: Value of type undefined not recognized.
    at ObjectToStructConverter.encodeValue_ (/opt/app/node_modules/@google-cloud/spanner/node_modules/@google-cloud/common-grpc/src/service.js:953:13)
    at Function.GrpcService.encodeValue_ (/opt/app/node_modules/@google-cloud/spanner/node_modules/@google-cloud/common-grpc/src/service.js:528:52)
    at encode (/opt/app/node_modules/@google-cloud/spanner/src/codec.js:224:29)
    at Array.map (<anonymous>:null:null)
    at /opt/app/node_modules/@google-cloud/spanner/src/transaction-request.js:351:31
    at Array.map (<anonymous>:null:null)
    at TransactionRequest.deleteRows (/opt/app/node_modules/@google-cloud/spanner/src/transaction-request.js:349:26)
    at spannerStoresDb.runTransaction (/opt/app/index.js:25:13)
    at /opt/app/node_modules/@google-cloud/spanner/src/database.js:1279:5
    at /opt/app/node_modules/@google-cloud/spanner/src/database.js:804:7
    at <anonymous>:null:null

Another engineer on my team said he has seen this error when doing querying large amounts of data as well if that helps.
Found this while looking around which makes me think calling this function should not throw an error.
https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2008#issuecomment-280864896
Let me know if my assumption there is wrong and I should be wrapping this code with better error handling

🤦♂ just realized I fell into the same trap as mentioned in the previous ticket, destructured using the wrong name and got undefined


Serenity flat design

Looking at the demo i noticed the slight modifications on button designs.

Is this something available in future version ? (i have updated my serenity.web.assets to 3.8.6 but cannot find this design - still having the classic raised buttons).
Thanks volkan, this is giving a more modern design to buttons

The theme is now released in Start#


Update README.md and fix typo in Server.py

Check Readme that It have correct Information

DO check The Readme

I don't use Angular tho... i use Flask for hosting the server

Added requirements.txt


Vault Operator - Allow to change statsd mapping configuration

Is your feature request related to a problem? Please describe.
I want to be able to change statsd configuration
Describe the solution you'd like
Expand Vault Operator spec to include another option where I can set custom statsd mapping configuration
Describe alternatives you've considered
Use default configuration
Additional context
https://github.com/banzaicloud/bank-vaults/blob/main/operator/pkg/controller/vault/vault_controller.go#L1526-L1531

Seems like it got resolved by the linked PR.


add separate jobs to travis-ci builds

Adding different env variables to the test matrix to split the build into multiple jobs. This should speed things up and actually test if it builds on all systems

From 20 minutes to 5, and it tests more than it did before! ^_^


how to replace Install ibfswatch with dynamic link library

I install lbfswatch failed,and how to replace Install lbfswatch with dynamic link library?

Sorry I don't understand the question.


chore: prepare v8.0.11 release

Draft PR to see CI green before tagging and publishing.

Green build: https://travis-ci.org/liferay/liferay-js-themes-toolkit/builds/544144754


dependencies: patch policy.

Clarify the conditions under which patches may be used on external deps.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

CC @wrowe

LGTM

We will have a lengthy discussion about the chromium msvc-cl deliberate breakage on it's own thread, per the new policy. Well summarized, thanks @htuch