tensorflow-bin build fails

Describe the bug
Error on installation of tensorflow-bin on nixpkgs master branch
ERROR: Could not find a version that satisfies the requirement tensorboard<1.15.0,>=1.14.0 (from tensorflow==1.14.0) (from versions: none)
ERROR: No matching distribution found for tensorboard<1.15.0,>=1.14.0 (from tensorflow==1.14.0)

To Reproduce
Steps to reproduce the behavior:
nix-env -iA nixos.python37Packages.tensorflow-bin

using unstable channel
Expected behavior
tensorflow-bin should install without an error.
Metadata
Please run nix run nixpkgs.nix-info -c nix-info -m and paste the result.
% nix run nixpkgs.nix-info -c nix-info -m                                                ~
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.84, NixOS, 20.03pre201791.c1966522d7d (Markhor)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.1`
 - channels(arsleust): `"home-manager"`
 - channels(root): `"nixos-20.03pre201791.c1966522d7d"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - tensorflow-bin
# a list of nixos modules affected by the problem
module:

the main tensorflow package has been bumped, this should probably be bumped as well

This breaks tensorflow on darwin
cc #71282
cc @timokau
I could not find whl for 0.15.0. This page lists some: https://www.tensorflow.org/install/pip
But 0.15 is not there for some reason.

I'm not maintaining the tensorflow-bin package, but I'm sorry that I forgot to update it along with tensorflow.
Do we even still need it? The source package works pretty well.

Building tensorflow from sources fails for non-sandboxed setups because of its dependency on bazel (https://github.com/NixOS/nixpkgs/issues/66311) so this package is the only way to reliably install tensorflow there.

I could not find whl for 0.15.0. This page lists some: https://www.tensorflow.org/install/pip
But 0.15 is not there for some reason.

I found some 0.15.0 whl's on PyPi:
https://pypi.org/project/tensorflow-cpu/#files
However they seem to require tensorflow-cpu-estimator instead of tensorflow-estimator, so we would need to add that package. Also, this way of downloading would break the patterns used in the current tensorflow-bin, we would have to switch it to use fetchPyPi, probably. I don't think I will take on this.

Do we even still need it? The source package works pretty well.

Yes, another reason is because tensorflow-bin is the tensorflow on darwin.

I'm not maintaining the tensorflow-bin package, but I'm sorry that I forgot to update it along with tensorflow.
Do we even still need it? The source package works pretty well.

Building tensorflow is very, very long. Most people don't want that.
Or maybe I misunderstood something.

Yes, I think that is a misunderstanding. There is a binary cache that will save you from having to build anything yourself unless you choose to.

although, having to do overrides to get old versions does usually cause a rebuild. I ran into a runtime issue with the tensorflow-1.15 package (not sure if issue with 1.15 in general, or just our build), and had to revert it back to when 1.14 still built...

True, but in that case you could revert the whole tree to a known-good state (just as you would with the binary package).

Yes, I think that is a misunderstanding. There is a binary cache that will save you from having to build anything yourself unless you choose to.

Ok thanks. Is it because I want it to support CUDA that the regular tensorflow package does a full build from source on my computer ?

Probably, I think hydra doesn't build unfree packages. Its unfortunate that cuda support has to be present at compiletime and can't just be detected at runtime. Maybe there's some way to achieve that.

Let's update tensorflow-bin to latest 1.x version; that is 1.15

This is still broken now in the 20.03 branch, and an update has other side effects:
py2 support is gone in the latest 1.15, also the naming scheme of the packages changed.
There are also incompatible dependencies (gast==0.2.2, opt-einsum, ...?).
Maybe the easiest fix is a private bundled downgraded tensorboard.

ERROR: Could not find a version that satisfies the requirement tensorflow-estimator<1.15.0rc0,>=1.14.0rc0 (from tensorflow==1.14.0) (from versions: none)
ERROR: No matching distribution found for tensorflow-estimator<1.15.0rc0,>=1.14.0rc0 (from tensorflow==1.14.0)

I think #116496 solved this.

Also relevant #121998


Add performance regress test_ondemand_download_churn.py

Summary of changes
Add performance regress test test_ondemand_download_churn.py.
Closes https://github.com/neondatabase/neon/issues/7146
Tagging @problame
Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Please re-request review once you've made changes. I'll be unavailable until next Tuesday.

The tests with 10, and 100 concurrency_per_target fail at the end but still produce results... I will try to investigate it a bit further.

I have found the issue and fixed it with the last commit. The requests are dropped at the end of the test and it is detected as an error in logs.

Sorry for the late reply.
I merged from main and pushed some changes, mostly orthogonal to yours.
Couple of high-level remarks:

The ondemand_download_churn.rs should produce absolute numbers instead of the per-second average.
the addition of AWS_ENDPOINT_URL: I guess you needed that for minio. At Neon, we use AWS_PROFILE for this sort of stuff. So, you'd use a custom aws profile for the minio S3 endpoint. An example for how to configure the profile is givin here. Would be nice if we can streamline your instructions in the README to just use AWS_PROFILE.

Again, sorry for the delayed reply. Let me know if you're still willing to pick up this PR.

No issues, yes I would like to pick it up, and finish this test

Thanks, go ahead and re-request review from me if that's possible, otherwise reply to this thread.

The ondemand_download_churn.rs should produce absolute numbers instead of the per-second average.

I have changed the output to look like this now:
{
  "downloads": 447,
  "evictions": 609,
  "runtime": {
    "nanos": 32640994,
    "secs": 30
  },
  "timeline_restarts": 1
}

the addition of AWS_ENDPOINT_URL: I guess you needed that for minio. At Neon, we use AWS_PROFILE for this sort of stuff. So, you'd use a custom aws profile for the minio S3 endpoint. An example for how to configure the profile is givin here. Would be nice if we can streamline your instructions in the README to just use AWS_PROFILE.

I have also added usage of AWS_PROFILE to replace AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Using endpoint_url in profile still does not fix how the pageserver command is constructed, since endpoint needs to be explicitly defined for pageserver for it to work in:
./target/release/neon_local init --config=/tmp/tmphvpqctqc --pg-version 15 --pageserver-config-override=remote_storage={ bucket_name = "neon-bucket", bucket_region = "eu-central-1", prefix_in_bucket = "2eedf453-65aa-43b7-a1ed-379824d75180/test-download-churn-release-pg15-1-tokio-epoll-uring-30-/pageserver", endpoint = "http://<IP_ADDRESS>:9000" }
 --pageserver-config-override=page_cache_size=16384 --pageserver-config-override=max_file_descriptors=500000

The endpoint is optional: https://github.com/neondatabase/neon/blob/c18d3340b5e3c978a81c3db8b6f1e83cd9087e8a/libs/remote_storage/src/lib.rs#L557-L563
Also, this week, I merged a bunch of PRs that change how neon_local populates pageserver config; tl;dr: the config override stuff is gone, the [[pageservers]] section in .neon/config is gone, and .neon/pageserver_$i/pageserver.toml is only written once during neon_local init.

I'll try out your instructions and changes and report back.

@jbajic I took the time to write some more elaborate docs on test suite & remote storage: https://github.com/neondatabase/neon/pull/7664
Can you try the instructions in that PR? Keep in mind that you need my changes from that PR, so, I recommend you rebase this PR on top of it.

Please re-request review once more when PR #7664 has been merged and this PR has been rebased 🙏 We're close to wrapping up!

Thanks for the fix! I have rebased and removed redundant changes.

@bayandin  I think this benchmark makes sense when run on EC2 against real S3.
https://github.com/neondatabase/neon/pull/7242
Should we mark it skip until we have that?

https://github.com/neondatabase/neon/issues/6297

Merging main and doing a CI run to get benchmarks run in https://github.com/neondatabase/neon/pull/7717 (I've added a label to that PR)

Last commit for fixing the error:
ERROR test_runner/performance/pageserver/pagebench/test_ondemand_download_churn.py::test_download_churn[release-pg14-github-actions-selfhosted-100-std-fs-30] - AssertionError: Log errors on pageserver_1: (9559, '2024-05-13T14:09:35.888170Z  WARN request{method=DELETE path=/v1/tenant/f40d46f8ad8e8508aa35f94adfeb9048/timeline/7ee05d10dd8bd3b978e809763cb7f98d/layer/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000034CD1261-000000003567D801 request_id=7cf26d30-7520-460f-aff8-af55c710e2f8}: request was dropped before completing\n')

It's done, @jbajic ! Thanks for your patience!

Thank you for the support and reviews!


object disappears to infinity when dynamic-body enabled

I am probably doing something wrong, but here's what happens: You have an object already in the scene. Then programmatically you turn on dynamic-body with setAttribute(). The behavior I'm observing is the object disappears, and if you find it in the editor has one of it's X, Y, or Z coordinates set to infinity/NaN.
There's probably some synchronization and other function calls needed to allow this to work better, to support building a scene where you can programmatically enable/disable physics. I've tried setting dynamic-body ahead of time, with "type: static" then switching it, same behavior results.

I have the same issue

Could you share a demo?

FWIW I can no longer reproduce this issue. I think it had to do with when I was turning on the dynamic-body as 'dynamic' attribute. Just stumbled across this, and feel it could be closed now


Toyota transformer may incorrectly process base price

transformer.transformers.parser.BodyStyleParser may in some cases not pull the base model price for a BodyStyle, but a slightly higher price for the configuration.
The price is a valid price for a configuration of the BodyStyle but may not be the lowest.

Fixed By a57704d659136449ea8d676e623e3acc7ef45bcc


Documentation Update for postcommits-policies-details.md

Fixing minor grammatical error in Documentation
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM, but I have no approval power, sorry.

Closing since I don't think we should take this. If you disagree/would like to engage further feel free to comment or reopen


Add LTR390 sensor with switching mode example

@brentru was thinking something like this for the switching light modes between Ambient Light (ALS) and UV (UVS) modes, inside  each event type.

@brentru that should be okay now. I've still not enabled standby mode between reads. Currently it feels like power usage is less important than having readings readily sampled, but maybe once we cover deep-sleep on esp32 we can revisit such thoughts


Only set query attribute if it exists

Proposed Release Notes
Fixed error when no query is provided
Links
https://www.apollographql.com/docs/apollo-server/performance/apq/
Details
In cases when apollo client is using persisted queries the query parameter is not sent in the request. In theory you could set the query has as an attribute but I just wanted to fix the 500 error.
This fixes a 500 error we had where cleanQuery was doing a regex on the value undefined.
TypeError: Cannot read property 'replace' of undefined

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

https://github.com/apollographql/apollo-server/blob/main/packages/apollo-server-types/src/index.ts#L88
Yup, looks like it is optional

Great catch @MightySCollins and thank you for the quick fix!  We'll push this fix through and get a patch release out in short order.
Are you using apollo-link-persisted-queries to persist the queries?  I just added a bug fix issue to capture the query whether its persisted or not and if you could add any extra context to it that would be awesome!
https://github.com/newrelic/newrelic-node-apollo-server-plugin/issues/57
Thanks!

Hey @MightySCollins, we just released v0.1.1 of this plugin with your fix if you want to upgrade. Thanks again for the contribution!


Added Unit Tests.

Added Both Build and Unit Tests.

Hey @offensive-vk ,This PR is completed?
can we merge it?

We can merge it either today or tomorrow.
You can also merge it @npm-run-test


Draw all tile indicators behind player option? Option to remove the arrow from the rs3 style destination indicator?

As title says would these 2 options be possible?

Yes, both should be possible.
Just a clarification: when you say all tile indicators do you mean the tile markers from the tile marker plugin?
I am quite busy at the moment, so could be a couple of days (1 week?) until i get around to it.

Ah, Yes I realise now that the tile markers are from a different plugin but yes that is what I meant. The arrow for the rs3 style destination indicator can be quite offset from where the actual destination is depending on the distance and angle of the camera.

cant see the options in runelite?

All working as inteded as far as I can see! Genuinely awesome that all the tiles are behind the player now!!

perhaps the only other feature I would request is an option to make all tile indicators round like the rs3 destination tile marker so they can be matching, but thats pretty niche I feel


Default uuid not working

Seems no default uuid code is generated;
import (
	"github.com/facebookincubator/ent"
	"github.com/facebookincubator/ent/schema/edge"
	"github.com/facebookincubator/ent/schema/field"
	uuid "github.com/google/uuid"
)

func (Table) Fields() []ent.Field {
	return []ent.Field{
		field.UUID("id", uuid.UUID{}).Default(uuid.New),
		field.Time("expires_at").Default(ExpiresDay),
	}
}

Hey @moh-abk,
What does it mean "no default code is generated".
We have code testing exactly this (1, 2) and I've just checked this locally (created another test for this #434) and it's working fine.
Closing, but please open if you find an actual bug.
Thanks

@a8m this line - https://github.com/facebookincubator/ent/blob/master/entc/integration/customid/ent/schema/blob.go#L24 is not for the id field -- the code is not generated for field.UUID("id", uuid.UUID{}).Default(uuid.New) where the table id field is uuid
I get insert node to table \"table_name\": pq: null value in column \"id\" violates not-null constraint"
I've to manually add SetID(uuid.New()).

@moh-abk got it! I just added it to the id field #436, and I'll merge this tomorrow.
Thanks for reporting this issue.


Fill or remove empty output in reservoir segments

This should not be a major issue with v02 as we explicitly index all output in dataframes.
Also, topological changes in #76 should prevent issues.

This should not be a major issue with v02 as we explicitly index all output in dataframes.
Also, topological changes in #76 should prevent issues.


However, I have run into an issue. I will describe what I am attempting, how I am attempting it and the results, along with a few screen shots to show the issue.
On a tour schedule for this particular project, there are roughly 30-50 dates displayed at any given time. When clicking on a venue name, it fires the modal with the relevant show and venue info. I am using a PHP foreach loop to display each show's respective row (
from Foundation) and after the ending tag, I have the modal code.

