Error with 'pip install shap' on both linux and mac

I am trying to install SHAP in my anaconda environment. But I run into error with gcc. See the error below and attached is the image of the error. Any help is appreciated! Thanks!
gcc: error trying to exec 'cc1plus': execvp: Permission denied

The issue is with my linux machine. I was able to figure out and could install the package. Closing the issue. Thanks!

Great!


Feature/binary gt pretraining

Description
New experiments and networks of the ICDAR/HIP paper

Codecov Report

Merging #145 (58f59c1) into dev (798836b) will decrease coverage by 0.01%.
The diff coverage is 60.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##              dev     #145      +/-   ##
==========================================
- Coverage   89.59%   89.59%   -0.01%
==========================================
  Files          56       56
  Lines        2874     2873       -1
==========================================
- Hits         2575     2574       -1
  Misses        299      299

Flag
Coverage Δ

cpu
89.59% <60.00%> (-0.01%)
:arrow_down:

pytest
89.59% <60.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/callbacks/wandb_callbacks.py
56.52% <33.33%> (ø)

src/models/backbones/unet.py
94.85% <100.00%> (-0.08%)
:arrow_down:

src/utils/utils.py
78.94% <100.00%> (+0.22%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Download Links for checkpoints not working

Hi, I was trying to evaluate the checkpoints for the digress models provided here but it seems the download links are now broken.
Can someone tell me where else i can get the pretrained checkpoints?
https://drive.switch.ch/index.php/s/hRWLp8gOGOGFzgR

My drive account has unfortunately been deleted, and I have lost access to the checkpoints. If you happen to have a downloaded checkpoint stored locally, I would be glad if you could send me an email at<EMAIL_ADDRESS>or raise a Github issue.


[RESOLVED] Unavailable by ICMP ping

Problem started at 20:27:16 on 2022.10.13
Problem name: Unavailable by ICMP ping
Host: W7PINGDEMO
Severity: High
Operational data: Down (0)
Original problem ID: 3914
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23136&eventid=3914

Problem has been resolved in 3m 0s at 20:30:16 on 2022.10.13
Problem name: Unavailable by ICMP ping
Host: W7PINGDEMO
Severity: High
Original problem ID: 3914


[BEAM-4420] Add KafkaIO Integration Tests

This pr adds basic IOIT that can be run for 1000 records (there's only hashcode for 1000 records currently). To make the code review easier and because I'm not a Kafka expert, I took a baby steps approach here - after this PR is approved consequent PRs will provide:

metrics collection
hashes for bigger loads
jenkins job to run automatically and on-demand & dashboards for them

I ran this test on existing kubernetes kafka cluster that is there in .test-infra folder (with success).
@aromanenko-dev @iemejia could you take a look?

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Checkstyle not happy, you should use the vendored version of guava. Can you please also squash the commits into one with the proper title. Thanks.

@iemejia @aromanenko-dev thanks for the review. I provided fixes.
@iemejia I didn't squash the commits on purpose -  those are two atomic, independent changes. Having them as separate commits shows better why exactly something changed with proper commit titles and descriptions (see the description for the Kubernetes change). Squash will obfuscate this and will result with multiple unrelated changes in one commit. Other than that it will be easier to revert parts if needed. Suppose I was to revert only the Kubernetes change. Should I be forced to revert the whole test too?

Thanks!


[CMT-742-1086] translate(article): yearn x tenderly - es

Description

Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.

This pull request ...
Fixed issue

Please indicate the fixed issues with this exact format Fixes #232 where 232 is the number of the issue. This will trigger an auto-close if the issue when this PR is merged.
Supported keywords:
Fixes #1,#2,#3
close #1, #2, #3
fix #1 #2 #3
resolve #1,#2 #3
Resolves: #1,#2,#3
closed : #1, #2, #3

Fixes #(issue)
Type of change

Please delete options that are not relevant and check the box.

[ ] Add a new article/page
[ ] Fix a Typo
[x] Add a new translation
[ ] Other

Resources

Any screenshots, links or relevant resources to explain better the changes.

Fixed, thanks
On Thu, Mar 3, 2022 at 6:32 PM Dark Ghosty @.***> wrote:

Assigned #1086 https://github.com/yearn/yearn-comms/pull/1086 to
@RestlessMike https://github.com/RestlessMike.
—
Reply to this email directly, view it on GitHub
https://github.com/yearn/yearn-comms/pull/1086#event-6179861460, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIKGRBYYU67BVUEADBHU3ODU6DZTRANCNFSM5P2IPJNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***>


YouTube Transcripts

Videos on YouTube can optionally be published under a CC-BY license. We can identify these videos with the YouTube API, download them, and transcribe them with an ASR system like whisperX.

Code for cataloging CC YouTube videos can be found in this repo: https://github.com/nkandpa2/youtube-commons. About 800K CC videos adding up to about 300K hours of primarily speech-based video have been cataloged.

Can we find any explicit statement that these videos are public domain, or do we need to rely on the reasoning that "these were made by the government, therefore they are public domain"

No, I was not able to find any explicit statements inside the government YouTube channels so far that the videos they host are in the public domain except by using the full-text search to search for "Public Domain" which only finds 3,000 videos: https://find.search.gov/search/news?affiliate=usagov_all_gov&channel=10448&sort_by=&query="public+domain".
The only explicit statement about a channel I was able find so far is on the USDA website, which states that all the content in their YouTube channel is in the public domain in a privacy assessment (p. 4): "Video content published to the USDA YouTube page will be previously approved by relevant Department and Office of Communications leadership, and will be available in the public domain." But while USDA makes this statement in this random document on their website, they do not include this statement in their YouTube channel or the videos themselves, which are indexed through find.search.gov.
Generally speaking, government videos are rarely expliclity declared to be in the public domain. But that's the standard case for federal government documents as well. Outside the cultural heritage sector works are rarely explicitly declared to be in the public domain with something like the PD Mark and even in the CH sector the use of a PD mark is much less common than CC licenses.
US Federal Government works are "born in the public domain" by law, they don't become part of the public domain at some later point through a waiver or expiration of rights. But such a general legal status is of course harder to document than an explicit rights statement, so it's worth evaluating whether it's worth the effort to transcribe government videos in addition to CC videos.

This is a great idea @storytracer. I think we can cover many of these videos by simply including the major US agencies' YouTube channels in the dataset. Looking through a couple of them from the search results you provided, channels sometimes will explicitly state in the description something along the lines of "Here you will find original content produced by [AGENCY]". So to me it feels reasonable to count this data as PD. We can always remove this later if we are unsure of the PD status.

@nkandpa2 What's the current state of cataloging? Do you have an ETA and do think you could upload the catalog as a dataset to HF? I would like to help with the distributed processing of the audio files on our infrastructure!


Make InputStreamDelegateDecoder support an empty InputStream.

Thanks for your interest in palantir/http-remoting, @GrahamDennis! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


Which breaking changes in 1.0.0?

I'm afraid to do the update now, because I saw "This is a major release with breaking changes".
But perhaps I missed the thing, but I do not see breaking changes listed in the notes.
Which breaking changes are in 1.0.0? So what is breaking, needs manual rework or whatever else?

The breaking changes are related to the configuration. You may have to configure it in the UI. See the README for how to do that.

"May" as in it should work but wasn't tested so you can try and see.


bp-wallet default-features false

By adding bp-wallet to the dependencies without specifying default-features = false we are also importing bp-esplora (because bp-wallet specifies default = ["esplora"]), making the rgb-runtime definition of the esplora feature (esplora = ["bp-esplora", "bp-wallet/esplora"]) pointless.
With this PR we import bp-wallet without default features, allowing users of rgb-runtime to avoid depending on bp-esplora unconditionally.

BTW this is duplicate of https://github.com/RGB-WG/rgb/pull/127

I was not sure it was correct removing esplora from the default features of bp-wallet, but this also does the trick so LGTM, thanks

removing esplora from the default features of bp-wallet

I think it was a mistake it got there first: bp-wallet is assumed to be a library. Originally it was a cli and that's why it needed default feature so users can do cargo install bp-wallet without --all-features (which always confuses people, who do not read README and leads to plenties of opened issue saying the same thing "this does not compile!" over and over again). But since it is library, and the cli name is bp-util, it was safe to remove it there


QOL: Paint terminal win32 host background so it looks like the launch profile?

Environment
Windows build number: 10.0.18363.778
Windows Terminal version (if applicable): 0.11.1121.0

Steps to reproduce
Start Terminal and observe the short gray-to-default-profile-background-color flicker before the shell is loaded. Close Terminal and observe the same in reverse.
Expected behavior
There should be no flickering. When starting, the background of the "empty" shell area should be the same color as the default profile. When closing, the shell area should use the background color of the currently active profile/shell.
Actual behavior
The "empty" shell area is always gray, which means it transitions very quickly from gray to (typically) black when the default profile shell is displayed. Similarly when closing Terminal.

Probably related to this: https://github.com/microsoft/terminal/pull/5277

Really? Why do you think so?

Yea that merged literally 3 days ago, it hasn't actually been shipped to anyone yet

@letmaik do you mean a gray window like this?

This is what the moment looks like when it starts/exits:

Oh, I thought it was part of the .11 release. So much for being obvious.

This happens for me as well, in the most recent release but also in previous ones. The terminal window appears with the default system background colour:

then the correct theme background is applied. Both with standard decorations, or with tabs in the titlebar. The same when closing the window.
Switching the system's "default app mode" to dark does not change the flash colour: it's still white.

Thanks for writing this all up!
I think it would be a nice quality of life improvement if we were to paint the window in a color closer to the one it'll eventually be filled with.
@dreadnaut your issue seems different, somehow... that titlebar doesn't look familiar to me (the standard Windows one is narrower, and the custom one we draw has different caption buttons ...)

(name changed to encompass what I think would be best)

@dreadnaut your issue seems different, somehow... that titlebar doesn't look familiar to me (the standard Windows one is narrower, and the custom one we draw has different caption buttons ...)

I use Terminal with acrylic disabled, and
    "alwaysShowTabs" : false,
    "showTabsInTitlebar" : false,

which means I only see the standard Windows titlebar until I open a second tab. If I switch to tabs-in-titlebar, the flash has the same colour. I'd say it's the same issue 🙂

Titlebar looks frankly bad. It’s so bad that I’m ready to use alternative terminals where the mouse doesn’t work in mc, etc., but it’s not painful for my eyes to look at them.
And if you turn on the acrylic - it gets even worse. Titlebar doesn't mix with absolutely anything! It should have the same color (and transparency if enabled) as the main menu.

I'm gonna also x-ref #11561 here. With the transparency changes in 1.12, the backgound starts as totally transparent, instead of gray/white.
There's also now the possibility that the Terminal is launching:

with some profile other than the default profile
with multiple tabs & panes, which might complicate this.

So this isn't necessarily straighforward "use the default profile's BG to paint the window".

In case this changes priority at all: getting flashbanged in the eyes like this is the #1 thing I know of that makes dark themes unhelpful for some people - if your eyes are sensitive in the right way, light theme is bad and unpleasant but still better than to let your eyes get used to dark only to get sliced across the eyes with a momentary flash.

For anyone looking for a slightly better experience, I noticed that if I install WSL Debian, set my default terminal application to Windows Terminal instead of Windows Console Host, and then run Debian, I only get the flash on close rather than on open.
(I presume you'd get the same improvement with any command-line program which indirectly launches Windows Terminal instead of directly, but I haven't checked.)

Actually I take that last statement back.
Upon further testing it seems that it's only sometimes fast enough to not do the white-ish flash on launch in those cases, but other times I still get the flash.
Also an interesting effect is that the initial color on start and final color on close are different. The open color seems dimmer, like a gray, while the close color seems closer to a white.

You know what, like 8 months ago we started having the HWND be entirely hidden until the window is ready to render. That basically makes this issue moot 😄

Now that you mention it, I don't remember being bothered by this problem lately.
(I moved to Emacs through gWSL as my daily driver terminal emulator about a year ago, so in those 8 months I've only opened the terminal a handful of times.)
Checking now, I can confirm that this issue seems to no longer happen, on both open and close. Big thanks.


Hi,excuse me,I want to konw why the SI-SNR loss doesn't decrease when I used reverberation dataset?

Hi.
Could you please explain a little more?
I don't know the correlation between using reverberation dataset and not reducing the SI-SNR loss.

When the training data has no reverberation, the SI-SNR can be reduced to -17, but after adding the reverberation to the training data, it will be reduced to 6 and will not move.

When the training data has no reverberation, the SI-SNR can be reduced to -17, but after adding the reverberation to the training data, it will be reduced to 6 and will not move.

When the training data has no reverberation, the SI-SNR can be reduced to -17, but after adding the reverberation to the training data, it will be reduced to 6 and will not move.

The loss range may differ because the training dataset has become more difficult for DNN to learn as reverberation is added to the training dataset.
What was the result of the training? Was the model not able to reduce noise or reverberation?

it is not easy to answer his question so far, but i do remember, that the train-dataset in the original paper DCCRN(by tan) has reverberation.
"In detail, at each training epoch, we rst convolve speech and noise with a room impulse response (RIR) randomly-selected from a simulated 3000-RIR set by the image method [32], and then the speech-noise mixtures are generated dynamically by mixing reverb speech and noise at random SNR between -5 and 20 dB."
yyd1994 may change the train-dataset very slowly and careful and observe the difference, which might be a big project...........


Add instructions on how to run the different models

add detailed instructions on how to run our models, e.g. which commands should someone run in order to run the rephraser etc.

Done for the Synthesizer.


Disable or Enable specific extensions in a workspace

It would be nice if one could explicitly enable or disable specific extensions for a workspace.  For example, I have some projects where I need eslint+prettier, others where I'm using Biome.  It's kind of annoying to get errors for one or the other, or have to manually enable/disable various extensions when switching between different projects over time.
The explicit disable should ignore any extensions that aren't installed or are already disabled.
The explicit enable should provide a dialog for any extension that is not downloaded locally, asking if it should be downloaded and enabled globally or just locally.
I did look for duplicates and after several pages of search results didn't find an existing match, apologies if this is a duplicate.

VS Code already supports disabling extensions for specific workspace. Alternatively, you can install extension when needed, disable it globally and re-enable only for needed workspaces.

Moreover, there is Profiles feature that keeps its own list of extensions/settings.
Have you tried this features?

@tracker1 Can you please try what @IllusionMH recommended in the above comment and let us know.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Question: Angle is in what? (Degrees or Radians)

Hi there kaboom community,
I am trying to make a 2d top-down shooting game... but I am besides myself stuck on what the angle is of an object.
Another good question I will have is (assuming it's degrees), how do I increment it by a single degree?
I have the math to convert the angle in degrees to a vec2 of x and y, that I will apply to my "bullet" to make it move in the direction it was fired from. (I just need to know how to get an exact/or close enough, angle in degrees from an object to use my math on it to get a more realistic bullet trajectory)
In the future of my game I am thinking of maybe even using the mouse to "aim" but for now everything is basic keybindings.
If you need any further information I will gladly provide it.

Can  you post an example project? Can help.

It's brought by the rotate() component. There's this example that changes angle.

Can you post an example project? Can help to explain what you are trying to do.

A general idea is for something (similar NOT identical) is the web game diep.io minus all the multi-player stuff.

It's brought by the rotate() component. There's this example that changes angle.

So obj.angle += 1 rotates exactly 1 degree? I want the angle to change based on keyDown not time.

Sorry for the delay is responding, I forgot to check my github on this.

angle is in radians, there is actually an undocumented deg2rad(deg: number) => number helper function for that for convenience.

Ah, ok... so I could just take my cosine and sine from that to get my vec2 of x,y for my bullet then... (And I use the deg2rad to rotate by X degrees?)

Ok, confirmed it with the example you gave me... does exactly what I was looking for. (Thank you for helping)

Are you trying to calculate the vector from an angle? Yeah if you're using degrees it'll be something like
function vec2FromAngle(a: number): Vec2 {
	return vec2(Math.cos(deg2rad(a)), Math.sin(deg2rad(a)));
}

(there's something similar used internally, maybe i should export it...)
Glad it helped!

Are you trying to calculate the vector from an angle? Yeah if you're using degrees it'll be something like
function vec2FromAngle(a: number): Vec2 {
	return vec2(Math.cos(deg2rad(a)), Math.sin(deg2rad(a)));
}

(there's something similar used internally, maybe i should export it...)
Glad it helped!

Well now that I know that obj.angle is in radians I just need to make
function vec2FromAngle(a: number): Vec2 {
	return vec2(Math.cos(a), Math.sin(a));
}

function spawnBullet(obj) {
  add([
    rect(3, 3),
    pos(obj.pos),
    {
       vel: vec2FromAngle(obj.angle)
    },
    'bullet'
  ])
}

Now I would pass player to spawnBullet and it should apply bullet.vel attribute so when I move it will look like
action('bullet', (b) => {
  b.move(b.vel[0], b.vel[1])
})

Assuming my math is right on that and I didn't transpose/mistype anything. :)
ka :boom: .js

b.move(b.vel[0], b.vel[1])

maybe a typo here? vec2 is { x: number, y: number } instead of array

Ooops, Yeah I always get that mixed up... I keep thinking it's a c++ vector or python list... but it's not.
So it really would be?
b.move(b.vel.x, b.vel.y)

Yep! Or just b.move(b.vel)

Ah, didn't help that my barrel.png was being rendered the wrong way.
Meh, but looks like everything works. (Again, Thank you very much)


added methods for getting keys, items and dict

This change enables to retrieve the row as a dict and iterate the keys and/or items, like with a normal dict; in other words, making the Row object a dict-like object:

row.dict()
{'name': 'Isabel', 'profession': 'bridge builder'}
for k, v in row.items():
for k in row.keys():

I signed it!

I'd like to do a thorough review of the code (e.g. keys() and items() could be generators) but want to wait until @tswast comments on whether or not these features are desired.

I see, good point about the generators, thanks. I'd fix that but will hold off until we know more about whether these are desirable at all. The thing is that it would be great to be able to either return the row as a dict or convert it to a dict really easily, which currently is a bit of a hacky process. Thanks!

I fixed it after all; the tests seem to have run successfully :-)

I like keys() and items() to make Row act even more like a dictionary. That part LGTM.
What is your desired use for dict()? Are you using it to serialize the rows?

I'm using dict() to serialise rows into a standard dict, which I can then convert to json. As long as keys() and/or items() makes it in, I'm happy not to have dict(), simply because I can do it in my own code. Alternatively, I'm happy to write a get() method for Row instead, so it's possible to get a value in a dict-standard failsafe way. Thanks!

As long as keys() and/or items() makes it in, I'm happy not to have dict().

Yeah, I'd prefer not to have dict() since it's not a standard method and it's easy enough for someone to make their own dictionary now that there is keys() and items().

Alternatively, I'm happy to write a get() method for Row instead, so it's possible to get a value in a dict-standard failsafe way. Thanks!

Ooh, yes please to adding the get() method. That sounds great.

I signed it!

So dict() is now removed and get() is in place, including code checks and the tests for the module check out (not yet completed for the whole hog but that should be fine). Please let me know if there are any issues with my code I should fix. Thanks!

Thanks :-)


IO.js 2.2 build/SSL issue for Travis CI

The latest version of Bluebird doesn't build on Travis CI any more, with IO.js 2.2:
WARNING: checksums are currently disabled for io.js
Now using io.js v2.2.0
$ node --version
v2.2.0
$ npm --version
2.11.0
$ nvm --version
0.23.3
5.19s$ npm install
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/io.js/v2.2.0/bin/iojs" "/home/travis/.nvm/versions/io.js/v2.2.0/bin/npm" "install"
npm ERR! node v2.2.0
npm ERR! npm  v2.11.0
npm ERR! code ESSL
npm ERR! SSL Error: https://registry.npmjs.org/bluebird does not support SSL
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

Note this line:
npm ERR! SSL Error: https://registry.npmjs.org/bluebird does not support SSL
Any idea why this is happening?

This is an issue with npm and/or io.js.

I was about to reply that I thought the same :) But lots of people are about to run into the same trouble, with the recent updates :)

yes but there is literally nothing that is relevant to bluebird here or nothing that bluebird could do


Tailwind 1.2?

@TVke  - Does this work with Tailwind 1.2? I am running into a few things when I try this with a tailwind.config.js file generated using 1.2:

I am trying to use the https://tailwindcss.com/docs/container/#app class but it doesn't look like this library is pulling that in.
Unless I remove maxWidth: {} from the config file, my app errors out: (breakpoints is not a function):

Hi @mattkoch614
Breakpoints are not supported in ‘react-native-tailwindcss’ as discussed in #25.
I will release a 1.2 version of this package soon when I see the time but breakpoints are not my priority right now.
I would accept a PR for this.
Greetings
Thomas

@TVke - OK, this makes sense. Thank you! For now I will remove this from the tailwind config.


Subscripts detected as runnable targets

Hi, I tried to run fzf-make on the glibc repos to get a better overview of the monster that is the Master Makefile for the GNU C library (yes this boi is 23k lines long). I was surprised that it even opened the preview window under 2s, (still very laggy but hey, that's a real stress test, to say the least)!

Here is a minimal example to reproduce this issue:
.PHONY: real_rule
real_rule:
	echo "good"

define my_script
#!/bin/bash

echo "this is a trap: not good"
endef

Skipping defines blocks would help to filter these lines easily

@Sigmanificient
Thank you for letting me know the issue and take time to report!
For now, the extraction of the target is done by reading the contents of the Makefile line by line, but it seems that it can be avoided by excluding irrelevant lines such as defines blocks before extracting the target.
Thank you for always reporting the issue in detail!


disable mainactor test

there's an unseen failure in CI

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


remove using $parents methods in navigation

Hi, I wanted to make an improvement with navigation, but noticed that you use methods directly from parents, not $emit.
Why is the a tag used for buttons, instead of button? This is a violation of semantics.
Thx for you library.

Coverage increased (+0.1%) to 62.981% when pulling f1cbfa437f966e866a7c77b042f14afe25416e43 on edDimensi:feat/navigation/refactor into cdf92d181caae0fa8a422c2c7331844a92522680 on SSENSE:master.

Hey @edDimensi, thanks for the PR! I'll review it later this morning.
I agree that using button elements would be more ideal - we actually have a few other sematic upgrades we could do using html5's semantic tags (at first glance, it looks like lots of divs could be 'section', 'nav' or 'details'). If you're interested in making that change feel free to submit a PR or add it to this one :~)

Yes, i add.

@edDimensi 🎉

@quinnlangille how update snapshots?

@quinnlangille
I added some changes to the semantics.
Also updated snapshots. And added a little more jsdoc

@quinnlangille ?


How are PageInfo::{start_cursor, end_cursor} set when using Connection?

Or do I need my own Connection to be able to set them?

Yes, you need to set them yourself, as described in this document.
https://relay.dev/graphql/connections.htm#sec-undefined.PageInfo.Fields

But do I need my own connection type and then use query_with? Or is there a setter for Connection I'm not seeing?

Wait, I guess the start and end cursors come from the cursor in the first and last edges that are inserted?

Sorry I was wrong. 😂
PageInfo is automatically generated from all edges within the Connection.
https://github.com/async-graphql/async-graphql/blob/b82186413b0accdf9903a9a5b4256512d1a36fde/src/types/connection/connection_type.rs#L132

Ooh, that's where the PageInfo creation was hiding, I didn't notice it when looking around.


Problems running code with GPU support.

Hi,
I'm in a tensorflow 1.15.0, with python 3 docker container.  GPUs seem to be working fine for simple test tasks e.g. tf can see
four gpus and I can load the up.
The requirements are all installed.
When I run
CUDA_VISIBLE_DEVICES=* python train.py --model_type gp-vae --data_type physionet --exp_name asdf
Everything works fine - it cylces through calculation -  but it runs on CPU only.
When I run anything else e.g.
python train.py --model_type gp-vae --data_type physionet --exp_name asdf
or
CUDA_VISIBLE_DEVICES=1 python train.py --model_type gp-vae --data_type physionet --exp_name asdf
Of any of the reference parameters sets, it bails as per below.
Its not batch size... I've already played with that.
Any ideas?
2021-05-12 21:11:18.088886: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2021-05-12 21:11:18.088901: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2021-05-12 21:11:18.088915: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2021-05-12 21:11:18.088928: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2021-05-12 21:11:18.088941: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2021-05-12 21:11:18.088954: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2021-05-12 21:11:18.088970: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2021-05-12 21:11:18.089512: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0
2021-05-12 21:11:18.089553: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1159] Device interconnect StreamExecutor with strength 1 edge matrix:
2021-05-12 21:11:18.089562: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1165]      0
2021-05-12 21:11:18.089570: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1178] 0:   N
2021-05-12 21:11:18.090103: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1304] Created TensorFlow device (/device:GPU:0 with 10320 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2080 Ti, pci bus id: 0000:5e:00.0, compute capability: 7.5)
GPU support:  True
Training...
2021-05-12 21:11:18.097352: I tensorflow/core/kernels/cuda_solvers.cc:159] Creating CudaSolver handles for stream 0x67c3e70
2021-05-12 21:11:18.097415: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2021-05-12 21:11:18.447486: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2021-05-12 21:11:18.735398: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2021-05-12 21:11:20.163447: E tensorflow/stream_executor/cuda/cuda_dnn.cc:329] Could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR
2021-05-12 21:11:20.170211: E tensorflow/stream_executor/cuda/cuda_dnn.cc:329] Could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR
Traceback (most recent call last):
File "train.py", line 473, in
app.run(main)
File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 299, in run
_run_main(main, args)
File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 250, in _run_main
sys.exit(main(argv))
File "train.py", line 239, in main
trainable_vars = model.get_trainable_vars()
File "/home/torenvln/gp-vae/GP-VAE/lib/models.py", line 325, in get_trainable_vars
tf.zeros(shape=(1, self.time_length, self.data_dim), dtype=tf.float32))
File "/home/torenvln/gp-vae/GP-VAE/lib/models.py", line 332, in compute_loss
return self._compute_loss(x, m_mask=m_mask, return_parts=return_parts)
File "/home/torenvln/gp-vae/GP-VAE/lib/models.py", line 280, in _compute_loss
qz_x = self.encode(x)
File "/home/torenvln/gp-vae/GP-VAE/lib/models.py", line 220, in encode
return self.encoder(x)
File "/home/torenvln/gp-vae/GP-VAE/lib/models.py", line 51, in call
mapped = self.net(x)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/base_layer.py", line 898, in call
outputs = self.call(cast_inputs, *args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/sequential.py", line 269, in call
outputs = layer(inputs, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/engine/base_layer.py", line 898, in call
outputs = self.call(cast_inputs, *args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/layers/convolutional.py", line 387, in call
return super(Conv1D, self).call(inputs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/keras/layers/convolutional.py", line 197, in call
outputs = self._convolution_op(inputs, self.kernel)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py", line 1134, in call
return self.conv_op(inp, filter)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py", line 639, in call
return self.call(inp, filter)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py", line 238, in call
name=self.name)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py", line 227, in _conv1d
name=name)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/util/deprecation.py", line 574, in new_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/util/deprecation.py", line 574, in new_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/nn_ops.py", line 1681, in conv1d
name=name)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/gen_nn_ops.py", line 1031, in conv2d
data_format=data_format, dilations=dilations, name=name, ctx=_ctx)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/gen_nn_ops.py", line 1130, in conv2d_eager_fallback
ctx=_ctx, name=name)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/eager/execute.py", line 67, in quick_execute
six.raise_from(core._status_to_exception(e.code, message), None)
File "", line 3, in raise_from
tensorflow.python.framework.errors_impl.UnknownError: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above. [Op:Conv2D] name: sequential/conv1d/conv1d/

