Checkbox doc for Validation needs accessibility information adding

🙋 Documentation Request
Validation needs to make it clear that the error must also be indicated in text. The color change is not sufficient for certain color blind users or high contrast users.
🧢 Your Company/Team

We will need to expose the HelpText component (or something like it) so users can add it to the Checkbox + update the api since the current one isn't what we wanna expose.

Guidance from Spectrum Design is that we should expose helptext to checkboxes similar to checkbox groups

What part of help text do we not want to expose?


Closed menu focus issue (page scrolling)

Describe the bug
I'm unable to scroll with keyboard buttons after menu is closed

Which site: dev.phanpy.social

To Reproduce
Steps to reproduce the behavior:

Open top-left menu
Close it by clicking outside
Buttons responsible for scroll (ArrowUp/Down, Cmd+ArrowDown etc) are not working until you click on page again (so it get focused)

Expected behavior
After menu is closed i can scroll with buttons without additional click on page
Screenshots

I think this is fixed, thanks!
Closing


Added Skew code

[duplicated Calvin for Skew]:

Duplicated Calvin folder for Skew, beginning to write Skew files. Calvin files are left for comparison for future PRs between - Calvin and Skew.

[added data structure for skew map]:

Added class ScheduleMapFactory to generate schedule maps
Added class SkewScheduleMap to store hash map and other important info relating to map
Added class SkewVector to store vector of class SkewKeyInfo and other important info for synchronization
Added class SkewKeyInfo to store transaction id and flag to determine if its write or read key

[deleted skew.h]:

Deleted ‘Skew.h’, which contains lock related functions required for Calvin. Skew doesn’t need them.

[wrote SkewExecutor]:

Implemented scheduler for Skew (this is different than sequencer which will determine the order of transaction execution)
schedule_transactions(): create schedule hash map
read_handler(): process for one read key
write_handler(): process for one write key

[added Skew helper functions]:

add_to_map(): add a key’s transaction info into the schedule hash map.
initAllWriteIndex(): init read_count and current_write_index for all the SkewVectors in the schedule_map.

[edited SkewManager.h]:

Initialize schedule_maps
Count batch of transactions
Hold schedule_maps

[changed class names for partitioner and message]:

Changed class names from Calvin to Skew inside SkewPartitioner.h and SkewMessage.h

[edited SkewRWKey.h]:

Add key_toString() to support single schedule map.
Also added the following:
set_write_key_bit()
clear_write_key_bit()
is_write_key()
set_read_for_write_key_bit()
clear_read_for_write_key_bit()
is_read_for_write_key()

[wrote transactions for Skew]:

Add rw_SkewRWKeys to hold all read and write keys in the transaction; prepare for schedule map generation.
Add write_handler function variable to hold write_handler.
Modified search_for_read(), search_for_update(), update() to add keys into rw_SkewRWKeys.

[changed context setting]:

Add time_to_run, time_to_warmup, time_to_cooldown

[edited worker factory]:

Add Skew to WorkerFactory.
Support creating Skew workers and Skew manager.
Also cleared random indentation in CalvinManager.h

[minor changes]:

Minor changes to coordinator.h

[changed asm instruction for M1 comp]:

switched from "pause" to "yield" to compile on M1/M2 mac

[finished debugging crit section]

finished debugging critical section for read/write handlers
cleaned up code, removed logs


Select field should allow for custom icons

Is your feature request related to a problem? Please describe.
For users who don't want to rely on an icon font it would be great if the mwc-select component could support external icons via slotting — much like the mwc-button component.
Describe the solution you'd like
If a user adds an icon inside the mwc-select component by using the slot="icon" attribute, it should render the icon in the position where icons rendered using the icon attribute would be rendered.
<mwc-select>
  <svg slot="icon">
    ...
  </svg>
   ...
</mwc-select>

Describe alternatives you've considered
Currently, there is no other way I know of to get non icon font icons in the mwc-select.
Additional context

I used <mwc-list-item value="3"><i class="mdi mdi-camera"></i> Option 3</mwc-list-item> in my markup and the icon showed in the dropdown, but not when the element was contracted
https://user-images.githubusercontent.com/5256724/139525152-979d5091-b446-4f2c-95be-0272f54a69b1.mov

Should be fixed in M3


Ctrl click sticky header is showing peek view out of viewport

Testing https://github.com/microsoft/vscode/issues/157055
Unexpected behavior here:
It seems to be scrolling to the right spot but the peek view is partially out of view:

The file https://github.com/xtermjs/xterm.js/blob/master/src/browser/Clipboard.ts
Code - OSS @ 380647ccd574049f9f5fb5836b4b28e3088202ac:
Version: 1.71.0
Commit: Unknown
Date: Unknown
Electron: 19.0.12
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000
Sandboxed: No

@aiday-mar This can happen when a symbol has multiple definition locations. In that case we use peek to show all definitions and we need to make sure that revealing works nicer.

This seems like it's still present on today's Insiders
https://user-images.githubusercontent.com/2230985/186279194-bce45183-1129-4112-a752-7ee67de7bb8e.mp4
If it helps to test, this is the file I was using: https://github.com/connor4312/cockatiel/blob/master/src/common/Executor.test.ts

Hi Connor, thanks for your bug. This should be solved with the PR: https://github.com/microsoft/vscode/pull/158887 that was created today. The new behavior is:

The cursor position is still wrong when I try verify on the same file:

Nvm, tested the wrong version due to delayed insiders today


Create Given a linked list of 0s, 1s and 2s, sort it

Hi! Thanks for the PR!
I don't accept any changes at this moment, only maybe fixes to the existing code. Plus, your code is not very related to the competitive programming as it seems.
I am closing this PR, but again, thanks for creating it and for using the repo!


bad link in Working with Multiple Environment

Bad link here
Additional Resources
•Tag Helpers in ASP.NET MVC 6 including the Environment Tag Helper

PR #701

Merged in b5525268ba34ad4abd090657043d129b567fde43


Backup pre ncn-m001 wipe/reboot upgrade log to cephfs config-data buc…

Summary and Scope
Adds a step to upgrade docs to copy /root/output.log from m001 to m002 before m001 is wiped and rebuilt. Also adds a step to copy it to the config-data bucket in S3
Example test
ncn-m002:~ # cray artifacts create config-data pre-m001-reboot-upgrade.log /root/output.log
artifact = "pre-m001-reboot-upgrade.log"
Key = "pre-m001-reboot-upgrade.log"

Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix? No, the config-data bucket only exists in 1.2 install or upgrade
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CASMINST-4403
Change will also be needed in <insert branch name here>
Future work required by [issue id](issue link)
Documentation changes required in [issue id](issue link)
Merge with/before/after <insert PR URL here>

Testing
List the environments in which these changes were tested.
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

/backport release/1.2 release/1.2.5


Force overwriting the symlink to the installed binary did not work

When the specific version (v12) of clang-tools was installed, trying to force overwriting the symlink to the installed library did not work.
ubuntu@CN-L:~/clang-tools-pip$ clang-format --version
clang-format version 7.1.0 (tags/RELEASE_710/final)

ubuntu@CN-L:~/clang-tools-pip$ clang-tools -i 12 -f
clang-format-12 already installed
clang-tidy-12 already installed

ubuntu@CN-L:~/clang-tools-pip$ clang-format --version
clang-format version 7.1.0 (tags/RELEASE_710/final)

Root cause: here return the false directly, also need to check overwrite: bool
https://github.com/cpp-linter/clang-tools-pip/blob/a4f8c90f8abdab261bb58451e0200bfb1bcba06d/clang_tools/install.py#L65

In the following case, when the clang-tools were installed with the apt-get install (Ubuntu), the target link is wrong.
Expect targe path is: /home/ubuntu/.local/bin/clang-format-10
https://github.com/cpp-linter/clang-tools-pip/blob/a4f8c90f8abdab261bb58451e0200bfb1bcba06d/clang_tools/install.py#L127
Actual path: /usr/bin/clang-format-10
(myenv) ubuntu@CN-L:~/clang-tools-pip$ which clang-format-10
/usr/bin/clang-format-10
(myenv) ubuntu@CN-L:~/clang-tools-pip$ clang-tools -i 10
clang-format-10 already installed
clang-tidy-10 already installed

I'm not sure I understand. Did you want to create a symlink to the already installed binary?

This kind of leads into "how to manage installed binaries?" I've been desiring a way to uninstall a binary for quicker testing purposes.

Did you want to create a symlink to the already installed binary?

Yes

The problem is that is_installed() does not check only the target's install path. It checks if the executable's name is able to be called. This means that when you clang-tools -i 12, ➡ is_installed() ➡ subprocess.run(["clang-tidy-12", "--version"])
Let's say there's nothing in the install path "~/.clang-tools" but you have clang-tidy-12 installed from apt
(env) brendan@B-DESKTOP:~$ sudo apt list clang-tidy-12
Listing... Done
clang-tidy-12/focal-updates,focal-security,now 1:12.0.0-3ubuntu1~20.04.5 amd64 [installed]
(env) brendan@B-DESKTOP:~$ ls ~/clang-tools/
<nothing to output>

Now when I go to install v12 (using our pkg) in a specific directory (~/clang-tools), it will detect the binary installed via apt, and it not be aware where the binary was installed:
(env) brendan@B-DESKTOP:~$ clang-tools -i 12 -d ~/clang-tools
/home/brendan/clang-tools directory is not in your environment variable PATH.
clang-format-12 already installed
clang-tidy-12 already installed
As you can see, creating a symlink in this situation is doomed because the binary was not downloaded and installed with our tool. It was instead installed using `apt`. The install path provided (via`-d`) is not the only path that our pkg checks when it looks to see if the binaries are installed.

To find the binary installed via apt, we could use which clang-*-<version>, but this is Linux specific. In Windows, this is equivalent to where in DOS prompt or Get-Command in PowerShell.
However, I think you're only concerned with the binaries that we're installing with this pkg. In that case I think the real solution to this issue is:
--- a/clang_tools/install.py
+++ b/clang_tools/install.py
@@ -59,8 +59,7 @@ def clang_tools_binary_url(

 def install_tool(tool_name: str, version: str, directory: str) -> bool:
     """An abstract function that can install either clang-tidy or clang-format."""
-    if is_installed(tool_name, version):
-        # TODO should probably skip this if `directory` is not in the PATH env var.
+    if Path(directory, f"{tool_name}-{version}{suffix}").exists():
         print(f"{tool_name}-{version}", "already installed")
         return False
     bin_url = clang_tools_binary_url(tool_name, version)
@@ -162,5 +161,6 @@ def install_clang_tools(version: str, directory: str, overwrite: bool) -> None:
             f"directory is not in your environment variable PATH.{RESET_COLOR}",
         )
     for tool_name in ("clang-format", "clang-tidy"):
