text:
When scoring a revision, return the version of the model used

Something like this:
{
  "version": 12,
  "scores": {
    "123": {
      "reverted": { ... }
    },
    "456": {
      "reverted": { ... }
    }
}

or maybe
{
  "meta": { "version": 12, "timestamp": ..., "etc": ... },
  "scores": {
    "123": {
      "reverted": { ... }
    },
    "456": {
      "reverted": { ... }
    }
}

This might be useful when debugging user reports.

+1.  This will be critical for secondary caches to make use of too.  For example, the ORES extension for MediaWiki needs to store scores so they can by queried and filtered.  We need to provide a model version at least for that extension to do invalidation in a reasonable way.

The MediaWiki extension is not going to rely on this feature.  We'll run the "check model versions" job once an hour and use the most recent values like a global variable, so even in the worst-case scenario the only negative impact of not including the model version is that we've unnecessarily invalidated the previous hour of results.
Still, this seems like an important enhancement, and easy.  It does enable simple caching in any consuming application.

I like the "meta" version that Helder proposes, but we'd need to also be able to include the info in multi-model mode. Here's what I imagine:
/scores/enwiki?models=damaging|reverted&revids=123456788|123456789&model_info=version|trained|stats

{
  "model_info": {
    "damaging": {
      "version": "0.0.4",
      "trained": 1234567890.00,
      "stats": {
         "auc": 0.8937382,
         "accuracy": 0.8892833
      }
    },
    "goodfaith": {
      "version": "0.0.4",
      "trained": 1234567890.00,
      "stats": {
        "auc": 0.9201838,
        "accuracy": 0.756293
      }
    }
  },
  "scores": {
    "123456789": {
      "damaging": {
        "prediction": false, ...
     },
     "goodfaith": {
       "prediction": true, ...
     }
    },
    "123456788": {
      "damaging": {
        "prediction": true, ...
     },
     "goodfaith": {
       "prediction": true, ...
     }
    }
  }
}

I think that it would then make sense to include the "scores" sub-field in a simple request.  E.g.:
/scores/enwiki/damaging/123456788

{
  "scores": {
    "123456788": {
      "damaging": {
        "prediction": true, ...
     },
    }
  }
}

One thing I am struggling with is changing the output format for ORES.  If we do this, I'd like to do it once since we'll ask our users to update their code when we deploy.  It would also be nice if we could have a transition period.  I imagine implement a function that formats a scoring results based on a version number.  E.g. ?format=v2 and that the default would stay "v1" for some transition period.  This function would look like this:
def format_output(scorer_models, scores, model_info, version="v1"):
    """
    Formats a JSON blob of scores.

    :Parameters:
        scorer_models : `set`
            A set of scorer models used in generating the scores.
        scores : `dict`
            A JSONable dictionary of scores by revision ID and model.
        model_info : `set`
            A set of model information keys that should be includes (e.g. "version",
            "trained" and/or "stats")
        version : `str`
           An output format version to apply.  "v1" excludes any `model_info`.
           "v2" returns a more complex JSON document format that can
           contain `model_info`
    """
    ...

It would return a JSON blob ready for output.  If version is set to "v1", the response format could not contain the meta information.  If the version is set to "v2", the response format will look like the one above.

This was addressed in https://github.com/wiki-ai/ores/pull/121

authors: adamwight halfak he7d3r

repo: wiki-ai/ores


text:
Add an example to demonstrate the use of API:Links module to identify red links on a page

More in response to the question asked here: https://discourse-mediawiki.wmflabs.org/t/data-returned-by-the-query-api-does-not-say-if-a-link-is-a-red-link-or-not/1043.
It would be a cool use case of how API:Links module can also be used as a generator.

Hi @srish I'd like to work on this issue.

Hey @srish can I work on this issue ?

Hello, @srish  I have made a pull request for this issue. Kindly review for corrections. Thanks!

@srish Hello, I am an outreachy applicant. And I wish to work on some issues. But as this issue is taken up by @edyasikpo , I would like to work on different issue.

@srish, I have made a Pull request for this issue. Please review. Thanks.!

#50

hey @srish  can i work on this issue despite other people already submitting their pull requests??

Thanks all for your interest in working on this issue! As @edyasikpo and @SupriyaSupugade are already working on this, please wait till we have other tickets available. In a couple of days, I will be opening more issues that you could look into! Check back again in a few days. Thanks for your patience!
In the future, when there will be more tasks, it might be ideal if you assign yourself to a task first that you are interested in, and then start working on it. That way others know, that the task is already taken up.

@srish isn't it the case that once you comment on the issue you wish to work on and then you start working on it only after it is assigned to you? As I don't see that practice being followed here. Please have a look at it as I commented on this issue as I wanted to work on but others just sent a pull request without the task being assigned to them.

@edyasikpo @SupriyaSupugade @brendajerop I've reviewed your pull requests! I don't like this approach, but I will only be able to accept one person's contribution. Whenever you are done incorporating the feedback, I will take a second look. But, don't worry, I will add more microtasks today.
@hasinifoss Yes, that's exactly how you would do it!
@yatri1609 that's exactly what I'm referring to in https://github.com/wikimedia/MediaWiki-Action-API-Code-Samples/issues/37#issuecomment-466203063.

@srish Thank you! I will send the PR with the above described implementation.

Okay @srish Thanks for the feedback!

@srish Okay. Apologies for the uncouth behaviour

@srish Okay. Apologies for the uncouth behaviour

@hasinifoss As others are already working on this issue, I encourage you to take a look at other microtasks now available: https://phabricator.wikimedia.org/T215682.

@srish, I am Racheal  an outreachy applicant and I would love to contribute on issues you posted 2 days ego here https://phabricator.wikimedia.org/T215682.  but as i can see all tasks have been booked. Is it okay if i pick the one am interested in and contribute or ? how should go about this? am really confused. Thanks

Thanks @brendajerop for your work on this! I've made some corrections in your Sandbox. You can now copy paste Example 2 from https://www.mediawiki.org/wiki/User:Jeropbrenda/Sandbox/API:Links#Example_2:_Fetch_missing_links and add it as a second example here https://www.mediawiki.org/wiki/API:Links!

source: gharchive/issue

authors: KaairaGupta RachealN SupriyaSupugade brendajerop edyasikpo hasinifoss kshitija08 srish yatri1609

license: MIT

license_type: permissive

license_source: github-api


text:
Thermos support

used this mod for a while now (its lovely) but it doesn't play nice with Thermos which I've just updated my 1.7.10 server with. any chance for support? https://github.com/TCPR/Thermos

Can agree, was just about to open an issue about this.

Please add this :D

please do, this sounds like the most amazing mod ever..AE2 takes a gigantic hit on my server, removing it would be sad for my entire player base, and this looks like it could help a ton!
i will gladly donate with thermos support

please make it

Sorry, but It's just too much work to maintain this for the different Server implementations. This mod makes changes to the bytecode, which wreak havoc when combined with servers which also make a lot of changes to the server code. Not to mention other mods which also does bytecode changes.
I have been thinking of maybe re-writing this to use Mixins later on, which would be easier to maintain. But that would most likely be for 1.10+
I have other things going on, so I can't update this. The source code is available, so anyone is free to try fixing this ;)

Was about to add this request as well, makes sense now why the server wouldn't start. SO now I'm using Ptweaks and ClearLagg but still for whatever reason sometimes creating new chunks while exploring kills the server... Running it on a Dell R710 24 core 96gb ram oh well :(

license: mit

license_source: bigquery


text:
SWARM-1711: Fix MP FT fraction to pass TCK.

Motivation
We need to fix MP FT fraction to pass the TCK.
Modifications
MP FT fraction put into operation. Note that we need customized hystrix
properties to pass the bulkhead tests (see also arquillian FaultToleranceExtension).
Result
MP FT TCK should pass.

MeterTest fails on windows machine again:

java.lang.AssertionError: expected:<0.184> but was:<0.2>
at org.eclipse.microprofile.metrics.tck.MeterTest.testRates(MeterTest.java:119)

source: gharchive/pull-request

repo: wildfly-swarm/wildfly-swarm


text:
Nil Pointer Exception when using Ingress without TLS

When installing without defining anything TLS related on an ingress configuration we are getting:
Error: INSTALLATION FAILED: template: wildfly/templates/ingress.yaml:2:4: executing "wildfly/templates/ingress.yaml" at <include "wildfly-common.ingress" (list . "wildfly.metadata.labels")>: error calling include: template: wildfly/charts/wildfly-common/templates/_ingress.yaml:32:4: executing "wildfly-common.ingress" at <include "wildfly-common.util.merge" (append . "wildfly-common.ingress.tpl")>: error calling include: template: wildfly/charts/wildfly-common/templates/_util.yaml:11:22: executing "wildfly-common.util.merge" at <include (index . 2) $top>: error calling include: template: wildfly/charts/wildfly-common/templates/_ingress.yaml:12:6: executing "wildfly-common.ingress.tpl" at <include "wildfly-common.deployment.ingressSecret" .>: error calling include: template: wildfly/charts/wildfly-common/templates/_helpers.tpl:148:14: executing "wildfly-common.deployment.ingressSecret" at <.Values.deploy.ingress.tls.secret>: nil pointer evaluating interface {}.secret
We should check if .Values.deploy.ingress.tls is defined before checking for .Values.deploy.ingress.tls.secret

https://github.com/wildfly/wildfly-charts/pull/136

repo: wildfly/wildfly-charts


text:
[WFCORE-3083] Removing a resource should result in its cap being trac…

…ked as reload-required
https://issues.jboss.org/browse/WFCORE-3083

I added the 'hold' label because I intend to add some tests to this. But I wanted to see what effect this had on the testsuite (i.e. any tests that inadvertently rely on the old broken behavior) so I submitted it early to get the CI run.

repo: wildfly/wildfly-core


text:
[WFCORE-767] Introduce parameters object for SimpleResourceDefinition

As Brian points out on the PR comment referenced in the description of https://issues.jboss.org/browse/WFCORE-767.

Linux Build 1993 is now running using a merge of bada5f7966eeb70cee22034440a958a9e16992d5

Windows Build 1541 is now running using a merge of bada5f7966eeb70cee22034440a958a9e16992d5

Core - Full Integration Build 1133 is now running using a merge of bada5f7966eeb70cee22034440a958a9e16992d5

Windows Build 1541 outcome was SUCCESS using a merge of bada5f7966eeb70cee22034440a958a9e16992d5
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:31

Linux Build 1993 outcome was SUCCESS using a merge of bada5f7966eeb70cee22034440a958a9e16992d5
Summary: Tests passed: 3209, ignored: 71 Build time: 0:26:03

Core - Full Integration Build 1133 outcome was SUCCESS using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8
Summary: Tests passed: 2878, ignored: 377 Build time: 0:49:53

Linux Build 1994 is now running using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8

Windows Build 1542 is now running using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8

Core - Full Integration Build 1134 is now running using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8

Windows Build 1542 outcome was SUCCESS using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:30

Linux Build 1994 outcome was SUCCESS using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8
Summary: Tests passed: 3209, ignored: 71 Build time: 0:25:44

Core - Full Integration Build 1134 outcome was FAILURE using a merge of 376d21561a80182e81867e0e14ab25853a7e04e8
Summary: Tests failed: 1 (1 new), passed: 2876, ignored: 377, muted: 1 Build time: 0:48:59
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testNoAuthSingleSignOn: <no details avaliable>

Maybe this build should be on ResourceDefinition directly so it could be easier to use it in all implementations.

Also while you are here, can you also add builder variant to constructor of PersistentResourceDefinition?

Linux Build 1995 is now running using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686

Core - Full Integration Build 1135 is now running using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686

Windows Build 1543 is now running using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686

Windows Build 1543 outcome was SUCCESS using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:22

Linux Build 1995 outcome was SUCCESS using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686
Summary: Tests passed: 3209, ignored: 71 Build time: 0:25:33

Core - Full Integration Build 1135 outcome was SUCCESS using a merge of 49ef192bbcc4ce9462d8c6dd14903a0b84e34686
Summary: Tests passed: 2877, ignored: 377, muted: 1 Build time: 0:53:25

Windows Build 1545 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Linux Build 1997 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Core - Full Integration Build 1137 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Windows Build 1545 outcome was SUCCESS using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:56

Linux Build 1997 outcome was FAILURE using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Execution timeout (new); tests passed: 2908, ignored: 56; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:09
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 1137 outcome was SUCCESS using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Tests passed: 2878, ignored: 377 Build time: 0:47:36

retest this please

Windows Build 1546 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Linux Build 1998 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Core - Full Integration Build 1139 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Windows Build 1546 outcome was SUCCESS using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:32

Linux Build 1998 outcome was FAILURE using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Execution timeout; tests passed: 2908, ignored: 56; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:02
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 1139 outcome was SUCCESS using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Tests passed: 2877, ignored: 377, muted: 1 Build time: 0:48:54

Linux Build 2002 is now running using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5

Linux Build 2002 outcome was SUCCESS using a merge of fa9cc55dcea22dbac3a82039cbcc0bf31ebab1b5
Summary: Tests passed: 3209, ignored: 71 Build time: 0:25:16

@ctomc This has been merged as-is, if you want to implement your ideas, please open a PR

authors: ctomc kabir wildfly-ci


text:
[WFLY-9707] Remove the JASPI module from the feature pack as this is now in the core feature pack.

:warning: Do not Rebase this PR, the commits in this PR are contained in further topic branches. :warning:
This pull request depends on the WildFly Core PR https://github.com/wildfly/wildfly-core/pull/3407
Thanks for submitting your Pull Request!
Please make sure your PR meets the following requirements:

[ x ] Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
[ x ] Pull Request contains link to the JIRA issue(s)
[ x ] Pull Request contains description of the issue(s)

The JASPI module is required in WildFly Core for the Elytron subsystem to depend on it, this change is to remove it from WildFly as we do not need to define it twice.

[ x ] Pull Request does not include fixes for issues other than the main ticket
[ x ] Attached commits represent units of work and are properly formatted

For bigger changes, major and minor component upgrades make sure your PR also meets following requirements:

[ ] Pull Request requires a change to the documentation
[ ] Documentation have been updated accordingly
[ ] Tests were added to cover changes

For new features ensure as well:

[ ] Analysis was done
[ ] Test Plan has been done
[ ] Tests were verified in advance

If you are not an active contributor of the WildFly project you can request sponsorship by one of the members to help guide you through the process.

Retest this please

@kabir I think we are still missing the related core update for this one.

retest this please

authors: darranl jamezp kabir

repo: wildfly/wildfly


text:
Update READMEs for WildFly 10

Surely needs more love, but at least for a start..

Windows Build 2123 is now running using a merge of 279d675928aa92e035959f53101104b6b7955c5f

Linux with security manager Build 1944 is now running using a merge of 279d675928aa92e035959f53101104b6b7955c5f

Linux Build 7069 is now running using a merge of 279d675928aa92e035959f53101104b6b7955c5f

Linux with security manager Build 1944 outcome was SUCCESS using a merge of 279d675928aa92e035959f53101104b6b7955c5f
Summary: Tests passed: 877, ignored: 284 Build time: 0:06:33

Linux Build 7069 outcome was FAILURE using a merge of 279d675928aa92e035959f53101104b6b7955c5f
Summary: Tests failed: 1 (1 new), passed: 2932, ignored: 354, muted: 1 Build time: 0:46:34
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.remote.suspend.EjbRemoteSuspendTestCase.testSuspendedCallRejected: <no details avaliable>

Windows Build 2123 outcome was SUCCESS using a merge of 279d675928aa92e035959f53101104b6b7955c5f
Summary: Tests passed: 2932, ignored: 354, muted: 2 Build time: 0:48:16

authors: rhusar wildfly-ci


text:
[Bug] Damage calculation simplifying references

Formulas with the Damage field on items, become simplified when the item is opened.
E.g. Formula "(@Classes.solarian.levels)d8" will calculate correctly, even after changing solarian level.
But opening the item the damage formula is in, even just to the description tab, will simplify the formula to current base values
"1d8","2d8" etc.

Fixed!

authors: Iankid TimToxopeus


text:
add support for symfony 3.0

Update version in composer.json to allow symfony/eventdispatcher for 3.x

thank you!

authors: Tschebel willdurand

repo: willdurand/EventDispatcherBehavior


text:
script: Create Meeting

Update issue OP with filled out template

use frontmatter
search issues/PRs for agenda labels

Create Google Doc
Create Google Calendar Event
Create Hangout link
Link issue in YouTube video
When closed, update YouTube with list of attendees?

Future improvements:

If no date in frontmatter, add doodle- data is finalized by new comment

Currently @rvagg uses https://github.com/rvagg/make-node-meeting, which relies on https://github.com/rvagg/node-meeting-agenda

hah- I knew he had SOMETHING! It was on my list to ask him. Thanks... I'll check it out now.

As a note, I couldn't actually get it to work properly when I tried.

repo: williamkapke/hookbot


text:
七牛文件夹不能下载，也不能统计文件夹有多少文件

七牛文件夹不能下载，也不能统计文件夹有多少文件

😅可否把问题描述的清楚一些...

批量下载没法下载文件夹里面的内容，这些文件夹也不能右键查看详情，比如文件夹里面有多少文件。

同一个七牛账号，有一个空间可以选择文件夹，有一个空间不能选择,

你是开发? 这里有个大概的解释.数据加载方式
等我想想有没有更好的方式,解决这个问题.

同一个七牛账号，有一个空间可以选择文件夹，有一个空间不能选择,
这句话没看懂?

我有l两个存储空间，一个空间是正常的一个空间不正常，就是右键文件夹的时候，kashen这个空间就是显示的0文件0B，wangdaijining这个空间就能显示正常的文件夹个数和大小。而且也能直接选择一个文件夹就可以下载。kashen那个空间就不能下载。

哦哦 懂了.  原因就是我上面给你贴的那个.👉数据加载方式
kashen 这个空间文件个数大于5000,会默认开始分页加载,所以按文件夹下载,文件夹属性的功能就废了.
wangdaijining  这个文件个数应该没有超过5000吧? 所以就默认全部加载,这样功能就全部正常了.
大文件这块,目前我也没什么更好的解决方案,真是抱歉~

kashen 9万多文件8G
wangdaijining 7.1万 4.9G
都是超过了5000的哦

你的意思是单文件夹 文件数超过5000还是空间总计呢。

空间总计
七牛有一个接口,可以获取到前一天的空间统计信息.我会根据这个接口返回的文件数来判断是全部加载还是分页加载.
但是这个接口有延迟,他并不是实时的. 如果wangdaijining这个空间不是今天文件数才涨到7w多的话,那就尴尬了😓 🐛...   明天我再好好测一下哈.

都开全部加载呗，哦那客户端的人大概都是想下载文件回来的。慢点就慢点咯，或者给个开关

嗯，好的。随后会加上。多谢 多谢~  😀

大概什么时候能用上呢

争取这2，3天吧.  mac的话明天改改应该就能用上.win的话,需要等我找个win的电脑😂

win的电脑有了么？能用我的电脑打包吗

不好意思 拖了这么久.  已经更新了.   0.3.2-win.exe

authors: ulifuqiang willnewii

repo: willnewii/qiniuClient


text:
added support for global prefix

Adds support for FASTLOG_GLOBAL_PREFIX environment variable
e.g.
process.env.FASTLOG_GLOBAL_PREFIX = '[ipAddress]';
var logger = require('fastlog')('configured', 'error', '${level} [${ category }] <${timestamp}>');
logger.error('You\'ve got a friend in me.');
// [ipAddress] error [configured] <Fri, 05 Dec 2014 02:10:48 GMT> You've got a friend in me.

why this might be useful:
Currently there's no way to ensure that all the logs in your application are using the same prefix.
For instance when you're including a dependency that's logging warnings (assuming that it's using fastlog for that). With the use of FASTLOG_GLOBAL_PREFIX it's easy.

not sure why Travis is failing.
I checked locally and when running node v0.10.48 (the version that travis is using) I get the same error on master.
the error:
/home/travis/build/willwhite/fastlog/node_modules/mocha/node_modules/debug/src/node.js:120
exports.inspectOpts = Object.keys(process.env).filter(key => {
                                                           ^
SyntaxError: Unexpected token >
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/travis/build/willwhite/fastlog/node_modules/mocha/node_modules/debug/src/index.js:9:19)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.

repo: willwhite/fastlog


text:
dns-01 with AzureDNS not working in v2.2.8

Describe the bug
When trying to create a certificate with the current version, the TXT-record is added, but there is only one check against the letsencrypt api, which initially fails as the record did not propagate yet... then the record gets removed without a retry.
Running the same steps with the same config using 2.1.22.x fails too on first try, but continues correctly with a retry after 30 seconds and creates the certificate successfully.
To Reproduce

Run with command line wacs.exe --verbose --validation azure --azuretenantid "xxxx" --azureclientid "xxxx" --azuresubscriptionid "xxxx" --azureresourcegroupname DNS --azurehostedzone mydomain.com ( azure client secret input manual )
Pick menu options M, 2, *.mydomain.com, Enter, 4, 6, 2, and all the rest with the default selected options
See error

Expected behavior
create TXT, check letsencrypt api, fail, retry, success
Log
Log here ( changed domain names and azure specific ids)
https://gist.github.com/erSitzt/c9ce1683c492e28da70994b0f86d1f91
Platform:

OS: [Windows 2022, German]
Version: [e.g. 2.2.8, 64-bit, pluggable]

It looks like PrevalidateDns is set to false (or undefined?) in your config file, causing it to skip the propagation verification before submitting.

@WouterTinus my bad... i had problems because we have the same domain hosted internally and externally and changing DnsServers did not work when i first tried it.
Now it works, not sure if i had another problem interfering here :)
thanks

authors: WouterTinus erSitzt

repo: win-acme/win-acme


text:
[Bug] @apply variant won't work in react project with less css preprocessor enabled.

Bug description
@apply variant won't work in react project with less css preprocessor enabled.
How to reproduce
check reproduction repo: https://github.com/Ynewtime/vite-react-ts-with-less

yarn create @vitejs/app
yarn install -D less
follow the install guide of https://github.com/windicss/vite-plugin-windicss#install
change src/App.css to App.less and add test class with @apply variant
use test class in src/App.tsx

More information
I've tested with sass and postcss-nesting, both work well with @apply variant, it seems just less could not.

Yeah, sorry I totally forget about less. It would work with v0.4.11 now.

authors: Ynewtime antfu

repo: windicss/vite-plugin-windicss


text:
To get the last version of windi - do I have to wait for a new version of this library?

I see the underlying windicss-webpack-plugin reference the latest windi, but when I try to upgrade with:
vue upgrade

or
yarn upgrade-interactive --latest

and both do not offer to upgrade the windicss sub-dependency.

Sorry for the delay, dependencies are updated in 1.1.4

thanks!

repo: windicss/vue-cli-plugin-windicss


text:
Weird coloring and @apply issues in SCSS files (or in Vue SFCs)

Here's my repo, you can see that I have src/stylesheets/scrollbar.scss that is imported within a root.scss file in the same directory, and I import that root in my nuxt.config.js > css. When I tried using Windi classes (with @apply), it didn't work in those files (you can check blame to see how I switched to variables instead). This only happens for external SCSS files. I tried some methods, putting that directory in includes of windi.config.js but no luck there either.
There's also another issue with @apply in both external files and in SFC style tags. They're not colored, which makes it look like it's not a part of the code. I don't think it's because of my VSC theme (I use Dracula) because, before the switch from Tailwind's official extension, they were all colored with no problems.

You see that the coloring of @apply is missing and all classes look weird. You can see here how it was when using Tailwind's extension).
🌟 One idea!
One thing I always cried about Tailwind's extension is that it wasn't able to sort classes in @apply. It's not important but it'd be amazing to see this in Windi's extension! If this is possible, I can create a different issue for this!

can you try to add following in your VS Code Editor Settings
  "windicss.includeLanguages": {
    "scss": "css",
  },

can you try to add following in your VS Code Editor Settings
  "windicss.includeLanguages": {
    "scss": "css",
  },

Nope, didn't work.

Yep, it looks fine in SFCs <style> tags and it's now working in my .scss files too. I can use classes but seems like colours are still missing from there. Is it supposed to be like this?

@eggsy if you talk about issue in functionality of actual usage it might be wrong repo to have this issue. If you are talking about bug in VS Code Extension it is correct. Not sure what you mean?

ok, so maybe please open for the second part an additional issue. It confused me sorry

/cc @voorjaar not sure if that is indented, but it seems .scss files are not quite working yet

@eggsy you checked the includeLanguages setting?
example:
"windicss.includeLanguages": {
  "ruest": "html", // css, js
  "svelte": {
    "type": "css"
  },
  "javascriptreact": {
    "type": "js",
    "patterns": ["@apply\s+\S+$", "..." ],
  },
}

@alexanderniebuhr didn't fix it. I don't know if that's the right config though, it says javascriptreact all I'm trying to achieve is get @applys coloured in .scss files.

It's just an example config, cause that setting supports more stuff

v0.16.6 should fix all problems, try it please.

Welp, they work as expected now! Even in commented lines, they are highlighted (might be a bug of my theme or I don't know but sure!). It'd be great if that's fixed in the next patch though 😅.

just going to close since there was no much activity lately, if some issue still exists please reopen a new issue

authors: alexanderniebuhr eggsy voorjaar

repo: windicss/windicss-intellisense


text:
无法编译通过

H:\project\src\ai\windosx\face-engine\cmd>go build -o test github.com/windosx/face-engine/cmd
github.com/windosx/face-engine
C:/TDM-GCC-64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -larcsoft_face_engine
collect2.exe: error: ld returned 1 exit status

@qinjinze 虹软的库文件是否放到gcc目录下的lib中了？

authors: qinjinze windosx

repo: windosx/face-engine


text:
Unable to install via backend

Winter CMS Build
1.1
PHP Version
7.4
Database engine
MySQL/MariaDB
Plugins installed
No response
Issue description
Trying to install a new theme (any theme) while testing Winter, I keep getting this error message:
Update failed
File from server is corrupt.

The "popup" is displayed, and things look like they're downloading. But very briefly after that, the error message is displayed.
It doesn't matter which theme I try to download.
I see no errors in the php.log file (I have error_reporting set to E_ALL, and Winter is in debug mode).
Steps to replicate

Enter backend
Go to Updates & Plugins
Choose themes
Pick any theme

Workaround
No response

This is not something we can control as of yet. The Backend of Winter still uses October's marketplace for downloading plugins and themes, and can break at any moment on the whims of the October maintainers.
Once our new Marketplace is online, we'll switch over these functions to use our Marketplace instead.

repo: wintercms/winter


text:
dispatch->delay Carbon\Exceptions\UnknownGetterException: Unknown getter 'timezone_type'

Winter CMS Build
1.2
PHP Version
8.1
Database engine
MySQL/MariaDB
Plugins installed
wikimedia/composer-merge-plugin
Issue description
The interesting thing is that the exception is shown only when debugging. Also the code inside dispatch is executed right away. It looks like adding delayed time does not work.
Stacktrace:
Carbon\Carbon->get (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/nesbot/carbon/src/Carbon/Traits/Date.php:1079)
Carbon\Carbon->__get (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/nesbot/carbon/src/Carbon/Traits/Date.php:822)
Carbon\Carbon->__isset (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/nesbot/carbon/src/Carbon/Traits/Date.php:1093)
Carbon\Carbon->__serialize (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/nesbot/carbon/src/Carbon/Traits/Serialization.php:149)
serialize (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/Queue.php:158)
Illuminate\Queue\Queue->createObjectPayload (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/Queue.php:158)
Illuminate\Queue\Queue->createPayloadArray (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/Queue.php:127)
Illuminate\Queue\Queue->createPayload (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/Queue.php:105)
Illuminate\Queue\SyncQueue->push (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/SyncQueue.php:38)
Illuminate\Queue\SyncQueue->later (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Queue/SyncQueue.php:147)
Illuminate\Bus\Dispatcher->pushCommandToQueue (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php:250)
Illuminate\Bus\Dispatcher->dispatchToQueue (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php:229)
Illuminate\Bus\Dispatcher->dispatch (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php:77)
Illuminate\Foundation\Bus\PendingDispatch->__destruct (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Foundation/Bus/PendingDispatch.php:193)
FriendLee\Rdart\Api\Controllers\ApplicationController->code (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/plugins/friendlee/rdart/api/controllers/ApplicationController.php:29)
Illuminate\Routing\Controller->callAction (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Controller.php:54)
Illuminate\Routing\ControllerDispatcher->dispatch (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php:43)
Illuminate\Routing\Route->runController (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php:260)
Illuminate\Routing\Route->run (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php:205)
Illuminate\Routing\Router->Illuminate\Routing\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php:797-799} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php:798)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:139-145} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:141)
FriendLee\Rdart\Api\Middleware\CorsMiddleware->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/plugins/friendlee/rdart/api/middleware/CorsMiddleware.php:12)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:156-187} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:180)
FriendLee\Rdart\Api\Middleware\ExceptionsMiddleware->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/plugins/friendlee/rdart/api/middleware/ExceptionsMiddleware.php:22)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:156-187} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:180)
Illuminate\Pipeline\Pipeline->then (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:116)
Illuminate\Routing\Router->runRouteWithinStack (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php:799)
Illuminate\Routing\Router->runRoute (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php:776)
Illuminate\Routing\Router->dispatchToRoute (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php:740)
Winter\Storm\Router\CoreRouter->dispatch (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/winter/storm/src/Router/CoreRouter.php:20)
Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:187-191} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:190)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:139-145} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:141)
Illuminate\Foundation\Http\Middleware\PreventRequestsDuringMaintenance->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php:86)
Winter\Storm\Foundation\Http\Middleware\CheckForMaintenanceMode->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/winter/storm/src/Foundation/Http/Middleware/CheckForMaintenanceMode.php:25)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:156-187} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:180)
Winter\Storm\Foundation\Http\Middleware\CheckForTrustedProxies->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/winter/storm/src/Foundation/Http/Middleware/CheckForTrustedProxies.php:56)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:156-187} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:180)
Winter\Storm\Http\Middleware\TrustHosts->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/winter/storm/src/Http/Middleware/TrustHosts.php:46)
Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure:/var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:156-187} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:180)
Illuminate\Pipeline\Pipeline->then (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:116)
Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:165)
Illuminate\Foundation\Http\Kernel->handle (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:134)
{main} (/home/vogdb/workspace/friendlee/rdart/rdart-back/html/index.php:43)