Is this due to tensroflow being bumped up - as per the closed issues?

Hi,
It sounds like the problem is due to incompatible tf version / cuda / cudnn / GPU model. Probably, one can try this solution: https://github.com/tensorflow/tensorflow/issues/24496#issuecomment-455265295 , it's a pretty popular problem. As far as I remember, I've successfully tested the current configuration about a year ago.

Thanks for that,
Got it running on 1.15.0 with the items listed in requirements.txt on a docker container.
As per the link you included, I added:
config = tf.compat.v1.ConfigProto()
config.gpu_options.allow_growth = True
sess = tf.compat.v1.Session(config=config)
Just after:
tf.compat.v1.enable_eager_execution()
in train.py
It appears to be running on a single GPU.
Does this model run on multiple GPU?

I don't think so. We didn't run multi-gpu training


Set default notify key

Summary
If DM_NOTIFY_API_KEY has not been defined, automatically decrypt
credentials (from DM_CREDENTIALS_REPO) and inject it. This should make
it easier to run tests locally - though you will still need to have
started your apps with this environment variable in place. Also adds the
@notify tag to two scenarios which were missing it.
This is kinda a strawman as it does mean that credentials will get decrypted every time (requiring 2fa input) even if you specify only a subset of the tests. Will this be faff/annoying?

