Making mesos task healthcheck configurable

The configurable parameters are delay, interval, timeout, grace-period
and max-consecutive-failures. More detail on these parameters at
http://mesos.apache.org/documentation/latest/health-checks/
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #4086 into master will decrease coverage by 5.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4086      +/-   ##
==========================================
- Coverage   86.14%   80.96%   -5.19%
==========================================
  Files         148      148
  Lines        7219     7249      +30
  Branches      438      442       +4
==========================================
- Hits         6219     5869     -350
- Misses       1000     1380     +380

Impacted Files
Coverage Δ

...scala/whisk/core/mesos/MesosContainerFactory.scala
61.81% <ø> (ø)
:arrow_up:

...la/src/main/scala/whisk/core/mesos/MesosTask.scala
86.11% <100%> (ø)
:arrow_up:

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.54%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-83.34%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
0% <0%> (-58.83%)
:arrow_down:

...ain/scala/whisk/core/invoker/InvokerReactive.scala
64.86% <0%> (-16.45%)
:arrow_down:

...la/whisk/core/database/cosmosdb/CosmosDBUtil.scala
92% <0%> (-4%)
:arrow_down:

...cala/whisk/core/containerpool/ContainerProxy.scala
94.02% <0%> (-2.07%)
:arrow_down:

... and 3 more

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 8851cab...7102ba6. Read the comment docs.

These changes are merged as part of https://github.com/apache/incubator-openwhisk/pull/4102
So closing this.


Fixing Publish Failure (#510)

Publish fails on poor searching of a nupkg file.
The issue is reported here.
On non en-US environments, MSBuild produces culture variant message. New-NugetPackage relies on the English string.

The main problem here is a wrong perspective.
We are dealing with a file path as a string not as a FileIO instance.

Closing in favor of similar changes merged in via PR #613

@anamnavi Nice, thank you for information. It took only 3 years. 🤣


sndjvu_format: annotation parsing errors

Parsing ANT* chunks is pretty different from the rest of the library's work—text vs. binary—so I've been using a separate Parsing type. This keeps the methods separate and also lets me use a &BStr instead of an &[u8] for the inner field (helps with Debug).
For similar reasons, I've also been using an AnnotationError type separate from the main ParseError. I'm now wondering whether ParseError should have an InAnt(AnnotationError) variant and accompanying From<AnnotationError> impl. It might be convenient for users of the library, but on the other hand it might muddle the interpretation of ParseError a bit.

All the type names have changed but this issue remains pertinent. The new sndjvu_format::parsing::Error is more complex (see all the machinery in sndjvu_format::parsing::internal) and hooking up annotation parsing errors to that type is correspondingly trickier, but I think it is worth doing.

resolved as of 6024565: annotation parsing will just emit parsing::Error instead of having its own error type


Kanban board

project link : https://github.com/yetemegn-telaye/catalog-of-my-things/projects/3
Note

There are three members in our team
Team member 1: @Dmambo
Team member 2: @yetemegn-telaye
Team member 3: @Trast00

Hi Team,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights 💯

Descriptive info ✔
Tasks distributed equally ✔

Optional suggestions
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Documentation: Fix typo. Add missing backtick

mockDOMSource missing closing bracket. Has a visible effect - the following sentence is shown in .

[ ] I added new tests for the issue I fixed/built
[ ] I ran yarn test for the package I'm modifying
[ ] I used yarn run commit instead of git commit

Hi @jameslawson, thanks for being involved in helping the framework. :)
The commit was for the HTML file, but we actually generate that automatically from source code. Could I ask you to do that change in dom/src/index.ts instead? I understand it's confusing that we have the HTML file too, and we're considering writing notes or warnings on how to avoid this problem in the future.

Thanks!


Missing scalar field in one-to-many self-relation example

Thanks to https://github.com/prisma/prisma/issues/2044#issuecomment-607966032 for pointing this out.
The example https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-schema/relations#one-to-many-self-relations is missing the scalar field teacherId Int and the @relation directive on teacher field has wrong value for fields (is [id], should be [teacherId])

Fixed by #375 - pardon delay and thank you! 💚


Time to DEPRECATE

For the first, THANK YOU for your efforts to maintenance this package!
I've use this package for years and I'm happy with it until l ask a question to myself "Why we put forms in Redux?" and the answer is that unnecessary!
Redux-form was a best package that I found a few years ago but today it's a wrong choice and I don't want any new devs have the same mistake like me!
As a developer perspective please DEPRECATE this package or at least noticed people considering before choosing this package and suggest to use another react form (w/o Redux) like Formik instead.

I tried over 4 hours to get the "new" material-ui v1 work with redux-form and couldn't do it. So i think you are right and i will have a look at Formik now.

If you're interested in a nearly identical API with an MUIv1 example, you might try React Final Form, by the same author as Redux-Form.


[Bug]: Editing data sources does not automatically synchronize the database

ODC version
ODC 4.2.0
OB version
any version of OceanBase
What happened?
Editing data sources does not automatically synchronize the database.
need to manually synchronize the database.
What did you expect to happen?
The database can also be automatically synchronized after editing the data source
How can we reproduce it (as minimally and precisely as possible)?
Edit the data source and replace the data source connection information.
Anything else we need to know?
No response
Cloud
No response

pass


Using rest params?

Nice lib! Docs say

(x) => {} matches an array with a single element eg.: [1], [[1, 2, 3]] (array with a single array), matches single character eg.: 'x' or matches a single number eg.:1
(x, xs) => {} matches array with more than one element. First parameter is the first element (head), second is others (tail)

Couldn't we use rest params to be more precise? If (x) => {} matches a single element I'd expect (x, y) => {} to match exactly two elements (array.length === 2). I'd use (x, ...xs) => {} to match an array with more than one element (first element (head) and others (tail)).

@donaldpipowitch nice idea! Yes it is possible, at least on ES6.
I'm started this project based on Haskell syntax, but your example can be useful for newcomers in functional programming to understand the last parameter tail concept.


Catch std::ios_base::failure by reference

This eliminates the following G++ warning:
zstr/src/strict_fstream.hpp:128:39: warning: catching polymorphic type ‘class std::ios_base::failure’ by value [-Wcatch-value=]

Duplicate of https://github.com/mateidavid/zstr/pull/11


Add some kind of favorite color list to highlighted users

Requested: http://hup.hu/cikkek/20161128/hupper_2?comments_per_page=9999#comment-2043707

Not favorite but user can apply same color from another user if she clicks on the color name.


Bug: Cannot find module '@oxlint/linux-arm64/oxlint'

pnpm exec oxlint --fix:
node:internal/modules/cjs/loader:1147
  throw err;
  ^

Error: Cannot find module '@oxlint/linux-arm64/oxlint'
Require stack:
-<EMAIL_ADDRESS>    at Module._resolveFilename (node:internal/modules/cjs/loader:1144:15)
    at Function.resolve (node:internal/modules/helpers:187:19)
    at Object.<anonymous> (/workspaces/WATS/node_modules/.pnpm/oxlint@0.2.3/node_modules/oxlint/bin/oxlint:22:13)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS>  ]
}

This happened after a recent update. I have not changed my configuration since. I am on an Mac M1 (ARM) running inside a DevContainer.

Does v0.2.4 fix this? I updated the bin file https://github.com/oxc-project/oxc/blob/main/npm/oxlint/bin/oxlint to handle musl / glibc.

Seems like it, yes! Thanks!


[Draft] Footnotes section func specs

Related Ticket(s)
#7698
Description
Added new functional specs for Footnotes section and Carbon list
Changelog
New

Footnotes section entry for wiki

Changed

N/A

Removed

N/A


Suggest a change to text for --frozen-packs option

Suggested to change text to:
new:
 --frozen-packs     Pack list and versions from cbuild-pack.yml are fixed and raises errors if it changes
current:
 --frozen-packs    The list of packs from cbuild-pack.yml is frozen and raises error if not up-to-date

replaced by https://github.com/Open-CMSIS-Pack/devtools/issues/1415


Update lr.js

Hi there i had made below changes for  better and improve readability in this lr.js file.
Replaced the usage of var with Const and let for variable declarations, ensuring better variable scoping and immutability where applicable.
Added comments throughout the code to provide clarity on the purpose and functionality of each section.
Extracted the https and path modules into separate require statements for better code organization and easier maintenance.
Simplified the conditional statement for checking the presence of apiKey and apiSecret in the configuration. Instead of using the === undefined comparison, I used the config.apiKey === undefined and config.apiSecret === undefined conditions directly in the if statement.
Introduced a new constant HELPER_PATH to store the path of the helper module, using the path.join function.
Refactored the request function by extracting repeated code into separate variables to improve code readability. Specifically, I moved the code related to isApiSecret, headers, and queryString into separate sections with meaningful variable names.
Simplified the conditional statement for checking the presence of formData before writing it to the request.
Renamed the response variable inside the resp.on('end') callback to parsedResponse to better reflect its purpose.
Updated the error message in the resp.on('end') callback to be more descriptive, specifying that a server error occurred.
Grouped related APIs together under separate sections using object properties, such as accountApi, roleApi, sottApi, etc., to enhance code organization and improve readability.

Many of these changes are covered in my PR: https://github.com/LoginRadius/node-js-sdk/pull/27
A main point of my changes was eliminating the reliance on any file system calls as they cause incompatibility with browser, as well as webpack or any post processing.


how to use --proxy-config in ng e2e modal?

i want to set the proxy in e2e modal? any idea?

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@filipesilva  i have solved this problem now , angular-cli e2e  load the  default server config.


Feat: Add Aliquot Sum of a Number algorithm, Class Math

Description of Change

Added the solution for getting Aliquot Sum of a Number. The corresponding link is here. This is the first time I'm contributing to this particular repository, so please do tell me if I messed up anywhere.
Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Umm, sorry to bother you @martin-sos but its been 3 days :sweat_smile:

Ummm, sorry to bother but why are we not merging this PR?

@Panquesito7 please take a look :sob:

I fixed them Panquesito (>.<)

Hey, @Panquesito7 uhhhhhhm, is it okay?

dies

Wait wtf :skull:

Check #2400 instead, Panquesito.


disconnect daodata from UI components

Remove DaoData from UI components
https://github.com/HausDAO/daohaus-monorepo/blob/master/libs/ui/src/components/organisms/MemberCard/MemberCard.tsx#L9
The UI contains 1 import from @daohaus/daodata - removing this unlinks ethers from the UI via ethers-utilities and removes any dependencies coming from daodata -- making our UI package alot smaller.

