Remove supportsConcurrency flag from top-docs collector managers.

Our collector managers have a supportsConcurrency flag to optimize the case when they are used in a single thread. This PR proposes to remove this flag now that the optimization doesn't do much as a result of #13943.

Here is the output of luceneutil on wikibigall with -searchConcurrency 0. Despite the removal of optimizations for the case when there is no search concurrency, all variations look like noise:
                            TaskQPS baseline      StdDevQPS my_modified_version      StdDev                Pct diff p-value
                         LowTerm      987.41      (9.9%)      964.04      (9.5%)   -2.4% ( -19% -   18%) 0.441
               HighTermTitleSort      138.88     (11.1%)      136.20     (12.3%)   -1.9% ( -22% -   24%) 0.602
                         MedTerm      663.03      (9.5%)      651.84      (9.1%)   -1.7% ( -18% -   18%) 0.568
                      TermDTSort      350.84     (11.6%)      345.28     (13.6%)   -1.6% ( -24% -   26%) 0.692
                        HighTerm      420.03      (9.3%)      413.92      (8.4%)   -1.5% ( -17% -   17%) 0.603
           HighTermDayOfYearSort      808.94      (9.4%)      798.37      (9.0%)   -1.3% ( -18% -   18%) 0.654
                        PKLookup      258.88     (10.6%)      255.85     (10.6%)   -1.2% ( -20% -   22%) 0.727
                          IntNRQ      183.20     (14.4%)      182.00     (12.9%)   -0.7% ( -24% -   31%) 0.879
                   OrNotHighHigh      265.37      (9.0%)      263.81     (10.3%)   -0.6% ( -18% -   20%) 0.848
            HighTermTitleBDVSort       15.58      (9.1%)       15.50     (11.6%)   -0.5% ( -19% -   22%) 0.876
                    OrHighNotMed      384.31      (8.9%)      382.57     (10.5%)   -0.5% ( -18% -   20%) 0.883
             And2Terms2StopWords      155.97      (8.1%)      155.41     (10.9%)   -0.4% ( -17% -   20%) 0.906
                 CountOrHighHigh       72.44      (9.2%)       72.19     (10.4%)   -0.3% ( -18% -   21%) 0.911
                   OrHighNotHigh      274.27      (8.9%)      273.45      (9.2%)   -0.3% ( -16% -   19%) 0.916
                CountAndHighHigh       55.45      (5.8%)       55.48      (7.6%)    0.0% ( -12% -   14%) 0.984
                          Fuzzy2       70.44      (8.9%)       70.49     (10.4%)    0.1% ( -17% -   21%) 0.980
                    OrNotHighMed      416.84      (9.9%)      417.32      (9.8%)    0.1% ( -17% -   21%) 0.970
                  CountOrHighMed      136.40      (8.2%)      136.67      (8.2%)    0.2% ( -14% -   17%) 0.939
                          OrMany       18.52      (8.9%)       18.57     (10.7%)    0.3% ( -17% -   21%) 0.928
                      OrHighHigh       68.65      (9.1%)       68.85      (9.9%)    0.3% ( -17% -   21%) 0.922
                          Fuzzy1       74.51      (9.9%)       74.84     (10.8%)    0.4% ( -18% -   23%) 0.895
                    OrNotHighLow      949.97      (9.6%)      955.23      (9.4%)    0.6% ( -16% -   21%) 0.854
                    OrHighNotLow      506.24     (10.7%)      509.09     (10.7%)    0.6% ( -18% -   24%) 0.868
                        Wildcard      107.93      (9.3%)      108.58     (10.3%)    0.6% ( -17% -   22%) 0.847
                       OrHighMed      164.04      (8.8%)      165.21      (9.9%)    0.7% ( -16% -   21%) 0.809
                       And3Terms      171.04      (9.3%)      172.28      (9.7%)    0.7% ( -16% -   21%) 0.811
                         Prefix3      110.72      (7.9%)      111.55     (10.8%)    0.7% ( -16% -   21%) 0.802
                    AndStopWords       31.21      (9.8%)       31.46      (9.1%)    0.8% ( -16% -   21%) 0.788
                     OrStopWords       35.41     (11.6%)       35.72      (9.8%)    0.9% ( -18% -   25%) 0.797
                        Or3Terms      172.95      (9.4%)      174.46      (9.3%)    0.9% ( -16% -   21%) 0.767
                      AndHighLow      968.15      (9.1%)      976.66      (8.9%)    0.9% ( -15% -   20%) 0.758
                 CountAndHighMed      161.43      (6.3%)      162.95      (6.8%)    0.9% ( -11% -   15%) 0.651
                      OrHighRare      264.93      (9.3%)      268.08      (9.1%)    1.2% ( -15% -   21%) 0.682
              Or2Terms2StopWords      159.11      (9.6%)      161.05      (8.9%)    1.2% ( -15% -   21%) 0.677
                     AndHighHigh       53.31      (9.4%)       53.98      (9.7%)    1.3% ( -16% -   22%) 0.678
                      AndHighMed      168.10      (8.9%)      170.24      (9.9%)    1.3% ( -16% -   22%) 0.669
                       OrHighLow      719.77      (9.5%)      729.34      (8.9%)    1.3% ( -15% -   21%) 0.648
               HighTermMonthSort     3003.54      (8.8%)     3046.54      (8.0%)    1.4% ( -14% -   20%) 0.592
                       CountTerm     7707.72     (10.5%)     7843.15     (10.3%)    1.8% ( -17% -   25%) 0.593


"minify" value in awsm.json respected now

Updates deploy_lambda.js to correctly skip minification if minify is set
to false in the awsm.json

+1 This would be really helpful to merge.

Thanks @Kenny-House This is pretty outdated so I'm going to close this.  Regardless, thank you for your work :)


Port example http connector to TableLayout API

Fix https://github.com/facebook/presto/issues/2709

Kindly ping
@haozhun @electrum @martint

Remove all occurrences of ConnectorPartition from presto-example-http

Instead, it looks like ExamplePartition may be removed entirely?

Please ping us again after addressing the comments.

thank you @haozhun get comments addressed

@martint @electrum This PR seems good.

Merged. Thanks!


Boolean fix

The issue
I was using for CodeGen, and I found a very extrange bug, after a bit of digging I found out that every time I used a type: boolean the result out of serde::try_from just included the URL.
My fix
Even though I am new to Rust after fumbling around a bit I found the PropertyInstance and I was like, if String doesn't "depend" on another type why should Boolean.
I changed Boolean(bool) into Boolean and fixed all the Boolean(_) mentions on the code and it finally worked.
Extra
Also I added missing features to the README. And added the ability to use specification when the json schema is an array type.

I just ran clippy and got a bunch of warnings hint hint ;)

The only error I got that is not alredy in master is https://github.com/FlowerAce/serde-json-schema/blob/57a656815c3218b4c1460695b44e565fb91de6db/src/lib.rs#L103 of just copying your code.


Updated documentation for custom image

@eaberman, please update your PR description to say "Closes XXX" (the bug that it addresses).


Pick a certain time

I have a variable with time, lon and lat dimensions.
I can specify longitude (uu = u.where(u.longitude >= 30)), similarly with latitude, but I'm struggling to specify a certain date/time.
Printing the time gives the following output:
>>> print u.time
<xarray.DataArray 'time' (time: 8)>
array(['2018-04-01T00:00:00.000000000', '2018-04-01T06:00:00.000000000',
       '2018-04-01T12:00:00.000000000', '2018-04-01T18:00:00.000000000',
       '2018-04-02T00:00:00.000000000', '2018-04-02T06:00:00.000000000',
       '2018-04-02T12:00:00.000000000', '2018-04-02T18:00:00.000000000'], dtype='datetime64[ns]')
Coordinates:
  * time     (time) datetime64[ns] 2018-04-01 2018-04-01T06:00:00 ...
Attributes:
    long_name:  time

I've tried naming the date by a number like uu = u.where(u.time >= 4) but it gives TypeError: invalid type promotion, and it's not very useful when using a dataset with a huge time dimension.
I'd just like some help figuring out the syntax for specifying days/times.

Hi @ameanijon , for me it's not clear what you mean with "specify longitude" in your post above. The command u.where(u.longitude >= 30) will mask out data, not select (or "pick") them as you write in your title.
Selecting data is called "indexing" in xarray and you'll find examples in the documentation here: http://xarray.pydata.org/en/stable/indexing.html  (also with time)

@fmaussion thank you! Think I got a bit confused


fix for windows, update readme and  fix lint warnning

fix for windows, update readme and  fix lint warnning

The tests for Python 2.6 and 2.7 still fail, I see that open has no encoding parameter http://stackoverflow.com/questions/10971033/backporting-python-3-openencoding-utf-8-to-python-2

Thanks! I merged your pull request and fixed the python 2.6/2.7 support


Implementation AI camera module interface

Implementation AI camera module interface

Video streaming API based on opencv2
Visualization API of camera stream data on jupyter notebook shell

{Pimodi gotta be fun, gotta be cool, and (with smile) gotta be sexy too}

idVendor, idProduct is promised argument name using in pyUSB package in order to find target usb device information.


  Consequently, locks Go language feature support to 1.13 in go.mod, upgrades the operator-sdk from 0.8.1 to 0.9.0 to enable full Go modules support, and fixes the Dockerfile to the Go 1.13 image.
Tested make targets with no apparent issues.
This change requires moving the aws-account-operator project folder from your $GOPATH, export GO111MODULE=on, and downloading the operator-sdk v0.9.0 binary.
Signed-off-by: Christopher Collins<EMAIL_ADDRESS>

/hold

Having some issues with test-awsfederatedrole & test-aws-ou-logic
Not sure if this is related to the change, or some AWS errors, but for completeness, mentioning here.

@2uasimojo:

Please update the operator-sdk reference in the README to the appropriate version.

Done!

Does 0.9.0 still have the same syntax with respect to things like operator-sdk up local? I know at some point they changed it to operator-sdk run --local. If there are discrepancies there, the make targets may need to be updated appropriately.

It appears to still have the same API as earlier versions, at least for the pieces we are using.

