feat: improved the UX on the feeds page and scroll behaviour

Description
Issue: Currently, there is an issue where the highlight filters and user card scroll along with the content when scrolling through the feed. This behaviour is not user-friendly and can lead to confusion and a bad user experience.
Changes Proposed:
In this pull request, i addressed the scrolling behaviour to enhance the overall user experience and ensure a smoother and more intuitive interaction with the feed. The following changes have been implemented:

Fixed Position for Navigation Menu: The navigation menu is now set to have a fixed position as the user scrolls through the feed. This means that the navigation menu will remain visible at the top, offering users quick access to navigation options.

Sticky Position for Filters and User Card: The filters and user card sections are now set to have a sticky position as the user scrolls through the feed. This means that these elements will remain visible at their designated positions, offering users quick access to important information and controls without any disruption caused by scrolling.

Smooth Transition: To maintain a visually pleasing transition, i have incorporated a smooth scrolling effect when transitioning between different sections of the feed. This ensures that the user's focus remains on the content while seamlessly interacting with the filters and user card.

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Fixes #1353 and Fixes #1451
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Thank you for having your first PR; since this is a transition behavior can you add a video of the before and after? an image would not describe the PR.

Thank you for having your first PR; since this is a transition behavior can you add a video of the before and after? an image would not describe the PR.

Yea, I wanted to record one but my PC doesn't have an inbuilt screen recorder😔

LGTM 🍕 The only feedback that I have is that we need to minimize the items on the left and right side of the screen, but that is out of the scope of this. Just wrote it here for visibility purpose.

Yea I get your point
We could have a specific height and make the repository items scrollable by adding overflow-y-auto to it or reduce the sticky top position

For the recording you can Google, screen recorder and you will find few online recorders
I used this couple of time, https://www.screencapture.com/
And there chrome extension for that, if you like an open source alternative you can check:OBS, or OBS streamlabs
As for the sidebar items, I think a review from the team would be great to have another opinion.
Sent from mobile device

