DRILL-5712: Update the pom files with dependency exclusions for commons-codec

In java-exec, we are adding a dependency for commons-codec of version 1.10. Other dependencies like hadoop-common, parquet-column etc are trying to download different versions for common codec. Exclusions should be added for common-codec in these dependencies.
This change has added exclusions in all the pom.xml files.

@sindhurirayavaram, please rebase this onto the latest master; looks like some stray commits have found their way into this PR.

@sindhurirayavaram, will you be able to rebase this & squash commits? Then I can merge it into master. Thanks!


Improve README for release

We should expand the README to include screenshots, gifs, configuration information and anything needed for using the plugin. This will be used by VSCode and the extension page when we publish it

I planned on doing this when we finalise the features for a first release. Current todos are:

Update the section on tasks. The CoreLLDB made some changes to how tasks work, and running executables is now handled with the debugger. The example on how to add command line arguments should also be updated to use the debugger.
Mention our dependency on CoreLLDB and explain how to set up the LLDB Library to use.
Mention that debugging doesn't work on Windows.
Mention our inclusion of SourceKit-LSP and include its configuration settings.
Mention our (limited) support for multi-root workspaces.


use s3 repository for model configs when using remote triton

Hi there,
Problem
When launching the analyzer in the remote mode (--triton-launch-mode=remote), it's not possible to test various model configs because the remote Triton is unable to read model configs from the same host path.
Solution
Triton inference server supports reading models from an S3 storage and we could use that to run model-analyzer with a remote Triton and write model configs to a S3 storage (something like --output-model-repository-path=s3://mybucket/triton-model-repository).
I'm willing to contribute with this PR if approved for development.

Hi @Rusteam
You are correct that Model Analyzer does not currently support sweeping configs in remote mode. The issue isn't just finding storage that both MA and the server have access to. MA also needs the ability to load and unload models on a remote server.
It is on our roadmap to support remote sweeping of configs.  The solution is likely to load and unload via the client API,  so I don't believe it would require something like S3 repository.

That's cool too. If you want help, let me know


Changing duration types from int64 to float64

Gitlab uses float format for build related information. Since it was not documented, it could not be part of previous PR. Below snippet is from test setup.
  "build_status": "running",
  "build_started_at": "2021-01-11 20:21:22 +0100",
  "build_finished_at": null,
  "build_duration": 0.08038407,
  "build_allow_failure": false,
  "build_failure_reason": "unknown_failure",
  "pipeline_id": 33,

@Toshik1978 Could you please merge this into v6? Thanks.

@Toshik1978 Could you please merge this into v6? Thanks.

@shaheed121 will do in the nearest days! Thanks a lot, that you found it before v6 release! I thought about build_duration because of @zrochler PR, but didn't found any examples and planned to test it ) You save my time

@shaheed121 will do in the nearest days! Thanks a lot, that you found it before v6 release! I thought about build_duration because of @zrochler PR, but didn't found any examples and planned to test it ) You save my time

@Toshik1978 Would you be able to make a new release? Appreciate all the help from you so far :)

@Toshik1978 Would you be able to make a new release? Appreciate all the help from you so far :)

@Toshik1978 Would you be able to make a new release? Appreciate all the help from you so far :)

@shaheed121 planned to wait for final v6, but ok, will merge now. Important comment. Now the import should be done via github, not gopkg.in - we finally added support of go modules for the project.

@Toshik1978 Would you be able to make a new release? Appreciate all the help from you so far :)

@shaheed121 planned to wait for final v6, but ok, will merge now. Important comment. Now the import should be done via github, not gopkg.in - we finally added support of go modules for the project.


No audio input device error: ValueError: -1 is not in list.

