Build Error: Inertia not found in build

Package version
1.1.0
Describe the bug
Sorry, I am not sure whether I should check this in adonisjs core instead...
I am getting a build error, it seems that inertia is not added at all in the build. If you look at the picture below, which is the build, there's no inertia folder at all. And when you cd into the build folder and run npm run start, you get the error: 5:24:40 PM [vite] Pre-transform error: Failed to load url /inertia/app/app.tsx (resolved id: /inertia/app/app.tsx). Does the file exist? and 5:24:40 PM [vite] Pre-transform error: Failed to load url /inertia/pages/home.tsx (resolved id: /inertia/pages/home.tsx). Does the file exist?.

Could it be because in the tsconfig as mentioned in the official inertia docs on adonis website, it ignores the directory where inertia is? I tried to remove inertia/**/* from the exclude option in the tsconfig but it now results in a bunch of errors around react and tsx. It should be using the tsconfig in the inertia folder for the build right?
{
  "compilerOptions": {
    // ...
  },
  "exclude": ["inertia/**/*"]
}

(TSX ERRORS from removing inertia/**/* from the tsconfig after build)

I deployed the application on fly and I am getting a similar error
{
  "level": 60,
  "time":<PHONE_NUMBER>946,
  "pid": 330,
  "hostname": "185e295b425448",
  "request_id": "g91q2v5gbxcf43j79d1aq1mx",
  "err": {
    "type": "EdgeError",
    "message": "Cannot find \"inertia/pages/errors/server_error.tsx\" chunk in the manifest file",
    "stack": "Error: Cannot find \"inertia/pages/errors/server_error.tsx\" chunk in the manifest file\n at anonymous (/app/build/resources/views/inertia_layout.edge:12:0)\n at Template.reThrow (file:///app/node_modules/edge.js/build/chunk-BEFAZY6F.js:523:11)\n at eval (eval at #wrapToFunction (file:///app/node_modules/edge.js/build/index.js:1168:14), <anonymous>:52:10)",
    "code": "E_RUNTIME_EXCEPTION",
    "line": 12,
    "col": 0,
    "filename": "/app/build/resources/views/inertia_layout.edge"
  },
  "msg": "Exception raised by error handler"
}

Reproduction repo
https://github.com/discoverlance-com/adonis-build-error

I see the issue, I should be running the yarn start command from the root directory. It was just not working when running from the root directory so that's why. I think it's because the default package.json command for start tries to run the command from bin/server.js instead of build/bin/server.js. So I have been able to change that at least locally.
Thanks.

I see the issue, I should be running the yarn start command from the root directory. It was just not working when running from the root directory so that's why. I think it's because the default package.json command for start tries to run the command from bin/server.js instead of build/bin/server.js. So I have been able to change that at least locally.
Thanks.

Wait I think this error still exists because from the adonis docs,

The compiled output is written inside the ./build directory. If you use Vite, its output will be written inside the ./build/public directory.

Once you have created the production build, you may copy the ./build folder to your production server. From now on, the build folder will be the root of your application.

So this means that the build folder should have the inertia build and should be possible to launch it without having to run it from my root directory as the build folder should have all build files including inertia.
Do I need to run an extra command to build inertia?

Have you been able to resolve this, if yes, please how, am facing same issue

Have you been able to resolve this, if yes, please how, am facing same issue

Could you let me know if you are running the code in production mode?
NODE_ENV=production node bin/server.js

📚 https://docs.adonisjs.com/guides/views-and-templates/inertia#why-my-production-build-is-not-working-

am getting this error
Cannot find "resources/css/app.css" chunk in the manifest file
first of all the css in resources are not being copied to the resources in build folder.
I have to copy it myself, then when I run without NODE_ENV=production it works, but if I use NODE_ENV=production, am getting the error above,
Can there be a documentation on how to build inertia for production

Have you been able to resolve this, if yes, please how, am facing same issue

Could you let me know if you are running the code in production mode?
NODE_ENV=production node bin/server.js

📚 https://docs.adonisjs.com/guides/views-and-templates/inertia#why-my-production-build-is-not-working-

Yes I did run in production too. It looks like the build does not build or move the inertia folder itself, because if you check in the build folder after build, there's no inertia folder in the build. This is just my assumption but it looks like in this case it's looking for the inertia/pages/* and the files are not found or in the build.
By looking at the buildSteps in src/plugins/vite.ts, it looks like the application is built in build/public/assets so could it be that the vite helper in the layout is not resolving it well? @vite(['inertia/app/app.tsx', inertia/pages/${page.component}.tsx]) and instead is looking for the files in inertia/** even after build?
buildSteps: [
          {
            name: 'build-client',
            description: 'build inertia client bundle',
            config: { build: { outDir: 'build/public/assets/' } },
          },
          {
            name: 'build-ssr',
            description: 'build inertia server bundle',
            config: {
              build: {
                ssr: true,
                outDir: options.ssr.output || 'build/ssr',
                rollupOptions: { input: options.ssr.entrypoint },
              },
            },
          },
        ],

Starting from your reproduction repo here: https://github.com/discoverlance-com/adonis-build-error
It seems like the build isn't picking up that your pages are actually in use and omitting them from the final build chunks. You should be seeing your pages split out into chunks like below:  Notice there's a chunk for app, server_error, and not_found
When you omit { eager: true } on your page glob import, the build will now properly pickup an chunk your pages within the build.
createInertiaApp({
  progress: { color: '#5468FF' },

  title: (title) => `${title} - ${appName}`,

  resolve: async (name) => {
    const pages = import.meta.glob('../pages/**/*.tsx') // 👈 no eager: true
    let page = pages[`../pages/${name}.tsx`]
    //@ts-ignore
    page.default.layout = name.startsWith('portal/')
      ? //@ts-ignore
        (p) => <DashboardLayout children={p} />
      : //@ts-ignore
        (p) => <GuestLayout children={p} />
    return page
  },

  setup({ el, App, props }) {
    createRoot(el).render(
      <PrimeReactProvider>
        <App {...props} />
      </PrimeReactProvider>
    )
  },
})

Alternatively, you can use the resolvePageComponent helper
createInertiaApp({
  progress: { color: '#5468FF' },

  title: (title) => `${title} - ${appName}`,

  resolve: async (name) => {
    const page = await resolvePageComponent(
      `../pages/${name}.tsx`,
      import.meta.glob('../pages/**/*.tsx')
    )
    // const pages = import.meta.glob('../pages/**/*.tsx', { eager: true })
    // let page = pages[`../pages/${name}.tsx`]
    //@ts-ignore
    page.default.layout = name.startsWith('portal/')
      ? //@ts-ignore
        (p) => <DashboardLayout children={p} />
      : //@ts-ignore
        (p) => <GuestLayout children={p} />
    return page
  },

  setup({ el, App, props }) {
    createRoot(el).render(
      <PrimeReactProvider>
        <App {...props} />
      </PrimeReactProvider>
    )
  },
})

Making either of these two changes gets your reproduction build working.

Thanks, I will try this in a bit.

Hello @tomgobich, I tried the changes and I went with the second method, it works now as also shown below. Thanks.
createInertiaApp({
  progress: { color: '#5468FF' },

  title: (title) => `${title} - ${appName}`,

  resolve: async (name) => {
    const page = await resolvePageComponent(
      `../pages/${name}.tsx`,
      import.meta.glob('../pages/**/*.tsx')
    )
    //@ts-ignore
    page.default.layout = name.startsWith('portal/')
      ? //@ts-ignore
        (p) => <DashboardLayout children={p} />
      : //@ts-ignore
        (p) => <GuestLayout children={p} />
    return page
  },

  setup({ el, App, props }) {
    createRoot(el).render(
      <PrimeReactProvider>
        <App {...props} />
      </PrimeReactProvider>
    )
  },
})


Why replace the predicted labels?

Why do we have the below replacement in the evaluate.py?
make the label ids consistent
    preds['label'] = preds['label'].replace(self.activity_index)

What happens if the validation or the test dataset does not have all the possible labels?

We follow the original ActivityNet evaluation code to replace the original string with the index to eval predictions. For your case, I think you should manually build the activity_index with the union of your all data.

thanks for the reply.


Removed duplicate '--with-fingerprint' parameter.

There was a duplicate option --with-fingerprint which I removed.

This is intentional. From the man page:
       --with-fingerprint
              Same as the command --fingerprint but changes only the format of
              the output and may be used together with another command.

and
       --fingerprint
              List all keys (or the specified ones) along with  their  finger‐
              prints.  This  is  the  same  output as --list-keys but with the
              additional output of a line with the fingerprint.  May  also  be
              combined  with  --list-sigs or --check-sigs.  If this command is
              given twice, the fingerprints of all secondary keys  are  listed
              too.

Difference:
pub   rsa4096/974EE250 2012-05-12 [SCEA] [expires: 2017-01-12]
      Key fingerprint = 5039 F36E E75C CD6E C444  A007 5CFC 3B88 974E E250