From: dev-phantom @.>
Sent: Sunday, August 6, 2023 11:36:06 PM
To: open-sauced/insights @.>
Cc: Abdurrahman Rajab @.>; Comment @.>
Subject: Re: [open-sauced/insights] feat: improved the UX on the feeds page and scroll behaviour (PR #1506)
LGTM 🍕 The only feedback that I have is that we need to minimize the items on the left and right side of the screen, but that is out of the scope of this. Just wrote it here for visibility purpose.
[image]https://user-images.githubusercontent.com/18273833/258662598-35d168e0-8482-48ce-8a90-4869b14829bb.png
Yea I get your point
We could have a specific height and make the repository items scrollable by adding overflow-y-auto to it or reduce the sticky top position
—
Reply to this email directly, view it on GitHubhttps://github.com/open-sauced/insights/pull/1506#issuecomment-1666962284, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AELNMKMTJ4FNGVXKRMAXI4TXT753NANCNFSM6AAAAAA3GCBCVQ.
You are receiving this because you commented.Message ID: @.***>

This looks good. We need to wait on #1490 to merge before this is merged.

It has been merged sir 🤔

Thanks @dev-phantom, this is good to go after the merge conflicts are resolved


Update resolution and overscan

Need to apply the same resolution and overscan settings to all tools including the loader.
"DisplayChip":
    {
        "width":264,
        "height":248,
        "maxSpriteCount":96,
        "overscanX":1,
        "overscanY":1
    },

All of the tools now share the same display chip settings.


Fix: Nav active fix

This pull request fixes #917 adds the Nav Active feature for mobile devices to enhance the user experience. The Nav Active feature ensures that the active menu item is visually highlighted when accessed on mobile devices, providing better navigation and usability.

hi, @priyankarpal  i made these changes as requested🙂


[BUG] Cloud Config User Data that was entered prior to clicking "create new" under User Data Template, disappears

Describe the bug
When creating a VM, under Advanced Options, Cloud Config User Data, if user is filling out Cloud Config information for that VM, if the user decides to click "Create New" under User Data Template, that user, if they then "close" out of the "Create New User Data Template" editing module, they will loose all the Cloud Config YAML that they had entered in the previous editor.
To Reproduce
Steps to reproduce the behavior:

Go to Virtual Machines
Go to Create
Build a Virtual Machine
Before create, goto Advanced Options
Start inputing Cloud Config YAML under the "Cloud Config" -> "User Data:" editor
Then click on "User Data Template"
Then select "Create New", module will pop up
Then select "Close"
You'll notice the edits that you had made in the main editor have disappeared

Expected behavior
That we would not be mutating the edits within the main editor on the UI.  If user "closes" out of a "User Data Template", "Create New" module, that user would be able to go right back to adding to the edits they were making prior.
Environment

Harvester ISO Version: master-937f333c-head
Underlying Infrastructure: Baremetal Dell PowerEdge R720

Additional context
https://user-images.githubusercontent.com/5370752/195692683-056d446c-7fb9-470a-a082-9edb4e1cc0b8.mp4

Thanks for the fix @n313893254 !
This looks great :smile:
Tested on, Harvester Version: master-14bbee2c-head
QEMU/KVM, single node.
https://user-images.githubusercontent.com/5370752/214411485-69f0380c-8edf-4ff3-a984-229d5fde011d.mp4


Which Algorithm is used for Eigenvalue Decomposition

Hello,
I am wondering which algorithm is used for the decomposition of eigenvalues.
What I need to compute is the smallest eigenvalue(s) of a matrix.
Thanks,
Mathias

I think it is
 Matrix.Evd()

Hi NullRefer,
thanks for replying! What I mean is that I need to know which (mathematical) algorithm is used for .evd. (Arnoldi,...). Any idea?
Best,
Mathias

I'm sorry that I don't know which algorithm is used for evd


Vector-tile issue

This seems to be a vector tile issue:

 Fix last issue for Genk before maintenance cycle.


[9.x] Unable to queue Mailable if using priority

Laravel Version: 9.0.1 (I think I saw this in 8.x too, but didn't investigate)
PHP Version: 8.0.14

Description:
If your Mailable has a priority (assuming the bug in #40916 has been fixed), then the message will fail to queue with:
Serialization of 'Closure' is not allowed

This is because the priority setting is done through a callback within Mailable.
Steps To Reproduce:
class MyTestEmail extends Mailable implements ShouldQueue {
    public function __construct() {
        $this->priority(1);
    }
}

\Mail::to('test@example.com')->queue(new MyTestEmail());

Moving priority() into the build function instead of the constructor works enough as a workaround, so maybe that's fine.

Yes please move this to the build method. Thanks


sidekiq-throttled.gemspec: Prefer add_dependency

This is a lint change, in order to get builds to 🟢

Sorry, missed this PR - closed via f1a86f12bf9660e5515620175f2633510fe4d4e7


A particular csv-file is not recognized

I'm runnnig version GGIR 1.11-0 on Arch Linux and R-Version 4.0.2, with data from
Actilive-Devices.
The filename is:

"MOS2E31191189 (2020-03-26)RAW.csv"

The Header of the file in question is:

------------ Data File Created By ActiGraph GT3X+ ActiLife v6.13.4 Firmware v1.9.2 date format dd.MM.yyyy at 100 Hz  Filter Normal -----------
Serial Number: MOS2E31191189
Start Time 10:15:00
Start Date 26.03.2020
Epoch Period (hh:mm:ss) 00:00:00
Download Time 10:41:48
Download Date 09.04.2020
Current Memory Address: 0
Current Battery Voltage: 3.85     Mode = 12
Accelerometer X,Accelerometer Y,Accelerometer Z
[...]

This file is not recognized by the package, but should be.
This is one my my first issues on github, if you need additional data let me
know.

Header looks good to me. Please post error message. Also please try running latest version of GGIR.
Thanks

I ran the latest version of ggir, this has fixed this issue.


Negative amount of beacon modules

It is possible to specify negative amount of modules for beacons. This results in negative amount of factories required, and with speed modules this can result in total power of f.e. -1234 W (without k).

Confirmed bug.

Is this pushed? It still goes negative when you use the number spinner. Also it is probably also wise to cap it to some max (16?). Globally or depending on type of structure (i.e. less for assemblers, more for big things like silo, etc).


Message: Timestamp interaction refactor

Message: Timestamp interaction refactor

This update refactors how a Timestamp is rendered into a Message,
or a Timeline component.
It now always renders into the DOM, but is hidden with CSS opacity.
Previously, it would be mounted/unmounted and revealed with HoverWrapper
combined with Animate. This worked, but it may have resulted in some
scroll jittering as the layout re-adjusts.
Opting for this new CSS reveal method, means that I was able to remove
HoverWrapper.
Other enhancements include adjusting how the Meta markup is structured
within ChatBlock. It now no longer affects the vertical positioning of
a Chat Timestamp.
Lastly, Timeline was refactored with Flow, and several components were
"prop connected".

Coverage remained the same at 100.0% when pulling dd658841decac86158a0b8e2beae85098d7cc926 on message-interaction-fixes into 5cabb1a133badb912dc1376f5be2e08dcb6e9ac3 on master.

Gonna merge this one up!!


Model evaluation migration

Migrating the data from model eval, and I have a few questions to resolve in this thread:

Are notebooks 1, 2, and 3 being replaced by notebooks the @alaws-USGS and @gzt5142 are working on? Or is it worthwhile to transfer these?
Do we need to keep any of these:
a. analyzed_data.csv
b. draft_03_nwm_benchmark_visualization.ipynb
c. draft_04_nwm_nhm_benchmark_visualization.ipynb
Are you ok with putting the preprocessing notebook in our dataset_preprocessing/archive folder? And then the model_evaluation folder will just contain notebooks with evaluation/visualization of those results?

I had been working through 02_nwm_benchmark_analysis.ipynb ... and got side-tracked in the rabbit-hole of writing helpers for the math/stats.
The replacement(s) are in https://github.com/USGS-python/hytest_notebook_tutorials/tree/dev/Syllabus/L3/NWM%20Benchmark
Note that those rely on having the math bits defined externally.  Last time we talked about it, opinions were mixed as to whether that's a good idea... Should that conversation continue?

Maybe I can move over the notebooks for now, with the assumption that your work will overwrite them in the future. I will put notebooks 2/3 in tutorials, knowing that we plan to replace them both with full-fledged tutorials at some point.

We can copy over what you have so far in a new branch - overwriting the current file with your version. Then once it is complete, we can make the merge request?

I think that works. With regards to the NWM workbooks, those were more fleshed out than the CONUS404 notebooks but they will be updated/adapted to turn them into tutorials rather than demos.

We can delete, that was me just messing around trying to improve the next version before Gene and Andrew came to save us.
b. draft_03_nwm_benchmark_visualization.ipynb
c. draft_04_nwm_nhm_benchmark_visualization.ipynb
I'm not sure what anaylzed_data.csv is, based on the comit comment, I think this has been resolved and moved into the existing notebooks.

I think notebook 1 will now live in dataset_preprocessing


Sofiar/feature phone numbers browse api

Description
Adding changes requested in the API Review.

@sofiar-msft the comments I left apply for both the sync and async client.


OG addons

Open graph updates:

share image size adjustments
og:url added

:cake:  @projectmushroom


Auto delete tag after deleting post

I want to delete tag automatically if there no any post related to the tags.
Please help me..

Thanks for reporting. This issue looks like a duplicate of #111. If you have additional information to add, please do so there.


More tests and conn handling improvements

Added a bunch more tests to carbonlink
Removed tests for logging side effects in favor of direct isolated unit
tests #83 #87
modified carbonlink to immediately drop connection on malformed queries
Enabled race detector in Makefile's test target

This PR should improve test coverage and reduce dependence on testing for exact language in errors and/or log messages.
The only behavioral change is that connections are dropped immediately on carbonlink queries that timeout while reading from the conn or fail on parsing the query packet. Both cases seemed like a sane behavior as there is no way to correct for receiving phase after an incomplete read.

Please, don't enable "-race" by default before https://github.com/Sirupsen/logrus/issues/295 fixed.

Tests should pass with race detection enabled, this PR handles the bug in logrus by removing calls to change the state of the logger so that bug doesn't trigger race detection.

Tests should pass with race detection enabled, this PR handles the bug in logrus by removing calls to change the state of the logger so that bug doesn't trigger race detection.

Ok
There is another problem. Race detector greatly slows down tests. On my MacBook started to fall another test
--- FAIL: TestThrottleChan (8.01s)
        Location:       throttle_test.go:38
	Error:		Should be true
	Messages:	perSecond: 531234, bw: 347932

FAIL

In travis same problem
--- FAIL: TestThrottleChan (7.00s)
	Location:	throttle_test.go:38
	Error:		Should be true
	Messages:	perSecond: 213000, bw: 200221

FAIL

The throttle chan test should really run as two steps, one where it runs unthrottled to determine the throughput in the given test env followed by a throttled run which sets the throttle to some significantly reduced rate(20% of the max or similar).


Command Bar - Issue with the Z - Index flow when "More Options" flyout is open.

Describe the bug

So, Here we have a Grid inside a ScrollViewer, where the first row is occupied by a command bar and the second row is occupied by a StackPanel with a bunch of buttons inside. Now, when we open the more options popup and scroll the contents inside the scroll Viewer, it seemed to float away beyond the set height. There seems to be an issue with Z-Index of the Command bar.

Here with I am also attaching a zip of the POC I did on this behalf.
POC.zip
Steps to reproduce the bug
You could go ahead and use the POC I have embedded along with the description.
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
No response

@Ajaiqmar a simple workaround would be to dismiss the flyout when the viewport changes.
  <CommandBar x:Name="commandBar" EffectiveViewportChanged="CommandBar_EffectiveViewportChanged">
  private void CommandBar_EffectiveViewportChanged(FrameworkElement sender, EffectiveViewportChangedEventArgs args)
  {
      commandBar.IsOpen = false;
  }


Fix for TypeError issues #20

I noticed these TypeError issues were triggered by both the settings dashboard and the create overlay for RedirectsViewer. I was able to fix this issue by adding a property-alias attribute to all <umb-property /> tags.

Hi @creativesuspects
Thx for this PR. I will merge it. It will be part of the beta release. I need to fix another issue and then I will release a new version

Hi @creativesuspects
Thx for this PR. I will merge it. It will be part of the beta release. I need to fix another issue and then I will release a new version


Joystick implimentatiom

We can grab the values but we don't have many meaningful ways to use it.

Mouse movements don't work right now. Id also love the ability to make a pinwheel type menu where you can select whatever you want


Bug when setting parallel paths variable and corresponding winding pattern

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
When changing the parallel paths variable (ParallelPaths) of a custom winding and then trying to set the appropriate winding pattern, Im getting the error:
SetWindingCoil failed - Path index too high. Check number of paths.
What Ive already tried:

Appropriately updating the undocumented CoilsPerPath_Array variable before trying to set information on the new path does not have an effect on the outcome either
Trying to run "create_winding_pattern()" before attempting to set information on the new path changes the error to a similar error: RPC Communication Error: Range check error without further information.
Its definitely possible to create a second path in the models im working with through the MotorCAD GUI.

📝 Steps to reproduce
# Open a model with a custom winding pattern and ParallelPaths == 1
# Increse the paths to 2
mcad.set_variable('ParallelPaths', 2)

# optionally update the CoilsPerPath_Array variable or run "create_winding_pattern()"

# Try to set some property on the second path
mcad.set_winding_coil(1, 2, 1, 19, 'C', 28, 'C', 53)

# Will throw the error: SetWindingCoil failed - Path index too high. Check number of paths.

💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2024.1.2
🐍 Which Python version are you using?
3.11
📦 Installed packages
not of interest

Okay it seems the bug can be circumvented when performing these steps:
# Open a model with a custom winding pattern and ParallelPaths == 1
# Increse the paths to 2
mcad.set_variable('ParallelPaths', 2)

# Change the winding type to anything not custom
mcad.set_variable("MagneticWindingType", 1)

# Create the winding pattern here, doesnt throw the range check error like it would for the custom winding type
mcad.create_winding_pattern()

# Change the winding type back to custom
mcad.set_variable("MagneticWindingType", 2)

# Set some property on the second path
mcad.set_winding_coil(1, 2, 1, 19, 'C', 28, 'C', 53)

# Will not throw any errors

Ill leave the issue open since this cant be the intended behavior and does require entering the entire custom pattern again.


[Contextual Cursor]

This issue is for the external plugin: Contextual Cursor
Wanted to say I love this plugin, no issues I've come across and I'll keep an eye for any in game menus that could use a cursor update. But, I did have an idea for a plugin that you might be interested, it's in the same vein as this plugin. I don't know if you remember the loot beams from RSHD but I always thought those were cool and increased that sweet dopamine hit. Would you ever have interest in making a plugin similar?

Loot beams are not possible as an external, due to major internal changes. Trevor has been looking to make them for a long time now.


Text: the text parser is not removing \ or \n from the input correctly before setting raw

good/equivs/emptystrings.ion has a few examples and whilst the text roundtrip may be similar the binary output is not. the text parser should be altering the raw value after lexing out the start/end indexes

merged


Doesn't import under Python 3

Python 3.5.3+ (default, Jun  7 2017, 23:23:48)
[GCC 6.3.0 20170519] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import treecompare
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/daniel/.virtualenvs/mypy/lib/python3.5/site-packages/treecompare/__init__.py", line 24, in <module>
    from .differ import make_differ
  File "/home/daniel/.virtualenvs/mypy/lib/python3.5/site-packages/treecompare/differ.py", line 1, in <module>
    from . import implementations as impl
  File "/home/daniel/.virtualenvs/mypy/lib/python3.5/site-packages/treecompare/implementations.py", line 98, in <module>
    class DiffNumbers(DiffPrimitives):
  File "/home/daniel/.virtualenvs/mypy/lib/python3.5/site-packages/treecompare/implementations.py", line 99, in DiffNumbers
    diffs_types = (int, long, float)
NameError: name 'long' is not defined

I'm curious about this too! (Interested in potentially diffing some trees for a recurring back-office chore.) Is this package being maintained? It looks to be <500 lines of Python. Adapting the build/test harness and debugging our way into Python 3 support would feel like a worthy package of open source effort - if there's a path to getting the changes into PyPI.

I forked this repo today and have filed a task in my personal project management to break down a Python 3 port into actionable steps. Note it's a very low-urgency chore I need this for, so I can't guarantee it will happen soon or quickly.
Would love input from any other watchers on this - I think the goal of this package merits its maintenance as Python moves forward, and I in particular would rather use it than hand-roll some junky ad hoc tree diffing stuff. Judging by the above date stamps, this repo appears abandoned, but please correct me if I'm wrong. I'd far prefer to contribute through PRs than maintaining a fork but will do the latter if it's the best way forward.


Undocumented and/or not functional env variable HH_ENV_VAR_PROMPT

I dvorka,
And first of all thank you for this great peace of software, it is very useful.
I wanted to change the default hh prompt to my $PS1, looking in the configuration documentation nothing  seems to describe how to it, but  searching a little bit in the code, the hstr.c module has a print_prompt() function that look for a HH_ENV_VAR_PROMPT environment variable to set the hh prompt to it if I understood correctly.
So I set this env var to $PS1 in my ~/.bashrc file:
export HH_ENV_VAR_PROMPT=$PS1

Of course $PS1 is set before it in the file
But it does not work, the prompt is still the default one.
Am I doing it wrong ? Is there something I didn't understand ?

Hi @lee-pai-long!
Please try HH_PROMPT as it's name of the environment variable (HH_ENV_VAR_PROMPT is name of C constant). However, copying $PS1 will not work for you as it contains Bash's DSL for prompt definition i.e. you have to somehow evaluate $PS1 to resulting prompt that can be in turn set to HH_ENV.

Thank you it works!

:wink:


 You can find more details on Oryx here: https://github.com/microsoft/Oryx
2023-05-04T11:02:21.8039137Z ---Oryx build logs---
2023-05-04T11:02:21.8039392Z
2023-05-04T11:02:21.8039604Z
2023-05-04T11:02:22.2262303Z Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
2023-05-04T11:02:22.2263046Z You can report issues at https://github.com/Microsoft/Oryx/issues
2023-05-04T11:02:22.2263662Z
2023-05-04T11:02:22.2264147Z Oryx Version: 0.2.20230501.1, Commit:<PHONE_NUMBER>5ab2977af68fc5b3c344d32858d8af, ReleaseTagName: 20230501.1
2023-05-04T11:02:22.2264717Z
2023-05-04T11:02:22.2265087Z Build Operation ID: 54605be3a677b955
2023-05-04T11:02:22.2265651Z OS Type           : bullseye
2023-05-04T11:02:22.2265996Z Image Type        : jamstack
2023-05-04T11:02:22.2266513Z
2023-05-04T11:02:22.2408818Z Detecting platforms...
2023-05-04T11:02:24.0905527Z Detected following platforms:
2023-05-04T11:02:24.0931564Z   nodejs: 18.16.0
2023-05-04T11:02:24.0955183Z Version '18.16.0' of platform 'nodejs' is not installed. Generating script to install it...
2023-05-04T11:02:24.1539190Z Detected the following frameworks: Typescript,React
2023-05-04T11:02:24.2560493Z
2023-05-04T11:02:24.3104052Z
2023-05-04T11:02:24.3117227Z Source directory     : /working_dir/app
2023-05-04T11:02:24.3117549Z Destination directory: /36a2a219-7c08-4d7e-b39d-64442ddeb153-swa-oryx/app
2023-05-04T11:02:24.3117758Z
2023-05-04T11:02:24.3117960Z Installing common platform dependencies...
2023-05-04T11:02:25.2363180Z Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
2023-05-04T11:02:25.3062082Z Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
2023-05-04T11:02:25.3073543Z Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
2023-05-04T11:02:26.1442370Z Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8183 kB]
2023-05-04T11:02:26.2673683Z Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [237 kB]
2023-05-04T11:02:26.3610445Z Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.6 kB]
2023-05-04T11:02:27.4695473Z Fetched 8643 kB in 2s (3614 kB/s)
2023-05-04T11:02:27.9474353Z Reading package lists...
2023-05-04T11:02:28.4459256Z Reading package lists...
2023-05-04T11:02:28.5673102Z Building dependency tree...
2023-05-04T11:02:28.5673795Z Reading state information...
2023-05-04T11:02:28.6412270Z Calculating upgrade...
2023-05-04T11:02:28.7266138Z 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2023-05-04T11:02:29.2144263Z Reading package lists...
2023-05-04T11:02:29.3351774Z Building dependency tree...
2023-05-04T11:02:29.3366102Z Reading state information...
2023-05-04T11:02:29.4675055Z git is already the newest version (1:2.30.2-1+deb11u2).
2023-05-04T11:02:29.4675381Z 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2023-05-04T11:02:29.4742466Z
2023-05-04T11:02:29.4748660Z Downloading and extracting 'nodejs' version '18.16.0' to '/opt/nodejs/18.16.0'...
2023-05-04T11:02:29.5056294Z Detected image debian flavor: bullseye.
2023-05-04T11:02:30.9937315Z Downloaded in 1 sec(s).
2023-05-04T11:02:30.9944103Z Verifying checksum...
2023-05-04T11:02:31.0200499Z Extracting contents...
2023-05-04T11:02:32.4230187Z performing sha512 checksum for: nodejs...
2023-05-04T11:02:32.6153326Z Done in 3 sec(s).
2023-05-04T11:02:32.6153582Z
2023-05-04T11:02:32.6793867Z Removing existing manifest file
2023-05-04T11:02:32.6809022Z Creating directory for command manifest file if it does not exist
2023-05-04T11:02:32.7195626Z Creating a manifest file...
2023-05-04T11:02:32.7195896Z Node Build Command Manifest file created.
2023-05-04T11:02:32.7196072Z
2023-05-04T11:02:32.7196313Z Found npm version spec to follow in package.json: '^9.3.1'
2023-05-04T11:02:32.7196575Z Updating version of npm installed to meet the above version spec.
2023-05-04T11:02:35.2300256Z
2023-05-04T11:02:35.2300808Z removed 1 package, and changed 60 packages in 2s
2023-05-04T11:02:35.2301082Z
2023-05-04T11:02:35.2301370Z 27 packages are looking for funding
2023-05-04T11:02:35.2301656Z   run `npm fund` for details
2023-05-04T11:02:35.2376670Z
2023-05-04T11:02:35.2377078Z
2023-05-04T11:02:35.2377348Z Using Node version:
2023-05-04T11:02:35.2433506Z v18.16.0
2023-05-04T11:02:35.2497210Z
2023-05-04T11:02:35.2497741Z Using Npm version:
2023-05-04T11:02:35.5419808Z 9.6.6
2023-05-04T11:02:35.6237333Z
2023-05-04T11:02:35.6237937Z Running 'npm install'...
2023-05-04T11:02:35.6238395Z
2023-05-04T11:02:52.3178652Z
2023-05-04T11:02:52.3178925Z added 752 packages in 16s
2023-05-04T11:02:52.3185282Z
2023-05-04T11:02:52.3185520Z 150 packages are looking for funding
2023-05-04T11:02:52.3185742Z   run `npm fund` for details
2023-05-04T11:02:52.3478634Z
2023-05-04T11:02:52.3482226Z Running 'npm run build'...
2023-05-04T11:02:52.3482417Z
2023-05-04T11:02:52.6173680Z
2023-05-04T11:02:52.6173958Z ><EMAIL_ADDRESS>build
2023-05-04T11:02:52.6174139Z > tsc && vite build
2023-05-04T11:02:52.6174280Z
2023-05-04T11:03:02.4712759Z vite v4.2.1 building for production...
2023-05-04T11:03:02.6660020Z transforming...
2023-05-04T11:03:28.7796566Z ✓ 12139 modules transformed.
2023-05-04T11:03:29.3561882Z Generated an empty chunk: "dom-helpers".
2023-05-04T11:03:29.3574027Z Generated an empty chunk: "html-parse-stringify".
2023-05-04T11:03:29.3637315Z Generated an empty chunk: "prop-types".
2023-05-04T11:03:29.4170804Z Generated an empty chunk: "void-elements".
2023-05-04T11:03:29.6836418Z rendering chunks...
2023-05-04T11:03:30.7892213Z computing gzip size...
2023-05-04T11:03:30.8967131Z build/assets/AdminTag-4cac5679.svg                    0.16 kB
2023-05-04T11:03:30.8972334Z build/assets/WarningIcon-3698bbd3.svg                 0.39 kB
2023-05-04T11:03:30.8975256Z build/index.html                                      3.37 kB
2023-05-04T11:03:30.8978079Z build/assets/errorIllustration-e71ee9a8.png          23.84 kB
2023-05-04T11:03:30.8980494Z build/assets/Nk-logo-positiv-b045f92b.png            73.70 kB
2023-05-04T11:03:30.8982812Z build/assets/loginPageIllustration-3f707991.png     225.16 kB
2023-05-04T11:03:30.8985242Z build/assets/dom-helpers-4ed993c7.js                  0.00 kB │ gzip:   0.02 kB
2023-05-04T11:03:30.8991639Z build/assets/html-parse-stringify-4ed993c7.js         0.00 kB │ gzip:   0.02 kB
2023-05-04T11:03:30.8994739Z build/assets/prop-types-4ed993c7.js                   0.00 kB │ gzip:   0.02 kB
2023-05-04T11:03:30.8997279Z build/assets/void-elements-4ed993c7.js                0.00 kB │ gzip:   0.02 kB
2023-05-04T11:03:30.9005109Z build/assets/clsx-1229b3e0.js                         0.36 kB │ gzip:   0.23 kB
2023-05-04T11:03:30.9008012Z build/assets/react-error-boundary-e160aa8d.js         1.45 kB │ gzip:   0.71 kB
2023-05-04T11:03:30.9011105Z build/assets/react-is-1aacdabe.js                     2.16 kB │ gzip:   0.79 kB
2023-05-04T11:03:30.9016389Z build/assets/react-router-dom-a3350d59.js             2.63 kB │ gzip:   1.35 kB
2023-05-04T11:03:30.9019622Z build/assets/hoist-non-react-statics-691fe6cb.js      2.65 kB │ gzip:   0.97 kB
2023-05-04T11:03:30.9022565Z build/assets/scheduler-04ce0582.js                    4.14 kB │ gzip:   1.80 kB
2023-05-04T11:03:30.9025715Z build/assets/stylis-581c9ed0.js                       4.21 kB │ gzip:   1.95 kB
2023-05-04T11:03:30.9030628Z<EMAIL_ADDRESS>                     4.56 kB │ gzip:   1.82 kB
2023-05-04T11:03:30.9033649Z build/assets/react-i18next-9b51b0f4.js                5.27 kB │ gzip:   2.28 kB
2023-05-04T11:03:30.9036158Z build/assets/react-transition-group-c9677172.js       6.42 kB │ gzip:   2.21 kB
2023-05-04T11:03:30.9041445Z build/assets/react-router-04b8a35a.js                 7.88 kB │ gzip:   3.11 kB
2023-05-04T11:03:30.9060885Z build/assets/react-985293de.js                        8.12 kB │ gzip:   3.08 kB
2023-05-04T11:03:30.9061177Z<EMAIL_ADDRESS>                 8.72 kB │ gzip:   3.78 kB
2023-05-04T11:03:30.9061469Z<EMAIL_ADDRESS>                  18.02 kB │ gzip:   7.79 kB
2023-05-04T11:03:30.9068599Z<EMAIL_ADDRESS>                 20.09 kB │ gzip:   7.49 kB
2023-05-04T11:03:30.9073064Z build/assets/i18next-3588fa67.js                     55.98 kB │ gzip:  15.08 kB
2023-05-04T11:03:30.9076669Z build/assets/recoil-ec59a727.js                      78.46 kB │ gzip:  24.61 kB
2023-05-04T11:03:30.9079801Z build/assets/react-dom-fbbf7044.js                  129.97 kB │ gzip:  41.79 kB
2023-05-04T11:03:30.9085060Z<EMAIL_ADDRESS>               131.82 kB │ gzip:  51.75 kB
2023-05-04T11:03:30.9090624Z<EMAIL_ADDRESS>                     165.17 kB │ gzip:  51.11 kB
2023-05-04T11:03:30.9094033Z build/assets/index-799ca6b2.js                      304.87 kB │ gzip:  72.15 kB
2023-05-04T11:03:30.9096545Z<EMAIL_ADDRESS>                   335.18 kB │ gzip:  71.80 kB
2023-05-04T11:03:30.9102686Z<EMAIL_ADDRESS>               1,308.20 kB │ gzip: 376.96 kB
2023-05-04T11:03:30.9106831Z
2023-05-04T11:03:30.9109322Z (!) Some chunks are larger than 500 kBs after minification. Consider:
2023-05-04T11:03:30.9118894Z - Using dynamic import() to code-split the application
2023-05-04T11:03:30.9119245Z - Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
2023-05-04T11:03:30.9119700Z - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
2023-05-04T11:03:30.9126037Z ✓ built in 28.44s
2023-05-04T11:03:31.0384576Z Preparing output...
2023-05-04T11:03:31.0387080Z
2023-05-04T11:03:31.0389658Z Copying files to destination directory '/36a2a219-7c08-4d7e-b39d-64442ddeb153-swa-oryx/app'...
2023-05-04T11:03:35.6063829Z Done in 4 sec(s).
2023-05-04T11:03:35.6074798Z
2023-05-04T11:03:35.6075070Z Removing existing manifest file
2023-05-04T11:03:35.6096123Z Creating a manifest file...
2023-05-04T11:03:35.6097772Z Manifest file created.
2023-05-04T11:03:35.6098032Z Copying .ostype to manifest output directory.
2023-05-04T11:03:35.6119198Z
2023-05-04T11:03:35.6119412Z Done in 71 sec(s).
2023-05-04T11:03:35.6771600Z
2023-05-04T11:03:35.6771821Z
2023-05-04T11:03:35.6772014Z ---End of Oryx build logs---
2023-05-04T11:03:35.6772211Z Finished building app with Oryx
2023-05-04T11:03:35.9948096Z Using 'staticwebapp.config.json' file for configuration information, 'routes.json' will be ignored.
2023-05-04T11:03:36.0033560Z Copying 'staticwebapp.config.json' to build output
2023-05-04T11:03:36.0253111Z No Api directory specified. Azure Functions will not be created.
2023-05-04T11:03:36.1154646Z Either no Api directory was specified, or the specified directory was not found. Azure Functions will not be created.
2023-05-04T11:03:47.5282201Z Zipping App Artifacts
2023-05-04T11:03:47.6524223Z Done Zipping App Artifacts
2023-05-04T11:03:47.6524539Z Uploading build artifacts.
2023-05-04T11:04:01.8534638Z Finished Upload. Polling on deployment.
2023-05-04T11:04:01.8910825Z Status: InProgress. Time: 0.0377411(s)
2023-05-04T11:04:16.9226016Z Status: InProgress. Time: 15.0679224(s)
2023-05-04T11:04:31.9617676Z Status: Succeeded. Time: 30.1030912(s)
2023-05-04T11:04:31.9618010Z Deployment Complete :)
2023-05-04T11:04:31.9618272Z Visit your site at: https://white-grass-0c1d11903.1.azurestaticapps.net
2023-05-04T11:04:31.9803307Z Thanks for using Azure Static Web Apps!
2023-05-04T11:04:31.9803593Z Exiting
2023-05-04T11:04:32.2312021Z ##[section]Finishing: AzureStaticWebApp

