Use a spritesheet for items

At the moment we use a spritesheet for Pokémon, but individual image urls for items. It might be better to have a spritesheet for items as well.

@SnowPhoenix Would it be easiest to do this while doing #543?

Didn't see this message until now, but yes, this will be taken care of at the same time as #543.


Remove OpenSea

What it solves
Resolves #2331
How this PR fixes it
By removing the OpenSea modules and imports, along with the async-sema package.
How to test it
Try to send and receive collectibles. Everything should work as before.
Any extra information
A cute narwahl picture.

The picture of the narwhal was 100% necessary, 10/10 I'd test again
It works fine for me.
Rinkeby Safe used: 0x9913B9180C20C6b0F21B6480c84422F6ebc4B808
The names of the NFTs (the one that have it) are there, every token looks fine with their image
The tokens names an icons look fine in the Send Collectibles forms and Review steps look good
The Send button in the collectible works fine
The Send button for send collectibles in the AB book look fine as  well
Sending and receiving collectibles works fine
The collectibles categories show up and disappear fine depending on if you have collectibles of that type or not
The tx shown in the Queue and Tx history look good when you send/receive collectibles
Check a mainnet safe ( 0xB88F61E6FbdA83fbfffAbE364112137480398018 ) with a ton of collectibles and they look fine
The app never crashed or had some unexpected behavior.

Awesome, thanks for the comprehensive testing @francovenica!


FAQ Answer on Software Heritage Foundation IDs

Signed-off-by: Ed Warnicke<EMAIL_ADDRESS>

LGTM


Add Glossary Page

Still a WIP...
Building out base for glossary per #970. Definitely needs more items so help would be much appreciated in checking/adding glossary items 👍

@bebraw would it make sense to port over most of the SurviveJS book glossary terms in here as the 'starting point'?

@rouzbeh84 just did one pass to clean up grammar and make the formatting more consistent. Please review, and let me know if you think any of the changes I made don't make sense. I think Bundle Splitting can probably be dropped or just point from there to the Code Splitting definition to prevent any confusion (plus I haven't seen the term bundle splitting used much).
@webpack/core-team @webpack/documentation-team any other thoughts for common terms and definitions that should be added here? I think this is a pretty good start but we could probably sneak a few more in before merging.

@bebraw would it make sense to port over most of the SurviveJS book glossary terms in here as the 'starting point'?

@rouzbeh84 You can expand/rewrite as needed. I wouldn't copy them verbatim (different writing style etc.).

Can you rebase against master? There's something funky going on with the commits.

@bebraw i dropped the duplicate commit that somehow got wrangled in...

@rouzbeh84 have you come up with any others yet or are there ones from SurviveJS you plan to port? I'm thinking we leave this open for the rest of this week then try to ship it this weekend. I'll give some thought as to where to add the link to it and add that in soon.

I figure I'll start by going through the intro section and adding words that further warrant explanation or will be referenced frequently throughout the docs as I can. I think the high level items are on there for the most part but will dig in each section and see what I can pull out for the glossary.
Also, I would love any help I can get! My explanations are sometimes good and sometimes not so great but I have a busy week this week with a few out of work events as well as work.

Closing in favor of #1242...


distro/rhel8: reinstate tar image type

See commit for details.

Thanks! Fixed.

The new tar test cases pass. Boot testing using qemu fails for some reason, which is an ongoing problem, and unrelated to this PR.

I ran the qemu tests locally, and they pass.


Fix player sprite facing wrong direction when poisoned <bug

Player sprite was facing the wrong direction when the player is in the poisoned state.

Merging my own pull-request, because otherwise it wouldn't be on time before the deadline...


Improve context timeout handling for PollMutableState

What changed?
Improve context timeout handling for PollMutableState.

Why?
Current implementation of PollMutableState by default will wait 20s for workflow to make progress. If the context timeout is less than 20s and there's no progress within that time period, a context deadline exceed error will be returned, and user will see timeout error returned from the rpc framework.
Even if user initially specified a long timeout for the long poll get history, say 60s, as long as their workflow takes longer time to run, the (java) client side, will keep decreasing the timeout and call server with shorter and shorter timeout, which eventually leads to timeout.
This means if user workflow takes longer time to run due to downstream dependencies issues, our SLO will also be impacted by those timeout errors.

How did you test it?
Integration test

Potential risks
N/A

Coverage increased (+0.2%) to 60.046% when pulling ae8ab6eebaf570e51fa9e396b711552a43b24d5b on yycptt:long-poll-get-history-err-handling into 49b64fc4407024e775f7ae7d6afaa0bf34496e42 on uber:master.


Request for Consideration: Inclusive Image Usage in Repository

I hope this finds you well. I would like to bring to your attention a concern regarding the usage of images, particularly pictures of women, in your GitHub repository. There's a possibility that the individuals in these images may not have consented to their use.
In the spirit of promoting inclusivity and respecting individuals' privacy, I kindly request a review and consideration for alternative, more inclusive imagery in your repository. It's essential to ensure that the visual content aligns with ethical practices and fosters a welcoming environment for all contributors and users.
Many journals also have be speaking out about using images without consent, so you can get problems with publishing this. Source: 1 Journal of Modern Optics, 2 Nature Nanotechnology 3 Optical Engineering
Furthermore here are some resources for alternative pictures or just use a picture of yourself, that would be a great showcase on how quickly it is possible to make anyone dance with your application! :)
I appreciate your understanding and attention to this matter. If you have any questions or would like further clarification, please feel free to reach out!

fair request... but I've seen these images used in other repositories, and I highly doubt the women depicted are in opposition to the fame since they did post it on tik-tok for million of fans

Why does this sound like it was written by ChatGPT

@Collin-Budrick thanks for agreeing with me on a needed confirmation of consent! Imo it makes a difference whether people post something they created with their body online to show million of fans or if someone else uses their body to show their work (the researcher team could have easily use their own images / videos to do so). Especially in the academic context, this is a huge no-go and can be liable to prosecution. You can also read about a similar case if you google "Lena Forsén". Many journals have be speaking out about using images unconsentionally, e. g. Nature Nanotechnology
I'd really appreciate it, if you could send me links to the other repositories where you saw this images being used! :)

what has inclusivity to do with it? What you describe is using someone's likeness without consent - an important topic, but one that is not relate to inclusivity in any shape or form.
Since we are talking about generative AI, I think a reasonable solution is to just use generated images, of non existing people. Problem solved.


Commands::get_entity() panics when its entity is deleted before it flushes.

Bevy version
0.14.2 and 0.15.0-rc.2
[Optional] Relevant system information

cargo 1.82.0 (8f40fc59f 2024-08-21)
macOS 14.5 x86

What you did
In a separate project, I have an issue where an entity is deleted by the time my commands.entity(id).insert(X) code comes around. I tried to circumvent this panic by using Commands::get_entity() which is fallible and returns on Option<EntityCommands>; however, that still causes a panic.
What went wrong
commands.get_entity() panics when the entity is no longer present. I expected it not to panic.
I expect commands.entity() to panic when the entity it's given is no longer present, and it does.
Additional information
I wrote the following code to replicate this issue.
use bevy::prelude::*;

fn main() {
    App::new()
        .add_systems(Startup, setup)
        .add_systems(Update, update)
        .add_observer(|trigger: Trigger<DeleteMe>, mut commands: Commands|
                 commands.entity(trigger.event().0).despawn())
        .run();
}

#[derive(Event)]
struct DeleteMe(Entity);

#[derive(Component)]
struct Me;

#[derive(Component)]
struct Stuff;

fn setup(mut commands: Commands) {
    commands.spawn(Me);
}

fn update(mut commands: Commands, query: Query<Entity, With<Me>>) {
    if let Ok(id) = query.get_single() {
        commands.trigger(DeleteMe(id)); // Or simply `commands.entity(id).despawn();` here.
        if let Some(mut ecommands) = commands.get_entity(id) {
            ecommands.insert(Stuff);
        }
    }
}

Here is the program's output for 0.15.0-rc.2.
Hello, world!
thread 'main' panicked at /Users/shane/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.15.0-rc.3/src/system/commands/mod.rs:1970:13:
error[B0003]: src/main.rs:30:23: Could not insert a bundle (of type `rug_pull::Stuff`) for entity 1v1#4294967297 because it doesn't exist in this World. See: https://bevyengine.org/learn/errors/b0003
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic when applying buffers for system `rug_pull::update`!
Encountered a panic in system `bevy_app::main_schedule::Main::run_main`!

Doh! Maybe all I need is try_insert(). Apologies. I think this can be closed. try_insert() is a good way to handle this.


[Documentation] Improve google play usage on how to get oauth token

Goal
Add step by step explanations on how to get oauth token.
Information
Tutorial based on Firefox 125.

Thank you!


docs: test

test

@sapphiredev deploy

Codecov Report

Merging #53 (a27c3c9) into main (9a3af3c) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a27c3c9 differs from pull request most recent head 8bf0416. Consider uploading reports for the commit 8bf0416 to get more accurate results

@@            Coverage Diff            @@
##              main       #53   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

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 9a3af3c...8bf0416. Read the comment docs.

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev deploy

@sapphiredev pack

@sapphiredev pack

@sapphiredev pack

@sapphiredev pack

@sapphiredev pack


Add auto post to patreon

when a new BOTD is set and it's been more than 16 hours.

As there's the image uploading etc. on the posts, this might be way too difficult to implement in a nice way. So I'll close this.


feat(onRunComplete): Prepend timestamp when reporting spec results

Motivation: When running test suites with watch functionality supported by Karma/Webpack it can be tricky to differentiate between runs, because the output gets appended to the console without any real delimiter between rebuilds/re-runs. So I added a timestamp when printing the overall results to make it easy to quickly differentiate between runs.
Also, I kept this timestamp behind the configuration option: showSpecTiming.

Coverage increased (+0.2%) to 84.783% when pulling 97f56fc0ea9ea82e66f5f15bb2c1864ec74f2959 on joshuaegclark:timestamp into a1a63b70e683ae95071c95bf97bb80faa402b4c1 on mlex:master.

Coverage increased (+0.2%) to 84.783% when pulling 97f56fc0ea9ea82e66f5f15bb2c1864ec74f2959 on joshuaegclark:timestamp into a1a63b70e683ae95071c95bf97bb80faa402b4c1 on mlex:master.