uid         [ultimate] Etienne Perot (https://perot.me/<EMAIL_ADDRESS>sub   rsa4096/EEDA047E 2012-05-12 [SEA]

$ gpg --list-public-keys --with-fingerprint --with-fingerprint<EMAIL_ADDRESS>pub   rsa4096/974EE250 2012-05-12 [SCEA] [expires: 2017-01-12]
      Key fingerprint = 5039 F36E E75C CD6E C444  A007 5CFC 3B88 974E E250
uid         [ultimate] Etienne Perot (https://perot.me/<EMAIL_ADDRESS>sub   rsa4096/EEDA047E 2012-05-12 [SEA]
      Key fingerprint = 02B0 355A 6F6F 4929 9FE8  100E 4D06 1903 EEDA 047E <----------

Yes, gpg is crazy.

Thanks for the clarification!


scheduler/job.c: use gziptoany for raw files (not just raw printers)

Printing banner pages with raw print files (but not on raw printers), causes only the banner to be printed.  The patch to fix https://github.com/apple/cups/issues/4782 caused a slight regression that re-introduced part of the issue described in STR #1933.  The gziptoany filter is invoked for multi-file jobs on raw queues, but not for raw files on a non-raw queue.

@bmasonrh any updates?


[Feature Request]: solution for leetcode 922

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I would like to add solution in c++,java,python, javascript for leetcode problem 922. Sort Array By Parity II
Use Case
solution for leetcode 922
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Ajay-Dhangar can you please aasign me.


DDNS Basic Implementation

Daemon/Area
ddns
Feature/Enhancement you are proposing
Effort is yet to be made for DDNS daemon
Basic implementation will provide common API calls first and then more specific ones
Reason for Feature/Enhancement
To encourage people to use API calls instead of directly managing the configuration

I'm Implementing DDNS in the next week or so, more great timing :) Thanks again!

Hi,
I'm wondering is the ddns daemon fully working now?
Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'"  error when trying to get ddns config.
Thanks in advance if you could give more details or help.

Hi,
I'm wondering is the ddns daemon fully working now?
Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'"  error when trying to get ddns config.
Thanks in advance if you could give more details or help.

Hi, I'm wondering is the ddns daemon fully working now? Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'" error when trying to get ddns config. Thanks in advance if you could give more details or help.

Hi, sorry I haven't had enough interest on the DDNS side to work on it fully yet (nor use it at the company which utilize this module heavily).
There is already a basic implementation for some of the API calls for interacting with the configuration (config-get, config-reload, config-set, config-test) and a few other statistics commands but that's it.
The forwarding socket not configured sounds like to me your control agent configuration hasn't defined the ddns socket to interact with the ddns daemon, are you using any sample configurations in this repo? (as I think I may not include a working ddns config)
I am happy to test out and go through some of the kea documentation for the latest version to see which API calls I could implement for the ddns implementation if you would like to be apart of the testing.
Thanks!

Hi,
I'm using my own configuration files.
I've defined ddns socket in control agent config file as below, as Kea documents suggested:
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/kea4-ctrl-socket"
},
"dhcp6": {
"socket-type": "unix",
"socket-name": "/tmp/kea6-ctrl-socket"
},
"d2": {
"socket-type": "unix",
"socket-name": "/tmp/kea-ddns-ctrl-socket"
}
},
I'm guessing is the issue caused by the socket name, i.e. "ddns" used in your repo but "d2" in original kea?
I did tried to change "d2" to "ddns" and add a new socket for "ddns". Neither of them works.
Appreciated if you could upload a working ddns config example, I'll try to compare my setting with yours to see if any fix.
Thanks a lot.


AlertManager errors when values are not defined

Describe the bug: (a clear and concise description of what the bug is)
Starting a fresh cluster with minimal values, and nothing defined for alerts, then alertmanager is started and throws an error shared in the comment below
To Reproduce
Steps to reproduce the behavior:

Start a fresh cluster with minimal values and don't define values for alerts.
Observe alertmanager crashing

Expected behavior: (a clear and concise description of what you expected to happen)
When no values are defined for alertmanager (prometheus) it is not started, and thus no errors occur.

Linked to this issue: https://github.com/redkubes/otomi-core/issues/471
level=info ts=2021-07-18T11:35:03.013Z caller=main.go:221 msg="Starting Alertmanager" version="(version=0.22.2, branch=HEAD, revision=44f8adc06af5101ad64bd8b9c8b18273f2922051)"
level=info ts=2021-07-18T11:35:03.013Z caller=main.go:222 build_context="(go=go1.16.4, user=root@b595c7f32520, date=20210602-07:50:37)"
level=warn ts=2021-07-18T11:35:03.254Z caller=cluster.go:251 component=cluster msg="failed to join cluster" err="1 error occurred:\n\t* Failed to resolve alertmanager-po-alertmanager-0.alertmanager-operated.monitoring.svc:9094: lookup alertmanager-po-alertmanager-0.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n\n"
level=info ts=2021-07-18T11:35:03.254Z caller=cluster.go:253 component=cluster msg="will retry joining cluster every 10s"
level=warn ts=2021-07-18T11:35:03.254Z caller=main.go:312 msg="unable to join gossip mesh" err="1 error occurred:\n\t* Failed to resolve alertmanager-po-alertmanager-0.alertmanager-operated.monitoring.svc:9094: lookup alertmanager-po-alertmanager-0.alertmanager-operated.monitoring.svc on <IP_ADDRESS>:53: no such host\n\n"
level=info ts=2021-07-18T11:35:03.254Z caller=cluster.go:671 component=cluster msg="Waiting for gossip to settle..." interval=2s
level=info ts=2021-07-18T11:35:03.304Z caller=coordinator.go:113 component=configuration msg="Loading configuration file" file=/etc/alertmanager/config/alertmanager.yaml
level=error ts=2021-07-18T11:35:03.305Z caller=coordinator.go:118 component=configuration msg="Loading configuration file failed" file=/etc/alertmanager/config/alertmanager.yaml err="unsupported scheme "" for URL"
level=info ts=2021-07-18T11:35:03.305Z caller=cluster.go:680 component=cluster msg="gossip not settled but continuing anyway" polls=0 elapsed=51.364921ms

Second to last line: err="unsupported scheme "" for URL"

Could you elaborate on this, this confuses me a bit. Like where/how did you start a fresh cluster, did you only deploy AlertManager, did you deploy anything else, etc. It is useful to isolate the problem so other people can reproduce it.

@mojtabaimani and I started a fresh cluster using his chart installer. We used minimal values necessary to successfully start the cluster/stack. Except for setting up alerts. Then this error pops up.

So did you fix the schema to align charts.alertmanager.enabled with the requirement of alerts?

So did any of you fix the schema to align charts.alertmanager.enabled with the requirement of alerts?
@mojtabaimani @Dunky13

No not yet. Will look at it tomorrow

This has to be fixed before we can deliver the chart to the public of course


Bug: not a git repository

Expected Behavior
Expecting to View Stories
Actual Behavior
$ club story
Loading... ⣾ fatal: not a git repository (or any of the parent directories): .git
(node:22132) UnhandledPromiseRejectionWarning: Error: Command failed: git branch
fatal: not a git repository (or any of the parent directories): .git

    at checkExecSyncError (child_process.js:621:11)
    at Object.execSync (child_process.js:657:15)
    at Object.<anonymous> (/usr/lib/node_modules/clubhouse-cli/build/bin/club-story.js:141:46)
    at step (/usr/lib/node_modules/clubhouse-cli/build/bin/club-story.js:33:23)
    at Object.next (/usr/lib/node_modules/clubhouse-cli/build/bin/club-story.js:14:53)
    at fulfilled (/usr/lib/node_modules/clubhouse-cli/build/bin/club-story.js:5:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:22132) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:22132) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Loading... ⣽

Steps to Reproduce
npm -g install clubhouse-cli
club install
club story

Yeah - this happens because the command was not passed a story ID, so it tries to pull the story ID from a git branch. We should catch the lack of a git repo and just exit.

In the --help there is also no indication that an ID needs to be passed

Currently, it is the first line of the usage in --help:
Usage: club-story [options] <id>

Sorry I was looking at club --help


Check the permissions on meizu Note6(Flyme <IP_ADDRESS>Q | Android 7.1.2) device always return true.

Overview

Cannot judge the status of permissions correctly. Check the permissions on meizu Note6(Flyme <IP_ADDRESS>Q | Android 7.1.2) device always return true.

Environment

PermissionsDispatcher library version is 3.2.0.
On Meizu Note6(Flyme <IP_ADDRESS>Q | Android 7.1.2) device.

Related to https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/303 ?
You need to give us the documentation for how we can support Flyme OS in English. Otherwise, we are not able to start discussing if we can support Flyme OS or not.

@iflytek-duan can you give us how we should fix the logic?

@shiraji @hotchemi
Thx.
I found the cause of the problem in the Flyme community, and Flyme always returns true to the native permission by default. They have used their own schemes for authority management, and they have not yet merged the two so that the problem can arise.
My English is bad, I hope you can understand my meaning.

Thank you but unfortunately we can't understand Chinese..😢
Do you have any suggestion? 🙇 @iflytek-duan

Not yet. If I have a better solution, I will reissue issues.@hotchemi


Task/UI redux

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 51.772%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
263

Relevant Lines:
508

💛  - Coveralls


c style function for run_evals

Current dependencies on/for this PR:

main

PR #52   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 5, 12:57 AM EST: @willseltzer merged this pull request with Graphite.


Bump to version 4.3.5 for draft orders support

Bumping gem version to 4.3.5 for releasing support for draft orders

 MONDAY: Update the Shopify API gem to include support for Draft Orders

@EiNSTeiN- Already published this new version, closing.


Computation of intersection between more than 2 faces

Is this correct?
https://github.com/liberostelios/urban-morphology-3d/blob/fba6e83a773ca6948438d85c6277226bc83406c5/geometry.py#L184-L185
In most cases len(polys)==2, but if len(polys)>2 wouldn't these lines give the wrong intersection result?

In theory not, because this calculation is done in a per plane base, so there can be more than two polygons that are on the same plane and need to be intersected. Think of two buildings, one having a long polygon on one side and the other one touching it at two different polygons on the other side.
I think that's the case, here. Unless I am missing something.

Just realised you are right, actually. At the first intersection, we already lost the rest of the polygon. This needs to be implemented in a way that all possible intersections are taken into account.


Spurious unused-parameter error

The following code:
    pub trait T1 {
    }

    pub trait T2<X>
        where X: T1
    {
    }

    pub struct S<A, B> where A: T1, B: T2<A> {
        b: B,
    }

produces the following error message:
error[E0392]: parameter `A` is never used
  --> src/main.rs:16:18
   |
