text:
mj-style in body to add styles to head

Hi,
We're working on component based emails and feel it would be extremely useful to be able to add styles to the head (for gmail) from within mj-body (the reverse of how mj-preview works?). Do you think this is something you could please implement if possible?
Thanks,
Nick

Well component in MJML3 has access to postRender with a jquery like syntax (you can look at carousel/column to see how it works)
In MJML4 we're looking to add a function to add style (https://github.com/mjmlio/mjml/issues/880)
Is this what you're looking for ?

Hi @iRyusa,
Yes it is, sorry didn't spot it in there before!
Thanks

Hi @iRyusa, I just reread over this and not quite sure it was what I was looking for actually.
I meant to be able to use mj-style anywhere within mj-body, as it can currently only be used in mj-head.
For the custom component wishlist is that saying to be able to add to the head specifically from the js file instead of using an mj-style in the mjml file?
Cheers

Hey @nickjl
Now that head style are supported almost everywhere why would you put an mj style inside a mj-body ?

Just reposting because I understand what you meant now, but I don't really see the advantage of getting mj-style in a middle of a template rather than grouping everything in the head ?

Hey @iRyusa
So in terms of our implementation, we use mj-include for the header (incl mj-head) and footer and then Atom with snippets that automatically pull in all the required mjml for any components that we use regularly. (not custom components but combinations of standard mjml ones with certain classes etc)
Each component that is then pulled in may need some slight css changes (hence why the styles for it cant already be in the mj-include within mj-head) and if mj-style could be used within the body, this then allows these style changes to reflect in the header.
Furthermore, this then also allows less technical people to build templates as everything required can be pulled into the template from one line of code and removes the need of having a lot of unnecessary styles in the header file (causing clipping in gmail), as they'd only be added to the head when the component is in the body.
I hope that makes sense?
Cheers

Well we split the core css of MJML and the mj-style part, so the gmail clipping is not really an issue.
About the usecase I understand what you want, i'm still not sure if it's a good idea to allow this.
In mj-include you can include both mj-head/mj-body to add some mj-style into the main document. mj-head will be append into the main MJML file. I think it's a good compromise between flexibility and keep the body for structural elements only

Hey @iRyusa, ahh yeah I understand the gmail clipping isn't an issue in terms of clashing with the core MJML css, I more meant for when it comes for less technical people to build components we have to have a lot of styles already in the head for incase they want to use a certain component (I'd say we have 15-20 that are regularly used). If it could be added from the body then it removes the need to have these extra styles in the head for if the component is used.
Essentially I think that if it was allowed in the body it allows MJML to easily be set up to allow people with very little understanding of MJML, HTML or CSS to easily build email templates (this is currently what we use it for) and the only problem they all have with it currently is when it comes to needing to add styles into the head from the component, as everything else can be done behind the scenes for them.
What potential problems would be caused by allowing mj-style to be used within the body?

I think it's more a semantic issue rather than a technical issue. We can do it quite easily in MJML4, but I think it's a matter of consistency over conveniency

I think it's more a semantic issue rather than a technical issue as we can do it quite easily in MJML4, (consistency over conveniency).

I more meant for when it comes for less technical people to build components we have to have a lot of styles already in the head for incase they want to use a certain component

It's more a behind the scene issue ?

If it could be added from the body then it removes the need to have these extra styles in the head for if the component is used.

Well I think the component should add it's own style by itself and shouldn't rely on any input in the template. You can easily know if a component is used in the markup and add styles you need for it ( in MJML3 through post-render, in MJML4 we gonna check it automatically )
I don't think it add so much overhead to do something like this in a mj-included file :
mjml
  mj-head
    mj-style
  mj-body
    // my include

From a learning standpoint, I think mixing head and body elements can add a lot of confusion about the goal of mj-head / mj-body

Ahh yeah ok I do see your point in regards to semantics but feel potentially convenience outweighs in the case for ease for say a marketing team.
For me personally it's easy enough to work with that method, and I really love how easy MJML makes it for me to make templates! But it's just the feedback I've had for when people have to make changes to say a colour or url in a style, and then move it up into mj-head, they consistently make mistakes which would be eliminated if it they didnt have to do these changes.
Although saying that, with the addition of adding styles to the head from a custom component. Is that then going to be the case that say a class name could be passed into the component and a variable like color too (class name for if using multiple of same component), that would then go into the head via that method or are the styles for the custom component going to be unchangeable from the mj tag?

You will be able to push what you want from a component so yeah, if you want to generate a specific style regarding props of a component you will be able to do that. Even with props you can already use them as inline style ( I think it's the best way to ensure it will be applied everywhere)

That's cool thanks, yeah I already use it for inline style but we need some things to change dependent on screen size too hence why want to be able to add to classes too.
So am I right in thinking that if I'll be able to push to classes in custom components in MJML 4 then this will essentially have the same effect as if it were mj-style in the body?
Thanks for all your explanations btw, really looking forward to MJML 4!!

So am I right in thinking that if I'll be able to push to classes in custom components in MJML 4 then this will essentially have the same effect as if it were mj-style in the body?

Well correct, then your component will need to generate and push the css he need/want

Ok great thanks.
I guess that'll be the best for me to use instead then if mj-style in the body isn't going to be an option.
Thanks for all your help! :)

authors: iRyusa nickjl


text:
Protection Code post processing

This PR adds a new protection that post-processes the protection code to counter common guides on how to circumvent the ConfuserEx obfuscation.

