Syntax error when compiling shader

Hello,
when i try to compile the shader, i get the following error message:

An error occurred compiling the shaders: ERROR: 0:? : '' : syntax error

My code is:
#pragma glslify: import("./src/utils/constants.glsl")
If i output the compiled shader, the constant is there, just as it is supposed to be:
#pragma glslify: import("./src/utils/constants.glsl")
const float PI_2 = 3.14159265359;
I am not sure if the macro line should be still there, too. Any ideas what i am doing wrong? My platform is OS X, using npm.
And of course, thanks for the awesome module!
Cheers!

Ok, found the source of the problem. A novice error. I didn't update my package.json to reflect the usage of glslify-import. My suggestion is to highlight the term transform stream in the readme and also include instructions on how to modify the npm package file. E.g. "glslify": { "transform": [ "glslify-import" ]  }
Cheers and thanks.


WPT fixes: channel splitter/merger error msg, offline ctx channel count mode

Big win with the AudioNode tests because of the fixed panic in the destination node
  RESULTS:
  - # pass: 5199 (+190)
  - # fail: 640 (-19)
  - # type error issues: 62 (+8)

Apart my small comment, looks all good to me


add option to show number of days left until event occurs

So you can, at a glance see how long until an event occurs.

Closing this issue as there's a newer one with better reasoning on why this feature is desired: https://github.com/plusonelabs/calendar-widget/issues/215


recenter causes img2img processes (which include adetailer) to result in blue-tinted images.

