1.3.0 broken and 2.0 not available on npm

Please yank 1.3.0 since it overwrites package.json - my CI started failing because of this today
The README now contains instructions that don't work. Perhaps 2.0 needs to be published, but either way it might be a good idea to either move 2.0 instructions to a branch until it's published or make a note that the instructions are for an unreleased version

Was able to install it at least by setting up an .npmrc file:
//npm.pkg.github.com/:_authToken=<your personal access token>
@danielbayley:registry=https://npm.pkg.github.com

And then installing with:
npm install @danielbayley/jest-preset-coffeescript

But I am still unable to get it to work when I add the "jest" piece to the package.json

@jaredmoody @unscene Sorry, things have been a bit chaotic recently…
I wanted to release a quick update in response to #35. Initially it seemed like a simple version bump to Jest, but it turned out they altered an upstream config option which broke this package, and forced me to quickly rewrite how it works (See https://github.com/facebook/jest/pull/9495#issuecomment-607566969).
Since the CI was passing, I pushed those changes, which was a mistake. Also, I didn't realise GitHub Packages were now immutable, as the last time I tested them was during the beta period, before this was the case.
Anyway, I'll fix this ASAP and post an update, including to npm… Although I want to migrate solely to GitHub Packages in future.

● Validation Error:

  Module /Users/Dan/Work/dev/npm/jest-preset-coffeescript in the setupFilesAfterEnv option was not found.
         <rootDir> is: /Users/roc58/myCode/pug-cli

  Configuration Documentation:
  https://jestjs.io/docs/configuration.html

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/roc58/.npm/_logs/2020-07-05T23_58_40_125Z-debug.log
The terminal process terminated with exit code: 1

I have this error when using the version in the github packages, but this error does not happen when installing directly from GitHub npm i https://github.com/danielbayley/jest-preset-coffeescript.

My CI also started failing and tracked it down to this. After many failed attempts to use the Github package (very hard to use with yarn, it seems), I tried yarn add https://github.com/danielbayley/jest-preset-coffeescript and then running jest. Unfortunately, this still causes the problem of clobbering package.json (#45). Is the fixed version not on Github? I don't see any commits that would fix it.

@edemaine This has been resolved here https://github.com/danielbayley/jest-preset-coffeescript/commit/07038d633a3e88d4c63e8608439f35741f6e97d7.

The README now contains instructions that don't work.

@jaredmoody @weotch @unscene @jacekk @Nevon @fcostarodrigo They clearly assume you already have npm configured to work with GitHub Packages:

Assuming you already have npm configured to work with GitHub Packages:

apart from the steps specific to this package:

npm config set @danielbayley:registry https://npm.pkg.github.com

But I have clarified a few things in the README just now, along with a couple of other fixes… please see latest release. Sorry for the delay! Everything should be working now, but please test… thanks! 👍

It seems that the new version still isn't on NPM: https://www.npmjs.com/package/jest-preset-coffeescript doesn't list it (perhaps because of the deprecation notice?) and npm install jest-preset-coffeescript@2 doesn't work.
Also, version 1.3.0 has not been pulled from NPM; I just got my package.json clobbered when running npm install (depending on version ^1.1.1 which auto-upgraded).

I am using my own solution now. Just published in case it is useful for someone else as well.
https://www.npmjs.com/package/coffeescript-jest-preset
About the package not being on npm, the author is publishing the package on github, so you have to configure npm to get the package from github.


Issue regarding navigation to next challenge from current challenge

Hi team ,
I am facing trouble while navigation from one challenge to next challenge. It is showing error while I move to next challenge after completion of the current challenge successfully.
I am attaching screenshot also.
Please help.

Regards,
Surender

Duplicate of #6958


Remove Atmospheric Retrieval Support

Deleting all files, docs and tests associated with atmospheric retrievals.

Hello @mfixstsci, Thank you for submitting the Pull Request !

In the file exoctk/exoctk_app/app_exoctk.py:

Line 20:1: E265 block comment should start with '# '
Line 391:1: W293 blank line contains whitespace
Line 761:21: W605 invalid escape sequence '('
Line 761:25: W605 invalid escape sequence ')'
Line 761:57: W605 invalid escape sequence '\c'
Line 761:74: W605 invalid escape sequence '\e'
Line 767:46: W605 invalid escape sequence '('
Line 767:48: W605 invalid escape sequence '\l'
Line 767:56: W605 invalid escape sequence '\m'
Line 767:66: W605 invalid escape sequence '\h'
Line 767:79: W605 invalid escape sequence '\m'
Line 767:85: W605 invalid escape sequence ')'
Line 768:46: W605 invalid escape sequence '('
Line 768:48: W605 invalid escape sequence '\l'
Line 768:56: W605 invalid escape sequence '\m'
Line 768:66: W605 invalid escape sequence '\h'
Line 768:79: W605 invalid escape sequence '\m'
Line 768:85: W605 invalid escape sequence ')'
Line 769:46: W605 invalid escape sequence '('
Line 769:48: W605 invalid escape sequence '\l'
Line 769:56: W605 invalid escape sequence '\m'
Line 769:66: W605 invalid escape sequence '\h'
Line 769:79: W605 invalid escape sequence '\m'
Line 769:85: W605 invalid escape sequence ')'
Line 775:58: W605 invalid escape sequence '('
Line 775:62: W605 invalid escape sequence '\m'
Line 775:69: W605 invalid escape sequence '\m'
Line 775:75: W605 invalid escape sequence ')'
Line 800:25: W605 invalid escape sequence '('
Line 800:29: W605 invalid escape sequence ')'
Line 800:61: W605 invalid escape sequence '\c'
Line 800:78: W605 invalid escape sequence '\e'
Line 806:50: W605 invalid escape sequence '('
Line 806:52: W605 invalid escape sequence '\l'
Line 806:60: W605 invalid escape sequence '\m'
Line 806:70: W605 invalid escape sequence '\h'
Line 806:83: W605 invalid escape sequence '\m'
Line 806:89: W605 invalid escape sequence ')'
Line 807:50: W605 invalid escape sequence '('
Line 807:52: W605 invalid escape sequence '\l'
Line 807:60: W605 invalid escape sequence '\m'
Line 807:70: W605 invalid escape sequence '\h'
Line 807:83: W605 invalid escape sequence '\m'
Line 807:89: W605 invalid escape sequence ')'
Line 808:50: W605 invalid escape sequence '('
Line 808:52: W605 invalid escape sequence '\l'
Line 808:60: W605 invalid escape sequence '\m'
Line 808:70: W605 invalid escape sequence '\h'
Line 808:83: W605 invalid escape sequence '\m'
Line 808:89: W605 invalid escape sequence ')'
Line 814:62: W605 invalid escape sequence '('
Line 814:66: W605 invalid escape sequence '\m'
Line 814:73: W605 invalid escape sequence '\m'
Line 814:79: W605 invalid escape sequence ')'

If you have not done so, please consult PEP8 and PEP257

@nespinoza @hover2pi this is a first pass. Hopefully we catch everything. I am going to fire up the app locally and see what it looks like.

Looks good to me 🤷 let me know if I missed anything.

Suggestion from the meeting today: now that this is going to be merged, test this in tlexoctk1 to triple check everything looks good.


ArrayUtils::inArray should use strict in_array?

Related: https://github.com/zendframework/zend-form/issues/18
In Zend\Form\View\Helper\FormSelect ArrayUtils::inArray is called with the strict parameter false.  This causes an issue with string matching ('1.1' and '1.10' treated equivalent):
<?php
$needle = '1.10';
$haystack = ['1.1'];

assert(in_array($needle, $haystack) === false);
// PHP Warning:  assert(): Assertion failed in <file> on line 5

(3v4l: https://3v4l.org/HKM8Q)
Simply changing FormSelect to use strict=true breaks an existing test which uses integer keys in the value options array.
Since ArrayUtils::inArray uses string casting to work around in_array's wonky non-strict behaviour, shouldn't the call to in_array always have strict=true?
diff --git a/src/ArrayUtils.php b/src/ArrayUtils.php
index 17e3ae3..69b9721 100644
--- a/src/ArrayUtils.php
+++ b/src/ArrayUtils.php
@@ -199,7 +199,7 @@ abstract class ArrayUtils
                 }
             }
         }
-        return in_array($needle, $haystack, $strict);
+        return in_array($needle, $haystack, true);
     }

     /**

I've tested this change here (all tests pass) and against zend-form (where it fixes the reported issue).
What's the protocol for testing changes to packages which may have knock-on effects on other packages?  Pull every repo that has a dependency on stdlib, apply the patch, and run the tests?

@adamlundrigan would everything be ok if you passed true to $strict?

@Ocramius

Simply changing FormSelect to use strict=true breaks an existing test which uses integer keys in the value options array.

I should have included a link to the source there for context.  If I simply change this line to add true for $strict then I get a failure in this test case which uses integer keys for the value options because it's strictly searching for "string 0" in an array that contains "int 0".

@Ocramius inArray is not covered by tests.

I'll do the logical question. Why not
<?php
$needle = '1.10';
$haystack = ['1.1'];

assert(in_array($needle, $haystack, **true**) === false);
// PHP Warning:  assert(): Assertion failed in <file> on line 5

That's exactly what I propose in my fix:
@@ -199,7 +199,7 @@ public static function inArray($needle, array $haystack, $strict = false)
                 }
             }
         }
-        return in_array($needle, $haystack, $strict);
+        return in_array($needle, $haystack, true);
     }

     /**

https://github.com/zendframework/zend-stdlib/pull/42/files#diff-8682a0029f402e6271c8db9da92088f6L202

Sorry I wrote wrong the example. I've edited

Marco asked same question above: https://github.com/zendframework/zend-stdlib/issues/41#issuecomment-151625729
It breaks an existing test in FormSelect.  The value_options array for Select can contain integer keys, which are converted to string when rendered by FormSelect.  With a strict check alone that will fail since the haystack has "int 0" but the form data has "string 0".  The only workaround that works for both cases is to pass "false" to ArrayUtils::inArray (so it casts everything to strings) but pass "true" to in_array to get strict matching.  That's what the code in my PR does.

Sorry I'm not able to understand why ArrayUtils::inArray($needle, $haystack, **true**) fail but ArrayUtils::inArray($needle, $haystack, false) { return in_array($needle, $haystack, **true**); }  works.
I've missing something in your answer.

ArrayUtils::inArray will cast everything to string when it's $strict argument is false:
    /**
     * Checks if a value exists in an array.
     *
     * Due to "foo" == 0 === TRUE with in_array when strict = false, an option
     * has been added to prevent this. When $strict = 0/false, the most secure
     * non-strict check is implemented. if $strict = -1, the default in_array
     * non-strict behaviour is used.
     *
     * @param mixed $needle
     * @param array $haystack
     * @param int|bool $strict
     * @return bool
     */
    public static function inArray($needle, array $haystack, $strict = false)
    {
        if (!$strict) {
            if (is_int($needle) || is_float($needle)) {
                $needle = (string) $needle;
            }
            if (is_string($needle)) {
                foreach ($haystack as &$h) {
                    if (is_int($h) || is_float($h)) {
                        $h = (string) $h;
                    }
                }
            }
        }
        return in_array($needle, $haystack, $strict);
    }

