Mode, or overlay view filter navigation in bottom LHS is becoming cluttered.

As we add more ways to overlay data and filter the contents of a view, the nav in the bottom LHS is becoming cluttered.

See also: https://github.com/weaveworks/scope/issues/1369


Support Open Service Broker API v2.12

Services API Tracker story #144682123
Why
The new Open Service Broker API v2.12 removed CF-isms and added a new optional context field. The implementation was added as part of this PR but the version not changed, this was so feedback could be obtained and provided to the working group. The group have now released v2.12 of the OSBAPI spec and CF can bump its supported version.
Release notes can be found here
What

Update X-Broker-Api-Version header from 2.11 to 2.12.
Add 2.12 compatibility test to broker api version tests.

PR

[X] I have viewed signed and have submitted the Contributor License Agreement
[X] I have made this pull request to the master branch
[X] I have run all the unit tests using bundle exec rake
[X] I have run CF Acceptance Tests on bosh lite

Thanks,
Sam
cc: @matthewmcnew / @ablease

Hey @Samze,
Thanks for the PR! We'll let it run through the pipes and see how it goes.
Thanks,
Aakash & @anniesing
CAPI Community Pair


New PAYONE gateway

I'll get the PR done - just logging here before I forget:

Gateway: PAYONE https://www.payone.de/en/platform-integration/interfaces/
Composer Package: academe/omnipay-payone https://github.com/academe/OmniPay-Payone
Maintainer: Jason Judge https://github.com/judgej

In the README several monts ago. How time flies.


SSLError when use Pyinstaller

I try to mix my python desktop app to exe file. When execute without compiler is OK but EXE it show error as below
Exception in Tkinter callback
Traceback (most recent call last):
  File "C:\try\build\main\out00-PYZ.pyz\Tkinter", line 1536, in __call__
  File "<string>", line 154, in on_btn_download
  File "C:\try\build\main\out00-PYZ.pyz\usgsDownloader", line 57, in search
  File "C:\try\build\main\out00-PYZ.pyz\usgs.api", line 302, in search
  File "C:\try\build\main\out00-PYZ.pyz\requests.api", line 109, in post
  File "C:\try\build\main\out00-PYZ.pyz\requests.api", line 50, in request
  File "C:\try\build\main\out00-PYZ.pyz\requests.sessions", line 465, in request
  File "C:\try\build\main\out00-PYZ.pyz\requests.sessions", line 573, in send
  File "C:\try\build\main\out00-PYZ.pyz\requests.adapters", line 431, in send
SSLError: [Errno 2] No such file or directory

Compile command
C:\try>pyinstaller -F --hidden-import=requests main.py

What should I fix it? thank

This is not a bug in requests. This is a bug in PyInstaller since it doesn't know how to detect static package data (e.g., the certificate bundle that requests is packaged with).

Thanks sigmavirus24 for giving a hint.
Fix this by http://stackoverflow.com/questions/21201238/twilio-python-module-errors-after-compiling/21206079#21206079

I too have the trouble with Pyinstaller and Requests. Thanks folks for posting the question and for pointing us in the right direction, much appreciated!


Add json output format for crc start

User can now do crc start -o json. Plain text behaviour is unchanged.
Only difference with json is that the status code is always 0 (this can be discussed maybe - it was easier).
$ crc start -o json
....
{
  "success": false,
  "error": "Failed to get pull secret: interrupt"
}
$ echo $?
0

$ crc start -o json
....
{
  "success": true,
  "clusterConfig": {
    "url": "https://api.crc.testing:6443",
    "adminCredentials": {
      "username": "kubeadmin",
      "password": "ILWgF-VfgcQ-p6mJ4-Jztez"
    },
    "developerCredentials": {
      "username": "developer",
      "password": "developer"
    }
  }
}
$ echo $?
0

Unit tests could be better if we could mock config and preflights.

Now, it catches preflight errors and outputs credentials.

/lgtm

/retest

@guillaumerose I can see 3 different commits with Remove call to logging.Fatal in preflight package should it can be merged to a single commit message?

I squashed the 3 commits, thanks!

/retest

@guillaumerose I am assuming this PR works for crc start with the flags passed to it.
e.g. crc start -p ${pullSecretFromSetting} -c ${cpuFromSetting} -m ${memoryFromSetting} -ojson

/retest

/retest

/test this please

/retest

/retest


WIP Add prerecorded speech to SystemCapabilityManager

Fixes #1123
This PR is not ready for review.
Risk
This PR makes minor API changes.
Testing Plan
Unit tests and smoke tests
Summary
Add new capability type
CLA

[X] I have signed the CLA

Codecov Report

Merging #1124 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #1124      +/-   ##
=============================================
+ Coverage      46.89%   46.89%   +<.01%
  Complexity      4048     4048
=============================================
  Files            457      457
  Lines          22286    22287       +1
  Branches        2522     2522
=============================================
+ Hits           10450    10451       +1
  Misses         11223    11223
  Partials         613      613

Impacted Files
Coverage Δ
Complexity Δ

...vicelink/proxy/rpc/enums/SystemCapabilityType.java
100% <100%> (ø)
4 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Dotnet keenum minor refactorings

This pull request covers the following issues:

#191
#192
#193
#194
#195
#196
#197
#198

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- dotnet/Simple.Sauce/IncorrectSafariVersionException.cs  1
- dotnet/Simple.Sauce/JsonUtils.cs  1
- dotnet/Simple.Sauce/SauceDriver.cs  1
- dotnet/Simple.Sauce/SauceOptions.cs  2

See the complete overview on Codacy


DSD-502 & DSD-421: Composing the Label element with Chakra elements

Fixes JIRA ticket DSD-502 and DSD-421
This PR does the following:

Uses Chakra to compose the Label component.
Updates the font size to 14px.

How has this been tested?
Storybook.
Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr705-ajvo6wo2ewshjlyjqvgftm308hapfdja.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6154e0294807c0a3403e92ef

Tugboat has finished building the preview for this pull request!
Link:

https://pr705-ajvo6wo2ewshjlyjqvgftm308hapfdja.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6154e0294807c0a3403e92ef

Tugboat has finished building the preview for this pull request!
Link:

https://pr705-ajvo6wo2ewshjlyjqvgftm308hapfdja.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6154e0294807c0a3403e92ef


maxFontSizeMultiplier doesn't work on Buttons

It works with Paragraphs, but not with Buttons.
It is possible to put a Paragraph inside the Button then it will work, but it would be great if the Button would support this.

check out v1.58.1 when it finishes publishing, re-open if not working


Special Achievements are not checked properly when two people are eligible at the same time

This came up with Qtrie's issue:
https://boardgamearena.com/bug?id=75544