2024-06-13 16:20:28 | INFO | faiss.loader | Loading faiss with AVX2 support.
2024-06-13 16:20:28 | INFO | faiss.loader | Successfully loaded faiss with AVX2 support.
2024-06-13 16:20:28 | INFO | configs.config | Found GPU NVIDIA GeForce RTX 4070 Ti
2024-06-13 16:20:28 | INFO | configs.config | Half-precision floating-point: True, device: cuda:0
Traceback (most recent call last):
  File "D:\Git\Retrieval-based-Voice-Conversion-WebUI\gui_v1.py", line 157, in load
    data = json.load(j)
  File "C:\Users\28622\AppData\Local\Programs\Python\Python310\lib\json\__init__.py", line 293, in load
    return loads(fp.read(),
  File "C:\Users\28622\AppData\Local\Programs\Python\Python310\lib\json\__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "C:\Users\28622\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "C:\Users\28622\AppData\Local\Programs\Python\Python310\lib\json\decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\Git\Retrieval-based-Voice-Conversion-WebUI\gui_v1.py", line 1070, in <module>
    gui = GUI()
  File "D:\Git\Retrieval-based-Voice-Conversion-WebUI\gui_v1.py", line 150, in __init__
    self.launcher()
  File "D:\Git\Retrieval-based-Voice-Conversion-WebUI\gui_v1.py", line 224, in launcher
    data = self.load()
  File "D:\Git\Retrieval-based-Voice-Conversion-WebUI\gui_v1.py", line 195, in load
    self.input_devices_indices.index(sd.default.device[0])
ValueError: -1 is not in list
請按任意鍵繼續 . . .

How can I adjust the code to skip the check and allow the program to continue running?

Now you can't start the real-time voice changing gui without a recording device.If you don't have a physical recording device, you can install at least one virtual device, such as using voicemeeter software


Add link to "edit this page on Github" on every /learn docs page

I implemented the functionality so far. Do we have a design for that?


Deployed Netlify App is being shown as 'Dangerous'

Describe the bug
When I opened the deployed link from the About Section of GitHub Repo, I couldn't access the website, and it was showing an error. Screenshot attached.
To Reproduce
Steps to reproduce the behavior:

Go to 'About Section of the GitHub Repo'
Click on 'the deployed link'
See error

Expected behavior
The original deployed web app/website with secure https link and access to the web app.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 116

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Go ahead and fix the issue

Go ahead and fix the issue @gkm0001


Accelerated Networking support also Windows 2022

[Enter feedback here]
I've got answer from the product group and confirmed that accelerated networking is supported in Windows 2022.
BUT this document didn't include Windows 2022 in the list of supported OS .

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

ID: fbfe1f3b-01da-a475-8dee-15f628bd7e17
Version Independent ID: 4315f677-aa2b-b82c-8491-634dfb3fc11e
Content: Accelerated Networking overview
Content Source: articles/virtual-network/accelerated-networking-overview.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

@eyoh5 , thank you for your feedback. We'll review this and get back to you shortly!

@eyoh5 , I've updated the doc to reflect Windows server 2022 as a supported OS for Accelerated Networking and it will reflect soon.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


NetworkTransform reliable/unreliable: onlySyncOnChange jitter

see NT jitter thread in discord.
may need to remove the feature.
posting so we don't forget it.

onlySyncOnChange wasn't the problem.  Turning it off made the problem worse.
The problem turned out to be SSL in Websockets transport being inadequate, and the solution to that was a reverse proxy.


guake: 3.3.0 -> 3.3.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/guake/versions.
meta.description for guake is: '"Drop-down terminal for GNOME"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/guake passed the binary check.
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/guake-toggle passed the binary check.
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/..guake-wrapped-wrapped passed the binary check.
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/.guake-wrapped passed the binary check.
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/..guake-toggle-wrapped-wrapped passed the binary check.
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/.guake-toggle-wrapped passed the binary check.
6 of 6 passed binary check by having a zero exit code.
0 of 6 passed binary check by having the new version present in output.
found 3.3.2 with grep in /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2
directory tree listing: https://gist.github.com/f597500b2afbf209ce285e7fd57195fc
du listing: https://gist.github.com/4fe833c36321aa1cfb36b4f3f9a64954

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout cb955845a03bc7ce524464d35b513ac9fd6b8459 && nix-shell --pure -I nixpkgs=. -p guake

cc @msteen for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: guake
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: guake
Partial log (click to expand)
Wrapping program /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/bin/guake-toggle
Wrapping program /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/bin/guake
shrinking RPATHs of ELF executables and libraries in /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2
strip is /nix/store/7iyn7gn33i7xxjgmwf25k20246y6nd9d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/lib  /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/bin
patching script interpreter paths in /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2
checking for references to /build in /nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2...
wrapping `/nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/bin/.guake-wrapped'...
wrapping `/nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2/bin/.guake-toggle-wrapped'...
/nix/store/ibq8f5qbh80hafb2jz9m5j52gdk1lzds-guake-3.3.2

Success on x86_64-linux (full log)
Attempted: guake
Partial log (click to expand)
Wrapping program /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/guake
Wrapping program /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/guake-toggle
shrinking RPATHs of ELF executables and libraries in /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2
strip is /nix/store/90vmpr41dzsx350k5argycaf693hnl1l-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/lib  /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin
patching script interpreter paths in /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2
checking for references to /build in /nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2...
wrapping `/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/.guake-wrapped'...
wrapping `/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2/bin/.guake-toggle-wrapped'...
/nix/store/vsxf3fvcghiwrvkmna0a8g1330xhjvqq-guake-3.3.2


Fix documentation code snippet of Queue.from

Closes #37943

Code review: https://dart-review.googlesource.com/c/sdk/+/121641

Thanks for the contribution! Can you please make a similar fix to the current branch of this library located here? https://github.com/dart-lang/sdk/blob/master/sdk_nnbd/lib/collection/queue.dart

Done :+1:  @mit-mit

This was actually fixed already in https://github.com/dart-lang/sdk/commit/04702d827bbcf51f8f331c23df8508b12b127bf6.
I'm not sure what happened there, but it seems like the issue was fixed independently of this PR. Thanks for your contribution and sorry for the mess.
For posterity:
Because there was no change if this PR was submitted, the Gerrit sync failed (or more accurately was a no op). If the sync had respected the PR's base the Gerrit review would've highlighted the problem (I'll see if that can be fixed). Because GitHub only seems to be able to diff against the PR it incorrectly claims there are changes here. The only way to correct that would be to rebase the PR (which would result in no changes).


How do I convert an PIL RGB data to OpenCV BGR data?

Here's the numpy code:
img = img[:, :, ::-1]

Looks like I can just dot product with a matrix, but the real problem is this doesn't support uint8, yet.

I haven't looked into integer support. But that should be doable. Portable SIMD supports all the datatypes that are relevant, including u8. Could you elaborate a bit more on what you would like to do (I assume RGB -> BGR is not all of it)?
I'm curious :)

Actually it is. I'm trying to avoid numpy(to reduce the size of my packaged app) and this is the only place I have to call numpy in my codebase.

I just made a new release. Could you try installing version 0.1.5 and let me know if that works for you?
You should be able to pass in a 3d array and then reverse the last axis. You should be able to use fancy indexing:
data = [
    [[1, 2], [3, 4], [5, 6]],
    [[7, 8], [9, 10], [11, 12]],
    [[13, 14], [15, 16], [17, 18]],
]

data_rnp = rnp.NumArray(data, dtype="uint8")

# reverse last axis
data_rnp = data_rnp[:, :, ::-1]


Timeline in Multitrack Doesn't Adjust with Zoom

Bug description
Timeline does not adjust with zoom level
Environment

Browser: Chrome

Minimal code snippet
https://wavesurfer-js.org/examples/#multitrack.js
Expected result
Timeline changes with zoom
Obtained result
https://github.com/katspaugh/wavesurfer.js/assets/1612230/c9954717-7ff2-4725-baba-a95c37d52f01

Following as I need to implement the same.

I'll prioritize it. 👍

Fixed in 0.3.1 ✅
Thanks for reporting!

Hi @zaptrem, I apologise for writing in this chat, but this is the only place where I can write, please tell me what I'm doing wrong that my timeline is rendered this way. I mean it ends when my first audio ends + I dont understand why i have 2 timelines

MultiTrack.create(
[
{
id: 1,
draggable: true,
startPosition: 0,
url: 'https://www.mfiles.co.uk/mp3-downloads/angels-we-have-heard-on-high.mp3',
options: {
height: 54,
waveColor: 'rgba(255, 255, 255, 0.80)',
progressColor: 'rgba(255, 255, 255, 0.80)',
barWidth: 3,
barGap: 2,
barRadius: 1,
barHeight: 1,
plugins: [
TimelinePlugin.create({
height: 10,
insertPosition: 'beforebegin',
primaryLabelInterval: 10,
formatTimeCallback: (seconds: number) => seconds + ' s',
style: {
fontSize: '10px',
color: '#2D5B88'
}
})
]
}
},
{
id: 2,
draggable: true,
startPosition: 0,
options: {
height: 54,
waveColor: 'rgba(255, 255, 255, 0.80)',
progressColor: 'rgba(255, 255, 255, 0.80)',
barWidth: 3,
barGap: 2,
barRadius: 1,
barHeight: 1
},
url: 'https://www.mfiles.co.uk/mp3-downloads/shepherds-shake-off-your-drowsy-sleep.mp3'
},
{
id: 3,
draggable: true,
startPosition: 0,
options: {
height: 54,
waveColor: 'rgba(255, 255, 255, 0.80)',
progressColor: 'rgba(255, 255, 255, 0.80)',
barWidth: 3,
barGap: 2,
barRadius: 1,
barHeight: 1
},
url: 'https://www.mfiles.co.uk/mp3-downloads/daisy-bell.mp3'
}
],
{
container: stemsWaveForm.current!,
minPxPerSec: 10,
rightButtonDrag: false,
cursorWidth: 2,
cursorColor: '#008EF3',
trackBackground: 'rgba(0, 0, 0, 0.10);',
trackBorderColor: '#494949',
dragBounds: true,
envelopeOptions: {
lineColor: 'rgba(255, 0, 0, 0.7)',
lineWidth: '4',
dragPointSize: window.innerWidth < 600 ? 20 : 10,
dragPointFill: 'rgba(255, 255, 255, 0.8)',
dragPointStroke: 'rgba(255, 255, 255, 0.3)'
}
}
)

Multitrack has its own Timeline, you don't need to initialize it on individual tracks. If you do that, it's expected that it spans only the duration of that track.
If you have any other questions, please feel free to post in our forum:
https://github.com/katspaugh/wavesurfer.js/discussions/categories/q-a


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d20g1r9gvh7n4i
Region: us-east-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I am trying to associate the pt.com TLD and www.pt.com with this app on Amplify, and it keeps telling me that the CNAME is in use somewhere, but I can't find the resource.  I've looked through my S3 buckets, CloudFront, etc, everywhere.
Error message
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

I have the same issue, no one's responding here, unfortunately. My case has been open for 5 days and I've been trying the same number of days.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

Thank you for the reply. I have read through the documentation multiple times. The error message doesn’t say what resource the CNAME is referencing, so I am stuck. I have combed through all of my AWS resources and can’t find any reference to playlist.com or www.playlist.com anywhere in my account. Can you tell me specifically what resources are in conflict, or reimplement the error message to specify the resource in contention?
Sent from my iPhone

On Mar 19, 2021, at 10:27 AM, brnmye @.***> wrote:

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

bump.  still stuck, no response.

@stevepetersen our records indicate that your custom domain for the app with id d20g1r9gvh7n4i  is available. Domain joh*****.com. In regard to your other domain, can you try re-creating a custom domain? It looks like it was deleted.

Re-open if you're still having issues.


Permissions Missing for Most VSTS management pages

Issue(s)

Most pages in the documentation for VSTS (Azure Dev OPs), do not provide information on which Permissions are required to perform the operations.
The UI for VSTS does not show operations/tasks if end-users do not have access or permissions to perform the operations. Since this is the case, the user spends time searching around in the VSTS UI to try and follow the documentation, but ultimately just thinks the documentation is out of date.
Each documentation page , at the top of the page, should provide details on required permissions, and a link to how to check your permissions and role. This will prevent people from wasting time from reading the article only to find out they can't even find/see the operations or workflow.

@LouMM Thank you for this feedback, I have added this to some topics (here is one example) and I agree, we should add it to more. I am passing this along. Do you have a specific area where you are being blocked, if so, I can try and help you with the required permissions for that area?


Chore: improve Spell checker API to the example

Description
It's already known that we have a simple API to be able to use our spell checker in the editor, but nevertheless, if we looked closely at how it was working, it was becoming quite cumbersome to activate and deactivate it due to everything that was involved. For this reason, it was updated to the latest version of simple_spell_checker in order to be able to use new methods like toggleChecker() (called into the provider as toggleState()) that just deactivates the service without having to close or replace it (something that we did before since there was no real way to deactivate it without changing the service), and isServiceActive() so that the developer can always get the status of the service.
This not only makes the API simpler for other developers but also improved performance since we don't have to change the instance of the service every time we deactivate or activate it.
Not related
It was updated to the latest version because if we had the service active there were commonly used characters that were lost or ignored or even checked as if they were a word (for example, in the previous version the character ":" was taken as a word)

[ ] ✨ New feature: Adds new functionality without breaking existing features.
[x] 🛠 Bug fix: Resolves an issue without altering current behavior.
[ ] 🧹 Code refactor: Code restructuring that does not affect behavior.
[ ] ❌ Breaking change: Alters existing functionality and requires updates.
[ ] 🧪 Tests: Adds new tests or modifies existing tests.
[ ] 📝 Documentation: Updates or additions to documentation.
[x] 🗑 Chore: Routine tasks, or maintenance.
[ ] ✅ Build configuration change: Changes to build or deploy processes.

Unrelated but while testing in my current branch, I'm always having this exception:
The following assertion was thrown building TextLine(dependencies: [MediaQuery, _LocalizationsScope-[GlobalKey#d9bd8], _QuillPressedKeysAccess], state: _TextLineState#09a95):
You cannot reuse this SimpleSpellchecker since you dispose it before
'package:simple_spell_checker/src/spell_checker_interface/abtract_checker.dart':
Failed assertion: line 256 pos 12: '!_disposed'

Sometimes the spell-checking is already disabled.


find bar looks out of place when unified_toolbar = true

We should probably be styling the find bar as well, in this case, or else we look like this:

Looks like it's broken again, now the find bar appears to be transparent...

And fixed again in 8901cdc818f9dda498a98a4b0817322bcfb8267f


Adding Event in Events.js

Problem Description
We have an upcoming event MicroMaster: 8051 Microcontroller masterclass which will be a workshop for 3rd year EnTC students where they can learn about 8051 Microcontrollers. Which is yet to be added in the event section.
Proposed Solution

Create a new card below the "A New Start". ( can copy the above card)
Give a suitable Title and Description and add the upcoming label to it.
Make a PR with a screenshot of the output.

Please assign this to me

I would like to do please assign me

Can I work on this issue @adityasimant?

@ianujvarshney This issue has already been assigned to a fellow associate. However, you can wait for upcoming issues or create an issue enhancing the webpage.


HTML comment that contains @ causes stray "–>" in output

Description
Input like the following causes the issue:
Hi there.

<!--
  @test
-->

In contrast, this renders correctly:
Hi there.

<!--
  test
-->

It seems like DocC is trying to parse an @ directive block in the middle of the comment.
Checklist

[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

rdar://101144032

There's a known issue (rdar://98695544) about block directives closing off any other container they're in (block quotes, lists, etc), but this seems like it would be solved differently. I'm not sure if cmark-gfm differentiates between an HTML comment or just any other kind of HTML block, but if we can tell we're in a comment we shouldn't parse directives in the first place. If all we know is that we're in an HTML block, we should solve the other issue with block directives, which would also solve this one.


New angular app throws "TypeError: Cannot read property 'projectPath' of undefined" on amplify init

Which Category is your question related to?
amplify init
Amplify CLI Version
4.47.1
What AWS Services are you utilizing?
Amplify
Provide additional details e.g. code snippets
I created a brand new angular app by doing
npx -p @angular/cli ng new amplify-app
Then changed into that directory. Then, running amplify-init results in the following error:
$: amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project amplifyapp
The following configuration will be applied:

Project information
| Name: amplifyapp
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
TypeError: Cannot read property 'projectPath' of undefined
    at getAngularConfig (/snapshot/node_modules/amplify-frontend-javascript/lib/framework-config-mapping.js:57:52)
    at getProjectConfiguration (/snapshot/node_modules/amplify-frontend-javascript/lib/framework-config-mapping.js:85:14)
    at Object.displayFrontendDefaults (/snapshot/node_modules/amplify-frontend-javascript/lib/configuration-manager.js:173:32)
    at Object.displayFrontendDefaults (/snapshot/node_modules/amplify-frontend-javascript/index.js:40:24)
    at displayAndSetDefaults (/snapshot/node_modules/@aws-amplify/cli/lib/init-steps/s0-analyzeProject.js:83:26)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async analyzeProject (/snapshot/node_modules/@aws-amplify/cli/lib/init-steps/s0-analyzeProject.js:99:9)
    at async Object.run (/snapshot/node_modules/@aws-amplify/cli/lib/commands/init.js:29:13)
    at async Object.executeAmplifyCommand (/snapshot/node_modules/@aws-amplify/cli/lib/index.js:236:9)
    at async executePluginModuleCommand (/snapshot/node_modules/@aws-amplify/cli/lib/execution-manager.js:164:5)
    at async Object.executeCommand (/snapshot/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at async Object.run (/snapshot/node_modules/@aws-amplify/cli/lib/index.js:112:9)

I've been poking at this with my team for hours, and we can't seem to find any fixes. We're running on macOS Big Sur 11.1 and using bash

Closing as a duplicate of https://github.com/aws-amplify/amplify-cli/issues/7060
You can use default mac terminal/zsh to get around this as mentioned in the issue above while we investigate this issue.

duplicate of #7060
this is #7060

Also, using zsh does not remedy this. I get the same error.

How did you install the CLI? Was it installed globally using - npm install -g @aws-amplify/cli ?

Yes, I did npm install -g @aws-amplify/cli. My version is up to date too, as amplify -v returns 4.47.1

While we investigate this issue, you can install an older version of the CLI using this command - npm install -g<EMAIL_ADDRESS>


Update images

Changelog

Updated images used for background, banners, avatar & user-icon.

New gradient blends

home1 & user profile: 4FC0E8 → 74EBD5
Hoxnox_banner1: 959494 → BC9065

Hey @Anupam-dagar, I'm doing it in phases to make sure everything fits in-line with the new logo specs. 😄

@maitreyav thanx for the contribution, but this one has a lot of variation in colors.I will have to make some major changes to accommodate these images.Let the images remain same as of now.

Sure, @Anupam-dagar. I was just testing how it will look visually appealing & unique with different blends as the user progresses.
The current Windows 8.1 hero image felt out of place with the current logo.
I feel there's bit inconsistency in typography and colours of UI elements aren't going well with the backgrounds. I'll be happy to contribute on that. What you say?

yeah I didn't paid any attention to typography while developing it.Sure you can suggest some good typography.

Open Sans seems good, in my opinion. Also, Raleway. I have a mockup in mind for the homepage.

I'll be sharing some concepts for the homepage and more in coming days.


Toast role="status" instead of role="alert"

Toast currently has the role attribute set to "alert", SLDS documentation specifies it as "status".
DSR Toast Snapshot:
https://github.com/salesforce/design-system-react/blob/master/components/toast/__tests__/__snapshots__/toast.snapshot-test.jsx.snap#L9
Toast documentation:
https://lightningdesignsystem.com/components/toast/#site-main-content

Yeah, it can updated. I've asked the SLDS team if we need to remove "the focus grab" also, on their GUS channel.

OK, SLDS says keep focus because of the links are present. Let's just align to role status as you said.


in terminal not input code

hello, when i open terminal ,i don't input anyone code,i don't know what went wrong。can you help me,thank you very much!

I am getting the same issue. No directory, just a flashing cursor with the inability to type

See issue #321

Terminal-fusion
Work for my
https://atom.io/packages/terminal-fusion


Add warning-generating keyword 'params' to reserved keywords list

This fixes a warning with some GraphQL type names.

@Zaid-Ajaj  - bump - would love to get this merged.

@varon merged and published as of Snowflaqe v1.48

Thank you, @Zaid-Ajaj


napari/_qt/qt_event_loop.py has Deprecation Warning without version number.

🧰 Task
In napari/_qt/qt_event_loop.py There is a warning without version number:
285-    warn(
286-        trans._(
287-            "\nThe 'gui_qt()' context manager is deprecated.\nIf you are running napari from a script, please use 'napari.run()' as follows:\n\n    import napari\n\n    viewer = napari.Viewer()  # no prior setup needed\n    # other code using the viewer...\n    napari.run()\n\nIn IPython or Jupyter, 'napari.run()' is not necessary. napari will automatically\nstart an interactive event loop for you: \n\n    import napari\n    viewer = napari.Viewer()  # that's it!\n",
288-            deferred=True,
289-        ),
290:        FutureWarning,

It would be nice to :

[ ] find since when/which PR/Whihch napari version it has been there.
[ ] add the version number in the message, and
[ ] potentially remove the deprecated functionality if we believe it's been long enough.

All of this are issues that would be easy for new contributor.

The gui_qt context manager was deprecated in https://github.com/napari/napari/pull/2533 on April 14, 2021.
That means the first napari release including a deprecation warning for gui_qt was napari version 0.4.8, released on May 19, 2021.

potentially remove the deprecated functionality if we believe it's been long enough.

I guess the real question is: when is "long enough"?
Personally, I'm in favour of removing it in the 0.5.0 release, since it's been deprecated for almost three years so far (and I imagine it will be longer than three years by the time the 0.5.0 release is done).


TypeScript interop example

@bhansconnect Thanks for the great comments! I believe they have all been resolved, and I also did some refactors to make things more reusable for future glue gen.


Move deployment to Travis CI

Work in progress here: https://github.com/hypriot/cluster-lab/tree/move_to_Travis-CI

That's already done.


Directories themselves do not contribute to size like they do in du

While experimenting with different distro images in Docker, I noticed that du and dua were a bit inconsistent (and later that du itself was inconsistent too with --apparent-size if the version of du was older).
I discovered that dua reported /usr/share/man as only 20KiB, but du was showing about 1MB. This location had many directories nested and most empty. Other locations were like this as well (I had been using zypper --installroot /rootfs install glibc for example to see how much space the package would weigh), contributing several MB in weight invisible to dua for this small glibc package (2.7MB of 10.7MB total). This is due to each directory using a minimum 4096 bytes as the smallest block-size, with a new enough version of du the --apparent-size option will treat these as 0 bytes.
dua has the -A / --apparent-size flag too, but without it directory size seems to still be treated as 0 bytes. Perhaps that is useful for some users vs using dua -A? 🤷♂

The linked discussion comment above suggested to raise an issue about this behaviour since it's technically a bug.
https://github.com/Byron/dua-cli/discussions/121#discussioncomment-10541462

It would probably be more correct if dua would also count empty directories as consumer of an inode, which typically clocks in at 4KiB.

It would be neat if dua interactive also supported toggling between --apparent-size btw, which as a bonus would make it available in the TUI help view?

Thanks a lot for reporting!
I think this issue should remain focussed on making the size-on-disk include directories as consumer of a single block.
Supporting the --apparent-size flag for interactive sessions (either interactively or using the flag) should be a separate issue, otherwise it might get lost here.


citygml-lod3-datasets/DEBY_LOD3_4959457

After the postprocessing workbench, a small wall part was erased

resolved!


ct: init at 0.4.1

Motivation for this change
Adds a package.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Things to do
I am very close to finishing this, there is just one catch. The output of running nix-build -A ct.all produces:
$ ls result-bin/bin/
internal  tools

The internal binary should be called ct and the tools binary should be discarded. I do not know ho to do this and despite my best efforts I have not been able to figure out the best way to fix this issue.
Once I am able to rename the binary the package should be ready to be merged, barring any welcomed feedback from the nixpkgs maintainers.
This is my first time contributing to nixpkgs. I am very excited to help the project. Feedback is welcome.

@Mic92 Thank you for the feedback. Let me know if there's anything else I should do.


the unit of socket_timeout and socket_connect_timeout  in RedisCluster

hi, the unit of the socket_timeout and the socket_ connect_timeout, seconds or milliseconds? who can help me？

@zhaoyi2 The issues section is for issues, if you have a general question please ask them inside the Discussion tabb here in github

@zhaoyi2 The issues section is for issues, if you have a general question please ask them inside the Discussion tabb here in github


Production build without SSR

🚀 Feature
Allow production builds without SSR
Motivation
I’v some custom plugins/webpack-loaders which seems to require the window object.
Works fine in dev build, but fails to build for prod thanks to SSR.
I don’t need SSR, a normal SPA is good enough for my purpose.
<BrowserOnly/> is not resolving my issues.
Pitch
Add a new flag to build
build no-ssr.

I don't think it is something we want to support unless there are strong args and many people asking for this.
Docusaurus is focused on content-centric websites and SEO, SSR, Jamstack is important for such sites.
Why is your build failing? BrowserOnly may be not enough, you might also need a lazy require instead of a top-level ES import.
https://github.com/facebook/docusaurus/discussions/4514


Update CONTRIBUTING instructions, and make PR template optional.

The contributing instructions were updated to reflect recent changes.
The pull request template for elements was moved to the hidden directory to make its use optional.

I will wait for #22 to be merged, then rebase here and update the guidelines about SSH cloning, as discussed during today's meeting.


Update setup.cfg

[x] Exclude holidays version 0.17
[x] Set Python range to 3.10 - 3.11

Exclude holidays version 0.17
-  f665c5043db3fde6e66882c21cec1c754d5488d3

Set Python range to 3.10 - 3.11
- 941a8cae58094d1f6c9cc269320aaf69c97f2083

Resolved by #25.


refactor(Algebra/Polynomial/Lifts): Golf some proofs

This PR golfs some proofs in Algebra/Polynomial/Lifts.lean.

maintainer delegate

There are two comments, but LGTM, thanks!
bors d+

bors r+


Morning session code review

In this code review, we suggest making the following improvements:

Make the close button of the mobile menu smaller in accordance with the Figma design. Further, I think you should increase the margin-top of the button because it is too close to the top of the viewport. In the Figma design, there is more space.
Please add alt attributes to social media icons, for accessibility reasons.

Completed


Failure of constr. projection now correctly handled in visibPRM

For a constrained problem, previous version of visib-PRM was using the projected sampled configuration even if he projection has failed.
This was leading to anormal 'jumps' of configurations when these wrongly projected configurations were present in the final path.

Merged into branch devel


Error 'Cannot read Cannot read properties of null (reading 'isSignedIn')'

VM219 google-auth-context-provider.js:121 gapi failed TypeError: Cannot read properties of null (reading 'isSignedIn')     at _callee$ (webpack-internal:///./src/google/context-providers/google-auth-context-provider.js:78)     at tryCatch (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:67)     at Generator.invoke [as _invoke] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:284)     at Generator.eval [as next] (webpack-internal:///./node_modules/regenerator-runtime/runtime.js:120)     at asyncGeneratorStep (webpack-internal:///./node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js:7)     at _next (webpack-internal:///./node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js:29)

isSignedIn is an attribute on the Google Auth Instance. It appears that something is causing this to not be initialized correctly.
Are there earlier errors logged?
Bret

Now it is working perfectly. I am not sure what happened here since I did not make any changes to the code. Thank you for your quick response!


build: Use pkg-config to find libseccomp on Linux

Some Linux distributions install libseccomp in non-standard directories.
Use pkg-config to look for it instead of guessing. Note that this
makes pkg-config a hard build-time dependency.
While we're at it, we can use pkg-config to do version tests, so make
libseccomp >= 2.3.3 a hard requirement and warn but proceed on
libseccomp < 2.4.1.
Fixes #419, fixes #418 (by eliminating the no-targets case).

(CI is actually passing, with a dummy commit that I have now removed)


Add more queries

Expand the possible ways the deployed multisig can be queried.

Query details by multisig core addr
Query details by original signing address

I guess one to query details by a member address could be useful as well, so user can see what msigs are available for them. Need to store members in the msig details then.


Including info about NativeScript in Native Rendering

Just added a paragraph about NativeScript and its Vue integration in the
"Native Rendering" section of the guide

Thanks! I shortened it slightly and made it more clear that the plugin is still relatively early in development.


Added documentation for conditional mocks

Relates to https://github.com/php-http/documentation/issues/255 and https://github.com/php-http/mock-client/pull/27

I'd agree with all the comments. On some of the style preferences, there's a couple of places in the docs which might want to be updated to match, for consistency if that's the preferred style.
I've updated the pull-request anyway - hope that's better.


Use other network plugin except flannel

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Is it possible to add option for replacing flannel as default network plugin?
currently there is only option for adding calico alongside flannel
but we observe some issues with ip assignment to pods
seems pods like coredns has been assigned ip by flannel and all new pods assigned ip by calico, and looks like there is little overlapping with ip pools
New or Affected Resource(s)

Potential Terraform Configuration

# Copy-paste any Terraform configurations for how the requested feature may be used.

References

Hi,
It is not possible to change the CNI for now. However, you can use Calico for network policy.

Thanks for reply,@hyder !
One more question
If we install calico alongside flannel , we observe some strange behaviour
After cluster installation, in kube-system namespace some pods, like coredns, dns-autoscaler, calico-node-controller are using ip from subnet <IP_ADDRESS>/16
for example:
coredns-5f5f66466b-tbwxq  <IP_ADDRESS>
or
coredns-5f5f66466b-n267r <IP_ADDRESS>
but when we install some other apps, somehow new pods assigned same ip that already has been assigned to existing pods in kube-system, and this kube-system pods starts crashing, because they can't pass readiness health checks
 scheduler-app             <IP_ADDRESS>   3/3 Running
coredns-5f5f66466b-n267r   <IP_ADDRESS>   0/1 Running

and it happens for all ip that already assigned to some system pods, they are reassigned to new pods
when we delete these system pods they recreated and has been assigned new ip and this overlapping never happens again
is it correct behaviour?


Yarn tests fail when building from source - potential timezone issue

Describe the bug
Following the instructions in https://github.com/yesoreyeram/grafana-infinity-datasource/blob/main/CONTRIBUTING.md, I am able to successfully build the plugin (e.g. with yarn watch). But when running yarn test or yarn build, the tests fail. All failing tests are due to mismatched timestamps.
Steps to reproduce
Check out code from git (either main branch of v1.2.0 tag). Run yarn and then yarn test.
Several tests fail, as timestamps are off by exactly 1 hour with respect to the expected time.
My timezone in CET (UTC+1) and my computer's clock is set to local time. I suspect this is the issue - though haven't had the chance to test with building on a machine in the UTC timezone.
Relevant output from failing tests:
 FAIL  src/app/uql.test.ts (8.473 s)
  ● uql › nested array parsing

    expect(received).toStrictEqual(expected) // deep equality

    - Expected  - 9
    + Received  + 9

      Array [
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 11.1,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 111.1,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 1.1,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 22.2,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 222.2,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 2.2,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 33.3,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 333.3,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 3.3,
        },
      ]

      83 |           | project "timestamp"="series.timestamp", "value"="series.value", "host", "disk", "metricId"
      84 |           | extend "timestamp"=unixtime_milliseconds_todatetime("timestamp")
    > 85 |           | order by "timestamp" asc`,
         |                                                   ^
      86 |         { data }
      87 |       )
      88 |     ).toStrictEqual([

      at next (src/app/uql.test.ts:85:51)
      at fulfilled (node_modules/tslib/tslib.js:114:62)

 FAIL  src/app/parsers/JSONParser.spec.ts (10.16 s)
  ● JSONParser › With Columns & Root Selector

    expect(received).toMatchSnapshot()

    Snapshot name: `JSONParser With Columns & Root Selector 2`

    - Snapshot  - 2
    + Received  + 2

    @@ -36,16 +36,16 @@
            2011-01-01T00:00:00.000Z,
          ],
          Array [
            "baz",
            30,
    -       2012-01-01T00:00:00.000Z,
    +       2011-12-31T23:00:00.000Z,
            2012-01-01T00:00:00.000Z,
          ],
          Array [
            "apple",
            32,
    -       2013-12-25T00:00:00.000Z,
    +       2013-12-24T23:00:00.000Z,
            2013-12-25T00:00:00.000Z,
          ],
        ],
      }

      146 |       },
      147 |       {
    > 148 |         text: 'Year',
          |                                        ^
      149 |         type: 'timestamp',
      150 |         selector: 'year',
      151 |       },

      at Object.<anonymous> (src/app/parsers/JSONParser.spec.ts:148:40)

 › 1 snapshot failed.
 FAIL  src/app/parsers/XMLParser.spec.ts (10.436 s)
  ● XMLParser › Basic XML

    expect(received).toMatchSnapshot()

    Snapshot name: `XMLParser Basic XML 3`

    - Snapshot  - 2
    + Received  + 2

    @@ -19,14 +19,14 @@
        "name": "",
        "rows": Array [
          Array [
            2553517.5573549946,
            "hello",
    -       2021-11-12T00:00:00.000Z,
    +       2021-11-11T23:00:00.000Z,
          ],
          Array [
            2552517.557354985,
            "world",
    -       2021-11-11T00:00:00.000Z,
    +       2021-11-10T23:00:00.000Z,
          ],
        ],
      }

      106 |         text: 'foo',
      107 |         type: 'string',
    > 108 |       },
          |                   ^
      109 |       {
      110 |         selector: 'e3',
      111 |         text: 'date',

      at Object.<anonymous> (src/app/parsers/XMLParser.spec.ts:108:39)

 › 1 snapshot failed.
 PASS  src/components/QueryColumnItem.test.tsx (46.545 s)
 PASS  src/components/SourceSelector.test.tsx (38.821 s)
 PASS  src/app/variablesQuery/index.test.ts (37.296 s)
 PASS  src/app/variablesQuery/VariableQuery.spec.ts (37.528 s)
 PASS  src/components/TypeSelector.test.tsx (48.161 s)
 PASS  src/components/FormatSelector.test.tsx (48.814 s)
 PASS  src/app/UQLProvider.test.ts
 PASS  src/components/GlobalQuerySelector.test.tsx
 PASS  src/app/parsers/JSONParser_JSONPath.spec.ts
 PASS  src/app/variablesQuery/Collection.spec.ts
 PASS  src/app/parsers/JSONParser.2.spec.ts
 PASS  src/app/parsers/utils.spec.ts
 PASS  src/app/variablesQuery/Join.spec.ts
 PASS  src/app/GROQProvider.test.ts
 PASS  src/app/variablesQuery/CollectionLookup.spec.ts
 PASS  src/app/variablesQuery/UnixTimeStamp.spec.ts
 PASS  src/components/JSONOptionsEditor.test.tsx
 PASS  src/app/parsers/CSVParser.spec.ts
 PASS  src/app/variablesQuery/Random.spec.ts
 PASS  src/app/variablesQuery/utils.spec.ts
 PASS  src/datasource.spec.ts (51.739 s)

Summary of all failing tests
 FAIL  src/app/uql.test.ts (8.473 s)
  ● uql › nested array parsing

    expect(received).toStrictEqual(expected) // deep equality

    - Expected  - 9
    + Received  + 9

      Array [
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 11.1,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 111.1,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T21:38:20.000Z,
    +     "timestamp": 2069-11-11T22:38:20.000Z,
          "value": 1.1,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 22.2,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 222.2,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T22:38:20.000Z,
    +     "timestamp": 2069-11-11T23:38:20.000Z,
          "value": 2.2,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3F",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 33.3,
        },
        Object {
          "disk": "DISK-F1266E1D0AAC2C3D",
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.disk.avail",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 333.3,
        },
        Object {
          "disk": undefined,
          "host": "HOST-F1266E1D0AAC2C3C",
          "metricId": "builtin:host.cpu.idle",
    -     "timestamp": 2069-11-11T23:38:20.000Z,
    +     "timestamp": 2069-11-12T00:38:20.000Z,
          "value": 3.3,
        },
      ]

      83 |           | project "timestamp"="series.timestamp", "value"="series.value", "host", "disk", "metricId"
      84 |           | extend "timestamp"=unixtime_milliseconds_todatetime("timestamp")
    > 85 |           | order by "timestamp" asc`,
         |                                                   ^
      86 |         { data }
      87 |       )
      88 |     ).toStrictEqual([

      at next (src/app/uql.test.ts:85:51)
      at fulfilled (node_modules/tslib/tslib.js:114:62)

 FAIL  src/app/parsers/JSONParser.spec.ts (10.16 s)
  ● JSONParser › With Columns & Root Selector

    expect(received).toMatchSnapshot()

    Snapshot name: `JSONParser With Columns & Root Selector 2`

    - Snapshot  - 2
    + Received  + 2

    @@ -36,16 +36,16 @@
            2011-01-01T00:00:00.000Z,
          ],
          Array [
            "baz",
            30,
    -       2012-01-01T00:00:00.000Z,
    +       2011-12-31T23:00:00.000Z,
            2012-01-01T00:00:00.000Z,
          ],
          Array [
            "apple",
            32,
    -       2013-12-25T00:00:00.000Z,
    +       2013-12-24T23:00:00.000Z,
            2013-12-25T00:00:00.000Z,
          ],
        ],
      }

      146 |       },
      147 |       {
    > 148 |         text: 'Year',
          |                                        ^
      149 |         type: 'timestamp',
      150 |         selector: 'year',
      151 |       },

      at Object.<anonymous> (src/app/parsers/JSONParser.spec.ts:148:40)

 FAIL  src/app/parsers/XMLParser.spec.ts (10.436 s)
  ● XMLParser › Basic XML

    expect(received).toMatchSnapshot()

    Snapshot name: `XMLParser Basic XML 3`

    - Snapshot  - 2
    + Received  + 2

    @@ -19,14 +19,14 @@
        "name": "",
        "rows": Array [
          Array [
            2553517.5573549946,
            "hello",
    -       2021-11-12T00:00:00.000Z,
    +       2021-11-11T23:00:00.000Z,
          ],
          Array [
            2552517.557354985,
            "world",
    -       2021-11-11T00:00:00.000Z,
    +       2021-11-10T23:00:00.000Z,
          ],
        ],
      }

      106 |         text: 'foo',
      107 |         type: 'string',
    > 108 |       },
          |                   ^
      109 |       {
      110 |         selector: 'e3',
      111 |         text: 'date',

      at Object.<anonymous> (src/app/parsers/XMLParser.spec.ts:108:39)

Snapshot Summary
 › 2 snapshots failed from 2 test suites. Inspect your code changes or re-run jest with `-u` to update them.

Test Suites: 3 failed, 21 passed, 24 total
Tests:       3 failed, 86 passed, 89 total
Snapshots:   2 failed, 36 passed, 38 total
Time:        53 s
Ran all test suites with tests matching "".
✖ Tests failed

Version Details:

Grafana version : N/A
Plugin code version : v1.2.0 tag or current main branch
Yarn: v1.22.10

Thanks @yesoreyeram for the pointer - unfortunately I didn't see that SO page in my googling, but your proposed solution is spot on!
I'm going to close this as I imagine it's not a widespread issue. Up to you whether package.json in the codebase itself should be tweaked - I'm not sure what the potential trade-offs there are.


Did you get this?

Hi Ric,
Welcome to Zenboards! We're still trying this - but we're hoping it will be useful for managing projects etc.
Best wishes,
Anthony

Hi Anthony,
I can see this, and so will declare that this issue is closed and close it!
Cheers,
Ric

Awesome! Thanks.


check in scripts for ADQ

These are the scripts Juncheng wrote for ADQ tests. These are not ready for merge yet but will be parked here as reference for the blog post. I will start generalizing this test in a day or two to make it more user friendly.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Yao Yue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Refresh rate too slow - Moving to push mode

Right now the integration refresh every 30 sec, which is too slow for many people.
We will be pivoting this integration in pull mode instead of push.
Temporary solution
you can lower the refresh rate
https://github.com/marcolivierarsenault/moonraker-home-assistant/blob/ca5c81fcf24264f6bf3a7910cbb274829c15e9be/custom_components/moonraker/__init__.py#L29

no, tbh, no bandwidth has not progressed in months.

I use to create template switch that makes respectively an output pin from the board up or down; then, using value_template for a numeric sensor I get from the board to refresh the state of the switch.
Having 30 seconds makes the switch temporarly revert to the older state when commuting.
Hardcoding 2 seconds solved the issue brillantly, nonetheless having this pull-based looks definitively much more elegant :)

Why not simply change/update the interval when the printer becomes active?

yeah that makes sense. with the delay to the push mode, I will likely add a parameter to pull at a higher frequence

@jamincollins I have added an option to set a different timer.
details here: https://moonraker-home-assistant.readthedocs.io/en/latest/connection.html#polling-rate-configuration
make sure to download latest (main) version of the code: https://moonraker-home-assistant.readthedocs.io/en/latest/support/latest.html

Thank you

Under configure tab in moonraker integrations on HA

where is that optin for change pooling rate?

Hi @marcolivierarsenault. Is there anything I can do to help move the integration toward push mode? Have you done any work or analysis on it that I can learn from?  I may be overthinking it but one of my concerns is whether we want to update all attributes in Home Assistant at the same frequency that they are pushed (although I've not done any analysis as yet on how often attributes are updated).

no sorry, no work done here.


Multiple settlements are not correctly accounted for

The code currently assumes a single SettleMultipleWithdrawals per transfer. The reality is that this event can be emitted multiple times for a single root. This assumption is seen in the fact that db.transferRoots.multipleWithdrawalsSettledTxHash can  be ovwerritten here when a new event is seen. Additionally, db.transferRoots.multipleWithdrawalsSettledTotalAmount overwrites the value here when it really should add to the existing value.
I'm not aware of all the implications of this change, so they will have to be thought through carefully.

Closed by https://github.com/hop-protocol/hop/pull/380


typo: exlude -> exclude

@nschonni  sorry this repo is being migrated to https://github.com/aspnet/AspNetDocs


[NFC] Change diagnostic text mentioning 'undeclared type'/'unresolved identifier'

TL;DR: I changed "use of undeclared type %0" -> "couldn't find definition of type %0", and "use of unresolved identifier" -> "couldn't find definition of"
Undeclared type diagnostic
The current diagnostic seems unclear from a user-perspective as to what "undeclared type" means, especially if you have not written C/ObjC/C++ before, which do have a distinct notion of declaring types in the surface language, as opposed to only being able to define types. It also potentially nudges the reader familiar with C/ObjC/C++ but new to Swift in an incorrect direction: "ok, this type is undeclared, can I declare it somehow and get rid of this error?" (The answer is you can't; you need to define it or import it.)
While the newer diagnostic is not technically as accurate (e.g. you can have a declaration of a type in a swiftinterface without a definition), that's not really something people write in Swift code (unless this is a part of the language that I don't know about?). So I think the newer diagnostic matches the user model better.
For comparison, Rust says:
cannot find type `T` in this scope

which also seems like a reasonable alternative (although it mentions 'scope' which seems a bit unnecessary perhaps, even though it is technically correct).
Elm is a bit more verbose: (e.g. type X = MakeX { x : Foo })
I cannot find a `Foo` type:
[..]
Hint: Read <https://elm-lang.org/0.19.1/imports> to see how `import`
declarations work in Elm.

Unresolved identifier diagnostic
The basic reasoning is the same as before: "unresolved identifier" is compiler jargon which a user does not necessarily need to care about. Instead we can simply say that we could not find the definition. We could also do something like Rust where we say "cannot find $thing in scope".
Misc Notes

I don't particularly care about the tense. If you think it should be cannot instead of couldn't, I'll change that, nbd.

I read through docs/Diagnostics.md and I don't think the recommendation of "phrase diagnostics as rules rather than reporting that the compiler failed to do something" is a good one. If we follow that recommendation, the diagnostic would look like:
definition of $thing cannot be found in scope

That seems overly aggressive IMO. Moreover, the point of the diagnostic here is not to describe a fundamental language rule (one about scoping and define-before-use), but to gently point out what went wrong. Of course, nothing's perfect, but I think it makes sense to not follow that recommendation here.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - f335438c4e23a7980816f9beb9b9874cac8bf345

Build failed
Swift Test Linux Platform
Git Sha - f335438c4e23a7980816f9beb9b9874cac8bf345

Tracking rdar://problem/62375243.

While the newer diagnostic is not technically as accurate (e.g. you can have a declaration of a type in a swiftinterface without a definition), that's not really something people write in Swift code (unless this is a part of the language that I don't know about?)

Could this be misleading in the context of protocol requirements? This is the one place I can think of where you're declaring things without providing a definition, and I'm wondering if that might cause confusion.

I read through docs/Diagnostics.md and I don't think the recommendation of "phrase diagnostics as rules rather than reporting that the compiler failed to do something" is a good one.

I think at some point we should re-evaluate the rules laid out in Diagnostics.md. This particular rule does seem to encourage more clinical language, which is not very friendly to the user and often leads to these really jargony messages.

Could this be misleading in the context of protocol requirements? This is the one place I can think of where you're declaring things without providing a definition, and I'm wondering if that might cause confusion.

Like in a function signature f<T : P>(_ t : T) -> ()? Or something else?

I just mean in general. Say a user is trying to call a function that is a protocol requirement, and they make a typo. Now, they will get the error message couldn't find definition of X. This could be really misleading because the user might think the error has to do with the conformance to that protocol. The error message isn't telling them that X doesn't exist.

I see what you mean, that makes sense. How about cannot find type X in scope/cannot find X in scope? That doesn't seem to have this problem. Any other ideas?

[Note to self: The test failures were due to LLDB -- it also needs to be updated since it is matching on the diagnostics.]

I agree that dropping definition and being specific about the kind of entity (if we can) avoids this problem. I like cannot find type X in scope/cannot find X in scope (and I haven't come up with anything better).
FWIW I don't think the word scope is jargon - this is a fundamental concept that programmers either will already know, or they will learn. This might be a good concept to explain in an educational note for this diagnostic.

Updated code to use cannot find X in scope/cannot find type X in scope.
Matching LLDB PR: https://github.com/apple/llvm-project/pull/1128
@swift-ci please test

apple/llvm-project#1128
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 5dead8a040764764ac59e685f1aa2b24536ba170

Build failed
Swift Test Linux Platform
Git Sha - 5dead8a040764764ac59e685f1aa2b24536ba170

apple/llvm-project#1128
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 4a48c02c19049e7e5c451982393ff0da57835e43

An LLDB test seems to be randomly failing. 😐
apple/llvm-project#1128
@swift-ci please test


Reduce clone thread to really only do cloning

benchmarking started... will merge after checking the result tomorrow

OK, I did what we discussed. Standard and clone-engine versions now produce identical results down to +- 2 tracks.


Accessibility Issue: Videos lack captions

There should be captions in the videos. Even if there isn't any more information in the videos than is contained in the Instructions, someone who needs the captions would have to do the extra work to find that out. That takes time away from the process of learning.

closed in favor of https://github.com/FreeCodeCamp/hikes/issues/160


FitFile remove caching of messages

Fix #59

@dtcooper @pR0Ps Do you agree to break backward compatibility a bit with this PR?

@pROP This saves a lot of memory. So is necessary when running fitparse on a server.
I think more BC changes should be mate to fitparse in regards of speed. So, a version bump is necessary.  Better to discuss it somewhere else.

What about an argument when instantiating FitFile's __init__ method to turn on/off the message cache?

@dtcooper Yes, an extra parameter would do the job, too. But IMO the FitFile has too many responsibilities and should be broken to more classes. See #72 for my proposal.

Implemented in 08d49beebba826f606de226acdf1537d47f41e6a


Examples of how to test reducer

Could you perhaps provide an example of how you test the reducer for actions that are created with redux-pack? Do you have to create an instance of the actual store and dispatch it as you would in the app?

I recommend using duck tests. We use redux-mock-store instead of a real store for tests.

@einarq I agree with @evandavis, you should not need or want to create a store in order to test a reducer or action creators. In fact, I consider this is one of the primary benefits of redux's architecture.
Right now, testing reducers that respond to redux-pack actions does unfortunately require you know a little bit about the implementation of it. We have discussed exporting test utilities in order to make this easier. Right now, it would go something like this:
import { LIFECYCLE, KEY } from 'redux-pack';
import FooReducer from '../path/to/FooReducer';

// this utility method will make an action that redux pack understands
function makePackAction(lifecycle, { type, payload, meta={} }) {
  return {
    type,
    payload,
    meta: {
      ...meta,
      [KEY.LIFECYCLE]: lifecycle,
    },
  }
}

// your test code would then look something like...
const initialState = { ... };
const action = makePackAction(LIFECYCLE.START, { type: 'FOO', payload: { ... } });
const endState = FooReducer(initialState, action);
assert(endState === expectedEndState);


fixed csv handling

Descriptions:
added more control for user input, users now can input either a list object or a CSV
Fix:
Add fix/changes here

Enhancement available in latest version.


Please note: Don forget to restart terminal after installing NVM for the first time

Restart terminal after you install nvm for the first time, only then will you be able to use it.
I wasted time on finding this out.
Hope this helps beginners save time.

The install script tells you this on the terminal, verbatim. I'm not sure how we can help beginners if people aren't reading instructions :-/


Add crop shape selection to default crop activity.

Adds a Crop Shape icon to the Toolbar
closes https://github.com/CanHub/Android-Image-Cropper/discussions/157
New Feature
Adds a Crop Shape icon to the Toolbar:
Added a few shape icons & change them in the accordingly in the Activity when changing the Crop Shapes of the CropImageView
Once the review is final, I can go ahead with the checklist.

Do you have any specific idea in mind by which we can highlight the change in horizontal/vertical shape crop?

Do you have any specific idea in mind by which we can highlight the change in horizontal/vertical shape crop?

I think would be nice to have height = 2*width for vertical and the other direction 2*h = w for horizontal.

@ItzNotABug any update?


Add missing Polyline options

Found some missing options for Polyline that I needed. Let's add 'em! :)

No. We only expose controlled/uncontrolled as properties in this function call:
https://github.com/Bazze/react-google-maps/blob/add-missing-polyline-options/lib/creators/PolylineCreator.js#L46
Other props should be specified in options just like Native JavaScript V3 API.

Oh, sorry. I was searching for something like that but could find it. Thanks!

Sorry for the confusing here.


display library 'sdl2' not available

Hi again.
I'm getting a new error, but now its with bochs.
I have sdl on my system and i have tried with the official bochs package and the aur package bochs-sdl but it does not work.
I get this:
Bochs x86 Emulator 2.7
Built from SVN snapshot on August  1, 2021
Timestamp: Sun Aug  1 10:07:00 CEST 2021
00000000000i[      ] BXSHARE not set. using compile time default '/usr/share/bochs'
00000000000i[      ] reading configuration from bochs_config
00000000000p[      ] >>PANIC<< bochs_config:7: display library 'sdl2' not available
00000000000e[SIM   ] notify called, but no bxevent_callback function is registered
00000000000e[SIM   ] notify called, but no bxevent_callback function is registered
Bochs is exiting with the following message:
[      ] bochs_config:7: display library 'sdl2' not available
00000000000i[SIM   ] quit_sim called with exit code 1

and i have no clue of why it cant find sdl2.
i needed to take out all the = signs in the error message so the markdown doesn't f*ck up the message.
this is the config file:
megs: 128
romimage: file=/usr/share/bochs/BIOS-bochs-latest, address=0xfffe0000
vgaromimage: file=/usr/share/bochs/VGABIOS-lgpl-latest
floppya: 1_44=build/main_floppy.img, status=inserted
boot: floppy
mouse: enabled=0
display_library: sdl2, options="gui_debug"

ok i dont know what i did more than changing sdl2 to sdl and in the cli thingie chose 6. but now it works.

You can also try x or wx if you have trouble.

Ok il try that when I get up from bed. I just woke up.


Why there is no option to disable scroll arbitrarily?

When using browser scroll, I always have an option to disable scroll with css overflow property. And I can do it whenever I want.
Why there is not the case here? Why there is no simple single option like disabled: boolean to control it?
Are there some fundamental problems to implement it?

oh,I also have this demand. Do you have any other way to solve it, thank you

Agreed this would be a good addition, this is my current solution
<Scrollbars
            renderView={({ style, ...props }) =>
                <div
                    {...props}
                    style={{
                        overflowY: preventScroll ? 'hidden' : 'scroll',
                        {...scroll}
                    }}
                />
            }
/>


Fix Spring hints for storage

Description
To fix errors encountered in https://github.com/sdeleuze/image-function, to add more hints.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

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


Fix JSON source type

Adds a JUnit test as well - using just checking.getAsString() resulted in an UnsupportedOperationException.

Thanks


Edited User Guide

Pull Request Test Coverage Report for Build 367

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

Totals

Change from base Build 366:
0.0%

Covered Lines:
1593

Relevant Lines:
2910

💛  - Coveralls


vidpid->state lookup container improvement; changing to std::array

While refactoring XLink using libusb wrappers, I saw that the vidpid -> xlink state lookup is implemented as std::unordered_map vidPidToDeviceState. For XLink's use case, this is a poor choice as it uses more memory, more binary size, and more cpu than a simple solution with std::array.
I wanted to learn/play with some new ai and benchmarking tools. They all agree to switch to std::array.
I am changing it in my refactor.
Setup

XLink at all current major branches
all platforms and compilers

Repro
First found with code review. godbolts and benchmarks below.

with only 4 elements, std::array is more efficient in code and memory than std::unordered_map
std::array has zero memory overhead and no allocations; can store the values at compile-time; search by comparing (at most) 8 ints
std::vector has memory overhead of ~24 bytes (on 64bit); runtime has to insert values into heap; search by jumping to heap location of vector data and comparing (at most) 8 ints
std::unordered_map has memory overhead of 72+ bytes (on 64bit) + ~20 bytes per element; runtime has to insert values; search by hash calc, hash calc, binary op, jump to calculated hash bucket pointer, jump to buckets linked list, walk linked list and compare 2 ints for each entity until find the match (walking list up to 4 times...likely less)

For this use-case of fixed never-changing elements and very small size, std::array is the best choice.
At https://godbolt.org/z/KM3E9Gdfd is code for both today's std::ordered_map and a new impl with std::array. You can chose which you want with -DUSE_UNMAP or -DUSE_ARRAY. After it compiles, notice several things
Result

The std::array implementation has compile-time created the array and stored it in the binary for immediate use by the app. This results in faster load times, no overhead, no memory allocations. gcc is also optimizing the compiled code given it knows what is in the array at compile-time. In contrast, the map implementation will have the raw initialization data stored somewhere in the binary and then it has to make heap allocations for each created entry into the map and make copies of the initialization data into them.
The binary size difference is substantial. array = 95,505 and unordered_map = 497,156. The map is 4x larger. (additional 400kb) in filesize 😥. All that extra code for nothing since this map is never mutated and t-i-n-y.

When benchmarked https://quick-bench.com/q/CNuAH-ebWBdson0Epl-F--C3ZXI the array implementation is 3.8x faster than map.

Slightly altered code to generate random vidpids show array still faster (1.3x faster) but not as dramatic. https://quick-bench.com/q/orjPkib5xLpID0nitgWJc-VowTY. I think this is due to the addional load of generating random numbers and that since a fixed search vidpid isn't known at compile time, then gcc can't optimize as aggressively.

The speed increase is not really significant. If that were the only thing I would say this is microoptimization ;-)
However, the file size is significant. Saving 400kb in filesize justifies the trivial change to std::array.

The speed increase is not really significant. If that were the only thing I would say this is microoptimization ;-)
However, the file size is significant. Saving 400kb in filesize justifies the trivial change to std::array.

