descDithers +  protoDC2 visit list generation code and output files.

@rbiswas4 so I've removed the dependency on DC1 code; there were only two functions and I was modifying their outputs anyway. Also, I have added to the ipython notebook additional info you requested.
Since there isnt much point in keeping all interm code/products for the visit list generation, I'll move all my code (with its commit history) to a separate repo; similar to the DC1 repo from where we only access the data files. I can tag and release that, which would allow tracking the specific output we end up using. Does that sound ok?

@humnaawan That sounds like a good idea. Can you point me to the repository with the extra stuff, I have some things like that as well, and it would be good to put all of these products together so that we don't forget.

It looks like there are now zero net changes in this PR.  In that case, I will close it now.  Please re-open (or file a new issue) if more work along these lines needs to be done.


Display Verbose Stream when Jobs are Received

Would it be possible to display verbose stream (when Write-Verbose is used in the script block being executed within a job) messages when RSJobs are received?  Traditional PSJobs do display the verbose stream if the $VerbosePreference variable is set to something other than SilentlyContinue within the script block but I'm not seeing verbose output with RSJobs.

Can you put together some demo code showing this so I can look at and then work to see if I can make a fix for this?

Duplicate of #20


Punch clock looks funny/has no functionality.

Commented it out for now, can choose to return to it later.


Add support for REGEXP_REPLACE

Description
This function is similar to regexp_replace functions offered by other databases like
postgres and oracle.
This function unlocks a few use-cases

Name rearrangement

If a column stores the name as first last, but you would prefer the report
to be displayed as last, first
SELECT REGEXP_REPLACE('John Doe','(.*) (.*)','$2, $1');

String removal