As title says, any process involving img2img and recenter results in a cooler tint to the image, noticeable even with 0.2 strength.
Admittedly, it's not really a problem in regular img2img since it can simply be turned off, but it's a problem when using adetailer, an automatic img2img inpaint extension. (https://github.com/Bing-su/adetailer/)
Really hoping you can fix this, it helps reduce that 'ai' feel to images.

So, you mean it specifically causes blue tint when adetailer is also enabled?

I've managed to recreate a similar problem now. While not a blue tint, the reactangular area processed by adetailer often comes out brighter than the rest during img2img.
Currently, I came up with a temporary solution, but it would break other functions. So I'm still trying to fix it.

Please test if the issue still persists~

Completely fixed, thanks a lot!


Add UCP 3.0.x packages to download for offline install/upgrade

Problem description

We should offer ALL supported UCP versions here for download in one place.

https://docs.docker.com/ee/ucp/admin/install/install-offline/
https://docs.docker.com/ee/ucp/admin/install/upgrade-offline/

@hannah-docker, as you know, we're short-handed right now. Would you be able to add the links to the supported UCP versions to this ticket, so we can get them added/merged? Thank you so much!


feat: more info provided at verse endpoint

I added more info at the Verse endpoint, it works for now but i need to change the structure of the response object.... Right now it's being returned like this:
{"verse":"In the beginning God created the heavens and the earth.","numVerses":31,"numChapters":50,"bookName":"Genesis"}
should be more like this:
{data: {"verse":"In the beginning God created the heavens and the earth.","numVerses":31,"numChapters":50,"bookName":"Genesis"}}

Also, need to find a way to make a request to the api because right now its requesting it for each piece of information which makes it slow

Somehow I've broken the VerseList endpoint

Somehow I've broken the VerseList endpoint... would appreciate a second set of eyes @JudeDavis1

Broke how? Was it erroring?

Somehow I've broken the VerseList endpoint... would appreciate a second set of eyes @JudeDavis1

Broke how? Was it erroring?

Yup, status code 500, the error message was "PathVariable "bookNum" has not been provideed" or something like that
Im thinking it might be a conflict with the two endpoints

We need to try and figure out a way to get Java build CI to build using the docker script instead of it's native build

We need to try and figure out a way to get Java build CI to build using the docker script instead of it's native build

I mean the runs are only for the tests (we don't have any yet 😂) to make sure commits don't introduce breaking changes, I don't see a need to make it use docker.


feat: trustedboot

replace _secureboot and _readonly with _trustedboot

we should merge https://github.com/gardenlinux/builder/pull/97 first, as this is using it as its base

blocked by https://github.com/gardenlinux/builder/pull/97
(will still need to adjust the commitish in build script after merge in builder)

replaced by #2341 to not have so many changes in one go


Source level

Need test and integration on syskit.
Set the source level (the signal power). Check depth of vehicle to not set a high power signal in the surface.
Add messages counters.
Use device settings as default property

I totally misunderstood the delivery report thing. There is just ONE delivery report per Instant Message (Failed or Delivered). Instant Message's counter make it clear (messageSent = messageDelivered + messageFailed).
Good thing, the code is cleaner.
The source level on auv and control according its depth needs a better understanding

If we have to change the source level dynamically, it would be a lot better to make it a separate dynamic property

Ok.
@doudou, I'm not sure the best way to deal with the source level, especially in auv, regarding the distance of the auv from the surface and from the dock side.
The Source Level is the power of the signal.  The manual says to set the source level to it minimal level outside water, once it can damage the device. Also, long distances between auv and dock requires a higher source level for data exchange.
There is this other property in usbl, Source Level Control, a bool. If it is set, it will change the local source level to match with the source level of the remote device in case of raw data transmission.
It's practical so we don't need to check if the actual source level is enough or not. Usbl deals with it.
But regarding the depth, and making sure the usbl will not work with high source level in the surface, how would be a good way to do it?
Change the source level and source level control properties so it stay in its minimal value near surface  and continue to transmit data ( even if it may be not delivered to remote device)?
Or just drop the data and not send it (raw data and instant message) when auv is above a certain depth (like 0.5m), and avoid change the properties with the change of depth?
What do you suggest?

If you make the source level a dynamic property, we could change it dynamically in Syskit without a problem. Just make the source level minimal by default.
Now, this source level control thing looks appealing. However, the AUV is really better placed than the dock to decide the source level (since it has an estimate of its own position).... So I would go with manually controlling it inside Syskit.

Ok. So it's not necessary to monitor the depth and change the parameter direct inside the task? It can be done by syskit through the dynamic property?
About the source level control, I think it should be set in one of the nodes. If not in auv, at least in dock.
If we control the source level in auv, then we need to monitor not only the depth, but also the quality of the acoustic link and estimate the distance to dock, and I think it can be a though task.  If we do it manually in auv, the vehicle need to be tethered.
We can do some tests till we better understanding the boundaries of each source level and when auv runs untethered, it automatically defines its source level. But if this automatic method fails we risk not been able to connect with auv.
So, I would go for the dock side defines the source level and let the source level control set in auv.
For safety, both the source level and source level control would be dynamic properties and auv just monitor the depth so it can unset the source level control and set the source level to minimal near surface.
What do you think?

Source Level and Source Level Control as dynamic properties.

So, I would go for the dock side defines the source level and let the source level control set in auv.
For safety, both the source level and source level control would be dynamic properties and auv just monitor the depth so it can unset the source level control and set the source level to minimal near surface.

I think it's probably the best option, at least until we get a better idea of how well / how all that stuff works. What I am concerned about is what happens when we lose the link. When that happens, the AUV will obviously not be able to do level control, so what happens then.
Anyways, let's use the automated way and figure it out when we get some experience.


Different behaviour for Desktop/Mobile Devices

Hello,
I am using Driver.js with Bootstrap 4. It is working fine when the website is viewed in a mobile environment, but does not work when the website is viewed in a desktop browser. I have noticed the following:

Using the browser's web-development tools (on my desktop computer), and with the browser configured to act as a mobile browser, I see that when Driver.js starts, the divisions class="container-fluid" with position "fixed" are turned to class="container-fluid driver-fix-stacking". These are divisions where I have Driver "steps" defined. The driver will proceed as intended.
If I turn off mobile emulation, I see that when Driver.js starts, the divisions  class="container-fluid" with position "fixed" remain class="container-fluid" and the Driver does not give sign of life.

Why is the driver not adding the driver-fix-stacking when the browser is desktop?
Many thanks.

Hey @aminemarref, do you have a sample code or a demo that I can look at?

Hey @aminemarref, do you have a sample code or a demo that I can look at?


Add support for nav_msgs/OccupancyGrid

🎉 New feature
Depends on https://github.com/ignitionrobotics/ign-msgs/pull/138/
Summary
Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Updated documentation (as needed)

Note to maintainers: Remember to use Squash-Merge

Sorry, the message bridge got busted off a bad rebase as I was originally working on the noetic branch.  This should be good now.

The melodic branch is supposed to build from source against Citadel, so we'll need to backport and release ignitionrobotics/ign-msgs#138 first.

Backport PR: https://github.com/ignitionrobotics/ign-msgs/pull/143


Allow SAIS team members to add vaccine batches, see existing batches

New link in the header

(not sure how to left-justify it like in the prototype)
Manage vaccines

Add a batch

Add a batch with errors

Batch added successfully

Notes for reviewers
This PR includes another experiment in the feature spec; instead of using FactoryBot to set up data, I'm calling operational Rake tasks (as this is how teams / vaccines / users are set up in production-like environments). This should hopefully mean that this feature spec is more likely to spot issues with these Rake tasks, and less prone to suffer from factory bugs. The  Rake task calls are wrapped in a method that temporarily suppresses STDOUT output, to prevent stray noise in the test runner.

@benilovj Added a utility class for the header navigation that can be put on the item that pushes the other items to the right. And then added this to the new ‘Manage vaccines’ navigation item, pushing this over to the left grouping.

Thanks for sorting @paulrobertlloyd !


IGN layer load with referrer API key : 403 forbidden errors

I try to load IGN layers from WMTS service with a referrer API key I created: https://wxs.ign.fr/key/geoportail/wmts?SERVICE=WMTS&REQUEST=GetCapabilities.
If I put it in Kano, it correctly gives me layers. However, when I display the layer, nothing appears. The network console shows 403 forbidden errors and the following response: <ExceptionReport><Exception exceptionCode="MissingParameter">Resource parameter not found</Exception></ExceptionReport>.
It could be a problem related to the permissions or the fact that the IGN WMTS service only supports the procedure oriented architectural style and not the resource oriented architectural style so that we need to use GetTile and not X/Y/Z based access.

According to the IGN documentation we should indeed use a GetTile request. Related to https://github.com/kalisio/kdk/issues/423.

I'm not sure adding WMTS GetTiles support will be enough, Geoportail securing mechanisms all require to add custom headers to the requests (referer, useragent or user/pass basicauth). Leaflet has no support to add custom headers when doing requests (https://github.com/Leaflet/Leaflet/issues/2091). I'll try but i'm a bit skeptical, even if the IGN doc doesn't mention http headers ...

Webservices have been updated recently by IGN and now uses generic keys (see https://geoservices.ign.fr/services-web-experts-cartes). For instance the following URL should work https://wxs.ign.fr/cartes/geoportail/wmts?SERVICE=WMTS&VERSION=1.0.0&REQUEST=GetCapabilities. However, the following error is raised: _lodash2.default.get is not a function or its return value is not iterable.
It seems to be related to the fact that vector tiles are also exposed using WMTS but the layer does not provide a style.

Should be now fixed by https://github.com/kalisio/kdk/issues/423.


Support for Parallel SSE Connections

Hi there! Been testing out the module and gotten it working using the build available in #15 with xk6 to connect to a single SSE endpoint, but when I'm trying to expand that to include multiple SSE endpoints the connection appears to "block" the Event Loop until client.close() is called.
Any recommendations on what I might be doing wrong? Might just be that the module isn't setup for that at this time, I tried looking around but I'm not very experienced with Go/k6 extension development so not sure where to start with a PR to add that functionality yet.
Here's a quick test script of what I'm looking for. In this I'd like both of the SSE connections to occur in parallel as my app will be getting data from multiple SSE endpoints at once. In the example below you'll notice that the connection isn't made to url2 until the first SSE connection is closed due to an event.id value of 4 being sent by https://echo.websocket.org/.sse. Given this my console output looks like this:
Current Console Output
INFO[0000] connected                                     source=console
INFO[0000] event id=1, name=server, data=1781505b56ee58  source=console
INFO[0000] event id=2, name=request, data=GET /.sse HTTP/1.1  source=console
INFO[0001] event id=3, name=time, data=2024-08-06T16:01:21Z  source=console
INFO[0002] event id=4, name=time, data=2024-08-06T16:01:22Z  source=console
INFO[0002] closing connection                            source=console
INFO[0002] started sse1                                  source=console
INFO[0003] connected                                     source=console
INFO[0003] event id=, name=, data={"testing":true,"sse_dev":"is great","msg":"It works!","now":1722960083350}  source=console
INFO[0005] event id=, name=, data={"testing":true,"sse_dev":"is great","msg":"It works!","now":1722960085350}  source=console

You can see from the above that the call to sse.open(...) appears to be blocking the event loop as the next line console.log('started sse1') isn't executed until after the client.close() function is called.
Example Script
import sse from "k6/x/sse"

export default function () {
  const url1 = "https://echo.websocket.org/.sse"
  const url2 = "https://sse.dev/test"
  const params = {
    method: 'GET',
    headers: {
      "Authorization": "Bearer XXXX"
    },
    tags: {"my_k6s_tag": "hello sse"}
  }

  const response1 = sse.open(url1, params, handleEvents);
  console.log('started sse1');
  const response2 = sse.open(url2, params, handleEvents);
  console.log('started sse2');
}

function handleEvents(client) {
  client.on('open', function open() {
    console.log('connected')
  })

  client.on('event', function (event) {
    console.log(`event id=${event.id}, name=${event.name}, data=${event.data}`)
    if (parseInt(event.id) === 4) {
      console.log('closing connection');
      client.close()
    }
  })

  client.on('error', function (e) {
    console.log('An unexpected error occurred: ', e.error())
  })
}

The blocking behavior of open defeats the purpose of sse support for my use case.  Looking for workaround...

I guess their async stuff has a ways to go....

Yes, k6 was designed syncIO, I reused the approch of the websocket extension.
Help is welcome to introduce new async client.


additional attributes from sensors

Hello.
In the JSON file for the Aqara Water Leak Sensor (SJCGQ11LM) there is a chip_temperature attribute:
cat /data/zigbee_gw/lumi.158d0004522a2b.json
{
"lumi.158d0004522a2b.mac": "158d0004522a2b",
"lumi.158d0004522a2b.model": "lumi.sensor_wleak.aq1",
"lumi.158d0004522a2b.prop": "{"props":{"CCA":1,"alarm":0,"alive":1,"battery":62,"battery_end_of_life":0,"chip_temperature":30,"cur_state":3,"fw_ver":4,"hw_ver":2,"lqi":0,"parent":0,"power_tx":10,"pre_state":4,"pv_state":0,"reset_cnt":15,"send_all_cnt":1,"send_fail_cnt":0,"send_retry_cnt":0,"voltage":2975}}",
"lumi.158d0004522a2b.version": "1.2"
}
Is it possible to get it somehow in HA?

Check #107 (duplicate)

Check #107 (duplicate)


Add back functionality to navigate route

Implements #44
Uses history.go as suggested by @ryanflorence in https://github.com/reach/router/issues/44#issuecomment-396368172

Any chances this gets merged ? I think this is pretty useful for Gatsby as the window object can't be used during build process.
Related to this issue.

Any update for this PR?

Would love to see this get merged. 🤘

Does this implementation re-render the previous tree? https://github.com/reach/router/issues/44#issuecomment-461431314

This would be great!

+1

Why not merge this commit?

+1000000

Please refrain from adding +1 comments. Adding emoji reacts communicates the same enthusiasm for the work without cluttering the thread

+1

+100

+1000

I believe that the createMemorySource should also implement this expected behavior on the history::go method. It's currently undefined.

+10000

Coming from Gatsby as well, wondering why it's still not possible to simply .goBack().
So, what's missing for this PR to get merged?

Thanks for your patience.
My hesitation here has been around how suspense and caches are going to work.
If you click "back" do we need to go into the transitioning state or can we assume since we're going somewhere we've already visited the cache will be filled already?
This PR assumes the cache will be filled. And I suppose the code already assumes they will be filled if the user clicks back.
Anyway, we may find issues when suspense ships in 2032, and we can figure out what to do then.
(j/k react team I love you suspense is going to be amazing)

Should this now be working as its merged to master? I'm using v1.2.1 and passing an int to navigate just attaches it to the end of the url

I'm having the same issue.
navigate(-1) just append /-1 to the end of the url

When this works I have some production workarounds to rectify xD

this doesn't quit work yet, to === "/-1" so it doesn't pass the typeof to === "number" check. somewhere it prepends to with a slash

I'm also on 1.2.1 and it is just appending a -1.

Yeah so the fix is on the beta release, so just do ‘yarn add @reach/router@next’

In some use cases I suggest:
<Link to="../">Back</Link>

I am also seeing the issue where navigate(-1) is appending a -1 to the url.
I ran ‘yarn add @reach/router@next’ as suggested by @rickiesmooth but the issues persists. Any fix for this yet?
This is my implementation in Gatsby
import { navigate } from "@reach/router";
const goBack = () => {
navigate(-1);
}
Back

I am also seeing the issue where navigate(-1) is appending a -1 to the url.
I ran ‘yarn add @reach/router@next’ as suggested by @rickiesmooth but the issues persists. Any fix for this yet?
This is my implementation in Gatsby
import { navigate } from "@reach/router";

const goBack = () => {
navigate(-1);
}

Back

FYI I fixed this by updating my project's packages to the latest versions by running
yarn upgrade
I'm assuming this worked because I got the latest fix to gatsby mentioned above (gatsby was updated to v2.24.63)


Don't have Xcode embed the Swift stdlib into SwiftXCTest.framework

This avoids issues arising from dyld trying to load both Xcode's
stdlib version and the just-built stdlib which may not be compatible.
Resolves: SR-2434

@swift-ci Please test

This looks to have worked! Merging this now as the first step to getting things cleaned up.
Note that I don't think there is much value in adding this to the swift-3.0-branch because no OS X products are actually shipped with Swift, this build style only exists as a convenience to corelibs contributors.


Stack Component registering made easier

Describe changes
Multiple times today I was registering stack components with flavors that I was unfamiliar with. Going into the docs or code takes quite a bit of time, so I simply registered them and waited for the error message to show me which fields I was missing.

In this Pull request I introduce code that will enter interactive mode, in case a required field is not set in the first command. Now it will look a bit like this:

The only disadvantage that I can see in this, is that the reverse-i-search will become less useful to figure out which command was run to register a given stack component. Looking forward to your comments.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

I added @bcdurak and @schustmi as reviewers to get their opinions on this. I am personally unsure myself whether this is a good default way or not. For me the error seems clear what to add and id rather not go in interactive mode

I added @bcdurak and @schustmi as reviewers to get their opinions on this. I am personally unsure myself whether this is a good default way or not. For me the error seems clear what to add and id rather not go in interactive mode

What downside do you see in going interactive?

In CI/CD settings, when I want to automate the construction of the stack in as script, I want it to fail gracefully rather than go in interactive mode and hang my machine :-)

Love the idea, super useful to register unknown components.
I also agree with @htahir1 that the "defaulting" to interactive might not be a good idea for any automated script, in that case you want it to just fail. Can we instead add this functionality with a -i/--interactive flag similar to the secret registration? We could even include optional attributes as well to make it a full-featured registration. (Btw we should definitely add this for stacks as well!)

Love the idea, super useful to register unknown components.
I also agree with @htahir1 that the "defaulting" to interactive might not be a good idea for any automated script, in that case you want it to just fail. Can we instead add this functionality with a -i/--interactive flag similar to the secret registration? We could even include optional attributes as well to make it a full-featured registration. (Btw we should definitely add this for stacks as well!)

Have implemented this and pushed :)


Send alert only for first match in certain timeframe

I have a case where if the application I'm monitoring encounters an error, the error log appears every 3 seconds. I want to create an Elastalert rule which will send alert only for the first match because all others are exact copies EXCEPT for the timestamp in the message. The rule I have currently (below) sends a list of all these error messages.
Current Rule:
name: Application Alert

type: frequency
index: filebeat-*
run_every:
  minutes: 10
num_events: 1
timeframe:
  minutes: 10

realert:
  minutes: 30

aggregation:
  minutes: 10

query_key: ["message"]

filter:
- query_string:
   query: '"some string here" AND "another string here"'

alert:
- "slack"

slack_msg_color: danger
slack_webhook_url: SlackWebHookURL

alert_text_args: ["message", "fields", "@timestamp"]
alert_text: "Details = {1} \n UTC Time = {2} \n Log = {0}"
alert_text_type: alert_text_only

Desired behavior:
Slack alert for above rule should have only one error log line even though there are 100s of matches in the 10 minute timeframe because only thing unique about them is the timestamp.
How do I go about it? Thank you!

I feel that the way to write query_string is strange. See below
https://github.com/Yelp/elastalert#my-rule-is-not-getting-any-hits

Yelp/elastalert is no longer maintained. Please use jertel elastalert. Questions to the discussion below
https://github.com/jertel/elastalert/discussions


remove non-metabolic genes from Glycerophospholipid metabolism

Description of the issue:

Non-metabolic genes are discovered in the GPR rules of following reactions in Glycerophospholipid metabolism subsystem:

gene
Reasons
Subsystems
RxnIDs

ENSG00000105198
not phospholipase, strong inducer of T-cell apoptosis
Glycerophospholipid metabolism
MAR00633;MAR00645

ENSG00000105205
has no lysophospholipase activity, but regulates immune responses
Glycerophospholipid metabolism
MAR00633;MAR00645

ENSG00000105223
Exonucleolytic cleavage in the 5'- to 3'-direction to yield nucleoside 3'-phosphates
Glycerophospholipid metabolism;Ether lipid metabolism
MAR00629;MAR00642;MAR00660;MAR08523;MAR08525;MAR07605

ENSG00000138308
does not seem to have catalytic activity
Glycerophospholipid metabolism;Ether lipid metabolism;Glycerolipid metabolism
MAR00463;MAR05254;MAR00630;MAR00643;MAR07603;MAR07615

ENSG00000166428
exhibits no phospholipase activity
Glycerophospholipid metabolism;Ether lipid metabolism
MAR00629;MAR00642;MAR00660;MAR08523;MAR08525;MAR07605

ENSG00000187980
annotated as inactive
Glycerophospholipid metabolism;Ether lipid metabolism;Glycerolipid metabolism
MAR00463;MAR05254;MAR00630;MAR00643;MAR07603;MAR07615

Current feature/value/output:

The association of these genes is lack of evidence according to the provided reasons

Expected feature/value/output:

Remove above genes from Human-GEM

I hereby confirm that I have:

[X] Done this analysis in the main branch of the repository
[X] Checked that a similar issue does not exist already

LGTM! Please go ahead!


Fix (and ignore one!) type errors

Related to handling ReadableStreams in writeFile and writeTextFile, convert bigint to number in offset parameter usage, and ignore one type error that I do not understand 😅
This change to the writeFile API was introduced, from what I can tell, in v1.30 of deno (here). The change to the seek operations seem to have come from here (also in v1.30).
This seems to pass the tests now, at least.
Not sure if this is entirely correct - could use a bit of guidance and review. Happy to adjust it as needed.

Thank you for your contribution!
I'm short on time this week, so I'll check this PR out later. please wait a little bit.

Hey @ayame113 I fixed up the PR and added tests for it - it actually works now, unlike my initial PR 😅


Extend res object with async method

Hi,
I want to extend res object with async method, like this:
res.sendStrream = async function (path) {...}

// then in http request handler:
uws.get("/", (res) => {
    res.sendStream(path);
})

But getting this error at runtime, when calling this new method:
(node:44040) UnhandledPromiseRejectionWarning: Using uWS.HttpRequest past its request handler return is forbidden (it is stack allocated).
(
(

Is it possible to avoid this error?

Using uWS.HttpRequest past its request handler return is forbidden (it is stack allocated).

This is a message for you to read. When you await anything, that's technically a return. So you cannot use the HttpRequest after this point, you have to copy out whatever you want to keep before you return or await.


RFP - SolveSpace

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details

Software project URL : http://solvespace.com/index.pl
Direct download URL for the software / installer : https://github.com/solvespace/solvespace/releases/tag/v2.3
Software summary / short description: SOLVESPACE is a free (GPLv3) parametric 3d CAD tool
GitHub: https://github.com/solvespace/solvespace
Maintainer: @whitequark
other Repositories and package managers: https://repology.org/metapackage/solvespace/versions

Status: Review
https://chocolatey.org/packages/solvespace

Status: Published
https://chocolatey.org/packages/solvespace
Can be closed.


Create docker-compose file

 (5) Create develop environment using docker compose

 (5) Create test environment using docker-compose


JavaScript - Typo in array fill method documentation

VS Code Version: 1.55.0
OS Version: Windows 10 20h2

Steps to Reproduce:
"Returns the this object" instead of "Returns this object".

Does this issue occur when all extensions are disabled?: Yes

Can I get in on this issue?


Sort by required points to level up

Can we add a column to the summoner page to show the required points to level up?
I wrote a script for my use, but i think it would be helpful for others if they are also interested in max leveling all champs.
Script: https://pastebin.com/uxY72LxF

Right now sorting by progress is a bit messed up. It currently sorts champions that are level 1-4 by progress to the next level (as a percentage), but sorts champions that are level 5-6 by progress to the max level. In the upcoming days, I'll try to get some feedback from users about their opinions on sorting by progress (including their opinions on if they want to be able to sort progress by the percentage to next level, the points to the next level, or both), and update the site based on that.
Once I gather some feedback on the issue, are you interested in creating a pull request to add the feature, or are you just suggesting that I add the feature?

If you are inclined to add, I can take care of the changes for the feature.

I gathered some feedback, and quite a few people are interested in having a 2nd progress columns. 1 column will be the progress towards the max level, and the other column will be progress towards the next level (by points required to level up).
Are you still interested in adding this feature yourself?

Cool. Yep, I ll add the feature sometime next week and follow up here.

I have the (tested) changes on my local. What is the next step here?
PS: I am new to GitHub, I couldn't push to a new remote branch. Without that, I don't see any options to make a PR. Is forking the only way?

You'll need to fork the repository to create a PR. The basic steps are:

Fork the repo
Push your changes to the forked repo
Make a pull request from the forked repo to the original repo

You can find more detailed instructions here

Thanks. Created the PR.

Thanks for your contribution!


LE Audio: Controller: Config settings with 44.1 kHz and 48 kHz are rejected at LE Create BIG

Describe the bug
Not high prio, posting just for the record:
Zephyr controller rejects the LE Create BIG if the fallowing config settings are used:

441_1
441_2
48_1
48_2
48_3
48_4
48_5
48_6

When the Zephyr controller is built with CONFIG_BT_CTLR_CONN_ISO_LOW_LATENCY_POLICY=n the LE Create BIG succeed, but only for the 441_1 setting. Even then the PTS device is not able to synchronize to the broadcast.
To Reproduce
With the AutoPTS and nRF5340 board.
Impact
Affected PTS test cases:
BAP/BSRC/STR/BV-09-C
BAP/BSRC/STR/BV-10-C
BAP/BSRC/STR/BV-26-C
BAP/BSRC/STR/BV-27-C
BAP/BSRC/STR/BV-28-C
BAP/BSRC/STR/BV-29-C
BAP/BSRC/STR/BV-30-C
BAP/BSRC/STR/BV-31-C
BAP/BSRC/STR/BV-32-C
BAP/BSRC/STR/BV-33-C
Additional context
@cvinayak

Please use our bug template when reporting bugs. You need to edit this issue to include the information requested in https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/001_bug_report.md

We should add broadcast testing to the existing GMAP and CAP AC tests, which currently only covers unicast.

@mkasenberg is there any pointer to be on "getting started" to be able to reproduce the failures reported?

To Reproduce
With the AutoPTS and nRF5340 board.

Assuming a new resource working on this issue, what are the needed steps to reproduce the issue?

@mkasenberg is there any pointer to be on "getting started" to be able to reproduce the failures reported?

To Reproduce
With the AutoPTS and nRF5340 board.

Assuming a new resource working on this issue, what are the needed steps to reproduce the issue?

I'll create a PR to add the CAP and GMAP broadcast audio configurations for BSIM

AutoPTS instruction can be found at:
https://docs.zephyrproject.org/latest/connectivity/bluetooth/autopts/autopts-win10.html
https://docs.zephyrproject.org/latest/connectivity/bluetooth/autopts/autopts-linux.html
Steps to reproduce:

Have nRF5340 board (revision 2.0.0 in my case)

Have 1 PTS dongle (the LE Only one)

Have installed the PTS <IP_ADDRESS>

Have installed the AutoPTS

instructions for Windows users
instructions for Linux users

I use Windows as host, because the PTS starts faster than when I used Linux host + Windows virtual machine. But it should not matter. I have installed Python 3.11.6..

Last Zephyr SHA that I tested and the issue still persisted is 3c0a6058b518f7d5dfbbadc9e857cc605632264b, so git-checkout on that:

git checkout 3c0a605
west update

Go to the zephyrproject/zephyr/samples/bluetooth/hci_ipc directory, then build and flash the app for the netcore:

west build -b nrf5340dk_nrf5340_cpunet -- -DOVERLAY_CONFIG='nrf5340_cpunet_iso-bt_ll_sw_split.conf;../../../tests/bluetooth/tester/nrf5340_hci_ipc_cpunet.conf'
west flash

Go to the zephyrproject/zephyr/tests/bluetooth/tester directory, then build and flash the app for the appcore:

west build -b nrf5340dk_nrf5340_cpuapp -- -DOVERLAY_CONFIG='nrf5340_hci_ipc.conf;overlay-le-audio.conf'
west flash

Close the PTS, if it is opened.

Go to the auto-pts directory and start the autopts server:

python autoptsserver.py

The autopts server will start the PTS in automation mode. Wait until the autoptsserver prints OK:
$ python autoptsserver.py
(2366879466768) Starting PTS 65000 ...
Local IP address: ('<IP_ADDRESS>', 'fe80::f87b:c093:ad28:dae8') DNS None
Local IP address: ('<IP_ADDRESS>', 'fe80::a694:4949:87af:e0b1') DNS None
Local IP address: ('<IP_ADDRESS>', 'fe80::f0b7:3be5:cc53:1889') DNS None
Serving on port 65000 ...
(2366879466768) OK

Find the jlink uart port name of the app core. There are usually two ports visible for nrf53. Find the one that prints these 5 bytes after board reset: 00 80 ff 00 00

It is the BTP ready event. You can use the PuTTY or the below python script to check the port output:
import serial
com = 'COM4'
ser = serial.Serial(com, 115200, timeout=5)
ser.flushInput()
ser.flushOutput()
input('Reset board and press enter')
print(ser.read(9999))
ser.close()

There should be no other bytes in the output except those of the BTP Ready event.

Start the autopts client:
(You may have to adjust the port name and the IPs here)

For Windows users:

python ./autoptsclient-zephyr.py zephyr-master -t COM4 -b nrf53 -c BAP/BSRC/STR/BV-09-C

For Linux users:

python ./autoptsclient-zephyr.py zephyr-master -t /dev/ACM0 -b nrf53 -l <IP_ADDRESS> -i <IP_ADDRESS> -c BAP/BSRC/STR/BV-09-C

where -l is the IP of Linux host and -i is the IP of Windows guest on virtual machine.
Don't hesitate to ask questions under AutoPTS issues or you can reach me on discord, as the first launch can be troublesome.

@cvinayak https://github.com/zephyrproject-rtos/zephyr/pull/67210 adds testing of all audio configurations and low latency presets from the BAP spec. Quite a lot of them are not passing (see the commented out tests).
This does not include the high reliability tests (yet).

@cvinayak #67210 adds testing of all audio configurations and low latency presets from the BAP spec. Quite a lot of them are not passing (see the commented out tests).
This does not include the high reliability tests (yet).

Work in progress addressing failures in #67210 is here: https://github.com/zephyrproject-rtos/zephyr/pull/67392

@mkasenberg Thank you for your instructions, I will switch to reproducing the issues once I get to fix controller for the test in #67210

@mkasenberg is it possible to run the failing PTS tests on a controller on this branch (before I get to setup my PTS)?  https://github.com/zephyrproject-rtos/zephyr/pull/67392

Yes, let's try if autopts bot is still operative.

@mkasenberg Looks like PR run has failed, is the failures same as original failures or any improvements seen in the controller fro the PR?

I saw the bot logs and the patch works great, controller has successfully accepted the config settings. The autopts cron has reported fails, because an MMI handler in autopts has a bug and does not send anything, the fix is not merged yet https://github.com/auto-pts/auto-pts/pull/1067/commits/f1453575017757489ef8250dc57a3ca0c95b5181#diff-fc44e218eeb03508ffb17b3eda2ca77928b173334fe43d2c55ff23df09b09e46R315-R323

thank you, added fixes comment for this gh issue in the Pr #67392 .... we can re-open this issue if there are problem when fixes are merged into main.


Saddle distance

Allow --min-dist and --max-dist arguments for compute-saddle.
Addresses https://github.com/mirnylab/cooltools/issues/54
Here is an example with some mouse ES cell data with mindist from 0 to 48 in 12 Mb increments, for 12 Mb bands (like in the Abramo paper).

lgtm!
@sergpolly, does this also resolve #87 ?

@Phlya @nvictus - yes looks like this would take care of #87 as well ...
Thank you @Phlya !
i'll leave here the way we've done it - just for history:
def make_cis_obsexp_diagband_fetcher(clr, expected, name, band_width_bins, inside=True):
    """
    Given a cooler object 'clr',
    cis-expected dataframe 'expected',
    and a column-name in cis-expected 'name',
    this function yields a function that
    returns slice of OBS/EXP for a given
    chromosome.
     Custom one with an additional band selector ...
    """
    full_obsexp = clr.matrix().fetch(chrom) / \
                toeplitz(expected.loc[chrom][name].values)
    i,j = np.indices(full_obsexp.shape)
    i = i.flatten()
    j = j.flatten()
    # fill NaNs outside of the desired selection:
    nan_band_selector = (np.abs(i-j) > band_width_bins) \
                     if inside else (np.abs(i-j) <= band_width_bins)
    full_obsexp[i[nan_band_selector],j[nan_band_selector]] = np.nan
    return full_obsexp

I also wonder if numutils.set_diag(matrix, np.nan, d) for a lot of diagonals is slower than the modified getmatrix approach ...

something like that to be tested:
def getmatrix(clr, expected, name, min_dist, max_dist):
    """
     ...
    """
    OE = clr.matrix().fetch(chrom) / \
                toeplitz(expected.loc[chrom][name].values)
    i,j = np.indices(OE.shape)
    i = i.flatten()
    j = j.flatten()
    # fill NaNs wherever needed:
    dist_mask = np.abs(i-j) > min_dist
    dist_mask = dist_mask & np.abs(i-j) < max_dist
    OE[i[dist_mask], j[dist_mask]] = np.nan
    return OE

vs
for d in diagonals_tobe_filled_with_nans:
    numutils.set_diag(matrix, np.nan, d)

Interesting.. then we can keep #87 open to consider alternative getmatrix implementations.


⚠ Shadow Does Streams has degraded performance

In 35332cd, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 5741 ms

Resolved: Shadow Does Streams performance has improved in 5ae1463 after 10 minutes.


Docker App release plan?

HI
I'm very interested in Docker App(https://docs.docker.com/app/working-with-app/) project .
I think that lately, There is no update on Docker App project.
who do you know Docker App road map in the future?

I agree, a public release schedule would be really helpful.


dimension type after apply_dimension has discarded labels

So if the callback in apply_dimension doesn't return the same array length as the source array, the labels get discarded (i.e. enumerated). That may work well for some dimension types like bands, but could an issue for the temporal dimension as the temporal reference is not available anymore. Should the dimension type be changed to other in this case?

While enumeration does not fit the usual calendar date/time structure, it could still be relative or symbolic time in some sense, so I don't think it is a problem to still call it a "temporal" dimension

Yes, but then you also need to reset the TRS (ISO 8601 / Gregorian calendar / UTC), too. And after renaming the labels you'd need to set the TRS again.

I'm not sure if I understand you correctly, but  you probably mean that the labels of a temporal dimension "MUST be strings compliant to ISO 8601"? So an dimension with enumerated labels can not be of type "temporal"?
in openapi.yaml I also found this https://github.com/Open-EO/openeo-api/blob/81dd248b9e8b8caeedbdd96c6a9dd8f3f56d0eb7/openapi.yaml#L4386-L4389 :

Data not compliant    with ISO 8601 can be represented as an             Additional Dimension Object with type set to             temporal.

I'm not sure though how to interpret this. Maybe this is a  leftover that became inconsistent?

I'm not sure myself what the implications of a temporal dimension are, but it probably must refer somehow to a specific instance in time that can be resolved, otherwise the default TRS (gregorian calendar) can't apply. A dimension with enumerated labels can surely be temporal if the TRS defines how to map them to time.
The part you found in the Collection spec is referring to the Data Cube Extension in STAC and has nothing to do with our data cube model. In STAC a dimension that is compliant to the temporal dimension json schema must be specified in metadata using ISO8601, but that doesn't imply anything to our data cubes. It's just a schema thing. An "Additional Dimension Object" can still specify a temporal dimension using another trs.


[Feat] [Translations] [Spanish]: advanced/middleware

@habemuscode Hi, you can request reviews from me.


Rescue StandardError makes all development errors failures

Since bumping omniauth from 1.9.1 to 2.0.1 in our application all development errors have become failures.  For example I purposefully introduce an error to a view.  It is caught by omniauth and calls fail which means that we can no longer use better_errors to debug.
195:       rescue StandardError => e
    196:        binding.pry
 => 197:         return fail!(e.message, e)
    198:       end
    199:
    200:       @app.call(env)
    201:     end

[1] pry(#<OmniAuth::Strategies::SAML>)> e
=> #<ActionView::Template::Error: undefined local variable or method `oops' for #<#<Class:0x00007f533c178068>:0x000055e0bcf640a8>>

Is there something that we misconfigured in omniauth setup?  We catch the failures to give users a message in their browser
https://github.com/ualbertalib/jupiter/blob/fe8409b9d4b4345e409c91a0cf6744b9ce4b91ba/config/initializers/omniauth.rb#L22
We can make this conditional based on environment but wondering if there is a better way?
https://github.com/omniauth/omniauth/blob/40e354c71094b663f928e1a987977690b67f2aa4/lib/omniauth/strategy.rb#L190-L197

You’ll want to take a look at the OmniAuth.config.on_failure setting, by default it’s set to call the OmniAuth Failure Endpoint https://github.com/omniauth/omniauth/blob/master/lib/omniauth/failure_endpoint.rb

You’ll want to take a look at the OmniAuth.config.on_failure setting, by default it’s set to call the OmniAuth Failure Endpoint https://github.com/omniauth/omniauth/blob/master/lib/omniauth/failure_endpoint.rb

If you're looking to preserve raising the errors out in development I'd suggest something like
on_failure do |env|
  if Rails.env.development?
    OmniAuth::FailureEndpoint.call(env)
  else
    SessionsController.action(:failure).call(env)
  end
end

If you're looking to preserve raising the errors out in development I'd suggest something like
on_failure do |env|
  if Rails.env.development?
    OmniAuth::FailureEndpoint.call(env)
  else
    SessionsController.action(:failure).call(env)
  end
end

Yes.  That's effectively what we've done.  We still think it's strange that omniauth is intercepting all errors (not just the ones relevant to omniauth).

Yes.  That's effectively what we've done.  We still think it's strange that omniauth is intercepting all errors (not just the ones relevant to omniauth).

I'll look into it a bit more, it really should only be catching errors that occur during the auth process

I'll look into it a bit more, it really should only be catching errors that occur during the auth process

Hi, I have a same problem. I use a omniauth-saml gem.
I found the omniauth-saml gem calls the call_app! method in the other_phase method. All errors have become failures and logs as "(saml) Authentication failure!" in the fail! method if an error occurs regardless of the auth process.

Thanks for the report and additional information @trysmr, I think this is a bug in omniauth-saml and will release a patch for that gem.

I saw https://github.com/omniauth/omniauth/issues/1032 and it is similar.  The error behaviour changed with the release of 2.0.2.  Now the failure mode is a redirect loop and the error is printed in the console.

This is printed 21x in the console

I have been looking into this, I haven't decided the best course of action yet. @pgwillia it looks like your session controller isn't handling the error but just redirecting to root?

@BobbyMcWho good observation.  That's what we've told it to do.
https://github.com/ualbertalib/jupiter/blob/7a5ce302771c471b5411bec24c4f4c2e61babb4d/app/controllers/sessions_controller.rb#L55-L57
That explains the redirect loop because the error I introduced is part of our welcome page.
@trysmr has summarized the issue that still persists.

So looking into a few strategies and how they have implemented the other_phase, it seems like they almost all call call_app! which is why this block will capture those application errors. I may have to pull that other phase out of the error handling capture.

Since the other_phase is not a common process for each omniauth strategy, I think it is better to leave its error handling to each strategy.
I am facing the redirect loop problem too. Luckily, I don't implement /metadata, /slo, /spslo paths, so I have temporarily undefined it now.

I just thought of one. How about adding an on_auth_path? method like this?
begin
  return options_call if on_auth_path? && options_request?
  return request_call if on_request_path? && OmniAuth.config.allowed_request_methods.include?(request.request_method.downcase.to_sym)
  return callback_call if on_callback_path?
  return other_phase if on_auth_path? && respond_to?(:other_phase)
rescue StandardError => e
  return fail!(e.message, e)
end

Ran into this today too, when when using omniauth with devise this totally masks any errors that happen.
It also makes it very very difficult to find out why things are failing.
Rescuing StandardError should be considered an anti-pattern; you could instead scope the errors you catch to specifically authentication errors.

Unfortunately, the commit that adds the rescue does not explain why the rescue was added.
Perhaps just undo it since there's no rationale included?
https://github.com/omniauth/omniauth/commit/ee2ef211d587fd35efac28ffd5c066cae4e7d021

@bisrael this was the PR in which it was added https://github.com/omniauth/omniauth/pull/689

If anyone can try out the branch for this pr and let me know if it resolves it for you: https://github.com/omniauth/omniauth/pull/1035


Correct BMC password credential limit

Should correct that the "BMC Password" character limit is 16 characters.
It is only stated for the "BMC Username"

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

ID: e4feaa2a-4850-478d-8122-7eb751ba0777
Version Independent ID: f5cd7372-0443-3f2e-c403-ed7ba1a56146
Content: Rotate secrets - Azure Stack Hub
Content Source: azure-stack/operator/azure-stack-rotate-secrets.md
Service: azure-stack
GitHub Login: @IngridAtMicrosoft
Microsoft Alias: inhenkel

@DiegoOrdonezHPE Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

in review

Please assign @BryanLa

@DiegoOrdonezHPE - thanks very much for your feedback.
I'm in the process of making major revisions to this article, and have included your feedback.
#please-close


Changing the value"editor.fontWeight": "normal" to anything below 400 doesn't make a difference.

VSCode Version: 1.17.0 (same was with previous version)
MacOS Version: 10.13.1 (same was with previous version 10.12.6)

Reproduces without extensions: Yes/No

This is the expected behaviour. pls see https://www.w3schools.com/cssref/pr_font_weight.asp
The value ranges from 100-900. 400 is the same as normal, and 700 is the same as bold


clarify the directions on how to upload

Maybe the UI has changed the docs were behind but now there is no button it is a drop down that allows Drag and Drop or browsing.

Resolve #203

@StevenTCramer Thank you, I have assigned this PR to the author for their review.

Hey @steved0x , I went ahead and made this change in the bulk branch I'm using for GitHub issues, you can close this without merging the changes. Again, thanks @StevenTCramer


[gtest] find_package(GTest) locates release version when CMAKE_BUILD_TYPE=Debug

Describe the bug
Attempting to build unit tests that link against gtest will fail when building in debug mode on Windows.
Environment
windows-2019 github action
To Reproduce
Steps to reproduce the behavior:

./vcpkg --triplet x64-windows-static gtest
build an application with -DCMAKE_BUILD_TYPE=Debug. Use find_package(GTest CONFIG REQUIRED) in CMakeLists.txt
compile applicant

Application fails to link
Expected behavior
Cmake should find a debug version of gtest.lib linked to the debug version of the standard library (/MTd)
Failure logs
  -- Found Threads: TRUE
  -- Found GTest: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/lib/gtest.lib
  -- Found unofficial-sodium: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/lib/libsodium.lib
  -- Found Protobuf: optimized;D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/lib/libprotobuf.lib;debug;D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/lib/libprotobufd.lib (found version "3.13.0")
  -- Found ZLIB: optimized;D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/lib/zlib.lib;debug;D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/lib/zlibd.lib (found version "1.2.11")
  -- Found Boost: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/include (found suitable version "1.73.0", minimum required is "1.73.0") found components: system filesystem missing components: stacktrace_basic
  -- Found Boost: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/include (found version "1.73.0") found components: thread chrono date_time atomic
  -- Found Boost: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/include (found version "1.73.0") found components: iostreams regex
  -- Found lmdb: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/lib/lmdb.lib
  -- Found OpenSSL: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/lib/libcrypto.lib (found suitable version "1.1.1h", minimum required is "1.0.1")
  -- Found unofficial-secp256k1: D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/lib/secp256k1.lib

...
  FAILED: tests/unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exe
  cmd.exe /C "cd . && C:\hostedtoolcache\windows\cmake\3.18.4\x64\cmake-3.18.4-win32-x86\bin\cmake.exe -E vs_link_exe --intdir=tests\blockchain\headeroracle\CMakeFiles\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\mt.exe --manifests  -- C:\PROGRA~2\MICROS~1\2019\ENTERP~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\link.exe /nologo @CMakeFiles\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.rsp  /out:tests\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exe /implib:tests\blockchain\headeroracle\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.lib /pdb:tests\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.pdb /version:0.0 /NODEFAULTLIB:libcmt.lib /NODEFAULTLIB:msvcrt.lib /NODEFAULTLIB:msvcrtd.lib /debug /INCREMENTAL /subsystem:console  && cmd.exe /C "cd /D D:\a\opentxs\opentxs\build\tests\blockchain\headeroracle && powershell -noprofile -executionpolicy Bypass -file D:/a/opentxs/opentxs/deps/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary D:/a/opentxs/opentxs/build/tests/unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exe -installedDir D:/a/opentxs/opentxs/deps/vcpkg/installed/x64-windows-static/debug/bin -OutVariable out""
  LINK Pass 1: command "C:\PROGRA~2\MICROS~1\2019\ENTERP~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\link.exe /nologo @CMakeFiles\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.rsp /out:tests\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exe /implib:tests\blockchain\headeroracle\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.lib /pdb:tests\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.pdb /version:0.0 /NODEFAULTLIB:libcmt.lib /NODEFAULTLIB:msvcrt.lib /NODEFAULTLIB:msvcrtd.lib /debug /INCREMENTAL /subsystem:console /MANIFEST /MANIFESTFILE:tests\blockchain\headeroracle\CMakeFiles\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.dir/intermediate.manifest tests\blockchain\headeroracle\CMakeFiles\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.dir/manifest.res" failed (exit code 1319) with the following output:
  gtest.lib(gtest-all.cc.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in main.cpp.obj
  gtest.lib(gtest-all.cc.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in main.cpp.obj
  gtest.lib(gtest-all.cc.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in main.cpp.obj
  gtest.lib(gtest-all.cc.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in main.cpp.obj
     Creating library tests\blockchain\headeroracle\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.lib and object tests\blockchain\headeroracle\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exp
  tests\unittests-opentxs-blockchain-headeroracle-add_checkpoint_already_in_best_chain.exe : fatal error LNK1319: 2 mismatches detected

considering that I use gtest myself i don't believe you are using find_package(GTest CONFIG REQUIRED) or are wrongly linking against gtests
Please show
a) the true context of the find_package call
b) the true context of the target_link_libraries call

Adding CONFIG to find_package fixes the vcpkg case. It breaks a few non-vcpkg build scenarios but those are issues for other bug trackers.

Hi @justusranvier,I cannot reproduce this on my machine( Windows10 )，Vcpkg version: 2020.06.15-nohash
Here are the steps I reproduced：
./vcpkg install gtest:x64-windows-static
CMakeLists.txt:
cmake_minimum_required(VERSION 3.0)

project(test)

add_executable(test CMakeProject16.cpp)

find_package(GTest CONFIG REQUIRED)
target_link_libraries(test PRIVATE GTest::gmock GTest::gtest GTest::gmock_main GTest::gtest_main)

CMakeSettings.json:
{
  "configurations": [
    {
      "name": "x64-Debug",
      "generator": "Visual Studio 15 2017 Win64",
      "configurationType": "Debug",
      "inheritEnvironments": [
        "msvc_x64_x64"
      ],
      "buildRoot": "${env.USERPROFILE}\\CMakeBuilds\\${workspaceHash}\\build\\${name}",
      "installRoot": "${env.USERPROFILE}\\CMakeBuilds\\${workspaceHash}\\install\\${name}",
      "cmakeCommandArgs": "-DCMAKE_TOOLCHAIN_FILE=F:/test3/vcpkg/scripts/buildsystems/vcpkg.cmake",
      "buildCommandArgs": "",
      "ctestCommandArgs": "",
      "variables": [
        {
          "name": "VCPKG_TARGET_TRIPLET",
          "value": "x64-windows-static"
        }
      ]
    }
  ]
}

 FinalizeBuildStatus:
    Deleting file "test.dir\Debug\test.tlog\unsuccessfulbuild".
    Touching "test.dir\Debug\test.tlog\test.lastbuildstate".
  Done Building Project "C:\Users\vzhli17\CMakeBuilds\f07d6b14-67bc-a335-9640-39316e44727b\build\x64-Debug\CMakeProject16\test.vcxproj" (default targets).

  Build succeeded.
      0 Warning(s)
      0 Error(s)

  Time Elapsed 00:00:04.09

Build succeeded.

Can you send me the CMakeLists that you use gtest?

@justusranvier: You can set https://cmake.org/cmake/help/latest/variable/CMAKE_FIND_PACKAGE_PREFER_CONFIG.html if you don't want to manually add CONFIG.
@JonLiu1993 he only used find_package(GTest REQUIRED) not find_package(GTest CONFIG REQUIRED) which is why it failed. Maybe a vcpkg_cmake_wrapper should be installed to always search for the -Config.cmake

@Neumann-A ,Okay, I will try to add vcpkg_cmake_wrapper

@Neumann-A I think we don't needed. vcpkg_cmake_wrapper in vcpkg is used to deal with mismatched cmake modules(Find*.cmake) and exported configurations(*-config.cmake).
In this case, the author just need to add keyword CONFIG in his find_package.

is used to deal with mismatched cmake modules(Find*.cmake) and exported configurations(*-config.cmake).

That is exactly the case here. The internal cmake FindGTest has other rules than the config.

@Neumann-A I prefer to use config mode because it's stronger, the module provided by cmake may be out of date, but it will not.
If we need to not use the CONFIG keyword and call them (to completely avoid to call the module provided by cmake) in the scene containing the exported configuration file, I think we should not implement it through vcpkg_cmake_wrapper.
This should be provided by vcpkg itself.

Also, FindGTest.cmake provides some special functions. If we add a wrapper, the user's right to use these functions is cancelled.
Closed this issue by solved.


[SPARK-38404][SQL][3.3] Improve CTE resolution when a nested CTE references an outer CTE

What changes were proposed in this pull request?
Please note that the bug in the SPARK-38404 is fixed already with https://github.com/apache/spark/pull/34929.
This PR is a minor improvement to the current implementation by collecting already resolved outer CTEs to avoid re-substituting already collected CTE definitions.
Why are the changes needed?
Small improvement + additional tests.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added new test case.

This backport is needed for https://github.com/apache/spark/pull/37751#issuecomment-1234336628
cc @cloud-fan

tests all passed https://github.com/peter-toth/spark/runs/8138671510

thanks, merging to 3.3!

@cloud-fan, for some reason this PR is still open after your merge to 3.3. Shall I close it manually?

let me close it


(fixed) nordic pkg installs plasma styles to the wrong directory

Description of changes

Things done

The nordic package was installing plasma styles $out/share/plasma/ which is the wrong path  i changed it to $out/share/plasma/desktoptheme/ which is the correct one

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

It looks like you accidentally mass-pinged a bunch of people, which are now subscribed
and getting notifications for everything in this pull request. Unfortunately, they
cannot be automatically unsubscribed from the issue (removing review request does not
unsubscribe), therefore development cannot continue in this pull request anymore.
Please open a new pull request with your changes, link back to this one and ping the
people actually involved in here over there.
In order to avoid this in the future, there are instructions for how to properly
rebase between branches in our contribution guidelines.
Setting your pull request to draft prior to rebasing is strongly recommended.
In draft status, you can preview the list of people that are about to be requested
for review, which allows you to sidestep this issue.
This is not a bulletproof method though, as OfBorg still does review requests even on draft PRs.


MAINTAINERS: Add a maintainer and collaborator for Silabs Platforms

Add Johan and Jerome to Silabs Platforms. Also update the subsystem and GitHub label name from "SiLabs" to "Silabs", since this is the more usual spelling.

Regarding the label change, I already renamed it in GitHub, so this PR will sync up with that.
CC @Jerome-pouiller @asmellby

Also, could one of the zephyrproject-rtos admins please add @jerome-pouiller to the GitHub organization, so that he can be added as reviewer, etc.

After internal discussion, added @asmellby as well as a Collaborator

I had overlooked that the hal_silabs section also needs similar updates. Now fixed. @carlescufi @kartben you'll need to re-approve - sorry for the hassle.


Remove logo and skywalking dev mail list

@heyanlong Since you have not decided the solution, I just try to remove the SkyWalking logo first.
I hope we could deal with the trademark and branding issue as soon as possible.

Two options

We try to donate this project to Apache incubator as a part of SkyWalking too. If you want and no dependencies license issues
Rename the project repo name and release name.

But for both solutions, I hope the old release under SkyWalking name could be removed.


style is broken on ubuntu

I can make correct pdf in windows.
but when I distribute on ubuntu, pdf is broken.
I have no idea why ubuntu has issue???

found out issue...
in option, pdf size unit was issue.
I changed unit to 'px' from 'in'.

zoom factor add in
in window zoom:1.0
in ubuntu different check it

https://stackoverflow.com/questions/37861807/html-pdf-npm-library-gives-different-output-on-windows-ubuntu
check this this will help you.

The CSS rule html{zoom: 0.7;} indeed helps, but also changing the width/height properties to px also improves the result.
The default values are the following config = { "height": "10.5in", "width": "8in" };
I changed them to the following assuming 96dpi to make the conversion from in to px.
config = { "height": "1008px", "width": "768px" }


create shallow relatedToOne objects from relationships hashes

Current
When loading models into the store, a relationships hash is added to each model. when the relationship is accessed, the model then looks in the store for the related object. However, if the model has not yet been loaded, nothing will be returned
const todoData = {
  attributes: { title: 'hello!' },
  relationships: {
    category: { data: { id: '1', type: 'categories' } }
  }
}

const todo = store.createModel('todos', '1', todoData)

todo.category
=> undefined

todo.relationships.category.data.id
=> '1'

store.createModel('categories', '1', attributes: { name: 'Cat5' })

todo.category
=> Category { id: '1', type: 'categories', name: 'Cat5' }

Proposal
Since we already have the relationship id and type, we should instantiate a model with just that information. (1) If it has been returned from the server, it is potentially useful to the application (for grouping, conditionals for polymorphism, etc). (2) It will be updated from the server if the model is later loaded.
const todoData = {
  attributes: { title: 'hello!' },
  relationships: {
    category: { data: { id: '1', type: 'categories' } }
  }
}

const todo = store.createModel('todos', '1', todoData)

todo.category
=> Category { id: '1', type: 'categories' }

store.createModel('categories', '1', attributes: { name: 'Cat5' })

todo.category
=> Category { id: '1', type: 'categories', name: 'Cat5' }

Tradeoffs
Current applications may use a null check on relationships as a proxy to see if data has been loaded into the store yet. This has the potential to invalidate those checks. However, this would allow a more targeted approach to conditionals based on model properties.

My thoughts on this -
I feel like looking for the id of a relationship to see if it's in the store is the best field to use - so I'm worried this will cause problems. Let's chat about specific problems this solves though!
If we do go this route are you planning on creating PRs for mobile and portal to update where we conditionally look for relationships before publishing this? I don't want us to get in a situation where we can't update to the latest mobx-async-store for a while.

superseded by https://github.com/iunu/mobx-async-store/pull/419


Display executable processes in deploy tool

Is your feature request related to a problem? Please describe.
In the collaboration diagram, the second participant is not marked as executable. It's OK regarding the best practices, however it can also lead to confusion when after 20 minutes of debugging your external task one discovers that the second pool is never deployed as an executable process (that's what happened during a microservices training).
Describe the solution you'd like
Display a list of processes which are actually deployed.
Describe alternatives you've considered
Leave it as it is.

To understand the impact of this issue: The user explicitly marked the second process as non-executable, right?

The opposite: the second participant added to a diagram is non-executable by default.

This is a bug, as all processes created by the user in the Camunda Modeler should be executable.
The executable fix we employ should take care of this.

@ingorichtsmeier Can you please share your opinion on this topic?

I take back my previous comment. :sheep:

This issue is indeed a valid feature request. :+1:


Output values are not changing for different inputs

Hi, I am using a movenet model from tfhub.dev with FrameProcessor and VisionCamera to try and apply human pose estimation to a person. It doesn't appear as though it is tracking my movements as the outputs in the console are always the same. This appears to be the case with all models I try to use.
Here is the link to the model
Here is the code I am using to resize the frame:
function getArrayFromCache(size) {
    'worklet'
    if (global[CACHE_ID] == null || global[CACHE_ID].length !== size) {
      global[CACHE_ID] = new Uint8Array(size);
    }
    return global[CACHE_ID];
  }

function resize(frame, width, height) {
    'worklet'
    const inputWidth = frame.width;
    const inputHeight = frame.height;
    const arrayData = frame.toArrayBuffer();

    const outputSize = width * height * 3; // 3 for RGB
    const outputFrame = getArrayFromCache(outputSize);

    for (let y = 0; y < height; y++) {
      for (let x = 0; x < width; x++) {
        // Find closest pixel from the source image
        const srcX = Math.floor((x / width) * inputWidth);
        const srcY = Math.floor((y / height) * inputHeight);

        // Compute the source and destination index
        const srcIndex = (srcY * inputWidth + srcX) * 4; // 4 for BGRA
        const destIndex = (y * width + x) * 3;           // 3 for RGB

        // Convert from BGRA to RGB
        outputFrame[destIndex] = arrayData[srcIndex + 2];   // R
        outputFrame[destIndex + 1] = arrayData[srcIndex + 1]; // G
        outputFrame[destIndex + 2] = arrayData[srcIndex];     // B
      }
    }

    return outputFrame;
  }

Here is my frame processor function:
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'
    if (model == null) return

    const newFrame = resize(frame, 192, 192)

    const outputs = model.runSync([newFrame])
    outputs = outputs[0]
    console.log(outputs[1])
  }, [model])

Here is the output in the console:

 LOG  0.46377456188201904
 LOG  0.46377456188201904
 LOG  0.46377456188201904
 LOG  0.46377456188201904
 LOG  0.46377456188201904
 LOG  0.46377456188201904

For each frame the camera sees the result is always the same.
Does anyone know how to resolve this issue?
Thank you

Please format your code properly.

I had a similar issue - in my case, the input size didn't match what the model was expecting. I'd also check that the model accepts uint8 input.
You can verify on https://netron.app

I had a similar issue - in my case, the input size didn't match what the model was expecting. I'd also check that the model accepts uint8 input. You can verify on https://netron.app

Hi, the frame input size and type (uint8) is correct. If it weren't, I wouldn't get console outputs above and I would get errors such as 'Invalid input size/type'.
My issue is that the output is not changing regardless of the input. If I understand correctly this model is meant to detect different features of the human body (nose, eyes, elbows, knees ect) and output values based on where they appear on the screen, which doesn't appear to be the case as the output values are always the same.

Does your newFrame contain new data each time?

Hi! Seemingly have the same problem. The resized image does change, however not the output of the tflite model.
I get the same when running your /example in this repo with the following output:
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 LOG  Running inference on 640 x 480 yuv Frame
 LOG  Result: 25
 ...

Well if the resized image changes but the output values don't then it might be an issue with your TFLite model? I am not sure if this is an issue here in this library...

Ok, I can confirm it was an issue with the input size as @willadamskeane suggested. For some reason, it does not output an error on wrong input size (e.g. 151x150 instead of 150x150 px using the vision-camera-resize-plugin).
If this is considered expected behaviour, from my end the issue can be closed.

@Silvan-M @s54BU Do either of you mind sharing your working code? I'm encountering the same behavior where the frame is updating but the results aren't. I've been using this model which should be the same as yours and have already been using vision-camera-resize-plugin.
My code is more or less as follows:
// ... imagine some model loading code here, poseModel is set in state somewhere
const poseModel = await loadTensorflowModel(
  require("../assets/movenet_multipose.tflite")
);

const maxPixels = 512;
// The longer side of the frame is resized to maxPixels, while maintaining the aspect ratio of the original frame.
let width, height;

if (frame.width > frame.height) {
  width = maxPixels;
  height = (frame.height / frame.width) * maxPixels;
} else {
  height = maxPixels;
  width = (frame.width / frame.height) * maxPixels;
}

// Resize the frame for more efficient inference
const resized = resize(frame, {
  scale: {
    width: width,
    height: height
  },
  pixelFormat: "rgb",
  dataType: "uint8"
});

const inference = poseModel.runSync([resized]);

@JEF1056, sure no problem! But I basically just used the example of the repo and changed it in such a way, that I can use as standalone application (without outer library, but library as import).
Also I don't use movenet, I used efficientdet. Looking at movenet multipose I find it kinda strange that don't require a specific input size (only a power of two) and when putting it into netron I get 1x1x1x3 as input (see screenshot). Not sure how this works, maybe someone else here has an idea if this works with this plugin.
You mentioned that the plugin returns [1, height * width * 3] this shouldn't be a problem since that's also the case for the example, which has [1, 320, 320, 3] and it seems to work well.
Your code looks good, however I could see a problem, since they require a width and height of a power of two (thus $2^x$ for some $x\in \mathbb{N}$). In your code this is only given for the larger image side, the other side is likely not a power of two, so make sure that both width and height are a power of two.
My example (adapted from /example): example-tflite.zip

After taking a look it seems that the 1x1x1x3 refers to a dynamic shape in tensorflow lite (e.g. 1 x null x null x 3) which would require you to resize the input shape first. It seems there was an issue thread here around adding support for this kind of behavior in this library but no specific API was made available for it
Unfortunately I don't have the C++ / native code experience to write a cohesive API around TfLiteInterpreterResizeInputTensor specifically for this libary- I might take a shot at writing some kind of wrapper with the patch in that PR, any thoughts? @mrousavy

Thanks for the quick response; It needs to get called after model loading but before memory allocation and model inference, so likely just before this line: https://github.com/mrousavy/react-native-fast-tflite/blob/main/cpp/TensorflowPlugin.cpp#L171
The best way to expose it as an API would probably be
loadTensorflowModel(source: ModelSource, delegate?: TensorflowModelDelegate, inputShape?: number[])

Where if inputShape is undefined, resize isn't called at all


Copy to clipboard feature

Would be cool if when clicking upon on of the icons like Kod grupy Termin ZOOM link etc, the contents of that (so for example zoom link, kod grupy) got copied to the clipboard

Good idea, I added to the list of features to be created in the new year.

IMO it would be better if the copy feature would work on right click (maybe menu) or some 'copy icon' next to contents as current zoom link click action is really useful.

IMO it would be better if the copy feature would work on right click (maybe menu) or some 'copy icon' next to contents as current zoom link click action is really useful.

Yeah, an icon would be the best choice

We are currently thinking about moving the application to the website, then the problem would be solved by itself :D

@waszkowski Do you mean making the app remote not desktop? It would help with sync between mutiple devices but in terms of security it would be better to migrate (at least mail) to OAuth2 as current way frequently triggers antivirus alerts about unverified connection.

I don't know what you mean by remote application. We are thinking of a web application.
The migration to Gmail started with OAuth. You can find the reason why we didn't do this at the link https://www.facebook.com/knnativeflow/posts/977167899359172


chat room

We can consider adding a chat room to the app. It's not hard to implementation a naive one but hard to make a good one. I don't know any library we can use to do this. Maybe we can try to create a room at slack and add a link to the room.

This is all too nice and easy: https://athanasea.ryver.com

There are a few chat packages in atmosphere. This one looks popular: https://atmospherejs.com/afruth/chapp


Some fixes + default extension

Hello,
I have started to use this extension, and after some tests I had to made some I think you may be interested :

A fix that allow to open the leaderboard more than once
I added default code (that do nothing) to be able to use the extension on simulator without exception + isSupported function to known if extension is supported on the current platform (so on simulator it returns false)

Has anyone fixed this? I almost got the ANE working perfect but it always crashed when I call the show Leaderboards


Standardize ETH contracts and Move modules names, parameters and functions

Is your feature request related to a problem? Please describe.
For the sake of consistency and clarity, it's important to use the same name for every aspect of a stack be it on Ethereum or Movement. it's also important to expect the same order of parameters.
Describe the solution you'd like

initiator param => originator
lockBridgeTransferAssets => lockBridgeTransfer
reorder function parameters
Add named errors
remove copy from BridgeTransfers (sneaking this safety update in here)

Describe alternatives you've considered
not including param reordering
Additional context

to fix your trouble check this fix, i see it in another issue,
https://github.com/aravinda-gamage/x86_64-win64-ranlib/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


There is no blueprint template for alexa.

The following stage has removed by AWS: "Select the Blueprints section and then use alexa-skills-kit-color-expert as the blueprint. It might help to type in "alexa" into the Blueprints search bar to narrow your results."
There is no blueprint template for alexa.

Having the same issue.

same problem

Under the serverless option. I have found the alexa skill set

Alex-Graham, OK.  So then what?  If you select "Browse serverless app repository" and then "alexa-skills-kit-color-expert, what do you do next?  It takes you to "Review Configure and Deploy", where all I can do is name the skill and enter a TopicNameParameter.  I can't follow the rest of the instructions at https://imgur.com/a/H5R7L/.  There is a "Copy as SAM Resource" near the top of the page, but I am lost as what to do next.

Under the serverless option. I have found the alexa skill set

Alex-Graham, OK.  So then what?  If you select "Browse serverless app repository" and then "alexa-skills-kit-color-expert, what do you do next?  It takes you to "Review Configure and Deploy", where all I can do is name the skill and enter a TopicNameParameter.  I have no idea what I should do with TopicNameParameter, but it's required. At this point, I am prevented from following the rest of the instructions at https://imgur.com/a/H5R7L/.  There is a "Copy as SAM Resource" near the top of the page, but I am lost as what to do next.

Fixed with the latest iteration of the setup guide. :) You won't need the blueprint/serverless app repository option for this to work.


fix: retain focus on chain select button

Resolves #184
Updated the SearchableSelect component to refocus the TargetButton whenever the dropdown menu is closed. Fixes the issues for both the ChainSelect and ChainSelectHref components.

Video

Hey @ryanpwaldon, thanks for creating this PR. Looks great! Only issue that I see is that the chainselect is now automatically focused on page load. Could you see if there's a way to prevent that?

Moved buttonRef.current?.focus() into handleSelectClose instead. Looks good on my end, but lmk if you spot anything else :)


Create onboarding process guide for submission of code into the repo

What detail is required beyond what is in the current CONTRIBUTING.md?

@murd0 none I don't think I just wanted to check with you before it was moved to done


1-1 BACKPORT: Use new handler for consensus gossip messages

Instead of using the GossipBroadcastHandler to send peer messages to
the consensus engine, use a new handler GossipConsensusHandler.
Notifying the consensus engine isn't a "broadcast" function, so it
should have a different handler. Now, the GossipBroadcastHandler will
simply pass when it encounters a peer message.
Signed-off-by: Logan Seeley<EMAIL_ADDRESS>Backport of PR https://github.com/hyperledger/sawtooth-core/pull/2019

This is a bug fix that affects the delivery of consensus messages; without this fix, a time to live value of 1 would prevent consensus messages from being sent to the consensus engine.


Update README.md

Description
Minor textual edits to conform with Dell style guidelines
Issues
List the issues impacted by this PR:

Issues

https://github.com/dell/karavi-observability/issues/28

Checklist:

[x] I have performed a self-review of my own changes.

@gallacher: Thank you for submitting your pull request!
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at<EMAIL_ADDRESS>

e2e pass


Please provide an option to encrypt full pages in obsidian

Please provide an option to encrypt full pages in obsidian  .
I don't need encryption ,just password protection so that no one who uses my computer can access a particular note , Kanban or mindmap

I would also love this capability, and would add that it would be awesome to encrypt files and folders. A use case would be for keeping a private journal inside a dedicated folder. Thank you for considering this!

I also don't need password protection for folders or files. But an option in MELT ENCRYPT to encrypt the full text (without text-selection) within a note would be great.

Hi @702573n , could you create a new issue for encrypting whole notes please?

Thinking about this further, I could implement another command to encrypt the whole page.  But decryption will always be inplace and directly to disk.  Which means if you have any syncing of your vault running,  the decrypted file would also get synchronised.
It would be up to the user to manage this and make sure they remember to re-encrypt the page once they are done editing.
Would this still be useful?


when attempting to import plugins in webpack i got the following js error

uncaught exception: sigma is not declared.

https://github.com/jacomyal/sigma.js/issues/880


[Foodtype Suggestion] Curry

Farmer's Delight is a very cool mod, and I am excited to play with it more, but I noticed that Rice only has a few uses, and with the Tatami blocks also added by the mod, I thought some types of curry could be interesting to see.
Utilising rice, chicken cuts, milk, onions or tomato, and perhaps other ingredients, a bowl of curry could be created. Perhaps some alternate types of curries, with different sauce ingredients and meats could also exist, similar to stews/soups already present in the mod. The other ingredients could include stuff like cocoa beans, mutton chops, fish slices, bacon, or eggs.

Hello @dhi-holo, it seems to be a good suggestion :), thank for report it, but I'll not add things that is not in the initial mod (forge version). My goal is only to "port" the original mod for Fabric loader.
So you can repost your suggestion in the github or Discord of original Farmer's Delight mod (forge version).


