minor: 循环拉取蓝盾流水线

 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.wheelwang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


images were not showing in single post view

Hi, I was using your template, it is very cool. But I couldn't see images in individual posts, so I have make a small change to fix this. Now if you have an image in the post, it will be shown, and if you dont set an specific image, it will show a blank image (without having to request another static file) with 0px height.

Example with image
https://samuelmartingc.github.io/blog/post/hello-world/
Example without image
https://samuelmartingc.github.io/blog/post/javascript-logical-operators-and-or/

Thank you for your pull requests.
This is my mistakes, i'm sorry.
I confirmed pull request now:)


Cross-platform build script

Replace psake with https://github.com/sakeproject/sake

If I update this project to netstandard, then I'll take of this.


getPullRequestChangedFiles does not get all changed files

I am reviewing a pull request with 550 changed files but not all of them are appearing in the list of changed files.
Inside async getPullRequestChangedFiles(pullRequest: IPullRequestModel): Promise<FileChange[]> It makes the first request and then requests an additional page only twice (while (response.headers.link && octokit.hasNextPage(response.headers)) {) resulting in only the first 300 changes.

Extension version: 0.1.5
VSCode Version: 1.28.0-insider
OS: Win10 Enterprise v1607

Steps to Reproduce:

Open a pull request with > 300 files changed.
Check if the files changes contains all of the files it should.

It seems there has been an update on this one. The linked github documentation mentions limit of 3000 changed files, not 300 which seems to be the limit now (I see this issue being triggered with 320 changed files).

Thanks for the update @cyrusmg!


Add Support for Resolving External JSON Schemas

We were exploring the visibility of creating a shared GS1 Schema definition instead of copying the same attributes into multiple files. For example, multiple GS1 Credentials have the same organization attributes.  Instead of copying these into each JSON Schema we wanted to create a shared GS1 Schema that could be loaded during Schema Validation.
The ajv.js library supports combining JSON Schema before validation using the $ref keyword https://ajv.js.org/guide/combining-schemas.html#combining-schemas-with-ref
One related question. Does the Transmute Library support a way to bypass JSON Schema validation. We have a use case were we like to directly run the JSON Schema validation using the ajv.js library and still use the Transmute library for the Revocation Check.

Our experience with trace-vocab has lead us to avoid using schemas with $ref.
its possible to support it, but it leads to security / performance issues, and complexity.
I would in general recommend against it, if you have the option to.

I'll leave this issue open, and see if I can add some tests demonstrating support for this.
The problem is that $ref is usually a relative reference, and the base will be an absolute URL, so even if its supported there could be compatibility issues between collections of schemas hosted via https and collections of schemas hosted in a file system.


Skew object for Lamination + FEMM

It would be interesting to add the possibility to skew the laminations. To achieve that it would require:

To add an instance of a Skew abstract object in the Lamination class. The Skew class define Nslice the number of skew slices.
Provide several daughters of Skew (for instance SkewLinear, SkewStep...) with the method comp_angle_skew that returns an array of length Nslice of the angular position of the lamination slices [rad].
The comp_angle_skew would also have an optional argument (alpha_ref) to normalize its output according to an angle [rad]. The idea is to be able to provide the skew as a multiple of the stator slot pitch for instance
The "angle_skew" of both laminations are computed in the comp_output_geo method of the Lamination object and stored in the corresponding OutGeoLam
In MagFEMM solve_FEMM method there is another loop on the skew slice. The skew is set in the update_FEMM_simulation to set the correct rotor relative position (angle_skew_rotor[ii] - angle_skew_stator[ii])
The resulting flux is stored in the OutMag object as Br_skew and Bt_skew with dimensions [Nt_tot, Na_tot, Nslices]. Br and Bt are then computed as the average of Br_skew and Bt_skew on the slices.
OutMag will define a get_flux_skew_rotor(Nslice) and get_flux_skew_stator(Nslice) that returns the flux at on a Z linspace. If Br_skew and Bt_skew are not available, the method returns just an extended [Nt_tot, Na_tot, Nslices] matrix of Br or Bt.
A validation case on each Skew daughter and one comparing Br and Bt of a no skew simulation with a simulation with a 0 linear skew would be interesting.

Hi everyone,
I dig up this issue to talk again about rotor skew implementation in machine and Magnetics objects. The implementation has changed consequently regarding the original issues. The implementation is now divided in three parts:
1st part: implement skew class as an attribute of lamination class:

The skew class takes as argument the skew type and the number of layers. The skew types can be linear continuous (e.g. for skewed squirrel cage) or stepwise (e.g. for PM rotor, with default stepwise patterns such as linear, V-Shape and zig-zag)
The skew class contains methods to calculate rotor skew angle function of axial dimension (z axis for radial flux machine) and plot it
For continuous linear skew, rotor skew angle can be given at the both axial extremities of the machine so the input number of layers is irrelevant as it is two.
For stepwise skew, rotor skew angle is given at the axial extremities of each magnet layer to describe the skew angle stepwise function.

2nd part: implement slice class in Magnetics class:

The new class SliceModel enables to calculate the slices that are relevant for magnetic calculation (2.5D assumption) by looking at the rotor skew type.  A new axis "z" is then added to the existing axes "time" and "angle". "z" is SciDataTool axis of type DataPattern which enables to only store unique slices and rebuild the matrix with all the slices if requested. For non-skewed rotor the "z" axis will only have one slice but I think it is better not to squeeze it to identically deal with skewed and non-skewed machines.
The method run() of Magnetics enables to loop on comp_airgap_flux() on each slice and update the rotor initial angle depending on rotor skew angle at the specific slice.
The method store() is quite the same for the airgap flux density, which is now always 3D even for non-skewed rotor. The main difference is how torque and winding flux are calculated. It can be done by using SciDataTool command to integrate torque/flux per slice that are embedded in DataPattern object.

3rd part: implement skew type setup in machine GUI:

A rotor skew setup widget is added at the end of rotor definition
The widget enables to choose among the different skew types and patterns, and even define an arbitrary pattern.
For SCIM the only available rotor skew should be continuous linear skew, the number of layers is implicitely 2. For rotor PM it is possible to define the number of layers and choose among the most common patterns: "linear","v-shape" and "zig-zag".

Please let me know if you have any questions/remarks,
Best regards
Emile

Hello everyone,
We had to clarify how torque/phi_wind are calculated in case of skew because the current method is not generic to all skew patterns. Right now the actual torque/phi_wind is obtained in MagFEMM by setting the machine length in the FEMM model. With multislice approach, the length would rather be:

in case of stepped skew (e.g. for PMSM with magnet segments): the length of each slice since the magnetic quantities are assumed to be constant all along each segment (scheme 1)
in case of continuous skew (e.g. for skewed squirrel cage): an infinitely small length, because the magnetic quantities are given at the exact slice position, and the values at other positions are obtained by interpolating between the slice before and the slice after. (scheme 2)

Both solutions require to treat separately stepped skew and continuous skew in the method run() of Magnetics, which is not really satisfying in terms of genericity.
There is a third solution which is described as below and that we think is the best to implement in pyleecan:

Remove length from FEMM to get Tem / Phi_wind per meter for each slice so it is generic to both continuous and step skew types
Store Tem_slice/Phi_wind_slice as DataTime objects with "time" and "z" axes (+ "phase" axis for Phi_wind_slice) in OutMag (while keeping already existing fields Tem and Phi_wind in OutMag for compatibility)
Add getter to calculate Tem from Tem_slice (resp. Phi_wind from Phi_wind_slice) using integration method of SciDataTool for DataPattern axes
User can either call out.mag.get_Tem() to get overall instantaneous torque or look at out.mag.Tem_slice to see slice contribution

Please let me know if you have any questions / remarks,
Best regards,
Emile


Create safe LLVM bindings

 Issue by brson
Saturday Aug 03, 2013 at 23:15 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/8274
This issue was labelled with: A-libs, A-llvm, E-tedious in the Rust repository

rustc's LLVM bindings are a bit of a hodgepodge. Some abstractions have been added on top of the C bindings, but not consistently. It would be nice to do some serious cleanup here so that rustc is using only safe, high-level bindings.

I've started work on safe LLVM bindings recently [1]. The work is in the very beginning (only small part of API is covered). My bindigs use llvm-sys [2] as unsafe bindings (not ones from rustc). Comments and pull requests are welcome. When something lacks in LLVM C API, I add wrappers for it and I have plans to push these wrappers upstream.
[1] https://github.com/jauhien/iron-llvm
[2] https://bitbucket.org/tari/llvm-sys.rs

There are also some other projects that are doing this:

https://github.com/gsingh93/llvm
https://github.com/TomBebbington/llvm-rs

Any news on this topic?

I am working on some rust ideomatic LLVM bindings right now

I am working on Inkwell which is a safe wrapper over llvm-sys. It's still early on, but I've got some neat ideas for providing a more pleasant interface.

Any progress here? 😅

Closing in favor of the tracking issue https://github.com/rust-lang/rust/issues/54892.


Release 0.20.2

Just pom.xml fixes so where we're using this for internal projects we aren't forced to try and release to Maven Central using the Nexus Staging plugin

Looks alright but it failing - flaky tests?

Not usually, looks like something was holding a bunch of ports on the runner preventing the tests from running correctly.  Hopefully a transient error as the new build seems to have passed OK


Add gemfile of rails 5.1 for running on travis

Rails 5.1 has been released 🎉
http://weblog.rubyonrails.org/2017/4/27/Rails-5-1-final/

👍

@indirect Are you a merge commit fan or squash & merger?

ah.. can i merge?


Remove obsolete code and TODO comments in serial.tsx and serialindicator.tsx

Also custom.css

Plus general code cleanup.

https://github.com/Microsoft/pxt/pull/3136


Visual artifact when using InteractiveViewer with ListView

Zoom in around where the listview's children connect from one to the next. Takes a few tries. You'll see this horizontal line.
That lines appears and disappears as you zoom in and out and then scroll up or down when it shouldn't be appearing at all. I noticed that it stops appearing past a certain threshold, so it only appears when zoom is a little over 1x.

Screenshots: 2 PNG + 1 GIF

Code
import 'dart:ui';

import 'package:flutter/material.dart';

void main() {
  runApp(MaterialApp(
    theme: ThemeData.dark(),
    home: InteractiveViewer(
      child: ListView(
        children: [
          'http://vertical-comics.com/images/seki_01/My_Neighbor_Seki-01-1.jpg',
          'http://vertical-comics.com/images/seki_01/My_Neighbor_Seki-01-2.jpg',
          'http://vertical-comics.com/images/seki_01/My_Neighbor_Seki-01-3.jpg', // up to 12
        ].map((e) => Image.network(e)).toList(),
      ),
    ),
  ));
}

Doctor
[✓] Flutter (Channel stable, 2.10.4, on Microsoft Windows [Version 10.0.22000.593], locale en-US)
    • Flutter version 2.10.4 at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (8 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\Agone\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.1.1)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.1.32228.430
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2021.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • 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 11.0.11+9-b60-7590822)

