[stdlib] NFC: Restore doc comment for Unsafe[Mutable]BufferPointer

Moves a // comment up above a /// documentation comment, since the latter needs to be attached directly to the declaration or it won't be picked up as documentation.

@swift-ci please smoke test

I’m fine with that approach too, Ben. My goal here is just to bring the documentation back; hopefully someone more familiar with the status of the FIXME can comment on whether it’s best to move or remove the comment.

@swift-ci please smoke test and merge

macOS smoke test failed on a lipo call; will try again later.

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@glessard Made one in #63362; let me know if anything looks off about the structure/reviewers, etc. Haven't done the release cherry-pick thing before.

Looks okay. Restating the purpose wouldn't be amiss, especially since the original description for this one has become out of date.


Cannot verify JWT at all??

Hi everyone,
we are evaluating Auth0 for our service and have problems to get going.
We can verify the token we get on jwt.io as you can see here:

However in the console I get the following:

I copied the values from the console into the webpage. So I am pretty confident that they are actually the same.
What can be the problem? Should I reinstall Ruby after my upgrade to macOS Sierra?

Can you please provide your Ruby version and jwt version you are using?
After my upgrade to macOS Sierra I had to re-install all my brew installs including rbenv.

Sure!
Ruby 2.3.1
JWT 1.5.6
Yeah, thought that OpenSSL might be messed up now or something. What was the problem you were having?

Yey, I got it to work like this:
JWT.decode(token, JWT.base64url_decode(secret), true)

Was trying it before with Base64.decode64 but this did not work.
Happy it works with the provided function :)

Ah, ok. The password was the issue.
The password isn't base64 encoded when creating a token with this gem. It needs to be plain text.

This is actually a problem with Auth0's quickstart documentation. Hope they update it soon :)


moving to yarn and prop-types

https://github.com/mWater/mwater-portal/issues/991

Dont merge this one yet

Now this can be merged


kapacitor: 1.7.0 -> 1.7.5

Description of changes
ZHF: https://github.com/NixOS/nixpkgs/issues/352882
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build kapacitor

@ofborg build kapacitor

@ofborg build kapacitor

@Scrumplex @ocfox Done.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 344895

x86_64-linux

:white_check_mark: 1 package built:

kapacitor


Update Python versions

Python 2.6, 3.2 and 3.3 are EOL and no longer receiving security updates.
They're also little used if at all.
Here's the pip installs for ConfigArgParse from PyPI for last month:

python_version
percent
download_count

2.7
88.83%
150,131

3.4
5.78%
9,762

3.6
3.08%
5,203

3.5
2.00%
3,379

2.6
0.25%
417

3.7
0.04%
63

None
0.03%
44

3.3
0.01%
18

Source: pypinfo --start-date -46 --end-date -19 --percent --pip --markdown ConfigArgParse pyversion
This removes those, and updates the code to use more modern Python features. It also adds Python 3.6.

I am currently evaluating the use of ConfigArgParse for the gcovr tool. If this PR is merged and ConfigArgParse drops support for Python 2.6, I will have to find a different way to deal with config files.
I understand the desire to move to modern Python. However, some operating systems (CentOS 6) are still stuck on Python 2.6. CentOS 6 will be EOL'ed after Nov 2020. I have no desire to break hundreds of downstream users unless continuing to support 2.6 would require excessive effort.
This PR doesn't seem to provide any substantial value that would be impossible with continued support for Python 2.6. I would therefore suggest that the PR is not merged in its current form – although some of the small fixes and enhancements are nice and can be rebased/cherry-picked independently.

I wouldn't say CentOS 6 is stuck on Python 2.6, I understand upgrading Python is officially supported by CentOS via the Software Collections Repository.

Enter Software Collections, also known as SCLs. As an example, SCLs allow you to run the default python that comes with CentOS (so yum and other system tools in CentOS work), while also allowing a newer version of python to be installed alongside the default python for use creating and running software with newer requirements.

https://wiki.centos.org/AdditionalResources/Repositories/SCL
And if upgrading from an old Python is unsuitable, pinning to an old release of this library is easily doable, as is already needed with other libraries for a 5-years-insecure 2.6.
Some Python libraries are already planning how to drop Python 2.7, which will be EOL on 2020-01-01.
See also:

Unsupported since 2013-10-29
https://snarky.ca/stop-using-python-2-6/
http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html
http://www.python3statement.org
Current pip 9 deprecates Python 2.6 support, pip 10 won't support it (https://github.com/pypa/pip/issues/3955)
Wheel no longer supports Python 2.6 https://github.com/pypa/wheel/commit/c9e54864b64ad5c949bfb6ce8cdfd77df03647ef
Not much PyPI traffic (June 2016) https://github.com/pypa/pip/issues/3796

Updated to add python_requires to help pip, and upgrade Python syntax using https://github.com/asottile/pyupgrade.

Rebased on master, removed the now-redundant sudo keyword from .travis.yml, and updated Python syntax with pyupgrade.

I'm ok to merge that. @bw2 ?

Here's the pip installs for ConfigArgParse from PyPI for May 2019:

category
percent
downloads

2.7
79.05%
778,985

3.4
11.50%
113,298

3.6
4.98%
49,039

3.7
2.65%
26,161

3.5
1.58%
15,563

null
0.16%
1,590

3.8
0.05%
498

2.6
0.02%
225

3.3
0.00%
20

3.2
0.00%
2

Total

985,381

Source: pypistats python_minor ConfigArgParse --last-month # pip install pypistats


housekeeping: compile csproj with multiple target frameworks in parallel

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀
What is the current behavior? (You can also link to an open issue here)

@ghuntley,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Coverage remained the same at 69.589% when pulling 21661d6d03ccc333937e35cb7ebef45802e2b668 on faster-builds into 23c9ba9c8667bf752903c6cd3a23144c0717c8d6 on develop.


Integration with Sonar (proper pull request)

I messed pull request https://github.com/futurice/mocha-jenkins-reporter/pull/17 so I had to create new one. Added some documentation and changed the way of replacing .js file extension.

I'll merge this first and make a release, thank you.

Thank you as well :)

Please make sure version 0.1.5 works for you.

I've just tested it in my project, works great. Thank you both :)


Update middleware for consistency with new-style django middleware

Currently broken on django 1.11 because of changes to middleware.  This change should allow middleware to work pre/post 1.11

Thank you.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 763 ms

Resolved: Bofrost.de performance has improved in dab981d.


feat(base-cluster/nginx): add possibility to disable ingress

Add ability to disable ingress.

You're missing the if in

[ ] https://github.com/teutonet/teutonet-helm-charts/blob/93b4747ddef340470c27162347971515afb9ab59/charts/base-cluster/templates/global/cluster-ingress.yaml#L1-L0

the namespace ingress-nginx should not be created if ingress is disabled

Added :+1:

I've now disabled the dashboards and disabled the cluster issuer if the ingress is disabled.


Clean up of the platform section

This cleans up the platform section into its own subdirectory.
I am not all that happy about how "see-also" works, but maybe that
is how it is meant to work, or alternatively I'm doing it wrong :)

@andraxylia - followup on your PR for a platform dir.  Renders well enough on my system.

@geeknoid thanks _index.md is in my local repo but forgot to commit it.  will take the platform setup out of each title.

@sdake thanks for making this work. I added two comments, please address before I can approve. Also, you need to fix some links, you have lint errors in circleci.

@andraxylia aware of the lint errors.
Cheers
-steve

@andraxylia the reason the link wasn't working was because of the uncommitted _index.md.  I think the link adds value to the site, as it permits people to go directly to the platform section and also is more consistent with the rendering of step 1 (download Istio).