Thanks for the updates @clcollins.
I'll note that this commit doesn't really appear to be doing what its title says (the osdk lines weren't touched).
Will continue watching for CI to go green.

@2uasimojo:

I'll note that this commit doesn't really appear to be doing what its title says (the osdk lines weren't touched).

The lines that were changed were the ones documented by the operator-sdk as needing to be added when upgrading to v0.9.0, specifically as a dependency for v0.9.0.
Ie: I'm fixing the "replaces" lines, as documented for v0.9.0.  :)

Ie: I'm fixing the "replaces" lines, as documented for v0.9.0. :)

Ah, thanks for the explanation.
Since this is CI green, and looks mechanically sound, I'm happy with it. I didn't pull it down and test it (not sure I'm going to get a chance) so I'll avoid stamping it officially. But lgtm.

Ok, all make tests are working fine now - issues with my local environment not with the code after the upgrades.

@rogbas @iamkirkbater

/retest

/retest

/retest

LGTM, merge it on Oct 5th
/hold

/lgtm
/approve

/hold cancel


local clone cannot access the api of extension like BingSearch and AI Search

Hi!
I have an issue that the localclone cannot access the api of AI Seach and Bing as "API is not authorized" while other function like chat is working without problem as well as the remote of the clone . I did "AdditionallyAllowedTenant=* in env.local file but nothing change .
Strangely, the setting of extension is synchronized with local's, namely, when I change the setting of the remote is relected to local's immediately.
I wisht to use the functionality of AI Search because I believe Search resource  is necessary for upload the file or  search the previous uploaded file  because I wisht to check the customized function at localclone prior to push to the Remote.
Appreciate if somebody advise how to solve this issue.

The headers are stored in AzureKeyVault and not locally.
If you inspect the header calls being made locally - you will see that the value of all headers are the "******" mask.
You would have to modify this function (in chat-api-dynamic-extension.ts):

Add a check before the return statement, that checks if the h.key is present in your local env file and if so return the value from your env file as "value"


npm vuln. packages

Hi,
I got this quite scary message when installing wg-dashboard:
found 33 high severity vulnerabilities in 2514 scanned packages

I ran npm audit fix which seems to have worked.
Also, consider mentioning that doing the automatic install will end up installing kernel modules and run the software as root. I read the script in advance of running it, and that definitively came as a surprise

found 33 high severity vulnerabilities in 2514 scanned packages

The so called vulnerabilities are coming from a dependency of nunjucks, which has not been updated yet.

Also, consider mentioning that doing the automatic install will end up installing kernel modules and run the software as root.

Yes, installing a kernel level VPN will install kernel modules. Root access is a requirement as seen in the README, it wouldn't be a requirement if we weren't to use it.

nevermind, i fixed it

Thanks, my comment about the root user was more that the web interface runs as root (as opposed to creating a new user to run as and using e.g. capabilities or sudo to configure wiregaurd).


TextFields don't meet minimum accessibility height (48 px) with default style (just 43)

Internal: b/141526836
Minimum a11y height requirements as per Material is 48dp whereas default style gives a height of 43.

b/141526836

this might be caused by the root issue of 41101#

I talked to Hans about this. Will start digging into it in the next day or two.


[Teachable] Unable to find video URL

Checklist

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2021.12.17
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones

Verbose log
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--cookies=../cookies-teachable.txt', '--download-archive', 'archive.txt', '-o', './%(chapter_number)s-%(chapter)s/%(autonumber)03d-%(title)s.%(ext)s', 'https://unf-vault.teachable.com/courses/enrolled/1696460', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.7.3 (CPython) - Linux-4.19.0-16-amd64-x86_64-with-debian-10.9
[debug] exe versions: ffmpeg 4.1.6-1, ffprobe 4.1.6-1
[debug] Proxy map: {}
[generic] 1696460: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 1696460: Downloading webpage
[generic] 1696460: Extracting information
[TeachableCourse] 1696460: Downloading webpage
[download] Downloading playlist: Creating an Interactive Menu in UE5 in the Style of Genshin Impact
[TeachableCourse] playlist Creating an Interactive Menu in UE5 in the Style of Genshin Impact: Collected 82 video ids (downloading 82 of them)
[download] Downloading video 1 of 82
[Teachable] 38493768: Downloading webpage
ERROR: Unable to find video URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python3.7/dist-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/lib/python3.7/dist-packages/youtube_dl/extractor/teachable.py", line 176, in _real_extract
    raise ExtractorError('Unable to find video URL')
youtube_dl.utils.ExtractorError: Unable to find video URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
All courses from https://unf-vault.teachable.com/ are now producing the above error, 2-4 weeks ago these were working just fine. I have updated my cookies file today incase that was a problem.
There are other issues with Teachable reported, but none of them reference a 'Unable to find video URL' error.

@dirkf 38493768_https_-_unf-vault.teachable.com_courses_1696460_lectures_38493768.log
I renamed the .dump as .log due to git's upload restrictions.

I also have the same issue.
Could I be notified when this gets fixed?

https://github.com/ytdl-org/youtube-dl/issues/31133


[4.0] [QoI] Improve contextual error diagnostics related to calls

Description: Currently some contextual errors are discovered too late
which leads to diagnostics of unrelated problems like argument
mismatches, these changes attempt to improve the situation
and try to diagnose contextual errors related to calls
before everything else.

Scope of the issue: diagnostic improvements for contextual errors related to calls.

Risk: Low.

Tested: New test cases added, Swift CI.

Reviewed by: Mark Lacey.

Resolves: SR-5045, rdar://problem/32934129

@swift-ci please test

@rudkx please review for 4.0

@swift-ci please test source compatibility


OC settings not being applied if fan control is used at the same time

Checklist

[X] The problem is not listed in the hardware support matrix as a known limitation
[X] I've included a debug snapshot if the issue is related to hardware configuration

Bug description
When only using the OC functionality, settings are applied as normal:

When fan control is also used, OC settings are suddenly no longer applying (note the memory clock dropping from 1300 to 1218MHz here):

I've talked about this problem already here. TL;DR, I suspect the order in which settings are written is causing the problem.
qlum on that thread doesn't seem to be able to reproduce the problem, but I consistently can, on multiple distros, distro installs, and kernels.
On my hardware, this custom script seems to work:
#!/usr/bin/env bash

CARD_ID=card1
HWMON_ID=hwmon3

PL=280
SCLK_MAX=3200
MCLK_MAX=1300
VOLT_OFF=-75
TEMP_TGT=70

GPU_SYSFS="/sys/class/drm/$CARD_ID/device"
HWMON_SYSFS="$GPU_SYSFS/hwmon/$HWMON_ID"
FANCTRL_SYSFS="$GPU_SYSFS/gpu_od/fan_ctrl"

echo "$((PL * 10**6))" > "$HWMON_SYSFS/power1_cap"

echo "s 1 $SCLK_MAX" > "$GPU_SYSFS/pp_od_clk_voltage"
echo "m 1 $MCLK_MAX" > "$GPU_SYSFS/pp_od_clk_voltage"
echo "vo $VOLT_OFF" > "$GPU_SYSFS/pp_od_clk_voltage"

echo "$TEMP_TGT" > "$FANCTRL_SYSFS/fan_target_temperature"

# commit both `pp_od_clk_voltage` and `fan_target_temperature` _AFTER_ setting everything
echo "c" | tee "$GPU_SYSFS/pp_od_clk_voltage" | tee "$FANCTRL_SYSFS/fan_target_temperature"

(yes I know this isn't an issue with LACT per se, but it'd be great to circumvent the issue now instead of having to wait for an amdgpu fix)
Debug snapshots:
OC only
OC & fan control
System info
- LACT version: 0.4.5-release
- GPU model: Sapphire Nitro+ 7800 XT
- Kernel version: 6.9.6-zen1
- Distribution: NixOS 24.11 unstable

Duplicate of #329, should be fixed in latest master.

I'll go ahead and close this issue then. Thank you!


ChromeCast appData callback for customData

Me again with some ChromeCast inquiries :)
I found this issue: https://github.com/google/shaka-player/issues/722
@joeyparrish mentioned here that "The customData field of the Load message will be given to shaka.util.CastReceiver's opt_appDataCallbackopt."
I imagine something like this.appDataCallback_(mediaInfo.customData) just next to contentIdCallback.
Now i noticed that is not the case, and i figured it would be pretty helpful, since that way my android sender can just use default namespace and not be aware of shaka namespace at all.
Is there a reason this wasn't implemented? Cause if there aren't any blocking reasons, i'd like to contribute and add that or make a feature request.

I went back through the history, and you're right.  There's no point where we ever passed the customData field of the standard LOAD command to the receiver's appDataCallback.
This should be very easy to fix.


Typo in app code sample

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/rest/apps/apps#create-an-installation-access-token-for-an-app
What part(s) of the article would you like to see updated?
Code sample
Additional information
respoitory is a clear typo.  It should at least be repository, but perhaps should be repositories, and the data an array.

As you can see, there's a typo in the word respoitory
I would like to fix this issue

Hi @Paras-Saini 👋 Thanks for your interest in updating this file! Most of our rest documentation has to be updated internally.
Please take a look at the help wanted section of our open source board to find open issues you can work on.
Thank you for your passion and enthusiasm for improving our docs! 💖

Since updates to the REST/GraphQL API description must be made internally. I have copied your issue to an internal issue, so I will close this issue.
Thank you for bringing this to our attention ✨


Docs issue with vmaUnmapPersistentlyMappedMemory

The comment/docs for vmaUnmapPersistentlyMappedMemory() reads;

Unmaps persistently mapped memory of types that is HOST_COHERENT and DEVICE_LOCAL.
This is optional performance optimization. You should call it on Windows for time of call to vkQueueSubmit and vkQueuePresent, for performance reasons, because of the internal behavior of WDDM.

The second half of that isn't particularly clear as to what you should and shouldn't do on Windows.
I'm torn between "don't unmap something between it being used in vkQueueSubmit and the following vkQueuePresent" and "only unmap/unmap persistently between where it is used and the following vkQueuePresent".

OK, maybe I should rephrase it this way:

(...) You should call it on Windows for time of +every+ call to vkQueueSubmit and vkQueuePresent. Example:
vmaUnmapPersistentlyMappedMemory(allocator);
vkQueueSubmit(...)
vmaMapPersistentlyMappedMemory(allocator);

It is as simple as that. No need to think about which resources are actually used. Any ideas how to describe it better?

Ah, I see now.
In which case I think I would phrase it;

(...) On Windows you should call it before every call to vkQueueSubmit and vkQueuePresent. After which you can remap the allocations again using vmaMapPersistentlyMappedMemory()
Example:
vmaUnmapPersistentlyMappedMemory(allocator);
vkQueueSubmit(...)
vmaMapPersistentlyMappedMemory(allocator);

I think that should make the usage clear.

OK, done.


Windows paths in msys32 environment

The Windows instructions at:
https://github.com/espressif/esp-idf/blob/master/docs/en/get-started/add-idf_path-to-profile.rst#windows
Instructs the user to use windows paths in the msys32 environment:

export IDF_PATH="C:/msys32/home/user-name/esp/esp-idf"

This will not work within the msys32 shell, and should probably be same as the linux instructions:

export IDF_PATH=~/esp/esp-idf

Is using a Windows-style path here not working?
We do some "magic" in the Makefiles to convert these paths, so Windows users can use a more familiar path style if they prefer: https://github.com/espressif/esp-idf/blob/master/make/project.mk#L75

Hi @paccerdk , did the above suggestion help you resolve the issue?


getFilterChanges() dies during infrequent polling

Version: 3.11.0
Python: 3.5
OS: linux (debian buster)

What was wrong?
Calling getFilterChanges() at intervals of at least 60 seconds results in it dying and returning nothing but []. Here is a script I produced that will reproduce the bug:
import time
from web3 import Web3, HTTPProvider

# Change this to another RPC node if you prefer.
# I have reproduced it with all mainnet/kovan nodes I've tried
rpc_node = "http://localhost:8545"

myweb3 = Web3(HTTPProvider(endpoint_uri=rpc_node))
block_filter = myweb3.eth.filter('latest')

# Cannot reproduce with 5, 20, 45, 50, 55
# Can reproduce with 60! (If you can't, try bigger intervals?)
interval = 60

print("If after a while you start getting only [], then you have reproduced the bug.")
print("Using time interval: ", interval, "seconds.")

while True:
   print(myweb3.eth.getFilterChanges(block_filter.filter_id))
   time.sleep(interval)

The buggy output looks like this:
$ python debug-invocations3.5.py
If after a while you start getting only [], then you have reproduced the bug.
Using time interval:  60 seconds.
['0x29cab435cace5f0ec52d7caf8b6a7863a202456da778c77e0c2786a68cea55b1']
[]
[]
[]
[]
[]
[]
[]

I have reproduced this bug on two different machines running web3 on python3.5: a laptop and a Digital Ocean VM (both running debian buster), connecting to both a local parity node (versions 1.6.10 and 1.7.0) and to a public RPC node.
Please let me know if you are able to reproduce.
Edit: I've now realised that this is a parity bug.
Final edit: I've now realised that this is a parity feature.

Maybe there is some gevent-related subtlety that I'm not understanding, as discussed here.

I've now realised that this is a parity feature.


fix(console): Chat report UI improvement

fixes #227

Unfortunately I cannot merge this PR. It is not visually appealing. The expectation is that it will look similar to the way we currently present messages.
This is what it currently looks like:

Next time, please include a screenshot in the PR for visual changes, then it would be easier to review and provide feedback.
I'll close this for now.


Get replay web page working in Uwazi display

At least on the Taiwan instance, it doesn't seem to be working at all. And there was always an issue in the past of having to reload to get it to work.
Webrecorder Discord debugging thread: https://discord.com/channels/895426029194207262/1145769876594634792/threads/1240365974255829043

Context: we have built a single-page Svelte app that is loaded as a plugin into Uwazi, a CMS. The main code for the app is here and in nearby files.
A minimal HTML reproduction of the setup does not have any issue. It's some interplay between my code and replayweb.page that is causing it to fail and just display a white block.


errors are resolved

Signed-off-by: gunjanmimo<EMAIL_ADDRESS>

@gunjanmimo given your success with the NSX-SM adapter, you might like to have another look at this PR.


Use an English vocabulary to generate random phrases

Depends on #22.
The /random-phrase endpoint currently generates a random phrase in Latin. Like this:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quamquam te quidem video minime esse deterritum. Hic nihil fuit, quod quaereremus. Facile est hoc cernere in primis puerorum aetatulis. Quo modo autem philosophus loquitur? Id enim natura desiderat. Duo Reges: constructio interrete.

This is too long for our screen. I think that on the screen of the demo app perhaps max 3 words can fit — more will go over the screen size. And it is also not funny — a dull Lorem Ipsum text everyone has seen hundreds of times.
Can we generate something ourselves?
For example, we could have a list of adjectives:

funny
green
hard
nerdy
wild
…

and a list of nouns:

programming
Python
clouds
code
…

and then create phrases from these like:

green clouds
nerdy kangaroo
furry Python

whatever. Any other ideas are welcome.
When done, I also suggest to write a unit test to cover this function. This unit test might check that the output string contains two words separated by a space, for example.

It,s realy funny & very good idea!!! In work:)


Support deprecated on fields in the OpenAPI conversion

Background
It seems that the OpenAPI transformation doesn't set deprecated: true for members that are annotated as @deprecated(...).
Started by just adding a failing test to check that it makes sense. If this is something that is not expected I will proceed to try a fix.

Might need a bit of guidance on this one. At 66b34621044a2d56d6b4e31890ed7a27546129e5 I'm setting the deprecated field for json schema for what I think are member fields. This seems to break cloudformation tests in CfnSchemasTest, how can this be separated?

"deprecated" was added in Draft 2019-09 (formerly Draft 8) and Smithy supports Draft 7 and Draft 2020-12. This means the behavior you've added needs to be controlled by the JsonSchemaVersion.
CloudFormation uses Draft 7, so those tests should pass when this field is not being added for that JSON Schema version.

@kstich thanks, I made some changes, including only setting it when the json schema version != DRAFT07, which I assume will work meaning set it if version is "greater" than DRAFT07.


Updating quickstart documentaton URL patterns example with re_path

Small update to the quickstart documentation regarding url patterns: changing url to re_path.
Reason

Since Django 2.0, the url() function is an alias to django.urls.re_path()
url() is deprecated since Django 3.1

Thanks for this!


Setup official GitHub Dependabot

Setup official GitHub Dependabot.
https://docs.github.com/en/github/administering-a-repository/about-github-dependabot-version-updates

GitHub Dependabot takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on.

This change is

Thanks for the review, @platosha!
I also have this other related PR: https://github.com/vaadin/vaadin-router/pull/450

Thanks for merge this PR @haijian-vaadin!
Could you also check #450? Otherwise, many PRs will be created about dependencies.


🚀 Restore Essential Functionalities - Book Search, Google Book Viewer, Google Login 🔧📚

Related Issue
Closes #1104
Description
his PR aims to address the unintentional removal of crucial functionalities during the recent migration to Next.js. I will promptly restore the Book Search, Google Book Viewer, and Google Login features to ensure a seamless user experience and improve user engagement. 🌟💻
Your feedback and review on this PR are highly appreciated as we work together to enhance the website's functionality and retain our valued users. 🙏
Screenshots
Checklist

[x] My code adheres to the established style guidelines of the project.
[] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

@Nishitbaria you can focus on developing the Book Search and Google Book Viewer functionalities. However, please refrain from working on the Google login feature as I am currently utilizing Next Auth for authentication purposes.

@rohansx @crocmons  please  update the environment variables in vercel this is sample.env use your own keys:
MONGODB=mongodb+srv://Jazzy49:MyNodeApp@nodeprojects.tsxlcqi.mongodb.net/Informaticon?retryWrites=true&w=majority
PORT=5000
GOOGLE_API_KEY=AIzaSyB3sYLJcjF78HW8zc10yTkW2dHM-uLRtOs

please review and merge my pull request

@Nishitbaria you can focus on developing the Book Search and Google Book Viewer functionalities. However, please refrain from working on the Google login feature as I am currently utilizing Next Auth for authentication purposes.

Already Done please once

Also, kindly check out the #1104 issues comment!

thanks, Also, kindly check out the https://github.com/rohansx/informatician/issues/1104 @rohansx  comment!

@crocmons How I can integrate other Book Viewer other than Google Book's as the books are coming from Google Books API only , integrating other Book's viewer is possible when we have file in pdf or other format but he we have not
So Understand and Please Review and Merge the PR because I have configured all functionality again for NextJs with Dynamic Routes
Since  I can Comment on Issue because its Locked for commenting

@crocmons How I can integrate other Book Viewer other than Google Book's as the books are coming from Google Books API only , integrating other Book's viewer is possible when we have file in pdf or other format but here we have not
So Understand and Please Review and Merge the PR because I have configured all functionality again for NextJs including Dynamic Routes
Since I cant Comment on Issue because its Locked for commenting

@rohansx

@rohansx ,please review and merge my pull request

@rohansx ,please review and merge my pull request

resolve the conflict.. #1087

@rohansx @crocmons  please merge this pull request asap so i can work on other issues

@rohansx ,please review and merge my pull request

resolve the conflict..Also check out this issue #1087

I have seen that


Bounds on aeson and tls loosened to accommodate the latest versions

Looks good for the latest version of aeson and tls, building fine.
The bounds for version 0.3.1 can be edited directly on Hackage.

Will merge and upload when I have a minute later today. Thanks.

http://hackage.haskell.org/package/network-api-support-0.3.2

Thanks @cdornan

Cheers


Node not displayed ImageConcatMulti

how to install the node?

This node is in https://github.com/kijai/ComfyUI-KJNodes
But you can remove it from this workflow. It is used only to create side-by-side video with original.

This node is in https://github.com/kijai/ComfyUI-KJNodes
But you can remove it from this workflow. It is used only to create side-by-side video with original.

Thanks!

Yes it's relatively new node in KJNodes, so updating that pack should fix it. It's also not necessary at all like mentioned, safe to delete and just use single image output.

Yes it's relatively new node in KJNodes, so updating that pack should fix it. It's also not necessary at all like mentioned, safe to delete and just use single image output.

Thanks!


BED-4598: added group entities to open api spec

Description
Added endpoint definitions for group entity endpoints to the open api spec
Motivation and Context
This PR addresses: BED-4141 / BED-4598
Types of changes

Chore (a change that does not modify the application functionality)

Checklist:

[x] I have met the contributing prerequisites

Assigned myself to this PR
Added the appropriate labels
Associated an issue: https://github.com/SpecterOps/BloodHound/issues/672
Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing

[x] I have ensured that related documentation is up-to-date

Open API docs
Code comments (GoDocs / JSDocs)

[x] I have followed proper test practices

Added/updated tests to cover my changes
All new and existing tests passed

I also added a README with some helpful information about paths, and removed a couple duplicate files


Fix "Rubocop/Metrics/AbcSize" issue in app/models/user.rb

Assignment Branch Condition size for unenrolled is too high. [21.1/15]
https://codeclimate.com/github/coder2000/lms/app/models/user.rb#issue_59f10d4d3e33a600010000a7

Not fixable
Query is too complex to simplify


change: Ignore qubit_count parameter for JAQCD

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

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

@speller26 I think you should go ahead and merge this, especially if it unblocks your work on https://github.com/amazon-braket/amazon-braket-default-simulator-python/pull/264


Rework description of --config local tests

The previous description of putting --config local tests into /sites/ and /integration/ does not reflect the reality of current Parsl development. cc @khk-globus who has put some thought into test organisation, but for now remove that advice.
Type of change

Update to human readable text: Documentation/error messages/comments

parsl/tests/sites/ is "just another directory" of tests, including tests that are nothing to do with tests.
No one runs any site-specific tests ever - that cough principle is one of the drivers for moving to weekly auto-releases with explicitly accepting there is no human testing. See the work leading up to PR #2612 which made the first autorelease after no release at all for more than a year.


How can we get detailed explanation of obvervation variables?

Hi~ Thanks for your great work.
I am playing with the locomotion soccer environment. But I have no idea about the meaning of some observation variables:
They look like the following:
        "team_goal_back_right",  # (1, 2)		[[20.39657422 -5.54516916]]
        "team_goal_mid",  # (1, 3)		[[ 11.73723908 -10.76243655   1.67126411]]
        "team_goal_front_left",  # (1, 2)		[[  3.07790393 -15.97970393]]
        "field_front_left",  # (1, 2)		[[-56.03425312  20.39720981]]
        "opponent_goal_back_left",  # (1, 2)		[[-49.91189073  34.54660858]]
        "opponent_goal_mid",  # (1, 3)		[[-41.25255558  39.76387596   1.67126411]]
        "opponent_goal_front_right",  # (1, 2)		[[-32.59322043  44.98114335]]
        "field_back_right",  # (1, 2)		[[26.51893661  8.6042296 ]]

Where could we find a detailed meaning of these variables?
Thanks!

Specifically, although we could find the definition in observable
But like the function at Line187, the meaning of each variable is still not clear...
https://github.com/deepmind/dm_control/blob/master/dm_control/locomotion/soccer/observables.py#L187

These observables generate values using the lambdas defined here. As you can see, these correspond to attributes of the goal posts, which are all subclasses of PositionDetector, defined here. From a quick glance, looks like they correspond to the Cartesian coordinates of the goal post's legs and center point.

These observables generate values using the lambdas defined here. As you can see, these correspond to attributes of the goal posts, which are all subclasses of PositionDetector, defined here. From a quick glance, looks like they correspond to the Cartesian coordinates of the goal post's legs and center point.

Thanks for your explanation.
I understand the variables regarding the goal. But how about the
"end_effectors_pos",  # (1, 3)		[[0. 0. 0.]]
 "joints_pos",  # (1, 1)		[[-0.00367045]]
 "joints_vel",  # (1, 1)		[[0.03756077]]

So seems like there is no such kind of information for specific explanation of the variable :(

@Frank-Dz Those are common across not just the soccer tasks but the walker agents in the locomotion module. Specifically, you can check the CMU humanoid class described here for more information.
joints_pos and joints_vel are the respective positions and velocities of the joints of the humanoid agent. end_effectors_pos refers to the position of the end effectors of the humanoid agent relative to its torso, in the egocentric frame. The end effectors are defined here and they're basically the right/left hands/feet.

@Frank-Dz Those are common across not just the soccer tasks but the walker agents in the locomotion module. Specifically, you can check the CMU humanoid class described here for more information.
joints_pos and joints_vel are the respective positions and velocities of the joints of the humanoid agent. end_effectors_pos refers to the position of the end effectors of the humanoid agent relative to its torso, in the egocentric frame. The end effectors are defined here and they're basically the right/left hands/feet.
The above might differ for different soccer agents, so you'll have to check.

Thank you so much!
I think I get the idea!
Btw, I have the last question. For a soccer environment, we could use random_state to specify the seed for the random state of the initial state. But what if we want the two teams always start from a specific formation? Like:

The red and blue teams are always facing to each other in at the start of the match... huh

@Frank-Dz Those are common across not just the soccer tasks but the walker agents in the locomotion module. Specifically, you can check the CMU humanoid class described here for more information.
joints_pos and joints_vel are the respective positions and velocities of the joints of the humanoid agent. end_effectors_pos refers to the position of the end effectors of the humanoid agent relative to its torso, in the egocentric frame. The end effectors are defined here and they're basically the right/left hands/feet.
The above might differ for different soccer agents, so you'll have to check.

but why the shapes of joint_pos and joint_vel are (1,1)? There is only one element, it should be 3 elements (xyz)?


Declare an eyeglass version. Fixes #152

https://github.com/at-import/breakpoint/issues/152

Please commit!
The following modules did not declare an eyeglass version:
  breakpoint
Please add the following to the module's package.json:
  "eyeglass": { "needs": "^0.8.1" }

Please can you merge this! And also on Singularity.gs, which has same issue.

Updates coming in next two weeks.

On Feb 12, 2016, at 3:55 AM, Phil Wareham<EMAIL_ADDRESS>wrote:
Please can you merge this! And also on Singularity.gs, which has same issue.
—
Reply to this email directly or view it on GitHub.

Great news, thanks!


Init schemas

What
Creating a utility to read and write from and using avro schemas.
closes https://github.com/LibertyDSNP/frequency/issues/1144

I find the read/write terminology a little bit confusing. Normally I consider a read operation to consume data from some source (optionally mutating the state of the read source, like current pointer, etc), and a write operation to send data to some data sink. In the read/write methods here, for read we're given a (non-mutable) data buffer to be transformed by decrypting/decompressing/deserializing, and for write we're given an object to serialize/compress/encrypt, resulting in a new object/buffer, but not mutating any external source/sink.
Perhaps serialize/deserialize is more appropriate terminology? Or am I not understanding what's happening?


Remove unnecessary query params for getThreads node method

We missed to remove an unnecessary query parameter for getThreads method under @liveblocks/node. Note that the presence of this query parameter doesn't affect the API response because the backend endpoint doesn't look at the query parameter. But, it is still a good idea to remove this query parameter from the method to remove any confusion.

Good catch 🙌


test: filedef simplify test

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

Project coverage is 100.00%. Comparing base (fe8fd6c) to head (beb9a78).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #387   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         3684      3684
=========================================
  Hits          3684      3684

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


Add initial minimal impersonation proxy.

Adds an initial minimal implementation of an impersonation proxy, which will be an alternative backend for the concierge. It will (once finished) add support for most managed Kubernetes cluster environments.
Fixes #355
Release note:
No release note yet because this functionality isn't really exposed in a usable way (it's listening on a port, but you can only use it with a large amount of manual setup).
NONE

Codecov Report

Merging #355 (e4c49c3) into main (cf73571) will decrease coverage by 0.22%.
The diff coverage is 72.07%.

@@            Coverage Diff             @@
##             main     #355      +/-   ##
==========================================
- Coverage   77.43%   77.20%   -0.23%
==========================================
  Files         110      113       +3
  Lines        5574     5792     +218
==========================================
+ Hits         4316     4472     +156
- Misses       1089     1145      +56
- Partials      169      175       +6

Impacted Files
Coverage Δ

internal/concierge/server/server.go
32.22% <0.00%> (-10.12%)
:arrow_down:

cmd/pinniped/cmd/login_static.go
92.06% <71.42%> (-2.68%)
:arrow_down:

cmd/pinniped/cmd/login_oidc.go
86.41% <82.60%> (-1.62%)
:arrow_down:

internal/concierge/impersonator/impersonator.go
90.54% <90.54%> (ø)

cmd/pinniped/cmd/kubeconfig.go
92.20% <92.00%> (-0.11%)
:arrow_down:

internal/clusterhost/clusterhost.go
100.00% <100.00%> (ø)

internal/concierge/impersonator/config.go
100.00% <100.00%> (ø)

cmd/local-user-authenticator/main.go
56.58% <0.00%> (ø)

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cf73571...e4c49c3. Read the comment docs.


Lazy and Eager Loading

Please can you provide an update on current status of lazy and eager loading of navigation properties in EF7. Or point me to some documentation of existing or future implementation. I have tried googling on Bing and ReadTheDocs but to no avail. Thank you.

Eager loading is implemented (using the Include/ThenInclude extension methods).
Lazy loading is not yet implemented. Lazy loading is a common request but is also the number 1 source of performance issues we see and folks are often not aware that they are using it. Based on this we are going to see how we go without it... but will add it if feedback shows that folks really need it.

Yep, lazy loading can get quite contentious in my experience. Thanks, Rowan, for the swift response :)

