Message: no such element (".//a[@class='text-info cursor-pointer']")

Hello!
I burnt my RPI few days ago, and after installing/updating the complete previous version, I am now having this error in noip-renew script:
Message: no such element: Unable to locate element: {"method":"xpath","selector":".//a[@class='text-info cursor-pointer']"}   (Session info: headless chrome=86.0.4240.197)
I have just gitcloned the project few minutes ago (I saw a PR has been submitted to fix this, but it is not working here).
EDIT: Ohh no my bad, I did not gitcloned because it was saying that the folder was already there
Thanks for your help!

Self answering and closing the issue.
Git pull and then install/repair script fixed it 👍


[REVIEW] avneesh0612

GitHub Profile Link
https://github.com/avneesh0612/

My profile was reviewed before but I have made some changes :P

Looks good. Really like the blogs section.

maybe center align the contents of the discord status section?

okay thanks!

Things that I like:

The blog section ✨  It's really cool that you have the header images over there and cooler still that it's automated!
The typing animation is lit! Bonus points for being an svg

Things that I'd change:

I'm not sure if you need a separate section for this when you are linking to a link tree - but then again, it does catch the eye. Perhaps you could push it to either the top or bottom of your profile?
Another thing that I'd suggest: make it clear that it is a link tree. "Feel free to reach me out on any platforms here" -> Feel free to reach me out on any platforms on my LinkTree
I'd round off the corners of the Read More button at the end: I see that you've used an image there, perhaps a different one can be used?

okay, thanks!


[Bug Report] Bug in el-table sort-method

Element UI version
1.3.4
OS/Browsers version
Chrome
Vue version
2.3.3
Reproduction Link
https://jsfiddle.net/2mjjx3n8/1/
Steps to reproduce
See jsfiddle.
What is Expected?
Sort should work.
What is actually happening?
First or last row is not sorted.

https://jsfiddle.net/2mjjx3n8/3/
The returned value of sort-method is supposed to be a boolean instead of 1, 0 and -1. This is different from Array.sort. I'll update the documentation to address this.

The documentation is still wrong (or wrong again)

Remove immediately this post, please!!!
test: function(a,b){
return a.age - b.age;
}
in the current version.


Feature Request: Use a github repo as XML/SQL storage

Feature Request
As a user, I'd like to have a way to store my designs directly on a github repository and read back from it, so that work can be easily stored and shared with a team as part of regular daily work.
Longer description
Would be cool if we could use the GitHub API for signing in, list the repos one has available, then list the branches available in the selected repo, to finally look for a directory or file where to store (or consume from) the XML.
Extra Points: Adding a quick-save button that asks for a commit message with the preselected repo/branch/filename combo :wink:

+1

Nice idea! I am currently far too busy to implement this, but it generally sounds like a good idea. Alternative storage could be a Gist.


Cargo gets confused about hashes when switching between toolchain versions

Problem
error[E0460]: found possibly newer version of crate `la_arena` which `profile` depends on
   --> crates/syntax/src/algo.rs:126:18
    |
126 |         let _p = profile::span("into_text_edit");
    |                  ^^^^^^^
    |
    = note: perhaps that crate needs to be recompiled?
    = note: the following crate versions were found:
            crate `la_arena`: /home/joshua/.local/lib/cargo/target/debug/deps/libla_arena-30ef6779a35b7e2f.rmeta
            crate `la_arena`: /home/joshua/.local/lib/cargo/target/debug/deps/libla_arena-af7c500c62bd5e59.rmeta
            crate `la_arena`: /home/joshua/.local/lib/cargo/target/debug/deps/libla_arena-af7c500c62bd5e59.rlib
            crate `profile`: /home/joshua/.local/lib/cargo/target/debug/deps/libprofile-6846f1b303b1dfdb.rmeta

error: aborting due to previous error

Steps

I am not able to replicate this. The original steps I did were something like this:

git clone https://github.com/rust-analyzer/rust-analyzer/ && cd rust-analyzer
cargo +stable doc --document-private-items
git fetch origin pull/7341/head && git checkout FETCH_HEAD
cargo +nightly doc --document-private-items
cargo +stable doc --document-private-items

But I tried running that again and it works fine now, so I don't know what went wrong. Probably this is related to incremental somehow? Let me know if this should be moved to rust-lang/rust.
Possible Solution(s)
:shrug:
Notes
I don't understand how I constantly run into bugs the first time I compile a project :facepalm: Not always cargo bugs. But always bugs. The last one was https://github.com/rust-lang/cargo/issues/8838, the one before was https://github.com/rust-lang/rust/pull/71819, the one before that was https://github.com/rust-lang/docs.rs/pull/432. I think hello world worked, though.
Output of cargo version:
> cargo +stable --version
cargo 1.49.0 (d00d64df9 2020-12-05)
> cargo +nightly --version
cargo 1.50.0-nightly (75d5d8cff 2020-12-22)

Ubuntu 20.04, x86_64-unknown-linux-gnu

Hm, I'm unable to think of a way this could happen.  Unfortunately without a repro or more information, it will be pretty difficult to figure it out.
This isn't related to incremental.  I'm not sure if you're familiar with SVH. That is the hash that is stored in the rlib that causes this error.  The key factor is probably the git command which changed some HIR node or something causing the SVH to change, but somehow between commands Cargo didn't rebuild it.
There were some extra steps that happened before the steps you listed above.  Since there is a .rlib file, that means you ran cargo build at some point.
Also, /home/joshua/.local/lib/cargo/target is not a standard layout.  It can be helpful if you have any non-default settings to mention them as well.
Generally, showing all the output can help. Even better is to create a tarball of the target directory immediately after it happens.  If you can reproduce it at all, also adding CARGO_LOG=cargo::core::compiler::fingerprint=trace cargo build can help.

Hm, I'm unable to think of a way this could happen.  Unfortunately without a repro or more information, it will be pretty difficult to figure it out.
This isn't related to incremental.  I'm not sure if you're familiar with SVH. That is the hash that is stored in the rlib that causes this error.  The key factor is probably the git command which changed some HIR node or something causing the SVH to change, but somehow between commands Cargo didn't rebuild it.
There were some extra steps that happened before the steps you listed above.  Since there is a .rlib file, that means you ran cargo build at some point.
Also, /home/joshua/.local/lib/cargo/target is not a standard layout.  It can be helpful if you have any non-default settings to mention them as well.
Generally, showing all the output can help. Even better is to create a tarball of the target directory immediately after it happens.  If you can reproduce it at all, also adding CARGO_LOG=cargo::core::compiler::fingerprint=trace cargo build can help.

Also, /home/joshua/.local/lib/cargo/target is not a standard layout. It can be helpful if you have any non-default settings to mention them as well.

The only non-default settings I have are
> set | grep _HOME
CARGO_HOME=/home/joshua/.local/lib/cargo
RUSTUP_HOME=/home/joshua/.local/lib/rustup

Generally, showing all the output can help. Even better is to create a tarball of the target directory immediately after it happens. If you can reproduce it at all, also adding CARGO_LOG=cargo::core::compiler::fingerprint=trace cargo build can help.

I'll do that next time, sorry. Unfortunately I'm not able to reproduce this anymore.

Also, /home/joshua/.local/lib/cargo/target is not a standard layout. It can be helpful if you have any non-default settings to mention them as well.

The only non-default settings I have are
> set | grep _HOME
CARGO_HOME=/home/joshua/.local/lib/cargo
RUSTUP_HOME=/home/joshua/.local/lib/rustup

Generally, showing all the output can help. Even better is to create a tarball of the target directory immediately after it happens. If you can reproduce it at all, also adding CARGO_LOG=cargo::core::compiler::fingerprint=trace cargo build can help.

I'll do that next time, sorry. Unfortunately I'm not able to reproduce this anymore.

When you are able to reproduce please reopen or make a new issue!


High CPU Utilization

Hello,
First, thank you for this great sound visualization tool!
I have one question about high CPU utilization of the ODAS studio.
Whenever I start it, the CPU utilization jumps to 100% immediately.
I've tested on the Raspberry Pi 3, and on the Windows desktop (Windows7 Enterprise, Intel Core i7-6700, 16GB RAM, GeForce GT730, node v8.11.3, npm v5.6.0, python v2.7.15).
I didn't do anything else just starting the ODAS studio.
Could you help me resolve this issue?
Thank you!

Thanks!
Hmm... That's unusual...
Does it return to normal after say a minute? Is there any error popup or message in the terminal?


Add commonjs support to hyperdrive-wasm

Hardhat (among other packages) are still using commonjs so if we want to be able to use hyperdrive-wasm with these tool we need to add cjs support.  I've added a basic build to the hyperdrive-wasm package that gets us both a cjs build and an esm build.

add cjs compat to hyperdrive-wasm
don't modify the package.json of output dir

closing in favor of #1649


[TIR] Update primfunc host attachment to include host

This PR updates the host function attachment to include host attribute so it can be lowered through MakePackedAPI.

cc @Lunderberg this is a temp workaround after #14986 , we might want to revisit the invariance of MakePackedAPI require a host attribute (it makes sense in some way but might also get misuse)

Thank you @tqchen, and this change makes sense, and would prevent any later use of BindTarget from adding an erroneous host.  I assume that this is needed for compatibility in the unity branch?  (Trying to think of functionality tests that could be added on the main branch to validate this behavior.)
Regarding MakePackedAPI, I think the main issue is that MakePackedAPI needs to know both the host, so that the resulting device function can have the same host as is used by other functions in the module, and needs the device so that the correct device type can be checked in ArgBinder::BindDLTensor.  I've been thinking about whether tir::Buffer could have an optional parameter for the device type, which could be populated during SplitHostDevice to provide the device type for MakePackedAPI to use.


Setting custom typescript libraries breaks the standard lib