:white_check_mark: Build ConfuserEx 318 completed (commit https://github.com/mkaring/ConfuserEx/commit/44f8cc49ba by @mkaring)

source: gharchive/pull-request

authors: AppVeyorBot mkaring

repo: mkaring/ConfuserEx

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 FarmPi Mirror is down

In 62ea54a, FarmPi Mirror (https://farmpi.octofarm.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FarmPi Mirror is back up in 3726a21 after 17 minutes.

source: gharchive/issue


text:
FR Nudge with cursors like gimp/photoshop while floating selection active

Since we're so close to being 1:1 with GimpShop :) it would be nice if:
Floating selections could be nudged like GimpShop.

Arrows move by 1 column/character
SHIFT+Arrows move by 10x column/character (or maybe 5? since our resolution is so small - maybe as a config option?)

I know this is being really needy because the resolution is so low already it's VERY precise to nudge, so not as huge a deal as it is when you are requiring precision in higher resolution canvases like in GimpShop photo editing or UI design.

Implemented - however I've slight problems selecting the editor programatically. Some things are still buggy in egui - focusing is certainly on the more instabile side atm :/.

authors: grymmjack mkrueger


text:
In-Place operators (+=, -=) for MLXArray

I have been using mlx-swift for my projects and have found it to be incredibly useful. However, I noticed that MLXArray does not support in-place operators such as += and -=.
Is there a specific reason why these operators have not been implemented? Additionally, are there any plans to add these in-place operators in the future?
These operators would be very beneficial for performance-critical applications where minimizing memory allocations and copies is crucial.
Thank you for your time and for the great work on mlx-swift!

Right from the user standpoint there are in-place operations. So if you do an in place operation then the object is unchanged:
orig_id = id(a)
a += b
new_id = id(a)

Then `orig_id == new_id``.
However, when it comes to memory management, that is completely opaque to the user. MLX often re-uses memory regardless of if the op is in place or not. It will reuse memory when it is safe to do so (typically if you don't retain references to arrays and the buffer sizes match).
So in the following:
def fun():
  a = mx.array([1,2,3])
  a = a + mx.array([2])
  return a

out = fun()
mx.eval(out)

Even though the op is not in place since the reference to the original array is out of scope before the call to eval the memory buffer is likely re-used

Agreed, these += and friends operators should be added.

authors: awni davidkoski kemchenj

repo: ml-explore/mlx-swift


text:
Scatter gradient implementations

Not sure if this is an issue or I'm just holding it wrong :-) I've got an alternative approach that seems to work with gradients by building up my output up by catting slices into my tensors, which does seem to work for the grads.
I have two tensors (token_embeddings and image_features), I want to interleave them in some way. It's for a llava like model, so my input tokens are like
   [
       [this, is, an, <image>],
       [two, images, <image>, <image>],
   ]

where <image> is a sentinel token. What I've got to so far is making my output a flattened tensor [batch * max_seq, dim] my token/image tensors [num_tokens, dim] and [num_images, dim] and forming indices to assign to, ending up looking like this:
output = mx.zeros(batch * max_seq, dim)
output[token_ix] = self.embeddings(token_ids)
output[image_ix] = image_features

It doesn't seem like I can get gradients for this though:
def fn(x):
    output = mx.zeros([4])
    output[mx.array([0, 1])] = x
    return output.sum()

x = mx.array([2,3])
print(fn(x))

grad_fn = mx.grad(fn)
print(grad_fn(x))

gives me
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[310], line 10
      7 print(fn(x))
      9 grad_fn = mx.grad(fn)
---> 10 print(grad_fn(x))

ValueError: Primitive's vjp not implemented.

Like I said, it seems like there's an alternative in catting things since:
def fn(x, y):
    val = mx.concatenate([x[:1, :], y[:, :], x[1:, :]])
    return val.sum()

x = mx.array([[2,3], [4, 5]])
y = mx.array([[2,3], [4, 5]])
print(fn(x, y))

grad_fn = mx.grad(fn)
print(grad_fn(x, y))

seems to work.

Scatter vjp is indeed missing from main at the moment. I started an implementation in the branch scatter-vjp so that you can be unblocked. The VJP for assignment is the only one implemented so far and not particularly well tested.
Depending on the number of assignments and the size of the assigned blocks concatenating slices might not be too bad of an implementation however.
On that branch the following worked fine:
import mlx.core as mx

def fn(x):
    output = mx.zeros([4, 128])
    output[mx.array([0, 1])] = x
    return output.square().sum()

x = mx.random.normal(shape=(2, 128))
print(fn(x))
# array(274.507, dtype=float32)

grad_fn = mx.grad(fn)
print(grad_fn(x))
# array([[1.08186, -1.9959, 1.18484, ..., 2.52877, 0.80407, 0.529424],
#        [-0.74177, -1.64652, 0.113564, ..., -1.66786, 1.31119, -0.58756]], dtype=float32)

Closing as this is now merged. Scatter multiply, max, min are still missing but assign and add are there.

repo: ml-explore/mlx


text:
Video classification example

When running the video classification example, I get this error :
Uncaught (in promise) Error: Requested texture size [0x0] is invalid.

just curious, are you using an external camera?

No it's the built in camera on a macbook pro. Just to be clearer I do get an image from the camera but it seems it won't just run through the ml5 treatments.
The rest of the message error is :
at Object.e.validateTextureSize (ml5.min.js:1)
at p (ml5.min.js:1)
at Object.e.createMatrixTexture (ml5.min.js:1)
at t.createMatrixTexture (ml5.min.js:1)
at t.acquireTexture (ml5.min.js:1)
at t.uploadToGPU (ml5.min.js:1)
at t.getTexture (ml5.min.js:1)
at t.fromPixels (ml5.min.js:1)
at t.fromPixels (ml5.min.js:1)
at t.fromPixels (ml5.min.js:1)

Sorry @b2renger for the late late late response. It seems I didn't have email notifications on for this repo. Let me know if you still have issues with this.

Hello guys, I had this problem using the example located at https://github.com/ml5js/ml5-examples/tree/master/p5js/ImageClassification_Video
To solve it I changed the version from p5.js to 0.6.1 in index.html
<script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/0.6.1/p5.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/0.6.1/addons/p5.dom.min.js"></script>
<script src="https://unpkg.com/ml5" type="text/javascript"></script>

I get this issue as well. Explicitly setting the video height + width  video.size(320, 240); in the setup function got rid of it for me.

GIve video element width & height like this

      <video
          crossOrigin="anonymous"
          autoPlay
          width="320"
          height="240"
          style={{ width: window.innerWidth, height: window.innerHeight }}
          ref={video => {
            this.video = video;
          }}
        />

authors: AndreasRef b2renger cvalenzuela hiteshsahu jeanpfs


text:
Improve model load: Parallelise download of model shards

Currently the shards are downloaded sequentially. Should be promisified  all the downloads
chat_module.js
await tvm.fetchNDArrayCache(modelUrl, tvm.webgpu(), "webllm/model");

runtime.js (TVM)
/**
   * Fetch list of NDArray into the NDArrayCache.
   *
   * @param ndarrayCacheUrl The cache url.
   * @param list The list of array data.
   * @param device The device to store the data to.
   * @param artifactCache The artifact cache
   */
  private async fetchNDArrayCacheInternal(
    ndarrayCacheUrl: string,
    list: Array<NDArrayShardEntry>,
    device: DLDevice,
    artifactCache: ArtifactCache
  ) {
    const perf = compact.getPerformance();
    const tstart = perf.now();

    let totalBytes = 0;
    for (let i = 0; i < list.length; ++i) {
      totalBytes += list[i].nbytes;
    }
    let fetchedBytes = 0;
    let timeElapsed = 0;

    const cacheOnly = await artifactCache.hasAllKeys(list.map(key => new URL(key.dataPath, ndarrayCacheUrl).href))

    const reportCallback = (iter: number) => {
      // report
      for (let j = 0; j < this.initProgressCallback.length; ++j) {
        let text = "Fetching param cache[" + iter + "/" + list.length + "]: ";
        text += Math.ceil(fetchedBytes / (1024 * 1024)).toString() + "MB fetched. "
        text += Math.floor(fetchedBytes * 100 / totalBytes).toString() + "% completed, "
        text += timeElapsed + " secs elapsed.";
        text += " It can take a while when we first visit this page to populate the cache."
        text += " Later refreshes will become faster.";
        if (cacheOnly) {
          text = "Loading model from cache[" + iter + "/" + list.length + "]: ";
          text += Math.ceil(fetchedBytes / (1024 * 1024)).toString() + "MB loaded. "
          text += Math.floor(fetchedBytes * 100 / totalBytes).toString() + "% completed, "
          text += timeElapsed + " secs elapsed.";
        }
        this.initProgressCallback[j]({
          progress: fetchedBytes / totalBytes,
          timeElapsed: timeElapsed,
          cacheOnly: cacheOnly,
          text: text
        });
      }
    };

    for (let j = 0; j < this.initProgressCallback.length; ++j) {
      this.initProgressCallback[j]({
        progress: fetchedBytes / totalBytes,
        timeElapsed: 0,
        cacheOnly: cacheOnly,
        text: "Start to fetch params",
      });
    }

    for (let i = 0; i < list.length; ++i) {
      reportCallback(i);
      fetchedBytes += list[i].nbytes;
      const dataUrl = new URL(list[i].dataPath, ndarrayCacheUrl).href;
      let buffer;
      try {
        buffer = await (await artifactCache.fetchWithCache(dataUrl)).arrayBuffer();
      } catch (err) {
        this.env.logger("Error: Cannot fetch " + dataUrl + " err= " + err);
        throw err;
      }
      const shardRecords = list[i].records;
      for (let j = 0; j < shardRecords.length; ++j) {
        const rec = shardRecords[j];
        const cpu_arr = this.withNewScope(() => {
          return this.detachFromCurrentScope(
            this.empty(rec.shape, rec.dtype, this.cpu())
          )
        });
        const recSource = buffer.slice(rec.byteOffset, rec.byteOffset + rec.nbytes);
        // first sync copy to cpu.
        this.ctx.arrayDecodeStorage(cpu_arr, new Uint8Array(recSource), rec.format, rec.dtype);
        // then async stream into GPU if needed
        if (device.deviceType === DeviceStrToEnum.cpu) {
          this.ndarrayCacheUpdate(rec.name, cpu_arr, false);
          cpu_arr.dispose();
        } else {
          // allocate a gpu arr and async copy to it.
          const gpu_arr = this.withNewScope(() => {
            return this.detachFromCurrentScope(
              this.empty(rec.shape, rec.dtype, device)
            )
          });
          gpu_arr.copyFrom(cpu_arr);
          await device.sync();
          this.ndarrayCacheUpdate(rec.name, gpu_arr, false);
          cpu_arr.dispose();
          gpu_arr.dispose();
        }
      }
      timeElapsed = Math.ceil((perf.now() - tstart) / 1000);
    }
    reportCallback(list.length);
  }

this is now enabled

authors: DavidGOrtega tqchen

repo: mlc-ai/web-llm


text:
Add Adam baseline

Adam Baseline

Implementation: Optax's AdamW
Tunable hyperparameters: learning_rate, b1, b2, weight_decay
Fixed hyperparameters: epsilon=1e8, eps_root=0.0

I assume the LR schedule is the same as for the target-setting runs?
Should label_smoothing, grad_clip, and warmup_steps be tunable hyperparameters? And what about the same hyperparamters for the other baselines (for the ones with polynomial LR schedule also end_factor and decay_steps_factor)?

Addressed by #306.

repo: mlcommons/algorithmic-efficiency


text:
Create taskmanagerui.html

hello ,
kindly look into it this is the code for the task manager page, this is the html part. Kindly please look into it and merge it as it is my first contribution to the hactoberfest.
kindly , thank you

@AditiBanik I can't see any changes that you have made. Try making some visible changes.

authors: AditiBanik akshat-singh-dev

repo: mlsacbvp/task-manager


text:
Update requirements.txt

Updated pandas and streamlit version

Please kindly update it to what you used. Thanks.
On Tue, 12 Nov 2024, 20:51 Yusuf Okunlola, @.***> wrote:

The Scikit-learn version is 1.1.1
I saw that you added 1.3.0, that's why I did not update it.
—
Reply to this email directly, view it on GitHub
https://github.com/mlsanigeria/nigeria-crime-trends/pull/30#issuecomment-2471434782,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJ65HM64JXDHOZFVKOPQ732AJL3HAVCNFSM6AAAAABRUQXGTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZRGQZTINZYGI
.
You are receiving this because you commented.Message ID:
@.***>

authors: Sammybams yusufokunlola

repo: mlsanigeria/nigeria-crime-trends


text:
FEAT: Added rst2myst_static_file_path

Config value having entries of static asset paths.

aargh. always forget to run pytest on this one,


text:
Fix missing json dependency in Gemfile

The bundle exec jekyll build didn't work on my Fedora 23 x86_64 until I added this to Gemfile.
I couldn't find answers on stackoverflow and ended up with my own explanation.

Have you tried some of the things in this issue for another of my themes? https://github.com/mmistakes/minimal-mistakes/issues/261
I believe the problem is an upstream issue with the jekyll-sitemap plugin.
To verify that's the case remove gem "jekyll-sitemap" run bundle update then bundle exec jekyll serve and see if you still get the json error. If not then you know it's the Sitemap plugin and you might want to submit an issue there so it can be addressed upstream.
I don't doubt adding the json gem fixes something weird with your Ruby environment, I'd like to verify that's the case first so it can be properly addressed before I merge anything in.

OK, I'll try in a clean environment and reply with the results later.
I need to reproduce the issue as it appeared to me the first time.

I took both repositories at their current master commits:

hpstr-jekyll-theme: 8fd9634a02dcdc595e163e91e98a05ae1018b0d3
minimal-mistakes: 2e67f66bdc7e5184f1282b979f19e19577386395

The minimal-mistakes had no issues. So, we are focusing only on hpstr-jekyll-theme from now on.
I'm new to ruby and went pedantic (maybe too much) by breaking down my steps into this sequence with detailed output below:

Step 0: Change http to https
This is purely to make it work in proxied environment - just in case if change raises any question.

Step 1: Run bundle update.

Step 2: Run bundle exec jekyll build --trace --verbose.

Step 3: Remove gem "jekyll-sitemap".
NOTE: All local Git changes in Gemfile were reinstated as they were after Step 0 first.

Step 4: Re-run bundle update.

Step 5: Re-run bundle exec jekyll build --trace --verbose.

Step 6: Add gem "json".
NOTE: All local Git changes in Gemfile were reinstated as they were after Step 0 first.

Step 7: Re-run bundle update.

Step 8: Re-run bundle exec jekyll build --trace --verbose.

Based on result, removing gem "jekyll-sitemap" didn't help.
I'm not sure how it is in ruby, but it is strange why json wasn't picked up as transient dependency and has to be explicitly specified in the top-level project (the jekyll theme itself).
Anyway, adding gem "json" avoids these problems.
Step 0
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..e3a1b50 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,7 +1,7 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

 gem "jekyll", "~> 3.0"
 gem "jekyll-sitemap"
 gem "octopress"
 gem "jekyll-paginate"
 gem "jekyll-gist"

Step 1
bundle update

Fetching gem metadata from http://rubygems.org/...........
Fetching additional metadata from http://rubygems.org/..
Resolving dependencies...
Using addressable 2.4.0 (was 2.3.8)
Using colorator 0.1
Using multipart-post 2.0.0
Using faraday 0.9.2
Using ffi 1.9.10
Using sass 3.4.22 (was 3.4.21)
Using jekyll-sass-converter 1.4.0
Using rb-fsevent 0.9.7
Using rb-inotify 0.9.7 (was 0.9.5)
Using listen 3.1.1 (was 3.0.5)
Using jekyll-watch 1.3.1
Using kramdown 1.10.0 (was 1.9.0)
Using liquid 3.0.6
Using mercenary 0.3.6 (was 0.3.5)
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using jekyll 3.1.3 (was 3.1.1)
Using sawyer 0.7.0 (was 0.6.0)
Using octokit 4.3.0 (was 4.2.0)
Using jekyll-gist 1.4.0
Using jekyll-paginate 1.1.0
Using jekyll-sitemap 0.10.0
Using octopress-deploy 1.3.0
Using octopress-escape-code 2.1.1
Using octopress-hooks 2.6.1
Using redcarpet 3.3.4
Using titlecase 0.1.1
Using octopress 3.0.11
Using bundler 1.7.8
Your bundle is updated!

NOTE: There is no json dependency above.
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..e3a1b50 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,7 +1,7 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

 gem "jekyll", "~> 3.0"
 gem "jekyll-sitemap"
 gem "octopress"
 gem "jekyll-paginate"
 gem "jekyll-gist"
diff --git a/Gemfile.lock b/Gemfile.lock
index 98db538..438d356 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,72 +1,69 @@
 GEM
-  remote: https://rubygems.org/
+  remote: http://rubygems.org/
   specs:
-    addressable (2.3.8)
+    addressable (2.4.0)
     colorator (0.1)
     faraday (0.9.2)
       multipart-post (>= 1.2, < 3)
     ffi (1.9.10)
-    jekyll (3.1.1)
+    jekyll (3.1.3)
       colorator (~> 0.1)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 1.1)
       kramdown (~> 1.3)
       liquid (~> 3.0)
       mercenary (~> 0.3.3)
       rouge (~> 1.7)
       safe_yaml (~> 1.0)
     jekyll-gist (1.4.0)
       octokit (~> 4.2)
     jekyll-paginate (1.1.0)
     jekyll-sass-converter (1.4.0)
       sass (~> 3.4)
     jekyll-sitemap (0.10.0)
     jekyll-watch (1.3.1)
       listen (~> 3.0)
-    kramdown (1.9.0)
+    kramdown (1.10.0)
     liquid (3.0.6)
-    listen (3.0.5)
+    listen (3.1.1)
       rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9)
-    mercenary (0.3.5)
+      rb-inotify (>= 0.9.7)
+    mercenary (0.3.6)
     multipart-post (2.0.0)
-    octokit (4.2.0)
-      sawyer (~> 0.6.0, >= 0.5.3)
+    octokit (4.3.0)
+      sawyer (~> 0.7.0, >= 0.5.3)
     octopress (3.0.11)
       jekyll (>= 2.0)
       mercenary (~> 0.3.2)
       octopress-deploy
       octopress-escape-code (~> 2.0)
       octopress-hooks (~> 2.0)
       redcarpet (~> 3.0)
       titlecase
     octopress-deploy (1.3.0)
       colorator
     octopress-escape-code (2.1.1)
       jekyll (~> 3.0)
     octopress-hooks (2.6.1)
       jekyll (>= 2.0)
     rb-fsevent (0.9.7)
-    rb-inotify (0.9.5)
+    rb-inotify (0.9.7)
       ffi (>= 0.5.0)
     redcarpet (3.3.4)
     rouge (1.10.1)
     safe_yaml (1.0.4)
-    sass (3.4.21)
-    sawyer (0.6.0)
-      addressable (~> 2.3.5)
+    sass (3.4.22)
+    sawyer (0.7.0)
+      addressable (>= 2.3.5, < 2.5)
       faraday (~> 0.8, < 0.10)
     titlecase (0.1.1)

 PLATFORMS
   ruby

 DEPENDENCIES
   jekyll (~> 3.0)
   jekyll-gist
   jekyll-paginate
   jekyll-sitemap
   octopress
-
-BUNDLED WITH
-   1.11.2

Step 2
bundle exec jekyll build --trace --verbose

  Logging at level: debug
Configuration file: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_config.yml
         Requiring: jekyll-sitemap
         Requiring: jekyll-paginate
         Requiring: jekyll-gist
         Requiring: kramdown
            Source: /home/uvsmtid/Works/hpstr-jekyll-theme.git
       Destination: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       EntryFilter: excluded /README.md
       EntryFilter: excluded /Gemfile.lock
       EntryFilter: excluded /Rakefile.rb
       EntryFilter: excluded /package.json
       EntryFilter: excluded /LICENSE
       EntryFilter: excluded /Gemfile
       EntryFilter: excluded /Gruntfile.js
           Reading: _posts/2011-03-10-sample-post.md
           Reading: _posts/2013-08-12-sample-link-post.md
           Reading: _posts/2012-05-22-readability-post.md
           Reading: _posts/2013-08-16-code-highlighting-post.md
           Reading: _posts/2013-06-25-video-post.md
           Reading: _posts/2013-10-26-background-image.md
           Reading: _posts/2013-05-23-readability-feature-post.md
           Reading: _posts/2013-05-22-sample-post-images.md
         Rendering: sitemap.xml
  Pre-Render Hooks: sitemap.xml
/home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `require': cannot load such file -- json (LoadError)
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `<top (required)>'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/convertible.rb:249:in `do_layout'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/page.rb:130:in `render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-sitemap-0.10.0/lib/jekyll-sitemap.rb:61:in `sitemap_content'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-sitemap-0.10.0/lib/jekyll-sitemap.rb:54:in `block in write'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-sitemap-0.10.0/lib/jekyll-sitemap.rb:54:in `open'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-sitemap-0.10.0/lib/jekyll-sitemap.rb:54:in `write'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-sitemap-0.10.0/lib/jekyll-sitemap.rb:20:in `generate'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:154:in `block in generate'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:153:in `each'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:153:in `generate'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:58:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/command.rb:26:in `process_site'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:60:in `build'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:33:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:16:in `block (2 levels) in init_with_program'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `call'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/bin/jekyll:13:in `<top (required)>'
        from /home/uvsmtid/bin/jekyll:23:in `load'
        from /home/uvsmtid/bin/jekyll:23:in `<main>'

Step 3
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..70f8bce 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,7 +1,6 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

 gem "jekyll", "~> 3.0"
-gem "jekyll-sitemap"
 gem "octopress"
 gem "jekyll-paginate"
 gem "jekyll-gist"
diff --git a/_config.yml b/_config.yml
index 4bc7487..5222530 100644
--- a/_config.yml
+++ b/_config.yml
@@ -40,7 +40,6 @@ future:      true
 highlighter: rouge
 markdown:    kramdown
 gems:
-  - jekyll-sitemap
   - jekyll-paginate
   - jekyll-gist
 sass:

Step 4
bundle update

Fetching gem metadata from http://rubygems.org/...........
Fetching additional metadata from http://rubygems.org/..
Resolving dependencies...
Using addressable 2.4.0 (was 2.3.8)
Using colorator 0.1
Using multipart-post 2.0.0
Using faraday 0.9.2
Using ffi 1.9.10
Using sass 3.4.22 (was 3.4.21)
Using jekyll-sass-converter 1.4.0
Using rb-fsevent 0.9.7
Using rb-inotify 0.9.7 (was 0.9.5)
Using listen 3.1.1 (was 3.0.5)
Using jekyll-watch 1.3.1
Using kramdown 1.10.0 (was 1.9.0)
Using liquid 3.0.6
Using mercenary 0.3.6 (was 0.3.5)
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using jekyll 3.1.3 (was 3.1.1)
Using sawyer 0.7.0 (was 0.6.0)
Using octokit 4.3.0 (was 4.2.0)
Using jekyll-gist 1.4.0
Using jekyll-paginate 1.1.0
Using octopress-deploy 1.3.0
Using octopress-escape-code 2.1.1
Using octopress-hooks 2.6.1
Using redcarpet 3.3.4
Using titlecase 0.1.1
Using octopress 3.0.11
Using bundler 1.7.8
Your bundle is updated!

NOTE: Again, there is no json dependency above.
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..70f8bce 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,7 +1,6 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

 gem "jekyll", "~> 3.0"
-gem "jekyll-sitemap"
 gem "octopress"
 gem "jekyll-paginate"
 gem "jekyll-gist"
diff --git a/Gemfile.lock b/Gemfile.lock
index 98db538..db647c7 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,12 +1,12 @@
 GEM
-  remote: https://rubygems.org/
+  remote: http://rubygems.org/
   specs:
-    addressable (2.3.8)
+    addressable (2.4.0)
     colorator (0.1)
     faraday (0.9.2)
       multipart-post (>= 1.2, < 3)
     ffi (1.9.10)
-    jekyll (3.1.1)
+    jekyll (3.1.3)
       colorator (~> 0.1)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 1.1)
@@ -20,18 +20,17 @@ GEM
     jekyll-paginate (1.1.0)
     jekyll-sass-converter (1.4.0)
       sass (~> 3.4)
-    jekyll-sitemap (0.10.0)
     jekyll-watch (1.3.1)
       listen (~> 3.0)
-    kramdown (1.9.0)
+    kramdown (1.10.0)
     liquid (3.0.6)
-    listen (3.0.5)
+    listen (3.1.1)
       rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9)