[✓] VS Code (version 1.65.0)
    • VS Code at C:\Users\Agone\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.37.20220301

[✓] VS Code (version 1.67.0-insider)
    • VS Code at C:\Users\Agone\AppData\Local\Programs\Microsoft VS Code Insiders
    • Flutter extension version 3.37.20220301

[✓] Connected device (5 available)
    • Redmi Note 9 Pro (mobile) • 77992d4a • android-arm64  • Android 11 (API 30)
    • Redmi Note 5 (mobile)     • e85b6adc • android-arm64  • Android 11 (API 30)
    • Windows (desktop)         • windows  • windows-x64    • Microsoft Windows [Version 10.0.22000.593]
    • Chrome (web)              • chrome   • web-javascript • Google Chrome 99.0.4844.84
    • Edge (web)                • edge     • web-javascript • Microsoft Edge 99.0.1150.55

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @noga-dev, Thanks for filing the issue  I am able to reproduce the issue on stable and the master channel.  The issue is more easily reproducible on mobile platforms.
https://user-images.githubusercontent.com/31410839/161526508-5cb8b353-4c81-41b2-bbb5-903ef8ded709.mov

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 2.10.4, on macOS 12.3 21E230 darwin-arm, locale en-GB)
    • Flutter version 2.10.4 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (3 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

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

[✓] Android Studio (version 4.2)
    • 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 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.65.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.37.20220301

[✓] Connected device (4 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:55555                    • android-arm64  • Android 11 (API 30)
    • iPhone 12 Pro (mobile) • 535317A4-921C-488F-B234-C2CC6D4AE5A1 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 99.0.4844.83

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 2.13.0-0.0.pre.277, on macOS 12.3 21E230 darwin-arm, locale en-GB)
    • Flutter version 2.13.0-0.0.pre.277 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 13d2381109 (6 hours ago), 2022-03-27 21:00:08 -0400
    • Engine revision 559e259c54
    • Dart version 2.17.0 (build 2.17.0-246.0.dev)
    • DevTools version 2.11.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! CocoaPods 1.10.2 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin
        usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

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

[✓] Android Studio (version 4.2)
    • 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 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.65.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.37.20220301

[✓] Connected device (4 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:55555                    • android-arm64  • Android 11 (API 30)
    • iPhone 12 Pro (mobile) • 535317A4-921C-488F-B234-C2CC6D4AE5A1 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 99.0.4844.83

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

This looks like an anti-aliasing issue that probably goes away if you add a white background behind the ListView.
For details see also: #14288

This looks like an anti-aliasing issue that probably goes away if you add a white background behind the ListView.
For details see also: #14288

Unfortunately adding a white bg is like adding white duct tape on a white canvas in this case since otherwise not every image will be white in other cases.

@maheshmnj I just confirmed that @goderbauer's solution is a band aid. Should this issue stay closed nonetheless assuming the underlying cause is in the linked issue above or perhaps it should be reopened?

The real issue is https://github.com/flutter/flutter/issues/14288.


Add Open Policy Agent to landscape

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, pick the single best GitHub repository for your project, not a GitHub organization.
[x] Does it follow the guidelines for new entries?
[x] Have you added an SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow logo guidelines?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~5 minutes after opening the pull request, the CNCF-Bot will post a link for you to preview your changes. Have you confirmed that they are correct and then added a comment to the PR saying "LGTM"?

/cc @anderseknert

Nice!


docs: fix incorrect useStore option (recursive)

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
The recursive option (useStore) is incorrectly documented as deep.
(Not sure I am supposed to add my name to the contributors list if only modifying docs. Sorry if not, the hype is strong)
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

thanks @fum4 !


Small artifact crafting disabled

Regular seablock modpack installed
Can craft the different pastes, but recipes for small and large artifacts are disabled
Seablock for KiwiHawk.zip

disabling and reenabling bob's enemies AND angel's bioprocessing fixes the issue, at the cost of removing all of the associated items and recipe progress from the game.

Fixed by #285


Added functionality to contact us page

#12

@tushargupta1504 please add gssoc ext and level label

@tushargupta1504 please add hactoberfest label

this is appearing two times please remove it

ok letme check

ig i changed only this part of code please let me know what part to be deleted


Docker for QSFS

alpine's mktemp complains when the template doesn't end with ...XXX
tested with https://github.com/threefoldtech/0-stor_v2/pull/80 and zdb rebuilt with this workaround
zdb-namespace file is uploaded to remote zdbs by listening on namespace-created hook action

I see you using always using backticks for shell execution in your script.
You should move to $(...) :)
http://mywiki.wooledge.org/BashFAQ/082

I see you using always using backticks for shell execution in your script. You should move to $(...) :) http://mywiki.wooledge.org/BashFAQ/082

Thanks! didn't know that, laziness was my only motive.
Converting to a draft pull requests until relevant projects are released (to update the versions).


sendMessageToActiveTab causes bugs when we switch tabs fast - info from one tab Sidebar.tsx can be sent to another tab's index.js.

Fixed in 5266494


having both  and "title:" metadata should error out

Since it's redundant to specify both <title> and a metadata title:, when both are present, ecmarkup should ideally error out and instruct me to remove one.
Alternatively, it should stop supporting both, and force one method of specifying the title.

I think I like the current behavior. You can specify a title in the metadata block and it will generate the header boilerplate, but if you wanted to you could override the document title.

Fair - perhaps a warning if they're the same? No worries if you don't think that's valuable.


TimeInput refreshes date to current date

I already have a date and time selected. When I open the picker and start typing into the time input, the date will refresh and display the current date. I have a screen recording below to demonstrate.
<DatePicker
  selected={
    new Date(sportInputFields.broadcast_start_time)
  }
  onChange={(date) => {
    setSportInputFields({
      ...sportInputFields,
      broadcast_start_time: date.toISOString(),
    });
  }}
  showTimeInput={true}
  dateFormat="dd/MM/yyyy - HH:mm"
/>

https://github.com/Hacker0x01/react-datepicker/assets/84858035/9571ce7e-8723-4db8-8f81-4fc55d28353b

Hi @Siminn-teiturg , I couldn't recreate the issue you mentioned.  Can you please try it in the official website playground - https://reactdatepicker.com/#example-input-time
If you still have the issue, please share the code


Watch and rebuild linked packages in yarn workspaces monorepo

Hey guys
Firstly I'd like to say fusebox is epic! It is a breath of fresh air coming from webpack and babel. Well done to all contributors for all of your hard work in making this such a great build tool with a well thought out api.
I just have a quick question in regards to using fusebox with yarn workspaces. Consider the following file structure:
-- applications
    -- main
        -- src
            -- index.ts
        -- fuse.js
        -- tsconfig.json
        -- package.json

-- packages
    -- components
        -- src
            -- accordion.vue
            -- dropdown.vue
            ...
            -- index.ts
        -- package.json
    -- styles
        -- src
            -- site.scss

Currently with my webpack setup if I modify a file in any of the linked packages (say ./packages/components/src/dropdown.vue) that are referenced by the app, webpack will automatically trigger a rebuild and hmr the app. It's also worth noting that our webpack.config.js file is located at ./applications/main/webpack.config.js not at the project root. The problem I am facing is that fusebox doesn't rebuild in the same scenario so I have to stop the process and rebuild the app each time a change is made in any of the packages.
I am aware of issue #1277 which suggests moving fuse.js to the root or manually aliasing the package paths however I would prefer to use this as a last resort. I have also tried setting the modulesFolder property in the fuse config to the path of the packages ../../packages (relative to ./applications/main/src as the homeDir) however this had no effect.
My fusebox config is as follows:
const {
    FuseBox,
    CSSPlugin,
    SassPlugin,
    VueComponentPlugin,
    WebIndexPlugin
} = require('fuse-box');

const fuse = FuseBox.init({
    homeDir: 'src',
    target: 'browser@es2015',
    output: 'dist/$name.js',
    useTypescriptCompiler: true,
    allowSyntheticDefaultImports: true,
    plugins: [
        CSSPlugin(),
        [
            SassPlugin(),
            CSSPlugin()
        ],
        VueComponentPlugin({
            style: [
                SassPlugin(),
                CSSPlugin()
            ]
        }),
        WebIndexPlugin()
    ],
});