Mar

07

              Wednesday

              5:00pm

BB’s Lawnside BBQ

            Kansas City, MO

Cancelled

BB’s Lawnside BBQ

Kansas City, MO

[google map]

Cancelled

Address
1205 E 85th St

Phone
816-822-7427

Website
http://www.bbslawnsidebbq.com/

            ×

This fires the modal, but more often then not, the modal is displayed in a strange place. And as you go further down the show listing, the modal gets pushed further and further down until it goes WELL below the footer of the page and you have to scroll quite a ways just to see the darn thing.
I have tried moving the modal code outside of the the ending div tags but when I do so, no modal windows fire at all when clicked.
The first show in the list - when clicked the first time displays the modal almost completely above the entire page (only partially visible): https://skitch.com/brilliantdick/889b4/shows-trampled-under-foot
Then after you close it, and re-click the first venue link, the modal is actually displayed in the proper place: https://skitch.com/brilliantdick/889n1/shows-trampled-under-foot
This has completely boggled me and I'm almost to the point of giving up on Reveal. Anybody have any ideas as to why the modal location is inconsistent each time you click it and why as you go down a list, the modal window's location gets lower and lower until its completely off the page?
I have tried placing the modal code right before the closing  tag but when I do that, no modals fire at all when triggered.

Alright with making a few changes to the way my loop adds the modals, I can now get the modals to display with them just before the closing  tag but the problem if inconsistent and improper modal placement when fired. Sometimes its high - high enough that you can't even see it, sometimes its low, sometimes its on a page or two down below.
Any thoughts on tackling this? Reveal in Foundation has been completely un-modified.

I'm having the same problem. No solution so far has worked. Making it fixed is not an option.

Anyone found a resolution for this? Been a huge issue in my project and haven't figured out a reasonable resolution.

Also having a similar issue, the modal appears but has "top" set at a crazy number, pushing the modal off the bottom of the screen


Update sbt-native-packager to 1.9.15

Updates com.github.sbt:sbt-native-packager from 1.9.11 to 1.9.15.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.sbt", artifactId = "sbt-native-packager" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-native-packager" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #192.


add support for prompt_lookup_num_tokens introduced in the latest transformer update (makes inference 3x faster)

https://github.com/vllm-project/vllm/issues/1802

Closing for https://github.com/vllm-project/vllm/issues/1802


Adding redis version compatibility details to the README

cc @uglide

@chayim - apparently you need to add redis to the wordlist :P

Codecov Report
Patch and project coverage have no change.

Comparison is base (cbdf537) 93.29% compared to head (f54a8fa) 93.29%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   93.29%   93.29%
=======================================
  Files          77       77
  Lines        4576     4576
  Branches      423      423
=======================================
  Hits         4269     4269
  Misses        185      185
  Partials      122      122

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

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

@chayim - apparently you need to add redis to the wordlist :P

I changed it to Redis

These set and forget PRs.. .oh good times :p


1.6.0Dev The year navigation error

If we click the back button in the top year area, the time show wrong.

@Azaret seems to be a bug wxhen u switch to decade or century view then the laft arrow also goes up: http://jsfiddle.net/zcvq0yhh/15/
If you have time to look at it that would be great! Otherwise I will have some time in the weekend!

Fixed in #1722


fix: repo fsck is deprecated

ipfs repo fsck seems to have been deprecated (https://github.com/ipfs/go-ipfs/commit/288a83ce7dcbf4a2498e06e4a95245bbb5e30f45) in the meanwhile so our logic wasn't working.
I changed it so now we manually check if it's a connection refused error. If so, check if there's a config file. If so, remove the api file.
If no config file, then it's a remote api connection, show error to the user.
License: MIT
Signed-off-by: Henrique Dias<EMAIL_ADDRESS>

I'm merging this for now since I'm stumble on this error every now and then and it's annoying. It's also a simple PR. We can change anything on another PR.


Disable scala.color in ReplSuite

I have a ~/.sbt/0.13/colour.sbt file:
initialize ~= (_ => if (ConsoleLogger.formatEnabled) sys.props("scala.color") = "true")

which was interacting with paradise's REPL tests.
With this change the issue is fixed.
Fixes #38

LGTM


fix: Data Resource Group block and update tests (#73)

Ran pre commit after removing resource group data block

Updates for location and default test should be minimum required.

Updates to the unit tests

Ran pre-commit

Update module version for breaking change

pin azapi provider to <1.13

Updates for new linting requirements

Description

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

Already Updated with another PR.


process replay: add Bosch long route and support alternative experiences

This ended up needing more thought than adding a new route, there's issues with controls mismatches, camera malfunction (no wideRoadCameraState, not sure how that worked before), and disable_ecu hanging on the drain_sock function


App crash after implementation 'com.google.ads.mediation:facebook:<IP_ADDRESS>'

Thank you so much for developing this package.
My problem is your package is working fine with Admob. But it crashes when I add "audience-network-sdk:6.3.0".
Crash here
    implementation 'com.google.android.gms:play-services-ads:19.8.0'
    implementation 'com.facebook.android:audience-network-sdk:6.3.0'
    implementation 'com.google.ads.mediation:facebook:<IP_ADDRESS>'

Crash here
    implementation 'com.google.android.gms:play-services-ads:19.8.0'
    implementation 'com.google.ads.mediation:facebook:<IP_ADDRESS>'

Work here
    implementation 'com.google.android.gms:play-services-ads:19.8.0'
    implementation 'com.facebook.android:audience-network-sdk:6.3.0'

It crash if I add "com.google.ads.mediation:facebook:<IP_ADDRESS>" this

It will be good if you can help :)

Hi @ahmadeyamin, what is the native error log for this crash in Android Studio ? Maybe that info will help to find the solution.

Thanks for your response. Could you try to call MobileAds.initialize in your MainActivity, as shown here, to see if it fixes your problem ?
package ...
import ...
import com.google.android.gms.ads.MobileAds;
import com.google.android.gms.ads.initialization.InitializationStatus;
import com.google.android.gms.ads.initialization.OnInitializationCompleteListener;

public class MainActivity extends AppCompatActivity {

    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        MobileAds.initialize(this, new OnInitializationCompleteListener() {
            @Override
            public void onInitializationComplete(InitializationStatus initializationStatus) {
            }
        });
    }
}

