XMLHttpRequest POST unrecognized selector exception

I'm currently writing an application requiring JSON data to be sent to a web service using HTTP's POST feature. However, when submitting the data using XMLHttpRequest I get a red box and the following error is displayed in Xcode's console:
[error][tid:com.facebook.React.BridgeMethodQueue][RCTBridge.m:1449] Exception thrown while invoking queryData on target <RCTDataManager: 0x171a8320> with params (
http,
    {
    data = "{\"MACAddress\":\"00:13:43:0c:20:6e\",\"SoftwareRevision\":\"2885\",\"HardwareRevision\":\"2\",\"WaitingTimeColdStart\":\"30\",\"WaitingTimeWarmStart\":\"10\",\"TimeDelayColdStart\":\"30\",\"TimeDelayWarmStart\":\"30\",\"TemperatureDropA\":\"0\",\"WaitingTimeB\":\"7\",\"WaitingTimeC\":\"4\",\"MotorA\":\"3.0\",\"MotorB\":\"2.0\",\"MotorC\":\"0.5\",\"TemperatureDropBColdStart\":\"9\",\"TemperatureDropBWarmStart\":\"5\",\"ColdBurnOffDetectionTime\":\"60\",\"ColdBurnOffDetectionTemperature\":\"3\",\"WarmBurnOffDetectionTime\":\"180\",\"WarmBurnOffDetectionTemperature\":\"25\",\"DoorOpenTime\":\"20\",\"MotorCurrentLimit\":\"600\",\"ThermalElementRMin\":\"2.0\",\"ThermalElementRMax\":\"30.0\",\"ThermalElementRCurrent\":\"65535000.0\",\"CyclesOfOperation\":\"14\",\"BatteryVoltage\":\"2.9065\",\"MaximumBoardTemperature\":\"34.556\",\"MaximumFireRoomTemperature\":\"20.0\",\"RecordDate\":\"2015-07-06T13:05:22.758Z\"}";
    headers =         {
        connection = close;
        "content-length" = 804;
        "content-type" = "application/json";
    };
    method = 1;
    url = "https://webservice.example.com:4443/records/00:13:43:0c:20:6e";
},
159
): -[__NSCFNumber length]: unrecognized selector sent to instance 0x171aaa40

I have used the following source code for creating and submitting the HTTP request:
var httpOperator = new XMLHttpRequest();

httpOperator.onreadystatechange = function()
{
	if (httpOperator.readyState !== XMLHttpRequest.DONE)
	{
		return;
	}

	if (httpOperator.status === 200)
	{
		onFullfilled();
	}
	else
	{
		onRejected(httpOperator.statusText);
	}
};

httpOperator.open(this.HTTPOperationType, this.URL, true);

httpOperator.setRequestHeader("Content-type", "application/json");
httpOperator.setRequestHeader("Content-length", this.DataToTransmit.length);
httpOperator.setRequestHeader("Connection", "close");

httpOperator.send(this.DataToTransmit);

