can't make entrypoints to work

Hello,
I only work with brunch since today because I need an alternative for Webpack. So far, I have been able to define an entry point or a JavaScript file via Webpack. Additional files have been inserted via "import". These imported files are partly also in the "node_modules" -directory and could be inserted automatically by a "resolve" in Webpack. If the modules in the "node_modules" directory also have dependencies, they are also resolved via the "resolve" in Webpack. This option I just can not find in brunch. In addition, brunch seems to include all directories or modules in the "node_modules" folder, although I need only certain directories or modules.
App
│───	app/    // es6-files
├───	node_modules/   // external modules
├───	tmp/   // output

By convention Brunch compile all js files inside app. No need to define an entry point. Node modules should be out of your working.
I have a set up quite similar to yours:
/
|--- src   <- input folder with css and js
     |--- main.js   <- js "entry" module
|--- node_module
|--- www
     |--- src   <- output
|--- brunch-config.js
|--- package.json

In the brunch-config.js you can configure the input folder to watch and the output this way:
module.exports = {
  paths: {
    watched: ['src'],
    public: 'www/src'
  },
  modules: {
    autoRequire: {
      'js/main.js': ['src/main']
    }
  },
  npm: {
    styles: {
      'normalize.css': ['normalize.css']
    }
  },
  files: {
    javascripts: {
      joinTo: {
        'js/vendor.js': /^(?!src\/)/,
        'js/main.js': /^(src\/.*\.js)/
      }
    },
    stylesheets: {
      joinTo: {
        'css/vendor.css': /^node_modules/,
        'css/main.css': /^(src\/)/
      }
    }
  }
};

It asks brunch to:

watch /src and to output in /www/src
compile normalize.css from a npm module in vendor.css
compile all css/stylus/sass files (depending on your brunch extensions) inside /src in /www/src/main.css
compile all js modules inside /src in /www/src/main.js
compile all js modules from npm in /www/src/vendor.js
autorequire the "entry" module /scr/main.js


Error when running with own configuration

After successfully running with the test configuration, I now tried running pre-processing with my own config and bam files and I get this fatal error
 FATAL | ccs ERROR: Missing base features: IPD or PulseWidth

any ideas why this is?

Sounds like an issue with the input subreads bam file. See https://github.com/PacificBiosciences/pbbioconda/issues/432#issuecomment-913427865.

@jemunro I have demultiplex bam files what can I do to generate bam reads with pw and ip tags?

The pipeline is designed for Sequel subreads output - can you run:
samtools view  <input.bam> | cut -f1,12- | head -1
and share the ouput to confirm the format of the pacbio reads?
Are able to get raw subreads output file and try that? (i.e. the file output from the sequel run).

Hi  Cyril,
Your input file contains CCS reads not subreads, which unfortunately is not a compatible with the pipeline. You will need to obtain the original subreads BAM file in order to use the pipeline.


How do I use it in vllm deployment

How can I use this approach in vllm deployment without training，can you give me a specific example. thx

Thank you for bringing this to our attention. Unfortunately, the current version of vLLM does not support the return of attention scores. However, we are pleased to inform you that this functionality is planned in the next release of the software.
In the meantime, we are working diligently to implement paged attention—the key feature of vLLM—as well as Flash decoding. These enhancements aim to accelerate the generation process and decrease the GPU memory of the KV cache.
we appreciate your patience while we work on these developments.
Stay tuned for updates.

@ChenxinAn-fdu  OK, thanks for your response

looking forward to the support in vllm!

@ChenxinAn-fdu Dose vllm support DCA now? We'd like to use this feature in the deployment.

@Shuai-Xie Hi, I left an issue in their official repo, but it seems that the current version of vllm only supports returning the output tensor without softmax_lse. We plan to implement it ourselves.
If you do not need continual batching, the current repo has implemented flash_decoding. You can use it for some preliminary experiments.


Rem

Not sure if brought up before but I was thinking using rem instead of pixels might be closer to android's dp sizing. Then you could use media query break points, set up a suitable font size at root and everything would scale. It's not going to be as accurate as android's dp but would help a lot. Current px values would work as fallback.

I definitely agree with this suggestion. I prefer thinking in relative sizes rather than in pixels, especially since responsive design became popular. A good article I read on the subject a while back: http://csswizardry.com/2011/12/measuring-and-sizing-uis-2011-style/

I just opened a pull request for this: #433.

@whodidthis @a1russell does #248 help?

@shaurya947 Are you asking if em is preferable to px in lieu of rem, I'd say yes; however, I would still have preferred rem. But I'm not going to re-do #433 if that's what you're asking. It was a lot of work, and it got me nothing.

My bad @a1russell, I actually meant to link to #2039.
Sorry to hear that buddy! Let's just see where 2039 goes, and if we need to make any changes to it..

@shaurya947: Ah, okay, gotcha. Looks like #2039 is similar to what I was trying to achieve, at least for one component. I haven't looked at this project since my PR was rejected, though, so I'm not sure if it covers everything. But it does look to be a step in the right direction. Best of luck!


Insecure random number generator

Hi,
The function basic_random_generator that is used by default to generate random numbers is insecure. It uses Perl's built-in "rand" function and the Perl docs state:
        "rand()" is not cryptographically secure. You should not rely on
        it in security-sensitive situations. As of this writing, a number
        of third-party CPAN modules offer random number generators
        intended by their authors to be cryptographically secure,
        including: Data::Entropy, Crypt::Random, Math::Random::Secure, and
        Math::TrulyRandom.

I would argue that while rand() is obviously not sufficient for cryptography, it is sufficient for password generation for most people.
However, precisely because rand() has known shortcomings, the module provides a built-in means for users to supply their own sources of randomness.
A new version of the module is nearly ready to be released, and it comes with two notable improvements in this regard. Firstly, it makes it a little easier to provide custom sources of randomness through polymorphism, and secondly, it will ship with a ready-to-use class that uses random.org's web service as it's source or randomness.
You can get a sneak-peak at the new version of the module, and, if you like, contribute the code to interface with another source of randomness, in the branch CPAN-prep: https://github.com/bbusschots/xkpasswd.pm/tree/CPAN-Prep

Den 2015-05-16 19:42, Bart Busscots skrev:

I would argue that while |rand()| is obviously not sufficient for
cryptography, it is sufficient for password generation for most people.

I don't know how rand() is implemented in Perl, but the docs clearly
recommend against using it in security-sensitive situations. Why take
the risk?
Also, how can you assume that users won't use the password as an
encryption key?

However, precisely because |rand()| has known shortcomings, the module
provides a built-in means for users to supply their own sources of
randomness.

If they know about it, that is. I didn't, until I read the source code.
Why not use a good RNG by default? Just read /dev/urandom or some Perl
module.

A new version of the module is nearly ready to be released, and it comes
with two notable improvements in this regard. Firstly, it makes it a
little easier to provide custom sources of randomness through
polymorphism, and secondly, it will ship with a ready-to-use class that
uses random.org's web service as it's source or randomness.

How is that better than /dev/urandom? Now I have to trust both my
computer and some external web service that I know nothing about.

You can get a sneak-peak at the new version of the module, and, if you
like, contribute the code to interface with another source of
randomness, in the branch CPAN-prep:
https://github.com/bbusschots/xkpasswd.pm/tree/CPAN-Prep

No thanks, I found a better program:
https://github.com/redacted/XKCD-password-generator
I just don't want anybody else to use a bad RNG by accident.
--
Pelle

Firstly and most importantly, attackers trying to guess a password or reverse a hash have no way of knowing how it was generated, so the RNG is not something they can attack. The strength of passwords lies in their length and their alphabet, and on that count, the passwords generated by this module are very strong indeed.
The key question is, are passwords generated with this module stronger than those you could make up with your own imagination? The answer to that is definitely yes.
To answer your specific questions, why rand()? Because rand() is part of every standard perl distribution, and the other models are not. Until the code is in CPAN I wanted it to be installable without the need to install any non-standard modules.
Why not use /dev/urand? Simple, it is not cross-platform. I may not like Windows, but a lot of people use it all the same, and I wanted my module to work for them too.
Having said all that - I'm going to update the module to use Data::Entropy, Crypt::Random, Math::Random::Secure, or  Math::TrulyRandom if they are installed, and only fall back on rand() when none of those modules are available. After all, in a contests between rand() and the human imagination, rand() is the clear winner!

Den 2015-05-16 21:13, Bart Busscots skrev:

Firstly and most importantly, attackers trying to guess a password or
reverse a hash have no way of knowing how it was generated, so the RNG
is not something they can attack. The strength of passwords lies in
their length and their alphabet, and on that count, the passwords
generated by this module are very strong indeed.

Indeed, as long as the software doesn't get very popular...

The key question is, are passwords generated with this module stronger
than those you could make up with your own imagination? The answer to
that is definitely yes. What ever you can say about |rand()|, it plus a
big dictionary file will produce a heck of a lot more randomness than
the human brain ever could!

True :-)

To answer your specific questions, why |rand()|? Because |rand()| is
part of every standard perl distribution, and the other models are not.
Until the code is in CPAN I wanted it to be installable without the need
to install any non-standard modules.
Why not use |/dev/urand|? Simple, it is not cross-platform. I may not
like Windows, but a lot of people use it all the same, and I wanted my
module to work for them too.

Right, but it could use /dev/urandom if available and otherwise fall
back on rand().

Having said all that - I'm going to update the module to use
|Data::Entropy|, |Crypt::Random|, |Math::Random::Secure|, or
|Math::TrulyRandom| if they are installed, and only fall back on
|rand()| when none of those modules are available. After all, in a
contests between |rand()| and the human imagination, |rand()| is the
clear winner!

Sounds fair :-) Please note it in the README also.
--
Pelle

I think this issue has been well addressed in the latest commit to the CPAN-Prep branch: https://github.com/bbusschots/xkpasswd.pm/commit/b8feb39a85fb0ec0b4fecc63137e0555d85ba2aa
Since the CPAN-Prep branch will be merged into the main branch any day now, I'm not going to back-port any of this to the current main branch.

Great! :-)


Export to RabbitMQ

Hello @quyse!
Thanks for the useful library, we have used it for one of our client. Although we have needed in such feature as connecting to RabbitMQ.
I hope this feature will be useful for someone else too and so suggest you to give us some feedback about contribution and merge this PR after all fixes.