-    mercenary (0.3.5)
+      rb-inotify (>= 0.9.7)
+    mercenary (0.3.6)
     multipart-post (2.0.0)
-    octokit (4.2.0)
-      sawyer (~> 0.6.0, >= 0.5.3)
+    octokit (4.3.0)
+      sawyer (~> 0.7.0, >= 0.5.3)
     octopress (3.0.11)
       jekyll (>= 2.0)
       mercenary (~> 0.3.2)
@@ -47,14 +46,14 @@ GEM
     octopress-hooks (2.6.1)
       jekyll (>= 2.0)
     rb-fsevent (0.9.7)
-    rb-inotify (0.9.5)
+    rb-inotify (0.9.7)
       ffi (>= 0.5.0)
     redcarpet (3.3.4)
     rouge (1.10.1)
     safe_yaml (1.0.4)
-    sass (3.4.21)
-    sawyer (0.6.0)
-      addressable (~> 2.3.5)
+    sass (3.4.22)
+    sawyer (0.7.0)
+      addressable (>= 2.3.5, < 2.5)
       faraday (~> 0.8, < 0.10)
     titlecase (0.1.1)

@@ -65,8 +64,4 @@ DEPENDENCIES
   jekyll (~> 3.0)
   jekyll-gist
   jekyll-paginate