-        if install_tool(tool_name, version, install_dir):
+        target_downloaded = install_tool(tool_name, version, install_dir)
+        if target_downloaded or (not target_downloaded and overwrite):
             create_sym_link(tool_name, version, install_dir, overwrite)

But this will ignore anything that's already in the PATH env var. So, again, I think this issue is leading to "How to manage the installed binaries?"

We should probably start using the SHA256 checksum provided with the binaries' releases to make sure the latest build of the version is installed.

Yes, that is another problem I mentioned here https://github.com/cpp-linter/clang-tools-pip/issues/23. For this issue is user pass -f but it doesn't work.

So, just to clear things up for me:
Do you want to be able to create a symlink to any installed binary that gets invoked in is_installed()?
Or do you want to only create a symlink to the binaries that this pkg installs?

To be straightforward I want to create a symlink to the binaries that this pkg installs.

Thank you. I can now work within those parameters.

I updated it after your review, please feel free to make changes.


fix: flush error for Startup/Password/SslError

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Should close #7137
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

Test locally it can print out normal error message. (Provide evidence later)


Leo/bsi b soup

As of 9 July, the following is done:

[x] Traversal of BSI webpage, only active certificates

As of 9 July, the following remains to be done:

[ ] Full traversal of archived certificates
[ ] Extraction of all information about a single certificate
[ ] Feed the BSI outputs into CommonCriteriaCert class
[ ] Output the mismatch between BSI source and CommonCriteria.org source
[ ] Select 3 certificates and verify (using hash function) that their reports are the same

This is now done in #247.


Better information when resource returns empty version list

We have been trying to use the concourse S3 resource to hold some state and
been running into some issues that proved hard to diagnose. We think that when
a resource returns an empty array of versions, atc gets confused and the job is
shown as pending.
We have pipeline containing:

an S3 resource pointing to a bucket where we keep our terraform state
a job which runs the terraform command and writes the state to the S3 bucket

resources:
- name: s3-bucket
  type: s3
  source:
    access_key_id: {{aws_key}}
    bucket: piotr-state
    region_name: eu-west-1
    secret_access_key: {{secret_key}}
    versioned_file: vpc.tfstate
jobs:
- name: test-s3
  serial: true
  plan:
  - get: s3-bucket
  - task: echo
    config:
      image: docker:///governmentpaas/bosh-init
      inputs:
      - name: s3-bucket
        path: ""
      run:
        path: date

This is a cut-down version of our pipeline, which runs on concourse-lite and is
used to bootstrap our real concourse installation.
When we run this for the first time, the S3 bucket contains no files matching
the versioned_file parameter passed to the S3 resource ie. the resource is
"empty" and has no versions.

There is no obvious error when clicking on the S3 resource in the UI and the
job is shown as pending.
There is no output from the resource visible in the UI, nothing to indicate
what is going wrong.

We did a bit of debugging and found that the call to check passed in a null
version, as might be expected from reading
http://concourse.ci/implementing-resources.html.
The output from the S3 resource check executable contained an empty array of versions.
When a resource is empty, how should it respond to a check? With an empty array
of versions or a single null version?
If a resource does respond in a way that's unexpected or not allowed by
atc/concourse, we think it would be helpful to make the job show as failed
along with a reason. We spent a fair amount of time thinking that the job
itself was hanging.

A resource returning an empty versions is valid, and what everything stabilizes on (there won't always be something new). It sounds like this is working as expected; if there's no versioned file in the bucket, there are no versions, and so the job can't run. Showing it as "pending" forever with no indication why doesn't help though.
We have a separate story for showing which resource a job is waiting on: https://www.pivotaltracker.com/story/show/99634350
see also #114

Thanks for the response, it looks like our issue is the same as concourse/concourse#114 and the story to show which resource a job is waiting on would have saved us time debugging.
Is there a way for us to indicate our interest in the feature?

@bleach leaving a comment should be enough


Use auditctl to load new rules

This is essential to get this cookbook working on CentOS 7. See the commit messages for details.
On discovering that none of the built in rules work on anything but RHEL or Fedora, I realised that adding support for those other platforms may have been a bit pointless but hey-ho.

This also fix CentOS 6.5/6.6? i noticed it doesn't converge on anything higher then CentOS 6.4

I think I only tested CentOS 7 (and Debian) but I will give 6.6 a try tomorrow.

thanks!

Turns out it's because Chef prepare CentOS their boxes with --excludedocs. This is true for CentOS 7 too but for some reason, the box I have still includes the docs anyway. It's not like they only added that directive recently either. I'm not sure what to do about this other than to exclude CentOS 6 from the built-in suite too. It would work fine on a real system.

Figures, thanks for looking into that part!
:)

Is there any movement on this update? Currently trying to load auditd for CIS ruleset on CentOS 7.1 and it breaks with...
================================================================================
           Error executing action `restart` on resource 'service[auditd]'
           ================================================================================

           Mixlib::ShellOut::ShellCommandFailed
           ------------------------------------
           Expected process to exit with [0], but received '4'
           ---- Begin output of /bin/systemctl restart auditd ----
           STDOUT:
           STDERR: Failed to issue method call: Operation refused, unit auditd.service may be requested by dependency only.
           ---- End output of /bin/systemctl restart auditd ----
           Ran /bin/systemctl restart auditd returned 4

Note that at the very least, any recipes calling :restart can call :reload and that should work fine. Unfortunately, the auditd cookbook hard-codes a restart once placing CIS rules.

We found that our fixes here were no longer working while the latest cookbook release now works fine so I'll close this.


[VS Code] Joining collaboration session: Request was cancelled

<!--
For Visual Studio problems/feedback, please use the Report

@sky1458 Thanks for reporting the issue, can you please attach liveshare logs to help us diagnose the issue. You can get the logs by running "Export liveshare logs" from VSCode command palette. I am closing the issue as a dupe of #1329 . Please add your comments / logs there


Option for whether lib.rs should be rebuilt after build.rs is rerun

Currently, whenever build.rs is re-run, both lib.rs and main.rs get rebuilt. It would be useful if there were some option to only rebuild main.rs after build.rs is rerun, not both. This wouldn't want to be the default behaviour, as most build scripts will affect content in lib.rs, but some will only affect main.rs, and an option for that would be nice.
This isn't that urgent, and it may not actually want to be built, but it would probably be useful.
This would probably depend on https://github.com/rust-lang/cargo/issues/1162.

I believe this is a duplicate of https://github.com/rust-lang/cargo/issues/1162 because Cargo does not currently ever assume that a binary is the location where a native library should be linked if a library is also present. Cargo will instruct the compiler to link the native library to the Rust library and then purposefully not link the native library to the binary generated.
Unfortunately this means that this is not possible for Cargo to know that a build script (or native dependency) is in fact for just a binary, not a library.

Would it be possible for this to be a configuration though? I realize it isn't going to be what most people want, but it seems like there would be some projects where build.rs only affects main.rs, not lib.rs (where it is used for something other than native library linking).

That sounds reasonable to me, I've opened https://github.com/rust-lang/cargo/issues/1430 on the topic.


Revisit client error when server aborts connection due to MaxConnections (ice protocol)

When an ice-protocol server rejects a new connection because MaxConnections is reached, it aborts the transport connection:
https://github.com/icerpc/icerpc-csharp/blob/c866c086c6e0b2064681351cf0c7c0a1b4f79d61/src/IceRpc/Server.cs#L908
This abort is in turn received by the client as an IceRpcError.ConnectionAborted (fine) or uncategorized error (IceRpcError.IceRpcError). See #2462.
This behavior is problematic because the ConnectionCache "move to the next server address" requires specific error codes, and IceRpcError.IceRpcError (= uncategorized error) is not among them. See #4027.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Popover inside Scrollview not supported?

When attaching a popover to a view inside a scrollView, the popover will remain at fixed position when scrolling. It seems to be impossible to let the popover follow the attached view.
Is this a bug or a missing feature?
ScrollView {
    …
    TextField(…)
    .popover(
        present: $focusedTextField,
        attributes: {
            $0.position = .absolute(
                originAnchor: .top,
                popoverAnchor: .bottom
            )
            $0.sourceFrame = { rectOfTextField }
            $0.sourceFrameInset.top = -16
            $0.rubberBandingMode = .none
            $0.dismissal = .init(
                mode: .none,
                dragMovesPopoverOffScreen: false
            )
        }
    ) {
        Templates.Container(…)
    }
}

A missing feature unfortunately. It’s a bit tricky to implement
On Sat, May 20, 2023 at 6:09 AM Patrick Horlebein @.***>
wrote:

When attaching a popover to a view inside a scrollView, the popover will
remain at fixed position when scrolling. It seems to be impossible to let
the popover follow the attached view.
Is this a bug or a missing feature?
ScrollView {
…
TextField(…)
.popover(
present: $focusedTextField,
attributes: {
$0.position = .absolute(
originAnchor: .top,
popoverAnchor: .bottom
)
$0.sourceFrame = { rectOfTextField }
$0.sourceFrameInset.top = -16
$0.rubberBandingMode = .none
$0.dismissal = .init(
mode: .none,
dragMovesPopoverOffScreen: false
)
}
) {
Templates.Container(…)
}
}
—
Reply to this email directly, view it on GitHub
https://github.com/aheze/Popovers/issues/85, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4C6PYLWPHTY2A65GNGUXLXHC7BVANCNFSM6AAAAAAYIXM6CE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Large allocations from mempool (primarily isomalloc)

Original issue: https://charm.cs.illinois.edu/redmine/issues/198