We need that, or else FormSelect will blow up if you set value_options with integer keys, like this:
        $element = new SelectElement('foo');
        $element->setValueOptions([
            0 => 'label0',
            1 => 'label1',
        ]);

        // Pretend this value came from POST and we're re-displaying the form
        $element->setValue("0");

That's a valid use case.  FormSelect view helper will take that and output something like this:
<!-- snip -->
<option value="0" selected="selected">label0</option>
<option value="1" selected="selected">label1</option>
<!-- / snip -->

The types don't match so ArrayUtils::inArray($n, $h, true) won't work there.  ArrayUtils::inArray($n, $h, false) fixes this case by casting everything to string before chucking it into in_array.
However, PHP has another thing we need to work around:
var_dump('1.1' == '1.10');
// bool(true)

https://3v4l.org/QRkkA
Which means that ArrayUtils::inArray($n, $h, false) won't work for this case:
        $element = new SelectElement('foo');
        $element->setValueOptions([
            '1.1' => 'label 1.1',
            '1.10' => 'label 1.10',
            '1.2' => 'label 1.2',
            '1.20' => 'label 1.20',
        ]);

        // Pretend this value came from POST and we're re-displaying the form
        $element->setValue("1.1");

We'll end up with both "1.1" and "1.10" selected when we render to HTML because in PHP's bizarro world "1.1" == "1.10".
Basically, we need a check that's strict on value (so "1.1" != "1.10") but not strict type (so "int 0" == "string 0"), and that's what sending true into in_array's $strict regardless of the value provided to ArrayUtils::inArray's $strict is doing.  It's making sure in_array does a strict check but casting everything to string first so types aren't an issue.

I understand the issue now.
Well, I see inArray has three responsibilities, 1. wrap in_array; 2. transform needle; 3. transform haystack.
My (abstract) proposal:

Refactor needle transformation as method.
Refactor haystack transformation as method.
Deprecate inArray in favor of :

 in_array(
   ArrayUtils::needleTransform($needle),
   ArrayUtils::haystackTransform($haystack),
   $strict
 );

I think it could be distilled down to a single generic "recursively cast array keys and non-array values to string" which would cover both the needle and haystack transforms.  castKeysAndValuesToString is long but leaves no ambiguity of purpose.
Regardless, it doesn't feel like the right solution.  The intention of ArrayUtils::inArray was to work around the wonky behaviour of non-strict in_array, but it's not doing that job completely in it's current state.

This repository has been closed and moved to laminas/laminas-stdlib; a new issue has been opened at https://github.com/laminas/laminas-stdlib/issues/5.


⚠ Bofrost.be has degraded performance

In bda3686, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1341 ms

Resolved: Bofrost.be performance has improved in 08e41c1 after 53 minutes.


[WIP] Add UI for generating authorization keys for remote regions

Add UI for generating authorization keys for remote regions
Links [Optional]
Steps for Testing/QA [Optional]

@miq-bot add_label wip, ui, enhancement

@miq-bot  remove_label wip

@carbonin - added the default value for ssh_host from the region's remote_ws_address - please review
/cc @dclarizio

Euwe Backport details:
$ git log
commit 678a241c327ba500b365cc871b0ded625ab4cc10
Author: Dan Clarizio<EMAIL_ADDRESS>Date:   Thu Oct 13 05:00:11 2016 -0700

    Merge pull request #11646 from lgalis/user_region_authentication_key_ui

    Add UI for generating authorization keys for remote regions
    (cherry picked from commit 099cf972b168ad709fc84d81989cd8ecc3a6a687)


Fix error message

rechunk is not a methode of DataArray or Dataset, chunk does rechunk.

Thanks!


add generator docs

Okay added some docs for generators. I wasn't sure what markdown:

is being referred to here. I don't have that lib installed. But here are some docs. They'll need to be rebuilt.

Something about how this works via the .then function would help folks if they run into issues.

LGTM. Should be OK to merge. No release needed.

@olalonde @pornel another one we should be able to quickly review and merge.

Thanks


:package: Chore: Productionize server package

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1192  👈
#1191
#1190
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


chore: inline benchmarks from tommilligan/rust-pretty-assertions-bench

Inline benchmarking code to the cargo workspace from https://github.com/tommilligan/rust-pretty-assertions-bench

Codecov Report

Merging #76 (707af6f) into main (7e339cf) will decrease coverage by 2.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
- Coverage   98.96%   96.95%   -2.01%
==========================================
  Files           2        3       +1
  Lines         193      197       +4
==========================================
  Hits          191      191
- Misses          2        6       +4

Impacted Files
Coverage Δ

...assertions_bench/benches/benchmarks/pretty_diff.rs
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Unhandled promise in message.ack() makes it hard for a terminating script to wait for ack

Environment details

@google-cloud/pubsub version: 2.10.0

Steps to reproduce
const pubsub = new PubSub();
const subscription = pubsub.subscription(subscriptionName);
subscription.on('message', (m: Message) => {
  const dataUtf8encoded = m.data.toString('utf8');
  let event: unknown;
  try {
    event = JSON.parse(dataUtf8encoded);
  } catch (ex) {
    m.ack();
    console.log('Fail!');
    // ISSUE: the process will exit before the ack has been sent
    process.exit(1);
  }
  doSomethingWith(event);
  m.ack();
});

See the comment line starting with // ISSUE:  in the code above. An unexpected message will in this case not be cleared from the subscription. If my process would restart automatically, it would be in an infinite loop now. The problem is that m.ack() does not return a promise (while the underlying subscriber ack function does). That seems to be a problem for others as well, see:

https://github.com/googleapis/nodejs-pubsub/pull/428
https://github.com/googleapis/nodejs-pubsub/issues/575

I read in  https://github.com/googleapis/nodejs-pubsub/pull/428:

Unfortunately this isn't the first time this request has been made, but we've had some push back from the PubSub API team in the past.

I cannot find that push back discussion. If there's a good reason not to return a promise, an alternative would be to make _waitForFlush a public method. That I can await that before exiting the process.
ps. I can of course set an arbitrary timeout before exiting the process, but that's ugly.

I would like an option to flush the acks and to be able to see a trace if there is a rejection there. Recently we run into the situation where we had to debug some occasional unhandled promise rejections, and we had to patch the ack/nack functions to use the underlying functions to be able to rule it out as the source.

That's pretty gross, yeah. I feel like this is probably related to this, work wise:
https://github.com/googleapis/nodejs-pubsub/issues/725
I'm going to add this issue to the internal backlog for that work.


Using a symlink for ".continuerc.json" does not work

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
No response
Description
I tried setting up the file .continuerc.json at the root level of my project by means of a symlink to a config file in a subdirectory. This doesn't seem to work. The configuration in that file is not applied.
I cross checked and it seems to work as soon as I directly put the configuration in the file as opposed to creating a symlink.
I think the following code part probably will need adapting:
https://github.com/continuedev/continue/blob/54c24fd8e0213d377b58b1a6cdce451d03172ee5/extensions/vscode/src/ideProtocol.ts#L317
To reproduce
No response
Log output
No response

Fixed here, thanks for finding the line!

Fixed here, thanks for finding the line!

Thanks for the swift fix!

@sestinj I just checked if the issue is resolved in v0.9.205 (which should include this fix) but it is still not working for me. The models that I define in my .continuerc.json don't show up in VSCode.
Apparently the line I mentioned wasn't sufficent to resolve this. Could you reopen this issue?
I sadly have neither VSCode extension nor TypeScript experience, so I don't quite have the capability to debug this extension locally.


Enhancement - Nether customization

