Authentication Token Failures on Entra Joined Autopilot devices causing build failures

Describe the bug
When performing Pre-Provisioning Autopilot/Entra Joined only provisioning, the Web Sign-in Icon is missing from the first Windows Logon screen.
Log Name:      Microsoft-Windows-AAD/Operational
Source:        Microsoft-Windows-AAD
Date:          5/28/2024 9:13:33 AM
Event ID:      1098
Task Category: AadTokenBrokerPlugin Operation
Level:         Error
Keywords:      Operational,Error
User:          DIR\azin.wright
Computer:      AP1A42914607213
Description:
Error: 0xCAA20002 The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.
Code: invalid_request
Description: AADSTS65002: Consent between first party application '3a4d129e-7f50-4e0d-a7fd-033add0a29f4' and first party resource '00000003-0000-0000-c000-000000000000' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens for that API. Trace ID: 7c201ba4-5f0a-4e02-a138-4248b792cc00 Correlation ID: 312125d7-f186-49a7-a147-f48e60ebffe1 Timestamp: 2024-05-28 14:13:33Z
TokenEndpoint: https://login.microsoftonline.com/common/oauth2/token
Logged at OAuthTokenRequestBase.cpp, line: 452, method: OAuthTokenRequestBase::ProcessOAuthResponse.
Request: authority: https://login.microsoftonline.com/common, client: 3a4d129e-7f50-4e0d-a7fd-033add0a29f4, redirect URI: ms-appx-web://Microsoft.AAD.BrokerPlugin/3a4d129e-7f50-4e0d-a7fd-033add0a29f4, resource: 00000003-0000-0000-c000-000000000000, correlation ID (request): 312125d7-f186-49a7-a147-f48e60ebffe1
Event Xml:
](http://schemas.microsoft.com/win/2004/08/events/event">)

1098
0
2
103
0
0x4000000000000012

2637

Microsoft-Windows-AAD/Operational
AP1A42914607213

3399614466
The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.
Code: invalid_request
Description: AADSTS65002: Consent between first party application '3a4d129e-7f50-4e0d-a7fd-033add0a29f4' and first party resource '00000003-0000-0000-c000-000000000000' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens for that API. Trace ID: 7c201ba4-5f0a-4e02-a138-4248b792cc00 Correlation ID: 312125d7-f186-49a7-a147-f48e60ebffe1 Timestamp: 2024-05-28 14:13:33Z
TokenEndpoint: https://login.microsoftonline.com/common/oauth2/token
Logged at OAuthTokenRequestBase.cpp, line: 452, method: OAuthTokenRequestBase::ProcessOAuthResponse.
Request: authority: https://login.microsoftonline.com/common, client: 3a4d129e-7f50-4e0d-a7fd-033add0a29f4, redirect URI: ms-appx-web://Microsoft.AAD.BrokerPlugin/3a4d129e-7f50-4e0d-a7fd-033add0a29f4, resource: 00000003-0000-0000-c000-000000000000, correlation ID (request): 312125d7-f186-49a7-a147-f48e60ebffe1

Related command
First Windows Login with a Passwordless User performing post-Technician part of the user-flow. It seems a local login fixes the issue, then the organizational user can perform a web sign in.
Errors
Error: 0xCAA20002 The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.
Code: invalid_request - Web Sign in is missing from the Windows Login page.
Issue script & Debug output
NGC logs have been collected.
Expected behavior
The web Sign in icon should be presented.
Environment Summary
Web Sign in icon should be presented, and a web sign-in method should be able to be followed to logon to windows the first time.
Additional context
A ticket has been created for Microsoft - Case ID:<PHONE_NUMBER>004430

Thank you for opening this issue, we will look into it.

Any updates on this @yonzhan? We are facing the same issue on a Windows 11 device which is already enrolled in Intune.

May have the same issue but with the "Application Office", how did you solve this?
Error: 0xCAA5001C Token broker operation failed.
Operation name: GetTokenSilently, Error: -895352830 (0xcaa20002), Description: AADSTS65002: Consent between first party application 'e9c51622-460d-4d3d-952d-966a5b1da34c' and first party resource 'f2d19332-a09d-48c8-a53b-c49ae5502dfc' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens for that API. Trace ID: [GUID] Correlation ID: [GUID] Timestamp: [DATE]
Logged at WebAccountProcessor.cpp, line: 680, method: AAD::Core::WebAccountProcessor::ReportOperationError.

https://learn.microsoft.com/en-us/answers/questions/1856430/user-getting-prompted-for-credentials-for-every-ap
https://learn.microsoft.com/en-us/answers/questions/1855739/cannot-enroll-ms365-licenced-users-into-intune-whe

Error: 0xCAA90056 Renew token by the primary refresh token failed.
Logged at RefreshTokenRequest.cpp, line: 150, method: RefreshTokenRequest::AcquireToken.

Request: authority: https://login.microsoftonline.com/common, client: e9c51622-460d-4d3d-952d-966a5b1da34c, redirect URI: ms-appx-web://Microsoft.AAD.BrokerPlugin/e9c51622-460d-4d3d-952d-966a5b1da34c, resource: f2d19332-a09d-48c8-a53b-c49ae5502dfc, correlation ID (request): [GUID]

https://learn.microsoft.com/en-us/answers/questions/1028825/mdm-hybrid-ad-prt
https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current#step-5-collect-logs-and-contact-microsoft-support
https://www.reddit.com/r/Intune/comments/skepvc/how_to_go_from_azure_ad_registered_to_hybrid/?rdt=57873
https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current#step-2-find-the-error-code

Error: 0xCAA20002 The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.
Code: invalid_request
Description: AADSTS65002: Consent between first party application 'e9c51622-460d-4d3d-952d-966a5b1da34c' and first party resource 'f2d19332-a09d-48c8-a53b-c49ae5502dfc' must be configured via preauthorization - applications owned and operated by Microsoft must get approval from the API owner before requesting tokens for that API. Trace ID: [GUID] Correlation ID: [GUID] Timestamp: [DATE]
TokenEndpoint: https://login.microsoftonline.com/common/oauth2/token
Logged at OAuthTokenRequestBase.cpp, line: 452, method: OAuthTokenRequestBase::ProcessOAuthResponse.

Request: authority: https://login.microsoftonline.com/common, client: e9c51622-460d-4d3d-952d-966a5b1da34c, redirect URI: ms-appx-web://Microsoft.AAD.BrokerPlugin/e9c51622-460d-4d3d-952d-966a5b1da34c, resource: f2d19332-a09d-48c8-a53b-c49ae5502dfc, correlation ID (request): [GUID]

https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/authentication/automatic-authentication-fails
https://learn.microsoft.com/en-us/answers/questions/1861206/aad-token-broker-operation-failed
(https://pariswells.com/blog/research/teams-pro-room-device-cannot-connect)

Reference Ticket: #2409181420002854


Updates kubeadm Docs for IPv6 Support

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.9 Features: set Milestone to 1.9 and Base Branch to release-1.9
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: Please check the “Allow edits from maintainers” box (see image below) to
allow reviewers to fix problems on your patch and speed up the review process.

I did not see @mmueen online and I'm unsure how to update someone else's PR, so I created a separate PR that supersedes: https://github.com/kubernetes/website/pull/6465
Fixes: https://github.com/kubernetes/kubernetes/issues/53824
Supports: https://github.com/kubernetes/features/issues/508
cc: @luxas @zacharysarah

This change is

@danehans 👋 Thanks for opening this--#6465 just merged, so we can go ahead and close this one. I appreciate the thought!


Some models display wrong in their x or z directions

Specially the spore plant from opposing force shows up in the editor facing one way but ingame it faces the other. This one is inverted in the Y axis I think but needs confirmation.
Then, most weapons rotate inverted in their X axis if i'm not mistaken. If you want ingame your gun to have 20 0 0  then you must do that in the editor but to calculate the rotation visually in the editor you have to use the negative -20 0 0 to see how it really will be ingame.

It may depend on different models you have in different folders where BSPGuy look for them. Or, if it's a problem of negative pitch, you can add this type of entity into list of negative Pitch entities in Rendering setteings.

@GarompaEstomper


[SPARK-48149][INFRA][FOLLOWUP] Use single quotation mark

What changes were proposed in this pull request?
This is a follow-up of

#46407

Why are the changes needed?
To fix the invalid syntax error

https://github.com/apache/spark/actions/runs/8989374763

The workflow is not valid. .github/workflows/build_python.yml (Line: 37, Col: 24): Unexpected symbol: '"pypy3"'.

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this fix, @HyukjinKwon ?

Merged to master.

Thank you!


Nonexistent discount retrieved

Hello!
A lot of times when I use the min_discount parameter on the "search_products" method I experience two issues:

The items retrieved have a lower discount. This can be solved by filtering items manually later
The discount in the "product.prices.price.savings.percentage" field is not present in Amazon. When I visit the product's page, there's no discount or there's a much lower one.

I've tried to access only the IT marketplace.
Here's a test case code snippet:
    min_discount = 70

    products = client.search_products(keywords="pc,usb", min_discount=min_discount, item_count=10)

    for product in products:
        discount = product.prices.price.savings.percentage

        if not discount or discount < min_discount:
            continue

        print("[{}%] {} {}".format(discount, product.title, product.url))
        print(product.info.product_group)
        print("---")

Sometimes Amazon API returns incorrect information, but that's something this wrapper can't change since it only helps managing the information provided by Amazon. I hope Amazon will improve someday it's API results, but for now the only way of getting more reliable information is with web scraping.


E2E Test Report Bug

I have run into an issue with this cucumber formatter where the reports are not reacting to test retries properly. If an integration test fails and is rerun, the report will show one test failed and one test passed rather than one test retried until it passed. This leads to a test coverage issues in my pipeline where the "retried" test is resulting in <100% passing percentage, even though the test is passing.
To give better context to the issue, I have recreated it in a small sample project.
Here is the steps.js
'use strict';

const { Given } = require('@badeball/cypress-cucumber-preprocessor');

let count = 0;
Given('it succeeds the second time', () => {
  count++;
  if (count === 1) {
    cy.log(`Fail on count ${count}`);
    throw new Error('fail on purpose');
  }
  cy.log(`Succeed on count ${count}`);
});

the feature file
Feature: Retry test
  Scenario: Fail first Pass second
    Given it succeeds the second time

This is the package.json
{
  "name": "reportingenv",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "cypress open",
    "headless": "cypress run"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@badeball/cypress-cucumber-preprocessor": "^15.1.5",
    "@bahmutov/cypress-esbuild-preprocessor": "^2.2.0",
    "@deepakvishwakarma/cucumber-json-formatter": "^0.0.3",
    "cypress": "^12.8.1",
    "cypress-xpath": "^2.0.1"
  },
  "cypress-cucumber-preprocessor": {
    "nonGlobalStepDefinitions": true,
    "stepDefinitions": [
      "cypress/integration/**/*.js"
    ],
    "filterSpecs": true,
    "omitFiltered": true,
    "json": {
      "enabled": true,
      "output": "reports/cucumber-report.json",
      "formatter": "node",
      "args": [
<EMAIL_ADDRESS>      ]
    }
  }
}

For the cypress-cucumber-preprocessor, I attempted both the displayed formatter settings and with the formatter set directly as<EMAIL_ADDRESS>This is the cypress.config.js
const { defineConfig } = require("cypress");
const createBundler = require("@bahmutov/cypress-esbuild-preprocessor");
const { addCucumberPreprocessorPlugin } = require("@badeball/cypress-cucumber-preprocessor");
const {createEsbuildPlugin} = require("@badeball/cypress-cucumber-preprocessor/esbuild");

module.exports = defineConfig({
  e2e: {
    retries: 2,
    specPattern: "**/*.feature",
    async setupNodeEvents(
      on,
      config
    ){
      // This is required for the preprocessor to be able to generate JSON reports after each run, and more,
      await addCucumberPreprocessorPlugin(on, config);

      on(
        "file:preprocessor",
        createBundler({
          plugins: [createEsbuildPlugin(config)],
        })
      );

      // Make sure to return the config object as it might have been modified by the plugin.
      return config;
    },
  },
});

Here we can see the configuration is set to retry any failing test.
This is the resulting cucumber-report.json
[
  {
    "description": "",
    "elements": [
      {
        "description": "",
        "id": "retry-test;fail-first-pass-second",
        "keyword": "Scenario",
        "line": 2,
        "name": "Fail first Pass second",
        "steps": [
          {
            "keyword": "Given ",
            "line": 3,
            "name": "it succeeds the second time",
            "result": {
              "status": "failed",
              "error_message": "fail on purpose"
            },
            "match": {
              "location": "not available:0"
            },
            "embeddings": [
              {
                "data": "(omitted random data)",
                "mime_type": "image/png"
              }
            ]
          }
        ],
        "type": "scenario"
      },
      {
        "description": "",
        "id": "retry-test;fail-first-pass-second",
        "keyword": "Scenario",
        "line": 2,
        "name": "Fail first Pass second",
        "steps": [
          {
            "keyword": "Given ",
            "line": 3,
            "name": "it succeeds the second time",
            "result": {
              "duration": 11000000,
              "status": "passed"
            },
            "match": {
              "location": "not available:0"
            },
            "embeddings": [
              {
                "data": "(omitted garbage data)",
                "mime_type": "image/png"
              }
            ]
          }
        ],
        "type": "scenario"
      }
    ],
    "id": "retry-test",
    "keyword": "Feature",
    "line": 1,
    "name": "Retry test",
    "uri": "cypress/integration/retry.feature"
  }
]

As you can see the report shows 2 tests with the same id, with the first failing and the second succeeding. This shows the test is retrying as expected, but it appearing as 2 individual tests.
 It then creates a second test (the retry) and succeeds on the second attempt as expected. Unfortunately, to the reporter this shows up as 2 separate tests, leading to the passing percentage issue described at the top.

Issue was resolved through @badeball/cypress-cucumber-preprocessor v16.0.0 release


Add CF statuses to docs for searchability

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Add CF statuses to docs for searchability


:attr="false" removes the attr in Vue3

Vue version
3.2.47
Link to minimal reproduction
https://sfc.vuejs.org/#eNp9jtFOwzAMRX8l8vOaSICEVBU0/iMv3Wog0CSW7YyHqf+OOxAam7S33HMdHx/hhcgfGkIPg+w5kTpBbfQcyxB+gD0tKGaaR0VLzg2pUFPXT0nG3YzTU4TXcRaMcPr3NwsbSJkqa5dH8h9Si3mO64b4W0iE3p3IyuyQNUd4VyXpQ2iFPt/8vuawtS5wK5oydlPN23t/5x8eg52g59yj5G7H9UuQzRhhc7Y8GDwgd4xlQka+KbuY/Se86K6kq3OJZYHlG+CGeuk=
Steps to reproduce

Create an input element with :disabled attribute.
pass boolean value false to the :disabled attribute.
Contrary to the documentation, it removes the disabled attribute from the element. It behaves like Vue2.

What is expected?
it does not removes the attribute when the passed value is false as the documentation says.
What is actually happening?
It removes the attribute even if the passed value is false.
System Info
System:
    OS: macOS 13.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 33.85 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.0 - ~/.nodebrew/current/bin/node
    Yarn: 1.22.19 - ~/.nodebrew/current/bin/yarn
    npm: 8.19.3 - ~/.nodebrew/current/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Chrome Canary: 112.0.5598.0
    Edge: 110.0.1587.41
    Firefox: 109.0
    Safari: 16.2
  npmPackages:
    vue: ^3.2.45 => 3.2.47

Any additional comments?
No response

disabled is a known boolean attribute for <input>. The breaking change described in the docs only affects non-boolean attributes.

Coercion for boolean attributes is left untouched.

Thanks @Justineo, this description  may be somewhat misleading.


Typo

Link to article:
https://docs.microsoft.com/en-us/sql/t-sql/data-types/time-transact-sql?view=sql-server-2017
Problem:
Minor typo but it made me stop and wonder:
"hh is two digits, ranging from 0 to 14, that represent the number of hours in the time zone offset."

This has been fixed. Closing.


Update Allstar to close issues when action: "fix"

Related to #159
Currently, this experience is possible:

Action is set to "issue". Allstar runs scans, finds repos out of compliance, and creates Github issues
Action is set to "fix" to automatically fix the failing repos, but the Github issues remain open unless you set action back to "issue" and wait for the scans to re-run

If action is set to "fix", then for a given repo I would like to see this behavior:

On initial scan, issues with repo are automatically fixed
Subsequent scan of the repo closes Github issues, if any

I can't really think of a downside this approach, so I went ahead and implemented it

authored


Functional Component for Calculator App

To create a calculator using functional components in React, These are the steps I took

I started by importing the useState hook from the React library. This hook allows me to manage the state of my application, which is crucial for building a functioning calculator.

Next, I defined the initial state of the calculator as an object with three properties: total, next, and operation. The total property stores the current total of the calculator, the next property stores the next number to be added or subtracted, and the operation property stores the current operator.

To handle button clicks, I defined an handleNumberClick function that takes in the value of the clicked button and calls a calculate function with the current state and button value. The calculate function returns an updated state object, which is used to update the state of the calculator using the setState function.

Finally, I rendered the calculator UI by returning a JSX expression that defines the structure of the calculator and binds the handleNumberClick function to the button click events.

In summary, I used functional components in React to build a calculator by defining an initial state object, using the useState hook to manage state, and defining an handleNumberClick function to handle button clicks. The JSX expression returned by the component defines the UI and binds the handleNumberClick function to the button click events.

Hi @frempongdev,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights
-Great PR description 👍.
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Thank you @Wes-Isaac for approving this issue.

Thank you @Wes-Isaac for approving this issue.


Empty new lines are lost when converting to MD

Hi @inokawa, just wondering if you are aware of this problem:
https://codesandbox.io/s/remark-slate-transformer-bffpe
I'm essentially trying to serialise the AST to markdown and store it as string, but noticed that new lines are lost during the serialisation/deserialisation process.
I noticed that for example other implementations, such as https://github.com/hanford/remark-slate, add some <br> tags to preserve them: https://github.com/hanford/remark-slate/blob/c17259600c1939bd85a338f77e5a3ac8906af767/src/deserialize.ts#L137-L144 🤔

@inokawa is there a solution so fix this?


Fix a timeout issue with broadcast vs incoming data

Fix a problem where a received line is perceived as a broadcast whereas we are receiving an answer. We check for "isIncoming" when branching into a broadcast.

thx 👍


lxd/resources: serial/uuid may not be accessible

Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Unprivileged users can't access any of the uuid or serial fields, so when run as root inside an unprivileged container we were getting failures in /1.0/resources.

For good measure, I've now tested this logic on physical, VM and containers as well as on all architectures we support.
It's coming up a bit light on architectures without ACPI/SMBIOS (so everything except x86_64 and aarch64) but if someone knows how to populate the information on those platforms, we can add that in later.

Testsuite passed


News Website using Vanilla Js  Issue #140

Bulma News Data Api Vanilla JS USed

@Jyo561 Thank you for your contribution. Looking forward to more such amazing contributions 🥂

Thank You


Fix 'The name of the outer type and the file do not match.' issue in 27(Binary trees part-2)\AVL.java

CodeFactor found an issue: The name of the outer type and the file do not match.
It's currently on:
27(Binary trees part-2)\AVL.java:2
Commit 9124ec29ca68b337d39cf29477051211d11d5856

closed


convert PSSM from 3dcons to deeprank

Hello, I try to convert the download pssm files from 3dcons with DeepRank_GNN/deeprank_gnn/tools/pssm_3dcons_to_deeprank.py, but it seem no result files?

Hi @Lsz-20! The script you're referring to is not part of this new version of the repository, but if you provide us with more details (e.g., the PSSM files you're using, how you're running the script, the OS) we can try to help you.


Why not impl Buf::get_array<const N: usize>(&mut self) -> [u8; N]?

The implementation of Buf::get_{number_types} could also be based on it, thus avoiding buf_get_impl!. Are there any other considerations such as MSRV? If not I can provide PR.
By the way, why not put Buf and BufMut into a separate crate? I had basically reimplemented Buf where there is no need for Bytes and forgot that there is an implementation inside this crate.

This is one half of my implementation of a Bytes-like thing for &[u8], mainly referencing impl Read::read_exact for &[u8] in std. Then as the other half, I implemented get_{number_types} in another crate based on BytesRead::read_to_array and then map({number_types}::from_be_bytes).

The MSRV of the bytes crate is too old for const generics, and I don't think we should bump it just for this.
As for moving Buf to another crate, potentially it could happen, but its complicated. See #479 for more.

Seems there is another problem: const generics will let Buf cannot be made into a trait object.
error[E0038]: the trait `Buf` cannot be made into an object
    --> src\buf\buf_impl.rs:1414:30
     |
1414 | fn _assert_trait_object(_b: &dyn Buf) {}
     |                              ^^^^^^^ `Buf` cannot be made into an object
     |
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
    --> src\buf\buf_impl.rs:288:8
     |
76   | pub trait Buf {
     |           --- this trait cannot be made into an object...
...
288  |     fn get_array<const N: usize>(&mut self) -> [u8; N] {
     |        ^^^^^^^^^ ...because method `get_array` has generic type parameters
     = help: consider moving `get_array` to another trait

For more information about this error, try `rustc --explain E0038`.
error: could not compile `bytes` due to previous error


Added getTag() and removeAttributes() and a test for both

I think that in some cases is needed the name of the tag and sometimes psalm/phpstan/others prefer a method over a property for that.
Sometimes you need remove all attributes. Instead a foreach each time the method "removeAttributes" is better
And I added a method delete() that serve as an alias of $this->outertext="";

This change is

Coverage increased (+0.03%) to 63.399% when pulling b6ca1cb495137e89ea911c9532efb5c2db2fab84 on marioquartz:auxiliar_functions into 91500ec3a0ab11556726dac084050bdf23da5ced on voku:master.

Thanks for the improvements, and special thanks for adding some tests. :1st_place_medal:


Fix #160729. Disable workspace md paste handler for notebook.

To make way for the notebook specific paste handler.

This is an ok workaround but I'll revisit this. Ideally the notebook one will be preferred in notebooks but we will let you fall back to the default markdown one too


[WIP] Adding Histogram Vignette

This adds a vignette that demonstrates how to test histograms, addressing issue #149.

For reference, here is a pdf of the vignette.
Testing Histograms — matplotcheck 0.1.0 documentation.pdf

For reference, here is a pdf of the vignette.
Testing Histograms — matplotcheck 0.1.0 documentation.pdf

thank you @ryla5068 it would be nice at the end of the vignette to demonstrate that you can use the basic assert statements to test for x and y axis labels and titles too. will you please add that to the vignette? i'm debating about whether this should be at the top of the bottom. the data part is what is NEW for histograms compared to basic plots. so that could be justification to add this to the BOTTOM in a section that says somethign like:
"You can also test plot x and y axes, and titles on histograms...
 this is really great. thank you so much for pulling this together @ryla5068

also all of CI is broke here. i'll go back to your other PR first to see if it has to do with something over there!

hey @ryla5068 looks like there are still some merge conflicts on this PR. can you please have a look, clean this up so I can review and merge?


Forward experimental Skia for web environment variable to engine

Description
Flutter for Web has an experimental flag for using the Skia engine. It requires the environment variable FLUTTER_WEB_USE_SKIA to be set (source).
Forwarding from tools does not require a custom build of the engine to try this experimental feature.
Related Issues
Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR.
Tests
WIP
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I signed the CLA.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[X] No, this is not a breaking change.

Please try to restart your computer

@jonahwilliams LMK if I should close https://github.com/flutter/flutter/pull/44083 in favor of this PR.

@yjbanov You should keep working on yours (and make it work for all of our dart compilers).

@jonahwilliams is this the approach that should be done?

This seems like a reasonable approach - you should sync up with @yjbanov since he has a fairly similar PR to see if you can pull out some common threads

My only concern is that this option may go away in the future, which is why in my PR I introduced it as part of a hidden option.

Closing in favor of https://github.com/flutter/flutter/pull/44083


Use the generic/ubuntu1604 image.

Compared to the custom "velocity42/xenial64" image, the build process
for "generic/ubuntu1604" is well-documented and reproducible and the
image is regularly updated to match latest security packages and updates
from Ubuntu.
Furthermore, the image is available for more providers, including libvirt
and Hyper-V.

thanks!

Sorry, this PR introduced a huge regression: generic/ubuntu* does not support the vbox guest additions and thus there is no synced directory. The last step of provision.sh copies the build artifact to /vagrant which does not exist. I'm currently evaluating the options here as the guest additions must match the host's version of VirtualBox and this is generally not a very good concept.


client.Repositories.Create doesn't wait until Github repo finishes creation

In our github automation we create a github repo using client.Repositories.Create(ctx, config.GITHUB_ORG, repo) and call ref, _, err := client.Git.GetRef(ctx, config.GITHUB_ORG, repoName, "refs/heads/master") right after to prepare to create a nightly branch from master.  More than half the time we'll get an error because the client.Repositories.Create function returns without waiting for the actual github repo creation to fully finish.
Right now we are putting in a sleep to fix this issue in our automation but that is obviously not a great solution.
Here's the error we receive:
2020/07/24 16:47:37 http: panic serving <IP_ADDRESS>:41894: GET https://api.github.com/repos/<org>/test/git/refs/heads/master: 409 Git Repository is empty. [] reposervice_1  | goroutine 6 [running]: reposervice_1  | net/http.(*conn).serve.func1(0xc0001c86e0) reposervice_1  |        /usr/local/go/src/net/http/server.go:1772 +0x139 reposervice_1  | panic(0x943900, 0xc0002340f0) reposervice_1  |        /usr/local/go/src/runtime/panic.go:973 +0x3e3 reposervice_1  | main.CreateBranch(0xc0000b6000, 0xaccba0, 0xc000028048, 0xc00009c015, 0xa, 0x9ffb7c, 0x6, 0xa00115, 0x7, 0xc000056aa8, ...) reposervice_1  |        /go/src/app/service_github.go:140 +0x42a

Yes, that is correct based on my experience as well.  You basically need to set up a loop with a fixed number of attempts with exponential backoff (e.g. 1, 2, 4, 8, 16, 32 seconds) to query the repo until it is found. Presumably this is due to allowing GitHub to propagate the changes throughout their servers.
You will experience the same thing if you were to use the "curl" equivalent calls directly.
~Closing since this is known behavior on how GitHub operates.~
Feel free to contact<EMAIL_ADDRESS>to see if they will wait to return the response until all changes have been fully propagated throughout their servers.
I'll leave this issue open for awhile in case someone would like to add comments to the RepositoriesService.Create endpoint to explain the situation... or if there is a response from GitHub tech support... but if there is no activity, then I'll close the issue.

@gmlewis I can give a PR to add relevant comment explaining this issue.


Shorten getters and setters of syntax nodes

This makes the Syntax*Nodes.swift more succinct and easier to read

@swift-ci Please test


[Hypersonic] Using pre-exisiting databases with different field names.

Extension – Hypersonic
Author: @prrrcl

Describe the feature and the current behavior/state.
Map date, title and label to another property name for an already existing database in notion
Who will benefit with this feature?
Anyone who doesn't want to/cannot port over their complete todo setup to hypersonic template.
Any Other info.

I don't know how to go about this, but I did modify the extension to have these preferences and be able to attach to custom databases. Is there anyway to have a pull request to submit possible modifications/upgrades to an extension made by someone else?

yes there is @mimansajaiswal, all the extensions are part of this repo and open-source. you can go ahead and add these improvements yourself and create a PR for it.

@prrrcl @igarcido95  I checked out your pull request branch and imported the extension. The filter option and changing property names works perfectly. Thank you.


tvb-gdist & www.thevirtualbrain.org

https://www.thevirtualbrain.org causes

ERROR    https_everywhere.adapter:adapter.py:126 handle_error requests.exceptions.SSLError: HTTPSConnectionPool(host='www.thevirtualbrain.org', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))

But http redirects to https, so we cant downgrade it otherwise there is too many redirects, and causes a timeout on https://ci.appveyor.com/project/jayvdb/pypidb/builds/31795479.
https://github.com/the-virtual-brain/tvb-geodesic/pull/24 already solves this for that package.
The maximum number of redirects should also be reduced.

The patch isnt parsed because the code doesnt support removing URLs.

https://www.thevirtualbrain.org/ needs to be rechecked, so that rule can be removed.


Remaining Balance formula causes writeoffs to be double-counted

Trailhead and PowerOfUs advises users to "change the Opportunity amount from the original pledge to the actual amount you received" when writing off payments (this makes sense, since we don't want rollups to reflect written off amounts). The "Remaining Balance" npe01__Amount_Outstanding__c formula field then subtracts the writeoff amounts AGAIN. The result is that users will end up with a negative Remaining Balance.
Remaining Balance Formula field:

Sample donation record with a writeoff:

Trailhead instructions (see step 5 for writing of payments):
https://trailhead.salesforce.com/en/content/learn/modules/donation-management-basics-with-nonprofit-success-pack/create-or-edit-payments
PowerOfUs (step 6 for Write Off One of More Scheduled Payments):
https://powerofus.force.com/s/article/NPSP-Manage-Multiple-Payment-Donations#ariaid-title4

Hi @mikeD72 - Best place to have a conversation about this functionality is on the Power of Us Hub. Would you mind starting a thread there instead of here? We reserve Github Issues only for replicable and actionable issues for our development team. Thanks for understanding and see you on the Hub!

Hi @mikeD72 - wanted to let you know that I brought this to our documentation team's attention and they're going to get the text updated to no longer recommend editing the Opportunity amount. Instead, I'd advise you to not edit the Opportunity and instead use Customizable Rollups to count payments accurately on Account/Contact records. Post in the Hub if you need assistance with this and thanks for bringing this to our attention.

Hi @judisohn , thanks for looking into this! I would suggest that the current documentation instruction to reduce the opportunity amount by the written off amount is correct. If this is not done, soft credits on Accounts and Contacts will be too large, i.e. they will summarize the collectible and written off amounts instead of just the collectible amount.
I'd be happy to converse on the Power of Us Hub if you think that is a better forum for the time being?

Yes, feel free to continue on the Hub @mikeD72 - I might argue that it's better to create Partial Soft Credit entries in that case?


refactor: deleted redundant lines.

Removed two lines which are re-defining plugins key-value pair that was passed from sharedConfig by spread operator.

LGTM


Create release for week 1

Release for this week: @evelynmoorhouse @SimardeepKaur @vermashivam679
https://github.com/UBC-MDS/hueniversitypy/tree/v0.1.0


distanceToScroll is wildly inaccurate

I've been trying to tweak the scrolling distance using PageScrollConfig.defaultScrollOffset, but the result is very inaccurate.
The larger the distance is, the more accurate it becomes but it always overscrolls. Increasing PageScrollConfig.defaultScrollOffset solves this, but then the shorter distances are very underscrolled.
I can only imagine that for some reason the following code from ng2-page-scroll yields unpredictable results.
let targetScrollTop:number = anchorTarget.offsetTop;
let distanceToScroll:number = targetScrollTop - this.body.scrollTop;

I will try to lookup into some successful jquery plugins, what they do differently.

I reduced to the code a lot so that the scrollTop is simply set without animation or timers and the problem still persists:
  private scrollView(anchor:string):void {
    let anchorTarget:HTMLElement = this.document.getElementById(anchor.substr(1));
    if (anchorTarget !== null) {
      let targetScrollTop:number = anchorTarget.offsetTop;
      let distanceToScroll:number = targetScrollTop - this.body.scrollTop;
      this.body.scrollTop = distanceToScroll - (this.pageScrollOffset === null ? PageScrollConfig.defaultScrollOffset : this.pageScrollOffset);
    }
  }

alright, the following calculation consistently scrolls to the right position:
this.body.scrollTop = anchorTarget.offsetTop - anchorTarget.scrollTop + anchorTarget.clientTop;

I'm going to fork this project to create a lite version that jumps instantly and doesn't attach the event handlers.


Update withdraw claim strategy to only withdraw own winning claims

I believe that without this, the agent will attempt to withdraw any invalid claim that were contested by someone else:
1- Bob makes wrong claim
2- Charles challenges
3- Claim expires and Charles wins
4- Agent (that did not participate so far) tries to withdraw
Also, without the continue in the withdraw if clause, the agent will try to challenge a terminated claim.
The withdraw does not fail, and instead sends the funds to Charles because that's how it is in the contracts, but I don't believe the Agent should do that.
I attempted to write a test and could actually verify the behaviour with logs, but since the withdraw tx does not fail, it's hard to write an effective test.
Idk if we should transition the claim to ignored state, I don't fully understand this.

When a claim is challenged and the actor is not involved the claim is transitioned into the ignored state. See https://github.com/beamer-bridge/beamer/blob/6f22a95e398687ec2703ea4c27905df3136c0bc8/beamer/state_machine.py#L158.
We should rather check whether the claim is in the correct state to actually call withdraw which is either ClaimerWinning or ChallengerWinning dependend on whether the agent is claimer or challenger. I'd rather like to see something more similar to process_requests() where we also ask for states, i.e.
if request.is_filled:
    do_something()

I attempted to write a test and could actually verify the behaviour with logs, but since the withdraw tx does not fail, it's hard to write an effective test.

How did you try to write those tests? Something like
https://github.com/beamer-bridge/beamer/blob/88b46bdd42360a8e7ab997fcd166fa622c56d0df/beamer/tests/agent/test_request.py#L149-L165
If so, I hope testing this would be easier with an approach as in
https://github.com/beamer-bridge/beamer/blob/88b46bdd42360a8e7ab997fcd166fa622c56d0df/beamer/tests/agent/test_handlers.py#L120-L138

I attempted to write a test and could actually verify the behaviour with logs, but since the withdraw tx does not fail, it's hard to write an effective test.

How did you try to write those tests? Something like
https://github.com/beamer-bridge/beamer/blob/88b46bdd42360a8e7ab997fcd166fa622c56d0df/beamer/tests/agent/test_request.py#L149-L165
If so, I hope testing this would be easier with an approach as in
https://github.com/beamer-bridge/beamer/blob/88b46bdd42360a8e7ab997fcd166fa622c56d0df/beamer/tests/agent/test_handlers.py#L120-L138

I did something like
# Scenario 4:
#
# Charlie          Dave
# --------------------------
# claim
#                  challenge
#
# Winner: Charlie
#
# Note: Bob is not participating in the challenge here. We test whether Bob
# will attempt to withdraw the stakes in place of Dave.
def test_withdraw_not_participant(request_manager, fill_manager, token, config):
    target_address = accounts[8]
    requester, charlie, dave = accounts[:3]

    agent = beamer.agent.Agent(config)

    # Submit a request that Bob cannot fill.
    amount = token.balanceOf(agent.address) + 1
    request_id = make_request(request_manager, token, requester, target_address, amount)

    stake = request_manager.claimStake()
    request_manager.claimRequest(request_id, 0, {"from": charlie, "value": stake})

    collector = EventCollector(request_manager, "ClaimMade")
    claim = collector.next_event()
    request_manager.challengeClaim(claim.id, {"from": dave, "value": stake+1})
    brownie.chain.mine(timestamp=claim.termination)

    agent.start()

    time.sleep(2)
    agent.stop()
    agent.wait()

But you gave me better ideas that I do not yet fully understand.


Decide on one sentance byline for OpenNARS

Decide on a one sentance byline that describes OpenNARS. Set this as the description on GitHub and it will also be used in maven to describe the project and elsewhere.

An implementation of the Non-Axiomatic Reasoning System (NARS) - A General Machine Intelligence

thanks ill update based on this.
On Sun, May 6, 2018 at 2:53 AM, Tony Lofthouse<EMAIL_ADDRESS>wrote:

An implementation of the Non-Axiomatic Reasoning System (NARS) - A General
Machine Intelligence
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opennars/opennars/issues/91#issuecomment-386858482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC5JAhS3tER2c3Yd84Qoy8dUQJthJlNbks5tvp3SgaJpZM4TwSSo
.


Read branch (or commit) from env

This adds the ability to specify the branch or commit to checkout based on an environment variable.
Currently the variable is hard-coded to branch_specifier though it could be made configurable in the future.
With this there are now 3 ways to specify the branch- env, scm config, and job name.  Under certain circumstances they will interact.  For instance, if a commit is specified in the environment, runbld will first checkout the branch specified in scm (or build, if no scm branch was provided) and then checkout the commit.
Shallow clones are also tricky because we may not have the commit in the local clone.  In an effort to fetch the commit (but not --unshallow the whole repo) I added some code to fetch the past 6 months worth of commits.  I wen't back and forth on it and finally just had to pick something.  I am happy to hear feedback.

I'm not qualified to review this PR, but I dig the comments and tests! ⭐

Thanks!  😊


Allow use of relative timestamps for AFL++ plot data in genstats

Using genstats coverage on a project run in with the aflpp flag would cause incorrect output. Timestamps would be negative in the output CSV.
More importantly, when the fuzzer restarts after a round of modelling, the timer also resets. Coverage results would then show all progress from inputs found prior to the current round as occurring in the first few seconds of the pipeline stage.

Thank you for the fix, guyf2010!


Pass attributes in context to enable child span for better sampling

Discovered a use-case where the child span needs information from the parent span's attributes. I come up with putting the attributes in the current context and passing it around in the same trace and use it.

Hey @azeemchauhan. If you want to do something like this in phoenix then you could add a plug and put whatever you'd like into context there. For where you're looking to do this, you'd want your plug inserted into your endpoint right after the telemetry plug.
We generally cannot pollute the context in instrumentation as it has performance implications.

@bryannaegele Thanks for the clarification. I was exploring options to get pass some information from parent span to the child span and then figured that there is no way of reading the parent's span attributes so I thought context could be right choice but looks like this will pollute the context and might have some performance implication due to extra info in context.
And, yes another way of achieving what I want is, update the Absinthe plug to add values from the conn ( ie. Host,  request headers etc) to the plug configuration and then pass to the Absinthe telemetry.


Pass zero-flux BCs to vlasov and gyrokinetic updaters

Presently the zero-flux directions are set within these updaters, but that doesn't allow the user to set zero-flux BCs in specific configuration-space directions.

solved in PR #216


Windows driver compliance for umdfGnss.inf

Resolve "Not isolated to DIRID 13" issue (1322 error). Remove "%12" and "\UMDF" references.
Replace the legacy pattern (2086 error). remove WUDFRD_ServiceInstall and GnssDriver_Device_AddReg.
Remove CoInstallers and WudfRdDisplayName for cleanup. Updated DriverVer.

Moved to 'develop' branch. Refer to https://github.com/microsoft/Windows-driver-samples/pull/1003
Will remove this PR.


Confusing syntax on challenge 07

This is part of the sample code:
const { customClass } = props;
  return (

  );

The destructuring assignment syntax seems to be a little confusing to a beginner. although you have mentioned it in the comments, but it would be better to also include a link for more information.
Of course a more beginner friendly approach would be using the folowing syntax, removing the assignment.
return (

  );

I think it's better to include this syntax in the comments or in another example and mention that these two syntaxes will produce the same output.

Ok, yes I agree with you looking at this now. Thanks for your comments! I've gone through and made some updates to this challenge to make it easier to understand.


Add external routing for Kafka

We will want to provide the option to produce/consume to Kafka from outside Kubernetes.

In Azure, nodes do not get external ip, so how we can use NodePorts in that scenario? How can we use LoadBalancer to access kafka from outside cluster?

What is the difference between service and headless-service. We can use headless-service for connecting to broker from clients inside the cluster, then what is the use case of service?


patch to master -- fix(listitem): need to support render function

Closes # internal https://github.ibm.com/wiotp/monitoring-dashboard/issues/1633
Summary

fix(ListItem): if you take a full React element as the rowAction prop, the clone can go into infinite recursion, this is because the React Element can point to it's parent, to fix allow you to pass a render prop so if you have complex rowActions you can use the renderProp
fix(list-item.scss): the overflow row actions can go offscreen because not enough padding space is saved, and also need to absolute position them

Acceptance Test (how to verify the PR)

I compared the layouts of all the list stories and made sure there were no regressions

Travis isn't going to complete because I turned it off for #1788 - I'll create a pr to hotfix the deployment change to master so the deploy will work on master for this PR.

:tada: This PR is included in version 2.140.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.141.0-next.18 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[STYLE]Text Alignment Issue on Front Page

Problem Description: In the current state of the website's front page, there is a text alignment issue that leads to frustration and a lack of visual coherence. The text appears misaligned, which creates inconsistency and hampers readability. This problem can be off-putting to users and detracts from the overall user experience.
Solution Description: I would like to address the text alignment issue on the website's front page by implementing a solution that combines both CSS and HTML modifications. The scroll should be removed, and we should bring all the details in proper alignment so that it can correctly fit into the front page.
Alternative: Without a Scroll may a footer to the page can also be added!!

Important Announcement: Closure of GitHub Repository Issues, Website Redesign, and Discord Channel Invitation
We apologize for the inconvenience caused, but we must inform you that all current issues in our repository will be closed. This decision aims to improve our development process and enhance organization.
Excitingly, we are announcing a complete redesign of our website, focused on improving user experience and incorporating new features aligned with our goals.
Please note that approximately half of the existing issues are redundant and will be closed accordingly.
We also invite you to join our Discord channel for project collaboration and communication. Visit GSSoC server and assign yourself Web Resource Hub project role using the self-roles feature.
Join here
Your feedback and support are invaluable to us. We look forward to hearing your thoughts on the upcoming changes.
Thank you for your understanding and continued support.
Sincerely,
Project Admin


NativeCodeAsset and DataAsset should accept an assetId instead of package and name.

Currently there is asymmetry between hooks and runtime

the hooks use e.g. NativeCodeAsset(package: ..., name: ...)
the runtime use @Native<Void Function()>(assetId: '...')

we should remove this asymmetry by only requiring an assetId everywhere.

This was changed in https://github.com/dart-lang/native/pull/946 based on feedback from @mosuem that having the package:$packageName/$name is bad usability.
If I remember correctly, the wish was to have the package name be automatic. But since the assets are data classes, and we have a single add method for assets rather than a new add method for BuildOutput for every asset, reading the package name from somewhere doesn't work.
I also don't mind having assetId everywhere instead. It also simplifies link hooks if they don't want to modify the assetId.
We could have an extension type AssetId on String that gives you the package name and asset name. And have a constructor that makes it take a package name and asset name. That would avoid users having to do string concatenation.

Users of this system will write hook/build.dart and lib/foo.dart  and it's very confusing if the two don't use the same way to identify assets. And using const DataAsset(package: 'foo', name: 'bar') is IMHO worse than const DataAsset('package:foo/bar'). Also the ladder allows for non-package uris in the future, which the former doesn't.

using const DataAsset(package: 'foo', name: 'bar') is IMHO worse than const DataAsset('package:foo/bar').

I disagree. Using a "non-typed" API by requiring a string in a certain format is (IMO much) worse than making the format explicit.

Also the ladder allows for non-package uris in the future, which the former doesn't.

Agree there.

If I remember correctly, the wish was to have the package name be automatic.

Yes, I think it is weird to ask the user to supply information we already have. The user should just choose the name, then the point about non-package uris would also be moot.

using const DataAsset(package: 'foo', name: 'bar') is IMHO worse than const DataAsset('package:foo/bar').
I disagree.

const DataAsset(package: 'foo', name: 'bar') is to me as a user clearly

harder to type on a keyboard
harder to read

(it has colons, quotes, commas spaces) than const DataAsset('package:foo/bar').
It doesn't prevent errors either, because I may supply the wrong package or names values. The only thing it really does is it adds a package: in front.
If we have an invariant that any asset ID must start with package: then one could even think of leaving that part away, since it's redundant information.
I understand the urge to model things very detailed with Dart classes, but it often leads to over engineered and hard to use APIs. (Tangential example: We used to have a Path class representing file system paths, it had e.g. Path.components for things between directory separators, ... - it tried to model in Dart classes what a file path looks like - it has been super cumbersome to use and nowadays all code uses package:path and strings. I think it's somewhat similar here.)

Using a "non-typed" API by requiring a string in a certain format is (IMO much) worse than making the format explicit.

The "format" is a ID for which a String seems appropriate.
The fact that currently the system restricts it to be package: uris is a self-imposed restriction that isn't necessary. Actually I do find it confusing to use that in the first place, because

users may think they can const DataAsset('package:intl/intl.dart').load() (normally package uris locate things inside the lib/ folder - but not for the asset package uris, which is confusing)
higher-level abstractions may want to use different naming scheme e.g. const ShaderAsset('shader:flutter/circle')
The existing @Native() API also takes a opaque String assetId
Flutter's asset APIs also take simple strings

If I remember correctly, the wish was to have the package name be automatic.

This asymmetric API is super confusing and I'm strongly opposed to this (me as a user of this have made mistakes due to this asymmetry several times). We should have hook/build.dart use the same names as in lib/foo.dart. And the package name cannot be automatic on the usage site, so it has to be explicitly written.
(Strongly in favor of KISS design principle - keep things simple, not over-engineer APIs, ...)

We should have hook/build.dart use the same names as in lib/foo.dart
Strongly in favor of KISS design principle - keep things simple, not over-engineer APIs, ...

Agree.

me as a user of this have made mistakes due to this asymmetry several times

Also agree - my problem is that I am always unsure what to type in String fields - does this want the name? The name prefixed with the package name? That package name prefixed with package:? I believe using named parameters for the individual components gets rid of this.
I am completely fine with a single assetId field, as long as there are no restrictions on what I can type in that field. If the field is a string, any string should be ok as an input. That is what the type String says. Obviously, the compilation throwing in case of colliding assetIds is still fine.

I understand the urge to model things very detailed with Dart classes, but it often leads to over engineered and hard to use APIs.

I agree that one has to be careful with this. In this case, we are talking about two components, so it's fine to model things in a more detailed way.

If we have an invariant that any asset ID must start with package: then one could even think of leaving that part away, since it's redundant information.

Maybe that is the issue to tackle here first before deciding on the API. If we do want this restriction, we should auto-fill that information when adding assets, and have a named argument package for loading assets, so that users only ever use the name to identify assets.
If we don't, then the identifier should be a "free-form" string field.

If we have an invariant that any asset ID must start with package: then one could even think of leaving that part away, since it's redundant information.

Hm, that's interesting. But that would break the symmetry omitting @DefaultAsset() and @Native(assetId and not omitting it. Because when they are omitted we default to the Dart library URI. (Or we need to change that to the Dart library URI but without the package:?)
Build hooks may only report assets that start with package:<your-own-package-name>/. This is to force (instead of nudge) to avoid naming conflicts between asset id's in various packages. We do allow linkers to pass through asset id's untouched of other packages. Also we allow native code assets and data assets to be used by dart code in a different library.
Since the reporting is restrictive in the build hook but not in the link hook and not in uses, and if we do want symmetry in reporting and using, we redundantly have to repeat <my-package-name>/ in the build hooks.

'shader:flutter/circle'

That's not allowed currently. Maybe we should? Or maybe we should clamp down our design and say we're never going to allow other schemes than package:?

'shader:flutter/circle'
That's not allowed currently. Maybe we should? Or maybe we should clamp down our design and say we're never going to allow other schemes than package:?

One can make this just fine. Because this is passed to a high-level API which is implemented in terms of a lower-level one, this implementation has to eventually bottom out on a data asset and use it's naming convention.
You can see an example in my recently sent out CLs pkg/asset/lib/hook.dart & pkg/asset/lib/asset.dart which re-writes asset names from higher level names to lower level ones.
I think one would want to have it like this because a const IntlData('<id>') and const Shader('<id>') should be two different things, defining a intl asset with <id> should not allow loading it as a shader, so higher level abstraction will

provide hook helpers that internally mangle the id
provide runtime implementation that internally mangles the id

Notes from discussion today. The majority prefers having separate arguments/getters over exposing the assetID string. And we should ensure that we then do the same everywhere. A hopefully exhaustive list:

We need a $package name somewhere in the asset ID to prevent collisions between assets from different packages. The embedder/storage format should to enforce this.
We need a user-defined $type in the asset ID to prevent collisions between different types of assets once users start building abstractions on top of DataAsset. The user-defined abstraction should enforce this. The Dart team can provide an example.
For the storage format, these need to be combined into a string and be deserializable again to provide the 3 components: package, asset name, and (optional) user-defined asset type. One way to do this would be package:$packageName/$assetName and package:$package/$type:$name.

There is no 100% guarantee that users reverse engineer the name mangling. And we can't enforce it in the protocol/embedder. Packages should be able to create any asset type defined by any of their dependencies, so there is no encapsulation similar to the package name that can be checked.
The "package:" is boilerplate for data assets. This boilerplate makes defaulting assetIds to the library URI work with native code assets. We could opt to diverge data assets and code assets, but it's only in the storage format anyway.

For the API in the base layer, we can have 2 String arguments and getters in the base API (asset name and package).
For the API in the user-defined layers we can have the same two arguments. This user-defined abstraction layer will put $type:$name inside the lower layer name.
In order for the error messages for native code assets to make sense and for the default assetIds from dart:ffi to work, native code assets should have also an assetId getter.
The data assets in the package:asset should be looked up with (String package, String name). And then we can hide the assetId getter from DataAsset in this package. cc @mosuem

I'll cook up a CL to change the API in this package.

I've cooked up some CLs to change the API in this package:

https://github.com/dart-lang/native/pull/1536
https://github.com/dart-lang/native/pull/1538
https://github.com/dart-lang/native/pull/1539

We should set us up for a future, where on the lowest level, we support various kind of asset types. Those asset types may be extensions to the basic build/hook protocol. None of the asset kinds are any more special than others, they should all be on same footing. Because of this, I think we should decouple code asset from data asset - they don't have to share a common class hierarchy with specific members for example.
(Imagine a package:flutter_build_hooks that provides a flutter-specific build config (e.g. gradle version) and flutter-specific asset kinds (e.g. proguard rules). We wouldn't want to make that inherit from a shared Asset class and require it to have an Asset.id. We may also add support for other asset kinds that won't have an Asset.file.)
=> So the first step I think is to decouple the data assets from code assets.
=> It should be possible for 3rd parties to extend the protocol to new asset types (that extensibility should work on the JSON protocol itself as well as on the APIs we design here that abstract over the JSON)
=> https://github.com/dart-lang/native/pull/1539 requires all assets to have Asset.{id,file} which we may not want to require
=> https://github.com/dart-lang/native/pull/1538 requires all assets to have Asset.{id,package,name,...} which we may not want to require
=> https://github.com/dart-lang/native/pull/1536 requires all assets to have a Asset.file which we may not want to require (it's nullable yes, but the concept of file may not make sense for some 3rd party asset types)
We may not want to model this as a Asset class hierarchy at all.
(It could possibly be buildOutput.dataFiles.add() / buildOutput.nativeCode.add() - and 3rd parties can add buildOutput.proguardRules.add() )
Then the next step is to decide for all asset kinds individually what the best hook API and runtime API looks like - it may choose a different way for code assets and data assets. But I think for a specific asset kind the hook API and the runtime API should refer to them the same way (i.e. symmetric API) to make it easy for users to understand the connection between their hook/build code that adds something and their lib/* that uses it.
There are considerations that may lead to different outcomes for the code & data assets:

Code Assets: They may (to be figured out!!!) form a global name space (@dcharkes do I recall this correctly that native libraries currently end up in the same folder without renaming and are therefore globally namespaced?): If package A emits a libfoo.so, a package B cannot emit libfoo.so - it would be a collision. Also the exported symbols in libfoo.a and libbar.a cannot overlap. That would be how it's done in C and it would allow taking static archive files from the build of all transitive packages and statically linking them together - as it would be in C. It would allow a bundling tool like flutter, to put all shared libraries in the same folder (instead of a folder per package or renaming shared libraries to include package name and re-writing install names, dependency names, ...)
=> If we go this route then code assets may be a global name space, not sub-namespaced per package. We wouldn't require the package name - neither in the @Native() annotation nor in the hook/build.dart code asset API  - it would be symmetric.
=> In fact right now it seems we don't enforce @Native() annotations to have package:* uris as their ids (at least not in the Dart code, maybe we do enforce on the hook/build.dart side?)
=> If it's possible to namespace native code per package properly, we may do that - but the point here is that we can decide that individually for code assets, independent of the decisions we make for data assets (or proguard assets, ...)

Data Assets: We want to have them namespaced per package. So the high-level APIs (e.g. const ShaderAsset() / const StringDataAsset()) either have to require users to specify it explicitly, or we (in restricted cases) deduce it automatically - 3rd parties can decide on their own, but should follow the general principle
=> If we deduce it automatically we should do so in the high-level runtime API and the high-level hook API
=> If we require explicit package name we should do so in the high-level runtime API and the high-level hook API
=> It should be symmetric
For the low-level data asset API (both the hook/build API and the runtime loading API - should be symmetric) we may could require them as separate arguments (e.g. buildOutput.files.add('pkgname', 'idname', ...) and loadStringAsset('pkgname', 'idname')). It may not matter much how exactly it's done because this is the low-level API that very few developers will use, most will use a higher-level API that may make their own choice (e.g. output.shaders.add('baz') / const Shader('baz') with automatically deduced package name).

(Apologies for the long comment)

form a global name space

Yes. We can rename files and rewrite dynamic linker imports for iOS/MacOS, but not for Linux. https://github.com/dart-lang/native/issues/1425

We wouldn't require the package name - neither in the @Native() annotation

How do you envision the default asset ids to work in this scenario if we don't default to library URI.

We may not want to model this as a Asset class hierarchy at all.

Before we end up doing that rewrite, should we land any of the 3 PRs, if not I'll just close them and leave it beautifully asymmetric until we get to that rewrite. As discussed offline, the rewrite of the Dart API is less urgent than getting the JSON protocol correct.


Rerelease v2.11.7 -> ffe6e79f97

You forgot to update the single header when you released v2.11.7, could you update the release to point to: ffe6e79f97f69d61f9f64e284227f1b2589f4757?
Thanks!

I think you may have closed the wrong issue.

Yeah, sorry: I fixed it.


chore: "chore: revert #1682 & #1721"

Reverts GaloyMoney/galoy#1745

Closing in favour of #1750 & #1751


The library 'libhostpolicy.so' required to execute the application was not found

dotnet core Newbie here, need help to find the right direction.
I'm trying to run the latest version of omnisharp-roslyn on Ubuntu 18.04 and .net core 3.0.0
Just trying to start it, I get the following error message:
$ dotnet ./OmniSharp.exe
A fatal error was encountered. The library 'libhostpolicy.so' required to execute the application was not found in '/opt/omnisharp-dist/omnisharp/'.
Failed to run as a self-contained app. If this should be a framework-dependent app, add the /opt/omnisharp-dist/omnisharp/OmniSharp.runtimeconfig.json file specifying the appropriate framework.

$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /usr/share/dotnet/sdk/3.0.100/

Host (useful for support):
  Version: 3.0.0
  Commit:  95a0a61858

.NET Core SDKs installed:
  3.0.100 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Any kind of suggestions appreciated, thanks!

OmniSharp is not a dotnet core application. If you want to run it on Ubuntu, please install Mono https://www.mono-project.com/docs/about-mono/releases/ and then use mono ./OmniSharp.exe to run it.

Oh, thanks. I do not want to use Mono, guess my plan is shattered then! :)

you have installed Mono 4.6.2, the required one is the latest - 6.4.0

Hi, upgrading Mono to 6.4.0 from the Ubuntu PPA solved the problem. Thanks.


Enable theming

There is no documentation for theming the input, nor pointers.
The only way is to hack into the source and hit the classes, thus, any class name change will break the visuals.

@DarkGhostHunter For input you can use dp-input slot and style it whatever. For the rest of the items, just find the class you need and change the style to your liking.


Schema registry missing class

Kafka fails to start with embedded schema registry with the following error. Running the same code with EmbeddedKafkaConfig instead of EmbeddedKafkaConfigWithSchemaRegistry allows Kafka to start normally.
09:35:52.238 [ScalaTest-run-running-AvroSerdeTest] ERROR o.a.zookeeper.server.ZooKeeperServer - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes
09:35:52.787 [ScalaTest-run-running-AvroSerdeTest] WARN  k.server.BrokerMetadataCheckpoint - No meta.properties file under dir /var/folders/gv/xmthgtn10ld6c4zntpyfhx700000gn/T/kafka5424540063163778361.tmp/meta.properties
09:35:53.286 [ScalaTest-run-running-AvroSerdeTest] WARN  k.server.BrokerMetadataCheckpoint - No meta.properties file under dir /var/folders/gv/xmthgtn10ld6c4zntpyfhx700000gn/T/kafka5424540063163778361.tmp/meta.properties
09:35:53.580 [ScalaTest-run-running-AvroSerdeTest] WARN  io.confluent.rest.Application - DEPRECATION warning: `listeners` configuration is not configured. Falling back to the deprecated `port` configuration.
09:35:53.737 [ScalaTest-run-running-AvroSerdeTest] WARN  io.confluent.rest.Application - DEPRECATION warning: `listeners` configuration is not configured. Falling back to the deprecated `port` configuration.
09:35:53.754 [ScalaTest-run-running-AvroSerdeTest-SendThread(localhost:57670)] WARN  org.apache.zookeeper.ClientCnxn - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
	at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
	at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
09:35:53.892 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.admin.AdminClientConfig - The configuration 'topic' was supplied but isn't a known config.
09:35:53.893 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.admin.AdminClientConfig - The configuration 'connection.url' was supplied but isn't a known config.
09:35:54.016 [ScalaTest-run-running-AvroSerdeTest] WARN  i.c.k.s.storage.KafkaStore - Creating the schema topic _schemas using a replication factor of 1, which is less than the desired one of 3. If this is a production environment, it's crucial to add more brokers and increase the replication factor of the topic.
09:35:54.222 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.producer.ProducerConfig - The configuration 'topic' was supplied but isn't a known config.
09:35:54.222 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.producer.ProducerConfig - The configuration 'connection.url' was supplied but isn't a known config.
09:35:54.254 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.consumer.ConsumerConfig - The configuration 'topic' was supplied but isn't a known config.
09:35:54.255 [ScalaTest-run-running-AvroSerdeTest] WARN  o.a.k.c.consumer.ConsumerConfig - The configuration 'connection.url' was supplied but isn't a known config.
09:35:54.423 [ScalaTest-run-running-AvroSerdeTest-SendThread(localhost:57670)] WARN  org.apache.zookeeper.ClientCnxn - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
	at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
	at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
09:35:54.639 [ScalaTest-run-running-AvroSerdeTest] WARN  io.confluent.rest.Application - DEPRECATION warning: `listeners` configuration is not configured. Falling back to the deprecated `port` configuration.
09:35:54.685 [ScalaTest-run-running-AvroSerdeTest] ERROR o.a.zookeeper.server.ZooKeeperServer - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes

A needed class was not found. This could be due to an error in your runpath. Missing class: org/eclipse/jetty/server/handler/ContextHandler$NoContext
java.lang.NoClassDefFoundError: org/eclipse/jetty/server/handler/ContextHandler$NoContext
	at org.eclipse.jetty.servlet.ServletContextHandler.newServletHandler(ServletContextHandler.java:260)
	at org.eclipse.jetty.servlet.ServletContextHandler.getServletHandler(ServletContextHandler.java:322)
	at org.eclipse.jetty.servlet.ServletContextHandler.relinkHandlers(ServletContextHandler.java:198)
	at org.eclipse.jetty.servlet.ServletContextHandler.<init>(ServletContextHandler.java:157)
	at org.eclipse.jetty.servlet.ServletContextHandler.<init>(ServletContextHandler.java:117)
	at org.eclipse.jetty.servlet.ServletContextHandler.<init>(ServletContextHandler.java:105)
	at io.confluent.rest.Application.createServer(Application.java:267)
	at io.confluent.kafka.schemaregistry.RestApp.start(RestApp.java:76)
	at net.manub.embeddedkafka.schemaregistry.EmbeddedKafkaWithSchemaRegistrySupport.startSchemaRegistry(embeddedKafkaWithSchemaRegistry.scala:122)
	at net.manub.embeddedkafka.schemaregistry.EmbeddedKafkaWithSchemaRegistrySupport.startSchemaRegistry$(embeddedKafkaWithSchemaRegistry.scala:111)
	at net.manub.embeddedkafka.schemaregistry.EmbeddedKafkaWithSchemaRegistrySupport.$anonfun$withRunningKafkaOnFoundPort$2(embeddedKafkaWithSchemaRegistry.scala:88)
	at net.manub.embeddedkafka.EmbeddedKafkaSupport.withTempDir(EmbeddedKafka.scala:265)
	at net.manub.embeddedkafka.EmbeddedKafkaSupport.withTempDir$(EmbeddedKafka.scala:261)

sbt dependency entry
"net.manub"              %% "scalatest-embedded-schema-registry" % "1.1.0-kafka1.1-nosr" % Test,

I also see this problem.

This may be related to incompatible versions of Jetty on your classpath. If you run something like sbt dependencyTree what's the ouptut for Jetty?


Add more command type and remove http client from pom

Add Auth and Last command type
Remove http client from pom.xml
Format PopCommand class by replacing tab with space

@krdev
Hi Kumar, here is the pull request we discussed. I have made  changes.
Fan


KeyError: 'model_emadecay'

Hello, thanks for your excellent job!
When I try to train the example, it came out with following error:
....
VideoTransformerBlock is using checkpointing
Initialized embedder #0: FrozenOpenCLIPImagePredictionEmbedder with 683800065 params. Trainable: False
Initialized embedder #1: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #2: ConcatTimestepEmbedderND with 0 params. Trainable: False
Making attention of type `vanilla-xformers` with 512 in_channels
Building MemoryEfficientAttnBlock with 512 in_channels...
Working with z of shape (1, 4, 32, 32) = 4096 dimensions
Making attention of type `vanilla-xformers` with 512 in_channels
Building MemoryEfficientAttnBlock with 512 in_channels...
Initialized embedder #3: VideoPredictionEmbedderWithEncoder with 83653863 params. Trainable: False
Initialized embedder #4: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #5: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #6: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #7: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #8: ConcatTimestepEmbedderND with 0 params. Trainable: False
Initialized embedder #9: ConcatTimestepEmbedderND with 0 params. Trainable: False
Making attention of type `vanilla` with 512 in_channels
Working with z of shape (1, 4, 32, 32) = 4096 dimensions
Skipping timestep embedding in ResBlock
Making attention of type `vanilla` with 512 in_channels
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Skipping timestep embedding in ResBlock
Keeping EMAs of 1434
Loading pretrained model from /horizon-bucket/saturn_v_dev/users/junyuan.deng/weights/svd_xt.safetensors
Traceback (most recent call last):
  File "/home/users/junyuan.deng/Programmes/Vista/train.py", line 668, in <module>
    svd[miss_k] = svd[ema_name]
KeyError: 'model_emadecay'

What should I do to solve the problem?

I have fixed the bug in the latest script. Thanks for pointing that out!


Conditional permission at a certain job level

Hello, I have an issue about Jobs' conditions to give temporary permissions once a certain level is obtained...
CONFIG SECTION (DELETE IF NOT RELEVANT):
  conditions:
    buch:
      requires:
      - j:Bucheron-40
      - p:tier.jobs2
      perform:
      - p:jobs.join.Menuisier-true`

I have players that have the first job "Bucheron", which is required to be lvl 40 to take "Menuisier". Except they can't.
After some tests I saw that they needed their secondary job (Miner, for my test subject) to get to lvl 40 to take "Menuisier".
May someone help me about this?
(Same goes for other jobs with 2 prerequisites, but not for all of they jobs I have on server...)
Jobs version: <IP_ADDRESS>
Server Type (Spigot/Paper/etc):  Purpur
Server Version (using /ver): 1.21.0
Relevant plugins (Delete if this isn't needed): LuckPermBungee ?

Looking at your setup, you have extra ' at the end of permission, so you will either need to add another ` at the start or remove it to make this as a valid line

conditions:
menuisier:
requires:
- j:Bucheron-40
- p:tier.jobs2
perform:
- p:jobs.join.Menuisier-true
it was just my discord copy-paste, there is no ' in my config


MOD files repeat endlessly

I have a few mod files that I downloaded a long time ago. I noticed that they repeat instead of stopping when they get to the end.
When playback should stop there is a log message in the console that says:
duh_render_int() returned short frame count: requested 512, got 256
According to Audio Overload my files are:
Amiga *Tracker (.mod) files, subtype ProTracker or subtype ProTracker/NoiseTracker
NB: The reported track length appears to be correct

Could you share one of the files either by posting or emailing me a link?

Here is one example:
https://modarchive.org/index.php?request=view_by_moduleid&query=167162
I have just noticed that their "Play with Online Player" also loops the track, so I guess it's just a problem with the decoder.

Thanks for reporting this. Could you try the changes in #300 and see if they work for you?

My 5 mod files all play just fine with the change. Many thanks. I should go away and download some more!


Fixed bugs regarding http headers and added full set of tests.

After using the new headers feature in 5.18.2 i stumbled upon two issues:

The RequestRunner readded the headers on each invocation of Run - Fixed by adding a check before adding headers
The FindEntry, FindEntries, FindScalar, SetMedia and GetMedia methods flowed through a different constructor of RequsetBuilder - Fixed by refactoring the internal methods so that headers are passed to that constructor as well.

I added a full set of unit tests for all public methods of the fluent API.
For the other public APIs the headers have to be added either as optional after CancellationToken (which is not very nice) or more overload should be added (but they are too many alread). So I decided to omit support for headers on the non fluent public APIs.

@object @watfordgnf would it be possible for someone to review and merge these fixes so we can use this feature in production?


Support Old Syntax

Support is being added to WyC for old() syntax, corresponding with class WyilFile.Old.  This should in principle be relatively straightforward to support:

[x] Update Translator
[x] Copy Test Files
[x] Make it work!
[ ] Loop Invariants
[ ] Properties

Looks like the minimal recursive test is the following:
type List is null|Node
type Node is &{ List next }

variant unchanged(List l)
where (l is Node) ==> (l->next == old(l->next))
where (l is Node) ==> unchanged(l->next)

method m(List l)
ensures unchanged(l):
    skip

I don't know why this doesn't verify.  Obviously, being recursive is tricky!


draw_state.cpp::find_entrypoint crashes if name is 0

I don't know whether this is covered by the param_checkers_layer, but ideally find_entrypoint would early out if name is null

It should be protected by param_checker, yes. There's a lot of cases like this...

I am running without param_checker since it fails building on Windows (something about a lxml python lib missing).

There's documentation for setting up the lxml stuff in the spec generation README:
https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/README

Mathias:
If the meta layer (VK_LAYER_LUNARG_standard_validation) is available, I suggest using it. It will put param_checker ahead (closer to the app) of draw_state in the layer chain allowing param_checker to catch the error.
I updated the BUILD.md document to include directions on installing python lxml.  I believe this issue can be closed.


How to debug a chainlit app

Hi there!
I've built my first chainlit app. It's very simple and it runs like this.
cd ./chainlit-backend
chainlit run app.py -h

Start the React app
cd ./frontend
npm i
npm run dev

How do I set it where I set break points in my IDE and debug? I'm currently using cursor but I have VS code and intellij as well. Any guidance would be amazing-- I would love to move forward but I think I'll be stumped until I can play around with breakpoints. Thank you

Hi,
In your main application script add:
if name == "main":
from chainlit.cli import run_chainlit
run_chainlit(file)
Then run the script from your IDE in debug mode. I hope this will help.
Best

In your main application script add: if __name__ == "__main__":  from chainlit.cli import run_chainlit  run_chainlit(__file__)
Then run the script from your IDE in debug mode. I hope this will help. Best

That's exactly how we do it as well.

I put in a PR.
Added this under 'advanced features' in the docs, although I also feel it should be in the cookbook as well.

I believe this pull request (https://github.com/Chainlit/docs/pull/107) is merged.
I'm new to GitHub project (and contributing also!), but in my experience, merged pull requests are automatically closed.
Why is it not the case here? I can help if needed.

I believe this pull request (Chainlit/docs#107) is merged. I'm new to GitHub project (and contributing also!), but in my experience, merged pull requests are automatically closed. Why is it not the case here? I can help if needed.

I think the PR is not linked to this issue.


Auto data flow

Also related to #138
This is PR for the review of my AutoFlow modification.
I want to use a DataHolder in AutoFlow rather than a simple placeholder, and make it possible to change the behavior of the AutoFlow in its child class.
The main purpose of this modification is to make it possible to pass an object other than tf.placeholder to the predictive method such as model.predict_f().
In my coregionalized model implementation, I want to pass an object that include a coordinate vector, task index as well as some methods to sort, split and merge, in a child class of AutoFlow (LabeledAutoFlow in #138).
I would be very great if anyone review this codes and comment if this change is acceptable or not.
If not, I will consider alternatives.

Closed because code direction was changed in #138 .


Keyboard Issues

Type: Bug
Some keys take a long time to work (~1-20 seconds). Specifically, backspace takes about 20 seconds most of the time, ctrl+c and ctrl+v take about 10 seconds each. Return is sometimes immediate and sometimes delayed by about 2 seconds. I've reset all my settings to factory, and completely removed VS code drom my machine and reinstalled it to no avail.
 Press F1 and then choose Developer: Reload Window with Extensions Disabled

Good afternoon Alexandru, Disabling all extensions, then re-enabling only the ones I used fixed the issue. Do you know what extension causes this issue? Sincerely, Daniel J. ***@***.***@vcu.edu(804-605-4233 From: Alexandru DimaSent: Thursday, March 30, 2023 8:34 PMTo: microsoft/vscodeCc: Dan-yelp; AuthorSubject: Re: [microsoft/vscode] Keyboard Issues (Issue #178646) Does this reproduce when disabling all extensions? Press F1 and then choose Developer: Reload Window with Extensions Disabled—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>
@Dan-yelp Since this no longer reproduce after disabling extensions, this indicates that this was a problem caused by one of your installed extensions. You can use extension bisect to narrow down the possible problematic extension:

run F1 > Help: Start Extension Bisect
(this will restart VS Code with half of your extensions disabled)
try to do the steps which reproduce the problem
if the problem reproduces, click "This is bad" (this narrows down the problematic extension to the half which was enabled)
if the problem does not reproduce, click "Good now" (this narrows down the problematic extension to the half which was disabled)
these steps will repeat until the problematic extension is found

initial
step
final


Resolving FB user ids

This is a follow up to #14
The addition will allow to resolve the given user id (e.g<EMAIL_ADDRESS>to the name of the user (e.g. Mark Zuckerberg).

Rebasing was too involved, so I just edited the history. Anyways this code should work, is somewhat hard to test, since not all FB ids will/can be resolved.

Bump :)

I tried to refactor, so that it makes better use of guard statements. Thanks for the reminder on that concept!
Hope the PR looks better now 😄

Sorry for my long absence. I was contractually not allowed to contribute to open source projects in the last months.

No worries!
And it's a bit of a busy week for me, but I'll dive back into this either
later this week, or next week!  Looking forward to reviving it :)
On Tue, Aug 29, 2017 at 7:57 AM, Nigel Schuster<EMAIL_ADDRESS>wrote:

Sorry for my long absence. I was contractually not allowed to contribute
to open source projects in the last months.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mdezube/sms-analysis/pull/16#issuecomment-325641243,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACo82nvZXhZ9zb3VKhgRnPAzqPQKPNI3ks5sc_yigaJpZM4MN0Wf
.

Bump :)

Ahh thank you for this Nigel, I lost track of this email :) Should have
time this weekend.
On Wed, Sep 20, 2017 at 6:25 PM, Nigel Schuster<EMAIL_ADDRESS>wrote:

Bump :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mdezube/sms-analysis/pull/16#issuecomment-330998278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACo82vQjH-UNRxUhHUJvyuQMkXaiMXqGks5skZDdgaJpZM4MN0Wf
.

Awesome code Nigel!  Now I'd recommend somehow prompting the user to choose the iphone_connector or facebook_connector, perhaps just with a comment in the code.


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Linkedin: https://www.linkedin.com/in/damiel-maquiling-3073ab195/
Facebook: https://www.facebook.com/blank.damiel/
Instagram: https://www.instagram.com/damieru_/


Support editorconfig max_line_length setting.

Editorconfig has a max_line_length setting which some editors/formatters use for wrapping text.
The EditorGuidelines-Plugin could also read this setting apart from its own guidelines setting.

Thanks for the tip. It's a good suggestion.

If someone wants to take a look, the code that parses guideline values from .editorconfig is in UpdateGuidelinesFromCodingConventionsAsync https://github.com/pharring/EditorGuidelines/blob/master/src/ColumnGuide/ColumnGuide.cs#L239
For now, I suggest we treat "max_line_length" just like any other guideline and merge its setting in with our own guidelines. I presume "max_line_length" is and our guideline settings are aligned (i.e. the guideline goes to the right of the given value; so a max-line-length of zero would be hard up against the left-hand edge and probably useless)

I'm starting work on this today


can you update?

Thanks for the great efforts.
Can you update the information of paper, Generating Realistic 3D Brain MRIs Using a Conditional Diffusion Probabilistic Model, it is accepted by MICCAI 2023. Thanks a lot~

Hi @xiaoiker,
Thanks for your interest! Congratulations on your acceptance and excellent paper. It is now updated.


Warnings/Types for the key attribute

Version
3.0.2
Reproduction link
https://jsfiddle.net/skirtle/2czyf41n/
Steps to reproduce
The example illustrates a couple of things:

Using objects for the key attribute works (this is good but undocumented).
No warning is shown when using the same key (value 1) for multiple adjacent siblings.

What is expected?
A quick recap of Vue 2:

Keys had to be primitives: string, number, boolean or symbol. Anything else triggered an immediate warning during rendering.
Using the same key on siblings triggered a warning about duplicate keys.

Observations about Vue 3:

From looking through the code it seems that keys are compared using ===. In some edge cases they are compared using a Map.  Either way, objects can now be used as keys. I think this is great.
From a TS perspective, keys are only permitted to be a string or number.
There is a warning about duplicate keys but it is only hit during updates and only in very specific circumstances.

Based on my best guess about what the expected behaviour is I suggest the following changes:

There should be a warning during rendering for duplicate keys. Duplicates indicate a developer error, even if they cause no real harm.
The TS definitions should be updated to allow anything to be used as a key.
The docs should be updated. Being able to use an object as a key is a great new feature and, if it's intentional, it's something worth shouting about. I'm happy to make the docs changes myself once I have confirmation of the officially supported behaviour.

https://github.com/vuejs/docs-next/issues/698
And add one, how should NaN -0 be treated?

I saw v-if/v-else is auto compiled to key:0 key:1 in the source. won't that cause error when the sibling is key=0 key=1 or other v-if/v-else also compiled to key:0 key:1?

The compiled render function will enter the optimization mode when patching, it respects the so-called block-tree algorithm, which has nothing to do with the key.

This PR provides the checking for duplicate keys

Just to clarify, adding the duplicate keys warning was just one, small part of this.
Primarily I was trying to get the types updated with a view to updating the docs.

Hey guys, just want to add another reason why I believe there should be a warning for siblings with the same key:
Previously there was an issue when siblings were not updated when using v-if, so this got fixed for vue templates in the compiler by automatically adding keys: https://github.com/vuejs/core/issues/1587
However, we ran into the same issue when using JSX: https://github.com/vitejs/vite-plugin-vue/issues/304
I believe that by having proper checks in place for keys this issue could be avoided.


Add a --panicOnWarning flag

This issue is especially targeted at deprecation warnings. These textual references without a file/template context (filename, line number) is sometimes very hard to debug. It would be much nicer if I could do hugo server --panicOnWarning and just iterate until the warnings go away.
We should also print that flag as part of the deprecation message.
/cc @jmooring

Perhaps intentional but this flag does not panic on WARN
Start building sites …
hugo v0.92.0-B3549403+extended linux/amd64 BuildDate=2022-01-12T08:23:18Z VendorInfo=gohugoio
WARN 2022/01/12 23:07:10 .File.TranslationBaseName on zero object. Wrap it in if or with: {{ with .File }}{{ .TranslationBaseName }}{{ end }}