I can't open Go Live

Hi - i been using Live Server for over a month with no issues. This morning, i just received this message: "Error on port 5500. Please try to change the port through settings or report on GitHub."

Have to tried to change the port?

I should have mentioned, i'm new to vs code, & coding in general. I did go to vs code's "Settings" - "Live Server Config", but i don't know what to do.?

open user settings,
{
"liveServer.settings.port" : 0
}

(this setting will make the port random)

All Settings:
https://github.com/ritwickdey/vscode-live-server/blob/master/docs/settings.md

Now i get "Error on port 0. Please try to change the port through settings or report on GitHub."

Ok! I'm sorry for your issue! I need few more info!
Please remove the settings and restart vscode.. now try to open the live server with port 5500 (Default).
Even if it is showing error. Try to open the address on browser. "http://<IP_ADDRESS>:5500/" .. Let me know, is this working or not?

I actually reinstalled Live Server before i got your reply. It appears to be working. Now it's opening up at port 61220, by default. Does that sounds ok to you?

Ok! I've no problem if you're happy with random port.
if you don't want random port, then just remove the port setting.

Anyway, thanks for the report!
If you really like the extension, please drop a review in vscode marketplace.
https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer


⚠ Samsung has degraded performance

In ca34bd0, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2322 ms

Resolved: Samsung performance has improved in b892e71.


Use strnlen to upper-bound the length of the dataset name coming from the file

Pull Request
strnlen guarantees that a corrupted or maliciously crafted file doesn't cause the std::string to read past the end of the buffer looking for a \0 terminator.
Type of change
Hardening of the file/response parser.
How has this change been tested?
Existing tests.

Hi Felipe,
Thanks for bringing this shortcoming to our attention. This will be improved in an upcoming commit, but with std::find instead of strnlen which isn't portable.

Hi Felipe, Thanks for bringing this shortcoming to our attention. This will be improved in an upcoming commit, but with std::find instead of strnlen which isn't portable.

Cool!


Added from_textfile_batched() method.

Added a from_textfile_batched() method, which takes batchSize as a parameter, and emits the corresponding-sized chunks of text downstream.
This method is DaskStream compatible.
Added pertinent unit test as well.

I am ambivalent on this PR, since you could easily implement the same using from_textfile().partition. What is the justification for a new method, does it provide a significant performance boost?
To get tests to pass, I suspect it would be enough to merge from master and fix the conflict. If I don't hear otherwise, I'll close this in the near future.