https://github.com/aspnet/EntityFramework/issues/3176
Are there any method to make a lift include?

+1 for lazy load

+100 for lazy load, that's just ridiculous without it.


Python quickstart using SDK

Purpose
This is a new sample that contains SDK-based code for use in the Face Quickstart for Python (rather than the REST API as in the current Quickstart)
Does this introduce a breaking change?
[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes - for Quickstart article
[ ] Other... Please describe:

How to Test

Get the code
Edit ina valid subscription key and make sure the endpoint region is correct
python face_quickstart.py
Script should find one face in the sample file and output this report:

Face 1
    ID: b6d3a0d5-3a9a-4c23-9ea0-23840c593f3c
    Rectangle: (459, 124) to (686, 351); height: 227 width: 227
    Landmarks: None
    Attributes None

The image should also appear in an image viewer window with a red rectangle around the detected face.

Closing the request. We will resubmit with the updated python structure + location


feat(release): Update SDK to use API released on 2023-11-07

:tada: This PR is included in version 0.20.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allow to reference Input via Autocomplete

I have a use case where I've to call the focus() method of the Input component from Autocomplete. And I think others can have to same.
To be able to do it, Autocomplete should be referenceable in the themr wrapper.

Makes sense! Thanks :)


mfrc522 - Fix 4-byte tag UIDs