Coverage increased (+0.2%) to 84.783% when pulling 97f56fc0ea9ea82e66f5f15bb2c1864ec74f2959 on joshuaegclark:timestamp into a1a63b70e683ae95071c95bf97bb80faa402b4c1 on mlex:master.

Is it possible you could create a separate config option for this? I realize it's super late now, but we appreciate the help!

Is it possible you could create a separate config option for this? I realize it's super late now, but we appreciate the help!

@joshuaegclark

Is it possible you could create a separate config option for this? I realize it's super late now, but we appreciate the help!

I realize it might be confusing to read this now, but the config option you are using is not taking into account the colors config. Once you do that, this PR will be merge-able.
I know this is super old and I will be working on this soon to make up for it

this
var currentTime = reporterCfg.showSpecTiming ? new Date().toLocaleString() + ' - ' : '';
to
var currentTime = reporterCfg.showSpecTiming ? (this.USE_COLORS ? (new Date().toLocaleString() + ' - ').yellow : new Date().toLocaleString() + ' - ') : '';
Then change the lines where you used currentTime.yellow to currentTime


[Versioning] plugin module ends up with older dependency that sometimes causes interface mismatches

As part of our release process, we tag the current version with a vX tag, and the plugin submodule with a plugin/vX tag to keep versions in-sync. However, the plugin submodule has its own go.mod that depends on a specific version of the grafana-app-sdk, and which doesn't get changed until after the release, meaning it always is at least one version behind. When doing local development and building, this issue is not exposed because the go.work file has the plugin submodule use the local version of the main module, but when using them as dependencies in an app, the plugin submodule uses what's in its go.mod, which can lead to interface mismatches when minor versions change.
Th proper solution to this is to release the main module, bump the plugin go.mod version, then release the plugin module for that version.

I think the most expedient approach for this (given that the main branch is protected) that avoids requiring manual steps, would be to have the release GH action workflow cut a branch called something like plugin-release/<version> from the tagged commit, update the plugin's go.mod to use the tag version for grafana-app-sdk, and then create a plugin/<version> tag for the plugin release. The release script in scripts should then not also create the plugin release tag, relying on the action to do so.