Can you please wrap your code in snippets for readability sake? (tripe `) :)

Sorry, copy&paste error.

I think the issue is that contentLength needs to be a string, so "804", not 804.

Thanks a lot. That worked. I'm closing the issue.


apk update conflicts with seccomp for alpine:edge

$ sudo rkt run --dns <IP_ADDRESS> --insecure-options image \
    docker://alpine:edge \
    --exec /bin/sh -- -c "apk update"
[174135.789209] alpine[5]: Bad system call

Most likely, this is due to:
https://git.alpinelinux.org/cgit/apk-tools/commit/?id=72b878e655
While likely an Alpine Linux issue, users will probably perceive it as "rkt is broken for Alpine" because it works in Docker 1.12.6:
$ sudo docker run -ti --rm alpine:edge /bin/sh -c "apk update"
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
v3.5.0-3581-g4f34754ccb [http://dl-cdn.alpinelinux.org/alpine/edge/main]
v3.5.0-3581-g4f34754ccb [http://dl-cdn.alpinelinux.org/alpine/edge/community]
OK: 8261 distinct packages available

Environment

rkt Version: 1.25.0
appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.10.6-200.fc25.x86_64 x86_64
--
NAME=Fedora
VERSION="25 (Twenty Five)"
ID=fedora
VERSION_ID=25
PRETTY_NAME="Fedora 25 (Twenty Five)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:25"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=25
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=25
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
--
systemd 231
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

I am a bit confused because /proc should be already provided to stage2 apps and because whitelisting mount results in a similar failure:
$ sudo rkt run --dns <IP_ADDRESS> --insecure-options image     docker://alpine:edge --seccomp mode=retain,@rkt/default-whitelist,mount    --exec /bin/sh -- -c "apk update"
[ 1009.029542] alpine[5]: fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
[ 1010.047881] alpine[5]: fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
[ 1010.287397] alpine[5]: v3.5.0-3602-g019e6343e3 [http://dl-cdn.alpinelinux.org/alpine/edge/main]
[ 1010.287755] alpine[5]: v3.5.0-3581-g4f34754ccb [http://dl-cdn.alpinelinux.org/alpine/edge/community]
[ 1010.287962] alpine[5]: OK: 8261 distinct packages available
[ 1010.294333] alpine[5]: Bad system call

I guess there is something more involved in here, and perhaps alpine detection logic is missing our case somehow.

@lucab, I used strace -f apk update 2>&1 | sed -n -e '/(/s/(.*$//p' | sort | uniq to get a list of the syscalls for Alpine 3.5 and Edge, and here's the diff:
16a17
> mkdir
17a19
> mount
32a35
> statfs
33a37
> umount2

So umount2 was missing too. Sure enough, including it fixes the problem:
$ sudo rkt run --dns <IP_ADDRESS> --insecure-options image \
    docker://alpine:edge \
    --seccomp mode=retain,@rkt/default-whitelist,mount,umount2 \
    --exec /bin/sh -- -c "apk update"
[260851.708160] alpine[5]: fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
...

The detection logic is definitely missing rkt's case somehow (though presumably not Docker's).

@tjdett thanks for the followup! Mind reporting this to apk upstream to get the detection logic improved?

@lucab Bug logged with Alpine:
https://bugs.alpinelinux.org/issues/7162

The upstream bug has now been fixed/closed (via commit).
Presumably the next alpine release should fix this!


Now builds for both Firefox and Chromium

Related Issue (if any)
No open issue
Describe the add-ons or changes you've made
Added support for Firefox with this PR and updated all packages to the latest versions without breaking the extension.
Just like how it is mentioned in the documentation, to build the Chromium extension you need to run this - npm run build
For Firefox you just run this - npm run buildFF
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
Tested the Firefox build on their stable build v103.0 (64-bit)
Checklist:

[x] My code follows the "contribution guidelines" of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

Related Issue (if any)
No open issue
Describe the add-ons or changes you've made
Added support for Firefox with this PR and updated all packages to the latest versions without breaking the extension.
Just like how it is mentioned in the documentation, to build the Chromium extension you need to run this - npm run build For Firefox you just run this - npm run buildFF
Type of change

[ ]  Bug fix (non-breaking change which fixes an issue)
[x]  New feature (non-breaking change which adds functionality)
[ ]  Code style update (formatting, local variables)
[ ]  Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x]  This change requires a documentation update

How Has This Been Tested?
Tested the Firefox build on their stable build v103.0 (64-bit)
Checklist:

[x]  My code follows the "contribution guidelines" of this project.
[x]  I have performed a self-review of my own code.
[x]  I have commented my code, particularly wherever it was hard to understand.
[x]  My changes generate no new warnings.
[x]  Any dependent changes have been merged and published in downstream modules.

Thanks!
Will review soon.

Issue #25 will be faced here btw

Hey @anjannair,
I'm aware of the issue #25, but I'm facing different issues.
I faced the 2 following issues in this PR:
MacOS Mozilla Firefox (104.0.1)

The extension closes after clicking on the upload button.
After clicking on the upload button it opens the file selector window (not shown in the below gif because it's not covering the whole window), and after that It's not even publishing to IPFS (checked on web3.storage dashboard).

Horizontal and vertical scroll bar.

What is your browser version? can you show a working gif?

@akhileshthite the main branch only has the Firefox build ready. The firefox branch however is a few commits ahead of the main branch consisting of the pop up solution. Do you want me to merge it into my main branch? Or do you want to test it before I merge it with my main branch

@akhileshthite the main branch only has the Firefox build ready. The firefox branch however is a few commits ahead of the main branch consisting of the pop up solution. Do you want me to merge it into my main branch? Or do you want to test it before I merge it with my main branch

I'm dealing with this extension crashing issue (latest dscan update without your firefox branch solution) on firefox browser only, and not on chromium browsers (chrome, brave, etc.).
Are you facing this #25 issue on chromium browsers? If so, then please mention your browser version and screen recording.

I tested your firefox branch, we don't want the #25 fix for normal build npm run build (chromium browsers).

Even on the firefox, I feel like opening a new window after clicking on the launch button would lead to a bad UX, can you try to fix the issue by keeping the old UI?

Don't change the naming.

Let's keep a single main branch, so it would be easier for development and docs.

Can you follow conventional commits guidelines as mentioned in the CONTRIBUTING.md.

@akhileshthite the main branch only has the Firefox build ready. The firefox branch however is a few commits ahead of the main branch consisting of the pop up solution. Do you want me to merge it into my main branch? Or do you want to test it before I merge it with my main branch

I'm dealing with this extension crashing issue (latest dscan update without your firefox branch solution) on firefox browser only, and not on chromium browsers (chrome, brave, etc.).
Are you facing this Extension loses focus on file/folder upload #25 issue in chromium browsers? If so, then please mention your browser version and screen recording.
I tested your firefox branch, we don't want the Extension loses focus on file/folder upload #25 fix for normal build npm run build (chromium browsers).
Even on the firefox, I feel like opening a new window after clicking on the launch button would lead to a bad UX, can you try to fix the issue by keeping the old UI?

Don't change the naming.

Let's keep a single main branch, so it would be easier for development and docs (merge your firefox with your main branch, so you don't need to make another PR for this issue).
Follow conventional commits guidelines as mentioned in the CONTRIBUTING.md.

@anjannair ?

@akhileshthite please give me a day or 2 to respond. Am in the middle of something hence can't reply

@akhileshthite please give me a day or 2 to respond. Am in the middle of something hence can't reply

Sure.

@akhileshthite honestly I just thought I'd help and contribute. I tried recording my screen but Linux breaks the recording every time. I'll instead type out the following - Open Chrome (the latest stable version), try to upload a file/ folder and get the link.
You'll understand what I am talking about.
Secondly, I didn't understand what you meant by this. You don't want to fix the out-of-focus issue for Chromium users????
Third, there is no solution to fix the out-of-focus issue without changing the UI. If you want to keep it the same you will face the before-mentioned issue.
If you want to fix these issues I believe my PR should be the way to go. If you still believe otherwise please feel free to close this pr 👍🏽

@akhileshthite honestly I just thought I'd help and contribute. I tried recording my screen but Linux breaks the recording every time. I'll instead type out the following - Open Chrome (the latest stable version), try to upload a file/ folder and get the link.
You'll understand what I am talking about.
Secondly, I didn't understand what you meant by this. You don't want to fix the out-of-focus issue for Chromium users????
Third, there is no solution to fix the out-of-focus issue without changing the UI. If you want to keep it the same you will face the before-mentioned issue.
If you want to fix these issues I believe my PR should be the way to go. If you still believe otherwise please feel free to close this pr 👍🏽

Google Chrome Latest Version 106.0.5249.91, it works ideally on Mac and Windows OS. Also, works ideally on brave, opera, and edge browsers.
Soon I'll test it on Linux OS, if you're dealing with any problems "YOU SHOULD" show them here. Your screen recorder is not working is not my problem, record it using a phone or something.
Please mention "every" detail in your PRs or issues. In your #25 issue, you didn't mention anything about browser, its version or OS. It's a really bad open-source practice.

@akhileshthite the main branch only has the Firefox build ready. The firefox branch however is a few commits ahead of the main branch consisting of the pop up solution. Do you want me to merge it into my main branch? Or do you want to test it before I merge it with my main branch

I'm dealing with this extension crashing issue (latest dscan update without your firefox branch solution) on firefox browser only, and not on chromium browsers (chrome, brave, etc.).
Are you facing this Extension loses focus on file/folder upload #25 issue in chromium browsers? If so, then please mention your browser version and screen recording.
I tested your firefox branch, we don't want the Extension loses focus on file/folder upload #25 fix for normal build npm run build (chromium browsers).
Even on the firefox, I feel like opening a new window after clicking on the launch button would lead to a bad UX, can you try to fix the issue by keeping the old UI?

Don't change the naming.

Let's keep a single main branch, so it would be easier for development and docs (merge your firefox with your main branch, so you don't need to make another PR for this issue).
Follow conventional commits guidelines as mentioned in the CONTRIBUTING.md.

I've explained clearly here.
Your current PR is changing the whole UI/UX of the extension for all browsers (which is poor).


ICMP protocol missing

Core low-level protocol needed for some basic functionality.

The basics of this have been implemented.


Implement menu hoisting for select

Context
In select's shadow root, we use <mwc-menu> this creates an <mwc-menu-surface> which creates a surface that is position:absolute. This gives the correct behavior of menu sticking and following around with the select.
Problem
The problem with this is that the stacking context of menu-surface is its current position in the tree. This means if there is an element after it in the tree with position: absolute, then it will very likely cover the element. If the menu is placed inside of an element with position: absolute or position: fixed then the stacking context of the menu-surface is now placed inside that element.
Example / Repro
lit playground
Workaround
In most cases the workaround is to add fixedMenuPosition to mwc-select. This will make the menu position: fixed which creates a window-level stacking context thus positioning it above all position: absolutes in the document.
Though this means if the user scrolls while the menu is open, then the menu will not "follow" the select on the page since fixed is relative to window not a relatively position element.
Proposed fix
The "Correct" fix for this is that mwc-menu should be position:absolute and placed as the last element in the document. This is what we call "hoisting the menu (to document.body)".
It does not make sense for the user to have to do this themselves and we don't want to do this within mwc-select itself as we don't want to step outside the lit WC rendering system as we do not know what renderers mwc-select will be placed in.
We should create a menu-hoisting / menu-requesting system. The real problem is how to handle templating, and css custom properties. e.g. something we napkined at the office
<body>
  <nav>
    <mwc-overlay-scope>
      <nav-item>...</nav-item>
      <nav-item>...</nav-item>
      <nav-item>...</nav-item>
      <nav-item>...</nav-item>
      <nav-menu title="...">
        <!-- without lit-html -->
        <mwc-menu id="navMenu"></mwc-menu>
    </mwc-overlay-scope>
  </nav>
  <mwc-overlay-scope>
    <div id="application">
      ...
      <!- with lit-html -->
      <mwc-select @input=${...} label="fruits" .renderer=${(node: HTMLElement) => {
        // import {html, render} from 'lit';
        const template = html`
          <mwc-list-item value="NONE" @click=${...}></mwc-list-item>
          ${items.map(item => html`
            <mwc-list-item ?selected=${item.selected} value=${item.value}>
              ${item.text}
            </mwc-list-item>
          `)}
        `;
      }}>
      </mwc-select
    </div>
  </mwc-overlay-scope>

  <script type="jsx">
    // or innerHTML or whatever rendering system you choose
    import {render} from 'react-dom';
    window.navMenu.renderer = async (node) => {
      const template = (
        <>
          <ListItem>...</ListItem>
          <ListItem>...</ListItem>
          <ListItem>...</ListItem>
          ...
        </>
      );

      render(template, node);
    }
  </script>
</body>

where the template of menu-overlay-scope is:
<style>
  :host {
    display: contents;
  }
</style>
<slot></slot>
<!-- some abstract surface that is used across tooltip and menus etc -->
<mwc-surface>
  ${callChildRenderer()}
</mwc-surface>

suggestion (as in #2409)
align with native select behavior -

menu is fixed
opened menu inert the outside context
user can't interact with the rest of the tree until menu is close

it is partially a modal like there's an invisible scrim underlying the menu
reasons -

aligns with native select

prevents adding - knowledge dependent - hoisting system for users to work against

bonus: aligns with angular material select

Think this is obsolete with M3 now


Add rough ideas on guidelines

Idk what I'm doing

@shawnmusgrave blah

@shawnmusgrave

[ ] do this thing

[ ] do this other thing

I'll try to

[] do something else


fix: Resolve incorrectly formatted validation objects and rename keys where appropriate

:tada: This PR is included in version 1.3.0-dev.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Steam patch doesn't work after Steam Client update on October 25th

After steam client update on October 25th, steam-patch does not apply icons and TDP limit in gamescope-session anymore.
ROG Ally buttons keep working as expected.

Yea this was the behaviour in the steam beta a few days ago, it looks like valve has pushed the beta to stable

Hey @dovcharov @ripplingsnake, could you please check this version?
https://github.com/Maclay74/steam-patch/actions/runs/6725563442
You'd have to manually download it and replace file steam-patch in your home/gamer/steam-patch folder.

Thanks will do !MarcOn 1 Nov 2023, at 23:09, MIkhail Kozlov @.***> wrote:
Hey @dovcharov @ripplingsnake, could you please check this version?
https://github.com/Maclay74/steam-patch/actions/runs/6725563442
You'd have to manually download it and replace file steam-patch in your home/gamer/steam-patch folder.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Works like a charm! The steam logo is überkool ;)
Tested after suspend (n-keys lost) and 2nd suspend (keys recovered)... works great!
Thanks a lot Maclay74!!!

Unfortunately since a few hours ago, it enters a steam update loop while gamescope-session. I'll report a bug.

Yea same here update loop and only way to stop it is disable steam patch


CMake modernization: add Backward::Interface and Backward::Object targets

This PR should make it easier to use the backward.cpp file in downstream projects. As documented in the README, with this PR there are now three targets:

Backward::Interface is an interface target that brings compiler definition
flags, include directory, and external libraries. This is all you need to use
the backward.hpp header library.
Backward::Object brings Backward::Interface and backward.cpp as an
OBJECT CMake library. This target cannot be exported, so it is not
available when Backward is used via find_package.
Backward::Backward brings Backward::Interface and backward.cpp as
either STATIC or SHARED library (depending on the BACKWARD_SHARED
option). This target is exported and always available, however note that the
linker will not include unused objects from a static library, unless the
-Wl,--whole-archive option (or similar) is used.

This PR marks the add_backward target as deprecated and removes the ${BACKWARD_ENABLE} variable.
Before this PR, using the Backward::Backward target was not easy and consistent:

the BackwardConfig.cmake defined the target such that its interface had only the things needed to use backward.hpp (i.e. BACKWARD_INCLUDE_DIRS, BACKWARD_DEFINITIONS, BACKWARD_LIBRARIES)
the main CMakeLists.txt file defined the target such that it contained even backward.cpp as either STATIC or SHARED library
linking to a static library libbackward.a does not have the desired effect, unless the
-Wl,--whole-archive option (or similar) is used (the linker discards unused objects from a static library)

Thank you for the fine work.


After Symfony Kernel reboot - Doctrine EventManager keep old Container

What are you trying to achieve?
I have case, when my service have some state, like MemoryStorage collect some data and I want to test what it collects. This MemoryStorage filled by some listeners, subscribed to Doctrine events.
What do you get instead?
My MemoryStorage empty.
Here is reproduce test https://github.com/ewgRa/symfony-standard/blob/codeception-bug-with-container/tests/functional/ContainerCest.php .
tryToTest failed, and tryToTestProof show the reason why it fail.
Problem that doctrine.orm.entity_manager is persistent service and it have EventManager, that actually ContainerAwareEventManager, that store container.
When Symfony module reboot kernel, it create new Container, but since doctrine is persistent, EventManager continue keep old container.
As a result Doctrine events work with its own container, while $I->grabService(...) work with another container.
Reproduce:
git clone git@github.com:ewgRa/symfony-standard.git
cd symfony-standard/
git checkout codeception-bug-with-container
composer install
vendor/bin/codecept run
So, is it feature? Or bug? Looks like 100% bug. Possible solution is update EventManager container also on kernel reboot. Or another solution - unpersist doctrine.
At least this must be mentioned somehow in documentation. Also some "I make service persistent, and it not works" issues can be related to this.

The same applies to Middlewares that have injected some Symfony services...


New Rule: UnnecessaryRequireNotNull

Expected Behavior of the rule
Would there be any appetite for a new UnnecessaryRequireNotNull rule?
This would be similar to UnnecessaryNotNullOperator but it would flag calls to requireNotNull  with a non-nullable parameter.
// non compliant code
var string = "foo"
println(requireNotNull(string))

// compliant code
var string : String? = "foo"
println(requireNotNull(string))

Context
We have seen optional field become required after refactorings, leaving behind unnecessary calls to requireNotNull.
We have built a custom rule to detect these cases and we would like to contribute it back.

I think this would be a great addition, and should also check for the same case with checkNotNull

I second this. This rule would be a great addition to detekt.
Shall the rule be called UnnecessaryNotNullCheck?
@pbreault may I ask you to take a stab at this rule?

I think a single UnnecessaryNotNullCheck  rule that encompasses checkNotNull and requireNotNull makes sense. Definitely more future-proof. I'll take a stab at it.


Fix for #251 (RqWithHeaderTest tests nothing)

Fix for https://github.com/yegor256/takes/issues/251 RqWithHeaderTest tests nothing)

Replaced Host header with X-Custom-header

@cyberone Many thanks, I will find someone to review it before we merge

@pinaf it's yours, please review

@rultor merge
@cyberone looks good. thanks!

@rultor merge
@cyberone looks good. thanks!

@pinaf Thanks for your request. @yegor256 Please confirm this.

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 12min)

@yegor256 this was merged 15 days ago :(

@pinaf it's marked as "invalid", see http://www.teamed.io/policy.html#13

@yegor256 I see. Why was it assigned to me?

@pinaf good question. it's our mistake. we'll try to avoid this in the future and will assign small pull requests directly to project architect, without a code reviewer.

@yegor256 ok got it. thanks.


feat: support Ed25519 publicKeyJwk

This PR adds support for Ed25519 publicKeyJwk.
Almost exactly 1 year after https://github.com/decentralized-identity/did-jwt/pull/160 😅

Thank you @mirceanis for merging it :)

Now I'm keeping an eye on https://github.com/decentralized-identity/did-jwt-vc/pull/108 😉


Remove "--dump-skp-on-shader-compilation" and all related code in engine and tool

We implemented --dump-skp-on-shader-compilation for customer: dream. Once they stop using it, we should remove it from our codebase, because as implemented it is essentially unusable. There's no documentation, and it is entirely unintuitive how to actually obtain the files to which it refers.
We may in due course want to create other mechanisms e.g. to save the SKPs for expensive frames from the DevTools, or similar, but that is a separate issue.

@Hixie is there a tracking issue somewhere for them removing it?  I only see it referenced in third_party right now, unless I'm missing it.

I have no idea if they plan to stop using it. Eventually, though, it will become unnecessary because we won't need shader warmup, at which point we can ask them to remove it, then this will become relevant.


Increasing image dimensions beyond 1024

Is this possible? Currently, typing over 1024 (eg. 2048) simply resets it to the max dimensions after clicking "re-light".

I think the issue with changing dimensions currently is that the model used is SD15 which caters towards the 512px -1024px width/height size.
I was able to bypass the limits by changing the gradio python files:
image_width = gr.Slider(label="Image Width", minimum=256, maximum=1344, value=512, step=64)
image_height = gr.Slider(label="Image Height", minimum=256, maximum=1344, value=640, step=64)
While it did let me generate bigger images, certain ratios created a lot of 'double pictures'.


Document DEV_MODE & maybe make it default on localhost

https://github.com/Laravel-Backpack/basset/blob/cf6a3b3a13d0b66b272242068d1df765209dd5d7/src/config/backpack/basset.php#LL5C24-L5C39
We need to document this super important bit!

I'm wondering... should we make BASSET_DEV_MODE default to true on localhost? 🤷♂ Isn't this something most devs will need to do, anyway?

I'll close this one in favor of, #54 and #55 👌


Use the most up-to-date analysis for binary to source class name lookup

This PR fixes #1268
Cause
During Dependency Extraction, internalBinaryToSourceClassName is used to map binary class name to source class name. It is constructed at the first cycle. Hence in subsequent cycles, it is outdated. This results in missing internal member reference dependency between a.Use pkgName.Test.
To fix it, we rebuild lookup using the most up-to-date analysis.
Other changes
This PR also removed internalSourceToClassNamesMap. It is currently not used, but it has the same staleness problem as internalBinaryToSourceClassName. So might as well remove it to prevent someone from accidentally using it in the future.
empty-package test is also modified to assert an exact dependency between a.Use pkgName.Test must exist. Running the modified empty-package on current latest develop branch commit now results in test failure.
Why empty-package erroneously passed on zinc repo
The complier bridge did recognize a dependency between a.Use and pkgName.Test exists. However, since internalBinaryToSourceClassName was stale, zinc failed to map pkgName.Test back to its .scala source file, and instead misclassified the dependency as a external library dependency. This can be observed in the zinc test log:
[debug] previous = Stamps for: 4 products, 2 sources, 1 libraries
[debug] current source = Set(${BASE}/pro/Use.scala)
[debug] Invalidating '${BASE}/pro/target/classes/pkgName/Test.class' because pkgName.Test$ came from analysis Analysis: 2 Scala sources, 4 classes

Then in invalidateInitial, all sources that depends on pkgName.Test library is invalidated via val byLibraryDep = changes.libraryDeps.flatMap(previous.usesLibrary)

TODO:

[ ] The edited scripted test passes in current latest 'develop' commit

In fact the checkDependencies was not used correctly in the first place.

Even if it is used correctly, the test still passes in current latest 'develop' commit...

I feel slightly nervous about deleting things, but hopefully this is ok.

Here's my chain of thought
The only case for problem to emerge is for  incHandlerOpt to be None while internalBinaryToSourceClassName lookup is still needed. For Scala compilation,  incHandlerOpt is never  None. For Java compilation,  incHandlerOpt is None, but internalBinaryToSourceClassName is called in one place only:
// JavaAnalyze.scala
(getMappedSource(fromBinaryName), getMappedSource(onBinaryName)) match {
  case (Some(fromClassName), Some(onClassName)) =>
    trapAndLog(log) {
      analysis.classDependency(onClassName, fromClassName, context)
    }
  case (Some(fromClassName), None) =>
    trapAndLog(log) {
      val cachedOrigin = classfilesCache.get(onBinaryName)
      for (file <- cachedOrigin.orElse(loadFromClassloader())) {
        val binaryFile: Path = remapClassFile(file)
        analysis.binaryDependency(
          binaryFile,
          onBinaryName,
          fromClassName,
          source,
          context
        )
      }
    }
  case (None, _) => // It could be a stale class file, ignore

In the above code, analysis.binaryDependency calls internalBinaryToSourceClassName, however it only happens when getMappedSource(onBinaryName) is None, which means the source file does not exist anyways.


Port to wasm32-wasi

This is an experiment if nothing else, I haven't event tested it yet. So feel free to complete ignore.

This uses the unstable wasi_ext feature, so don't merge this :)

Closing this for now as it was never really worked.


doc: Specifies required properties

This is for #69
Specifies properties dpid and in_port as required into the openapi file.
Still need to validate according to the OpenAPI specification, waiting for openapi-core and the validator decorator to be moved to kytos-ng core.

Yes @viniarck, you are right.


Load WCS data

While we get WMS images as layers, we need to get WCS layers as geojson that we can process in the frontend to calculate analytics on

Could we use or get inspiration from https://github.com/EOX-A/libcoverage.js ?


[Question]: Defining Prompt Template for OpenAIAgent

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
How to use pormpt template in OpenAI agent
agent = OpenAIAgent.from_tools(tool_spec, llm=llm, verbose=True)
agent.get_prompts()

>> []

from llama_index.core import PromptTemplate

REACT_SYSTEM_PROMPT = PromptTemplate(react_system_header_str)
agent.update_prompts({"agent_worker:system_prompt": REACT_SYSTEM_PROMPT})

>>  for module_name, sub_prompt_dict in sub_prompt_dicts.items():
     [74](file:///C:/Users/anant/miniconda3/envs/super/Lib/site-packages/llama_index/core/prompts/mixin.py:74)     if module_name not in prompt_modules:
---> [75](file:///C:/Users/anant/miniconda3/envs/super/Lib/site-packages/llama_index/core/prompts/mixin.py:75)         raise ValueError(f"Module {module_name} not found.")
     [76](file:///C:/Users/anant/miniconda3/envs/super/Lib/site-packages/llama_index/core/prompts/mixin.py:76)     module = prompt_modules[module_name]
     [77](file:///C:/Users/anant/miniconda3/envs/super/Lib/site-packages/llama_index/core/prompts/mixin.py:77)     module.update_prompts(sub_prompt_dict)

ValueError: Module agent_worker not found.

With this i also have some additional questions:

I noticed that OpenAIAgent is faster then ReActAgent
Secondly using PromptTemplates provided more controlled and consistent output compared to system prompts

@anantgupta129 there is no prompt template for an openai agent
It is just sending the chat history and list of tools through the openai client.
So in that sense, the only prompt is the chat history, and the schemas of tools

hey @logan-markewich  follow-up questions

is there plan to integrate prompt templates with OpenAI agents
what is the difference between OpenAI agent and ReAct agent & which to use
using PromptTemplates provided more controlled and consistent output compared to system prompts
in case of agent AzureOpenAI is very slow as compared OpenAI, there is about 10x delay in response generation. I have tried with both ReActAgent & OpenAIAgent

llm = AzureOpenAI(
    model=os.getenv("AOAI_COMPLETION_MODEL"),
    deployment_name=os.getenv("AOAI_DEPLOYMENT_NAME_COMPLETION"),
    api_key=os.getenv("AZURE_OPENAI_API_KEY"),
    azure_endpoint=os.getenv("AOAI_ENDPOINT"),
    api_version=os.getenv("AOAI_API_VERSION"),
)

@anantgupta129 Have you tried this?


Document how to (re)build jni native library in lookup exception

To run this test again: /usr/local/google/home/dacoharkes/flt/engine/flutter/bin/cache/dart-sdk/bin/dart test test/jni_array_test.dart -p vm --plain-name 'Java string array'
00:02 +5 -24: test/jni_object_test.dart: Passing strings in arguments [E]
  Invalid argument(s): Failed to lookup symbol 'GetAccessors': build/jni_libs/libdartjni.so: undefined symbol: GetAccessors
  dart:ffi                                                       DynamicLibrary.lookup
  package:jni/src/third_party/jni_bindings_generated.dart 70:72  JniBindings._GetAccessorsPtr

This should ideally tell me what command I need to run to make this error go away.
We'd probably want to use:

https://github.com/dart-lang/native/issues/228

Alternatively, we'd have to wrap all calls to JniBindings, which is a bit unwieldy.
Note the command to run jni$ dart bin/setup.dart or jni$ flutter pub run jni:setup.

Will be addressed when we start using build hooks!


auto-detect default branch name in [bitbucketpipelines gitlab travisphpversion]

refs #5215
In some cases, we can use the handy HEAD trick to query whatever the default branch is with one HTTP call. Sometimes we can't, so we have to use another method to find out the default branch using another network request. One option is we can make an API call to github/bitbucket/gitlab. The other is we can shell out to git and call git ls-remote --symref https://github.com/badges/shields.git HEAD. Inevitably there are some tradeoffs to consider. Not all of them necessarily come into play in this PR, but I'm going to list them all anyway as this is something we will have to think about more in future.
In general, it is best to make an API call if we can because:

An HTTP API gives us nice error codes (e.g: 404 = repo not found, 403 = private repo, etc)
An HTTP API call can be easily mocked under test with nock. The request made by git is harder to mock
If we need to support private repos/self-hosting, the available credentials might influence what we can use. For example, git only allows HTTPS basic auth or SSH key, but if we only hold an API token for self-hosting users, we can't authenticate with either of those methods for private repos.
A JSON response can be more reliably parsed than the text output of git
This probably varies a bit, but in general it seems to be faster to use a JSON API than git

There is one advantage of using git directly though:

If we use git, we don't need to worry about an API rate limit. This makes it more suitable if we don't have API credentials, or if we would be likely to exceed a rate limit.

So.. the upshot of that is I've chosen:

Bitbucket pipelines: Call the BitBucket API
Gitlab Pipelines: Shell out to git
Travis PHP Version: Call the Github API

In slightly more detail:
BitBucket pipelines
BitBucket's API allows us to pass a ref_type

The following reference types are supported:

branch
named_branch
bookmark
tag

As far as I can tell, none of them allow us to pass HEAD as a ref, so this now makes two API calls - fairly straightforward implementation. Making two API calls does impact performance but both the calls are pretty quick.
Gitlab pipelines
With GitLab we don't have an API token (or a pool of them), which is why pipelines is the only gitlab badge we support. This somewhat ties our hands. I've implemented a general helper which uses simple-git to call ls-remote (although gitlab pipelines is the only service which uses it). It requires git to be installed (I think the heroku buildpack does have this. We'll find out when we get this on staging). Again, there is some performance impact as we're now making two network calls but its far from our worst performing badge. If/when we implement a proper suite of gitlab badges using their API it would probably be good to review this approach.
Travis PHP Version
Travis PHP version calls the travis-ci .org API, which I think means the source repo is hosted on GitHub, so I've used a call to the GitHub API here (AFAIK only travis.com supports bitbucket so this is something we would need to bear in mind if we generalised). In the abstract, adding a call to the Github API isn't the end of the world - as APIs go its pretty fast. Unfortunately, the Travis PHP Version badge already makes two API calls and this brings us up to three, which is a bit rubbish.
To offset this, I've done a bit of acrobatics to fire off two of the requests at the same time to keep the performance within reasonable bounds. I think we could probably look at caching the PHP versions in Redis instead of fetching it on every request, but this solution keeps the performance in check for now.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against 2cd7cbe3f7c67664e9e29fa116229f5032dabf20

Thanks for putting this together! I'm hoping to carve out some time to dig through this over the weekend.

Again, there is some performance impact as we're now making two network calls but its far from our worst performing badge

Besides the extra networking call, any concerns and/or config we may need to account for process spawning associated with this? (which I presume is happening somewhere)

any concerns and/or config we may need to account for process spawning associated with this?

Hmm. Interesting question. I hadn't really given much thought to the gitlab badge, which invokes git from JS. I guess it is going to spawn an OS process for each badge call which could potentially stack up. I'm not really sure if that's something we need to worry about or not.. do you have any more detailed thoughts on it? Its pretty standard practice in most languages that every request spawns its own process, but then I don't reckon we'd be serving the level of traffic we do off just 4 servers in most languages.
For the ones that just make 2 API calls, its javascript, so its single thread and promises. Although we try and avoid them, we've already got a few services that make more than one API call (or can do) e.g: matrix, nuget, f-droid, codeclimate. Its basically the same setup here.
If we're not convinced on the gitlab approach but we're happy with the other two, I can split this up into multiple smaller PRs if needed.
Btw, I totally forgot to check this on a review app after I initially submitted the PR, but I've just set up https://shields-staging-pr-5241.herokuapp.com/ and the gitlab badge does work, which is useful.

I'm not really sure if that's something we need to worry about or not.. do you have any more detailed thoughts on it?

I don't have anything concrete at the moment, but I do think that the process spawning (associated memory implications) is a factor we'll need to take into account (especially given our Heroku strategy of horizontally scaled small dynos).
We're not getting a ton of GitLab traffic today because as you noted we only support the one badge today. As such it's unlikely to have any noticeable impact. However, I imagine it could quickly become significant with higher volume badges.

Also, I'm still having my own internal debate to try to make up my mind on whether I think Shields should continue trying to do auto-magic default branch detection for services that require Shields to send them a branch param, but don't provide their own auto-magic solution like GitHub does with HEAD.
On one hand I understand the convenience for users to not have to specify a branch when setting up their badge. OTOH, setting up a given badge is really a one time action for end users (it's not like they have to take action and keep re-specifying their branch every the time the badge is loaded/viewed), but Shields has to do this auto-magic work on every (non-cached) badge request.
For me it's a matter of tradeoffs and weighing the convenience for a user to not have to include a /my-branch when they add their badge to a readme/etc. against the increased workload for the badge servers (extra network calls, process spawning, etc.) and associated code maintenance.

I know there are a couple of conflics on this PR but they are only on package.json/package-lock. I'll deal with resolving them if/when we're happy with the main body of code.

Also, I'm still having my own internal debate to try to make up my mind on whether I think Shields should continue trying to do auto-magic default branch detection for services that require Shields to send them a branch param, but don't provide their own auto-magic solution like GitHub does with HEAD.
On one hand I understand the convenience for users to not have to specify a branch when setting up their badge. OTOH, setting up a given badge is really a one time action for end users (it's not like they have to take action and keep re-specifying their branch every the time the badge is loaded/viewed), but Shields has to do this auto-magic work on every (non-cached) badge request.
For me it's a matter of tradeoffs and weighing the convenience for a user to not have to include a /my-branch when they add their badge to a readme/etc. against the increased workload for the badge servers (extra network calls, process spawning, etc.) and associated code maintenance.

Although we try and avoid them, we've already got a few services that make more than one API call (or can do) e.g: matrix, nuget, f-droid, codeclimate

That's quite true although AFAIK in all of those cases (other codeclimate) the sequential API calls are strictly necessary to get the required data vs. Shields making assumptions/auto-populating a parameter value that the upstream service requires by making multiple networking calls.

This message is a good summary of the trade-offs we have to consider. 👍
In my opinion, making the users specify a branch when setting up their badge is not the end of the world, especially as they'll rarely change the default branch name. It even has the nice side effect of making badges paths more consistent. I find it suboptimal that we specify most optional elements as query parameters in our badge URLs, but for branches we've historically been using optional path elements.
I don't think we should go down the route of increasing our code complexity. Doing multiple network calls to render our badges makes them less reliable and will impact performance. We've always been careful when implementing badges that do multiple network calls and as mentioned by @calebcartwright it's generally been as a last resort if we can't get the information by any other means or if the parameter value is not easily "guessable" by the user.

Just to clarify, what's your proposed way forward?
Are you saying we should:

Convert branch to a required param on these badges and break badges for existing users who are using Bitbucket Pipeline, Gitlab Pipeline and Travis PHP version without a branch (which is probably most of them).
Leave things as they are (assuming the default branch is called master) for these three services?

My proposed way forward would be something in the middle: make the branch name a required parameter, but add a service redirect that assumes that the default branch is master to avoid breaking existing badges.

My proposed way forward would be something in the middle: make the branch name a required parameter, but add a service redirect that assumes that the default branch is master to avoid breaking existing badges. What do you think?

That's what I had in mind as well

Two follow-up questions:

Do you think we should do that in all three of these cases, or do you think we should only do it on GitLab/BB (where we have to increase the render time of the badge in order to work out the default branch) but audo-detect on TravisPHP (where we can add the extra call without having to increase render time because we can issue two requests at once)?

We touched on this slightly in #5215 , but in your view, what is the difference between:

branch is not a required param. If you don't specify it, we'll assume master
branch is a "required" param (but if you don't specify it we'll assume master for backwards-compatibility via a redirect - don't tell anyone though :wink: )

I'm not necessarily against this approach, but I'm interested in understanding your thinking.

We touched on this slightly in #5215 , but in your view, what is the difference between:

Fair question. While I agree that from an end-user perspective the result is essentially the same, the motivation and justifications are different. Philosophically I think that our badge route parameters should require the same data points that the upstream service/platform requires, and option 2 moves us to that end.
Yes, we'd have to do the redirect thing because we don't have a time machine and can't break existing badges, but we're still moving to a point where our set of required params match the upstream set.
If anyone "discovers" the master branch assumption, IMO it's easier to explain that we had to do so with a redirector to avoid breaking a massive set of badges vs. it being a strategic decision that Shields is continuing to auto-assume master. The redirect behavior will also impact existing badges in the sense that they'll be ever so slightly slower due to the redirect, so there's motivation for existing users to update their badge routes (especially if/when folks start renaming their default branches).
The second option would presumably help avoid accruing any more "debt" of new users leveraging the assumed branch behavior, at least relative to the first option.
Lastly, I think the second option helps avoid any future debates with other services, as it takes the sails out from the "well the XYZ service class route has an optional param with an assumed default even though XYZ requires it"

Do you think we should do that in all three of these cases

I'd vote for all three for many of the same reasons as above.

I realize that one impact of the approach I'm suggesting (not assuming/detecting a default branch) means that users that change their default branch name will likely see broken badges and have to correct their badge routes.
I'm quite sure there will be some folks that will be angry/irritated by that, and can understand that initial frustration, but still feel this is the right way to go. It'll be a minor, one-time nuisance, but it's not Shields job IMO to assume/determine values for required params on behalf of users and the drawbacks of attempting to do so just far outweigh the pros.

Also, if we do end up going the route of auto-detecting branches then I do think the code and changes here are probably good to go. Would just want to keep an eye on the resource utilization on Heroku for a bit post-deployment

Lots of great points all around! @chris48s thanks for taking on this work!
I think multiple requests are not ideal, but okay in circumstances where it is required to get the information we need, or where it makes the badge drastically easier to use. (Matrix is a good example of that, IIRC.)
A handful of the badges used to invoke a subprocess but I think we've now gotten those down to zero. I do think subprocesses are important to avoid, as it is a very, very easy way to overwhelm the server with a DoS.
If we need to ls-remote would it be worth looking at a pure JS implementation like Isomorphic Git? (Also definitely want to be really careful with sending credentials. I also am not sure if the legacy servers might have private SSH keys on them which could have access to non-public repos.)
In terms of how we handle the defaulting, a redirect will very gently nudge people to the new URLs, mainly because when it's pasted into a browser, you will end up seeing the redirect target. I do think the redirect approach will reduce the number of new repos which will rely on the default. Someday we could deprecate the redirect and replace it with a "please specify a branch" message. Assuming we're not ready now to break existing badges and say, "please specify a branch," I think that'd be my preference.

Yeah I think I will close this and submit a new PR making branch "required" (but not actually required :wink:). While at the moment there are "only" three badges to think about, its not inconceivable we may end up with a full suite of bitbucket or gitlab badges at some later date. If we commit to auto-detect/two requests now, its hard to row back on it later. If we start publicising the existing badge as "requiring" a branch param now we can say its a hard requirement if/when we add more. We could always add a branchless option in future for example if BB/Gitlab allows it to be done in a single query (like GH does), but once it exists its basically impossible to take it away.
The replacement PR will be a lot simpler than this one, but I haven't got time tonight. I'll aim to have a look at the weekend.


AdAttribution tweaks for macOS

Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL: https://app.asana.com/0/856498667320406/1202474256801516
iOS PR:  will follow
macOS PR: https://github.com/more-duckduckgo-org/macos-browser/pull/700
What kind of version bump will this require?: Major
Description:
Added support for async API. Updated tests.

Steps to test this PR:
Test along with macOS attribution PR.

OS Testing:

[ ] iOS
[ ] macOS

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks @samsymons


scroll issue

It use to work fine but after upgrade to RN 0.42.3 scrolling in android stops.
Any help please?

Any help please?

guys anybody working on this component anymore? the scroll is not working at all in iOS or android


 If so, could you produce a conda .yml file and post it here?
Background: we're working on including an environment file for each chapter so that these things can be better encapsulated, particularly where different chapters are using conflicting versions of the same python packages.

Hi @jmason86 thanks for the note and for updating these chapters. Unfortunately, I do not have that environment. Happy to help generate a .yml file that would work, though, if you have suggestions

Cool, thanks! I haven't actually tried to build and run your notebook yet. It may be an easy one. Some of the others I've tried have been really hard which is why I've reached out to everyone. If yours does turn out to be one of the hard ones, I'll post on this issue here to solicit your help and insight. Thanks for your quick response!

Got it - happy to help! Thanks for making this an uncommonly usable resource. We have a new paper coming out in SpWxJ that would make an ideal new chapter for this book, so I'll likely be in touch before long


Formatting for release-process.md

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: via pre-push github hook no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please make sure to document it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please make sure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then make sure to get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it.

See the developer guide for a bit more details.

Codecov Report

Merging #426 (7402411) into main (cd32aae) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #426      +/-   ##
==========================================
- Coverage   70.56%   70.53%   -0.04%
==========================================
  Files          50       50
  Lines        2633     2603      -30
==========================================
- Hits         1858     1836      -22
+ Misses        589      583       -6
+ Partials      186      184       -2

Impacted Files
Coverage Δ

pkg/git/git.go
58.33% <0.00%> (-16.03%)
:arrow_down:

pkg/consoleui/interface.go
0.00% <0.00%> (ø)

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 cd32aae...7402411. Read the comment docs.


Explicitly define dynamic path in 0.9.0?

Hello, I have been using Nuxt to rapidly prototype ideas and I've been really enjoying the simplicity of it. However as of the breaking change to routes in 0.9.0 I am unsure if I can explicitly define my desired path anymore and I fear the simplicity has become somewhat of a limitation without the option for more fine-tuned control.
The examples provided indicate that pages prefixed with an underscore are directly transformed into the path, but what if I wish to have a more complex path regex? Prior to 0.9.0 I had a path along the lines of /(watch|play)/:id, this wouldn't work using the folder structure.
Have I missed some information on this or is this simply no longer possible?

Hi @Kentoss
Thank you for spotting this issue, indeed we did not think of this possibility.
We want to make Nuxt.js as simply as possible but without removing any feature. Anyone looking at a Nuxt project pages/ directory should be able to understand quickly the routes of the project.
Actually, we can translate /(watch|play)/ as watch or play, this could be translated to a directory named watch_OR_play.
So for /(watch|play)/:id it will be this file tree:
pages/
--| watch_OR_play/
-----| _id.vue

Can you let me know what do you think of this idea?

Thinking about this more, it seems rather difficult to come up with a compromise. I understand the goal of this change, but I would honestly find it marginally more frustrating to browse through the pages directory and have to pick apart what the regex for a folder is supposed to represent. I would also wonder how to determine the intention, whether the folder should be translated as regex or literally. For instance as an edge case, what if my path was supposed to be /bot_or_not/, how could I signal that it's literal?
Personally I would prefer not to always have the directory structure literally translated one to one as the endpoints for my site. It's very convenient for simple setups, but my intuition wants me to sort related pages into their own labelled folder and define the path separately when I need more complex dynamic routing.
I was content when the underscore prefix simply prevented the page from being accessed directly because it allowed me to provide my own logic for how it should be accessed. It would be nice to be able to control a page's router path from within as part of the export, but I can see how that might conflict with having an easy to read structure.

Hi @Kentoss
After talking with my brother, we agreed on the fact that the _OR_ in the filename is not a solution and also can add confusion as well.
For you Regexp (watch|play), I think it's a special case and the best way to do it is with this file tree:
pages/
--| watch/
-----| _id.vue
--| play/
-----| _id.vue

Furthermore, it will be also more lisible to understand your routing this way.
If you need to re-use components between the same route, your can add them in the components folder and import them in your _id.vue files.
It's not easy to make this kind of choices for nuxt but we believe it will be easier for everyone to follow this convention when writing or managing nuxt projects.


Array converting to String while passing in extras

Hi @lampaa
window.startApp.set({
'intent': 'com.**************',
 'uri': 'locate:'
}, { upcs : ["123445","12334646"] }).start(function () {

But upcs (extras) is sending while navigating from Hybrid app to native Android app as STRING instead of ARRAY
"upcs" : "["123445","12334646"]"
Array is converted to string, could you please resolve this issue ASAP

At the moment, such support is not foreseen.


Bug with switch, dynamic segments and popstate

Make codesandbox
And video with reproducing bug 🦖

Hey @jeetiss, thanks for reporting.
My guess is that this isn't connected to the popstate event, but rather to a fact that the rendering order of Switch and nested Route isn't deterministic: while normally the rendering order is as following:

Switch renders
Route renders

when an event happens outside of the event handling routine it could happen that the inner Route renders first and then the corresponding Switch component. I have one possible solution in mind, but I first need to reproduce this as a regression test.

Closed via #46

@jeetiss Released the new version v2.1.1, feel free to upgrade!


Ad creative not changing

Hello.
First of all, great plugin.
I am having the following issue:
I am using jquery-pjax (https://github.com/defunkt/jquery-pjax) in my website. Everything seems to be working fine, including jquery.dfp, except from the fact that ad creatives do not change on subsequent page loads using pjax. This means that if AdCreative1 is displayed on Page1, no matter how many times I come back to Page1, the same creative  (AdCreative1) will be displayed.
If I refresh the page through the browser, a new creative is fetched, as normal.
I have tried using the provided callbacks, along with some other possible solutions (such as window.googletag.pubads().clear() and window.googletag.pubads().refresh(), before and after each ajax page load respectively), but neither seems to be working as expected.
Any help?
Thanks,
Ilias

Edit: When using data-adunit instead of id, each ad (creative) is displayed once and then nothing appears on the ad slot.
For example, assuming I have 3 banners (creatives) for a specific ad slot, first page load displays Banner1, second page load displays Banner2 and third page load displays Banner3. Then, on the fourth page load, nothing is displayed. All these slots are in the same page and this page is loaded through jquery-pjax.

Do you have an example page that I could view?

i ended up doing it like so in every page load:
if (window.googletag && googletag.apiReady) {
    window.googletag.pubads().updateCorrelator();
}
$.dfp({
    dfpID: '4205444',
    collapseEmptyDivs: true
});

Without window.googletag.pubads().updateCorrelator() the ad slot did not reload (get filled) on each page.
However, the problem I just discovered right now, is that line item's impressions count in DFP is not correct. I know that a line item has delivered way more than 200.000 impressions, but in DFP I can see that only 56.000 impressions are measured. Any idea why this is happening?
The site I am using jquery dfp is www.rocking.gr
Thanks,
Ilias


chore: update header linter to accept any year

Update CI to accept any year range instead of just the current year.

Codecov Report
Base: 31.69% // Head: 33.03% // Increases project coverage by +1.34% :tada:

Coverage data is based on head (73a971b) compared to base (8b75d32).
Patch coverage: 30.97% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #696      +/-   ##
==========================================
+ Coverage   31.69%   33.03%   +1.34%
==========================================
  Files          95      126      +31
  Lines       11588    13966    +2378
==========================================
+ Hits         3673     4614     +941
- Misses       7586     8930    +1344
- Partials      329      422      +93

Impacted Files
Coverage Δ

api/server/v1/collation.go
0.00% <ø> (ø)

api/server/v1/error.go
0.00% <0.00%> (ø)

api/server/v1/header.go
0.00% <ø> (ø)

api/server/v1/marshaler.go
9.93% <0.00%> (-0.30%)
:arrow_down:

api/server/v1/realtime.go
0.00% <0.00%> (ø)

api/server/v1/tx.go
0.00% <ø> (ø)

api/server/v1/validator.go
0.00% <0.00%> (ø)

internal/cache.go
0.00% <0.00%> (ø)

keys/key.go
34.61% <ø> (ø)

lib/container/priority_queue.go
100.00% <ø> (ø)

... and 129 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Feature]: Adding dark theme to the website

The Feature
I think we should have a dark theme for the website. This feature will provide users with an alternative visual experience that reduces eye strain, especially in low-light environments. A dark theme can enhance readability and improve user engagement by offering a modern aesthetic that many users prefer.
Motivation, pitch
The motivation behind this proposal comes from the increasing demand for customizable user experiences. Many users today prefer dark themes for various reasons, including me. Having a dark theme will help.
As helicone is open sourced I would love in particular to work on this things and add a dark theme to the website ?
Will by pr be merged if I do the suitable changes for the website ?
Twitter / LinkedIn details
https://www.linkedin.com/in/om-chandankar/

Should I start working on it ?


tests, libvmi: Introduce the oper sub-package with the sync-delete command

What this PR does / why we need it:
The operation of deleting a VMI in a synchronic manner is extracted out
to a dedicated libvmi/oper package.
The new SyncDelete attempts to delete a VMI and wait for it to
disappear from the API server.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
~Depends on #8307 (please examine the last commit).~
~It was introduced as a separate PR because I prefer not to block on this part the original change.~
Release note:
NONE

/cc

/test all

/remove-lifecycle stale


⚠ GitLab Server has degraded performance

In 8cbd4d4, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6898 ms

Resolved: GitLab Server performance has improved in ff8baa9.


Add buildTransitive to fix netcoreapp3 on windows vs not

Due to the way netcoreapp3 works, after discussion with @terrajobst, we need to use the new buildTransitive folder with NuGet to supply two versions of the library for netcoreapp3: 1 with the overloads and one without.
https://github.com/NuGet/Home/wiki/Allow-package--authors-to-define-build-assets-transitive-behavior
We can switch them on a condition (UseWPF/UseWindowsForms/something else?) from a targets file for that TFM and be sure the targets will be applied across all consumers.
Plan:

Build netcoreapp3 twice, with and without
put a blank entry in \lib\netcoreapp3.0 (_._).
Use a targets file in buildTransitive\netcoreapp3.0 to include an ItemGroup with a Reference element. Will conditionally use the right version of the library based on the properties.

This is fixed in #859


Add ability to parse Annex B stream in FU-A

Summary
Add ability to break apart an Annex B stream sent in a FU-A. Fixes #68
Details
My V380 cam would send a FU-A after establishing RTSP connection. The FU-A was not conformant to spec.
FU-A (start) => [ sps header - sps - boundary - pps header - pps - boundary - idr header - idr ] # Annex B stream
FU-A (...) => [ sps header - idr ]
FU-A (end) => [ sps header - idr ]

Notice how all the frags have the same header (as they should be), but the start has an Annex B stream, meaning the last NAL picked from that packet is an IDR. This means the last NAL saved from first packet will be an IDR, but the next fragment will have... the header for SPS, but data for IDR, which is wrong.
It appears that the camera only does this for FU-A that has SPS & PPS. FU-As & single NAL units for other NAL types are conformant to spec.
I have only modified this logic for the FU-A flow. We can however use the start_rtp_nal, append_rtp_nal and end_rtp_nal to handle all NAL types.
Camera details
Name: V380 (It's a generic V380 outdoor camera)
Firmware: HwV380E31_WF8_PTZ_WIFI_20201218 (I had asked them for a firmware update file to enable RTSP support)

I added a bunch of comments, but this is a great first pass! Thanks for digging in; it's really nice to get contributions like this.

Thanks for taking the time out to review. I'll take a look at the comments and update the PR.

Should NalParser ignore continuous zeros? Currently benches/client.rs is failing because it creates a long 0x00 bytes data, which break_apart_nals fails to parse because it expects that three consecutive 0x00 are a boundary, and not part of a nal.
benches/client.rs is sending a FU-A (start) with all bytes being 0x00. Isn't this test data incorrect?

Apologies—I've been quite bogged down. Will look through your comments and updates tomorrow.

Apologies—I've been quite bogged down. Will look through your comments and updates tomorrow.

Wishing you good health. Please take your time to recover.

Closing in favor of #100


Fix assertion error in _Chunk.split

Deleted some redundant declaration and fixed the assertion error by adding gc manipulations. See #2074 for details.
This my first contribution to the project, any suggestions are welcome.

@okuta I assigned you to this PR.

Add GC check and refactor with context manager. Tried some micro-benchmark and no regression is observed.

jenkins, test this please.
I will check memory allocation performance.

Jenkins CI test (for commit 670f999f3326f235dd5a96a8d102ad484e5c7ecd, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

LGTM!


Fix some issues reported on Slack

To reproduce the issue, try to run a wizard session based off of the file https://github.com/ashwani-rathee/io-project/blob/main/gifwrapper/gen/libgifextra.zip?raw=true.  You eventually get:
ArgumentError: '/tmp/jl_geNiLj/JIG6zjMf/srcdir' exists. `force=true` is required to remove '/tmp/jl_geNiLj/JIG6zjMf/srcdir' before copying.
Stacktrace:
  [1] checkfor_mv_cp_cptree(src::String, dst::String, txt::String; force::Bool)
    @ Base.Filesystem ./file.jl:312
  [2] cp(src::String, dst::String; force::Bool, follow_symlinks::Bool)
    @ Base.Filesystem ./file.jl:349
  [3] cp
    @ ./file.jl:349 [inlined]
  [4] setup(source::BinaryBuilderBase.SetupSource{FileSource}, target::String, verbose::Bool)
    @ BinaryBuilderBase ~/.julia/packages/BinaryBuilderBase/IKZGk/src/Prefix.jl:309

Because the .zip file is incorrectly seen as a FileSource, rather than an ArchiveSource.

Looks like tests are unhappy


typo: assoicated -> associated

Add code fence language as well

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/core/mssna-tn3270session-class1.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


More readable diagnostic output

Running rkr why <file> tells you, in plain English, why a file was regenerated during a build.  It can be combined with --dry-run to tell you what would happen.
E.g.,
$ rkr why --dry-run <file>

produces output like
File 'file' was regenerated by 'command -abcd' because 'foo' changed.

where foo is the "root cause" of a rebuild (i.e., the file that changed).
Leaving off <file> produces a complete list of changes in English, ala dodo check -vvv, but in English.

You can view this information with rkr --log rebuild, although a more readable output may be useful in the future.


[Bug]: "Install Pipelines Operator" link shows two versions to choose, instead of one

Is there an existing issue for this?

[X] I have searched the existing issues

Deploy type
Downstream version (eg. RHODS 1.29)
Version
1.34
Current Behavior
When data science pipeline operator is missing, user can press the button to install operator:

However, the link takes the user to Openshift OperatorHub, where it lists two versions to install:

This confuses the user, to which operator version is required:

Version 1.12.0: https://console-openshift-console.apps.ods-qe-08.rhods.ccitredhat.com/operatorhub/ns/openshift-operators?keyword=red+hat+openshift+pipelines&details-item=openshift-pipelines-operator-rh-redhat-operators-openshift-marketplace

Or

Version 1.10.4: https://console-openshift-console.apps.ods-qe-08.rhods.ccitredhat.com/operatorhub/ns/openshift-operators?keyword=red+hat+openshift+pipelines&details-item=openshift-pipelines-operator-rh-rhods-catalog-dev-openshift-marketplace

Expected Behavior
It should list only one operator to install.
Steps To Reproduce
Go to Data Science Pipelines in Dashboard - before the Pipeline operator is installed.
Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Anything else
No response

Talked with DevOps and QE for RHODS and they are intentionally including a duplicate catalog... I'm closing this issue as not an issue.


[12.0.x] ISPN-12821 CLI connection url does not support url-encoding in auth s…

https://issues.redhat.com/browse/ISPN-12821

Merged, thanks


Fix transform build operation test for two consumer projects

The test did not check for the build operations of the second transform step identity, and also ordering of those is not guaranteed between the consumer projects.

@bot-gradle test and merge

I've triggered a build for you.


BDynamics Mk22 Cockpit KSP version override

KSP compatibility to match forum thread.
Should enable #4496 to build

LGTM, merging


Deprecated Errors with PHP 8.4 Compatibility in thecodingmachine/safe

What happened?
Using thecodingmachine/safe with PHP 8.4 results in deprecated warnings related to implicitly nullable parameters, causing compatibility issues.

Library version
2.7.0
PHP version
8.4.0 RC3
What operating systems are you seeing the problem on?
macOS, Windows
Notes
No response

This is an issue with the Safe package, not with this package. 👀 https://github.com/thecodingmachine/safe/pull/441
Feel free to upvote that, and follow the progress there. 👍🏻

thecodingmachine/safe hasn't had any meaningful updates for years -- I'm personally considering it abandoned, and have switched to my more-maintained php8-compatible fork at https://github.com/shish/safe , which is marked as a drop-in replacement for easy migration

This is an issue with the Safe package, not with this package. 👀 thecodingmachine/safe#441
Feel free to upvote that, and follow the progress there. 👍🏻

It seems that dependency is abandoned. If we just wait for it to be fixed the problem may persist forever for PHP 8.4. Maybe we should find for another solution or use a fork of that package.

I'll have a look at switching over to the fork on Monday. 👍🏻 Or just dropping it completely.

Released v2.8.0 which removes the Safe package, and implements a simpler solution (it seems unnecessary to pull in a larger library for 2 functions).
This version also updates to Font Awesome v6.7.1 👍🏻


Simplify delegate invoking

Simplify delegate invoking
fixes #561

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks!


[FEATURE] Set up CI to track ml-commons agent_framework feature branch

Is your feature request related to a problem?
The various feature branches in ml-commons will eventually be merged into the agent_framework branch.  We should set up our CI to track that branch.
What solution would you like?
CI needs to publish to maven local for the ml-commons dependency.
Do you have any additional context?
We can keep our dependency on ML commons 2.x until this branch is ready; and we need to make sure appropriate PRs get backported into that branch.

@dbwiddis there are 2 branches agent_framework and agent_framework_dev which should we run CI on?


Documenation about Asp.Net Core has incorrect example in the "Quick Start"

Hi mates,
In accordance with your documentation: Quick start, you recommend using next code for initialization AppMetrics.
public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddMvc()
                .SetCompatibilityVersion(CompatibilityVersion.Version_2_1);

        services.AddMetrics();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseMvc();
    }
}

But there is a problem, that this code doesn't provide any informations about "Transactions Per Endpoint" and doesn't show it routes, like this "route:GET api/values".
It looks strange, but next code works correctly:
public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddMvc()
                .SetCompatibilityVersion(CompatibilityVersion.Version_2_1)
                .AddMetrics();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseMvc();
    }
}

Can you explain why the first sample doesn't work and what the difference between them.
Thanks,

Thank you sir! I just spent an hour trying to figure it out. It makes sense, since AddMvc() returns IMvcBuilder so calling AddMetrics on it will probably add filters to MVC pipeline and you can't do that on IServiceCollection.

Either way it doesn't work at the moment, the correct way provided above gives me:

'IMvcBuilder' does not contain a definition for 'AddMetrics'


Make Sensor Types fully Configurable

Delete hard-coded and predefined Sensor-Types and Icons for Temperature, Humidity and VOC and instead introduce two different types:

oneValue
twoValues

One Value can either be Raw or JSON, whereas twoValues has to be in JSON Format.
Behaviour is the same, except users now have to provide a JPG for the icon through the JSON:
oneValue (single value)
    "devices": [{
      "name": "Temperature DHT Sensor",
      "type": "oneValue",
      "jsondata": true,
      "firstIcon": "temperature_small",
      "firstKey": "temperature",
      "getTopic": "bedroom/esptemp"
    }]

twoValue (twin values)
    "devices": [{
      "name": "Living Room DHT",
      "type": "twoValues",
      "firstIcon": "temperature_small",
      "secondIcon": "humidity_small",
      "jsondata": true,
      "firstKey": "temperature",
      "secondKey": "humidity",
      "getTopic": "livingroom/temphumidity"
    }]

ping @jholthusen ... do you have any suggestions for better names? I don't find oneValue \ twoValues that easy to understand...

@jholthusen I suppose singleValue and combinedValue may be better after all?

Updated


Crash on "empty trash"

Describe the bug
Application crashes once I try to empty trash on imap folder
To Reproduce

Go to 'deleted items' folder
Click on '...'
Click on 'empty trash'
application crash

Expected behavior
expect no crash
Environment

K-9 Mail version: 5.800
Android version: 9
Device: ZTE Axon 9
Account type: IMAP

Logs
Please take some time to retrieve logs and attach them here:
2021-07-27 14:41:25.832 2549-30323/? E/memtrack: Couldn't load memtrack module
2021-07-27 14:41:25.832 2549-30323/? W/android.os.Debug: failed to get memory consumption info: -1
2021-07-27 14:41:26.330 2161-2161/? D/VendorServiceStateTracker: handleMessage: Event: 12
2021-07-27 14:41:26.333 2161-2161/? D/VendorServiceStateTracker: handleMessage: Event: 100
2021-07-27 14:41:26.333 2161-2161/? D/VendorServiceStateTracker: [0] Event EVENT_VENDOR_SIGNAL_STRENGTH_UPDATE Received
2021-07-27 14:41:26.333 2161-2161/? D/VendorServiceStateTracker: mLteEarfcn =-1, lteBand =-1
2021-07-27 14:41:26.336 1997-2362/? D/class com.zte.adapt.systemui.MobileSignalControllerAdapt: Signal changed! Google 4 operator 5
2021-07-27 14:41:26.385 2161-2161/? D/VendorServiceStateTracker: handleMessage: Event: 43
2021-07-27 14:41:26.512 29060-29147/? D/OpenGLRenderer: endAllActiveAnimators on 0x7003984a00 (RippleDrawable) with handle 0x70038e2ae0
2021-07-27 14:41:26.538 1997-1997/? D/LightBarControllerAdapt: forbitLightMode:false
2021-07-27 14:41:26.538 1997-1997/? D/LightBarControllerAdapt: forbitLightMode:false
2021-07-27 14:41:26.652 29060-29101/? W/CursorWindow: Window is full: requested allocation 517 bytes, free space 7 bytes, window size 2097152 bytes
2021-07-27 14:41:26.689 715-1773/? W/SurfaceFlinger: Attempting to set client state on removed layer: com.fsck.k9/com.fsck.k9.activity.MessageList#1
2021-07-27 14:41:26.689 715-1773/? W/SurfaceFlinger: Attempting to destroy on removed layer: com.fsck.k9/com.fsck.k9.activity.MessageList#1
2021-07-27 14:41:26.691 715-795/? W/SurfaceFlinger: Attempting to set client state on removed layer: Surface(name=c07cf8a com.fsck.k9/com.fsck.k9.activity.MessageList)/@0xf3d3a18 - animation-leash#0
2021-07-27 14:41:26.691 715-795/? W/SurfaceFlinger: Attempting to destroy on removed layer: Surface(name=c07cf8a com.fsck.k9/com.fsck.k9.activity.MessageList)/@0xf3d3a18 - animation-leash#0
2021-07-27 14:41:26.705 715-1773/? W/SurfaceFlinger: Attempting to set client state on removed layer: Dim Layer for - Task=18212#0
2021-07-27 14:41:26.769 10512-10512/? D/SWPD: PD: R->W
2021-07-27 14:41:26.816 29060-29524/? W/CursorWindow: Window is full: requested allocation 517 bytes, free space 7 bytes, window size 2097152 bytes
2021-07-27 14:41:26.863 2549-2549/? D/BoundBrokerSvc: onUnbind: Intent { act=com.google.android.gms.clearcut.bootcount.service.START cmp=com.google.android.gms/.chimera.PersistentBoundBrokerService }
2021-07-27 14:41:27.006 29060-29101/? E/CursorWindow: Failed to read row 919, column 0 from a CursorWindow which has 918 rows, 19 columns.

    --------- beginning of crash
2021-07-27 14:41:27.007 29060-29060/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.fsck.k9, PID: 29060
    java.lang.IllegalStateException: Couldn't read row 919, col 0 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.
        at android.database.CursorWindow.nativeGetLong(Native Method)
        at android.database.CursorWindow.getLong(CursorWindow.java:538)
        at android.database.AbstractWindowedCursor.getLong(AbstractWindowedCursor.java:75)
        at android.database.CursorWrapper.getLong(CursorWrapper.java:127)
        at android.database.CursorWrapper.getLong(CursorWrapper.java:127)
        at com.fsck.k9.provider.EmailProvider$SpecialColumnsCursor.getLong(EmailProvider.java:689)
        at com.fsck.k9.cache.EmailProviderCacheCursor.<init>(EmailProviderCacheCursor.java:47)
        at com.fsck.k9.provider.EmailProvider.query(EmailProvider.java:248)
        at android.content.ContentProvider.query(ContentProvider.java:1083)
        at android.content.ContentProvider.query(ContentProvider.java:1175)
        at android.content.ContentProvider$Transport.query(ContentProvider.java:267)
        at android.content.ContentResolver.query(ContentResolver.java:804)
        at android.content.ContentResolver.query(ContentResolver.java:753)
        at android.content.ContentResolver.query(ContentResolver.java:711)
        at com.fsck.k9.ui.messagelist.MessageListLoader.loadMessageListForAccount(MessageListLoader.kt:125)
        at com.fsck.k9.ui.messagelist.MessageListLoader.getMessageList(MessageListLoader.kt:45)
        at com.fsck.k9.ui.messagelist.MessageListLiveData$loadMessageListAsync$1$1.invokeSuspend(MessageListLiveData.kt:33)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

    --------- beginning of system
2021-07-27 14:41:27.012 1458-4281/? W/ActivityManager:   Force finishing activity com.fsck.k9/.activity.MessageList
2021-07-27 14:41:27.016 1458-4281/? D/ActivityTrigger: ActivityTrigger activityPauseTrigger
2021-07-27 14:41:27.022 29060-29060/? I/Process: Sending signal. PID: 29060 SIG: 9

to the record:
I've just did
Reproduce
Go to 'deleted items' folder
Click on '...'
Click on 'empty trash'
Removed trash
Environment
K-9 Mail version: 5.800
Android version: 10
Device: Samsung SM-A207M
Account type: IMAP

@carlosm2 to be clear: It also crashed for you with that reproduction?
Some more input:
I found a work-around. Instead of selecting the entry to empty trash, I selected all Messages inside the trash folder and clicked on delete. This worked.
On my error case I had a larger amount of deleted mails in the trash. Over 3.000. When I retried with about 20, it worked with the "empty trash" command.
So I guess this is an issue with the window coming from the content provider being out of sync with the data, so the cursor points to not existing items.
https://github.com/k9mail/k-9/blob/756ffc78564f051f34edc56b65784f393b72de1b/app/core/src/main/java/com/fsck/k9/provider/EmailProvider.java#L207
It was the first "empty trash" after the update to 5.800. Could it be that the database was not converted properly?

So I guess this is an issue with the window coming from the content provider being out of sync with the data, so the cursor points to not existing items.

That could be it. I believe the cursor window is limited in size and only the first one is filled when the query call to the database returns. So when more than one is needed to fetch all results there's the possibility of a race condition (initial query includes messages that are later deleted before data about them could be read from the cursor).


Question on RobotState msg

When creating a fleet adapter for a custom robot fleet which supplies RobotState messages, is it necessary to supply the last parameter in the msg Location[] path?  Other RobotState parameters will be supplied like battery percent except for the path array whose elements will be all 0, would such messages still work or will it cause traffic management issues?

The RobotState API is considered deprecated. The recommended way to integrate a full control category robot is to use the C++ API.
But if you decide to use the rmf_fleet_msgs API, then you do need to provide the path field, or else, like you inferred, there will be traffic management issues because RMF won't know where your robot is trying to go.

Closing as this is not an issue. To continue discussing this topic, please open a discussion.


Get user approx. location

use https://ipgeolocation.abstractapi.com/

this is handled with html5 navigator instead of via IP, but will only happen after the user consents by enabling the switch


Post links directing to empty pages.

I'm creating blog posts like it says here but when I click the post it directs me to an empty page.
If I do hugo new --kind post posts/testing then inside the testing directory I have an index.md where I can put in the info. Writing something in the summary section will display the summary, but when I click on the title of the post it takes me to an empty page. I've tried adding a testing.md file inside and outside the directory but I still can't manage to get it to work.
It would help a lot if you could give me some tips or direct me to where to look. Thanks.

Please follow the Questions link in the Readme: https://github.com/wowchemy/wowchemy-hugo-modules/discussions


Unable to send custom Emojis in message payload

Description
Unable to use custom emojis in a message.   Is there a technique I am missing?  Not sure why I can get this to work with the API but not with this action.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Hey @grndvl1 👋 Thanks for writing in about this! This seems unexpected to me, so I'm curious about the method you're using to post the message?
I'm finding that including custom emojis in either payload and slack-message seem to both work for me, both from a bot token and incoming webhook, so any other details would be helpful for troubleshooting!

👀 Going to close this as stale - the latest @v2 version is now released! - since you're noticing this works with the API but not this action, though I'm still curious if this continues to happen in the latest release.
For future reference, this step sends a message with custom emoji in the current version:
- name: Send a message with custom emoji
  uses<EMAIL_ADDRESS>  with:
    errors: true
    method: chat.postMessage
    token: ${{ secrets.SLACK_BOT_TOKEN }}
    payload: |
      channel: ${{ env.SLACK_CHANNEL_ID }}
      text: "greetings :octocatted:"

Please feel free to comment or open a new issue if this seems to not continue to not work for you. I'd be interested in knowing of errors that might be returned too! 🙏


Hello! The color style of the extended page cannot be customized and modified

Hello! The color style of the extended page cannot be customized and modified
The background color cannot be modified and the border color cannot be modified:

Markdown preview title border cannot be modified:

VSCode 1.81
Windows 10

This issue makes it impossible to customize the theme appearance, hope you can fix it, thank you very much! 😜👍

The foreground color cannot be modified


stardust-xr-gravity: 0-unstable-2024-08-21 -> 0-unstable-2024-12-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for stardust-xr-gravity is: Utility to launch apps and stardust clients at an offet
meta.homepage for stardust-xr-gravity is: https://stardustxr.org
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-12-29 in filename of file in /nix/store/492qwp8446vl4iqq81ch53rqlaxgqqyw-stardust-xr-gravity-0-unstable-2024-12-29

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

stardust-xr-gravity

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/492qwp8446vl4iqq81ch53rqlaxgqqyw-stardust-xr-gravity-0-unstable-2024-12-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A stardust-xr-gravity https://github.com/r-ryantm/nixpkgs/archive/ad981657df8022fc54cebdd795a89b97858d11ab.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ad981657df8022fc54cebdd795a89b97858d11ab#stardust-xr-gravity

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/492qwp8446vl4iqq81ch53rqlaxgqqyw-stardust-xr-gravity-0-unstable-2024-12-29
ls -la /nix/store/492qwp8446vl4iqq81ch53rqlaxgqqyw-stardust-xr-gravity-0-unstable-2024-12-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

stardust-xr-gravity

Maintainer pings
cc @Pandapip1 @technobaboo for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge
No apparent code changes


Updated, rearranged software repositories and package managers

I added Slackware to the list of software repositories, and moved NixOS and GNU Guix to that category since their package managers are independent and closely related to their base distributions. I also added APK (for Alpine Linux and FreeBSD) and APT-RPM (for PCLinuxOS, Vine Linux, and ALT Linux) to the list of package managers.

Since the lower section is for the independent package managers it would better to swap the positions of the Nix & Guix lines with the APK & APT-RPM ones.
I like that you updated the "Available as ..." text with the install command.  Maybe the APK & APT-RPM lines should be split up to have each OS and it's install command as well?

Ok, what about now? I also decided to add Chocolatey and Winget to the repos list because why not, let me know what you think.

Does one really need to specify version for Slackware?

I mean if people package it for Slackware, why not :D
I'm sure someone will use it

I mean if people package it for Slackware, why not :D
I'm sure someone will use it

My question was more in the direction that a command having a version in it will soon stop functioning as written.

Thanks for incorporating instructions for Slackware users. The "upgradepkg --install-new" is the simplest instruction I can think of, so thanks Ahrotahn for suggesting it.
And finally, it may help users to know the full path to the packages instead of merely the URL for the webhost - this URL will never change: http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/

Why did you remove GNU and why did you change the order. It was good, it was alphabetic :)


Anyway of forcing OpenSSL on C++ Compile

What version of gRPC and what language are you using?
C++ with 15e95b30e962178cf8ea7c16662bd104fce0b29d
What operating system (Linux, Windows, …) and version?
REHL 6
What runtime / compiler are you using (e.g. python version or version of gcc)
devtoolset-7 gcc 7.4
What did you do?
Currently we are trying to build grpc on rehl6, the rehl6 is using OpenSSL 1.01, so gRPC itself is using boringSSL. However BoringSSL has slightly difference compare to OpenSSL which cause a bug on using gRPC to communicate with Google Speech.
When called BIO_new() in BoringSSL it would not create a ex_data structure compared to OpenSSL, which later on when reading the same private key from google cloud, boring SSL would return null on PEM_read_bio_RSAPrivateKey in json_token.cc:105,makes grpc crash on segment fault.
This crash force us to use OpenSSL, the docs does not include how to turn on forcing OpenSSL, i tried the EMBED_OPENSSL option to true it does not work.

gRPC requires OpenSSL 1.0.2, so you can't use OpenSSL 1.0.1 to build it. Sorry.

Also, the boringssl crash you are describing warrants its own bug report, is you want to extract it as an independent bug report.

Sure, if that api difference is a bug i will report to Boring SSL issue board. Thx for help.


enable-menu-swipe-with-back-views argument.

Short description of what this resolves:
Allows to open side menu with back views using swipe gesture.
Added enable-menu-swipe-with-back-views.
Ionic Version: 1.x

Hello, thanks for using Ionic! While we really appreciate your PR I am going to have to close this for now and ask that you re submit it to this repo. Sorry about that!


Instance nuclei segmentation from semantic segmentation as input?

Does cellpose support just instance segmentation from semantic stack as input?
Attached is a crop volume of semantic segmentation output with a CNN network. Current cellpose network works poor on the original raw data. But luckily, an inhouse trained network works better on the raw data to generate a semantic segmentation.
I am looking for cellpose to take this semantic segmentation as input and generate an instance 3D segmentation of these 3D nuclei.

That's a good idea! Any transformations you can do to make your images to look more like the ones in the Cellpose training set should help. It is not as good as just retraining Cellpose on your own ground truth data, but it is worth a try. You can use the do_3D option to perform 3D segmentation on this volume (see the documentation for details, you may have to slice the volume first for Cellpose to read it in as a 2D stack).

Hi @kevinjohncutler the issue i raised here was making use if the pixel prediction values in the input stack for instance segmenting them using cellpose.
These are already 2D slices.
Let me explain my workflow:
I obtain the pixel prediction of nuclei for the raw microscopic images using an inhouse nuclei model. As far as i understand, cellpose doesnt read those pixel predictions as input images and instance segment them. For this reason, i convert those informative images into a less informative RGB image using imageJ. Image/Color/Create composite, then Image/Color/Stack to RGB. I save that image and open it in cellpose such that it read the obtained pixel predictions as a raw image. Further what happends is cellpose repredict the nuclei and instance segment them. This seems to work fine in most of the cases, but I was wondering if cellpose could make use of the more informative pixel prediction image to generate the instance nuclei segmentation.
Best,
Athul

@athulrv, yes. If your in-house model produces 2D slices, you can stack them together again to give to cellpose. If your pixel predictions are the same shape as the original dataset you are giving to cellpose, it should work. It doesn't need to be RGB, monochrome images are fine.


feat: setting data-control

💻 变更类型 | Change Type

[x] ✨ feat: setting data-control
[x] 🐛 fix: replace Index => index
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

ref: #8


posix: pthread: fix warning about uninitialized variable

Initialize ret to zero. I don't think there is any way out of this function without it being initialized, so IMHO it's a false positive.

I'm still confused why CI didn't catch this when the initial PR was submitted?

I'm still confused why CI didn't catch this when the initial PR was submitted?

Same. It's a bit baffling.


use internal fetch function of node

related to #2649
With Node >= v18 comes an internal fetch method. This PR centralizes the use of fetch in a new module js/fetch.js and uses the internal fetch function of node instead external node-fetch library if node version >= v18.

Codecov Report

Merging #2855 (ab7934f) into develop (a4c77f0) will decrease coverage by 0.98%.
The diff coverage is 28.57%.

@@             Coverage Diff             @@
##           develop    #2855      +/-   ##
===========================================
- Coverage    64.80%   63.82%   -0.99%
===========================================
  Files            8        9       +1
  Lines          287      293       +6
===========================================
+ Hits           186      187       +1
- Misses         101      106       +5

Impacted Files
Coverage Δ

js/fetch.js
16.66% <16.66%> (ø)

js/server.js
66.21% <100.00%> (ø)

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 a4c77f0...ab7934f. Read the comment docs.


[Test suite] Add insert integration test

Description
add insert integration test
Test
    test! {
        sql: "SELECT * FROM Test",
        expected: Ok(select_with_null!(
            id  | num | name;
            I64(1)   I64(2)     Str("Hi boo".to_owned());
            I64(3)   I64(9)     Str("Kitty!".to_owned());
            I64(2)   I64(7)     Str("Monsters".to_owned());
            I64(17)  I64(30)    Str("Sullivan".to_owned());
            I64(1)   I64(28)    Str("Wazowski".to_owned());
            I64(1)   Null      Str("The end".to_owned())
        ))
    };

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

52 of 52 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 98.135%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
33355

Relevant Lines:
33989

💛  - Coveralls