Relevant log output
Before task:
-rw-r--r-- 1 vsts docker 1379 May  4 11:01 app/.npmrc
After task:
-rw-r--r-- 1 root root 1379 May  4 11:01 app/.npmrc

2023-05-04T11:04:32.3743391Z ##[section]Starting: npmAuthenticate
2023-05-04T11:04:32.3746567Z ==============================================================================
2023-05-04T11:04:32.3746673Z Task         : npm authenticate (for task runners)
2023-05-04T11:04:32.3746876Z Description  : Don't use this task if you're also using the npm task. Provides npm credentials to an .npmrc file in your repository for the scope of the build. This enables npm task runners like gulp and Grunt to authenticate with private registries.
2023-05-04T11:04:32.3747065Z Version      : 0.218.0
2023-05-04T11:04:32.3747119Z Author       : Microsoft Corporation
2023-05-04T11:04:32.3747192Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm-authenticate
2023-05-04T11:04:32.3747288Z ==============================================================================
2023-05-04T11:04:32.4959884Z ##[error]Unhandled: EACCES: permission denied, open '/home/vsts/work/1/s/app/.npmrc'
2023-05-04T11:04:32.4976036Z ##[error]Error: EACCES: permission denied, open '/home/vsts/work/1/s/app/.npmrc'
    at Object.openSync (node:fs:594:3)
    at Object.writeFileSync (node:fs:2207:35)
    at copyFile (/home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/node_modules/azure-pipelines-tasks-packaging-common-v3/util.js:20:8)
    at Object.restoreFileWithName (/home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/node_modules/azure-pipelines-tasks-packaging-common-v3/util.js:58:13)
    at /home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/npmauthcleanup.js:27:18
    at Generator.next (<anonymous>)
    at /home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/npmauthcleanup.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/npmauthcleanup.js:4:12)
    at run (/home/vsts/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.218.0/npmauthcleanup.js:18:12)
