Webhook triggering Jenkins builds on all open PRs and master

It seems like when a PR finishes its Travis build and triggers the web hook on Jenkins, that causes a rebuild of every open PR and the master branch. In this case, it looks like #192 finished Travis triggered all of these builds:

#200 that I opened yesterday isn't running Jenkins at all :(

#200 ran because I manually did "Scan Repository Now" just to make sure that it would be picked up that way.  I still have to figure out how instruct the webhook to provide appropriate information about what should be built.  Fundamentally, it's the same problem as how to ensure that lots of builds in other branches don't get triggered for every PR.

Closed by #214


chore(feat-multi-module-components): release 0.92.9

:robot: I have created a release beep boop
0.92.9 (2024-10-03)
Features

support for component level default tags (#340) (6a742c2)

Misc

bump github.com/runatlantis/atlantis from 0.28.4 to 0.30.0 in the atlantis group across 1 directory (#339) (10c626f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vincenthsh/fogg/releases/tag/v0.92.9 :sunflower:


Fixes #276 - Allow use of aligned heaps

Before we merge, we'll need to add some tests for the new interface.

I had a look, but as you said, it was a bit tricky to figure out where and how to add the tests :sweat_smile:

I can give you guidance on navigating our test suite.

I'm happy to take a stab at it, if you give me some details... Could you let me know where the right place in the repo would be for these tests? Any additional guidelines would be appreciated as well.

It might be a little bit before I can get to doing that, so if merging the PR quickly is important

If this is a matter of a couple of weeks, I'm happy to wait as well :smiley:

If this is a matter of a couple of weeks, I'm happy to wait as well

A couple weeks sounds about right. I'd also like to use this as an opportunity to write some better docs about how our test suite is laid out. We have the start of docs on the wiki but that page is not sufficient to answer your questions.

@shravanrn sorry for the delay on this. I've added more detail to the wiki page that hopefully helps answer your questions.
To make the advice there specific to this use case, I would put unit tests in /lucet-runtime/lucet-runtime-internals/src/region/mmap.rs or a new child module, depending on size; integration tests should probably go in /lucet-runtime/tests.
Another idea that could help get a lot of test coverage quickly without too much new typing would be to create a wrapper type, something like AlignedMmapRegion, that would create an underlying MmapRegion with a particular alignment. Then, where you see the test macros instantiated with MmapRegion, you could add another instantiation with AlignedMmapRegion. I think it'd still be worth writing some tests that are specific to the alignment APIs, though.

That's great! Thanks for the info. This next week unfortunately is pretty busy, but I should be able to get some tests written up the following week.

Hi,
Sorry for the delay here. I got pulled away on some other stuff and have finally resumed the lucet changes. I have rebased and added some tests. Does this look ok?

@acfoltzer @pchickey - just following up about this

Have made requested changes.


Values missing due to omitempty

First of all, thank you for this package! It is awesome and super simple to use. Great job!
I've got my message definition
message Points {
  int32 team_a = 1;
  int32 team_b = 2;
}

which is translated into a Go type.
type Points struct {
	TeamA int32 `protobuf:"varint,1,opt,name=team_a,json=teamA" json:"team_a,omitempty"`
	TeamB int32 `protobuf:"varint,2,opt,name=team_b,json=teamB" json:"team_b,omitempty"`
}

I'm using JSON to communicate between browser and twirp backend. Now I've got a match where team_a = 2 and team_b = 0. In the browser the value for team_b is missing since 0 is the zero value for int. Those are left out due to the omitempty flag.

The "omitempty" option specifies that the field should be omitted from the encoding if the field has an empty value, defined as false, 0, a nil pointer, a nil interface value, and any empty array, slice, map, or string.

That's a bit annoying :)
Any ideas how to make it work? How do you handle those cases at Twitch?

Hi @zemirco — the json field tags are a bit of a red herring. What you're seeing is part of how proto3 messages are encoded: default values aren't sent. The proto3 guide says that when a message is deserialized you can't tell whether zero values were set or not, and it uses that to save space/time on the wire by not sending zero values of primitives in the first place.
The way to work around this is by using the "wrapper" message types defined in google/protobuf/wrappers.proto. The types defined there are known to the jsonpb package and get encoded as primitive values, not as nested messages.
import "google/protobuf/wrappers.proto";

message Points {
  google.protobuf.Int32Value team_a = 1;
  google.protobuf.Int32Value team_b = 2;
}

Keep in mind that Twirp's json encoding is done with the golang/protobuf jsonpb package rather than by encoding/json, and that the jsonpb.Marshaler has OrigName set. That means that the json field names will match the protobuf field names rather than being a weird lowerCamelCase version (yay), but that the json_name annotation will be ineffective.

Thanks for the quick reply.
With google.protobuf.Int32Value I'd have to use the .Value workaround. For now I simply use
sed -i "s/,omitempty//" service.pb.go

A bit hacky but works for me.

Yeah, this is the way the JSON format for protobuf data works. In protobuf, there is no distinction between a zero value and an unset value, so what you're seeing is entirely correct. omitempty is not really what's doing this; it's the way jsonpb works and is defined by a pretty thorough specification.
If you want to distinguish between an unset value and a zero value, you need to use the wrapper types that @rhysh linked to.
@zemirco, could you say a little more about how this is affecting you? Ideally, with Twirp, the serialization of the request and response are just implementation details. If you're using a generated JavaScript client, you shouldn't need to care about the fact that the JSON encoding skips zero values.

I'm not using one of the generated JavaScript clients. Wanted to keep it simply and just use fetch. e.g.
    fetch('twirp/trpc.Haberdasher/GetMatchesPoints', {
      headers: {
        'Content-Type': 'application/json'
      },
      method: 'POST',
      body: JSON.stringify({...})
    })
    .then(response => {
      return response.json()
    })
    .then(data => {
      console.log(data)
    })

Using the wrapper types work fine for the frontend (zero values are now included) but in my backend my model now looks like this.
type Points struct {
	TeamA *google_protobuf1.Int32Value `protobuf:"bytes,1,opt,name=team_a,json=teamA" json:"team_a,omitempty"`
	TeamB *google_protobuf1.Int32Value `protobuf:"bytes,2,opt,name=team_b,json=teamB" json:"team_b,omitempty"`
}

Using it with some data makes it a bit more complicated.
	p := &Points{
		TeamA: &wrappers.Int32Value{
			Value: a,
		},
		TeamB: &wrappers.Int32Value{
			Value: b,
		},
	}

I wrote a code generator for plain JavaScript without any dependencies. Check it out at https://github.com/zemirco/protoc-gen-twirp-es. It's my first time writing a code generator for protobuf so please by nice :smiley: I'm very thankful for feedback.
It's actually pretty simple. Here is my .proto file
message Player {
  string hash_id = 1;
  int32 user_id = 2;
  string first_name = 3;
  string last_name = 4;
}

service Haberdasher {
  rpc GetPlayer(google.protobuf.Int32Value) returns (Player);
}

Here is the generated code
const GetPlayer = async (input) => {
  const res = await fetch('twirp/trpc.Haberdasher/GetPlayer', {
    headers: {
      'Content-Type': 'application/json'
    },
    method: 'POST',
    body: JSON.stringify(input)
  })
  const data = await res.json()
  const Player = {
    hash_id: data.hash_id || "",
    user_id: data.user_id || 0,
    first_name: data.first_name || "",
    last_name: data.last_name || ""
  }
  return Player
}

export {GetPlayer}

As you can see every field is now included in the result. If the field is undefined the zero value is used. This way you can always be sure to get some value.
The indentation (in the resulting file) is a bit off but that's OK for now. It also works for nested messages and arrays. In your code you simply use it like this.
import {GetPlayer} from  './service'

const player = await GetPlayer(1)

That's pretty sweet now. Thank's for building Twirp!


Change the google analytics event catagory, action and lable

Use different methodology to manage the 3 layers event info:
1 In the event category, use: "Role - nav - category"
2 In the event action, which fits our test plan:
"Mac - Safari", "Windows - Chrome", "Android - Chrome", "iPhone - Safari", "Other"
3 In the event label:
"gender- age- language"
The age should be: "young(1-30)", " mid-age(31-60)", "senior(61+)"

Branch analytics-test created, and the new hosting web is : https://canbewell-test.web.app/
Google analytics has not changed it. Also the firebase logging.
Possibly, the GaEvent will be mixed-up, but will not test this schema in the master site.
This branch is currently only for test.

The hosting web site is in the same firebase project, and the only necessary change for deploying on the different websites is in the firebase.json : { hosting: { site: {$sitename} }.
Need to switch it back if use this in master


Caching mistakes in "Hires. fix" by LyCORIS? LyCORIS model settings called in the past with lyco: are resurrected again when Hires. fix.

LyCORIS model settings called in the past with lyco: are resurrected again when Hires. fix.
Example:
1st prompt & Hires. fix
lyco:lora-weights:0.2:1.5→
========================================
Apply LyCORIS model: lora-weights
Text encoder weight: 0.2
Unet weight: 1.5
DyLoRA Dim: None
========================================
(Here is the progress bar during hiresfix.)
========================================
Apply LyCORIS model: lora-weights
Text encoder weight: 0.2
Unet weight: 1.5
DyLoRA Dim: None
========================================

Second prompt & Hires. fix
lyco:lora-weights:1.2:2.5→
========================================
Apply LyCORIS model: lora-weights
Text encoder weight: 1.2
Unet weight: 2.5
DyLoRA Dim: None
========================================
(Here is the progress bar during hiresfix.)
========================================
Apply LyCORIS model: lora-weights
Text encoder weight: 0.2
Unet weight: 1.5
DyLoRA Dim: None
========================================

If lyco: is deleted, it will be restored during Hires.fix.
Is it because of cache settings etc?

Wow, it looks like the equals I pasted from the terminal did a bad job, sorry.

I think the problem is by sd-webui
since this part is not managed by my extension

Sorry, I didn't notice the spec change!
There is a separate prompt input area that is applied during the hires.fix and it was written there!
Sorry for the hassle, thanks for the response!


Click noise when skipping songs

I am experiencing the opposite issue as this: https://github.com/dtcooper/raspotify/issues/231
This is happening on a raspberry Pi zero with a DAC hat board.
raspotify version 0.16.0~librespot.v0.1.3-37-g0adb851 armhf
If I allow the music to flow from a tune to another everything works flawlessly.
If I skip manually to another tune, then I hear a popping sound similar to a clipping one.
The logs don't report anything problematic.

In my case, when I skip songs it sounds like spotify is replaying 1-2sec of last song.

In my case, when I skip songs it sounds like spotify is replaying 1-2sec of last song.

I have the exact same issue. A loud crackling sound when skipping or changing song. Using a Pi Zero and playing through the USB which is plugged into my dac/amp.

The new release is live. Please update and see if that solves your issue.

This is an upstream issue. If after updating to the latest version of Raspotify the issue persists please file a bug with librespot.


program not opening

i extract the file and run the executable and it creates a text file called engine_run.log which contains the text, "20:13:04 [INFO] Creating renderer for window size [1920, 1080]" and then nothing else happens. I am on windows and i have python, cmake, and ninja installed, and i have allowed the program to run. Any ideas?

thanks again for the response. Im pretty new to guithub, so im not entirely sure what you mean. Could you elaborate further?

That would require use of the command prompt.

Install git for windows https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
Open command prompt, type git clone https://github.com/hakolao/sandbox enter
type cd sandbox to enter the folder of the project
type cargo run --release. If you don't have Rust (and cargo) installed, install that first https://www.rust-lang.org/tools/install, reopen command prompt and try again (cd sandbox) then cargo run --release.

There may be some things missing from this, but running this indeed needs some technicality. Apologies. This isn't really a game, more of a test project to learn to make pixel simulations.


Fix: Serialize task: Don't serialize derivation context or even entir…

…e Nar objects in operators just because ^believe is part of a term of the task. So The nar member was removed from operator, and also the DerivationContext member in Anticipate.

I agree, good point, will set it to 65535 which should easily enough for our purposes.


Web UI and CLI for Archaius (& soon Eureka) with FF4j

First, I would like to thank you for the material you provided to the community, NetFlix OSS rocks ! This "issue" is neither a bug report nor a pull request. This is for communication / awareness and maybe to get some feedbacks on the work I did.
FF4j
FF4j  is a proposition of framework to implement Feature Toggle pattern in Java.

You can enable and disable features at runtime through provided clients and consoles (Web, CLI, JMX).
You can persist the features states in different technologies like JDBC, Redis, Mongo, Neo4j, Cassandra, Elastic, JCache, EhCache...*
Features have not only a status (true/false) but can be enabled for dedicated users (Canary release) or/and have a custom strategy (Pattern Strategy)
You have metrics of the usage of your features.

Properties
We noticed pretty soon that "features states" are very closed from properties (at the end of the day they are "only" properties of boolean type). Yet, they are not used in the same way and this is the reason why we created aside the "PropertyStore" interface to implement CRUD operations on properties. In the same way as FeatureStore we also provided UI and clients.

Archaius and Commons configuration
For version 1.6.x we implement wrappers & bridges to combine CommonsConfiguration/FF4J and Archaius.
Use the FF4J properties as a source for Commons-configuration
You already has set up your application to use commons configurations but feel limited as the existing Configuration  are limited to properties and xml files. Use the FF4jConfiguration to inject properties coming from other sources. sample code

Use the FF4J properties as a source for Archaius
Sample principle as before. Archaius leverage on commons configuration and provides new sources for properties. You can use the FF4JConfiguration and add FF4J properties to the dynamic configuration. Archiaus also introduce the PolledSourceConfiguration mechanism to polled target properties provider and update configuration accordingly. The ff4j-archaius module propose and implementation of PolledSourceConfiguration to work with FF4J. sample code

Objective : You can now use Archiaus with properties coming from : JDBC, Redis, Mongo, Neo4j, Cassandra, Elastic, JCache*, EhCache*
Use Commons Config for FF4J property store
If properties are defined in a ff4j  PropertyStore, they will be available in the web UI and CLI. AS a consequence you can perform CRUD operations through UI (caution some stores are read-only). sample code

Use Archiaus for FF4J property store
Sample principle as before with Archaius, define a PropertyStore to work with a dynamic configuration, you will get all properties values in the UI. sample code

Objective:

You will have a  CLI to edit and display properties.

You will have a dedicated WebUI to see properties, and edit them.

As a working sample is always better than documentation or long text you can test it yourself here:
Let me know if you find this useful, well any feedbacks are welcomed.
NB: Next version of ff4j will provide the FeatureStore and PropertyStore to work with directly with Eureka.

It would be really interesting tool! Is this WIP?

it's ready and working. Please find here a working sample:
https://github.com/clun/ff4j-samples/tree/master/ff4j-sample-archaius
FF4J is about 10k download per month from Central and I was surprised with the "no reaction" effect of this entry. Any feedbacks are more than welcomed.

I'm testing it right now! I'll back with my feedback and questions. Thank you very much!

It's working as expected, test it if you wish, I can close this issue


minor typos

Thanks for the PR. We ended up making the changes in the source code instead of the readme. :)


Arduino IDE states 'Category in library FlowMeter is not valid'

Expected behavior
Everything is fine while compiling for ESP8266 on the Arduino IDE.
Observed behavior.
Arduino IDE 1.8.5 reports warning:

WARNING: Category 'Device Control Sensors Sensor Measurement Liquid Water Flow Meter' in library FlowMeter is not valid. Setting to 'Uncategorized'

Took me a while to respond, sorry. Swamped with work. Will look into it soon.

Would be cool if you could merge the two pull requests from @per1234 .
Cheers

Giving up due to time constraints, accepting without prior tests. ;)


IIS deployment information

Describe the feature
It would be nice to have ISS added to the nitro provider list.
Additional information

[X] Would you be willing to help implement this feature?

Let's track via https://github.com/unjs/nitro/issues/1427


[Bug] fix wrong null flag

Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Why not adjust null_map pos inside set_source_column?

set_source_column

@cambyzju If we do so,  inside get_data_at,  offset will be never applicate for nullmap any more so we have to add a different offset for column data and null map. I think it's a bad implement so I just did this.


Downloadr does not find all Flickr albums

Trying to download photos from an album and for whatever reason Flickr Downloadr only finds a subset of albums.  Not sure why.

Please check if the following field is blank, otherwise it will trigger a
filter of only the albums whose name matches its value:
[image: image.png]
On Fri, Jan 3, 2020 at 2:07 AM Lampornis<EMAIL_ADDRESS>wrote:

Trying to download photos from an album and for whatever reason Flickr
Downloadr only finds a subset of albums. Not sure why.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/flickr-downloadr/flickr-downloadr-gtk/issues/110?email_source=notifications&email_token=AAQU6ST4PT4ZSKV3775F6HDQ32FWLA5CNFSM4KCINC4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IDZFYAQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQU6SQJ42J3CUL26NW5TO3Q32FWLANCNFSM4KCINC4A
.

Thanks for the quick reply.  The image you attached is not showing up.  Can you repost it?  Thanks!

Thanks.  I actually do enter an album name in the field because I am trying to download photos from specific albums.  However, when I leave this field blank it tells me I have 800+ albums, but only shows about half of them.  I did end up solving the problem by tagging all the photos in the album of interest and creating a new album in Flickr.  It was able to download the new album.

I have +4000 albums, and it shows me all of them (paginated on 19 pages).

Not sure if this is related, but I've seen albums that I can go to if I have the link but they're not listed in the user's Albums list. Example:

Albums list - https://www.flickr.com/photos/superjens/albums
An album not in list - https://www.flickr.com/photos/superjens/albums/72157606964580760/


Improved and fixed interactive play script

Motivation and Context

The rendered image and text was flipped the wrong direction. Other sensor images were not being rendered to the screen, now all sensors are automatically rendered. Refactored observations_to_image to allow variable sized sensor images. The different image sizes are now tiled side by side.
How Has This Been Tested

Via the interactive play script: python examples/interactive_play.py --cfg configs/tasks/rearrangepick_replica_cad_example_ik.yaml
Added a new test test_different_dim_observations_to_image for new changes to observations_to_image utility function.
New test test_rearrange_example_modules to make sure the interactive_play script runs.

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Example of interactive play output:
https://user-images.githubusercontent.com/877440/126211420-e2802555-8d2a-47c1-8ebd-4b6c67aa8bcd.mov

Example of interactive play output:
https://user-images.githubusercontent.com/10453381/125808852-fc4e3f07-3eba-4042-a8ef-3232bc7e0272.mov

@mathfac I improved code readability based on comments.


Upgrade consul-template to v0.12.2

Changing the binary target because the zip does not expand into a subdirectory. This is consistent with other Hashicorp tools in the caskroom.

Thank you for the contribution. It was merged directly as 1cedc65d9c93810c70c6d66ba516f440d61bdc34 to keep commit history cleaner. Your contribution is still credited to you.


fix player can bypass the maximum chatbox/playerdetector range by setting a negative range

PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION

Please check if the PR fulfills these requirements

[x] The commit message are well described
[x] All changes have fully been tested

What kind of change does this PR introduce? (Bug fix, feature, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)

#623

Does this PR introduce a breaking change? (What changes might users need to make in their scripts due to this PR?)
No

Didn't see that this is a draft on my phone
Woops

Yeah player detector has same issue, fixing rn


Use lttng_ust_tracef instead of lttng_ust__tracef

Follow-up to #95
Follow-up to #98
The "official" symbol that the LTTng documentation mentions is:

>=2.13: lttng_ust_tracef(), not lttng_ust__tracef()

Docs: https://lttng.org/docs/v2.13/#doc-tracef
Code: https://github.com/lttng/lttng-ust/blob/2e8e974039487cb8b2b22dc01ffdd6c9931ec02b/include/lttng/tracef.h#L23

<=2.12: tracef(), not _lttng_ust_tracef()

Docs: https://lttng.org/docs/v2.12/#doc-tracef
Code: https://github.com/lttng/lttng-ust/blob/6b0c6b76480d8162cb00919367cc2d13ccbe7037/include/lttng/tracef.h#L35

I thought that the difference between them is that the former checks if the tracepoint is enabled before triggering the tracepoint, while the latter just triggers it, but that is not the case. We can observe this by not enabling lttng_ust_tracef:event in tracetools_test/case.py: the tracepoint does not get triggered. The latter still ends up checking if the tracepoint is enabled before triggering it. The difference is that the latter formats the string using vasprintf() and then tries to trigger the tracepoint, which may or may not trigger depending on whether it is enabled or not: https://github.com/lttng/lttng-ust/blob/9261aeadea4674c3d68e05c2e8fcbcefa54feb56/src/lib/lttng-ust/tracef.c#L46. Therefore, the former avoids formatting the string if the tracepoint is not enabled.
Anyway, all of this is to say that we should just use lttng_ust_tracef()/tracef() even though it's just a test.
This should be tested on RHEL because it uses LTTng <=2.12.

Linux
Linux-aarch64
Windows
RHEL


Data Annotation

Call for Ideas
So you've loaded your data into CRViz and you've found some interesting pattern or feature of the data, but now you need a snazzy way to communicate this to outside users.  Maybe to people who aren't familiar with your data or even the underlying problem space your data exists in.  How do you go about doing that?  Great question! The short answer is, we don't really know.  Tell us how you'd like to show your data off.  If you are super technical and want to open a pull request for an implementation thats great.  Maybe you are a graphic designer and you can upload wireframes in this thread, that's awesome too.  If you just have an idea, describe it for us as best you can.  We are open to any and all input.

Closed by #415


error when updating from 1.2.1

Problem
This error pops up when updating from 1.2.1 to 1.3.0
Expected behavior
Should upate
Actual behavior
When updating, this error pops up:
Can't install ghcr.io/t0bst4r/matterbridge-home-assistant-addon/aarch64:1.3.0: 500 Server Error for http+docker://localhost/v1.45/images/create?tag=1.3.0&fromImage=ghcr.io%2Ft0bst4r%2Fmatterbridge-home-assistant-addon%2Faarch64&platform=linux%2Farm64: Internal Server Error ("manifest unknown")

got a new update not 1.3.2-61 with the same behavior
Can't install ghcr.io/t0bst4r/matterbridge-home-assistant-addon/aarch64:1.3.2-61: 500 Server Error for http+docker://localhost/v1.45/images/create?tag=1.3.2-61&fromImage=ghcr.io%2Ft0bst4r%2Fmatterbridge-home-assistant-addon%2Faarch64&platform=linux%2Farm64: Internal Server Error ("manifest unknown")

Oh wow, this was quick.
I am currently working on the release workflow, automating addon releases. sorry for that.
i'll write another message when this is done (probably in 10-30 minutes)

could you give it a try with 1.3.2-64 ?

could you give it a try with 1.3.2-64 ?

It worked for me.

NIce! I hope there will be no more problems in the future! 👍

Sorry bout this. I just went from1.2.1 to the new addon_a1b84aa7_matterbridge_1.3.2-64. Seemed to install and run well. Till... I looked at devices and saw none.  Sorry didnt track/copy yhem. Tried adding and removing devices from config but no devices ever show up in the matterbridge UI. Went back to 1.2.1 backup tar and seems all work nice again. Love this sofwate btw. Would hate to see it "broke" for long. Also it looked like the cpu meter in the addon was pegged while loading the new version. proxmox hassio full dell opti smff btw

@Ian-Zz
Let me just get your post right:

update to 1.3.2-64 was successful
After updating it does not show any devices
Then you rolled back to 1.2.1 and all the device were back

Is that correct so far?
Without any logs I cannot do anything to fix it.
Logs from the UI don’t help a lot, but the addon logs (from the addon details in HA) are helpful.
If you still face that issue, please create a new issue and paste the logs from the addon logs.

t0bst4r Yup. 64 did seem to update and start proper but just would never show any devices before or after a few restarts and reboots. I see a newer 65 already so I might try that and watch better and try to track any logs. Would that be in this neighborhood for more/better logging http://my-ip-blah-blah/config/logs?provider=a1b84aa7_matterbridge. Either way just happy to get my devices back after roll back. That was grand.

The crossed out lines in addon log are like this (maybe it helps):
[22:23:57.642] [Matterbridge] Failed to load plugin matterbridge-home-assistant: Error: ENOENT: no such file or directory, open '/app/node_modules/matterbridge-home-assistant/package.json'
[22:23:58.643] [Matterbridge] The plugin matterbridge-home-assistant is in error state.
[22:23:58.643] [Matterbridge] The bridge will not start until the problem is solved to prevent the controllers from deleting all registered devices.
[22:23:58.643] [Matterbridge] If you want to start the bridge disable the plugin in error state and restart.
[22:23:58.695] [Matterbridge] The plugin matterbridge-home-assistant is out of date. Current version: 1.2.1, Latest version: 1.3.3

i have missed to fix a bug in the addon, which i already fixed in the main project.
could you give it a try with 1.3.3-66 ?

Update... results from 65 were the same. Nearly pegged cpu/add on usage and no devices showing up.
Main log text I got....
#############################
[17:07:17.676] [Matterbridge] Created Matterbridge Plugin Directory: /root/Matterbridge
[17:07:17.681] [Matterbridge] Matterbridge version 1.3.4 mode  running on Linux 6.6.33-haos linux x64
[17:07:17.686] [Matterbridge] Plugin /usr/local/lib/node_modules/matterbridge-home-assistant/package.json already added to matterbridge
[17:07:18.739] [Matterbridge] Matterbridge version 1.3.4 mode bridge restart mode docker running on Linux 6.6.33-haos linux x64
[17:07:19.011] [Matterbridge] WebSocketServer is listening on ws://<IP_ADDRESS>:8284
[17:07:19.011] [Matterbridge] The frontend is listening on http://<IP_ADDRESS>:8283
[17:07:19.020] [Matterbridge] Loading plugin matterbridge-home-assistant type DynamicPlatform
[17:07:19.022] [Matterbridge] Failed to load plugin matterbridge-home-assistant: Error: ENOENT: no such file or directory, open '/app/node_modules/matterbridge-home-assistant/package.json'
[17:07:20.021] [Matterbridge] The plugin matterbridge-home-assistant is in error state.
[17:07:20.021] [Matterbridge] The bridge will not start until the problem is solved to prevent the controllers from deleting all registered devices.
[17:07:20.022] [Matterbridge] If you want to start the bridge disable the plugin in error state and restart.
[17:07:20.213] [Matterbridge] The plugin matterbridge-home-assistant is out of date. Current version: 1.2.1, Latest version: 1.3.3
I'll give 66 a try. But to be honest with 1.2.1 working for me I am plenty happy with that.
Thanks.

Yeah, i just fixed one thing in 66.

Great News. 67 works for me. After install cpu was pegged again. Didn't check much else. Just rebooted. See my devices and zero crossed out lines in the log. cpu at about a 4. Cool. Thanks.


5.12.0

@jcfr  You probably just want to make a new branch for this version.

assuming this project is abandoned.  Closing outdated PR that is now in conflict.

@jamesobutler I will let you assess if any of the work of @hjmjohnson is still relevant.
Site note: @jamesobutler and @hjmjohnson  to streamline future effort, I will both grant you write access to the repo


Azure Pipelines: Make build work

Pull Request (PR) description
Update the azure pipelines config to successfully build.
This Pull Request (PR) fixes the following issues

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

@johlju, I have a PR for another fix but it would be better to fix this first.

This was integration tests on two different windows OS version, I guess we can remove that if there are no point of testing on two OS versions.


Reviewable status: 6 of 8 files reviewed, 1 unresolved discussion (waiting on @Samathingamajig)

public/database/grade_distributions.db line 0 at r1 (raw file): 20 megabytes seems a bit large, is there no way for us to bring this down? cc @doprz

I added my full prod db but after talking to @sghsri we're going to limit it down to 2016-Present

After talking with the rest of the admins, we're going to update the way we handle the database and move all work to #163


[BUG] Broken docker install script

Broken external link (https://sdk.lunarg.com/sdk/download/<IP_ADDRESS>/linux/vulkansdk-linux-x86_64-<IP_ADDRESS>.run) results in https://github.com/apache/incubator-tvm/blob/master/docker/install/ubuntu_install_vulkan.sh failing to execute successfully.
Note: the 'run' script downloads successfully, however the result is a file containing the text 'Not Found'

We should update the script to points to new version of vulkan drivers then

https://github.com/apache/incubator-tvm/pull/5566


Class name error when crawling posts

(This issue is related to #78)
Most of the times, when one tries to crawl the post information from an user, the logging provides the following output:
Message: no such element: Unable to locate element: {"method":"class name","selector":"Xl2Pu"
If it helps, I am using MacOS with chromedriver.
Thanks for your time
Daniyal

Well, as a matter of fact, it seems like the whole thing doesn't really work anymore. Maybe Instagram did an update. I'm having a look at it now.


Rewind the keyFileStream before each read

When using either keyFile or keyFileStream to provide credentials to the ServiceBuilder, if the user's credentials expire between requests, an error will occur when trying to load credentials from the file stream, because the pointer is at the end of the stream.
Here's the output from the test prior to calling $keyFileStream->rewind() within the ServiceBuilder:
PHPUnit 5.1.3 by Sebastian Bergmann and contributors.

.....................EE.......................................... 65 / 96 ( 67%)
...............................                                   96 / 96 (100%)

Time: 250 ms, Memory: 16.77Mb

There were 2 errors:

1) Google\Cloud\Tests\RequestWrapperTest::testCredentialsFromKeyFileStreamCanBeReadMultipleTimes with data set #0 (array(Closure Object (...), Closure Object (...), '{"type":"authorized_user","cl..."abc"}'))
array_key_exists() expects parameter 2 to be array, null given

/Users/mike/Code/mcrumm/gcloud-php/vendor/google/auth/src/CredentialsLoader.php:118
/Users/mike/Code/mcrumm/gcloud-php/src/RequestWrapper.php:177
/Users/mike/Code/mcrumm/gcloud-php/tests/RequestWrapperTest.php:115

2) Google\Cloud\Tests\RequestWrapperTest::testCredentialsFromKeyFileStreamCanBeReadMultipleTimes with data set #1 (array(Closure Object (...), Closure Object (...), '/Users/mike/Code/mcrumm/gclou...e.json'))
array_key_exists() expects parameter 2 to be array, null given

/Users/mike/Code/mcrumm/gcloud-php/vendor/google/auth/src/CredentialsLoader.php:118
/Users/mike/Code/mcrumm/gcloud-php/src/RequestWrapper.php:177
/Users/mike/Code/mcrumm/gcloud-php/tests/RequestWrapperTest.php:115

FAILURES!
Tests: 96, Assertions: 115, Errors: 2.

Thanks for this @mcrumm, Looks good to me.


Feat:Missing Hover on Social Icons In Transaction page

Describe the feature
Missing Hover Effect on Social Icons In Transaction page
Let me fix it as a GSSCO24 conributor
Add ScreenShots
check tis video once:
https://github.com/Anushkabh/krishiconnect/assets/108344062/4011f029-c579-4c74-8025-fee61abdc066
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@SumithThota please ensure the same uniformity is maintained across the website

@RitiChandak, Yes I will maintain the same uniformity


Update: Serraniel.DiscordMediaLoader version <IP_ADDRESS>

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


Email previews failing to load with Rails 7

We need a new release for this gem to work with Rails 7 that includes this https://github.com/glebm/rails_email_preview/commit/aac54191e1590819dc1c91e8eaf6a341a36b91f6

I'll publish a new release over the next few days. Can you check if HEAD works?

Released v2.2.3 and added Rails 7 to CI


Adding depth option to the texture of guiOffscreenCanvas

Related to: http://forums.torque3d.org/viewtopic.php?f=10&p=6964#p6964
These small changes fix the rendering in the named texture of a guiOffscreenCanvas with 3d views.
Without this change, the objects in the 3d view are copied as they're created and that causes depth issues (objects behind being rendered in front).
Creating the gui with the field "useDepth" as true enables the fix.
It's off by default so guiOffscreenCanvas that don't use 3d views or don't need the texture part won't get the extra workload of the fix.
-Example of its use-
Add these functions to a .cs script in a "Full" project and exec it:
`
   //createRearView(0);
   //createRearView(1);
   function createRearView(%depthtest)
   {
      if(!isObject(RearViewUpdater))
      {
         %tickObj = new ScriptTickObject(RearViewUpdater);
         %tickObj.setProcessTicks(true);
         MissionCleanup.add(%tickObj);

        %guiOffscreen = new GuiOffscreenCanvas() {
           targetSize = "300 300";
           targetFormat = "GFXFormatR8G8B8A8";
           targetName = "RearViewTexture";
           dynamicTarget = "1";
           useDepth = %depthtest; //this one to enable the depth fix
           numFences = "0";
           displayWindow = "1";
           position = "0 0";
           extent = "300 300";
           visible = "1";
           active = "1";

           new GameTSCtrl() {
              cameraZRot = "180";
              position = "0 0";
              extent = "300 300";
           };
        };
        %guiOffscreen.cursorOff();

        %tickObj.guiOffCan = %guiOffscreen;

        %playGuiRearWindow = new GuiBitmapCtrl() {
           position = "100 100";
           extent = "150 150";
        };
        PlayGui.add(%playGuiRearWindow);

        %tickObj.miniWindow = %playGuiRearWindow;
     }
  }

  function RearViewUpdater::onInterpolateTick(%this, %delta)
  {
     (%this.miniWindow).setNamedTexture("RearViewTexture");
  }

  function RearViewUpdater::onRemove(%this)
  {
     (%this.miniWindow).delete();
     (%this.guiOffCan).delete();
  }

`
After that, start the desert level. If you add a few TSStatic and half-bury them in the terrain the fix will be shown better.
Now, use in the console:
   createRearView(0);
This will create a guiOffscreenCanvas with the fix disabled as its useDepth field is zero.
You'll see a small window showing the rear view of the soldier. This window has depth errors like objects not being correctly covered by the terrain.
Delete the window and the guiOffscreenCanvas with:
   RearViewUpdater.delete();
Finally use:
   createRearView(1);
to create a guiOffscreenCanvas with the fix enabled (useDepth field is true).
Now the window should show the objects being correctly rendered.

Nicely done. Thanks for the PR.

Just perfect. Thanks (:


Convinient methods for margins and paddings

Makes sense! Why I didn't thought about that? 🙈
Do you think it is worth renaming params from t -> top, b -> bottom and so on?

Yeah, I believe meaningful names would be better to have.


Update request_handlers.h sendState() is not declared

Move MQTT callback / connection handler before WS request handlers because otherwise sendState() is not declared
Can't create Issues, but tested your new Code.
HA updates now, when the color is changed at the McLightning site.
Will also look closer to the code the next days.

request_handlers.h:450: error: 'sendState' was not declared in this scope

Sorry just now saw this PR. Have made appropriate modifications. Thanks!


-1 returns as UINT_MAX

I'm running node-odbc talking to a MSSQL server on 2008R2 using FreeTDS version 7.2
When I get a value of -1 back in a result set it is mapping to 4 294 967 295. Coincidentally (not) that is UINT_MAX as per https://msdn.microsoft.com/en-gb/library/296az74e.aspx.
The SQL field is a simple int field so why is it being converted to a uint here? I can't see anything odd looking in odbc.cpp so I'm guessing this is a FreeTDS issue.

This is definitely something in node-odbc. I'm going to try to track down the version in which it showed up.

This is fixed in 53d4a235 which was released to npm in v1.1.6. Give that version a shot and see if fixes your issue while not creating others. :)
This was happening on Sqlite, FreeTDS and the MSSQL Native Linux driver. But it was not happening on MySQL. I think the issue had to do with passing a long value to NanNew<Number>(value). I changed it to int32_t value and NanNew<Integer>(value).
I think we tried this before but Nan wouldn't allow returning that Integer type. That appears to be fixed now.
Please let me know if this works out for you so we can close the issue.

Sorry it took so long, I've managed to retest this now and can confirm it's working (at least in my very specific case).
Thanks for the help!
Closed


Merge webxr-2019 branch into master

@jsantell: While it's not 100% complete the code in the webxr-2019 branch is relatively functional and can run a majority of the code written against the current WebXR spec, the VR portion of which we no longer expect to break backwards compatibility with.
Given that the master branch now reflects a version of the spec that will never be shipped, it's currently pretty awkward to tell people how to get to the polyfill for testing. As such I think it would be appropriate to merge the webxr-2019 branch into master relatively soon, and continue development there. What, if anything, would you like to see happen prior to that merge?

I think you've hit the limit of what can be fixed before merging back to master.  Merge it in and lets just start using it for everything and see what breaks!

If it's working with most of the examples, that sounds great; let's get it merged, and start filing issues we find -- tests are probably the biggest one!

Poof! Done!


changing the character case of a file does not work with git on OS X

To reproduce:

change the character case of a git controlled file in VS Code for OS X by renaming

Observe: the file is correctly shown in VS Code's explorer but it doesn't show up in the git viewlet

modify the file

Observe: now the file shows up in git but with the original character casing

commit the change

Observe: the file change doesn't show up in the git history
Workaround: I had to switch to VS Code on linux to successfully change the character case of a file.

If the same steps are done in the command line, the same results will follow, so Code isn't doing anything wrong.
The git config core.ignorecase seems to help you in these situations.


Date data

When I export data that contains a date, it gets converted to an integer.
get-adcomputer Somecomputer -properties lastlogondate |export-excel "Adcomputer.xlsx"
LastLogonDate	Name	ObjectClass
42114.61478	Somecomputer	computer

Dates are now formatted


Fixes 4091: add template docs

Summary

Adds docs for content templates
Updates package dependency graph
Adds a few entries to the code layout table

Testing steps

Point out anything you see that's wrong, missing, or could be phrased better

https://issues.redhat.com/browse/HMS-4091

/retest


Obsidian theme breaks lockscreen images from Minimal Lock Screen

The obsidian theme makes the background on the plugin "Minimal Lock Screen" only a single color, even when using a picture. Disabling obsidian fixes the issue so this has to be obsidian doing some skinning that overwrites what minimal lock screen does. An option to disable skinning on the lock screen would be very appreciated

I managed to fix this issue by removing the !important tag on the lockscreen segment in shared.css might want to add a toggle to turn that on or off for other people using the minimal lock screen plugin.

Obsidian is up to Ver 3.0 and this is still an issue... and theres a listed fix right here.

Obsidian is up to Ver 3.0 and this is still an issue... and theres a listed fix right here.

i did make a fork with an easy workaround but emerald does not seem to want to use that fix even though it is pretty minimal and fixes this issue. i am currently only using my fork on my steam deck to get around this problem. see #53

Appreciate the update, Emerald :) Hope the exams go/went well.

This is fixed by https://github.com/EMERALD0874/Steam-Deck-Themes/commit/4f9d5060e0707f2a26f6537552ddaabf55cba8cf. If you continue to have issues, make sure the Minimal Lock Screen theme is enabled after Obsidian. If you are still having issues, please reach out to their developers and ask them to add an !important flag to the background so it overrides Obsidian.

issue persists in most recent version

Disable both themes. Enable Obsidian first (lower precedence) then Minimal Lock Screen (higher precedence). If this doesn't fix your issue, please reach out to the developers of Minimal Lock Screen and ask them to consider adding !important given it only targets the lock screen and should override other more general themes.
I tested the above fix myself and it worked on my end.


mediapipe error

OS Platform and Distribution
windows 10
Compiler version
No response
Programming Language and version
python 3.10.11
Installed using virtualenv? pip? Conda?(if python)
pip
MediaPipe version
0.8.11
Bazel version
No response
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
A bug happened!
Complete Logs
import cv2
import mediapipe as mp
import time

cap = cv2.VideoCapture(0)

mpHands = mp.solutions.hands
hands = mpHands.Hands()
mpDraw = mp.solutions.drawing_utils

pTime = 0
cTime = 0

while True:
    success, img = cap.read()
    imgRGB = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)
    results = hands.process(imgRGB)
    # print(results.multi_hand_landmarks)

    if results.multi_hand_landmarks:
        for handLms in results.multi_hand_landmarks:
            for id, lm in enumerate(handLms.landmark):
                # print(id, lm)
                h, w, c = img.shape
                cx, cy = int(lm.x * w), int(lm.y * h)
                print(id, cx, cy)
                # if id == 4:
                cv2.circle(img, (cx, cy), 15, (255, 0, 255), cv2.FILLED)

            mpDraw.draw_landmarks(img, handLms, mpHands.HAND_CONNECTIONS)

    cTime = time.time()
    fps = 1 / (cTime - pTime)
    pTime = cTime

    cv2.putText(img, str(int(fps)), (10, 70), cv2.FONT_HERSHEY_PLAIN, 3,
                (255, 0, 255), 3)

    cv2.imshow("Image", img)
    cv2.waitKey(1)