I believe the root cause is in getActivePlayerIdsInTurnOrderStartingWithCurrentPlayer(), likely with how we determine who the "current player" is.
Not going to lie, this will be annoying to fix (and test that it's working well), but it's worth doing.

I think this is best fixed by reverting the special achievement changes (https://github.com/micahstairs/bga-innovation/issues/764).

This is no longer worth doing now that we've changed the special achievement check back.


Error when creating a node without selecting a node type

When creating a new node and no type is selected you can still press Create, which creates a error.
This should be handled or the Type selection radio should have a default selected. Also a little UX improvement 💪

did this help out?
https://github.com/jccguimaraes/atom-project-viewer/blob/929623ebb47264604662a28e6278620c98e71002/src/editor-view.js#L652

Yep, but UX wise defaulting would be better. Or at least provide a small alert, so that the user knows what he forgot to set.

so you think it's best to make it default like to project?

correct. then you have one click less for the default scenario.
Btw did you not had create project and create group in the context menu? Was there a reason to add the layer of the interface in between there? Or did you plan future use of the pane for a later expansion?
Sorry if I am bit nitpicky here 😸

hey @Hammster, sorry for late implementation. It's done now.
I didn't understand the last part "Was there..."

Currently the steps are as followed
Right Click -> Create New -> Select the Type -> Fill Information -> Create
Before it was a little bit shorter
Right Click -> Create "Type" -> Fill Information -> Create
Was there a reason to do this ?

solo option for not having 2 menu items instead of just one... :D

UX wise i would prefere to have two options, it feels a little bit artificial :P
Also no worries for the late responses, i am also stuck in a pile of work ;)

will try to add both then

done! will ship on next release. Taking the time to close some others I hope

please validate this issue!

Great work, nothing to complain about 😄👍


Sync the system time of all of servers behind Ceryx reserve proxy

Hello,
When a client request to sync the system time of all of servers behind Ceryx reserve proxy, such as to sync with a timestamp server. Could Ceryx comply this kind of specifiction? If yes, could we design a control program via API, and how? Thanks.

Hi @junge1999! Thanks for the comment.
Can you share a few more details about this? Do you think of it as multiple Ceryx servers coordinating together or Ceryx synchronising targets? Also, is there any other example of such technology that we can drive inspiration from?


Missing check successfulMessages[versionedHash] after the external call succeeds

Related to this issue from OP, we should check successfulMessages[versionedHash] must be false before setting it to be true(when the external call succeeds)
In CrossDomainMessenger.relayMessage, we already included it. But we override relayMessage on L1CrossDomainMessager and missed it

CrossDomainMessenger.sol:

//
if (success) {
      // This check is identical to the one above, but it ensures that the same message cannot be relayed
      // twice, and adds a layer of protection against reentrancy.
      assert(successfulMessages[versionedHash] == false);
      successfulMessages[versionedHash] = true;
      emit RelayedMessage(versionedHash);
}

L1CrossDomainMessager.sol
 if (success) {
          successfulMessages[versionedHash] = true;
          emit RelayedMessage(versionedHash);
}

-> Suggestion changes
 if (success) {
      assert(successfulMessages[versionedHash] == false);
      successfulMessages[versionedHash] = true;
      emit RelayedMessage(versionedHash);
}

Any idea how this was missed?
Or was it purposefully left out?

Any idea how this was missed? Or was it purposefully left out?
The reason why I asked is to figure out if we need to check other overridden functions.

Because we added the override function and didn't know this issue -> we assumed that this condition was already checked at line 273.
But this is a different issue, so it would be good to add it now.

I understood this attack scenario.
I removed it because i thought that it is useless. This scenario is really complex because it relates to upgrading process. I will update the code.
Thank you, @0x6e616d

I think the code is still safe because there is other protection: https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L365
But I think still need to add a check

I think the code is still safe because there is other protection: https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L365
But I think still need to add a check

Yes, this issue is resolved by:

Do not over the xDomainMsgSender if it is not the default value.
Add another check that successfulMessages for the message is still false after the
external call.

-> We added point 1, with point 2, we already added it on the XDM contract, so but with L1XDM, we overrode relayMessage function, so we still need to add the check

Thank you, @0x6e616d
I updated: https://github.com/tokamak-network/tokamak-thanos/commit/f4ecf1c906a36faa5eac05104f935b92eaa69658
As I understood, there was an error with Optimism when they upgraded their contract with their multi-signatures solution as what described here: https://github.com/ethereum-optimism/optimism/pull/8864. It does not happen with our case even if there is no updates because we are not using multi-signatures. But It is better for update the code here
With Optimism's multi-signature policy, attackers can try to make reentrancy attacks the function relayMessage when having enough vote for upgrading.
About the first solution: Do not over the xDomainMsgSender if it is not the default value.

Call relayMessage function
At  the line https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol#L307, there is a call to upgrade the contract, after finishing the upgrade process, there is a sub call to relayMessage again with the same message
The Optimism fixed the attack line 369-371 (called when upgrading) https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L367

Without this fix, xDomainMsgSender = Constants.DEFAULT_L2_SENDER and it is possible for a reentrancy call

Call the relayMesasge with the same message

This time, the reentrancy check works : https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol#L286

About the first solution: Added another check that successfulMessages for the message is still false after the
external call.
This solution does not prevent reentrancy attack, however still solve the issue

Call the relayMessage the first time
When running to the line call upgrade and relayMessage with same message
The reentrancy call is successful, and  successfulMessages[versionedHash] = true;
Return to the first relayMessage call

The first call will be failed by the check:  assert(successfulMessages[versionedHash] == false);
So for the second solution, the problem is solved, but the reentrancy call is successful while the first call is failed.

Thank you, @0x6e616d
I updated: f4ecf1c
As I understood, there was an error with Optimism when they upgraded their contract with their multi-signatures solution as what described here: ethereum-optimism/optimism#8864. It does not happen with our case even if there is no updates because we are not using multi-signatures. But It is better for update the code here
With Optimism's multi-signature policy, attackers can try to make reentrancy attacks the function relayMessage when having enough vote for upgrading.
About the first solution: Do not over the xDomainMsgSender if it is not the default value.

Call relayMessage function
At  the line https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol#L307, there is a call to upgrade the contract, after finishing the upgrade process, there is a sub call to relayMessage again with the same message
The Optimism fixed the attack line 369-371 (called when upgrading) https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L367

Without this fix, xDomainMsgSender = Constants.DEFAULT_L2_SENDER and it is possible for a reentrancy call

Call the relayMesasge with the same message

This time, the reentrancy check works : https://github.com/tokamak-network/tokamak-thanos/blob/codeReview/packages/tokamak/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol#L286

About the second solution: Added another check that successfulMessages for the message is still false after the external call. This solution does not prevent reentrancy attack, however still solve the issue

Call the relayMessage the first time
When running to the line call upgrade and relayMessage with same message
The reentrancy call is successful, and  successfulMessages[versionedHash] = true;
Return to the first relayMessage call

The first call will be failed by the check:  assert(successfulMessages[versionedHash] == false);
So for the second solution, the problem is solved, but the reentrancy call is successful while the first call is failed.  => the whole transaction is failed

Thank you! Sound goods


Add empty session tips for Auto

:Release Notes:
Add empty session tips for Auto
:Detailed Notes:
After flashing booting, user should select "profile icon" on the screen.
At this time, the session list is empty. So, CLI commands print
unexpected results. Add tips message to user
:Testing Performed:

Before run TC, you must select a profile on each display.
TC passed on AUTO & OSE target and Auto emulator.
eslint passed
Verified with CLI commands
a. boot Auto board. The login UI is shown
b. Run CLI commands. "select profile" tips should be printed.

$ ./ares-install.js com.domain.app_1.0.0_all.ipk
$ ./ares-launch.js -r
$ ./ares-launch.js -H sampleWeb
$ ./ares-launch.js -c com.test.app
$ ./ares-device.js -s
$ ./ares-inspect.js -s com.domian.app.test
$ ./ares-install.js -l
$ ./ares-install.js -F
$ ./ares-shell.js -dp 1
$ ./ares-log.js -ul -dp 1 (on Auto target)
> ares-xxxx ERR! [Tips]: Please select the profile on the display

:Issues Addressed:
[PLAT-143757] Add "login profile" tips after flash booting

Code :+1:
Verified :+1:

In case emulator user is developer, "$ ./ares-log.js -ul -dp 1" is displayed "ares-log ERR! [Tips]: Unable to connect to the target device. root access required".
Is this your intention? I think this is okay. I'm asking for confirmation.
On Test performed, #1 is needed more explanation.
For example, Before test run, you must select a profile each display. Pass TC~~

#1. Yes.  At first, ares-log checks root permission and then sessionlist for -dp 1. So, "Unable to connect to the target device. root access required" is expected Tips
#2. I updated it.

Code 👍
Verified 👍

code :+1:
verify :+1:


Support for loading data from meters

Hi,
I'm diabetic and will take a look at this for sure - I know Django and something I can play with would be great. My greatest pain point has always been the manual recording of data in a logbook and doing this thru a GUI doesn't improve things (it wasn't clear from the description if this supports data download).
Software I recently looked at, OneTouch's OTDMS (finally decided to download it), is generally awful (poor graphics and UI) which is probably why they have discontinued it and are trying to force users to use their web based app (no, I'm not sending my health data to god knows what insurance company to be resold). The iOS apps I've looked at also have this problem of needing to manually input data (and a lot have bad UIs).
The Freestyle Libre software is pretty nice (I can send you screenshots if you want), but their CGM things (that use Bluetooth) are a bit too flaky I think - I returned too many in a row to justify keep buying them.  I just got a new GlucoRx meter but haven't started using it so don't know how nice their software is yet.
For info on dealing with meters, https://openaps.org/ would be a starting point. There is a whole bunch of diabetes software out there, but I'm not sure about the amount of info for dealing with hardware/meters (just have stuck with the OneTouch for too long).
So even some sort of import option to import a csv file (assuming one can get that in some fashion from your meter/other software) would be useful.

Thanks. I'll have a look at all of this. If i could help with improvements that will be a pleasure

Hi,
I read your post more precisely, and have questions:

What do you need, to use that project if it covers a part of your needs ?

Do you search a tool/soft that automatically synchronizes the data of the device that collects your health state and displays a graph of anything you want ?

The manufacturer does not provide such a thing ?
if no, how could we get the data from the device ?

If data can be collected, we can try to build another project that follow more precisely your needs (and may be the needs of many more diabetic people)
Just tell me :)
Regards

Hi,
Sorry to say, I haven't really taken a look at this project yet - I'm getting a MSc in Data Science right now and the work all last year was more than I thought it'd be. And this semester looks worse.
I submitted this issue to provide some suggestions - I guess I was interested to see a web type app that handles the usual functionality of what all the different diabetes related software do. A web app is a lot more ... useful? than some closed source mobile phone app or SaaS system you have to sign up to. For privacy conscious consumers who are not technical, but don't want to be submitting their health data to some corporation, a Django based web site that could be rolled up into a Docker image or AWS free tier based sort of thing would be useful - personal web sites for non-tech people, etc. Or a simple install of Nginx, etc that runs on one's PC. Maybe that is a key idea - how can non-technical people easily install and use the system you are building?
As far as I know, manufacturers of blood glucose meters don't really offer tech specs on how the meters transfer data - closed source Windows drivers etc. With that info, a developer could easily write something to get data from the meter as they see fit. So that is the biggest tech issue I see. I'm sure there is info available somewhere, and at the very least, some hardware reverse engineering to decode the protocol is always possible - I bet someone has, I just haven't looked for it.
I will look at this Django app when I get a chance and give you some more feedback - I have a lot of work this semester, and then it's the dissertation...

I've noticed that there are a lot of projects that add a lot of tracking and smart capabilities for type 1 diabetics on insulin pumps, but not many that cater for us that still use the manual blood tests.  There is significant fragmentation among the various providers of pumps on how data is kept and transferred on these devices, but I've noticed that lately a lot of them appear to be moving to general USB storage device and CSV files (I can provide some files for example) that should theoretically be importable (they are nothing but standard CSV files).
This project is great that it will allow me to enter data from pretty much any device that has an internet connection, but to be able to import a CSV file would be interesting!

Yes that will be wonderful to have that possibility.
If you could provider an exttact of a CVS file i'll be glad to make an import process.
If you could also give the model of your pump, thus, may be someone else could use the project or would contribute by sharing à CVS file related to his/her pump
Thanks

To be reopened once news info will be provided

I read https://github.com/openaps/openaps/blob/master/README.md and saw that the app can work with devices. As i don't have any, I can't go thurthere more.  If you could provide data from the commands:
openaps report invoke

or
openaps-use pump


[geostyler-data] Export ReadParams Interface

Every Parser should export a ReadParams interface so its clear what params need to be passed to the readData function of the specific parser.

duplicate of #227


NEWS: add v3.2.0