fuse.dev();

fuse
    .bundle('app')
    .instructions(' > index.ts')
    .hmr()
    .watch();

fuse.run();

Is there any way to configure fusebox to behave similar to webpack in the given scenario and rebuild/hmr upon changing a file in a linked package?

@andrewcourtice Hi and thanks for such kind words!
modulesFolder is one of the oldest features and it requires some love. Due to the amount of requests for this workspace setup (You aren't even the first nor the second to ask for this feature), I will try to implement and squeeze it into 3.7 release.
There is one thing that might be helpful in fuse-box@next. You can keep fuse.js in your homeDirectory and reference homeDir higher up in the hierarchy.  I'm looking forward to the 3.7 release. In the meantime I'll give fuse-box@next a go. Thanks again for your help 👍

Closing this for now. I believe the @next version solves the problem


python310Packages.jupyterlab_server: 2.15.0 -> 2.15.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: "JupyterLab Server"
meta.homepage for python310Packages.jupyterlab_server is: "https://jupyter.org"
meta.changelog for python310Packages.jupyterlab_server is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.15.1 with grep in /nix/store/z92xi8l5v05zw9f6nkv4rhx7hjs5vx0c-python3.10-jupyterlab_server-2.15.1
found 2.15.1 in filename of file in /nix/store/z92xi8l5v05zw9f6nkv4rhx7hjs5vx0c-python3.10-jupyterlab_server-2.15.1

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

11 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python39Packages.jupyterlab
python39Packages.jupyterlab-git
python39Packages.jupyterlab-lsp
python39Packages.jupyterlab_server
python39Packages.jupytext

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z92xi8l5v05zw9f6nkv4rhx7hjs5vx0c-python3.10-jupyterlab_server-2.15.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.jupyterlab_server https://github.com/r-ryantm/nixpkgs/archive/aaa733d00a6554ec76c757b496abd44fd54a7091.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z92xi8l5v05zw9f6nkv4rhx7hjs5vx0c-python3.10-jupyterlab_server-2.15.1
ls -la /nix/store/z92xi8l5v05zw9f6nkv4rhx7hjs5vx0c-python3.10-jupyterlab_server-2.15.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages failed to build:

python39Packages.jupyterlab
python39Packages.jupyterlab-git
python39Packages.jupyterlab-lsp
python39Packages.jupyterlab_server
python39Packages.jupytext

6 packages built:

manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext

Maintainer pings
cc @costrouc for testing.

Fixed the Python 3.9 build with: https://github.com/NixOS/nixpkgs/pull/188608

Addressed by #188608


typo: respository -> repository

Docs Build status updates of commit 3dc351a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/microservices/ci-cd.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support subqueries in the SELECT clause

The following demonstrates a subquery in the SELECT clause:
SELECT t1.*, (SELECT COUNT(*) FROM t2) AS num_t2
FROM t1;

where (SELECT COUNT(*) FROM t2) is the subquery.

This is already supported:
$ ./sqltoaster/sqltoaster "SELECT a, (SELECT b FROM t2 WHERE t1.id = t2.t1_id) FROM t1"
OK
statements[0]:
  <statement: SELECT
   selected columns:
     0: column-reference[a]
     1: scalar-subquery[
<statement: SELECT
   selected columns:
     0: column-reference[b]
   referenced tables:
     0: t2
   where:
     column-reference[t1.id] = column-reference[t2.t1_id]>]
   referenced tables:
     0: t1>
(took 34524 nanoseconds)


Reconsider and clarify Flashing Beacon

Background
The WZDx specification defines a FlashingBeacon object that is defined as:

a flashing beacon light of any form (e.g. trailer-mounted, vehicle), used to indicate something and capture driver attention.

There has been confusion about what specific devices are considered to be a flashing beacon, especially when looking at the MUTCD which defines categories of flashing beacons. Some types of flashing beacons in MUTCD are not applicable here, such as intersection control beacons or stop beacons.
Some producers have considered anything with flashing lights (such as a work truck) to be represented with a flashing beacon; other ideas are that the flashing beacon should be for conditional impacts, such as a "Vehicles Entering" sign where the condition is only active when the lights are flashing.
Solution
The specification documentation should clarify when the flashing beacon should be used.
Possible producer use cases of devices with flashing lights should be discussed and determined which are "flashing beacons" and how to represent those that are not (e.g. with a Location Marker).
It's possible that the Flashing Beacon object should be renamed to be more specific and possibly reference a concept defined in MUTCD (such as flashing warning beacon).

There is some confusion between how we have defined a “Flashing Beacon” in the Device Feed and how the practitioners in the field are actually utilizing the device.  We want to ensure that we are following the MUTCD definition of a “Flashing Warning Beacon” that is used in a temporary work zone environment versus a permanent condition.  To address this in the most simplistic way, I propose a modification to the text that is used to describe the Flashing Beacon Object as follows:
Current: The FlashingBeacon object describes a flashing beacon light of any form (e.g. trailer-mounted, vehicle), used to indicate something and capture driver attention.
Proposed: The FlashingBeacon object describes a flashing warning beacon used to supplement a temporary traffic control device, mounted on a sign or channelizing device that are used to indicate a warning condition and capture driver attention.

Thank you @NeilBoudreau, I will make a PR updating the description of FlashingBeacon.

Resolved in #354.


Adds element annotations to SerialDescriptor derivation

Adds ability to add com.xebia.functional.xef.auto.Description annotations to scala classes with derived serializers. Avoids using shapeless-3-deriving because mixed Java and Scala annotations on a class that is subsequently passed to AllAnnotations results in an InstantianitonException at compile-time.

Adds com.xebia.functional.xef.auto.WrappedAnnotation to wrap scala annotations retreived at compile time and add to the serial descriptor element annotations list
Adds com.xebia.functional.xef.auto.getAnnotations[A: ClassTag] to fetch both scala and java annotations and store them in a Map[String, List[java.lang.annotation.Annotation]] map for retrieval during serial descriptor derivation.
Adds com.xebia.functional.xef.auto.getAnnotationsMacro and com.xebia.functional.xef.auto.getAnnotationsImpl to retrieve scala annotations for field members at compile time

Feature suggested by @raulraja in https://fortyseven.slack.com/archives/C051PG86AH0/p1688485085031159?thread_ts=1688413411.157379&cid=C051PG86AH0

@diesalbla accepted your changes. Please re-review when the tests are done.


feat: #1684 set collection method as parametrized

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #1684 🦕

We cannot take this change as it breaks some invariants as explained in https://github.com/googleapis/nodejs-firestore/issues/1684


Splash page in mobile lansdcape has a disappearing FIP

Description of issue

When you put the alpha site splash page in mobile landscape mode on safari the position of the content box is calculated using the height of the screen and so the FIP disappears off the page:

Screenshot

Canada.ca Splash page

VC fixed this by making the background fixed and the box margin auto. We used similar tailwind configuration so the vue template should match up nicely.
Example code https://github.com/Toad-Labs/vc-frontend-static/blob/main/src/views/Splash.vue

The Francais button is also missing the lang="fr" attribute for WCAG 3.1.2 compliance


payment functionality using razorpay

#102 issue resolved

First of all resolve the merge conflicts and secondly add that nodemodules inside the gitignore file so that they should't be committed

sure. can you guide me how to resolve the merge conflict? Should I close the PR and do it again?


DRAFT: feat(ks-backend): testing review environment & EMAIL_HOST env variable

Description :sparkles:
feat(ks-backend): testing review environment & EMAIL_HOST env variable
DO NOT MERGE! THIS COMMIT IS FOR REVIEW ENVIRONMENT TESTING ONLY!
refs YJDH-682
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

API branch is deployed to platta: https://kesaseteli-pr2401.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2401.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2401.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2401.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2401.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-employer-pr2401.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-youth-pr2401.dev.hel.ninja :laughing::tada::tada::tada:

Not needed anymore, testing was successful.


Inconsistent output for floor_divide / remainder / divmod

When working on some code that needs to find the nearest sample index and the distance from it, I came across some inconsistencies in the available floor division and remainder functions. The following function returns the floor division and remainder calculated in three ways: with standard // and % operators, with the floor_divide and remainder functions and with the divmod function:
@numba.njit()
def fdiv(a, b):
    return (
        (a // b, a % b),
        (np.floor_divide(a, b), np.remainder(a, b)),
        np.divmod(a, b),
    )

When called with a=0.5 and b=0.05, in an ideal world all the tuples would be (10, 0). With floating point, calling the original Python function (i.e., the NumPy implementations), we get 9 and something very close to 0.05:
>>> fdiv.py_func(np.float_(0.5), np.float_(0.05))
((9.0, 0.049999999999999975),
 (9.0, 0.049999999999999975),
 (9.0, 0.049999999999999975))

However, the compiled version differs -- the operator result is the same, but the function results give 10 and something very close to 0.05:
>>> fdiv(np.float_(0.5), np.float_(0.05))
((9.0, 0.049999999999999975),
 (10.0, 0.049999999999999975),
 (10.0, 0.049999999999999975))

This division result is off by one for the corresponding remainder. To put it another way, the reconstitution a == b * (a // b) + (a % b) within roundoff (as promised in the floor_divide docstring) does not happen:
@numba.njit()
def fdiv_reconstitute(a, b):
    dm = np.divmod(a, b)
    return (
        (b * (a // b)) + (a % b),
        (b * np.floor_divide(a, b)) + np.remainder(a, b),
        (b * dm[0]) + dm[1],
    )

>>> fdiv_reconstitute(0.5, 0.05)
(0.5, 0.5499999999999999, 0.5499999999999999)

I get this behaviour on both the latest Git versions of numba (28573bb985) and llvmite (numba/llvmlite@b40a72a), and with the latest releases (numba 0.56.4, llvmlite 0.39.1) installed as wheels from PyPI. This is using Python 3.10 on ArchLinux, Intel i9-9900K CPU, LLVM 11.

Hi @bcbnz , Thank you for reporting the bug. I can reproduce it. Looks like this deviation happens due to the different implementations of divmod within Numba codebase:
Both the a // b and a % b operations go through lower_builtin API and is being executed by a more mathematically accurate/ CPython inspired implementation of divmod:
https://github.com/numba/numba/blob/28573bb985cf4816e1c6f54ce2f4bd1e44617bcd/numba/cpython/numbers.py#L626-L731
Whereas, the NumPy functions in JIT code np.floor_divide/np.remainder/np.divmod uses the ufunc_db API and ends up using a combination of LLVM  fdiv and llvm.floor instructions respectively:
https://github.com/numba/numba/blob/28573bb985cf4816e1c6f54ce2f4bd1e44617bcd/numba/np/npyfuncs.py#L462-L465
Which I suspect leads to the numerical inconsistency that you've pointed out.

xref #8700


the pip sometime shrink by itself in chrome 71.0.3578.98 (Official Build) (64-bit) when watching Twitch

Thanks @Syas18 for the feedback.
Which platform do you use? Linux, Mac, Windows?
Does "shrink" is the same as "closed"?

I've fixed PiP window resize algorithm at https://chromiumdash.appspot.com/commit/1874661393200861f053d8af2e861d1866542813. Can you give it a try in Chrome Dev and let me know if that works better for you?

Hi, sorry for late reply. I tried to use  the current pip, and found out that the "shrink" is no longer occur when i set the video quality to auto or change the video quality. I think the problem solve by itself. Maybe the problem is in my pc, not the extension 😅.. So do I still need to do thing you ask me to in your last post(try in chrome dev etc)? sorry for the bad english


chore: add additional filetype to doc source mappings

Adds additional doc source to vim filetype mappings.

@benelan can you please also add ["yaml.ansible"] = "ansible",? Your PR is quite fresh and I'm to lazy to create the same PR just for one line. 😅

Thanks for the PR :)


default tekton pipeline for appsody stack should include test task

@csantanapr commented on Fri Oct 11 2019
Is your feature request related to a problem? Please describe.
Problem is that I think the default pipeline which includes 2 tasks build and deploy should have a 3rd task that runs the same process as appsody test
Describe the solution you'd like

The task test-task should be first in the pipeline.
This task should use the container appsody stack (ie Dockerfile-stack), this is specified in the .appsody-config.yaml from the git source
For example nodejs:cat .appsody-config.yaml
stack: kabanero/nodejs-express:0.2

The working directory should be /project
The command should similar to $APPSODY_INSTALL and $APPSODY_TEST

Describe alternatives you've considered
I have something working for nodejs-express but I hit a few problems.
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: csantana-nodejs-express-build-task
spec:
  inputs:
    resources:
      - name: git-source
        type: git
  steps:
    - name: npm-test
      image: kabanero/nodejs-express:0.2
      workingDir: /project
      command:
        - /bin/bash
      args:
        - -c
        - |
          set -e
          cp -a ${inputs.resources.git-source.path}/* $APPSODY_WATCH_DIR
          # perform npm install
          $APPSODY_INSTALL
          # run npm test on project and user-app
          delimiter=" && "
          s=$APPSODY_TEST$delimiter
          array=();
          while [[ $s ]]; do
              array+=( "${s%%"$delimiter"*}" );
              s=${s#*"$delimiter"};
          done;
          for i in "${array[@]}"
          do
            echo executing $i
            $i
          done

Some of the problems I hit:
. hardcoding the image name kabanero/nodejs-express:0.2 this should be from the config file .appsody-config.yaml
. something weird about running $APPSODY_TEST with the value is npm test && npm test -- prefix user-app mocha tries to parse && as argument, so the workaround I did was to parse the variable and execute it
[nodejs-express-test-build-task : npm-test] ><EMAIL_ADDRESS>test /project/user-app
[nodejs-express-test-build-task : npm-test] > mocha "&&" "npm" "test"
[nodejs-express-test-build-task : npm-test]
[nodejs-express-test-build-task : npm-test] Warning: Cannot find any files matching pattern "&&"
[nodejs-express-test-build-task : npm-test] Warning: Cannot find any files matching pattern "npm"

. I really wanted to avoid to run appsody extract, this takes too much time when using a volume, so I tried to do a softlink to avoid the cp -a, with ln -s /workspace/git-source /project/user-app the files get map correctly, the problem is with node.js when it tries to resolve node dependencies the cd .. get's resolve into /workspace instead of /project
I guess we can add the appsody extract at this stage, and remove it from the build-task
I'm going to look into spring-boot and microprofile appsody stacks to implement the unit test tasks.
Additional context
Tekton should have a way to dynamically specify the image name for step in a task some how, this way we don't need to hardcode kabanero/nodejs-express:0.2
cc @seabaylea

@csantanapr commented on Fri Oct 11 2019
In case is useful to anyone doing tekton task development and debugging, I'm using the tekton tkn CLI to simulate the same pipelinerun that get's trigger thru git webhook
tkn pipeline start nodejs-express-test-build-deploy-pipeline \
        -r git-source=csantana-nodejs-git \
        -r docker-image=csantana-nodejs-image \
        -p image-tag=master \
        -p image-name=docker-registry.default.svc:5000/kabanero-samples/appsody-sample-nodejs-express \
        -p release-name=appsody-sample-nodejs-express \
        -p repository-name=appsody-sample-nodejs-express \
        -p target-namespace=kabanero \
        -p docker-registry=docker-registry.default.svc:5000/kabanero-samples \
        -s kabanero-operator \
        -n kabanero

resources:
---
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
  name: csantana-nodejs-git
spec:
  type: git
  params:
    - name: url
      value: https://github.com/csantanapr/appsody-sample-nodejs-express
---
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
  name: csantana-nodejs-image
spec:
  type: image
  params:
    - name: url
      value: docker-registry.default.svc:5000/csantana/appsody-sample-nodejs-express:tkn

@csantanapr commented on Fri Oct 11 2019
Here is the log output, as you can see if running the mocha tests from the /project directory and second run on the /project/user-app
tkn pipelinerun logs nodejs-express-test-build-deploy-pipeline-run-gd2bq -f -n kabanero

output
[test-task : git-source-csantana-nodejs-git-rtsn5] {"level":"warn","ts":1570849767.937413,"logger":"fallback-logger","caller":"logging/config.go:69","msg":"Fetch GitHub commit ID from kodata failed: \"KO_DATA_PATH\" does not exist or is empty"}
[test-task : git-source-csantana-nodejs-git-rtsn5] {"level":"info","ts":1570849768.3113258,"logger":"fallback-logger","caller":"git/git.go:102","msg":"Successfully cloned https://github.com/csantanapr/appsody-sample-nodejs-express @ master in path /workspace/git-source"}

[test-task : npm-test] added 170 packages from 578 contributors and audited 295 packages in 6.59s
[test-task : npm-test] found 0 vulnerabilities
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test] ><EMAIL_ADDRESS>test /project
[test-task : npm-test] > mocha
[test-task : npm-test]
[test-task : npm-test] [Sat Oct 12 03:09:38 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics <IP_ADDRESS>909191743 (Agent Core 4.0.5)
[test-task : npm-test] [2019-10-12 03:09:38.674] [INFO] k8sutil.js - k8sutil K8sutil() Current namespace kabanero
[test-task : npm-test] [Sat Oct 12 03:09:39 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test] App started on PORT 3000
[test-task : npm-test]   Node.js Express stack
[test-task : npm-test]     /metrics endpoint
[test-task : npm-test]       ✓ status (42ms)
[test-task : npm-test]       ✓ contains os_cpu_used_ratio
[test-task : npm-test] [2019-10-12 03:09:39.307] [ERROR] k8sutil.js - k8sutil K8sutil() pods "nodejs-express-test-build-deploy-pipeline-run-gd2bq-test--4njjn" not found
[test-task : npm-test]       ✓ contains process_cpu_used_ratio
[test-task : npm-test]     /ready endpoint
[test-task : npm-test]       ✓ status
[test-task : npm-test]     /live endpoint
[test-task : npm-test]       ✓ status
[test-task : npm-test]     /health endpoint
[test-task : npm-test]       ✓ status
[test-task : npm-test]     /blah endpoint
[test-task : npm-test]       ✓ status
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test]   7 passing (178ms)
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test] ><EMAIL_ADDRESS>test /project/user-app
[test-task : npm-test] > mocha
[test-task : npm-test]
[test-task : npm-test] [Sat Oct 12 03:09:40 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics <IP_ADDRESS>909191743 (Agent Core 4.0.5)
[test-task : npm-test] [2019-10-12 03:09:41.503] [INFO] k8sutil.js - k8sutil K8sutil() Current namespace kabanero
[test-task : npm-test] [Sat Oct 12 03:09:41 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test] App started on PORT 3000
[test-task : npm-test]   Node.js Express Simple template
[test-task : npm-test]     / endpoint
[test-task : npm-test]       ✓ status (105ms)
[test-task : npm-test] [2019-10-12 03:09:41.961] [ERROR] k8sutil.js - k8sutil K8sutil() pods "nodejs-express-test-build-deploy-pipeline-run-gd2bq-test--4njjn" not found
[test-task : npm-test]
[test-task : npm-test]
[test-task : npm-test]   1 passing (177ms)
[test-task : npm-test]

@csantanapr commented on Fri Oct 11 2019
Here how they look in tekton dashboard of ICP4Apps v3
One weird thing, they run in the correct order test(1), build(2), deploy(3) but the rows in the UI doesn't show them like this when the pipelinerun is completed.

@csantanapr commented on Fri Oct 11 2019
Here is how my test pipeline resource looks like
apiVersion: tekton.dev/v1alpha1
kind: Pipeline
metadata:
  name: nodejs-express-test-build-deploy-pipeline
spec:
  resources:
    - name: git-source
      type: git
    - name: docker-image
      type: image
  tasks:
    - name: test-task
      taskRef:
        name: csantana-nodejs-express-build-task
      resources:
        inputs:
          - name: git-source
            resource: git-source
    - name: build-task
      taskRef:
        name: nodejs-express-build-task
      runAfter: [test-task]
      resources:
        inputs:
          - name: git-source
            resource: git-source
        outputs:
          - name: docker-image
            resource: docker-image
    - name: deploy-task
      taskRef:
        name: nodejs-express-deploy-task
      runAfter: [build-task]
      resources:
        inputs:
          - name: git-source
            resource: git-source
          - name: docker-image
            resource: docker-image

In case anyone is interested, we have a doc that shows how to create a pipeline that includes test task for nodejs-express, spring, and microprofile here https://ibm-cloud-architecture.github.io/Learning-Kabanero-101/web/1.0.0/tekton-create-pipeline.html
The only thing is that the container image for the test needs to be hardcoded at the creating of the task:

kabanero/nodejs-express:0.2
kabanero/java-spring-boot2:0.3
kabanero/java-microprofile:0.2


Define DynamoDB Transaction limit

Description
Defines the DynamoDB Transaction limit of 100 operations in a single transaction, similar to the way it is defined for CosmosDB.
This is necessary for Workflow, so it can be inferred what the max parallel operation batch size should be.

Linter's complaining


Update Release Notes for #189.

Pull request #189 didn't include an update to the Release Notes; these need to be added.

Pull request in #207.

Fixed in #207


Fix a11y addon, add ability to change context

Issue:#4889
A11y addon requires to have Info addon and also info add-on must have settings
// info addon settings
{
        inline: true, // where the components are inlined
        source: false,
}

What I did
So I removed this requirement and also add ability to configure context for a11y checking.

I see the info addon requires { inline: true }, is it possible to enable a11y without having to display info inline?
Thanks !

I see the info addon requires { inline: true }, is it possible to enable a11y without having to display info inline?
Thanks !

Not for actual version of a11y addon, but after approving this pull request we can use it without inline info option. I had the same issue and trying to fix it by this set of commits.


Pylance not working at all.

Language Server version: v2020.9.6
OS and version: ArchLinux, Kernel 5.8.10-arch1-1
Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
VSCode version: 1.49.0

Hi, it's not working at all whatsoever. I did change the languageServer to pylance in settings, I have python pacakge installed
Logs

python ~/.vscode-oss/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
python ~/.vscode-oss/extensions/ms-python.python-2020.9.111407/pythonFiles/pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
Error 2020-09-24 20:27:45: Listing Nuget Packages, Class name = d, completed in 1ms, has a falsy return value, Arg 1: "https://pvsc.blob.core.windows.net", Arg 2: "-stable", Arg 3: "", Arg 4: "https://pvsc.azureedge.net", Arg 5: Uri:/tmp/test.py, Return Value: undefined [SyntaxError: Container name format is incorrect.
at f (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:184960)
at v.t.containerNameIsValid (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:185222)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:410066
at Object.t.validateArgs (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:189467)
at z._listBlobsOrDircotriesSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:409993)
at z.listBlobsSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:367960)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313790
at new Promise ()
at listBlobStoreCatalog (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313768)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async listPackages (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313474)]
Error 2020-09-24 20:27:45: Get latest language server nuget package version, Class name = d, completed in 1ms, has a falsy return value, Arg 1: Uri:/tmp/test.py, Arg 2: "0.0.0", Return Value: undefined [SyntaxError: Container name format is incorrect.
at f (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:184960)
at v.t.containerNameIsValid (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:185222)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:410066
at Object.t.validateArgs (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:189467)
at z._listBlobsOrDircotriesSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:409993)
at z.listBlobsSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:367960)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313790
at new Promise ()
at listBlobStoreCatalog (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313768)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async listPackages (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313474)] {
vslsStack: [
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {}
]
}
Error 2020-09-24 20:27:45: Get latest version of language server, Class name = f, completed in 2ms, has a falsy return value, Arg 1: Uri:/tmp/test.py, Return Value: undefined [SyntaxError: Container name format is incorrect.
at f (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:184960)
at v.t.containerNameIsValid (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:185222)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:410066
at Object.t.validateArgs (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:189467)
at z._listBlobsOrDircotriesSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:409993)
at z.listBlobsSegmentedWithPrefix (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/node_modules/azure-storage.js:211:367960)
at /home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313790
at new Promise ()
at listBlobStoreCatalog (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313768)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async listPackages (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:47:313474)] {
vslsStack: [
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {},
CallSite {}, CallSite {}
]
}
Error 2020-09-24 20:27:45: Get language server folder name, Class name = f, completed in 5ms, has a falsy return value, Arg 1: Uri:/tmp/test.py, Return Value: undefined [TypeError: Cannot read property 'version' of undefined
at getLanguageServerFolderName (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:193095)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)]
Error 2020-09-24 20:27:45: Failed to start language server, Class name = r, completed in 9ms, has a falsy return value, Arg 1: Uri:/tmp/test.py, Arg 2: {"architecture":3,"path":"/usr/bin/python","version":{"options":{"loose":false,"includePrerelease":false},"loose":false,"raw":"3.8.5-final","major":3,"minor":8,"patch":5,"prerelease":["final"],"build":[],"version":"3.8.5-final"},"sysPrefix":"/usr","fileHash":"1464759c31e1da69bb7f6ffdb3bb22a39cfef12e58f642c2c193cd404a009bde8f52ade67fd62c17898def6a05c9dc9c3496101e0d1b200a7097d22d98f8f80e","envType":"Unknown","displayName":"Python 3.8.5 64-bit"}, Arg 3: {"documentSelector":[{"scheme":"file","language":"python"},{"scheme":"untitled","language":"python"},{"scheme":"vscode-notebook","language":"python"},{"scheme":"vscode-notebook-cell","language":"python"}],"synchronize":{"configurationSection":"python"},"outputChannel":{"name":"Python Language Server","_channel":{}},"revealOutputChannelOn":4,"middleware":{"configService":{"serviceContainer":{"container":{"options":{"autoBindInjectable":false,"defaultScope":"Transient","skipBaseClassChecks":false},"guid":"f396513f-11a8-c16b-a909-ba29840f2997","_bindingDictionary":{"_map":{}},"_snapshots":[],"_middleware":null,"parent":null,"_metadataReader":{}}},"workspaceService":{}},"lastCaptured":{},"nextWindow":0,"eventCount":0,"workspace":{},"connected":false,"eventName":"LANGUAGE_SERVER.REQUEST"},"connectionOptions":{"cancellationStrategy":{"_sender":{"folderName":"e9f61e331a2b997e6c7e60d9406fd9c97ff531926e"}}}}, Return Value: undefined [TypeError: Cannot read property 'version' of undefined
at getLanguageServerFolderName (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:193095)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-24 20:27:45: Starting language server, Class name = r, completed in 11ms, has a falsy return value, , Return Value: undefined [TypeError: Cannot read property 'version' of undefined
at getLanguageServerFolderName (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:193095)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-24 20:27:45: Restarting language server, Class name = r, completed in 12ms, has a falsy return value, , Return Value: undefined [TypeError: Cannot read property 'version' of undefined
at getLanguageServerFolderName (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:193095)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}
Error 2020-09-24 20:27:45: Failed to restart language server, Class name = r, completed in 12ms, has a falsy return value, , Return Value: undefined [TypeError: Cannot read property 'version' of undefined
at getLanguageServerFolderName (/home/behzad/.vscode-oss/extensions/ms-python.python-2020.9.111407/out/client/extension.js:24:193095)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:94:5)] {
vslsStack: [ CallSite {}, CallSite {}, CallSite {} ]
}

Pylance is only supported in official builds of VS Code; you appear to be using "VS Code - OSS" from the Arch repos. See https://github.com/microsoft/pylance-release/issues/135#issuecomment-662607952.


Modifier.pointerMoveFliter(onMove = {...}) does not called in nested composables

on this screen onMove functions in both children composables were not invoked.

sorry I i found solution)

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Implement a frontend framework like Vue or React

I am not really a fan of web designing, but I believe that the front-end side of Praesentia is getting a bit more overwhelming as the features increase.
Implementing a front-end framework will make the code cleaner and easier to maintain. If someone could wire up a PR for it, I would really appreciate that!

I think there is no need to do this. Not relevant anymore.


How do you get to the black hole?

Old issue. Ask in the discord, don't necro old issues


Fix WSL2 detection

Adds a more verbose uname command to fix detection of WSL2.

@groggemans This is a tweak to my previous contribution.  I had previously updated the case statements to detect for WSL substrings, but I neglected to update the uname call to give the more verbose output required to detect. This adds that change in.

Looks good, thank you!
I'm currently not on a machine where I can run the release script, but this should get included in a new release later this week!


Can't find Winload.efi

I am working on this project, but when I first boot, it gives me a blue screen saying that it can't find \windows\system32\winload.efi I know that this file exists after checking it using raspberryian on the pi. Any help would be greatly appreciated.

Not a WOA Deployer problem.


builds with node 6.0.0

For the just-released node.js 6.0.0 there was also an update to nan, 2.3.2. This PR loosens the dependency on nan so that a 6-compatible version can be pulled in.

👍

All of the tests pass for me after this change.  Node v6.0.0, OSX 10.11.4.

Try npm install nan first. I had the same issue and below command solved it for me.
npm install nan@latest
<EMAIL_ADDRESS>is actually installed


Fix some warnings

what's left is mostly a lot of UnitStrippedWarnings. cc @keewis

Nice, thanks a lot @dcherian !

Thanks for the reviews @keewis and @max-sixty


Updated Sentiment analysis project idea

Added idea for stock market prediction by twitter sentiment analysis

@add19 please add a relevant dataset and add this as a separate idea - and then reopen this Pull Request :)


Feature Request: Use mouse to attract or repel particles

Sometimes I sit watching and wish I could change it a tiny bit.
I think left click should attract and right click repel or vise versa.

Absolutely, that has been something I thought of adding but never got around to do it.


Calling routine doesn't dispatch any action

I've upgraded to v2 and all of my actions were broken.
Changes I've made into my code is:

Use routinePromiseWatcherSaga instead of routinesWatcherSaga to add to saga middleware.
Use bindRoutineToReduxForm and pass created routine to it to create redux-form compatible handler.
Update mapDispatchToProps implementation to remove bindRoutineCreators and return routines directly as below:

function mapDispatchToProps(dispatch) {     return {         ...{ commandBarAddItemsRoutine },         dispatch     }; };

Replace any this.props.routine.trigger(payload) with this.props.routine(payload). (optional)

Before upgrading to v2, my codes works well. I've not updated other related packages like redux, redux-saga so I think the issue is related to this package.

Hi, may I see the code, that does not work: component, and saga?

If you use bindRoutineToReduxForm you do not need to pass bound routine thru mapDispatchToProps.

Ok here is it.
`//Routine and triggerer
import { put, call } from 'redux-saga/effects';
import { createRoutine, bindRoutineToReduxForm } from 'redux-saga-routines';
export const chooseLetterPreparingFindEmbeddedLetterIdRoutine = createRoutine('CHOOSE_LETTER_PREPARING_FIND_EMBEDDED_LETTER_ID');
export const chooseLetterPreparingFindEmbeddedLetterIdHandler = bindRoutineToReduxForm(chooseLetterPreparingFindEmbeddedLetterIdRoutine);
export function* chooseLetterPreparingFindEmbeddedLetterIdTrigger(action) {
try {
console.log(chooseLetterPreparingFindEmbeddedLetterIdRoutine.request, action);
yield put(chooseLetterPreparingFindEmbeddedLetterIdRoutine.request());
    const response = yield call(wordService.findEmbeddedLetterId);

    yield put(chooseLetterPreparingFindEmbeddedLetterIdRoutine.success(response));
} catch (error) {
    yield put(chooseLetterPreparingFindEmbeddedLetterIdRoutine.failure(error));
} finally {
    yield put(chooseLetterPreparingFindEmbeddedLetterIdRoutine.fulfill());
}

}`
`import { fork, takeLatest } from 'redux-saga/effects';
import { chooseLetterPreparingFindEmbeddedLetterIdRoutine, chooseLetterPreparingFindEmbeddedLetterIdTrigger } from './choose-letter-preparing.action';
export function* appWatcherSaga() {
yield [
...,
fork(takeLatest, chooseLetterPreparingFindEmbeddedLetterIdRoutine.TRIGGER, chooseLetterPreparingFindEmbeddedLetterIdTrigger),
....
];
}`
`Component usages
import { chooseLetterPreparingFindEmbeddedLetterIdRoutine } from '../actions/choose-letter-preparing.action';
export class ChooseLetterPreparingComponent extends React.Component {
componentDidMount() {
this.props.chooseLetterPreparingFindEmbeddedLetterIdRoutine(payload);
}
render() {
    return (
        <p>
            blah blah blah
        </p>
    );
}

}
function mapStateToProps(state) {
return { ... };
}
function mapDispatchToProps(dispatch) {
return {
...{ chooseLetterPreparingFindEmbeddedLetterIdRoutine },
dispatch
};
};
export default withRouter(connect(mapStateToProps, mapDispatchToProps)(ChooseLetterPreparingComponent));
`

Problem is here:
function mapDispatchToProps(dispatch) {
    return {
        ...{ chooseLetterPreparingFindEmbeddedLetterIdRoutine },
        dispatch
    };
};

Try to change it with following:
function mapDispatchToProps = {
  chooseLetterPreparingFindEmbeddedLetterIdRoutine,
};

Thank you @afitiskin

@afitiskin If i need to this.props.dispatch to dispatch an action that is not in the form of routines, what I have to do?
function mapDispatchToProps(dispatch) {
    return {
        myRoutine,
        dispatch
    };
};

Use bindActionCreators from redux package as you do with simple action creators, or just manually dispatch result of routine call: dispatch(myRoutine())

@afitiskin As you told me, I have to write my mapDispatchToProps like below.
const mapDispatchToProps = {
  myRoutine,
};

Above result don't provide dispatch to this.props. If I use below, nothing will be dispatched.
function mapDispatchToProps(dispatch) {
    return {
        myRoutine,
        dispatch
    };
};

I've confused a little bit. Using bindActionCreators also requires this.props.dispatch.

As I see you do not know how connect works. Please read carefully docs of react-redux.
You have 2 options:

Just not provide mapDispatchToProps. In this case your component will get dispatch as a prop. To dispatch routine action you need to do this.props.dispatch(myRoutine())
Use bindActionCreators from redux:

mapDispatchToProps = (dispatch) => ({
  ...bindActionCreators({
    myRoutine1,
    myRoutine2,
  }),
  dispatch,
});

If you pass an object to mapDispatchToProps as I recommend above, react-redux will use bindActionCreators internally to bind passed action creators.
And one more note: why you need both: bound action creators (or routines) and dispatch? I think you are doing something wrong...


Potential redundancy in using np.array

Thank you for submitting a TensorFlow documentation issue. Per our GitHub
policy, we only address code/doc bugs, performance issues, feature requests, and
build/installation issues on GitHub.
The TensorFlow docs are open source! To get involved, read the documentation
contributor guide: https://www.tensorflow.org/community/contribute/docs
URL(s) with the issue:
Please provide a link to the documentation entry:
https://www.tensorflow.org/tutorials/generative/deepdream
Description of the issue (what needs changing):
In this example, we are already performing this: original_img = np.array(original_img) in the beginning. Then, what is the point of repeating it here: img = tf.constant(np.array(original_img)) and here: shift_down, shift_right, img_rolled = random_roll(np.array(original_img), 512)?

@sayakpaul Taking it up an octave and Scaling up with tiles are two different techniques.
In the 1st technique, you converted an image to tensor and then cast it to float32 to multiply it by an octave(i.e., floating point number) but in the second technique you are just passing in the original image that is a numpy array directly to the function.
I don't think this is redundant information.

@gowthamkpr

@sayakpaul Taking it up an octave and Scaling up with tiles are two different techniques.

I guess I never mentioned scaling up octaves and tiling are the two same techniques.
Regarding the redundancy, the order of the lines code (that I mentioned initially) in the tutorial goes like the following:
original_img = np.array(original_img)
img = tf.constant(np.array(original_img))
shift_down, shift_right, img_rolled = random_roll(np.array(original_img), 512)

All I am trying to say is if we are creating an np.array of the original_img in the very beginning then what's the point of doing it again for the downstream tasks as original_img is already an np.array (made in the first step)?

@sayakpaul Yes, I agree with you. We will take a look into it. Thanks!

I opened a PR for the same as well. @gowthamkpr


Fix kyuubi-ctl error output

Why are the changes needed?

Print error message to right place.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

cc @lightning-L

please make the PR title meaningful

Thanks, merging to master


Threading cannot work properly when argument contain list

Describe the bug
Threading cannot work properly when argument contain list. It seems thread accept contents of list as its arguments. This problem show in numpy array too.
Expected behavior
I expect the thread will accept a reference point to each list beginner, so that I can use in the function
To Reproduce
import threading

def temp(l):
    for i in range(3):
        l[i]=l[i]+1

array = [[1,2,3],[4,5,6]]
threads = []
for i in range(2):
    t = array[i]
    threads.append(threading.Thread(target=temp,args=(t)))
for thread in threads:
    thread.start()
for thread in threads:
    thread.join()

print(array)

My Platform
Windows 10
Python 3.7.3

It  seem that this problem specifically occur when I put a list from 2D array as args in threading. However temp(array[0]) works for me.

Hi, this issue tracker is for issues with the codebase behind pypi.org itself, not the projects hosted on PyPI, nor for Python itself.
You should report this issue to the tracker for the project in question instead. For Python, this will be on https://bugs.python.org I believe


UI design

Hi, I would like to give some UI design for this app using Figma.
Figma is a designing tool where web and app designs can be created.

Hi, I would like to give some UI design for this app using Figma. Figma is a designing tool where web and app designs can be created.

I believe the UI of this package is customizable as per the developer. It doesn't need any UI design. The UI in the screenshot are just examples. Is that what you meant?

yes

yes

If you have any other idea regarding the project, let me know! Closing this as of now.
Thanks for your time!


install: make conda, choco, or pip the default method for Win. Installer has this problem:

Similar to iterative/dvc#2677, Windows prevented me from running the latest installer (dvc-0.91.1.exe) with a screen but I didn't take a screenshot and now it's not happening again with any version after I told it to run it anyway. It looked like this but green:

and the [Run anyway] button is hidden until you click a "More info" link.

I think we already have one in docs to rearrange the order of options we recomend

@jorgeorpinel https://github.com/iterative/dvc/issues/936

I think we already have one in docs to rearrange the order of options we recomend

True, closing in favor of #904


adding support AlertBase-CVP.json

Adding support to locally download AlertBase-CVP.json file and its corresponding latest.md5 file from Software downloads.

will be submitting another PR for this. aborting this merge.


support --nofork on the Windows batch files (fix issue #658)

Anybody have any thoughts? :smile_cat:

I'm not sure but we've better to add setlocal on the top of bat file.

Ahh, I've never played around with setlocal before.   How far back does support for that feature go?

setlocal works on XP, So you can put setlocal in all of the bat file which dosinst generated, I think.

Ooooh, and I don't need to know all the exit paths: the endlocal is implicit, according to this.

@mattn, I've added that now!


Refacting search logic without using fixed DB logic

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


MT-32 : no Mac platform support (neither x86_64 nor Mac M1)

The native libraries are missing in the Nuget package Mt32emu.net

In the future: this could replace the current solution:
https://github.com/nukeykt/Nuked-SC55
It needs to be complete, and be as agood as MUNT.
It could also complete Mac support for Spice86 of MT-32 emulation.


Type inference for for loops

Now that basic support for associated types is implemented, we should be able to
implement type inference for for loops. E.g. here:
let v = Vec::new();
v.push("foo");
for x in v {
    x;
}

hovering x should say &str (and hence we should get completions for x., etc...).
rustc implements for loops by desugaring to a loop.
We could do the same (once we support resolving associated type paths), but I
feel it'd be simpler to implement type inference for them directly (at least for
now).
Basically the only thing we have to do is introduce a type variable for the type
of the loop variable, and make sure that this variable equals the projection of
the IntoIterator::Item associated type of the iteratee. E.g. let's say we have
let v = Vec::new();
for x in v {}

So at the point we're looking at the for loop, we've already inferred that v
is of type Vec<?0> (where ?0 is an inference variable). We then introduce a
new inference variable ?1 for the type of x and need to 'remember' the
relationship <Vec<?0> as IntoIterator>::Item = ?1. (In this case we could just
immediately resolve the projection, but in general that may not always be
possible.) The type inference process keeps such relationships as
'obligations' that it then regularly tries to resolve to gain further information. Currently
we only have Implements obligations, so we need to add Projection
obligations that say 'this associated type projection equals this other type'. The variant is actually already there, just commented out because we didn't need it so far :)
So, the basic steps to implement this are:

Add a test for for loop inference to ty/tests.rs
Add the Projection variant to Obligation
Handle these obligations during obligation resolution.
This should work very similar to the existing code for Implements, except
it needs to call the normalize query instead of implements.
When looking at a for loop, introduce a type variable for the pattern (where it currently just uses
Ty::Unknown), and register a Projection obligation that the projection of
::std::iter::IntoIterator::Item for iterable_ty should equal the new type
variable. Note that IntoIterator isn't a lang item, since rustc just uses a
desugaring, so we need to somehow resolve the absolute path to get the trait.
See whether the test passes.

I think that's it? The test might be a bit awkward because it needs to define
the IntoIterator trait at the right absolute path, and in general having to
hardcode the path is a bit weird (but no different than what rustc does, I
think).
Here's a Zulip stream for questions about this.

I'd like to tackle this issue if no one is solving it.

Note, this is implemented, but it's not working yet correctly because Chalk seems to get confused by the impl<T> IntoIterator for T where T: Iterator blanket implementation, so I'll leave this open until we find a solution for that.

It's great that we have a (partial) implementation, and sorry that I have not solved this issue until now. I was working on this but I need to gain more knowledge about RA and rust, so it took me too much time to get a solution.
Congrats.

The bug with the IntoIterator implementation has actually been fixed in Chalk by now, and this is usually working.


Bug 2093772: add env resource changes boot order pending alert

📝 Description
the pending alert is linked to the entire bootorder of all disks but we want to know only about the bootdisk when is changed
🎥 Demo
before:

after:

Signed-off-by: Aviv Turgeman<EMAIL_ADDRESS>

/bugzilla refresh


Refactor Deadline Submission JobInfo

Changelog Description
This PR tries to make DL submissions easier, mostly handling of JobInfo segment. Collection of values is moved out of submission phase much earlier where values could be filled from default values in Settings or overriden by selected list of field by artist in Publisher UI.
Move to universal collector should help with potential validation of filled values.
Profiles in Settings should allow more control of values (like priority, limit_groups) based on task_types or hosts etc.

Additional info
Should be used with https://github.com/ynput/ayon-core/pull/958  !!
All DCC need to be tested:

[x] AfterEffects
[ ] Blender
[ ] CelAction
[ ] Fusion
[ ] Harmony
[ ] Houdini
[ ] Max
[ ] Maya
[x] Nuke
[ ] Unreal

Testing notes:

do regular DL publishing
test that nothing breaks
update ayon+settings://deadline/publish/CollectJobInfo with new defaults and check if they propagete to Publisher
update values in Publisher if they propagate to DL

Currently translated DCC:

blender
houdini (questions about submit_houdini_render_deadline.export_* - should they be pushed to collect_jobinfo too?)
harmony
max
maya
unreal

All of them needs to be thoroughly tested.
Issue is with:

nuke
fusion
celaction

which are not using abstract_submit_deadline.AbstractSubmitDeadline.
Not sure I am best person to switch them to AbstractSubmitDeadline if they should (and I think they should).

houdini (questions about submit_houdini_render_deadline.export_* - should they be pushed to collect_jobinfo too?)

@MustafaJafar @antirotor thoughts?
I'd say, likely not? Or least, they are separate from the render job and publish job.
In most cases we have the following deadline jobs:

Render job
Publish job

But for these we have:

Export job
Render job
Publish job

The export job runs the host application on Deadline to export a scene file format, like e.g. .usd or .ifd or .ass (or whatever render scene file format the renderer supports) for then the renderer to "render" without the host application, usually through the standalone renderer instead. So a .ass file would be rendered through e.g. Arnold job on Deadline, and not a Houdini job. Similarly, a .usd exported file may be rendered through HuskStandalone deadline plug-in which doesn't require e.g. the Houdini license, etc.
However, going based on some recent discussion with @iLLiCiTiT it does make sense to push these to a Collector so the choices made for those attributes are accessible e.g. during validation as well easily by collecting them into instance data in a logical way.

Issue is with:
* nuke

* fusion

* celaction

which are not using abstract_submit_deadline.AbstractSubmitDeadline.
Not sure I am best person to switch them to AbstractSubmitDeadline if they should (and I think they should).

I could give Fusion a go if needed and we want to do that ASAP. I suppose that'd also make it somewhat of a test run for this pR while we're at it.

@BigRoy Should I remove collect_pools and move it to collect_jobinfo in this PR? It makes sense to do it now when it will need to be tested, imho.

@BigRoy Should I remove collect_pools and move it to collect_jobinfo in this PR? It makes sense to do it now when it will need to be tested, imho.

Good question. It must be noted that it means existing instances will be backwards incompatible and any pools previously set on an instance will then be 'misconfigured' after this PR.
Preferably we find a way to have backwards compatibility for that? But I don't know how feasible that is. @iLLiCiTiT ?
I'd say that if moving it to Collect Job Info plug-in cleans this up massively then I think we should move it over too - yes.

Is there possibility of not being it backward compatible? All instances that should be pushed to DL will need to go through collect_jobinfo so that value will be resolved there and then.

Is there possibility of not being it backward compatible? All instances that should be pushed to DL will need to go through collect_jobinfo so that value will be resolved there and then.

An existing instance would have its chosen attribute definition values stored in publish_attributes.CollectPools. Now with this PR it's reading them from publish_attributes.CollectJobInfo (or alike). Which means that existing instances in existing scenes would need to be reconfigured for the new collector because the original configured attributes are basically 'lost data' and not converted to the new plug-in.
Does that explain it? Or what did you mean?

I think groups are missing.

Are we duplicating the frames to fix?

Frames: "Explicit frames to be rendered. (1, 3-4)", (what about frame gaps when publishing?)
Frames To Fix: Insert frame(s) to be rerendered (It's not propagated to farm submissions.)

Are we duplicating the frames to fix? (or may be are we adding support to make it work on farm)
* **Frames:** "Explicit frames to be rendered. (1, 3-4)", (what about frame gaps when publishing?)

* **Frames To Fix:** Insert frame(s) to be rerendered (It's not propagated to farm submissions.)

This is a tricky case because these are actually different use cases.

"Frames": Render only these frames (regardless of whether it's a fix to the previous render). It's totally fine now to submit e.g. a render of just 1, 10, 20 or 1-20, 50-100 and leave a gap in the publish. At least, that's how I understood.
"Frames to fix": Render only these frames but apply them to the previous render. (Like extend frames logic we had elsewhere)

So no, we're not duplicating it but we're definitely facing confusion here. I think we should rethink the "Frames to fix" so that you don't need to supply just frames there - but instead allow your full submission to be just a 'fix submission' or alike - and for the frame ranges you may use the regular frame ranges.

faced this error.
I've almost the default profile (only exposed everything in the list) and didn't put any values in the publisher.
Traceback (most recent call last):
  File "C:\Users\Mustafa Taher\AppData\Local\Ynput\AYON\dependency_packages\ayon_2410301643_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
    runner(*args)
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\plugins\publish\global\collect_jobinfo.py", line 45, in process
    job_info = AYONDeadlineJobInfo.from_dict(attr_values)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\lib.py", line 376, in from_dict
    "Pool": data["primary_pool"],
            ~~~~^^^^^^^^^^^^^^^^
KeyError: 'primary_pool'

faced this error. I've almost the default profile (only exposed everything in the list) and didn't put any values in the publisher.

Fixed.

another error 😶🌫
DEBUG: http://<IP_ADDRESS>:5000 "POST /graphql HTTP/1.1" 200 105
DEBUG: Response <RestApiResponse [200]>
DEBUG: Looking for matching profile for: hosts: "houdini" | product_types: "pointcache" | task_names: "modeling" | task_types: "Modeling"
DEBUG: "pointcache" not found in "product_types": ['review', 'render', 'prerender']
DEBUG: "houdini" not found in "hosts": ['standalonepublisher']
DEBUG: "houdini" not found in "hosts": ['maya']
DEBUG: "houdini" not found in "hosts": ['traypublisher']
DEBUG: "houdini" not found in "hosts": ['max']
DEBUG: Profile selected: {'product_types': [], 'hosts': [], 'task_types': [], 'task_names': [], 'template_name': 'default'}
DEBUG: Submitting Deadline publish job ...
DEBUG: Starting new HTTP connection (1): <IP_ADDRESS>:8081
DEBUG: http://<IP_ADDRESS>:8081 "POST /api/jobs HTTP/1.1" 200 3832
Traceback (most recent call last):
  File "C:\Users\Mustafa Taher\AppData\Local\Ynput\AYON\dependency_packages\ayon_2410301643_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
    runner(*args)
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\plugins\publish\global\submit_publish_cache_job.py", line 374, in process
    json.dump(publish_job, f, indent=4, sort_keys=True)
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\__init__.py", line 179, in dump
    for chunk in iterable:
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 432, in _iterencode
    yield from _iterencode_dict(o, _current_indent_level)
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 406, in _iterencode_dict
    yield from chunks
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 326, in _iterencode_list
    yield from chunks
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 406, in _iterencode_dict
    yield from chunks
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 406, in _iterencode_dict
    yield from chunks
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 439, in _iterencode
    o = _default(o)
        ^^^^^^^^^^^
  File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.370\python311\Lib\json\encoder.py", line 180, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type AYONDeadlineJobInfo is not JSON serializable

Implemented enums for:

machines
groups
limit_groups

Not sure if we are caching anything via Deadline addon, doesn't seem so.

another error 😶🌫

Should be fixed.

found another error 👼
Traceback (most recent call last):
  File "C:\Users\Mustafa Taher\AppData\Local\Ynput\AYON\dependency_packages\ayon_2410301643_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
    runner(*args)
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\plugins\publish\global\submit_publish_cache_job.py", line 351, in process
    inst.data["deadline"].pop("job_info")
    ^^^^^^^^^
AttributeError: 'dict' object has no attribute 'data'

And one more error 😇
=======================================================
Error
=======================================================
Error: Global job preload script 'C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py': RuntimeError : Missing required env vars: AYON_PROJECT_NAME, AYON_FOLDER_PATH, AYON_TASK_NAME, AYON_APP_NAME (FranticX.Scripting.PythonNetException)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py", line 725, in __main__
    inject_ayon_environment(deadlinePlugin)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py", line 543, in inject_ayon_environment
    "Missing required env vars: AYON_PROJECT_NAME,"
   at Python.Runtime.PyObject.Invoke(PyObject[] args)
   at Python.Runtime.PyObject.InvokeMethod(String name, PyObject[] args)
   at FranticX.Scripting.PythonNetScriptEngine.CallFunction(String moduleName, String functionName, Object[] args)
   at Deadline.Plugins.PluginWrapper.d()
   at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)

=======================================================

And one more error 😇
=======================================================
Error
=======================================================
Error: Global job preload script 'C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py': RuntimeError : Missing required env vars: AYON_PROJECT_NAME, AYON_FOLDER_PATH, AYON_TASK_NAME, AYON_APP_NAME (FranticX.Scripting.PythonNetException)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py", line 725, in __main__
    inject_ayon_environment(deadlinePlugin)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\Major-Kalawy\plugins\672953049e7c913653c87dcd\GlobalJobPreLoad.py", line 543, in inject_ayon_environment
    "Missing required env vars: AYON_PROJECT_NAME,"
   at Python.Runtime.PyObject.Invoke(PyObject[] args)
   at Python.Runtime.PyObject.InvokeMethod(String name, PyObject[] args)
   at FranticX.Scripting.PythonNetScriptEngine.CallFunction(String moduleName, String functionName, Object[] args)
   at Deadline.Plugins.PluginWrapper.d()
   at Deadline.Plugins.PluginWrapper.StartJob(String& outMessage, AbortLevel& abortLevel)

=======================================================

@MustafaJafar which type of job/publish did you submit in this case?

@MustafaJafar which type of job/publish did you submit in this case?

Houdini cache.

This looks weird.

It should be

I've applied my suggestion locally. and both render and split export and render works fine in Houdini.

This looks weird.

Fixed.

Not all the parameters are propagated to the job.

Also, a weird funny thing
When only submitting a cache to farm, Some ayon env variables are mssing.

But, when submitting a cache as well as a render from my scene at the same time, the ayon env variables are no longer missing.

Also, a ~weird~ funny thing When only submitting a cache to farm, Some ayon env variables are mssing.
But, when submitting a cache as well as a render from my scene at the same time, the ayon env variables are no longer missing.

@BigRoy found out the reason.
The cache publish family is being triggered at a later order that the the deadline collector therefore, it's never triggered when submitting cache to deadline
https://github.com/ynput/ayon-houdini/blob/9167fdcc101d1ac2f0ff0feabf615ae3fb2638e2/client/ayon_houdini/plugins/publish/collect_cache_farm.py#L14

Other than the issues mentioned in #49 (comment) and #49 (comment) This PR works in Houdini.

For what it's worth, I suspect we can bump that collector to a later order just fine. Feel free to nudge it towards the end of CollectorOrder.
Also, I think the issue may actually already exist outside of this PR.

Removed env_search_replace_values and env_allowed_keys
It seems obsolete and not really useful to push through artist values of environment variables.
Possible filtering of env vars should be handled in extractenvironments

I don't know it this comment relates to this PR.
But, is it intended for the tile assembly to use a value from another plugin's settings?
https://github.com/ynput/ayon-deadline/blob/a04203add8a6692280566347326d010c15d4ff2f/client/ayon_deadline/plugins/publish/maya/submit_maya_deadline.py#L458-L461
Maybe we can have one more setting for it in the Maya Submit to deadline .
and modify the code in in the maya submitter to
assembly_job_info.Pool = self.tile_pool or instance.data.get("primaryPool", "")

or
assembly_job_info.Pool = attr_values.get("tile_pool",
                                         instance.data.get("primaryPool", ""))

any idea why disabling the plugin in settings doesn't stop the plugin from working?

I cleaned up active/enabled/optional for DCC submission plugins as it doesnt make sense for them to be optional or could be disabled (as now they are separate and have only impact for particular host - previously we were disabling broken plugins to limiting affecting other DCCs).
I removed submission plugins which lost all their fields to global JobInfo.

group and pool weren't propagated.

Fixed.

Sorry one more bug 😅
when splitting render and export in Houdini,
Both render and export jobs get the values of export.

The current default value of Collect JobInfo plugin doesn't work.

I think it's similar to the bug discussed above https://github.com/ynput/ayon-deadline/pull/49#pullrequestreview-2430889131
Traceback (most recent call last):
  File "C:\Users\Mustafa Taher\AppData\Local\Ynput\AYON\dependency_packages\ayon_2411052009_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
    runner(*args)
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\plugins\publish\global\collect_jobinfo.py", line 52, in process
    job_info = AYONDeadlineJobInfo.from_dict(attr_values)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\Ynput\ayon-deadline\client\ayon_deadline\lib.py", line 519, in from_dict
    "ChunkSize": data["chunk_size"],
                 ~~~~^^^^^^^^^^^^^^
KeyError: 'chunk_size'

My bad about disabling CollectJobInfo, it shouldnt be possible to disable it at all, but commit didnt get through.
Fixed, submission plugins enablement/optionality removed as it doesn't make much sense anymore.
Provided basic profile for CollectJobInfo

It works pretty well in Houdini.
Publishing cache doesn't error any more. Cache jobs don't error any more.
Publishing renders works fine with different targets. Render jobs work fine.
(there's still  one bug mentioned in https://github.com/ynput/ayon-deadline/pull/49#issuecomment-2470912116  where export job attributes override render job attributes. I'll try to debug it on my side.)

Tested Nuke. it works.
maybe we can update the label of the jobs to differentiate between bake and render but that's a separate issue I guess.

Related, my PyCharm is bitching about unexpected argument here https://github.com/ynput/ayon-deadline/blob/fa016580575b9eedcd7526aabcd2c3cfa3ec5281/client/ayon_deadline/plugins/publish/global/submit_publish_job.py#L402

Works well when submitting from blender aka not failing...still need to  test the profiles and propagation of attribs to the host and deadline tho,
just the core func without issues with blender atm.

Working together with Fusion been successfully tested.

I have tested in maya and getting error during publishing:
Fixed

Failed in Unreal with:

Could be because wrong ayon-core? (Should be used with https://github.com/ynput/ayon-core/pull/958 )

@kalisp I dont see any addon settings when built the addon package....it used to work with older commits (when first time tested)
??

@kalisp now addon settings been visible...so all good on this front!


pretrained model

Hi,foamLiu. Thanks for your pytorch implementation of Tacotron2! Could you please share the weight file？Thank you very much.

The author has shared his model in release.

Thanks @zsl24