4-byte UIDs incorrectly included a 5th csum byte. 7-byte UIDs were unaffected.
fixes #21

Codecov Report

Merging #22 (7512d19) into main (47f3fec) will decrease coverage by 0.3%.
The diff coverage is 0.0%.

:exclamation: Current head 7512d19 differs from pull request most recent head 1de13d5. Consider uploading reports for the commit 1de13d5 to get more accurate results

@@           Coverage Diff           @@
##            main     #22     +/-   ##
=======================================
- Coverage   60.4%   60.1%   -0.3%
=======================================
  Files         48      48
  Lines       6442    6454     +12
=======================================
- Hits        3893    3882     -11
- Misses      2414    2436     +22
- Partials     135     136      +1

Impacted Files
Coverage Δ

mfrc522/mfrc522.go
0.6% <0.0%> (-<0.1%)
:arrow_down:

hx711/hx711.go
69.4% <0.0%> (-5.6%)
:arrow_down:

mcp9808/mcp9808.go
98.8% <0.0%> (-1.2%)
:arrow_down:

lepton/lepton.go
86.2% <0.0%> (-1.0%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 47f3fec...1de13d5. Read the comment docs.

Sorry about the force push, it turns out accidentally transposing two characters in my last commit message makes it massively inappropriate. 😳

No worry about the force push, I squash anyway.


Create Git Tags for releases

Release points or special versions should be tagged in the Git repository of the UI.
ACs

Version number should be set in package.json
We are using SemVer
Major and Minor version of the UI should be align to Marathon
Release point must have the versioned Git tag in the UI repository
Git tag must have a CHANGELOG

Should we create a tag called 0.9.0 based on the current master to freeze a point that is shipped with the next release of Marathon?
What do think? @aquamatthias @philipnrmn @pierlo-upitup

Please do so. If I understood correctly this tag should be used in the releasing-0.9 branch?

OK, cool, yes you understood correctly.

https://github.com/mesosphere/marathon-ui/releases/tag/v0.9.0

Hey @aldipower can you set that in the release branch?

Oh yes, I see.


Add "Seed:#" Argument to Createworld Command

^ Please? :D

Added to the latest developmental builds

Why wasn't this marked as a dupe of #1412?

Forgot. I'm going to go ahead and close both since it's in the developmental builds


uv add resolution failure error includes current project version

$ uv add 'httpx>9999'
error: Because only httpx<=9999 is available and example==0.1.0 depends on httpx>9999, we can conclude that example==0.1.0 cannot be used.
And because only example==0.1.0 is available and you require example, we can conclude that the requirements are unsatisfiable.

It's really weird to include the following:

only example==0.1.0 is available and you require example

Should it even say "you require example"?

Definitely not, that's part of the problem.

Even if example is a workspace member, but not the root...?

I'm not sure. We should probably have a special-case for workspace members though 😭

Solved in #6092


Wrapper cookbook fixes

This solves issue #89 and adds a unit test for same. Essentially I removed any mention of the cookbook source from the custom job resource so that the attribute-set value in the original template definition won't be pointlessly overwritten.
I also applied all the cookstyle recommended fixes.

Travis is failing for reasons I don't understand (kitchen is complaining about a missing cookbook dependency on apt that is clearly there in metadata.rb, plus my local kitchen-vagrant worked). I'm going to keep digging at this, but I'd appreciate a heads up from @elijah or similar saying that I should continue working on getting this PR to pass hound AND travis vs resetting it to just the original unit test and custom resource changes.

Do your best, but... i am not sure Travis is particularly reliable of late.
--elijah
On Feb 26, 2018 10:45 AM, "lamont"<EMAIL_ADDRESS>wrote:

Travis is failing for reasons I don't understand (kitchen is complaining
about a missing cookbook dependency on apt that is clearly there in
metadata.rb, plus my local kitchen-vagrant worked). I'm going to keep
digging at this, but I'd appreciate a heads up from @elijah
https://github.com/elijah or similar saying that I should continue
working on getting this PR to pass hound AND travis vs resetting it to just
the original unit test and custom resource changes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elijah/chef-prometheus/pull/91#issuecomment-368605308,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACok5yKq9rSXt_eFFteKquRYyK5pqumks5tYvuvgaJpZM4SSupy
.

