Got HTTPS warning

Data returned successfully but got https warnings.
data = get_historical_klines('BTCUSDT', Client.KLINE_INTERVAL_4HOUR, 'October 15, 2020', 'October 20, 2020')

/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py:981: InsecureRequestWarning: Unverified HTTPS request is being made to host 'api.binance.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings

This happens because Binance does not support a sandbox API. This is fine and you can ignore it and continue on with whatever you want to do, or you can suppress the warning using
import warnings
warnings.filterwarnings("ignore")

This happens because Binance does not support a sandbox API. This is fine and you can ignore it and continue on with whatever you want to do, or you can suppress the warning using
import warnings
warnings.filterwarnings("ignore")

just make sure you put it before the data line

I'll try. Thanks.


The Sample Page Has an Error

FIREBUG:
17:42:04.562 ERROR:  Not Connected! Error: Cannot connect to ErizoController (socket.io error)1 erizo.js:169:1
17:42:04.563 DEBUG:  Event: room-error1 erizo.js:169:1
and it just has one camera view in the page.Could you Help me?
Thanks!

Hi @yuanxing008, we had a problem with our servers, but it's solved by now. Thanks!


Possible leakage of email addresses in "mail everyone"

In a few places:

https://github.com/swcarpentry/amy/blob/d9e9c32fea7cf978cf9c264bff50daeabd9e1823/workshops/templates/workshops/event.html#L129
https://github.com/swcarpentry/amy/blob/d9e9c32fea7cf978cf9c264bff50daeabd9e1823/workshops/templates/workshops/instructors_by_date.html#L25
https://github.com/swcarpentry/amy/blob/d9e9c32fea7cf978cf9c264bff50daeabd9e1823/workshops/templates/workshops/workshop_staff.html#L46

we use mailto:bunch_of_emails. These email addresses may end up in "To" field instead of "BCC" (correct me if I'm wrong). In that case, recipients can see other recipients' email adresses. However, I'm not sure if this is unwanted behaviour. @gvwilson, any opinion?
Fix: use mailto:?bcc= instead of mailto:.

:+1: to this change - good catch.


feat: update to drawio-desktop 24.7.17

Automated changes by create-pull-request GitHub action

:tada: This PR is included in version 1.38.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Archive gometalinter

The gometalinter GitHub project will be archived on 2019-04-07. Releases will still be available for download but no further code will be committed and issues will be read-only.
Switch to golangci-lint.
Many thanks to all contributors, in particular @dnephin who has helped me maintain gometalinter for the last year or two.
Edit: Just to be clear: binary downloads will still be available and the repository will remain, it will just become read-only and all development will cease. Any existing projects that use gometalinter will continue to work.

Please, don't be too fast with this decision.
Let this issue be open for at least several weeks.
Maybe someone would have good arguments in favor of not doing it.
My first step outside of "go lint only" was gometalinter, so I feel nostalgic. :(

I do not have much time to maintain the project. At most I seem to have a bit of time to answer the occasional question on the issue tracker.
Maybe a first option could be to add a note at the top of the README and in the issue template saying something like the above (current maintainers are considering archiving the project, if you are interested in taking over please say something).
If nothing changes over the next few (maybe 6?) months then I guess archiving would seem like an acceptable option.
I can volunteer to make those changes sometime over the next week or so if that is what we decide.

That sounds reasonable.

Put a note in the README of our intentions.
Archive it in 3 months.

@alecthomas thanks so much for all your hard work on this project! It's had a measurable impact on runatlantis/atlantis and found a couple of bugs I'd missed.
Golangci-lint almost has feature parity so I think EOL'ing this project is a totally legit decision.
🥂 Cheers and thanks again! 🥂

You're welcome.
I'll archive the project on April 7th.

Thank you for all your great work @alecthomas 💯

I've updated the title and README accordingly.

Thanks for making such a great project @alecthomas!

Thanks for all the work @alecthomas!

Thank you for all the hard work @alecthomas and @dnephin .
I was going to offer my help to keep the development of the project alive, especially adding more concurrency and recycled buffers, but I realized that taking care of all the code, issue tracker, and —possibly— editor plugins would require a significant amount of time. I would also end up rewriting the entire code base and releasing a binary very similar to golangci-lint, so maybe it’s not worth the trouble.
I still like gometalinter more than golanci-lint.
Yesterday I spent a few hours creating a new version of the SublimeLinter package for golangci-lint, an improvement over this [1]. Unfortunately, after learning a bit more about this linter, I started to dislike it, especially the fact that some warnings are sent to /dev/stderr and others to /dev/stdout . It also seems to encourage people to configure its behavior using a configuration file, and considering how opinionated Go is, I was expecting something more simple, a plug-and-play sort of thing.
Thank you, once again, and let us hope golangci-lint gets better to justify the switch.
[1] https://github.com/alecthomas/SublimeLinter-contrib-golang-cilint

@alecthomas thank you for this great project! I used gometalinter in a lot of projects, it helped our teams a lot.

@alecthomas you are totally awesome.
You really make a difference to the go community (at least the parts I know).
I particularly respect that you saw another tool out there that did something similar to your project and you decided it's doing it better in many ways and there is no point competing, so you just retire yours and put your effort into other things (hopefully I'm not misinterpreting it all).
That is just really cool and humble all at the same time.
Chapeau, monsieur!

Thanks everyone for all the kind words, I appreciate it.
And yes, @juliaogris, you are interpreting the situation correctly. gometalinter is a tool that started out as quite straightforward, but due to the proliferation of linters in the Go community (which is excellent), quickly got out of hand. @dnephin and I discussed integrating the linters directly as golangci-lint has done, but neither of us had the time nor frankly the inclination, given that gometalinter worked well enough for our purposes. Once golangci-lint popped up, integrating linters in-process as we had planned, I was personally quite relieved that someone else had done the work! :)
Anyway, thanks again and all the best.

Gometalinter was pivotal in the development of Go Report Card. It made the linter output more consistent and easier for us to parse. Thank you for your work.

Sad to see the project closing. Thank you for developing and maintaining for as long as you have.

@alecthomas
Strongly suggest NOT asking ppl to move to golangci-lint for now, nothing is working there, too much issues, the project is still at a very immature state.

@lnshi, could you be more specific, please?
It might help to solve those issues (much) faster.

I reported all issues on their side, but no reply.
On Mon, 1 Apr 2019 at 19:45, Iskander (Alex) Sharipov <
<EMAIL_ADDRESS>wrote:

@lnshi https://github.com/lnshi, could you be more specific, please?
It might help to solve those issues (much) faster.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alecthomas/gometalinter/issues/590#issuecomment-478546170,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXcQErsmczcE1Wo6SmQA0obQ4bFs8P-nks5vcfFJgaJpZM4am40w
.

You reported those issues 2-6 hours ago. Have some patience. I and many others have been using golangci-lint for months across many machines, different CI infrastructure, etc. with no issues. One anecdote doesn't make a fact.

golangci-lint as GPLv3 is a major headache for many commercial companies and in some cases an insurmountable barrier.  I just wanted to point it out.  I am not saying you shouldn't do what you need to do with this project.  Do you have other non-GPLv3 recommendations?

I'm not aware of any other alternatives, no.
Given that golangci-lint is a tool, not a library, I'd say any objections to its use based on it being GPLv3 are issues brought about by corporate policy, not practicality. Additionally, they offer a commercial solution.

golangci-lint as GPLv3 is a major headache for many commercial companies and in some cases an insurmountable barrier.

If you want to ship a commercial linter product, maybe fork the code and maintain it yourself?

Well, it's time.
Thanks again to all the contributors over the years, in particular @dnephin, and all the users who've been helpful.
So long, and thanks for all the fish.


Made headers case insensitive

Coverage remained the same at 100.0% when pulling ad839b3689f764ac4160e81660a71607241db3e7 on whiskeysierra:bugfix/case-insensitive into 9c9c1d1d1ec5169f072e1d37a7fea207b9579afe on zalando:master.

Coverage remained the same at 100.0% when pulling ad839b3689f764ac4160e81660a71607241db3e7 on whiskeysierra:bugfix/case-insensitive into 9c9c1d1d1ec5169f072e1d37a7fea207b9579afe on zalando:master.

Coverage remained the same at 100.0% when pulling 4c52ae62593b2685b44513e56eaa0e4d99f77ac1 on whiskeysierra:bugfix/case-insensitive into 9c9c1d1d1ec5169f072e1d37a7fea207b9579afe on zalando:master.


[cocoapods david lgtm] An invalid JSON is mocked using invalidJSON in all service tests

This PR standardize mocking a invalid JSON in service tests. This is a follow-up to https://github.com/badges/shields/pull/1755. I tried to find all custom mocks of the invalid JSON using grep, but I could miss something.

Thanks @chris48s! Fixed, all tests passed :-)


Improve accessibility of inputs

Changes

Improve keyboard and screen reader accessibility of <Toggle/> component
Restore keyboard accessibility of <Checkbox/> and <RadioButton/> components

Coolio.


[Feature request] Is it possible to provide debug mode?

Hi @jedmao, thanks for writing such an awesome open source tool, it's very useful for me.
I just found that I'm facing a strange situation which may be caused by a bug of eclint, so I wonder how can I debug it.
I have my indent configured to 2 spaces, and I have some files with 4 indent but both eclint check & eclint fix do nothing on them, the result of eclint infer tells me the files are using 4-spaces indent which is correct, but it didn't detect anything wrong when I'm using check or fix command, do you have any suggestion, please?
Many thanks!

This may be a bug from editorconfig-core-js as I use the command line of editorconfig nodejs version, it tells me that the files is using 2 spaces, but there is no 2 spaces indent in the files, so the infer of eclint is much more smarter than the upstream!

how can we get spaces number of one indent in a line? 8 spaces maybe 2, 4 or 8.

I guess that's how the infer doing? 2 or 3 lines will help to decide the indent spaces?

eclint does not do syntax parsing, so we do not prevent users from using a two-unit indent.
If you want to parse syntax, you should use tools such as gulp-stylelint, gulp-eslint, etc.

Yeah I guess so :)

Has your problem been resolved? Can I close this issue?


docs: update toturial for IntelliJ IDEs

Closes: #9

/cc @trivikr

This tutorial is broken after 1 year and I'm using a M2 macbook pro. Seems like there is an arch-related issue?

This tutorial is broken after 1 year and I'm using a M2 macbook pro. Seems like there is an arch-related issue?

@himself65 would you mind updating the PR? Or maybe we could merge this one if it is working for non-m-series users.

