Added support for upgrading<EMAIL_ADDRESS>projects solving #932

Added support for upgrading<EMAIL_ADDRESS>projects solving #932

Coverage remained the same at 100.0% when pulling 737671ba3499b651cd204daf00ffcd491a409cb7 on waldekmastykarz:spfx-180 into d3b1450e4de1ae3eb4e5664a263e3ec6c81205c7 on pnp:dev.


Multiple Account Login Results in Duplicate Articles

When using the Reddit extension with more than one Reddit account, Netnewswire does not respect individual account subscriptions and generates duplicate articles.


WIP JDK 20

https://issues.apache.org/jira/browse/SOLR-XXXXX

Closing since main is on jdk 21 now


Pin connexion[swagger-ui]

Connexion 3.0 was released earlier this month and is breaking workflow. Pinning it to < 3.0.0.

Merging in spite of the failed integration workflow, as the PR fixes the issue.


[HTTP] Need a native function to get entity as "application/octet-stream"

When the content-type header is not available, entity should be consider as application/octet-stream. Hence, we need a native function that can return a blob.

Doesn't the already existing function getBinaryPayload() satisfy this requirement?
https://github.com/ballerinalang/ballerina/blob/master/modules/ballerina-http/src/main/java/org/ballerinalang/net/http/nativeimpl/request/GetBinaryPayload.java

This has been implemented.


Db tests fixed example

Codecov Report

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

@@              Coverage Diff               @@
##             development      #39   +/-   ##
==============================================
  Coverage               ?   78.43%
==============================================
  Files                  ?        9
  Lines                  ?       51
  Branches               ?        1
==============================================
  Hits                   ?       40
  Misses                 ?       10
  Partials               ?        1

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 43a7093...507759b. Read the comment docs.


Automated script for OpenMAVN deployment in Azure subscription

Include basic setup for including deployment of Back End components, mobile app, and settings service.
@thelittledevops

@thelittledevops please work with @PaterSantyago to create sub tasks and define the issue in further detail


ARROW-16268: [R] Remove long-deprecated functions

Also has a fix for the check NOTE about union_all and distinct.

Windows CI crash looks like it may be related to https://github.com/apache/arrow/pull/13521 cc @wesm

Sorry about that -- I see the error in #13521 but I misread the error that it looked like a flake
https://github.com/apache/arrow/runs/7243906864?check_suite_focus=true
What's the best way to diagnose so I can try to fix?

I looked to the end of the verbose test output, where you see test-chunked-array running and then it dies after the assertion on L260: https://github.com/apache/arrow/runs/7243906864?check_suite_focus=true#step:11:6360
So I checked out what's happening in the test. By my reading of the output, it does not always occur, but when it does, it happens when you Filter an empty ChunkedArray with another (boolean) empty ChunkedArray: https://github.com/apache/arrow/blob/master/r/tests/testthat/test-chunked-array.R#L265

I've spent about an hour tinkering on this and I feel somewhat powerless to debug the problem. Are there instructions about how to debug the mingw32 RTools 4.0 C++ build on Windows? We don't run the C++ unit tests when building the Arrow libraries, and my guess is that running arrow-compute-vector-test in a debug build will reveal the issue (and with mingw32 we can use gdb to find out where the issue is coming from)? If there's someone better equipped to help identify the issue I would really appreciate it.

I don't have access to a Windows VM right now otherwise I would try to do it myself, but it should be sufficient to build the C++ library locally with the mingw32 RTools toolchain and run the unit test suite -- building the R package may not be needed

I haven't yet built the 32-bit version, but I will look into that now. My instructions for 64-bit are here FWIW: https://www.datawill.io/2022/04/02/windows-apache-arrow-development-environment-with-rtools-4-0/

Just confirming here also that https://github.com/apache/arrow/commit/88b42ef66fe664043c5ee5274b2982a3858b414e fixed the issue


Adding utch.edu.mx domain

https://www.utch.edu.mx/index.php/tecnologias/

@EnriqueMascote I am sorry, I have to close the request without merging, because you made a mistake in a request and requested to merge too many files, most of them do not relate to the organization which you would like to add to this repository. Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Add service annotations

Which problem is this PR solving?
When I use the jaeger operator, I need to add the annotations of the jaeger-query or jaeger-collector service. But the jaeger-operator do not supply the function. So I alter the code to supply this.
Short description of the changes

I didn't alter the jaeger's type , just use the Annotation field. Before, it's just use to the component deployment, now I add the code to use it to the component service .

For the issue
https://github.com/jaegertracing/jaeger-operator/issues/1534
https://github.com/jaegertracing/jaeger-operator/issues/1096

@rubenvp8510 could you please take a look and review the PR.

Ahh the ci thing was also failing. calling make format should fix it.

I have performed the fix operation, waiting for the review.


Metrics reference is for (unreleased) v1.29

Fixes #44008
To fix this issue, this PR revert this PR -> #42823

@kubernetes/sig-docs-en-owners

/assign @sftim

/lgtm


AWS: deploy doesn't work with many dependencies

1 validation error detected: Value '{git=git@40github.com@3Aadobe@2Fhelix-resolve-git-ref.git@238041cbe3f89b7b5efed9d7e4aedf37a2653f907d, repository=https@3A@2F@2Fgithub.com<EMAIL_ADDRESS>updated=1607869330560, pkgVersion=1.7.17_hedy, dependencies=@adobe/gh-resolve-ref:1.1.0,@adobe/helix-fetch:1.9.2,@adobe/helix-log:4.5.3,@adobe/helix-status:8.2.3,@adobe/openwhisk-action-utils:4.4.0,already:1.13.2,asynckit:0.4.0,balanced-match:1.0.0,big.js:6.0.2,brace-expansion:1.1.11,buffer-from:1.1.1,bunyan:1.8.14,callguard:2.0.0,centra:2.4.0,colorette:1.1.0,combined-stream:1.0.8,concat-map:0.0.1,core-util-is:1.0.2,delayed-stream:1.0.0,dtrace-provider:0.8.8,ferrum:1.7.0,fetch-h2:2.5.1,form-data:3.0.0,get-stream:6.0.0,glob:6.0.4,http-cache-semantics:4.1.0,inflight:1.0.6,inherits:2.0.4,isarray:1.0.0,lodash.isplainobject:4.0.6,lru-cache:6.0.0,mime-db:1.43.0,mime-types:2.1.26,minimatch:3.0.4,mkdirp:0.5.5,mv:2.1.1,ncp:2.0.0,node-fetch:2.6.1,object-sizeof:1.6.1,once:1.4.0,path-is-absolute:1.0.1,phin:3.4.1,process-nextick-args:2.0.1,psl:1.8.0,readable-stream:3.6.0,readable-stream:2.3.7,rimraf:2.4.5,safe-buffer:5.1.2,safe-json-stringify:1.2.0,serverless-http:2.6.0,source-map:0.6.1,source-map-support:0.5.19,string_decoder:1.1.1,throat:5.0.0,through2:4.0.2,to-arraybuffer:1.0.1,tough-cookie:4.0.0,triple-beam:1.3.0,universalify:0.1.2,util-deprecate:1.0.2,webpack:4.41.2,winston-transport:4.3.0,wrappy:1.0.2,yallist:4.0.0}'
at 'tags' failed to satisfy constraint: Map value must satisfy constraint: [Member must have length less than or equal to 256, Member must have length greater than or equal to 0, Member must satisfy regular expression pattern: ^([\p{L}\p{Z}\p{N}_.:/=+\-@]*)$]

256 chars don't give us too much wiggle room. We could create one tag for each dependency or just truncate the value.

for now I would ignore the dependency information or put it inside a dependency.json in the zip.
we can later figure out how to retrieve it efficiently.
in any case with I/O runtime we already have a comprehensive database of all the actions and dependencies.
so, if we need to figure out which action/version contains a certain dependency, we can retrieve it there.


Fill system health flags in commander for automated checklists

What this is about
This PR fills many of the sensor/system health flags of the MAVLINK SYS_STATUS message. Therefore, this PR implements the functionality that allows proper system health evaluation in ground stations. It thereby also enables automated checklists, and is thus the counterpart to the QGroundControl automated checklist PR at https://github.com/mavlink/qgroundcontrol/pull/6364.
Notes on implementation

This heavily cleans up the previous subsystem_info publishing code and centralizes this more towards commander/preflightCheck and the voted_sensors_update.cpp files. Some drivers (optical flow, distance sensor) still publish their own subsystem_info, which is why the interface functions in src/modules/systemlib/subsystem_info_pub.cpp are required. If at any point the decision that each and every sensor or capability can be checked entirely inside commander/preflight check is taken, then these interface functions can be removed.
The convention of the health flags in the MAVLINK SYS_STATUS message was a bit confusing at first, but with @dagar we discussed that "enabled"=the user actually wants the sensor to work and thus the sensor should deliver valid data, "present"=the sensor is installed (i.e. has responded in some initial form to a request, but it may deliver invalid data), "health" = the sensor actually delivers valid data (which requires that the sensor is present). This is also how QGC seems to define this. The question whether the user has enabled a sensor is inferred mostly from the parameters that the user set.

Testing status
Tested extensively in the lab for various missing, failing or uncalibrated sensors or systems (Mag, Gyro, Accel, Baro, DiffPressure, RC Transmitter, GPS, Global Position Estimate aka EKF2 validity checks). A previous version (based on an older master) was already used during some fixed-wing test flights.
Next (related) steps