Agree on the conclusion - though WRT file size, what is that measuring, final compiled binary?

Yes final -O2 compiled binary size on disk. You can see it in the godbolt links. It is in tiny text in the compiler output pane.
I do also see unordered_map  being used for the createPlatformDeviceFdKey() map store. The file savings might not be as large since some of it is (maybe?) shared.
The createPlatformDeviceFdKey map itself is a area that I'll investigate within just a few days as it involves my c++ work in #63. This is one of the C <-> C++ boundaries that I want to handle well. During that investigation, I'll explore how large that map becomes and how often it is mutated....to understand what container is best used for it. While the USB scenario isn't so many (only so many ports usually on a computer), the PoE scenario could be up to MAX_LINKS which is currently 64.

Yes final -O2 compiled binary size on disk. You can see it in the godbolt links. It is in tiny text in the compiler output pane.
I do also see unordered_map being used for the createPlatformDeviceFdKey() map store. The file savings might not be as large since some of it is (maybe?) shared.

Got it - yeah, in that case would be intermixed with other uses

The createPlatformDeviceFdKey map itself is a area that I'll investigate within just a few days as it involves my c++ work in https://github.com/luxonis/XLink/pull/63. This is one of the C <-> C++ boundaries that I want to handle well. During that investigation, I'll explore how large that map becomes and how often it is mutated....to understand what container is best used for it. While the USB scenario isn't so many (only so many ports usually on a computer), the PoE scenario could be up to MAX_LINKS which is currently 64.

