text:
ReactOnRails is not defined when including application.js at bottom of body

When including application.js at bottom of body like this:

  <%= javascript_include_tag 'application', 'data-turbolinks-track' => true, 'data-turbolinks-eval' => false %>

and using react_component helper to render a component in a view (i.e.: /admin/purchases/new)
<%= react_component("PurchaseForm", {}, prerender: false, trace: true, generator_function: false) %>

I get a Uncaught ReferenceError: ReactOnRails is not defined.  Obviously this is because the Javascript written by the helper is executed when the DOM is loading, and before the application.js is included.
In order to avoid the error what I've done is the following:

  <%= javascript_include_tag 'application', 'data-turbolinks-track' => true, 'data-turbolinks-eval' => false %>
  <%= content_for :react_components %>

and in the view:
<% content_for(:react_components) do
    concat react_component("ClientApp", {}, id: 'reactRoot', prerender: false, trace: true, generator_function: false)
  end %>

I just wanted to share my experience using this gem... Is there any better approach for this? If not maybe you'd like to include this strategy in the README.

@hisapy application.js should be included in the head of the document. Any reason you're placing it in the body?

Feel free to re-open this ticket if you're sure that there's a case for putting application.js in the body.

Actually, it seems no there is need anymore to move it out from the head.

@justin808 Yahoo recommends loading scripts at the bottom of the page to avoid blocking parallel downloads.

@rupurt we did a little research and concluded that the Yahoo advice is no longer worthwhile due to typical caching of the bundled JS file as well as the use of turbolinks. That being said, if you can create a simple demo of a performance gain, we'd be very happy to change the way we're organizing the JS code.

@rupurt Please look at this: http://forum.shakacode.com/t/should-rails-apps-use-defer-when-loading-application-js/404/3?u=justin

authors: hisapy justin808 rupurt


text:
🛑 Shakedown Social - Uploads is down

In f6ce227, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 289 ms

Resolved: Shakedown Social - Uploads is back up in 1488746.

source: gharchive/issue

repo: shakedown-social/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Shakedown Social - Uploads is down

In 9b31d2b, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 411 ms

Resolved: Shakedown Social - Uploads is back up in 93a7213.


text:
🛑 Shakedown Social - Uploads is down

In 1bd967b, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 519 ms

Resolved: Shakedown Social - Uploads is back up in a2acc97.


text:
🛑 Shakedown Social - Uploads is down

In 5dd0410, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 294 ms

Resolved: Shakedown Social - Uploads is back up in 2b42549.


text:
🛑 Shakedown Social - Uploads is down

In 106f1b9, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 433 ms

Resolved: Shakedown Social - Uploads is back up in 9450d75.


text:
🛑 Shakedown Social - Uploads is down

In 27fd9a1, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 311 ms

Resolved: Shakedown Social - Uploads is back up in 99242c9.


text:
🛑 Shakedown Social - Uploads is down

In 3c397ae, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 278 ms

Resolved: Shakedown Social - Uploads is back up in c7d0efb.


text:
🛑 Shakedown Social - Uploads is down

In 17927dc, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 370 ms

Resolved: Shakedown Social - Uploads is back up in ef8fac4.


text:
[3pt]  - Add tests for comments counter - Student B

Make sure that the function for the comments counter is covered with unit tests using Jest.
Make sure that you have tests for all edge cases.

Nice work! https://github.com/shakerAbuDrais/FreeEpicGames/pull/28

authors: julzedz shakerAbuDrais

repo: shakerAbuDrais/FreeEpicGames


text:
Eror no run HamsterKombatBot-main>

(venv) D:\GMP\tele\HamsterKombatBot-main\HamsterKombatBot-main>python main.py
Traceback (most recent call last):
File "D:\GMP\tele\HamsterKombatBot-main\HamsterKombatBot-main\main.py", line 4, in
from bot.utils.launcher import process
File "D:\GMP\tele\HamsterKombatBot-main\HamsterKombatBot-main\bot\utils_init_.py", line 8, in
if not os.path.exists(path='sessions'):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: nt._path_exists() takes no keyword arguments
run statt.bat
Activating virtual environment...
Starting the bot...
Traceback (most recent call last):
File "D:\GMP\tele\HamsterKombatBot-main\HamsterKombatBot-main\main.py", line 4, in
from bot.utils.launcher import process
File "D:\GMP\tele\HamsterKombatBot-main\HamsterKombatBot-main\bot\utils_init_.py", line 8, in
if not os.path.exists(path='sessions'):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: nt._path_exists() takes no keyword arguments
Press any key to continue . . .
Thanks

Install and configure all correctly:

https://github.com/shamhi/HamsterKombatBot/issues/290#issuecomment-2162692634

authors: ButCheR-PRO nvquangil

repo: shamhi/HamsterKombatBot


text:
Tools page sort dropdown does nothing

The sort dropdown gives alphabetical by name no matter which of the dropdowns I choose.
http://long-read-tools.org/tools.html?sort=techs

This problem seems to exist on the categories and technologies tabs too.

Fixed in the new facelifted database

Fixed in the new facelifted database

authors: scottgigante shaniAmare


text:
SYS-291 : Fix log endpoint auth

Adds the same auth to log stats endpoint on json-rpc-server as debug endpoints on shardeum validators.

adds rate limiting to debug endpoints (set to 100 calls per 15 min)

@CodiumAI-Agent /review

PR Reviewer Guide 🔍

⏱ Estimated effort to review: 4 🔵🔵🔵🔵⚪
🧪 No relevant tests
🔒 Security concerns
Sensitive information exposure: The PR includes hardcoded sensitive defaults for passphrase and secret_key in src/config.ts. This could lead to unintentional use of these defaults in production, posing a significant security risk.
⚡ Key issues to review
Sensitive InformationThe default passphrase and secret key are hardcoded in the configuration, which could lead to security risks if these defaults are used in production environments.
Error HandlingThe error handling in the saveInterfaceStat function logs the error but does not handle it further, which might lead to unhandled exceptions affecting the application's stability.
Security ConcernThe handleDebugAuth function uses a counter to prevent replay attacks, but it relies on incrementing a variable that could be manipulated or reset, potentially allowing bypass of security checks.

depending on merge order this is going to require changes to the (not yet merged) jest tests #43

@CodiumAI-Agent /review

Persistent review updated to latest commit https://github.com/shardeum/json-rpc-server/commit/a766365150e06cddf1e53bf324b5ced13468f5e4

Persistent review updated to latest commit https://github.com/shardeum/json-rpc-server/commit/6e50e6a7cafc21d80b3e8b540049d22c63aeff8f

source: gharchive/pull-request

authors: CodiumAI-Agent asyed94 chrypnotoad

repo: shardeum/json-rpc-server


text:
ci: Use GITHUB_OUTPUT envvar instead of set-output command

save-state and set-output commands used in GitHub Actions are deprecated and GitHub recommends using environment files.
This PR updates the usage of set-output to $GITHUB_OUTPUT
Instructions for envvar usage from GitHub docs:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter

Thank you

authors: arunsathiya sharkdp

repo: sharkdp/diskus


text:
Update index.html

updated tags

x

x

x

x

x

x

x

x

x

repo: shaunaboyer/intro-html


text:
yo_sheduler not working as root user

I'm trying to use yo_scheduler via JAMF. When I'm on a system, I can run yo_scheduler as the logged in user and I get my notification. I cannot run the scheduler as root via CLI (so it shows up for the logged in user). Scripts in JAMF run as root, so that explains why my policy is failing as well. Is there anything else that I need to do to make the scheduler work, when running this as root?

Hi @vandehey. This has always worked for me from Munki, also running as root. Let me investigate. Let me know if you can give me any further details.

Thanks @sheagcraig . It's hard to say exactly what I was doing in March when I posted this. But I just looked in JAMF, and it looks like I set my policy to cat a script into place, chmod it, then run the script. So a sort of a script within a script is what it looks like on my end.

authors: sheagcraig vandehey

repo: sheagcraig/yo

license_source: bigquery


text:
🛑 North CTopUp is down

In 8da6817, North CTopUp (https://north.speedpayplus.com:50506/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: North CTopUp is back up in 7a8d93e after 1 hour, 56 minutes.


text:
chore: fix test coverage parsing bug

For some reason it seems like nyc v14 is incompatible with node v16/v18/v20. See this CI run as an example:
https://github.com/shelljs/shelljs/actions/runs/5956710281/job/16287478757?pr=1129
This updates nyc to v15 which should fix the issue.
Fixes #1130
Test: nvm use v16.20.2
Test: npm run test-with-coverage

I fixed this in #1139 instead. It's safe to close this.

repo: shelljs/shelljs


text:
Prediction with only one input sentence fails

At the prediction step, if the input file contains only one sentence, it results in an error.  For example, after all the preprocess was applied to the AMR 2.0 (LDC2017T10) data (following the steps in README.md), there will be a preprocessed test data file test.preproc in data/AMR/amr_2.0/ directory.  However, if I removed all the "paragraphs" (that is, a pair of "comments" (including id, snt, and tags etc.) and AMR graph) except for the first paragraph from the file, and then apply the "6. Prediction" phase, the program shows the following error:
Traceback (most recent call last):
  File ".../anaconda/envs/stog/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File ".../anaconda/envs/stog/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File ".../stog/stog/commands/predict.py", line 252, in <module>
    _predict(args)
  File ".../stog/stog/commands/predict.py", line 208, in _predict
    manager.run()
  File ".../stog/stog/commands/predict.py", line 182, in run
    for model_input_instance, result in zip(batch, self._predict_instances(batch)):
  File ".../stog/stog/commands/predict.py", line 143, in _predict_instances
    results = [self._predictor.predict_instance(batch_data[0])]
  File ".../stog/stog/predictors/predictor.py", line 46, in predict_instance
    outputs = self._model.forward_on_instance(instance)
  File ".../stog/stog/models/model.py", line 117, in forward_on_instance
    raise NotImplementedError
NotImplementedError

This error occurs whenever input file with only one AMR paragraph was given to --input-file option of stog.commands.predict module.  Also, if the input file contains more than two paragraphs, this error doesn't seem to be happening.

For some reason, thre's an if statment in stog/commands/predict.py::_predict_instances() (about line 141) that sends the code on a different path if your batch_data size is 1 (ie.. only one sentence).  The stog model doesn't have that code implemented.  I'm not sure if there is still a valid reason for this but it appear to work if you comment-out the if/else.
Here's the revised function....
def _predict_instances(self, batch_data: List[Instance]) -> Iterator[str]:
    # removed - doesn't work for single instance of batch data.
    #if len(batch_data) == 1:
    #    results = [self._predictor.predict_instance(batch_data[0])]
    #else:
    results = self._predictor.predict_batch_instance(batch_data)
    for output in results:
        yield self._predictor.dump_line(output)

authors: TonalidadeHidrica bjascob

repo: sheng-z/stog


text:
Vim 常用操作学习 | 大芒果

https://shenggaogao.github.io/blog/tool/vim/vim操作.html
大芒果的博客

测试

repo: shenggaogao/blog


text:
update renovate.json

[ ] ignore typedoc
[ ] group commitlint

ignoring typedoc because typedoc requires typescript 3.8.x (peer-dependency) and we don't want to bump the peerDependency of dynamo-easy because of that, we don't think it's worth it because new versions of typedoc don't bring essential features

authors: michaelwittwer simonmumenthaler

repo: shiftcode/dynamo-easy

license: mit


text:
Nice

I like the new website design

thx :)

