snakemake>5.25: "Can't locate LWP/Simple.pm in @INC "

I'm using a conda env that includes perl-lwp-simple    6.15  pl526h470a237_4. If I just activate the conda env locally and run  perl -MLWP::Simple -e 1, everything is fine. The same goes for a qsub to the cluster that I'm using. However, snakemake jobs to the cluster generate the following error:
Can't locate LWP/Simple.pm in @INC (you may need to install the LWP::Simple module) (@INC contains: /ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/site_perl/5.26.2/x86_64-linux-thread-multi /ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/site_perl/5.26.2 /ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/5.26.2/x86_64-linux-thread-multi /ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/5.26.2 .).
BEGIN failed--compilation aborted.

This error does not occur if I use snakemake 5.25, but does occur with 5.28 or 5.30, so this issue was introduced in 5.26-5.28

Note: this error makes maxbin2 effectively unusable with snakemake, so I'm surprised that no one has reported this issue before.

The same is true for the python module search path. Cluster jobs generate ImportError: No module named ... errors for python scripts. The error does not occur if the jobs are run locally nor when they are run with snakemake 5.25.
These errors do occur with snakemake 5.30.1.
Did something happen to how the cluster job scripts are formatted after v5.25?

My SGE job script template is:
#!/bin/bash
export OMP_NUM_THREADS=1
# properties = {properties}
if [[ -f ~/.bashrc &&  $(grep -c "__conda_setup=" ~/.bashrc) -gt 0 && $(grep -c "unset __conda_setup" ~/.bashrc) -gt 0 ]]; then
   echo "Sourcing .bashrc" 1>&2
   . ~/.bashrc
else
   echo "Exporting conda PATH" 1>&2
   export PATH=/ebio/abt3_projects/software/dev/miniconda3_dev/bin:$PATH
fi

{exec_job}

It appears that job submission via snakemake (using my SGE profile) results in python from snakemake being used instead of python from the conda env. For instance, the sys.path from a snakemake cluster job:
['',
'/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/python36.zip',
'/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/python3.6',
'/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/python3.6/lib-dynload',
'/ebio/abt3/nyoungblut/.local/lib/python3.6/site-packages',
'/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/lib/python3.6/site-packages']

...and sys.path for the same job if run locally or a qsub script that just includes . ~/.bashrc; conda activate /ebio/abt3_projects/software/dev/ll_pipelines/llcds/.snakemake/conda/a3edfd94/; python -c "import sys; print(sys.path)"
['',
'/ebio/abt3_projects/software/dev/ll_pipelines/llcds/.snakemake/conda/a3edfd94/lib/python37.zip',
'/ebio/abt3_projects/software/dev/ll_pipelines/llcds/.snakemake/conda/a3edfd94/lib/python3.7',
'/ebio/abt3_projects/software/dev/ll_pipelines/llcds/.snakemake/conda/a3edfd94/lib/python3.7/lib-dynload',
'/ebio/abt3_projects/software/dev/ll_pipelines/llcds/.snakemake/conda/a3edfd94/lib/python3.7/site-packages']

The SGE profile job script template just runs . ~/.bashrc and then {exec_job}, so I don't understand why snakemake>5.25 results in the altered paths.

It appears that the issue is cause by snakemake >5.25 is editing the PATH variable in the job submission script:
#!/bin/bash
# properties = {"type": "single", "rule": "validate_read1", "local": false, "input": ["/ebio/abt3_scratch/nyoungblut/LLMGQC_27982106400/88_T6/1/1/R1_tmp.fq.gz"], "output": ["tests/output_amy_n6/raw/88_T6/1/1/fastq_validate_R1.done", "tests/output_amy_n6/raw/88_T6/1/1/fastq_stats_R1.txt"], "wildcards": {"Sample": "88_T6", "Run": "1", "Lane": "1"}, "params": {"params": ""}, "log": ["tests/output_amy_n6/logs/88_T6/1/1/fastq_validate_R1.log"], "threads": 1, "resources": {"time": 472, "mem_gb_pt": 8}, "jobid": 83, "cluster": {}}

# if [[ -f ~/.bashrc &&  $(grep -c "__conda_setup=" ~/.bashrc) -gt 0 && $(grep -c "unset __conda_setup" ~/.bashrc) -gt 0 ]]; then
#    echo "Sourcing .bashrc" 1>&2
#    . ~/.bashrc
# else
#    echo "Exporting conda PATH" 1>&2
#    export PATH=/ebio/abt3_projects/software/dev/miniconda3_dev/bin:$PATH
# fi

# exit on first error
set -o errexit

# OMP
export OMP_NUM_THREADS=1

# snakemake job
 cd /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc && \
PATH='/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/bin':$PATH /ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake/bin/python3.6 \
-m snakemake tests/output_amy_n6/raw/88_T6/1/1/fastq_validate_R1.done --snakefile /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/Snakefile \
--force -j --keep-target-files --keep-remote --max-inventory-time 0 \
--wait-for-files /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/.snakemake/tmp.iqubs2mt /ebio/abt3_scratch/nyoungblut/LLMGQC_27982106400/88_T6/1/1/R1_tmp.fq.gz /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/.snakemake/conda/f65dfec9 --latency-wait 120 \
 --attempt 2 --force-use-threads --scheduler ilp \
--wrapper-prefix https://github.com/snakemake/snakemake-wrappers/raw/ \
--directory /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc --configfiles /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/config.yaml -p --allowed-rules validate_read1 --nocolor --notemp --no-hooks --nolock \
--mode 2  --skip-script-cleanup  --use-conda  && exit 0 || exit 1

In contrast, snakemake 5.25 does not edit the PATH variable:
# snakemake job
 cd /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc && \
/ebio/abt3_projects/software/dev/miniconda3_dev/envs/snakemake-5.25/bin/python3.9 \
-m snakemake tests/output_amy_n6/raw/36_T6/1/1/fastq_validate_R2.done --snakefile /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/Snakefile \
--force -j --keep-target-files --keep-remote \
--wait-for-files /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/.snakemake/tmp.xl5a312n /ebio/abt3_scratch/nyoungblut/LLMGQC_27982106400/36_T6/1/1/R2_tmp.fq.gz /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/.snakemake/conda/f65dfec9 --latency-wait 120 \
 --attempt 3 --force-use-threads \
--wrapper-prefix https://github.com/snakemake/snakemake-wrappers/raw/ \
--directory /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc --configfiles /ebio/abt3_projects/software/dev/ll_pipelines/llmgqc/config.yaml -p --allowed-rules validate_read2 --nocolor --notemp --no-hooks --nolock \
--mode 2  --skip-script-cleanup  --use-conda  && exit 0 || exit 1

I'm guessing that this is the source of my sys path issues for python and perl. Now how do I fix it...

While adding export PATH=$CONDA_PREFIX/bin:$PATH to all shell: commands works, it's not ideal, given that it has to be done for every shell command in which this PATH issue occurs.

thank you, I got this today haha