Actually, the best quick fix here (as a more complete solution would be part of https://github.com/grafana/grafana-app-sdk/issues/236) might be to have this done in the scripts/release.sh script instead, updating the plugin/go.mod and plugin/go.sum, cutting the branch, pushing the branch, and then creating and pushing the plugin/<version> tag.


CZML image material doesn't work when its entity‘s position is time-dynamic

Sandcastle Sandcastle Example:
Browser: Chrome 91.0.4472.124
Operating System: Win10
Just to open the Sandcastle Example I paste.

Thanks @Orcallxl, I can reproduce this in Chrome on macOS as well and this looks like a bug to me. We'll take a look when we get a chance 👍

Also reported by @calogeromauceri in #10812.


Issue with /docs/user-guide/node-selection/: optional "namespaces" field for podAntiAffinity doesn't work as documented

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
The optional namespaces field for podAntiAffinity doesn't work according to the the docs page for anti-affinity which says

If [namespaces] is omitted, it defaults to the namespace of the pod where the affinity/anti-affinity definition appears. If defined but empty, it means “all namespaces.”

I discovered that if namespaces is omitted, it defaults to "all namespaces"
Proposed Solution:
Change the docs or change the default behavior to match the docs
Page to Update:
https://kubernetes.io/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-alpha-feature
Kubernetes Version: 1.5.2
Hosted on: AWS
Number of minions: 17 (although likely not a requirement)
Steps to Reproduce

Create a k8s namespace test-ns1: kubectl create ns test-ns1
Create a test deployment YAML, with anti-affinity, and N-1 replicas (where N is number of k8s nodes). Leave out the optional namespaces field in the annotation to get the default behavior.

Save .yaml file below to: ./nginx-deployment.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 16
  template:
    metadata:
      labels:
        app: nginx
      annotations:
        scheduler.alpha.kubernetes.io/affinity: >
          {
            "podAntiAffinity": {
              "requiredDuringSchedulingIgnoredDuringExecution": [
                {
                  "labelSelector": {
                    "matchExpressions": [
                      {
                        "key": "app",
                        "operator": "In",
                        "values": ["nginx"]
                      }
                    ]
                  },
                  "topologyKey": "kubernetes.io/hostname"
                }
              ]
            }
          }
    spec:
      containers:
      - name: nginx
        image: nginx:1.7.9
        ports:
        - containerPort: 80

Create deployment on test-ns1: kubectl --namespace=test-ns1 create -f ./nginx-deployment.yaml --record

Confirm all pods are scheduled (and on different nodes)

Create a separate ns: kubectl create ns test-ns2

Create deployment on test-ns2: kubectl --namespace=test-ns2 create -f ./nginx-deployment.yaml --record

Expected Behavior:
All pods should be able to placed since this is a separate namespace. The YAML didn't specify namespaces ... so I expected the default behavior to only use anti-affinity pods within the namespace and not across all namespaces.
Actual Behavior:
Some test-ns2 pods remaining in a "Pending" state. Doing a kubectl --namespace test-ns2 describe pod [pod-name] on a "Pending" pod shows the anti-affinity is preventing the pods from being replaced even though it's in a separate namespace.
Events:
  FirstSeen	LastSeen	Count	From			SubobjectPath	Type		Reason			Message
  ---------	--------	-----	----			-------------	--------	------			-------
  2m		20s		14	{default-scheduler }			Warning		FailedScheduling	pod (nginx-deployment-2310940957-gtdgv) failed to fit in any node
fit failure summary on nodes : MatchInterPodAffinity (17)

NOTE: If I add a namespaces field with a value in the anti-affinity annotation, then the affinity is only applied on the namespace specified... but I expected that to be the default behavior (leaving namespaces out of the podAntiAffinity annotation altogether).

I think this is a bug in the implementation, not the docs. The Kubernetes source code seems to confirm this:
https://github.com/kubernetes/kubernetes/blob/e443277d58e3ff1f0701ab97a1f4932389c27847/pkg/api/types.go#L1904-L1906
Perhaps resubmit this as an issue on the main Kubernetes repo?

Just an update: this is indeed a bug in the implementation, and has been fixed on the 1.7 branch. A backport to 1.6 is being discussed in https://github.com/kubernetes/kubernetes/issues/45484.

@erikgrinaker - Thanks for submitting this on the main k8s repo, and keeping me posted! Closing this doc bug.


Expandable options to select whether show non-matching tabs, regex search, select all/matched/non-matched

This is not necessary anymore.


add_recoverable_error + bump version to 0.9.0

switched from unrecoverable error to recoverable errors, to improve error handling
added to error.rs file for custom errors
bump version
fixed issue #26

Will probably have to do another to fix the linter issue

target was pushed?

@shuhuiluo yeah mistake, just pruned the branch


ongoing pickups not being listed

The url http://binners.herokuapp.com:80/api/v1.0/pickups/ongoing  is not listing the on going pickups but when I access http://binners.herokuapp.com:80/api/v1.0/pickups it retrieves all the pickups including the on going pickups,

Hi @matheusruschel, I just tried it now and it is working. Could you check it out again and let me know if something is not going as should?

Best,

Yeah, I'll try this weekend, thanks buddy!


pred_time_limit clarification and logging

resolve #318

That certainly answers my original question, so is an improvement on the status quo, but doesn't explain how to choose reasonable values - is the pred_time of models that are being fit as part of the AutoML process being logged somewhere, so one could retrieve it and look at the range of values it takes? This could be a super useful argument, if only I understood how to use it well :)

Thanks for the suggestion. I just updated the PR to log the prediction time in the log file. Please let me know if that addresses what you asked.

Perfect, thanks a lot!


Add RestoreChannelPath to 24-host

Summary
The chain must store the previous channel end so that it may restore it if the upgrade handshake fails. This may be stored in the private store.
Add RestoreChannelPath to 24-host with associated key func.

RestoreChannelPath
RestoreChannelKey

Ref: 24-host/keys.go
function restorePath(portIdentifier: Identifier, channelIdentifier: Identifier): Path {
    return "channelUpgrade/ports/{portIdentifier}/channels/{channelIdentifier}/restore"
}

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Review spec for any updates to key paths

I'll pick this one up

After syncing with @AdityaSripal we've decided to use the following pattern to adhere with existing keys defined in 24-host:
function restorePath(portIdentifier: Identifier, channelIdentifier: Identifier): Path {
    return "channelUpgrades/restore/ports/{portIdentifier}/channels/{channelIdentifier}"
}


Add UCP connection pool support in dbclient

Add UCP connection pool support in DBClient as an alternative to Hikari.
Also take the opportunity to review the API by trying to implement this in user space.
E.g.
DbClient dbClient = new JdbcDbClientProvider().builder()
    .config(config)
    .connectionPool(UCPConnectionPool.create(config))
    .build()
    .build();

The above snippet doesn't look right. We also need to make sure the programmatic way can be used to setup the connection.

CC @Tomas-Kraus @tomas-langer

Now we can use JdbcDbClientProviderBuilder.create()

Also ability to setup UCP with SslContext and tns names would make integration with #3072 great.
UCPConnectionPool.builder()
  .sslContext(sslCtx)
  .tnsNames(stringInMemory)
  ...
  .build()

@arjav-desai : Just adding the comment to the existing  bug. We are also using Helidon's dbclient obj for all the DB interactions. I don't see any methods which can accept "UCP" as the connection object from DbClient class(I can see only support for Hikari CP as of now in Helidon SE 4.0.2 SE version). It was recommended by helidon framework team to move from Hikari CP to UCP. This will definitely help us understand which JDBC connection pool would be relevant for our use case for both OP and k8's deployment. Also we are planning to include "Observability and tracing" as part of our next phase, so UCP support in dbclient will be very crucial for our product.
Note: The key selling point for our product is performance.
Please share your thoughts on this.


select date demo

I am wondering if you have a date select demo? As having a text field that users put in their date of birth may result in the following types of dates being entered.

02/03/2011
02-03-2011
03-02-2011
03-02-11
03/02/11
2nd of march 2011

I think people can see my point here.
Would be great to have a MDC looking date selector.

i didn't really get you.
do you need a text field+ date selector demo? or text field which re adjust text according to a specified format or what?

ideally something that looks like this https://storage.googleapis.com/material-design/publish/material_v_12/assets/0B3321sZLoP_Hamc5d1k2SmhlV2c/components-pickers-date3.png

ahh ok, the problem with this is, PMC is maintained as a wrapper over mdc-web. So a new component request should actually go to mdc-web and we'll expose it the preact way.


Difference between jemalloc_active_bytes and node memory

Observed from longevity test OOM.
jemalloc_active_bytes: 9.93 GB

Node memory: 12.3 GB

Difference is 2.37 GB.
Previous a very similiar issue https://github.com/risingwavelabs/risingwave/issues/9669 has been solved by https://github.com/risingwavelabs/risingwave/pull/9795

JVM is not used in longevity test.

I didn't have better ideas, so I am now trying to

Since I have no better ideas, now I am trying to manage the LRU watermark according to the system resident memory (rss) instead of Jemalloc's statistics.
Code: https://github.com/risingwavelabs/risingwave/compare/main...eric/try_manage_memory_by_rss
Test run: https://buildkite.com/risingwave-test/longevity-test/builds/816
The test was succeeded because the MemoryManager managed to controller the memory at around 7.5GB

JemallocMemoryControl { threshold_stable:<PHONE_NUMBER>, threshold_graceful:<PHONE_NUMBER>, threshold_aggressive:<PHONE_NUMBER>2 }

Resolved by #13648


Report wash trade on collection

On-chain autists has been appointed.
https://canary.kodadot.xyz/ahk/collection/u-117/activity

linking for future:

#2746

linking for future:

@yangwao I always like that


If git repo is unreachable, exception is thrown and kills the server

Whoops.
[2018-03-18 22:03:29] DEBUG CheckForNewCommitsOnGithubWorker:  Checking for new commits in All rubocops pass
Thread terminated with exception: git '--git-dir=/Users/jliebowitz/.fastlane/ci/86286442-360f-4b9f-8e2b-d60cd0f257e7/.git' '--work-tree=/Users/jliebowitz/.fastlane/ci/86286442-360f-4b9f-8e2b-d60cd0f257e7' fetch 'origin'  2>&1:fatal: unable to access 'https://github.com/fastlane/ci/': Could not resolve host: github.com
  /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:937:in `command'
  /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/lib.rb:731:in `fetch'
  /Users/jliebowitz/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/git-1.3.0/lib/git/base.rb:317:in `fetch'
  /Users/jliebowitz/dev/ci/shared/models/git_repo.rb:360:in `block in fetch'

I think this does not happen anymore on #283 but should be tested😁

I guess it's time to dive into #283
BRB, packing a lunch and a gallon of water to take with me.

Take some survival materials too. You might need to camp in the office 🤣

😎


Fix docs issue

We shouldn't pin the pip version. see discussion here: https://github.com/spatialaudio/nbsphinx/issues/563
It was an issue with Jinja2 that got fixed upstream, but by pinning pip we were having issues getting the recent version with the fix.

Codecov Report

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

@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage        ?   23.47%
=======================================
  Files           ?       33
  Lines           ?     2956
  Branches        ?      588
=======================================
  Hits            ?      694
  Misses          ?     2225
  Partials        ?       37

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 0a69b56...6bf428f. Read the comment docs.


Parse frontmatter to enable document-scope configuration + shell configuration

Runme currently retains frontmatter opaquely like a blob. It does not attempt to parse it.
Let's add support for yaml/json frontmatter. Toml is a nice-to-have which we could add later.
Similar to the fenced code block annotations, we want to add a configuration option allowing users to set a shell, such as /bin/bash instead of defaulting to the system's.

This is really two separate issues, the former of which is covered in #88.


.travis: fix issue that etcd exited on Arm64

Set env variables ETCD_UNSUPPORTED_ARCH=$(ARCH)
Signed-off-by: Jianlin Lv<EMAIL_ADDRESS>Fixes: #9898

This change is

Coverage decreased (-0.002%) to 45.604% when pulling 4724c3e4b1524e66c5e4cfd513df4c5c76c2ad05 on Jianlin-lv:pr-travis-arm64 into 0dc12fb94ed19adcef1c92f13fa50c42bc01546c on cilium:master.

Fixes: #9898

@Jianlin-lv Should this pull request actually close #9898, or does it only fix the Travis CI build for aarch64?

test-me-please

Fixes: #9898

@Jianlin-lv Should this pull request actually close #9898, or does it only fix the Travis CI build for aarch64?

I proposed #9898 to enabling cilium on arm64. CI/CD is also within the scope of planned contributions, so I attach this patch to 9898.

CI/CD is also within the scope of planned contributions, so I attach this patch to 9898.

Okay :+1: Please change "Fixes: " to something else (e.g., "Helps resolve: " or "Related: "), otherwise GitHub will close the issue when we merge this pull request.

CI/CD is also within the scope of planned contributions, so I attach this patch to 9898.

Okay 👍 Please change "Fixes: " to something else (e.g., "Helps resolve: " or "Related: "), otherwise GitHub will close the issue when we merge this pull request.

Make sense, I will update this patch later

Arf! GitHub also catches "resolves:" as indicating it should close the issue. Sorry about that. "Related:" should be fine.

Arf! GitHub also catches "resolves:" as indicating it should close the issue. Sorry about that. "Related:" should be fine.

Done

test-me-please


insert a couple of line breaks at 80 chars

Just tweaking README slightly to break up long lines (to make it easier to review on a phone!).

As a note, Nicolas M aligned all the READMEs a while ago, so you might want to apply these same changes to our other projects.


herd top yaks

Not sure if this is intended functionality or not, but when I'm in my herd and hit top yaks, I get top yaks in my area rather than top yaks in my herd.

It honestly slipped my mind to look at that. Let me check and see if the official app shows you Top Yaks while in your herd.

Apologies for the delay...I wiped my PC and installed Windows 10 the other day, and it took a while to get my Android emulator up and running again.
It looks like Top Yaks in My Area doesn't use your My Herd location in the official apps-- that is to say, it always shows your local yaks.
I agree that this is a little confusing...I think the right course of action here would be to hide the "Top Yaks" link while you have My Herd turned on. What do you think?

Yeah, I think that's a solid solution. Alternatively, you could sort the yak list by score if that's your cup of tea.


Development 1.1 leave excuse

Frontend feature done
Related Issues
#382
#389

I don't know what is the Leave Request and its value is 365 days?

The Leave excuse it added in the backend as you see and it's value for the logged in user is only 6

Also i got wrong date format


License?

What's the license on this, were does the code come from?

It's based on ChaCha20.
License's uploded.


Extending Step defs throws syntax error

I know Karate point is to make sure to not add more steps but there is always more custom requirement in projects where you have to do checks more than just API. I could have used the example of using java code example in the feature file but having just one step and all the code behind it simplifies the feature file and makes  the file readable too.
I tried to  extend the StepDefs class and added the glue to the cucumber options to the package where the steps was added but it still throws syntax.
com.intuit.karate.exception.KarateException: syntax error:

duplicate of #398 this has been discussed in depth there.


Issues deploying via Netlify

Hello. I forked your awesome website repo and went to deploy to netlify just to understand the deployment process and even though I can build just fine locally, building when deploying on netlify results in build failures.
My build settings are nothing special, I really only assigned the npm run build command and it knows it's a gatsby project.
When building:

I should also note that right when I initially deployed to netlify (without making any changes), the project deployed just fine to netlify. Once I deleted yarn.lock to get a safe build locally that's when it started failing netlify.

I should also note that right when I initially deployed to netlify (without making any changes), the project deployed just fine to netlify. Once I deleted yarn.lock to get a safe build locally that's when it started failing netlify.

Make sure you remove the node_modules and go via npm install --force command


Patch default ubuntu-release-upgrader policy

Dependencies

#225, which depends on

#223, which depends on

#221
#222

Refactor
This PR is a refactor of #213.
Status
WIP
Explanation
Ubuntu desktop proposes upgrades according to a certain policy:
$ cat /etc/update-manager/release-upgrades
# Default behavior for the release upgrader.

[DEFAULT]
# Default prompting and upgrade behavior, valid options:
#
#  never  - Never check for, or allow upgrading to, a new release.
#  normal - Check to see if a new release is available.  If more than one new
#           release is found, the release upgrader will attempt to upgrade to
#           the supported release that immediately succeeds the
#           currently-running release.
#  lts    - Check to see if a new LTS release is available.  The upgrader
#           will attempt to upgrade to the first LTS release available after
#           the currently-running one.  Note that if this option is used and
#           the currently-running release is not itself an LTS release the
#           upgrader will assume prompt was meant to be normal.
Prompt=lts

There are different releases of Ubuntu WSL on the Microsoft store. These can be classified in three categories. Currently, the policy is always lts by default. This PR changes the default upgrader policy to:

Category
Releases in store
Desired default policy

Preview
Ubuntu (Preview)
normal

Latest LTS
Ubuntu
lts

Numbered
Ubuntu 18.04.5 LTSUbuntu 20.04.4 LTSUbuntu 22.04 LTS
never

Closing as we'll take a diferent approach


Publish rom-rethinkdb to RubyGems

Are there plans to publish rom-rb/rom-rethinkdb to RubyGems? Or is it still a WIP and not ready for use?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/25697335-publish-rom-rethinkdb-to-rubygems?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github).

Yes, unfortunately nobody has found the time to do that yet :) I can push what we have as 0.0.1. It probably needs a couple smaller updates but it shouldn't take too long.
 I've been reading about it and it seems pretty awesome. Would love to try it out.

I used RethinkDB a bit several months back just to try it out. It's a cool and definitely well thought out system. I'm looking at using it for a new project where realtime streams would be beneficial.
I just converted some of my codebase from rom-sql to rom-rethinkdb (it's amazing how easy it is with ROM) and was met with some limitations in the rom-rethinkdb gem. I forked it so I'll try to add some functionality.

@abernardes aah, I just updated it to ROM 0.9.0.beta in master and configured build on travis
It'd be awesome if you could add some features. We'll definitely push a release together with ROM 0.9.0.

The adapter has been released :)


NUTCH-2732: .template for configuration files.

In order to avoid ignored and tracked files by git at the same time I renamed those files to extension .template.

+1


Angular SPA Template Returning Status Code from Angular App