This is just a suggestion for a future release maybe to be combined with the upcoming 16 release.
Customization of Dangerous Caves to add more depth to the nether. This can be done by taking current mobs and structures and doing some hopefully small rewrites (and possibly a config just for the nether Or a new plugin maybe even make it a new paid plugin to help you out for your hard work(I'd gladly pay for it))
Aging:
_- Structures could change from wooden and random stone to Netherrack and other newly introduced stone types.

Randomly spawned traps could remain the same.
Cave growth could be set at a much slower rate and include a % change to age Netherrack and quartz to Obsidian(25%), Coal Ore(25%), Diamond Ore(rare 15%), and the new Netherrite(extremely rare 5%). Other considerations could be added for aging including cobwebs etc.
Keep cave growth of stalagmites and stalactites as is with a chance of using Glowstone or mushroom lights for special effects. Again factor in rarity.
Chest spawning could now include a higher rate of food spawning.
Chest types could also include a 30% chance of trapped chest type meaning the risk factor has increased.
The Nether ould not include the variable for how hot it is as the nether is always going to be very hot._

Mobs:
_- Randomly spawned spawners could offer instead of silverfish, wither skeletons or Piglins.

Nether Ghost(customized to mimic the current Smoke Deamon with particle effect change)
Baby Ghast (Smaller faster ghast that are more of a pain and travel in groups of 2 or 3, They do not shoot fireballs but can explode)
Nether Miner (similar to Dead Miner, only drops nether materials and a % chance of Netherite or diamond armor drops)
Keeping Magma Monster and TNT Creeper As they fit well in the Nether
And finally, introduce 2 new mobs that are designed to envoke a dark sinister side these mobs would have higher hit points and attacks that are specific to the Nether such as Lava attack or Fire throw in a circle(used to encircle the player to prevent escaping)_

I know this seems like a lot which is why I also added the note of maybe a separate plugin. Possibly a paid plugin. Also, I have some other ideas but those would need to see what really comes with 16.
If you have questions or just want to know my why please feel free to ask.
Thanks for all your hard work to date, I cannot wait to see what the future holds.

I was frequently asked for a new plugin for nether *stuff*. Probably I'll start a new plugin called Dangerous Dimensions for the nether and the end gameplay changes. It's will be free, just because I don't want to mess with money.

If you decide to pursue the Dangerous Dimensions project and are looking for a tester or ideas please feel free to hit me up.  I would be more than will to test or suggest so long as you are welcome to the input. Also while I have ideas for the end I was not about to open my mouth on that as I figured I'd be pushing it with information/suggestion overflow.
I look forward to any plugins you make and will continue to endorse the use of this plugin as well as it is awesome and very well accepted by the players of the FreindlyWorldServer network.
Again thank you for all your hard work.
Respectfully
EchocallingEarth
(Owner FriendlyWorldServer Network)

If possible, maybe consider adding dangerous nether content to this plugin.

It's possible, but sorry, I'm not going to do that. I want to save DC as an addition for survival - not a whole new gameplay. Original Dangerous-nether has too many changes to the nether to fit it into the DC. As being said - I will just start a new project instead.

Locally started development. Further information in 2-3 weeks.

Sounds a bit like this plugin :D
https://www.spigotmc.org/resources/very-dangerous-nether.76333/


When installing docker-ce >= 18.09, should install / uninstall docker-ce-cli

Problem description

It seems that docker-ce-cli package has been separated after docker version 18.09.
If I install docker-ce through yum install command, docker-ce-cli package will be installed as a dependency but the latest version will be.
Therefore, installed docker-ce / docker-ce-cli package version can be different. It is not the desired situation for installer who wants to get the docker with specific version.
Problem location

I saw a problem on the following URL:

https://docs.docker.com/install/linux/docker-ce/centos/#uninstall-old-versions
https://docs.docker.com/install/linux/docker-ce/centos/#install-docker-ce-1

docker-ce-cli should be installed first before installing docker-ce package to get a specific version of docker.

to take that into account. -->
Suggestions for a fix

It is better to let document readers to know that if they want to get a docker package with specific version, you should uninstall docker-ce-cli, docker-ce and install docker-ce-cli, docker-ce in order.

I can also attest to this issue. I am trying to control my environment when installing docker, but I am unable to because of docker-ce-cli not honoring the version specified when installing docker-ce.
Below are several examples when installing on various vagrant boxes.
Ubuntu16
vagrant@u16:~$ apt list --installed | grep docker

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

vagrant@u16:~$ sudo apt-get install docker-ce=5:18.09.0*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '5:18.09.0~3-0~ubuntu-xenial' (Docker CE:xenial [amd64]) for 'docker-ce'
The following additional packages will be installed:
  aufs-tools cgroupfs-mount containerd.io docker-ce-cli libltdl7 pigz
Suggested packages:
  mountall
The following NEW packages will be installed:
  aufs-tools cgroupfs-mount containerd.io docker-ce docker-ce-cli libltdl7 pigz
0 upgraded, 7 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/50.4 MB of archives.
After this operation, 243 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package pigz.
(Reading database ... 55031 files and directories currently installed.)
Preparing to unpack .../pigz_2.3.1-2_amd64.deb ...
Unpacking pigz (2.3.1-2) ...
Selecting previously unselected package aufs-tools.
Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
Unpacking cgroupfs-mount (1.2) ...
Selecting previously unselected package containerd.io.
Preparing to unpack .../containerd.io_1.2.2-1_amd64.deb ...
Unpacking containerd.io (1.2.2-1) ...
Selecting previously unselected package libltdl7:amd64.
Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.6-0.1) ...
Selecting previously unselected package docker-ce-cli.
Preparing to unpack .../docker-ce-cli_5%3a18.09.1~3-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-ce-cli (5:18.09.1~3-0~ubuntu-xenial) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a18.09.0~3-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-ce (5:18.09.0~3-0~ubuntu-xenial) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu21.15) ...
Setting up pigz (2.3.1-2) ...
Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Setting up cgroupfs-mount (1.2) ...
Setting up containerd.io (1.2.2-1) ...
Setting up libltdl7:amd64 (2.4.6-0.1) ...
Setting up docker-ce-cli (5:18.09.1~3-0~ubuntu-xenial) ...
Setting up docker-ce (5:18.09.0~3-0~ubuntu-xenial) ...
update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
Processing triggers for libc-bin (2.23-0ubuntu10) ...

vagrant@u16:~$ docker --version
Docker version 18.09.1, build 4c52b90

vagrant@u16:~$ apt list --installed | grep docker

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

docker-ce/xenial,now 5:18.09.0~3-0~ubuntu-xenial amd64 [installed,upgradable to: 5:18.09.1~3-0~ubuntu-xenial]
docker-ce-cli/xenial,now 5:18.09.1~3-0~ubuntu-xenial amd64 [installed,automatic]

Fedora 28
[vagrant@fedora28 ~]$ sudo yum install docker-ce-3:18.09.0-3.*
Last metadata expiration check: 0:12:40 ago on Fri 08 Feb 2019 08:03:24 PM UTC.
Dependencies resolved.
==============================================================================================================================================================================================================================================
 Package                                                       Arch                                          Version                                                            Repository                                               Size
==============================================================================================================================================================================================================================================
Installing:
 docker-ce                                                     x86_64                                        3:18.09.0-3.fc28                                                   docker-ce-stable                                         19 M
Installing dependencies:
 container-selinux                                             noarch                                        2:2.80-1.git1b655d9.fc28                                           updates                                                  45 k
 containerd.io                                                 x86_64                                        1.2.2-3.fc28                                                       docker-ce-stable                                         18 M
 docker-ce-cli                                                 x86_64                                        1:18.09.1-3.fc28                                                   docker-ce-stable                                         14 M
 iptables                                                      x86_64                                        1.6.2-2.fc28                                                       fedora                                                  487 k
 libnetfilter_conntrack                                        x86_64                                        1.0.7-1.fc28                                                       updates                                                  65 k
 libnfnetlink                                                  x86_64                                        1.0.1-13.fc28                                                      fedora                                                   32 k
 libtool-ltdl                                                  x86_64                                        2.4.6-24.fc28                                                      updates                                                  57 k

Transaction Summary
==============================================================================================================================================================================================================================================
Install  8 Packages

Total size: 51 M
Installed size: 225 M
Is this ok [y/N]: y
Downloading Packages:
[SKIPPED] docker-ce-18.09.0-3.fc28.x86_64.rpm: Already downloaded
[SKIPPED] containerd.io-1.2.2-3.fc28.x86_64.rpm: Already downloaded
[SKIPPED] docker-ce-cli-18.09.1-3.fc28.x86_64.rpm: Already downloaded
[SKIPPED] container-selinux-2.80-1.git1b655d9.fc28.noarch.rpm: Already downloaded
[SKIPPED] iptables-1.6.2-2.fc28.x86_64.rpm: Already downloaded
[SKIPPED] libnfnetlink-1.0.1-13.fc28.x86_64.rpm: Already downloaded
[SKIPPED] libnetfilter_conntrack-1.0.7-1.fc28.x86_64.rpm: Already downloaded
[SKIPPED] libtool-ltdl-2.4.6-24.fc28.x86_64.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Installing       : libnfnetlink-1.0.1-13.fc28.x86_64                                                                                1/8
  Running scriptlet: libnfnetlink-1.0.1-13.fc28.x86_64                                                                                1/8
  Installing       : libnetfilter_conntrack-1.0.7-1.fc28.x86_64                                                                                2/8
  Running scriptlet: libnetfilter_conntrack-1.0.7-1.fc28.x86_64                                                                                2/8
  Installing       : iptables-1.6.2-2.fc28.x86_64                                                                                3/8
  Running scriptlet: iptables-1.6.2-2.fc28.x86_64                                                                                3/8
  Installing       : libtool-ltdl-2.4.6-24.fc28.x86_64                                                                                4/8
  Running scriptlet: libtool-ltdl-2.4.6-24.fc28.x86_64                                                                                4/8
  Installing       : docker-ce-cli-1:18.09.1-3.fc28.x86_64                                                                                5/8
  Running scriptlet: docker-ce-cli-1:18.09.1-3.fc28.x86_64                                                                                5/8
  Installing       : container-selinux-2:2.80-1.git1b655d9.fc28.noarch                                                                                6/8
  Running scriptlet: container-selinux-2:2.80-1.git1b655d9.fc28.noarch                                                                                6/8
neverallow check failed at /var/lib/selinux/targeted/tmp/modules/100/base/cil:9156
  (neverallow base_typeattr_7 unlabeled_t (file (entrypoint)))
    <root>
    allow at /var/lib/selinux/targeted/tmp/modules/200/container/cil:1573
      (allow spc_t unlabeled_t (file (entrypoint)))

Failed to generate binary
/usr/sbin/semodule:  Failed!
  Installing       : containerd.io-1.2.2-3.fc28.x86_64                                                                                7/8
  Running scriptlet: containerd.io-1.2.2-3.fc28.x86_64                                                                                7/8
  Running scriptlet: docker-ce-3:18.09.0-3.fc28.x86_64                                                                                8/8
  Installing       : docker-ce-3:18.09.0-3.fc28.x86_64                                                                                8/8
  Running scriptlet: docker-ce-3:18.09.0-3.fc28.x86_64                                                                                8/8
  Verifying        : docker-ce-3:18.09.0-3.fc28.x86_64                                                                                1/8
  Verifying        : containerd.io-1.2.2-3.fc28.x86_64                                                                                2/8
  Verifying        : docker-ce-cli-1:18.09.1-3.fc28.x86_64                                                                                3/8
  Verifying        : container-selinux-2:2.80-1.git1b655d9.fc28.noarch                                                                                4/8
  Verifying        : iptables-1.6.2-2.fc28.x86_64                                                                                5/8
  Verifying        : libnfnetlink-1.0.1-13.fc28.x86_64                                                                                6/8
  Verifying        : libnetfilter_conntrack-1.0.7-1.fc28.x86_64                                                                                7/8
  Verifying        : libtool-ltdl-2.4.6-24.fc28.x86_64                                                                                8/8