There seems to be a serious problem in the memory allocation scheme provided by mempool under the gemini_gni-crayxe layer for AMPI. A simple example shown here demonstrates the problem, which is arising in actual executions of Jacobi and BRAMS, under gemini_gni-crayxe on Blue Waters and JYC with GNU compilers.
Although the mempool source code (mempool.c, mempool.h) looks to have been designed to support up to 1GB of allocation, the actual limit available is much lower. The code example below, which declares a 1 GB array that is sliced across the number of processors in use, will work fine with 8 processors (i.e. 128 MB allocated by each processor), but when it's run with 4 processors (i.e. 256 MB per processor) it fails on every processor with error-messages like
[0] CmiAbort: Mempool-requested slot is more than what mempool can provide as    one chunk, increase cutOffNum and cutoffPoints in mempool
So, apparently there's something that is wrongly limiting the amount of memory that one can allocate, which would mean a bug. Also, 1GB is probably a low limit these days, anyway, as a Cray-XE node has 64 GB of memory, and even when running one process per integer core, each process has 2GB of memory available -- in fact, using fewer tasks per node, each process can use even more than that. So, once the current bug is fixed, it would also be good to increase that current 1 GB limit, if at all possible.
This test was done with GNU compilers (module PrgEnv-gnu loaded) on JYC, using AMPI from a Charm checkout on March-6/2013. I left the example code shown below, plus a Makefile, job-submission script and execution outputs, on JYC under ~cmendes/BUG-AMPI/BUG-3/
AMPI Code Example:
SUBROUTINE MPI_MAIN
include 'mpif.h'

PARAMETER (N=16384)
REAL, ALLOCATABLE :: A(:,:)
INTEGER comm, myrank, p, ierr, m

comm=MPI_COMM_WORLD
CALL MPI_INIT(IERR)
CALL MPI_COMM_SIZE(comm, p, ierr)
CALL MPI_COMM_RANK(comm, myrank, ierr)

m = N/p
ALLOCATE (A(N,m))

CALL MPI_BARRIER(comm, ierr)
print *,"[",myrank,"] Done!"
CALL MPI_FINALIZE(IERR)

END

Original author: Nikhil Jain
Original date: 2013-06-07 01:38:49

Patched in a fix to 6.5 that allows allocations till 1 GB (minus the mempool header size). A generalized solution is been added to master for 6.6.

Original date: 2013-08-28 18:55:37

No further complaints from Celso or Alvaro, so presumably this is sufficiently dealt with.


Pull request for Women of Polkadot - Milestone 1

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
[x] I understand that 30% of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

I have read and hereby sign the Contributor License Agreement.

@JustLuuuu asked me to help out a bit. In my opinion all the milestones listed here are quite technical. We removed the only non-technical one and, as a consequence, also reduced the asking price a bit.

I have read and hereby sign the Contributor License Agreement.

Hi @JustLuuuu and @poppyseedDev thanks for the application. I love the idea of creating more initiatives for women in the space, and cool to see that you have already successfully hosted a few side events. However I have to concur with my colleague that none of the deliverables are specific to Polkadot tech, and therefore isn't a great fit for the technical grants program, which aims to focus mainly on Polkadot core tech & tooling. A general website & merchandise platform might be better supported by the DF program or treasury, as mentioned above.
Additionally, just a note regarding the deliverables, typically 0a. - 0e. are reserved for the mandatory deliverables. So I would argue that 0d. Error Logging could be moved further below in the numbered section, and Testing/Testing Guide could be added back in for 0d.

Thank you. We will reconsider our options and proceed once we decide how to proceed. Thank you for your time.


clean up the outgoing links

https://github.com/tim-hub/obsidian-bible-reference/discussions/115

I feel like it does not match a clean UI, so just try to remove them here

Hello! I liked the backlinks because it helps keep track of where in my notes I'm referencing a certain piece of scripture, fully making use of Obsidian's internal linking, which is more helpful than just tags.
Would it be possible to revert this feature, but add the option of choosing where the backlink appears? e.g. either at the header, or in the body text before the tags

Technically, it is outgoing links in Obsidian, they are not backlinks. :)

Backlinks in Obsidian are the links other notes link to current notes.
Outgoing links are the current note to the other notes.

Anyway, just to clarify, I am not again this feature, there are 2 issues here:

The UI, it makes the rendering logic more and more complicated, some users prefer simpler UI, others prefer more function, this is very hard to balance.

The Link format, Obsidian supports 2 types, dependents on user choice.

[[]] (by default)

We need a proper way to handle the link.

IMHO, I personally prefer pausing this, until we can resolve these 2 issues.

Hello! I liked the backlinks because it helps keep track of where in my notes I'm referencing a certain piece of scripture, fully making use of Obsidian's internal linking, which is more helpful than just tags.
Would it be possible to revert this feature, but add the option of choosing where the backlink appears? e.g. either at the header, or in the body text before the tags

Just another question as a user feedback (if you don't mind) @TheCatchyName

I may miss some perspectives

Do you use tags or use Outgoing links  or both in this case?
#john vs [[john]] which do you think it is better? And why?

@tim-hub

Technically, it is outgoing links in Obsidian, they are not backlinks. :)

Thanks for the clarification, I'm still new to Obsidian and transitioning and setting up from Notion :) Your plugin has been a big help thus far!

IMHO, I personally prefer pausing this, until we can resolve these 2 issues.

I understand the rationale behind this, I'll make do for now! If I think of any suggestions I'll do my best to make them where necessary.

Do you use tags or use Outgoing links or both in this case?
#john vs [[john]] which do you think it is better? And why?

From what I understand of how Obsidian works, I think I will prefer to have Bible chapters as individual pages, where I can then add themes, ideas, concepts (or even an MOC if the chapter is really dense), hence using e.g. [[john]]. Furthermore, outgoing and backlinks provide a way for me to navigate between pages and jump around faster, rather than just centring on a topic of #john and then having to perform another search of the tags to navigate around.
I'll have to do more experimentation though, because I think my understanding isn't full enough to give proper feedback :) Thank you for considering these things!

@tim-hub

Technically, it is outgoing links in Obsidian, they are not backlinks. :)

Thanks for the clarification, I'm still new to Obsidian and transitioning and setting up from Notion :) Your plugin has been a big help thus far!

IMHO, I personally prefer pausing this, until we can resolve these 2 issues.

I understand the rationale behind this, I'll make do for now! If I think of any suggestions I'll do my best to make them where necessary.

Do you use tags or use Outgoing links or both in this case?
#john vs [[john]] which do you think it is better? And why?

From what I understand of how Obsidian works, I think I will prefer to have Bible chapters as individual pages, where I can then add themes, ideas, concepts (or even an MOC if the chapter is really dense), hence using e.g. [[john]]. Furthermore, outgoing and backlinks provide a way for me to navigate between pages and jump around faster, rather than just centring on a topic of #john and then having to perform another search of the tags to navigate around.
I'll have to do more experimentation though, because I think my understanding isn't full enough to give proper feedback :) Thank you for considering these things!

Thanks for sharing 👍

This is a bummer. I did love this feature. But I understand. Would love to see it come back some day.

This is a bummer. I did love this feature. But I understand. Would love to see it come back some day.

@cjulin6651
Do you mind sharing how do you use the outgoing links?  and what do you think about this as well? :) thanks, if you don't mind.

Do you use tags or use Outgoing links or both in this case?
#john vs [[john]] which do you think it is better? And why?

I will start by saying, I am relatively new to Obsidian, so my processes may change some as I go, however, the sole reason I got Obsidian is to study Biblical Literary patterns. This plugin is perfect for me because it allows me to very easily quote and reference particular passages within the note. One of my goals is to visualize how each of these patterns connect to each other and see potential connections that I might have missed based on the books and chapters they connect to. As I connect passages to my notes on themes, I'll see on my graph how those themes connect to particular areas of scripture. (See example below)

To accompany this, my notes and file structure is built so that each book of the Bible has its own note that has prebuilt all the possible chapter tags that your app would use when I insert a note (I did this quickly with a chat GPT prompt and then just copy and pasted). That way, it auto connects to the book on the graph. As I use additional chapters in notes, I simply create a blank note for that chapter so that it visualizes on my chart.
(See Genesis note and sidebar below as well as the primary graph).

I don't use the tag (at least not yet), because I played with both links and tags when formatting it, but found that, for my particular purposes, links look better when you are tracing the themes. Tags are useful for search, links are better for the visual element.

I will start by saying, I am relatively new to Obsidian, so my processes may change some as I go, however, the sole reason I got Obsidian is to study Biblical Literary patterns. This plugin is perfect for me because it allows me to very easily quote and reference particular passages within the note. One of my goals is to visualize how each of these patterns connect to each other and see potential connections that I might have missed based on the books and chapters they connect to. As I connect passages to my notes on themes, I'll see on my graph how those themes connect to particular areas of scripture. (See example below)

To accompany this, my notes and file structure is built so that each book of the Bible has its own note that has prebuilt all the possible chapter tags that your app would use when I insert a note (I did this quickly with a chat GPT prompt and then just copy and pasted). That way, it auto connects to the book on the graph. As I use additional chapters in notes, I simply create a blank note for that chapter so that it visualizes on my chart.
(See Genesis note and sidebar below as well as the primary graph).

I don't use the tag (at least not yet), because I played with both links and tags when formatting it, but found that, for my particular purposes, links look better when you are tracing the themes. Tags are useful for search, links are better for the visual element.

Thanks for sharing how you use it.
It is amazing.

Thanks for sharing how you use it.
It is amazing.

I appreciate that! I'm quite excited with the ability to study the Bible in Obsidian

@TheCatchyName @cjulin6651  this should be backed in 2.3.0 release


UWP ARM build error

Describe the bug
I'm trying to build latest master branch of MR WebRTC for HoloLens 2 (UWP ARM), but I'm facing the issue with perl assembler preprocessor. The x86 and amd64 versions are building fine, the problem only appears when I try to compile ARM version.
To Reproduce
Steps to reproduce the behavior:

Setup environment
Clone the repository
Build
According to https://microsoft.github.io/MixedReality-WebRTC/manual/building-windows.html

Expected behavior
Builded plugin
Screenshots

Environment

MR-WebRTC master  branch
Architecture: UWP ARM
Target device: HoloLens 2

I have never seen this I think but I'd say you have a missing dependency. Please check the dependency lists here and here. Which variant of Perl do you have installed? I only ever tried with Strawberry Perl.