I can see this being frustrating e.g. if someone has left their phone at home for the day.
Perhaps we could have a setting in local.sh/example.sh that would override this and skip the @notify tests if DM_NOTIFY_API_KEY is not present?

Hmm, well I guess a simply override for this would be to set DM_NOTIFY_API_KEY in local.sh to any value. If the env var is set, it won't try to decrypt credentials.

I guess it boils down to whether new/phoneless devs can live with a couple of tests failing noisily (this is only mildly annoying at the moment).

I feel like it's probably worse to have a thing magically skip tests than for them to fail because they're not set up correctly.

Any input @galund?

I guess I'm concerned about the "you will still need to have started your apps with this environment variable in place" thing: is it common to have the env var in place when starting up an app, but then not have it when running tests?
It might be worth doing a thought experiment about an optimal way to configure an environment for  the frontend apps too, is maybe all I'm saying. Because that might share something in common with what we do for the functional tests.


Javadoc in java files are ignored when formatting

Multiline Javadoc ("/** ... */") in java files are ignored when formatting.
Java code around javadoc is formatted successfully, but not the javacode. Comments ("// ..." and "/* ... /") and singleline javadoc ("/* ... */") are formatted successfully too.
Example :
/**
         * Multi-line Javadoc
                       */
           List<String>          save1   (      Object    obj);

        /** Single-line Save */
    List     <String>    save2   (Object    obj     );

   /**
         * Multi-line Comment
                       */