Create minimum.c

Hi Dear @HIDE810
Great code
Thanks for your contribution......
Show your support on my youtube channel web Pixar(The institute of coding)
like , share , subscribe
youtube - https://youtu.be/5qnQjgdpFPg
telegram-channel - https://t.me/WebPixar
join our telegram channel for more goodies , swag packs


[reproducer only] ApplicationGenerator instance sometimes not idempotent: is this problem?

Hi @tarilabs , can we close this PR or is something still to be done? Thanks

The Linux check has failed. Please check the logs.

No idea @r00ta https://github.com/kiegroup/kogito-runtimes/pull/133#issuecomment-804770983
I raised the point to the kogito leads but I never received a feedback if this is a problem or not 🤷♂
Maybe @danielezonca is something you want to be aware of, that I discovered a while ago?

No idea @r00ta #133 (comment)
I raised the point to the kogito leads but I never received a feedback if this is a problem or not
Maybe @danielezonca is something you want to be aware of, that I discovered a while ago?

Ok np, I woke up this morning with the (bad) idea to check all the old opened PRs to understand if they can be closed or what :)

Closing as stale/inactive, please reopen if required.


Setting additionalLogProperties gives error

Hello,
I was trying to set some logging properties with additionalLogProperties field, with something like
additionalLogProperties:
  - "log.path=var/log/server.log"