Hi @Znack! Looks very good, thanks for the contribution! I'm not sure why PR #17 (presumably by your colleague) was self-closed, and was too busy to get back to him, sorry! Merged now.

Thanks for merging, the first PR was just too raw, so we decided to refactor it little bit :)


LUCENE-10058: fix gradle lucene:benchmark:run error

When running ./gradlew lucene:benchmark:run, the default thread name is main not ParallelTaskThread, StringIndexOutOfBoundsException error is thrown.
I set the threadIndex default value to 0 to fix this bug.

Thanks @xiaoshi2013!  Could you also open a backport PR against branch_8x in lucene-solr github repository?  Thanks!

Yes, I will submit a PR to branch_8x soon.
At 2021-08-23 22:37:45, "Michael McCandless" @.***> wrote:
Thanks @xiaoshi2013! Could you also open a backport PR against branch_8x in lucene-solr github repository? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

As you suggested, I have also submitted a PR for lucene_8x: LUCENE-10051, thanks.
At 2021-08-23 22:37:45, "Michael McCandless" @.***> wrote:
Thanks @xiaoshi2013! Could you also open a backport PR against branch_8x in lucene-solr github repository? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Thanks @xiaoshi2013! Could you also open a backport PR against branch_8x in lucene-solr github repository? Thanks!

Hi @mikemccand As you suggested, I have also submitted a PR for lucene_8x: LUCENE-10051, the PR is #2559.


dart2js - minor optimization opportunity for identical check

This issue was originally filed by @bp74

What steps will reproduce the problem?
I have a very hot function and tried to optimize it for dart2js. Thereby i noticed an optimization opportunity which doesn't improve the performance but still it would be a nice if the compiler knows how to optimize it.
Dart code (first version):
  if (foo != null && !identical(foo, _foo)) {
    // Do stuff
  }
Dart code (second version):
  if (foo!= null) {
    if (!identical(foo, _foo)) {
      // Do stuff
    }
  }
What is the expected output? What do you see instead?
The first version generates this JavaScript code:
  var t1;
  if (foo != null) {
    t1 = this._foo;
    t1 = foo == null ? t1 != null : foo !== t1;
  } else
    t1 = false;
  if (t1) {
    // Do stuff
  }
The second version generates this JavaScript code:
  var t1;
  if (foo != null) {
    t1 = this._foo;
    if (foo == null ? t1 != null : foo !== t1) {
      // Do stuff
    }
  }
I can imagine that the first version of the Dart code may be harder to optimize, but the second version should be easier because the test for "foo == null" is always false in this block. In a perfect world the compiler would recognize this in the first version too and the JavaScript code would look like this:
  if (foo != null && foo !== _foo) {
    // Do stuff
  }
What version of the product are you using? On what operating system?
Dart Editor version 1.2.0.dev_01_00 (DEV)
Dart SDK version 1.2.0-dev.1.0
Please provide any additional information below.

Closing, since the current code generated is:
  update$2: function(a, b) {
    if (a != null && a !== this._a)
      this._a = a;
    if (b != null)
      if (b !== this._b)
        this._b = b;
  }

There is a related issue discussed at https://github.com/dart-lang/sdk/issues/28330: if (A&&B) is generated as the test if ( phi(false, B)), so we don't learn as much as we would if the code was if (A) if (B) ....


Remove version: 360.360Chrome.X version 22.3.3015.64

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://down.360safe.com/cse/360csex_22.3.3015.64.exe
Status Code: 200
(Automated message - build 896)

Close with reason: Package still available.;


Import SVG?

Hi I have a use case where I would like to import an existing svg then add more elements to it using drawsvg is that possible? Is there an example for how to do that?

Modifying an existing SVG is not an intended use case of drawsvg.  This is hard for library to do in a robust way.
I suggest you either:

Look into drawsvg.Raw (to inject arbitrary SVG text into the drawing) or
Use an XML parsing library to merge your existing SVG with the output of d.as_svg().


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/oweitman/ioBroker.mytime

[ ] [E605] No actual year found in copyright. Please add "Copyright (c) 2023 oweitman<EMAIL_ADDRESS>at the end of README.md
[ ] [E701] No actual year found in LICENSE. Please add "Copyright (c) 2023 oweitman<EMAIL_ADDRESS>at the start of LICENSE

I have also found warnings that may be fixed if possible.

