Allow transfer to smart contract principal

This started with testing a simple Clarity contract that can stack its own STX through pool delegation.
Tried to fund the contract from the sandbox using a deposit function, but without post-conditions the deposit failed.
Next tried transferring using the Send screen of the wallet extension, which resulted in Address provided is not valid

Was able to get past this by writing a script, but should this type of transfer be allowed from the wallet? Maybe with a warning?

Thanks for the request. It looks like we're tracking it here as well: https://github.com/hirosystems/stacks-wallet-web/issues/2514
@kyranjamie see any reason why this wouldn't be a simple validation change? Does the wallet need to handle the recipient value differently if it contains a contract?

It could be fairly straightforward, I'd need to look into it. Not 100% sure Stacks.js supports contract principals


stop hiding .js.map files in the .gitignore

fixes https://github.com/dart-lang/polymer-dart/issues/54

lgtm


Fixed Poison.SyntaxError when receiving 204 response

I was using hound's navigate_to helper on BrowserStack's Amazon KindleFire 2 device, and was receiving a 204 No Content response after a POST /session/<session_id>/url request that changes the page. Since the request succeeded, it seems Hound should be able to handle the response
without throwing the following error:
Unexpected end of input at position 0
  (poison) lib/poison/parser.ex:55: Poison.Parser.parse!/2
  (poison) lib/poison.ex:83: Poison.decode!/2
  (hound) lib/hound/response_parser.ex:29: Hound.ResponseParser.parse/5
  (hound) lib/hound/request_utils.ex:48: Hound.RequestUtils.handle_response/3

This change just skips the response parsing if the status code is 204 and the raw content is empty (which it should be).

Thank you very much! :smile:


Consolidate exports to top-level index files

I find that when I go to import uses or creates in my IDE (IntelliJ), the IDE adds the import from @xh/core/modelspec.
That is fine and works, of course, but I would rather it be imported from @xh/core directly to reduce the overall number of import lines, and because we had wanted to standardize on requiring a single level of package nesting for most/common imports. If we only export the inner packages from the top-level index file, the IDE auto-creates the import statements as desired.
This would be a breaking change, of course, and would increase the size of these top-level index files. But it would also let us remove all the nested index files, and in the end I think it would encourage the import statements we want and potentially give us a bit more flexibility in the future to restructure nested packages with fewer breaking changes.
Thoughts?
Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[ ] Caught up with develop branch as of last change.
[ ] Added CHANGELOG entry, or determined not required.
[ ] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[ ] Updated doc comments / prop-types, or determined not required.
[ ] Reviewed and tested on Mobile, or determined not required.
[ ] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Totally agree that those internal index files were not intended for app-level imports.  Might we use a convention of, say,  _index.js ?  Just something to consider.

Thanks for taking a look.  I will enter a ticket for the comprehensive change
We can see if the _index.js approach looks helpful. I think it might just be a bit more confusing than it's worth (i.e. not immediately to a developer looking over the code why sometimes we have _index and other times index), but if the listings in the top-level index.js files get outta control that sounds like the best way to wrangle it.

THANK YOU for this!!

agree with all that.  If we organize the top-level index file by
sub-directory, I will be happy!
On Mon, Mar 30, 2020 at 7:11 AM Tom Tirapani<EMAIL_ADDRESS>wrote:

THANK YOU for this!!
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/xh/hoist-react/pull/1794#issuecomment-605937201, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARTL2JAQUO7WHXUUFDVE2TRKB47LANCNFSM4LUE3NEQ
.

Hi - sorry, why did we close this and delete the branch? I had asked Petra to continue working on this PR off of the branch/ticket.  It had been opened as a draft, so work was still ongoing.

Nevermind I see she opened a new one entirely.


Add missing ClientCompletionKeys

SpongeAPI | Sponge

https://github.com/SpongePowered/Sponge/commit/a9e71e73bc26c074687322d87eae022a464728bc


Add at least some test-coverage for the RenderTask.onContinue functionality

The default viewer, and thus Firefox, depends on the RenderTask.onContinue functionality to pause/continue rendering (such that the most visible page always renders first).
Despite this functionality thus being very important, it has however never actually been tested at all as far as I can tell. Hence this patch which adds a new boolean renderTaskOnContinue parameter (false by default), that can be used to force a reference-test to use the RenderTask.onContinue code-path in the InternalRenderTask class.
Note that I purposely made this new reference-test behaviour optional, since I didn't want to negatively affect the general runtime of the tests (given that there's a slight delay added to the rendering). Also, for e.g. benchmarking you'd most likely want to stay away from the RenderTask.onContinue functionality for similar reasons.

/botio test

Looks good!


Add flutter to existing app : No installed package from pubspec get registered

Added a flutter module in existing iOS app,
and the module works fine when run standalone followed the guide,
but when the app is ran inside the host,
none of the packages installed from pubspec.yaml works

How do i register all my plugins when presenting a view controller with implicit engine?
https://flutter.dev/docs/development/add-to-app/ios/add-flutter-screen#alternatively---create-a-flutterviewcontroller-with-an-implicit-flutterengine

Hi @carotkut94
can you please provide your flutter doctor -v and pubspec.yaml from your module?
Also, to better address the issue, would be helpful if you could post a minimal code sample in a repository to reproduce the problem
Thank you

@carotkut94
I hope you've solved the issue.
Closing as additional information isn't provided.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of flutter doctor -v please.


Crashes my mac

Can you please help me? when I enable the gpu plugin It crashes my mac after a few hours
here are my logs
jvm_crash_pid_7039.log
jvm_crash_pid_30251.log
jvm_crash_pid_56604.log
jvm_crash_pid_71781.log
jvm_crash_pid_99320.log
jvm_crash_pid_7992.log

So, you're having problems with runelite. Looks like we cannot help you because the crashes happen outside the JVM. runelite crashes inside the driver of the graphics card (AMDRadeonX6000GLDriver) and that's so deep inside native code that there isn't even a trace of the JVM inside the stacktrace. Best you can do is update your Mac (if you haven't already) and then report the problem to runelite.

So, you're having problems with runelite. Looks like we cannot help you because the crashes happen outside the JVM. runelite crashes inside the driver of the graphics card (AMDRadeonX6000GLDriver) and that's so deep inside native code that there isn't even a trace of the JVM inside the stacktrace. Best you can do is update your Mac (if you haven't already) and then report the problem to runelite.

Thank you. Sorry for bothering you and contacting the wrong person. Have a good day!


VMAP is not supported with live source stream

Workaround: do not use VMAP VAST tag with live source.

I did not observe any issues with live streams using VMAP.

Sometimes however I experienced some "stability" errors. Like:

midroll adbreak coming immediately after preroll adbreak
no autoplay after adbreak ended

@aFilipMalinowski yes, using midroll with live stream source may lead to unexpected behaviour as it is internally handled by IMA SDK.


glTF assets loading issue

Hi,
I am trying to load .glTF assets defined with relative paths and getting these exceptions:

java.io.FileNotFoundException: /data/user/0/com.arapp.factory/cache/1540463947423-0/../shared/lolipop.bin

CompletionException: java.io.FileNotFoundException: /data/user/0/com.arapp.factory/cache/1540466822606-0/0/glass1_transparent.png

Here is an .glTF fragment:
"buffers" : [
        {
            "byteLength" : 2433560,
            "uri" : "../shared/lolipop.bin"
        }
    ],
    "images" : [
        {
            "name" : "glass1_transparent",
            "uri" : "/0/glass1_transparent.png"
        },
        {
            "name" : "glass2_transparent",
            "uri" : "../shared/glass2_transparent.png"
        }
]

Would help with organizing shared assets such as .bin and some textures. E.g. multiple furniture variations. Currently everything has to be placed in the same folder.
I tried many variations and It does fail even in cases when you go only "deep" in folder structure. Am I doing something wrong or it is by design?  Would be great adding that feature. Thanks

The issue is that RenderableSource call method doesn't download correctly the files that are in a subfolder, compared to the location of the gltf file.

I have the same problem. Is there a workaround or somewhere a fix?

I have the same problem. Is there a workaround or somewhere a fix?


qdigidoc: fix TSL loading

These are what's used to regularly push new certificate fingerprints to clients, so we need to keep the original URL configured.
Use the same approach as fedora, ship an "initial" TSL as a patch, and also patch out the downloading part during the build phase.
This seems to reliably get ID Card and SmartID signing to work again.
Fixes #334397.
Fixes #307927.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

[x] I have built this change locally.
[x] I tested both mobile id, and id-card signing. All works now!! Hurray!!

PR for 24.05 is at https://github.com/NixOS/nixpkgs/pull/357559.


Set select2 id container

set id container set property data-s2-id-container on select:

Select a option
Option 1
Option 2
	...

The outer container itself doesn't have an id (usually you don't need it), but the selection container has the [instance-id]-container id set, the results container uses [instance-id]-results, and individual results use [instance-id]-result-[result-id].