16 |     pub struct S<A, B> where A: T1, B: T2<A> {
   |                  ^ unused parameter
   |
   = help: consider removing `A`, referring to it in a field, or using a marker such as `std::marker::PhantomData`

But I think this is valid code, as A was used (in the definition of B).
And, incidentally, if you try to follow the error message's advice and use std::marker::PhantomData to make:
    pub trait T1 {
    }

    pub trait T2<X>
        where X: T1
    {
    }

    pub struct S<A, B> where A: T1, B: T2<A> {
        a: std::marker::PhantomData<A>,
        b: B,
    }

you get the error:
error: `core::marker::PhantomData` is not supported (note: you may be able to add a Verus specification to this function with the `external_type_specification` attribute) (note: the vstd library provides some specification for the Rust std library, but it is currently limited)
  --> src/main.rs:16:5
   |
16 | /     pub struct S<A, B> where A: T1, B: T2<A> {
17 | |         a: std::marker::PhantomData<A>,
18 | |         b: B,
19 | |     }
   | |_____^

error: aborting due to previous error

It seems that the error message shouldn't suggest using something that Verus doesn't support.

This is a restriction of rust's not something we can do anything about. We can, however, add support for PhantomData, which is easy to do thanks to the new external type supports. I've now done so in dddb344ffb92dd9554cbd88aa6e0dfb4f8387811.


Tooltip wrapped toggle buttons break highlight

For, ToggleButtons wrapped in a tooltip, the toggle highlight doesn't work.

I believe this may be similar to #13206

[ x] The issue is present in the latest release.
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Tooltips break toggle buttons highlighting behavior.
Expected Behavior 🤔
I expect Tooltips to not affect highlighting behavior.

Steps to Reproduce 🕹
https://codesandbox.io/s/lingering-bird-6zrc4?fontsize=14

Context 🔦
I wanted to put a tooltip on the buttons so users know what the buttons do.

Your Environment 🌎

Tech
Version

Material-UI
v4.5.2

React
16.11.0

Browser
firefox 69

TypeScript
n/a

We have covered this problem a couple of times already. They are 3 possible approaches, 2 you can leverage today.

Forward the prop to the write element (use a "prop catcher")
Apply the tooltip to the label:

      <ToggleButtonGroup
        value={mode}
        exclusive
        onChange={(e, newValue) => setMode(newValue)}
      >
        <ToggleButton value="kill">
          <Tooltip title="Set mode to kill">
            Kill
          </Tooltip>
        </ToggleButton>

For Material-UI to avoid the cloneElement API: #12921.

@joziahg Yes, I think that the issue you have linked is related, please upvote #12921 if you would like the radio group's solution generalized.

Forward the prop to the write element (use a "prop catcher")

Could you give me a link with some code doing this? I would like to adapt this into our codebase.

We are doing this method on our ToggleButton however in adding the wrapping Tooltip it's breaking the ToggleButton styles, they are no longer grouped and instead look like two separate buttons. Do you have a workaround for this or do we need to specifically overwrite the styles to make it appear correct?
Without Tooltip

With Tooltip

I'm starting to thing this should be supported by ToggleButton by default
Maybe pass a prop to ToggleButton like tooltip="ButtonText" so it automatically creates a tooltip for it.

Agreed with @modbender. That would be more useful than having to manually juggle the props forwarding!

That must be a slot prop, because many projects use their own fancy themed tooltips

So far I've had success by applying the tooltip inside the ToggleButton, but using absolute positioning to achieve the full hit area of the ToggleButton.
<ToggleButton value={value}>
    Option 1
    <Tooltip title="Option 1 description">

    </Tooltip>
</ToggleButton>


update Miniconda2 to Miniconda3

Failures in Python 3.5 may be remedied by swapping out Miniconda2 for Miniconda3 with building TravisCI test environments.
This was part of the solution for correcting the segmentation fault: code 139 error in pysal/splot that we were seeing.

I don't think the failures are related to that. Because we create a new environment with a specific python version anyway (with https://github.com/darribas/contextily/blob/master/.travis.yml#L19).
But, that said, it is certainly a good idea to switch to download the Miniconda3 version.

@jorisvandenbossche yep, it did not completely fix the issue as it did in splot. Now rasterio seems to causing issues, both with and without - conda config --set channel_priority strict

related to #54

To repeat what I said above: updating to Miniconda3 is a good idea, but it is not related to testing of python 3.7 or not (since we create new environments anyway and don't use the base miniconda install)

Miniconda update resolved.


Wrong username in repo URL

Hi,
Please change the repo URL on package "featuretoggle-lib-js" from
<EMAIL_ADDRESS>to
<EMAIL_ADDRESS>Also, please remove the "featuretoggle-lib-js-2" package, which is a duplicate I registered too make sure the second URL was valid.
Thanks

done


unexpected behaviour with amplitude modulation

I'm getting a steady tone from the following code when I would expect silence. Is the oscillator interpreting the data from a signal object differently than a number ?
function setup(){
var mod = new p5.Oscillator();
mod.disconnect();
mod.setType('square');
mod.freq(1);
mod.amp(0.0);
mod.start();
var car = new p5.Oscillator();
car.setType('sine');
car.freq(440);
car.amp(mod);
car.start();
}
EDIT: It sounds to me like the signal is being mixed with the original. Is this intentional ?

I'm having a very similar issue. I'm making a synthesizer keyboard, and I'm using envelopes with the oscillators for ADSR and for some reason when I load up the page it's already playing the oscillators, regardless of whether or not I played anything on the keyboard. And interestingly, this only happens in Chrome. It works completely fine in Firefox.

With much love and respect to the brilliant people working on this sound library, I would like to strongly recommend that this bug to be prioritized because it's a year later and this issue still exists, and not only that, it renders a lot of basic audio synthesis unreliable.
I've tested on the most recent p5.sound.js (v0.3.6 2017-10-25) in Chrome, Firefox, and Safari using a 2016 macbook PRO running Sierra 10.12.6 (just to be EXTRA specific).
in kimon-satan's example, we should expect a bipolar modulator signal with an amp of zero to multiply all carrier signal values to 0, but instead, a non-zero value is being multiplied to all carrier signal values. And that value is inconsistent, depending on the browser.
I have made a few sketches outlining the issue:
CASE 1: http://alpha.editor.p5js.org/datramt/sketches/BJqRUVsJf
In the above example, I converted the bipolar modulator signal to unipolar. Despite the fact that my waveform FFT of the disconnected mod signal correctly displays the desired signal range (er, as I expect it anyways), the audio behaves otherwise, and never truly reaches zero.
CASE 2: http://alpha.editor.p5js.org/datramt/sketches/ByO-GVoyz
This is simply another attempt, but using a square wave mod signal
CASE 3: http://alpha.editor.p5js.org/datramt/sketches/SJyNDVsyz
I wanted to try to find the zero-point of the audio signal. In order to do that I had to add a considerable amount of DC. In chrome, it was -0.7 DC; in Firefox and Safari, it was -0.5 (ish)
Does disconnecting a source from the audiocontext convert its behavior into a unipolar signal? If so, this should be consistent across browsers, and it should be reflected in the FFT.waveform()
Also if that's the case, I'd propose that disconnected sources behave as bipolar unless scaled otherwise as is the case with the FFT.waveform()
If it is indeed behaving as you all desire, then I think we could benefit greatly from better documentation, as it took me hours to debug what I thought was rather simple synthesis concepts.
Thanks and <3
Dan

This issue took me a long time to understand, but I think I finally know what is going on here.
The .amp() method accepts a number and/or another oscillator object, in this case, you are passing in an oscillator object as a modulator signal.
It seems to me that if you intend to do amplitude modulation, for it to be a balanced bipolar signal, you need to initialize the carrier .amp() method to the number 0 before you connect the carrier amplitude to the oscillator object using the same method, .amp(). In other words, you need do both:
car.amp(0);
car.amp(mod);

If you wanted to do frequency modulation, it is similar, but there is more of a reason why one might want this sort of functionality. If you set car.freq(440) then car.freq(mod), then you would have a base frequency of 440 Hz, and the modulation will be +/- values according to whatever value is in mod.amp().
So the confusion here—I believe—is this: by default, the amplitude of a signal is set to some non-zero value depending on the browser. If you never explicitly override that non-zero value by passing in the number 0 into .amp() then there will be DC offset. It's as though you have a base amplitude of, say, 0.5, and the modulation is +/- values from the 0.5.


Use of Kingfisher with Alamofire - SessionDelegate - Xcode 12

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
Showing All Errors Only
'SessionDelegate' has different definitions in different modules; first difference is definition in module 'Alamofire.Swift' found method
Xcode 12:
Add Pods of Alamofire and Kingfisher
Build Project

I ended up forking Kingfisher and just applying the name space for the SessionDelegate.
https://github.com/TrueRowing/Kingfisher/commit/248b225fbc50340f24b5ff381d34258b320d3fde

I don't have this issue when trying in a sample project installing both the latest versions of Kingfisher (5.15.3) and Alamofire (5.2.2). It might be either a version issue or a local project setting problem. And it is not strange that CocoaPods is generating the ObjC compatible header by default, so it is still triggering #1517.
@christophercotton That fix is nice and I will also add it to this repo so we can solve it in any dependency manager.

@onevcat it happens with Alamofire 4.x. Which sadly we are still on for one product. Though it would probably conflict with any other project that had a SessionDelegate. Thanks for adding the change.

Resolved in 5.15.4
Thanks @onevcat


new virus false positive - Windows Defender, UNINSTALL\VulkanRT<IP_ADDRESS>

This seems related to the previus case: https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/issues/474
This morning, 3/31/2017, Windows Defender on Windows 10 x64 Pro reported the following:
"
The following error occurred: Error code 0x80070057. The parameter is incorrect.
Category: Trojan
Description: This program is dangerous and executes commands from an attacker.
Recommended action: Remove this software immediately.
Items:
file:C:\Program Files (x86)\VulkanRT\<IP_ADDRESS>\UninstallVulkanRT.exe
file:C:\Program Files (x86)\VulkanRT\<IP_ADDRESS>\V.ico
regkey:HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\VulkanRT<IP_ADDRESS>
regkeyvalue:HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths\G:
regkeyvalue:HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths\J:
uninstall:HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\VulkanRT<IP_ADDRESS>
Get more information about this item online.
"
My virus and spyware definition versions are 1.239.494.0.
I don't know if this is an MS issue or a Vulkan one, but it looked like last time, Khronos was able to do something to resolve.

In general, we do try to prevent our installers and uninstallers from being flagged by antiviruses, but it's essentially impossible to avoid it entirely. In this case, you're using a fairly old runtime (I think we released <IP_ADDRESS> sometime around July or August). There's really nothing we can do to prevent old installers from being flagged, since we don't change them. All we can do is release newer installers where we attempt to resolve the issue.
You said you're not sure if it's an MS issue or a Vulkan one. It's really an MS issue, since it's their software that's falsely reporting a virus, but like you said we do have some tricks to change around what the software reports (essentially we just recompile with different options to cause the code to look different).
Since you're reporting this against an old runtime, there's not really anything I can do except report the false positive to MS (and they would likely ignore me). If this issue exists for the newest (<IP_ADDRESS>) installer, then it's worth making sure we avoid the problem in our next SDK, but I would be surprised if Windows Defender was flagging the newest runtime without us having heard about it.
Since we can't really do anything about antiviruses flagging old runtimes, I'm going to close this issue. My advice is to update your runtime, either by updating your graphics drivers or by installing an SDK (you can feel free to manually uninstall the <IP_ADDRESS> runtime if your system is unhappy with it). If you find that your system flags the <IP_ADDRESS> files, then please do reopen the issue, but there really isn't anything we can do about old installers, except report them to the antivirus vendor.

Thanks for the info.  I didn't realize I had an old runtime.  I'll get the new driver.

For anyone else trying to search for this issue, I am receiving similar warnings from Windows Defender. It's being classified as:
Trojan:Win32/Suweezy
Trojan:Win32/Xadupi
It appears to be in version <IP_ADDRESS> and is matching all of the files in the directory, including LICENSE.txt, VULKANRT_LICENCE.rtf, and V.ico. This suggests to me that this isn't merely a false positive, but that the malware is actually using the Vulkan runtime and Microsoft has incorrectly flagged Vulkan because it arrived in a sample.

The way I read the error message from @jbhurst, I don't think it was finding anything wrong with the files that the runtime installed. It looks to me like it simply believes you should remove them because they were created by the installer and it thinks the installer is a virus. It also says that the registry keys that the runtime created should be deleted, and the registries are in integral part of Windows (so not a virus). So I think it's just saying you should revert everything that the installer did. I can't say if that's the same for @ironiridis, since I don't have the error message, but my guess would be that it's the same.
Also, <IP_ADDRESS> is more than a year old, and was back before we had taken any measures to avoid antivirus false positives. So it doesn't surprise me that Windows would think that one is a virus. We've sent runtimes to antivirus vendors before, and every response we've received has indicated that it was a false positive. I can't remember if we've had <IP_ADDRESS> specifically tested, but I'd be very surprised if that was a virus.
On top of that, running the <IP_ADDRESS> runtime installer through VirusTotal, which aggregates the results of a number of different antiviruses says that 0 / 62 antiviruses flag it as a virus. This makes me feel strongly that Windows Defender is simply reporting a false positive.

I have the same warning with Windows Defender now.
I'm using VulkanRT <IP_ADDRESS> which is included in latest nvidia driver.

If Windows Defender is flagging <IP_ADDRESS> as well, then we probably have a problem. I just ran Windows Defender on the runtime installers for <IP_ADDRESS>, <IP_ADDRESS>, and <IP_ADDRESS> and Windows Defender didn't flag any of them. I'm using virus definition version 1.239.506.0 (same as @ironiridis). Enough people have reported this issue that I'm quite sure this is a real issue — my computer must just be different in some way.
I'm using Windows 10 Home, Version 1607, OS Build 14393.953. If any of you could report the exact version of Windows and of your virus definitions, that would be helpful. Ideally, I'd like to figure out a way to get Windows Defender to mark a runtime installer as a virus on a machine I have access to. If I can't do that, then all I'll be able to do is file a false positive report with Microsoft (which I'll probably do regardless).

Windows Defender catches <IP_ADDRESS> for me too:
"The following error occurred: Error code 0x80070057. The parameter is incorrect.
Category: Trojan
Description: This program is dangerous and executes commands from an attacker.
Recommended action: Remove this software immediately.
Items:
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\LICENSE.txt
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\UninstallVulkanRT.exe
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\V.ico
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\vulkaninfo.exe
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\vulkaninfo32.exe
file:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>\VULKANRT_LICENSE.rtf
folder:C:\Program Files (x86)\vulkanrt
folder:C:\Program Files (x86)\vulkanrt\<IP_ADDRESS>
regkey:HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\VulkanRT<IP_ADDRESS>
regkeyvalue:HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths\C:\Program Files (x86)\Intel\Bluetooth
uninstall:HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\VulkanRT<IP_ADDRESS>"
Identifies it as Trojan:Win32/Xadupi and Trojan:Win32/Suweezy
https://www.microsoft.com/security/portal/threat/encyclopedia/entry.aspx?name=Trojan%3AWin32%2FXadupi&threatid=2147709752&enterprise=0
https://www.microsoft.com/security/portal/threat/encyclopedia/entry.aspx?name=Trojan%3AWin32%2FSuweezy&threatid=2147716113&enterprise=0

VirusTotal report for <IP_ADDRESS> that was included in latest Nvidia drivers:
https://www.virustotal.com/en/file/1f30c3ec401b2af80a528550020667743a60b2fc8d59621f3774ff2a1a8685b7/analysis/
SHA256:	1f30c3ec401b2af80a528550020667743a60b2fc8d59621f3774ff2a1a8685b7
File name:	VulkanRT-Installer.exe
Detection ratio:	2 / 61
Analysis date:	2017-03-31 20:21:33 UTC ( 35 minutes ago )

Just got new definitions for Windows Defender, version 1.239.517.0, still same detection of v<IP_ADDRESS> files.

OS: Windows 10 Pro, Version 1607 (Build 14393.969)
Defender: Antivirus: 1.239.517.0, Spyware: 1.239.517.0
Vulkan: <IP_ADDRESS>
But scanning the folder now manually does not show any results?

I just submitted a false positive report to Microsoft's support center with the <IP_ADDRESS> runtime installer. Hopefully they'll be able to do something.
It looks like I'm running very nearly the same OS as @Maik268, which unfortunately really doesn't clear anything up. I'm running a full system scan now with <IP_ADDRESS>, <IP_ADDRESS>, and <IP_ADDRESS> all installed. Hopefully that will flag something, but we'll see. I'll post anything new that comes up here.

I actually got a very quick response from Microsoft. I've pasted the worthwhile part below:
The Microsoft Malware Protection Center (MMPC) has investigated the following file(s) which we received on 3/31/2017 2:09:39 PM Pacific Time.
Below is the determination for your submission.

========
Submission ID MMPC17033131569576

  Submitted Files
  =============================================
  VulkanRT-<IP_ADDRESS>-Installer.zip [Not Malware]
  +---VulkanRT-<IP_ADDRESS>-Installer.exe [Not Malware]

Analyst Comments
================
-- 3/31/2017 2:27:04 PM --
This has been identified as an FP (false positive) and these false detections have been fixed and will be released in VDM build 1.239.530.0 and above.
SDN has been issued for the signatures and detections should not happen anymore for cloud-connected clients.

Your submission was scanned using antimalware definition version 1.239.517.0.
========

I have no idea when this will go live, but it sounds like it should be fixed in the near future. Whenever this does get released I'll check if it only applies to <IP_ADDRESS>. If that's the case I'll just submit all of the runtime installers to try to get Windows Defender to stop flagging them. I'm going to close this issue now. If 1.239.530.0 releases and the problem isn't fixed, then we'll reopen the issue.

I updated to 1.239.530.0 definitions and they seem to play nicely with both <IP_ADDRESS> and <IP_ADDRESS>.


Added Panel as option to Publication Venue

Panel is now included as an option for the publication venue choices.

It should come before Other. Other should be last thing in list.


[fix][schema-understand][docs] Minor correction in producer side step 1

Motivation

The producer side section states ...  Pulsar extract schema definition from the POJO class and construct the....

Modifications

Updated to ...Pulsar extracts schema definition from the POJO class and constructs the ...

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): no
The public API: no
The schema: no
The default values of configurations: no
The wire protocol: no
The rest endpoints: no
The admin cli options: no
Anything that affects deployment: no

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[x] doc
(Your PR contains doc changes) - It's a documentation update

[ ] doc-complete
(Docs have been already added)

Thanks @Anonymitaet for your time.


Add support for Android for requestAnimationFrame

Based on the information from canIUse.
Fixes #704.

Hi @ruiaraujo, can you give us a but more info here?
https://cdn.polyfill.io/v2/docs/contributing/common-scenarios#adding-browsers
Particularly we need to know we're not going to break older versions of Android if they choke on the polyfill code.  If you have devices to hand and can run some tests, that would be very helpful.

I have running with always|gated for a few months now and it seems to be fine.
But I will pick up a jsFiddle and test some old browsers.
Also, it seems I should also update the configs of the dependencies of rAF like performance.now since also has no android targets.

I tried to find an Android 3 device, physical or emulated. I have no access to a physical device and browserstack, saucelabs, crossbrowser-testing do not offer android 3 emulators, I couldn't find one to install on my machines either. I then looked at gs.statcounter.com data for android 3 and found 0% usage.
If anyone has an android 3 device, would you be able to visit this page and post a screenshot of the result into this issue?

I have visited that page on every Android version from 2.2 to 4.3. The test fail on Android 2.x.
Screenshot of the 3.0 emulator.

Thanks! The polyfill not working for 2.x is okay as our baseline support for android is >=3.


DX: Migrate from Firebase Cloud Functions to Vercel Serverless Functions

We use Firebase Cloud Functions today, mostly for things that we can't trust the client for (user balance modifications; referencing Stripe, email, and other secret keys). However, it's bad that to do any server-based work we have to drop into Firebase Cloud Functions; it adds a pretty big layer of friction to development. FCF is bad because:

Slow to test

Have to enter a bunch of command line commands correctly to spin up
Doesn’t hot reload

Even more annoying to deploy

Needs to remember to go do something right after committing
Not in lockstep with our Git code

Untyped?

Seems to pass through api-call.ts which breaks the typing

The nicest thing about FCF is the built-in authentication that works with Firebase Auth, which allows the function to act on behalf of a particular user. We could just build this ourselves using tokens/cookies. Here are some examples:

https://blog.logrocket.com/implementing-authentication-in-next-js-with-firebase/
https://colinhacks.com/essays/nextjs-firebase-authentication
https://github.com/gladly-team/next-firebase-auth

These use the client Firesbase lib instead of the Admin SDK but it's unclear to me what functionalities on the Admin SDK we actually need; I think we could still use the Admin SDK in Vercel, if necessary.
(I'd happily pay a M$ 20K bounty just for this, fwiw)

Officially offering a $256 USD cash bounty, or the equivalent in M$, for anyone who wants to take this on.
Manifold employees are eligible. (FWiW this means if I end up implementing this, I'm going to have Manifold pay me M$ 25,600).
If you'd like to start work on this, please say so in this thread so we don't waste anyone else's time!

am unilaterally revoking the bounty. future bounties should be made via Manifold

and now unilaterally closing!
the more I learn, the less I believe in serverless


Deploy issue

Hello, @pmac
I'm having a problem deploying this deployer app to a new dokku instance.
Step 7 from the installation instructions is driving me to the following error:
Step 8/20 : RUN groupadd -g ${GROUP_ID} dokku
 ---> Running in 8ad22fcf6a7b
groupadd: GID '0' already exists
remote: The command '/bin/sh -c groupadd -g ${GROUP_ID} dokku' returned a non-zero code: 4

Thanks

Hey! I didn't know anyone else had found this :) So the $GROUP_ID variable should be coming from the values found in step 5. If you've run those commands as root though it would be 0 and therefore cause this issue. I was thinking it'd be run as the dokku user on the server. So maybe that's the issue? If you're running everything as root you can delete lines 10 and 11 from the Dockerfile.


Reduce selector overuse in v2 branch.

Right now the code will create new selectors to check for EOF, even though each connection now has one. We should probably stop doing that. :D

Codecov Report

Merging #1139 into v2 will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff          @@
##             v2   #1139   +/-   ##
====================================
  Coverage   100%    100%
====================================
  Files        22      22
  Lines      1976    1981    +5
====================================
+ Hits       1976    1981    +5

Impacted Files
Coverage Δ

urllib3/util/connection.py
100% <ø> (ø)
:arrow_up:

urllib3/sync_connection.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

:tada:


Fixes passing caddy env variables from #1016

Should fix #1016, turns out you were using the key to check for '{' instead of the value @dunglas .

🤦
Thank you very much! I should have added a test...

Btw turns out the unnecessary work from the logger was coming from caddy

Thanks!


Feature request: Create announcements slider for multiple announcements

First of all, many thanks for this amazing plugin. Much appreciated!
Now, to my request:
When there are multiple announcements, one has to refresh the page to see the next one, and so on.
My humble request would be to create a sort of announcement slider where a user can simply view an announcement, dismiss, press next to view next one, and so on.
Maybe also add a setting where admin can choose to view them with most recent first, or oldest first, etc.
Otherwise thanks again!
Kind regards.

Thanks for the suggestions, interesting ideas.
Unfortunately, I don't have time to invest on this plug-in at the moment, so don't hold your breath...
I do welcome pull requests though 😉


Inline "small" systems into the multithreaded executor

Objective
Minimize overhead from scheduling large numbers of systems with very little work to do. Partially address #7208.
Solution
Keep a exponential moving average for how long it takes to run each system. If a system has historically run in under 2 microseconds, run it inside the multithreaded executor.
The threshold is currently hard-coded and is rather conservative to avoid potentially inlining too many systems and forcing it large sections to run single threaded.
TODO:

[ ] Defer inline execution until all non-inlinable system tasks are spawned to avoid blocking
[ ] Add an escape hatch for cases where systems have highly kurtotic behavior.

Performance
TODO

With #11906 now running the multithreaded executor immediately after every system, we can achieve similar results without needing to inline the systems. I've also come to realize that running systems inline is likely an all around bad practice given that it potentially blocks starting new systems even without a strict before/after relationship, and that's a huge risk in any cooperative task scheduler. Closing this out.


python3 compatible

passes travis 3.6 test
existing 2.x tests pass
note: i bumped the version; feel free to alter

Just to say, I also had troubles using the released version on Python 3.6, so this PR should really be merged, in my view.


Handing promise rejections from GuildAuditLogs#build to the user

Please describe the changes this PR makes and why it should be merged:
See #1471
The not catchable rejection is caused by fetching a rejection when fetching webhooks or invites.
This will take care of that.
Appending a .catch(reject); would also work.
Not sure what is the preferred solution here, both will lead to the same result.
Semantic versioning classification:

[ ] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Wouldn't it also be the same but better just to return the Promise.all without returning a new Promise()? Technically we shouldn't need to create a promise just to resolve a Promise.all...


逻辑回归计算中更换数据集之后出现error

Issue Type
Bug
Source
source
Secretflow Version
secretflow 最新版
OS Platform and Distribution
MacOS 13.0
Python version
3.8.13
Bazel version
No response
GCC/Compiler version
No response
What happend and What you expected to happen.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [8], in <cell line: 22>()
     20 # Validate the model
     21 X_test, y_test = load_test_dataset()
---> 22 auc=validate_model(W,b, X_test, y_test)
     23 print(f'auc={auc}')
     24 print(type(x1))

Input In [5], in validate_model(W, b, X_test, y_test)
      4 def validate_model(W, b, X_test, y_test):
      5     y_pred = predict(W, b, X_test)
----> 6     return roc_auc_score(y_test, y_pred)

File ~/opt/anaconda3/envs/secretflow/lib/python3.8/site-packages/sklearn/metrics/_ranking.py:560, in roc_auc_score(y_true, y_score, average, sample_weight, max_fpr, multi_class, labels)
    553         raise ValueError(
    554             "Partial AUC computation not available in "
    555             "multiclass setting, 'max_fpr' must be"
    556             " set to `None`, received `max_fpr={0}` "
    557             "instead".format(max_fpr)
    558         )
    559     if multi_class == "raise":
--> 560         raise ValueError("multi_class must be in ('ovo', 'ovr')")
    561     return _multiclass_roc_auc_score(
    562         y_true, y_score, labels, multi_class, average, sample_weight
    563     )
    564 elif y_type == "binary":

ValueError: multi_class must be in ('ovo', 'ovr')

Reproduction code to reproduce the issue.
%matplotlib inline

# Load the data
x1, _ = load_train_dataset(party_id=1)
x2, y = load_train_dataset(party_id=2)

# Hyperparameter
W = jnp.zeros((4,))
b = 0.0
epochs = 10
learning_rate = 1e-2

# Train the model
losses, W, b = fit(W, b, x1, x2, y, epochs=100, learning_rate=1e-2)

# Plot the loss
plot_losses(losses)

# Validate the model
X_test, y_test = load_test_dataset()
auc=validate_model(W,b, X_test, y_test)
print(f'auc={auc}')
print(type(x1))

Hi @data-alexpan ,
Please check https://scikit-learn.org/stable/modules/generated/sklearn.metrics.roc_auc_score.html

Did this model(logic regression) support multi-classification? i try some multi-classification datasets but it didn't work.


reset auth token on request if it has expired

Good work @coopaq!

@echessman "Why not put the refresh inside of the context?" Unsure of the pattern you are referring to here, but we could revisit this in the future as there may be some better practices in general with the basket+token+session work. We could also planned to recreate the cart on token timeout/refresh.


Unable to run in linux background using headscale.service

Everything is normal. However, after configuring the headscale.service file, headscale cannot be started normally. The following error message is displayed
headscale.service - headscale controller
Loaded: loaded (/etc/systemd/system/headscale.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2023-02-09 23:05:19 CST; 2s ago
Process: 29425 ExecStart=/usr/local/bin/headscale serve (code=exited, status=1/FAILURE)
Main PID: 29425 (code=exited, status=1/FAILURE)
Feb 09 23:05:19 VM-12-7-centos systemd[1]: headscale.service: main process exited, code=exited, status=1/FAILURE
Feb 09 23:05:19 VM-12-7-centos systemd[1]: Unit headscale.service entered failed state.
Feb 09 23:05:19 VM-12-7-centos systemd[1]: headscale.service failed.

Same here :(

Hello.  I am having the same issue as well.  I tried setting the service as both headscale / headscale as well as root / root with the same result:
Feb 11 21:26:31 headscale systemd[1]: headscale.service: Scheduled restart job, restart counter is at 386.
Feb 11 21:26:31 headscale systemd[1]: Stopped headscale controller.
Feb 11 21:26:31 headscale systemd[1]: Started headscale controller.
Feb 11 21:26:31 headscale headscale[11585]: 2023-02-11T21:26:31Z INF ../../../home/runner/work/headscale/headscale/derp_server.go:92 > DERP>
Feb 11 21:26:31 headscale headscale[11585]: 2023-02-11T21:26:31Z INF STUN server started at [::]:3478
Feb 11 21:26:31 headscale headscale[11585]: 2023-02-11T21:26:31Z INF Setting up a DERPMap update worker frequency=86400000
Feb 11 21:26:31 headscale headscale[11585]: 2023-02-11T21:26:31Z FTL ../../../home/runner/work/headscale/headscale/cmd/headscale/cli/server>
Feb 11 21:26:31 headscale systemd[1]: headscale.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 21:26:31 headscale systemd[1]: headscale.service: Failed with result 'exit-code'.
Worth mentioning there are two things in the instructions that confused me so I possibly got them wrong:
"Note that when running as the headscale user ensure that, either you add your current user to the headscale group:"
Seems like an incomplete statement.  For testing, I added root to the headscale group.
And if you follow the instructions to create the headscale user with --shell /usr/bin/nologin   (I corrected to /usr/sbin/nologin) you can't su headscale due to the nologin shell.  "This account is currently not available"
Thank you for any advise.

This issue can be done by running the command sudo headscale serve to generate the private key.
I guess you were using a sudo user to run headscale in the background with systemd.

@MDQ0512 @darientops
You can also replace the private key, the noise private key, and the db_path with  /var/lib/headscale/ instead of ./filename
It worked for me.

This is not an issue, but a support question, please continue the conversation on Discord.

I get this issue in Ubuntu 24.04 / Headscale 0.23.0 (also in 22.3 alpha 3/5/9).
sudo headscale serve returns this:
WRN Failed to read configuration from disk error="While parsing config: yaml: line 12: did not find expected key"
2024-10-23T07:23:11Z FTL ../runner/work/headscale/headscale/cmd/headscale/cli/root.go:48 > Error loading config error="fatal error reading config file: While parsing config: yaml: line 12: did not find expected key"
I do have this in config file:  /var/lib/headscale/
I followed the official install docs.


Unit Tests

Hello Deborah, thanks for putting this course together on pluralsight! It would be a great companion to include unit testing for this demo and would really complete this demo from start to finish. Would love to see some unit testing especially for the product-edit.component.
Thanks!

Thank you for the suggestion!
When I do my C# courses, I often add unit testing and assume the viewer is knowledgeable of the basics so I can just cover how to test the pieces we build in the course. But with Angular there are no basic resources for unit testing in the Pluralsight library yet. Hopefully some day!


how to make equalprg and formatprg use CocAction('format')

in my .vimrc I have this:
command! -nargs=0 Format :call CocAction('format')
xmap <leader>f  <Plug>(coc-format-selected)
nmap <leader>f  <Plug>(coc-format-selected)

Is there a way to make equalprg and formatprg use this CocAction('format') ?
The reason I want to do it is because I see a difference in formatting when I use the == vs :Format

  autocmd FileType typescript,json setl formatexpr=CocAction('formatSelected')

equalprg should does indent only.


Iteration 1 submission

Presented in front of the class, can you mark it

OK, ASAP..

Some comments:

Please use the issue template for submitting iterations
I could not understand from the page wiki (nor the mislestone1 in issues) what are the issues that belong to this iteration!
no git tag for this iteration
missing iteration retrospective to the wiki
no "class materials" section in wiki page, although it is clear that it is not a bad MVP already


Add uint8_t -> int8_t requant method

This is required when input to the model is in uint8_t format.
We need this quant op as a first layer.
One of such example is image data.
Related MR: https://github.com/tensorflow/tensorflow/pull/44580

@advaitjain PTAL

Ran into this issue today..
It looks like converting to .tflite networks that support uint8 input, as seen in the person-detector example, is not possible anymore. In other words, with the current TFLite converter, it is impossible to create a network that the ESP32 can natively use with its uint8 camera frames.

Hi @EliZucker right. UInt8 input case needs to be enabled.
The code/checks around these lines(Prepare from quantize.cc) will look like this:
  if (input->type == kTfLiteFloat32) {
    // Quantize use case.
    TF_LITE_ENSURE(context, output->type == kTfLiteInt8 ||
                                output->type == kTfLiteInt16);
  } else {
    // Requantize use case.
    // We allow Int16, UInt8 and Int8 inputs.
    TF_LITE_ENSURE(context, input->type == kTfLiteInt16 ||
                                input->type == kTfLiteUInt8 ||
                                input->type == kTfLiteInt8);

    // Output is restricted to Int8.
    TF_LITE_ENSURE(context, output->type == kTfLiteInt8);

    double effective_scale = static_cast<double>(input->params.scale) /
                             static_cast<double>(output->params.scale);

    QuantizeMultiplier(effective_scale, &data->output_multiplier,
                       &data->output_shift);
  }

Some of the checks are inspired from classic tflite's quantize.cc above.
Kept Float32 in above change. Shall I remove Float32 support completely?
Also, this line from my code:
    // Output is restricted to Int8.
    TF_LITE_ENSURE(context, output->type == kTfLiteInt8);

restricts output to Int8. Since we want to deprecate all other OPS to just keep Int8 OPS.
cc @advaitjain

Adding to the discussion between @EliZucker and @vikramdattu:
These lines should also be updated (I would hope that a unit test would catch this case):
https://github.com/tensorflow/tensorflow/blob/107b96da1ca5f0db752a11c4fae85ef1272ee175/tensorflow/lite/micro/kernels/quantize.cc#L73-L76
Additionally, since the TF_LITE_ENSURE checks that @EliZucker pointed out in the Prepare function are basically a repeat of the checks in Eval, I would be fine with removing this code block completely:
https://github.com/tensorflow/tensorflow/blob/107b96da1ca5f0db752a11c4fae85ef1272ee175/tensorflow/lite/micro/kernels/quantize.cc#L65-L71

@advaitjain
I get error when I run test for x86 (OS: MacOS Catalina 10.15.07)
tensorflow/lite/micro/examples/person_detection/person_detection_test.cc:30:24: error: argument to 'section' attribute is not valid for this target: mach-o section specifier requires a segment and section separated by a comma
__attribute__((section(".bss.NoInit"), aligned(16)))
                       ^
1 error generated.
make: *** [tensorflow/lite/micro/tools/make/Makefile:488: tensorflow/lite/micro/tools/make/gen/osx_x86_64/obj/tensorflow/lite/micro/examples/person_detection/person_detection_test.o] Error 1
make: *** Waiting for unfinished jobs....

Can you please help get pass the issue?

@vikramdattu I fixed some errors by using ESP-IDF Toolchain v4.0 for that example project. Might be the issue.

@EliZucker thanks for quick reply.
I got past this error by simply commenting out that attribute.
I now get one test fail even without UInt8 quant addition.
tensorflow/lite/micro/tools/make/gen/osx_x86_64/bin/person_detection_test_int8: FAIL - '~~~ALL TESTS PASSED~~~' not found in logs.
Testing TestInvoke
person data.  person score: -4, no person score: 4

person_score > no_person_score failed at tensorflow/lite/micro/examples/person_detection_experimental/person_detection_test.cc:103
no person data.  person score: -72, no person score: 72

@advaitjain @EliZucker
One more question:
I have added few more tests: QuantizeOpTestUInt8toInt8 and QuantizeOpTestUInt8toInt8NoZeroPoint.
How do I know if these are getting called? Is running x86 tests does this already?

@advaitjain @EliZucker manually tested this with a custom example I have created here: https://github.com/vikramdattu/tensorflow/commits/master
Please refer this README to build and run example on ESP32. [Please do ignore some of the unclean code]

@vikramdattu Can you please resolve conflicts? Thanks!

@vikramdattu Can you please resolve conflicts? Thanks!

@gbaned done! Please take a look again.

@advaitjain please take a look. Tests are added.
Please take a look at choice of values:
const float values[] = {64, 66, 68, 70, 72, 182, 184, 186, 188, 190};

These are values used for int8 test+128
const float values[] = {-64, -62, -60, -58, -56, 54, 56, 58, 60, 62};

@vikramdattu Can you please resolve conflicts? Thanks!

@gbaned conflicts are resolved. PTAL.

@vikramdattu Can you please resolve conflicts? Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@vikramdattu  Any update on this PR? Please. Thanks!

Hi @gbaned the PR raised is 4-5 months old and I have done multiple merges to update it.
Do you mind if I reconsider it for new PR?

@advaitjain Can you please assist on above comments from @vikramdattu. Thanks!

@advaitjain Any update on this PR? Please. Thanks!

With TFLM moving to its own GitHub repository, we are not going to be merging any TFLM specific pull requests in the TensorFlow repository starting today.
I am closing the current PR but please feel free to open a new PR in https://github.com/tensorflow/tflite-micro/.
https://groups.google.com/a/tensorflow.org/g/micro/c/W4DACgjPmOE


Number matching will be enabled "starting" Fed 27

Microsoft will enable number matching for all tenants starting Feb 27, 2023, not by Feb 27, 2023. This confused some customers.

Learn Build status updates of commit ee57ac1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory/authentication/how-to-mfa-number-match.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@juntakata Thanks for the correction! Sorry for delay. I committed the same change on my side to work around the branch conflict. you can see it live now. #please-close.


fix: Updates + icon to take user to select pages page instead of direclty importing a template

Description
When in add pages from template flow, if a user clicks on + icon in the templates list.
Current: the template gets added automatically
New: now user will be taken to page selection view(similar to when users click on template image)

Adds test case for + button now redirects to select pages
Adds test case for + icon in the similar templates

Fixes # (issue)
21200
Media
Type of change

Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/build-deploy-preview

/ok-to-test sha=e5ed2d7

/ok-to-test sha=67d2f8e

/ok-to-test sha=08d7af2

/ok-to-test sha=08d7af2

Hey @ramsaptami , Can you please do QA for this?
this PR fixes this issue: https://github.com/appsmithorg/appsmith/issues/21200
I've added some cypress tests and all of them are passing.

/build-deploy-preview env=release

This is working as expected, tested Use Template complete flow on the DP url.

/ok-to-test sha=b899529


release date

Hi,
can you tell me please if this project in development? and what is the estimated date to release?

It is in development. No release date to announce at this time.

Since this is what was holding up progress on andrewelkins/cabinet per #30 I too am eagerly awaiting the release of this.

@DiaaFares if you were still waiting you might want to check out https://github.com/mrakodol/Laravel-5-Bootstrap-3-Starter-Site

Just release an alpha build of the starter site. Need to add the readme on how to get it rolling, but it's on it's way.

Awesome would love to give it a try. Thanks.

@EHLOVader Thank you very much :)


bug: certificate typo

we have to edit the public/certificate.png only right? @hkirat

@hkirat  can you assign it to me?

Created dynamic description and fixed the typo.

@hkirat  Can you check this ?

@AyushShivhare79 I'm a beginner to open source. Can you tell me how you run tests for the certificate? I tried the same way, but I couldn't get it to run.


Fix issue 726: Missing selector in Broker resource for selecting security groups

Description of your changes
Missing selector in Broker resource for selecting security groups: add selectors for the securityGroup
Now can use next selectors:
securityGroupRefs
securityGroupSelector

Fixes https://github.com/upbound/provider-aws/issues/726
I have:

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

How has this code been tested

/test-examples="examples/mq/broker.yaml"

/test-examples="examples/mq/broker.yaml"


The reverb level indicator should be the other way around

Now it starts from the top; it should start from the bottom. Not that it really matters.

I've decided to leave this as it is now. Real-world use shows that there's not really any difference how it's presented, and also I guess that it's a bit more idiosyncratic this way.


Put Ludography after references in main.tex

Hi Josh,
Super glad you put this together and pushed us to handle this. I discussed it with the other paper chairs and we would like to follow exactly what you have. The only difference is we think the Ludography should come after the normal References since it is kind of an extra (appendix-like thing). Would you consider accepting this pull request and then I will refer to your repo in a blog post that we put up with some directions on Ludographies?

Great, thanks!


Images in tutorials not rendering on main site

The create your first chain tutorial has several embedded images. This page should show them. You can see they are listed in the source code https://github.com/substrate-developer-hub/tutorials/blame/3a784997b5f1b907ba0d11e10218ef86182e4359/tuts/create-your-first-substrate-chain/v2.0.0-alpha.5/background.md#L33
We've tried a few different ways to link to that image including an absolute path starting with /tutorials. @thisisvilla Do you know how we might fix these images?

nvm. @danforbes figured this on out. Image links can be written like ../assets/forks.png and the build process will insert the correct link.


Readme file updation

'GirlScript Summer of Code' needs to be added in the Open Source section in the Readme file.

Hi! Please assign this issue to me under GSSOC.


Model 1_80x80 ?

In your Data Processing README Part, you mentioned about three scaling factors 1_80x80, 2.7_80x80 and 4_80x80 and you have provided 2.7 and 4.0 pretrained models but no 1.0 model? Can you provide 1_80x80 model also.
Thank You

We provived the two models because they were used in APK.They are not pretrained models.

So is there any 1_80x80 model that you have trained and can share?


"For details:" Circular reference GitHub <=> seek4science

https://github.com/SysMO-DB/JERMOntology
says

Please visit http://seek4science.org/JERMOntology for details about contributing to the JERM

but
http://seek4science.org/JERMOntology
says only

The ontology is available online at GitHub - https://github.com/SysMO-DB/JERMOntology

Thanks for pointing this out. We intended having a dedicated page for
contributing suggestions and terms for the JERM ontology. For now I've
fixed it to point out our general contributors guide.
On Wed, 10 Feb 2016 at 11:45 Jon Olav Vik<EMAIL_ADDRESS>wrote:

https://github.com/SysMO-DB/JERMOntology
says
Please visit http://seek4science.org/JERMOntology for details about
contributing to the JERM
but
http://seek4science.org/JERMOntology
says only
The ontology is available online at GitHub -
https://github.com/SysMO-DB/JERMOntology
—
Reply to this email directly or view it on GitHub
https://github.com/SysMO-DB/JERMOntology/issues/1.


fix: line separator in test resources

Resolves #12

The issue is valid only for windows. Git eol=lf must be configure on client side to successfully pass the tests.


The gc frequency of e2e should be reduced, for example, adjusted to 30s

What would you like to be added?
Enhance e2e functionality
Why is this needed?
No response
How to implement it (if possible)?
NONE

Additional context
No response
I've read and agree with the following

[X] I've checked all open and closed issues and my request is not there.
[X] I've checked all open and closed pull requests and my request is not there.

fix #2604


Multiple Different designSize

What if I have multiple desingSize in Figma for example
I have These  first one is Size(365, 1060) for mobile,
Second one is Size(1440, 1440) for Web,
and it declared once here

I tried use that function inside build method for mobile and web widgets
 ScreenUtil.init(
      context,
// for web
      designSize: const Size(1440, 1440), // for mobile Size(365,1060)
    );

but I think isn't works well.

Need this feature as well

Duplicate of #469


The command "seed:generate user" does not exist.

While calling through Artisan Facade.
$modelNamespace = 'user';
Artisan::call('seed:generate ' . $modelNamespace, []);

Does it solved? If yes, maybe please write some description. Thank you.


Add event-wire

https://github.com/nodeca/event-wire
Decide yourself. That's a combination of mediator and responsibility chain paradygms + sugar for convenience. Simplifies creating apps with extendable logic. See example with before/after/on stuff.
This approach is used to build miracle nodeca app :).

Thanks for the suggestion but going to pass on this.


Simplify setup

Minor changes for convenience:

add a requirements file;
suggest using venv.

Thanks a lot for the improvements!


PHPUnit errors in SF5 when injecting service

Hi,
I'm having some issues when using this bundle as a service in SF5. Service is configured as follows:

I need to use ServiceRegistry, so in my class I inject it:

But when passing tests, I'm having this output:

As you can see, tests are passing OK, but a lot of warnings are appearing.
Maybe I'm not decraring properly the service?
By the way, my yaml config file:
nelmio_solarium:
    endpoints:
        foo:
            scheme: http
            host: '%env(resolve:SOLR_HOST)%'
            port: 8983
            path: /
            core: Foo_all
        bar:
            scheme: http
            host: '%env(resolve:SOLR_HOST)%'
            port: 8983
            path: /
            core: Bar_all
    clients:
        foo:
            endpoints: [foo]
        bar:
            endpoints: [bar]

Thanks in advance and hope you're allright,
Javi

Which version of this bundle did you use? It should be resolved on master.


Fix for ClientToProxyConnection.copy() not copying headers

Fix for https://github.com/adamfisk/LittleProxy/issues/271

This looks good to me. Thanks, @MediumOne. If nobody has any issues, I'll go ahead and merge.

LGTM!

Thanks, @adamfisk and @MediumOne. Merged.


Move some header files into 'inc' directory

This move facilitates header file sharing between projects that is
necessary in the UWP apps branch of this code (in TFS).

@jkotas , @janvorli , PTAL

LGTM


Re-Add Nginx PAM authentication

This PR re-adds PAM authentication as ruthlessly pulled out by myself in #188. Some more kinks to work out, this gets the build back in working order.

LGTM


Return history page

@nishant-cyro @priyank-gupta Return history page don't have any heading or way to go back

@bansalakhil - Thanks for pointing the issue, we will look into it and let you know when fixed.

@nishant-cyro Addressed this one in below PR.
https://github.com/vinsol-spree-contrib/spree_item_returns/pull/18


Initial Install Warning

Describe the issue / bug.

vue init simulatedgreg/electron-vue my-project
cd my-project/npm install
Console warning.

How can I reproduce this problem?
Above steps.
If visual, provide a screenshot.

Tell me about your development environment.

Node version: 9.2.0
NPM version: 5.6.0
vue-cli version: (if necessary) 2.9.2
Operating System: Windows 10 64

Fix is to pin "electron-debug": "1.4.0".


etcd-agent: cleans page cache when cleaning up

https://www.kernel.org/doc/Documentation/sysctl/vm.txt
https://github.com/torvalds/linux/blob/master/fs/drop_caches.c
I cannot directly write to /proc/sys/vm/drop_caches using Go (without sudo).
http://unix.stackexchange.com/questions/17936/setting-proc-sys-vm-drop-caches-to-clear-cache

the value you can read is whatever you put last, but it's not used anywhere,

We need to clean up page cache as Xiang suggested. Otherwise, the memory usage shown in grafana keeps increasing.
/cc @heyitsanthony @xiang90
Thanks.

LGTM

Thanks. Will merge in green lights.


Add a document with contribution guidelines

This gives us a place to point new contributors, as well as to document
our project practices.

r? @nix-rust

The part of this I'm really excited about is the issue labels. There are probably more to add, but here's a start!

@abbradar as a new contributor, would a document like this be helpful?

The [homu] link seems wrong.

Several more things which might be useful:

Code style (basic things, like "4 spaces").
Policies w.r.t. new APIs that are more or less agreed upon (use libc, provide wrappers to libc structures where it sounds a good idea).
Testing policy (i.e. don't forget to run cargo test at least for your compiler and platform).

(BTW I'll continue working on my patches later, as I'm a bit short of time now)

The [homu] link seems wrong.

Fixed, and added a link to the queue as well.

@abbradar thanks for the comments!

Code style (basic things, like "4 spaces").

I'm going to leave this out for now. I'm planning to make real progress on https://github.com/nrc/rustfmt/issues/434 and hopefully soon we'll be able to just say "run cargo fmt-diff" or whatever the command looks like.

Policies w.r.t. new APIs that are more or less agreed upon (use libc, provide wrappers to libc structures where it sounds a good idea).

I think these belong in the conventions doc. There's definitely more that needs to go in there though. Thanks for the suggestions!

Testing policy (i.e. don't forget to run cargo test at least for your compiler and platform).

Hm, I thought this would be implied by us having travis-ci set up. How do you think I could make it clearer?

Also cc: @posborne :-)

Travis forces the "tests should pass" policy but from my experience reminding that contributors should run final tests on their own machines somewhere can nevertheless reduce the volume of "Travis fails on this patch; can you please look?" messages from maintainers. An example would be yours truly -- I didn't have much Rust experience so I actually found out about cargo test because Travis has failed on one of my patches. That said, there's good chance it's just me having poor contributing discipline -- I imagine one would look around and find out if there are tests and how to run them for any project they want to contribute to.

It's probably a decent idea to include a small section on testing. Something that describes how to run the tests and instructs contributors to include tests with their PR when appropriate, etc.

Agreed.  I am working on some additional test infrastructure for several of the more exotic targets (ARM, bsd, ...) and will do my best to come up with a solution that would allow for tests to be run locally (using docker, qemu, etc.) in a way that matches what Travis will be running.  This should make it easier to both contribute to those platforms and avoid regressions.

@abbradar @arcnmx can you take another look?

That said, there's good chance it's just me having poor contributing discipline -- I imagine one would look around and find out if there are tests and how to run them for any project they want to contribute to.

No, your changes were great! This one's definitely on us. :-)

@posborne

come up with a solution that would allow for tests to be run locally (using docker, qemu, etc.)

That would be so great.

Looks good to me!

Looks good here too!

The moment the merge conflict and the build failure (how can either happen, with a completely new file that is not code ...) are resolved I propose to merge this.

I just squashed and rebased. Let's see how the on-behalf-of thing works.
@homu r=@fiveop

:pushpin: Commit 901f3e5 has been approved by @fiveop

:hourglass: Testing commit 901f3e5 with merge 6e99ad6...

:sunny: Test successful - status


Two paper-autocompletes on the same page

I have two paper-autocompletes on the same page. The first one worked great until I added the second one. Now, the dropdown for paper-autocomplete#2 shows up attached to the bottom of paper-autocomplete#1.

Never mind. This was a bug in my code.

Ok...btw, the demo page has two autocomplete components...one pulling from a hard-coded states' array and the other dynamically querying the github user api.


WFCORE-564¸Fix PersistentResourceXMLDescription parser

it now properly supports mixing attribute groups & wrappers
add support for multiple resources inside wrapper element
add option to override also marshaller insde parser definition

also add tests to make sure this works properly

Core - Full Integration Build 544 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Windows Build 966 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Linux Build 1282 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Linux Build 1282 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 3049, ignored: 68 Build time: 0:21:59

Windows Build 966 outcome was FAILURE using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests failed: 40 (40 new), passed: 3029, ignored: 68 Build time: 0:25:56
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveBlockCompletionCancelSlave: java.lang.AssertionError: block not present after 5000 ms
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveBlockCompletionCancelSlave: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation succeeded.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForFailure(DomainTestUtils.java:179)
	at org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.executeForFailure(OperationCancellationTestCase.java:1037)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveServerBlockRuntimeCancelMaster: java.lang.AssertionError: block not present after 5000 ms
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveServerBlockRuntimeCancelMaster: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation succeeded.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForFailure(DomainTestUtils.java:179)
	at org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.executeForFailure(OperationCancellationTestCase.java:1037)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveBlockModelCancelSlave: java.util.concurrent.TimeoutException: Operation timed out
	at org.jboss.threads.AsyncFutureTask.operationTimedOut(AsyncFutureTask.java:66)
	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:283)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveBlockModelCancelSlave: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation succeeded.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForFailure(DomainTestUtils.java:179)
	at org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.executeForFailure(OperationCancellationTestCase.java:1037)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testMasterServerBlockCompletionCancelMaster: java.lang.AssertionError: Multiple instances of block present: [-1150578475 -- {
    "access-mechanism" => "undefined",
    "address" => [

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testMasterServerBlockCompletionCancelMaster: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation succeeded.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForFailure(DomainTestUtils.java:179)
	at org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.executeForFailure(OperationCancellationTestCase.java:1037)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testMasterServerBlockRuntimeCancelMaster: java.lang.AssertionError: block not present after 5000 ms
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testMasterServerBlockRuntimeCancelMaster: org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation succeeded.
	at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForFailure(DomainTestUtils.java:179)
	at org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.executeForFailure(OperationCancellationTestCase.java:1037)

org.jboss.as.test.integration.domain.suites.OperationCancellationTestCase.testSlaveServerBlockRuntimeCancelServer: java.lang.AssertionError: block not present after 5000 ms
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)

##### there are 30 more failed tests, see build details

Core - Full Integration Build 544 outcome was FAILURE using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests failed: 1 (1 new), passed: 2826, ignored: 415, muted: 1 Build time: 0:48:50
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice: javax.xml.ws.WebServiceException: Could not send Message.
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:150)

retest this please

Windows Build 970 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Core - Full Integration Build 548 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Linux Build 1286 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Windows Build 970 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 3049, ignored: 68 Build time: 0:19:12

Linux Build 1286 outcome was FAILURE using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Execution timeout (new); tests passed: 2705, ignored: 53; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:03
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 548 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 2827, ignored: 415, muted: 1 Build time: 0:49:36

Linux Build 1287 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Linux Build 1287 outcome was FAILURE using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests failed: 9 (9 new), passed: 3045, ignored: 68 Build time: 0:20:29
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPS: java.io.IOException: java.util.concurrent.CancellationException: Operation was cancelled
	at org.jboss.threads.AsyncFutureTask.operationCancelled(AsyncFutureTask.java:70)
	at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:267)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPS: java.io.IOException: org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated
	at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:190)
	at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:327)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTP: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTP: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPWithSecureInterface: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPWithSecureInterface: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPSWithSecureInterface: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase.testHTTPSWithSecureInterface: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://[::1]:9999. The connection failed
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)

retest this please

Linux Build 1289 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Windows Build 972 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Core - Full Integration Build 550 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Windows Build 972 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 3049, ignored: 68 Build time: 0:20:08

Linux Build 1289 outcome was FAILURE using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Execution timeout (new); tests passed: 2705, ignored: 53; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:02
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 550 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 2827, ignored: 415, muted: 1 Build time: 0:48:40

Linux Build 1293 is now running using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d

Linux Build 1293 outcome was SUCCESS using a merge of d1184ed50e8b15c37a00b55da4f4d8dea1fef71d
Summary: Tests passed: 3049, ignored: 68 Build time: 0:21:59

Windows Build 976 is now running using a merge of a9e231ca8a7be8257e1304de583eae81462f601c

Linux Build 1295 is now running using a merge of a9e231ca8a7be8257e1304de583eae81462f601c

Core - Full Integration Build 554 is now running using a merge of a9e231ca8a7be8257e1304de583eae81462f601c

Linux Build 1295 outcome was SUCCESS using a merge of a9e231ca8a7be8257e1304de583eae81462f601c
Summary: Tests passed: 3049, ignored: 68 Build time: 0:18:27

Windows Build 976 outcome was SUCCESS using a merge of a9e231ca8a7be8257e1304de583eae81462f601c
Summary: Tests passed: 3049, ignored: 68 Build time: 0:19:30

Core - Full Integration Build 554 outcome was FAILURE using a merge of a9e231ca8a7be8257e1304de583eae81462f601c
Summary: Tests failed: 1 (1 new), passed: 2826, ignored: 415, muted: 1 Build time: 0:49:35
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[7, -8, 115, 19, 45, 35, 70, -57, -87, -53, -23, -117, 126, 68, -64, -97]} refers to an invalid bean group 150105ed-7dc9-49ed-aff8-73391db92d88
	at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:76)
	at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266)