OK, I made it work again by another config


支持AES解密

支付宝官方文档:  https://docs.alipay.com/mini/introduce/aes
应用场景: https://docs.alipay.com/mini/introduce/getphonenumber

已经合并，新版本 https://github.com/wi1dcard/alipay-sdk-php/releases/tag/v1.2.0 已同步至 Packagist，欢迎更新、测试。
再次感谢您的贡献。

Pull Request Test Coverage Report for Build 137

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

Totals

Change from base Build 133:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Tradebot does nothing on Kraken

I'm on the exchange XLM-XBT and I've let the bot run for 3 days with these settings and it does nothing but this :

Here are my settings :

It's currently very hard to work with kraken, we are in the process of fixing this.
We just merged some changes into the develop version of Gekko that might change it, see #1411. You can try it out by downloading the develop branch of Gekko here: https://github.com/askmike/gekko/tree/develop
If you run into issues with that branch, please report them here (and specify exactly what version of Gekko you have the issues with): #1431.
Closing this as a duplicate of #1431.


Fix: add package version for cache key

Close #436

Codecov Report

Merging #443 (ecc292e) into release-next (cbbd9be) will decrease coverage by 0.00%.
The diff coverage is 72.72%.

@@               Coverage Diff                @@
##           release-next     #443      +/-   ##
================================================
- Coverage         81.71%   81.70%   -0.01%
================================================
  Files                87       87
  Lines              7519     7521       +2
  Branches            949      950       +1
================================================
+ Hits               6144     6145       +1
- Misses             1368     1369       +1
  Partials              7        7

Impacted Files
Coverage Δ

packages/ice/src/service/config.ts
86.58% <72.72%> (-0.46%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update Pylint RC file

@tseaver After running
pylint --generate-rcfile

I curated the output to mostly match ours and made a simple diff:
diff --git a/pylintrc_default b/pylintrc_default
index 27c4b5d..72bb922 100644
--- a/pylintrc_default
+++ b/pylintrc_default
@@ -19,9 +19,6 @@
 # pygtk.require().
 # DEFAULT: init-hook=

-# Profiled execution.
-# DEFAULT:  profile=no
-
 # Add files or directories to the blacklist. They should be base names, not
 # paths.
 # DEFAULT:  ignore=CVS
@@ -42,15 +39,33 @@ ignore =
 #            they document.
 load-plugins=pylint.extensions.check_docs

-# DEPRECATED
-# DEFAULT:  include-ids=no
+# Use multiple processes to speed up Pylint.
+jobs=1
+
+# Allow loading of arbitrary C extensions. Extensions are imported into the
+# active Python interpreter and may run arbitrary code.
+unsafe-load-any-extension=no
+
+# A comma-separated list of package or module names from where C extensions may
+# be loaded. Extensions are loading into the active Python interpreter and may
+# run arbitrary code
+extension-pkg-whitelist=

-# DEPRECATED
-# DEFAULT:  symbols=no
+# Allow optimization of some AST trees. This will activate a peephole AST
+# optimizer, which will apply various small optimizations. For instance, it can
+# be used to obtain the result of joining multiple strings with the addition
+# operator. Joining a lot of strings can lead to a maximum recursion error in
+# Pylint and this flag can prevent that. It has one side effect, the resulting
+# AST will be different than the one from reality.
+optimize-ast=no

 [MESSAGES CONTROL]

+# Only show warnings with the listed confidence levels. Leave empty to show
+# all. Valid levels: HIGH, INFERENCE, INFERENCE_FAILURE, UNDEFINED
+confidence=
+
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option
 # multiple time. See also the "--disable" option for examples.
@@ -120,13 +135,9 @@ reports=no
 # (RP0004).
 # DEFAULT:  evaluation=10.0 - ((float(5 * error + warning + refactor + convention) / statement) * 10)

-# Add a comment according to your evaluation note. This is used by the global
-# evaluation report (RP0004).
-# DEFAULT:  comment=no
-
 # Template used to display messages. This is a python new-style format string
 # used to format the message information. See doc for all details
-#msg-template=
+# DEFAULT:  msg-template=

 [SIMILARITIES]
@@ -157,6 +168,27 @@ reports=no
 # you should avoid to define new builtins when possible.
 # DEFAULT:  additional-builtins=

+# List of strings which can identify a callback function by name. A callback
+# name must start or end with one of those strings.
+callbacks=cb_,_cb
+
+
+[SPELLING]
+
+# Spelling dictionary name. Available dictionaries: none. To make it working
+# install python-enchant package.
+spelling-dict=
+
+# List of comma separated words that should not be checked.
+spelling-ignore-words=
+
+# A path to a file that contains private dictionary; one word per line.
+spelling-private-dict-file=
+
+# Tells whether to store unknown words to indicated private dictionary in
+# --spelling-private-dict-file option instead of raising a message.
+spelling-store-unknown-words=no
+

 [LOGGING]

@@ -168,7 +200,7 @@ reports=no
 [FORMAT]

 # Maximum number of characters on a single line.
-# DEFAULT:  max-line-length=80
+max-line-length=100

 # Regexp for a line that is allowed to be longer than the limit.
 # DEFAULT:  ignore-long-lines=^\s*(# )?<?https?://\S+>?$
@@ -198,6 +230,9 @@ max-module-lines=1500
 # Number of spaces of indent required inside a hanging or continued line.
 # DEFAULT:  indent-after-paren=4

+# Expected format of line ending, e.g. empty (any line ending), LF or CRLF.
+expected-line-ending-format=
+

 [MISCELLANEOUS]

@@ -207,15 +242,12 @@ max-module-lines=1500

 [BASIC]

-# Required attributes for module, separated by a comma
-# DEFAULT:  required-attributes=
-
 # List of builtins function names that should not be used, separated by a comma
 # DEFAULT:  bad-functions=map,filter,apply,input,file

 # Good variable names which should always be accepted, separated by a comma
 # DEFAULT:  good-names=i,j,k,ex,Run,_
-# RATIONALE:  'pb' and 'id' have well-understood meainings in the code.
+# RATIONALE:  'pb' and 'id' have well-understood meanings in the code.
 good-names = i, j, k, ex, Run, _,
              pb,
              id,
@@ -292,13 +324,19 @@ good-names = i, j, k, ex, Run, _,

 # Regular expression which should only match function or class names that do
 # not require a docstring.
-# DEFAULT:  no-docstring-rgx=__.*__
+no-docstring-rgx=^_

 # Minimum line length for functions/classes that require docstrings, shorter
 # ones are exempt.
 # DEFAULT:  docstring-min-length=-1

+[ELIF]
+
+# Maximum number of nested blocks for function / method body
+max-nested-blocks=5
+
+
 [TYPECHECK]

 # Tells whether missing members accessed in mixin class should be ignored. A
@@ -307,21 +345,19 @@ good-names = i, j, k, ex, Run, _,

 # List of module names for which member attributes should not be checked
 # (useful for modules/projects where namespaces are manipulated during runtime
-# and thus existing member attributes cannot be deduced by static analysis
+# and thus existing member attributes cannot be deduced by static analysis. It
+# supports qualified module names, as well as Unix pattern matching.
 # DEFAULT:  ignored-modules=

 # List of classes names for which member attributes should not be checked
-# (useful for classes with attributes dynamically set).
-# DEFAULT:  ignored-classes=SQLObject
-
-# When zope mode is activated, add a predefined set of Zope acquired attributes
-# to generated-members.
-# DEFAULT:  zope=no
+# (useful for classes with attributes dynamically set). This supports can work
+# with qualified names.
+ignored-classes=

 # List of members which are set dynamically and missed by pylint inference
-# system, and so shouldn't trigger E0201 when accessed. Python regular
+# system, and so shouldn't trigger E1101 when accessed. Python regular
 # expressions are accepted.
-# DEFAULT:  generated-members=REQUEST,acl_users,aq_parent
+generated-members=

 [IMPORTS]
@@ -344,10 +380,6 @@ good-names = i, j, k, ex, Run, _,

 [CLASSES]

-# List of interface methods to ignore, separated by a comma. This is used for
-# instance to not check methods defines in Zope's Interface base class.
-# DEFAULT:  ignore-iface-methods=isImplementedBy,deferred,extends,names,namesAndDescriptions,queryDescriptionFor,getBases,getDescriptionFor,getDoc,getName,getTaggedValue,getTaggedValueTags,isEqualOrExtendedBy,setTaggedValue,isImplementedByInstancesOf,adaptWith,is_implemented_by
-
 # List of method names used to declare (i.e. assign) instance attributes.
 # DEFAULT:  defining-attr-methods=__init__,__new__,setUp

@@ -357,6 +389,10 @@ good-names = i, j, k, ex, Run, _,
 # List of valid names for the first argument in a metaclass class method.
 # DEFAULT:  valid-metaclass-classmethod-first-arg=mcs

+# List of member names, which should be excluded from the protected access
+# warning.
+exclude-protected=_asdict,_fields,_replace,_source,_make
+

 [DESIGN]

@@ -400,6 +436,9 @@ min-public-methods=0
 # RATIONALE:  API mapping
 max-public-methods=40

+# Maximum number of boolean expressions in a if statement
+max-bool-expr=5
+

 [EXCEPTIONS]

Some things worth noting

the default list of disabled went from empty to include 50 things
max line length went from 80 to 100 (but AFAIK it's 79 in the pep8 defaults)
adding [MASTER].jobs to speed up execution (happy, happy)
a [SPELLING] section was enabled for spellcheck (via python-enchant)
[FORMAT].expected-line-ending-format added (so we can disallow Windows line endings)

@tseaver Can you inspect the diff and comment on things we should take advantage of?

@tseaver Bump

The new commented out defaults are fine.
Definitely not OK with bumping max-line-length above 80 chars.
I thought we were already requiring docstrings even for private methods / functions / classes, but would be fine with dropping that requirement.
max-nested-blocks and max-bool-expr look arbitrarily low:  if it doesn't cause a barf on current code, we can leave it be.
Are the new values for exclude-protected based on our usage, or just defaults?

Thanks
max-line-length=100 is strange to me
I prefer docstrings everywhere, since it helps other people understand our thoughts
I didn't try the new config yet (or at least don't remember if I did) so can't speak on the barf
RE: exclude-protected, these are just values from pylint --generate-rcfile

What about expected-line-ending-format for Unix only? w00t
Are you not excited by jobs=1?

max-line-length=100 is strange to me

Violates PEP8.

I prefer docstrings everywhere, since it helps other people understand our thoughts

I think the "full-court press" docstring style (intended to generate Sphinx markup) is less than helpful for non-API methods (which I don't think should be in Sphinx, either).

I didn't try the new config yet (or at least don't remember if I did) so can't speak on the barf

I'm definitely against introducing new dogmatic opinions without testing their impact first.

What about expected-line-ending-format for Unix only? w00t

If we ever get Windows contributors, we'll need to allow them to run the linter without barfing on their own machines.  Maybe do this check only in Travis, and document that they need to use `core.autocrlf'.

Are you not excited by jobs=1?

Not much point in 1. :)