However I got an error java.lang.IllegalArgumentException: No enum constant io.airlift.log.Level./VAR/LOG/SERVER.LOG
After some trials, I found out that the logging properties may need to be set in config.properties instead of log.properties, which is supposed to contain only log level.
Would someone be able to valid that it's a valid issue, and confirm whether the similar issue exists for other additional* variables in the chart ? Thanks in advance.

Log properties should be set in log.properties file .. which is what the chart does. The additionalLogProperties be single log lines for that file in the format package=loglevel
The linked logging properties are for configuring logging .. not for setting log levels. It might be a bit badly named ...

Thanks for the explanation ! Closing the issue


Versions of Configuration Manager that MBAM supports

I noticed on the MBAM Supported Configurations page it states that it supports Configuration Manager 1610 but no mention of higher versions. Should we be requesting this be updated to state “version 1610 and later”?

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

ID: 3bd86f5e-6388-d226-2460-997fc24945d9
Version Independent ID: aa827a7d-725a-a5d0-f6aa-3f1df8cc310a
Content: MBAM 2.5 Supported Configurations
Content Source: mdop/mbam-v25/mbam-25-supported-configurations.md
Service: unspecified
GitHub Login: @jamiejdt
Microsoft Alias: jamiet

@jamiejdt -- Can you take a look at this issue?