-  jekyll-sitemap
   octopress
-
-BUNDLED WITH
-   1.11.2
diff --git a/_config.yml b/_config.yml
index 4bc7487..5222530 100644
--- a/_config.yml
+++ b/_config.yml
@@ -40,7 +40,6 @@ future:      true
 highlighter: rouge
 markdown:    kramdown
 gems:
-  - jekyll-sitemap
   - jekyll-paginate
   - jekyll-gist
 sass:

Step 5
bundle exec jekyll build --trace --verbose

  Logging at level: debug
Configuration file: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_config.yml
         Requiring: jekyll-paginate
         Requiring: jekyll-gist
         Requiring: kramdown
            Source: /home/uvsmtid/Works/hpstr-jekyll-theme.git
       Destination: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       EntryFilter: excluded /README.md
       EntryFilter: excluded /Gemfile.lock
       EntryFilter: excluded /Rakefile.rb
       EntryFilter: excluded /package.json
       EntryFilter: excluded /LICENSE
       EntryFilter: excluded /Gemfile
       EntryFilter: excluded /Gruntfile.js
           Reading: _posts/2011-03-10-sample-post.md
           Reading: _posts/2013-08-12-sample-link-post.md
           Reading: _posts/2012-05-22-readability-post.md
           Reading: _posts/2013-08-16-code-highlighting-post.md
           Reading: _posts/2013-06-25-video-post.md
           Reading: _posts/2013-10-26-background-image.md
           Reading: _posts/2013-05-23-readability-feature-post.md
           Reading: _posts/2013-05-22-sample-post-images.md
         Rendering: _posts/2011-03-10-sample-post.md
  Pre-Render Hooks: _posts/2011-03-10-sample-post.md
/home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `require': cannot load such file -- json (LoadError)
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `<top (required)>'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/renderer.rb:53:in `run'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:171:in `block (2 levels) in render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in `each'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in `block in render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in `each'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in `render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:59:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/command.rb:26:in `process_site'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:60:in `build'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:33:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:16:in `block (2 levels) in init_with_program'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `call'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/bin/jekyll:13:in `<top (required)>'
        from /home/uvsmtid/bin/jekyll:23:in `load'
        from /home/uvsmtid/bin/jekyll:23:in `<main>'

Step 6
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..89fee7a 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,5 +1,6 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

+gem "json"
 gem "jekyll", "~> 3.0"
 gem "jekyll-sitemap"
 gem "octopress"

Step 7
bundle update

Fetching gem metadata from http://rubygems.org/...........
Fetching additional metadata from http://rubygems.org/..
Resolving dependencies...
Using addressable 2.4.0 (was 2.3.8)
Using colorator 0.1
Using multipart-post 2.0.0
Using faraday 0.9.2
Using ffi 1.9.10
Using sass 3.4.22 (was 3.4.21)
Using jekyll-sass-converter 1.4.0
Using rb-fsevent 0.9.7
Using rb-inotify 0.9.7 (was 0.9.5)
Using listen 3.1.1 (was 3.0.5)
Using jekyll-watch 1.3.1
Using kramdown 1.10.0 (was 1.9.0)
Using liquid 3.0.6
Using mercenary 0.3.6 (was 0.3.5)
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using jekyll 3.1.3 (was 3.1.1)
Using sawyer 0.7.0 (was 0.6.0)
Using octokit 4.3.0 (was 4.2.0)
Using jekyll-gist 1.4.0
Using jekyll-paginate 1.1.0
Using jekyll-sitemap 0.10.0
Using json 1.8.3
Using octopress-deploy 1.3.0
Using octopress-escape-code 2.1.1
Using octopress-hooks 2.6.1
Using redcarpet 3.3.4
Using titlecase 0.1.1
Using octopress 3.0.11
Using bundler 1.7.8
Your bundle is updated!

NOTE: Finally, there is json dependency above.
git diff

diff --git a/Gemfile b/Gemfile
index 0a429af..89fee7a 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,5 +1,6 @@
-source "https://rubygems.org"
+source "http://rubygems.org"

+gem "json"
 gem "jekyll", "~> 3.0"
 gem "jekyll-sitemap"
 gem "octopress"
diff --git a/Gemfile.lock b/Gemfile.lock
index 98db538..cb4e703 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,12 +1,12 @@
 GEM
-  remote: https://rubygems.org/
+  remote: http://rubygems.org/
   specs:
-    addressable (2.3.8)
+    addressable (2.4.0)
     colorator (0.1)
     faraday (0.9.2)
       multipart-post (>= 1.2, < 3)
     ffi (1.9.10)
-    jekyll (3.1.1)
+    jekyll (3.1.3)
       colorator (~> 0.1)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 1.1)
@@ -23,15 +23,16 @@ GEM
     jekyll-sitemap (0.10.0)
     jekyll-watch (1.3.1)
       listen (~> 3.0)
-    kramdown (1.9.0)
+    json (1.8.3)
+    kramdown (1.10.0)
     liquid (3.0.6)
-    listen (3.0.5)
+    listen (3.1.1)
       rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9)
-    mercenary (0.3.5)
+      rb-inotify (>= 0.9.7)
+    mercenary (0.3.6)
     multipart-post (2.0.0)
-    octokit (4.2.0)
-      sawyer (~> 0.6.0, >= 0.5.3)
+    octokit (4.3.0)
+      sawyer (~> 0.7.0, >= 0.5.3)
     octopress (3.0.11)
       jekyll (>= 2.0)
       mercenary (~> 0.3.2)
@@ -47,14 +48,14 @@ GEM
     octopress-hooks (2.6.1)
       jekyll (>= 2.0)
     rb-fsevent (0.9.7)
-    rb-inotify (0.9.5)
+    rb-inotify (0.9.7)
       ffi (>= 0.5.0)
     redcarpet (3.3.4)
     rouge (1.10.1)
     safe_yaml (1.0.4)
-    sass (3.4.21)
-    sawyer (0.6.0)
-      addressable (~> 2.3.5)
+    sass (3.4.22)
+    sawyer (0.7.0)
+      addressable (>= 2.3.5, < 2.5)
       faraday (~> 0.8, < 0.10)
     titlecase (0.1.1)

@@ -66,7 +67,5 @@ DEPENDENCIES
   jekyll-gist
   jekyll-paginate
   jekyll-sitemap
+  json
   octopress
-
-BUNDLED WITH
-   1.11.2

Step 8
 bundle exec jekyll build --trace --verbose
  Logging at level: debug