authors: Yedboypl shikoshib

repo: shikoshib/winerr

license: ISC


text:
Sample code - Object detection and tracking

How can I detect objects from a camera and how can I track them from frame to frame? Could you provide me an example code please?

yes, good idea

authors: betrw nombrote

repo: shimat/opencvsharp


text:
It can't work in OS X!!

Hi @shimat .
I check your source codes,and some codes does not support OS X.
So How can I use it for Unity in OS X?
I'm sorry for my poor English.

Sorry but it is difficult to support Unity. Please consider using OpenCV for Unity (https://www.assetstore.unity3d.com/en/#!/content/21088).

authors: TommyTC shimat


text:
[WIP] Add ubuntu binary to NuGet

Try to add CI for Ubuntu (AppVeyor or Travis CI)
Built OpenCV .a files for Ubuntu are fetched from my other repository  https://github.com/shimat/opencv_files/releases
In the case of .NET Core, it seems that there is no problem with the native OpenCvSharpExtern reference without .props
Some bugfixes
Remove cv::estimateRigidTransform because it is deprecated

I don't know how to pack nupkg from "libOpenCvSharpExtern.so" created on Ubuntu VM and "OpenCvSharpExtern.dll" created on Windows VM.
Travis is preferable because it is much much faster than AppVeyor. But Travis does not seem to have artifacts storage (S3 is needed).

windows/x64 test is too slow... zombie process?

todo: move Ubuntu CI from appveyor to travis for speeding up


text:
连接代理，出现乱码

什么网站，开的什么类型代理，有没有报错

转发到burp上就好了

在添加这个修复以后，火狐浏览器通过代理时出现“内容编码错误”

一样出现这种问题

authors: ctrlbbj gdszps longzaizai001 renblog shimmeris

repo: shimmeris/SCFProxy


text:
期待加入UDP部分

包括UDP重传，心跳等

后续会考虑加入UDP ARQ实现的 ：）

authors: dqiang shineframe

repo: shineframe/shineframe


text:
Resolve fatal: detected dubious ownership in repository at '/workspace/source'

Changes
Append git command to add safe.directory of cloned source directory to config, which fixes:
[source-default] 2023/08/14 23:57:02 fatal: detected dubious ownership in repository at '/workspace/source'
#   [source-default] To add an exception for this directory, call:
#   [source-default]
#   [source-default] 	git config --global --add safe.directory /workspace/source (exit code 128)

Fixes https://github.com/shipwright-io/cli/issues/190
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[ ] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Add cloned source directory to git config as safe.directory

/kind

/kind failing-test

repo: shipwright-io/build


text:
refactoring

[ ] Scene Description Layer
[ ] Baking Layer
[ ] Udon Layer (with U# ver1)

Scene Description Layer

Udon Layer

Baking Layer


text:
Update protobuf@7.3

Build protobuf@7.3

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-extensions


text:
Update grpc@8.1

Build grpc@8.1

:beers: @BrewTestBot has triggered a merge.


text:
Update protobuf@7.2

Build protobuf@7.2

:beers: @BrewTestBot has triggered a merge.


text:
Change the theme of the Contact Page and match it with the Home Page Theme

@Abirpal202049 Can I work on this?


text:
[bug] [cosmetic] white bar at bottom of window

There's a white bar in the bottom of the window, which shouldn't be there:

running on Mac OS X 10.11.5
Electron 1.1.0
Node v.6.2.0

Could you please try again, @sg-s?

Hi @shockone
sorry, this didn't fix it for me. I get the same behaviour.
While installing/updating black-screen, I got the following warnings:
npm WARN lifecycle black-screen@0.0.1~preinstall: cannot run in wd %s %s (wd=%s) black-screen@0.0.1 npm prune /code/black-screen
npm WARN lifecycle black-screen@0.0.1~postinstall: cannot run in wd %s %s (wd=%s) black-screen@0.0.1 npm run recompile /code/black-screen
npm WARN tslint@3.10.2 requires a peer of typescript@>=1.7.3 but none was installed.

Would you be able to check in development tools what causes the issue?

sure thing -- can you be more specific as to what and where I should look for? thanks.

HI guys! It's a css overflow-x: scroll property the one that is causing this issue, changing it to auto fix the problems.

You must be using an older version. The latest one doesn't have overflow-x at all. https://github.com/shockone/black-screen/releases

wow! this fixed the problem, but created two new ones:

now there's a white bar on the right
now, i can't move the window anywhere. It's pinned in place, and I can't drag it anywhere. ???

I've created separate issues for those.
https://github.com/shockone/black-screen/issues/626
https://github.com/shockone/black-screen/issues/627

@sg-s, fixed both in v.0.2.7

thanks so much, it's awesome!

authors: ignaciopicun sg-s shockone

repo: shockone/black-screen


text:
use if constexpr in DenseDistance

use if constexpr to replace explicit  template specialization

is get_feature_type() used anywhere in the codebase? I think it might be a good idea to remove it completely no? @vigsterkr

@LiuYuHui disregard my previous comment, for now we are keeping this. I'll merge it

repo: shogun-toolbox/shogun


text:
Replace deprecated phpstan config option

Phpstan suggests replacing deprecated config option checkMissingIterableValueType with missingType.iterableValue  if we want to continue ignoring missing typehints from arrays.
https://phpstan.org/error-identifiers/missingType.iterableValue

Thanks!

authors: ioanok shyim

repo: shopware/recipes


text:
[Github] Fix symfony scheduler bridge

1. Why is this change necessary?
Currently the recommended way to run a message worker is with a command like this:
bin/console messenger:consume scheduler_shopware --time-limit=60

However with the way the ScheduleProvider.php is currently working, all timers will be reset, when the message worker is restarted. Therefore, a job running only every 3600 seconds would never be executed.
Sadly, the corresponding Symfony docs are not very clear about this.
2. What does this change do, exactly?
Making the Schedule stateful will ensure Symfony writes the last execution time to the cache. Thereby it can pick up where it left off, when the worker was killed.
I was thinking about introducing a separate cache pool for the scheduled tasks because object cache is deprecated and you might want to specify different settings (like cache ttl) for your scheduled tasks cache. Let me know how you would like this to be handled.
There is still one major difference in behaviour, when compared to the scheduled-task:run command. Symfony Scheduler will queue the message as many times as it would have run if the messenger wasn't stopped. See the following example for clarification:
Messenger is stopped for 5 minutes.
Job A has an interval of 60 seconds.
Scenario A: Tasks are scheduled by scheduled-task:run
After restarting, the command will notice that the task is overdue and dispatch ONE message.
Scenario B: Tasks are scheduled by messenger:consume scheduler_shopware
After restarting, the transport will notice that the task was last run 5 minutes ago. It will calculate 300s / 60s = 5 and therefore dispatch 5 messages.

I also added a lock to the schedule to ensure it is handled correctly when multiple workers are running.
3. Describe each step to reproduce the issue or behaviour.

Create a scheduled task (set the interval to 60s for example)
Create the corresponding handler. It could for example look like this:

#[AsMessageHandler(handles: ExampleTask::class)]
class ExampleTaskHandler extends ScheduledTaskHandler
{

    public function run(): void
    {
        dump("RUNNING TASK");
    }
}

Run bin/console messenger:consume scheduler_shopware --time-limit=30 (make sure the time limit is shorter than your interval)
Notice that even after running this command multiple times, the RUNNING TASK debug output will never be printed.

[!IMPORTANT]
Make sure to test in prod mode, because the caches are deactivated in dev mode.

4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfill them.

Imported from Github. Please see: https://github.com/shopware/shopware/pull/5456

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39542
[created from NEXT-39542, comment 512047]

[public]

Status Change: In Review

Work on this ticket is complete and is now pending review.
[created from NEXT-39542, comment 512053]

[public]

Status Change: In Progress

Work on this issue has started. It is now being implemented.
[created from NEXT-39542, comment 512052]

[public]

Status Change: Resolved

The ticket has been successfully completed; the solution is implemented and verified.
[created from NEXT-39542, comment 512116]

[public]

FixVersion Change: 6.6.9.0

This issue will be / was solved in Shopware version 6.6.9.0.
[created from NEXT-39542, comment 512117]

repo: shopware/shopware


text:
[BUGFIX] Set lastBacklogId after applying backlog in shop indexer

Description
After applying the Elastic Search backlog, the id of the last processed backlog entry
should be set, because otherwise the backlog entries will be processed
again every time, decreasing indexing performance big time.

Questions
Answers

Why?
See description

BC breaks?
no

Tests exists & pass?
no

Related tickets?

How to test?
./bin/console sw:es:index:populate; mysql -e "SELECT value FROM s_core_config_elements WHERE name='lastBacklogId' "

Requirements met?
yes

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-18509.
Please use this issue to track the state of your pull request.

Any news when this will be merged?

Hi @m-knabe-reply,
i merged your pull request. The changes are available in the next 5.3 version

authors: OliverSkroblin lhwparis m-knabe-reply shopwareBot


text:
adds possibility to use boolean keywords when defining boolean attributes

1. Why is this change necessary?
for better developer experience it should be possible to use the standard boolean keywords true and false, when defining a new article attribute of type boolean, currently one must use 0 or 1
2. What does this change do, exactly?
during parsing of the default value ask it its true other wise its false
3. Describe each step to reproduce the issue or behaviour.

define a new article attribute in  a plugin
set type to boolean
set defaultValue to false
install plugin
there will be a mysql error

4. Please link to the relevant issues (if any).
there is no issue
5. Which documentation changes (if any) need to be made because of this PR?
none
6. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @rene-gust,
can you add more test cases?
E.g.: Empty string, 'true', 'false', '1', '0', NULL, 'NULL'

Hey shopwareBot,
I added the test cases, hope now it looks better

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21303
Please use this issue to track the state of your pull request.

Please merge this PR as it's an easy pick.

thanks for your contribution @rene-gust :+1: :tada: :blue_heart:

authors: FiveDigital mitelg rene-gust shopwareBot


text:
account orders unrelated to showEsd setting

sorry, if there already is a pr, just to be sure...
1. Why is this change necessary?
The showEsd config setting affects whether or not the link to both, esd downloads AND regular orders
are shown in the account sidebar. Previously it would only affect whether the link to the downloads would be shown in the account sidebar, which is the expected behavior.
2. What does this change do, exactly?
Remove the condition on showEsd in the template for the account orders menu entry.
3. Describe each step to reproduce the issue or behaviour.
Enable showEsd, try to access previous orders in storefront account.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-22044
Please use this issue to track the state of your pull request.

thanks for your contribution @dneustadt :+1: :tada: :blue_heart:

authors: dneustadt mitelg shopwareBot


text:
[SW-22002] Fix ambiguous column names for birthday cron

1. Why is this change necessary?
See ticket description.
2. What does this change do, exactly?
Add table prefix for select statement and reorder for legibility.
3. Describe each step to reproduce the issue or behaviour.
See ticket description.
4. Please link to the relevant issues (if any).
SW-22002
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

@pascalheidman-bedarf Thanks for your comment. I've adjusted the code to your suggestion.

Hey @sobyte,
thanks for your contribution.
Anyway, it is best practice to add a prefix to your custom attributes, so plugins don't conflict with each other.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-22213
Please use this issue to track the state of your pull request.

Hi @sobyte, thank you for your contribution! 💙

authors: shopwareBot sobyte soebbing


text:
1.0.2 breaks my instantiation of converter

I recently upgraded the version of Showdown in my webapp from 0.9.x to 1.0.2; my inclusion now reads:
<script
  src="//cdnjs.cloudflare.com/ajax/libs/showdown/1.0.2/showdown.js">
</script>

However, when in my code I called as per http://showdownjs.github.io/showdown/:
var converter = new Showdown.converter();
it ceased working with either (s)howdown or (S)howdown. (S)howdown was not defined; when I changed my code to reference (s)howdown, the error changed to "undefined is not a function", apparently because showdown.converter is not defined.
Did 1.x include API changes that the page is out of sync with? If "var converter = new Showdown.converter();" is out of sync with 1.x, what should I be doing to get a new converter / instead of getting a new converter? If there's not a ready answer, what would be a good older cdnjs URL to revert to?
Thanks,

@JonathanHayward Hum interesting. You just cut us in the middle of our release, where we have component that haven't been updated completed and hence the out of sync issue you're facing. Hang in tight, we'll resolve those bumps shortly.
New instance from 1.x are now using the following construction
var converter = new showdown.Converter();

That being said, I thought we were backward compatible in terms of API. @tivie ?

Thanks! My code runs without crashing now.
Thanks...

@JonathanHayward  v 1.0.0 breaks compatibility in a few key points.
see CHANGELOG.md.
@pdeschen maybe we should add CHANGELOD.md contents to the webpage? make it visible so that people can find it easily?

@tivie Right forget about those bits. I just added a link to the changelog into the Help section of the website. Key here was to at least have the code sample in the "Use It" section to be valid. My bad!

authors: JonathanHayward pdeschen tivie

repo: showdownjs/showdown


text:
Add License

What license is this code under? MIT?

Please consider using an already existing license. In many part of the world your license is certainly not valid (for example the phrase «All rights reserved» it is incontrast with «Redistribution and use in source and [..] are permitted»).
If you want your name on every fork of your files and you want to take advantages on forks code, please consider the great GNU General Public License v3.
If you allow people to create proprietary software with you code (as your current license), use something similar to the MIT license or the Apache 2.0:
The GNU GPL, the Apache 2 and the MIT license have the same disclaimer, so you are not responsible for every problem. All are practically recognized at worldwide level. All grant that "you" are the copyright holder and your name can't be legally deleted.

Hi @valerio-bozzolan as said in the commit log, the license of the repo is the same as Leaflet core which seems to be a BSD license :
https://github.com/Leaflet/Leaflet/blob/master/LICENSE
http://opensource.org/licenses/BSD-2-Clause

authors: brunob kmiyashiro valerio-bozzolan

repo: shramov/leaflet-plugins


text:
Feature to remove any noise from the output

With reference to wordlist generated at https://github.com/shriyanss/subdomains_wordlist/blob/main/wordlist.txt, add a feature, that will remove any UUIDs or hashes from the output
Noise includes:-

Hashes
UUIDs
Random numbers

Feature added in PR https://github.com/shriyanss/subdomain_wordlist_gen/pull/6


text:
change the package name from models

While importing github.com/shubhexists/go-json-db/models doesn't seem appropriate for some reason : ).
I am thinking of making it github.com/shubhexists/go-json-db/go-json-db. A bit memorable for the end user maybe?

Apparently there can't be any hyphens in package names, so gojsondb it is

repo: shubhexists/go-json-db


text:
codeblock render very differently between nextra-theme-blog version 0.1.2 and 0.1.4

Hi,
I tried to bump nextra and nextra-theme-blog version for my site, but my codeblocks render differently.
PR: https://github.com/YikSanChan/site/pull/19
Check codeblock before the bump: https://yiksanchan.com/posts/practical-mlsys-goodreads
Check codeblock after the bump: https://site-git-bump-nextra-yishengdd.vercel.app/posts/practical-mlsys-goodreads
basically, before:

after:

Is there a way to maintain backward compatibility, or some upgrade guide? Thank you!

@shuding Hi Shu, could you please help take a look? Thanks!

I have the same issue with a default/new setup using Vercel

It seems that the THEME configuration  affects the inline style of the prism-code element, making the text black.
https://github.com/shuding/nextra/blob/836156ea7ecc2ee7d23045e082a03072a6f29b4b/packages/nextra-theme-blog/src/mdx-theme.js#L11

I’ll take a look soon!

authors: YikSanChan emptypockets-dev shuding zjhou

repo: shuding/nextra


text:
Optionally disable "/" (forward slash) search shortcut

Hey,
Thanks for nextra, it's very nice, however we're using interactive code editors in our docs, but we cannot write a closing HTML/JSX element because the / key is a shortcut for searching. Is there a way of turning this off in the configuration?

Exactly the same issue here, you beat me to 8 minutes :P
This is my site: https://react-docgen.dev/playground

@james-bowers which code editor are you using?

I am against removing cmd-/ shortcut (it is a bit popular and in the end we can still find a workaround like @danez mentioned)

We're integrating Sandpack inside our internal documentation project made with Nextra.
Even though I set the editor of Sandpack's contenteditable to true the search bar always gets focused when I press the / key.
The Sandpack editor component itself doesn't set the contenteditable attribute, so I had to manually add it using the useEffect hook.
const CustomSandpack = () => {
  const editorRef = useRef(null);
  // ...
  useEffect(() => {
    if (showCode && editorRef.current) {
      editorRef.current.contentEditable = 'true';
    }
  }, []);
  // ...
}

After that when I focused on the editor document.activeElement.isContentEditable become true, however, the search bar still hijacking the / keypress.
Is there any workaround for this?

authors: B2o5T adhrinae danez james-bowers


text:
Change color scheme of dark mode on Docs Theme

Is there a way for me to change the color scheme of dark mode without having to import the whole theme to my project and swap color values? Right now this is the only change I want to make to the theme at all

global.css helped me to figure it out


text:
Do you have plans for long-term maintenance of this project?

I've noticed there haven't been updates for the last two months. Are there plans for long-term maintenance of this project?

This project is maintained, and there are no plans to stop maintaining it. For now, I am busy with other open source projects

Thanks for your explanation! I plan to use it for the documentation of my project.

authors: dimaMachina lausannel


text:
add: jayrkyd

Description
[Include a brief description of the changes you've made]
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
[Describe the changes you've made in detail. Be specific and include any relevant code snippets.]
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

I hope everything looks good and I am able to merge my PR

Fixed changes hopefully everything looks good

@JayRKyd Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and Star the repo to help us grow even further!
Note: Don't make a PR from master branch. Create a new branch for any changes you made.

authors: JayRKyd shyamtawli

repo: shyamtawli/devFind


text:
Rename crate to tsify-next

Rename crate so that it can be published on crates.io

Work is being done on the main branch now.

repo: siefkenj/tsify


text:
Add prehalt and postresume to reg command.

This should allow for at least some basic quick access to read/write CSRs. With a larger program buffer and some scratch RAM it might be possible to do almost anything.

I don't even see it as a complicated state machine. It's basically linearly
moving from one step to the next. Then depending on how you structure it
you have side states to take actions, or the actions are just conditional
in these linear states. There's one way out to an error condition, but
otherwise I think the transitions are all straightforward, using signals
that exist anyway.
But it's been a long time since I did any state machines and I could be
missing something.
Tim
On Thu, Feb 2, 2017 at 12:04 PM, Megan Wachs notifications@github.com
wrote:

@mwachs5 commented on this pull request.
In abstract_commands.xml
https://github.com/sifive/riscv-debug-spec/pull/9:

     <field name="0" bits="31:24" />

   <field name="0" bits="23:22" />

   <field name="prehalt" bits="23">

       When 1, halt the hart before performing the rest of the command.

Ok. For some reason I thought we had this in the previous 0.11
implementation, but if not, simplicity is good. It seems the debugger could
basically do something like this by using normal breakpoint exceptions and
normal code, which is then basically the debug monitor situation.
I need to think about whether this is complicated. I keep thinking that
this command state machine is really complicated, but then I realize that
it is basically what our ROM code was doing before, and all of it can be
done in code vs. hardware (as desired) and I get less freaked out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sifive/riscv-debug-spec/pull/9, or mute the thread
https://github.com/notifications/unsubscribe-auth/APYH7REqfgjt0VZYX0fOEym17hic4NVuks5rYjbkgaJpZM4L1iRa
.

It's not complicated, but it is a state machine, vs something that just dumbly does the single action you ask it to do. If it takes a while for a hart to halt, for example, you now have to introduce hardware that waits for that, vs. just reporting whether the hart is halted or not to the debugger, which is smart enough to understand what it can do once the hart is halted.
I don't think this is really more complicated than the other 'preexec' stuff, but I think I should defer to the other people who are implementing this abstract interface in some other way than having processor execute code (because that's a cheap and easy way of moving through a state machine).

That's fair. Should I merge this into the main spec, or wait until next
week to solicit feedback, after more people have read the core spec?
Tim
On Thu, Feb 2, 2017 at 1:00 PM, Megan Wachs notifications@github.com
wrote:

It's not complicated, but it is a state machine, vs something that just
dumbly does the single action you ask it to do. If it takes a while for a
hart to halt, for example, you now have to introduce hardware that waits
for that, vs. just reporting whether the hart is halted or not to the
debugger, which is smart enough to understand what it can do once the hart
is halted.
I don't think this is really more complicated than the other 'preexec'
stuff, but I think I should defer to the other people who are implementing
this abstract interface in some other way than having processor execute
code (because that's a cheap and easy way of moving through a state
machine).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sifive/riscv-debug-spec/pull/9#issuecomment-277082110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APYH7c8GSLoyGnOI9JGhloepFKvaD2T7ks5rYkPsgaJpZM4L1iRa
.

I don't know... seems like you should put it in otherwise no one would be able to comment on it, but maybe you should ask for feedback on the mailing list as well.
I'll update my picture branch.
What happens if postresume is set and there is an error? Does the thread stall or resume?

I've just pushed this into the main branch.
I decided that any error just aborts the whole operation. That's more
straightforward than some special behavior. It does mean that if something
goes wrong that you're interrupting the target code when you don't intend
to.
Tim
On Thu, Feb 2, 2017 at 6:14 PM, Megan Wachs notifications@github.com
wrote:

I don't know... seems like you should put it in otherwise no one would be
able to comment on it, but maybe you should ask for feedback on the mailing
list as well.
I'll update my picture branch.
What happens if postresume is set and there is an error? Does the thread
stall or resume?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sifive/riscv-debug-spec/pull/9#issuecomment-277146244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APYH7RMIscNzXZg6G42k1sDIMCpVILGRks5rYo2fgaJpZM4L1iRa
.

Hmm I can imagine different scenarios you'd want error to do different things.
Anyway maybe "error behavior" should be a different high-level topic.

On Fri, Feb 3, 2017 at 9:47 AM, Megan Wachs notifications@github.com
wrote:

Hmm I can imagine different scenarios you'd want error to do different
things.

So can I, but how much flexibility do we really need? As you pointed out,
the state machine is already getting larger.

Right. I'd rather figure out whether people are OK with this whole state machine thing at all, then we can discuss errors seperately.

I attempted to make things more clear in
https://github.com/sifive/riscv-debug-spec/commit/e18a68d68ed060c9845e9a04019037875133f2c3
On Fri, Feb 3, 2017 at 9:48 AM, Megan Wachs notifications@github.com
wrote:

@mwachs5 commented on this pull request.
In abstract_commands.xml
https://github.com/sifive/riscv-debug-spec/pull/9#pullrequestreview-20065625
:

     <field name="0" bits="31:24" />

   <field name="0" bits="23:22" />

   <field name="prehalt" bits="23">

       When 1, halt the hart before performing the rest of the command.

       If the hart is already halted, the command may fail.

   </field>

   <field name="postresume" bits="22">

       When 1, resume the hart after performing the rest of the command.

       If the hart is already running, the command may fail.

Actually this doesn't make any sense. It seems that in the common case
both prehalt and postresume would be set. So the hart would be running
already in most situations where you set this, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sifive/riscv-debug-spec/pull/9#pullrequestreview-20065625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APYH7eyUqg5XPbb_0Q6mJXHPlagauHnRks5rY2iEgaJpZM4L1iRa
.

This has been changed to a seperate "Quick Access" command

repo: sifive/riscv-debug-spec


text:
[caat-2697] Add DontCares to undriven ports

Moving things off chisel2 semantics exposed some undriven ports
There may be a better solution. This PR represents the basic sledgehammer approach

Wrong target branch

repo: sifive/testchipip


text:
Filter Events in k8sobjects

Is it possible to filter namespaces in k8objects using regex?
  k8sobjects:
    auth_type: serviceAccount
    objects:
    - mode: watch
      name: events
      namespaces:
      - kube-*
      - openshift-*
      - default

No, it is not possible to use the regex to filter namespaces. You have to either specify individual namespace names or don't specify any namespace to collect from every namespace, and filter objects using a processor within the OTel agent.

Maybe a good enhancement request for the collector, upstream from this project.

The thing is that the kube api server doesn't provide a way to specify the regex. K8sobject receiver is simply utilizing the APIs exposed by the API server. (https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-uris)
So, using a processor to filter based on regex is the best option here.

Please see the recommendation above. Please refer to https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/filterprocessor documentation to set up filters. Closing this issue.

authors: atoulme hvaghani221 louise-zhang

repo: signalfx/splunk-otel-collector-chart


text:
Docs: Clarify relation between role, RAG and agent

Sorry if there is a better place for this kind of request, but I am confused by the new agent feature (using 0.19rc-2) and the relationship to roles and RAG. I am very eager to try this out but the mental model is not clear to me.
Here are a couple of questions that I have:

Can agents do everything a role/rag can do? I.e. if I try to add all functionality I want as agent definitions, can I forget about roles and RAG config? Are there multiple ways to achieve the same things?  Is there ever a use case for combining an agent and a role?
Are all tools global (all or nothing) or can certain tools be allowed to just some roles?
Is llm-functions supposed to be a showcase, a helper tool or "the primary/only way to create agents and tools" for aichat?
It says that "AI Agent = Prompt (Role) + Tools (Function Callings) + Knowndge (RAG)". But where are RAG definied for agents? Is it documents:  - files/doc.pdf in the agent index.yaml-file? (EDIT: Answered, YES)
Can RAG configurations be agent specific in the config file? (for example rag_template). It is also a bit confusing that some of these things should configured in the agent index.yaml and others in the config.yaml.
Is there currently a way to reuse/share tools between agents?

Thank you for a very exciting project!

I've created a hello_world javascript agent now, with a RAG.
I think I have stumbled upon a REPL/CLI inconsistency though:
❯ aichat -a helloworld
helloworld>@rag>

(i.e. starts with rag)
However, if I write aichat -a helloworld "What is the meaning of life" it seems to not use the RAG. I need to use aichat -a helloworld -R rag "What is the meaning of life" for it to use the RAG.
If an agent always has the same RAG, then the -R flag doesn't make sense does it?

AI Agent = Prompt (Role) + Tools (Function Callings) + Knowndge (RAG) is the answer. If you don’t understand something, try it yourself. Agent already contains its own role, how can it combine other roles?

There is only one functions.json file, but each role uses a functions_filter field to select its functions.

AIChat only requires a functions.json file and the existence of the related executable.  Anyone can create their own llm-functions project.

No, the agent's index.yaml file only contains data related to its functionality.  Remember, the agents of llm-functions are versatile and can be used in projects beyond just AIChat.

Unclear. We have not decided yet.

Use aichat -a helloworld <text>... , no need to pass -R rag.

authors: einarpersson sigoden

repo: sigoden/aichat


text:
Race-condition Vulnerability

Race-condition Vulnerability
I knew this vulneraility recentlt, and ask @hyjun0407 to PoC
Thankfully, he gave me video used race-condition vulnerability.
https://github.com/sihyeokpark/dimi6/assets/56220973/b2be0ed0-7973-46ef-9a9f-6fcca2a521c1

I blocked this vulnerability through this commit
https://github.com/sihyeokpark/dimi6/blob/dd110e98bc46447c719218dd4a870fe616451e44/src/app/api/item/buy/route.ts#L23-L26


text:
Question regarding %

How can I get the percentage working?  For example 4%.

% is mod. Making it unary must be tricky.

repo: silentmatt/js-expression-eval


text:
classes are cool

hey so i thought my stuff was better so why not add it

looks good, not quite up to my standards yet

authors: Leaxe silso

repo: silso/special-siteswap-generator


text:
chore: upgrade Node to 16.15.0 and NPM to 8.5.5

also switches to focal ubuntu distro in travis ci config
update node-sass to v7 since previous versions do not support ARM

Coverage remained the same at 0.0% when pulling c3b9cfb2235118a750918a5e90d7cdc5c68389f8 on pbredenberg:pb/upgrade-node-npm into dbdc13a454d8d75f256eb19fdce6c9a2809d7866 on silvermine:master.

@yokuze wanted to get your take on the node-sass upgrade.

@pbredenberg mind rebasing this now that #126 has been merged? Thanks!

@onebytegone done!

authors: coveralls onebytegone pbredenberg

repo: silvermine/videojs-chromecast


text:
Deleting Products via the Catalog deletes from Draft Site, but not from published

To replicate, delete a product via admin/catalog/
The product is deleted from the Catalog (i.e can't be found there), but

shows in the SiteTree as 'Removed from Draft',
remains live.

Expected behaviour: Product would also be removed from the Live site.
I assume the Product page also needs
->deleteFromStage("Live");
but I'm unsure of how to implement this.

Deleting records doesn't seem to be enabled by default. What did you do to enable deletion of records in the catalog-admin?

Sorry, I mean when you 'edit' a Product from the Catalog - the Delete button there:
e.g.
/admin/catalog/Product/EditForm/field/Product/item/1/edit/

Yeah, somethings seems to be going wrong there… although I get an "Unpublish" button instead of the "Delete" button, and the "Delete" button appears at its place once the product has been unpublished. That seems to be fine, but I get some other PHP errors when trying to unpublish/delete via ModelAdmin.
Not sure if this is a problem with shop, or a bug in handling Versioned records in ModelAdmin.

Thanks Roman, I tracked down my issue to being related to the silvershop-discounts module and the versioned-gridfield.
The baseTable function of the versioned-gridfield was returning 'GiftVoucherProduct' for the ClassName instead of just the Product - which was throwing out the 'published' status.
Overriding that function to just return the ClassName has fixed my problem.

I've come across this too.  it's confusing users a bit.
@beeonlinenz  - do you know if the discount module maintainer knows about this?

authors: asecondwill beeonlinenz bummzack

repo: silvershop/silvershop-core


text:
localized file names issue

If I will upload a file with localized name it will have wrong file name for example:
"ûüù.jpg" will be saved as "jpg" which will make file extension undetectable.

I assume you discovered this in 3.x? 4.x will have a similar, yet different problem. :)

yes, that's right. I think file name shall use file ID or some random name in case after removing localized chars file name is empty or transliterated it's security breach right now.

repo: silverstripe/silverstripe-framework


text:
"compound literals are a C99-specific feature" error with C++

When adding the arm/neon.h include to a C++, compiled with Apple clang 12 in macOS using the -pedantic flag, I get the following error:
In file included from /.../simde-no-tests/arm/neon.h:51:
/.../simde-no-tests/arm/neon/ceqz.h:203:49: error: compound literals are a C99-specific feature [-Werror,-Wc99-extensions]
    return simde_vceqq_f16(a, simde_vdupq_n_f16(SIMDE_FLOAT16_VALUE(0.0)));
                                                ^
/.../simde-no-tests/arm/neon/../../simde-f16.h:204:38: note: expanded from macro 'SIMDE_FLOAT16_VALUE'
  #define SIMDE_FLOAT16_VALUE(value) SIMDE_FLOAT16_C(value)
                                     ^
/.../simde-no-tests/arm/neon/../../simde-f16.h:89:35: note: expanded from macro 'SIMDE_FLOAT16_C'
  #define SIMDE_FLOAT16_C(value) ((simde_float16) { HEDLEY_STATIC_CAST(__fp16, (value)) })
                                  ^
1 error generated.

There is a second occurrence of the same error in the same file, which I have not reproduced here.
The error appears to be limited to these two points of this single file (for now). Could this be rewritten to avoid this error? Additionally, would it be interesting to add this scenario to the CI tests to prevent this error in the future?

This was fixed in https://github.com/simd-everywhere/simde/commit/90523a281a67a50b0892364bc35f37a5fbfb7479

authors: dgazzoni mr-c

repo: simd-everywhere/simde


text:
netflix trends

netflix EDA

approved

repo: simhachala/Data-Analysis


text:
Top level tags differ between XML/TeX flavors

I'm trying to sort out the mess I made with #465, #505 and also looking at #502 and one thing that's been bothering be for a while is....

The top level opening tag expected in XML-flavor markup is <sile>.
The top level opening tag expected in TeX-flavor markup is \start{document}.

I don't see any reason these should be different. Am I missing some logic improved by this nomenclature?
If not I propose normalizing them over two stages.

Deprecate whichever one we don't like as much, but still parse for it and give a warning.
Later after a version or two, stop parsing for it.

If, per my comment on #505, we didn't have to worry about guessing the markup flavor and could just assume it based on context, we could not require top level tags at all for the case of includes or other fragments:
SILE.doTexlike = function (doc)
  doc = "\\begin{document}" .. doc .. "\\end{document}"
  SILE.process(SILE.inputs.TeXlike.docToTree(doc))
end

Would become:
SILE.doTexlike = function (doc)
  SILE.process(SILE.inputs.TeXlike.docToTree(doc))
end

And depending on the calling context the parsed tree would just make sense to matter what it started with. Basically it would be a tree appropriate to splice into the calling context.
One of the issues  with requiring a wrapping document tag is that it's not intuitive what extra space will come it. Really this should be fixed in #105, but as an example a TeX-like document for inclusion in another document will bring in leading and trailing space that would have been dropped had it been processed on it's own. See also 53807e6 for a case I had to work around this.

XML flavour should allow arbitrary top-level tags, because SILE is fundamentally a typesetting system for arbitrary XML files.

Just a note that #1052 has significant examples and discussion about what use cases need this to be fixed.

How about this for an idea:

Allow any root tag in both formats.
Setup the classes to handle whatever the root tag is using whatever function they have for it. In this case we're parsing for document in the case of SIL or sile in the case of XML input, but in some cases we also attach attributes to those tags. How this is handled between input formats and fragments (SILE.doTexlike()) is completely inconsistent. In this proposal all options to the root tag would be passed to the classes's root tag handler, something determined by the class not by any preconceived idea about what that tag will be called.

Let's resurrect this old issue.

How about document is the only top-level tag for SIL (as \begin{document} or \begin[... options...]) and its XML flavor (<document ...>)? KISS...

Regarding other XML files, how about all tags are prefixed with the xmlns of the root if set, or the root tag if unset, at least by default? Say my document starts with <TEI.2> or <article xmlns="http://docbook.org/ns/docbook">...
This point would be "a bit" breaking, but is kind of necessary when handling random XML formats that would have tags in their schema overriding SILE commands with different semantics (and likely different attributes even when semantics sort of match by mere luck)

It would make things easier for implementers not to have to "save" commands (which could also depend on loaded packages) that would conflict with the schema, an guess when they have to restore them (which is tricky). Consider DocBook's <info> vs. SILE \info nodes (different semantics) or DocBook's <footnote> (same semantics, but different attributes and different type of content, white space handling is an issue)...
The XML inputter(s) could also have a way to load necessary packages based on that information. In the above example, it could automatically load necessary packages to support the appropriate tag set...

I have dabbled into supporting several XML schemas from the start of my using SILE (TEI dictionary subset, TEI critical apparatus subset, USX, USFX, to name a few) and it's pretty messy with the current XML inputter. Of course I can also replace that with my own inputter and address the above. Yet it feels the wrong way to go...

authors: Omikhleia alerque simoncozens

repo: simoncozens/sile


text:
Fix depwarns on 0.6

Also update CI versions

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b8a63ca). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #5   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?     22
  Branches          ?      0
=======================================
  Hits              ?     22
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

src/StructsOfArrays.jl
100% <100%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-io yuyichao


text:
Feature idea: --always columns

Sometimes you might find that you want to record a value every time for a column even while using the mechanism which uses null for values that have not changed - for this project for example: https://github.com/simonw/scrape-instances-social
Idea: a --always colname option which turns this on (and can be applied multiple times).

Quick prototype of this feature - not fully tested, may not cover all the edge-cases:
diff --git a/git_history/cli.py b/git_history/cli.py
index f3a4c40..975da28 100644
--- a/git_history/cli.py
+++ b/git_history/cli.py
@@ -79,6 +79,13 @@ def cli():
     is_flag=True,
     help="Record full copies in the item_version table, not just the columns that changed since the previous version",
 )
+@click.option(
+    "always_columns",
+    "-a",
+    "--always",
+    multiple=True,
+    help="Record this column in the item_version table even if it has not changed",
+)
 @click.option("ignore", "--ignore", multiple=True, help="Columns to ignore")
 @click.option(
     "csv_",
@@ -130,11 +137,12 @@ def file(
     namespace,
     branch,
     ids,
-    ignore,
     start_at,
     start_after,
     skip_hashes,
     full_versions,
+    always_columns,
+    ignore,
     csv_,
     dialect,
     convert,
@@ -306,7 +316,7 @@ def file(
                     updated_values = {}
                     updated_columns = set()

-                    if item_is_new or item_full_hash_has_changed:
+                    if item_is_new or item_full_hash_has_changed or always_columns:
                         # TODO: delete-me
                         previous_item_hash = item_id_to_last_full_hash.get(item_id)

@@ -349,7 +359,9 @@ def file(
                                     if column in RESERVED_SET:
                                         continue
                                     value = item_flattened.get(column)
-                                    if value != previous_item.get(column):
+                                    if column in always_columns or str(value) != str(
+                                        previous_item.get(column)
+                                    ):
                                         updated_values[column] = value
                                         updated_columns.add(column)
                             else:

repo: simonw/git-history


text:
Fixed bug on main repo for issue#523: non-secure session data not bei…

References this issue https://github.com/simplabs/ember-simple-auth/issues/523
Issue: non-secure session data was being wiped from the store and not restored when the session.restore() method was called.
I altered a test to check its functionality as well.
Only issue i could see happening here is that an event attached to session data being changed might fire twice now.

:+1:

:+1: can we get a beta.3 from this? Thanks!

authors: Kilowhisky kenips marcoow

repo: simplabs/ember-simple-auth


text:
Support Razor UI in class libraries

This is coming in the ASP.Net Core 2.1 update. This feature seems to lend itself well for building modules so I'm hoping this can be added in V2.

Sure. I have upgrade to 2.1-preview1 on another branch. There a some small issues. I think I can go with preview2

What are the problems?
What's the branch?
Can we even try to migrate?

I last time I try (2 - 3 months ago), it's didn't work. I don't remember exactly the issue. I think we should make another try

There is an issue with dynamic loading when using Razor Class Library see https://github.com/thiennn/dynamicLoadingRazorLib/

Please take a look at the prototype at https://github.com/thiennn/dynamicLoadingRazorLib/ if there are no concern. We will apply for SimplCommerce soon

#610

authors: afernandes tdavisjr thiennn

repo: simplcommerce/SimplCommerce


text:
3phase "hybrid" stepper code sinePWM + SVPWM

Thanks to much research and tinkering done with @Copper280z

Thanks so much for contributing this!

repo: simplefoc/Arduino-FOC-drivers


text:
Using newer versions of Electron(9.0.0 and up)

When using later versions of Electron, nothing shows on the screen.

Same issue, tried using older version too

Yeah, it worked with a very old version, nothing showing on the screen. Any suggestions on how to debug?

I could only get it to work on electron version 4. Haven't tested it on versions above, but people say it doesn't work on versions above 9. Would like to get it to work with higher versions so I can keep the electron version up to date.

authors: CleverCarpet KorbsStudio traderjosh

repo: simply-coded/electron-navigation


text:
Metaballs display type

Use Case
As a user with agents that change shape over time, I want to prepare my data to visualize these agents without having to prepare meshes for each agent at each time step.
Acceptance Criteria
Simularium files have a metaballs display type, where positions and radii of metaballs are saved in subpoints for that agent.
Details

add a display type "METABALLS"
save XYZ position and radius for each metaball in the subpoints for the agent, i.e. [metaball1 position X, metaball1 position Y, metaball1 position Z, metaball1 radius, metaball2 position X, metaball2 position Y, metaball2 position Z, metaball2 radius, ...]
also add a viz type "METABALLS"? Or is now a good time to talk about removing viz type since it is redundant with display type?

@toloudis does this sound right? and what do you think about the viz type vs display type issue?

At first glance, I'd say we don't want to add more vis types.  We want to phase that out (e.g. leave it there but never depend on it) and have the display driven by the agent type's display info.
The deeper implication is the following:  if a single agent needs to change its display type, how do we handle it?   I could imagine possibly letting an agent type description having several displaytypes to choose from.  Instead of just saying {displayType:"SPHERE"}, you could have a list [{displayType:"SPHERE"}, {displayType:"OBJ", url:"meshurl"}] and NOW a single particular agent of this type could have a bit of info that lets it flipflop between sphere and obj (the per-agent vistype is now 0 or 1 to select from its agent type's display options).
I would suggest that we prototype the metaballs by generating an all-subpoints version of one of the ABM files, to at least demonstrate converting subpoints to metaball.

I'll show you my implementation in a PR for the viewer and you'll see the display type I created.

https://github.com/simularium/simularium-viewer/pull/261/files#diff-94ea671de54a9e3dcdb0381fad89b6322ec71f112081552ebca4369d9b60f597R9

authors: blairlyons toloudis

repo: simularium/simulariumio


text:
Add support for FilePath for stl models

Currently there is an option FileUrl for import, but FilePath with an absolute local path would be great.

discussed by mail. there is an option using local files located inside wwwroot directory

authors: MarynaChernysheva simutaroman


text:
Add Create React App

https://github.com/tuchk4/awesome-create-react-app
Great tool from facebook team. Used to create React app with zero configuration.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
The list I added

has been around for at least 30 days, +
is the result of hard work and is the best I could possibly produce,
is a non-generated Markdown file in a GitHub repo,
is not a duplicate,
includes a succinct description of the project/theme at the top (example),
includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
contains the awesome badge on the right side of the list heading,
has a Table of Contents section named Contents as the first section,
has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
has contribution guidelines,
doesn't include a Travis badge. Now includes. CI runs awesome but to check broken links
has been checked for inconsistent formatting, spelling, and grammar:

Each link description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it again. The guidelines are not followed.

added contributing.md
update all links to fit AP format

but

not all links have description because in most cases link because link title speaks for itself
has a travis badge. CI runs awesome bot to check broken links

Table of Contents -> Contents is simpler. Although I would agree with @sindresorhus that some of the links could do with a bit more of a description. Such as differentiating the links under https://github.com/tuchk4/awesome-create-react-app#tweaking-configuration

has a travis badge. CI runs awesome bot to check broken links

You can still have that and not have the badge. Travis is mostly just useful for PRs.

ping

authors: davisonio sindresorhus tuchk4

repo: sindresorhus/awesome


text:
Add Esoteric

Add Awesome-Esoteric, a curated list of esoteric programming languages

https://github.com/angrykoala/awesome-esoteric
This list contains esoteric programming languages and resources related to those languages.
It will contain only languages that are considered esoteric (a.k.a. not intended for maintream development) and are in some way interesting and different to other languages of the list. Languages without compiler/interpreter will be accepted as long as are properly documented.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the list project/theme. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell.
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
Not a duplicate.
Includes a succinct description of the project/theme at the top of the readme. (Example)
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Has the Awesome badge on the right side of the list heading,
Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

Each link description starts with an uppercase character and ends with a period.Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Not followed:

Drop all the A / An prefixes in the descriptions.
The repo should have the following GitHub topics set: awesome-list, awesome, list.
Includes a succinct description of the project/theme at the top of the readme.

Changes made according to your feedback @legodude17

Still not followed:

Includes a succinct description of the project/theme at the top of the readme. E.x: "Esoteric languages are..."
Has an appropriate license (like CC0)

@legodude17

Added a small description of what an esoteric language is
Content is already licensed as CC0, I'm not aware if there is a specific way required to add the license

Add a LISENSE file with the CC0 lisense in it. Also, some videos or talks would be cool.

CC licenses (as far as I understand) are not usually added as a LICENSE file in the repository, but as part of the document licensed that way (usually with a license badge), in fact, the repository awesome along with some awesome lists, are licensed this way without LICENSE file, so I don't see how it is required to be added.

I agree, I don't know of any good video or talk about esolangs. I will do some research and find something, however, wouldn't it be an issue/PR to the awesome-esoteric repository better?

@angrykoala ok. What do you mean issue/PR to the repository?

That an issue or pull request to https://github.com/angrykoala/awesome-esoteric may be a better place to discuss the addition videos/talks as it is content of the list itself

Sounds like a good idea. Does @sindresorhus have anything to add?

Any update on this? @sindresorhus @legodude17

In the Languages section, be consistent and only use language, not programming language, in the descriptions. "Programming" is already implied by the context.

I'd like to see some good videos and blog posts linked.
https://www.youtube.com/results?search_query=esoteric+programming+languages&page=&utm_source=opensearch

I'd like to see some links to community resources: Stack Overflow tag, IRC, chat, forums, communities, Reddit, etc. Example: https://github.com/sindresorhus/awesome-electron#community
For example: https://www.reddit.com/r/esolangs/ and https://esolangs.org/wiki/Esolang:Community_portal
http://stackoverflow.com/questions/tagged/esoteric-languages
http://stackoverflow.com/questions/1508581/is-there-any-practical-use-for-an-esoteric-language

Would be cool to have an illustration. Maybe something like https://www.google.co.th/search?q=esoteric+programming+languages&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi-3ML0-brTAhWLLI8KHfNJBCIQ_AUIBigB&biw=1440&bih=799#imgrc=P5bkWSSaGQTnUM: or https://www.google.co.th/search?q=esoteric+programming+languages&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi-3ML0-brTAhWLLI8KHfNJBCIQ_AUIBigB&biw=1440&bih=799#imgrc=mQgCJOfed_cKBM:

@sindresorhus

I Agree, descriptions changed.
There is an issue for this (https://github.com/angrykoala/awesome-esoteric/issues/3) I'm looking for some of the videos, but it takes time to check it is actually useful
Added links to reddit and irc. Stack overflow doesn't seem appropriate as "Community in Esolangs"
If, by illustration you mean a logo, there is also an issue for that (https://github.com/angrykoala/awesome-esoteric/issues/2) I would rather use a custom logo, but a Piet illustration (as a graphical programming language) may be good too

Hi @sindresorhus
Is there still a reason for this PR not being accepted?

Title changed in the awesome list, ¿it is really needed to change the title in the readme?  could it be changed to esolangs rather than "esoteric programming languages"?

Using "Esolang" as title seems better as is shorter than "Esoteric Programming languages" and is solves the ambiguity, title changed in readme.
I tried to change the description aproprietly, but it may be a bit more tuning as "Esoteric" is not anywhere

Any reason left for this not being merged?

Looks good, I've just been busy in real life.

authors: angrykoala legodude17 sindresorhus


text:
Support for images/non text clipboard?

Right now when you read the clipboard, clipboardy errors if the clipboard doesn't have text.
Being able to copy other stuff from the clipboard (like: returning a buffer when the clipboard isn't text) would be an amazing feature to have.

oops #40

repo: sindresorhus/clipboardy


text:
Dockerfile for showing cows on Docker.

Adding Docker usage, because why not?

After cloning the repository Node.js is not needed to see the cows
Entrypoint instruction lets you specific the cow number you want to see.
Can also be pushed to the Docker Hub to get loads more attention for the project.

@Docker may re-tweet this if they think it's fun.
Re-tweet of Raspberry PI on Docker

Building:
$ docker build -t cows .
Sending build context to Docker daemon 550.4 kB
Step 1 : FROM mhart/alpine-node:4
 ---> bc374b5ad19d
Step 2 : RUN mkdir -p /code/
 ---> Running in cc370c2a5960
 ---> f072e7030bbc
Removing intermediate container cc370c2a5960
Step 3 : WORKDIR /code/
 ---> Running in fdd0c7558940
 ---> 6cd088de8d2e
Removing intermediate container fdd0c7558940
Step 4 : ADD package.json ./
 ---> 4e3bed7c9cb4
Removing intermediate container d06c81b7561c
Step 5 : ADD *.js ./
 ---> d4b4933cc1d8
Removing intermediate container 0eb595b378ba
Step 6 : ADD cows.txt ./
 ---> 9db3c5d9c756
Removing intermediate container 2e3f40768607
Step 7 : ENTRYPOINT node show_cow.js
 ---> Running in b11351132f2f
 ---> 81192ba5f26e
Removing intermediate container b11351132f2f
Successfully built 81192ba5f26e

Running it:
$ docker run cows 400
          /)  (\
     .-._((,~~.))_.-,
      `-.   @@   ,-'
        / ,n--n. \
(`'\   ( ( .__. ) )  /`')
 `.'"._ ) `----' (_,"`.'
   "._             _,"
      /            \
     (              )
     (`-.__    __.-')
      \   /`--'\   /
       ) /      \ (
      /._\      /_,\

$ docker run cows 423
               (__)
(__)           (oo)
(oo)      ______\/
-\/    /|      |
| |   * |______|
| |        ||
---        --
Cow Computer

I would suggest creating a docker-cows repository and push that to docker hub.

Hah, cool idea, but as @SamVerschueren said, would be better as a separate repo. I'd be happy to link to it from here :)

That's a shame guys. I figured since you had a .travis.yml file (which uses Docker) you would appreciate this addition. Have you considered adding a paragraph on contribution guideline to the README?

Docker image is named  alexellis2/cows:
$ docker run alexellis2/cows 423
               (__)
(__)           (oo)
(oo)      ______\/
-\/    /|      |
| |   * |______|
| |        ||
---        --
Cow Computer

$ docker run alexellis2/cows 0
Enter cow number between [1-423]

Docker hub link

Have you considered adding a paragraph on contribution guideline to the README?

Nah, it's already visible in the file browser and when you open an issue you get a yellow box telling you to read it.

Docker image is named alexellis2/cows:

Cool. I added a link to it in the readme: https://github.com/sindresorhus/cows/commit/c9ebd517a52acc7a24deb40aeb31a5acffac65b4 :)

$ docker run alexellis2/cows 0
Enter cow number between [1-423]

Maybe return a random cow when no number is supplied.

authors: SamVerschueren alexellis sindresorhus

repo: sindresorhus/cows


text:
Add object-curly-newline rule

http://eslint.org/docs/rules/object-curly-newline
'object-curly-newline': [2, {multiline: true, minProperties: 1}],

The above will enforce putting the contents of objects (everything inside the braces) on a newline unless there's only one property.
The main issues with this rule is that it then enforces that all objects with one property is inline {foo: true}. I think it would make more sense not to enforce anything then, as having it inline or not when only property depends on the situation.
The second issue is that it also applies to object destructuring, where having multiple properties inline is quite ok. const {foo, bar} = unicorn();.

I kind of like being able to specify quick objects on one line when the number of keys is relatively small.
Another case where this is nice and this rule gets in the way IMO is when you create objects with the ES6 same-name shorthand (don't know the name of this)
const foo = 1, bar = 2;
const object = {foo, baz};

I'm not currently a big fan of this rule at the moment.

Official name: Object Literal Property Value Shorthand

I agree with @jfmengels. I have even disabled it on some files at work because of those "issues".

But consistency and readability! :) Isn't readability better than slight convenience? I applied XO on many projects today and a lot of code became clearer when the object properties got on separate lines. That also improves diffing and reduces chances of merge conflicts. That being said, I'm open to reconsider if everyone feels it's wrong, but please try it out a little bit first. It might just be something you need to warm up to.

when the number of keys is relatively small.

How do we enforce "relatively small"?

Can you guys provide some real-world examples of it getting in the way?

Btw, I know it's confusing, but this rule is actually different from the one that enforces multiple properties on new lines. See: https://github.com/sindresorhus/eslint-config-xo/commit/7ff915813633977ae1e2c8c96a1d3dfbffdaa191 and https://github.com/sindresorhus/eslint-config-xo/pull/23

please try it out a little bit first. It might just be something you need to warm up to

Sure, no problem with trying it out.

when the number of keys is relatively small.

How do we enforce "relatively small"? What number is that?

If I had to write the rule now, I'd go for a character length limit (meaning the number of characters between { and } would need to < X), but frankly you'd need a stronger heuristic between number of characters, whether they use literal property value shorthand and whether the properties have long names.
foo({a: 1, b: 2}) // nice and readable IMO (at least readable enough)
foo({
  a: 1,
  b: 2
}) // Wouldn't do it, but I get that it could be considered more readable
foo({
  someProperty: Object.assign(foo, {ok: 2}),
  someProperty2: Object.assign(foo, {ok: 3})
}) // Definitely would do it
foo({a: 1, b: 2, c: 3, d: 4}) // starting to get crowded.
foo({a, b, c, d}) // Reasonably readable
foo({
  a,
  b,
  c,
  d
}) // Definitely overkill

foo({prettyLongPropertyName1, prettyLongPropertyName2}) // readable
foo({
  prettyLongPropertyName1,
  prettyLongPropertyName2
}) // might start considering it, but probably wouldn't do it on my own
foo({prettyLongPropertyName1, prettyLongPropertyName2, prettyLongPropertyName3}) // getting crowded...?
foo({prettyLongPropertyName1: someValue, prettyLongPropertyName2: foo(a, b, c), prettyLongPropertyName3: prettyLongPropertyName3}) // (╯°□°）╯︵ ┻━┻

tl;dr: I'm far from having hard science and hard opinions here. Don't mind trying it out a bit. I'd say that minProperties: 2 would be a nice compromise between these cases.

Let say we allowed two properties. I too have done a lot of foo({a: 1, b: 2}). Don't you think users would abuse it and do this all the time?
foo({someProperty: Object.assign(foo, {ok: 2}),someProperty2: Object.assign(foo, {ok: 3})})

Linting is strict for a reason. Sometimes it affects convenience, but in the long run it's better for everyone. In addition to readability and diffing benefits, I must mention refactoring/changing. It's a lot easier to delete and add properties when they're on separate lines.
For background: I've been thinking about this rule for a long time, as I was unsure about it too, but I've had so many PRs with cluttered code from inline objects that I decided to pull the trigger now.

See https://github.com/eslint/eslint/issues/6211 regarding ignoring object shorthands. I agree it doesn't make sense to put those on separate lines.

I'd say that minProperties: 2 would be a nice compromise between these cases.

The object-property-newline  doesn't support a minProperties option. It's either all or nothing. (Again, not to be confused with object-curly-newline which does support such option.

See eslint/eslint#6211 regarding ignoring object shorthands. I agree it doesn't make sense to put those on separate lines.

Ah cool!

I've had so many PRs with cluttered code

When it comes to linting for submitted PRs, you have a lot more experience and frustration than me ;)
Let's try it out, but I'd love to see eslint/eslint#6211 come to fruition to cut a break for object shorthand.

Ok, I've made it a warning until we decide on something here and https://github.com/eslint/eslint/issues/6211 is done.

It might just be something you need to warm up to.

When I started using XO, I had to change a lot of my previous practices. It's all frustration in the beginning, but at the end, you notice the beauty of all the strict rules. So yes, it's perfectly possible that we/I have to getting used to this rule.

See: https://github.com/eslint/eslint/issues/6251

authors: SamVerschueren jfmengels sindresorhus

repo: sindresorhus/eslint-config-xo


text:
How do I specify the base path for templates?

Hello!
Thank you for this great library!
However, how do I specify the base path for templates? The opts here doesn't have such option.
Thanks!

+1
Right now, gulp-nunjucks uses the base path of the file that was passed to the plugin as the first argument that is passed to the nunjucks.FilesystemLoader constructor. This means that it is impossible to for instance include any files that live in any parent directory.
Maybe allow specifying paths in the compile signature?

@slavafomin You can work around it by passing a nunjucks.Environment in the options to compile like so:
.pipe(gnunjucks.compile({},{
  env: new nunjucks.Environment(new nunjucks.FileSystemLoader('some-base-path'))
}))

This base path will be used for all your require and extend statements.

Yup, that's the correct way to do it, else it falls back to file.base. https://github.com/sindresorhus/gulp-nunjucks/blob/master/index.js#L21.

I've found this module to have better API and more options:
https://github.com/carlosl/gulp-nunjucks-render
And it has path option out of the box. Gonna use it for now.

A slightly cleaner way around this can be achieved by using gulp-base:
.pipe(base('src'))
.pipe(nunjucks.compile())
.pipe(base('src/html'))

If you get
TypeError: nunjucks.FileSystemLoader is not a constructor

That is probably because you imported gulp-nunjucks as nunjucks, like
const nunjucks = require('gulp-nunjucks');

You need to import the original nunjucks like this:
const nunjucks_lib = require('nunjucks');

And usage could be like
gulp.src('some-base-path/file.template')
  .pipe(nunjucks.compile(data,{
    env: new nunjucks_lib.Environment(new nunjucks_lib.FileSystemLoader('some-base-path'))
  }))
  // ...

After around 5 years I've stumbled upon the same problem and had to use another package again :)

After so many hours of investigation I've found out that all I had to do was add a second argument to the src function of gulp:
gulp.src('./docs/homepage/index.html', {base: './docs'})

Because gulp-nunjucks will fallback to this path, and so the ./docs will be the base path and all include statements in the Nunjucks code needs to be changed now to take this into consideration.

authors: kasperisager kevva luckydonald slavafomin wolthers yairEO

repo: sindresorhus/gulp-nunjucks


text:
Add support for async templates

The project I'm working requires using the asynchronous templates which causes this plugin to error.

IssueHunt Summary

Sponsors (Total: $40.00)

 issuehunt ($40.00)

Become a sponsor now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

@issuehunt has funded $40.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

authors: IssueHuntBot software-opal


text:
is parsed as white space

I see there is a test that indicated + should be parsed into white space, however when I test this here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent
+ is encoded as %2B.

Hey @caddac
This did not work in my case. When doing
const urlEncode = encodeURIComponent(location.search)
const urlParsed = query.parse(urlEncode)

it returns

Why does query-string.parse() still convert '+' into ' ' when the decode option is set to false? This isn't handled by decode-uri-component but it's manually done via string manipulation.

Why does query-string.parse() still convert '+' into ' ' when the decode option is set to false? This isn't handled by decode-uri-component but it's manually done via string manipulation.

In my use case, URL has a Base64 query string value, it will be wrong if the + convert to space automatically. Maybe I need to replace back to + for my Base64 query string.

authors: Anusien Bijiabo caddac visualcookie

repo: sindresorhus/query-string


text:
allow default behavior in textareas

I often use the tab key to move on in github forms. I understand the desire to have it indent text, but I'd really like a workaround. I think allowing the user to enter alt + tab to get default behavior is reasonable as long as this doesn't interfere with some other common key binding I'm unfamiliar with. (Totally just tripped up again trying to submit this pull request by hitting tab...)
Definitely open to other ways to enable this...

I should note that submitting is simple enough with ⌘ + enter. It's the other buttons (like Close and comment) that I'd like to navigate to.

How does this work with Windows and Alt + Tab window switching there?

Shift+Tab (also what Sublime uses for alternative tab behavior) would probably be safer. This also needs to be documented.

Updated and documented.

LGTM

authors: hkdobrev kentcdodds sindresorhus

repo: sindresorhus/refined-github


text:
feat: add 'patch' option to automerge

Fixes #537

Thanks for this. It seems to cover everything but I will probably take a day or more to think about if there's anything else needing adding.
One thing to consider - is our current approach to branch naming still valid? If you split both patch and minor PRs then both will try to use the branchName renovate/foo-1.x by default. I need to think if there are an undocumented assumptions we have about branchNames, because grouping by branch name is a pretty important piece of logic for some functionality.

For the current behavior, it seems still valid since I had only modified the automerge behavior.
For #538, it seems there should be an separateMinorReleases option, so that it can select the branch name based on the option, true for something like 1.x (minor) and 1.2.x (patch), false for the current behavior 1.x (minor+patch).

lgtm

authors: ikatyang rarkins

repo: singapore/renovate


text:
Create R API examples

Draft R API examples and request review.

Hi @ambrosejcarr ... Aaron Lun pointed this project out to me and I wanted to let you know that we at Bioconductor are interested and willing to devote effort to achieving interoperability with SingleCellExperiment.  Since we've invested quite a bit of effort in HDF5 as a back end (both for on-disk and for the HSDS API) we are interested in comparative data on effectiveness of TileDB as a back end in this domain.  If you have example data for benchmarking the new API let us know.

@vjcitn that's great to hear! We're thrilled to hear that you're interested in working on this. Our next steps are to add R-based API examples to the draft, solicit feedback, and then create an initial implementation for benchmarking and further iteration.
We'd love to have your critique of the API draft and your help in benchmarking. Would you be interested in getting on a call to hear a bit more about the project goals? If yes please contact me at acarr@chanzuckerberg.com and we can set up a time.

Hi @ambrosejcarr -- just checking in here -- if we can help at the R end in any way, let us know.

Thanks for checking in, and sorry for being a bit quiet. We've been focused organizing work towards demonstrating a proof of concept for this API specification.
Our initial focus is on establishing an effective feedback loop as quickly as possible. We think the way to do that is to enable an in-memory round trip of data from Seurat, Bioconductor, and Scanpy, through the tiledb implementation of the matrix API, and back to a Seurat, Bioconductor, and Scanpy object. We're planning to use the 10x Multiome data as our first test case.
Our approach will be to use TileDB array primitives which will be composed using a C++ API and R and python shims, and aim to have this done by the middle of February.
After we have this work completed, we see at least three ways we want to collaborate:

Would you be interested in implementing the connector(s) between bioconductor and the R API?
Can you give us feedback on the implementation? Are there use cases that the implementation doesn't enable?
We expect to find incompatibilities between the matrix API model and the three tool chains, or between the three toolchains. We plan to post these as issues on the repository as we discover them and would greatly appreciate it if you're interested in participating in discussions to resolve (and ideally align) on these questions.

We also expect to post a draft development roadmap next week, and will welcome your feedback on the sequencing of work. We appreciated the feedback on not leaving multiomics for later during our earlier call and have incorporated that into the plan.
If this sounds good, we'll get back in touch with the roadmap, and from there will probably want to get some meetings on the calendar for an initial demo, and some synchronization calls to follow.

Sounds good to me.  We are definitely able to collaborate in items 1-3.  I am keeping the Bioconductor Technical Advisory Board abreast of this issue stream, so we should have input from multiple highly engaged voices.

The R API of tiledsoma is still under development. We anticipate it will be completed in ~1 month. Once it is finished this conversation can be resumed.

authors: ambrosejcarr pablo-gar vjcitn

repo: single-cell-data/SOMA


text:
[python] Improve resume-mode/schema-only testing [main-old]

The unit-test code on this PR was, erroneously, using a new tempdir on each rewrite pass -- not actually testing rewrite of the same soma directory. This PR fixes that oversight.

Thanks @nguyenv ! :)

repo: single-cell-data/TileDB-SOMA


text:
refactor(storage): refine scan interface of Keyspace

What's changed and what's your intention?
Removed original scan.
Renamed scan_strip_prefix to scan, and all reference to the original scan will refer to this function.
Strip prefix of the returned values of scan_with_start_key.
Please explain IN DETAIL what the changes are in this PR and why they are needed:
Same as above.

Summarize your change (mandatory)
Refractor two functions so that the parameters and returned values of the exposed scan and scan_with_start_key will not contain prefix of the keyspace.

Checklist

[x] I have added necessary unit  tests and integration tests

Refer to a related PR or issue link (optional)
#1989

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.clearlovewei seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Could you please also resolve the conflicts?

Could you please also resolve the conflicts?

done

Thanks for the PR. Please run risedev check for linting and fixing format issues. https://github.com/singularity-data/risingwave/blob/main/CONTRIBUTING.md#lint

Thanks for the PR. Please run risedev check for linting and fixing format issues. https://github.com/singularity-data/risingwave/blob/main/CONTRIBUTING.md#lint

resolved and all check passed, thanks.

Thanks for the PR. Please run risedev check for linting and fixing format issues. https://github.com/singularity-data/risingwave/blob/main/CONTRIBUTING.md#lint

resolved and all check passed, thanks.

Thanks for the PR! Merged.

authors: BugenZhao CLAassistant ClearloveWei hzxa21

repo: singularity-data/risingwave


text:
API: Make config path relative to the config loader

Since I used it tonight for my uni project: There is a way to load a file relatively to the code file. We should use this for the config loader, and so untangle the relative path issue.
import "filepath"
// ... among others

path, err := filepath.Abs("../") // /api folder then, even if called from a test
if err != nil {
	panic(fmt.Errorf("Fatal error config file: %s", err))
}
viper.AddConfigPath(path)

Nice :)

I think this might currently not be needed, as config loading was restructured a while ago. Let's keep it in mind though
Closing for now

authors: geigi jeyemwey paulschwoerer

repo: sipgate/gnt-cc


text:
refine UI

Add Text message and Link

the bias that this model recognize the shape of mouth much, but don't recognize the shape of eyes much

it may be because training data don't include Japanese or any Asian faces (I heard that people in Europe or America express smile with mouth, but not with eyes).

link to the page detect
link to github repository including the source which made face expression detection model

Exception Handling
notify user of following things in Japanese

camera is not usable when it is

Add easy feature

remain displaying the most positive image on browser at another area

Other

modify the text size of the message telling detection result

Additional

recommend to access with https if user is accessing with http


text:
Feature request: Edit mode

How would I save the image with inverted colors?
Or how would I save the resized image?
A button "replace original image" and "add as new image" would be really helpful.
Thank you very much for this plugin but i don't see much value if there is no way to save the edits.
Thank you for consideration.

How would I save the image with inverted colors?
Or how would I save the resized image?
A button "replace original image" and "add as new image" would be really helpful.

I have been working on the feature of saving the changed image (inverted color, resized image, ...), and want to make it more helpful.

Thanks so much 👍

authors: cocoonkid sissilab

repo: sissilab/obsidian-image-toolkit


text:
Display the alternative text of the image as the image title

for example， the image pattern like : ![alternative text](image utl)
Can alternative text be displayed as image captions? like this

Can alternative text be displayed as image captions?

If you choose 'Normal' mode, the 'alternative text' you mentioned will be displayed at the lower-middle position.
But if you choose 'Pin' mode, it won't be displayed. Did you mean that you wanna display it in 'Pin' mode?


text:
DuplicateFileException: Duplicate files copied in APK about.mappings

Error:Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.

com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK about.mappings
File1: /home/ansari/Music/Health-Hive/app/libs/org.eclipse.emf.ecore-2.11.2.v20160208-0816.jar
File2: /home/ansari/Music/Health-Hive/app/libs/org.eclipse.emf.common-2.11.1.v20160208-0816.jar

adding files...............
compile files('libs/org.eclipse.emf.common-2.11.1.v20160208-0816.jar')
compile files('libs/org.eclipse.emf.ecore.xmi-2.11.1.v20160208-0816.jar')
compile files('libs/org.eclipse.emf.ecore-2.11.2.v20160208-0816.jar')
mydependencies...
packagingOptions {
exclude 'META-INF/DEPENDENCIES.txt'
exclude 'META-INF/LICENSE.txt'
exclude 'META-INF/NOTICE.txt'
exclude 'META-INF/NOTICE'
exclude 'META-INF/LICENSE'
exclude 'META-INF/DEPENDENCIES'
exclude 'META-INF/notice.txt'
exclude 'META-INF/license.txt'
exclude 'META-INF/dependencies.txt'
exclude 'META-INF/LGPL2.1'
}

Hard to tell what's going on out of context, but, those (eclipse.emf) jars are MDHT dependencies. They should not be dependencies of this project. If you are using any of the SITE C-CDA validator projects (referenceccdavalidator, etc.) they leverage MDHT and will include those dependencies. So, maybe you are adding them manually, in addtion to using one of the C-CDA projects, creating the duplicate error?

repo: siteadmin/codevalidator-api


text:
missing script: start

As i have clone the repo and made build to run in my local system, It gives error as:-
npm ERR! missing script: start

Just enter webpack command, webpack will start watching for your changes.

repo: sivadass/react-shopping-cart