text:
Remote API Handler : result data array or object ?

Hi, thanks for your work.
Disclaimer : This is probably a noob question because I'm quite new to angular, just a few days :)
I try to use to remote api handler on this angucomplete element :
 <angucomplete-alt id="product"
                          placeholder="Product name ?"
                          pause="400"
                          selected-object="product"
                          remote-api-handler="search"
                          remote-url-data-field="results"
                          title-field="title"
                          input-class="form-control form-control-small"/>

I use Laravel 5.1 as backend and my API is a result from elasticsearch.
angular.module('ProductController', []).controller('ProductController', ['$scope', '$location', '$routeParams', 'Product',
  function ($scope, $location, $routeParams, Product) {

  [ ...]

    $scope.search = function(userInputString) {
      var product = new Product({
        title: userInputString
      });
      return product.$search(function (res) {
      }, function (err) {
        console.log(err);
      });
    }
  }
]);

My service is :
angular.module('ProductService', []).factory('Product', ['$resource',
  function ($resource) {
    return $resource('/api/v1/product/:productSlug', {
      productSlug: '@slug'
    }, {
      update: {
        method: 'PUT'
      },
      search: {
        method: 'POST',
        url: '/api/v1/product/search'
      },
    });
  }
]);

Routes and controller on Laravel are OK.
Input : "bar"
When writing "bar" in the input field, results from my api (POST:/api/v1/product/search) are :
[{"id":25,"title":"Daugherty, Barrows and Stokes","slug":"velit-doloribus-veritatis-laborum-corrupti-natus-enim-sit","created_at":"2015-07-10 14:12:19","updated_at":"2015-07-10 14:12:19"},{"id":36,"title":"Greenholt, Bartoletti and Cummerata","slug":"mollitia-animi-cupiditate-ut-ut-modi-est-dolores-repellat","created_at":"2015-07-10 14:12:19","updated_at":"2015-07-10 14:12:19"}]

(DB populated with faker data)
I can't achieve to make angucomplete field to work, I'm getting this error :
Error: [$resource:badcfg] Error in resource configuration for action `search`. Expected response to contain an object but got an array (Request: POST /api/v1/product/search)

And if I put in my ProductService.js / search :
search: {
        method: 'POST',
        isArray: true,
        url: '/api/v1/product/search'
      },

I have this error :
TypeError: value.push is not a function

In both cases il also raises this error :
http error

I'm sure I mess with something linked to object/array conversion or remote-url-data-field="results" but I can't find what :)
Maybe someone here can help me.
Thanks.

Remote API needs to return an object.
Open up your browser's dev console and have a look at this github example:
http://ghiden.github.io/angucomplete-alt/#example5

Thanks for your time and answer.
So I build an array and return it as a json object as required by angucomplete :
{"total":2,"results":[{"id":25,"title":"Daugherty, Barrows and Stokes","slug":"velit-doloribus-veritatis-laborum-corrupti-natus-enim-sit","created_at":"2015-07-10 14:12:19","updated_at":"2015-07-10 14:12:19"},{"id":36,"title":"Greenholt, Bartoletti and Cummerata","slug":"mollitia-animi-cupiditate-ut-ut-modi-est-dolores-repellat","created_at":"2015-07-10 14:12:19","updated_at":"2015-07-10 14:12:19"}]}

No (visible) difference with Json returned by your example 5. It seems to be ok, it stops complaining about response not being an object.
But I still have a JS error :
TypeError: Cannot read property 'results' of undefined
    at extractValue (angucomplete-alt.js:224)

Any idea ?
Note : remote-url-data-field="results"

Your $scope.search is callback-based. Try changing it to promise-based.
https://docs.angularjs.org/api/ngResource/service/$resource

Ok, 3 hours digging later, I learn something new : promises :)
But I can't achieve to write it correctly using my service and my controller.
Could you help me with this ?
This actually is my ProductService.js
angular.module('ProductService', []).factory('Product', ['$resource',
  function ($resource) {
    return $resource('/api/v1/product/:productSlug', {
      productSlug: '@slug'
    }, {
      update: {
        method: 'PUT'
      },
      search: function(userInputString, timeoutPromise) {
	return $http.post('/api/v1/product/search', {q: userInputString}, {timeout: timeoutPromise});
      }
    });
  }
]);

This is the ProductController.js
angular.module('ProductController', []).controller('ProductController', ['$scope', '$location', '$routeParams', 'Product',
  function ($scope, $location, $routeParams, Product) {
   [...]
    $scope.search = function(userInputString) {
      var promise = Product.search(userInputString, 400);
      return promise;
    };
  }
]);

And this is not working, it seems that my 'promise' is not really a 'promise'...
TypeError: scope.remoteApiHandler(...).then is not a function
    at getRemoteResultsWithCustomHandler (angucomplete-alt.js:493)

Note :  that is working if I don't use the service part and write directly in my controller :
angular.module('ProductController', []).controller('ProductController', ['$scope', '$location', '$routeParams', 'Product', '$http',
  function ($scope, $location, $routeParams, Product, $http) {

    $scope.search = function(userInputString) {
      return $http.post('/api/v1/product/search', {q: userInputString}, {timeout: 400});
    };

  }
]);

Product.search(null, {name: 'test'}, {timeout: timeout}).$promise
Just go back to your original Product factory implementation.
And, in your controller, try this:
$scope.search = function(userInputString, timeoutPromise) {
  return Product.search(null, {q: userInputString}, {timeout: timeoutPromise}).$promise;
};

Thanks for your time ghiden.
It's more clean this way, the request is ok but I still have an error.
TypeError: (success || noop) is not a function
    at angular-resource.js:628
    at processQueue (angular.js:14569)
    at angular.js:14585
    at Scope.$get.Scope.$eval (angular.js:15848)
    at Scope.$get.Scope.$digest (angular.js:15659)
    at Scope.$get.Scope.$apply (angular.js:15953)
    at done (angular.js:10366)
    at completeRequest (angular.js:10538)
    at XMLHttpRequest.requestLoaded (angular.js:10479)

http error
  httpErrorCallback @ angucomplete-alt.js:457
  processQueue @ angular.js:14569
  (anonymous function) @ angular.js:14585
   $get.Scope.$eval @ angular.js:15848
   $get.Scope.$digest @ angular.js:15659
   $get.Scope.$apply @ angular.js:15953
   done @ angular.js:10366
   completeRequest @ angular.js:10538
   requestLoaded @ angular.js:10479

ProductService.js
    search: {
        method: 'POST',
        url: '/api/v1/product/search'
      }

ProductController.js
   $scope.search = function(userInputString,timeoutPromise) {
      return Product.search(null, {q: userInputString}, {timeout: timeoutPromise}).$promise;
    };

The Json is returned OK, so the request seems ok, the problem is after.
NB : excuse my english, I'm french :)

I thought it would work.
I personally never user $resource as I had bad experience with $resource back in the days of angular 1.0.
Probably the result is different from what it gets returned from $http.