Installed:
  docker-ce.x86_64 3:18.09.0-3.fc28  container-selinux.noarch 2:2.80-1.git1b655d9.fc28  containerd.io.x86_64 1.2.2-3.fc28  docker-ce-cli.x86_64 1:18.09.1-3.fc28  iptables.x86_64 1.6.2-2.fc28  libnetfilter_conntrack.x86_64 1.0.7-1.fc28
  libnfnetlink.x86_64 1.0.1-13.fc28  libtool-ltdl.x86_64 2.4.6-24.fc28

Complete!

[vagrant@fedora28 ~]$ docker --version
Docker version 18.09.1, build 4c52b90

[vagrant@fedora28 ~]$ sudo yum list docker-ce |grep docker-ce
docker-ce.x86_64               3:18.09.0-3.fc28                @docker-ce-stable
docker-ce.x86_64               3:18.09.1-3.fc28                docker-ce-stable

CentOS7
[vagrant@cent7 ~]$ sudo yum install docker-ce-3:18.09.0-3.*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.mirror.ndchost.com
 * extras: mirror.hmc.edu
 * updates: mirrors.ocf.berkeley.edu
Resolving Dependencies
--> Running transaction check
---> Package docker-ce.x86_64 3:18.09.0-3.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================================================================================================
 Package                                                Arch                                                Version                                                       Repository                                                     Size
==============================================================================================================================================================================================================================================
Installing:
 docker-ce                                              x86_64                                              3:18.09.0-3.el7                                               docker-ce-stable                                               19 M

Transaction Summary
==============================================================================================================================================================================================================================================
Install  1 Package

Total download size: 19 M
Installed size: 81 M
Is this ok [y/d/N]: y
Downloading packages:
docker-ce-18.09.0-3.el7.x86_64.rpm                                                                                |  19 MB  00:00:07
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : 3:docker-ce-18.09.0-3.el7.x86_64                                                                                1/1
  Verifying  : 3:docker-ce-18.09.0-3.el7.x86_64                                                                                1/1

Installed:
  docker-ce.x86_64 3:18.09.0-3.el7

Complete!

[vagrant@cent7 ~]$ docker --version
Docker version 18.09.1, build 4c52b90

[vagrant@cent7 ~]$ sudo yum list | grep docker-ce
containerd.io.x86_64                        1.2.2-3.el7                @docker-ce-stable
docker-ce.x86_64                            3:18.09.0-3.el7            @docker-ce-stable
docker-ce-cli.x86_64                        1:18.09.1-3.el7            @docker-ce-stable
docker-ce.x86_64                            3:18.09.1-3.el7            docker-ce-stable
docker-ce-selinux.noarch                    17.03.3.ce-1.el7           docker-ce-stable

Unfortunately, the suggested solution of installing docker-ce-cli, docker-ce in order does not meet my needs. I am configuring my machines with Ansible. I am using the ansible-role-docker to perform the docker installation.

I think the solution for that would be to open an enhancement request in that repository.
w.r.t. the request to make the cli (docker-ce-cli) always have the exact same version as the engine (docker-ce); this was a conscious choice to allow the user to upgrade/downgrade components individually. In future, we're exploring the option to provide meta-packages that tie all packages (cli, engine, containerd, runc) to exact versions for situations, but there's no ETA for those packages yet.

Hi,
I'm having a problem where I can't even find the docker-ce package. This is my repolist.
[root@xxxx-xxxx-xxx yyyyy]# yum repolist
docker-ce-stable/x86_64                                                         Docker CE Stable - x86_64                                                                              8+35
elastic-6.x                                                                     Elastic repository for 6.x packages                                                                     490
epel/x86_64                                                                     Extra Packages for Enterprise Linux 7 - x86_64                                                     13,219+1
jenkins                                                                         Jenkins-stable                                                                                88
jlaska-proot/x86_64                                                             Copr repo for proot owned by jlaska                                                                     2+1
lynis                                                                           CISOfy Software - Lynis package                                                                          41
mariadb                                                                         MariaDB                                                                                79+1
newrelic/x86_64                                                                 New Relic packages for Enterprise Linux 5 - x86_64                                                      192
newrelic-infra                                                                  New Relic Infrastructure                                                                                252
pgdg94/7Server/x86_64                                                           PostgreSQL 9.4 7Server - x86_64                                                                         779
rackspace                                                                       Rackspace Monitoring                                                                                1
rackspace-rhel-x86_64-server-7-common                                           Rackspace - RHEL  x86_64 Server 7 - Common                                                               96
rackspace-rhel-x86_64-server-7-ius                                              Rackspace - RHEL (v. 7 for 64-bit x86_64) - IUS                                                       8,497
rhel-x86_64-server-7                                                            Red Hat Enterprise Linux Server (v. 7 for 64-bit x86_64)                                             24,345
rhel-x86_64-server-optional-7                                                   RHEL Server Optional (v. 7 64-bit x86_64)                                                            17,777
rhn-tools-rhel-x86_64-server-7                                                  RHN Tools for RHEL Server (v. 7 for x86_64)                                                             136
rs-epel/x86_64                                                                  Extra Packages for Enterprise Linux 7 - x86_64                                                     13,218+2
spp                                                                             HP SPP                                                                                1,388
repolist: 80,608

but if I execute
[root@xxxx-xxx-xxxx yyyy]# yum search docker
Loaded plugins: ps, replace, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
=================================================================================== N/S matched: docker ===================================================================================
golang-github-fsouza-go-dockerclient-devel.x86_64 : Client for the Docker remote API
imagefactory-plugins-Docker.noarch : Cloud plugin for Docker
pcp-pmda-docker.x86_64 : Performance Co-Pilot (PCP) metrics from the Docker daemon
python-docker-scripts.noarch : Collection of scripts to help manage Docker
python-dockerfile-parse.noarch : Python library for Dockerfile manipulation
python2-avocado-plugins-runner-docker.noarch : Avocado Runner for Execution on Docker Containers
python2-dockerpty.noarch : Python library to use the pseudo-tty of a docker container
python36-docker.noarch : A Python library for the Docker Engine API
python36-docker-pycreds.noarch : Python bindings for the docker credentials store API
python36-dockerpty.noarch : Python library to use the pseudo-tty of a docker container
kdocker.x86_64 : Dock any application in the system tray
kompose.x86_64 : Tool to move from 'docker-compose' to Kubernetes
reg.x86_64 : Docker registry v2 command line client

Cannot fine docker-ce package here, anyone knows why is this happening?

Is your package cache/index up to date?

Indeed this was added to documentation:
https://docs.docker.com/install/linux/docker-ce/centos/#install-docker-engine---community-1
I was also having troubles when I upgrade docker in my docker swarms via Ansible, I ended up adding:
- name: install Docker latest
  yum: name={{item}} state=present update_cache=yes
  become: yes
  become_user: root
  with_items:
  - docker-ce
  - docker-ce-cli

Of course I have another to install a specific version

This worked for me:
VERSION=5:18.09*
sudo apt install -y docker-ce=$VERSION docker-ce-cli=$VERSION

see more here:  https://docs.docker.com/install/linux/docker-ce/ubuntu/

according to https://serverfault.com/questions/964152/what-does-docker-version-name-means

18.05: the major release number from docker's rolling releases
5: the patch number, where fixes are released without new functionality

The suggested fix worked for me. The following steps resolved my issue on Ubuntu 18.04 LTS on Windows Virtualbox:

sudo apt remove docker-ce-cli
sudo apt remove docker-ce
sudo apt install docker-ce-cli
sudo apt install docker-ce
(optional) 5. sudo docker run hello-world (to test)
(optional) 6. sudo docker login --username= --password


Add "content" release type to commit-lint and release-please

Need
The site is primarily a content site, so we would like to add the commit type content, which is not a standard Conventional Commit type. This can be an alternative to docs, as docs are about web implementation and not content.
Approach

Add content as a valid commit type for commit lint.
Modify the release-please-config.json to use a "Content" section for the content commit type.

Thanks!

Complete


Incompatibility with react-navigation v3