2023-05-04T11:04:32.5009123Z ##[section]Finishing: npmAuthenticate

Aditional info
The task runs fine but cleanup fails

I was getting the same error as shown above on the npmauthenticate clean-up task. it just seems to have started happening today. I had been using the task specified like this:
 - task: npmAuthenticate@0
              inputs:
                workingFile: 'frontend/.npmrc'

but then tried specifying a (presumably earlier version)  and it fixed my issue. so now I have the task specified as :
 - task<EMAIL_ADDRESS>              inputs:
                workingFile: 'frontend/.npmrc'

I have the same issue, the "s" directory in the _work path changed ownership to root.
The first run work, but any subsequent results in permission denied:
`Starting: Checkout Front-End@develop to s
Task         : Get sources
Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
Version      : 1.0.0
Author       : Microsoft
Help         : More Information
Syncing repository: Front-End (Git)
git version
git version 2.34.1
git config --get remote.origin.url
##[warning]'git config --get remote.origin.url' failed with exit code: 1, output: ''
##[error]One or several exceptions have been occurred.
##[error]System.UnauthorizedAccessException: Access to the path '/data/devops-agent/_work/1/s/.gitignore' is denied.`
tb-admin@tb-tools-test1:/data/devops-agent/_work/1$ ls -al total 24 drwxr-xr-x 6 tb-admin tb-admin 4096 May  8 12:40 . drwxrwxr-x 9 tb-admin tb-admin 4096 May  8 12:37 .. drwxr-xr-x 2 tb-admin tb-admin 4096 May  8 12:40 TestResults drwxr-xr-x 2 tb-admin tb-admin 4096 May  8 12:40 a drwxr-xr-x 2 tb-admin tb-admin 4096 May  8 12:34 b drwxr-xr-x 8 root     root     4096 May  8 12:36 s tb-admin@tb-tools-test1:/data/devops-agent/_work/1$

Confirmed seeing it too on linux self-hosted

We are seeing this as well

Does anyone have a workaround for this ?
we tried adding a shell script to change the folder permissions after the static app task and it fails, too. Very strange it works sometimes and most of the times it does not. Whats even strange is shell script checking for node path
below is the log and attached screenshot for details.
##[debug]Evaluating condition for step: 'change permissions back'
##[debug]Evaluating: SucceededNode()
##[debug]Evaluating SucceededNode:
##[debug]=> True