becomes :
/**
         * Multi-line Javadoc
                       */
List<String> save1(Object obj);

/** Single-line Save */
List<String> save2(Object obj);

   /**
         * Multi-line Comment
                       */

Expected :
/**
  * Multi-line Javadoc
  */
List<String> save1(Object obj);

/** Single-line Save */
List<String> save2(Object obj);

/**
 * Multi-line Comment
 */

works fine for me

What kind of sorcery is this ?
Please have a try with my Eclipse files : http://filebin.net/03l1xcfa8c

org.eclipse.jdt.core.prefs:
org.eclipse.jdt.core.formatter.comment.format_block_comments=false
org.eclipse.jdt.core.formatter.comment.format_javadoc_comments=false
org.eclipse.jdt.core.formatter.comment.format_line_comments=false

that's it, but the file is too short anyways, please go through https://github.com/krasa/EclipseCodeFormatter/blob/master/README.markdown#instructions - on "Get Eclipse formatter settings file"

You the man ! thanks a lot.
My bad, turns out it's a RTFM issue :)


Add support for server hostname checks

This adds support for enabling verify_server_hostname to true in the consul server configuration. This is a recommended setting for production consul servers to ensure that agents can't promote themselves to become a server using the client certificate key (if verify_server_hostname is false, then any certificate that is validated by the RPC CA can become a server).
See https://www.consul.io/docs/agent/options#verify_server_hostname for more info.

is this a common enough setting to add to run-consul for all users?

According to the docs, this is recommended to set to true for any cluster that is configuring RPC encryption:

If verify_server_hostname is set, then outgoing connections perform hostname verification. All servers must have a certificate valid for server.. or the client will reject the handshake. This is a new configuration as of 0.5.1, and it is used to prevent a compromised client from being able to restart in server mode and perform a MITM (Man-In-The-Middle) attack. New deployments should set this to true, and generate the proper certificates, but this is defaulted to false to avoid breaking existing deployments.

So I think this is something we should offer in the core. In fact, I originally wanted to set this to true without an opt-in flag, as a production cluster using RPC encryption should have this included. However, as the docs mention, it breaks existing clusters that don't have the proper certs, so I opted for a feature flag instead to maintain backwards compatibility.

Tests passed! Merging now.

https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.7.9


[FindMyMouse]Account for low double click settings

Summary of the Pull Request
What is this about:
After https://github.com/microsoft/PowerToys/pull/14045 it's possible that users who have double click time set up to work with < 100ms will no longer be able to activate FindMyMouse.
So, we should take into account this and not force an absolute minimum for recognizing a double control click.
Requested in:
https://github.com/microsoft/PowerToys/pull/14045#pullrequestreview-796029158
What is include in the PR:
Code to use minimum double click time as  the minimum between 100ms and 1/5 of the configured double click time.
How does someone test / validate:
Just check if it still works correctly and general code check.
Double clicking under < 100ms can be hard.
Quality Checklist

[x] Linked issue: #14043
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

I'm kind of confused. I normally use the word "click" only for mouse and never for keyboard. Add the "double click time" - which I only know to be a thing for mouse - and I lost the connection to a keyboard button.

Yes, the wording should be "press" for keyboard, I guess.
I think the double click setting was used for being the most similar thing we have to configuring double pressing time on Windows.
These names/setting use is still from the original implementation of SuperSonar. Changing some names for "press" would be good, but I see no issues in keep using the double click setting for this.

Changing some names for "press" would be good, but I see no issues in keep using the double click setting for this.

I agree. My comment was only about naming stuff and using "click" in comments.


Vue warn “style” is a reserved attribute

while testing vuejs + webpack starter template, in console I am seeing this error vue.common.js:431 [Vue warn]: “style” is a reserved attribute

and cannot be used as component prop.

It's framework7-vue related issue. You can track the issue from https://github.com/nolimits4web/Framework7-Vue/issues/148.

Fixed?? I still this issues opened.


Support on ChangeDetection-Strategy OnPush

Could also possibly fix https://github.com/wittlock/ngx-image-zoom/issues/36
We have ngx-image-zoom embedded in an OnPush component and apparently this is not supported (at least it stopped working with Ivy / NG9).
This is a work in progress, open for discussion. I did not dive deep into the code, just needed a quick fix for our app.
I published this branch on NPM as @zeit-dev/ngx-image-zoom, v0.6.1 if anybody would like to try.
Cheers
Marian
PS: To replace the original ngx-image-zoom with @zeit-dev/ngx-image-zoom don't forget to remap the path in tsconfig.json:
{
  "compilerOptions": {
    ...,
    "paths": {
      "ngx-image-zoom": ["node_modules/@zeit-dev/ngx-image-zoom"]
    }
  },
  ...
}

Any plans on working further on this one?

Closing this due to lack of progress. Feel free to open a new one if interest resurfaces.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210914001647413 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210914001647413 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.643%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26408

Relevant Lines:
57436

💛  - Coveralls


A QUESTION FROM THE DEPLOYED THAT SEEMS TO NOT BE WORKING.

Previously when I visited the deployment it used to send an stk push to my phone requesting me to send 1 bob to you :)
My question is , does mpesa api support customer to customer transactions. If yes , how .

I'll update it 👍.

Previously when I visited the deployment it used to send an stk push to my phone requesting me to send 1 bob to you :)
My question is , does mpesa api support customer to customer transactions. If yes , how .

Customer to customer payments are not yet supported via Daraja for now.


How can add participitant as listner

in documentation there is listen() method to add participitant as listner but this is not present in sdk only join is there so how can i join as a listner?