Submit a Mavlink PR that adds the SUBSYSTEM_TYPE_MISSION health flag in mavlink, too.
Get the QGC PR (mavlink/qgroundcontrol#6364) merged.

@dagar This is the PR that we have been discussing for a while rebased on the current master.

Very cool! I haven’t reviewed the code yet but we really needed this subsystem to be improved.

So if I've followed this correctly the modules aren't actually publishing, but writing directly into commander's vehicle_status? That's okay from other parts of commander, but shouldn't be done from other modules.
I'm also not sure that it's worth staying tied to these mavlink SYS_STATUS flags within PX4. Having all of this information within commander via vehicle_status_flags would be tremendously valuable for locking down arming or handling other things in the state machine. Then the mavlink module would be responsible for mapping vehicle_status_flags -> SYS_STATUS.onboard_control_sensors_present, etc.

So if I've followed this correctly the modules aren't actually publishing, but writing directly into commander's vehicle_status?

The modules are calling the publish_subsystem_info_xxx functions in the systemlib, and these functions then (via a pointer that was initialized when commander started) write into commander's status->onboard_control_sensors_present/... variables. The code used for writing is exactly the same as before, it is found here. Also note that these modules are actually only changing those bitfields that commander itself isn't writing because the respective checks are not implemented yet. There is thus no risk of a "write conflict".

That's okay from other parts of commander, but shouldn't be done from other modules.

Why do you mean? Sure, it would be "nicer" to have this completely in commander, i see that, but i dont get why it would be "strictly forbidden". The current situation is:

The RANGEFINDER type sensors are the only sensors that actually publish health information via the publish_subsystem_info_xxx functions -> This could easily be changed such that this is handled inside commander.
The only other code where external modules are using publish_subsystem_info_xxx is in the voted_sensors functions (here  ), which constantly updates the health states of all sensors. -> This cannot be changed that easily, i.e. unless one would pull the complete sensor health checking code inside commander. That's why I think we need a method to write commander health flags from external modules.

I'm also not sure that it's worth staying tied to these mavlink SYS_STATUS flags within PX4. Having all of this information within commander via vehicle_status_flags would be tremendously valuable for locking down arming or handling other things in the state machine. Then the mavlink module would be responsible for mapping vehicle_status_flags -> SYS_STATUS.onboard_control_sensors_present, etc.

Personally i don't care in what health flags these states are stored. But this decision on whether we stick with the mavlink style or use commander's vehicle_status_flags (and then do the transition somewhere else) then would need to be taken very quickly by your @dagar or by @LorenzMeier . Adapting the code of my PR to using commander's vehicle_status_flags would be very simple, but given that tons of new commander health flags would need to be defined (and you @dagar have been driving this) I'd actually think its better if you @dagar would then just take my PR (i.e. especially the IMHO somewhat improved sensor checking in PreFlightCheck) and quickly adapt it to whatever commander vehicle_status_flags you want. What do you think?

@dagar Updated as per our discussions. This means:

Swtiched back to uORB for inter-module communication
GPS checks are now completely handled by the ekf2check
Distance sensor / rangefinder checks inside the drivers removed, this is now handled by preFlight check.

Looking good. Within commander can the flags be set directly in the bitfield? If you still need the systemlib portions after that please move it to a new library under lib. We're slowly trying to get rid of systemlib.
If you rebase on current master the CI failures should go away.

Looking good. Within commander can the flags be set directly in the bitfield? If you still need the systemlib portions after that please move it to a new library under lib. We're slowly trying to get rid of systemlib.

@dagar Updated. Two questions remain:

I opted for a hybrid solution w.r.t. directly writing the bitfields inside commander. Commander still calls the publish_subsystem_info function from the lib/ folder (which is nice because it is much more compact and consistent than writing the bitfields with bitwise operators directly), and then passes a pointer to its vehicle_status_s variable. Outside of commander calls to publish_subsystem_info use uORB. See https://github.com/PX4/Firmware/pull/9436/files#diff-da432bc423dd61237ace87aad8d3359bR69 . Is this OK for you or does this still pose thread-safety issues?
Do you know a better way to check whether we need to check the distance sensor than the mess I am doing here?

That looks safe, although to be honest it's a bit misleading to call something publish that doesn't publish and to automatically determine that behaviour based on a pointer argument being null or not. If you really want to share this then I'd suggest extracting the core parts that are actually common and then calling that from separate helpers for either publishing subsystem_info or directly setting vehicle_status.

As far as I know all actual usage of distance_sensor in the system depend on the estimator. I think it's ultimately the configuration of the estimator that dictates if it's enabled and considered active or healthy. We have similar issues with GPS and optical flow that need to be sorted out. In general try not to access parameters outside of the relevant module. Parameters are culled from a build if the module isn't included.

@LorenzMeier @dagar So whats the decision here? Merge this "now" (https://github.com/PX4/Firmware/milestone/24), i.e.as soon as you give the OK, and then @bkueng refactors voted_sensors for https://github.com/PX4/Firmware/milestone/25?

Rebased. All checks passing now.

I need to have another pass to make sure I’m not missing anything. But looking great!

@LorenzMeier @dagar Any update?

@bkueng All your feedback was integrated, LGTM?


Glob function is slow & inefficient

Hi, like the title says, the glob function (https://github.com/fsspec/adlfs/blob/main/adlfs/spec.py#L576) is slow and inefficient in specific use-cases (especially when using azure data lake gen 2's hierarchical namespace) because from the first * it stops matching and just requests everything after it.
In our use case, we've got data structured with a few columns which are often used to filter, then followed by year/month/day(/hour).
So if we have files like these for about 3 years, with the filter columns having a cardinality of 5 values (as an example), with 1 file per hour:
some/common/prefix/filtercol1=somevalue1/filtercol2=somevalue2/year=2023/month=01/day=12/hour=01/0.parquet
and then want to query all files from a specific day and filtercol2 value, but we don't care about the filtercol1 value like so:
some/common/prefix/filtercol1=*/filtercol2=somevalue2/year=2023/month=01/day=12/hour=*/*.parquet
We would like to have to check 5 * 1 * 1 * 1 * 24 = 120 files
But instead, the implementation of the glob function checks 5 * 5 * 3 * 365 * 24 = 657000 files (as far as we understand)
We've got a working example that does nothing of the fancy stuff of the current _glob function, but saves us about 50 euros per day (difference seen in azure cost management) just by not listing all the files all the time: https://github.com/mh-data-science/adlfs/blob/master/adlfs/spec.py#L689, not to mention the difference in speed.
Known issue: we don't support ** this way (i.e. * is only valid between two / characters, we're traversing the actual folders), and probably not a lot of the kwargs stuff or other fancy things either.
So questions:

Are we correct in our understanding of the current _glob function?
If yes, what do we need to do to get this conceptual improvement into the main branch?
Feedback on our glob code and how to add ** support always welcome, especially if a pull request is expected

I'm pretty sure there has been a big regression in the performance of glob at some point.
2022.11.0: 2 seconds
2024.1.0: After about 3 hours it fails and never completes.

I can confirm this and have an implementation of glob for all azure filesystems that supports ** (recursive directory match) and doesn't have this problem. It's critical to my team as well because we have folders with cardinality on the order of millions. I can try to create a PR, but I'm not familiar with this code base yet.


Make height between image and button configurable

Thanks for the pull request, but that feature is already added in this pull request https://github.com/MortimerGoro/MGSwipeTableCell/pull/145


Screen flicker on linux ubuntu on my c720

whenever im on my acer c720's linux using crouton my screen flickers to the chrome OS screen,
it happend after i reloaded linux once
the time i installed it and immediatly loaded it, it was perfect,
but one time it randomly crashed and now i reloaded it and it flickers
IT BUGS ME ALOT

Started having this problem on the Pixel 1 too (using Xorg). Just tried updating to latest crouton, no dice. It sporadically flickers to chrome OS when using crouton. Possibly an interaction between the xorg and xiwi target; every time it flickers it emits a " => message from non-tab target" to the crosh, and disabling the extension makes it flicker less, but then it emits a "croutonwebsocket error: Error: not connected."
Chrome OS version: 50.0.2661.91 beta (64-bit)
croutonversion:
crouton: version 1-20160420122426~master:46f3c372
release: trusty
architecture: amd64
xmethod: xorg
targets: xorg,xiwi,touch,xfce
host: version 7978.66.0 (Official Build) beta-channel link
kernel: Linux localhost 3.8.11 #1 SMP Wed Apr 27 15:27:04 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

Hello.
I'm using same env as Mr.DerpyKirby (crouton/Ubuntu on c720), and the flicker had occurred.
After running of crouton's script,  I changed my Chrome OS channel from stable to beta, and Ubuntu began to work correctly.
(Possibly it was a bad method. But some crouton's problem are complex because of the combination of Chrome OS, crouton and OSes on crouton. so, sometimes I try changing the channel.)

I have encountered the screen flicker now as well. It does not seem to occur immediately after a restart, but some time later (perhaps after the machine sleeps, I haven't figured it out yet) it comes back. In particular, using ctrl-alt-right to go to the chroot works, but very frequently (but not consistently --- sometimes more than once a second) the screen will flicker back to the Chrome OS screen+browser.
I'm on a c720p.
I've updated crouton, but that has not fixed the flicker. I've been using crouton for several years, and this is new. I suspect it has something to do with the most recent Chrome OS update.

I also have been experiencing this screen flicker issue since the last Chrome OS update. It does not appear for me when Chrome OS is freshly restarted and then I start up crouton, but it does happen after my computer has fallen asleep.
I'm on a c720p as well.
version 1-20160420122426~master:46f3c372
trusty

Exact same thing as slhale, but I use xfce.

I'm having the same issue on Dell Chromebook 11 using xfce. This is from the console when it happens.
`No Chromium OS X server is available.
_IceTransmkdir: ERROR: euid != 0,directory /tmp/.ICE-unix will not be created.
xfce4-session: No gpg or ssh authentication agent found
/usr/bin/xbindkeys_autostart: line 24: CONF: unbound variable
(xfwm4:27203): GLib-CRITICAL **: g_str_has_prefix: assertion 'prefix != NULL' failed
(xfwm4:27203): xfwm4-WARNING **: The property '/general/double_click_distance' of type int is not supported
(polkit-gnome-authentication-agent-1:27223): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
(polkit-gnome-authentication-agent-1:27223): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
(xfsettingsd:27229): GLib-CRITICAL **: g_str_has_prefix: assertion 'prefix != NULL' failed
Timeout waiting for extension to connect.
Cannot open /sys/class/tty/tty0/active: No such file or directory
croutonwebsocket error: Error: not connected.(II) AIGLX: Suspending AIGLX clients for VT switch
Error: target STRING not available
croutonwebsocket error: EError: not connected.(II) AIGLX: Suspending AIGLX clients for VT switch
Error: target STRING not available`

The v51 is now on the stable channel, and I updated from 50.0.2661 to 51.0.2704, and the problem seems to be resolved for me (C720, unity target, on Ubuntu trusty).

I tried the fix in the second post of #1519 and it does not stop the flickering for me (C720, trusty). I have not received the v51 update yet, but keeping my hopes up!

I myself had to manually check for updates manually to get it: https://support.google.com/chromebook/answer/177889?hl=en
If that doesn't work, you might be able to get it from the beta channel: https://support.google.com/chromebook/answer/1086915?hl=en
You can always go back to stable just after getting v51, if you're not comfortable running beta software in the long run.

I also have flickering in ChromeOS only not Ubuntu
this only started after presumed crash, when battery dried up.
It would be nice to have some guidance on procedure to identify problem....

deleting $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc
wfm
https://forum.kde.org/viewtopic.php?f=289&t=128589


rocket->hipchat. "You must be in this room to send a message."

I'm having problem with sending message from rocket.chat to hipchat. See below.
What I'm doing wrong?
hipchat->rocket doesn't work at all
p.s. we are using our own hipchat server, not on hipchat.com.
Which version of matterbridge are you using?
# matterbridge-linux64 -version
version: 1.0.0-rc1 c28b876

Please describe the expected behavior.
Message sent to hipchat channel
Please describe the actual behavior.
2017/07/31 15:14:14 2017/07/31 15:14:14 {"token":"********","bot":false,"channel_id":"*******","channel_name":"tag","message_id":"e8BJzrFR3PQH7YqvJ","timestamp":"2017-07-31T12:14:14.189Z","user_id":"******","user_name":"Denis","text":"testrc2"}
<message<EMAIL_ADDRESS>type='error'<EMAIL_ADDRESS><Denis> testrc2</body><error code='403' type='auth'><forbidden xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>You must be in this room to send a message.</text></error></message>

Any steps to reproduce the behavior?

run matterbridge
send message from rocket.chat to hipchat

Please add your configuration file
[xmpp.work]
Server="hipchat.example.com:5222"
<EMAIL_ADDRESS>#Password (your hipchat password)
Password="*****"
Muc="conf.btf.hipchat.com"
Nick="denis"
RemoteNickFormat="[{PROTOCOL}/{BRIDGE}] <{NICK}> "

[rocketchat.home]
#Url is your incoming webhook url as specified in rocketchat
#Read #https://rocket.chat/docs/administrator-guides/integrations/#how-to-create-a-new-incoming-webhook
#See administration - integrations - new integration - incoming webhook
WebhookURL="https://chat.example.net/hooks/******"

#Address to listen on for outgoing webhook requests from rocketchat.
#See administration - integrations - new integration - outgoing webhook
# matterbridge is on same server with rocker.chat
WebhookBindAddress="<IP_ADDRESS>:9999"

Nick="matterbot"
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "

[[gateway]]
name="mygateway"
enable=true

    [[gateway.inout]]
    account="xmpp.work"
    channel="1_rc-test"

    [[gateway.inout]]
    account="rocketchat.home"
    channel="#tag"

Oh, never mind. I've missed:
<error code='406' type='modify'><not-acceptable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'>Please use the nickname "Denis Kot" instead of "denis" when joining rooms. Setup instructions for common clients are available at http://help.hipchat.com</text></error></presence>


Unable to configure modsecurity with XAMPP in windows

Hi,
I'm using xampp v3.2.1
I've downloaded "mod_security2-2.8.0-2.4.x-x86.zip" and configured it as per instructions (README)
After configuration I'm unable to restart apache (XAMPP) server.
Error I'm getting is,

If I remove modsecurity from configuration, it is working fine.
Please guide me on solving this issue.
Thanks.

Hi @st4rk013, Any specific reason to use 2.8 instead of 2.9 ?

Please give it a try with release 2.9.2.
Closing this one because of lack of feedback from reporters. If the problem persists let us know.

The problem persist  :
Apache <IP_ADDRESS>
mod_security-2.9.12  (the version that you like )
3:17:52  [Apache] 	Attempting to start Apache app...
BTW the guy maybe is using 2.8 because was required by his apache version ?
Thats why open source , and free software sucks , so i choiced apache instead of iis and i depend of 3º party "modules" from 3º party corporations to have basic security ...
suck my dick man

I am getting the same error with
xampp-win32-7.2.11-0-VC15-installer
mod_security-2.9.2-win32-VC15
In line with the mod_security package documentation I performed the following steps:

Copied mod_security2.so to apache/modules
Renamed apache/bin/libcurl.dll
Copied yajl.dll and libcurl.dll to apache/bin
Inserted in apache/conf/httpd.conf "LoadModule security2_module modules/mod_security2.so"
Uncommented in apache/conf/httpd.conf "LoadModule unique_id_module modules/mod_unique_id.so"
Restarted apache server - received error as reported by the OP above
Commenting out both 4 and 5 and restarting apache resolved the error, but uncommenting either or both back in generated the error again

I would appreciate any help because I wanted to test mod_secure locally.
(PHPinfo on my live site on a shared server does not display any apache configuration information, but although the host assures me mod_security is enabled I'm dashed if I can get it to do anything for me)


[WIP] Update filter on slider handle release

Apply Q filter changes on range slider release instead of whenever it is moved.
Part of https://github.com/uwdata/voyager2/issues/175

Weird bug: the event is firing properly, but the changes are only observed when the user mouses over the chart area.

I just rebased this to master for you.
However, from my testing it appears that scope.apply only forces things to update only the first time you modify the filter, but not afterward.  Thus, this is not mergable yet.

Ah found the bug, it's actually not caused by this PR.  I'll merge this awesome work then!


Graph API not enable in VSTS account

When the task in VSTS being execute, I am getting the following error:
"An error occurred while attempting to execute the scan. Error details: Failed to retrieve the list of users from the specified VSTS account. Please ensure that the Graph API is enabled on the account."
How can I resolve the issue.
Thanks

This extension utilizes VSTS APIs, and the VSTS Graph API is a crucial set of APIs that the extension needs in order to function. That error message indicates that the Graph API is not available on your account.
I believe the Graph API is still in preview, but it was supposed to be rolled out to all VSTS accounts last week. This can be enabled on your account, but has to be done by a member of the VSTS Team.
Will get back to you shortly

@yaprigal can you provide the VSTS account name(s) of the accounts you'd like to have the Graph API enabled on?
If you'd prefer to speak in private then send me an email<EMAIL_ADDRESS>and I'll get you in contact with someone who can enable the API on your VSTS account(s).
Alternatively, the Graph API should be rolled out by this time next week if you'd prefer to wait.

Thanks for the quick response. closing the issue.


Add support for a sort argument in WordNet methods

WordNet object methods support a series of methods, such as hypernyms, antonyms, etc., that under the hood use a private method called _related, that supports an argument called sort which by default is True. This argument sorts the output objects by name. For example, see:
https://github.com/nltk/nltk/blob/e2d368e00ef806121aaa39f6e5f90d9f8243631b/nltk/corpus/reader/wordnet.py#L134-L135
However, in some cases, we don't need the output to be sorted, and we may be performing these operations multiple times and on long lists, which incurs in considerable penalties because of multiple needless sorting going on under the hood.
Thus, I believe it'd be important that such methods supported a sort argument (as _related does), whose default value is True (to avoid breaking backward compatibility).

There are two _related() functions: one for lemmas, which does not support a sort argument, and one for synsets, which has sort set to True by default.
But False would be a better default, because most users  normally  don't want the output to be sorted alphabetically, and those who need it can easily sort it by themselves.
So, even though it breaks backward compatibility,  the easiest fix would be to just remove the sort option from the synsets' _related() function.

However, it seems that we need to sort the output, because otherwise it would be returned in random order, so no test would be reproducible.
Consider the hyponyms of legal action with sort set to False :
from nltk.corpus import wordnet as wn
ss = wn.synset('legal_action.n.01')
print([(wn.ss2of(x),x) for x in ss.hyponyms()])

[('01184230-n', Synset('civil_action.n.01')), ('01184407-n', Synset('counterclaim.n.01')), ('01198588-n', Synset('test_case.n.01')), ('01184045-n', Synset('antitrust_case.n.01')), ('01198307-n', Synset('prosecution.n.01')), ('01184720-n', Synset('lis_pendens.n.01')), ('01184565-n', Synset('custody_case.n.01'))]

This output is in no particular order, and subsequent runs produce a different order.
Also, while it is true that some lists may be long (up to 600 elements in a few cases), there is no reason why it would be sorted multiple times, except if the user explicitly repeated the same call, which is not likely to happen anyway, and would not be an NLTK concern.
After all, the alphabetical sort produces the nicest presentation order, and especially it is stable, so I'm not sure that this issue needs fixing.

However, it seems that we need to sort the output, because otherwise it would be returned in random order, so no test would be reproducible.
Consider the hyponyms of legal action with sort set to False :
from nltk.corpus import wordnet as wn
ss = wn.synset('legal_action.n.01')
print([(wn.ss2of(x),x) for x in ss.hyponyms()])

[('01184230-n', Synset('civil_action.n.01')), ('01184407-n', Synset('counterclaim.n.01')), ('01198588-n', Synset('test_case.n.01')), ('01184045-n', Synset('antitrust_case.n.01')), ('01198307-n', Synset('prosecution.n.01')), ('01184720-n', Synset('lis_pendens.n.01')), ('01184565-n', Synset('custody_case.n.01'))]

This output is in no particular order, and subsequent runs produce a different order.

Tests can be reproducible by taking the output and sorting it:
from nltk.corpus import wordnet as wn
ss = wn.synset('legal_action.n.01')
print(sorted((wn.ss2of(x),x) for x in ss.hyponyms()))

Also, while it is true that some lists may be long (up to 600 elements in a few cases), there is no reason why it would be sorted multiple times, except if the user explicitly repeated the same call, which is not likely to happen anyway, and would not be an NLTK concern.

My use case involves recursively visiting hypernyms and/or hyponyms of synsets that I won't know prior (they are determined at runtime). I'd need to sort multiple of them multiple times, and I need to do it quickly. See, for example, this function.
I can see other people recursively traversing such relations (or similar ones) without needing to have them in memory (creating a temporary list for them) or sorted.

After all, the alphabetical sort produces the nicest presentation order, and especially it is stable, so I'm not sure that this issue needs fixing.

I agree it's nice to see it sorted when looking at examples manually. But it'd also be nice to have it disabled for performance considerations. E.g., ls, the Unix utility to list directory contents, returns the output sorted but supports an option (-U) that doesn't sort. This option allows saving compute/time for very large directories, and it also allows saving memory because sorting typically requires making a copy in memory. In other words, it's O(n) in memory usage, unlike being O(1) if you just return them one by one and forget about the past.

Thanks @bryant1410 for your suggestion to sort the tests' output. However, this would not be necessary if we keep sort=True as default.
Considering your use case, if it was possible to specify sort=False,
would it then really be computationally cheaper to keep making multiple identical calls, rather than caching (eventually all) the results in memory?

Considering your use case, if it was possible to specify sort=False,
would it then really be computationally cheaper to keep making multiple identical calls, rather than caching (eventually all) the results in memory? Wordnet has around 100,000 synsets, 200,000 lemmas, and a limited number of relations, so everything fits easily inside a manageable python dictionary with O(1) lookup.

As you can see in the linked function, I'm already caching its result (among other functions' results I also cache). This function has a @functools.cache.

Thanks @bryant1410! Your linked source script contains the following comment:

# For the following two functions: we use _related instead of the actual nice names to avoid sorting unnecessarily.
# @ = hypernyms
# ~ = hyponyms

And you solve the present issue like this, using nothing else than what is already available in NLTK:
 for parent in synset._related("@", sort=False):
So users have presently two options: use hypernym() if they want sorted output, or use the lower-level _related() if they want more control.
This seems to justify closing this issue as "already fixed", especially when very little time is available for review or merging eventual PRs.

IMHO, what I'm doing is more like a workaround than a solution. _related is a private method, meaning somebody in NLTK could move, remove, or rename it without considering backward compatibility.
The solutions I see for this are:

Making this method public and, as such, part of the supported public API.
Adding sort to the public methods. I think this one is better.

Besides this, it'd be great if _related avoided creating a list when sort=False. Note that I'm calling this method repeatedly in a short time, and it'd be great if I could avoid incurring extra memory and compute. It could return a generator.
I'd be happy to submit a PR.

That sounds great, @bryant1410, and you're very welcome to submit a PR! Please note that these functions are called in many doctests all around, and especially in nltk/test/wordnet.doctest. The tests would fail if the output order changed. But you wrote earlier that you will maintain backward compatibility, so your proposal is fine.

Do any of the public methods that call _related() have docstrings that promise a sorted result? I prefer the solution that _related() does not sort by default.
Are there use cases for returning an iterator instead of a list? (E.g. large result sets? How large do they get?)

Are there use cases for returning an iterator instead of a list? (E.g. large result sets? How large do they get?)

My use case would be to avoid constantly creating temporary lists. Each of them is typically very short. I listed each relation size for each English synset and got these stats:
count<PHONE_NUMBER>00
mean          1.643047
std           5.655514
min           1.000000
25%           1.000000
50%           1.000000
75%           1.000000
max         661.000000

(Though note the most frequent synsets may get larger ones on average.)

I prefer the solution that _related() does not sort by default.

Me too: it breaks backward compatibility, but the current defaults are not optimal. Moreover, returning a generator is also often quicker than a list.

Are there use cases for returning an iterator instead of a list? (E.g. large result sets? How large do they get?)

A very plausible use case could be that you want to check if two given synsets are directly connected. Synsets have only a very small number of hypernyms, but they may have many hyponyms. In that case, it is advantageous to stop computing more hyponyms as soon as the required target is found. I tested this effect, using the new parameters available in PR #3240, finding that the speedup is huge (over 10x) when the target is at the start of the list, but still high (58%) in the median position:

from nltk.corpus import wordnet as wn
import timeit

def speedup(t1,t2):
    return round((100*t1/t2)-100, 2)

def check_hypo_list(source, target):
    return target in source.hyponyms(sort=False, force_list=True)

def check_hypo_generator(source, target):
    return target in ss.hyponyms(sort=False, force_list=False)

def testcase(ss, goal):
    t1 = timeit.timeit(lambda: check_hypo_list(ss, goal), number=100)
    t2 = timeit.timeit(lambda: check_hypo_generator(ss, goal), number=100)
    print(f"| {goal.name()} | {speedup(t1,t2)}% |")

#ss = wn.synset('man.n.01')
ss = wn.synset('woman.n.01')

# Test a randomly ordered list of hyponyms:
hypos = ss.hyponyms(sort=False, force_list=True)
print(f"Checking {len(hypos)} hyponyms of {ss.name()}:\n")
print("| Synset | Speedup |")
print("|--------|---------|")

for goal in hypos:
    testcase(ss, goal)

print("|--------|---------|")

# Retest the median position:
goal = hypos[len(hypos)//2]
testcase(ss, goal)

Checking 58 hyponyms of woman.n.01:

Synset
Speedup

nymph.n.03
1055.79%

eyeful.n.01
808.67%

unmarried_woman.n.01
644.24%

nullipara.n.01
546.76%

girlfriend.n.02
496.08%

heroine.n.02
434.9%

nanny.n.01
376.01%

coquette.n.01
332.75%

white_woman.n.01
303.59%

inamorata.n.01
274.54%

old_woman.n.01
248.17%

bridesmaid.n.01
227.85%

lady.n.01
199.07%

widow.n.01
181.02%

maenad.n.01
171.69%

smasher.n.02
151.89%

wonder_woman.n.01
145.24%

girl.n.01
136.59%

amazon.n.01
127.05%

ball-buster.n.01
117.97%

dominatrix.n.01
109.49%

sylph.n.01
102.35%

vestal.n.01
95.0%

donna.n.01
90.53%

divorcee.n.01
85.16%

cat.n.03
78.66%

gravida.n.02
72.16%

dame.n.02
63.75%

wave.n.09
64.57%

girl.n.05
58.12%

girlfriend.n.01
47.55%

cinderella.n.01
49.99%

maenad.n.02
52.94%

mistress.n.01
40.44%

nymphet.n.01
39.26%

matriarch.n.01
35.61%

bluestocking.n.01
34.15%

gold_digger.n.02
31.52%

wac.n.01
29.87%

matron.n.03
25.65%

jilt.n.01
24.7%

yellow_woman.n.01
22.37%

mestiza.n.01
19.15%

broad.n.01
17.45%

ex-wife.n.01
14.9%

shiksa.n.01
13.65%

bachelor_girl.n.01
11.49%

jezebel.n.02
10.26%

enchantress.n.01
8.74%

black_woman.n.01
6.85%

mother_figure.n.01
5.34%

debutante.n.01
3.89%

wife.n.01
2.13%

matriarch.n.02
2.63%

b-girl.n.01
-0.57%

baggage.n.02
-2.09%

geisha.n.01
-3.0%

prostitute.n.01
-5.92%

--------
---------

girl.n.05
58.55%

Changing the default output order of the relations would have far-reaching consequences, since it would modify the output of higher order functions like closure  and tree, and deeply alter the topology of the relation trees.
But a "middle of the road" alternative is possible, that combines the advantages of both the old and the optimized approach:
keeping the plain relation functions unchanged, and adding  a new set of "quick" functions (quick_hypernyms(), quick_hyponyms(), and so on ...), which call a _related_generator() function:
    def _related_generator(self, relation_symbol):
        get_synset = self._wordnet_corpus_reader.synset_from_pos_and_offset
        if relation_symbol not in self._pointers:
            return []
        pointer_tuples = self._pointers[relation_symbol]
        yield from (get_synset(pos, offset) for pos, offset in pointer_tuples)

This approach allows to postpone the choice of eventually shifting to better defaults later on.

it would modify the output of higher order functions like closure and tree, and deeply alter the topology of the relation trees.
@ekaf can you please clarify how?

Also, do any docstrings of functions that call _related() promise sorted results?

Also, do any docstrings of functions that call _related() promise sorted results?

None of these functions has any docstring, so they don't promise anything. Nevertheless, they have returned stable output for so long that users may expect some stability.
Functions like closure and tree repeatedly call a given relation on all the outputs of that relation. So when the output order changes, it may also  impact the output order at each level of the tree. It gets worse when redundant branches are truncated, because the truncations can occur at different places of the tree, depending on which node is traversed first.

Looping over all the noun synsets in WordNet shows some examples of differences in the tree outputs.
However no particular difference is ever guaranteed, since the unsorted order is random, and may or may not be identical to the sorted order by pure chance.
from nltk.corpus import wordnet as wn
from pprint import pprint
ss = wn.synset('medoc.n.01')

With tree(), using the default hypernyms(sort=True):
pprint(ss.tree(lambda s: s.hypernyms(), depth=2))

[Synset('medoc.n.01'),
[Synset('bordeaux.n.02'), [Synset('wine.n.01')]],
[Synset('red_wine.n.01'), [Synset('wine.n.01')]]]

With tree(), using the new hypernyms(sort=False):

[Synset('medoc.n.01'),
[Synset('red_wine.n.01'), [Synset('wine.n.01')]],
[Synset('bordeaux.n.02'), [Synset('wine.n.01')]]]

The difference can become bigger with acyclic_tree(), since it discards all the cycles, truncating the output tree, from the place where it detects a cycle:
pprint(ss.acyclic_tree(lambda s: s.hypernyms(), depth=2))
With acyclic_tree(),  using the default hypernyms(sort=True):

[Synset('medoc.n.01'),
[Synset('bordeaux.n.02'), [Synset('wine.n.01')]],
[Synset('red_wine.n.01')]]

With acyclic_tree(), using the new hypernyms(sort=False):

[Synset('medoc.n.01'),
[Synset('red_wine.n.01'), [Synset('wine.n.01')]],
[Synset('bordeaux.n.02')]]

What about just adding an optimized public related method, and leaving everything else unchanged:
   def related(self, relation_symbol):
        """
        :param relation_symbol: the pointer symbol of a synset relation
        :type relation_symbol: str
        :return: an iterator over the relation targets in random order.

        >>> ss = wn.synset('girlfriend.n.01')
        >>> print(sorted(ss.related("hypernyms")))
        [Synset('friend.n.01'), Synset('woman.n.01')]
        """
        if relation_symbol not in self._pointers:
            return iter([])
        return (self._wordnet_corpus_reader.synset_from_pos_and_offset(pos, offset)
                for pos, offset in self._pointers[relation_symbol])

What about just adding an optimized public related method, and leaving everything else unchanged?

Interesting idea, though it risks making code less readable, having two ways of doing nearly the same thing.

the unsorted order is random

Are you sure? I suspect the unsorted order is based on the order that related synsets appear in the underlying corpus. I'd be grateful if you wouldn't mind checking.

@stevenbird, in the Wordnet db, relation targets are ordered by byte offset, which is not a meaningful order.
Nltk makes it a set:

436:        self._pointers = defaultdict(set)
1648:                    synset._pointers[symbol].add((pos, offset))

These sets are unordered, and one can observe that their output order changes arbitrarily.
A further optimization is possible: since _self.pointers is a defaultdict, there is no need to check that relation_symbol is present in it.
I also suggest making the private _related() a wrapper around the optimized wnrel() (or any other better name):
    def _related(self, relation_symbol, sort=True):
        """
        Get the output of 'wnrel' as a list, by default sorted.

        :param relation_symbol: the pointer symbol of a synset relation
        :type relation_symbol: str
        :return: a list of this synset's relation targets

        >>> ss = wn.synset('girlfriend.n.01')
        >>> print(_related(ss.wnrel("@")))
        [Synset('friend.n.01'), Synset('woman.n.01')]
        """
        r = list(self.wnrel(relation_symbol))
        if sort:
            r.sort()
        return r

    def wnrel(self, relation_symbol):
        """
        Get an iterator over the synsets related to 'self'.

        :param relation_symbol: the pointer symbol of a synset relation
        :type relation_symbol: str
        :return: an iterator over this synset's relation targets in random order.

        >>> ss = wn.synset('girlfriend.n.01')
        >>> print(sorted(ss.wnrel("@")))
        [Synset('friend.n.01'), Synset('woman.n.01')]
        """
        return (self._wordnet_corpus_reader.synset_from_pos_and_offset(pos, offset)
                for pos, offset in self._pointers[relation_symbol])

I favour returning unsorted results which calling programs can trivially sort, and documenting this in docstrings (and release notes and ChangeLog). Yes, some people will see different behaviour and might need to update their code, which has always happened from time to time with NLTK releases. I think that is preferable to proliferating the access methods.

Returning unsorted results for all wordnet relations is a big change, that causes many failures in test/wordnet.doctest. Moreover, the number of failures changes randomly between subsequent runs:
1248c1266
<   15 of 197 in wordnet.doctest
---
>   17 of 197 in wordnet.doctest
1250,1251c1268,1269
< 182 passed and 15 failed.
< ***Test Failed*** 15 failures.
---
> 180 passed and 17 failed.
> ***Test Failed*** 17 failures.

And it has also implications outside the wordnet module, with 4 doctests failing in nltk/util.py.
Many doctests can be fixed by wrapping the call with sorted(). But with tree() the changes are deeper in the output structure, and require the possibility of setting sort=True in the relation call.
I initially found it attractive to change the default setting, but am now leaning toward considering a smoother transition.
Another question is what do do with the second part of @bryant1410's proposal: should _related() return a list or an iterator?

The interface breaking update required for 3.9 was my opportunity to make @bryant1410's suggested breaking change. I went further to drop the sort flag. I haven't re-implemented _related() as an iterator (but can still consider this change)

@stevenbird, did you consider the code included here? It has the desired effect, by giving access to an optimized wnrel function, without breaking the default sort order? Changing the default has too profound consequences to be realistically able to deal with it.


[FIX] Bug #77: Invalidated parameter mapping after device transfer in KFAC

Fixes #77

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-7 of 25 (72.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 88.705%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

curvlinops/_base.py
0
2
0.0%

curvlinops/kfac.py
18
23
78.26%

Files with Coverage Reduction
New Missed Lines
%

curvlinops/_base.py
1
85.61%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
966

Relevant Lines:
1089

💛  - Coveralls

I agree it would be good to refactor this. I will look into using parameter names rather than .data_ptr()s as identifiers. If this refactoring is possible, we can remove the checks for outdated data_ptrs.


🤖 Add file patterns to config.json

⚠ This PR requires you to make a simple change before merging. ⚠

To save maintainers from having to manually specify the files key in their exercises' .meta/config.json files, we are providing support for track-level patterns. See this PR for details.
This PR adds (purposefully wrong) file patterns to the config.json file. It is up to you, the track maintainers, to change these patterns to their correct value.
You can use the following placeholders:

%{kebab_slug}: the kebab-case exercise slug (e.g. bit-manipulation)
%{snake_slug}: the snake_case exercise slug (e.g. bit_manipulation)
%{camel_slug}: the camelCase exercise slug (e.g. bitManipulation)
%{pascal_slug}: the PascalCase exercise slug (e.g. BitManipulation)

We will soon update configlet to enable it to automatically populate the .meta/config.json file's files property, at which point we will then batch-PR updates to all tracks that have merged this PR.
Tracking
https://github.com/exercism/v3-launch/issues/19

I've created a script that will automatically populate the files property based on the pattern specified in the config.json (which was added in this PR). If you'd like, I could run the script for your track, which would result in a PR that looks like this: https://github.com/exercism/csharp/pull/1507
In the future, we'll update configlet to include this functionality. For now, I can thus do this for you by running a script. Let me know if you'd like me to run the script for your track.

Please do. :rocket:


add component name filter to frontend

:+1:

Closed by https://github.com/aframevr/aframe-registry/pull/66


Error in open Google Drive Steam in Files

Explain the bug
Write a clear description of what the bug is.
When I press a folder in Google Drive that already sync on my device, the Files wasn't response and auto exit.
To reproduce

Go to 'Files'
Click on 'any folder in Google Drive partition'
See the error

Expected behavior
Write a clear description of what you expected.
I expect that Files will response which error was happened.
Logfile
Upload the log file here for us to understand your issue better.

You can access it from Settings->About->Open log location.
or
Copy the debug.log and debug_fulltrust.log from the following directory, and upload the files here.
%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState
debug_fulltrust.txt
debug.txt

Screenshots
Add screenshots to help explain your problem if needed.
System Information

OS Version: Windows 10 21H1 19043.928
App version: <IP_ADDRESS>

Additional comment
Add any other comment about the problem here. Does this problem happen again after restarting the app?

Thanks for this report. Please add Files version to the issue description and upload the log files.

Thanks for this report. Please add Files version to the issue description and upload the log files.

I have already added Files version and uploaded log files

Thanks I can confirm this issue is fixed in latest code


What should happen when the user clicks the "Share" link on the results page?

Currently, nothing happens. We should either remove it or implement some useful feature.

@talumbau, I am attempting to integrate https://github.com/carrot/share-button for the share button. Which sites do you want to integrate with? FB? Pinterest? Twitter? Email? G+ seems to require that the URL be whitelisted with Google API first. I'll have to check on that.

Actually, Google just don't like people sharing localhost URL with the world. Including FB, Twitter, G+, and email options. I will need the text for the subject line and the message body.


Updaing requirements.txt

Adding PyYAML to the requirements.txt and updating README.md
with instructions to perform a setup in a virtual environment.

Thanks, looks good


[INLONG-1915][Bug] tubemq master can not start

Fixes #1915

Codecov Report

Merging #1924 (b46d475) into master (92a9fca) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1924   +/-   ##
=========================================
  Coverage     12.27%   12.28%
- Complexity     1157     1158    +1
=========================================
  Files           413      413
  Lines         35225    35225
  Branches       5542     5542
=========================================
+ Hits           4325     4328    +3
+ Misses        30131    30127    -4
- Partials        769      770    +1

Impacted Files
Coverage Δ

.../inlong/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (-1.12%)
:arrow_down:

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
34.07% <0.00%> (-0.45%)
:arrow_down:

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.70% <0.00%> (+1.56%)
:arrow_up:

.../client/producer/qltystats/BrokerStatsItemSet.java
72.09% <0.00%> (+4.65%)
:arrow_up:

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 92a9fca...b46d475. Read the comment docs.


405 response does not return Allow header field.

RFC 7231 requires an allow header field to be returned with a 405 response. Currently, if hitting the endpoint with a GET request, a 405 response is returned with no Allow header field.

@apophisnow are you referring to a mattermost-plugin-jira endpoint, and if so which one?
Also, somewhat out of personal curiosity, was there a specific use-case that triggered this issue report?

We haven't received an update so we'll assume that the problem is fixed or is no longer valid.
If you still experience the same problem, try upgrading to the latest version.
If the issue persists, reopen this issue with the relevant information and we'd be glad to help you where we can.


Call from promise

Why I cannot call from AddPost
 created() {
  this.getData()
},
methods: {
  getData() {
    const posts = []
    postsCollection.get()
    .then(snapshot => {
      snapshot.forEach(doc => {
        let newpost = doc.data()
        newpost.id = doc.id
        posts.push(newpost)
      })
          this.$toast.show('Keeping it simple') //works

      this.posts = posts
    })
  },
  addpost() {
      postsCollection.add({
        text: this.newpost,
        completed: false,
        id: this.posts.length,
        createdAt: new Date()
      })
      .then(function(docRef) {
        console.log("Document written with ID: ", docRef.id);
          this.$toast.show('Keeping it simple')// doesn't work

      })
      .catch(function(error) {
        console.error("Error adding document: ", error);
      });
      this.newPost = '';
    }
  }

Its driving me crazy

@flakerimi did you check for what exactly is this ? are you in the nuxt context? what happens when you console.log(this.$toast)

Well its undefined
Error adding document:  TypeError: Cannot read property '$toast' of undefined


[Feature Request] Ability to set max-height of scrollview wrapper for customView

What I'd picture is something like:
MaterialDialog foo = new MaterialDialog.Builder()
  .customView(R.id.customViewResource, true)
  .maxCustomViewHeight(INT_OR_DOUBLE) // Double as percent of viewport (eg, 0.5), int as dp
  .show();

My scenario is I have a very tall custom view to create new users, and I'd like it to be sized so that when the keyboard shows, the whole dialog is still visible.
Another option would be something like an "alwaysFit" parameter, that resizes the dialog when the available space changes, or even a manual call to refit() or something.
Of course, the alwaysFit() scenario is more-or-less equivalent to calling
foo.getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_ADJUST_RESIZE);

after the fact.

The current behavior is how Android dialogs behave.
If you need a long form, e.g. for creating new users, you probably shouldn't be using a dialog; you should be using a simple Activity.

Fair enough.


group by having problem

select userid,count(1)c from test_tbl where type='a' group by userid having userid='user0001'
select * from (select userid,count(1)c from test_tbl where type='a' group by userid)t where userid='user0001'
The result is not the same? why?
env:16 node,2billion rows
version:crate-3.0.0-20180516

hi @cmdares,
thanks for reporting, we will look into that.
thanks,
joe

Is the result deterministically different?
CrateDB is eventually consistent, if you're inserting while you're executing the queries it could be that sometimes the query hit the replicas and sometimes primaries - that could explain a difference in the result.


DevOps architecture diagram

Describe the task
Create a detailed DevOps architecture diagram.
Acceptance Criteria

[ ] first
[ ] second
[ ] third

Additional context

Add any other context about the task here.
Or here

our "GGIRCS Deployments architecture diagram" could be expanded to reflect the CIF app and its dependencies

Audience: internal, and sharing with anyone interested by the technical side

The Miro board containing the previous diagrams can be found here: https://miro.com/app/board/o9J_kjtHnq8=/?share_link_id=933124605694

We have a miro board that we can use as a base for this

This is a beautiful diagram. I'd love someone to walk me through it.


: Adding normalization of the vector representation of CGPoint.

 : feature/test

          2 Messages

  :book:
  Executed 121 tests, with 0 failures (0 unexpected) in 1.013 (1.167) seconds

  :book:
  Executed 114 tests, with 0 failures (0 unexpected) in 1.006 (1.212) seconds

  Generated by :no_entry_sign: danger

Current coverage is 32.41% (diff: 100%)

Merging #279 into master will increase coverage by 0.09%

@@             master       #279   diff @@
==========================================
  Files            46         46
  Lines          2033       2036     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            657        660     +3
  Misses         1376       1376
  Partials          0          0

Powered by Codecov. Last update 8ada79a...6375ed8

Thanks 👍
Would you mind adding more tests, both to this and the distance one. Like maybe 5:12:13 and others.


Add new ga sources

Hey @ingalls
Can you explain a bit about the lineage of these cached files?  I'm noticing a lot of 0 character fields

These sources are derived directly from parcel data. Many of the parcel in georgia don't seem to have been assigned addresses resulting in null/0 fields.

I figured these fields were missing data.  But were the zeros introduced during your processing of the data?  I see 0's in fields for records containing partial addresses and null fields for records without any address data.  As you know, the two are not the same.  Just trying to make sure we're not adding data.

@geobrando The script I have does almost no processing on the actual data. Any 0 or 0 <Street> fields are exactly what the source data is returning.


d455 camera dropped while using，prompt no device connect

Required Info

Camera Model
d455

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
Linux tx2-nx 4.9.201-tegra

Platform
NVIDIA Jetson tx2

SDK Version
2.50.0

Language
python

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
I used an docker to build a container to use the camera, but the camera drops during use, and the camera device cannot be queried, but the host can recognize the device.

The situation is that it happens during the use process. It can be used normally in the docker at the beginning, and the disconnection occurs after a period of time.
Running the python program directly in the host computer will also cause the camera to drop. It can be used normally at first, but after a period of time, it will prompt "No device connected", reboot does not work, reinserting the type-c header does not work, only reinserting usb plug to continue normal use.

Hi @ssshello  It does not sound as though there is a problem with the camera hardware if it can run correctly for a period of time and can re-connect when reset with a USB unplug-replug when a connection drop occurs.
Does the camera's casing feel hot to the touch if you touch it a few minutes after you begin streaming from a cold start, please?

你好@ssshello 如果它可以正常运行一段时间并且在发生连接断开时使用USB拔出重新插入重置时可以重新连接，则听起来相机硬件没有问题。
如果您在从冷启动开始流式传输几分钟后触摸相机外壳，摸起来会不会感觉很热，好吗？

Hello, the camera feels a little hot to the touch after using it for a while, but is there a way to make the host re-read the camera device without re-inserting the usb? Is there any python code or shell script available? or something like that?

Hello, the camera feels a little hot to the touch after using it for a while, but is there a way to make the host re-read the camera device without re-inserting the usb? Is there any python code or shell script available? or something like that?

Hi @ssshello It does not sound as though there is a problem with the camera hardware if it can run correctly for a period of time and can re-connect when reset with a USB unplug-replug when a connection drop occurs.
Does the camera's casing feel hot to the touch if you touch it a few minutes after you begin streaming from a cold start, please?

Hello, the camera feels a little hot to the touch after using it for a while, but is there a way to make the host re-read the camera device without re-inserting the usb? Is there any python code or shell script available? or something like that?

If the camera is taking a while to heat up instead of within the first few minutes then it is likely not experiencing overheating (which can occur due to a bad USB cable, a glitch on the USB port or overheating of a single-board computer that the camera is attached to).
A camera can be reset without an unplug-replug using the SDK instruction hardware_reset().  A simple Python example of code to initiate this is below:
ctx = rs.context()
devices = ctx.query_devices()
for dev in devices:
dev.hardware_reset()

If a specific camera in a set of multiple cameras needs to be reset then https://github.com/IntelRealSense/librealsense/issues/5428 describes how to perform this in Python using a camera serial number.
Another way to reset is to use a Linux bash script to reset the entire USB port instead of just the camera, like the script at https://github.com/IntelRealSense/librealsense/issues/8393

If the camera is taking a while to heat up instead of within the first few minutes then it is likely not experiencing overheating (which can occur due to a bad USB cable, a glitch on the USB port or overheating of a single-board computer that the camera is attached to).
A camera can be reset without an unplug-replug using the SDK instruction hardware_reset(). A simple Python example of code to initiate this is below:
ctx = rs.context()
devices = ctx.query_devices()
for dev in devices:
dev.hardware_reset()

If a specific camera in a set of multiple cameras needs to be reset then #5428 describes how to perform this in Python using a camera serial number.
Another way to reset is to use a Linux bash script to reset the entire USB port instead of just the camera, like the script at #8393
hi,@MartyG-RealSense ,thanks for the reply
Usually the result returned by query_devices() when the camera is offline is an empty list so hardware_reset() cannot be used, and the bash script in the referenced link doesn't seem to work for my device because calling the lspci command can't find the usb controller, I tried Similar commands such as:
echo 2-2.3 > /sys/bus/usb/drivers/usb/unbind
echo 2-2.3 > /sys/bus/usb/drivers/usb/bind
But this method doesn't work
Use the command ls /sys/bus/usb/drivers/usb/ to see the device number that exists in usb3, such as 2-2.x(the serial number type of the usb3 device on the industrial computer I am using), but the lsusb command cannot query the device
The actual operation is to re-insert the camera so that lsusb can rediscover the camera. So I try to search for some bash command or code that can replace this operation.Because I think the camera is connected to the machine, but the machine does not re-read the camera device.

You mentioned in the above comment that you are using an industrial computer.  That could be significant information, as the SDK may sometimes experience issues on an industrial computer with a more exotic hardware / software configuration than a typical consumer PC.  In that situation, building the SDK with the RSUSB backend = true installation method can resolve problems.
This is because an RSUSB-based build of the SDK bypasses the Linux kernel.  It is therefore not dependent on Linux versions or kernel versions and does not require patching.
Instructions for installing the SDK from source code in RSUSB = true mode on Jetson can be found at https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-707501049

Hi @ssshello  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


TextField updates

Corrected prop multiline to textarea to match mdc classnames.
Added error message and deleting label value when trying to use with fullwidth text fields.
^ this logs the message 3 times in the sample project. maybe this logic shouldn't be in the materialDom function?

Added error message and deleting label value when trying to use with fullwidth text fields.
^ this logs the message 3 times in the sample project. maybe this logic shouldn't be in the materialDom function?

Not that big of an issue I'd say, it's just there for debugging purposes after all. But yeah, materialDom is rendered everytime props change, which might be a few times until the first render is complete. Might be possible to optimize performance though, haven't quite looked into that.

@mellogarrett @filoozom I'd like to remove any sort of errors and just do the console log and leave it as is

@prateekbh done. Let me know if that's what you had in mind


highlight code block problem

I've cloned the startbootstrap-clean-blog-jekyll repo. I wrote some markdown files at the _post , and  I found that the code block can't be highlighted. How can I solve?

I have the same issue, you can see an example of it here (scroll down to step 4).
I also included in `_config.yml' the following
highlighter: rouge

Any help would be greatly appreciated.
Great theme

I just started using Jekyll today and have been playing around with this template, so this probably a horribly hacky way to do it, but it seems to work.
Background
Somewhere in the Jekyll docs they mention that each theme is responsible for importing CSS that handles syntax highlighting.
If you look in the SCSS directory for this theme, you can see that it does not appear to do that:
https://github.com/BlackrockDigital/startbootstrap-clean-blog-jekyll/tree/master/assets/vendor/startbootstrap-clean-blog/scss
If we look in the default theme, minima, we can see that it does it in _syntax-highlighting.scss
Solution
1. Find this theme's location on your computer
First, find the gem directory for this theme on your computer by running bundle show jekyll-theme-clean-blog in the root of your blog directory.
For me on macOS using rbenv, it was /Users/<username>/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/jekyll-theme-clean-blog-<IP_ADDRESS>.
2. Import a syntax highlighting file
Now edit assets/vendor/startbootstrap-clean-blog/scss/clean-blog.scss in that directory. It'll look like this.
Add the following line to the end of clean-blog.scss:
@import "syntax-highlighting.scss"

3. Add the syntax highlighting file itself
Then copy the contents of the file _syntax-highlighting.scss from the minima repo into a file called _syntax-highlighting.scss in the same directory as clean-blog.scss, modified above.
Also, comment out the vertical-rhythm line in _syntax-highlighting.scss, like so:
  /* @extend %vertical-rhythm; */

4. Profit!
Syntax highlighting in posts like the following should now work:
{% highlight ruby %}
def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.
{% endhighlight %}

```ruby
def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.
```

Note: you'll probably need to restart the jekyll server before the changes will be recognized.
Next steps
If someone who is more familiar with Jekyll wants to make a PR for this change or describe a more idiomatic way to do it, that'd be much appreciated.

Any update on this issue? @clintgibler, it's a neat hack. Thank you for that. It has solved my issue for the time being but we still need a permanent fix.

@sahilpatel14 Unfortunately the author of this theme seems permanently AFK. Note the number of directly mergeable PRs that are still open (like this one).
I'd say patch your own locally, unless someone is willing to maintain and update a fork?

I have customised my blog with this theme and it looks dope. I don't want this awesome project to go dormant. Lets hope the author returns soon.

I had this problem. I think syntax highlighting was happening (I could see in Chrome that there were <span /> tags around keywords, etc. in my code, but there was no CSS for the styles to "see" the formatting.
My solution was to add a syntax.css into the style sheets that get pulled in.
As for a PR, I don't know how to proceed. I'm new to Jekyll and don't really understand well enough how Clean Blog's supposed to be forked to start one's own blog. When I tried it with GitHub pages I had trouble with missing files. Everything works locally (jekyll) but I don't want to commit some 1500+ files (esp. CSS in fontawesome) to a GitHub repo (which is what Git is saying is necessary.)

I had this too.
I solved using the way @fuhrmanator has mentioned.
You can choose any of syntax highlight css from predefined css or make your own.
Just add syntax.css file and include it in your head.html or other places. I will just work.

@sahilpatel14  Hi, do you face the problem that post date cannot be 2019? If I create a post dated in 2019, then the webpage does not show that post.


Doc - Conflict with zone.js should be more precise

Description
In the quick-start page (https://handsontable.github.io/angular-handsontable/quick-start), step 3 Import Handsontable before Zone.js should be more precise about the import order of the libraries.
My project does not use the angular-cli (but is built with webpack).
I have adapted my polyfills.ts as specified in step 3 but still have the famous "ZoneAwarePromise" problem.
The error still occurs because of the import order of the differents libraries. My main module (AppModule) was imported after zone.js. This module contains the import for "angular-handsontable" which import "handsontable".
Solution
The solution was to remove "zone.js" from polyfills.ts and to import it right after importing my AppModule.
My final code in main.ts looks like this :
// Main App module
import {AppModule} from './app.module';

// Polyfills
import './polyfills';
import 'zone.js/dist/zone.js';

// Bootstrap Angular
import {enableProdMode} from "@angular/core";
import {platformBrowserDynamic} from "@angular/platform-browser-dynamic";

if (production)
    enableProdMode();

platformBrowserDynamic().bootstrapModule(AppModule);

More details
The webpack configuration inside angular-cli (also in my config) bundle the whole 'polyfills.ts' file in a separate file. As zone.js is imported inside this file, it is still loaded before the main code and, therefore, before handsontable.
The solution proposed in the current document will bundle 'handsontable' inside the polyfills. While it is working, following the principle of polyfills (giving a browser methods it has not yet implemented), I think we should not import handsontable inside this file.
Also, explaining this problem in the documentation seems like a nice idea, isn't it ? ;-)
My 2 cents...

Hi @mselerin,
Thank you for your investigation.
We have to check why ZoneAwarePromise think that it is overwritten.
Step 3 in Quick start is a temporary workaround (I would like to remove this step in the stable version).
Are you using a ts-loader/js?

Hi,
I am using the @ngtools/webpack loader provided by Angular (just like the angular-cli).
Also, a small hint : when I enable "aot", the error is back ;-(
Ang btw, the ZoneAwarePromise just check if window.Promise is modified or not. I'll try to help and to figure out where the Promise function is overwritten...

Ok, we have to check it.
Thanks! I suppose, that could be related to handsontable.js.

I just had a look on the code and see nothing wrong inside Handsontable.
I see that Babel is used to build the distribuable version. I think that Babel include some sort of polyfills and could create their own version of Promise.
I am not a Babel expert so I can't be sure...

I was using a blank project created using angular cli.
The only change I had to make in the Quick start was in step 3 - import 'angular-handsontable'; instead of import 'handsontable';
import 'angular-handsontable';

/*********************************************************
* Zone JS is required by Angular itself.
*/
import 'zone.js/dist/zone';  // Included with Angular CLI.


restore: add an option to not keep restored files with errors

Output of restic version
restic 0.16.0 compiled with go1.20.6 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
Add an option to "restic restore" to avoid files with errors staying in destination directory.
I try to restore a snapshot of about 200Gb and there sis many errors like 'read blob <data/331832e5> from a4a4f68a: wrong data returned, hash is d46d67ab...", while "restic check" don' find any error.
For these files, after the restore, they are still there but with bad content.
If they can be automatically deleted, it is easy to identify them.
What are you trying to do? What problem would this solve?
I try to restore a (big) snapshot with thousand of files and many have the error mentioned.
Did restic help you today? Did it make you happy in any way?
I am very happy with restic, it is very helpful, the notion of snapshots, the deduplication by blocks,
the encrypting is very useful.
And such a tool with only one executable that don' need anything else is very convenient in
environments were you cannot install complex things: just download, make it executable and there you are!

You can use the repair snapshots command to get a list of damaged files (see https://restic.readthedocs.io/en/stable/077_troubleshooting.html ).


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 0.2.3
OS Version: Darwin x64 17.7.0
VS Code version: 1.66.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

@maacu6038  please close this yourself - this issue is not useful at all as it has no content about an actual issue, just the version numbers


Error: "Cannot read property 'forRoot' of undefined" after installing version 2.0.0-alpha.11-1

I uninstalled the older version<EMAIL_ADDRESS>as instructed on the release notes then installed the new one and it doesn't seem to load it since on @NgModule({imports: [ ... ]})
I switched back to 2.0.0-alpha.10 and it works fine.
Which versions of Angular, Material, OS, browsers are affected?
angular: 2.2.3,
material: 2.0.0-alpha.11-1,
windows 7

FWIW, I updated my Material<EMAIL_ADDRESS>to<EMAIL_ADDRESS>in package.json, rm -rf node_modules, npm install, and ran my application without any issues...on Linux.

Does someone have a deeper stack trace?

Nevermind, I've reproduced it on a fresh angular-cli project. For some reason my existing project didn't run into this...

I've tried with alpha.10, alpha11, alpha.11-1 and all of them if you do console.log(MaterialModule) it prints  undefined importing it with import { MaterialModule} from '@angular/material';
I got a repo here with a clean reproduction with angular cli https://github.com/Toxicable/materialtest

Uncaught TypeError: Cannot read property 'forRoot' of undefined
at app.module.ts:111
at Object. (app.module.ts:119)
at webpack_require (bootstrap 98affba…:52)
at Object. (rxjs-operators.ts:46)
at webpack_require (bootstrap 98affba…:52)
at Object. (src async:7)
at webpack_require (bootstrap 98affba…:52)
at Object. (zone.js:1613)
at webpack_require (bootstrap 98affba…:52)
at webpackJsonpCallback (bootstrap 98affba…:23)
at main.bundle.js:1

I've got a reproduction, trying to figure out why it's happening; AFAICT, MaterialModule is totally there.

Have a tentative fix on the @experimental label, validating it now. Would be awesome if someone else here also confirmed.

That appears to have done it on the @experimental

Okay, I've bumped @latest to 2.0.0-alpha.11-2 which should fix this.
For anyone wondering what was wrong:
alpha.11-1 added some re-exports to index.ts files for input, tabs, menu, and select using export * (to fix a bug with AoT). We haven't had any issues with export * before, but adding these seemed to break WebPack's module loading somehow (I have no idea why). I changed the exports to use specific symbols and everything was peachy.
I'll consult with @hansl (knows more about webpack than I do) tomorrow and figure out why this happened.

Confirmed, @jelbourn  -- my application works with 2.0.0-alpha.11-2. Thanks!


Reply to this email directly, view it on GitHub, or unsubscribe.


Which conditions lead to a natural "skip" event?

Hi, I have this question that can't figure out from the current documentation.
My app plays exactly two tracks, with IDs "1" and "2", each pointing to a radio stream that represents a station that "never ends".
  const tracks = [
    {
      id: "1",
      url: STREAM_URL_01,
      type: "default",
      title: "Station 01",
      artist: "Radio",
    },
    {
      id: "2",
      url: STREAM_URL_02,
      type: "default",
      title: "Station 02",
      artist: "Mixtape",
    },
  ];

So the way we switch from one "track" (station) to the other, is through a button, that changes the station ID, which maps to the corresponding track (1 or 2). This usually works fine.
However, in certain rare events, usually after a quick network flap, we see that a natural skip occurs, without the radio ID having changed in the app, and without the button having been pressed.
Question is: under which events the TrackPlayer would "naturally" try to skip a track? (for example, queue empty?) and would there be a way to disable this?
Thanks!

This is a queue, whenever a track finishes playing or an error occurs that makes that track impossible to play, the next one will start playing.
If you want to avoid changing from one station to another, you can add only one track to the queue, if you'd like to switch radios, you can remove the previous one and add the new one, there's no need to have both at the same time in the queue.

Thanks @Guichaguri , will split the queues then 👍


readme/manpage typo (%XDG_CONFIG_HOME%)

On Linux you put $ before a var, not surround it in % like on Windows.
Guessing it's a typo since the rest of the README gets this right.

Install

yt-dlp obeys the variable for both windows and Unix. Using % for some and $ for others in the readme is more confusiong imo

$ is already used in the rest of the README when giving instructions for Linux. If anything %XDG_CONFIG_HOME% is more confusing for Windows and Linux users. It's a Linux variable formatted like a Windows one as part of a Linux directory. Also on Linux, in any other scenario (other programs, terminal, shell scripts) the % wouldn't work and you'd use $XDG_CONFIG_HOME. $ is a universal Linux solution while % just happens to work in yt-dlp.

I don't think you understood what I meant. yt-dlp obeys XDG_CONFIG_HOME in all platforms. So whether it is documented as $XDG_CONFIG_HOME or %XDG_CONFIG_HOME%, it is wrong in some OS. Since all the other variables are documented with %, it doesn't make sense to change this one


Contact form not working and field titles centered

I noticed that the contact form on the index.html page is not working when submitted. When I click the "Submit" button, nothing happens. Additionally, I noticed that the titles of the form fields are aligned to the center, and I would like them to be aligned to the left for better readability. Please resolve this issue. To be looked into and investigated further. Aware that this is in fact two separate issues but the alignment of field titles seems small enough to squeeze in here.

i am intrested in doing this can i do this??

@seabeePraveen sure. let me know if you still interested.
to break it down this is more two issues with the same form. as the second part is really small and can be done while fixing the primary bug i have batched it together.
issue #1:

contact form can be filled but nothing happens when submitted.

Contact Form:
The contact form on the website is currently not functioning properly. It uses the emailjs library to send emails. The following steps need to be taken to fix the issue:

Obtain your User ID from the EmailJS dashboard [Service ID: service_vj4t28e]

Add the EmailJS library script tag to your HTML file.

Initialize the library in your JavaScript file using your User ID.

Update the form submission code to use the correct service and template IDs.

Add<EMAIL_ADDRESS>email address.

Add EmailJS Library to Your Project:

In your JavaScript file, initialize the EmailJS library your User ID:
emailjs.init('service_vj4t28e');

Yes, I am interested.
On Tue, 22 Aug 2023 at 8:49 PM, David Vermeulen @.***>
wrote:

@seabeePraveen https://github.com/seabeePraveen sure. let me know if
you still interested.
to break it down this is more two issues with the same form. as the second
part is really small and can be done while fixing the primary bug i have
batched it together.
issue #1
https://github.com/Dave-Vermeulen/Dave-Vermeulen.github.io/issues/1:

contact form can be filled but nothing happens when submitted.
Contact Form:
The contact form on the website is currently not functioning properly.
It uses the emailjs library to send emails. The following steps need to be
taken to fix the issue:
Obtain your User ID from the EmailJS dashboard [Service ID:
service_vj4t28e]
Add the EmailJS library script tag to your HTML file.
Initialize the library in your JavaScript file using your User ID.
Update the form submission code to use the correct service and
template IDs.
Add @.***" email address.
Add EmailJS Library to Your Project:

In your JavaScript file, initialize the EmailJS library your User ID:
emailjs.init('service_vj4t28e');
—
Reply to this email directly, view it on GitHub
https://github.com/Dave-Vermeulen/Dave-Vermeulen.github.io/issues/1#issuecomment-1688396967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVFU5TR7YDSHQPWXHO3KUDTXWTEXFANCNFSM6AAAAAAWUAO37A
.
You are receiving this because you were mentioned.Message ID:
@.***>

@seabeePraveen okay go ahead and attempt. submit PR for review when done. will assign this to you.


[BUG] FileSizeFilter make memory leak

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
when file size filter calc file size, serverRequest.bodyToMono(DataBuffer.class) .flatMap(size -> {}) make memory leak because of not close stream.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s):master

Debug logs
No response
Anything else?
No response

fix it，

i want to try to fix it, please asign to me.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping k8s.io/api a1613d7...cd271e7:
  > cd271e7 Update dependencies to v0.23.5 tag
  > a6b2207 Merge pull request # 108139 from liggitt/automated-cherry-pick-of-# 108138-upstream-release-1.23
  > 80b93d4 Revert v1beta1 PodDisruptionBudget select patchStrategy
bumping knative.dev/hack 14f832e...f067737:
  > f067737 Adding code of conduct to reference knative/community's CoC (# 162)
bumping k8s.io/apimachinery 276a8a7...276a8a7:
bumping k8s.io/code-generator fb849a7...fb849a7:
bumping k8s.io/client-go b425fb6...97582f2:
  > 97582f2 Update dependencies to v0.23.5 tag
bumping knative.dev/eventing 5df47e1...02663e2:
  > 02663e2 Update community files (# 6290)
  > 04eafff Process empty tracing config in test images (# 6289)
  > 3890b39 Wathola Tracing for upgrade tests (# 6219)
  > eb2bfff upgrade to latest dependencies (# 6288)
  > 7001b65 upgrade to latest dependencies (# 6286)
  > 4be06cd Feature/keep ports for service (# 6283)
  > 5081edd Drop sendevent tool since there is kn-plugin-event (# 6284)
  > a27ee9e Use env config for tests instead of hardcoded configs (# 6282)
  > 9b9cdee Adding code of conduct to reference knative/community's CoC (# 6281)
bumping knative.dev/pkg e6e3cf0...0a1ec2e:
  > 0a1ec2e upgrade to latest dependencies (# 2474)
  > 1f7514a bump k8s deps to v0.23.5 (# 2469)
  > 19a2589 fix coverage settings (# 2471)
  > 2daa86a Electors can provide an initial set of buckets (# 2473)

/lgtm
/approve

/lgtm
/approve


Standardize XML API

We're getting more and more attributes that should be stored (and usually exposed) on HTMLElement or HTMLDocument. It worries me a lot and I'd like to minimize the amount of common attribute space pollution caused by L20n.
My proposal is:
HTMLDocument.l10n.retranslate - a method that fires retranslation of the whole document
HTMLDocument.l10n.data - an attribute that exposes JSON structure with document context data
HTMLDocument.l10n.ctx - an attribute that exposes the L20n context used for document localization
HTMLElement.l10n.retranslate - a method that fires retranslation of the node
HTMLElement.l10n.data - an attribute that exposes JSON structure with the node context data (live object generated from l10n-args attribute)
HTMLElement.l10n.status - potentially an attribute that stores that localization status of the element
HTMLElement.l10nId - value of l10n-id attribute
HTMLElement.l10nArgs - value of l10n-args attribute
HTMLElement.l10nAttrs - value of l10n-attrs attribute
HTMLElement.l10nPath - value of l10n-path attribute
The major difference is that everything that is not set on the DOM via HTML code is being moved under "l10n" attribute in order to limit pollution.
Opinions?

Speaking as a JavaScript hacker…
I’d be perfectly fine with HTMLElement.dataset.l10n* until l20n becomes a standard, since we’ll have to use data-l10n-* attributes to keep our document HTML5-compliant. On the other hand, if you want an abstraction between HTMLElement.dataset.l10n* and HTMLElement.getAttribute("l10n-*"), HTMLElement.l10n[Id|Args|etc.] makes sense.
However, in order to limit the pollution as you say, why don’t we use a global “l10n” object instead of adding an “l10n” property to every HTML element?
l10n.translate(document, …)
l10n.translate(HTMLElement, …)
l10n.data(document, …)
l10n.data(HTMLElement, …)
l10n.status(HTMLElement, …)
l10n.ctx

(nit: why not “translate” instead of “retranslate”?)
It’d make more sense to me because when [re-]translate() is called on an HTML element, we want the element and all of its descendants to be translated — not only the element itself. Besides, there are other l10n functions that we want to expose (e.g. l10n.get).

Thinking of it a bit more…
I’d prefer using a global “l10n” object for a cross-browser JS implementation, but your proposal does make sense when thinking of l20n as a standard — e.g. HTMLElement.l10n.* would be comparable to HTMLElement.style.*.
In that case, I’d suggest to put everything under HTMLElement.l10n — e.g. HTMLElement.l10n.id, HTMLElement.l10n.attributes, etc.

The data-l10n-* and the current client-side library is just a temporary spin-off, I'd prefer not to make any design decision with a focus on the intermediate step instead of the ultimate schema.

"Besides, there are other l10n functions that we want to expose (e.g. l10n.get)."
No, that's very separate. We will not have l10n.get, we will have GlobalObject.getContext() and then everything will happen within the context.
And this is pure L20n API, what we are discussing here is L20n XML API, which is very different thing (it's like discussion between JS classes vs. DOM classes exposed in JS)

I’d suggest to put everything under HTMLElement.l10n — e.g. HTMLElement.l10n.id, HTMLElement.l10n.attributes, etc.

But then you'd still need an l10n-id (and company) or something like that as an attribute that can be defined in the HTML, no?  Like so:

But then you'd still need an l10n-id (and company) or something like that as an attribute that can be defined in the HTML, no?

Staś: you’re right, *.l10nId, *.l10nArgs and so on are more consistent with l10n-id or data-l10n-id attributes. The comparison with the “style” attribute / property is not relevant.

The data-l10n-* and the current client-side library is just a temporary spin-off, I'd prefer not to make any design decision with a focus on the intermediate step instead of the ultimate schema.

Gandalf: yeah, I think most webdevs prefer a global object (e.g. window.l10n) for a JS library, and properties/methods attached to HTML elements when it’s built-in.
I’m biased here because we need a JS library for Gaia. Thinking of your API as a future standard, your proposal makes more sense.

I’m biased here because we need a JS library for Gaia

Yeah, I hear you.
I'm pretty sure that for Gaia case we can provide a global object with ease if we'll decide to move away from what L20n API will look like (I'd prefer to keep it as close to the native impl. and the spec that we're going to propose as possible, but I understand your POV).
I'd love to hear Henri's take on this.

Staś: you’re right, *.l10nId, *.l10nArgs and so on are more consistent with l10n-id or data-l10n-id attributes. The comparison with the “style” attribute / property is not relevant.

I may be taking this overboard here, but what if we did follow the CSS way and introduced a meta/manifest format to be specified in head or linked to in a separate file, similar to how CSS rules are defined?  Then the only attribute to be defined on the node would be l10n-id.
HTML:
<link rel="l10n-manifest" href="/l10n.manifest" type="text/l10n-manifest">

Howdy

l10n.manifest (with a CSS-like syntax):
foo {
  attrs: -defaults, title;
}

As far as arguments go, they're not metadata so I don't think it would make sense to put them in the manifest.  They're supposed to allow the developer to overwrite context variables on the single node level.  However, I wonder if we can assume that the developer should instead:

either manipulate the node l10n data via the JS API, or
manipulate the data in the document context.

What is the use case for allowing to override the node data by typing/printing it in the HTML?

I may be taking this overboard here, but what if we did follow the CSS way and introduced a meta/manifest format to be
specified in head or linked to in a separate file, similar to how CSS rules are defined?

I think that it would significantly increase the complexity burden on the developer to make HTML file localizable. Please, remember that in 95% of cases l10n-id will be the only attribute needed anyway!

What is the use case for allowing to override the node data by typing/printing it in the HTML?

A list of users and their statuses (user X is connected in chat list UI) where l10n-args provide the gender of the user.

I think that it would significantly increase the complexity burden on the developer to make HTML file localizable. Please, remember that in 95% of cases l10n-id will be the only attribute needed anyway!

That's exactly why I suggested moving attrs to someplace hidden, like a manifest file.  You'll probably never need to use it anyways :) (assuming the HTML/XML bindings' defaults are good enough).  This way we'd avoid polluting HTMLElement with new attributes that are not l10n-namespaced, in exchange of a slightly (but possibly too much, I agree) more complex solution for the edge cases.

A list of users and their statuses (user X is connected in chat list UI) where l10n-args provide the gender of the user.

Hmm, wouldn't it be preferable to keep them in the document context anyways?

That's exactly why I suggested moving attrs to someplace hidden, like a manifest file. You'll probably never need to use it anyways :)

I think I don't like the idea of introducing the whole new format and piece of L20n XML chain instead of operating on well-known things like node attributes, just to "avoid polluting HTMLElement" in extreme cases.

Hmm, wouldn't it be preferable to keep them in the document context anyways?

No. If we have 100 users and one node per each () it would make sense to define the name/gender on the node as node args imo.

We're getting more and more attributes that should be stored (and usually exposed) on HTMLElement or HTMLDocument. It worries me a lot and I'd like to minimize the amount of common attribute space pollution caused by L20n.

I think namespace pollution isn't a problem if/when names begin with "l10n" anyway.

HTMLElement.l10n.retranslate

It seems to me that introducing an l10n object for each element might cause unnecessary overhead. However, I'm not an expert at how to optimize stuff like this. bz, sicking or smaug would probably be able to give better input about the complications caused by an extra object.
The namespace pollution problem would be equally solved by HTMLElement.l10nRetranslate.

Note: if “l10n-path” becomes a CSS selector, I’d much prefer to call it “l10n-select”.

Yes.

I'd prefer not to make any design decision with a focus on the intermediate step instead of the ultimate schema

To design the "ultimate schema" for something that gets exposed on Document and Element (we want to localize SVG text, too, right--not just HTMLElements), it would be good to ping the WHATWG list.


Not all post show up in archive?

So, I was trying out cactus-dark but there seem to be a strange problem that not all post show up in archive page, although if I use the url from generate log I can access the pages. How can I fix this?

Do only the X most recent posts show up? If so, see #16.
Otherwise, I need more information to address the problem. Have these posts specific front-matter? Is there a public repo for your blog or is it published somewhere?

thanks, now I see that pagination is not yet implemented so only 10 posts showed up. so disabling it seems to fix that.

hi, how to disable pagination?

@walkerwzy
per_page: 0