CLI option for update frequency

Is there a CLI option to set how many seconds between mouse movment? I just see -j for start with enable checked.

I have a PR open for this feature, but @cerebrate hasn't got to it yet.
https://github.com/cerebrate/mousejiggler/pull/17

Willing for this too, great job anyway ! I love this app even if it's minimal

Functionality included in upcoming 2.0 release.

Functionality included in upcoming 2.0 release.


[RHOAIENG-11850] Updated etcd manifest

Updated the manifest to include requests and limits for the etcd deployment.
Tested by applying resource quota to the redhat-ods-applications project and viewing which resources did not automatically rollout after applying the rq.
After finding that the etcd deployment was the only pod that was not automatically redeployed, viewed the metrics for the etcd pod with no changes to find the request boundaries, and then added and deleted multiple ISVC's to find the limit boundaries.
Instructions to apply ResourceQuota:
Here is a copy of the RQ I used:
apiVersion: v1
kind: ResourceQuota
metadata:
  name: compute-resources
spec:
  hard:
    pods: "4"
    requests.cpu: 50m
    requests.memory: 96Mi
    limits.cpu: "1"
    limits.memory: 512Mi

2 ways to apply -- CLI or UI

Using the CLI, ensure you are logged into the cluster, and using the intended project you want to apply the RQ to (in this case we are applying to the redhat-ods-applications project/namespace.
a. in the directory where you have saved the above RQ yaml, run oc apply -f <nameOfResourceQuota.yaml>

Using the UI, there are 2 ways -- Creating a Pod or a ResourceQuota directly

Creating a Pod to create a ResourceQuota:
a. In the sidebar, navigate to Workloads, and then Pods.
b. Ensure you are in the project you want the RQ applied to. There is a drop-down list at the top left of the screen.                  In this case we are using the redhat-ods-applications project
c. Click the blue "Create Pod" button at the top right of the page, and paste the RQ yaml defined above.
d. Click the blue "Create" button at the bottom.  -- View the ResourceQuota by navigating to the sidebar again,             clicking Administration > and then Workloads.
Creating a ResourceQuota Directly:
a. In the sidebar, navigate to Administration > and then ResourceQuotas.
b. Ensure you are in the project you want the RQ applied to. There is a drop-down list at the top left of the screen.                  In this case we are using the redhat-ods-applications project
c. Click the blue "Create ResourceQuota" button at the top right of the page, and paste the RQ yaml defined above -- or you can manually edit the values you want for the RQ.
d. Click the blue "Create" button at the bottom.
Once the RQ is applied, modify the request and limit values to satisfy the resources in your project. The deployments that are not automatically redeployed are the deployments that do not have resource values defined.
Motivation
Modifications
Result
PR checklist
Checklist items below are applicable for development targeted to both fast and stable branches/tags

[ ] Unit tests pass locally
[ ] FVT tests pass locally
[ ] If the PR adds a new container image or updates the tag of an existing image (not build within cpaas), is the corresponding change made in live-builder and cpaas-midstream to add/update the image tag in the operator CSV? Link the PRs if applicable

Checklist items below are applicable for development targeted to both fast and stable branches/tags

[ ] Tested modelmesh serving deployment with odh-manifests and ran odh-manifests-e2e tests locally

So, I have tried this. I had to tune the ResourceQuota to let pods to be created successfully.
Despite applying the fix here, I still saw the problem reported in the ticket:
Error creating: pods "etcd-68d5dbd5f7-ssffm" is forbidden: failed quota: compute-resources: must specify limits.cpu for: etcd-secret-creator; limits.memory for: etcd-secret-creator; requests.cpu for: etcd-secret-creator; requests.memory for: etcd-secret-creator
Looks like the existing resources aren't the problem, but it is the initContainer (which is the one named etcd-secret-creator, as noted in the error) not having any resources set. Observe here: https://github.com/opendatahub-io/modelmesh-serving/blob/main/config/overlays/odh/quickstart.yaml#L50-L78 the missing resources field.
The PR as is is lowering the memory limits of the etcd container. IMO, if current requests/limits are working (given the right allocation of quotas) we should keep them untouched, and only fix the missing resources spec of the etcd-secret-creator initContainer.


binutils: fix the kernel build for PowerPC

Description of changes
The kernel fails to build on PowerPC. This is a bug unrelated to NixOS, but it is patched upstream, so I'm proposing to add it here.
Fun fact: Yocto is using an untagged version of binutils from the binutils-2_38-branch branch. This fix missed the tag by 14 days :slightly_smiling_face:
To test the changes:
let pkgs = import nixpkgs {
    system = "x86_64-linux";
    crossSystem =
      nixpkgs.lib.systems.examples.ppc64 // {
        linux-kernel = {
          # ppc64e_defconfig implies DEFAULT_UIMAGE which needs U-Boot
          target = "uImage";
          # But somehow there is no Make target to install the uImage...
          # I should create a separate issue for this.
          installTarget = "install";
          baseConfig = "ppc64e_defconfig";
          autoModules = false;
          name = "ppc64e";
        };
      };
  };