Configuration file: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_config.yml
         Requiring: jekyll-sitemap
         Requiring: jekyll-paginate
         Requiring: jekyll-gist
         Requiring: kramdown
            Source: /home/uvsmtid/Works/hpstr-jekyll-theme.git
       Destination: /home/uvsmtid/Works/hpstr-jekyll-theme.git/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       EntryFilter: excluded /README.md
       EntryFilter: excluded /Gemfile.lock
       EntryFilter: excluded /Rakefile.rb
       EntryFilter: excluded /package.json
       EntryFilter: excluded /LICENSE
       EntryFilter: excluded /Gemfile
       EntryFilter: excluded /Gruntfile.js
           Reading: _posts/2011-03-10-sample-post.md
           Reading: _posts/2013-08-12-sample-link-post.md
           Reading: _posts/2012-05-22-readability-post.md
           Reading: _posts/2013-08-16-code-highlighting-post.md
           Reading: _posts/2013-06-25-video-post.md
           Reading: _posts/2013-10-26-background-image.md
           Reading: _posts/2013-05-23-readability-feature-post.md
           Reading: _posts/2013-05-22-sample-post-images.md
         Rendering: sitemap.xml
  Pre-Render Hooks: sitemap.xml
  Rendering Liquid: sitemap.xml
  Rendering Markup: sitemap.xml
 Post-Render Hooks: sitemap.xml
         Rendering: _posts/2011-03-10-sample-post.md
  Pre-Render Hooks: _posts/2011-03-10-sample-post.md
  Rendering Liquid: _posts/2011-03-10-sample-post.md
         Requiring: rouge
         Requiring: rouge
  Rendering Markup: _posts/2011-03-10-sample-post.md
         Requiring: kramdown
  Rendering Layout: _posts/2011-03-10-sample-post.md
         Rendering: _posts/2012-05-22-readability-post.md
  Pre-Render Hooks: _posts/2012-05-22-readability-post.md
  Rendering Liquid: _posts/2012-05-22-readability-post.md
  Rendering Markup: _posts/2012-05-22-readability-post.md
  Rendering Layout: _posts/2012-05-22-readability-post.md
         Rendering: _posts/2013-05-22-sample-post-images.md
  Pre-Render Hooks: _posts/2013-05-22-sample-post-images.md
  Rendering Liquid: _posts/2013-05-22-sample-post-images.md
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
  Rendering Markup: _posts/2013-05-22-sample-post-images.md
  Rendering Layout: _posts/2013-05-22-sample-post-images.md
         Rendering: _posts/2013-05-23-readability-feature-post.md
  Pre-Render Hooks: _posts/2013-05-23-readability-feature-post.md
  Rendering Liquid: _posts/2013-05-23-readability-feature-post.md
  Rendering Markup: _posts/2013-05-23-readability-feature-post.md
  Rendering Layout: _posts/2013-05-23-readability-feature-post.md
         Rendering: _posts/2013-06-25-video-post.md
  Pre-Render Hooks: _posts/2013-06-25-video-post.md
  Rendering Liquid: _posts/2013-06-25-video-post.md
         Requiring: rouge
  Rendering Markup: _posts/2013-06-25-video-post.md
  Rendering Layout: _posts/2013-06-25-video-post.md
         Rendering: _posts/2013-08-12-sample-link-post.md
  Pre-Render Hooks: _posts/2013-08-12-sample-link-post.md
  Rendering Liquid: _posts/2013-08-12-sample-link-post.md
  Rendering Markup: _posts/2013-08-12-sample-link-post.md
  Rendering Layout: _posts/2013-08-12-sample-link-post.md
         Rendering: _posts/2013-08-16-code-highlighting-post.md
  Pre-Render Hooks: _posts/2013-08-16-code-highlighting-post.md
  Rendering Liquid: _posts/2013-08-16-code-highlighting-post.md
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
  Rendering Markup: _posts/2013-08-16-code-highlighting-post.md
  Rendering Layout: _posts/2013-08-16-code-highlighting-post.md
         Rendering: _posts/2013-10-26-background-image.md
  Pre-Render Hooks: _posts/2013-10-26-background-image.md
  Rendering Liquid: _posts/2013-10-26-background-image.md
         Requiring: rouge
  Rendering Markup: _posts/2013-10-26-background-image.md
  Rendering Layout: _posts/2013-10-26-background-image.md
         Rendering: 404.md
  Pre-Render Hooks: 404.md
  Rendering Liquid: 404.md
  Rendering Markup: 404.md
  Rendering Layout: 404.md
         Rendering: feed.xml
  Pre-Render Hooks: feed.xml
  Rendering Liquid: feed.xml
  Rendering Markup: feed.xml
  Rendering Layout: feed.xml
         Rendering: /posts/index.html
  Pre-Render Hooks: /posts/index.html
  Rendering Liquid: /posts/index.html
  Rendering Markup: /posts/index.html
  Rendering Layout: /posts/index.html
         Rendering: /tags/index.html
  Pre-Render Hooks: /tags/index.html
  Rendering Liquid: /tags/index.html
  Rendering Markup: /tags/index.html
  Rendering Layout: /tags/index.html
         Rendering: index.html
  Pre-Render Hooks: index.html
  Rendering Liquid: index.html
  Rendering Markup: index.html
  Rendering Layout: index.html
         Rendering: /theme-setup/index.md
  Pre-Render Hooks: /theme-setup/index.md
  Rendering Liquid: /theme-setup/index.md
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
         Requiring: rouge
  Rendering Markup: /theme-setup/index.md
  Rendering Layout: /theme-setup/index.md
         Rendering: /about/index.md
  Pre-Render Hooks: /about/index.md
  Rendering Liquid: /about/index.md
  Rendering Markup: /about/index.md
  Rendering Layout: /about/index.md
         Rendering: /assets/css/main.scss
  Pre-Render Hooks: /assets/css/main.scss
  Rendering Liquid: /assets/css/main.scss
  Rendering Markup: /assets/css/main.scss
         Rendering: /page2/index.html
  Pre-Render Hooks: /page2/index.html
  Rendering Liquid: /page2/index.html
  Rendering Markup: /page2/index.html
  Rendering Layout: /page2/index.html
                    done in 1.107 seconds.
 Auto-regeneration: disabled. Use --watch to enable.

I'm no Ruby expert either and I barely understand it myself. I have no problem merging in the change as it appears harmless, but it still bothers me as to what is causing the problem.
The json gem is definitely needed by something. I'm almost 100% certain it's one of the Jekyll plugins that needs it but aren't requiring it properly in their Gemfile.
Can you do one more test just to identify if it's your environment. It would be helpful to identify if it's one of the gems too so they can fix it upstream for other users.
Test Scenario 1

Create a new Jekyll project. jekyll new test-site
cd test-site and then run bundle init.
Add gem "jekyll" to Gemfile then bundle install.
Run bundle exec jekyll build and see if you get the json error.

Test Scenario 2

Use the same test-site project but add the following gems to Gemfile

gem "jekyll-sitemap"
gem "octopress"
gem "jekyll-paginate"
gem "jekyll-gist"

Run bundle install then bundle exec jekyll build.
See if the error occurs. If it does start adding each gem one by one, running bundle each time then bundle exec jekyll build to determine which gem is the problem`.

I think you nailed it in the scenario 1. :+1:
It seems bundle has no information from jekyll gem about its dependency on json.
So, should it be an issue with jekyll 3.1.3 as output suggests?
Test Scenario 1
I put commands in try.sh script to capture whole output at ounce:
#/bin/sh
set -e
set -v
set -x
test ! -e test-site
jekyll new test-site
cd test-site
bundle init
echo 'gem "jekyll"' >> Gemfile
cat Gemfile
bundle install
bundle update
bundle exec jekyll build

Output :
set -x # debut output
test ! -e test-site
++ test '!' -e test-site
jekyll new test-site
++ jekyll new test-site
WARN: Unresolved specs during Gem::Specification.reset:
      listen (~> 3.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
New jekyll site installed in /mnt/btrfs/home/_/uvsmtid/Works/test-site/test-site.
cd test-site
++ cd test-site
bundle init
++ bundle init
Writing new Gemfile to /mnt/btrfs/home/_/uvsmtid/Works/test-site/test-site/Gemfile
echo 'gem "jekyll"' >> Gemfile
++ echo 'gem "jekyll"'
cat Gemfile
++ cat Gemfile
# A sample Gemfile
source "https://rubygems.org"

# gem "rails"
gem "jekyll"
bundle install
++ bundle install
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using colorator 0.1
Using ffi 1.9.10
Using sass 3.4.22
Using rb-fsevent 0.9.7
Using kramdown 1.10.0
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using bundler 1.11.2
Using rb-inotify 0.9.7
Using jekyll-sass-converter 1.4.0
Using listen 3.1.1
Using jekyll-watch 1.3.1
Using jekyll 3.1.3
Bundle complete! 1 Gemfile dependency, 15 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
bundle update
++ bundle update
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using colorator 0.1
Using ffi 1.9.10
Using sass 3.4.22
Using rb-fsevent 0.9.7
Using kramdown 1.10.0
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using bundler 1.11.2
Using rb-inotify 0.9.7
Using jekyll-sass-converter 1.4.0
Using listen 3.1.1
Using jekyll-watch 1.3.1
Using jekyll 3.1.3
Bundle updated!
bundle exec jekyll build
++ bundle exec jekyll build
Configuration file: /mnt/btrfs/home/_/uvsmtid/Works/test-site/test-site/_config.yml
            Source: /mnt/btrfs/home/_/uvsmtid/Works/test-site/test-site
       Destination: /mnt/btrfs/home/_/uvsmtid/Works/test-site/test-site/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
/home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `require': cannot load such file -- json (LoadError)
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in `<top (required)>'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/renderer.rb:53:in `run'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:171:in `block (2 levels) in render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in `each'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in `block in render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in `each'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in `render'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:59:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/command.rb:26:in `process_site'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:60:in `build'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:33:in `process'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:16:in `block (2 levels) in init_with_program'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `call'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/bin/jekyll:13:in `<top (required)>'
        from /home/uvsmtid/bin/jekyll:23:in `load'
        from /home/uvsmtid/bin/jekyll:23:in `<main>'

Scenario 2
I just tried adding suggested dependencies together to see if error disappears.
Because it failed in Scenario 1 and in Scenario 2 using full list, I didn't try combinations in the middle.

I would, just so their aware of it. Or maybe there's some other fix. Let me
know what you find, in the meantime I'm planning on merging your PR in
since it gets the job done for now.
On Mon, Apr 25, 2016 at 9:08 AM, Alexey Pakseykin notifications@github.com
wrote:

I think you nailed it in the scenario 1. [image: :+1:]
It seems bundle has no information from jekyll gem about its dependency
on json.
So, should it be an issue with jekyll 3.1.3 as output suggests?
Test Scenario 1
I put commands in try.sh script to capture whole output at ounce:
#/bin/sh
set -e
set -v
set -x
test ! -e test-site
jekyll new test-site
cd test-site
bundle init
echo 'gem "jekyll"' >> Gemfile
cat Gemfile
bundle install
bundle update
bundle exec jekyll build
Output :
set -x # debut output
test ! -e test-site
++ test '!' -e test-site
jekyll new test-site
++ jekyll new test-site
WARN: Unresolved specs during Gem::Specification.reset:
listen (~> 3.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
New jekyll site installed in /mnt/btrfs/home//uvsmtid/Works/test-site/test-site.
cd test-site
++ cd test-site
bundle init
++ bundle init
Writing new Gemfile to /mnt/btrfs/home//uvsmtid/Works/test-site/test-site/Gemfile
echo 'gem "jekyll"' >> Gemfile
++ echo 'gem "jekyll"'
cat Gemfile
++ cat Gemfile
A sample Gemfile
source "https://rubygems.org"
gem "rails"
gem "jekyll"
bundle install
++ bundle install
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using colorator 0.1
Using ffi 1.9.10
Using sass 3.4.22
Using rb-fsevent 0.9.7
Using kramdown 1.10.0
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using bundler 1.11.2
Using rb-inotify 0.9.7
Using jekyll-sass-converter 1.4.0
Using listen 3.1.1
Using jekyll-watch 1.3.1
Using jekyll 3.1.3
Bundle complete! 1 Gemfile dependency, 15 gems now installed.
Use bundle show [gemname] to see where a bundled gem is installed.
bundle update
++ bundle update
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using colorator 0.1
Using ffi 1.9.10
Using sass 3.4.22
Using rb-fsevent 0.9.7
Using kramdown 1.10.0
Using liquid 3.0.6
Using mercenary 0.3.6
Using rouge 1.10.1
Using safe_yaml 1.0.4
Using bundler 1.11.2
Using rb-inotify 0.9.7
Using jekyll-sass-converter 1.4.0
Using listen 3.1.1
Using jekyll-watch 1.3.1
Using jekyll 3.1.3
Bundle updated!
bundle exec jekyll build
++ bundle exec jekyll build
Configuration file: /mnt/btrfs/home//uvsmtid/Works/test-site/test-site/config.yml
Source: /mnt/btrfs/home//uvsmtid/Works/test-site/test-site
Destination: /mnt/btrfs/home//uvsmtid/Works/test-site/test-site/_site
Incremental build: disabled. Enable with --incremental
Generating...
/home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in require': cannot load such file -- json (LoadError)         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/filters.rb:2:in <top (required)>'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/renderer.rb:53:in run'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:171:in block (2 levels) in render'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in each'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:169:in block in render'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in each'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:168:in render'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/site.rb:59:in process'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/command.rb:26:in process_site'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:60:in build'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:33:in process'
from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/lib/jekyll/commands/build.rb:16:in block (2 levels) in init_with_program'         from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in call'
from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in block in execute'         from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in each'
from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in execute'         from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in go'
from /home/uvsmtid/.gem/ruby/gems/mercenary-0.3.6/lib/mercenary.rb:19:in program'         from /home/uvsmtid/.gem/ruby/gems/jekyll-3.1.3/bin/jekyll:13:in <top (required)>'
from /home/uvsmtid/bin/jekyll:23:in load'         from /home/uvsmtid/bin/jekyll:23:in '
Scenario 2
I just tried adding suggested dependencies together to see if error
disappears.
Because it failed in Scenario 1 and in Scenario 2 using full list, I
didn't try combinations in the middle.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/mmistakes/hpstr-jekyll-theme/pull/147#issuecomment-214310144

authors: mmistakes uvsmtid

repo: mmistakes/hpstr-jekyll-theme

license: mit

license_source: bigquery


text:
Center aligning the main content

In higher resolution screens the right-hand space feels quite empty when everything is left aligned.
I would like to center align the contents of the home page and the post page.
So, it should look something like this.

How can I achieve the above? Thank you.

Thank you, that worked. BTW I really liked your tiny paintings. :smile:

Add margin-left: auto; and margin-right: auto; to the .inner element via CSS and it'll center those elements like you want.
.inner {
  max-width: $large;
  margin-left: auto;
  margin-right: auto;
}

ref: https://github.com/mmistakes/jekyll-theme-basically-basic/blob/master/_sass/basically-basic/_layout.scss#L59-L61

Add margin-left: auto; and margin-right: auto; to the .inner element via CSS and it'll center those elements like you want.
.inner {
  max-width: $large;
  margin-left: auto;
  margin-right: auto;
}

ref: https://github.com/mmistakes/jekyll-theme-basically-basic/blob/master/_sass/basically-basic/_layout.scss#L59-L61

Hi!
How can I keep the hero image aligned to the left while making the content centre aligned?
@mmistakes @8hantanu

Add margin-left: auto; and margin-right: auto; to the .inner element via CSS and it'll center those elements like you want.
.inner {
  max-width: $large;
  margin-left: auto;
  margin-right: auto;
}

ref: https://github.com/mmistakes/jekyll-theme-basically-basic/blob/master/_sass/basically-basic/_layout.scss#L59-L61

Thank you it worked for me as well! I have an other question as well. Do you know how I could make the content wider? It looks a bit strange that I have such huge margins and the content is shrunk in the middle.
Thank you in advance! : )

repo: mmistakes/jekyll-theme-basically-basic


text:
paginate help

1.Include the jekyll-paginate plugin in your Gemfile.
group :jekyll_plugins do
gem "jekyll-paginate"
end
2.Add jekyll-paginate to the plugins array (previously gems) in your _config.yml file and the following pagination settings:
paginate: 10  # amount of posts to show per page
paginate_path: /page:num/
3.Create index.html (or rename index.md) in the root of your project and add the following front matter:
layout: home
paginate: true
i do the same as your tutor, but i got an error:
Pagination: Pagination is enabled, but I couldn't find an index.html page to use as the pagination template. Skipping pagination.
what would i do, i need help

repo: mmistakes/so-simple-theme


text:
[expect-type] not.toMatchTypeOf error on non-matching union type

Thanks for your work on this library. Ran into this scenario today:
expectTypeOf<string | number>().toMatchTypeOf<string>(); // Error (as expected)
expectTypeOf<string | number>().not.toMatchTypeOf<string>(); // Error (?)

I think the second line should not produce an error.
Edit: same with expectTypeOf<any>
expect-type@0.9.2, typescript@4.1.2

This is an interesting one, and maybe kind of philosophical. toMatchTypeOf corresponds to extends. The type logic relies on distributive conditional types, which means that when typescript evaluates string | number extends string ? true : false, it produces a union of string extends string ? true : false (=> true) and number extends string ? true : false (=> false).
So the result is true | false, which is the same as boolean. For toMatchTypeOf to succeed, it would need to be true. For .not.toMatchTypeOf to succeed, it would need to be false. But it's neither!
I think there's an argument this is correct behaviour, or at least as good as we're likely to get. The type system can't say with confidence that it does or doesn't match, because we haven't really said what "it" is - whether it matches depends on whether it's a string or a number. I can't immediately think of how to "fix" this without side-effects.
In the real world, though, I guess you just want to write a type assertion. So it'd be good to hear about the specific use case. Can you just use toEqualTypeOf? This works as expected:
expectTypeOf<string | number>().not.toEqualTypeOf<string>()

Relatedly, I think there's room to improve the UX around union types generally. Maybe something like
expectTypeOf<string | number>().excluding<number>().toBeString()
expectTypeOf<string | number>().excluding<boolean>().toBeString() // Error, can't exclude boolean from string | number

toMatchTypeOf corresponds to extends

Right, I assumed toMatchTypeOf would be roughly equivalent to "is assignable to this type", i.e.
const x: string = "foo" as string | number // Error

which is why false made sense to me. I also assumed that .not would simply flip the result of the following assertion, but the actual behavior makes sense with your explanation, and with that in mind I don't necessarily think this needs to be "fixed", just something to be aware of.

So it'd be good to hear about the specific use case

My use case goes back to the question of assignability. Basically, I'm trying to figure out how best to simulate TypeScript error ts(2322) when adding unknown properties to a typed object literal (without actually reproducing the error in the test suite, of course). The type in question is a generic mapped type with well-defined properties (no extras allowed) unioned with a bunch of primitive values (numbers and strings), hence this "discovery".
toEqualTypeOf does seem like the better fit here, as it forbids extras, except you have to basically pretend the type being tested is the complete type, optional properties and all, otherwise:
expectTypeOf<{foo: string}>().toEqualTypeOf<{foo: string, bar?: number}>() // Error, missing bar?
expectTypeOf<{foo: string} | number>().toEqualTypeOf<{foo: string}>() // Error, missing number