Steps to replicate
I've put this code inside my controller:
        dispatch(function () {
            echo 'hello';
        })->delay(Carbon::now()->addMinutes(5));

Workaround
No response

It's because I have sync for my Queue configuration. Does not happen with database. Closing the issue. Sorry to bother/


text:
Add composer replace config.

@bennothommo @LukeTowers should we go ahead with this and suggest to people having trouble to tweak their merge plugin config?

repo: wintercms/wn-translate-plugin


text:
webpack-encore - not compatible

I tried to implement this plugin in symfony(webpack encore).
but it reflects below issue:
WAIT  Compiling...                                                                                12:58:04
ERROR  Failed to compile with 7 errors                                                                                12:58:09
These relative modules were not found:

./Buffer in ./node_modules/protip/protip.min.js
./Class in ./node_modules/protip/protip.min.js
./Constants in ./node_modules/protip/protip.min.js
./GravityParser in ./node_modules/protip/protip.min.js
./GravityTester in ./node_modules/protip/protip.min.js
./Item in ./node_modules/protip/protip.min.js
./PositionCalculator in ./node_modules/protip/protip.min.js

this to very urgent,  plzzzzzz sort it out.

The minfied file is already browser ready, the whole thing is not meant to be imported as a module. If you want to do that, you can try to import from src as:
import 'protip/src/Plugin'