I have posted this in the react-navigation (https://github.com/react-navigation/react-navigation/issues/5594) and react-native-gesture-handler (https://github.com/kmagiera/react-native-gesture-handler/issues/465) repositories since it seems that the error is more at their end. However the issue still concerns this repository so I'm posting here with the hope that someone with knowledge of rn-maps will have a better idea what is going on and has ideas for a workaround/fix.
Here is a gif of the issue:

React-navigation in version 3 users react-native-gesture-handler under the hood and it seems that something in the marker dragging prevents rn-gesture-handler from finding out that there is no gesture taking place.
Here is the repository with only gesture handler and react-native-maps
https://github.com/compojoom/rnMapsNavigationBug/tree/gesture_hangler
When you drag the marker and afterwards try to press any button it won't work until you drag the map.

Is this a bug report?
yes
Environment
iOS. Issue doesn't happen on Android
Steps to Reproduce
View provided repository
https://github.com/compojoom/rnMapsNavigationBug/tree/gesture_hangler

Some issue on IOS, working good on Android

@compojoom were you able to find a workaround for this?
I'm trying to keep track of when the user moves the map so that I can show a "search this area" button. I'm trying to use onMoveShouldSetResponder to change the state on touch, which means I'm using react native's default gesture responder instead of React-Native-Gesture-Handler, but that works fine on Android when disabling gestures in React Navigation, but the event doesn't fire on iOS.
People had similar problems, as discussed in https://github.com/react-native-community/react-native-maps/issues/1038, and they were able to use other responder events in React Native's default gesture responder, but not onMoveShouldSetResponder. Because using the default responder works on android when disabling gestures in React Navigation but not on Android, I think the issue may be related to https://github.com/kmagiera/react-native-gesture-handler/issues/255 since he didn't test on Android, but because RNGH isn't working with react-native maps, nor is the default responder, I can't seem to find an efficient workaround.

The last release about the memory fix was talking about gestures, so I decided to see if it will solve the problem, but it doesn't. I've updated the repository to 0.24.2 and the problem remains.
Since it is working after moving the map I thought that if I move the map with animateToCamera or to Region it could work, but it didn't. Problem remains.
The only workaround that I have right now is to use react-navigation v2 - which doesn't rely on rn-gesture-handler... But react-navigation v2 has it's own set of issues...

I have exactly the same problem. Did you somehow solved this issue with an current version of navigation?

parche only hide map onEnDrag event in IOS with setState like this:
changePositionMarker = e => {
if (Platform.OS == 'ios') {
this.setState(
{
latLong: e.nativeEvent.coordinate,
showHideMap: false,
},
() => {
this.setState({
showHideMap: true,
});
}
);
} else {
this.setState({
latLong: e.nativeEvent.coordinate,
});
}
};

Creo que encontre la solucion, es la misma solucion de @yamaka pero implementada en un componente funcional
`import React, {useState,useEffect} from 'react';
import {StyleSheet,View, Text, TouchableOpacity} from 'react-native';
import MapView, { PROVIDER_GOOGLE } from 'react-native-maps';
import { mapStyle } from '../styles/mapStyle';
import defaultMapOptions from '../config/mapOptions'
function RegisterMarketScreenStep2(props) {
const CompanyInfoSchema = {
	company_name : 'SIB C.A.',
	address : 'Barinas',
	company_email<EMAIL_ADDRESS>	primary_phone : '330 7364527',
	secondary_phone : '330 8746302'
}

const [ CompanyInfo ] = useState(CompanyInfoSchema)
const [Origin , setOrigin] = useState({
	          	latitude: 18.388725,
			  	longitude: -66.130101,
			})

const [ZoomMap , setZoomMap] = useState({
				latitudeDelta: -0.001,
				longitudeDelta: 0.0180,
		  })

const [ForceRefresh , setForceRefresh ] = useState( Math.floor(Math.random() * 100) )

useEffect(() => {
	setForceRefresh(Math.floor(Math.random() * 100))
  },[Origin]);

return <View style={styles.container}>

		<View style={styles.captionContainer}>
          	<View style={{flex : 1,flexDirection:'row'}}>
              	<View style={{ flex: 1, flexDirection: 'row', alignItems: 'center',padding:10,justifyContent:'center'}}>
					<TouchableOpacity>
						<Text style={{color:'white'}}>Drag and drop ther marker and set your bussiness location</Text>
					</TouchableOpacity>
              	</View>
          	</View>
          </View>

        <MapView
		  key={ForceRefresh}
          style={styles.map}
          provider={PROVIDER_GOOGLE}
          region={{
            ...Origin,
            latitudeDelta: ZoomMap.latitudeDelta,
            longitudeDelta: ZoomMap.longitudeDelta,
          }}
          defaultOptions={defaultMapOptions}
          customMapStyle={mapStyle}
          showsCompass={false}
          zoomEnabled={true}
          zoomControlEnabled={true}
          toolbarEnabled={false}
          >

        <MapView.Marker
			coordinate={{...Origin}}
			title={"You are here"}
			image={require('../assets/pin.png')}
			draggable
    		onDragEnd={(e) =>setOrigin(e.nativeEvent.coordinate)}

		>
        </MapView.Marker>
        </MapView>

        <View style={styles.buttonContainer}>
        	<View style={{flex : 1,flexDirection:'row'}}>

				<TouchableOpacity
					style={{ flex: 1, flexDirection: 'row', alignItems: 'center',padding:10,justifyContent:'center'}}
					onPress={ () => this.props.navigation.goBack() }
				>
					<Text style={{color:'white'}}>Back</Text>
				</TouchableOpacity>

				<TouchableOpacity style={{ flex: 1, flexDirection: 'row', alignItems: 'center',padding:10,justifyContent:'center'}}>
					<Text style={{color:'white'}}
					onPress={ () => props.navigation.navigate('MarketConfirm', {company : {...CompanyInfo}, origin : Origin }) }>Next</Text>
				</TouchableOpacity>
        	</View>
        </View>

    </View>

}
export default RegisterMarketScreenStep2
const styles = StyleSheet.create({
map: {
height : '100%',
flex: 1,
zIndex: 2,
backgroundColor: '#FFFFFF'
},
container: {
flex: 1,
},
captionContainer: {
flex : 1,
position : 'absolute',
top : 0,
zIndex : 4,
backgroundColor: '#6812c0',
padding: 10,
width : '100%',
shadowRadius: 10,
shadowOpacity: 0.25
},
buttonContainer: {
flex : 1,
position : 'absolute',
bottom : 0,
zIndex : 4,
backgroundColor: '#6812c0',
padding: 10,
width : '100%',
shadowRadius: 10,
shadowOpacity: 0.25
},
button: {
flex : 1,
backgroundColor: '#6812c0',
zIndex : 3,
justifyContent : 'center',
marginTop : 3,
color:'white',
textAlign : 'center',
borderRadius: 5,
padding: 10,
shadowColor: '#6812c0',
shadowOffset: {
width: 0,
height: 3,
},
width : '100%',
shadowRadius: 10,
shadowOpacity: 0.25

},
caption : {
textAlign:'center',color:'yellow',flex : 1, fontSize : 24
}
});`

We also had this issue.
Our solution was to use Touchable* components provided by react-native-gesture-handler package instead of react-native ones:
import { TouchableOpacity } from 'react-native-gesture-handler';

They continue to work after map marker dragging.

import { TouchableOpacity } from 'react-native-gesture-handler';

This isn't really a viable option for us, since our map is on the home scree.
We would need to swap out every since Touchable in our App to fix this issue.

We also had this issue.
Our solution was to use Touchable* components provided by react-native-gesture-handler package instead of react-native ones:
import { TouchableOpacity } from 'react-native-gesture-handler';

They continue to work after map marker dragging.

there are other components in my project which i did not build and they get locked up because of that as well.. so it doesn't solve it completely. i noticed that if i tap on the map after the long press function then the issue resolves. i tried to look up how to simulate a tap in react native but couldn't find any way. (it's my first app in react native)

anything new here? it literally renders my app useless..

Still no other solution but swapping react-native's TouchableOpacity for react-native-gesture-handler's TouchableOpacity?
The latter comes with its own set of issues (flexbox, absolute positioning, touch sounds).

@avlonder I don't think so, we eventually revert back to Apple Map for our app.


Use releases to derive version list

Fixes #12

Looks like build is failing because the mise action is still trying to pull in the unreleased version

This needs to respect the GitHub api token if it's set, try to see if you can find a reference from a different plugin

This needs to respect the GitHub api token if it's set, try to see if you can find a reference from a different plugin

Done - saw that in another plugin but didn't realise it was universal and left it out :)

Thanks @jdx :)


Faster brew formulae command (and formula completion!)

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[X] Have you successfully run brew tests with your changes locally?

brew formulae starts to get really slow if you have even a fairly modest number of taps tapped. On my system:
time brew formulae

real	0m0.441s
user	0m0.089s
sys	0m0.292s

This command gets called every time completion is attempted on the formula list, like brew install and half a second is definitely enough to make using tab completion for formulae feel bad rather than snappy.
The reason this happens is that we haven't added the .git repo folder to the list of names for find to omit from its search in items.sh (which is what brew formulae ultimately calls).  The .git folder tends to have a large number of files inside and nothing we need for building a list of installable tap formula names.
This PR is about as simple as they come, it just adds .git to the list of things for the find command to ignore.
After this change:
time brew formulae

real	0m0.159s
user	0m0.042s
sys	0m0.078s

Formula completion now feels much faster!

This is a great idea! It runs around 4.5x faster on my machine.
$ hyperfine --parameter-list branch master,faster_formulae --warmup 5 --setup 'git switch {branch}' 'brew formulae'
Benchmark 1: brew formulae (branch = master)
  Time (mean ± σ):     299.2 ms ±   3.5 ms    [User: 90.1 ms, System: 210.7 ms]
  Range (min … max):   296.6 ms … 308.5 ms    10 runs

Benchmark 2: brew formulae (branch = faster_formulae)
  Time (mean ± σ):      66.6 ms ±   7.6 ms    [User: 28.6 ms, System: 37.9 ms]
  Range (min … max):    59.6 ms …  99.6 ms    46 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  brew formulae (branch = faster_formulae) ran
    4.49 ± 0.51 times faster than brew formulae (branch = master)

This also speeds up brew casks which also uses items.sh internally by 3x too.
$ hyperfine --parameter-list branch master,faster_formulae --warmup 5 --setup 'git switch {branch}' 'brew casks'
Benchmark 1: brew casks (branch = master)
  Time (mean ± σ):     334.7 ms ±  21.4 ms    [User: 105.2 ms, System: 224.9 ms]
  Range (min … max):   323.9 ms … 395.0 ms    10 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: brew casks (branch = faster_formulae)
  Time (mean ± σ):     109.5 ms ±  12.2 ms    [User: 51.2 ms, System: 55.5 ms]
  Range (min … max):   101.3 ms … 151.8 ms    23 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  brew casks (branch = faster_formulae) ran
    3.06 ± 0.39 times faster than brew casks (branch = master)

Both commands produce the same output as before according to my brew branch-compare command as well.


Fixes 187: speed up seeds_test

Currently seed test is the slowest test file, taking over a second.
Some of this is due to 'batch size' for inserting, and a desire to test a number greater than that.
This ticket makes the batch size configurable so the seeding can test with a loweramount

https://issues.redhat.com/browse/HMSCONTENT-187


CL random accepts a float argument that can be below 1, so I think this ...

...definition matches better.

CL random returns an integer when called with an integer argument and a float when called with a float argument: (random 4) is guaranteed to be either 0, 1, 2 or 3. The corresponding JavaScript expression per your definition, 4 * Math.round() will almost always return a non-integer. I don't see any good way around this problem. JavaScript simply doesn't differentiate between floats and integers (Number.isInteger(4.0) returns true, etc.), which means that we'd have to determine what kind of argument our random is called with on the Lisp side. If we want to handle the general case, this would cause us to supply PS with a statically checked type system—hardly a realistic prospect. And since our random definition is going to be incorrect anyway, we're forced to choose which part of it we prefer to get right: that it work with fractional numbers, or that it return integers on integer input. IMO, the second case occurs more frequently as JavaScript programs go, so I'd rather stick with our current definition. Any objections?

The definition can check for abs(x) < 1 and return a float for numbers less
than 1.
On Wed, Jun 10, 2015 at 11:53 AM, Boris Smilga<EMAIL_ADDRESS>wrote:

CL random returns an integer when called with an integer argument and a
float when called with a float argument: (random 4) is guaranteed to be
either 0, 1, 2 or 3. The corresponding JavaScript expression per your
definition, 4 * Math.round() will almost always return a non-integer. I
don't see any good way around this problem. JavaScript simply doesn't
differentiate between floats and integers (Number.isInteger(4.0) returns
true, etc.), which means that we'd have to determine what kind of argument
our random is called with on the Lisp side. If we want to handle the
general case, this would cause us to supply PS with a statically checked
type system—hardly a realistic prospect. And since our random definition
is going to be incorrect anyway, we're forced to choose which part of it we
prefer to get right: that it work with fractional numbers, or that it
return integers on integer input. IMO, the second case occurs more
frequently as JavaScript programs go, so I'd rather stick with our current
definition. Any objections?
—
Reply to this email directly or view it on GitHub
https://github.com/vsedach/Parenscript/pull/22#issuecomment-110876533.

Ok. So here is new patch that do what vsedach proposed: best of both world.

Great, thanks! But could you perhaps also keep the no-args version of random? Just for reverse compatibility's sake.

done.

Oh, and another problem I regrettably have overlooked is that this macro is going to break on (random (get-height block)) etc. The arg of your definition is a macro variable referring to the syntactic form (the list (get-height block) in the example) rather an in-code variable referring to the numeric value. May I propose:
(def-js-maths
    ...
    (random (&optional arg)
      (if arg
          (maybe-once-only (arg)
            `(if (< (abs ,arg) 1)
                 (* ,arg (funcall (@ *math random)))
                 (floor (* ,arg (funcall (@ *math random))))))
          '(funcall (@ *math random)))))

Here is agrostis solution. So I think I can close this issue now.


Add papermill package

Per @yugangzhang's request for CHX.

Merging it to build faster and make it available for CHX.


Plan and Conduct Workshops

[ ] - Organize workshops and training sessions for children, young adults, and community members
[ ] - Develop schedules, agendas, and content for these sessions
[ ] - Gather feedback to improve future workshops

@clentafrica/wg-education

@clentafrica/wg-education


Refactor ClickHouse monitor implementation

This PR implements the flow visibility ClickHouse monitor with a long-running pod instead of the Cronjob which is used before. This implementation brings the following advantages.

It reduces the overhead of creating and destroying new pod every time the monitor executes
It avoids reading the K8s logs to check the last state of execution

Signed-off-by: Yanjun Zhou<EMAIL_ADDRESS>

Codecov Report

Merging #3498 (6fb8b8e) into main (6c4e5a3) will decrease coverage by 29.76%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3498       +/-   ##
===========================================
- Coverage   65.59%   35.83%   -29.77%
===========================================
  Files         268      106      -162
  Lines       26780    14543    -12237
===========================================
- Hits        17567     5211    -12356
- Misses       7314     8842     +1528
+ Partials     1899      490     -1409

Flag
Coverage Δ

integration-tests
35.83% <ø> (?)

kind-e2e-tests
?

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/controller/grouping/controller.go

multicluster/cmd/multicluster-controller/member.go

pkg/agent/cniserver/server.go

pkg/agent/util/ndp/ndp_linux.go

pkg/agent/openflow/groups.go

...g/controller/networkpolicy/clusternetworkpolicy.go

pkg/agent/controller/networkpolicy/priority.go

pkg/ipfix/ipfix_registry.go

pkg/agent/util/ipset/ipset.go

pkg/agent/multicast/mcast_socket_linux.go

... and 364 more

/skip-all
can skip tests based on code changes


Update Composer dependencies (2021-10-02-00-11)

Visual regression test passed!
View the visual regression test report


Add seq function

Cool, that works.

looks good. can you or have you added Seq to the arbitrary? :page_facing_up:


Subterritory DnD doesn't work

Can be done in another way - so depending on how difficult it is to fix, move to the proper milestone.

But you are only able to dnd children inside one parent so you dont have any possibility to change order here.

@Ptrhnk OK, maybe it makes sense to leave it as it is.
But handle somehow the result - I think that the "no drop" sign should appear. Instead, this is how the screen remains after a failed attempt - all territories disappear until page reload:

@davidzbiral Ok, I see now, that it's possible to invoke an error with this behavior.

But you really have some problem with cursor. It would be nice to be able to analyze it somehow. Are you working in zoom in mode in browser?

I would put it differently - the app has problem with my cursor :-D Now at 120%. Shown now in the GIF in #935.


Revert "Fix phony fixture IDs in bootstrap4"

Reverts MushroomObserver/mushroom-observer#584
I'm that by reverting this it will somehow fix the Error shown here:
https://travis-ci.org/github/MushroomObserver/mushroom-observer/builds/701442243

Didn't work. I'm getting the same problem with continuous-integration/travis-ci/pr.
See https://travis-ci.org/github/MushroomObserver/mushroom-observer/builds/701461878
The log for that build includes:
Auto-merging test/fixtures/triples.yml
CONFLICT (content): Merge conflict in test/fixtures/triples.yml
Auto-merging test/fixtures/name/descriptions.yml
Auto-merging test/fixtures/location/descriptions.yml
Automatic merge failed; fix conflicts and then commit the result.

and later:
rake aborted!
SyntaxError: /home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:39: syntax error, unexpected ===
=======
^~~
/home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:43: syntax error, unexpected tCONSTANT, expecting ')'
...://eol.org/search?q=Abortiporus+biennis&type%5B%5D=TaxonConc...
...                    ^~~~~~~~~~~
/home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:43: syntax error, unexpected tCONSTANT, expecting ')'
...h?q=Abortiporus+biennis&type%5B%5D=TaxonConcept'\n".freeze
...                              ^
/home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:43: syntax error, unexpected tCONSTANT, expecting ')'
...=Abortiporus+biennis&type%5B%5D=TaxonConcept'\n".freeze
...                              ^
/home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:46: unterminated string meets end of file
; _erbout
         ^
/home/travis/build/MushroomObserver/mushroom-observer/test/fixtures/triples.yml:46: syntax error, unexpected end-of-input, expecting ')'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixture_set/file.rb:65:in `render'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixture_set/file.rb:50:in `raw_rows'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixture_set/file.rb:39:in `config_row'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixture_set/file.rb:29:in `model_class'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:800:in `block (2 levels) in read_fixture_files'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixture_set/file.rb:17:in `open'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:799:in `block in read_fixture_files'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:798:in `each'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:798:in `each_with_object'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:798:in `read_fixture_files'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:607:in `initialize'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:548:in `new'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:548:in `block in create_fixtures'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:545:in `map'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/fixtures.rb:545:in `create_fixtures'
/home/travis/.rvm/gems/ruby-2.6.6/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/databases.rake:217:in `block (3 levels) in <top (required)>'
/home/travis/.rvm/gems/ruby-2.6.6/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/home/travis/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:24:in `eval'
/home/travis/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:24:in `<main>'
Tasks: TOP => db:fixtures:load
(See full trace by running task with --trace)
The command "rake db:fixtures:load" failed and exited with 1 during .
Your build has been stopped.


hot module reload

Enable hot module reloading for JS/CSS in the uploader.

As mentioned above, please lock down the dependencies in the package.json and add an explanation of that weird warning (about the checked in key file) in the README. Otherwise LGTM, go ahead and merge @krystophv

@jebeck - Could I get a quick opinion about the summary of the warning Chrome throws on the unpacked extension? Is it clear enough?

Explanation of the warning looks good @krystophv, but want to take another look at point 10 on the README? Probably should change to explain hot-reloading. I'd put something like "React components and CSS will hot load after changes, but changes to device drivers and other code outside of the React components will not - use 'Reload' from chrome://extensions to reload after such changes."

@jebeck does https://github.com/tidepool-org/chrome-uploader/commit/044b3eddcc435c345ba7f7f37b1722db20e3a638 look good?

 There should be a way to get it to not issue the hot-update either (and thus potentially not need the App refresh - see https://github.com/gaearon/react-hot-boilerplate/issues/1 ) but I couldn't get that implementation working properly, likely due to the write to disk plugin.


Environment variable configuration using API

I think the documentation about env vars needs some more clarification.
First of all, I thought configuration set in env vars would always be considered, but as far as I understand only the Maven and Gradle integrations obey these variables since they use the ConfigUtil. In other words, settings env vars has no effect on the Java API as long as I instantiate Flyway by myself: new Flyway(). On the Java API I'm expected to call the configuration setters (setCleanDisabled(...)) also before using the Flyway object.
In addition, things behave different for the Spring Boot Autoconfiguration. If I'm having my Flyway object injected, Spring Boot will configure it for me - by using Spring's configuration enviroment.  Thus I can use environment variables here, but I have to stick to Spring's property notation, e.g. flyway.clean-disabled=true.
I had to learn this the hard way. Could you please clarify this in the documentation?

The environment variable docs have now been clarified. We plan on adding optional environment variable config to 5.1 as well.
The Spring Boot issue is something I am not sure we should address on that page. Our dedicated Spring Boot page may be a good place for that though.

Hey Axel,
thanks for the fast reaction! Your edit to the env vars page looks good to me.
For Spring Boot I understand that it's also been documented there before - implicitely:

You can then configure a good number of Flyway properties directly from your application.properties or application.yml file.

But maybe one could extend this to make it a bit more explicit?

You can then configure a good number of Flyway properties directly from your application.properties or application.yml file. In Spring Boot, this configuration can also be moved to the system's environment variables. Be aware that the properties' notation is different then compared to Flyway's native support for environment variables.

@PeterWippermann Good suggestion. I have integrated it (with slightly different wording).

Thank you! :-)

Actually I was to leave this open until support for env vars configuration using the API is implemented.

This has now been implemented. Flyway's envVars can now be used for configuration via the API by calling the envVars() method on the configuration object.


LightningQubit2 VJP support

Before submitting
Please complete the following checklist when submitting a PR:

[ ] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[x] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[ ] Ensure that the test suite passes, by running make test.

[x] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[ ] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:

[sc-59045]

Lots of test failures in Pennylane due to lack of VJP support in Lightning. I am skipping such tests for now, but they should stop being skipped once this PR is merged. See the files changed in PL #5434 to find which tests need to be updated.

TODO in pennylane: Uncomment interface tests using lightning.qubit with device_vjp=True. These were commented out due to LightningQubit not being able to compute VJPs.


[Feature]: Support rerank models

🚀 The feature, motivation and pitch
Rerank models are essential to RAG workflow. There are quite a few models available, such as jina-reranker-v2. Some inference frameworks already support rerank models, for example, https://inference.readthedocs.io/en/latest/models/builtin/rerank/index.html
Do we have plans to add support for this?
What are the main steps if someone tries to implement?

+1

+1

+1

+1

Looks like there is some support now: https://docs.vllm.ai/en/latest/models/supported_models.html#sentence-pair-scoring

the API path is v1/score


Clean up api-server-bypass-risks.md

Remove extra spaces
Provide a consistent indentation for ordered list preceded with 3 spaces
Remove extra lines

/kind cleanup

/lgtm
/approve


Katana high memory usage when running with high concurrency and large lists

Please describe your feature request:

Describe the use case of this feature:

I guess my issue is relevant to this.
When crawling pretty big gitea repository (don't ask me why), katana may take more then 1GB of RAM and 100% CPU depending on threads/concurrency settings.
That's the example for scan with more then 1GB of RAM:
katana -u 'https://gitea.com/gitea/blog' -d 2
The key here is size of repo. With larger repos it take more RAM. But my problem that I'm running with -d 2 which should crawl only one URL basically extracting URLs from it, right?!

Here also issues with large lists however I kept lower conc but the ram runs full (32gb) after a couple hundred domains


Update links

Resolves https://github.com/kubernetes/website/issues/28575#issuecomment-866633898
Resolves #28795

/language en

/hold

We should replace

docs/tasks/administer-cluster/out-of-resource -> docs/concepts/scheduling-eviction/node-pressure-eviction (redirection entry already exists)
docs/concepts/scheduling-eviction/out-of-resource -> docs/concepts/scheduling-eviction/node-pressure-eviction (redirection entry does not exist)

/unhold
I pushed another commit that resolves https://github.com/kubernetes/website/pull/28797#pullrequestreview-702610954 and https://github.com/kubernetes/website/pull/28797#issuecomment-876847777 .
@Arhell @sftim Could you please take a look again?
Thank you!

/lgtm

/lgtm
/approve


Add a "--version" option

For QC purposes

The submodules have a --version option (eg nanopolish eventalign --version) but you are right, the main program should support this.
Jared


"Sudoku Solver" project has an error "setGrid is not defined" when user changes data inside textarea

Description:
There is an issue “ReferenceError: setGrid is not defined” in “Sudoku Solver” https://sudoku-solver--freecodecamp.repl.co/ example project when a user enters/changes/removes data inside. Also, if data inside textarea was changed no changes apply to the sudoku grid. I suppose the second issue is because of the first.

Browser Name:  Firefox
Browser Version: 79.0 (64-bit)
Operating System: macOS Catalina 10.15.6

Steps:
Go to -> https://sudoku-solver--freecodecamp.repl.co/
Open Dev Tools -> Console in browser
Go to the page and find the textarea with the sample sudoku string and two buttons (Solve and Clear)
Change data inside the textarea: remove/change/add any symbol.
(I removed last 34 positions)
Check the console for errors, check sudoku grid for changes

Actual result:
You can see an error in console.
Uncaught ReferenceError: setGrid is not defined
oninput https://sudoku-solver--freecodecamp.repl.co/:1
sudoku-solver–freecodecamp.repl.co:1:1
Uncaught ReferenceError: setGrid is not defined
oninput https://sudoku-solver--freecodecamp.repl.co/:1

The grid is not updated after changes:

Expected result:
No error about setGrid is not defined.
If textarea was changed then changes should be applied to the grid.

I also realized this today when I was looking for a way to solve the project.
I was able to get it working by adding an event listener to textArea and a handler function.
const onInputHandler = (e) => {
  const str = e.target.value;
  setGrid(str);
};

textArea.addEventListener("input", onInputHandler);

This way, there's no need to use the oninput attribute that is within the textarea of the index.html file.
I have not contributed to open source projects yet, but I hope my comment can be of help to solve this issue.

As the error message suggests, the function setGrid is not recognized. This might be because it's not getting imported.
While using type="module", the function needs to be imported like this:
<script type="module">
  import {sayHi} from './say.js';

  document.body.innerHTML = sayHi('John');
</script>

Or better just remove type="module" from the script tag.

This issue appears to be fixed in the new demo project. As such, we are going to close the issue. If you feel this has been done in error, feel free to request that it be reopened and provide all relevant information. 🙂


[Issue]: MAD_MODEL_NAME no longer supported

Problem Description
I tried specifying a target model using MAD_MODEL_NAME, however, in the latest version it appears this env variable is no longer supported.
https://github.com/ROCm/MAD/commit/e744d4c5fecf33c985caa7948241f2919c5e7976
I suggest you remove mention of MAD_MODEL_NAME from your README since --tags is no the preferred method of targeting a specific model
Operating System
Rocky Linux 9.4
CPU
AMD EPYC 7V13 64-Core Processor
GPU
AMD Instinct MI250
ROCm Version
ROCm 6.2.0
ROCm Component
No response
Steps to Reproduce
git clone https://github.com/coleramos425/MAD.git
export MAD_MODEL_NAME=pyt_huggingface_gpt2
python3 tools/run_models.py --live-output

/home1/colramos/mad-fork/tools/utils.py:944: SyntaxWarning: invalid escape sequence '\d'
  perf_regex = ".*performance:\\s*([+|-]?\d*[.]?\d*)\\s*.*\\s*"
/home1/colramos/mad-fork/tools/utils.py:946: SyntaxWarning: invalid escape sequence '\d'
  metric_regex = ".*performance:\\s*[+|-]?\d*[.]?\d*\\s*(\w*)\\s*"
Traceback (most recent call last):
  File "/home1/colramos/mad-fork/tools/run_models.py", line 494, in <module>
    sys.exit(main() == False)
             ^^^^^^
  File "/home1/colramos/mad-fork/tools/run_models.py", line 480, in main
    with open('tags.json') as t:
         ^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'tags.json'

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

MAD_MODEL_NAME is an env variable for docker cmd. It is not used with python3 tools/run_models.py. Please use the following line to run your model as reference.
python3 tools/run_models.py --tags pyt_huggingface_gpt2 --live-output


[WIP] Update to Avalonia 11 RC 1

Just another set of test changes to build with the latest Avalonia 11 nightly, as you can never break too many things

Ok, Avalonia 11 now has an actual release candidate package available :-)

So it's building ok, and the control catalog seems to work :-)
There are a bunch of new warnings about some style related things being deprecated, that I haven't looked at, e.g.
/home/runner/work/Avalonia.FuncUI/Avalonia.FuncUI/src/Avalonia.FuncUI/Components/StaticComponent.fs(24,15): warning FS0044: This construct is deprecated. This interface may be removed in 12.0. Use StyledElement, or override StyledElement.StyleKeyOverride to override the StyleKey for a class

I'm merging this.


Support for OneFlow variety of release management

I feel like it's probably possible to handle this with the current flag commands, but I'm not entirely sure how. We're currently using this plugin, but need to switch to a simpler alternative, hence we'd like to do OneFlow. This means we just tag each release/support branch when they end, merging them back to develop (no master branch essentially). Is this currently possible? I feel like I just need to do something like this, but I'm not sure if it will accomplish what I want.
➜ mvn -s ~/.m2/release-settings.xml -DbuildScmBranch=master -Dtag=0.5.0 -DgitURLExpression=git@github.com:blah/blah.git -DgitBranchExpression=release/0.5.0 -DmasterBranchPattern=release/0.5.0 clean deploy

That seems kinda close, but in that case, it would probably be better to introduce a new one-flow specific goal that would do the artifact promotion and tagging on the release / support / hotfix branch and ignore the master.

@bvarner hm do you have any suggestion on how to do that?


Missing information in regards to mapping

Hello
This is a very interesting subject, but some critical information is missing:

Line mapping definitions are missing for most of the table mappings
"One-way, and data is transformed in the process." is used in the above for many mappings, but you say nothing about how the data is being transformed. please explain further.

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

ID: 5034c9f1-31bf-9649-f8f8-af7cca2da37e
Version Independent ID: ecd0db96-4b9a-7d65-986c-523fa42f6ce0
Content: Integrate procurement between Supply Chain Management and Field Service - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/data-entities/dual-write/scm-field-service-procurement.md
Service: dynamics-ax-applications
Product: ****
Technology: ****
GitHub Login: @mkirknel
Microsoft Alias: mkirknel

@IvanLarsen87 - thank you for the feeback.
@kamaybac - can you please take a look and assign this to the correct PM?

@IvanLarsen87 - thank you for the feeback.
@kamaybac - can you please take a look and assign this to the correct PM?

@RichardLuan,  please review this customer feedback and consider whether we could update this topic to meet this request. Thanks.

@RichardLuan,  please review this customer feedback and consider whether we could update this topic to meet this request. Thanks.

BUG 552834 created to track.

This has been fixed.


Unable to get a default value on Select using the package

Could you please help me with this query. Not sure where to reach out to someone to get some insights on this.
https://stackoverflow.com/questions/69966125/fauna-db-and-flutter-unable-to-get-a-default-value-on-select-using-the-faunadb

Hey, so you want to return a String as the result from Select if the specified key doesn't exist? Am I understanding that correctly?

I have just pushed a new version 0.13.4. Please try this out.

Thanks for the lightening fast resolution. Its working.


bug: fix variable decoder updatedAt

Looks like there is a typo in the encoder pipeline that should have been updatedAt instead of createdAt.

Yup, thanks @mrvicadai!


Generate new genesis dump for 2.35.0

For scanner release 2.35.0.

@jvdm I think e2etests are failing because you may be based on an old branch? Can you rebase?

@jvdm I think e2etests are failing because you may be based on an old branch? Can you rebase?

Yeah, let's track the E2E here and here.


Dialog review

Checklist

[x] Build process is done without errors and all tests pass in the /lib directory.
[x] Self-reviewed the code before submitting.
[x] Meets accessibility standards.
[x] Added/updated documentation to /website as needed.
[x] Added/updated tests as needed.

Description
Summary:

Extra padding-top removed (#1446). Now, when displayed, the decision of how to avoid the clear action button relies on the user.
The content is now free from development decisions (#1470). The content is no longer subject to its container display value (removed flex). The decision of how to lay out the components inside the Dialog relies on the user.
Responsive values updated. The width of the dialog when the screen is smaller changes from 800px to 696px.
New implementation: Focus Lock. A new utility component was added to the DS that keeps the focus on its children and autofocuses the first available element.
Removed several tokens related to the typography of the custom content: fontFamily, fontSize and fontWeight.
Updated specifications with the new values in the tables. Also, removed the previously mentioned tokens from every place on the documentation.

Closes #1446 #1470 #1485 #1496

These are some of the strange behaviours I have found out for now:
If there is an element with a tabIndex > 0 the focus can leave the dialogue. When using the shift tab from the first element it seems to need an extra step to focus on the last element.

The second case is already fixed. In regards to the first case, I could reproduce it since in my laptop is working fine, could you please paste your code in a comment?

I just simply added a DxcButton with tabIndex={1} to the dialog.
Related to this issue using the shift tab I was nerver able to focus on the button with positive tabIndex.

I just simply added a DxcButton with tabIndex={1} to the dialog. Related to this issue using the shift tab I was nerver able to focus on the button with positive tabIndex.

I saw the problem. When we change the tabIndex of the inner content to a different value than the Dialog's one, it seems to lose the lock (understandable). I'm currently checking this since I'm not sure how it should work in this cases.

I just simply added a DxcButton with tabIndex={1} to the dialog. Related to this issue using the shift tab I was nerver able to focus on the button with positive tabIndex.

I saw the problem. When we change the tabIndex of the inner content to a different value than the Dialog's one, it seems to lose the lock (understandable). I'm currently checking this since I'm not sure how it should work in this case.

One more thing I noticed is that if the first element has  tabIndex > 0 it is still autofocused even if there are elements with higher priority.

I just simply added a DxcButton with tabIndex={1} to the dialog. Related to this issue using the shift tab I was nerver able to focus on the button with positive tabIndex.

I saw the problem. When we change the tabIndex of the inner content to a different value than the Dialog's one, it seems to lose the lock (understandable). I'm currently checking this since I'm not sure how it should work in this case.

One more thing I noticed is that if the first element has tabIndex > 0 it is still autofocused even if there are elements with higher priority.

That's because that's not how tabIndex works. Here, the main goal is to autofocus the first available focusable item of the Dialog. By changing the value of its tabIndex you are only establishing a different order in the normal sequence of tabbable elements. tabIndex is not used for autofocusing, for that kind of purpose is the autofocus property (which is what we are trying to reproduce).


Presentation and documentation

contributed to the slides pages and the projects documentation

I worked with other teammates to achieve our aim towards the presentation and documentation

I worked on the beginning of the documentation and my team mates helped in completing the rest.
For the presentation I and my other team mate made a video but we decided to go for the one that was much better putting into consideration all necessary things.

I participated actively in the presentation process whilst my team members worked on the documentation.

I shared ideas during the preparation of the document. I assisted other team members in preparing the presentation slides.

I wrote the introductory paragraph of the documentation and the content under sub-header "Style guide and ‘Project Conficon Design System’ " https://docs.google.com/document/d/1NHwGURyTuiTAt0hmV3LlThZmMjWY6PStkSYUXEhmAvM/edit
I also edited the general documentation with assistance from @Sinonaif. I worked with @Sinonaif to complete the presentation slides by providing images for the slides.

I was not able to contribute to this at the time, a network problem

I worked and added input to structure properly the : Problem Statement, Research Objectives
https://docs.google.com/document/d/14mBeRUoBKj3ynNwAG_E2vqnylWgz9SolZeaH5qfoisg/edit?usp=sharing

with @Sinonaif,  I helped curate and edit the slides content


Doesnt work on usage according to documentation

Hi , I have done an npm install and used the component as explained. But the images dont render in pano or cube pano or any other. Its just blank. I have no errors also. Do i need to install any dependencies??
I also cloned the repository and tried. There is a memory crash because of the rendering of the connection scenes. Can you please help me making this work.

I have rechecked and changed few things in my code. Now it works. But when I put the Pano component in div it fails to work. Do you know why this scenario occurs so that I can find a fix??

There is memory issue when you clone the repo and run locally. I will fix it later.
But there is no this issue if you use it as library.
as for next issue, could you plz share some demo in jsfiddle or other? it would be good if u ask in stackoverflow unless it is bug report


[opt](primary key bf) enhance primary key bloomfilter by fixed slice type

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Currently, the primary key Bloom filter index can be created with any data type. However, when adding values, it only supports slice values. This inconsistency may lead to potential misuse or future issues.
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall


High number of collisions in lookup for existing boxes for objects

The dictionary for deduplication of objects has an entry for each object or value in the serialized graph.
There is large number of collisions for objects with HashCode = 0 (0, false, 0.0, Tuple(0, 0), enums with value zero, ...)

Has been resolved by changes to EqualityComparer in
304f70d


fix(protocol): Batch Decoding

Description
Breaks out the small batch decoding fix from #234.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#235 👈
main

This comment was automatically generated by st.


Link to the extension's VSCode Marketplace href

First of all, thanks for cooking this up! Given the extension is relatively new, I think adding the extension page (for ease of installation) to the repo's 'About' setting might be helpful. If you agree, here's the href: https://marketplace.visualstudio.com/items?itemName=gp-pereira.refatorex

I added the href to the about page, many thanks. I'll added an "editors installation" section soon when i start porting it.


Show breadcrumbs also for untitled files

Breadcrumbs used to be enabled for untitled files (#54094, 9768dabba7).
Following a complain about having an empty bar (#74924), it was removed
(#75325).
This change enables breadcrumbs for new files, but only if the language
is not plaintext. So for a completely new file without contents nothing
is shown, but when a language is detected/chosen it will appear.
Fixes #84746.

ping

Anyone?

@jrieken @bpasero

This change enables breadcrumbs for new files, but only if the language
is not plaintext. So for a completely new file without contents nothing
is shown, but when a language is detected/chosen it will appear.

Don't assume every new file is plain text, there is settings and UX flows where new files are associated with a language mode (see files.defaultLanguage) With your change the empty bar will return which isn't wanted.
I believe the right approach here to dynamically enable breadcrumbs for such files, e.g only it when they symbol-path information.

Why isn't it wanted? For types that support breadcrumbs, I prefer it will always be there rather than flickering when the content is changed.

Why isn't it wanted?

#74924 is why. Also note that many language services don't support untitled files (forever whitespace) and that after reload it takes a bit for them to be initialised (temporary whitespace). That makes me think a dynamic solution is the only way to approach this properly

@jrieken I tried to do this, but it gets too complicated for me. Can you please do this, or guide me through?
I pushed my attempted fix, which doesn't work as expected.
It does hide the breadcrumbs bar, but when I edit the file it doesn't reach updateBreadcrumbs, so it is not shown.

@jrieken ?

Can you please do this, or guide me through?

Yes, I will do it but as a separate PR and only as soon as time permits

Thank you!


Plans for OData v4?

When I started the project I implemented v4 but switched to v2 quickly cause SAPUI5 didn't support v4.
In the meantime I stopped development of this project cause there were not enough collaborators and it's too much work for a one-man-show.


Promotion: Differentiate ZKPs with side-effect on basket and those without a side effect on the basket

Important difference in the app and handling of adding these to the basket after payment.

Done, see NoSideEffect and RewardSideEffect :)


Program forget last state when crash. Runtime error when attempting recheck torrent while other torrent is rechecking

0.15.0
Hello, when i attempt to recheck torrent while other torrent is already rechecking, then i see Runtime error and also other crash where WIndows 10 invite me to close the app, No other option.
And when i reopen app, then it forgets torrents i rechecked during the previous session.
THis issue with rechecking does not happen always apparently. But most important think is that Pico Torrent do not remember my changes, rechecks for whole previous session.

Can't reproduce this in #672 - closing this and should it happen again when 0.16 has been released, feel free to reopen 😄


fix: resolve jsxImportSource with types mode in absence of jsxImportSourceTypes

When there is a jsxImportSource and no jsxImportSourceTypes, we need to try and resolve the same specifier with ResolutionMode::Types to see if it resolves somewhere else, as we do with ES deps.
I hit this bug in the LSP specifically when using jsx import source npm:preact with byonm.

It looks like the lockfile changes occurred due to https://github.com/denoland/deno/pull/25059 -- I'm looking into why

Confirmed that https://github.com/denoland/deno_lockfile/pull/34 fixes the issue. I will land this in Deno and then we can merge this PR.

@dsherret Thanks, it's green now