[linux]flutter app at ubuntu show chinese doesn`t work

Steps to Reproduce

1.use snap to install flutter sdk on ubuntu20.04.
2.show chinese words in flutter made app.(I guess the reason is there is no chinese fonts)
Expected results:

Actual results:

Logs

flutter doctor -v
[✓] Flutter (Channel master, 1.23.0-14.0.pre.148, on Linux, locale zh_CN.UTF-8)
• Flutter version 1.23.0-14.0.pre.148 at /home/flutter/snap/flutter/common/flutter
• Framework revision ac751cc50c (10 小时前), 2020-10-12 17:44:23 -0700
• Engine revision 11d756a62e
• Dart version 2.11.0 (build 2.11.0-207.0.dev)
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /home/flutter/Android/Sdk
• Platform android-29, build-tools 29.0.3
• Java binary at: /home/flutter/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/193.6821437/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Linux toolchain - develop for Linux desktop
• clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
• cmake version 3.10.2
• ninja version 1.8.2
• pkg-config version 0.29.1
[✓] Android Studio (version 4.0)
• Android Studio at /home/flutter/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/193.6821437
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] VS Code (version 1.50.0)
• VS Code at /usr/share/code
• Flutter extension version 3.15.0
[✓] Connected device (1 available)
• Linux (desktop) • linux • linux-x64 • Linux
• No issues found!

Duplicate of #30700


PaymentButtonContainer is not inflating Android (0.8.1)

Describe the bug
Using com.paypal.checkout.paymentbutton.PaymentButtonContainer with ('com.paypal.checkout:android-sdk:0.8.1') but its not rendering , inflating error in android.
How i can use that ? or there is some other approach ?
To Reproduce
Steps to reproduce the behavior:
add 'com.paypal.checkout:android-sdk:0.8.1'
then add <com.paypal.checkout.paymentbutton.PaymentButtonContainer
android:id="@+id/payment_button_container"
android:layout_width="match_parent"
android:layout_height="100dp"
app:paypal_button_color="silver"
app:paypal_button_label="pay"
app:paypal_button_shape="rectangle"
app:paypal_button_size="large"
app:paypal_button_enabled="true">

Hi @HafizAwaiskhan,
Thank you for reporting the issue. Could you please replace the 100dp height with warp_content. Also, implement the view state listener on the view and see what exception do you get then report it here so we know what is the actual reason for not rendering.
For example:
paymentButtonContainer.viewState = PaymentButtonContainerViewState.invoke(
                onLoading = { ->
                    Log.d(tag, tag.toString())
                },
                onFinish = { fundingEligibilityState, exception ->
                    fundingEligibilityState?.let {
                        Log.d(tag, fundingEligibilityState.toString())
                    }
                    exception?.let {
                        Log.d(tag, exception.message.toString())
                    }
                }
            )

Hi @mahmoud-turki
Thank you for reply .
D/nxoPayPalButton: eligibility status updated: Loading
D/nxoPayPalCreditButton: eligibility status updated: Loading
D/nxoPayLaterButton: eligibility status updated: Loading
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cybermart.paypalcheckoutintegration/com.cybermart.paypalcheckoutintegration.MainActivity}: android.view.InflateException: Binary XML file line #10 in com.cybermart.paypalcheckoutintegration:layout/activity_main: Binary XML file line #10 in com.cybermart.paypalcheckoutintegration:layout/activity_main: Error inflating class com.paypal.checkout.paymentbutton.PaymentButtonContainer
and your method is not even called because its crashes in beginning.

I see, it looks to me that you didn't set the config on your application level. PayPalCheckout.setConfig(checkoutConfig: CheckoutConfig). Could you check if you have the config set probably on the application level and let me know?

class MainActivity : AppCompatActivity() {
lateinit var paymentButtonContainer: PaymentButtonContainer
val TAG = "paypal"
override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)
    paymentButtonContainer = findViewById(R.id.payment_button_container)
    val config = CheckoutConfig(
        application = application,
        clientId = "AY_DPizCxyvnG91I1jHgN4A4TC5KwtFOaEyuIGkdb9Wz638V1t3W5Pnq3oALaFaz0CjYnuXWT2-nOJCa",
        environment = com.paypal.checkout.config.Environment.SANDBOX,
        currencyCode = CurrencyCode.USD,
        userAction = UserAction.PAY_NOW,
        settingsConfig = SettingsConfig(
            loggingEnabled = true
        )
    )
    PayPalCheckout.setConfig(config)

    paymentButtonContainer.paypalButtonEnabled = true
    paymentButtonContainer.setup(
        createOrder =
        CreateOrder { createOrderActions ->
            val order =
                Order(
                    intent = OrderIntent.CAPTURE,
                    appContext = AppContext(userAction = UserAction.PAY_NOW),
                    purchaseUnitList =
                    listOf(
                        PurchaseUnit(
                            amount =
                            Amount(currencyCode = CurrencyCode.USD, value = "10.00")
                        )
                    )
                )
            createOrderActions.create(order)
        },
        onApprove =
        OnApprove { approval ->
            approval.orderActions.capture { captureOrderResult ->
                Log.i("CaptureOrder", "CaptureOrderResult: $captureOrderResult")
            }
        },
        onCancel = OnCancel {
            Log.d("OnCancel", "Buyer canceled the PayPal experience.")
        },
        onError = OnError { errorInfo ->
            Log.d("OnError", "Error: $errorInfo")
        }
    )
}

}
Here is my main class ! can you please check what is wrong ?

The config should be set on the application level before you start the MainActivity otherwise you will get exception.

thank you


RapiDoc Features

Highlighting some of RapiDoc's features as these may be helpful for making a decision if RapiDoc is the right tool
I have included links of some examples below, sources of all of them can be found at https://github.com/rapi-doc/RapiDoc/tree/master/docs/examples
and the OpenAPI specs used by the examples can be found at https://github.com/rapi-doc/RapiDoc/tree/master/docs/specs
RapiDoc Features
Theming and Customization
One of the main advantage of RapiDoc is its powerful customization. RapiDoc do not put any text that indicates the documentation is rendered using RapiDoc, you can completely replace the logos with your own, colors, fonts and theme can be changed to match with your own brand. Below are some of the feature that’s usually used

You may change font according to your liking
3 different Font Sizes and spacing available
Dark and Light theme - Examples of Dark and Light Theme
Extend Dark and Light theme with your own mix of Background, Foreground, and other colors
Provide your own brand color, Logo - Logo Example
Checkout this Theme Playground for various changes that you may do

Three Different Presentation Styles

View (accordion style exploration - resembles Swagger UI but with better space management with an option of side by side Request/Response or one below the other, suited mostly for API programmers) - Example
Read (typical left navigation and content, easy to read, good for specs that are heavy on descriptions and illustrations, images, tables etc) - Example
Focused (resembles read style, but instead of continuous scroll, it focuses on a single operation at a time ) Example

Hide/Show Sections to restrict or enable functionality

Enable/Disable Built In console (TRY Feature)
Hide or Show authentication section
Hide or Show API server’s associated with your spec
Hide or show Overview sections.

2 Beautiful Schema Presentation style

Tree Style (Good for schemas that are heavily nested, resembles typescript style type annotations )
Table Style (Good for flat or schemas with less nesting )
Example where you can toggle between both the styles and find out which one suites your need

Search and Filter Functionality

Supports in place filtering of operations
You can use filtering to hide certain operations for certain users. So the same spec can be presented showing different operations to different users
Provides advance search functionality allows you search specific locations like in response, request body, parameters

Authentication

Inbuilt Authentication using OAuth, if the spec has it
For OAuth you may pre-fill the clientId and secret for your users
Supports HTTP basic and Token based authentication
You may pre-authenticate you users by supplying your own token
Various Authentication example
Pre fill client-id and secret example

Built In API console
Not a premium feature, in fact we do not have any premium product.

You can Try out API calls from the documentation
You can provide multiple API servers and make calls to any of them Example
Generates curl syntaxes
Parameters/ Request body can be pre-filled with examples, they also can be cleared or filled with a single click from the UI (nice to have for specs with lots of request parameters) Example
Auto generates multiple combinations of Request Body examples based on the schema definition -
Support Binary responses such as Images and renders them in the UI - Example

Markdown

Supports multiple markdown flavors - Example
Supports Code Syntax Highlight for various languages - Java, JavaScript, C#, python, Go and many more - Example
Create links to various sections of the Spec or list them on the side navigation bar - Example

Supports Open Schema Composition

Supports ALL-OF , ANY-OF, ONE-OF combinations and renders them beautifully - Example
Supports refs to externalize definitions

HTML, JavaScript and CSS Injection
Sometimes markdown is not enough to achieve, what’s needed. For those situations you can inject your own functionality using JS , HTML and CSS.
It also allows you to present the same spec with different, content to different section of users
You can use JS to add functionality, such as provide a button inside the document that can automatically authenticate your user
HTML Injection Example
RapiDoc’s Vendor Extensions

Code Samples
OAuth - Pre filling of clientId and Secret

Microservices support
Micro-services architecture may end up generating several OpenAPI spec, each with few Operations, However for the purpose of documentation you may want to list all these Specs in a single integrated view and should appear as a single spec. Thats possible with RapiDoc. For an inspiration have a look at this example -  https://www.northbricks.io/apis/ , which appears to be a single documentation but is made with multiple instance of RapiDoc , each rendering a separate OpenAPI spec. (VIew source from browser to check implementation)
Framework Agnostic
All the above listed feature is programmable, You may check our API section to see how you can use these feature programatically. This isn’t a React, Angular or Vue component, But a standard natively supported Web Component and therefore can be accessed and integrated with any framework or just using a plain javascript without any other library
Here is a RapiDoc API Playground where we use plain JavaScript to dynamically make changes to the RapiDoc

Hello,
What about typescript definitions?
I tried to use rapidoc in a typescript react project without success.

@francipvb
Same problem. I started working on a wrapper for use in react:
/* eslint-disable @typescript-eslint/no-explicit-any */
import React from 'react';
import 'rapidoc';

interface RapiDocProps
  extends React.DetailedHTMLProps<
    React.HTMLAttributes<HTMLDivElement>,
    HTMLDivElement
  > {
  // General
  'spec-url': string;
  'update-route'?: boolean;
  'route-prefix'?: string;
  'sort-tags'?: boolean;
  'sort-endpoints-by'?: 'path' | 'method' | 'summary' | 'none';
  'heading-text'?: string;
  'goto-path'?: string;
  'fill-request-fields-with-example'?: boolean;
  'persist-auth'?: boolean;
  // UI Colors and Fonts
  theme?: 'light' | 'dark';
  'bg-color'?: string;
  'text-color'?: string;
  'header-color'?: string;
  'primary-color'?: string;
  'load-fonts'?: boolean;
  'regular-fonts'?: string;
  'mono-fonts'?: string;
  'font-size'?: 'default' | 'large' | 'largest';
  // Navigation
  'use-path-in-nav-bar'?: boolean;
  'nav-bg-color'?: string;
  'nav-text-color'?: string;
  'nav-hover-bg-color'?: string;
  'nav-hover-text-color'?: string;
  'nav-accent-color'?: string;
  'nav-item-spacing'?: 'default' | 'compact' | 'relaxed';
  // UI Layout & Placement
  layout?: 'row' | 'column';
  'render-style'?: 'read' | 'view' | 'focused';
  'on-nav-tag-click'?: 'expand-collapse' | 'show-description';
  'schema-style'?: 'tree' | 'table';
  'schema-expand-level'?: number;
  'schema-description-expanded'?: boolean;
  'schema-hide-read-only'?: 'always' | 'never' | string;
  'default-schema-tab'?: 'model' | 'example';
  'response-area-height'?: string;
  // Hide/Show Sections
  'show-info'?: boolean;
  'info-description-headings-in-navbar'?: boolean;
  'show-components'?: boolean;
  'show-header'?: boolean;
  'allow-authentication'?: boolean;
  'allow-spec-url-load'?: boolean;
  'allow-spec-file-load'?: boolean;
  'allow-spec-file-download'?: boolean;
  'allow-search'?: boolean;
  'allow-advanced-search'?: boolean;
  'allow-try'?: boolean;
  'allow-server-selection'?: boolean;
  'allow-schema-description-expand-toggle'?: boolean;
  // API Server & calls
  'server-url'?: string;
  'default-api-server'?: string;
  'api-key-name'?: string;
  'api-key-location'?: 'header' | 'query';
  'api-key-value'?: string;
  'fetch-credentials'?: 'omit' | 'same-origin' | 'include';
  // Events
  beforeRender?: (spec: any) => void;
  specLoaded?: (spec: any) => void;
  beforeTry?: (request: any) => any;
  afterTry?: (data: any) => any;
  apiServerChange?: (server: any) => any;
}

declare global {
  interface HTMLElementTagNameMap {
    'rapi-doc': HTMLDivElement;
  }
  /* eslint-disable @typescript-eslint/no-namespace */
  namespace JSX {
    interface IntrinsicElements {
      'rapi-doc': RapiDocProps;
    }
  }
}

export const RapiDocReact = React.forwardRef<HTMLDivElement, RapiDocProps>(
  (
    {
      beforeRender,
      specLoaded,
      beforeTry,
      afterTry,
      apiServerChange,
      children,
      ...props
    }: RapiDocProps,
    ref
  ) => {
    const localRef = React.useRef<HTMLDivElement>(null);

    React.useEffect(() => {
      const rapiDocRef =
        typeof ref === 'object' && ref?.current
          ? ref?.current
          : localRef.current;

      const handleBeforeRender = (spec: any) => {
        beforeRender && beforeRender(spec);
      };

      const handleSpecLoaded = (spec: any) => {
        specLoaded && specLoaded(spec);
      };

      const handleBeforeTry = (request: any) => {
        beforeTry && beforeTry(request);
      };

      const handleAfterTry = (data: any) => {
        afterTry && afterTry(data);
      };

      const handleApiServerChange = (server: any) => {
        apiServerChange && apiServerChange(server);
      };

      console.log(`rapiDocRef`, rapiDocRef);
      if (rapiDocRef) {
        beforeRender &&
          rapiDocRef.addEventListener('before-render', handleBeforeRender);
        specLoaded &&
          rapiDocRef.addEventListener('spec-loaded', handleSpecLoaded);
        beforeTry && rapiDocRef.addEventListener('before-try', handleBeforeTry);
        afterTry && rapiDocRef.addEventListener('after-try', handleAfterTry);
        apiServerChange &&
          rapiDocRef.addEventListener(
            'api-server-change',
            handleApiServerChange
          );
      }
      return () => {
        if (rapiDocRef) {
          beforeRender &&
            rapiDocRef.removeEventListener('before-render', handleBeforeRender);
          specLoaded &&
            rapiDocRef.removeEventListener('spec-loaded', handleSpecLoaded);
          beforeTry &&
            rapiDocRef.removeEventListener('before-try', handleBeforeTry);
          afterTry &&
            rapiDocRef.removeEventListener('after-try', handleAfterTry);
          apiServerChange &&
            rapiDocRef.removeEventListener(
              'api-server-change',
              handleApiServerChange
            );
        }
      };
    }, [
      ref,
      localRef,
      specLoaded,
      beforeRender,
      beforeTry,
      afterTry,
      apiServerChange,
    ]);

    return (
      <rapi-doc {...props} ref={ref || localRef}>
        {children}
      </rapi-doc>
    );
  }
);

export default RapiDocReact;

Then you can use it like:
export function Example() {
  return (
    <RapiDocReact
      specLoaded={(spec) => {
        console.log(spec);
      }}
      show-header={false}
      spec-url="https://petstore.swagger.io/v2/swagger.json"
      render-style="read"
      theme="dark"
      style={{ height: '100vh', width: '100%' }}
    />
  );
}

export default Example;

how to change the markdown styles. for ex: If i need to style the table,what is the approach?

@mrin9 Hi Mrinmoy, pls can you update examples for the filtering functionality, specifically to hide certain operations for specific users?
Thanks

It'd be great if you could generate other syntaxes than curl. This is useful, but generating a fetch call would also be useful for developers.


Dots in definition interface name

https://github.com/Azure/azure-rest-api-specs/blob/master/specification/policyinsights/resource-manager/readme.md#tag-package-2018-07

Please reopen if this is still an issue in v4 generator.


Make publishers thread-safe

Switches to using a buffer per call to Publish() rather than a global shared one. A bytes.Buffer is not thread safe, so if you have a publisher in use in multiple goroutines, it is possible that they will interfere with eachother and write unpredictable messages to the AMQP server.
There are two alternative approaches to this:

Document publishers are not thread safe. We should probably do that at the broker level even so that the contract is clear.
Wrap a mutex around the calls to Publish().

@armon either way you want to go is fine with me. Let me know what you think.

FWIW the underlying streadway/amqp lib are thread-safe for both Publish() and Consume() (consume returns a channel and publish takes a lock).

@armon bringing this in as I think we should probably be thread-safe here for the reasons mentioned above. Let me know if you'd prefer it another way and I can make any adjustments!


With replicas > 1, Runners enter a kill loop of the user code

No clue why this is happening yet, and it only seems to occur when a single deployment has > 1 live replica. It does not occur when there are two deployments with 1 replica each.
The only message is the following, which is singularly unhelpful.
trace: Registered with ControlPlane, next heartbeat in 3.405476999s
trace: Registered with ControlPlane, next heartbeat in 3.918494051s
error: signal: killed: Deployment terminated.
trace: Registered with ControlPlane, next heartbeat in 4.587428223s
trace: Registered with ControlPlane, next heartbeat in 3.600794194s

I can no longer replicate this.


Add external group (generic I/O of arrays beyond the trexio format)

This PR will partially address the following:

#112

I have implemented trexio_[write|read|has]_external_[int32|int64|float32|float64]_array family of functions in C and Python APIs. Fortran front end is not supported yet.
Only TREXIO_HDF5 back end is supported, attempt to use TREXIO_TEXT should raise TREXIO_NOT_SUPPORTED error.
The list of arguments is different from conventional TREXIO functions due to the absense of explicit dimensions and data types as in TREXIO format.
One important difference is that we have to provide name string to all aforementioned functions, which defines the name of the array in the TREXIO file. This argument is key to accessing the data correctly.

Nice!
Can you please add a section at the end of the trex.org file for documentation? It would be nice to briefly explain that this feature exists, and give a few examples.
Also, it would be interesting to have a function that returns the number of external arrays, and an array with the names of the arrays.
For the text back-end, I think we can create an "external" text file that contains the external arrays.
I would prefer to merge when the text backend also has this feature, otherwise I am afraid that these two will diverge. If you want, can help with that.

Can you please add a section at the end of the trex.org file for documentation? It would be nice to briefly explain that this feature exists, and give a few examples.

OK, will do. I think examples should go in the front end org file since they involve API calls. What do you think?

Also, it would be interesting to have a function that returns the number of external arrays, and an array with the names of the arrays.

Maybe. It might be useful to have a function, which returns dimensions and ranks of  external arrays in order to allocate the memory accordingly.

For the text back-end, I think we can create an "external" text file that contains the external arrays.

As we discussed in #112 , it's easier to have one text file per external array, rather than one external file with all arrays. I will not have time for that in the nearest future though. The PR is not urgent, still experimental.


TypeError: e.map is not a function

Bug
Unable to get into entries on the CMS to update my pages due to error page being presented. "TypeError: e.map is not a function"
To reproduce
I log in to Netlify CMS, navigate to pages, click on index and then am presented with the attached screenshot.
What I expect
I would expect to log in, navigate to pages, select the index page and be presented with editable boxes.
Screenshot

Applicable Versions:

Netlify CMS version<EMAIL_ADDRESS>Git provider: git-gateway
Browser version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36

CMS configuration
backend:
  name: git-gateway
  branch: master
site_url: https://secure24.co.uk
publish_mode: editorial_workflow
media_folder: _site/images/uploads
public_folder: src/images/uploads
collections:
  - name: pages
    label: Pages
    files:
      - name: index
        label: Index
        folder: src/site/_data/
        file: src/site/_data/index.json
        fields:
          - label: Title
            name: title
            widget: string
          - label: Subtitle
            name: subtitle
            widget: string
            required: false
          - label: Intro
            name: intro
            widget: markdown
          - label: Secondary content
            name: secondaryContent
            widget: list
            required: false
            fields:
              - label: Title
                name: title
                widget: string
              - name: content
                label: Content
                widget: list
                fields:
                  - label: Paragraph
                    name: paragraph
                    widget: markdown
                    required: false
                  - name: bullets
                    label: bullets
                    widget: list
                    required: false
                    fields:
                      - label: BulletPoint
                        name: bulletpoint
                        widget: string
                        required: false
          - name: pricing
            label: Pricing
            widget: list
            fields:
              - label: Package
                name: package
                widget: string
              - name: features
                label: Features
                widget: list
                fields:
                  - label: Feature
                    name: feature
                    widget: string
              - name: pricing
                label: Pricing
                widget: list
                fields:
                  - label: Price
                    name: price
                    widget: string
      - name: about
        label: About
        folder: src/site/_data/
        file: src/site/_data/about.json
        fields:
          - name: about
            label: about
            widget: list
            fields:
              - label: Title
                name: name
                widget: string
              - label: Subtitle
                name: subtitle
                widget: string
              - name: about
                label: About
                widget: list
                fields:
                  - label: Paragraph
                    name: paragraph
                    widget: markdown
                  - label: Image
                    name: image
                    widget: image
                    required: false
      - name: caseStudies
        label: Case Studies
        folder: src/site/_data/
        file: src/site/_data/caseStudies.json
        fields:
          - name: studies
            label: Studies
            widget: list
            fields:
              - label: Name
                name: name
                widget: string
              - label: Subtitle
                name: subtitle
                widget: string
              - name: about
                label: About
                widget: list
                fields:
                  - label: Paragraph
                    name: paragraph
                    widget: markdown
                  - label: Author
                    name: Author
                    widget: string
                    required: false
              - label
...

Hi @LisaP117, thank you for opening the issue.
Do you mind sharing the full configuration? That will make it easier for others to reproduce the issue

Please let me know if this is correct. Thanks
Repository - https://github.com/LisaP117/secure24
Full config.yml file
backend:
name: git-gateway
branch: master # Branch to update (optional; defaults to master)
site_url: https://secure24.co.uk
This line should not be indented
publish_mode: editorial_workflow
media_folder: "_site/images/uploads" # Media files will be stored in the repo under images/uploads
public_folder: "src/images/uploads"
collections:
- name: "services"
label: "Services"
create: true
folder: "src/site/_data/_services/"
fields:
- {label: Title, name: title, widget: string}
- name: services
label: Services
widget: list
fields:
- {label: Title, name: name, widget: string}
- {label: Subtitle, name: subtitle, widget: string}
- name: content
label: Content
widget: list
fields:
- {label: Paragraph, name: paragraph, widget: markdown}
- {label: 'Image', name: 'image', widget: 'image', required: false}

name: "pages"
label: "Pages"
files:

name: "index"
label: "Index"
folder: "src/site/_data/"
file: "src/site/_data/index.json"
fields:

{label: Title, name: title, widget: string}
{label: Subtitle, name: subtitle, widget: string, required: false}
{label: Intro, name: intro, widget: markdown}
label: Secondary content
name: secondaryContent
widget: list
required: false
fields:

{label: Title, name: title, widget: string}
name: content
label: Content
widget: list
fields:

{label: Paragraph, name: paragraph, widget: markdown, required: false}
name: bullets
label: bullets
widget: list
required: false
fields:

{label: BulletPoint, name: bulletpoint, widget: string, required: false}

name: pricing
label: Pricing
widget: list
fields:

{label: Package, name: package, widget: string}
name: features
label: Features
widget: list
fields:

{label: Feature, name: feature, widget: string}

name: pricing
label: Pricing
widget: list
fields:

{label: Price, name: price, widget: string}

name: "about"
label: "About"
folder: "src/site/_data/"
file: "src/site/_data/about.json"
fields:

name: about
label: about
widget: list
fields:

{label: Title, name: name, widget: string}
{label: Subtitle, name: subtitle, widget: string}
name: about
label: About
widget: list
fields:

{label: Paragraph, name: paragraph, widget: markdown}
{label: 'Image', name: 'image', widget: 'image', required: false}

name: "caseStudies"
label: "Case Studies"
folder: "src/site/_data/"
file: "src/site/_data/caseStudies.json"
fields:

name: studies
label: Studies
widget: list
fields:

{label: Name, name: name, widget: string}
{label: Subtitle, name: subtitle, widget: string}
name: about
label: About
widget: list
fields:

{label: Paragraph, name: paragraph, widget: markdown}
{label: Author, name: Author, widget: string, required: false}

{label: 'Image', name: 'image', widget: 'image', required: false}
{label: YouTube video embed URL, name: 'videoUrl', widget: string, required: false}

name: "privacyPolicy"
label: "Privacy Policy"
folder: "src/site/_data/"
file: "src/site/_data/privacyPolicy.json"
fields:

{label: Title, name: title, widget: string}
{label: Subtitle, name: subtitle, widget: string}
{label: Intro, name: intro, widget: markdown}
name: sections
label: Section
widget: list
fields:

{label: Title, name: title, widget: string}
{label: Policy Description, name: policy, widget: markdown}

name: "faqs"
label: "FAQs"
folder: "src/site/_data/"
file: "src/site/_data/faqs.json"
fields:

{label: Title, name: title, widget: string}
{label: Subtitle, name: subtitle, widget: string}
{label: Intro, name: intro, widget: markdown}
name: sections
label: Section
widget: list
fields:

{label: Title, name: title, widget: string}
{label: Answer, name: answer, widget: markdown, required: false}
label: List
name: list
widget: list
required: false
fields:

{label: Content, name: content, widget: markdown}

Can I work on this issue? I am new to the project and would like to learn through this issue.

Yes you can, I’d appreciate the help!

I could not replicate the issue by using the test-repo as backend as I was open and access the index page.

To connect with your backend through git-gateway I believe I would be needing some credentials

I used the gatsby template for the backend and was not able to reproduce this error. It was working perfectly fine and I was able to access the index page.

I am getting the above error when i deploy to netlify please help

can i work on this ? is it resolved yet ?

@AryanSwaroop sure, I assigned you the issue.

thanks 1 working on it

not able to reproduce the issue , not on netlify or local. @aravindont @LisaP117 can you share the repo , old one not there !!


Fix typos in README.md

Hi everyone!
Thanks for this awesome and helpful extension 🙌
Just a quick PR fixing some typos I found in the Readme

@dogenoh @K8Liu @MichaelBenliyan @fsalazar88 @justin27kim
Please review


API Documentation

Research / Work on the ability to create source code documentation right out of the source code.

For Java you can easily generate a html documentation out of source code. It's important that the comments are formatted this way:
/**

Comment here.
*/

This is the Javadocs comment style. There are probably free tools out there, that can generate a documentation, but I personally use the integrated tool that IntelliJ offers. I already generated a first version, that can be found in Backend/docs (Payment Branch currently)
On the frontend side there are most certainly also tools, that can be used to generate documentation from javascript code. But we would probably also have to use a specific comment style, so that it works?


Parsing of async software tasks and allowing 0-priority async tasks

This was part of R&D work to get async support and what became RTIC v2. This branch was paired with the now superseded work in https://github.com/rtic-rs/rtic/pull/646
RTIC v2 includes all this and more
Closing


[Editor] Fix windows can go into a state where right click doesn't rotate camera

Fixes #93613
I’m not sure of the solution, but an error occurs when calling SetTimer() with activate_state != WA_CLICKACTIVE

It doesn't seem like my code caused 🐧 Linux / Editor with doubles and GCC sanitizers to fall.

It doesn't seem like my code caused 🐧 Linux / Editor with doubles and GCC sanitizers to fall.

No, this was a temporary issue on the master branch when you made the PR. You'll need to rebase to solve it though.


Migration of theme to modern responsive theme

https://github.com/python/devguide/pull/679

There's two PRs opened on python-docs-theme to modernize the current theme:

responsive
dark theme

But I do not have the CSS-fu to help here, I can only test them.
Beware if we want to switch theme, they'll have to support our language and version switchers, which is currently probably too convoluted :

cpython's tools/templates/layout.html add placeholders in the rootrellink block.
docsbuild switch (which knows the list of versions and languages) injects a switchers.js right before

In the other hand, rootrellink is from sphinx, not the theme, so it could by chance just work.

@pradyunsg, quoting you to continue in this relevant thread:

If there's genuine interest in the modernization of the Python documentation and python-docs-theme (i.e. fairly major changes to look more like from-this-decade), I am very very interested in helping with that. :)

I think we all agree that the theme should evolve. Even from an SEO point of view (mobile-first ranking in SERPs) it's important.
As you understood, my front-end skill is absent, that's why I refrained to comment on https://github.com/python/python-docs-theme/issues/55 for example (which I followed carefully). I also avoid to merge PRs in the theme without approbations of skilled front-end developers: I can test the visual quality, but not the implementation quality.
But if you need any help understanding how the language and version switchers work, or if they need to be changed, I'll gladly help here. I recently added a github workflow on python-docs-theme to build with the version and language switchers (html downloadable as a build artifact).

I admit that I also don't have front end JS/CSS skills. I've been following all the discussions in python-docs-theme repo as well. I. just don't know how to test or how to review those changes.

I can take a look at the existing python-docs-theme along with Furo to determine if it makes more sense to add Python-specific stuff to Furo or vice versa. One of the nice things about Furo is it was designed with Sphinx 3.x in mind so it will bake in the advantage of updates from that, at least from a theme perspective. I've been using Furo in other projects and have been very happy with it in those.

language and version switchers

Yup yup! IIUC, those are the main CPython-docs-specific thing, and there's decent complexity in the build scripts due to this.
I'll take a closer look at the build scripts over this long weekend! FWIW, I'm on the PSF Slack, so if it's needed at some point, it would be possible to have a fast-than-GitHub-comments chat there.
FWIW, If there's no "strict" time pressure, I'm working on https://github.com/pradyunsg/sphinx-basic-ng/, which might actually be a better base to build upon than Furo. That + Furo's CSS which basically describes the other Sphinx theme I'm working on right now. :)

I just don't know how to test

I just made this very simple: the python-docs-theme now provide a cpython built documentation as a check artifact. It even has the version and language switchers, exactly like it's built on docs.python.org (with all the dirty tricks I'm not proud of, like editing HTML using sed).
Next step would be to temporarily (has to be defined...) host artifacts somewhere (has to be defined...) and make a bot to give the link in the PR?

Next step would be to temporarily (has to be defined...) host artifacts somewhere (has to be defined...) and make a bot to give the link in the PR?

How about including some test docs that uses the theme, and deploy to Read the Docs? We could then enable previews from PRs, and it would automatically build and deploy using the theme to a test RTD site, making it easy to test the PR on desktop and mobile.
For example, https://github.com/python/devguide/pull/679 has a preview at https://cpython-devguide--679.org.readthedocs.build/

I have no idea how incompatible our language and version switchers are with RTD though.

I believe that RTD has a pretty comprehensive version switcher. We should reach out to Eric Holscher and team.

I just flagged this discussion to @humitos, as he's in one of the members of RTD. :)

For info, here's how the current language and version switchers in docs.python.org are working:

The theme places an empty div

 so we can play around later.
The theme have the CSS style for those switchers.
The docsbuild script is the only source of truth about known versions and known languages.
The docsbuild script creates a JS file with this list of languages and versions, what's needed to create the DOM elements, and the event handlers to do the switches.
And now for the ugly part: the docsbuild script injects the JS on every pages.

Here are some ideas on how to enhance this: https://github.com/python/docs-community/issues/4

Okay, so... I've definitely been nerd-sniped by this. Here's an update/brain-dump on how that's going. 😅
I've started working on a Sphinx theme, for documentation sets with the size and structure of Python's documentation. The initial working name is Lutra, which is what I'll use in this comment, but it is definitely subject to change. Here's the documentation sites I'm currently using, to draw inspirations from (additional suggestions welcome):

Furo (du'oh!)
Ionic Framework documentation
Just the Docs for Jekyll
mkdocs-material for MkDocs
Tailwind CSS documentation

My thought process for how things could work is: Lutra builds upon sphinx-basic-ng (more on this below) and becomes the base theme for python-docs-theme and pypa-docs-theme, with the python-docs-theme being only for Python's documentation. This model means we can get rid of documentation-related templates in CPython's source tree and specialise python-docs-theme to only be for Python, which may be super useful if we want to add build-time logic (in the Sphinx extension code for python-docs-theme), for generating the switchers (#4) or including the top bar from https://www.python.org/ (as I'd originally proposed in https://github.com/python/python-docs-theme/issues/10).
(theme dependency tree -- status quo)
basic (built-in Sphinx theme)
╰─▶ default (built-in Sphinx theme)
    ╰─▶ python-docs-theme
        ╰─▶ pypa-docs-theme

(theme dependency tree -- what I'm currently thinking of)
basic (built-in Sphinx theme)
╰─▶ basic-ng
    ├─▶ [other themes]
    ╰─▶ lutra
        ├─▶ pypa-docs-theme
        ├─▶ python-docs-theme
        ╰─▶ [other themes]

As for sphinx-basic-ng -- that's something that will quite possibly be used by some other major themes in the Sphinx ecosystem (like sphinx-book-theme and pydata-sphinx-theme) -- I'm working closely with multiple theme authors/maintainers to figure out ways to reduce the repeated work, and have an actually thought out scaffold for this. See sphinx-basic-ng's repository/issue tracker if you're curious. I worked on it a bit last weekend and am pretty happy with where it is now, in terms of the actual implementation. It still needs a lot of documentation for theme authors, but slow-and-steady progress is the ongoing goal for all these things. And because video >> pictures >> words, here's a quick demo of sphinx-basic-ng, specifically the default behaviour of the fairly customisable scaffolding that comes with it:
https://user-images.githubusercontent.com/3275593/137479237-61c72b0a-9c75-421a-818f-35c6291ec71e.mov

Can I just say that I love it?

I've made some more progress, and things are at a point that it's worth sharing.
The main thing is that I've settled down on the design/aesthetic I'm going for, as well as the typography and navigation design now. I'm pretty happy with how this is working now!
https://user-images.githubusercontent.com/3275593/142778891-4eeb1202-2d8c-4e53-be77-e361a464c5dd.mov
I also ended up writing a development workflow tool which is a PEP 517 backend as well. So... yea. That happened. 😅
The next things to do would be the rest of the scaffold (like the top bar, the footer, figuring out sidebar overflows etc), adding search + domain index + module index pages, and... stylizing everything that's in the metaphorical kitchen sink for Sphinx. So... yea, baby steps.

It's a new year! And I have made even more progress!

There's a dark mode toggle now (auto/dark/light), and everything is stylized to respect this!
https://user-images.githubusercontent.com/3275593/148451030-7de943a8-9a56-4e39-9c5e-28930e38cf85.mov

I've stylized most of the content that Sphinx can output.  I'm quite happy with how the anchors / :target styling for various things has worked out though!
https://user-images.githubusercontent.com/3275593/148451130-af821752-d119-47b2-8eb6-229c65d0edec.mov

As you can probably tell, there's two big pieces that need to be stylized still -- the header and footer. Along with that, I also wanna get with a few bits of functionality done, before we can start testing things out with the docsbuild-scripts (eg: highlighting right sidebar entries on scroll, showing "back to top" when scrolling up, "edit this page" buttons, "was this page helpful", ability to add stuff to the top of the right sidebar etc).
I was briefly worried that this is currently written as a Sphinx 4+ theme, but it looks like the current main on CPython is Sphinx 4 already: https://github.com/python/cpython/blob/c9137d4b638c0699b904011cafe68895d28dd80b/Doc/requirements.txt#L6

(oh, and I tweaked the colors to be purple out of the box, but it's like, ~10 lines of code in a downstream theme to change that -- I'd imagine that python-docs-theme can change that to the cyan-ish colors from the video in the comment before)

Love it! If I was still an active Sphinx maintainer, I'd suggest that this become the new default :grin:

@pradyunsg It looks awesome! Do we have a RTD site where we can test the theme? I like it and I would like to make that the prefered choice for most python based projects, including lots of Ansible tools my team is managing.
It would be great if we could get an audit/review from an UX designer, especially around the accessibility areas. Making changes after adoption would be much harder so is better to do the accessibility checklist before.
I do have some previous experience with i18n/a11y but not enough to do it myself. Still, I will mention few bits

[ ] able to use most screen sizes, portrait/landscape, mobile, different text size in browser, it should be ok even zoom at 125%
[ ] color blindness
[ ] display visited links differently than normal links (:hover, :visited)
[ ] some level of branding
[ ] Does it work well with RTD service?
[ ] Is auto/light/dark mode preference saved using localStorage instead of cookies? Nobody likes them, or the mandatory prompts their presence require.

I do remember a nightmare related to Docker documentation which for 3+ years it was impossible to display in a narrow/split screen (even 4K/5K) as the sidebar was switching to mobile view and taking the whole page width.

Do we have a RTD site where we can test the theme?

No. I'll put this up once I'm ready to put things up for testing. :)

It would be great if we could get an audit/review from an UX designer, especially around the accessibility areas.

I have spent a not-insignificant amount of time working on the accessibility aspects of Furo, so I'm not "flying blind" -- none the less, if we can get someone who has done this professionally to review these aspects, that would be great! :)

Is auto/light/dark mode preference saved using localStorage instead of cookies?

See https://github.com/pradyunsg/furo/blob/d6b217f8bb021f137928aa30f1b41e829e87d73f/src/furo/assets/scripts/furo.js#L57, which is what this is based off.

Hmm... I was thinking about this a bunch today, and a good question came to mind: What do people find good about the existing docs.python.org theme?
One potential answer that came to mind was: The collapsing sidebar. So... I've gone ahead and implemented that. I can't really think of anything else, and short of sending an email to something like python-ideas, does anyone have any suggestions for how to easily survey a bunch of folks?

The collapsing sidebar

I personally don't like it, but I heard of people using it.

any suggestions for how to easily survey a bunch of folks?

Deploy the theme on docs.python.org/dev/ (I can help) and see if someone miss something? I used this strategy a lot at $DAYJOB, we called it WDD for Whine Driven Development: Push to production and raise an ear to catch if someone whines, (works best in big open spaces).

@pradyunsg add a banner/admonition to the docs like the one I've made for pip in the past, for the UX research? Our community/docs folks at Ansible do this as well putting links to surveys there.

add a banner

Oh yes, we do use a "deprecation notice" banner on docs.python.org too, see: https://docs.python.org/2.7/.

add a banner/admonition to the docs like the one I've made for pip in the past, for the UX research?

I'd prefer to instead allow adding a upvote/downvote thing, into a survey platform or whatever -- similar to the bottom of https://squidfunk.github.io/mkdocs-material/getting-started/#with-git or https://www.gatsbyjs.com/docs/quick-start.

Oh yes, we do use a "deprecation notice" banner on docs.python.org too, see: docs.python.org/2.7.

Yup! We'll treat that as an "announcement", similar to how Furo does things! :)

Hi! Let me play project manager here.
What's the status of this issue? With https://github.com/python/python-docs-theme/pull/46 merged, is this “done”? If not, when will it be considered done? Should individual issues be filed for the remaining work?

What's the status of this issue?

Still needs more work. :P

With python/python-docs-theme#46 merged, is this “done”?

I don't think so. When Python documentation came up in a Talk Python to Me podcast episode, one of the things explicitly pointed out was that docs.python.org vs something like https://tailwindcss.com/docs/ are completely different experiences -- with the latter being a lot more pleasing to look at.

If not, when will it be considered done?

I don't think this should be considered done unless we make some progress on improving the overall site design.

Should individual issues be filed for the remaining work?

I don't think we have a clear set of steps for what we want to do here TBH. :)

So... that theme that I've been posting progress updates about here -- I've put the very-WIP code for it in a GitHub repository: https://github.com/pradyunsg/lutra/. The theme's own documentation is built using itself, and is available at https://pradyunsg.me/lutra/
Everything about this is very WIP but... hey, it is available publicly under MIT now! :)

For posterity, there was some discussion about the documentation theme in the Python Documentation Community Discord (starting around https://discord.com/channels/935215565872693329/935215566334079058/975795392027447387).

I've gotten Lutra to a point where it's building the Python documentation without crashes and most elements are stylised. Here's a link to CPython's current main rendered with Lutra: https://pradyunsg-cpython-lutra-testing.readthedocs.io/en/latest/index.html.
I'd like to gather folks' inputs/opinions/feedback, to figure out what else needs to be changed/improved about it. To avoid hijacking this issue, I've filed https://github.com/pradyunsg/lutra/issues/22 which is where I'd request folks to post their feedback. I've also added some additional context there, for folks who are interested!
Fair warning: The theme is still WIP, so don't be surprised if you spot things that are borked/non-functional -- please let me know if/when you see that!

Is not having an index page intentional? I think also I'd prefer if languages was spelled out as the word, I was confused by the red glyph in the navigation bar and thought it was a rendering error initially.

Screenshot

A

Waiting on the RTD build which will add a description for why that page is empty: https://github.com/pradyunsg/cpython/commit/f41c09bb9e7ad12af6c0528a8f6ec44c487e146f
The red glyph is mostly a placeholder reminder for me, that I have to handle language and version selectors outside of RTD builds.


⚠ Bofrost.de has degraded performance

In 7068b24, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2025 ms

Resolved: Bofrost.de performance has improved in c08c599 after 45 minutes.


CharacterBody3D is not implemented

I get error _physics_process not implemented for the CharacterBody3D.
Edit:
when placing a characterbody2D with a script and a _physics_process function you will get a "_physics_process not implemented for CharacterBody3D" error

Yeah, I haven't looked at CharacterBody3D at all yet. Currently I'm focused on getting RigidBody3D working with all its different shapes and configurations. After that it's likely gonna be Area3D, since it shares a lot of stuff with RigidBody3D. So it might be a while before I get to this.
Feel free to include some steps of how to reproduce the error though, for future reference.

ahh yes... Updated


Change examples to a more use case/guides oriented documentation

Currently, we have the examples documented as if they were all in the same project.
It would be better if they were written more oriented to use cases. Similar to what Quarkus has on its guides.

@hbelmiro, feel free to open another issue to enhance the documentation of our examples. Also, we need to migrate to Quarkus Guides Antora style.


:react-native-my2c2p-sdk:compileDebugJavaWithJavac FAILED

/my-project/node_modules/react-native-my2c2p-sdk/android/src/main/java/com/wednesdaynight/rn2c2p/RN
My2c2pSdkPackage.java:19: error: method does not override or implement a method from a supertype
@Override
^
1 error

I am use gradle version 3.1.0

just remove the @override on the mentioned file.
It works for me


Android Probability Crash

This is the crash call stack.
It looks like the crash point is at https://github.com/cberner/redb/blob/master/src/tree_store/btree.rs#L52
redb is used by me to cache messages on websocket, inserting them when they come in and removing them when they are successfully consumed. crash happens on some phones, I'm not sure if it has something to do with different versions of db format.

Unfortunately that backtrace is just from a poisoned lock, presumably during panic unwinding, and not the actual error. Can you run with RUST_BACKTRACE=full? Or even better, do you have a way to reproduce this?

I can't reproduce it at the moment, I'll try to reproduce the problem in the next two days

I found a bug that could potentially cause this, although it's impossible to know without a repro. Feel free to re-open if you continue to have this issue after that PR lands.


Small fixes to build instructions

Make instructions in docs consistent with the readme. In the examples, only refer to the readme (in case it's ever changed again).

Thanks!


Tensor inversion RuntimeError and the possibility to use customized forward PnP solver

Hi Bo CHEN,
Thanks for sharing the wonderful code. I have some questions regarding the BPnP implementations and I would appreciate it if you could give me a hand:

torch.inverse() RuntimeError. I encounter this error when running the demoPoseEst.py. The other 2 demo scripts work perfectly though. The complete error message is:

(bpnp) qiyan@qiyan-qdlpc:~/Documents/BPnP$ python demoPoseEst.py
i:    0, loss:21164.001953125
i:    1, loss:21162.431640625
i:    2, loss:21160.376953125
i:    3, loss:21158.195312500
i:    4, loss:21156.015625000
i:    5, loss:21153.923828125
i:    6, loss:21151.771484375
i:    7, loss:21149.613281250
i:    8, loss:21147.451171875
i:    9, loss:21145.251953125
i:   10, loss:21143.001953125
Traceback (most recent call last):
  File "demoPoseEst.py", line 67, in <module>
    loss.backward()
  File "/home/qiyan/anaconda3/envs/bpnp/lib/python3.7/site-packages/torch/tensor.py", line 195, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/home/qiyan/anaconda3/envs/bpnp/lib/python3.7/site-packages/torch/autograd/__init__.py", line 99, in backward
    allow_unreachable=True)  # allow_unreachable flag
  File "/home/qiyan/anaconda3/envs/bpnp/lib/python3.7/site-packages/torch/autograd/function.py", line 77, in apply
    return self._forward_cls.backward(self, *args)
  File "/home/qiyan/Documents/BPnP/BPnP.py", line 96, in backward
    inv_J_fy = torch.inverse(J_fy)
RuntimeError: inverse_cuda: U(6,6) is zero, singular U.

I tried using cpu instead of cuda and the problem remains. BTW, as you suggested in here, torch 1.4.0 and torchvision 0.5.0 are used. Accordingly, kornia 0.2.2 is installed for compatibility as shown in here, rather than using the latest version.

Can we use another customized PnP solver in the BPnP forward loop?
https://github.com/BoChenYS/BPnP/blob/114f731dbf2b287f818b8afdce0ac479068fa4f1/BPnP.py#L20-L42
For the vanilla BPnP forward function, the output pose doesn't come with autograd and it seems fine to use alternatives to solve 2D-3D correspondences.
So do you think it feasible to implement BPnP directly for other PnP solvers by replacing line 32, 36? For example, those based on P3P/EPNP which are also supported by the openCV.

Many thanks! Have a nice day & week-end.
Qi Yan

Hi Qi,
I couldn't reproduce your first error, so not sure where went wrong. It seems that you get a singular Jacobian J_fy, which is highly unlikely. If it happens a lot, can you try adding small values to J_fy to see if it solves the problem, such as:
J_fy = J_fy + 1e-12*torch.eye(m)
For the second question, the answer is yes. The PnP solver can be replaced with other solvers in the forward pass. Yet the effect should be depending on your application and the solver.
Cheers
Bo

Hi Bo,
Thanks for your helpful feedback!
For the first one, unfortunately I cannot solve it by adding small values. This issue can be avoided by using numpy matrix inversion: inv_J_fy = torch.from_numpy(np.linalg.inv(J_fy.cpu().numpy())).to(device). This might not be an elegant solution though.
For the second one, could you please elaborate a bit on it? In my understanding, it is because of the stationary condition required by eq. (13), and as long as a local minimum is obtained, we can freely use alternative PnP solvers.
Many thanks,
Qi Yan

Hi Qi,
Yes, you are right. I should have added that the objective of the PnP solver is used in the backward pass for constructing the f function. Currently backward assumes that the objective is the sum squared reprojection residuals, which is true for most PnP solvers, I think. But if your PnP solver specifically optimises a different objective, then you might want to watch out for the gradients.
Hope that helps.
Bo

Thanks for your message!


Add documentation for Windows systems

[ ] Add Windows in the list of compatibility systems
[ ] Test and mark which functions are not fully working on Windows
[ ] Add results in lb_df_fstype() for Windows

FS types for Windows:

NTFS: ntfs


Feature request: Show more suggestions in the search result list

First: This plugin is great! Thanks!
But: Currently the 'normal / tag search' and the 'recent search' shows only a maximum of 10 suggestions / search results. This a an annoying restriction (especially when searching tags).
It would be great, if the search result lists shows more/all (preferably a custumizable number of) suggestions (resulting in a scrollable result list like in the 'backlink search').

Hi, @avirosso. Thank you for your FR!
I agree with you, so I'll implement it 👍

@avirosso
I have released to v3.1.0 🚀
Please confirm whether it works as you expected.

Yes, works great (and even custumizable)! Thanks!


Differentiate object literal braces with other braces

Currently the grammar only mark switch case braces with switchStart and switchEnd. Is it possible to do this for other type of braces?
Here's the list that's not currently supported:

function / arrow fn braces
conditional braces
for and while loop braces
object literal braces

Probably, but why do you need this? The reason I tag the switch statements is to support my JSX auto indentation.

I see, I'm creating atom syntax theme and I want to dim all braces and punctuation colors, except when for object literal (because it's not block statement).
Can you help me guide which part I should learn. I'll try to contribute if this is something that you think it's okay

Added litobj class to object braces. Needs Atom ^1.13.0 & language-babel 2.49.4


Add links to badges

The badges (see the below image) in the README.md file doesn't contain any link to the related web pages and without them they are of no use.

I want to  add links to the badges so that anyone can go to the webpages after clicking on them.

@Tejas1510 sir should I go ahead to make changes??

@Umesh-01 go ahead!!


Set async mode true for ResourceGroup

Description of your changes
Potential fix for: https://github.com/upbound/provider-azure/issues/577
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Manually:

ResourceGroup.azure:

status:
  atProvider:
    id: /subscriptions/038f2b7c-3265-43b8-8624-c9ad5da610a8/resourceGroups/example-resources
    location: westeurope
    tags:
      provisioner: crossplane
  conditions:
  - lastTransitionTime: "2023-10-30T13:27:02Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2023-10-30T13:27:59Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2023-10-30T13:27:21Z"
    reason: Success
    status: "True"
    type: LastAsyncOperation
  - lastTransitionTime: "2023-10-30T13:27:21Z"
    reason: Finished
    status: "True"
    type: AsyncOperation

VirtualNetworkRule.dbformariadb

status:
  atProvider:
    id: /subscriptions/038f2b7c-3265-43b8-8624-c9ad5da610a8/resourceGroups/example-vnr/providers/Microsoft.DBforMariaDB/servers/example-vnr/virtualNetworkRules/example-vnr
    resourceGroupName: example-vnr
    serverName: example-vnr
    subnetId: /subscriptions/038f2b7c-3265-43b8-8624-c9ad5da610a8/resourceGroups/example-vnr/providers/Microsoft.Network/virtualNetworks/example-vnr/subnets/internal-vnr
  conditions:
  - lastTransitionTime: "2023-10-30T18:13:55Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2023-10-30T18:14:06Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2023-10-30T18:14:06Z"
    reason: Finished
    status: "True"
    type: AsyncOperation
  - lastTransitionTime: "2023-10-30T18:16:02Z"
    reason: UpToDate
    status: "True"
    type: Test

Uptest:

examples/azure/resourcegroup.yaml: https://github.com/upbound/provider-azure/actions/runs/6693578476
examples/containerapp/containerapp.yaml: https://github.com/upbound/provider-azure/actions/runs/6694618936
examples/automation/hybridrunbookworkergroup.yaml: https://github.com/upbound/provider-azure/actions/runs/6694659454
examples/web/linuxwebapp.yaml: https://github.com/upbound/provider-azure/actions/runs/6694706218
examples/cdn/endpoint.yaml: https://github.com/upbound/provider-azure/actions/runs/6694734728
examples/databoxedge/device.yaml: https://github.com/upbound/provider-azure/actions/runs/6694763539
examples/logic/appworkflow.yaml: https://github.com/upbound/provider-azure/actions/runs/6694821041
examples/storage/tableentity.yaml: https://github.com/upbound/provider-azure/actions/runs/6694856344
examples/servicebus/topic.yaml: https://github.com/upbound/provider-azure/actions/runs/6695380326
examples/relay/eventrelaynamespace.yaml: https://github.com/upbound/provider-azure/actions/runs/6694957500
examples/loadtestservice/loadtest.yaml: https://github.com/upbound/provider-azure/actions/runs/6694978639
examples/keyvault/key.yaml: https://github.com/upbound/provider-azure/actions/runs/6695984231

/test-examples="examples/azure/resourcegroup.yaml"

/test-examples="examples/containerapp/containerapp.yaml"

/test-examples="examples/automation/hybridrunbookworkergroup.yaml"

/test-examples="examples/web/linuxwebapp.yaml"

/test-examples="examples/logic/appworkflow.yaml"

/test-examples="examples/storage/tableentity.yaml"

/test-examples="examples/servicebus/topic.yaml"

/test-examples="examples/relay/eventrelaynamespace.yaml"

/test-examples="examples/loadtestservice/loadtest.yaml"

/test-examples="examples/keyvault/key.yaml"

/test-examples="examples/keyvault/key.yaml"

/test-examples="examples/dbformariadb/virtualnetworkrule.yaml"

/test-examples="examples/dbforpostgresql/virtualnetworkrule.yaml"


ManageIQ Orchestrator image issue

Hi,
I'm trying to upgrade from Murphy Appliance to Oparin k8s. After installing Oparin on a fresh k8s 1.26, and restoring old PG database, operator pod starts successfully, but all the autogenerated deployments cannot start due to incorrectly set image:
1-generic-7f456fb8d8-9b9kj                                    0/1     InvalidImageName    0          7s
1-generic-7f456fb8d8-prglr                                    0/1     InvalidImageName    0          7s
1-priority-55fc744578-92w2h                                   0/1     InvalidImageName    0          7s
1-priority-55fc744578-lj6n5                                   0/1     InvalidImageName    0          6s
1-schedule-758987d86-5psbs                                    0/1     InvalidImageName    0          6s
2-ansible-tower-automation-event-catcher-4-5bb4d59df6-6c87g   0/1     InvalidImageName    0          29s
2-ansible-tower-automation-refresh-4-5778799785-t9g75         0/1     InvalidImageName    0          24s
2-ems-metrics-processor-5877d4f85f-2f4pj                      0/1     InvalidImageName    0          23s
2-ems-metrics-processor-5877d4f85f-rtdmg                      0/1     InvalidImageName    0          23s
2-event-handler-78c6785f48-skppj                              0/1     InvalidImageName    0          23s
2-generic-88d758945-52ndf                                     0/1     InvalidImageName    0          22s
2-generic-88d758945-lrrx8                                     0/1     InvalidImageName    0          23s
2-priority-64dfb5cff7-6qvvf                                   0/1     InvalidImageName    0          22s
2-priority-64dfb5cff7-g7zd7                                   0/1     InvalidImageName    0          22s
2-remote-console-6c9bc5d6d9-hf49d                             0/1     Running             0          21s
2-reporting-85cd8b8bcc-srr55                                  0/1     InvalidImageName    0          22s
2-reporting-85cd8b8bcc-x2x9j                                  0/1     InvalidImageName    0          21s
2-schedule-cddf844f-9sf7t                                     0/1     InvalidImageName    0          21s
2-ui-7ccbb486bf-6q8tp                                         0/1     ContainerCreating   0          20s
2-ui-7ccbb486bf-jzcnz                                         0/1     Running             0          20s
2-web-service-b58f686ff-c8pl9                                 0/1     Running             0          20s
httpd-84b9958c84-nx2sz                                        1/1     Running             0          51m
manageiq-operator-7b87f87db6-d4cpf                            1/1     Running             0          51m
memcached-787c4698bf-28b2s                                    1/1     Running             0          51m
orchestrator-5cc99d88b9-j7v5h                                 1/1     Running             0          2m5s
postgresql-666cdcbb78-sfpkw                                   1/1     Running             0          51m

the image for them looks like this:
artifactory.my.local/manageiq-base-worker:17011/manageiq/manageiq-orchestrator
Probably it is related to env variables set in orchestrator deployment:
CONTAINER_IMAGE_NAMESPACE:  artifactory.my.local
CONTAINER_IMAGE_TAG:        17011/manageiq/manageiq-orchestrator

but orchestrator itself takes correct image address given in CR:
orchestratorImage: artifactory.my.local:17011/manageiq/manageiq-orchestrator:oparin-1.1
How to apply correct image for autogenerated pods?

Did you set the GUID in the CR to the same GUID from the appliance?

artifactory.my.local is wrong (unless that's your artifactory instance.  @bdunne @nasark can you look here?

Sure, it's an internal repo.
spec:
  appName: manageiq
  applicationDomain: manageiq.my.local
  backupLabelName: manageiq.org/backup
  databaseRegion: "0"
  databaseSecret: postgresql-secrets
  databaseVolumeCapacity: 15Gi
  deployMessagingService: false
  enableApplicationLocalLogin: true
  enableSSO: false
  enforceWorkerResourceConstraints: false
  httpdAuthenticationType: internal
  httpdImage: artifactory.my.local:17011/manageiq/httpd:latest_01242024
  kafkaImage: artifactory.my.local:17011/manageiq/kafka:latest_01242024
  kafkaVolumeCapacity: 2Gi
  memcachedImage: artifactory.my.local:17011/manageiq/memcached:1.6
  memcachedMaxConnection: "1024"
  memcachedMaxMemory: "64"
  memcachedSlabPageSize: 1m
  migrationsRan:
  - "20210503163000"
  - "20210504113000"
  orchestratorImage: artifactory.my.local:17011/manageiq/manageiq-orchestrator:oparin-1.1
  orchestratorInitialDelay: "480"
  postgresqlImage: artifactory.my.local:17011/manageiq/postgresql:13
  postgresqlMaxConnections: "1000"
  postgresqlSharedBuffers: 1GB
  serverGuid: bd87dfc5-8066-4f07-b0cb-9105965c8b0a
  uiWorkerImage: artifactory.my.local:17011/manageiq/manageiq-ui-worker:oparin-1.1
  webserverWorkerImage: artifactory.my.local:17011/manageiq/manageiq-base-worker:oparin-1.1
  zookeeperImage: artifactory.my.local:17011/manageiq/zookeeper:latest_01242024
  zookeeperVolumeCapacity: 1Gi

Ok, so we are clearly not handling the port in the image name, and instead see the : as the image tag separator.  @bdunne This looks like a clear bug to me.  Please take a look.


Entry Point Not Found

Good afternoon,
I have just downloaded OpenFAST v2.5.0 from the openfast/releases. I downloaded the precompiled binaries zip. I saw the issues regarding missing .dlls and downloaded the 2017 redistribution libraries as recommended in Issue #352.
However, now when I try to run openfast_x64.exe, I get the error:
"The procedure entry point for_stop_core_quiet could not be located in the dynamic link library" then it gives the path where my openfast_x64.exe is and that is the end of the message. I have included a picture of the error message below:

Is this because the redistribution libraries are not at the same location as the executable?
As a bit of extra information I have been using OpenFAST v1.0.0 with no issues.
Thanks in advance,
Bruce

Hi Bruce,
We recently upgraded to a newer Intel compiler suite for building the precompiled Windows executables of OpenFAST.  These require a newer version of the redistributable.
@rafmudaf, can you suggest which redistributable is now required?  I can test it later for you.
Cheers,
Andy

Hi Bruce,
We recently upgraded to a newer Intel compiler suite for building the precompiled Windows executables of OpenFAST.  These require a newer version of the redistributable.
@rafmudaf, can you suggest which redistributable is now required?  I can test it later for you.
Cheers,
Andy

Hi Andy,
Thank you for the tip, I downloaded the 2020 redistributable libraries and it seems to be working now. Can you or rafmudaf please confirm that I am correct and that these are the redistributables that OpenFAST v2.5.0 needs?
Thanks,
Bruce

Hi Andy,
Thank you for the tip, I downloaded the 2020 redistributable libraries and it seems to be working now. Can you or rafmudaf please confirm that I am correct and that these are the redistributables that OpenFAST v2.5.0 needs?
Thanks,
Bruce

I'm having trouble installing that package on my Windows computer due to inadequate admin rights. @andrew-platt could you try on your virtual machine?
Otherwise, @Bruce-Cavanagh I suspect that version is correct. I used the Intel Fortran classic compiler that came with the new oneAPI installation, and I believe that corresponds to ifort 19 2020.

I'm having trouble installing that package on my Windows computer due to inadequate admin rights. @andrew-platt could you try on your virtual machine?
Otherwise, @Bruce-Cavanagh I suspect that version is correct. I used the Intel Fortran classic compiler that came with the new oneAPI installation, and I believe that corresponds to ifort 19 2020.

Just tested. The 2020 redistributable corrects the issue.  Should we post a link to that in the release notes?

Just tested. The 2020 redistributable corrects the issue.  Should we post a link to that in the release notes?

I've added the link to the release. Thanks @andrew-platt and @Bruce-Cavanagh.

I've added the link to the release. Thanks @andrew-platt and @Bruce-Cavanagh.

Thank you for your assistance.

Thank you for your assistance.

Good evening,
I have a similar problem as the one mentioned in this post. When I try to run OpenFAST from an Anaconda 3 command prompt, I get the error "The procedure entry point for_stop_core_quiet could not be located in the dynamic link library". Running OpenFAST from a normal command prompt works fine. I am working on a Windows 10 computer and work with precompiled OpenFAST  v2.5.0 binaries and redistributables for the 2020 Intel Fortran compiler (as mentioned in the release notes). What could be the cause of this problem and how can I solve it?
Thank you in advance!
Christophe

It sounds like the Anaconda prompt isn't locating the Intel redistributable libraries. @bjonkman do you have any insight?

It could be a path issue, I'm not sure if that would help, but you can try to compare the content of the %PATH% environment variable in both the usual terminal and the conda terminal. Maybe the anaconda prompt doesn't have the path to the redistributables. You can look at the path using:
 echo %PATH%

or to split by new lines
  python -c "import os; print(os.environ['PATH'].replace(';', '\n'));"

It could also be that anaconda provides some similar libraries, and shadows the redistributables path since it will put its own path first.  You can try to prepend the path of the dlls:  set path="C:\PATH\TO\REDISTRIBUTABLES;%path%" . A last resort is to put the dlls next to you executable, or have everything (folder+exe) in a folder that is always in your path.

Dear ebranlard,
Thank you for your solution! I ended up implementing the last resort solution and I put the dlls next to the executable. Now it works fine.

I'm having trouble installing that package on my Windows computer due to inadequate admin rights. @andrew-platt could you try on your virtual machine?
Otherwise, @Bruce-Cavanagh I suspect that version is correct. I used the Intel Fortran classic compiler that came with the new oneAPI installation, and I believe that corresponds to ifort 19 2020.

Hi rafmudaf,
Recently I'm also having this trouble as Intel no longer supports the Parallel Studio XE for Fortran compiler. My student license expired a couple of days ago and I have to install the oneAPI. It can build my program with no error. However, the issue same as Bruce's occurred when I executed the program. I followed Andy and Bruce's suggestion and installed the new redistributable libraries vc_redist.x64.exe. It does not help. The problem is still there.
Do you have any other suggestions or hints that might direct me to the right track?
Thanks,
Chaoxian

You should install the Intel redistributables not the Visual Studio redistributables. The link to the appropriate package corresponding to the latest release is included in the release notes.

You should install the Intel redistributables not the Visual Studio redistributables. The link to the appropriate package corresponding to the latest release is included in the release notes.
https://github.com/OpenFAST/openfast/releases/tag/v2.5.0

Hi rafmudaf,
Thanks for your kind reply. I followed your suggestion and installed the Intel redistributable. However, the problem is still there. I read their installation instruction and found something did not happen during my installation.
The installation creates a new env-var "INTEL_DEV_REDIST" with the value of above installation directory, and the PATH env-var is updated with [INTEL_DEV_REDIST]\redist[ia32|intel64]\compiler and [INTEL_DEV_REDIST]\redist[ia32|intel64]\mpirt (for Fortran packages). The "redist\intel64" directory is added only on 64-bit systems.
However, I did not found this new env-var on my computer. Could you please take a look at the computer on your end and see if you can find this new env-var after installing the Intel redistributables?
Very much appreciate it,
Chaoxian

Did you restart your command prompt?

Did you restart your command prompt?

Yes. I just realized that the new env_var is already there. I misunderstood the 'INTEL_DEV_REDIST'. I thought the name is 'INTEL_DEV_REDIST'. Actually, it is 'redist'. I did see the changes in the path 'Common Files\Intel\Shared Libraries\redist\intel64_win\compiler\1041'. But it seems that it doesn't work when I executed the program.

@Imcxqi : are you having trouble running the executable that you built (with Intel Parallel Studio? or oneAPI?) or the executable from the OpenFAST GitHub Releases page?

@Imcxqi : are you having trouble running the executable that you built (with Intel Parallel Studio? or oneAPI?) or the executable from the OpenFAST GitHub Releases page?

I am having trouble running the executable file that I built with oneAPI. The problem is '' The procedure entry point for_stop_core_quiet could not be located in the dynamic link library"

Can you open the Intel compiler command prompt and run the code from there? If you built the code on the computer you are using, the libraries should already be installed without using the redistributable package, but you have to make sure they are on the path (i.e., run it from the Intel compiler command prompt window). I don't have oneAPI, but you should be able to find the Intel compiler command prompt from your start menu, something like this: Start->Intel oneAPI->compiler 2021 for x64 Visual Studio XXXX environment (or win32 if that's what you used to build the code).
Otherwise, you may need to make sure you've got the right redistributable for the compiler(s) you installed (see https://software.intel.com/content/www/us/en/develop/articles/oneapi-standalone-components.html)

Can you open the Intel compiler command prompt and run the code from there? If you built the code on the computer you are using, the libraries should already be installed without using the redistributable package, but you have to make sure they are on the path (i.e., run it from the Intel compiler command prompt window). I don't have oneAPI, but you should be able to find the Intel compiler command prompt from your start menu, something like this: Start->Intel oneAPI->compiler 2021 for x64 Visual Studio XXXX environment (or win32 if that's what you used to build the code).
Otherwise, you may need to make sure you've got the right redistributable for the compiler(s) you installed (see https://software.intel.com/content/www/us/en/develop/articles/oneapi-standalone-components.html)

Thanks for your kind reply. I did test it as you suggested. It has the same problem as I run the exe in the system prompt. I totally agree with you that there might be something wrong with the library path. It shows the 'for_stop_core_quiet' cannot be located. It seems that the program cannot find the DLL related to 'for_stop_core_quiet' when it is executed.

Did you build this executable using CMake or the Visual Studio solution file in <openfast>/vs-build/FAST/FAST.sln? The Visual Studio build should be set to use static libraries, in which case you shouldn't need the redistributable libraries.

Hi guys,
I just solved the problem by following the suggestion in Intel Fortran Compiler Community under the topic.
_Go to  Intel® oneAPI standalone component installation files
Select Runtime Versions > Windows > Intel Fortran Compiler Classic for Windows
Download and install that._
Thanks for your kind help! Hope you doing well.


Optimization of MPI layer

Original author: Nikhil Jain
Original issue: https://charm.cs.illinois.edu/redmine/issues/23

Revisit MPI layer and possibly rewrite to improve performance.

Original date: 2013-02-06 06:29:03

I've heard through the grapevine (not to be confused with Harshitha's LB strategy) that Ralf has achieved near-parity with some native layer in his work at Argonne for Pavan. Marking it 'in-progress' accordingly.

Original author: Nikhil Jain
Original date: 2013-02-11 22:24:31

Quoting Ralf's Email on this-
As for MPI, we've found something that apparently makes it be as fast as gemini_gni-crayxe, and the same seems to be true of ibverbs. We're testing this on intrepid & vesta as well. Pavan doesn't care about tcp (i.e. MPI over sockets) at all, where the difference in performance is biggest (almost 4x).

Original date: 2017-01-17 03:29:53

It looks like none of the work mentioned above was ever merged...

Original date: 2018-04-29 22:45:56

Small optimization to use MPI-3's MPI_Mprobe and MPI_Mrecv where possible: ~~https://charm.cs.illinois.edu/gerrit/#/c/charm/+/2785/~~ https://github.com/UIUC-PPL/charm/commit/f7fbaaaae1088ee65988c1345203da3ed55abcc4
Edit: we ended up reverting this because support for MPI_Mprobe is spotty and not really detectable at configure time in a portable manner.


LinkedIn Authentication

Is there any plan to implement a LinkedIn authentication namespace to allow authorisation against LinkedIn credentials?
Adam

No, but there's a comunity implementation available here:
https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers/tree/dev/src/AspNet.Security.OAuth.LinkedIn


Use depricated link in Product list

In following page:
https://eclipse-tractusx.github.io/community/products/
Trace-X description have this link:
https://github.com/eclipse-tractusx/traceability-foss-backend
But repositoy haven't been having update more than 1 year.
Currently, following repository seems used as development repository.
https://github.com/eclipse-tractusx/traceability-foss
Please update Trace-X repository link.

HI @okamototk,
thanks for spotting. You are right, the data used to render the product overview does not seem to be actively updated by the teams. I fixed the Trace-X link in #851
@danielmiehle, @Siegfriedk @stephanbcbauer: I think this shows, that we either need to automate this, find dedicated maintainers, or remove the product overview, if we cannot keep it up to date. What do you think?
Automation could be done via release dashboard. There, we are anyways reading product metadata. Maybe we should open a discussion for that topic

@SebastianBezold weird anyway that the page exists as it does; Who decided on the products?!

@SebastianBezold weird anyway that the page exists as it does; Who decided on the products?!

Not really sure. @maximilianong, do you have background info in that. I only moved the page ones as we created the "Community" top-level nav. Cannot remember, where I moved it from and who created the initial data

Its beed a while. I think this page was a requirement that got initiated in combination with the release management but Im not sure. @danielmiehle has the background info here. Lets wait for his feedback what to do with the page :) But anyway, thanks @SebastianBezold for fixing!

We initially created the products based on the products in the consortium. If there are any changes or another bundling of the repos makes more sense, we are happy to adapt the page.

Ok so background seems to be clear. I think the problem is, that no one feels responsible for keeping this up to date. So from my point of view we could either get rid of the products overview, since misleading info can be worse than none (we still have the TRG checks dashboard with a product list), or automate the whole info gathering.


"symbol not found" on alpine 3.19

On the latest ruby image with alpine 3.19, I can install sqlite3 ruby gem, but it emits "symbol not found" errors at runtime.
This is a quick test on alpine 3.18:
$ docker run --rm -it ruby:3.2.2-alpine3.18 /bin/sh
/ # gem install sqlite3
Fetching sqlite3-1.6.9-x86_64-linux.gem
Successfully installed sqlite3-1.6.9-x86_64-linux
1 gem installed

A new release of RubyGems is available: 3.4.10 → 3.4.22!
Run `gem update --system 3.4.22` to update your installation.

/ # ruby -rsqlite3 -e 'puts SQLite3::SQLITE_LOADED_VERSION'
3.44.2
/ #

And here's the same on 3.19:
$ docker run --rm -it ruby:3.2.2-alpine3.19 /bin/sh
/ # gem install sqlite3
Fetching sqlite3-1.6.9-x86_64-linux.gem
Successfully installed sqlite3-1.6.9-x86_64-linux
1 gem installed

A new release of RubyGems is available: 3.4.10 → 3.4.22!
Run `gem update --system 3.4.22` to update your installation.

/ # ruby -rsqlite3 -e 'puts SQLite3::SQLITE_LOADED_VERSION'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3.rb:6:in `rescue in <top (required)>'
	from /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3.rb:2:in `<top (required)>'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `rescue in require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:39:in `require'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require': Error relocating /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/3.2/sqlite3_native.so: posix_fallocate64: symbol not found - /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3/3.2/sqlite3_native.so (LoadError)
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from /usr/local/bundle/gems/sqlite3-1.6.9-x86_64-linux/lib/sqlite3.rb:4:in `<top (required)>'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `rescue in require'
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:39:in `require'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- sqlite3 (LoadError)
	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/ #

I'm not sure if this is the gem or the docker image causing the issue here.

Similar report just came in #435, too.
I believe something changed in the alpine image, since we test alpine in the CI pipeline and it passed last week, but started failing yesterday with the new image

pass https://github.com/sparklemotion/sqlite3-ruby/actions/runs/7111900210/job/19361046596
fail https://github.com/sparklemotion/sqlite3-ruby/actions/runs/7163242730/job/19501550558#step:6:117

Will investigate. In the meantime, a workaround is to use ruby:3-alpine3.18

I copied /lib/ld-musl-x86_64.so.1 from ruby:3-alpine3.18 Docker image and that seems to fix the problem, so it would appear that the problem is related to some change in Musl libc or how Musl is compiled.
By looking the exported symbols from the library (e.g., readelf -Ws --dyn-syms /lib/ld-musl-x86_64.so.1 | grep posix_fallocate64) I've confirmed that the symbol posix_fallocate64 is present in the previous version but missing in the new version. I'm not sure yet if this was intended or if it was an oversight. I'll try to dig more.

Just a note: the symbol missing for the user in #435 is fcntl64, where the one reported missing in this issue is posix_fallocate64.

OK, it seems this was an intentional breaking change in Musl 1.24:

On the API level, the legacy "LFS64" ("large file support") interfaces, which were provided by macros remapping them to their standard names (#define stat64 stat and similar) have been deprecated and are no longer provided under the _GNU_SOURCE feature profile, only under explicit _LARGEFILE64_SOURCE. The latter will also be removed in a future version. Builds broken by this change can be fixed short-term by adding -D_LARGEFILE64_SOURCE to CFLAGS, but should be fixed to use the standard interfaces.

So if I understood correctly, functions with the 64 suffix were dropped and the correct fix is to use the unsuffixed versions instead.
Here are examples of other projects that were also affected by this:

https://github.com/rust-lang/rust/issues/111285
https://gitlab.alpinelinux.org/alpine/aports/-/issues/15151

@pdfrod Thank you so much for doing this research! I should have time tomorrow to investigate if I can work around this in the native (precompiled) gems.

I'm not sure there's a fix for this other than for rake-compiler-dock to support generating native musl-specific gems. Upstream issue is https://github.com/rake-compiler/rake-compiler-dock/issues/75

Thanks for looking into this; I did wonder if it was upstream.
I'll pin to alpine-3.18 for now.

I've updated the issue description with a TLDR summary of the workarounds.

Confirm a breaking change in the Alpine image. I redeployed the same app with no change to the Gemfile or Dockerfile and now receive this error:
[info] /usr/local/bundle/gems/sqlite3-1.7.0-x86_64-linux/lib/sqlite3.rb:6:in `require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
[info] Did you mean? sqlite3/3.3/sqlite3_native
[info] sqlite3/3.2/sqlite3_native
[info] sqlite3/3.1/sqlite3_native
[info] sqlite3/3.0/sqlite3_native
[info] from /usr/local/bundle/gems/sqlite3-1.7.0-x86_64-linux/lib/sqlite3.rb:6:in `rescue in <top (required)>'
...

And that this diff got my deploy working again:
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,4 +1,4 @@
-FROM ruby:3.2.2-alpine AS base
+FROM ruby:3.2.2-alpine3.18 AS base

( :wave:  :wave: Hi Mike)

Confirm a breaking change in the Alpine image. I redeployed the same app with no change to the Gemfile or Dockerfile and now receive this error:
[info] /usr/local/bundle/gems/sqlite3-1.7.0-x86_64-linux/lib/sqlite3.rb:6:in `require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
[info] Did you mean? sqlite3/3.3/sqlite3_native
[info] sqlite3/3.2/sqlite3_native
[info] sqlite3/3.1/sqlite3_native
[info] sqlite3/3.0/sqlite3_native
[info] from /usr/local/bundle/gems/sqlite3-1.7.0-x86_64-linux/lib/sqlite3.rb:6:in `rescue in <top (required)>'
...

And that this diff got my deploy working again:
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,4 +1,4 @@
-FROM ruby:3.2.2-alpine AS base
+FROM ruby:3.2.2-alpine3.18 AS base

( :wave:  :wave: Hi Mike)

Please follow #442 for the fix-in-progess for this issue.


Labels for "Streams" and "Notifications" in settings page have  switched places

Thanks for the report. A fix has been pushed and will be published as soon as possible.


[Question] Any way to get the raw token output from the model?

I read through the documentation and it seems the model is compiled with a specific chat template.
My chat template is more dynamic, is there any way to get the raw token outputs after inference so I can implement my own logic?
For example, my "roles" in the chat template changes dynamically on each message. Additionally, there are specific logic such as guidance I would like to implement on token output.

i think this is what you're looking for:
https://github.com/mlc-ai/notebooks/blob/main/mlc-llm/tutorial_raw_text_generation.ipynb

we are moving towarda a fully OAI compatble API, which hopefully allows some customizations in systems . You can use LM chat template which is mostly raw


Mac OS - No Noteskins Available error when launched

What you were doing before it crashed and what action made the game to crash.

On Mac OS.
I downloaded the DMG, copied all the files to the Applications folder.
Where I launch the application, I get an error message that says "No Noteskins available."

Upload the crashinfo.txt (GameFolder/crashinfo.txt)

None generated

Upload the info.txt and log.txt (GameFolder/Logs)

None generated.
Explain how we can reproduce the error
On Mac OS.
I downloaded the DMG, copied all the files to the Applications folder.
Where I launch the application, I get an error message that says "No Noteskins available."
Sreenshots/Videos

Additional information
The file folders are in the same folder as the app. Not sure if it needs to be in a different folder.

https://wiki.projectmoon.dance/books/stepmania-user-guide/page/troubleshooting
Go down to MacOS Related Issues

Thanks. That did the trick. For reference, a link to that wiki does not appear anywhere on the main website. I would suggest linking to that page under in the Notices section on the Downloads page.