Not tested tho.

worked, thanks.
But other thing is I am unable to find examples of use of your plugin in different variations.
I understand you did effort to make this example tool to test the requirement on page "http://protip.rocks/"
but, that will be helpful if you can provide the script compiled from that tool on your home page.
for e.g.   https://coolcarousels.frebsite.nl/c/67/  . if you click ok on [...] , you will get example code for it.

currently I am trying to plug your protip into old project without making much noice.
like:
 delete

authors: seetpalsingh wintercounter

repo: wintercounter/Protip


text:
fix(clamav): Switch to official clamav image

I chose the _base version of the image because the previously used MailU version didn't include a database either.
Fixes #325
Fixes #432

@desaintmartin Did you have a chance to look at this? (Mentioning you since you seemed interested in #325)

That's nice, thanks for the contribution! Is there anything to know when changing to upstream?

@desaintmartin Not that I am aware of, no. As you can see, the UID of the clamav user in the image changes. But at least in our use case, everything else worked as expected.
Something we experienced with both MailU's and upstream's _base images - since they don't contain any database - were problems with the CDN's rate limit. Especially in combination with the HPA (which is enabled by default), the rate limit was quickly exhausted, causing the pods failing to start at all. We solved that by using a caching proxy (see #458 for the necessary changes to the chart). But maybe the HPA shouldn't be enabled by default, since frequently starting new pods facilitates early exhaustion of the rate limit.

It wasn't, thanks for noticing!
As I understand the docs, that option is only relevant when freshclam is started as root (not the case by default) and in that case the user given has to have write access to the database directory. Since (in the default security context) that directory is owned by group 101, the setting should probably default to user 100 as well (although it doesn't take effect in default config anyway)

I was worried because of #322   which implies there could be issues when a PVC is involved. They had to give the pod security context the fsGroup of 2000, I assume to match the value in freshclam
We're about to rollout an install using Flux to AKS and I was double checking issues and settings. This got me worried enough that we decided we were going to try and override the freshclam conf defaults to use a matching GID, but unclear if it's really going to be necessary.

authors: desaintmartin jplitza pinkfloydx33

repo: wiremind/wiremind-helm-charts


text:
Several EGP elements dissapear permanently if not updated constantly

Please note: This issue tracker is for bug reports
If your issue isn't a bug report, or if you are unsure whether it's a bug, please go to our discord channel instead at https://discord.gg/H8UKY3Y
If you are confident your issue is a bug, please fill in as much information as you can below.
Describe the bug
linestrips, polyoutlines, triangleoutlines, and lines when parented to a 3d tracker all delete themselves when you look away from them
To Reproduce
Steps to reproduce the behavior:
parent any of these elements to a 3d tracker, look more than 120 degrees away, and away indeed it goes
Expected behavior
they disappear permanently
Screenshots
just imagine a screenshot where first the triangle is there and then it isnt, took me like an hour and a half before i realized what was happening and just used a circle outline

Looked into it, it seems the vertices are being set to an impossible number from moving so far off the screen. Not sure how to remedy this best, maybe just clamp to a really high number.

authors: Ally-for-Hire Denneisk

repo: wiremod/wire


text:
Don't accept unmatched string delimiters in HLZASM

Now "Foo' isn't a valid string constant, but "isn't" is.
Fixes #1011

@suunrider would you be able to test this? I won't have a computer at my house until Saturday.

The string "Foo' errors with Newline in string constant, also the editor highlights it like a normal string.

@suunrider okay, I've changed the error message for "Foo' and the editor should highlight it in red. (There seems to be no proper syntax error highlighting colour?)

There aren't any syntax checks in the zcpu editor, so doesn't "notfound" color exists. Just add ["notfound"] = { Color(240, 96, 96), false}, to the colors (copied from e2).
The error messages work properly now :+1: .

Whoops, I didn't realise the two syntax highlighters had their own syntax colour tables. Fixed.

The error highlighting ain't working: "Foo gets highlighted as string

Okay, I'll wait until I have a computer I can run and test my code on. Thanks for your help.

In most editors I've used "foo would be highlighted as a string. (I don't know the reason - maybe so they don't change colour when you finish typing them)

If it's meant to be like C then 'A' should be the number 65 (ASCII code of A) rather than a string.

It already does that (see hc_tokenizer.lua#L288).

Why did you change the C-Style operators to lua ones?

Because my editor doesn't understand them, and those particular ones were causing it to show errors down the entire rest of the file, and we have a rule that the C-style operators shouldn't be used in our code. So I figured it'd be better to just sneak in that unrelated improvement to the codebase while I'm there :wink:

Oh, some codestyle guidelines would be useful then since there are many different coding styles in wiremod

#350 was the closest we got, but you're right that it would be worth having some documentation somewhere.

Once ported the HL-ZASM Compiler out of gmod: https://github.com/suunrider/hlzasm. Uploaded it to github, i thought it maybe would be useful for you. I don't have a zcpu emulator yet, so it's only useful to check if something parses.

authors: AbigailBuccaneer immibis suunrider


text:
Added "lastFuncError()" e2 function.

[Added] "lastFuncError()" to "try call" a string function. First you call
it like "test"(). Then use this function to get the error message (or ""
if no errors). Resolves #926
Interested to know if this is an appropriate solution.

funcError should be separate for each e2.

Thanks! Rookie mistake ;)

You said you wanted a functionExists thing, though. That's totally possible; what happened to that?

This is pretty much the same. And easier to make, cheaper to do. So I went with this. But it is less beautiful.

I'm in favor of a delegate type
I was under the impression that already exists.

@TomyLobo because we didn't have delegates, calling strings was a quick fix

you mean adding a new kind of operator to the parser and compiler was easier than just adding a new data type with a call method?

Yes because we don't have call methods so that'd be even more work

dude
F:call(...) and you're done

I assumed you meant to add a function type and then registerOperator( "call", "f", ... )
I don't remember the exact reason that callable strings were added, but it had something to do with proper function types being a pain to get working, I dunno. If you can do it, go ahead.

Could have been S:call(...) just as well

authors: Divran Measuring TomyLobo thegrb93


text:
udev: add specific tag to WB-internal modems

решили привязать нашему модему специальный тег, чтобы потом дёргать модем по нему
предлагаю тег "wbc"
интересно, что udev имеет доступ к of_compatible и of_name из коробки
проверить можно mmcli -m wbc --set-primary-sim-slot=1

Я, правда, не уверен в названии wbc. Может, просто wb?

Я бы не стал, мало ли вдруг у нас какие-то внешние модемы появятся. wbc хорошо тем, что на модеме так написано и везде в коде встречается. Можно было бы wb_internal сделать или что-то такое, но я не очень понимаю, зачем.
Тут ещё вопрос, как бы сделать так, чтобы пользователю без документации было понятно, что вписать для того, чтобы обратиться к нашему модему; может, обёртку для mmcli, которая по умолчанию будет подставлять -m wbc? И ещё вопрос, что будет выводить mmcli -L, будет ли там написано, что наш модем называется wbc

authors: vdromanov webconn

repo: wirenboard/wb-configs


text:
Fix configs links creation

Fix configs links creation

@evgeny-boger done


text:
Add the ssh port forwarding for the wbdev

Добавил проброс ssh порта в докер контейнер.
Для включения нужно в переменную WBDEV_SSH_PORT_FORWARDING установить значение локального порта с которого осуществляется проброс на 22й порт контейнера.
Опция полезна для отладки и разработки.

Глупый вопрос - а ты не пробовал подключаться через сеть docker (172.17.0.0/24)? Там не нужен проброс портов, можно напрямую к контейнеру обращаться к нужным портам. Ещё по идее можно как-то заставить резолвиться hostname у docker-контейнеров.

Закрываю за невостребованностью

authors: rkochkin webconn

repo: wirenboard/wirenboard


text:
Update sbt to 1.9.2

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

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

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

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #147.

repo: wiringbits/my-photo-timeline


text:
Should we add docs on using Bun as runtime?

As you know, Bun has existed for quite a while now.
I tested it recently with Astro and it works fine. Should we document this somewhere?
Willing to pick this up for sure!

But I did notice that the @astrojs/image integration does not work!

Interesting. How would you imagine documenting it? Is it effectively a replacement for npm/pnpm/Yarn so e.g. we’d add bun i astro anywhere we show  npm i astro or is it more complicated than that?

At this moment, I feel like it's indeed something like 'bun install' and 'bun run ...'. But maybe there's more here then we see at first sight, for example, what with 'npx create-astro' and such.
I'll take a deeper look into this tomorrow and gather some more thoughts!
I'll update this issue sometime tomorrow!

Thanks! If that were the case, that’s a pretty big change to go through updating all our package manager prompts to also include bun — especially if it turns out to still be a bit experimental and not support everything (like the image integration). So definitely something to chat through and figure out what’s best.

Just pinging this for freshness... and wondering whether this could be a good recipe as an experiment, until we figure out whether it seems like something stable enough for more general purpose?

Yes, I definitely think this would fit better in the recipes section than an overall page! Want me to write this out?
In the meantime, I verified that Bun is very usable with astro, except for the creation of a project, but we can mention that in docs for sure!

@ElianCodes Would be happy to have this in docs if you're up for writing it out!  🙌

authors: ElianCodes delucis sarah11918

repo: withastro/docs


text:
Document getStaticPaths in non-HTML pages

Non-HTML pages support exporting a getStaticPaths function just like .astro dynamic routes do, but we don’t currently document it. This should at least be mentioned in the non-HTML section of the Pages guide and probably deserves a comment in the getStaticPaths reference and Dynamic routes docs.
Particular gotcha to mention:
If the file route is src/pages/[api].json.ts, the api param returned by getStaticPaths need to include .json. Not sure if that’s intended or a bug — we should check with core. Here’s an example:
import type { APIRoute } from 'astro';

export const get: APIRoute = async ({ params }}) => {
  return {
    body: JSON.stringify({
      path: params.api,
    }),
  };
};

export function getStaticPaths() {
  return [
    { params: { api: 'a.json' } }, // ✅ works => outputs '/a.json'
    { params: { api: 'b' } },      // ❌ breaks => outputs '/b'
  ];
}

(I guess under the hood this is essentially working as if the .json part of the filename is not there.)

Closing in favour of tackling everything together in #760


text:
i18n(ja): Update cli-reference.mdx

What kind of changes does this PR include?

New or updated content
Translated content

Description

Update cli-reference.mdx.

LGTM👍


text:
i18n(zh-cn): Update guides/cms/keystatic.mdx

Description (required)
Update guides/cms/keystatic.mdx
Upstream PR: #7067
Related issues & labels (optional)

Closes #
Suggested label:

So fast


text:
i18n(ru): Add studio.mdx translation

Description
This PR adds the Russian translation of the studio.mdx page, addressing missing content identified by the Translation Tracker.

@yanthomasdev Yan, I'll fix the link shortly.


text:
Converted bullet points from Importing Markdown section into subsections. Fixes #669

What kind of changes does this PR include?

[x] Minor content fixes (broken links, typos, etc.)
[ ] New or updated content
[ ] Translated content
[ ] Changes to the docs site code
[ ] Something else!

Description

What does this PR change? Give us a brief description.

Converted bullet points from Importing Markdown section into subsections. Fixes #669

Did you change something visual? A before/after screenshot can be helpful.

N/A

Thanks, @felixsanz ! This is looking much cleaner!
@delucis @aFuzzyBear - With <h3>'s, each of these exported properties becomes their own entry in the right sidebar. What do we think about this? I'm not sure whether we want this, especially given what it would do on mobile.
One option would be to add something like ### Exported Properties and then the individual properties themselves can all become <h4> and would NOT show up in the right sidebar. Thoughts?

@sarah11918 @delucis Done!

this does make it look alot cleaner, wanna check the toc component on desktop when I'm back on,

this does make it look alot cleaner, wanna check the toc component on desktop when I'm back on,

i'm on desktop, they don't show now:

authors: aFuzzyBear felixsanz sarah11918


text:
ci: update reference docs

This PR is auto-generated by a nightly GitHub action to update the reference docs from source code in withastro/astro.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/configuration-reference.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


text:
Routed price feed: ELON/USD

As requested by Annex.
Depends on #109.

Deployed and verified on Cronos Testnet:

Price-ELON/USD-9: 0x77A87f3A0f71A69D32E59A8ebBa34aBD90EB8cd9

authors: aesedepece guidiaz

repo: witnet/witnet-price-feeds


text:
Use jest.setTimeout instead of jasmine timeout

Summary
Replace jasmine.DEFAULT_TIMEOUT_INTERVAL with jest.setTimeout() in Jest Guide.
Since jest@20 or so jest.setTimeout is available, instead of jasmine-specific timeout constant. I think it's worth using official APIs when available.

Can you please rebase the branch (or master into it), I want to make sure everything is green on Travis

The build failure is unrelated, but we can wait until you resolve that, no rush :)

builds are green again, please rebase your PR.

authors: rotemmiz thymikee

repo: wix/detox


text:
how to set 'native' option to true?

The docs for using react-templates with react-native specify that:

In order to use React Templates for React Native you should set the native option to true.

Where is this option set?

by looking at the source, it's --native.

Thanks again @nippur72
Can you post a link to the source?
How would I use that option which looks like a shell command option?

So I figured out this --native argument has to be used with the CLI although when compiling the following template with rt test.rt --native:
<View>
    <ListView dataSource="{this.state.dataSource}">
        <Row>
            <Text>{rowData}</Text>
        </Row>
    </ListView>
</View>

I get:
var testRT = function () {
    return React.createElement(View, {}, React.createElement(ListView, { 'dataSource': this.state.dataSource }, React.createElement(Row, {}, React.createElement(Text, {}, rowData))));
};

instead of  what the docs suggest I should get:
'use strict';
var React = require('react-native');
var _ = require('lodash');
function renderRow1(rowData) {
    return React.createElement(React.Text, {}, rowData);
}
module.exports = function () {
    return React.createElement(React.View, {}, React.createElement(React.ListView, {
        'dataSource': this.state.dataSource,
        'renderRow': renderRow1.bind(this)
    }));
};

My bad, I wasn't using the '-r' to overwrite the previous file.
Now I get:
var testRT = function () {
    function renderRow1(rowData, sectionID, rowID, highlightRow) {
        return React.createElement(React.Text, {}, rowData);
    }
    return React.createElement(React.View, {}, React.createElement(React.ListView, {
        'dataSource': this.state.dataSource,
        'renderRow': renderRow1.bind(this)
    }));
};

But this still lacks the var React = require('react-native').

I will be closing this now since the original question has been solved.

You have to provide the --modules commonjs option too, otherwise it will default to none (no modules).

Can you post a link to the source?

see options.js

Strange. The docs say:

In native mode the default modules option is set to commonjs and the default react-import-path is set to react-native.

Maybe I'm doing something wrong.
When using rt template.rt -r --modules commonjs --native I get:
'use strict';
var React = require('react/addons');
var _ = require('lodash');
module.exports = function () {
    return React.createElement(React.View, {}, React.createElement(React.Text, {}, 'Hola'));
};

Which still misses var React = require('react-native');.

It seems I got it right with rt template.rt -r --modules commonjs --native --react-import-path react-native.
I will open a new bug about the --native option not doing its thing.

repo: wix/react-templates


text:
OnOther action dosent work

I've already posted here before with an error -> https://github.com/wiz0u/WTelegramClient/issues/129
Then I did not solve the error, for some reason my OnUpdate method did not receive ReactorError
Now when I get the error "You must connect to telegram first" again, I discovered and opened this issue:
https://github.com/wiz0u/WTelegramClient/issues/157
I updated the library to version 3.5.2-dev.20, however it didn't help me. Method Client_OnOther for some reason still not being called after calling Dispose. I have tried this on my app and also on "Fatal reactor error" demo app:

Why might a method Client_OnOther not be called?

Previously (when there was only one OnUpdate signal), I got updates about new messages etc. but never got a ReactorError update, now this problem persists.

The issue with ReactorError not being correctly raised was fixed in 3.5.2-dev.1 and later
In any case, by design, ReactorError is not raised AFTER you call Dispose.
I think you got things backwards.
ReactorError can be caused by fatal errors (like non-transient network loss) while the client is running. And THEN while YOU handle such ReactorError in your OnOther handler, the recommended action is that you call Dispose.

I tested calling a OnOther signal on your code template, and I can't seem to get the OnOther signal to be called. Where could be the error?

PEBKAC


text:
added gh and gss, fixed gl4 alias, sorted/uniq'ed

gh: seclorums history
gss: show order of all branches

thanks honey!  😘


text:
被tableview盖住了，如何解决？

点击菜单，下拉出来的选项，被tableview挡住了，该怎么解决？我的tableview是放在SB上的，和这个有关系吗？

把我的控件放到最上面吧，比如用 self.view insertsubview  above……

或者是加完了 tableview 后再downMenu 这样就在最上面一层

我是先添加tableview，在创建downMwnu，问题解决了。谢谢！

authors: smileat wjTime

repo: wjTime/WJDropDownMenu


text:
added an option 'DISABLE_CATKIN'

I've made some changes that will enable building the project without relying on Catkin. This should provide more flexibility for users who prefer to build the project in environments where Catkin is not available or not desired.

the changes were made for Windows users who may find installing Catkin challenging due to its lack of official support.

repo: wjwwood/serial


text:
Start a new pre-release: 2.0.0-alpha.1

To use dropdown component

Yay! a chance to test the new prerelease workflow. I'll try it first if you don't mind.

authors: Ladsgroup itamargiv

repo: wmde/wikit


text:
Support modules

Support import that:

Evaluates a fizz file.

The file should be relative to the current module's root, or
The working directory in the case of virtual modules.

Exposes the file's symbols to the current scope.

(import "/path/to/my-module.fizz")
(my-module/module-fn)

Modules are now supported, however:

Errors on failure are terrible.
deleteModule doesn't clean up references to the module.

[1] will be left to a larger error improvement effort. [2] will be the final blocker to close this out.

repo: wmedrano/fizz


text:
allow TSI that is not 5 or 7 digits to support non land stations

Can we please allow TSI that is not 5 or 7 digits to support non land stations :

@david-i-berry can this be closed ?

Addressed in #41.

authors: david-i-berry maaikelimper


text:
How to check if Snappy library is used

hi,
i installed snappy library (compression library) on my macbook pro (osx 10.7.3 + xcode 4.2.1) using homebrew
brew install snappy

which will install snappy into /usr/local/Cellar/snappy/1.0.4
homebrew adds these path to $PATH
my question is, how to get the information if snappy is used properly?

snappy is used.
i faced off an error message about snappy
/Users/fibric/.rvm/rubies/ruby-1.9.3-p0/bin/ruby -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /Users/fibric/Projects/StoreBox/lib/store_box.rb
dyld: lazy symbol binding failed: Symbol not found: __ZN6snappy19MaxCompressedLengthEm
Referenced from: /Users/fibric/.rvm/gems/ruby-1.9.3-p0@leveldb/gems/leveldb-ruby-0.10/lib/leveldb/leveldb.bundle
Expected in: flat namespace
dyld: Symbol not found: __ZN6snappy19MaxCompressedLengthEm
Referenced from: /Users/fibric/.rvm/gems/ruby-1.9.3-p0@leveldb/gems/leveldb-ruby-0.10/lib/leveldb/leveldb.bundle
Expected in: flat namespace
Process finished with exit code 133
i used this code in
ruby
db = LevelDB::DB.new 'asdf'
db.put :key, :value
db.get :key

I'm not even sure why Snappy is being called in the first place. From what I can tell, the OS X-specific code bits explicitly avoid using snappy. You may wish to talk to the LevelDB authors. Another experiment would be to see whether a pure C++ client on OS X works, i.e. whether it's the Ruby bindings that are introducing the issues.
Sorry I don't have a better answer for you.

no problem. i'll ask in google groups about that situation.
i can't fix it by my self because i have almost zero knowledge about c/c++

I ran into the same issue - (Ruby 1.9.2, Mac OS X 10.6.8)
The issue was that I had installed the snappy library (using just ./configure; make; sudo make install). Installing the leveldb-ruby gem after this gave me the same error:
dyld: lazy symbol binding failed: Symbol not found: __ZN6snappy19MaxCompressedLengthEm
Referenced from: /Users/jones/.rvm/gems/ruby-1.9.2-p0/gems/leveldb-ruby-0.10/lib/leveldb/leveldb.bundle
Expected in: flat namespace
Poking around in the Leveldb source, included in the gem, I saw that this is referenced from a couple of include files, but only when it finds that the snappy library is installed.
So I uninstalled Snappy with a 'sudo make uninstall' from the snappy build directory.
I then did a gem 'uninstall leveldb-ruby' followe by a fresh 'gem install leveldb-ruby'
Problem solved !
I presume that the leveldb installation will no longer use snappy compression (I don't think there is any snappy code in the included leveldb code) - that's not a problem for me (in the short term at least)
--Rob Jones

I also removed snappy from search path and all my problems are gone. Of cause snappy is not the best compression library out there but the fastest one for plain text. I hope that snappy can be combined with leveldb-ruby rather sooner than later ;-)

authors: craic fibric wmorgan

repo: wmorgan/leveldb-ruby


text:
Is ExtendedXmlSerializer thread safe?

I have a single static instance of IExtendedXmlSerializer defined like so: new ConfigurationContainer().Create(). It is used in multiple threads. I haven't had any problems with it, but I wanted to make sure that this is the intended and safe way to use it, can someone confirm or deny this? I don't see it mentioned in the docs and readme, I only found one vague issue comment here.

It should be. :)  Your profile picture is perfect for my assessment, @bpaczkowski. 😆
FWIW I had a problem once with initialization so I added an EnableThreadProtection extension method (and extension, of course).  Here it is in action:
https://github.com/wojtpl2/ExtendedXmlSerializer/blob/afe70bb87188072c94b31f3f0151991faabf9d59/test/ExtendedXmlSerializer.Tests/ReportedIssues/Issue208Tests.cs#L17-L30
That should take care of any issues you might encounter.  Please note that this accounts for the components within ExtendedXmlSerializer and you will have to manage external components (such as streams) on your own.
Please let me know if you encounter any issues around this and I will look further into it for you.