If you'd prefer to replace a string that matches a pattern - for example
email addresses that might be in a text column, you can replace the pattern
with generic text so that queries don't accidentally leak data.
SELECT DISTINCT REGEXP_REPLACE(diffUrl, 'diff=\d*', 'diff=****') from wikipedia`
This PR has:

[ ] been self-reviewed.
[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

Marked as WIP since it has insufficient tests

not stale... new PR coming this month 🤞

one more time please stalebot 🙏

one more time please stalebot 🙏

two more times? 🙂

one more time please stalebot 🙏

two more times? 🙂

Just want to say that I'm really looking forward to this being eventually merged and thank @suneet-s for implementing it.


Fix CI failures

@vishal423 Should this pass and be merged before a release?

@mraible, Lets not wait for this issue. It can go as part of next dot release

On further debugging, the CI Integration test failures are reproducible with the native build. As part of #279, we plan to upgrade mongock dependencies to the latest version. Let's wait on that if that fixes this issue as well.


lot's and lot's of stuffs

Sorry for delay on this - was disconnected for a bit on vacation. I'll take a look at your two PRs sometime this week.
Thanks!

We moved dev on this from my repo to LessEverything's repo.

Gotcha - so I can close #19 and just look at this one, right?

Yeah. :)
Wishing you happiness,
Steven Bristol
Founder of LessAccounting http://bit.ly/lessacc
On Mon, Apr 13, 2015 at 11:53 AM, Stephen Birarda<EMAIL_ADDRESS>wrote:

Gotcha - so I can close #19 https://github.com/birarda/logan/pull/19
and just look at this one, right?
—
Reply to this email directly or view it on GitHub
https://github.com/birarda/logan/pull/20#issuecomment-92409426.

out of curiosity, what was activesupport needed for in that?

.blank?
Wishing you happiness,
Steven Bristol
Founder of LessAccounting http://bit.ly/lessacc
On Wed, May 20, 2015 at 12:57 PM, Stephen Birarda<EMAIL_ADDRESS>wrote:

out of curiosity, what was activesupport needed for in that?
—
Reply to this email directly or view it on GitHub
https://github.com/birarda/logan/pull/20#issuecomment-103958309.

Got it, thanks. Would rather not require activesupport if we don't need to so I replaced that with nil? and then empty?


Inconsistent visible columns processing

We need to use a single, common visible column parsing routine that can handle all the syntactic variants and convert them (or reject if invalid) for the given application context.  A DBA should be able to set a single * context visible column list that functions correctly for all applications, if they don't want to bother customizing each context:

"Column", {"source": "Column"}, and {"source": ["Column"]} are semantically equivalent and should be supported everywhere that regular columns are supported.  There should be no difference in ermrest query formulation regardless of which notation is used.
["S", "FK"] and {"source": [{"outbound": ["S", "FK"]}, "RID"]} are semantically equivalent and should be supported everywhere that a single outbound foreign key is supported. There should be no difference in ermrest query formulation regardless of which notation is used.
The generalized pseudo column syntax should be acceptable everywhere. If the path is too complex for the individual context, that pseudo column should be discarded. It should never cause an application failure.  (Right now, the "entry" contexts violate this rule.)
The "markdown_name" and "comment" features of the pseudo column notation should be accepted and used for point-of-use customization in every application context, overriding any other column or foreign key annotation preference, even for the simple column and foreign key cases.

The only contexts that are treated differently are entry (entry/edit, entry/create), and filter.
The reason that I'm not allowing the pseudo-columns in entry context is because I wasn't sure to what extend we actually want to support this. Only pseudo-columns that have a source without any foreignkey or just one outbound foreignkey? Anything other than that should be ignored? Or do we actually want to support the all-outbound pseudo-columns too?
And for filter, currently the way it works is that if you haven't defined the specific context, we're creating facets based on visible-columns in compact and related entities in detailed. Which we can change obviously. But I think the reason behind having specific filter context was to make sure that those are specifically defined for facet. There are some extra attributes that facet objects can have that are not applicable to columns (choices, ranges, etc.).

I'm not suggesting any changes to the core functionality as far as
which pseudo-column types work in each app context. I'm only
requesting that we treat the different annotation variants as
equivalent where they have the same semantic meaning:

a local column

"Column Name"
{"source": "Column Name"}
{"source": ["Column Name"]}

a single outbound foreign key

["Schema", "Constraint"]
{"source": [{"outbound": ["Schema", "Constraint"]}, "RID"]}

These are not different kinds of pseudo column, but just different
notations for the same two core concepts. The DBA shouldn't have to be
intimately aware of implementation issues nor have to repeat
themselves just to put the same list into different "normal forms".
The only behavior change I am suggesting is that we accept all
equivalent notations in all contexts and include support for whatever
extra display options are possible in the more explicit
syntax. E.g. "markdown_name" or "comment" fields on a pseudo
column should override any other column or table display annotation
that would otherwise be applied in their absence.
We would still have the restriction that more general source paths
are not supported in some contexts, and those should be filtered out
rather than having the app fail with an exception.  Data-entry of
course can only handle editable fields of the record (scalar columns
and single-hop outbound foreign keys), so it should discard any other
more complex pseudo columns in the list.
If a pseudo column includes initial filter state, I think that state
should just be ignored in non-filtering contexts rather than discarding
the whole pseudo column.
A general principle should be that a single master visible-column list
on the "*" context should be technically possible to exercise all
available functions in all app contexts.  Each app context should
consume the subset that is meaningful and skip the rest, without
causing app failures.  A DBA should only have to configure specific
sub-contexts when they actually want to choose a different subset of
the available features.

I forgot to mention, the filter app context should discard pseudo
columns that use aggregation, since ermrest does not allow you to
express filters over aggregate results.
I don't think it would be appropriate to just discard the aggregate
function while keeping the pseudo column. Aggregation is an important
part of the pseudo column semantics (unlike filter state which is just
more of an initial/default controller state which the user can change
at runtime).

I changed the logic of pseudo-columns so they are the same in all the contexts of visible-columns list. Since filter context is used to define an actual filter and not just list of columns, it remains as before and different from other contexts.


Skipping plugin installation

Expected Behaviour
Plugin installation
Actual Behaviour
Skipping Installation of push plugin
Installing "phonegap-plugin-push" for android

Plugin doesn't support this project's cordova-android version. cordova-android: 6.3.0, failed version requirement: >=7.1.0

Skipping 'phonegap-plugin-push' for android
Adding phonegap-plugin-push to package.json

Saved plugin info for "phonegap-plugin-push" to config.xml

Reproduce Scenario (including but not limited to)
ionic cordova plugin add phonegap-plugin-push

npm install --save @ionic-native/push

ionic cordova run android

Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 7.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Samsung
Cordova CLI version and cordova platform version
cordova --version                                    7.1.0 (global)
cordova platform version android                     android 6.3.0

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

Latest version of the plugin requires cordova-android 7.1.0

@jcesarmobile  the default installation of the latest ionic is come with cordova-android 6.30. is it possible to update the cordova-anroid to 7.1.0

try with ionic cordova platform rm android and the ionic cordova platform add<EMAIL_ADDRESS>

build process failed

I fix it by changing the minSdk from 16 to 19 in config.xml

I fix it by changing the minSdk from 16 to 19 in config.xml


implement block entity data and signs, improve Vector3 usage

implement block entity data tracking in world
implement sign placement in interact
make Vector3 more flexible by allowing dict and iterables (tuple/list) as init argument
allow iterables (Vector3/tuple/list) as block positions in world
clean up the event plugin
add Python 3.5 to CI

Example for accessing sign text: (cc @AndrewBuck)
# in plugin class:
requires = ('world', ...)

# in some handler:
logger.debug('sign text: %s', self.world.get_block_entity_data(sign_pos).lines)

ERROR:   py35: InterpreterNotFound: python3.5

um, ok I guess ...


Problem: kiota escapes the client namespace

When using kiota to generate the Go client passing --namespace-name=go.artefactual.dev/ssclient/kiota the generated client is not built properly (the use of the go. prefix is problematic for some reason). Our Makefile has some logic in it to work around the issue by using a different name and then sed the generated code, but we should try to fix the issue in the kiota generator.
I'll file an issue in the kiota repo.

This was fixed in https://github.com/artefactual-labs/ssclient-go/commit/1e4eaacacefc73eba675172b506a66ce35644a0f (v0.5.0) by updating the version of kiota used.


Some methods in facades are not showing up (e.g. Route::prefix)

The following does not seem to autocomplete correctly in PHPStorm.
 Route::prefix(...)

There are other examples, but I think this may be a common issue with some magic method in facades.

+1, for example Auth::routes() also missing

Yes please can anyone help us with theses two ?

Route::prefix works, I just tested (maybe because of https://github.com/laravel/framework/pull/24086 , not sure)
As for Auth::routes(), there' already an issue for this => https://github.com/barryvdh/laravel-ide-helper/issues/513
@barryvdh original issue works, other mentions is a dupe => IMHO issue can be closed! :}


[apptools-android] Add tests to check required minimum API target version for apptools android

Impacted tests(approved): new 2, update 0, delete 0
Unit test platform: [Android]
Unit test result summary: pass 2, fail 0, block 0
https://crosswalk-project.org/jira/browse/XWALK-3833
https://crosswalk-project.org/jira/browse/XWALK-5181

LGTM


Let mocha use its default "colors" setting when not specified

Mocha uses its defaults when the parameter to .useColors is undefined: https://github.com/mochajs/mocha/blob/master/lib/mocha.js#L344-L347
Right now, you are always overriding it to false unless an argument is given to always override it to true, which defeats the point of mocha's default.

Nice, thank you!


Crash when scanning Barcode

scan barcode
???
App crashes

Could it be because it is out of focus? It that case it should still not crash.

Open Food 0.5 from F-Droid
Fairphone 2 with Open OS 16.12.0 (Android 5.1)

Can you provide a trace ?

@teolemon no, but i would like to get it if you tell me how.

You can install Android Studio, connect your device using a USB cable, and look at the log in Android Studio.

That would take some time... is that log a file on the device? I can give you any file on the device.
I have here another image that crashes the app on my device.

Can you reproduce it? Then you can also check if a potential fix works.

I tried it with the latest version from Trunk: the product doesn't exist, and it doesn't crash.

@teolemon does it crash when you try to add it?

Any update? Feel free to reopen it =)

I just updated to latest version (0.7) and successfully scanned a product and added it. I don't have the box i had trouble with anymore but i will create a new bugreport if i have any problems. Thanks!


[libyuv] No avx/sse/etc... feature support on MSVC build

Describe the bug
Libyuv compiled by vcpkg does not enabling advanced instructions optimizations under debug build (probably also release build, unable to breakpoint there)
Environment

OS: Windows 11
Compiler: Latest MSVC

To Reproduce
Steps to reproduce the behavior:

./vcpkg install libyuv
Debug into any libyuv copy function and step into it. It jumped over all optimized instructions.

Expected behavior
The library should use best advanced instruction (avx,sse,qmemcpy) on debug build, as it makes no sense to disable it.
Moreover, the port should provide features to make user enable avx512, etc.

arch dependent stuff needs to be toogled by the triplet/toolchain unless the library does a proper runtime detection of cpu functionality. SSE could probably be activated for x64 however.

It does runtime cpuid detection, but some macro is not defined unless use clang. From this aspect we can see there's no point to stick with MSVC


Code blocks are not displayed in the documentation

Code blocks are not displayed in the extBase documentation. Instead showing, TODO: Enter Code
Refererence: https://docs.typo3.org/typo3cms/ExtbaseFluidBook/2-BasicPrinciples/1-Object-oriented Programming-in-PHP.html#interfaces

Actually this has nothing to do with the theme. Instead it's about missing content in the manual. So I close this ticket here.


Lump API content into API buckets for RPC, Horizon, AP, & SDP

What problem does your feature solve?
Currently API content for RPC, Horizon, Anchor Platform, and Stellar Disbursement Platform are separated out below Admin Guides. They should be nested under an API Reference bucket for better usability.

https://github.com/stellar/stellar-docs/pull/448


router.push with alias not changing original URL

Reproduction
https://jsfiddle.net/h3gdzkaf/3/
Steps to reproduce the bug
Add the following to your router:
{ path: '/bar', alias: '/bar/alias', component: Bar }
Expected behavior
when I'm access '/bar/alias' from '/bar', URL should be change
Actual behavior
original URL not change, always '/bar'
Additional information
No response

This is expected, it's considered a duplicated navigation and it's skipped.


Enable proper CAP macro check.

Signed-off-by: Jiewen Yao<EMAIL_ADDRESS>

You'll also want to add LIBSPDM_ENABLE_CAPABILITY_MUT_AUTH_CAP and LIBSPDM_ENABLE_CAPABILITY_ENCAP_CAP to CI/CD to ensure that things build when these capabilities are disabled.

I filed https://github.com/DMTF/libspdm/issues/1369


Balder/add in memory crc for summary cache

@geirst and @toregge PR
Best reviewed in sequence. Only the last adds any semantics

Please update unit tests, so they pass too.

@geirst PR Now it should be OK.


Kills are not updated!

Kills are not updated when you do a kills, deaths are updated

Yeah I'm aware, the resource does not work correctly and I am currently not supporting it, but feel free to put in pull requests.
I might continue to work on it in a few weeks but no promises

(It is version 0.0.1 after all lol)


[WIP] Region Flattening by the use of RegionViews

As titled,
This PR alters the way we store data significantly by 'flattening' regions and storing  graph data as pure blocks. This is done by using of RegionViews which are an extension/refactor of the existing ConcealedRegionViews which were designed for the very same purpose.

Closed in favour of #61 according to the latest numba-rvsdg discussion meeting.


ekanite cause a high cpu usage, any fix or how to debug?

top - 11:07:44 up 43 days, 17:30,  2 users,  load average: 1.06, 1.03, 1.05
Tasks: 127 total,   4 running, 123 sleeping,   0 stopped,   0 zombie
%Cpu0  : 60.4 us, 38.9 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.3 si,  0.3 st
KiB Mem:   1016332 total,   895712 used,   120620 free,    85044 buffers
KiB Swap:        0 total,        0 used,        0 free.   237724 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
28941 root      20   0 1554440 115492  98036 R 99.0 11.4   8490:51 ekanited

thx.

Thanks for the report @zjqzero -- I need much more information that this. What was the program doing at the time? What resources does the program have? CPU, RAM, etc? Without this information, it's impossible to know if there is actually a problem.
You can also enable standard Go CPU and memory profiling, via the command line options. Pass -h to the program to learn these options. Once enabled, follow these instructions:
https://blog.golang.org/profiling-go-programs

thanks for your answer.
I run ekanite in docker on ubuntu14.04.   Can you pass
-cpuprof cpu.pprof, let the CPU spike for a while, shutdown the program, and then make the file available? I also need to know what version you are running.

Also, what rate of log messages are you indexing?

When I  use -cpuprof option. The cpu utilization has been normal for a few days.
I will continue to monitor it.
The running version is release 1.0.0

@otoolep
here is the cpu.pprof,  please check, thks
cpu.pprof file

Does the CPU load disappear if you stop indexing?

What OS are you running?

HOST OS is ubuntu 14.04
DOCKER container is also ubuntu 14.04
When I shutdown the NIC interface， the high CPU load never disappered

Closed in error.

pprof002.svg.zip

Attached .svg file, showing profiling. Nothing jumps out at me.
What rate are you indexing at? How many messages a second? https://github.com/ekanite/ekanite/blob/master/README.md#diagnostics will tell you the endpoint to hit to get stats. Perhaps log messages are just piling up within?
I should point out that I have never done any performance optimization on Ekanite. There is probably a ton of stuff we could do to reduce CPU load.

https://github.com/ekanite/ekanite/pull/37 is the start of better diagnostics support. Hopefully I can provide better debugging built into Ekanite soon, to help with issues like this.

ok ， it will help much
Sent from my iPhone

On Aug 14, 2016, at 09:40, otoolep<EMAIL_ADDRESS>wrote:
#37 is the start of better diagnostics support. Hopefully I can provide better debugging built into Ekanite soon, to help with issues like this.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@zjqzero -- upgrade to v1.1.0 (just released) and see if that addresses your issue. v1.1.0 has a fix for an issue that might have resulted in excessive CPU usage.

@otoolep
hi, there may be some thing wrong with 1.1.0,  it can index nothing with my syslog-ng config that works on 1.0.0.
I capture the packets with wireshark, I think the message is correct, but ekanite have no index.
please check. thanks
Frame 1081: 202 bytes on wire (1616 bits), 202 bytes captured (1616 bits) on interface 0 Ethernet II, Src: 02:42:ac:11:00:03 (02:42:ac:11:00:03), Dst: 02:42:b3:2b:b5:93 (02:42:b3:2b:b5:93) Internet Protocol Version 4, Src: <IP_ADDRESS>, Dst: <IP_ADDRESS> Transmission Control Protocol, Src Port: 39150 (39150), Dst Port: 5514 (5514), Seq: 36195, Ack: 1, Len: 136 Syslog message: USER.NOTICE: 1 2016-09-06T00:33:44+00:00 L700 VWMS stunnel  - LOG5[197]: Connection closed: 1573 byte(s) sent to SSL, 5331 byte(s) sent to socket     0000 1... = Facility: USER - random user-level messages (1)     .... .101 = Level: NOTICE - normal but significant condition (5)     Message: 1 2016-09-06T00:33:44+00:00 L700 VWMS stunnel  - LOG5[197]: Connection closed: 1573 byte(s) sent to SSL, 5331 byte(s) sent to socket

OK, thanks @zjqzero -- I ran a quick test of the code before releasing and it seemed fine to me.
I'll take a look.
Can I see your syslog-ng config?

@otoolep here's my syslog-ng config file:
@version: 3.5
options {
use_dns(no);
keep_hostname(yes);
create_dirs(yes);
ts_format(iso);
};
source file_app_log {
file("/appdata/log/app.log" follow-freq(3));
};
template app { template("<${PRI}>1 ${ISODATE} ${HOST} VWMS ${PROGRAM} ${PID} - $MSG"); template_escape(no); };
destination d_net_app {
tcp("<IP_ADDRESS>" port(5514) template(app));
};
log {
source(file_app_log);
destination(d_net_app);
};

Please show me the output of:
curl <IP_ADDRESS>:9951/debug/vars
when the program is supposedly receiving log messages.

zhou@L700:~/Test/ekanited-v1.1.0-linux-amd64/data$ curl localhost:9951/debug/vars
{
"bleve": {"bootDuration": 29713, "indexes": {}},
"cmdline": ["./ekanited","-datadir","./data","-tcp","<IP_ADDRESS>:5514","-queryhttp","<IP_ADDRESS>:18000"],
"ekanite": {"launch": 2016-09-05 16:17:15.052635122 +0000 UTC},
"engine": {},
"input": {"rfc5424Unparsed": 1189, "tcpBytesRead": 267034, "tcpConnReadEOF": 4, "tcpConnReadError": 1717, "tcpConnReadTimeout": 1713, "tcpConnections": 1, "tcpEventsRx": 1189},
"memstats": {"Alloc":2704008,"TotalAlloc":2704008,"Sys":8231160,"Lookups":28,"Mallocs":18456,"Frees":266,"HeapAlloc":2704008,"HeapSys":4751360,"HeapIdle":999424,"HeapInuse":3751936,"HeapReleased":0,"HeapObjects":18190,"StackInuse":491520,"StackSys":491520,"MSpanInuse":45360,"MSpanSys":49152,"MCacheInuse":4800,"MCacheSys":16384,"BuckHashSys":1443476,"GCSys":163840,"OtherSys":1315428,"NextGC":4194304,"LastGC":0,"PauseTotalNs":0,"PauseNs":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"PauseEnd":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"NumGC":0,"GCCPUFraction":0,"EnableGC":true,"DebugGC":false,"BySize":[{"Size":0,"Mallocs":0,"Frees":0},{"Size":8,"Mallocs":61,"Frees":0},{"Size":16,"Mallocs":2211,"Frees":0},{"Size":32,"Mallocs":5621,"Frees":0},{"Size":48,"Mallocs":1661,"Frees":0},{"Size":64,"Mallocs":546,"Frees":0},{"Size":80,"Mallocs":1809,"Frees":0},{"Size":96,"Mallocs":252,"Frees":0},{"Size":112,"Mallocs":667,"Frees":0},{"Size":128,"Mallocs":1256,"Frees":0},{"Size":144,"Mallocs":835,"Frees":0},{"Size":160,"Mallocs":347,"Frees":0},{"Size":176,"Mallocs":675,"Frees":0},{"Size":192,"Mallocs":380,"Frees":0},{"Size":208,"Mallocs":229,"Frees":0},{"Size":224,"Mallocs":110,"Frees":0},{"Size":240,"Mallocs":105,"Frees":0},{"Size":256,"Mallocs":412,"Frees":0},{"Size":288,"Mallocs":102,"Frees":0},{"Size":320,"Mallocs":60,"Frees":0},{"Size":352,"Mallocs":36,"Frees":0},{"Size":384,"Mallocs":149,"Frees":0},{"Size":416,"Mallocs":26,"Frees":0},{"Size":448,"Mallocs":3,"Frees":0},{"Size":480,"Mallocs":7,"Frees":0},{"Size":512,"Mallocs":144,"Frees":0},{"Size":576,"Mallocs":12,"Frees":0},{"Size":640,"Mallocs":23,"Frees":0},{"Size":704,"Mallocs":26,"Frees":0},{"Size":768,"Mallocs":23,"Frees":0},{"Size":896,"Mallocs":24,"Frees":0},{"Size":1024,"Mallocs":90,"Frees":0},{"Size":1152,"Mallocs":29,"Frees":0},{"Size":1280,"Mallocs":44,"Frees":0},{"Size":1408,"Mallocs":11,"Frees":0},{"Size":1536,"Mallocs":10,"Frees":0},{"Size":1664,"Mallocs":33,"Frees":0},{"Size":2048,"Mallocs":32,"Frees":0},{"Size":2304,"Mallocs":30,"Frees":0},{"Size":2560,"Mallocs":3,"Frees":0},{"Size":2816,"Mallocs":10,"Frees":0},{"Size":3072,"Mallocs":10,"Frees":0},{"Size":3328,"Mallocs":10,"Frees":0},{"Size":4096,"Mallocs":26,"Frees":0},{"Size":4608,"Mallocs":0,"Frees":0},{"Size":5376,"Mallocs":9,"Frees":0},{"Size":6144,"Mallocs":12,"Frees":0},{"Size":6400,"Mallocs":6,"Frees":0},{"Size":6656,"Mallocs":1,"Frees":0},{"Size":6912,"Mallocs":3,"Frees":0},{"Size":8192,"Mallocs":1,"Frees":0},{"Size":8448,"Mallocs":0,"Frees":0},{"Size":8704,"Mallocs":0,"Frees":0},{"Size":9472,"Mallocs":0,"Frees":0},{"Size":10496,"Mallocs":0,"Frees":0},{"Size":12288,"Mallocs":1,"Frees":0},{"Size":13568,"Mallocs":0,"Frees":0},{"Size":14080,"Mallocs":0,"Frees":0},{"Size":16384,"Mallocs":0,"Frees":0},{"Size":16640,"Mallocs":0,"Frees":0},{"Size":17664,"Mallocs":0,"Frees":0}]}

"tcpEventsRx": 1189 and "rfc5424Unparsed": 1189 tells me your messages are being received, but not getting parsed. This means they do meet the required format.
Can you provide me an example log line?

An easy way to see the log messages as they would be received by Ekanite is to start netcat instead, like so:
netcat -l <IP_ADDRESS> 5514
and watch the received log messages get dumped to stdout.

netcat output:


README.md: Clean up the contributing section

Manual updates of meta-balena are no longer neeeded so we remove that info. Also, clean up the restrictions on the commit message length since that's not used anymore either.
Changelog-entry: Clean up the contributing section from README.md

@balena-ci I self-certify!

Can one of the admins verify this patch?


Do you know what "for educational purposes" means?


Fix issue with dotnet template null handling

Related Issue
Fixes #5963
Description
It seems the null substitution options were being overwritten within the AdaptiveCardsTemplateVisitor class.
How Verified
Added two unit tests for the cases with/without null substitution.
Microsoft Reviewers: Open in CodeFlow

@paulcam206 Is it possible to get these changes in 1.2.1 as well?
https://github.com/microsoft/AdaptiveCards/issues/7210


New collision layer labels not visible in previously opened node

Godot version: 3.1 beta8
OS/device including version: Windows 10 1803
Issue description:
Collision layer labels are not refreshed in previously opened node. Must re-open node to see newly added collision labels.
Steps to reproduce:

Minimal reproduction project:
Reproducible with new project from scratch.

Closing in favor of https://github.com/godotengine/godot/issues/29991, as this is actually a bug.


Add a "public" flag option to the /jira view <key> to post the link to the channel - not an ephemeral message.

From a customer:

"When you do a ‘/jira view ’ it displays the issue only visible to you.
Is there a way to make that viewable to the channel? Or maybe adding a ‘/jira show’ or ‘/jira print’ which functions the same way as view but displays output to the channel.
Use case: “Hey Bill did you see this latest service desk ticket?” <run /jira show>.
As it currently is, you either have to copy the URL to the Jira issue and post in the channel (then they have to click on it, and open browser and log in…), OR copy the output of /jira view and paste it into a channel post and it completely mangles the format.
Even just being able to copy the output of /jira view and paste it and have it maintain its basic format and issue link and description would be a gigantic improvement. Any others make this request for a ‘/jira show’? This one seems like a small development investment but large efficiency payoff.

Two possible approaches:

Add a "public" flag to the /jira view command such as /jira view mm-123 public would post a public message to the current channel.
Add an interactive "Share Publicly" button to the epehemral message itself, and let the user click it to make a post in that channel if they want to.  This button could be shown on the ephemeral message after a jira issue is created as well.
Or do both...

Hello @aaronrothschild can I do this?

@hectorgabucio Absolutely, thanks for your help - let me know if you have any questions.  Myself @mickmister or @jfrerich (Developers at Mattermost) will be happy to hep as this moves along.  I was JUST talking with a customer about this yesterday - they would be very excited if this feature moved along!

@hectorgabucio Thanks for your interest in contributing to the project! If you'd like, you can join the Jira plugin channel on our community server to discuss more with the team.

@hectorgabucio I think the public button should also show in the output of /jira create (after the issue is created). Can you check to see if this is the case?

@mickmister

PS: I was trying different styles, thats not the final look, we are discussing it in the jira plugin channel, there you will find more pictures and updates :D


Use a mechanism other than set_interval to run application's dispatch

We should use a real task or application method to do this.

should be able to use a regular task class that waits for the app to be installed? we have a test task that uses the UI so we should have a good example already

Implement this first: https://github.com/vkottler/runtimepy/issues/115.

Implemented on https://github.com/vkottler/conntextual/pull/18.


[ui] url shown only as popup window and the toolbar is too high

compared to other embedded browser plugins and sidebars, toolbar is high (like 1.6x higher) and takes too much screen space

what's the reason of making URL visible as popup window only? weird

Attached screenshot for clarity

@wizzard0 About point 2:
It is not only visible as a pop up - you need to increase the width of the toolwindow - Jetbrains recommend not to set a default width size to toolwindow so not sure how to make it better
About 1.  this is the default size of the height of a toolbar in the IDE, I did not change the height of it so not sure what other embedded browser are doing - any examples ?

@wizzard0  I resized the input text should take less screen space.
You can check the new version in here
Closing this issue for now.


favicon: add

Adds an optional favicon option

Tests pass locally; no merge conflicts - released as v1.2.0 - thanks!


Remove boto and pip installation from default installation

Fixes #116

modules/install-vault/install-vault was tested by building new AMIs and launching new instances successfully.
I didn't test the example.

We can't run automated tests automatically for external PRs for security reasons. Could you run those yourself? Or, if that's too much setup work, could you deploy the example with the new AMI and make sure the cluster comes up OK? Thank you!

The AWS IAM auth script (and thus the Boto requirement) is not even used at all for starting up a Vault cluster.
Are you OK if I test using the IAM Auth example instead?
I will see if I can make some more changes to only install Boto/Pip when needed for that example.

Sure! As long as you're putting the new AMI through its paces and it works, I'd be confident in merging this. Thanks!

Did a couple of tests:

The IAM Auth example which spins up a Vault and Consul cluster and an additional EC2 instance that authenticates via IAM worked.  (i.e. I was able to curl http://<auth instance ip>:8080 and get back a secret I defined.)
I set install_auth_signing_script in the Packer template to anything other than true and I can confirm that Boto and Pip were not installed and the sign-request.py script is deleted.

ubuntu@ip-10-158-3-212:~$ sudo apt list --installed | grep python-pip

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ubuntu@ip-10-158-3-212:~$ ls /opt/vault/scripts/
ubuntu@ip-10-158-3-212:~$ ls /tmp/
systemd-private-b9c55fb6e3aa41549d63e9cbf8003c6b-systemd-timesyncd.service-hN1JET
ubuntu@ip-10-158-3-212:~$


ID fields defined as just a String32 is insufficient

Problem:
This specification (and the CSV spec) simply define IDs as "up to 32 character strings".
This is problematic because:

ID collisions across systems if an auto-incrementing database ID are used.
"Collisions" here mean two rows could end up with the same ID if data is pushed from two different systems.
Some systems may decided to put PII into the IDs (like "LastName SS#") since there's no guidance NOT to do this. This will likely leak PII into logs since API requests put IDs into the URLs.

Proposal:

Define the ID to be a UUID. Without the - characters, it is exactly 32 characters long (128 bits).
Possibly add an opaque "ExternalID" field to all individual models that have an ID. This is like a cookie and can be used by syncing to re-associate data.

Issues with this proposal:

Existing data may already have IDs, remapping them is problematic. (ExternalID may help here)

Closing #26 is a more detailed feature request.

Oh, but it might apply to OTHER ID fields, so going to reopen and rework the title/description.


Autostart ads

I have some ads that does not autostart on Chrome in Windows (works fine in Ubuntu).
Does anyone knows why that happens? Or maybe have a solution?

Fixed


Integrate Android app links

As a feature suggestion, you could implement Android app links so it automatically opens the app when clicking on a medium.com link.

thanks for the suggestion, I'm working on it 😊

I've added this feature in the 1.3.0 version, you can download it here

Thank you! 🙏
Just a small note, it would be nice if custom medium urls worked.
Here are some of them that i noted down:

https://towardsdatascience.com/
https://uxdesign.cc/
https://betterprogramming.pub/
https://plainenglish.io/
https://uxplanet.org/

(It would've been smarter to say this before you implemented it, sorry)

I've made a pull request with the changes, although I am not a android developer so you may need to change it.
#9

It is already working for me with these urls, except the first, does not work for you?
Can I ask you which Android you are running?

I'm running a stock Samsung although only uxdesign and uxplanet are working for mr. I just didn't try the others because the first one failed (silly of me). I will update the PR to only include towards data science, betterprogramming and plainenglish :)


Add audioCues.terminalCommandSucceded and success.mp3 (issue #178989)

Corresponds to https://github.com/microsoft/vscode/issues/178989 in Feature request.
This PR adds the ability to play a sound when a terminal command finishes with a 0 exit code, which is a useful feature for both multitasking and accessibility, like its similar, already existing, setting audioCues.terminalCommandFailed, which was added at PR https://github.com/microsoft/vscode/pull/174621
In the previous PR (#204408) I was using terminalBell.mp3:
I'm using the terminalBell.mp3 sound because it feels the most succeed to me. It's also very similar to other OS terminal bells (on MacOS, when pressing Ctrl+G on the terminal you will hear it)
I think it is ok to use this in 2 different places because they are very well differentiated.
Actually, on a second thought, I also think it would be wrong to reuse the terminal bell sound because it means user mistyped (thx @meganrogge for the feedback)
So I've asked a friend to join the contribution and create a new success.mp3 SFX for this 😎 (thx @JuanjeMC)
We put special attention to make it similar to the already existing warning.mp3 and error.mp3 SFXs, so it sounds well integrated
https://github.com/microsoft/vscode/assets/16073309/198c83b1-76d2-4352-a333-2916fcba3ea4

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

@Maximetinu thanks for this. we cannot use externally provided sounds. We have a sound designer, @afre100, that we use for such things.

Why was this closed, can't the sound just be replaced? This is the second PR opened for this (the first being https://github.com/microsoft/vscode/pull/204408) and the work is essentially done but it's not's not clear what the next step is for this. Will a sound be created by the Code team?
(FWIW, I think the sound in the video above really complements the existing failure sound 🙂)

@meganrogge let's use this as a base regardless of whether we use the new sound of not. I'm not sure if there are rules around accepting external sounds but we can verify that, if we can accept it and plan on replacing it then we could merge this and mark it as experimental and then swap out the sound when it's ready.

@Tyriar @meganrogge  It's very cool that someone made a sound externally! I see the logic of its design :)
Unfortunately (booo), no matter how great it might be, rule of thumb is to never ship external sound assets in this manor due to multiple risks (legal, IP, copyright, accessibility, UX, brand, etc).
Re marking this experimental -- this means including it in Insiders, right? It'd be beneficial to provide temporary placeholder sound(s), so long as it's ok to replace w/a different final sound in the future.
If possible, we always avoid confusing users if there's a chance they'll get used to sound 1, only to have it changed to sound 2. This is particularly sensitive for audio assets, and has caused issues in the past. I'm pretty sure (?) it happened due to use in a stable build, not a short lived Insiders or testing situation -- happy to zero in on the parameters with you all more.
(Btw, very happy to discuss any of this on a call if useful!). Couple things:

If we definitely would like a "success" sound, can you give me a date you'd like this for, and we can definitely roadmap?

And if there's a situation where we need placeholder sounds (and it isn't risky), when would you need that by?

@AFre100
If you want to use the sound for now as placeholder it isn't a problem for me. The sound itself was made from the project 'warning' sound, so it won't cause any kind of legal, IP or copyright issues.
Thank you for the kind words about it, we really thinked about how to make a well implemented sound in vscode (firstly I tried to make some from scratch).
Have a nice week you all! :)

@JuanjeMC Appreciate that info and figured as such -- awesome design thinking and execution, no doubt. Unfortunately, as absurd as it sounds, that mitigates only a fraction of the many existing legal and copyright liabilities for a situation like this.
Extremely punk rock and open source vibes, I know.
Thanks again for doing a cool thing, and we will definitely consider that design concept. (It's also cool to see it mocked up because, crucially, it demonstrates the likelihood of rapid repetition.)
cc @meganrogge @Tyriar sent you all and email about this :)

@meganrogge et all, I'm thinking that the audio cue for Success might make more sense as a globally/generically usable "action complete" sound, which could cover other interactions that come up. This could reduce cognitive load, things to learn, clutter overall.

Thoughts on that, and any good reason the sound needs to be very specific to this interaction?

I originally had the intention for our existing Save sound to serve as this generic Action Complete (and still do, but not the current shipped version). I'll soon be sending a subtle update to Save, which I believe a) reflects the idea of generic Action Complete a little better and b) addresses/implements some existing feedback for the as-is Save sound.

With the right sounds, how do you feel about Save being a use case of Action Complete, or do you feel it needs to be dedicated?

@AFre100 I think we should use a different sound because that lessens cognitive burden. Save is an action completed by the user or the workbench (autosave) whereas terminal completion is dictated by the shell.

great control flow call out -- thank you @meganrogge for setting the record straight! Totally agree there.
And what do you think about two sounds: 1) global user-initiated success/completion (Save etc) and 2) global system-initiated/controlled success/completion (terminalCommandSucceeded etc)?

@AFre100 what's the timeline here?

@meganrogge I had to take off early today — I'll send an update on Monday :)

@meganrogge In time for May's Insiders would be great — so what would that be, final by May 17?

Yes @AFre100

Hello, can I do something to help moving this forward? Should I fix the conflicts with main?
I've been using my own fork to have this feature for a while and I couldn't live without it now, thx for making it happen 👏 !

@meganrogge We're on track for a May 17 final delivery for Insiders. Will ping you offline early next week (possibly earlier) to align!

@Maximetinu if you'll fix the conflicts, I have the sound we want to use, so we can likely get this in for May.

@Maximetinu if you'll fix the conflicts, I have the sound we want to use, so we can likely get this in for May.

Done @meganrogge, conflicts resolved! 👌 Let me know if you need anything else, and feel free to make any modifications (you may have to replace the .mp3 by your new sound I suppose). Thanks!

@Maximetinu , I'm unable to push to your branch due to permissions issues. Could you pls fix the conflict, IE accept the incoming sound that I added, so this can be merged?
Thanks!

@Maximetinu , I'm unable to push to your branch due to permissions issues. Could you pls fix the conflict, IE accept the incoming sound that I added, so this can be merged?

@meganrogge done! 👍


Menubar items blurry

Prerequisites

[ ] Can you reproduce the problem in safe mode?
[x ] Are you running the latest version of Atom?
[ ] Did you check the debugging guide?
[ x] Did you check the FAQs on Discuss?
[ x] Are you reporting to the correct repository?
[ x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
I think it's self-explanatory. Could it be because of the Chromium engine - Visual Studio Code is having the same issue?!
Two disclaimers:
-I don't think this requires safe mode or debugging
-first-time contributor in GitHub(Markdown's still not my strength)
Steps to Reproduce
Expected behavior: The font of the menu should be crisp and clear.
Actual behavior: The font of the top menu(the triggering text only) appears blurry. The cascade items that open are OK.
Versions
Atom is latest 1.6.2, the OS is latest Windows 10 64bit with all the updates.

4k Resolution by any chance?

No, it's 1080p.

Alright, cause I am using same atom version and Win 10 64bit and do not have such blurry fonts as you describe. Have you made any modifications to the fonts within Atom or system wide?

No, but I could try some things to narrow down the cause:

I think, but not so sure, some fonts were bugging me the same way when I had been trying out the Chrome browser on the same machine(I'm using mainly Firefox). So, I could try Installing Chrome back and look around.
I'm using Remote Desktop to access that machine, so I may try out Atom ont the notebook I am using to ininiate the RD session. This, although with less chance(I enabled all the enhancements of the session, one of which is 'Font smoothing'), won't hurt.

Btw, I'm not just describing it - it's clearly visible from the screenshot.

it is visible, clearly. I am either losing my vision or I do not see the same issue with my atom. Here is my atom

what the, now that I posted the screenshot the quality of the menu degraded as well, in the screenshot that is o_O

Sorry, but I couldn't get this - do you find any difference or not?!
If I zoom to 100% the two screenshots, I find the font of both menubars blurry - as if it is not getting anti-aliased. Yours even have blurry fonts on other places.

I, personally, do not see the difference. Maybe I grew accustomed to the font that's why I do not "see" any blur

You must've adapted. I think it's everywhere, which is pity :( Look at this new screenshot - the dot of the 'i'-symbols and the thickness of the 'l'-symbols are different:

Again, I am not 100% sure, but I think it must be some general issue, I was having with the Chrome browser back than.

Unfortunatelly, here it is in Chrome settings as well:

It is the same on non remote desktop session(the laptop is connected to the monitor via an HDMI cable). Fresh installation of Chrome(32-bit) on both machines.
I'll try contact Chrome support for that. In the meantime, I'll be using something else for editing source code. Even though people don't spent that much time in the settings, IT people spent a lot of time with these tools in general. Rendering HTML might be great job by Chromium, but these settings' fonts are just bugging me. I hope they take it seriously.

What you're seeing is text rendered using sub-pixel positioning. It's an option available in the low-level DirectWrite windows font renderer and Chrome's renderer Blink chose to use that mode.
They are continually going back and forth and tweaking it so it's possible it will improve again as they tweak it and Atom take newer Chromium builds with those tweaks but there is not something we have direct control over.

Thanks for the input. Although I havn't used Chrome much, I can't remember these fonts looking OK on my two machines.
As a side note, just for people not getting biased, I'm having issue with directwrite on one of the machines with Firefox as well. IE's ok on both, but slower, choppier and uglier(personal opinion).
I guess I should close the issue as unrelated or sth?!

Also try adjusting the ClearType on your machine to see if you can find something a little better for your eyes. Start Menu > Adjust ClearType Text.
Yeah we should close for now. I've been keeping an eye on Blink to see what changes they've been making to DirectWrite but it takes a while for them to make it into Chromium, new builds of Chromium to make it into Electron and new Electrons to finally make it to Atom.

Even in the adjusting dialog I detect the blurriness(the boldest options). Do you think downgrading to Windows 7 will make the things better(I have another blocker with Firefox html5 videos choppiness on the laptop)?! I also tried 125% dpi, but I really don't like it, although fonts are a little better.
Wow, that stack is amusing.
As to what I read on the Internet, the issue is a blocker for normal dpi monitors - MS are pushing to high density displays and most 32-bit user programs are suffering from that. They say the fonts should be better on OS X, so I think trying out a virtual machine. Later, I may buy a Mac, although Apple were also mentioned to pay more attention to the ultra high dpi displays(their Retina's, of course).
I don't know - I just got even more confused.

I doubt Windows 7 will make anything different. Presumably the drop-down menu in Chrome is also bad for you?
I don't know it's a blocker for normal dpi monitors - how bad it is depends very much on your monitor settings, your eyes and viewing environments. Microsoft have been tweaking font rendering for quite some time and the reality is there is no one-fits-all.  I agree tho that it's not sharp enough for me.
Fonts on Mac OS X are a whole other issue. Right now they are using ClearType sub-pixel rendering but at a higher resolution that the screen then scaling down on their retina displays which I find terrible. Thankfully you can turn off their version of ClearType and it gets a bit better.

Cross link to the Visual Studio Code issue:
https://github.com/Microsoft/vscode/issues/5217

Just an appeal found while discussing the issue on the VSCode thread:
Bring sharp fonts back in Google Chrome (Disable DirectWrite)
Anyone teased by this should support the petition. If reconsidered, that kind of functional rollback should improve the typographic performance of chromium-based software on a lot of hardware!

That petition is inaccurate. It states

DirectWrite is incapable of giving the same look and feel as GDI, as you don't need glasses to see this in the comparison above.

First off. The comparison at the top is blown-out to exaggerate the difference.  More importantly however DirectWrite has a number of options when rendering text and in fact it CAN look very similar to GDI.  You only need to check out Visual Studio 2015 to see what the DWRITE_RENDERING_MODE_CLEARTYPE_GDI_CLASSIC mode in action.
This isn't however the default in Chrome today as it's primary purpose is rendering a mix of fonts, styles and sizes.  In a text editor that is typically used with a monospaced font DWRITE_RENDERING_MODE_CLEARTYPE_GDI_CLASSIC can make all the difference.
The effort would be better off allowing Chromium to expose DirectWrite font flags to applications that use it so it can be fine-tuned as appropriate.
It's also worth reminding people that font smoothing is very gamma dependent and ClearType is especially sensitive to LCD characteristics. Windows includes a ClearType tuner you can use to find what works best for you through a series of steps (and remember each display is different so you may need to do it on each monitor you have).
If you find ClearType too blurry you can still fall back to greyscale anti-aliasing by running the tuner and turning it off. If that turns off all smoothing entirely then go into Windows performance settings and turn font smoothing on to get greyscale AA (I do this).
Font rendering is often tweaked and adjusted between different versions of Chrome and you will find different versions of Atom change how they look as we pick up newer builds via Electron (current beta is locked on grey-scale but the next Electron build enables ClearType again)

I agree(already expressed my doubts this petition 'smells' in the VSCode thread). 10x again for the technical dive.


chore: update dependency for devpod.

While this builds, I'm unsure that this package currently works. The devpod agent seems to die immediately.

the agent was dying due to podman not being available inside of the container. Rechecked with docker and podman being available.


Atom crashes when installing module via NPM

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
On Linux Mint 18.3, Atom crashes when installing/uninstalling a module via NPM while sitting on the app's root directory.
Steps to Reproduce

Opened Bash terminal at app root directory
Typed atom . to open Atom
Typed cd client && npm i -S react-slick
Atom will crash while the module is being downloaded/installed

Expected behavior: Not to crash.
Actual behavior: It will either succeed or crash.
Reproduces how often: Crashes about 50% of the time.
Versions
Linux Mint 18.3 4.13.0-26-generic x86_64

Atom: 1.23.3
apm: 1.18.12
Electron: 1.6.15
Chrome: 56.0.2924.87
git: 2.7.4
Node: 8.9.3
npm: 5.6.0
python: 2.7.12

Additional Information
Video:
https://www.youtube.com/watch?v=GGF_xElWxbw
Checked and made sure node_modules wasn't being tracked:

Extra steps:

Renamed ~./atom to ~./atom_backup (still crashes)
Started app with atom --safe (still crashes)
Cleared atom window state (still crashes)

Happens randomly, as you can see here (I installed, uninstalled, reinstalled, then it crashed)

I am seeing the exact same thing:

OS: Ubuntu 17.10
Atom: 1.23.3

node_modules is not being tracked.

@scottsweb If you have some time, try removing Atom 1.23.3 and try installing Atom 1.18.0 and see if that resolves your issue.

Here the same when installing or uninstalling packages with npm.
Quite new issue before I had no problems. Not sure with which version exactly.
Now I'm using 1.24.1

It's unrelated if I run npm install/npm uninstall from internal or external terminal.

@henri-hulski Try downgrading to Atom 1.18.0. (see above post for link) and see if that resolves your issue.

@mattcarlotta Yep with 1.18.0 the issue is gone.
But I don't think we have to go so far back. As I said the issue is quite recent for me and I'm regularly updating Atom.

Ok just tried with Atom 1.22.1 and it also crashes.

Tested and passed:
✓ 1.20.0
✓ 1.20.1
✓ 1.21.0
x 1.21.1 -- crashes after 3 installs/3 uninstalls
x 1.21.2 -- crashes after 2 installs/1 uninstall
x 1.22.0 -- crashes after 2 installs/1 uninstall

I've experienced Atom (1.25.0, on Windows 10) becoming very sluggish during/after an npm install. It seems to recover after a minute or two. The "Editor has become unresponsive" message is shown after about a minute, but ignoring that seems to allow the editor to recover.

Does anyone still have this issue on the latest version of Atom? I'm running Atom 1.26.1 and the issue seems to have disappeared altogether.

It seems fixed for me as well now (1.26.1).

@mattcarlotta can you confirm if you still see the crash in 1.26.1?

Updated to 1.26.1, ran a several npm install/uninstalls and it appears to be working. But, I'd recommend long-term testing before calling it stable.

I'm running 1.26.1 and its slowing down and sometimes un-responsive and crashing when I install node_modules. I thought it was particular module but its not.

@eric-personal What Atom version were you running before?
I'm going to continue to test 1.26.1 for awhile before closing this issue. But, to expand on my above comment, I ran at least 10 iterations of npm i -S react-slick and npm uninstall -S react-slick and it's been pretty smooth (no hangs, unresponsiveness nor sluggishness) :

APM version info:

apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.26.1
python 2.7.12
git 2.7.4

Local machine info:

linux: Mint 18.3
kernel: 4.13.0-41-generic x86_64
npm: 6.0.1
node: 8.9.3
chrome: 66.0.3359.170

@eric-personal I believe it's pretty simple to downgrade Atom on Mac OS. You just delete the Atom.app file from your Applications folder, then go here and download the Atom release version you want, unzip the file, then drop that Atom.app file into your Applications folder to install it.

Thanks @mattcarlotta unfortunately when I download 1.21.0 source folder and unzip it I don't see any Atom.app Shame Atom don't have any notes on downgrading.

@eric-personal Don't download the source, instead download this: Atom v1.21.0 mac.zip

Do you happen to know if deleting Atom.app and installing the downgrade version will remove packages installed and themes ? I would like not to have to install all those over again.

@eric-personal I don't recommend this, but if you must: Go to your Applications folder, right click on the Atom.app and click "Show Packages Contents". It'll open a new folder and you should see several other folder, including a "packages" folder. Copy this "packages" folder to your desktop. Delete the Atom.app. Drop the v1.21.0 Atom.app into your Applications folder. Double click on it to install and open Atom. Close Atom. In your Applications, folder right click on the Atom.app and click "Show Packages Contents" again. Then copy the "packages" folder from your desktop and paste the folder into this Atom.app folder (the packages folder may or may not already exist). Reload Atom and it should have all your packages installed.

Other issues have popped up in v1.26.1...
When attempting to delete files, it won't (you can't see the pop up menu when I right-click, but I'm selecting "Delete"; also, hitting the delete button does nothing):
https://youtu.be/hMD73GBlbIo
I had to close Atom, reopen it, close the "NewPassword.js" tab again, close Atom, and reopen it.
I've also noticed, from time to time, it will create duplicate tabs of the same file. Causing major conflicts and headaches (spent an hour trying to figure out how my app was calling my API when I commented out the AJAX function -- duplicate tabs of the same file in different save states)...
Dropping back down to v1.21.0 for the time being.

Just to let everyone know I updated to V1.27.0 and still running into the freezing issue when installing node_modules. When I try to install the latest webpack it just slows down and is unusable. I've wasted too much time going back and forth so I decided for now to just move to another IDE that is more stable. I really hope Atom can figure this all out as I really loved the simplicity of its user face.

@mattcarlotta off-topic question if you don't mind. What's your syntax theme?

@dspacejs UI Theme: One Dark, Syntax Theme: Babel React

I just had this happen once again. Now on Ubuntu 18.04 with Atom 1.26.1 and an npm run build caused Atom to report it had crashed and offered a reload button. The reload button didn't seem to properly recover the editor.

For anyone able to consistently reproduce this, can you open the Developer Tools in Atom, make sure you are on the Console tab, and then reproduce this? It's likely there will be an error printed there.
It may also be useful to start Atom initially with the --enable-electron-logging option from a CLI, with that option error messages that normally don't make it to the Console will be printed to your CLI.

as an update, I am no longer seeing the crash issue.
I purged the entire Atom package from my system and did a clean install of version 1.31.1 x64 on Ubuntu 16.04.
After the reinstall npm install no longer crashed Atom, which I was previously seeing daily. My assumption is that something was corrupted while upgrading incrementally in the past. Since I can no longer reproduce the error, my issue is fixed and will report if the situation changes.

I still randomly get crashes. Usually it happens when the package.json is opened/focused in a tab.

@Arcanemagus Had the dev tool at console tab open and unfortunately... no luck there:

Reproduction:

Open package.json file to a tab.
Type npm i when in a terminal.

apm  2.1.1
npm  6.2.0
node 8.9.3 x64
atom 1.31.2
python 2.7.15rc1
git 2.17.1

Atom    : 1.31.2
Electron: 2.0.7
Chrome  : 61.0.3163.100
Node    : 8.9.3

Is there a crash dump located somewhere?

I am also seeing the random crashes.
Atom 1.31.2 x64 on KDE Neon (an Ubuntu 18.04-based distro).

@mattcarlotta for what it's worth, in your screenshot there are 56 items hidden because of the log filters

@SidneyNemzer Those were just filtering warnings. Just to be sure, I replicated the crash with verbose (the warnings you do see were caused by creating new files via right click and selecting new file):

I see this also on Atom 1.35.1 x64, fresh install of Ubuntu 18.04. Atom crashes on the 2nd or 3rd npm install

Running rm -rf node_modules may crash Atom as well.
(with Atom 1.36.1 x64 installed on Ubuntu 16.04 using snap)

This seems to have solved it for me: https://medium.com/@kandros/prevent-fuzzy-search-in-node-modules-folder-in-atom-editor-a1fb337c2f97

Theres an option in fuzzy finder’s setting to allow you to decide ignore, even better the package automatically include a global ignore list that packages can subscribe to.
The global ignore is in the core setting and accept multiple value separated by a comma, some values are already ignore by default, .git for example, to add node_modules to the folder to ignore just add it in here.

1.34.0 x64  still crashes for me, every time. This morning I made the change above.
Now I can't MAKE it crash.
Nice work @Tails !!

Exactly same thing happened to me, editor crased while installing NPM package.
I was just getting started with Atom and this happened :(


Update Home/Landing page with new design

The website needs to be updated to reflect a modern look and show the value it provides to users.
Criteria

Implement the new design (new design will be available in a Figma link)
Support multiple pages, navigation between them and creation of additional pages in the future.
All design elements and standards of the website apply to this page

Hi @oleg-pah is there a need to be assigned or should I just start work on it


🎉 2.0.1

ℹ About this release

Version: 2.0.1
Type: patch
Last Release: 2.0.0 (6/14/2023, 6:50:46 PM) [?]
Commits to merge: 14 [?]

📦 Dependencies

Added tsup ^7.2.0
Update cosmiconfig from ^8.0.0 to ^8.2.0

📦 Development Dependencies

Update @semantic-release/changelog from ^6.0.2 to ^6.0.3
Update @semantic-release/npm from ^9.0.2 to ^10.0.4
Update @typescript-eslint/eslint-plugin from ^5.45.0 to ^6.4.1
Update @typescript-eslint/parser from ^5.45.0 to ^6.4.1
Update c8 from ^7.11.3 to ^8.0.1
Update eslint from ^8.29.0 to ^8.47.0
Update eslint-plugin-jsonc from ^2.5.0 to ^2.9.0
Update mocha from ^10.1.0 to ^10.2.0
Update typescript from ^5.0.2 to ^5.1.6

:tada: This PR is included in version 2.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


In SkyWalkingAgent class, why ignore the classes which start with org.apache.logging.?

Question

In SkyWalkingAgent class, why ignore the classes which start with org.apache.logging.? Because that，I can‘t enhance org.apache.logging.log4j.ThreadContext. With enhancing ThreadContext, I want to print traceId and traceSegmentId to log in async mode.

Could you do that by a standard log4j formater? We recommend you do like other application toolkit did.

Ok, I try it.


Improve font renderer capabilities

With re-implementing the U8g2 font subsystem I now have an idea of what the capabilities of an established font rendering algorithm are.
I published it as a separate crate and with no integration to embedded_graphics::Text. The reason is that there are several shortcomings of the font rendering interface of embedded_graphics that I'd like to add in the future:

[ ] Compatibility with format_args!() to avoid the necessity for temporal string allocations when rendering arguments
[ ] Support for newlines
[ ] Return rendered dimensions from text drawing functions

Sadly, the first point already (format_args!()) is completely incompatible with the current API, because the current API is based o the builder pattern, and format_args!() does not live long enough for chained calls.
I'd like to improve the existing API, so I hope to have a little bit of a discussion here. (@rfuest)
If we provide an API similar to u8g2_fonts::FontRenderer, then I think the actual abstract Renderer trait could be reduced to renderGlyph, getRenderedGlyphDimensions, and several getAscent, getDescent, etc.
The value that embedded-graphics would provide, then, is to convert the input (like char, &str or format_args!()) into glyph render calls, handling multi-line rendering, etc.

In general you are right that a TextWriter struct could be used, but that is only possible for left aligned strings. For centered or right-aligned you need to know the size of the entire string beforehand.
So what I read from your comments is that you would rather keep it as-is and declare that utf8-fonts is an external font renderer explicitly?

Removed the newlines comment

In general you are right that a TextWriter struct could be used, but that is only possible for left aligned strings. For centered or right-aligned you need to know the size of the entire string beforehand.

OK, centered text would be a problem. But I still think that it should be possible to implement it similar to your implementation in u8g2-fonts.

So what I read from your comments is that you would rather keep it as-is and declare that utf8-fonts is an external font renderer explicitly?

I assume you mean u8g2-fonts?
I apologize if my comments made you think that I just want to dismiss your suggestions. Finding a common solution that works for all text renderers would be the best solution. I prefer to keep the required API changes to a minimum, but if you convince me that bigger API changes are required we could implement them for e-g 0.8.

Sounds good :) I'd be course be willed to adjust my api, with the premise that I don't want to lose any features in the process.

As a little background: the biggest issue was not just the alignment, it was the multi-line alignment without allowing memory for caching the line widths. Because you need to render each line twice, once for width, and once for the actual aligned rendering. And you can't easily re-render the current line with format_args!()

As a little background: the biggest issue was not just the alignment, it was the multi-line alignment without allowing memory for caching the line widths. Because you need to render each line twice, once for width, and once for the actual aligned rendering. And you can't easily re-render the current line with format_args!()

Hmm, that's a problem. I did take a quick look at the implementation in u8g2-fonts. Am I correct that ArgsLineDimensionsIterator is used to implement the caching of the line width? That struct is pretty large and will, in many cases, consume more memory than a string buffer.
Perhaps we could limit format_args to single line rendering, or at least offer single and multi line variants. I suspect that single line rendering would be the most common use case and it should be as memory efficient as possible. A multi line variant could also use const generics to set the maximum number of lines to keep the line dimensions buffer size smaller.

The line dimensions buffer is 20 right now. I felt like this is a good compromise. If there are more than 20 lines, the input string is read again. So it's not actually that big. It can further be optimized to be 20*i32 instead of 20*RenderedDimensions. So I personally thought that is quite small compared to the amount of memory that gets moved to do the actual rendering.
If you have a const generic, then you basically move the buffer allocation back to the user. And then the use could as well allocate a string buffer and write!() to it directly and render with a &str. That's at least my thought.
Are you sure that all the things you talk about here are actually performance relevant? Because my intuition says the slowest part is the glyph lookup and the glyph rendering. And if you have the kilobytes of memory that a font requires, I don't think 80 bytes of line buffer really matter, or the time to fill that buffer.
So before basing an entire architecture on the premise that this is not fast enough, I would honestly benchmark.

My comment was related to memory consumption and not performance. Although benchmarking the performance of having to format the string multiple times is a good idea.
The font data is constant and can be stored in flash on an embedded system and don't require any RAM. But the line dimensions will end up on the stack and 20*RenderedDimensions is big for a microcontroller with a few kilobytes of RAM.

@rfuest I reduced the cache down to 5*(i32,u32,i32), meaning, 60 bytes. Do you think this is acceptable for most microcontrollers?
https://github.com/Finomnis/u8g2-fonts/pull/3

Yes, I think 60 bytes are fine. Users with even more memory constrained targets should probably not be using core::fmt anyway and switch to something more memory efficient like ufmt.

@rfuest Just released v0.2.0 of u8g2-fonts, where I integrate the embedded_graphics::text subsystem. So it's no longer just an external renderer.
I'd close this discussion section for now, if that's fine with you.


RTFD badge broken by 0974027

New readthedocs.io URLs were used in 0974027. The new url seem to give a text/html (https://readthedocs.org/?version=master, actually) in its final destination and fails the image. Likewise, the https://readthedocs.io/projects/pygccxml/?badge=master link only takes you to https://readthedocs.org/?badge=master. Since the badges are not part of the pygccxml project-subdomain, it's almost certain that it's a mistake to change the badge URLs too.
Regarding project-subdomains, personally I don't think it's a good idea to change as long as https://readthedocs.org/projects/pygccxml/ is giving the .org site instead of the .io site...

Should be good now. I was too hasty at changing all the urls ...

I just released version 1.7.5. Everything should hopefully be fine now. I'll let you close this bug.


rust-bindgen does not have its shebang fixed

Describe the bug
The rust-bindgen binary has a shebang mentioning /usr/bin/env.
To Reproduce
Steps to reproduce the behavior:
~/build/nixpkgs $ head -n1 $(nix-build -A pkgs.rust-bindgen)/bin/bindgen
#!/usr/bin/env bash

Expected behavior
This should have a shebang pinning a specific bash, so that the program works on systems without /usr/bin/env
Notify maintainers
@JohnTitor , @Ralith
Maintainer information:
attribute:
- rust-bindgen

Seems to be fixed now.


Compile Error: unresolved import crate::arch::x86_64::_mm_movemask_pi8

When trying to compile a hello world program with packed_simd-0.3.3 as a dependency, I'm getting the following compile error:
error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:47:21
   |
47 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:41:1
   |
41 | impl_mask_reductions!(m8x8);
   | ---------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:62:21
   |
62 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:41:1
   |
41 | impl_mask_reductions!(m8x8);
   | ---------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:47:21
   |
47 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:47:1
   |
47 | impl_mask_reductions!(m16x4);
   | ----------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:62:21
   |
62 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:47:1
   |
47 | impl_mask_reductions!(m16x4);
   | ----------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:47:21
   |
47 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:52:1
   |
52 | impl_mask_reductions!(m32x2);
   | ----------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0432]: unresolved import `crate::arch::x86_64::_mm_movemask_pi8`
  --> C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask\x86\sse.rs:62:21
   |
62 |                 use crate::arch::x86_64::_mm_movemask_pi8;
   |                     ^^^^^^^^^^^^^^^^^^^^^----------------
   |                     |                    |
   |                     |                    help: a similar name exists in the module: `_mm_movemask_epi8`
   |                     no `_mm_movemask_pi8` in `arch::x86_64`
   |
  ::: C:\Users\me\.cargo\registry\src\github.com-1ecc6299db9ec823\packed_simd-0.3.3\src\codegen\reductions\mask.rs:52:1
   |
52 | impl_mask_reductions!(m32x2);
   | ----------------------------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0432`.