Thank you @asadumair for your question, we also have received your support request. Are you targeting React Native or Cordova?
The React Native SDK has a listen function.
The Cordova plugin is what we call a UXKit, it is a fully ready to go application (not an SDK) and it does not have the listen capability.


Knockout Observables

http://live.bridge.net/#c4565dcbc66e8b4a7bc7
I am trying to get the outputted JS to match how Knockout.js is used normally.
[Name("")]
public string GetValue() {
    return "";
}

this should convert to someproperty();  instead it is outputted with an extra dot i.e. someproperty.();

refernce https://github.com/maverix/ScriptSharpKnockout/blob/master/src/Observable.cs

encase my first comment wasn't clear.
someproperty.GetValue();  should be represented in javascript as someproperty();
of course, I might be stuck in the ScriptSharp way of doing things and there might be an entirely different way of representing a Knockout observable which is essentially a Function with Properties and Methods attached to it (JS is a crazy dynamic language)

Not sure if clear understood you but do you need such code?
http://live.bridge.net/#0ee1452f3b1c2a1530fa
I mean to use [Template("{this}()")] for GetValue instead Name attribute

Perfect. I was hoping for something in the template attribute, but couldn't find the magic string

http://live.bridge.net/#cb089aa55fdeb2748a28
Yep looks good.  Thanks!


Mention mailing list and maintenance status

We look for developers who would like to join or take over maintenance of this code.

Looks good. Thanks!


WebXR HitTestSource fix

PR #5778 introduced a bug where the absence of hit test results would still provide a callback with the null result at the position of the controller.
Fixes #5884
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Thank you @slimbuck, I did a typo there. Should work well not: gaze based hit test works well, screen input sources too, and controller hit tests. Tested on Android phone and Quest 3.

Thanks @Maksims , but how about?:

Model-viewer is still not receiving hit results for touchscreen because of this line. Looks like the inputSource isn't being added to hitTestSourcesSet when using xr.hitTest.start().

Thanks @Maksims , but how about?:

Model-viewer is still not receiving hit results for touchscreen because of this line. Looks like the inputSource isn't being added to hitTestSourcesSet when using xr.hitTest.start().

I have tested Android and Quest 3 from examples, they work as intended. Will re-check again then.

Thanks Maks. I just tested with your latest changes and the following callback is still never invoked:
// register for touchscreen hit test
xr.hitTest.start({
    profile: 'generic-touchscreen',
    entityTypes: [XRTRACKABLE_POINT, XRTRACKABLE_PLANE, XRTRACKABLE_MESH],
    callback: (err: Error | null, hitTestSource: XrHitTestSource) => {
        ...
    }
});

Ok, now it should work well with profiles provided.
But bear in mind: when using profile that will cover multiple input sources (multiple controllers of the same profile (left/right), multi-touch, etc), it will trigger result for each of those input sources.
Best would be to listen for added/removed input sources, and while there is added input source of required profile, start hit test for it, and ignore any other input sources until that active one is removed. That way in multi-touch scenario any concurrent taps will not lead to overtaking hit test results.

Hi @Maksims,
I can confirm this works with model-viewer - thanks!
I am just wondering about your last comment. If I start hitTest using profile generic-touchscreen, won't I only get callbacks from touchscreen devices? (And devices presumably only have a single touchscreen so this isn't an issue?).

I am just wondering about your last comment. If I start hitTest using profile generic-touchscreen, won't I only get callbacks from touchscreen devices? (And devices presumably only have a single touchscreen so this isn't an issue?).

Indeed, it will only cover touchscreen devices.
Just for a model-viewer, the problem is that:

Single tap screen
Get a callback
Without releasing start moving tap around
Then add another tap
You now have multi-touch scenario, and result callbacks will be fired for both.

So if you don't use XrInputSource.id to know which tap started, then moved and finished. Then you will start using hit test result from another tap.
That is why it is recommended to use explicit hit test on the input source, that way you know when to start listening for results, for which particular input source, and so on.
This is not related to this PR.

BTW is it possible to perform a hitTest with a screen-space pixel offset? Currently we perform hitTest directly under the finger always, but we'd like to perform a hitTest at, say, touch-position + vec2(40, 20) pixels. Is this currently possible?

BTW is it possible to perform a hitTest with a screen-space pixel offset? Currently we perform hitTest directly under the finger always, but we'd like to perform a hitTest at, say, touch-position + vec2(40, 20) pixels. Is this currently possible?

There is a way to provide XRRay for ray offset, but it has not been exposed through integration. It would be a separate PR.

Yep of course, created https://github.com/playcanvas/engine/issues/5927 to track.

@slimbuck Is this mergeable now?

Yes! Approved


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 6.3.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Debug selected tests does not stop at breakpoint

Hi,
Version: NTVS for VS 2015 29-Apr.
The issue outline here https://nodejstools.codeplex.com/workitem/801 has resurfaced in the latest build.
I tried rolling back, but the 03-Mar version is also failing with the same problem on VS 2015 RC.

Same as #79?

Yes, it is, thanks.


Finish New Autocomplete Input

-DUPLICATE- will be done by @harshitsan in a parallel task
Finish the integration of the new Plan search bar component from this PR:
https://github.com/meirim-org/meirim/pull/429
Remaining tasks:

[ ] Make component sticky.
[ ]  Close the loop on filter by status (align with the api IN_PROGRESS/ APPROVED status).
[ ] Use the new component (instead of the current one) in Plans.jsx:

Blocked by #468

closing due to design change


`Give title of project “My git practical”

Please create index.html file and add h1 tag with “My git practical` and
description

Issue solved


webassemblyhub.io should not allow email-formatted usernames

Describe the bug

webassemblyhub.io provided me with an invalid email-formatted username as the default in its signup form.
That default username caused my initial wasme build operation to fail.

To Reproduce

When creating an account at https://webassemblyhub.io , on the signup form I was presented with a username and email that matched by work email address.  I accepted those defaults and my account was established with an email-formatted username.
Working through the Getting Started guide, my wasm build action failed with an Error: invalid reference format error.  Establishing a different account with a non-email-formatted username succeeded.

% wasme build assemblyscript -t webassemblyhub.io/jim.barton@solo.io/add-header:v0.1 .
Building with npm...skipping login
running npm install && npm run asbuild
npm WARN workspace No description
npm WARN workspace No repository field.
npm WARN workspace No license field.

audited 5 packages in 0.467s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities

> @ asbuild /src/workspace
> npm run asbuild:untouched && npm run asbuild:optimized

> @ asbuild:untouched /src/workspace
> asc assembly/index.ts -b build/untouched.wasm --use abort=abort_proc_exit -t build/untouched.wat --validate --sourceMap --debug

> @ asbuild:optimized /src/workspace
> asc assembly/index.ts -b build/optimized.wasm --use abort=abort_proc_exit -t build/optimized.wat --validate --sourceMap --optimize

INFO[0009] adding image to cache...                      filter file=/tmp/wasme372924219/filter.wasm tag="webassemblyhub.io/jim.barton@solo.io/add-header:v0.1"
Error: invalid reference format
Usage:
  wasme build assemblyscript SOURCE_DIRECTORY [-b <bazel target>] -t <name:tag> [flags]

Flags:
  -e, --email string      Email for logging in to NPM before running npm install. Optional
  -h, --help              help for assemblyscript
  -p, --password string   Password for logging in to NPM before running npm install. Optional
  -u, --username string   Username for logging in to NPM before running npm install. Optional

Global Flags:
  -c, --config string    The path to the filter configuration file for the image. If not specified, defaults to <SOURCE_DIRECTOR>/runtime-config.json. This file must be present in order to build the image.
  -i, --image string     Name of the docker image containing the Bazel run instructions. Modify to run a custom builder image (default "quay.io/solo-io/ee-builder:0.0.32")
      --store string     Set the path to the local storage directory for wasm images. Defaults to $HOME/.wasme/store
  -t, --tag string       The image ref with which to tag this image. Specified in the format <name:tag>. Required
      --tmp-dir string   Directory for storing temporary files during build. Defaults to /tmp on OSx and Linux. If unset, temporary files will be removed after build
  -v, --verbose          verbose output

Expected behavior

An invalid email-formatted username should not have been the default choice.
An invalid email-formatted username should not have been accepted to create the account.

Related to (although not a duplicate of) - https://github.com/solo-io/wasm/issues/137 - These two should probably be tackled together.

Related to (although not a duplicate of) - https://github.com/solo-io/wasm/issues/137 - These two should probably be tackled together.