In the end I settled on this:
expectTypeOf<Thing | {extra?: any}>().not.toEqualTypeOf<Thing>`()

where Thing is the complete union type and extra is a property I know will not be present in the case I am testing. I think it's close enough, though not sure if 100% sound.

Relatedly, I think there's room to improve the UX around union types generally

Sounds neat, basically a way of exhaustively testing union members, right?

I'm still not sure I fully understand the scenario, but yeah I don't know if .not.toEqualTypeOf is particularly useful there, since it distinguishes between any and other types so it might pass too easily. What does the union type Thing need to look like?

type ResponsiveProp<T> = T | T[] | { xs?: T, sm?: T, md?: T, ... }

This is for a React component, the keys correspond to CSS @media breakpoints. Actually a mapped type, because the names of the keys are configurable, but the shape would end up something like this.
I think I could also isolate the object part and test it without the union. Mainly I want to test that no unknown keys can creep into the type because something of something that got refactored down the line. You're right about any, in this case I'd substitute in the concrete type of T.
Sorry, this is kind of straying off the topic of the original issue.

authors: mmkal reiv

repo: mmkal/ts


text:
Handle unexpected return values

I noticed that we are using a very simple case statement to enforce the behaviour of the PullConsumer which means that if a user ever implements a function that has an unexpected return value it will crash their PullConsumer without sending back a NACK or any other indication to the jetstream server.
I think this type of thing could happen pretty easily by using a with statement in user code.
This seems like something we should handle by logging an error and potentially returning a NACK to jetstream, but we probably shouldn't just crash the whole PullConsumer?

Returning something unexpected is a programmer error, and personally I would throw tantrums from our code in such case because it's contract violation.
I do agree that raising a more meaningful exception is a good thing here to do.
I am not sure if we should send NACK back because:

a stream may be configured in NoAck mode for example
not sending anything is also a Jetstream-recognizable behaviour (as far as I know, I may be wrong) and it means that consumer encountered an internal error -- which is exactly the thing that happens here

authors: mkaput mmmries

repo: mmmries/jetstream


text:
Does not work with Metrics.NET v3.4 (the latest) prerelease?

Metrics.NET v3.4-pre is not supported? It is true that it is prerelease, but obviously guys that are working on Metrics.NET do not care too much about releases (the last release is 2.16 from March 2015), so we must go with prerelease versions.
Anyway, Metrics.NET.InfluxDB 2.05 beta with Metrics.NET 3.4-pre throws the following exception:
`An unhandled exception of type 'System.MissingMethodException' occurred in Metrics.NET.InfluxDB.dll
Additional information: Method not found: 'Metrics.Reports.MetricsReports Metrics.Reports.MetricsReports.WithReport(Metrics.Reporters.MetricsReport, System.TimeSpan)'.`
Thanks
PS. Honestly, if I were you, I wouldn't know what to do - to stick with the release version of the parent project, or to work on compatibility with prereleases.

In a very unfortunate turn of events, the original author and maintainer of Metrics.NET passed away. His former employer stepped up and has taken ownership of the project within the last month or two. Hopefully they will give it the attention it deserves.
I'm holding out hope that the 3.x series will soon be released as a full version. If not, I'd consider a 3.x branch of this lib that tracks 3.x of Metrics.NET, assuming it has a good ROI. To that end -- have you found 3.4-pre to be stable? What additional features/fixes does it add that you find particularly valuable?

I'm holding out hope that the 3.x series will soon be released as a full version. If not, I'd consider a 3.x branch of this lib that tracks 3.x of Metrics.NET, assuming it has a good ROI. To that end -- have you found 3.4-pre to be stable? What additional features/fixes does it add that you find particularly valuable?

Turns out I needed a 3.x-pre version b/c of the Owin.Metrics package we're using. I've pushed a v3 branch as well as a 3.x package to NuGet.

Huh, I'm very sad to hear that! RIP...
Regarding stability of 3.x - I can't help you at the moment since I'm just starting to implement Matrix.NET - not enough experience. And obviously since I'm bound to Metrix.NET.InfluxDb - I will not migrate to 3.x before you do.
Regarding 3.x features I need - at the moment nothing. I simply assumed that the newer versions can be improved in terms of stability and performance, so I wanted to go there. Soon I will implement Metrics.NET in MVC/Owin project, and I'll see if some of the new features are needed there. I'll let you know.
Thanks for being so helpful! I wish you luck.

Hey, 3.0.59  version depends on Metrics.NET v3.4? It means that you've migrated towards their prerelease?

Yep. The day after you mentioned it I found that I needed to do it because we had become dependent on v3 of the Metrics OWIN extension.

Re "implement Metrics.NET in MVC/Owin" I wrote the current Metrics.Net OWIN adapter, OWIN's a thing of the past now (that didn't last long :)), I've written and adapter for ASP.NET Core  if you're interested - https://www.nuget.org/packages/AspNet.Metrics/.
I just hooked the this package up to the MVC sample, works well thanks! You should point to this in the Metrics.NET wiki - https://github.com/Recognos/Metrics.NET/wiki/InfluxDb
Running the latest influx db on the Windows 10 Linux subsystem works like a charm as well :)

authors: alhardy mnadel peske


text:
List command fails with "--week" option and invalid timestamp pattern

The following command line fails:
rbnotes list --week 2020

Traceback says;
Invalid timestamp pattern: cannot convert to a date [2020] (Rbnotes::InvalidTimestampPatternError)

The fix will be to add InvalidTimestampPatternError to the rescue clause to the top level of rbnotes.

repo: mnbi/rbnotes


text:
ENH: add plotting method / function for global field power

Since we're polishing our sensor space / EEG edge I thought it would be time for it.
Like here: https://gist.github.com/dengemann/deb5e011d7d6b0c60fa9
cc @agramfort

ping @teonlamont

haha, I had the same idea and forgot about it. seems like this could address https://github.com/mne-tools/mne-python/issues/1939. It could be combined with @jona-sassenhagen's suggestion for auto plotting predefined rois, etc.

Do we need this even though we have the GFP? (We have the GFP right?) If it's about selecting a subset of sensors, can't they do evoked.pick_types(...) or evoked.pick_channels(...).plot_white() now?

ideally, I would like to have some very simple ways to plot contrasts in sensor space. in the way of ERP analysis, it is useful to be able to do one of the following, for a given set of contrasts, e.g. evoked a, and evoked b:

select a single channel and plot the contrast of evoked a and evoked b
select a region of interest (pick several channels) and plot the contrast. for ERP, plot the average over the channels, for ERF, plot the RMS of the channels.
split the channels into pre-defined regions and plot the contrast. ERP, average, ERF, RMS.
(minor addition, the ability to flip the axes for ERPs to be à la mode)

This would be a simple but pretty use addition. it doesn't have to be wrapped in the plot_gfp.  it could be something like plot_contrasts. It's very useful with teaching, and it is still useful with ERP-related research.

GFP is independent of noise cov for the common use case.

@teonlamont can you open a different issue for that, then? The title and most of the discussion of this one is a bit confusing.
@agramfort so you're saying we still need a separate function to plot the GFP?

ok, i just reopened the one I closed. this topic is mostly about gfp, but there were mentions of a general plotting function. so it seemed like this might be a relevant topic

@agramfort https://github.com/agramfort so you're saying we still need
a separate function to plot the GFP?

I would add it to plot evoked method. A green line like brainstorm does it.
http://neuroimage.usc.edu/brainstorm/Tutorials/TutSourceEstimation?action=AttachFile&do=get&target=sources1.gif

Does anyone have time for this one?

I'm +0 on this ... We should mark it 0.10, my 2 cents.

Done, if someone feels passionately about it, let them be the one to implement it for 0.9 :)

What would this entail?  Just a gfp trace at the bottom of evoked.plot() and/or a separate gfp plotting method for Evoked objects?  Are we talking the traditional definition from Lehmann and Skrandies using spatial variance?  I've been computing this a lot recently, so it would be relatively straight forward to implement I think.  I would propose the following:

An option to evoked.plot() called gfp, defaulted to False.  So the call evoked.plot(gfp=True) would produce the brainstorm-like plot that @agramfort mentions.

An Evoked method called plot_gfp, so that the call evoked.plot_gfp() would return only the gfp and not the butterfly.  Perhaps also an optional cov arg, defaulted to None that, if passed, would whiten the Evoked first?  I guess that's maybe not necessary since we already have mne.whiten_evoked().

+1 for 1.

We have 2 already, evoked.plot_white

We have 2 already, evoked.plot_white

I was wondering about that,  but wouldn't it make sense to have a basic method for Evoked objects for plotting just the gfp?

@teonlamont, are you indifferent or -1 on suggestion 2?

I wanted to say that would be complementary.

On 23 Apr 2015, at 12:16, "Andrew R. Dykstra" notifications@github.com wrote:
@teonlamont, are you indifferent or -1 on suggestion 2?
—
Reply to this email directly or view it on GitHub.

+1 for 1
plot_white is using a noise cov which makes it different.

how about gfp = True/False/'only'

I'd start with True/False but whatever

Do we really need to keep adding stuff just shortly before releasing?
We used to have a 2 week feature addition stop and usually many bugs
emerged and were fixed after that point.
Would it make sense to release in one or two weaks but stop with
implementations of whatever in 2 days?
2015-04-23 14:51 GMT+02:00 Alexandre Gramfort notifications@github.com:

I'd start with True/False but whatever
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/issues/1276#issuecomment-95575497
.

+1000
this was not suggested for 0.9

Ah ok. Sorry then. Anyways. We should stop pushing features and spend more days on bug search and fixing.

Do we really need to keep adding stuff just shortly before releasing?

Doesn't matter to me whether this goes into 0.9 or not - just thought that since no one was picking it up I could.
I'm gathering that folks are -1 on creating separate gfp plots?  That would actually be my main use case, as opposed to including it at the bottom of an evoked butterfly plot.

@adykstra that's why I suggesting an option to gfp that if it is 'only', then it would plot just the gfp and not the butterfly plot. since it's in evoked.plot, it would save on a separate method.

Would gfp=True | False | 'only' work for your case @adykstra?

Definitely, but a separate method to accomplish it seems cleaner and more explicit to me.  I'd be happy with either though.

I think the push to avoid more functions will make it easier just to have a param. @adykstra you up for making a PR? It may or may not make it into 0.9 depending on what we decide regarding a feature freeze, but it sounds like we want it eventually regardless.

you up for making a PR?

Sure.

@dengemann, regarding rank, is estimate_rank from mne.utils sufficient?  For the example data, it returns 67 (65) for grads (mags), and 58 for eeg.  Also, if I understand correctly, the rank of SSS'd MEG data should be estimate jointly for grads and mags?  So ... estimate_rank(evoked.pick_types(meg=True).data)?

Rread the source code of evoked.plot_white and find the answers :)
We have special private functions.

On 25 Apr 2015, at 13:24, "Andrew R. Dykstra" notifications@github.com wrote:
@dengemann, regarding rank, is estimate_rank from mne.utils sufficient? For the example data, it returns 67 (65) for grads (mags), and 58 for eeg. Also, if I understand correctly, the rank of SSS'd MEG data should be estimate jointly for grads and mags? So ... estimate_rank(evoked.pick_types(meg=True).data)?
—
Reply to this email directly or view it on GitHub.

authors: Eric89GXL adykstra agramfort dengemann teonlamont

repo: mne-tools/mne-python


text:
Mini-symposium at Scipy

There's a call for a minisymposium at Scipy on neuroscience in Python. I think it would be a good place to highlight the work from the Supervised Neural Time Series Sprint in NYC.
The call ends March 27th, which means we have less than three weeks if we wanted to do so. I will be around this summer to go and can take the lead on the submission if we decide to go for it. Thoughts?

I plan to go to scipy to give a sklearn tutorial with Andy so I can also
talk about MNE
@teonbrooks https://github.com/teonbrooks are you coming too?

cool cool. I would like to go. I will be right after my Mozilla fellowship ends so I need to find new support to go.

FYI I just submitted a proposal of talk on MNE-Python.

oh ok, cool. 👍

authors: agramfort teonbrooks


text:
DOC: Better Annotations docs

Added some cross-references and we're now using annotations_from_events in the tutorial – a function which I only came across accidentally, as it wasn't mentioned anywhere in the docs.

annotations are not showing up on the final plot in the tutorial. But that is not a result of this PR, it's probably a bug I introduced with the raw plotting overhaul. stable master & this PR.

@drammock

annotations are not showing up on the final plot in the tutorial. But that is not a result of this PR, it's probably a bug I introduced with the raw plotting overhaul.

Yep, already opened an issue here: #8421

authors: drammock hoechenberger


text:
UICapturedEffectImage does not work with 'ScreenSpace - Overlay' mode

Hello. I can't make it work with this UI mode. On enable canvas (or any child) with UICapturedEffectImage attached to it, an error appears:
[d3d11] attempting to ReadPixels outside of RenderTexture bounds! Reading (0, 0, 290, 452) from (736, 414)
Unity version is 2018.2.2f1

Hi @Scarabay
Thank you for reporting the bug!
I will check it later.

Well... on edit mode only?

authors: Scarabay mob-sakai

repo: mob-sakai/UIEffect


text:
fixed API response bug. Market prices are now displayed

Market <-- Ryan
Fixed Market Screen responseJSON bug

@ryanliszewski  I have merged the ryan branch into Market branch

repo: mobile-space/crypto-pos


text:
Add support for many languages to TitleExtensionToolbar

Hi @stephrdev ,
when using TitleExtensionToolbar in current implementation, if site has multiple languages Extension... will be duplicated for each existing page translation. This branch implements fix - for single language pages the behaviour is unchanged. For Multiple languages an Extension submenu is added.
LG,
Magda

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   97.77%   97.77%
=======================================
  Files           3        3
  Lines          90       90
  Branches       13       13
=======================================
  Hits           88       88
  Misses          1        1
  Partials        1        1

Continue to review full report at Codecov.

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

authors: codecov-io lenarother

repo: moccu/django-cms-helpers


text:
UnhandledPromiseRejectionWarning: Unhandled promise rejection

When I run tests on functions that returns a rejected promise, the test passes but an UnhandledPromiseRejectionWarning: Unhandled promise rejection is outputted to the console.
const chai = require('chai');
const expect = chai.expect;

function testFunc (opt) {
  if (opt === undefined) {
    return Promise.reject(new Error());
  }
}

describe('testFunc', function () {
  it('return with a promise', function () {
    expect(testFunc()).to.be.a('promise');
  })
  describe('return with a promise that', function () {
    it('is rejected when no parameters are passed to it', async function () {
      try {
        const result = await testFunc();
      } catch (e) { return; }
      return Promise.reject(new Error('Should have thrown'))
    })
  });
});

It produces the following output:
$ npx mocha

  testFunc
    ✓ return with a promise
(node:28519) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error
(node:28519) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    return with a promise that
      ✓ is rejected when no parameters are passed to it

  2 passing (29ms)

I have created a repository at to repreduce this issue.
I believe this will be fixed with #2640 and a similar issue was filed at #2797, but this repository provides an easy, minimalistic way to reproduce the issue.

I guess calling "reject" on the Promise class itself is not recommended anymore, but I'm not sure why.

@JimTheMan , if that's the case, then it would be nice to give an example on how to 'mock' a rejection, if that's the thing you need to test...
In most cases, having the error is good, because 99% of the time, it's because a return was forgotten, but in the example given (which I also have now encountered), the .reject needs to be called in order to test how rejection is being handled by your code.

Why was this closed? I get this issue in the latest version of mocha 5.2.0

Maybe it will help somebody, I had the same issue, but because of my own subtle bug:
In a test I forgot to await an async function call, which was throwing an exception. The test wasn't failing, but it was printing this awkward warning.

@JimLynchCodes Can you tell us why this was closed, please?

authors: CodeSandwich JimTheMan d4nyll dietergeerts hovissimo jwickens

repo: mochajs/mocha


text:
sklearn interface get_params/set_params not supported

Every sklearn estimator provides the get_params(deep=True) and set_params(params) methods. These are used e.g. when cloning an estimator. The parameters of an estimator are the arguments of its __init__ method and, as of sklearn's convention, these are all set as class attributes (see BaseEstimator._get_param_names()). When an argument of __init__ is not set as a class attribute, as is the case with ActiveLearner.bootstrap_init, BaseEstimator.get_params() prints a warning. As of version 0.24 of sklearn, an error will be thrown.
This is a minimalistic code snippet which should reproduce the issue.
from modAL.models import ActiveLearner
from modAL.uncertainty import uncertainty_sampling
from sklearn.ensemble import RandomForestClassifier

learner = ActiveLearner(
    estimator=RandomForestClassifier(),
    query_strategy=uncertainty_sampling
)
learner.set_params(learner.get_params(deep=True))

A simple solution would be to save all arguments of the __init__ method as class attributes.

Thanks for the report, I am investigating this!

authors: BoyanH cosmic-cortex

repo: modAL-python/modAL


text:
Add ability to save and restore port positions

When resizing a block in an IBD diagram the location of the associated ports are changed, requiring manual work to fix them.
As I used I would like to be able to resize the block so that at the end of the operation the ports remain at their original place.

A way to solve this problem could be the following:

Add a button to store the location of the ports
Do the resize
Press a button to restore the locations

This is also true for BDD diagrams:

Done in 1.1

repo: modeldriven-hu/astah-easy-diagram


text:
Mapping of Arrays stopped working in Groovy

Similar to issue https://github.com/jhalterman/modelmapper/issues/115, I have been having trouble using modelmapper 0.7.3 and groovy. Here is the test I ran against it, and it seems like skip is being ignored and mapping of arrays is happening.
https://github.com/plbarrios/modelmapper-tests/blob/master/ModelMapperTest.groovy

I think it should be fixed by #131, I'm not sure. Can you post your stacktrace? Thanks.

repo: modelmapper/modelmapper


text:
可以支持一下InternLM2-Math-Plus-Mixtral8x22B的微调吗

这个模型效果非常不错,数学上面接近gpt4o了

@tastelikefeet 大佬计划什么支持呀

@tastelikefeet 大佬计划什么时候支持呀

repo: modelscope/swift


text:
🛑 Dozzle is down

In f770a5b, Dozzle ($DOZZLE_URL) was down:

HTTP code: 521
Response time: 206 ms

Resolved: Dozzle is back up in d3e432d.


text:
🛑 NZBHydra2 is down

In 221675e, NZBHydra2 ($HYDRA_URL) was down:

HTTP code: 523
Response time: 960 ms

Resolved: NZBHydra2 is back up in eaac5db.


text:
WIP - Use proc_open to process realtime

Not sure if this is a better approach, it's more food for thought, really.

While this may be a WIP, it does function and it does improve my PR. I'm merging it into mine. :dancers:

authors: borkweb lucatume

repo: moderntribe/tric


text:
Tickable priority binding missing?

The documented means of binding ITickable priority seems to be missing from DIContainer. As far as I can tell, I couldn't find any different way to do so.

You mean this?
Container.BindTickableExecutionOrder<Foo>(10);
This seems to work when I try it

That method does not show up for me in intellisense, nor does it show up in the DIContainer class, or any method with the word "Order" in its name. The version I have is 5.2.0.

Oh I bet it's because those methods are extension methods, which means you have to execute "using Zenject" at the top of your file to see them.  I'm guessing you refer to zenject classes using their namespace (eg. Zenject.MonoInstaller)?
I think we should make these normal methods to avoid this problem

Ah, not having the namespace was indeed the issue, tho not for the reason you theorized. I was trying to bind in a class that extends a class that extends MonoInstaller
example...
using Zenject;

public class BaseInstallerClass : MonoInstaller
{

}
----------------------- Separate File ------------------
public class SubInstallerClass : BaseInstallerClass
{
    public override InstallBindings()
    {
        // The priority binding methods do not show up
    }
}

repo: modesttree/Zenject


text:
Extend SimpleDefinitionVerifier with basic functionality

It should not be possible to have duplicate AttributeRules with the same name or AssociationRules with the same targetName.
In those cases, the verify method must return false.

realted to #28

repo: modicio/modicio