After update VS Code hangs on typing several chars in typescript code

We have written the
Issue Type: Performance Issue
Hello
After recent update my insider version of Visual Studio Code hangs after typing something in typescript files for about 20 seconds. Then it releases and than hangs again after input. It is unusable now.
VS Code version: Code - Insiders 1.32.0-insider (9441f43636a639aaffa28a9c7e6e36151944c8b3, 2019-02-12T06:16:54.110Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (4 x 1800)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.89GB (5.17GB free)

Process Argv

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    72	 18648	code-insiders main
    0	   207	  5588	   window (● dashboard.state.ts - QuoteBuilder.Frontend - Visual Studio Code - Insiders)
    0	    26	  9592	     searchService
    0	   149	 11592	     extensionHost
    0	   540	 13040	       electron_node tsserver.js
    0	    16	 18676	         electron_node typingsInstaller.js typesMap.js
    0	    19	 13104	       "C:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" "c:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\json-language-features\server\dist\jsonServerMain" --node-ipc --clientProcessId=11592
    0	    46	 17344	       electron_node server.js
    0	    37	 23412	       electron_node tslintServer.js
    0	     9	 18860	     electron-crash-reporter
    0	    11	 22356	     watcherService
    0	     5	 16496	       console-window-host (Windows internal process)
    0	   212	  9500	   window (Process Explorer)
    0	    65	 13752	   window (Issue Reporter)
    0	   347	 14228	   gpu-process
    0	    48	 20028	   shared-process

Workspace Info
|  Window (● dashboard.state.ts - QuoteBuilder.Frontend - Visual Studio Code - Insiders)
|    Folder (QuoteBuilder.Frontend): 3800 files
|      File types: ts(1200) dll(493) cs(429) html(373) scss(367) xml(234)
|                  pdb(157) resources(95) resx(95) config(91)
|      Conf files: csproj(11) package.json(2) tsconfig.json(1) tslint.json(1)
|                  settings.json(1) tasks.json(1);

Extensions (9)

Extension
Author (truncated)
Version

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

tslint
eg2
1.0.43

vscode-scss
mrm
0.6.2

tsimporter
pmn
1.2.14

typescript-hero
rbb
3.0.0

vscode-icons
rob
8.1.0

stylelint
shi
0.48.0

vscodeintellicode
Vis
1.1.3

needed data into your clipboard because it was too large to send. Please paste.

Window becomes about 40% after typing something.
40%	   207	  5588	   window

To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks.
When Code is consuming lots of CPU, please run "code --status" from the command line (or "code-insiders --status" if you are using VS Code Insiders edition).
Please attach the output of this command to this issue. Thanks!

I had the same issue, code hangs in a matter of seconds after start and code --status some times would hang as well. After sometime a prompt pops up asking for waiting or closing app. Here is a successful attempt of status info:
Version:          Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:19:29.629Z)
OS Version:       Linux x64 4.4.0-142-generic
CPUs:             Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz (4 x 1126)
Memory (System):  3.76GB (0.50GB free)
Load (avg):       0, 0, 0
VM:               0%
Screen Reader:    no
Process Argv:     --disable-extensions
GPU Status:       2d_canvas:                    enabled
                  checker_imaging:              disabled_off
                  flash_3d:                     enabled
                  flash_stage3d:                enabled
                  flash_stage3d_baseline:       enabled
                  gpu_compositing:              enabled
                  multiple_raster_threads:      enabled_on
                  native_gpu_memory_buffers:    disabled_software
                  rasterization:                disabled_software
                  surface_synchronization:      enabled_on
                  video_decode:                 unavailable_off
                  webgl:                        enabled
                  webgl2:                       enabled
CPU %	Mem MB	   PID	Process
    1	   123	 15788	code main
    0	    39	 15795	   zygote
    1	   196	 15839	     window (quiz1.md - Visual Studio Code)
    0	    96	 15867	       extensionHost
    0	   100	 15884	     shared-process
    0	    92	 15827	   gpu-process

But after using --disable-gpu flag on startup, code stopped hanging any more.

Hello
I can't execute this command because vs code is hanging. There're 2 processes that hangs
"C:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" --type=renderer --no-sandbox --enable-features=FixAltGraph --service-pipe-token=8C863131AE42839404695F23D9F42785 --lang=en-US --app-user-model-id=Microsoft.VisualStudioCodeInsiders --app-path="C:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app" --node-integration=true --webview-tag=true --no-sandbox --background-color=#1e1e1e --device-scale-factor=1 --num-raster-threads=2 --enable-main-frame-before-activation --enable-compositor-image-animations --service-request-channel-token=8C863131AE42839404695F23D9F42785 --renderer-client-id=4 --mojo-platform-channel-handle=2224 /prefetch:1
"C:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" "c:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\SERGEY~1\AppData\Local\Temp\vscode-typescript\tscancellation-62cd592ffca271fd318b.tmp* --logVerbosity verbose --logFile "c:\Users\Sergey Kuchuk\AppData\Roaming\Code - Insiders\logs\20190213T095022\exthost1\vscode.typescript-language-features\tsserver-log-7ZrWlr\tsserver.log" --globalPlugins @vsintellicode/typescript-intellicode-plugin --pluginProbeLocations "C:\Users\Sergey Kuchuk.vscode-insiders\extensions\visualstudioexptteam.vscodeintellicode-1.1.3" --locale en --noGetErrOnBackgroundUpdate

Issue is not appearing if to type in field name

@drweb86-work

Do you see this issue if you disable all extensions?
Can you also check the developer console to see if there are any errors. To do this, run the Developer: Toggle Developer tools command in VS Code and look in the console section of the developer tools window that opens.

Hello
That happens because of TypeScript Importer plugin
https://github.com/starkevin/VSCode-TypeScript-Importer/issues/14
Thanks.


Add commits and contributor links on homepage

Remove bold from last compiled date
Move "View commits" link to new line, increase font size
Add "Contributors" link next to "View commits"
"Contributors" links points to https://github.com/QuantEcon/lecture-python-programming/graphs/contributors

nice. Thanks @DrDrij


Uploading files with umlaute (ö,ä,ü) causes Error 500

Tested with uploading Bandsäge.aac as an audio file.

geht bei mir

@dkehne @svenseeberg worked for me as well

Problem still occurs on the live system. Same for image files.

fixes in #150 and #160


Account for non-square pixels

Video formats can contain non-square pixels. I forgot how FFMPEG handles this, but it shouldn't be difficult to implement.

struct AVFrame in avcodec.h

    /**
     * sample aspect ratio (0 if unknown)
     * That is the width of a pixel divided by the height of the pixel.
     * Numerator and denominator must be relatively prime and smaller than 256 for some video standards.
     * - encoding: Set by user.
     * - decoding: Set by libavcodec.
     */
    AVRational sample_aspect_ratio;


Tokens remain in Vault after SettleFunds is executed

I am writing a client (in Rust) to interact with Serum. When testing@devnet it (a simple case when two participants place Asks / Bids orders with an exchange rate of 1:1), I encountered a problem that the Ask side funds (pc token) are not returned to the account even after the SettleFunds instruction has been executed. In this case, the proceeds from the sale of coin tokens pc tokens are stored in the vault. Thus, for payer / wallet # 1 we have the following balance (after order execution and SettleFunds) -1 coin, for payer / wallet # 2: -1 pc, +1 coin.
P.S> Do you plan to develop a client library for Rust (similar to serum-ts) ?
Before order placement

State after orders execution and SettleFunds

SettleFunds logs for payer#1

SettleFunds logs for payer#2

Vault

Market Info
own_address:    7KH444DFaHsnJECWhmLe3VYhqSn8XY2RtxPrsLS92rhS
coin_mint:      9ZpZqwJfDQzppXkazKBTqNFW1z4rLL9wxbkbhPbWTb3n
pc_mint:        G5JuS6p1TX7P3dz2DhiQ1L1exERem6Ayn5ZwqXx29dkn
coin_vault:     8h8yreygpuRiwqhRwzGFNdrNT7P9qx9f9HADyzxZrJvY
pc_vault:       HiX9rBut3LU5P3GwT2aR8uC1co6gKRjM5UYtcPZHca7j
req_q:          EXeDheqgB8dQLN7NYrUn6zwm6Cg6Z21LLXxb9xvWRfTR
event_q:        FR6Gn5HHNG8i4au62ec7hA1RnsBSXS1SMFCiTtKj6qdq
bids:           5Fm4HGTVeRsttjM3oSPVuyUq5awLdbTT5UtpmCwMghwM
asks:           CamnzxFGMKCszpUgHsYipHh9YTag3TeXSWtnqvqiDdn8
coin_lot_size:  100000
pc_lot_size:    100
pc_decimal:     9
coin_decimal:   9

Payers/wallet Info
wallet #1 addres: BXhe2cKFT6UEF5gLiHCDJnqQVxyKVsjnH95m3AaCDCRc
wallet #1 pc addres: 3dhhuqUTq2oQxh4Lhz1zyeJoUnip31LWUK6sWvccyptL
wallet #1 coin addres: 5f9UiFcVPnK1u2k9sHW4Qqx6kesbpBLrVfSBCRujK5h6

wallet #2 addres: 857hQyZViutfWSSUj5HL1oxJP5goBHTvzAMNWCQpg9Z7
wallet #2 pc addres: 2UiNCsmECibXM4AW7ePGe7zFQkxoAtfGsGWX6jn6iuRU
wallet #2 coin addres: CSYU2V943K4ZPEvwLRZvPDaFumVjaZ4Sht3UKe3WNy5o

Additional Info