It looks much better now with the _index.md in platform-setup, the menu on the left also got re-organized.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: andraxylia, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [sdake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: andraxylia, sdake
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [sdake]
content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Just some a few grammar fixes please...

Would it make sense to move "Platform Setup" at the top of the menu in the left-hand nav? Just set the weight of docs/setup/kubernetes/platform-setup/_index.md to a smaller value to make this happen.

@geeknoid - will address grammar problems shortly.
Cheers
-steve

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: andraxylia, sdake
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Close: Openshift -> OpenShift


Lack of consistency in parameter generation

Expected behavior
The type of parameter generated should be consistent
Actual behavior
The type of parameter generated should be consistent
Steps to reproduce

Create a spec file

Something
=========

sfsdfsdf
--------

* This is showing as implemente"b"d

use create a step implementation.
The generated parameter type is Object
Now use shift f6 and refactor the step to This is "showing" as implemente"b"d
The newly generated parameter is of type String

Gauge version
Gauge version: 0.4.1.nightly-2016-04-19

Plugins
-------
html-report (2.1.0)
java (0.3.4.nightly-2016-04-19)

Not a Gauge issue. Which IDE is this happening?

This happens on IntelliJ

This issue was moved to getgauge/Intellij-Plugin#227


PARQUET-1523: [C++] Vectorize Comparator interface, remove virtual calls on inner loop. Refactor Statistics to not require PARQUET_EXTERN_TEMPLATE

This patch supersedes https://github.com/apache/arrow/pull/3752
I took the liberty of consolidating the comparator code with the statistics code since the two things are effectively inseparable. I also renamed the statistics classes for clarity, since "Statistics" is clearer than "RowGroupStatistics" -- the "scope" of the statistics need not be limited to a row group.
I apologize for the size of the diff; it is largely the result of moving code around and shuffling code from header files into parquet/statistics.cc

I wanted to get this up for feedback in case I did something deeply offensive -- I will add doxygen comments to the header files before merging this.
I also need to run the benchmarks to see if there is impact (this should be faster, but I'm not sure how much the benchmarks exercise the stats on the write path)

I'll fix the CI issues tomorrow.
Write performance benchmarks
before
--------------------------------------------------------------------------------------------------------------
Benchmark                                                                       Time           CPU Iterations
--------------------------------------------------------------------------------------------------------------
BM_WriteInt64Column<Repetition::REQUIRED>/1048576                         6112498 ns    6112346 ns        117   327.207MB/s
BM_WriteInt64Column<Repetition::OPTIONAL>/1048576                         8175286 ns    8175149 ns         86   244.644MB/s
BM_WriteInt64Column<Repetition::REPEATED>/1048576                        11043673 ns   11043294 ns         64   181.105MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::SNAPPY>/1048576    6491432 ns    6491125 ns        107   308.113MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::SNAPPY>/1048576    8357793 ns    8357599 ns         84   239.303MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::SNAPPY>/1048576   11278808 ns   11278491 ns         63   177.329MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::LZ4>/1048576       6614531 ns    6614423 ns        105    302.37MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::LZ4>/1048576       8529249 ns    8528994 ns         81   234.494MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::LZ4>/1048576      11289507 ns   11289159 ns         62   177.161MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::ZSTD>/1048576      6566587 ns    6565922 ns        106   304.603MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::ZSTD>/1048576      8647931 ns    8647881 ns         81   231.271MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::ZSTD>/1048576     11137814 ns   11137516 ns         62   179.573MB/s

after
--------------------------------------------------------------------------------------------------------------
Benchmark                                                                       Time           CPU Iterations
--------------------------------------------------------------------------------------------------------------
BM_WriteInt64Column<Repetition::REQUIRED>/1048576                         4245946 ns    4245849 ns        166   471.048MB/s
BM_WriteInt64Column<Repetition::OPTIONAL>/1048576                         6416929 ns    6416840 ns        108    311.68MB/s
BM_WriteInt64Column<Repetition::REPEATED>/1048576                         9377082 ns    9376758 ns         75   213.293MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::SNAPPY>/1048576    4551200 ns    4551132 ns        156   439.451MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::SNAPPY>/1048576    6406567 ns    6406357 ns        109    312.19MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::SNAPPY>/1048576    9436338 ns    9436170 ns         74    211.95MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::LZ4>/1048576       4488158 ns    4487987 ns        158   445.634MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::LZ4>/1048576       6364199 ns    6364079 ns        109   314.264MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::LZ4>/1048576       9488606 ns    9488350 ns         75   210.785MB/s
BM_WriteInt64Column<Repetition::REQUIRED, Compression::ZSTD>/1048576      4764453 ns    4764293 ns        149   419.789MB/s
BM_WriteInt64Column<Repetition::OPTIONAL, Compression::ZSTD>/1048576      6514745 ns    6514404 ns        110   307.012MB/s
BM_WriteInt64Column<Repetition::REPEATED, Compression::ZSTD>/1048576      9441827 ns    9441712 ns         76   211.826MB/s

So anywhere from 10-40% faster with the vectorized stats

@pitrou @lidavidm I fixed some (valid) clang warnings that aren't caught in our CI for some reason -- I guess we don't build Flight with clang yet

This patch is ready to go I think, I'm just addressing the last CI issues

Merging now


Inherit container policy when doing a switch

I noticed that doing a bootc switch from a signed image results in switching to an unsigned image unless you explicitly pass --enforce-container-sigpolicy
Reproducible Example:

Given a status of ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:40
bootc switch ghcr.io/ublue-os/bluefin:39
Do a status and it's ostree-unverified-registry:ghcr.io/ublue-os/bluefin:39

Passing the enforce flag works as expected. The use case is that when doing testing it's common to switch a bunch. I was digging for a regression and switching between daily builds in multiple VMs, and by the time I was done all my images were unsigned.
Not sure on what the UX should look like as I would guess there are other enterprise policy features that would need to be accounted for. But it would be nice if the signing was transparent unless there was an error, so I figured if you're on a signed image you'd want to stay on a signed image.

This is all a bit confusing, ostree-unverified-registry doesn't mean that signatures are disabled. It just means that we didn't enforce that /etc/containers/policy.json didn't have a default fallback to insecureAcceptAnything.
There's a whole "observability problem" with the image signature bits here that we should definitely highlight in status in the case where we did verify a signature.
Another way to say this is I'm trying to deprecate the special ostree-container signature verification; bootc should behave the same as podman. IOW if we have something like bootc switch --enforce-signature or so, then podman pull --enforce-signature should exist too.
But basically I believe we were still enforcing signatures while you were switching assuming that you've configured /etc/containers/policy.json - does that make sense?

ostree-unverified-registry doesn't mean that signatures are disabled

Hah, yes of course, this makes total sense.
Gotten so used to it being "the one where the user didn't bother to set up signing" that it ended up just turning into "disabled" in my brain. Thanks! 😄

Reopening after a quick discussion at kubecon.
Here's the UX problem we're trying to solve: Switching between streams. Scroll down a bit to he manual examples.
Typing the long sigpolicy flag gets old quickly when doing development. But if you don't use that flag the switch rebases to the target but is unsigned. We'd like for it to just only switch between signed images so we don't need to deal with the long flag.
Colin seems surprised by this and thought maybe there was an issue here, so reopening.


Lock LevelSprite diagonal ratio on resize

When resizing a Sprite using the HandlePoints in the corner, the ratio should be locked (just like Word image resize for example)

Done in commits :
https://github.com/Sygmei/ObEngine/commit/4ccdbe05dfc5ca9715101ab2ca46f4582931a62e
and
https://github.com/Sygmei/ObEngine/commit/afd4ab3a88bb54c6e1befdec3a443bfe5265767e


Fixed names and aliases in autocomplete

Converted autocomplete ES query to use a dismax query so that it will query against multiple fields with different weights
Added a boosting strategy that favors exact symbols and aliases first, followed by (whitespace split) starts-with matching on symbol, aliases and names.
Fixed some bad matching because the starts-with tokenizer was running at both index and query time, returning false positives if they started with the same substring
(plus a little bit of drive-by automated tab to space reformatting)
Fixes #151

Wow, nice work Kevin, this is awesome.

Any thoughts on the conflict resolution?

Whoops, I'll merge development in and get rid of the conflict

Ok, merged and conflict free!

Looks good to go IMO. Perhaps lets merge in the morning in case anyone else wants to review it?


How to get HTML content of the text?

Is there a way to return the content of textproperty with all the html stuff?
Thanks

That's essentially the first question that came to mind for me, too.
@ageitgey mentions that this package might be useful to build an Instapaper clone; however, tools like Instapaper or Pocket retain the text formatting from the body of the article (headings, subheadings, italic, bold, links [sometimes transformed into footnotes], etc.).

Thanks for replying @ageitgey.
Any chance you could point me in the right direction if I wanted to take that upon myself?


express.json() breaks AsyncLocalStorage in node 14

If express.json() is added between middleware which sets asyncLocalStorage and code which retrieves it, the storage goes missing on requests with a body, e.g. POST requests.
Works
import {AsyncLocalStorage} from 'async_hooks';
import {json} from 'express';

const asyncLocalStorage = new AsyncLocalStorage();
const setContext = (req,res,next) => ayncLocalStorage.run('foo', next);

// ...
app.use(
  json(),
  setContext,
  (req, res, next) => {
    asyncLocalStorage.getStore(); // foo
  });

Fails
// ...
app.use(
  setContext,
  json(),
  (req, res, next) => {
    asyncLocalStorage.getStore(); // undefined <<<===
  });

This is because ayncLocalStorage.run('foo', next); only works when your following middleware are sync, which body parsing is not, as it needs to wait for the body to arrive before continuing.
https://nodejs.org/dist/latest-v14.x/docs/api/async_hooks.html#async_hooks_asynclocalstorage_run_store_callback_args

This methods runs a function synchronously within a context and return its return value. The store is not accessible outside of the callback function or the asynchronous operations created within the callback.

Thanks guys. This is really helpful. Provides a clear and simiple way to handle other async middleware, as well.

I recall fastify to have a simmilar body-related issue that got fixed by using AsyncResource, https://github.com/fastify/fastify-request-context/pull/12 should help here :)

Is the TL;DR here that we need to use enterWith for Async Local Storage when using express? 🤔

Has anything changed in nodejs or express? The following example works as expected:
const { AsyncLocalStorage } = require('async_hooks');
const express = require('express');

const asyncLocalStorage = new AsyncLocalStorage();
const app = express();

function storageMiddleware() {
  return (req, res, next) => {
    asyncLocalStorage.run('Hello World', next);
  };
}

app.use(
  storageMiddleware(),
  express.json(),
  (req, res) => {
    res.send(asyncLocalStorage.getStore() ?? 'Missing');
  }
);

app.listen(3000, () => {
  console.log('Server is running on http://localhost:3000');
});

@remen this issue is from 2020 and then Express added async local support in 2022 so it has worked since then (4.18.0 or higher).


Voice Channel Invite posted along with the LFG message

It would be a really cool feature if the bot would post a voice channel invite alongside the LFG message if the person looking for the group is currently in a voice channel and requests for the VC to be posted aswell.

Hello @ChrisCartagena
Thank you for the idea.
My current concern with your idea is that person looking for a group may create an lfg call for a future/uncertain time period (which is 90% of the bot usage I've known), in which case posting an invite link would be pointless or in some cases even cause some issues when people will join VC when they were not expected at that moment.
We may discuss this idea a bit further and might come to an agreement with a bit more specifics/limitations.
Just like a temporary solution - create an invite link to the desired VC and just put it in the description.

Closed due to inactivity.
Consider reopening this ticket in case you want to resume the conversation


Fix various typos in notebooks

Found using codespell -wi3 and some manual editing.

@Calinou  thanks for making all these edits! When you're using codespell, do you know if it's possible to skip those large "image/png" inside the .ipynb notebooks?

@GokuMohandas I'm not sure about this, sorry :slightly_frowning_face:


Add docs for code-level warning suppression

https://github.com/jenkins-infra/jenkins-codeql/issues/4
Related: https://github.com/jenkins-infra/jenkins-security-scan/pull/13

Not sure this is a great location for this documentation.
Given how findings from https://github.com/jenkins-infra/jenkins-security-scan are presented in affected repositories, nobody is looking at the top-level documentation of this repo unless they're diving into internals. For easy access, this repo already has a ton of duplication in finding-specific Markdown files, compare e.g. https://github.com/jenkins-infra/jenkins-codeql/blob/main/src/UnsafeCalls.md and https://github.com/jenkins-infra/jenkins-codeql/blob/main/src/BadRoleCheck.md and instructions for suppression should be integrated there (item 2 of Next Steps), for example: https://github.com/daniel-beck/jenkins-codeql/commit/7574dde3b4c281ebdd9668513b8b296863dbae7d

What else works:
// lgtm[jenkins/no-permission-check]
// codeql[jenkins/no-permission-check]
// lgtm
// LGTM!
// lgtm[jenkins/csrf], lgtm[jenkins/no-permission-check] suppresses multiple rules
@SuppressWarnings({"codeql[jenkins/csrf]", "codeql[jenkins/no-permission-check]"})
@SuppressWarnings({"lgtm[jenkins/no-permission-check] yes permission check","lgtm[jenkins/csrf]"})

What doesn't work:
// codeql
// lgtm[]
// codeql[]
@SuppressWarnings("lgtm")
@SuppressWarnings("codeql")
@SuppressWarnings("lgtm[]")
@SuppressWarnings("codeql[]")
// lgtm[jenkins/no-permission-check, jenkins/csrf]
// codeql[jenkins/no-permission-check, jenkins/csrf]

These are the ones I've tested. There's probably more, but I think with these we have more than enough ways to suppress.

FYI It's a bit counter intuitive for the comment approach when it's about a method. You have to place the comment at the end of the signature line, not before, not after the method. It seems that was corrected in more recent versions of java-queries.
:x: The current version of the "next steps" seems wrong to me.
Using https://github.com/Wadeck/sample-repo-plugin/blob/with-codeql-warning-comment/src/main/java/io/jenkins/plugins/samplerepo/SampleBuildStep.java for the testing ;)

Full report after suppressed removal


FEAT: Add option to execute download notebooks

It would be nice to have the option to pre-execute the download collection of notebooks that are generated by the downloadnb option.
@AakashGfude this should be pretty simple to add? The julia team would like this feature.
Lets use:
jupyter_download_nb_execute = True

with a default value of False

@AakashGfude the Julia team would like this to be able to populate their live environments with pre-executed notebooks. It is best to use the download collection as they contain URL referenced images.

This has been merged.


Change image dimensions for next-song album art

gsx default is 40x40px, my skin is using 50px but i plan to make it 120px like the now-playing song.
example:

40px http://images.gs-cdn.net/static/albums/40_3382191.jpg
120px http://images.gs-cdn.net/static/albums/120_3382191.jpg

You want me to increase the size or just use the '120_' as source ?

120_ source.


Updating worker environment does not work in 1.3.4 and greater

I have a worker environment which I cannot update with versions 1.3.4, 1.3.5, and 1.4.0. The specific issue is that the plugin fails to find the environment. The environment is present and the status is Green.
I tried in version 1.3.3 and I am able to update.

oops. can you send me in private your pom so I could look into it?
Sent from my Windows Phone
-----Original Message-----
From: "David Venable"<EMAIL_ADDRESS>Sent: 2/28/2015 5:07 PM
To: "ingenieux/beanstalker"<EMAIL_ADDRESS>Subject: [beanstalker] Updating worker environment does not work in 1.3.4 andgreater (#58)
I have a worker environment which I cannot update with versions 1.3.4, 1.3.5, and 1.4.0. The specific issue is that the plugin fails to find the environment. The environment is present and the status is Green.
I tried in version 1.3.3 and I am able to update.
—
Reply to this email directly or view it on GitHub.

Our POM is fairly complicated because it uses a parent-child hierarchy. I'll see if I can break down the properties for you.
One important thing to note - running the beanstalk:wait-for-environment Maven goal succeeds just fine in version 1.3.5. There must be something different in how the two wait commands are setup.

mvn help:effective-pom
--
-- Aldrin Leal<EMAIL_ADDRESS>Master your EC2-fu! Get the latest ekaterminal public beta
http://www.ingenieux.com.br/products/ekaterminal/
On Sat, Feb 28, 2015 at 8:19 PM, David Venable<EMAIL_ADDRESS>wrote:

Our POM is fairly complicated because it uses a parent-child hierarchy.
I'll see if I can break down the properties for you.
One important thing to note - running the beanstalk:wait-for-environment
Maven goal succeeds just fine in version 1.3.5. There must be something
different in how the two wait commands are setup.
—
Reply to this email directly or view it on GitHub
https://github.com/ingenieux/beanstalker/issues/58#issuecomment-76562488
.

Hello @aldrinleal, I sent you an email at the email address listed in your Git commits for this project.

hello @aldrinleal, I have the same issue and not sure if I put a proper configuration in POM. Could you, please, refer to working example or some docs describing configuration for the Worker tier.
thanks in advance!

mkalinin has also submitted a PR: https://github.com/ingenieux/beanstalker/pull/68 which should address this issue. Is there any chance of it being merged in the next few days/weeks?

@dlvenable, can you see if the current snapshot (with the @mkalinin patch) appears to solve your problem?
@scatat, please way, things are a bit slower here :)

@mkalinin, there was an archetype example in the service webapp, but I think you saw it.
@dlvenable, I created an example at github.com/aldrinleal/example-awseb-worker.
First, I deployed it with mvn -Pawseb deploy
It had an issue, which was good. Fixed it, then ran the same command again but with wait-for-environment:
$ mvn -Pawseb clean deploy beanstalk:wait-for-environment
...
[INFO] Artifact Uploaded
[INFO] SUCCESS
[INFO] null
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:create-application-version (deploy) @ example-worker-app ---
[INFO] SUCCESS
[INFO] {
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "description" : "Update from beanstalk-maven-plugin",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "sourceBundle" : {
[INFO]     "s3Bucket" : "elasticbeanstalk-us-east-1-235368163414",
[INFO]     "s3Key" : "apps/example-worker-app/example-worker-app-20150918015711.zip"
[INFO]   },
[INFO]   "dateCreated" :<PHONE_NUMBER>432,
[INFO]   "dateUpdated" :<PHONE_NUMBER>432
[INFO] }
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:put-environment (deploy) @ example-worker-app ---
[INFO] ... with environmentName matching re '\Qexample-worker-app\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Calling update-environment, and using versionLabel:<PHONE_NUMBER>5711
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "example-worker-app",
[INFO]   "environmentId" : "e-9ssmpvubdf",
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2015.03 v2.0.0 running Docker 1.6.2",
[INFO]   "description" : "example-worker-app",
[INFO]   "dateCreated" :<PHONE_NUMBER>398,
[INFO]   "dateUpdated" :<PHONE_NUMBER>466,
[INFO]   "status" : "Updating",
[INFO]   "health" : "Grey",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:wait-for-environment (default-cli) @ example-worker-app ---
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qexample-worker-app\E'
[INFO] ... with status   set to 'Ready'
[INFO] ... with health equal to 'Green'
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "example-worker-app",
[INFO]   "environmentId" : "e-9ssmpvubdf",
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2015.03 v2.0.0 running Docker 1.6.2",
[INFO]   "description" : "example-worker-app",
[INFO]   "dateCreated" :<PHONE_NUMBER>398,
[INFO]   "dateUpdated" :<PHONE_NUMBER>508,
[INFO]   "status" : "Ready",
[INFO]   "health" : "Green",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:49 min
[INFO] Finished at: 2015-09-17T23:02:00-03:00
[INFO] Final Memory: 33M/126M
[INFO] ------------------------------------------------------------------------

...and it worked. I suggest you start by reviewing beanstalk.environmentRef values and paste the lookup prefix (the lines like the ones below) so we can validate it together:
[INFO] Environment Lookup
[INFO] ... with environmentId equal to 'e-9ssmpvubdf'
[INFO] ... with status   set to 'Ready'
[INFO] ... with health equal to 'Green'

Thank you

@aldrinleal, it appears that the latest source code does not find the existing environment. The environment does exist and is in the Green state.
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Updating'
[WARNING] FAILURE
org.apache.maven.plugin.MojoExecutionException: Timed out
	at br.com.ingenieux.mojo.beanstalk.cmd.env.waitfor.WaitForEnvironmentCommand.executeInternal(WaitForEnvironmentCommand.java:271)
	at br.com.ingenieux.mojo.beanstalk.cmd.env.waitfor.WaitForEnvironmentCommand.executeInternal(WaitForEnvironmentCommand.java:46)
	at br.com.ingenieux.mojo.beanstalk.cmd.BaseCommand.execute(BaseCommand.java:73)
	at br.com.ingenieux.mojo.beanstalk.AbstractNeedsEnvironmentMojo.waitForNotUpdating(AbstractNeedsEnvironmentMojo.java:490)
	at br.com.ingenieux.mojo.beanstalk.env.UpdateEnvironmentMojo.executeInternal(UpdateEnvironmentMojo.java:211)
	at br.com.ingenieux.mojo.aws.AbstractAWSMojo.execute(AbstractAWSMojo.java:386)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)

$ mvn beanstalk:describe-environments. Can you paste its output?

[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:describe-environments (default-cli) @ web-worker ---
[INFO] SUCCESS
[INFO] {
[INFO]   "environments" : [ {
[INFO]     "environmentName" : "web-worker-TEST",
[INFO]     "environmentId" : "e-spqiyyjjey",
[INFO]     "applicationName" : "testing-web-worker",
[INFO]     "versionLabel" : "Web Worker 1.0.11",
[INFO]     "solutionStackName" : "64bit Amazon Linux 2014.09 v1.2.0 running Tomcat 7 Java 7",
[INFO]     "description" : "Web Worker",
[INFO]     "dateCreated" :<PHONE_NUMBER>771,
[INFO]     "dateUpdated" :<PHONE_NUMBER>400,
[INFO]     "status" : "Ready",
[INFO]     "abortableOperationInProgress" : false,
[INFO]     "health" : "Red",
[INFO]     "tier" : {
[INFO]       "name" : "Worker",
[INFO]       "type" : "SQS/HTTP",
[INFO]       "version" : "1.0"
[INFO]     }
[INFO]     }
[INFO]   } ]
[INFO] }

The health is Red now because I made some changes. But, it was Green when I ran the first update-environment command.

I just re-tried update-environment, while the state was Red and it worked.
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Updating'
[INFO] Calling update-environment, and using versionLabel: this Web Worker 1.0.13
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "web-worker-TEST",
[INFO]   "environmentId" : "e-spqiyyjjey",
[INFO]   "applicationName" : "testing-web-worker",
[INFO]   "versionLabel" : "Web Worker 1.0.13",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2014.09 v1.2.0 running Tomcat 7 Java 7",
[INFO]   "description" : "Web Worker",
[INFO]   "dateCreated" :<PHONE_NUMBER>771,
[INFO]   "dateUpdated" :<PHONE_NUMBER>842,
[INFO]   "status" : "Updating",
[INFO]   "abortableOperationInProgress" : true,
[INFO]   "health" : "Grey",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

this is closed, but doesn't indicate the solution.

@bpappin, can you show your maven output and beanstalk.* settings please?
Thank you


update release checklist

Description
Update release checklist for publication on conda-forge
Fixes #65
Type of change
Please check options that are relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
By publishing to conda-forge for the first time
Checklist:

[x] I have read the contributing guidelines
[x] I have updated the HISTORY.rst and AUTHORS.rst files
[x] Linting passes successfully : flake8 . --exclude=doc
[x] Typing passes successfully : mypy mapie examples --strict
[x] Unit tests pass successfully : pytest -vs --doctest-modules mapie
[x] Coverage is 100% : pytest -vs --doctest-modules --cov-branch --cov=mapie --pyargs mapie
[x] Documentation builds successfully : cd doc; make clean; make html

Codecov Report

Merging #67 (b2fc627) into master (2f7507e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #67   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          554       554
  Branches        42        42
=========================================
  Hits           554       554

Continue to review full report at Codecov.

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


Add duplicate validation to add question

This commit add frontend and backend duplicate validation for add question.

LGTM! Duplicated the same updates to the Update Form as well in later commits of the branch.


Update health question interruption and check answers page

Description
Checklist

[ ] Tested against our testing policy (Resolution, Browser & Accessibility)
[ ] CHANGELOG entry

Thanks Henry. I'm going to close this. I've added in the check answers update but leaving the interruption card until we've reviewed it today.


Default device selection is a checkbox that allows user to NOT have any default device.

Go into Settings, scroll down Devices.
Notice: UI control for selecting Default Device are checkboxes.
Click the checked Default Device to uncheck it.
Click Save Changes.
Result: Generates a script error when trying to save.

Add and edit facility no longer allow unselecting the default device


DefaultTemplate not rendering any menu items in sidebar

Link to reproduction
https://github.com/elliott-w/payload-3.0-nav-bug
Payload Version
Beta 67
Node Version
v20.12.2
Next.js Version
15.0.0-canary.58
Describe the Bug
Dashboard has menu items in navbar:

But custom view does not:

Reproduction Steps
Create a custom view that uses the DefaultTemplate component imported from @payloadcms/next/templates.
Or clone my repo:
pnpm install
npm run dev
And go to:
localhost:3000/admin/test
Adapters and Plugins
db-mongodb

Oops realised this issue is the same as https://github.com/payloadcms/payload/issues/6823


Add support for conversion functions to bitmaps

Description:

wxImage has four conversion functions which could potentially be useful. For example, ConvertToGreyscale() could be useful to use for the unchecked image in a menu. ConvertAlphaToMask() would be useful for a PNG Header image being used for a toolbar button.
We could add a conversion option that would have:
- none
- disabled
- greyscale

This could be saved as an integer with 0 being none, and the others in numerical order.
The alpha conversion should only be available for PNG Header images, so it would need to be it's own option. We could store it as a bit flag added to the above conversion integer so that an extra parameter wouldn't be needed. Note that code generation would be quite different since unlike the other conversions, this one does not return a wxImage.

Need to at least investigate this further for the 1.1 release since it would involve an additional property and affect code generation for all 4 languages.

Postponing to 1.1.x milestone -- there isn't time to work on this until after the 1.1 release.

Low priority, so I removed all milestones for this issue.

I just don't think this is going to be used enough to justify further expanding the bitmaps properties -- they are already long, and about to get a fourth parameter.


Team sizes and licenses

Is there a relationship between team sizes and the licenses that were used? Probably look across all repos, not just those created.

1-person teams tend to have no license. Permissive licenses are more common than non-permissive throughout.


Dotnet Restore/ Build command fails for repo

Hi,
I am trying to run the command as below - [with .net core 6.0]

And it fails with compatibility of some Nuget packages as visible in the attached diagram. Any guidance on how to resolve?

Very wierd.  We do dotnet restore / dotnet build when we build the automated builds, so it's surprising that this is not working for you.  We also have other entities that build the tools themselves and they also have not reported any issues.
Do you have something in your environment that would cause you not to consult nuget for packages?  A nuget.config file, for example.

I cannot reproduce this.  We do dotnet restore / build as part of our build pipelines, and running it locally also works fine.  Sorry, we cannot help with dotnet environment issues.


Parsing failed For Tailwind 2.0

I get an JS error when trying to import my Tailwind 2.0 project. The ui gives me no errors or indication anything happened. For some context: it's a fairly complex project with a few plugins.

I've attached the json file I attempted to use:
tailwind.json.txt

I think the author abandoned this project. It should be archived


Fixes #46 - Manage utPLSQL core compatiblity explicitely

use utPLSQL annotation API starting with utPLSQL version 3.1.3

UtplsqlDao.xtend

added, modified tests

DalTest.xtend
UtplsqlParserTest.xtend

release v0.7.0

pom.xml

Fixes #46 - Manage utPLSQL core compatiblity explicitely


How to get withdrawal fee (txFee) for any supported cryptocurrency?

For Polo i use: public_get_returncurrencies()
Does ccxt have universal method?

Hi, @mazertwo! Sorry, but this issue is a duplicate of this: https://github.com/ccxt-dev/ccxt/issues/40. I suggest let's move our discussion there, if you have questions after reading what's already there ;)


Return last modified in UTC

AWS SDK expects LastModified time encoded in UTC:
        <*awserr.requestError | 0xc00039bd00>: {
            awsError: {
                code: "SerializationError",
                message: "failed to decode REST XML response",
                errs: [
                    {
                        Layout: "2006-01-02T15:04:05.999999999Z",
                        Value: "2020-06-19T06:56:55+03:00",
                        LayoutElem: "Z",
                        ValueElem: "+03:00",
                        Message: "",
                    },
                ],
            },
            statusCode: 200,
            requestID: "1592539015628364172",
            bytes: nil,
        }
        SerializationError: failed to decode REST XML response
                status code: 200, request id:<PHONE_NUMBER>628364172
        caused by: parsing time "2020-06-19T06:56:55+03:00" as "2006-01-02T15:04:05.999999999Z": cannot parse "+03:00" as "Z"

Thanks a lot!


cli: add option to export connection envvars

Changes config splitting default minor versions and exportable
environment variables per service.

Adds new flag --env so developers can eval the output and
configure their shell (closes #15).

Local test scenarios:
The solution doesn't implement exactly the description in #15, because it is not possible to change the parent shell environment from Python. Instead, the solution which most of the CLI programs implement, having a command/option that is directly exportable, has been implemented.
Scenario 1, short way:
$ env | grep SQL
$ eval "$(docker-services-cli up postgresql12 elasticsearch6 --env)"
$ env | grep SQL
SQLALCHEMY_DATABASE_URI=postgresql+psycopg2://johndoe:password@localhost:5432/database
$ docker ps | grep postgres:12
7ffdd557a950   postgres:12.4                                              "docker-entrypoint.s…"   About a minute ago   Up About a minute   <IP_ADDRESS>:5432->5432/tcp                           docker_services_cli_postgresql_1
$ docker ps | grep elasticsearch-oss:6.8.12
346c7f1adca0   docker.elastic.co/elasticsearch/elasticsearch-oss:6.8.12   "/usr/local/bin/dock…"   55 seconds ago   Up 54 seconds   <IP_ADDRESS>:9200->9200/tcp, <IP_ADDRESS>:9300->9300/tcp   docker_services_cli_elasticsearch_1
$ eval "$(docker-services-cli down --env)"
$ env | grep SQL

Scenario 2, the first time developer sees the feature:
$ # Clean env
$ docker-services-cli down
$ unset SQLALCHEMY_DATABASE_URI
$ docker-services-cli up postgresql12 elasticsearch6 --env
: '
Environment setup
Creating network "docker_services_cli_default" with the default driver
Creating docker_services_cli_postgresql_1    ... done
Creating docker_services_cli_elasticsearch_1 ... done
postgresql not ready at 1 retries, waiting 2s
postgresql up and running!
elasticsearch not ready at 1 retries, waiting 2s
elasticsearch not ready at 2 retries, waiting 4s
elasticsearch up and running!
Services up!
'
export SQLALCHEMY_DATABASE_URI=postgresql+psycopg2://johndoe:password@localhost:5432/database
# Configure your environment running:
# eval "$(docker-services-cli up postgresql elasticsearch --env)"
$ env | grep SQL
$ eval "$(docker-services-cli setup-env postgresql elasticsearch)"
$ env | grep SQL
SQLALCHEMY_DATABASE_URI=postgresql+psycopg2://johndoe:password@localhost:5432/database
$ docker-services-cli down --env
: '
Stopping docker_services_cli_postgresql_1    ... done
Stopping docker_services_cli_elasticsearch_1 ... done
Removing docker_services_cli_postgresql_1    ... done
Removing docker_services_cli_elasticsearch_1 ... done
Removing network docker_services_cli_default
Services down!
'
unset SQLALCHEMY_DATABASE_URI=postgresql+psycopg2://johndoe:password@localhost:5432/database
unset SQLALCHEMY_DATABASE_URI=mysql+pymysql://johndoe:password@localhost:3306/database
unset CACHE_TYPE=redis
unset CACHE_TYPE=memcached
unset BROKER_URL=redis://localhost:6379/0
unset BROKER_URL=amqp://localhost:5672//
# Configure your environment running:
# eval "$(docker-services-cli down elasticsearch postgresql mysql redis memcached rabbitmq --env)"
$ eval "$(docker-services-cli down elasticsearch postgresql mysql redis memcached rabbitmq --env)"
$ env | grep SQL

Note: docker-services-cli doesn't take services as a parameter, so the command will output unset instructions for all possible environment variables, even the ones that were not set.
Scenario 3, backwards compatible way:
$ # Clean env
$ docker-services-cli down
$ docker-services-cli up postgresql
$ docker ps | grep -i postgres:9
7524edf202a5   postgres:9.6.19   "docker-entrypoint.s…"   23 seconds ago   Up 22 seconds   <IP_ADDRESS>:5432->5432/tcp   docker_services_cli_postgresql_1

Questions

Should --env be the default output of up/down commands?

⚠  Documentation not updated until we agree on a final solution.

Feedback welcome. Usage in PR description core change in https://github.com/inveniosoftware/docker-services-cli/pull/16/commits/32f7b0c800cc283b6380f4dcd9de38e30dde8afa.
cc @lnielsen @ppanero @mvidalgarcia

I confirm the unset problem mentioned by @ppanero:
$ eval "$(docker-services-cli down --env)"
Stopping docker_services_cli_postgresql_1 ... done
Removing docker_services_cli_postgresql_1 ... done
Removing network docker_services_cli_default
unset: SQLALCHEMY_DATABASE_URI=postgresql+psycopg2://johndoe:password@localhost:5432/database: invalid parameter name

(thanks for all the ' vs ", and line adjustments too!)

' vs " -> I have black on save
line adjustments too -> most of them have come from pycodestyle checks.

One last minor thing: shuoldn't the unset printed in console be simply the variable name? e.g. unset SQLALCHEMY_DATABASE_URI, instead of unset unset SQLALCHEMY_DATABASE_URI=...? Otherwise, at least in zsh, it fails (an e.g. my comment of making it harder to run).

Definitely 🤦♀ , fixing it.

I am not a fan of having to use eval and add complexity to the way the command is used. It makes is highly error prone since not all terminals behave the same way, etc. So in my opinion it has been:

Simplified at configuration level
Made harder at "running it" level

We have a proven usability problem, everyone in GA actions sprint got confused and got it wrong, so it needs to be fixed 100%.
First proposed solution is not technically possible in a proper way (injecting envvars to parent processes).
This is presented as an opt-in feature to solve the problem, if one leaves out --env then there is no complication, other than you have to remember yourself to set the envvars (original problem).
i. To be 100% clear, I am not attached in any way to this, I just followed what is a non written standard in CLI tools when they need to export configuration to be used by other apps. If you have a better idea on how to solve this so it is easier for everyone I am all ears 😊 .

Discussed IRL, All ok for me :)

Minor: I'm not sure if this is expected but when I install it in editable mode it doesn't work.

I've quickly tested this on master branch and it happens there too. Once we merge I will create an issue from your comment to keep track of it.


Auto-skips cutscenes

When playing with the mod, the game auto skips the cutscenes near the end

Hello there!
I've done a speedrun of a meme category named "Cutscene%" - in which we watch all the cutscenes.
In the speedrun, we are required to use SilentPatch - and I never noticed any cutscenes being autoskipped anywhere; neither has anyone else reported this.
If you could check you've not got any conflicting mods (Perhaps a menu mod, eg; supermod, havoc's menu) and then perhaps return us some video footage of this happening, that would be much appreciated.
Thanks.

I don't have any other mods than silentpatch, I'll record a video and post here

It should also be noted that I play the game with Windows XP compatibility mode and forced administrator (as this was another fix for crashes), do you think that this could influence the cutscene scips?

Also found this: https://steamcommunity.com/app/12200/discussions/0/1710690018669840714/
I had FPS cap set to 144, could possibly be the problem here

Update: Set FPS limit to 30 and the cutscenes weren't autoscipped

Update: Set FPS limit to 30 and the cutscenes weren't autoscipped

60 FPS also worked fine

Turn off Comparability mode and run as admin. They don't need to be used.
Only 30fps should be used. 60fps breaks collision objects and anything over that will make the game run at double speed.

Closing then. As @xamzy said, only 30FPS is supported, an ability to lift the limit up is only a courtesy so you may freeroam at 60FPS.


the checkbox not display in role update or create

the checkbox not display in role update or create

Are you sure about that?
I just did a fresh install and everything seems to work

Did you set up everything properly?

Closing this, due to not following the configuration guide, if you get the same error please attach screens with the error.

@jstojiljkovic Hey I have the same issue.. this is the error i get in console

and this is what i see:

I have copied the content from your config/permission.php . they are indentical


Issue with GraphQL query

I am working with Apollo GraphQL .
I have table with three  records and queried from the same with graphQL as flows
Query
query getAuthors($lastName: String){
  author(lastName:$lastName){
    id
    firstName
    lastName
  }
}

Query variable
{
  "lastName": "Smith"
}

Result
{
  "data": {
    "author": [
      {
        "id": 1,
        "firstName": "James",
        "lastName": "Smith"
      }
    ]
  }
}

But if I  supply query variable as null, I am getting the  response as follows (Seems like fetching all records )
Query variable
{
  "lastName": null
}

Result
{
  "data": {
    "author": [ {
        "id": 1,
        "firstName": "James",
        "lastName": "Smith"
      },
      {
        "id": 2,
        "firstName": "Maria",
        "lastName": "Garcia"
      },
      {
        "id": 3,
        "firstName": "Maria",
        "lastName": "Rodriguez"
      }]
  }
}

I am confusing that why i am getting all records even if I pass null value for lastName

hey @jamsheer-thottathil
can you also paste code of your resolver?
this is what your resolver returns..
also, what would you expect to if variable is null?

I want to return only records which has lastName is null.
My resolver is
https://github.com/apollographql/graphql-server/issues/395#issuecomment-302409483
const resolvers = {
Query: {
author(_, args) {
return Author.findAll({ where: args });
},

hmm, to me it sounds like findAll with lastName: null just find all lastNames..
can you test it off-graphql? i mean like open small js file and console.log the result of Author.findall(where last name is null)

Right,  findAll with lastName: null just find all lastNames .
In my case its making sense less. If give null value for lastName (currently handling with client side validation )Its leads to return all records , It may give wrong search result for end user.

alright, looks like this is resolved =)
you just need to send the right query to your database..


how to shift to port 8080

Greetings,
I am learning your system on Cloud9.
It is currently confugured for port 3000.
how do I shift it to port 8080 so I can work it on port 8080?
Thank you

Thank you.  I appreciate the education.
On Fri, Sep 2, 2016 at 11:37 PM, Prashanth Batchu<EMAIL_ADDRESS>wrote:

Change the port number in config.js
dev: {
port: 3000,
...
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/antonybudianto/angular2-starter/issues/146#issuecomment-244526258,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC1-yEr1CBGvEf_OQS8tdTcMmX_gaSveks5qmPmQgaJpZM4J0Nb0
.

--
Thanks
Evan


Add Lucy Gateway

Adds in support for Lucy payment gateway. We also use track2 information so added a track2 reader to credit_card.

I'd be happy to review this for merge if you can update it to apply cleanly to master. Thanks!


"CUDA_ERROR_NOT_FOUND: named symbol not found" in Docker container

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
2.16.1-0-g5bc9d26649c
Custom code
No
OS platform and distribution
Windows 11 Pro + WSL2 Ubuntu 22.04
Mobile device
No response
Python version
3.11.0rc1
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
RTX 4080
Current behavior?
I am using Docker Desktop with WSL2 on Windows 11 Pro to run the tensorflow-gpu:latest Docker container. After starting it no GPU is found and the error failed call to cuInit: CUDA_ERROR_NOT_FOUND: named symbol not found occurs. CUDA, cuDNN and Python versions are all dictated by the Docker image so I cannot change them.
Things I have tried without success:

using a different container version (2.16.1, 2.15.0, 2.14.0, 2.13.0)
reinstalling WSL2/Ubuntu
reinstalling Docker Desktop
reinstalling GPU drivers

Reinstalling the drivers is the only thing that had any effect at all. It changed the error from CUDA_ERROR_NO_DEVICE to CUDA_ERROR_NOT_FOUND.
I have found https://github.com/google/jax/issues/13570 with a similar error but it's fix doesn't apply here. RTX 4000 cards require CUDA >=11.8 which I am using.
Standalone code to reproduce the issue
docker run --rm --gpus all -it tensorflow/tensorflow:latest-gpu bash
python3 -c "import tensorflow as tf; print(tf.config.list_physical_devices('GPU'))"

Relevant log output
2024-05-27 18:05:30.149964: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-05-27 18:05:31.089452: E external/local_xla/xla/stream_executor/cuda/cuda_driver.cc:282] failed call to cuInit: CUDA_ERROR_NOT_FOUND: named symbol not found
[]

I have the same issue: #68710

Please make sure that you have installed the Nvidia container toolkit before. Your docker container is not able to find the relevant CUDA, hence the error. Here's the documention: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

I have tried that already and it did not make a difference. AFAIK it's only necessary when running Docker on a native Linux host. In my configuration with WSL2 it should already be covered by Docker Desktop.
I have found this YouTube tutorial where it works without the container Toolkit too: https://youtu.be/YozfiLI1ogY.

**I'm getting the same issue, within the docker image  tensorflow/tensorflow:latest-gpu-jupyter (2.16.1) I am getting...
./__nvcc_device_query
./__nvcc_device_query failed to call cudaLoader::cuInit(0) with error 0x1f4 (CUDA_ERROR_NOT_FOUND)
./nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0
nvidia-smi
Tue May 28 10:03:54 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.42.03              Driver Version: 555.85         CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3070        On  |   00000000:02:00.0  On |                  N/A |
|  0%   48C    P8             21W /  220W |     637MiB /   8192MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+**

I'm getting the same issue with tensorflow/tensorflow:2.13.0-gpu-jupyter ....
E tensorflow/compiler/xla/stream_executor/cuda/cuda_driver.cc:268] failed call to cuInit: CUDA_ERROR_NOT_FOUND: named symbol not found

I can install and run CUDA samples in WSL....(Ubuntu 22.04) by installing the CUDA tool kit 12.5
Device 0: "NVIDIA GeForce RTX 3070" with Compute 8.6 capability
printf() is called. Output:
[2, 0]:         Value is:10
[2, 1]:         Value is:10
[2, 2]:         Value is:10
[2, 3]:         Value is:10
[2, 4]:         Value is:10
[2, 5]:         Value is:10
[2, 6]:         Value is:10
[2, 7]:         Value is:10
[3, 0]:         Value is:10

The workaround is working. Since this issue is pretty much a duplicate of the other one I will close it now. The other one should be left open until the latest drivers is working again.

Nvidia 555.85 not working. Cuda 12.5 buggy
Use 551.86 game ready driver and Cuda 12.4 with docker tensorflow/tensorflow:latest-gpu

Nvidia 555.85 not working. Cuda 12.5 buggy
Use 551.86 game ready driver and Cuda 12.4 with docker tensorflow/tensorflow:latest-gpu

the solution you provided it worked for me even NVidia has stated that they have fixed this specific issue in thier nvidia driver download website but seems like its not solved yet, i was on latest version as 555.85 i downgraded it to 551.86 and everything worked fine thnak you.

Nvidia 555.85 not working. Cuda 12.5 buggy
Use 551.86 game ready driver and Cuda 12.4 with docker tensorflow/tensorflow:latest-gpu

I've been running v552.22 for some time now and I don't like being so out of date. Can you, @pyjsql or anyone else, give any more details? You say that CUDA v12.5 is buggy, but the latest Nvidia driver v561.09 includes CUDA v12.6 I still have this issue under that version. In fact, I just tested every Nvidia driver v552.22-v561.09, and v552.44 is the most recent that works. Are there users using Nvidia CUDA under WSL with v561.09 successfully? What's the causal factor here? Is it the age of the GPU hardware? The WSL kernel version? What's the right place to follow this issue and find out when it's safe to upgrade the Nvidia driver? I've done a ton of googling and your "Cuda 12.5 buggy" is the most complete explanation I've found. ;-)

Thanks for all of you guys !
I've updated docker desktop on windows 10 and now it is working !


[KAF-227] suppress/revive support

To support suppress/revive
Also adds ObjectPropertyDeserializer to support reading serialized java objects from zk
Adds SchedulerState (factored out from KafkaStateStore)

@gabrielhartmann Needs review

@gabrielhartmann ready for re-review

@gabrielhartmann ready for re-review

@mgummelt:  In general, I agree with @nickbp 's comments.

@nickbp @gabrielhartmann ready for re-review


PR: Declare a clear API for Projects and move implementation code to its main widget

Description of Changes

Projects had no clear API because almost all its implementation code was part of its plugin.
This PR moved that code to its main widget, so that we can have a discernible API in the plugin.
Fix signatures of Project's public signals because they had some incorrect or outdated args.

Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ccordoba12

@dalthviz, this is ready for review.

@dalthviz, in my last commit I also fixed some bugs about recent projects that I discovered while trying to fix the bugs you reported. Its list was not being updated at startup, shutdown and when deleting a project.

Just in case, while checking again, seems like something else is still not working completly right with the recent projects functionality since you can change the maximum number of recent projects but that doesn't affect until you close Spyder:

Seems like this also is happening on 5.x though

@dalthviz, I amended my last commit to fix the bug you found and implement the change you suggested.

That's a good idea @dalthviz. Let's merge this one for now and I'll try to add tests for the bugs we found in a follow-up PR.


[BUG]

C:\Users\GUILHERME\Desktop\terraria\gta\Discord\DISCORD I.A\BingGPT-Discord-Bot>docker-compose up
[+] Building 0.2s (0/0)
[+] Running 1/1
✔ Container dcbot  Recreated                                                                                14.3s
Attaching to dcbot
dcbot  | Traceback (most recent call last):
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_exceptions.py", line 10, in map_exceptions
dcbot  |     yield
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/backends/sync.py", line 100, in connect_tcp
dcbot  |     sock = socket.create_connection(
dcbot  |   File "/usr/local/lib/python3.8/socket.py", line 808, in create_connection
dcbot  |     raise err
dcbot  |   File "/usr/local/lib/python3.8/socket.py", line 796, in create_connection
dcbot  |     sock.connect(sa)
dcbot  | OSError: [Errno 99] Cannot assign requested address
dcbot  |
dcbot  | The above exception was the direct cause of the following exception:
dcbot  |
dcbot  | Traceback (most recent call last):
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
dcbot  |     yield
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_transports/default.py", line 218, in handle_request
dcbot  |     resp = self._pool.handle_request(req)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_sync/connection_pool.py", line 261, in handle_request
dcbot  |     raise exc
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_sync/connection_pool.py", line 245, in handle_request
dcbot  |     response = connection.handle_request(request)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_sync/connection.py", line 92, in handle_request
dcbot  |     raise exc
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_sync/connection.py", line 69, in handle_request
dcbot  |     stream = self._connect(request)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_sync/connection.py", line 117, in _connect
dcbot  |     stream = self._network_backend.connect_tcp(**kwargs)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/backends/sync.py", line 107, in connect_tcp
dcbot  |     sock.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, 1)
dcbot  |   File "/usr/local/lib/python3.8/contextlib.py", line 131, in exit
dcbot  |     self.gen.throw(type, value, traceback)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
dcbot  |     raise to_exc(exc) from exc
dcbot  | httpcore.ConnectError: [Errno 99] Cannot assign requested address
dcbot  |
dcbot  | The above exception was the direct cause of the following exception:
dcbot  |
dcbot  | Traceback (most recent call last):
dcbot  |   File "src/bot.py", line 44, in
dcbot  |     gptbot = Chatbot(cookie_path='cookies.json')
dcbot  |   File "/app/src/EdgeGPT.py", line 604, in init
dcbot  |     _Conversation(self.cookies, self.proxy),
dcbot  |   File "/app/src/EdgeGPT.py", line 324, in init
dcbot  |     response = self.session.get(
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 1041, in get
dcbot  |     return self.request(
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 814, in request
dcbot  |     return self.send(request, auth=auth, follow_redirects=follow_redirects)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 901, in send
dcbot  |     response = self._send_handling_auth(
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 929, in _send_handling_auth
dcbot  |     response = self._send_handling_redirects(
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 966, in _send_handling_redirects
dcbot  |     response = self._send_single_request(request)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 1002, in _send_single_request
dcbot  |     response = transport.handle_request(request)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_transports/default.py", line 218, in handle_request
dcbot  |     resp = self._pool.handle_request(req)
dcbot  |   File "/usr/local/lib/python3.8/contextlib.py", line 131, in exit
dcbot  |     self.gen.throw(type, value, traceback)
dcbot  |   File "/usr/local/lib/python3.8/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
dcbot  |     raise mapped_exc(message) from exc
dcbot  | httpx.ConnectError: [Errno 99] Cannot assign requested address

Could you elaborate more on the steps followed to produce the error? But first, better to check there's no network or token related issues.

#33


Other apps files are deleted at Images startup

At a test environment (one server) I have two databases running exactly the same set of apps. Images is obviously one of them. We've realised, that sometimes image and other files are missing, but without any specific pattern. I found out that at every application startup we execute this method:
https://github.com/StarcounterPrefabs/Images/blob/master/src/Images/Helpers/IllustrationHelper.cs#L82
So basically we delete all files that don't exist in starting app's database. What is the reason to delete this files automatically at startup? I think that this behaviour is very unpredictable for user/administrators. I know, that I can set up different upload folders for each app in settings, but only after startup, so it's to late. Most of the users just don't change default settings at all.
I propose to remove this function. WDYT?
cc @warpech @miyconst @aloscha

I totally agree that the app should not make a decision to delete all files in the directory. Please remove this feature and the helper method.
In future, we might add an admin page to manage files in the media files directory. But that would be a more complex feature, that would allow you to check what files are used.
Please test what happens when you try to upload a file with a name that already exists in the directory.

An afterthought: Just keep the helper method, but don't call it at the application startup. Bind it to a button on the Settings page instead.

PR #58 merged to develop. Thanks!


Base Exception Class

Just create a single base exception to allow easier catching or errors.
Note: I also made a PR for 1.5 also. I wasn't sure what one I should do or if I should do both.

Closing as wontfix.


StorageSample: Wrong assignment of GTMSessionFetcher to GTMHTTPFetcher

In the storageSample, in downloadFileClicked the fetcherService returns a GTMSessionFetcher, where there is a GTMHTTPFetcher expected:
In file 'StorageSampleWindowsController.m', line 185:
GTMHTTPFetcher *fetcher = [self.storageService.fetcherService fetcherWithURLString:urlString];
It sais:
"StorageSampleWindowController.m:185:27: Incompatible pointer types initializing 'GTMHTTPFetcher *' with an expression of type 'GTMSessionFetcher *'"
I don't yet understand the neither content of the two fetchers, their differences and the already described issues in this issue list regarding those twos. Nevertheless I assume there is a coding error in the sample.
Regarding the described HTTP- / Session- Fetcher reference problems:
I fixed the missing files by referencing to the cloned files of the google projects gtm-session-fetcher and gtm-http-fetcher (where for the latter I added the -fno-objc-arc compiler flag). I assume that is the right fix and the problem lies, as said in the sample.

Yeah, the code deciding whether to use the session fetcher vs the HTTP fetcher is wrong. More details on it in are here: #100


[Android] Small Icon not working correctly in release build

I am having a weird issue with small icon. In the beginning, I thought it is just not working in release build because it was working with development build. So I checked other closed issues 243 and 92.
It works in the beginning or may be just for first few notifications then after sometime it shows a white circle.
I followed the notifee guide thoroughly and generated icons in Android Studio. Read about Shrinking via @mikehardy twitter link.
So I enabled minify and shrinking. I also added a keep.xml to make sure my icon is in resources and I checked APK in Android Studio resources.arsc in drawable it has the icon.
Now I don't know what to do because it was working and now it is not working automatically.
I'm using Expo latest version:
"expo": "^51.0.21"
"react-native": "0.74.3"
"@notifee/react-native": "^7.8.2"

Why it is working partially? Can anyone please help with this.. I am not getting any lead.
Thanks!!

I tried to reinstall the release APK but it didn't show icon at all. Just white circle!
But then I noticed a thing.
When I dismiss any notification it shows a blank notification with my icon correctly.
Here is the video.
this is the code for background event I have:
notifee.onBackgroundEvent(async ({ type, detail }) => {             const { notification, pressAction } = detail;             await notifee.cancelNotification(notification?.id || '');         });

Issue still require attention and is not fixed.

Same here, any updates?

Im facing the same issue i have pixel 6a and also pitcture we are sending are not displaying
My code:
async function onDisplayNotification(remoteMessage: any) {
await notifee.requestPermission();
const channelId = await notifee.createChannel({
id: 'default',
name: 'Default Channel',
importance: AndroidImportance.HIGH,
vibration: true,
vibrationPattern: [300, 500],
});
await notifee.displayNotification({
  title: remoteMessage?.notification?.body,
  body: remoteMessage?.notification?.title,
  android: {
    channelId,
    smallIcon: 'ic_notification',
    pressAction: {
      id: 'default',
    },
    style: {
      type: AndroidStyle.BIGPICTURE,
      largeIcon: require('../../assets/appIcon.png'),
      picture:
        endPoints.showImage +
        remoteMessage?.notification?.android?.imageUrl,
    },
  },
});

}

Solution will be appreciated thank you.

@kartvya here's my channel creation and payload
await notifee.createChannel({
id: 'my-channel-id',
name: 'My Channel',
description: 'Notifications for updates and reminders',
sound: 'default',
importance: AndroidImportance.HIGH,
});
await notifee.displayNotification({
title,
body,
android: {
channelId: 'my-channel-id',
importance: AndroidImportance.HIGH,
pressAction: {
id: 'default',
},
smallIcon: 'ic_notification',
color: '#E64626',
},
});
Maybe try specifying a color ;)
My ic_notification.png sized files are in the respective drawable-xxx folders under res. They are transparent pngs with a solid white foreground icon.

@devpascoe Thanks for respose. My icons are located in minmap files is this the corret way if it's not please correct me and also i can't genrate icons for notification i don't know what is the issue with all the sites
This is how i used it and im testing in pixel devices

same +1

same +1

need attention.

Problem with expo too

I managed it using transparent png icon and giving that icon red color to show.

My icon -


[bug report][suggestions] few providers are not working as it should

After you select ranobes, it shows its library with all the novels, but whenever you click in any novel, it will get stuck in infinite loading. The website now have a captcha before opening any novel, so it could be the problem.

Most providers filters are lacking options to filter or simply working less than intended. There is some options available to some providers but not to all of them despite being available in their websites. This feature could get a bit more refined.
Allnovel infinitely repeats the same novels when scrolling

Azynovel gives a few errors that will be attached in the print

Mtlnovel doesn't show any novels after selecting it to browse.

For these, there can be a few suggestions. While the actual method works, one competitor, Shousetsu, makes it different that could help  speed the development of the app in some ways (if possible): it stores those sites and the methods to get the novels in a repository that's in another git and allows users to implement other repos and fixing it faster, since all the things related to repos would have its dedicated space. As well, it helps patch without waiting to merge other things and solve other problems, since everytime you open the app with internet access, it will look to update the repos. Another way could be to try something else with webview or a data scrapper that passes captcha on other sites, since websites like ranobe and webnovel will try to fight against novel apps. But I'm not a developer, so that's just random gambling for what could work.
Another app that works wonders but lacks lots of features (while having others that I envy) is LNReader. The way they implement sources is really some fine work. Would be nice to take a look at their work. What they miss is the direct way to download in epub and open in an external reader directly from the app.

fixed as of https://github.com/LagradOst/QuickNovel/commit/3bc8b08fe13ef7d447e743578e35a59d40e72b93
removed RanobesProvider due to capcha
added cloudflarekiller to MTLNovel (still not working)
fixed NovelFull+AllNovel pages
removed Azynovel as it does not exist anymore

bypassing any sort of capcha is not possible even with webview
Shousetsu repos use an entirety different backend and not smth I can just add without much work
LNReader uses React, I am not even sure if I can those sources


Dynamic relay list

Replace the static list of relayers with a dynamic one: now the backend_urls.json file is embedded at the compilation stage. It would be necessary to implement its dynamic loading when opening the page with the application (app.html).

Resolved in #79


Project dead?

It seems this project is not actively maintained currently.
There are many PRs that are open, awaiting reviews / merges.
@nacmartin if you don't have any time to maintain, would you be open for adding new maintainers?

@deguif sure, I'd like to devote more time to this project but unfortunately life keeps adding more priorities to my TODO list. Would you (or maybe someone else) want to volunteer?

Yes will be pleased to help maintaining this project.
I'm already impliqued in many other bundles / projects

Thanks for your kind offer! Invited :)


Quick fix to parse post in transformer when a string is passed in

Fixes # (issue)
Goals :soccer:

Implementation Details :construction:

Testing Details :mag:

rerun tests


NadekoBot occasionally crashes

Running NadekoBot on my Win7-64bit system, it occasionally crashes with a Windows error "NadekoBot.exe has stopped working". Is there any way to get a crash report and put it here next time it occurs?

You can always go to Nadeko's Discord server, and ask for help from support. But you should also check your Nadeko setup, because this is the first time I see this error. :]

Yep, this should never happen, please come to our discord server and we'll resolve it. https://discord.gg/0ehQwTK2RBjAxzEY


Flipper Hub Ultimate board Touchscreen issue

Hey again.
Updated the Flipper Hub Ultimate board with the spookytools flasher.
Touchscreen has no function.
Flashed marauder on it to confirm functionality of the screen. Hardware is ok, Touchscreen works.
Flashed GhostESP 1.4.2 and 1.4.3 on it.
Touchscreen with bot fw without function.

Hey again. Updated the Flipper Hub Ultimate board with the spookytools flasher. Touchscreen has no function. Flashed marauder on it to confirm functionality of the screen. Hardware is ok, Touchscreen works. Flashed GhostESP 1.4.2 and 1.4.3 on it. Touchscreen with bot fw without function.

it should work as i verified it worked on 1.4.2 can you give me more details

I flashed as suggested with your flasher. FlipperHub, blue port, flashed successfully. Touchscreen doesn't work. Flashed Marauder with FZEE on it, Touchscreen works. Tried launching WebUi. I remembered it showing V 1.4.1 before, but now I cant even get the WebUi to show up.
I don't know what I'm doing wrong

I flashed as suggested with your flasher. FlipperHub, blue port, flashed successfully. Touchscreen doesn't work. Flashed Marauder with FZEE on it, Touchscreen works. Tried launching WebUi. I remembered it showing V 1.4.1 before, but now I cant even get the WebUi to show up. I don't know what I'm doing wrong

id recommend you showing me some logs of you attempting to use it through the serial terminal as that will give me more insight of what is happening

serial_logs.txt
Added logs... hope I did it right

SD card rendered fake touch input due to bord layout. SD card removed and Touchscreen worked.
Unser error.
Thanks for the help though


Persistent RNN functions in cuDNN v6

This PR is related cupy PR ( https://github.com/cupy/cupy/pull/549 ).
Note that only CA (Compute Capability) > 6.0 supports Persistent RNN.
https://developer.nvidia.com/cuda-gpus
I have checked this PR in cuDNN v6 and v7.

algo=standard (v6, v7)
algo=static (v6, v7)
algo=dynamic (v6, v7)

jenkins test this please

I think that travis error is not related this PR.

As we discussed offline, we found it is not enough fast with the current implementation. I think our implementation has another bottle neck especially when mini-batch size is small. Before merging this PR, we need to improve the current implementation.
BTW, i refactored RNNs. Please check the latest one.

OK. Thank you for refactoring!!
After papr submission (deadline is 2/23 in Japan), I will fix code.

It seems that when we use rnn_algo = 'static' or 'dynamic', output does not correspond to standard.
https://gist.github.com/aonotas/be96e909e2382013c4c0df5ebc844525
I will support rnn_algo = 'standard' only.
Branch
Chainer : https://github.com/aonotas/chainer/tree/support_persistent_rnn_cudnn
Cupy : https://github.com/aonotas/cupy/tree/support_persistent_rnn_cudnn
I close this PR.


Remove data access URL when uploading data manually?

We have a data access url in a datasets settings which we use to pull data when an import is triggered.
You can also manually upload an archive though. Should this then remove the access url from the settings? Otherwise hitting import again after the upload has happened will overwrite the manually uploaded data.
For example reptile db still has the old ACEF file listed in its settings, but the data in CLB is more up to date because of manual uploads.

@gdower would you agree with that?

Do you mean just setting the data access URL to empty when an archive is uploaded? That's fine by me, so long as I can still set the data access URL.

yes, set it to NULL.
Otherwise I fear we overwrite the manually uploaded archive easily

or we could change the UI to ask if you also want to reset the access url whenever you upload a file

I think setting it to NULL is a good idea for now. Other users probably won't realize that the data access URL is reset when they upload an archive, so at least warning them that the data access URL will be reset would probably be a good idea.

ok, I'll do so then


aarch64: "manifest unknown: manifest unknown" error from "docker pull"

Description
"docker pull portainer/portainer" fails with "manifest unknown: manifest unknown"
Steps to reproduce the issue:

Docker 1.12.5 on CentOS 7.3 on Packet 2A server
docker pull portainer/portainer
error:

docker pull portainer/portainer
Using default tag: latest
Trying to pull repository docker.io/portainer/portainer ...
latest: Pulling from docker.io/portainer/portainer
manifest unknown: manifest unknown

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Expected the aarch64 version of portainer to be pulled to my docker instance.
Technical details:

Portainer version: none
Portainer Docker image tag (latest/arm/windows...):
Target Docker version (the host/cluster you manage): Docker version 1.12.5, build 047e51b/1.12.5
Target Swarm version (if applicable):
Platform (windows/linux): linux/arm64
Browser: none

And now it just works; I wonder if there's some dependency on AWS triggered by recent downtime.
Since this isn't likely to have been a minio problem, I'm closing.

Yup, probably related to the AWS outage yesterday.


Mica doesn't work when applied to an UserControl

Describe the bug
When you apply Mica to an UserControl, it doesn't work.
Steps to reproduce the bug

Steps to reproduce the behavior:

Create a new UWP project
Install WinUI 2.6
Replace Page/Frame with UserControl
Apply Mica to the UserControl using muxc:BackdropMaterial.ApplyToRootOrPageBackground="True".
Deploy and run the app on Windows 11 and see the issue

Expected behavior
Mica should be applied on the surface.
Version Info

NuGet package version:

Microsoft.UI.Xaml 2.6.1

Windows app type:

UWP
Win32

Yes
No

Windows version
Saw the problem?

Insider Build (22000.100)
Yes

October 2020 Update (19042)

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

@jevansaks thoughts?

By default does UserControl draw a background? I can't remember but I feel like Control and UserControl are weird in that they have the Background property but it's up to the template/code-behind to do something with the value.
Take Mica out of the picture, what happens if you set UserControl's Background="Orange". Do you see anything?

By default does UserControl draw a background? I can't remember but I feel like Control and UserControl are weird in that they have the Background property but it's up to the template/code-behind to do something with the value.
Take Mica out of the picture, what happens if you set UserControl's Background="Orange". Do you see anything?

That's right, the background that I set doesn't actually apply to the content inside by default however at least I should be able to apply Mica to a Grid for example.

I thought Mica can only be applied to the Window/Page background, at the lowest level surface?

I thought Mica can only be applied to the Window/Page background, at the lowest level surface?

The lowest level surface need not be a Page. You can use a UserControl as the root element or any other control for that matter.

I thought Mica can only be applied to the Window/Page background, at the lowest level surface?

The lowest level surface need not be a Page. You can use a UserControl as the root element or any other control for that matter.

This is true. But the behavior of the BackdropMaterial attached property is that it sets the Background property in the fallback case so it needs to be hooked up correctly in the control. @ranjeshj you can use this issue to track updating the documentation?


Temp Files

Setup or portable version of the app?
Portable
Steps to reproduce
Temp Files Directory - C:\Users\  Your Pc Username Here  \AppData\Local\Temp

Open any zip, cbz, epub file in yomikiru.
After they are unzipped and loaded, open temp files directory.
You can see all the temporary files stored there with the names and extension of the zip, cbz, epub previously opened by the app.

✔ Expected Behavior

I am using portable version, so the temp files should be stored in the portable directory with folder name temp or any other.
And the temp files should be deleted from the portable directory on app exit.

❌ Actual Behavior

The temp files are being stored in the user directory even though I am using the portable version of the app.
The temporary files are not being cleared even after closing the application.

I am using portable version, So the temp files should be stored in the portable directory.
And the temp files should be deleted from the portable directory on app exit.

I'm not sure if that's how it is supposed to work. Temp directory is managed by the system and is recommended for this kind of work. Though it is possible to make it that way but then I will hate to create different rules for portable and setup version.
As for the deleting, there might be some issue there, I'll check that.


Documentation and code are inconsistent

Hi!
Thanks for your team's great work!
I read your docs carefully and see for tasks like, "StackCube-v1", "PickSingleYCB-v1", etc., do support xarm. However, when I run the code  like
env = gym.make(
"PickSingleYCB-v1",
obs_mode="state",
robot_uids="xarm",
num_envs=16
)
it still keeps saying the robot is not supported.
So, how can I use xarm for these tasks?
Thanks in advance.

Looks like we need to add back the xarm in to those tasks as supported. If I recall correctly we needed to fix some parts of the xarm. We will get this fixed soon


Restructure pr curves notebook

This PR is ready for review!
In this PR, the class PR curves notebook is restructured to follow the structure of the evaluate notebooks.
This means all the models are evaluated on each data subset and the resulting data are saved in one compiled `.tsv. file.

Thanks for the review! These images should not be replaced by anything new. The format for the 3.evaluate_model module is to save the intermediate data for evaluations in .tsv and keep the image evaluations in the notebooks.


Returning clause of insert statement

Oh, the PR had a comment that it was only inserts. Maybe it was enhanced midway through the PR's revisions?

@Alex-Monahan is there anything blocking this getting merged? Would be great to be able to point to the docs for this

Nothing blocking, just a todo for delete and update statements (that could be a separate issue)

Let’s merge this then and deal with the other statements separately


key combination/sequence disables ability to use first key e.g. C-x  doesn't work if C-x C-f defined

Example:
Install Claire plugin.
It will include:
{:+ {:app {"ctrl-x ctrl-f" [:claire-show]} ... .
At this point, "ctrl-x" [:editor.cut] won't work anymore.
Try to add the following to user.keymap:
{ :- { :app
          { "ctrl-x ctrl-f" [:claire-show] }
     [others]
}

and cut will work again.
Great IDE imho, I will try to contribute as much as I can.

I don't know if this is by design or a bug but the core team will look into it at some point

@cldwalker What can we do for this? Not allow the Emacs-style bindings to be bound if an leading sequence of key combinations have already been bound?

@kenny-evitt It's not so much an Emacs plugin issue as it is investigating how combo keybindings are clobbering individual keys

@cldwalker But what could we do? Just prevent combo keybindings from clobbering existing keys? Or prevent any keybinding from clobbering an existing one?


home-assistant: support here_travel_time component

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

686 / 994 components supported, i.e. 69.01% sunglasses

Faster than the vaccination status in Germany.

686 / 994 components supported, i.e. 69.01% sunglasses

Faster than the vaccination status in Germany.

I fear they'll overtake us.


Azure CLI --sdk-auth is getting deprecated

Azure example in this documentation uses --sdk-auth flag to generate credentials. But Microsoft documentation shows that it is deprecated.
Currently, azure cloud provision uses NewEnvironmentCredential that crafts credentials from environment variables previously set from the JSON access token file. A possible alternative is to use ClientSecretCredential and initialize it from the new JSON file that is returned if --sdk-auth is not specified.
New JSON file sample:
{
  "appId": "", // same as client id
  "displayName": "",
  "password": "", // same as client secret
  "tenant": ""
}

So what do you suggest using instead of passing --sdk-auth to obtain the initial token?
I.e. what replaces?
SUBSCRIPTION_ID="YOUR_SUBSCRIPTION_ID"
az ad sp create-for-rbac --role Contributor --scopes "/subscriptions/$SUBSCRIPTION_ID" --sdk-auth \
  > $HOME/Downloads/client_credentials.json

And is this just a docs change or does code need to change also? I suspect the former?
cc @zechenbit

/add label: helpwanted

Thanks @d0pare for raising this and putting useful information together. I found some related discussions in Azure CLI repository:

How the fields are mapping with and without --sdk-auth: https://github.com/Azure/azure-cli/issues/22297
https://github.com/Azure/azure-cli/issues/20743

Per their discussion (https://github.com/Azure/azure-cli/issues/21693#issuecomment-1120115472), the --sdk-auth won't be removed in near future. Many tools are still relying on this such as https://github.com/marketplace/actions/azure-login.
If it is just the naming, then maybe we can just change our fileToEnvMap: https://github.com/inlets/cloud-provision/blob/master/provision/azure.go#L35
The NewEnvironmentCredential will eventually call NewClientSecretCredential https://github.com/Azure/azure-sdk-for-go/blob/sdk/azidentity/v1.5.1/sdk/azidentity/environment_credential.go#L80


how to add or get AZ details when pod created.

What happened:
how we can get or add AZ details when pod is created.
What you expected to happen:
we didn't get any info when the pod is created on which AZ and for doing this we need to write a script.
is there any other way we can achieve this?

Hi @jainpratik163, I'm not sure how this is related to the pod identity webhook, since the purpose of the webhook is to provide AWS IAM credentials to a pod's Service Account.
Depending on what Kubernetes solution you are using (EKS, kops, self-deployed, etc), you may have passed the AWS region into the Pod's definition via environment variables or possibly as annotations on the Pod's metadata.


Do not remove summary dir

https://github.com/taomanwai/tensorboardcolab/blob/337dce9890dadcb977b60322c30c76dee7fb42b1/tensorboardcolab/core.py#L21
Every time i rerun the setup, it removes all my saved summaries. While sometimes after a long run model, the ngrok connect breaks, so i have to rerun the tensorboardcolab, and hours of works are gone.
Of course i can always run ngrok http 6006 instead after the setup, but somehow i forget every time.

I also encountered the same problem. After a long run, ngrok will show 'tunnel expired error' since we do not log in ngrok account. How about designing an input box and let we fill in the authtoken?


Adds LangGraph tracing guide

thanks! added a couple comments in vercel preview

Addressed your comments, thanks!