a [SPELLING] section was enabled for spellcheck (via python-enchant)

I'm not a big fan, especially given that we'd need to be checking in the dictionary.

Not much point in 1

I just meant the feature. We should crank it up to 11.

Not much point in 1

I just meant the feature. We should crank it up to 11.

I'll send one or two PRs with slow updates to the new defaults (and I'll re-org the sections to match the new output order)


Fetched in submodule path 'libs/aliyun/iotkit-embedded', but it did not contain e6bd..

git submodule update --init                                                                                !7500
error: Server does not allow request for unadvertised object e6bd3556039538ac504c005f0c31dbdd0e906658
Fetched in submodule path 'libs/aliyun/iotkit-embedded', but it did not contain e6bd3556039538ac504c005f0c31dbdd0e906658. Direct fetching of that commit failed.

1. SDK version（SDK 版本）
{
git log -n1
commit 2d493e48b1413736eb8decdea38cdd1461d8ab4b
Author: Neucrack<EMAIL_ADDRESS>Date:   Thu Nov 8 16:52:28 2018 +0800
optimize mqtt demo

}

2. In what kind of operation problems appear, and how to reproduce the problem ?（什么样的操作步骤问题会出现，是否是稳定复现，如何复现问题？）
{
git clone https://github.com/Ai-Thinker-Open/GPRS_C_SDK.git --recursive
git submodule update --init
also fails with the same error as above
}