It seems that the SpaPrerendering services support returning proper status code such as 404 for not found error (https://github.com/aspnet/JavaScriptServices/issues/1423).
But the documentation lacks the details on how do we return the status code from the Angular App.
Can you please guide and update the docs?
Thank you

cc:
@SteveSandersonMS
@MarkPieszak

@SteveSanderson can you please take a look at this approach https://stackoverflow.com/a/50937983/2755616 and share the feedback?


TILA-2571: Validate duration being a multiple of interval

Change log

Updated duration validation
Updated tests

Other notes
This means that if reservation unit's interval is set to 15 minutes, allowed durations are 15, 30, 45 etc. If interval is 30 minutes, allowed durations are 30, 60, 90 etc.
Deployment reminder

No changes required

Fly me to the moon! 🚀

Thanks for the earworm! 🤣


Updated the occurrences of py36 to py37

Removed occurrences of py36 in public documentation since py36 is getting deprecated. The minimum python version that is supported is py37.

Learn Build status updates of commit e2e46b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 3e11907:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 9183885:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/v1/how-to-train-scikit-learn.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

includes/machine-learning-service-inference-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 5e72d32:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/v1/how-to-train-scikit-learn.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-tensorflow.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

includes/machine-learning-service-inference-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit b2deec5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/v1/how-to-train-keras.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-pytorch.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-scikit-learn.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-tensorflow.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

includes/machine-learning-service-inference-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 7317774:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/how-to-train-with-custom-image.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-keras.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-pytorch.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-scikit-learn.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-tensorflow.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-auto-train-image-models-v1.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

includes/machine-learning-service-inference-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit e1ec1e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/machine-learning/how-to-train-with-custom-image.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-auto-train-image-models-v1.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-deploy-inferencing-gpus.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-keras.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-pytorch.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-scikit-learn.md
:white_check_mark:Succeeded

articles/machine-learning/v1/how-to-train-tensorflow.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-1st-experiment-sdk-train.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-auto-train-image-models-v1.md
:white_check_mark:Succeeded

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:white_check_mark:Succeeded

includes/machine-learning-service-inference-config.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@v-qquaidjoha - recommend not adding more commits to this PR. If you need to update additional articles, open a new PR. In the public repo, each article author has to approve changes so this PR may take a while to get fully approved, but if it's split into smaller PRs - each with one article (for example) the approvals usually go more quickly.
So far, I see approval by

@Blackmist

Still waiting on:

@aminsaied @lgayhardt @saachigopal @balapv @swatig007

Thanks.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Looks like, this PR needs explicit signoff from partners. Reached out to @saachigopal , @balapv , @swatig007 for the review and approval.

#sign-off

#sign-off


fix: s3 source cannot read incremental files

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
prev fix does not handle the case right https://github.com/risingwavelabs/risingwave/pull/17702

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Maybe related: #17991

New update:

Fixed the issue of being unable to read stock files
Temporarily set the sleep interval to 1 minute, and try to make it a configuration item later. (open an issue to track https://github.com/risingwavelabs/risingwave/issues/18123)

Since I also modified this PR, this PR needs approval from another reviewer( @xxchan @fuyufjh ). Basically
, this PR has fixed the problem of reading newly added files. Currently, json and csv encode have been fixed. There is another problem with parquet encode, which will be fixed in the another PR.

This test(S3 source and sink on parquet file) is a flacky test. It will also fail in other PRs, regardless of the changes made in this PR.


link below "Next Steps" at bottom of page incorrect

link below "Next Steps" at bottom of page incorrect
Currently shows:
Proceed to Phase 1: Setup.
Should read:
Proceed to Phase 1: Prepare
NOTE - link works correctly and proceed to 1:Prepare

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

ID: 71fea5e3-4515-b0a0-2db7-94f320343509
Version Independent ID: 71fea5e3-4515-b0a0-2db7-94f320343509
Content: Migrate from a third-party protection service to Microsoft Defender for Office 365 - Office 365
Content Source: microsoft-365/security/office-365-security/migrate-to-defender-for-office-365.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@dcaddick, fixed.
Thanks for the feedback.
Closing


Abort Trap: 6 error

I'm getting an Abort trap:6 code error when I try to generate a consensus sequence.
nanopolish consensus -w 1910bp:1-1910 --reads /Users/lukewoodford/Data/Input/DWVsurvey/500_read_subsets/DWV_BC01_500a.fa --bam BC01_500reads.eventalign.sorted.bam --genome /Users/lukewoodford/Data/Refs/DWV/REF1910.fa --models /usr/local/bin/nanopolish_dir/etc/r9-models/ -o /Users/lukewoodford/Desktop/BC01_DWV_500reads.fa  Abort trap: 6
Does anyone know what is causing this and how to fix it?
Thanks, Luke

nanopolish consensus is deprecated, try using nanopolish variants --consensus instead (see README for the syntax)

Thanks. I've got the following error now
nanopolish variants --consensus polished.{1}.fa -w {1} -r /Users/lukewoodford/Data/Input/DWVsurvey/500_read_subsets/DWV_BC01_500a.fa -b BC01_500reads.eventalign.sorted.bam -g /Users/lukewoodford/Data/Refs/DWV/REF1910.fa -t 1 --min-candidate-frequency 0.1 #CHROM	POS	ID	REF	ALT	QUAL	FILTER	INFO	FORMAT	sample Error: could not find path to FAST5 for read 0052e7d0-fd76-48bf-94e9-6eaef5dc6fd9_Basecall_2D:2D_000:2d Please make sure that this path is accessible: /Users/lukewoodford/Data/Albacore_analysis/workspace/barcode01/Lukes_MacBook_Pro_local_20170427_FNFAE22557_MN20133_sequencing_run_270417_DWV_26537_ch272_read12418_strand.fast5``
Not sure why it is saying it can't find a particular read. I've checked and that sequence is definitely in that directory and the path is correct.

This looks like a difference between OSX and Linux. I'm looking into it.

Hi Jared, just wondering if you've had any joy with this?

Not yet sorry. Is it possible for you to run nanopolish on a linux system?

We'll need to set a system up for that, we're exploring that option now.

Hi Jared, I've switched to a linux system and I'm trying to process the same files. I'm getting an error now of
error: could not parse model string
when trying to eventalign my indexed sam files.
What does this error mean and do you know a way around it?

You need to basecall your files with the standalone version of albacore, not MinKNOW.

Hi Jared, these reads were basecalled using Albacore 1.1.0 (they are 2D reads, so I haven't ungraded!).

If you use albacore 1.2.4 it should work - it is the most recent version that includes 2D support.

ok, I'll try that out. Thanks

Hi Jared, my second albacore set using version 1.2.4 gave me the same error as before. Following advice you'd posted elsewhere I extracted all files as 1D reads and tried the process again.
I'm now getting the following errors:
nanopolish eventalign -t 4 --sam -r '/home/david/bin/Barcode01_1d/312_1d_90_T00001.fa' -b '/home/david/bin/BC01_312_0001reads.sorted.bam' -g '/home/david/bin/Ref/BC01_1d_312_00001ref.fa' --models '/home/david/Downloads/nanopolish/etc/r9-models' | samtools view -S - | samtools sort -O BAM -o '/home/david/bin/BC01_312_0001reads.eventalign.sorted.bam' Error: duplicate read name 7f6dc0d0-4a7f-437b-b821-74501e7d3501_Basecall_1D_template:1D_001:template found in fasta file
And when I remove the repeated read...
david@linus:~$ nanopolish eventalign -t 4 --sam -r '/home/david/bin/Barcode01_1d/312_1d_90_T00001.fa' -b '/home/david/bin/BC01_312_0001reads.sorted.bam' -g '/home/david/bin/Ref/BC01_1d_312_00001ref.fa' --models '/home/david/Downloads/nanopolish/etc/r9-models' | samtools view -S - | samtools sort -O BAM -o '/home/david/bin/BC01_312_0001reads.eventalign.sorted.bam' [fai_load] build FASTA index. [E::sam_parse1] missing SAM header [W::sam_read1] parse error at line 1 [bam_sort_core] truncated file. Aborting.
Can you offer any advice here?
Thanks.

Hi,
The --sam and --models options are no longer required and you shouldn't need to provide them. What are you trying to do with nanopolish (call SNPs, call a consensus sequence, etc)? If you let me know I might be able to improve your workflow.
Regarding the error, trying running eventalign on its own (without piping into samtools) and it might print a more informative error message.
Jared

Hi,
I'm trying to generate consensus sequences. I've tried what you've suggested and I'm able to print the eventalign output in terminal, but I'm not sure how to output this as a file which can then be indexed.
Simple > eventalign.sorted.bam prints all output, but this is obviously not the right format for indexing...

Ok. You should use this workflow, which does not require running eventalign:
https://github.com/jts/nanopolish#computing-a-new-consensus-sequence-for-a-draft-assembly

OK, I think I'm nearly there...
Getting the following during consensus generation:
nanopolish variants --verbose --consensus BC01_312_00333con.fa --window 649ed0bf:1-1500 --reads '/home/david/bin/Barcode01_1d/312_1d_90_T00333.fa' --bam '/home/david/bin/BC01_312_00333reads.sorted.bam.bai' --genome '/home/david/bin/Ref/BC01_1d_312_00333ref.fa' ##fileformat=VCFv4.2 ##INFO=<ID=TotalReads,Number=1,Type=Integer,Description="The number of event-space reads used to call the variant"> ##INFO=<ID=SupportFraction,Number=1,Type=Float,Description="The fraction of event-space reads that support the variant"> ##INFO=<ID=BaseCalledReadsWithVariant,Number=1,Type=Integer,Description="The number of base-space reads that support the variant"> ##INFO=<ID=BaseCalledFraction,Number=1,Type=Float,Description="The fraction of base-space reads that support the variant"> ##INFO=<ID=AlleleCount,Number=1,Type=Integer,Description="The inferred number of copies of the allele"> ##FORMAT=<ID=GT,Number=1,Type=String,Description="Genotype"> #CHROM	POS	ID	REF	ALT	QUAL	FILTER	INFO	FORMAT	sample nanopolish: src/alignment/nanopolish_alignment_db.cpp:364: void AlignmentDB::load_region(const string&, int, int): Assertion m_region_end >= 0' failed.
Aborted`

You've given the .bai file as the --bam argument instead of the .bam.

Ah yes, woops! I've removed it, however I'm getting the same error. I wondered if it was a fault with the --window argument? Currently I'm using the name of the ref fasta and seq length, is this appropriate?

Yeah, that should be fine. Are you using the latest version of nanopolish?

It's 0.7.1

Is 649ed0bf the complete name of the fasta record?

Yes

I just pushed a change that might help identify the problem, could you update to the latest code and test it?

Hi, here is the output with the updated Nanopolish:
/home/david/nanopolish/nanopolish variants --consensus BC01_312_00333con.fa --window 649ed0bf:0-1593 --reads '/home/david/bin/Barcode01_1d/312_1d_90_T00333.fa' --bam '/home/david/bin/BC01_312_00333reads.sorted.bam' --genome '/home/david/bin/Ref/BC01_1d_312_00333ref.fa' error: faidx could not get contig length for contig 649ed0bf

Ok so either 649ed0bf is not a valid fasta record name, or your .fai file is corrupted. Maybe try to delete the .fai file and try again?

Great, deleting the .fai file has worked and the consensus file has been generated. Thank you so much for all your help!

Great, glad to hear it!


PlaybackFinished has no effect on iOS

Steps to reproduce :scroll:

AnimationView in a Xamarin.Forms control

Animation is started manually by executing AnimationView.PlayProgressSegment(0, 1)

AnimationView.PlaybackFinished() is called

Expected behavior :thinking:
Animation should be stopped.
Actual behavior :bug:
Animation keeps running.
Configuration :wrench:
Version: 2.5.4
Platform:

[ ✓ ] :iphone: iOS
[  ] :robot: Android
[  ] :checkered_flag: WPF
[  ] :earth_americas: UWP
[  ] :apple: MacOS
[  ] :tv: tvOS
[ ✓ ] :monkey: Xamarin.Forms

@RustamIrzaev can you check this?

@martijn00 I could, but at the moment, I don't have an access to my Windows machine, only to Mac. So I could try to fix the issue only for iOS/Droid platforms, but not for UWP (in case it needs fixing)

@RustamIrzaev Yes iOS/Droid only would be fine, i could make a fix for Windows after you do them.

@martijn00 I've stuck with errors during building the project.
Something like
`/Users/rustamirzaev/Projects/LottieXamarin/Lottie.Forms/Lottie.Forms.csproj: Error NU1202: Package Com.Airbnb.iOS.Lottie 2.5.4 is not compatible with netstandard2.0 (.NETStandard,Version=v2.0). Package Com.Airbnb.iOS.Lottie 2.5.4 supports:

xamarinios10 (Xamarin.iOS,Version=v1.0)
xamarinmac20 (Xamarin.Mac,Version=v2.0)
xamarintvos10 (Xamarin.TVOS,Version=v1.0) (NU1202) (Lottie.Forms)`

Probably, I have to wait until new VS4Mac release will appear. By the way, I will try again after work

Yeah VS4Mac can't compile it, so you have to compile from command line.
msbuild Lottie.sln /t:restore
msbuild Lottie.sln /p:Configuration=Release


Refactor TCP socket read impl to handle correctly EOF and no data

I noticed that the read implementation of the TCP Socket located in wifi_interface.rs is incorrect. When I was trying to use the embedded_tls package to perform HTTPS requests using esp-wifi I noticed that the TLSConnection could not perform handshake and always returns an IoError.
It seems that the current read implementation does not check if there is data available. Indeed, the recv_slice on smoltcp TCP Socket returns Ok(0) when there is no data available, and RecvError::Finished when the reading half is closed, take a look at the smoltcp docs. The issue is that an Ok(0) [no data] returned by the WifiStack TCP Socket read function can be interpreted as an EOF and thus trigger some kind of IO Error, whereas the socket is fine and is just waiting for data.
Furthermore, the recv function in smoltcp TCP Socket checks whether the reading half is open, which reduces a lot the code for the read implementation.
https://github.com/smoltcp-rs/smoltcp/blob/fa7fd3c321b8a3bbe1a8a4ee2ee5dc1b63231d6b/src/socket/tcp.rs#L1092C1-L1104C6
PS: Should read return IoError::TcpRecvError or IoError::SocketClosed ?

Thanks!
Unfortunately, the dhcp.rs example doesn't work correctly with this anymore since it never gets a SocketClose. It kind of works since it runs into a timeout but it always only gets Ok(0) after receiving the http response.
In Wireshark however I definitely see the FIN

Err(SocketClosed)

I think returning Err(IoError::SocketClosed) in the Err(RecvError::Finished) case is the correct thing to do since otherwise the client cannot know if it's getting a zero-length read because there was no data ready to read or the socket got closed
This will at least fix the dhcp-example - if your use-case (using embedded_tls) still works this way I'd say we should do it like this

Both dhcp-example and my code using embedded_tls works with this modification!


V4 Rename $card-link-hover-color to $card-inverse-link-hover-color

I think $card-inverse-link-hover-color is a better description of what this variable does.

Thanks!

/x-ref #22414


split terminal fails in a new terminal

Does this issue occur when all extensions are disabled?: Yes/No
Yes
Version: 1.58.1 (user setup)
Commit: 2aeda6b18e13c4f4f9edf6667158a6b8d408874b
Date: 2021-07-13T06:58:28.115Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:

click "new terminal"
click "split terminal"
it opens error widow "The terminal process failed to launch: starting directory cwd.  does not exist"

Although splitting in the first terminal works well, (only on new terminal it gives this error)

/duplicate #128277


Auto merge PR with limited merging strategy (e.g. Rebase)

If there are defined branch policies that limits the way PR can be merged one needs to first set completionOptions of the pull request object, otherwise it would look like all checks/policies are green but PR is still not merged and requires manual intervention. To fix that I had to use following curl:
PR_PATCH_URL="$SYSTEM_TEAMFOUNDATIONCOLLECTIONURI$SYSTEM_TEAMPROJECTID/_apis/git/repositories/PROJECT/pullrequests/$p?api-version=7.0"
curl -XPATCH -u :$(PAT) -H "Content-Type: application/json" -d "{ autoCompleteSetBy: \"$IDENTITY_ID\", completionOptions: { mergeStrategy: \"rebase\"} }" $PR_PATCH_URL

I think having optional task parameter for that purpose could be useful

@molszews , contributions are welcome


multi arch build

would be awsome to see multi arch builds.

This should be supported now!

The docker images now include linux/amd64 and linux/aarch64 artefacts.

@philn awesome. thanks a bunch


Visibility State and URL Query Params dimension Scope

Hi Phil,
Thank you for all your work. I've started to learn more about analytics and your resources have been great. I've a question about the last two dimension on this object:
const dimensions = {
  TRACKING_VERSION: 'Tracking Version',
  CLIENT_ID: 'Client ID',
  WINDOW_ID: 'Window ID',
  HIT_ID: 'Hit ID',
  HIT_TIME: 'Hit Time',
  HIT_TYPE: 'Hit Type',
  HIT_SOURCE: 'Hit Source',
  VISIBILITY_STATE: 'Visibility State',
  URL_QUERY_PARAMS: 'URL Query Params',
};

What should the scope be? To fill this form:

Thank you,
-Ricardo.

Set a "Hit" scope as these values can change within a session (and thus user).
In general, if you're unsure, the safest bet is "Hit" as it's the most flexible. This video on the Google Analytics data model might help you better understand when to choose which.


changes to CREATE2

What is wrong?
CREATE2 is changing:

problem description: https://github.com/ethereum/EIPs/pull/1014#issuecomment-413990682
proposed solution: https://github.com/ethereum/EIPs/pull/1014#issuecomment-414160604
change to gas cost proposed by V: https://github.com/ethereum/EIPs/pull/1375#issuecomment-425641771

How can it be fixed
Wait to see where things land with the spec and update our implementation.

I would like to work on this issue. Could you please guide me regarding the codebase as to where to start?

Correct me if I'm wrong but this issue is going to require some depth of knowledge with this library which I don't believe you have.  Probably best to stick to things labeled as "Good first issue" until you are more familiar with the codebase.


Update README.md due to update of clang-tools:all

Refer to https://github.com/shenxianpeng/clang-tools/issues/20

Reopen this ticket because I forgot to update action.yml


Python Rest API example

Include Python API examples

I'd like to work on this one. Just wanted more details or to know if there's any requirement that should be met.

Sure, lets talk about that


Getting mavlink feed from TCP but not UDP on QGC.

On my raspberry Pi I launched the router as follow:
mavlink-routerd -e <IP_ADDRESS>:14550 /dev/ttyPixhawk:921600

It displays
Could not open conf file '/etc/mavlink-router/main.conf' (No such file or directory)
Error while trying to write serial port latency: Unknown error -1
Open UART [4] /dev/ttyPixhawk *
UART [4] speed = 921600
Open UDP [5] <IP_ADDRESS>:14550
Open TCP [6] <IP_ADDRESS>:5760 *

If I add a comm link on QGC over TCP using my RaspberryPi IP and port 5760 it works.
But if I add a comm link on QGC over UDP using my RaspberryPi IP and port 14550 it doesn't work.
I notice that there is a difference between <IP_ADDRESS>:14550 and <IP_ADDRESS>:5760 *. The wildcard isn't on my rule. I tried to add it but it doesn't work.

Same thing when connecting with MAVROS.

You need to specify the target IP address on a UDP endpoint, if it's in normal mode. When QGC is running on the same machine, use the localhost/ loopback address <IP_ADDRESS>. In your case the UDP packets don't know where to go, because no network interface has <IP_ADDRESS> as address. (You can only use that one to receive from everyone, when opening a port with mavlink-router.)
And the asterisk in the log output shows, that mavlink-router will bind to/ listen on that IP and port. It's no wildcard. I also had to search the source code to find that piece of information.

I'll close this now because of inactivity. Please comment, if this issue is still unsolved.


Error: No space while executing gk-deploy

I am facing this "No space error".
Logs while executing gk-deploy:
All the vdb devices are freshly added using virt-manager and they are raw devices each of 4GB size.
===================================
[root@m1 deploy]# ./gk-deploy -c oc -g topology.json
Welcome to the deployment tool for GlusterFS on Kubernetes and OpenShift.

Before getting started, this script has some requirements of the execution
environment and of the container platform that you should verify.

The client machine that will run this script must have:

Administrative access to an existing Kubernetes or OpenShift cluster
Access to a python interpreter 'python'
Access to the heketi client 'heketi-cli'
Each of the nodes that will host GlusterFS must also have appropriate firewall
rules for the required GlusterFS ports:
2222 - sshd (if running GlusterFS in a pod)
24007 - GlusterFS Daemon
24008 - GlusterFS Management
49152 to 49251 - Each brick for every volume on the host requires its own
port. For every new brick, one new port will be used starting at 49152. We
recommend a default range of 49152-49251 on each host, though you can adjust
this to fit your needs.
In addition, for an OpenShift deployment you must:
Have 'cluster_admin' role on the administrative account doing the deployment
Add the 'default' and 'router' Service Accounts to the 'privileged' SCC
Have a router deployed that is configured to allow apps to access services
running in the cluster
Do you wish to proceed with deployment?
[Y]es, [N]o? [Default: Y]: Y
Using OpenShift CLI.
NAME STATUS AGE
glusterstore Active 9h
Using namespace "glusterstore".
Checking that heketi pod is not running ... OK
template "deploy-heketi" created
serviceaccount "heketi-service-account" created
template "heketi" created
template "glusterfs" created
node "m1" labeled
node "c1" labeled
node "c2" labeled
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ... OK
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ... OK
Creating cluster ... ID: fc74e4ee3cd42c127b3d45adbdc1f8aa
Creating node m1 ... ID: 8ac07a8c8dbbdd392c1f8dab81dd4395
Adding device /dev/vdb ... OK
Creating node c1 ... ID: eccf5f908572dff94886e9b7d505efb2
Adding device /dev/vdb ... OK
Creating node c2 ... ID: 9a4953c772e57555d4dbb14c23609fcf
Adding device /dev/vdb ... OK
heketi topology loaded.
Error: No space
Failed on setup openshift heketi storage

===================================

@SaravanaPunith Could you also paste your topology file?

[root@m1 deploy]# cat topology.json
{
  "clusters": [
    {
      "nodes": [
        {
          "node": {
            "hostnames": {
              "manage": [
                "m1"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/vdb"
          ]
        },
	{
          "node": {
            "hostnames": {
              "manage": [
                "c1"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/vdb"
          ]
	},
        {
          "node": {
            "hostnames": {
              "manage": [
                "c2"
              ],
              "storage": [
                "<IP_ADDRESS>"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/vdb"
          ]
        }
      ]
    }
  ]
}

@SaravanaPunith Thanks. I'm not seeing anything to point to cause immediately. @humblec can you take a look?

some logs from node, while running gk-deploy:
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 81.467µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters/fc74e4ee3cd42c127b3d45adbdc1f8aa
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 211.72µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /nodes/8ac07a8c8dbbdd392c1f8dab81dd4395
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 219.326µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /nodes/9a4953c772e57555d4dbb14c23609fcf
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 318.617µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /nodes/eccf5f908572dff94886e9b7d505efb2
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 235.497µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters/fc74e4ee3cd42c127b3d45adbdc1f8aa
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 144.224µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters/fc74e4ee3cd42c127b3d45adbdc1f8aa
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 145.059µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters/fc74e4ee3cd42c127b3d45adbdc1f8aa
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 136.018µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 62.476µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /clusters/fc74e4ee3cd42c127b3d45adbdc1f8aa
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 175.811µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started POST /volumes
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 202 Accepted in 70.729µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [asynchttp] INFO 2017/04/17 18:33:19 Started job 363bc6ae41bbcbe5037a727d77268fc3
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] INFO 2017/04/17 18:33:19 Creating volume 3af06af7544b3cc173e8ea615311e3a6
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] INFO 2017/04/17 18:33:19 brick_num: 0
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Started GET /queue/363bc6ae41bbcbe5037a727d77268fc3
Apr 17 14:33:19 c1 dockerd-current[1164]: [negroni] Completed 200 OK in 22.258µs
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] INFO 2017/04/17 18:33:19 brick_num: 0
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] INFO 2017/04/17 18:33:19 brick_num: 0
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] INFO 2017/04/17 18:33:19 brick_num: 0
Apr 17 14:33:19 c1 dockerd-current[1164]: [heketi] ERROR 2017/04/17 18:33:19 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: No space
..
Apr 17 14:33:22 c1 systemd[1]: Scope libcontainer-11229-systemd-test-default-dependencies.scope has no PIDs. Refusing.
Apr 17 14:33:22 c1 dockerd-current[1164]: time="2017-04-17T14:33:22.162669864-04:00" level=warning msg="containerd: unable to save 2c9117e1bc89df452f85bfe205c0452f2a89744fd9d0991b076afcecd1729f36:53f0d48e58acc040c5c4849a964aa3275df06bd0c4f1890cf162c81057edd378 starttime: open /proc/11240/stat: no such file or directory"
Apr 17 14:33:22 c1 dockerd-current[1164]: time="2017-04-17T14:33:22.162991184-04:00" level=info msg="containerd: 2c9117e1bc89df452f85bfe205c0452f2a89744fd9d0991b076afcecd1729f36:53f0d48e58acc040c5c4849a964aa3275df06bd0c4f1890cf162c81057edd378 (pid 11240) has become an orphan, killing it"

@jarrpa He is using old heketi-client-3.0.0-1 Which makes use of 4 GB for the db volume AFAIK.

Thanks to @MohamedAshiqrh , issue is fixed as below:
// heketi version is old
[root@m1 deploy]# rpm -qa | grep heketi
heketi-client-3.0.0-1.el7.x86_64
heketi-3.0.0-1.el7.x86_64
heketi-templates-3.0.0-1.el7.x86_64
downloaded heketi-client-v4.0.0.linux.amd64.tar.gz from https://github.com/heketi/heketi/releases.
// Replaced heketi-cli as below:
cp bin/heketi-cli  /usr/bin/heketi-cli/
Now, all is well :+1:

Time to update heketi in official Centos release ?
# yum search heketi
===================================================== N/S matched: heketi =====================================================
heketi-client.x86_64 : Command line client for Heketi
heketi-templates.x86_64 : Heketi and GlusterFS templates for Heketi
python-heketi.x86_64 : Python libraries for Heketi
heketi.x86_64 : RESTful based volume management framework for GlusterFS
Name and summary matches only, use "search all" for everything.

[root@m1 deploy]# yum info heketi-client.x86_64
Loaded plugins: fastestmirror
Repository centos-openshift-origin is listed more than once in the configuration
Repository centos-openshift-origin-testing is listed more than once in the configuration
Repository centos-openshift-origin-debuginfo is listed more than once in the configuration
Repository centos-openshift-origin-source is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: centos.excellmedia.net
 * epel: epel.mirror.angkasa.id
 * extras: centos.excellmedia.net
 * updates: centos.excellmedia.net
Installed Packages
Name        : heketi-client
Arch        : x86_64
Version     : 3.0.0
Release     : 1.el7
Size        : 17 M
Repo        : installed
From repo   : epel
Summary     : Command line client for Heketi
URL         : https://github.com/heketi/heketi
License     : ASL 2.0
Description : Command line client for Heketi
            :
            : Command line program to interact with Heketi

@SaravanaPunith you can create a Issue in heketi repo to build a new rpm for centos.

the same issue

heketidbstorage volume takes 2 GB now but in the build 3.0.0-1 it takes 32GB.

Thanks @MohamedAshiqrh! Closing this issue. :)


gst_all_1.gstreamermm: mark broken

gst_all_1.gstreamermm: mark broken

linux-x86-64: logs: https://termbin.com/n5hb

Downstream packages broken by extension:

mapmap
subtitleeditor

From the homepage:

The GStreamer API C++ bindings are based on gtkmm. They are currently not actively developed and won't compile with the latest GStreamer and glibmm versions.

From the homepage:

The GStreamer API C++ bindings are based on gtkmm. They are currently not actively developed and won't compile with the latest GStreamer and glibmm versions.

I'm out of context. I just wanted to mark package as broken because it is showing up in downstream build results.

With the patch from debian, it compiles.
I will make a PR for this.

Sorry. Merged on mistake. Best past forward would be to Romildo to rebase his PR. And then we are good.

Sorry. Merged on mistake. Could revert but best path forward would be to Romildo to rebase his PR.


docs: Chainstack implementation update

What I did

Updated README with clear instructions.
Renamed provider.py to providers.py.
Added Goerli network to __init__.py.

How I did it
Forked and modified my branch.
Ran pre-commit
Checklist

[ x] Passes all linting checks (pre-commit and CI jobs)
[x ] New test cases have been added and are passing
[x ] Documentation has been updated
[ x] PR title follows Conventional Commit standard (will be automatically included in the changelog)

I think I'll close this PR and re-fork the updated code. I'll test it and if it works I'll open another PR just to update the README!


FF ONLY Merge 0.6.x into master, October 16

Motivation: bring the JDK 9 build fixes on master.
$ git checkout -b merge-0.6.x-into-master-october-16
Switched to a new branch 'merge-0.6.x-into-master-october-16'

$ git st

$ export mb=$(git merge-base scalajs/0.6.x scalajs/master)

$ git log --graph --oneline --decorate $mb..scalajs/0.6.x | cat
*   d47c20c (scalajs/0.6.x) Merge pull request #3151 from sjrd/build-on-jdk9
|\
| * e285985 (origin/build-on-jdk9, build-on-jdk9) Work around #3152: disable Scaladoc generation for `library` on JDK 9.
| * 16c7866 Forward the system property `scala.ext.dirs` in `ExternalCompile`.
| * 9ebbf6d Do not call `super.finalize()` because it is deprecated in JDK 9.
| * 98973d4 Correctly setup `apiMappings` on JDK 9.
| * bfb4b16 Add new overloads of existing methods of Math in Java 9.
| * 41544fc Use `valueOf` instead of constructors for boxed classes.
| * 157add3 Adapt the codebase to changes in nio Buffers in Java 9.
| * 7e8433b Allow to load the build on JDK 9.
|/
*   02e3830 Merge pull request #3136 from MikaelMayer/fix-group-regex
|\
| * 4aecb56 Fix #3134: Make regex.Matcher report correct group positions.
|/
*   9b4de23 (origin/0.6.x, 0.6.x) Merge pull request #3149 from sjrd/fix-test-suite-on-node-js-8
|\
| * 4b42ad7 (origin/fix-test-suite-on-node-js-8) Fix #3148: Make our test suite pass on Node.js 8.
|/
*   31a51c0 Merge pull request #3131 from sjrd/review-stringbuilder-stringbuffer
|\
| * a487545 (origin/review-stringbuilder-stringbuffer) Rewrite and complete j.l.String{Builder,Buffer}.
|/
*   f82f4ac Merge pull request #3137 from sjrd/fix-relative-source-maps
|\
| * 4d8f39a [no-master] Fix #3135: Relativize source map URIs against the .js file.
* |   4204fcb Merge pull request #3138 from sjrd/further-reduce-test-suite-on-phantomjs
|\ \
| |/
|/|
| * e722745 [no-master] Further reduce the pressure on PhantomJS in the test suite.
|/
*   7245687 Merge pull request #3129 from sjrd/fix-jdk7
|\
| * cb194ae (origin/fix-jdk7) Fix #3128: Avoid a binary incompatibility on JDK 7.
* b6e35e2 Merge pull request #3130 from sjrd/fix-escape-backslash-a
* 5a9a546 (origin/fix-escape-backslash-a) Fix #3125: Do not pretty-print '\u0007' as '\a'.

$ git merge --no-commit 7245687
Auto-merging test-suite/shared/src/test/scala/org/scalajs/testsuite/compiler/RegressionTest.scala
Auto-merging ci/matrix.xml
Automatic merge went well; stopped before committing as requested

$ git st
M  ci/matrix.xml
M  ir/src/main/scala/org/scalajs/core/ir/Utils.scala
M  test-common/src/main/scala/org/scalajs/testcommon/RPCCore.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/compiler/RegressionTest.scala

$ git commit
[merge-0.6.x-into-master-october-16 56125c1] Merge '0.6.x' into 'master'.

$ export mb=$(git merge-base scalajs/0.6.x HEAD)

$ git log --graph --oneline --decorate $mb..scalajs/0.6.x | cat
*   d47c20c (scalajs/0.6.x) Merge pull request #3151 from sjrd/build-on-jdk9
|\
| * e285985 (origin/build-on-jdk9, build-on-jdk9) Work around #3152: disable Scaladoc generation for `library` on JDK 9.
| * 16c7866 Forward the system property `scala.ext.dirs` in `ExternalCompile`.
| * 9ebbf6d Do not call `super.finalize()` because it is deprecated in JDK 9.
| * 98973d4 Correctly setup `apiMappings` on JDK 9.
| * bfb4b16 Add new overloads of existing methods of Math in Java 9.
| * 41544fc Use `valueOf` instead of constructors for boxed classes.
| * 157add3 Adapt the codebase to changes in nio Buffers in Java 9.
| * 7e8433b Allow to load the build on JDK 9.
|/
*   02e3830 Merge pull request #3136 from MikaelMayer/fix-group-regex
|\
| * 4aecb56 Fix #3134: Make regex.Matcher report correct group positions.
|/
*   9b4de23 (origin/0.6.x, 0.6.x) Merge pull request #3149 from sjrd/fix-test-suite-on-node-js-8
|\
| * 4b42ad7 (origin/fix-test-suite-on-node-js-8) Fix #3148: Make our test suite pass on Node.js 8.
|/
*   31a51c0 Merge pull request #3131 from sjrd/review-stringbuilder-stringbuffer
|\
| * a487545 (origin/review-stringbuilder-stringbuffer) Rewrite and complete j.l.String{Builder,Buffer}.
|/
*   f82f4ac Merge pull request #3137 from sjrd/fix-relative-source-maps
|\
| * 4d8f39a [no-master] Fix #3135: Relativize source map URIs against the .js file.
* 4204fcb Merge pull request #3138 from sjrd/further-reduce-test-suite-on-phantomjs
* e722745 [no-master] Further reduce the pressure on PhantomJS in the test suite.

$ git merge -s ours f82f4ac
Merge made by the 'ours' strategy.

$ git show --stat
commit a194f1821672973230d5255f3f8059a54147197c
Merge: 56125c1 f82f4ac
Author: Sébastien Doeraene<EMAIL_ADDRESS>Date:   Mon Oct 16 13:01:47 2017 +0200

    Skip the [no-master] commits 4d8f39a and e722745.

$ export mb=$(git merge-base scalajs/0.6.x HEAD)

$ git log --graph --oneline --decorate $mb..scalajs/0.6.x | cat
*   d47c20c (scalajs/0.6.x) Merge pull request #3151 from sjrd/build-on-jdk9
|\
| * e285985 (origin/build-on-jdk9, build-on-jdk9) Work around #3152: disable Scaladoc generation for `library` on JDK 9.
| * 16c7866 Forward the system property `scala.ext.dirs` in `ExternalCompile`.
| * 9ebbf6d Do not call `super.finalize()` because it is deprecated in JDK 9.
| * 98973d4 Correctly setup `apiMappings` on JDK 9.
| * bfb4b16 Add new overloads of existing methods of Math in Java 9.
| * 41544fc Use `valueOf` instead of constructors for boxed classes.
| * 157add3 Adapt the codebase to changes in nio Buffers in Java 9.
| * 7e8433b Allow to load the build on JDK 9.
|/
*   02e3830 Merge pull request #3136 from MikaelMayer/fix-group-regex
|\
| * 4aecb56 Fix #3134: Make regex.Matcher report correct group positions.
|/
*   9b4de23 (origin/0.6.x, 0.6.x) Merge pull request #3149 from sjrd/fix-test-suite-on-node-js-8
|\
| * 4b42ad7 (origin/fix-test-suite-on-node-js-8) Fix #3148: Make our test suite pass on Node.js 8.
|/
* 31a51c0 Merge pull request #3131 from sjrd/review-stringbuilder-stringbuffer
* a487545 (origin/review-stringbuilder-stringbuffer) Rewrite and complete j.l.String{Builder,Buffer}.

$ git merge --no-commit scalajs/0.6.x
Auto-merging tools/shared/src/main/scala/org/scalajs/core/tools/io/IRFileCache.scala
Auto-merging project/build.sbt
Auto-merging project/JavaLangString.scala
Auto-merging project/JavaLangObject.scala
Auto-merging project/ExternalCompile.scala
Auto-merging project/Build.scala
CONFLICT (content): Merge conflict in project/Build.scala
Auto-merging library/src/main/scala/scala/scalajs/runtime/RuntimeString.scala
CONFLICT (modify/delete): library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala deleted in HEAD and modified in scalajs/0.6.x. Version scalajs/0.6.x of library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala left in tree.
CONFLICT (modify/delete): library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala deleted in HEAD and modified in scalajs/0.6.x. Version scalajs/0.6.x of library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala left in tree.
CONFLICT (modify/delete): library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala deleted in HEAD and modified in scalajs/0.6.x. Version scalajs/0.6.x of library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala left in tree.
Auto-merging javalanglib/src/main/scala/java/lang/Character.scala
Auto-merging ci/checksizes.sh
CONFLICT (content): Merge conflict in ci/checksizes.sh
Auto-merging build.sbt
Automatic merge failed; fix conflicts and then commit the result.

$ git st
M  build.sbt
UU ci/checksizes.sh
M  javalanglib/src/main/scala/java/lang/Character.scala
M  javalanglib/src/main/scala/java/lang/Math.scala
M  javalanglib/src/main/scala/java/lang/StringBuffer.scala
M  javalanglib/src/main/scala/java/lang/StringBuilder.scala
M  javalib/src/main/scala/java/io/InputStreamReader.scala
M  javalib/src/main/scala/java/io/OutputStreamWriter.scala
M  javalib/src/main/scala/java/io/Reader.scala
M  javalib/src/main/scala/java/nio/Buffer.scala
M  javalib/src/main/scala/java/nio/ByteBuffer.scala
M  javalib/src/main/scala/java/nio/CharBuffer.scala
M  javalib/src/main/scala/java/nio/DataViewCharBuffer.scala
M  javalib/src/main/scala/java/nio/DoubleBuffer.scala
M  javalib/src/main/scala/java/nio/FloatBuffer.scala
M  javalib/src/main/scala/java/nio/GenDataViewBuffer.scala
M  javalib/src/main/scala/java/nio/GenHeapBufferView.scala
M  javalib/src/main/scala/java/nio/GenTypedArrayBuffer.scala
M  javalib/src/main/scala/java/nio/HeapByteBufferCharView.scala
M  javalib/src/main/scala/java/nio/HeapCharBuffer.scala
M  javalib/src/main/scala/java/nio/IntBuffer.scala
M  javalib/src/main/scala/java/nio/LongBuffer.scala
M  javalib/src/main/scala/java/nio/ShortBuffer.scala
M  javalib/src/main/scala/java/nio/StringCharBuffer.scala
M  javalib/src/main/scala/java/nio/TypedArrayByteBuffer.scala
M  javalib/src/main/scala/java/nio/TypedArrayCharBuffer.scala
M  javalib/src/main/scala/java/nio/charset/CharsetDecoder.scala
M  javalib/src/main/scala/java/nio/charset/CharsetEncoder.scala
M  javalib/src/main/scala/java/util/Throwables.scala
A  javalib/src/main/scala/java/util/regex/GroupStartMap.scala
M  javalib/src/main/scala/java/util/regex/Matcher.scala
M  junit-runtime/src/main/scala/org/junit/internal/ArrayComparisonFailure.scala
M  library/src/main/scala/scala/scalajs/niocharset/ISO_8859_1_And_US_ASCII_Common.scala
M  library/src/main/scala/scala/scalajs/niocharset/UTF_16_Common.scala
M  library/src/main/scala/scala/scalajs/niocharset/UTF_8.scala
DU library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala
DU library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala
DU library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala
M  library/src/main/scala/scala/scalajs/runtime/RuntimeString.scala
M  project/BinaryIncompatibilities.scala
UU project/Build.scala
M  project/ExternalCompile.scala
M  project/JavaLangObject.scala
M  project/JavaLangString.scala
M  project/build.sbt
M  project/project/ScalaJSEnvGenerator.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/javalib/lang/StringBufferTest.scala
A  test-suite/shared/src/test/scala/org/scalajs/testsuite/javalib/lang/StringBuilderTest.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/javalib/lang/StringTest.scala
A  test-suite/shared/src/test/scala/org/scalajs/testsuite/javalib/lang/WrappedStringCharSequence.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/javalib/util/regex/RegexMatcherTest.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/niobuffer/BaseBufferTest.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/niobuffer/BufferAdapter.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/niobuffer/BufferFactory.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/niobuffer/ByteBufferTest.scala
M  test-suite/shared/src/test/scala/org/scalajs/testsuite/niocharset/UTF16Test.scala
M  tools/shared/src/main/scala/org/scalajs/core/tools/io/IRFileCache.scala

$ git rm -f library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala
library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala: needs merge
library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala: needs merge
library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala: needs merge
rm 'library/src/main/scala/scala/scalajs/runtime/BooleanReflectiveCall.scala'
rm 'library/src/main/scala/scala/scalajs/runtime/LongReflectiveCall.scala'
rm 'library/src/main/scala/scala/scalajs/runtime/NumberReflectiveCall.scala'

[...] edit conflicting files
$ git diff
diff --cc ci/checksizes.sh
index 15f3366,fa1e2fb..0000000
--- a/ci/checksizes.sh
+++ b/ci/checksizes.sh
diff --cc project/Build.scala
index 36734a8,459b7ed..0000000
--- a/project/Build.scala
+++ b/project/Build.scala
@@@ -1,4 -1,7 +1,6 @@@
+ package build
+
 -import sbt._
 -import Keys._
 +import scala.language.implicitConversions

  import scala.annotation.tailrec

$ git add -u

$ git commit
[merge-0.6.x-into-master-october-16 882e13b] Merge '0.6.x' into 'master'.

checksizes.sh will likely fail at first, since I removed the changes done on the 0.6.x branch, to see the exact effect on the master branch.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4308/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5781/
Test FAILed.

OMG, the failures are scary (linking error in the test suite), but the cause of those failures--and why they were not spotted in 0.6.x--are even scarier.
We got this:
[info] Fast optimizing /localhome/jenkins/a/workspace/scalajs-task-worker/test-suite/js/target/scala-2.10/scalajs-test-suite-test-fastopt.js
[error] Referring to non-existent method java.lang.AssertionError.<init>(java.lang.String,java.lang.Throwable)
[error]   called from org.junit.internal.ArrayComparisonFailure.<init>(java.lang.String,java.lang.AssertionError,scala.Int)
...

Sure enough, there is no overload with (String, Throwable) in our implementation of AssertionError. This is not very surprising, as it was introduced in JDK 7, according to the JavaDoc.
But then why did it link in 0.6.x? Well, that's because in 0.6.x we still had the linking-time hack to synthesize missing constructors from their parent (because we used not to generate "trivial" constructors). The hack was removed in 1.x, causing the linking error.
There is a bigger mystery, however: how on earth did it even compile in the JDK 6 builds on the CI? Well, it turns out AssertionError has an overloaded taking an Object, i.e., an Any. Guess what does scalac do if you call a method with 2 arguments that only accept 1 argument? Auto-tupling! So when building on JDK 6, we're not even calling the correct constructor :scream:.
We cannot fix this in any reasonable way in the merge of this PR. We need to fix it in 0.6.x first, then re-do the merge on top of that.

Updated after #3156.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4310/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5784/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/4311/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5785/
Test PASSed.


Idea to improve "clickability" using dead drawablePadding space

I've experimented some hard times clicking when the drawable is small. One simple but not elegant solution is to use bigger drawables or include empty margins in the drawable.
I think that checking only for inner X border is smart, but could be even better by adding some extra space.
My first simple approach was to add an offset to the border. I used a relative value, but it could be done with an absolute value too:
private static double boundsXExtension = 1.5f; //It could be an xml attribute
// Then inside onTouchEvent()
 if ((leftToRight && (x >= (this.getRight() - (int)(boundsXExtension*bounds.width())))) ||
                    (!leftToRight &&  (x <= (this.getLeft() + (int)(boundsXExtension*bounds.width()))))){

Then i came up with a probably more elegant solution; which is taking advantage of the "drawablePadding" attribute. Its pixel value is accesible via getCompoundDrawablePadding(). This solution feels quite nice since it is adding some user value to an empty space that i guess everyone is using!
if ((leftToRight && (x >= (this.getRight() - (bounds.width()+getCompoundDrawablePadding())))) ||
                    (!leftToRight &&  (x <= (this.getLeft() + (bounds.width()+getCompoundDrawablePadding())))))

Hey @guillermomuntaner thanks for suggesting this, I played with using getCompoundDrawablePadding() but it didn't give me the results I was looking for it was often very high and couldn't figure out why. So i've opted for an additionalTouchTargetSize attribute that you can pass a resource size to and that'll increase the clickability. This is in 0.7


Custom identifiers for tRFs

I got a list of tRF identifiers from miRge3.0 (e.g. Arg_Comb_44 and SeC_Comb_1). Do you know where I can find information regarding these tRFs, and additionally, if there is a method to link these custom identifiers to known genomic coordinates or sequences? Thank you!

Awesome. Thank you!


Report from publicapis.dev

Name: Age of Empires II
Category: Games & Comics
Issue: Broken link
This report was sent from publicapis.dev.

Heroku app is either offline or it has been deleted.

Removed, thanks.


Add future in branch protection

/build-and-push-container

/build-and-push-container

/build-and-push-container

/build-and-push-container

/build-and-push-container


String#start_with? and #end_with? for empty string

Expanded specs to also cover testing if the empty string starts or ends with the empty string.
And aligned the two specs to look more alike.
JRuby used to differ from other implementations on this.
See https://github.com/jruby/jruby/issues/2434

Looks great, thanks for you contribution!


Implement IP address extraction functionality using regular expressions

Issue Description
In many web applications, there is a common requirement to extract IP addresses from text. This issue is to add IP address extraction functionality to our Regex Pro project, which allows users to work with regular expressions.
Task
Your task is to implement IP address extraction using regular expressions. Here are the requirements for this task:

Implement the regular expression pattern to extract IP addresses from the input text.
Add the regular expression pattern in the extractionForms in pages.js.

Additional Information

You can refer to the existing extraction forms as examples.
The regular expression pattern for IP address extraction should cover common IPv4 and, if needed, IPv6 address formats.
You may find resources online to help with regular expressions for IP address extraction.

Getting Started

Fork this repository to your GitHub account.
Create a new branch for this task.
Implement the changes as described.
Commit your changes and push them to your fork.
Open a pull request to this repository.

Additional Notes

This is a "Good First Issue" suitable for contributors who are new to the project and want to get involved.
Please reach out if you have any questions or need assistance with the task.

We look forward to your contribution! 😄

Assign me this issue. I will look into it.

Best of Luck 👍

Fixed by PR https://github.com/hammadsaedi/regex-pro/pull/18


The content type for PING API is not set - resulting in browsers wanting to save instead of display the data

Hitting the export client PING API (<IP_ADDRESS>:48071/api/v1/ping) results in the browser asking if you want to save the response versus just display it.  Check the content type returned - and see how core data does this.

You can assign it to me.


retrieve & analyze final count of records accepted by IPCC

confirm this statement: "The discrepancy between the number of records sent and that posted to EFDB is primarily attributable to the time required for the IPCC to review the records, and it is not expected that many -- if any -- records will be rejected."

Two statements will need to change:

[ ] Complete records needed to be reviewed by the EFDB editorial board and then posted in the database -- a process that lags behind submission of records and had not yet been completed for all records sent as of r format(Sys.time(), '%B %d, %Y').
[ ] ...

This does not need to be resolved before sending for review. I have made the necessary edits such that the manuscript is accurate. When EFDB posts the latest data, I will update the manuscript accordingly (assuming this happens before publication).

Done!


Fluid duplication bug via Fluid Tanks + Buckets

In version <IP_ADDRESS>7 it is possible to duplicate fluids using a Fluid tank.
[REDACTED]

i can't seem to do that using both the normal tank and the pressurized with same version with forge 1286 however i found something interesting if you set it to push on any side you cannot use bucket on that tank to fill it and vice-verse and if you set it to disable you no longer can fill it up or take liquids from it i don't know if this is a bug or intended but it's kinda cool

Fixed in @MatthiasMann's PR. Sensitive info redacted.


"bower unregister" -> feature or bug?

Nothing seems to work at the moment:
$ curl -X DELETE "https://bower.herokuapp.com/packages/exports-boilerplate?access_token=xxxx"
Must be a collaborator on GitHub.com repository

$ bower unregister exports-boilerplate
bower EFORBIDDEN    Use "bower login" with collaborator credentials

"bower login" wants my git credentials?? No!
I am using bower version 1.5.2. How to delete a package with this?

My access token is limited to the following scope:
repo, repo:status and user
Is there anything missing?

exports-boilerplate is registered to github.com/leolux/exports-boiplerplate and it doesn't exist ;/ You need to create this repository, remove package from bower, and remove repository

Alright, thanks!
So I would suggest to add this to the error message "The repository needs to exist in order for the unregistration to work"

Yeah ;/ We need to improve it. I'll add an issue


open notebooks working for titanic plus remove button removed for all

merge with added button and details with the all option


Q

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version:
Python version:
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
Provide the exact sequence of commands / steps that you executed before running into the problem
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached...

@mouse36872 Please go through the contributing guidelines at https://www.tensorflow.org/community/contribute.


nnstreamer/apptest: Improve readability of apptest facility

Fixed issue https://github.com/nnsuite/nnstreamer/issues/905.
This commit is to improve an entire code flow of the existing apptest facility
for maintenance and readability.
Changes proposed in this PR:

Added annotations additionally for maintenance
Updated the existing statements for readability
Refactored the variables and function name

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>

:memo: Version: 1.20181123. Thank you for submitting PR #432. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/TAOS-CI/ci/taos/.


Fix spelling errors and typos flagged by CodeSpell.

Signed-off-by: Shaun Case<EMAIL_ADDRESS>Description
Fixed spelling and typographical errors found by CodeSpell.  See https://github.com/codespell-project/codespell
Status
READY
Requires Backporting
NO
Migrations
NO

Thanks for the contribution!
Could you please rebase - removing the merge commit, and the duplicate Signed-off-by in the commit message.

I made a mistake and removed the commit that had the changes.  I'll redo it and open a new PR.


Time of test

How long it take if I just run the test.py by using the Trained weights in the Google Drive? Thank you for your time

It depends on your machine. We've reported the test time in our paper. Please check it.

Sorry, I can't find the test time in ECCV paper. Would you please point out which part includes the test time?

It is near the end of Section 4.1.


Searching end points

In order to get the cards of #27 we need to read the data from the local storage.
At least we need to endpoints:

One to read some recents cards went tags filter is empty.
Read some data went with tags restriction.

Some interesting sources that can be used:

SQLite order by
Patter machine

We need to process multiple tags