Hi @PraetorP same issue here. To be precise, I observed that for any maker sell / buy order, the maker does not receive  proceeds after transaction settles. Order settles fine with taker. Did you manage to resolve this issue?

Hi @PraetorP same issue here. To be precise, I observed that for any maker sell / buy order, the maker does not receive proceeds after transaction settles. Order settles fine with taker. Did you manage to resolve this issue?

Hi @beepsaidblue! Yes, I found a solution. I wanted to close the issue, but I saw your message :) . If you have your own test market, then you need to run crank for it or make your own approach to processing the event queue (with calling the consume events ix).

@PraetorP Could you point me to any sample code for how to do cranking?


Add mention of sharing accounts and credentials

Front, like some ticketing and communications solutions, sees some usage of "shared accounts" where daily access to the platform is not needed. For example, and IT Administrator may only need to access Front when a new user needs to be created or adjusted. It would be helpful to add a section explaining this or calling out this article: https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/users-sharing-accounts

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

ID: e166e294-8c53-e18d-a01e-2c595fb2f4bc
Version Independent ID: 3d8b5f47-727f-9f60-a24c-19622fcea177
Content: Tutorial: Azure Active Directory integration with Front
Content Source: articles/active-directory/saas-apps/front-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@tonypitkin
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@tonypitkin
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@tonypitkin I think you are referring to service accounts here. In this scenario we are suggesting to use the Federated single sign on for the application. For service account scenario they can use OIDC OAuth non-interactive sign in and that is much better and secure here.

@please-close


list of all issues/PRs of all owned repos

Description
list of all issues of all owned repos
from a blog article Flexible issue management

Like many open source developers I use GitHub to publish my work. It comes with a built-in issue tracking system, however, it isn’t that great.
The main issue - no pun intended - I have with it is that there is not an easy way to see all open issues and pull requests on all repositories you have.

I can hardly give a better description of the issue.
apologies if this is already possible and I've missed it, thanks

<insert host>/pulls?type=your_repositories&repo=0&sort=&state=open
<insert host>/issues?type=your_repositories&repo=0&sort=&state=open
Do you mean something else ?
Those are obtained through the top bar: Issues and PR.

thanks it's great in gitea; still can't find it in GitHub but thanks anyway!


Revision token issues shouldn't result in a 5xx error

Currently it does
/kind bug

/kind good-first-issue

Sample logs
2020-08-04T03:36:13.331056Z DEBUG SERVER - Current day keys are not being embargoed. E
2020-08-04T03:36:13.346488Z attempt to revise key not in revision token. E
2020-08-04T03:36:13.348433Z error writing exposure record: attempt to revise key not in revision token. E
  undefined

stacktrace: "github.com/google/exposure-notifications-server/internal/publish.(*publishHandler).handleRequest
	github.com/google/exposure-notifications-server/internal/publish/publish.go:239
github.com/google/exposure-notifications-server/internal/publish.(*publishHandler).ServeHTTP.func1
	github.com/google/exposure-notifications-server/internal/publish/publish.go:282
net/http.HandlerFunc.ServeHTTP
	net/http/server.go:2041
github.com/mikehelmick/go-chaff.(*Tracker).HandleTrack.func1
	github.com/mikehelmick/go-chaff@v0.3.0/tracker.go:212
net/http.HandlerFunc.ServeHTTP
	net/http/server.go:2041
github.com/google/exposure-notifications-server/internal/publish.(*publishHandler).ServeHTTP
	github.com/google/exposure-notifications-server/internal/publish/publish.go:298
net/http.(*ServeMux).ServeHTTP
	net/http/server.go:2416
go.opencensus.io/plugin/ochttp.(*Handler).ServeHTTP
	go.opencensus.io@v0.22.4/plugin/ochttp/server.go:92
net/http.serverHandler.ServeHTTP
	net/http/server.go:2836
net/http.(*conn).serve
	net/http/server.go:1924"

/assign
put up a short term fix so that bypass works
need to add tests for bypass
and make sure that 400 level errors don't result in 500 error codes


Has the quarterly dataset update schedule been adhered to?

On the cloud console details page both the public patents and research datasets are said to update quarterly.  However, the bigquery details tab for each datatset lists February as the last update (6-7 months ago at the time of this issue).
In the event this isn't the right place to ask about the dataset updates,  where should I reraise this issue?

That date is (confusingly) the last updated date for the marketplace info page. Look at the last modified date of the table in BigQuery: https://console.cloud.google.com/bigquery?p=patents-public-data&d=patents&page=table -> details.

We've updated the tables again this week

@wetherbeei Is it possible to open source the ETL pipeline?
I'm assuming its Dataflow.

Sorry it isn't possible- it relies on an underlying data feed from IFI Claims.
If update speed is a concern, IFI Claims has a weekly updated paid BigQuery table with many more fields and all of the translated full text.

Thanks for that info.


Dashboard tab for admin displays a users table that will not scroll (bug)

https://github.com/ledgerleapllc/devxdao-backend/issues/59

Frontend commit  https://github.com/ledgerleapllc/devxdao-frontend/commit/e0a010cc930c1330e292980493f77769e81bb152


Vectorized Parquet Read In Spark DataSource

The Parquet file format reader that is available in core Spark includes a number of optimizations, the main one which is in vectorized columnar reading. In considering a potential migration from the old Spark readers to Iceberg, one would be concerned about the gap in performance that comes from lacking Spark's numerous optimizations in this space.
It is not clear what is the best way to incorporate these optimizations into Iceberg. One option would be to propose moving this code from Spark to parquet-mr. Another would be to invoke Spark's parquet reader directly here, but that is internal API. We could implement vectorized reading directly in Iceberg, but that is very much to suggest that we reinvent the wheel.

I think there's some merit to passing off all the low level optimizations to parquet-mr - that way they're available everywhere, Spark - Iceberg - otherwise. Much of that work isn't specific to Spark, from my understanding.
If we did it that way, the delta between using Spark's Parquet data source or implementing one's own isn't that large. It becomes more of just flavor around how to bootstrap the parquet-mr modules.

There are a few problems with the vectorized read path in Spark: it only supports flat schemas and has no support for schema evolution.
What we've been planning on is to use the Arrow integration in Spark to get vectorized reads. There's already an implementation of Spark's ColumnarBatch translates from an Arrow RowBatch for PySpark/Pandas integration. Having deserialization directly to Arrow would be a benefit to multiple engines. We're considering using it in the Presto connector as well, and it would work well in a record service (possibly using Flight).

