Go checker --buildmode archive in go1.10

An improvement in 2015 to reduce check times using go1.7 relied upon a 'bug' in the go builder which has been 'fixed' in go1.10.1. (I believe it worked in 1.10, but can't confirm)
The --buildmode archive flag now throws an error on main packages: no packages to build
(It may not be a bug, but the new behavior matches the docs)
Commit which added the --buildmode archive flag as default: https://github.com/vim-syntastic/syntastic/commit/3c2e7e4ce37bc68b54f23c62efd0be291e6dc450
Discussed in issue https://github.com/vim-syntastic/syntastic/issues/1528
workaround:
let g:syntastic_go_go_build_args=''

Please find out in what release version --buildmode was removed from go.

that's also the problem what I meet

"main.go" 18L, 197C
syntastic: 0.310996: g:syntastic_version = '3.8.0-110 (Vim 800, Darwin)'
syntastic: 0.311181: &shell = '/bin/bash' (!), &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '',
 &autochdir = 0, &shellxescape = ''
syntastic: 0.311913: UpdateErrors (auto): default checkers
syntastic: 0.312639: CacheErrors: default checkers
syntastic: 0.313797: g:syntastic_aggregate_errors = 1
syntastic: 0.314236: getcwd() = '/Users/arthur/golang/src/mytest/test'
syntastic: 0.318493: CacheErrors: Invoking checker: go/go
syntastic: 0.354267: system: command run in 0.035340s
syntastic: 0.355396: SyntasticMake: called with options: {'errorformat': '%f:%l:%c: %m,%-G%.%#', 'defaults': {'type': 'e'}, 'makeprg': 'gofmt -l main.go > /dev/null'}
syntastic: 0.369400: system: command run in 0.013536s
syntastic: 0.369574: checker output: ['']
syntastic: 0.369993: raw loclist: []
syntastic: 0.370387: SyntasticMake: called with options: {'cwd': '/Users/arthur/golang/src/mytest/test', 'errorformat': '%W%f:%l: warning: %m,%E%f:%l:%c:%m,%E%f:%l:%m,%C%\s%
\+%m,%+Ecan''t load package: %m,%+Einternal error: %m,%-G#%.%#', 'defaults': {'type': 'e'}, 'makeprg': 'go build -buildmode=archive', 'env': {'GOGC': 'off'}}
syntastic: 0.461755: system: command run in 0.090842s
syntastic: 0.462017: checker output: ['no packages to build', '']
syntastic: 0.462696: raw loclist: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'no packages to build'}, {'lnum': 0,
 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 0.463155: getLocList: checker go/go returned 1
syntastic: 0.463330: go/go raw: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': 'no packages to build'}, {'lnum': 0,
'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': ''}]
syntastic: 0.463663: quiet_messages filter: {}
syntastic: 0.463861: getLocList: checker go/go run in 0.145190s
syntastic: 0.464217: aggregated: {'_sorted': 0, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}
syntastic: 0.464489: sorted: {'_sorted': 1, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}
"main.go" 18L, 197C written
syntastic: 3.360674: g:syntastic_version = '3.8.0-110 (Vim 800, Darwin)'
syntastic: 3.360863: &shell = '/bin/bash' (!), &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '',
 &autochdir = 0, &shellxescape = ''
syntastic: 3.361397: UpdateErrors (auto): default checkers
syntastic: 3.361884: CacheErrors: default checkers
syntastic: 3.362690: g:syntastic_aggregate_errors = 1
syntastic: 3.362956: getcwd() = '/Users/arthur/golang/src/mytest/test'
syntastic: 3.363558: CacheErrors: Invoking checker: go/go
syntastic: 3.364597: SyntasticMake: called with options: {'errorformat': '%f:%l:%c: %m,%-G%.%#', 'defaults': {'type': 'e'}, 'makeprg': 'gofmt -l main.go > /dev/null'}
syntastic: 3.378678: system: command run in 0.013704s
syntastic: 3.378878: checker output: ['']
syntastic: 3.379331: raw loclist: []
syntastic: 3.379785: SyntasticMake: called with options: {'cwd': '/Users/arthur/golang/src/mytest/test', 'errorformat': '%W%f:%l: warning: %m,%E%f:%l:%c:%m,%E%f:%l:%m,%C%\s%
\+%m,%+Ecan''t load package: %m,%+Einternal error: %m,%-G#%.%#', 'defaults': {'type': 'e'}, 'makeprg': 'go build -buildmode=archive', 'env': {'GOGC': 'off'}}
syntastic: 3.459639: system: command run in 0.079064s
syntastic: 3.460394: checker output: ['no packages to build', '']
syntastic: 3.461369: raw loclist: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'no packages to build'}, {'lnum': 0,
 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 3.461866: getLocList: checker go/go returned 1
syntastic: 3.462028: go/go raw: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': 'no packages to build'}, {'lnum': 0,
'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': 'e', 'pattern': '', 'text': ''}]
syntastic: 3.462335: quiet_messages filter: {}
syntastic: 3.462496: getLocList: checker go/go run in 0.098779s
syntastic: 3.462870: aggregated: {'_sorted': 0, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}
syntastic: 3.463194: sorted: {'_sorted': 1, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}

see also #2164

https://github.com/vim-syntastic/syntastic/issues/2164

It occurred between 1.9 and 1.10.1, I am not sure if the problem exists in 1.10 - I’m not entirely sure how to get a copy at that revision

(The flag was not removed, but it’s meaning has changed)

It occurred between 1.9 and 1.10.1, I am not sure if the problem exists in 1.10 - I’m not entirely sure how to get a copy at that revision

git pickaxe?  My development machine is broken right now, so I can't do it myself. shrug

Ill have a look later on, should be easy enough to find the commit.
It could be considered a bug in the go tool, but I suspect that discussion will go on for a while

but nothing different from go help buildmode
in go 1.7
The 'go build' and 'go install' commands take a -buildmode argument which
indicates which kind of object file is to be built. Currently supported values
are:

	-buildmode=archive
		Build the listed non-main packages into .a files. Packages named
		main are ignored.

	-buildmode=c-archive
		Build the listed main package, plus all packages it imports,
		into a C archive file. The only callable symbols will be those
		functions exported using a cgo //export comment. Requires
		exactly one main package to be listed.

	-buildmode=c-shared
		Build the listed main packages, plus all packages that they
		import, into C shared libraries. The only callable symbols will
		be those functions exported using a cgo //export comment.
		Non-main packages are ignored.

	-buildmode=default
		Listed main packages are built into executables and listed
		non-main packages are built into .a files (the default
		behavior).

	-buildmode=shared
		Combine all the listed non-main packages into a single shared
		library that will be used when building with the -linkshared
		option. Packages named main are ignored.

	-buildmode=exe
		Build the listed main packages and everything they import into
		executables. Packages not named main are ignored.

	-buildmode=pie
		Build the listed main packages and everything they import into
		position independent executables (PIE). Packages not named
		main are ignored.

in go 1.10.1
The 'go build' and 'go install' commands take a -buildmode argument which
indicates which kind of object file is to be built. Currently supported values
are:

        -buildmode=archive
                Build the listed non-main packages into .a files. Packages named
                main are ignored.

        -buildmode=c-archive
                Build the listed main package, plus all packages it imports,
                into a C archive file. The only callable symbols will be those
                functions exported using a cgo //export comment. Requires
                exactly one main package to be listed.

        -buildmode=c-shared
                Build the listed main package, plus all packages it imports,
                into a C shared library. The only callable symbols will
                be those functions exported using a cgo //export comment.
                Requires exactly one main package to be listed.

        -buildmode=default
                Listed main packages are built into executables and listed
                non-main packages are built into .a files (the default
                behavior).

        -buildmode=shared
                Combine all the listed non-main packages into a single shared
                library that will be used when building with the -linkshared
                option. Packages named main are ignored.

        -buildmode=exe
                Build the listed main packages and everything they import into
                executables. Packages not named main are ignored.

        -buildmode=pie
                Build the listed main packages and everything they import into
                position independent executables (PIE). Packages not named
                main are ignored.

        -buildmode=plugin
                Build the listed main packages, plus all packages that they
                import, into a Go plugin. Packages not named main are ignored.

The problem is ‘packages named main are ignored’ - it looks like the code now matches the docs.
+1 for dropping support, would make it much easier to help users debug issues if there is only one way they can be configured.

Packages named main are ignored.

that's the key


Compatibility issue - player movement does not follow camera with Forkcart installed

Mod Name
Forkcart
Mod Homepage
https://github.com/ImplicitSaber/Forkcart
Minecraft version
1.20.1 (LTS)
Describe the bug
Player movement does not follow camera
Steps to reproduce

Install the mod
Try to move yourself
PROFIT!

Logs
https://mclo.gs/6DPOMF1
Additional context
No response

As our LTS support target, 1.20.1 now only receives critical fixes related to Connector bugs. Please upgrade to the latest version for mod compatibility support.


org.knowm.xchange.exceptions.ExchangeException: 0: null.What does this message mean?

Hello, i have encounter this Exception when i am trying to place a limit order on Bitbay exchange.The code i have write is this:
                        TradeService tradeService = bitbayExchange.getTradeService();
                        BigDecimal tradeableAmount = new BigDecimal("5.00");
                        BigDecimal price = new BigDecimal("4901.15");

                        LimitOrder limitOrder = new LimitOrder(Order.OrderType.BID,tradeableAmount,CurrencyPair.BTC_EUR,null,null,price);

                        String orderID = tradeService.placeLimitOrder(limitOrder);
                        System.out.println("Limit Order ID: "+ orderID);

Does anyone knows what i have write wrong? Thanks a lot!

Hi makarid,
I think this might be a bug in the implementation of bitBinance or a lack of parameter checking. It would be easier for people to help you if you included a stack trace.

Hi Xion345,
thanks for your reply! I am sorry that i didn't put the stack trace.Here it is :
Exception in thread "main" org.knowm.xchange.exceptions.ExchangeException: 0: null
at org.knowm.xchange.bitbay.service.BitbayBaseService.checkError(BitbayBaseService.java:37)
at org.knowm.xchange.bitbay.service.BitbayTradeServiceRaw.placeBitbayOrder(BitbayTradeServiceRaw.java:41)
at org.knowm.xchange.bitbay.service.BitbayTradeService.placeLimitOrder(BitbayTradeService.java:64)

If you turn on the logging properties that dump out the actual JSON response from the exchange you might see the error in more detail.