This is a "one time" modded structure per up/down event. And the lookups thereafter to retrieve the actual FD (per R/W event)

This is fixed in my fork of XLink. It is faster (tests above) and smaller filesize (also above). The latter is most beneficial when xlink is a DLL instead of a static library. While this is function is not a high-volume use, these fixes are code simplification; removing unneeded complexity and filesize.
Closing as the fixes can be seen around https://github.com/diablodale/XLink/blob/636dc4142774e11f9a1d68125575f2782d65744a/src/pc/protocols/usb_host.cpp#L165


Terminal not full width

VSCode Version: 1.41.0
OS Version: macOS 10.15.2 (19C57)

Steps to Reproduce:

open terminal
the right hand side has an empty space, so the terminal can not be full width

Does this issue occur when all extensions are disabled?: Yes

same as https://github.com/microsoft/vscode/issues/86425


Extra new line while using Telnet connection

Windows Terminal version
<IP_ADDRESS>.0
Windows build number
10.0.19043.1526
Other Software
VMware® Workstation 16 Pro (version: 16.1.0 build-17198959)
EVE-NG Community edition (version: 2.0.3-112)
Steps to reproduce
I use WT for network labs. I connect to nodes with a Telnet connection. And while I am inside the CLI of nodes and doing some stuff there. Exactly at this point when I press the Enter key to go to the new line. It gives me two new lines. It feels like I have pressed the key twice.
Instead of WT when I use Solar-Putty this does not happen. Whereas I prefer to use WT and want it to work properly.
Expected Behavior
It should give only one new line each time I press to the enter key
Actual Behavior
It doubles the new line. Which is irritating.
In case you need more detail, the following virtual images are from vendors such as:

Juniper: vMX Router:

Cisco: IOS Router:

how the devil did we not see your first post...? That apparently never got into the triage queue. Sorry about that! Which telnet client are you using?

I use SolarPuTTY and Windows Terminal

Okay, where'd you install telnet.exe from? Did that ship with SolarPuTTY or did you get it from somewhere else?

Isn't the Telnet default Microsoft Windows Feature? If not then SolarPuTTY is based on the PuTTY emulator, so perhaps this is where it shipped from.

Workaround/fix:
Host: telnetd on Terminal IDE app by SpartacusRex
Client: PuTTY telnet
Fix: open PuTTY settings > Connection > Telnet > remove checkmark from box "Return key sends Telnet New Line instead of ^M"

Hi 👋
same issue here. I use telnet for my GNS3 lab.
In my case, this is the telnet I use:
Name            : telnet.exe
CommandType     : Application
Definition      : C:\WINDOWS\system32\telnet.exe
Extension       : .exe
Path            : C:\WINDOWS\system32\telnet.exe
FileVersionInfo : File:             C:\WINDOWS\system32\telnet.exe
                  InternalName:     telnet.exe
                  OriginalFilename: telnetc.exe.mui
                  FileVersion:      10.0.22621.1554 (WinBuild.160101.0800)
                  FileDescription:  Microsoft Telnet Client
                  Product:          Microsoft® Windows® Operating System
                  ProductVersion:   10.0.22621.1554
                  Debug:            False
                  Patched:          False
                  PreRelease:       False
                  PrivateBuild:     False
                  SpecialBuild:     False
                  Language:         English (United States)