in pkgs.linux

Pinging @ericson2314 and @lovesegfault as maintainers. @r-burns might also be interested.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@Mindavi I thought patching only for this architecture would be better to avoid rebuilding the whole world for those not impacted. I seem to remember seeing quite a bit of conditional patches for packages closely tied with cross-compilation.

Yeah, that makes sense right now to prevent a world rebuild.


Leverage Quarkus code generation for Salesforce DTO generation

It'd be good if we could leverage the code generation features of the quarkus-maven-plugin to do the generation of the Salesforce DTOs.
Currently this is handled by the camel-salesforce-maven-plugin. If we could make the core logic available is some artifact that our extension would depend on, then we should be able to add hooks for the generate-code mojo.

I aussme that the basic idea here is to implement such a class
public class CamelSalesForceCodeGen implements CodeGenProvider {
    @Override
    public String providerId() {
        return "camel-salesforce-codegen";
    }

    @Override
    public boolean trigger(CodeGenContext context) throws CodeGenException {
        /* the core logic in camel-salesforce-maven-plugin to generate DTOs */
        /*
             1. fetch Object descriptions by RestClient
             2. use velocity engine to generate the DTOs java codes
         */
    }

}

some properies could be similar with the camel-salesforce-maven-plugin Mojo parameters
quarkus.camel.salesforce.codegen.skip = false
quarkus.camel.salesforce.codegen.includes = Account
quarkus.camel.salesforce.codegen.includePatterns = *
...

