Start Marketing / Docs Site

Choose a system suitable for building a site tailored both for marketing and documentation.
Leading Options:
Astro
Vitepress
Docusaurus
Ideally the simplest option that can produce a decent looking site that covers the basics without too many issues.

Site started. Needs additional documentation though.


Added build.exe

Description

Added a windows application built off builder.py using auto-py-to-exe.
Updated README to include it as a viable build option for users without python interpreter installed.

Fixes # The assumption that users have python already installed.
Type of change
Please select the relevant option.

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[x] Documentation update
[x] Other (please describe below)

Checklist
Please check the following items before submitting your pull request.

[x] I have read the CONTRIBUTING.md document.
[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.
[x] I have tested that my RP does not break anything.

Additional information

File looks clean to me. https://www.virustotal.com/gui/file/bc3e0a088b549740342bf6b3104bc7a5c9de86ab90ea61ea16b9fd3f5e9f1f02?nocache=1
Merged into v1.0.0 for now. Will be merged into Main soon in a bigger PR along with some other items.
Would be cool to add our a icon / logo to the build.exe in a future update.

Reverting this for now, after some reconsideration. #151
We will need to discuss this with the entire team.

I have done some reconsideration and thought about it and concluded with:

This is really stuff you should learn as a developer anyways.
Bundling an EXE with our source code opens up a lot of security risks.
I know a lot of people who refuse to clone projects with EXE files in them.
It creates more maintenance as we need to rebuild the exe file with the latest version of our project, which can be time-consuming and require additional resources.
They are in general larger in terms of file size
Could potentially create legal issues as we may need to obtain the necessary licenses or permissions before bundling external dependencies required to run the exe with your project.


Feature: Bonemeal Wisteria Leaves + hitbox alignment

Bonemealing wisteria leaves should generate a hanger. Bonemealing those hangers should grow them further.
Also the hitbox for wisteria hangers is not aligned to the model, which is annoying

Resolved on b1.7 branch. Change needs to be ported to 1.18.2

Resolved on 1.18.2


Linked List Insertion

❗Write Code in Only One Language ( CPP , C , Java , Python )
Give File Name :  Linked List Insertion  ✅ In respective language folder
📑 DESCRIPTION
Linked List Insertion

Create a link list of size N according to the given input literals. Each integer input is accompanied by an indicator which can either be 0 or 1. If it is 0, insert the integer in the beginning of the link list. If it is 1, insert the integer at the end of the link list.
Hint: When inserting at the end, make sure that you handle NULL explicitly.
Example 1:
Input:
LinkedList: 9->0->5->1->6->1->2->0->5->0
Output: 5 2 9 5 6
Explanation:
Length of Link List = N = 5
9 0 indicated that 9 should be
inserted in the beginning. Modified
Link List = 9.
5 1 indicated that 5 should be
inserted in the end. Modified Link
List = 9,5.
6 1 indicated that 6 should be
inserted in the end. Modified Link
List = 9,5,6.
2 0 indicated that 2 should be
inserted in the beginning. Modified
Link List = 2,9,5,6.
5 0 indicated that 5 should be
inserted in the beginning. Modified
Link List = 5,2,9,5,6.
Final linked list = 5, 2, 9, 5, 6.

Example 2:
Input:
LinkedList: 5->1->6->1->9->1
Output: 5 6 9

Follow-up: Can you come up with an algorithm that is less than O(n^2) time complexity?

Hello, how are you?
I think I solved this problem... check my pull request (https://github.com/Akatsuki-Coding-Club/Data-Structures-Algorithms-Akatsuki-Coding-CLub/pull/74)

Hi! I'd like to solve the problem in C so could you assign it to me?


How to use with springboot project？

Hi @meiMingle - currently this plugin supports being built into a distribution with the Gradle application plugin and the jib Gradle plugin for building container images. If your spring boot build leverages either of those plugins, the distributions should work just fine and have the javaagent configured. If there is an alternative packaging/distribution method you would like, feel free to file an issue with specific details. I won't necessarily have time for it but can prioritize it with other initiatives. I'm sure there are many ways to package spring boot applications into a distribution for deployment, some of which are a good fit for this plugin to handle.

The Spring Boot Gradle plugin provides a number of Boot-specific tasks for running and packaging the application:
% ./gradlew tasks | grep boot
bootRun - Runs this project as a Spring Boot application.
bootTestRun - Runs this project as a Spring Boot application using the test runtime classpath.
bootBuildImage - Builds an OCI image of the application using the output of the bootJar task
bootJar - Assembles an executable jar archive containing the main classes and their dependencies.
assembleBootDist - Assembles the boot distributions
bootDistTar - Bundles the project as a distribution.
bootDistZip - Bundles the project as a distribution.

As far as I can tell, these tasks differ from the built-in ones because:

They detect the main class name by scanning for the @SpringBootApplication annotation, rather than making the user specify it.
The distribution contains a single jar that contains a few .class files and a lot of nested .jar files (as opposed to .jar files at the top level, or a shaded jar).
The launch script is different.

Hopefully that helps to understand the effort required to add support for these tasks.

The OTel "Getting Started" instructions for Java use Spring Boot and Gradle. Fixing this issue would help to improve the onboarding experience for all new users of OTel-Java.

I currently have no plans to develop spring-specific support for this plugin personally. If someone would like to lead this initiative, I'm happy to re-open this issue and provide guidance on the kind of contributions I'd be open to accepting.

Thanks @ryandens, it's great to know that you're open to reviewing a contribution for Spring support. When I have time, I'll draft a PR and seek your help for any blockers.

No problem! Note, given the complexity of this change it will require unit and functional tests


Remove KtTreeCompiler

After #7007 all our clients provide a list of files to evaluate, it doesn't provide directories nor include/exclude rules.
For that reason we can remove KtTreeCompiler and the code related with include/exclude input.
This PR is ready but it goes on top of #7007

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against 311487c1bbdcdb4cea069659c2661f6e8d680a5e


Compass3D Support

Hey, I just wanted to let you know that I added support for this mod to my mod Compass3D. Compass3D is a client-side mod that adds an overlay arrow to compasses to indicate the y-direction of the target, to make it easier to find the target. Happy modding! :D

Added a link to your mod to the description of Dark Compass.
Many thanks for including my mod!


Criticism: Using Custom Router Harms Adoption

I have about a month of patternfly_yew use under my belt and have found my end-products with it to be excellent. However, getting there is unnecessarily painful.
This quickstart project uses a custom router (https://github.com/ctron/yew-nested-router) rather than the ubiquitous yew_router.
I have read the issue that spawned the creation of the custom router and I am happy to believe that it is a technically superiour router. However, it is not a drop-in replacement for yew-router, and in my experience, pretty challenging to understand.
Trying to learn this custom router and the particulars of this component framework at the same time is high-friction.
I don't believe that this example project requires the custom router. I am using yew_router with my project without any pain so far.
Suggestion
yew-nested-router should not used for this quickstart project.[^1]
I'm happy to work on a PR to make this happen, but only if this change would be welcome.
[^1]: I think it should also be opt-in for the parent project, patternfly_yew, rather than opt out with  default-features = false; a component library shouldn't (IMO) dictate router choices - it makes it much more difficult to switch to and away from, making the perceived technical debt much higher

So the main projects contributing so far to this project make use of the nested router, because it's required. I am absolutely open adding an additional implementation, but I would want to keep the current implementation the default.
The main reason for that is that it automatically gets more test coverage.

Trying to learn this custom router and the particulars of this component framework at the same time is high-friction.

So maybe that's something to improve. If you could give some feedback on what would have helped you to have an easier introduction, that would definitely be helpful, and might let others benefit too.
The reason why it's enabled by default in patternfly-yew is that, if you want to use it, it's easier to get started. Assuming there would be an additional implement (e.g. based on yew-router) it might indeed be an idea to disable both by default and let the user choose.

So the main projects contributing so far to this project make use of the nested router, because it's required. I am absolutely open adding an additional implementation, but I would want to keep the current implementation the default.
The main reason for that is that it automatically gets more test coverage.

I can appreciate that motivation; more testing makes better libraries. It will hurt adoption, though, but I can accept if that is a lower priority.
yew-nested-router has effectively has one contributor; If you disappear, we will either have to fork and maintain that dependency or convert back to yew-router, which is a technical debt time-bomb.
patternfly_yew feels less risky in the same sense because the use-case is much more clear and broad: people want component libraries and are willing to contribute to them (I maintain yew-bootstrap and get lots of helpful contributions, and it's tiny!). We don't have many of them for Rust. I don't think the same motivation exists for router alternatives.

Trying to learn this custom router and the particulars of this component framework at the same time is high-friction.

So maybe that's something to improve. If you could give some feedback on what would have helped you to have an easier introduction, that would definitely be helpful, and might let others benefit too.

The reason why it's enabled by default in patternfly-yew is that, if you want to use it, it's easier to get started. Assuming there would be an additional implement (e.g. based on yew-router) it might indeed be an idea to disable both by default and let the user choose.

I agree that your quickstart would get people up and running quickly - if they are starting from scratch.
My project began using a different component library, and when it got in my way I swapped it out for yours. However, I was using yew-router and had plenty of routes defined. I had to then try to convert my yew-router implementation to match yew-nested-router. I abandoned the attempt, but luckily found that I could opt-out.
I anticipate that others will approach the project this way; they'll have existing yew projects, which means yew-router implementations, for better or worse.
If we are to improve onboarding for yew-router users, I think we'd need to write a guide specifically targeting the topic of converting a project to yew-nested-router from yew-router. With before/after snippets, explanatory text, and finally some motivating examples that demonstrate why it was worth it (i.e.: nesting). I think a blog-post style would work well.
I'd be happy to contribute to this documentation with writing, editing, and testing, though you're probably the one that would have to get it started, as you understand both routers better than anyone.

Fair arguments. And as I said, I would definitely welcome an additional router implementation. I just don't have the need or time to do this. This would need to come as a contribution.
And if that's the case, I am also fine to make both routers opt-in. Just to make it easier to let the user choose.
I am also ok with starting to write some kind of blog post/documentation as you suggested. That might be a good idea anyway. I will put it on my "to do" pile :)

Btw, not sure you know, but there's a also a Matrix channel: https://matrix.to/#/#patternfly-yew:matrix.org … might be quicker for some chats.


Root level packages show up as "DynamicTypeBrowseObject" in the object browser

Usually these have friendly names, such as Package or Dependency. If you choose the child, you get:

Dupe of https://github.com/dotnet/roslyn-project-system/issues/1258


refactor(delete-user-data) move package.json into functions dir

Checks

[x]  move package.json into functions dir
[x]  change paths of scripts & imports in package.json
[x]  change package.json name to be of the format: ${extensionName}-functions
[x]  remove** the sourceDirectory field from the extension yaml
[x]  move jest.config.js into functions dir
[x]  move jest.setup.js into functions dir (if applicable)
[x]  move jest.teardown.js into functions dir (if applicable)
[x]  move tsconfig.json into functions dir
[x]  ensure compiling on lerna rebuild
[x]  updated contributions
[x] move tests into functions folder (if applicable)
[x]  add functions project to lerna.json
[x]  generate readme move up a directory with ..
[x]  update test to jest in package json (if tests exist)

Testing
Extension successfully deploys and successfully delete user data

Codecov Report

Merging #312 into next will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next     #312   +/-   ##
=======================================
  Coverage   40.09%   40.09%
=======================================
  Files          20       20
  Lines         631      631
  Branches       83       83
=======================================
  Hits          253      253
  Misses        376      376
  Partials        2        2


Turbo 8 Beta 1: Button with formmethod="patch" sends form method in lower case

When using formmethod="patch" on a button in Turbo 7.3.0 the form was sent with method in upper case. In Turbo 8 Beta 1 the method is sent in lower case. Is this a regression?
Example
<html>
  <head>
    <script type="module">
      import * as Turbo from 'https://unpkg.com/<EMAIL_ADDRESS>      //import * as Turbo from 'https://unpkg.com/<EMAIL_ADDRESS>    </script>
  </head>

  <body>
    <turbo-frame id="form">
      <form action="">
        <input type="submit">

        <button type="submit" formmethod="patch">Patch</button>
      </form>
    </turbo-frame>
  </body>
</html>

Turbo 7.3.0

Turbo 8 Beta 1

Chrome (Mac)
Version 119.0.6045.199 (Official Build) (arm64)

Yea this is resulting in 400 requests for me

Same issue for links with data-turbo-method="patch".

If you're using Rails resource routing (where PATCH and PUT are mapped to the same controller action) you can substitute with data-turbo-method="put" as it still works.

I can confirm this issue.


port-install(1): remove stray backslash

Unfortunately due to how our documentation build system works, we are not rebuilding the generated manpages on users' machines (because they lack the required dependencies) and the regeneration thus needs to be in a separate and newer commit.
I've done that now and will merge as soon as the CI build is finished.


Bump automl runtime version for release

Codecov Report
Base: 95.35% // Head: 95.35% // No change to project coverage :thumbsup:

Coverage data is based on head (fc91c06) compared to base (b864509).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   95.35%   95.35%
=======================================
  Files          26       26
  Lines         904      904
=======================================
  Hits          862      862
  Misses         42       42

Flag
Coverage Δ

unittests
95.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


issue on installation magnum plugins with makefile

when i try to run this cmake -DCMAKE_BUILD_TYPE=Release -DWITH_ASSIMPIMPORTER=ON -DWITH_DDSIMPORTER=ON -DWITH_JPEGIMPORTER=ON -DWITH_OPENGEXIMPORTER=ON -DWITH_PNGIMPORTER=ON -DWITH_TINYGLTFIMPORTER=ON -DWITH_STBTRUETYPEFONT=ON .. # this will enable quite a few Magnum Plugins that are not necessarily needed for robot_dart (please refer to the documentation of Magnum for more details on selecting only the ones that you need) i get this kind of error
CMake Error at /usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)

You haven't installed all the Magnum dependencies. Please check here for the needed packages.

Thank you for the answer, these i have to download manually


chore(frontend): Change bullet point in header when logged out

Motivation
Re-wording one of the bullet points, since OISY will be indeed network-controlled.

@peterpeterparker good catch! I will change the README file in this one (the modals are being worked on exactly with that scope)
please re-review


Redirect after payment points to localhost:8000

After successfully paying for an order via. Stripe, I'm redirected to http://localhost:8000/order/9306ae71-45c1-44b4-8a03-759ffa38cd17/create-password/, instead of the hosted URL.
I'm not sure why this occurs? This is after deployment to Heroku.

Perhaps the Site instance referenced by your settings file points to that domain?

In /saleor/settings.py? I cannot find any references to localhost or <IP_ADDRESS>. May you provide an example of where this might be?

Please see the Django documentation. This change has to be done in the database and you'll need to restart the application as there's currently no way to modify the site programmatically (there's a bug in how they are cached by Django).

@mikeres0 Go to Dashboard -> Scroll down sidebar -> Settings and edit the “Domain” value.

@joshkehn Thank you. I hadn't delved into the site settings just yet, but thanks for pointing that out.


Fix json switch on export command

This fixes broken implementation of the recently added --json switch. Prior to this commit it only would have worked if --output-format json were simultaneously supplied.

rebranched https://github.com/foxglove/foxglove-cli/pull/132


Is this diagram correct?

The diagram is described currently as
The Flutter framework is organized into a series of layers, with each layer building upon the previous layer.
However shouldn't the following diagram have Mater and Cupertino on the same level? Rather than Material building off Cupertino?

The diagram is correct.  Material re-uses some Cupertino widgets to implement https://material.io/guidelines/platforms/platform-adaptation.html
It's confusing enough that we should probably remove the diagram.

(There's another bug on file somewhere for removing the diagram.)

Ah okay thanks!

I'd love to make material and cupertino as peers. I think there's value in the diagram, it shows the many capabilities of the system.
@abarth are you comfortable if we make this a "logical diagram" and thus put cupertino and material as peers?


The generator does not generate train images just test !!

I tried several times to repeat the code but when i run >> 2) Data generation:
it Generating testing data successfully but failed to do so for training ?? any help ??

https://github.com/strvcom/strv-ml-mask2face/issues/1#issuecomment-973081302

Me too... Up please

Guys please in configuration.json
change "train_image_count": 13233 from 15000


Ratio Calculator

Create a Ratio Calculator in html,css and javascript.

Add navbar in your tool's html file. You can copy the navbar from index.html.
Add screenshot of your tool in, PR message and also in the folder of your tool
Before Making the PR Pull the latest changes that have been made to the repository

**Note: Please Don't Make Any Changes In index.html AND contributors.html **
**Note: Only make changes to the folder that you have created for your tool/utility **
Add the below mention section to your PR message
Title
Number of files/folder added
changes made
check the options that you have completed,
I have;

[ ] Read contibuting.md
[ ] Followed all the guidelines
[ ] Followed the directory Structure
[ ] updated readme.md
[ ] add your name in the footer of your tool.html file (if you created length conversion tool then add your name to length.html file you created)
[ ] provide below mentioned details if you want your name to be added in contributors.html
[ ] mail, twitter, github profile link.

Hi @shubham2704 I would like to work on this. Please assign this to me.

@shubham2704 I have created below PR to resolve this issue. Please check.
https://github.com/codeezzi/utility/pull/104


Incompatible LTO version of liblt_9518_zephyr.a

Target: TLSR9518ADK80D
Zephyr versions:  v3.2.0, main.
Host OS: Ubuntu 22.04
lto1: fatal error: bytecode stream in file '/workdir/modules/hal/telink/tlsr9/ble/proj_lib/lib/liblt_9518_zephyr.a' generated with LTO version 9.3 instead of the expected 12.0
compilation terminated.
lto-wrapper: fatal error: /home/egor/.local/zephyr-sdk-0.15.1/riscv64-zephyr-elf/bin/riscv64-zephyr-elf-gcc returned 1 exit status
compilation terminated.
/home/egor/.local/zephyr-sdk-0.15.1/riscv64-zephyr-elf/bin/../lib/gcc/riscv64-zephyr-elf/12.1.0/../../../../riscv64-zephyr-elf/bin/ld.bfd: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

Reproduce:
add CONFIG_FPU=y to zephyr/boards/riscv/tlsr9518adk80d/tlsr9518adk80d_defconfig
west build -p -b tlsr9518adk80d ../zephyr/samples/bluetooth/peripheral

Expected: successful build

@carlescufi Query on this, the command above seems to imply that a closed source blob is being included in a hal repo - see https://github.com/zephyrproject-rtos/hal_telink/tree/main/tlsr9/ble/proj_lib
I was under the impression that blobs had to be fetched using west blobs and could not be included in the default zephyr instance?

@andy-liu-telink Could you please fix it? I would like to use main Zephyr repo instead of Telink fork

@AlexKolosovTelink are you be able to help out here? If this is not fixed I think we'll have to remove B91 Bluetooth support from Zephyr.

I've opened a pull request to remove the HCI driver, since it turns out it doesn't build even with the binary blob made manually available: #73289

@jhedberg
I have notified the proper team members to look into this issue.
@s07641069
@andriy-bilynskyy
Could you take a look?

Since HCI driver is no longer available #73289 the initial issue is no longer valid

Since HCI driver is no longer available #73289 the initial issue is no longer valid

That PR hasn't been merged yet, but from the responses I'd conclude that there are no objections to proceeding with the removal of the HCI driver.


ssr not working with webpack 4.0.0-beta1

export const Layout = loadable( () => import( / webpackChunkName: "main.layout" / './components/layouts/container.mjs' ) )
first error:
loadable-components: modules entry is missing, your are probably missing loadable-components/babel
then I set in webpack server config:
module: {
    rules: [
      {
        test: /\.(js|mjs)$/,
        use: [
          {
            loader: 'babel-loader',
            options: { plugins: [  'loadable-components/babel', 'dynamic-import-node' ] }
          }
        ],
        exclude: /node_modules/
      }
    ]
  },

then another error:
Error: Cannot find module './components/layouts/container.mjs'
"devDependencies": {
    "babel-core": "^6.26.0",
    "babel-loader": "^7.1.2",
    "babel-plugin-dynamic-import-node": "^1.2.0",
    "webpack": "^4.0.0-beta.1",
    "webpack-cli": "^2.0.4",
    "webpack-node-externals": "^1.6.0"
  },
"dependencies": {
    "loadable-components": "^1.1.1",
    "prop-types": "^15.6.0",
    "react": "^16.2.0",
    "react-dom": "^16.2.0",
    "react-redux": "^5.0.6",
    "redux": "^4.0.0-beta.1",
    "styled-components": "^3.1.6"
  }

but all works with webpack 3.10.0

I haven't tested Webpack 4 yet. Thanks for reporting!

I tested it with Webpack 4 and it works, anyway it still in beta and loadable-components is not Webpack dependent so it should not be impacted. I hope your issue will be solved soon.

the problem appears when I use files with .mjs extensions ( webpack 4 parse them in a special way )
file c1.js
import { Component, createElement } from 'react'
export default props => createElement( 'p', {}, 'hello' )

file main.js
import { createElement } from 'react'
import loadable from 'loadable-components'
import { getLoadableState } from 'loadable-components/server'

const View = loadable( () => import( /* webpackChunkName: "main.view" */ './c1.js' ) )

const main = async () => {
  try {
    const loadableState = await getLoadableState( createElement( View ) )
    console.log( loadableState )

  } catch ( error ) {
    console.error( error )

  }
}

main()

file main.mjs
import * as React from 'react'
const createElement = React.default.createElement

import * as LoadableComponents from 'loadable-components'
const loadable = LoadableComponents.default.default

import * as LoadableComponentsServer from 'loadable-components/server'
const getLoadableState = LoadableComponentsServer.default.getLoadableState

const View = loadable( () => import( /* webpackChunkName: "main.view" */ './c1.js' ) )

const main = async () => {
  try {
    const loadableState = await getLoadableState( createElement( View ) )
    console.log( loadableState )

  } catch ( error ) {
    console.error( error )

  }
}

main()

which gives me
{ Error: loadable-components: modules entry is missing, your are probably missing `loadable-components/babel`
    at /Users/artemxgruden/projectsm2/node-views-provider-template/node_modules/loadable-components/dist/loadable-components.server.cjs.js:153:17
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
    at Function.Module.runMain (module.js:703:11)
    at startup (bootstrap_node.js:190:16)
    at bootstrap_node.js:662:3 queryErrors: [ [Circular] ] }

my webpack 4 configuration for server:
const nodeExternals = require( 'webpack-node-externals' )

module.exports = ( { NODE_ENV, PORT, VIEW_TYPE, DATA_PROVIDER }, webpack, joinPath ) => ( {
  target: 'node',
  externals: [ nodeExternals() ],
  node: {
    __dirname: true
  },
  entry: {
    main: joinPath( `./unbundled/server/main.mjs` ),
    // main: joinPath( `./unbundled/server/main.js` ),
  },
  output: {
    path: joinPath( `./bundled/server/` ),
    filename: '[name].js',
  },
  resolve: {
    modules: [
      'node_modules',
      joinPath( './unbundled/' ),
    ],
    extensions: [ '.mjs', '.js', '.json' ],
  },
  devtool: 'source-map',
  optimization: {
    splitChunks: {
      chunks: 'all'
    }
  },
  plugins: [
    new webpack.DefinePlugin( {
      'process.env': {
        'NODE_ENV': JSON.stringify( NODE_ENV ),
        'PORT': JSON.stringify( PORT ),
        'RUNNING_ENV': JSON.stringify( 'SERVER' ),
        'DATA_PROVIDER': JSON.stringify( DATA_PROVIDER ),
        'VIEW_TYPE': JSON.stringify( VIEW_TYPE )
      }
    } ),
  ],

  module: {
    rules: [
      {
        test: /\.(js|mjs)$/,
        use: [
          {
            loader: 'babel-loader',
            options: { plugins: [  'loadable-components/babel' ] }
          }
        ],
      }
    ]
  },
} )

@neoziro Hello!
Do you have any news?

@artemxgruden no, I am sorry I don't see what could be the problem.

Here's a link to a test project - https://github.com/gcardella/react-universal so you can understand the problem better.
src/server/render.js has the call to ${loadableState.getScriptTag()}
See comments in the webpack.server.config.js. I am not able to load components using ssr due to the error below:
Error on server:
 Error: Cannot find module "function (){return t("../home/Home")}".
0|server   |     at n (/Users/gcardella/Documents/projects/joe-website/dist/0.server.js:1:132)
0|server   |     at /Users/gcardella/Documents/projects/joe-website/dist/server.js:1:5008
0|server   |     at <anonymous>

webpack.server.config.js:
const nodeExternals = require('webpack-node-externals');
const path = require('path');

const srcPath = path.resolve(__dirname, 'src');
const distPath = path.resolve(__dirname, 'dist');

module.exports = {
  context: srcPath,
  entry: './server/index.js',
  output: {
    path: distPath,
    filename: 'server.js',
    publicPath: '/assets/'
  },
  target: 'node',
  node: {
    __dirname: false,
    __filename: false,
  },
  resolve: {
    modules: ['node_modules', 'src'],
    extensions: ['*', '.js', '.json']
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /(node_modules)/,
        loader: 'babel-loader',
        options: {
          presets: [
            ['env', {
              targets: {
                node: 8
              }
            }]
          ],
          /*  if I remove 'babel-plugin-dynamic-import-node', the page loads, the ssr code is there in view source, but I get an error in the client console: Uncaught Error: loadable-components state not found. You have a problem server-side. Please verify that you have called `loadableState.getScriptTag()` server-side. */
/* If I leave the babel-plugin-dynamic-import-node, the no pages load because of a server error:
   Error: Cannot find module "function (){return t("../home/Home")}".  --- the contents of t("..") are the current route.
*/
          plugins: [ 'loadable-components/babel', 'babel-plugin-dynamic-import-node' ]
        }
      },
      // ...
    ]
  },
  externals: nodeExternals()
};

@neoziro thank you, I have no problems with node 9.8.0, since node 9.6.0 has support dynamic import feature
module versions:
"webpack": "^4.1.1",
"webpack-cli": "^2.0.12",
"loadable-components": "^1.1.1",
I have no webpack configuration for server, only for client
and for client I have no babel-loader in module section of webpack configuration
javascript``` module: {
rules: [
{
test: /.(js|mjs)$/,
use: [
{
loader: 'babel-loader',
options: { plugins: [  'loadable-components/babel' ] }
}
],
}
]
},

I have node -v 9.9.0 ... I don't think the problem is with loadable-components. I think the problem is with babel-plugin-dynamic-import-node not being webpack 4 ready? If I rollback webpack to ver 3.x, everything works without errors.

babel-plugin-dynamic-import-node should not be used with Webpack.
For Webpack: only loadable-components/babel.
For Node: loadable-components/babel + babel-plugin-dynamic-import-node

hi @neoziro still not working when get ssr markup from node without webpack bundling
node version 9.10
loadable-components versions 1.1.1
c1.mjs
export default props => createElement( 'p', {}, 'hello' )

main.mjs
import * as React from 'react'
const createElement = React.default.createElement
const Component = React.default.Component

import * as ReactDOMServer from 'react-dom/server'
const renderToNodeStream = ReactDOMServer.default.renderToNodeStream
const renderToString = ReactDOMServer.default.renderToString
const renderToStaticMarkup = ReactDOMServer.default.renderToStaticMarkup
import * as LoadableComponentsServer from 'loadable-components/server'
const getLoadableState = LoadableComponentsServer.default.getLoadableState

import * as LoadableComponents from 'loadable-components'
const loadable = LoadableComponents.default.default

const c1 = loadable( () => import( /* webpackChunkName: "c1" */ './c1.mjs' ) )

console.info( c1 )
console.info( 'markup', renderToStaticMarkup( createElement( c1 ) ) )

markup is empty string

@neoziro thank you, my mistake
main.mjs now
import * as React from 'react'
const createElement = React.default.createElement
const Component = React.default.Component

import * as ReactDOMServer from 'react-dom/server'
const renderToNodeStream = ReactDOMServer.default.renderToNodeStream
const renderToString = ReactDOMServer.default.renderToString
const renderToStaticMarkup = ReactDOMServer.default.renderToStaticMarkup
import * as LoadableComponentsServer from 'loadable-components/server'
const getLoadableState = LoadableComponentsServer.default.getLoadableState

import * as LoadableComponents from 'loadable-components'
const loadable = LoadableComponents.default.default

const c1l = loadable( () => import( /* webpackChunkName: "c1" */ './c1.mjs' ), {
  modules: [ './c1.mjs' ],
} )

const main = async () => {
  const composition = createElement( c1l )
  getLoadableState( composition ).then( app => {
    console.info( 'markup', renderToString( composition ) )
  } ).catch( e => {
    console.log( e )
  } )

}

main()

webpack 4 config for node server
const nodeExternals = require( 'webpack-node-externals' )

module.exports = ( { NODE_ENV, PORT, VIEW_TYPE, MACHINE }, webpack, joinPath ) => ( {
  target: 'node',
  externals: [ nodeExternals( {
    whitelist: [

    ],
  } ) ],
  node: {
    __dirname: true
  },
  entry: {
    main: joinPath( `./unbundled/server/main.mjs` ),
  },
  output: {
    path: joinPath( `./bundled/server/` ),
    filename: '[name].js',
  },
  resolve: {
    modules: [
      'node_modules',
      joinPath( './unbundled/' )
    ],
    extensions: [ '.mjs', '.js', '.json' ],
  },
  devtool: 'source-map',
  optimization: {
    splitChunks: {
      chunks: 'all'
    }
  },
  plugins: [
    new webpack.DefinePlugin( {
      'process.env': {
        'NODE_ENV': JSON.stringify( NODE_ENV ),
        'PORT': JSON.stringify( PORT ),
        'RUNNING_ENV': JSON.stringify( 'SERVER' ),
        'MACHINE': JSON.stringify( MACHINE ),
        'VIEW_TYPE': JSON.stringify( VIEW_TYPE )
      }
    } ),
  ],

  module: {
    rules: [
      {
        test: /\.(js|mjs)$/,
        use: [
          {
            loader: 'babel-loader',
            options: { plugins: [ 'loadable-components/babel' ] },
          }
        ],
      }
    ]
  },

} )

"webpack": "^4.2.0",
"webpack-cli": "^2.0.13",
"babel-core": "^6.26.0",
"babel-loader": "^7.1.4"

@neoziro but I have error when running main.mjs without webpack bundling
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.
    in LoadableComponent
{ Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
    at invariant (/Users/artemxgruden/projectsm/cvz-nvp/node_modules/fbjs/lib/invariant.js:42:15)
    at ReactDOMServerRenderer.render (/Users/artemxgruden/projectsm/cvz-nvp/node_modules/react-dom/cjs/react-dom-server.node.development.js:2482:7)
    at ReactDOMServerRenderer.read (/Users/artemxgruden/projectsm/cvz-nvp/node_modules/react-dom/cjs/react-dom-server.node.development.js:2312:19)
    at renderToString (/Users/artemxgruden/projectsm/cvz-nvp/node_modules/react-dom/cjs/react-dom-server.node.development.js:2684:25)
    at getLoadableState.then.app (file:///Users/artemxgruden/projectsm/cvz-nvp/functions/unbundled/server/main.mjs:25:29)
    at <anonymous> name: 'Invariant Violation', framesToPop: 1 }

@neoziro Please add support for new getDerivedStateFromProps react 16.3 method
https://reactjs.org/docs/react-component.html#static-getderivedstatefromprops

@neoziro Please up static methods of wrapped components.
I have my own lib, and I added such fix especially for using with loadable-components:
c - ƒ LoadableComponent()
if ( c && c.Component && c.Component && c.Component.preloadDataState && Object.prototype.toString.call( c.Component.preloadDataState === '[object AsyncFunction]' ){
...
}

@artemxgruden I do not understand the last one. Can you describe it completely in a different issue?

@neoziro https://github.com/smooth-code/loadable-components/issues/58


Solitude clockwork terminus

What happened?
missing wall
Modlist version
1.1.693

wall was rotated, reverted and fixed

fixed in 1.1.694


Gather block stats

The mozilla schema has two fields I don't think we have the data for yet:

largest_free_vm_block
tiny_block_size
write_combine_size

Haven't yet looked into where in the minidump file they come from.

That info gets populated here, from the memory info list stream, which we don't currently support reading (#21).

It's not really useful info, is it? I think I never looked at those fields in all these years.

bsmedberg added it ages ago when we were having lots of issues with OOM crashes (before we had e10s) and we were getting malformed or empty minidumps because we didn't have enough memory left to write the dump. I suspect that's no longer useful. Also, at some point we started submitting memory reports alongside the dump in low-memory scenarios, which is likely to be way more actionable.

I'm gonna say we're not gonna bother with this one. It relies on the extra json and isn't really useful anymore.


I created Ollama - Open WebUI Script - Give it a try!

I created "Ollama-Open-WebUI-Script" for those who, like me, prefer not to overload their PC at startup with too many resources. Instead of manually starting Docker, then Ollama, and finally Open WebUI, this script simplifies the entire process, giving you direct and easy access to these two fantastic projects.
Give it a try here https://github.com/Special-Niewbie/Ollama-Open-WebUI-Script, and enjoy a smoother experience with Ollama and Open WebUI!

This is cool, thank you for sharing it!


Riderlink cannot be installed into 5.3 UE project

This is super barebones and easy to reproduce:

Create new FPS template, C++ project in UE 5.3
Open the project in rider.
When prompted by Rider to add Riderlink, select Add to Editor.
Process begins, gets almost to 79/79, then fails at the very end. Every time no matter what I do.

As you can see there's pretty much no room for me to configure or do anything differently here. I'm guessing that Riderlink simply isn't updated for 5.3 yet, which is only a week old from what I can tell.
Here is what it says at the end of the build script terminal output:
BUILD FAILED
Failed to build RiderLink plugin for G:\UE_5.3
Failed to build RiderLink plugin

Just above that it gives a path to a log file. The log file is attached in full below, but I scanned it for pertinent details and I think this is the key error:
C:\Users\neuro\AppData\Local\Temp\UnrealLink\Coqelaz\HostProject\Plugins\RiderLink\Source\RiderGameControl\Private\RiderGameControl.cpp(20): fatal error C1083: Cannot open include file: 'UnrealEd/Public/Editor.h': No such file or directory

However, that file DOES seem to exist. I can locate it in rider, it is in "G:\UE_5.3\Engine\Source\Editor\UnrealEd\Public\Editor.h"
Any ideas?
UBT-UnrealEditor-Win64-Development.txt

To clarify I have tried everything short of using a different editor version. Reboots, reinstalls, nothing seems to solve this problem.

I neglected to mention Rider version. There's some other info in here too, maybe it's useful 🤷♂
JetBrains Rider 2022.3.2
Build #RD-223.8617.53, built on January 25, 2023
Licensed to ***
You have a perpetual fallback license for this version.
Subscription is active until ***
Runtime version: 17.0.5+1-b653.25 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
.NET 7.0.0 (Server GC)
GC: G1 Young Generation, G1 Old Generation
Memory: 1500M
Cores: 16
Registry:
ide.mac.bigsur.window.with.tabs.enabled=false
debugger.show.values.use.inlays=false
ide.new.project.model.index.case.sensitivity=true
platform.projectModel.workspace.model.file.index=false
ide.workspace.model.rbs.as.tree=false
rdclient.asyncActions=false
vcs.empty.toolwindow.show=false
indexing.enable.entity.provider.based.indexing=false
database.show.search.tab=false
Non-Bundled Plugins:
com.markskelton.one-dark-theme (5.7.3)
com.jetbrains.fast.mouse.scroll (1.6.0)
com.microsoft.vso.idea (1.162.1)

Pack it up, boys!

BUILD SUCCESSFUL

Rider 2023.2.1 worked fine.

Pack it up, boys!

BUILD SUCCESSFUL

Rider 2023.2.1 worked fine.

Hi, I'm having the same issue that you had, I'm working with Rider 2022.2.4 and I can't install RiderLink.
I tried to switch to Rider 2023.2.1 and now I can't open the project at all.
If I'm trying to open any C++ file through Unreal, I get this message: "No project was found to open the file in".
I also tried to switch to Rider 2023.2.0 or Rider 2023.2.2, but I got the same results.
Any advice?

I have the same problem，my rider version is 2022.3.3，how can i do without update rider?

Try
Ctrh+Shift+A
Extract RiderLink
Swap RD folder of RiderLink with https://github.com/JetBrains/UnrealLink/tree/0a24d30f1af7ff79672a6a5cf968740cc2a57a23/src/cpp/RiderLink/Source/RD

Try Ctrh+Shift+A Extract RiderLink Swap RD folder of RiderLink with https://github.com/JetBrains/UnrealLink/tree/0a24d30f1af7ff79672a6a5cf968740cc2a57a23/src/cpp/RiderLink/Source/RD

Tried it with JetBrains Rider 2022.2.4, it doesn't work
Do we need to patch different source files ?

Try Ctrh+Shift+A Extract RiderLink Swap RD folder of RiderLink with https://github.com/JetBrains/UnrealLink/tree/0a24d30f1af7ff79672a6a5cf968740cc2a57a23/src/cpp/RiderLink/Source/RD

It actually worked. Thanks

Try Ctrh+Shift+A Extract RiderLink Swap RD folder of RiderLink with https://github.com/JetBrains/UnrealLink/tree/0a24d30f1af7ff79672a6a5cf968740cc2a57a23/src/cpp/RiderLink/Source/RD

what is Ctlr+Shift+A actually do? where should I do the Ctrl+Shift+A ???

Try Ctrh+Shift+A Extract RiderLink Swap RD folder of RiderLink with https://github.com/JetBrains/UnrealLink/tree/0a24d30f1af7ff79672a6a5cf968740cc2a57a23/src/cpp/RiderLink/Source/RD

I did not understand where i've to insert the github link :(

same issue, UE 5.4.4 and Rider 2024.2.4


Adjusting the ASTM E 1049-85 Python Rainflow to 4 point

Python uses ASTM E 1049-85 3 Point Rainflow Count while glyphworks uses the 4 point method, Is there a way to adjust the 3 Point to 4 Point in Python?
Is there a 4 Point Rainflow code in Python?

This project offers a python package with ASTM E 1049 (2011) 4 point method now.


Added a not to have (attribute|attributes) assertion.

This is useful to testing that a button is not disabled.
expect(button, 'not to have attribute', 'disabled')

@papandreou except the failing linting :-S I'm creating a prettier branch, I can't code without it :-)

Coverage increased (+0.09%) to 93.75% when pulling 401663c278e64081bb5ddfc6c6ca678c1327b7b2 on ssimonsen/not-to-have-attributes into 56e455771956823f930c70eb67d33f3929bd850b on master.


Fix faiss arm compile error in partitioning.cpp

issue #232
/kind bug

@chasingegg Tbh I'm not sure what exactly this PR fixes, at least from the description and the ref to an issue. Could you please provide more details?

@chasingegg Tbh I'm not sure what exactly this PR fixes, at least from the description and the ref to an issue. Could you please provide more details?

We have move simd related code to new file partitioning_avx2.cpp(maybe a better name..), non-simd related code is only used for x86 sse, so the header is proteced by a marco ifdef __AVX2__. There are many ways to fix the issue, I try to make the code stay the same with its original version before upgraing faiss, just exclude arm marco and use partitioning_avx2.cpp's implementation for arm arch.


[Technical Task] Investigate how to generate recaptcha token

Brief overview
Recaptcha was added to the auth endpoint and without it, it's impossible to authorize in the swagger and postman.
Expected result
There is an endpoint that will return valid recaptcha token.

In fact, it's a violation of reCaptcha Terms Policy, so it was decided to create a video with explenations of where to get captcha token


Added a new remove unofficial docker step

I found an error when trying to install the official docker-engine, as there a second package that conflicts with the new package.  Added instructions on how to remove it.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

These look great, if you add Fedora, it will be good to go. Don't forget, that Fedora uses dnf instead of yum.


Electron 9.4.1

Electron ~9.4.0~ 9.4.1 is more recent stable than 9.3.5

@sadick254 Should be trivial

Is there any macos build for this branch to test it out?

@asturur I can make one. Are you on a specific OS (Linux, macOS, Windows)? There have been some build problems affecting some OSes with the Electron 9 upgrade at the moment, and the upgrade isn't finished yet, but there are workarounds, so I think I could build for any OS.

@asturur I can make one. Are you on a specific OS (Linux, macOS, Windows)? There have been some build problems affecting some OSes with the Electron 9 upgrade at the moment, and the upgrade isn't finished yet, but there are workarounds, so I think I could build for any OS.

i m on macos 10.15.7, or if there is a consistent way to build i m fine building it.
I just did non want to mess up with brew too much since i m worried to messup some libraries as i did in the past

i m on macos 10.15.7, or if there is a consistent way to build i m fine building it.
I just did non want to mess up with brew too much since i m worried to messup some libraries as i did in the past

Here is a build I did in my fork's CI: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=959&view=artifacts&pathAsName=false&type=publishedArtifacts
Direct download link: https://dev.azure.com/DeeDeeG/_apis/resources/Containers/11598672/atom-mac.zip?itemPath=atom-mac.zip%2Fatom-mac.zip

Here is a build I did in my fork's CI: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=959&view=artifacts&pathAsName=false&type=publishedArtifacts
Direct download link: https://dev.azure.com/DeeDeeG/_apis/resources/Containers/11598672/atom-mac.zip?itemPath=atom-mac.zip%2Fatom-mac.zip

Thank you it works great, feels smoother than the latest nightly.
I know is probably a placebo effect :)

Thank you it works great, feels smoother than the latest nightly.
I know is probably a placebo effect :)

When is this going to be merged?

When is this going to be merged?

So, just to be clear, this is to bump the "Electron 9" effort up from 9.3.5 to 9.4.x
The main thing blocked is getting the app fully working and tests passing on Electron 9, generally speaking. I suppose it wouldn't hurt to merge this to the Electron 9 PR, with the understanding that there is still work to do for Electron 9 more generally.

So, just to be clear, this is to bump the "Electron 9" effort up from 9.3.5 to 9.4.x
The main thing blocked is getting the app fully working and tests passing on Electron 9, generally speaking. I suppose it wouldn't hurt to merge this to the Electron 9 PR, with the understanding that there is still work to do for Electron 9 more generally.

just to add my 2 cents, i tried the build more and i realized sometimes it was impossible to quit or start new windows  or add project folders.
Now this could also be caused by my addons setup not ready for electron 9.
Not blaming anynone, just saying it wasn't as smooth as it seemed first 2 days.

just to add my 2 cents, i tried the build more and i realized sometimes it was impossible to quit or start new windows  or add project folders.
Now this could also be caused by my addons setup not ready for electron 9.
Not blaming anynone, just saying it wasn't as smooth as it seemed first 2 days.

Hi @asturur, I think that was fixed in https://github.com/atom/atom/pull/21847 but it didn't make its way to the Electron 9 branches yet.
Not sure if others see this, but opening project folders and files wasn't working very well for me on the Electron 9 branch last time I tried it.

Hi @asturur, I think that was fixed in https://github.com/atom/atom/pull/21847 but it didn't make its way to the Electron 9 branches yet.
Not sure if others see this, but opening project folders and files wasn't working very well for me on the Electron 9 branch last time I tried it.

I can confirm that opening projects/files is still buggy on the electron 9 branch.

I can confirm that opening projects/files is still buggy on the electron 9 branch.

Thanks for merging.
I tried opening projects and files but have not experienced those problems, using the build from https://github.com/atom/atom/pull/21777/commits/a241462bbff56c344e0d3db2822c1080a3d1fb89

Thanks for merging.
I tried opening projects and files but have not experienced those problems, using the build from https://github.com/atom/atom/pull/21777/commits/a241462bbff56c344e0d3db2822c1080a3d1fb89

I tried opening projects and files but have not experienced those problems, using the build from a241462

@mfonville if you don't mind, what OS are you using? Is this Linux (Ubuntu)?

Yes, Ubuntu Linux 20.10
Though Atom had forgotten my recent project history when I switched back to the stable build (using the same atom configuration directory)


[Feature Request] Date to Append/Prepend

Hi Carlo,
It'd be great if the following could be implemented when appending/prepending into a note, e.g. syntax formatted date/time before/after text.
So: [date/time]: [TEXT] / [TEXT]:[date/time]
e.g. 20240329-1143: [TEXT]
Many thanks!

I try to keep the functionality as generic as possible, and that addition would be way too specific for my taste. For example, you might like it that way, but the next person would like another prefix or a different timestamp format or something.
It's simple enough to add that prefix/suffix to the content parameter yourself when calling the URI – so I won't add that feature, sorry.


Wagtail API not working for custom PagesAPIViewSet

I am on Wagtail version 6.1.3 and when I try accessing the api at http://localhost:8000/api/v2/offices/ I get a 0 items even though there is around 10 or so publish listings. And I tried testing out  if other models work but it is the same with every model all of them display 0 even though they have multiple listings. Could someone please help me with this issue
from django.core.validators import MaxValueValidator, MinValueValidator, EmailValidator
from django.db import models
from modelcluster.fields import ParentalKey
from wagtail.admin.panels import (
    FieldPanel,
    InlinePanel,
    MultipleChooserPanel,
    MultiFieldPanel,
    TitleFieldPanel,
)
from wagtail.api import APIField
from wagtail.blocks import RichTextBlock, StructBlock, CharBlock, BooleanBlock
from wagtail.fields import RichTextField, StreamField
from wagtail.images.blocks import ImageChooserBlock
from wagtail.models import Page, Orderable

class City(models.Model):
    """Model to store city details"""

    name = models.CharField(max_length=100, blank=False, null=False)
    state = models.CharField(max_length=100, blank=False, null=False)
    country = models.CharField(max_length=100, default="India")
    priority = models.IntegerField(
        default=0,
        help_text="Higher the number, higher the priority",
        blank=False,
        null=False,
    )

    def __str__(self):
        return self.name + ", " + self.state + ", " + self.country

    class Meta:
        verbose_name = "City"
        verbose_name_plural = "Cities"

class OfficesIndexPage(Page):
    subpage_types = ["offices.OfficePage"]
    max_count = 1

class ShowcaseImage(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="showcase_images"
    )
    image = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )

    panels = [
        FieldPanel("image"),
    ]
    api_fields = [
        APIField("image"),
    ]

class GalleryImage(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="gallery_images"
    )
    image = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )

    panels = [
        FieldPanel("image"),
    ]
    api_fields = [
        APIField("image"),
    ]

class AboutPoint(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="about_points"
    )
    point = models.TextField(blank=False, null=False)

    panels = [
        FieldPanel("point"),
    ]
    api_fields = [
        APIField("point"),
    ]

class AmenitiesPoint(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="amenities_points"
    )
    title = models.CharField(max_length=250, blank=False, null=False)
    icon = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )

    panels = [
        FieldPanel("title"),
        FieldPanel("icon"),
    ]

    api_fields = [
        APIField("title"),
        APIField("icon"),
    ]

class YoutubeVideo(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="youtube_videos"
    )
    youtube_url = models.TextField(blank=False, null=False)

    panels = [
        FieldPanel("youtube_url"),
    ]

    api_fields = [
        APIField("youtube_url"),
    ]

class NearbyPlaces(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="nearby_places"
    )
    title = models.CharField(max_length=250, blank=False, null=False)
    image = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )
    distance = models.CharField(
        max_length=250,
        blank=False,
        null=False,
        help_text="Make sure to include the unit as well (eg. 1.5 km or 100 meters)",
    )
    panels = [
        FieldPanel("title"),
        FieldPanel("image"),
        FieldPanel("distance"),
    ]

    api_fields = [
        APIField("title"),
        APIField("image"),
        APIField("distance"),
    ]

class LayoutBlock(StructBlock):
    """
    Custom block to hold image and rich text content
    """

    title = CharBlock(required=True, max_length=250)
    icon = ImageChooserBlock(required=True)
    content = RichTextBlock(required=True)

    class Meta:
        label = "Layout Item"

class FloorPlan(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="floor_plans"
    )
    title = models.CharField(
        max_length=250,
        blank=False,
        null=False,
        help_text="The name of the floor or floor "
        "number, preferabely in the format "
        "like this 'Floor 1' or 'Level 1' or 'Ground Floor'",
    )
    image = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )

    layout = StreamField(
        block_types=[
            ("layout_item", LayoutBlock()),
        ],
        blank=False,
    )

    panels = [
        FieldPanel("title"),
        FieldPanel("image"),
        FieldPanel("layout"),
    ]

    api_fields = [
        APIField("title"),
        APIField("image"),
        APIField("layout"),
    ]

class PricingPlans(Orderable):
    page = ParentalKey(
        "OfficePage", on_delete=models.CASCADE, related_name="pricing_plans"
    )
    title = models.CharField(max_length=250, blank=False, null=False)
    icon = models.ForeignKey(
        "wagtailimages.Image",
        on_delete=models.PROTECT,
        related_name="+",
        null=False,
        blank=False,
    )
    pricing_details = RichTextField(blank=False, null=False)

    panels = [
        FieldPanel("title"),
        FieldPanel("icon"),
        FieldPanel("pricing_details"),
    ]

    api_fields = [
        APIField("title"),
        APIField("icon"),
        APIField("pricing_details"),
    ]

class OfficePage(Page):
    """
    Model to store office details
    """

    name = models.CharField(max_length=250, blank=False, null=False)
    city = models.ForeignKey(City, on_delete=models.PROTECT, null=False, blank=False)
    area = models.TextField(
        blank=False, null=False, default="", help_text="Used to display in frontend"
    )
    address = models.TextField(blank=False, null=False)
    priority = models.IntegerField(
        default=0, help_text="Higher the number, higher the priority"
    )
    space_rating = models.IntegerField(
        default=0,
        help_text="The rating has to be between 0 and 5",
        validators=[MinValueValidator(0), MaxValueValidator(5)],
    )
    about_content = RichTextField(blank=False, null=False, default="")
    amenities_content = RichTextField(blank=True, null=True, default="")
    google_map_embed = models.TextField(
        blank=False,
        null=False,
        help_text="Google Maps embed data, you can get it "
        "byt clicking on the share button on the "
        "Google Maps listing and then selecting "
        "embed.",
        default="",
    )
    internal_email = models.EmailField(
        blank=False,
        null=False,
        help_text="This is used for internal communication, "
        "receiving emails from forms etc.",
        default="",
        validators=[EmailValidator()],
    )
    external_email = models.EmailField(
        blank=False,
        null=False,
        help_text="This is used for external communication, "
        "and is displayed in the website as your "
        "contact email address",
        default="",
        validators=[EmailValidator()],
    )
    phone_number = models.CharField(max_length=250, blank=False, null=False, default="")
    floor_plan_heading = models.TextField(blank=True, null=True)
    floor_plan_description = models.TextField(blank=True, null=True)
    pricing_heading = models.TextField(blank=False, null=False, default="")
    pricing_description = models.TextField(blank=False, null=False, default="")
    form_heading = models.TextField(blank=False, null=False, default="")
    form_description = models.TextField(blank=False, null=False, default="")
    is_managed_office_space = models.BooleanField(default=False)
    is_coworking_space = models.BooleanField(default=False)

    content_panels = [
        MultiFieldPanel(
            children=[
                TitleFieldPanel(
                    "title",
                    apply_if_live=True,
                    placeholder=False,
                ),
            ],
            heading="Office Name",
        ),
        FieldPanel("priority"),
        FieldPanel("space_rating"),
        FieldPanel("is_managed_office_space"),
        FieldPanel("is_coworking_space"),
        MultiFieldPanel(
            children=[
                FieldPanel("city"),
                FieldPanel("address"),
                FieldPanel("area"),
                FieldPanel("google_map_embed"),
                InlinePanel(
                    relation_name="nearby_places",
                    label="Nearby Places",
                    min_num=1,
                ),
            ],
            heading="Location Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("internal_email"),
                FieldPanel("external_email"),
                FieldPanel("phone_number"),
            ],
            heading="Contact Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("form_heading"),
                FieldPanel("form_description"),
            ],
            heading="Form Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                InlinePanel(
                    relation_name="showcase_images",
                    label="Showcase Images",
                    min_num=1,
                    max_num=3,
                    help_text="Add up to 3 showcase images, these images will be displayed on the top of the page as "
                    "hero images & slideshows everywhere else.",
                ),
                MultipleChooserPanel(
                    relation_name="gallery_images",
                    label="Gallery Images",
                    chooser_field_name="image",
                    help_text="These images are used to display in the office gallery section.(Make sure to have atleats 4 images)",
                    min_num=4,
                ),
                InlinePanel(
                    relation_name="youtube_videos",
                    label="Youtube Videos",
                    min_num=1,
                    help_text="Make sure that the url is valid and has the youtube video id in it.",
                ),
            ],
            heading="Gallery Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("about_content"),
                InlinePanel(
                    relation_name="about_points", label="About Points", min_num=1
                ),
            ],
            heading="About Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("amenities_content"),
                InlinePanel(
                    relation_name="amenities_points",
                    label="Amenities Points",
                    min_num=1,
                ),
            ],
            heading="Amenities Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("floor_plan_heading"),
                FieldPanel("floor_plan_description"),
                InlinePanel(
                    relation_name="floor_plans",
                    label="Floor Plans",
                ),
            ],
            heading="Floor Plans Section",
            classname="collapsed",
        ),
        MultiFieldPanel(
            children=[
                FieldPanel("pricing_heading"),
                FieldPanel("pricing_description"),
                InlinePanel(
                    relation_name="pricing_plans",
                    label="Pricing Points",
                    min_num=1,
                ),
            ],
            heading="Pricing Section",
            classname="collapsed",
        ),
    ]

    api_fields = [
        APIField("name"),
        APIField("priority"),
        APIField("space_rating"),
        APIField("is_managed_office_space"),
        APIField("is_coworking_space"),
        APIField("city"),
        APIField("area"),
        APIField("address"),
        APIField("google_map_embed"),
        APIField("nearby_places"),
        APIField("internal_email"),
        APIField("external_email"),
        APIField("phone_number"),
        APIField("showcase_images"),
        APIField("gallery_images"),
        APIField("youtube_videos"),
        APIField("about_content"),
        APIField("about_points"),
        APIField("amenities_content"),
        APIField("amenities_points"),
        APIField("floor_plan_heading"),
        APIField("floor_plan_description"),
        APIField("floor_plans"),
        APIField("pricing_heading"),
        APIField("pricing_description"),
        APIField("pricing_plans"),
        APIField("form_heading"),
        APIField("form_description"),
    ]

    class Meta:
        verbose_name = "Office Page"
        verbose_name_plural = "Offices Page"

    def __str__(self):
        return self.name

    # This is used to set the name of the office to the same as the title of the page
    def save(self, *args, **kwargs):
        self.name = self.title  # Synchronize the title with the name
        super().save(*args, **kwargs)

    parent_page_types = ["offices.OfficesIndexPage"]
    subpage_types = []

from wagtail.api.v2.views import PagesAPIViewSet
from wagtail.api.v2.router import WagtailAPIRouter
from wagtail.images.api.v2.views import ImagesAPIViewSet
from wagtail.documents.api.v2.views import DocumentsAPIViewSet
from offices.models import OfficePage

from wagtailmedia.api.views import MediaAPIViewSet

# Create the router. "wagtailapi" is the URL namespace
api_router = WagtailAPIRouter("wagtailapi")

# Add Office Api view
class OfficeAPIViewSet(PagesAPIViewSet):
    model = OfficePage

# Add the three endpoints using the "register_endpoint" method.
# The first parameter is the name of the endpoint (such as pages, images). This
# is used in the URL of the endpoint
# The second parameter is the endpoint class that handles the requests
api_router.register_endpoint("pages", PagesAPIViewSet)
api_router.register_endpoint("images", ImagesAPIViewSet)
api_router.register_endpoint("documents", DocumentsAPIViewSet)
api_router.register_endpoint("offices", OfficeAPIViewSet)
api_router.register_endpoint("media", MediaAPIViewSet)

I could get the data by manually setting the get_queryset funtion to return all the live data. But this wasn't required a day or two ago and this , I don't believe is the default behavior.
    def get_queryset(self):
        queryset = OfficePage.objects.live().public()
        return queryset

It seems in my haste in following someone else's code rather than the actual documentation. I inherited from PageApiViewSet rather than BaseAPIViewSet.

I'm unable to replicate this on a fresh Wagtail project using the code provided. I created an offices app and pasted this into models.py, along with an api.py in the project folder; after running the necessary migrations (and registering City as a snippet) I was then able to create an OfficePage, which showed at http://localhost:8000/api/v2/offices/ as expected.
If you're able to replicate this as a minimal example on a fresh Wagtail project, please open a new issue and I'll be happy to investigate further.

I'm unable to replicate this on a fresh Wagtail project using the code provided. I created an offices app and pasted this into models.py, along with an api.py in the project folder; after running the necessary migrations (and registering City as a snippet) I was then able to create an OfficePage, which showed at http://localhost:8000/api/v2/offices/ as expected.
If you're able to replicate this as a minimal example on a fresh Wagtail project, please open a new issue and I'll be happy to investigate further.

@gasman I did try it just now in a fresh install by just copying forward just the offices app, but it did not work no matter how much I tried, I had to manually override the get_queryset function. If you are open to it I can share the project with you, perhaps that would give  you a better insight


update async-profiler to 1.8.6

What does this PR do?

Checklist

[ ] This is an enhancement of existing features, or a new feature in existing plugins

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[ ] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[ ] This is something else

[ ] I have updated CHANGELOG.asciidoc

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Reason: Aborted from #2

Start Time: 2021-07-09T07:31:46.124+0000

Duration: 4 min 47 sec

Commit: 2af8a1cc82701a60bba1b5da905cc2912ecfb6d9

Trends :test_tube:

Log output
Expand to view the last 100 lines of log output

[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-log-shipper-plugin                              [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-micrometer-plugin                               [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-resttemplate                             [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-resttemplate-plugin                      [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-webflux                                  [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-webflux-testapp                          [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-reactor-plugin                                  [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-webflux-plugin                           [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-webmvc-plugin                            [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-urlconnection-plugin                            [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-scheduled-annotation-plugin                     [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-quartz-job-plugin                               [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-process-plugin                                  [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-dubbo-plugin                                    [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-scala-concurrent-plugin                         [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-struts-plugin                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-vertx                                           [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-vertx-common                                    [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-vertx3-plugin                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-vertx4-plugin                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-sparkjava-plugin                                [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-jdk-httpserver-plugin                           [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:elastic-apm-agent                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-agent-benchmarks                                [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-spring-resttemplate-test                        [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-logback-plugin-legacy-tests                     [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-es-restclient-plugin-7_x                        [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-jms-spring-plugin                               [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-jedis-2-tests                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-jedis-3-tests                                   [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-lettuce-3-tests                                 [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-grpc-test-1.6.1                                 [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-grpc-test-latest                                [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-rabbitmq-test-3                                 [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-rabbitmq-test-4                                 [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-okhttp-test                                     [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-vertx3-test-latest                              [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:apm-opentracing                                     [jar]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:integration-tests                                   [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:simple-webapp                                       [war]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:jsf-app                                             [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:jsf-app-dependent                                   [war]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:jsf-app-standalone                                  [war]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:cdi-app                                             [pom]
[2021-07-09T07:35:09.447Z] [INFO] co.elastic.apm:cdi-app-dependent                                   [war]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:cdi-app-standalone                                  [war]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:soap-test                                           [war]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:external-plugin-test                                [pom]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:plugin-instrumentation-target                       [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:external-plugin-app                                 [war]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:external-plugin                                     [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:apm-agent-attach                                    [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:apm-agent-attach-cli                                [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:application-server-integration-tests                [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-1-5                                     [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-2                                       [pom]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-2-base                                  [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-2-jetty                                 [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-2-tomcat                                [jar]
[2021-07-09T07:35:09.448Z] [INFO] co.elastic.apm:spring-boot-2-undertow                              [jar]
[2021-07-09T07:35:09.448Z] [INFO]
[2021-07-09T07:35:09.448Z] [INFO] ------------------< co.elastic.apm:apm-agent-parent >-------------------
[2021-07-09T07:35:09.448Z] [INFO] Building co.elastic.apm:apm-agent-parent 1.24.1-SNAPSHOT         [1/120]
[2021-07-09T07:35:09.448Z] [INFO] --------------------------------[ pom ]---------------------------------
[2021-07-09T07:35:16.026Z] [INFO]
[2021-07-09T07:35:16.026Z] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ apm-agent-parent ---
[2021-07-09T07:35:16.596Z] [INFO]
[2021-07-09T07:35:16.596Z] [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (enforce-java) @ apm-agent-parent ---
[2021-07-09T07:35:18.392Z] Sending interrupt signal to process
[2021-07-09T07:35:18.509Z] [INFO]
[2021-07-09T07:35:18.509Z] [INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ apm-agent-parent ---
[2021-07-09T07:35:18.778Z] script returned exit code 143
[2021-07-09T07:35:18.802Z] Sleeping for 10 sec
[2021-07-09T07:35:30.196Z] Stage "Tests" skipped due to earlier failure(s)
[2021-07-09T07:35:30.406Z] Stage "Unit Tests" skipped due to earlier failure(s)
[2021-07-09T07:35:30.422Z] Stage "Smoke Tests 01" skipped due to earlier failure(s)
[2021-07-09T07:35:30.436Z] Stage "Smoke Tests 02" skipped due to earlier failure(s)
[2021-07-09T07:35:30.450Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2021-07-09T07:35:30.464Z] Stage "Javadoc" skipped due to earlier failure(s)
[2021-07-09T07:35:30.652Z] Failed in branch Unit Tests
[2021-07-09T07:35:30.662Z] Failed in branch Smoke Tests 01
[2021-07-09T07:35:30.671Z] Failed in branch Smoke Tests 02
[2021-07-09T07:35:30.682Z] Failed in branch Benchmarks
[2021-07-09T07:35:30.691Z] Failed in branch Javadoc
[2021-07-09T07:35:30.984Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2021-07-09T07:35:31.086Z] Stage "Stable" skipped due to earlier failure(s)
[2021-07-09T07:35:31.187Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-07-09T07:35:31.229Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2021-07-09T07:35:32.068Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1907
[2021-07-09T07:35:32.392Z] [INFO] getVaultSecret: Getting secrets
[2021-07-09T07:35:32.441Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-07-09T07:35:33.391Z] Click here to forcibly terminate running steps
[2021-07-09T07:35:33.445Z] + chmod 755 generate-build-data.sh
[2021-07-09T07:35:33.445Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1907/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1907/runs/1 ABORTED 227047
[2021-07-09T07:35:33.445Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1907/runs/1/steps/?limit=10000 -o steps-info.json
[2021-07-09T07:35:33.695Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1907/runs/1/tests/?status=FAILED -o tests-errors.json
[2021-07-09T07:35:33.695Z] Retry 1/3 exited 22, retrying in 1 seconds...
[2021-07-09T07:35:35.039Z] Retry 2/3 exited 22, retrying in 2 seconds...
[2021-07-09T07:35:36.900Z] Retry 3/3 exited 22, no more retries left.
[2021-07-09T07:35:36.900Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1907/runs/1/log/ -o pipeline-log.txt


Bug: I cant able to load project

Still some issues in loading project. I cant load the project in OB 2.2.6

Can you show me your project file? the index.js in the pack.------------------ 原始邮件 ------------------
@.>
发送时间: 2021年9月8日(星期三) 中午12:43
@.>;
@.***>;
主题: [openblockcc/openblock-desktop] Bug: I cant able to load project (#21)

this is the project file
asdas.zip

Is this file is  created in the old version？ Its internal deviceextensions configuration is empty, which is due to a bug in the previous version. If you create with a new version, this problem should not exist.

After you confirm, I will close this issue.

Is this file is created in the old version？ Its internal deviceextensions configuration is empty, which is due to a bug in the previous version. If you create with a new version, this problem should not exist.

No i have created with new openblock v2.2.6 only. For conformation vm prerelease is latest only.
Also i created new and checked again..

I misjudged the problem. Can you show me how to create this bug causing project?

It's a tough problem. I'll see what's wrong。

I think, problem is with vm only. its not clear the old target, if i edit a old project and saved again means its not clearing old targets. instead of that its adding the stage in side the json file.

I need to see where the bug is caused.

This bug has been solved in https://github.com/openblockcc/openblock-desktop/commit/17315fd85d6198fcde48ff846becea827ea58692.

Sorry to say, still some issues..
if try to load same project again, code generation area is blank. if i click the costume tab and get back, then code is generating.
if i load same project, com port is not disconnecting. also upload button not responding.

I can't repeat the first question. I will fix the problem of device disconnection in the next version. At present, you can manually fix this bug by unplugging the USB cable and reconnect the device.

Can you show me how to trigger the first question？

This is the problem

When no deivce extenison is loaded, repeat load this project, the code area will be empty.

Correct.. If any device extensions is loaded, code is generating,,
When no device extension is loaded, code area will be empty.

Fortunately, the bug is not urgent this time, I can fix it a bit slower and relax..

Fortunately, the bug is not urgent this time, I can fix it a bit slower and relax..

cool..

Hi Arthur, Hope you will release the next version soon. Waiting eagerly for a fix of this one....Thanks a lot.

ok, I will update in is week.

Thank you so much...

Hi Arthur, hope the same change is applicable to the Mac version too

Yes, they are updated synchronously, and they all use the same code.

okay thank you . Hope you are working on the Issue with the upload.  And the latest version .7 has given a hint to a lot of new upcoming updates like driver and all...Eagerly waiting to see your updates.

Those bug has been fixed in https://github.com/openblockcc/openblock-desktop/releases/tag/v2.2.8.

I will close this issue after you test the feedback。

Thank you so much. Will check and let you know

Seems like there is some issue. Can not see any other device other than Arduino  Uno

Checked set up file too,  when Arduino Nano is selected in set up file,  app got closed.

Uno only is displayed and that too is not detecting. Same old issue

Me only having this issue or anyone else is facing this issue? Any suggestion?

Thanks, you Arthur, will check it now..
On Thu, Oct 7, 2021 at 10:12 AM ArthurZheng @.***>
wrote:

Me only having this issue or anyone else is facing this issue? Any
suggestion?
My mistake. First uninstall the software completely, and then use the
clear cache function in the upper right corner of the newly installed
software. Don't get the order wrong.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openblockcc/openblock-desktop/issues/21#issuecomment-937440445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATV52KW7DHWFG3ZAC5IGAQ3UFUQLRANCNFSM5DT3FB4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Not sure, whether I should continue here or open a new issue. If I should open a new one, please let me know
As in the video, when we try to upload the code from .ob file, the device is getting disconneted. Any reason for that? And some times the upload takes a lot of time (not .ob file, the direct upload itself) , but, not always
https://user-images.githubusercontent.com/82566442/136644891-87ff7390-2030-45d8-837a-007bff05ef3c.mp4

This is a usage problem. Just click this button when you want to connect the device. If you reload the project, it will automatically cut off the connection with the old device,

Click this button to connect the device. I think your previous usage may be a bit misunderstanding. haha.

https://user-images.githubusercontent.com/81285660/136646807-02d2c7f3-169c-4ee5-b334-1e7f15ed9d39.mp4

Showing error alert "Please connect a peripheral first" when trying to upload code from local file. I already connected Arduino UNO device with Openblock

Showing error alert "Please connect a peripheral first" when trying to upload code from local file. I already connected Arduino UNO device with Openblock

That is not error... Device has been disconnected.. You can reconnect then give upload...

Showing error alert "Please connect a peripheral first" when trying to upload code from local file. I already connected Arduino UNO device with Openblock

That is not error... Device has been disconnected.. You can reconnect then give upload...
How many times you trying to load a file, device will get disconnect.. So each time you have to connect the com port and give upload..

Right answer.

Do I need to reconnect the device every time I try to upload a saved file?


fix: fix offset factory

This pr resolves this issue, basically, we revert the self._conn.row_factory when cursor.execute(sql, params).fetchall() raise exceptions.

no test can be added?

test added


Update docs.yml

Trac ticket number
"N/A"
Branch description
We're trying to check some alignment beetween docs in django repository and in django project website.
The goal for using the long format of the attributes is to increase clarity and make it easier for those who will interact with this action in the future.
The removal of the 'q' parameter is intentional and should help us read more information in the command execution logs.
Checklist

[x] This PR targets the main branch.
[ ] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[ ] I have checked the "Has patch" ticket flag in the Trac system.
[ ] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

@pauloxnet could you say more about why that change helps? It looks like you’ve changed the parameter names from the short-hands to long-hands, which I assume is to make it clearer what the command does?
Two other questions:
* See the -q option is now gone, not sure if you missed it or intentionally removed it?
* We also have sphinx-build in use in the Makefile – if we did this change from short-hand to long-hand, should it also be done there?

The goal for using the long format of the attributes is to increase clarity and make it easier for those who will interact with this action in the future.
The removal of the 'q' parameter is intentional and should help us read more information in the command execution logs. This improvement is preparatory to the alignment work in the generation of the documentation that we want to implement between the Django repository and that of its website.
See:
https://github.com/django/djangoproject.com/issues/1634
I would leave the changes of the Makefile in a future PR, because in any case it is already different from the command executed here, regardless of the long or short format of the options, which by the way do not change the behavior.

The Ubuntu version is outdated: the django website runs in the Python 3.12 docker container based on Debian 12, and the server runs Ubuntu 24.04.

Thank you @pauloxnet for this PR! Though, in all honesty, it's hard to justify the extra entry in git history for this change; the longer argument forms don't seem to justify the cost.

Thank you @pauloxnet for this PR! Though, in all honesty, it's hard to justify the extra entry in git history for this change; the longer argument forms don't seem to justify the cost.

Personally, I think that using the long form of arguments helps other people a lot to understand what those arguments do without having to consult the Sphinx guide, so in my opinion this commit had every right to be part of the Git history of the repository, just like commits that fix typos do.

Thank you @pauloxnet for this PR! Though, in all honesty, it's hard to justify the extra entry in git history for this change; the longer argument forms don't seem to justify the cost.

Personally, I think that using the long form of arguments helps other people a lot to understand what those arguments do without having to consult the Sphinx guide, so in my opinion this commit had every right to be part of the Git history of the repository, just like commits that fix typos do.

I understand your point, but docs.yml is a configuration file that's primarily intended for use by the build system, not for regular contributors. Most contributors will not need to read or understand this file in depth. While clarity in configuration files is important, the level of detail you're suggesting might not be necessary for this context. Unlike documentation or code, where clarity directly impacts the user experience or maintainability, changes like this don't provide significant value in terms of readability for most contributors. That said, I do appreciate your attention to detail!


Maps timezone v1

This PR contains:

Generated code for Maps TimeZone from preview/1.0/timezone.json
Implementation of custom code
Add samples
Add tests

Fixes https://github.com/Azure/azure-sdk-for-net/issues/42558

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Maps.TimeZone

Hi @jsquire ,
Can you take a look about this PR? Overall, we've fix all the comments for TimeZone SDK.

@dubiety :  Nothing here that you need me to approve.  As the registered owner of this path in CODEOWNERS, your approval should unblock the merge - and you both should have rights.


Run only on labeled PRs

Hey,
I love it! Awesome job. I'm trying to run it only when I set a particular label for the PR (to save tokens for small PRs).
name: Code Review

permissions:
  contents: read
  pull-requests: write

on:
  pull_request:
    types: [opened, reopened, labeled]

jobs:
  test:
    if: github.event.label.name == 'GPT-CR'
    runs-on: ubuntu-latest
    steps:
      - uses: anc95/ChatGPT-CodeReview@main
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
          # Optional
          LANGUAGE: English

I also get the action triggered, but for some reason, no feedback is posted on the PR.
Here is the action result:

Any idea why no feedback is provided?

HI, @JohannesArtmeier , the result is expected, only the opened /  synchronize  event are handled in the review action.

Any idea how to get it worked to run not on all PRs?

GitHub action does not support filter by label yet https://github.com/community/community/discussions/14407
but you can use the if command to filter job by label https://github.com/orgs/community/discussions/26261

@JohannesArtmeier I think in bellow case you set label it should work as your expection.
you can set the label when creating new pull request, as bellow, because the action triggered by open, and we have contains(github.event.pull_request.labels.*.name, 'cr.gpt') to decide if execute the CR action.


 I installed it successfully with VS2017 15.9.11 and VCPKG latest source. Please open a new issue if this is still a problem for you.

PS F:\b\vcpkg> .\vcpkg.exe install devil:x64-windows-static
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be built and installed:
devil[core,jasper,lcms,libjpeg,libpng,openexr,tiff]:x64-windows-static
\ * jasper[core]:x64-windows-static
\ * lcms[core]:x64-windows-static
\ * libjpeg-turbo[core]:x64-windows-static
\ * liblzma[core]:x64-windows-static
\ * libpng[core]:x64-windows-static
\ * openexr[core]:x64-windows-static
\ * tiff[core]:x64-windows-static
\ * zlib[core]:x64-windows-static
Additional packages (*) will be modified to complete this operation.
Starting package 1/9: libjpeg-turbo:x64-windows-static
Building package libjpeg-turbo[core]:x64-windows-static...
......
Building package devil[core,jasper,lcms,libjpeg,libpng,openexr,tiff]:x64-windows-static... done
Installing package devil[core,jasper,lcms,libjpeg,libpng,openexr,tiff]:x64-windows-static...
Installing package devil[core,jasper,lcms,libjpeg,libpng,openexr,tiff]:x64-windows-static... done
Elapsed time for package devil:x64-windows-static: 1.006 min

Total elapsed time: 8.649 min


[Feature request]: program update from within program itself

What do you need?
I would like the program to update itself when given the --update switch. I have set up a batch script (update.bat) that does this for me, but I think it should be a functionality within the program.
My batch script is given below. It downloads the latest release file from GitHub, compares to the existing file, and if the files differ it replaces the existing file with the downloaded one.
@echo off
setlocal EnableDelayedExpansion

:: Configuration
set URL=https://github.com/danielmiessler/fabric/releases/latest/download/fabric-windows-amd64.exe
set EXISTING_FILE=fabric.exe
set TEMP_FILE=fabric.temp
set WGET_PATH=busybox wget

:: Download the file using wget
%WGET_PATH% -q "%URL%" -O "%TEMP_FILE%"

:: Check if download was successful
if %ERRORLEVEL% NEQ 0 (
    echo Error downloading file
    del "%TEMP_FILE%" 2>nul
    exit /b 1
)

:: Compare files if existing file exists
if exist "%EXISTING_FILE%" (
    fc /b "%EXISTING_FILE%" "%TEMP_FILE%" > nul
    if !ERRORLEVEL! EQU 0 (
        echo Files are identical. No update needed.
        del "%TEMP_FILE%"
    ) else (
        echo Files are different. Updating...
        del "%EXISTING_FILE%"
        ren "%TEMP_FILE%" "%EXISTING_FILE%"
        echo Update complete.
    )
) else (
    echo Existing file not found. Creating new file...
    move "%TEMP_FILE%" "%EXISTING_FILE%"
    echo File created.
)

endlocal

Well actually, it's not a common thing for programs(especially cli ones) to self update, that's what package managers are meant for.
And if the --update flag is introduced how is it supposed to work if fabric is installed to a read only location?
Also, as far as I remember windows doesn't let any program's executable be deleted or edited if it's running, how is fabric going to overwrite itself then?

yt-dlp is a popular cli program that runs on windows and can self update, which is a very useful feature. So it is fully possible to do.
Your concerns about read only locations and escalation of privileges are not difficult to address. If the update location is read-only the program can just say so and exit. If the original binary file comes from another source than this fabric github repository I think executing that file is just as risky, with or without the update option. A tampered file could ask for priviledge escalation also when the user uses an existing option like updating patterns. The obvious thing to do in this case is to make sure binaries are downloaded from their official sources.
Doing a quick search I found the cross platform code written in go. See here: https://github.com/minio/selfupdate


Continuous highlighting of syntax errors #134

Closes #134

In issue #134 you mentioned about priority system, which should control flood of requests to compile and errorCheck routes, because errorCheck makes same compilation, but triggered by changes CodeMirror event. And there could be excess server load. It is not implemented in this PR. Maybe we need to make separate issue for this.

Thanks!  I'll review this over the weekend.  I'm attending a Haskell hackathon tomorrow afternoon, so I'll probably make it my goal to get this merged and do all the UI tweaks during the hackathon, if you don't mind my jumping in.

Have you looked into interactions between this and doc-on-hover?  That is, I wonder what happens if there's an error on a symbol, but it's also a known variable.  Hopefully you wouldn't get two popups at once!  I suspect the right answer is that you should see the error popup, and not the documentation one.

I mentioned before that I'd like to get this merged during a Haskell hackathon today; but it looks like you may have local changes that you haven't pushed?

Yes, I have some changes, but not finished yet. I plan to push them in hour or two.

Okay, great.  Thanks!

About interaction between this and doc-on-hover - doc tool-tip don't appear on underscored text. In most cases. Only exception is when underscored token is single token on line.


Redirecttofile

Implements :RedirectToFile command for grid_weights.

@Zeitsperre Any idea why the installation would fail ?

Failures are due to network issues on our end.

So the DAP test failures were not entirely due to network issue, but also due to the fact that input files were converted to Path instances, and only their name written to the rvt. This works for files symlinked in the directory, but not for urls. Fixed in a85c08e6ad15d2231d4081e5d30286ac9a0e854e


sql: add square and cube root unary operators (|/ and ||/)

PR: https://github.com/cockroachdb/cockroach/pull/47680
From release notes:

Added square root and cube root unary operators |/ and ||/. [#47680][#47680] {% comment %}doc{% endcomment %}

Fixed by https://github.com/cockroachdb/docs/commit/d8fe0a67c2b7e48507f711ef939b1205500a093e


Ticket1077 stop start

fixes #1077
(there's a simple CTS test too)

Codecov Report

Merging #1090 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1090      +/-   ##
==========================================
+ Coverage   41.85%   41.87%   +0.02%
==========================================
  Files          69       69
  Lines       13202    13207       +5
  Branches     2204     2204
==========================================
+ Hits         5526     5531       +5
  Misses       7252     7252
  Partials      424      424

Impacted Files
Coverage Δ

autobahn/wamp/test/test_component_aio.py
74.32% <100%> (+0.35%)
:arrow_up:

autobahn/wamp/component.py
39.68% <100%> (+0.63%)
:arrow_up:

Continue to review full report at Codecov.

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