error: could not compile `packed_simd`

To learn more, run the command again with --verbose.

I'm using rustc 1.50.0-nightly (f76ecd066 2020-12-15) on Windows.
Edit:
I just tried compiling the same program on Linux (same rustc version) and it gave me the same error

Ok guys I'm just dumb and didn't read the docs, I just imported the old broken version of packed_simd. Sorry guys

No worries, it's a bit confusing!

@Sp00ph can you tell me what you did to remove this error?
I am getting the same error while using nightly to build my code.

You need to use packed_simd_2 as a dependency, packed_simd on crates.io is unmaintained

Can you guide me how to make those changes?
I tried adding: packed_simd = { version = "0.3.4", package = "packed_simd_2" } to the dependencies.
Still, I couldn't resolve the error.

You need to use packed_simd_2 as a dependency, packed_simd on crates.io is unmaintained

Can you guide me how to make those changes?
I tried adding: packed_simd = { version = "0.3.4", package = "packed_simd_2" } to the dependencies.
Still, I couldn't resolve the error.

Maybe try cargo clean and then  cargo build? I think cargo sometimes messes up when you change dependencies

I tried this but still it isn't resolved. You can check this link:
I finally managed to resolve it. Thanks for your help.


Whitelisting lodash-es using nodeExternals not working