Hi npomfret,
thank you for your reply.I don't know if this is the thing that you talking about,but i debugg the program and this printed on my console:
4835 [main] INFO org.knowm.xchange.bitbay.BitbayExchange - Calling Remote Init...
4836 [main] INFO org.knowm.xchange.bitbay.BitbayExchange - No remote initialization implemented for Bitbay. The exchange meta data for this exchange is loaded from a json file containing hard-coded exchange meta-data. This may or may not be OK for you, and you should understand exactly how this works. Each exchange can either 1) rely on the hard-coded json file that comes packaged with XChange's jar, 2) provide your own override json file, 3) properly implement the remoteInit() method for the exchange (please submit a pull request so the whole community can benefit) or 4) a combination of hard-coded JSON and remote API calls. For more info see: https://github.com/timmolter/XChange/wiki/Design-Notes#exchange-metadata
4846 [main] INFO org.knowm.xchange.bitbay.BitbayExchange - Calling Remote Init...
4846 [main] INFO org.knowm.xchange.bitbay.BitbayExchange - No remote initialization implemented for Bitbay. The exchange meta data for this exchange is loaded from a json file containing hard-coded exchange meta-data. This may or may not be OK for you, and you should understand exactly how this works. Each exchange can either 1) rely on the hard-coded json file that comes packaged with XChange's jar, 2) provide your own override json file, 3) properly implement the remoteInit() method for the exchange (please submit a pull request so the whole community can benefit) or 4) a combination of hard-coded JSON and remote API calls. For more info see: https://github.com/timmolter/XChange/wiki/Design-Notes#exchange-metadata

Search the docs for how to turn on the exchange json logging. Sorry, can't remember exactly how to do it right now.

Thanks a lot for your fast response!!! I will search it and post if i found something.Thanks again!

@makarid Look at BitbayBaseService.java:37 and you will discover the issue.

Hello timmolter,
thanks for your response.I am sorry but i am not a pro on programming and i am not sure if i can understand the error here correctly.In line 37 there is an if statement checking if the bitbay response on the request or not.If it is not responding then throws an error like ours? The only thing that come's to my mind is that i haven't put some parameters correctly(or not at all) on the getExchangeSpecification method that i call when i am creating the exchange instance.I have put only setApiKey and setSecretKey and then i call the applySpecification method.
Thanks for your response and your help.

You'll have to quickly become a pro then! :)
Clone the source code, and debug the code, looking at the values of everything. Unfortunately, the error response doesn't give much info.

This problem happens after the bitbay 3.0 version released.I hadn't any problem on bitbay 2.0 version.This is the code that i use to create my bitbay exchange instance if something seems strange please tell me,thanks:
private  static Exchange bitbayApiConnection(){

    final String username = "***";
    final String bitbayApiKey = "***";
    final String bitbayApiSecret = "****";

    Exchange bitbayExchange =ExchangeFactory.INSTANCE.createExchange(BitbayExchange.class.getName());

    bitbayExchange.getExchangeSpecification().setApiKey(bitbayApiKey);
    bitbayExchange.getExchangeSpecification().setSecretKey(bitbayApiSecret);
    bitbayExchange.getExchangeSpecification().setUserName(username);

    bitbayExchange.applySpecification(bitbayExchange.getExchangeSpecification());

    return bitbayExchange;
}

I no longer get this error anymore.Thanks for you help!!!

@makarid can You tell me how You did manage it? I get the same error "No remote initialization for Bitbay". My code where im creating exchange instance looks the same like Yours.


emmet-helper getEmmetCompletionParticipants should be typed

emmet-helper getEmmetCompletionParticipants returns an any, and in the HTML code it is assumed to match the HTML and CSS perticipants.
That's very fragile.
I also want to avoid the any[] in https://github.com/Microsoft/vscode/blob/666e95e8e7f679e23c0e42d86864cba4f2e00025/extensions/html-language-features/server/src/modes/languageModes.ts#L38
Idealy, each mode (CSSMode, HTMLMode) interacts separately with the emmet helper.
Let each mode do the caching and pass in the triggerKind to the mode.
IMO for HTML we don't really need to do the caching. And in the long term I'd like to avoid the caching by improving the CSS parser.

The move of emmet for css completions to the css extension didn't work out. See https://github.com/Microsoft/vscode/issues/29113#issuecomment-383453793 to learn more.
So now we have just the html extension providing emmet completions outside of emmet extension. See https://github.com/Microsoft/vscode/issues/28545#issuecomment-383453951 on why this isn't much useful.
Reverting the move of emmet html completions from html extension with https://github.com/Microsoft/vscode/commit/c314388da21720d893e7a36345e1cac36d1cfd5f
Enabling css emmet completions in embedded css parts in html files with https://github.com/Microsoft/vscode/commit/79a2512769762928f089e4fd0b84764e37a1ce0d


Node.js version outdated and vulnerable

Issue Type: Feature Request
KLA11231 Multiple vulnerabilities in Node.js
Multiple serious vulnerabilities have been found in Node.js. Malicious users can exploit these vulnerabilities to cause denial of service.
Below is a complete list of vulnerabilities:
An unspecified vulnerability in the HTTP parser can be exploited remotely via Content-Length parameter to perform unspecified attacks;
A regular expression vulnerability in the ‘path’ module can be exploited remotely via specially crafted string to cause denial of service;
A DNS rebinding vulnerability in Node.js Inspector can be exploited remotely co execute arbitrary code.
Affected products:
Node.js earlier than 9.10.0
Node.js earlier than  8.11.0
Node.js earlier than  6.14.0
Node.js earlier than  4.9.0
VS Code version: Code - Insiders 1.27.0-insider (7b9afc4196bda60b0facdf62cfc02815509b23d6, 2018-09-03T09:14:29.879Z)
OS version: Windows_NT x64 10.0.10240

Details https://threats.kaspersky.com/en/vulnerability/KLA11231/
Per https://github.com/desktop/desktop/issues/4664, its my understanding that we have mitigated this by upgrading to Electron 2.0, which happened in our previous iteration.

Thanks for the report, we're aware of this issue. I don't believe VS Code specifically is vulnerable to any of these CVEs, but regardless we're working with Electron to backport the fixes such that the version of node that ships with Electron includes the fix (and follow up with Kaspersky if necessary).


Fluent management library does not work as expected in ASP.NET projects

We were using the following code from an ASP.NET API method (which is sync call) and the call never returns. I think somewhere in the code, it is using as async and wait. Can you please check?
public void CreateResourceGroup(
            Subscription subs, string rgName, string trainee, string trainer, string wsCode, int wsId)
       {
            var azure = subs.GetAzureReference();
            var rg = azure.ResourceGroups
                            .Define(rgName)
                            .WithRegion(Region.US_WEST)
                            .Create();
       }

public static IAzure GetAzureReference(this Subscription subscription)
       {
            var credentials = AzureCredentials.FromServicePrincipal(
                                subscription.AppId,
                                subscription.AppSecret,
                                subscription.TenantId,
                                AzureEnvironment.AzureGlobalCloud);
            return Azure.Authenticate(credentials).WithSubscription(subscription.Guid);
       }

The same code when invoked from a console app works. So I thought this is a sync/async mismatch in the SDK code.
Since we already had non-fluent sdk working, we did a fall back completely to non-fluent sdk for now.

@hovsepm Please assign to a sprint

Got the same problem when running azure.SqlServers.GetById() in ASP.NET.
Here is the workaround:
Thread thread = new Thread(() => { /* azure fluent code here */ });
thread.Start();
thread.Join();

Still doesnt work. Cant get any response in ASP.Net...

Duplicate of https://github.com/Azure/azure-sdk-for-net/issues/3238


Fixed deprecation warnings in materialized-views project by updating project structure.

Currently running DBT, while having this project installed as a dependency, will yield the warning:
13:33:39  Running with dbt=1.0.3
13:33:39  [WARNING]: Deprecated functionality
The `source-paths` config has been renamed to `model-paths`. Please update your
`dbt_project.yml` configuration to reflect this change.
13:33:39  [WARNING]: Deprecated functionality
The `data-paths` config has been renamed to `seed-paths`. Please update your
`dbt_project.yml` configuration to reflect this change.

This pull request makes the suggested changes and is therefore in-line with modern DBT. And in doing so will resolve the source of these warnings.
I have tested this PR on my local repositories.

@jtcohen6 Since you're usually quick and helpful when I tag you I'll do so again. This was again fairly low-hanging fruit.

@jtcohen6 Could you check it out again? I've implemented your requested changes a while ago.


riscv64: Initial support for the ZiCond Extension

👋 Hey,
This PR adds support for the ZiCond: Integer Conditional Operations (Chapter 12 of the Unprivileged RISC-V ISA Manual).
This extension adds two instructions that either zero a register, or move one of the arguments, depending on a condition register.

czero.eqz rd, rs1, rs2 - Moves zero to a register rd, if the condition rs2 is equal to zero, otherwise moves rs1 to rd.
czero.nez rd, rs1, rs2 - Moves zero to a register rd, if the condition rs2 is nonzero, otherwise moves rs1 to rd

It doesn't include a full conditional move of two registers, but that is implemented by combining both of the instructions above.
The ISA manual also suggests some interesting instruction sequences for conditional add/sub/and/or/etc... that only contain two instructions.
This PR only implements the base cases. The direct lowerings of the instructions, as well as the full conditional move of two registers. I'm planning on implementing the other sequences at a later date.

It looks like one of the CI jobs was canceled part way through. I wonder if this is also related to the issues in #8701


Update webpack dev config to fix sourcemap warning

See this: https://github.com/webpack/webpack/issues/91

Cheers 👍


SpriteFontX class and DrawString Extensions

After some discussion, we believe ExampleMod is not the place for this. The primary purpose of tModLoader is to provide modifications to Terraria's base code that enable the creation of compatible mods. We understand that you have added it to ExampleMod and not tModLoader, however we don't believe there is enough interest to warrant adding it, and would like to keep the purpose of ExampleMod clean and simple.
We suggest just adding this personally to any mods you're making that require it, or putting it in a shared dll or library mod. If there is enough interest we may consider adding it to tModLoader as a core utility for everyone at a later date


flaky test: test_operator.test_depthwise_convolution