Boom, travis fixed! I just updated the Gemfile to some latest stuff. I also got a good pointer from Dan Webb on the community chef slack and will open a new PR to use the latest, blessed version of https://github.com/chef-cookbooks/aws/blob/master/.travis.yml which lets us do kitchen via dokken.
Assuming you're happy with this PR (so green!) please merge and version as you see appropriate.

Sorry to bother, but I'd like to get a ruling on this PR and merge it if you agree it fixes the issue. It does solve the unit test I added at least, and I got kitchen working again. @elijah are you the party I should ask?

Merged. ;-)


Fix for ReadTheDocs dependencies

The issue:

we have the docs deps under PDM dev deps; this is not accessible via readthedocs extra requirements install
Instead, moving the docs deps to "optional dependencies" in pyproject.toml; was able to use pip install .[docs] locally and get furo theme in my environment :+1:
Did switch the name of the docs deps from doc -> docs

NOTE: CI now will test the build of the docs on PRs!


Support for rp2350

Groundwork for support for the Raspberry Pi RP2350 micro controller

Modification of the existing RP2040 hal to include the 2350
Addition of the RP2350 families into the UF2 tool
Addition of the ARM Cortex-m33 into CPU's
Extracted bootroom form Pico-SDK (following pattern from the RP2040)
Extracted SVD from Pico-SDK (patched to more closely resemble the RP2040 to simplify differences in the HAL)

@timsavage closing as I took this initial work + added to it for my PR here:
https://github.com/ZigEmbeddedGroup/microzig/pull/244
Thank you for getting the ball rolling on this!

Awesome, time to give this a try.


Not overridden options

Hello!
The problem arose from the fact that I override options, and the output is a file with the default settings.
http://joxi.ru/Dr8nq07H8EeG26 - css file
http://joxi.ru/E2pkaRxIN1l4mY - gulpfile
http://joxi.ru/xAee4zWTEB9BAy - output file
I expect the file to shrink, only formatted. And he shrinks and classes are grouped. I can not understand what the problem is.

I'd suggest opening an issue with clean-css if you're experiencing issues with tweaking the options. Whatever you specify is passed through to the library.


[MERGE]: release to master

[MERGE]: release to master
Description
Merge release to master
Proposed changes

Changes should be logged in CHANGELOG.md file from release branch

Related issue

N/A
Notify
Repository owner: @marcoandre1
Thank you! 🙌

Oh crap! 😞

🥳 🥳 🥳 🥳 🥳 🥳 🥳 🥳


Warning: Cannot load LoopBack app server/server.js Use --force to continue.

