Rough draft release plan

A first draft of how I my idea for us to take control of the versioning story.

If we go with this plan, it makes sense to me to strictly follow the rules of Semantic Versioning: https://semver.org/
Rather than loosely defining our own versioning number scheme and criteria.

Semantic versioning is the standard, but, in this case, I like how @JoshOrndorff is trying to identify more specific criteria that corresponds to the nature of our work and workflow. What we call the release categories (semantics) isn't that important. So, we could just change the name point to patch to get semver, but I don't think all of the semver rules map perfectly to what we're doing.
I do have a few thoughts on the proposed criteria though and will add comments soon.

I actually thought I was taking the names directly from semver , I just forgot what the last one was called. I'd happily rename it to patch. And yeah, I'm a big fan of semver. We should follow as much of their semantics as we can without undermining our release story.

It seems that in the Substrate internal chat, we had buyoff to establish clear versioning around most of the SRML and the Runtime Development APIs.
These aspects of Substrate seem like the key things for documentation in the time being.
In which case I suggest we move this issue/effort to the Substrate repo, and then documentation will just follow along.

I suggest we move this issue/effort to the Substrate repo, and then documentation will just follow along.

That's wonderful! What does that mean for Substrate Package? Seems like it's still useful to have a known working version of at least the ui tempate for each upstream release of Substrate.

I think we will maintain the Substrate package since Substrate, even while using clear versioning, will be moving fast, and people cannot rely on Master to work with our docs.
We will maintain a "stable" version, which aligns with our docs using the Package, however, we will not invent any versioning, we should just use Substrate.

LGTM. So in future, if I make a significant patch/feature to front-end, will let you know, and decide if we want to include that in substrate-package.

My summarized thoughts around versioning on Substrate is the following:

In general I want it. I think a good versioning system will be better for our users and documentation.
I want it done right. If the Developer Hub is going to have official documentation which points to released versions, it will represent Parity and the main Substrate project itself, and will be something that our customers will begin to rely on.
It is my understanding and belief that the Substrate project is not quite ready for this kind of versioning as a whole. Parts of consensus, networking, etc... will knowingly change quite a bit, and without hesitation around versioning.
It is possible that Runtime Development as an isolated part of Substrate is ready for versioning, but if that is the case, it is my belief that this versioning should be dictated by the Substrate repository. For example, using something like the spec_version and impl_version would make sense as a basis for versioning, but I am not sure they versions track more minute details about Substrate development like syntax changes which do not reflect changes in the actual logic (but will make a difference to end users).

I would lean toward the following solution for v2/immediate future:

Write all v2/master docs assuming there will not be breaking runtime changes from now until the official v2 release. Hence, usage of the package, or any part of the package, will "just work", independent of when a user picked up that package from now until then.
Eat a little bit of individual work if a breaking change comes up and we need to make minor modifications. (This is something we can always re-evaluate given practical examples)
When v2 is officially released, turn all revdependencies on Substrate to a branch = v2.0 dependency, and that is the most granular versioning we will support on our "green path" scenario. (note this is shown to work with v1.0, so I see no reason to believe it would not work.)

Finally I think it is without saying that this is only a problem which will appear again from v2.0 to the release of Polkadot on v3.0. We should get ahead of the game here.
We need buy-off from the Substrate team to establish a reliable versioning system for Runtime developers between v2.0 and v3.0. This versioning system should be established in the Substrate repository, and there should be a process in place that every change that affects runtime development should cause some change to the version, just like we have in place for spec_version or impl_version.
On top of this we need to establish a runtime developer changelog which describes the changes from any one version to another. This would act as a map to allow a developer who is using a "pre-release v3.0" version of substrate to migrate their work from one version to another.
I imagine this may require a little initial work to set up, but ideally would be as simple as bumping a number and writing some text for the core dev team from change to change.
Without this buyoff, we either have an issue with resources, which means we may need to contribute those resources from the DevEx team, or an issue that Substrate is not ready to be versioned and supported in this way, in which case, we should seriously evaluate why the core dev team thinks it is not ready, and why we would do it anyway.


Gitlab Collector Docker Config

Added a properties builder for Gitlab and updated references in the dockerfile.  Fixes #1012

LGTM

LGTM


Update Data exploration

Fixes #4

shortened and restrutured text

missing

[ ] explicit instruction for students to do the exercise?
[x] the Quiz M1.01 still shows in the menu bar on the left (see screenshot). how can I remove it?

one of the html files was not updated, fixed now

thanks for the suggestion, I've cut it now


#7035 | escape single quote

What's changed, or what was fixed?

escaping '
making caniuse https

Fixes: #7035
Target Live Date: YYYY-MM-DD

[ ] This has been reviewed and approved by (NAME)
[ ] I have run npm test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

thank you!


Using slide-level predictions that differ within the same patient

Feature
I am using the run_project.py and actions.py workflow, which heavily relies on slideflow.Project objects. However, my current diagnostic task is to train a network to predict bone marrow fibrosis grade on a slide. Because multiple slides per patient may have different fibrosis scores at different times, there likely will be different outcomes per patient.
When trying to run the analysis, slideflow outputs an error when running training_validation_split because there are multiple outcome labels per patient.
It is not clear to me how to go about doing this type of analysis using slideflow.Project objects. I have tried changing the val_strategy to no avail. I know that the "trick" is to tell slideflow that each slide is actually a unique patient (which is not technically true, but it would fix the issue).
Pitch
I propose an additional flag in slideflow.Project.train() such as "outcome_uniqueness_group" that can clarify that the outcome is unique to the patient or unique to the slide (or potentially later on, unique to the tile).
Alternatives
Otherwise the ability to reassign patient names in an already established sf.Project object would suffice. I would not recommend this approach as much, because the syntax would be confusing to the user.
I know that there is documentation on how to reassign patient names to individual slides using the slideflow.model.Trainer() functions, but I am trying to stick with the slideflow.Project interface.

I know that the "trick" is to tell slideflow that each slide is actually a unique patient (which is not technically true, but it would fix the issue).

This would be the preferred method of addressing your use case. The "patient" identifier is simply an ID column that enables support for multiple slide images per ID. If each slide has its own outcome, just duplicate the "slide" column and name it "patient".
While I think it's reasonable to consider add the option for an outcome to be slide-level or patient-level (perhaps argument outcome_level='patient' vs outcome_level='slide'), it would require a moderate amount of refactoring and could introduce new issues of its own. For simplicity, I would recommend the workaround described above. If this becomes burdensome or a recurring issue, we can explore a more definitive solution.


Noisy build messages

Caused by warnings of changing include/exclude rules. See this Travis log for example.

Should be very easy to fix, see https://github.com/rust-lang/cargo/issues/4268

Thanks. All that's required is to change include = ["data"] to include = ["data/shaders/*.glsl", "data/fonts/*.ttf"].

include = ["./data/"] is better.


[Hub Generated] Review request for Microsoft.ApiManagement to add version stable/2019-01-01

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Fix for user raised issue in the spec
https://github.com/Azure/azure-sdk-for-node/issues/4718

Automation for azure-sdk-for-java

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

@veronicagg this looks like an issue with the rest-api-specs validator. The property properties.document is a jobject. The validator is treating it like another definition  and trying to figure out a file.
I can remove the example, but it would be good to have it fixed.

@veronicagg a gentle ping on this. This is customer reported issue and we are trying to fix it. The spec was incorrect.


Container exits

Describe the bug
The program exits in the container
Screenshots or Logs
epicgames  | [2024-02-14 05:59:30.504 +0100] ERROR: Timed out after 21567974 ms
epicgames  |     user<EMAIL_ADDRESS>epicgames  |     err: {
epicgames  |       "type": "Error",
epicgames  |       "message": "Timed out after 21567974 ms",
epicgames  |       "stack":
epicgames  |           Error: Timed out after 21567974 ms
epicgames  |               at Timeout._onTimeout (/usr/app/src/device-login.ts:78:29)
epicgames  |               at listOnTimeout (node:internal/timers:569:17)
epicgames  |               at processTimers (node:internal/timers:512:7)
epicgames  |     }
epicgames  | [2024-02-14 05:59:30.547 +0100] WARN: Current version
epicgames  |     COMMIT_SHA: "a9756df29cf752f3b5bafab03a44b6cd9b970b77"
epicgames  |     BRANCH: "master"
epicgames  |     DISTRO: "alpine"
epicgames  | [2024-02-14 05:59:30.548 +0100] INFO: Exiting successfully

Additional context

This was intentionally added in https://github.com/claabs/epicgames-freegames-node/commit/89c8ea44daa24ddb005907e6a175a3016fd5aa9e to ensure the program runs each scheduled time, so the device token doesn't expire and ask you to log in daily. Essentially, the notification must timeout before the next run.
You don't provide much context in this issue, but I assume a login request notification was sent and ignored. If you complete the login, it will resolve itself.

Got it.
The cron runs every 6 hours (0 0/6 * * *), and the problem occurs between the midnight one and the one at 6 am.
What happens now is that because the program seems to exit, I can't complete the login notification, as I get a bad gateway error from my reverse proxy (as the webserver doesn't work).
When I restart the container, it works properly again.
Would it help by changing the cron to run every 12 hours? Or is that too long?

I've changed the cron config to
"0 3,9,15,21 * * *",
Hopefully, that will resolve the issue :)

What happens now is that because the program seems to exit, I can't complete the login notification, as I get a bad gateway error from my reverse proxy (as the webserver doesn't work).

I think it's flipped actually. The program is exiting after 6 hours of waiting for you to log in. You should really only have to log in once ever. If you're logging in multiple times, maybe there's something wrong persisting the token?

The program is exiting after 6 hours of waiting for you to log in

That makes sense, as the notification comes at midnight, and the next run is at 06:00, which is when I usually have not woken up yet.

You should really only have to log in once ever. If you're logging in multiple times, maybe there's something wrong persisting the token?

I've had to log in daily, since when I started to run the container.
I used to get the notification at midnight, and then I could login in the morning (usually would do that at around 7/7:30).