But theoretically EnableThreadProtection is not needed? I think locking the serializer would result in a performance degradation.
From my testing it would seem that ExtendedXmlSerializer stores some state internally even between instances of ExtendedXmlSerializer, is that correct? The way I tested is the first parsing of an xml after starting a process is the longest, all further parsing is an order of magnitude faster, even when recreating the serializator.

I think locking the serializer would result in a performance degradation.

It totally does!  Haha.  I do not think it is needed except for some scenarios where you might have a race condition with creating a serializer.  Technically that is not the concern of EXS and could be handled outside of it.  It's probably why I haven't really mentioned it until now, either.
And yes there is a lot of caching mechanisms that are employed so that sounds about accurate.  Most are via static singletons which are probably being accessed for the first time which is the startup cost that you are experiencing.  It shouldn't be too bad though.  We are right up there in terms of speed with the classic serializer.  Or were.  I had a little issue with the performance story and got a little derailed. (Long story haha).
If any issues do arise or something seems awry please do bring it to our attention and we'll check it out.
Also:

😂

Ahh I see. The serializer is created statically so I guess that shouldn't be a problem. Thanks for the prompt response.
That "long story" was an interesting read :wink:
I do have another totally unrelated question. Is the big performance degradation when using UseOptimizedNamespaces expected? Not a very good example, but recently we had a migration that required parsing and serializing back a few hundred xmls, some of them relatively big (still under 1 MB though). When UseOptimizedNamespaces was used, that migration took over an hour. With it removed and nothing else changed, the time needed was reduced to mere seconds. Reproducible every time. I could look into this a little more and maybe come up with a small repro project, but I wanted to make sure it's not the expected behavior.