Linux Build 1299 is now running using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09

Windows Build 980 is now running using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09

Core - Full Integration Build 559 is now running using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09

Linux Build 1299 outcome was SUCCESS using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09
Summary: Tests passed: 3049, ignored: 64 Build time: 0:18:14

Windows Build 980 outcome was SUCCESS using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09
Summary: Tests passed: 3049, ignored: 64 Build time: 0:18:24

Core - Full Integration Build 559 outcome was FAILURE using a merge of fdf5a7297982ca58b3706edfb35c09e69702ae09
Summary: Tests failed: 1, passed: 2826, ignored: 415, muted: 1 Build time: 0:50:53
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: java.lang.reflect.UndeclaredThrowableException: null
	at com.sun.proxy.$Proxy62.runTestMethod(Unknown Source)
	at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:77)

Linux Build 1307 is now running using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d

Windows Build 987 is now running using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d

Core - Full Integration Build 567 is now running using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d

Windows Build 987 outcome was SUCCESS using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d
Summary: Tests passed: 3049, ignored: 64 Build time: 0:18:47

Linux Build 1307 outcome was FAILURE using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d
Summary: Execution timeout (new); tests passed: 2705, ignored: 49; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:09
Build problems:
Execution timeout
Process exited with code 137

Linux Build 1308 is now running using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d

Core - Full Integration Build 567 outcome was SUCCESS using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d
Summary: Tests passed: 2828, ignored: 415 Build time: 0:51:22

Linux Build 1308 outcome was SUCCESS using a merge of ce811e402571d14b42ff5a3911b03801f81fe16d
Summary: Tests passed: 3050, ignored: 64 Build time: 0:22:12

retest this please
Problems on master-ignore:
http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=37837&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreMasterIgnoreIntegration

retest this please

@bstansberry you are right, something was wrong, replacement PR is #543