Just did a restart of the container, due to the latest container update, and it automatically logged in.
So I do think that the cron notation of 0 0/6 * * * was not working properly, which caused the daily login messages (as it would only run once per day).
Everything works fine now!


Adapter damaged

Devices were flickering (PES-508
PES-511).
Adapters were damaged.

Looks like a loose connection barrel connector on 511. The adapter is changed for 508.


Add 'if' parameter to parsers

Description of Changes
Adds the parameter if to the helper.Parser type. This allows a parser to be skipped based on an expression condition, which greatly simplifies many common cases where we would currently need a router. This is currently not implemented for timestamp or severity parsing because they do not embed helper.Parser, however, if #207 is fixed, this will apply to those as well.
A simple example of this in action.
Config:
pipeline:
- type: stdin
- type: json_parser
  if: '$record matches "^{.*}$"'
- type: stdout

Command:
(echo '{"test":"key"}' ; echo "notjson" ) | stanza -c ./dev/config.yaml | jq

Output:
{
  "timestamp": "2020-11-12T15:12:56.649494-05:00",
  "severity": 0,
  "record": {
    "test": "key"
  }
}
{
  "timestamp": "2020-11-12T15:12:56.649744-05:00",
  "severity": 0,
  "record": "notjson"
}

Closes #170
Please check that the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Add a changelog entry (for non-trivial bug fixes / features)
[x] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.8276267
+0.068971395
130.12123
+2.402481

1
5000
6.517333
+0.39639854
134.9414
-1.8154602

1
10000
12.2416525
+0.15521526
141.33284
-5.022354

1
50000
59.08731
+2.8295517
180.97333
+4.4022064

1
100000
113.21013
+1.2071838
226.26347
-0.52734375

10
100
2.3621027
-0.034606457
131.59428
-1.355072

10
500
6.672539
+0.034521103
139.13618
+0.28353882

10
1000
13.604034
+0.24166107
147.0194
-0.78178406

10
5000
67.17396
+5.399868
185.79445
+0.15597534

10
10000
126.49294
+5.729912
228.03273
+6.335663

On second inspection, it seems like it will be difficult to migrate the severity and timestamp helpers to be parsers since they are embedded in the helper.Parser type. Instead, I think the best move will be to implement if on the helper.Transformer which is shared by those

@djaglowski I've got most of the way to getting it into the transformer yesterday afternoon. I plan to get a PR out this morning with that change.

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.7241672
+0
129.61679
+2.400734

1
5000
6.086384
-0.068892
137.43036
+0.094955444

1
10000
12.293467
+0.06895542
145.91824
+1.3213959

1
50000
61.587555
-1.2426796
178.49677
-1.1000824

1
100000
116.92211
-3.8635178
230.08984
+0.35990906

10
100
2.3621254
-0.068972826
129.18858
-5.608017

10
500
6.9312005
-0.43107176
137.85304
+0.061691284

10
1000
13.58649
-0.56901646
146.3754
-3.874466

10
5000
64.931984
+0.13523102
183.14883
-1.4571686

10
10000
127.29671
+1.2211075
231.7931
-0.9923248

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.7586491
+0.034481883
127.71794
+0.50188446

1
5000
6.0345926
-0.12068319
136.72845
-0.60694885

1
10000
12.517456
+0.2929449
146.28421
+1.6873627

1
50000
60.932392
-1.8978424
179.39911
-0.19773865

1
100000
116.48304
-4.3025894
228.49205
-1.2378845

10
100
2.2931325
-0.13796568
132.97427
-1.8223267

10
500
7.0518627
-0.31040955
140.39735
+2.6060028

10
1000
14.84518
+0.6896734
143.05725
-7.1926117

10
5000
63.466976
-1.3297768
186.21404
+1.6080322

10
10000
123.44894
-2.6266632
219.97617
-12.809265


Bug : Frontend tweeting doesn't work

I believe it's related to a missing environment variable in frontend container

@Jacelius Har det fikset det?


add translations - [merged]

In GitLab by @erdzan on Apr 27, 2021, 20:10
Merges ngxtranslate -> master
Co-authored-by: Ben Lakhoune<EMAIL_ADDRESS>

In GitLab by @erdzan on Apr 27, 2021, 20:10
approved this merge request

In GitLab by @erdzan on Apr 27, 2021, 20:11
added 2 commits
382be4c1 - 1 commit from branch masterb61ab284 - Merge remote-tracking branch 'origin/master' into ngxtranslate
Compare with previous version

In GitLab by @erdzan on Apr 27, 2021, 20:11
approved this merge request

In GitLab by @erdzan on Apr 27, 2021, 20:11
mentioned in commit 5a0fe54e847ac9a4bff91ede6da2a5fadb19340b


Allow remove option to be additionally expressed as String[][]

There are package.json property keys that contain dots (.), namely exports. Since the dot has a special meaning, references to these properties are not possible simply by a string.
Consider the cost of updating the replace option to allow the similarly functionality.

Instead of adding an additional type, decided to move to dot-prop which supports escaping the dot.


Can only run the flash_simulator test once on native_posix

Describe the bug
The first time you run this it works. The second time, the flash.bin file is still around from last time and the test fails.
To Reproduce
Steps to reproduce the behavior:
1.west build --force -b native_posix tests/drivers/flash_simulator
2. rm flash.bin
3. ./build/zephyr/zephyr.elf  - all good
4. ./build/zephyr/zephyr.elf  - fails
5. go to 2
Expected behavior
Should always pass
Impact
annoyance
Screenshots or console output
$  ./build/zephyr/zephyr.elf
*** Booting Zephyr OS build zephyr-v2.2.0-2692-gff856e01f5d8  ***
Running test suite flash_sim_api
===================================================================
starting test - test_int
PASS - test_int
===================================================================
starting test - test_write_read
PASS - test_write_read
===================================================================
starting test - test_erase
Incremental pattern expected
Erased area expected
Incremental pattern expected
PASS - test_erase
===================================================================
starting test - test_access
PASS - test_access
===================================================================
starting test - test_out_of_bounds
PASS - test_out_of_bounds
===================================================================
starting test - test_align
PASS - test_align
===================================================================
starting test - test_double_write
PASS - test_double_write
===================================================================
Test suite flash_sim_api succeeded
===================================================================
PROJECT EXECUTION SUCCESSFUL
ellesmere:/scratch/sglass/cosarm/zephyrproject/zephyr$ ./build/zephyr/zephyr.elf
*** Booting Zephyr OS build zephyr-v2.2.0-2692-gff856e01f5d8  ***
Running test suite flash_sim_api
===================================================================
starting test - test_int

    Assertion failed at tests/drivers/flash_simulator/src/main.c:84: test_int: (0xff not equal to test_read_buf[i])
sim flash byte at offset 0x0 has value 0x002
FAIL - test_int
===================================================================
starting test - test_write_read

    Assertion failed at tests/drivers/flash_simulator/src/main.c:102: test_write_read: (0 not equal to rc)
flash_write (-5) should succedd at off 0x0
FAIL - test_write_read
===================================================================
starting test - test_erase
Incremental pattern expected

    Assertion failed at tests/drivers/flash_simulator/src/main.c:62: test_check_pattern32: (val32 not equal to r_val32)
flash word at offset 0x4 has value 0xffffffff02
FAIL - test_erase
===================================================================
starting test - test_access
PASS - test_access
===================================================================
starting test - test_out_of_bounds
PASS - test_out_of_bounds
===================================================================
starting test - test_align
PASS - test_align
===================================================================
starting test - test_double_write
PASS - test_double_write
===================================================================
Test suite flash_sim_api failed.
===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.11.2
1fed229f6e

Additional context
Add any other context about the problem here.

Creating the file only once is expected behaviour.
If recreating a file each time is needed please make this optional behaviour.

So should we change the test to write first and then read, rather than assuming that the flash is erased?

@vanwinkeljan @nvlsianpu @fnde-ot What is the correct course of action here? Either document that flash.bin needs to be erased in between test runs, or change the test sequence so it erases the flash prior to writing it?

I would say erase the flash, on the other hand is it not assumed that  tests run in a pristine environment, eg. if you use sanitycheck instead of west (+ run manually) to run the test the issue is not encountered?

cc @de-nordic

Proper solution would be introduce configuration (ERASE_ON_EACH_STARTUP maybe) which determine  how thread existing flash.bin.
Probably in test environment erasing the file should be the default behavior.
I found useful for some samples/application that them might store some data between resets.
I know that some users utilizes this fact as well.
@vanwinkeljan saniticheck indeed create pristine environment if it comes to the file existence as it creates new directory on each run.

I was thinking about generating random file name in /tmp for that.

Proper solution would be introduce configuration (ERASE_ON_EACH_STARTUP maybe) which determine how thread existing flash.bin.
Probably in test environment erasing the file should be the default behavior.

Dont agree on this one, on real HW the flash will not be erased each time you reset/power-up your board. If the code assumes that the flash is eased at startup it should take care of this

There is advantage of leaving the file for debugging purposes.
Though I do not think that one test should depend on an output of another test, so when flash needs to be present and set prior to running test cases (power on case), operation of filling data into test should be part of test initialization, because it also ensures that test will be given predictable data.
I do not know how to test down/up case scenario with such approach, though I think that you should usually just test subsystem, that is use subsystem to write into flash the test data and then use the same subsystem read and check if you get what you expect.

So shall we change the test to write whatever data it relies on? That's what I have in the 'flash read' test:
https://github.com/zephyrproject-rtos/zephyr/commit/6cc3f8f111074effaaef2198ac5d2821bed93be4

So shall we change the test to write whatever data it relies on? That's what I have in the 'flash read' test:
6cc3f8f

Yes, I believe so. It makes it easier to modify or expand a test without impacting other tests. It will not break tests if the order of tests get changed.

OK I added another commit here to fix that:
https://github.com/zephyrproject-rtos/zephyr/pull/25048


When running Example getting TypeError: 'staticmethod' object is not callable