That "long story" was an interesting read 😉

Haha I honestly am so burnt out over that whole ordeal.  I had about 10% of the energy required to even force myself to write anything remotely close to it.  It's cool now as I have a much better perspective when diving into performance and have the tooling needed to weed out false positives, etc.  But still.  THE BURN OMG NEW TOPIC PLEASE.

When UseOptimizedNamespaces was used, that migration took over an hour. With it removed and nothing else changed, the time needed was reduced to mere seconds.

WOW... that does sound suspicious.  To be certain we do travel the object graph each time to ensure we have all the necessary namespaces but that sounds overwhelmingly inordinate!  I will look into this one and see what I can find.  Is there any chance you can provide the class(es) used in your migration?  There might be something funky going on with the graph that we haven't considered.  Obfuscating the names is OK if it's a data issue.  I am interested in the types used.
I have captured this in a new issue here:
https://github.com/wojtpl2/ExtendedXmlSerializer/issues/209

Closing this for now as I believe we answered the driving question here.  Please feel free to comment further and we can re-open if need be.

authors: Mike-EEE bpaczkowski


text:
Pcode

Pcode completed. Test it!

我想到应该可以用 ifdef 宏来共同支持 llvm 和 pcode。不过目前试了一下，项目结构应该要大改。之后我弄一下这部分内容。