Will update the date when we actually release it. (Will merge right before the release).
Please let me know if I am missing anything.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6846e49). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #7995   +/-   ##
=========================================
  Coverage          ?   74.87%
=========================================
  Files             ?      340
  Lines             ?    26538
  Branches          ?        0
=========================================
  Hits              ?    19871
  Misses            ?     5214
  Partials          ?     1453

Continue to review full report at Codecov.

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

defer to @heyitsanthony

@heyitsanthony @xiang90 PTAL.


Add R2 score function

Implement R2 score function to evaluate PDBbind dataset

Codecov Report

Merging #253 into master will decrease coverage by 6.55%.
The diff coverage is 89.49%.

@@            Coverage Diff             @@
##           master     #253      +/-   ##
==========================================
- Coverage   88.77%   82.22%   -6.56%
==========================================
  Files         108      112       +4
  Lines        5246     5484     +238
==========================================
- Hits         4657     4509     -148
- Misses        589      975     +386


Consider reframing this to be a list of awesome *byexample.com websites

I notice that this list duplicates much of the content from:

https://github.com/lauragift21/awesome-learning-resources
https://github.com/razum2um/awesome-clojure
https://github.com/sorrycc/awesome-javascript
https://github.com/krispo/awesome-haskell#resources
https://github.com/markets/awesome-ruby
all the more focused "awesome ${thing}" lists

imo it has too broad a scope: example resources for everything 😵
I would suggest pivoting this list to focus specifically on *byexample.com -like sites like:

https://javascriptbyexample.com/
https://gobyexample.com/
https://lotz84.github.io/haskellbyexample/
https://examples.deno.land/
https://denobyexample.dev/
https://www.cbyexample.com/
etc.

why this might be a good idea:

fill a niche that doesn't have an awesome list yet
provide a community index of *byexample.com sites
already shows up when searching for "awesome by example" on google

note that this is a suggestion. its ok if this idea isn't the right fit for this list :heart:

This is what I came here looking for too. But not just websites, repo's with notebooks that go through things using a series of examples.

https://github.com/rust-lang/rust-by-example
https://github.com/billtubbs/pandas-examples/blob/master/Brief-intro-to-pandas-by-example.ipynb
https://github.com/samuelcolvin/JuliaByExample

And there are also courses and books!
I like this way of learning but it's hard to find a list the includes tutorials that are just by example


Mock Response Builder : add cookie

Add cookie to the ClientContext

Thanks for contributing. I will prepare version 1.5.0 and publish it this week.


[SPARK-23217][ML][PYTHON] Add distanceMeasure param to ClusteringEvaluator Python API

What changes were proposed in this pull request?
The PR adds the distanceMeasure param to ClusteringEvaluator in the Python API. This allows the user to specify cosine as distance measure in addition to the default squaredEuclidean.
How was this patch tested?
added UT

cc @srowen @BryanCutler

Test build #87507 has started for PR 20627 at commit 8fe8efa.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/935/
Test PASSed.

Test build #87507 has finished for PR 20627 at commit 8fe8efa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87507/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/966/
Test PASSed.

Test build #87553 has started for PR 20627 at commit 6b379ef.

Test build #87553 has finished for PR 20627 at commit 6b379ef.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87553/
Test PASSed.

OK by you @BryanCutler ?

LGTM, thanks for making the addition to java param tests @mgaido91

Merged to master


Unable to disable dark mode

I'm not able to disable dark mode. The dark mode on this site is too high contrast and has caused severe eyestrain after viewing for a short period of time. Please allow me to swap between light and dark mode, or at least select which theme I want.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 96771ba5-ef91-ed15-33a3-ff5e5b9e753f
Version Independent ID: de9baa15-55e1-4cb8-32d0-6583a8b5d689
Content: Understand your detailed usage and charges
Content Source: articles/cost-management-billing/understand/understand-usage.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@em-turner Thank you for the feedback. We are actively investigating and will get back to you soon.

@em-turner Hi there. Sorry you were having trouble finding the theme selection. Unfortunately, the option isn't as obvious as some would like. You can find it at the bottom of every article on https://docs.microsoft.com. Here's a screenshot to help.

#please-close


Better Transaction Names

Sentry has the concept of 'culprit' today, but we're likely going to move to a transaction name pattern. I dont think we'll be renaming the attribute as part of this, but the goal will be to provide a native API within clients to override it using a stack approach (see Python draft).
That is, if you're using Rails, the transaction might be the route name (or the route class that handles it, rather), instead of some semi-arbitrary function in the stacktrace.
Wanted to open this issue to begin discussion on what would fit best there.
For reference, the current culprit that would be replaced shows up similar to app/foo.rb in block in blah at line 13.

That is, if you're using Rails, the transaction might be the route name (or the route class that handles it, rather), instead of some semi-arbitrary function in the stacktrace.

In Rails, we should probably report /.

Confirmed that we should be overloading Culprit in most integrations

Opening a new issue for overhauling integrations


Is the SECURITY.md email address still correct?

Just checking on the status of the email address specified in SECURITY.md. Is that still live?

@crenshaw-dev yes, that email address is still active.


Use explicit, working versions for logging stack

Elasticsearch has made major changes in version 8.x, which is automatically pulled by Helm we run inside the setup.sh script. These major changes eventually lead to failing deployment of ES, Kibana and Fluentd connector Pods. Our Helm values for logging components should be adjusted to make everything to work again.
Quick fix is proposed in this PR to still use that suitable for our version which is was probably the latest version back then when this script was developed initially.

@pklopotowski  Could you double check and merge if ok?

@pklopotowski could you please check this one? We would like to merge this sooner the better.
CC: @hectorrios , @alibahadirzeybek


clients throw error when the S3 rate limit is hit

rpc error: code = 13 desc = invalid header field value "SlowDown: Please reduce your request rate.\n\tstatus code: 503, request id: 1134F6E552866794"

S3 has a request rate limit of 300 req/s when that gets hit it triggers an rpc error in the golang client

This is actually a bit curious. Unless I'm misreading the code it seems that in the amazon obj client we're using an exponential backoff writer which should catch errors like this and retry.
@derekchiang any thoughts on this one?

@erikreppel we've increased the backoff rate and added more logging so that if this error happens again, there will be more info to work with.


Jobs Getting Stuck in Active State

Hi @behrad  I am still experiencing jobs being stuck in the active state, similar to issue #391
I am using<EMAIL_ADDRESS>and redis 2.8.17
I have tried to carefully setup all recommended steps to avoid this.  Here are some code snippets.  If I'm doing something wrong I would love to hear about it.  I've just torn out the bits of source that deal with kue/jobs here and redacted stuff that wasn't relevant.
producer -- separate node process
var jobs = kue.createQueue({ disableSearch: true, redis: config.redis });

var dying = false;
process.on('uncaughtException', function (err) {
   log.error('uncaught exception', err.stack);
   die();
   dying = true;
});

process.on('SIGTERM', function () {
  log.error('SIGTERM');
  die();
  dying = true;
});