Describe the error
i have install the manim as per the instruction given on the documentation, when running the example getting TypeError: 'staticmethod' object is not callable
Code and Error
Code:
manimgl example_scenes.py OpeningManimExample
Traceback (most recent call last):
File "/Users/arpansaini/opt/anaconda3/bin/manimgl", line 5, in
from manimlib.main import main
File "/Users/arpansaini/Documents/Techsqually/projects/maniumProj/manim/manimlib/init.py", line 14, in
from manimlib.animation.animation import *
File "/Users/arpansaini/Documents/Techsqually/projects/maniumProj/manim/manimlib/animation/animation.py", line 5, in
from manimlib.mobject.mobject import _AnimationBuilder
File "/Users/arpansaini/Documents/Techsqually/projects/maniumProj/manim/manimlib/mobject/mobject.py", line 58, in
class Mobject(object):
File "/Users/arpansaini/Documents/Techsqually/projects/maniumProj/manim/manimlib/mobject/mobject.py", line 555, in Mobject
def serialize(self):
TypeError: 'staticmethod' object is not callable
Error:

Environment
MAC OS:
manim version: master
python version:3.9.12

Same here too.

It works after I removed the static decorators in manim/manimlib/mobject/mobject.py and manim/manimlib/mobject/types/vectorized_mobject.py.
I submitted a pull request. Let's see.

Fixed in #1951

For newbies like me who encountered this problem:  you may have installed the package by cloning the library. Check your env library by command pip list to see if your manimgl/manimlib is suffixed by your own path like home/name/manim.
If it is, uninstall them and reinstall directly via pip.
pip uninstall manimgl manimlib
pip install manimgl manimlib

Quote from README.md: If you want to hack on manimlib itself, clone this repository and in that directory execute:


remove all *_currency fields

All fields with *_currency in them are a bug.  They should not be part of the API.  I removed all references to them, but someone may want to check my work (I didn't run any code to generate output).
I just put in a fix so that these fields should not show up again in API output (see https://github.com/CruxConnect/crux-api/pull/1063).

Why are currency fields a bug? How will the UI know what currency to display if there isn't a currency field?

Follow up, @jtprince: Did we decide somewhere to only use USD and I just missed the decision? If we are always and only doing USD then it makes sense to remove currency fields.

@nickcoleman This PR needs to have the updated master paw file merged into it and have the changes applied to its docs.

[ ] _product_retailer/get_catalog_detail.md
[ ] _product_retailer/get_catalog_detail.md
[ ] _product_retailer/get_item_detail.md
[ ] _product_retailer/get_item_export.md
[ ] _product_retailer/get_items.md
[ ] _product_retailer/get_items.md
[ ] _product_retailer/get_skus.md
[ ] _product_retailer/search_items.md
[ ] _product_supplier/catalog_add_item.md
[ ]  _product_supplier/create_catalog.md
[ ] _product_supplier/create_item.md
[ ] _product_supplier/create_sku.md


Register package on bower

It would be nice if I could install this using bower like the rest of my frontend dependencies.

I don't know much about Bower, but I'm not opposed to adding this to the project if it's not too intrusive.
FYI - whenever you add chessboard.js to your website, it puts itself on window.ChessBoard

chessboardjs is on npm now


[Bug] spconfig export --include WORKFLOWS fails without details

using v1.2 of the CLI, running:
sail spconfig export --include WORKFLOWS
and then checking the status with:
sail spconfig status --export
results in the following which doesn't have details on what the error is
Job Type: EXPORT
Job ID: 517b1476-cd1a-44be-a8a3-d9537b13ea92
Status: FAILED
Expired: 2023-09-15 17:41:00 +0000 UTC
Created: 2023-09-08 17:41:00.777 +0000 UTC
Modified: 2023-09-08 17:41:00.902 +0000 UTC
Completed: 0001-01-01 00:00:00 +0000 UTC
Getting the status via API shows the error information in more detail:
{
"jobId": "517b1476-cd1a-44be-a8a3-d9537b13ea92",
"status": "FAILED",
"type": "EXPORT",
"message": "java.lang.IllegalArgumentException: Supplied types are not supported: [WORKFLOWS]",
"expiration": "2023-09-15T17:41:00Z",
"created": "2023-09-08T17:41:00.777Z",
"modified": "2023-09-08T17:41:00.902Z"
}
To Reproduce Steps to reproduce the behavior:
sail spconfig export --include WORKFLOWS
sail spconfig status --export
Expected behavior
The output would included the error message as shown in the API status response
Actual behavior
No detail provided
Screenshots
n/a
Operating System (please complete the following information):

OS: Mac OS Ventura 13.5.2
CLI Environment: terminal zsh
Version: 1.2

Browser (please complete the following information):

Browser: n/a
Version: n/a

Additional context Add any other context about the problem here.
The api doc here https://developer.sailpoint.com/idn/api/beta/export-sp-config has WORKFLOWS

I did some more digging. in postman using the spconfig apis directly, workflows export if you do NOT provide an includeTypes list.
{   "includeTypes": [    ] }
The downloaded file includes workflows.
but:
{   "includeTypes": [       "WORKFLOWS"    ] }
fails with:
{
"jobId": "eae4ea66-d930-4ad4-9179-4fb2c06f40d3",
"status": "FAILED",
"type": "EXPORT",
"message": "java.lang.IllegalArgumentException: Supplied types are not supported: [WORKFLOWS]",
"expiration": "2023-09-15T20:50:55Z",
"created": "2023-09-08T20:50:55.961Z",
"modified": "2023-09-08T20:50:56.143Z"
}

The correct value is "WORKFLOW" singular. Documentation needs to be updated to reflect that.

This has been referenced in the 2.0 release of the CLI.  Please resubmit if this is still an issue using v2.0.


HTTP server segfaults

I get various segmentation faults running httpserver.pony and:
$  weighttp -n 200 -c 1 http://<IP_ADDRESS>:50000

This is on Linux version 4.0.0-1-mainline (mborch@wavel) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 25 12:00:24 CEST 2015.

(gdb) bt 5
#0  0x0000000000406bd1 in $tuple_String_String_$trace ()
#1  0x0000000000418ede in gc_handlestack () at src/libponyrt/gc/gc.c:329
#2  0x000000000041999e in pony_recv_done () at src/libponyrt/gc/trace.c:43
#3  0x0000000000412680 in http__ServerConnection_$dispatch ()
#4  0x0000000000414f17 in handle_message (actor=0x7ffff4dece00, msg=0x7ffff5df6700)
    at src/libponyrt/actor/actor.c:97```

#0  0x000000000041e788 in actorref_hash (aref=0xffffffff00000000)
    at src/libponyrt/gc/actormap.c:21
#1  0x000000000041df9f in search (map=0x7ffff4e044e8, pos=0x7fffffffe390,
    key=0xffffffff00000000, hash=0x41e778 <actorref_hash>, cmp=0x41e795 <actorref_cmp>)
    at src/libponyrt/ds/hash.c:19
#2  0x000000000041e3e8 in hashmap_put (map=0x7ffff4e044e8, entry=0xffffffff00000000,
    hash=0x41e778 <actorref_hash>, cmp=0x41e795 <actorref_cmp>,
    alloc=0x41c82e <pool_alloc_size>, fr=0x41c875 <pool_free_size>)
    at src/libponyrt/ds/hash.c:135
#3  0x000000000041e1a0 in resize (map=0x7ffff4e044e8, hash=0x41e778 <actorref_hash>,
    cmp=0x41e795 <actorref_cmp>, alloc=0x41c82e <pool_alloc_size>,
    fr=0x41c875 <pool_free_size>) at src/libponyrt/ds/hash.c:68
#4  0x000000000041e456 in hashmap_put (map=0x7ffff4e044e8, entry=0x7ffff5e2bfc0,
    hash=0x41e778 <actorref_hash>, cmp=0x41e795 <actorref_cmp>,
    alloc=0x41c82e <pool_alloc_size>, fr=0x41c875 <pool_free_size>)
    at src/libponyrt/ds/hash.c:144```

(gdb) bt 5
#0  0x00000000004194a2 in object_inc_some (obj=0x0, rc=256)
    at src/libponyrt/gc/objectmap.c:78
#1  0x0000000000418ff3 in gc_acquire (gc=0x7ffff4decab8, aref=0x7ffff1d59140)
    at src/libponyrt/gc/gc.c:355
#2  0x0000000000414e0e in handle_message (actor=0x7ffff4deca00, msg=0x7ffff1d4ed40)
    at src/libponyrt/actor/actor.c:58
#3  0x000000000041507d in actor_run (actor=0x7ffff4deca00)
    at src/libponyrt/actor/actor.c:136
#4  0x000000000041d454 in run (sched=0x636110) at src/libponyrt/sched/scheduler.c:398

(gdb) bt 5
#0  0x00007ffff6c4a4b7 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff6c4b88a in abort () from /usr/lib/libc.so.6
#2  0x00007ffff6c4341d in __assert_fail_base () from /usr/lib/libc.so.6
#3  0x00007ffff6c434d2 in __assert_fail () from /usr/lib/libc.so.6
#4  0x000000000041880f in gc_recvobject (current=0x7ffff4df6400, heap=0x7ffff4df6440,
    gc=0x7ffff4df64b8, p=0x7ffff4624080, f=0x40c9d0 <http_URL_$trace>)
    at src/libponyrt/gc/gc.c:146

(gdb) bt 5
#0  0x0000000000419369 in object_alloc (address=0x7ffff462b540, mark=2)
    at src/libponyrt/gc/objectmap.c:30
#1  0x000000000041974c in objectmap_getorput (map=0x7ffff5e11218,
    address=0x7ffff462b540, mark=2) at src/libponyrt/gc/objectmap.c:112
#2  0x000000000041e9a2 in actorref_getorput (aref=0x7ffff5e11200,
    address=0x7ffff462b540, mark=2) at src/libponyrt/gc/actormap.c:91