另外为了方便切换 llvm 和 pcode，能不能避免 PcodeRuntime 作为 PcodeVisitor 友元？可以像 llvm 部分一样，使用 Module 作为 Visitor 和 Runtime 的中介。pcode 输出的部分也最好移动到 Module 中。

authors: Pan-Pan-Pan wokron

repo: wokron/tolangc


text:
Pipeline never completes, timeout doesn't kick

Component
server
Describe the bug
We have jobs that have been running for over 16h and are still considered in progress, like this:
https://woodie.osgeo.org/repos/30/pipeline/777
The timeout is set to 180 minutes (3 hours)
System Info
source	"https://github.com/woodpecker-ci/woodpecker"
version	"1.0.1"

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

We found that the problem was a non-silent infinite loop. Is the woodpecker timeout only effective during silent periods ?
https://trac.osgeo.org/postgis/ticket/5473

repo: woodpecker-ci/woodpecker


text:
wip: render button as a tag (need feedback)

Closes #1259
I've adjusted the button component to conditionally render the proper element given the props. I did run into one oddity. If you specify both the :href="..." and :to="..." the Router Links will not work, hence the btnAttrs work around to avoid the issue.
Additionally, this PR currently causes a recursive render because the Button component and the DOM button element share the same name, so if we conditionally render based on the string button it tries to render the Button component and then we hit a max recursion limit. To resolve this we need to rename the button component.
What should I rename it to? BaseButton would be my suggestion, but I wanted some feedback for I make that big of a change.