http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-14016/4/pipeline/
ERROR: test_operator.test_depthwise_convolution
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/work/mxnet/tests/python/unittest/common.py", line 173, in test_new
orig_test(*args, **kwargs)
File "/work/mxnet/tests/python/unittest/test_operator.py", line 1676, in test_depthwise_convolution
np.testing.assert_allclose(arr1.asnumpy(), arr2.asnumpy(), rtol=1e-3, atol=1e-3)
File "/work/mxnet/python/mxnet/ndarray/ndarray.py", line 1995, in asnumpy
ctypes.c_size_t(data.size)))
File "/work/mxnet/python/mxnet/base.py", line 252, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
MXNetError: [01:40:38] src/operator/nn/mkldnn/mkldnn_base.cc:576: Check failed: similar
NOTE: The test fails on CPU when MKLDNN is enabled and passes when MKL-DNN is disabled. So, the issue is mostly due to MKL-DNN.

@mseth10, Thanks for reporting this. Confirmed it's caused by mkldnn bug. The fix is already in mkldnn master, but not available in its latest release. We will upgrade mkldnn when its next release comes out.

@ZhennanQin Thanks for confirming it's an MKLDNN bug. Good to know that it's fixed. Can you also give an ETA on when the next release containing the fix be rolled out?

Resolved so closing.


Replace "/"s in branch names with the URL encoding

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Fixes #35.
Why should this Pull Request be merged?
We currently fall back to master when trying to build dependencies if the branch name contains a "/". This affects dev and release builds for the SEECD.
What testing has been done?
Kicked off a build on a dev branch containing a slash, confirmed it chose the correct (non-master) branch. http://coordinator/job/VeriStand/job/ni/job/niveristand-scan-engine-ethercat-custom-device/job/dev%252Fadd_9266/7/console

I think replaceAll just takes a regex https://beginnersbook.com/2013/12/java-string-replace-replacefirst-replaceall-method-examples/


livestreamer 1.12.2 with --twitch-oauth-token drops error message, but works

d:>livestreamer --twitch-oauth-token  https://www.twitch.tv/asmodaitv best
[cli][info] Found matching plugin twitch for URL https://www.twitch.tv/asmodaitv
[plugin.twitch][info] Attempting to authenticate using OAuth token
[plugin.twitch][error] Failed to authenticate, the access token is invalid or missing required scope
[cli][info] Available streams: audio, high, low, medium, mobile (worst), source (best)
[cli][info] Opening stream: source (hls)
[cli][info] Starting player: 'C:\Program Files (x86)\VideoLAN\VLC\vlc.exe'
This leads to twitch-livestreamer-gui not working, it rejects the token as invalid. After this, the stream starts regularily in VLC.

I cannot reproduce the issue. Maybe the API was on the fritz.


Assets required

Need these icons
The assets attached are not correctly displayed
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/3a269cfa-6af3-4aba-a644-67d52ea1ca61/specs/
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/e8f62e6f-d5a4-43fc-8420-bc54e1236a56/specs/
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/fc919e29-b7c7-4657-bb06-c4cd279cbe47/specs/
Note: Left screenshot is of design and right screenshot is of app

Need these icons
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/6300f10c-0dc8-4cd8-b420-7654b055d8e1/specs/

need collaborative wallet icon. The design does not have a collaborative wallet variant for this screen.
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/bd388c80-b4f6-4d71-902e-25fb716b060c/specs/

https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/e8f62e6f-d5a4-43fc-8420-bc54e1236a56/
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/fc919e29-b7c7-4657-bb06-c4cd279cbe47/
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/f1271953-23ac-413b-993a-676cba904f91/

@summikhan11 Collaborative wallet icon is not  attached to assets in this screen.
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/f1271953-23ac-413b-993a-676cba904f91/

Verified this issue on keeper app v 1.2.0(319)


Prevent type confusion through parameter tampering

The fpath parameter can be manipulated by passing it multiple times:
https://lgtm.com/projects/g/adobe/git-server/alerts/?mode=tree&ruleFocus=1506301137371
https://lgtm.com/rules/1506301137371/

Codecov Report

Merging #15 into master will decrease coverage by 0.2%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   78.57%   78.36%   -0.21%
==========================================
  Files           9        9
  Lines         280      282       +2
  Branches       35       36       +1
==========================================
+ Hits          220      221       +1
- Misses         60       61       +1

Impacted Files
Coverage Δ

lib/commitHandler.js
60.34% <50%> (-0.37%)
:arrow_down:

Continue to review full report at Codecov.

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


Playing with qmake and build options. Cleanup.


Improve performance of dilation with large kernels

Input
A graph g (Image::<Ternary>) and a kernel ker (Image::<bool>).
Output
The dilated graph g_out (Image::<Ternary>).
Algorithm

Decompose g into two images:
g_t ← true pixels mapped to 1 and the others to 0,
g_u ← uncertain pixels mapped to 1 and the others to 0.
Apply FFT to g_t, g_u, and ker.
g_t ← g_t ⊙ ker,
g_u ← g_u ⊙ ker.
Apply IFFT to g_t and g_u.
g_out ← non-zero pixels of g_t mapped to true, other non-zero pixels of g_u mapped to uncertain, and the others set to false.
Note that the non-zero test may require some threshold.

any plan on vector tracing and curve offseting for antialiasing, instead of bitmap dilation? though somehow risky, but potentially energy-saving for smoother picture for most nice functions. (i.e. other than real ^ and gcd and some other discrete monsters).
this might help: https://pomax.github.io/bezierinfo/#offsetting

Hi!
I think dilation by convolution as currently implemented is not so slow. However, it is certainly an interesting topic to produce error-bounded vector traces of line-like graphs (or more)!


NaiveDateTime Duration math seems slightly incorrect

#[test]
fn test() {
    let base = chrono::NaiveDate::from_ymd(2000, 1, 1).and_hms(0, 0, 0);
    let t = -946684799990000;
    let time = base + chrono::Duration::microseconds(t);
    assert_eq!(t, (time - base).num_microseconds().unwrap());
}

thread 'types::chrono::test' panicked at 'assertion failed: `(left == right)` (left: `-946684799990000`, right: `-946684796695032`)', tests/types/chrono.rs:23

Interestingly, this version does pass:
#[test]
fn test() {
    let base = chrono::NaiveDate::from_ymd(2000, 1, 1).and_hms(0, 0, 0);
    let t = -946684799990000;
    let time = base - chrono::Duration::microseconds(t);
    assert_eq!(t, (base - time).num_microseconds().unwrap());
}

This was very, very subtle bug that has escaped existing tests. I probably have to prepare systematic tests soon... Thank you so much!

Thanks for fixing it!


Azure Function timer trigger unclear on v2 doc

[Enter feedback here]
I found hard to understand what's the things needs to be done to make a function timer trigger here.
All the chatgpt is giving v1 answer where need function.json
some chatgpt v2 is always giving same official doc answer which is quite hard to understand.
why does it has to be main function? can it be just normal functions?
what's the code needs to add as decorator? Is it just ", timer: func.TimerRequest" as part of function parameter?
what's the repeat schedule about?
Can I write a Http Trigger function, and every time it get called, it will run a function 5 minutes later?
E.g. I want to write a JSON to database and I want to trigger 5 minutes later delete that json ? How to do it?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b5527c3b-a5da-c73d-66c2-20d96003ff7c
Version Independent ID: 42154c7b-b0e0-26db-79bc-3f1673c48e40
Content: Timer trigger for Azure Functions
Content Source: articles/azure-functions/functions-bindings-timer.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@jacobjiangwei
Thanks for your feedback! We will investigate and update as appropriate.

Moreover, the python documentation links to C# and node snippets


athena: pagination to listDataDirectory

Fixes #24571
Description
@adeebshihadeh, @jnewb1, @gregjhogan,  can you please take a look at this PR.
I added pagination to listDataDirectory method in athenad.py file, and created test method in test_athenad.py file.
Is this the implementation that was required by the issue? This returns just one batch (page) at the time, for example there is way it can yield all the batches, or save last file that passed etc. I didn't do it that way because i wanted input from you guys.
Verification
I run pre-commit hooks and python tests run via pytest

Hi @gregjhogan , i saw you commented on PR #32013, can you take a look at this too, please. I need some inputs.

@gregjhogan did you have an intended use case for this (smart downloader?) or was it just an idea? if not think we should just close this and the issue

On slow network connections I have seen it be completely unusable in the current state because the request will always time out listing a large number of segments. This can cause devices to never get segments enqueued for smart downloader, but I don't think it is a common or significant issue currently.


New Logo Design for Minimal Todo

Hello sir, my name is Samet Ceylan and I am a designer. If you want and let me, I want to design a creative logo for Minimal Todo. I want you to know that I will do it for you. I do not want any compensation. If you would like me to design and if you have any particular detail, please contact me.

@sametceylan that would be great. I'm excited to see what you come up with.

@avjinder well. Do you have an idea or task about logo? I can create as your requests

@sametceylan I'd like to see what you come up with. Surprise us all.

@sametceylan Hey could you possibly think of making a logo/icon for my app Jurassic Gains? That would be cool. Thanks!

Hi @BUInvent. Hi, my name is Munadi Kiehl. I'm a graphic designer and I would like to collaborate on your open source project and to propose free icon/logo design. If you're interested in, please, let me know.
Best Regard,
Munadi Kiehl

Yes @munadikiehl. Yes I most definitely am interested. Thanks for asking!

@munadikiehl Maybe we should setup a chat somewhere like on Google Hangouts. Let me know.

Hi @BUInvent. Thanks for your feedback. Do you have discord to continue our discussion.

Yes I do we will have to exchange discord #'s. Mine is #3398

Hmm... didn’t work. I cannot find your account. May be you can try invite my account : munadikiehl#0187

Just sent friend request


Remove lodash dependency to reduce bundle size?

I wonder what you thought about the idea of using native JavaScript functions instead of lodash?
In my minified bundle, lodash takes up 41 KB in addition to Chevrotain's 136 KB, so it seems that this would probably be the biggest opportunity for reducing bundle size (#1697).
JavaScript has gained a lot of the utility functions provided by lodash in the past 10 years, so this change might be a lot more doable than it was a few years ago.
It might also be worth bumping the minimum JavaScript version to something like ES2020 in the same go, so that we get access to most of the new functions. ES2020 is currently compatible with ~95% of global web users' browsers, down from 98% for ES2015.

Great points! Do you think you would be able to create a PR with these replacements?

Sure, I'd volunteer a PR. I think having a minimum ES version to target (preferably larger than 2015) would be the main thing I need to get going.

In regards to the compilation target.
I recently started working on a switch to ESM modules.

