Flutter 2.0: CanvasKit Path constructor invoked with wrong number of params

Steps to Reproduce
Install fl_charts example app from GitHub: https://github.com/imaNNeoFighT/fl_chart.git
Change to branch: dev-nullsafety
Run on Chrome with "run -d chrome"
This is happening on both the Beta channel as well as the Stable channel.
Expected results:
The example app is running
Actual results:

Logs

https://api.flutter.dev/flutter/dart-ui/ChannelBuffers-class.html
══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY
╞═════════════════════════════════════════════════════════
The following NativeJavaScriptObject object was thrown during paint():
  BindingError: Tried to invoke ctor of Path with invalid number of parameters (1)
  - expected (0)
parameters instead!

Another exception was thrown: BindingError: Tried to invoke ctor of Path with
invalid number of parameters (1) - expected (0) parameters instead!
Another exception was thrown: BindingError: Tried to invoke ctor of Path with
invalid number of parameters (1) - expected (0) parameters instead!
Another exception was thrown: BindingError: Tried to invoke ctor of Path with
invalid number of parameters (1) - expected (0) parameters instead!
Another exception was thrown: BindingError: Tried to invoke ctor of Path with
invalid number of parameters (1) - expected (0) parameters instead!

flutter analyze
Analyzing example...

   info • `Future` results in `async` function bodies must be `await`ed or marked
          `unawaited` using `package:pedantic` •
          lib/bar_chart/samples/bar_chart_sample1.dart:307:7 • unawaited_futures
   info • Omit type annotations for local variables •
          lib/bar_chart/samples/bar_chart_sample2.dart:115:35 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/bar_chart/samples/bar_chart_sample2.dart:116:40 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/bar_chart/samples/bar_chart_sample2.dart:214:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/bar_chart/samples/bar_chart_sample2.dart:215:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample1.dart:181:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample1.dart:204:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample1.dart:226:5 •
          omit_local_variable_types
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead.
          See the migration guide in
          flutter.dev/go/material-button-migration-guide). This feature was
          deprecated after v1.25.0-8.1.pre. •
          lib/line_chart/samples/line_chart_sample2.dart:40:18 •
          deprecated_member_use
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample3.dart:56:23 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample5.dart:49:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample6.dart:29:10 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:24:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:25:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:26:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:31:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:34:5 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/line_chart/samples/line_chart_sample8.dart:36:5 •
          omit_local_variable_types
   info • This method overrides a method annotated as '@mustCallSuper' in 'State',
          but doesn't invoke the overridden method • lib/main.dart:57:8 •
          must_call_super
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample1.dart:98:9 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample2.dart:100:7 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample2.dart:101:7 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample3.dart:50:7 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample3.dart:51:7 •
          omit_local_variable_types
   info • Omit type annotations for local variables •
          lib/pie_chart/samples/pie_chart_sample3.dart:52:7 •
          omit_local_variable_types
warning • Publishable packages can't have path dependencies • pubspec.yaml:24:5 •
       invalid_dependency

26 issues found. (ran in 4.8s)

flutter doctor -v
[✓] Flutter (Channel beta, 2.0.0, on macOS 11.2.1 20D74 darwin-arm, locale en-DE)
    • Flutter version 2.0.0 at /Users/tilo/development/flutter
    • Framework revision 60bd88df91 (5 hours ago), 2021-03-03 09:13:17 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/tilo/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = /Users/tilo/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 54.0.3
    • Dart plugin version 203.7759

[✓] Connected device (3 available)
    • Pixel 5 (mobile) • 08081FDD4002T6 • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos          • darwin-arm64   • macOS 11.2.1 20D74
      darwin-arm
    • Chrome (web)     • chrome         • web-javascript • Google Chrome
      88.0.4324.192

• No issues found!

FWIW: The dev channel does not have this issue. Works perfect with the version as listed below:
flutter doctor -v
[✓] Flutter (Channel dev, 2.1.0-10.0.pre, on macOS 11.2.1 20D74 darwin-arm,
    locale en-DE)
    • Flutter version 2.1.0-10.0.pre at /Users/tilo/development/flutter
    • Framework revision cc9b78fc5c (6 days ago), 2021-02-25 13:26:03 -0800
    • Engine revision a252ec09b7
    • Dart version 2.13.0 (build 2.13.0-77.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version
    30.0.3)
    • Android SDK at /Users/tilo/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = /Users/tilo/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 54.0.3
    • Dart plugin version 203.7759

[✓] Connected device (3 available)
    • Pixel 5 (mobile) • 08081FDD4002T6 • android-arm64  • Android 11 (API
      30)
    • macOS (desktop)  • macos          • darwin-arm64   • macOS 11.2.1 20D74
      darwin-arm
    • Chrome (web)     • chrome         • web-javascript • Google Chrome
      88.0.4324.192

• No issues found!

@tiloc
This is similar to https://github.com/flutter/flutter/issues/75473 which has been fixed and merged in master. Please switch to latest master and try again to confirm.
The fix may not yet have reached beta and stable and hence you may be seeing the issue in those channels. https://github.com/imaNNeoFighT/fl_chart/issues/561#issuecomment-790088310

Not sure how to "switch to latest master". as mentioned by me earlier, this issue does not exist on dev channel. What is the typical cadence for fixes to move from dev to stable?

We have roughly 4 stable releases per year. beta comes out once a month or so. Dev is continuous, but a little behind master as it must pass additional customer tests.
Sorry, I thought that this fix would make it into this stable release on its own and so I didn't request a cherry pick. I'll see if I can request a hot-fix, but can't promise anything. Hot-fix bar is quite high.

@tiloc
flutter channel master
flutter upgrade