feat(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1561

Questions ?
Please refer to the Backport tool documentation


[Firefox] [UI] Add Contributors Modal: Contributor permissions dropdown entire words not shown

Steps using Firefox browser:

Go to a project you have admin access on
Click to go to the sharing tab
Click to Add a new contributor
Enter a name to get a contributor list
Select one of the users in the list by clicking the + sign
In the Permission dropdown toggle to select 'administrator' and 'read+write'

Expected
I would expect the entire word to show in the dropdown selector like it does on other browsers

Actual
On Firefox, the words are cut off

I can work on this one! Thanks!

The PR has been merged. So this issue could be closed now.

Got it - Thanks


Drop-In "Card Number" field with Android FireFox 34.0

Steeps to reproduce:

Enter “Card Number” value
Try to change digits and entered value will be selected

It is not possible to change separate digits. The only option is to delete CC number and retype it.

@CheapData as mentioned in #8, this has been addressed in v2.5.3

The same functionality persists in v2.5.3. I gues it is more likely FireFox for Android native behavier than a bug.


Update protocols-in-tls-ssl--schannel-ssp-.md

@wqweto : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Adding @jess-krynitsky for review.

Thanks @jess-krynitsky and @wqweto ! I've merged the changes and they should be live soon.


Cannot instantiate avif wasm module manually

When darting through the code recently I think I observed a potential bug that would stop people from manually instantiating a wasm module. People using this in a CloudFlare Worker would likely be impacted.
https://github.com/jamsinclair/jSquash/blob/f76973eaec7803b79738c3a9cece15489e6a721e/packages/avif/encode.ts#L28-L31
Notice we never set the emscriptenModule with the passed module. This would prevent us from storing this module in memory.

Fixed by 7b7dc50e2ef178ddcc92fd22a56df939798548df


Questions about developing an operator that responds to as many Kubernetes versions as possible.

Type of question

Best practices
General operator-related help
Question
What did you do?
Hello.
There is an operator I developed based on the operator-sdk v0.17.2 version.
Based on this project, in other Kubernetes versions, the crd generated output is not correct, so I am thinking about creating a project for each Kubernetes version.
People who have had CRD problems have had other issue as well.
So I checked the docs and saw a guide saying that the operator-sdk version and the kubernetes version match.
So, to check which Kubernetes version operator-sdk is fully compatible with, I download the binary linked to the github release menu and run the operator-sdk version command. Can I judge the version by ?
$ ls -al
total 554496
drwxr-xr-x  2 root root     4096  3월  2 09:46 .
drwxr-xr-x 11 root root     4096  6월 24  2021 ..
-rwxrwxrwx  1 root root 89473879  5월 12  2021 argocd
lrwxrwxrwx  1 root root       22  5월 18  2021 GitAhead -> /opt/GitAhead/GitAhead
-rwxr-xr-x  1 root root 45113344  9월  9 14:34 helm3
-rwxrwxrwx  1 root root 32138779  8월 27  2021 kubebuilder
-rwxrwxrwx  1 root root 48541136  5월 14  2021 kubectl-argo-rollouts
lrwxrwxrwx  1 root root       35  4월 29  2021 libreoffice7.1 -> /opt/libreoffice7.1/program/soffice
lrwxrwxrwx  1 root root       35  2월 28 16:18 operator-sdk -> /usr/local/bin/operator-sdk-v0.19.4
-rwxr-xr-x  1 root root 69896879  8월 30  2021 operator-sdk-v0.17.2
-rwxr-xr-x  1 root root 76794439  2월 28 11:49 operator-sdk-v0.19.4
-rwxr-xr-x  1 root root 68108655  3월  2 09:28 operator-sdk-v1.4.0
-rwxr-xr-x  1 root root 68108368  3월  2 09:28 operator-sdk-v1.4.2
-rwxr-xr-x  1 root root 69589068  3월  2 09:26 operator-sdk-v1.9.2
$  operator-sdk-v0.17.2 version
operator-sdk version: "v0.17.2", commit: "0258db0119e8e18e15d035532427c329fce1e871", kubernetes version: "unknown", go version: "go1.13.10 linux/amd64"
$  operator-sdk-v0.19.4 version
operator-sdk version: "v0.19.4", commit: "125d0dfcc71fef4f9d7e2a42b1354cb79ffdee03", kubernetes version: "v1.18.2", go version: "go1.13.15 linux/amd64"
$  operator-sdk-v1.4.0 version
operator-sdk version: "v1.4.0", commit: "67f9c8b888887d18cd38bb6fd85cf3cf5b94fd99", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"
$  operator-sdk-v1.4.2 version
operator-sdk version: "v1.4.2", commit: "4b083393be65589358b3e0416573df04f4ae8d9b", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"
$ operator-sdk-v1.9.2 version
operator-sdk version: "v1.9.2", commit: "319e77f2fff57c6c862bddd64ecf9c562f2d2161", kubernetes version: "1.20.2", go version: "go1.16.6", GOOS: "linux", GOARCH: "amd64"

I want to install and test the operator I developed from version 1.17 to the most recent version of Kubernetes.
Please note that this inquiry is the result of processing with Google Translate.
What did you expect to see?

What did you see instead? Under which circumstances?
Environment
Operator type:

Kubernetes cluster type:

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Additional context

Hi @smartkuk,
The versions of k8s deps used in the CLI or scaffolded by it is not exactly what will drive the supportability statement of your Operator.
Note that k8s API has some API removals, see: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
Then, for example, if your Operator is using APIs which were removed in the K8s version 1.22 that means that your project will not work on this one and upper versions. So, let's use the CRD API as an example:
If your project is using the API v1 for the CRDs then, your project can work on from k8s versions 1.16. However, you will be unable to make a project mainly integrated with OLM that works in versions < 1.16 and upper or equals 1.22 (Openshft 4.9).
You might be able to support more versions if you try to create logics that will work accordingly with the cluster versions, or better, the APIs available on the cluster. See: Why not couple an Operator's logic to a specific Kubernetes platform?
If your project is integrated with OLM (If you are distributing your project via OperatorHub.io, Openshift, etc):
OLM will try to apply the CRDs to initialized the Operator.  Note that the API v1 for CRDs was introduced with the k8s version 1.16 and in its release 1.22, the v1beta1 was removed. Then, technically it is not achievable to build a bundle that supports
both Kubernetes versions e.g 1.22 and 1.15 in this case.
However, if you publish new versions where they have any logic to create resources on runtime according to cluster apis that would be possible and work with OLM assuming that:
a) All manifests shipped on the bundle does not use the removed APIs  (it might only work for specific scenarios where you create the resources via the code and they are resources that are not used to initialize the solutions such as the CRD)
b) Your distribution must be workable on the previous and upper versions where your solution will be distributed
If you are distributing your solution via Openshift Catalogs such as RedHat Community
We also recommend, for those who would like to still ship bundles that use these removed APIs on 1.22/OCP 4.9:
a) Configure the OCP version where the bundle should be shipped accordingly by using OCP Labels. It should have a range that does not contain 4.9 and upper versions.
b) Add the max OCP version annotation = 4.8 to not allow the Operator users to upgrade their cluster from 4.8 to 4.9 with a version installed that does not work on 4.9+.
c) Create two bundles versions where one can only be shipped to be published on OCP versions < 4.9 and another one that does not use these APIs targeting the OCP upper versions >= 4.9.
For further information see: https://docs.openshift.com/container-platform/4.8/operators/operator_sdk/osdk-working-bundle-images.html#osdk-control-compat_osdk-working-bundle-images
However, it is important to highlight that all OCP/OLM versions which are actually supported would work with the upper versions of these APIs. (See that OCP 4.4 is no longer supported at all)

Hi @smartkuk,
It shows that further and detailed information was provided above already. So, I am closing this one as sorted out. However, please, feel free to re-open or raise new issues as you see fit.


Webhooks Implementation: Seamless Integration and Real-Time Performance

We have implemented webhooks in our project, allowing for real-time updates and seamless integration. Explore how this feature enhances our system's efficiency.

Can u give some guidelines for create web hooks ?

Please follow the below steps to start with Webhook create
Steps:-
step 1 : login into admin spurt_cms
step 2 :Go to Webhook tab
step 3 : Now Explore your Webhook feature


All intents are returned as endConversation: true

Minor thing, but it appears that for whatever reason, all tests are evaluating to endConversation: true despite the implementation of the particular intent in DialogFlow.  I tried turning on/off the "set this intent as end of conversation," but in either the tests are always expecting endConversation: true to achieve a passing result.

@zerowon01 Hmm... I have a question. Which is your situation?

The Dialogflow your project always returns a value as endConversation: true. Therefore, if you define each test-case with endConversation: false, but the test-case is failed.
The Dialogflow your project returns a value as 'endConversation: false'. However, all test-cases for this tool have a definition as endConversation: true. Therefore, some test-cases are failed.

@zerowon01 Ok, I understand your situation. I will investigate the cause, just a moment. Thank you for the reporting.

@zerowon01 Hmm... I can't reproduce the issue you reported. Could you send me your yaml file and the output log? At this time, you can include more detail information with -d option at running this tool.

Git didn't allow yaml or yml so I renamed it with txt extension.
This is the test file that I'm currently working on. As you will see ALL of my test definitions include endConversation: true. Otherwise they fail to test as expected (endConversation: false). I'm using v1 of the DialogFlow API if that makes any differnce...
test.txt

Test evaluation returned: "Expected: false \n Actual: true"

At least, the Actual: true means that the Dialogflow returned the following response:
"expect_user_response": false,

