global variable info is not defined. can you have a look?


I'm trying to find information on Mapboxjs 3.0.0 and 3.0.1. Should I point my production website currently using 2.4.0 at the newer version? I don't know what if it's stable, what is new, or if there are any breaking changes.


So I'm going to assume that I don't have to start finding new offsets then. Sweet! I am trying to get the offsets for armor and equippables now and I will make a pull request with a file that contains the offsets. I'm not that good with C#... I've been learning with your code


Same file is placed at shubhid/output.csv


So this is the same data structure from the earlier commit, which has thread-specific slots. In general, this "advanceTo" function is meant to be thread safe, because threads only access their specific data. I can add some comments and asserts.


Yes, but if the .js file references the .map file, every time one opens the develop console, the browser tries to find the referenced map file leading to 404s.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1699](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18720&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 287, ignored: 4 Build time: 00:11:10


Don't know if it's an issue, but this looks like an API break. Not sure if we can solve the issue without this break, though.


@serghey-rodin What do you think about replacing PHP-FPM with PHP7-FPM for Ubuntu 16.04? Will that cause any problems to Vesta?


I see...


👍 Cool But ... How about Simu witch have NO  icons ;-(

Thanks Miguel


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1700](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18723&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 259, ignored: 4 Build time: 00:10:04
### Failed tests
```
org.genivi.sota.core.PackageResourceWordSpec: <no details avaliable>

```


Looks great - thanks for fixing this issue. Raise a PR and I'll get it merged. Thanks again.


Hi there,
you wrote in the comment, the "bug" was caught by the unit tests. How do you test such things?
Thanks


Soy nuevo en esto, tengo una duda donde f¿configuro los datos del cliente, y donde le pongo el  API de google?


All right, I see the js file doesn't reference the map file so it should be OK.


Yeah, and I guess I should remove the `this->` in the call.


In case you haven't noticed I remove it a few days ago :)
Anything else you want me to do? ^^


You definetely have to suffix the search_path with $user and public for your queries to work properly: all core functions are in these schemas.
Tried it first without, made many problems.


Couldn't we do this without resorting to undefined behavior?

For example:

    #include <csignal>

    raise(SIGSEGV);


Don't forget to change the name of the variable in the declaration within the class ItemDocument on line 78:

private $public = false;

to

private $sharedpublic = false;


Replaced with `/* Constructor for cli_ui_out_impl.  */`.


saw approval from andytill
at https://github.com/basho/riak_kv/commit/a8c0bb27ee0dd8cec2a855cf7117cf5e2f903584


merging basho/riak_kv/fix-az-use_lk_to_pk_in_keyconvfun_to_unbreak_listkeys = a8c0bb27 into borshop-integration-1542-fix-az-use_lk_to_pk_in_keyconvfun_to_unbreak_listkeys


basho/riak_kv/fix-az-use_lk_to_pk_in_keyconvfun_to_unbreak_listkeys = a8c0bb27 merged ok, testing candidate = e2887eac


编译时注解


nothing important to mention here.


No problem, we all have to start somewhere. :)
The accessory offsets should be around the first block after the colors.


Yeah, I think it's more readable with lines between the different cases... I guess I changed it because I touched code right next to it.  Je vais essayer d'en passer une tite vite :P


same


nothing big to mention.


`splice` is not defined for the object, causing and error and the graph to never load.


I know the armor is right near the first quick slot because I've edited armor before. I will get my dump/inject workspace ready and start testing


It's probably a pre-existing bug, but "_source" may be a JsonArray according to the [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/search-request-source-filtering.html), so this call to `getAsJsonObject` might explode mightily.

Maybe we should add a check for this, and transform:

```
"_source": ["some*", "*patterns"]
```

... to:

```
"_source": {
  "include": ["*some", "*patterns"]
}
```

... before continuing?


And I've also seen the first slot of accessories too


Keep on writing comprehensive commit message (and a bit less developer/designer-oriented  :wink: ). It's appreciable


PHP 7 should be by defaullt on Ubuntu 16x


I also have one more thing to say. Be VERY careful when editing the header of the file. You can crash your Wii U if you edit the wrong thing


@FreifunkBremen/publicity
Da die Zeitumstellung und somit die Sommerzeit durch ist, denkt daran, dass wenn Ihr einen Blogpost verfasst nicht mehr `+0200` sondern `+0100` verwendet. Ich wurde gerade davon überrascht, dass der Blogpost früher als gedacht veröffentlicht wurde.


This fails with a DoesNotExist error if a bad org_id were to be passed in through the request.

Also, this method name is slightly misleading since it returns the organizations pk, not the organization itself, and there is at least one other, nearly identical method out in the codebase that uses the same method name and does return the organization rather than the pk.


LIGON FORM!!!!!!!!!!!


For this commit in particular, the impact for developers was bigger than for the enduser.

But I'll think of your statement in the next commit message I write :+1:


Atmel is present on both hydrogen and helium. My hydrogen is with Focaltech. I'll over the thread where we discovered this thing and find you a user with hydrogen atmel to test for you...


Those changes where the result of me trying to compile with VS2008 on a windows machine.  With gpuarray/config.h it works.  With stdint.h if fails complaining that it didn't find the header.


Already have the Header informations. 1 Byte looks like is the save version number.


Added an "app.config" file reference in the Artifactory.csproj file but didn't include the app.config in the commit.  Opening the Artrifactory.csproj results in "file missing" error on app.config.


Are you sure that you should not add the call to super after addChannelToMeasures?


![](https://github.trello.services/images/mini-trello-icon.png) [introduire un lock pour s'assurer de pas lancer 2 fois l'initialisation de l'instance](https://trello.com/c/AFJfh9oD/114-introduire-un-lock-pour-s-assurer-de-pas-lancer-2-fois-l-initialisation-de-l-instance)


What's the offset for a 1 character name for the save version number?


Je pense que c'est quand même clair comme ça, mais bon je l'ai changé et c'est clair aussi avec une fonction:

```
/* Helper to return the implementation behind UIOUT, casted to a
   mi_ui_out_impl *.  It is an error to call this function with an ui_out that
   is not an MI.  */

static mi_ui_out_impl *
mi_ui_out_impl_from_ui_out (ui_out *uiout)
{
  mi_ui_out_impl *impl = dynamic_cast<mi_ui_out_impl *> (ui_out_impl (uiout));

  gdb_assert (impl != NULL);

  return impl;
}

int
mi_version (ui_out *uiout)
{
  return mi_ui_out_impl_from_ui_out (uiout)->version ();
}

void
mi_out_put (ui_out *uiout, struct ui_file *stream)
{
  return mi_ui_out_impl_from_ui_out (uiout)->put (stream);
}

void
mi_out_rewind (ui_out *uiout)
{
  return mi_ui_out_impl_from_ui_out (uiout)->rewind ();
}
```


First website commit


Merge was very fast... maybe too fast.


Tagging @chrisbianca for review


I would prefer that names are as generic as possible, the name should reflect what it does, nothing more or less.

Btw, we should prepare for a new release, so any new stuff/fixes should be added today, as I will start testing for release tomorrow.


Pedro va probablement suggérer une façon super C++11 de faire ça anyway :P


Si tu veux, je me met a ça. C'est facile

On Wed, Nov 23, 2016 at 5:32 PM, Ingwie <notifications@github.com> wrote:

> 👍 Cool But ... How about Simu witch have NO icons ;-(
>
> Thanks Miguel
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Ingwie/NextStepRc_Dev/commit/9f8543bf62cdee2b7c2580fed0901187dbde6b43#commitcomment-19940712>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AVF8dQhx-PUfiYpRboQVIGTFPEAU6u09ks5rBGqhgaJpZM4K6y4s>
> .
>


done


0x01 => (MAYBE) Save Version
0x02 => Name Length
0x03 => Name start


missing once wrap around callback


The first yes. However, the second provides conditional functionality for the live `__call__` function resulting in two possible return values. That design practice should be avoided whenever possible.

The first question I have, is how likely is it that someone would want to retrieve only a single update? If not terribly likely, the interface to manually fetching a single update could be through just the LiveUpdate model constructor without a direct interface.

If you think it's common, it's again unfortunate because `reddit.live.update` unfortunately won't work. While the interface isn't pretty, we could do it by overloading the bracket operator like `reddit.live(thread_id)['update_id']`. That approach is used to obtain WikiPages because Subreddit.wiki is a list-like object. A live thread could be treated that way as well.


asd


asdad


I would not limit it, unless it is not night time. (complete_crawling == false)


dadad


da


asdafds


fds


sd


sdfgh


some changes like speed, size, steps per unit, homing direction and available end stops concern my physical machine setup.


ggg


gggg


Yes !! S'il te plais

Je dois finir le splash perso en priorit�.

----- Original Message -----
From: jmentero <notifications@github.com>
To: Ingwie/NextStepRc_Dev <NextStepRc_Dev@noreply.github.com>
Cc: Ingwie <theingwie@gmail.com>,  Comment <comment@noreply.github.com>
Date: Wed, 23 Nov 2016 08:47:19 -0800
Subject: Re: [Ingwie/NextStepRc_Dev] Menu icons added. (9f8543b)

> Si tu veux, je me met a �a. C'est facile
>
> On Wed, Nov 23, 2016 at 5:32 PM, Ingwie <notifications@github.com> wrote:
>
> > ?? Cool But ... How about Simu witch have NO icons ;-(
> >
> > Thanks Miguel
> >
> > �
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/Ingwie/NextStepRc_Dev/commit/9f8543bf62cdee2b7c2580fed0901187dbde6b43#commitcomment-19940712>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AVF8dQhx-PUfiYpRboQVIGTFPEAU6u09ks5rBGqhgaJpZM4K6y4s>
> > .
> >
>
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/Ingwie/NextStepRc_Dev/commit/9f8543bf62cdee2b7c2580fed0901187dbde6b43#commitcomment-19940981
>


using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Runtime.InteropServices.WindowsRuntime;
using Windows.Foundation;
using Windows.Foundation.Collections;
using Windows.UI.Xaml;
using Windows.UI.Xaml.Controls;
using Windows.UI.Xaml.Controls.Primitives;
using Windows.UI.Xaml.Data;
using Windows.UI.Xaml.Input;
using Windows.UI.Xaml.Media;
using Windows.UI.Xaml.Navigation;
using Windows.UI.Popups;
using System.Diagnostics;

// The Blank Page item template is documented at http://go.microsoft.com/fwlink/?LinkId=402352&clcid=0x409

namespace GuessGame
{
    /// <summary>
    /// An empty page that can be used on its own or navigated to within a Frame.
    /// </summary>
    public sealed partial class MainPage : Page
    {
        public MainPage()
        {
            this.InitializeComponent();
        }

        //Generate a random number
        static Random rnd = new Random();
        int rndNumber = rnd.Next(1, 10);

        //Method to reset variables
        public void Reset()
        {
            rndNumber = rnd.Next(1, 10);
        }

        //Method to handle user input
        public async void Guess()
        {
            try
            {
                int userInput = int.Parse(txtGuess.Text);

                if (userInput != rndNumber)
                {
                    if (userInput > rndNumber)
                    {

                        MessageDialog lower = new MessageDialog("The number is lower than " + userInput + ".");
                        lower.Commands.Clear();
                        lower.Commands.Add(new UICommand { Label = "Ok", Id = 0 });
                        var res = await lower.ShowAsync();
                        return;
                    }
                    else if (userInput < rndNumber)
                    {
                        MessageDialog higher = new MessageDialog("The number is higher than " + userInput + ".");
                        higher.Commands.Clear();
                        higher.Commands.Add(new UICommand { Label = "Ok", Id = 0 });
                        var res = await higher.ShowAsync();
                        return;
                    }

                }
                else
                {
                    MessageDialog correct = new MessageDialog("You guessed correctly! The number was " + rndNumber + ". Play again?");
                    correct.Commands.Clear();
                    correct.Commands.Add(new UICommand { Label = "Yes", Id = 0 });
                    correct.Commands.Add(new UICommand { Label = "No", Id = 1 });
                    correct.DefaultCommandIndex = 0;
                    correct.DefaultCommandIndex = 1;
                    var res = await correct.ShowAsync();
                    if((int)res.Id == 0)
                    {
                        Reset();
                        Guess();
                    }
                    else
                    {

                        MessageDialog congrats = new MessageDialog("Congratulations!");
                        congrats.Commands.Clear();
                        congrats.Commands.Add(new UICommand { Label = "Ok", Id = 0 });
                        var resi = await congrats.ShowAsync();
                        return;
                    }

                }
            }

            catch (Exception)
            {
                MessageDialog incorrect = new MessageDialog("Your input was invalid. Please try again.");
                incorrect.Commands.Clear();
                incorrect.Commands.Add(new UICommand { Label = "Ok", Id = 0 });
                var res = await incorrect.ShowAsync();
                return;
            }

        }

        private void getValue_Click(object sender, RoutedEventArgs e)
        {
            // Call the Guess method to check user input when they click a button.
            Guess();
        }
    }
}


sdftsgdg


I've seen it in some of Pedro's patches:

```c++
const std::vector<std::string> &wholly_collected ()
{ return m_wholly_collected; }

const std::vector<std::string> &computed ()
{ return m_computed; }
```

I'll change it so it's on two lines like his.


dfdfgdgd bitch


dsfsdfsdf


@AndreyEremeevEPAM  уже так сделал


Same error when I switch to using the 7.1 deps:
https://ci.appveyor.com/project/krakjoe/apcu/build/master.5#L3270


Ce tuto <https://openclassrooms.com/courses/gerez-vos-codes-source-avec-git>
peut
tout t'expliquer vachement bien :-)

En gros : d'abord tu clones ce (très petit) dépôt de code, ou tu n'a pour
l'instant que le README.md.
Ca va télécharger tout le dépôt chez toi.

Ensuite, tu ouvre bloc-notes ou n'importe quoi, tu modifie ce fichier
(voire tu en rajoutes d'autres).

Tu créé un commit (C'est dire en gros ("je viens de créer un nouvelle
version") )
Tu envoie ton commit sur le serveur avec git push.

Après, comme tes modifs sont sur le serveur, moi je pourrais les récupérer,
etc.

2016-11-23 17:26 GMT+01:00 Creutzer <notifications@github.com>:

> Du coup comment que c'est que je fais?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/faistos18/exemplePourJB/commit/7ceac48ba5db0ecb10438f6919fc9a21ae6fa510#commitcomment-19940642>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AIxD2tCQb6PG_ZvRosFEzk18JV0npTBVks5rBGlSgaJpZM4K6yeh>
> .
>


komentarz


koment


✔  for what your code example looks like

I would suggest starting with inheriting from object. If the code from `SubredditRelationship` can be shared then it probably needs to be renamed to be more encompassing and we can refactor that later if necessary.


Yes you are right. I though it required apt-get install php7-fpm but apt-get install php-fpm installs PHP 7 as well.

Thanks.

From: "anton-reutov" <notifications@github.com>
To: "serghey-rodin" <vesta@noreply.github.com>
Cc: "Alexandros Ioannides" <alex@ioannides.net>, "Comment" <comment@noreply.github.com>
Sent: Wednesday, 23 November, 2016 18:41:49
Subject: Re: [serghey-rodin/vesta] Merge pull request #927 from ioannidesalex/patch-5 (9a0b310)

PHP 7 should be by defaullt on Ubuntu 16x

—
You are receiving this because you commented.
Reply to this email directly, [ https://github.com/serghey-rodin/vesta/commit/9a0b31065eb26622136e08ae7fda9130c37e3802#commitcomment-19940855 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AVV3ionv5SO572FASRUn1EIVkgkIDYoTks5rBGzNgaJpZM4K6y3b | mute the thread ] .


I will double check but I believe the   DoesNotExist Errror does not occur here, but in the field validation which occurs before this,


This is not compiling at the moment:
```
mempool.h(37) : warning C4229: anachronism used : modifiers on data are ignored
mempool.h(37) : error C2143: syntax error : missing '{' before '*'
mempool.h(38) : error C2059: syntax error : 'type'
mempool.h(39) : warning C4229 : anachronism used : modifiers on data are ignored
mempool.h(39) : error C2143: syntax error : missing '{' before '*'
mempool.h(40) : error C2059: syntax error : 'type'
mempool.h(41) : error C2059: syntax error : 'type'
quality.c(105) : warning C4133: '=' : incompatible types - from 'int *' to 'alloc_handle_t *'
rules.c(781) : warning C4133: '=' : incompatible types - from 'Action *' to 'Action *'
rules.c(808) : warning C4133: '=' : incompatible types - from 'Action *' to 'Action *'
rules.c(817) : warning C4133: '=' : incompatible types - from 'Action *' to 'Action *'
rules.c(847) : warning C4133: '=' : incompatible types - from 'Action *' to 'Action *'

```


A quoi sert ce changement?


koment cos


thanks!

On Wed, Nov 23, 2016 at 11:42 AM, Padraig Gleeson <notifications@github.com>
wrote:

> @salvadord, see here for gap junction example
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/OpenSourceBrain/NetPyNEShowcase/commit/
> a239a2818a361610b64cccb92028b42c04948f45
>


@ioannidesalex well it seems like Ubuntu guys are going to use meta packages for php in next releases and I like that. The idea to name php package php7.0 sounds is a bit weird to me.

Frankly saying I never quite understood why  Debian and Ubuntu packagers are using names like bind9 or exim4 when there is dpkg tool for version handling. I guess it could be explained by some legacy issues.

So I welcome their decision to get rid of redundant verisioning in package name. For us it means less modification in the installer when new Ubuntu is released.


ok to komentarz


caly koment


wtfff XXDD


I changed it to the same format in ui_out_impl as well.


done


Ok.


dfgfdgf


Sorry for my poor explanation, and here is a complete version.

What is "cancelable"?

Current flow:
1. clicking the "advance summon" button
2. the system will show you the available tribute monsters

At this stage, a player can:
(a) select the tribute monsters
(b) cancel the advance summon and go back to ordinary main phase
The cancelable argument controls whether you can do (b) or not.

Although the information shown in step 2 seems trivial, it is still the result calculated by the ygopro system.
(By the way, it is NOT so trivial in certain cases like Soul Exchange.)
If the system allows "cancelable", a player can press the "advance summon" button, go to step 2 to see the computation result, and cancel his move to think again.

In a real card game, a player is supposed to make his move in game on his own.
By allowing "cancelable", we actually let the player use the information calculated by the system before they complete their move.
It is not allowed in a real YGO card game, and I firmly believe that this is not reasonable in ygopro either.

I believe that the fun in a card game is making the game stragety.

Allowing a player complete his stragety by the result calculated by other people or machine is by far a reasonable idea.

About the comments above
I try my best to read through all the comments above.
But there are too many comments, and I cannot reply all these comments one by one....
I am sorry for that.

About touchpad version:
I don't know much about apps on mobile device, so I can't tell what is suitable for the touchpad version.
But I do believe that this is a problem of GUI on touchpad version, allowing cancelable is just a compromised and even harmful solution.

About "punishing missclick":
There are other ways in GUI that can prevent a miss click, such as:
- Widen the command button
- Add a short delay between "clicking a card" and "showing the command list"
...and so on

We don't need to compromise on this harmful solution.

@DailyShana @mercury233
原本的流程是：
1. 按下"上級召喚"按鈕
2. 系統分析過所有卡片效果之後，顯示出目前可選的祭品怪獸

在這個階段玩家可以：
(a) 選擇祭品怪獸
(b) 取消目前的動作回到主要階段的一般狀態
cancelable控制的是玩家在這時可否選擇(b)

雖然步驟2的分析乍看之下只是顯而易見的計算，但無論如何這個步驟顯示的結果是系統按照現有效果計算後的結果
允許(b)的取消就代表玩家可以按下"上級召喚"按鈕，到達步驟2並且看過系統計算的結果後再取消回到主要階段

我同意"在自动处理效果的游戏中追求和实体卡相同的体验是不现实的。"
但是有一點我堅信的是：
卡片遊戲的樂趣在於自己想出能夠獲勝的操作過程

允許取消就等同於允許玩家看過系統計算的結果之後，以此為基礎再重新思考

無論是實體卡還是ygopro，
讓玩家看過其他人或機器計算的結果在執行自己的操作都是在某些程度上破壞遊戲性的作法

關於防止误操作
防止誤操作應該有其他GUI層面的辦法，例如放大按鈕的大小，甚至是在按下卡片後經過一小段延遲再顯示按鈕以預防連點等等
我的想法是不需要妥協於這種會破壞遊戲性的方案

@IamIpanda
很抱歉我解釋得不夠清楚
這裡的"可取消"指的是已經按下"上級召喚"按鈕，並且進入選擇祭品的畫面之後仍然可以回溯到主要階段
由於上述理由，我認為這並不合理，而反覆瀏覽額外牌組並不會受到影響


To reproduce the error, flush the log so that the data doesn't start at index of 0. Then the JSON gets parsed/created as an object.


gfjhudc


Haha, it was meant for you actually, so that was surprising 😁


Hello,
Thanks first of all for Aurora, it is really an amazing software!
I've added here support only for Roccat peripherals, and not for the Ryos Keyboard, which requires some more work. It works relatively well, the device is initialized and the color information is correctly transmitted. I've run into problems though. My mouse (which is the only Roccat device I have at my disposition) shows way more blue that it should, this is why I've added a may to rescale the color. Also, it seems that I can't really change either the effect type or speed. I think it is because of the way I've done it. It is far from being finished.
I have considered doing a pull request, but since it isn't fully functional, I haven't.
I will probably redo it in the following days, hopefully correcting everything I've mentioned above.


same


drfegdsgh


fhdfthdrf


fhfdhdf


gcdfhgfhgfh


ghgfhf


Yeap you are right on this. I can't understand this either. apache2 as well (I mean come on who is using apache1 anymore)

From: "Serghey Rodin" <notifications@github.com>
To: "serghey-rodin" <vesta@noreply.github.com>
Cc: "Alexandros Ioannides" <alex@ioannides.net>, "Mention" <mention@noreply.github.com>
Sent: Wednesday, 23 November, 2016 18:51:04
Subject: Re: [serghey-rodin/vesta] Merge pull request #927 from ioannidesalex/patch-5 (9a0b310)

[ https://github.com/ioannidesalex | @ioannidesalex ] well it seems like Ubuntu guys are going to use meta packages for php in next releases and I like that. The idea to name php package php7.0 sounds is a bit weird to me.

Frankly saying I never quite understood why Debian and Ubuntu packagers are using names like bind9 or exim4 when there is dpkg tool for version handling. I guess it could be explained by some legacy issues.

So I welcome their decision to get rid of redundant verisioning in package name. For us it means less modification in the installer when new Ubuntu is released.

—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/serghey-rodin/vesta/commit/9a0b31065eb26622136e08ae7fda9130c37e3802#commitcomment-19941057 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AVV3iu1lvndKujuNWFZHrYljbxr0V9T5ks5rBG74gaJpZM4K6y3b | mute the thread ] .


gfdhfdg


ghfd


This does not really fix #11270 which is a login issue happening before playlist download.


ghfdh


done


We shouldn't use `application.properties` file in libraries, because they're loaded non-deterministically. Shouldn't we perhaps consider using an autoconfigured EnvironmentPostProcessor ?


gfhfh


ghfhdh


komentarz do linijki


ghfdhhgf


partial fix 77098be4d84b57d3859529788ddd97084f7bed50


ghfdhdfh


0x01 is 15 for a 1 character name. Is this what you have for that offset?


Dans des reviews, Pedro disait de les enlever lorsque c'était pour accéder à un membre `m_*`.  Avec le préfixe, ça rend ça clair.  Quand on appelle une autre méthode, je sais pas à quel point c'est clair si on le met pas...


Nope. 0x02 is name.
0x01 is 15 for all chars from the new version. Last version was 13


The API endpoint appears to allow you to either invite or directly add someone as a contributor. Thus I would do away with the `type_` param and instead have two methods:

 * `thread.contributor.add`
 * `thread.contributor.invite`

Note that ModeratorRelationship has these two separate methods:
https://github.com/praw-dev/praw/blob/f4a600ba5a84b5ab1b29c4895cac38cfe171076d/praw/models/reddit/subreddit.py#L841


Genre
```
this->field_string (fldno, width, alignment, fldname, buffer);
```
vs
```
field_string (fldno, width, alignment, fldname, buffer);
```


Should this be an expression so that we don't build the string every time?


Olha a quantidade de adições e fica quito cara!!! kkkk


* trusted sanitizer as a nunjucks filter
* bug on occ gallery fixed (displayed first media not first image)
* scientific name in gallery
* table styles
* new fonts
* general styling sitewide


On the other hand then we waste memory storing the string and the listeners.


yeah, sorry. will do that.


bonito se a professora olha nosso código aqui kkk


「あぼーん」が含まれている場合、見た目なんとなく正しいのだけれどhtmlがぐちゃぐちゃになる現象が発生。なので、「あぼーん」が含まれるケース限定のreplaceパターンを記述。

また、「broken」クラスを追加。NGではない運営のレス削除などの「あぼーん」にのみクラスを付与。

「あぼーん」を含むdatの例
ref: http://kohada.open2ch.net/yume/dat/1457048022.dat
```
名無しさん＠おーぷん<><>2016/03/04(金)14:27:36 ID:???<> みんなで削除依頼何回も出せば独占してる奴アク禁になるんじゃねえ？ <>
あぼーん<>あぼーん<>あぼーん<>あぼーん<>あぼーん
あぼーん<>あぼーん<>あぼーん<>あぼーん<>あぼーん
あぼーん<>あぼーん<>あぼーん<>あぼーん<>あぼーん
名無しさん＠おーぷん<><>2016/03/04(金)21:02:52 ID:???<> 表現の自由と言えば他者に迷惑かけても良いと思っている害悪がここにｗ <>
```


LGTM


How should I install this?

Best wishes,

Jon


@Aranud Spaces?


This may be related (although apcu does not depend on php_sysvshm.dll on PHP 5):
```
C:\php-sdk\php71dev\x64\Release\php-7.1.0RC6>type php.ini
extension_dir = "ext"
extension=php_sysvshm.dll
extension=php_apcu.dll
;extension=php_apc.dll

C:\php-sdk\php71dev\x64\Release\php-7.1.0RC6>php-cgi -m
PHP Fatal error:  PHP Startup: apc_shm_attach: shmat failed: in Unknown on line 0
```


Same here


There is also one group (70-80) where noone survived. By setting the age labels manually to this, you are hiding the group.


komenrtarz]


asfasfasfasgf


asgasgasg


kasnfhkashfasfhgasdgghasjghjgasjhlkjasdklj


xvzXZvXZV


bzxcbXCbzxcb


change v.1.2


xczbxzcbxcb


no jak to tak mozna tutaj


ahaha


Missing update in the description: This CL does in fact delete `ParserOptions`.


all tests pass:
success: http://buildbot.bos1/builders/test-riak_kv/builds/4317


HAH. I still missed one!


@cyberium broke Escort AI by putting JustSummoned in AIM INIT, (valid change, not without consequences). If I recall correctly he didnt fix it yet, since I still have the 4 month old hackfix in my core. I told him about it twice, I even provided solutions. + there is an issue about it, but its not called like that.


Regardez au niveau des requêtes SQL ce qui se passe.

https://laravel.com/docs/5.3/eloquent-relationships#constraining-eager-loads


This just started failing for me too. I'm using your old (non chef) clean-winsxs.ps1 script

```
==> virtualbox-iso: Provisioning with Powershell...
==> virtualbox-iso: Provisioning with shell script: scripts/windows/common/clean-winsxs.ps1
    virtualbox-iso: Cleaning up WinSxs, This could take a long time...
    virtualbox-iso:
    virtualbox-iso: Deployment Image Servicing and Management tool
    virtualbox-iso: Version: 6.3.9600.17031
    virtualbox-iso:
    virtualbox-iso: Image Version: 6.3.9600.17031
    virtualbox-iso:
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Script exited with non-zero exit status: 16001. Allowed exit codes are: [0]
```


I made some of these changes too... I'm trying to pay attention to the eslint errors!


Votre clavier ne possède-t-il pas le "é" ?


You're welcome 👍


Master branch: minor modifications are available.


ne serait-ce pas plus joli d'avoir ceci dans l'URL ?


This will miss something like `$_\alpha`


Please @domschiener next time, send a pull request.


1. **great job jon!

@@jon

- [ ] 1.

keep it

- [ ] up!#**


Closes #89


That's what this commit fixes


Trial


changed ubuntu version to trusty64


저번에 comment 해주신, "사용자 입력은 별도 클래스로 분리해서 만들어도 좋을 거 같네. 사용자 입력 받으면 그걸 Command 같은 걸로 변환해서 리턴해주는..."에서 사용자 입력받으면 command 같은 걸로 변환해서 return해주라는 말이...어떤,,,동작이에요? switch case문에 literal들 대체해주는 enum class 하나 만들라는 뜻인가요?
메모 입력하는 부분을 시작하려는 데, 그냥 하려니, list로 할 지 map으로 할 지부터 결정해야겠네요..;


I have an issue because of this. My entity have two methods, getExpired() and isExpired()  and  when in twig view  I use object.expired|date  isExpired()  is triggered and  date displaed as 1970....


Looks good!  Looking forward to talking more about it this evening!


> @cyberium broke Escort AI by putting JustSummoned in AIM INIT

Killerwife. What are you talking about? https://github.com/cmangos/mangos-tbc/blob/master/src/game/Creature.cpp#L768 <- That's AIM_INIT. Where's the JustSummoned call?


Ok. homework is completed!!!


no, you have an issue because this is *not* there in the latest stable relase


Confirmed. I'll open a PR with a solution soon.


nice job


HTML dans JavaScript c'est presque aussi joli que dans du PHP.

N'avez pas moyen de mettre ça côté PHP et réutiliser vos templates _blade_ ?


Enables this additional field:

![screen shot 2016-11-23 at 12 10 15 pm](https://cloud.githubusercontent.com/assets/1117989/20571545/e239750a-b175-11e6-9ac9-280635aa0e22.jpg)


Why is skipping better than instead using an empty lambda?


Creates a stairs of hash tags. This uses the delete method for array elements.


Background information: http://tech.scargill.net/banana-pi-m2/#comment-27941

It would be great to identify a specific device based on DT or machine entry in fex file (thinking here about a more generic approach suitable for other distros too. In Armbian it's already easy since there is `/etc/armbian-release`)


## renameと言いつつ色々変更していた。。

### スレ一覧　→　スレッド一覧 に変更
理由は、スレ一覧という言葉はopen2chに出てこないから。

### consoleなどを削除
理由は、一通り役目を終えたため。また復活するかもしれないが:confused:

### _getLocalJSON を追加
実はこの関数追加がメインだったと思う。。
bbsnameJを取得するのに修正前はhistoryを見に行くロジックだった。
しかし、historyは削除されるかもしれない、つまり永続的なものではない。
そこで、永続的にbbsnameJを保持するためのkey-valueなものが欲しくなった。
しかし、background.jsにそのkey-valueなるものをハードコーディングするのは、量が多すぎるので無理である。なにせ、板は800ぐらいあるので。。。
そこで、あらかじめ板リストをJSONで取得しておき、bbsnameからbbsnameJを引っ張ることにした。
これでbbsnameJが取れなくなることはほぼほぼなくなった。
ただし、板リストに全ての板が網羅されているとは限らないので、

- 板リストにbbsnameJがあればそれを使う
- 板リストにbbsnameJがなければ
  - 履歴からbbsnameJを探し
    - 履歴にあったらそのbbsnameJを使い
    - それでもなければbbsnameをbbsnameJに設定する

というロジックになった。

### NGキーワード登録処理を少し整理
これは説明が面倒なので、修正後のコードを見ての通りです。


JustRespawned, my bad


Nice 👍


 Request | Time
------------ | -------------
~50 Orders | ~2s
~300 Products | ~6s

Seems to work great now. Have you tested the reference issue?


I have 01 at 0x02 though. That can't be right


Copy me your bytes from 00 to 0F


fast-forwarding riak_ts-develop to borshop-integration-1542-fix-az-use_lk_to_pk_in_keyconvfun_to_unbreak_listkeys = e2887eac


2 things
a) you no longer need the Bitboard b
b) it would be more logical if  line 853 would be using - instead of +


ref: https://gist.github.com/awn-git/202b7342924e6c86b4094a95194f1e1b

```javascript
// note: bbsmenuから bbsname -> bbsnameJ なJSONを作る
// ref: http://menu.open2ch.net/bbsmenu.html
var bbs = document.querySelectorAll("a");
var outobj = {};
for(var ix = 0, len = bbs.length; ix < len; ix++){
	if( (bbs[ix].href).indexOf("http://") > -1 ){
		outobj[ (bbs[ix].pathname).replace(/\//g,"") ] = bbs[ix].innerText;
	}
}
JSON.stringify( outobj );
```


@neildf, is this whitespace intentional?


00150131000100000100640064000000
The character's name is 1 btw. I was testing with name lengths


fajny commit


bardzo mi się podoba


fajna linijka


I agree, reason why I was in doubt about its documentation until I see the dialog in qt.


podoba mi się


It's correct. 31 => Char for 1 and 01 at 0x02 is the length of the char name. 1 char


co dzisiaj pijemy?


#Final Schematic


a no może jakiś sok


a może jednak pepsi


no może dobry pomysł


ale mielismy komentować kod!


a no tak, zapomniałem


Did you do this ?


hahahaha


to już ostatni


#include<stido.h>


I'm guessing that assumes the OrgValidatorMixin is supplied to the serializer.  If the OrgQuerySetMixin is used on a view without the serializer validator, like with GreenAssessmentViewSet, then it breaks with DoesNotExist.


it is not in 1.28.1 ?


Why not global STATICBOXINFO ?


Fixed in master, thanks!


@randalburns this should work. I added both singed and unsigned to ndtype. Did you pull the latest ndlib?


@Miskerest did this get into the code? if so it's not good.


You know python infinitely better than me,.. still tons of " endif;" and ; after set_stage


Misspelled "canola"!


komentarz 4 dyskusja


What's up with these "--lax" options marked "OK"?


Vergiss meine Frage.
Ich hab deinen vorhergehenden Commit nicht gesehen.


updates for #25  and #26


@dukeboard maybe we should remove the generated js files from the git?


The following doc(s) have been deployed to the [terminusof](https://terminusof-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/terminus/examples](https://terminusof-static-docs.pantheonsite.io/docs/terminus/examples)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/_partials/footer_scripts.html)
- [source/docs/assets/css/main.css](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/docs/assets/css/main.css)
- [source/docs/assets/scripts/reset-dev-to-live.sh](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/docs/assets/scripts/reset-dev-to-live.sh)


Three might be a better solution to handle exception.


@daspecster I'm very interesting in what Sphinx error was caused by the seemingly valid

```
``0.0 - 1.0``
```


Sharp eyes!  You are right.  But since TikaLinkExtractor is not as flexible, I know it will fail these new tests.  I added a TODO note about either updating it in a future release or simply deprecating TikaLinkExtractor since it does not bring anything over using the default generic one.


what is this?


Yikes, sorry I missed this when doing the `logLevel` plumbing! :-/ It is now fixed. And indeed the IDE does not use `deploySite` (nor `deployDoc`) for that matter so this will just affect deployments from the R console.


Be careful thee order is in the device sensor list. Not the sensor order


Pretty good. A thing i was waiting for years. GJ!


but the JustRespawned call, we want to do that, right? Is that call breaking escorts? that'd be news to me at least.


You don't need the label here, as yuo don't use it in this task


forse non ha preso la nuova immagine. Per ambiente invece tutto ok


debug trace?


You may have already seen this, but the previous code (which called the private `pandoc_html_highlight_args` function w/ extra arguments) has broken a couple of packages on CRAN:

https://www.r-project.org/nosvn/R.check/r-patched-linux-x86_64/MetaIntegrator-00check.html
https://www.r-project.org/nosvn/R.check/r-patched-linux-x86_64/filematrix-00check.html

Is there a way to propagate the fix into the version of Bioc CRAN is currently using? (v3.4 ).

As an aside, the comments for the forked version of `html_document` indicate that the fork was to change one aspect of MathJax behavior. I'm happy to make whatever change you need directly in `rmarkdown::html_document` so that the fork is no longer necessary.


Go try shattrath City of Light escort quest. It should be broken to my last knowledge. JustRespawned is called for Tempsummoned Escort AI mob which makes the mob think it "died" inbetween calling the constructor and JustRespawned.


If you write Hello Anna instead of Pamrpapanrampa you can have 1 line shorter code.
That's one line shorter fun though :)


yeap, go ahead


Good luck with this !
Maybe a smaller SafeCheck bonus will work better ?


This graph operations are super hard to follow. We need to find a way to make this simple. I think entries need to hold more state somehow.


это синхронная операция?


Please use gitignore :)
Otherwise nice job 👍


@rburkey2005 I locally have an alternate scan of R-700v3 (though I can't for the life of me remember where I got it if it wasn't from your site):
![unharmed_table](https://cloud.githubusercontent.com/assets/94056/20572244/8d1a000a-b15f-11e6-8ae0-ab6d3aaf50a0.png)

It's not as easy to read but didn't have destructive OCR performed.


加油


That makes sense, the validator mixin was originally used on viewsets,  I used to  use a try except loop to catch this and throw a validation error ,but the validation error didn't get reported correctly, so I switched to using the serializer and  I took it out as it was getting caught by the field validator.  Since the other mixins get used after validation (right before the serializers saves) its right  at the end of the process. I took a quick look at the DRF source code and I might be able to raise PermissionDenied which would get better handled, and seems appropriate in this case.


there are times plugin can tell us or give us a clue. This is an optional field, imo. If plugin thinks it knows better, I let them be.


minor, but shouldn't this be FAST_VECTOR as two words


Guys, I've added a requirement we overlooked about duplicate bucket names. Feel free to add/clarify this. With this set of requirements, bucket names `hiking` and `Hiking` would be different buckets unfortunately, but this would simplify our work.

Another option we could do is convert bucket names to lowercase (like we already do for email and username fields). The downside here is that this might make some bucket names less readable to the user. Bucket `HappyBirthday` would get converted to `happybirthday`. Maybe this isn't a big deal, though.

**What does everyone think? Please comment with your suggestions.**


Через `_` це приватні методи, не треба їх використовувати


sude_users={188179863},--sudo users


+1 on the rename


In an automatic simulator, hand-holding elements are inevitable. With that logic, we should also force players to hold A in order to use an optional trigger effect.

An IRL example would be if Player A had a Summoner Monk and another monster, and attempted to tribute Monk to summon a Monarch. Player B or any other observer would point out that Monk couldn't be sacrificed. Player A would have to return the Monarch to hand and Monk to field to correct the game state. However, the judge wouldn't force Player A to tribute the other monster.


for one, it is not complete because of the configuration we were talking about.


@akoeplinger it's great that it was already fixed in master, looking forward for fix it in v4.8


Oh dear... didn't mean for you to have to write so much code for this problem...

Remind me to buy you a couple beverages of your choice at next gcc / food / something. Really appreciate you working on this.


I'll look at adding test coverage for this.


I don't get why exception was needed, pls explain tomorrow :)


commented code


sude apt-get update


`ListElement.prototype = {}`
Такий підхід міє право на існування, але в нього є недоліки, не зможеш зробити наслідування.


awesome!


Robert,

I guess you’re correct with the long-range behavior of the perturbed density. My current test case is the nuclear gradients of the PF3 molecule which is very compact and very singular, and I have not tested Rydberg states with the new code yet.

The current rationale is that only where the density is well defined the xc functional, potential and kernel are well defined. Once the density drops below the threshold, the density, the density gradients and subsequently all derivatives of the functional are consistently set to zero (by virtue of the log derivatives), and their product with the perturbed density should also vanish. In that sense the binary munging should even be redundant.

However, currently I’m munging the GGA parts of the kernel tighter (usually ggatol = 1e-4) than the LDA parts (default rhotol = 1.e-7).  I can’t compute the derivatives of the perturbed densities with the log trick, so they are not (yet?) as stable as the ground state densities. These parameters should be tested more extensively though, and they should also be related to the MRA thresholds.

On another note, the gradients of the perturbed densities (esp if they are related to heavy nuclei displacements) cover many orders of magnitude, they are proportional to something like e.g. (Z^2 x y)/r^4 for the x electronic derivative of the y nuclear derivative. Taking the div operation after multiplication makes it even worse..

So far my experience with GGA kernels is that they just adds noise to the fairly stable LDA kernels, and in the PF3 case I can’t even converge the CPHF equations.

Florian

> On Nov 23, 2016, at 4:48 PM, Robert J. Harrison <notifications@github.com> wrote:
>
> Florian ... thanks for the pull request. I am reading through it and have
> asked Scott, Hideo and Bryan to also take a look.
>
> One quick question is about the screening routine for the perturbed density
>
> double binary_munge(double rho, double refrho) const {
> if (refrho<rhotol) rho=rhomin;
> return rho;
> }
>
> where rho is the perturbed density and refrho is the ground state density
>
> Since the perturbed density can be much more diffuse than the ground state
> density this screening does not seem correct ... i.e., it forces (in this
> context of evaluating the xc functional) the perturbed density to have the
> same foot print as the ground state.
>
> At long range the ground state density is dominated by the HOMO
>
> rho(r) ~= phi_homo(r)^2
>
> So the derivative density looks like
>
> rho'(r) = 2 phi'(r) phi(r)
>
> We can bound phi'(r) as being O(1) ... e.g., if it is decaying very slowly
> or is even in the continuum. Thus, we have
>
> |rho'(r)| <= O( |phi(r)| )
>
> So we might have |rho'| ~= sqrt(rho)
>
> Circling back to the code ... the screening would likely not impact valence
> excitations or properties, but Rydberg excitations and higher-order
> response properties could be incorrect.
>
> Since the functionals can accommodate a negative response density why do we
> need to screen it? Is the problem actually in correct screening of the
> ground state density (and sigma) in higher-derivatives of the functional?
>
> Robert
>
>
> On Monday, November 21, 2016, fbischoff <notifications@github.com> wrote:
>
> > After the little mishap the other day I’ve pushed a branch
> > “multi_to_multi” with my proposal for xcfunctional. Comments and changes to
> > the proposed code are welcome.
> >
> > I’ve implemented a multi_op_values which returns a vector as result, so
> > that all grid operations in xcfunctional can be done without reprojection
> > into the MRA basis, and libxc needs to be called only once. All preparatory
> > work is done in prep_xc_args in XCOperator, as before. The user only needs
> > to construct an XCOperator and call its methods.
> >
> > The commits change the interface to xcfunctional, so I can retain the old
> > API for the current code. However, the new code is faster and numerically
> > more stable.
> >
> > Florian
> >
> >
> >
> > > On Nov 19, 2016, at 6:39 PM, Florian Bischoff <
> > florian.bischoff@hu-berlin.de
> > <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de');>> wrote:
> > >
> > > I’m sorry for that.. The idea was to have a pull request as a starting
> > ground for discussion. I will undo the changes, if not today then on Monday.
> > >
> > >
> > >> On Nov 19, 2016, at 6:31 PM, Robert J. Harrison <
> > notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> > >>
> > >> Can we please have design discussions before changing to commonly used
> > >> APIs? There's lots of code using the XC library including in forks and
> > >> branches not merged with the main stream.
> > >>
> > >> In December I plan to take the next step in implementing the separation
> > of
> > >> core and application codes that we agreed upon doing. Stuff that is core
> > >> needs a communal approach.
> > >>
> > >> On Nov 19, 2016 11:05 AM, "fbischoff" <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> > >>
> > >> Sorry, last two commits were meant to be a pull request..
> > >> I've implemented a vector to vector operation and reimplemented
> > >> xcfunctional to avoid frequent projections of the xc potentials into the
> > >> MRA basis, which should improve efficiency and numerical stability.
> > >>
> > >> —
> > >> You are receiving this because you are subscribed to this thread.
> > >> Reply to this email directly, view it on GitHub
> > >> <https://github.com/m-a-d-n-e-s-s/madness/commit/
> > 8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19891272>,
> > >> or mute the thread
> > >> <https://github.com/notifications/unsubscribe-auth/AHMgPUk9q0dZAd-
> > 1CwuGRMYGy_r4V0-uks5q_x4ugaJpZM4K3Sht>
> > >> .
> > >> —
> > >> You are receiving this because you commented.
> > >> Reply to this email directly, view it on GitHub, or mute the thread.
> > >>
> > >
> > >
> >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/m-a-d-n-e-s-s/madness/commit/8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19902876>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHMgPdreUi-C_3dfK6iQgK7ytny0EjFvks5rAZN4gaJpZM4K3Sht>
> > .
> >
>
>
> --
> Robert J. Harrison
> tel: 865-272-9262
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


According to ascii, the start of the name is at 0x03
I will also copy over the first line of my other test characters to show you that 0x02 was correct when you first had it


dyskusja kom


Mi ero sbagliato e avevo caricato il vecchio file. Ora è ok


6e0bd1b Sorry, it was in the queue; forgot to sync :)


same here: why do you need exception?


Hi @basvandijk , adding an unqualified reference to `glibc` like this breaks the `postgresql` build on Darwin, where we don't use `glibc`.  The exact error is:

```
while evaluating the attribute ‘propagatedNativeBuildInputs’ of the derivation ‘postgresql-simple-0.5.2.1’ at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/development/haskell-modules/generic-builder.nix:158:3:
while evaluating the attribute ‘nativeBuildInputs’ of the derivation ‘postgresql-libpq-0.9.2.0’ at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/development/haskell-modules/generic-builder.nix:158:3:
while evaluating the attribute ‘postFixup’ of the derivation ‘postgresql-9.5.5’ at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/servers/sql/postgresql/default.nix:7:5:
while evaluating ‘callPackageWith’ at /Users/johnw/.nix-defexpr/nixpkgs-next/lib/customisation.nix:95:35, called from /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/top-level/all-packages.nix:7112:11:
while evaluating ‘makeOverridable’ at /Users/johnw/.nix-defexpr/nixpkgs-next/lib/customisation.nix:54:24, called from /Users/johnw/.nix-defexpr/nixpkgs-next/lib/customisation.nix:99:8:
while evaluating anonymous function at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/development/libraries/glibc/default.nix:1:1, called from /Users/johnw/.nix-defexpr/nixpkgs-next/lib/customisation.nix:56:12:
assertion failed at /Users/johnw/.nix-defexpr/nixpkgs-next/pkgs/development/libraries/glibc/default.nix:8:1
```


salix的核心观点是“讓玩家看過其他人或機器計算的結果在執行自己的操作都是在某些程度上破壞遊戲性的作法”，就此点反驳如下：

1.可取消对于这个游戏性造成的所谓破坏远远小于移除可取消对玩家造成的体验下降。考察过玩家实际情况之后会发现被反驳观点是主观的。
2.科乐美的官方规则是即使玩家已经叠放了卡片或者移动了同调素材，甚至是拿出了卡片放在桌子上，只要没有明确拍出在指定位置都可以反悔。
3.由于某些原因，攻击不能取消，如果是由于出于统一考虑的话我可以pull攻击的可取消而不是关闭所有取消的设定。
4.可取消是白银在多年前用了很多心血做出来的，在设计上面参考了游戏王的许多官方设计，也是这个ygopro设计的一部分。
5.事实上ygopro设计目标从来不是模拟实卡，模拟实卡是dn和nbx的目标，ygopro就是因为给用户提供的巨大方便才能发展到今天。

综上所述：“取消” 于情，于理，都不该移除。

在中国的一些游戏王社区已经有投票贴。如果要求取消的呼声强烈或者在一段时间内事实证明可取消的必要性，我会重新pull入可取消的代码，并补全可取消攻击的代码。


I think I'll transcribe it for the site, thanks!  I spent quite a while this morning looking for a better version, without success, but I did find vol. 2, which had previously been missing.


Well, the regression is part of Twig 1.28, and this commit fixing it will be part of the upcoming Twig 1.28.2 (not yet released.

Btw, the github interface shows where this commit is. And for now, there is no tags listed here:
![github_tags](https://cloud.githubusercontent.com/assets/439401/20572562/453c9c32-b1ac-11e6-8a81-f4fec7de5c8d.png)


I actually just came across this issue with a button not working inside an ion-item (at least, I had a click handler on the ion-item and a click handler on the button that is nested in the ion-item.

What is the best way to handle this? The best solution I thought of (but didn't implement) was just wrapping a div outside the ion-item and then making the button a sibling of the ion-item

Sent from my iPhone

> On Nov 23, 2016, at 3:02 AM, Gabriel González <notifications@github.com> wrote:
>
> So in RC3 is no longer possible to have buttons inside items? I cannot get click event in an ion-button inside an ion-item. In RC2 it worked calling $event.stopPropagation() in the button's handler.
> Thanks
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


нащо ти все через підкреслення?
так позначаються приватні методи


thanks @answer261 !


Another thing that came up, we should cache the roots we find per fact type.  Looking this up at runtime is unnecessary and does take up a non-trivial % of the time of the alphas fn returned.

So basically we need to return something like
```clj
[[fact-type1 roots] [fact-type2 roots] <etc>]
```
here so that we already know the roots that go with a fact type later when we do the `insert-or-add` calls.


Притримуйся однакової поведінки в своїх методах


Name: 12
Hex 00 - 0F: 00150231320028000001006400640000

Name: 123
Hex 00 - 0F: 00150331323300040000010064006400

Name: 1234
Hex 00 - 0F: 00150431323334002C00000000640064

Name: 12345
Hex 00 - 0F: 00150531323334350014000001006400


`return arr.filter(func)[0]` is also possible


Краще написати:
`if (this != b) return "";`
так менша вкладеність


In that case, here's the PDF I have saved: [r-700_volume3.pdf](https://github.com/virtualagc/virtualagc/files/609598/r-700_volume3.pdf) :)


Sorry I will fix, thanks for attention


А взагалі не бачу в цьому проблеми, що this == b, просто нічого не роби


I'll remove them for now, we'll see what people say on the ML.


Я б вертав true, або нічого


`arr.sort()` is an option instead of two else blocks


ciekawa dyskusja


sphinx chokes and throws a build error for bad indentation :( But I can rearrange it in some way I suppose.


bardzo


В тебе тут багато дублікації коду, спрости якось.


```
/vision-usage.rst:66: ERROR: Unexpected indentation.
```


how do I set the desired port with this change?
which config file do I modify?


Shouldn't this be remapped to keyword?


Yes I agree it seems nicer


Actually, it is my RST plugin that has a bug in it. 😠


Спрости, подебаж.


Dear @AndreasHeger, this [does not seem to exist](http://pandas.pydata.org/pandas-docs/stable/generated/pandas.Index.html), did you mean `dataframe.index` or `dataframe.index.names`? I think probably the latter, I have a commit to fix this but no permissions to create a new branch. Jakub


@gbprz can you tell me where this js file comes from?  It's not in the repo, and no cities are coming up for me or other users...  was this url supposed to point somewhere else?


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1701](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18733&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


some info http://stackoverflow.com/questions/6973942/is-optimizing-javascript-for-loops-really-necessary


haha je suis curieux mais par exemple, un tip de quand j'etais dev mac...

Tu est pas oblige d'ecrire from_What dans le func name comme avec le func overloading etc  c'est deja defini par le type et tu peut reutiliser ca...

fk tu peut avoir une fonction : mi_ui_out_impl_from (type var) et overloader ca  comme ca t'as juste 1 func.


The following doc(s) have been deployed to the [terminusof](https://terminusof-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/terminus/examples](https://terminusof-static-docs.pantheonsite.io/docs/terminus/examples)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/_partials/footer_scripts.html)
- [source/docs/assets/css/main.css](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/docs/assets/css/main.css)
- [source/docs/assets/scripts/reset-dev-to-live.sh](https://github.com/pantheon-systems/documentation/commit/08dfc80c7a9ba9773d25b867a499a5b0cb4963cf/source/docs/assets/scripts/reset-dev-to-live.sh)
- [source/docs/assets/scripts/reset-dev-to-live.txt](https://github.com/pantheon-systems/documentation/commit/a0a8647349f622e8ede89a87d8c3923820e3425a/source/docs/assets/scripts/reset-dev-to-live.txt)


You missed some globals at [lyke_individual.h](https://github.com/richelbilderbeek/pbdmms/blob/lyke/lyke_individual.h#L12) @LykeStuurman ... :beach_umbrella: :cocktail: :city_sunset:


Done


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1702](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18735&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


I think this broke RF with a fresh Blender 2.78a install.  looking into it now


А чого ти конструктором не користуєшся?


Interesting, worked perfectly in all my tests, although I neglected to try installing fresh.


`result` is never changed


Спрости, бо зараз це читати неможливо


if `func(arr[i])` is always false the next line will never execute. it's good to write tests for this first.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1703](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18737&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


is this way id or graphid?


if its way id i think we should call it  `way_id` since that is what we call it on input


id is graphid
base_data_id is wayid


I think I'll have to post both full copies of volume 3.

But transcribing the table is harder than it sounded in my head.  There's some very dubious info (though conceivably correct) in the original table, which is unfortunately not legible in your copy either.  For example, in the OCR'd copy, 2021112-111, Jan. 1970, is at Rev. 9, but -121, Feb. 1970, is Rev. 1.  How could that be?  In your copy, it _might_ say Rev. 9, but then again it might just be crapped up.

In reality, as long as the dates and version codes for the various missions agree, I think I'll just let the table as it was.


> In a real card game, a player is supposed to make his move in game on his own.
By allowing "cancelable", we actually let the player use the information calculated by the system before they complete their move.
It is not allowed in a real YGO card game, and I firmly believe that this is not reasonable in ygopro either.

The player should have this information, and does have this information during a tournament setting or when facing a knowledgeable opponent. By making a "mistake" they are forced to revert the game state by their opponent or a judge. This is not possible in YGOPro. The system assumes the user intentions. "Trust but verify" is the saying. Inversely YGOPro provides information to the user to prevent illegal moves by telling them what they can not do.

If complete accuracy is your goal YGOPro is not the medium for this. Platforms like DuelPortal and DuelingNetwork are.

> I believe that the fun in a card game is making the game strategy.

Others hold an extremely opposed view to this, and this commit is harmful to that logic as it punishes misclicks, temporary lapses in judgment, and obscures information when it is suppose to be assisting the user.

> It is not allowed in a real YGO card game, and I firmly believe that this is not reasonable in ygopro either.

This is false. A player is allowed to ask a judge reasonable questions about allowed moves to prevent themselves from making illegal plays or if they do not fully understand how cards interact.

> (By the way, it is NOT so trivial in certain cases like Soul Exchange.)

Thank you for answering my question correctly. If you are making an effort to improve the health of the code and intend on reintroducing this feature I can support this commit. One can not simply ignore a domain problem which complex code solves but they can change the way it flows to make it less difficult to work with. If you can point out the pain points we can work with you to make it less difficult to work with.

@lllyasviel what is nbx?


t


should we change the input to be base_data_id then as well?


Enterprise Java. Not even once.


we discussed this - you and dave both liked base_data_id since it is not always a way_id
however, if we already have way_id then yea it should be the same


I did not understand why password protected functions should be blacklistable.
You could change the password and keep it safe.


Email:frazaomarcos@outlook.com


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1701](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18733&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 287, ignored: 4 Build time: 00:15:32


Nice catch! Patching!


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1702](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18735&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 287, ignored: 4 Build time: 00:14:48


Ah I see.

At the previous commit: 86940755 bytes
At this commit: 86954460 bytes

But maybe RTTI is included even before this commit for some reason.  We'll see at review time.


Looks like it's hitting this route: https://github.com/concerto/concerto-weather/blob/master/config/routes.rb
Which leads to this controller that responds with results from the openweathermap api: https://github.com/concerto/concerto-weather/blob/master/app/controllers/concerto_weather/search_controller.rb


Oddly enough Hideo and I (along with a visitor, Mune Kamiya who is the
author of the 4th order response code in NTChem and a code generator for
high order functional derivatives) were just yesterday discussing some of
the instabilities that seem to appear (either real or as implementation
artifacts) in GGA response theories and how they seem to be fixed once the
potential has the correct form at long range (c.f., HF).

One way to approach this is for some GGA to assume that rho=exp(-a*r) and
rho'=exp(-b*r) and examine what the limits look like for r->infinity for
each term.

Also, Mune and Hideo pointed out that quantities such as

    d^nExc / drho^n

are always multiplied by

    ( drho/dlamba)^n = rho' ^n

So we need to analyze the full product since it may be reasonable for
d^nExc / drho^n to diverge while the full expression remains finite or go
to zero (e.g., as is already the case for higher derivatives of the LDA
functional).

If even the nuclear-derivative first-order CPKS equations are problematic,
there are clearly some more immediate problems we need to address with GGAs
that are not fixed by long range corrections.

Greg and I (with Stig) now have 3 new implementations of the derivative
operator that have different smoothing and accuracy characteristics.  The
implementation needs a little clean up but I will soon make a branch that
people can evaluate.

Again the goal here is to smooth noise, including the small discontinuities
that exist at the edges of boxes. Underlying this is the assumption that
the function is smooth at the length scale on which it is being
differentiated.  If the function is not smooth (e.g., there is a real cusp)
then the assumption is not valid, and the derivative will be the derivative
of the projection of the input function into whatever basis underlays the
smoothing (b-splines, approximate prolates, or Fourier filter).

On Wednesday, November 23, 2016, fbischoff <notifications@github.com> wrote:

> Robert,
>
> I guess you’re correct with the long-range behavior of the perturbed
> density. My current test case is the nuclear gradients of the PF3 molecule
> which is very compact and very singular, and I have not tested Rydberg
> states with the new code yet.
>
> The current rationale is that only where the density is well defined the
> xc functional, potential and kernel are well defined. Once the density
> drops below the threshold, the density, the density gradients and
> subsequently all derivatives of the functional are consistently set to zero
> (by virtue of the log derivatives), and their product with the perturbed
> density should also vanish. In that sense the binary munging should even be
> redundant.
>
> However, currently I’m munging the GGA parts of the kernel tighter
> (usually ggatol = 1e-4) than the LDA parts (default rhotol = 1.e-7). I
> can’t compute the derivatives of the perturbed densities with the log
> trick, so they are not (yet?) as stable as the ground state densities.
> These parameters should be tested more extensively though, and they should
> also be related to the MRA thresholds.
>
> On another note, the gradients of the perturbed densities (esp if they are
> related to heavy nuclei displacements) cover many orders of magnitude, they
> are proportional to something like e.g. (Z^2 x y)/r^4 for the x electronic
> derivative of the y nuclear derivative. Taking the div operation after
> multiplication makes it even worse..
>
> So far my experience with GGA kernels is that they just adds noise to the
> fairly stable LDA kernels, and in the PF3 case I can’t even converge the
> CPHF equations.
>
> Florian
>
>
>
>
>
>
>
> > On Nov 23, 2016, at 4:48 PM, Robert J. Harrison <
> notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> >
> > Florian ... thanks for the pull request. I am reading through it and have
> > asked Scott, Hideo and Bryan to also take a look.
> >
> > One quick question is about the screening routine for the perturbed
> density
> >
> > double binary_munge(double rho, double refrho) const {
> > if (refrho<rhotol) rho=rhomin;
> > return rho;
> > }
> >
> > where rho is the perturbed density and refrho is the ground state density
> >
> > Since the perturbed density can be much more diffuse than the ground
> state
> > density this screening does not seem correct ... i.e., it forces (in this
> > context of evaluating the xc functional) the perturbed density to have
> the
> > same foot print as the ground state.
> >
> > At long range the ground state density is dominated by the HOMO
> >
> > rho(r) ~= phi_homo(r)^2
> >
> > So the derivative density looks like
> >
> > rho'(r) = 2 phi'(r) phi(r)
> >
> > We can bound phi'(r) as being O(1) ... e.g., if it is decaying very
> slowly
> > or is even in the continuum. Thus, we have
> >
> > |rho'(r)| <= O( |phi(r)| )
> >
> > So we might have |rho'| ~= sqrt(rho)
> >
> > Circling back to the code ... the screening would likely not impact
> valence
> > excitations or properties, but Rydberg excitations and higher-order
> > response properties could be incorrect.
> >
> > Since the functionals can accommodate a negative response density why do
> we
> > need to screen it? Is the problem actually in correct screening of the
> > ground state density (and sigma) in higher-derivatives of the functional?
> >
> > Robert
> >
> >
> > On Monday, November 21, 2016, fbischoff <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> >
> > > After the little mishap the other day I’ve pushed a branch
> > > “multi_to_multi” with my proposal for xcfunctional. Comments and
> changes to
> > > the proposed code are welcome.
> > >
> > > I’ve implemented a multi_op_values which returns a vector as result, so
> > > that all grid operations in xcfunctional can be done without
> reprojection
> > > into the MRA basis, and libxc needs to be called only once. All
> preparatory
> > > work is done in prep_xc_args in XCOperator, as before. The user only
> needs
> > > to construct an XCOperator and call its methods.
> > >
> > > The commits change the interface to xcfunctional, so I can retain the
> old
> > > API for the current code. However, the new code is faster and
> numerically
> > > more stable.
> > >
> > > Florian
> > >
> > >
> > >
> > > > On Nov 19, 2016, at 6:39 PM, Florian Bischoff <
> > > florian.bischoff@hu-berlin.de
> <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de');>
> > > <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de
> <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de');>');>>
> wrote:
> > > >
> > > > I’m sorry for that.. The idea was to have a pull request as a
> starting
> > > ground for discussion. I will undo the changes, if not today then on
> Monday.
> > > >
> > > >
> > > >> On Nov 19, 2016, at 6:31 PM, Robert J. Harrison <
> > > notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > >>
> > > >> Can we please have design discussions before changing to commonly
> used
> > > >> APIs? There's lots of code using the XC library including in forks
> and
> > > >> branches not merged with the main stream.
> > > >>
> > > >> In December I plan to take the next step in implementing the
> separation
> > > of
> > > >> core and application codes that we agreed upon doing. Stuff that is
> core
> > > >> needs a communal approach.
> > > >>
> > > >> On Nov 19, 2016 11:05 AM, "fbischoff" <notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > >>
> > > >> Sorry, last two commits were meant to be a pull request..
> > > >> I've implemented a vector to vector operation and reimplemented
> > > >> xcfunctional to avoid frequent projections of the xc potentials
> into the
> > > >> MRA basis, which should improve efficiency and numerical stability.
> > > >>
> > > >> —
> > > >> You are receiving this because you are subscribed to this thread.
> > > >> Reply to this email directly, view it on GitHub
> > > >> <https://github.com/m-a-d-n-e-s-s/madness/commit/
> > > 8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19891272>,
> > > >> or mute the thread
> > > >> <https://github.com/notifications/unsubscribe-auth/AHMgPUk9q0dZAd-
> > > 1CwuGRMYGy_r4V0-uks5q_x4ugaJpZM4K3Sht>
> > > >> .
> > > >> —
> > > >> You are receiving this because you commented.
> > > >> Reply to this email directly, view it on GitHub, or mute the thread.
> > > >>
> > > >
> > > >
> > >
> > >
> > > —
> > > You are receiving this because you commented.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/m-a-d-n-e-s-s/madness/commit/
> 8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19902876>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/AHMgPdreUi-C_
> 3dfK6iQgK7ytny0EjFvks5rAZN4gaJpZM4K3Sht>
> > > .
> > >
> >
> >
> > --
> > Robert J. Harrison
> > tel: 865-272-9262
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub, or mute the thread.
> >
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/m-a-d-n-e-s-s/madness/commit/8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19941778>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHMgPSxB7HSz3lPz_l2LNPgIETbvkqfLks5rBHoNgaJpZM4K3Sht>
> .
>

--
Robert J. Harrison
tel:  865-272-9262


We want to know which address the SIGSEGV is being raised on because we need some escape path in the new memory manager that will recognize that it should let this one SIGSEGV go through and cause an error and a stack dump. I couldn't figure out how to do this with raise(SIGSEGV).


Why sleep again after password change? This doesn't seem necessary for me...


Ouais j'y ai pensé, mais j'était pas trop sûr.  C'est probablement un vieux réflexe de C en fait, je vais faire comme tu dis.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1703](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=18737&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 287, ignored: 4 Build time: 00:13:43


I noticed that too, and can't make heads or tail of it. Maybe they were reverting some changes? The dates are just when they were released to Raytheon, so it could have just been that they had never manufactured Rev. 1 ropes before that. Or maybe it was supposed to say "Rev. 10" or "Rev. 11" or something like that. The Computer History Museum has a copy of this, so if I end up needing to get a membership there for the ARGUS manual I can take a peek to clarify.

I did discover while looking around for info on Luminary 210 that its GSOP does call out the revision and drawing number, on page 2-18a (pdf page 38) of https://www.ibiblio.org/apollo/Documents/R-567-GSOP-Luminary1E-Section2-DataLinks.pdf

``` ASSEMBLE REVISION 210 OF AGC PROGRAM LUMINARY BY NASA 2021112-161 ```

Maybe if we find Section 2 for Apollo 10 it'll have the same info.


^^ temporarily, given it breaks things right now


Je met habituellement une ligne vide entre le comment d'une class/struct/enum et la class/struct/enum, mais je sais pas si c'est bien ou pas.


It doesn't look like anything changed here, so not sure what the pull request is for.


Why is "settings_redis"? I think that should be "settings".


lisdhugfp;lasdgfu;lasdhfug


My developer and unstable multimc.cfg doesnt have option in it "Analytics=false". I deleted multimc.cfg after the updates to see if bugged and still didnt help.  Something on my end or isnt implemented in dev version of multimc yet ? TIA


Good.


Ok, je vais enlever les explicit.


I'm getting a warning like below from this commit when building:

```
In file included from executor/executor.cc:33:0:
executor/common.h:5:0: warning: "_GNU_SOURCE" redefined [enabled by default]
 #define _GNU_SOURCE
 ^
<command-line>:0:0: note: this is the location of the previous definition
```


Why did you choose to add a JFrame field to the ClickCounter class instead of make it extend JFrame Class?


I think the drop in size is because @cushon migrated us away from Eclipse and dropped the dependency in 946e01cc1440cd5f6fdcad11225b62357f1ed910.


Ok, I thought the POST is async, so better save than sorry. :-) Is it sync? Then this is not necessary. I'll look into the documentation.


it gives me an error on Qapplication


Could you share some more insights on why this has been decided? What kind of issues have you faced?


kindly tell me how to remove this error.error is "no such file or directory"


ah ben je sais pas, j'ai pas trop pigé comment ça marche non mais en effet ça sert à rien


![](https://github.trello.services/images/mini-trello-icon.png) [Google Maps API Integration](https://trello.com/c/2CTiFREu/10-google-maps-api-integration)


qweqweqwe


qweqweqweqwe


![](https://github.trello.services/images/mini-trello-icon.png) [Admin console](https://trello.com/c/NIbHJh3A/18-admin-console)


Ah I didn't look in the routes, sorry.

> On Nov 23, 2016, at 9:09 AM, Gabe Perez <notifications@github.com> wrote:
>
> Looks like it's hitting this route: https://github.com/concerto/concerto-weather/blob/master/config/routes.rb
> Which leads to this controller that responds with results from the openweathermap api: https://github.com/concerto/concerto-weather/blob/master/app/controllers/concerto_weather/search_controller.rb
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


adasdad


![](https://github.trello.services/images/mini-trello-icon.png) [Auth0 Implementation](https://trello.com/c/15OkHLof/9-auth0-implementation)


asdasdasdasd


asdasdasdasdasd


asdasdasd


asdasdas


DOdaję komentarz do pierwszego komitu


dasdasd


tyurr


Super drugi komentarz!


Dans les classes déjà converties, il y a plusieurs exemples où c'est fait comme ça:

```
119   struct minimal_symbol *record_with_info (const char *name,
120                                            CORE_ADDR address,
121                                            enum minimal_symbol_type ms_type,
122                                            int section)
123   {
124     return record_full (name, strlen (name), true, address, ms_type, section);
125   }
```

```
1651   /* Swap the std::string storage with STR, and return a pointer to
1652      the beginning of the new string.  */
1653   const char *swap_string (std::string &str)
1654   {
1655     std::swap (m_string, str);
1656     return m_string.c_str ();
1657   }
1658
1659   /* Set the malloc storage to now point at PTR.  Any previous malloc
1660      storage is released.  */
1661   const char *set_malloc_ptr (char *ptr)
1662   {
1663     m_malloc.reset (ptr);
1664     return ptr;
1665   }
```


komć


komentarz


kometarz


komentarz4 chyba


kometarz 5


Some posts were missing... like this one:

Before:

After:


kom 6


kom 7


Dear Danilo Alexandre,
We are both interested in project dcm4chee. I want to create my own build of dcm4chee with Russian localization. But all my attempts were unsuccessful, I can't compile project. Dcm confluence didn't help me. Do you have any instructions how to configure and compile project? Could you send me on email some instructions how to do it?

Regards, Maksim Kuznietsov
maksim.kuznetsov.kh@gmail.com
http://kuznietsov.com/


I think that's ok, when there are long messages it's often split like this.  The alternative would be like this, using implicit string concatenation:

```
126       internal_error (__FILE__, __LINE__,
127                       _("extra table_body call not allowed; there must be "
128                         "only one table_body after a table_begin and before "
129                         "a table_end."));
```

What do you prefer?  I actually prefer this modified version, so I'll change it :)


kom 9


huru


kom 10 ostatnii


@NateWr, might this be changed to protected? -- In order for child scripts to do with it something else? -- If so it will also have to be renamed into $preview i.e. without '_' at the end...


Hey, at least there's no `AnnotatedMixinElementHandlerSoftImplementsFactoryProvider`


This was fixed in core via https://core.trac.wordpress.org/ticket/38830


It's just that the DEV version of the lib doesn't block the online. ;)


Hej Bartek ta linijka jest zle


EJ no nie no, jest dobrze!


A no w sumie morzesz miec racje


pisze sie możesz!


a no tak


same


komentarz


odpisz


izi


odpiywanko


koment


No, it doesn't block online, a friend of mine uses blankCheatMenu for his own private plugin and he is able to go online.
Can you confirm this @AnalogMan151 as I don't have a n3DS to test the plugin.


This commit causes a regression in Nascar 09 . Due to this regression resolution is reported as 640 x 2495 instead of 640 x 448 and causes various graphical issues ingame. @gregory38 and @FlatOutPS2 please review this. I will post a gsdump if required.


Film Manager
Testy do film manager


@mendhak, I couldn't open an issue on https://github.com/mendhak/rhythmbox-tray-icon.

Please consider adding this for 3.3 support.


Can add me if you want.  I should be able to help more soon.


Good catch!


Testy do kategoria manager


@ChrisLaganiere


Hey Jason, we needed gmes_petap.pl as a dependency for funannotate.
Didn't realize that we already had it under genemarkHMM. We will correct this duplication.
Thanks


I think having the 'player look' function available in debug mode can help us debug the messages printed when the player looks at something.

Otherwise I do really like how easy it is to move around while in debug mode now.


This break in true /bin/sh on Solaris.  We need to do unset SSH_AUTH_SOCKET.  I am working on a pull request.


豆瓣和知乎爬虫


poprawa drobnych błędów
początkowe testy do kategoria manager


@mattdowle does that mean 1.9.8 was pushed to CRAN?


stworzenie pustego projektu oraz potrzebnych plików


Ah, cool, good to know. I may follow up on this once I've finalized all the changes I need / gotten them merged into dev.


Are you adding Pinterest? Noticed the Pinterest logo


Utworzenie konstruktorów oraz interfejsów


This line is still required.
Options:
- reinstate from logging import warn
- change all warn messages (3 in total) to self.warn ?will this work


Looking at this again, it was unclear why we needed to build the map `type->nodes-facts`.  I decided to experiment more directly mapping a map of alpha roots to facts, which is what we ultimately want.  I think doing this cuts out some intermediate steps.  It also provides some opportunity to sort the results correctly later, but we'll need node-id's on alpha nodes first.  Also, this does not use the user-defined fact-type as a map key as aggressively as the current approach.  And lastly, this memoizes the creation of a wrapper for the key, I still have it called `FactTypeWrapper` even though it probably should be renamed to `RootsWrapper` or something, to use in a Java map.

I haven't tested this whatsoever.  I'm just getting the idea documented here for discussion.
```clj
(defn- create-get-alphas-fn
  "Returns a function that given a sequence of facts,
  returns a map associating alpha nodes with the facts they accept."
  [fact-type-fn ancestors-fn alpha-roots]

  (let [ ;; If a customized fact-type-fn is provided,
        ;; we must use a specialized grouping function
        ;; that handles internal control types that may not
        ;; follow the provided type function.
        fact-grouping-fn (if (= fact-type-fn type)
                           type
                           (fn [fact]
                             (if (isa? (type fact) :clara.rules.engine/system-type)
                               ;; Internal system types always use Clojure's type mechanism.
                               (type fact)
                               ;; All other types defer to the provided function.
                               (fact-type-fn fact))))

        fact-type->roots (memoize
                          (fn [fact-type]
                            ;; TODO, alpha roots could provide a sortable value - such as an alpha id
                            (into #{}
                                  ;; If a given type in the ancestors has no matching alpha roots,
                                  ;; don't return it as an ancestors.  Since this helper function is memoized,
                                  ;; but the later runtime dispatch on the types isn't, this will reduce the work
                                  ;; needed later.
                                  (keep #(when-let [roots (not-empty (get alpha-roots %))]
                                           (FactTypeWrapper. roots)))
                                  (conj (ancestors-fn fact-type) fact-type))))
        update-roots->facts! (fn [roots->facts roots fact]
                               (if-let [v (.get roots->facts roots)]
                                 (.add ^List v fact)
                                 (.put roots->facts roots (doto (LinkedList.)
                                                            (.add fact)))))]

    (fn [facts]
      (let [roots->facts (LinkedHashMap.)]

        (doseq [fact facts
                roots (fact-type->roots (fact-grouping-fn fact))]
          (update-roots->facts! roots->facts roots fact))

        (let [return-list (LinkedList.)]
          ;; Make the list of facts for each type unmodifiable.  We use mutable structures for performance here,
          ;; since we may have many facts.  The expectation is that the number of fact types to iterate over here
          ;; will be small and the performance consequences of this iteration to make unmodifiable lists will be
          ;; inconsequential.  If this assumption is incorrect we may remove this logic later and rely on a convention
          ;; of not modifying the return value of this function.
          (doseq [^Map$Entry e (.entrySet roots->facts)]
            (.add return-list [(.getKey e) (Collections/unmodifiableList (.getValue e))]))

          (Collections/unmodifiableList return-list))))))
```


Either we need to call unset SSH_AUTH_SOCKET or do SSH_AUTH_SOCKET= and then export SSH_AUTH_SOCKET.  Do you know if it needs to be declared empty or if undefined is ok?  I am going to go with declared empty since that is the closest match despite the fact your commit calls for unsetting .


oh no that's just a browser addon haha 😛


I came across ImageIcon, but wasn't sure what it is for. Did it work?

Nice, easy-to-follow codes. 👍


Curl is waiting for Neo4J to respond (as curl -v shows), so you're right. Waiting is not necessary.


My comment was meant to annotate https://github.com/google/google-java-format/commit/946e01cc1440cd5f6fdcad11225b62357f1ed910 ... never mind.

Only `guava` and `javac` left. Couldn't a JDK environment replace that `javac` dependency?


TYPO s/exatly/exactly


LMAO this is so funny. How did they find this? Also, how did you find it Kale?

> On Nov 22, 2016, at 6:39 PM, JDeeth <notifications@github.com> wrote:
>
> Hah. Your commit got picked up by a Twitter bot. Well done :D
>
> https://twitter.com/callouscommits/status/801243412288643072 <https://twitter.com/callouscommits/status/801243412288643072>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub <https://github.com/CaptainKirk1609/CSCI499/commit/ab1aa7e24304991d18a80391e73beb3ff62cf22f#commitcomment-19931738>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQgKCTx2uSzS5zEfyBM49KvkcXqLlfogks5rA6dUgaJpZM4K6Kv6>.
>


Can i make any changes to UI ?


> One way to approach this is for some GGA to assume that rho=exp(-a*r) and
> rho'=exp(-b*r) and examine what the limits look like for r->infinity for
> each term.
This is what you get when you plot \nabla \zeta (zeta being defined by rho=exp(zeta) ) as it is used in the log derivatives. It’s a constant function for large r, proportional to the orbital energy. I don’t know what the b constant should look like, but I feel it should also be proportional to the orbital energy.

> Also, Mune and Hideo pointed out that quantities such as
>
> d^nExc / drho^n
>
> are always multiplied by
>
> ( drho/dlamba)^n = rho' ^n
>
> So we need to analyze the full product since it may be reasonable for
> d^nExc / drho^n to diverge while the full expression remains finite or go
> to zero (e.g., as is already the case for higher derivatives of the LDA
> functional).

I think the problem here is that the result should be small and smooth, but for large r we have basically noise divided by noise, which is undefined.

I’m definitely looking forward to the new gradient implementations, it might really help in extending the range for which we can provide numerically stable potentials and kernels.

> On Nov 23, 2016, at 7:09 PM, Robert J. Harrison <notifications@github.com> wrote:
>
> Oddly enough Hideo and I (along with a visitor, Mune Kamiya who is the
> author of the 4th order response code in NTChem and a code generator for
> high order functional derivatives) were just yesterday discussing some of
> the instabilities that seem to appear (either real or as implementation
> artifacts) in GGA response theories and how they seem to be fixed once the
> potential has the correct form at long range (c.f., HF).
>
> One way to approach this is for some GGA to assume that rho=exp(-a*r) and
> rho'=exp(-b*r) and examine what the limits look like for r->infinity for
> each term.
>
> Also, Mune and Hideo pointed out that quantities such as
>
> d^nExc / drho^n
>
> are always multiplied by
>
> ( drho/dlamba)^n = rho' ^n
>
> So we need to analyze the full product since it may be reasonable for
> d^nExc / drho^n to diverge while the full expression remains finite or go
> to zero (e.g., as is already the case for higher derivatives of the LDA
> functional).
>
> If even the nuclear-derivative first-order CPKS equations are problematic,
> there are clearly some more immediate problems we need to address with GGAs
> that are not fixed by long range corrections.
>
> Greg and I (with Stig) now have 3 new implementations of the derivative
> operator that have different smoothing and accuracy characteristics. The
> implementation needs a little clean up but I will soon make a branch that
> people can evaluate.
>
> Again the goal here is to smooth noise, including the small discontinuities
> that exist at the edges of boxes. Underlying this is the assumption that
> the function is smooth at the length scale on which it is being
> differentiated. If the function is not smooth (e.g., there is a real cusp)
> then the assumption is not valid, and the derivative will be the derivative
> of the projection of the input function into whatever basis underlays the
> smoothing (b-splines, approximate prolates, or Fourier filter).
>
>
>
>
> On Wednesday, November 23, 2016, fbischoff <notifications@github.com> wrote:
>
> > Robert,
> >
> > I guess you’re correct with the long-range behavior of the perturbed
> > density. My current test case is the nuclear gradients of the PF3 molecule
> > which is very compact and very singular, and I have not tested Rydberg
> > states with the new code yet.
> >
> > The current rationale is that only where the density is well defined the
> > xc functional, potential and kernel are well defined. Once the density
> > drops below the threshold, the density, the density gradients and
> > subsequently all derivatives of the functional are consistently set to zero
> > (by virtue of the log derivatives), and their product with the perturbed
> > density should also vanish. In that sense the binary munging should even be
> > redundant.
> >
> > However, currently I’m munging the GGA parts of the kernel tighter
> > (usually ggatol = 1e-4) than the LDA parts (default rhotol = 1.e-7). I
> > can’t compute the derivatives of the perturbed densities with the log
> > trick, so they are not (yet?) as stable as the ground state densities.
> > These parameters should be tested more extensively though, and they should
> > also be related to the MRA thresholds.
> >
> > On another note, the gradients of the perturbed densities (esp if they are
> > related to heavy nuclei displacements) cover many orders of magnitude, they
> > are proportional to something like e.g. (Z^2 x y)/r^4 for the x electronic
> > derivative of the y nuclear derivative. Taking the div operation after
> > multiplication makes it even worse..
> >
> > So far my experience with GGA kernels is that they just adds noise to the
> > fairly stable LDA kernels, and in the PF3 case I can’t even converge the
> > CPHF equations.
> >
> > Florian
> >
> >
> >
> >
> >
> >
> >
> > > On Nov 23, 2016, at 4:48 PM, Robert J. Harrison <
> > notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> > >
> > > Florian ... thanks for the pull request. I am reading through it and have
> > > asked Scott, Hideo and Bryan to also take a look.
> > >
> > > One quick question is about the screening routine for the perturbed
> > density
> > >
> > > double binary_munge(double rho, double refrho) const {
> > > if (refrho<rhotol) rho=rhomin;
> > > return rho;
> > > }
> > >
> > > where rho is the perturbed density and refrho is the ground state density
> > >
> > > Since the perturbed density can be much more diffuse than the ground
> > state
> > > density this screening does not seem correct ... i.e., it forces (in this
> > > context of evaluating the xc functional) the perturbed density to have
> > the
> > > same foot print as the ground state.
> > >
> > > At long range the ground state density is dominated by the HOMO
> > >
> > > rho(r) ~= phi_homo(r)^2
> > >
> > > So the derivative density looks like
> > >
> > > rho'(r) = 2 phi'(r) phi(r)
> > >
> > > We can bound phi'(r) as being O(1) ... e.g., if it is decaying very
> > slowly
> > > or is even in the continuum. Thus, we have
> > >
> > > |rho'(r)| <= O( |phi(r)| )
> > >
> > > So we might have |rho'| ~= sqrt(rho)
> > >
> > > Circling back to the code ... the screening would likely not impact
> > valence
> > > excitations or properties, but Rydberg excitations and higher-order
> > > response properties could be incorrect.
> > >
> > > Since the functionals can accommodate a negative response density why do
> > we
> > > need to screen it? Is the problem actually in correct screening of the
> > > ground state density (and sigma) in higher-derivatives of the functional?
> > >
> > > Robert
> > >
> > >
> > > On Monday, November 21, 2016, fbischoff <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
> > >
> > > > After the little mishap the other day I’ve pushed a branch
> > > > “multi_to_multi” with my proposal for xcfunctional. Comments and
> > changes to
> > > > the proposed code are welcome.
> > > >
> > > > I’ve implemented a multi_op_values which returns a vector as result, so
> > > > that all grid operations in xcfunctional can be done without
> > reprojection
> > > > into the MRA basis, and libxc needs to be called only once. All
> > preparatory
> > > > work is done in prep_xc_args in XCOperator, as before. The user only
> > needs
> > > > to construct an XCOperator and call its methods.
> > > >
> > > > The commits change the interface to xcfunctional, so I can retain the
> > old
> > > > API for the current code. However, the new code is faster and
> > numerically
> > > > more stable.
> > > >
> > > > Florian
> > > >
> > > >
> > > >
> > > > > On Nov 19, 2016, at 6:39 PM, Florian Bischoff <
> > > > florian.bischoff@hu-berlin.de
> > <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de');>
> > > > <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de
> > <javascript:_e(%7B%7D,'cvml','florian.bischoff@hu-berlin.de');>');>>
> > wrote:
> > > > >
> > > > > I’m sorry for that.. The idea was to have a pull request as a
> > starting
> > > > ground for discussion. I will undo the changes, if not today then on
> > Monday.
> > > > >
> > > > >
> > > > >> On Nov 19, 2016, at 6:31 PM, Robert J. Harrison <
> > > > notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > > >>
> > > > >> Can we please have design discussions before changing to commonly
> > used
> > > > >> APIs? There's lots of code using the XC library including in forks
> > and
> > > > >> branches not merged with the main stream.
> > > > >>
> > > > >> In December I plan to take the next step in implementing the
> > separation
> > > > of
> > > > >> core and application codes that we agreed upon doing. Stuff that is
> > core
> > > > >> needs a communal approach.
> > > > >>
> > > > >> On Nov 19, 2016 11:05 AM, "fbischoff" <notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>
> > > > <javascript:_e(%7B%7D,'cvml','notifications@github.com
> > <javascript:_e(%7B%7D,'cvml','notifications@github.com');>');>> wrote:
> > > > >>
> > > > >> Sorry, last two commits were meant to be a pull request..
> > > > >> I've implemented a vector to vector operation and reimplemented
> > > > >> xcfunctional to avoid frequent projections of the xc potentials
> > into the
> > > > >> MRA basis, which should improve efficiency and numerical stability.
> > > > >>
> > > > >> —
> > > > >> You are receiving this because you are subscribed to this thread.
> > > > >> Reply to this email directly, view it on GitHub
> > > > >> <https://github.com/m-a-d-n-e-s-s/madness/commit/
> > > > 8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19891272>,
> > > > >> or mute the thread
> > > > >> <https://github.com/notifications/unsubscribe-auth/AHMgPUk9q0dZAd-
> > > > 1CwuGRMYGy_r4V0-uks5q_x4ugaJpZM4K3Sht>
> > > > >> .
> > > > >> —
> > > > >> You are receiving this because you commented.
> > > > >> Reply to this email directly, view it on GitHub, or mute the thread.
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > > > —
> > > > You are receiving this because you commented.
> > > > Reply to this email directly, view it on GitHub
> > > > <https://github.com/m-a-d-n-e-s-s/madness/commit/
> > 8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19902876>,
> > > > or mute the thread
> > > > <https://github.com/notifications/unsubscribe-auth/AHMgPdreUi-C_
> > 3dfK6iQgK7ytny0EjFvks5rAZN4gaJpZM4K3Sht>
> > > > .
> > > >
> > >
> > >
> > > --
> > > Robert J. Harrison
> > > tel: 865-272-9262
> > > —
> > > You are receiving this because you commented.
> > > Reply to this email directly, view it on GitHub, or mute the thread.
> > >
> >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/m-a-d-n-e-s-s/madness/commit/8845662a5a28a4634bd984bda06992e0b5cd2255#commitcomment-19941778>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHMgPSxB7HSz3lPz_l2LNPgIETbvkqfLks5rBHoNgaJpZM4K3Sht>
> > .
> >
>
>
> --
> Robert J. Harrison
> tel: 865-272-9262
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


`/resources/assets/js/bootstrap.js` importe jQuery pour vous.


@mendhak, let us know if you want a pull request for this.


Sure we can lower it for the beginning, however it should be dynamically. If you use NetInstall it might even need more space. Windows-Clicki-Bunti will always press next, next, next.


yeah I guess so.


Hmm… to 2017?


Sorry, when I implemented #537 I forgot to add the default for `fluxAnimation` in case the `method` exists. Thanks for taking care of it @moellep! I think we need to get rid of this fix-up function and move all the defaults to SRW schema. This way we could automate fix-ups on the fly based on the values from the schema.


It was a good idea to make a separate method for the code in greetings().


I think I understand, but if it's set inside a function that's inside the main function, is it still accessible? I see the redundancy considering i return setValue at the end of my code though. Also, I took your comments from DavidE's code and tried them on my code in JSBin. response was that "theVault.setValue is not a function" that's the answer I think I was hoping for as it means my functions and their values are hidden, right? If that's the case, how in the future would I ever be able to setValues like playerName, score, isDead, promoCode etc...from an outside source? Aren't we going to have to create some pointers/some way in to...theVault?

```'use strict';
function theVault(){

  var security = {};

  function setValue(key,value){

      security[key] = value;

  }

  function getValue(key){
    if(security[key]){

    return security[key];

    }else{

    return null;

    }

  }

  return{
    setValue: setValue,
    getValue: getValue
  };
};
theVault();

theVault.setValue('playerName', '');
theVault.setValue('score', 0);
theVault.setValue('isDead', false);
theVault.setValue('promoCode', undefined);

let playerName = theVault.getValue('playerName');
let score = theVault.getValue('score');
let isDead = theVault.getValue('isDead');
let promoCode = theVault.getValue('promoCode');

console.log('playerName should be "", actual value:', playerName);
console.log('score should be 0, actual value:', score);
console.log('isDead should be false, actual value:', isDead);
console.log('promoCode should be undefined, actual value:', promoCode); ```


they did it like this, in the second video, i just copied, basically :D


I've just releases 1.28.2 which includes the fix.


Please add the reference to View in public enum Event

public enum Event {
        case willShow(UIView?)
        case didShow(UIView?)
        case willHide(UIView?)
        case didHide(UIView?)
    }


No, because of the enum type called state, it would clash.  But I can rename the type to something else if you'd like.