Do you still plan on finishing this @brossetti1?


ExternalNameSpace.setMap() causes NPE

setMap() sets this.externalMap to null, then calls
this.clear(), which tries call this.externalMap.clear().
Reported by: jeffdrost
Original Ticket: "beanshell/bugs/276":https://sourceforge.net/p/beanshell/bugs/276

Looks like fixed in 3c395bb07e157bc1bcfab7d285484495fa61c010

@opeongo tyvm
Closed: working


Adding ng-model to predefined Select element adds undefined option

Adding ng-model:"foo" to a prepopulated select element results in an additional "undefined" option being added and removes the effect of select:"select".
The HTML:
<select ng-model="foo" ng-app >
    <option value="1">1</option>
    <option selected="selected" value="2">2</option>
    <option value="3">3</option>
    <option value="4">4</option>
    <option value="5">5</option>
</select>

Becomes:
<select ng-model="foo" ng-app >
    <option value="? undefined:undefined ?"></option>
    <option value="1">1</option>
    <option selected="selected" value="2">2</option>
    <option value="3">3</option>
    <option value="4">4</option>
    <option value="5">5</option>
</select>

In the example above the first option  value="? undefined:undefined ?" is selected instead of the expected option value="2".
Reproduced at http://jsfiddle.net/K8rSu/

选择追踪依据

done!!

@pkozlowski-opensource Same problem, I think ? undefined:undefined ? should not be set as value. When a user choose nothing the ? undefined:undefined ? will be submitted as value.

I tried this and it worked,

I think that my problem with all of this is when you are rendering the select via PHP / Twig templates then allowing AngularJS to take over afterwards.
Why can't I just tell AngularJS to select based on the index of the option regardless of value?

     Thing

@trisweb , this is work for me.

@trisweb :+1:

the same problem

Bachelor Degree
Postgraduate Diploma
MBA
Master's Degrees
Doctorate (PhD)
Intermediate Certificate/ Institute

Agree with @itsmechlark comment

I just came into this problem as well. @itsmechlark has a good point. Framework should not provide a selected option if none is provided within Angular. "? undefined:undefined ?" just seems irresponsible from the framework.

This worked for me.
<select ng-model="foo" ng-init="foo='1' ">
    <option ng-selected="true" value="1">1</option>
    <option value="1">1</option>
    <option value="3">3</option>
</select>

Agree with @eyeamaman

I run across the same problem too,
the option value is generated by php script
<?php while ($row = $options->fetch_array()) { ?>
          <option><?= $row['title']?></option>
<?php }?>

I don't think I can use ng-init="foo='1'  to set default value ,cause I don't know the value in advance.

@robinclark007, it's a workaround (for a not-really-supported usecase), but you could try setting ngInit on the selected option. (You should know the value by then, right ?).

This can be a huge pain with traditional CMS work where you want to rely on the server for a lot of data (and not create a webservis for every bit of it) but still use angular. Here is a small directive to use in the place of ng-model, which will set your model's initial value based on the static markup (value, selected, etc) https://github.com/vespoli/init-model

I wrote a workaround for this issue in the form of a directive: https://gist.github.com/Tobiaqs/97fba556349281f2db90
Include ts-select-fix in your app dependencies.
<select ng-model="data.kindOfCheese">...</select>
becomes
<select ts-select-fix ng-model="data.kindOfCheese">...</select>
This directive allows you to:

Set a default value for a select
Render options using ng-repeat
Propagate UI changes to model

Plunker demonstrating the effect:
https://plnkr.co/edit/TCaqT1Kr37b1jQyyRSyv?p=preview

Using 'ng-selected="true' on the option tag I wanted to show as selected worked for me

I found a better answer.
html:

1
2
3
4
5

css:
#buggySelect option[value="? undefined:undefined ?"] {
display:none;
}
js controller:
$scope.foo = "2";
this will remove the blank option and point it back to the correct place.

@Fierfek Brilliant. Thanks mate.

This happens even when the initial value is defined and is a valid option.
HTML
<select ng-model='itemIndex' ng-init='itemIndex = 0'>
    <option value='{{$index}}' ng-repeat='item in lists.items' ng-selected='$parent.itemIndex === $index'>{{$index + 1}}</option>
</select>

Controller
$scope.itemIndex = 0; // Initialized here even though using ng-init in the HTML.