Firstly, thanks a million for this fantastic app!!!
I have it working but some dependencies were not met at first grunt.
Doing a PR with modified package file.
(for future readers who might bumb into an Error: listen EADDRINUSE after a successful grunt, try the following to kill running npm tasks you might have launched by trying stuff:
ps aux | grep node
Find the process ID (second from the left)
kill -9 PRCOCESS_ID

This happens everytime I run the project with grunt serve. Btw, thanks for this incredibly project !

@jgauna I'm glad it is working for you.
There should be no need for downgrading to node version 0.10 though. I've been working on this project with the latest io.js, version 3.0.0 and everything seems to be working well.
I'm using n to use different node versions, it has support for iojs too:  https://www.npmjs.com/package/n


Document the dependency on OSX CoreAudio

This doesn't even compile under Linux or Windows. The README doesn't even mention the dependency.

Thanks for the report, but I believe the readme does mention the dependency?
"Note: Due to current limitations in the emu project on which this depends, this will only build on OS X. Other platforms will be supported promptly."
It's the second paragraph under the "Description" section.

The dependency has been made a dev-dependency for now in https://github.com/emu-rs/snes-apu/commit/92e73bf990a4bacf99fdfec4011f43895aba43f6, as the audio driver abstractions were only actually necessary to build the example. The rest of the code should build on other platforms just fine.
I'll update the text in the readme to reflect that the example currently only supports OS X, and close this.


Have the pyrsia docker images tagged with semantic version number

By default, we would create a tag based on schematic version number.  Then we can also tag with latest and stable.
Latest = nightly main branch build
Stable = stable branch, tag, or release

This is same as #930 and #905? @sbtaylor15


vpu: mount myd_ion device for topology hints to work

Previously, /dev/ion device was just arbitrary string and the plugin
did not need the device for anything. After adding the checks for
topology hints, the device node must be bind mounted in the plugin
container.
Signed-off-by: Alek Du<EMAIL_ADDRESS>

Duplicate of #312

@bart0sh this was for the release branch

ah, ok. reopening then.

Force update to trigger CI run again :-(


New Artifactory app

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/614/
Test PASSed.


Self-Signed Certs now dead, so is this and all other self-signed cert how-tos

Now that Azure has killed using self-signed certs, how do we do this without paying out the nose for an external CA cert? LetsEncrypt doesn't seem to allow separate user certs, which is the secure method of configuring P2S VPN user certs.?.

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

ID: 63df9645-af2c-3cfc-8f65-413912d88efe
Version Independent ID: d2edf564-2c83-f1da-dbf0-dbc41c4948bf
Content: Generate and export certificates for Point-to-Site: PowerShell: Azure
Content Source: articles/vpn-gateway/vpn-gateway-certificates-point-to-site.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@rphensley Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@rphensley - self-signed certs are not dead. The only thing that has changed is Azure is now using a CA to issue its own Azure-level certificates for the gateway. For P2S authentication from your clients, you can still use self-signed certs and there is no plan to remove that capability.

#please-close

@rphensley We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Power isn't being store or moved

Not sure if I am just doing this wrong or if there is some sort of bug. I originally set up a creative ender io capacitor and an alloy smelter to try and transfer power over. I ended up occassionally getting a small amount of power to transfer over but randomly clicking the options, but nothing would ever continually transfer power. I then hooked up a coal generator to the same Flux Plug as the capacitor. It seems the plug is taking the energy (the generator isn't filling up its buffer past 30), but the energy isn't actually going anywhere.

After a little more testing, it seems to have been an issue with the capacitors from ender io, creative or otherwise.

Okay, I may have to look at adding specific support for Ender IO. Try placing a Flux Controller and changing the Transfer Mode

I think I just figured it out. It is transferring the energy into the capacitors in my inventory, which is taking priority over everything. You can directly hook them into a capacitor and things transfer just fine, however if a creative capacitor is in your inventory, all transferring will stop.

Normal capacitors in the inventory work just fine, however. So not a huge deal, as people shouldn't really have creative capacitors in their inventory, however, it might happen with other items.. so might be worth looking at.

Ahh, so the issue is transferring into a creative bank infinitely, probably as their max capacity will be -1. Thanks for reporting :) Keep throwing my issues, they'll be quite a few as the mod is still brand new.

Will do! I'll be adding it to my personal server with the next round of updates so it'll be getting some play time. This mod fills a void on there, so it'll be perfect.

You got EnderIO ones to work awk? I'm not having any luck and I have no creative caps in my inventory. I made sure transfer mode was turned off too. :(
Plug attachs to the cap [tried basic, vibrant] but it will not send power. I tried single caps and multiblock caps, same deal, no power.
I did find a workaround but it's an odd one. If I use a Mekanism universal cable on the capacitator bank and put the flux plug ON the wire instead of the bank, works fine.  Note I have to manually set the Mek cable to pull mode but that's minor. Oddly trying the same workaround using EnderIO conduits does not work.
I'm wondering if it is having some sort of issue converting power somewhere. It's RF across the network but the only real diff between Mek and Ender cables is that Mek will convert RF/Tesla/EU automatically. Still odd since this mod only supports RF. :)

Interesting addition to my other item I logged... the above workaround works on the Mekanism Induction Matrix too. Place Mek universal cable then place plug on it.

Addendum - the workaround only works for putting power into the induction matrix, will not pull power out :(

Hmm, yeah I had no problem once I fiddled around a bit. Haven't played mine craft much since then. I'll have to hop back on at some point and make sure everything is still working on my end.

Transfer should be fixed in the next update.

Sweet! Thank you for the update. :)

On Aug 3, 2016, at 12:33 PM, Ollie Lansdell<EMAIL_ADDRESS>wrote:
Transfer should be fixed in the next update.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi here,
I think i will report the same bug as described above.
In case of this specific case helps ;p
I tested in creative with a superflat world.
I am using minecraft 1.10.2 with mods :

Calculator-1.9.4-3.1.0 + SonarCore-1.9.4-3.1.1 + Flux-Networks-1.9.4-1.0.3
EnderCore-1.10.2-<IP_ADDRESS>-beta + EnderIO-1.10.2-<IP_ADDRESS>_beta
industrialcraft-2-2.6.40-ex110

Send :
IC2::Generator -> Calculator::AdvancedPowerCube :ok:
EnderIO::StirlingGenerator ->Calculator::AdvancedPowerCube :ok:
Calculator::AdvancedPowerCube -> FluxPlug :ok:
Receive :
FluxPoint -> Calculator::AdvancedPowerCube :ok:
FluxPoint -> EnderIO::CapacitorBank :red_circle:
All are on the same flux network.
Hoppe this helps.

Fixed in dev

This will require a SonarCore update not a Flux Networks one


Update the max ocp version available in openshift-ci

Signed-off-by: Melvin Hillsman<EMAIL_ADDRESS>

/lgtm


Database file is updated via the Internet

Hi guys!
Is there a way to download a database file from the Internet resource and then open it with your library?
If I just replace DB file (Context.getDatabasePath(String name)) with newly downloaded can I somehow re-init library?

Hi yes, you should make sure the database file is fully downloaded before accessing it. (Creating the DatabaseSource). If you intend to try to replace it you have to make sure the DatabaseSource is closed and you have no outstanding references to anything accessing it (queries/cursors etc).


Update azure-openai-chat.adoc

In v0.8.1, the property spring.ai.azure.openai.chat.options.model does not exist anymore. I have tried with spring.ai.azure.openai.chat.options.deployment-name and am able to connect to the Azure Open AI service.
Considering spring.ai.azure.openai.chat.options.deployment-name is the correct property name, I have updated the document to reflect this.
I have also removed this statement "In a subsequent release, Spring AI will rename the property spring.ai.azure.openai.chat.options.model to spring.ai.azure.openai.chat.options.deployment-name to avoid confusion." as this has already been renamed. I have added an appropriate note related to this.
@pivotal-cla This is an Obvious Fix.

Yeh we did this change in https://github.com/spring-projects/spring-ai/commit/1e98f82e03529506c9afaa650717b3819633d573 and I'm surprised we've missed to update the doc.
Thanks for catching it.


merge from konsum-frontend-svelte

package.json

chore(deps): add ^2.9.10 remove ^2.9.9 (devDependencies.vite)

.github/workflows/codeql_analysis.yml

chore: add 16.15.1 (jobs.analyze.steps.with.node-version)

.github/workflows/browser_ci.yml

chore: add 16.15.1 (jobs.release.steps.with.node-version)

:tada: This PR is included in version 1.31.18 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.31.18
GitHub release

Your semantic-release bot :package::rocket:


Screen flickers on page down in vim

Whenever I use <C-d> or <C-f> in vim while scrolling through a large file the screen flickers - it looks like for a moment the screen goes black and then the new content is redrawn, but it takes enough time to be noticeable and annoying. What's perhaps more interesting is that when I scroll half of the page via <C-d> only the bottom part of the window flickers, while top one does not. This issue is observed both inside and outside of tmux. Other terminal emulators don't have this issue.

My alacritty is built with cargo from sources, repo at commit d5ab4183c69e37e8d309acf7b38c2071106bceb7.
OS: Arch linux with kernel 4.10.13-1-ARCH
Graphics:

drivers: intel (unloaded: modesetting)
GLX Renderer: Mesa DRI Intel Ivybridge Mobile
GLX Version: 3.0 Mesa 17.1.0

I have also reproduced it on a different machine, with nvidia's GPU, alas low in terms of performance:

The same repository commit (d5ab4183c69e37e8d309acf7b38c2071106bceb7)
OS: Arch linux kernel 4.11.2-1-ARCH
Graphics:

driver: nvidia
GLX Renderer: Quadro 600/PCIe/SSE2
GLX Version: 4.5.0 NVIDIA 381.22
Direct Rendering: Yes

Do you have any idea what could be a problem here? This issue prevents me from using alacritty on a daily basis, because said flashing constantly distracts me.
This problem is also mentioned in #555

I've experienced this as well. This bug turns out to be an interesting problem! To see why we get the flickering and why it's difficult to resolve, consider how the read/parse/draw loop works:

Some data arrives from the pty. The I/O thread reads this into a buffer.
I/O thread locks the terminal state struct and runs that buffer through the parser.
I/O thread registers that terminal is dirty and requests a draw.
I/O thread releases lock on terminal state, blocks for another read.
The render thread acquires lock, draws frame, and calls swap buffers.

The call at the end to swap buffers will block for ~17ms, and another frame cannot be drawn until it returns. The flickering happens because:

Just enough data is read to cause the terminal to scroll
frame is drawn
more data arrives to fill in scrolled area, but it cannot be drawn until next frame

To me, this seems like a problem with terminal protocol. There's no framing, so we cannot know whether more data is coming or not.
Since we can't fix terminal protocol, we're left with doing something heuristical like trying to read with a short timeout. The trick with such a heuristic is providing sufficient time for related data to arrive without ever causing a frame skip.
If you or anyone else has other ideas on how to address this, or even ideas about how such a heuristic could work, I'm all ears. I've been thinking about this problem for a while and haven't come up with a solution I love.

@jwilm thanks for the in-depth explanation!
@fuine I'm using this plugin, and not experienced the flicker with it, might want to check it out: https://github.com/yuttie/comfortable-motion.vim. It's also pretty cool to use.

@jwilm thanks for the explanation, I will think about that problem. @asilvadesigns I've tried that plugin before but I don't like the CPU overhead that it brings to the table

There is also ongoing work in neovim to improve the terminal gui. For example:
https://github.com/neovim/neovim/pull/6816
When using alacritty in neovim I notice a lot more cursor flickering than with other terminals. However, I think this is a problem with vim/neovim because there as been quite a few pull requests that tries to clean up the terminal ui code so that the cursor doesn't jump around so much when drawing updates.
Speaking of which, @jwilm could there perhaps be a debug mode in alacritty where you can step though the screen updates? That is, you can freeze the screen and then step through the cell updates. I think it would be really helpful when debugging flickering issues in neovim (so you can see what neovim does when it redraws the cursor position for example).

If your program operates as described, which I am taking on trust and have not looked at your program to check, then this does have its roots in your program.
Programs like vim and nvim collect screen output into in-memory buffers and flush it at certain points.  (This is their own buffering system.  Of course, full-screen programs that use standard I/O buffering instead, still do the same thing.)  This results (as one can see from tools like truss, dtrace, and strace) in all output for things like scrolling operations or full screen redraws being sent often in one giant write() system call, often several KiB in one big lump.
Your best strategy in receiving this is to attempt to read and process all of that lump in one go before letting your renderer lock the terminal state for a vertical blanking interval.  It is a falsehood to say that there's no way of doing this.  There are three different approaches, each with their own tradeoffs:

For programs based upon kevent(), the EVFILT_READ events contains the number of bytes available to read in the data field of the event structure.  It also signals EOF separately from this.
Making the pseudo-terminal master use non-blocking I/O tells read() to return if there are no more data.  This somewhat complicates hangup processing as a side-effect, as read() returning zero bytes can mean either temporarily no more data or pseudo-terminal EOF.
There is a FIONREAD generic ioctl() available (at least) on the BSDs, on Solaris, and on Linux for terminal devices.

Instead of simply reading a portion, processing it whilst holding a lock, sending the other thread a shoulder-tap, then going back to look for another portion; make your program repeatedly read and process all portions until the master side of the pseudo-terminal is drained of output sent from the slave side, and only send the shoulder-tap when that is the case.
Or make your rendering side use a snapshot of the terminal state, and not lock the terminal state for the entire length of time that takes to render.

Instead of simply reading a portion, processing it whilst holding a lock, sending the other thread a shoulder-tap, then going back to look for another portion; make your program repeatedly read and process all portions until the master side of the pseudo-terminal is drained of output sent from the slave side, and only send the shoulder-tap when that is the case.

That's actually how alacritty currently works: https://github.com/jwilm/alacritty/blob/3c8514ba103d5d987d2269c421a3cc09e6784904/src/event_loop.rs#L259-L307
However, I think the idea of snapshotting the terminal state instead of holding a lock sound promising.

No, that's not how that code works.  That reads a portion, processes it whilst holding a lock, sends the other thread a shoulder-tap the first time around, and then releases the lock and goes back to look for another portion. That's not the same as sending the shoulder tap after the master has been drained; it is not the same as checking that there's no more to read before sending a shoulder tap.
Moreover, programs like nvim easily will cause multiple iterations of that loop with a single screen refresh, or scroll.  A redraw of a mere 80×25 window with syntax colouring on, for example, can easily generate between 6KiB and 8KiB of output in 256-colour mode; more in true-colour mode.  (I have managed to cut this down a bit for the nvim people, but this is what current release nvim does.)
Programs such as nvim can easily generate far more output in one lump for a single scroll/redraw than you are reading there in each iteration.  And the initial clear screen or scroll command that comes early in the output leaves part of the terminal blank until they re-draw what is on it later in the output.
So the problem behaviour is as described.  You are starting the render, locking the terminal state for a vertical blanking interval, when there's more than half of the nvim refresh/scroll output yet to be read from the pseudo-terminal and processed and half of the terminal is temporarily blank.  The fix is to process it all before rendering.  Then you won't get tearing like this.

Fun fact: I print out a string. Alacritty seems to print it out character by character, which definitely causes this behavior in my program.

@jdebp thanks for all the feedback. I'm working on this right now, and I think the way to go is just reading until getting an EWOULDBLOCK.

For programs based upon kevent(), the EVFILT_READ ...

This sounds great, but there's no equivalent for epoll.

There is a FIONREAD generic ioctl() ...

Doesn't work in my testing on macOS. Upon the event loop signaling read readiness, the ioctl just returns 0.

Making the pseudo-terminal master use non-blocking I/O tells read() to return if there are no more data.

I've been experimenting with this approach locally with good results. Note that nvim sometimes sends another tiny chunk after the primary chunk when paging. Here's some logs showing bytes processed on each iteration. When WouldBlock is encountered, the renderer is notified and the terminal lock released.
==== enter loop ====
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 1024
got 635
got 25
WouldBlock
processed: 11924
==== enter loop ====
got 75
got 81
WouldBlock
processed: 156

I'll follow up again here once there's a patch for others to try.

Please see #650 for the patch I promised. Although it seems to resolve the issue with neovim, it doesn't have any affect with vim 7.4 (haven't tested with 8) since write batching was apparently added in neovim.
I'm looking for some specific feedback on the patch. It seems that, on my system, this patch causes some hiccups where a frame is skipped, or input isn't delivered in a timely fashion. Could have been my imagination too. Would love to hear how it works for others!

@jwilm no flicker in neovim, or neovim in tmux!!

@jwilm I get a very occasional flickers on ctrl-f with neovim and the screen still flickers using neovim in tmux

FWIW, applying #650 on top of the current master fixed the flickering issues I previously had with regular vim 8.0 inside tmux 2.5.
> vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 22 2017 14:20:33)
MacOS X (unix) version
Included patches: 1-741
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     -tcl
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      -terminal
++builtin_terms  +fork()          +multi_lang      +terminfo
+byte_offset     -gettext         -mzscheme        +termresponse
+channel         -hangul_input    +netbeans_intg   +textobjects
+cindent         +iconv           +num64           +timers
-clientserver    +insert_expand   +packages        +title
+clipboard       +job             +path_extra      -toolbar
+cmdline_compl   +jumplist        +perl            +user_commands
+cmdline_hist    +keymap          +persistent_undo +vertsplit
+cmdline_info    +lambda          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      +lua             +rightleft       +windows
+diff            +menu            +ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      +startuptime     -xpm
+eval            +mouse_dec       +statusline      -xsmp
+ex_extra        -mouse_gpm       -sun_workshop    -xterm_clipboard
+extra_search    -mouse_jsbterm   +syntax          -xterm_save
+farsi           +mouse_netterm   +tag_binary
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X_UNIX  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector -L/usr/local/lib -L/usr/local/opt/libyaml/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lncurses -liconv -framework Cocoa  -L/usr/local/lib -llua -mmacosx-version-min=10.12 -fstack-protector-strong -L/usr/local/lib  -L/usr/local/Cellar/perl/5.26.0/lib/perl5/5.26.0/darwin-thread-multi-2level/CORE -lperl -lm -lutil -lc -F/usr/local/opt/python/Frameworks -framework Python   -lruby.2.4.1 -lobjc