BaseButton sounds fine to me
cc @anbraten


text:
add apps to humanize and dehumanize bytes

app humanize
app dehumanize
use scala-native for these apps
publish in AUR

done in b9a307e and 5a73068

repo: wookietreiber/scala-cli-tools


text:
Move to bintray

cc @aforcier

:shipit:

authors: aforcier maxme


text:
Add snakeyaml.

This change is

imports/java/org/yaml/BUILD.bazel line 4 at r1 (raw file):
Previously, stevenwarejones (Steven Ware Jones) wrote…
whats the need for this dep?

@stevenwarejones It is for parsing liquibase yaml files when testing postgres code.


text:
tls-aware upgrade client + config and docker compose

Changelog:

Deployment files for external party reshare servers
Local setup with NGINX and TLS
Removed the auto-generated clients, and implement a TLS aware client
Documentation

@carlomazzaferro Just FYI, there is an official way to pass tls config to the autogenerated client. I would probably do that instead of modifying the autogenerated client, since it is a hassle to do so again if the protobuf definitions change
I can quickly implement this way if you want.

@carlomazzaferro Just FYI, there is an official way to pass tls config to the autogenerated client. I would probably do that instead of modifying the autogenerated client, since it is a hassle to do so again if the protobuf definitions change I can quickly implement this way if you want.

@dkales  hat would be wonderful, I struggled a bit with it yesterday. Feel free to push to the same branch

@carlomazzaferro  I cannot really test it locally anymore with the new docker files since I do not have pull permissons on the docker repo, could you test this?

@carlomazzaferro I cannot really test it locally anymore with the new docker files since I do not have pull permissons on the docker repo, could you test this?

On it

@dkales managed to get the ssh chain working, and the client you implemented also works flawlessly with it. Thank you!
Feel free to give it another look, and I'll merge it.

authors: carlomazzaferro dkales

repo: worldcoin/iris-mpc


text:
Top up functionality

To be able to budget on seperate accounts sometimes you want to 'top up' your account to a certain amount. For example every month I want to be able to spend 50€ on beer from my beer account.
In IFTTT you can create montly triggers but it is currently not possible to top up your account from a savings account (or any other) to a certain dedicated account.
This pull request creates this functionality. What is still missing is:

Documentation for the wiki
A more efficient way to fetch the balance of the target monetary account (currently this goes via updating all bunq accounts)

Btw, awesome project! I was able to very quickly implement additional functionality and even got the whole project working from my mobile phone.
We can discuss a little bit if you think this functionality should be implemented and how.

When playing around with IFTTT it becomes clear that it even would be better if:

ifttt/v1/actions/bunq_topup/fields/source_account/options would return the top up amount as well for ingredients to provide a better verbiage.

Thanks! I will have a look at this somewhere in the next few days...

Ok, so I have taken your suggestion, but decided to make it a bit more generic. Using two new 'target balance' actions, you can top up your account in the same way your code allows, but also:

skim an excess balance away to another account
use draft payments (instead of only direct payments)
even use payment requests to top up from an account at e.g. another bank

I am therefore closing this pull request, but thank you so much for the suggestion!

Great! Thanks for your effort, I will make sure to update to your version.

authors: OlafHaalstra woudt


text:
Error importing from bags

Describe the bug
One of the items in my bag is failing to import when i try to do "import from bags" in the new Batch tab.  I'm use WowSims Exporter to get my bag items, and when I go to import them I get an error saying "Error: Cannot parse JSON null for proto.ItemSpec#gems".  I narrowed it down to being a specific piece of gear in my bag causing the problem, which is Bloodthirsty Gladiator's Felweave cowl.  This helm does not have a meta gem equipted, but it does have a mastery gem equipted, so when wowsims generated the json string it's pulling null in for the meta, and then choking when it goes to import is my guess.
In the string below, this helm is item ID 64746.
To Reproduce
Steps to reproduce the behavior:

Go to new Batch tab for Demonology Warlock
click import from bag
use this string:
{"items":[{"id":45691,"gems":[]},{"id":58188,"gems":[]},{"id":58157,"gems":[52208]},{"id":56319,"gems":[]},{"id":65167,"gems":[]},{"enchant":4115,"gems":[],"id":62357},{"enchant":3854,"gems":[],"id":56461},{"enchant":3252,"gems":[52219,52219],"id":59454},{"id":75065,"gems":[]},{"enchant":3834,"gems":[],"id":56357},{"id":54498,"gems":[]},{"id":55810,"gems":[]},{"enchant":4091,"gems":[],"id":56306},{"id":56276,"gems":[]},{"id":65169,"gems":[52207]},{"enchant":4063,"gems":[],"id":55998},{"id":56440,"gems":[]},{"enchant":4068,"gems":[52207],"id":58158},{"id":59519,"gems":[]},{"id":54496,"gems":[]},{"id":54499,"gems":[]},{"id":64725,"gems":[]},{"enchant":2332,"gems":[],"id":64723},{"id":54487,"gems":[]},{"id":64746,"gems":[null,52219]},{"id":54489,"gems":[]},{"id":60480,"gems":[]},{"id":54494,"gems":[]},{"id":54497,"gems":[]}]}

Expected behavior
the import to work
Sim Links and Screenshots
If applicable, add links to your sim settings or screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser Chrome
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@IOEggception Thanks for the report and the detailed research!
I'll dive into this.

@IOEggception a fix for this was just pushed to the addon! Should be on curse soon. Thanks for reporting.

repo: wowsims/cata


text:
Crash Report -1312450110