Thank You so much
 setContentView(R.layout.activity_main);

It's working after removing this line :)


Starting Ion testsuite and finishing compatibility

@aegis22 I'm mergin his as we can now start splitting work for creating tests


feat: pwa

Feat: PWA
Vuestic-admin now behaves as PWA.

Thanks!
Merging but we need to test PWA is working on staging environment.


Prettier error messages on missing plugins

I like gobblejs. A lot. It's like fly but made for ES5.
One of the features of gobble I like the most is auto-npm-install-ing of gobble plugins, better explained here: https://youtu.be/9NttxOJqb2A?t=851
In other words, if I use gobblejs and want to run a transform through a gobble plugin that is not (yet) installed, I'll get the following:
$ gobble
gobble: could not load uglifyjs plugin. Have you installed it? npm install --save-dev gobble-uglifyjs
install uglifyjs plugin? [y/n]

$ fly default
[10:34:9] default failed due to TypeError: this.source(...).uglify is not a function
$

Gobble is helpful. It tells me what I need to do in order to use the "uglify" plugin, and it will even save me typing npm install. Fly is not as helpful - the error is confusing; at this point (following the tutorials) I haven't been told that Fly relies on plugins, and at this point I don't know how to install them.
Please be like gobble. Pretty-print error messages of (potentially) missing plugins so users can learn they need to npm install --save-dev fly-whatever when something fails.

You are right about that error message. It's not helpful.
We are going through a major rewrite and a lot of this stuff will be improved.
I wouldn't go as far as creating a prompt for that, but I agree the error message needs to be improved dramatically.

There needs to be better error handling throughout Fly. The one you listed is practically the only one.
I'm with Bucaran tho and don't think auto-installing is a good idea, especially since it is and will be impossible to know what NPM package you'd want when more than one plugin shares the same method name.
For example, would .uglify be "fly-uglify" or "fly-uglifyjs"?
Similarly, and I recently ran into this, "fly-nunjucks" was already registered on NPM and seemingly abandoned. I also wanted to use a compiler sequence different than what was used, so I had to do "fly-nunjucks-render."
They are completely different plugins and both expose .nunjucks .. and I imagine there will only be more instances of that as time goes on

Yeah, I've had that problem with Gobble - similar plugins like gobble-less and gobble-less-all are not nice.
I wonder if a monorepo for plugins, like babel does, would be a better approach to this problem. At least the fly maintainers could remove abandoned plugins and/or replace them with ""official"" forks.

I don't really believe it to be a problem tho. Like 99% of all other NPM use-cases, I feel one should actually look at the Readme before downloading something they what may or may not end up wanting.
Without getting too far off track, this issue is about improving errors and Bucaran and I both agree on that point.