I have never seen this I think but I'd say you have a missing dependency. Please check the dependency lists here and here. Which variant of Perl do you have installed? I only ever tried with Strawberry Perl.

FWIW, I think Jerome is right on target.  I recently did a build on a newly installed dev machine on which I had neglected to install Perl.  It appears to be needed only for the ARM build.  I don't remember the exact errors, but they were similar to those reported here.  I installed Strawberry Perl and all was well.

FWIW, I think Jerome is right on target.  I recently did a build on a newly installed dev machine on which I had neglected to install Perl.  It appears to be needed only for the ARM build.  I don't remember the exact errors, but they were similar to those reported here.  I installed Strawberry Perl and all was well.

Thank you very much!
Install Strawberry Perl helped me.

Thank you very much!
Install Strawberry Perl helped me.

Yes it's only for the ARM build and I'll be honest I know nothing about Perl and never tried anything else than just installing that distribution. Glad it worked! I'm closing the issue, feel free to reopen if there's still a problem.

Yes it's only for the ARM build and I'll be honest I know nothing about Perl and never tried anything else than just installing that distribution. Glad it worked! I'm closing the issue, feel free to reopen if there's still a problem.


Add django deployment checks

Refers to TD-150 / TD-342

Add release script with checks
Fix security checks (apart from W009 - secret key < 50 characters)
Fix deprecated field check

Regarding migrations:
When generating migrations for replacement of deprecated field
it showed that survey.show_question_progress was previously
altered to include some help text but the migration was not generated
for this. This is why it is included in the latest migration file.

@syphar Release log for this deployment looks good 👍
-----> Running deployment checks
       System check identified no issues (1 silenced).
-----> Running migrations
       Operations to perform:
         Apply all migrations: admin, auth, contenttypes, sessions, threesixty
       Running migrations:
         Applying threesixty.0005_auto_20210302_1123... OK
-----> Done!


Auto-refactor on file renaming?

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
nvim-tree, nvim-lsp-file-operations,
Description
Hi, I love your work! I use several of the plugins in my own setup, and absolutely love mini.files. Is there a way to enable refactoring of imports on file renaming, similar to nvim-lsp-file-operations for nvim-tree/neotree?
I've tried to mimic the functionality using the mini.files events, but it doesn't seem to work - but I'm a bit of a neovim noob, so not sure if I'm doing something wrong.
Here I'm setting up a listener on the MiniFilesActionRename event, and trying to mimic what nvim-lsp-file-operations does for handling willRenameFiles, but it doesn't seem to do anything

Hi! Thanks!
This kind of action won't be part of 'mini.files' itself, because, yes, utilizing events is the proposed approach here. So I'll convert it to discussion.


Add two steps to create a disk with root.tar.gz for debian

Using GCS path as disk raw source to create disk. Using this disk to create the image. Then we can export image using gce_export tool to export image.
remove image_dest as argument.

Test Result:
hanga-testing-daisy-bkt/debian/debian-9-stretch-v20200730/metadata.json
hanga-testing-daisy-bkt/daisy/hanga/daisy-debian-9-20200730-21:35:30-r4j4b/logs/inst-exporter-debian-9-export-metadata-r4j4b-serial-port1.log

[debian-9]: 2020-07-30T21:47:33Z Running step "export-metadata" (IncludeWorkflow)
[debian-9.export-metadata]: 2020-07-30T21:47:33Z Running step "setup-disks" (CreateDisks)
[debian-9.export-metadata.setup-disks]: 2020-07-30T21:47:33Z CreateDisks: Creating disk "disk-exporterprep-debian-9-export-metadata-r4j4b".
[debian-9.export-metadata]: 2020-07-30T21:47:35Z Step "setup-disks" (CreateDisks) successfully finished.
[debian-9.export-metadata]: 2020-07-30T21:47:35Z Running step "run" (CreateInstances)
[debian-9.export-metadata.run]: 2020-07-30T21:47:35Z CreateInstances: Creating instance "inst-exporter-debian-9-export-metadata-r4j4b".
[debian-9.export-metadata]: 2020-07-30T21:48:25Z Step "run" (CreateInstances) successfully finished.
[debian-9.export-metadata.run]: 2020-07-30T21:48:25Z CreateInstances: Streaming instance "inst-exporter-debian-9-export-metadata-r4j4b" serial port 1 output to https://storage.cloud.google.com/hanga-testing-daisy-bkt/daisy/hanga/daisy-debian-9-20200730-21:35:30-r4j4b/logs/inst-exporter-debian-9-export-metadata-r4j4b-serial-port1.log
[debian-9.export-metadata]: 2020-07-30T21:48:25Z Running step "wait" (WaitForInstancesSignal)
[debian-9.export-metadata.wait]: 2020-07-30T21:48:25Z WaitForInstancesSignal: Instance "inst-exporter-debian-9-export-metadata-r4j4b": watching serial port 1, SuccessMatch: "ExportSuccess:", FailureMatch: ["ExportFailed:"] (this is not an error), StatusMatch: "ExportStatus:".
[debian-9.export-metadata.wait]: 2020-07-30T21:48:35Z WaitForInstancesSignal: Instance "inst-exporter-debian-9-export-metadata-r4j4b": SuccessMatch found "ExportSuccess: exits with return code 0"
[debian-9.export-metadata]: 2020-07-30T21:48:35Z Step "wait" (WaitForInstancesSignal) successfully finished.
[debian-9.export-metadata]: 2020-07-30T21:48:35Z Running step "delete-inst" (DeleteResources)
[debian-9.export-metadata.delete-inst]: 2020-07-30T21:48:35Z DeleteResources: Deleting instance "inst-exporter".
[debian-9.export-metadata]: 2020-07-30T21:49:04Z Step "delete-inst" (DeleteResources) successfully finished.
[debian-9]: 2020-07-30T21:49:04Z Step "export-metadata" (IncludeWorkflow) successfully finished.
[debian-9]: 2020-07-30T21:49:04Z Serial-output value -> source-size-gb:20
[debian-9]: 2020-07-30T21:49:04Z Serial-output value -> target-size-gb:1
[debian-9]: 2020-07-30T21:49:04Z Workflow "debian-9" cleaning up (this may take up to 2 minutes).
[debian-9]: 2020-07-30T21:49:28Z Workflow "debian-9" finished cleanup.
[Daisy] Workflow "debian-9" finished
[Daisy] All workflows completed successfully.
{
  "build_date,": "2020-07-30T21:48:31.482171",
  "version": "20200730",
  "packages": [
    {
      "commit_hash": "'",
      "name": "'google-cloud-packages-archive-keyring",
      "version": "1.2-1"
    },
    {
      "commit_hash": "https://github.com/GoogleCloudPlatform/guest-configs/tree/2f0cd2ab3afc1f44a9eac79307ad969836828242'",
      "name": "'google-compute-engine",
      "version": "1:20200626.00-g1"
    },
    {
      "commit_hash": "https://github.com/GoogleCloudPlatform/guest-oslogin/tree/7b956e59ae133351ddee60cfc471bb9f854c71e3'",
      "name": "'google-compute-engine-oslogin",
      "version": "1:20200507.00-g1+deb9"
    },
    {
      "commit_hash": "https://github.com/GoogleCloudPlatform/guest-agent/tree/a264aa6fcf1436efa0a9ef5885776f7254fdfaba'",
      "name": "'google-guest-agent",
      "version": "1:20200706.00-g1"
    },
    {
      "commit_hash": "https://github.com/GoogleCloudPlatform/osconfig/tree/3d0bf6f002a653949ddba1c27fbbfb7e8f91d38f'",
      "name": "'google-osconfig-agent",
      "version": "1:20200723.01-g1"
    }
  ],
  "family": "debian-9",
  "build_repo": "staging",
  "location": "gs://hanga-testing-daisy-bkt/centos/debian-9-stretch-v20200730/root.tar.gz"
}

/lgtm
and
/hold
bc I want zach to also approve

/lgtm

/unhold

/lgtm


Search for translation sources with custom extensions via make-json

make-json extract JavaScript strings from PO files with .js and .min.js files extensions while generating individual JSON files like it should. But I have JS files with other extensions (for example .tag), which ignored this way.
In /i18n-command/blob/master/src/MakeJsonCommand.php start at 134 line I found code which responsible for it. So there inside iteration it check for each extension and return source if was found. Off course, I can "hardcode" and this will work. Something like:
if ( substr( $file, - 4 ) === '.tag' ) {
    return $file;
}

But my request is in core update from your side, because I think a lot of people will use with feature for their own purposes and there can be a great variety of similar extensions. Feature must be multipurpose for any extension and, desirable, provide this opportunity to programmers at their own discretion (like --extensions=tag argument or something similar). I.e additional to .js and .min.js will search for extensions specified in --extensions argument.
Or maybe you have any other suggestions for resolving my request? I am open to discussion and ready to listen to any suggestions.
Thanks!

Hi!
Have you got some updates about this issue?

No uodate I‘m afraid. I personally haven‘t had time to look into it but it sounds like a feasible enhancement and PRs are more than welcome.
You do have some exotic file extensions I must say :-)


Use in-memory database during (most) tests

The disk I/O incurred by BoltDB is dramatically slowing down tests. It's true that we want the database to be well-tested, but it should be possible to do this without slowing other tests. Otherwise, any test that interacts with the database will need to be marked as a long test.

I'm not sure how ramdisks work but it might be possible for us to mount ram to one of the /tmp folders.

I'm closing this as 'low priority'.
Not that we don't need it, but we have 10 million things to do and I'm trying to keep the focus as narrow as fits the size of our engineering team.


Enable passing plane data to select modules.

Several modules like mirror() and half_of() take normal vector and center-point data.  It would be nice to be able to pass a plane definition [A,B,C,D] where Ax+By+Cz=D in place of the vector, giving both normal and center-point info.
ie:
plane = plane3pt(p1,p2,p3);
mirror(plane) ...

or
plane = plane3pt(p1,p2,p3);
half_of(plane) ...

Implemented in 182688cf025cddd70457535ab582073b6228897a


How to save many-to-many?