[ ] [W171] "common.title" is deprecated in io-package.json
[ ] [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W170] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[ ] [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

I noticed that in the io-package under “restartAdapters” only vis is available. If your widget also runs with vis-2, you might want to add “vis-2” to the list too.
I found vis as “dependencies” in the io package. Please remove this dependency.
Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

should be fixed


Crash in dns.go

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
What happened:
Applied ClusterIssuer resource change (enabled DNS-01 with CloudDNS).
Applied changes to existing ingresses ( removed tls-acme, added certmanager.k8s.io/cluster-issuer, certmanager.k8s.io/acme-challenge-type, certmanager.k8s.io/acme-dns01-provider to switch to DNS-01 )
Deleted existing certificate resources manually to work around the fact that ingress-shim still doesn't update them correctly if they already exist.
Tested this procedure in 2 dev / staging environments with different domains, and it worked fine (cert-manager reissuing certificates correctly using DNS-01)
Moved to production (8 certificates to process instead of 4) and the following crash happened :
I0531 16:43:15.673137       1 leaderelection.go:175] attempting to acquire leader lease  kube-system/cert-manager-controller...
I0531 16:43:15.691168       1 leaderelection.go:184] successfully acquired lease kube-system/cert-manager-controller
I0531 16:43:15.791984       1 controller.go:138] clusterissuers controller: syncing item 'letsencrypt'
I0531 16:43:15.792049       1 controller.go:152] ingress-shim controller: syncing item 'production/api-ingress'
I0531 16:43:15.792357       1 sync.go:123] Certificate "api-SECRETDOMAIN1.com-tls" for ingress "api-ingress" already exists
I0531 16:43:15.792380       1 sync.go:126] Certificate "api-SECRETDOMAIN1.com-tls" for ingress "api-ingress" is up to date
I0531 16:43:15.792411       1 controller.go:166] ingress-shim controller: Finished processing work item "production/api-ingress"
I0531 16:43:15.792087       1 acme.go:159] getting private key (letsencrypt-private-key->tls.key) for acme issuer kube-system/letsencrypt
I0531 16:43:15.792547       1 controller.go:152] ingress-shim controller: syncing item 'production/static-ingress'
I0531 16:43:15.792710       1 sync.go:123] Certificate "static-SECRETDOMAIN1.com-tls" for ingress "static-ingress" already exists
I0531 16:43:15.792733       1 sync.go:126] Certificate "static-SECRETDOMAIN1.com-tls" for ingress "static-ingress" is up to date
I0531 16:43:15.792835       1 controller.go:166] ingress-shim controller: Finished processing work item "production/static-ingress"
I0531 16:43:15.792862       1 controller.go:152] ingress-shim controller: syncing item 'production/static-ingress-SECRETDOMAIN2'
I0531 16:43:15.791992       1 controller.go:152] ingress-shim controller: syncing item 'production/ws-ingress-SECRETDOMAIN2'
I0531 16:43:15.792984       1 sync.go:123] Certificate "ws-SECRETDOMAIN2.com-tls" for ingress "ws-ingress-SECRETDOMAIN2" already exists
I0531 16:43:15.793022       1 sync.go:126] Certificate "ws-SECRETDOMAIN2.com-tls" for ingress "ws-ingress-SECRETDOMAIN2" is up to date
I0531 16:43:15.793059       1 controller.go:166] ingress-shim controller: Finished processing work item "production/ws-ingress-SECRETDOMAIN2"
I0531 16:43:15.793101       1 controller.go:152] ingress-shim controller: syncing item 'production/ws-ingress'
I0531 16:43:15.793201       1 sync.go:123] Certificate "ws-SECRETDOMAIN1.com-tls" for ingress "ws-ingress" already exists
I0531 16:43:15.793235       1 sync.go:126] Certificate "ws-SECRETDOMAIN1.com-tls" for ingress "ws-ingress" is up to date
I0531 16:43:15.793274       1 controller.go:166] ingress-shim controller: Finished processing work item "production/ws-ingress"
I0531 16:43:15.792196       1 controller.go:152] ingress-shim controller: syncing item 'production/api-SECRETDOMAIN2-ingress'
I0531 16:43:15.793344       1 sync.go:123] Certificate "api-SECRETDOMAIN2.com-tls" for ingress "api-SECRETDOMAIN2-ingress" already exists
I0531 16:43:15.793379       1 sync.go:126] Certificate "api-SECRETDOMAIN2.com-tls" for ingress "api-SECRETDOMAIN2-ingress" is up to date
I0531 16:43:15.793417       1 controller.go:166] ingress-shim controller: Finished processing work item "production/api-SECRETDOMAIN2-ingress"
I0531 16:43:15.792218       1 controller.go:152] ingress-shim controller: syncing item 'production/sc-ingress'
I0531 16:43:15.793488       1 sync.go:123] Certificate "sc-SECRETDOMAIN1.com-tls" for ingress "sc-ingress" already exists
I0531 16:43:15.793524       1 sync.go:126] Certificate "sc-SECRETDOMAIN1.com-tls" for ingress "sc-ingress" is up to date
I0531 16:43:15.793545       1 controller.go:166] ingress-shim controller: Finished processing work item "production/sc-ingress"
I0531 16:43:15.792249       1 controller.go:152] ingress-shim controller: syncing item 'production/sc-ingress-SECRETDOMAIN2'
I0531 16:43:15.793576       1 sync.go:123] Certificate "sc-SECRETDOMAIN2.com-tls" for ingress "sc-ingress-SECRETDOMAIN2" already exists
I0531 16:43:15.793603       1 sync.go:126] Certificate "sc-SECRETDOMAIN2.com-tls" for ingress "sc-ingress-SECRETDOMAIN2" is up to date
I0531 16:43:15.793616       1 controller.go:166] ingress-shim controller: Finished processing work item "production/sc-ingress-SECRETDOMAIN2"
I0531 16:43:15.793471       1 logger.go:67] Calling GetAccount
I0531 16:43:15.794070       1 sync.go:123] Certificate "www-SECRETDOMAIN2.com-tls" for ingress "static-ingress-SECRETDOMAIN2" already exists
I0531 16:43:15.794100       1 sync.go:126] Certificate "www-SECRETDOMAIN2.com-tls" for ingress "static-ingress-SECRETDOMAIN2" is up to date
I0531 16:43:15.794134       1 controller.go:166] ingress-shim controller: Finished processing work item "production/static-ingress-SECRETDOMAIN2"
I0531 16:43:17.166439       1 setup.go:73] letsencrypt: verified existing registration with ACME server
I0531 16:43:17.170936       1 controller.go:152] clusterissuers controller: Finished processing work item "letsencrypt"
I0531 16:43:17.735501       1 controller.go:177] certificates controller: syncing item 'production/api-SECRETDOMAIN2.com-tls'
I0531 16:43:17.735540       1 controller.go:177] certificates controller: syncing item 'production/api-SECRETDOMAIN1.com-tls'
I0531 16:43:17.735635       1 controller.go:177] certificates controller: syncing item 'production/sc-SECRETDOMAIN1.com-tls'
I0531 16:43:17.735951       1 sync.go:239] Preparing certificate production/api-SECRETDOMAIN2.com-tls with issuer
I0531 16:43:17.735999       1 acme.go:159] getting private key (letsencrypt-private-key->tls.key) for acme issuer kube-system/letsencrypt
I0531 16:43:17.736074       1 sync.go:239] Preparing certificate production/api-SECRETDOMAIN1.com-tls with issuer
I0531 16:43:17.736130       1 acme.go:159] getting private key (letsencrypt-private-key->tls.key) for acme issuer kube-system/letsencrypt
I0531 16:43:17.736396       1 sync.go:177] Certificate production/sc-SECRETDOMAIN1.com-tls scheduled for renewal in 646 hours
I0531 16:43:17.736450       1 controller.go:191] certificates controller: Finished processing work item "production/sc-SECRETDOMAIN1.com-tls"
I0531 16:43:17.736496       1 controller.go:177] certificates controller: syncing item 'production/sc-SECRETDOMAIN2.com-tls'
I0531 16:43:17.736546       1 prepare.go:247] Cleaning up previous order for certificate production/api-SECRETDOMAIN2.com-tls
I0531 16:43:17.736746       1 prepare.go:263] Cleaning up old/expired challenges for Certificate production/api-SECRETDOMAIN2.com-tls
I0531 16:43:17.736759       1 logger.go:22] Calling CreateOrder
I0531 16:43:17.736830       1 prepare.go:247] Cleaning up previous order for certificate production/api-SECRETDOMAIN1.com-tls
I0531 16:43:17.736872       1 prepare.go:263] Cleaning up old/expired challenges for Certificate production/api-SECRETDOMAIN1.com-tls
I0531 16:43:17.736912       1 logger.go:22] Calling CreateOrder
I0531 16:43:17.737030       1 sync.go:177] Certificate production/sc-SECRETDOMAIN2.com-tls scheduled for renewal in 1151 hours
I0531 16:43:17.737061       1 controller.go:191] certificates controller: Finished processing work item "production/sc-SECRETDOMAIN2.com-tls"
I0531 16:43:17.737108       1 controller.go:177] certificates controller: syncing item 'production/ws-SECRETDOMAIN1.com-tls'
I0531 16:43:17.736566       1 controller.go:177] certificates controller: syncing item 'production/static-SECRETDOMAIN1.com-tls'
I0531 16:43:17.737501       1 sync.go:177] Certificate production/ws-SECRETDOMAIN1.com-tls scheduled for renewal in 94 hours
I0531 16:43:17.737529       1 controller.go:191] certificates controller: Finished processing work item "production/ws-SECRETDOMAIN1.com-tls"
I0531 16:43:17.737571       1 controller.go:177] certificates controller: syncing item 'production/www-SECRETDOMAIN2.com-tls'
I0531 16:43:17.737305       1 controller.go:177] certificates controller: syncing item 'production/ws-SECRETDOMAIN2.com-tls'
I0531 16:43:17.738288       1 sync.go:177] Certificate production/static-SECRETDOMAIN1.com-tls scheduled for renewal in 1434 hours
I0531 16:43:17.738299       1 sync.go:177] Certificate production/www-SECRETDOMAIN2.com-tls scheduled for renewal in 1293 hours
I0531 16:43:17.738409       1 controller.go:191] certificates controller: Finished processing work item "production/www-SECRETDOMAIN2.com-tls"
I0531 16:43:17.738369       1 controller.go:191] certificates controller: Finished processing work item "production/static-SECRETDOMAIN1.com-tls"
I0531 16:43:17.738757       1 sync.go:177] Certificate production/ws-SECRETDOMAIN2.com-tls scheduled for renewal in 1151 hours
I0531 16:43:17.738833       1 controller.go:191] certificates controller: Finished processing work item "production/ws-SECRETDOMAIN2.com-tls"
I0531 16:43:18.592558       1 acme.go:193] Created order for domains: [{dns api.SECRETDOMAIN2.com} {dns stats.SECRETDOMAIN2.com}]
I0531 16:43:18.592686       1 logger.go:52] Calling GetAuthorization
I0531 16:43:18.627645       1 acme.go:193] Created order for domains: [{dns api-int.SECRETDOMAIN1.com} {dns api.SECRETDOMAIN1.com} {dns stats.SECRETDOMAIN1.com}]
I0531 16:43:18.627717       1 logger.go:52] Calling GetAuthorization
I0531 16:43:18.783531       1 logger.go:52] Calling GetAuthorization
I0531 16:43:18.944275       1 logger.go:52] Calling GetAuthorization
I0531 16:43:18.972728       1 logger.go:52] Calling GetAuthorization
I0531 16:43:19.130297       1 logger.go:77] Calling DNS01ChallengeRecord
I0531 16:43:19.130407       1 logger.go:77] Calling DNS01ChallengeRecord
I0531 16:43:19.130436       1 prepare.go:263] Cleaning up old/expired challenges for Certificate production/api-SECRETDOMAIN2.com-tls
I0531 16:43:19.130450       1 logger.go:47] Calling GetChallenge
I0531 16:43:19.266562       1 logger.go:77] Calling DNS01ChallengeRecord
I0531 16:43:19.266637       1 prepare.go:263] Cleaning up old/expired challenges for Certificate production/api-SECRETDOMAIN1.com-tls
I0531 16:43:19.266681       1 logger.go:47] Calling GetChallenge
I0531 16:43:19.290991       1 dns.go:78] Checking DNS propagation for "api.SECRETDOMAIN2.com" using name servers: [<IP_ADDRESS>:53]
I0531 16:43:19.309791       1 dns.go:85] DNS record for "api.SECRETDOMAIN2.com" not yet propagated
I0531 16:43:19.310159       1 sync.go:177] Certificate production/api-SECRETDOMAIN2.com-tls scheduled for renewal in 526 hours
E0531 16:43:19.310373       1 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
/usr/local/go/src/runtime/asm_amd64.s:509
/usr/local/go/src/runtime/panic.go:491
/usr/local/go/src/runtime/panic.go:63
/usr/local/go/src/runtime/signal_unix.go:367
/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88
/usr/local/go/src/runtime/asm_amd64.s:2337
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xece4c1]

goroutine 112 [running]:
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x111
panic(0x13c8d00, 0x1f699d0)
	/usr/local/go/src/runtime/panic.go:491 +0x283
github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1.(*ACMEIssuerDNS01Config).Provider(0x0, 0xc4202eeec8, 0x8, 0x1f6a550, 0x0, 0x1f7c7b0)
	/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20 +0x51