I requested a cherry pick for 2.0.1, which should be released much sooner than 2.1.0 (not sure exactly when, but I think we're counting days, not weeks).

I'm closing the issue as the fix is making its way to the release channels already.


Is it possible to upload a small example of preprocessed KITTI data on google drive?

Hello!
I can not use Baidu Yun, and I was wondering if you could upload a small example KITTI data set on google drive.

Hi, @majbos, thanks for your interest in our work!
I uploaded a small KITTI test set in https://drive.google.com/drive/folders/19fztoJCWj7_V1HYb5UVPyD-bHvB2_XPc?usp=sharing. Maybe you need to modify the test_kitti.txt in https://github.com/QingyongHu/SpinNet/blob/main/KITTI/Test/test_kitti.txt by deleting 9 and 10 and follow the instructions to run the test code.
Best.


Fix failing tests after the changes in bytecodealliance/wasmtime#7285

Fix failing tests after the changes in bytecodealliance/wasmtime#7285.
Since that change, threads, multi-memory, and relaxed-simd are enabled by default. E.g. disabling bulk-memory also requires disabling threads, and disabling simd also requires disabling relaxed-simd.

@kpreisser thanks for fixing this!


⚠ Bofrost.at has degraded performance

In 7161f8a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1209 ms

Resolved: Bofrost.at performance has improved in 6b9fc38.


Error setting up iCloud

The problem
iCloud integration is added successfully, however I'm getting errors in the log and no device trackers are created. I have various devices in iCloud, like watches and laptops, not only phones.
Environment

Home Assistant release with the issue: 0.104.3
Last working Home Assistant release (if known): ???
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration causing this issue: iCloud
Link to integration documentation on our website: https://www.home-assistant.io/integrations/icloud

Problem-relevant configuration.yaml
not applicable
Traceback/Error logs

hass_1         | 2020-01-24 09:49:24 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry<EMAIL_ADDRESS>for icloud
hass_1         | Traceback (most recent call last):
hass_1         |   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
hass_1         |     hass, self
hass_1         |   File "/usr/src/homeassistant/homeassistant/components/icloud/__init__.py", line 158, in async_setup_entry
hass_1         |     await hass.async_add_executor_job(account.setup)
hass_1         |   File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
hass_1         |     result = self.fn(*self.args, **self.kwargs)
hass_1         |   File "/usr/src/homeassistant/homeassistant/components/icloud/__init__.py", line 307, in setup
hass_1         |     self.update_devices()
hass_1         |   File "/usr/src/homeassistant/homeassistant/components/icloud/__init__.py", line 338, in update_devices
hass_1         |     self._devices[device_id].update(status)
hass_1         |   File "/usr/src/homeassistant/homeassistant/components/icloud/__init__.py", line 514, in update
hass_1         |     self._battery_level = int(self._status.get(DEVICE_BATTERY_LEVEL, 0) * 100)
hass_1         | TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

Additional information
Looks similar to #30829 but is caused by other part of the accessed object I assume.

@Quentame
Hello,
My name is Gary Cobb. Sorry to post here on this issue but I could not find any other way to contact you. Hopefully this message will get through to you.

Extensive iCloud3 documentation here
Download iCloud3 v2.0 here
The iCloud3 Repository is here

I developed the iCloud3 device tracker custom component over the last few years (links below) and it has gained a wide following because of it's many features that include Waze route tracking, variable interval time down to 15-second polling, tight integration with the HA iOS App, multiple tracking methods, track from multiple zones, sensor templates, gps wandering solutions, and others. The original iCloud HA component was used as a starting point and it grew to more than 7500 lines of code as features were added.
When I first wrote iCloud3, I used pyicloud to interface with the iCloud Location Service like the iCloud component. At that time, the iCloud component and pyicloud supported 2sa authorization. As you know, last year Apple started issuing notifications every time the users iCloud account was accessed last year, making this method no longer viable for location tracking. To solve this problem, I added various pieces of code to pyicloud that had been added by users on the pyicloud repository over the years that had never made it into the base code. I also added code from other sources, along with additional error checking and recovery code and created a customized version of pyicloud that I use with iCloud3. This customized version supports the Find My/Find-my-Friends location tracking by using a non-2fa iCloud account tied to the 2fa iCloud accounts as contacts.
Although this method works fine, I would again like to be able to include the ability to use the users 2fa iCloud account for location tracking without the account login notification issues.
The new rewritten iCloud component has solved this problem and I would like your help and advice on how to do this in iCloud3. I would appreciate it if you would contact me at my email address below so we can establish a dialog on the concepts that are used by iCloud3,  how iCloud does the authorization, what changes need to be made to iCloud3, etc.
Thank you and I look forward to hearing from you.
Gary Cobb
<EMAIL_ADDRESS>

@Quentame thanks for chiming in!
I've played with get a bit and it seems like the only way self._status.get(DEVICE_BATTERY_LEVEL, 0) can return a non int value is when _status already has a None value under DEVICE_BATTERY_LEVEL key:
>>> dict = {'DEVICE_BATTERY_LEVEL': None}
>>> dict.get('DEVICE_BATTERY_LEVEL', 0) is None
True

I'd guess iCloud might be returning null battery status even when DEVICE_BATTERY_STATUS is not Unknown.

Ups, my bad, will fix soon

@Quentame thank you!


⚠ Bofrost.de has degraded performance

In 4115e00, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 951 ms

Resolved: Bofrost.de performance has improved in fa6a107 after 9 minutes.


XxeProcessingProcessor does not add checked exception to method signature when using XFactory.setFeature

This is is something I overlooked. It appears as if the setFeature method always throws a checked exception. The factory creator method must therefore also throw that checked exception.

@monperrus This turned out to be a bit complicated. As an example from Redhat RSP, there's this method:
	@Override
	public void save(OutputStream os) throws IOException {
		Result result = new StreamResult(os);
		Source source = new DOMSource(factory);
		try {
			TransformerFactory factory = TransformerFactory.newInstance();
			factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
			Transformer transformer = factory.newTransformer();
			transformer.setOutputProperty(OutputKeys.INDENT, "yes"); //$NON-NLS-1$
			transformer.setOutputProperty(OutputKeys.METHOD, "xml"); //$NON-NLS-1$
			transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8"); //$NON-NLS-1$
			transformer.setOutputProperty("{http://xml.apache.org/xalan}indent-amount", "2"); //$NON-NLS-1$ //$NON-NLS-2$
			transformer.transform(source, result);
		} catch (TransformerFactoryConfigurationError | TransformerException e) {
			throw new IOException(e);
		}
	}

We turn that into the following:
	@Override
	public void save(OutputStream os) throws IOException {
		Result result = new StreamResult(os);
		Source source = new DOMSource(factory);
		try {
			TransformerFactory factory = createTransformerFactory();
			Transformer transformer = factory.newTransformer();
			transformer.setOutputProperty(OutputKeys.INDENT, "yes"); //$NON-NLS-1$
			transformer.setOutputProperty(OutputKeys.METHOD, "xml"); //$NON-NLS-1$
			transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8"); //$NON-NLS-1$
			transformer.setOutputProperty("{http://xml.apache.org/xalan}indent-amount", "2"); //$NON-NLS-1$ //$NON-NLS-2$
			transformer.transform(source, result);
		} catch (TransformerFactoryConfigurationError | TransformerException e) {
			throw new IOException(e);
		}
	}

	private static TransformerFactory createTransformerFactory() {
		TransformerFactory factory = TransformerFactory.newInstance();
		factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
		factory.setAttribute(XMLConstants.ACCESS_EXTERNAL_DTD, "");
		factory.setAttribute(XMLConstants.ACCESS_EXTERNAL_STYLESHEET, "");
		return factory;
	}

The problem here is that createTransformerFactory does not declare TransformerFactoryConfigurationError (which is a checked exception) as thrown, and so this does not compile. That's easily fixed in this particular case; simply add that exception to the method signature. However, if to original code had looked like so:
	@Override
	public void save(OutputStream os) throws IOException {
		Result result = new StreamResult(os);
		Source source = new DOMSource(factory);
		TransformerFactory factory = TransformerFactory.newInstance();
		try {
			factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
			Transformer transformer = factory.newTransformer();
			[...]
		} catch (TransformerFactoryConfigurationError | TransformerException e) {
			throw new IOException(e);
		}
	}

then we suddenly have a problem, as the factory is created outside of the try/catch that handles the checked TransformerConfigurationError. If the factory is used in between its creation and the try/catch block, it gets even more complicated.
For now, I suggest that we remove the handling of setFeature calls. The checked exception thing is an interesting general problem, but I want to get a PR to RSP this week and don't think I'll have a full solution that fast :)

For now, I suggest that we remove the handling of setFeature calls.

OK for me.


pages linked

Fixes Issue
closes #2000
@codervivek5

Changes proposed

Screenshots

Note to reviewers

Summary by CodeRabbit

New Features

Enhanced user interface for the authentication form by adding clickable hyperlinks for "Terms of Use" and "Privacy Policy," allowing direct access to these documents for improved usability and compliance.

Have you aded it for both login and signup?


Link updates

Removes Update/Save method of work item link repository and all controllers.
The only permitted actions to a link once created are:

delete
show
list

In order to mimic the update behavior you have to delete and recreate a link with different settings (e.g. with a different link type). This is needed in order for us to maintain a valid topology.
Also the Create method has been removed from the /api/workitems/<ID>/relationships/links endpoint. Only the List method remains for this endpoint.

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1822-1

@kwk snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1822-2

Codecov Report

Merging #1822 into master will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1822      +/-   ##
==========================================
+ Coverage   63.86%   63.94%   +0.07%
==========================================
  Files         128      128
  Lines       11926    11822     -104
==========================================
- Hits         7617     7559      -58
+ Misses       3623     3588      -35
+ Partials      686      675      -11

Impacted Files
Coverage Δ

controller/work_item_relationships_links.go
90.47% <ø> (+26.68%)
:arrow_up:

workitem/link/link_revision.go
100% <ø> (ø)
:arrow_up:

controller/work_item_link.go
84.81% <ø> (-0.04%)
:arrow_down:

workitem/link/link_repository.go
75.88% <ø> (+4.55%)
:arrow_up:

Continue to review full report at Codecov.

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


Drop the usage of deprecated request package

request package has been finally officially deprecated, after long time without support. This should be replaced promptly with a maintained, secure and performant library. I'd make a strong recommendation towards https://www.npmjs.com/package/node-fetch, as it provides the standard window.fetch API in a straightforward, minimal implementation.

All usages have been changed to node-fetch.


Create "You must wait until thumbnail finishes uploading" message

I have been loving the new thumbnail upload feature!
However, it's possible that users will attempt to click 'Publish' before their thumbnail is done uploading to spee.ch.
In this case, we should have a message similar to "You must agree to terms and service" that lets them know that they can't publish without the thumbnail being published.

I think it makes the most sense if this message only pops up AFTER they click on agreeing to the terms and services. This way they don't see two messages at once saying "You must..." (we don't want to seem too demanding).
This also makes it so that they never see the message until they're actually ready to publish and the thumbnail upload is the only thing preventing them from it.

I was aware of this but didn't file because once the new wallet is inplemented, the response time should be a couple seconds.
Let's keep open until it's confirmed.

You mean it will only take a couple of seconds to upload the thumbnail?

Yes, sorry for not being clearer.

Agreed, we should implement this regardless. I may take a stab at it this weekend, shouldn't be too difficult.

Closed via https://github.com/lbryio/lbry-desktop/pull/1867


show readme before dirs

Now, the readme is after all dirs. I want to add a config option to show readme before dirs.

Readme can now be rendered on top.

https://dir.adriansoftware.de/v3/configuration/
Will be published in next release v3.2.


Simplify travis file