I also got this same problem, anyone can help on this ?

@Ashirov , do you have any workaround?

Change the value of CRLF from 1 to 0 in registry works well for me.


feat: RunnerSets

This is still WIP but I just wanted to submit this as a draft for the early review :)
The build passes and the implementation should be complete. But it's not tested at all. I'll make this out of the draft state once I've tested it on a real cluster.
UPDATE: This is tested E2E with running a Ginkgo suite on GitHub Actions. See make test and pkg/controllers/runnerset_controller_test.go.

RunnerSet is basically ReplicaSet for Runners.
It is responsible for maintaining number of runners to match the desired one. That is, it creates missing runners from .Spec.Template and deletes redundant runners.
Similar to ReplicaSet, this does not support rolling update of runners on its own. We might want to later add RunnerDeployment for that. But that's another story.
Notes:

RunnerSet has availableReplicas and readyReplicas under Status, which are showns in kubectl get output as AVAILABLE and READY respectively. These are borrowed from ReplicaSet.

@summerwind I believe this is now ready for your review.
Not sure this can either be a long-term solution or not. But I think this still worth being included in this project as the baseline to compare future solutions against.
Background: As we've talked face-to-face, a StatefulSe-and-mutating-webhook based solution may replace this. We may completely remove RunnerSet and instead just introduce RunnerDeployment based on that.