(also, sorry that it's taken me so long to respond here)

The method would not only provide flexibility to tune the delimiter, batch size of data you want to read depending on the type/volume/message size/speed of data. Also, I had experimented with the partition approach, but my method performed better in streaming use cases.

from_textfile does already allow you to specity the delimiter https://streamz.readthedocs.io/en/latest/api.html#streamz.from_textfile

batch size of data

.partition() would allow you to do exactly this, no? You mean you want to batch by number of bytes? I don't think that's what your code does.

my method performed better

Would love to see some numbers here. I suspect that when the CPU load per message processing is significant, you would see no difference from this first stage.

So, this still holds true: [https://github.com/python-streamz/streamz/issues/235].
If I remember correctly, I was able to get around 6 MBps when I used .partition() instead. The speedup in using from_textfile_batched() would come from the fact that if the batch size is large enough, the buffering happens while emitting elements downstream at the start of the streaming pipeline, as opposed to calling self._emit() for each element and then buffering using .partition().
Let me know what you think of this.

I suspect that when the CPU load per message processing is significant, you would see no difference from this first stage.

This may be true, but the speedup would still be significant if the batch sizes are large, IMO.

Compared to 10-12MBps, right? What size were the lines here? I am still tempted to say that it's not worth complicating the API. Perhaps you can think of a way to add batchsize= into the existing from_textfiles.

What size were the lines here?

1.1 kB

I am still tempted to say that it's not worth complicating the API.

Okay.


WIP: Simplify export blueprint modal dialog

Closing because I renamed my fork and now it does not update automatically.


Define HAVE_* for public libyara headers

Public yara headers use several HAVE_* macros (HAVE_STDBOOL_H, HAVE_CLOCK_GETTIME, and others).
While building yara itself, they are defined on command-line using -D switches,
so everything works fine.
However, when building 3rd-party code against libyara, they are not defined anywhere,
which results in different set of declaration in yara headers.
For example, HAVE_CLOCK_GETTIME is defined during yara build itself, so YR_STOPWATCH gets struct timespec,
but when compiling against libyara HAVE_CLOCK_GETTIME is not defined, so YR_STOPWATCH gets struct timeval instead.
I think -DHAVE_* defines used for building yara itself need to be made available in public headers -- either through shipping of config.h (and unconfig.h not to bleed into 3rd-party code) or through pkg-config file (would be nice to rename the macros to YR_HAVE_* not to interfere with similar-named 3rd-party HAVE_* macros).
I see that there were some issues with config.h in the past (#165, #541), but from a quick glance none of them seem unsolvable.
Also, regarding YR_STOPWATCH, can it be simply turned into an opaque structure (and only used by pointer), so that public API doesn't care about its size?

If you are familiar with how to do this using pkg-config your contributions are welcomed. In the past we used a config.h file, but I'm not sure that's the best solution for this problem. The config.h file is generated by the ./configure script, gathering information from your own system, and is not supposed to be distributed.
I'm investigating how to do this with pkg-config, but haven't found anything so far.

If you are familiar with how to do this using pkg-config your contributions are welcomed.

Basically, I was thinking of adding required macros (determined at configure time), like -DYR_HAVE_STDBOOL_H -DYR_HAVE_CLOCK_GETTIME to Cflags field in yara pkg-config file.
(macros are prefixed with YR_ since they are a part of public interface and so that they don't conflict with 3rd-party own macros of similar name)

The config.h file is generated by the ./configure script, gathering information from your own system, and is not supposed to be distributed.

It shouldn't be distributed as part of source package.
But it affects libyara ABI, so it's a part of public interface of libyara library, and thus needs to be distributed within yara devel binary package (RPM/deb).
pkg-config file doesn't actually differ much from config.h -- both are generated at compile time, both carry the required macros, both are shipped within a binary package.
For example, glib does a similar thing by placing generated config.h under /usr/lib64/glib-2.0/include/glibconfig.h. (yes, /usr/lib64, not /usr/include, because it differs to different ABIs (like x86 vs x86_64)).
(for Ubuntu/Debian, the path is /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h)
Ideally, yara public ABI just shouldn't depend on availability of clock_gettime or something else, and use opaque YR_STOPWATCH, for example, or a platform-independent wrapper around timespec/timeval, which can fit any of those.

I completely agree. But haven't found any reference on how to autogenerate the pkg-config file with the required macros. I'm not very familiar with pkg-config nor binary package generation, this part was contributed by someone else. That's why I'm calling for someone with more experience than me in this area.
Regarding the YR_STOPWATCH issue, I think this should solve the problem: https://github.com/VirusTotal/yara/pull/1125
With that change you can build your program with the YARA header files no matter if the library was built with HAVE_CLOCK_GETTIME or not.

Oh, I see.

Regarding the YR_STOPWATCH issue, I think this should solve the problem: #1125

Oh, that's great, thank you!
Out of all HAVE_* macros used in libyara headers, YR_STOPWATCH struct size was the most risky one.


Controll Hub Downgrade

Issue for pinning the project to 8.2.0
Just opening an issue here, thought it would be a good way to organize ideas.
My initial thoughts where, after @blarghmatey changed the dependencies,
dependencies {
    implementation 'org.firstinspires.ftc:Inspection:8.2.0'
    implementation 'org.firstinspires.ftc:Blocks:8.2.0'
    implementation 'org.firstinspires.ftc:RobotCore:8.2.0'
    implementation 'org.firstinspires.ftc:RobotServer:8.2.0'
    implementation 'org.firstinspires.ftc:OnBotJava:8.2.0'
    implementation 'org.firstinspires.ftc:Hardware:8.2.0'
    implementation 'org.firstinspires.ftc:FtcCommon:8.2.0'
    implementation 'org.firstinspires.ftc:Vision:8.2.0'
    implementation 'androidx.appcompat:appcompat:1.2.0'
}

To then change the version of the Android Gradle plugin from (7.2.0) to (4.1.3) thinking that when downgrading the andoird version you'd need to use an older version of the Android Gradle plugin.
classpath 'com.android.tools.build:gradle:4.1.3'

In addition I tried to change the minSdkVersion, targetSdkVersion and compileSdkVersion in build.gradel(FTC_Robot_controller) and set it to 27, this means we'd be building for Android 8.1+ (API level 27), which is the closest match to Android 8.2.0 I could find.

android {
    defaultConfig {
        minSdkVersion 27  // For Android 8.1+ (API level 27)
        targetSdkVersion 27  // Targeting Android 8.1 (API level 27)
        buildConfigField "String", "APP_BUILD_TIME", '"' + (new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSSZ", Locale.ROOT).format(new Date())) + '"'
    }

    compileSdkVersion 27  // Compile against Android 8.1 (API level 27)

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    namespace = 'com.qualcomm.ftcrobotcontroller'
}

--ALSO --
I ran into another major issue (maybe) when trying to use an older version of the android gradle plugin, it looks like I'm not able to use Java 12, and instead I need to use Java 8?
> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 66

So I'm pretty unsure as to how to deal with this, I'm not sure If changing the Android Gradle plugin is the best approach here, but I think if it is there might be some more major issues that might come up.
Asking for assistance here, wondering if someone could run this on their machine?

 Get bot software back to working state for Fall Fest

So this confirms what I was noticing before, to downgrade to the last supported version of Android on our controller, we would need to downgrade our entire codebase to Java 8-11, currently, we're using Java 17.

Is that hard to do?
On Sun, Sep 22, 2024 at 18:50 Torin Etheridge @.***>
wrote:

So this confirms what I was noticing before, to downgrade to the last
supported version of Android on our controller, we would need to
downgrade our entire codebase to Java 8-11, currently, we're using Java
17.
Screenshot.2024-09-22.at.6.48.33.PM.png (view on web)
https://github.com/user-attachments/assets/a74a6881-cbde-4ec5-af43-7a5bc9dcb50b
—
Reply to this email directly, view it on GitHub
https://github.com/CapitalRobotics/Janxs_Brain/issues/3#issuecomment-2367000978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DXPAIIXSR7ZLJTYEFBNI3ZX5CR5AVCNFSM6AAAAABOTBJW36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRXGAYDAOJXHA
.
You are receiving this because you were assigned.Message ID:
@.***>

I don't think so, but since we're using Java 17 we'd lose access to all the Java 17-specific features and libraries (idk if we're using any now) and it might make future development harder, I think you wouldn't be able to use sealed classes, pattern matching for instanceof, records, text blocks (multi-line strings) switch expressions, and the NullPointerException messages. probably missing some other ones. So idk if there's another way to do this, but I think this is kinda a big problem if we don't get the driver hub soon.

Currently we arent using it now, and its not supposed to be a long term
solution I’d imagine, its for the fall fest mostly right?
On Sun, Sep 22, 2024 at 19:05 Torin Etheridge @.***>
wrote:

I don't think so, but since we're using Java 17 we'd lose access to all
the Java 17-specific features and libraries (idk if we're using any now)
and it might make future development harder, I think you wouldn't be able
to use sealed classes, pattern matching for instanceof, records, text
blocks (multi-line strings) switch expressions, and the
NullPointerException messages. probably missing some other ones. So idk
if there's another way to do this, but I think this is kinda a big problem
if we don't get the driver hub soon.
—
Reply to this email directly, view it on GitHub
https://github.com/CapitalRobotics/Janxs_Brain/issues/3#issuecomment-2367005307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5DXPANB5QLWGYNSWME5HELZX5EMXAVCNFSM6AAAAABOTBJW36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRXGAYDKMZQG4
.
You are receiving this because you were assigned.Message ID:
@.***>


pp-7475 add dependabot config

WHAT
Added a dependabot configuration

I'm a bit hesitant about adding Dependabot for this lambda - it's currently manually deployed but not visible on Control Plane. If we end up merging a whole bunch of Dependabot PRs and forget to deploy them, then we're likely to see a significant drift between what's on master here and what's actually running, which could cause confusion down the line.

Righto, will close.


add persistence example

@ibgreen @philogb
Hey guys, here's a persistence example. The screenshot doesn't really do it justice; it's much better in motion. Enjoy! :tada:

Very neat!


Outlier detection cannot eject unhealthy hosts

I used the httpbin docker image to test the health check and outlier detection feature of envoy in a k8s cluster:
...
      clusters:
      - name: httpbin
        outlier_detection:
          consecutive_5xx: 3
          interval: 1s
          base_ejection_time: 60s
          max_ejection_percent: 100   # eject all hosts
...

I expected the host to be ejected after I pass 3 consecutive /status/500 requests to it:
curl http://$envoyUrl/httpbin/status/500

HTTP/1.1 500 Internal Server Error
server: envoy
date: Tue, 14 Apr 2020 09:48:20 GMT
content-type: text/html; charset=utf-8
access-control-allow-origin: *
access-control-allow-credentials: true
content-length: 0
x-envoy-upstream-service-time: 0

I also checked the cluster statistics using admin API:
...
httpbin::<IP_ADDRESS>:80::health_flags::/failed_outlier_check
...

But when I pass a status/200/ request to it, it returned HTTP 200:
curl http://$envoyUrl/httpbin/status/200

HTTP/1.1 200 OK
server: envoy
date: Tue, 14 Apr 2020 09:48:25 GMT
content-type: text/html; charset=utf-8
access-control-allow-origin: *
access-control-allow-credentials: true
content-length: 0
x-envoy-upstream-service-time: 1

I also tried for 2 httpbin pods and over 10 consecutive 500 requests, but the hosts did not get ejected.

@snowp do you know if this is working as intended?

Do you happen to be using a stats filter? There's a known issue with outlier detection and not having the requisite stats available: https://github.com/envoyproxy/envoy/issues/8259

Also IIRC there is a min host requirement/config for outlier detection. I would look at that.

@snowp I didn't use any stats filter

Late note:  #11629 is the fix


Added EventBridgePutEventsPolicy template

Issue #, if available: N/A
Description of changes: Adds a dedicated template policy for EventBridge granting the permissions to publish events to EventBus either custom ones or partner events.
Description of how you validated changes: Unit tests for transformed had been added to validate that the additional policy had been output.
Checklist:

[X] Write/update tests
[X] make pr passes
[ ] Update documentation
[X] Verify transformed template deploys and application functions as expected
[X] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I had updated the pull request. Changes made added EventBus name as parameter and I removed the policy on PutPartnerEvents.

Codecov Report

Merging #1409 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1409   +/-   ##
========================================
  Coverage    94.37%   94.37%
========================================
  Files           78       78
  Lines         4678     4678
  Branches       934      934
========================================
  Hits          4415     4415
  Misses         121      121
  Partials       142      142

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 f8e0505...5e11259. Read the comment docs.


fix: aztec node to save outbox adddress to config

Without this talking to outbox address fails in the sandbox

Benchmark results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 43422805 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,912
868,112
3,449,624

l1_rollup_execution_gas
841,999
3,595,220
22,204,993

l2_block_processing_time_in_ms
1,009 (-1%)
3,868 (-2%)
15,249 (-2%)

note_successful_decrypting_time_in_ms
320
976 (-2%)
3,595 (-2%)

note_trial_decrypting_time_in_ms
24.0 (+9%)
:warning: 85.0 (-25%)
136 (-1%)

l2_block_building_time_in_ms
8,854 (-1%)
35,539 (-1%)
148,019 (-1%)

l2_block_rollup_simulation_time_in_ms
6,569 (-1%)
26,406 (-1%)
104,497 (-1%)

l2_block_public_tx_process_time_in_ms
2,243 (-1%)
9,009 (-1%)
43,066 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,474 (+4%)
31,432 (+3%)

note_history_successful_decrypting_time_in_ms
2,384 (+5%)
4,831 (+4%)

note_history_trial_decrypting_time_in_ms
122 (-1%)
147 (-1%)

node_database_size_in_bytes
1,649,440
1,192,123

pxe_database_size_in_bytes
27,188
54,187

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
43.1 (-1%)
56,577
14,745

private-kernel-ordering
21.3
20,137
8,089

base-rollup
850
631,605
811

root-rollup
37.9
4,072
1,097

private-kernel-inner
35.8 (-1%)
72,288
14,745

public-kernel-private-input
46.8
37,359
14,745

public-kernel-non-first-iteration
27.7
37,401
14,745

merge-rollup
0.855 (-2%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,723
27,094


[BrightcoveNew] Fix: find videos embedded in xilinx.com site

In xilinx.com sites there are no video tags, the video_id can be found in a div tag.
(the brightcove script is before the div (video-id) tag.)
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
The xilinx.com site uses embedded brightcove videos, but there is no html video tag, so the original BrightcoveNewIE could not determine the video_id.
These sites uses a script tag (similar to what the original code search for), and after that there is a div tag, where the data-video-id (video_id) can be found.
Example sites:
https://www.xilinx.com/video/soc/how-to-use-the-zynq-7000-verification-ip-verify-debug-simulation.html
https://www.xilinx.com/video/hardware/model-composer-product-overview.html

This is not a generic embed thus should go into separate extractor.
Core tests are broken.

Should I use this branch, or create a new one (called xilinx) and delete this branch / pull request?

Up to you.

Done.


Remove rails as a dependency

By depending directly on Rails, clearance becomes a source of dependency
inflation - pulling in every Rails framework into any app that uses clearance,
even when they were not needed.
This change updates the dependencies to just those which clearance actually
needs to run.
Inspired by priors - https://github.com/thoughtbot/clearance/pull/776 and https://github.com/thoughtbot/clearance/pull/763 - and updated against more recent changes.

🆒

Hi @mjankowski! Are there any plans to build a new release with this change?
I see the work on 2.0 is underway, any chance of rolling out 1.6.2 before that? This shouldn't affect backwards compatibility, right?

In theory the removal of the rails requirement should just be a silent change that doesn't impact anything ... I guess there could be someone who was unknowingly relying on clearance to pull in part of rails for them or something?
Either way - thanks for reminder. Yes, I'd like to do a release soon which gets out at least the stuff in master since last release, if not a full 2.0 rc release. Will review soon.


General Housekeeping

This PR includes a handful of general housekeeping things that were annoying me.
There are a few things changed:

kernel sources are moved into a kernel directory. Scripts are moved into a script directory.
The Makefile is parameterized and updated to be easier to maintain.
Separate userland programs are segregated by directory.
The README has been updated with some build/run instructions, including a reference about how to setup the cross compiler.

Please note that the script script/MKDISK.sh and the build rule for george.disk have not been updated or confirmed to still work. These unfortunately include hard-coded paths, which ideally should be fixed.
For now, userland programs only depend on a file main.c. I defered supporting other file names until a more general solution for loading userland programs is proposed. It would however be easy to substitute the current rules for recursive make rules.
Finally, I considered updating the Makefile to use gcc invocations instead of direct as invocations, but decided not to. Note that the invocations of the assembler do not include debug symbols.

LGTM


Question on \Slim\Router->finalize()

Why Slim needs to call all Routes->finalize() via \Slim\Router->finalize()?
I tried to look for a reason but I did not find.
My question is because I'm trying to work around this issue:
https://github.com/slimphp/Slim/issues/1604
Why not 'finalize' only the dispatched Route?

I think this is a fair assessment. I don't see why we have to finalize all routes instead of the one matching route. However, I don't think this is paramount for the 3.0.0 RTM release. Will move to the 3.1.0 milestone.

There are some edge cases such as sub requests, etc. We'd want to save the "finalized" state as a member variable in each route instance, and then finalize routes lazily on invocation. But a problem to be addressed later in 3.1.0 for sure.

I thought about sub requests and I moved the finalized state to Route class on my "fix" for Lazy resolving of route middlewares:
https://github.com/mathmarques/Slim/commit/99a85f9f1fbabfde730e160898da0024e56c7bb3
@codeguy Is it too early for create a PR for change this finalize behavior? :)

Not too early. Just be prepared to potentially rebase your PR in the future.

If this is running successfully, we may as well just merge this into RC3 /cc @akrabat

@codeguy can we get this tested on an app that makes heavy use of middleware's first, both Route and App level middleware.

@silentworks For sure.

I just need to work on removing the \Slim\Router->finalize() (A lot os unit tests use this function and I just remove the content of this function)
I'll make the changes here and open a PR.

Fixed by #1632.


How do you specify vCard data?

I'm trying to set the vCard. I've tried sending JSON and XML, but in either case the server registers the vCard as blank.
http://xmpp.org/extensions/xep-0054.html
var vcard={      "FN": "Peter Saint-Andre",
    "N": {
        "FAMILY": "Saint-Andre",
        "GIVEN": "Peter"
    },
    "NICKNAME": "stpeter",
    "URL": "http://www.xmpp.org/xsf/people/stpeter.shtml",
    "BDAY": "1966-08-06",
    "ORG": { "ORGNAME": "XMPP Standards Foundation" },
    "TITLE": "Executive Director",
    "ROLE": "Patron Saint",
    "TEL": [
        { "NUMBER": "303-308-3282" },
        { "NUMBER": "303-555-1212" },
    ],
    "ADR": [
        {
            "EXTADD": "Suite 600",
            "STREET": "1899 Wynkoop Street",
            "LOCALITY": "Denver",
            "REGION": "CO",
            "PCODE": "80202",
            "CTRY": "USA"
        },
        {
            "LOCALITY": "Denver",
            "REGION": "CO",
            "PCODE": "80209",
            "CTRY": "USA"
        }
    ],
    "EMAIL": { "USERID"<EMAIL_ADDRESS>},
    "JABBERID"<EMAIL_ADDRESS>    "DESC": "Check out my blog at https://stpeter.im/"};

    client.publishVCard(vcard, function (result) {
                        console.log(result);
                        client.disconnect();
                    });

What am I doing wrong? Thanks for any pointers.

I've inspected the XML I need to create
<iq xmlns='jabber:client' type='set' id='purpled80a9c1a'>
	<vCard xmlns='vcard-temp' prodid='-//HandGen//NONSGML vGen v1.0//EN' version='2.0'>
		<EMAIL>
<EMAIL_ADDRESS>		</EMAIL>
	</vCard>
</iq>

I'm just not getting it right, though. Everything I do wipes out the vCard.

check this
<EMAIL_ADDRESS>but you have
<EMAIL_ADDRESS>also on the xep site it says
"Currently there is no method for partial updates of a vCard, and the entire vCard must be sent to the server in order to update any part of the vCard."

See https://github.com/otalk/stanza.io/blob/master/lib/stanza/vcard.js for the mapping.
For Peter's example from XEP-0054, you would use:
client.publishVCard({
    fullName: 'Peter Saint-Andre',
    name: {
        family: 'Saint-Andre',
        given: 'Peter'
    },
    nicknames: [ 'stpeter' ],
    website: 'http://www.xmpp.org/xsf/people/stpeter.shtml',
    birthday: '1966-08-06',
    title: 'Executive Director',
    role: 'Patron Saint',
    organization: {
        name: 'XMPP Standards Foundation'
    },
    emails: [
        { email<EMAIL_ADDRESS>preferred: true }
    ],
    phoneNumbers: [
        { number: '303-308-3282', work: true }
    ],
    addresses: [
        {
            work: true,
            street: '1899 Wynkoop Street',
            street2: 'Suite 600',
            city: 'Denver',
            region: 'CO',
            postalCode: '80202',
            country: 'USA'
        },
        {
            home: true,
            city: 'Denver',
            region: 'CO',
            postalCode: '80209',
            country: 'USA'
        }
    ],
    jids: [<EMAIL_ADDRESS>],
    description: 'Check out my blog at https://stpeter.im/'
}, cb);

@triniwiz  Thanks - same problem. In my example, I am trying to follow the XML format  that Adium produces, which successfully registers a vCard against my server.

@legastero wow, thanks for putting that together.


Consider downtargeting SourceLink.Create.CommandLine to .NET 4.6

It would be super awesome if it was possible to change the SourceLink.Create.CommandLine NuGet package to target .NET Framework 4.6 (instead of 4.6.1). This would enable codebases such as MSBuild that still target 4.6 to leverage SourceLink v2.
Thanks!

Ugh, never mind, it was a NuGet bug :(

Glad you got it working. What NuGet bug?

https://github.com/NuGet/Home/issues/2865. Wasn't your fault at all.


Instance Page Improvement

refers to #627
As a console user, I want to access and view the instance settings on a single page.
Acceptance Criteria

[ ] remove primary navigation (Organizations, Views, Failed Events, Settings, Customer Portal link)

[ ] use /instance as single site with our basic overview, organizations, and sidenavigation where settings are shown

[ ] Failed events and views are displayed as seperate sidemenu items

[ ] rename instance button to settings

Benefits with the simplifications are the following:

As instance settings are the fallback for all org settings we could hide irrelevant UI from the user, (b2c or single org) -> hide org settings, but show the navigation with multiple organizations.
The above point ensures that instance settings are percieved as the main settings of the instance and reduces complexity.

Do I understand it correct that the part where I am on an organization stays as it is.
The only thing thant changes is renaming of the button instance to settings and that we have it as a sidenav instead of top menu?

yes the org part does not change and theres a single page for all instance settings

I do have some open questions regarding this.

If we rename the Instance button to settings, we do have twice settings when the user is on an organization, Once for the organization in the nav and one in the top. Maybe name it default settings?
Do I understand it correctly that we would just take the settings page we currently have and add the points we have in the main nac Instance, Organizations, Events, etc to the sidenav.

@peintnermax did you discuss this with @juergrinaldi ? If not can you do it, so we are sure this makes sense from a ux perspective and we don't miss something?


Hi Vincent! Is there any way I can train a language model on my dataset using Nabu for rescoring the outputs? Please reply.

Hi Vincent! Is there any way I can train a language model on my dataset using Nabu for rescoring the outputs? Please reply.


td-agent v4.3.2

Release v4.3.2 - 2022/06/28
News
This release is mainly for supporting new distributions released in FY22Q2.
We choose Ruby 3.1 to bundle for such new distributions to adopt to recent
environment such as OpenSSL 3.0. For other distributions, we still use
Ruby 2.7. We'll migrate to Ruby 3 completely after Ruby 3.2 is released.

Support new distributions

Red Hat Enterprise Linux 9
Ubuntu 22.04 LTS (Jammy Jellyfish)

Remove nokogiri from Linux and macOS packages

It's not used in actual by default on such environments.
Fix #400

Update yajl-ruby to v1.4.3 to address vulnerability

Fix #397

Update OpenSSL to 1.1.1p (for macOS and Windows)

Is nokogiri really removed from Linux and macOS packages? I cannot find a change regarding nokogiri in your commit. I still can see nokogiri as a dependency.

It was a separated pull request and already merged into master branch: #389
Please note that we'll check really built package from now.

I confirmed that nokogiri is no longer included in built Linux packages.


Customized "message"

Cool package!
I believe you should allow more customization of the "message". For example, I would love the "message" to be centered.  An option of "message" of type "Widget" alongside the option of type "String" can be handy.
Thanks

Thank you for your suggestion!


[Bug]: Replace Tokens in HTML module settings gets Unchecked after upgrade

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
During a test upgrade from DNN 9.10.02 to 9.13.00 any module that had Replace Tokens enabled (check marked) in the HTML Module Settings was changed to disabled (or no longer check marked) after the upgrade. This occurred in every html module across every portal in the DNN installation that had the Replace Tokens enabled under HTML Module Settings. Which caused the token to display on the website since it was no longer parsed.
Steps to reproduce?
Have a html module using a token before upgrade with Replace Tokens enabled (check marked) in the HTML Module Settings. Upgrade to 9.13.00 and the Replace Tokens box is unchecked.
Current Behavior
No response
Expected Behavior
No response
Relevant log output
No response
Anything else?
No response
Affected Versions
9.13.0 (latest release)
What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Additional information...
Looks to have something to do with clearing the cache.
If you have a module with Replace Tokens enabled (check marked) in the HTML Module Settings and it is correctly parsing the tokens, then you go to Servers and hit the Clear Cache button, it actually removes the checkmark from Replace Tokens in the HTML Module Settings and then the tokens are no longer parsed in the html content.

Maybe this is caused by https://github.com/dnnsoftware/Dnn.Platform/pull/5742?
I'm not experienced with the caching of modules, so this is just a guess: the cache key is now set to the portal ID. Doesn't this mean 2 modules can get the same cache (since they are both in the same portal)?

@valadas That makes sense to me, that the change introduced cache conflicts between modules in the same portal. I think the right approach is to include both the portal ID and tab module ID in the cache key, and then clear anything with the portal ID prefix whenever there's a change. Does that sound like it would work better? Are we missing something that is preventing conflicts?

@bdukes did you intend to ping me about this or someone else ?

Sorry, wasn't clear about that. I did intend to ping you b/c #5742 was your PR.

Ok, good point, let me put my thinking hat here...

@bdukes I think your suggestion makes sense. We also have hostGuid and portalGuid we could leverage potentially... Unfortunately we don't have guids on the lower levels for modules and tabModules... But yeah, I feel like we probably need a compount cache-key here is some fashion.

@bdukes thanks for helping with this bug. Is there a patch that I can apply now, or do I just wait until 9.13.01 comes out? This bug is a pretty big hindrance to upgrading to 9.13.00. Thanks

Well if you just want to test it out you can download a "nightly build" from here: https://dev.azure.com/dotnet/DNN/_build/results?buildId=99491&view=artifacts&pathAsName=false&type=publishedArtifacts
However this is not an official release yet, so for production use I would wait on 9.13.1, which I believe could be done quickly...

@valadas ok thanks for the info, I'll wait for the official 9.13.1. Thanks for your contributions to the platform!


Black screen when i launch virtual machine with Windows 98 SE in VMWare Workstation 17.0.2 build-21581411

After updating SoftGPU to the latest version v0.4.2023.19-alpha, my Win 98 SE VM stopped booting. The Win 98 logo appears and then I only see a black screen and nothing happens. I have a virtual machine on VMWare Workstation 17.0.2 build-21581411, before the SoftGPU update the virtual machine was working. Has this happened to anyone else?

Hello,
This could happen if you enabled SIMD95 in SoftGPU installation on VMware (or it is accidently or by bug). Try to edit autoexec.bat (from safe mode – hold CTRL during boot or boot from recovery floppy:[^1] edit C:\autoexec.bat). If there is line "C:\simd95.com", delete it.
Otherwise, I don’ know where the problem could be :-(
[^1]: you can you use patcher9x boot floppy  as well


[Proposal] Migration plan for Guice 7+

Wanted to make an issue for tracking migration to Guice 7.0.0.
@ThePumpingLemma migrated to using Guice 6.0.0 (#2846), however, there remains issues with projects wanting to use misk-inject with Guice 7+. The largest issue is that when a project tries to use Guice 7+, it can not inject classes that are labelled with javax.inject.XXX annotations. Guice 6+ happily accepts both jakarta and javax.
Proposed path forwards
It seems like the path to migration would be twp steps:

Replace all usages of javax.inject.XXX with com.google.inject.XXX

This enables projects to transition to using jakarta.inject in their own projects, while consuming misk-inject @ 6.0.0

Eventually cut over to Guice 7.0.0 at some point
Optional: Replace com.google.inject.XXX with jakarta.inject.XXX

Open question

misk uses detekt. Could we enable forbidding imports to enforce only using jakarta.inject.XXX?

IntelliJ can also be adjusted to ignore certain imports for "Auto import" (Link), but there is no intellij configuration within misk by default

P.S. I'm happy to do the find-and-replace 😄

👋 I'm one of the engineers working on frameworks at Cash.
We'd have to migrate our internal downstream services before we're able to do the migration to Guice 7. Will talk to the team about where to prioritise that. Given Guice 7 doesn't really have anything that isn't in Guice 6 at the moment, I'd lean towards doing the cutover later.
Using detekt would be great to check for imports!

I'm curious btw, why com.google.inject instead of jakarta.inject if they both work? I think I'd prefer to use the more generic one of the two where possible.

If we used Jakarta, it would force usage of 6.0+.. which seems fine... 🤦🏻 Admittedly, I'm biased as our downstream services are not on 6.0 yet and it would force our update - which we need to do.

I agree strongly with holding off on the cutover until later, but doing the initial migration to Jakarta seems good to get done.


[PORTAL] Update the portal with a plan of record list of Big 4

The deliverables portal at https://trustoverip.github.io/deliverables/results/2021_roadmap/ would need to be updated and suitably modified to reflect the "Big 4" priority deliverables.

Hi all,
There is a confusion between "Big 4" and "Big 5" deliverables. We have 5 deliverables in the list, but we call them "Big 4". Is there a way how we combine DP0005 and DP0006 in one document to follow "Big 4" name or should we keep calling them as "Big 5"?
I'll post this comment on Slack too.


Auto-merge pull requests

How to categorize this issue?

/area dev-productivity
/kind enhancement
What would you like to be added:
With @gardener/gardener-maintainers we discussed the idea of adding some automation for merging pull requests (like prow in kubernetes projects).
We would like a pull request to be merged automatically

if at least one reviewer has added the /lgtm label
if it was approved (according to GitHub status – at least one maintainer approval) and no more changes are requested
if all required verification steps have completed successfully (including CLA, CI, release milestone check, ...)
if none of the following blocking labels is present: reviewed/do-not-merge, needs/second-opinion, needs/rebase
with the "Squash and Merge" option by default (opt out via /merge keep-commits / /keep-commits (merge/keep-commits label))

This makes the review process two-staged like in kubernetes projects: first get a review by some reviewer, then get an overall approval / final review by an approver.
We could also think about using a dedicated approved label triggered by /approve (similar to /lgtm) to make the workflow more intuitive.
Reviewers/maintainers can then:

/lgtm + /approve for immediate merging once all conditions are met
just /lgtm for signaling that the PR has passed review
/lgtm + /second-opinion for signaling that the PR needs an additional review by someone else

With that in place, there should be no need to manually merge PRs anymore and it should be restricted to GitHub admins (if that's possible).
Why is this needed:

currently, the merge/{keep-commits,squash} labels are just indicators for maintainers merging PRs and they have to remember to choose the desired option when merging
PRs sometimes stay open for another day or two after approval although a second opinion might not be needed

From a recent experience reviewed/lgtm and needs/second-opinion are mutually exclusive labels and setting one of them unsets the other one, for example see here. So, this needs to be improved for the /lgtm + /second-opinion case.

We would like a pull request to be merged automatically ...

One more condition should be required - there must be no conflicts, but I guess GH does not allow the merge in this case anyway.

I did some research on how the above goals can be achieved. I mainly see two options:
Use GitHub Actions
There is already a GitHub Action, that seems to provide what we want to achieve: https://github.com/pascalgn/automerge-action
(if there was some gap, we might consider contributing or forking)
However, users are encouraged to switch to GitHub auto-merge, which doesn't support what we want to achieve:

This functionality is now available directly in GitHub as auto-merge. Note that GitHub does not currently support auto-rebasing pull requests. The automerge-action project will still be maintained, but users are encouraged to switch to auto-merge for simple workflows, as it offers a faster and more stable experience.

Use Prow/Tide
We could also consider setting up prow (in a first step, a rather minimal setup including tide).
Prow is obviously much more comprehensive and can achieve much more than just what is described in this issue.
I followed https://github.com/kubernetes/test-infra/blob/master/prow/getting_started_deploy.md for setting up a simple prow instance and it worked quite nicely, wasn't really complicated.
Considerations

the GitHub Action approach is obviously much simpler and should be implementable very quickly
there might be race conditions between the different GitHub Actions we already have and the automerge Action (would need to test)
we might somewhen in the future run into limitations in GitHub Actions minutes, if we keep adding new Actions
prow is more flexible in configuring required reviews/approvals (according to OWNER file), while the GitHub Action only allows configuring the number of required approvals
prow scales very nicely: kubernetes uses only one GitHub token for managing all of their repos
prow provides a nice overview dashboard via deck
prow also features functionality that we already have implemented in other GitHub Actions, so we could harmonize our setup and use one system for everything (sooner or later)

Commit Messages Check (current action) is provided by invalidcommitmsg
Release Milestone Check (current action) is provided by merge blocker issues (even more flexible than what we have today)

prow has several general advantages, once we would also configure presubmit tests (e.g. verify jobs)

PRs are retested before merging, i.e. batch test+merge (making sure, we don't get a broken master branch caused by concurrent merges)
PRs are retested again changed based branch
jobs get the requested amount of compute resources (instead of running on contended concourse workers)
the underlying cluster can properly autoscale, i.e. save resources and money when not in use (at night, on weekends, etc.) but also provide enough resources during high load timeframes
adds comments on PRs once tests fail (currently authors have to actively check PRs for seeing results)
easy retesting of only the failed jobs by typing /retest
simple parallelization of e.g. test, test-integration, check-generate (speeding up jobs)
public build logs by default
PR history
job history for easily detecting flakes (even better when connected to testgrid)
monitoring for jobs can be reused

with prow, GitHub access can be stripped down to a minimum amount of admins, everything can be achieved via /foo style commands
prow can easily be extended via external plugins: https://github.com/kubernetes/test-infra/blob/master/prow/plugins/README.md#external-plugins
prow jobs are very easy to configure (some basic k8s knowledge is sufficient)
prow is well-known in the k8s community: https://github.com/kubernetes/test-infra/tree/master/prow#prow-in-the-wild
prow config can be autodeployed by updateconfig and images can be autobumped by autobump
prow provides tools for verifying job config, debugging jobs, running jobs locally: https://github.com/kubernetes/test-infra/blob/master/prow/cmd/README.md#cli-tools
if we want to transition to prow, we would have multiple CI systems for a longer timeperiod (concourse + prow)

Having outlined the results of my preliminary research and experiments with prow, I would conclude the following:
GitHub Actions is clearly the much simpler approach and we would probably be done with the goals in this issue very quickly
However, I think that prow is in general the much more sustainable approach, as we are reimplementing more and more stuff that is already existing in the community. In the long run it will provide many benefits over reimplementing everything on our own and will also relieve us from several other pain points with our current CI setup.
Though, this is just my feeling and I will discuss this in person with @gardener/gardener-maintainers.

Update on this:

the way forward on this topic was discussed multiple times in different rounds
long story short would be: we want to try out prow in order to get a better feeling of "maintenance effort" and value add. After a POC/experimentation phase we want to decide on the target picture based on our first hands-on experiences.

What already happened:

we now have a (basic) initial prow setup at https://prow.gardener.cloud (configured in https://github.com/gardener/ci-infra)
right now it is only configured for the ci-infra repo itself (presubmit checks, postsubmit deploy jobs, auto-merge, etc.)
also, there is one e2e-test job for g/g, which will be configured as a presubmit job once https://github.com/gardener/gardener/pull/5115 is merged (also see https://github.com/gardener/gardener/issues/5024)

Next steps:

we can achieve the goals described in this issue by (simply) augmenting the prow for this repo (activate plugins, tide, branachprotector, etc.)
we would need to

change our review process slightly to follow what kubernetes is doing
start using the new commands (/lgtm and /approve)
set up OWNERS files for this repo (replace CODEOWNERS)
disable @gardener-robot on this repo to prevent conflicts in commands, label sync, etc. (already in the works)

However, it is still to be clarified, when and by whom this will be done.

Heads-up: auto-merging will be activated for this repository with https://github.com/gardener/ci-infra/pull/144
cc @oliver-goetz

Implemented with https://github.com/gardener/ci-infra/pull/144. Thank you very much @oliver-goetz! 🚀
/close


Machine win-13 temp directory is full.

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
infra task
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
Machine win-13 temp directory is full.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Removing and cleaning files under C:\Users\wwarming\AppData\Local\Temp directory to clear the error.


Features.doc fixes

Moved USE_ENVIROMENT_INPUT (the typo version) to now be standardized as USE_ENVIRONMENT_INPUT.  In order to not break backwards compatibility, the old one is still supported.
Fixed various typos and grammar usage in the README.md file.
Added the license text to the top of the version.h file.

The clang / LLVM build crashes LLVM.  The corresponding ticket is under
https://github.com/llvm/llvm-project/issues/79678

Looks like dietlibc has issues with networking running inside a docker container in a github action.  This needs some digging.

This has been superseded by a different patch.


Password characters flash from color to black&white

Password characters (animals to click on, instead of typing in letters) flash in color for a half-second when you login. Then after that fraction of a second, the animals revert to black+white.
It happens on slow connections.
Below is on Chrome with Slow 3G mode.

Referenced by https://github.com/iiab/iiab/pull/2613#issuecomment-721199618

Fixed in https://github.com/llaske/sugarizer/commit/10be097082871eebc820b7978e6ed899e5d2142b


OS not working with strip-all

.. and it would be glorious if it did.

I found the problem to be with the -Oz optimization flag. Simply using -Os fixed all the strange issues with broken stacks and so on. It seems like -Oz creates broken code. I tried debugging the ELF header and everything seemed fine. Some functions returned bogus values on stack etc. so I can only assume that -Oz does something cute to reduce size that simply doesn't work for us.


help: Open Help Center links in new tab for empty message lists.

Fixes: #25337

Screenshots and screen captures:
https://user-images.githubusercontent.com/72064462/235568716-a7622606-c368-42db-beca-371d9a9ea21a.mov
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

These links all need rel="noopener noreferrer; it's an important security thing whenever using _blank.

@timabbott I have updated the PR, you can re-review now.

This looks good, merged, thanks @akarsh-jain-790!


VKObserver doesn't push TEdit or TMemo controls above the keyboard when at the bottom of a listbox/scrollable container (maybe other cases too)

I tried various versions of this and could reliably reproduce when the control are in a TListBox control.
If you create a TListBox, aligned to client and fill with TListBoxItem so you have some at the very bottom of the device screen. Add a TEdit to one of those at the bottom well below the keyboard.
Run the app and tap the TEdit. It doesn't push the control up above the keyboard.
I've discovered that it's because the ContentBounds isn't being increased on the list box so there isn't enough "scroll" to push it up.
Adding some extra space to the bottom of the content bounds fixes this but the ideally the VKObserver needs to do this itself to avoid having to do this on every container.
procedure TForm2.listboxCalcContentBounds(Sender: TObject; var ContentBounds: TRectF);
begin
ContentBounds.Bottom:=ContentBounds.Bottom + 400;
end;
Thanks

Interestingly, changing the top margin on the TListBox does seem to work fine with set to Client - all except for the bottom rows of the list, but may just be coincidental effect. I agree with not hooking the OnCalcContentBounds, that would be a headache waiting to happen, I just wondered if there was some other way to do this but I suspect not.
Thanks for the info, I'll apply ActiveFrame.Height.


(WIP) Fix #158: support empty Projection clause

What this PR does:
Adds support for optional empty "projection" parameter, validation that if passed its JSON Object.
Serves as the base for actual projection implementation
Which issue(s) this PR fixes:
Fixes #158
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

Right now this will only support empty "projection", fail on non-empty. I will create a follow-up for completing handling but want to get this merged so that we can reconcile work for sorting and keep PRs from getting huge.

On a related note @tatu-at-datastax , what do you think about adding support for empty options object as well? Right now, Mongoose always sends empty options to deleteOne(), for example, which always fails. We can strip that out in the driver layer, but I think it would be better for the jsonapi to handle that.

Merged; had to re-run cancelled CI once.


Added support for tekton taskrun

Short description:
Create support for tekton taskrun
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

Hello, I see some failures in pre-checks .Unsure why it failed as i don't see failure logs

/retest python-module-install

/retest python-module-install

I see some additional changes happened but those looks okay to me so marking it as verified @myakove @rnetser
/verified

/lgtm


Test prefetcher hanging with changes to get around asserts

Repro hang:

git checkout aliu/test-prefetcher-hang
CONFIG=Release ./build_metal.sh or CONFIG=Debug ./build_metal.sh
TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_metal/perf_microbenchmark/dispatch/test_prefetcher -t 1 -i 5 -ss 16384

The changes on the branch are to get around asserts seen with Debug build. Seems like the test should be still valid, but probably a new test case.

I reproduced the hang, fixed a couple of test sizes, then cannot reproduce a hang on either GS or WH after a few hundred iterations.

Changes in main. Closing


YOLO V3 INT 8 quantization weights

Hi, thanks for the great work! I run the INT-8 inference using YoloV3 weights(248M) with the flag -quantized successfully, just wondering is it possible to save the INT 8 quantization weights first (size would be ~60M), and then run a float 32 inference, is anyone compare the performance difference here?

@Yinling-123 Hi,
If you will use INT8-weights and FLOAT32-inference:

then speed will be the same as for FLOAT32-weights and FLOAT32-inference
accuracy will be slightly lower than for FLOAT32-weights and FLOAT32-inference

So it doesn't make sense and isn't implemented, because FLOAT32-weights and FLOAT32-inference better.
In this repository is implemented INT8-weights and INT8-inference, +30% speedup and -2% accuracy.

@AlexeyAB Thanks for your quick reply, I will be greatly appreciated if you can guide me how to converter the FLOAT32-weights to INT8-weights use this repo?

Hi, is it possible to add the converter feature (which save the INT8 weights) in this repo, I found gplhegde version darknet has the converter but not support YOLO V3 weights,

@Yinling-123 Hi,
No, there is no code for saving INT8-weights currently.

Yes, now you can!

In this repository is implemented INT8-weights and INT8-inference, +30% speedup and -2% accuracy.
You mean fp32 weights and int8 inference right?

@isgursoy

You mean fp32 storage and int8 inference right?

I mean fp32 storage, fp32->int8 weights conversion, and int8 inference.

Why one would need to dump int8 like https://github.com/AlexeyAB/darknet/issues/1405 ? What are pros and cons doing that?
Thanks for your time.

@isgursoy

Why one would need to dump int8 (on Pascal or Tesla) like AlexeyAB/darknet#1405?

Can you clarify? I don't understand.

Hi,
Let's say I exported fp32 weights as you described in https://github.com/AlexeyAB/darknet/issues/1405.
I wonder the pros and cons of using int8 storage on Pascal or Tesla GPUs.

@isgursoy
Pros - small weights-file size
Cons - you can't use this weights-file as pre-trained weights-file

Can you roughly estimate gpu mem gain and the loss of accuracy if there will be?
Motivation for us is accuracy-mem tradeoff here.
Regarding pretrained weights, it wont be problem if we get export after training right?

May be it will use ~3x less GPU_RAM

Without loss of accuracy?

If you just will store weights-int8 instead of weights-fp32 then you willn't get any gain in GPU-RAM / CPU-RAM and will not get any loss of accuracy.
To get less GPU-RAM usage you must implement all layers int8 in yolov3: upsample, route, shortcut. And should use only l.biases_gpu, l.weights_int8_int8x4_gpu and l.output_gpu_int8 instead of: https://github.com/AlexeyAB/yolo2_light/blob/master/src/additionally.c#L2820-L2827
You will get low drop in accuracy.

是的，現在可以了！

How can i use ?!


Setup e-mail

acceptance criteria:

[ ] There is a "no-reply" email address configured from which Jenkins can send emails.
[ ] Replies to that address are deleted.
[ ] There is an admin-mailing list where the server can send error messages.

hint:

have a look at https://cloud.google.com/compute/docs/tutorials/sending-mail/

won't fix because of #154


[BUG] Inconsistent of register-center-access

https://shenyu.apache.org/zh/docs/user-guide/property-config/register-center-access
The configurations in shenyu-client配置 are inconsistent. Some is shenyu.client and others are shenyu.register

I think shenyu.register is correct.
reference: some yaml files in shenyu-examples
https://github.com/apache/shenyu/blob/52f7f77d35a42fc66be544ae10b9337ecd1c8739/shenyu-examples/shenyu-examples-http/src/main/resources/application.yml#L22-L23
https://github.com/apache/shenyu/blob/52f7f77d35a42fc66be544ae10b9337ecd1c8739/shenyu-examples/shenyu-examples-dubbo/shenyu-examples-alibaba-dubbo-service/src/main/resources/application.yml#L27-L28
https://github.com/apache/shenyu/blob/52f7f77d35a42fc66be544ae10b9337ecd1c8739/shenyu-examples/shenyu-examples-websocket/shenyu-example-spring-annotation-websocket/src/main/resources/application.yml#L20-L21

doc is error， you can refer example to fix


[CT-1666] Dynamically change the page title according to a dbt resource

Describe the feature
dbt-docs dynamically changes an URL when opening a dbt model. However, because the page title remains unchanged, they appear in our browser history as fixed. When we want to open an URL on the browser history, it is difficult to identify one at a glance. So, it can get better by dynamically changing the page title as well.

Describe alternatives you've considered
I don't have any alternative ideas.
Additional context
N/A
Who will this benefit?
dbt-docs users can identify pages in their browser history.
Are you interested in contributing this feature?
I would love to contribute.

@dbeatty10 I'm not familiar with angular. But, according to my research, it might be good to take advantage of the existing stateProvider or $urlRouterProvider. I will look into it later.
https://github.com/dbt-labs/dbt-docs/blob/834e84aa1ca94ecdba9566ca64ad317cb2f5c17b/src/app/index.routes.js#L24-L144
It seems that an OSS AngularJS module under MIT license specialized to dynamically change title on top of ui-router. But, it hasn't been maintained for more than 6 years.
https://github.com/nonplus/angular-ui-router-title


[stdlib] Speeding up typechecking for complex expressions with integers

Utilizing the shortcut in the compiler to make expression with heavy use of bitwise operators and shifts compile much faster, especially in Swift 3 mode.
Fixes: https://bugs.swift.org/browse/SR-4709, https://bugs.swift.org/browse/SR-4864, and also rdar://problem/31543153.

@swift-ci Please smoke benchmark

@swift-ci Please test

@swift-ci Please Test Source Compatibility

@swift-ci Please test

@swift-ci Please smoke benchmark

@swift-ci Please Test Source Compatibility

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - e0df75fcfcf65a093a1e45d1745cd8554e240cab
Test requested by - @moiseev

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - e0df75fcfcf65a093a1e45d1745cd8554e240cab
Test requested by - @moiseev

The need for these changes makes me 😢 but glad you figured this out

Build comment file:
Build failed before running benchmark.


network data mode changed

Hi Jim,
I have just got a comment on the Steam guide I made regarding the 'pCARS and pCARS2 (network data)'
The latest update has pCARS (network data) and pCars2 without the UDP controller in the bottom left. If we want to use network data do we have to use the pCars1 option?
Is it possible to reinstate this option?

yes, if you want to use network data in pCARS2 you have to use pCARS1 mode. The pCARS2 UDP data is still too buggy to use. I've implemented it but it really doesn't work properly so it's unavailable, When SMS sort out the many issues I'll finish the Crew Chief implementation


Upgrade httpclient from v3 to v4

Purpose
$subject

The PR is closed due as we are using WSO2 forked and managed Axis2 library (1.6.1-wso2v76), in the runtime the Axis2 requires commons-httpclient (httpclient v3).  The HTTP transport in Axis2 1.6.x uses commons-httpclient 3.x. Only Axis2 1.7.x onwards has support for HttpClient 4.x. In that case Axis2 have to be upgraded before hand.


Update to Python 3; Adapt to changed ACM confirmation

ACM confirmation mail for the certificate change and code had to be adapted
building the code locally with Python 2.7 did not work --> updated to 3.8
replaced urllib with requests

Thank you @heroldus 😄

Thank you @heroldus 😄


Error: Query root type must be provided

I seem to be getting this error:
https://github.com/prismagraphql/graphql-import/issues/73
I'm running 0.0.10, with a schema generated by graphql-cli from a gatsby project:
# source: http://<IP_ADDRESS>:8000/___graphql
# timestamp: Sat Jul 28 2018 17:46:31 GMT+0000 (Greenwich Mean Time)

schema {
  query: RootQueryType
}

"""
A date string, such as 2007-12-03, compliant with the ISO 8601 standard  for
representation of dates and times using the Gregorian calendar.
"""
scalar Date

# ...

Here's the full error:
(node:15016) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Query root type must be provided.
(node:15016) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

No stack trace, unfortunately.

@rdrey Thanks for reaching out. Where did you get this error from? Can you please share some more details.

I'll get back to you in a few hours (hopefully with a tiny example project), thanks!

I have mentioned only 1 mutation in my schema,
on graphql getting this error like "Query root type must be provided."

@rdrey : Can you share your schema please?
@TEJAPS : Again, can you share your schema please?
According to the GraphQL spec: http://facebook.github.io/graphql/June2018/#sec-Root-Operation-Types
The Query root type must be provided. If you schema is missing it then that would result in this error.
I think this is not a bug but a feature. Need more information to validate.
Thanks!

const WAUsers = require('../models/wibesAppUsers');  //this is mongodb model
const wAUType = new GraphQLObjectType({
name:'wAP', //like table name
fields:() => ({  //like column names
human_name:{type:GraphQLString},
pass_code:{type:GraphQLString},
})
});
const Mutation = new GraphQLObjectType({
name:'Mutation',
fields:{
addWAUser:{
wAUType,
args:{
human_name:{type:new GraphQLNonNull(GraphQLString)},
pass_code:{type:new GraphQLNonNull(GraphQLString)},
},
resolve(parent,args){
let user = new WAUsers({
human_name:args.human_name,
pass_code:args.pass_code,
}); //Author is the collection imported from models
return user.save();
}
}
}
}
})
module.exports = new GraphQLSchema({ mutation:Mutation
});
i am importing mongodb model and inserting into it using graphql schema

But if i pass a query along with the mutation , error is gone .
But the thing is i don't want any query on that page

Can you please provide a small reproduction repository? Thanks1


[Request] Command to reinstall latest versions of default_packages

Currently we use nvm install [same version we're already using] - but this is a bit unwieldy and presumably does quite a bit of unnecessary work.
Our use case is to update to the latest version of global dependencies that often introduce/resolve bugs, requiring rather frequent upgrades.

While there basically shouldn't be any globally installed packages - community guidance/best practices on that has evolved since the feature was added in 2017 - this seems reasonable.
We have nvm reinstall-packages $version already - maybe nvm install-default-packages?

Another option might be to allow passing this nvm --reinstall-packages-from=default without the need for a command like nvm install.
nvm reinstall-packages latest would be good too, if latest were allowed as a version.

latest is already a potential user alias, as is default, so i don't think we can leverage reinstall-packages for this.

Does nvm reinstall-packages * work? I'm not able to check for a while, but that would be a good syntax if there's nothing blocking it.
New commands would also be welcome, of course!

While there basically shouldn't be any globally installed packages

I somewhat agree, but the reality looks different (i.e. expo-cli has to be installed globally to work or neovim/tree-sitter-cli for LunarVim
I need a dedicated command to just update those global dependencies, because this will fail with permission issues:
	npm_global_packages=($(npm list -g --depth 0 | awk '/ /{print $2}'))
	for val in "${npm_global_packages[@]}"; do
		npm i -g --force $(echo $val | tr "." "\n" | head -1)
	done

My goal is to upgrade node, reinstall all packages form the previous node version and upgrade all default-packages.

Anything global should work with npx also.
Why will that fail with permissions issues? Anyone running node should have full ownership of npm root -g

@ljharb Thanks, for some reason I had issue, but I retried today and somehow cannot reproduce. In fact, the code-snippet I shared above is working fine to upgrade all globally installed permissions. Although it's still not what was originally requested, because it will not just upgrade default-packages, but minor versions of all global packages.
npx itself is great, but it does not upgrade without @latest suffix, as you mentioned.

I checked the code - nvm install $(nvm current) doesn't really do much extra work; and if you have an .nvmrc, nvm install would do the same thing.
That said, this is a trivial command to add, so I'll do it.

But what if a user only needs to update one out of, say, 15 global packages? In that case nvm install is doing a lot of extra work reinstalling all of those, no?

@Slapbox well sure, but nvm install-default-packages would do that too. If you know which packages you need to update, you'd just run npm install -g $thatPackage.

Basically, it just does npm install -g a b c d or whatever, and npm figures out what needs to be actually updated. nvm wouldn't do any further optimization than that.

@Slapbox well sure, but nvm install-default-packages would do that too.

Definitely fair. I'd forgotten that was my original suggestion.

If you know which packages you need to update, you'd just run npm install -g $thatPackage.

I hadn't thought that was safe to run when using nvm. Thanks for the tip!

I personally I think there's no point adding any additional command with your findings in mind - I think the existence of this issue and your comments are sufficient - but I'll leave it to you to decide whether to close this now or later.
Thanks again @ljharb!

In that case, I'll close it until there's demand in the future.
I did land f062cca, which refactors things so it'll be a two-liner and a test file to add the command if needed in the future.

Was the takeaway here than with node installed via nvm, we can use npm install -g [package] and it's effectively the same as what nvm does with the default-packages file?

That’s never been the behavior.

I don't know what to say. It definitely used to occur for me on both macOS and Linux.

Sorry, I should clarify. If you have a $NVM_DIR/default_packages file, then it definitely should reinstall them when you install a new node version. My understand is that this issue was asking for a command that reinstalls them on demand?
You can npm install -g $(nvm_get_default_packages), although there's no guarantee that internal function will remain around.

Thanks for the tip, I'll give that a try!
But previously (in 0.39.0), if we were on Node 20.11.0, running nvm install 20.11.0 would indeed reinstall all the global packages, whereas now it simply says that the version is already installed. The new behavior is probably more idiomatically correct, but there's definitely been a change in behavior somewhere in the patch versions.

That's fair, and makes sense. If you're able to bisect and figure out in exactly which version it changed, I can pinpoint the commit that caused it, and then can evaluate whether that change was necessary.


How do I use my data on the wiki?

I've installed this plugin but I can't see how to use it from the wiki's side. If I go to a quest's page it still doesn't show any information. I would assume I would have to write my RSN somewhere like in the RS3 wiki but I don't where.

We are looking at deploying the required changes to the wiki this week/weekend, but right now we are still testing some stuff on the wiki end so nothing is available publicly yet. We had to release it on plugin-hub first in order to avoid getting blocked on that.
Sometime in the coming week, you should see text inputs similar to RSW's on quest pages where you'll be able to type in your username. I'll leave this issue open until we deploy it on-wiki for everyone to see.

This should be live now (assuming the cache has had time to purge). So feel free to try it out! Closing this issue now since we have released.


More flexible database creation and existence check methods

It is common with some database systems (in particular SQL Azure) to get an empty database provisioned and only create tables. With the current Create and Exists method this situation is not easy to handle, Exists will respond that the database exists but the application cannot use it without the tables.
Create already does both database and table creation but looking at this scenario we are worried about muddying the semantics of Exists (there are are actually very possible variations for checking tables, e.g. it could check if there "any table" or "any table from the model" or even "all tables of the model").
Tentative plan for now is (from Arthur's email):

context.Database.Exists => True if database exists regardless of whether it has tables or not
context.Database.HasTables => True if database exists and has tables (any tables, not just mapped ones)
context.Database.Create => Creates the database but not the tables
context.Database.CreateTables => Creates the tables in the database

Then one wrapper method for common case:

context.Database.EnsureCreated => Creates the database and tables if necessary

Method names will be revisited, as well support for shared databases scenarios.

@rowanmiller The current design does not work well with several DbContexts pointing to the same database https://github.com/ErikEJ/EntityFramework7.SqlServerCompact/issues/205


site-navigation request

hi
I want site-navigation will back.
This image link explain everything.
thank you

The way it was implemented was not user-friendly. If we add those links, it would be great to rework them.

Done with #1551 & #1545


Laboratory work #7, Kulaeva Amaliya - 20FPL2

Necessary implementation of loading your dataset.

It's time to write the loading of your dataset.

And again: it's time to write the loading of your dataset.

And again: it's time to write the loading of your dataset.

It's time to start doing your first lab.

It's time to start doing your first lab.


%%async

how about a magic that lets a cell run in the background?
%%async --then tag and could trigger other cells when done?

Would need to show a cancel button until it finishes.
Std Output would go here, unless captured by the Output Widget.

https://github.com/leriomaggio/async-ipython-magic


[kuksa-feeders] Support for a c(pp) SDK

Dear Kuksa Team,
We are currently looking to integrate one of our C applications into the kuksa world.
To do this, I am looking for a C or a C++ SDK for interacting with the databroker.
kuksa-someip-provider does something like this already, but the code is tightly coupled with the someip application.
Dont you think making the databroker APIs from the kuksa-someip-provider available as a library will help integrating other C/C++ applications?
Thanks.

IMHO it would be great if we would have a kuksa-c-sdk or kuksa-cpp-sdk similar to https://github.com/eclipse-kuksa/kuksa-python-sdk. As far as I know no-one is however working on it or plan to do something in the near future. If someone one would be willing to contribute a first version we could start a discussion on where it should be stored.

I'm interested in contributing to this 😄

Discussed at Kuksa community call today. Short notes below

We do not want to create a kuksa-cpp-sdk repo until we actually have something that actually can be called an SDK. We are planning to create a kuksa-incubation repo where this could fit mid-term, but as that repo does not yet exist initial work could be performed as a pull request to this repo.
The KUKSA SOME/IP provider could possibly be used as designbase, but unclear how well structured the client/SDK parts in that repo are.
Coordination with Velocitas project could be useful, as they already have some form of CPP SDK/Client, however focusing on their needs only. Could possibly be used as designbase and extended to cover more Kuksa functionality. It anyway need to be refactored to use the "newer" databroker API.

We are about to archive this repo soon. If you consider this issue as important please file a new issue at one of the new Kuksa repos at https://github.com/eclipse-kuksa


add a public API:remove

When I develop a dynamic web server I find no method to  unregister route(s), so I add this API to remove path(s) and handler(s).

Hi! Thanks for this pull request! Unfortunately there are no tests included, which you will need to add tests to cover all possible branches in your code before we can accept.
Also, please take some time to search through some old pull requests that tried to implement this feature, as your implementation has the same issues as the others, namely that there is no safe way to use your method, since it will break all in-flight requests at the time your method is called.
You can find a recent discussion on this topic here: https://github.com/expressjs/express/pull/2695

Thanks for your response.
I didn't think about the situation you say and I'll search that~

I considerate this remove method and issue these days.
I have an idea:I give every route in the stack a boolean variable “flag” to mark it available.When I call this "remove" method.It just mark the "flag" false to resist request.
I'm not sure if there is any other problem~
How do you think?
Could you give me your opinion?
Thanks~

@yalishizhude referring to your last comment, it might be best to do at your application level, instead of building the functionality into the framework. We want to keep Express flexible but basic and simple at core.
Do we want to keep this PR still open? There was a similar one https://github.com/expressjs/express/pull/2695, which was closed.


[DNM] replace Box::new(cb) with box cb

Signed-off-by: zhangjinpeng1987<EMAIL_ADDRESS>

/release

/bench

If possible could you compare with Box::new_with from the boxext package?


feat: add Witnet to the ecosystem page

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Re-initialize ScreenUtil when handling multiple layouts

Currently, my application has two different UI design drafts for mobiles and tablets. The mobile design draft has the size 375x812 and the tablet draft has a size of 768x1024.
I'm using LayoutBuilder widget to display different UI to the user according to the screen size. My question is that how can I initialize or rather re-initialize ScreenUtilInit separately for mobile and tablet layouts?
For example, consider the below code -
@override
Widget build(BuildContext context) {
  return ScreenUtilInit(
    designSize: Size(375, 812), // Draft size according to mobile device
    allowFontScaling: true,
    builder: () {
      return MaterialApp(
        home: LayoutBuilder(
          builder: (context, constraints) {
            if (constraints.maxWidth > 600) {
              //UI for tablet devices
            } else {
              //UI for mobile devices
            }
          },
        ),
      );
    },
  );
}

In this case, is there an option to re-initialize ScreenUtil with different dimensions when the application is running on tablet devices?

device_info can determine whether the device is a tablet or a mobile phone.
And it’s better to use dp as the unit of the design draft, because the unit of initialization is now dp more appropriate


Containing deprecated service

The related paragraph:
Security features of the Premium service tier include content trust for image tag signing, and firewalls and virtual networks (preview) to restrict access to the registry. Microsoft Defender for Cloud optionally integrates with Azure Container Registry to scan images whenever an image is pushed to a registry.
The link of "scan images" is to: https://learn.microsoft.com/en-us/azure/security-center/defender-for-container-registries-introduction
This method is deprecated and is being replaced by Vulnerability assessments for Azure with Microsoft Defender Vulnerability Management.
Hence, I believe some improvements has to be done.
I suggest the following content can be appended:

Microsoft Defender Vulnerability Management (MDVM) for scanning images in Azure Container Registry (ACR) when image is being pushed, imported, pulled, or required by continuous rescan.

I did not create a PR because

I don't know if I should add this description as a note.
I also don't know if I should delete the deprecated-related feature's description, which is referring to "Microsoft Defender for Cloud optionally integrates with Azure Container Registry" here.

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

ID: b876f15f-5cad-5764-891d-ff8184f3d8ca
Version Independent ID: 7831214a-7ed5-30ae-d3c0-d0474a90f56c
Content: Managed container registries - Azure Container Registry
Content Source: articles/container-registry/container-registry-intro.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@JoeyC-Dev
Thanks for your feedback! We will investigate and update as appropriate.

@JoeyC-Dev
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

https://github.com/MicrosoftDocs/azure-docs-pr/pull/270434


Highlight Kubernetes Training: CKA/CKAD and Intro to Kubernetes edX.org

This is a response to @timstclair:
https://twitter.com/cra/status/1227977913393438721
We highlight KTPs on the partners page but for individuals, we should find a way to highlight the free Intro to Kubernetes course on edX.org + the CKA/CKAD courses. Anything we can do to highlight education options for the Kubernetes ecosystem is a win.

@timothysc

👋  @zacharysarah asked me to look at this.
If I understand correctly, the things we want to highlight are:

The free edX courses here: https://www.edx.org/learn/kubernetes
The different training programs provided by the companies here: https://kubernetes.io/partners/#ktp
k8s training and certs here: https://training.linuxfoundation.org/

Is there anything else that comes to mind?
In terms of execution: I think the best option (also suggested by Zach) would be to add a "Training" menu item to the top nav. As smart as pointing people to relevant training in sections of the documentation might be, I think it would leak vendor/company-specific content into the documentation, which is a no-no.

/assign @celestehorgan

@celestehorgan Sounds good! ➕


gnome-logs-3.20.1 fails to start with error Settings schema 'org.gnome.desktop.interface' is not installed

Issue description
Attempting to run gnome-logs while not in the GNOME desktop environment results in the error:
(gnome-logs:25409): GLib-GIO-ERROR **: Settings schema 'org.gnome.desktop.interface' is not installed
Simply installing the package gsettings-desktop-schemas-3.20.0 is not sufficient to resolve this error.
Steps to reproduce
Install gnome-logs with nix-env -i gnome-logs. Do not install GNOME (I am using xfce4 + xmonad). Try to run gnome-logs.
Technical details

System: NixOS 16.09.1799.058983a (Flounder)
Nix version: nix-env (Nix) 1.11.6
Nixpkgs version: 16.09.1799.058983a

This was fixed in #28053


Fix missing source stacktrace in DioError

Improve nullability in DioMixin.assureResponse

there should never be a case where there are not RequestOptions available
this is technically a breaking change but we should instead mark this @internal in the future

Fix missing source stacktrace in DioError

a DioError should always have a meaningful stacktrace which points to the actual invocation of Dio.get/post/xxx
Dio historically lost a lot of this source information due to a multitude of asynchronous calls
now the source stacktrace is consistently being set into the RequestOptions instance and can later be retrieved and used when a DioError is constructed
additionally a DioError may contain another cause which may itself contain a separate stackTrace with more detailed information

New Pull Request Checklist

[x] I have read the Documentation
[x] I have searched for a similar pull request in the project and found none
[x] I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
[x] I have added the required tests to prove the fix/feature I'm adding
[x] I have updated the documentation (if necessary)
[x] I have run the tests without failures
[x] I have updated the CHANGELOG.md in the corresponding package

Additional context and info (if any)
The existing behavior which was somewhat correct got lost in https://github.com/cfug/dio/pull/1405 which was merged in the temporary diox repository.

Is it another approach to fixing stack trace in errors or it contains the fix that #1721 does overall?

I feel like we would improve the current code base and the exceptions if we improve the inner workings of dio, instead of trying to attach the correct stacktraces

I agree but currently it is just not possible to trace any error to it's source. And this broke in 5.0.0
This is a minimal invasive approach to add the old behavior back.
I don't see anyone rewriting the inner workings anytime soon and even if, then you will still have a lot of async gaps that break the stack traces.

But yea this will currently not work when any interceptor manually creates a new instance of RequestOptions.

I read a little bit last night. This has nothing to do with how dio is written. There is just no way to avoid the async gaps when async/await is used. There is always a new stacktrace from the moment the async call is started and at that point the context of the original call site of Dio().xxx is lost.
But this is the only important information any dio client/user needs, a stacktrace which starts somewhere inside DioMixin.fetch helps nobody.

I feel like we would improve the current code base and the exceptions if we improve the inner workings of dio

So as a result I don't think this is an option.
There is https://pub.dev/packages/stack_trace which uses zone magic to combine stacktraces across async gaps. This can combine the stacktrace(s) correctly but it also comes with the performance overhead of zones and a different string representation of the stacktraces. I created https://github.com/cfug/dio/pull/1723 tho showcase this.

We need to discuss how to proceed here. https://github.com/cfug/dio/pull/1721 also attempts to fix a smaller part of the same problem. There is no simple solution for the async gaps but IMHO dio needs to ensure that the stacktraces in DioError are available and useful.

I will see if I can add some tests similar to those in #1723 so we can make sure that stacktraces are not lost again.

I think this is ready

As this PR seems to handle the issue I intended to solve in #1721, but also solves a bigger issue as well, maybe you could take the two tests from my PR to hopefully catch future regressions in regards to stack traces in interceptors?

I still got an invalid stack using the branch to test with #1749.
With the branch:

The real stack should be:

I still got an invalid stack using the branch to test with #1749.
With the branch:
The real stack should be:

I don't now, should it really be that stackTrace? You don't have any indication of the call of your code in it. You see that jsonDecode failed but nothing more.

I don't know, should it really be that stackTrace? You don't have any indication of the call of your code in it. You see that jsonDecode failed but nothing more.

IMO it should be. When you trying with #1749 with the previous code, catchError((e, s) {})'s stack can obtain the correct stack (as in my last image). But with this fix, the stack is completely gone even if we add back the stack trace argument and I have no idea who cause the format fail.

Well, that is the trade off. It would be the same with https://github.com/cfug/dio/pull/1721 - in the interceptor you would not see the jsonEncode stack trace.
I guess we need a discussion about this:

a DioError should always have a meaningful stacktrace which points to the actual invocation of Dio.get/post/xxx

It just seems not pointed to the real request.

a DioError should always have a meaningful stacktrace which points to the actual invocation of Dio.get/post/xxx

It just seems not pointed to the real request.

Yea that will not work, unless we can use Error.throwWithStackTrace. If we throw DioError(...) then the stackTrace that you catch will always point to this line. But DioError.stackTrace should be correct and reference your test file.

But we still have a problem if DioError.error is Exception - in this case we lose the original stackTrace from where the exception was thrown. The only way I see is, we wrap it again, which is horrible.

Sounds like we should have an issue to track for problems with exceptions, about what shall we do, what we've done, and when to do something.
I'll leave this PR to @ueman to decide what's next.

I recognize that we're right probably not able to always have a useful stacktrace due to the various reasons already laid out. I also think we (well not me but you guys, @kuhnroyal and @AlexV525) tried our best at getting a useful stacktrace here, but it might simply not be possible to satisfy every use case.
FWIW, I think the stacktrace of the dioerror should point to the invocation of get, post, etc and the inner stacktrace should always be the stacktrace of the inner exception. But since we can't use Error.throwWithStackTrace yet.
To conclude, as long as the errors got at least somewhat better than before, I'm happy with this PR. We don't need to get it perfect right now, since we can always iterate and improve later on.
Especially with Dart 3 right around the corner we have a good opportunity to revamp how we deal with exception and stacktraces (as well as other parts if needed). @kuhnroyal already started a discussion for that over at https://github.com/cfug/dio/discussions/1753

I will resolve the conflicts and add the tests suggested by @lohnn - then we can release this as 5.1.0 I would suggest.

We should wait with the merge until we have released another hotfix 5.0.4 with some encoding fixes.


Compiling with warnings in create-react-app

Describe the bug
When importing this module into a react app, I am seeing some warnings from the Webpack source-map-loader.
Compiled with warnings.

Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/constants.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/constants.ts'

Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/helpers.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/helpers.ts'

Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInLayer.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInLayer.ts'

Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInScene.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInScene.ts'

Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushin.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushin.ts'

src/App.js
  Line 3:10:  'PushIn' is defined but never used  no-unused-vars

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

WARNING in ./node_modules/pushin/dist/esm/pushin.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/constants.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/constants.ts'

WARNING in ./node_modules/pushin/dist/esm/pushin.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/helpers.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/helpers.ts'

WARNING in ./node_modules/pushin/dist/esm/pushin.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInLayer.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInLayer.ts'

WARNING in ./node_modules/pushin/dist/esm/pushin.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInScene.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushInScene.ts'

WARNING in ./node_modules/pushin/dist/esm/pushin.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushin.ts' file: Error: ENOENT: no such file or directory, open '/Users/nathanblair/Sites/pushin-react/node_modules/pushin/src/pushin.ts'

To Reproduce
Steps to reproduce the behavior:

Create a new web app using npx create-react-app my-app
Run npm install pushin
Import the library at the top of App.js using import { pushin } from 'pushin'
Run npm start

Expected behavior
create-react-app should be able to compile without warnings.

This is fixed on v4.1.2


Telemetry Manager code move to new repository (dry-run)

Description
Changes proposed in this pull request:

Entire code move to the new repository

Related issue(s)
https://github.com/kyma-project/kyma/issues/16736

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build


How to run wexflow on docker with custom Task

where i should put the custom task .dll file when using docker?

Custom tasks are not supported when using Docker for the moment. They are only supported by the .NET version.
What you can do is to clone the repo, open Wexflow's solution and add your custom tasks in the .net core version. In this case, don't forget to reference your custom task in Wexflow.Server project.

Custom tasks are not supported when using Docker for the moment. They are only supported by the .NET version.
What you can do is to clone the repo, open Wexflow's solution and add your custom tasks in the .net core version. In this case, don't forget to reference your custom task in Wexflow.Server project.

Is wexflow support linux with custom tasks?

No, custom tasks are not supported in Linux for the moment. Even if you copy .dll and .pdb files to /opt/wexflow/Wexflow.Server, it won't work.
To create your own tasks on Linux, you have to clone the repo, create your custom task in the solution, reference your custom task in Wexflow.Server project then create the .net core package (see .net core installation script).

No, custom tasks are not supported in Linux for the moment. Even if you copy .dll and .pdb files to /opt/wexflow/Wexflow.Server, it won't work.
To create your own tasks on Linux, you have to clone the repo, create your custom task in the solution, reference your custom task in Wexflow.Server project then create the .net core package (see .net core installation script).

I try the docker way to run custom task and it is work by copy .dll and .pdb files.

But i found that the running workflow is remove when restart the docker container using sqlite way.
The processing workflow can not maintain the status when restart container using sqlite way.
Dose the sqlite store the status of running workflow?

Do you use Dockerfile or Docker Compose?
Also, Try another database system like MongoDB for example.

@jeremy-xu I added support for custom tasks to the .net core server. Now, you just have to copy the .dll and it will work. I will publish this feature in the v5.4.

@jeremy-xu I've just released the v5.4. Can you test   the .net core version and custom tasks and let me know?

The v5.4 is working fine now regarding custom tasks for both the .net and the .net core version.


Team & Maintainership - post here to discuss membership on this project

This is an "evergreen issue" (which will not be closed), post here to coord team topics and membership; for bigger topics create new issues and refer to this one to link them.
If/when it gets too long/busy we'll close and roll over to a followup up "issue".

@antoinepairet @shyamal890 @jkurz @ProLoser

Hopefully with some help we can

T&R... 1.0.2 with a bunch of well understood fixes, such as the memleak referred to in #387
evaluate whether master is stable (it is not for me right now :-/ ) and how to address
address any changes needed for 2.7.0

Related

Anyone against marking 1.0.1 and 1.0.0 as releases in the github releases page? It is confusing as it stands.
Who can manage the bower db entry? does it need to be managed?
Who can manage the npm db entry? does it need to be managed? https://www.npmjs.com/package/angular-ui-calendar - it says "luchesar" but I dunno who that is. @luchesar ?

@martin-langhoff I've made you a team maintainer so you can add other collaborators

@ProLoser thank you!

Quick update:

marked recent releases as releases here in github
published my 1.0.x maintenance work on a maint-1.0 branch

My intent is to consider/review PRs with narrow and safe fixes for landing, towards a 1.0.2 T&R.
The only potentially controversial thing on my maint branch is (I hope) a pass of dos2unix. Working through recent git history is rather hard because there are newline and spacing inconsistencies, and they ebb and flow from commit to commit. One of my goals is to tidy that up.

The maint branch at last - https://github.com/angular-ui/ui-calendar/tree/maint-1.0

@martin-langhoff is there plan to publish your changes to npm? thanks

@peterver - maintainership discussion.

:] as i told @martin-langhoff in the discussion #408 i'd be happy to start collaborating on this

Apologies about delay, added @peterver , will look at making an RC in coming days, then aiming towards tag-and-release.

@martin-langhoff is there any progress?


Codemirror version used?

Hi, this part of the doc state that desktop uses CM v5 while mobile uses v6

https://marcus.se.net/obsidian-plugin-docs/editor

Another page states that everything is v6
https://marcus.se.net/obsidian-plugin-docs/editor/extensions
Is the notice outdated? can be removed?

Looks like the official docs have the same ambiguity:

https://docs.obsidian.md/Plugins/Editor/Editor
https://docs.obsidian.md/Plugins/Editor/Editor+extensions