full text from clone:
git clone https://github.com/Ai-Thinker-Open/GPRS_C_SDK.git --recursive                                                              !7497
Cloning into 'GPRS_C_SDK'...
remote: Enumerating objects: 21, done.
remote: Counting objects: 100% (21/21), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 4030 (delta 7), reused 17 (delta 6), pack-reused 4009
Receiving objects: 100% (4030/4030), 30.09 MiB | 243.00 KiB/s, done.
Resolving deltas: 100% (1917/1917), done.
Submodule 'libs/aliyun/iotkit-embedded' (https://github.com/aliyun/iotkit-embedded.git) registered for path 'libs/aliyun/iotkit-embedded'
Submodule 'libs/gps/minmea/src' (https://github.com/kosma/minmea.git) registered for path 'libs/gps/minmea/src'
Submodule 'libs/lvgl/src' (https://github.com/littlevgl/lvgl.git) registered for path 'libs/lvgl/src'
Submodule 'platform/csdk' (https://github.com/Ai-Thinker-Open/GPRS-C-SDK-LIB.git) registered for path 'platform/csdk'
Cloning into '/tiamat/git/GPRS_C_SDK/libs/aliyun/iotkit-embedded'...
remote: Enumerating objects: 23458, done.
remote: Total 23458 (delta 0), reused 0 (delta 0), pack-reused 23458
Receiving objects: 100% (23458/23458), 72.06 MiB | 260.00 KiB/s, done.
Resolving deltas: 100% (7783/7783), done.
Cloning into '/tiamat/git/GPRS_C_SDK/libs/gps/minmea/src'...
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 524 (delta 0), reused 1 (delta 0), pack-reused 520
Receiving objects: 100% (524/524), 198.56 KiB | 325.00 KiB/s, done.
Resolving deltas: 100% (332/332), done.
Cloning into '/tiamat/git/GPRS_C_SDK/libs/lvgl/src'...
remote: Enumerating objects: 41, done.
remote: Counting objects: 100% (41/41), done.
remote: Compressing objects: 100% (30/30), done.
remote: Total 11332 (delta 15), reused 24 (delta 11), pack-reused 11291
Receiving objects: 100% (11332/11332), 9.83 MiB | 274.00 KiB/s, done.
Resolving deltas: 100% (9000/9000), done.
Cloning into '/tiamat/git/GPRS_C_SDK/platform/csdk'...
remote: Enumerating objects: 320, done.
remote: Total 320 (delta 0), reused 0 (delta 0), pack-reused 320
Receiving objects: 100% (320/320), 160.43 MiB | 311.00 KiB/s, done.
Resolving deltas: 100% (142/142), done.
error: Server does not allow request for unadvertised object e6bd3556039538ac504c005f0c31dbdd0e906658
Fetched in submodule path 'libs/aliyun/iotkit-embedded', but it did not contain e6bd3556039538ac504c005f0c31dbdd0e906658. Direct fetching of that commit failed.

merge #266 to master!
$ hub pr checkout 266
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0
Unpacking objects: 100% (4/4), done.
From github.com:Ai-Thinker-Open/GPRS_C_SDK
 * [new ref]         refs/pull/266/head -> lsaavedr-update_iotkit-embedded
M	libs/aliyun/iotkit-embedded
M	libs/gps/minmea/src
M	libs/lvgl/src
M	platform/csdk
Switched to branch 'lsaavedr-update_iotkit-embedded'
[  8:31AM ]  [ thoth@thoth-GS70-stealth:~/git/GPRS_C_SDK(lsaavedr-update_iotkit-embedded✗)(ruby-2.2.4) ]
 $ git submodule update --init
Submodule path 'libs/aliyun/iotkit-embedded': checked out '26fe75c8788e7e265596164632bc052838dcd38c'
Submodule path 'libs/gps/minmea/src': checked out 'cd27e72970cd50b46e9c95c1c0076a49c1ceaf33'
Submodule path 'libs/lvgl/src': checked out '59464fa41beff11780219b1b2eaae0d855d8d8ec'

this has not moved to master and remains an issue

I have problem: git clone https://github.com/Ai-Thinker-Open/GPRS_C_SDK.git --recursive
...
error: no such remote ref e6bd3556039538ac504c005f0c31dbdd0e906658
Fetched in submodule path 'libs/aliyun/iotkit-embedded', but it did not contain e6bd3556039538ac504c005f0c31dbdd0e906658. Direct fetching of that commit failed.

For anyone not familiar with git enough to checkout a pull request try these steps if this hasn't been merged.

Github has also written a wrapper for git that makes this a bit easier:
https://hub.github.com/
so the above becomes
hub pr checkout 266

That being said, you should understand what is going on in the manual method before relying on that shortcut.


Improve Donate Page Dark Mode

Describe the bug
After doing in Dark Mode the donate Webpage isn't being dark, it is since in white mode
Expected behavior
It also should be in dark mode,by doing it in Dark Mode
Screenshots
If applicable, add screenshots to help explain your problem.

please assign this issue to me

Hey there! I'm Ashutosh Kumar, a full-stack MERN web developer. With experience in numerous successful MERN stack  projects, I excel in  HTML, CSS,JavaScript,C, C++,jQuery, Node.js, React.js, Bootstrap, Tailwind, Express, MongoDB, API,GraphQL,WebRTC.
You can find me on LinkedIn : https://www.linkedin.com/in/ashutosh-kumar-60b262251/
GitHub : https://github.com/Ashutosh-0506.
Looking forward to contributing to GSSOC 2024!


[DEN-248] Fixed empty RE policy bug, simplified RE example for clarity

@stevenpaz these changes look good to me, approving as is.
Do you want to update all the 0.4.4 references (mostly in example files I believe) to 0.4.6 if you are going to do a new release?
Did you check whether go generate would have any documentation updates due to the validation changes?

The validation changes did not change the docs. My modification of the example did though.


[Bug]: Startup parameter ODC_APP_EXTRA_ARGS does not work as expected

ODC version
4.3.0
OB version
<IP_ADDRESS>
What happened?
When I was developing in integrating ODC in ob-operator, I found that the startup argument ODC_APP_EXTRA_ARGS not working.
(The following IP address is an internal mock one)
I set ODC_APP_EXTRA_ARGS="--odc.integration.bastion.account.query.request-url='http://<IP_ADDRESS>:18084/api/v1/auth/${account_verify_token}' --odc.integration.bastion.enabled='true' --odc.integration.bastion.account.auto-login-enabled='true' --odc.connect.database.sync.block-internal-database='false' --odc.database.schema.sync.exclude-schemas.ob-mysql=''"
And I found that the sun.java.command indeed contains the extra args in odc.log.

But the parameters do not work at all. I need to update them in the metadata database and restart odc server to make them work as expected.
What did you expect to happen?
Parameters set in ODC_APP_EXTRA_ARGS work as expected. The bastion link could be opened normally.
How can we reproduce it (as minimally and precisely as possible)?
Run odc server with environment variable ODC_APP_EXTRA_ARGS set to --odc.integration.bastion.enabled='true' --odc.integration.bastion.account.auto-login-enabled='true', visit URL http://xx.xx.xx.xx:8989/#/gateway/test and you will found "session expired, please log in again". After login, visit the above URL again and you will get another error message.

If the parameters were set in metadata database and restart the odc server, the problem disappeared.
Anything else we need to know?
No response

pass


Swashbuckle Integration

I am trying to use the Swashbuckle Integration as defined here 'https://github.com/dotnet/aspnet-api-versioning/wiki/Swashbuckle-Integration' for asp.net core. However I get the following error when compiling the example:
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1061	'ApiDescription' does not contain a definition for 'IsDeprecated' and no accessible extension method 'IsDeprecated' accepting a first argument of type 'ApiDescription' could be found
I have also tried the example here -https://github.com/dotnet/aspnet-api-versioning/blob/master/samples/aspnetcore/SwaggerSample/SwaggerDefaultValues.cs but get the same error.
What is it that I'm missing?

One or more of the following must be true:

You did not reference  Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer
You did not include using Microsoft.AspNetCore.Mvc.ApiExplorer; (I'm assuming C#)
You're using an older library version before IsDeprecated was introduced (you didn't say which version you're using)

Hopefully, one of those leads you to the solution; otherwise, I'm happy to help continuing to resolve the issue.

@commonsensesoftware  thank you for your reply. It was the first one. Please can the need for that package be added to the wiki here - https://github.com/dotnet/aspnet-api-versioning/wiki/Swashbuckle-Integration in order to help others.

I had hoped it would have been clear from the landing page and example project, but I'm happy to add more documentation to the wiki. Glad that solved your issue. Thanks for the feedback.


Change memory in manifest.yml to 256

256MB of memory keeps us in the free tier, which is where we want to be.

Done.

Closed via commit 5f205defb438cc32b84eda660a7e7463d8e1b794
@ragudiko FYI i'm happy to review any PRs


CI test runs crash on forks because they do not use the github-action secrets provided

Source name
All sources while doing CI runs on forks.
Make sure that

[x] I checked the README in the source folder
[x] If I have problems with the credentials I checked the credentials docs and troubleshooting

Describe the bug
Please describe the bug. If possible provide us:

name of the dlt source causing the problem: all
name if the dlt resource causing the problem: all
which destination you are loading into: all
any stack traces and logs you can share: See https://github.com/dlt-hub/verified-sources/actions/runs/5904871862/job/16017862670?pr=246#step:9:13903

I observed two defects:

the CI test runs cannot find the secrets I provided
when an existing source is changed the CI does not run only the changed source but a multitude of sources – maybe all? When a new source is added, however, it runs only the new source.

To Reproduce
Steps to reproduce the behavior:

make any change in an existing connector or add a new connector
add the secret for that source to the DLT_SECRETS_TOML
make a PR in a fork of the verified-sources repository
watch it crash 💥

Expected behavior
The CI run should pick up the secrets I provided in the github settings of my fork.
Stack traces and other evidence
Please paste any stack traces, logs and screenshots. Mind that the issue is public!
    dlt.common.configuration.exceptions.ConfigFieldMissingException: Following fields are missing: ['private_app_password'] in configuration with spec ShopifySourceConfiguration
E           	for field "private_app_password" config providers and keys were tried in following order:
E           		In Environment Variables key SHOPIFY__SOURCES__SHOPIFY_DLT__SHOPIFY__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key SHOPIFY__SOURCES__SHOPIFY_DLT__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key SHOPIFY__SOURCES__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key SHOPIFY__PRIVATE_APP_PASSWORD was not found.
E           		In secrets.toml key shopify.sources.shopify_dlt.shopify.private_app_password was not found.
E           		In secrets.toml key shopify.sources.shopify_dlt.private_app_password was not found.
E           		In secrets.toml key shopify.sources.private_app_password was not found.
E           		In secrets.toml key shopify.private_app_password was not found.
E           		In Environment Variables key SOURCES__SHOPIFY_DLT__SHOPIFY__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key SOURCES__SHOPIFY_DLT__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key SOURCES__PRIVATE_APP_PASSWORD was not found.
E           		In Environment Variables key PRIVATE_APP_PASSWORD was not found.
E           		In secrets.toml key sources.shopify_dlt.shopify.private_app_password was not found.
E           		In secrets.toml key sources.shopify_dlt.private_app_password was not found.
E           		In secrets.toml key sources.private_app_password was not found.
E           		In secrets.toml key private_app_password was not found.
E           Please refer to https://dlthub.com/docs/general-usage/credentials for more information

See https://github.com/dlt-hub/verified-sources/actions/runs/5904871862/job/16017862670?pr=246#step:9:13903
On a side note, I am surprised that not only the changed source runs but also others.

Run sources_list="chess facebook_ads google_sheets notion shopify_dlt "

Running environment

OS: [e.g. Linux, MacOs, Windows]
dlt Version: 0.3.11
Virtualization / Runner [e.g. local, VM, Docker, Composer, Kubernetes]
Orchestrator / Deployment platform [e.g. Airflow, github actions, Astronomer, Google Composer, Codespaces]

Additional context
I've got a private chat with @rudolfix already running.

@willi-mueller thanks! so it seems the way I try to run our CI for forks is wrong and we need something else. will ping you back with updates


No data in practice sessions.

Describe the bug
Basically if you'r doing a race, you do have the telemtry outputting nicely.
But as soon as you jump into a practice session, there is no data coming out of the listeners.

Hey @iamisti I noticed you closed this issue. Sorry I have not been able to put much time onto the project lately. Has this been resolved by you?

Problem solved, it was on my end.


Test managed Grafana on EKS

Towards: https://github.com/giantswarm/roadmap/issues/2673
Ensure that Grafana can run as managed app on imported and adopted EKS clusters.

I guess this should be done prior to https://github.com/giantswarm/roadmap/issues/2886

grafana finally deployed on the sample-customer cluster on the snail installation :
zirco@Zirko-laptop:~/Templates$ k get pods -n kube-system --kubeconfig=sample-customer.kubeconfig | grep grafana
grafana-7d6bc44c46-8ggd7                                        1/1     Running   0          3h53m

It's also working as intended when trying to access it :

Obviously without any prometheus and/or dashboards, there aren't a lot of things to see.

I guess one can ensure that grafana is working on EKS imported cluster. What are your thoughts @QuentinBisson ?

Good 🚀

Did you test on a CAPA managed EKS?

Did you test on a CAPA managed EKS?

Not yet, I wanted to first ensure Loki and Promtail are working on the same imported EKS cluster and use grafana to ensure this before moving to CAPA for both :)

Sure, sorry :D

tested on a WC on golem with provider eks and working as well :
zirco@Zirko-laptop:~$ k get pods -n kube-system | grep grafana
grafana-8d99d97f7-zrzmh                                        1/1     Running     0          156m


Jira plugin: collect the epic issue in an issue's epic link

Description
Many Jira users use epic to represent 'strategy'. For example, any issue created under an epic is considered "Strategic", otherwise "Non strategic". With the epic issue, we can calculate the percentage of issues in each category: "Strategic", "Non-strategic", and "Bug fixing", so that users know the task allocation.
Background
The current Jira plugin only collects issues by board. However, the epics that issues belonging to may not be collected.
For instance, a user collected Jira board 76 and got issue-1, issue-2 and issue3. Issue-1's epic link is issue 4 (an epic issue). As a result, issue-4 is not collected and will not appear in the issues table in the domain layer.
Describe the solution you'd like
Jira plugin should also collect the epics that issues belonging to.

collect all epic issues referenced by existing issues
used to showing epic detail, no need to build board/epic relationship

@klesh @mindlesscloud
Epic is just one of standard issue type in Jira (core). Jira installs an official plugin to provide the special ability for Epic out of box. This plugin also create some custom key within JIra and lock them. Though those key are customized, Epic has been a key feature of JIra, and we should seem those keys as original attributes of issue object.
Ideally, in my opinion, we can follow Jira's pattern, and store epic as normal issue, but add epic related keys into issue object.

@leglars No problem, since we had already collected jira_issues.epic_key, what we left to do is to collect those epic issues and store them into the jira_issues table as well,  Am I understand it correctly? @Startrekzky

@leglars No problem, since we had already collected jira_issues.epic_key, what we left to do is to collect those epic issues and store them into the jira_issues table as well, Do I understand it correctly? @Startrekzky

Correct. I guess the flow is:

Collect the epic issue when a Jira issue's epic_key is not empty.
Store the 'epic-type' issues should be stored in tables in all 3 layers: _raw_jira_api_issues, _tool_jira_issues, issues
a. Make sure the epic issues are de-duplicated.
b. Make sure the epic issues are enriched and converted just like other issues.

Please let me know if the flow needs to be polished. @klesh @keon94

@klesh is this still slotted for the v0.12.0 release?

Hi @keon94 , @mindlesscloud  is working on this issue already.

Hi @keon94,  @mindlesscloud and I had discussed this matter during Sync Up, he would like you to take over, and he will post his solution here. Would you like to keep working on it? Thanks

@keon94 No, you can take it, but there is one thing I would like to draw your attention to. The epic issues should not appear in the table _tool_jira_board_issues and board_issues if it does not belong to the board. Maybe we need another tool layer table to track epic issues.

@klesh, is this being worked on? If not, I can take this one

cc @CamilleTeruel

@keon94 Hi Keon, thanks for putting together this proposal. I'll summarize my understanding and questions below.

Right now we collect regular Jira issues by board. A regular Jira issue that belongs to an epic issue will have a non-emptyepic_key field.
Your plan first collects regular Jira issues as before. Then a new collector gathers all non-empty epic_keys from _tool_jira_issues table, and call agile/1.0/epic with those epic keys.
Then a new extractor transforms raw epics to _tool_jira_issues, _tool_jira_board_issues, and etc.
The same old converter transforms tool layer tables to domain layer tables

Questions:

Can you elaborate a bit more on the optimization you mentioned in your point 1? Having trouble understanding that part.
How do we figure out which board an epic belongs to and create entries in _tool_jira_board_issues accordingly? Does agile/1.0/epic give out this info?
Where are the dupes that need to be dealt with in the new extractor coming from?

@hezyin
You understood correctly, but for (3), we shouldn't need to extract the raw epics into _tool_jira_board (as mentioned by @mindlesscloud as well), because the regular issues extractor will already have extracted all the board-relevant epics to that table. This extractor should ideally only be dealing with epics that are not part of the board, but that are parents of issues that do belong to that board. Maybe we need a better name for the subtasks, like [Foreign/Indirect/Referenced,etc]EpicCollector/Extractor.
As far as your questions:

If we simply grab all the epics by IDs (epic-key field in_tool_jira_issues ) that's also going to return those epics that belong to the board. But these epics will already have been processed by the IssueCollector (and later IssueExtractor). We can optimize this so that we only get those that are not from the board. We should be able to run a DB Join query on _tool_jira_board_issues and _tool_jira_issues to only get the epic IDs of those issues whose epic issue-IDs are not in the _tool_jira_board_issues (issue_id key) table. This might probably be a complicated query though.

If we run the optimization in (1), we know we're dealing with epics that are not part of the board. My understanding from this request is that we won't be mapping these epics to the boards table. Separate pipelines involving these epics' boards will need to be run to get them on that table.

The collector will be getting the epics of many issues. Some issues may share the same epic. So the list of epic IDs that we get from the query might contain duplicates. We should be able to take care of this on the query itself though.

@keon94 Did you mean _tool_jira_board_issues by _tool_jira_board in the following sentence?

@hezyin You understood correctly, but for (3), we shouldn't need to extract the raw epics into _tool_jira_board (as mentioned by @mindlesscloud as well), because the regular issues extractor will already have extracted all the board-relevant epics to that table.

Thanks for the clarification. Let me summarize my latest understanding to make sure everyone involved in the thread is on the same page.

If an epic issue belongs to the Jira board that we collect regular issues from, then they're already collected by the current implementation. This issue (#1681) is really about collecting (foreign) epic issues that don't belong to the Jira board themselves but are linked to regular issues from that Jira board.

When we collect the epic issues by going through the epic_key field in _tool_jira_issues, we can skip the ones that actually belong to the Jira board we collected. This can be checked by querying _tool_jira_board_issues.

The dedupe step can be done at the collector stage (when going through the epic_key field) instead of the extractor stage.

If foreign epic issues don't have corresponding entries in _tool_jira_board_issues, then we need to be careful when writing SQL queries for dashboards since right now many SQL queries use a board as a filter. @Startrekzky

Please advise if there's any misunderstanding in the summary above. @klesh @Startrekzky @terrymanu @keon94

@keon94 Did you mean _tool_jira_board_issues by _tool_jira_board in the following sentence?

Yes, I meant the _tool_jira_board_issues table.

Hi @hezyin @keon94 I think we're on the same page about the epic collection and enrichment flow.
In terms of the following point, it's a design that I'm already aware of. But this won't be a problem, as the query logic will be 'boards' -> 'board_issues' -> 'issues (non-epic)' -> 'issues (epic)'. In this way, we can use boards to filter non-epic issues and get the epic that these issues belong to. As a result, we can get epic-level metrics, ie. strategic and non-strategic issue ratio.

If foreign epic issues don't have corresponding entries in _tool_jira_board_issues, then we need to be careful when writing SQL queries for dashboards since right now many SQL queries use a board as a filter. @Startrekzky

Please advise if there's any misunderstanding in the summary above. @klesh @Startrekzky @terrymanu @keon94

Closed by #2401


CDPS-937: Adding prisonId to sync telemetry events

Codecov Report
Attention: Patch coverage is 95.83333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 84.97%. Comparing base (2d271b3) to head (07d94e7).

Files with missing lines
Patch %
Lines

...son/service/event/publish/TelemetryEventService.kt
89.47%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #130      +/-   ##
============================================
+ Coverage     84.77%   84.97%   +0.20%
- Complexity      655      662       +7
============================================
  Files           100      100
  Lines          2062     2097      +35
  Branches        193      196       +3
============================================
+ Hits           1748     1782      +34
  Misses          191      191
- Partials        123      124       +1

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


connect ETIMEDOUT

When I want to run the project, there is an error. I tried proxy, firewall, etc., but there is no solution. What are the possible reasons and solutions?
FetchError: request to https://discord.com/api/v10/applications/1118079193654251581/commands failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
at ClientRequest. (file:///D:/Users/Desktop/discord-example-app/node_modules/node-fetch/src/index.js:108:11)
at ClientRequest.emit (node:events:525:35)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
erroredSysCall: 'connect'
}

Same here. It could be a problem specific to (mainland) Chinese network conditions. I have tried using proxy in Terminal but it seems have no use.

Hi! Here's how I fixed the problem.
This request does not follow the system proxy rules, so it wouldn't work even if you have enabled global proxy. You can turn on the TUN mode in the proxy software to take over these traffics and realize network card level global proxy.

Seems like this is resolved :)


Jesse: Watch suntec-elektro.de

Jesse requests the watch of the watch_keyword suntec-elektro\.de. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

suntec-elektro\.de has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Using pyresttest as library and trying to execute two or more yaml files in parallel, causes issues.

Using pyresttest as library and trying to execute two or more yaml files in parallel, causes issues.
steps:
try to run multiple yaml files in parallel.
result:
test runs interfere with each other and cause test runs to fail.

@akshay059, could you explain more on how you ran the tests? Are the
tests(response) independent of each other?
On Tue, 29 Mar 2016 at 12:47 akshay059<EMAIL_ADDRESS>wrote:

Using pyresttest as library and trying to execute two or more yaml files
in parallel, causes issues.
steps:
try to run multiple yaml files in parallel.
result:
test runs interfere with each other and cause test runs to fail.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/svanoort/pyresttest/issues/183

I invoked it from a view in a django project, there were two yaml files that ran in parallel which caused the issue. Tests in those files were independent of each other.

I think the requests are dependent on each other, can you elaborate on the
api's(is it DB changes)?
Regards,
Pradeep. S
On Tue, 29 Mar 2016 at 23:12 akshay059<EMAIL_ADDRESS>wrote:

I invoked it from a view in a django project, there were two yaml files
that ran in parallel which caused the issue. Tests in those files were
independent of each other.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/svanoort/pyresttest/issues/183#issuecomment-203021851

Both yaml files just do a lot of get requests with different params and validate the response using a  common json schema file.
When I put lock on the call to main, everything works correctly, although requests are processed one by one. So I am pretty sure it is a threading issue.
I moved all the code to a class file from the module, which worked when using completely independent test files, but again failed when executing yaml files which used same json schema files.
I think issue is where we are using cd but I am not sure.

@svanoort - I think we need your help here.

@akshay059  I think you are correct - the os.chdir operation here changes the working directory completely, and is used in the cd operation.  I've made an attempt to correct this by adding a lock around just the pieces using it.  It's hacky (better to drop the CD utility already and make all paths absolute to the correct locations, I think), but it should resolve it.
Please give this version of source a try and let me know if it works: https://github.com/svanoort/pyresttest/pull/186
Never thought I'd see threading issues in python code!  :smile:
@spradeepv  As always, thank you for assisting with questions and investigating issues.  I am adding a mention to the changelog for this, because it contributes even more toward making big features/enhancements possible than writing code would.

@svanoort No issueses. Happy to help!!
On Wed, 30 Mar 2016 at 18:40 Sam Van Oort<EMAIL_ADDRESS>wrote:

@akshay059 https://github.com/akshay059 I think you are correct - the
os.chdir operation here changes the working directory completely, and is
used in the cd operation. I've made an attempt to correct this by adding a
lock around just the pieces using it. It's hacky (better to drop the CD
utility already and make all paths absolute to the correct locations, I
think), but it should resolve it.
Please give this version of source a try and let me know if it works: #186
https://github.com/svanoort/pyresttest/pull/186
Never thought I'd see threading issues in python code! [image: :smile:]
@spradeepv https://github.com/spradeepv As always, thank you for
assisting with questions and investigating issues. I am adding a mention to
the changelog for this, because it contributes even more toward making big
features/enhancements possible than writing code would.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/svanoort/pyresttest/issues/183#issuecomment-203424411

@svanoort Adding lock to cd worked :)
Thanks for the help :+1:
@spradeepv thanks :+1:


bug: Card images in iOS are deformed

Type: bug
Ionic Version: 2.x
Platform: ios 9 webview
I have created a list of cards using ion-card and *ngFor. In google chrome the ionic serve --lab command works fine in all platforms. However, when using ionic view to test my app on actual devices, Images inside my card are deformed on an iOS device, but not on android. Since I wanted to show a loading on images until they are completely loaded I have used ion-image for my images like this:
<ion-img [src]="img.src"></ion-img>
  <ion-spinner></ion-spinner>

and  in scss file the following code:
.img-loaded + ion-spinner {
  display:none;
}

All my images come from a server and they are all 500x500 large

don't use ion-img except inside virtualscroll.  Just use a standard img [src]

With a standard img [src] how can I have lazy loading?

that's something to ask on the ionic forums, I'm not sure.  I just know that the docs say that ion-img is currently for use in virtualscroll lists only and even in that scenario I have found it to be a complete mess at present.
If ion-img is turned into a generic lazy-loading img tag then it would be awesome but at the moment it's not there.

Thanks
So right now ion-img is a mess and is a work in progress, right?

that has been my experience trying to use it yep.  I think the ionic guys are probably focusing on getting fundamentals all in place before they loop back to some of these really nice but not critical things like ion-img.  There are a few issues already raised for it if you search on here.

Hello everyone! Thanks for using Ionic! At this time ion-img should be only used in virtualScroll but there is an issue open to make it work outside of virtual scroll. Once we are in stable we will start to focus on features like that. Thanks again!


Manifest merger failed : uses-sdk:minSdkVersion 21 cannot be smaller than version 22 declared in library

I am trying to make example project work. And unfortunately I can't.
I see the example project was built using Unity 2019.1.19f1 which uses 'API level 21' as Minimum API level.
I have spent some time on trying to set up the environment in the same way, and it just doesn't work.
Seems like API Level 21 has been deprecated.
My question is, is there any chance the library will be able to use API level 22 as its minimum sdk version?

I was able to fix this myself (I am mostly a Unity developer and not familiar with Android Studio but here is how I did it:)

In Android Studio use Ctrl + Shift + F on the Project tab (usually seen on top left where you can see all the project files)
Search for minsdk
This took me to the build.gradle file
In build.gradle, you can see

   ext {
        buildToolsVersion = "31.0.0"
        minSdkVersion = 21
        compileSdkVersion = 31
        targetSdkVersion = 31
        ndkVersion = "21.3.6528147"
    }

In this, you want to change minSdkVersion = 21 to minSdkVersion = 22
However, this has now led me to this error which I am looking into Manifest merger failed : Apps targeting Android 12 and higher are required to specify an explicit value for android:exportedwhen the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

@ROBYER1 Yep.. aand this is where I stuck too :D
Moreover, I managed to add "android:exported" in every missing place I could find, (that is unity library manifest). Unfortunately I then get the same error but for some mysterious "service" thing. Although I cannot find any "service" keyword in my android project...

What's the exact error for the service thing? Maybe we can figure this out together if you share the error?

@ROBYER1 Yep.. aand this is where I stuck too :D Moreover, I managed to add "android:exported" in every missing place I could find, (that is unity library manifest). Unfortunately I then get the same error but for some mysterious "service" thing. Although I cannot find any "service" keyword in my android project...

Where did you add android:exported?
Also what is the error about service?

Okay so I haven't fixed the emulator running issue but I don't need that anyway - I got it running on device, I had to do the following:
In Unity Project Settings > Player, set il2cpp instead of mono and ticked ARMv7 and ARM64
In Android Studio I had il2cpp errors about NDK so I installed the matching NDK that Unity used in Android Studio SDK manager
On build and run, the app would still have the error about the Metro server not running, I ran this command to get past that:
adb reverse tcp:8081 tcp:8081 from:  https://stackoverflow.com/a/46250725

In my project I use minSdkVersion = 26 and everything works fine, I can’t understand what is the problem with building a Unity project with this flag and running it in RN?

In my project I use minSdkVersion = 26 and everything works fine, I can’t understand what is the problem with building a Unity project with this flag and running it in RN?

I would close this issue if I was the owner, if anyone follows my steps above they will get past any unusual errors in the Example app. However the real issue now is that the app runs and if I try to open the Unity window a second time it always crashes - I filed a bug here please see
https://github.com/azesmway/react-native-unity/issues/34

Hi @ROBYER1,
I have the same problem (i have a lot of problem): Manifest merger failed : Apps targeting Android 12 and higher are required to specify an explicit value for android:exported
I followed your tread and i put  android:exported in unity export manifest but nothing.... i have the same errror....
any suggestion?
your build work?
Thanks

ok now build!
i changed
->
ext {
buildToolsVersion = "31.0.0"
minSdkVersion = 22
compileSdkVersion = 31
targetSdkVersion = 31
ndkVersion = "21.3.6528147"
}
with ->
ext {
buildToolsVersion = "30.0.0"
minSdkVersion = 22
compileSdkVersion = 30
targetSdkVersion = 30
ndkVersion = "21.3.6528147"
}

Great! This can probably be closed now?

Yes I think....
you have any suggestion for this problem?
https://github.com/azesmway/react-native-unity/issues/39#issuecomment-1225519321
Thanks


🤖  Reenable Dependabot for daap- containers

User Story
As a service team
I need dependencies to be kept up to date
So that we don't accumulate avoidable technical debt
And security patches get quickly applied to our product
Value / Purpose
Previously we switched off dependabot - it was raising a lot of PRs that failed our linter, and we weren't keeping up with it.
However keeping our dependencies up to date is more important than enforcing lint rules, so we should switch it back on.
Proposal
First see if we can use https://github.com/marketplace/actions/dependabot-changelog-helper to ensure that dependabot PRs are easily mergable.
If this doesn't work, we can disable the lint rule that forces every version update to have a changelog entry.
Then revert https://github.com/ministryofjustice/data-platform/commit/bb1c035a27def56459f6ee70277e986a483b3b4a
We may want to consider changing the schedule so that all the dependabot PRs come in on one day of the week. That way we can focus on reviewing them on that day.
Additional Information
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
Definition of Done

[ ] Dependabot is enabled
[ ] Dependabot PRs don't fail the checks every time
[ ] Everyone on the team knows how to manage dependabot PRs

No longer relevant


update eoxcloudless to 2021

@Dorothyrono anything else you want to me adjust? Thanks

Checked it is okay now.  We can merge
sorry for delay


Display empty raw events as "0x"

https://explorer.dev.oasis.io/mainnet/sapphire/tx/0x3e6a8066a7c1866a416c0b18fe765f245b2c0cd1317d361efb6495ec6239f551
https://explorer.sapphire.oasis.io/tx/0x3e6a8066a7c1866a416c0b18fe765f245b2c0cd1317d361efb6495ec6239f551/logs

Before
After
Blockscout

I'm not sure, was this really the requirement?


Add celonis-ems documentation & related images

@capono - Thanks for your submission. Would you take a moment to sign the CLA? After you do so, we can route this PR to the appropriate assignee.
Thanks!
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@capono - Thanks for your submission. Would you take a moment to sign the CLA? After you do so, we can route this PR to the appropriate assignee.
Thanks!
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

@ShannonLeavitt  - this PR is due to the Submission of our Connector in ISV-Studio following question came upon agreeing the CLA.
(i) why we need additional terms for the submission of Documentation when this is already covered under the original Platform Partner Agreement; and (ii) why we’re being asked to agree to the Contribution License Agreement as it does not seem to bear any specific relation to the Connector.

@capono,
The Contributor License Agreement (CLA) is an automated check that must be completed during the Validation phase of the pull request process in the public repos. A PR can't be reviewed or merged until all checks are successfully completed.
See Pull request processing for more info.


Delete the RTFs files from BaseTools\UserManuals (Bugzilla Bug 1626)

This issue was created automatically with bugzilla2github
Bugzilla Bug 1626
Date: 2019-03-14T22:21:29+00:00
From: BobCF
To:   BobCF
CC:   edk2+bugs+int+994+563148131503455288, yonghong.zhu
Last updated: 2019-03-20T23:07:21+00:00

Comment 6802
Date: 2019-03-20 23:07:21 +0000
From: Yonghong Zhu <<yonghong.zhu>>
Bob will work on it.

Comment 6726
Date: 2019-03-14 22:21:29 +0000
From: BobCF

Industry Specification: ---
Releases to Fix: EDK II Master
Target OS: ---

Delete the RTFs files from BaseTools\UserManuals after finish BZ 1625#


[#1177] improvement: Reduce the write time of tasks

What changes were proposed in this pull request?
Use callback and queue to optimize the write time.
Why are the changes needed?
Fix: #1177
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI passed.

Codecov Report

Merging #1179 (35a9690) into master (2ee11a9) will increase coverage by 0.52%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1179      +/-   ##
============================================
+ Coverage     53.63%   54.15%   +0.52%
+ Complexity     2582     2109     -473
============================================
  Files           391      319      -72
  Lines         22407    14448    -7959
  Branches       1875     1314     -561
============================================
- Hits          12019     7825    -4194
+ Misses         9681     6204    -3477
+ Partials        707      419     -288

see 73 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


QRenderDoc crash on Fedora 24

QRenderDoc crash during startup on Fedora 24.
Apparently the crash happens during the window creation, attemping to call glXGetVisualFromFBConfig(...).
At that point the debugger shows that the glhooks table is uninitialized and all the pointers are set to 0x0, and setting a breapoint on PopulateHooks reveals that the function is not called at all.
I attached the stack trace recovered from gdb.
qrenderdoc_crash.txt
Matteo

This looks like maybe a clash between recent fixes to the GL hooking code and Qt, it's picking up some of the exported symbols that are only intended for hooking external applications not really used for internal symbols.
It should be fixable, but honestly at this point it's probably not worth reporting bugs against qrenderdoc - it's barely runnable and even if you get it working, it has no usable functionality. Given the current status it's just not mature enough to be worth tracking individual bugs.

Funny, I was just about to report this issue and then @Corralx showed up and already did it. This is also crashing for me on Arch Linux compiled with gcc (gcc (GCC) 6.2.1 20160830) with the exact same stacktrace.

Well that's no great news.
Since I've used it with success on Windows on my personal projects, I was just about the test it at work to see if it was feasible on Linux.
I understand that being alone, maintaining all the platform/API combinations is really hard and Linux is not a priority in the 3D graphics world :)
I'll see what I can do to contribute onto the Linux/OGL path.
May I contact you privately at this point to see the state of the work and what could be done for it?
Matteo

I would prefer if the roadmap were open so that contributors like us could just choose to tackle random issues here and there.

Yeh you can always email me if you want to, but I don't think there's any reason to take this privately. Right now though there's not a specific roadmap - it's just "get everything ported to Qt, doing some clean up & refactor along the way".
Getting the UI up and running on linux is definitely a priority though. The survey results indicated that the next two priorities are D3D12 support and Linux native UI, so those are what I'm working on right now.
It's hard to give exact timelines as I like to stay flexible enough to respond to things when they come up and changing priorities, but I'm hoping at least there will be some basic functionality there by the start of next year. As in - not necessarily feature complete and comparable to the winforms UI, but at least usable to debug a bit.
You're welcome to PR improvements, just be aware that since the Qt UI is still pretty raw, the code will be churning a lot so there's more chance of clashes, constant rebasing and duplicated work :smile:.

Oops, well one of those commits (which github decided to double-report because I pushed to two branches) should have been for #365.
Either way, I think this is fixed now and qrenderdoc is back to being working but severely non-functional :). Let me know if it fixes it for you, or if you're still having some issues.