nowarn falsely reports "annotation does not suppress any warnings" when suppressing unused private members

Compiler version
3.3.3
Minimized code
@scala.annotation.nowarn()
object Test:
  private val aa = "aa"

Scastie at https://scastie.scala-lang.org/OVJH4ESRR4iswVLoeyay2A
Output
@nowarn annotation does not suppress any warnings

Expectation
Should not output a warning since it suppresses a "unused private member" warning that would appear otherwise.
Similar to
Maybe a duplicate of #18341 ?

Maybe a duplicate of https://github.com/scala/scala3/issues/18341 ?

Seems to be the case.
I'm closing this, let's track it under #18341


nixosTests.3proxy: port test to python

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/72828
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg test 3proxy

@GrahamcOfBorg test _3proxy


Using multiple Jenkins servers

Is there a way to configure multiple Jenkins instance?
I tried to change jenkins to jenkinsA and jenkinsB in the config file and calling jenkinsA.job_status, but it doesn't work.
Before digging more, I was wondering if you know an existing solution.
Thank you.

@tomav, unfortunately, no, the problem being the env var configuration with multiple instances.
I don't have a solution for now, but I'll think about that :)

@plouc have a look at https://github.com/codeandfury/hubot-jenkins-enhanced. they are supporting env var based configuration with multiple instances

@plouc do you think you'll have a solution to this issue ?


CHAOS-4788 Add a note for network faults

Add a note for network faults

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65f984995dba58c3b9f8ebb4--harness-developer.netlify.app


How are double clicks handled?

I searched the documentation and found nothing about double clicks. I think there should either be some state for this in the mouse input event or at least a function to get the double click time from the system.
Keep in mind that triple clicks and so on also need to be supported. Triple click typically selects a paragraph in a text view.

@portstrom this is currently left up for the application to solve. In Alacritty, we record a timestamp whenever a click is received, and using a configurable timeout, watch for double and triple clicks.

Should be able to read system setting i think but would that be in the winit scope?


Add DispatcherDatasource to abstractions

https://github.com/aspnet/Routing/issues/527

@rynowak Are there abstractions required that I have missed?

what do you think we gain by moving this type to abstractions?

Ah, I mistakenly thought that MVC referenced only the abstractions so it had to be here.
Hmmm, right now I don't know enough about the use and purpose of the abstractions package to say where it should go.

Yeah I'm honestly not sure either.

what do you think we gain by moving this type to abstractions?

To help explore this a little more - if the data source is part of abstractions - then we're effectively saying "you can provide routing info by just referencing routing.abstractions". I'm not sure if that's going to shake out to be true, or untrue.

My perspective (I also want to hear yours): I not sure if it's a priority to enable you can provide routing info by just referencing routing.abstractions. Should we let other things happen and see if it comes up? I don't want to make a bunch of 2nd order and 3rd order decisions based on something unimportant.
It's also non-breaking to move a type from routing -> routing.abstractions.


Grafana plugin still using parameter "selectGroups" and "auth"

In the nginx error log I see a lot of messages saying that parameter "selectGroups" and "auth" are depretated
I'm using the latest version of the plugin.
I saw similar issues, they are closed, but my problem persists.
| Grafana | Zabbix | Grafana-Zabbix Plugin |
| 10.3.1    | 6.4.4    | 4.4.5                             |

same here, I see also:
PHP Deprecated:  Parameter "/real_hosts" is deprecated. in /usr/share/zabbix/include/classes/validators/CApiInputValidator.php on line 1516

#1931  should fix this


[Fix] Terraform - Updates for azurerm v4

Added subscription_id as required input to all modules. This is now required in azurerm v4. Marked as sensitive to prevent display of subscription id anywhere Terraform displays variable values
Updated route table property for bgp propagation from disable_bgp_route_propagation = true to bgp_route_propagation_enabled = false

Why did you pass subscription_id everywhere instead of running just this line before the terraform plan:

export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)

By adding the subscription id parameter you add a sensitive value in the script instead of just adding an env variable before runing the script @ibersanoMS @mosabami

@damienaicheh Both solutions have merit for different scenarios, but given that the new requirement only affects those using the Azure CLI and not a service principal or OIDC which would be used in most scenarios and CI/CD, I agree it's easier to use an environment variable than pass it as a variable.

Yes, but the Terraform documentation is not clear, maybe I missed something here:
This change will not impact users who use any authentication method other than Azure CLI, for example those authenticating as a service principal using the provider's native support, users authenticating using OIDC, or authenticating using managed identity.
...
By making it mandatory to specify the subscription ID for all authentication methods, this will also make it possible to implement a number of improvements to our authentication support in the future.
If the change has no impact for OIDC and managed identity so you dont need to update the scripts, otherwise you just use the export command if you run the az cli. That's my understanding.


Categories should be re-fetched again after updated

Summary:
Currently we have the function to edit categories from the app: #3851 . But unfortunately, we have a logic to fetch uploads only once when the contrib list is being loaded until we close the app. So, if the user changes the categories both from the app or from web interface, our contrib list remains same since it is fetched from db, not from servers. We should:
a- refetch all whenever an update is made (inefficient in terms of bandwidth)
b- fetch the specific field and update the db accordingly (most efficient in terms of bandwidth)
c- having a class to re-fetch the contribution from servers with all fields (so that we can use the same class to update descriptions or license along with categories). Then update the db with new contribution with contributionsRepository.updateContribution(Contribution contribution)  method.
Related classes to edit our local db are ContributionsPresenter, ContributionsListPresenter and ContributionsRepository.updateContribution(Contribution contribution)

yes, the app says something like "update success", but when looking at details it is not reflected there, which makes the user feel like: was it really updated?

@neslihanturan @nicolas-raoul Can I work on this issue?