#3  0x0000000000418951 in gc_recvobject (current=0x7ffff4dfc000, heap=0x7ffff4dfc040,
    gc=0x7ffff4dfc0b8, p=0x7ffff462b540, f=0x403630 <String_$trace>)
    at src/libponyrt/gc/gc.c:174
#4  0x0000000000419ac6 in pony_traceobject (p=0x7ffff462b540,
    f=0x403630 <String_$trace>) at src/libponyrt/gc/trace.c:62

Thanks! This should be fixed now.

Getting segmentation faults on httpget test.
Using following command to reproduce:
N=0; CD=0; while [ $N -lt 100 ]; do ./httpget http://habrahabr.ru >/dev/null 2>&1; [ $? -ne 0 ] && CD=$((CD+1)); N=$((N+1)); echo $N $CD; done; echo $CD coredumps

With it i am getting up to 90 coredumps out of 100 runs.
(gdb) bt 5
#0  0x00007ffff79a0620 in ssl_session_LHASH_HASH () from /usr/lib/libssl.so.1.0.0
#1  0x00007ffff7618104 in lh_delete () from /usr/lib/libcrypto.so.1.0.0
#2  0x00007ffff79a8058 in timeout_LHASH_DOALL_ARG () from /usr/lib/libssl.so.1.0.0
#3  0x00007ffff761843c in lh_doall_arg () from /usr/lib/libcrypto.so.1.0.0
#4  0x00007ffff79a8e07 in SSL_CTX_flush_sessions () from /usr/lib/libssl.so.1.0.0
(More stack frames follow...)
(gdb) bt
#0  0x00007ffff79a0620 in ssl_session_LHASH_HASH () from /usr/lib/libssl.so.1.0.0
#1  0x00007ffff7618104 in lh_delete () from /usr/lib/libcrypto.so.1.0.0
#2  0x00007ffff79a8058 in timeout_LHASH_DOALL_ARG () from /usr/lib/libssl.so.1.0.0
#3  0x00007ffff761843c in lh_doall_arg () from /usr/lib/libcrypto.so.1.0.0
#4  0x00007ffff79a8e07 in SSL_CTX_flush_sessions () from /usr/lib/libssl.so.1.0.0
#5  0x00007ffff79a25b2 in SSL_CTX_free () from /usr/lib/libssl.so.1.0.0
#6  0x0000000000408011 in ssl_SSLContext__final (this=<optimized out>)
    at /home/loko/project/pony/ponyc/packages/net/ssl/sslcontext.pony:179
#7  0x000000000041bb30 in objectmap_final (map=0x7ffff4de7ad0)
    at src/libponyrt/gc/objectmap.c:133
#8  0x0000000000415fc9 in gc_final (gc=0x7ffff4de7ab8) at src/libponyrt/gc/gc.c:446
#9  0x00000000004189f3 in actor_final (actor=0x7ffff4de7a00)
    at src/libponyrt/actor/actor.c:207
#10 0x000000000041d217 in collect (d=0x7ffff4de7000, per=0x7ffff25e5200)
    at src/libponyrt/gc/cycle.c:541
#11 0x000000000041d54e in ack (d=0x7ffff4de7000, token=0) at src/libponyrt/gc/cycle.c:651
#12 0x000000000041d7e7 in cycle_dispatch (self=0x7ffff4de7000, msg=0x7ffff5deae00)
    at src/libponyrt/gc/cycle.c:730
#13 0x000000000041868b in handle_message (actor=0x7ffff4de7000, msg=0x7ffff5deae00,
    notify=0x7fffffffdd36) at src/libponyrt/actor/actor.c:95
#14 0x00000000004187cb in actor_run (actor=0x7ffff4de7000)
    at src/libponyrt/actor/actor.c:134
#15 0x000000000041e87b in run (sched=0x635010) at src/libponyrt/sched/scheduler.c:405
#16 0x000000000041e905 in run_thread (arg=0x635010) at src/libponyrt/sched/scheduler.c:430
#17 0x000000000041ec3b in scheduler_start (library=false)
    at src/libponyrt/sched/scheduler.c:514
#18 0x000000000041847d in pony_start (library=false) at src/libponyrt/sched/start.c:145
#19 0x00007ffff6c37800 in __libc_start_main () from /usr/lib/libc.so.6
#20 0x0000000000402bf9 in _start ()

Nice catch. This is a completely different bug from the original one. I've found the problem, working on a solution now.

This should be fixed in HEAD now.

Still get 2 coredumps on 100.
System: archlinux x86_64
(gdb) bt
#0  0x00007f4ca5235e94 in free () from /usr/lib/libc.so.6
#1  0x00007f4ca5ae8f1d in CRYPTO_free () from /usr/lib/libcrypto.so.1.0.0
#2  0x00007f4ca5bbb6e7 in sk_free () from /usr/lib/libcrypto.so.1.0.0
#3  0x00007f4ca5c0b254 in X509_VERIFY_PARAM_free () from /usr/lib/libcrypto.so.1.0.0
#4  0x00007f4ca5f465a1 in SSL_CTX_free () from /usr/lib/libssl.so.1.0.0
#5  0x00000000004081f1 in ssl_SSLContext__final (this=<optimized out>) at /home/loko/project/pony/ponyc/packages/net/ssl/sslcontext.pony:179
#6  0x000000000041bd34 in objectmap_final (map=0x7f4ca338bad0) at src/libponyrt/gc/objectmap.c:133
#7  0x00000000004161dc in gc_final (gc=0x7f4ca338bab8) at src/libponyrt/gc/gc.c:446
#8  0x0000000000418bc5 in actor_final (actor=0x7f4ca338ba00) at src/libponyrt/actor/actor.c:205
#9  0x000000000041d84d in final (self=0x7f4ca338b000) at src/libponyrt/gc/cycle.c:688
#10 0x000000000041dbda in cycle_terminate (forcecd=false) at src/libponyrt/gc/cycle.c:821
#11 0x000000000041e558 in read_msg (sched=0x10c1010) at src/libponyrt/sched/scheduler.c:169
#12 0x000000000041e62a in quiescent (sched=0x10c1010, tsc=216272832638919) at src/libponyrt/sched/scheduler.c:204
#13 0x000000000041e7fc in steal (sched=0x10c1010) at src/libponyrt/sched/scheduler.c:284
#14 0x000000000041ea8b in run (sched=0x10c1010) at src/libponyrt/sched/scheduler.c:396
#15 0x000000000041eb84 in run_thread (arg=0x10c1010) at src/libponyrt/sched/scheduler.c:439
#16 0x000000000041eeba in scheduler_start (library=false) at src/libponyrt/sched/scheduler.c:523
#17 0x000000000041864f in pony_start (library=false) at src/libponyrt/sched/start.c:145
#18 0x0000000000414da7 in main () at /home/loko/project/pony/ponyc/packages/net/ssl/sslinit.pony:13

This appears to be fixed now. Thanks!


Upload and download conan artifact to make ut build faster

Issue: #429

/lgtm

/lgtm

CPU image build time with ASAN and COVERAGE enabled: 26 minutes -> 10 minutes
pyknowhere build time: 21 minutes -> 4 minutes


Add IPY operation detail

We have added IPY Operation detail, this is based in the following documentation:

Hey @lauragilgz, sorry for the mess, @frantisekrokusek and I talked about this PR and we did some tests but I realize that it might add a bit of confusion here. 🙏
@frantisekrokusek and I will have a PP around those issues this morning, I'll keep you posted!

@RDeckard Sure thing! No problem at all 😄


[Gateway] Fix BRIDGE ALL

Codecov Report

Merging #354 (74bb2b8) into develop (afbded3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #354   +/-   ##
========================================
  Coverage    53.79%   53.79%
========================================
  Files           13       13
  Lines          329      329
  Branches        58       58
========================================
  Hits           177      177
  Misses         152      152

Flag
Coverage Δ

core-utils
53.79% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 afbded3...74bb2b8. Read the comment docs.


Won't run when using design rule set.

This one is weird and I didn't see it elsewhere.
When using the design rule set I get an error and it closes. When I remove it, it works fine.
From Circle CI with design:
#!/bin/bash -eo pipefail
./vendor/bin/phpmd ./init.php xml cleancode,codesize,controversial,design,unusedcode,naming

Exited with code 1

Without design:
#!/bin/bash -eo pipefail
./vendor/bin/phpmd ./init.php xml cleancode,codesize,controversial,unusedcode,naming

<?xml version="1.0" encoding="UTF-8" ?>
<pmd version="@project.version@" timestamp="2017-09-06T20:00:17+00:00">
</pmd>

Here is my CircleCI script:
version: 2
jobs:
  build:
    docker:
      - image: circleci/php:7.1-browsers
    working_directory: ~/repo
    steps:
      - checkout
      - restore_cache:
          keys:
          - v1-dependencies-{{ checksum "composer.json" }}
          - v1-dependencies-
      - run: composer install -n --prefer-dist
      - save_cache:
          paths:
            - ./vendor
          key: v1-dependencies-{{ checksum "composer.json" }}
      - run: ./vendor/bin/phpmd ./app/addons xml cleancode,codesize,controversial,design,unusedcode,naming

composer.json
{
    "name": "cwilsontv",
    "description": "phpmd test",
    "authors": [
        {
            "name": "cwilsontv",
            "email": ""
        }
    ],
    "require": {
    },
    "require-dev": {
        "phpmd/phpmd" : "@stable",
    },
    "autoload": {
        "psr-0": {

        },
        "classmap": [

        ]
    },
    "scripts": {

    }
}

Everything is completely barebones, just a file, composer, and phpmd. The php file I point it at doesn't seem to matter either.
Same thing happens locally on two different machines when I run it through the command line, but at least I get a message:
C:\src\phpmdtest>php .\vendor\phpmd\phpmd\src\bin\phpmd .\init.php xml naming
<?xml version="1.0" encoding="UTF-8" ?>
<pmd version="@project.version@" timestamp="2017-09-07T14:52:26+00:00">
</pmd>