Thanks, I can see QRenderDoc launching correctly now.
As soon as I find time (this week I'm a bit constrained at work) I'll look into what needs to be done to take the Qt UI on par with the .NET one.


move shop menu button to fixed header

Describe the solution you'd like
On mobile devices the button for the shop navigation should move to the fixed header beside the sevice button. The search field can then extend across the entire width of the screen.
Possible solution (if any)

https://github.com/chameleon-system/chameleon-shop-theme-bundle/pull/32

The shop navigation is still next to the search field and below the service navigation in 7.0 (ok in 6.3)


chartjs cc binding issue

hi @oblomov-dev
seems like demo 148 seems not to work correctly.

seems to not do camel case to the binded variables, hence they are not interoerted correctly in chartjs
previously binidng edit syntax was /EDIT/VARIABLE
a change was made on that ??
what is the XX ??

this is ground breaking as per using expression binding on values, every place was using the /EDIT/ prefix.... :\
see below 1 + 2

thanks for checking this. there was a bug with camel case, fixed it with:
https://github.com/abap2UI5/abap2UI5/pull/917
yes i changed the name of the edit model, there was the danger when someone names an attribute in the class with the name "edit" that there will be a collision and it breaks the functionality of abap2UI5. thats why i changed to the more cryptic naming of XX, with the hope that this will not be used as a variable name. i was not aware that you use the naming somewhere, otherwise i would have warned you or would have been more careful. i put the name of the edit model now here:
https://github.com/abap2UI5/abap2UI5/blob/a31f1cbc3937dc0f437fae8dcd61e722d3e28be4/src/01/02/z2ui5_if_core_types.intf.abap#L8
is there a chance that you use this constant instead of writing the name directly? that would ensure that we don't run into incompatibilities in the future.

thanks, at least now there is an option to change it,
i guess XX do the trick but again naming variables edit in abap seems wrong, but hey, at least there is a way to change it ba k

work thanks !


simpleTensorCoreGEMM has errors in output when compiled with CUDA10 for Turing GPUs

simpleTensorCoreGEMM has errors in output(beyond the additive tolerance of 1e-5 and multiplicative tol of 1.01) when compiled with CUDA10 for Turing GPU (arch=sm_70, RTX 2080Ti)
I did not modify any datatypes in the run and both the wmma based explicit GEMM implementation and the cuBlasGemmEx call use the Tensorcores.
I am wondering what might be causing the errors beyond the specified tolerance limits?

While I can't speak to what's going on under the hood (certainly didn't look at the generated PTX) I proposed a fix in #23
Turing is actually sm_75 and targeting that during compilation resolves the issue.


[core] Move TorrentCreator to read and hash in parallel

This is a v1 refactor to test the idea of putting disk IO in one thread and SHA1 hashing in a second thread when hashing torrents.
The original implementation parallelised on each 16kB chunks as I was investigating what it would take to create merkle trees as per bittorrent v2 spec[0]. However, normal bittorrent hashing can only parallelise on entire pieces, which will require a little bit more work in order to get the same scaling benefits as the merkle tree approach received.
[0] tl;dr i don't see any benefit in implementing this as only one other client has attempted to do so, and the spec is so poor it doesn't provide a usable description of the new messages it has introduced. The only way to implement it is to look at the only pre-existing implementation and replicate the approach/layout they used for the new messages, or guess and probably be incompatible.

Closing this in favour of https://github.com/mono/monotorrent/pull/177. It's basically the same, but done better.


Maze Activity, add a 'Help' palette

A palette to give the users instructions on how to play the game would be helpful.
Initially when I used the activity, I didn't know that there were 4 players, until I went through the code.
Would a palette be better for this purpose or should I just show the instructions on the page itself overlapping the canvas until a user performs an action (lets say a click) to hide the instructions?

You're right, it's not a documented feature but it works only for device with keyboard. I guess this activity will be mainly use with the mouse or with the finger on touch devices. So I'm not sure it's so important to do help on this.
Plus, if there is a help palette, it must be localized.

(I think its helpful to leave pull requests open until they are ready to merge; you can set pull requests to "auto-squash" all commits into one if you like, or pick the option at merge time, in https://github.com/llaske/sugarizer/settings :)

it works only for device with keyboard

Perhaps a multi user mode could work with touch... eg, opposite sides/corners of the screen to tap for each person sat/stood around the screen


Add commitlint example in full_guide

Relates to this issue: https://github.com/evilmartians/lefthook/issues/122 The solution provided here doesn't stop the process of committing.
Also mentioned here https://github.com/evilmartians/lefthook/issues/110 but I find that is not the right solution as it doesn't use commitlint.

Great job! This is pretty useful!


feat: configure Netlify CMS for workshops

[x] This pull request has been linted by running npm run lint without errors
[x] This pull request has been tested by running npm run start and reviewing affected routes
[x] This pull request has been built by running npm run build without errors
[x] This isn't a duplicate of an existing pull request

Description
This PR migrates workshops from Airtable into an Eleventy file-based collection, and configures a Netlify CMS instance to manage the collection.
Steps to test

Review the Initiatives page on the deploy preview.
Check out the branch, run npm start, and navigate to http://localhost:3000/admin.

Expected behavior:

The Initiatives page and individual initiatives are properly displayed.
The workshops are editable via the CMS interface with live previews.

Additional information
See updated docs.
Note that the CMS is set to manage the dev branch currently. This will need to be changed once this PR has been tested and is merged to main.
Related issues
Not applicable.

I noticed when an image is uploaded from the local disk, the preview panel won't be able to show the image. If the image is specified via an URL, the preview responds to this change. This bug appears to be a known issue with Netlify CMS.

I noticed when an image is uploaded from the local disk, the preview panel won't be able to show the image. If the image is specified via an URL, the preview responds to this change. This bug appears to be a known issue with Netlify CMS.

I think this is actually an unrelated issue. But that's a good reminder that we need to test image uploading once this is merged into dev and make any necessary adjustments before it goes into main, and also that I need to move the images for existing workshops from Airtable to the uploads path in the images folder here.

@cindyli I made the change from Workshops to Initiatives. If the build passes this is now ready to merge to dev.

Thanks for the renaming, @greatislander.
The other change we talked at today's meeting was to add the "Event Date" to the "sort by" list for the initiatives collection. It seems this can be achieved by using the sortable_field config in the config.yml.

@cindyli I've added the configuration.

The sorting works great, @greatislander.
I checked the initiatives data in the Airtable and this PR. It seems there's at least changes to the "The Metric Society and the Unmeasurable" workshop since your last data update. Could you re-pull the Airtable data before I merge this PR? Thanks.

@cindyli I've updated the content from Airtable.


[AKS] aks enable-addons: Add new parameter --enable-msi-auth-for-monitoring to support enabling managed identity auth

Description

This PR introduces additional flag --enable-msi-auth-for-monitoring for customer to enable AKS monitoring addon with managed identity auth
Testing Guide

Enable monitoring addon with MSI auth for the new cluster
az aks create -g  <rgName> -n <clusterName> --enable-addons monitoring --enable-msi-auth-for-monitoring --generate-ssh-keys
Enable Monitoring addon with MSI auth for existing AKS cluster
az aks enable-addons -a monitoring -g <rgName> -n <clusterName> --enable-msi-auth-for-monitoring

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AKS

@ganga1980 I modified the PR title, please see if it's description is accurate

/azp run

Hi,  @jsntcy , @kairu-ms , I would like to merge this PR to meet our release schedule, can you please review this PR? I have tested all the scenarios and this PR up to date.


Improve asynchronous API (JAVA-821, JAVA-822)

Work in progress, I will add automated tests in separate commits.
SessionManager#prepareAsync is covered in JAVA-725 (#396).

I refactored session init so that setting the keyspace is non-blocking (e1e1694).
This will require a few adjustments when merging with JAVA-544, because 544 makes connection failures non-fatal when initializing a pool. However there is one exception to this, which is an InvalidQueryException when setting the keyspace at session creation (what is captured by SetKeyspaceException in this commit).

Force pushed to rebase on current 2.0 (which includes fix for 544). I've also cherry-picked the fix for 725 on this branch.


[Bug]: Paginator revisited

What happened?
I've been trying to find a good way to extend/replace the OpdsPaginator() so that it can generate the right output in json() or xml() without messing up the feeds in paginate() or using the wrong route(), but I can't seem to find it without some major code surgery.
Ideally I'd like to pass along the actual total, items per page and current page, perhaps with some callback to generate the right route for first/previous/next/last links, and then let json() and/or xml() do its work to generate the correct feed links.
Maybe we could have a public paginate() method in Opds() that could handle that, and not call some protected paginate() inside OpdsEngine()->feed() ?
How to reproduce the bug
Try to paginate
Package Version
1.0.30
PHP Version
8.2
Which operating systems does with happen with?
Linux
Notes
No response

I see, it's a good idea, I will add this feature to create a fully custom paginator ;)

A PR with a XML/JSON support is available: https://github.com/kiwilan/php-opds/pull/43

v2.0.0 ready with new paginate() method!

Thanks - seems to work fine :-)


chore: update to latest dependency versions

Codecov Report
Base: 52.96% // Head: 44.76% // Decreases project coverage by -8.19% :warning:

Coverage data is based on head (06c4ad1) compared to base (b5621b2).
Patch coverage: 35.35% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
- Coverage   52.96%   44.76%   -8.20%
==========================================
  Files           8       12       +4
  Lines        1316     2437    +1121
==========================================
+ Hits          697     1091     +394
- Misses        502     1140     +638
- Partials      117      206      +89

Flag
Coverage Δ

unittests
44.76% <35.35%> (-8.20%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/ipfs/adder.go
0.00% <0.00%> (ø)

mobile/discovery.go
30.14% <16.07%> (-0.89%)
:arrow_down:

internal/replication/replication.go
36.73% <34.56%> (-13.68%)
:arrow_down:

mobile/datahop.go
41.94% <38.73%> (-20.87%)
:arrow_down:

internal/replication/group_replication.go
41.11% <41.11%> (ø)

internal/repo/state.go
44.44% <44.44%> (ø)

internal/ipfs/ipfs.go
57.96% <52.21%> (ø)

internal/repo/repo.go
55.61% <63.63%> (-1.03%)
:arrow_down:

internal/security/security.go
64.28% <64.28%> (ø)

internal/config/config.go
75.00% <100.00%> (ø)

... and 7 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


cannot access my remote mysql

Maybe you  haven't shutdown your Firewall of  the remote server, make the port that mysql work on and try again. Welcome to communicate with me if there is still any problem.

i have test, it is okay to access remote db

it is my fault, sorry

i have found that the issue is the system cannot access to SPECIFIC DATABASE!


Update README.md

Replaced "git clone git@github.com:BunqCommunity/BunqDesktop.git" with "git clone https://github.com/BunqCommunity/BunqDesktop.git". First one didn't work for me, second one did.

The first URL is a correct. If you follow the instructions here you should be able to connect with Github using SSH. (That also means you no longer have to enter your username/password everytime which I assume you have to do now by using the https version)

I got an error with the first URL. The second URL is the URL that always works (all repos) to clone a repo to a local folder.
Github recommends https URL's for cloning. For more information: https://help.github.com/articles/which-remote-url-should-i-use/


641 product citations embeds

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #641
Test URLs:

Before: https://main--danaher-ls-aem--hlxsites.hlx.page/
After: https://641-product-citations-embeds--danaher-ls-aem--hlxsites.hlx.page/us/en/products/family/mica#citations
After: https://641-product-citations-embeds--danaher-ls-aem--hlxsites.hlx.page/us/en/products/family/cloneselect-imagers#citations

@mhaack  and @duynguyen  - if I check the lighthouse scores on main then I am getting 96 to 99, but this is giving 65 to 77.  Could this just be generally, or is this because of the citations code being injected?  Could/Should we load it on click or differently?

@davenichols-DHLS let's merge this PR and open a new issue for LHS improvement. It's because the TBT is quite high, caused by the jquery from bioz. However, it's only affecting the citations tab.

@davenichols-DHLS let's merge this PR and open a new issue for LHS improvement. It's because the TBT is quite high, caused by the jquery from bioz. However, it's only affecting the citations tab.

Excellent, I was thinking the same, I added the other tests and the main pages are great, it's just when loading bioz.  I am happy to take this.


Create site architecture diagram

Sitemap/whatever to describe the site layout. Makes it easier to structure code and links, etc.

Just to clarify, you are looking for an actual diagram and not the sitemap.xml?

Yep. Even just a whiteboard sketch or google doc or something.
A lot of the issues and suggestions for the site involve new content and where to put it, so I think an outline would be useful.
I should be able to work on this today and get some feedback from you and the group when I'm done.

:thumbsup:

Illegible refrigerator draft: ✅. On to high-tech...

Ok gave it a shot with Lucidchart. Read-only published version is here and I will post the edit link in Slack if anyone wants to add comments, notes, or edits.

Great Yoast article on site structure: https://yoast.com/site-structure-seo/

This looks great and is something that is definitely needed. The site has been improving with time, but still leaves a lot to be desired. The site is not organized, lacks content and isn't the greatest user experience. A chart like this will help solve many of those problems and provide a model to work towards.
I like how the categories are arranged by "thought", i.e. "Get Involved".
We should add an image of the lucid chart to the README, even if it isn't perfect yet, so that there is a reference for us to start working towards. Then we should start fleshing out a plan to start moving the site in that direction. As we do that we can keep iterating on this design chart.


Merge 3.12.x branch with console in master

Issue
https://github.com/gravitee-io/issues/issues/6145
Description
A PR to merge "3.12.x + console-webui" in "master + console-webui", in order to have a clean history for future merges.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.


fix(deps): update jest and ts-jest to v27

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Circle packing performance when there are a lot of nodes at the same level

I am visualizing a file tree structure with pack. This works great when files are spread throughout the file tree, but the packing algorithm becomes really slow if there a lot of files in a single folder.
For reference, when i try to pack 40k items, it takes about 10 seconds.
Is there a way to make packing items faster when there are a lot of items in the same folder?
I have summed and sorted the hierarchy.

The packing algorithm described in this essay: https://observablehq.com/@d3/d3-packenclose, and is implemented here for the part that packs all "siblings" (circles that must be packed together at the same level).
Barring new ideas to make the algorithm or the implementation faster, here are a few oblique suggestions:

If the file structure is always the same, you could run the algorithm once, and save its results in a file.
If the structure is always different, maybe the pain comes from the fact that the browser hangs during computation?  In that case you could pass it to a web worker. You will still need to wait 10s before you have the result, but the browser could show something else during that time (maybe an approximation computed from the top 10% of the circles…).
Since this is an iterative algorithm, it might be possible to tweak the implementation to yield after every new circle has been added to the pack. So instead of staring for 10s at a blank screen, you would spend the same 10s seeing the structure emerge.

The algorithm appears to be O(N^2) in time—and about 4 times slower when the nodes are sorted by descending radius (the largest in the center), than when the smaller nodes are in the middle.
On my computer I see 1.6s for 40k nodes in the first case, and 0.4s in the second case; I need 135k sorted nodes to get to 10s, and at this point it's the visualization that's starting to slow things down.


[release-4.14]: OCPBUGS-20898: bump library-go to include switch to HTTP/1.1

Pre-merge verified and got the expected results.  Detail see https://issues.redhat.com/browse/OCPBUGS-20898?focusedId=23392774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23392774

/label qe-approved

/lgtm

/label cherry-pick-approved

/retest

@dgrisonnet Needs backport-risk-assessed

/label backport-risk-assessed
/lgtm
/approve

/test e2e-aws-ovn


Added End of Life notice

This project was marked as end of life in #230, so I have done the change necessary.

Thanks for the pull request.


Lights using flux_led component does not turn on with effects

Home Assistant release with the issue:

0.73.0
Last working Home Assistant release (if known):
0.72.0
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

flux_led component
Description of problem:
Hello. With version 73 my Hassio is unable to turn on the light with effects data, for example:
service: light.turn_on
{
  "entity_id": "light.ledsalatv",
  "effect":"colorloop"
}

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: flux_led
  devices:
    <IP_ADDRESS>:
      name: ledsalatv
      mode: "rgb"
    <IP_ADDRESS>:
      name: ledsaladesktop
      mode: "rgb"

Traceback (if applicable):
No logs available...
Additional information:
Since update, a few automations and scripts like this stoped working:
- alias: TV sala
  trigger:
    - platform: state
      entity_id: media_player.tv_sala
      from: 'off'
      to: 'playing'
  action:
    - service: light.turn_on
      data:
        entity_id: light.ledsalatv
        effect: colorloop

Thanks.

This is due to #14713 which moved turnOn() down below the effect handling.
CC: @oblogic7

Thanks @amelchio! As a temporary workaround, I had the component downgraded, so it works fine for now.
I was wondering, if you might know about these issues too:
The effect drop down menu always clear up after selecting the effect, becomes blank and settings are not persistent after the light is turned off and on again.
Also, I've notice that if I turn the light on using Home App on iOS, the light always turns on without effect, maybe related to the behavior above.
Thanks a lot sir!

Sorry, I don't know about those things.
If you can test my change in #15472, we should be able to get this issue fixed for 0.74.


Fixed local download path to verify with MD5.

local_file_path is not defined anywhere. Chef fails on first time run. Second run is fine because distribution archive is already there, ruby_block resource is not notified.
Fixed security issue - the second chef run wouldn't check downloaded file vs MD5.

Hi @DmitrySolodovnyk, the md5sum is only checked the first time a release is downloaded, and the sha256 is used by Chef to check whether the remote and local file are the same, and if it's not it'll download the remote file again, which will trigger the md5 check as well, so don't really need to run it on every Chef run.

Merged in c0ea1488e58a91d6e4de3b52d3b14c007e77f8cb.


no async support for embeddings

hi all, it appears that the langchain Redis vector db interface does not support async calls to embeddings APIs e.g. to embed query strings.
the langchain OpenAIEmbeddings interface, for example, does implement an async aembed_query() method in addition to embed_query(), but as far as i can tell, the Redis interface only uses the latter.
am i missing something? if not, are there plans to add async support for embeddings?

@mziru, thanks for the report. We're working on our Async features. Stay tuned.


Automatical close.

Please, make in the future option for automatical close h-encore after his working.

No need its one click and its not a bug.  It will be closed soon this topic
On Sat, 3 Nov 2018, 20:59 Smichara<EMAIL_ADDRESS>wrote:

Please, make in the future option for automatical close h-encore after his
working.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TheOfficialFloW/h-encore/issues/64, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AnVATE7u0llZYD1LlqDEICbNS7pJ6k9Qks5urgO9gaJpZM4YM_0j
.


gateway deletion docs

Write docs explaining how the gateway deletion works and what gets removed

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 30 days since being marked as stale.


Update sbt to 1.3.0

Updates org.scala-sbt:sbt from 1.2.8 to 1.3.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: semver-minor

closed in favour of https://github.com/scala/scala-continuations/pull/57


nc_open fails in Windows with network drives

netcdf version: 4.8.0
hdf5 version: 1.8.12
OS: windows 10
Compiler: VS2019 u7.7
This was caught while running some of our tests on netcdf files hosted in a network drive.
nc_open fails when the file is accessed using the network path. However, if I map the network drive, and then try to access the same file, it works fine.
I could not reproduce the issue with netcdf v4.7.4 + hdf5 1.8.12.
As shown in the repro code below, v4.8.0 errors if the file is accessed by the network path
string FILE_NAME = "\\\\mathworks\\devel\\sandbox\\abaruah\\Features\\NetCDF_New_Features\\temp\\monotonic.nc";
The output of the program below is
Open status: 2
NCID: -858993460
status after close = -33
But if I map the network drive and then try to access the file, it works
string FILE_NAME = "Y:\\abaruah\\Features\\NetCDF_New_Features\\temp\\monotonic.nc";
Open status: 0
NCID: 65536
status after close = 0
#include <stdio.h>
#include <string>
#include <netcdf.h>
#include <iostream>
#include <vector>

using namespace std;

int
main()
{
    int status;
    int ncid;
    string FILE_NAME = "\\\\mathworks\\devel\\sandbox\\abaruah\\Features\\NetCDF_New_Features\\temp\\monotonic.nc";
    //string FILE_NAME = "Y:\\abaruah\\Features\\NetCDF_New_Features\\temp\\monotonic.nc";

    status = nc_open(FILE_NAME.c_str(), NC_NOWRITE, &ncid);
    std::cout << "Open status: " << status << std::endl;
    std::cout << "NCID: " << ncid << std::endl;
    status = nc_close(ncid);
    printf("status after close = %d\n", status);

    return 0;
}

Frankly, I completely forgot about network drives. I suspect I assumed they
would all be mounted under a drive letter. Which probably serve as a work-around.

Correct. Mounting the network drive as a drive letter works as a workaround.
But since unmounted network drives worked in previous versions of netcdf, we are concerned if this would break existing customer workflows once we upgrade to v4.8.0.

I will add a fix for this case.

I tried to fix this here: https://github.com/Unidata/netcdf-c/pull/2065
But since I do not have access to  network drive, I cannot test it.
When it gets integrated, please let me know if it works.

This has been integrated into the gihub master. Please test it if you can.

Thanks a lot. I tried this out. The bug is resolved.


Fix issue when using namespaced variables for enums

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

Fix issue when using strawberry.enum(module.EnumClass) in mypy


关于PIR，PSI和隐语SQL的问题

Issue Type
Bug
Source
binary
Secretflow Version
secretflow 0.6.13b0
OS Platform and Distribution
Linux Ubuntu 18.04
Python version
3.8.13
Bazel version
No response
GCC/Compiler version
No response
What happend and What you expected to happen.
I want to know whether the filtering and joins in sf MPC SQL uses the technology of PSI and PIR, or are they related to them. Can I understand that PSI and PIR are part of MPC SQL

Reproduction code to reproduce the issue.
#


Have you opened the dataset? ''rename ClipShots to data.tar.gz''? I do not quite understand what it means.

Have you opened the dataset? ''rename ClipShots to data.tar.gz''? I do not quite understand what it means.
the uploaded dataset is compressed by the 'tar' command, and then splited into multiple files by the command 'split'。 so rename these files as 'data.tar.gz.a', 'data.tar.gz.b' , and then use the command 'cat' and ‘tar’ to uncompress the archives

Originally posted by @hermit0 in https://github.com/Tangshitao/ClipShots/issues/3#issuecomment-473117445

No. Please rename the root directory.

No. Please rename the root directory.

The file name was changed to data.tar.gz, then what? It is still a folder. . .


Uro error

λ cat newfile222.txt | uro
Traceback (most recent call last):
File "C:\Users\Yaseen\AppData\Local\Programs\Python\Python39\Scripts\uro-script.py", line 33, in
sys.exit(load_entry_point('uro==0.0.1', 'console_scripts', 'uro')())
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\site-packages\uro\uro.py", line 139, in main
if matches_patterns(path):
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\site-packages\uro\uro.py", line 107, in matches_patterns
if re.search(pattern, path):
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\re.py", line 201, in search
return _compile(pattern, flags).search(string)
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\re.py", line 304, in _compile
p = sre_compile.compile(pattern, flags)
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\sre_compile.py", line 764, in compile
p = sre_parse.parse(p, flags)
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\sre_parse.py", line 948, in parse
p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\sre_parse.py", line 443, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
File "c:\users\yaseen\appdata\local\programs\python\python39\lib\sre_parse.py", line 836, in _parse
raise source.error("missing ), unterminated subpattern",
re.error: missing ), unterminated subpattern at position 379
cat: write error: No space left on device
Can you help, it saying space issue, i have alot of space

Uro has nothing to with cat: write error. However, the error before it has been fixed. Upgrade your package from pypi and see if the problem still exists.