I don't experience any flickers while scrolling since #1403 merge. Can anyone confirm this?

@fuine Has this issue been resolved for you with the latest master?

Closing as resolved by #1403. Should this issue still occur, please let me know and I'll re-open.

Still experiencing this
Details:
OS: MacOS Mojave
Alacritty: 0.3.0
Nvim: 0.3.4
Tmux: 2.8
NOTE: Alacritty flickers without tmux as well.

I'm on MacOS, this fix the flickering issue:
startup_mode: SimpleFullscreen

@tuannvm Nice find 👍
I can confirm this fixes the issue without tmux, however, with tmux issue still persists.

thanks @pratz , comment edited for clarification

I'm also experiencing the same issue 😢

I am also experiencing a similar issue to @pauldariye, it seems to happen in vim when my cursor hits certain lines in the buffer, the rendering issue is consistent to the line the cursor is on, not rendering further than that line

Having done a bit of quick experimenting, this seems to have been introduced in 0.3.1, 0.3.0 has been working fine so far, but I'll revert here if that changes

I'm also experiencing the same issue 😢

I'm experiencing the exact same problem with alacritty v0.3.2, nvim v0.3.5, tmux 2.9a.
It's usually fine at first, then it starts flickering like crazy after a few minutes of use. Flickering disappears each time I restart alacritty. Hope this gets addressed soon.

My problem actually seems to be fixed. https://github.com/jwilm/alacritty/issues/2353

@j30ng This is a different issue, it predates the regression of #2353.

I'm experiencing this issue as well. Are the labels still accurate for this issue? Doesn't seem like it's waiting on any feedback.

The feedback label is not accurate anymore, that got messed up in the re-open, thanks.

Any updates on this? I experience the same when I run flatpak update.

There have been some changes to the original issue, yes, but I don't think it's resolved. The primary issue is that I personally have never experienced it, so I can't look into it.
It's possible that some flickering in some applications can occur because Alacritty draws faster than the application would like it to draw, in which case there's little we can do.

@chrisduerr Other terminals don't have this issue so I'm sure it's somehow possible to avoid it.

@eternal-sorrow Slower terminals that take longer to draw would certainly have less issues and I don't think slowing down Alacritty would be an option.

i have the same issue. with and without tmux.