C:\src\phpmdtest>php .\vendor\phpmd\phpmd\src\bin\phpmd .\init.php xml design
PHP Warning:  file_get_contents(design): failed to open stream: Permission denied in C:\src\phpmdtest\vendor\phpmd\phpmd\src\main\php\PHPMD\RuleSetFactory.php on line 551
PHP Notice:  Trying to get property of non-object in C:\src\phpmdtest\vendor\phpmd\phpmd\src\main\php\PHPMD\RuleSetFactory.php on line 556

Not sure how it can be a permission issue for just design, especially since composer installs everything.
Next trouble shooting steps I'll try:

Use 7.0 instead of 7.1
Use a ruleset xml to specify the rules to run.

This works if I make a custom xml ruleset.

Has this been resolved?


Update ember docs for<EMAIL_ADDRESS>

Issue: Ember docs have unnecessary steps
What I did
In<EMAIL_ADDRESS>the addon installs the necessary @storybook/ember dependencies and creates files needed to start using Storybook. Also removed section about creating a package.json file via npm init since ember applications & addons should already be configured via ember-cli.
How to test
Create an ember app via ember-cli & ember install ember-cli-storybook

Is this testable with Jest or Chromatic screenshots?
Does this need a new example in the kitchen sink apps?
Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

I don't see any dep on @storybook/ember in ember-cli-storybook, so I don't think this is an optional step.
@gabrielcsapo can you confirm?

This afterInstall step in the addon configuration will install the needed deps.
https://ember-cli.com/api/classes/Blueprint.html#method_addPackagesToProject

OK thanks for the clarification @billpull -- I don't use ember so I'll let @gabrielcsapo
I just didn't see reference to @storybook/ember anywhere in ember-cli-storybook so it looked suspicious 😉

@shilman would you be able to help me publish ember-cli-storybook under @storybook? So we can keep the library under the storybook namespace.

Merging this as this is accurate right now, will update when we update the location of ember-cli-storybook. Thanks @billpull!

Wait is this needed? This information exists since I added it in https://github.com/storybooks/storybook/commit/d6ed6fffc2ec22e845054b48384aabaddc0daa5f?

@shilman we probably need to revert this.

@gabrielcsapo Sure. Let's sort it out after v5 is released


Correctly scope configuration for code snippets and overview generation

Both the overview generation and code snippets injection are using the exec-maven-plugin however the configurations for both weren't scoped to the execution which meant that the code snippets was overriding the overview generation.

/azp run java - appconfiguration


feat: Label integration tests; update or eliminate makefile

Summary
When running locally, it would be useful if we could rely on the labels to filter integration tests. For instance --query-filter='!pulsar && !redis' to run all of the tests other than Pulsar and Redis tests.
We already have many of the tests properly labeled. For example: https://github.com/kaskada-ai/kaskada/blob/main/tests/integration/api/mat_pulsar_to_obj_store_test.go#L28
However, some of the tests rely on Pulsar without being labeled. For example: https://github.com/kaskada-ai/kaskada/blob/main/tests/integration/api/queries_v1_test.go#L36
In general, we should prefer to label entire functions as we currently do. But based on the Gingkgo docs, there are other options if we really need these tests that use Pulsar internally:
It("can save books remotely", Label("network", "slow", "library query") {
  if Label("performance").MatchesLabelFilter(GinkgoLabelFilter()) {
    exp := gmeasure.NewExperiment()
    // perform some benchmarking with exp...
  }
  // rest of the saving books test
})