I think the main problem has been fixed already?
I just tested: when I add a category within the app, it is immediatly visible.
Everything (including the filename and the image's binary itself) can be modified outside of the app, but for bandwidth reasons we can not update everything everytime, right? How about refreshing everything only if the user explicitely requests it, for instance with a swipe to the top?

@nicolas-raoul Yes, I know the problem has fixed now. But It just showing the new categories. It doesn't refetch the categories from the server. The app has a short-term hack to show the new categories. You can see in the image that there is a TODO in the update categories. But yes it's showing the updated categories. But as @neslihanturan mentioned in point "c". We can have a class for getting description, categories, licenses e.t.c. from the server and fetch with the help of the one class when required. (Fetch the new categories with the help of the class)
Also, your idea of refreshing everything when user swipes to the top is great.

So what should I do? Should I keep the updateCategories logic as it is in the app and  refresh everything when user swipes to the top or should I follow the "c" point of @neslihanturan

@nicolas-raoul Can you put your thoughts on this?

The current behavior is not shocking to me.
How about keeping it, removing the TODO comment, and implementing a swipe gesture that does what Neslihan described in the "c" point?

@nicolas-raoul Ok, I will do that. So when user swipes top the app should fetch all sections of the contribution item from the server. I think description, license, location, categories can be fetched together using getWikiText method. Is there any API for fetching Filename and image from the server for a contribution?


[KNI] pfpstatus: fix BaseDirectory bug

A typo disallowed user setting override of the builtin BaseDirectory. Turns out the builtin default is not needed or used, so remove it.

/cherry-pick release-4.14

backport: #124

backport: #126


use sdkmanager(1) instead of downloading compnents with wget(1)

Issue

N/A

Overview (Required)

Android SDK tools provides sdkmanager(1) that manages all the Android SDK components including constraint-layout
wget constraint-layout sucks. Use sdkmanager instead.
There are some circle-ci tweaks to make the build more stable

Thank you so much!! 👏


update PR: update for #679

This is an update for the PR #679 raised by @savvakism

NOTE: looks like he had not set up his git configs correctly, so the initial commit made by him is not well attributed :( 6a07d95

Good stuff, thanks! :smile:


Updated BE types and fix bugs with not being able to assign modules

Mostly changes to sync with BE: https://github.com/terraware/terraware-server/pull/2617
Also fixed an issue where module list is not showing up when assigning new modules, by using new module endpoints.

Thanks for all these changes Tommy! I was testing this and in the cohort edit view, I add a module and then delete it, and it doesn't get delete (I think it is just UI, because it happens after saving)

addressed the module changes not getting applied issue! In general there was a bit of weirdness around having no modules. (for example from deleting all). This should have fixed it now!


feat: Verify that every user wrote down their seed phrase

Is your feature request related to a problem? Please describe.
Currently a user can skip the seed phrase confirmation by reloading the page after a wallet is created.
Describe the solution you'd like
It should be verified that - no matter what - that the user wrote down the seed phrase.
Describe alternatives you've considered
The alternative is that a user might not have written down the seed phrase and is at risk at losing funds.
Which basically means: There is currently no alternative other than forcing the user to write down the seed.
Additional context
After creating a wallet a user will be asked to confirm the seed.
If the user (accidentally) reloads the page, a prompt will appear that asks:

This page is asking you to confirm that you want to leave — information you've entered may not be saved

However, a user can decide to reload anyway, in which case the wallet is created and Jam never verifies that the seed was written down.
A possible solution is to save the successful confirmation of a seed to local storage (per wallet).
However, this would mean that Jam needs to reconfirm the seed when browser data is deleted or browsers are switched (might be annoying...).
If you can think of other (read: better) solutions than this: Please state them as a comment here!

I thought we had a confirmation page? https://www.figma.com/file/kfejZJFlwBywvLEnPEmJo1/JoinMarket-UI?node-id=3754%3A73346&t=jXaHwHPykBPXLYJC-11
should be unskipable and on every reload, or back / forth its randomizing the 6 fields: so you have to write it down to confirm.

@theborakompanioni thanks for clearing things up again.

got it
you are right, lets keep it the way it is.
sound even worse

you are right, more thinking is needed. on the one hand, we don't want to annoy people and on the other hand we already had some failures in the chat, where people just think they are smarter until lightning strikes and the hard drive is toast…
we could implement more annoying steps like:

you want to do your first CJ? please enter word 7 to continue.
you want to create a FB? please enter word 12 to continue + [ ] don't bother me again.
you want to tumble the wallet? please enter word 3 to continue + [ ] don't bother me again.
we are not asking anymore.

sure, i dont think thats important right now and users understand the importance here.


ISPN-15101 Quarkus 3.2.3.Final

https://issues.redhat.com/browse/ISPN-15101
CI also upgraded to use GraalVM community edition 20.0.2.

Native tests is failing with
Error: Class-path entry file:///home/infinispan/.m2/repository/org/graalvm/sdk/graal-sdk/23.0.1/graal-sdk-23.0.1.jar contains class com.oracle.svm.core.annotate.TargetElement. This class is part of the image builder itself (in jrt:/org.graalvm.sdk) and must not be passed via -cp. This can be caused by a fat-jar that illegally includes svm.jar (or graal-sdk.jar) due to its build-time dependency on it. As a workaround, -H:+AllowDeprecatedBuilderClassesOnImageClasspath allows turning this error into a warning. Note that this option is deprecated and will be removed in a future version.

I tried to update graalvm/core to only include graal-sdk as a provided dependency, however this breaks the exec-maven-plugin and I couldn't get the plugin to add the graal-sdk to the classpath. So for now I have just included the flag -H:+AllowDeprecatedBuilderClassesOnImageClasspath and I will revisit this later when this is no longer supported.

merged! thanks @ryanemerson !


Make rewards transparent

The BASE_REWARD_QUOTIENT parameter dictates the per-epoch reward. It corresponds to ~2.54% annual interest assuming 10 million participating ETH in every epoch.
Is there a source for how this figure was computed? (I can get something close, ca. 2.1%, but not this exact figure)
I also would suggest that the maximum reward computation should become part of the spec. Then we could write a test case for it and if rewards are modified to not match this formula we would notice, which I would see as an advantage. Small changes could make a big difference here.

There is some discussion on this here https://notes.ethereum.org/s/rkhCgQteN#Base-rewards
Note that this is missing the "source" reward and should be 1/5
I haven't re-run the numbers, but I imagine the 2.54% is compounding whereas the 2.1% is not.

I also would suggest that the maximum reward computation should become part of the spec.

Do you mean a formula showing how this is derived?

I haven't re-run the numbers, but I imagine the 2.54% is compounding whereas the 2.1% is not.

Compounding make a tiny difference of 0.03% here, so it's not that. I guess I am unsure how many times exactly the base_reward can be applied, the block proposer reward is not obvious. Also relates to #944 -- is the number 5 exact there? Because I feel it's not.

Do you mean a formula showing how this is derived?
I would even go as far as including a function that computes the expected rewards per time period. Then we could add a test case and be sure that rewards will be what we expect them to be, no matter how we change the spec later :)

In #1159 I've recalculated the appropriate value for BASE_REWARD_FACTOR (previously called BASE_REWARD_QUOTIENT) based on the policy that max issuance is about 2^21 ETH when the total effective balance is 2^17 ETH.

Is there a source for how this figure was computed?

In the PR description I put the script used to calculate BASE_REWARD_FACTOR.

I also would suggest that the maximum reward computation should become part of the spec.

At some point we should have a "design rationale" document justifying, among other things, the constants.

Closing in favour of #1344

I also would suggest that the maximum reward computation should become part of the spec.

At some point we should have a "design rationale" document justifying, among other things, the constants.

I've glanced at #1344 and it's only a calculator without the 'design rationale' part. I'm hunting for the rationale. Is there a good link for that yet?

It should live in the annotated specs, though they go well into the rationale behind penalties and slashings and arguably not enough in the rewards:

https://github.com/ethereum/annotated-spec/blob/master/phase0/beacon-chain.md#rewards-and-penalties=
https://benjaminion.xyz/eth2-annotated-spec/phase0/beacon-chain/#rewards-and-penalties


fix(pristine): pristine uses initialvalue for comparision

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #3   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          72    103   +31
  Branches        3      5    +2
=====================================
+ Hits           72    103   +31

Impacted Files
Coverage Δ

src/use-formstate.ts
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow custom characters for vishraams

Puneet Singh mentioned that it would be nice to use spacing to differentiate vishraams. Though he understands that vishraams using spaces at the end of a line-break is difficult to figure out, it is still something he'd like to be able to do. Allowing custom characters would let him put say 4 spaces for heavy vishraams.

Presumably this would be a toggle?

It could just be an input box with a reset button too
On Tue, Jun 25, 2019 at 8:33 AM Harjot Singh<EMAIL_ADDRESS>wrote:

Presumably this would be a toggle?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ShabadOS/desktop/issues/43?email_source=notifications&email_token=ADLZ3B2RPQUXB4ROSKS44YLP4IGBNA5CNFSM4EL3VDVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYQCRTI#issuecomment-505424077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLZ3B4F6K65HPSF3JKHB7TP4IGBNANCNFSM4EL3VDVA
.

I do not believe this is helpful to enough users


v0.8.4: AlertDialog no focus multi textfield when keyboard above

Steps to Reproduce

showDemoDialog<DialogDemoAction>(
                        context: context,
                        child: new AlertDialog(
                            content: const TextFormFieldDemo(), // from flutter gallery text_form_field_demo.dart
                            actions: <Widget>[
                              new FlatButton(
                                  child: const Text('CANCEL'),
                                  onPressed: () {
                                    Navigator.pop(
                                        context, DialogDemoAction.cancel);
                                  }),
                              new FlatButton(
                                  child: const Text('DISCARD'),
                                  onPressed: () {
                                    Navigator.pop(
                                        context, DialogDemoAction.discard);
                                  })
                            ]));
                  }),

Please add the output of flutter doctor -v
and please also add a screenshot that shows the current behavior.
Can you please provide a complete running minimal example (main.dart) that only contains the code required to demonstrate the issue.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

How to make input fields appear above keyboard in Dialog?

what is the solution?


Swagger-tools raising security risks

Hi Team,
we are using swagger-tools and now our security team has raised a License issue with it as Swagger is using json-refs which inturn is using Slash.
Slash is flagged as vulnerable with GPL license.
Our current version is:
Swagger-tools : 0.10.1
→ json-refs : 2.1.7
→slash : 1.0.0 (Vulnerable)
we can upgrade it but slash vulnerability still remains and slash not in development from 2006.
Could you please let us know if we have any alternative here. It is very critical as our production release will be stuck.

Hi Swagger Team,
please let me know if there is any work around on this.
thanks
Sumit

Looks like this is an abandoned project, they should state that in their README

It's not abandoned, there is just a major feature freeze done and fixing this requires a major release.  Please see #335 for more details.

I'll take a peek.  Development on swagger-tools is halted, with only high impact bug fixes being implemented at this time.  Please see #335 for more details.

can there a release of swagger-tools with just updated third party modules? This will fix lot of security related issues.

@whitlockjc  is swagger-tools being deprecated? I would like to understand if vulnerabilities will be fixed.
Also, sway-connect doesn't seems to be a recent project and active mantained.
What is the alternative to swagger-tools that is being maintained?


Reduce timeouts while waiting for extension resources

What this PR does / why we need it:
Reduce the timeouts while waiting for extension resources to display errors provided by extension controllers faster.
Special notes for your reviewer:
/cc @ggaurav10
Release note:

The shoot flow does now propagate errors provided by extension controllers faster to the end-user (via the `Shoot`'s `.status` fields).

I need to do another follow-up commit in extensions as well


Order precedence if statement fix in README example

Demonstration:
var name = 'pull_request';
var action = 'reopened'

name == 'issues' && action == 'opened' || action == 'reopened' // incorrectly true
name == 'issues' && (action == 'opened' || action == 'reopened') // correctly false

That you very much for that catch and fix.


Error message indicating Controller class not found in drogon v1.9.2 which did not appear in v1.9.1

I have something which looks like this:
drogon::app().loadConfigFile(std::string("./") + APP_STRING_NAME + "_server/config.json");
auto cis_http_controller =  std::make_shared<APP_NAME::cis_controller>();
drogon::app().registerController<APP_NAME::cis_controller>(cis_http_controller);
auto drogon_main = std::thread([]{drogon::app().run();});

which worked OK with v1.9.1 but is flagging the issue in the title from drogon/lib/src/HttpControllersRouter.cc line 237.
Can you think of something that had changed which would cause that?
Thanks in advance.

@eniv thanks for your feedback. but I can't reproduce the problem in my environment. please paste the whole error log line which including the controller name.
BTW: I tested your code in my linux server with drogon 1.9.2, it works fine. And if your controller constructor has no parameters, there is no need to create it manually.

Thanks for the quick response.
I'm also on Linux. This is the exact error message: 20240124 03:51:47.860891 UTC 338518 ERROR Controller class not found: controllerClassName - HttpControllersRouter.cc:237
I got into the habit of manually creating controllers to keep things consistent with controllers whose constructors do take parameters.
Could it be related to a config setting?
I've attached my config.json which I've been using since version 1.8.4 (if I remember correctly)

Please remove the simple_controllers_map option in the configuration file.

That was it.
Thank you!


Links on 'blog page, to individual posts, are not visually apparent

On https://brew.sh/blog/ there are a series of post titles and abstracts, where the post titles link to the full text of each 'blog post.
However, there are no visual affordances that the posts' titles are actually links to the full posts, or that there is any more of the post to read than the initial paragraph.  An example of this is the post announcing v1.0.0 - it contains quite a bit of detail about the release, but it's not clear that all that information is there, because the heading of the post is not visually styled like a link, and there's no ~"read the full v1.0.0 article" link below the first paragraph.
Just having a "read more" link below each article's abstract would not be good for accessibility, because people using assistive technologies to browse the web often navigate through the links in a page (e.g. using Tab, or via a list of all links on the page) and in that case they'd just be presented with a series of identical "read more" links, rather than "read more about the v1.0.0 release" and so-on.  It is possible to include extra text in links to give such users the context of the link, without having it appear visually, as per Example 1 in the Web Content Accessibility Guidelines (WCAG) Technique for hiding some link text with CSS.
If you would like to address this, then a good simple approach would be to include such "read more about X" links (with sufficient context for users of assistive technologies, as above) rather than having the headers for each post as links, as doing so overloads their purpose (generally, heading elements are for navigation within the current page; links are for navigation to other pages).  However, if the heading links are to be kept, styling them in the same way as the other links on the site would be appropriate, so at least users know they're links.
A further, related issue [if you like I can file this separately] is that the contrast between link text and the page background is only 4.3:1, whereas 4.5:1 is recommended by WCAG as a minimum, and the contrast between body (non-link) text and link text is only 2.3:1, whereas at least 3:1 is a good minimum (and 4.5:1 is preferable if possible). One solution to this would be to lighten the link text a bit to get it to 4.5:1 and also have links visually underlined, so that even people who can't distinguish them from the body text by colour will still be able to tell they're links, due to the underline.

rather than having the headers for each post as links, as doing so overloads their purpose (generally, heading elements are for navigation within the current page; links are for navigation to other pages)

I don't agree with this, I'm afraid. I don't think I've seen many mainstream blogs where the headers for each post aren't links. It may well be they are doing it wrong too, I admit.

styling them in the same way as the other links on the site would be appropriate, so at least users know they're links.

Could you be more specific here and consider pasting some images, ideally annotated?

One solution to this would be to lighten the link text a bit to get it to 4.5:1

I'm up for this.

and also have links visually underlined

Similarly, I don't agree as it doesn't seem to be a mainstream requirement on the internet now for links to be underlined.

Any chance you'd be able to submit a pull request for any of these changes? That'd be the easiest way to discuss this further.

Thanks for your quick reply.  Happy to do a PR, though won't be able to until next week, so for now I'll answer what I can...
This image shows that there are two different types of links on the page (the heading links and the links in the body text).  Currently the only indication that the heading links are links is that the mouse pointer becomes a hand shape when resting over them (the other links are a different colour to the body text):

This also leads into underlines (or similar)… there ought to be a way to distinguish links from body text that does not rely on colour; some users may be using low-end monitors that can't display colours accurately; others may not be able to see the difference between colours very clearly.  The contrast between body text and link text is very low (only 2.3:1) and there's no visual clue that links are links, other than colour.  WCAG has more info on why using colour alone can be problematic for users.  There is also a suggested technique to distinguish links from surrounding text however this mainly relies on a stronger contrast between body and link text and thus does not fully solve the problem for users who are browsing on a touch-based device, as they have no :focus or :hover to rely upon to show the text decoration (though it would still be an improvement, of course).
Here is what the page looks like in in Mac greyscale mode (which sort-of approximates poor colour perception).  Imagine how it might look when on a mobile, perhaps out in daylight, or just on a desktop with sub-optimal lighting the difference between links and the rest of the text would be lost on some people):

The links' text is has only a ratio of 4.3:1 with the page background; glad to hear you're up for increasing this.  However, if you do increase the link text brightness so that the links are more easily readable (i.e. 4.5:1 against the page background) then the contrast between link text and body text would drop even lower than the present 2.3:1 and it will be even harder for people to distinguish links from the body text.
I would recommend some sort of decoration on links to indicate they're links (as this would keep the 'feel' of the site closer to how it is presently), but maybe it would be possible to find a different colour scheme under which links contrast clearly (>=4.5:1) with the background and at least 3:1 with the body text (though this could still leave out users who don't see the difference between colours so well, it would be an improvement, as above).

I'd missed the bold-ness of the link text at first, though yes, they are. (My sight isn't perfect, though that's not the only reason I am really for underlines on links :-).)
Just want to check the parameters for the PR I'm going to do; I understand they are:

Improve indication that some headings are also links.
Improve contrast between link text and page background.
Improve contrast between link text and non-link body text.

Are there any colours that you would rather I don't change?  I am not sure if it'll be possible, but thought I should check; I'm thinking priorities would be:

Page background colour
Body text colour
Link colour

I'm assuming that I won't be adding underlines or similar to links (though doing so may give more flexibility with respect to not changing the colours), and will of course try to keep as many of the colours the same/as close as possible, so the character of the site is the same.
If this sounds OK, I'll give it a go...

I'd missed the bold-ness of the link text at first, though yes, they are. (My sight isn't perfect, though that's not the only reason I am really for underlines on links :-).)

Ah, cool. Could make them even more bold, perhaps? Would underline-on-hover be any good?

Just want to check the parameters for the PR I'm going to do; I understand they are:
Improve indication that some headings are also links.
Improve contrast between link text and page background.
Improve contrast between link text and non-link body text.

Sounds good 👍 I expect there will be some back-and-forth.

Are there any colours that you would rather I don't change?

Basically the overall theme look should remain the same but we should just adjust specific colours as much as required.

will of course try to keep as many of the colours the same/as close as possible, so the character of the site is the same.

Sounds perfect.

If this sounds OK, I'll give it a go...

Full speed ahead, thanks again!