Link:
https://wowsims.github.io/cata/warlock/demonology/#eJzlVF1oHVUQ3pmz996zE43bk5+uR+jdbH24LG28PwgxlN5N8CGID6EU6WsgbbUolURBfUrUh6hVUiumubQPDYgaLhLypIEWDNpGU+ntj61tIxFtuCkEGhRF0ahn9+yG1Pqo+OC8zOw3M9+cmTNnaQuHAB6HEYCjAO8BzAF8BbAKMIIwhdDdGPr3wHMwFTmEId9oqLB075N9z+8d4Bmby5tAwv6oxpxbrmdVx82lGrtSY5Sxa3WWGwW6xz55jjnLrsd+GYsAsj9W0Ufc0Bb29cvMWcx66Vtjkf8I0N32ReU/0eaBkRsDsu1jdebcyHqm8kfIXXb9feal1adKUhTXFMVh10uPHA2BXCWs+b3K+S3rJUDGPns6Km7Zh9dYBCvs1LkIy9iLN1junfBkU6vMGXb1KRfUKX7N6uy31sJIz+Kp/OZecxTAP4MO0M9g/E9F9PxTTJ1GtzUE8X69iSYhGTMot5dKhaKSUj5fKuSLyi4UFFbMF2fxfv7NPNpX5tG5tITud/OYu7qE+a+XsOP3Cxi8eBF71i7gHJo1bLiGxrd4MqXuqoW4TJPJZz81PYsylNre0Z4fpCZKS1XT2RSDxfYHB9djK8uwEW6mjEwR4+cLMZpXqDAldhqiXW4jT7rUNA02NfJXWt0/ElFbV4GQ7uaiKWMtdsodtFW0kTUduYY/MRPzpQ9TiTkxb4oWsh4+ePCp/c/2DfQLfayVURAtsomsCYg7SjoTO2QnFeQDCYGCEvPHVaTNfgtnwpqJgLnXIUwjLA3GXYmwAR2TORBC103JK2ZsaSUmQb4LdBykehjdIqBtvh9yHlDz4AvogrxvGh0OglcwzFhASRUzcZLtN/KUwEcMXVoNdbfYRW1+VnE0zdw5Oh1WHCTHb729jDKIFZTn7yYudWk9JT38yUMRWajv6LMKSZ9VnVq9bcArh5iM9UbG8Z9Qxlq4cgs1C0GpzxH5+oV/+ZquqXRUs9Vv5mlhzUbO86dSYS2CQhRTV0tBcn3vhCX1sn3QsIz9q/g2DDP9YNzghLaGHgteZYZXxx6wNLAv2KRjdgb3VsZD+az8kEZq5bZ9kVwud31xNpSVcrGKT0/+AC807Op7ot/d3Tewf+8z7h4n4//H/7Xel4N/g3ao/8xG3kc7jh/r+mtMNK2hCatrHPQAr5bjGDP4E/CwLRo=
RNG Seed: 1871982685
runtime error: invalid memory address or nil pointer dereference
Stack Trace:
goroutine 13 [running]:
runtime/debug.Stack()
/opt/hostedtoolcache/go/1.21.12/x64/src/runtime/debug/stack.go:24 +0x6
github.com/wowsims/cata/sim/core.runSim.func1()
/home/runner/work/cata/cata/sim/core/sim.go:125 +0x10
panic({0x14a000, 0x1daebc0})
/opt/hostedtoolcache/go/1.21.12/x64/src/runtime/panic.go:914 +0x2c
github.com/wowsims/cata/sim/warlock/demonology.(*DemonologyWarlock).registerSummonFelguard.func1(0x33fe120, 0x38ad400, 0x38ad528)
/home/runner/work/cata/cata/sim/warlock/demonology/demonology.go:92 +0x6
github.com/wowsims/cata/sim/core.(*Unit).RegisterSpell.(*Spell).makeCastFunc.func6(0x33fe120...

Bug caused by trying to cast summons without a pet selected in the settings

authors: kayla-glick volbiathenewb


text:
Enable https if using cloudflare / provide manual override

Hi,
We use cloudflare for the Name Server, and cloudflare serves https content if we use them even if the origin server uses http (See https://support.cloudflare.com/hc/en-us/articles/200170416-What-do-the-SSL-options-mean- )
Hence, in this scenario, using custom domains and CNAME using cloudflare, it would make sense to allow a manual override enabling https in your plugin settings if the site admin knows what they're doing.
Can you add this in please so chrome can show the website as secure again ?
Thanks.

I came here just to file the same request for this feature only to find @davidcommarmond's ;)

@davidcommarmond  I have just forked this plugin and added the Force SSL feature.
It is over at -> https://github.com/wpCloud/wp-stateless/pull/282

When will this feature be released? Do you have any ETA?

@roku6185 if in the "Domain" field you also add https:// in front of the domain name, it'll serve from https and not http (Not sure where I read this in the code but there's a condition there).

Works well on our website https://www.i-spy360-mauritius.com/

@williamli thanks, hopefully it'll be merged to stable, will avoid confusions on how it works.

@davidcommarmond @roku6185 it has been merged into stable a while ago in v2.1
https://github.com/wpCloud/wp-stateless/pull/282

I'm using wp-stateless 2.1.7 and I don't see any option for "Force SSL". What version should I be using? I installed Wordpress yesterday, so I guess I'm using the latest version of wp-stateless.
Putting "https://<MY_CDN_DOMAIN>" in the "Custom domain" field doesn't do anything for me. The "Preview" URL doesn't change nor do the image URLs in posts have the new custom URL.

Will be release soon.
You can use pre-release version
https://github.com/wpCloud/wp-stateless/releases/tag/2.1.8-RC1

I dowloaded the pre-release but I can't find the new option "Force SSL" in the code:
grep "Force SSL" wp-stateless-2.1.8-RC1/ -rn
, results in nothing. But according to the patch it should be there: https://github.com/wpCloud/wp-stateless/pull/282/files#diff-546de7b1d43b494ce1b2e9bb59e7cdffR185

@roku6185 Sorry for the miscommunication.
Check issue #291
You just have to prepend  https:// in Domain field.
https://cdn.example.com

This is very confusing. Prepending "https://" in the Domain field doesn't work. The preview isn't updated and the resulting images (e.g. in posts) only have the raw bucket url. I get the following javascript error on the "Stateless Settings" page:
Error: $scope.apply is not a function
angular.min.js:114:210

@roku6185
Please use the this version
https://github.com/wpCloud/wp-stateless/releases/tag/2.1.8-RC2

@alimuzzaman I just tried 2.1.8-RC and experienced the same problem as mentioned by @roku6185. As soon as I added https:// to the domain field, the preview link auto resets itself back to using google storage url.

authors: alimuzzaman davidcommarmond roku6185 williamli

repo: wpCloud/wp-stateless


text:
Follow official tutorials for multi-lingual porfolio

Hello @wr0124, I guess you want to add Chinese !
You may want to follow this playlist :

[ ] Vidéo

[x] Video 1 : customization
[x] Video 2 : create new language

@hugolpz Thanks for writing through github! it is a nice way to learn how to use it!   I had watched video2, but I get problem of Synchronization. I can totally modify the files as following the steps, but failed to connect to github.  I guess maybe due to some setting issues ?


text:
Module.json points to old version of FXMaster

If you don't have FXMaster installed when you install this module, the prompt to install it as a dependency points to an old (version 1.2.1) version of FXMaster. Therefore, unless you update it to the latest (2.4.0 I believe), the module is broken and scenes will not load.
it is pointing to a version on gitlab that hasn't been updated in 9 months, rather than the up-to-date one here:
https://github.com/ghost-fvtt/fxmaster

ghost — Today at 12:28 PM
Yeah, that’s from before I have taken over the module. Use this manifest URL instead: https://github.com/ghost-fvtt/fxmaster/releases/latest/download/module.json

ghost — Today at 12:29 PM
Also, i don’t think you even need to specify the manifest at all for dependencies. If you don’t, foundry will simply pick the latest version that’s listed

Can confirm, it grabbed a much newer version without the manifest specified. I'll remove it.

Done; prepped for release in 0.2.9.

authors: boostedPeaks wrycu

repo: wrycu/StarWarsFFG-Enhancements


text:
Unable to add API specific policy using YAML format via Publisher REST API

Description
Unable to add an API specific policy through the publisher rest api as provided in the documentation[1] when using YAML format.
[1].https://apim.docs.wso2.com/en/latest/reference/product-apis/publisher-apis/publisher-v3/publisher-v3/#tag/API-Operation-Policies/operation/addAPISpecificOperationPolicy
Steps to Reproduce
Start APIM Server.
Create an API.
Try to add the policy as below for the API_ID using policySpecFile=@setHeader.yaml and  policyDefinitionFile=@setHeader.j2 , policy spec file in YAML.
curl -k -H "Authorization: Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8" -H "Content-Type: multipart/form-data" -F policySpecFile=@setHeader.yaml -F policyDefinitionFile=@setHeader.j2 "https://127.0.0.1:9443/api/am/publisher/v3/apis/96077508-fd01-4fae-bc64-5de0e2baf43c/operation-policies"
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Need to merge the public fix: https://github.com/wso2/product-apim/pull/13191


text:
Remove Hazelcast Usage from Carbon Kernal

Description
As we have deprecated the hazelcast based distributed caching use cases in APIM, removing the hazelcast dependency from carbon-kernal repository.
Affected Component
APIM
Version
4.2.0
Related Issues
#471
Suggested Labels
No response

Completed via https://github.com/wso2/carbon-kernel/pull/3440

authors: hisanhunais piyumaldk


text:
No Validation for Wrong Username Formats in "Forgot Password" Option and Throw a Exception When Trying with a Username with"@"

Problem
When a user try to change his/her password through "Forgot Password" Option, But Mistakenly add a "@" for the username or an email as the username, APIM will not handle the exception in a proper way. User will  be redirected to "unable to handle this request" page.

Solution
Add Field Validation to stop users from adding emails and usernames with @ will be one solution. Showing an error after trying to reset the password will be another solution.
Additional Note
In order to try the Forgot Password option in APIM, you can follow this documentation.
Since it may need a minor improvement, you may also read this issue which is related to the above documentation.
Affected Component
APIM
Version
4.2.0-M1
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Added the PR with the fix : https://github.com/wso2/product-apim/pull/13038

authors: GihanAyesh piyumaldk


text:
move subs protos

move subs protos

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c449b39) 28.12% compared to head (c039dc5) 32.59%.
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1927      +/-   ##
==========================================
+ Coverage   28.12%   32.59%   +4.47%
==========================================
  Files         123       76      -47
  Lines       13932     5093    -8839
  Branches     2567     2567
==========================================
- Hits         3918     1660    -2258
+ Misses       9881     3433    -6448
+ Partials      133        0     -133

Flag
Coverage Δ

config-deployer-service
26.83% <ø> (?)

idp-domain-service
80.18% <ø> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


text:
Corrected pass through docs images and other docs.

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

resolves #
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

This seems already merged.


text:
Improvements fix for https://github.com/wso2/carbon-kernel/pull/1817

Purpose
Fix https://github.com/wso2/carbon-kernel/pull/1817 review comments
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant sarubi


text:
APIM 4.0 docs - Need to update the token API endpoints

Description:
With the latest APIM 4.0, the token end points have been changed, For example
https://<host>:<port>/token has been changed to https://<host>:<port>/oauth2/token but this has not been reflected on the docs.
Note that the ports mentioned in the example cURLs also need to be updated accordingly.
Bellow are some of the documentation links we need to fix this

https://apim.docs.wso2.com/en/latest/design/api-monetization/monetizing-an-api/
https://apim.docs.wso2.com/en/latest/reference/product-apis/admin-apis/admin-v2/admin-v2/#section/Authentication

This seems to be fixed now so I'm closing this.

authors: rnavagamuwa samgnaniah


text:
Add Mysql jar using an init container

Latest docker images does not contain the mysql jar. Hence init container is used to download the jar to the API Manager container.

Fixed with https://github.com/wso2/k8s-wso2am-operator/pull/46


text:
problem when we create 2 gateway environments with same name.

If we make 2 different types of gateway environments with the same name it shows only one gateway Environment in the publisher. It doesn't display any notice or error while executing the code.

Obvious user configuration issue.

authors: ShanJayaweera chamilaadhi


text:
Adding test for product-apim/issues/11894

Adding test for product-apim/issues/11894

Closing the test


text:
Add organization administrator button is not working in the console

Describe the issue:
Add organization administrator button is not working in the console
How to reproduce:
Go to Administrators tab in the console and try to add an admin.

Didn't released with alpha. Hence moving the milestone.

This is a regression due to an improvement in Add User Wizard.

Fixed with: https://github.com/wso2/identity-apps/pull/4454


text:
Bump Dependencies #9267890619

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/9267890619

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant jenkins-is-staging


text:
IDENTITY-4796 - Add test function to retrive federated IdPs for users who have login …

…permission

Test case was added with #817. Therefore closing this PR.

authors: isurusuranga mefarazath


text:
remove danieljdufour/djenv

29 stars, 0 forks, 13 commits. How could it have been included in the first place?

Thank you for your feedback. We understand your concerns about the project's inclusion in Awesome Django based on its engagement metrics. We evaluate each submission based on various factors, including functionality, usefulness, and relevance to the Django community. While engagement metrics like stars, forks, and commits can provide some insight, they are not the sole determining factors for a project's inclusion.
We will review the project again and determine whether it meets the criteria for inclusion in Awesome Django. If you have any specific concerns about the project's quality or utility, please share them with us; we will consider them during our review. We appreciate your input and strive to maintain a high standard for the projects included in our list.

Hi @deronnax, Echoing @jefftriplett here, thank you for this PR and bringing up your concerns. On reflection I agree it seems a little light in usage for inclusion. So I'm approving this PR.

Thank you so much 🙏

authors: deronnax jefftriplett wsvincent

repo: wsvincent/awesome-django