How would that integrate with the existing Parquet file format? This would be a blocker for many places that rely on Parquet in existing data sources and want to port over to Iceberg (this is what we're thinking of doing). We can't afford to lose the read optimizations there, that would be a performance regression for our Spark applications.
Are there ways to patch the vectorized read path in Spark to address those issues? Or can we support vectorized read with the limited subset of cases where it does work?

We could create vectorized readers in Iceberg that do the same thing as Spark, but I think it is a better use of time to deserialize to Arrow, which has support for memory optimizations like dictionary-encoded row batches.
All of this work can be thought of as an in-memory representation. Iceberg has an API for deserializing pages to rows, it would add one for deserializing to a column batch.
Agreed that this is a performance blocker if you have flat tables and don't need schema evolution. But I don't think that producing Spark's ColumnarBatch would be much easier than producing Arrow.

Iceberg would deserialize to Arrow's RowBatch, which is a more useful in-memory representation because it could support non-Spark engines. Spark can use Arrow RowBatch because there's a wrapper than translates to its internal columnar representation, ColumnarBatch. The vectorization part is the materialization to Arrow.
Performance should be comparable and would also support projection and nested data.

I should also note a few things about performance:

Iceberg can prune splits more aggressively using min/max stats, which can be a huge speed-up for selective queries even without vectorization.
Iceberg should be faster than the native Parquet read path in Spark when not using the vectorized reader. The native read path uses a slower record materialization API and also makes 2 copies of every row before passing it up to the next operator. See the v2 InternalRow PR for more detail.

Cool, we can experiment with that but we always use the vectorized reader though. Is there an expected timeline for the Arrow vectorized read to land? Would also be happy to help move that forward.

I don't have a timeline for Parquet to Arrow reads. @julienledem has some experience with that and can probably comment on the amount of effort it would require.
I built the record-oriented read path here in a couple of weekends, so I think it would go fairly quickly. There's a lot of work we could do here, though. Including getting the APIs right to take advantage of page skipping.

It looks like Parquet into Arrow conversion is already available for Python at least: https://arrow.apache.org/docs/python/parquet.html. I think there's something similar for C++ but am still exploring the tech: https://github.com/apache/arrow/tree/master/cpp
I wonder what it would take to port this work over to Java? I would hope the algorithms in the implementations would translate between languages nicely.

I've opened a new issue for this in the ASF project: https://github.com/apache/incubator-iceberg/issues/9
Let's move further discussion there. Thanks!


 Now that you've assigned yourself, people who drop by know that they're welcome to participate, but you'll be carrying this issue across the finish line. :sunglasses:.
Let's use GitHub Pages
Now, on to business! GitHub Pages allow you to serve a static site from a repository. We've filled this repository with some site content, but the rendered site isn't visible right now. Let's change that.
:keyboard: Activity: Enable GitHub Pages

Click on the Settings tab in this repository
Scroll down to the "GitHub Pages" section
From the "Source" drop down, select master branch

Note: Even though you'll see an option to choose a theme, do not apply a theme at this point. We've protected the code so you can't make unintended changes. You'll have the opportunity to apply a theme when the course is completed.

I'll respond in this issue when I detect GitHub Pages has deployed your site.

Turning on GitHub Pages creates a deployment of your repository. I may take up to a minute to respond as I await the deployment.

Originally posted by @github-learning-lab[bot] in https://github.com/Documentus/github-slideshow/issue_comments/707961075

Turned on GitHub pages over 15 hours ago, still seeing the same message!


Hidden requirement for geopandas in apache-sedona[spark] 1.5.2

Expected behavior
Installing Sedona for pyspark with package apache-sedona[spark] we expect that all package dependencies are installed correctly and geopandas is not needed when not using kepler or pydeck.
Actual behavior
After installing apache-sedona[spark] and trying to import from sedona.spark import * we see failure ModuleNotFoundError: No module named 'geopandas'
$ pip install "apache-sedona[spark]"==1.5.2
$ python
Python 3.8.18 (default, Feb 13 2024, 15:47:05)
[Clang 15.0.0 (clang-15<IP_ADDRESS>.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from sedona.spark import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/spark/__init__.py", line 44, in <module>
    from sedona.maps.SedonaKepler import SedonaKepler
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/maps/SedonaKepler.py", line 18, in <module>
    from sedona.maps.SedonaMapUtils import SedonaMapUtils
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/maps/SedonaMapUtils.py", line 19, in <module>
    import geopandas as gpd
ModuleNotFoundError: No module named 'geopandas'

Steps to reproduce the problem
Create clean python environment and run commands:
$ pip install "apache-sedona[spark]"==1.5.2
$ python
Python 3.8.18 (default, Feb 13 2024, 15:47:05)
[Clang 15.0.0 (clang-15<IP_ADDRESS>.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from sedona.spark import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/spark/__init__.py", line 44, in <module>
    from sedona.maps.SedonaKepler import SedonaKepler
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/maps/SedonaKepler.py", line 18, in <module>
    from sedona.maps.SedonaMapUtils import SedonaMapUtils
  File "/python/versions/3.8.18/lib/python3.8/site-packages/sedona/maps/SedonaMapUtils.py", line 19, in <module>
    import geopandas as gpd
ModuleNotFoundError: No module named 'geopandas'

Settings
Sedona version = 1.5.2
Apache Spark version = 3.5.1
Apache Flink version = ?
API type = Python
Scala version = N/A
JRE version = 1.8
Python version = 3.8
Environment = Standalone

Hello, thanks for the fast and response!
I think that the python will load the __init__.py file for the sedona.spark module even when importing sub file from the given module sedona.spark.

This is very sad. We will make a follow up release to fix this bug.

We have released 1.5.3 to fix this bug! @joonaspessi


feat(new): Added Azure.ServiceBus.GeoReplica

PR Summary
Working towards #2988
Added Azure.ServiceBus.GeoReplica.
PR Checklist

[x] PR has a meaningful title
[ ] Summarized changes
[ ] Change is not breaking
[ ] This PR is ready to merge and is not Work in Progress
Rule changes

[ ] Unit tests created/ updated
[ ] Rule documentation created/ updated
[x] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Hi @BernieWhite. I need some feedback from you on how to construct the rule body on this in the best way possible, also given the updates that will come so we don't have to do major refactor. The documentation states specifically Currently only a single secondary is supported.
Do you have any thoughts on how the rule body can look like? I have uploaded the draft design in this PR, but I feel it is to static and if the order is wrong in the array it will not work correctly.
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-replication#using-bicep-template

Hi @BernieWhite. I need some feedback from you on how to construct the rule body on this in the best way possible, also given the updates that will come so we don't have to do major refactor. The documentation states specifically Currently only a single secondary is supported.
Do you have any thoughts on how the rule body can look like? I have uploaded the draft design in this PR, but I feel it is to static and if the order is wrong in the array it will not work correctly. Maybe two contains methods can be used? If the operand is an array of strings, only one string must contain the specified string.
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-replication#using-bicep-template

Thanks @BenjaminEngeset I think the can primarily count how many entries are in properties.geoDataReplication.locations. i.e should be 2 or greater. The specific locations or roles and their order don't really matter and could easily change.

Ready for review @BernieWhite.
I noticed one thing that made me unsure about using YAML and that was that once the AllOf operator finds a fail, it will return and yield only that. So when the customer thinks that it is only the SKU that is the problem, next time it will yield the geo-replication configuration. I want both failures to be yielded. What do you think, is there anything we can do or should we move over to PowerShell?

Ready for review @BernieWhite.
I noticed one thing that made me unsure about using YAML and that was that once the AllOf operator finds a fail, it will return and yield only that. So when the customer thinks that it is only the SKU that is the problem, next time it will yield the geo-replication configuration. I want both failures to be yielded. What do you think, is there anything we can do or should we move over to PowerShell?

That's fair. We should just improve that behaviour in PSRule.

Thank you for the feedback. The requested changes have been implemented, @BernieWhite.


Disable caching

Hello,
Great piece of software. It is very helpful.
I use it as OAuth2 resource server. But I would like to turn off caching because I need to revoke access to resource instantly after revoking token on authorization server.
When I tried to set OIDCCacheShmMax to 0 I get sometimes (do not know when) Apache errors. Is there a proper (Or at least another) way how to disable caching?
Thank you
Ondrej

You should make the Authorization Server indicate that the token should not be cached. i.e. in  expires_in value of the token introspection result.

I'm not sure we understand each other. If token is cached on the resource server (in openidc module) it does not even contact authorization server, right?
If module askes for the first time I send expiration time. But if somebody decides to revoke token on authorization server earlier than expiration time (e.g. user decide he do not want to give access to the client anymore) module had no opportunity to find out.

Bottom line is: if the Authorization Server wants to be able to allow token revocation, it should make the Resource Server not cache the token by sending the appropriate expires_in value.
Theoretically there could be a configuration option that overrides the cache hint from the authorization server, but practically it doesn't make sense to try and support token revocation without the Authorization Server supporting it so I'd say you should configure the Authorization Server appropriately.

Ehm. Where did you find it? It is not in spec, is it?

As https://github.com/pingidentity/mod_auth_openidc/wiki/OAuth-2.0-Resource-Server suggests it depends on the Authorization Server that you use. If it implements RFC 7662 the relevant claim would be called exp. mod_auth_openidc supports a range of variants.

I think I got it. Expires_in value can be different for client and resource server. And these values can be less than real expiration time of token. And in case I do not want to cache it server has to put 0 value in expiration_in for resource server. Unfortunately my authorization server (OAuth-Apis) seems it can not distinguish these two values. I will figured out it somehow. Anyway the value should be called different (e.g. cache_time) if it is something different than expiration time. :/
Thank you. You can close it.
Ondrej

if you think about long enough you'll see that there is no difference


bash history mixed between different terminal

Hi I love this tool, but not it is mixing the story between all the terminals.
So, when I move up in the historic on a terminal A, I see the commands I have recently executed on terminal B. This is not the usual behaivour.
I guess it is because of the hopt -s histappend , is it oka to remove this line from the basrc? or, it would affect other features of hstr?

I have the issue issue.  The way I would expect this to work is that any new shells should see the history of all shells, but existing shells should have the immediate history of itself.


feat: json and bson document unwinding

It's nifty (and I think good!) to expose document-native tools for
filtering and selecting data stored in document formats (as we have
and may do more of.) But why not convert documents to the DF Struct
type so that we can just use normal SQL.
Remaining work

[ ] testing, obviously.
[ ] make sure we're good with unwind as a name for this.
[ ] (maybe?) do something recursive in JSON (this patch doesn't do that yet.)
[ ] come to some agreement about how to hanlde (potentially heterogeneous) arrays.

make sure we're good with unwind as a name for this.

I'm good with unwind, I'm even more good with parse_* since I think that would match what people would expect.

For array handling (and we should normalize here and this elsewhere), the options are:

reject heterogeneous arrays (what happens here for bson), and convert all arrays to lists.
do not attempt to unwind arrays, and leave these in their serialized forms (this is what happens here for json).
treat arrays and objects/documents (e.g. structs with keys that are either indexes (integers) or stringified integers). This is the internal representation of bson documents (string keys).

There exists the broken implementation in the current MongoDB and BSON table funcs (which share code), which is that we decide the type of the array for the schema based on the type of the first element and then convert all values to strings.
Having implemented options one and two, I'm inclined to convert everything to option 3:

pros: doesn't lose data, doesn't error
cons: potentially unintuitive. potentially inconsistent with native JSON handling.

Thoughts?

reject heterogeneous arrays (what happens here for bson), and convert all arrays to lists.

For array handling (and we should normalize here and this elsewhere), the options are:
* reject heterogeneous arrays (what happens here for bson), and convert all arrays to lists.

* do not attempt to unwind arrays, and leave these in their serialized forms (this is what happens here for json).

* treat arrays and objects/documents (e.g. structs with keys that are either indexes (integers) or stringified integers). This is the internal representation of bson documents (string keys).

There exists the broken implementation in the current MongoDB and BSON table funcs (which share code), which is that we decide the type of the array for the schema based on the type of the first element and then convert all values to strings.
Having implemented options one and two, I'm inclined to convert everything to option 3:
* pros: doesn't lose data, doesn't error

* cons: potentially unintuitive. potentially inconsistent with native JSON handling.

Thoughts?

Is the problem we're trying to solve here around being able to accurately infer the type of an array?
If so, I think we'll be hitting some amount of difficulty with getting accurate types, especially in the case of heterogenous arrays no matter if we go with option 1 or 3.
I have no issue with option 3, and I'd be down to explore that, especially if it makes the type problems easier.

Is the problem we're trying to solve here around being able to accurately infer the type of an array?

Yes. If you have [1, true, null, "hello world", 0.34, {"a": 1}] what do you do with this?

If so, I think we'll be hitting some amount of difficulty with getting accurate types, especially in the case of heterogenous arrays no matter if we go with option 1 or 3.

Option 1 is just to error (and this would cause the users' query to fail. I think we should do this rather than just ignore these values, but it's bad.
Option 3 couldn't error in this case. What is the difficulty you're referring to?

I have no issue with option 3, and I'd be down to explore that, especially if it makes the type problems easier.

I think it does. The main questions/problems that it raises:

It might be unexpected to users.
It might (probably?) would be inconsistent with how the JSON table functions and external data provider function.

I'm good with unwind, I'm even more good with parse_* since I think that would match what people would expect.

I was mostly just stealing this term, which isn't a good fit, admittedly.
Particularly if we do the thing with recursively parsing arrays into structs then it is closer to unwinding.
There's future work if people like this to let people project here, which would be kind of boss.

Yes. If you have [1, true, null, "hello world", 0.34, {"a": 1}] what do you do with this?

Idk, I remember doing the initial mongo implementation and just punting on it since I didn't have a good answer then (or now). So I'm definitely down to explore option 3 to get that to work.

Option 1 is just to error (and this would cause the users' query to fail. I think we should do this rather than just ignore these values, but it's bad.
Option 3 couldn't error in this case. What is the difficulty you're referring to?

I meant to say that I think we would have the same amount of difficulty if we tried to use Lists or Structs for this since they'll both end up with some complicated types, because we could generate a list data type that includes all possible field types with structs and unions.

I think it does. The main questions/problems that it raises:
It might be unexpected to users.
It might (probably?) would be inconsistent with how the JSON table functions and external data provider function.

I'd want to think on this a bit more, I don't have a strongly formed opinion on this yet, and I'd want to see what other databases (like postgres) do here.

I meant to say that I think we would have the same amount of difficulty if we tried to use Lists or Structs for this since they'll both end up with some complicated types, because we could generate a list data type that includes all possible field types with structs and unions.

Oh I hadn't thought about the list/union situation. This is gross, but maybe cool. Let's call this option 4.

I'd want to think on this a bit more, I don't have a strongly formed opinion on this yet, and I'd want to see what other databases (like postgres) do here.

postgres supports heterogeneous arrays, probably doing something like option 4.
I'm still worried about sort of just having to copy what datafusion does.

Regardless, I think we should probably do the better array handling as part of another PR.

Regardless, I think we should probably do the better array handling as part of another PR.

Completely agree with this.

make sure we're good with unwind as a name for this.

I'm good with unwind, I'm even more good with parse_* since I think that would match what people would expect.

+1 for parse_*.
FWIW, that's what snowflake calls this function as well.

Going to close. I don't think writing an arrow_cast-type function makes sense right now, and despite some poking, I don't think there's much to be done.


issue in iOS app with wkwebview

Description

Editor does not respond when built for ios using cordova.
iOS version -13.5
How to reproduce?
Create the editor as usual. Build for the ios version using<EMAIL_ADDRESS>Textarea, toolbar touch does not work, user has to double tap for any action.

I will not fix that in v2 so if you need that, you should try another WYSIWYG.
I keep this issue in mind for v3.


Force a tab to start at a certain scroll position

Hey(once again), I was trying to force a tab to always start at a certain scroll position, this is a really specific behavior, what I tried to do was on the indexChange call the scrollTo on that tab to place it on the position where I need, example
      onIndexChange={(onChangeData) => {
            const {tabName} = onChangeData;
            if (tabName === TabKey.MAP) {
              (mapRef.current as ScrollView).scrollTo({
                y: IMAGE_SLIDER_HEIGHT - HEADER_BAR_HEIGHT,
                animated: true,
              });
            }
          }}

This works great for the current tab but the others tab don't sync their position properly, should I call another function or just update some value from the context? Thanks once again

This should be fixed by #93, and #99 also makes it simpler.

@andreialecu Hey, nice to know, while trying to debug it I noticed that this only occurs if snap is enabled


Stuttgart ECP with spin-orbit terms

This pull request add the ECPs that contains spin-orbit ECPs from the diracprogram repository which is supposed to come from the stuttgart group.
The ECPs for element 119 and 120 are ignored since these are not added as supported elements in PySCF.
I added them explicitly because the basisset-exchange website don't have support for these spin-orbit ECPs.

@bogdanoff do you think the new database good to merge?

Yes, I think it is ready to be merged.


drive: improve directory notifications in ChangeNotify

What is the purpose of this change?
When moving a directory in drive, most of the time only a notification for the directory itself is created, not the old or new parents.
This tires to find the old path for the changed directoy in the dirCache and the new path with the dirCache of the new parent, which can result in two notifications for a moved directory.
Was the change discussed in an issue or in the forum before?
It is somewhat related to #2006, but affects directories instead of files.
Checklist

[x] I have read the contribution guidelines.
[x] I have added tests for all changes in this PR if appropriate.
[x] I have added documentation for the changes if appropriate.

[x] I'm done, this Pull Request is ready for review :-)

Thank you :-)


add support for scalar request bodies in php

see #1535
see #1560
see https://github.com/microsoft/kiota-abstractions-dotnet/pull/19

closed in #1937


Encode bytes type feature properties using base64

Resolves #1262, which I discovered when trying to convert https://github.com/OSGeo/gdal/blob/master/autotest/ogr/data/parquet/test.parquet to GeoJSON. This bug has been lurking for a while.
@mwtoews what do you think?
@jorisvandenbossche what's the pyogrio approach to serializing bytes in GeoJSON?

what's the pyogrio approach to serializing bytes in GeoJSON?

That's a good question, I don't think we already support this.
We don't have custom JSON serialization, and so only support it when writing using the GeoJSON driver. And our writing code starts from numpy arrays, and anything that is not in the list of mapped dtypes will either fall back to using OTFString type (when it is numpy object dtype) or raise a not-implemented error.
When starting from a geopandas dataframe, bytes will be stored in object dtype, and thus we currently write a "string repr" of the python bytes object ("binary": "b'\\x00\\x01'", not particularly useful IMO)
When using ogr2ogr, it raises a warning about it: Warning 1: The output driver does not natively support Binary type for field binary. Misconversion can happen. -mapFieldType can be used to control field type conversion., and then the result actually shows "binary": "0001" (which is the hex encoded version, I think?)
Checking with a quick patch to pyogrio to write a column of bytes to OTFBinary using OGR_F_SetFieldBinary just by passing the python bytes object, it seems that GDAL automatically does this? It also results in a GeoJSON file with "binary": "0001" (although without raising the warning, so that warning seems to be custom in ogr2ogr)
I assume that the GeoJSON driver will call GetFieldAsString on each Field value, and this calls CPLBinaryToHex in case of OTFBinary type.
So in summary, I think if we would add support in pyogrio, we would let GDAL do its thing, and thus use hex encoding and not base64 encoding.


bump version

@jameslamb could you update R's version accordingly? you can create a new PR if needed.

We don't necessarily know that the next release will be 3.0.1 instead of 3.1.0, right?
What do you think about the convention where the development version is like <IP_ADDRESS>99 (newer than 3.0.0, older than any future release we do with a 3-part number), and then we change to 3.0.1 or 3.1.0 based on what is new?
If any new features are added between now and the next release, then that release should be 3.1.0. If it is only maintenance tasks, 3.0.1

I like the proposal. With that, we can distinguish the dev and release versions.

After merge this, we can start to merge the blocked PRs about new features.

I'll update the R version right now and make a PR into this one

I can also upload the R artifacts to the 3.0.0 release manually tonight

created #3345


Add config variable to print integers as hex

Is your feature request related to a problem? Please describe.
In some domains, decimal integers are hardly ever used and most values only make sense when examined as hex/octal/binary. Think bit flags, special magic numbers like 0xdeadbeef, etc. bpftrace always prints ints out as decimal.
A very common action (for me at least) is to print out the fields of some structure. #2557 is amazing in that regard, but because it prints out all integer-y arguments as decimals I ended up not using it anywhere.
Describe the solution you'd like
Add a new config variable that controls the default formatting of integer types, globally, everywhere.
Describe alternative solutions or features you've considered
I've settled on running bpftrace scripts through cpp(1) first, and using an X-macro like pattern to define structures, which allows me to generate code that "visits" every field and print it out with printf("%x"). Resulting code has additional moving parts (cpp) and ends up being about 2x larger than it should be.

This looks like a useful feature. I think that it would be limited to the print builtinl, right?
Anyways, it should be quite easy to add a new config option like that.

I think that it would be limited to the print builtinl, right?

Yes. There's two places where I'd really love to see this:

print(*$some_struct_ptr);
@[$some_int] = $some_other_int; print(@);

IMO (1) is 90% of the issue, and the $some_int part of (2) is another 9%. For $some_other_int, I'm guessing consistency is the best choice so same rules as well?
For everything else, you can use printf() and specify the format manually.
Another alternative might be to pass an additional argument to print() to choose how to format ints for that call only?

Another alternative might be to pass an additional argument to print() to choose how to format ints for that call only?

I had this thought as well but it map printing already has additional arguments top and div. That's not to say we can't add another one but maybe it's just easier to have a config var.

It would be nice to be able to control this individually for each print() call, but I do see the issue with too many arguments.
Just throwing out an idea that I haven't really thought through, but what if we introduced named arguments, e.g.:
print(@mymap, top=5);
print(@mymap, fmt=hex);

(maybe we could also use it for async map printing: #3028)

And maybe the up-front map declaration syntax could also somehow specify how to print the keys/values: #2954.

what if we introduced named arguments

Yes, love this idea. I think we should try to generally move in this direction. Positional arguments often end up being just a pain for backward compatibility and are just less easy to grok.
That being said I think a config might still be good for this particular use case to reduce repetition if there are multiple print statements.

And maybe the up-front map declaration syntax could also somehow specify how to print the keys/values: https://github.com/bpftrace/bpftrace/issues/2954.

IDK. I'm less keen on this idea just because the printing of maps seems separate from defining the map itself. It also just seems like a strange middle ground between a global config and a local print that specifies the print style in an named arg.

Also related: #2952, which describes a way in which maps can be printed in hexadecimal now.

Thinking about it some more, IMO the best default behavior would be to print unsigned types as hex, while signed types get printed as decimal. That would be too much of a breaking change for actual defaults, but a config variable that turns on that behavior gets you the best of all worlds.

Just a couple of thoughts on what was said in this thread:

what if we introduced named arguments

I like the idea. Also, it would make it easier to allow optional parameters to user-defined functions, if we want to add them one day.

And maybe the up-front map declaration syntax could also somehow specify how to print the keys/values: https://github.com/bpftrace/bpftrace/issues/2954.

IDK. I'm less keen on this idea just because the printing of maps seems separate from defining the map itself.

Agreed with @jordalgo here. The printing of maps should be independent from the map itself.

Thinking about it some more, IMO the best default behavior would be to print unsigned types as hex, while signed types get printed as decimal. That would be too much of a breaking change for actual defaults, but a config variable that turns on that behavior gets you the best of all worlds.

I would avoid having a different default behaviour for signed and unsigned types.
Overall, I'd go with the config option for now. I'd suggest something like print_int_format with possible values either from an "enum" ("dec", "hex", "oct", ...) or with a printf-like specifier. Then, we could add it as an optional print param once we introduce calls with named arguments.

Bear in mind that there are already ways to print integers as hex in the given use-cases, they just take a bit more manual work with printf (a function designed for formatted printing).

Yeah, but when you want to print a huge struct (task_struct for instance), you really don't want to give the full printf specifier. In addition, it won't be portable between kernel versions.


Adding MKL matmul op

Adding build, op and registration for the MKL matmul op.

Can one of the admins verify this patch?

Looks good. As discussed offline, rmlarsen's comment will be addressed in a separate PR.

@tensorflow-jenkins test this please

Please fix the buildifier error mentioned in https://ci.tensorflow.org/job/tensorflow-pull-requests-sanity/3098/console and we can retest.  Thanks!

Ran buildifier on tensorflow/core/BUILD, tensorflow/core/kernels/BUILD and pushed the changes

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please

Weird, I'm seeing the following now:
ERROR: missing input file '//third_party/mkl:libmklml_intel.so'.

ERROR: /workspace/third_party/mkl/BUILD:11:1: //third_party/mkl:intel_binary_blob: missing input file '//third_party/mkl:libmklml_intel.so'.

I think this error should appear if you build with --config=mkl while not enabling mkl when you configure (currently it is disabled in the configure file). Can you confirm if that is the case?

Where does this PR stand currently? @vrv  Can you describe what configure and build settings you used when you got the error you mentioned 5 days back?

I'm just pointing at the test results... click on "details' and then 'console log" for the relevant failing tests.

Previously, we were not testing with "bazel test" in our setup so we could not reproduce the error earlier. Now, I updated the third_party/mkl/BUILD to fix the test failures due to missing MKL libs

@tensorflow-jenkins test this please

Jenkins, test this please.


Assumptions - Automated tests for the code structure of the TypeScript compiler

This library is based on a lot of assumptions about the TypeScript library.
Take the following example property:
prop: string;

In certain parts of this library, no compile error would be thrown if the above type were changed to:
prop: string | number;

It would be good to have automated tests to make sure certain parts of the TypeScript compiler haven't changed. This could be done using this library and it would be very easy to do.

Would be nice, but closing because I don't think it's worth it at the moment. Maybe in the future.

I've realized the best way to handle this is to assign the compiler type to a variable that is explicitly typed. For example:
const compilerNameNode: ts.PropertyName | undefined = this.compilerNode.name;

What's discussed in this issue isn't needed because when the compiler type changes then the explicit type will throw an error.


Automated cherry pick of #6679

Cherry pick of #6679 on cloud-ga.
/cc  @nickmisasi

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers


Documentation still vague about pagination of relational data

As asked before here, https://github.com/json-api/json-api/issues/1291, the answer given is still pretty vague, and the documentation is still unclear.
In the sentence
| Any pagination links in a relationship object MUST paginate the relationship data, not the related resources.
What is the "relationship data" and what is the "related resource"?
If we assume "Bar" is the "relationship data" - do we just show the first, next and last pagination links and call it a day?
Or is it trying to say we have to be able to call /foo/123?page[number]=3 to get Foo with page 3 of Bar?
Or, is the "relationship data" something altogether? (perhaps /foo/123/relationship/bar ?)

Relationship data is the data included as resource linkage. I see that it is confusing that the term relationship data is used instead of resource linkage at two places. It is only indirectly specified in the fetching relationships section:

A server MUST support fetching relationship data for every relationship URL provided as a self link as part of a relationship’s links object.

The term related resources is used in the specification at several places. I think it is well defined as resource objects, which represent resources referenced by a relationship of another resource. This could be done either by a related resource link or resource linkage. I don't see clarification needs for this term.
For pagination it means that pagination links belong to the self link of a relationship. Not to its related resource link (related). An example may look like this:
{
  "type": "posts",
  "id": "7",
  "relationships": {
    "comments": {
      "data": [
        { "type": "comments", "id": "1" },
        { "type": "comments", "id": "2" },
        { "type": "comments", "id": "3" },
        { "type": "comments", "id": "4" },
        { "type": "comments", "id": "5" },
      ],
      "links": {
        "related": "/posts/7/comments",
        "self": "/posts/7/relationships/comments",
        "next": "/posts/7/relationships/comments?page[number]=2",
        "prev": null,
        "first": "/posts/7/relationships/comments",
        "last": "/posts/7/relationships/comments?page[number]=5"
      }
    }
  }
}


Update mocha_v2.4.x.js

Mocha: before and after methods can have description.

Can you add a couple of tests that show both forms of these functions working?

Ok try add tests, now.

@jeffmo some crazy error in CI after me. Please check it and give advice.
Can not imagine what I'm done wrong.
Also I am confused with spaces. Can not understand logic should I
do description:string
or description : string.

some crazy error in CI after me. Please check it and give advice

I commented inline. It looks like you've asserted expectations of an error in places where Flow isn't actually erroring.

should I do description:string or description : string.

I generally do description: string

This hasn't been updated for quite a while and I can't add commits to the PR.
If this is still relevant please submit a new PR.


Issue/3470 add global variable (#4391)

Pull request opened by the merge tool on behalf of #4391

Merged into branches iso5 in cc88279cf912792911c32531f95653a81f4b6ab9


dissapear

Mod Version
2.0.0
Client Log
No response
Crash Report (if applicable)
No response
Bug Description
throphy vanishes if broken with anything else but pickaxe
Steps to Reproduce
place
break with hand
trophy gone
sad player
Please Read and Confirm The Following

[X] I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
[X] I have confirmed this issue is unique and has not been reported already.

trophies are meant to be broken with a pickaxe, but i'll make it so it doesnt require one to break them

wounderfull!


Multi view history

Introducing a change history implementation allowing for multiple simultaneous views.
This is intended for applications having multiple view modes,
that should retain the change history when switching modes.
At the same time this forms a good basis to bring real-time editing further.

Incredible.


core: docstring update

Added missed docstrings. Updated docstrings to consistent format.

@baskaryan Thank you!


TabViewItem header hit test/mouse over problems in 1.6.0 experimental 2

Describe the bug
The hit test and mouse over areas for tab view item headers and their buttons are incorrect. Please see the attached video.
The bug is only evident when there is an even number of tabs and the display scaling is set to 125%. It isn't reproducible at 100% scaling, I haven't tried other scale factors.
https://github.com/microsoft/microsoft-ui-xaml/assets/28826959/fb4fd2db-f064-4db5-ab01-886622ca9f81
Steps to reproduce the bug

Build the attached solution.
Set display scale to 125%.
Open an even number of tabs.

HitTestIssue.zip
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.6 Experimental 2: 1.6.240701003-experimental2
Windows version
Windows 11 (22H2): Build 22621
Additional context
I also experienced similar bugs in my real app in the tab's contents, not just the tab item headers. For example the expander drop down buttons could be clicked when the mouse was outside of any part of it's expender. I suspect it's a common cause.

This is a known issue in both 1.6-experimental1 and experimental2. I believe the fix was just checked in, but leaving active for the fix developer to verify.

Yes, this should be fixed in the newest version of WindowsAppSDK.


Bug: changelogs not marking viewed under certain circumstances

If you have a module that has a changelog you haven't marked viewed, and you uninstall said module before you get around to it, it gets stuck: https://gfycat.com/OddConsiderateHorsefly
That gif is from a pf2e world, and as you can see there's a starwarsffg module in there; I do have that module installed still, and that's an error on its dev's end, but also maybe an edge case you want to account for, because after recording the above, I loaded the appropriate world, and it worked correctly: https://i.imgur.com/JCvKe74.png
edit: so I was wrong, that star wars module does have its' settings correct, and wasn't showing on the list in the pf2e world. So that's probably less uncommon than I was thinking, and would happen any time a module for another system than the one your current world is has updated.
edit2: a 'reset changelogs' does remove the old entries, so that's working fine, and after the reset it didn't show the star wars module in the pf2e world, but did correctly show it on going back to the star wars world. I'm vaguely remembering that module may have updated its manifest link recently? that could have broken something?

I will add a check when updating changelogs that I loop through the previously tracked changelogs and remove any that don't exist or no longer have a file in their directory.

This should be resolved in the latest update, if not please re-open this issue


feat(core): Added SASL DIGEST-MD5 support

This PR adds support for DIGEST-MD5 SASL authentification to Zookeeper.
Usage is as same as before except that we can now use the 'sasl' mechanism:
from kazoo.client import KazooClient
zk = KazooClient(hosts='<IP_ADDRESS>:2181', auth_data=[('sasl', 'user:password')])
zk.start()
...

I mainly followed Zookeeper's client-server mutual authentication documentation for this implementation.
It uses the pure-sasl library to manage the SASL challenge. It is a very well documented library to use for SASL authentification and can also be used if we want to add a GSSAPI support for Zookeeper.
Some tests also have been added.
Thank you
Stephen

Thank you!
I will update all my PRs next week.

@jeffwidman I just updated this PR following your advises. In case pure-sasl library is missing, the client will fall back connection to zk without any auth. Example:
>>> zk.start()
2018-10-01 12:02:14,215 - kazoo.client - INFO - Connecting to <IP_ADDRESS>:2181
2018-10-01 12:02:14,216 - kazoo.client - DEBUG - Sending request(xid=None): Connect(protocol_version=0, last_zxid_seen=0, time_out=10000, session_id=0, passwd='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00', read_only=None)
2018-10-01 12:02:14,752 - kazoo.client - WARNING - Pure-sasl library is missing while sasl authentification is configured. Please install pure-sasl library to connect using sasl. Now falling back connecting WITHOUT any authentification.
2018-10-01 12:02:14,752 - kazoo.client - INFO - Zookeeper connection established, state: CONNECTED

--- Zookeeper side
2018-10-01 10:02:14,217 [myid:] - INFO  [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:NIOServerCnxnFactory@215] - Accepted socket connection from /<IP_ADDRESS>:44144
2018-10-01 10:02:14,218 [myid:] - INFO  [NIOServerCxn.Factory:<IP_ADDRESS>/<IP_ADDRESS>:2181:ZooKeeperServer@948] - Client attempting to establish new session at /<IP_ADDRESS>:44144
2018-10-01 10:02:14,752 [myid:] - INFO  [SyncThread:0:ZooKeeperServer@693] - Established session 0x10000619e220005 with negotiated timeout 10000 for client /<IP_ADDRESS>:44144


fix: prisma --version (#13737)

Essentially, PR #13737 without breaking ecosystem-tests.
Closes https://github.com/prisma/prisma/issues/14014.

Most likely, an invocation of these lines from inside pkg caused a segmentation fault:
export async function getEngineVersion(enginePath?: string, binaryName?: BinaryType): Promise<string> {
  if (!binaryName) {
    binaryName = getCliQueryEngineBinaryType()
  }
  // >>> from here:
  enginePath = await resolveBinary(binaryName, enginePath)
  if (binaryName === BinaryType.libqueryEngine) {
    await isNodeAPISupported()

    const QE = load<NodeAPILibraryTypes.Library>(enginePath)
    return `libquery-engine ${QE.version().commit}`
  } else {
    // ...
  }
}

The previous code in https://github.com/prisma/prisma/pull/13737 assumed that the engine version could be read in a logical try / catch expression, resulting in either a string, or an error. Apparently, if enginePath is undefined, the execution of the above lines fails badly, causing the require defined inside load to read memory it's not supposed to read, thus causing a segmentation fault.


AJ-1011: generated server

Based on feedback from #353, this PR adds our generated server-side code to git, so we have it in the codebase and we can track changes to it.
In this PR, the following files were autogenerated (so you can choose to skip review of them if desired):

ImportApi
ImportRequestServerModel

I wonder if we should mark the files as generated (rather than ignored) so GitHub can suppress them on initial render, but make them available for optional review, as described in https://medium.com/@clarkbw/managing-generated-files-in-github-1f1989c09dfd and https://medium.com/@clarkbw/managing-generated-files-in-github-1f1989c09dfd
Note...I've never done this, so no idea how usable the outcome would be.

@jladieu I've updated to 1) add back the timestamp, and 2) mark those files as generated in .gitattributes, good call on that.


sentestingkit/sentestingkit.h not found xcode 7

Today,I update my xcode to xcode7.0.I try to run this project,but can't do that.Can you help me?

Hmm, I'm sorry to hear that. I'll investigate and get back to you.

I've reproduced the issue, and I'm working on a fix.

OK, I've pushed a fix for that. Thanks for letting me know if wasn't working – please let me know if you run into any other issues!

Thanks.It run success.

Great!


As a user I want to able to see the links for Social Media (Facebook, Twitter and LinkedIN)

Acceptance Criteria

[ ] Links are not yet provided Facebook, Twitter and LinkedIN

@partini  Please see below links for Social Media:
Facebook: https://www.facebook.com/BngladeshPeaceObservatory/
Twitter: https://twitter.com/PeaceObservator
Google Plus<EMAIL_ADDRESS>No need for LinkedIn


RtmRegisterEntity Access violation

Summary
I try to impl this example https://learn.microsoft.com/en-us/windows/win32/rras/register-with-the-routing-table-manager
and I get
Exception has occurred: W32/0xC0000005
Unhandled exception at 0x00007FFCFACEBCE4 (rtm.dll) in clash-rs.exe: 0xC0000005: Access violation writing location 0x0000000000000000.

I also get a bit confused about windows::Win32::NetworkManagement::Rras::RTM_ENTITY_ID
https://microsoft.github.io/windows-docs-rs/doc/windows/Win32/NetworkManagement/Rras/struct.RTM_ENTITY_ID.html
and the embedded Anonymous, RTM_ENTITY_ID_0_0 stuff.
is that due to the def is a union https://learn.microsoft.com/en-us/windows/win32/api/rtmv2/ns-rtmv2-rtm_entity_id
typedef struct _RTM_ENTITY_ID {
  union {
    struct {
      ULONG EntityProtocolId;
      ULONG EntityInstanceId;
    };
    ULONGLONG EntityId;
  };
} RTM_ENTITY_ID, *PRTM_ENTITY_ID;

and that is how it looks like mapping to Rust?
I'm not sure if it's related to the pointer issue
Crate manifest
[target.'cfg(windows)'.dependencies]
windows = { version = "0.58", features = [
    "Win32_Networking_WinSock",
    "Win32_Foundation",
    "Win32_NetworkManagement_Rras",
]}

Crate code
let address_family = match dest {
        IpNet::V4(_) => AF_INET,
        IpNet::V6(_) => AF_INET6,
    };

    let rtm_reg_handle: HANDLE = null_mut();
    let mut rtm_entity_info = RTM_ENTITY_INFO::default();
    let mut rtm_regn_profile = RTM_REGN_PROFILE::default();

    rtm_entity_info.RtmInstanceId = 0;
    rtm_entity_info.AddressFamily = address_family.0;
    rtm_entity_info
        .EntityId
        .Anonymous
        .Anonymous
        .EntityProtocolId = PROTO_IP_RIP.0.try_into().unwrap();
    rtm_entity_info
        .EntityId
        .Anonymous
        .Anonymous
        .EntityInstanceId = protocol_id(
        PROTO_TYPE_UCAST,
        PROTO_VENDOR_ID,
        PROTO_IP_RIP.0.try_into().unwrap(),
    );
    let rv = unsafe {
        RtmRegisterEntity(
            &mut rtm_entity_info,
            null_mut(),
            None,
            false,
            &mut rtm_regn_profile,
            rtm_reg_handle as *mut _,
        )
    };

    if rv != ERROR_SUCCESS.0 {
        let err = unsafe { GetLastError().to_hresult().message() };
        error!("failed to register entity: {}", err);
        return Err(new_io_error(err));
    }

This sounds more like an API question. Might I suggest https://stackoverflow.com/search?q=windows-rs as I'm not personally familiar with this API.

thanks @kennykerr I posted on so https://stackoverflow.com/questions/78929446/rtmregisterentity-access-violation
however regarding the union mapping, is the _0_0 suffix somehow by design, is this how people should pass unions to winapi, do you have examples demonstrating APIs using a union?
tysm!

You can have a look at the overlapped sample:
https://github.com/microsoft/windows-rs/blob/9f5ec21529ec0530ac16e9a1c5d16eb8bb290535/crates/samples/windows/overlapped/src/main.rs#L24-L34

The challenge is the C, unlike Rust, supports nested structs. So this is a workaround to express that in Rust.

i see isee .thanks for the explanation!


Please provide at least 4 concrete characters at the beginning of the pattern

This is the output of the console application:
Is 64bit process: True
Please provide at least 4 concrete characters at the beginning of the pattern
Invalid user pattern 1-\d\d\d-GOOG-411
Press any key to exit.
Is this result expected?

If your talking about the Tesseract.ConsoleDemo sample app no it should print out contents of a sample image included in the demo (amongst some other diagnostic information). I just ran the demo, from the master branch, and it steamed to be working fine.
If your talking about your own app then I guess that depends on your app though I doubt it's desired :)
I do loosely recall getting similar error messages when I was playing with custom user pattern that were incorrect. However if your using the stock language files make sure they're from the same version of tesseract (3.02 for the latest release of this library).

I mistakenly started the "Tesseract.Tests.Console" project which gave these errors. Then I realized that there is the "Tesseract.ConsoleDemo" which worked fine.
Thx


[Bug]

Description
Currently when website is seen in mobile the toggle button appears in hamburger -

It should be in navbar instead of hamburger component like below(a rough idea) -

Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Pls complete your assigned issue first @PratikMane0112


Broker LoadFactor CPU NaN

We've found that brokers are saving loadFactorCPU as NaN in zookeeper path /loadbalance/settings/load_factor_cpu, and think this is probably messing load balancing.
{"loadFactorCPU":"NaN"}
How can this end up being NaN? What consecuences can this bring?
PS: I've also seen some other fields in /loadbalance/brokers/* with NaN, such as allocatedCPU and preAllocatedCPU

https://github.com/apache/incubator-pulsar/pull/2618

this should be resolved in the next realease

This is fixed by #2618


api: reindex doesn't work if the queue is not initialized

Problem:
If, after install invenio3, I run:
invenio3 index reindex --yes-i-know
invenio3 index run

It doesn't index the records because the queue is not previously declared.
What we need to do is declare the queue the first time we initialize the system.
Solution proposed:
We can add a signal inside the invenio-search cli init and destroy; in the same time, in invenio-indexer register a signal to initialize and destroy the queue every time the indices are created or destroyed.

cc @lnielsen @jirikuncar

IMHO reindex could create and purge the queue.

Declaring the queue is comparable to creating indexes in ES or tables in the DB, so I don't think reindex would be the right place.

@lnielsen I am fine with adding new signals. There should be another way to create/purge the queue without creating/dropping all indices.

Proposal

invenio3 index queue init
invenio3 index queue purge
invenio3 index queue destroy


Provide ability to disable ssl verification

Sometimes we do not have luxury of valid ssl certificates and should use self-signed for temporary testing purposes.
This PR enables the functionality to disable ssl verification in torpedo run

@dprince  can we merge it ?

@ytsarev yes, thanks for this


Fiona 1.7.2 for windows

Theres a Fiona 1.7.2 for windows?
Install package?
Thanks

No @paulopires16 there are no official Windows packages at this time. Maybe in the future, but I simply do not have the required Windows know-how.


[BUG] Postgres Exporter upgrade broken - no vars generated during upgrade

Describe the bug
Postgres exporter upgrade fails on task [postgres_exporter : Include specification vars from postgres_exporter role]:
2022-01-13T18:37:24.2525347Z[38;21m18:37:24 INFO cli.engine.ansible.AnsibleCommand - TASK [postgres_exporter : Include specification vars from postgres_exporter role] ***
2022-01-13T18:37:24.4826409Z[31;21m18:37:24 ERROR cli.engine.ansible.AnsibleCommand - fatal: [ec2-1-1-1-1.eu-west-1.compute.amazonaws.com]: FAILED! => {"ansible_facts": {"exporter_vars": {}}, "ansible_included_var_files": [], "changed": false, "message": "Could not find or access 'roles/postgres_exporter/vars/main.yml'
Searched in:
\t/shared/build/12to13armawcecalico/ansible/roles/postgres_exporter/vars/roles/postgres_exporter/vars/main.yml
\t/shared/build/12to13armawcecalico/ansible/roles/postgres_exporter/roles/postgres_exporter/vars/main.yml
\t/shared/build/12to13armawcecalico/ansible/roles/postgres_exporter/tasks/upgrade/vars/roles/postgres_exporter/vars/main.yml
\t/shared/build/12to13armawcecalico/ansible/roles/postgres_exporter/tasks/upgrade/roles/postgres_exporter/vars/main.yml
\t/shared/build/12to13armawcecalico/ansible/vars/roles/postgres_exporter/vars/main.yml
\t/shared/build/12to13armawcecalico/ansible/roles/postgres_exporter/vars/main.yml on the Ansible Controller.
If you are using a module and expect the file to exist on the remote, see the remote_src option"}

The reason for this is that in unrelated PR #2819 postgres exporter has been removed from roles with defaults 😢
https://github.com/epiphany-platform/epiphany/pull/2819/files#diff-c347f852c48b4116fd8f4282377ec7c782e8301b32a6650e9ea8072ed40237f4L72
Thanks @cicharka for investigating the issue.
How to reproduce
Steps to reproduce the behavior:

deploy v1.2 cluster with PostgreSQL component enabled
execute epicli upgrade to v1.3

Expected behavior
Upgrade should be successful
Config files
Environment

Cloud provider: [all]
OS: [all]

epicli version: [v1.3 + develop]
Additional context

DoD checklist

[ ] Changelog updated (if affected version was released)
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Case covered by automated test (if possible)
[ ] Idempotency tested
[ ] Documentation updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Backport tasks created / doesn't need to be backported

:heavy_check_mark: Upgrade of Postgres Exporter works fine now. Tested upgrade from v1.0.1 and v1.2.0.


I tried the webpack-closure-compiler aka PLOVR

Solved
This was easier than expected, it's not really a java issue, the error was javascript that can not run java.
pacman -S jdk8-openjdk
Symptoms( my original post )

Do you want to request a feature or report a bug?
Probably bug

Sad :-(
What is the current behavior?
java error
If the current behavior is a bug, please provide the steps to reproduce.

https://asciinema.org/a/7gbdlwkvzurbqaqglmohsxofu

https://asciinema.org/a/7gbdlwkvzurbqaqglmohsxofu

webpack-closure-compiler
What is the expected behavior?
PLOVR compiled output
If this is a feature request, what is motivation or use case for changing the behavior?
Have a real compiler run for production deployment.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
FF Dev Ed 54.0a2 (2017-03-19) (64-bit)
$ node -v
v7.7.3
$ uname -a
Linux x240webshop 4.9.8-1-ARCH #1 SMP PREEMPT Mon Feb 6 12:59:40 CET 2017 x86_64 GNU/Linux
Solved
This was easier than expected, it's not really a java issue, the error was javascript that can not run java.
pacman -S jdk8-openjdk

It looks like this issue is not directly related to this project. We try to only keep issues directly related to this project in the issue tracker. Therefore I'm closing this issue.
Please file the issue on roman01la/webpack-closure-compiler.
You can easily copy your text if you click on "edit" on this issue. Also make sure to follow the issue requirements of the target project when pasting this issue.

@sokra it seems Closure Compiler breaks harmony on ADVANCED settings: it can't optimize an "a" getter correctly. Can you direct to me to the part that is responsible for this? Seems like a quick fix.

Ok, it's this part: https://github.com/webpack/webpack/blob/aecc297c509f08f95148ccb2915a2b9ff3ee5fa3/lib/MainTemplate.js#L148
So there's a getter function named "a" that get's defined on all harmony modules and gets called via dot notation later. Now I only need to find where webpack does this.


Does not overwrite line in sakura terminal

Hi guys,
Thanks for this package. It is really useful.
I recently switched from urxvt to sakura terminal. In urxvt, the spinner successfully overwrote the previous line. In sakura, it did not. It continuously writes new lines.
I am just beginning in go, but from what I can tell, the erase function essentially backspaces for each character in the previously printed line. Would it be better if we just used fmt.Fprintf(s.Writer, "\033[2K")?
\033[2K works in Sakura in other programs that use it.
More info on terminal escape codes
If you think this would work, I can PR.
Thanks!

Thank you very much for this issue.  If you want to put a PR together for testing and discussion, that'd be awesome.

Huh. Running the tests in sakura, it stays on the same line. Running my project in sakura, it makes a bunch  of lines. Running my project in urxvt, it stays on the same line.
How do I use my local fork of spinner in my go project?

If you've cloned it into your ${GOPATH}, you should be able to just reference it from another project.

Will reopen if tests are worked on to make passing in #38


Support hard links

At the moment, restic saves enough meta data to restore hard links, but this is not implemented yet.

More context: When backing up a directory that contains two or more files with the same inode (on the same filesystem), restoring the backup will create two files with identical content (rather than only one file and hardlinks to that file's inode).
This issue can be closed when there is a config option (enabled by default I would suggest) that is smart enough to only create one inode when restoring a backup like this.
Need to think about the rare corner case of inodes being identical by coincidence (because the source files were on different file systems -- marginally related to https://github.com/restic/restic/issues/47).

We could add stat.Dev to the meta data, that should uniquely identify the device containing the file:
struct stat {
    dev_t     st_dev;         /* ID of device containing file */
    [...]
}

[...]
The st_dev field describes the device on which this file resides.  (The
major(3) and minor(3) macros may be useful to decompose the device ID in this
field.)

(from stat(2))

os.SameFile might be useful

Nice method, I wasn't aware of it. Unfortunately it won't help. In order to detect hard links during backup, we need to maintain a list of all files (tuples of (inode, dev)) seen so far.

For *nix, wouldn't it be sufficient to maintain a list of only the files for which the value of nlink_t in struct stat is greater than 1?

I think we already have all the metadata recorded, but the restore part is missing.

What I have right is support for hard links using the restic restore command.
It requires a repository change since the dev id of the file has to be stored to resolve inode collisions (two files with the same inode id but on different file systems).
Also, the solution supposes that all hard links for a file are included in the backup and are restored. If not, a warning is raised during the restore that hard links are missing.
I also had a look to see if hard links can be supported by restic mounts.
So far, I have not found an efficient solution.
During file creation, a file plus all the hard links have to be created. For that purpose, there should be a list of all files with hard links. One option could be to traverse the back up tree, but this time consuming. Another option could be to store a map of files and hard links during the backup already.

Let's start with archiving/restoring hard links, and then solve the fuse mount. Please submit a pull request so we can discuss the code :)

FYI: PR #763 is almost ready.

Aaaand it has been merged! Thanks a lot to @jgfrm!

Excellent!


Code sample: add Java version

This PR adds the Java version of the code sample in chapter 17.18 Subcommands and default values.

Thank you for the contribution!


haskell generic-builder: Limit usage of --extra-framework-dirs on Darwin for compat

Motivation for this change
I have no idea why this appears  to be  a Darwin only thing. It would be nice to investigate that.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Best to just unbreak Darwin now. We can improve the condition later.

Yeah.

Wait what 😮. This condition makes completely no sense to me, can you, please, elaborate? 😕
This appears to be a macOS-only thing, so why is it !buildPlatform.isDarwin? Why does the version of ghc matter? I guess, my question can be summed up as “Why not simply buildPlatform.isDarwin?”

I guess I just don’t understand what was the original issue.
Current condition triggers on Linux unconditionally (??? I suppose this option does nothing there and even $p/Library probably never exists on Linux) and on Darwin with recent versions of GHC. So if the issue was about older versions of GHC (actually, Cabal, I suppose, as this is a Cabal flag?), then shouldn’t the condition be buildPlatform.isDarwin && versionAtLeast nativeGhc.version "8.0"?
@Ericson2314

@kirelagin This is specifically for cross compiling, the flags where added for linux->darwin and this fixes native darwin.

Why not `hostPlatform.isDarwin && versionAtLeast nativeGhc.version "8.0" then?

Do you mean !hostPlatform.isDarwin or targetPlatform.isDarwin?

the flags where added for linux->darwin and this fixes native darwin

Again, the problem probably is that I do not understand the original issue. How stopping to include frameworks in certain cases can help with a cross-compilation to Darwin, when Darwin is exactly where these frameworks are needed?
I see how this could fix Darwin -> Linux compilation if buildHost libraries were included and the linker tried then to link a Linux binary to Darwin frameworks.
I now see that those frameworks are needed for host only, so, then, I think the condition should be hostPlatform.isDarwin, because we want to link with macOS frameworks when we are building a binary for it, regardless of the build platform (and of the target platform, I think).

@kirelagin Yes the condition is weird AF. I was gonna make it unconditional with the understanding that it would have no effect on Linux anyways. But then it failed with the Canal that came with GHC 8 on Darwin for unknown reasons. I think that was Cabal 1.24 and I tried the flag on Linux and it was recognized! So I have no idea what's going on.


⚠ Bofrost.at has degraded performance

In 9f1ad5b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1828 ms

Resolved: Bofrost.at performance has improved in cd8e24d.


Feature idea: Character sub menu

Taking your forum advice and posting some feature ideas. Absolutely stunning work, thanks so much for the amazing mod.
Would be incredible to have a separate controller menu for "character":
Circular thumb-pad controls clothing state:
Press up removes top
Press down removes bottom
Press left removes bra
Press right removes panties
Trigger cycles through custom characters:
Each trigger pull automatically loads the next alphabetical character in your directory of PNGs

I like the idea of making a tool for changing the character state.
I wouldn't use the trigger for switching through the characters, though, since it's the button that is easiest pressed and it's hard to get back to your previous character. Perhaps it could be used in conjunction with the thumbpad, à la you can back and forth by pressing left or right while pressing the trigger.

Yeah, that actually sounds way better since the trigger/pad combo would allow you to cycle both forward and reverse through all the characters. Great stuff, thanks for the reply.
On Tuesday, May 31, 2016 2:40 PM, Eusth<EMAIL_ADDRESS>wrote:

I like the idea of making a tool for changing the character state.I wouldn't use the trigger for switching through the characters, though, since it's the button that is easiest pressed and it's hard to get back to your previous character. Perhaps it could be used in conjunction with the thumbpad, à la you can back and forth by pressing left or right while pressing the trigger.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Do you think this would be a possible addition to your next release? Changing through characters without having to drill down into the sub-menus would be great (and having quick access to clothing state). Regardless, thanks for all of your excellent work.


Recover 1

Recover Account Details
Success State:

Loading State:

Error State:

1 - On success there's a countdown timer - next PR?


Empty JPG Images on Raspberry Pi Zero & 3b

Hello,
as written in the topic, i dont get any images from my Arducam Mini 2MP. There are also two older ISSUES describing the same problem but didn't get fixed.
I tested it with two new camera modules and with a PI Zero and also PI 3 b. It is always the same error.

in the image it is to see that the code don't run through all states. there is no jpg header sent by the cam. when i look the MISO line with my oscilloscope I also see that the cam only replys 0x00 on the line.
I installed the driver like described in the readme.
I think there is an error in this driver for some reason.
can someone help?
regards

any ideas? i think there is a bug in this driver implementation for raspberry. can i provide more information in order to help?

Please use the source code from: https://github.com/ArduCAM/RaspberryPi/tree/master/SPI_Camera

@ArduCAM thank you really much for your help. unfurtunatly even this lib does not work really. I installed it like described in the Readme /Quick Install instruction. However when I run "sudo ./run_Arducam_Demo" nothing happens. no output, no open port 2002.
can you help again?

@ArduCAM I'm using pi zero and figured out that pi zero has the BCM2835, in this lib there is a base address defined for BCM2836. I changed the base periph address define to the 2835, however now I'm seeing this errors:

okay I found the mistake. in the lib the CS Pin is defined to 17 and i connected it to GPIO 8. changed it solved the interface error.


Allow custom response text on error

The result of onerror(xhr.response) was null, even when response text is present. By removing the onerror() call, this will correctly return xhr.response to the onerror function.

Can't merge this, it returns null so xhr.statusText is used by default. You can supply your own onerror function to return the xhr.response.

I can understand the idea of implementing a custom onerror function to do what I need to with the response object, but I'm trying to work with React-Filepond and no matter how I implement the onerror, the only solution that has worked for me is editing the request.onerror in filepond itself.
I attempted to put the custom onerror handler on the server prop itself, this was never invoked.

I tried using the onerror prop that is in the documentation, but as I tried to point out in the PR, only the xhr.statusText comes through. This displays 'Unprocessable Entity' correctly, but there is no access to the response or responseText, never mind the raw response object.

Finally, once updating the filepond's customFileProcessorFunction's onerror function to remove the called to onerror in this PR, which didn't seem to be overwritten in anyway (which I'm starting to think is an issue with react-filepond mapping the props correctly to the filepond instance being created), I was able to see my custom error message from my backend.

I'm just trying to wrap my mind around how to get this response body to my frontend. I've looked over several of the issues on react-filepond. I've seen that you keep saying that it is possible through the library, but I have not been able to figure it out for myself.
Maybe you can spell it out for me?
My only other thought would be setting the default action.onerror || (res => null) to action.onerror || (res => res) as it is with onload.
I hope your garden office is coming along well.

Thanks! We've torn down our old shed and construction of the new one should start next week.
I can't check the source now but I believe onerror doesn't propagate to the different server end points and needs to be set specifically on each one.
Like this (https://pqina.nl/filepond/docs/patterns/api/server/#object-configuration):
FilePond.setOptions({
    server: {
        url: 'http://<IP_ADDRESS>',
        timeout: 7000,
        process: {
            url: './process',
            method: 'POST',
            headers: {
                'x-customheader': 'Hello World'
            },
            withCredentials: false,
            onload: (response) => response.key,
            onerror: (response) => response.data,
            ondata: (formData) => {
                formData.append('Hello', 'World');
                return formData;
            }
        },
        revert: './revert',
        restore: './restore/',
        load: './load/',
        fetch: './fetch/'
    }
});

I see, so process would get its own onerror and if I needed another one for load I'd have to define one there as well. I'll give it a shot. Thanks for the detailed feedback.


Should we check the version of lua-resty-events?

In 1.6.2 there is a line:
local RESTY_EVENTS_VER = [[^0\.1\.\d+$]]

It says that the library only supports 0.1.x version of lua-resty-events.
Is it necessary? If lua-resty-events changes the version we will get a disaster.

Hmmm it looks like it was intentionally introduced by @locao in https://github.com/Kong/lua-resty-healthcheck/pull/118
I don't think there's an easy answer to this since we don't have good semver parser here.
Kong apparently already uses lua-resty-events in version 0.2.0. Did we get anny issues? If not then I think we can change it here manually for next release? How does it sound? @chronolaw
Latest lua-resty-events release: https://github.com/Kong/lua-resty-events/releases/tag/0.2.0
Changelog in kong that bumps up lua-resty-events to 0.2.0: https://github.com/Kong/kong/blob/release/3.4.x/CHANGELOG.md#dependencies

When lua-resty-healthcheck started to support both lua-resty-worker-events and lua-resty-events I choose to not keep the events library requirements in the rockspec, as one of these libraries would be installed just to fulfill the requirements and would never be used. The version requirement listed in the line quoted by @chronolaw was just a way to log to lua-resty-healthcheck users that any of these modules were required and none was available.
In my opinion, from the next release on we should remove all lua-resty-worker-events support (including tests), remove this version check in the code, and go back to control all requirements using the rockspec by adding lua-resty-events to it.
What do you think @nowNick @chronolaw?

Good answer, thank you @nowNick @locao.
Now lua-resty-events is 0.2.0, but in lua-resty-healthcheck we are using the compat module, which's version is still 0.1.x, so the version of lua-resty-events will not impact library.

I agree @locao - if we're not using lua-resty-worker-events and we won't provide new features with this runner we should probably drop it. However it might require major version bump, am I right? A change like this I think justifies 4.x.x?

@nowNick @locao , do we have any decision for it now?

@chronolaw @nowNick in my opinion:

add a lua-resty-worker-events deprecation warning to 3.x.x HEAD.
start a 4.x.x branch

remove all lua-resty-worker-events support (including tests)
remove the version check in the code
go back to control all requirements using the rockspec by adding lua-resty-events to it.

If there are no opposing views, I can create the required tickets on our backlog.