Oddly enough, this same code works later on the page for another <select> element.  The only difference is the index variable name and the list of items I repeat over (e.g. `ng-repeat='item in itemList``).  Everything is initialized the same way.

@c1moore, if you think this is a different problem, please open a new issue and provide a runnable demo (e.g. using CodePen, Plnkr etc).


cmake: use $MPI_INCLUDE as hint for gasnet

Using $MPI_INCLUDE as a hint will help cmake to find mpi-enabled version of gasnet in Fedora.
/cc: @tuxfan

I have no objections, as long as it doesn't break if MPI_INCLUDE is not present in the environment.
@chuckatkins , your thoughts?

While I'm not opposed to the idea, you would want to implement it a bit differently, like this:
if(GASNet_ROOT_DIR)
  set(_GASNet_FIND_INCLUDE_OPTS PATHS ${GASNet_ROOT_DIR}/include NO_DEFAULT_PATH)
else()
  set(_GASNet_FIND_INCLUDE_OPTS HINTS ENV MPI_INCLUDE)
endif()
find_path(GASNet_INCLUDE_DIR gasnet.h ${_GASNet_FIND_INCLUDE_OPTS})

This ensures that if GASNet_ROOT_DIR is specified then it's used exclusively.  Also the "ENV VARNAME" syntax rather than $ENV{VARNAME} is specific to find_* commands and takes some additional steps to deal with some OS level escaping issues.

Done!


test(consensus): test if untimely proposal is decided after multiple rounds

This test should fail with the current implementation in feature/pbts.
This test should pass when changes from  #2432 are implemented.
This is a proof of concept and should not be merged.

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[ ] Title follows the Conventional Commits spec

From @cason : The test unit added there is present in feature/pbts and passes.


Make "volatile" container

I would like to re-initialize my database with each restart.
This would make it much easier to run unit tests in a local environment.
Ideally, I would like to just delete the database without having to delete the Docker container.
What's the simplest way to accomplish this?
Thanks!

My apologies, this was meant for osixia/docker-openldap.
Created https://github.com/osixia/docker-openldap/issues/463.

My mistake.


"Add to Project" doesn't ask for the export folder

Hello,
we want to check-in our Logic App changes into our repository. Therefore we used the context menu option "Add to project". The problem with that is, that it only adds the files in the root folder of our workspace, and doesn't give the option to choose a subfolder.
But the file does already exist in a subfolder. This means we have to delete the original files and move the exported files into the subfolder. Or we copy and paste the code.
(It would be nice, if the files does sync directly with the extension)

It sounds like the request is to show a folder picker (defaulting to the root folder) instead of always choosing the root folder here.
https://github.com/microsoft/vscode-azurelogicapps/blob/main/src/commands/logic-app/addLogicAppToProject.ts#L25

Thanks for your answer. It doesn't have to be a folder picker. Could also be a setting. Or maybe some config file, for each LA, to define different folders.


Please invite me to the GitHub Community Organization

Please invite me to the GitHub Community Organisation.

Name: Ujjwal Goyal

Discord Username(if exists): importhuman

Additional Context:

:nerd_face:

Welcome @importhuman :nerd_face:

Thanks @krishdevdb, glad to join! Looking forward to contribute 😄

Thanks @krishdevdb, glad to join! Looking forward to contribute 😄

How about starting with our Hacktoberfest-Practice Repo @importhuman?

@importhuman Welcome enthusiast and have good start.
Enjoy it.

@krishdevdb Thanks, but as it's just for practice, I've picked up a different issue. 😄

@krishdevdb Thanks, but as it's just for practice, I've picked up a different issue. 😄

Np


chore: add none to textStyle overflow

related to https://github.com/apache/echarts/pull/14214

Seems we don't handle 'none' currently. null is used to disable overfull

Seems we don't handle 'none' currently. null is used to disable overfull

@pissang should we remove 'none' in doc?

@susiwen8 yes it makes sense


chore: keep java 8 compatibility

Maintain java 8 compatibility by just switching Optional.isEmpty to !Optional.isPresent

Could you let me know if the issue has been resolved or not for the contribution?

Could you let me know if the issue has been resolved or not for the contribution?

Hi, I'm not sure what you're asking about. What issue are you referring to? This change allows Moquette to build with Java 8 again, which worked until recently when a change introduced a requirement for Java 11.

@andsel Thank you very much for reviewing my other PR. This one is also ready for review. I'm not sure on your Java version compatibility thoughts, but this is the only 1 line of code that requires Java 11 and the Java 8 version isn't really any worse (IMO).

Java 8 is almost 10 years old. Last week Java 21 come out, I personally would push forward, for 0.18 would be nice to be not more older than JDK 17.

Why still support JDK 8, as per report the state of usage in production in 2023 for JDK 8  moved from 46% (2022) to 33% , so it's decreasing yoy, why still support it?

Right, I can certainly understand that. Of course you can do what you want, my only argument would be that raising the minimum version is not providing any benefit to the code. You may implement new features that rely on newer Java versions, but I'd just suggest to keep the minimum version the same until those new features are actually used.
This is your project so of course it is up to you, but I did want to offer my viewpoint and the simple fix (for the current state of what Java features are used).

I do not have any data to support it, but we use Moquette in Greengrass and Greengrass has a minimum supported version of JDK 8. The data from New Relic shows still 30% for Java 8 which seems pretty high still; and their data is primarily from cloud services too where it is easier to change the Java version. We're using Moquette in semi-embedded scenarios where people are unlikely to ever change the Java version if what they have is working.
Like I said in my previous reply, I feel that Java 8 should remain supported until you need (or maybe not need, but you at least want) a feature from a newer Java version which makes the code/project better.

@MikeDombo  you convinced me :-)

Ok awesome, thank you!


Running with pyside doesn't work

Issue:
I am trying to run rviz via python pyside:
import rospy
import sys

setattr(sys, 'SELECT_QT_BINDING', 'pyside')
import rviz

from PySide2 import QtCore, QtGui, QtWidgets
app = QtWidgets.QApplication(sys.argv)
frame=rviz.VisualizationFrame()
frame.setSplashPath("")
frame.initialize()

I get:
>>> import rviz Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/opt/ros/melodic/lib/python2.7/dist-packages/rviz/__init__.py", line 17, in <module>     from . import librviz_shiboken
Part of this: https://github.com/ros-visualization/visualization_tutorials/issues/51
Part of this: https://github.com/ros-visualization/visualization_tutorials/issues/52
Your environment

OS Version: Ubuntu 18.04
ROS Distro: [Melodic]
[ INFO] [1594919224.337276138]: rviz version 1.13.13
[ INFO] [1594919224.337304520]: compiled against Qt version 5.9.5
[ INFO] [1594919224.337312176]: compiled against OGRE version 1.9.0 (Ghadamon)

Pyqt4/5 installed
PySide and Pyside2 installed

Uncommenting this line and building from source seem to have fixed the problem. Still testing. But I suspect the Shiboken lib was just not built  I am  not sure if the reason it was no longer supported is fixed or not. but will try in a bit
TODO(wjwwood): re-enabled PySide2 support when it is fixed.
add_subdirectory(shiboken)

PySide support was disabled due to https://bugreports.qt.io/browse/PYSIDE-218.
I'm not sure this is fixed. You are welcome to validate the linked test script on a recent version of PySide shipped with Ubuntu 18.04. Note, that PySide is also disabled here (and you should have seen a corresponding cmake info):
https://github.com/ros-visualization/rviz/blob/291df89957e2f643a3fde28e5cb239fe1f6f5b73/src/python_bindings/shiboken/CMakeLists.txt#L14-L23
You might want to try PySide2 instead of PySide1. Not sure this is supported by python_qt_bindings.

Thanks I'll try passing that check too.
python_qt_binding for melodic talks about pyside2: http://wiki.ros.org/python_qt_binding
I'm not sure how I would make rviz use pyside2 tho, but I guess i need to find where it uses python_qt_binding and somehow setattr to pyside2?

Mmh. The python_qt_bindings   shiboken_helper  is all setup for Shiboken2 and PySide2. Its is looking for shiboken2 and fails to find it.  Anything that I find online says its suppose to be in /usr/lib/cmake/Shiboke....  But that doesnt exists.
It uses PYTHON_EXTENSION_SUFFIX: -x86_64-linux-gnu
to find it. But when I do

locate shiboken2
that doesnt really come up. Tho to be fair no .cmake files come up anywhere on the system.

apt show python-pyside2/shiboiken2
both show installed
I'm pretty clueless here. Trying to learn cmake by doing this :D
Also found this, but probs not related: ttps://bugreports.qt.io/browse/PYSIDE-508

Let's continue the discussion in #1526. Closing here.
By the way, I had issues installing python-pyside2 in Ubuntu 18.04. There were package requirements, which couldn't be fulfilled.
Hence, I just worked under Ubuntu 20.04.

Awesome, thanks for looking into it.
Sorry for the dumb question but:
So I also had pyside2 installation issues with apt-get but pip worked fine and I'm able to use pyside2 under 18.04 to create guis.
I understand apt-get is a system-wide install from canonical, but if virtual environment is not enabled  an install from pip still makes pyside2 available. But from messing around with it I'm guess pip doesn't install something (I guess cmake files) that is required during rviz build?

The python_qt_binding script searches for shiboken2, PySide2, and PythonLibs.
You should have a look into the cmake log and the file build/rviz/CMakeCache.txt to check, whether those were found.
Did you install the python2 or pyhton3 version of PySide? Python2 is required for ROS Melodic.


Error: Cannot destructure property 'media' of 'theme.sanity' as it is undefined.

Hello, when trying to use this plugin i get the following error message when click the "Duplicator" button in the navbar:
Error: Cannot destructure property 'media' of 'theme.sanity' as it is undefined.
TypeError: Cannot destructure property 'media' of 'theme.sanity' as it is undefined.
    at responsiveFlexItemStyle (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:11383:5)
    at Ne (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1058:14)
    at Ne (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1048:20)
    at Ne (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1059:252)
    at e4.generateAndInjectStyles (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:926:20)
    at http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1177:88
    at http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1179:8
    at O2 (http://localhost:3333/node_modules/.sanity/vite/deps/@sanity_cross-dataset-duplicator.js?v=03e5f1f3:1183:6)
    at renderWithHooks (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-5SD63G7R.js?v=06ac2227:12526:26)
    at updateForwardRef (http://localhost:3333/node_modules/.sanity/vite/deps/chunk-5SD63G7R.js?v=06ac2227:15221:28)

If it helps, here's where the error originates: It looks to be caused by @sanity-ui. I tried updating both @sanity/ui and sanity to the latest version, but that unfortunately didn't help. Maybe there could be a version conflict between your version (which seems to be 1.0.0) and the later versions?

Here's my studio config if it helps:
import { crossDatasetDuplicator } from '@sanity/cross-dataset-duplicator'
import { dashboardTool, projectInfoWidget, projectUsersWidget, sanityTutorialsWidget } from '@sanity/dashboard'
import { table } from '@sanity/table'
import { visionTool } from '@sanity/vision'
import { defineConfig, definePlugin, SchemaTypeDefinition, WorkspaceOptions } from 'sanity'
import { muxInput } from 'sanity-plugin-mux-input'
import { deskTool } from 'sanity/desk'
import Logo from './components/NomonoLogo'
import { API_VERSION, PREVIEWABLE_DOCUMENT_TYPES, workspaces } from './lib'
import { resolveProductionUrl } from './plugins/productionUrl'
import { defaultDocumentNode, pageStructure, singletonPlugin } from './plugins/structure'
import { schemaTypes } from './schemas'
import * as documents from './schemas/documents'

import './main.css'

const singletons = [documents.siteSettings.name, documents.checkoutSettings.name]

const sharedConfig = definePlugin({
	name: 'shareConfig',
	plugins: [
		deskTool({
			structure: pageStructure(Object.values(documents), singletons),
			defaultDocumentNode: defaultDocumentNode(PREVIEWABLE_DOCUMENT_TYPES)
		}),
		dashboardTool({ widgets: [sanityTutorialsWidget(), projectInfoWidget(), projectUsersWidget()] }),
		muxInput(),
		table(),
		singletonPlugin(singletons),
		resolveProductionUrl({ types: PREVIEWABLE_DOCUMENT_TYPES }),
		visionTool({ defaultApiVersion: API_VERSION }),
		crossDatasetDuplicator({
			// Required settings to show document action
			types: Object.values(documents).map((doc) => doc.name),
			// Optional settings
			follow: ['inbound', 'outbound']
		})
	],
	schema: {
		types: schemaTypes as SchemaTypeDefinition[]
	}
})

export default defineConfig(
	workspaces.map<WorkspaceOptions>((workspace) => ({
		...workspace,
		studio: {
			components: {
				logo: Logo
			}
		},
		plugins: [sharedConfig()],
		parts: []
	}))
)

Can you wipe node_modules and install again?

Yes, tried that now, unfortunately I'm still getting the same error :(
After that I also tried to make sure there's only 1 version of @sanity/ui (1.3.1) and react (1.8.2).
I also tried to create a minimal repro, but it works just fine there of course. Any ideas what it could be?

Usually this happens when multiple versions of Sanity are installed in a project and so there's a hook trying to read from the wrong context. I wonder if some other package is installing another version.

Yeah this happened for me in a monorepo structure using yarn berry workspaces. Needed to clear the root node_modules too.

Any found a fix for this? Getting this issue using Sanity embedded in Next.js. Package manager is pnpm.


fix python version support badge

The badge currently shows that python 3.6 to 3.10 are supported which is not true. Support badge should be changed to show 3.9 to 3.10.

Fixed in dev


Feat/ignore special grab

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

npm package (@latest dist-tag)
v1.3.0
GitHub release

Your semantic-release bot :package::rocket:


Error loading web.whatsapp.com

I'm trying to open web.whatsapp.com, but it always stays on the logo, does anyone know why it doesn't load?...I am using vb6

I'm trying to open web.whatsapp.com, but it always stays on the logo, does anyone know why it doesn't load?...I am using vb6

IMHO, magic number 49 (in miniblink49 projectname) mean(s) that this thing based on... chromium 49.0.... and Meta company don't like old builds of chromium...


Content of ToastSelectionBox and ToastSelectionBoxItem mingled

The schemas of ToastSelectionBox and ToastSelectionBoxItem are intermingled on this page and currently make no sense.

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

ID: 0ebc794c-dad4-28d6-b799-19b2daf922f3
Version Independent ID: 95d05b52-288a-1c6f-760a-0b57f3b115b2
Content: Toast content schema - UWP applications ▷ ToastSelectionBox
Content Source: windows-apps-src/design/shell/tiles-and-notifications/toast-schema.md
Product: uwp
Technology: design
GitHub Login: @hickeys
Microsoft Alias: hickeys

Hello. We apologize for the delay in resolving this issue. As we transition to a new feedback system, we are closing all outstanding issues. Any issues that can be addressed will be tracked using a different internal tool, and we regret that we won't be able to provide further updates on this particular matter. We value your input and assure you that all feedback is reviewed. We recommend visiting the Microsoft Q&A site, where your issue may have already been discussed.


feat: [CDS-59495]: add support for aws backoff strategy override

Describe your changes
Comment Triggers

PR Check triggers

Build: trigger build
Sub Category Field Check: trigger subcategoryfieldcheck

trigger build, subcategoryfieldcheck

trigger build, subcategoryfieldcheck


Atom does not start when using x2go

I first saw the issue for version v0.152.0 debian package in ubuntu 12.04 VM running on vmware ESXi.

$ [20853:1201/101159:ERROR:browser_main_loop.cc(162)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
Xlib:  extension "XInputExtension" missing on display ":10.0".
Xlib:  extension "XInputExtension" missing on display ":10.0".
App load time: 368ms
[20877:1201/101159:ERROR:gl_surface_glx.cc(333)] GLX 1.3 or later is required.
[20877:1201/101159:ERROR:gl_surface_x11.cc(57)] GLSurfaceGLX::InitializeOneOff failed.
[20877:1201/101200:ERROR:gpu_child_thread.cc(143)] Exiting GPU process due to errors during initialization
atom: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.

I then installed it from webupd8 team:

sudo add-apt-repository ppa:webupd8team/atom
sudo apt-get update
sudo apt-get install atom
However I got the same issue.

I compiled then from sources following all instructions from README but still got the same issue.

To replicate just right click on a file to get a context menu and once you start moving your mouse it will fail with the error above.

I updated to latest version debian package (186) won't even start. It will fail right up front with the same error.

I am on 0.179.0 and facing the same issue on Ubuntu 12.04.5 LTS (precise) with the Trusty Hardware Enablement Stack. If it matters, I am running this on a VM (i.e. most likely software rendering).

If this is the general "doesn't work without DRI GLX", consider this a me-too. Running latest release from source on Debian Jessie, in a Virtualbox VM accessed through a Cygwin X-server (which supports aiglx). Initially it crashes on startup because it can't find swrast, after installing swrast I get this error (here just using raw X from guest to host, no ssh forwarding):
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 259 error_code 2 request_code 12 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Updated from v177 to the latest version (186) today without a problem, using the .deb installer.

On Ubuntu 14.04 (Mint 17) as host (running X client) Atom.io will not run in either x2go or TurboVNC sessions for similar reasons.
So is Atom usable with any remote desktop software when running under Linux?
Is there a way to pass something like " --disable-webgl " to Atom?
Tried with Atom editor version: 0.192.

Answering my own question: tigervnc (v 1.4.3.) does the job!  Atom starts without a hitch.

Still would be good to know if we could disable unnecessary webgl, since there's no reason to use VNC to access a VM running on the same computer.

Confirming that it won't work for me either under X2Go due to the lack of GLX support. Chromium's --disable-gpu flag silences the complaints about GLX errors, but it still fails to connect to the X server despite this.

Same here using X2Go & Xubuntu 14.04 :(

Not that the distro's really matters it's an Atom issue, but this also is preventing Atom to work through X2Go on Manjaro.

rdesktop over VPN connection to a Ubuntu 14.04.2 LTS desktop fails with GLX 1.3 or later is required.
Atom version 0.202.0

Same thing on Debian Jessie amd64 using x2go client atom 1.0.11

@thomasjo Why is this closed without any information? Is the bug fixed?

@jrgifford Pretty sure I didn't mean to close this one. At the very least I don't understand why I did. Thanks for the heads up!

Another "me too" for this. Been hoping to try Atom for a while but my main dev environment is an X2go one, so no dice. Tried every possible chromium option I could think of that disabled GPU acceleration/WebGL but no dice. Chrome/Chromium on the other hand do work over X2go.

Me too... trying to use Atom via a manually compiled xrdp 0.9.0. Chrome, however, complaints in the same way as Atom, but starts fine:
$ /opt/google/chrome/chrome
Xlib:  extension "XInputExtension" missing on display ":10.0".

Same problem using Ubuntu 15.10 desktop.
Any workarounds yet?

I am also getting this issue on Ubuntu Mate 15.10

Same issue with dpkg install of v1.5 (atom-amd64.deb) on headless 12.04 server (bare metal) --> vnc

I was seeing the same error message and debugged it down to an X extension "BIG-REQUESTS". You can use xtrace to trace all the X traffic and I saw an 8MB message before it crashed.
I first disabled all extensions with (xtrace -e ) and that worked.
My final hack was to copy libxcb.so.1 into /usr/share/atom, open up in editor, and change 'BIG-REQUESTS' to '_IG-REQUESTS'. I figure when the client library asks if this extension is supported it will reply no and no more big messages.
hope this helps

@tonywmnix - the libxcb.so.1 hack worked for me with Ubuntu Mate 15.10 via XRDP. Thanks.

@tonywmnix & @IronicBadger
Could you please write a step-by-step instruction? I've no idea how you did it. When I view the file in mc I can't find 'BIG-REQUESTS'. There are only 'big_requests' but when I change them I get errors when running atom (something like "don't know what to do with _ig_requests...").
I've Windows10 host with Xubuntu 15.10 on Hyper-V and RDP session (not the most convenient solution but the only one working reasonably with UHD monitor).

@bs-ug I just used vi. Then search for the string and replaced it.

@IronicBadger - So simple! Thanks!

@tonywmnix libxcb.so.1 hack worked for me on Debian. Well done

And why not just use a symlink to the original file?
For cases when it is binded to a specific libxcb.so version then it would make sense to use this specific library file.

Just to give an update here that ubuntu 14.04 LTS with atom 1.5.4 debian package downloaded from https://atom.io/ works out of the box without any issues over xrdp. Cheers, - Nestor

+1 for @tonywmnix this really did fix the issue. It also fixes it for Visual Studio Code.
One of the rare times a GitHub issue saves you so much time. Thanks!

+1 to @tonywmnix 's solution. It works for me.
Ubuntu 14.04.3 LTS + .deb package downloaded from atom.io today.

Ubuntu 15.10, headless system accessed over xRDP.  Thank you @tonywmnix.

In case you're looking for a step-by-step for @tonywmnix's hack:

Find libxcb.so.1 (somewhere under /usr) (we'll call it $LIBXCB)
cd /usr/local/atom
cp "$LIBXCB" .
sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1

Note that you may need to run the last two as sudo. Also usual disclaimer for running commands off the internet.

Did the trick for me as well, and works with the beta version too

@tonywmnix solution works on Fedora 22 xfce, where $LIBXCB=/usr/share/atom, and the  .so is in /usr/lib64

Worked for me on Ubuntu 16.04 as well over XVnc.  LBXCB=/usr/lib/x86_64-linux-gnu/libxcb.so.1

@nestoru , what version of ubuntu and what desktop environment are you using with the xrdp?

@elico, see my comment above ( Mar 14).

@nestoru I have seen the comment but maybe I am missing what desktop.

GNOME
MATE
XFCE
OTHER..

@elico, gotcha. This was tested with lxde.

@elico It worked for me on XFCE.

@NelsonCrosby thanks for the details.

@tonywmnix @NelsonCrosby Thanks! Workaround fixed GLX problems on Ubuntu MATE 16.04 when using it over xrdp.

If you're having trouble finding the file libxcb.so.1 like I was you can type dpkg -L libxcb1

@NelsonCrosby Thanks for your suggestion. Tried it on Ubuntu 14.04 server with Mate Desktop but it didn't work.
Atom is /usr/bin/atom
libxcb.so.1 is at /usr/lib/x86_64-linux-gnu/libxcb.so.1
Copied libxcb.so.1 to /usr/bin/ but it looks like atom does ignore it.

@AlexZeitler you need to copy libxcb.so.1 to that atom application installation directory.  Once it's there you need to modify the file with:  sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1 ?

@danielpclark Thanks, I just located the directory using dpkg -L atom which pointed me to /usr/share/atom.
After copying the modified version of libxcb.so.1 into that directory, I was able to start Atom.

While the libxcb.so.1 hack makes it possible to start atom, it is very, very slow over x2go. Barely usable.

@Cotix What Link Quality Compression are you using? also what Display Size?
These affect anything inside a x2go session.
I am using it over x2go on a Atom(the remote..) server and it works ok for me on 1440x900.
And It's not related to the libxcb.so.1 but to other properties of the software in general.

Thanks @NelsonCrosby  @tonywmnix !
FYI to others, my atom executable was in /opt/atom; atom was installed via apt.
Ubuntu 16.04.1 LTS
Atom 1.9.8-1~webupd8~0
Here was the full fix:
sudo cp /usr/lib/x86_64-linux-gnu/libxcb.so.1 /opt/atom/
sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' /opt/atom/libxcb.so.1
No restart of xrdp service was required; worked immediately

Ubuntu 16.04.1 LTS
sudo add-apt-repository ppa:webupd8team/atom
sudo apt-get update
sudo apt-get install atom
sudo cp /usr/lib/x86_64-linux-gnu/libxcb.so.1 /opt/atom/
sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' /opt/atom/libxcb.so.1
Thank you! Atom is working via RDP (xrdp/mate)

Would prefer to see a real solution here rather than a hack.

It worked fine for my on 16.04.1 using TightVnc and I'm happy it's working
even with a hack.  (but I still agree with Seth).

Using atom-beta .deb package on Ubuntu 16.04 with LXDE over X2Go and couldn't get atom to start with the same error as above. I happened to be logged into the system locally at the same time and noticed that atom was actually opening on my local desktop when I tried to launch from X2Go before implementing the hack for disabling big messages. I'm not sure if that information helps locate and fix the bug, but I thought I'd provide it in case.

It worked for me on CentOS 7 with XFCE on X2GO with both the Website Version of Atom and the COPR Repository Version:
Instructions:
WEBSITE METHOD
yum install libXScrnSaver redhat-lsb-core.x86_64 libXScrnSaver.i686
wget https://atom.io/download/rpm
mv rpm atom-date +%b-%d-%Y-Centos7.x86_64.rpm
rpm -ivh atom-Centos7.x86-64.rpm
yum install libxcb.x86_64
cp /usr/lib64/libxcb.so.1 /usr/share/atom/
cd /usr/share/atom/
sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1*
COPR REPOSITORY METHOD
wget https://copr-be.cloud.fedoraproject.org/results/alonid/yum-plugin-copr/epel-7-x86_64/00110045-yum-plugin-copr/yum-plugin-copr-1.1.31-508.el7.centos.noarch.rpm
rpm -ivh yum-plugin-copr-1.1.31-508.el7.centos.noarch.rpm
yum copr enable helber/atom
yum update
yum install atom
yum install libxcb.x86_64
cp /usr/lib64/libxcb.so.1* /usr/share/atom/
cd /usr/share/atom/
sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1*
HOWTO INSTALL X2GO with XFCE on Cento7
#1.     Add EPEL repository first.
yum install epel-release
#2.     Then, install X2Go server package using command:
yum install fuse-sshfs
yum install x2goserver x2goserver-xsession
#3.     Install XFCE Desktop
yum -y groupinstall "Xfce"
Hope this helps!

The libxcb.so.1 hack works for me on Fedora 25 with X2Go and XFCE.

@zparihar
this worked for me on rhel 7.2 but, I can only launch it from CL.

That's interesting... Can you specify the full path of atom when you edit
the menu item?
On Jan 20, 2017 8:09 PM, "chagara"<EMAIL_ADDRESS>wrote:

@zparihar https://github.com/zparihar
this worked for me on rhel 7.2 but, I can only launch it from CL.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/4360#issuecomment-274233182, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AApx2rV6Um66a_XVkcQaG8TszqDZezmEks5rUYUBgaJpZM4DChRJ
.

@zacharysarah woks for me on CentOS latest(7.3?).
a MATE desktop over x2go.

Here is the solution. Tested in Ubuntu 14.04 LTS
sudo cp /usr/lib/x86_64-linux-gnu/libxcb.so.1 /opt/atom/ (Folder of the Atom)
cd /opt/atom (Folder of the Atom)
sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1

Bug still present in Atom 1.15.0

Bug is still exists in 1.15.0 but @tonywmnix hack's works well on Ubuntu 14.04.5 LTS

The libgconf-2-4 package might be missing preventing the application to launch.
This might help:
sudo apt-get install libgconf-2-4

Title is a just Atom does not start when using x2go
it more of window manager not x2go or tightvncserver
Came across this when
Debian from minimal install
using
lxde http://lxde.org/
or
awesomewm https://awesomewm.org
apply  @tonywmnix hack's
and it works for x2go and tightvncserver

The hack does works. However, I found the backspace doesn't work in the vscode editor and also, I cannot select the completion with enter. Is it possible that is the side-effect of the hack library?

I use atom via X2GO and decided to disable the BIG-REQUESTS extension of X2Go:

open /etc/x2go/x2goagent.options
Change X2GO_NXAGENT_DEFAULT_OPTIONS to include -extension BIG-REQUESTS

Then restart the server and reconnect to have atom working in x2go

bneijt's solution worked like a charm. Prefer it over patching shared objects with regular expressions.

@bneijt by server do you mean service(software) or server(machine)?

@elico service, not the whole server. It is a setting specific to the x2go service (software)

@bneijt Thanks!
I was 99% that this is what you meant but now 100%.
I tried it here with CentOS and it seems to work great.
No need for any libraries patches\hacks to work with atom and couple other applications.

Getting problems when running this on a server to which I connect using ssvnc.
With an old version of atom (1.6.2) the following fix worked:

copy libxcb.so.1 into /usr/share/atom
sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' libxcb.so.1

However with more recent versions, 1.19.0 or 1.20.--beta0 a different problem occurs: atom does start but all characters inside the editor window (with the exception of the menu bar which is in Courier) are shown as reactangles (unknown character placeholders?)

The easy fix for x2go and x11 forwarding using Ubuntu 16.04 and Mint is:
~$ sudo ln -s /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0 /opt/atom/libxcb.so.1
~$ sudo sed -i 's/BIG-REQUESTS/_IG-REQUESTS/' /opt/atom/libxcb.so.1
I did not have the same problem listed by @johann-petrak.

I experienced the atom/x2go problem on Ubuntu with atom from both the standard repository (i.e., installation via "snap") and with atom from the webupd8team launchpad repository.
@bneijt's answer works, and as others have mentioned, has the advantage that it does not require patching code that may or may not need to be re-patched in the next release.
Please note that you must add "-extension BIG_REQUESTS" on the server, i.e., the remote server that you're connecting to.

Not using x2go (at least I don't believe I am), but experienced the same problem on Linux Mint 18.2 (MATE).
Copied /usr/lib/x86_64-linux-gnu/libxcb.so.1  to /usr/share/atom
Opened libxcb.so.1 in 'vi' and change BIG-REQUESTS to _IG-REQUESTS
Now Atom starts just fine.
Thanks to all who helped solve this problem.

Thanks @ggodreau for the easy steps specific to version 16
thanks @NelsonCrosby  for steps
thanks @tonywmnix for fix

As noted in other Atom bugs this appears to be a version of an upstream bug https://github.com/electron/electron/issues/2256 that affects some VNC/NX servers (note that new versions of tigervnc's server do not seem to manifest this issue).


Crash in evdns.c

http://sentry.adguard.com/adg/adguard-android-rs/issues/6351/activity/

core/pull-requests/542


Adds git-together

I would like to get people's input on the proper way to initialize 'git-together' -- if I understand the  alias git=git-together this means that if the user wants to use git duet, then all git commands will first be run through git-together (which should do nothing) then pass the command onto git-duet. Likewise for git pair.
In other words, if this works properly, one can use git duet, git pair, or git together after this pull request is accepted.
If it is helpful, I'm willing to bring up a new machine using this pull request and verify that everything works =)
@kejadlen @nertzy


Think about how to resolve identifier/keyword confusion

Right now we have a lot of keywords that people might use unintentionally. Examples include default, read, write, from, duration etc.
I tried doing a fix for #3654, where if we expected an identifier but found a keyword, we would use the keyword as an identifier, but this gets confusing in the case where you forget an identifier. The following keyword would then be interpreted as the identifier and mess up any error reporting.
One way of fixing this is to keep track of the potential follow set for the rule currently being produced, but this has a huge impact on the number of functions in the parser, since we then have to have a special function for each context in which a production can exist that is followed by a keyword
My preferred way of fixing this would be to trim the number of keywords heavily and rely on predeclared identifiers in a typechecking pass done after the parse. It seems like the typechecker is needed anyway, since we do a lot of ad hoc verification right now which could be more rigorously done in a separate pass.

@DanielMorsing can you do more investigation on this? What would be the impact of your preferred way of doing things? We still have a ton of keywords and I'm guessing that the number is going to go up a bit over time.

It's mostly a case of defining all the scopes for where we expect a keyword now and putting in predeclared identifiers. Shouldn't be too hard.

@beckettsean could you unassign me from this issue and #3654?

I'm going to close this since I don't think we're going to have any further changes to the query language before 1.0. We will put in a notice that bare identifiers (those not surrounded by double quotes) may conflict with keywords and that clients should always surround identifiers with double quotes for the best compatibility.
Maybe we'll revisit this if we decide to make a change to the query language after 1.0.


Is there a deployed version/demo available & Screenshots?

screenshots in README of App
Link to deployed service

:+1:

:-) the app is currently just in the specification stage: https://github.com/dogweather/ducking-octo-dangerzone/wiki
I expect to begin coding this week.


Easier way to mass duplicate items

Currently if you replace a type of food or potion you will have to keep duplicating items and placing them back into the worn items setup, and it can become quite tedious, it would be nice if perhaps another popup appears asking how many of this item do you want duplicated, or just multiple options that says duplicate item, duplicate item-5, duplicate item-X, etc, or potentially a default option in the settings that the user can choose to duplicate a set amount of times everytime

I'd rather a hotkey. hotkey + click for duplicate, another hotkey for removing an item, etc.
Or, ideally you could just use the auto-layout after setting up your inventory. auto-layout can be buggy though and I'd like to update it at some point.


docs: improved recursive url loader docs

you'll want to run make format in root of dir (for docs) and in libs/community


Fix late publication of ATXs not possible

Motivation
Closes #5272
Changes
If the node failed to publish an ATX during the cycle gap and is restarted after the new PoET round started, the ATX builder incorrectly waits until the next cycle gap before checking for the existing challenge or building a new one. Instead it should verify and use the existing challenge to publish an ATX asap to be still be eligible for rewards in the upcoming epoch.
Example:
In epoch 8 a user missed the PoET registration deadline due to a crash, without the fix the node would now wait until epoch 9 to discard the challenge, build a new one and register at PoET.
With the fix the node will take the existing challenge and immediately build and publish an ATX.
This way the affected user will receive rewards in epoch 9 and only miss rewards in epoch 10; without the fix they would miss rewards for both epochs.
Test Plan

a new test was added to verify the changed behavior is correct

TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors try

bors merge


Add rdkit and matplotlib as explicit dependencies

Changelogs

Add rdkit and matplotlib as explicit dependencies

Oops! https://github.com/polaris-hub/auroris/pull/15

I tagged along some other changes I've wanted to make, so I hope you don't mind my closing this PR in favor of the other one.


Add a documentation license

Specify under which license the 'Learning-Cuis' content may be used.
I suggest one of the
https://creativecommons.org/education/
licenses to make it an OER

I added the CC licence.
Looks too complex by far.
-KenD


Added overview page for keyboard controls

Added a button to the far bottom of the main menu that opens a page displaying the key combinations for each of the available hotkeys. If/when hotkeys are added/changed/removed from the editor in future iterations, the overview page will automatically adapt.
Also rewrote hotkey related stuff in other places because I had to change the hotkey keyMap to an object.
Intended to resolve #310.

Regarding 1: But not enough to fit the word "video" it seems. I don't see a better way to avoid this issue unfortunately.

Looking at my screenshot: I see more than enough space if there is a break between the two tables, which there is in the screenshot anyway, since the second table does not fit properly.

Regarding 2&3: Definitely seems to be caused by the main menu ending prematurely. Do you have any meany by which I can reproduce this?

The screenshot is just from a browser snapped to the left half of my screen. But this also appears in mobile mode or basically any other situation where the content is longer than the menu.

Regarding 5: Attempted to move to a centered layout with the recent commits. Will cause overlap with the main menu for small widths, not sure why though.

Yep, that seems to break things:


Stabilize traffic light - First part

Description

Increased InmantaBootLoader timeout when everything is being shut down -> to make sure every component has enough time to be stopped without leaking resources (background task, ...)
Remove sugar in logs to not hide teardown
Add more logs when Scheduler tests are failing (check if other processes are interefering)

Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

This branch was not deleted as it seems to still be in use.


[WIP] Try hugo upgrade

@danielramirez0 I think I've got this pretty well working. Main thing left is I will be updating the README to reflect the new version changes and other details. We can look at this together next week and we should socialize to TDC Slack channels for folks who build locally as they will need to do some brew upgrades, etc.


Make pep8 tests a warning rather than a fail for travis?

I get bitten every. single. time.

Allow me to introduce you to your new best friend, autopep8

Glorious!
I wonder if I can make it a pre-checkin hook for my git client...

I wonder if I can make it a pre-checkin hook for my git client...

Please don't. ;-) It's worth having a look at what it does, and
also running tests.


"Parchment does not support Internet Explorer" but I'm not using Internet Explorer

I'm using the Borogove IDE in SeaMonkey 2.53. This is the browser I use for writing projects, to keep myself from getting distracted by all my bookmarks and such in my regular browser. It works fine for all of the sites I use it for.
I know Parchment supports this browser, because I have no issues on PlayFic. Further, I have no problems compiling, playing, and downloading on Borogove, though I didn't realize at first that I could actually type in commands in the on-site preview since there's a CSS rule being deliberately applied to the cursor to make it invisible, so it looks like I can't do anything.
My browser works just fine, and I'm not even using the browser Borogove thinks I'm using, so can this unnecessary warning banner maybe be removed?

Thanks, I've removed the check from Parchment – it's basically unnecessary here because the IDE won't work in Internet Explorer anyway. I'll open a new ticket about the core issue in the Parchment repository.

Looking at the Parchment source more carefully, it looks like it's moving to use dynamic module import that SeaMonkey doesn't support yet. SeaMonkey 2.53 corresponds to Firefox 56, but module support is available from Firefox 67 onward. Playfic uses an older version of Parchment that doesn't use modules and Borogove uses a later version that has the IE check in place but doesn't fully use modules yet.
It's likely that Borogove's Parchment version will be updated later but there's no pressure to do that yet. When that happens it'll stop working again unless SeaMonkey gets an update. Also if you only use SeaMonkey to keep it separate from the regular browser, it's also possible to make multiple profiles in Firefox that behave practically the same as different browsers.

Yeah sorry, the work in progress Parchment (not yet live on iplayif.com) uses dynamic import, which is supported nearly everywhere now. I didn't know SeaMonkey was still being produced. ESR releases are also likely to not work. I'll change the error message to be more generic, but at this stage I don't intend to support browsers without dynamic import.

Well, that's sad to hear. I'll have to bring it up with the SeaMonkey devs.


just: airplane mode

I'm on a trip and it'd be a nice to have a just shortcut to disable the autoupdates to everything that we can, especially until updates are more efficient.
Perhaps there's a way to display that service's status when I open a terminal or something to remind me it's on as a reminder to turn it back on when I'm not on slow internet.

This feature would need to encompass both images having ublue-update and the regular gnome-software and discover counterparts, too, I'd think.

I think just turning the flatpak and autoupdate services on and off should do the trick?

Network Manager allows us to mark a connection as metered. I don't know where exactly it stores that information but it'd be great if that information was fed into systemd so that you can use that info in your service definition. If we're able to read that maybe we can also incorporate that into a script before firing rpm-ostree/flatpak commands?

Yeah this sounds awesome! The reason I wanted the explicit toggle is the data consumption while I'm on slow networks. "I'm going on a trip, I turn this off until I get back" so I'm not flooding my network with an update while checking my email.
Smarter network manager support is awesome, that'd be a great thing to have no matter what, so if you want to work on that let's do it! Thanks!

The reason I wanted the explicit toggle is the data consumption while I'm on slow networks. "I'm going on a trip, I turn this off until I get back" so I'm not flooding my network with an update while checking my email.

So you want "travel mode" rather than "airplane mode" 😁

@castrojo so do you still want a just command or should I just stick to NetworkManager metered connection?

I decided to do the metered connection first, it seems to be working but looking for testers!

Added disable-updates and enable-updates into 10-update.just (decided to do this on the same PR).

Thank you @ArtikusHG for taking responsibility for this!

Hey, uh, it's been almost a week, is this going anywhere? Can someone at least take a quick look at the PR so I can fix it if something is wrong?

Hey, uh, it's been almost a week, is this going anywhere? Can someone at least take a quick look at the PR so I can fix it if something is wrong?

FYI - i didn't realized you had a PR... it the future, it's helpful to add reviewers on the PR itself

it's helpful to add reviewers on the PR itself

It doesn't seem like I have the right to request a review on a PR, or did you mean just ping someone in there?

it's helpful to add reviewers on the PR itself

It doesn't seem like I have the right to request a review on a PR, or did you mean just ping someone in there?

Interesting...
You don't have this gear for choosing approvers?

Thanks for letting me know. I don't want to assume people have access to that widget if they don't.

I might be missing something, but yeah, I don't see that icon

I might be missing something, but yeah, I don't see that icon

Thank you for the feedback. Good to know!

I think with #123 merged, we can close this issue.

Hi. Although this is merged, GNOME still tries to fetch updates and seems to cause a lot of bandwidth. Is there a way to prevent this?


Support languages names and RFC 1766 codes

Accept languages names (case-insensitive) as dest/src params in the translate routine.
Accept RFC 1766 codes (eg.: nl_nl, es_uy@euro, etc.) as well.
Move dest/src params check to the translate routine.

Coverage remained the same at 100.0% when pulling 60939273de34175937380812f47707385357a3c1 on vuolter:patch-1 into 633fc40a57b5ded5b28b0ae97f424d866b509492 on ssut:master.

Thanks @vuolter!


Long customer names throw error

Current behaviour
When creating a tenant with a name longer than 32 characters (concatenated with the bpn) the creation of the wallet fails. The same error occurs when using any other character than alphabetic or numeric characters.
Expected behaviour
Even for customers with special characters and very long names we want to be able to create the wallet

Successfully tested :)


change missing values encoding from hatching pattern to centered dash

The dash has the big advantage that it also works in overview mode.

High LOD:

Medium LOD:

Low LOD:

very nice, much better than the hatching.


How to setup a hadoop cluster in a kubernetes cluster?

I would like to setup a hadoop cluster in a kubernetes cluster.There are 4 nodes for kubernetes cluster.
I create a pod for hadoop master in a kubernetes cluster node.And I create three pods for hadoop slaves in the other 3 nodes.I have to do that all the pods in a intranet each other.I want to do that multiple pods in different nodes in a intranet. What should I do?Any help is appreciated!

Please ask ok Slack or Kubernetes-users@ Google Groups mailing list. 😊


Improve import material

Description of the current limitations
test_18_stackup is producing errors, but unittest is still passing. The cause of failure is material name is sensitive. Failed to set COPPER since copper is already in material library.
My suggestion is to update material properties when material already exists.
@SMoraisAnsys  @svandenb-dev
Code sample expected
No response
Useful links and references
No response

We can discuss about this but I would rather avoid that. If I'm not mistaken, there is a way to remove a material and I feel like it would make more sense to let the user remove something to create another one. This way, we would ensure that he is aware of the case sensitive issue.
@ring630 Can we discuss about this when I'm back from PyCon US? I probably don't have (again) enough knowledge on the materials aspects and your point of view could help me understand how we should do things.

@SMoraisAnsys Material is a special case, and it was not handled properly. I am glad you are fixing it. Let's discuss further.
Here I list the facts.
1, AEDT UI is not case sensitive. COPPER and copper cannot coexist.
2, EDB is case senstitive. It should be prevented to have both COPPER and copper.
3, extra care is required to rename COPPER to copper if COPPER already exist. Layers are using COPPER.

Summaryze changes required:

allow changing the name of a material
allow a configuration to "update" the material information (either rename + update data or delete + create)
use lower case when loading AMAT file

Reopening this issue as I don't think it is fully handled.

what is the status @SMoraisAnsys ?


PCL support

How about convert TrueCraft to PCL?
I have something that I can call a "client". Runs on mobile platforms and blah blah.  Would be cool if I could run both client and server on, for example, android.
Will help, of course.

I'd be willing to try and change TrueCraft.API and TrueCraft.Core to PCL so long as it didn't have substantial effects on the actual functionality of the software or the quality of the codebase.

I tested fNbt. It works in PCL, but will need PCLStorage or similar to interact with filesystem. All nunit test works except with filesystem

fNbt ported. You can use my fork https://github.com/MineLibOrg/fNbt to test it personally. Requires .NET 4.5, if everithing is good, can make pull request.
Works as it was before.

Cool, will test soon.

This is out of scope, we've made some other choices that make it difficult to port TrueCraft to mobile targets anyway.


Lyrics API Down

Looks like https://lyrics.altart.tk is no longer available.

I changed the domain a while ago and forgot to change it, but I don't have the same desire as before to maintain and update this library.
The API linked in this domain will shut down soon, but I will post a gist with the code to make the request
https://gist.github.com/alt-art/f5e38428fc4f814c991a447f8d719b83

This token was acquired by reverse engineering the genius android application.


can't develop through gitpod due to pnpm version

Looking forward for reporting a security issue:
Please report security issues by following our security policy: https://contribute.freecodecamp.org/#/security
Describe the bug
A clear and concise description of what the bug is.
Gitpod can't be used to develop right now. Or maybe it's possible but someone new wouldn't know what steps they need to take.
Should i add a note in how-to-setup-freecodecamp-locally.md so that new people know?
https://github.com/freeCodeCamp/freeCodeCamp/pull/50613#issuecomment-1577010365
To Reproduce
Steps to reproduce the behavior:

follow instructions in how-to-setup-freecodecamp-locally to develop with gitpod, fails with message  ERROR  /<EMAIL_ADDRESS>is an invalid relative dependency path

Thanks for letting us know @jmetev1.
On the pnpm side this should be resolved by https://github.com/pnpm/pnpm/releases/tag/v8.6.2
@ShaunSHamilton any idea why our .gitpod.Dockerfile isn't already using the latest version of pnpm?

@ShaunSHamilton any idea why our .gitpod.Dockerfile isn't already using the latest version of pnpm?

Because I have forsaken the local config to focus on: https://github.com/freeCodeCamp/gitpod-images/pull/3/files#diff-b093d34eec92adf6e0cc6e445edb7147ea45d25fb0c98f2f84a60f5aae6f34f7
For this repo, I have just been manually running npm i -g pnpm. Personally, I do not like everything running from the get-go, but realise many like the one-button setup.
This is so quick to fix, I will just PR it before the long-term fix is ready.


Dataloader crashes when using torchvision style custom transform (random brightness)

Following the ffcv doc, I made random bright augmentation using PIL Image reference using keras and pytorch augmentation. (torchvision transform style)
(keras, pytorch)

I make pipeline with ffcv transformation and also the above augmentation and call dataloader.

I got the above error and tried a lot, but can't find how to solve it.
(I checked ImageDecoder output is numpy array)

I'm currently using ffcv 0.0.3 version

Hi @Jasonlee1995 ! Torchvision augmentations operate on Tensors and not numpy arrays, so you should move the augmentations to come after the "ToTensor" operation in your pipelines.

@andrewilyas

Thanks to your advice, I change my augmentation operation to tensor not numpy and change the pipeline order.
(reference pytorch codes)
But what I get is error about wrong shape and check the shape.

I know that pytorch works on individual image not batch images, which mean printed shape should be (C, H, W) or (H, W, C).
(cause I add print code on augmentation code)
But what I got is (batch size, H, W, C) and I think it's strange.

Thanks!
I find the ways not using PIL Image, but use numpy to augment the images using brightness, contrast, saturation.
As soon as I test my FFCV transformations, I'll send pull request!


add goto list in command palette

Summary

Ticket Link

Related Pull Requests

Has server changes (please link here)
Has mobile changes (please link here)

Screenshots

Release Note

Hello @VishakhaPoonia,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


execution failed for task ' compiledebugjavawithjavac'

Error:Note: E:\WorkSpace\VirtualAPK-master\app\src\main\java\com\didi\virtualapk\MainActivity.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

No signature of method: static com.android.build.gradle.internal.ide.ArtifactDependencyGraph.getAllArtifacts() is applicable for argument types: (com.android.build.gradle.internal.scope.VariantScopeImpl, com.android.build.gradle.internal.publishing.AndroidArtifacts$ConsumedConfigType, null) values: [VariantScopeImpl{debug}, COMPILE_CLASSPATH, null]
Possible solutions: getAllArtifacts(com.android.build.gradle.internal.scope.VariantScope, com.android.build.gradle.internal.publishing.AndroidArtifacts$ConsumedConfigType, com.android.build.gradle.internal.ide.DependencyFailureHandler, com.google.common.collect.ImmutableMap)

I did not get how to fix this issue. please let me know how to solve it.
Thanks in advance.

Please use com.didi.virtualapk:gradle:<IP_ADDRESS>-dev or the later version.


Don't include sources in their errors' display()

When trying to use source() in a chain, each display() currently includes the succeeding errors, causing a lot of duplication.
When one wants to easily display an error chain intercalated by ": ", they should format using the alternate format: format!("{:#}", err)
Also fixed extraneous quoting around paths in errors

:+1: on adding #[source] annotations.
I'm not quite so sure about removing the source from the Display impls.. I don't see anything about {:#} for getting the error chain in the docs for std::error::Error, std::fmt, or std::fmt::Display. Is that a thiserrorism?

Not seeing anything about the alternate display mode in thiserror's docs either, nor does it seem to work in practice (https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=f8fa20aca31d5a4ab5dd725c62a92f54).

Oh, you're totally right, the {:#} handling is a anyhow::Error feature, my bad.

My point still stands w.r.t. display(), it's impossible to display each error in the chain without the remainder at each step, it's how color_eyre displays errors, so I assume that's how display() is meant to be implemented, I might be wrong.

Including the source in Display impl or not is still under debate (leaning towards not), but we shouldn't do both (Display and #[source]).

The short answer is that both design decisions (as in, whether to print the source error on the Display impl) have upsides and downsides; some error handling libraries impose an opinion on this (e.g. anyhow/eyre) whereas others currently do not (SNAFU); and although things appear to be turning towards letting the job of printing the source error to the reporter, this is still not a well established consensus, to the point that this has not been accepted to become part of the API guidelines (rust-lang/api-guidelines#210), mostly because it would still break some expectations.
https://github.com/rust-lang/project-error-handling/issues/23#issuecomment-739940091

To add some more to that, we're currently leaning towards the reporter based design, but it's too early to start pushing for it across the ecosystem because there are quite a few edge cases still where context for errors can be discarded because no reporter is ever used.
...
For now, the recommendation is to always do one or the other. If you're going to print your sources, you should not return them via the source function and vice versa.
https://github.com/rust-lang/project-error-handling/issues/23#issuecomment-740070694

For thiserror usage, dtolnay wrote:

Using thiserror's attribute syntax for convenience, the contents of the error type should appear either in the message:
#[derive(Error)]
enum Error {
    #[error("Failed to read settings: {0}")]
    ReadSettings(io::Error),
}

or as a source:
#[derive(Error)]
pub enum Error {
    #[error("Failed to read settings")]
    ReadSettings(#[source] io::Error),
}

but never both.
https://users.rust-lang.org/t/do-people-not-care-about-printable-error-chains-a-k-a-how-to-nicely-implement-display-for-an-error/35362

Now that we're getting more into opinions, my vote would go towards putting sources into both Display and source. Why?

Not implementing source means that we hide semantically useful information (such as source downcasting)
I'm not really aware of a good error formatting library that I'd be comfortable recommending (that doesn't also try to be its own error handling universe, like color-eyre does)
If you're doing custom trace formatting then it's not much extra work to strip_suffix the source (see https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=f3a8475d9934fa520fc8ecd4181e18e8, for example)
Even if you don't strip the duplicates, duplicate messages is still a better situation to be in than missing messages

Found https://github.com/rust-lang/project-error-handling/issues/27 which is more relevant to us a library.
And more up to date comment:

We came to the consensus that the primary role of the error trait is providing a structured access to error context for the purpose of reporting, so our guidance is officially decided.

Return source errors via Error::source unless the source error's message is included in your own error message in Display.

https://github.com/rust-lang/project-error-handling/issues/27#issuecomment-763950178

We should follow the official guidelines, but we don't have the necessary tools yet (they're planning to add Report in std). I think the "fix" to remove source from Display can wait until when the migration path is established.
I'm more concerned about not having focused errors (lightly discussed in https://github.com/clux/kube-rs/discussions/453).

I bumped into this very same issue recently - specifically when trying to publish Kubernetes' events in a controller.
I'd like a short to-the-point description of what went wrong for the operator using kubectl describe, while the more verbose cause chain should be displayed in the controller logs.
By only returning the underlying error in source, you can still print the entire error chain without any special support by std or external library:
fn error_chain_fmt(e: &impl std::error::Error) -> String {
    let mut buffer = String::new();
    writeln!(buffer, "{}\n", e).unwrap();
    let mut current = e.source();
    while let Some(cause) = current {
        writeln!(buffer, "Caused by:\n\t{}", cause).unwrap();
        current = cause.source();
    }
    buffer
}

@LukeMathWalker

By including the source in both source and Display, it becomes impossible to achieve.

It's not the prettiest, but you could do something along the lines of:
let mut msg = err.to_string();
if let Some(source) = err.source() {
    msg = msg.trim_end_matches(format!(": {}", source)).to_string();
}

By only returning the underlying error in source, you can still print the entire error chain without any special support by std or having to pull in external libraries:

You can, but the question is what people actually do. FWIW, tracing's console formatter only fixed this less than two weeks ago (and the JSON formatter still doesn't, over backwards compat concerns).

It's not the prettiest, but you could do something along the lines of:
let mut msg = err.to_string();
if let Some(source) = err.source() {
    msg = msg.trim_end_matches(format!(": {}", source)).to_string();
}

That looks very brittle :/
I also doubt that kube-rs considers (or wants to consider!) the structure of the Display representation as part of its API interface guarantees, semver-wise.

You can, but the question is what people actually do. FWIW, tracing's console formatter only fixed this less than two weeks ago (and the JSON formatter still doesn't, over backwards compat concerns).

I am not arguing with the broader underlying assumption - the Rust community is still, collectively, iterating on what are considered the best patterns for error handling. Tools in the space have some catch-up to do.
But there is clear guidance from the relevant working group around the usage of source and its interplay with Display, so it's safe to assume that the ecosystem will converge to it.

That looks very brittle :/
I also doubt that kube-rs considers (or wants to consider!) the structure of the Display representation as part of its API interface guarantees, semver-wise.

Absolutely, please don't try to parse the Display output!
That said, in this particular case, the only way that I can imagine we'd change this would be to remove the source entirely from the Display (once the error-rendering ecosystem has caught up with the error WG's guidance), which that example would cope with fine (trim_end_matches becomes a no-op if there are no matches). Plus, the worst-case scenario (changing {}: {} to something like {}, caused by {}) would still fail mostly graciously (the full source error would be included again, but it shouldn't cause anything to fail).

We'll do this as part of refining errors (#688).


wavefront.Granularity should me marked as a required option

If wavefront.NewExporter is called without wavefront.Granularity option, the created Exporter is not able to export the histogram and Error sending histogram: histogram granularities cannot be empty is logged in the console by wavefront-sdk-go.
This is neither documented at OpenCensus docs or in the README of this repo.

After the PR is merged, wavefront.Granularity is no longer a required option.


Add smaller versions of radio buttons and checkboxes

Introduces smaller versions of the radios and checkboxes components.

Despite being visually smaller, these have a target size of 44 x 44px, as the input extends outside of the boundaries of the visual control.
To make it clear which control will be activated when hovering in the gap between the controls, we add a hover state.
This PR also simplifies the way that existing checkboxes and radio buttons are rendered in IE8 and increases the touch area of the existing radios and checkboxes to 44x44px.
👉Checkbox examples in the review app
👉Radio examples in the review app
👉Radios and checkboxes, big and small, in all the states
👉A contrived example
Browser and assistive technology testing

[x] Internet Explorer 8 (Windows 7, Browserstack)
[x] Internet Explorer 9 (Windows 7, Browserstack)
[x] Internet Explorer 10 (Windows 8, Browserstack)
[x] Internet Explorer 11 (Windows 10, Browserstack)
[x] Edge 18 (Windows 10, Browserstack)
[x] Edge 17 (Windows 10, Browserstack)
[x] Google Chrome 73 (mac)
[x] Mozilla Firefox 65 (mac)
[x] Safari 12 (mac)
[x] Safari 11 (mac, Browserstack)
[x] Safari 10 (mac, Browserstack)
[x] Safari 9.1 (mac, Browserstack)
[x] Safari (iOS 12, iPhone X)
[x] Google Chrome (iOS 12, iPhone X)
[x] Safari (iOS 11, iPhone X, Browserstack)
[x] Safari (iOS 10, iPhone 5c)
[x] Safari (iOS 9.3, iPhone 5)
[x] Safari (iOS 7, iPhone, iPhone 4)
[x] Google Chrome, Android 9, Browserstack
[x] Google Chrome, Android 8, Browserstack
[x] Samsung Internet, Android 8, Browserstack
[x] Samsung Internet, Android 7, Browserstack
[x] Google Chrome 73 - mixed input modes (Chromebook)
[x] Google Chrome 73 - 400% zoom (macOS)
[x] Internet Explorer 11 - high contrast mode (Windows 10)
[x] Internet Explorer 11 - ZoomText (Windows 10)
[x] Internet Explorer 11 - 400% zoom (Windows 10, Browserstack)
[x] Internet Explorer 11 - larger text (Windows 10, Browserstack)
[x] Mozilla Firefox 65 – custom colours (mac)
[x] Mozilla Firefox 65 – night mode (iOS)

Physical device testing
Chrome 69, Android 7.0 (Galaxy S6)
Works as expected
Chrome 50, Android 5.1.1 (Nexus 10 tablet)
Works as expected
Chrome 71, Android 4.4.2 (Galaxy Note 2)
Tested with stylus and touch. Worked as expected
Android Browser, Android 4.4.2 (Galaxy Note 2)
The stylus triggers hover style
Touch triggers the hover style, and clicking once triggers hover style then after a delay triggers the click. Not ideal but still usable.
Android 2.2 (Galaxy S)
Radios are square – seemingly no support for border-radius – an existing issue.
Small hidden element highlighted on tap. Hover state not visible.
Safari, iOS 10.3.2 (iPhone 5C)
Works as expected
Safari, iOS 9.3.2 (iPhone 5)
Works as expected
Safari, iOS 7.1.2 (iPhone 4)
Hover state is visible and 'sticks', but clicking once still triggers the control
Internet Explorer, Windows Phone 8.1 (Lumia 630)
Works as expected
Screenshots

Chrome 70 (macOS Mojave)

Chrome 70 (Windows 10)

Chrome 71 (macOS Mojave)

Chrome 71 (Windows 10)

Firefox 62 (macOS Mojave)

Firefox 62 (Windows 10)

Safari 9.1 (OS X El Capitan)

Safari 10.1 (macOS Sierra)

Safari 11.1 (macOS High Sierra)

Safari 12 (macOS Mojave)

Internet Explorer 8 (Windows 7)

Internet Explorer 9 (Windows 7)

Internet Explorer 10 (Windows 8)

Internet Explorer 11 (Windows 10)

Edge 18 (Windows 10)

Android 7.1 (Google Pixel)

Android 8.0 (Google Pixel 2)

Android 9.0 (Google Pixel 2)

iOS 8.3 (iPhone 6)

iOS 10 (iPhone 7)

iOS 11 (iPhone 8)

iOS 12 (iPhone XR)

Known issues
The hover state 'sticks' on devices that support both touch and pointer based interaction, such as Chromebooks and Surfaces.

Video showing issue

If you try to use a hint with the smaller radios and checkboxes, moving the cursor over the hint will trigger the hover state, but clicking the hint won't actually select the control.

Video showing issue

Addresses https://github.com/alphagov/govuk-design-system-backlog/issues/162

Is the a recommended way to add the small boxes into a table for example to select rows? This was an important driver for the smaller check-boxes I think, but I am not clear how to adapt the component to centralise in a  nicely without breaking something.

Is the a recommended way to add the small boxes into a table for example to select rows? This was an important driver for the smaller check-boxes I think, but I am not clear how to adapt the component to centralise in a nicely without breaking something.


Passing a multiple variable definition as an if condition causes rock to segfault

Recently I have been making a compiler for a toy Greek programming language (practise before I jump on oc :) ) and I used nagaqueen + rock's AstBuilder type as a template for my fronted. While studying AstBuilder, I bumped into this:
// FIXME: Better detection to avoid 'stack' being passed as a Statement to, say, an If

In AstBuilder's onVarDeclEnd method. Intrigued, I tried to compile the following code, wich caused rock to segfault.

if(a,b: Int = 1) {
    "true" println()
}

This code also segaults when we replace the if statement by a while statement.

 Better design from the start could've avoided that!


Default values for push constants in D3D12

In D3D12, push constants are part of the root signature, which is associated with the pipeline layout. Therefore, values always flow from the root signature into the shader, not the other way around. If we want to use the default value and not require the user to always provide some, we should be reading it from the shader. Here are rough steps:

when creating a pipeline, read the default values for push constants, match them against the pipeline layout, and store them somewhere in the pipeline
in flush_user_data, if a constant doesn't have a value in the user_data, we need to get it from the current pipeline.

Ideally, we need to rehash the understanding about how the default values work in Vulkan...

Is this about specialization constants? Would be news to me that there are default values for push constants in SPIR-V

You are right, I mixed things up. I was talking about this line:
layout(constant_id = 0) const float scale = 1.2f;

It is a specialization constant.
I got confused because the example specifies the push constant ranges.
Anyway, need more of a fresh head when I'm hacking stuff. Thank you for correction!


[BUG] Non Sticky Navbar

Description

Right now the navbar is not sticky to its position
Its move up upon scrolling
And as a user its very time consuming for me to every time go back to top and download the icons

Expected behaviour

The navbar should stick to its position so that it very helpful for user to navigate easily on your website

Screenshots/Video
https://github.com/Bookingjini-Labs/bookingjini-icons/assets/101205226/19244628-6406-4f3c-b13c-5fca7d4eb675
Additional context
Hey @AshutoshDash1999

I will redesign the navbar with position stick to top
Also i will  made transparent navbar with background blur effect giving it glass morphism effect

What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I will work on this issue (optional)
[X] I am a GSSoC'23 contributor

@parasss19 ok


Component should support exclude some files inside from compile

There is such case that developers want certain file inside one component is excluded from compiled. There are many reasons, a common one is some c source file is just for demo an alternative usage.

https://arm-software.github.io/CMSIS_5/Pack/html/pdsc_components_pg.html#element_file
category="other" or "template" does that already.  template is a source file that might be added by the user.


Azure Signalr Service Issue with Blazor Application

Issue moved from dotnet/aspnetcore#26600

Please respond to @mithunscout.

From @mithunscout on Monday, October 5, 2020 5:16:41 AM
Team,
I have one application which uses the below logic ->
Step 1-> Azure SQL Database gets a row from Web API from another application and one stored procedure runs and creates an entry on the table
Step 2-> once the Entry is created in this table there is one Azure Logic App which pushes the row into Queue Table in Azure
Step 3 -> Once the queue table gets an entry using Queue Trigger it pushes the record to Signalr Hub where clients are connected and the record is distributed to users;
The issue I am facing here is I moved this application from Web Based to Blazor. Here when I moved this I am facing below issues
a. on local system without Azure Signalr Service everything works perfectly (Only Locally)
b. when I turn of the Azure Signalr Service and publish it as Web Service App and push it to Azure-> the application fails with Blazor Negotiation Error - Error Message Azure Signalr Service is not started
c. When I turn on the Azure Signalr from Startup and try running it locally - it doesnt work
same error Azure Signalr Service Is not Started / Connection ID Required
d. When I try to push it to Web App with Azure Signalr R Service started - it doesnt work and gives me same error (Azure Signalr Service Not started / Connection Id Required)
find below blazor server logs;
[2020-10-05T05:16:00.498Z] Information: Starting up blazor server-side application.
blazor.server.js:1 [2020-10-05T05:16:00.499Z] Information: Normalizing '_blazor' to 'https://localhost:44345/_blazor'.
blazor.server.js:1 [2020-10-05T05:16:00.499Z] Debug: Starting HubConnection.
blazor.server.js:1 [2020-10-05T05:16:00.499Z] Debug: Starting connection with transfer format 'Binary'.
blazor.server.js:1 [2020-10-05T05:16:00.499Z] Debug: Sending negotiation request: https://localhost:44345/_blazor/negotiate?negotiateVersion=1.
_blazor/negotiate?negotiateVersion=1:1 Failed to load resource: the server responded with a status of 500 ()
blazor.server.js:1 [2020-10-05T05:16:00.522Z] Error: Failed to complete negotiation with the server: Error
e.log @ blazor.server.js:1
blazor.server.js:1 [2020-10-05T05:16:00.523Z] Error: Failed to start the connection: Error
e.log @ blazor.server.js:1
blazor.server.js:1 [2020-10-05T05:16:00.523Z] Debug: HubConnection failed to start successfully because of error 'Error'.
blazor.server.js:19 [2020-10-05T05:16:00.523Z] Error: Error
e.log @ blazor.server.js:19
blazor.server.js:1 [2020-10-05T05:16:00.523Z] Debug: Call to HubConnection.stop(undefined) ignored because it is already in the disconnected state.
blazor.server.js:1 Uncaught (in promise) Error: Cannot send data if the connection is not in the 'Connected' State.
at e.send (blazor.server.js:1)
at e.sendMessage (blazor.server.js:1)
at e.sendWithProtocol (blazor.server.js:1)
at blazor.server.js:1
at new Promise ()
at e.invoke (blazor.server.js:1)
at e. (blazor.server.js:19)
at blazor.server.js:19
at Object.next (blazor.server.js:19)
at blazor.server.js:19

Issue moved from dotnet/aspnetcore#26600

Please respond to @pranavkm.

From @pranavkm on Monday, October 5, 2020 4:36:56 PM
@BrennanConroy could you help?

Issue moved from dotnet/aspnetcore#26600

Please respond to @BrennanConroy.

From @BrennanConroy on Monday, October 5, 2020 4:39:05 PM

Azure Signalr Service is not started

Have you configured the service correctly? https://docs.microsoft.com/azure/azure-signalr/signalr-quickstart-dotnet-core

Issue moved from dotnet/aspnetcore#26600

Please respond to @mithunscout.

From @mithunscout on Monday, October 5, 2020 10:25:09 PM
Hi I have gone through this document and have configured it as per this...

Issue moved from dotnet/aspnetcore#26600

Please respond to @mithunscout.

From @mithunscout on Tuesday, October 6, 2020 6:12:49 AM

Hi Brennan,
I am seeing this error when I click the link on my console. Pls find attached the screenshot for the same. I still dont see any server side activity on my Signalr Service;

Regards
Mithun

Issue moved from dotnet/aspnetcore#26600

Please respond to @mithunscout.

From @mithunscout on Tuesday, October 6, 2020 8:49:06 AM
Hi Brennan
Pls find attached the Server Logs for the same
Regards
Mithun
AzureSignalrLog.log

Please provide me an update on this

The server side, how is it configured to use Azure SignalR? Where you set the ConnectionString?
Also could you please provide your blazor app server side log following https://github.com/Azure/azure-signalr/blob/dev/docs/howto-tsg.md#add_logs_server_aspnetcore when the app server starts? We need the app server side log to identify why it fails to connect to Azure SignalR. Typically we care about logs that "Starting transport" and "Failed to connect", the log should show up right after the app server is started. The logs would be similar to below:


unable to add or delete environment variables to project or environment

Describe the bug
Post RBAC integration, a user is unable to add any environment variables to a project or environment, the operation performs as expected for a user with an existing admin token.
To Reproduce
Steps to reproduce the behavior:

As a user who is of OWNER|MAINTAINER|DEVELOPER attempt to add an environment variable to a project or environment

mutation mutation1 {
  addEnvVariable(input:{
    type:PROJECT
    typeId:11
    scope:GLOBAL
    name:"TESTING"
    value:"CHECK"
  }) {
    id
  }
}

For all cases, attempting to add a PROJECT environment variable results in
Unauthorized: You don't have permission to \"project:add\" on \"env_var\".

Attempting to add an ENVIRONMENT environment variable results in
Unauthorized: You don't have permission to \"environment:add:undefined\" on \"env_var\".

For the deleteEnvVariable mutation the results are similar.
Expected behavior
Environment variable should be saved\deleted to\from the API

Appears that the issue is still there for OWNER adding a project level env var
"message": "Unauthorized: You don't have permission to \"project:add\" on \"env_var\".",