This isn't about slow/fast terminals, or about slowing down Alacritty.
A "bad behaving" client (one not buffering data into a single write, as described in https://github.com/alacritty/alacritty/issues/598#issuecomment-305961703) will lead to flickering, regardless of how fast the terminal is. But since it is timing dependent, how noticeable - if at all - depends.
Even XTerm, one of the slowest (if not the slowest) terminal has this problem (charproc.c):
    if (should_wait) {
	/* wait 25 msec for potential extra data (avoids some bogus flickering) */
	/* that's only 40 FPS but hey, it's still lower than the input lag on some consoles! :) */
	usleep(25000);
	should_wait = 0;
    }

Either you ignore this and say those clients should be patched to write updates in a single write. Or you could implement Synhronized Updates. This still requires the clients to be patched though.
Or you use heuristics to workaround the issue. Assuming you're vsyncing, then this is not about slowing down the terminal, but adding a delay between reading client data and rendering the updated state, in such a way that you give the client enough time to write its update in its entirety, but without delaying the rendering to the next frame. This is the tricky part.

The only option for alacritty are synchronized updates, however I don't see any reason for us to add implementation before proposal will be merged, etc. Once it'll be done we'll implement them. Though I'm fine if someone send a patch for it before acceptance, so we can just keep it around like we have PR for OSC 7 thing.
The issue about synchronized updates in alacritty is tracked there #2919 .

Or you use heuristics to workaround the issue. Assuming you're vsyncing, then this is not about slowing down the terminal, but adding a delay between reading client data and rendering the updated state, in such a way that you give the client enough time to write its update in its entirety, but without delaying the rendering to the next frame. This is the tricky part.

This is not an option, there's no notion of "enough time", it's subjective. synchronized updates are not subjective, since you know when clients are ready to be drawn.

if (should_wait) {
/* wait 25 msec for potential extra data (avoids some bogus flickering) /
/ that's only 40 FPS but hey, it's still lower than the input lag on some consoles! :) */
usleep(25000);
should_wait = 0;
}

but how do they know that 25ms is enough, 40 FPS isn't an option to render things. Like you can't say that 60FPS/90FPS is enough. you should just draw as fast as you can and not speculate with data, etc.

Assuming you're vsyncing, then this is not about slowing down the terminal, but adding a delay between reading client data and rendering the updated state, in such a way that you give the client enough time to write its update in its entirety, but without delaying the rendering to the next frame.

Delaying a render for any amount of time is slowing down the terminal for applications that are behaving just fine. Assuming you meant this without the support for the proposed synchronization escape.
It's also just a band-aid solution that will never actually work. It will just slow things down, hoping to help in some scenarios while never actually solving the problem.
So the synchronization escape is the only solution.

Delaying a render for any amount of time is slowing down the terminal for applications that are behaving just fine.

Rendering a frame takes (more or less) a fixed amount of time, yes? I know this is to simplify it, but roughly. You only need to render that frame before the next page flip, it doesn't matter when you render it (between the last flip and the next). Yes? So how is this slowing things down? You're not busy-waiting. You still process incoming data and update the internal state.
 That's bad. That's why it's tricky.

It's also just a band-aid solution that will never actually work.

Band-aid, yes. Not working, no.

So the synchronization escape is the only solution.

The absolutely most advantageous and preferred one, yes. Only one, no.

This is not an option, there's no notion of "enough time", it's subjective. synchronized updates are not subjective, since you know when clients are ready to be drawn.

The notion "enough time" does exist. You page flip at a fixed interval. Either your frame is ready by then, or it is not. Did you know that at least some Wayland compositors delay compositing to improve latency? It's not the same issue as discussed here, but related.
But yes, you can't know when the client's update is "done". That's why it's called heuristics. The assumption is that the writes of an update comes in a very quick succession.

but how do they know that 25ms is enough, 40 FPS isn't an option to render things

They don't. That's why it's called heuristics. It's a trade-off - you get less flickering, but you risk causing missed/skipped frames.
The XTerm solution is a very simple one that doesn't even try to guess how long time it can wait. I didn't say the XTerm solution was good. Just that XTerm also has this synchronization problem since there were comments here suggestion only "fast" terminals have it.

You only need to render that frame before the next page flip, it doesn't matter when you render it (between the last flip and the next). Yes?

No? Rendering a frame does not take a fixed amount of time, it depends on vsync which is its purpose. We might have approximately the same amount of time between frames, but even that would only be true if every frame was dirty. While it might be possible to delay the rendering a bit, up to the point where vsync blocks for basically zero seconds, this is not reliable, hard to determine consistently and would only give an extremely small timeframe that likely isn't going to help much.
XTerm's 25ms are massive for example. No matter how far away you are from the next vsync, that'll cause troubles. Which means frames are actually delayed, causing increased input latency.

Not working, no.

Not working, yes. No matter how long you delay, it will never stop you from an application pushing new stuff right when you decide to render.

The absolutely most advantageous and preferred one, yes. Only one, no.

Delaying rendering is not a solution. It's a hack that should help users perceive the problem less in some scenarios. The issue persists, it's just less prominent. That is not what a solution is.

The assumption is that the writes of an update comes in a very quick succession.

Just like the assumption that all connected data will be done in a single write. Completely pointless if you have to make assumptions about a client you have no control over.

Just that XTerm also has this synchronization problem since there were comments here suggestion only "fast" terminals have it.

The suggestion is just that fast terminals make it more obvious, which is true based on my testing.

No? Rendering a frame does not take a fixed amount of time, it depends on vsync which is its purpose.

Obviously, if you include the wait time caused by vsync. But that's an implementation artifact. Actual rendering is more or less fixed. At least if we for simplicity assume for example a full window with no empty cells.

While it might be possible to delay the rendering a bit, up to the point where vsync blocks for basically zero seconds, this is not reliable, hard to determine consistently and would only give an extremely small timeframe that likely isn't going to help much.

I did say it was tricky. My CPU-based terminal renders a full window update in ~5ms on a laptop without the CPU running in power saving mode. That means I have ~11ms to play with. That's not a "small" timeframe. Yes, it is unreliable. With the presentation protocol on Wayland, one can do better.

Not working, yes. No matter how long you delay, it will never stop you from an application pushing new stuff right when you decide to render.

Of course. It's a mitigation. Not a solution. While it's not "working", in theory, it actually does work in practice. But if it works in all the applications I use, then it is working. For me.

Delaying rendering is not a solution. It's a hack that should help users perceive the problem less in some scenarios. The issue persists, it's just less prominent. That is not what a solution is.

Yes, it's a hack. And I'll agree to not calling it a solution.

Just like the assumption that all connected data will be done in a single write. Completely pointless if you have to make assumptions about a client you have no control over.

Except that in practice, clients aren't malicious entities trying to break your terminal. This isn't about providing a 100% fool proof, always working solution, but, yes, to hide the problem from the users. A temporary workaround until clients, and terminals, implement synchronized updates.

The suggestion is just that fast terminals make it more obvious, which is true based on my testing.

Did you check if they implement workarounds?

My CPU-based terminal renders a full window update in ~5ms

That highly depends on the content of your full window and its size. Worst case you have basically no time to do any additional waiting and then just spend valuable resources that could have been used to actually improve the performance itself. That just doesn't align with Alacritty's goals.
I'm fully willing to implement the escape as soon as it's standardized on though and I'm perfectly happy driving that forwards. I've got only limited time and the time I have I'd rather spend bothering people to drive forwards a proper solution rather than implementing a hack that doesn't work, goes against the project's goals and has only negative impacts on people that do not experience these issues.

Did you check if they implement workarounds?

I tested Alacritty against itself. So yeah, pretty sure it doesn't implement any hacks for this.

To save a future reader/searcher of GitHub issues some time (and to save the maintainers having to answer the same thing twice ;-)...
This issue makes most programs using ncurses susceptible to flickering.
I did a bit of digging into ncurses itself to find out why this is the case; links below.
By default, ncurses buffers up changes made to the screen, and writes out only the difference between the last screen and the current one on a call to refresh(3). It does this with multiple write(2) calls that change the cursor position, satisfying the conditions for this issue.
A program can ask ncurses to not do this diffing, and instead redraw the entire screen, using clearok(3). Anecdotally, though, this'll still lead to multiple write(2) calls. I tried inserting a call to clearok(3) right before calling refresh(3), and ncurses redrew the entire screen with dozens of calls to write(2) (one per non-empty line).
That is to say, there is no obvious workaround here short of patching/refactoring ncurses itself to use a big enough buffer to perform the entire update in one go.

That is to say, there is no obvious workaround here short of patching/refactoring ncurses itself to use a big enough buffer to perform the entire update in one go.

In that case can this be reported to ncurses?

Chiming in here, please do tell if you wan't me to provide any sorts of information! It's still happening for me (running alacritty 0.5 on Windows)
Same behavior with scrolling in fzf as in https://github.com/alacritty/alacritty/issues/3819 (with and without tmux, doesn't matter) but it also happens when typing (filtering) in fzf. Highlighting things in vim with * causes the cursor to disappear completely and generally just moving with hjkl causes ghost cursors to appear (for me) both in bottom bar and in buffer/tab bar.
Another interesting problem occurs when running tmux with 2 windows, one containing vim and one just a terminal running yes. This causes cursor flickering in vim (cause yes is spamming the other window with y ?) and whenever you type in vim cursor flickering also occurs in the window running yes. This is a minor annoyance (similar to the fzf issue), but even more annoying is that vim is extremely slow during this time, compared to a traditional terminal emulator which runs fine without flickering. Now, of course i don't sit in vim all day with yes running in another tmux window, but the same behavior for applications producing any kind of output (e.g. logs or compilations etc.)
This, unfortunately, makes the terminal emulator borderline to unusable, as a daily driver, to me :-(
I'm not sure if the disappearing cursor on highlight is related, or if it's a separate issue (let me know and i'll create one with more info)


[P1] Migrate all .NET projects to .NET 8 (released GA on March 15th 2024)

Migrate all .NET projects to .NET 8 (released GA on March 15th 2024)
https://dotnet.microsoft.com/en-us/download
Let's do it incrementally while we "touch/update" code from the multiple services using .NET.
But we should be using .NET 8 in all services before mid-April.

This is done, all .NET projects are using now .NET 8.0


FontAwesome provide non-CDN url

Hi,
We are using this great library inside an application that is running internally on-premise without internet connectivity. The application on it's turn is also a standardised CMS, so modifications in terms of inserting FontAwesome on the index.html is not really..appreciated. If at least we want to stick to the latest version and not create our own version.
We are working on a PR to include the CMS's dependencies locally instead of loading them via CDN. Thus we also did it for simplemde. Now we see that simplemde also uses a cdn inside their code base.
Looking at the documentation, the first parameter autoDownloadFontAwesome

autoDownloadFontAwesome: If set to true, force downloads Font Awesome (used for icons). If set to false, prevents downloading. Defaults to undefined, which will intelligently check whether Font Awesome has already been included, then download accordingly.

Looking at the code, it's not so "intelligently" as I hoped:
https://github.com/sparksuite/simplemde-markdown-editor/blob/6abda7ab68cc20f4aca870eb243747951b90ab04/src/js/simplemde.js#L1276
It simply enforces to load via CDN anyway if it's not in the index.html (or loaded in another way).
Feature request:

Could we provide an additional config parameter fontAwesomeUrl to specify an URL for ourselves? In this way we can reference to our own (relative) url?

SELECT * from DSDSDSDS


Website is down

There seems to be some major server issue, as the website only returns a continuously-reloading CloudFlare landing page.

Issue seems to be resolved, don't know if it was just a hosting issue or something that resolved itself automatically, but I'll close this.

Thank you!


remove duplicated nova in text editors

NOTE: A similar PR may already be submitted! Please search among the Pull request before creating one.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply

[ ] New addition to list
[ ] Fixing bug in existing item in list
[x] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.
I have remove the duplicated Nova from text editors as it has already been added.
reason: Panic is the name of the makers of coda, as you can see from here.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[x] I have added necessary documentation (if appropriate)

Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@mooxiu It needs to be in alphabetical order.

My fault, I will fix it soon

@mooxiu thx!


Parallel state execution impl

This PR is related to https://github.com/coinbase/step/issues/61
In this PR were implemented following:

was added ability to execute parallel state itself
was added validation of unreachable states in state machine
jsonpath was slightly expanded to process array of interface{} (for work with arrays in InputPath and OutputPath)
were added a series of tests that shows how to execute state machine with go handler functions

Hey, thanks for this PR!
We are going to be archiving this project and moving it internally. It will continue to be available to fork and use.
The main comments I would make around this PR (for future PRs) is that this should be 2-3 PRs and to minimize the diffs removing unnecessary changes. This would make it easier to review and test individual changes and merge.
Cheers again for the good work.
Graham


optionally append to the chef log in cron mode

What it says on the tin. Default behavior remains the same - log will be overwritten each time.
This was my first time doing test kitchen things - let me know if it's appropriate.

Closing in favor of #261 due to non-response


add tags in invocation structure

Coverage increased (+1.2%) to 63.034% when pulling 2a3175ab612593e02700a22885ef86d6ee1b4463 on tianxiaoliang:master into 34e3984b923d981d09105215f02003c8f84e159b on ServiceComb:master.


Update metadata fields in order to create links

@ainurchik Could provide one example to help with this? For any one indicator, what link would you like to appear?

Sorry, Brock...What link/example you ask? I am not understand your question

Брок просит дать пример как будет выглядеть ссылка показателя/индикатора

No problem - I believe this issue was about getting a link into the "National Metadata" for an indicator. I think the purpose was to link to a PDF file?
I was wondering if you could provide one as a specific example. In other words, let me know this info:

Which indicator?
What the link should say?
Where the link should link to?

It's not urgent, but would helpful to me.

Ok, Brock...I understand and try to provide some example some later, on this weekend

I will close this for now, and we can open new issues as needed.