I logged both returned values :
In the first case (no resource, working) :
Promise {$$state: Object}
  $$state: Object
    pending: undefined
    processScheduled: false
    status: 1
    value: Object
      config: Object
      data: Object
      headers: function (name) {
        status: 200
        statusText: "OK"
     __proto__: Object
    __proto__: Object
  error: function (fn) {
  success: function (fn) {
  __proto__: Object

in the second case (not working) :
Promise {$$state: Object}
  $$state: Object
    pending: undefined
    processScheduled: false
    status: 1
    value: TypeError: (success || noop) is not a function
    __proto__: Object
 __proto__: Object

I'm closing this. If you need more help on this, please let me know.

This is still open. I can't get it working. Resource is an important part of Angular.

@evanjmg It should work now. There was a bug in my code but recently I fixed it.
Are you calling like this?
$scope.search = function(userInputString,timeoutPromise) {
      return Product.search(null, {q: userInputString}, {timeout: timeoutPromise}).$promise;
};

authors: evanjmg ghiden pierrerigal

repo: ghiden/angucomplete-alt


text:
Support major after options

In my projects i often use this npm script:
"publish": "npm run build && lerna publish --create-release=github --force-publish",

Now i sometimes want to force a major update and thus i am tempted to use npm run publish -- major
But it wont work. Running lerna publish --create-release=github --force-publish major ignore the major argument. While running lerna publish major --create-release=github --force-publish works.
Could it be possible for it to be independant of the order?

@ghiscoding ok i could create a PR for this. but thanks i did not know about the bump arg. it resolves my issue !

source: gharchive/issue

repo: ghiscoding/lerna-lite

license: MIT

license_type: permissive

license_source: github-api


text:
Error in not finding downloaded files

This package is amazing!
When running the example code, I got the following error:
Error in h(simpleError(msg, call)) :
  error in evaluating the argument 'x' in selecting a method for function 'crop': subscript out of bounds

When troubleshooting the bm_get_data function, I realized the following line of code wasn't finding any files:
 lista <- list.files(path = file.path(Sys.getenv("USERPROFILE"),
                                       "Desktop", fsep = "\\"), pattern = "VNP46A2", full.names = T)

Not sure if relevant, but I'm on a Mac -- happy to share any other details to help troubleshoot.
But I ended up changing this line
dl_func(link, paste0(file.path(Sys.getenv("USERPROFILE"),
                                    "Desktop", fsep = "\\"), "\\", paste0(file[j],
                                                                          ".nc4")), username, password)

to
dl_func(link, file.path("~/Desktop/tmp", paste0(file[j], ".nc4")), username, password)

And I changed
lista <- list.files(path = file.path(Sys.getenv("USERPROFILE"),
                                     "Desktop", fsep = "\\"), pattern = "VNP46A2", full.names = T)

to
lista <- list.files(path = "~/Desktop/tmp", pattern = ".h5.nc4", full.names = T)

I would do a pull request, but not sure if this is the most elegant solution / if it'll work in all cases (but at least gets things working for me).
Also note in the last line I changed pattern = "VNP46A2" to pattern = ".h5.nc4" -- wonder if that's needed in case someone wants VNP46A1 or VNP46A3?

Apologies for my very delayed answer. Thank you for spotting this, as I had no opportunity to test the package in a Mac environment. Could you please send a pull request so that I can integrate the bugfix? Many thanks.

authors: giacfalk ramarty

repo: giacfalk/blackmaRble


text:
Replace grunt-mocha-cov

This package is unmaintained so we should use something else.

I'd be willing to cut the grunt cruft and just roll a simple npm scripts solution. Thoughts?

Agreed. The tasks here are so simple we are better off with plain npm
scripts.
On Jul 10, 2017 15:15, "Ryan Zimmerman" notifications@github.com wrote:

I'd be willing to cut the grunt cruft and just roll a simple npm scripts
solution. Thoughts?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/giakki/uncss/issues/317#issuecomment-314088153, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVVtd37xAD4VQiAkv2tSs5d5aWWcNYIks5sMhXegaJpZM4OSNpn
.

I started working on a branch. I'll push it to this repo and make a PR so that you guys can review and contribute too.

authors: RyanZim XhmikosR

repo: giakki/uncss

license: mit

license_source: bigquery


text:
[ENHANCEMENT] GUI/How-to

It would be nice to have GUI or a how-to for some slightly less involved in the scene people to avoid spending lots of time figuring things out. Otherwise, thanks for your involvement! :-)

Hey!
A GUI isn't in the scope of this project specifically, as the goal is to provide an encoder for use either as a standalone binary (where it isn't very useful) or within other projects.
That being said, I maintain a GUI for Linux called Aviator! It is available as a Flatpak, and it uses SVT-AV1-PSY under the hood by default no matter what distro you're on. See more here (Flathub Link)
If you'd like more flexibility via the command line, check out rAV1ator CLI. If you are on Windows, there is a WSL installation tutorial on the wiki page. I pre-compiled binaries with rAV1ator CLI alongside an easy-to-use TUI for installing them, so after the initial setup you do not need to build SVT-AV1-PSY yourself.
Thanks for your interest, I hope one of these two tools works for you!

authors: LTGM gianni-rosato


text:
Support creating Clusters using an http proxy in cluster-cloud-director

Support creating clusters using HTTP_PROXY in cluster-cloud-director.
Please make sure that we are using the same interface (helm variables) as team hydra. See https://github.com/giantswarm/cluster-aws/pull/105
Tasks

[ ] Make sure that app platform still supports running behind a proxy so that we can get things bootstrapped.

PR to align proxy values with CAPA => https://github.com/giantswarm/cluster-cloud-director/pull/30
No change in functionality, we still use the native capvcd integration.
This only set environment variables on the nodes, not the workloads.

The HTTPS Proxy env variable is configured for containerd on the nodes and can pull images fine.
However there is a bug upstream that it doesn't pupolate the HTTP env variable. The maintainers will have it fixed quickly.

Closing this as it is done from a cluster chart perspective.

@vxav I think this story is already implemented? current proxy implementation by @bavarianbidi was tested on CAPVCD

The current implementation in cluster-cloud-director based on this PR in cluster-api-provider-cloud-director make it possible to create a cluster behind a proxy.
in upstream issue #299 we track the current process of our forked changes (as in one of the recent meetings with CAPVCD-maintainers we decided with them that the current build-in solution isn't very flexible)

authors: bavarianbidi cornelius-keller gawertm vxav

repo: giantswarm/roadmap


text:
cilium network policy

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Important: After this PR is tested and approved, ensure you "Squash and Merge" unless you are updating a subtree. The release automation in use on this repository relies on squashing, but git subtrees will be lost if squashed. This repo allows both, so you may need to change the merge type when merging.

Thanks for the help here, Nick. I'm going to close this one because starboard is deprecated and this is one more great reason folks should move to Trivy Operator :smile:

source: gharchive/pull-request

authors: njuettner stone-z

repo: giantswarm/starboard-app


text:
Fix #350 -- Show diagrams Animations as animated .gif images

I have added a module IHaskell.Display.Diagrams.Animation to ihaskell-diagrams which is re-exported by IHaskell.Display.Diagrams. This fixes #350.
A sample cell:

Gives output:

@gibiansky I am not sure how to fix the merge conflicts. I have commented on the commit that caused them here.

The output for that same snippet of code, after two new commits looks like this:

Looks good. In order to deal with merge issues, you should rebase your branch onto master. I just pushed a commit to fix the compilation issue (I think it arose from the 7.10 patch attempt)

Once it can merge I will go ahead and merge this, it looks good.

I accidentally made the opposite rebase :(
When I tried to revert it, I found that this PR was automatically closed.
I'll send another one with no merge conflicts.

And.. it seems like I lost all my code. :(

Oh no! See here for some details -- maybe it's recoverable? :(

I'll try and see what I can do.

I'm used to merging instead of rebasing. Didn't have any idea that they were so different.
I'll see what I can do. It might be easier to just re-write the whole thing.

It is possible that a merge would have been necessary here, since there were changes to the same files. In general a rebase is preferable as it avoids an extra merge commit, which gives you a clean history as well, and makes it seem like the commits all happened synchronously. Sorry for the confusion :(

The rewrite is complete. Hopefully, it won't be different from the previous one.
Also, the mistake was on my part. I had a misconception that git-rebase was just git-merge without any extra commits. Seems like it was too different from what I had in mind.
The data was still not lost. It was lost when I used --set-upstream on the diagrams-animation branch, which was not rebasing due to absence of an upstream. I might've been able to recover had the data not been lost there.
It's working again, and that's what matters. Thanks for the explanation. :+1:

authors: gibiansky sumitsahrawat

repo: gibiansky/IHaskell


text:
🛑 N L is down

In dc7e7a0, N L (https://gildlab-ipfs-1.eu.ngrok.io/api/v0/version) was down:

HTTP code: 404
Response time: 395 ms

Resolved: N L is back up in aa99b25.

repo: gildlab/upptime


text:
Error building luajit on aarch64

Build fails on aarch64 because luajit version included does not support aarch64. Able to build LuaJIT 2.1.0-beta3 on the same machine
$ make
==== Building LuaJIT 2.0.5 ====
.
.
lj_arch.h:55:2: error: #error "No support for this architecture (yet)"
 #error "No support for this architecture (yet)"
  ^~~~~
lj_arch.h:294:2: error: #error "No target architecture defined"
 #error "No target architecture defined"
  ^~~~~
.
.
.
Makefile:109: recipe for target 'default' failed
make: *** [default] Error 2

Wrk2 seems to be using luajit-2.0.3.
We've upgraded our wrk2 fork to luajit-2.1.0-beta3 a while ago; maybe the commit can be cherry-picked to upstream?
Please note that the commit referenced also enables luajit's 64bit garbage collector by default. 64bit address space support (which allows LUA scripts to handle significantly more data) was our main reason for upgrading.

with this patch, I still got error
src/hdr_histogram.c:10:23: fatal error: x86intrin.h: No such file or directory

with this patch, I still got error
src/hdr_histogram.c:10:23: fatal error: x86intrin.h: No such file or directory

@gaozhangfei @t-lo
I ran into this same issue and was able to get wrk2 to build and run on my aarch64 system. There were two additional code changes I had to make. Here's how I tied it together on a bare-metal aarch64 system:

I clone the Kinvolk wrk2 fork with compatible LuaJIT version, here.
The hdr_histogram.c file imports x86 intrinsics, which aren't available on aarch64. It simply needed to be ifdef'd out (see below).
I don't fully understand this one because I'm far from a C programmer, but there was an issue with how the command line was being parsed and the variable declaration for "c" needed to be changed to a signed char. I found this fix referenced here.

With these changes I'm able to successfully build wrk2 natively on aarch64.
My change to hdr_histogram.c:
from
#include <x86intrin.h>

to
#ifdef __x86_64__
#include <x86intrin.h>
#endif

My change to src/wrk.c line 746:
from
char c, **header = headers;

to
signed char c, **header = headers;

As a follow on, I created this fork that's cloneable and immediately buildable on aarch64: https://github.com/AmpereTravis/wrk2-aarch64

As a follow on, I created this fork that's cloneable and immediately buildable on aarch64: https://github.com/AmpereTravis/wrk2-aarch64

Thanks AmpereTravis,
I can build on aarch64 with fix 9e5f897 isrc/hdr_histogram.c, docker/prometheus: fix / add ARM64 support
But app still can not run
With the fix: bf8133e Update parse_args to use explicitly signed char to avoid argparse bugs.
The app can run on aarch64
Thanks

I can't get neither this fork to compile nor the one from Kinvolk.
Not a C expert, would gladly take how to. got gcc ,make, openssl install via brew.

Duplicating work appears to be game in wrk2 town, so to add to the pile, here's a comment for the issue I found on a popular search engine when trying to build wrk2 on M1. Oh btw, it links 2 PRs to fix this. I've verified one of them. Good luck all!

As a follow on, I created this fork that's cloneable and immediately buildable on aarch64: https://github.com/AmpereTravis/wrk2-aarch64

👆 fails to build on latest darwin/aarch64, so if you're on that combo see my comment above:
In file included from src/wrk.c:3:
src/wrk.h:11:10: fatal error: 'openssl/ssl.h' file not found
#include <openssl/ssl.h>
         ^~~~~~~~~~~~~~~
1 error generated.
make: *** [obj/wrk.o] Error 1

authors: AmpereTravis galderz gaozhangfei orefalo prasun3 t-lo


text:
First Time Running Problem, After First Signup

I installed project on server, I migrated db on sql lite
I started on server and i created new user, after signup operation,
I had this error,
NoMethodError in Home#index
Showing /usr/lib/ruby/gems/1.8/gems/social_stream-0.0.5/app/views/home/_groups.html.erb where line #1 raised:
undefined method `where' for []:Array
ActionView::Template::Error (undefined method `where' for []:Array):
<% if current_user.recent_groups.any? %>

   <%=t('group.other') %>

Hi, omeryavuz. It seems you are running social_stream version 0.0.5
Current social stream version is 0.12.3
Please, run bundle update

authors: atd omeryavuz


text:
PyPI version 1.0.2 appears to be missing 'hotpie.py'

Hey, your library is awesome and I'd love to use the latest version; but installing it from PyPI with pip results in the hotpie.py file not being installed. I've just quickly checked the source distribution URL listed during the install and it is definitely missing the hotpie.py file.

Thanks for spotting this @leesdolphin. I'm not terribly familiar with the whole setup.py / pypi shenanigans, so I must have missed something when "borrowing" setup.py from another package. I'll see if I can figure out how to make it pick up the hotpie.py file.

@leesdolphin I updated pypi to 1.0.5 and hopefully now things should work again. Can you give it a try?

Thank you so much; it's working beautifully.

authors: gingerlime leesdolphin

repo: gingerlime/hotpie


text:
🛑 API endpoint is down

In dc5190a, API endpoint (https://api.checklyhq.com/v1/check-statuses/$CHECKLY_ENDPOINT_FORUM_URL) was down:

HTTP code: 200
Response time: 312 ms

Resolved: API endpoint is back up in 7afa0e3.

repo: ginsul/up


text:
Hibernate Queries and Annotations

Description
Hibernate Annotations and Queries
Session and Session Factory
Hibernate Annotations
Hibernate Queries for Crud Operations
Domain
Backend Dev (Java)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign

repo: girlscript/winter-of-contributing


text:
DFS Traversal of graph

Description 📜
In my documentation, I have explained what is graph, DFS traversal in brief. I have also added the CPP code of DFS traversal and explained it. All the images added in the documentation are created by me.
Fixes #1518

Type of change 📝

[X] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[X] C/CPP

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@cookieg13 amazing work !!
Add a relative link to the readme file in the Graph folder . Here is how you add a
[relative link] (https://stackoverflow.com/questions/7653483/github-relative-link-in-markdown-file)

Hi! @ChetasShree and @Suvraneel Thank you so much for reviewing! ❤  I have updated the readme file.


text:
[Bitwarden] Abstract away DB-WAL setting

DB_WAL is either true for sqlite or false for actual databases.
We can easily abstract this away (certainly when custom env's get supported)

DB_WAL is automatically disabled on other DBs and defaults to true for SQLite. The user does have the option to disable it if he wants to. I don't think there is more abstraction needed, what do you suggest?

@sgissi I understood it wrong:
Enable DB Write-Ahead-Log for SQLite, disabled for other databases
maybe make it:
Enable DB Write-Ahead-Log for SQLite, automatically disabled for other databases

repo: gissilabs/charts


text:
[BUG] 新打开标签页的添加可能失败

在打开一个新标签页的时候，可能无法给 Diagram 添加「pop up」特性：
详见视频（在沙盒仓库中测试）：
https://github.com/user-attachments/assets/753a53da-73a0-4abb-9d8c-0e7e20bdc21c

另一种情况是，如果编辑了 mermaid 代码块，重新渲染的时候，也无法添加特性：

插件版本是 0.2.60
Obsidian 版本是 1.7.6

我稍后看看，谢谢反馈
------------------ 原始邮件 ------------------
发件人:                                                                                "gitcpy/obsidian-diagram-popup"                                                                                @.>;
发送时间: 2024年11月15日(星期五) 下午3:19
@.>;
@.***>;
主题: [gitcpy/obsidian-diagram-popup] [BUG] 新打开标签页的添加可能失败 (Issue #10)
在打开一个新标签页的时候，可能无法给 Diagram 添加「pop up」特性：
详见视频（在沙盒仓库中测试）：
https://github.com/user-attachments/assets/753a53da-73a0-4abb-9d8c-0e7e20bdc21c
另一种情况是，如果编辑了 mermaid 代码块，重新渲染的时候，也无法添加特性：
17c8480d-da0b-4432-8e5c-bbcb5dc89c42.gif (view on web)
插件版本是 0.2.60
Obsidian 版本是 1.7.6
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

我查看了一下，确实存在你说的两种情况
但是我无法确认原因，具体是

ctrl+左键 新标签打开md文档，情况比较诡异，有概率无法添加弹窗按钮；
但是在左边文件浏览器右键菜单 新标签打开md文档都能添加弹窗按钮，没发现方法无法添加
进入编辑状态，这个也诡异，之前我测试的是编辑后预览都能正常，也不知道产生的原因，
这个刚好概率相反，有一定概率正常添加如下视频所示：

https://github.com/user-attachments/assets/059495ee-77c6-4c61-8fbd-2980826c24a7
目前的解决办法是，你遇到这个情况，要么重开文档，要么就在 编辑模式 和 阅读模式 切换看看， 一般都会重新添加上

晕，又看了好几遍你的gif图。。。原来你在 dataview 里面用。。。。下次记得描述清楚，录清楚点。。。不然，还以为只是mermaid的问题，还好我仔细看，不过我这边错也错的刚好，看到 ob的 mermaid 本身有问题

我特地又尝试了下 dataview 下的 gantt 的 插件使用，我这边是正常的。。。
https://github.com/user-attachments/assets/ded603e5-8529-45d7-9897-d7cfae93010a

这个 obsidian 的 编辑模式 的 代码块 渲染预览，没有相关的事件，很难处理，官方也没有开源，能找到的 MarkdownPostProcessor 和 MarkdownCodeblockProcessor 也是语焉不详，经过测试是关于编辑后切换到阅读模式的事件，所以正常情况下，确实进入编辑状态退出后预览是没有的，并且也没有事件可以做处理，所以基本都是本人 靠ai和 自行测试 写的插件。。。非常无奈，最后用了一个不优雅的方法，observer监听。。。

更新到 0.2.62， 修复了 新开文档按钮可能丢失的bug，然后 编辑状态跟随这次更新没重现，你试试，有问题再留言

总的来说，这两个bug，更多的原因我推测是 obsidian 内部机制引起，你多试试。

晕，又看了好几遍你的gif图。。。原来你在 dataview 里面用。。。。下次记得描述清楚，录清楚点，那个gif太快了，我特地录屏，慢放暂停看的。。。不然，还以为只是mermaid的问题，还好我仔细看，不过我这边错也错的刚好，看到 ob的 mermaid 本身有问题

啊，抱歉抱歉……
确实比较快，为了减少 gif 的体积所以压缩了时长，不然超过大小限制会无法上传
下次还有的话我就直接传视频吧~

总的来说，这两个bug，更多的原因我推测是 obsidian 内部机制引起，你多试试。

比较奇怪的就是我之前用这个插件的时候，确实是没问题的
所以怀疑是不是 OB 更新了之后修改了一些机制，导致原来可行的方案现在失效了
（官方明确说了的是一个 Defer 机制，会延迟后台页面的加载）
我先更新试试看！

我的神，难怪了，你那里看到的，我去了解一下，谢谢交流！
------------------ 原始邮件 ------------------
发件人:                                                                                "gitcpy/obsidian-diagram-popup"                                                                                @.>;
发送时间: 2024年11月16日(星期六) 晚上11:00
@.>;
@.@.>;
主题: Re: [gitcpy/obsidian-diagram-popup] [BUG] 新打开标签页的添加可能失败 (Issue #10)
总的来说，这两个bug，更多的原因我推测是 obsidian 内部机制引起，你多试试。
比较奇怪的就是我之前用这个插件的时候，确实是没问题的
所以怀疑是不是 OB 更新了之后修改了一些机制，导致原来可行的方案现在失效了
（官方明确说了的是一个 Defer 机制，会延迟后台页面的加载）
我先更新试试看！
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

我的神，难怪了，你那里看到的，我去了解一下，谢谢交流！
…
------------------ 原始邮件 ------------------ 发件人: "gitcpy/obsidian-diagram-popup" @.>; 发送时间: 2024年11月16日(星期六) 晚上11:00 @.>; @.@.>; 主题: Re: [gitcpy/obsidian-diagram-popup] [BUG] 新打开标签页的添加可能失败 (Issue #10) 总的来说，这两个bug，更多的原因我推测是 obsidian 内部机制引起，你多试试。 比较奇怪的就是我之前用这个插件的时候，确实是没问题的 所以怀疑是不是 OB 更新了之后修改了一些机制，导致原来可行的方案现在失效了 （官方明确说了的是一个 Defer 机制，会延迟后台页面的加载） 我先更新试试看！ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

啊，我找给你，稍等——
说明文档在这里：
https://docs.obsidian.md/Plugins/Guides/Understanding+deferred+views

1.7 版本更新的时候添加的，如图：

@Moyf 感谢，请问我们在一个qq群:427063403 吗？

@Moyf 感谢，请问我们在一个qq群:427063403 吗？

乐，不在~ 我可以加一下

authors: Moyf gitcpy

repo: gitcpy/obsidian-diagram-popup


text:
🛑 inv.riverside.rocks is down

In 65225f7, inv.riverside.rocks (https://inv.riverside.rocks/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: inv.riverside.rocks is back up in f4c527d.

repo: gitetsu/invidious-instances-upptime


text:
🛑 inv.riverside.rocks is down

In 89a78aa, inv.riverside.rocks (https://inv.riverside.rocks/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: inv.riverside.rocks is back up in 3378f93.


text:
🛑 whoogle.lunar.icu is down

In abd2414, whoogle.lunar.icu (https://whoogle.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.lunar.icu is back up in ce34e6f after 13 minutes.

repo: gitetsu/whoogle-instances-upptime


text:
🛑 whoogle.lunar.icu is down

In e2845c4, whoogle.lunar.icu (https://whoogle.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.lunar.icu is back up in 7fae7fc after 5 minutes.


text:
Lint commits more

We already have patch count linting via #178 (which was just merged). With this PR, we also refuse to send patch series where the original PR contains merge commits, and we now also disallow bogus "...@users.noreply.github.com" email addresses.

I have not reviewed it all yet but had an alternate implementation at https://github.com/webstech/gitgitgadget/commit/611d4aa98f222d762c180de97bbabd9f64bebca6.  This uses the github api and is all set to start linting the commit messages.
It also attempts to set the missing email address if possible based on comments you made in the issue.  Obviously this can be moved to a separate commit.

I have not reviewed it all yet but had an alternate implementation at webstech@611d4aa. This uses the github api and is all set to start linting the commit messages.

Okay. Let's wait with the fetching approach for now, then.
Did you plan on opening a PR for this soon?

I have not reviewed it all yet but had an alternate implementation at webstech@611d4aa. This uses the github api and is all set to start linting the commit messages.

Okay. Let's wait with the fetching approach for now, then.

I actually "rebased" my patches on top of yours, adjusting to your approach of using the GitHub API to obtain already-parsed commits.

I had to rebase on top of master because the changes from #183 conflicted with your commit, @webstech.

addressParser is probably overkill for this.

For now, yes. If we ever encounter other fake email addresses that we need to suppress, then we should probably start looking into addressParser ;-)

@dscho Thanks for using the github api code.  It had been festering on my machine for awhile.

authors: dscho webstech

repo: gitgitgadget/gitgitgadget

license: ISC


text:
🛑 DynDNS afraid is down

In f07e5a8, DynDNS afraid (https://freedns.afraid.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DynDNS afraid is back up in ff9c1c0 after 11 minutes.

repo: gitgrub/uptest


text:
mui icon 도입에 대한 논의

안녕하세요.
MUI를 설치함에 따라 #609 기존 svg로 사용되었던 아이콘들도 유지 보수성 향상을 위해 mui-icons로 교체하고자 하였습니다.
그런데 githru 내 아이콘은 5개보다 많은 데도 불구하고 svg가 5개밖에 보이지 않는 점이 이상해서 더 찾아보니, 일부 아이콘은 이미 react icons를 설치하여 사용하고 있었습니다.

// src/components/VerticalClusterList > Summary > Content > Content.tsx
import { IoIosArrowDropdownCircle, IoIosArrowDropupCircle } from "react-icons/io";

그래서 react-icons 에 대해 더 찾아보고 장단점을 분석해보았습니다.
패키지 크기

React Icons은 다양한 아이콘 세트를 포함하고 있기 때문에, 패키지의 크기가 상대적으로 큽니다. 우선 설치할 땐 모든 아이콘이 설치되고, tree shaking을 통해 빌드할 땐 사용한 아이콘만 포함됩니다.
Material UI는 상대적으로 사이즈가 작으며, Google Fonts를 통해 CSS 기반으로 아이콘을 사용할 수 있습니다.

렌더링 시 성능

React Icons은 SVG 아이콘을 사용하므로, 렌더링 성능은 보통 우수합니다. 컴포넌트이므로 최적화가 가능합니다.
Material UI는, CSS와 웹폰트를 사용하여 스타일시트에서 직접 렌더링하기 때문에 약간 더 좋습니다.

정리
react-icons 는 초기 설치 시 크기가 상대적으로 무겁습니다. 두 라이브러리 모두 렌더링 성능이 좋지만 material-ui가 조금 더 좋습니다. 이렇게 말하면 react-icons가 상대적으로 비효율적인 것 같지만, react-icons 는 많은 종류의, 아름다운 아이콘을 제공하고 있어 선택지가 넓은 편입니다. Hero, radix 등 깔끔하고 현대적인 아이콘들이 많아 이점이 있습니다.

기존에 UI 프레임워크 자체는 MUI로 하기로 #596 에서 의견을 나누고 #607 에서 결정했는데, MUI도 아이콘의 경우 따로 패키지를 다운 받아야 하기 때문에, 이미 사용하고 있는 icon 라이브러리가 있는 경우도 전면 교체로 결정된 것인지 헷갈려 이슈 올립니다.
우선 어떤 것을 사용하던 간에 svg (아이콘만)은 교체할 것 같습니다. 다만 mui icon과 react-icon을 둘 다 사용하는 것은 비효율적이고, 이미 react-icons에서 mui 아이콘도 지원하기 때문에..

아이콘만이라도 더 아름다운 것을 사용함 (유지보수 가능. 러닝커브 낮음)
MUI 컴포넌트들과 디자인 시스템을 통일함

두 가지 방향 중 하나 골라 의견 남겨주시면 감사하겠습니다. 어느 정도 의견 취합 후 업데이트하여 pr 올리겠습니다~!
+) 어떤 라이브러리를 사용하든 지금보단 조금 더 (선 끝 모양) 동글동글하고 깔끔하게 선택하려고 합니다! 그게 githru라는 이름과 로고의 느낌과도 더 알맞는것 같아서요!

제 개인적인 의견으로는 mui icons로 통일하는 게 낫지 않을까 싶습니다 !
말씀하신대로 mui-ui를 사용하기 떄문에 디자인 통일성을 유지할 수 있고, 사용하기 쉽다는 점도 이점이 되겠지만,
프로젝트에서 사용되는 아이콘의 양이 많지 않기 때문에 mui icons로도 충분할 것 같다는 생각이 듭니다.
react icons의 가장 큰 장점은 다양한 아이콘을 하나의 라이브러리로 사용할 수 있다는 것으로 보이는데, 아이콘의 중요성이 그렇게 크지 않은 저희 프로젝트에서는 다소 오버스펙이 ㅎㅎ 아닐까 싶기도 합니다 !!

저도 일단은 아이콘 양이 그렇게 많이 필요하다고 생각하지 않아서, mui icons로도 충분하지 않을까 싶습니다!

오 성능까지 비교를!!! 멋집니다 👍👍👍👍👍👍👍👍

@taboowiths @xxxjinn 의견 감사합니다! 저도 MUI가 더 맞는 것 같습니다 ㅎㅎ 그러머 기존 svg 포함해서 REACT-ICONS의 아이콘들도 수정해서 올리도록 하겠습니다!

해결 완료!

authors: pcwadarong taboowiths xxxjinn ytaek

repo: githru/githru-vscode-ext


text:
[GHSA-592j-995h-p23j] RDoc RCE vulnerability with .rdoc_options

Updates

Affected products

Comments
The CVE number reported seems not to exist....

Hi @AndrzejBiernacki2010 it appears the CVE has been reserved but not yet published.

repo: github/advisory-database


text:
Suggested: update to GitHub's markdown support for Basic writing and formatting syntax section

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Web link: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
What part(s) of the article would you like to see updated?
Reason and outcome: This update will allow GitHub community to use more features supported by GitHub platform which aren't currently mentioned on the docs, this new addition will help the members working on mathematical and scientific fields on GitHub to use appropriate markup to represent relevant scientific and mathematical notations improving there repository more readable to the subject experts/audience.
e.g. The equation chemical notation of water could be interpreted as H2O by writing as H2O
Page section: Styling text
Additional information
Page after suggested update:

@LRANUL
Thanks so much for opening an issue! I'll triage this for the team to review :eyes:

@ramyaparimi This issue got closed, with the removal of the forked repository on my profile, shall I reopen this issue another pull request for the same ?

@LRANUL I will go ahead and reopen this issue. Please create a PR for the issue at your convenience 💛 .
Thank you so much for your passion in improving GitHub docs 💖 .

@LRANUL @ramyaparimi this certainly does look like a bug. I've opened an internal engineering issue to look into the problem. I apologize for the inconvenience.

authors: LRANUL rachmari ramyaparimi

repo: github/docs


text:
duplicate of #124?

          duplicate of #124?

Originally posted by @muzimuzhi in https://github.com/github/vscode-github-actions/issues/240#issuecomment-1663041862

          duplicate of #124?

Originally posted by @muzimuzhi in github/vscode-github-actions#240 (comment)


text:
$RUNNER_OS/etc environment variables not documented (GitHub Actions)

What article on docs.github.com is affected?
https://docs.github.com/en/actions/reference/environment-variables#default-environment-variables

What part(s) of the article would you like to see updated?

This StackOverflow answer claims that GitHub Actions workflow steps are provided with an environment variable $RUNNER_OS that contains the value of ${{ runner.os }}.
This is confirmed by a simple workflow that just prints out env | sort:
…
RUNNER_OS=Linux
RUNNER_PERFLOG=/home/runner/perflog
RUNNER_TEMP=/home/runner/work/_temp
RUNNER_TOOL_CACHE=/opt/hostedtoolcache
RUNNER_TRACKING_ID=github_069548eb-c4f3-4542-baac-43ed0d140801
RUNNER_USER=runner
RUNNER_WORKSPACE=/home/runner/work/pysam
…

It also appears to be confirmed by the runner source code; see https://github.com/actions/runner/blob/419ed24c1ee8c70eeb096570980e700e833f81f6/src/Runner.Worker/RunnerContext.cs#L13
The affected web page lists environment variables available to workflow steps, including $CI and many variables of the form $GITHUB_xyz. If (some of) these $RUNNER_xyz environment variables are also supported for use by workflow steps, it would be useful if they were added to this listing.
Additional information

This is somewhat related to the previously-reported #2031, but that issue was interpreted as being about the context expression ${{ runner.os }} rather than the environment variable $RUNNER_OS.

Hi there! Thanks for pointing this out. We should add that environment variable to https://docs.github.com/en/actions/reference/environment-variables#default-environment-variables as you suggest. You or anyone else is welcome to open a PR doing so! ⚡

Only GitHub staff are in a position to confirm which of the seven RUNNER_* environment variables observed are supported for use in workflows.
Note that only three of the corresponding runner context properties are documented.

On Thu, May 13, 2021 at 1:10 PM John Marshall @.***>
wrote:

What does this mean? Or what should I do?

Only GitHub staff are in a position to confirm which of the seven RUNNER_*

environment variables observed are supported for use in workflows.
Note that only three of the corresponding runner context properties
https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#runner-context
are documented.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/6127#issuecomment-840804200, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASFMGJA7VWZALXREF3IZMULTNQW3XANCNFSM44KSEGGQ
.

@jmarshall That's a good call! Could you check with our wonderful support team about whether or not that variable should be documented? If it is, you can either comment here and we'll reopen this issue or open a new issue 💖
Thanks so much for helping to improve the GitHub docs!

@janiceilene: I don't understand why you've closed this. @lecoursen agreed that changes are warranted (but didn't clarify which particular variables are supported). No additions have been made to environment-variables.md so the issue remains unresolved.

@jmarshall Sorry about the confusion! I closed this issue because it isn't something the team can take action on right now. If you want to check in with our support team to find out with variables are supported, you can come back and let us know! At that point we can either re open this issue or you can open a new one 💛

Reopening based on discussion in PR https://github.com/github/docs/pull/6740

Changes are now live:

Published article
Changes

“Default environment variables”
Adds entries to table for RUNNER_OS, RUNNER_TEMP, and RUNNER_TOOL_CACHE

"Context and expression syntax for GitHub Actions"
Moved descriptions into reusables for consistency.


text:
Describe how to re-request a review

What article on docs.github.com is affected?

I think we should update one of the subsections belonging to this main section:
https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests
What part(s) of the article would you like to see updated?

Why should the docs be changed?
I can't find anything in the GitHub docs about re-requesting a review??? I would expect it to be in one of the articles in the Reviewing changes in pull requests section, but I can't find it there at all.
What use cases does it support?
This should be documented somewhere, so that repository maintainers can link to this section to explain how "re-requesting an review" works.
This also exposes this functionality to anyone who reads the GitHub docs, that way they can "stumble into" this functionality.
Expected outcome
There is a section in the GitHub docs that explains that you can click on the refresh icon next to a review, to ping the reviewer for a fresh review.
Additional information

See the image below for an example of the refresh icon that I'm talking about:

👋 @HonkingGoose I don't see anything about re requesting a PR review either! It sounds to me like you're interested in an addition that focuses on a contributor requesting an additional review after they've made changes in an already reviewed PR. Is that right?
The article you linked to above ☝ Reviewing changes in pull requests is aimed at the reviewer, so I don't think that's quite the right place for this information to live.
What about adding it to either About pull request reviews? Or maybe Incorporating feedback in your pull request, since that article focuses on how to apply suggested changes and open an issue for out of scope suggestions?

First of all, thanks for the quick response! :smile:

It sounds to me like you're interested in an addition that focuses on a contributor requesting an additional review after they've made changes in an already reviewed PR. Is that right?

Yes, that's right! :smile:

The article you linked to above :point_up: Reviewing changes in pull requests is aimed at the reviewer, so I don't think that's quite the right place for this information to live.

Agree, it should go somewhere else.

What about adding it to either About pull request reviews?

Sounds good to me, I think I like this place better than " Incorporating feedback in your pull request", as that seems to me more focused on the review feedback. I can see the case for both places though.
I think some keywords should be: "refresh review", "ping for a fresh review", "re-request review", I think things like that are what people would be search for. I know I typed in "re-request review" and "request review" to try to find this documentation.

The hover text says "re-request review," so I think that's what we should use here. I think it'd be beneficial to add the information to both articles. So what we can do is create a new reusable in https://github.com/github/docs/tree/main/data/reusables/pull_requests that includes:

a sentence or two about why someone would want to re-request a review (like after making substantial changes)
a quick explanation of how to re-request a review, using the sync octicon

We can add a new section called "Re-requesting reviews" to the About pull request reviews article after the "Resolving conversations" section with that reusable. We can also add a new section and reusable to Incorporating feedback in your pull request after the procedural, above the "Opening an issue for an out-of-scope suggestion" section.
Anyone is welcome to open a PR implementing that plan if you want to!

I'll go make a PR request for this then. :+1:

authors: HonkingGoose janiceilene


text:
Update about-github-packages.md

Why:
Fixes #140 .
What's being changed:
Changed the sentence as suggested (removing the extra article in bold): "You can a delete a version of a private package on GitHub"
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

If you haven't already, you can add yourself to the list of contributors by creating a new comment in this PR using these instructions. Thanks again! :sparkles:

@all-contributors please add @casals for content doc

authors: casals janiceilene


text:
Add Squeak topic

Please confirm this pull request meets the following requirements:

[x]  I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md.
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Curating a new topic

[x] I've formatted my changes as a new folder directory, named for the topic as it appears in the URL on GitHub (https://github.com/topics/squeak)
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

There are already many repositories assigned to this topic with over 1000 stars in total.

ช้าเนอะ เอามาร่วมกันสร้างสมดุลด่วน

@LinqLover one more CI failure to address: https://github.com/github/explore/runs/5404491386?check_suite_focus=true#step:4:17

Sorry, still needs tweaked: https://github.com/github/explore/runs/5409499854?check_suite_focus=true#step:4:18

Sigh. Should work now, I hope. 😅
Please let this PR open for one more week, I have requested feedback from a few other community members.

@LinqLover Is this ready to mark as "Ready for Review" and potentially be merged?

authors: Anshuman279 LinqLover MikeMcQuaid

repo: github/explore


text:
Add LIKO-12 topic

Thank you for contributing! Please confirm the following:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

LIKO-12 is a fantasy console that has a few tagged repos 🕹

Thanks @leereilly!

authors: MikeMcQuaid leereilly


text:
Add a Gitter chat badge to README.md

github/generator-hubot now has a Chat Room on Gitter
@michaelansel has just created a chat room. You can visit it here: https://gitter.im/github/generator-hubot.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Wow, that was way too easy to accidentally create.

authors: gitter-badger michaelansel

repo: github/generator-hubot


text:
Create Cordova.gitignore

Gitignore for the Cordova framework.
Reasons for making this change:
There was no gitignore for Cordova yet.
Links to documentation supporting these rule changes:
Cordova Reference
If this is a new template:

Link to application or project’s homepage: https://cordova.apache.org/

Duplicate of gitignore in community folder

repo: github/gitignore


text:
Create LTspice.gitignore

Reasons for making this change:
LTspice is a high-performance SPICE simulation software, schematic capture and waveform viewer with enhancements and models for easing the simulation of analogue circuits.
It is the most popular Freeware SPICE simulator used extensively in both hobby and professional environments. As a hardware engineer using Github, a built in template would be quite valuable.
This is a rework of #3080, putting the .gitignore file in the correct directory.
Links to documentation supporting these rule changes:
LTSpice Filetypes List
If this is a new template:

Link to application or project’s homepage: LTspice website

I think this might be missing the *.plt files, apologies if I am incorrect. Aside from that, I think this is useful and should be merged

authors: Kaweees bartlettD


text:
Can support for  Open in new tab ?

For details, please click to seeing to 👇
https://github.com/Mottie/GitHub-userscripts/issues/123

hotkey simply calls click, so this is not its concern. Where a link is opened should be handled by the element it clicks on, for example, <a target="_blank">.
https://github.com/github/hotkey/blob/0691586c0eca5d198b5619b7321594706f5cc194/src/utils.ts#L16-L22

Thank you very much for your reply!

authors: dnknn muan

repo: github/hotkey


text:
Add PDDL

Description

Adds support for PDDL.
Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3Apddl+NOT+nothack

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

https://github.com/MylerRL661/AI-Pathfinding
https://github.com/EL2425/Drone_Project_2017-

Sample license(s):

https://github.com/MylerRL661/AI-Pathfinding/blob/main/LICENSE
https://github.com/EL2425/Drone_Project_2017-/blob/master/LICENSE.md

[x] I have included a syntax highlighting grammar: https://github.com/jan-dolejsi/vscode-pddl

See inline comment.
We also don't need quite so many nearly identical samples, not the large ones. Please remove the samples that are collapsed in the diff (clear indicator they're too big) and pick the most diverse two or three of the remaining samples and remove the others.

Thank you, I have applied the suggestions now. Please let me know if there is anything else.

Running script/list-grammars and committing the changes should fix the tests.

authors: celrm lildude

repo: github/linguist


text:
High

Looking for

config:debugger

#2086

Android Upgrades


text:
Improve a weird sentence

No one would say it that way.

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

No one would say it that way.

[x]  Have you followed the contributing guidelines?
[x]  Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

#2019


text:
hhh

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

SPAM - Locked and reported.

Spam, locked and reported

authors: ahpook bunyuh


text:
Display repositories contributed to

I mostly make contributions to pre-existing repositories, so my projects section is pretty bland. It'd be nice to be able to add arbitrary repositories we want to showcase and support pulling repositories where we have contributor access or have had a PR merged.

This does sound like a good idea however I think this project is very limited and tightly bound to the Jekyll Github plugin and as you can see, there are very few endpoints available. You can always see if it's possible to contribute to the plugin.

I miss this feature and also something like #32. In fact, any information related to contributions would be of a great value in the personal website. Is there a plan to support this out of the box any time soon?

Closing in favor of #83.

authors: BaileyJM02 SUPERCILEX ghjansen

repo: github/personal-website


text:
Refactor micro time to use a rounded duration

This is a big refactor of the micro format, to remove our rather strange rounding logic and instead use Duration with some logic which is a bit easier to reason about (and potentially easier to delete).
The main benefit here is that:

micro format is now like elapsed but with some extra logic. This pairs down a lot of the complexity we had with the format.
The micro format is now somewhat easier to deprecate, which is our intent with v5.
The format relies more on our Duration object which is a ponyfill for Temporal.Duration, and so one day can be deleted (perhaps a v6 version :wink:)
This lays ground work for us to better refactor the timeAgo and timeUntil functions which just need to be wrangled to use the same rounding logic.

It should be noted that this does change some tests! Mostly around the ways with which the micro format gets displayed. Units are rounded up in what might be considered more expected ways. Week units are introduced (so 4d, 5d, 6d, 7d will all now become 1w). Days are rounded to months, so 31d is 1m, and days are now rounded to years (so 364d becomes 1y).

:wave: Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

:art: If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
:fast_forward: If this is a PR that includes changes to an interaction, please include a video recording in the description.
:warning: If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.

authors: keithamus primer-css

repo: github/relative-time-element


text:
Daily experience improvements for Projects

Summary
We want to make sure that using projects on a day-to-day basis is a great experience. There are a number of these 'daily activities' that we want to make sure are possible, including:

[x] Re-orderable views
[x] Group-by assignee and repos
[x] Show linked pull requests
[x] Team level permissions
[x] Ability to filter by the @current iteration

This list is non-exhaustive and we expect to continue iterating and improving based on your feedback.

Re-orderable views: 🚢 Shipped! https://github.blog/changelog/2021-11-18-the-new-github-issues-11-18-update/

https://github.blog/changelog/2021-11-18-the-new-github-issues-11-18-update/
https://github.blog/changelog/2021-12-02-the-new-github-issues-12-02-update/
https://github.blog/changelog/2021-12-16-the-new-github-issues-12-16-update/

repo: github/roadmap


text:
Adding AcademicPilot's coordinates

@githubteacher Add longitude and latitude for Missoula, MT
This pull request closes #4591

Wrong repository

repo: github/training-kit


text:
🛑 MSP-002 is down

In cfe8498, MSP-002 (https://msp-portal.gw002.oneitfarm.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-002 is back up in edc1f65.

repo: gitsrc/upptime


text:
can't create kanban board since version v0.4.10

After the update to v0.4.10 I got the following error:
Updating dynamic block ‘kanban’ at line 2...
org-kanban//cleanup-description: Symbol’s function definition is void: s-replace

switching back to version v0.4.9 and the errors are gone.
tested with a plain orgfile and one TODO-Entry.
Org mode version 9.2.2 (9.2.2-13-g0007df-elpa)

Thanks for the bug reports.
Looks like there is a problem with the dependencies specified for org-kanban. Especially "s" seems to be missing. Two options come to mind:

Get rid of the call to s-replace (its only at two places),
Add the dependency.

May I ask which packaging system you are using?
Will try to do the first solution. Should be simple enough.

Should be fixed in 0.4.12.
I added s as dependency to the package header as well as to the el-get recipe.

@gizmomogwai sorry my late reply. The new version works again perfectly. To answer your questions (it might be of any value) I installed org-kanban with package-install and I had "s" installed as well. anyway thanks for the quick fix :+1:
Cheers

@veselinovic lets see.
i found several not so nice things, but i hope those are cleaned up now.

authors: gizmomogwai veselinovic

repo: gizmomogwai/org-kanban


text:
Fix to always set environment intensity

Reproduction Paths

after the environment of Pathtracer is set once, change the environment of scene to null.
when pathtracer is executed again with the environment null, it does not set the environment intensity because it is the same as the previous environment, and the old environment of the scene is rendered.

Solution
Always reset environment intensity

Sorry for the delay! Nice catch - thank you very much!

repo: gkjohnson/three-gpu-pathtracer


text:
CSV gem needs adding to Gemfile/gemspec in preparation for Ruby 3.4.0

Running command bundle exec tanakai list gives the following mesage
warning: csv was loaded from the standard library, but will no longer be part of the default gems since Ruby 3.4.0.
Add csv to your Gemfile or gemspec. Also contact author of tanakai-1.7.3 to add csv into its gemspec.

thank you, I've just merged your PR and released tanakai 1.7.4

authors: glaucocustodio n-at-han-k

repo: glaucocustodio/tanakai


text:
Occasional double rendering

Sometimes the whitespace is rendered twice (need to figure out a reliable way to reproduce).

Turns out I had two copies of the extension installed

repo: glebm/render-whitespace-on-github


text:
🛑 Schoelcher is down

In 7a89d8e, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 7cb25c2 after 488 days, 12 hours, 15 minutes.

repo: glefait/martinique-public-websites


text:
🛑 Schoelcher is down

In 69a51d4, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in b2261b3 after 5 minutes.


text:
🛑 Schoelcher is down

In 64c06bd, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in b182215 after 5 minutes.


text:
🛑 Schoelcher is down

In 9288a1b, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 72bc859.


text:
🛑 Schoelcher is down

In 3d2da6a, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in dcf2c78.


text:
Synth instrument names in MusyngKite soundfont don't match GM names, breaking programChange events

For example, a code like this, based on http://gleitz.github.io/midi-js-soundfonts/MusyngKite/names.json
MIDI.loadPlugin({
	soundfontUrl: "http://gleitz.github.io/midi-js-soundfonts/MusyngKite/",
	instrument:"synthbrass_1",
	onsuccess: function() {
		var startingPoint = MIDI.getContext().currentTime;

		MIDI.programChange(0,62);
		MIDI.noteOn(0, 72, 127, startingPoint);
		MIDI.noteOn(0, 74, 127, startingPoint + 1);
		MIDI.noteOn(0, 70, 127, startingPoint + 2);
		MIDI.noteOn(0, 58, 127, startingPoint + 3);
		MIDI.noteOn(0, 65, 127, startingPoint + 4);

	}
});

will result in complete silence and the error synth is undefined. Changing the instrument input to synth_brass_1 like in the MIDI.GM object will cause a 404 when loading the instrument file.
FluidR3_GM, on the other hand, has the proper name, thus will play music
MIDI.loadPlugin({
	soundfontUrl: "http://gleitz.github.io/midi-js-soundfonts/FluidR3_GM/",
	instrument:"synth_brass_1",
	onsuccess: function() {
		var startingPoint = MIDI.getContext().currentTime;

		MIDI.programChange(0,62);
		MIDI.noteOn(0, 72, 127, startingPoint);
		MIDI.noteOn(0, 74, 127, startingPoint + 1);
		MIDI.noteOn(0, 70, 127, startingPoint + 2);
		MIDI.noteOn(0, 58, 127, startingPoint + 3);
		MIDI.noteOn(0, 65, 127, startingPoint + 4);

	}
});

I would be willing to accept a PR that fixes this issue.

authors: DoomTay gleitz

repo: gleitz/midi-js-soundfonts


text:
Trouble getting startet

I have tested your model in your provided demo and find it very good!
Nevertheless, I am not able to set it up to run on my local computer. (I'm quite new in this and has e.g no experience with docker.)
Is it possible for you to create a more thorough guide to get the model up and running on a local system?

Did you get it to work?

repo: gligen/GLIGEN


text:
fmmpeg not being recognised (macOS)

Hello, I've been trying to get the animation options working in the mod but for some reason, ffmpeg is not being detected. I have tried installing it via brew.sh and also manually putting the ffmpeg folder and file in the .minecraft folder but nothing worked still. Is there anything I'm missing? I am using an M1 chip if that matters and using PrismLauncher.

As you can see in this comment on issue #46, it is not currently possible to use FFmpeg on macOS without modifying your launcher settings
Since this also a duplicate of the mentioned issue, I'll be closing it
Cheers

repo: gliscowo/isometric-renders


text:
MessageFormat formatters

The messageformat library supports custom formatter functions. You could register globalize's formatters, so they could be used in messages, e.g. "Balance: {0, currency}", or "Posted at {0, datetime, long}".
It would also be great if there was a way to pass custom formatter functions to MessageFormat.

Thanks for your message and sorry for the delayed answer.
Please, use variable replacement instead, e.g.: "Balance: {currency}" or "Posted at {date}" and have the variable formatted using the appropriate formatter in your code, e.g.:
Globalize.formatMessage("message", {date: Globalize.formatDate(new Date())});

If you find any problem using variable replacement instead or if you have further questions feel free to post additional comments.
PS:

The messageformat library supports custom formatter functions

... and I was one of the early pushers for such API to be adopted by SlexAxton/messageformat.js (the libraries Globalize uses for mesage formar under the hoods) (link). :smile: (and Alex an Eemeli did a great work updating the library). Having said that, given variable replacement could be used instead with no prejudice in that case, we opt for that.
If you want to update globalize message format to support such feature, feel free to contribute the change and I'd be happy to consider it: (a) send informal messages first to discuss the new API, then send a pull request with the implementation.

The problem with using a formatter in the variable is that it doesn't allow you to change the format in the message file. It's hard-coded.
This would not only allow the format to be customized for each language, it would also allow changing it without touching the code. E.g. if you have an interface where an admin can change the message files used by your app, this change would allow an admin to customize the format used in a message.

I made a quick proof of concept. The issues with it are:

the formatter function only gets a locale string (or array), so it needs to create a new Globalize instance: https://github.com/nkovacs/globalize/commit/bba99b7a82d25d92818c08114132c2657c7a071a#diff-731a3fca6b201d79e2639fe1456b8787R166
I added a global object to Globalize in core.js to collect the formatters: https://github.com/nkovacs/globalize/commit/bba99b7a82d25d92818c08114132c2657c7a071a#diff-7eb52b366866677666470e019283c8eaR89. This is probably not the most elegant way to do this.
The compiler compiles the message 'Hello World {now, date, long}' into this:

Globalize.b955419430 = messageFormatterFn((function(  ) {
  return function (d) { return "Hello World " + fmt.date(d.now, ["en"], "long"); }
})()

Ideally I'd like the compiler to automatically detect the call to fmt.date, and compile the dateformatter as well, but I don't know if that's possible with the current version of MessageFormat.
This is the test file I used: https://gist.github.com/nkovacs/d6e429f7a5e0871ceb392e739031c100

As an earlier step, could you please show me a map between each Globalize formatters option and its inlined message format representation? For example, above you mentioned long, is long the value for date, time, or datetime? Also, how to pass a skeleton?

Ideally I'd like the compiler to automatically detect the call to fmt.date, and compile the dateformatter...

Yeap the compiler could statically parse the message and do that (i.e., reuse the message formatter parser to deduce the formatters).

The message was {now, date, long} in the example, so it becomes {date: 'long'}. {now, time, long} would be {time: 'long'}, and {now, datetime, long} would be {datetime: 'long'}.
This is similar to what ICU does (http://icu-project.org/apiref/icu4j/com/ibm/icu/text/MessageFormat.html), except ICU only has date and time.
ICU also accepts a raw format (if the parameter is not one of the short formats), so {now, date, yyyy-MM-dd} would become {raw: 'yyyy-MM-dd'} if you wanted to emulate that.
Skeleton could be implemented in a few different ways:

{now, date, skeleton:GyMMMd}: this means you can't have {raw: 'skeleton:yyyy-MM-dd'}, but I don't think that's a big problem.
{now, date, skeleton, GyMMMd}: presumably no-one wants to use 'skeleton' as a raw value
{now, dateskeleton, GyMMMd}

The basic mapping could look like this:

{now, date, long} -> dateFormatter({date: 'long'})
{now, time, long} -> dateFormatter({time: 'long'})
{now, datetime, long} -> dateFormatter({datetime: 'long'})
{x, relativetime, day} -> relativeTimeFormatter('day')
{x, relativetime, day, short} -> relativeTimeFormatter('day', {form: 'short'})
{x, number} -> numberFormatter()
{x, number, percent} -> numberFormatter({style: 'percent'})
{x, currency, USD} -> currencyFormatter('USD')
{x, currency, USD, accounting} -> currencyFormatter('USD', {style: 'accounting'})
{x, unit, second} -> unitFormatter('second')
{x, unit, second, short} -> unitFormatter('second', { form: "short" })

But one reason I'd like to be able to customize the formatters is that I wanted to integrate globalize with Yii, and I could write custom formatters that work the same way ICU in php does (http://www.yiiframework.com/doc-2.0/guide-tutorial-i18n.html#message-formatting). That way I could use the same messages in php and in javascript, which is kind of a pain right now (I have to render everything in php to get pluralization and such things, and then return the html in the ajax response).

Yeap the compiler could statically parse the message and do that (i.e., reuse the message formatter parser to deduce the formatters).

Yeah, but for globalize I think it would be better if the custom formatter function received the Globalize instance, the same one used to render the message, so you don't have to instantiate another one and compile a new formatter each time the message is rendered (if you're not using pre-compiled files). But that requires modifying messageformat or using messageformat-parser directly. The runtime binding code is already a bit hacky, it could also be cleaned up.

I liked it so far. /cc @jzaefferer and @alunny for their inputs.

I've hacked messageformat so that the custom formatter function can use the same globalize instance, and the dependent formatters can be passed to globalize-compiler: https://github.com/nkovacs/globalize/commit/21cb3b3923fbac0937bc5ab0d626d6e107a6fb30#diff-731a3fca6b201d79e2639fe1456b8787L156
I'll try to clean it up and get it into messageformat.js, but for now I just wanted to show how it could be done in globalize.

This sounds great. Any news on it?

Compilation now works. The only thing that needs to be changed in globalize-compiler is the compilation order.
Messageformat.js has since released a major new version, so I'll have to update that too.

Messageformat.js 1.0 has changed so much that the hacks used to integrate it into globalize no longer work. In particular, since the runtime is no longer static, I was unable to extract it and inject it into globalize's message-runtime module.
So instead I copied the messageformat compiler and runtime into globalize.js, and used messageformat-parser (which has since been extracted into a separate npm package). Since I now had direct access to the compiler, I was also able to remove the regexp hacks in messageFormatterRuntimeBind (the compiler can tell the runtime binding function what features are needed, e.g. plurals, select etc.).
Here's the commit: https://github.com/nkovacs/globalize/commit/1586e12ff1b7f24a649e442899e76575f6c19b2d
What do you think?

These presets look nice:

{now, date, long} -> dateFormatter({date: 'long'})
{now, time, long} -> dateFormatter({time: 'long'})
{now, datetime, long} -> dateFormatter({datetime: 'long'})

Any of the below look nice to me too, except for the fact that adding a time pattern in the skeleton below will result in a datetime output, which sounds inconsistent with date since we have message formatters named time or datetime. Do you see what I mean? I have no suggestion at the moment though.

{now, date, skeleton, GyMMMd}
{now, dateskeleton, GyMMMd}

Messageformat.js 1.0 has changed so much that the hacks used to integrate it into globalize no longer work. In particular, since the runtime is no longer static, I was unable to extract it and inject it into globalize's message-runtime module.

So instead I copied the messageformat compiler and runtime into globalize.js, and used messageformat-parser (which has since been extracted into a separate npm package). Since I now had direct access to the compiler, I was also able to remove the regexp hacks in messageFormatterRuntimeBind (the compiler can tell the runtime binding function what features are needed, e.g. plurals, select etc.).

The existing "live-patch" isn't great, but I want to avoid copying dependencies and modifying them, because this is even harder to maintain over time. We need a better approach... Are there any changes we could propose in their code that would make it easier in our side? Is there any sort of JavaScript patch we could use instead of the bunch of replaces in Gruntfile?

About plural requiring cardinal + ordinal data... I want to avoid that. I'm wondering if {plural, ... could use a cardinal formatter, and {selectordinal, ... could use a ordinal formatter?

Any of the below look nice to me too, except for the fact that adding a time pattern in the skeleton below will result in a datetime output, which sounds inconsistent with date since we have message formatters named time or datetime.

I didn't implement the skeleton and raw options yet because I'm not sure how to do that. The rest are done: https://github.com/jquery/globalize/commit/4c95d9499efa4add7e0ed80fb8a531f62de754de.

About plural requiring cardinal + ordinal data... I want to avoid that. I'm wondering if {plural, ... could use a cardinal formatter, and {selectordinal, ... could use a ordinal formatter?

With the custom compiler, yes. I'm not sure if it's doable if using messageformat.js directly, in the current version of globalize. It probably is, but it won't be pretty. That ties into your next question.

The existing "live-patch" isn't great, but I want to avoid copying dependencies and modifying them, because this is even harder to maintain over time. We need a better approach... Are there any changes we could propose in their code that would make it easier in our side? Is there any sort of JavaScript patch we could use instead of the bunch of replaces in Gruntfile?

I've used messageformat-parser from npm (it's not available in bower), so I only had to copy and rewrite the compiler and the runtime, which is relatively small, and that allowed me to customize it to globalize's needs. For example, the new messageFormatterRuntimeBind is much better.
I think this is a better approach than heavily patching messageformat.js in the Gruntfile.
It might be possible to use messageformat.js from npm and use only the compiler (compiler.js), but that's internal, so you'd again be left with something that can change and break at any time, plus some monkey-patching would still be needed.
The changes required to messageformat.js to make it usable in globalize would be extensive. They'd have to make it possible to customize the compiler. I doubt they'd want to add that complexity to messageformat.js, when you can just use messageformat-parser and write your own simple compiler.

I only had to copy and rewrite the compiler and the runtime

Could you please show me a diff?

https://github.com/nkovacs/globalize/blob/1586e12ff1b7f24a649e442899e76575f6c19b2d/src/message/compiler.js, which is based on https://github.com/messageformat/messageformat.js/blob/master/lib/compiler.js (plus some small parts of https://github.com/messageformat/messageformat.js/blob/master/lib/index.js)

and

https://github.com/nkovacs/globalize/blob/1586e12ff1b7f24a649e442899e76575f6c19b2d/src/message/formatter-runtime.js, which is based on https://github.com/messageformat/messageformat.js/blob/master/lib/runtime.js (with unnecessary toString code removed)

Yeap, but looking at a diff from the original compiler and runtime to their rewritten ones would be easier to see what the changes are. Don't worry if you don't a diff handy, I can generate one...
Basically, I'm in line with your suggestion of using a newer messageformat. Although, I want to better understand the changes and impact.

It's a bit hard to see it here because of the whitespace changes required by the coding standard:
compiler.js: https://gist.github.com/nkovacs/8dea134c8af7345c1c7ed921e9dc7aad/revisions
runtime.js: https://gist.github.com/nkovacs/11f320e6ae60b1dccf943768367dab4d/revisions
The first revision is messageformat.js's version indented with 4 spaces (original is 2 spaces), second revision is my version.

I used your gists and created this diff that ignores white space changes:

https://gist.github.com/rxaviers/0e57ed723f28800c06e1c07e6c069f1d

@nkovacs how to you suggest we maintain these files? For instance, let's suppose messageformat publish new releases with updates to those files and we want to bring those updates in.

Another question is, what are the challenges and cost of using the new messageformat as is?

EDIT: Another question is, what are the challenges and cost of using the new messageformat as is? From your above comments, one of them is "They'd have to make it possible to customize the compiler", what customization would be required please?

The problems I ran into trying to use messageformat 1.0.2:

This part here needs changes: https://github.com/jquery/globalize/blob/master/Gruntfile.js#L189
Some of these replacements no longer work, because the code has changed, e.g.: MessageFormat.plurals and MessageFormat._parse. You could fix these, but this patching is hard to maintain.

message-runtime has changed to a dynamic object instead of a static one: https://github.com/messageformat/messageformat.js/blob/v1.0.2/messageformat.js#L239. This part won't work: https://github.com/jquery/globalize/blob/master/Gruntfile.js#L237

This also won't work: https://github.com/jquery/globalize/blob/master/src/message/formatter-runtime-bind.js#L26, because instead of pluralFuncs.en, it's now just en.

The problems with using messageformat in general (this applies to 0.3.0 as well):

messageFormatterRuntimeBind has to use  regexp to detect the dependencies of the formatter function: https://github.com/jquery/globalize/blob/master/src/message/formatter-runtime-bind.js#L14
I was able to simplify this by having direct access to the compiler: https://github.com/nkovacs/globalize/blob/563-custom-formatters/src/message/formatter-runtime-bind.js#L13

The biggest problem for this feature is this part: https://github.com/messageformat/messageformat.js/blob/v1.0.2/messageformat.js#L113 (similar in 0.3.0: https://github.com/messageformat/messageformat.js/blob/v0.3.0/messageformat.js#L1715). I'd have to use regexps in messageFormatterRuntimeBind to try to figure out which formatters are used, and with what parameters. I changed this part so that it calls the registered formatter factory function, and returns that function to the compiler, which can then bind that: https://github.com/nkovacs/globalize/blob/563-custom-formatters/src/message/compiler.js#L159 (this.formatters is passed as embeddedFormatters to messageFormatterRuntimeBind: https://github.com/nkovacs/globalize/blob/563-custom-formatters/src/message/formatter-runtime-bind.js#L25)

The problem is that messageformat.js compiles {now, date, short} to something like fmt.date(d.now, 'short'), but globalize.js needs the 'short' parameter at compile time to be able to compile an appropriate formatter function.
The minimum change required in messageformat.js would be to return the compiler's runtime property and add the arguments to its formatters object.
Globalize's compiler could then generate the appropriate wrappers and an fmt object with a special wrapper fmt.date function, and bind the compiled dateformatter as a dependency.
My version does it slightly differently: {now, date, short} is compiled to fmt[0](d.now), and the wrapper function receives an fmt array, where the 0th element is Globalize.dateFormatter({date: 'short'}).
Here's a complete compiled example:
Globalize.b955419430 = messageFormatterFn((function(plural, fmt, en) {
    return function(d) {
        return "Hello World number( " + plural(d.x, 0, en, {
            one: "one task " + fmt[0](d.now) + " ",
            other: d.x + " tasks " + fmt[1](d.now) + " "
        });
    }
})(messageFormat.plural, [Globalize("en").dateFormatter({
    "date": "long"
}), Globalize("en").dateFormatter({
    "date": "short"
})], Globalize("en").pluralGenerator({
    type: "both"
})), Globalize("en").pluralGenerator({
    "type": "both"
}), Globalize("en").dateFormatter({
    "date": "long"
}), Globalize("en").dateFormatter({
    "date": "short"
}));

and the original message was:
'Hello World number( {x, plural, one {one task {now, date, long} } other {{x} tasks {now, date, short} } }'

I'm not sure why the extra parameters are passed to messageFormatterFn, but I think that's already happening with the current version of globalize.js and pluralGenerator.

Any update on this? I am running into this as well. The messages for me are potentially user defined so formatting the value passed in isn't an option.

authors: ccschneidr jrsearles nkovacs rxaviers

repo: globalizejs/globalize


text:
Poder navegar los productos filtrando por rubro

#144

[ ] Aplicar bold y color igual que la descripcion de producto (ver imagen)

[ ] Agregar negritas al rubro y su flechita

authors: belluccifranco facundososalopez

repo: globo-technology/sic-com


text:
run unit tests with gradle

./gradlew test
should execute all unit tests.

Resolved by fded6c5a4ef3191a6ef70888c94d7766ab45755e

authors: eugener johanvos

repo: gluonhq/strangefx


text:
Missing include-file

C:\Users\raffi\Documents\Arduino\libraries\ESPNtpClient-main\src/ESPNtpClient.h:41:16: fatal error: TZ.h: No such file or directory
If i look there, the TZ.h is missing.
My mistake or your fault?
Greeetings,
Ralf

After updating to the actual esp8266 core,  everything is fine

Good to know. Thank you


text:
Disconnect hangs

Hello,
Thanks a lot for developing this nice tool.
I've got a question regarding the connection Disconnect function; when I use it, it hangs, and when I debug it, the debugger stops at the following line:
https://github.com/gmallard/stompngo/blob/78e25a2785946491585cc90d1d9a5ca9266eaee4/disconnect.go#L83
Do you have any ideas why this might be the case?
Thanks a lot for your help in advance.
Feel free to let me know if you need any further information.

Furthermore, the line above does not seem to take the ReadDeadline into account, if I am not mistaken?

I do have test(s) for disconnect receipts, and do not see hangs.
What stompngo version are you running ?
Do you have a short example that shows this behavior ?
Can you get me a stack trace of the hang (on Linux press Ctrl-\ when the hang occurs)?
Can you enable logging and show me that output ?
ReadDeadLine is reset between all calls to the TCP reader.  They have to be.  Otherwise nothing would work right.
You could always request no receipt as a work around.

Thank you very much for your prompt reply, much appreciated!
stompngo version: v1.0.12
I'm currently working on a minimal example, I'll come back to you as soon as I know more or have it available.
Please find the recorded stack trace with enabled connection logging attached:
stackdumpWithLogMasked.txt
I enabled the logging with conn.SetLogger. Please let me know if you'd like me to log something else as well.

ReadDeadLine is reset between all calls to the TCP reader. They have to be. Otherwise nothing would work right.

Alright, I see. Thanks a lot for the information.

You could always request no receipt as a work around.

Unfortunately I have to request a receipt to make sure that the disconnection has worked properly, for reasons that are probably beyond the scope of this.
Thank you very much for your help.
If you have any questions/comments, please do not hesitate to say so.

Are you fully draining your input queues/topics ?
It looks like the system is deadlocked trying to send you a MESSAGE frame which you have not received.

thanks a lot for your help. now I'm draining the topic in a parallel goroutine while disconnecting, and it doesn't hang anymore -- however, now, it never receives a receipt. conn.DisconnectReceipt is empty, as well as all subsequent messages on conn.

short update: I see now that it works for some servers, for some not. I'll further investigate whether the error is in on the side of server's STOMP implementation, and come back to you if that error source is excluded. In the meantime I'll close this issue.
Thanks a lot for your prompt and helpful input, much appreciated!

By now I can say that the error is not on the side of the servers.
My most recent insights are: Your library sees and records the receipt (visible in the logs):tada:, but when I try to access it with conn.DisconnectReceipt, it's sometimes no longer there. :thinking: Because of that, I can't verify that the receipt ID is the right one. Does the connection shutdown logic delete the recorded receipt, s.t. this issue would be due to a race condition?

The receipt is never deleted by stompngo code.
Show me the logs you are looking at please.  The receipt should actually be in the logs (see code in disconnect.go).
Also ..... I need some code that recreates this.  Because I cannot recreate it here .......

I've now taken another look at the logs and found something potentially interesting.
LOG:  2019/10/31 13:42:09.991834 connection.go:182: ID:< SOME ID, MASKED > < $HOME - MASKED >/go/pkg/mod/github.com/gmallard/stompngo@v1.0.12/disconnect.go 84 [DISCONNECT dr receipt:6
 {{  []} <nil>}]

Contrary to my original suspicion, the logged receipt in this line is not the one in the received message (which is in fact empty, as logged) -- it is a second mentioning of the earlier sent receipt.
This is the code creating the log entry:
c.log(DISCONNECT, "dr", ch, c.DisconnectReceipt)

where ch is a clone of the headers the user passed as the method's argument + a receipt, if the user didn't disallow it explicitly.
I suggest to check in the library whether the received receipt is the valid & expected one, e.g. with
conn.DisconnectReceipt.Message.Headers.ContainsKV(stomp.HK_RECEIPT_ID, receipt)

and with listening to the receipt with some safety margin. For example, one can start listening already right before sending the DISCONNECT frame, and keep listening some time until a receipt arrives. If the receipt doesn't arrive within a given timeout, one can mark the disconnection as unsuccessful -- I'm interested in hearing your input on how to handle this best, what follow-up actions to take if the disconnection didn't work. So far I've closed the underlying connection with a defer statement and stopped program execution to avoid the message buffer exploding on the server side.
I've implemented this mentioned procedure, let me know if you'd like me to contribute the code.
The only part that's missing is to start listening to the receipt already before sending the DISCONNECT frame, I'll do that now and keep you posted.
Also, I'm working on a small example, I'll come back to you as soon as I know more.

I'd like to give a short progress update.
As mentioned earlier, this issue doesn't always appear. I wrote a small example to connect and then disconnect with a receipt, but so far it works. There seems to be some sort of race condition or the like. Should I be able to reliably reproduce the error at some point, I'll tell you.
Since I have no idea where the issue comes from, and since the hypothetical race condition seems nontrivial to debug, I've now chosen the following procedure (and will change it back as soon as this issue is solved): If I don't get a receipt, it's not too bad, since I close the underlying connection afterwards anyways. So, I attempt to do it the nice way -- with a receipt -- but if it doesn't work, the program doesn't throw an error, it just warns, closes the underlying connection, and exits, since this is anyway the last action (at least in the current implementation).
If you'd like to suggest a different procedure or would recommend a different approach, please feel free to let me know, I'd be happy hear your feedback.

Put a check in your code that looks at what is actually in conn.DisconnectReceipt.  I want to know if it is actually an ERROR frame.
That is entirely possible, and my code does not handle that properly.  I am working on a fix for that.

Ah, I think there might be a small misunderstanding :) I did not receive ERROR frames, but entirely empty ones; I have checks for this in the code:
if r.Message.Command == "" && (len(r.Message.Headers) == 0) && (len(r.Message.Body) == 0) {
    emptyMsgCount += 1
}

In general , thanks a lot for looking into this, much appreciated!

Two items:

There is an enhancement/correction to Disconnect on HEAD of the dev branch.  You might try that to see if it provides any more data about this.

This section in the specification:

https://stomp.github.io/stomp-specification-1.2.html#Connection_Lingering
Read the last sentence of that section.

Sorry for the delayed message.
Thanks a lot for pointing me to that sentence in the specification, that is very helpful!
Thanks also for the changes in the dev branch, they look good to me. If possible I'll try them out sometime soon and tell you how it went.

Note that there is another reference to this behavior in:
https://stomp.github.io/stomp-specification-1.2.html#DISCONNECT
Question:  have you tried this with heartbeats on?

Indeed, this is very helpful! Thanks a lot, your help is much appreciated.
Yes, I had heartbeats on.

There is another enhancement to DISCONNECT on the dev branch.
It allows the user to optionally specify a "disconnect timeout".  After the timeout expires, if no RECEIPT frame has been received, DISCONNECT will return an error indicating a timeout.

Also, I pushed v1.0.13 to github a bit ago.  Includes all the DISCONNECT enhancements.  Please give that a try.

Please excuse the delayed reply.
Thanks a lot for the new features, this looks good to me.
At the moment I've switched from ActiveMQ to something else. I'm quite busy atm, but generally I'd be happy to try the changes out -- I'll let you know if I get a chance :)
Two small suggestions looking at the code: How about implementing timeouts with
case <- time.After(<timeout>)

instead of creating a ticker and assigning the channel output to _ here?
This is just a minor suggestion, nothing crucial.
Source: https://gobyexample.com/timeouts , last visited: 19. November 2019

I am always curious about brokers.  I would like to ask:  from AMQ to what ?
Here I test with:

AMQ
Rabbit
Artemis
Apollo (the last release, since development has ceased)

Using time.After is a good idea, thanks,  I will probably tweak the code to do that.

I switched from AMQ to a totally different approach that doesn't involve messaging at all -- not because of the messaging itself, but because my program needs to fetch information from somewhere else after all. :)
You're welcome, as already said just a small suggestion, nothing important.
Thank you very much for helping with this, very much appreciated! And in general thank you very much for maintaining this library.

Apologies for the very tardy reply.
Removal of TIcker form that code has been on DEV since 12/23/19.  Commit:
950baf2f32bd72518525eaa3d97c6d223d9998d0
I hope you have been able to try that.
I am going to close this issue based on the above.  If you need to re-open it, please d so.
Regards, Guy

Thanks much for your message :) no worries about the delay.
I opened the issue during an internship, by now I don't have access to the code anymore for which I experienced the issue. Closing the issue sounds good to me.

authors: c-bg gmallard

repo: gmallard/stompngo


text:
Can't work with documented syntax

Relates to #32
In service A, I got the resource created successfully on deployment:
resources:
  Resources:
    LambdaFailureQueue:
      Type: AWS::SQS::Queue
      Properties:
        QueueName: ${self:provider.stage}-${self:service}
        MessageRetentionPeriod: '1209600'
        VisibilityTimeout: '60'

and a handler in the same serverless.yml file successfully gets triggered by
    events:
      - sqs:
          arn:
            Fn::GetAtt:
              - LambdaFailureQueue
              - Arn

So far, so good. Then, in service B, I'm trying to attach fallback behavior to this previously created dead letter queue.
These don't work:
    deadLetter:
      targetArn:
        - 'Fn::Join':
          - ':'
          -
            - 'arn:aws:sqs'
            - Ref: 'AWS::Region'
            - Ref: 'AWS::AccountId'
            - '${self:provider.stage}-ingestion-dead-letter-queue'

Results in:
Function property parseCsv.deadLetter.targetArn object is missing GetResourceArn property.

    deadLetter:
      targetArn:
        GetResourceArn:
          - 'Fn::Join':
            - ':'
            -
              - 'arn:aws:sqs'
              - Ref: 'AWS::Region'
              - Ref: 'AWS::AccountId'
              - '${self:provider.stage}-ingestion-dead-letter-queue'

Results in
Expected params.LogicalResourceId to be a string

The only syntax, which works is the following:
    deadLetter:
      targetArn: 'arn:aws:sqs:${self:provider.region}:12345:${self:provider.stage}-ingestion-dead-letter-queue'

I've tried using serverless-pseudo-parameters in order to have the following syntax:
    deadLetter:
      targetArn: 'arn:aws:sqs:${self:provider.region}:#{AWS::AccountId}:${self:provider.stage}-ingestion-dead-letter-queue'

However, this results in
Function property parseCsv.deadLetter.targetArn object is missing GetResourceArn property.

Another approach I tried:
Make an export from service A:
  Outputs:
    LambdaFailureQueue:
      Description: The dead letter queue for AWS Lambda handlers.
      Value:
        Fn::GetAtt: ["LambdaFailureQueue", "Arn"]
      Export:
        Name: "${self:custom.eubfrEnvironment}:${self:service}:LambdaFailureQueue"

And then try an import in service B:
    deadLetter:
      targetArn:
        Fn::ImportValue: ${self:custom.eubfrEnvironment}:ingestion-dead-letter-queue:LambdaFailureQueue

-> not working
Function property parseCsv.deadLetter.targetArn object is missing GetResourceArn property.

trying also
    deadLetter:
      targetArn:
        GetResourceArn:
          Fn::ImportValue: ${self:custom.eubfrEnvironment}:ingestion-dead-letter-queue:LambdaFailureQueue

-> again error
Expected params.LogicalResourceId to be a string

My goal is to find a way to get rid of the specific account number, as a wildcard also results in:
Function property parseCsv.deadLetter.targetArn = 'arn:aws:sqs:eu-central-1:*:chernka204-ingestion-dead-letter-queue'.  This is not a valid sns or sqs arn.

This solution worked quite well as a workaround.


text:
Chore/api corrections

Small adjustments to API

Thank you.

authors: allanbrondumkr gmosx

repo: gmosx/xrpl-sdk-rust


text:
Update gulp, babel, eslint, add package-lock

Project can't build without package-lock.json. I was got many errors when i tried to do it. I think that PR make it better

Hey @kondr1, this repository specifically uses a Yarn and a yarn.lock file, one of many package managers for node. Maybe it would be better to include that information in the documentation, and update the dependencies there?

Hmm. Ok

license: Unlicense


text:
midterm done and dusted

https://www.youtube.com/watch?v=Iviz8cNECTg

Ah but do you know your curveballs from your googlys: https://en.wikipedia.org/wiki/Googly

authors: austronomer gnarayan


text:
Update sbt-typelevel to 0.5.0

About this PR
📦 Updates org.typelevel:sbt-typelevel from 0.4.22 to 0.5.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "sbt-typelevel" } ]

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

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:n:2

Superseded by #522.


text:
chore: better support for mac shortcuts

On Mac, you typically use the metaKey instead of ctrlKey and Backspace is also considered a delete operation

Addressed in https://github.com/gniziemazity/advanced_drawing_app/pull/32 as well


text:
Async redis cmds (sync connection pool)

Closes #803

Seemingly working with async comands
No need for additional crates, just additional features from redis-rs
We should probably look into using a ConnectionManager

Moving in favour of the solution with an async connection pool

repo: gnosis/safe-client-gateway


text:
Use 1.3.0 contract for all safes

Description
We should target 1.3.0 proxy factory and multisend contracts for all safes on all networks.
However, create new safes still only on 1.1.1 on mainnet and rinkeby.

Closes, because not needed. Safes created on 1.3.0 will target 1.3.0 contracts already.

repo: gnosis/safe-react


text:
(Fix) Preserve contract name in custom contract interaction flow

What it solves
fixes #2384
How this PR fixes it
By following the same strategy as in SendFunds modal. That is, lookup the name in AB, then pass it as param between screens.
How to test it
Follow steps in the issue.

the fix is in #2422, once merged I'll rebase the base branch to this PR's branch

@francovenica, branch updated. You should be able to test this PR now.

The PR doesn't crash anymore. Thanks!
I've checked the name of the contract in the review step for both, regular contract interaction with methods and contract interaction with a data hex encoded. I both the name of the contract is shown properly

Looks good to me

authors: fernandomg francovenica


text:
🛑 Forkmon ETH2 is down

In d0216a2, Forkmon ETH2 (https://eth2-forkmon.chiadochain.net/) was down:

HTTP code: 502
Response time: 216 ms

Resolved: Forkmon ETH2 is back up in 762399d after 2 minutes.

repo: gnosischain/chiado-uptime


text:
centos 8.4 / docker-compose 部署，因数据库字符集问题，导致无法初始化

运行环境

应用版本:

atomci-frontend:  1.3.0
atomci: 1.3.0

Kubernetes: 1.3.0
os: cenos 8.5

问题描述
docker-compose 部署， 数据库字符集问题，导致无法初始化 atomci不能启动
截图

修复方案：
$ docker exec -it mysql /bin/bash

> mysql -uroot -p

原因：　mysql字符集设置未生效，
可以按照上图的方案手动修复，也可重新下载已经release的版本, 如：1.3.0

repo: go-atomci/atomci


text:
[Feature] Expose name of deleted PR branches

Gitea version (or commit ref): 1.11.0
Git version: 2.24.1
Operating system: Linux (Alpine)
Database (use [x]):

[x] PostgreSQL
[x] MySQL
[x] MSSQL
[x]  SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes: https://try.gitea.io/ppmathis/test/pulls/1
[ ] No
[ ] Not relevant

Description
When the head branch of a pull request in either state gets deleted, the pull request no longer exposes the original branch name. This is directly related to #9158, which requested tracking the ref to the tip of the deleted branch and a working commit/changes view.
I would like to suggest to also expose the name of the branch which got deleted through both UI and API instead of just showing from deleted into <target branch>. The name of the branch can usually be accessed as head.ref in the API, however the whole head property is null as soon as the branch got deleted.
Screenshots
PR with correct branch name before branch deletion

PR with missing branch name after branch deletion

Because that branch maybe from another repository which deleted.

We should probably display branch name even if it is deleted just without link and marked as deleted

@lafriks That would be the kind of behavior I'd expect - even when the branch or repository got deleted, the PR should still expose the original branch name through UI and API.
This also follows the implementation of all other major Git platforms including GitHub and is useful for stateless bots which can determine if a PR has been previously opened by checking for a predictable branch name.

authors: lafriks lunny ppmathis

repo: go-gitea/gitea


text:
Filter repositories by type

An option to filter the repositories (on user and explore pages) by type (mirror, repository, fork, private, public) would be useful.

I was just able to make a mockup which should address this issue and make #1318 a duplicate if implemented, hope it helps someone who wants to implement this feature.


text:
[FR] notify admins on account registration with REGISTER_MANUAL_CONFIRM

The new config flag REGISTER_MANUAL_CONFIRM = true is a mvp, but not very usable:
As an site-admin I don't know when somebody wants an account, because I don't get notified.

+1 for this one.
I run 1.14 with REGISTER_MANUAL_CONFIRM = true and this works. on 1.15(Master it has not worked!)
It would be really requried to have emails to admin after registration and email to user after admin activates account.
Thank you very much.

Agree! this is just necessary ;)

authors: hidiego noerw vsatmydynipnet