function die() {
  if (!dying) {
    jobs.shutdown(function (err) {
      if (err) { log.error('Kue DID NOT shutdown gracefully', err); }
      else { log.info('Kue DID shutdown gracefully'); }
      process.exit(1);
  }
}

// createJob( ) is called on an interval as needed

function createJob(data) {
   var job = jobs.create('deliver:sub', { title: 'Deliver Subscription', sub: data })
    .removeOnComplete(true)
    .attempts(5)
    .backoff({type: 'exponential'})
    .save(function (err) {
      if (err) { return log.error('Error creating deliver:sub', err); }
      log.info(util.format('job[%s] created', job.id));
  });

  job.on('complete', function() {
    /* logic here */
  });

  job.on('failed', function () {
    log.error(util.format('job[%s] failed ', job.id));
  });
}

consumer -- separate node process
var jobs = kue.createQueue({ disableSearch: true, redis: config.redis });

try {
  kue.app.listen(3001);
} catch (err) {
  log.error('Error: could not start kue express server', err);
}

// called in master b/c we use job retries
jobs.promote();

jobs.watchStuckJobs();

var dying = false;
process.on('uncaughtException', function (err) {
  log.error('uncaught exception', err.stack);
  die();
  dying = true;
});

process.on('SIGTERM', function () {
  log.error('SIGTERM');
  die();
  dying = true;
});

function die() {
  if (!dying) {
    jobs.shutdown(function (err) {
      if (err) { log.error('Kue DID NOT shutdown gracefully ', err); }
      else { log.info('Kue DID shutdown gracefully'); }
      process.exit(1);
    });
  }
}

jobs.process('deliver:sub', 5, function (job, done) {
  var domain = require('domain').create();

  domain.on('error', function (err) {
    log.error('domain error for deliver:sub', err);
    done(err);
  });

  domain.run(function () {
    process.nextTick(function () {
      /* logic here that ends with either */
      done();
      /* OR */
      done(err);
    });
  });

please first read my replies to your other topics and try to fix/find properly what's point of your problem. Then I am here to answer to your higher resolution questions.

hi @behrad, i read your comments here as well as scoured through numerous other issues/comments trying to find if there's something i'm doing wrong.
the suggestion to trap uncaught exceptions and use domains is one i have implemented.  i pasted the snippet above to hopefully get a second set of eyes and see if there is something i'm not doing correctly.
can you take a quick look when you have a chance, and let me know how jobs can get stuck in the active state if the snippet above were deployed (and what else i can do to prevent it)?

I thought I should add, even thought I am trapping on uncaughtException, SIGTERM, and any uncaught domain error, when the jobs run and do get stuck, there is no evidence that an error was thrown.  I log things fairly dilligently, esp. for error scenarios, and we monitor the app very closely using logentries with alerts set up to ping via email, hipchat, etc.
This situation happened again today where about 6 jobs were stuck in the active state.  I am able to convert them to inactive in the kue ui, and force them to run again, but I am trying to figure out why they ever get stuck in the active state in the first place.
All nodes are in EC2, same VPC, so network connectivity should be quite good.  I don't see any other errors indicative of network loss or disconnects.

Could it be related to a backpressure situation?  For example, if the consumer is not able to consume the jobs fast enough and process them, then new jobs end up waiting in the active state.
I have them configured to allow 5 concurrent...e.g. jobs.process('deliver:sub', 5, function (job, done) {
The actual job itself may take several seconds to complete.

ould it be related to a backpressure situation?

No

Hi @behrad, I have looked at all the other threads and applied any and all suggestions.  If you think I have missed something, I'd love to hear about it.
Do you have any other suggestions?

busy days... Please BUZZ me a few days later I ll try to help more

the only thing comes to my mind now, is it is related to a poor connection problem, or a unseen, swallowed error in your code...
please try to bind to error events:
kue.on( 'error', ... )

I am also seeing this issue. when viewing our logs, I can see 32 "stuck" jobs from the past few days, some with no attempts, others where they were attempted twice and then got stuck as active. We are not registering any errors, and all recommendations are in place for error catching.

which version are you on!?
and make sure to read https://github.com/Automattic/kue#error-handling

Our package.json has "kue": "^0.8.11". We have implemented the uncaughtException catching in our application.

99% percent of a job being stuck in ACTIVE state is user applications miss to call done So first you should try to trace whats happened to your stuck job! and node.js process and worker :)

For the record, this is still a problem for me too.  AFAICT I implemented all the suggested error handling with domains, process.on('uncaughtException'), etc.  I'm seeing about 2-3 jobs fail out of maybe 50 per day.  I just haven't had time to get back to this issue, but it is on my todo list soon.  I am also using the latest kue release from npm.  If there's any other info I can provide, I'll be happy to do so.
The code I posted above is a stripped down / simplified version of what I have in production.
I intend to instrument kue with additional logging so I can try to gauge better what might be going on.

is your redis connection unstable?
are you calling watchStuckJobs?

can watchStuckJobs be called on all instances, or just one? There's no documentation on that, and I know that promote can only be called on one instance.

it should be called on just one instance, like promote

I am calling watchStuckJobs on one node (master) only, and the redis connection is stable.  All nodes are in the same VPC in amazon, low latency, etc.  Plus I have log alerts ping me if, for example redis throws an error in the logs, or the node goes down or fails a status check.

I am calling watchStuckJobs on one node (master) only, and the redis connection is stable. All nodes are in the same VPC in amazon, low latency, etc. Plus I have log alerts ping me if, for example redis throws an error in the logs, or the node goes down or fails a status check

then it shouldn't be your app missing to call done, may be you have some errors in queue.on('error') or may be you are forgetting to call done in your logic...
I'll try to setup your provided code ASAP however I don't think it generates this

watchStuckJobs does not look for stuck active jobs it AFAICT looks for stuck inactive jobs. It's because some job (that was promoted to active from queued) in its processing stage isn't calling done() before a process exit and it's not being put into the inactive status. There are many reasons why this could happen.
Either we 1) make sure that active jobs that haven't updated "soon enough" are returned to inactive state, or 2) we similarly watchForStuckActiveJobs(..)
I have been playing around with something like this to watch jobs that have been in the active state too long and not updated recently enough:
// this code can be cleaned up quite a bit...
// the interval we want to check the active job list for stuck jobs:
var interval = 5000;
setInterval(function() {

  // first check the active job list (hopefully this is relatively small and cheap)
  // if this takes longer than a single "interval" then we should consider using
  // setTimeouts
  queue.active(function (err, ids) {

    // for each id we're going to see how long ago the job was last "updated"
    async.map(ids, function(id, cb) {
      // we get the job info from redis
      kue.Job.get(id, function(err, job) {
        if (err) { throw err; } // let's think about what makes sense here

        // we compare the updated_at to current time.
        var lastUpdate = +Date.now() - job.updated_at;
        if (lastUpdate > 2000) {
          console.log('job ' + job.id + 'hasnt been updated in' + lastUpdate);
          rescheduleJob(job, cb);  // either reschedule (re-attempt?) or remove the job.
        } else {
          cb(null);
        }

      });
    });
  });
}, interval);

I'm working on a good test case for you @behrad that will hopefully show you why this is happening :-) then maybe I'll send that with a patch for you to look over...

Thats right for watchStuckJobs, it is looking for inactive->active failures that is Kue responsibility. But I've not made up a watchStuckActiveJobs since it is more the app responsibility... however at kue side, it should make sure no active jobs are stuck, which is being implemented by  TTL feature
I'd be more than thankful for your suggestions

So, I've managed to reduce the frequency of this by limiting the number of jobs that can run down to one at a time.  In essence, I have removed all concurrency.  Jobs can be put into Redis/Kue as fast as they want - I am not rate limiting producers or anything, but job consumers only execute one at a time.
This has improved the stuck jobs for me, but last night, 62 jobs were stuck in the active state this morning.  No errors reported.  Note that if I lose connectivity to Redis for any reason, the error logs spit out a firehose into our private HipChat window.  I never see this.
What I did see this morning were 62 jobs waiting in the active queue, and 1 listed in the failed queue.
I could try to toggle the active jobs to inactive, but it just moved them.  It did not trigger them to be consumed and run.
So, I go and restart the web server which is currently responsible for consuming the jobs, and voila...all the jobs stuck in active start draining and complete.
This is the problem I see:  It is like the consumer side just gets stuck and no longer pulls from the queue -- even though this web server is active and healthy serving up normal http request just fine -- nothing unusual in system stats (memory, cpu, etc. totally normal).  It's like the kue consumer side of kue just gets in a state where it won't consume jobs anymore, but if I restart the app it fixes it.
Why is this?

It is like the consumer side just gets stuck and no longer pulls from the queue -- even though this web server is active and healthy serving up normal http request just fine --

When by each stuck active job, you lose one worker concurrency,  then done callback is not called by application. I still think you are missing to call done in some situations/execution paths, however you can add debug console logs to kue source to find out whats exactly happening.
Ensure for each job you are calling done by trace logs...

Thanks for the response @behrad -- that is my next step, enable trace debug on kue lib and see what is really happening.
One follow-up question: Let's say for argument's sake that something strange is happening here like the job executor somehow dies, and i don't trap the error, and the done callback is never called (I've reviewed this code several times and I don't see it, but let's just say that is the case).
Why would one failure cause all the rest to get stuck in the active queue, when the consumer is perfectly healthy and ready to accept active jobs?
I run pm2 on all my node processes which restarts them immediately in the event of failure.
There is something different about this scenario that I don't think is being handled properly.  I need to give a bit more background info.
I have the following node processes running on various physical hardware; actual kue jobs are named in fixedtype:font below, and each bold-face list item represents a running node process.  There are three processes involved in this flow, which is as follows:

subscription-process: queries database for different subscriptions that need to be executed at a certain time of day, when that time of day arrives, it puts a message in kue via a job named deliver:subscription
webapp-process: consumes deliver:subscription job and fires off a request to print-process via a job named create:pdf
print-process: consumes create:pdf, generates a PDF, uploads to S3 and calls done() on job sending back S3 url
webapp-process: consumes create:pdf response, emails link to user, calls done() on deliver:subscription

So, it is really a two-hop workflow.  I have other one-hop work-flows in this same system and they never get stuck.  It seems to be related to the double-hop.  Not sure if that means anything to you, but I feel it is warranted to disclose.  I will trace debug the lib and see if I can determine what is really going on.

Why would one failure cause all the rest to get stuck in the active queue,

this is not a true argument. for each job stuck in active queue, it's done has been missed to be called. this is something randomly happening in your case it seems.

when the consumer is perfectly healthy and ready to accept active jobs?

how can prove each worker is perfectly healthy and ready to accept active jobs? each stuck jobs represents a worker waiting for done to be called, until that worker process is restarted.
you can chain jobs and create flows... don't see it related to this. If you can create and post a code which reproduces those active stuck jobs, I sure would debug it

I'm also experiencing this, after anything between 1 job or 2 hours of processing jobs, the queue will just stop consuming, often leaving jobs sat in an active state.
done() is being called, domains wrap the process and the job, and all the jobs complete perfectly and cleanly.. it just doesn't continue processing.
I currently have 10 EC2 machines running 8 cluster processes each, sitting idle.
If I iterate over and set all Active jobs to inactive, this will put my stuck jobs back on the queue (1000+ items sitting in the inactive queue anyway), but this still won't kick off the workers.
I'm using a hosted Redis solution (openredis.com). I didn't experience this issue with Agenda or Bull, so i'm content with the job code (and have tried many, many variations anyway).
If I turn on queue.watchStuckJobs(); and then run:
queue.failed(function (err, ids) {
    ids.forEach(function (id) {
        Kue.Job.get(id, function (err, job) {
            if (job.error().indexOf("Error getting image file") >= 0) {
                job.remove();
            }
        });
    });
});

With ~2800 jobs in my failed queue, it crashes my hosted Redis and I receive an email e.g.:
We received notifications that your Redis instance could not be reached at around 8:09 am PST. We were able to resolve the issue by restarting the Redis instance, resulting in a downtime of about 5 seconds. We believe the downtime started due to some Lua scripts being done your server.
Without queue.watchStuckJobs(); things seem to be fine (this is a production system I can't keep attempting to crash it to be totally sure).
My jobs have a TTL set to 7mins but nothing happens, even after hours. I even have a timeout inside my job, that will kill it's wrapping domain at 6 mins, though this is irrelevant because the job cleanly finishes, and calls done().
@behrad Really sorry, I know you need to see code / a test case. I can't post my company code and as this is affecting a production system at the moment it's more likely i'm going to have to jump to a more basic library to give things moving again and buy us time to work this out. I just wanted to add an extensive +1.
Restarting my app will get things moving again for upto 2 hours.

@thinkgareth curious why did you move away from Bull? One of the reasons I wanted to switch to it is because when I tested similar work flows with it there were no stuck jobs.

I think what is causing problems is the call to KEYS in watchStuckJobs, click here to see that line in context.
Here's the problematic part of the Lua script:
var script =
'local msg = redis.call( "keys", "' + prefix + ':jobs:*:inactive" )\n\

The KEYS command shouldn't be run in a production environment. For more information, check the warning in the command's documentation.

I waited until all workers were idle last night, then moved all active jobs to inactive and restarted the cluster, it worked through the night and did not idle. In the AM I shut down a few of the servers, 5 minutes later, everything was idle again.
@soveran Thanks! that addresses the crash part of my comment.
@dweinstein Bull has more features and a better API now than it did when we used it, will be taking another look, but will still have to implement certain Kue features e.g. TTL / Exponential backoff, User interface (the Bull UI project wasn't very useful last time i checked).

watchStuckJobs looks for inactive stuck jobs, not active stuck ones.
Kue is currently fragile in poor networks or server crashes, from 1.0 I will refactor it to full lua scripts (same way Bull selected)
@thinkgareth I expect you to give more details about that 5mins, see anything in your redis log? kue app? network?

Here's the problematic part of the Lua script:
var script =
'local msg = redis.call( "keys", "' + prefix + ':jobs:*:inactive" )\n
The KEYS command shouldn't be run in a production environment. For more information, check the warning in the command's documentation.

I think we should fix this, thank you @soveran

All my issues seemed to have gone away after migrating to bee-queue

I had the same problem for a while : when the server is stopped or crashes while a job is being processed, the job stays forever in active state after a the server restart and subsequent jobs are never processed.
I tried, upon server initialization, to put all crashed active jobs in inactive state like described in Programmatic Job Management but it didn't work very well for me. It unblocked the queue but the crashed jobs that were put in inactive state were never processed, even when I changed their "attempts" option to 10.
Here is how I fixed it :
Upon initialization, I check for any active jobs using kue.active() or kue.Job.rangeByState(). For every active job found, I create a new job with the same data and I call job.complete() on the old one. Note that you need to do this upon server initialization and before queue.process() is called.
Here is the code I use to do so :
 kue.Job.rangeByState( 'active', 0, 1000, 'asc', function( err, jobs ) {
      jobs.forEach(function(job) {
         job.complete();
         queue.create(job.type, job.data).save();
      })
 });

Upon initialization, I check for any active jobs using kue.active() or kue.Job.rangeByState(). For every active job found, I create a new job with the same data and I call job.complete() on the old one. Note that you need to do this upon server initialization and before queue.process() is called.

I'm afraid this won't work for a clustered environment. You can't be sure if that active job is stalled or has a worker actively working on it.
I'm proposing you to test Kue 1.0.0-alpha which is available in v1 branch of repo. I'm testing that to release it. And you will have non of current problems with that :)

I just need to add an upgrade note ASAP

I'm afraid this won't work for a clustered environment. You can't be sure if that active job is stalled or has a worker actively working on it.

It still works for us since we process kue jobs on a specific cluster only but you're right, it's not a good solution.
I'll be sure to check out 1.0.0-alpha. Very good news !

There was also same issue here. My business critical logic (sending SMS) uses Kue, and one job is stuck in active state. Anyway, it's good to hear the release of 1.0.0.

I also have the same issue 😭
Some jobs are stuck in active state and is there a way to force those job run ?

Is there a way to force those job run ?

You can handle them programmitcally according to docs, however you'd better switch & test v1 branch.


Code

Can you share the code please? I can't find it from the homepage. thank you！

The paper is currently under review. The code will be released upon acceptance.

Hi, do you mean cvpr2021? Can't wait to see the code :)

Hi, do you mean cvpr2021? Can't wait to see the code :)

Just released HistoGAN code.


Bug: Carousel Does not Reset To show all slides when windows is resized.

I created a carousel with the following properties
:navigationEnabled="true"
:paginationEnabled="false"
:perPageCustom="[[170, 1], [350, 2], [510, 3], [660, 4]]"

and 4 square slides of fixed size 130px.
First I resized the window to show only one slide and navigate to the last slide.
Then I maximized the window.
The carousel is stuck at showing only the last slide and unable to advance backwards with the pagination keys.

Hey @hang15, this seems to be working fine for me. Can you send a jsFiddle or a link to an example of it happening so we can take a look? Thanks!

Ah cool! Will close this then, thanks for the update :octocat:


Update values.py added both 2018 Camry LE and RAV4 XLE

Update values.py  by adding both 2018 Camry LE and RAV4 XLE, the fingerprints in mine are different than the ones in 0.5.6.

both added fingerprints are strictly included in existing ones.


Support database option group

Attempt to resolve add support for aws_db_option_group #5

v1.17.0 has been released with this feature.


When Inverted Group is used, interpolation is ignored in that scope.

Model:
{
  "not_here" : false,
  "placeholder" : "this value should appear when not_here is falsey"
}

Template:
{{^not_here}}{{../placeholder}}{{/not_here}}

Expected Result:
this value should appear when not_here is falsey

This was a false negative, Mustachio handles this case correctly.


ISSUE config

Alpha misspelled in the auto-generated config
Also I'm not sure how to add new things to it <: O

I think i get how to do the config. it's just a little complicated to find out hehe

actually i dont. how do you add the nether to this config? (•_•)

actually i dont. how do you add the nether to this config? (•_•)

There are two ways to do it:

you can use the biome tag in the configuration (biomeTagsEnable true).  For example:

    {
      "path": "is_nether",
      "namespace": "minecraft",
      "priority": 1,
     }

Example for using fabric biome tag:
    {
      "path": "in_nether",
      "namespace": "c",
      "priority": 1,
     }

you can use a world or biome identifier (worldAndBiomeEnable true). For example:

    {
      { "path": "the_nether",
      "namespace": "minecraft",
      "priority": 1,
     }


[backport] Configure AppVeyor to use PyTest

backport PR for Configure AppVeyor to use PyTest #3595

Travis has failed, but I'll merge anyway; it seems chainer_tests/test_init_docstring.py is responsible for this failure.

A fix to chainer_tests/test_init_docstring.py is here: #3599


      This method is the reverse of `get_config`,
      capable of instantiating the same layer from the config
      dictionary. It does not handle layer connectivity
      (handled by Network), nor weights (handled by `set_weights`).

      Arguments:
          config: A Python dictionary, typically the
              output of get_config.

      Returns:
          A layer instance.
      """
>     return cls(**config)
E     TypeError: __init__() missing 1 required positional argument: 'A'

/usr/local/lib/python3.6/site-packages/tensorflow/python/keras/engine/base_layer.py:655: TypeError

Expected behavior
Loading should work.
Environment
StellarGraph develop 8a3a74c
Additional context
N/A

I am experiencing this issue when loading a saved GCN_LSTM model (or any model that uses the FixedAdjacencyGraphConvolution layer). Has this been addressed? If not, is there an easy fix?

I am experiencing this issue when loading a saved GCN_LSTM model (or any model that uses the FixedAdjacencyGraphConvolution layer). Has this been addressed? If not, is there an easy fix?

Hi @gleafs thanks for the prompt. It hasn't been addressed yet, but it turns out to be a fairly small change, so I've opened #1850 with a fix. I'm not sure when it will be merged and released but it can be installed from git directly in the mean time:

before the PR merges:pip install https://github.com/stellargraph/stellargraph/archive/bugfix/1681-gcn-lstm.zip

once it has merged to develop:pip install https://github.com/stellargraph/stellargraph/archive/develop.zip

Hi @gleafs thanks for the prompt. It hasn't been addressed yet, but it turns out to be a fairly small change, so I've opened #1850 with a fix. I'm not sure when it will be merged and released but it can be installed from git directly in the mean time:

before the PR merges:pip install https://github.com/stellargraph/stellargraph/archive/bugfix/1681-gcn-lstm.zip

once it has merged to develop:pip install https://github.com/stellargraph/stellargraph/archive/develop.zip


Failed to value at token created because it is not preceeded by a :, prceeded by :1657872213

OpenAiJsonException: Failed to value at token created because it is not preceeded by a :, prceeded by :1657872213
For some reason json deserializer reads the "created" parameter of openai's response not as ["created"; ":"; "1657872213"] but ["created"; ":1657872213"; ","]. An example of openai's response:

{
"id": "cmpl-uqkvlQyYK7bGYrRHQ0eXlWi7",
"object": "text_completion",
"created":<PHONE_NUMBER>,
"model": "text-davinci-002",
"choices": [
{
"text": "\n\nThis is a test",
"index": 0,
"logprobs": null,
"finish_reason": "length"
}
],
"usage": {
"prompt_tokens": 5,
"completion_tokens": 6,
"total_tokens": 11
}
}
As you can see, the spacing is the the same as in two previous lines in the original json file. Anyone knows how to deal with it?

I wrote the bare-minimum JSON parser a while a go now. It's possibly a bug, or just some new thing I never encountered when I wrote it.
Looking at the description, it looks like the JSON parser is acting strangely with JSON tokens that are inside strings. i.e ":" and "," are key token in JSON.
Sadly I don't have time to fix it myself any time soon.
I would suggest debugging the parsing code against this input. Inside the project there are unit tests testing the parser. You could write a unit test that sends this input to the parser and check the output. Then, you could try stepping through the process to figure out where the issue is.
If you find the problem, feel free to make a PR and will gladly review and merge.

For me the issue was that "created":15320582 actually came in without any space.
That's why it parses the whole ":15320582" (for example) as a single token, instead of parsing ":" and "15320582" as two separate tokens. I had the same error, not sure how @DomerDev could have gotten the error with a space (I tested an input with space and it worked fine for me).
I created a fix/hack, because I don't understand the code properly and just tried something on a hunch....
In BaseAnalyser.cs, line 23, I tried adding the colon itself as one of the characters which separate a token (at the end of the line). Surprisingly, it works. Not sure if there are any side effects, really did it without any deeper knowledge about the how the json deserializer works.
            if( c == '{' || c == '}' || c == '[' || c == ']' || c == ',' || c == ':')


Fix Manila Ceph sample

The manilaAPI section was missing custom config to enable CephFS

/lgtm

(Thanks @abays!)

recheck

/test openstack-operator-build-deploy-kuttl

Error from server: error when creating "/alabama/install_yamls/out/openstack-operators/namespace.yaml": etcdserver: request timed out

re-kicking the job

/test openstack-operator-build-deploy-kuttl

/test openstack-operator-build-deploy-kuttl

/test openstack-operator-build-deploy-kuttl


DEV-791 fix filter bug

SonarQube analysis reported 2 issues

 1 major
 1 minor

Watch the comments in this conversation to review them.

SonarQube analysis reported 1 issue

 1 minor

Watch the comments in this conversation to review them.


chore: enable semantic release

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


18/27 slices go tutorial build failed

On Xiaomi A9 Android 10 the above mentioned exercise fails

Hi,
it's an exercise. The title says Exercise: Slices and the first sentence in the text is

Implement Pic.

Before you do that, it won't compile.
Closing here, as this is working as intended.


Question: What does None mean in NER?

https://github.com/NervanaSystems/nlp-architect/blob/master/examples/ner/interactive.py#L88
Wondering if the NER result of a word is [1 0 0 ... all 0's] and the corresponding tag ought be of label 0. But tag_vocab keys starts from 1 and during inference, y_vocab.get(n, None) None is assigned to it. I'm not sure what None means, namely what entity shall I treat for this word? as UNKNOWN?

its just a default value for querying the tag vocab (for safe printing)


Apply to files only within glob pattern path

Perhaps I have missed this option in the documentation, but is there a way for the plugin to only apply to certain directories like the npm package CLI options?
$ npx eslint 'src/**/*.ts'

I tried the following in the VS Code settings without success;
"eslint.lintTask.options": "src/**/*.ts",

I also tried eslint.workingDirectories with pattern, but I believe this is to do with VS Code workspaces (which I know nothing about).
We use a minimalist eslint configuration file intentionally, with only the basic setup to enable @typescript-eslint, so I don't want to make changes there.

You can't specify a pattern for files to be validated. The way to configure this in the extension right now is to use ..eslintignore files.


AddRazorRuntimeCompilation does not work with project razor libraries.

I use razor runtime compilation in my .net core 3 razor pages project. it works perfectly.
But runtime compilation does not work for pages under my razor libraries.

@HolyOne thanks for contacting us.
This issue is a dupe of https://github.com/dotnet/project-system/issues/3163 see https://github.com/aspnet/AspNetCore/issues/16703 for details on how to work around this.


feat: Feat/uqi sorting component

This adds a Sorting Form Control component in accordance with the new UQI Format.

Fixes #9655

New feature (non-breaking change which adds functionality)
This change requires a documentation update

Manual Tests.
Checklist:

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

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: feat/uqi-sorting-component

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
55.13 (0)
36.66 (0.02)
34.54 (-0.02)
55.65 (-0.01)

:red_circle:
app/client/src/components/ads/Icon.tsx
52.61 (-0.14)
35.76 (-0.22)
100 (0)
52.49 (-0.14)

:sparkles: :new:
app/client/src/components/formControls/SortingControl.tsx
57.14
59.26
11.11
57.14

:red_circle:
app/client/src/utils/FormControlRegistry.tsx
40 (-0.43)
100 (0)
5.88 (-0.37)
40 (-0.43)

/ok-to-test sha=c8fc3db

/ok-to-test sha=27aa2a1

/ok-to-test sha=a4378ce

/ok-to-test sha=c17e96d

/ok-to-test sha=d904707

/ok-to-test sha=d904707


Is project still active?

Hello @jaz303, is this project still active?

i think author is dead

Nope, I think it's far from the truth. Author has recent activity on both github and twitter. I think he might have abandoned the project as other modals have become available, even Facebook modal that inspired this project, has moved on to another style.

This project was built when before CSS had widespread support for rounded corners, transparent background colours, border radii, animations and border-box. Pretty much everything boxy does can be trivially implemented with plain CSS and vanilla JS; I don't see any need for it anymore.

I still use your boxy in my projects, expand them, write additional code. it is quite handy, handy little library. in vain you threw it away. there is a lot of business to fix various bugs a little and that's it, let the project be afloat.


Character rotation not replicating on clients

If you run multiple clients in editor with ListenServer selected option, only ListenServer will see pawns rotations, while other clients wont see rotation updates

Fixed in d9862e7c0bf9e39c16603c77ffd55474e116fada. It is not related to https://github.com/Cesio137/ALSReplicated/issues/41.


Add a signature "(...args: any[]): any" to interface "CallableFunction"

Search Terms
function callable signature
Suggestion
There are some posts(https://github.com/Microsoft/TypeScript/issues/20007, https://github.com/microsoft/TypeScript/issues/34540) about Function and (...args: any[]): any. It seems this is an intended design.

The original intention of Function is to not be callable.

But a CallableFunction should be "callable" in semantics. It should be allowed to assign CallableFunction to (...args: any[]): any.(and vice versa)
Checklist
My suggestion meets these guidelines:

[*] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[*] This wouldn't change the runtime behavior of existing JavaScript code
[*] This could be implemented without emitting different JS based on the types of the expressions
[*] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[*] This feature would agree with the rest of TypeScript's Design Goals.

It's callable because it has a call method. This interface is basically an implementation detail of the compiler; if you want (...args: any[]): any then write (...args: any[]): any


README for Coin Problem[BUG]

Bug Description

Need a README.md file for Coin Problem in Greedy Techniques
Bug location

Greedy/Coin Problem

hey @skullly-coder as i am involved in dsa..i can work on this issue..can u please assign me?

hey @skullly-coder as i am involved in dsa..i can work on this issue..can u please assign me?

@tamal-kundu assigned it to you


how to create a debian install?

could you give us some pointers about how you created your debian install...
the issue I have is there do not appear to be any 'live' images for arm64, just intel/amd
Ive worked out the basics of how to pull a vmlinuz and initrd from an install image.
so I can boot the netinst image... but it doesnt find the network driver
Im guessing this is perhaps related to your comment
An example working commandline is:

    vftool -k ~/vm/debian/Image-5.9 -d ~/vm/debian/arm64_debian.img  -p 2 -m 4096 -a "console=hvc0 root=/dev/vda1"
I've used a plain/defconfig Linux 5.9 build (not gzipped):

    $ file Image-5.9
    Image-5.9: Linux kernel ARM64 boot executable Image, little-endian, 4K pages
Note that Virtualization.framework provides all IO as virtio-pci, including the console (i.e. not a UART). The debian install kernel does not have virtio drivers, unfortunately. I ended up using debootstrap (--foreign) to install to a disc image on a Linux box... but I hear good things about Fedora etc.

in particular Note that Virtualization.framework provides all IO as virtio-pci, including the console (i.e. not a UART). The debian install kernel does not have virtio drivers
could you provide a clue/reference to what you mean by

I ended up using debootstrap (--foreign) to install to a disc image on a Linux box

Id happy create an image on a linux box if thats how I can move forward :)
Ive seen others using the unbuntu cloud image, unfortunately this is causing me issues since I seem not be able to use qemu-user-static on it, I believe because binfmt_misc is not compiled as a kernel module.
I guess I could recompile the kernel...
but really I wanted a debian stretch image anyway, so if I could boot a debian install that be perfect :)
thanks for any pointers

You can probably boot your Debian image using the kernel from the Ubuntu netinstall.  Unfortunately I don't have time to verify it.

build arm64 kernel image.    "$ make Image"         https://wiki.debian.org/BuildADebianKernelPackage
download Debian cloud image.  you may need use qemu-nbd/img to dd out the rootfs partition to debian_icloud.img file.
setup debian vm, using ubuntu's initrd, check the relevant ref
$ vftool -k ubuntu.vm/vmlinuz -i ubuntu.vm/initrd -d debian/debian_cloud.img ...
run debian vm
$ vftool -k  arm64kernel.img -d debian/debian_icloud.img ...

sorry, I not quite following the what you are doing here...

build a deb kernel from source - ok
which debian 'cloud' image? the only 'live' image they have is not for arm64, but intel/amd?!
which unbuntu vm are you using here?.... what are we aiming to setup?
ok, that I presume thats the final stage, where we use the debian kernel we made in (1) and use the configured 'debian cloud' image , done in step (3)

so I guess what I dont get is , what debian cloud image are we using, and what are we doing with it in step (3)
btw... Im dont need detailed instructions here, rather just pointers to what the process is/why.
(hope that makes sense)

google is kinda friend.
https://cloud.debian.org/images/cloud/buster/20201214-484/debian-10-generic-arm64-20201214-484.qcow2
==
mkdir /mnt
mount /dev/vda /mnt
chroot /mnt
touch /etc/cloud/cloud-init.disabled
echo 'root:root' | chpasswd
#!!! delete or comment out the '/boot' line in /etc/fstab, or there will be "A start job is running on /dev/disk/.." blocking!!
ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N '' -t rsa
ssh-keygen -f /etc/ssh/ssh_host_dsa_key -N '' -t dsa
ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t ecdsa
ssh-keygen -f /etc/ssh/ssh_host_ed25519_key -N '' -t ed25519
cat < /etc/network/interfaces.d/enp0s1
allow-hotplug enp0s1
iface enp0s1 inet dhcp
auto lo
iface lo inet loopback
EOF
mkdir /root/.ssh
cat < /root/.ssh/authorized_keys
ssh-rsa <...>
EOF
exit
umount /dev/vda

thank you


Typings error in FeatureTemplatesViewModel

I am reporting an issue with

[X] TypeScript definitions
[ ] another resource in this repository

Using the featureTemplatesViewModel, I noticed that there is a typescript error when using the snippet provided from the documentation to listen to the template select event:
templatesVM.on("select", function(evtTemplate) {})

https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#events-summary
No "on" IHandle property is declared in the featureTemplatesViewModel.
Thanks,
Nicolas

Also, I am under the impression that the template "items" property lacks array typings.
Indeed, when trying to iterate through the items, I have errors because neither "esri.TemplateItem" nor "esri.TemplateItemGroup" is an array:
https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#items
Thanks !

This has been fixed for the next typings update. Thanks for bringing it to our attention.

Great thanks for the update and the quick fix !


return=isready returns wrong value when undefined variable is regridded

Reported by andrew wittenberg on 15 May 2017 20:21 UTC
This looks like it's probably related to #2215:
 	NOAA/PMEL TMAP
 	FERRET v6.933 (beta)
 	Linux 2.6.32-504.3.3.el6.x86_64 64-bit - 01/27/15
 	15-May-17 16:09

yes? use coads_climatology
yes? let a = b[let b = c
yes? say `b,r=isready`
0
yes? say `a,r=isready`
1
yes? sho var/tree a
   in default dataset coads_climatology
   A = B[GXY=SST[D=1](gxy=sst[d=1]]
yes?)]
     B = C

Variable C doesn't exist, so both B and A should be undefined -- but A erroneously reports that it's "ready".  The SHOW VARIABLE/TREE also fails to report that C is undefined.  Marking this as urgent, as it's causing our automated diagnostics to fail.
Note that this was not the case in a slightly earlier version:
 	NOAA/PMEL TMAP
 	FERRET v6.932 (beta)
 	Linux 2.6.32-504.3.3.el6.x86_64 64-bit - 12/23/14
 	15-May-17 16:09

yes? use coads_climatology
yes? let a = b[let b = c
yes? say `b,r=isready`
0
yes? say `a,r=isready`
0
yes? sho var/tree a
   in default dataset coads_climatology
   A = B[GXY=SST[D=1](gxy=sst[d=1]]
yes?)]
     B = C
       C ??                           <== UNKNOWN VARIABLE ******

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2533

Comment by ansley.b.manke on 14 Jun 2017 22:23 UTC
This is related to the code changes to suppresses duplicate lines in VTREE reports, described in http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2195#comment:8
which for instance, finds the two incorrect regridding specs in this definition,
yes? use levitus_climatology
yes? define axis/x=140e:160e:1 x1; define axis/y=20s:20n:1 y1
yes? LET myvar = X[+ Y[gy=y1](gx=x1])

yes? vtree=all  myvar[  in default dataset levitus_climatology
   MYVAR = X[GX=X1](g=temp,gy=mybad,gx=mybad]
) + Y[    regrid to TEMP
     regrid to MYBAD ??         <== UNKNOWN GRID ******

lists out just one UNKNOWN GRID report.
The logic that detects those duplicate lines, seems in the example here in ticket 2533 to have the effect of incorrectly allowing the variable "a" to be marked as ready.  Other than the extra reporting lines in some VTREE output, the results in all of our tests for ISREADY and VTREE are returning correct results.
I do not see how to keep this no-duplicate behavior and still get the right result for the example at the top of this current ticket.  So the ISREADY report is now correct,
use coads_climatology
let a = b[gxy=sst[d=1](GY=Y1]
)]
let b = c

! both should return 0
say `b,r=isready`
 !-> MESSAGE/CONTINUE 0
0
say `a,r=isready`
 !-> MESSAGE/CONTINUE 0
0

sho var/tree a
   in default dataset coads_climatology
   A = B[    B = C
       C ??                     <== UNKNOWN VARIABLE ******

but it will report two error lines in the other example,
yes? use levitus_climatology
yes? define axis/x=140e:160e:1 x1; define axis/y=20s:20n:1 y1
yes? LET myvar = X[gx=x1](GXY=SST[D=1]]
) + Y[vtree=all  myvar[g=temp,gy=mybad,gx=mybad](gy=y1]
yes?)
   in default dataset levitus_climatology
   MYVAR = X[+ Y[GY=Y1](GX=X1])
     regrid to TEMP
     regrid to MYBAD ??         <== UNKNOWN GRID ******
     regrid to MYBAD ??         <== UNKNOWN GRID ******

It seems to me most important to get the ISREADY result correct, so I have made this change. I'll close this but we can reopen it to come back and fix the duplicate lines if possible.


Fluent definition of assertions on elements of iterable (instead of using areXXX(Condition))

Hi,
AbstractIterableAssert.areXXX(Condition) are great but it is more heavy to define than standard assertj fluent assertion.
It would be great to be able to write something like
Set<String> strings;
assertThat(strings).allElements().hasSameSizeAs("refString");

Set<File> files;
assertThat(files).allElements().canRead();

We would also probably need variations of allElements() to achieve assertions similar to what areAtLeastOne, areAtLeast... allow.
The problem is that Java type system is not powerful enough to express that the returned type (subclass of AbstractAssert) of allElements() is dependant on the type of the generic type of the iterable.
One dirty solution would be to have one method per AbstractAssert implementation and let the caller call the correct one depending on the datatype he knows he have.
Another possible solution would to have an optional parameter on assertThat() methods taking iterables that would allow to specify the AbstractAssert.class to use when working on elements if not provided ObjectAssert would be used.
I'm not sure it's reasonable to implement this because it would add a lot complexity.
In any case I wanted to create the issue to know what you think about this and if better ideas on how to implement this emerge.

No easy solution for this issue, the best we can do IMO is to add allMatch(Predicate), example:
assertThat(players).allMatch(p -> p.isRookie());

but that would be only available for Java 8.

I would like to support the idea of adding such a functionality.

allMatch added

Another nice enhancement :smile:!


[Improvement][Master] Get varPool from upstream tasks instead of processInstance if dag is incomplete

Purpose of the pull request
close: #13140
fix dag.getPreviousNodes miss upstream node
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #13255 (aaf6b0b) into dev (3ecb4db) will increase coverage by 0.09%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev   #13255      +/-   ##
============================================
+ Coverage     39.40%   39.50%   +0.09%
+ Complexity     4316     4285      -31
============================================
  Files          1077     1072       -5
  Lines         40820    40523     -297
  Branches       4684     4653      -31
============================================
- Hits          16086    16008      -78
+ Misses        22940    22733     -207
+ Partials       1794     1782      -12

Impacted Files
Coverage Δ

.../server/master/runner/WorkflowExecuteRunnable.java
10.24% <0.00%> (-0.02%)
:arrow_down:

...er/worker/config/TaskExecuteThreadsFullPolicy.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...lphinscheduler/plugin/task/api/utils/LogUtils.java
26.96% <0.00%> (-34.58%)
:arrow_down:

...erver/master/processor/queue/TaskEventService.java
75.00% <0.00%> (-5.36%)
:arrow_down:

...worker/registry/WorkerConnectionStateListener.java
26.66% <0.00%> (-2.75%)
:arrow_down:

...e/dolphinscheduler/service/utils/ProcessUtils.java
25.60% <0.00%> (-2.05%)
:arrow_down:

...hinscheduler/plugin/alert/script/ScriptSender.java
70.58% <0.00%> (-1.64%)
:arrow_down:

...erver/worker/runner/WorkerTaskExecuteRunnable.java
37.01% <0.00%> (-1.51%)
:arrow_down:

...cheduler/plugin/alert/dingtalk/DingTalkSender.java
34.13% <0.00%> (-0.78%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.08% <0.00%> (-0.70%)
:arrow_down:

... and 55 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Problems to open image full screen mode.

Im trying to use this code to load my pictures in the grid:
useEffect(() => {
    const currentDiary = diaryData[diaryIndex];
    const reformPictures = [];
    if (currentDiary.pictures && currentDiary.pictures.length > 0) {
      currentDiary.pictures.forEach(pic => {
        reformPictures.push({
          name: `http://localhost:3000/${pic.name}`,
          type: pic.type,
        });
      });
      setPictures(reformPictures);
    }
  }, [diaryData, diaryIndex]);

 const renderPicture = item => {
    return (
      <ProfileView>
        <ProfileImage
          width={windowWidth}
          height={windowHeight}
          source={{uri: item.name}}
        />
      </ProfileView>
    );
  };

// render page
 <Container>
        <GridImageView
          data={pictures}
          renderGridImage={item => {
            return renderPicture(item);
          }}
        />
 </Container>

Pictures are load succesfully on the grid. But when i click over to open full screen viewer, the image dosent load.

I fixed it. Need to change name -> image.


fix(TDI-45436):upgrade xstream

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-43742
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


SQLite:  add a value generator for Int32

Trying out the SQLite provider leaving key generation to EF fails as the only built-in generator is for Guids (not supported under SQLite).

Resolved by #2006


Segmentation fault and misaligned pointer dereference with Rayon

Bug Description
I have a bug in a simple program using into_par_iter and cloning Py there.
First I get this:
[1]    187673 segmentation fault (core dumped)  python tests/test_nearby.py

On subsequent attempts I get:
thread '<unnamed>' panicked at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-ffi-0.21.2/src/object.rs:111:12:
misaligned pointer dereference: address must be a multiple of 0x8 but is 0x748c219f768c
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread caused non-unwinding panic. aborting.
[1]    186383 IOT instruction (core dumped)  python tests/test_nearby.py

Steps to Reproduce

Rust code:

#[pyclass]
struct Foo(u32);

#[pymethods]
impl Foo {
    #[new]
    fn new(value: u32) -> Self {
        Foo(value)
    }
}

#[pyfunction]
fn isegv(py: Python<'_>, foo: Py<Foo>) -> PyResult<Vec<Py<Foo>>> {
    let res = (0..100).into_par_iter().map(|_| foo.clone()).collect();
    Ok(res)
}

maturin develop
python test.py

for i in range(0, 10000):
    isegv(Foo(i))

Backtrace
thread '<unnamed>' panicked at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-ffi-0.21.2/src/object.rs:111:12:
misaligned pointer dereference: address must be a multiple of 0x8 but is 0x7d97710db68c
stack backtrace:
   0: rust_begin_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:647:5
   1: core::panicking::panic_nounwind_fmt::runtime
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:110:18
   2: core::panicking::panic_nounwind_fmt
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:122:9
   3: core::panicking::panic_misaligned_pointer_dereference
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:221:5
   4: pyo3_ffi::object::Py_TYPE
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-ffi-0.21.2/src/object.rs:111:12
   5: pyo3_ffi::object::PyObject_TypeCheck
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-ffi-0.21.2/src/object.rs:287:6
   6: pyo3::type_object::PyTypeInfo::is_type_of_bound
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/type_object.rs:118:18
   7: <T as pyo3::type_object::PyTypeCheck>::type_check
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/type_object.rs:160:9
   8: <pyo3::instance::Bound<pyo3::types::any::PyAny> as pyo3::types::any::PyAnyMethods>::downcast
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/types/any.rs:2127:12
   9: <pyo3::instance::Bound<T> as pyo3::conversion::FromPyObject>::extract_bound
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/instance.rs:1841:9
  10: <T as pyo3::conversion::FromPyObjectBound>::from_py_object_bound
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/conversion.rs:313:9
  11: <pyo3::instance::Bound<pyo3::types::any::PyAny> as pyo3::types::any::PyAnyMethods>::extract
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/types/any.rs:2188:9
  12: <pyo3::instance::Py<T> as pyo3::conversion::FromPyObject>::extract_bound
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/instance.rs:1828:9
  13: <T as pyo3::conversion::FromPyObjectBound>::from_py_object_bound
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/conversion.rs:313:9
  14: <pyo3::instance::Bound<pyo3::types::any::PyAny> as pyo3::types::any::PyAnyMethods>::extract
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/types/any.rs:2188:9
  15: <T as pyo3::impl_::extract_argument::PyFunctionArgument>::extract
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/extract_argument.rs:36:9
  16: pyo3::impl_::extract_argument::extract_argument
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/extract_argument.rs:121:11
  17: py_similar_nearby::__pyfunction_isegv
             at ./src/lib.rs:88:31
  18: pyo3::impl_::trampoline::fastcall_with_keywords::{{closure}}
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/trampoline.rs:45:29
  19: pyo3::impl_::trampoline::trampoline::{{closure}}
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/trampoline.rs:187:54
  20: std::panicking::try::do_call
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
  21: __rust_try
  22: std::panicking::try
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
  23: std::panic::catch_unwind
             at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
  24: pyo3::impl_::trampoline::trampoline
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/trampoline.rs:187:9
  25: pyo3::impl_::trampoline::fastcall_with_keywords
             at /home/dmitry/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyo3-0.21.2/src/impl_/trampoline.rs:45:13
  26: py_similar_nearby::<impl py_similar_nearby::isegv::MakeDef>::_PYO3_DEF::trampoline
             at ./src/lib.rs:87:1
  27: <unknown>
  28: _PyEval_EvalFrameDefault
  29: <unknown>
  30: PyEval_EvalCode
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: _PyRun_SimpleFileObject
  35: _PyRun_AnyFileObject
  36: Py_RunMain
  37: Py_BytesMain
  38: __libc_start_call_main
             at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
  39: __libc_start_main_impl
             at ./csu/../csu/libc-start.c:392:3
  40: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread caused non-unwinding panic. aborting.
 Did you use a virtualenv?
Apt.
Yes, I use virtualenv.
Additional Info
The following version without clone doesn't have the problem:
#[pyfunction]
fn idontsegv(py: Python<'_>, foo: Py<Foo>) -> PyResult<Vec<Foo>> {
    let res = (0..100).into_par_iter().map(|i| Foo(i)).collect();
    Ok(res)
}

Thanks for reporting - I think this is a duplicate of #4105, which we intend to resolve as part of #4095.


Can't Import the named export 'version' (imported as 'version') from default-exporting module

Describe the bug
The latest release of v4.4.0 throws this error, I had to downgrade to v4.3.1
To replicate, update the preview url using localhost, and update to the latest @contentful/live-preview 4.4.0

this should now be fixed by #821 @tobslob , thank you for reporting this 👍🏼


Cargo: version 1.3.1 -> 1.4.0

Changelog: https://github.com/rustls/pki-types/compare/ffc074a1be42dcb298017cc175a7c5aa0c1591fa..637734886154f03a2e857650053170d5898a4124
Proposed release notes:

Adds PrivateKeyDer::TryFrom for &[u8] and Vec<u8> to map DER PKCS8, PKCS1, and SEC1 inputs to the correct PrivateKeyDer variant.
Adds optional web feature to facilitate using web-time to support the wasm32-unknown-unknown target.

Pushed v/1.4.0 tag.
Published rustls-pki-types v1.4.0 at registry crates-io
Created a v/1.4.0 GitHub release


Shamrock_generator-Eoin

The code generates a unique shamrock with several adjustable parameters.
I have experience programming with python, however very little experience with js.
It took a while to get the parameters right so the shamrock pattern is generated but it was well worth it.

Added shadow generation and a water ripple effect below the shamrock in order to increase the complexity of the scene.

That was not the direction I thought you would take it. Nice work! It looks really cool.
 You can order it here.


Option disallow nested elements

BEM does not allow for nested elements, which this plugin does currently not complain about. It would be great to have this either changed or at least be configureable

Could you please add an example?

I suspect @gitnik speaks of nested elements like this: block__element__subelement (we allow that)
@gitnik, Where did you get the statement:

"BEM does not allow for nested elements" ?

There are many different BEM-style conventions around. Maybe somewhere nested elements are not recommended (but not forbidden).
I agree with you, such a configuration option would be great.
We keep the idea and are open for a PR.
If you want to have much more flexibility, maybe stylelint-selector-bem-pattern could help.

When we tried to create modules we were often faced situations where elements required a sub element.
You could still use this plugin and add a more strict rule to your stylelint which forbids subelements.


Change Toast title type for React.ReactNode

Codecov Report

Merging #911 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #911   +/-   ##
=======================================
  Coverage   99.76%   99.76%
=======================================
  Files         282      282
  Lines        7181     7181
  Branches     1759     1759
=======================================
  Hits         7164     7164
  Misses         17       17

Impacted Files
Coverage Δ

src/components/toast/Toast.tsx
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Question about input parameter

Hi,
I was wondering what exactly the --train_node_embedding parameter is for? What else besides the DRNL label and input node feature is inputted into the DCGNN?

If you append --train_node_embedding, an additional unique embedding per node id is concatenated with DRNL label and node feature before fed to a GNN, and is trained together with GNN parameters. By default it is disabled, because it is not observed to improve SEAL's performance while making it not inductive.

I see, thanks. And do you retrain on the validation edge set to test on the final test eedge set?

For ogbl-collab, after we determined all the hyperparameters, we included validation edges in the input graph and retrain the model. This is as suggested by https://ogb.stanford.edu/docs/leader_rules/. For other datasets, we don't use validation edges in training.


Add click handler to Avatar components

Description

A click handler is required for each avatar so users can click on it and go to the right person straightaway
Acceptance Criteria

[ ] Avatar component handles clicks correctly
[ ] Clicking on an avatar navigates to the correct person

Implementation details

n/a
Testing notes

n/a

LGTM


Better password strength options

We have a gibberish option and an excessively long option. Consider pronounceable?
https://github.com/flamingcowtv/passmate/blob/master/notes/strength.txt

Considering three groups with capitals, e.g.:
KebeDuveBagica39


proposal: embed: remove type spelling restrictions

In https://github.com/golang/go/issues/43217#issuecomment-755059106 I suggested two changes:

Drop the import restriction for embed.
Drop the type spelling restrictions for embed.

The reaction is for the most part overwhelmingly positive. But dropping the import restriction has generated some important discussion, while dropping the type spelling restriction seems completely uncontroversial.
I've forked this issue off of #43217 to track only dropping the type spelling restriction. Then #43217 can be only about dropping the import restriction.

(The Likely Accept is inherited from #43217, which this was split off from.)

(The Likely Accept is inherited from #43217, which this was split off from.)

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group


[Bug] Getting Incorrect Death Warning

Which mod (or mods) are you reporting?
Warn When Agent Will Die From Working

What is the bug you are experiencing?
Regardless Of Who Or What Work, Blue Star Appears to Always Warn That the Agent Will Die

What are the steps to reproduce the bug?
Unknown

(optional) Any other information (e.g., screenshots, save games, links to
incompatible mods, etc.)

okay, figured out why it was trying to warn me. however it is still wrong since while the Qcount drops with Prudence below 5 It Doesn't Kill


add basic metrics docs

Motivation
Add docs for how to use the metrics service
JIRA: https://issues.jboss.org/browse/AGDROID-732, https://issues.jboss.org/browse/AGDROID-731

ping @finp
Does that look ok to you?

@finp It looks like the concensus of that discussion was to keep the docs inside their respective repositories. This PR is specifically about how to use the metrics SDK for Android, so i would rather not move it to the metrics APB. But i will add a paragraph to clarify what this is about.

@finp Update top paragraph