What's the benifit we can get from this enhancement ? Maybe generate different codes with  launch mode, coulde be useful for testing purpose..

What's the benifit we can get from this enhancement ?

I think the main benefit is the ergonomy: end users do not need to maintain an extra version of an extra Maven plugin. All is done via Quarkus plugin (that must be there anyway) and the underlying CQ extension that must be there too.

@jamesnetherton I found there is a change in CodeGenContext which uses Config config instead of  Map<String, String> properties to read the properties in build time.
https://github.com/quarkusio/quarkus/commit/afaca21cc49064a78f79ce14345681065faf9e46#diff-093e7aa039ebc68d29ba9fe5eee571a0298831111766385c33987bd227e62962
I assume that we need to use the Config to read the properties of quarkus.camel.salesforce.codegen.. So we might implement CamelSalesForceCodeGen in quarkus-main branch. WDYT ?

So we might implement CamelSalesForceCodeGen in quarkus-main branch. WDYT ?

Quarkus 2.5.0.CR1 will be released some time today. So I'll be merging quarkus-main to main. So lets wait for that and any work related to cogen can continue on main as per normal.

Some random things on this topic:

wonder if the same model can then be extended to servicenow and openapi route generator
wonder it we can leverage camel components extension to have a generic generator at Camel level that camel quarkus can leverage