That is, your mention "My agent: has (0) intents where endConversation: true" is not correct, I think. For example, you select the "end conversation" checkbox on the Dialogflow intent form, but the Dialogflow returns "expect_user_response": false, if you use app.tell() function in your fulfillment logic.
@zerowon01 I will be able to know the behavior under your situation by your yaml file and the output log.

@zerowon01 Oh, sorry. I have a mistake. Is your issue the following, right?

You defined some test-cases with endConversation: true.
You ran the tests, but these test-cases output the log Expected: false, for endConversation checking. The correct behavior is Expected: true, .

@zerowon01 I found an issue in your file. I guess that you defined two test cases of "#Default fallback intent?" and "#Who are you?". However, the definition has only one test case, because there is not - character before the 2nd condition:. In YAML, each item in an array must start - character.

I'm saying the problem is that any test I write I MUST use endConversation: true to pass, despite the actual value in DialogFlow. Maybe I should put in an API reply snippet (I suppose DialogFlow could be "broken.").. API output added below. (While doing that I noticed there is no mention of endConversation in the API response..... Perhaps I'm not understanding something here in the DialogFlow spec...?)
Anyway, if I assume that the test code works correctly, this would mean that all my intents ARE in fact defined as endConversation: true. I know this is NOT true. So my assumption is that the test code is malfunctioning in some way so it APPEARS that my defined intents are defined as endConversation: true.
API reply for my Default Fallback Intent:
{     "id": "xxxxxxxxxxx",     "name": "Default Welcome Intent",     "auto": true,     "contexts": [],     "responses": [         {             "resetContexts": false,             "action": "input.welcome",             "affectedContexts": [],             "parameters": [],             "messages": [                 {                     "type": 0,                     "speech": [                         "Hi!",                         "Hello!",                         "Good day!",                         "Greetings!"                     ]                 }             ],             "defaultResponsePlatforms": {},             "speech": []         }     ],     "priority": 500000,     "webhookUsed": false,     "webhookForSlotFilling": false,     "fallbackIntent": false,     "events": [         {             "name": "WELCOME"         }     ],     "userSays": [],     "followUpIntents": [],     "templates": [] }

@zerowon01 Sorry, this issue is about endConversion, but it is YAML format, I think. Please see https://github.com/yoichiro/dialogflow-query-checker/issues/19#issuecomment-370305019. And, I just updated the sample code in the README.md file. Could you check your configuration YAML file?

@yoichiro Fixing the YAML syntax did solve  #21. However the endConversation: true issue in this ticket, is still being observed.
For this issue, the test results are VERY explicit. Expected: false, Actual: true. Despite my intent very clearly being of the condition "endConversation: false" per the DialogFlow console.

@zerowon01 Hmm... Ok, give me a few hours to further investigate this issue.

@yoichiro Thanks in advance.

@zerowon01 Finally, I could reproduce your situation on my environment. I will fix this issue. I'm sorry for my confused comments.

@zerowon01 I have just released a new version 1.11.1 https://github.com/yoichiro/dialogflow-query-checker/releases/tag/1.11.1 including a code to fix this issue. Could you test your yaml file using this version?

@zerowon01 I cannot access your Dialogflow agent, therefore, I cannot understand the details. You can output the detail log with -d option. For example, dialogflow-query-checker run -d ./foo.yml. I may know your situation, if you send me the log output.

@yoichiro, please find below:
Here is the condition/expect pair
  condition:
    query: "Let's stop talking about this topic now"
  expect:
    action: "misc.end.conversation"
    intentName: "misc.end.conversation"
    speeches:
      - "Yeah, I've got better things to do anyway."
    endConversation: true

Here is the debugging output as requested:
The debug mode is on
The count of retrying: 0
Running query tests for Dialogflow.
[Start] Query: Let's stop talking about this topic now
 {
"lang": "en",
"originalRequest": {
"source": "google",
"data": {
"user": {
"locale": "en-US"
}
}
},
"query": "Let's stop talking about this topic now",
"event": {},
"sessionId": "03104e56-3e46-4a32-9bda-4e0a175d57a4"
}
 200 OK
 {
"id": "097a3b6d-137c-4171-81ac-1cf05759f5c3",
"timestamp": "2018-03-05T07:39:09.286Z",
"lang": "en",
"result": {
"source": "agent",
"resolvedQuery": "Let's stop talking about this topic now",
"action": "misc.end.conversation",
"actionIncomplete": false,
"parameters": {},
"contexts": [],
"metadata": {
"intentId": "6f6ed5a4-5147-4b7a-a2fe-1c82531aac14",
"webhookUsed": "false",
"webhookForSlotFillingUsed": "false",
"endConversation": true,
"intentName": "misc.end.conversation"
},
"fulfillment": {
"speech": "Yeah, I've got better things to do anyway....",
"messages": [
{
"type": 0,
"speech": "Yeah, I've got better things to do anyway...."
}
]
},
"score": 0.7699999809265137
},
"status": {
"code": 200,
"errorType": "success",
"webhookTimedOut": false
},
"sessionId": "03104e56-3e46-4a32-9bda-4e0a175d57a4"
}
....F

@zerowon01 Thank you for posting your log. As the result, I just notice that it is hard to fix this issue. At least, I don't have any good idea to fix this.
In this current version, this tool checks whether the conversation was ended by "data.google. expectUserResponse" response value. As my testing, when a fulfillment was used, the expectUserResponse value was returned. However, when a fulfillment was not used (that is, the dialogflow returned the result directly), the expectUserResponse value was NOT returned. I guess that your situation is the 2nd. This means that this tool cannot recognize whether the conversation is ended or not.
Probably, this reason may be that this tool cannot emulate a request as same as AoG, I guess. That is, I need to find an idea that the Dialogflow always returns the expectUserResponse value.

@zerowon01 Anyway, I will release a new version which the endConversation checking is disabled.

@yoichiro Yeah, I believe the endConversation logic is specific to the Google Assistant / Actions on Google implementation. Anyway, for my case, being able to circumvent the check is perfect, as it's not something I would really test for. Thanks again for your effort.

I have just released the new version 1.12.0 which the endConversation check feature deleted: https://github.com/yoichiro/dialogflow-query-checker/releases/tag/1.12.0
@zerowon01 Thank you for the great reporting! I close this issue.


⚠ Secret Website 3 has degraded performance

In 0d9239a, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2092 ms

Resolved: Secret Website 3 performance has improved in e1fa9ae.


Meetings not displaying in visitor's timezone

Thanks heaps for the hard work on tsml-ui. It looks perfect for our use case (an Australia wide meeting list for DA).
I saw that https://github.com/code4recovery/tsml-ui/issues/93 was closed but it doesn't seem to work the way I'd expect.
I've configured tsml-ui to use Sydney time but it still shows Perth meetings in Perth time.

If I click on the Perth meeting, it shows both timezones but in a confusing way. No-one in Australia would understand what GMT+8 vs GMT+10 means.

Steps to replicate:

Here is my spreadsheet: https://docs.google.com/spreadsheets/d/1YRpUph8Xfw-hX-2IegFx_S4YQUprFTqLPYxfL42Pb98/edit#gid=0

oops yes there was a bug here when data-timezone is specified - it was not normalizing other timezones to that zone. i would still remove data-timezone for your use-case but the bug should be fixed now


Integrate with Hawkular

Metrics are good.  Akin to Logstash integration I reckon.

https://wildfly-swarm.gitbooks.io/wildfly-swarm-users-guide/content/hawkular.html


[WIP][Consensus] Leader Election - Round Robin (secondary)

Objective
Implement a secondary, round-robin leader election mechanism to be used when the primary VRF sortition with CDF fails to produce a value. This ensures that the consensus process continues even when the primary leader election method fails.
Origin Document
Primary Leader Election
V0 References:

Implementation: https://github.com/pokt-network/tendermint/blob/746fd7abc65ee1c019c8196cd878ff4b12aff5ba/types/validator_set.go#L86
Test: https://github.com/pokt-network/tendermint/blob/746fd7abc65ee1c019c8196cd878ff4b12aff5ba/types/validator_set_test.go#L138

V1 References:

https://github.com/pokt-network/pocket/tree/main/consensus/leader_election

Goals

Implement a fallback round-robin leader election mechanism that will be used when the primary VRF sortition with CDF fails.
Integrate the round-robin leader election into the existing consensus process seamlessly.

Deliverable

[ ] Design and implement the round-robin leader election mechanism
[ ] Modify the existing consensus process to use the round-robin leader election when the primary VRF sortition with CDF fails

Non-goals / Non-deliverables

Modifying the primary VRF sortition with CDF leader election process
Making round-robin the primary leader election mechanism

General issue deliverables

[ ] Update the appropriate CHANGELOG
[ ] Update any relevant READMEs (local and/or global)
[ ] Update any relevant global documentation & references
[ ] If applicable, update the source code tree explanation
[ ] If applicable, add or update a state, sequence or flowchart diagram using mermaid

Testing Methodology