https://github.com/Chevrotain/chevrotain/compare/master...esm#diff-0b280a445be167f54cd916c0718c952b8e0d4ca9621903d05eec25efd4c6ed6d

That turned out a lot bigger than initially expected and is currently shelved until I have more time to invest in it.

Do we need to switch to ESM to support ES2015? I don't think so?
@joliss what lodash functions in use could be replaced by native 2015 methods? That would help understand the size of the change. It might be that only one or two utility methods would need to be re-introduced.
@bd82 do you have a minimum ES language target? 2015 is 7 years ago, surprisingly!

do you have a minimum ES language target? 2015 is 7 years ago, surprisingly!

Whatever works on the oldest still supported nodejs version
and supported in major greenfield browsers.

I wasn't looking to change the compile target, but rather just to bump the advertised compatible ES version.

What is the value proposition in that? this would be "officially" a breaking change...

@bd82 seems like @joliss's PR was merged into https://github.com/Chevrotain/chevrotain/tree/remove_lodash, but not released. We're trying to switch MermaidJS' parser to Langium, which uses chevrotain.
Bundle size is a big concern for us and would really appreciate it if @joliss' changes make it to a release.
Perhaps you were waiting for NodeJS 14 EOL (April 2023)?

Hello @sidharthv96
I am a-lot less active on Chevrotain recently...
I will try taking a peek at this in the next couple of weeks, but I can't make any promises...

@bd82 thanks for creating such a wonderful tool and also for the prompt response. I've created a PR https://github.com/Chevrotain/chevrotain/pull/1942 which you can review.

I tried out almost all available grammar tools and none checked all the boxes like Chevrotain did.
We started work on the migration last year with https://github.com/mermaid-js/mermaid/pull/3432, which is superseded by https://github.com/mermaid-js/mermaid/pull/4450 using langium (chevrotain under the hood).
I genuinely understand shifting priorities and that we don't have any obligations for maintaining previous work. Moreover, things like CJS vs ESM and export maps are very frustrating things to do, outside our core product (I've personally dealt with it in Mermaid).
But as a potential user of chevrotain, we were wondering what the redundancy plans are for chevrotain, do you have other trusted maintainers who could help with the maintenance? If not, could we discuss something for this please?

@sidharthv96 you are welcome 😄

But as a potential user of chevrotain, we were wondering what the redundancy plans are for chevrotain, do you have other trusted maintainers who could help with the maintenance? If not, could we discuss something for this please?

msujew from langium has write permissions to this repo and helps mainly by answering questions on the discussions tab.
I would definitively not mind having additional maintainers, but I am not sure how to achieve this...
The project is in the "maintenance" phase of the life-cycle with most of the remaining work not being particularly glamorous, e.g:

migrate https://github.com/bd82/regexp-to-ast into this repo
support newer ECMAScript regexp syntax
ESM support.
Improve Bundling.

I have a little more free time recently and will try to push some of these items...

All-right @sidharthv96 @joliss I have status update:
Removing lodash with ECMAScript built-ins #1949:
I'm not going to merge this.
I've invested a few hours into reviewing this and beginning code review fixes.
However, I've encountered several issues:

Lexer performance reduced by 5% in JSON lexer benchmark.

Strange because I thought such utils were avoided in hot-spots.

Readability decreased imho,

e.g: https://github.com/you-dont-need/You-Dont-Need-Lodash-Underscore/issues/333

I ended up re-implementing some library utils for readability which is what I wanted to avoid in the first place
when I introduced lodash.

indentation changes (unavoidable) are causing larger than optimal diffs to review.

Replacing lodash with just-* libraries #1950
Just-* is a minimalist and tiny implementation of lodash like utils.

https://github.com/angus-c/just

This approach is temporarily shelved
until I can evaluate what I suspect to be a better approach see below.
Basically the idea is to replace only the from clause of import statements, e.g:

`import values from "lodash/values" --> import values from "just-values"

However, I've encountered several issues:

Logic bug: https://github.com/angus-c/just/issues/564
Lower quality TypeScript signatures versus Lodash --> solved by casting and / or re-typing.
Less edge case handling --> solved by wrapping just-* functions in @chevrotain/utils/src/library.ts
Missing utilities, particularly the basic ones (e.g map/forEach) resulting in either:

mixing style of coding (built-ins vs library utils)
implementing additional library utils myself.

I am also a little wary of performance implications, as performance is not one of the goals of just-*
And while these library utils are not supposed to be used in runtime(parsing) hot-spots,
they are definitively used in "design time" analysis (construction) of the parser instance.
Considering the above points and Looking into just-* tradeoffs it seems as though just-* may not be the "best tool for job"

Replacing lodash with Remda

https://github.com/remeda/remeda#remeda-design-goals

Remda is:

Designed to have "minimal" functions and support tree-shaking.
Seems to include most(all?) of the utilities needed, including built-ins such as map/forEach.
Has docs to assist in the conversion: https://github.com/remeda/remeda/blob/master/mapping.md

So it seems to match all the requirements and may reduce bundle size by ~15% while keeping
the benefits of a "standard library".
The one blocker is that it requires ES6 (or polyfills).
So I will first need to do a breaking-change and change the compilation target.

In #1952 there is a POC to replace lodash with remeda This seems to reduce bundle size (.min) by ~20Kb.
However, it also causes a performance regression in parser/lexer initialization time.
Perhaps the best approach would be to re-implement these utilities inside chevrotain

There are about ~30 of these.
Implementation, may simply defer to built-in utils in many cases with some param checks.
compile target was upgraded from ES5 --> ES2015, so more of the built-ins are available to defer to.

Normally I would not consider it worth-while just to save 20-30Kb of bundle size.
However, if native implementation can also provide a significant init speed boost, then it may be worth exploring

The following steps reduced the *.min bundle size to ~136K-140K: (umd/esm)

Switching to target=ES2015
Compiling to esm modules instead of commonjs modules (Pure ESM).
Switching to lodash-es (tree shaking?).

These will be released in version 11.0.0 as they are breaking changes.

I know this is closed, but still persists as an issue folks would like to solve.
What about replacing lodash functions individually rather than a large all-in-one PR? For instance, replace _.isArray() with Array.isArray()? This would focus the remaining replacements that are difficult to replace (like _.uniq()) down to a more manageable size.

Hello @mattbishop
For me this is past the point of diminishing returns.
I am not planning on investing additional effort into this topic.
Nor am I interested in accepting the compromises / inconsistencies of hybrid solutions or implementing the relevant utils directly.


Governance. Delegate activity. Go to Voted history may lead to crash

Description

Environment
https://github.com/novasamatech/nova-spektr/commit/e46cf22783eb1b45d361fdd4fc63e8f9277da5b0

Status verification: ✅


[netcpp] Update to 0.4.1

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@MonicaLiu0311  In my environment, I successfully installed this package on Linux with local vcpkg. Can you show me the error log?

Download CI log artifacts at
https://dev.azure.com/vcpkg/public/_build/results?buildId=106304&view=artifacts&pathAsName=false&type=publishedArtifacts
FAILED: src/CMakeFiles/netcpp.dir/native.cpp.o
/usr/bin/c++ -DNETCPP_BUILD -D_LIBCPP_ENABLE_EXPERIMENTAL -I/mnt/vcpkg-ci/b/netcpp/src/v0.4.1-25bd05a929.clean/src/include -I/mnt/vcpkg-ci/b/netcpp/src/v0.4.1-25bd05a929.clean/include -fPIC -g -std=gnu++20 -MD -MT src/CMakeFiles/netcpp.dir/native.cpp.o -MF src/CMakeFiles/netcpp.dir/native.cpp.o.d -o src/CMakeFiles/netcpp.dir/native.cpp.o -c /mnt/vcpkg-ci/b/netcpp/src/v0.4.1-25bd05a929.clean/src/native.cpp
In file included from /mnt/vcpkg-ci/b/netcpp/src/v0.4.1-25bd05a929.clean/src/native.cpp:1:
/mnt/vcpkg-ci/b/netcpp/src/v0.4.1-25bd05a929.clean/include/net/native.hpp:30:10: fatal error: liburing.h: No such file or directory
   30 | #include <liburing.h>
      |          ^~~~~~~~~~~~

Look like it lacks the -I... for using vcpkg's liburing.
And actually I don't see any relevant lookup in CMakeLists.txt. You will have to patch it. liburing provides pkg-config files.

The CI has passed. But it still couldn't find {TRIPLET}/lib/liburing/liburing.pc file. How do I modify it?
error log:
/usr/bin/ld: cannot find -luring: No such file or directory

I'm trying to create a new app with vcpkg manifest and link this package. and find liburing.pc and add cmake command link_directories. But still it makes -luring not found error.

I created a new app with vcpkg manifest and linked this package. I also use liburing.pc file with pkg-config to add cmake command link_directories. But It still makes -luring not found error. How to resolve it?

I resolve it to add link_directories at root CMakeLists.txt. I'm sorry my cmake skills are not good...

The usage test passed on x64-linux (header files found):
netcpp provides CMake targets:

    find_package(netcpp CONFIG REQUIRED)
    target_link_libraries(main PRIVATE netcpp::netcpp)

Thanks for the review


Build: investigate generating dbt project documentation during builds

As the project continues to grow, I think it would be useful to build the dbt project documentation during builds.
Additionally, if we add Superset entities as exposures, this documentation could improve discoverability of new charts and datasets and would allow stakeholders to research questions of data provenance without going through the project code.
Here are some questions I think should be considered before adding a build step to generate documentation:

The dbt docs generate command writes documentation as HTML. Once the documentation is built, how is it going to be served?
How can we programmatically add Superset assets such that the documentation always stays in sync with what's available in Superset?

Closed by https://github.com/openedx/aspects-dbt/pull/31


Adding/update user and company profile endpoints

User is expected to have several data ie dp, cv, title, bio, about, website... We expect to have add dp and add cv routes separately, and add profile route... This also means there is a need to add these data while fetching user.
Same goes for the company endpoint, we need company logo, email, about, bio as shown in the design @BaharaJr @iam-budodi @nab-in/backend

Hello, @bmsteven may you please clarify this. Thank you.

Hello, @bmsteven may you please clarify this. Thank you.

User and company will need additional profile information.
User should be able to upload their profile pictures and CV, also they should be able to add details about themselves such as bio, about, title(like a software developer), website etc as per design.
A company too needs a logo and some other info as per design

I think these details are mentioned in readme


Update condition of spec components

Related Issue

Fixes #
Checklist:

[ ] I have read the contributor's guide.
[ ] I linked an issue in the previous section
[ ] I have commented on the linked issue
[ ] I was assigned the linked issue (not required)
[ ] I have tested the change to the best of my ability against the sandbox or a local build.

Optional items:

[ ] My change adds new text and requires a change to translations.
[ ] My change requires a change to the documentation.
[ ] I have submitted a PR to the documentation repo.
[ ] I was not able to test... (explain below, e.g. you did not have permissions to test a specific feature)
[ ] This change depends O-FISH Realm repository changes (explain below)

Optional: Add any explanations here

Optional: Add any relevant screenshots here

This change affected the filters. I tested the date and risk level filters and they still work, so I'll accept this.


CC-BY-NC-SA 4.0 misidentified

GitHub is identifying the following as CC-BY-SA:
https://github.com/awsdocs/aws-go-developer-guide/blob/master/LICENSE
Licensee 9.2.1 gives me:
$ licensee aws-go-developer-guide/
License: Other
Matched files: ["LICENSE"]
LICENSE:
Content hash: 25d0e91dacd76fecc5e7d2e2c47ede1da4fed28e
License: Other
Closest licenses:
* MPL-2.0 similarity: 42.93%
* GPL-2.0 similarity: 39.31%
This is presumably because I have removed the parts of the CC license that do not relate to the license.
In both cases the expected result is that it should identify it as X% CC-BY-NC-SA 4.0; and I should be grumbling that SPDX have too much text in their license file.

Mostly because it was detected before better false positive avoidance for non-open CC licenses was implemented in https://github.com/benbalter/licensee/pull/168
I believe if you update the file or ask https://github.com/contact for that repo's license to be re-detected, no license will be identified.

Thanks. I'm going to be changing the license, so that should take care of the GitHub 'bug'.
Should licensee do a better job at matching the license text rather than pointing to MPL or GPL?

Maybe. The reason it gives a non-intuitive list of closest matches is that it only even tries to match licenses that are close in length. With that and the CC false positive check turned off locally, I get:
$ script/git-repo https://github.com/awsdocs/aws-go-developer-guide
License: Other
Matched files: ["LICENSE"]
LICENSE:
  Content hash: 25d0e91dacd76fecc5e7d2e2c47ede1da4fed28e
  License: Other
  Closest licenses:
    * CC-BY-SA-4.0 similarity: 90.06%
    * CC-BY-4.0 similarity: 88.35%
    * AFL-3.0 similarity: 46.33%
    * OSL-3.0 similarity: 46.15%
    * EUPL-1.1 similarity: 45.81%
    * EPL-1.0 similarity: 42.95%
    * MPL-2.0 similarity: 42.93%
    * CC0-1.0 similarity: 42.73%
    * Apache-2.0 similarity: 42.66%
    * ECL-2.0 similarity: 42.25%
    * AGPL-3.0 similarity: 39.78%
    * GPL-3.0 similarity: 39.65%
    * GPL-2.0 similarity: 39.31%
    * Artistic-2.0 similarity: 37.40%
    * LGPL-2.1 similarity: 35.72%
    * LPPL-1.3c similarity: 35.25%
    * LGPL-3.0 similarity: 30.98%
    * OFL-1.1 similarity: 30.53%
    * MS-RL similarity: 30.22%
    * MS-PL similarity: 28.92%
    * BSD-3-Clause-Clear similarity: 26.58%
    * BSD-3-Clause similarity: 24.72%
    * BSL-1.0 similarity: 22.98%
    * BSD-2-Clause similarity: 22.73%
    * NCSA similarity: 22.44%
    * PostgreSQL similarity: 20.44%
    * MIT similarity: 20.07%
    * Unlicense similarity: 19.74%
    * ISC similarity: 17.80%
    * Zlib similarity: 17.47%
    * WTFPL similarity: 7.72%

I guess that's a curiosity, and more intuitive than the result without that modification. But usually note useful to do the comparisons we know aren't going to match.


Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
passed all the tasks from description
What did you learn from the changes you have made?
to work with np
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I provided some in comments
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
no
How were these changes tested?
manually
A reference to a related issue in your repository (if applicable)
n/a
Checklist

[ x] I can confirm that my changes are working as intended

Thanks for your assesment!
I've just reexecute all functions and output got "False". I had reexecuted it and added space to create new commit ))
I think I was playing with different parametrs and when I went back for final version the output was from previous execution with another parametrs.


Do not fetch fonts that have already been fetched

I have a function that calls this
WebFont.load({
      google: {
        families: requiredFonts
      }
});

This requiredFonts is computed based on which page number the user clicks from the pagination tab. I want that if the user comes back to a page then WebFont.load should NOT fetch the requiredFonts again and instead get them from the cache. Currently, it keeps making the calls for the fonts that have already been fetched before.
Request Header: cache-control: no-cache
Response Header: cache-control: public, max-age=31536000
Can someone please tell me how I can ensure that it refetches the fonts from the cache instead of making the call again? P.s i am using the fonts that I fetch.

Turns out my disable cache was on.


adjusted font size of result display

Coverage remained the same at 92.162% when pulling bf437745cb119158819c2d56a88584df93a05aeb on ALim95:UI_imageFeedBack into 48708a8cea44be48a2adb7abaa81cd152648848d on CS2103AUG2017-T15-B4:master.


Improve devonfw Java quality profile

With issue #16 implemented by PR #56 we now automatically provide a standard devonfw Java quality profile to SonarQube.
This comes from here:https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/resources/com/devonfw/ide/sonarqube/common/rules/devon4j/devon4j.xml
We need feedback from projects if this is a suitable default.
Obviously you can have endless discussions about this, but everyone is invited to provide feedback and request for change if a rationale is given. Examples are

we might miss out a cool new rule that you suggest to add by default telling what the rule archives and linking to details. The rule should not produce many false-positives if the suggested default severity is higher than info
we might use a rule that is deprecated or otherwise replaced by a newer and better rule.
we might include a rule with a too high or too low severity. Please explain in detail why you want to raise or lower the severity. Give examples whenever possible.

My first feedback:

squid:S2699 (Add at least one assertion to this test case.) - This rule is creating issues of severity Blocker.  It does not support soft-assertions. It does not support when a test method delegates to a reused check-method that does the actual assertions, etc. So in the end it is better to entirely disable this rule (or at least put it down to Info severity).

Status:

[X] S2699 - severity lowered from blocker to info
[X] S3369 - no problem: devon4j projects do not have web.xml anymore. Projects that do have it might take value from the rule or mark the single finding as not an issue/false positive.
[X] S2063 - has been removed
[X] S00121 - no problem: rule is fine. We need to fix devonfw-ide settings for eclipse.

Therefore considering done and closing.


<EMAIL_ADDRESS>yields (-A-B) not -(A+B)

This version is included in the 2023 redeployment on BB5, see: https://bbpgitlab.epfl.ch/hpc/nmodl/-/jobs/586400
https://github.com/BlueBrain/spack/pull/1866 was needed in order for the tests to execute.
https://github.com/BlueBrain/spack/pull/1867 is probably needed in order for nvhpc compilation to succeed.

https://bbpgitlab.epfl.ch/hpc/nmodl/-/pipelines/106578 was launched with it; setting SPACK_BRANCH is not enough because we need the deployed Spack configuration too

CI_BRANCHES:SPACK_BRANCH=olupton/thou-shalt-not-use-submodules

We can also remove the version requirement in https://github.com/BlueBrain/nmodl/blob/master/requirements.txt

We can also remove the version requirement in https://github.com/BlueBrain/nmodl/blob/master/requirements.txt

We could try, but it might just lead to more issues 🤷 This PR just gets the tests to pass for one more specific version, rather than doing anything substantive towards getting all versions to pass. So it might still be good to specify a version that we know works.

We can also remove the version requirement in https://github.com/BlueBrain/nmodl/blob/master/requirements.txt

We could try, but it might just lead to more issues shrug This PR just gets the tests to pass for one more specific version, rather than doing anything substantive towards getting all versions to pass. So it might still be good to specify a version that we know works.

I can check again but IIRC this was the only failing test with the newest sympy version


Add windowed exponentiation for (Dyn)Residue

Made pow_montgomery_form() windowed; measured speedup is ~ 35us to 23.1us
Added proptests for pow() and pow_specific() for DynResidue
Added DynResidue::one()

Thanks!


OOM if setting concurrentHTTP1ConnectionsPerHostSoftLimit: .max

I would like to make the pool create as many concurrent connections as possible. So I thought the best way of spelling this is
        var httpClientConfig = HTTPClient.Configuration()
        httpClientConfig.connectionPool = .init(
            idleTimeout: .hours(1),
            concurrentHTTP1ConnectionsPerHostSoftLimit: .max
        )
        httpClientConfig.timeout = .init(connect: .seconds(10), read: .seconds(100), write: .seconds(100))

unfortunately, the concurrentHTTP1ConnectionsPerHostSoftLimit: .max makes AHC OOM even before it creates any connections because HTTPConnectionPool.HTTP1Connections.init() preallocates an array of that size.
It shouldn't do that or at least cap it to something reasonable like 1024.

@weissi Do you think it should cap the actual pool size at 1024, or it should pre-initialize the first 1024, but allow making more of the app is actually trying to use more?
I'm not 100% certain but it feels like 1024 should be enough for any single connection pool?

or it should pre-initialize the first 1024, but allow making more of the app is actually trying to use more?

That's what which has been implemented.

I'm not 100% certain but it feels like 1024 should be enough for any single connection pool?

I wouldn't put a relatively arbitrary limit like that. We connect to our own internal services over http and there can be a lot of connections, although I don't think we've reached 1024.


The WACK always returns an error

No matter what I do, the app manifest resources test is 'blocked from execution'
I'm not at my PC right now, so don't have the exact error to hand

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bea36edd-22d6-7d1e-73c3-63d8f276d679
Version Independent ID: a50a03aa-e89d-55da-43ba-b23155b9bbaf
Content: Windows App Certification Kit - UWP applications
Content Source: windows-apps-src/debug-test-perf/windows-app-certification-kit.md
Product: uwp
Technology: deployment
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: kbridge

Hi @TechPhil - This feedback is not specifically about the documentation, but rather a support request. Please contact the following support channel.

For developer issues, or suspected product bugs, there's Microsoft Support; a support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.

Here are all of the developer support resources, for completeness.

The Feedback Hub app is the right place to lobby for a change, a feature, or to make a suggestion.
For community assistance with development questions, there are our forums, and StackOverflow.
The Windows developer support site explains other support options.
The Visual Studio developer community is available, and responsive. The former User Voice feature is now there on the Suggest a feature tab, if you want to lobby for a change, a feature, or to make a suggestion.

If you receive assistance via any support resource, and you believe that information would help us improve the docs, then please come back and let us know.


utf8proc: 2.2.0 -> 2.3.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/utf8proc/versions.
meta.description for utf8proc is: '"A clean C library for processing UTF-8 Unicode data"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.3.0 with grep in /nix/store/2mpzpg04lj3swy8sxgnwl4frj9rmdmdc-utf8proc-2.3.0
directory tree listing: https://gist.github.com/580d57bc3facbddbc20987efec0041f0
du listing: https://gist.github.com/a045f6f01685145a22bc01222c2e8a74

Rebuild report (if merged into master) (click to expand)

141 total rebuild path(s)
41 package rebuild(s)
41 x86_64-linux rebuild(s)
39 i686-linux rebuild(s)
32 x86_64-darwin rebuild(s)
29 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
cabal2nix
chronos
dep2nix
gitAndTools.gitFastExport
gitAndTools.gitFull
gitAndTools.gitSVN
gitAndTools.svn-all-fast-export
gitAndTools.svn2git
gitAndTools.svn_all_fast_export
gitFull
gitSVN
hydra
julia
julia_07
julia_1
julia_10
julia_11
marathon
mesos
muse
nix-prefetch-scripts
nix-prefetch-svn
nix-update-source
perl528Packages.SVNSimple
perldevelPackages.SVNSimple
python27Packages.pysvn
rabbitvcs
rapidsvn
reposurgeon
spark
spark_22
subversion
subversionClient
subversion_1_10
subversion_1_11
svn2git
svnfs
urjtag
utf8proc
vcstool
ydiff

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2mpzpg04lj3swy8sxgnwl4frj9rmdmdc-utf8proc-2.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A utf8proc https://github.com/r-ryantm/nixpkgs/archive/a0703af2815e2154f84131a3bf375594cc06eff5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2mpzpg04lj3swy8sxgnwl4frj9rmdmdc-utf8proc-2.3.0
ls -la /nix/store/2mpzpg04lj3swy8sxgnwl4frj9rmdmdc-utf8proc-2.3.0/bin

cc @ftrvxmtrx for testing.

@GrahamcOfBorg build subversion
@GrahamcOfBorg build julia
@GrahamcOfBorg build hydra
@GrahamcOfBorg build nix-prefetch-scripts
@GrahamcOfBorg build gitFull
@GrahamcOfBorg build cabal2nix

For trace:
utf8proc subversion nix-prefetch-scripts hydra gitFull cabal2nix succeeded
julia timed out

@GrahamcOfBorg build hydra
@GrahamcOfBorg build nix-prefetch-scripts

I built julia_11 locally. julia could not complete because it got killed by the oom_reaper during the stress test (in a 16GiB VM!) but it went through the whole build phase without issue nonetheless


Cite NIST OSCAL Tools Page, Explain How We Don't Duplicate It

I meant this for Awesome OSCAL, woops! Transferring in 3 ... 2 ... 1...


Menu entry swapper

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 11
Bug description
The menu entry swapper used for having the "pay" option on farmers as the number 1 choice does no longer work. each time I log in the main option is set back to "trade" instead of pay.
Screenshots or videos
No response
RuneLite version
Runelite Version: 1.10.38
Launcher version: 2.7.2
Logs
No response

Added in e3a2c3edd6f069b99ebdbac9776042cf994e38ce


TangQingYing

TQYtqy12345678

good

I think it's good.

Thanks. We will wait for your suggestion with appreciation


Technical/fix kotlin version

https://cafonsomota.medium.com/getting-rid-of-those-red-underline-errors-on-your-kmp-project-ios-8a2273cae61a

these changes are not necessary right now.


fileFormatVersion and vendorName tags not being captured from XML

Hi,
I have started to use measdatacollectionparser and I have noticed that the resulting CSV file is not including fileFormatVersion and vendorName tags (those columns are empty). After taking a look to the source code and comparing with the 3GPP XML Specification, in my opinion those tags are located at fileHeader area, however the code is trying to find them at fileSender area and is not being success and it is the reason.
localDN attribute is just the opposite (it belongs to fileSender), but because fileSender is a subset of fileHeader, it still works.
Best regards, Jose
if (tag == "fileHeader") {
            for (m <- attrs) {
              if (m.key == "localDn") fileSenderLocalDn = m.value.toString()
              if (m.key == "elementType") elementType = m.value.toString()
              if (m.key == "dnPrefix") fileHeaderDnPrefix = m.value.toString()
            }
          }

          if (tag == "fileSender") {
            for (m <- attrs) {
              if (m.key == "fileFormatVersion") fileFormatVersion = m.value.toString()
              if (m.key == "vendorName") vendorName = m.value.toString()
            }
          }

@jsanz01, I have checked and you are very correct.  Let me correct that.

Resolved by PR #8


simplify code

simplify code

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@00f7638). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #257   +/-   ##
=========================================
  Coverage          ?   80.13%
=========================================
  Files             ?       19
  Lines             ?     1601
  Branches          ?        0
=========================================
  Hits              ?     1283
  Misses            ?      281
  Partials          ?       37

Continue to review full report at Codecov.

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


Resume detox recorder to simplify element identification and make detox easier

Describe your idea
It's regret to stop detox recorder support due to lack of manpower. auto recorder is an effective approach to simplify coding and a way to increase efficiency.
Not sure if it will be resumed in someday. I hope detox would align with other open source framework and make it better. Also, to support iOS real device.
I haven't found a better tool than Detox for RN app.

@aaronpliu Thanks, we might actually resume work on the recorder one day because of it will provide us great value as testers, as well. Nevertheless at the moment any improvement in the project will be based on voluntary contribution.

There's a repo for detox-recorder project (this is not part of detox itself). You can open this discussion there, maybe someone will be willing to contribute fixes to this open source project.
https://github.com/wix-incubator/DetoxRecorder


feat: add file uploads to request body

continuation of https://github.com/scalar/scalar/pull/1966
needs some polish from @cameronrohani :)

worked with @geoffgscott on the binary file upload option, we will fast follow with removing axios here and using fetch : )


[Lake][DuckDB] Production tables data is getting deprecated if CSV data is deleted and refetched

How to reproduce:

go trough etl raw update flow
delete csv files
go trough etl raw update flow again and you should see that the deleted data from CSVs are duplicated inside the production tables

When it comes to the current PR written:

Our systems are not "smart". If you do what you're describing, you're breaking any sync.
If you delete data from CSV, there are no expectations that Raw or ETL tables will be updated.
GQLDF is meant to be a "dumb system". It's role is just to update the CSVs and then make sure the lake is up-to-date/syncd.

The current PR will therefore not be merged because .
When it comes to Sync, and the work that can be done to avoid duplicates:

There is a potential edge case where data already exists.
GQLDF is run to be updated so it can write new records to CSV + DuckDB
CSV is at 0, but DuckDB has rows up-to 100
When CSV goes to be updated, it resumes from 0, but DuckDB isn't clamped to 100 so it will experience duplicate records
Because there are already records in DuckDB Raw Tables, the records won't be properly handled/clamped, and we'll end up with duplicates

This still needs to be completed.


Php 7 with laravel 5.5.40 mongo db driver issue

Php 7 with laravel 5.5.40 mongo db driver issue
composer update jenssegers/mongodb
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: remove laravel/framework v5.5.40
- Conclusion: don't install laravel/framework v5.5.40
- jenssegers/mongodb v3.4.0 requires illuminate/database ^5.6 -> satisfiable
by illuminate/database[v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6
.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.3, v5.6.4, v5.6.5
, v5.6.6, v5.6.7, v5.6.8, v5.6.9].
- jenssegers/mongodb v3.4.1 requires illuminate/database ^5.6 -> satisfiable
by illuminate/database[v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6
.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.3, v5.6.4, v5.6.5
, v5.6.6, v5.6.7, v5.6.8, v5.6.9].
- jenssegers/mongodb v3.4.2 requires illuminate/database ^5.6 -> satisfiable
by illuminate/database[v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6
.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.3, v5.6.4, v5.6.5
, v5.6.6, v5.6.7, v5.6.8, v5.6.9].
- don't install illuminate/database v5.6.0|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.1|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.10|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.11|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.12|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.13|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.14|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.15|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.16|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.17|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.19|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.2|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.20|don't install laravel/framework
v5.5.40
- don't install illuminate/database v5.6.3|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.4|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.5|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.6|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.7|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.8|don't install laravel/framework v
5.5.40
- don't install illuminate/database v5.6.9|don't install laravel/framework v
5.5.40
- Installation request for laravel/framework (locked at v5.5.40, required as
5.5.*) -> satisfiable by laravel/framework[v5.5.40].
- Installation request for jenssegers/mongodb ^3.4 -> satisfiable by jensseg
ers/mongodb[v3.4.0, v3.4.1, v3.4.2].

composer require jenssegers/mongodb 3.3.1

composer require jenssegers/mongodb 3.3.1

Saved my life!


Attempt to solve inconsistent results when using genmypy cmake hooks in catkin workspace

Hey there, thanks for the rospypi effort in general!
I attempted to use this in my ROS workspaces but had very inconsistent results.
I first thought that it was because the generation of the module files were dependant on the message/services pyi files being generated. While it helped a bit I still couldn't have reproducible builds.
Looking a little bit into it, it looks like the generation of the init.pyi files is dependant on already having a proper init.py file fully generated for the module. Is that a correct assumption ?
If so by using the changes in this PR I succeeded to have reproducible and more complete init.pyi files.
The PR basically introduced a dependency between genpy finishing generating message and module files for the genmypy file generation to kick in.
How I tested this:

Made a workspace with the common_msgs repo
5 times:

Ran catkin_make_isolated
Looked at the number of lines of the generated pyi files

Using current master:
$ cat `find -name *.pyi` | wc -l
3747
$ cat `find -name *.pyi` | wc -l
3749
$ cat `find -name *.pyi` | wc -l
3762
$ cat `find -name *.pyi` | wc -l
3751
$ cat `find -name *.pyi` | wc -l
3736

Using this PR:
$ cat `find -name *.pyi` | wc -l
3765
$ cat `find -name *.pyi` | wc -l
3765
$ cat `find -name *.pyi` | wc -l
3765
$ cat `find -name *.pyi` | wc -l
3765
$ cat `find -name *.pyi` | wc -l
3765

The CI error is totally unrelated to this PR. I will fix the issue, so please wait for a while :bowing_man:

I have fixed the issue at #46, so could you merge the latest master branch into your PR or rebase this branch from the master branch? Thank you!

Looks great! Thank you for your contribution!

Thanks!
Do you think this can be released in noetic in the near future🙏 ?


connect aliyun

connect to aliyun iot (iot-as.aliyuncs.com:8000) failed
but i connected success use mqttfx
clientid:1000068245:ESP8266Test:1
password is blank.
if (client.connect("1000068245:ESP8266Test:1",MQTT_USER,""))
Attempting MQTT connection...failed, rc=3 try again in 5 seconds
please help me .thanks

I changed "keep_alive =60" in pubsubclient.h，it's working now!


Add to Packagegist/Composer

Hi
I see this issue is from 2014 ;) Any status?

Hey, sorry no. Feel free to fork (or browse existing forks) as I have no time/use for this package anymore unfortunately. Sorry!


CB-3013 alter Snowflake session parameter on start

to avoid SELECT statement reading issues

Knowable issue for now: SELECT CURRENT_DATABASE(), CURRENT_SCHEMA() is working before ALTER SESSION, and because of that, we do not see the default catalog at the start (if it is not in the bootstrap settings).

Any other ideas are welcome. Because I do not know - what if old Sbowlake databases do not support
ALTER SESSION SET JDBC_QUERY_RESULT_FORMAT='JSON'

New code version again :D

It was a good, but incorrect solution.


remove notifications from the list

Expected Behaviour
notification should be removed from the list once it's been "tapped" on by the user.
Actual Behaviour
ON IOS 7,1,1. (iphone 4s)
     var pushService = PushNotification.init({
                            android: {
                                senderID: tindrive_anrdoid_sender_id
                            },
                            ios: {
                                senderID: tindrive_ios_sender_id,
                                gcmSandbox: true,
                                alert: "true",
                                badge: "true",
                                sound: "true"
                            },
                            windows: {}
                        });

I send a notification from a java app through the end point:
https://gcm-http.googleapis.com/gcm/send
(because I am using GCM sandbox).
I send a notification:
{
  "to": "luE0jC7ja7w:APA91bHjVRljQFxTds1Tpbfz5UK6aJzQcKHuIwrJujKufbu62IpYp75mUbqOUdVSpo3QdTq_0F6VuG__Mlk8Wz3zny-RNg98U-Zr9WqkDLls24fHpAKIXHMlJzRai72T2xCsrcuO14yJ",
  "notification": {
    "title": "hello title",
    "body": "great match!",
    "td": "2"
  }
}

the notification is displayed on the IPHONE
--> everything is fine.
the notification is displayed for "around 5 seconds" then disapear
--> perfect!
if you go on the "list of notifications" of the iphone you can see it
--> perfect!
if you tap on the notification the app launches and the on('notification') callback is called
--> perfect
the problem is that once you have done that, if you close the app (or kill it) and you go to the list of notifications on the list, the notification is still there...*(and I think it should not, it should have been removed from the list of notifcations...).
*
And if you tap on the notification again, then the on('notification') callback is called again for the same notification.
--> that's a problem!
so my question is:
how do you remove the notification from the list once it has been handled?
thank you
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
ON IOS 7,1,1. (iphone 4s)
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Cordova CLI version and cordova platform version
cordova --version                                    5,4,1
cordova platform version IOS                   3.9.2

Plugin version
cordova plugin version | grep phonegap-plugin-push   1.5.3

Sample Push Data Payload
Sample Code that illustrates the problem
Logs taken while reproducing problem

I can't reproduce this and iOS7 is not supported anymore.


Fixes for importing DDS textures

Enable cluster fit option, increases image quality by reducing compression artifacts.
Specify that we don't want mipmaps to ImageMagick, it seems to add them by default otherwise. Saves around 25KB for a 256x256 image.
Minor formatting fixes.
With these changes UPFF seems to be on-par with the built-in Unity DDS texture importing.

LGTM


feat: add react email implementation

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Add React.email implementation and remove styled-components.
After the merge this issue is redundant.
What is the current behavior?
Emails are styled by styled-components - issue
What is the new behavior?
Emails are styled by tailwind

It would be great to see the react-email come to life! As a user of saas boilerplate, I would greatly appreciate the flexibility to create more email templates with a pre-tested components library. One idea to throw around: would it be possible to keep using storybook instead of rely on react-email for email template previewing?  That would keep the component library in one place and avoid running multiple platform just to preview.


MethodError: transcode(::Type{CodecZlib.ZlibCompressor}, ::String) is ambiguous

After updating packages, this diagram errors
Kroki.Diagram(:Mermaid, "
graph LR
    MTK[ModelingToolkit
model] -->|Linearize| CS[ControlSystems
model]
    CS --> D{Control
design}
    D --> V1{Linear
Verification}
    V1 -->|ODESys| MTK2[ModelingToolkit
model]
    MTK2 --> S{Nonlinear
simulation}
    V1 -->|Refine| D
    S --> V2{Nonlinear
Verification}
    V2 -->|Refine| D
    V2 --> C-code
    classDef cMTK fill:#f66,stroke:#333;
    classDef cCS fill:#66f,stroke:#333;
    class MTK,MTK2,S,V2 cMTK;
    class CS,D,V1 cCS;
")

Failed to show value:

MethodError: transcode(::Type{CodecZlib.ZlibCompressor}, ::String) is ambiguous. Candidates:

transcode(T, src::String) in Base at c.jl:291

transcode(::Type{C}, args...) where C<:TranscodingStreams.Codec in TranscodingStreams at /home/jrun/data/.julia/packages/TranscodingStreams/5yQuA/src/transcode.jl:33

Possible fix, define

transcode(::Type{C}, ::String) where C<:TranscodingStreams.Codec

var"#render#4"(::Dict{String, String}, ::typeof(Kroki.render), ::Kroki.Diagram, ::String)@Kroki.jl:172
render@Kroki.jl:149[inlined]
show(::IOContext{IOBuffer}, ::MIME{Symbol("image/svg+xml")}, ::Kroki.Diagram)@Kroki.jl:351
show_richest(::IOContext{IOBuffer}, ::Any)@PlutoRunner.jl:1170
show_richest_withreturned(::IOContext{Base.DevNull}, ::Any)@PlutoRunner.jl:1095
format_output_default(::Any, ::Any)@PlutoRunner.jl:995
var"#format_output#60"(::IOContext{Base.DevNull}, ::typeof(Main.PlutoRunner.format_output), ::Any)@PlutoRunner.jl:1012
formatted_result_of(::Base.UUID, ::Base.UUID, ::Bool, ::Vector{String}, ::Nothing, ::Module)@PlutoRunner.jl:905
top-level scope@WorkspaceManager.jl:476

JuliaSimControl docs build also errors with the same message
https://github.com/JuliaComputing/JuliaSimControl.jl/actions/runs/4681764684/jobs/8294761719

Thanks for reporting! This is the equivalent of JuliaIO/TranscodingStreams.jl#139 and appears to be caused by changes made to the signature for transcode in JuliaIO/TranscodingStreams.jl#136.
I could try to work around this here, but this seems like an issue that should be fixed in TranscodingStreams instead. If you need a quick fix, you can pin TranscodingStreams to v0.9.11 which appears to be working from some quick tests.

This has been resolved through JuliaIO/TranscodingStreams.jl#141 which has been released in<EMAIL_ADDRESS>This should now be working again as expected.


RenderDoc 1.8 Fails to compile on Arch Linux

Description
The binary release is giving me problems, so I wanted to try a local build to see if my problem persisted. During that process the build fails when it can't find a swig binary.
Steps to reproduce
Install the renderdoc package from AUR. Take a look at the PKGBUILD to clearly see what is the build command executed by the package manager.
Here's the log for the failure I'm encountering:
Scanning dependencies of target renderdoccmd
[ 95%] Building CXX object renderdoccmd/CMakeFiles/renderdoccmd.dir/renderdoccmd.cpp.o
[ 95%] Performing install step for 'custom_swig'
[ 96%] Building CXX object renderdoccmd/CMakeFiles/renderdoccmd.dir/renderdoccmd_linux.cpp.o
[ 96%] Linking CXX executable ../bin/renderdoccmd
[ 96%] Built target renderdoccmd
[ 96%] Completed 'custom_swig'
[ 96%] Built target custom_swig
Scanning dependencies of target swig-bindings
[ 97%] Generating renderdoc_python.cxx, renderdoc.py
[ 97%] Generating qrenderdoc_python.cxx, qrenderdoc.py
/bin/sh: ../bin/swig: No such file or directory
make[2]: *** [qrenderdoc/CMakeFiles/swig-bindings.dir/build.make:108: qrenderdoc/renderdoc_python.cxx] Error 127
make[2]: *** Waiting for unfinished jobs....
/bin/sh: ../bin/swig: No such file or directory
make[2]: *** [qrenderdoc/CMakeFiles/swig-bindings.dir/build.make:141: qrenderdoc/qrenderdoc_python.cxx] Error 127
make[1]: *** [CMakeFiles/Makefile2:600: qrenderdoc/CMakeFiles/swig-bindings.dir/all] Error 2
make: *** [Makefile:150: all] Error 2

Let me know if you think this is a package issue, in that case I'll dig some more.
Environment

RenderDoc version: 1.8
Operating System: Arch Linux
Graphics API: Vulkan

I do not provide any support for downstream packages. If you have a problem building directly from this repository's source then open an issue outlining how you're building and what goes wrong.


Release new major version w/ expires

expires has been added to the context, this needs a major release.

Any idea when this release will happen? Thanks.

cc: @davidlehn, we need a major release here.

Releasing this as a patch because the context was incorrect and did not match the live one; expires was not added to the context, but rather the URL is maps to was fixed to match the actual v1 context.

Actually, just checked this more closely -- it was fixed up prior to a release, so this is a major change as expires was added since the last version. This is a major version release of this package, but the live context has stablized at v1.

Version 2.0.0 has been released.


PowerShell session should not "remember" debug commands in history

Summary of the new feature / enhancement
When stepping through a function, one usually "spams" a combination of 'v' 'n' 'c' in debug mode. Once the function ends, or the user enters 'q', debug mode ends but those collection of debug commands are saved in the history of inputted commands, making it harder to find relevant commands in the history (pressing up on the keyboard) while searching through it. These debug commands should be disposed of from the history when debug mode ends because they are no longer useful in the scope of the session.
Proposed technical implementation details (optional)
No response

Good point, but note that this problem must be addressed in PSReadLine.
Perhaps a team member can transfer your issue there.

I was looking into this briefly and this would need to be added in both PSReadLine and also in core product due to duplications in how history items are dealt with so would need an issue in both to track and manage and update the areas where this is needed.
I'll get an issue in PSReadLine raised but it won't be a quick fix in either & would be an opt-out mechanism if implemented

Issue raised in PSReadLine

Thanks, @kilasuit, but I'm not sure that there's anything to be done in this repo:

Get-History does not show the debugging commands.

While interactive command recall with up-arrow does, I think this is a feature of conhost.exe and Windows Terminal windows over which PowerShell presumably has no control.

Ahh yeah I forgot that the up history of conhost/terminal is a thing too and likely we can't do anything about that in PowerShell, thou keeping this open for the WG to discuss

Related: #20738 Write-Debug expands -Message when it should SilentlyContinue

Thankfully there is an $PSDebugContext automatic variable that is available while debugging, so you can add this little snippet to your profile to make sure that debug commands are not saved:
Set-PSReadLineOption -AddToHistoryHandler {-not (Test-Path -Path 'Variable:PSDebugContext')}


asynchronous UDF functionality  - UDAs, wrapping and registration

https://msdn.microsoft.com/en-us/library/office/ff796219(v=office.14).aspx

in particular this is useful for example for long-running get/put operations.  we don't want to block excel whilst the data access operation is running.  much better to return immediately and update a status when remote server returns it.
also useful for long-running calculations

Duplicate of #35


Fix:announcements by the screen reader interrupt any existing speech

TODO comment: Use announceForAccessibilityWithOptions to queue this behind any in-progress announcements
announceForAccessibility() replaced with announceForAccessibilityWithOptions().
By default, announcements will interrupt any existing speech. they can be queued behind existing speech by setting queue to true.
fixes: #5611

Thanks! I see you created two different PRs, #5642 and #5643, for the same issue. In future please force-push to the same PR instead of making a new one, as I said at https://github.com/zulip/zulip-mobile/pull/5643#issuecomment-1398824903.
Please format your commit message according to our style: https://github.com/zulip/zulip-mobile/blob/main/docs/style.md#git-commits-commit-messages
Were you able to do any manual testing to make sure this new piece of React Native API worked as intended, without breaking anything?

Yes, As you told me previously that force-push to the same PR instead of making a new one, I had tried to do that but couldn't figure it out, Open Pull Request Button had been disabled in PR #5643 and I got confused there and opened a new PR.
Can you tell me the correct procedure to do it?
also, the commit message style part
if you explain to me how my commit is not formatted according to the zulip style then it would be really helpful.
I know, I am asking to you very silly questions but it will be very helpful for me in my growth.

For the commit message:
Fix:announcements by the screen reader interrupt any existing speech

TODO comment:Use announceForAccessibilityWithOptions to queue this behind
any in-progress announcements

By default announcements will interrupt any existing speech, but they can be queued
behind existing speech by setting queue to true in the second parameter of
announceForAccessibilityWithOptions method as it takes an object.

i have replaced announceForAccessibility() with announceForAccessibilityWithOptions().

fixes: #5611

How about:
offline notice: Queue non-urgent a11y announcements behind in-progress ones

Fixes: #5611

(That uses the abbreviation "a11y" for "accessibility" just to keep the summary line at 76 characters or below, according to our requirements.)
I think that communicates the change more efficiently to someone who's interested in this part of the project's Git commit history.

For issues with force pushing your changes to the same PR branch, please ask in #git help in the Zulip development community.

tools/test --all runs automated tests, and I don't expect those to confirm that

this new piece of React Native API worked as intended, without breaking anything

What I mean by "manual testing" is, have you run the app with TalkBack (Android) or VoiceOver (iOS) enabled, and confirmed that your commit changes the app's behavior in the way we want it to?

I have changed the commit according to zulip commit style and as you suggested to do.
Also, I have tested manually.
it works as we want to.

One commit-message nit: please capitalize the "f" in Fixes: #5611, according to our style guide and the suggestion I gave.

Also, I have tested manually.
it works as we want to.

Great, thanks! Could you walk me through your testing procedure in some more detail? In particular, if there's anything you didn't get a chance to test, please let us know so that we can test ourselves. If you tested on both iOS and Android, did you notice any differences in behavior, or did the announcement get queued on both platforms? Thanks.


Tutorial seems from 2020, how much has changed?

Hi there,
I wanted to dig into custom components a bit and found your extensive tutorial. As it has a timestamp of 2020, I am wondering how much has changed in the meantime?
Would you say the concepts still apply and it's a solid starting point?
Bye,
Jo

I've tried to do my best to update both this repository and the blog post(s) as things change.  There are definitely some best practices that are new that I haven't added (specifically around unit testing, see https://developers.home-assistant.io/docs/development_testing#writing-tests-for-integrations).
I'd say it's still a good foundation, as the integration this builds does indeed work in the latest version of HA (as of writing it's 2022.11.2 )

I am lost already at this section:

In which file does this need to go?
PLATFORM_SCHEMA seems not importable for me from anywhere

* `PLATFORM_SCHEMA` seems not importable for me from anywhere

I don't have much information to go on about your setup but it's imported here in the diff: https://github.com/boralyl/github-custom-component-tutorial/compare/feature/bare-repo...feature/part1?expand=1#diff-255aba5fb48c0aa31b860458cce10c3034d30602391ff77dbe42d0529322b6afR13

PLATFORM_SCHEMA seems not importable for me from anywhere

Sorry for the noise, PyCharm did not find the symbol although it exists. I trusted PyCharm more than the sources.


unit test for MessageType

What happened:
add unit test for MessageType

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

assign to me

常量的 ut 看起来似乎意义不大 🤖
cc @luky116

常量的 ut 看起来似乎意义不大 🤖 cc @luky116

防止大家把常量的值改了，发生问题，加个单测可以预防下

fixed in：https://github.com/seata/seata-go/commit/cf5661e9ec85bde1f06b02b91f341053a85a2369


fix: workaround provider idempotent issue

Description
Provider 1.68.0 has an idempotent issue with ibm_database.  https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5546
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
This works around an idempotent issue in the 1.68.0 provider.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

:tada: This issue has been resolved in version 1.11.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


AsyncClient connection crushes

Hi I played with AsyncClient and sometimes got
    client_session: <aiohttp.client.ClientSession object at 0x7f8e144331d0>
    Unclosed connector
    connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f8e142e3d08>,  20664.425)]']

and then my application was crushed
How can I avoid this ?

sorry, my mistake


Refactor GetPropertyValueType

Imagine a picker that picks content type alias "foo" - we want GetPropertyValueType to return typeof(Models.Foo) but that is not possible because the type does not exist because it is being generated. So, GetPropertyValueType needs to be refactored to return a string and be passed a dictionary of (alias, type name).

This is now provided by the ModelType class in Umbraco.Core, used for instance in the nested content value converters - closing.


[5.1] tiny update for deprecated static find function

The find function isn't deprecated. It's just dynamic.


Socket CLI errror missing tiny-updater dependency

The Socket CLI for a number of releases has generated the following error and failed to generate a report (seen in all of my Node projects). From the package.json definition, tiny-updater appears to be in devDependencies, not dependencies, but is used in the socket command entrypoint.
$ npm i -g<EMAIL_ADDRESS>npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
added 719 packages in 38s
117 packages are looking for funding
  run `npm fund` for details
$ socket report create . --view
node:internal/modules/cjs/loader:1252
  throw err;
  ^
Error: Cannot find module 'tiny-updater'
Require stack:
-<EMAIL_ADDRESS>    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15)
    at Function._load (node:internal/modules/cjs/loader:1075:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:[21](https://gitlab.com/gitlab-ci-utils/tests/node-cjs-test/-/jobs/8726909343#L21)9:24)
    at Module.require (node:internal/modules/cjs/loader:1340:12)
    at require (node:internal/modules/helpers:138:16)
    at Object.<anonymous> (/usr/local/lib/node_modules/@socketsecurity/cli/dist/module-sync/cli.js:15:37)
    at Module._compile (node:internal/modules/cjs/loader:1565:14)
    at Object..js (node:internal/modules/cjs/loader:1708:10)
    at Module.load (node:internal/modules/cjs/loader:1318:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS>  ]
}
Node.js v[22](https://gitlab.com/gitlab-ci-utils/tests/node-cjs-test/-/jobs/8726909343#L22).12.0

The Socket CLI for a number of releases has generated the following error and failed to generate a report (seen in all of my Node projects). From the package.json definition, tiny-updater appears to be in devDependencies, not dependencies, but is used in the socket command entrypoint.
$ npm i -g<EMAIL_ADDRESS>npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
added 719 packages in 38s
117 packages are looking for funding
  run `npm fund` for details
$ socket report create . --view
node:internal/modules/cjs/loader:1252
  throw err;
  ^
Error: Cannot find module 'tiny-updater'
Require stack:
-<EMAIL_ADDRESS>    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15)
    at Function._load (node:internal/modules/cjs/loader:1075:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:[21](https://gitlab.com/gitlab-ci-utils/tests/node-cjs-test/-/jobs/8726909343#L21)9:24)
    at Module.require (node:internal/modules/cjs/loader:1340:12)
    at require (node:internal/modules/helpers:138:16)
    at Object.<anonymous> (/usr/local/lib/node_modules/@socketsecurity/cli/dist/module-sync/cli.js:15:37)
    at Module._compile (node:internal/modules/cjs/loader:1565:14)
    at Object..js (node:internal/modules/cjs/loader:1708:10)
    at Module.load (node:internal/modules/cjs/loader:1318:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS>  ]
}
Node.js v[22](https://gitlab.com/gitlab-ci-utils/tests/node-cjs-test/-/jobs/8726909343#L22).12.0

https://github.com/SocketDev/socket-cli/issues/279#issue-2760208442

@aarongoldenthal  @DemonBarber1020 Please try again. Updated to v0.14.38. You can now use npm i -g socket btw.


Testdata cleanup

The testdata is considered as type script files due to the .ts extension. That should be corrected together with the change to set the filepath to the test data by a project variable for easier usage.

Done with #34.