wonder if the same model can then be extended to servicenow and openapi route generator

Yes, I was thinking the same thing. We should try to do the same for those other extensions. I can create issues for that.

wonder it we can leverage camel components extension to have a generic generator at Camel level that camel quarkus can leverage

I think that's the general aim. I.e have something in Camel that both the maven plugin and quarkus extension can reuse so we don't end up reinventing everything in CQ.

raise upstream CAMEL-17306 to refactor the DTO generation codes.

yeah, feel free to take this issue. Thanks!


Publishing not ready endpointslices to cloudmap

The current implementation syncs the not ready IPs also to cloud-map from the endpointslices. This ends up publishing not ready IPs to cloud-map. Can we make it a flag to push only healthy IPs to cloud-map?

We will have a look into this.

Fixed by https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/210


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #229 (9ef6365) into main (2974dfe) will increase coverage by 8.72%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #229      +/-   ##
==========================================
+ Coverage   83.33%   92.05%   +8.72%
==========================================
  Files           2        1       -1
  Lines         126      340     +214
  Branches       31       40       +9
==========================================
+ Hits          105      313     +208
- Misses         21       27       +6

Impacted Files
Coverage Δ

src/index.ts
92.05% <100.00%> (+10.05%)
:arrow_up:

example/src/main.ts

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 7be23a0...9ef6365. Read the comment docs.


Use networkingv1 instead of extensionsv1beta1

Fixes https://github.com/gruntwork-io/terratest/issues/840
NOTE: due to the way the k8s APIs are designed, we have no choice but to duplicate the functions to support the separate API versions.

Thanks for review! Build failed, but it looks like it is unrelated to this change, so going to merge + release this!