[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @jessicadaugherty

This one is a little light as I couldn't find the code for reference in pocket core but ptal when you have a chance @Olshansk

This one is a little light as I couldn't find the code for reference in pocket core but ptal when you have a chance @Olshansk

Added


Remove references to operating system specific packages

The page at http://www.dita-ot.org/download implies that there is one version (=download) of DITA-OT for Windows and another one for MacOS/Linux. This is not the case; when unpacked, the downloads are identical, the only difference is that one download is a zip-file, while the other is a tar.gz file.
I suggest to remove the references to the operating systems and just provide download links to the client package, maybe as simple as this:

DITA-OT2.0_client_bin.zip [30.8MB]
DITA-OT2.0_client_bin.tar.gz [29.7MB]

The .tar.gz & .zip variants will be retained for 2.1 per discussion in dita-ot/dita-ot#1914.


Model v1.6-mistral-7b --load4bit

Describe the issue
Hello,
I am currently using model v1.6-mistral-7b with 4-bit quantization. I am getting this warning and I was wondering whether i shoudl take care of it or it is not relevant.
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.self_attn.v_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.self_attn.q_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.self_attn.q_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.self_attn.out_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.self_attn.out_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.layer_norm1.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.layer_norm1.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.mlp.fc1.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.mlp.fc1.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.mlp.fc2.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.mlp.fc2.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.layer_norm2.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.10.layer_norm2.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.k_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.k_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.v_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.v_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.q_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.q_proj.bias: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)
2024-04-10 15:03:09 | ERROR | stderr |   warnings.warn(f'for {key}: copying from a non-meta parameter in the checkpoint to a meta '
2024-04-10 15:03:09 | ERROR | stderr | /home/samuele/anaconda3/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py:2025: UserWarning: for vision_model.encoder.layers.11.self_attn.out_proj.weight: copying from a non-meta parameter in the checkpoint to a meta parameter in the current model, which is a no-op. (Did you mean to pass `assign=True` to assign items in the state dictionary to their corresponding key in the module instead of copying them in place?)

I get it several times actually, not only the ones reported here.
Thank you for your help :)

same here, any ideas?

me too. Can anyone help?


[ErrorCodes] errorutil output files in sync with codes updated by the utility

Description
This PR fixes #74
Notes for Reviewers

In case of update, an analysis/validation is performed after the update, (the equivalent of running analyze), meaning that there are 2 passes through the code.
The output files reflect now the state of the code after error codes have been updated.
An error is be issued if next_error_code is not greater than the highest code in the code.

Signed commits

[x] Yes, I signed my commits.

Hey @mgfeller This looks good to me. But I have question like from now on all the three JSON files and the component_info.json with go under the helpers directory and that means that we have update all the makefile to go run github.com/layer5io/meshkit/cmd/errorutil -d . update -i ./helpers -o ./helpers

Thanks @sayantan1413 to answer your question: it appears so, I didn't take part in that discussion / decision.


Make the documentation reproducible.

Whilst working on the Reproducible Builds effort [0], we noticed
that python-testfixtures could not be built reproducibly.
[0] https://reproducible-builds.org/
This issue was originally filed in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853912

Coverage remained the same at 99.977% when pulling 0d088220bd89683cdc55b7982b215d99fad929d6 on lamby:reproducible-build into 355de4f03ef5c8ba5313df72d9b1929eb0884107 on Simplistix:master.

Do you need a release for this?

Do you need a release for this?

Preferably, yes.

https://github.com/Simplistix/testfixtures/tree/4.13.4 released with your changes.

Thank you @cjw296


Revisit double-negative command line options (e.g. -disable_fast_concat)

See https://github.com/bigdatagenomics/adam/pull/1479#issuecomment-296806121

Closing as WontFix


Generate documentation for the SwiftSyntaxMacroExpansion module on swiftpackageindex.com

This module was missing from .spi.yml
This will be caught by the check from https://github.com/apple/swift-syntax/pull/1635 once the CI nodes have been updated so that we can use Swift regex on them.

@swift-ci Please test


What happens if the Rails cache store is set to :file_store?

http://guides.rubyonrails.org/caching_with_rails.html#activesupport-cache-filestore
Will Rack Attack still work then? Or should I then set Rack::Attack.cache.store to something else that's memory backed?

Using FileStore means that the cache is local to each server rather than shared. As a result, rack-attack may appear to work fine for a single server, but won't accurately enforce throttle limits with multiple servers.


Set up continuous integration

Docker and Travis-CI, similar to https://github.com/alexanderzimmerman/nsb-pcm

Complete as of commit 499a487d6049665e433588ced41ef295a11c3b3d


Unable to test React with Material-UI Hidden element

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I raised this as an issue in the Enzyme GitHub here: https://github.com/airbnb/enzyme/issues/2179
The issue contains detailed information of the bug but please let me know if you want me to transcribe that information in here as well. They believe the issue might be due to either some breaking change in MaterialUI or JSDom.
I am hoping that someone here can take a quick look at the issue I raised there and give any guidance as to where or not it might be an issue with the MaterialUI library or not.

https://github.com/airbnb/enzyme/issues/2179#issuecomment-529320192 is interesting. Not sure if this is the recommended approach to getting this initialWidth in the material UI context? A mechanism like this would also be useful for setting this initial width based on client hints in a serverside rendered app.

We cover this topic in https://material-ui.com/components/use-media-query/#testing. See https://github.com/mui-org/material-ui/issues/16073#issuecomment-502359758


Added some data to image object types.

Hi, as described here: #2554
Objects of type image now include size and flipped state data.

Lovely, thanks.


cleanup: various source code comment corrections

Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

@Madhu-1 one more small change in the last commit. ptal

/retest all

/retest  ci/centos/mini-e2e/k8s-1.19

/retest ci/centos/mini-e2e/k8s-1.20

/retest ci/centos/mini-e2e-helm/k8s-1.19

/retest ci/centos/mini-e2e-helm/k8s-1.20

/retest ci/centos/mini-e2e/k8s-1.19

/retest ci/centos/mini-e2e-helm/k8s-1.19

@Madhu-1 can we add ready-to-merge label here?


Explicitly configure memcached user

This is a "fix" for https://github.com/weaveworks/flux/issues/2106 by getting more explicit with the memcached container securityContext and also while there adding some sensible defaults and dissalowing privilege escalation.
As I found some discrepancies with the uid/gid between versions of memcached, it appears as though there was some work in the later versions to settle on the well known value of 11211 (https://github.com/docker-library/memcached/pull/41) so I upgraded to the latest version which so far appears to be working fine.
While this fix is probably not required it ties in with my work of running as non-root and getting explicit about the users running containers and removing capabilities that are not required.

Looks reasonable to me! @stefanprodan, one for you when you are back :palm_tree:


Update Contour Version

Contour is going to cut a new release as soon as Gateway API releases v1beta1/v0.5.0. In the mean time, updating to a recent commit on main for now to start running tests and fixing issues/updating tests.
For more context, see this bit of discussion:
update to Gateway API v0.5.0/v1beta1 · Issue #4560 · projectcontour/contour

Done.


Go 1.10 Support

Thank you so much for this project!
I'd like to request support for Go 1.10, which was released recently.
There have also been a couple patch releases to 1.8 and 1.9, latest of those releases are 1.8.7 and 1.9.4.

Hi! Thanks for letting us know about this. It's not easy to track new releases of as many compilers as we have. I'll add them today, and if everything goes well, they should hit the live site later in the day :)

Ok, so I've added the new versions. They should hit the site in a bit. Thanks again for the heads up! :)


Output window doesn't scroll with certain editor scale settings

Godot version
v4.2.dev5.official [e3e2528ba]
System information
Godot v4.2.dev5 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 970 (NVIDIA; <IP_ADDRESS>23) - Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 Threads)
Issue description
#79975 closed his issue too early, it's a separate issue to #78434.
I'll just repost his same gif:

Steps to reproduce
I had a theory it was related to editor settings and I tracked it down:

Editor -> Display Scale = Custom
Editor -> Custom Display Scale = 1.15
Click Save & Restart
Print stuff

var number := 0
func _process(delta: float) -> void:
	number += 1
	print(number)

The scale number matters, 1.1 seems to be fine but smaller decimal places such as 1.15 are what cause the issue.
Minimal reproduction project
printbug.zip

CC @bruvzg

@Swarkin Can you test https://github.com/godotengine/godot/pull/82079

@Calinou the artifacts are expired sadly and dont have the time to compile right now
The editor is maximized and im using normal scale (100%) both editor and OS.
I have 2 screens (secondary 4k 60hz / main 2560x1440 144hz), using the main one.
v4.2.rc1.official - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon RX 6700 XT (Advanced Micro Devices, Inc.; 31.0.22023.1014) - Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (6 Threads)

Re-running so artifacts will be available

That build seems to fix the issue


experimental: extend and improve various places

This commit improves the logic by:

Identifying language of target project, to make language specific
prompts
Adds context to the prompts based on cross-references, source code and
extended typing
Adds two new prompts for C
Adds an addition harness run for each auto-gen harness with
detect_leaks=0. This is to get idea of how well a harness performs
in the event it runs into a leak fast.
Saves the introspector reports used per analysis. This is important
for development purposes to make it easy to track what the prompts
used.
Saves the prompts generated per auto-gen harness.

This code is not tested in the CI so will skip trial runs

/gcbrun skip