github.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).solverForIssuerProvider(0xc420f75420, 0xc4202eeec8, 0x8, 0x134d380, 0xc42067a9a0, 0xc420f5e600, 0x1f145a0)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136 +0x7a
github.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).Present(0xc420f75420, 0x1f145a0, 0xc42004f140, 0xc420f77040, 0xc4206322a0, 0x6a, 0xc4204075c0, 0x5b, 0xc420888020, 0x6, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67 +0x5a
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentChallenge(0xc420469680, 0x1f145a0, 0xc42004f140, 0x1f1c300, 0xc420f6d150, 0xc420f77040, 0xc4206322a0, 0x6a, 0xc4204075c0, 0x5b, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236 +0x3a1
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).processChallenge(0xc420469680, 0x1f145a0, 0xc42004f140, 0x1f1c300, 0xc420f6d150, 0xc420f77040, 0xc4206322a0, 0x6a, 0xc4204075c0, 0x5b, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173 +0xb6
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentOrder(0xc420469680, 0x1f145a0, 0xc42004f140, 0x1f1c300, 0xc420f6d150, 0xc420f77040, 0xc420841a40, 0x159b3b8, 0x30)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146 +0x928
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).Prepare(0xc420469680, 0x1f145a0, 0xc42004f140, 0xc420f77040, 0x2, 0xed11d0)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94 +0x3df
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).issue(0xc42042e1c0, 0x1f145a0, 0xc42004f140, 0x1f14860, 0xc420469680, 0xc420f77040, 0xc421164000, 0x0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240 +0x163
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Sync(0xc42042e1c0, 0x1f145a0, 0xc42004f140, 0xc420109a88, 0x0, 0x0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108 +0x385
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).processNextWorkItem(0xc42042e1c0, 0x1f145a0, 0xc42004f140, 0xc4202ff560, 0x1c, 0x2, 0x2)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215 +0x2b5
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).(github.com/jetstack/cert-manager/pkg/controller/certificates.processNextWorkItem)-fm(0x1f145a0, 0xc42004f140, 0xc4202ff560, 0x1c, 0x2, 0x134d380)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69 +0x52
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker.func1(0xc42042e1c0, 0xc420e21da8, 0xc4203041e0, 0x134d380, 0xc420362ca0, 0x0, 0x0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178 +0x24f
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker(0xc42042e1c0, 0xc4203041e0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183 +0x166
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run.func1()
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x33
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4206495c0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x5e
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4206495c0, 0x3b9aca00, 0x0, 0x600000001, 0xc4203041e0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0xbd
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4206495c0, 0x3b9aca00, 0xc4203041e0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d
created by github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x182

What you expected to happen:
cert-manager reissuing certificates correctly using DNS-01 without crashing.
How to reproduce it (as minimally and precisely as possible):
See above
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): client v1.9.7 , server v1.10.2-gke.1 ( the 2 environments that do NOT crash are on "v1.10.2-gke.3" however)
Cloud provider or hardware configuration**: GKE
Install tools: Helm, cert-manager-v0.3.1
Others:

Just made some progress to mitigate the crash (even if I didn't address the root cause)
The stack trace hinted at an issue with the ClusterIssuer config ( https://github.com/jetstack/cert-manager/blob/master/pkg/issuer/acme/dns/dns.go#L136 )
I simply deleted that resource and recreated it. No more crashes.
For reference, here's the resource content that was causing a panic :
Name:         letsencrypt
Namespace:
Labels:       <none>
Annotations:  kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"ClusterIssuer","metadata":{"annotations":{},"name":"letsencrypt","namespace":""},"spec":{"acme":{"e...
API Version:  certmanager.k8s.io/v1alpha1
Kind:         ClusterIssuer
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-05-31T12:30:39Z
  Generation:          1
  Resource Version:    123695238
  Self Link:           /apis/certmanager.k8s.io/v1alpha1/clusterissuers/letsencrypt
  UID:                 6d3aa8e8-64ce-11e8-9eeb-42010a8400dc
Spec:
  Acme:
    Email<EMAIL_ADDRESS>    Http 01:
    Private Key Secret Ref:
      Key:
      Name:  letsencrypt-private-key
    Server:  https://acme-v02.api.letsencrypt.org/directory
Status:
  Acme:
    Uri:  https://acme-v02.api.letsencrypt.org/acme/acct/REDACTED
  Conditions:
    Last Transition Time:  2018-05-31T17:39:47Z
    Message:               The ACME account was registered with the ACME server
    Reason:                ACMEAccountRegistered
    Status:                True
    Type:                  Ready
Events:
  Type     Reason                Age                 From          Message
  ----     ------                ----                ----          -------
  Warning  ErrVerifyACMEAccount  21m                 cert-manager  Failed to verify ACME account: acme: urn:ietf:params:acme:error:serverInternal: failed check for existing account
  Warning  ErrInitIssuer         21m                 cert-manager  Error initializing issuer: acme: urn:ietf:params:acme:error:serverInternal: failed check for existing account
  Warning  ErrInitIssuer         19m (x12 over 21m)  cert-manager  Error initializing issuer: acme: urn:ietf:params:acme:error:serverInternal: failed check for existing account
  Warning  ErrVerifyACMEAccount  17m (x13 over 21m)  cert-manager  Failed to verify ACME account: acme: urn:ietf:params:acme:error:serverInternal: failed check for existing account

Fixed as part of #708! Sorry for the non-response earlier. This bug report slipped!
The patch will be in v0.3.2 onwards.


No tray icon on startup with KDE

On system startup the tray icon is missing.
Disable and enable it from Setting view make it visible.
Scenario:
OS: Ubuntu 18.04 with KDE Plasma 5.19.4
Ferdie: 5.5.0 (x64) installed via DEB package
Ferdie is configured to show notification icon in the tray area.
On startup the app is started but no icon is visible in the tray.
Disable and enable the tray icon from setting view make it visible until system shutdown.
Debug info:
{"host":{"platform":"linux","release":"5.4.0-45-generic","screens":[{"id":13761487533244482,"bounds":{"x":0,"y":0,"width":1920,"height":1080},"workArea":{"x":0,"y":0,"width":1920,"height":1080},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}","depthPerComponent":8,"size":{"width":1920,"height":1080},"workAreaSize":{"width":1920,"height":1080},"scaleFactor":1,"rotation":0,"internal":false,"touchSupport":"unknown"},{"id":9585557217974596,"bounds":{"x":1920,"y":0,"width":1920,"height":1080},"workArea":{"x":1920,"y":0,"width":1920,"height":1044},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}","depthPerComponent":8,"size":{"width":1920,"height":1080},"workAreaSize":{"width":1920,"height":1044},"scaleFactor":1,"rotation":0,"internal":false,"touchSupport":"unknown"}]},"ferdi":{"version":"5.5.0","electron":"8.2.3","installedRecipes":[{"id":"linkedin","version":"1.0.0"},{"id":"messenger","version":"1.1.0"},{"id":"skype","version":"1.3.0"},{"id":"slack","version":"1.0.15"},{"id":"telegram","version":"3.0.0"},{"id":"whatsapp","version":"2.0.3"},{}],"devRecipes":[],"services":[{"id":"5dd7143f-c67f-4369-8fbb-df09032dd99e","recipe":"whatsapp","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"aaefb64d-10f8-4379-a723-64dc4ba34d14","recipe":"telegram","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"68bcece1-2287-486f-81dc-80ff1c4bec84","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"ed134c88-d506-43fd-9e2a-37fdad497922","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"e0d9dd79-f055-4362-9c6a-f625b985835e","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"0f18ecee-b55e-43ea-bdfe-213e7aeab586","recipe":"skype","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"55d0adc5-c478-44c6-8678-b5e579e2b293","recipe":"linkedin","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"8031ab98-4731-4fc4-87bd-6844ce35b1fc","recipe":"messenger","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true}],"messages":[{"type":"error","info":["error","[mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: 'Reaction[Autorun@160]'",{}]},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"You are using Ferdi without a server"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"You are using Ferdi without a server"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"You are using Ferdi without a server"},{"type":"log","info":["log","Notification from Telegram",{"icon":"/assets/img/notification-badge.gif","body":"","tag":"c1056857024_489413804680899826","silent":true}]},{"type":"log","info":["log","Notification from Slack IAM",{"body":"","icon":"/assets/img/notification-badge.gif","tag":"tag_1599462145.002300","silent":true}]},{"type":"log","info":["log","Notification from Slack IAM",{"body":"","icon":"/assets/img/notification-badge.gif","tag":"tag_1599462145.002500","silent":true}]},{"type":"log","info":["log","Notification from WhatsApp",{"tag":"393337154314@c.us","renotify":true,"dir":"auto","lang":"it","silent":true,"body":"","icon":"/assets/img/notification-badge.gif"}]},{"type":"log","info":["log","Notification from WhatsApp",{"tag":"393337154314@c.us","renotify":true,"dir":"auto","lang":"it","silent":true,"body":"","icon":"/assets/img/notification-badge.gif"}]},{"type":"log","info":["log","Notification from WhatsApp",{"tag":"393495311399-1521224565@g.us","renotify":true,"dir":"auto","lang":"it","silent":true,"body":"","icon":"/assets/img/notification-badge.gif"}]},{"type":"log","info":["log","Notification from Telegram",{"icon":"/assets/img/notification-badge.gif","body":"","tag":"c1056857024_489413804680899826","silent":true}]}],"workspaces":[],"windowSettings":{"width":800,"height":600},"settings":{"autoLaunchInBackground":false,"runInBackground":true,"reloadAfterResume":true,"enableSystemTray":true,"startMinimized":false,"minimizeToSystemTray":"","privateNotifications":true,"showDisabledServices":true,"showMessageBadgeWhenMuted":true,"showDragArea":false,"enableSpellchecking":true,"spellcheckerLanguage":"it-it","darkMode":true,"locale":"it","fallbackLocale":"en-US","beta":false,"isAppMuted":false,"enableGPUAcceleration":"","serviceLimit":5,"server":"You are using Ferdi without a server","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernate":false,"hibernateOnStartup":true,"hibernationStrategy":300,"inactivityLock":0,"automaticUpdates":true,"showServiceNavigationBar":false,"universalDarkMode":true,"adaptableDarkMode":true,"accentColor":"#7367f0","serviceRibbonWidth":68,"iconSize":20,"sentry":false,"navigationBarBehaviour":"never","customTodoServer":"","todoServer":"isUsingCustomTodoService"},"features":{"isSpellcheckerIncludedInCurrentPlan":true,"needToWaitToProceed":false,"needToWaitToProceedConfig":{"delayOffset":3600000,"wait":10000},"isServiceProxyEnabled":true,"isServiceProxyIncludedInCurrentPlan":true,"isAnnouncementsEnabled":true,"isWorkspaceIncludedInCurrentPlan":true,"isWorkspaceEnabled":true,"isCommunityRecipesIncludedInCurrentPlan":true,"isSpellcheckerPremiumFeature":false,"isServiceProxyPremiumFeature":true,"isWorkspacePremiumFeature":false,"isSettingsWSEnabled":false,"isServiceLimitEnabled":false,"serviceLimitCount":0,"isCommunityRecipesPremiumFeature":false,"isCustomUrlIncludedInCurrentPlan":true,"isMagicBarEnabled":true,"isTeamManagementIncludedInCurrentPlan":true,"isTodosEnabled":true,"isTodosIncludedInCurrentPlan":true,"defaultTrialPlan":"franz-pro-yearly","subscribeURL":"https://getferdi.com","planSelectionURL":"https://getferdi.com","hasInlineCheckout":true,"isPlanSelectionEnabled":false,"isTrialStatusBarEnabled":false,"canSkipTrial":true,"pricingConfig":{"currency":"$","currencyID":"USD","plans":{"personal":{"monthly":{"id":"ferdi-free","price":0,"billed":0},"yearly":{"id":"ferdi-completely-free","price":0,"billed":0}},"pro":{"monthly":{"id":"ferdi-still-free","price":0,"billed":0},"yearly":{"id":"ferdi-forever-free","price":0,"billed":0}}}}},"user":"82c1cf9d-ab58-4da2-b55e-aaa41d2142d8"}}

For the record I don't have this issue on:
OS: Ubuntu 18.04 bionic
DE: KDE 5.47.0 / Plasma 5.12.9
Ferdi 5.5.0 x64

Installed via Flatpak


Contact Merge: Better defaulting of master record, show number of contacts in account

In the contact merge UI, the current default is selected based on the last modified contact record. Ideally, the contact whose household has the most members would be defaulted, and the number of household members would be shown in the merge UI.

Also we need more information in the search function besides name: number of household members, number of donations, potentially other fields.

**lurch: add

Tracking W-009673

Maybe we could use search layouts for displaying the contact search results.

I like that. It gives more control to the admin.  As long as we can access that in the metadata API I say go for it

Salesforce has determined that this issue will not be explored further.


cli: add separate 'tilt dump engine' and 'tilt dump logstore'

found this useful when debugging some things. it splits out the logstore from the rest of the engine state, and prints byte[]s as strings instead of as base64 encodings

woooo, I've been wanting this for a while


[Relax][Analysis] Validate global_symbol on non-Relax functions

Prior to this commit, the well-formed checker verified that the "global_symbol" attribute, if present, matches the name of the GlobalVar.  However, this check was only applied for Relax functions.  As a result, discrepencies between the "global_symbol" and the gvar->name_hint could result in unexpected bugs.  (For example, https://github.com/apache/tvm/issues/17176.)
This commit updates the well-formed checker to verify "global_symbol" on all functions in an IRModule.

I expect this PR to fail CI, as https://github.com/apache/tvm/pull/17202 resolves a failure mode that this change is designed to detect.  (Though that isn't necessarily the only case that this check will catch.)


fix(aws-ecs): export instance drain hook

fix #1391
Pull Request Checklist
Please check all boxes, including N/A items:
Testing

[ ] Unit test and/or integration test added
[ ] Toolkit change?: integration tests manually executed (paste output to the PR description)
[ ] Init template change?: coordinated update of integration tests (currently maintained in a private repo).

Documentation

[x] README: README and/or documentation topic updated
[x] jsdocs: All public APIs documented

Title and description

[x] Change type: Title is prefixed with change type:

fix(module): <title> bug fix (patch)
feat(module): <title> feature/capability (minor)
chore(module): <title>  won't appear in changelog
build(module): <title> won't appear in changelog

[x] Title format: Title uses lower case and doesn't end with a period
[x] Breaking change?: Last paragraph of description is: BREAKING CHANGE: <describe exactly what changed and how to achieve similar behavior + link to documentation/gist/issue if more details are required>
[x] References: Indicate issues fixed via: Fixes #xxx or Closes #xxx

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

@rix0rrr @SoManyHs was this intentional?

Yes. It's not clear to me why it should be exported. @cohalz, what problems is this causing for you?

Even if I create your own without using the ECS construct I want to use instance drain hook.

That brings up my next question: what use cases of yours is the rest of the ECS library not satsifying?

Oh I see, spot instances

I don't confirm whether hooks can be used in spot instances, I think that there is no loss by being exported when using ondemand.


Quantum circuits created using a shared register end up on different registers when combined after transpiling

Information

Qiskit Terra version: 0.9.0
Python version: 3.7.4
Operating system: Ubuntu 18.04.3

What is the current behavior?
When you combine two quantum circuits, that were created using the same shared register, they will appear on different registers.
Steps to reproduce the problem
from qiskit import QuantumRegister, QuantumCircuit, ClassicalRegister
from qiskit.compiler import transpile

qr = QuantumRegister(3)
cr = ClassicalRegister(1)
qc1 = QuantumCircuit(qr)

qc1.x(qr[1])
qc1.h(range(3))
qc1.cx(qr[1], qr[2])
qc1.cx(qr[0], qr[1])

qc2 = QuantumCircuit(qr)
qc2.x(qr[1])
qc2.h(range(3))
qc2.cx(qr[1], qr[2])
qc2.cx(qr[0], qr[1])

qc2 = transpile(qc2, coupling_map=[[0, 1], [0, 2], [1, 2]])
qc1 += qc2
qc1.draw(output='mpl').show()

Produces this:

What is the expected behavior?
The two circuits should end up on the same register. This is the behaviour when running the above code on Qiskit 0.11.0.
Suggested solutions
The expected behaviour is restored when removing the coupling map in the above example. This could provide a starting point for debugging.

Hi @bjader , thanks for reporting. Following Qiskit 0.12.0, this is the expected behavior. Terra 0.9 included several bugfixes to standardize the way in which circuits are laid out by the transpiler,  including laying out circuits over a standardized device register.
You should be able to achieve the old behavior by either transpiling with a custom pass manager that excludes layout passes, or by looking at the circuit._layout property on the output circuit which will hold the layout used during transpile. N.B. The location/format of circuit._layout hasn't been finalized, and may move in future releases.

Hi @kdk thank you for the response! It's good to know that this is the expected behaviour now - although I think in this particular case the old behaviour would be more commonly what a user would like to happen.
I'll have a try with the circuit._layout property. Could you give more details on what you mean by "look" at it. Would I modify the property to use the original register?

Try qc1.draw(output='mpl', with_layout=True).show().


Use reusable workflows for release and report status

INTER-196

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

v2.5.1
GitHub release

Your semantic-release bot :package::rocket:


Please update dependencies

I get following npm warning for stylelint 13.6.1:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^10.0.0 but none is installed. You must install peer dependencies yourself.

duplicate of #634


fix(ingest/looker): Fix typo on ViewField creation for measures

Getting errors here, just looks like a typo to me
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@Mohd-gslab - do you know why this wasn't caught by our testing?


Update akka-actor, akka-actor-typed, ... to 2.6.16

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-actor-typed
com.typesafe.akka:akka-serialization-jackson
com.typesafe.akka:akka-slf4j
com.typesafe.akka:akka-stream
com.typesafe.akka:akka-stream-testkit
com.typesafe.akka:akka-testkit

from 2.6.15 to 2.6.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.6.15).
You might want to review and update them manually.
project/EndpointsSettings.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #928.


Babel plugin does not work with Storybook

🐛 Bug Report
I have an error that comes and goes randomly when I use the babel plugin with storybook, the error is:
react.development.js:228 Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.

Check the render method of `InnerLoadable`.
    in InnerLoadable (created by Context.Consumer)
    in Unknown (created by ForwardRef)
    in ForwardRef (created by Route)
    in Route (created by App)
    in Switch (created by App)
    in div (at App.js:101)
    in div (at App.js:88)
    in div (at App.js:87)
    in div (at App.js:86)
    in App (created by Context.Consumer)
    in Connect(App) (created by InnerLoadable)
    in InnerLoadable (created by Context.Consumer)
    in Unknown (created by ForwardRef)
    in ForwardRef (created by Route)
    in Route
    in Switch
    in Provider (at app.js:83)
    in Route (at RouterRedialTrigger.js:82)
    in RouterRedialTrigger (created by Route)
    in Route (created by withRouter(RouterRedialTrigger))
    in withRouter(RouterRedialTrigger) (at app.js:82)
    in Unknown (created by Route)
    in Route (created by withRouter())
    in withRouter() (at app.js:81)
    in ScrollToTop (created by Route)
    in Route (created by withRouter(ScrollToTop))
    in withRouter(ScrollToTop) (at app.js:92)
    in Router (at app.js:91)

The object contains { __esModule: true, default: undefined } when I have the error.
I made some refreshments and the error disappears, to return soon after.
I can counter this problem by using @babel/plugin-syntax-dynamic-import instead.
Run npx envinfo --system --binaries --npmPackages @loadable/component,@loadable/server,@loadable/webpack-plugin,@loadable/babel-plugin --markdown --clipboard
Paste the results here:
## System:
 - OS: Linux 4.4 Ubuntu 16.04.5 LTS (Xenial Xerus)
 - CPU: (4) x64 Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
 - Memory: 234.49 MB / 11.61 GB
 - Container: Yes
 - Shell: 5.1.1 - /bin/zsh
## Binaries:
 - Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
 - Yarn: 1.13.0 - /usr/bin/yarn
 - npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
## npmPackages:
 - @loadable/babel-plugin: ^5.6.0 => 5.6.0
 - @loadable/component: ^5.6.0 => 5.6.0

This is due to something other than Storybook because I also have the problem outside. This is probably due to another babel plugin, I would do more tests to clarify.

The first log comes from here: https://github.com/smooth-code/loadable-components/blob/0d3e7dee3045737be1709ffa300aca083aef457c/packages/component/src/createLoadable.js#L99
In storybook I can not wait for preloading, and the error happens when rendering is done before having the chunks, and it's random.

{ __esModule: true, default: undefined } is the result of loadSync, I realize I have the error only when ctor.isReady returns true and loadSync is used.

If I replace
https://github.com/smooth-code/loadable-components/blob/0d3e7dee3045737be1709ffa300aca083aef457c/packages/component/src/createLoadable.js#L100-L101
with
if (result) {
  this.state.result = result
  this.state.loading = false
}

And
https://github.com/smooth-code/loadable-components/blob/0d3e7dee3045737be1709ffa300aca083aef457c/packages/component/src/resolvers.js#L5-L7
with
if (Component) {
  hoistNonReactStatics(Loadable, Component, {
    preload: true,
  })
}

I can bypass the errors and get a webpack error inside my loadable component, on an import ... from ....

This is a problem with the storybook webpack configuration.

@bertho-zero how did you solve it?

The response is in the referenced issue: https://github.com/storybookjs/storybook/issues/5524#issue-408200164
In your .storybook/webpack.config.js try to add the following line:
defaultConfig.optimization.splitChunks.chunks = 'initial';


The link pointing to the current version of the specs doesn't work.

The link in the specs that is supposed to link to the current version of the specs doesn't actually work.
Therefore, it's not possible to link to the used version of the specs in the fdp-o:conformsToFdpSpec property.

Fixed.
The index.html now only redirects to a page containing the specific version of the FDP specs. We have a page for v1.1 and for the old v1.0.


Add 3d rotations

This adds 3D support to the Rotate transformation, and introduces
RotateX, RotateY, and RotateZ for 3D rotations around the x, y, and z
axes.
PR Checklist

[x] Tests are added
[x] Documentation, if applicable

Thnaks! Could you add to the documentation in doc/src/transforms.md and docs/src/ref.md?

Thanks! Could you add to the documentation in doc/src/transforms.md and docs/src/ref.md?

Hi @CarloLucibello, thanks for taking a look. I just pushed two commits. The first  commit is probably what you were looking for, just adding the documentation to ref.md. In a second commit,  I went much further with a bit of reorganization, but maybe not what you wanted. I can pull this commit out into a separate PR if that makes more sense.

I like the reorganization! still something to do or we can merge?

@CarloLucibello I am all done with this, you can merge.


Set up the development workflow for the project

Make sure code reviews are required, and that we have basic presubmit checks using Travis.

Basic presubmits on github actions runners:
https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions
As far as it seems, you can create files like .github/workflows/action.yml to trigger on commits.

Make sure to set up branch protection or have the CODEOWNERS file protect us from accidentally directly pushing to the repo.

Since we already set the branch protection, do I need to add CODEOWNERS file?

That's a good point, @tengpengli. Let's skip the CODEOWNERS part then!

The CODEOWNERs will automatically assign reviewers, but not sure if it matters since the number of PRs will be small


Scam site on your server

Do you know about this scam site on your server<EMAIL_ADDRESS>It tries to steal the email account password one of my customers.

closing as resolved via blocklist


Discussion for Announcement 195: RC2 => RTM maxLength needs to be added to existing migrations

Discussion for https://github.com/aspnet/Announcements/issues/195

so, what's the suggestion here? I run dotnet ef migrations add but I don't see anything about maxLength. should I re-create the whole database, again?

@Bartmax I really hope not, we are not in a phase where we can simply drop and recreate the DB.

You should just need to edit your existing migrations and add the maxLength specification to columns that need it. No need to drop database or delete migrations.
Any issues would only show up when applying those existing migrations to a new database. The problem is that the absence of the maxLength in the migration would result in varchar(max) in the database, which would then fail when the index is created (since you can't index a varchar(max) column).

@rowanmiller Changing the HasMaxLength value (let's say add one) in the OnModelCreating and add a new migration after upgrading to 1.0.0 should do the trick too, right?

@gdoron you shouldn't need to change anything in your model, this is just about updating the code in existing migrations so that they produce the same schema when they are applied with the RTM runtime. Any new migrations that you scaffold will correctly include the maxLength specification where needed.
You also may not need to do this anywhere. You can always try running the existing migrations against a new database to see if they successfully apply.

ok. To get rid of the error for creating the tables, I only need to update the migration for max length on columns that have indexes.
On the identity config, https://github.com/aspnet/Identity/blob/ed1d8cfbd001676c7b187881934d207577cf8a24/src/Microsoft.AspNetCore.Identity.EntityFrameworkCore/IdentityDbContext.cs
I can see that more properties have a MaxLength specified, but since they don't have indexes it won't throw an error. (but it will create the column with varchar(max) on new database).
So in reality, all columns that had a MaxLength before defined somewhere (like metadata or fluent) must be checked and updated the migration. am I right ?
Is there a safe way to recreate migrations from scratch without affecting database ?
Will this work?:

Change connection string to new database.
Delete migrations/snapshot
Add migration.
Update database.
Revert configuration file to old database.

I prefer to deal with a new correct big migration than to update manually all migration I already have. Sorry, but I have too many tables/migrations already.

Ok I did that and worked. Way better for my scenario. Seeing the new migration file I had 40 maxlength entries. thanks.

@Bartmax Not really.

Add a migration
Update database

You'll probably get an error because the migrations which were already applied to the old DB don't match the new one.
You probably need to change the migration history table.
(Didn't test it since I'm waiting for Azure to support 1.0.0 before migrating to 1.0.0)

@gdoron that's weird, because it does make sense what you said, but it actually worked (?)

@Bartmax maybe because the migration was empty?
Did it had something?

@Bartmax How do you update the DB?
Maybe you run it in a safe script?
IF (EXISTS ...

migration wasn't empty.
I didn't updated the DB. Created a new one and then discarded it.

Did the migration you generated have the same name as the previous one? We match based on names stored in the migration history table to work out whether a migration is already applied or not.

@rowanmiller so that seems to be the easiest solution.

Delete the migrations folder
add a migration.
3.Delete the __EFMigrationsHistory table in the DB
Insert the new migration to __EFMigrationsHistory.

BTW, isn't the ProductVersion in __EFMigrationsHistory there so there'll be backward compatibility?

@gdoron yep that works. You can ignore product version, it's fine for it to be the RC2 or RTM number.
It may be used in the future if we make changes between RTM releases. For example, if we made a change like this one between RTM releases we would compensate for it internally by looking at product versions. Though for this particular change it would be the version number in the migration code-behind rather than the one that applied the migration to the database.

Might be a good idea adding to the announcement this solution as an alternative one.

I confirm that next migration failed miserably with weird (but  expected) errors.
Updating the migrations table by hand did the trick.
So the steps I get to make it working were:

Delete the migrations folder.
Add a new migration
Changes the connection string to another DB (tempDB)
Update database (this creates tempDB)
Revert connection string to initial DB
Update migration history table of initial DB from data of tempDB

One can skip the new db creation (steps 3 to 5) by deleting all entries on migrationHistory table and add an entry that matches the new migration. Being the MigrationId the same as the file created without the cs extension in the Migration folder, and for the version you can keep what you have or update to 1.0.0-rtm-21431
in my case:
MigrationId:<PHONE_NUMBER>4458_InitialMigration
ProductVersion: 1.0.0-rtm-21431

Hope this helps others in a similar situation.

Updated known issue (https://github.com/aspnet/Home/releases/tag/1.0.0#issue141) and announcement (https://github.com/aspnet/Announcements/issues/195) with the recommendation to rescaffold migrations rather than editing them (including detailed steps on how to do it).

Just a small typo: in both documents it should be dotnet ef migration**s** add InitialSchema.

@stephtr thanks, I've fixed it


Text in some languages is not downloading/showing up correctly

Thanks so much for already rolling in the fallback language change!
Not sure what is causing this, but when I download languages (such as Arabic or Catalan) from Localise, many items are translated with garbled content like below:
    <!-- DOWNLOADS -->
    <string name="DOWNLOAD">تحميل</string>
    <string name="DOWNLOAD_RETRY">إعادة محاولة التحميل</string>
    <string name="DOWNLOAD_FAILED_TITLE">�?شل التحميل</string>
    <string name="DOWNLOAD_RETRY_LATER">يرجى محاولة تحميل %s مرة أخرى �?ي وقت أخر</string>

Do you have any idea what is causing these "�?"? Whenever I download straight from the Loco dashboard, it doesn't happen.

I saw this issue appear at a coworker that was using Windows, but haven't had time to investigate yet. Might have something to do with encoding / format (UTF8) or the way we handled it in the library, but couldn't figure it out yet.

According to this Stack Overflow answer, it may be because of the UTF-8 format instead of UTF-16.

Thanks for being patient! Sorry for all the changes and lack of ability to test.

Sorry for the delay; Do you have a string that I could test with?

Of course!
Here's the English string: Copyright %s Kitefaster, LLC.  All rights
reserved.
Correctly exported in Arabic: حقوق النشر %s كايتفاستر ش م م. جميع الحقوق
محفوظة.
Incorrectly exported: حقوق النشر %s كايت�?استر ش م م. جميع الحقوق مح�?وظة.
On Thu, Aug 6, 2020 at 7:59 AM Yannick Pulver<EMAIL_ADDRESS>wrote:

Sorry for the delay; Do you have a string that I could test with?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/appswithlove/loco-android/issues/14#issuecomment-669911101,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG5UEPWXKPZYDRHJVLJNZ4DR7KSLHANCNFSM4PUYVE5Q
.

Thanks a lot. Could you try out version 0.1.6 and see if it fixes that issue for you?

I tested it, and it did not fix the issue. The fallback language is working correctly though :thumbsup:
I've just pushed a pull request, seeing if changing from getBytes() to getText() helps.

Sorry for the delay, I updated it in 0.1.7 that reverts back the encoding as provided by your PR #16

I'm afraid that has just made it worse! I'm not sure what the problem is, and I wish I could debug it better to help. I may just have to stick with the earlier version, and just modify the pieces that aren't quite right.

One thing that did work correctly though was the regional naming of folders, so it may be good to keep that.

Aw snap. Thanks for the quick feedback! I reverted it to the old way in 0.1.8. Need to get my hands on a windows machine to test it properly, or somehow figure out how the encoding must be done to get it right.

Sounds good, thanks for all the help!
On Mon, Sep 21, 2020 at 3:07 PM Yannick Pulver<EMAIL_ADDRESS>wrote:

Aw snap. Thanks for the quick feedback! I reverted it to the old way in
0.1.8. Need to get my hands on a windows machine to test it properly, or
somehow figure out how the encoding must be done to get it right.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/appswithlove/loco-android/issues/14#issuecomment-696344146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG5UEPXXHFCTLLE77753VHLSG6XB5ANCNFSM4PUYVE5Q
.

So I kind of am getting this error on windows with version 0.2.0

@gardyna Could you post the config (except apiKey) you are using as well as the resulting strings.xml file? We didn't introduce any changes to formatting in 0.2.0.

Thanks for providing that info @gardyna.
I'm now pretty sure that it has to do something with the encoding. We expect the strings to come as utf-8 from localise.biz. However, it might be that on Windows they are provided in another format (latin-1) and that the library doesn't expect.
Because latin-1 æ results in utf-8 Ã¦. I think that's the problem.

@gardyna Could you try it again with just published version 0.2.1? (Should be available shortly)
According to Localize.biz - Character Encoding they allow us to add as a Accept-Charset header the specific charset that we are looking for, so I entered utf8. Let's see if that helps 🤞 .

@yannickpulver seems to work pretty well now. couple of emoji that are bungled "💝" became "�?"
but those cases are rare and I can solve those with Unicode literals as well. would not regard that as super high priority

Awesome, I'll give this version a try again now as well!
On Thu, Nov 4, 2021 at 4:21 PM Dagur Arinbjörn Daníelsson <
@.***> wrote:

@yannickpulver https://github.com/yannickpulver seems to work pretty
well now. couple of emoji that are bungled "💝" became "�?"
but those cases are rare and I can solve those with Unicode literals as
well. would not regard that as super high priority
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/appswithlove/loco-android/issues/14#issuecomment-961434467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG5UEPUUDBCB3DCZCV2QESLUKL2MDANCNFSM4PUYVE5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hi @gardyna
I was not able to reproduce the issue with the emoji's on Windows with the latest 0.2.2 version. Here's how I added it to Loco:

And how it looked inside of the Android Studio project on Windows:


Proposal for adding a new method for point clouds

Hi everyone!
I feel like, for those of us working closer to the field of Computer Graphics, it would be cool if this library also implemented the "EdgeConv" operation from this paper:
https://arxiv.org/pdf/1801.07829.pdf

Thanks! Will work on it.

https://github.com/rusty1s/pytorch_geometric/blob/master/torch_geometric/nn/conv/edge_conv.py


Publish 7.6-20220915002311+0000

Publish 7.6-20220915002311+0000

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

@bot-gradle test and merge

OK, I've already triggered a build for you.


"DBT is not installed" - issue that may come up for users who installed dbt using homebrew or in a non-standard location

Hi,
For some reason, my VS Code bar is saying "dbt is not installed" in my terminal due to the dbt power user extension:

But as you can see it is installed:

When I try installing (clicking yes in the first screenshot), I am left with this error as it tries to install dbt:

Any thoughts? If I cannot fix this, I will just end up using Terminal and VSCode in tandem (not ideal).
Thank you!

Thanks. Ran into this problem and homebrew was the culprit. I thought the purpose of using homebrew was so that it won't install dependencies already present on the system. Is that not so?

I ran into this problem today, too, after trying the extension. Thanks for providing this workaround, but unless I'm mistaken this problem will reoccur every time dbt is updated. I'm using dbt-snowflake, but substitute below with your $HOMEBREW_PREFIX (usually /opt/homebrew/ or /usr/local/) and dbt package. This is the example from my system:
/opt/homebrew/Cellar/dbt-snowflake/1.2.0/libexec/bin/python

If you notice there's a 1.2.0 version in the path, so if dbt comes out with dbt 1.2.1 and I update the path changes. The way homebrew works is that everything is installed into the Cellar by package name and then version, and the preferred version (usually the newest, but you can override that on a per package basis) is linked outside the Cellar to be used. So, instead of using the path provided by dbt debug you should instead use the linked version which in my case would be:
/opt/homebrew/opt/dbt-snowflake/libexec/bin/python

Also, I thought I'd point out to people looking here for a solution that the interpreter path can be changed by opening the command palette (⌘ + ⇧ + P) and searching for Python: Select Interpreter. I'm not usually a Python developer and therefore have no experience using it in VSCode, so I had no idea where that was.
@sijain2: That usually is the case, but dbt's homebrew formulae link to specific versions they want to use.

I have a similar issue. I am using windows and installed my dbt with pip install dbt-postgres. I connected my venv to VS Code bit the sign still persists

I still have this problem on ubuntu.
I can not get rid of it.
Uninstalling does not help me at all. Can someone help me pls?

Make sure the version of the VS Code extension is recent enough to match the version of dbt. I recently encountered a cloud development environment that was using an old version of code-server that limited my marketplace extensions; no error was given from the marketplace, just old versions of the extension. Once I updated code-server, I was able to install a recent enough extension that it fixed this problem.

I had success with selecting the interpreter at the workspace level. I have multiple repositories in the workspace, and there's a venv specifically for my DBT project, so I really don't want to do that, but it makes it so Power User can find dbt at least.

Still struggling with this and my devs in 2024, but generally the fix is to:

Create a fresh venv using python3 -m venv ~/.venv.
Once that exists, activate the new venv with source ~/.venv/activate.
Install dbt flavor of your choice with pip install dbt-snowflake.
Switch the Python interpreter - at the workspace level if you're using multiple repos at once - by hitting Cmd+Shift+P and searching Python Interpreter. Set it to the correct path of ~/.venv/bin/python3.12
The final and most important. Uninstall the dbt Power User extension, hit restart extensions, then install dbt Power User again. No matter what you do, it will not detect that the correct package is installed until it's been removed and reinstalled.

The final and most important. Uninstall the dbt Power User extension, hit restart extensions, then install dbt Power User again. No matter what you do, it will not detect that the correct package is installed until it's been removed and reinstalled.

That seems incorrect. Reinstalling the extension doesn't yield any effect. Restarting/reloading vscode should be enough as we cannot detect changes to the environment (dbt being installed through CLI commands).


basic search for event, site, person, work in progress

Adds haystack search for models.

#115 uses simple-minded SQL search, which is probably good enough for now - shall I close this one?


Color Palette selection issues

Running into issues selecting colors, likely due to different screen resolution affecting X,Y coordinates of color buttons. Will look into using pyautogui.locateOnScreen to grab each of the colors manually.

Yes, that is an issue I knew was gonna come up, I just found no good way to locate the colors.
Maybe write a new subroutine to configure the settings and store them in a .json?


Wrong Syntax Highlighting for keywords in OptionMembers

Please include the following with each issue:
1. Describe the bug
If you create OptionMembers with keywords then those values are highlighted as keyword.
2. To Reproduce
Steps to reproduce the behavior:

Create a new Option field

table 50000 "PTE Dummy"
{
    Caption = 'PTE Dummy';
    DataClassification = CustomerContent;

    fields
    {
        field(1; "No."; Text[20])
        {
            Caption = 'No.';
            DataClassification = CustomerContent;
            NotBlank = true;
        }
        field(10; "My Special Type"; Option)
        {
            Caption = 'My Special Type';
            DataClassification = CustomerContent;
            OptionCaption = 'none,internal,protected,CorrectHighlithing';
            OptionMembers = none,internal,protected,CorrectHighlithing;
        }
    }

    keys
    {
        key(Key1; "No.")
        {
        }
    }

}

3. Expected behavior
The keywords shouldn't get this formatting if they are OptionMembers.
4. Actual behavior
Currently they are hightlighted as on other places.
5. Versions:

AL Language: v13.0.903630

Hello, thank you for reporting this issue on syntax highlighting in the AL languge extension. Unfortunately, this is not something that we can resolve well in syntax highlighting. To know whether a word is used in the context of an OptionMembers declaration, that requires just that: Context-awareness. Syntax highlighting lacks such a context, unfortunately, but you can use semantic highlighting in Visual Studio Code to achieve better highlighting awareness.
You can read more about semantic highlight here, but the short solution is to open your VSCode settings and add "editor.semanticHighlighting.enabled": true and enjoy more accurate highlighting.


huggingface_hub.utils._errors.RepositoryNotFoundError: 401 Client Error. (Request ID: Root=1-64d23a76-223c75184c82f38733ae8e33;9906dc7e-c132-423c-99c9-463af43648a8)

Repository Not Found for url: https://huggingface.co/api/models/llama-2-7b-chat.ggmlv3.q8_0.bin/revision/main.
Please make sure you specified the correct repo_id and repo_type.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password.
@AIAnytime Please help me out on this issue

sentence-transformers/all-MiniLM-L6-v2ile "/home/developer/Desktop/Llama2-Medical-Chatbot/vnv/lib/python3.10/site-packages/transformers/utils/hub.py", line 433, in cached_file
raise EnvironmentError(
OSError: private/model is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'
If this is a private repository, make sure to pass a token having permission to this repo with use_auth_token or log in with huggingface-cli login and pass use_auth_token=True.

yes repository Not Found for url: https://huggingface.co/api/models/llama-2-7b-chat.ggmlv3.q8_0.bin/revision/main.
Please make sure you specified the correct repo_id and repo_type.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password. i get also this error

In line 43 of model.py update the model as shown below
model = "TheBloke/Llama-2-7B-Chat-GGML",


Fix delete quota command

This fixes a delete resource quota command:
$ kubectl delete resource quota pods-limit  # current

error: the server doesn't have a resource type "resource"

$ kubectl delete quota pods-limit  # as it should be

resourcequota "pods-limit" deleted

Thanks for fixinhg this!

Thanks for fixing this!


Upgrade k8s.io/apimachinery to v0.19.0-beta.2 to be able to handle big YAML file

WHAT
This pull request upgrades k8s.io/apimachinery to v0.19.0-beta.2 to be able to handle big YAML file.
The stein uses k8s.io/apimachinery/pkg/util/yaml package to decode YAML file, but it has a similar issue to https://github.com/b4b4r07/stein/pull/23.
I found https://github.com/kubernetes/apimachinery/commit/822d4d0151e235ce1caf4e01101f6370d53dc92d to fix the issue.
Since the latest stable version<EMAIL_ADDRESS>doesn't have the change, this pull request uses v0.19.0-beta.2.
This pull request also changes Test_handleYAML_LineTooLong accordingly.
WHY
To fix the following error If YAML is very big (over: bufio.MaxScanTokenSize):
bufio.Scanner: token too long

Thank you for the review! I'm going to merge it and release v0.3.4 💪


Pin workflow runners to ubuntu-22.04

Signed-off-by: Marco Franssen<EMAIL_ADDRESS>

Happy to merge after conflicts are resolved.

Happy to merge after conflicts are resolved.

Done 🚀


🎮 Game Request
SpacePi is a mouse accuracy/agility game revolving around the defense of 13 bases in the most desolate regions of space.
Point down the features
Create lines to defend against enemy lines. Protect your base until it has grown to its target radius. Collect coins to purchase upgrades. Collect powerups to gain benefits.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @S-ishita !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @S-ishita!
We are already having a similar game request in #1037 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

Hey @S-ishita ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[Enhancement] support any_value on complex type

Fixes #issue
Support any_value on array/map/struct
MySQL test> select any_value(v1), any_value(a1), any_value(m1), any_value(s1) from sc3 ;
+---------------+---------------+---------------+---------------------------------------------------------------------------------+
| any_value(v1) | any_value(a1) | any_value(m1) | any_value(s1)                                                                   |
+---------------+---------------+---------------+---------------------------------------------------------------------------------+
| 1             | [1,2,3]       | {1:11,2:21}   | {"s1":1,"s2":[{"a":1,"b":1},{"a":2,"b":1}],"s3":{1:11,2:21},"s4":{"e":1,"f":1}} |
+---------------+---------------+---------------+---------------------------------------------------------------------------------+

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
3
3
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PolymorphicFunctionAnalyzer.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PolymorphicFunctionAnalyzer.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PolymorphicFunctionAnalyzer.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PolymorphicFunctionAnalyzer.java
1
1
100.00%
[]

this is mysql'resuts, does this PR. keep the same?
mysql> select any_value(score) from ss;
+------------------+
| any_value(score) |
+------------------+
|               90 |
|               80 |
|             NULL |
|             NULL |
|             NULL |
|               98 |
|             NULL |
|             NULL |
|               99 |
|               98 |
|               78 |
|             NULL |
|               22 |
|             NULL |
+------------------+
14 rows in set (0.00 sec)

mysql> select any_value(score) from ss where id < 1;
Empty set (0.00 sec)

mysql> select any_value(score) from ss group by id;
+------------------+
| any_value(score) |
+------------------+
|               90 |
|             NULL |
|             NULL |
|             NULL |
|             NULL |
|               98 |
|             NULL |
+------------------+
7 rows in set (0.00 sec)

The purpose isn't compatible with mysql, just supported work on complex type, and looks is  different on select any_value(score) from ss, sr's any_value is aggregate function

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
3
3
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/FunctionSet.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PolymorphicFunctionAnalyzer.java
1
1
100.00%
[]

@Mergifyio backport branch-3.1


Warp client Linux download links don't work

Example URL(s)
https://pkg.cloudflareclient.com/
Actual Behavior
Connection timeout while trying to connect to the linux app download website.
Expected Behavior
It should be available at https://pkg.cloudflareclient.com/
Additional information
No response

Howdy, this isn't exactly something our team can help with (since we're a docs repo)... but I'll forward along internally.


[Bug] Wildcard removing commas

Commas at the start or end of an option in a wildcard get removed.
Template example: test {, one|, two}, test, {three, |four, }, test, {five,|six,} test
Generates: test one, test, four, test, five test
Instead of: test, one, test, four, test, five, test
I think this is a recent bug.
I'm using commit 7fea2229 (v.2.17.1)

Checking if this has been fixed with 0645c944d379c52e9f97bff7d24096f82165c59c...

Sorry, did't see that it was already in #106


[FEATURE] Allow caller to set custom HTTP Accept header value in the Invoke-PnPSPRestMethod cmdlet

These two calls fail:
Invoke-PnPSPRestMethod -Method GET -Url "https://contoso-admin.sharepoint.com/_api/v2.0/sites/4B6B5FC7-4313-4DA3-BAF5-00A11ED30800" -Raw

Invoke-RestMethod -Method  GET  -Uri "https://contoso-admin.sharepoint.com/_api/v2.0/sites/4B6B5FC7-4313-4DA3-BAF5-00A11ED30800" -Headers @{ accept = "application/json; odata=nometadata"; Authorization = "Bearer eyJ0....." }

This call command works:
Invoke-RestMethod -Method  GET  -Uri "https://contoso-admin.sharepoint.com/_api/v2.0/sites/4B6B5FC7-4313-4DA3-BAF5-0A11ED30800" -Headers @{ accept = "application/json"; Authorization = "Bearer eyJ0....." }

The difference between the is the value for the accept header.  PnPSPRestMethod includes the odata=nometadata, which causes several SharePoint Online REST API endpoint to fail with:
Invoke-PnPSPRestMethod : {"error":{"code":"invalidRequest","message":"Invalid request"}}
Allowing the caller to override the default headers would allow devs to use the _api/v2.0 and $batch endpoints with Invoke-PnPSPRestMethod.
Reference: https://github.com/pnp/powershell/blob/dev/src/Commands/Base/InvokeSPRestMethod.cs#L55

Hi @joerodgers , have added an additional parameter Accept to allow you to specify custom values there.
It will be available from tomorrow's nightly and later builds :)

Is there any way to include custom headers in Invoke-PnPSPRestMethod? I am trying to add the below header to check a workaround.
SPHome-ClientType: SharePointIOS

Faced same issue today. Not having access to the headers is blocking. In my case I wanted to update a list item (Set-PNPListItem isn't working for an unknown reason).
Calling manually the update endpoint requires to pass If-Match:* in the headers.
The only workaround I found was to move from
            $updateListItemApiUrl = "/_api/web/lists/getbyId(guid'$($list.Id)')/items($($item.Id))"
            $body = @{
                'Title'  = $label
            }
            Invoke-PnPSPRestMethod -Method PATCH `
                 -Url $updateListItemApiUrl `
                 -Content $body `
                 -ContentType "application/json;odata=nometadata" `
                 -Accept "application/json;odata=nometadata" `

to
            $updateListItemApiUrl = "/_api/web/lists/getbyId(guid'$($list.Id)')/items($($item.Id))"
            $body = @{
                'Title'  = $label
            }
            $token = Get-PnPAccessToken -ResourceTypeName SharePoint
            $web = Get-PnPWeb
            Invoke-RestMethod -Method PATCH `
                -Uri ($web.Url + $updateListItemApiUrl) `
                -ContentType "application/json;odata=nometadata" `
                -Body ($body | ConvertTo-Json -Depth 100) `
                -Headers @{
                "Authorization" = "Bearer $($token)"
                "Accept"        = "application/json;odata=nometadata"
                "Content-Type"  = "application/json;odata=nometadata"
                "If-Match"      = "*"
            }


Cannot build node-se

While building node-se I've got this error:
  Compiling ton_abi v1.0.0 (https://github.com/tonlabs/ton-labs-abi.git#e8527154)
error[E0599]: no method named `prepend_reference_cell` found for struct `BuilderData` in the current scope
   --> /home/runner/.cargo/git/checkouts/ton-labs-abi-444eec65f3f6eb9d/e852715/src/function.rs:361:25
    |
361 |                 builder.prepend_reference_cell(BuilderData::with_raw(signature, len).unwrap().into_cell().unwrap());
    |                         ^^^^^^^^^^^^^^^^^^^^^^ help: there is an associated function with a similar name: `append_reference_cell`

error[E0599]: no method named `prepend_reference_cell` found for struct `BuilderData` in the current scope
   --> /home/runner/.cargo/git/checkouts/ton-labs-abi-444eec65f3f6eb9d/e852715/src/function.rs:363:25
    |
363 |                 builder.prepend_reference_cell(Cell::default());
    |                         ^^^^^^^^^^^^^^^^^^^^^^ help: there is an associated function with a similar name: `append_reference_cell`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0599`.
error: could not compile `ton_abi`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Process completed with exit code 101.

This issue has been fixed.


Unable to run Pi example with default permissions in Helm chart

I'm attempting to use the operator on a k3s cluster. I made a custom image based on amd64 but otherwise didn't change anything. I installed with:
helm install bc-release spark-operator/spark-operator --namespace spark-operator --create-namespace --set image.repository=<IP_ADDRESS>:5000/spark-operator --set image.tag=latest --set uiService.enable=false

When I run spark-py-pi.yaml with namespace: spark-operator and serviceAccount: bc-release-spark, my driver log contains entries like:
+ exec /usr/bin/tini -s -- /usr/bin/spark-operator driver --properties-file /opt/spark/conf/spark.properties --class org.apache.spark.deploy.PythonRunner local:///opt/spark/examples/src/main/python/pi.py
W0828 21:52:37.937420      10 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: failed to list *v1beta2.ScheduledSparkApplication: scheduledsparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:spark-operator:bc-release-spark" cannot list resource "scheduledsparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
E0828 21:52:37.937472      10 reflector.go:140] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: Failed to watch *v1beta2.ScheduledSparkApplication: failed to list *v1beta2.ScheduledSparkApplication: scheduledsparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:spark-operator:bc-release-spark" cannot list resource "scheduledsparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
...

Is there some additional configuration needed aside from what the Helm chart is doing? Thanks for any pointers.

@barrettc I think namespace parameter of  spark-pi.yaml should be equivalent to --set sparkJobNamespace=default parameter of helm install. Hope that solves your problem.

@oguzhangur96 Thanks for the reply. I tried this out adding the --set sparkJobNamespace=default option to my helm install command like you noted. I'm seeing this in my logs:
+ exec /usr/bin/tini -s -- /usr/bin/spark-operator driver --properties-file /opt/spark/conf/spark.properties --class org.apache.spark.examples.SparkPi local:///opt/spark/examples/jars/spark-examples_2.12-3.2.3.jar
W0919 14:42:46.795783       9 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: failed to list *v1beta2.ScheduledSparkApplication: scheduledsparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:default:bc-release-spark" cannot list resource "scheduledsparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
E0919 14:42:46.795838       9 reflector.go:140] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: Failed to watch *v1beta2.ScheduledSparkApplication: failed to list *v1beta2.ScheduledSparkApplication: scheduledsparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:default:bc-release-spark" cannot list resource "scheduledsparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
W0919 14:42:46.795846       9 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: failed to list *v1beta2.SparkApplication: sparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:default:bc-release-spark" cannot list resource "sparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
E0919 14:42:46.795858       9 reflector.go:140] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: Failed to watch *v1beta2.SparkApplication: failed to list *v1beta2.SparkApplication: sparkapplications.sparkoperator.k8s.io is forbidden: User "system:serviceaccount:default:bc-release-spark" cannot list resource "sparkapplications" in API group "sparkoperator.k8s.io" at the cluster scope
W0919 14:42:46.795870       9 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: failed to list *v1.Pod: pods is forbidden: User "system:serviceaccount:default:bc-release-spark" cannot list resource "pods" in API group "" at the cluster scope

For reference, here's the spark-pi.yaml I used:
apiVersion: "sparkoperator.k8s.io/v1beta2"
kind: SparkApplication
metadata:
  name: spark-pi
  namespace: default
spec:
  type: Scala
  mode: cluster
  image: "<IP_ADDRESS>:5000/spark-operator:latest"
  imagePullPolicy: Always
  mainClass: org.apache.spark.examples.SparkPi
  mainApplicationFile: "local:///opt/spark/examples/jars/spark-examples_2.12-3.2.3.jar"
  sparkVersion: "3.2.3"
  restartPolicy:
    type: Never
  volumes:
    - name: "test-volume"
      hostPath:
        path: "/tmp"
        type: Directory
  driver:
    cores: 1
    coreLimit: "1200m"
    memory: "1024m"
    labels:
      version: 3.2.3
    serviceAccount: bc-release-spark
    volumeMounts:
      - name: "test-volume"
        mountPath: "/tmp"
  executor:
    cores: 1
    instances: 1
    memory: "1024m"
    serviceAccount: bc-release-spark
    labels:
      version: 3.2.3
    volumeMounts:
      - name: "test-volume"
        mountPath: "/tmp"

Do you see anything obviously wrong? Thanks for any help

I was getting this type of error if the cluster role binding was not enabled. Maybe this was your problem too @barrettc.


  If the given version isn't installed, return an error and suggest use of the --install flag.

This should be done using click.  A good opportunity to learn it.


Merge branch 'dev' into master

Blocked by: https://nuget.visualstudio.com/NuGetMicrosoft/_git/NuGetDeployment/pullrequest/910?_a=files
Build: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=2690642