error
File "c:\Users\성준\Desktop\project\a.py", line 8, in <module>
    hands = mpHands.Hands()
  File "C:\Users\성준\AppData\Roaming\Python\Python310\site-packages\mediapipe\python\solutions\hands.py", line 114, in __init__
    super().__init__(
  File "C:\Users\성준\AppData\Roaming\Python\Python310\site-packages\mediapipe\python\solution_base.py", line 265, in __init__
    validated_graph.initialize(
FileNotFoundError: The path does not exist.

hands.py line 114
super().__init__(
        binary_graph_path=_BINARYPB_FILE_PATH,
        side_inputs={
            'model_complexity': model_complexity,
            'num_hands': max_num_hands,
            'use_prev_landmarks': not static_image_mode,
        },
        calculator_params={
            'palmdetectioncpu__TensorsToDetectionsCalculator.min_score_thresh':
                min_detection_confidence,
            'handlandmarkcpu__ThresholdingCalculator.threshold':
                min_tracking_confidence,
        },
        outputs=[
            'multi_hand_landmarks', 'multi_hand_world_landmarks',
            'multi_handedness'
        ])

solution_base.py line 265
# MediaPipe package root path
    root_path = os.sep.join(os.path.abspath(__file__).split(os.sep)[:-3])
    resource_util.set_resource_dir(root_path)
    validated_graph = validated_graph_config.ValidatedGraphConfig()
    if binary_graph_path:
      validated_graph.initialize(
          binary_graph_path=os.path.join(root_path, binary_graph_path))
    else:
      validated_graph.initialize(graph_config=graph_config)

Hi @junjunjunman,
We are closing this issue because it is the same as issue #5150. Please check the latest issue you raised for updates and a resolution.
Thank you!!


[Flake] Spanner CreateDatabase takes too long in database_integration_test

GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/4342840d-3d82-439a-bcc6-1ad58425e934;tab=detail?project=cloud-cpp-testing-resources
Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/7904f0f44ade543207b01eed1d130ce27eaaf58a/fedora-34-integration-daily/log-4342840d-3d82-439a-bcc6-1ad58425e934.txt
The errors look like:
[----------] 22 tests from DataTypeIntegrationTest
Creating database and table .......................................................................................................................TIMEOUT
google/cloud/spanner/testing/database_integration_test.cc:132: Failure
Failed

... which points to this code: https://github.com/googleapis/google-cloud-cpp/blob/225f0663d17d553d4e68d5f523483e8251ea8bf2/google/cloud/spanner/testing/database_integration_test.cc#L121-L133
These are the affected tests:
//google/cloud/spanner/integration_tests:client_integration_test         FAILED in 224.5s
//google/cloud/spanner/integration_tests:data_types_integration_test     FAILED in 225.6s
//google/cloud/spanner/integration_tests:rpc_failure_threshold_integration_test FAILED in 225.6s
//google/cloud/spanner/integration_tests:session_pool_integration_test   FAILED in 221.1s

https://source.cloud.google.com/results/invocations/4d4d6bd5-c625-45d0-9a67-12e2f94e1dce on macOS.

In this last case we saw ...
2021-11-01T15:13:51.849045000Z [DEBUG] <0x10cd09dc0> AsyncCreateDatabase(1) <<
2021-11-01T15:19:37.307110000Z [DEBUG] <0x700006971000> AsyncCreateDatabase(1) >>

for an elapsed time just to obtain the long-running operation of about 5m45s, so the 5m app-level poll timeout had already expired.
In the previous (non-macOS) cases we saw ...
2021-10-29T07:11:27.707399389Z [DEBUG] <139821468375104> AsyncCreateDatabase(1) <<
2021-10-29T07:17:23.584736387Z [DEBUG] <139821442754112> AsyncCreateDatabase(1) >>

and
2021-10-22T07:19:03.167386218Z [DEBUG] <140261828769856> AsyncCreateDatabase(1) <<
2021-10-22T07:21:23.205296345Z [DEBUG] <140261803148864> AsyncCreateDatabase(1) >>

for elapsed times of about 5m54s and 2m20s respectively (the latter being when the app-level poll timeout was 2m).
I wonder how long we would have needed to poll those long-running operations in order to see the final result?  The subsequent DropDatabase() calls all succeeded in 5m12s, 4m58s, and 1m45s respectively.  Perhaps we were just seeing general service-latency problems at those moments.
In any case, it seems there is an argument for bumping the app-level poll timeout once more.  Remember that these are tests that will timeout by themselves, and that the default LRO polling limit is 30m, so going from 5m to 10m is reasonable.

The 600s timeout seems to be holding, so I'll declare this closed for now.


Add comments about deploy keys

Clarifies their purpose, why there is DOCUMENTER_KEY and COMPATHELPER_PRIV, and link to docs
This workflow is linked to from the README/docs as an example so these comments should help users.
xref https://julialang.slack.com/archives/C6A044SQH/p1734169106738789

I think this is uncontroversial so I'll add it to the merge queue, but if there is post-merge feedback I'll gladly make a new PR to address it

I was going to ask if some version of this content should be added to the README. But as you point out, we already link to this YAML file from the README, so it may be sufficient to have the comments in the YAML file.
@ericphanson Should we also update PkgTemplates.jl so that the templated CompatHelper.yml file that PkgTemplates creates (in new packages) contains these same comments?

that would be good, but they probably can't be the exact same since whether or not you have a documenter key depends on how you configure the template. So I think the comments would either need to be slightly more generic / not always applicable, or templated.


Bump gem version to 17.18.1

Includes:

Changes content item to have symbolic keys #1002

Does this need a line in the Changelog?

Does this need a line in the Changelog?

I decided against it as this is a bug fix and does not provide any usefulness in change notes.

@DilwoarH rebase this and pushed. Hope you don't mind. If you're happy with it please merge.

Closed in favour of #1006


TruncatedNormal bound incorrectly

TensorflowSharp has a signature for TruncatedNormal unlike https://www.tensorflow.org/api_docs/python/tf/truncated_normal
It doesn't take the shape as a tensor, and there is no way to specify a mean and std dev (very important for this distribution).
Its signature should be more like RandomNormal.

Not sure this is true, at least not in r1.5:
def truncated_normal(shape,
                     mean=0.0,
                     stddev=1.0,
                     dtype=dtypes.float32,
                     seed=None,
                     name=None):
  """Outputs random values from a truncated normal distribution.
  The generated values follow a normal distribution with specified mean and
  standard deviation, except that values whose magnitude is more than 2 standard
  deviations from the mean are dropped and re-picked.
  Args:
    shape: A 1-D integer Tensor or Python array. The shape of the output tensor.
    mean: A 0-D Tensor or Python value of type `dtype`. The mean of the
      truncated normal distribution.
    stddev: A 0-D Tensor or Python value of type `dtype`. The standard deviation
      of the normal distribution, before truncation.
    dtype: The type of the output.
    seed: A Python integer. Used to create a random seed for the distribution.
      See
      @{tf.set_random_seed}
      for behavior.
    name: A name for the operation (optional).
  Returns:
    A tensor of the specified shape filled with random truncated normal values.
  """

  with ops.name_scope(name, "truncated_normal", [shape, mean, stddev]) as name:
    shape_tensor = _ShapeTensor(shape)
    mean_tensor = ops.convert_to_tensor(mean, dtype=dtype, name="mean")
    stddev_tensor = ops.convert_to_tensor(stddev, dtype=dtype, name="stddev")
    seed1, seed2 = random_seed.get_seed(seed)
    rnd = gen_random_ops._truncated_normal(
        shape_tensor, dtype, seed=seed1, seed2=seed2)
    mul = rnd * stddev_tensor
    value = math_ops.add(mul, mean_tensor, name=name)
    return value

from https://github.com/tensorflow/tensorflow/blob/r1.5/tensorflow/python/ops/random_ops.py so basically it calls:
    rnd = gen_random_ops._truncated_normal(
        shape_tensor, dtype, seed=seed1, seed2=seed2)
    mul = rnd * stddev_tensor
    value = math_ops.add(mul, mean_tensor, name=name)

which would be equivalent to something like this in C#:
            const float mean = 0.0f;
            const float stddev = 0.1f;
            TFOutput shape_output = g.Const(shape.AsTensor());
            TFOutput rnd = g.TruncatedNormal(shape_output, TFDataType.Float);
            TFTensor mean_tensor = new TFTensor(mean);
            TFTensor stddev_tensor = new TFTensor(stddev);
            TFOutput mean_output = g.Const(mean_tensor);
            TFOutput stddev_output = g.Const(stddev_tensor);
            TFOutput mul = g.Mul(rnd, stddev_output);
            TFOutput value = g.Add(mul, mean_output);
            TFOutput initial = value;


ci: build GCC 14, build nowallet depends and source with it, stage built packages in /opt, allowlist LLVM libc++

Motivation
This PR is a spiritual continuation of dash#5375. Unlike upstream, Dash uses a development image for CI and therefore, is limited by the packages provided by the base distro (in our case, Ubuntu 22.04 jammy) unless additional efforts are placed to make those packages available, those efforts were expended for Clang and in this PR, it is being expanded to GCC to be able to catch issues like the ones resolved in dash#5064 within CI itself.
Additional Information

Depends on https://github.com/dashpay/dash/pull/6400
Dependency for https://github.com/dashpay/dash/pull/6389
As of develop (a8e2316d6f9c6726a498bcae2c5c5d7354769511), packages built by the container are stored in /tmp, which is inadvisable as it is the same directory used to store functional test runs and it's not too difficult to delete /tmp's contents to save space in a long running develop container and then realize that both shellcheck and cppcheck are stored there and now you have to ditch the container you're working in and restart it.

To remedy this, packages are now built and stored in /opt in accordance with the FHS (source). /usr/local was a contender but it's pre-populated, meanwhile ls /opt would give you a very quick picture of what's built for the container.
/tmp will not be entirely empty because pypa/pip#10753 results in residual .pem files leaking into /tmp and pyenv stores its build log there and keeping it around has some debug value.

Using LD_LIBRARY_PATH to point to our compiled GCC's library files (and extending that to LLVM's library files) are acceptable and will not interfere with executing binaries built using the distro's packaged compiler as it will eventually search default paths and find the libraries shipped with the distro (source).

depends built using GCC 11.4 (distro's GCC) can be used to build Dash Core using GCC 14.2 (compiled GCC) but the reverse doesn't hold true.

Breaking Changes
None expected.
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas (note: N/A)
[x] I have added or updated relevant unit/integration/functional/e2e tests (note: N/A)
[x] I have made corresponding changes to the documentation (note: N/A)
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

GitHub Actions on 62d4636 works as expected on my fork, see https://github.com/kwvg/dash/actions/runs/11764281671/job/32769805675#step:6:1

GitHub Actions run for 3263879a874e96f43bcf9b9116287f2ee25c4cc6, https://github.com/kwvg/dash/actions/runs/11949630923.


Give warning if something is returned from thunk

Hi. I am new to contributing to open source and I am really. I work on #3.
1 . I checked if something either than undefined was returns for invoking the thunk and printed a
warning as request
2.  One test was added and function was added.
Fixes #3

See #16

Thanks a lot @Gregjarvez! Left a few comments, but looking good :)

Released as part of 0.1.0


Allow authentication with LDAP in Pachyderm

Currently the only way to authenticate in Pachyderm is using a GitHub account, as Pachyderm has only implemented OAuth integration with GitHub. However, many users have internal LDAP systems and accounts configured, and we'd like Pachyderm to work with those

Not sure if any of these are requirements/hard reasons to not proceed this way, but a few considerations we should take into account:

Dex's SAML connector doesn't support refresh tokens. Without that I think either people would have to either constantly re-login, or else we cache auth results locally, but that would mean we wouldn't reflect changes from the SAML server. According to their docs, this is a fundamental issue with the way dex works.
it appears dex doesn't have support for RADIUS, kerberos, or CAS which afaiu are all pretty widely used. Not sure if there's any fundamental reason it couldn't interop with those, but it's not super encouraging that the radius issue has been open for a month with no comment (and the other don't appear to have ever been mentioned)
dex provides authentication, but not authorization. At the moment, we hold all authz info internally, but if we did want to support using LDAP-based authz, or ABAC/XACML*, it seems having dex as an indirection layer may complicate doing so.

*: This seems likely: afaiu ABAC was specifically designed with ("big") data security in mind/is supported by hadoop, and it's usage over RBAC is now officially recommended by NIST/mandated for federal US government organizations

These are all really good concerns to keep on our radar. That said, Pachyderm doesn't support any kind of refresh flow with OAuth (once a user has authenticated, we discard their access token and then they authenticate Pachyderm token), so the lack of a SAML refresh flow isn't a regression, and if dex saves us time I think it would be a useful stepping stone to a more comprehensive solution. We also don't support OIDC, so the lack of support for OIDC groups is also not a loss.
My perspective is that I haven't seen many SAML implementations in Go (there is https://github.com/crewjam/saml, but it seems to be maintained by one person, and it doesn't seem to support ID-provider-initiated auth), so improving on what we get from dex seems like a large project to me, and I'm eager to postpone it :-)


Published the SDK to crates.io

Fixed all examples
Renamed a number of vars to use Valkey* naming convention vs Redis*
Will be working on remaining ones in separate PRs but wanted to keep the scope of changes manageable.
Some these changes will be backwards incompatible but since we are very early in the project it's a low impact to users.

@madolson - let me know if you have feedback before I publish it to crates.io with version 0.1.0


Fix and optimize handling of vectorized memory accesses

Description
For operators, which performance is limited by global memory bandwidth, it is important to issue the widest possible loads, as it ensures that the bandwidth is fully utilized.
Currently in MXNet we use vectorized loads and stores only for half_t type for a few operators (some elementwise binary operators and elementwise_sum). Unfortunately, the way it was done makes some assumptions about MXNet's NDArrays which do not hold true for all cases.

Failure 1:

import mxnet as mx
ctx=mx.gpu()
a = mx.nd.array([1,2,3,4], dtype='float16', ctx=ctx)
b = mx.nd.array([1,2,3,4], dtype='float16', ctx=ctx)

c = a[1:3]
d = b[1:3]
mx.nd.elemwise_add(c, d, out=c)

Results in error:
Check failed: e == cudaSuccess: CUDA: misaligned address

Failure 2:

import mxnet as mx
ctx=mx.gpu()
a = mx.nd.array([1,2,3,4], dtype='float16', ctx=ctx)
b = mx.nd.array([1,2,3,4], dtype='float16', ctx=ctx)

print(a)
c = a[0:3]
d = b[0:3]
mx.nd.elemwise_add(c, d, out=c)
mx.nd.waitall()
print(c)
print(a)

gives:
[1. 2. 3. 4.]
<NDArray 4 @gpu(0)>

[2. 4. 6.]
<NDArray 3 @gpu(0)>

[2. 4. 6. 8.]
<NDArray 4 @gpu(0)>

which is a silent data corruption (the last element of a should not have been changed).
It was not noticed before because a + b for NDArrays launches the broadcast_add instead of elemwise_add (and is not vectorized), whereas in the symbolic execution slices give new allocations, which do not exhibit those issues.
This PR:

fixes those issues
introduces helpers for handling vectorization (for all types, not only half_t)
increases performance of vectorized kernels
introduces vectorization for all binary/unary/binary with scalar ops
(WIP) introduces vectorization for broadcast ops

@eric-haibin-lin @sxjscience @haojin2
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
[ ] Code is well-documented:
For new C++ functions in header files, their functionalities and arguments are documented.
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Properly handle vectorized loads and stores in elementwise kernels
[x] Handle vectorized loads and stores in elementwise broadcast kernels

@haojin2 I'm hitting again the OoM on Windows build, like you did before. I started looking at the numpy versions of those functions and I see that you have way more templates there (some of which are actually not compiled on Windows) and I started thinking that we should probably just switch to runtime compilation of those kernels - there is just too many variants here. What do you think about this (also @eric-haibin-lin @szha @leezu  for comments)?
Also - I don't see elementwise ops in the numpy python package, just broadcast ops - this is pretty bad because knowledge that the shapes are the same is pretty important in optimizations - for example the pointwise fusion would not really work for such operators.

For OoM, could updating the windows toolchain help https://github.com/apache/incubator-mxnet/pull/17808 ?

The windows CI has been updated w/ 64bit toolchain so this PR should be unblocked now

@leezu Have you seen such error in the edge CI before?
[2020-04-17T16:15:43.821Z] CMake Error at /usr/local/lib/python3.6/dist-packages/cmake/data/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):