Sorry for the delay, though I believe I've finally got a got set of colours that increases the contrast between links and non-link text.  I used http://jxnblk.com/colorable/demos/matrix/ to tweak the background, body text and link text colours.
I've just noticed that you've added underlines to the links---this is excellent; it makes them much clearer to read (for me and I'm sure others).  I was thinking of simply making the links in headings the same colour as normal links, but I think your solution is better.
Was planning to submit a PR this evening with the new colours.  However my only concern about them was that, whilst increasing the contrast between body text and link text, they also decrease the contrast between link text and the background (this was the best solution I could find whilst preserving the feel of the original palette, and the link text to background ratio is still within the limits set out in WCAG 2 AA).  In light of your improvements to the links, though, I may revisit this slightly before submitting the PR.

I've just noticed that you've added underlines to the links—this is excellent; it makes them much clearer to read (for me and I'm sure others).

Thanks for the kind words.

Was planning to submit a PR this evening with the new colours. However my only concern about them was that, whilst increasing the contrast between body text and link text, they also decrease the contrast between link text and the background (this was the best solution I could find whilst preserving the feel of the original palette, and the link text to background ratio is still within the limits set out in WCAG 2 AA). In light of your improvements to the links, though, I may revisit this slightly before submitting the PR (can always tweak the PR as required, and discuss things there, of course).

I'm happy to defer to your experience. I'm sure there is going to be a little discussion before it's merged anyway so feel free to open earlier rather than later for conversation. Thanks again!

(This is in progress, via #167.)


Callback implementation and tests for write and end

This pull request attempts to resolve #80 and #46.  This PR adds conditional support for callbacks in versions of node that support callbacks.
Callbacks will be called on write and end when supported in nodejs (requires nodejs >= 0.12.x).
Credit goes to @jpodwys for the majority of the implementation.

It looks like this has the same issues as other PRs: It will sometimes add callback support to Node.js 0.10 and sometimes not, depending on if the response was compressed. In Node.js 0.10, callbacks should not work at all.

I've updated the PR to address your concern. Node.js 0.10 will never call the callbacks.  I also updated the tests to assert that no callbacks were happening (that test failed before I made the additional changes).

I've read through your comment. I've have been thinking a lot about it and doing some research.
The good news is that both spdy (https://github.com/indutny/node-spdy#api) and http2 (https://github.com/molnarg/node-http2/blob/master/lib/http.js#L1092) use http.OutgoingMessage in their prototype. So doing feature detection on http.OutgoingMessage.prototype.write.length seems completely appropriate and inline Express.js TC goal to support spdy and http2.

... so bugs from using this module with others causing almost impossible to debug hangs is not something I am looking forward to answering for a long time to come :)

I can see only 2 ways to solve this problem.

Throw an error if the callee supplies a callback and the underlying request doesn't support it.
Honor the OutgoingMessage api and pass through the callbacks in versions of node that support it.

The first approach eliminates your concern about "impossible to debug hangs" but will break anyone who is currently supplying a callback. The second approach puts the onus on the developer to only use middleware that support callbacks (if he needs the functionality) but can lead to "hangs" if any of the middleware he is using doesn't support the callback.
IMHO i think the second approach is the right one. It is best practice when proxying or monkey patching to maintain the original interface. So when compression overwrites OutgoingMessage.write or OutgoingMessage.end it should maintain the same function signature. I realize other middleware may not honor the callback but compression can be better and maintain the full functionality.

So doing feature detection on  http.OutgoingMessage.prototype.write.length  seems completely appropriate and inline Express.js TC goal to support  spdy  and  http2 .

No, it is not. The whole point is that we should not imply that that is going to be in the prototype. I'm not sure if the http2 module has changed since my comment, but that was simply an example, not the rule. If you distill it to a rule, the rule should be like you stated:

it  is best practice when proxying or monkey patching to maintain the original interface.

That means that if you are checking an object completely unrelated to the object you are given, how can you even be sure that you are maintaining the original interface at all?

I've removed the version bump from the PR.
I also implemented the first approach of throwing an error in a separate branch in my repo to see what it would be like.
https://github.com/whitingj/compression/commit/3462f9a031b80334081db406edfed6ebb4cd7785
After implementing it I'm not really sold on that approach.

Also, I don't think you understood that http2 source code; the OutgoingMessage on the line you linked to is not the one from Node.Js, rather it refers to the object defined in that file directly. AFAICT http2 module does not derrive from the Node.js OutgoingMessage instance at all

That sounds OK on the surface, but I suspect that will eventually run into issues because I'm sure there are a lot of monkey patching that does something like res.write = function () { return write.apply(this, arguments); } or similar where the .length may not reflect what it can do since it will eventually call .apply with the original arguments. If I knew a solution, I'm sure it would have been fixed already :)

And to be clear about what we want to do: we have determined over the years we need to make as little assumptions, especially with all the mocks and other servers out there. Even things like FastCGI implemented in Node.js and hosted with this on it can end up without the core Node.js prototype on the chain.
The more I think about your comments, I think we could simply defer fixing this until Express 5.0 and issuing a breaking change in this module that (1) requires Node.js 0.10+ (or even 4+) and changes the assumption that res.write and other methods accept a callback instead of even trying to detect it, which is basically a loosing battle in JavaScript.
So my proposal: let's just make the PR assume that everything supports callbacks and defer landing this change until a major version around the Express 5.0 time frame (which I think would be a few month or so).

@dougwilson thanks for being so responsive on this thread.  I've updated the PR to just pass through the callbacks. I didn't update the node version in package.json as I figured you'd do that when you merge and update to a new major version.  Please review the changes and let me know if I need to change anything.  Thanks and I'll be bugging you again closer to the release of express 5.0.

Hey y'all, any chance we want to revive this?  I'm running into an issue where I can't properly handle errors while attempting to stream responses using gzip compression.  Errors from res.write calls end up unhandled without the res.write callback.  Do you need some help getting this PR cleaned up to be merged, or are there outstanding issues with it?  Thanks @dougwilson for your continued support of this project!

Looks like it just needs a rebase now. I will rebase it and get it pushed out.


timedb/develop/scripts/install.sh｜ sh SELECT* FROMsystem_metrics ORDERBYts

This bug doesn't seem to be related by Niva. Could you provide more infomation?


add observation type RAM

inspired by Gym's Atari Env.
helps find out:

what can be achieved using RAM input
what challenges differ from image input
whether it helps to train on image -> RAM -> action vs just image -> action directly

I think this is an interesting idea, but uses the size of emulator state as the size of ram and I'm not sure this works with the current dict format of data.memory.  Do you have any interest in updating this PR @tycho01 ?

Yeah, states and RAM are different. Some states are even compressed, so that wouldn't be workable in the first place.

Some states are even compressed, so that wouldn't be workable in the first place.

hm, that does seem unfortunate. would you know if the affected portion of the roms presently used would be significant?
@endrift:

shape = (len(self.em.get_state()),)

[this] uses the size of emulator state as the size of ram and I'm not sure this works with the current dict format of data.memory.

oh. I'm not super familiar with the format used there. would you know what that's like? from get_state I couldn't quite make out anything about that. if I know what to do I'd gladly fix that.

would you know if the affected portion of the roms presently used would be significant?
I believe every single SNES game and possibly every single Genesis game, but I can't remember offhand.

Also state sizes can vary, so...yeah

okay, I'll close this PR then. if we find a way around these issues, I guess we can open a new one.

I think you don't use get_state at all, just use data.memory, reduce it to a single np.ndarray and use the size of that.

@christopherhesse thanks, I've updated it to directly use the shape of data.memory now.


Fix crash with ruby 2.5.0 'No method Dir::Tmpname.make_tmpname'

Ruby 2.5.0 removed the method make_tmpname ( https://github.com/ruby/ruby/commit/25d56ea7b7b52dc81af30c92a9a0e2d2dab6ff27 ), so I implemented the same fix that the rails team used.

Thanks for catching this! I made one small suggestion above, but otherwise this looks good to me 👍

No problem.  Okay, I renamed the method to tmpsock!

Thanks again. I've released your fix on RubyGems as 3.0.1.


Ubuntu WSL not showing icons

I've downloaded and intalled both lsd and nerd-fonts but the icons are failing to display

What environment are you using? I assume Windows? PowerShell?
You need to configure your Terminal to actually use the respective Nerd Font.

What environment are you using? I assume Windows? PowerShell?
You need to configure your Terminal to actually use the respective Nerd Font.

yes im using windows and ubuntu WSL.. how do I do this?

I'm not a Windows user, so I don't know, sorry. What's the terminal emulator that you user? What does it say in the title bar?
I'd assume it's PowerShell. Try googling PowerShell change font or something along these lines.

Fixed it.
needed to download de nerdfont directly on windows and not on the Ubuntu WSL
thanks for the help anyways!

Great to hear that and thanks for following up with the solution.
Can you close the issue then? :)

I've downloaded and intalled both lsd and nerd-fonts but the icons are failing to display
![image](https://user-images.githubusercontent.com/38656207/84038163-f383f280-a975-11ea-8128-3d5908eec494.png

I've downloaded and intalled both lsd and nerd-fonts but the icons are failing to display

hi, could you please give me hint on what exactly font did you installed in order for lsd to work properly, i.e. show icons?
I happed to download the whole repository of nerd-fonts from GitHub and installed them in one take, that is 387 fonts.
But none of them helped. And they are actually installed, 'cause I can use them in, say, MS Word and else. And I can even change the value of "fontFace" in settings.json file for my terminal. It also seems to work, except it doesn't help see the incons. Sooo ... I don't know =-(

@fontes99 how to download nerdfont diractly in windows ?

@SreehariTS03 as @fontes99 mentioned, you just have to download the font you want directly on windows, not using WSL, after that you can change the font of the WSL terminal on the settings option (I assume you're using WSL2).
You can find all the nerd fonts on:

nerdfonts.com/font-downloads or
https://github.com/ryanoasis/nerd-fonts#patched-fonts (try to download the ones that are optimized for windows).

After that, you should be able to see all the icon references on the terminal. Hope this works for you.


[Master | latest] member modal takes half the screen on mobile

Expected behavior
User sidebar is hidden until user swipes to see it (where it then fills 100% of the screen)

Current behavior
Sidebar takes 50% of screen

Steps to reproduce

Platform info

Meower Client

Meower Client Version + Build Date: last push in main

Desktop/Mobile Device

OS: Android
Version: 8
RAM: 4GB
Storage: 64gb

Did I read the instructions before making this bug report?

I have HAVE read the instructions.

updated with screenshots


How to make getKind() future-proof?

Version: 14.4.5
I have the following expression:
const ts = require('typescript');

return prop.getKind() === ts.SyntaxKind.PropertyDeclaration;

Before I upgraded ts-simple-ast and typescript this used to work, and would get inlined as 152 === 152.
After the latest upgrade this stopped working because now it inlines as 152 === 151.
I think this is related to a mismatch between the version of TS this library uses VS what my own package.json version is.
How can I make this expression future-proof?

You should import everything from ts-simple-ast. I'm not on a PC right now but I'm pretty sure it exports the SyntaxKind enum that it uses.
There are also type guards isPropertyDeclaration

Thank you! That's just what I needed.


Changes to the Debug window | fix travis

Pulled 3 relating commits into this one PR to have the order right and also fix Travis builds in one. Build with --disable-wallet works fine locally, now let's see if Travis wants to complain...

Added a workaround to fix travis for now, until the OpenSSL fix from 1.8.2 is pulled over


doc: translate dom-elements

Besides words mentioned in Glossary, I remain these untranslated.

server/client (side)
style
timestamp
key
property
pixel
camelCase
controlled component

Welcome for further discussion.

Fixed and updated!

@piovischioh thank you for translation, I merged it.


fix: workbench deployment + change path for its manifests in build

Description

sync to changes in ODH on workbench: to fix the problem of we did not apply correct workbench image before params.env gets updated
also uplift branch to 2.13 to get new manifests
refer to https://github.com/opendatahub-io/opendatahub-operator/pull/1226 but since it has the path change, cannot just sync from ODH to rhoai

ref: https://issues.redhat.com/browse/RHOAIENG-12409
How Has This Been Tested?

local build with PR: quay.io/wenzhou/rhoai-operator-catalog:v2.14.910-0
result similar to ODH PR
mock build with passing env for workbenchimages: quay.io/wenzhou/rhoai-operator-catalog:v2.14.910-2
enable workbench
2 CM created + imagestream created: quay.io/modh/.... are used
see both notebook-controller and kf-notebook-controller have issue to pull image which passed from Operator => expected, params.env is working to use these images instead of one from quay.io

Screenshot or short clip

Merge criteria

[ ] You have read the contributors guide.
[ ] Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
[ ] Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

/test rhods-operator-e2e

Is this required for 2.13 release branch?

/test rhods-operator-e2e

Is this required for 2.13 release branch?

no, this is the original PR which is targeting for "main"
with both fix for jira 12409 and some misaligement of workbench in ODH and RHOAI.
i created a new jira to follow this https://issues.redhat.com/browse/RHOAIENG-12732


Fix for Extended APDUs

Not all Java Cards that support extended APDUs have APDU buffer lengths long enough to include the attestation certificate. This causes registration to fail when extended APDUs are used, as is the case with iOS.
The fix is to build the extended responses incrementally instead of staging them all at once in the APDU buffer.
Note that this fix alone is not enough to enable support for native iOS usage (although it is required to do so). See #12 for more information.

Do not merge. Additional fix needed.


I want to compile CGO (trustcore) program for Linux execution on MAC, using XGO, but I have the following problems

I want to compile CGO (trustcore cgo) program for Linux execution on MAC, using XGO, but I have the following problems：
$ xgo --targets=linux/amd64 .
Checking docker installation...

Cross compiling wallet-services...
Building locally wallet-services...
Compiling for linux/amd64...
# wallet-services/blockchain/wallet
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:9:0,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBlockchain.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:10,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCurve.h:8:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:11,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDVersion.h:8:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:12,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHRP.h:11:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:13,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPrivateKey.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:14,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWData.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPrivateKey.h:11,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:14,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPublicKey.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPrivateKey.h:12,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:14,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPublicKeyType.h:8:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPublicKey.h:11,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPrivateKey.h:12,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:14,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWString.h:9:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPublicKey.h:12,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPrivateKey.h:12,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:14,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWPurpose.h:8:0,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinType.h:15,
                 from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWHDWallet.h:10,
                 from blockchain/wallet/wallet.go:8:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
In file included from /ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWCoinTypeConfiguration.h:8:0,
                 from blockchain/wallet/wallet.go:13:
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:47:18: error: missing binary operator before token "("
 #if __has_feature(assume_nonnull)
                  ^
/ext-go/1/src/github.com/trustwallet/wallet-core/include/TrustWalletCore/TWBase.h:56:19: error: missing binary operator before token "("
 #if !__has_feature(nullability)
                   ^
2020/04/21 09:30:56 Failed to cross compile package: exit status 2.

How can I solve it？

we haven't tried xgo, but from the error log, you need to use clang not gcc

Another error occurred when I compiled with clang：
`$ CGO_ENABLED=1 GOOS=linux GOARCH=amd64 go build
os/user
/usr/local/go/src/os/user/getgrouplist_unix.go:16:35: warning: passing 'gid_t *' (aka 'unsigned int *') to parameter of type 'int *' converts between pointers to integer types with different sign [-Wpointer-sign]
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/unistd.h:650:43: note: passing argument to parameter here
wallet-services
/usr/local/go/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: warning: ignoring file /var/folders/cy/7fkrjtpd4b37r0ldlhm_xxtc0000gn/T/go-link-201281400/go.o, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 )
Undefined symbols for architecture x86_64:
"__cgo_topofstack", referenced from:
__cgo_3298b262a8f6_Cfunc_mygetgrgid_r in 000001.o
__cgo_3298b262a8f6_Cfunc_mygetgrnam_r in 000001.o
__cgo_3298b262a8f6_Cfunc_mygetpwnam_r in 000001.o
__cgo_3298b262a8f6_Cfunc_mygetpwuid_r in 000001.o
__cgo_3298b262a8f6_Cfunc_realloc in 000001.o
__cgo_3298b262a8f6_Cfunc_sysconf in 000001.o
__cgo_3298b262a8f6_Cfunc_mygetgrouplist in 000002.o
...
"__cgoexp_07a0021afc18_secp256k1GoPanicError", referenced from:
_secp256k1GoPanicError in 000023.o
"__cgoexp_07a0021afc18_secp256k1GoPanicIllegal", referenced from:
_secp256k1GoPanicIllegal in 000023.o
"_crosscall2", referenced from:
_secp256k1GoPanicIllegal in 000023.o
_secp256k1GoPanicError in 000023.o
"_main", referenced from:
implicit entry/start for main executable
(maybe you meant: _ge25519_is_on_main_subgroup)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)`
My go env:
$ go env GO111MODULE="" GOARCH="amd64" GOBIN="/Users/yangminghai/git_workplace/go_projects/bin" GOCACHE="/Users/yangminghai/Library/Caches/go-build" GOENV="/Users/yangminghai/Library/Application Support/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="darwin" GONOPROXY="" GONOSUMDB="" GOOS="darwin" GOPATH="/Users/yangminghai/git_workplace/go_projects" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/usr/local/go" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64" GCCGO="gccgo" AR="ar" CC="clang" CXX="clang++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/cy/7fkrjtpd4b37r0ldlhm_xxtc0000gn/T/go-build085958413=/tmp/go-build -gno-record-gcc-switches -fno-common"

Have you tried the sample? it should work for both mac and linux

I have this problem too now
did you find any solution for that?
#if __has_feature(assume_nonnull)


test: fix g-code-testing hanging

Overview
This attempts to fix g-code-testing CI workflows that are failing in edge.
Changelog
See investigation in this Slack thread.
Something was failing behind the scenes with this error:
Could not open port socket://foo:9997: [Errno 8] nodename nor servname provided, or not known

Where foo was the name of my laptop.
That appears to come from here: https://github.com/Opentrons/opentrons/blob/528a4960fdc1dcb589d208e54a6201867fdb20e9/api/src/opentrons/hardware_control/emulation/proxy.py#L122
This PR's attempted fix is to replace that socket.gethostname() with a hard-coded "<IP_ADDRESS>".
Test plan

[ ] Make sure all CI is passing and nothing is timing out.

Note that timed-out workflows are gray in the GitHub UI, not red!

[ ] Make sure all tests (api and g-code-testing) are passing locally. Or, at least, the "fast" G-code tests, if you don't want to run the whole thing.

This isn't working for me, but I think it's because the tests are flaky for unrelated reasons.

If I run those failing tests individually, they pass.
I'm ticketing this as RQA-798.

Review requests
I don't remotely understand what was going on here.
Why did this suddenly start failing? Maybe something changed in the platform's name resolution logic? But we're seeing this across operating systems. Maybe something changed in socket.gethostname()? But we haven't updated Python, either.
Is it okay to change this URL? I don't understand its significance, or what uses it. This is a Unix socket, right? But if so, why does it have a port? Aren't ports a UDP and TCP concept that doesn't apply to Unix sockets?
Is it appropriate to use <IP_ADDRESS> here? I see this pattern elsewhere in our codebase (1, 2, 3, 4), but it doesn't make sense to me for the same reason the port number doesn't make sense to me.
Risk assessment
Medium.
This appears to be emulation-only code, so I don't think it can break actual robots, but it has the potential to cause very confusing failures in CI or in https://github.com/Opentrons/opentrons-emulation setups.

Okay so Amit wrote this a while back so I am going to do my best to explain what is going on.
If I remember correctly, when building the module emulators we ran into the issue of needing to replicate using the hw serial connection from modules to the robot-server.
Well replicating the USB connection was disgusting and way too much work. What was decided was to instead add a proxy between the modules and robot-server that would behave the same way the serial connection did.
This was implemented with an asyncio TCP socket server using asyncio.start_server. We call the server the emulator proxy.
We start a proxy for each type of module. Note that these proxies are TCP socket servers so that is where the port number comes from.
That proxy emulator proxy has the connection information for the robot-server already. When a module connects to it's respective proxy, the proxy in turn establishes a connection to the robot-server and acts as a pass-through for the data between both
BUT, because these are docker containers running on a single machine, they all have the same IP address. That is what is being retrieved with socket.get_hostname(). There might be some issue resolving the host name. But since they are all running on the same machine and only communicating over the internal docker network, it should be totally okay to just hard code it to <IP_ADDRESS>.

I'm also getting a couple of tests in /api/tests/opentrons/hardware_control/emulation/test_proxy.py failing ~50% of the time, but I guess that's also happening on edge now, so I don't think it's related to this fix. Ticketing that in RQA-804.


[Global/Emacs] add numerous rules

Reasons for making this change:
This file is missing definition for Emacs standard lisp package and famous packages.
Links to documentation supporting these rule changes:

https://github.com/auto-complete/auto-complete/blob/master/auto-complete.el#L134-L141
https://github.com/knupfer/haskell-emacs/blob/master/haskell-emacs.el#L48-L51
http://git.savannah.gnu.org/cgit/emms.git/tree/lisp/emms.el#n286
https://github.com/jwiegley/emacs-async/blob/master/async-bytecomp.el#L54
https://github.com/sigma/pcache/blob/master/pcache.el#L61
https://github.com/kiwanami/emacs-edbi/blob/master/edbi.el#L901
https://github.com/nonsequitur/smex/blob/master/smex.el#L44
https://github.com/tkf/emacs-request/blob/master/request.el#L62

@zonuexe conflicted currently, apologies! :cry:

@shiftkey I added comment to each lines.  Is this work as you expected?

@shiftkey Could you review this PR?

@zonuexe apologies for missing this. The problem with this big PR is that other smaller PRs are easier to review and they land first, causing conflicts again with your branch.

I bumped into this PR, after finding out that Emacs.gitignore ignores things like the server folder or dist folder 🤔
This changeset only makes it worse. request, var, games, bookmarks, tutorial would all be ignored in repos that have nothing to do with emacs.
It's great to consolidate templates and reuse, but at a much granular level, and at a much stricter level. If the server folder would have made it into the vscode-gitignore template, you'd probably have a riot.

ISSUES
There are many issues identified with this, including but not limited to the few attributed from within an adjacent pull node.


Installation Instructions Are Incomplete

After installing manually, because MELPA doesn't have Codeium and I am unaware of any other package installation which does, I attempted to perform M-x codeium-install. Emacs does not recognize codeium-install.
What are the instructions missing?

Do you have the command M-x codeium-init? Based on my experience, the -init does the same job.

We've written down various ways to actually install the package here. MELPA isn't an option unfortunately, but most other package managers should work. You need to install the Codeium package before performing M-x codeium-install.

Closing due to staleness. Please feel free to re-open if you are still experiencing issues.

Maybe you should add (require 'codeium) after (add-to-list 'load-path "~/.emacs.d/elpa/codeium.el").
I met the same situation as you. There was no codeium-install when I pressed the M-x, but I use it to solve!


R83 RPi3B+ RPi 7" touchscreen touch not working

Genuine RPi 7" touchscreen not detecting touches
RPi3B+
Chromium OS r83
Modified config.txt to enable 7" touchscreen display output (sourced details from a closed issue)
To Reproduce
Steps to reproduce the behavior:

Touch screen on wifi network selection screen, nothing happens

Expected behaviour

Touch screen on wifi network selection screen, selection registered and able to touch next button to continue

Earlier version (r77 r3) seems to work fine

The official screen enforces fkms mode, hence the previous need to modify config.txt. The current r86r1 build fixed this issue.


Unable to use in electron projects

I have an electron project which I am building using webpack.  I have configured the node-loader plugin so that any requests for .node files are handled correctly.  I also am using electron-rebuild to ensure the native module is built against the version of nodejs being used in my electron project.
Unfortunately, it still seems to error out with the following:
 ERROR in ./node_modules/nodegit/dist/nodegit.js
 Module not found: Error: Can't resolve '../build/Debug/nodegit.node' in 'C:\Users\atrauzzi\Development\atrauzzi\gerty\node_modules\nodegit\dist'
  @ ./node_modules/nodegit/dist/nodegit.js 18:11-49
  @ ./src/Layer/Domain/Thunktor/Git/CloneGitRepository.ts
  @ ./src/Layer/Gerty/Component/Repository/AddGitHubRepository.tsx
  @ ./src/Layer/Gerty/Component/Repository/AddRepository.tsx
  @ ./src/Layer/Gerty/Component/Workspace.tsx
  @ ./src/Layer/Gerty/Component/App.tsx
  @ ./src/Layer/Gerty/GertyServiceProvider.ts
  @ ./src/Bundle/GertyElectron.ts

The most suspicious thing here is the Debug as when I check the path it's trying to load, all I get is this:

It's a somewhat educated guess, but the fact that I'm only getting Release seems suspicious.  I'm just not sure of how to make nodegit request Release instead of Debug or alternatively how to make the build produce a Debug version.
It might be that the instructions to get going with electron and/or webpack need to be updated, but I'm hoping you guys can offer some help in the meantime.
😄

Have posed a general question to Stack Overflow, although I'd love any assistance from maintainers in getting this boulder moved!

check out my boilerplate project i created.   It uses Electron, Webpack, React and NodeGit.
https://github.com/newblord/electron-react-webpack-nodegit-boilerplate

Follow this article. All you will need is for your --target param to match that of the electron version you wish to compile to.

Hi

Follow this article. All you will need is for your --target param to match that of the electron version you wish to compile to.

Hi, can you ellaborate that? I use Electron and try to use nodegit. I installed nodegit through npm i. Thank you!

@atrauzzi
By chance, did you ever manage to get nodegit importing properly via webpack with electron?


Release Device is running on

Feature Request:
First of all: I really like your work!
A great thing would be to see, on which release the Device is running. Maybe by showing
Device ***
3 Commits behind latest.

I'm working on it right now - to select/show/check releases of application, pin device to release, and pin app to release

Fixed by my PR

@markFieldman Thanks for your contribution. I really enjoy the new interface :)
What do you think about my point, to show the difference between device commit and current commit, like mentioned above.
I think it would be a very comfortable feature, because the commit hashes dont really show me if its a commit from a year ago or not.


Create-react-app with typescript and const enums

Is your feature request related to a problem? Please describe.
Project templates like create-react-app use tsconfig.json with isolatedModules: true option. There is no support for const enums in ambient contexts (d.ts files).
Cannot access ambient const enums when the '--isolatedModules' flag is provided.ts(2748)

There is no way to use LineStyle, CrosshairMode, LineType, PriceLineSource and PriceScaleMode in such environments.
The workaround is to use literal values for example 1 instead of PriceScaleMode.Logarithmic.
Describe the solution you'd like
It would be nice to have this enums as normal enums, or other solution which can help.

Actually that const enums have output in JS code so importing should works in both JS and TS envs, but it looks like TS doesn't understand it so far. I'll prepare an issue for TypeScript soon.

Here we go https://github.com/microsoft/TypeScript/issues/37774

Ok, looks like we can't wait for "feedbacks" in TypeScript repo. We'll fix it from our side: https://github.com/timocov/dts-bundle-generator/issues/110.


AppImage shows developer console

The AppImage shows only the developer console as seen here on Ubuntu MATE 16.04:

Hi @probonopd what's shown at the DevTools console?

Thank you! We're so sorry, Libris is currently under development and ~it has too many bugs~ we are so grateful with everyone that tell us any issue found. I'm gonna fix it on this new commit, in the meanwhile (this is not a fixing but I think it'd work) you can copy the config.json file wrapped at the repo or create a new config.json file in your /home/me/ directory
{
  "directory": "default",
  "extensions": [ "epub" ]
}

I promise to give you some pretty good news as queekly as possible 💌
Again, thank you ❤

Hello @probonopd I think commit c38ebb96d374380858bafb3d299b3f1409b7dfaf fixes this error.


Recipe and import content

Will there be in a deployment plan an option to export a recipe that define also the 'schema' of a content type?
Then, will there be an admin UI to import a recipe?

Yes, we need more "deployment steps".

Will there be a new RecipeExecutionStep in Orchard.ContentTypes that allows to import a 'schema'?

There will be one, once someone creates it. And it should be simple as the content types definition is already stored as a json document in the database. So exporting/importing should be straighforward, and the import might just work with the JObject.Merge method.

In order to migrate my existing blog, I will try to generate the json data to include in a recipe to import (during the setup, because for for he moment, there is no import page) the existing blog and blogpost.
One way to achieve this would be to create a Migration module in O1 that allows to export the data by serializing them in json.

I am currently working on an O1 module that allows you to export the contents to a json recipe that you can import with Orchard Core.
I already managed to export the blog posts and generate a OC 'setup like' recipe.

Is there an easy way to import from Orchard 1.10.2 ?

Not yet!!! In the works :)
Sent from my iPhone

On 23 Jul 2017, at 08:41, Atiq Rahman<EMAIL_ADDRESS>wrote:
Is there an easy way to import from Orchard 1.10.2 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


New reflected Class not included when executing the application with GWT superDev mode

Issue details
It seems like the reflection cache isn't updated, when you test the application with the GWT superDev mode (gradle html:superDev). This leads to the error Couldn't find Type for class, when the application is recompiled, after a new class thats used with reflection has been added.
Reproduction steps/code

Include an empty package to the reflection

<module>
	<source path="com.application" />

	<extend-configuration-property name="gdx.reflect.include" value="com.application.reflect.me" />
</module>

Start the code server (e.g. with gradle html:superDev)
Test that the application runs error free
Create a new class in the previously added package and create a new instance with the reflection API
Recompile the application

Workaround

Stop the coder server
Package the application for the web (e.g. with gradle html:dist)
Start the code server again

If there's no way to fix this properly, please add a note to the reflection wiki page.
Version of LibGDX and/or relevant dependencies
1.9.6-SNAPSHOT
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[x] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

Confirmed, looks like the cache gets recreated on compile, but it doesn't pick up any changes. @MobiDevelop any ideas?
The workaround just requires shutting down the superDev instance and restarting it, no dist required.

Yes, I can confirm that restarting the superDev instance is enough to update the reflection cache.
I don't think that there's an easy way to fix this, since other frameworks that rely on reflection (like artemis-odb) have the same issue. But a note in the reflection wiki page would be helpful.

There are some other things not updated or recompiled when you just recompile from superDevMode, for example assets or changed dependencies.  As TomSki said, you have to shutdown the server and restart the compilation process.


can't use all the accounts as owner in tronbox test

I was writing test cases for my contract.
and I needed to switch the owner account to access the contract functions.
tronbox only picks the first account (accounts[0]) as the owner.
I don't see any way to switch the owner's account other than changing the private key in tronbox config file.
(sending { from: address } with a transaction is not working (it worked with truffle))

The owner is the address that deploys the contract, which using Tronbox is accounts[0].
I guess you should add a function in your contract to change the owner.

@sullof Yes, I've added a function to change the owner.
But when I transfer ownership to account[1] or any other listed account, I can not use that to call any function.
let's say i have a function which only returns the address of the caller of that function.
function test() public view returns(address sender) {
    sender = msg.sender;
}

now, in test cases, this function will always return the address of accounts[0]. I simply can not make a call from other accounts.


Twitch Chat Commands do nothing

I downloaded the zip file - extracted all files - created browser source with local file - edited configs.js file with twitch oauth token and channel/username - i can run tests and they are successful in streamlabs but when i type !task create a timer nothing populates on the overlay. I made sure oauth and username were correct... what am i doing wrong?   ?-?

style changes work! but interacting with it using twitch chat commands does nothing to the overlay

Can you please show the chat screenshot of you trying the commands and the config.js screenshot with oauth blacked out?

I have the same issue


Not tracking at all in 0.16(722)

Hi
After install the new 0.16 version, my tracker does not track at all in any way. It seems after upgrade to 0.16 I am the only one reporting this problem. So I am wondering if there is a specific path of hearthstone directory to set in the preference, since I am installing the new one rather than upgrading and I totally forget how to do that.
Best
Chen

All right, it seems a lot of people have this problem right now. So I just closed the problem and wait for the next version to come.


0.7 k8s fails after reboot

As discussed in in other issue:
[root@k8s-master ~]# kube-config info
Architecture: armv7l
Kernel: Linux 4.4.15
CPU: 4 cores x 1200 MHz

Used RAM Memory: 135 MiB
RAM Memory: 922 MiB

Used disk space: 2.7GB (2773068 KB)
Free disk space: 53GB (55253568 KB)

SD Card/deb package was built: 18-07-2016 20:11

kubernetes-on-arm:
Latest commit: 1d0bbe1
Version: 0.7.0

systemd version: v230
docker version: v1.10.0
kubernetes server version: v1.2.0

CPU Time (minutes):
kubelet: 0:15
kubelet has been up for: About a minute
apiserver: 0:15
controller-manager: 0:03
scheduler: 0:00
proxy: 0:00
[root@k8s-master ~]# kube-config info
Architecture: armv7l
Kernel: Linux 4.4.15
CPU: 4 cores x 1200 MHz

Used RAM Memory: 135 MiB
RAM Memory: 922 MiB

Used disk space: 2.7GB (2773068 KB)
Free disk space: 53GB (55253568 KB)

SD Card/deb package was built: 18-07-2016 20:11

kubernetes-on-arm:
Latest commit: 1d0bbe1
Version: 0.7.0

systemd version: v230
docker version: v1.10.0
kubernetes server version: v1.2.0

CPU Time (minutes):
kubelet: 0:15
kubelet has been up for: About a minute
apiserver: 0:15
controller-manager: 0:03
scheduler: 0:00
proxy: 0:00

Startup of k8s-master: https://gist.github.com/Mangirdaz/4857bf6502f935795b46ba2ff4ba9a17
reboot initiated:
https://gist.github.com/Mangirdaz/092b8d80c9244effaadfa4036b0b1f1f
failure:
Jul 18 23:05:59 k8s-master sh[710]: See 'docker run --help'.
Jul 18 23:05:59 k8s-master systemd[1]: k8s-master.service: Main process exited, code=exited, status=125/n/a
Jul 18 23:06:01 k8s-master docker[721]: Failed to stop container (k8s-master): An error occurred trying to connect: Post http:///var/run/docker.sock/v1.22/containers/k8s-master/stop?t=10: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Control process exited, code=exited status=1
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Unit entered failed state.
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Failed with result 'exit-code'.
Jul 18 23:06:06 k8s-master systemd[1]: k8s-master.service: Service hold-off time over, scheduling restart.
Jul 18 23:06:06 k8s-master systemd[1]: Stopped The Master Components for Kubernetes.
Jul 18 23:06:06 k8s-master systemd[1]: Starting The Master Components for Kubernetes...
Jul 18 23:06:08 k8s-master docker[738]: Failed to kill container (k8s-master): An error occurred trying to connect: Post http:///var/run/docker.sock/v1.22/containers/k8s-master/kill?signal=KILL: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:10 k8s-master docker[747]: Failed to remove container (k8s-master): An error occurred trying to connect: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:11 k8s-master systemd[1]: Started The Master Components for Kubernetes.

docker:
docker.service: Failed with result 'resources'.
will give it proper debug cycle later, but suggestions and hits are more than welcome :)

v0.8.0 is released, and it does not support reboots.
Closing...
Did you ever find a solution?


All Decor Items spawn when creating a new run

When I open a new or old save file all decor items(dartboard ,sign ,and both rugs) all spawn in without me buying them.

idk it went away


Multiple plots with independent legends

Greetings,
I've been trying to use
`
figure;
t = 0:0.01:5;
subplot( 1, 2, 1 );
plot( t, t, t, sin(t), t, cos(t) );
[~, l1] = legend( {'a', 'b', 'c'} );
subplot( 1, 2, 2 );
plot( t, t.^2, t, sinh(t), t, cosh(t) );
[~, l2] = legend( {'d', 'e', 'f'} );
plot2svg( 'myname.svg', '', '', [l1; l2] );
`
But the output svg file contains double legend l1 and l2 for each subplot. Am I using the function incorrectly for this kind of situation?
Kind regards,

fixed with commit a1aea03a9eb39f65648dcdeeb8dc09d71078f29f

it wasn't implemented. now you can do it as follows:
plot2svg( 'myname.svg', '', '', {l1 l2} );

Thank you for the quick response! I was thinking about the same fix in case there was nothing else planned. :D


Support for netstandard2.0

Currently DartSassBuilder targets .net60 - thus not able to include in .net frame projects. Can this be made work with .netstandars or multitarget ?

Hi @mediabuff  - you should be able to include it in .NET Fx projects.
Although DSB targets the latest .NET versions, your project doesn't need to because it executes before your application builds. The only requirement should be that your OS has the targeted .NET installed.

Thanks for your response. I thought I was  unable to see the DartSassBuilder package in Visual Studio IDE Nuget Package Manager in .Net Fx projects.  Where as LibSassBuilder had worked. Now I am not able to reproduce. Will try to find a non-working project.