I've added make tests to run E2E tests on GitHub Actions. I've confirmed it to work on my fork. Please see Run tests job in https://github.com/mumoshu/actions-runner-controller-ci/runs/459416632?check_suite_focus=true

@mumoshu Thank you for adding tests in addition to the implementation!
I agree with using this as a "baseline" implementation.
The code looks good to me. Let's merge.


Add automatic fold after save to TeX-fold

Since the Tex-fold-buffer bind (C-c C-o C-b) is really clunky and preferably we (I?) want the buffer as folded as possible, I see this as an optimal solution.

I'm not sure I always want the buffer as folded as possible. Many times I save + compile to see what my changes made to the pdf. In case the cursor was in something that would be folded (say a footnote, or in the middle of a macro), folding would kick it out of there. That's also why +latex-fold-last-macro-a does a wierd search instead of just folding the current paragraph - to have the smallest chance of getting in your way.
Personally, I just use the TeX-fold-paragraph keybind (SPC m f) from time to time.

@tecosaur
I never encountered such a large file...
How about we define a defcustom for it can be turned off/on from the user config.el?

How about we define a defcustom for it can be turned off/on from the user config.el?

Seems like an overcomplication to me, instead of leaving it to the user to add the after-save-hook.

Since it seems to boil down to personal preference, has possible performance implications, and is trivial for users to add to after-save-hook, I'll turn down this PR. Thanks for bringing it to my attention, in any case!