monaco-editor version: 0.10.1 (and whatever version is on the monaco playground.
Browser: Firefox | Safari
OS: OSX
Steps or JS usage snippet reproducing the issue:

Paste and run the following into the Monaco Editor Playground

monaco.editor.create(document.getElementById("container"), {
	value: "var x = [1,2,3];\n",
	language: "typescript"
});

monaco.languages.typescript.typescriptDefaults.setCompilerOptions({
    target: monaco.languages.typescript.ScriptTarget.ES5,
    lib: ["DOM", "ES5", "ScriptHost"] // these are the default libraries for the ES5 target
});

In the demo editor, type x. and notice that Array autocomplete does not show up.
Retype the first line to var x: number[] = [1,2,3].
Retype x. and notice that Array autocomplete does not show up.

It looks like the only way to get working standard library features like Array is to not use custom lib   options.

Workaround: use         monaco.languages.typescript.typescriptDefaults.addExtraLib(<>, "lib.d.ts"); with the entire source of lib.d.ts

Thanks for the workaround! I ran into the same issue back in September: #579

Are there any plans to address this issue in the near future?

@TyOverby , the workaround to use addExtraLib(<>, "lib.d.ts") doesn't seem to work for me and results in a syntax error because of "<>" (the first parameter). Is there a way to avoid this error?

@dennis-yemelyanov: you aren't supposed to literally put <>, you should put
| the entire source of lib.d.ts

Ah I see. Was trying to figure out a way do avoid downloading the source myself, but looks like that's the only option for now.

This bug cost me several hours of confusion today as I tried to understand why neither Array<T> nor T[] worked but also didn't cause any obvious errors.
I'm trying to build a Typescript editor for editing Node.js modules, so I don't want the DOM or other browser-specific stuff.

For anyone else still having this issue in 2019, here's a work around I came up with for Webpack:
// Reduce all the .d.ts files to a filename => content object
// Note this will add all of those files to your build even if you don't use them
const ctx = require.context('typescript/lib', true, /\.d\.ts$/)
const allLibs = ctx.keys().reduce((acc, k) => {
  acc[k] = ctx(k).default
  return acc
}, {})

monaco.languages.typescript.typescriptDefaults.setCompilerOptions({
  target: monaco.languages.typescript.ScriptTarget.ES5,
  allowNonTsExtensions: true,
  noLib: true,
})

// Add every lib from the typescript source
Object.entries(allLibs).forEach(([filename, content]) => {
  // Potentially exclude some libs here

  monaco.languages.typescript.typescriptDefaults.addExtraLib(content, filename)
})

This bug cost me several hours of confusion today as I tried to understand why neither Array<T> nor T[] worked but also didn't cause any obvious errors.
I'm trying to build a Typescript editor for editing Node.js modules, so I don't want the DOM or other browser-specific stuff.

I'm currently doing the same kind of project. Be aware that using noLib option will kill the typescript inference capabilities.
I just opened an issue for that #1673

Choosing custom libs is not supported and will not be supported. There are workarounds described in this thread, where it is possible to add them on your side via addExtraLib.


Using stardist-conic without pip install

Hello team, I was trying to try out the conic model (https://github.com/stardist/stardist/tree/conic-2022/examples/conic-2022) on my custom dataset. I tried several times installing the conic branch using pip install. I was wondering if I can simply use the conic branch without a pip install. Like locally importing the necessary libraries after downloading the code.
Thanks!

Yes, I read the troubleshooting section as well. This is how I tried to install the conic branch:
conda create stardist-conic python=3.9 followed by brew install gcc and then CC=gcc-10 CXX=g++-10 pip install git+https://github.com/stardist/stardist.git@conic-2022.
But this gives an error and the installation stops. Am I doing anything wrong? I am using a macbook, but I get the same error on a Ubuntu machine.

conda create stardist-conic python=3.9 followed by brew install gcc and then CC=gcc-10 CXX=g++-10 pip install git+https://github.com/stardist/stardist.git@conic-2022.

On my Mac, brew install gcc tries to install gcc version 13, i.e. gcc-10 / g++-10 have to be changed to gcc-13 / g++-13. You can install a specific gcc version like this: brew install gcc@13. (The same applies to linux.)
This might work:
brew install gcc@13
conda create stardist-conic python=3.9
# ...
conda activate stardist-conic
CC=gcc-13 CXX=g++-13 pip install git+https://github.com/stardist/stardist.git@conic-2022

But this gives an error and the installation stops.

It would have been helpful to see the error message.

I am using a macbook

Despite what I wrote above, compiling on Mac might also work without installing gcc first. I.e. try this:
brew install libomp  # optional to speed up some computations
conda create stardist-conic python=3.9
# ...
conda activate stardist-conic
pip install git+https://github.com/stardist/stardist.git@conic-2022

Thanks, I will try your approach now. In the meantime, is there a way you can share the conic trained model, so it will be easier for me to test it on custom HE image?

Hello @uschmidt83, I was able to pip install the conic branch on a Ubuntu machine, but only the CPU version. The training for 1000 epochs as mentioned in the train notebook would roughly take one month to complete on my CPU workstation.
It would therefore be great if you could share/upload the trained model as well, as I can test it out on my colon HE images, instead of waiting for a month for the training to finish.
Best, Ajinkya

The training for 1000 epochs as mentioned in the train notebook would roughly take one month to complete on my CPU workstation.

There seems to be a problem with tensorflow not recognizing your GPU. You can check this with
tf.test.is_gpu_available()


Don't hardcode runsettings if built from VS

Attempt to fix https://github.com/Azure/azure-sdk-for-net/issues/20674 .
The <RunSettingsFilePath Condition="'$(RunSettingsFilePath)' == ''">$(RepoEngPath)\nunit.runsettings</RunSettingsFilePath> didn't work :-(
https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2015/msbuild/visual-studio-integration-msbuild?view=vs-2015&redirectedfrom=MSDN#building-solutions

I was hoping to teach people to switch settings by commenting/uncomenting lines in the centralized file.

I was hoping to teach people to switch settings by commenting/uncomenting lines in the centralized file.

Maybe we can also AND this with some env variable to make it opt-in.
I find editing a file far less pleasant experience than clicking a checkbox to select between few prepared files...

There seems to be another variable for runsettings location:

Can you see whether VS uses that one instead?

I tried <RunSettingsFilePath Condition="'$(VSTestSetting)' == ''">$(RepoEngPath)\nunit.runsettings</RunSettingsFilePath> without luck. However by looking at that snippet - shouldn't VSTestSetting take precedence over RunSettingsFilePath if that VS were using that one?

We'll follow up with VS team to seek better solution.


How to import in Typscript project like Angular2?

How to import in Typscript project like Angular2. I am using systemjs and we try to use this example for a POC. Would you be able to guide me on correct way to import in Angular2

What have you tried?


Vue config async support

What problem does this feature solve?
Allow for asynchronous actions within vue.config.js. The specific use-case I'm looking at right now is the need to prerender dynamic routes based on data returned by an api. I'm found a few things online but nothing that appears to work with vue cli 3.x
What does the proposed API look like?
Await the result of the configureWebpack or chainWebpack methods:
const path = require('path')
const axios = require('axios')
const PrerenderSPAPlugin = require('prerender-spa-plugin')

module.exports = {
  configureWebpack: async () => {
    const { data } = await axios.get('http://some-api.com/companies')
    const { companies } = data
    return {
      plugins: [
        new PrerenderSPAPlugin({
          // Required - The path to the webpack-outputted app to prerender.
          staticDir: path.join(__dirname, 'dist'),
          // Required - Routes to render.
          routes: [ '/' ].concat(companies.map(company => `/companies/${company}`))
        })
      ]
    }
  }
}

If need both build:async and serve:async, currently, I have to... (in vue.async.config.js)
function configureWebpack(webpackConfig) {
  ...
}

function defineWebpack(webpackConfig, def) {
  webpackConfig.plugin("define").tap((args) => {
    args[0] = {
      ...args[0],
      ...def
    }
    return args;
  });
}

async function generateDefinitions() {
  await ...
}

module.exports = (api, options) => {
  api.registerCommand('build:async', async (args) => {
    const def = await generateDefinitions();

    api.configureWebpack(configureWebpack);
    api.chainWebpack((webpackConfig) => {
      defineWebpack(webpackConfig, def);
    });

    await api.service.run('build', args)
  }),
  api.registerCommand('serve:async', async (args) => {
    const def = await generateDefinitions();

    api.configureWebpack(configureWebpack);
    api.chainWebpack((webpackConfig) => {
      defineWebpack(webpackConfig, def);
    });

    await api.service.run('serve', args)
  })
}

module.exports.defaultModes = {
  'build:async': 'production',
  'serve:async': 'development'
}

There should be a single Vue Config object, therefore, a more elegant way to do this...

I'm write a excel web-addin and it's dev-mode need to load https Cert like below
// vue.config.js
const devCerts = require('office-addin-dev-certs')

module.exports = {
  devServer: {
    port: 3000,
    https:  await devCerts.getHttpsServerOptions()
    headers: {
      'Access-Control-Allow-Origin': '*'
    }
  }
}

I had to split the async code into a new js file and run by node xxx.js to get it work
maybe vue.config.js support exports an async function is a good solution here

That could make sense, but would also be a lot of work and possibly a breaking change. We will have to have a thorough look at this.
Meanwhile, you can use a local plugin file to write your own wrapper around build and do the async fetching before actually running build:
package.json:
"vuePlugins": {
  "service": ["build.prerender.js"]
  }

build.prerender.js
module.exports = (api, options) => {
  api.registerCommand('build:prerender', async (args) => {
    const PrerenderSPAPlugin = require('prerender-spa-plugin')
    const { data } = await axios.get('http://some-api.com/companies')
    const { companies } = data
    api.chainWebpack(config => {
      config.plugin('prerender').use(PrerenderSPAPlugin, [{
          // Required - The path to the webpack-outputted app to prerender.
          staticDir: path.join(__dirname, 'dist'),
          // Required - Routes to render.
          routes: [ '/' ].concat(companies.map(company => `/companies/${company}`))
        }])
    })

    await api.service.run('build', args)
  })
}

module.exports.defaultModes = {
  'build:prerender': 'production'
}

Usage in package.json:
"scripts": {
  "build": "vue-cli-service build:prerender"
}

How to change the devServer option? I want to do something like this:
let devcert = require('devcert')
let ssl = await devcert.certificateFor("localhost", { getCaPath: true });
module.exports = {
  "transpileDependencies": [
    "vuetify"
  ],
  productionSourceMap: false,
  // crossorigin: 'anonymous',
  // publicPath: process.env.VUE_APP_ENV === 'production' ? 'https://w.rummycard.in/' : '/',
  devServer: {
    https: ssl,
    proxy: {
    }
  }
}

That could make sense, but would also be a lot of work and possibly a breaking change. We will have to have a thorough look at this.
Meanwhile, you can use a local plugin file to write your own wrapper around build and do the async fetching before actually running build:
package.json:
"vuePlugins": {
  "service": ["build.prerender.js"]
  }

build.prerender.js
module.exports = (api, options) => {
  api.registerCommand('build:prerender', async (args) => {
    const PrerenderSPAPlugin = require('prerender-spa-plugin')
    const { data } = await axios.get('http://some-api.com/companies')
    const { companies } = data
    api.chainWebpack(config => {
      config.plugin('prerender').use(PrerenderSPAPlugin, [{
          // Required - The path to the webpack-outputted app to prerender.
          staticDir: path.join(__dirname, 'dist'),
          // Required - Routes to render.
          routes: [ '/' ].concat(companies.map(company => `/companies/${company}`))
        }])
    })

    await api.service.run('build', args)
  })
}

module.exports.defaultModes = {
  'build:prerender': 'production'
}

Usage in package.json:
"scripts": {
  "build": "vue-cli-service build:prerender"
}

@LinusBorg
What about if I can' use Service Plugin, and I also can't use any webpack compiler hook?
Does Vue Cli provide any way to run once-time async code when I...

Start dev (i.e. npm run serve)
before compiling

FYI, I knew that can be achieved by using Vite's configResolved.
But does that mean Vue Cli can't do that?


NA returned by get_DeepCC_label

Hello,
I get about 12 out of 300 samples with NA prediction after running get_DeepCC_label with default parameters. Could you please explain why this happens and if there is a workaround?
Thanks,
Ahwan

Hi Ahwan,
Prediction with get_DeepCC_label will return the probability of each type. If the probabilities of all types are all lower than 0.5, then the final prediction will be NA.
Best wish,
Chenghang


Busyloop while calculating cache keys in bst build --track

See original issue on GitLab
In GitLab by [Gitlab user @samthursfield] on Nov 8, 2017, 16:36
With BuildStream commit 34ba445fd1963acada0733c196483c98a57fd753 and gnome-modulesets.git commit d9eb944fce94d31f5320cbf6e41e5f29159f3e7b I can cause a busyloop.
First run: bst build --track apps.bst
Then hit CTRL+C at some point.
Eventually all status output will stop, and the main bst progress will peg a CPU at around 100% forever. CTRL+C is ignored in this state, kill -9 seems the only way to stop the process.
Attaching a debugger shows that we are stuck in Element._get_cache_key() for one of the elements that had a track job recently succeed.
Here's a partial, rough Python traceback that I came up with while investigating the issue:
# this is element causing the hang; this method never completes.
Element._cached ()
PullQueue.skip()
list comprehension in queue.py:152
# the elts argument will contain the element causing the hang
Queue.enqueue(self=PullQueue(), elts=[CMakeElement(name='apps/evolution.bst')])
Scheduler.sched()
buildstream._scheduler.Queue.job_done()
# the element argument here will be the element causing the hang
buildstream._scheduler.job.Job.child_complete()
# the 'pid' argument here will correspond to the track process for the element causing the hang
asyncio.unix_events.SafeChildWatcher._do_waitpid()
asyncio.unix_events.SafeChildWatcher._do_waitpid_all()
asyncio.unix_events.BaseChildWatcher._sig_chld()
scheduler.loop.run_forever()
Scheduler.run()
_pipeline.Pipeline.build()

It seems that the issue is: an element tracks successfully, so we try to add it to the pull queue. We check if it's cached in order to find out whether we should pull it, which requires calculating its cache key, which gets stuck in an infinite loop presumably because some of its dependencies are inconsistent.

In GitLab by [Gitlab user @samthursfield] on Nov 8, 2017, 16:55
A possibly related discussion of lazy calculation of cache keys in the context of incremental workspace builds: https://gitlab.com/BuildStream/buildstream/merge_requests/126#note_46286435

In GitLab by [Gitlab user @juergbi] on Jan 11, 2018, 09:40
mentioned in commit c05e85bfb86634361d9c606f731ac0e977651229

In GitLab by [Gitlab user @juergbi] on Jan 11, 2018, 09:41
mentioned in commit 93099418ebec58ddeeacb5bc3bc40a584831d9c4

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 05:07
mentioned in commit 64c9803e4364d9b5be341e5e70868d5ee525c22f

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 10:24
mentioned in commit bc492fa8f3973367c3817c84064629f3975b22bd

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 11:51
closed via commit bc492fa8f3973367c3817c84064629f3975b22bd

In GitLab by [Gitlab user @juergbi] on Jan 12, 2018, 11:51
closed via merge request !215

In GitLab by [Gitlab user @juergbi] on Jan 25, 2018, 14:11
mentioned in commit 6446a5912336c2bfa5dc254cbb24666d0b5af543


Minor updates for all labs

Module: 0 to 5
Lab/Demo: 0 to 7
Fixes # .
Changes proposed in this pull request:

Updated instructions for Minor updates for all labs
Updated instructions for UI changes in co-pilot
Updated screenshots with UI updates

#sign-off

@a-ainamdar - apparently, I can only approve. Can you merge?


build issue related to mongodb

still hit the following issue even i install mongodb

Make Warning at plugins/db_plugin/CMakeLists.txt:6 (find_package):
By not providing "Findlibmongoc-1.0.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"libmongoc-1.0", but CMake did not find one.
Could not find a package configuration file provided by "libmongoc-1.0"
(requested version 1.8) with any of the following names:
libmongoc-1.0Config.cmake
libmongoc-1.0-config.cmake

Add the installation prefix of "libmongoc-1.0" to CMAKE_PREFIX_PATH or set
"libmongoc-1.0_DIR" to a directory containing one of the above files.  If
"libmongoc-1.0" provides a separate development package or SDK, be sure it
has been installed.
Could NOT find MongoDB. db_plugin with MongoDB support will not be included.
-- Doxygen found.  Contract documentation will be generated.
-- Configuring incomplete, errors occurred!
See also "/Users/crazybit/eosio/eos/build/CMakeFiles/CMakeOutput.log".
make: *** [cmake_check_build_system] Error 1

Please use Telegram EOS Developers for support.
This is only a warning and you can build without mongodb.
If you want to build db_plugin with mongo then you need to install the required libraries, not just install mongodb. I recommend you take a look at the .travis.yml file.


Don't ask repository owners to sign a CLA ?

should we differentiate between repository owners and "external" committers?
pro:

there is actually no need to sign a CLA from side of the repository owner(s)
teams, which work with pull requests, are not "bothered" about signing CLA

contra:

it is hard to test/validate for newcomers, whether CLA assistant work properly
each person have to sign a CLA only once (until it changes) - shouldn't be a big deal for repository owners

@thojansen , @mierschp , @yaseminc any thoughts on this?

No, would not change this behaviour. I think any pull request should be checked and even project members can very easily sign the CLA via one click. We cannot assume that every contributor or owner is legally allowed to contribute. Maintaining another list is not easier that just clicking two buttons, so I would opt for sticking with the current flow.


How to speed up lark for a simple grammar?

I have a very simple grammar:
predicate: CNAME
           | CNAME "(" arg_list ")"

arg_list: predicate ("," predicate)*

I am parsing mostly short strings, on the order of 100 characters.
I used to use my hand-written ONP parser to parse it, which worked fine, but I didn't want to support it.
I gave lark a go, but I observed a huge (around 30x, from ~0.5ms to 14ms) increase in parsing time.
Is there any way I may be able to make lark faster under the assumption that my grammar is very simple and my texts are short? Any idea why it may be so slow (I don't count transforming nor building the parser in the timing above, although my parser also does a transformation after parsing).

Hand written parsers will always be faster than any library. You could try parser combinatorics as an alternative to lark ( I am assuming you are already using lalr instead of early). But this discussion is better had on gitter.

Are you using parser="lalr"?

@MegaIng

Hand written parsers will always be faster than any library

That may be true for expertly written grammars. But I don't think it would be very easy to beat Lark on a non-trivial grammar.

@erezsh
Yes, but this specific grammar is really simple.

Thank you for such a quick response! Indeed, adding parser="lalr" improves speed 10x for me, making lark ~3x slower than my hand-written parser, which I'd find acceptable.

It can be made even faster. Read the JSON tutorial for tips.


Executing twice the same instance results in a panic

Hello,
I am playing a bit with your implementation. I have a use case for which I would like to be able to instantiate once a wasm file and then call as much as I want the entry point of this wasm file. I did some modification to compile and instantiate without running the main function at instantiation time (in my use case, I would like to pre-load the wasm binary). I got the following backtrace when executing twice the main function of the same instance:

frochet@Attila:~/Documents/WebAssembly$ ./wasmtime/target/debug/wasmtime  --debug  --env=RUST_BACKTRACE=1 --dir=. --dir=/tmp demo/target/wasm32-wasi/debug/demo.wasm
Run the wasm file once
Run the wasm file a second time
thread 'main' panicked at 'assertion failed: c.borrow().is_none()', src/libstd/sys_common/thread_info.rs:37:26
thread 'main' panicked at 'Invoke error: StartTrap("wasm trap at 0x7f4ca98e0e37")', src/libcore/result.rs:999:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at src/libstd/sys_common/backtrace.rs:59
             at src/libstd/panicking.rs:197
   3: std::panicking::default_hook
             at src/libstd/panicking.rs:211
   4: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:474
   5: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:381
   6: rust_begin_unwind
             at src/libstd/panicking.rs:308
   7: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
   8: core::result::unwrap_failed
             at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libcore/macros.rs:18
   9: core::result::Result<T,E>::expect
             at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libcore/result.rs:827
  10: wasmtime::main
             at src/wasmtime.rs:300
  11: std::rt::lang_start::{{closure}}
             at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/rt.rs:64
  12: std::panicking::try::do_call
             at src/libstd/rt.rs:49
             at src/libstd/panicking.rs:293
  13: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:85
  14: std::rt::lang_start_internal
             at src/libstd/panicking.rs:272
             at src/libstd/panic.rs:394
             at src/libstd/rt.rs:48
  15: std::rt::lang_start
             at /rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libstd/rt.rs:64
  16: main
  17: __libc_start_main
  18: _start

I am new to Rust, and my current understanding is too limited to narrow down the problem here. Do you have any idea on this?

(in my use case, I would like to pre-load the wasm binary)

When you are running a function from the same instance twice, they will share the same global memory. For example changing a static from one invocation will affect the other. This may not be what you want.

Do you have any idea on this?

I don't. I never contributed to wasmtime, only used it.

Hello! Thanks for your answer =)

(in my use case, I would like to pre-load the wasm binary)

When you are running a function from the same instance twice, they will share the same global memory. For example changing a static from one invocation will affect the other. This may not be what you want.

What I want is extending C host programs with small WebAssembly code that can be called as much as needed and store a state on its heap. So, I need this share global memory between calls, in the WebAssembly side.
Also, running the same instance several times for small programs (even without a heap) would also save me from the overhead of the compilation at each instantiation.
It seemed like this was easy to do with a light modification of Wasmtime. But I got this weird backtrace :/

Do you have any idea on this?

I don't. I never contributed to wasmtime, only used it.

Hello! The wasm trap message means it's probably trapping in wasm code. Are you producing your wasm via either the Rust wasm32-wasi target or the was-sdk / clang wasm32-wasi targets? If so, calling the wasm start function means rerunning the libc startup code, which isn't really meant to be called multiple times. I don't know if that's what's causing the crash, but it could be, and in any case, it could be inefficient if you're calling it a lot. I'd suggest instead of calling the wasm start function multiple times, give the wasm module an export, and call the export multiple times.
Also, yes, better backtraces, error messages, and debugging are things we're aware of and are working on.

Hey!

Hello! The wasm trap message means it's probably trapping in wasm code. Are you producing your wasm via either the Rust wasm32-wasi target or the was-sdk / clang wasm32-wasi targets?

Indeed via Rust wasm32-wasi target

If so, calling the wasm start function means rerunning the libc startup code, which isn't really meant to be called multiple times.

That's a valuable piece of information :) Ok then I am not suppose to do that

I don't know if that's what's causing the crash, but it could be, and in any case, it could be inefficient if you're calling it a lot. I'd suggest instead of calling the wasm start function multiple times, give the wasm module an export, and call the export multiple times.

So, I need to call the start function of the module once, but I don't want the module to run at instantiation time. One way to avoid that would be not to have a main function into the wasm file and give an export to the module for the other functions to call?

Also, yes, better backtraces, error messages, and debugging are things we're aware of and are working on.

Great! This work is really game changing, thanks!

I believe that the wasmtime API crate has the necessary protections against this and the debugging experience has gotten better with better error messages and stack traces in the meantime, so closing.


Replace default lambda expression with explicitly lambda

Try to fix this issue: https://github.com/NVIDIA/stdexec/issues/1389
But I'm not sure if using lambda as a template parameter has any other purpose.

But I'm not sure if using lambda as a template parameter has any other purpose.

It does have another purpose. When defined as a template parameter, the mangled name is much shorter. See the following:

https://godbolt.org/z/nnxoW9cbP
I haven't measured, but I would be very surprised if your proposed change didn't regress compile time performance.

closing for now since #1389 no longer seems to repro.


Jpeg image size

Trying to use the ruby-vips .jpeg saved image in Onyx RIP software, the image sizes are different.
Ruby-vips saved “.tif” and any Photoshop image (.jpg, .tif) size is right: 10 x 10, the ruby-vips saved .jpg size is showing: 20.83 x 20.83 and is ripping that size.
Attached are the ruby-vips generated "10x10_Vips.jpg" and the "10x10_from_Photoshop.jpg" images:
10x10_Vips_and_Photoshop.zip
When running the vipsheader -a I am getting:

Tried to remove all the “data”, tried to make a copy including the x/y-res – same size issue.
#!/usr/bin/ruby
ENV["VIPS_WARNING"] = '1' # For ignoring VIPS-WARNING: Incompatible type for "RichTIFFIPTC" - for tif images
require 'vips'

im = Vips::Image.new_from_file "./10x10.tif"  # "./10x10.jpg"

#im.remove "xmp-data"
#im.remove "photoshop-data"
#im.remove 'jpeg-thumbnail-data'
#im.remove "exif-data"

#final_dpi = 150
#new_image = im.copy xres: final_dpi / 25.4, yres: final_dpi / 25.4 # 150 = 5.9055118560791, 300 = 11.811023622047
#new_image.jpegsave "./10x10_Vips.jpg", profile: './AdobeRGB1998.icc', Q: 95

im.jpegsave "./10x10_Vips.jpg", profile: './AdobeRGB1998.icc', Q: 95

#im.tiffsave "./10x10_Vips.tif", profile: './AdobeRGB1998.icc', xres: final_dpi / 25.4, yres: final_dpi / 25.4, resunit: 'inch'

Tried to "set" some of the missing tag (exif-ifd1-XResolution, exif-ifd0-ImageWidth), but I am getting the "unimplemented gtype for set" error. Is there any way to write a new tag in the exif data?
new_image = im.copy()
tag = 'exif-ifd1-XResolution'
new_image.set(tag, ' 72/1')

Tried
C:\vips-dev-8.10\bin\vips.exe magicksave "D:/Images/10x10.tif" "D:/Images/10x10_vips_1.jpg"
same size issue...
Any help or guide to the right direction is appreciated. Thank you.

I think I've found it. JPG files have two different ways of attaching resolution information: as a JFIF tag, and as part of EXIF. libvips was setting both, but leaving the JFIF tags at their default values of 72 DPI. Most loaders will prefer the EXIF resolution, but your RIP seems to pick JFIF first.
I've changed libvips to not output the JFIF tags if it sets EXIF resolution. This change should be in 8.10.2.
Thanks for the report!

Thank you @jcupitt. Looking forward to download the 8.10.2


Add logging of DB connection contention back in

I was too hasty when I said we don't need to log about excessive waits when getting a connection from the database pool. Turns out when a node is going sideways it's useful to see when contention starts.
This PR adds logging about that back in, but done as a r2d2 event handler, and with a threshold of 100ms instead of 10ms. It also adds a Prometheus gauge that reports the number of currently checked-out connections.

Fixed formatting and rebased to latest master


Added support for Python HelloWorld for Python version detection

:warning: This is a Pull Request Template :warning:

Checkout all the things you've done by placing an x within the square braces below.

Proposed Changes

[X] I've read the CODE OF CONDUCT and abide to it.
[X] I've read the CONTRIBUTING.md
[X] I've forked the repository.
[X] I've created a branch and made my changes in it.
[X] I understand opening a PULL REQUEST doesn't mean it will be merged for sure.

Please re-submit when you're ready 👍


showing shadow in android 9

dots showing shadow in android 9

yeah just ran into that as well, any solution?

HI, sorry for the late response, maybe I should add this in the readme, I have not updated this library in a while, especially have not tested with android 9 and above, if you have the time please make a PR for the fix, ill work on this issue as soon as possible (which should be next weekend at the earliest, since I am doing a full time job at the moment).

hmm, I am pretty sure we don't need shadow for the dots, probably would a be good idea to remove that line permanently

can you plz accept fork request


Handler shouldn't have to be 'static

Having a 'static lifetime requirement on Handlers seriously cripples handlers. This means you cannot have any &Ts in Handlers that aren't static also. I encountered this problem today while trying to integrate ivanceras/rustorm today with rustful with this code snippet. This doesn't work because ApiHandler stores a &Database, which isn't 'static. I work around this issue by diving a bit lower and passing around the r2d2 connection pool instead, but that heavily bloats my code.
tl;dr: please make Handler not require 'static, it would make it a lot more flexible

I would love to do this, but it's unfortunately a restriction from the  Hyper backend (see hyperium/hyper#504). You could try to use the global field if you don't want to bloat the ApiHandler.

I wrote this snippet on purpose to avoid using global, in order to employ the guarantees of the type-system to ensure I have a correct and usable database context in my handlers. But thanks for the reply, I will be patiently waiting for the upstream fix then.

Oh, ok. You could look into Arc instead.

The upcoming

The previous implementation has been scrapped in favor of the upcoming 0.11.0.


ToText(...)

Hi @erdomke -
Could you add a few overloads to RtfPipe?
Rtf.ToHtml(string RtfContent);
Rtf.ToText(string RtfContent);

I'm particularly interested in the ToText method that will convert RTF to plain text instead.  If we need to contribute a donation to enable this, please:

Let us know how much (just post it here)
An online link we can use to make the donation
An ETA on when a new build with the new method will exist.

Thanks!

Actually, you can already do this today if you are willing to add a dependency on one of my other libraries, BracketPipe. As described on StackOverflow, you could use either the MarkdownWriter or PlainTextWriter classes to write out either Markdown or plain text instead. If that doesn't work for you, those two classes give you a good idea of how you could create your own class inheriting from XmlWriter in order to pull out just the text content. If that still doesn't meet your need, let me know.
using BracketPipe;
using RtfPipe;

private string RtfToMarkdown(string source)
{
  using (var w = new System.IO.StringWriter())
  using (var md = new MarkdownWriter(w))
  {
    Rtf.ToHtml(source, md);
    md.Flush();
    return w.ToString();
  }
}

Actually, you can already do this today if you are willing to add a dependency on one of my other libraries, BracketPipe. As described on StackOverflow, you could use either the MarkdownWriter or PlainTextWriter classes to write out either Markdown or plain text instead. If that doesn't work for you, those two classes give you a good idea of how you could create your own class inheriting from XmlWriter in order to pull out just the text content. If that still doesn't meet your need, let me know.
using BracketPipe;
using RtfPipe;

private string RtfToMarkdown(string source)
{
  using (var w = new System.IO.StringWriter())
  using (var md = new MarkdownWriter(w))
  {
    Rtf.ToHtml(source, md);
    md.Flush();
    return w.ToString();
  }
}

Hi @erdomke , I don't know, if this repo is still supported, but I tried your sample and it is not working. Wen I try run it, it crash with "Stack empty" exception.
How could I convert rtf to plain text?


[Rust] Use folked sqlparser to unblock rust crate release

Published a forked version of sqlparser-lance, which means that we can use crate version of sqlparser instead of git version as dependency, which prevents cargo publish.

Closes #726


Add tooltips to metrics and selectors.

@pbeshai thoughts?
We can scale up or down on tooltip locations.
There is a bug with the placement of the tooltip that i could use your help on if we want to move forward with this approach...

+1


stm32f7xx-hal v0.6.0 docs build failure

Crate name
stm32f7xx-hal
Build failure link
https://docs.rs/crate/stm32f7xx-hal/0.6.0/builds/457266
Additional details
From the build logs, it appears that the build sandbox could not resolve DNS for crates.io  despite 2 retries.

Hmm, this happens because cargo tries to fetch sources for the dependencies when network access is blocked. But those sources should already have been fetched by rustwide before entering the sandbox. I guess cargo might make different decisions for fetching when we pass --target? I wonder if this is related to https://github.com/rust-lang/docs.rs/pull/1559 somehow.

The build is from 2021-11-02, so before the #1559 changes.

What's weird is that it's attempting to download stm32-fmc 0.2.4, while the Cargo.lock specifies stm32-fmc 0.2.3, so for some reason the lockfile got invalidated? (but at a point where it should be readonly?)

The uploaded Cargo.lock does show 0.2.4 (which answers a question I've long had on whether the uploaded source is actually the crate contents, or docs.rs modifies it during the build).
The build was from before the currently retained logs, so no extra clues there. I have requeued the build to see if it works correctly now or if we can get some more info.

Ah, the initial build fails
 error[E0432]: unresolved import `embedded_hal::digital::v2::PinState`
   --> src/gpio.rs:50:9
    |
 50 | pub use embedded_hal::digital::v2::PinState;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `PinState` in `digital::v2`

then it regenerates the Cargo.lock and tries again (https://github.com/rust-lang/docs.rs/pull/1490), but it doesn't refetch the newly locked dependencies; and then only uploads the second build log.

Has been rebuilt and docs are available.


hello world post

This @contrafactum is not meant for the Barry Clark origin branch , close this and fork it to your own repo

My mistake. Noobie.


Cannot build with XCode

I followed this tutorial here to setup xcode project. Also added Library Search Paths $SRCROOT/.build/debug, for both Kitura and Kitura Net targets, But I am still receiving ld: library not found for -lCHttpParser for architecture x86_64 error. Using Swift development snapshot 2016-06-06 (a). .Package(url: "https://github.com/IBM-Swift/Kitura.git", majorVersion: 0, minor: 20)

It is currently a bit wonky, but the xcode generated project contains only frameworks, and in the case of CHttpParser, the output should be a modulemap and a dylib (as seen if you build from the commandline).
The workaround is to add a new target to the project that will build the dylib file:

new target, type library, dynamic
in the build settings of that target, change the name (you won't be allowed to use CHttpParser, as it's used by the framework build, and you probably shouldn't remove that one, so let's assume you named it something like "CHttpParserLib") to CHttpParser
you should see under "products" in your navigator something called libCHttpParser.dylib
in the build phases of that target, add the 2 CHttpParser files (http_parser.c and utils.c)
add that target as a dependency of the framework CHttpParser
build & profit

It looks convoluted, but it's really hyper detailed to make sure there is no ambiguity, and is done in a handful of seconds. Hope that helps

@tomasgibas, did @krugazor's comment help? If you are still having trouble, you can post your project.

@krugazor, @dfirsht
I did all step by step and now I has error "library not found for -lCHttpParser" inside CHttpParserFramework itself. Looks a bit recursive (.
Any ideas what could be wrong?

@krugazor, @dfirsht Yes it helped me. Thanks a lot.

@yocaminobien you need to add the new target (the dylib) to the link phases of the framework, and that should be enough.
I have forgotten to specify that step here:

add that target as a dependency of the framework CHttpParser

it's both a dependency in the sense of build and in the sense of link.

@krugazor Thanks a lot. Yes, it is working now

Possible somebody could update wiki to mention this step

It is a bug in the new swift release that didn't happen before, as far as I can tell, it will hopefully be fixed before the final version

Thanks. Is everyone OK with this issue being closed now?

@ianpartridge is there a way to "close" it but still keep it visible, until the swift package manager is updated? I'm assuming it surprises a lot more people than the ones participating in this thread...

Hi, I think our wiki explains things. Plus people can always include closed issues in their searches.


Make sure Sticker methods works fine 🧩

Bot API 6.6 | March 9, 2023, came with many changes in Sticker methods and classes.
Make sure it all works fine.

The createNewStickerSet method seems to be failing.

The addStickerToSet had some issues too!
Fixed along with #58


Dropdown open again and again when click for closing while open.

I am using Semantic-UI Multiple select dropdown, on web PC/Laptop its working like charm but on mobile its behaving strange, when i click for open it opens fine but when i click again for close, it open again and never close.
Any one have idea how to fix it? you can view this over here when you open side menu on mobile device.

Hi @awaistechverx, this is a known issue: #3304. We might also be tracking it in another thread that I can’t find right now, as it behaves similarly on Chrome for Android.


Implement public API collecting ContextData from publisher

JIRA: EE-1323

Nicely done! Not much to say, just the naming that is a bit inconsistent I think, context:, contextData: and loadAdWithContext:. I think it would be preferable to use withContext: everywhere.
That leads me to think that the context class could have been simply named CRContext, Data not bringing much value, but that is clearly NIT / not a requested change.

Agreed to use withContext everywhere it is simpler. For CRContext, this would force us to have CRUser instead of CRUserData. Don't you this that CRUser is kind of too general ?

Oh also, I have seen some (temporary) lines of Swift code with nil arguments, I would suggest to verify that this is properly checked at compile time. (Can do this if you want)

?? Are you talking about the context: nil /* TODO */ I've put in intermediate commits ? Yes it makes the compilation fail. So intermediate commits are not passing the CI. I've done this way to ease the dev and review process. If it is an issue, I can squash the commits.

Agreed to use withContext everywhere it is simpler. For CRContext, this would force us to have CRUser instead of CRUserData. Don't you this that CRUser is kind of too general ?

CRUserContext could be more adapted, as the context is the Data. But that is really NIT, I'm fine with ContextData, especially if you have the same on Android side.

?? Are you talking about the context: nil /* TODO */ I've put in intermediate commits ? Yes it makes the compilation fail. So intermediate commits are not passing the CI. I've done this way to ease the dev and review process. If it is an issue, I can squash the commits.
Yup I was talking about this, looking at commits I thought it was building, It is ok if it does not. No need to squash.

Agreed to use withContext everywhere it is simpler. For CRContext, this would force us to have CRUser instead of CRUserData. Don't you this that CRUser is kind of too general ?

CRUserContext could be more adapted, as the context is the Data. But that is really NIT, I'm fine with ContextData, especially if you have the same on Android side.

Ok, I keep them to be like on Android.
I also added the initWithDico and migrate HTML -> obj-c doc.


build: examples not working in dev app

Fixes a couple of issues related to examples in the dev app:

The path mappings for all the new example entry points (e.g. @angular/material-examples/material/button) weren't being configured in the System config which meant that any page that consumes any of the examples would break. These changes make it so that whenever we configure a new entry point we automatically configure its examples.
The popover-edit examples were placed under the stable cdk and material example packages which is incorrect, because popover-edit itself is still experimental. These changes add new cdk-experimental and material-experimental packages under material-examples for consistency with the rest of the repo and so that we don't end up accidentally publishing these examples.

Updated the Rollup globals to include the experimental packages. Also FWIW, what I meant with exposing something by accident is that if we decided in the future to just render out all available examples rather than maintaining the list manually.


#[instruction(token_bump: u8, mint_bump: u8)] attribute on Context is undocumented

https://docs.rs/anchor-lang/latest/anchor_lang/derive.Accounts.html#instruction-attribute


Make progress and errors translatable when exporting to Android

master version of #51131.

Needs rebase for CI.

Thanks!


Add gitlab tests and documentation

Ventures at work have exposed me to the seriously cool gitlab ci system which runs strictly in images.
So, Docker in Docker in Docker - poses problems in tests.
In getting it mostly working, I can actually get this working with the use of remote testing (#24 and #23). I really want to include a way of easily running those tests from anywhere as there's tremendous value in the simple and concise tests we can run on base images #22.
The documentation and example here will be a testament to this tool.

Check out https://github.com/meAmidos/dcind
Using the DCIND I'm able to run ansible-tole-tester in concourse (which is running on docker)


Fixed build issues on MinGW-w64. Applied/adapted patches kindly provided by Alexey Pavlov with pull request #26

Original pull request by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

This pull request applies the long pending (pull request #209) and meanwhile deleted patches for building Coin with MSYS2/MinGW.

Output names corrected for MinGW in CMake build scripts.

Comments on the PR very welcome.

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

Thanks a lot, you’re both doing a great job clearing up long standing issues. You’re bringing a lot of strength to the team!

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).


Wkbrd security patch

This branch adds additional securityContext controls to align with those available from the Bitnami Helm charts.
This also renames the securityContext value to podSecurityContext in alignment with the Bitnami values.
Added Apache license details from Bitnami due to the README.md borrowing text from the Bitnami README.md file

Thanks @wkbrd! Always good to see some security-minded folks having a look and seeking to improve things.
I just took a review pass and left some feedback above. The gist: the new default values look good to me, but I'd like to see some diligence on compatibility so we don't inadvertently break things for folks when they upgrade this chart.

Hi @canterberry , I think this addresses the changes you requested.  The only changed file is now values.yaml.


[feature] Added support for LIKE Wildcards #323

I really needed this, so I went ahead and fixed it.

That's good, thank you for your request.

I want to discuss more about this patch. In SQL LIKE, there are two wildcard characters % for many chars and _ for single char.
In the medoo's documentation Londo_ matches London, Londox, Londos doesn't clearly define the _ in medoo meaning many characters after the word or just single char after the word.
@catfan can you explain this?

@SyuTingSong this was clear to me as meaning "wildcard" just like the name implies: "anything after this", just like the % means in SQL. I'm not 100% sold on the % and _ suffixes/switches but it's @catfan's framework, so it's his call.
(I just made sure they work as the Documentation stated, because I had committed to Medoo for a project and I discovered too late that not all the features were implemented. It was quicker for me to fork and fix Medoo than to find and implement a new framework! Obviously my impression of the feature was correct as @catfan has merged my commit).


Celery(Redis) issue - AttributeError: 'float' object has no attribute 'items'

I have just pulled the source from this repo and build airflow in my local machine.  When I execute airflow in with Celery Executor, I can see docker logs at the worker with error "AttributeError: 'float' object has no attribute 'items'".   The tutorial DAG I have triggered is in the running state without end and no task has been completed.
Does anyone know how to fix this issue?

Found the fix from https://github.com/celery/celery/issues/5175 by installing redis 2.10.6.


Do not set accepted_at to nil when reverting from recruited to pending

Context
We introduced some services last cycle to allow Support users to revert the status of application choices.
A small mistake was made when creating the RevertRecruited to PendingConditions service.
It is not sensible to set the accepted_at date to nil because the application is still accepted by the candidate.
Guidance to review

Link to Trello card
Trello Ticket
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault

 Bug: accepted_at field reverting to nil when support reverts recruited


Electron build for Texture 2

We should prepare new bundling.

[x] Evaluate and use latest electron
[x] Update electron-builder
[x] Check the issues with file saving (see #1009)

@Integral it is important that you keep your branch rebased on the latest master. Otherwise the codecov reports are giving us false alarms.


Documentation Website not working

Hey, just checked your site and it seems that your navigation does not work correctly.
https://dockware.io/

Seems to work again. Thanks!

hi :)
server maintenance :D you had a brilliant timing haha


Exception while loading assemblies - FileNotFoundException - Could not load assembly System.Memory

Good day. I;m trying to create simple Xamarin Forms app (<IP_ADDRESS>2510) - iOS, Android + .net Standard projects. I've added Microsoft.EntityFrameworkCore.Sqlite (2.1.0-rc1-final) to all projects. there is no issues with building common project, but when I'm trying to build Android I have build error with following exception:
Error		Exception while loading assemblies: System.IO.FileNotFoundException: Could not load assembly 'System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. Perhaps it doesn't exist in the Mono for Android profile?
File name: 'System.Memory.dll'
   at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve(AssemblyNameReference reference, ReaderParameters parameters)
   at Xamarin.Android.Tasks.ResolveAssemblies.AddAssemblyReferences(DirectoryAssemblyResolver resolver, ICollection`1 assemblies, AssemblyDefinition assembly, Boolean topLevel)
   at Xamarin.Android.Tasks.ResolveAssemblies.Execute(DirectoryAssemblyResolver resolver)	XF3EFCTest.Android	C:\VisualStudio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets	1590

Visual studio - 15.7.1

@divega to follow up with Xamarin

If you want I can give you my test solution

I ran into the same problem and used the following workaround https://github.com/azabluda/InfoCarrier.Core/commit/30abe4238050b64ed37134902da01f8d58040426

@ajcvickers Good day! I've tried your workaround, but it seems doesn't work for me.

I utilize Microsoft.EntityFrameworkCore.Sqlite in a NetStandard 2 common library for data services for both Xamarin.Android and Xamarin.IOS. I just updated to EFCore.Sqlite to release 2.1. I now get the build error as above.
I have a question...
How can something like this happen? Xamarin.Android is NetStandard v2.0 compatible and EFCore.Sqlite 2.1 is NetStandard v2.0 compatible. Aren't they both guaranteed to support the same APIs? Perhaps my assumption that Xamarin.Android is NetStandard v2.0 compatible is wrong.
Is there a Xamarin.Android ( and Xamarin.IOS ) (pre)release that supports system.memory 4.0.1?

Workaround: copy System.Memory.dll from ../Xamarin.iOS/v1.0/Fascades to ../Xamarin.Android/v1.0/Fascades ( in your vs2017 Community 15.7.2 installation ).

I'm getting the same behavior.  Going to try the workaround.  Thanks @ToddThomson . Anyone else have any luck with it?

Im in the same position, it seems that the writing has been on the wall since April about this one. Pity there was not more coordination for a smooth release and upgrade.
[(https://github.com/aspnet/SignalR/issues/1886)]

@marek-safar FYI, this is one of two System.Memory-related issues reported to block EF Core 2.1 RTM from working on Xamarin. The other one is https://github.com/xamarin/xamarin-macios/issues/4168. I am assuming that they maybe separate issues because the errors are different.
Would it be better if we move this one to a Xamarin repo?
FWIW, the dependency on System.Memory comes indirectly through Microsoft.Extensions.Primitives.
Do you know if the fix for https://github.com/dotnet/corefx/issues/29847 would fix this too?

After encountering a similar issue with Xamarin.iOS, I tried my case in a Xamarin.Android project. Also fails with EF Core 2.1 due to dependency on newer System.Memory. Here's the issue I jsut filed for Xamarin.Android: Android app build fails when referencing package (e.g. Entity Framework Core 2.1) that depends on newer System.Memory.

I can confirm that VS 2017 15.7.3 fixes this issue ( at least for Xamarin.Android app builds ).
Before installing the 15.7.3 update I removed my workaround as mentioned above.

@divega I'd certainly try if that fix resolves the issue as well and it's quite possible. If you please open Xamarin issue with repro.
Thanks

If you please open Xamarin issue with repro.

@marek-safar Thanks. I think @cwrea beat me to it: https://github.com/xamarin/xamarin-android/issues/1769. And that one is already closed because it doesn't repro anymore in 15.7.3 due to changes for Android.
I will go ahead and close this issue as external since the only actionable item left on the EF Core side is the missing testing for Xamarin (https://github.com/aspnet/EntityFrameworkCore/issues/8792) which could have helped detect this sooner.

Reopening and assigning to @smitpatel who is going to do some testing for the fix.

Testing with pre-release 2.1.1 bits shows that it is not going to fixed for first patch.
VS for Mac 7.5.2 build 40

I think the meta-issue here (and here, and here) is that packages like EF Core 2.1 (and SignalR) took what have turned out to be hard dependencies (whether direct, or indirect) on new package bits from .NET Core 2.1—package bits which are neither present in .NET Standard 2.0 nor yet truly available for other Standard-conforming platforms.
By "truly available" above, I don't just mean published—because as evidenced (and perhaps in error), Microsoft.Extensions.* and System.* packages can be published on NuGet while claiming "No dependencies" on supported platforms like Xamarin.iOS and Xamarin.Android, and yet those underlying "supported" platforms could be missing the actual implementation that the package asserted¹ would be there.
And so developers of Standard-conforming platforms other than .NET Core (which got these new APIs first) now have to play catch-up just to get back to compatibility—compatibility not with the Standard itself, but with the new bits now required by new releases of these popular libraries that had cross-platform as a goal.
Perhaps it may not be reasonable to expect Xamarin.iOS and Xamarin.Android to simultaneously get new APIs as they are added to .NET Core. The Xamarin mobile platform developers are already tasked with keeping up with what Google is doing with Android, and what Apple is doing with iOS. And iOS 12, in particular, is probably top-of-mind for the next couple of Xamarin.iOS releases. There are far more Xamarin app developers who'd be upset if the latest UIKit weren't supported in the product vs. those of us eager to take advantage of the new Entity Framework Core release.
Perhaps it may also not be reasonable to expect the .NET Standard itself to get revved as every useful new API is added to .NET Core. There's a discussion about this here.
So maybe developers of packages who desire to maintain cross-platform² compatibility could be more conservative in adopting features from .NET Core that aren't yet truly available on other platforms that the package would like to maintain compatibility with? Or adopt a strategy whereby new bits can be taken advantage of when present, but not break compatibility when not present?
TL;DR: As the complexity of a package increases, the likelihood that cross-platform capability comes as free side-effect quickly approaches zero.  :/

¹ "asserted" by use of a _._ placeholder file within the package's lib subfolder for the supported platform.
² "cross-platform" is meant as in across multiple target frameworks that conform to a specific .NET Standard version, and not just across the handful of desktop and server OSs you get by targeting only .NET Core.

@cwrea As pointed out in issue 682 in dotnet/standard, New ,NET Core releases will always have an increasing/changing API surface that is a superset of .NET Standard. This is excellent - use newer bits and get any and all benefits. For developers, we choose a target framework(s) for the API surface we need for the platforms our software will run on.
Release 2.1 of EFCore took a dependency on Microsoft.Extensions.Logging 2.1 which in its dependency chain uses System.Memory 4.5 ( Options->Primitives ). Now, I have no idea whether the System.Memory API is part of .NET Standard v2. It might be (.NET Standard 1.1); it might be part of the latest bits from .NET Core. I shouldn't have to know! When I take a dependency in my code I only look at the nuget dependencies ( or rather, I'm hoping that my dev tools do the job ). If I am targeting .NET Standard 2 then I should expect that ALL my dependencies ( and their dependency chain) target .NET Standard 2. That is the beauty of .NET Standard!
At least with Xamarin.Android ( before its release update in VS 2017 v15.7.3 ) System.Memory was not included. This was just a bug. It was reported and fixed. With the current release cadence of VS 2017 I can live with that.
EF Core 2.1 targets .NET Standard 2. It should be compatible with any platform that supports .NET Standard 2. If .NET Standard platforms are missing required implementation packages then that is a bug. If a published package doesn't properly identify its target framework then that is a bug.
Before a nuget package is released it should be tested on all .NET platforms that support the package's target framework. With EF Core 2.1, it appears that this is not yet the case. This is a bit troubling as the great .NET Standard 2 changes have been in place for a while now.

@ToddThomson Re:

If I am targeting .NET Standard 2 then I should expect that ALL my dependencies ( and their dependency chain) target .NET Standard 2. That is the beauty of .NET Standard!

I agree completely. As an app developer, this is the ideal. Platform developers and library developers have to be more concerned about the details, but what you wrote is the way I wish it to be at the app development level. I know there will be bugs and it will never be perfect, but things can get closer to that ideal than where we are today.
BTW, I elaborated on the Standard and the dependency chain issue at https://github.com/dotnet/standard/issues/682#issuecomment-395486228, just after my comment above on this issue. Looks like there's more than one path that leads to the dependency on System.Memory.
And re: "EF Core 2.1 targets .NET Standard 2." ... in theory, but there's work to do (as you know, having commented there too) before I'll feel more confident in that holding true. .NET Standard is so much more than .NET Framework and .NET Core.
Anyway, crossing my fingers! EF Core is relevant for mobile app development scenarios, esp. w.r.t. code sharing opportunities with the server side. Not all the same concerns on client vs. server, but there are certainly places where sharing can make sense.

Moving this to 2.1.3 to verify as part of that release.

While https://github.com/xamarin/xamarin-android/issues/1769 has been closed and 15.7.3 did address a build issue with Xamarin.Android and EF Core 2.1, I discovered that enabling the Xamarin.Android linker, even with the conservative "SdkOnly" setting (i.e. not user assemblies), is causing a new problem. I just opened the following issue:

xamarin/xamarin-android - Android app build fails during "SdkOnly" linking when referencing package (e.g. Entity Framework Core 2.1) that depends on newer System.Memory #1813.

This issue is fixed in upcoming release of Xamarin.


Parsing repeated sections

The code below works well, if the student section contains one student How do I handle the case where there are multiple student sections?
from lark import Lark, Transformer

studentList = '''
Student 1   (lastname=Lark, firstname=Joe)
     Maths : 100
     Physics : 50
Student 2   (lastname=Karl, firstname=Sam)
     Maths : 100
     Physics : 50
'''

grammar = '''

start : student_info

student_info : "Student" WS* STUDENT_ID "(" student_name_parts ")" WS* subject_scores
student_name_parts: "lastname" WS* "=" WS* STUDENT_LAST_NAME WS* "," WS* "firstname" WS* "=" WS* STUDENT_FIRST_NAME
subject_scores: subject_score+
subject_score: WS* SUBJECT_NAME WS* ":" WS* SUBJECT_SCORE WS*

STUDENT_ID: INT
STUDENT_LAST_NAME: (LETTER|DIGIT)+
STUDENT_FIRST_NAME: (LETTER|DIGIT)+
SUBJECT_NAME: (LETTER|DIGIT)+
SUBJECT_SCORE: (DIGIT)+

%import common.LETTER
%import common.DIGIT
%import common.INT
%import common.WS
%ignore WS
'''

class StudentInfoTransformer(Transformer):
    pass

parser = Lark(grammar, start='student_info')
tree = parser.parse(studentList)
mytransformer = StudentInfoTransformer()
print mytransformer.transform(tree)

Did you try this?
start: student_info+

Also, if you %ignore WS, you don't need to write it everywhere inside the grammar.

Thank you for the pointers!! I handled WS properly as given below, and I could have this solved.
from lark import Lark, Transformer

studentList = '''
Student 1   (lastname=Lark Stark, firstname=Joe)
     Maths : 100
     Physics : 50
Student 2   (lastname=Karl, firstname=Sam)
     Maths : 100
     Physics : 50
'''

grammar = '''

start : student_info+

student_info : WS* "Student" WS* STUDENT_ID WS* "(" WS* student_name_parts WS* ")" WS* subject_scores
student_name_parts: "lastname" WS* "=" WS* STUDENT_LAST_NAME WS* "," WS* "firstname" WS* "=" WS* STUDENT_FIRST_NAME
subject_scores: subject_score+
subject_score: WS* SUBJECT_NAME WS* ":" WS* SUBJECT_SCORE WS*

STUDENT_ID: INT
STUDENT_LAST_NAME: (LETTER|DIGIT|" ")+
STUDENT_FIRST_NAME: (LETTER|DIGIT)+
SUBJECT_NAME: (LETTER|DIGIT)+
SUBJECT_SCORE: (DIGIT)+

%import common.LETTER
%import common.DIGIT
%import common.INT
%import common.WS
'''

class StudentInfoTransformer(Transformer):
    pass

parser = Lark(grammar)
tree = parser.parse(studentList)
print tree.pretty()
mytransformer = StudentInfoTransformer()
print mytransformer.transform(tree)

This generates the following output:
start
  student_info

    1

    student_name_parts
      Lark Stark

      Joe
    subject_scores
      subject_score

        Maths

        100
      subject_score

        Physics

        50
  student_info

    2

    student_name_parts
      Karl

      Sam
    subject_scores
      subject_score

        Maths

        100
      subject_score

        Physics

        50

Tree(start, [Tree(student_info, [Token(WS, '\n'), Token(WS, ' '), Token(STUDENT_ID, '1'), Token(WS, '   '), Tree(student_name_parts, [Token(STUDENT_LAST_NAME, 'Lark Stark'), Token(WS, ' '), Token(STUDENT_FIRST_NAME, 'Joe')]), Tree(subject_scores, [Tree(subject_score, [Token(WS, '\n     '), Token(SUBJECT_NAME, 'Maths'), Token(WS, ' '), Token(WS, ' '), Token(SUBJECT_SCORE, '100')]), Tree(subject_score, [Token(WS, '\n     '), Token(SUBJECT_NAME, 'Physics'), Token(WS, ' '), Token(WS, ' '), Token(SUBJECT_SCORE, '50')])])]), Tree(student_info, [Token(WS, '\n'), Token(WS, ' '), Token(STUDENT_ID, '2'), Token(WS, '   '), Tree(student_name_parts, [Token(STUDENT_LAST_NAME, 'Karl'), Token(WS, ' '), Token(STUDENT_FIRST_NAME, 'Sam')]), Tree(subject_scores, [Tree(subject_score, [Token(WS, '\n     '), Token(SUBJECT_NAME, 'Maths'), Token(WS, ' '), Token(WS, ' '), Token(SUBJECT_SCORE, '100')]), Tree(subject_score, [Token(WS, '\n     '), Token(SUBJECT_NAME, 'Physics'), Token(WS, ' '), Token(WS, ' '), Token(SUBJECT_SCORE, '50'), Token(WS, '\n')])])])])

Closing the issue as resolved! This was more of a request for help, rather than an issue.


Timeout to response of URL

When entering a URL, there are times that stays constantly looking at that URL without continuing, it is possible to put a timeout period by URL?

there is already a connection timeout of 3 sec, and a request timeout of 5 sec.
Timeout is set on the extractor package that is used by the crawler: https://github.com/hedii/extractors/blob/master/src/Extractor.php#L105


Make the git script a git subcommand

Convert the script to a proper sub command.
https://git.github.io/htmldocs/howto/new-command.html

Closed by #d96e73b


Add resources for developers with some design docs on "Embulk v2"

@muga Adding resources for developers, with "Embulk v2" resources.

Since v2 will be a kind of big changes, and we don't have a big set of documents for the time being, I suggest to have v2 core/plugin documents under a separate top-level section. I thought it could be nice to have other (non-v2) documents separated to core and plugins, but I'm afraid we don't have so much documents to separate...
What do you think reconstructing in parallel to adding documents?

@dmikurube Sorry for the delay.

What do you think reconstructing in parallel to adding documents?

Sounds good to me. Let's merge first and then I will think about it again.

@muga Thanks! Merging this, and let's improve them later.


Natspec docs

Updated contracts to NatSpec

This PR is stale/ out of sync with repo, and for now we will keep the current documentation style. Most contracts have already been deployed. We will discuss internally whether to convert project to /// from /* */ syntax. Thanks for your contribution please see contributing.md for more information

This PR is stale/ out of sync with repo, and for now we will keep the current documentation style. Most contracts have already been deployed. We will discuss internally whether to convert project to /// from /* */ syntax. Thanks for your contribution please see contributing.md for more information


CodePeer wrongly listed as proprietary software

Hi,
As one of the developers of CodePeer at AdaCore, I'd like to point out that it is in fact distributed to our customers with GPLv3 license (AdaCore is a FLOSS tool provider), but that there is no "free" (as in free beer) version available on the Web.
It is also not the only available static anlyzer for Ada, you could list also:

PolySpace Ada (https://www.mathworks.com/products/polyspace-ada.html)
Understand for Ada (https://scitools.com/ada-programming-essential/)
Axivion Bauhaus Suite (https://www.axivion.com/en/products-services-9#products_bauhaussuite)

Good to know @yannickmoy. I've changed the license to OSS and added the tools you mentioned. Thanks! 👍


Fixes #329: Support $slice modifier for Projection

What this PR does:
Implements support for $slice projection modifier
Which issue(s) this PR fixes:
Fixes #329
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

LGTM. One potential suggestion: maybe worth testing $slice with nestedArray?

Sounds reasonable, will do. Thanks!


Update model_utils.py

I ran into an issue where save_layer in model_utils.py is giving me an error that: AttributeError: 'Dense' object has no attribute 'output_shape'
I found that layer.output.shape works, but isn't always a tuple, which runs afoul of the JSON encoder. So I added check for that too.
I modified the code and it seems to work on Macos, Linux, Windows. I've included my debugging print statements so you can see what I was looking at.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.26%. Comparing base (0b0e5d0) to head (3aff951).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   95.70%   93.26%   -2.45%
==========================================
  Files          58       23      -35
  Lines        3892     1662    -2230
==========================================
- Hits         3725     1550    -2175
+ Misses        167      112      -55

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Looks good on my end! Thanks for the contribution.


Amend small bits of doc

Documentation is provided here https://testslide.readthedocs.io/, let's not use links to GitHub sources directly.
I don't think there's an of the shelf way to get the current version so we can generate a link to https://testslide.readthedocs.io/en/2.0.1/testslide_dsl/async_support/index.html, so I added a short version of the doc in the exception message.

Meh, nevermind, thanks for the quick review!


Kubectl Explain doesn't list properties of mapping.spec

Please describe your use case / problem.
I'd like to get some useful information from Kubernetes about the CRD using kubectl explain.
at 16:30:11 ❯ k explain mapping.spec
KIND:     Mapping
VERSION:  getambassador.io/v2

DESCRIPTION:
     MappingSpec defines the desired state of Mapping

Describe the solution you'd like
This command can return useful information that I'm used to with other CRDs like ArgoRollouts.
Additionally, it would be very nice if the API spec was published similar to how K8s publishes all resources here:
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/
Describe alternatives you've considered
Trying to glean the object structure, fields, valid values, defaults, etc from this page:
https://www.getambassador.io/docs/edge-stack/latest/topics/using/mappings/
Additional context
N/A

(Closing given the workaround.)


ES modules: how to import watchUtils and Button?

Hi,
when I used esri-loader, to import watchUtils and Button I wrote:
  loadModules([
      "dijit/form/Button",
      "esri/core/watchUtils",
    ], options)
      .then(([
        Button,
        watchUtils,
      ]) => {})

How can I do with ES modules?
Writing:
import Button from '@arcgis/dijit/form/Button';
import watchUtils from "@arcgis/core/watchUtils";

I cannot do it.
Thanks for hekp.

I solved for watchUtils:
import * as watchUtils from<EMAIL_ADDRESS>Nothing for Button

Glad you got it figured out for watchUtils, there's no default export on that module.
Nope, we don't have anything equivalent for button that's part of the JS API.

Ok, I think I solved both problems.
For watchUtils:
import * as watchUtils from<EMAIL_ADDRESS>For button the best solution is (this example put as icon the esri-icon-collection):
var element = document.createElement('div');
element.className = "esri-icon-collection esri-widget--button esri-widget esri-interactive";
element.addEventListener('click', function(evt){
  console.log("clicked");
})
view.ui.add(element, "top-right");

If you are using ionic, you can put a ionic icon removing 'esri-icon-collection ' and adding a innerHTML, like;
var element = document.createElement('div');
element.className = "esri-widget--button esri-widget esri-interactive";
element.innerHTML = '<ion-icon name="expand"></ion-icon>'
element.addEventListener('click', function(evt){
  console.log("clicked");
})
view.ui.add(element, "top-right");

Followup note - for those reading this that aren't using Ionic, or Vanilla JavaScript, you just need a slight modification of the element.innerHTML to make this work:
        let element = document.createElement('div');
        element.className = "esri-widget--button esri-widget esri-interactive";
        element.innerHTML = ''
        element.addEventListener('click', (evt) => {
           console.log("clicked");
        });

        view.ui.add(element, "top-right");


Lily SEGV on unknown address with the test file binary_trees.lily.

$ ./lily  binary_trees.lily
Segmentation fault
The GDB debugging information is as follows:
(gdb) set args binary_trees.lily
(gdb) r
...
(gdb) x/10i $pc
=> 0x501d20 <lily_get_error+1520>:	mov    0x7fff8000(%rax),%al
0x501d26 <lily_get_error+1526>:	test   %al,%al
0x501d28 <lily_get_error+1528>:	jne    0x501dfe <lily_get_error+1742>
0x501d2e <lily_get_error+1534>:	movzwl (%rdi),%ecx
0x501d31 <lily_get_error+1537>:	mov    %rsi,(%rsp)
0x501d35 <lily_get_error+1541>:	xor    %eax,%eax
0x501d37 <lily_get_error+1543>:	mov    0x28(%rsp),%rdi
0x501d3c <lily_get_error+1548>:	mov    0x30(%rsp),%r8
0x501d41 <lily_get_error+1553>:	lea    0xd6578(%rip),%rsi        # 0x5d82c0 <.str.177>
0x501d48 <lily_get_error+1560>:	callq  0x5b9330 <lily_mb_add_fmt>
(gdb) i r rax
rax            0x1fffffffffffffff<PHONE_NUMBER>213693951
(gdb) si
Program received signal SIGSEGV, Segmentation fault.
0x0000000000501d20 in build_error (parser=) at /home/icy/real/lily-asan/src/lily_parser.c:4836
4836	                        func->module->path, frame->code[-1], class_name,
(gdb) bt
#0  0x0000000000501d20 in build_error (parser=) at /home/icy/real/lily-asan/src/lily_parser.c:4836
#1  lily_get_error (s=) at /home/icy/real/lily-asan/src/lily_parser.c:5016
#2  0x00000000004f1dd4 in main (argc=, argv=) at /home/icy/real/lily-asan/run/lily.c:107
(gdb) c
Continuing.
ASAN:DEADLYSIGNAL
==63877==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000000501d20 bp 0x0c0c00001670 sp 0x7fffffffe340 T0)
#0 0x501d1f  (/home/icy/real/lily-asan/build/bin/lily+0x501d1f)
#1 0x4f1dd3  (/home/icy/real/lily-asan/build/bin/lily+0x4f1dd3)
#2 0x7ffff6ee682f  (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#3 0x41fd58  (/home/icy/real/lily-asan/build/bin/lily+0x41fd58)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/home/icy/real/lily-asan/build/bin/lily+0x501d1f)
==63877==ABORTING
[Inferior 1 (process 63877) exited with code 01]
The vulnerability was triggered in function build_error() at lily_parser.c:4836
4780 static void build_error(lily_parse_state *parser)
4781 {
...
4811     else {
4812         lily_call_frame *frame = parser->vm->call_chain;
4813
4814         lily_mb_add(msgbuf, "Traceback:\n");
4815
4816         while (frame->prev) {
4817             lily_function_val *func = frame->function;
4818             const char *class_name = func->class_name;
4819             const char *func_name = func->trace_name;
4820             char *separator = ".";
4821             if (class_name == NULL) {
4822                 class_name = "";
4823                 separator = "";
4824             }
4825             else if (strcmp(func_name, "") == 0) {
4826                 func_name = "";
4827                 separator = "";
4828             }
4829
4830             if (frame->function->code == NULL)
4831                 lily_mb_add_fmt(msgbuf, "    from [C]: in %s%s%s\n",
4832                         class_name, separator, func_name);
4833             else
4834                 lily_mb_add_fmt(msgbuf,
4835                         "    from %s:%d: in %s%s%s\n",
4836                         func->module->path, frame->code[-1], class_name,
4837                         separator, func_name);
4838
4839             frame = frame->prev;
4840         }
4841     }
4842 }

Strange. I don't see any issues when running it under valgrind, either normally or with -m32 on my own system.
What platform and arch are you using? Are you also using the latest version? Are you running a 64 bit system or a 32 bit one?
I'm quite confused about this because binary trees shouldn't be raising an exception at all, so that may be why it's crashing. The code[-1] section would fail if not properly within __main__. Can you figure out what's triggering a raise at all (if it's done through the vm, it'll go through maybe_catch_exception).

Thank you for your attention, i run it under ubuntu16.04,64bit. I'll check the  phenomenon again tomorrow @FascinatedBox

I think it's a NullPointerException.Both ubuntu 16.04 and ubuntu 15.10
Breakpoint 1, build_error (parser=) at /home/icy/real/lily/src/lily_parser.c:4836
4836	                        func->module->path, frame->code[-1], class_name,
(gdb) p *frame
$7 = {start = 0x868930, top = 0x868968, register_end = 0x869290, code = 0x0, function = 0x68f700,
return_target = 0x869ce0, prev = 0x86cbb0, next = 0x0}
(gdb) p frame->code[-1]
Cannot access memory at address 0xfffffffffffffffe
$ cat /etc/issue
Ubuntu 16.04.2 LTS \n \l

My apologies, I haven't run the benchmarking on my own system in quite some time. I saw both of your issues before heading out the door and feared that they were the cause of another arch or 32 bits.
I did a little bit of investigation while I was out. The underlying bug is that the recursion limit is being hit. I increased it to 20K and it's still being hit, and it was never hit before. But on top of that, the recursion limit raise isn't doing the code pointer fix that all other raises do as a preamble. That's why the crash is happening.
I didn't poke around much with the other bug, but my guess is that it happened during some hash api change.


can we get champagne run to work without the need for init?

nextflow run nf-core/chipseq -profile test,docker --outdir output just works for nf-core pipelines, without the need to first download anything at all. In theory we should be able to get the same working for our nextflow pipelines so champagne run -profile test ... will just work without initializing anything.

init could still be helpful as an optional helper to copy an example samplesheet or params.yml file for users to customize for their needs, but this way it could be optional instead of required.

offering my thoughts on this- i think (biased- see below) init is crucial for reproducibility and tracking and while its nice to maybe avoid that in dev, i dont think for production it should be optional.
from a historical standpoint, init has evolved from what was just a copy some configs and random files to the outputdir to how it is set up on most pipelines. i've pushed for and added (hence, bias) a lot of the code in our pipelines related to init because of experiences i've had with my own work, and with assisting others running our pipelines. a few thoughts on why it should remain a requirement for production.

(for all users) it saves all configuration metrics and input params with the output directory. this ensures if we go back to the project months down the line, we don't have to dig through log files to know what params were being used (and it's easily labeled so PI's can look it up without asking us). when i go to write manuscripts i always go to the tools json/config file to easily pull all version (or containers) to pop into the methods section. no searching through logs.
(power users) related,  running more than one project on the same pipeline, at the same time, makes for dangerous outcomes if you haven't initialized a single source for configs etc.
(for all users) similarly provides defined manifests for users to update, rather than need to recreate on their own. this is the number one source of headache for new users with new pipelines - the manifest file is formatted incorrectly; even with the best documentation.
(power users) copies scripts used directly to the output directly which were run during the creation of the output material. this allows users to perform single-project needed updates to code quickly, while saving these changes directly in the output dir for reproducibility.

all that aside, for dev, this is a super helpful tool, especially if the pipeline has test profiles. in that instance you're just running on what is already set up and defined and dont really care about history. I think it's a perfect use case for that, but not as much for production.

Currently the init implemented here is substantially smaller / has fewer features than the init of the snakemake workflows. We can definitely satisfy all of the goals/pros you listed, it's just a matter of deciding how that should/could be implemented with our nextflow pipelines.
I think some of the reproducibility goals may be better handled at run time rather than during initialization. We do plan to eventually get all processes to output their software versions just like the nf-core pipelines (see #27) -- in those pipelines that's something handled at run time because the version can change depending on which container is used for a given process.
Config options set at the CLI also can change between runs/reruns in the same directory, so we'll want to make sure we're capturing those at run time also -- I think that actually may already be handled by nextflow's built-in execution report but we should double check, and if not make sure we output a time-stamped file with an exhaustive list of the params used.
I do think copying boilerplate config/params files, example sample sheets, etc are good examples of tasks best handled by init.


Not redirected to interview when log back in

Page title
Log in

Steps to reproduce
I got logged out of my account so I tried to log back in using my phone.

Expected behavior
I got sent a verification code and put it in. I expected to be logged back in.

What happened instead
I got a screen that said "File not found" and could not return to my interview.

Other information

Maturity target
Level 2 - this needs to be fixed to meet expectations of a basic intake

Tester contact info
Allie MLRI

config issue, test again, check with Jonathan if still not working

Worked when I tested it on mobile


Development

Codecov Report

Merging #19 (3e4f585) into main (11ac6c4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   60.64%   60.64%
=======================================
  Files          12       12
  Lines         155      155
  Branches       13       13
=======================================
  Hits           94       94
  Misses         58       58
  Partials        3        3

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 11ac6c4...3e4f585. Read the comment docs.


ROGER-754: Script marathon upgrades.

Remove old ansible style upgrade tasks.
Script for upgrading marathon.

LGTM. Might be good if @ankanm takes a look at it as well.

LGTM


Issue on MacOS

Whenever i run python3 RsaCtfTool.py or just ./RsaCtfTool.py, it shows
Traceback (most recent call last):   File "./RsaCtfTool.py", line 21, in <module>     from Crypto.PublicKey import RSA ModuleNotFoundError: No module named 'Crypto'
I have installed module crypto but it still wont work. It was working a few months back.

Hello,
I had the same issue as you, and I've fixed it by installing crypto via easy_install not pip.
So try to run easy_install crypto (I assume you are using pyenv).
I still haven't found the clue of this inconsistency, I'll check it later.
Also, I suggest you to switch to PyCryptoDome instead of unmaintained Crypto. It's a fork of it so it maintains the same module name, be careful to remove the old Crypto module.


DataHarmonizer Provenance in CNPHI export

CNPHI has agreed that we can output the DataHarmonizer provenance version information into a (free-text) column called additional comments.

Example DH-CNPHI Export CSV:

Example Successful CNPHI Upload:

done!


Licensing information is inconsistant

Hey,
Nifty code and very useful.  However, while you state Apache License 2.0 in your readme / license.txt file, the source code headers still include LPLG.

Thanks. Yeah, may be some legacy items in there that we need to remove. I'll take a look. Be assured, you can use it under the terms of the Apache License though. More folks wanted a more liberal license, so it was switched over some years ago.

Just in my job we check the source code first for the license, then the project.
If there is a difference, the license closest to the source code wins.  In your case it would be LPGL.
I'll certainly point out this thread (and see if I can get an override).
Thanks

I've just pushed a commit to remove the old reference: d6dd3092cc2ab4c545f54a53a14559efd546d9d8


Workflow on PRs not starting run

Current Behavior
The github action "Build and deploy to GitHub Pages" currently doesn't run on Pull Requests and remains in state "Expected - waiting for status to be reported". This blocks merging approved PRs as visible below:

Expected Behavior
Action runs. Produces success or error.
Steps To Reproduce
Open a PR or take a look at #1069, #1064, #1061 or a couple other ones that are open right now.
Important technical details:
Might have something to do with branch protection rules like here

thx @arnoweiss -> @matbmoser do you remember where we changed the protection rule?

mh i think there was a missunderstanding by activating this  cause as i remember (but not 100 % sure) this action is executed after merge, but merge is now blocked because of this check, which gets never green?
@matbmoser @arnoweiss

That sounds like accurate analysis. @matbmoser - can you prep a PR for this?

should be fixed by https://github.com/eclipse-tractusx/.eclipsefdn/pull/108

thanks for the fix!