Hi! How should I save related objects? I mean, thinking about a post for example that has many tags, and a tag could be in many posts. Should I create the Tag(), the Post() save them in a transaction and then create a TagPost() with the tag and the post fields? Because I've tried something similar in other situation, but turns out that one of the fields of the TagPost (the tag or the post) stay null on the database even the Tag and the Post being saved and the documentation for many-to-many is a little poor on the website although I should say that in general the documentation for aqueduct is awesome and the project itself either (loving it, thank you by the way)

Can you provide the queries you are writing?

Hey @Reductions I have similar question here a example for one-to-many relationship:
class Author extends ManagedObject<_Author> implements _Author {}
class _Author {
  @primaryKey
  int id;
  String name;
  ManagedSet<Book> books;
}

class Book extends ManagedObject<_Book> implements _Book {}
class _Book {
  @primaryKey
  int id;
  String name;
  @Relate(#books)
  Author author;
}

I want to post Author with Books with that json body:
{
    "name": "author11",
    "books": [
      {"name": "book1"},
      {"name": "book2"}
    ]
}

How can I do that post easily without define new model type? What is the best way to do this?
Same question for many-to-many post.


Verify crate with official ABNF

There's an official ABNF for TOML. I'd love to generate documents based on the ABNF and then verify that they parse correctly.
This is a pretty significant project, though!

Maintenance of this crate has moved to the https://github.com/toml-rs/toml repo.  As a heads up, we plan to move toml to be on top of toml_edit, see https://github.com/toml-rs/toml/issues/340.
Closing this out.  If this is still a problem, feel free to recreate this issue in the new repo.


[FEATURE] Add CLI programs for Ed25519 and Ed448

Even though signing and verifying is outside of the scope of ECIES, it'd still be neat to have matching Ed25519 and Ed448 example implementations inside the programs/ collection. A simple CLI with just two parameters as seen in the others is already enough... Keep it simple too!

Programs to be added:

ed25519_keygen
ed25519_sign
ed25519_verify
ed448_keygen
ed448_sign
ed448_verify

Done in a separate repo to keep this one clean:
https://github.com/GlitchedPolygons/eddsac


Increase Camera Zoom Limit

For large objects you can not zoom out far enough...

Usability: The zoom in/out speed of the camera should increase when further away from the center.


Fixed the issue that the date does not automatically update when the month or year changes

Fixed the issue that the date does not automatically update when the
Please select PR type by entering x between [ ].

[x] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Documentation content changes

Fix #39 Not displaying all months while set end date in the Middle of the year. if I Change the year the month and date are not automatically update.


Odata Documentation

I want to add a few articles (and code examples as well) about Odata support in ASP.net core so as required in CONTRIBUTING.md file for complex submissions i opened this issue to get approval for them.
what i have in mind is a simple example of adding odata capabilities on top of existing API and also some tips for scenarios which include  starting a new API project  with odata support from scratch.
also i come across this (https://github.com/aspnet/Docs/issues/9740) open issue about odata so i was wondering should i do it or wait for odata official team.
also i think it worth to mention that im having 1.5+ years experience with ASP.net core and 3+ years experience with C# and ASP.net mvc (.net framework) and also good understanding of odata.

@FIVIL thanks for checking first. @blowdart and @HaoK will make that decision. They'll probably want an outline before you start.

As long as the security implications and mitigations are covered I have no problems.

@FIVIL  can you post an outline here?

@Rick-Anderson  Sure.
as i mentioned earlier what i have in mind contains two separated parts which are

Adding OData support to a existing REST API
Creating a new REST API with OData support

for the first one i do not intend going into details so ill make a single article .
in this single article i will explain how you can add OData support to your existing API with as less modification as possible in your codebase without breaking the existing API routes with backward compatibilities.
in this article i will expand this already existing project in docs, though i might change the model class for better demonstration of OData capabilities by adding some new properties
the outline will look like this:

Overview
-what we are going to build-
Prerequisites
-VS 2017+ and .ner core SDK 2+-
Introduction
-what is OData-
Loading the project
-which as i mentioned in this step i will show how you can load the existing project in VS-
Adding Nuget Packages
-i will use this official package from MS-
Updating Model Class
-adding some new properties to use OData capabilities-
Adding migratings
Registering required services in DI container
Configuring middlewares
-i will show how you can add OData route and also how you can expand your existing API routes using  routeBuilder.EnableDependencyInjection();-
Changes in Controllers
some example
-how to invoke new api methods using OData queries-
Security concerns
-how you can prevent or add some OData features-
Additional resources
ill try to make this article as short and as simple as possible

also i will add some code examples and i might include some screenshots from postman to showing the result of invoking the API
for the second part i intend to make a couple of articles and in them i will go further into details and internals of OData
Outline:
article number 1 -> Overview : what the end result would look like and link to other articles in this series
article number 2 -> complete introduction to OData, explaining that how OData is actually a open specification and .net core libraries, also i will dive into query language and functionalities of OData
article number 3 -> Getting Started

Prerequisites
Creating The Project
Adding Nuget Packages
Running the Project to make sure everything is fine

article number 4 -> adding model classes:
in this step i will use the contos university example which is a well understood example from MS
article number 5 -> Configuring Database:

Adding database context class
Adding migrations

article number 6 -> Configurations of the project:

Adding Services in DI container
Adding middlewares with much more details

article number 7 -> Scaffolding

Scaffolding the Controllers
Applying required changes to the controllers

article number 8 -> Pushing some data into API
article number 9 -> Examples:

querying data
querying a single record
filters
querying  relational data
invoking functions

article number 10 -> Security concerns
so im expecting to do this in at least 3 RRs one for article number 1, one for series of articles in 2nd part and one last PR for the code examples

Looks good to me.
@blowdart and @HaoK  any comments on the outline?

@FIVIL would you be interested in helping @guardrex  with #5106?

@Rick-Anderson Sure, honestly im having some spare time within next few month and i want to get best out of it by contributing to aspnet repos, so im open to help with any task that can be done by community.
also im waiting for @blowdart  and @HaoK  approval for OData doc outline so i can get started on them as well.

I think #5106 provides what I need to perform the update. Within Tratcher's remarks, I see about three aspects missing from the topic. @FIVIL, I'll ping u on the PR to review it if you have time.

@guardrex  sounds great to me, so im waiting to hear from you.

@FIVIL ping me next week if @blowdart  doesn't approve your outline. @scottaddie / @danroth27  please review outline.

Harsh but fair @Rick-Anderson.
Security to 10 maybe? My concern here is, for example, someone reads enough to expose their data because that's what they want to do, without understanding they now have a DoS vector or Information Leak via joins.
Notes in each section to the security section would work though.

@blowdart sure, ill keep your notes in mind.

so im trying to deliver first draft as soon as possible.

@Rick-Anderson
I'm done with the first set of tutorials, however, I will cover more materials in the next set of articles.
you can check out the sample files in:
https://github.com/FIVIL/AspNetCore.Docs/tree/OData/aspnetcore/tutorials/first-odata-api/samples/2.2/TodoApi
and markdown file in:
https://github.com/FIVIL/AspNetCore.Docs/blob/OData/aspnetcore/tutorials/first-odata-api.md
and tell me if they are Ok, so i can send a PR, or if they need any changes
TNX

@FIVIL  looks great. Create a PR then I'll submit some commits to your branch for minor edits.

@FIVIL when you submit the PR, @mention me only so I have a chance to make some edits, then we can mention @blowdart

@FIVIL  I moved two of them over - see https://docs.microsoft.com/en-us/odata/webapi/odata-expand
The last one is in PR at https://github.com/MicrosoftDocs/OData-docs/pull/83


Create Progressive Web App manifest

Is your feature request related to a problem? Please describe.
Rating Tracker is only available in the browser, so the browser navigation is always visible.
Describe the solution you’d like

[ ] A manifest is created, which allows installing Rating Tracker as a PWA e.g. on home screens
[ ] The manifest may be generated by vite-plugin-pwa
[ ] A theme and a background color are declared to render a splash screen (possibly using the primary color, since we cannot distinguish between light/dark mode)
[ ] The app icon shows a white icon on a primary color background
[ ] The app icon is available as SVG, and a maskable version is provided
[ ] The meta tag theme-color is adapted per layout (e.g. with and without sidebar header)
[ ] Check robots.txt for validity, consider replacing it by backend route

Putting this on hold until it becomes clear how this is affected by the presumed removal of PWAs from iOS 17.4.

It would appear that PWAs are not to be removed from iOS 17.4, so this feature is ready to be implemented.

Support for PWAs on iOS is still subpar. Issues include the lack of a splash screen and poor support of light/dark mode switch.


Error object stored on Runnable._trace leaks memory

FYI: In V8, Error objects keep closures alive until the err.stack property is accessed, which prevents collection of the closure (and associated objects) until the Error objects die.
Mocha creates a long-living Error for each Runnable: https://github.com/mochajs/mocha/blob/2303c669ef1b47fef7cf86f5ef486d537033d443/lib/runnable.js#L56.
Would it make sense to either 1. store a string message instead of an Error, or 2. clear Error.stack, or 3. format Error.stack eagerly instead?
See also: https://crbug.com/v8/7142 and https://twitter.com/wSokra/status/935790750188625920.

@schuay Is this a bug in V8?

Webpack's workaround
I don't really think Mocha should be changing any code unless there are widespread problems with this.  If it's a handful of projects having the problem, they should be able to work around it.

if it turns out that this is a "feature" and not a "bug" in V8, then we should modify Mocha, and this seems reasonable:
this._trace = new Error().stack;

then we can just console.error(this._trace) if it triggers.

I wouldn't necessarily call it a bug on the V8 side. Our expectation is that in general Error objects are not long-lived, that not a huge number of them are live at once, and that for most Error objects the stack property will not be accessed.
Lazy stack formatting exploits that to skip expensive work. But that leads to the 'leak' in this case since we need to keep a few objects around in order to be able to format the stack later.
Your proposed solution above will basically format stack eagerly, and depending on how often it's called, may lead to significant slowdown.
So I'm not sure there's currently a perfect solution that will be ideal in all use-cases. In V8, we may be able to avoid keeping the closure alive, which might already improve things significantly.
Would it be an option to avoid exposing stack traces entirely?

@schuay Yes, you're right about the slowdown.
The point of storing the Error is the stack itself.  It's used if someone does this (and yes, code like this gets written; we just get fewer bug reports about it now that we provide a stack):
describe('test suite', function () {
  it('is an async test which is bad', function (done) {
    setTimeout(() => {
      done(); // this test passes
      setTimeout(done); // but this is a problem.
    });
  });

  it('is an async test just minding its own business', function (done) {
    setTimeout(() => {
      // the previous test's error appears somewhere around here,
      // even though this test also passes!
      done();
    });
  });
});

IMO, the "real" solution is one of:

native language support for "zones" or "async hooks" or whatever, because it's painful to connect the dots otherwise, OR
tail call support so that we can run tests in a recursive manner w/o having to break the stack via calls to setImmediate() due to "Maximum call stack exceeded" problems

Mocha could address this by basically implementing @sokra's hack behind a flag, I guess.

ugh, and the Error never goes out of scope because we have to call setImmediate() to avoid call stack problems, right?
maybe someone can spend an afternoon and rewrite the test runner as a for loop 😝

Hmm, I'm not familiar with Mocha at all. Could you elaborate what the problem is in your previous code example?

@schuay So, you call done to tell Mocha your test is finished.  This allows you to do async things (in lieu of Promises) within your test, e.g. setTimeout() or HTTP requests or whathaveyou.
When that async execution is complete, the user executes the done callback, and the test is complete.
But this doesn't necessarily halt execution of the test.  Users can do weird stuff (and they do) like trying to call that done callback multiple times.  This is indicative of a Problem in the user's code.
Given the example as above (repeated):
describe('test suite', function () {
  it('is a good async test', function (done) {
    setTimeout(done);
  });

  it('is a good synchronous test', function () {
    // omitting the parameter means the test is not expected to be asynchronous
    // unless a Promise is returned
  });

  it('is an async test which is bad', function (done) {
    setTimeout(() => {
      done(); // this test passes
      setTimeout(done); // but this is a problem.
    });
  });

  it('is an async test just minding its own business', function (done) {
    setTimeout(() => {
      // the previous test's error appears somewhere around here,
      // even though this test also passes!
      done();
    });
  });
});

We will see output from Mocha like this (roughly):
- test suite
  - is a good async test - **OK**
  - is a good synchronous test - **OK**
  - is an async test which is bad - **OK**
  - is an async test just minding its own business
**ERROR**: done() callback called twice <insert stack trace here> - **OK**

Now, where did we call done() twice?  This is confusing for the user.  We won't know without that stack as saved via this._trace; each test is run in its own setImmediate() callback.
Does that help?

I see, thanks. If you don't necessarily need the full stack trace, another option would be V8's prepareStackTrace API.
Using that, you could fetch e.g. the line/column numbers and the file name of the top frame and skip full stack trace formatting. Once the stack is formatted that way, all internal information (e.g. the closure and receiver of each frame) is freed.
Of course, ensuring that Error objects go out of scope at some point would be the best fix :)
And just FYI, there's also support for async stacks in DevTools / the inspector protocol, although I suppose that won't be relevant for you.

I see, thanks. If you don't necessarily need the full stack trace, another option would be V8's prepareStackTrace API.

Mocha doesn't just run in V8, so we can't use runtime-specific APIs.

And just FYI, there's also support for async stacks in DevTools / the inspector protocol, although I suppose that won't be relevant for you.

It is relevant, actually.  While it means the user will need to open a separate tool to track down what's going on, at least such a tool now exists.
That means it may be OK to simply drop the stack and tell the user to open an inspector to figure it out.  😛
@schuay In what version of V8 was this behavior introduced (specifically, which Node.js version does it correspond to)?

Mocha doesn't just run in V8, so we can't use runtime-specific APIs.

In theory you could check for the existence of Error.prepareStackTrace, but I agree it's not a nice solution.

@schuay In what version of V8 was this behavior introduced (specifically, which Node.js version does it correspond to)?

Hmm, not sure, but it's been roughly one year from looking at git blame. cc @ak239 and @hashseed who will know exactly when async stack traces were released.

Latest Node.js supports inspector bindings, so in theory you can enable async stacks using Debugger domain and then somehow fetch this stack trace.
But I believe that we should provide capabilities in JavaScript runtime which will allow to enable / disable async stacks. Something like Error.captureAsyncStacks(true) and then Error.stack will contain async stacks as well.

this._trace.stack = this._trace.stack;

This is a workaround without functional changes. It forces v8 to "calculate" the stack trace as string.

This is a workaround without functional changes. It forces v8 to "calculate" the stack trace as string.

Accessing stack is enough to force eager formatting and clear internal data, no need to write to it.
But as discussed above, eager formatting is probably to slow to be a viable fix. I think this._trace should just be removed and debugging async stacks delegated to proper tools.


[mini.test] screenshot name is prefixed with . when run_file() argument starts with ./

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.test
Description
screenshot name is prefixed with . when run_file() argument starts with ./
Neovim version
0.9.5
Steps to reproduce
run:
:lua MiniTest.run_file('./tests/test_something.lua')

Expected behavior
Paths should be normalized relative to the parent of tests/
Actual behavior
will results in screenshot names for that test file being prefixed with . so they become hidden files.

Thanks for the issue!
I'll take a look if this is worth fixing or it might be better to document.


Twin Setting expects valid JSON or quoted String

Module twin content must be a string surrounded by quotation marks or valid JSON error message is displayed in the Azure Portal for this step.

cc: @mlottner

@MSKeith : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


null byte in tags

When using id3v2.ParseReader(reader, id3v2.Options{Parse: true}) on (all?) mp3 downloaded from https://www.jamendo.com, extracted artist, album, title, ... contains a null byte at the end of the string.
I'm using strings.TrimRight(s,"\x00") as a workaround but I think that should be done inside id3v2.decodeText

I don't know if it's jamendo's issues or mine, but I don't think that each text in tag should be terminated with $00 (00). It's also not 100% clear from spec. But anyway I'll add trim.

Reminder for me: Add tests

Also see https://github.com/bogem/id3v2/pull/33


feat: adding react and fullstack templates

Proposed changes

Whitelisting react and full stack templates

@robdmoore sorry clicked request re-review by accident


Update Github Action workflows

Use on push only on stable branches to avoid duplicate runs (see syntax)
Update project automation

@caguero could I get a quick review?


feat(devInfo): set devInfo into axis component

Brief Information
This pull request is in the type of:

[ ] bug fixing
[x] new feature
[ ] others

What does this PR do?

set devInfo into axis component

Fixed issues

https://github.com/apache/echarts/issues/17697
Details
Before: What was the problem?

After: How does it behave after the fixing?

Document Info
One of the following should be checked.

[x] This PR doesn't relate to document changes
[ ] The document should be updated later
[ ] The document changes have been made in apache/echarts-doc#xxx

Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[ ] Please squash the commits into a single one when merging.

Other information

@sz-p Hi, thanks for your contribution! I marked this PR as a draft as it needs further discussion to determine the necessity, design, and implementation.

Thanks for the work! This information are very useful in the visual editor of ECharts.
Some suggestions or questions:

The component level and sub-component level should be separated. For example:

eCompName: 'barBackground'

Is better to be
component: 'series.bar',
element: 'background' // Other name better than element will be appreciated.

Naming should be consistent so it can be easily guessed by the developers. The naming rule should not expose the inside naming on the variables. For example:

eCompName: 'candlestickEl'

Is better to be
component: 'series.candlestick'
element: 'main' // Perhaps it can be optional if there is only one type of elements in the series. Which is the most common case

eCompName: 'barRect'

is better to be
component: 'series.bar'
element: 'main' // Perhaps it can be optional if there is only one type of elements in the series. Which is the most common case

Should these information only available in the __DEV__ mode so we can ship less code in the final productions. And we can provide a utility method to add this __devInfo

if (__DEV__) {
  // The second parameters can be optional in most of series.
  addDevInfo(el, 'series.bar', 'main');
}


Publishing

Publishing

Is it possible to look at this before Friday? I am on holiday from Friday evening and would like to get it published before I go. In case this is not possible, please contact<EMAIL_ADDRESS>or<EMAIL_ADDRESS>from 10th-20th.


Add details about Graph Activity Feed Notifications to the Bot conversations 'Notifications to your message' section

Is it possible to include a brief overview and a link to the Graph docs on how to send an activity feed notification using their API.
I spent some time recently trying to understand how to send a notification that links to a tab, but realised it wasn't possible with botframework, but was possible with the API.
I would suggest briefly explaining some limitations of this API, what is possible in the Graph API and then linking to the Activity feed notifications or bot framework messages documentation.
Helping developers understand that other parts of Platform can complete what they are trying to do would be useful.

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

ID: afbc5b84-5be5-b5c4-30c0-58782a748a03
Version Independent ID: ef6b8aee-52e7-f5d4-7dfa-8f34a1698330
Content: Messages in bot conversations - Teams
Content Source: msteams-platform/bots/how-to/conversations/conversation-messages.md
Product: msteams
GitHub Login: @surbhigupta
Microsoft Alias: anclear

We are looking into it. We will get back to you.

@AkJo - Could you please help us to update the document?


The new generation UI - Basic set up

for https://github.com/polymorpher/one-wallet/issues/260
visit /v2ui to toggle on / off the new ui

We can have multiple PRs on this, each replacing some components while still making the UI usable. I think the network selector is missing in the changes so far

We can have multiple PRs on this, each replacing some components while still making the UI usable. I think the network selector is missing in the changes so far

ya totally, the network selector is missing in the figma as well. I have my other changes on top of this and making separate PRs for them

Looks good, except the header needs some alignment and height regulation

Looks good, except the header needs some alignment and height regulation

ya i think we will need a responsive design for this, especially now there are a lot more elements on the top

Looks good, except the header needs some alignment and height regulation

added a new breakpoint at 1200 to hide the statsinfo, that will give us enough room to show the remaining items before reaching the mobile endpoint

headers are not working on mobile

fixed it


Improve creator UI

More closely approximate the mockups at RHCLOUD-30247.

There is also a missing banner.

That will need https://github.com/data-driven-forms/react-forms/pull/1476 to be merged so that the padding around the wizard body can be removed (and the banner can go to the edges).

Alright, I think that's everything fixed that I can replicate locally:

Banner added
Bundles input required
Work check toggle
Task title array input rewritten
Preview disabled on last step

I've asked UX about what that help text should be. Still not sure what's causing the display issues on your end; is there anything else you can share? What OS is this?

@randomnetcat not blocking getting this in - but I noticed if I fill out the details on step 2 for any content type, then switch back and choose a different content type, the fields on the second page remain filled for the new type. I think we discussed this before - but it would be nice to have a way to "clear" the form fields. I know we have overlap between each type - but if I make a mistake or don't want to carry things over - it would be nice to "reset".

I did notice it is possible to submit a quickstart with task 1's title being empty (although it looks to be required with the red asterisk):

Which results in a weird UI:


User View Navigation Regression

Issue:

User profile view has the search above. Search functionality is not on the target right now for V0 nor alpha. Product design has to be discuss before to apply on this version. Though it is a good implementation idea, it has to be executed step-by-step.

Indications:

Restore User profile view as it is on figma designs: https://www.figma.com/file/nDZnCkmXwOo2I71TXDBQTs/Masterbots-AI?type=design&node-id=531-2&mode=design&t=f8Eq5IexTWv0EmcP-4

Originally posted by @AndlerRL in https://github.com/bitcashorg/masterbots/issues/206#issuecomment-2092002789