##[debug]Result: True
Starting: change permissions back
Task         : Bash
Description  : Run a Bash script on macOS, Linux, or Windows
Version      : 3.224.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
##[debug]Using node path: /agent/externals/node16/bin/node
##[error]An error occurred trying to start process '/agent/externals/node16/bin/node' with working directory '/agent/_work/1/s'. Permission denied
##[debug]System.ComponentModel.Win32Exception (13): An error occurred trying to start process '/agent/externals/node16/bin/node' with working directory '/agent/_work/1/s'. Permission denied
at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Microsoft.VisualStudio.Services.Agent.Util.ProcessInvoker.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, InputQueue1 redirectStandardIn, Boolean inheritConsoleHandler, Boolean keepStandardInOpen, Boolean highPriorityProcess, Boolean continueAfterCancelProcessTreeKillAttempt, CancellationToken cancellationToken) in /home/vsts/work/1/s/src/Agent.Sdk/ProcessInvoker.cs:line 291
at Microsoft.VisualStudio.Services.Agent.ProcessInvokerWrapper.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, InputQueue1 redirectStandardIn, Boolean inheritConsoleHandler, Boolean keepStandardInOpen, Boolean highPriorityProcess, Boolean continueAfterCancelProcessTreeKillAttempt, CancellationToken cancellationToken) in /home/vsts/work/1/s/src/Microsoft.VisualStudio.Services.Agent/ProcessInvoker.cs:line 308
at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.DefaultStepHost.ExecuteAsync(String workingDirectory, String fileName, String arguments, IDictionary`2 environment, Boolean requireExitCodeZero, Encoding outputEncoding, Boolean killProcessOnCancel, Boolean inheritConsoleHandler, Boolean continueAfterCancelProcessTreeKillAttempt, CancellationToken cancellationToken) in /home/vsts/work/1/s/src/Agent.Worker/Handlers/StepHost.cs:line 76
at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.NodeHandler.RunAsync() in /home/vsts/work/1/s/src/Agent.Worker/Handlers/NodeHandler.cs:line 206
at Microsoft.VisualStudio.Services.Agent.Worker.TaskRunner.RunAsync() in /home/vsts/work/1/s/src/Agent.Worker/TaskRunner.cs:line 407
at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.RunStepAsync(IStep step, CancellationToken jobCancellationToken) in /home/vsts/work/1/s/src/Agent.Worker/StepsRunner.cs:line 236

Commenting to keep the issue from going stale. This is still an issue.

Commenting to keep the issue from going stale. This is still an issue.


Cannot start jupyther notebook

After download and install kernel with ./gradlew install , start new notebook got error
Starting server: KernelConfig(ports=[64057, 64053, 64056, 64055, 64054], transport=tcp, signatureScheme=hmac-sha256, signatureKey=9f641ffe-cea077832b193c4d7a1d72e4, pollingIntervalMillis=100, classpath=[/Users/eggcaker/.ipython/kernels/kotlin/kotlin-stdlib-1.2.21.jar, /Users/eggcaker/.ipython/kernels/kotlin/jupyter-lib-0.6.0.jar, /Users/eggcaker/.ipython/kernels/kotlin/annotations-13.0.jar])
[main] INFO ikotlin - start listening
Exception in thread "main" java.lang.NoClassDefFoundError: org/jetbrains/kotlin/com/intellij/openapi/diagnostic/Logger
	at uy.kohesive.keplin.kotlin.script.resolver.AnnotationTriggeredScriptDefinition.<clinit>(AnnotationTriggeredScriptDefinition.kt:70)
	at org.jetbrains.kotlin.jupyter.ReplForJupyter.<init>(repl.kt:22)
	at org.jetbrains.kotlin.jupyter.IkotlinKt.kernelServer(ikotlin.kt:62)
	at org.jetbrains.kotlin.jupyter.IkotlinKt.main(ikotlin.kt:41)
Caused by: java.lang.ClassNotFoundException: org.jetbrains.kotlin.com.intellij.openapi.diagnostic.Logger
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 4 more

Same problem here. Is there a workaround until a proper fix is released?

I'll check Keplin and the Jupyter-Kotlin to see where the breaking is, and where that reference is coming from.

Could it be jetbrains moved the intellij.openapi.diagnostic.Logger class?
In the keplin source:
keplin-core/src/main/kotlin/uy/kohesive/keplin/kotlin/script/resolver/AnnotationTriggeredScriptDefinition.kt
...
import org.jetbrains.kotlin.com.intellij.openapi.diagnostic.Logger
...
Exception in thread "main" java.lang.NoClassDefFoundError:
org/jetbrains/kotlin/com/intellij/openapi/diagnostic/Logger
Current location of the class:
found in kotlin-compiler-1.2.21.jar
com/intellij/openapi/diagnostic/Logger.class
I don't have enough experience to know how to fix this, if it is indeed the problem.

I see the mismatch in compiler libraries, so working to fix that now.

Can someone check master now and see if you still have the issue?

It's fixed here. Muchas gracias!

Same here. Herzlichen Dank!

works. 👍


add null data filter

@dawsbot please review

@dawsbot just merged with v1 so the pr is up to date and tested the pulling process. everything is looking good to me, please review.


Workaround JDK bug that will cause an AssertionError when calling Ser…

…verSocketChannel.config().getOptions().
Motivation:
There is a JDK bug which will return IP_TOS as supported option for ServerSocketChannel even if its not supported afterwards and cause an AssertionError.
See http://mail.openjdk.java.net/pipermail/nio-dev/2018-August/005365.html.
Modifications:
Add a workaround for the JDK bug.
Result:
ServerSocketChannel.config().getOptions() will not throw anymore and work as expected.

/cc @meshcow @amizurov

@meshcow also verified the fix... merging


Path Autocomplete Crashes

Issue Type: Bug
Issue:
The extension 'Path Intellisense' by Christian Kohler crashes randomly but takes down other Intellisense as well.
Thinking maybe this was an error with the extension I uninstalled it and tried 'Path Autocomplete' by Mihai Vilcu instead. But this has the same issue. So, now I'm reporting this as a bug with VS Code's Intellisense extension ability.
Likely cause:
When using path related Intellisense, backspacing to a previous folder then re-adding the slash quickly. Ex:

import MyComponent from '../../components/MyComponent/MyC
import MyComponent from '../../components/MyComponent
import MyComponent from '../../components/MyComponent/

This doesn't always happen, but it seems like that pattern, followed quickly trips up Intellisense and then all Intellisense is gone until rebooting VS Code. :(
VS Code version: Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz (4 x 2904)

Memory (System)
7.88GB (0.97GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.7

prettier-vscode
esb
1.2.2

path-autocomplete
ion
1.8.1

Reproduces only with extensions

vscode has a built-in path completion since the last couple updates.
I've removed path-intellisense and node-intellisense (not sure if that was the name) since the functionality comes included, BUT this very same problem happens anyway.
I have a LOT of other extensions installed, and everything worked just fine right until this update where the path intellisense became part of the editor. Now I just sometimes get An unknown error occurred. Please consult the log for more details. in the devtools, and I can't find any more info on this.

Ctrl + Shift + P, Reload Window is now my most used shortcut because of that. =/

ohler crashes randomly but takes down other Intellisense as well.

Can you define crash? Also, please attach readings from the log (F1 > Show Logs > window).

I think they meant that intellisense just stops working, there really isn't a crash when it happens.
Right after a import React from "react"; it stops, and the logs say:

@jrieken, when I say it crashes I mean that Intellisense stops making suggestions, except for sometimes still offering suggestions for same-document variable/function names, but even that isn't always the case. I'll watch that more carefully next time it crashes.
The logs for window were blank. Here are the logs from ext host.
[2018-03-19 08:07:50.569] [exthost3] [info] extension host started
[2018-03-19 08:07:50.635] [exthost3] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":""}
[2018-03-19 08:07:50.636] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\emmet\out\extension
[2018-03-19 08:07:51.204] [exthost3] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":""}
[2018-03-19 08:07:51.204] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\git\out\main
[2018-03-19 08:07:52.180] [exthost3] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":""}
[2018-03-19 08:07:52.180] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\merge-conflict\out\extension
[2018-03-19 08:07:52.344] [exthost3] [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint {"startup":true,"activationEvent":""}
[2018-03-19 08:07:52.344] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\dbaeumer.vscode-eslint-1.4.7\client\out\extension
[2018-03-19 08:07:52.643] [exthost3] [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode {"startup":true,"activationEvent":""}
[2018-03-19 08:07:52.643] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\esbenp.prettier-vscode-1.2.2\out\src\extension
[2018-03-19 08:07:53.349] [exthost3] [info] ExtensionService#_doActivateExtension ionutvmi.path-autocomplete {"startup":true,"activationEvent":""}
[2018-03-19 08:07:53.349] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\ionutvmi.path-autocomplete-1.8.1\out\src\extension
[2018-03-19 08:07:53.468] [exthost3] [info] eager extensions activated
[2018-03-19 08:08:34.423] [exthost3] [info] extension host started
[2018-03-19 08:08:34.452] [exthost3] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":""}
[2018-03-19 08:08:34.452] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\emmet\out\extension
[2018-03-19 08:08:34.637] [exthost3] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":""}
[2018-03-19 08:08:34.637] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\git\out\main
[2018-03-19 08:08:34.870] [exthost3] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":""}
[2018-03-19 08:08:34.870] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\merge-conflict\out\extension
[2018-03-19 08:08:34.897] [exthost3] [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint {"startup":true,"activationEvent":""}
[2018-03-19 08:08:34.897] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\dbaeumer.vscode-eslint-1.4.7\client\out\extension
[2018-03-19 08:08:34.979] [exthost3] [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode {"startup":true,"activationEvent":""}
[2018-03-19 08:08:34.979] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\esbenp.prettier-vscode-1.2.2\out\src\extension
[2018-03-19 08:08:35.212] [exthost3] [info] ExtensionService#_doActivateExtension ionutvmi.path-autocomplete {"startup":true,"activationEvent":""}
[2018-03-19 08:08:35.212] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\ionutvmi.path-autocomplete-1.8.1\out\src\extension
[2018-03-19 08:08:35.235] [exthost3] [info] eager extensions activated
[2018-03-19 08:08:35.239] [exthost3] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"activationEvent":"onLanguage:javascript"}
[2018-03-19 08:08:35.239] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\typescript\out\extension
[2018-03-19 08:08:40.091] [exthost3] [info] extension host started
[2018-03-19 08:08:40.114] [exthost3] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.114] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\emmet\out\extension
[2018-03-19 08:08:40.201] [exthost3] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.201] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\git\out\main
[2018-03-19 08:08:40.374] [exthost3] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.374] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\merge-conflict\out\extension
[2018-03-19 08:08:40.400] [exthost3] [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.400] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\dbaeumer.vscode-eslint-1.4.7\client\out\extension
[2018-03-19 08:08:40.483] [exthost3] [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.483] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\esbenp.prettier-vscode-1.2.2\out\src\extension
[2018-03-19 08:08:40.726] [exthost3] [info] ExtensionService#_doActivateExtension ionutvmi.path-autocomplete {"startup":true,"activationEvent":""}
[2018-03-19 08:08:40.726] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\ionutvmi.path-autocomplete-1.8.1\out\src\extension
[2018-03-19 08:08:40.745] [exthost3] [info] eager extensions activated
[2018-03-19 08:08:51.738] [exthost3] [info] extension host started
[2018-03-19 08:08:51.768] [exthost3] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"activationEvent":""}
[2018-03-19 08:08:51.768] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\emmet\out\extension
[2018-03-19 08:08:51.902] [exthost3] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"activationEvent":""}
[2018-03-19 08:08:51.902] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\git\out\main
[2018-03-19 08:08:52.077] [exthost3] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"activationEvent":""}
[2018-03-19 08:08:52.077] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\merge-conflict\out\extension
[2018-03-19 08:08:52.100] [exthost3] [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint {"startup":true,"activationEvent":""}
[2018-03-19 08:08:52.100] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\dbaeumer.vscode-eslint-1.4.7\client\out\extension
[2018-03-19 08:08:52.182] [exthost3] [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode {"startup":true,"activationEvent":""}
[2018-03-19 08:08:52.182] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\esbenp.prettier-vscode-1.2.2\out\src\extension
[2018-03-19 08:08:52.423] [exthost3] [info] ExtensionService#_doActivateExtension ionutvmi.path-autocomplete {"startup":true,"activationEvent":""}
[2018-03-19 08:08:52.423] [exthost3] [info] ExtensionService#loadCommonJSModule C:\Users\jason.anderson.vscode\extensions\ionutvmi.path-autocomplete-1.8.1\out\src\extension
[2018-03-19 08:08:52.451] [exthost3] [info] eager extensions activated
[2018-03-19 08:08:52.455] [exthost3] [info] ExtensionService#_doActivateExtension vscode.extension-editing {"startup":false,"activationEvent":"onLanguage:markdown"}
[2018-03-19 08:08:52.455] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\extension-editing\out\extension
[2018-03-19 08:08:52.480] [exthost3] [info] ExtensionService#_doActivateExtension vscode.markdown-language-features {"startup":false,"activationEvent":"onLanguage:markdown"}
[2018-03-19 08:08:52.480] [exthost3] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\markdown\out\extension

likely typescript/javascript

Okay, here are logs after the first noticeable error:
Window logs:
[2018-03-19 08:22:58.968] [renderer1] [info] Uninstalling the extension ionutvmi.path-autocomplete-1.8.1 from window 1
[2018-03-19 08:30:35.502] [renderer1] [error] Cannot read property 'match' of undefined: TypeError: Cannot read property 'match' of undefined
at new MyCompletionItem (c:\Program Files\Microsoft VS Code\resources\app\extensions\typescript\out\features\completionItemProvider.js:54:34)
at TypeScriptCompletionItemProvider.provideCompletionItems (c:\Program Files\Microsoft VS Code\resources\app\extensions\typescript\out\features\completionItemProvider.js:232:26)
at
[2018-03-19 08:30:52.155] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:31:20.215] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:31:38.122] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:35:36.114] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:39:43.161] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:40:06.017] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:40:20.371] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:43:05.372] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:44:04.489] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:46:23.104] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
[2018-03-19 08:48:45.329] [renderer1] [error] An unknown error occurred. Please consult the log for more details.
ext host logs:
2018-03-19 08:07:42.947] [exthost1] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"activationEvent":"onLanguage:javascript"}
[2018-03-19 08:07:42.947] [exthost1] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\typescript\out\extension
[2018-03-19 08:13:11.041] [exthost1] [info] ExtensionService#_doActivateExtension vscode.extension-editing {"startup":false,"activationEvent":"onLanguage:typescript"}
[2018-03-19 08:13:11.041] [exthost1] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\extension-editing\out\extension
[2018-03-19 09:15:34.354] [exthost1] [info] ExtensionService#_doActivateExtension vscode.css {"startup":false,"activationEvent":"onLanguage:scss"}
[2018-03-19 09:15:34.354] [exthost1] [info] ExtensionService#loadCommonJSModule c:\Program Files\Microsoft VS Code\resources\app\extensions\css\client\out\cssMain

Not sure if it matters that much but I was using Windows 10, 64bit and having these issues.
The same messages and initially sluggish behavior appear when I switched to Ubuntu 17.10, but it's no where near that bad. It's just a hiccup when you try to access intellisense once again after a "path" use, but then it becomes normal.
The same errors are there, but intellisense doesn't stop working, it just slows down a little bit, and only once.

Can you try please try the latest insiders build with all extensions disabled. I fixed one of the typescript errors from the logs: https://github.com/Microsoft/vscode/commit/b26862c89b3ee94cad227e821a36e72b89688bbb

@mjbvz I've been trying the insider's build all morning. It seems to work now. Whereas my production build of VS Code keeps crashing about every 10 to 15 minutes.
It is commit: 952b2a64

It's crashing again. Using
Version | 1.23.0-insider
Commit | 7c62e560a3e494
Date | 2018-04-13T05:17:33.810Z
All IntelliSense stops working. This is in a create-react-app bootstrapped app.

Can you also please try collecting the TypeScript server logs:

Add "typescript.tsserver.log": "verbose" to your user settings and restart VSCode.
Reproduce the issue
In vscode with a js/ts file open, run the TypeScript: Open TS Server logs command. This should open a log directory with a tsserver.log file in it

Look for errors, stack traces, or other suspicious info near the end of the logs. If you can share the logs I can try looking through them to see what is going on

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

I followed those steps @mjbvz . I have a log file now.
It's about 40k lines and I'm not sure I want to post everything on GitHub anyway.

From the log, the last thing is:
Info 11762[14:42:10.524] event:     {"seq":0,"type":"event","event":"projectsUpdatedInBackground","body":{"openFiles":["pathToFile.js","pathToFile2.js","pathToFile3.js"]}} Info 11763[14:42:10.525] Sending request:     {"projectName":"/dev/null/inferredProject1*",     "fileNames": [...lotsOfFiles], ... }

Do you see this in the latest VS Code insiders builds?

@mjbvz , I've not noticed it as much lately, but stopped watching for it. I've also had fewer times I've needed to import at 3+ levels deep. I'll watch for it and respond again in a few days.
That said, I do know today and yesterday I was able to go 4 levels deep 2 different times. So, maybe it is fixed. Thanks for the update!

Ok, let me know if you see it again in the latest insiders builds


Error when install

bower install video-player
bower video-player#*        not-cached git://github.com/addyosmani/video-player.git#*
bower video-player#*           resolve git://github.com/addyosmani/video-player.git#*
bower video-player#*      ENORESTARGET Tag/branch master does not exist

Additional error details:
No tags found in git://github.com/addyosmani/video-player.git
Available branches: gh-pages

You can basically use bower install video-player#gh-pages to aim the single branch available right now.
Bad thing too, this is a Polymer 0.x component, that need to be updated to the 1.x version.


Seo improve

The current structured data for the homepage and post are missing some fields in the Google Rich test.
You can see the test result for https://hugodoit.pages.dev/ at  google test result for home page.
For the post page at google test result for article.
This test result is after applying these fixes:
google test result for home page and google test result for article
The title and canonical URL are identical on paginated pages. https://github.com/gohugoio/hugo/issues/4507.
so I do this:

Removed microdata and unified use of JSON-LD.
Add alternateName field to webSite schema. That is an alternate site name used in Google search results.
Fix the missing field in the Google rich result test.
Prioritize using the featured image in the front matter as the article image in JSON-LD.
Display page count for paginated titles.
The canonical URL for pagination is the same as the page URL.

But the og:url for pagination is not fixed. I think is not worthwhile to leave it to the Hugo community to resolve.

@HEIGE-PCloud Is it possible to implement this improvement? Thanks!

Thank you very much!


Db export fails to export column of type 'REAL'

Describe the bug
Exporting the db with exportToJson({jsonexportmode:'full'}) fails to export column of type REAL.
To Reproduce
Create a db with a table that has a column type of REAL, and export the data.
Expected behavior
The exported data should also contain the data from column of type REAL.
Screenshots
Given the schema:

And the following table rows:

This is what is exported:

Note that the weight column data is missing in the last picture (the values, 11, 12, 13 from picture 2).
Desktop (please complete the following information):

OS: Ubuntu

Smartphone (please complete the following information):
Android Emulator
Additional context
I'm assuming that it has to do with the column being of type REAL, as it's the only difference compared to the other columns.
This used to work in a previous version of the plugin, but there seems to have occurred a regression at some point.
Plugin version: 2.9.13

@accron-1 I will have a look

@accron-1 Well it is working fine.
your entry for the import should be :
  export const dataToImport94: any = {
    database : "db-from-json94",
    version : 1,
    encrypted : false,
    mode : "full",
    tables :[
        {
            name: "reps",
            schema: [
                {column:"id", value: "INTEGER PRIMARY KEY AUTOINCREMENT UNIQUE"},
                {column:"fk_workoutexercices", value:"INTEGER NOT NULL"},
                {column:"weight", value:"REAL NOT NULL"},
                {column:"reps", value:"INTEGER NOT NULL"},
                {column:"rest", value:"INTEGER NOT NULL"},
                {column:"note", value:"TEXT"},
            ],
            values: [
                [1,1,11,21,31,"NULL"],
                [2,1,12,22,32,"NULL"],
                [3,1,13,23,33,"NULL"],
            ]
        },
    ]
  };

@accron-1 you can see it working in https://github.com/jepiqueau/angular-sqlite-app-starter/tree/refactor

Thanks for looking into it!
However, that's not the output I get:
{
  "database": "gymrat",
  "encrypted": false,
  "mode": "full",
  "tables": [{
	  "name": "reps",
	  "schema": [
		{"column": "id","value": "INTEGER PRIMARY KEY AUTOINCREMENT UNIQUE"},
		{"column": "fk_workoutexercises","value": "INTEGER NOT NULL"},
		{"column": "weight","value": "REAL NOT NULL"},
		{"column": "reps","value": "INTEGER NOT NULL"},
		{"column": "rest","value": "INTEGER NOT NULL"},
		{"column": "note","value": "TEXT"},
		{"value": "REFERENCES workoutexercises(id) ON DELETE CASCADE ","foreignkey": "fk_workoutexercises"}
	  ],
	  "values": [
		[1,1,21,31,"NULL"],
		[2,1,22,32,"NULL"],
		[3,1,23,33,"NULL"],
	  ]
	},]
};

So there seems to be something else at play here.
My overall db schema is more complex of course:

Also, this was one of the first features that I added and tested in my app, about a year ago, and it did work with an older version of the plugin.
I didn't try it since then, but as I have just upgraded my app from Vue2 -> Vue3 I re-tested everything to make sure nothing is broken in the Vue code, and this is how I discovered it.

I just tried changing REAL to INTEGER for the table schema, to see if it makes a difference, and sure enough everything works as expected:

So it definitely has something to do with the col type being REAL.

I didn't try it since then, but as I have just upgraded my app from Vue2 -> Vue3 I re-tested everything to make sure nothing is broken in the Vue code, and this is how I discovered it.

To clarify: between the first implementation, when it worked, and now, I have upgraded the plugin on a few occasions, but I never tried the export-feature between upgrades. Therefore I can't say at what version it stopped working.

@accron-1 If you can make a small replicate of the app showing the problem and share it on github i could have a look otherwise it would be difficult for me to grab what is wrong as i could not replicate it

I'm not sure if I can break down the app to anything smaller.
But in the meantime I've come up with another test: I set the col type to INTEGER (which we've seen seems to work), but insert a float instead (Sqlite doesn't enforce types, so it's no problem). Thus:
These values (note that Weight is now a decimal number):

are represented as this in the JS and app:

Note that the db and app work fine with the decimal numbers.
However, the export still fails to include the weight column:

So it's not only an issue of the col being defined as REAL, but it also seems to be a problem that the value is a float.
Maybe this can give you some clue as to what the problem might be.

@accron-1 I tested it on android and ios in an angular app using the @capacitor-community/sqlite@latest which is the 2.9.13 .
i bound the value according to the type which can be TEXT, REAL, INTEGER, BLOB and that is it so FLOAT is not a sqlite3 type.
if you cannot split the application in a small one and share it i could not really help as it works with my test app.

@accron-1 look at https://www.sqlite.org/datatype3.html for the supported types

I'm aware that a FLOAT type doesn't exist in Sqlite, I was merely illustrating another potential issue.
What test can I do that will give you more info regarding this issue?

Another difference between your export and mine is that yours contains the version number: version : 1
My export doesn't have that, as you can see above.
I noticed that from the start, but thought that I hadn't defined the version in my db script. I checked now and I do have it:
PRAGMA user_version = 1;
It's more evidence that our versions don't behave the same.

@accron-1  ok show me your package.json file
Did you run npx cap sync before building your app.
Show me your MainActivity.java file
Was your database created with an importFromJson process or through standard use of SQLite statements (Execute, ExecuteSet, Run ...)
if importFromJson give me the json object  as you enter it
otherwise show me the statements.
Can run this statement with query and give me the result in the sql field
SELECT name,sql FROM sqlite_master WHERE type = 'table' AND name='reps';

Can you run this statement  with execute or run and give me the result
PRAGMA table_info("users");

@accron-1 In android studio, can you open your app
open the folder capacitor-community-sqlite
open the folder java and the subfolder com.getcapacitor.community.database.sqlite.SQLite.ImportExportJson
open the file UtilsJson.java
go to line 158
            if (type.equals("REAL") && (value instanceof Double || value instanceof Integer)) ret = true;
change it with
            if (type.equals("REAL") && (value instanceof Double || value instanceof Float || value instanceof Integer)) ret = true;
clean the project and rebuild it
tell me if it does change something and give you the right result

When I did npx cap sync I saw that I was actually still stuck on v. 2.4: I had updated the package.json but had failed to run npx. I have now upgraded to 2.9.13 (according to npx cap ls).
That certainly explains the different output for you and me, but I haven't been able to verify it yet.
To request storage permission we used to do:
const handlerPermissions = CapacitorSQLite.addListener(
        'androidPermissionsRequest', async (data) => {
          if(data.permissionGranted === 1) {
            ....
          }
      });
      CapacitorSQLite.requestPermissions();

But not anymore it seems. What's the new way of doing this? I couldn't find anything in the docs.

@accron-1 this i not required so it has been removed on the request of some developers. Yes it is important that you npx cap sync each time you change the version of the plugin and also when you upgrade capacitor/core ...
Now is it working?

I had to adapt all my db calls to the new api, so it took a while.
The exported data now contains the REAL field, so the export and import finally works as expected! Thanks for mentioning the npx sync.
Question: will the api's change again in the upcoming v.3?

@accron-1 The API will not change except that the call to db method will have to be done through a try...catch to get back the error messages which was requested by a lot of developers. You can see it in https://github.com/capacitor-community/sqlite/blob/master/docs/Ionic-Vue-Usage.md . I know that it can be a bit frustrating but i just make changes when developers ask for it and there is a value for the capacitor community. But everything is clearly documented and demonstrated in app starters depending on the framework. Hope this clarify. i wish you all the best for your app. The 2.9.x series will be stopped to be maintained as soon as Capacitor 3 will be released. To day it is in Release Candidate.

Can you close the issue when everything has been finally tested on your site


Update code-signing-cert-manage.md

Added new Certera EV Code Signing product as it is much more cheaper.

I added Certera EV Code Signing Certificate to make this list complete. Please accept pull request and merge it live.

See #3578.


Placing focal point property on Settings tab makes the focal point appear on the wrong place when revisiting tab

Placed focal point:

After publishing and opening tab:


Bold text everywhere

I have installed the theme and everything text-related is in bold. I also removed everything, which contains anything revolving font-weight and or any "bold"-statement at all. Still makes every textarea bold.

Sounds like your internet is somehow not downloading the non-bold styles of the font.

Having the same problem

Any suggestions as to what I can do on my end?
Thanks

Encountering the same problem, have done fresh reinstalls of Discord, BD and theme. Any suggestions as to what I can do on my end to try and resolve this? Thank you.

same thing happening to me


Does it must train from pre-trained EfficientNet for backbone？

I'm grateful to you for your contribution.  I have a problem about pre-trained model.  When I trained without any pre-trained model, it convergenced slowly， and  the ap is lower. So, does it must train from pre-trained EfficientNet of backbone？

You do need a pre-trained backbone even if it is pretrained for a different dataset. Detection models are slow to converge and unstable with a random backbone.


Endpoint to lookup tenant by email address

Also added the tenant matching the query string in the email search

Assigning to @mrvisser for review

From slack:

Hmm, I had anticipated this to just be a more descriptive error when the user tries to share w/ an invalid email address
I’m guessing a proactive UI check is needed as a usability improvement to that?
what I meant was that, rather than build a back-end endpoint and let the UI determine if an error should be shown, I thought we would just leave the widget the way it was, but when they sent the request to share with the emails, the error that came back would outline the emails it failed to share with
no new back-end endpoint, no additional ajax request in the AS plugin, it would just give more information about the error when they attempt to share with them.
but as long as we purposefully determined that there is an improvement by pro-actively making that request to check if there is an issue, I’m fine w/ it

@simong @nicolaasmatthijs can you confirm all the extra complexity is necessary?

From a usability point of view, I think it is better to do the check before the sharing actually happened. If you know before sharing that you won't be able to share with some of the people you're trying to share with, it might change your intention. If you don't know before sharing, you potentially have to start cleaning up those that did work or something along those lines.

Looks good, just a few doc-related-things. Back to @simong


script crashes after search query is submitted

Attempting to use anime-cli via Termux on an SGS9. I'm far from being either a termux or a python wizard, so the issue may not actually be with anime-cli, but I'm not quite savvy enough to determine that for myself, so please forgive me!
anime-cli appears to install normally via pip install anime-cli
When I start the script by entering anime-cli I'm greeted with the prompt ? What anime would you like to watch?. Regardless of what I enter, the result is a stream of errors ending with: InquirerPy.exceptions.InvalidArgument: argument choices cannot be empty
Python version is 3.10.0
Please let me know if there are any logs I can share or further information I can provide.

Termux Screenshot:

Thanks, for reporting the issue, seems like gogoanime moved to some other site which is causing the issue

Hey, I have fixed this issue, update anime-cli by running
pip install anime-cli --upgrade

although streaming to video player is still broken and I am working on it

Update, I have fixed the issue completely. I am closing this now, you can open it anytime again
just upgrade the anime-cli version


Update prerequisites.md

Adding information on Azure Extension for SQL Server installation on VMWare clusters outside of Azure.

Replaced by https://github.com/MicrosoftDocs/sql-docs-pr/pull/26258.
#please-close


[BUG] If neovim is opened without a file as argument, norme.nvim won't work

Description
If Neovim is opened solely with nvim, the norme linter won't run.
Steps to reproduce

nvim
Open a .c or .h file inside nvim
Induce a norme error

Expected Behaviour
Show the error with LSP diagnostics.
Neovim version
$ nvim -v
NVIM v0.5.0-dev+1291-gb227cedf8
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az207-747

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

Run :checkhealth for more info

I'm gonna test if this is something due to nvim-lint or a norme.nvim specific error.
@paulo-santana

It seems to be something wrong with norme.nvim. I tested nvim-lint with pylint and it works fine.

Can confirm: Pylint works, so does Flake8, but norme does not

Looking in the code, both flake8 and pylint set stdin=false. We should check the behavior of another linter that reads from stdin, like shellchek

Shellcheck also works

When removing the line ignore_exitcode = true, from
https://github.com/vinicius507/norme.nvim/blob/1e157c19197fca3e97adfb6cbccf202b43f08ee7/lua/norme.lua#L43-L50
Neovim shows the message Linter exited with code 1 when reproducing the steps for the problem.
Do we have access to any kind of log from nvim-lint?


Changes done

u just need to push changes to the same branch that you worked on from the previous pull request

push the changes to your branch changes

push the changes to your branch changes
no need to make a new pull request

I am getting error in my git bash that Changes cannot be resolved to branch

so that's why I made new branch

whats the error? You could also use GitHub Desktop to make it easier

whats the error? You could also use GitHub Desktop to make it easier

"Changes cannot be resolved to branch this is the" error

I will try Github desktop

Now I got it what I have to do , can I make new pr in this branch i.e changes_done because a the branch Changes is not visible in git hub desktop

Now I am able to commit on this same branch thankyou for suggesting about GitHub Desktop :)

alright looks good to go :)

Thankyou so much @redxzeta you really helped me a lot as I am a beginner. It was really a good experience working with you. Can I work with you in the future, if you have a team can I join ?


Update module and dependency gardener/etcd-druid to v0.23.0

How to categorize this PR?

/area backup control-plane quality
/kind enhancement
What this PR does / why we need it:
This PR updates gardener/etcd-druid version to v0.23.0, which brings some major changes to the changes to the etcd pod labels, druid controller design, Etcd resource reconciliation, new Etcd status fields for better operability of etcd clusters, new webhook handler to protect druid-managed resources from unintended modifications/deletions, security fixes, etc (please refer to the release notes below for the full list of changes).

Etcd-Druid v0.23.0 Release Notes
⚠ Breaking Changes

[OPERATOR] Custodian controller has now been removed in favour of etcd status reconciliation handled by etcd controller. CLI flags --custodian-workers and --custodian-sync-period have now been removed, and are no longer recognised by etcd-druid. by @unmarshall [#777]
[OPERATOR] Labels on druid-managed resources are now streamlined, and no longer include name and instance. Instead, these are now standard labels app.kubernetes.io/managed-by and app.kubernetes.io/part-of, as recommended by Kubernetes. Additionally, app.kubernetes.io/component label is also used to set the type of the component for an etcd cluster. by @unmarshall [#777]
[OPERATOR] Creation of Etcd resource no longer requires annotation gardener.cloud/operation: reconcile to be set on it for etcd-druid to reconcile it. In other words, creation of Etcd resource is immediate, irrespective of whether etcd-spec-auto-reconciliation is enabled or not. by @unmarshall [#777]
[OPERATOR] CLI flag --workers has now been renamed to --etcd-workers. Additionally, etcd controller also accepts new CLI flags enable-etcd-spec-auto-reconcile to control how and when the etcd spec is reconciled, and etcd-status-sync-period to specify the duration after which an event will be re-queued to ensure etcd status reconciliation. CLI flag ignore-operation-annotation has been deprecated, and will be removed in an upcoming release. by @unmarshall [#777]
[OPERATOR] Volume mounts for the etcd StatefulSet have now been fixed, to allow individually specifying TLS secrets for the etcd and backup-restore servers. CA and TLS certificates used for etcd client-server communication, relevant to the container that they are mounted on, can be found at /var/etcd/ssl/. CA and TLS certificates used for etcd peer communication, relevant to the container that they are mounted on, can be found at /var/etcd/ssl/peer. CA and TLS certificates used for etcd-backup-restore client-server communication, relevant to the container that they are mounted on, can be found at /var/etcdbr/ssl. by @unmarshall [#777]
[DEVELOPER] Vendor directory has now been removed from the project. Please run make tidy to pull dependencies into go mod cache initially, and whenever required. by @shreyas-s-rao [#748]
[USER] Before upgrading druid to v0.23.0+, please ensure that druid is running with at least v0.22.3+. This is required to avoid any downtime during the upgrade of the etcds by the new druid version, as well as to ensure backward compatibility of your etcds, in case you wish to downgrade back to v0.22.3+. by @shreyas-s-rao [#823]

📰 Noteworthy

[OPERATOR] A new condition DataVolumesReady has been introduced in etcd.Status to capture and report PVC warnings. by @unmarshall [#777]

[OPERATOR] Annotation druid.gardener.cloud/ignore-reconciliation has been marked as deprecated. Please use druid.gardener.cloud/suspend-etcd-spec-reconcile instead, which provides the same behavior. by @unmarshall [#777]

[OPERATOR] Scale-up logic for single-node etcd clusters with peerTLS disabled to multi-node etcd clusters with peerTLS enabled, has been improved by making it deterministic and eliminates an unnecessary restart of the first etcd member, thus making this process faster and error-free. by @unmarshall [#777]

[OPERATOR] CLI flag --leader-election-resource-lock is now deprecated, and will be set to leases from a future release onwards. by @unmarshall [#777]

[OPERATOR] A new validating webhook named sentinel has been introduced to safeguard resources created by etcd-druid. A new annotation druid.gardener.cloud/disable-etcd-component-protection has been introduced, which if set, tells sentinel webhook to allow manual changes by an operator on any resource managed by etcd-druid.
This webhook is disabled by default, and can be enabled as follows:

If deploying druid via the binary, please pass CLI flag --enable-sentinel-webhook to it. Additionally, CLI flags --webhook-server-bind-address, --webhook-server-port and --webhook-server-tls-server-cert-dir need to be passed when enabling the webhook, which enforces TLS communication using the given certs.
If deploying druid via the Helm charts, please set chart value webhooks.sentinel.enabled: true.
If deploying druid via Skaffold, please set environment variable DRUID_ENABLE_SENTINEL_WEBHOOK=true. This is also applicable when running Make targets such as deploy, deploy-dev, deploy-debug, test-e2e, etc, except for ci-e2e-kind. by @unmarshall [#777]

[OPERATOR] The component model used for deploying resources has now been replaced with a simplified ResourceOperator model, found under /internal/operator. by @unmarshall [#777]

[OPERATOR] CLI flag --metrics-addr is now deprecated. Please use --metrics-bind-address and --metrics-port instead. by @unmarshall [#777]

[USER] Remove usage of *_STORAGE_API_ENDPOINT` environment variables for Google and Azure providers. Storage API endpoint / domain will instead be directly consumed by etcd-backup-restore from the mounted backup secret. by @shreyas-s-rao [#856]

[DEVELOPER] We are moving towards using golang native tests. This also allowed us to relook at the unit and integration tests that we have. In this PR we have only partially introduced comprehensive golang native tests for specific packages (internal/operator, internal/webhook, internal/controller/etcd/ and internal/utils/). We have also added comprehensive integration tests for etcd controller and the new IT tests are present at test/it/controller/etcd. In future PRs we will replace the ginkgo based tests and replace it with native golang tests for rest of the packages as well. by @unmarshall [#777]

[DEVELOPER] All packages under /pkg and /controllers directories have now been moved to new parent /internal directory. by @unmarshall [#777]

✨ New Features

[OPERATOR] Etcd resource status now includes field LastErrors to indicate any errors encountered in the last reconciliation of the etcd resource. Custom error codes have been introduced to help capture contextual information from the reconciliation run. by @unmarshall [#777]
[OPERATOR] Etcd resource status now includes field LastOperation to indicate the last operation performed on the etcd resource. This includes a unique RunID to help sift through logs containing the specific RunID, improving debuggability. Every reconciler run generates a unique RunID. by @unmarshall [#777]
[DEVELOPER] etcd-druid now supports end-to-end testing with Azurite - the Azure Blob Storage Emulator by @renormalize [#753]
[DEVELOPER] Builds for non-native platforms can now be done using the docker-build make target instead of having to invoke the docker buildx command. The platform can be specified using the PLATFORM variable which is passed while invoking make. by @renormalize [#873]
[USER] Added support for new backup store provider stackit which is an alias for S3. by @unmarshall [#777]

🏃 Others

[OPERATOR] etcd-backup-restore container was started with SYS_PTRACE linux capability. This prevented creating etcd cluster with Pod Security Standards. This linux capability has now been removed as it is no longer required. by @unmarshall [#777]
[OPERATOR] set cpu and memory requests for compaction pods by @anveshreddy18 [#853]
[OPERATOR] Etcd pods now mount files with DefaultMode set to 0640. by @unmarshall [#777]
[OPERATOR] Upgrade github.com/gardener/etcd-backup-restore dependency from 0.26.0 to 0.29.0 by @anveshreddy18 [#830]
[OPERATOR] 1. Dependency version upgrades done to gardener/gardener, controller-runtime, controller-tools, k8s.io/*, logr, zap, ginkgo, uber mock, uuid dependencies.
2. Adapted golanglint-ci recommendations.
3. Removed dependency on gardener/gardener hack/scripts.
by @unmarshall [#834]
[OPERATOR] Enhanced parallel execution support in e2e tests, reducing time and improving test suite robustness. by @seshachalam-yv [#833]
[OPERATOR] Upgrades to golang version 1.22.4 by @unmarshall [#826]
[OPERATOR] Updated e2e tests to support label changes during HA upgrades, preventing the reconciliation process from getting stuck and ensuring smooth transitions in deployment scenarios.
by @seshachalam-yv [#838]
[OPERATOR] Introduced new Makefile targets:
deploy-dev - starts skaffold in dev mode allowing reloading druid upon change.
deploy-debug - starts skaffold in debug mode allowing using breakpoints to interrupt the control-flow.
undeploy - uses skaffold delete to delete all resources that are installed via skaffold. by @unmarshall [#777]
[OPERATOR] Enabling the configurability of --max-backups for LimitBasedGC through the etcd resource spec .spec.backup.maxBackupsLimitBasedGC. by @anveshreddy18 [#755]
[OPERATOR] Updated README.md by @unmarshall [#851]
[DEVELOPER] Introduced testing guidelines, added developer productivity scripts and make targets to stress test, debug integration tests, formatting and detecting incompatible api changes. by @unmarshall [#857]
[DEVELOPER] Fixes unit tests for internal/health package, includes missing tests in the Makefile test target and minor refactoring of test utility functions. by @unmarshall [#822]
[DEVELOPER] Add Make target make docker-clean for cleaning up all docker builds related to etcd-druid. by @shreyas-s-rao [#842]
[DEVELOPER] Add Make targets make clean-build-cache and make clean-mod-cache for cleaning up Go build and mod caches respectively. by @shreyas-s-rao [#842]
[DEVELOPER] use localstack:s3-latest image instead of localstack:latest in tests for faster setup by @anveshreddy18 [#805]
[DEVELOPER] remove deprecated pkg k8s.io/utils/pointer and use pkg k8s.io/utils/ptr by @anveshreddy18 [#861]

📖 Documentation

[OPERATOR] Introduce DEP-05: Design document for operator out-of-band tasks.  by @ishan16696 [#757]

[gardener/etcd-backup-restore]
⚠ Breaking Changes

[USER] Remove support for specifying Azure custom endpoint via environment variable AZURE_STORAGE_API_ENDPOINT. Please use the new domain field (via JSON or file) instead. by @shreyas-s-rao [gardener/etcd-backup-restore#759]

🏃 Others

[DEVELOPER] Added support to use Azurite, which emulates Azure Blob Storage for local development and testing - which can be enabled by setting the AZURE_EMULATOR_ENABLED and  AZURITE_STORAGE_API_ENDPOINT environment variables. by @renormalize [gardener/etcd-backup-restore#699]

[DEVELOPER] Fixed the check make target when run locally, and a link in docs/development/new_cp_support.md. by @renormalize [gardener/etcd-backup-restore#754]

[DEVELOPER] Added documentation to use etcdbrctl as a process for testing locally, for a better developer experience and faster iteration speeds. by @renormalize [gardener/etcd-backup-restore#723]

[DEVELOPER] AWS S3 client Go module upgraded from v1.32.6 to v1.54.20. by @renormalize [gardener/etcd-backup-restore#755]

[DEVELOPER] Improved error handling for OpenStack Swift during deletion of objects. by @renormalize [gardener/etcd-backup-restore#710]

[DEVELOPER] Added support for using fake-gcs-server for all etcdbr functionalities. To enable: Either

Set GOOGLE_EMULATOR_ENABLED environment variable when running etcdbrctl command OR
Set emulatorEnabled: true in GCP backup secret when deploying via Helm chart. by @anveshreddy18 [gardener/etcd-backup-restore#697]

[USER] Do not rely on the snapshotter state when stopping the snapshotter. The snapshotter will now always be closed when a member goes from being the leader to any other state.  by @avestuk [gardener/etcd-backup-restore#680]

[USER] Add support for specifying Google storage API endpoint via file ~/.gcp/storageAPIEndpoint. Environment variable GOOGLE_STORAGE_API_ENDPOINT is deprecated, and will be removed shortly. by @shreyas-s-rao [gardener/etcd-backup-restore#759]

[USER] Add support for specifying custom domains for Azure storage.  by @shreyas-s-rao [gardener/etcd-backup-restore#759]

[OPERATOR] Bump alpine base version for Docker build to 3.18.2. by @shreyas-s-rao [gardener/etcd-backup-restore#638]

[OPERATOR] etcd-backup-restore now supports server-side encryption using customer provided keys (SSE-C) for S3-compatible providers by @amold1 [gardener/etcd-backup-restore#719]

Additionally, this PR contains the following changes:

[x] Add ValidatingWebhookConfiguration for druid in order to use the new etcd-components-webhook to protect resources that are managed by druid from unintended modifications/deletions. This also includes the creation of a new TLS server cert secret for the webhook handler.
[x] Configure etcd-events to set .spec.unhealthyPodEvictionPolicy: AlwaysAllow for its PDB. /cc @dguendisch
[x] Adapt backup-restore container resource requests, as well as etcd container VPA minAllowed values as per recommendations from https://github.com/gardener/etcd-druid/issues/783. /cc @vlerenc

Which issue(s) this PR fixes:
Fixes https://github.com/gardener/etcd-druid/issues/783
Special notes for your reviewer:
/cc @unmarshall @ashwani2k
Release note:

The `gardener/etcd-druid` image has been updated to `v0.23.0`. [Release Notes](https://redirect.github.com/gardener/etcd-druid/releases/tag/v0.23.0)

Thank you @shreyas-s-rao.

FYI/cc: @dguendisch @adenitiu

/test pull-gardener-e2e-kind-migration-ha-single-zone
/test pull-gardener-e2e-kind-ha-single-zone-upgrade
/test pull-gardener-e2e-kind-ha-multi-zone-upgrade

/test pull-gardener-e2e-kind-migration-ha-single-zone
/test pull-gardener-e2e-kind-ha-single-zone-upgrade
/test pull-gardener-e2e-kind-ha-multi-zone-upgrade

/test pull-gardener-e2e-kind-migration-ha-single-zone
/test pull-gardener-e2e-kind-ha-single-zone-upgrade
/test pull-gardener-e2e-kind-ha-multi-zone-upgrade

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/test pull-gardener-e2e-kind-ha-single-zone

/retest

/retest

/test pull-gardener-e2e-kind-operator

/retest

/retest

/retest

/test all

/test all

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.
The list of commits with invalid commit messages:

f166ffe addressed review comments from @rfranzke

fix this ...

/approve
/retest

/test pull-gardener-e2e-kind-ha-multi-zone

/test pull-gardener-e2e-kind-ha-single-zone

/test pull-gardener-e2e-kind


The experience for new users coming through Getting Started is really poor

If I found this page trying to see what Rust was about and learn about the language for the first time, I'd be really, really discouraged.
I come to the main page, and see a big "Get Started" button. Great! I click that (I genuinely had not noticed the "Learn" link at the top because the button is so prominent). I start to read through the page. I'm first told to install rustup, ok, this is pretty normal. I'll install it, then move on.
Now I'm told I have also installed cargo, and shown a bunch of commands like building, running, and testing. Okay. This is useful, but where's the code? I can't build, run, or test anything yet. This feels really out of place. I'm definitely nowhere near cargo publish!
Next, let's make a new project. Okay, I guess. I still haven't seen code, but I guess if I need a project to get coding, let me do that. I'll make my project.
Next up is adding dependencies. Why am I doing this here? I don't want dependencies, I just want to code! I'm told to add a package as a dependency, with no explanation of what that package does or why I'm adding it as a dependency. If I were really visiting Rust for the first time, out of curiosity, this is probably the point where I give up for real, because I can't understand what I'm doing any more and you want me to follow a link to a library I probably don't care about. At this point in writing this issue, I actually click the link to see what the library does, and I can confidently say that having a crap say words was not in my top favourite libraries I want to know about in a new language.
I personally would definitely have given up on this page and started looking elsewhere at this point. If for some reason I didn't, I'm happy that I finally get to see Rust code! Here's a ton of lines to do... something. Just give me Hello World please?
Scrolling down, I see Learn More. Finally! I click it. There's a link to a book! Excellent! I'll just go there. I'm prompted to choose between the first and second editions. It says if I'm not sure, I should go for the second edition, so I do (we should probably just link the second edition directly?). I go, read through the front matter...
And the first page of actual content is on how to install Rust.

Thanks Aaron. I apologize that my critique came across the way it did and I'll try to watch myself in the future. Thank you for offering the criticism in a respectful, constructive manner. :)


Feature/bayes

Adds user guide on Bayesian computational imaging

@joanrue Thanks for this contribution. After applying some fixes manually (421f0a53), this PR is now merged into master.
I am unsure however if we want this entry to come first in the user guide? To be discussed with @matthieumeo .