(from https://onsi.github.io/ginkgo/#spec-labels)
The other part of this is that the current structure of the makefile makes it difficult to pass arguments -- we need to create additional targets for every change. We should look at passing other arguments through the makefile, or using a shell script or something. Then we could more easily run something like ENV=local-local go run github.com/onsi/ginkgo/v2/ginkgo ./... --label-filter='!pulsar && !redis' (note that this also omits the -vv since the extra verbosity is just spammy in many cases).

#490 adds the remaining pulsar test labels.

I think we should make a small CLI tool for running the most of the commands currently in the Makefile.
Options on commands would be much more straightforward than enumerating every potential command in the Makefile.

I'm 50/50 -- I think it may be nice to just document the commands and people can create aliases if they want? Specifically, it seems easier to "know" how things are being run if we just document "use the ginkgo runner". But :shrug:


There is no way to add Files to the Context for Large Projects

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude 3.5 Sonnet
What happened?
For projects with a large numbers of files, there is a hard limit to the number of files in the file list. Any files above this limit won't appear in @ search or browse.
Steps to reproduce

Open a project with a large number of files
Try to @ search for or browse for a deeply nested file
It won't be in the list

Relevant API REQUEST output
No response
Additional context
To brainstorm some potential solutions:

Increase the file limit

Make the file limit configurable

It is possible to exclude unneeded files through .gitignore but this might work better through a Cline specific file e.g. .clineignore

Add other ways to add files to the context e.g.

Right click in Explorer to add to context

Right click on an open file's tab to add to context

Add an @ option for adding an already open file to context

I'm having trouble just adding files to the context using @. It seems to work on and off, not sure if its vscode or the plugin.

same

Same Here. Start typing @ lets me choose a single file. I can't add the whole root directory

In my case it has something to do with multi directory workspaces

I noticed I don't have to add my whole directory. Whenever I have a question about my workspace content/project I just type the question! Cline automatically picks/sends/includes the files that are required to be changed

it's too buggy


Removing unnecessary templates

Role poa-parity keeps in its templates folder almost all the templates that is not used by poa-parity role, but is used in another roles, where the similar templates already located.
We should remove them since they are only confusing people, who would like to dig into the playbooks code.

Closing because of #133


Remove file headers

Q
A

QA
yes

Description
Remove file headers

Overlooked that there is an open PR, closing in favor of #29


Unable to find an existing installation of library: tbb

I'm using openvino 2022.3.0 on ubuntu 22.04 and encountered the following building error:
The following warnings were emitted during compilation:

warning: Found library to link against: /home/user/openvino_2022.3.0/runtime/lib/intel64/libopenvino.so
warning: Found library to link against: /home/user/openvino_2022.3.0/runtime/lib/intel64/libopenvino_c.so

error: failed to run custom build command for `openvino-sys v0.4.2 (https://github.com/intel/openvino-rs#0bc3a8f1)`

Caused by:
  process didn't exit successfully: `/home/user/test/target/release/build/openvino-sys-ff82748da3e36088/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs
  cargo:rerun-if-changed=Cargo.toml
  cargo:rerun-if-changed=src/generated/mod.rs
  cargo:rerun-if-changed=src/generated/functions.rs
  cargo:rerun-if-changed=src/generated/types.rs
  cargo:rerun-if-changed=src/linking/dynamic.rs
  cargo:rerun-if-changed=src/linking/runtime.rs
  cargo:rerun-if-changed=src/linking/mod.rs
  cargo:rerun-if-changed=src/lib.rs
  cargo:rustc-cfg=feature="dynamic-linking"
  cargo:warning=Found library to link against: /home/user/openvino_2022.3.0/runtime/lib/intel64/libopenvino.so
  cargo:warning=Found library to link against: /home/user/openvino_2022.3.0/runtime/lib/intel64/libopenvino_c.so

  --- stderr
  thread 'main' panicked at 'Unable to find an existing installation of library: tbb', /home/user/.cargo/git/checkouts/openvino-rs-d79b91ff7f77ee0b/372f4c7/crates/openvino-sys/build.rs:152:13

OpenVino is built from source using:
git clone -b 2022.3.0 https://github.com/openvinotoolkit/openvino.git
cd openvino/
git submodule update --init --recursive
chmod +x install_build_dependencies.sh
sudo ./install_build_dependencies.sh
mkdir build && cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make --jobs=$(nproc --all)
cmake --install . --prefix ~/openvino_2022.3.0

It seems that it can't find libtbb, because it is in different path than defined search paths:
$ ldconfig -p | grep libtbb
        libtbbmalloc_proxy.so.2 (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbbmalloc_proxy.so.2
        libtbbmalloc_proxy.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbbmalloc_proxy.so
        libtbbmalloc.so.2 (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbbmalloc.so.2
        libtbbmalloc.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbbmalloc.so
        libtbb.so.12 (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbb.so.12
        libtbb.so.2 (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbb.so.2
        libtbb.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libtbb.so

Setting export LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/ fixes the problem. I'm not sure where exactly the cause is, maybe Ubuntu 22.04 moved libtbb from /usr/lib to /lib/x86_64-linux-gnu?

Thanks for the report. The reason for this is a hole in the openvino-finder code. It doesn't understand how to find shared libraries on the default system paths. In the new 2023 release, OpenVINO will install itself to more traditional locations (like /lib/x86_64-linux-gnu, e.g.) so the openvino-finder will have to gain this ability soon-ish. I have been mulling over how to best do this without listing all the locations for all of the supported OSes (suggestions welcome!).

In the new 2023 release, OpenVINO will install itself to more traditional locations (like /lib/x86_64-linux-gnu, e.g.) so the openvino-finder will have to gain this ability soon-ish.

This is awesome. It was a struggle each time I needed to install OpenVino (except pip versions). The setupvars.sh is also weird, I would expect the installed library to be always available like all other libs.

I have been mulling over how to best do this without listing all the locations for all of the supported OSes (suggestions welcome!).

I think good examples here are gstreamer-rs and opencv-rust. Both of them primarily use pkg-config, which is the prefered method for linux, but works okay for mac and windows too. In addition to that, opencv also uses cmake and vcpkg as fallback methods. Listing all search paths is pretty uncommon. Environment variables are mostly used to override auto discovery.

Yeah, I had looked at pkg-config but was concerned about the non-Linux OSes. The biggest roadblock at the moment is being able to test this in those environments.

Took a look at this today and found some problems:
Problem #1: the pkg-config crate expects to be used at build time, not run time (and we have a --features runtime-linking need)

it expects to shell out to call the pkg-config binary — is this a performance concern?
additionally it emits cargo build.rs text; I was able to disable this with .env_metadata(false).cargo_metadata(false)

Problem #2: it doesn't find the openvino_c library

we would need to have a file like /usr/lib64/pkgconfig/openvino_c.pc, I think, but OpenVINO does not install this
I also do not see a tbb.pc file, which may also be necessary (re: this issue)

Problem #1: the pkg-config crate expects to be used at build time, not run time (and we have a --features runtime-linking need)

Yeah it's supposed to only be used in build.rs. Not sure if using it at runtime has issues. Btw, what is the purpose of runtime linking and how is it different from dynamic? Is it so that user can specify lib path at runtime?

it expects to shell out to call the pkg-config binary — is this a performance concern?

I don't see a reason why it would be. pkg-config is used by many C/C++ build systems and Rust libs. For end users openvino's build.rs would be invoked only once for initial clean build. Subsequent incremental builds do not invoke build.rs unless openvino-rs itself is modified.

additionally it emits cargo build.rs text; I was able to disable this with .env_metadata(false).cargo_metadata(false)

It is important, because it emits rerun-if-changed commands to rerun build.rs when environment variables for pkg-config are changed.

Problem #2: it doesn't find the openvino_c library

we would need to have a file like /usr/lib64/pkgconfig/openvino_c.pc, I think, but OpenVINO does not install this

I wonder if you could use the regular openvino.pc? It seems to include both openvino and openvino_c. You could filter out the C++ libs.

I also do not see a tbb.pc file, which may also be necessary (re: this issue)

It works for me on Ubuntu 22.04. pkg-config --debug tbb shows that it uses /usr/lib/x86_64-linux-gnu/pkgconfig/tbb.pc. What OS were you using?

I'm on Fedora, so there might be some differences there.
Let me explain a bit about openvino-finder: the openvino crate is used by Wasmtime for one of its wasi-nn backends. The Wasmtime binary doesn't want to have a library dependency on openvino; in other words, Wasmtime should work fine whether OpenVINO is installed on the system or not. If it is, then wasi-nn function calls will need to be satisfied by a shared library that is loaded at runtime (e.g., dlopen). The openvino-finder crate locates the shared library (see find for the logic there) and the openvino-sys crate binds to it using the libloading crate (which on Linux eventually delegates to dlopen). All of this runtime-linking behavior is enabled with --features runtime-linking. But, since users may also want to link directly to the OpenVINO libraries (I call this "dynamic linking" in the build.rs), that is also a possibility in the build.rs file; this case re-uses openvino-finder but emits the right Cargo incantations in build.rs.
Hopefully that explains the complexity here: we need to support both dynamic and runtime linking and the support needs to be reliable. And there's another twist: with OpenVINO 2022.3 (I misspoke earlier, it is not 2023), the files can be either on the system paths (when installing from an RPM, DEB, etc.) or on the custom paths that openvino-finder already understands (when installing from a TAR or ZIP). I can't "just use pkg-config" because I would like this to work everywhere (not just Ubuntu) and with different kinds of installation methods. I'm still thinking through what the options are — suggestions welcome!

Thanks for the in depth explanation. The runtime linking issue is now clear. I assume there are other libraries that do runtime linking (not even necessarily rust), it would be interesting to see how they do it. I will report when if I find any examples worth considering.
The reason why I'm suggesting pkg-config is because that's what I observed from the whole linux ecosystem. Almost all gnu and alike libraries have pkg-config scripts so it's not an Ubuntu thing. The biggest problem with pkg-config is probably windows, which is a bit of a wild west in terms of library auto discovery.

I believe this should now all be fixed in v0.5.0 — let me know what you think!


How to import project?

My steps:
File -> New -> Project from version control -> github
Git URL:
https://github.com/googlesamples/android-testing-templates.git
then I see this:

I clicked "Configure"
and see this:

I clicked "ok
and it does not work:

"

Probably because the project is inside a directory. Just use git clone.
$ git clone https://github.com/googlesamples/android-testing-templates


Stuck in a loop of "DEBUG: No data for: [query] | retrying in [quantity] seconds

How do I stop this?

I have the same issue and receive an email with a confirmation code at the same time. Is there any option to provide that confirmation code to twitter-api-client?

same issue, was working, started asking for confirmation code. any idea how to fix this?

Hi again, I did manage to fix it. Here's how: I usually code from my own PC and then push to my server, my server is in Paris while I live in Lebanon, naturally, It would think thats suspicious, All I had to do is get a VPN to Paris, login with it and do email verification, then It will no longer think its suspicious, and it will function normally. I thank the developers of this library for his hard work because it helped me circumvent the use of Twitter's paid API, alongside public info limitations like age restrictions. Great work!


Set up hello email to direct to Jon

This is set up. Close once Jon confirms that the email alias I set up in gsuite works.

confirmed:  e-mail is directed to<EMAIL_ADDRESS> THANK YOU!


Hello, I am very interested in your work, but why can't I find your paper

Hello, I am very interested in your work, but why can't I find your paper：Pre-training Vision Transformers for Visual Times Series Forecasting

Hello,
it's still under review in International Conference on Pattern Recognition (ICPR 2024). It will be available in about 1-2 weeks.

May your paper be accepted soon!


Microsoft.OperationalInsights: Update big commitment tiers (capacityReservation)

Add support for large commitment tiers

You are updating an existing API, the pipeline didn't flag it as breaking change but you'll need to request a breaking change approval first:
Breaking changes review (Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:
The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

You are updating an existing API, the pipeline didn't flag it as breaking change but you'll need to request a breaking change approval first:
Breaking changes review (Step 1) If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you, you must follow the breaking changes process. IMPORTANT This applies even if: The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes. You believe there is no need for you to request breaking change approval, for any reason. Such claims must be reviewed, and the process is the same.

Please get breaking changes reviewed and approved before ARM reviews this PR.


Edit task modal: it should not be possible to save a task with done and cancelled date

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.
[X] I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
[X] I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description
In the current edit task modal it is possible to set done and cancelled date to the task. I suggest that this kind of task is wrong and this should not happen.
✔ Solution
Make the Apply button unusable while done and cancelled valid dates are present, highlight done and cancelled date input blocks with red.
❓ Alternatives
Hide/show done and cancelled date based on status:

if status is todo, do not show either
if status is done, show only done date
if status is cancelled, show only cancelled date

📝 Additional Context
No response

At first glance this seems like a duplicate of:

https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2986

Indeed, I duplicated myself,

Hahah. And you even searched the "I searched previous Ideas..." 😉

The labels are pretty useful for those searches... (thanks for adding them)


td template v-if not working on IE 10 & 11, IE 9 is OK

Version
2.4.2
Reproduction link
https://jsfiddle.net/j4o16zzk/
Steps to reproduce

123123
123123

What is expected?
all IE version is ok
What is actually happening?
IE9 OK
IE10,IE11 NG

Different permissions show different UI

This is one of the limitations of in dom templates, due to browsers, see https://vuejs.org/v2/guide/components.html#DOM-Template-Parsing-Caveats for more 🙂


checkHDUs params not loaded

Using the function get_scalar_metrics(selected_process_id, cam), 'checkHDUs' is not appearing among the keys of the loaded dictionary.
This field 'params' inside this dictionary is now necessary to read the exposure time.

@felipeaoli is this still happening?

This is no longer necessary since we have moved to mergedQA. I'm closing this issue now.


Add spge-bg.txt

Sofia Vocational High School of Electronics "John Atanasoff". We would love to have the chance to participate as well. =)

@Stev3nT #745 fixed the Travis build. If you close and re-open this thread, it should trigger a new Travis build.

Reopened at #820


log without context manually

In Elmah mvc version, you can log manually for example in projects without HttpContext.
I can't find a way to that.

Use ElmahExtensions.RiseError (version 1.2.2)

Nice! thanks!

It doesn't work on mine.

It doesn't work for me with .Net Core 3.0 and Elmah Core version 1.2.5 and Elmah Core Sql 1.2.5.


[WIP] Filtering behaviour isn't comprehensively documented

[placeholder that I will come back to]

Hey! I took a stab at documenting filtering here: https://github.com/cds-snc/nrcan_api/blob/master/docs/using_the_api.md
Maybe something can be added to make it more clear?

This has been addressed


autocompletion is not working after import formKitTailwind from '@formkit/themes/tailwindcss'

Reproduction
http
Describe the bug
HI by using the formkittailwind plugin the autocompletion of webstorm tailwind does not work anymore.
When I open the project in Visual Studio everything works fine.
Hope you can help me out.
Cheers,
Eric
Environment
• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

@ericlaaper Is there a reproduction you can make/any more information you can give?


[tvOS] Accessibility properties don't seem to work

Description
I am working with accessibility support on my app. I tried out TalkBack, which worked as expected on react-native-tvos.
But VoiceOver from tvOS seems to not work properly with react-native-tvos.
I add accessible properties on my Texts, and they're still not focusable via VoiceOver. I try accessibilityActions with 'activate' and I do not have my onAccessibilityAction callbacks triggered.
They do work properly on AndroidTV.
Any idea?
React Native Version
0.72.6
Output of npx react-native info

Output of `npx react-native info`
info Fetching system and libraries information...
System:
  OS: macOS 14.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 308.47 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.3.1
    path: ~/Library/Caches/fnm_multishells/24196_1699375881319/bin/node
  Yarn:
    version: 1.22.19
    path: ~/Library/Caches/fnm_multishells/24196_1699375881319/bin/yarn
  npm:
    version: 9.6.7
    path: ~/Library/Caches/fnm_multishells/24196_1699375881319/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.2
    path: /Users/pierpo/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK:
    API Levels:
      - "28"
      - "30"
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 34.0.0
    System Images:
      - android-24 | Google APIs ARM 64 v8a
      - android-31 | Google TV ARM 64 v8a
      - android-31 | Google APIs ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10811636
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.6
    path: /usr/bin/javac
  Ruby:
    version: 3.0.3
    path: /Users/pierpo/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false

Steps to reproduce
I put the following code in packages/rn-tester/js/RNTesterAppShared.js, and I activated VoiceOver in the tvOS settings.
  return (
    <RNTesterThemeContext.Provider value={theme}>
      <View style={{backgroundColor: 'black', padding: 100, gap: 20}}>
        <Text
          accessible
          accessibilityLabel="read me if you can"
          style={{color: 'white', fontSize: 40}}>
          Hello, I want to be focused through accessibility but it doesn't work
          :'(
        </Text>
        <View
          accessible
          accessibilityLabel="try to focus this box if you can"
          style={{backgroundColor: 'green', height: 50, width: 50}}
        />
        <TouchableOpacity
          accessible
          accessibilityRole="button"
          accessibilityActions={[{name: 'activate'}]}
          onAccessibilityAction={() => console.log('did I work? do I didnt')}
          style={{backgroundColor: 'grey', padding: 10}}>
          <Text style={{color: 'white', fontSize: 40}}>FIRST BUTTON</Text>
        </TouchableOpacity>
        <TouchableOpacity
          accessible
          accessibilityRole="button"
          accessibilityActions={[{name: 'activate'}]}
          onAccessibilityAction={() => console.log('did I work? do I didnt')}
          style={{backgroundColor: 'grey', padding: 10}}>
          <Text style={{color: 'white', fontSize: 40}}>SECOND BUTTON</Text>
        </TouchableOpacity>
      </View>
    </RNTesterThemeContext.Provider>
  );

Snack, screenshot, or link to a repository
In this example, I can only focus the two TouchableOpacity, and that's it. I would expect the green square and the text to be focusable as well.

I'll take a look.


Surviving mutations discovered by Stryker Mutator

Updated: The surviving mutations indicate missing test cases that need to be added now.
There are a few mutations that were missed by Stryker 2.1.0 and now detected by Stryker 2.5.0 & 3.1.0 (see below).

Surviving mutations discovered by Stryker Mutator 3.1.0 (with diff highlighting):
1. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:2:27
-   const logSymbols = require('log-symbols');
+   const logSymbols = require("");

Ran all tests for this mutant.
7. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:17:6
-       ? `
-   ${emoji.get('bulb')} check out the example app in ${moduleName}/${exampleName}
-   ${emoji.get('bulb')} recommended: run Metro Bundler in a new shell
-   ${logSymbols.info} (cd ${moduleName}/${exampleName} && yarn start)
-   ${emoji.get('bulb')} enter the following commands to run the example app:
-   ${logSymbols.info} cd ${moduleName}/${exampleName}
-   ${platforms.split(',').map(platform =>
-     `${logSymbols.info} react-native run-${platform}`
-   ).join(`
-   `)}
-   ${logSymbols.warning} first steps in case of a clean checkout
-   ${logSymbols.info} run Yarn in ${moduleName}/${exampleName}/ios
-   ${logSymbols.info} (cd ${moduleName}/${exampleName} && yarn)
-   ${logSymbols.info} do \`pod install\` for iOS in ${moduleName}/${exampleName}/ios
-   ${logSymbols.info} cd ${moduleName}/${exampleName}
-   ${logSymbols.info} (cd ios && pod install)
-   `
+       ? ""

Ran all tests for this mutant.
8. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:18:12
-   ${emoji.get('bulb')} check out the example app in ${moduleName}/${exampleName}
+   ${emoji.get("")} check out the example app in ${moduleName}/${exampleName}

Ran all tests for this mutant.
9. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:19:12
-   ${emoji.get('bulb')} recommended: run Metro Bundler in a new shell
+   ${emoji.get("")} recommended: run Metro Bundler in a new shell

Ran all tests for this mutant.
10. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:21:12
-   ${emoji.get('bulb')} enter the following commands to run the example app:
+   ${emoji.get("")} enter the following commands to run the example app:

Ran all tests for this mutant.
11. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:23:18
-   ${platforms.split(',').map(platform =>
+   ${platforms.split("").map(platform =>

Ran all tests for this mutant.
12. [Survived] ArrowFunction
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:23:27
-   ${platforms.split(',').map(platform =>
-     `${logSymbols.info} react-native run-${platform}`
+   ${platforms.split(',').map(() => undefined

Ran all tests for this mutant.
13. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:24:2
-     `${logSymbols.info} react-native run-${platform}`
+     ""

Ran all tests for this mutant.
15. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:25:7
-   ).join(`
-   `)}
+   ).join("")}

Ran all tests for this mutant.
27. [Survived] ArithmeticOperator
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:62:34
-   ${emoji.get('clock9')}  It took ${Date.now() - beforeCreation}ms.
+   ${emoji.get('clock9')}  It took ${Date.now() + beforeCreation}ms.

Ran all tests for this mutant.
30. [Survived] ConditionalExpression
/home/brodybits/dev/create-react-native-module/lib/cli-command.js:67:10
-         if (err.stack) {
+         if (true) {

Ran all tests for this mutant.
102. [Survived] ArrayDeclaration
/home/brodybits/dev/create-react-native-module/lib/cli-program.js:19:20
-   (command.options || [])
+   (command.options || ["Stryker was here"])

Ran all tests for this mutant.
107. [Survived] ArrowFunction
/home/brodybits/dev/create-react-native-module/lib/cli-program.js:23:18
-       opt.parse || (value => value),
+       opt.parse || (() => undefined),

Ran all tests for this mutant.
236. [Survived] BlockStatement
/home/brodybits/dev/create-react-native-module/lib/lib.js:264:26
-                 } catch (e) {
-                   console.error('pod --version failure, aborting with broken example app');
-                   throw (e);
-                 }
+                 } catch (e) {}

Ran all tests for this mutant.
237. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/lib.js:265:30
-                   console.error('pod --version failure, aborting with broken example app');
+                   console.error("");

Ran all tests for this mutant.
241. [Survived] StringLiteral
/home/brodybits/dev/create-react-native-module/lib/lib.js:275:30
-                   console.error('pod install failure, aborting with broken example app');
+                   console.error("");

Ran all tests for this mutant.
242. [Survived] BlockStatement
/home/brodybits/dev/create-react-native-module/lib/lib.js:274:26
-                 } catch (e) {
-                   console.error('pod install failure, aborting with broken example app');
-                   throw (e);
-                 }
+                 } catch (e) {}

Ran all tests for this mutant.
449. [Survived] ArrayDeclaration
/home/brodybits/dev/create-react-native-module/templates/index.js:8:17
-   module.exports = [].concat(
+   module.exports = ["Stryker was here"].concat(

Ran all tests for this mutant.

Most of these should be covered by PR #376. There are very few mutants left, now visible from the Stryker dashboard.


SMS channel seems to have stopped working

C# - latest version of the framework (was previously working in this version)
Works fine in the portal test chat box and also via the emulator pointed to the live URL.  However, SMS via Twilio which has been working for weeks all of a sudden now responds only with:
Sent from your Twilio Trial account - _Sorry, -my bot name- is having a problem responding right now._
Any ideas?
TIA,
-r

Are you still seeing this issue?  If so, please add your botId (or email it to<EMAIL_ADDRESS>and we'll look in our logs and see if we can determine the cause.

Thanks I sent my bot id to the email address you provided.  It is still occurring.  I tried removing the channel and recreating it with my twilio details and it still occurred.  I should mention that even when it was working I regularly got emailed error reports from Twilio such as the one below:
Notification SID
NOed54288900706a12ffcb215e34846b43
Error
11200 HTTP retrieval failure
Description
An attempt to retrieve content from https://sms.botframework.com/api/sms returned the HTTP status code .

Thanks for your assistance with this.  Sending /deleteprofile to the framework and clearing my profile data seems to have resolved this.
-r

I am experiencing the same issue with just Twilio. Using nodejs and botbuilder v3.8.0.


custom resource changes

This looks great, looking forward to merging this!
The only problem I can see is that when a ViewDefinition declares one of the profiles, it seems to cause an error.

Fixed next release of the IG publisher


Pipeline export dialog checkbox not working

When exporting a pipeline, the checkbox to the field Replace if file already exists looks off and doesn't allow being checked anymore.

Turns out the checkbox was being checked, only the checkmark not correctly displayed.
This was because it was inheriting CSS height and appearance props from lab input style.
This part of the code hasn't changed for lab3, but it did change how the input is being displayed somehow. We should check an example used in lab to make sure nothing's broken on their end.


[Bug] resetProperties didn't work when using CPU rendering

Describe the Bug
Hi, When I initialize cornerstonejs/core using "useCPURendering: true", the StackViewport api resetProperties can not work correctly. Is it because the resetProperties function can't be used when rendering with the CPU, or what?
Steps to Reproduce

init cornerstonejs/core with useCPURendering:true

Take the example in the cornerstone3D core library: packages\core\examples\stackAPI

Reset Viewport Button casue an uncaught error

The current behavior

The expected behavior
Reset StackViewport properties correctly
OS
Windows11
Node version
16.17.1
Browser
Edge 120.0.2210.144

And I have these errors:
1)

2)

3)

4)

5)

cpu rendering is not as feature rich as gpu rendering, so there might be some bugs

I am also facing same issue. Any solution on this?

We don't really have long term plan to support cpu. There might be a simple fix but don't have bandwidth to fix it unfortunately


Nginx 安装失败

Try mirror server https://repo.istoreos.com/repo
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Installing app-meta-nginx (0.0.1-1) to root...
Downloading https://repo.istoreos.com/repo/all/meta/app-meta-nginx_0.0.1-1_all.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency luci-nginx for luci-nginxer
 * pkg_hash_fetch_best_installation_candidate: Packages for luci-nginxer found, but incompatible with the architectures configured
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for app-meta-nginx:
 *      luci-nginx
 * opkg_install_cmd: Cannot install package app-meta-nginx.
Try origin server https://istore.linkease.com/repo
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Installing app-meta-nginx (0.0.1-1) to root...
Downloading https://istore.linkease.com/repo/all/meta/app-meta-nginx_0.0.1-1_all.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency luci-nginx for luci-nginxer
 * pkg_hash_fetch_best_installation_candidate: Packages for luci-nginxer found, but incompatible with the architectures configured
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for app-meta-nginx:
 *      luci-nginx
 * opkg_install_cmd: Cannot install package app-meta-nginx.
Fetch feed list for x86_64
Update feeds index
Downloading https://istore.linkease.com/repo/all/nas_luci/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/is_nas_luci
Downloading https://istore.linkease.com/repo/all/store/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/is_store
Downloading https://istore.linkease.com/repo/x86_64/nas/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/is_nas
Downloading https://istore.linkease.com/repo/all/compat/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/istore_compat
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/targets/x86/64/packages/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_core
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/base/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_base
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/helloworld/Packages.gz
*** Failed to download the package list from https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/helloworld/Packages.gz

Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/kenzo/Packages.gz
*** Failed to download the package list from https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/kenzo/Packages.gz

Downloading https://mirrors.cloud.tencent.com/lede/releases/18.06.9/packages/x86_64/luci/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_luci
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/packages/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_packages
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_luci/Packages.gz
*** Failed to download the package list from https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_luci/Packages.gz

Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_packages/Packages.gz
*** Failed to download the package list from https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_packages/Packages.gz

Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/routing/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_routing
Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/small/Packages.gz
*** Failed to download the package list from https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/small/Packages.gz

Downloading https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/telephony/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/openwrt_telephony
Downloading https://istore.linkease.com/repo/all/meta/Packages.gz
Updated list of available packages in /tmp/is-root//tmp/opkg-lists/is_meta
Collected errors:
 * opkg_download: Failed to download https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/helloworld/Packages.gz, wget returned 8.
 * opkg_download: Failed to download https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/kenzo/Packages.gz, wget returned 8.
 * opkg_download: Failed to download https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_luci/Packages.gz, wget returned 8.
 * opkg_download: Failed to download https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/passwall_packages/Packages.gz, wget returned 8.
 * opkg_download: Failed to download https://mirrors.cloud.tencent.com/lede/snapshots/packages/x86_64/small/Packages.gz, wget returned 8.
Try origin server https://istore.linkease.com/repo
Multiple packages (libgcc1 and libgcc1) providing same name marked HOLD or PREFER. Using latest.
Installing app-meta-nginx (0.0.1-1) to root...
Downloading https://istore.linkease.com/repo/all/meta/app-meta-nginx_0.0.1-1_all.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency luci-nginx for luci-nginxer
 * pkg_hash_fetch_best_installation_candidate: Packages for luci-nginxer found, but incompatible with the architectures configured
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for app-meta-nginx:
 *      luci-nginx
 * opkg_install_cmd: Cannot install package app-meta-nginx.

这是你自己的固件有问题，要么固件太老，要么配置的软件源没法用。


Update package json int

See main pr

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 401761473aa8f97346456309beba93e89e24179f


sp_rename should update the object name in babelfish_schema_permission catalog

Description
We had introduced a catalog babelfish_schema_permission to hold the information about objects and its permissions. With this change, sp_rename should update the object name in babelfish_schema_permission catalog so that the permission is tracked correctly in the catalogs.
Issues Resolved
Task: BABEL-4485
Signed-off-by: Shalini Lohia<EMAIL_ADDRESS>Test Scenarios Covered

Use case based - Added

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 37 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 72.781%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
40967

Relevant Lines:
56288

💛  - Coveralls

I think this has happened a number of times where we add a catalog but forget to align DDL code for it. Could you please open a Jira for the same and we should come up with a generic framework to catch it as part of either compilation or testing. This change can go ahead independently.

Sure.

Can you update PR description with Testing?


Add configurable analytics and cookie control

Our initial design choice for analytics was to add CloudFlare as this provided cookie free information about the site however we have decided that we need to make the Dorset Council version of this application use the same policies as the wider Dorset Council website. This would have a few benefits to us as users:

it means our site would be consistent and easier to to understand to other council developers
it means that accepting cookies on the main council website would also be accepted on this application.

To ensure that this application remains flexible for use by others we have decided to make the change configurable so that you can choose which analytics you want to use for your own deployment and even version by version (version = map definition).
The support I have added at present covers four mainstream options:

CloudFlare
Google Analytics
Microsoft Application Insights
** This is referring to the client side implementation of this package rather than the server side options.
Microsoft Clarity

We have added a section to manage the analytics to the System management page:

On the page you can then add, edit and remove analytics using the buttons and tools.

The current assumption is that code snippets will be committed into the main views rather than being stored in the database because it might be generally safer to avoid injecting HTML from any other source if possible. This means that rather than inserting a code snippet you only put in the unique ID provided by the analytic provider. This might need to change if we discover a good reason but for now it seems to be working.
The required code is inserted via partials (or JavaScript) in the head and body sections of the page layouts as required by the supplier and has been deployed to the test GIFramework maps site for review.
In the Dorset Council context the Google Tag Manager (GTM) has been configured to inject a cookie control into the site. This results in a html element which is interfering with the map layout and obscuring the copyright statement:

We are investigating how to to disable this HTML element at present and the change will not be published until this element has been removed. We know this is possible from the documentation but we are looking for a solution that will work of other sites using the same tag manager. Please ignore this aspect when reviewing the pull request as we will not be merging until it has been resolved.

This is a blocking comment to be resolved once the cookie control element has been resolved.

Comment from Dorset Council user:
Just one UX related thought, do you think the 'focus' is strong enough on the cookie popup at this point?

A user could believe that the popup they need to deal with is the white box first. Maybe the overlay could be darker or something?

Comment from Dorset Council user: Just one UX related thought, do you think the 'focus' is strong enough on the cookie popup at this point?
A user could believe that the popup they need to deal with is the white box first. Maybe the overlay could be darker or something?

After discussion we will raise this as a separate topic to investigate the idea of deferring the welcome message. This comment should be seen as non-blocking on this pull request.

We have agreed that once the cookie control button issue has been fixed we will approve this pull request to live subject to a further code review to improve the entity framework sections. See work item #126 for more information.

Just a reminder to update the privacy section of the docs - https://dorset-council-uk.github.io/DorsetExplorer-Docs/privacy/ - when you switch analytics providers

Just a reminder to update the privacy section of the docs - https://dorset-council-uk.github.io/DorsetExplorer-Docs/privacy/ - when you switch analytics providers

Because the change means that we are going to be using the standard default policies we are going to point the page at the Dorset Council site instead of the GIFramework one as accepting on our implementation (DorsetExplorer) would mean they are not prompted if they then go to another Dorset Council site (in theory). This means we need to put the relevant bits in the main page really.
In addition we felt that three links is too much so we are likely to try and reduce it back to just two but we will review that now as we have some time whilst we are waiting for the cookie control to be updated again.


Consistent headers across .html files

Can we get somewhat consistent headers for all static files. I noticed a significant difference between projects.html and experience.html for example, which are unrelated to the contents of the respective pages.

Sure if you can make changes without affecting function go ahead.


Fix typo in LoopbackPort export

There was a typo in #8361, sorry for that.

(There's no point in running tests, since the src/pdf.js file isn't used in testing.)
/botio-linux preview

Thanks for the patch!


make_nuscenes_label.py failed

Hello, when I tried to run make_nuscenes_labels.py, the ouput is like this:

What is the matter with this, but the GT label seems OK?

And also, the categories number in mine is different from this one, which is 23 and mine is 32.

Hi,
The "error" messages are not actually error messages. They are just logging the currently processed scene name and token. In order to make sure that they will be printed, I set them to logging.error. So there is no problem.
I don't know what exactly that image is. I assume it is non-decoded GT label. GT labels are encoded in PNG and it is use dafter decoding. So this looks very much normal to me. The black region is non-occluded, light gray is visible area and darker gray is visible AND non occluded. It will be much easier to see it when you look at the decoded labels.
You having different number of categories might have someting to do with your nuscenes version. Can you check if it is v1.0? If not, you can still try to run the code but I haven't tested it with other nuscenes versions so there might be problems.

Hi, The "error" messages are not actually error messages. They are just logging the currently processed scene name and token. In order to make sure that they will be printed, I set them to logging.error. So there is no problem. I don't know what exactly that image is. I assume it is non-decoded GT label. GT labels are encoded in PNG and it is use dafter decoding. So this looks very much normal to me. The black region is non-occluded, light gray is visible area and darker gray is visible AND non occluded. It will be much easier to see it when you look at the decoded labels.
You having different number of categories might have someting to do with your nuscenes version. Can you check if it is v1.0? If not, you can still try to run the code but I haven't tested it with other nuscenes versions so there might be problems.

Thank you for your generous reply. I have another question, the code used for generating NuScenes bev labels is similar to PON, but the number of labels is different. In PON, the number is 204895, yours is 34150.

That is not number of labels. The generation code is adopted from PON. We and PON use 14 classes (4 static and 10 object).

That is not number of labels. The generation code is adopted from PON. We and PON use 14 classes (4 static and 10 object).

Sorry for the confusing formulation. The number here is the total number of .png files after running this code.

PON trains on all 6 cameras of the rig. We just use the front camera.

Oh, I see. Thanks!

您好，当我尝试运行make_nuscenes_labels.py时，输出是这样的：  这是怎么回事，但 GT 标签似乎还可以？
而且，我的类别编号与这个不同，它是 23，我的是 32。
**
**

嗨，“错误”消息实际上不是错误消息。它们只是记录当前处理的场景名称和令牌。为了确保它们将被打印出来，我将它们设置为 logging.error。所以没有问题。我不知道那个图像到底是什么。我假设它是未解码的 GT 标签。GT标签以PNG编码，并在解码后使用。所以这对我来说看起来很正常。黑色区域是非遮挡区域，浅灰色是可见区域，深灰色是可见且未遮挡的区域。当您查看解码的标签时，会更容易看到它。
您拥有不同数量的类别可能与您的 nuscenes 版本有关。你能检查一下它是否是v1.0吗？如果没有，您仍然可以尝试运行代码，但我还没有使用其他 nuscenes 版本对其进行测试，因此可能会出现问题。

Thank you for your generous reply. How do I decode the ground truth image? I have obtained a similar GT image but I'm not sure if it's correct. Thank you very much.