So much simpler :+1: Now all the others :(

👍 Thank

I'll do both improvements at once.


[Feature] Add the YAML to sample YAML tests

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Follow up of https://github.com/ray-project/kuberay/pull/2602
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

/assign @win5923


Attribute in options are not show

<select name="type" class="form-control">     <option value="1" data-column-id="1" data-type="string" data-index="0" data-unique="1">         label 1     </option>     <option value="2" data-column-id="11" data-type="integer" data-index="1" data-unique="1">         label 2     </option>     <option value="3" data-column-id="22" data-type="image" data-index="0" data-unique="0">         label 3     </option>     <option value="4" data-column-id="30" data-type="name" data-index="1" data-unique="0">         label 4     </option> </select>
In this case when I use your choices then I cannot get the selected option data attribute value and don't show any other element to my option attributes.
Thanks

@hirenkeraliya Difficult to see the problem here. Could you provide a reduced test case please highlighting the issue.
Thanks

@jshjohnson Yeah when passing the data attribute to the <option data-type="string">  so how I get the data-type attribute value of the selected option?

@hirenkeraliya  I would recommend adding the data to the customProperties so then it can be access via the event.detail on 'addItem' event

when the change the selection of the select box then I need those custom properties so, how I get those custom properties


More information about a selected file

Hi,
After selecting a file, could you add an option to get more information? (e.g patch, size, dimensions,...)
Thank you.

Do you want an option to get information on selected files (when you are selecting them in the Album view)?

Yes, something like this:

You can already get information about filepath, size, dimensions, ... , when you hit the info button in the image View.

My bad... I was searching from the 3 dots menu.
Thank you.

Could you move the information option on the actionbar or in the 3 dots menu?
I can't open this file so I can't know where it is stored.

I now made it possible to open broken files.

Would this fix your issue?

Yes. I keep the file until the next update.

Fixed now?

Oh yes, thanks.


feat: add support for external sources, from discussion #403

Codecov Report

Merging #406 (cb3d5bd) into main (86ec47e) will increase coverage by 0.14%.
The diff coverage is 90.80%.

@@            Coverage Diff             @@
##             main     #406      +/-   ##
==========================================
+ Coverage   53.04%   53.18%   +0.14%
==========================================
  Files          48       45       -3
  Lines        5405     5377      -28
==========================================
- Hits         2867     2860       -7
+ Misses       2538     2517      -21

Impacted Files
Coverage Δ

lua/neo-tree/sources/common/components.lua
60.09% <ø> (ø)

lua/neo-tree/setup/init.lua
73.08% <78.57%> (-0.06%)
:arrow_down:

lua/neo-tree/sources/manager.lua
66.35% <85.71%> (+0.53%)
:arrow_up:

lua/neo-tree/command/parser.lua
73.39% <98.00%> (+0.49%)
:arrow_up:

lua/neo-tree/defaults.lua
95.90% <100.00%> (+0.06%)
:arrow_up:

lua/neo-tree/sources/common/container.lua
55.05% <0.00%> (-9.56%)
:arrow_down:

lua/neo-tree/sources/filesystem/init.lua
62.44% <0.00%> (+0.42%)
:arrow_up:

lua/neo-tree/utils.lua
49.44% <0.00%> (+0.55%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Does werkzeug have plans to support ASGI?

Werkzeug offers many useful methods, it would be much easier if it supported ASGI than if we started from scratch.

Yes, Werkzeug and Flask will eventually support ASGI. I do not have a timeline for this, although I would be happy to help review a PR if someone started one.

I'm interested in working on this.
I have some working but hacky ASGI support going on: werkzeug, flask. I'd like to understand more about any plans you may have before going any further.
Things that occur to me already, beyond the fact that everything I've done there could be generally nicer:

I'm supporting the form parser by just running its synchronous code in a thread (which I block while I read the data asynchronously). I don't think this will do. My preferred approach would be to factor out the IO.
Context-local support is pretty fragile. There seems to be a right way to do this, but it involves interfering with global state, and especially with ASGI we can't assume we own the world.
There's no obvious way, when running under ASGI, to parse form data on-demand for a synchronous function. It might be worth considering eagerly parsing form data unless we can tell the view function is async. Whatever the default is, there could obviously be a decorator to override it.

Please let me know your thoughts.

I'm supporting the form parser by just running its synchronous code in a thread (which I block while I read the data asynchronously). I don't think this will do. My preferred approach would be to factor out the IO.

I guess the light touch approach will be just to reimplement the existing parser, but with async IO. It'd be cleaner if the two parser classes could share a common sans-IO implementation under the hood, but it might be more practical just to duplicate & slightly modify the existing implementation.

Context-local support is pretty fragile.

Context locals (for asyncio) exist in the 3.7 stdlib. https://docs.python.org/3.7/library/contextvars.html
I'd guess use those, with an optional compat library to support earlier versions of python. (Or else just assume that ASGI on Flask would end up being a 3.7+ thing)
Does werkzeug use thread-locals? (I'm aware that Flask does)

There's no obvious way, when running under ASGI, to parse form data on-demand for a synchronous function

I'd suggest not offering a synchronous interface for parsing form data. (Or for accessing the request body in any way), and instead just offer async APIs onto it. See Starlette's API for some examples here... https://github.com/encode/starlette#body

Since Python 3.7 is out I wouldn't be opposed to having async features requiring Python 3.7 as long as no other code is affected by it. But if there's a backport that's as good as the native 3.7 solution - even better!

Sure, or just make values and friends asynchronous themselves: values = await request.values or values = await request.values(), depending mostly on which looks nicer.

wouldn't that require rather ugly things like (await request.form)['foo'] to do an async call while getting a dict element directly without assigning in between?

yes :(
I'm not sure that's particularly avoidable, though. I don't think
form = await request.form
form['foo']

is really any more or less ugly than
await request.parse()
request.form['foo']

though that's obviously subject to taste.
I guess we could also invent an "async dict" whose members are all async-ified instead, but without having seen one I'd imagine it would end up rather confusing.

Sure, or just make values and friends asynchronous themselves: values = await request.values or values = await request.values(), depending mostly on which looks nicer.

I'd suggest using function calls for I/O-performing operations, rather than properties.

wouldn't that require rather ugly things like (await request.form)['foo'] to do an async call while getting a dict element directly without assigning in between?

Shrug - Don't do that.
asyncio is necessarily more explicit about which parts of the codebase perform I/O, so I'd tend to split those out into separate lines.
form = await request.form()
form['foo']

While I'm all for adding async support, we still can't break Python 2 and sync versions. One approach I heard about from @njsmith is to write everything as async, then use a tool similar to 2to3 to generate the sync version. Apparently it's being tried in urllib3, but I don't know enough about it.

I wonder if we could add magic to the objects behind request.form etc. so calling them will do async stuff while the usual dict-like methods will be sync (and would fail in async mode). Or we could just fail any access to request.form etc. in async mode and use a separate name for the async versions, e.g. request.parse_form().
Or... request_class = AsyncRequest if someone wants async; this could actually be a default in an AsyncFlask class.

Or... request_class = AsyncRequest if someone wants async; this could actually be a default in an AsyncFlask class.

That's the sort of approach that'd make sense to me, yeah.

Regarding the form parser, I've made an attempt at sansio-ing it in #1330.

There's also a streaming form parser implementation at https://github.com/andrew-d/python-multipart with 100% coverage. (I found one other but it wasn't obvious that it could be easily adapted into a "feed data, handle events" flow.)
python-multipart is the library I'm now using for Starlette. You can take a look at the integration with the async stream here: https://github.com/encode/starlette/blob/master/starlette/formparsers.py#L207

I've also been thinking about best ways to present a sync and async compatible interface, since I also want that for Starlette (although going in the other direction to Werkzeug, for me it's about "I have an existing async interface, how do I now also present a sync one")
For Starlette I think I'll probably push the actual parsing into an async parse(self) method, and typically call that sometime during request dispatch, but expose regular plain properties form, files etc... for accessing the results from user code.

Off topic, but related to a popular ASGI and werkzeug case (I don't want to derail this issue, but don't want to create a duplicate issue without substance to add):
If you're running https://github.com/django-extensions/django-extensions with ./manage.py runserver_plus and https://github.com/django/channels (which uses ASGI) is giving Opcode -1 (opcode minus 1) in inspector, try running ./manage.py runserver for now until ASGI is supported.
(Werkzeug is used underneath the hood on Django with django-extensions and I spent a few hours figuring out why since I'm so used to developing with runserver_plus for debugging)

I use runserver_plus so that I can use https in development.
I am now trying to add Websockets support using Django channels, and have run into the issue that the channels uses runserver and does nto support runserver_plus. So, I can use channels OR I can use https, not both!

@davidism please tell me if there are any changes in the implementation of ASGI support for Flask since your last answer in this topic and whether your plans have changed in connection with this task to end support for Python 2 ?

Apparently it's being tried in urllib3, but I don't know enough about it.
Just saw this from a while back

Small bump to make this issue back on the radar. With 3.5 reaching EOL this year, I think it's a good time to start thinking about async support?

In the year and a half since this was posted, there hasn't been much activity to implement it. I don't personally have any experience or need for asyncio, and although I do like ASGI, it was never something that I was going to take on myself.
In the mean time, @pgjones, author of Quart, has become more involved in Werkzeug. Quart now uses Werkzeug behind the scenes where possible, and we're continuing to develop that. There was some pushback from a Flask maintainer about going with ASGI, so he also created pallets/flask#3412 that at least allowed routing to async def functions, but that has been sitting for a while now. At this point I'd rather go ASGI than settle for that.
You might ask, "Why can't Flask do what Django did?" I am not an expert on the internals of Django, but @andrewgodwin explained to me a while ago that Django has an "easier" time of it due to how it originally adapted to WSGI, as opposed to the very WSGI-centric API that Werkzeug and Flask started with. Also, Django just gets a ton more full time attention and resources than Pallets does.
So where does that leave this issue? If you want a Flask-compatible framework that uses Werkzeug, use Quart. Contribute to Quart (or Flask) to make them more API compatible where that's missing. If you want Werkzeug and Flask to support ASGI, you are going to need to step up. Start learning about ASGI. Start identifying the WSGI-specific and blocking parts of Werkzeug's API. Start thinking of abstractions we can make to enable implementations for both WSGI and ASGI. Then bring that research back to this discussion so we can start designing and writing PRs.

Thanks for the Quart suggestion, I'd be very happy to accept contributions to it.
I've tried to answer why I think Flask can't do what Django has done in this article. Ultimately I think pallets/flask#3412 is the best solution for Flask.
In terms of Werkzeug I think that ASGI is possible, with some pain. A notable example of the pain is that many things in Werkzeug are WSGI callables (e.g. exceptions). With ASGI it isn't clear how this functionality could/should be used, so I'd prefer to remove it.
My plan is to keep integrating Werkzeug into Quart adjusting Werkzeug towards ASGI (sans-io) as I go (as much as can be accepted) - my only obstacle is a lack of time.

I've been using Quart lately and I'm very happy with it. It would gain much more attention if its name was Flask 2.


Implement the linter strategy starting by LSP

/cc @slrtbtfs
Offline linter will come later

Related to #5

:+1: besides comment

It might be worth investigating whether it's possible to additionally show those error messages below the editor, without having to hover over the red lines.

No idea if it's possible, but otherwise it's how the IDE are working in generally, and I didn't think it was so bad. But maybe it's just me hahaha


Use world units for point sizes

By default,  uses the scale property to determine the size of all points. gl_PointSize expects values in pixels rather than in units in world space, though.
The changes in this commit introduce a new optional flag to use world space point sizes instead of pixels. In order to accomplish that goal, the vertex shader computes a scaled point size based on the current view transformation and render target size.
Test plan: Added new stories for <Points /> command, using both screen and world space point sizes with unit cubes for reference.
Versioning impact
Minor: the new flag is used to ensure backward compatibility

I guess the part that's left is figuring out how to integrate this with the rest of Webviz, any ideas here? I.e. Jason's issue here is rendering points from MarkerArray.

The optional useWorldSpaceSize  flag allows Worldview to remain generic, supporting both render modes (screen and world space), since it doesn't really know about markers. In Webviz, we need to use that flag so point markers will be always rendered in world space. This is a similar to how we handle screen invariance in <GLText />, which is always enabled in Webviz.
Does that make sense?

The optional useWorldSpaceSize flag allows Worldview to remain generic, supporting both render modes (screen and world space), since it doesn't really know about markers. In Webviz, we need to use that flag so point markers will be always rendered in world space. This is a similar to how we handle screen invariance in , which is always enabled in Webviz.
Does that make sense?

Yea totally! I guess my real question here is whether adding this flag on by default in Webviz will be backwards compatible with many of the points we already display. Lidar points seem easy, since we control how they're rendered. However, for example, I don't have a good sense how much folks rely on MarkerArray points in production.


Text Expander

Description of the new feature / enhancement
A text expander that detects when you type a specific keyword and replaces it with something else is very usefull.
Scenario when this would be used?
A textexpander helps me write much faster when I take notes in college because it allows me to replace keywords with whole sentences or complicated words. I use it a lot to write Latex math equations very fast, but it can also be used while programming and in all contexts where you have to write the same words many times.
Supporting information
Now I'm using Espanso as text expander. This is his GitHub repository: https://github.com/espanso/espanso

AutoHotkey could do this without breaking a sweat!

+1

/dup https://github.com/microsoft/PowerToys/issues/5074


remove ref to archive, typos

FAQ entry mentioned CSC archive, simplified language a bit, too

related to #523


Flag provided but not defined.

[root@server]/tmp/websocketd# ./websocketd \
--address "[::]" \
--port 3030 \
--binary true \
../ws_server
flag provided but not defined: -binary

Usage:

  Export a single executable program a WebSocket server:
    websocketd [options] COMMAND [command args]

  Or, export an entire directory of executables as WebSocket endpoints:
    websocketd [options] --dir=SOMEDIR

  Or, show extended help message using:
    websocketd --help

--version ?

websocketd 0.2.11 (go1.4.2 linux-amd64) -- - I get it here - http://websocketd.com/#download

https://github.com/joewalnes/websocketd/releases pleasse try 0.2.12 from here


Add ability to mark pkg repository as "view-only" so that packages are not available to be installed

Describe the problem/challenge you have
It might be useful for user to add a package repository to view its contents but not have kapp-controller use it for installation (as part of auto updates).
this is also useful for when you would like to add a pkg repo to a mgmt cluster to view contents, but do not want those packages be available for install on the mgmt cluster itself.

I could see this being helpful if someone wants to know more about a PackageRepo before making its Packages available to end users. Will accept this.

One possible approach is to shift this experience to the kapp-controller CLI. This would allow a user to see what the contents of a PackageRepository source is.
Other user experiences like a UI could also show the PackageRepository contents in their own way to users.

cc @renuy -- idea for kctrl package experience


feat(vue-app): support app/router.scrollBehavior.js and deprecate scrollBehavior

This PR allows to overwrite application and modules templates with the app/ directory directly.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Not really a feature, but a refactor to move the router scrollBehavior to router.scrollBehavior.js.
Why?
In order to stop serializing function and start opening another way of changing the scrollBehavior with a file.
It also avoid restarting the whole Nuxt application since it's actually a config related to the Vue app.
Before:
// nuxt.config.js
export default {
  router: {
    scrollBehavior: function (to, from, savedPosition) {
       return { x: 0, y: 0 }
    }
  }
}

After:
// app/router.scrollBehavior.js
export default function(to, from, savedPosition) {
  return { x: 0, y: 0 }
}

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly. (PR: https://github.com/nuxt/docs/pull/1472)
[x] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

YES, thank you -- I was getting close to going down the acorn rabbit hole just to write us a working serializeFunction. It's definitely much better to have these imported as live JavaScript instead.

I plan to do the same logic to most of the configuration option that have to be serialised (head, transition, etc) 😄

Codecov Report

Merging #6055 into dev will increase coverage by 45.56%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              dev    #6055       +/-   ##
===========================================
+ Coverage   50.12%   95.69%   +45.56%
===========================================
  Files          82       82
  Lines        2695     2695
  Branches      692      692
===========================================
+ Hits         1351     2579     +1228
+ Misses       1035       98      -937
+ Partials      309       18      -291

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.12% <ø> (ø)
:arrow_up:

#unit
92.8% <ø> (?)

Impacted Files
Coverage Δ

packages/vue-app/src/index.js
0% <ø> (ø)
:arrow_up:

packages/webpack/src/config/server.js
100% <0%> (+3.12%)
:arrow_up:

packages/webpack/src/utils/perf-loader.js
100% <0%> (+5.26%)
:arrow_up:

packages/utils/src/lang.js
100% <0%> (+6.66%)
:arrow_up:

packages/webpack/src/config/base.js
94.94% <0%> (+7.07%)
:arrow_up:

packages/webpack/src/config/client.js
98.18% <0%> (+7.27%)
:arrow_up:

packages/core/src/module.js
98.33% <0%> (+10%)
:arrow_up:

packages/utils/src/context.js
100% <0%> (+11.11%)
:arrow_up:

packages/cli/src/commands/index.js
11.11% <0%> (+11.11%)
:arrow_up:

packages/utils/src/resolve.js
96.07% <0%> (+13.72%)
:arrow_up:

... and 48 more

Continue to review full report at Codecov.

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

I need to add support for watching app/**/*.(js|vue) when creating or removing file there.

Watching app/ is done, I also added dir.app key in config

We can now overwrites custom templates given in build.templates with app/${dst}.
Example of a module adding press/common/pages/source.vue with this.addTemplate(), the user could overwrite it by adding app/common/pages/source.vue.
Nuxt will automatically watch the app/ dir and handle file added/updated/removed for it so the module author won't have to deal with watchers.

@pimlie actually it was already doing this since a long time (can't remember the version). Actually i found the name perfect to overwrite our default vue-app template (and also modules like NuxtPress: app/press/common/pages/source.vue)

Good catch for typings Kevin, I think it's fine if they have autocomplete and then Nuxt warning 🤔

2.9.0 notes updated to mention

I really like the fact that we avoid serialization with that step, however (as briefly discussed with @Atinux), this means we can't provide data from the nuxt.config.js inside such a external file in app (at the moment at least). For scrollBevahior, this might not have a huge impact, however for further split ups of things like transitions or head it could create a few problems if we don't handle it. :relaxed:


Doesn't work in build

Hi, thanks for the view cone it works well but i'm trying to make it work on unity HDRP 2021.3.16f1 and it doesn't work when i build my project (it goes through obstacles)

Could reproduce - seems like the cameras are not recording any depth.
Build:

Editor:

IDK why. It could be the custom pass code - maybe something changed in the API. Or maybe something else.
It's not because ...

Cameras are disabled
Textures are not assigned (they are)
The Shader not existing in the build (it's compiled and shipped with the build)
The Custom Pass shader not existing in the build (there is no custom pass shader, it just executes the C# code - also it's linked in the Enemy prefab and EnemyVisionCone script, so it has to exist in the build)

Yea, I don't really know what else I could check. Any help is appreciated.

Hi, anything new concerning the issue ?


Need a centralized repo for datafiles

https://github.com/gaia-unlimited/gaiaunlimited/blob/e5e44c5a93eb8a3a22de9138a10bd66946609c3a/src/gaiaunlimited/selectionfunctions/surveyTCG.py#LL73C53-L73C53

All non-ESA files uploaded to Zenodo:
Data for emprical selection function paper: https://zenodo.org/record/8063930
Legacy files for the GaiaUnlimited tools: https://zenodo.org/record/8300616


Cloud Ops API README udpate

What was changed

The README file has been updated with the following information:

Change from Preview to Public Preview to indicate this is prod quality and an unstable API
Add a bit more context to the How to Use section
Added Steve A's examples to the Samples section
Added more context about the Go Samples in the Samples section

Why?

This was done to assist users in using the Cloud Ops API
Checklist

Closes
n/a

How was this tested:

n/a

Any docs updates needed?

README is the only change made

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


add guideline: Node.js version usage & support

What version(s) of Node.js should be run in a development, CI, or production environment?  Evaluate risk of running EOL Node.js versions in these environments.
For OSS projects, should the minimum supported Node.js version track the above?  When can OSS projects drop an old version of Node.js, when should they, and when must they?
Any special considerations for odd-numbered releases?  These versions do not enter LTS and have a lifespan of about nine months.
Given Node.js has a documented release cadence--a version going EOL should not be a surprise--how should projects use this info to stay within the guidelines over time?

We've also had questions around:

what the engines.node field in package.json represents and how that relates to the current, past, and future versions of Node (considering that Yarn v2+ ignores it by default when installing dependencies)
what .nvmrc represents and what its relationship to engines.node is
how the versions of Node we test (i.e. the matrix we use in CI) relate to both of these

Perhaps we ought to use this space to clarify these as well?


DelayBetweenAnalyzingFrames not working with ZXingScannerFragment.

Tried to use the ZXingScannerFragment with similar way provided in sample code and also tried using CustomOverlay as well. Well most of the features works but DelayBetweenAnalyzingFrames  and CustomOverlay not working with this in android. Also I was stuck when i am trying to provide a click listner for camera view and which also fails by not catching events. Anyone please help me on these.

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!


Bug: didyoumean monitor

I had a couple of issues with this monitor.

Tried downloading and it never downloaded over 15 minutes long. Console showed npm install completed in about 10 seconds. package.json was also updated. However, the file was never downloaded and the bot was stuck on saying Loading Monitors. It is hours later and still, that message says Loading Monitors.

I finally managed to get it installed by doing download the third time. After which I discovered some more errors with it. I believe these errors may be occurring only in 0.20.5, nonetheless, I think it is worth reporting.

Line 7: const conf = client.configuration.get(msg.guild); This calls something called configuration but configuration is undefined.

Point 1 was already discussed with you on the support channel, pm2 --watch will leave the message saying Loading Monitors as it now has no idea what to edit/ it's a blank slate
Point 2 occurs because the pieces will most likely be outdated for Komada Indev and only work for Komada 0.19.7

Actually Cyber, all the pieces are retrocompatible, with exception of the ones which uses the configuration system (KConfigs vs SettingGateway)

So is it confirmed that this monitor is not compatible due to the SettingGateway? Is there any way someone could update the file with perhaps a comment to show anyone like me using the beta on how to convert it so it is SettingGateway friendly please

Exactly, it's not compatible because of SettingGateway, but it goes much further: It uses methods and properties from 0.18.1-0.19.7 that are not longer in Komada since 0.20.0.
Currently I'm very busy, but if you want to use it and you don't know how to fix it, I'll try to find a way to make it work, and I'll attach it in a comment so people who use indev can use the link instead and get a fully working piece.
However, the methods that are used to reproduce what DidYouMean does has changed in the last commits, so I can't ensure it'll work completely in the future.

Leave it be then. Don't worry too much it was just a cool addition I was hoping had a small fix for the new settings.

The DidYouMean piece will be rewritten along all the pieces for an update, soon.

In the current architecture from Komada 0.20.x (and also Klasa), this piece is not longer viable as this makes Komada parse the prefix and command twice.

This piece got modified in #98, test it and let me know if it works.

No response, I'll close this. Feel free to re-open if you have any issue.


Dask Helm Chart - Ingress Route error

I'm having issues installing dask-gateway helm chart.
I followed the revised version of the helm installation procedure:
microk8s helm repo add daskgateway https://dask.org/dask-gateway-helm-repo/
microk8s helm repo update
microk8s helm upgrade --install \
>     --namespace $NAMESPACE \
>     --version $VERSION \
>     --values path/to/your/config.yaml \
>     $RELEASE \
>     daskgateway/dask-gateway

I have the following error:
Error: validation failed: [unable to recognize "": no matches for kind "IngressRoute" in version "traefik.containo.us/v1alpha1", unable to recognize "": no matches for kind "Middleware" in version "traefik.containo.us/v1alpha1"]

Please help with this issue.
Thanks,

This is solved by creating the crd objects per the provided traefik.yaml file.
Thanks,

@vinhdiesal I am having the same issue. How did you end up providing the traefik.yaml file to helm?


fix(markdown): escape dollar symbol when doing replacement

Fixes #4931
https://github.com/facebook/lexical/assets/6022672/ed92ec13-674a-4185-932f-d371db469711

Closing this PR due to staleness! If there are new updates, please reopen the PR.


When UC options get filtered the first option does not cacscade value changes

Happy new year @kinow ! Hope 2015 produces a record deficit of bugs!
This one does not get logged towards 2015 since I've detected it before going on holidays ;-)
When applying a filter to uno-choice options the first value on the resulting list does not trigger cascade changes.
See http://<IP_ADDRESS>:8080/job/issue-70
In or famous state-cities example when the option list contains a single state, I can't cascade it's change to update the cities.

Originally I thought that this bug only affected a list that filtering reduced to a single value, but I think that this happens even when the list has moire than one values selected by the filter (try this example).

Hope you are well refreshed after the holidays!
best regards
Ioannis

Happy new year @imoutsatsos !!!
Hmmm, interesting issue... maybe I've overseen it during our tests, because I think I remember having this problem somewhere in the past.
I'll finish some development cycle on other tools and will get back at BioUno development within some days. Stay tuned for a wave of issue fixes (hopefully fixes + tests) :)

Added a simple propagation event, so that when the filter gets updated (i.e. the user enters a key in the filter input box) it tells the parameter that it changed.
We need to test if this new event is not interfering with other elements. But I think it will work. We don't have tests covering event propagation yet.

This seems to work as expected now. I have not observed any other issues, but I'm still doing some additional testing with a bunch of projects that I have migrated to v0.23. Thanks for completing another 1.0 milestone @kinow !

Yay! Thanks @imoutsatsos ! With every issue we get closer to 1.0! \o/

Seems to be working now in 1.0. Please feel free to re-open an issue in https://issues.jenkins-ci.org/ with component name active-choices-plugin in case the issue persists. Thanks!


Python 3.11 compatibility

Hi,
the current release worked fine with Python 3.9 but we recently switched to Python 3.11 and now it looks like PyExt isn't working anymore. Is there any chance to get this working with 3.11?
After calling !pystack I just get the following error in WinDbg:
************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Deferred                                       srvc:\symbolshttp://pythonsymbols.sdcline.com/symbols/
Symbol search path is: srv*;srvc:\symbolshttp://pythonsymbols.sdcline.com/symbols/
Executable search path is:
Windows 10 Version 17763 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Debug session time: Thu Feb  2 01:29:45.000 2023 (UTC + 1:00)
System Uptime: 15 days 16:39:34.970
Process Uptime: 0 days 0:00:11.000
................................................................
.............
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2288.320c): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffa`5e931344 c3              ret
0:006> .load pyext
0:006> !pystack
Thread 6:
ERROR: !pystack: extension exception 0x80004002.
"ExtRemoteTyped::Field: unable to retrieve field 'tstate_head' at 7ffa374ee200"

It looks like CPython moved PyInterpreterState.tstate_head into a nested struct, PyInterpreterState.threads.head in this commit
It should be doable to add an extra check here to look for the head in its new location first, but fall back on the old location for Python <3.11 support.
The extension has to do this sort of trick whenever CPython moves its internal members around. For example, here's how it handles the possible locations of the PyInterpreterState.

It turns out this is actually a bit more difficult. The tstate_head to threads.head change was easy, but CPython 3.11 also changed how stack frames work considerably. It looks like PyFrameObject are now lazy-constructed and rely on on a new _PyInterpreterFrame which is missing many of the members we need to construct a helpful callstack.
Looking at how the new frame data structures work, it should still be possible to generate a bare call stack, missing line numbers, I don't have a lot of free time to put into supporting the new stack frame format, but if nobody else pitches in, I'll probably get around to it someday.

Hey, any updates on whether or not 3.11 will be supported any time soon?


Improve setting option values, and add user events

Add user events to allow the user to customize the indentation after the
detection, to fix some options that might be inherited from the initial
configuration. Allows to customize via the configuration which options
are set.
When tabs are detected, set shiftwidth=0 to ensure that the shifting
value is the same as the tabstop. Same with softtabstop=0 to disable it.
When spaces are detected, make optional setting of the tabstop and
softtabstop option.
Use case: In my init.vim I set default indent options for empty files:
set sw=2 sts=0 ts=8 et

When guess-indent detects a file with tabs, it needs to be able to override these values.
Also, I prefer to always keep a tabstop of 8 characters, so I prefer not to have the value changed. And I also prefer to keep the softtabstop option disabled, but if it is enabled when spaces are detected, it needs to be disabled wen tabs are detected.

Should have been adressed by #17.


Official plugin?

Is this plugin going to be installable from Figma?

Hi @plainspace! It won't, simply because it's not built to walk you through setting up a theme and is hard coded right now to work with Discord. However, I did document it so other teams could hard code their own values for each theme and use as they liked!
Official plugins require using jsonbin.io or other login services to sync which I didn't want to deal with since our team can just use this!
Hope that makes sense!


Links to FoD/SSC prep pages in docs don't work.  (Capitalization mismatch)

https://github.com/fortify-ps/FortifyBugTrackerUtility/blob/3107fce8b9c5334fe9c3a06aa82fc529659619aa/bugtracker/src/site/site.xml#L35-L36
These capitalization of these hyperlinks appear to not match the names of the actual target HTML files.  For example, this is what I get when I click on "Preperations -> SSC" in a web browser:

Thanks for reporting this, I guess most users read the documentation from case-insensitive Windows filesystems. I've now fixed the links, new release should be posted later today.


fix: check installplan status in bundle e2e test

Description of the change:
Motivation for the change:
Reduce flakiness of bundle with additional objects e2e test.
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

2020-07-10T15:22:31.9409853Z     Timed out after 60.000s.
2020-07-10T15:22:31.9410158Z     expected no error finding vpa object associated with csv
2020-07-10T15:22:31.9410383Z     Expected success, but got an error:
2020-07-10T15:22:31.9410835Z         <*errors.StatusError | 0xc000b85cc0>: {
2020-07-10T15:22:31.9410958Z             ErrStatus: {
2020-07-10T15:22:31.9411081Z                 TypeMeta: {Kind: "Status", APIVersion: "v1"},
2020-07-10T15:22:31.9411200Z                 ListMeta: {
2020-07-10T15:22:31.9411315Z                     SelfLink: "",
2020-07-10T15:22:31.9411432Z                     ResourceVersion: "",
2020-07-10T15:22:31.9411545Z                     Continue: "",
2020-07-10T15:22:31.9411636Z                     RemainingItemCount: nil,
2020-07-10T15:22:31.9411752Z                 },
2020-07-10T15:22:31.9411863Z                 Status: "Failure",
2020-07-10T15:22:31.9412203Z                 Message: "verticalpodautoscalers.autoscaling.k8s.io \"busybox-vpa\" not found",
2020-07-10T15:22:31.9412339Z                 Reason: "NotFound",
2020-07-10T15:22:31.9412654Z                 Details: {
2020-07-10T15:22:31.9412905Z                     Name: "busybox-vpa",
2020-07-10T15:22:31.9413172Z                     Group: "autoscaling.k8s.io",
2020-07-10T15:22:31.9413299Z                     Kind: "verticalpodautoscalers",
2020-07-10T15:22:31.9413416Z                     UID: "",
2020-07-10T15:22:31.9413531Z                     Causes: nil,
2020-07-10T15:22:31.9413647Z                     RetryAfterSeconds: 0,
2020-07-10T15:22:31.9413757Z                 },
2020-07-10T15:22:31.9413867Z                 Code: 404,
2020-07-10T15:22:31.9413976Z             },
2020-07-10T15:22:31.9414060Z         }
2020-07-10T15:22:31.9414530Z         verticalpodautoscalers.autoscaling.k8s.io "busybox-vpa" not found

^ Sample failure here. If this is what we're seeing in general, I think there may be a deeper issue with conflicting test setup or even with OLM's reconciliation. The fact that it still doesn't exist after 60 seconds is suspicious to me.

I was troubleshooting this with @ecordell locally and it looks like the VPA CRD installplan stepresource gets stuck in WaitingforAPI even though the VPA CRD itself is established and accepted on-cluster. So this causes the e2e test to fail (on the first run) locally. However it sometimes passes, as we've seen when it gets through CI.
I think there was also a question of whether the VPA is shipped in OpenShift by default and the provided CRD is unnecessary - but I could not find a reference to the VPA CRD in a stock clusterbot cluster.

WaitingforAPI even though the VPA CRD itself is established and accepted on-cluster. So this causes the e2e test to fail (on the first run) locally. However it sometimes passes, as we've seen when it gets through CI.

Do we ensure CRDs are ordered before any CRs? If so, what happens if the CR is applied by the InstallPlan while the API is unavailable? Are we resyncing InstallPlans in this state when CRDs they've applied have changed?

WaitingforAPI even though the VPA CRD itself is established and accepted on-cluster. So this causes the e2e test to fail (on the first run) locally. However it sometimes passes, as we've seen when it gets through CI.

Do we ensure CRDs are ordered before any CRs? If so, what happens if the CR is applied by the InstallPlan while the API is unavailable? Are we resyncing InstallPlans in this state when CRDs they've applied have changed?

We do ensure that CRDs are created first (they are the first thing that gets reconciled in ExecutePlan). We don't currently have a check in our dynamic object creation that the CR that is attempting to be created actually has the associated CRD in a ready and established state on the cluster (which I think you're getting at). So potentially we have a race here, where sometimes the VPA CRD is still in WaitingforApi before the VPA CR is created from the bundle. That would explain the flakiness. I wonder if we would have this issue with the prometheus objects @awgreene added as well though?
Yes, we should be re-syncing the installplan with respect to the CRDs. The code certain looks that way. The issue here is that it looks like the sync is not happening fast enough?

So with this change instead of creating VPA CRs before the VPA CRD is Complete, the InstallPlan check will fail and the test will fail there.
A little confusing since a lot of the flakes we saw where around the PDB not so much the VPA. I think this fix helps with the PDB check (we were checking too early, before the installplan got a chance to create it) but uncovered another issue with the VPA object.

Personally I think this PR addresses the original intended issues and makes things marginally better so we could merge and address the potential race we uncovered in a follow-up. Thoughts @njhale @ecordell

/lgtm

/approve


bugfix: fix pkg as_name check in resolver.

fix bug about import pkg with as_name
import a as b
a.xxx

It should be emit err in resolver, then this error can be checked in lint and IDE.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):
sema/resolver

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

change module kind scope object key and obj name to import_stmt.name, instead of import_stmt.path
fn resolver_var use names[0] instead of pkg_path

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 87.787%

Files with Coverage Reduction
New Missed Lines
%

compiler_base/parallel/src/executor/timeout.rs
1
92.98%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
2293

Relevant Lines:
2612

💛  - Coveralls


Add cache_dir config for save HFTransformersNLP pre-trained model data.

Proposed changes:

Add cache_dir for save HFTransformersNLP pre-trained model data

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Thanks for submitting a pull request 🚀 The assigned reviewer will take a look at it as soon as possible✨


pre-install: Setup nydus-snapshotter

This is a patch to setup remote snapshotter instead forked containerd in CoCo. As discussed in https://github.com/kata-containers/kata-containers/issues/7658, operator is responsible to set up the snapshotter.

Let me take a look here and then I will provide you some pointers.

Actually, I think we can pass the snapshotter as an env var here.

Simply doing make reqs-image fails for me with the following errors:
...
 => CACHED [nydus-binary-downloader 2/4] RUN mkdir -p /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     apk add --no-cache ca-certificates build-base git curl &&     git clone https://github.com/containerd/nydus-snapshotter -b main /nydus-snapshotter &&     make -C /nydus-snapshotter &&     chmod +x /nydus-snapshotter/bin/containe  0.0s
 => ERROR [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-p  0.2s
------
 > [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     rm -rf /nydus-static /nydus-static-v2.2.3-linux-s390x.tgz:
------
Dockerfile:80
--------------------
  79 |
  80 | >>> RUN [ "${ARCH}" != "s390x" ] && \
  81 | >>>     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz && \
  82 | >>>     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / && \
  83 | >>>     chmod +x /nydus-static/nydus-image && \
  84 | >>>     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin && \
  85 | >>>     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz
  86 |
--------------------
ERROR: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c [ \"${ARCH}\" != \"s390x\" ] &&     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz &&     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin &&     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz" did not complete successfully: exit code: 1
make: *** [Makefile:10: reqs-image] Error 1

Here are the commands that I ran:
export registry=quay.io/surajd/reqs-payload
pushd install/pre-install-payload
make reqs-image

Simply doing make reqs-image fails for me with the following errors:
...
 => CACHED [nydus-binary-downloader 2/4] RUN mkdir -p /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     apk add --no-cache ca-certificates build-base git curl &&     git clone https://github.com/containerd/nydus-snapshotter -b main /nydus-snapshotter &&     make -C /nydus-snapshotter &&     chmod +x /nydus-snapshotter/bin/containe  0.0s
 => ERROR [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-p  0.2s
------
 > [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     rm -rf /nydus-static /nydus-static-v2.2.3-linux-s390x.tgz:
------
Dockerfile:80
--------------------
  79 |
  80 | >>> RUN [ "${ARCH}" != "s390x" ] && \
  81 | >>>     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz && \
  82 | >>>     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / && \
  83 | >>>     chmod +x /nydus-static/nydus-image && \
  84 | >>>     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin && \
  85 | >>>     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz
  86 |
--------------------
ERROR: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c [ \"${ARCH}\" != \"s390x\" ] &&     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz &&     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin &&     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz" did not complete successfully: exit code: 1
make: *** [Makefile:10: reqs-image] Error 1

Here are the commands that I ran:
export registry=quay.io/surajd/reqs-payload
pushd install/pre-install-payload
make reqs-image

Do I need anything else I should be doing?

Thanks for your information. Let me take a look.

Simply doing make reqs-image fails for me with the following errors:
...
 => CACHED [nydus-binary-downloader 2/4] RUN mkdir -p /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     apk add --no-cache ca-certificates build-base git curl &&     git clone https://github.com/containerd/nydus-snapshotter -b main /nydus-snapshotter &&     make -C /nydus-snapshotter &&     chmod +x /nydus-snapshotter/bin/containe  0.0s
 => ERROR [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-p  0.2s
------
 > [nydus-binary-downloader 3/4] RUN [ "s390x" != "s390x" ] &&     curl -fOL --progress-bar https://github.com/dragonflyoss/image-service/releases/download/v2.2.3/nydus-static-v2.2.3-linux-s390x.tgz &&     tar xvzpf nydus-static-v2.2.3-linux-s390x.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image /opt/confidential-containers-pre-install-artifacts/opt/confidential-containers/bin &&     rm -rf /nydus-static /nydus-static-v2.2.3-linux-s390x.tgz:
------
Dockerfile:80
--------------------
  79 |
  80 | >>> RUN [ "${ARCH}" != "s390x" ] && \
  81 | >>>     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz && \
  82 | >>>     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / && \
  83 | >>>     chmod +x /nydus-static/nydus-image && \
  84 | >>>     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin && \
  85 | >>>     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz
  86 |
--------------------
ERROR: failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c [ \"${ARCH}\" != \"s390x\" ] &&     curl -fOL --progress-bar ${NYDUS_REPO}/releases/download/${NYDUS_VERSION}/nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz &&     tar xvzpf nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz -C / &&     chmod +x /nydus-static/nydus-image &&     mv /nydus-static/nydus-image ${NODE_DESTINATION}/bin &&     rm -rf /nydus-static /nydus-static-${NYDUS_VERSION}-linux-${ARCH}.tgz" did not complete successfully: exit code: 1
make: *** [Makefile:10: reqs-image] Error 1

Here are the commands that I ran:
export registry=quay.io/surajd/reqs-payload
pushd install/pre-install-payload
make reqs-image

Do I need anything else I should be doing?

That's the error in downloading nydus and I have fixed it. Please try again. Thanks.

/test

@ChengyuZhu6 yes the build worked fine, I will try to deploy this now.

I was able to do the regular operator installation with this.

@ChengyuZhu6, I'm closing this one as your commit was part of https://github.com/confidential-containers/operator/pull/267


"John" and 156 do not exist in the if else statements

Challenge Replacing If Else Chains with Switch has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function chainToSwitch(val) {
  var answer = "";
  // Only change code below this line

  switch(val){

    case "bob":
    answer = "Marley";
    break;

    case 42:
    answer = "The Answer";
     break;

    case 1:
    answer = "There is no #1";
     break;

    case 99:
    answer = "Missed me by this much!";
    break;

    default:
    answer = "Ate Nine";

  }

  // Only change code above this line
  return answer;
}

// Change this value to test
chainToSwitch(7);

I get the following errors because "John" ans 156 are not in the original if else statements.
chainToSwitch("John") should be "" (empty string)
chainToSwitch(156) should be "" (empty string)

Your code is incorrect. Please use the Help chat room for getting challenge related help. Happy Coding!


Fricton or Friction

There is a typo in friction firld/property/option it is missing secind "i" and is 'fricton' it break in react version

OMG it's 'friction'! I misspell the word for years!
The fix of this may cause breaks, if you don't mind I'd like to fix it in the next major release(i.e. v5.x.x).


Optimise copy[-*] icons/add copy-down (download all/generic clone) icon

copy-down can be a generic clone icon, 'download all' or downloads…
copy-file-path is self-explanatory… Useful in editors.
copy-image self-explanatory, but also can be photos/album/gallery…
copy-type is copy with formatting (closely related to #1298)

This PR is merged to the lab branch. This PR does not match our PR template, which requires valid use cases. To move on we merged this PR to the lab branch, which will be moved to a separate repo in the future.


How to update comments style, like height, bgColor?

Hello,
How to update comments style, like height, bgColor?
Thanks

This is a feature we currently offer in our Pro compendium.  We hope to eventually merge changes here but that will be after a 1.0.0 release


Fixes to the Python version of Hamurabi

I tried playing the python version and discovered a bug that makes it unplayable.
Unless the rats eat some of the food (50% chance per turn),
your harvest wasn't added to the total.
This was due to an indentation error, so the calculation for total bushels was
included in the rat condition.
The other commit checks the amount of people available to harvest the fields.
In the rules, each person is supposed to be able to harvest 10 acres, but the
code as written doesn't like you harvest that maximum.
However, I think that bug was in the original code.

Thank you for these fixes!


How to make it work with tern-lint?

Are there any gotchas for best IDE-level javascript linting and syntax highlighting? When I run tern-lint I get out of memory errors or call stack size exceeded.

What exactly gives you out of memory errors and stack size exceeded?

So your tern-lint crashes under its own weight.  Perhaps you should report that to some Tern forum?

yes, of course, but may be you have some experience with it.  This is one big issue, it's not just about tags, it's about syntastic also https://github.com/ramitos/jsctags/issues/50

may be you have some experience with it.

I believe I used tern-lint exactly the ~10 minutes it took to write a syntastic checker for it.  Aside from some other ~5 minutes reading the docs, that's about my entire experience with it.

This is one big issue, it's not just about tags, it's about syntastic also https://github.com/ramitos/jsctags/issues/50

What syntastic does is run tern-lint against your files, and parse the resulting JSON.  As far as syntastic is concerned the data involved is tiny, and munging it is completely straightforward.  Unless you can point to a case where syntastic doesn't parse tern-lint results correctly, there is very little help you can get here.  Sorry about that.


Add a link to the live version

When someone finds this repository, they have to use Google to find the web address and it doesn't appear on the first page of Google results (at least for me).
It would be convenient to have a link to https://campexplorer.io/ either in the readme or in the github repo description.
And possibly a link to install the extension as well, although that is the first google result for me.

Sorry for the slow response, thought I had already responded. Great idea! I never thought that people would find this repository first but instead that they would come here from the website itself. Adding it to the readme and description now.


Models with init_score

The current code uses init_score to inject starting values, but what about modeling problems that need to use init_score to represent an offset, e.g. in insurance, a gamma severity or poisson frequency problem where init_score would be the log(exposure)? Could this be made to get_init_score from the dataset and incorporate that somehow during the process of setting starting values? Or would you be forced to use weights of exposure and change the response variable to y/exposure?

I think the desired offset would take the place of the np.ones it uses now but you'd have to know how it relates to the distribution parameters through the distributions mean function, right? So for Gamma, you could multiply the offset by the concentration starting value but you have to invert it for the rate. For Gaussian, you'd multiply it by the starting mean but not the sigma, etc. That would require having the ability to determine the correct operation to perform for each parameter for each distribution. Does that make sense?

Thanks for your interest in the project.
So the initial scores serve as to initialize the boosting model, i.e., the model uses the initial scores as starting values where to boost from for the first itertation. Since we model all parameters of a distribution, LightGBMLSS currently calculates the unconditional parameter values from the data using the LBFGS model, based on the NLL. Hence, there is no need to multiply them with a value since they already reflect a reasonable starting value.
So for a Poisson distributed variable, the rate parameter is initialized with the unconditional parameter values and for the remaining iterations, the rate parameters changes as a function of x.
Does that answer your question?

In a traditional context, one can either use weights + transformed response or no weights and an offset. In a non-LSS approach where predictions are in terms of the response value rather than distribution parameters, init_score serves as the place bring in an offset. So, for example, I can predict loss severity by using losses as response and log(exposure) as init_score. My prediction will then be severity / exposure. Alternatively, I can use losses/exposure as my response and exposure as weights. That should produce similar models (though not precisely similar in terms of the path training might take).
As I understand you answer, LSS needs to use init_score for distribution parameters, not means, and so I'd have to resort to the losses/exposure + exposure weights approach. The thought in my initial response was basically thinking that if I was really committed to using my domain offset, I'd just need to relate it to parameter init_scores in the proper way. For example, in Gamma the mean is alpha/beta. So if the init_scores were alpha*log(exposure) and beta/log(exposure), then I'd get the parameter predictions for Gammas that were already in terms of a loss/exposure distribution rather than a raw loss distribution without having to transform my response.
Transforming the response and using weights isn't a big deal, but there are cases were you really would like to use an offset in a regression, like if I want to build a model off the prior model's predictions (even if they are distributional parameters) or if I want to start from (to use insurance again) my current rating plan's relativities.
So the thought behind the ticket is really how one might be able to take any init_score you might have for your problem space that you planned to use in a traditional LGBM context (just like you have a response variable that itself doesn't start out as a set of distribution parameters) and have it work in the same manner, transparently, with the LSS version of the model.

@neverfox Thanks for the detailed explanation.
I need to see how to incorporate an offset without transforming the response.

@neverfox I looked into it, however, I don't see how I can possibly change the start values to a transformation of the response. So for now, the onl way to do it would be to transform the response accordingly.

Can I close this?

You can. I am still thinking the issue through but it might take me some time.

Feel free to re-open if necessary. Thanks.


A first version with static data

This is the basic reproduction of the original table with static data. This includes the project setup with vite.
Should be good enough to deploy.

Looks good to me 👍


upgrade to duo authproxy 2.4.12

https://circleci.com/gh/jumanjihouse/docker-duoauthproxy/45 is clean
:ship:


Too much box

I trained the model but it does not detect the numbers. There is too much box.
Please need help....

same ! you found the issue ?

Yes, the same.

Is this the result of following 2-training-from-scratch?

Yes. I also try other training and have the same issue.

I am just confusing, @Penny, didn't u get this kinda out put when u trial out the application ? because use the same weights same models nah

@penny4860  ?

@slimamk @TharakaMadhusanka
I apologize for the delay. Related bug was fixed in Bugfix train params. Please checkout the latest master and check it out.

Sure !

@AliceDinh I had the same issue when I tried to reproduce the results in Google Colab.
Was there any solution that was found? I found the same number of boxes as well 66 and 76.
@penny4860 do we have to train the model from scratch to resolve the issue?

Might I add, getting the weights by training from scratch produced a set of weights that resolved the issue from 66 boxes and 76 boxes to 0 boxes and 1 box with a threshold of 0.3.
Reducing the threshold to 0.05 brought the results to 1 box and 2 boxes 😂
I think something went wrong with training. let me check again.

@janithwanni Thank you for using this project. In the case of Yolo v2, learning is a rather difficult problem. Yolo v3 has relieved much of this problem, so we recommend using Yolo v3 at this point.


Skill Name Problem

I just tested the new 0.0.3 version, and I encountered 1 problem.
Some skills were not named correctly (It was for Yodarha in this case).
I'll add a screenshot. Hope this can help you ^^

Thanks for the report, I think there are a few missing skill names as you've pointed out that aren't in our list yet..
https://github.com/false-spring/gbfr-logs/blob/d16aeadc31edbabe8cc2bc813a2bfb1bafecd979/src/lang/en.json#L394-L420

This will be fixed in the next 0.0.6 version as part of https://github.com/false-spring/gbfr-logs/pull/19


ORC-192 Implement zlib compresion stream

Implement zlib compressor based on the output stream. Add corresponding
UTs. Also rename the existing test suite from TestCompression into
TestDecompression.
Change-Id: I6c594cc8f8a769078bbe561056adfd5d0389dbc1

@omalley can you please take a look at this? Thx.

@majetideepak @omalley please take another look.

+1 LGTM

Hi @majetideepak , what happens next after you approved? are you able to accept this pull request?

@xndai I should get rights to merge by next week. @omalley  will merge them until then.

I just merged this commit. Thanks @xndai for the contribution and @majetideepak  for the reviews!


Expense Flow: Incomplete side-effects

Update the side-effects of Incomplete expense updates:

[ ] When Expense or its items value or description change: automatically move it to Pending and email Collective admin.
[ ] When only Payout information is updated, move it to Approved for fiscal host admin to pay.

@iamronen we need to set a default action to when the user only comments on the expense. Considering that this probably requires Fiscal Host interaction, should we move it to Approved?

I don't think it's ok to approve an expense after only a comment by the submitter. It can be a question or request for further clarification (Exhibit A).
I am pushing here again to create the "assign" action because then it's clearer that when an expense submitter answers using the comments, it gets back on the tray of the fiscal host admin chores. @kewitz @iamronen

@Memo-Es the problem with assign is that it not only gets the ball back to the fiscal host but also starts to get into work balancing host admins. I would really like to keep the work balance out of our scope for now because this generates a whole new set of problems.
The suggestion for setting it back to approved is to convey the idea that the expense should be checked by any available host admin if it is for paying for the expense or just replying to any further questions from the payee.


Optionally dereference symlinks

Thanks @CalebQ42 for this extremely useful library.
When I wrote go-appimage, one area that I would have loved to have is the option to follow (dereference) symlinks when extracting from squashfs. Sometimes want to extract the symlinks as such, sometimes you want to extract the files/directories they point to.
I think the go-appimage code could be significantly cleaned up if this capability could become part of this library.

That's definitely something I could do. It probably wouldn't be too difficult to add something like file.ExtractSymlink with the option to extract just the symlink, or extract what the symlink is pointing to.

Related:
https://github.com/plougher/squashfs-tools/issues/77

Thanks for implementing this.
We should make use of it in these places:
https://github.com/probonopd/go-appimage/search?q=symlinks


Provide a setting to disable cursor position restoration when re-opening files

When we close a file and then re-open it, VS Code will restore the cursor position.
In many cases this is desired. However, in some cases it is not, therefore it would be useful to provide a setting for this and allow it to be configured differently depending on the language being used.
For example: when I run git commit in terminal, the COMMIT_EDITMSG file will open in VS Code. Ideally my cursor would be positioned at the top so I can start writing my commit message right away. However, many times my cursor is positioned elsewhere, presumably because VS Code is trying to restore it to the position when I closed this file the last time I wrote a commit message.
This also happens when I run git rebase --interactive and the rebase todo list is opened in VS Code.

@bpasero Not sure if this feature is from you.

We have "workbench.editor.restoreViewState": true but you cannot set it as resource setting currently.

We have "workbench.editor.restoreViewState": true but you cannot set it as resource setting currently.

Ah I didn't find that when I was searching for keywords "cursor, position, reset, restore". Maybe we could add those as keywords so the setting is more easily found.

Verification:

configure workbench.editor.restoreViewState for a language, e.g. markdown
open a couple of files including markdown and scroll + set a selection you can memorize
switch between tabs and verify view state is restored
reload window and do the same and verify view state is restored
close a non-markdown file and open it again and verify view state is restored
close the markdown file and open it again and verify view state is NOT restored

I have verified this works as expected, with the following correction to the last two bullet points

close a non-markdown file and open it again and verify view state is NOT restored
close the markdown file and open it again and verify view state IS restored

Since I have configured for markdown to restore view state this is expected behavior imho.

I think what I meant to say is to configure workbench.editor.restoreViewState: false for [markdown] because the default is to restore view state always.

Ok, let me verify it again...

Works fine! Thanks for clarifying.


Include HttpService trait

This is not intended to be implemented by the end user. Instead, it is a trait alias of sorts, allowing users to directly reference and add bounds to the request and response body types.

@olix0r
It's currently used as part of tower-grpc. However, it is generally useful to anything doing HTTP + Tower. It's mostly used so that one can reference the body type directly without doing a whole bunch of generic acrobatics each time.


Mock functions can insert into function names that contain mocked function word

The injectMockFunctions can insert a mocked function into a function name that contains the mocked function name within the function name.  For instance mock_movel will cause hb_movel to become hbmock_movel.  This prevents us from mocking functions that have names that could be contained within another function definition.

This will be resolved in #29


Document how to mount a volume (cookbook using pod_patch?)

Beyond general docs for pod_spec and pod_patch (tracked in #3567), we should have somewhere in the docs (maybe a Cookbook?) specifically telling people that is the feature that should be used to add volumes, since, if i'm looking for how to add a volume, it is far from obvious that pod_patch is what I should be looking for to do so

https://pachyderm-users.slack.com/archives/C3UN0S0Q0/p1585662848052100

pod_patch would indeed be the way to do this. It’s a JSON patch of the fields you want to change in the pipeline pod spec. So the steps would be:
Create the persistent volume on the cluster
Figure out what the volume mount would look like on the pod as a k8s manifest
Turn that manifest into a JSON patch
Add that JSON patch to the pipeline spec
I’m not aware of any examples of this offhand, but let me check in with the docs/customer team to see if there is something available.
To fill in the blanks on step 3:
3.a. Get the rc for the pipeline into a file.  The command will be something like
kubectl get rc pipeline-- -o json > -rc.json
3.b. Edit the volumes section to add the volume mount you want.  Save it into a file with another name, so you can do a diff later on.
3.c  Deploy the rc and make sure the pipeline pod restarts.  You may need to kill the pod so it gets restarted from the rc.
3.d Test the pipeline, to see if it works right
3.e  Repeat 3.b-3.d until it works
3.f  Use a json patch generator to generate the patch between your original rc manifest and the one you edited.
4. Same as above
5.  Redeploy the pipeline using the new spec.
6. Test to make sure it works.