Mostly added in 2.0 (#218)
Fly will now notify where there is a name conflict. In that event, the secondary copy will be renamed & mounted with that new name. Eg, if two plugins want to use the name babel, the second one will be renamed to babel1:
'babel' was renamed to 'babel1' because its name was taken`

Closing for now. Any new plugin-related behavior suggestions should be opened as a new issue.
Thx!


Crash on iOS 14 When Initializing SiweMessage Instance

Description
The SIWE (Sign-In with Ethereum) library encounters a crash immediately upon initialization when running on iOS 14. This seems to be related to a syntax error in parser.js.
Steps to Reproduce

Initialize a SiweMessage instance on an iOS 14 device.
Observe that the app crashes immediately after load.

Expected Behavior
The SiweMessage instance should load without causing the app to crash.
Actual Behavior
The app crashes and the following error is displayed in the console:
(Unhandled Promise Rejection: Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
Possible Solution
N/A
Additional Information

This issue occurs consistently on iOS 14.
No such issues have been observed on later versions of iOS or on other platforms.

Environment

Device: iphone 8 plus
OS: iOS 14
Browser: safari
SIWE Library Version: ^2.1.4

Screenshots

Acknowledgements
I would like to express my gratitude to the development team for creating the SIWE library. Your work significantly contributes to the ecosystem, and I appreciate the effort put into making such tools available and maintained.

@osmanthustonx I'm running into the same issue! Did you manage to figure out what it was?

@chrismin no idea🥲

Same

Hello team?

Any news, workarounds or updates on this topic?
I recently encountered the same issue.
UA:
iOS Version: 14.6
iPhone
Mobile Safari 14.1.1

Having the same issue with Android


Godot 3 shader compiler bug

Godot version:
3.0.4 (and 3.0.2)
OS/device including version:
GLX version: 1.4
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.4
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 11.0.4
OpenGL shading language version string: 1.30
Issue description:
It translates the shader program so that CanvasShaderGLES3 fails. This is the shader code:
shader_type canvas_item;

void fragment()
{
	float fr = sin(0.5)*273758.5453123;
}

But it fails with this error message:

drivers/gles3/shader_gles3.cpp:168 - CanvasShaderGLES3: Fragment Program Compilation Failed:
0:248(30): error: syntax error, unexpected NEW_IDENTIFIER, expecting ')' or ','

the generated code is:
247: 	{
248: 		float m_fr=(sin(0.5f)*273759f);
249: 	}

I think the problem is related to<PHONE_NUMBER>123, my current workaround is to rewrite that number as 273758.0 + 0.5453123
Steps to reproduce:
Put an element in the scene and attach it this shader code:
shader_type canvas_item;

void fragment()
{
	float fr = sin(0.5)*273758.5453123;
}

I've encountered this bug before, for some reason floats with many decimal figures get rounded when generating GLSL code (String::num_scientific is used). I only get this bug when using my laptop, can't reproduce it on my main PC.
It might have some relation with the fact that float constants are parsed and stored as doubles and later on converted to float.
I haven't come up with a solution to this other than changing
snprintf(buf, 256, "%lg", p_num); to snprintf(buf, 256, "%.16lg", p_num); here, but I guess the #defined is there for a reason.

Same error caused by the loading of a GDNativescript library.
Got the issue on a Linux laptop (Intel GPU), didn't tested with Linux on my main PC yet but it works on Windows.
Code generated :
{
    color_interp.rgb=mix(pow(((color_interp.rgb+vec3(0,055))*(1.0f/(1.0f+0,055f))), vec3(2,4)), (color_interp.rgb*(1.0f/12,92f)), lessThan(color_interp.rgb, vec3(0,04045)));
    uv_interp=((uv_interp*m_uv1_scale.xy)+m_uv1_offset.xy);
}

It also caused the line numbers in the script editor to be displayed like this:
1,000000
2,000000
3,000000

Happens with Godot 3.0.6 stable
Probably an issue with localized floats separators (the FR local specifies to use a , instead of a .)


Revamp the way we publish and deploy Lambdas

What is this PR trying to achieve?
This is a complete rethink of the way we deploy Lambdas. Rather than installing files locally, we:

Have Travis build a ZIP “deployment package” inside a Docker container
Upload the ZIP to S3 (but only if there are changes against the current version, and in non-test code)
Use that S3 object when deploying the Lambda

Resolves #971.
Still to do is adding the Travis config, but that’s blocked on a merge of #987.
Who is this change for?
Devs who want neater deployment procedures.
Also, me when I come to pull apart the Lambdas stack.
Have the following been considered/are they needed?

[ ] Deployed new versions
[x] Run terraform apply.

Mmm. This appears to be missing some code – in particular, my hand-rolled ZIP comparison code, which should be replaced with a call to zipcmp.

Merging with approval from @kenoir in Slack.


Feature: Add support for .NET 8

Version 7 will be maintained for external package upgrades and urgent bug fixes via a separate branch.

Closed by #28


tour: [each number must have two square roots in complex numbers ]

Context: https://tour.golang.org/flowcontrol/5
Hello!
In the given exercise, you show only one complex square root of a number.
according to the Fundamental theorem of algebra, there always must be always two of them.
My proposal is to modify the return block minorly, like this:
return fmt.Sprint(math.Sqrt(x)) + " " + fmt.Sprint(-math.Sqrt(x))

Hi, an thanks for the report.
It's done that way to mimic the behaviour of cmplx.Sqrt, which only returns the principal value. This is typical for functions that manipulate complex numbers in programming languages (csqrt, from C, does the same).
I don't think doing otherwise would buy us anything: people that does not know how complex numbers work will be confused by the double return, and the ones who know will understand that we are returning the principal value. Again, this is extremely common in programming languages implementations of complex sqrt.
Closing here, since I believe the example should stay as it is.


[zh] sync certificate-signing-requests.md

Sync with en text:
content/zh-cn/docs/reference/access-authn-authz/certificate-signing-requests.md

See preview please.

/approve

/lgtm


Resource landing page UI - suggestions

I will be addressing recent suggestions made by Dave and Jeff on the modifications I've made to the resource landing page. This changes are running in the sandbox at http://sandbox.hydroshare.org/
Dave's:

[x] {This will be done via the download button}It should be possible to download the file itself by clicking on it, in addition to download all
[x] The Sharing information seems to belong near the Rights information.  I suggest bringing the statement about Sharing to after rights, before Keywords.  I think that sharing information from System Metadata and sharing status can be combined.  Sharing Status: Public seems the same as This resource can be viewed and downloaded by anyone.  I suggest that they be combined to something like:
Sharing Status: Public (This resource can be viewed and downloaded by anyone)
[x] I think that the blocks for creators and contributors take up too much space.  Could we have one line for each person, e.g.
Jeff Horsburgh, Utah State University, 8200 Old Main Hill, Logan UT 84322-8200, Phone:<PHONE_NUMBER>, Web: http://jeffh.usu.edu
[x] There is not much information in the temporal tab.  Could this be combined with other date information on System Metadata to have one place that has all date information together
[x] For my taste the line spacing in the abstract could be a bit smaller.
[x] The share and delete icons top right should not be visible when I am not logged in with credentials to use these
[x] The URL in the Citation should be a hyperlink
[x] Citation should read "How to cite"

Jeff's:

[x]  Let's keep the headings consistent.  Add an "Abstract" heading that is the same style as  as "Keywords" and "Content".
[x]  Change "Citation" to "How to Cite" as dave suggests and make it a heading that is consistent with "Abstract", "Keywords", "Content", etc.
[X] Move the "Sharing" heading up and consolidate with the rights information as Dave suggests.  Make the rights information the same font size as the rest of the content.
[x]  When I make the page narrow in my browser, the "System Metadata" tab wraps to the next line.  I think you should set is so the tabs never wrap.
[x]  {Taken care of in another issue}I get an error when I click the delete file button.  I wanted to delete the existing file and upload the same file, but with a different file name, but I wasn't able to do it because the delete button is broken. Eventually, we may want to consider a "Rename File" option, but not for this round.
[x]  The Share, Edit, and Delete icons for the resource (at the top of the page) and the download and delete icons (on the file) are too small.  They need to be larger and/or somehow more pronounced so they are easier to find.  Dave suggested having the file download when you click on it, but I prefer the download button so that you know for sure what is going to happen when you click on it.
[x] Hide tabs if they are empty
[x] Add Creative Common badges to 'Rights'
[x] Restyle 'Manage Access' panel
[x] Check if authors/contributors are HydroShare users and display as link
[x] Authors and contributors should be links to user's HydroShare profile when applicable.

I have reviewed these changes in sandbox.hydroshare.org and am happy to approve the layout.  @horsburgh can close when he approves.  However see #209.

@horsburgh is this ready to close


Develop a network system

Unable to take the items in the GUI

I think I could fix it myself... I think there's something that is related to container that's not implemented.

yeah we need some work on network...

I think we should fix it as soon as possible

I think it might be somewhat fixed by the commit above...

still not

Um, we might need a rewrite.

Or register TileEntity?

....... still not = =

You might try first. I am not free recently.

Only you are talking.Where are the others?

Haha @Java0 @JAVA10086 They do not work. They've just registered a github account and wait happily.

你们够了，说中文OK？

@Couther You need to contribute some day...

Um, this is International website, so we should use english

Develop a better network system

@liach Do you know how to cast Object to byte[] ?

http://stackoverflow.com/questions/10730929/cast-an-object-to-bytearray

if use ObjectOutputStream, the Object must implement Serializable

现在没问题了吧


pre-commit: use exclusion instead of ever-growing regex

Thanks! Sorry for taking so long to get to this

No problem!


As a data editor, I want to enter months for periodical publication dates and non-numeric volumes when entering multivolume and periodical details.

convert issue number from numeric field to string to accommodate content like "19-20"
(maybe) convert year to partial date field to accommodate months when known

@jkotin @clmahoney please comment with any other changes you're aware of now based on Cate's testing.
I propose converting the year field to a partial date: this would accommodate the months Cate found for one journal and would also be used for sorting.

@jkotin I've done a test implementation of the volumes/issues list based on Gissoo's design for the bibliography page to make sure I can generate the display and to check on the data model changes for Edition records.
Here are the changes I propose:

convert issue number from numeric to string so we can handle non-numeric issues like "19-20"
add help text to season to indicate it should include season or month spelled out if it should be included in the issue citation (wording suggestions appreciated)
convert year to a partial date field so that it can include month (and even day) when a more specific date is known; only the year will be shown when the issues/volumes are listed, but month/day will be used for sorting

Question:

Will volume always be numeric?

Please review these proposed changes and confirm your agreement or let me know any adjustments so that we can proceed with implementing them.

@rlskoeser This all sounds good. I'm tagging @clmahoney so she can confirm -- she's done the most work on the volumes/issues. For help text for season, how about "Spell out month or season if part of numbering"?  That's not very elegant.  I'm happy for alternatives.

@clmahoney please review and let me know if these changes sound like what we need based on the volume/issue data work you've done.
One thing that occurred to me: entering month in both the partial date and as text in the "season" field is redundant, and we have an existing template tag that will let me easily display month and year if month is known, or just year if month is not known. The one problem with that is if we need more control over the display: will you ever know the month but not want it displayed? (e.g. if there is also a season)

@rlskoeser yes, volume is always numeric.
Re: season v. month. Usually it's one or the other; rarely both. I think it would be most helpful to see the month, since that can narrow down the most quickly.

YES, I can add non-numeric values. Tried with that two issue span and it works! See note:

YES, I see the season field help text:

YES, partial dates work too! I tried year only and only month and date:
.

Looks great!


Restore "xunit ->" message when running tests

This got lost on the xplat branch, but it's nice to have.
cc @AndyGerlicher--pretty sure we talked about this bugging us.

Nice! That had been bugging me.


To use akamai_group, you need to specify contract.

The content created by create-property will not work.
akamai terraform create-property xxxxxxxx

cat property.tf

data "akamai_group" "group" {
 name = "XXXXXXX"
}

terraform plan

Error: looking up group with name: "XXXXX": 'contractId' is required for non-default name: XXXXX
│
│   with data.akamai_group.group,
│   on property.tf line 11, in data "akamai_group" "group":
│   11: data "akamai_group" "group" {

Specifying contract works well.
vim property.tf

data "akamai_group" "group" {
 name = "XXXXX"
 contract = "ctr_XXXXX"
}

Thank you.
I'll check if it's fixed in 0.2.0 and close it.

It was updated and improved.


Fixing deprecated preg_replace usage in classmap_generator.php

With php >= 5.5, the /e parameter in preg_replace is deprecated and gives the warning:
Creating class file map for library in '<path>'...
PHP Deprecated:  preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in <path>/zf2/bin/classmap_generator.php on line 231

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in <path>/zf2/bin/classmap_generator.php on line 231
Wrote classmap file to '<path>/autoload_classmap.php'

As suggested, this PR changes the preg_replace to preg_replace_callback.

Thanks @samsonasik! Fixed.

Merged, thanks @Lansoweb!
master: zendframework/zf2@4513cc4b754cd6535ce9a216dcaacf7170738746
develop: zendframework/zf2@99e0bc074cafe3efee2644160cbf128a6264b25f

@Ocramius My pleasure. Can close bug https://github.com/zendframework/zf2/issues/7134 too.


Why not use event callbacks?

Its an interesting choice how drivers work in Cycle. I'm curious why you didn't stick with the whole "callback" style of registering events. This would make it easier to build drivers and to integrate with other libraries.
I think this example maintains the spirit of Cycle, but allows you to use React (and React Native) and entirely deals away with the the issue of isolation (isolateSink and isolateSource).
import {stream, scan} from 'flyd'
import lift from 'flyd/module/lift'
import h from 'react-hypersrcipt'

const counter = (props$) => {
  const action$ = stream()
  const state$ = scan(add, 0, action$)
  const inc = () => action$(+1)
  const dec = () => action$(-1)
  const view = (props, state) => {
    return h('div', props, [
      h('button', {onClick: dec}, '-'),
      h('span', state),
      h('button', {onClick: inc}, '+')
    ])
  }
  return {
    html$: list(view, props$, state$),
    count$: state$
  }
}

The way the current DOM driver works (binding actions before creating the DOM), makes me think that they're may be certain dynamic interfaces that couldnt be created.
Anyways, I'm curious about your thoughs on this decision.

@ccorcos Hello, thanks for your interest in Cycle.js
This was a very conscious decision that was made, as it separates your view logic from your event logic. We believe this to be a better pattern an easier to reason about. Introducing event handlers in your markup is a strict coupling between the two. Avoiding strict coupling is something we generally try to avoid.

This would make it easier to build drivers and to integrate with other libraries.

I'm not sure why you believe drivers to be difficult to create, or why you believe it's difficult to integrate with existing libraries? We are a young project with a small community, simply many integrations have not happened yet.

The way the current DOM driver works (binding actions before creating the DOM)

The first part is not quite true. The DOM driver uses event delegation. It attaches event listeners to the root element supplied to makeDOMDriver('#rootElement') and uses filters and other techniques to properly match the events to the right places, and are connected before updating the view.
The order in which we write it because of this seems to be very fluid (to me). User events -> model -> view. Or in other words,"What does my application/component allow the user do?" -> "How does that affect the state of my application?" -> "How do I represent my new state on the screen for the user?"

makes me think that they're may be certain dynamic interfaces that couldnt be created.

I'm curious what interfaces you refer to here? We're always looking for ways to improve.

Why not use event callbacks?

Very simple to answer: because user events are read effects, and they should come through sources, not in the form of callbacks on sinks (meant only for write effects). This is super important for maintaining dataflow properties in Cycle.js.

I think this example maintains the spirit of Cycle, but allows you to use React (and React Native) and entirely deals away with the the issue of isolation (isolateSink and isolateSource).

We are able to use React (Native) already in Cycle.js, because we postpone attaching event callbacks. See https://github.com/cyclejs/cycle-react-native as an example.
The snippet your wrote looks a lot like Yolk.js: https://github.com/yolkjs/yolk. Check it out if you prefer that approach. When it comes to Cycle.js, we're pretty sure we want user events separate from view.
Thanks for the conversation.

why you believe it's difficult to integrate with existing libraries?

I just don't understand how to you connect drivers.DOM.select('input').events('click') to the input thats eventually returned to the DOM driver. It seems pretty challenging or littered with mutations. Take React for example -- how does the event handler get injected into the vdom before its rendered?

I'm curious what interfaces you refer to here?

 So you represent an entire application with a static data structure, and you compute the application ui using that data structure.
So suppose a user drags a div into the app workspace and then wants to add a "click" event to to trigger something else. With cycle.js it doesnt seem like you can dynamically add or remove event listeners like that. In order for this to work, every div in my app-builder app would need to bind any event handlers that user may want to use. Was that too contrived or does that make sense?

The snippet your wrote looks a lot like Yolk.js

Interesting, you're right. I've never seen that. I'm really just trying to get a good understanding of Cycle.js vs Elm Architecture. Elm makes it trivial to build a time-traveling debugger but its has come performance concerns. Cycle.js looks like it has great performance, but doesnt offer quite as much introspection into your running program since the state is littered throughout in isolated places using stream.scan. Would you say thats a reasonable assessment?

I just don't understand how to you connect drivers.DOM.select('input').events('click') to the input thats eventually returned to the DOM driver. It seems pretty challenging or littered with mutations. Take React for example -- how does the event handler get injected into the vdom before its rendered?

I'm not a Cycle expert but I wanted to make clear that even React does not actually “inject handlers into vdom”. It is usually bad for performance to attach many event handlers, so under the hood React just registers component handlers in a map by the internal component ID, and only sets up a single event handler at the root of React hierarchy. This is similar to the event delegation approach that has long been used in Backbone and jQuery. I think in some cases React might actually subscribe to the node in question (depends on the event and browser quirks) but more often I think (it's best if you verify!) it subscribes to the root node.

Interesting. So you're saying, in concept, that React might just register a 'click' handler on the body, and then as an even bubbles up, it will interpret the event and dispatch a synthetic event for some div or button on the page?

Yeah, I think this is pretty much what React does. In addition it normalized synthetic bubbling behavior across browsers to match the spec.

Nowadays Cycle DOM also does event delegation.

Would love a cycle api that works something like the following:
dom.registerEventHandlers({
dec() {
}
inc() {
}
})
and you can return dom like this:
+
registerEventHandlers is basically sugar over the existing setup. Instead of doing select('.className').on('eventName').call(eventHandler), registerEventHandlers would search the dom for event handler name attributes, and then register the specified function name for the specified event.
This frees up the className attribute to be used just for css, and draws a much more explicit connection between the view to event handlers.

So this will silently "fail":
    a(".link", {
      props: {
        href: "/signup",
      },
      on: {
        click: () => alert(data),
      },
    }, "Click me!")

Right?
I was confused when tried to make it work :)

@bloadvenro The event listener callback module is not used by default. You can pass an array of snabbdom modules to the DOM driver
But why would you actually want to use this? It wont work with the rest of the DOM driver.

@jvanbruegge Thank you)
I actually didn't know how to do it right. I started working with CycleJS only recently.

@jvanbruegge

But why would you actually want to use this? It wont work with the rest of the DOM driver.

I tried to implement input normalization inside view function. The piece of code above is just a quick test.


[Getting Started] Updating TFM for .NET 5

https://github.com/dotnet/designs/blob/master/accepted/2020/net5/net5.md#design
I've only updated this documentation for consuming the package.
It still appears that the projects in the repo need to be updated as #189 but that's a separate concern from this documentation.

I'm using VS 16.7.0 Preview 1.0 and the 5.0.100-preview.4.20258.7 SDK.
I haven't updated my non-Preview VS in a while...

So both TargetFramework net5.0 and netcoreapp5.0 work fine in VS 16.6. However, -f net5.0 doesn't work with dotnet new. Lets hold off on updating the docs until dotnet new is fixed in the next preview.


Hyperlink also names, not only arrows, on Open > GitHub

Click Open > GitHub. I see
▼積丹尼 Dan Jacobson
▶circe
▶mymaps
OK good. But I can only click the arrows above.
The names should be also part of the same hyperlink.
The result is I must aim the mouse with a steady hand to click the arrows.

No longer relevant after UI refresh


cloud-init bond interface

Is there a way to setup a bond interface with cloud-init?
I know how to do it on for example CoreOS, but because the way you specify network settings is different in Rancher OS, it isn't clear on how to accomplish this if even possible.

To clarify, on CoreOS you would do something like this:
- name: dhcp.network
  content: |
    [Match]
    Name=bond0

    [Network]
    DHCP=true
- name: m1.network
  content: |
    [Match]
    Name=eth0

    [Network]
    Bond=bond0
- name: m2.network
  content: |
    [Match]
    Name=eth1

    [Network]
    Bond=bond0
- name: b1.netdev
  content: |
    [NetDev]
    Name=bond0
    Kind=bond

I'm also looking to do something similar if possible

+1

Just like to say this is a feature we'd like to make use of to give us network redundancy on our physical hosts. Be good to know if this is just a case of using the right config or if it requires a feature coding.

I think this functionality should be supported with our recent networking changes (http://docs.rancher.com/os/configuration/networking/).

This is totally possible In RancherOS. For example:
#cloud-config
rancher:
  network:
    interfaces:
      bond0:
        addresses:
        - <IP_ADDRESS>/31
        - <IP_ADDRESS>/31
        gateway: <IP_ADDRESS>
        bond_opts:
          downdelay: "200"
          lacp_rate: "1"
          miimon: "100"
          mode: "4"
          updelay: "200"
          xmit_hash_policy: layer3+4
        post_up:
        - ip route add <IP_ADDRESS>/8 via <IP_ADDRESS>
      mac=0c:c4:d7:b2:14:d2:
        bond: bond0
      mac=0c:c4:d7:b2:14:d3:
        bond: bond0

rancher/rancher.github.io#343

This will be released in the docs when v0.5.0 is released


[move-prover] Assumed/Asserted aborts and error codes.

This PR adds new features around aborts specification, as outlined in the design doc:

aborts_if P with code allows to specify an error code for this aborts condition. If P is true and the function aborts, it must abort with code otherwise a special verification error is produced. The error message contains detail information about expected and provided error code.  For examples, see here.
aborts_with code1, ..., codeN allows to specify an aborts code without any condition.
aborts_if [assert] P and aborts_if [assume] P allows to specify that the error condition should either become a precondition which needs to be verified to not happen, or an assumption. For examples, see here.

Together with this PR comes a refactoring in spec_translator.rs on how conditions are translated for the different entry points of a function. The new approach uses a more systematic and declarative way how to do this which is easier to understand and modify using the new ConditionDistribution data type.
Closes #5266
Closes #4906
Motivation
More scalable treatment of aborts.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
New tests.
Related PRs
NA

This PR has been updated to implement the semantics as discussed yesterday w/ @shazqadeer , @emmazzz , and @DavidLDill. Moreover, the aborts_with codes clause has been added as suggested by @sblackshear .

@bors-libra r=emmazzz

:pushpin: Commit 16889e6 has been approved by emmazzz

:hourglass: Testing commit 16889e633f39fc738a1c7801b7debb5d8806d5ea with merge 2169e9b2c7fb15c07b30b51713945d03a1103a34...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: emmazzz
Pushing 2169e9b2c7fb15c07b30b51713945d03a1103a34 to master...


Allow jobconfig to be dynamically configured by Service labels

While the concept that everyone creates ServiceMonitors to get their endpoints scraped is great, it would also be nice to have a small amount of ServiceMonitors, with more flexibility.
We'd like to have labels on the k8s Service actually be used to determine the metrics_path and port(name). This would allow a minimal of ServiceMonitors with only a small amount of configuration being static.
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: generic-servicemonitor
  labels:
    prometheus: k8s
    k8s-app: bolcom-app
spec:
  endpoints:
  - interval: 30s
    pathFromLabel: metrics-path
    targetPortFromLabel: metrics-port
  namespaceSelector:
    any: true

Where a service would provide metrics-path and metrics-port labels
apiVersion: v1
kind: Service
metadata:
  labels:
    metrics-path: /metrics
    metrics-port: 8080
  name: myapp
spec:
  ports:
  - name: http
    port: 8080
  selector:
    application: myapp

This seems reasonable to me, happy to accept a PR for this, only nit would be that I'd prefer pathLabel and targetPortLabel. Also we would need to document the behavior that we expect and/or whether these would work mutually exclusive to the existing selection mechanism.

I have a draft of this working. Will test it a bit and open a PR for this tomorrow if it works out.

Would annotations be more appropriate than labels for these?

The imeplementation I chose leaves this up to the user :) I can imagine scenarios where people would want either.

We recently released a new feature that enables users to do the same thing as you envisioned here. ServiceMonitors can now be selected across namespaces using the serviceMonitorNamespaceSelector, meaning that teams can define their ServiceMonitor including port, labeling, etc in their own namespace, while the Prometheus server itself can be managed in another namespace by an infrastructure team. Let us know if that solves your problem @wleese !

@brancz perfect!


GH-1108: @QueueBinding.key recursive resolution

Fixes https://github.com/spring-projects/spring-amqp/issues/1108
@RabbitListener.queues() resolves String[] recursively.
AMQP-722 added support for multiple routing keys to @queueBinding but
did not add support for recursive resolution. This is required to support
constructs like key = "#{'${my-app.amqp.routing-key}'.split(',')}".
cherry-pick to 2.1.x

... and back-ported into 2.1.x as https://github.com/spring-projects/spring-amqp/commit/53c9150b718eeae0a2f084ff302631a6e605deaa after fixing conflicts in tests.


AuthenticateWithClaims doesn't respect UnmarshalJSON implementers

In sessions.AuthenticateWithClaims you use mapstructure to decode the custom claims into the object.
The call you are using doesn't respect a type implementing the json.Unmarshaler interface. Ideally you would use the standard json library for this, but I understand that it's difficult to implement (may need to unmarshal twice or something). The alternative is to add a DecodeHook to your mapstructure config which handles types which implement json.Unmarshaler

Hey! This is a great suggestion. I'm wondering if something simple like this would hypothetically work:
if unmarshaler, ok := claims.(json.Unmarshaler); ok {
    // use unmarshaler to decode the custom claims
} else {
    // existing unmarshal logic using mapstructure
}

You don't have the JSON bytes available, just map[string]any.. If you can get the JSON bytes then you should just be using the json package!


huh?

if you said smth in the discord i quitted discord

this'd go to Nekos-API/Nekos.Land and nekos.land will be up at land.nekosapi.com from now on.


add a note for multi-gpu training of endoscopic inbody classification…

… bundle.
Signed-off-by: binliu<EMAIL_ADDRESS>Fixes # .
Description
Add a description for endoscopic inbody classification bundle for multi-gpu training.
Status
Ready/Work in progress/Hold
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/build


handle exceptions with rich's logging handler

Type of changes

[ ] Bug fix
[x] New feature
[x] Documentation / docstrings
[x] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
Handling exceptions with rich's logging handler #298

Well this is strange, test_track_thread of test_progress.py  failing on macos. I don't think I touched it...

There is a test involving a thread that fails randomly. Need to look at that. Rerunning tests tends to fix it

The exc_value of the traceback does not get printed.

I tried to find out why and I think it disappears in the print function, at this point:
https://github.com/willmcgugan/rich/blob/a16a234c2906665279f5fc01fd138ff42e4c7dbb/rich/console.py#L958-L959
Thou I don't know why...

@taliraj That is strange. Any change you can print traceback.stacks. If you see the exc_value there then something must have gone wrong in rendering.

@taliraj That is strange. Any change you can print traceback.stacks. If you see the exc_value there then something must have gone wrong in rendering.

@willmcgugan  I added a print(traceback.trace.stacks), this is the result:

Indeed the exc_value is there.

Still not sure what is happening to that exc_value, but it does look to be on the render side. I'll merge this and fix. Thanks!


Remove unused opam file

Unused since 9906bfeb5fbd395db1acec40f4e6d3d99ca0ab9e

Thanks, your patch was integrated upstream :+1:.

Thanks a lot! I also noticed that miouu is still mentioned in the README

Yes, I'm currently update step by step tutorials and documentations, I take a big time 😅 .


Acknowledge contributors

[ ] Update link to Zenodo DOI (newer version available)
[ ] Include sentence on how to cite
[ ] Add contributors as described by the all-contributors emoji key

Thank you @miykael! I hadn't read that about the most recent version! Perfect.
And thank you for updating your affiliation! #35 is merged 💯


pkg builds some projects by default that it didn't used to

This Bug Report affects these Traffic Control components:
None/all, depending on your point of view. This bug only affects pkg.
Current behavior:
The pkg script, when given no arguments, will build every project listed by -l.
Expected behavior:
Previously, the default build list was not the same as the output of -l, which just listed all projects that could be built. In particular, docs, weasel, and grovetccfg_build used to be skipped when building without listing specific projects. weasel takes a while, so this does represent a significant increase in build time.
However, this behavior does seem more consistent. I may even like it better than the old behavior, but for convenience I'd want to at least be able to explicitly exclude projects from the build, because I almost never want to build docs, source, grove (both regular grove and grovetccfg), or weasel.
So in conclusion, I'm not sure we want to consider this a regression bug or an intended feature change, but the bottom line is that things that used to not happen are now happening, so that's why it's labeled like this. Feel free to change it.
Steps to reproduce:
Run ./pkg from the repo root, notice what it builds.

"low impact" is a guess, since this needs more information.


Custom easing

Is there a way to set a custom easing of the slides (especially when using parallax) through the options?

You can specify it via transition-timing-function css property


Don't use a shell array where not needed

Builds are failing with unbound variable at this line.    Doesn't need to be an array and isn't used safely as one.

@saad-ali this isn't the same thing you were chasing is it?

LGTM, and yes, it looks like  this be the same issue. I saw the following in the logs:
  Waiting for apiserver to be up
  /jenkins-master-data/jobs/kubernetes-soak-weekly-deploy/workspace/kubernetes/hack/e2e-suite/services.sh: line 90: results: unbound variable
  error: couldn't read version from server: Get https://<IP_ADDRESS>/version: dial tcp <IP_ADDRESS>:443: connection refused

If so, this should close #10127

I don't know why it suddenly started firing...
On Mon, Jul 13, 2015 at 5:26 PM, Saad Ali<EMAIL_ADDRESS>wrote:

LGTM, and yes, it looks like this be the same issue. I saw the following
in the logs:
Waiting for apiserver to be up
/jenkins-master-data/jobs/kubernetes-soak-weekly-deploy/workspace/kubernetes/hack/e2e-suite/services.sh: line 90: results: unbound variable
error: couldn't read version from server: Get https://<IP_ADDRESS>/version: dial tcp <IP_ADDRESS>:443: connection refused
If so, this should close #10127
https://github.com/GoogleCloudPlatform/kubernetes/issues/10127
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11198#issuecomment-121097963
.

Jenkins passed - merging


Tiny Snake not running on fresh delivered device.

I got my delivery and wanted to test out the play shield. After loading the files of the repository https://github.com/tinypico/tinypico-micropython/tree/master/play shield examples/tiny-snake I get this error:
File "ssd1306.py", line 109, in write_data
AttributeError: 'I2C' object has no attribute 'writevto'
MicroPython v1.10-231-g673db939b-dirty on 2019-03-31; ESP32 module with ESP32

Workaround:
I manged to get it to work by replacing the lines 108,109 of the ssd1306.py file with its previous content from Commit cf9a2b58275134654843b9b81cc9154185a043ba :
def write_data(self, buf):
        self.temp[0] = self.addr << 1
        self.temp[1] = 0x40
        self.i2c.start()
        self.i2c.write(self.temp)
        self.i2c.write(buf)
        self.i2c.stop()

I am new to micropython and its usage but it seems to me that this latest version is assuming a newer or different  'core/kernel' (or whatever the pre installed image is called ) version.

Closing this because the workaround is good enough to get my hardware tests done. Only wrote this issue to document for others 😉 .

Hi @RobertK66
You are correct, I accidentally had a newer ssd1306 library included :(
I've replaced it with the correct library now, so no workarounds are required.
Thanks for letting me know
Seon.

I'm still getting failures on this even after the revert:
Traceback (most recent call last):
  File "main.py", line 298, in <module>
  File "ssd1306.py", line 99, in __init__
  File "ssd1306.py", line 36, in __init__
  File "ssd1306.py", line 61, in init_display
  File "ssd1306.py", line 104, in write_cmd
OSError: [Errno 110] ETIMEDOUT

@noderat FWIW, the current head of git works for me although I'm on 1.11 now.
Can you check what devices you can see on the bus? Just to make sure it's not a connection issue.
from machine import I2C
i2c = I2C(scl=Pin(22), sda=Pin(21))
i2c.scan()

@noderat - That doesn't look good. As @konimaru suggests, can you do a scan to make sure the screen can be found? It should find the OLED and IMU on the I2C bus.
 The latest 1.11 is pretty stable, so if the I2C scan sees the screen and the IMU, maybe look at flashing your TinyPICO with the latest MP?

I upgraded to 1.11 shortly after receiving my kit, but it doesn't look like it's picking up the display:
MicroPython v1.11-187-g00e7fe8ab on 2019-08-01; ESP32 module with ESP32
Type "help()" for more information.
>>> from machine import I2C, Pin
>>> i2c = I2C(scl=Pin(22), sda=Pin(21))
>>> i2c.scan()
[]

@noderat: does pressing RESET on the game shield have any effect on the TinyPICO (when plugged in)?

@noderat Are you on the Unexpected Maker discord server?
https://discord.gg/wkT3pd2
If not, join and PM me please so we can discuss next steps.


[HOLD App#22901] Fix/address page state navigation

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/23725
PROPOSAL: https://github.com/Expensify/App/issues/23725#issuecomment-1656792082
Tests

Go to Settings > Profile > Personal details > Home address > State
Click back button of device
Notice it Properly navigates to Home address screen

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/65986357/b4deae99-c426-444f-94b5-45602eb87847

Mobile Web - Chrome
https://github.com/Expensify/App/assets/65986357/383ec463-d4a5-4827-8454-5b3934c52e4f

Mobile Web - Safari
https://github.com/Expensify/App/assets/65986357/c7aa615d-13cb-4a35-b195-741d3556f6ba

Desktop
https://github.com/Expensify/App/assets/65986357/93c9e5de-a097-4358-a6f5-a6b91d3ab71c

iOS
https://github.com/Expensify/App/assets/65986357/b54f8816-59eb-492a-950e-d6cf99565032

Android
https://github.com/Expensify/App/assets/65986357/55b3fcc3-5cae-4292-84b9-023dae47e1db

@parasharrajat I have made the changes. Will soon add the screenshots and complete the checklist.
I'd like to hightlight 2 minor issues:

As you can see wherever StateSelector is used, i have added the code to fetch state  from params and then pass it to StateSelector. Do you think this is redundant and something could be done inside StateSelector?
Regarding CountryPicker (not related to StatePicker/ this PR), I see behavior (attached below) where after modifying state value, there's form error on validation when you change country. This issue was slighlty diferent before the first PR. I couldn't figure what was the difference. I am leaning towards labelling it unintentional. Do you think this needs fixing? Also, if you just touch the input and change the country, the error was there before the change as well as after it. The first part of video shows behaviour on country-selector branch and the second part on the main branch (main branch before country picker update)

https://github.com/Expensify/App/assets/65986357/79885e06-544b-4981-8f4e-8ee768aaa644

Are you saying that after changing the country the state picker that was filled shows an error? I think this is because the form input remains dirty even after we clear it on the setting country. We should reset its state when changed programmatically.

Yes. Because the state field has been touched, the error ("this field is required") is shown after you change the country and set state to empty string

@parasharrajat, I'm not sure. Upon reviewing the files, it seems that the change is a replacement for the Picker component, and not CountryPicker or StatePicker. While more general components could be advantageous, it might stray a bit from the scope of this task; however, I trust your judgment on what's best.

@parasharrajat CountryPicker and StatePicker are very similar indeed. I suppose, if whole components can't be repalced with a single component, a good chuck of their code can be. Some differences that i initially see which might be not very straightforwrad to tackle include these in CountrySelectionPage and StateSelectionPage

bump @parasharrajat

@parasharrajat Updated. I've also removed StateSelector logic of getting param from URL in various files and also fixed autocomplete bug for state if you want to test

@parasharrajat Done

@parasharrajat Merged and updated

@parasharrajat Done

@mountiny Okay. I think the CountryPicker and StatePicker issues are months old and waiting more will result in further merge conflicts. The code snippet in question is optional and wont cause any issues even when #22901 is done. If you want to remove it anyway due to redundancy, I'd be gald to open a new PR after #22901 is done without any payment. However, if this feels cumbersome and non-standard, I don't mind waiting. Whatever you feel is the best!

We are pushing ahead with the refactor quite fast, so it should be done next week and this could just add more issues for the Callstack people working on the refactor with deadline
cc @gedu @Swor71 @MrMuzyk for review later

@parasharrajat I merged fix/address-page-state-navigation into main and then merged main back into fix/address-page-state-navigation. But as you see Github shows a lot of commits. You think i need to create a new PR or can this be fixed somehow?

Yep, it is here

Lets close this in favour of https://github.com/Expensify/App/pull/36770 then thank you


Float Divide by zero issue in util.py

codes\utils\util.py
Got this while creating an LMDB, line 314 in util.py division by zero error. Pretty sure its because it runs that line immediately and obviously 0 time has passed.
fps = self.completed / elapsed
I "fixed" it by changing it to
fps = self.completed / (elapsed + 0.01)
I'm not sure what the appropriate etiquette is here but I'm sure someone that knows better than me can write a more elegant fix.  But it works. Its just for the progress bar while creating the database so its really not a big deal.

Thanks for your suggestion.
We will upgrade MMSR to MMEditing (in the same repo), which consists of SR, inpainting, matting and generation tasks.
And MMSR will be deprecated and no longer exist.
Your suggestions will be updated in MMEditing.


kitty, discord and possibly more not rendering on x11 with dwm

Describe the bug
I'm on the latest nixos-unstable using lightdm with dwm on xserver. A couple of programs do not redraw/update except when I manually resize the window.
As far as I can tell, these include:

Discord
Kitty
Alacritty
Kdenlive
Possibly more

Video
clip.webm
Expected behavior
Interaction with UI elements inside the window cause visible changes and render.
Notify maintainers

kitty: @tex @rvolosatovs @Luflosi
dwm @viric @neonfuz
Although it's probably an underlying issue with packaging of xserver, opengl or some framework that kitty, discord and whatever else have in common.

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.19.3, NixOS, 22.11 (Raccoon), 22.11.20220824.b784c5a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - channels(jan): `""`
 - channels(root): `"nixos, nixos_22_05-22.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Nevermind the channel, it's a flake installation. At first I thought it was a kitty issue, but then I realized it happens with Discord, too.

Not sure which maintainers I should ping here @SuperSandro2000

I'm only a maintainer because I added a feature back to DWM and they wanted me to be a maintainer. I use  NixOS stable + DWM so I can't test this easily.

I tried to reproduce it in a VM, but without success.
My configuration.nix was:
{config, pkgs, ...}: {
  users.users.root.initialPassword = "root";

  services.xserver.enable = true;
  services.xserver.windowManager.dwm.enable = true;
  environment.systemPackages = with pkgs; [kitty dmenu];

  boot.kernelPackages = pkgs.linuxPackages_5_19;

  documentation.nixos.enable = false;
  services.openssh.enable = true;
}

Then I run:
NIXOS_CONFIG=$PWD/configuration.nix nixos-rebuild build-vm --no-flake
./result/bin/run-nixos-vm

It might be that the behavior depends on graphics drivers or other setup. @con-f-use Are you able to reproduce it if you run your config in a VM? Does it happen, if you run the above config on your hardware? Maybe, you can use specialisations to easily test different configurations.

Problem occurs on my framework laptop with 12th gen cpu + graphics.
I'll try to find a minimal configuration that reproduces the bug once I have time.

Okay so an update: the framework laptop uses intel on-board graphics, which seem to have problems at the moment (e.g. requiring a gpu hang workaround).
My problem was that I had:
services.xserver.videoDrivers = ["intel"];  # works with "modsetting"

when it works with "motstetting" instead of "intel". I have no idea why or what exactly they even do. Maybe somebody can explain.

I think that the intel driver is more or less deprecated these days. Years ago, switching from intel to modesetting solved many problems for me. Some information with links to relevant sources about deprecation can be found in Arch wiki (in the blue Note box).


Added documentation for out of space and certificate error

Documentation for issues https://github.com/jamesog/tailscale-edgeos/issues/29 e https://github.com/jamesog/tailscale-edgeos/issues/15

Just ran into this issue and these directions resolved my issues. Thanks!

Just ran into this issue and these directions resolved my issues. Thanks!

I need to be honest and confess that I migrated EdgeRouter-X to OpenWRT, there is already a ready-made package for TailScale and other VPNs, it was much easier than I imagined and the project continues to be updated, unlike EdgeOS with Unifi.


Maven: create sources jar.

This would simplify debugging and learning from the sources in IDE.
I currently use http://jitpack.io to import orion.

:cookie:


Support more authentication provider Facebook

I think login via Facebook is an important upgrade. thank

For now, adding direct support for Facebook will be a bit hard. But I'll create an example showing how you can do it yourself.

For now, adding direct support for Facebook will be a bit hard. But I'll create an example showing how you can do it yourself.

thank you


pull request for e2e test at 01/19/2017 07:15:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature request: sort subscriptions by user choice

I suspect that #853 will be higher priority than this one, but I really appreciate Innoreader allowing me to group things by my own view of importance.

Duplicate of https://github.com/Ranchero-Software/NetNewsWire/issues/356


cargo install on Windows fails if executable is currently running

OS: Windows 10 x64
Console Output:
C:\Users\USERNAME\Documents\Rust\winres>cargo install racer -f
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling rustc-serialize v0.3.22
   Compiling unicode-segmentation v0.1.3
   Compiling libc v0.2.18
   Compiling typed-arena v1.2.0
   Compiling utf8-ranges v0.1.3
   Compiling bitflags v0.7.0
   Compiling memchr v0.1.11
   Compiling ansi_term v0.9.0
   Compiling winapi-build v0.1.1
   Compiling regex-syntax v0.3.9
   Compiling unicode-width v0.1.4
   Compiling unicode-xid v0.0.3
   Compiling kernel32-sys v0.2.2
   Compiling strsim v0.5.2
   Compiling aho-corasick v0.5.3
   Compiling log v0.3.6
   Compiling vec_map v0.6.0
   Compiling winapi v0.2.8
   Compiling toml v0.2.1
   Compiling syntex_pos v0.52.0
   Compiling thread-id v2.0.0
   Compiling term_size v0.2.1
   Compiling term v0.4.4
   Compiling thread_local v0.2.7
   Compiling clap v2.19.3
   Compiling regex v0.1.80
   Compiling syntex_errors v0.52.0
   Compiling syntex_syntax v0.52.0
   Compiling env_logger v0.3.5
   Compiling racer v2.0.4
    Finished release [optimized + debuginfo] target(s) in 613.58 secs
   Replacing C:\Users\USERNAME\.cargo\bin\racer.exe
error: failed to move `C:\Users\USERNAME\.cargo\bin\cargo-install.txmENb8PGFGR\racer.exe` to `C:\Users\USERNAME\.cargo\bin\racer.exe`

To learn more, run the command again with --verbose.

cargo version:
C:\Users\USERNAME\Documents\Rust\winres>cargo version
cargo 0.17.0-nightly (740f9c0 2016-12-29)

rustc version:
C:\Users\USERNAME\Documents\Rust\winres>rustc -vV
rustc 1.16.0-nightly (4ecc85beb 2016-12-28)
binary: rustc
commit-hash: 4ecc85beb339aa8089d936e450b0d800bdf580ae
commit-date: 2016-12-28
host: x86_64-pc-windows-msvc
release: 1.16.0-nightly
LLVM version: 3.9

This is likely related to racer running in the background still, and cargo install not working to uninstall programs that are currently running.

Could we kill all racer instances in this case?

That's probably not Cargo's job itself, but Cargo can likely do something better here regardless.

2 years later, do we want to assume this still needs fixing?

I also get this almost every second time I do a cargo install. It's quite annoying really.

I forget about this every time the new version of nu shell comes out. And to update it I have to close vscode, all the console windows and open up powershell or cmd and run cargo install nu there. Quite annoying. I wonder if cargo can issue this call
https://stackoverflow.com/questions/1606140/how-can-a-program-delete-its-own-executable when run on windows.


New file / Compile / Recompile

Divided Neo-Compiler into 2 projects: Neo-Compiler and Neo-Compiler-Lib.
Refactored project dependencies. Neo-Compiler used to depend on Neo-Debugger-Core, now both Neo-Compiler and Neo-Debugger-Core depends on Neo-Compiler-Lib (.NET standard).
Using embedded compiler in Neo-Debugger-Core / Fixed file paths
Menu Item: Create new file (template contract added too)
Menu Item: Compilation / Recompilation (Rebuild). Also recompiling before opening InvokeWindow

Award lock9 300 points

https://neoscan.io/transaction/296902d9809c764eb5980d4d5ddae97a7cfc0126872cff8c4ff0e7a97ed14a1b


Fix #1175: INDEX function should behave like Excel's INDEX on horizontal ranges

Fixes #1175.
Excel Behavior:

Fixed Luckysheet Behavior:

Thanks


Automated cherry pick of #5881: fix: 阿里云资源组同步

Cherry pick of #5881 on release/3.1.
#5881: fix: 阿里云资源组同步

Codecov Report

Merging #5988 into release/3.1 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           release/3.1   #5988      +/-   ##
==============================================
- Coverage         7.45%   7.45%   -0.01%
==============================================
  Files              584     584
  Lines            98616   98665      +49
==============================================
  Hits              7352    7352
- Misses           90692   90741      +49
  Partials           572     572

Flag
Coverage Δ

#aFlag
7.45% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/cloudproviders.go
1.00% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/external_projects.go
5.35% <0.00%> (-0.20%)
:arrow_down:

pkg/multicloud/esxi/datacenter.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/manager.go
1.23% <0.00%> (-0.05%)
:arrow_down:

pkg/multicloud/esxi/resourcepool.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

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 080c776...c1198af. Read the comment docs.


Cuda out of memory

Tried to train Transformer Transducer model on Librispeech "train-clean-100" dataset on 16GB GPU. But getting "CUDA out of memory" error . Also tried by splitting various layers on 3 GPUs, 16GB each, but getting same thing. And error is pointing to ''joint'' layer, maybe because large size of tensors in joint layer.
Details:
Number of MFCCs = 128
Timesteps =512
Vocabulary size = 21800 ( tried to reduce it to 5K, but getting same thing)
Embedding layer dimension =Vocab_size*512
Audio Encoder = TransformerTransducerEncoder
Label Encoder =TransformerTransducerDecoder
loss = RNNTLoss
If anyone trained Transformer Transducer successfully and able to get results comparable with https://arxiv.org/abs/2002.02562 , please let me know the number of accelerators and their respective memory capacity.

Unfortunately, it takes a lot of memory to learn the speech recognition model.
In particular, the transducers model needs more.

Hi  @sooftware  , Thanks for your reply. Do you have idea which GPU would be good to handle this Transformer Transducer model?

Of course, the bigger the better. If several A100s are possible... That would be good.
Or it would be a good idea to reduce the mfcc coefficient and vocab size.
Transducers will use a lot of memory depending on the vocab size.

Yes, reducing the tensors dimension by various ways will work. But the thing is, I'm trying to achieve the same WER as mentioned in paper. And reducing dimensions may effect the results.

Then, I think you have no choice but to use a lot of GPUs. 😂


eitems: files and links

add login_required field in backoffice
display files and links on frontsite document details
fix links in frontsite series details (I see that refactoring may be needed there)
fix frontsite document details circulation null error
fix environment label styling on mobile
fix missing text in searchbar on frontsite document/series details

travis build


Create script is in a weird position in the UI

Godot version: 3.0
Issue description: Create script, for more logical consistency, should be in the Node inspector panel. I know it is possible in the inspector (at the bottom), but scrolling all the way down is annoying and the button on top hints to something that is more scene-specific rather than node-specific.

I'm against this for these reasons:

Inspector is also for things that aren't nodes (Resources, core types etc.) and adding script to those has little gain, while Scene Dock is about Nodes only.
New Script button attaches script to the currently selected Node in the Scene Dock. It doesn't create free script. Free script can be created using Inspector "New Resource" button (or Script Editor). Moving this button there would imply (for me at least) that it creates free script.

IMO, this button is more closely related to Scene Dock than Inspector. (Btw, I never use that button, I right-click the node and attach script from the context menu.)

In my opinion it would be better because

Scene dock is about Nodes only, yes, but treats them in "group", while inspector is dedicated to a single Node, so it makes more sense to me that when you create a script you create it for a single Node.
Free scripts should be created from the Script tab File>New. Creating them from a specialized scene is counter-intuitive, because you are working on a scene/node.

The Inspector works for all kinds of Objects, not only Nodes.
This is where this proposal is actually good - scripts get attached to Objects, not Nodes. Nodes happen to be Objects, but yet a "proper" UI is only available for Nodes. So I think this proposal is actually good since it discriminates less against non-Node types.

scripts get attached to Objects, not Nodes

What are scripts attached to Object useful for ? If it is possible but never used, I would keep the UI as it is for now.

When I work with NativeScript I attach scripts to Resources all the time. Granted, I do that by using NativeScript::_new() and let that handle that, but every once in a while I do attach scripts to stuff in the property editor because it's not a Node.

Are you using them to make game or work on the editor ? ^^
I'm not against it, but for now the UI seems more appropriate as most of the time scripts are attached to nodes. I believe there should be a real use case before changing that, as it should not worse the workflow for the sake of consistency.

Groud, while it might be obvious for an experienced Godot user, I still find it counter intuitive. The scene dock is there to manipulate the nodes between one another, organize them and sometimes multiple editing of properties. Since you can't instance a script on his own in the scene but you need to attach it to one node, I think it's more logically consistent if it is in the inspector. When I say logical consistency, I am talking about "where I expect it to be as a user", not something theoretical :)

Well, on the other hand, by now the button to access a node's script is on the node panel (on the same line as the node). Having to go down the inspector to add a script is as unintuitive as having it on the top of the tree window.
If we move the "add script" button down to the inspector, we should also provide a way to open it, and to signify in an obvious manner that a resource/a node has a script attached to it. And as it is quite useful there, we should not remove the open script button in the node tree.

I don't think so, because the script edit button on the node in the scene dock server also as an overview of which nodes are specialized and which nodes are regular nodes. Editing the script from that button makes the interaction straighforward, while i don't think that the add script on top makes the interaction straightfoward. i might want to specialize the root node (which is generally the case when you make a scene, at least for me) and have another node selected. In that case, the editor would create the script for a different node than the one i wanted. If it is moved to the inspector is clear that it is referred to that particular node

Note: Judging by the conversation above, there doesn't seem to be much support for this proposal. It may have to be rethought before you can open a new proposal.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!