after upload the file, got an error message "Language Client is not ready yet." what does it means?

after upload the file, got an error message "Language Client is not ready yet." what does it means?

Originally posted by @TalariaxKhin in https://github.com/microsoft/azuredatastudio/issues/2090#issuecomment-1200632887

I have installed the latest version of Azure data studio and connecting successfully to SQL Server in a docker container on my Pop!_OS. I installed this extension and while importing any csv files, i am getting the following errors on the 2nd step of the import wizard:
- Error: Connection got disposed.
- Language client is not ready yet
- Cannot read property 'map' of undefined

When i opened and checked the extension page in Azure Data Studio, in the runtime status section it shows the following error:

Does anyone know how to resolve this issue?

@aasimkhan30 any ideas what these errors on Import extension activation would mean?
@SIFAR786 could you please check the "Help->Developer Tools" Console for the callstack details for the exceptions that are being raised (if present)?  Thanks!

@kburtram i am not sure i understood your request. I don't know how to get the call stack details. Kindly help.

I have the same issue here. Any updates on how to solve it ?

same issue here as well

this is the screenshot of the callstack.

moving to march milestone. The fix is independent of ads release


they did not do the same thing.

now they do.

Actually, you misunderstood the example. The one you "corrected" is meant to demonstrate property binding.
I think I can clarify the label so that is more obvious.
Closed by PR #1568

My brain wasn't working logically at the time. I can see now, they indeed do the same thing. However, it can be clearer so no one have a change to misunderstand like I did.

And I think I have improved it. Thanks for bringing it to my attention.


Implement Clone for reqwest::Error

Can we derive/implement Clone for reqwest::Error, so the error can be shared across threads.

Need this so shared futures work. Meantime, I'll use some kind of workaround to map the error values to my own cloneable type. 😢


Tier is always Epic if you have too much luck

This issue was first found by someone on a server using relics (from the RelicEx mod, the server uses the latest MMC1-Fabric modpack) that gave luck. They noticed every time they reforged an item, it was always Epic.
I tested this on singleplayer by only giving me the luck effect (as the relics are hard to replicate), and noticed the issue started at around luck 40~45, but you could get other (better) tiers from time to time. Starting at luck 50 the only tier when reforging is Epic.
I know is a bit of an edge case, but one would expect that with better luck you would get better tiers and not get stuck only with Epic.
Thanks in advance!

I've tested this and it works fine for me. By vanilla the player will never see such a high effect lvl btw^^
Change the config setting called luck_reforge_modifier to a lower value to reduce the effect of luck.


Pre-0.0.2 housekeeping

This pull request is meant to do some general project housekeeping tasks.
It:

Bumps various crate and node package versions that could be increased with only minor refactoring;
Addresses a todo by refactoring the list_directory function;
Addresses a todo by adding removed thumbnail counting;
Addresses a todo by providing a description for ThumbnailGenerationJob; and
Addresses a todo by making PauseJob and ResumeJob take an AcknowledgeableCommand parameter.

Any reason not to bump it up to 1.77.2 (the current stable release)?

I don't think so, might as well give it a shot and see what CI says

@JMicheli I updated the toolchain and a few other miscellaneous things (e.g. pdfium version, lints after updates, merge conflicts, etc).
There was actually a clippy bug I found, too!
Let me know if there's anything you want to add to this PR. I'll plan to merge this tomorrow after work, get a nightly image out, then 0.0.2 over the weekend. Thanks again for doing all of this cleanup!

I won't have time today to do anything further, I say merge it if you're good to do so.


Strip build directory from pachd stack traces

This is the 2.1.x version of #7413
Currently, stack traces emitted by pachd include the directory that pachd was built in, e.g. /Users/avigil:
Info 2022-03-09T23:16:08.889986614Z error stack:
  github.com/pachyderm/pachyderm/v2/src/internal/task.(*etcdDoer).Do.func1.2.1 /Users/avigil/Pachyderm/Pachyderm_releases_2.1.x/pachyderm/src/internal/task/etcd_service.go:145
  github.com/pachyderm/pachyderm/v2/src/internal/collection.watchF /Users/avigil/Pachyderm/Pachyderm_releases_2.1.x/pachyderm/src/internal/collection/etcd_collection.go:587
  github.com/pachyderm/pachyderm/v2/src/internal/collection.(*etcdReadOnlyCollection).WatchOneF /Users/avigil/Pachyderm/Pachyderm_releases_2.1.x/pachyderm/src/internal/collection/etcd_collection.go:697
  github.com/pachyderm/pachyderm/v2/src/internal/task.(*etcdDoer).Do.func1.2 /Users/avigil/Pachyderm/Pachyderm_releases_2.1.x/pachyderm/src/internal/task/etcd_service.go:131 golang.org/x/sync/errgroup.(*Group).Go.func1 /Users/avigil/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:57 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1581

This removes the /Users/avigil from pachd/pachctl stack traces (tested manually, locally)

Per Slack conversation with Tony, we'll merge this after the code freeze is over

Because v2.1.4 is now released, I'm merging this PR


Add ReductionRows as part of the SYCL-BLAS library

@Bensuo Requesting you as a reviewer on this.

If you rebase on master once #307 is merged that should fix the issues with the checks.

@Bensuo and @mehdi-goli The build is working and the issue with lowest() is fixed. Can you approve the PR?


cuda-driver-dev may need to expose the driver stub to LD_LIBRARY_PATH

In pre-CUDA 12, it's expected that the libcuda.so stub is default loadable, but it seems this assumption no longer holds, and I have to tweak it so that the import cupy test (which loads the stub) works with CUDA 12.

Looking to add cuda-cudart-dev_{{ target_platform }} as a requirement of cuda-nvcc-impl_{{ target_platform }} in PR ( https://github.com/conda-forge/cuda-nvcc-feedstock/pull/11 ) to ensure it is present and near the compiler when it links it. Hoping that is enough
Would be a little worried about adding the stub libraries to LD_LIBRARY_PATH as it can cause issues in runtime environments (where maybe a compiler and these libraries are also needed for CuPy or Numba). Namely the stub libraries get picked up by the library loader instead of the actual libraries
So would suggest we try and see if we can solve this in the compiler package (maybe tweaking the search paths of the compiler itself)

In pre-CUDA 12, it's expected that the libcuda.so stub is default loadable, but it seems this assumption no longer holds

This is not true. Pre-CUDA 12, there is a /usr/local/lib/libcuda.so.1 in the docker image we use which loaded by the dynamic linker. With CUDA 12, we use the regular docker image without that library.


Requirements should only be used to eligibility criteria

From work in Kiev:
(1) Requirements should only be for eligibilityCriteria which are pass/fail criteria applying to a bidder, not awardCriteria which can be evaluative criteria (pass/fail OR weighted) that apply to the item or the bidder. At the moment we suggest it can be used for both, and give an example based on properties of the item.
(2) Requirements may (in some cases) vary by lot - suggested a relatedLot property may be required in some cases.
We identified a couple of terminological issues to clarify:

Qualification criteria - pass/fail  - is the bidder eligible 'in general' to participate in procurement
Eligibility criteria - pass/fail - is the bid eligible
Selection criteria - weighted scoring - how should features of the bid or bidder be factored into the selection (against pricing criterial also)

We need to:

[ ] (1) Evaluate where use of requirements is currently recommended;
[ ] (2) Review whether we can use the requirements data model for award criteria, or whether the ProZorro features approach is appropriate for this
[ ] (3) If (2) then check whether we should use the same object, but different properties for (e.g.) eligibilityCriteriaStructured and awardCriteriaStructured

Note that EU might just need very simple awardCriteria breakdown to who balance between price and non-price criteria.
Related issues:

https://github.com/open-contracting/standard/issues/385#issuecomment-278358093
https://github.com/open-contracting/standard/issues/499

In NSW eTendering and AusTender (Australian commonwealth) there are criteria based on the CCCEV. They are never evaluated automatically, and many of the responses are documents (insurances, evidence of previous performance, qualifications etc).  Each criteria is given a pass/fail rating during the evaluation phase. These are prequalifications, so a contract is not directly awarded based on the status of the criteria.
Based on Tim's comment, we would have an Eligibility Criteria for each item, and (I assume) when every item passes the tenderer becomes qualified.  From the information on this ticket at the moment, I can't decide where the pass/fail for each individual item would go.  Working on that this week.

Moved https://github.com/open-contracting/ocds-extensions/issues/4


Unresolved import when using "extern crate self as"

I created new project using cargo init --lib, and wrote following code in src/lib.rs
extern crate self as x;
pub struct A;
pub use x::A as B;
pub use crate::A as C;

Then an unresolved import error occurred at line 3.

version: nightly (2472851)
I'm getting another error (unresolved extern crate) on the first line.
This error has been occurring since commit 98718e0544.

version: nightly (2472851)
I'm getting another error (unresolved extern crate) on the first line.
This error has been occurring since commit 98718e0544.


Add future package to ensure Python2 compatibility

Hi @davidgasquez!
Just a small fix, I came across an issue on this line when trying to use kiner in Python2:
https://github.com/bufferapp/kiner/blob/master/kiner/producer.py#L4
It seems this was caused by importing from queue instead of Queue (http://python-future.org/compatible_idioms.html#queue)
The easy fix was just to use the future package, which could be great for potential other compatibility issues.

Merging this into master because we need it :smile:

Thanks @michael-erasmus! I see the build failing because the secret is malformed. I'll fix that later, for the moment I pushed the new version to Pypi.