[2020-04-17T16:15:43.821Z]   Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)

[2020-04-17T16:15:43.821Z] Call Stack (most recent call first):

[2020-04-17T16:15:43.821Z]   /usr/local/lib/python3.6/dist-packages/cmake/data/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445 (_FPHSA_FAILURE_MESSAGE)

[2020-04-17T16:15:43.821Z]   /usr/local/lib/python3.6/dist-packages/cmake/data/share/cmake-3.17/Modules/FindOpenMP.cmake:529 (find_package_handle_standard_args)

[2020-04-17T16:15:43.821Z]   CMakeLists.txt:404 (find_package)

[2020-04-17T16:15:43.821Z]

[2020-04-17T16:15:43.821Z]

[2020-04-17T16:15:43.821Z] -- Configuring incomplete, errors occurred!```

It's because you modify all C compile flags with -mcmodel=medium. This setting is architecture dependent and while a medium memory model exists on ARMv8, gcc does not implement it.
I suspect cmake will test compile a file to check if openmp is working, which fails with gcc saying "Sorry but -mcmodel=medium isn't implemented yet"

@leezu Makes sense. And the mcmodel=medium did not even fix the failure with the CMake static build in unix-gpu :-(. Do you have any idea why CMake static build fails, while normal build does not?

The reason for mcmodel=medium not fixing the problem is that it only affects the code built by us. But we rely on the C standard library, which has lib/../lib64/crti.o which is not built for medium memory model.

Ok, considering code freeze date of 1.7 and me really wanting to include vectorization support there,I decided to limit this PR to just elementwise ops and leave the broadcast ops for the next PR, not included in 1.7.
That should enable passing the CI, while still keeping at least some of the improvement.

@ptrendx the built on master branch (git clean -ffxd; python ci/build.py --platform publish.centos7_gpu_cu101 /work/runtime_functions.sh build_static_python_cu101_cmake --cache-intermediate will produce:
-rw-r--r--  1 ubuntu ubuntu 2.4G Apr 17 18:46 libmxnet.a
-rwxr-xr-x  1 ubuntu ubuntu 2.0G Apr 17 18:46 libmxnet.so

On the other hand, with your PR
-rw-r--r--  1 ubuntu ubuntu 2.8G Apr 17 19:12 libmxnet.a

So there is a significant binary size increase.
I have some ideas for reducing the size of .so, but the most immediate (and easy to backport) solution is to reduce the number of architectures in https://github.com/apache/incubator-mxnet/tree/master/config/distribution

I think I will settle with the elementwise ops for now and instead of trying to squeeze stuff into the already huge binary, think about ways of reducing that size for longer term.
Also, this current solution does not really touch numpy ops too much, so that would need to be tackled as well (and judging from the current code, will introduce much bigger bloat), so the need for real solution is big.

@ptrendx Sorry to ask but are these optimizations also applicable to all the numpy operators?

@sxjscience Frankly I did not look in to much detail in the numpy ops but from what I saw they use only partially the previous implementation, as they need to deal with potentially different types etc, which makes them use special kernels. Also, they do seem to be mostly broadcasting ops (which scares me a little in the context of implementing fusions for example, as those would not qualify). So currently I would not expect it impacting numpy ops, but would like to work on extending this work to be able to unify and optimize both numpy and non-numpy versions.

@ptrendx Thanks!

@mxnet-bot run ci [windows-cpu]


Implemented JSON output processor

Implemented JSON Output processor
Refactored output processors to be in the core module
Refactored mojos to add more feature to standalone mode and put more of the shared logic in the abstract class.

@pvdbosch could you please review?
Example output:
{
  "violationCount" : 10,
  "ignoredViolationCount" : 0,
  "groupedBy" : "RULE",
  "violations" : [ {
    "group" : "[cod-design]",
    "occurrences" : 1,
    "violations" : [ {
      "ruleName" : "[cod-design]",
      "description" : "New code types SHOULD be represented as string values in lowerCamelCase.",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "logo.yaml",
      "lineNumber" : 15,
      "pointer" : "/components/schemas/LogoMetaData/properties/mediaType"
    } ]
  }, {
    "group" : "[err-problem]",
    "occurrences" : 1,
    "violations" : [ {
      "ruleName" : "[err-problem]",
      "description" : "Each error response of each operation SHOULD have a media type \"application/problem+json\"",
      "message" : "[Operation: GET /health]",
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 518,
      "pointer" : "/paths/health/get/responses/500"
    } ]
  }, {
    "group" : "[evo-object]",
    "occurrences" : 5,
    "violations" : [ {
      "ruleName" : "[evo-object]",
      "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 156,
      "pointer" : "/paths/organizations/post/requestBody/content/application/json"
    }, {
      "ruleName" : "[evo-object]",
      "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 187,
      "pointer" : "/paths/organizations/{enterpriseNumber}/get/responses/200/content/application/json"
    }, {
      "ruleName" : "[evo-object]",
      "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 223,
      "pointer" : "/paths/organizations/{enterpriseNumber}/put/requestBody/content/application/json"
    }, {
      "ruleName" : "[evo-object]",
      "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 232,
      "pointer" : "/paths/organizations/{enterpriseNumber}/put/responses/200/content/application/json"
    }, {
      "ruleName" : "[evo-object]",
      "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 262,
      "pointer" : "/paths/organizations/{enterpriseNumber}/patch/responses/200/content/application/json"
    } ]
  }, {
    "group" : "[hdr-case]",
    "occurrences" : 1,
    "violations" : [ {
      "ruleName" : "[hdr-case]",
      "description" : "By convention, HTTP headers SHOULD use Kebab-Case with uppercase for readability and consistency. ",
      "message" : null,
      "type" : "MANDATORY",
      "fileName" : "openapi.yaml",
      "lineNumber" : 365,
      "pointer" : "/paths/logos/{id}/get/parameters/1"
    } ]
  }, {
    "group" : "[jsn-naming]",
    "occurrences" : 1,
    "violations" : [ {
      "ruleName" : "[jsn-naming]",
      "description" : "All JSON property names SHOULD be written in lowerCamelCase notation.",
      "message" : "[propertyName: Image]",
      "type" : "MANDATORY",
      "fileName" : "logo.yaml",
      "lineNumber" : 24,
      "pointer" : "/components/schemas/Logo"
    } ]
  }, {
    "group" : "[oas-exampl]",
    "occurrences" : 1,
    "violations" : [ {
      "ruleName" : "[oas-exampl]",
      "description" : "Example does not validate against schema",
      "message" : "employerId: Type expected 'integer', found 'string'. In Schema: employer.yaml#/components/schemas/Employer : <belgif/employment/identifier/v1/employment-identifier-v1.yaml#/components/schemas/EmployerId>.<type>\nemployerId: Value '164893015' does not match format 'int64'. In Schema: employer.yaml#/components/schemas/Employer : <belgif/employment/identifier/v1/employment-identifier-v1.yaml#/components/schemas/EmployerId>.<format>",
      "type" : "MANDATORY",
      "fileName" : "employer.yaml",
      "lineNumber" : 40,
      "pointer" : "/components/schemas/Employer/example"
    } ]
  } ]
}

@jpraet and @pvdbosch , could you provide feedback on the output format / structure?

Below a proposed modified output JSON format, more compliant with the REST guide:

remove properties with null value
lowerCamelCase for codes ("mandatory", "rule" in groupedBy)
ruleName => ruleId
"total" when counting number of entries
use group key as a property name in violations object
rename second "violations" to "occurrences"

{
  "totalViolations": 10,
  "totalIgnoredViolations" : 0,
  "groupedBy" : "rule",
  "violations" : {
    "[cod-design]": {
      "total": 1,
      "occurrences" : [ {
        "ruleId" : "[cod-design]",
        "description" : "New code types SHOULD be represented as string values in lowerCamelCase.",
        "type" : "mandatory",
        "fileName" : "logo.yaml",
        "lineNumber" : 15,
        "pointer" : "/components/schemas/LogoMetaData/properties/mediaType"
      } ]
    },
    "[evo-object]": {
      "total" : 5,
      "occurrences" : [ {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 156,
        "pointer" : "/paths/organizations/post/requestBody/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 187,
        "pointer" : "/paths/organizations/{enterpriseNumber}/get/responses/200/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 223,
        "pointer" : "/paths/organizations/{enterpriseNumber}/put/requestBody/content/application/json"
      }
      ]
    }
  }
}

Implemented feedback.
Example:
{
  "totalViolations" : 10,
  "totalIgnoredViolations" : 0,
  "groupedBy" : "rule",
  "violations" : {
    "[cod-design]" : {
      "total" : 1,
      "occurrences" : [ {
        "ruleId" : "[cod-design]",
        "description" : "New code types SHOULD be represented as string values in lowerCamelCase.",
        "type" : "mandatory",
        "fileName" : "logo.yaml",
        "lineNumber" : 15,
        "pointer" : "#/components/schemas/LogoMetaData/properties/mediaType"
      } ]
    },
    "[err-problem]" : {
      "total" : 1,
      "occurrences" : [ {
        "ruleId" : "[err-problem]",
        "description" : "Each error response of each operation SHOULD have a media type \"application/problem+json\"",
        "message" : "[Operation: GET /health]",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 518,
        "pointer" : "#/paths/health/get/responses/500"
      } ]
    },
    "[evo-object]" : {
      "total" : 5,
      "occurrences" : [ {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 156,
        "pointer" : "#/paths/organizations/post/requestBody/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 187,
        "pointer" : "#/paths/organizations/{enterpriseNumber}/get/responses/200/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 223,
        "pointer" : "#/paths/organizations/{enterpriseNumber}/put/requestBody/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 232,
        "pointer" : "#/paths/organizations/{enterpriseNumber}/put/responses/200/content/application/json"
      }, {
        "ruleId" : "[evo-object]",
        "description" : "In a request or response body, if any, you MUST always return a JSON object (and not e.g. an array) as a top level data structure to support future extensibility. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 262,
        "pointer" : "#/paths/organizations/{enterpriseNumber}/patch/responses/200/content/application/json"
      } ]
    },
    "[hdr-case]" : {
      "total" : 1,
      "occurrences" : [ {
        "ruleId" : "[hdr-case]",
        "description" : "By convention, HTTP headers SHOULD use Kebab-Case with uppercase for readability and consistency. ",
        "type" : "mandatory",
        "fileName" : "openapi.yaml",
        "lineNumber" : 365,
        "pointer" : "#/paths/logos/{id}/get/parameters/1"
      } ]
    },
    "[jsn-naming]" : {
      "total" : 1,
      "occurrences" : [ {
        "ruleId" : "[jsn-naming]",
        "description" : "All JSON property names SHOULD be written in lowerCamelCase notation.",
        "message" : "[propertyName: Image]",
        "type" : "mandatory",
        "fileName" : "logo.yaml",
        "lineNumber" : 24,
        "pointer" : "#/components/schemas/Logo"
      } ]
    },
    "[oas-exampl]" : {
      "total" : 1,
      "occurrences" : [ {
        "ruleId" : "[oas-exampl]",
        "description" : "Example does not validate against schema",
        "message" : "employerId: Type expected 'integer', found 'string'. In Schema: employer.yaml#/components/schemas/Employer : <belgif/employment/identifier/v1/employment-identifier-v1.yaml#/components/schemas/EmployerId>.<type>\nemployerId: Value '164893015' does not match format 'int64'. In Schema: employer.yaml#/components/schemas/Employer : <belgif/employment/identifier/v1/employment-identifier-v1.yaml#/components/schemas/EmployerId>.<format>",
        "type" : "mandatory",
        "fileName" : "employer.yaml",
        "lineNumber" : 40,
        "pointer" : "#/components/schemas/Employer/example"
      } ]
    }
  }
}

@jpraet , does the format in last example of @smals-mavh seem OK for you?
'type' property will still be renamed to 'level' in the output

Yes, output format looks good to me.


[SPARK-20293][WEB UI][History]In the page of 'jobs' or 'stages' of history server web ui,,click the 'Go' button, query paging data, the page error

What changes were proposed in this pull request?
In the page of 'jobs' or 'stages' of history server web ui,
Click on the 'Go' button, query paging data, the page error, function can not be used.
The reasons are as follows:
'#' was escaped by the browser as% 23.
'& CompletedStage.desc = true% 23completed', the parameter value of 'desc' becomes ' true% 23',is not 'true', causing the page to report an error. The error is as follows:
HTTP ERROR 400
Problem Access / history / app-20170411132432-0004 / stages /. Reason:
For input string: "true # completed"
Powered by Jetty: //
The amendments are as follows:
The URL of the accessed URL is escaped to ensure that the URL is not escaped by the browser.
please see attachment of 'https://issues.apache.org/jira/browse/SPARK-20293'.
How was this patch tested?
manual tests
Please review http://spark.apache.org/contributing.html before opening a pull request.

I don't quite understand, in that you say that the problem was URL-encoding the URL, but the solution here is to URL-encode it again. Is that right? maybe you can show a more concrete example of the URL as generated by the UI, and exactly what it is interpreted as, and the error page. This isn't very clear now.

Can one of the admins verify this patch?

Is this, the only way to encode, will not let the browser to escape our special characters.The page will not be error.

@guoxiaolongzte This seems familiar, are you using the latest version of Knox with your Spark UI?

@ajbozarth I am using the  latest  spark version.

After taking another look I was mixing this bug up with another when I asked that

On a quick git blame this is my code that seems to be broken. I'll take a more detailed look when I can in the next couple days.

So how do I deal with this PR?@ajbozarth

I just downloaded the latest spark master code to compile and install , test the problem, there are still bugs, the page is wrong.

I attempted to recreate this with the latest code on Safari, Firefox and Chrome and everything worked fine for me. What browser/environment are you using that you see this issue?

Browser is Chrome.
Spark version is 2.1.0.
Must be History Server Web ui.
My Url:
http://<IP_ADDRESS>:18082/history/app-20170411132432-0004/jobs/?completedJob.prevPageSize=100&completedJob.sort=Job+Id&completedJob.desc=true%23completed&completedJob.page=1&completedJob.pageSize=100#completed
Excuse me,Are you testing at the History Server Web Ui?
Today,I try to recreate the latest Apache master code to test the bug.

I can reproduce this bug by the following steps provided in the JIRA - https://issues.apache.org/jira/secure/attachment/12862828/jobs.png and https://issues.apache.org/jira/secure/attachment/12862829/stages.png
Chrome

Safari

After replacing %23 to #, it seems showing the contents correctly as below:

maybe you can show a more concrete example of the URL as generated by the UI, and exactly what it is interpreted as, and the error page. This isn't very clear now.

+1. @guoxiaolongzte do you mind if I ask to fill up the PR description with them? I think UI changes require before/after snapshots.

Thanks for the followup @guoxiaolongzte and @HyukjinKwon I'll take another look at work tomorrow. Also for clarification, the reason I'm being extra detailed about this is because I want to make sure this fix isn't just a band-aid solution.

@ajbozarth @HyukjinKwon   I have added the PR description again.

So I'm still not able to recreate this, I'm unsure how the Go button is creating the url you have, the issue here is for some reason #completed is being inserted in the middle of the url where it's not supposed to be and the extra # is being encoded and causing you issues. I'm not sure this is a good fix, but we should figure out why your history server is adding the extra #completed to the middle of your url and not mine and fix that.
In order to help me figure out why our results are difference could you do an inspect on the Go button on your stage page and attach a screenshot? This is what mine looks like:

@ajbozarth, I am terribly sorry. I just realised that my classpath was pointing out Spark 2.1.0.... (I was testing regressions.....).
  I think we should close this. I apologise again ...

I am trying hard to test it in apache master.

@HyukjinKwon
Now build the apache master is error.
[INFO] Compiling 73 Java sources to /home/spark_build/spark-2.1.0/common/network-common/target/scala-2.11/classes...
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:144: 错误: 非法的表达式开始
[ERROR]     channel.writeAndFlush(new ChunkFetchRequest(streamChunkId)).addListener(future -> {
[ERROR]                                                                                ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:144: 错误: 非法的表达式开始
[ERROR]     channel.writeAndFlush(new ChunkFetchRequest(streamChunkId)).addListener(future -> {
[ERROR]                                                                                ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:144: 错误: 需要';'
[ERROR]     channel.writeAndFlush(new ChunkFetchRequest(streamChunkId)).addListener(future -> {
[ERROR]                                                                                ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:145: 错误: 不是语句
[ERROR]       if (future.isSuccess()) {
[ERROR]          ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:145: 错误: 需要';'
[ERROR]       if (future.isSuccess()) {
[ERROR]                              ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:151: 错误: 有 'if', 但是没有 'else'
[ERROR]       } else {
[ERROR]         ^
[ERROR] /home/spark_build/spark-2.1.0/common/network-common/src/main/java/org/apache/spark/network/client/TransportClient.java:163: 错误: 非法的类型开始
[ERROR]     });
[ERROR]      ^

After seeing @HyukjinKwon inspector I tracked down the issue and found #16953 that fixed this in master and 2.1 already. It was such a tiny pr I forgot all about it.

@guoxiaolongzte I assume your Java version is 7. I think we dropped the support of Java 7 (https://issues.apache.org/jira/browse/SPARK-19493). We are able to build this on Windows but there are additional settings needed (e.g., memory for maven).
(FYI, I was able to build Spark on Windows 7 with 32 bits before and we are building it Windows server 2012 64 bits via AppVeyor up to my knowledge.)
@ajbozarth, thank you for your time and effort. I at least confirm that this issue is not reproducible in the current master. @guoxiaolongzte Let's close this.

@ajbozarth
@HyukjinKwon
OK.thanks. I will close this PR.

@HyukjinKwon
Thank you again, and now windows machines can compile apache master.
No my java version is 1.8.

@HyukjinKwon
I just replaced the spark-core_2.11-2.2.0-SNAPSHOT.jar
Successfully start history server, but I click the Go button, now is error, the error log is as follows:.
17/04/14 13:21:33 WARN ServletHandler: /history/app-20170411132432-0004/1/jobs/
scala.MatchError: java.lang.NoSuchMethodError: org.apache.spark.scheduler.TaskInfo.accumulables()Lscala/collection/mutable/ListBuffer; (of class java.lang.NoSuchMethodError)
at org.apache.spark.deploy.history.HistoryServer.org$apache$spark$deploy$history$HistoryServer$$loadAppUi(HistoryServer.scala:230)
at org.apache.spark.deploy.history.HistoryServer$$anon$1.doGet(HistoryServer.scala:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.spark_project.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.spark_project.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
at org.spark_project.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at org.spark_project.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at org.spark_project.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at org.spark_project.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.spark_project.jetty.servlets.gzip.GzipHandler.handle(GzipHandler.java:479)
at org.spark_project.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at org.spark_project.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.spark_project.jetty.server.Server.handle(Server.java:499)
at org.spark_project.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.spark_project.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.spark_project.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
at org.spark_project.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.spark_project.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)

It sounds a different issue with this. If it is a question, maybe, it might be better to ask a question to mailing list first before opening a JIRA. If it is really an issue, it might be better to report it with description, snaptops and steps to reproduce like I did above https://github.com/apache/spark/pull/17608#issuecomment-294059200 and https://github.com/apache/spark/pull/17608#issuecomment-293771070
It seems a warning not an error BTW.


Getting a couple of errors when checking this in the console. Any guidance appreciated.

http://localhost:3000/packages/ethereum_web3.js?6eb7f7927c94ee7c887d8b1303ce4d32e2190c29 is being assigned a //# sourceMappingURL, but already has one ethereum_web3.js:6625:4
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help http://xhr.spec.whatwg.org/ ethereum_web3.js:2924:0
Also what is the suggested policy for adding server startup code? Is that added to the client/index.js file?
or is it better to make a separate server directory and add it there?

I believe this comes with the territory of using xhr XMLHTTPRequests. I think this is more with web3 than this repo.


alex 2.0.0 has some trouble with '?

I think this screen will illustrate best

Thanks, I’ll dig in!

Okay, the three commits above fix the warnings you mentioned. If you rm -rf node_modules/ and npm install again, things should be operating normally!
Thanks again for raising the issue!

:100:


Fps and No. of particles:

How to remove the information box of FPS and Number of particles present at top left corner of the screen?

stats.domElement.style.display = 'none'

Thank you for following up on this. Even if it's silly and old. :D

I couldn't get the fps out of the left corner either, so I found your comment with the same question, and thought there might be more people with the same question. Hope it helps more people! :D

Sure it does :)
I don't understand why they didn't create a disable button to not show it. Which makes me think, maybe they did! Or not...
Either way, that'll do the work :D

same problem thanks for answer :)

i got same problem. thank @mrbrunelli  your answer fix it..

stats.domElement.style.display = 'none'

Thanks man, its great answer!

stats.domElement.style.display = 'none'

It does not work with react, What can I do?


Adding react-native-modal to eigen

New Dependency
Name: react-native-modal
URL: https://github.com/react-native-community/react-native-modal
Focus
Wraps the react-native Modal component and enhances it with additional animation and display features. Makes it really easy to do things like animating a modal sheet from the bottom and having the background fade. The fact that it has a simple API and hooks into the RN modal means it's easy to plug in and would be easy to remove if RN adds these features to their own lib.
See example PR here: https://github.com/artsy/eigen/pull/3267
Check List

[X] Have read over the source code
[X] Has had a release in the last year, or looks done and stable
[X] Could you fit this codebase in your head after reading the source?
[X] Is this the stand-out obvious answer to a particular domain problem?
[ ] Do you expect your team to be the only people who know about this dependency?
[X] Is this obviously being used in production by the maintainers, and thus battle-tested?
[ ] Does our bundle already include a (transitive) dependency that solves the problem and could we use that instead?
[X] Do you feel well versed in the domain of this dependency and/or could maintain it if that needs to become an
option?

Alternatives

Re-implement functionality ourselves

The library is lightweight so I think we'll save time and effort (in addition to having a community) by using the dependency, but we could certainly build the functionality ourselves.

Awesome, thanks Sarah! The MX team went over the RFC in our Knowledge Share this morning and we agree it makes sense to add this dependency 👍 The PR you added was particularly helpful. Please feel free to resolve at your convenience.
We also talked this RFC process itself. We think it some cases, like this one, the RFC process can introduce extra friction where it’s not needed. However, we felt it’s worth having the process in place to make sure larger dependencies get discussed. As someone who just went through the process, do you have any feedback on it? Was this too onerous? Etc. Thanks again!

@ashfurrow good question! Here are some thoughts on this case:

I included some reasoning in my PR that added the dependency, so it felt a little redundant to also create this issue (although the checklist here is more comprehensive).
I worry in general that the requirements to read through the source code/fit it in ones head could cause some developers to feel uncomfortable about adding dependencies (not a blocker in this case, but I had that thought as I was reading through).
We also allow for PRs to serve as RFCs, especially for things like adding documentation. Would it be possible to adapt this to a PR workflow (maybe a description template)? That would have the added benefit of colocating the dependency addition with the repo it's introduced to.

I like the idea of treating a PR-as-RFC, especially for smaller dependencies like this one. For a larger dependency, say Redux for example, I wouldn't want to encourage engineers to finish a complete PR's worth of work before adding the PR. I'll look into GitHub's tooling around a description template.
The checklist is more of a list of things to consider before adding the dependency, to encourage developers to take ownership of the code they add to the app bundle. I agree that the requirement to fit the entire source code in one's head is onerous – I never considered it a must-have, so maybe we can reword the RFC template to clarify the purpose of the list a bit.


Need support for search delay (debounce)

Thank you for really helpful flutter package. I think there is an important feature missing which is debounce.
When user search in list it immediately invkoing the searchFn which is a performance issue.
It will be more helpful, if there is an option for setting a property for search delay like debounce:500 or delay:500 where 500 is milliseconds value.

Hello @farukaziz ,
Would your request be fulfilled if you added a 500 milliseconds delay in the searchFn?

It’s okay for my current request.

If you add the search delay feature with package that would be great.

Hello @farukaziz ,
Would your request be fulfilled if you added a 500 milliseconds delay in the searchFn?

Yes

Hello @farukaziz ,
Since search_choices now supports Future searches for internet calls, it was even more important to support this delay request. searchDelay is a new parameter with version 2.0.16 of the search_choices plugin.


Create MPI-Usage.md

Adding the basic information that a DAPHNE user may need to execute DAPHNE scripts with the distributed MPI backend support.
@corepointer @aristotelis96  @pdamme  feel free to edit whatever is needed

LGTM - thx for your contribution @AhmedEleliemy. I've linked the document from the documentation about distributed execution.


joplin-desktop: 1.0.143 -> 1.0.158

Motivation for this change
https://github.com/laurent22/joplin/releases/tag/v1.0.158
and previous, see:
https://github.com/laurent22/joplin/releases
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@dtzWill thanks!