Describe the bug
I am using lodash-es in my Angular project and want to use Universal in this project. I faced issues in this regard
node_modules\lodash-es\cloneDeep.js:1
(function (exports, require, module, __filename, __dirname) { import baseClone from './_baseClone.js';
                                                              ^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:616:28)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.lodash-es/cloneDeep (G:\Work\MEAN\elitebgs\dist\server\main.js:10379:18)

which is expected since lodash-es is, well, ES and I need a commonJS build. As such I found that whitelisting lodash-es with webpack-node-externals would fix this. As such I modified the angular.json
"architect": {
    "server": {
      "builder": "@angular-builders/custom-webpack:server",
      "options": {
        "customWebpackConfig": {
          "path": "./universal-webpack.config.js",
          "mergeStrategies": { "loaders": "replace" }
        },
        "outputPath": "dist/server",
        "main": "src/main.server.ts",
        "tsConfig": "src/tsconfig.server.json"
      }
    }

and the custom webpack is
const nodeExternals = require('webpack-node-externals');

module.exports = {
    externals: [
        nodeExternals({
            whitelist: [/^lodash-es/]
        })
    ]
}

But this does not change the main.js that is built nor is the above error message.
To Reproduce
See above
Expected behavior
I expect for Angular Universal to work fine with lodash-es as a dependency.
Builder:

@angular-builders/custom-webpack
7.0.0

Libraries

angular-devkit/build-angular: 0.11.0

Additional context
If you need any more information, I will gladly give them

I don't think you need this at all since you're in Typescript. Are you using @types/lodash-es along with lodash-es?

Well, that's embarrassing. I have been at for half a week and almost decided to move all 45 components of my app to Vue and it all boils down to the incorrect merge merge object.
Yup, "mergeStrategies": { "externals": "replace" } fixed it.
Thanks a lot for looking into this.


New action, add new pull requests to GitHub projects

This action allows new pull requests to automatically be added as a card to projects.

NOTE: Normally, we ask that any new additions go to the end of the section that they are being added to, but since in this case, the two at the bottom are from your other 2 PR's, I am going to go ahead and merge this.
I just wanted to add this note in case anyone looks back on this PR and wonders about the decisions made here.

@alex-page your changes have been merged, thanks for your contribution 👍

@gep13 sorry about that, I did a flakey merge which messed up the order.

@alex-page honestly, nothing to apologise for, just wanted to point it out for anyone else wondering what I was up to 😄


Feature Request: Reverse Workflow for Disposable Emails

Thanks for publishing this!
Feature Request:
Is it possible to add a reverse workflow for managing disposable emails? Instead of creating a new alias for each service, consider accepting all emails with a wildcard by default and blocking specific addresses as needed.
This would reduce the need to log in and create a new alias for every service beforehand, and still allow for targeted blocking of unwanted emails.

You can achieve this using Cloudflare and Gmail (and probably other email clients).
in cloudflare you can create a catch-all forwarding. Then in Gmail you could just block or filter out specific emails.
I use that method nowadays. Works like a charm.
Of course, this method is not 100% “safe” since one could just change the email prefix to go around the filter/block.
x2.email is better if one needs 100% control.


[request] Multiple ratelimiting options per API

Here is our usecase:
For an API, we impose a monthly limit of 100,000 calls. Also there is a second level throttling of 5 requests/second to avoid too many concurrent requests. Currently, this is not possible with kong.
I think we can allow to have multiple rate limits per API provided they have different period values. And while throttling the requests, we can verify all of them and throw a 429 even if any one has crossed the quota. I would like a send a PR to fix this. But, before I would like to have the feedback.
Thanks!

:+1:

+1

+1

Thanks for the :+1:
Currently the rate limiting config is like:
--data "value.limit=100" and --data "value.period=hour"
There are two ways I can think of supporting multiple configurations.

--data "value.limits=5,1000" and --data "value.periods=second,hour" (Having limit and periods as separate options and rely on the order supplied by the user to match them).
--data "value.limits=5:second, 1000:hour" (Much cleaner, but removing a existing option from API)

which one do you guys prefer?

I think the second solution is much cleaner, it sounds great.

note: these kind of plugins are currently "per API" only, but in the very near future will be and should be per endpoint too.

@sinzone Agreed., this addition wouldn't stand in the way of supporting per endpoint level configs.

I like option 2, but with the key=value pairs inverted like second:5, hour:10.
This is because we are using Lua tables internally so having the same limit for different period wouldn't be possible and the last one would override the previous ones, for example if we had 5:second, 5:hour then 5:hour would be the only one available since the unique key 5 is being used two times.

That's just a matter of how you parse them.

PR for documentation/website change is here : https://github.com/ind9/getkong.org/pull/1

:+1:

Closed with #382.


Beacon multiple pairing (IOS build 99

try with https://talao.co/sandbox/saas4ssi/dapp
wallet receive 2 messages to pair

pb version ?


Uploading image with HTTPS enabled fails

Describe the bug
When I have HTTPS/Cloudflare proxying on, images fail to upload and auto-save functionality fails (and leaves notifications).
Turning off cloudflare HTTPS rewrites/proxying resolves the issue.
(Note: I am using Cloudflares free SSL in Flexible mode)
Steps To Reproduce
Steps to reproduce the behavior:

Ensure HTTPS is enabled via Cloudflare DNS
Navigate to page
Edit page
Attempt to upload image to server.
Image upload fails.

Expected behavior
Image should upload while HTTPS is enabled.
Screenshots
https://i.imgur.com/WynIsJD.png
https://i.imgur.com/RacXJXl.png
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v0.27.5
PHP Version: 7.1.33
Hosting Method (Nginx/Apache/Docker): Apache

Additional context
Add any other context about the problem here.

I resolved my problem by changing from "Flexible" SSL over Cloudflare to Full SSL using signed certs/keys on my host server.
Images/content load over mixed connections (http/https). I'm hoping I can ask for a solution to this instead, forcing all images/etc to load over https.
Thanks!

And I fixed my issue with mixed content by setting my APP_URL.


feat(esl-utils): allow to pass array of targets to the ESLEventListener

:tada: This PR is included in version 4.0.0-beta.15 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(PanoImageRenderer): make preserveDrawingBuffer false

Issue
#139
Details

fix(PanoImageRenderer): make preserveDrawingBuffer false

Coverage increased (+0.1%) to 89.91% when pulling d17c63f2e27678fb1a719dcbb8ba436ea63915e1 on PanoImageRenderer#139 into 29a81bdf90d245f4d19fcb94a5c92525617c2a28 on 3.0.0-rc.


Add flip_h and flip_v properties to textures

Allows textures to be flipped horizontally or vertically during UV mapping, allows for fixes when mapping textures from existing sources such as Pokemon XYORAS's BCLIMs.
Before:

After:

The pointer texture was loaded with it's data pointing directly to the decompressed bclim data from the box data DARC in Pokemon ORAS. The Mega Charizard had to be "depaletted" into an RGB5A1 texture, but no other changes were made. In their normal state, they were flipped, and by adjusting flip_h and flip_v to 1, both were returned to normal.

Actually it seems like the UVs are being mapped backwards only vertically? The image itself is being pulled starting from the bottom left and up however tall the image is. I was right in that the images needed a vertical flip, but the horizontal flip wasn't needed. The PR still works as-is, but it seems that there's still some funky stuff going on with UVs.

Have you tried using the scale function and passing -1, -1 as the scale values? It should to the flipping.

I'll try that later today, didn't think to do that. If I can flip using scaling and adjust the UVs, having a wrapper function on my end won't hurt too much.

That works, although I have to translate the texture down an added amount of how tall the image is.
sf2d_draw_texture_part_scale(texture, x, y+texture->height, 0, next_pow2(texture->height) - texture->height, texture->width, texture->height, 1, -1);

Is what I ended up wrapping it in to get it to work. In any case I'll go ahead and close this up.


QuickDebug.h not found

Steps to reproduce

Added library to arduino
Tried compiling, but failed with error "QuickDebug.h" could be located.

I checked you code. it looks like you have used DEBUG_DBG to print debug logs.
Solution

Please add "QuickDebug.h"

Can confirm I just encountered exactly the same issue.

You need to install https://github.com/gmag11/QuickDebug too

With latest release (https://github.com/gmag11/QuickESPNow/releases/tag/0.7.0) QuickDebug is not required if you don't need to get debug messages


Allow predicting backwards in predictor

Currently, the predictor uses the time difference of a state to a new time (assuming the time will always be positive) the predicted covariance uses this time difference. If one were to want to predict backwards, i.e., the new time occurs before the current state, the time difference is negative and therefore the predicted covariance (which uses the negative time difference) creates a covariance with negative elements.
I suggest the covariance calculation uses the absolute time difference rather than the time difference to allow the covariance to remain positive when predicting backwards in time.

We may want to be careful with this one. If the reason you get a negative time-difference is because due to out of sequence measurements, simply processing measurements with an absolute time difference is not the correct approach. I have found myself in situations where I hadn't ordered the measurements correctly and the fact I was getting negative covariances enabled me to debug my issues.

+1 for OP, +1 for note of caution. Whilst inferring backward in time is useful for out-of-sequence and track stitching, it's not strictly 'prediction' (retrodiction perhaps?). The physicist part of me appreciates the arrow of time and that if we were to wind it back slightly covariances can decrease (dependent on the model) - and as Lyudmil says, one can go too far and end up with 'unphysical' estimates, which is a useful sanity check.
How about a separate Retrodictor class? That would allow a distinct backward-in-time transition model which could be symmetric (i.e. use absolute time), or use a reversible transition model, or something a bit more heuristic. The latter recognising that track stitching is often done very ad-hoc.


cargo-shear: init at 0.0.24

Description of changes
Adds https://github.com/Boshen/cargo-shear, a tool for detecting and removing unused dependencies from your Cargo.toml.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

works pretty well, even found an unused dependency in one of my actual projects.


pdctl: improve the output of faild commands

Signed-off-by: nolouch<EMAIL_ADDRESS>
What problem does this PR solve?

unknow the result meaning.
What is changed and how it works?
improve the output.
Check List
Tests

Manual test (add detailed scripts or steps below)

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1962   +/-   ##
=========================================
  Coverage          ?   77.88%
=========================================
  Files             ?      170
  Lines             ?    16875
  Branches          ?        0
=========================================
  Hits              ?    13143
  Misses            ?     2704
  Partials          ?     1028

Impacted Files
Coverage Δ

tools/pd-ctl/pdctl/command/global.go
66.03% <0%> (ø)

tools/pd-ctl/pdctl/command/operator.go
68.53% <100%> (ø)

Continue to review full report at Codecov.

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

/merge