 Review and Fix Alpha UI/UX Regressions


[11.x] Add optional ability to array wrap associative arrays

These additions allow array wrapping for associative arrays. Currently, Arr::wrap() does not wrap an associative array, but simply returns that same array. This feature is fully backwards compatible because the wrapping of associative arrays is opt in.. by passing true to Arr::wrap as the $wrapIfAssoc argument. This defaults to false which maintains current wrapping behavior.
Use Case
Functions that define an array parameter could be passed a list or an associative array. Also, many users implement functions that could be used on 1 data set or many data sets.. i.e. associative arrays. Being able to wrap associative arrays produces slightly more concise code and convenience.
Here, $params could either be ['id' => 1] or [['id' => 1], ['id' => 2]]...
Before

function (array $params) {
    $params = array_is_list($params) ? $params : [$params];

    foreach ($params as $param) {
        // process param
    }
}

After
function (array $params) {
    foreach (Arr::wrap($params, true) as $param) {
        // process param
    }
}

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


[Bash] Variable used as array not string

As proposed by static analysis tool:
https://github.com/koalaman/shellcheck/wiki/SC2178

Can one of the admins verify this patch?

Closing these all out. Mind making all these changes in one pull request? It's easier to run through tests that way.


Unable to create indexes/configuring users/changing passwords

I tried to install Open Distro for Elasticsearch on Fedora 30. I have installed:
opendistroforelasticsearch-1.0.0-1.noarch
and
opendistroforelasticsearch-kibana-1.0.0-1.x86_64
and followed the documentation on the website. Apart from a minor hickup (the default kibana.yml is slightly incorrect, see #96 ) it works, and I can create a user via Kibana, but after that I get stuck: I cannot get the user to write any data, or have any roles assigned.
I looked at https://opendistro.github.io/for-elasticsearch-docs/docs/install/docker-security/#change-passwords-for-read-only-users and followed the steps (RPM method), but the passwords simply do not get overwritten.
What am I doing wrong, or is the documentation outdated?

OK, some PEBKAC here, but still issues that prevent me from using Open Distro for Elasticsearch. I added some data into Elasticsearch (this went OK), but when creating an index pattern as that user in Kibana I just get stuck and "Create index pattern..." keeps spinning endlessly.
I am getting errors like these:
[2019-07-13T00:17:42,040][INFO ][c.a.o.s.p.PrivilegesEvaluator] [leela.thuis] No index-level perm match for User [name=bang, roles=[], requestedTenant=user] Resolved [aliases=[.kibana_3016248_bang], indices=[], allIndices=[.kibana_3016248_bang_2], types=[], originalRequested=[.kibana_3016248_bang], remoteIndices=[]] [Action [indices:data/write/bulk[s]]] [RolesChecked [own_index]]
[2019-07-13T00:18:11,002][INFO ][c.a.o.s.p.PrivilegesEvaluator] [leela.thuis] No index-level perm match for User [name=bang, roles=[], requestedTenant=user] Resolved [aliases=[], indices=[], allIndices=[], types=[*], originalRequested=[], remoteIndices=[]] [Action [indices:admin/mappings/get]] [RolesChecked [own_index]]
As the console works and I can get data out of Elasticsearch it is not Elasticsearch.
I have no idea where I am going wrong. I have gone through the docs and I don't see any mention of this particular problem.

Looks like the problem was having stale data. After removing the old data, reinstalling the software and following the steps again it works.


How to extend FormlyForm Component.

Is it possible in some way to extend the FormlyForm component?
Suppose I want to pass a new property to the form, or do any other type of operation such as changing the form template and adding an h1 at the end (Just an idea that comes to mind now) or even changing the selector . It's possible ?

Possible but instead of extending the FormlyForm (you may rely on internal API) I suggest wrapping formly-form component inside another component where you can use another selector/add extra content.


Respect disable_pip_input setting from Pipfile

The issue
https://github.com/pypa/pipenv/pull/5301 broke keyring support again until https://github.com/pypa/pip/pull/11029 gets merged into Pip and then vendored into Pipenv.
The fix
This makes get_pip_args() respect disable_pip_input that was introduced in https://github.com/pypa/pipenv/pull/5036.
The checklist

[ ] Associated issue
[ ] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

@Darsstar Thanks for the PR, I remember that issue now.


install-to-dest script has wrong path to pacman hook

I was having an issue installing the latest version of yabsnap. I would keep hitting this error here:
install: cannot stat 'artifacts/pacman/05-yabsnap-pacman-pre.hook': No such file or directory

I found that the install-to-dest.sh script has the wrong path for the hook. It says 05 instead of 01. https://github.com/hirak99/yabsnap/blob/9dd7753165dcbe84446f89a07ff426383e2b1f18/scripts/install-to-dest.sh#L59C43-L59C43. In my case I changed the file listed in the artifacts folder from 01 to 05.
Turns out there was some prior work to update the PKGBUILD here, https://github.com/hirak99/yabsnap/issues/18#issuecomment-1782668293.
I think the script should be updated to reference the correct path, but if the hook's priority has changed according to the linked comment above, maybe there should be some extra logic to remove the existing hook as well?

Sorry about that, thanks for reporting.
Changed, also added a test to the workflow to detect future breakages.


Fix complex negative property access

Input:
lastChild := node.children.-1

Output without this PR:
let ref;const lastChild = (ref = node.children[ref.length-1])

Output with this PR:
let ref;const lastChild = (ref = node.children)[ref.length-1]

Context
Civet doesn't work if built with current Civet because this line is compiling incorrectly:
https://github.com/DanielXMoore/Civet/blob/41ba011b4a506af1c0a08b22a838a46e9f637fd2/source/parser/binding.civet#L140
Hopefully this will allow us to upgrade Civet and fix the CLI according to #1261.

P.S. I wonder about adding another test mode that runs yarn test but where it uses the current code to build itself (after building itself with the current release). Essentially yarn build + yarn test using the current build instead of NPM. I wouldn't run this all the time, probably, but it would be especially good for CI testing to avoid surprises like this in the future. Civet is of course the largest example of Civet code, so it's a good real-world test.
Alternatively or in addition, an interesting idea could be to run yarn build with the current Civet dep, and then run yarn build again with the resulting build, and output a diff of the output (and ideally show that in CI, maybe as an artifact). Sometimes diffs are fine/good, but it might be good to be aware of them and make it part of code review?


Bootloop ios 12.1.1 after RootFS Restore b28

RootFS Restore only supports iOS 11.0-11.4.1 :) !

Xabbasoo rootFS restore support all ios from 11 to 12.1.2.
I have try rootfs restore u0 3.0.0~b27 on ios 12.1.1 beta 3 it's not problem and work perfectly

Same here @coenkcore, prepared for FR, successfully went from 12.1.1b3-12.1.1. Something happened, I used uncover and it renamed the snapshot then reboot straight into boot loop.

@pwn20wndstuff @Cryptiiiic

i think you have ota updates installed..

Folks, make sure that there is no OTA update downloaded. We've since improved the checker for this, in the meantime, restore to 12.1.1b3 while it's still signed.


New styles for search results dropdowns (#2128)

Overview
Brief description of what this PR does, and why it is needed.
Connects #2128
Demo
Optional. Screenshots, curl examples, etc.
Notes
Optional. Ancillary topics, caveats, alternative strategies that didn't work out, anything else.
Testing Instructions

How to test this PR
Prefer bulleted description
Start after checking out this branch
Include any setup required, such as bundling scripts, restarting services, etc.
Include test case, and expected output

Checklist

[x] fixup! commits have been squashed
[ ] CI passes after rebase
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[x] This PR is targeted at the correct branch (develop vs. ogr/develop)
[ ] If this PR applies to both OAR and OGR a companion PR has been created

Looks good! It seems like a styling change was introduced by PR #2151  that impacted the style of the facility search input label - can you adjust the search input so it matches the other labels again?


MaskedEditExtender with ClearMaskOnLostFocus=False adds extra character at first position

The AJAX Control Toolkit
Version 18.1.1
The installation method
NuGet package
Minimal steps to reproduce the bug

On Visual Studio 2013 create a Windows Form App

Create a ASP.NET Web Application

Add a Textbox

Add MaskedEditExtender to that Textbox

For that MaskedEditExtender use settings like these:
<ACT:MaskedEditExtender ID="MaskedEditExtender1" runat="server" TargetControlID="TextBoxID" Mask="09-9999-9999"
ClearMaskOnLostFocus="false" AutoComplete="true" InputDirection="LeftToRight"/>

Run the application.

Click inside and outside the TextBox

Perform something that call a PostBack

Actual result
When one clicks inside and outside the TextBox, the mask adds an extra character. This same behaviour is presented when a PostBack is performed.
Expected result
No extra character must be added on these situations.
Browser(s) used
Chrome
Edge
WebApplication_Mascara.zip

We fixed the issue in the master branch. Check the 'Updating the Project from CI Builds' guide to learn how to update the project before an official AJAX Control Toolkit release is available.

Thanks for your attention on this issue. We really appreciate it.
El jue., 17 oct. 2019 a las 22:02, AlekseyMartynov (<
<EMAIL_ADDRESS>escribió:

We fixed the issue in the master branch. Check the 'Updating the Project
from CI Builds'
https://github.com/DevExpress/AjaxControlToolkit/wiki/Updating-the-Project-from-CI-Builds
guide to learn how to update the project before an official AJAX Control
Toolkit release is available.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DevExpress/AjaxControlToolkit/issues/493?email_source=notifications&email_token=AMO6A7UT3VRWHZBAN6Z2BM3QPEYO3A5CNFSM4H36CLYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBSPHXY#issuecomment-543486943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMO6A7UKOL5D4XVK42XDSALQPEYO3ANCNFSM4H36CLYA
.


Restoring completed task does not restore priority

Did you check if the bug has already been reported? I did...
Describe the bug
Marking a prioritised task as completed will remove the task from the active list in that prioritiy's group and convert the priority into a pri: control. With completed tasks set to visible, unmarking the task will restore it but without priority. The pri: control remains in the task text.
To Reproduce

Create a new task and assign a priority letter
Mark the task as completed
Unmark the task as not completed (incidentally, the tooltip on the marker box for completed tasks says "In progress".)
The task is restored without priority

Do you see any error entries in sleeks developer tools?
No errors, only Success and Info messages
Expected behavior
Task is restored to its original priority group and the pri:[A-Z] control string in the task text is removed.
Oh, while on the subject... Feature request: Ability to restore recurring tasks to their state with dates before having been marked as done - a bit like an "Undo" for recurring tasks...
Desktop (please complete the following information):
Sleek v.1.1.9 from Github Releases on Win10x64

Same here, sleek 1.1.6 and upwards, Debian 11.3

@Bumpyride @andrei-a-papou this is not a bug, it's a non standard todo.txt feature that hasn't been implemented yet. It is part of this pre release though: https://github.com/ransome1/sleek/releases/tag/v1.2.0-rc.1
Give it some testing if you find the time.

@Bumpyride @andrei-a-papou this is not a bug, it's a non standard todo.txt feature (or rather an enhancement of an already implemented feature) that hasn't been implemented yet. It is part of this pre release though: https://github.com/ransome1/sleek/releases/tag/v1.2.0-rc.1
Give it some testing if you find the time.

Good to know. I was expecting it to restore as is, but it's good to know that it's not a bug. Thanks. Still, It would be a good enhancement.

@ransome1 @andrei-a-papou I finally managed to get around to test with v1.2.0-rc1
Heads up - this issue is RESOLVED!
I tried with several combinations and everything works as intended. Surprise bonus - restoring recurring tasks works, too. I thought that would have to be a separate enhancement request, due to the additional complexity.

Works for me as well, thanks, @ransome1!


Better types for EntityHooks

fixes #1263

Can you add a test?

I updated an existing test, is that good enough?


Webhook auth mode support

Do you know if its possible to override these values with the provider?
I am trying to enable Webhook auth mode.

Yes, you can configure this using kube_api_server_config, see https://registry.terraform.io/providers/eddycharly/kops/latest/docs/resources/cluster#kube_api_server_config
Is this what you're after ?

Closing, looks like it's already implemented, please reopen if needed.


Fixed #4 (part deux)

Added escaping of single quote (') for column names and table name.

Thanks again!

You're welcome. But but somebody with real SQL skill (not me) should take a look at this code, because while I've checked as many things against the sqlite docs as I could, there is still a chance that I've missed something or made wrong assumptions.


custom updater?

the custom updater didn't delete this update and also have disappear...

https://community.home-assistant.io/t/smartir-climate-component/100798/46


feat: mmap transport for macos

Not tested.

I test it on my macbook air (m1).
db error: ERROR: called `Result::unwrap()` on an `Err` value: Os { code: 9, kind: Uncategorized, message: "Bad file descriptor" }

@silver-ymz Could you run sqllogictest tests on the latest commit?

I don't think we need to check so many versions. It is best to control the CI duration within 5 minutes.

@VoVAllen
All checks in linux can be finished in 10 minutes. However, checks in MacOS need about 20 minutes.

Please move most tests to merge queue test according to https://stackoverflow.com/questions/62846375/perform-github-action-when-trying-to-merge-branch. One check is enough for each commit I think. Run all the tests only when the PR got into the merge queue

Or control the test manually by issue label like
on:
  label:
    types: [run-full-ci]

Does https://github.com/tensorchord/pgvecto.rs/pull/139 depend on this PR for postgres 14? cc @silver-ymz

Does https://github.com/tensorchord/pgvecto.rs/pull/139 depend on this PR for postgres 14?

No.

@VoVAllen We need to modify branch protection rules.

I'm on the train. Will modify it when go home


Allow different ways of limitting the transactions in a block

Currently we limit the size of all extrinsics in the block (see https://github.com/paritytech/substrate/pull/1581) and have the limit hardcoded in the runtime.
However interaction with other modules (namely srml-contract) may require some other mechanism of limitting the number of transactions. For instance contracts use up gas and we can have a block gas limit alike Ethereum.
Would be perfect if the weight of the transaction was also given to the pool to allow better (more optimal) allocation of extrinsics to block to maximise both: fee and utilisation
It's a follow up issue on #1354 (see comment https://github.com/paritytech/substrate/issues/1354#issuecomment-453928936)

When we're building blocks we also want to be informed of when this limit has been hit and how close we are to it. If the proposer can get back an Error::BlockFull(remaining_weight) and finish proposing / push more transactions withsum(new_txs.weight) <= remaining_weight that would work really well.

I guess that's resolved with #3157


Better logging for _get_attribute_value to debug wrong configurations

We were debugging mapping problems and ended up using this piece of code as a monkey patch to pinpoint the problem. I believe it's useful for other people

Thank you, please increase the djangosaml2 version, I'll merge it and we'll have a new release with your contribution

Thanks! To be honest: I don't quite know how to increase the version. Is this a code change?

Yes, just change this
https://github.com/IdentityPython/djangosaml2/blob/master/setup.py#L30
to 1.5.3

Thanks for the info! Just did that.


Optimize BigInteger by making smarter use of Longs.

Here are a couple general ideas that have been used in several places:

Using appropriately the unsigned division and remainder operations provided by {Integer,Long}.{divide,remainder}Unsigned.
Carry variables in loops can be Ints, and reinterpreted as Longs inside the loop, which avoids having mutable records.
When performing both unsigned division and remainder on Longs, it is much more efficient to compute the remainder from the quotient: subtraction + multiplication are way faster than one remainder.

Review by @nicolasstucki

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3321/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4320/
Test PASSed.

LGTM


fix for #300

Fun with LD_LIBRARY_PATH.

Will run unit tests on this, and then merge.

Rebased this PR on master and ran unit tests.  All looks good.


Implement CopyObjectRequest.

This is part of the work for #812. It implements the request object
for Objects: copy.

This change is

Ping.

PTAL.


Corruption when joining on LAN

My brother and I wanted to try out a 100 days  on hardcore as endermen, and decided this would be the perfect mod. When I did this solo, it worked perfectly. However when my brother joined my LAN world, all the blocks were simply messed up. On my screen it was end moss, on his screen it was waterlogged blackstone bricks. Better end blocks did exist on his screen, he could see some blocks corrupted as better end blocks. How do I fix this, we just want to play D:

This means that mods or configs on both clients are different, this is not the issue of the mod


Rework

Hi, since a while, i'm working on a full rewrite of this crate. It's because i've found many issue making it too easy to use it incorrectly and difficult to use correctly.
This is still a work in progress, for example i plan to "type state" more the system to prevent doing meanless things like reading data register while being in transmit mode, but i didn't yet determined what extactly to put in the "type state" system.
I'm currently trying to validate a proof of concept by using it on stm32f4xx-hal and implementing an example using a master and a slave through interruption.

hi, i just finished a working example on my stm32f4xx-hal fork. It use a master receiver, a slave transmitter, the whole things driven through interrupts using rtic.
https://github.com/YruamaLairba/stm32f4xx-hal/blob/i2s_rework/examples/i2s-rtic-audio-in-out.rs

This looks good so far.

lol, i was very in depth in the typestate system.
In your opinion, does it worth to re implement audio sample transfer in blocking/ not blocking mode ?

I like using type state, as long as there's decent documentation.
I don't have a strong opinion on blocking or non-blocking, but ideally we should have something that could work with the proposed I2S traits.

Hi, i worked on another branch to have a "higher level of abstraction" for I2s https://github.com/YruamaLairba/stm32_i2s/tree/rework_transfer. I didn't try to implement the I2s hal because i don't find it good, I just implemented API for blocking and non-blocking read/write on a new Transfer object. There is 4 key methods:

write_iter: blocking write by consuming an iterator,
write: non-blocking write a full audio frame (L,R). Need to be called continuously to actually transmit sample,
read_while: blocking read using a closure, can be used to get only one channel or to lower bit depth on the fly,
read: non-blocking read a full audio frame (L,R). Need to be called continuously to receive correctly sample,

However, i discovered is some issue and unexpected behavior, i can't yet solve or workaround:

disable/enable a master I2s device doesn't reset clock phase,
the CHSIDE flag is not very reliable in master transmit mode,
because of that:
Once a master transmit device have been disabled, the corresponding Transfer can't work correctly anymore until the next MCU reset
Master Receive is not implemented for PCM since i use the CHSIDE flag to recover channel information.

I also need to reorganize and rename stuff for coherence, probably have seperate module for driver and transfer

Ready for a review, sorry for the big chunk of commits, as i said, i was working on another branch. I didn't (yet) fix previously mentioned problems, i just documented them

I already found a issue with "transfer", i have a channel inversion when i'm using "master transmit" + "slave receive". I don't know what's wrong.

Now that I've had some time to look more, this looks like a great set of changes. I'm ready to merge this whenever you think it's ready.

unfortunately not ready. Since I found the "channel inversion" issue, i realized my test wasn't rigorous enough. I was just testing with my pcm* ADC and DAC devices but having sound does mean everything is right. So I started a project dedicated to test. The main idea is to use 2 I2s perpipheral, write few data with the first and read those data with the second. This makes me discover another issue.

Errors fixed ! I did a project dedicated to test to find them

Released as 0.3.0