Someone hacked my persnol data

Someone hacked my all my persnal information my own personal delete  my all Gmail account to my old Samsung account to my Google Drive belt on my Google photos my other social media account to my all Personal Care Service Canada account someone hacked please help me protect me

The motherfuker someone hack my old personal data my all personal information had hack

Someone I have my own personal information my old personal data on my old Gmail all around my Samsung all account my Google Drive data AND YouTube channel personal URL number And My all domain name,s and my someone create my IP address the Wikipedia website helping so my all data hacking so that’s why please help me name IP address and my only Internet IP address my domain name my personal you are a number my TV my LED my YouTube ALL channel where the heck March 20, 2020 every day I can face on this happen so help me protect me please

Someone I have my own personal information my old personal data on my old Gmail all around my Samsung all account my Google Drive data AND YouTube channel personal URL number And My all domain name,s and my someone create my IP address the Wikipedia website helping so my all data hacking so that’s why please help me name IP address and my only Internet IP address my domain name my personal you are a number my TV my LED my YouTube ALL channel where the heck March 20, 2020 every day I can face on this happen so help me protect me please

Someone I have my own personal information my old personal data on my old Gmail all around my Samsung all account my Google Drive data AND YouTube channel personal URL number And My all domain name,s and my someone create my IP address the Wikipedia website helping so my all data hacking so that’s why please help me name IP address and my only Internet IP address my domain name my personal you are a number my TV my LED my YouTube ALL channel where the heck March 20, 2020 every day I can face on this happen so help me protect me please

Someone I have my own personal information my old personal data on my old Gmail all around my Samsung all account my Google Drive data AND YouTube channel personal URL number And My all domain name,s and my someone create my IP address the Wikipedia website helping so my all data hacking so that’s why please help me name IP address and my only Internet IP address my domain name my personal you are a number my TV my LED my YouTube ALL channel where the heck March 20, 2020 every day I can face on this happen so help me protect me please

Someone I have my own personal information my old personal data on my old Gmail all around my Samsung all account my Google Drive data AND YouTube channel personal URL number And My all domain name,s and my someone create my IP address the Wikipedia website helping so my all data hacking so that’s why please help me name IP address and my only Internet IP address my domain name my personal you are a number my TV my LED my YouTube ALL channel where the heck March 20, 2020 every day I can face on this happen so help me protect me please


Cannot link to existing and new entity of same domain type in a spreadsheet at the same time

Scoped out from ebi-ait/dcp-ingest-central#712
Steps to replicate:

Create 2 spreadsheets.

spreadsheet 1 should contains:

donor 1 ->  specimen 1 (linked via collection protocol 1)
specimen 1 -> cell suspension  1(linked via dissoc protocol 1 and enrichment protocol 1)
cell suspension 1 -> 2 files (linked via sequencing protocol 1, lib prep protocol 1)

spreadsheet 2 contains:

new donor 2
specimen 2 linked to donor 1  and donor 2 via collection protocol 1

Upload the first spreadsheet, upload files, validate graph and submit to HCA.
Upload the second spreadsheet, upload files and validate the graph.

Actual Behavior:
The specimen is linked to donor 1 only
Expected Behavior:
The specimen 2 should be linked to donor 1  and donor 2 and the linking process should be linked to collection protocol 1 in Ingest database
Workaround: Do linking via UI

This is now in staging, @idazucchi would you be able to verify this in staging? Thanks!

I tested this with submission ticket280_test_case2 in staging
In one process I can link:

existing and new biomaterials
existing and new protocols

the fix is working correctly!


Red background color when LORA cannot be found makes the prompt barely visible

Hello,
Nice themes, thank you very much making it. However i'm facing a very little annoying issue. When i send prompt to Txt2img, sometimes some Lora are missing, in this case, the positive prompt background color turns red and the grey text above becomes almost invisible... it is super annoying to fix the prompts. I have to go back and forw with webmaster tools to quick fix the css each time i neeed to bring a prompt fix....
My suggestion : instead of the RED background, can you please instead only make a 1px or 2px red border frame ? Thus, it still focuses on an issue (lmissing loras)
can you please fix this to all templates ?
Thank you so much in advance !
here is what it looks on my end when a Lora is missing to my prompt

Temporary fix add a background color in style.css
textarea{
background: black !important;
}

please assign me this issue under hacktoberfest label


Document snapshots on Developers

Is this done? https://developers.wellcomecollection.org/datasets/

Yes


Buddybuild badge not loading on the GitHawk repository

Buddybuild badge not loading on the GitHawk repository overview screen:
bindViewModel() nil Optional(Error Domain=SDWebImageErrorDomain Code=0 "Downloaded image has 0 pixels" UserInfo={NSLocalizedDescription=Downloaded image has 0 pixels}) SDImageCacheType Optional(https://dashboard.buddybuild.com/api/statusImage?appID=59d904ff8588d60001729c4e&branch=master&build=latest)

Oh, looks like this is a SVG document, maybe that's the problem

We added a small bit of logic which is if the file name contains SVG then load it using a web view - that URL doesn't actually say it's an svg hence fails
I know we don't like dependencies, but we might wanna explore something like SVGKit to handle it properly, or do a request and check the mime type

This is tricky b/c the URL doesn't say what type of image it is. Maybe we need to check the URL and if it doesn't have a supported extension, render it as HTML instead?


Scan cards with different sizes

It seems the "search" and the "product not found" cards don't have the same height, a valid result:

(That one is clearly not a priority)

I have fixed this issue, Please checkout the pull request https://github.com/openfoodfacts/smooth-app/pull/1573


Replace redirect code 302 with 301 in config-network's comment

The http to https redirect is usually 301 rather than 302.
This patch changes the config-network comment and add test case for
status probe with 301.
/cc @julz @markusthoemmes

/lgtm
/approve

/hold

Sorry I wrote wrong PR :sweat_smile:
/lgtm cancel
/approve cancel
/hold cancel


Solved Add alt text to the images in docs #116

Notes for Reviewers
This PR fixes #116
Signed commits

[x] Yes, I signed my commits.

@surajvast1 Can you please keep the original formatting in hugo.toml ?

As in about the page format or the code please specify your questions if its page format i have already done if its about code then we need to do the changes in toml file by adding alt

If you think this is complete, could you please merge it? I'm also willing to assist in any way possible."

Hey @surajvast1   Let's discuss this on website call today at 6:30 PM IST / 7 AM Central time. Please add this as an agenda item in the meeting minutes.

@surajvast1 make sure to always sign off your commit, otherwise DCO check fails

Okay I'll make sure that, is it ok for now?

Excellent!

Thankyou so much

Thankyou


 (Optional)

Well, isn’t this helpful.

Pls delete this

Oxid, update the coming soon plz.
LOL

Gus, the coming soon isn't updated.

Well, isn’t this helpful.

Nah, I just checked the current version of coming soon and it is saying that it is out of date.
Oxide please fix

Pls delete this

If we do that, then we may forget to update the coming soon.

Pls delete this

If we do that, then we may forget to update the coming soon.

EDITED : well for someone that want join multi verison ,check this out : https://github.com/Foreheadchann/ViaMCP-Reborn and about clickgui check this one out, replace it with old one : https://github.com/DarkStorm652/Minecraft-GUI-API

Everyone knows about those, and you shouldn't use DarkStorm GUI API if you know what you are doing.

yall are the fattest skids ever, just rewrite this stuff yourselves and you wont need to ask for an update


Improvements for compress! function using SVD

There are several potential improvements for the compress! function, especially using SVD.

Normalize singular values in _factorize:
We need to consider normalizing these values by the maximum singular value, as we discussed about this issue with one of the developers.

Proposed change:
trunci = min(
    replacenothing(findlast(>(tolerance), factorization.S/maximum(factorization.S)), 1),
    maxbonddim
)

I am not sure what the maximum values are when using CI.

Avoid recompression during left canonicalization:
When making tensor trains left canonical by sweeping from left to right using SVD, we should avoid recompressing the tensor train. The current implementation sets the tolerance or maximum bond dimensions to finite values, so these must be fixed.

Contract singular values with left unitary matrix:
In the right-to-left sweep in _factorize, that is, we move the canonical center from left to the right, we need to contract the singular value matrix with the left unitary matrix of SVD.
This could improve the accuracy of the recompression of TT. However, current implementation contracts the singular value matrix with the right unitary matrix of SVD.

Proposed change in _factorize:
trunci = min(replacenothing(findlast(>(tolerance), factorization.S/maximum(factorization.S)), 1), maxbonddim)
return (
    factorization.U[:, 1:trunci] * Diagonal(factorization.S[1:trunci]),
    factorization.Vt[1:trunci, :],
    trunci
)

@sakurairihito
Thank you.
Point 1: We should provide an option to choose whether or not we normalize the error in SVD/QR and CI.
Point 2: This may be a bug.
Point3: This may be a bug.
@rittermarc
What do you think?

@rittermarc
I am implementing a fix.

I agree with all of your points. I would consider 2. and 3. bugs, and we should fix them.


emmc-flasher does not set custom dtb in uEnv on eMMC?

Hi!
I added an own config to the build system (https://github.com/robert-budde/omap-image-builder/blob/master/configs/ibb_gateway_debian_testing_armhf.conf) which sets chroot_uenv_txt="ibb_uEnv.txt". The file states "dtb=am335x-boneblack-ibb.dtb". Writing non-flasher sd-cards using setup_sdcard.sh works like a charm and makes the resulting card also use the referenced dtb, though using a flasher-image to flash the eMMC seems it does not migrate the dtb-setting?

That's very odd, as the eMMC flasher just modifies /boot/uEnv.txt it doesn't generate it from scratch:
https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh#L360
So you custom dtb= define should stay their.
Regards,

I could not find the reason for this but did a workaround by creating my own machine configs which include the specific dtb. Maybe this is also the more correct way of doing it.


High DPI support, interface scaling

Hey, fine job in there. Do you by aby chance have scaling on your radar? Maybe I could help.

Thank you very much! I'm afraid not. It's been a while since i actively developed the project and right now i am focusing on other things. If you are interesed in the project though feel free to clone and make it your own :)


Add clone 👨🤝👨 repo button 🔘 after create

Fixes https://github.com/microsoft/vscode-azurestaticwebapps/issues/101
I'm not sure how commonly we use telemetry as part of a conditional statement, but it made sense to me in this case.  If we don't want to do that, I can always mess around with the contexts settings that are passed around.
I unshifed clone because I feel like it is the more important post-action compared to Show Actions in this case.

Closing until we have a better understanding of customer scenarios


App resolves to 404 due to missing orgId from Clerk

When starting the app, it resolves to a 404 even after signup. I added all the env vars, including LIVEBLOCKS_SECRET.
It looks like the app tries to find an orgId in Clerk and it returns undefined. Then, because it can't, it 404s.

I already tried creating an org manually in Clerk and adding the user to it, but nothing comes through.
Any extra steps that need to be taken here that aren't documented?

When logging what await auth() returns there's no orgId at all. How is this supposed to work? Because when I sign up an account there's no flow to create an organization, and yet it enforces it here so it's a bit confusing.

How do we get the orgId in here
How does the user create an org in order for this to work while enforced?

Update: this was related to using bun instead of pnpm.


Added get_tracked_mappoints function

Exposed useful function, if one needs to process tracked points

I'm happy with these changes, but you've bumped the python version, which is unrelated. I'll try and work out how to merge without that change, or if you can omit that commit from the pull request, I'll merge.

Sorry about that. Fixed


Added link for accepted time zone values

Added a link to Azure docs for accepted time zone values for changing app service time zone.

@tfosmark : Thanks for your contribution! The author, @genlin, has been notified to review your proposed change.

@andrewstefanik Thanks for helping to improve the document.
#sign-off

Hi @andrewstefanik:
This PR has branch conflicts that you need to resolve before it can be merged.
Thanks,
Trisha
#hold-off


Improved Relay integration

Closes #1292

@tillkruss Lmk if there's anything else we need to improve

coverage: 81.579% (-0.9%) from 82.431%
when pulling c5435f58b5241f7bcc9e659f30fd1c990f092c38 on feature/relay-improvements
into b02c33149b84efe87c622da09b1fbd49bf451a6e on v3.x.

@vladvildanov This needs a rebase when you have a moment.


message view: EXIF orientation is ignored, causing images to look rotated

(@gnprice:) Here's a nice description of the issue from a different webapp, complete with instructions for how to fix it as a user:

The cause:

You may notice that sometimes when [posting a photo on Zulip] that the image is not rotated correctly. This is not a bug [in Zulip]! Rather, this is a fairly technical behind-the-scenes issue that involves the photo's orientation meta data and a web browser's inability to interpret it. [...]

Cameras, especially those on mobile phones and tablets, have built-in orientation sensors that assign special rotation information to every photo they take. Behind the scenes, this tells other apps what the correct rotation angle should be for that photo. In other words, your photos are actually taken and saved sideways but then extra orientation meta data specifies a rotation angle for correctly displaying the photo. When you view that photo in your phone's gallery, or in an app that understands the orientation meta data, it appears as if the image is rotated properly when it's actually not. Unfortunately, web browsers [don't] honor orientation meta data. This is why a photo might appear sideways after it has been uploaded [to Zulip].

Sad but true. Some phones prevent this problem by rotating the actual image data, but many (even many recent, high-end phones) do not.

How to fix it for your photos:

To make sure that a photo will be displayed properly in web browsers the best option is re-save the photo with proper rotation and without orientation meta data. On a mobile device, you can often achieve this by opening a photo and rotating it 360 degrees or until it appears correctly then re-saving it as a new photo. Alternatively, you could save a slightly cropped version of the same photo. You could also download the photo onto a desktop computer and adjust it using the basic photo apps built into OSX and Windows (both called Photos) or an advanced photo editing program such as Adobe Photoshop or Lightroom.

We should also develop a solution that fixes photos up automatically, so people don't have to do it themselves. More on that below.

(@gnprice's technical description, following the investigation below:)
By default in a JPEG photo, the pixels around coordinates (0, 0) -- i.e., the first pixels in the file -- go in the upper left. Many devices produce JPEG files that start somewhere else. These contain some metadata, in the EXIF format, to say something like orientation=upper-right, meaning the pixel at (0, 0) goes in the upper right instead of the upper left. This means any software displaying the photo needs to respect that metadata; if it doesn't, the photo will come out wrong, e.g. rotated sideways.
Unfortunately, while a lot of software does respect EXIF orientation metadata, the web does not. Specifically, an <img> element in HTML ignores it. The result, given we don't do anything to deal with this, is that these photos are shown sideways in the Zulip webapp, desktop app, and most of the mobile app.
Devices that produce photos with this problem include some phones, but not others, from each of Apple, Samsung, and Google; also some phones from Motorola and probably other vendors; probably some standalone digital cameras too, but nobody in these threads has tried one. Reports of this issue have referred to uploaded photos in messages and to user avatars.
To fix this, we'll need to inspect uploaded images (including user avatars) on the server at upload time to extract the EXIF orientation metadata. Then we can do either of the following:

Normalize the orientation to upper-left, rearranging the pixels as needed. (A Medium post linked below has example code to do this in Python, using PIL.)
Convey that metadata to the client (perhaps in a data- attribute on the img?) so it can apply a CSS transform to fix the orientation.

For more detail and background, see https://github.com/zulip/zulip/issues/8177#issuecomment-534310596 below, and the comments after it.

(original report:)
quoting a conversation:
A: my pictures come in sideways when i upload them, even when they are the correct orientation
B: If they are coming from a phone, this might be a matter of browser support. The image is rotated, but has metadata that specifis the correct orientation taken from the phone's gyro. Browser not respecting this metadata might result in the issue.
C: I remember hearing about something crazy that iPhones specifically did here -- like if you go and rotate them in the built-in camera app, it just does something in some idiosyncratic metadata that Apple's stuff all pays attention to.
D: Yeah this happens w iPhone metadata and browser uploads. Just detect the orientation by width vs height and make sure it's not rotated.
E: This is relevant:
https://developer.mozilla.org/en-US/docs/Web/CSS/image-orientation#Browser_compatibility

Do you think this would be an easy bug to fix? If so, I would like to claim it.

OK here's a sample image with this problem for testing: https://www.dropbox.com/s/khc0ila04oomi4i/A9791474-33C6-4B84-8A99-2FA4D7A2F017.jpeg?dl=0
What happens in Zulip after uploading is the image is rotated 90 degrees off.

https://stackoverflow.com/questions/13872331/rotating-an-image-with-orientation-specified-in-exif-using-python-without-pil-in might be relevant.

@zulipbot claim

The thumbnail and avatar images which we are resizing can be fixed with PIL.
The issue for the other (e.g message) images lies on the browser side. The relevant chromium issue is https://bugs.chromium.org/p/chromium/issues/detail?id=56845.
The problem can be fixed on the browser side as shown at https://stackoverflow.com/questions/20600800/js-client-side-exif-orientation-rotate-and-mirror-jpeg-images, but that would require us to call that load function from everywhere we display a user-inputed image.
If we were only displaying images uploaded to the zulip server, rotating each image containing exif Orientation data with PIL and get rid of the orientation exif data would be a good option. But that would not cover the case of user using the image markdown to display image from an external url.

OK.  Well, to start, we should probably fix our PIL thing, since that's fully under our control.  For the rest, we might want to see whether the Thumbor thumbnailing system does the right thing.

Here's another sample incorrectly-rotated image if it's useful:
https://www.dropbox.com/s/7vb5y14vr73lt3r/2018-07-27 18.51.30.jpg?dl=0
(The pens should appear at the top of the page)

It looks like this bug still exists even with Thumbor PR completed.

We've gotten a similar-sounding report on the mobile side which I've filed as https://github.com/zulip/zulip-mobile/issues/3583 .
I've been unable to reproduce it, though. (Details there.) For people still seeing it, I would be curious to hear details of how to reproduce!

I believe the issue reported here was about taking a picture (presumably with landscape orientation) with the iOS camera and then sending it in a message in Zulip.  The mobile apps need not be involved; the issue is that the iOS phone camera uses unusual orientation metadata that a lot of image-processing software does not respect.

(I think if you download the image Waseem posted above and send it in a Zulip, you'll see this issue)

I looked further into this today after @timabbott provided an example of it on chat.zulip.org, and following helpful reports on zulip/zulip-mobile#3583 from another user trying several devices. I think we have a diagnosis!
Details of my investigation are at https://github.com/zulip/zulip-mobile/issues/3583#issuecomment-534302762 . I think the conclusions are:

The specific metadata we're not handling is the EXIF "orientation" metadata.

With the file utility (after downloading the image), this looks like orientation=upper-right on Tim's example photo. It's orientation=upper-left for photos that don't have this problem.
I believe that means the pixel at coordinates (0, 0) is supposed to go in the upper-right corner (vs. the usual upper-left)...
and the issue is that <img> in HTML doesn't respect that EXIF orientation metadata. That would completely explain what we're seeing.
(OTOH browsers have no trouble when looking at the image alone -- if you click through to the image URL for one of these, it gets displayed correctly.)

Looking around on the web, it seems like there isn't an easy good solution. There was an effort to get into CSS a property image-orientation and value from-image that would tell the browser to handle this in <img> just like it can in a freestanding image; but it didn't achieve cross-browser consensus.
I think the basic possible shapes for a solution are:

On the server at upload time, consult the EXIF metadata and normalize it to upper-left, rearranging the pixels as needed.

This would naturally go into the Thumbor flow.

On the client at display time, apply a CSS transform to fix the orientation.

This seems to also require fiddling with width vs. height.
Two sub-possibilities for this, about identifying what the EXIF orientation metadata says:

Determine that on the server (at upload time?), and include that metadata in some form more convenient to the client.
Determine that on the client, by invoking some library to actually look at the EXIF metadata in the image blob.

These each have advantages and disadvantages and it's not obvious to me which is the best, or least bad.
Some links with leads for whoever pursues this:

Helpful background article: https://www.howtogeek.com/254830/why-your-photos-dont-always-appear-correctly-rotated/
SO question with useful discussion

SO questions with various possible solutions, both client- and server-side: one, another, a third

2012 blog post testing about 20 then-popular services on the web and finding that most of them didn't handle this right. (It's probably better in 2019, with lots more people posting photos from their phones.)

I don’t think it’s feasible to detect the orientation on the client at download time because the browser doesn’t expose the bytes of the encoded image to JS. All the client-side solutions I see seem to be about detecting the orientation at upload time.
Thumbor already has a RESPECT_ORIENTATION option defaulting to False that we could enable.

I don’t think it’s feasible to detect the orientation on the client at download time because the browser doesn’t expose the bytes of the encoded image to JS.

Hmm. That certainly makes sense, but...

All the client-side solutions I see seem to be about detecting the orientation at upload time.

some of the suggested solutions on those SO threads certainly appeared to be doing the detection in the client at display time.
I hadn't dug into how they accomplished that. Looking at one of them now, it turns out:
https://github.com/exif-js/exif-js/blob/53b0c7c1951a23d255e37ed0a883462218a71b6f/exif.js#L383
that if you point it at an <img> tag with a src that isn't a data: or blob: URL... it goes and downloads the image a second time in order to get at the bytes.
I think that makes the cut for "feasible" :grin: . Not so much for "solution we actually want", though. So yeah, we'll need to at a minimum detect the orientation on the server.

Had another report of this today, in a support email.
A couple of fun facts I learned while replying to it:

In 2019, people are still seeing this problem on at least Facebook and Imgur. So the situation on the web at large may not in fact be much improved from that 2012 blog post.

It seems to me that the root issue here is that the web itself -- specifically <img> tags -- simply does not support this metadata. (Except Firefox with image-orientation.) In other words there's basically a standoff between browser vendors, who have chosen not to support it, and many phone vendors, who persist in using it. Services, from Zulip on up to giants like Facebook, are caught in the middle, with the choice of each implementing our own workarounds that really shouldn't be necessary. Still I'm kind of surprised that Facebook in particular hasn't succeeded in working around it.
Also kind of puzzling because in that 2012 post Facebook was actually one of the few that did completely handle EXIF orientation metadata. Not sure if there's been a regression, or if there's something else going on with the reports of photos there rotating wrong -- these reports aren't as technically concrete as the 2012 post.

On at least the Pixel 3 XL and the Pixel 3a, the issue reportedly goes away if you go into camera settings, turn HDR off, and turn it back on again. Silly, but if it's effective then great. Hopefully that workaround is helpful for someone.

Tried on two Motorola phones (Z2 and Z3) and it didn't change the behavior.
Also tried with HDR off altogether, no luck.
On Fri, Sep 27, 2019, 7:12 PM Greg Price<EMAIL_ADDRESS>wrote:

Had another report of this today, in a support email.
A couple of fun facts I learned while replying to it:

In 2019, people are still seeing
https://forums.androidcentral.com/google-pixel-3-pixel-3-xl/934785-incorrect-photo-rotation.html
this problem on at least Facebook and Imgur. So the situation on the web at
large may not in fact be much improved from that 2012 blog post.

It seems to me that the root issue here is that the web itself --
specifically  tags -- simply does not support this metadata.
(Except Firefox with image-orientation.) In other words there's
basically a standoff between browser vendors, who have chosen not to
support it, and many phone vendors, who persist in using it. Services, from
Zulip on up to giants like Facebook, are caught in the middle, with the
choice of each implementing our own workarounds that really shouldn't be
necessary. Still I'm kind of surprised that Facebook in particular hasn't
succeeded in working around it.
Also kind of puzzling because in that 2012 post Facebook was
actually one of the few that did completely handle EXIF
orientation metadata. Not sure if there's been a regression, or if there's
something else going on with the reports of photos there rotating wrong --
these reports aren't as technically concrete as the 2012 post.

On at least the Pixel 3 XL
https://forums.androidcentral.com/google-pixel-3-pixel-3-xl/934785-incorrect-photo-rotation.html
and the Pixel 3a
https://forums.androidcentral.com/google-pixel-3a-pixel-3a-xl/974633-photos-post-upside-down-sideways-facebook.html,
the issue reportedly goes away if you go into camera settings, turn
HDR off, and turn it back on again. Silly, but if it's effective then
great. Hopefully that workaround is helpful for someone.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/issues/8177?email_source=notifications&email_token=AAQNAEUMC2QTOESLTAWFA7TQL2HM7A5CNFSM4ENVBSYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD72JP7Y#issuecomment-536123391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQNAEWTXPLV4U66YEDIZ3LQL2HM7ANCNFSM4ENVBSYA
.

Tried on two Motorola phones (Z2 and Z3) and it didn't change the behavior.

Good to know, thanks.
The HDR off/on workaround is quirky enough that I wouldn't really expect it to generalize beyond Pixel 3-family phones -- or perhaps Pixel phones more broadly -- so that fits. If someone sees this issue on a Pixel device, I'd be quite curious to hear whether this workaround works (and what specific device model they're on.)

I took four pictures with my Pixel 2 in all four orientations, without changing any settings or closing the camera app. They all got saved with EXIF orientation top-left, and display correctly in EXIF-aware and non-EXIF-aware viewers. There are probably zillions of variables involved so I don’t know what to conclude from this other than that my particular phone doesn’t exhibit this problem.

I took four pictures with my Pixel 2 in all four orientations, without changing any settings (HDR+ is enabled) or closing the camera app. They all got saved with EXIF orientation top-left, and display correctly in EXIF-aware and non-EXIF-aware viewers.

Yeah, I got similar results the other day with my Pixel 2 XL: https://github.com/zulip/zulip-mobile/issues/3583#issuecomment-534302762
It seems to me like if you're trying to make a quality phone, the strategy "always save with EXIF orientation top-left" is clearly the one that's best for your users, given all the software out there -- most of all, the web itself -- that's incompatible with anything else. So I'd interpreted that observation as "oh good for Google, they've decided to do the user-friendly thing in Pixel devices". As a result I was surprised to learn that a newer Pixel model could have the problem.

There are probably zillions of variables involved so I don’t know what to conclude from this other than that my particular phone doesn’t exhibit this problem.

Yep, agreed.

https://medium.com/@ageitgey/the-dumb-reason-your-fancy-computer-vision-app-isnt-working-exif-orientation-73166c7d39da may be helpful for doing the rotation in our Python codebase (it has some nice code examples).

We just had a fresh report of this, in the form of an App Store review titled "Mobile app needs work- profile picture is sideways". It'd be good to fix.
I found it took a bit of doing to refresh myself on the state of this thread, so I went and wrote a new description with where it currently stands.

Sorry for the dupe comment... wrong issue initially:
I noticed that in a recent mobile release, this has been resolved, and mobile uploads are appearing in the correct orientation on the mobile client! :smiley:  Mobile uploads viewed in the desktop client, however, are still unoriented. :cry:  Glad to see there's progress! :+1:

@cognusion Hmm interesting -- I'm not actually aware of any change we've made that would have fixed this!
Is it possible the images where it worked were taken from a different device than the images where you've seen the problem?
I'd expect the situation is still:

Photos taken by some devices (or by some other devices under the right settings, the right phase of the moon, etc.), have the standard orientation upper-left in the first place, and are immune to this problem on all clients.
In the mobile app, all photos show up correctly on some screens: in particular the lightbox you get when you tap on an upload, and people's profile pictures when you look at their profile.
But if an image (a) has an alternate orientation, which is true of all photos taken from some devices; and (b) you're seeing it in the webapp, in the desktop app, or when looking at messages in the mobile app (including people's profile pictures as seen next to their messages); then it'll show up rotated or otherwise mis-oriented.

If you can pin down a situation that diverges from that, then we should revise our diagnosis and that will be interesting!

@gnprice maybe a dependency got updated? I scrolled back through photos I know were at the wrong orientation previously, and they are oriented properly on Zulip Android.
To test, I uploaded a JPEG to a Zulip room with the following (upper right):
JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=11, manufacturer=motorola, model=moto z3, orientation=upper-right, xresolution=164, yresolution=172, resolutionunit=2, software=messi_verizon-user 9 PDX29.84-51-11 cb789 release-keys, datetime=2020:04:25 12:42:36, GPS-Data]

And it is showing properly in Zulip Android both in-line and in the lightbox (which has always been correct). But in the desktop, it is mis-oriented. Screens attached. Apologies for the quick-and-ugly censoring.

Fascinating! Well, that is good news even though we don't understand it :wink: Thanks much for the report and the details.

Aha! Looks like in fact this is fixed by Chrome 81:
https://www.chromestatus.com/feature/6313474512650240
which just rolled out over the last few weeks.
And reportedly the same thing was already true in iOS Safari as of sometime last year -- so at least in iOS 13 -- and it's now landed in Safari more broadly:
https://bugs.webkit.org/show_bug.cgi?id=89052
Firefox (which doesn't affect the mobile app, but does the webapp) is also planning to ship the change soon:
https://www.fxsitecompat.dev/en-CA/docs/2020/jpeg-images-are-now-rotated-by-default-according-to-exif-data/
So that's great news. It looks like this issue, as I described it above, is getting fixed for the whole Web:

In other words there's basically a standoff between browser vendors, who have chosen not to support it, and many phone vendors, who persist in using it. Services, from Zulip on up to giants like Facebook, are caught in the middle, with the choice of each implementing our own workarounds that really shouldn't be necessary.

I think we can just about close this issue now as a result. The one action that's really left for us to take in the Zulip project is we should ship a desktop release where the embedded Chromium version is 81+ -- that's the one place where we're responsible for browser updates. I'll file an issue there.

Awesome!  It looks like Electron 9 will be out with that fix in late May which is pretty soon, so indeed it seems like we can close this issue as resolved by browsers (which definitely feels like the right solution structurally for the Web, in addition to conveniently not requiring us to write a workaround).
And https://github.com/zulip/zulip-desktop/issues/946 will suffice to track the desktop app update side of this.
Thanks for the follow-up @cognusion!

We recently had a report of this again.
This time, the image file in question is a PNG, not a JPEG. As discussed above, this issue was finally resolved for JPEGs by the browser vendors; but apparently it still exists for PNGs.
The image file does indeed have EXIF metadata with a non-default orientation:
$ exiftool ~/Downloads/83b4bf6721844a9e6ee0f5a0ace02e0c0c33175b.png | grep -i orient
Orientation                     : Rotate 90 CW

Some devices and browsers show the image rotated 90° clockwise from the intended orientation (i.e. they put the sky, and the top of the person's head, to the right instead of the top.) Given the value of that metadata, I suspect this means the intended orientation is the one gotten by ignoring that metadata, and the clients where the image looks wrong are the ones that are correctly displaying what the image says.
Observed behavior is (see that chat thread for version numbers):

Rotated clockwise (so apparently correctly applying the metadata): Safari on macOS; Safari on iOS; Zulip mobile app on iOS
Intended orientation (so apparently not applying the metadata): Chrome on macOS; Chrome on Linux; Zulip mobile app on Android

I don't think there's any useful action we can reasonably take to address this, unfortunately. This is a matter for the browser vendors, to sort out consistent behavior amongst themselves.
For users, I think the best workaround is to avoid using a PNG with non-default EXIF orientation. Fortunately I think these are rare -- it's only likely to arise in the case of a photo, and photos are usually stored as JPEG rather than PNG. Options include:

Use a JPEG rather than a PNG.
Process the PNG file to apply the rotation to its actual image representation, so that the orientation in the metadata can become the default. (For example, if you convert the image to a simple lossless format like BMP, and back to PNG, I expect that would accomplish this.)


Color does not look right

I am trying your library with this image and the colors does not look right, especially the yellow color. Could you please explain to me why this happen?

![1477210243mtzdjveyisca2fl](https://cloud.githubusercontent.com/assets/9668858/19624931/5512f07e-9934-11e6-97e1-9e13d7e90a6f.jpg)

See my response on #30


updated application model

Added two more keys in the application model:

status: can be rejected or accepted
reason: this will be there if the super user has rejected a particular application

@prakashchoudhary07 as per our discussion yesterday in call regarding changing the reason key, I was thinking of changing this to DecisionFeedback, what do you think?

@prakashchoudhary07 as per our discussion yesterday in call regarding changing the reason key, I was thinking of changing this to DecisionFeedback, what do you think?

How about just feedback?
you can get suggestions from others also

@prakashchoudhary07 as per our discussion yesterday in call regarding changing the reason key, I was thinking of changing this to DecisionFeedback, what do you think?

How about just feedback? you can get suggestions from others also

feedback also look good for me
as it can give in any case reject or approve


On-demand (Exec) script runs constantly if RTSP clients times out before source starts publishing

I believe there is a bug with exec source (possibly other on-demand sources) when the frontend client times out prior to the backend publishing.  Below you can see the logs from my application along with messages from go2rtc.  You can see that a client connects to the stream initially, and this runs the start-stream.sh script with the correct parameters as it should, this works perfectly to trigger my application code to start a stream.  However, due to various issues (network issues, slow service response, etc) this can sometimes take a long time or even fail completely.
In the case below my code is unable to start the stream before the RTSP client (VLC) times out (5 seconds seems to be the common RTSP timeout).  Overall, this is no big issue, I would expect go2rtc to simply see that it no longer has a client and stop the exec.  However, instead, go2rtc ignores that the client timed out and is no longer requesting the stream and instead keeps running the exec command.  Even if I force kill the script (for example, timeout with an error after 10 seconds), go2rtc will continue to re-run the exec command even though there are no longer any RTSP clients requesting the stream.  As far as I can tell it will do this forever, even if the stream eventually starts publishing.  It seems that, when a frontend client times or errors out, it is never removed as a client, and the on-demand stream effectively becomes an always-on stream.
  ring-rtsp [go2rtc] DBG [rtsp] new consumer stream=3ce1a1b144ac_live +7s
  ring-rtsp [go2rtc] DBG [streams] probe producer url=exec:/mnt/c/Users/tsigh/Documents/GitHub/ring-mqtt/scripts/start-stream.sh 3ce1a1b144ac live ring/a9ce28cb-fafb-421c-4508-29d54f48cbd3/camera/3ce1a1b144ac {output} +1ms
  ring-rtsp [go2rtc] DBG [exec] run url="exec:/mnt/c/Users/tsigh/Documents/GitHub/ring-mqtt/scripts/start-stream.sh 3ce1a1b144ac live ring/a9ce28cb-fafb-421c-4508-29d54f48cbd3/camera/3ce1a1b144ac rtsp://localhost:8554/6653381986c34366669eac944e9c06ac" +0ms
  ring-rtsp [Front Porch] Sending command to activate live stream ON-DEMAND +0ms
  ring-mqtt [Front Porch] Received set live stream state ON-DEMAND rtsp://localhost:8554/6653381986c34366669eac944e9c06ac +941ms
  ring-mqtt [Front Porch] ring/a9ce28cb-fafb-421c-4508-29d54f48cbd3/camera/3ce1a1b144ac/stream/state ON +1ms
  ring-attr [Front Porch] ring/a9ce28cb-fafb-421c-4508-29d54f48cbd3/camera/3ce1a1b144ac/stream/attributes {"status":"activating"} +941ms
  ring-mqtt [Front Porch] Starting a live stream session via Ring servers +1ms
  ring-rtsp [Front Porch] State indicates live stream is activating +78ms
  ring-rtsp [go2rtc] WRN github.com/AlexxIT/go2rtc/cmd/rtsp/rtsp.go:202 > error=EOF +5s
  ring-rtsp [go2rtc] WRN github.com/AlexxIT/go2rtc/cmd/rtsp/rtsp.go:202 > error=EOF +3ms

Ok, if I understand the code correctly, I think I see why this is happening.  When a new consumer is registered, the code runs stream.AddConsumer() and creates a closer function to be used to remove that consumer once the connection is closed.  However, if the client connection times out, that is handled by error handler at line 202 when closes the connection and returns and never calls the closer() function, at which point, I don't think that the closer function will ever be called, thus there will forever be a consumer.
Admittedly, I've never written any golang, but that's what I think is happening anyway.  Not 100% sure of the proper fix, but maybe just need to call closer in the error handler?  I may give that a spin.

OK, so modifying this code in cmd/rtsp/rtsp.go:
	if err := conn.Accept(); err != nil {
		log.Warn().Err(err).Caller().Send()
		_ = conn.Close()
		return
	}

to:
	if err := conn.Accept(); err != nil {
		log.Warn().Err(err).Caller().Send()
		_ = conn.Close()
		if closer != nil {
			closer()
		}
		return
	}

I have no idea if this is the correct way to fix this, but I couldn't reproduce the issue after this.

You right! And you make right fix. I'm already did it. But not published yet. Just testing stability and other problems

Great, thanks for confirming!  It seems to work just fine for me now, but maybe next time I'll have to confidence to just open a PR instead.

Should be fixed https://github.com/AlexxIT/go2rtc/releases/tag/v0.1-rc.8


new request

Ok, I do a new request at once this time. Fresh start!
I did a video to explain things https://youtu.be/mNV5bVua6FI
Take your time, it's not hurry. Not too much because we all die at the end. lol

ok no answer I guess I try something else

ok no answer I guess I try something else

Hi, thank you but I have not been in front of a computer to review this.
A quick look shows that all the same comments I made in https://github.com/claremacrae/reveal-active-file-button-plugin/pull/6#issuecomment-1469557053 apply here too, though, about it being too large a change, and about history being lost by source files being copied and then deleted, instead of moved.

Specifically:

But again, I would love to accept a PR that only contains only the fixes needed to remove the double-click workaround cleanly.

I understand what you mean because it's hard to read changes. but I'm not familiar with pull requests. So I think you understood my first changes if you watched the repo I show you. organizing differently the files won't change much. after some modifications I done were not essential. to add the option I did later I did another plugin. it's less complicated then changing an existing plugin. and maybe I would introduce bugs I can't change directly later. so thks for your answer.


Fix Initialization in AcknowledgePossession, possible race condition

After a lot of debugging, I found that there is a possible race condition during bad network conditions (~200ms, 5% packet loss) with 5%~10% of repro chances.
If this happens, ASC will not be initialized properly and you will get LogAbilitySystem: Warning: Can't activate LocalOnly or LocalPredicted ability %s when not local!
This happens because during AcknowledgePossession, the pawn controller is not setup yet, and during FGameplayAbilityActorInfo::InitFromActor, PlayerController will be null forever, and then, when calling UAbilitySystemComponent::InternalTryActivateAbility, bool bIsLocal = AbilityActorInfo->IsLocallyControlled() will be false
I consider that OnRep_Pawn is a good place to call RefreshAbilityActorInfo, that will call FGameplayAbilityActorInfo::InitFromActor again, but the controller will be valid at that point.

@tranek this issue is still reproduceable, and following the documentation examples will end in this issue sooner or later in any networked game.
If there is a way I can help you to repro this, and waste less time, let me know.

@linqen Is it reproducible yet?

@linqen Is it reproducible yet?

It is using UE 5.0. I don't have much free time right now, so I can't confirm on newer versions.


URL and Alt fields styling bug inside image modal window

When we add an image to a markdown field, the URL and Alt fields from the opening modal are displayed over the top left icon. You can easily reproduce this bug in the official demo.

There were changes to that modal recently. As of current I am not able to reproduce this in the latest version. Can you update to 2.3.3 and confirm if this issue is still present or not?

It looks fine on Chromium based browsers, but it is still present is the online demo in Firefox (113.0.1): https://demo.staticcms.org/#/collections/posts/entries/2015-02-15-this-is-a-json-frontmatter-post
And it even worse on Safari (15.6.1) as you can see in the screenshot bellow:

Adding w-full class on the SVG element should fix it.


BooleanCell (checkbox)

Currently no way to represent booleans, especially with a write mode.

Closed in 58b40c9


Adding Code-Of-Conduct File to the repo

As this repo is open source having a code-of-conduct File Becomes Important:- code-of-conduct:- We propose adding a comprehensive Code of Conduct to our repository to ensure a safe, respectful, and inclusive environment for all contributors and users. This code will
serve as a guideline for behavior, promoting diversity, reducing conflicts, and attracting a wider range of perspectives.
Issue type

[✅] Docs

If you were planning this issue kindly assign it to me! I would love to work on it ! Thank you !

Thanks for your valuable contribution in PR127! If you have any other questions, feel free to contribute. Best wishes!


chore(master): release 0.4.1

:robot: I have created a release beep boop
0.4.1 (2023-07-30)
Bug Fixes

cursor: re-add new VSCodeNotifyRange impl (368c58d)
cursor: re-add new VSCodeNotifyRange impl (#1358) (368c58d)
custom_commands: wait for cursor update before issuing command (368c58d)
lua: rename vscode lua plugin to vscode-neovim (#1356) (72adf16)
re-add VSCodeCommentary (368c58d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vscode-neovim/vscode-neovim/releases/tag/v0.4.1 :sunflower:


DOTA2：courier using equipment event

i want to get information about courier equipment using，but through @OnCombatLogEntry ,CombatLogEntry.getInflictorName().equals(”the equipment name(eg:item_smoke_of_deceit)”)  can't get it.
I would appreciate it if you could help me.

There is m_hTransientCastItem property in each CDOTA_Unit_Courier entity. But the property never perform properly. I asked my friend to use a smoke with courier at 31:13 in radiant fountain in game<PHONE_NUMBER> but its not detected. Maybe spheenik can you fix this property please? Just sayin.

Sorry: I just provide the data in the replay, I do not modify it in any form. If the data sucks, you've got to complain to Gaben.

Yeah I understand cant really blame spheenik for that. I use modifier_add combatlog in the current project and everything is ok except cant find smoke center when courier uses smk (but we know if there is no user for smoke, then user is a courier). It seems
a smoke is the only item a courier can use. Luckily a pro tells me he didn't smoke in a courier for more than a year, so i guess no need to worry to much.


Smoother Template Cnt Loading

Designers want to reduce the delay for the loading effect so that the loading of the number seems smoother and can better attract the attention of users.
Resolves: https://jira.corp.adobe.com/browse/MWPW-138096
Test URLs:
Before: https://stage--express--adobecom.hlx.page/express/templates/
After: https://template-cnt-loading--express--adobecom.hlx.page/express/templates/?lighthouse=on

Codecov Report

Merging #380 (faee9ea) into stage (70b514d) will increase coverage by 0.11%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##            stage     #380      +/-   ##
==========================================
+ Coverage   30.51%   30.63%   +0.11%
==========================================
  Files         124      124
  Lines       25213    25209       -4
==========================================
+ Hits         7695     7722      +27
+ Misses      17518    17487      -31

Files
Coverage Δ

express/blocks/template-list/template-list.js
15.94% <0.00%> (+0.01%)
:arrow_up:

express/blocks/template-x/template-x.js
4.86% <0.00%> (+<0.01%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Coordinator initialize had an error: request timeout

Hi, I have follow your instructions with the patch and IAR.
It compile, I can upload hex file but when I try zigbee shepherd I get this error :
serialport/bindings loading WindowsBinding +0ms
zigbee-shepherd starting +0ms
zigbee-shepherd:init zigbee-shepherd booting... +1ms
serialport/stream opening path: COM6 +0ms
serialport/binding-abstract open +0ms
serialport/stream _read queueing _read for after open +7ms
serialport/stream opened path: COM6 +85ms
cc-znp The serialport COM6 is opened. +99ms
serialport/stream _read reading +2ms
serialport/binding-abstract read +92ms
zigbee-shepherd:request REQ --> SYS:osalNvRead +5ms
cc-znp:SREQ --> SYS:osalNvRead, { id: 3840, offset: 0, len: 1, value: [ 85 ] } +2ms
serialport/stream _write 8 bytes of data +20ms
serialport/binding-abstract write 8 bytes +22ms
serialport/stream binding.write write finished +9ms
cc-znp:SRSP <-- SYS:osalNvRead, TIMEOUT, { id: 3840, offset: 0, len: 1, value: [ 85 ] } +4s
zigbee-shepherd:request RSP <-- SYS:osalNvRead +6ms
zigbee-shepherd:init Coordinator initialize had an error: request timeout +2ms
With the hex that you provide it works well.
Any Idea ??
My IAR version 10.30.1

Did you exactly follow the intructions or did you made some modifications?

Yes
1- I have download the Z-Stack Home 1.2.2a.44539
2- I have copy/paste the patch file in the directory
3- Git apply firmware.patch & I can see the modification on files
4- Open znp enw in IAR click Yes twice to convert projects
5 - Set target to cc2530-prodhex
6- put only "FIRMWARE_CC2530_DEFAULT" in Defined symbols
7- Change Override default  to CC2530.hex
8 - Rebuild all
9 - Flash my CC2530 with this hex file

What do you mean with 7- Change Override default to CC2530.hex?

In option -> linker -> output I have to set  override default with a .hex otherwise it generate a .a51 file   !

That shouldn't be needed, probably the reason why it fails, setting target to cc2530-prodhex should produce a .hex file.


fix: Make #2 actually work

Yeah, #2 didn't work, so here's the fix for that + README update.
TIL jq had a --arg flag. Before that I had some weird quotation mark errors.

😍
Thanks for updating the syntax/readme as well!


Rails 5.0 support check list/notes

This is a list of activities we need to release 5.0 support.  At this point we have some individual issues that likely will not be fixed at release time.

[x] Add 1 issue per problem for big three adapters (mysql, sqlite, postgresql)
[x] Make master a maintenance branch and move rails-5 to master
[x] Fixup build script to generate .gem (probably mostly working now)
[x] Add to travis (not technically needed for release but highly desirable)
[x] pare down local test suite to only test things not covered by AR test suite

Has DB2 / AS400 support been dropped for rails 5?


Add Update Profile + Delete Profile Option

Description
Add Update Profile endpoint and Delete Profile endpoints.
Update Profile
@route POST api/profile/me
@desc Create your own profile (and if profile already exists then update it)
@access Private
Delete Profile
@route DELETE api/profile/me
@desc Delete profile, user
@access Private

cc: @madhup01 @priyalweb


Fix issues with poller

Hey,
Thanks for merging the last stuff! As you pointed out there were a couple of issues with redundant tests / test failures as well as the fact that I hadn't added the pbxproj to the commit - this is all included in this pull request. Hope it looks okay.
Jon

Thanks :+1: but I already fixed it in f9a4be8737957c076114baeb78cfffc7081f91d5 and debdef5a938e71bf40c7888641f24f6565ec1783. Closing pull request.

Ah okay, thanks - sorry I was too hasty!
Jon

You should be since you are a Swift programmer :+1:
I really appreciate your help. Maybe take a look at https://github.com/azawawi/SwiftyZeroMQ/issues/4.

Sure, feel free to assign to me and I will take a look.

Have fun, I am working at the moment on #3. Also I noticed a random test failure here.


[locale] (sw) Add Swahili Language Support

Hello There,
Kindly review the addition of Swahili language to the supported language list,
Cheers!

Asante! This has been deployed in<EMAIL_ADDRESS>

The pleasure is all mine :+1:


[Feature] support db2 + cassandra

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
No response
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

sink or source?

优先source，最好支持sink。


Cells run infinitely when including import of mpi4py

Describe the bug
When a cell imports mpi4py or any library importing it, the cell will execute but infinitely run on. Interestingly this only happens when importing MPI from mpi4py, not when importing mpi4py alone. Also note that code after the import will still execute, but the cell never stops thus preventing later cells from executing at all.
Now, one might say that this should not be an issue since why would you use mpi with marimo anyways, but the issue is that many libraries offer support for mpi4py, often importing it as follows:
try:
    from mpi4py import MPI
except:
    MPI = None

and thereby making mpi optional. This works perfectly well outside of marimo, but even the import in the try statement will cause the cell to run forever when executed in marimo.
Version
1.50
Code to reproduce
from mpi4py import MPI

@weidler, thanks for the very thorough bug report — I'll take a look!

Hi @weidler, I was unable to reproduce this issue unfortunately: from mpi4py import MPI works fine for me.
To debug further, it would help to have more information about your environment. Can you run marimo env at your terminal and paste the output here?

I've been unable to reproduce this. @weidler, if you are still encountering this on the latest version of marimo, please re-open

Hi @akshayka,
sorry for the late follow-up, had to finish a revision.
I reproduced the error on a different system (still Ubuntu, but 23.04 instead of 22.10) under similar conditions. I am running marimo in a conda environment. To isolate the issue I created a new conda environment and freshly installed mpi4py and marimo as follows
conda create --name marimo
conda install -c conda-forge openmpi mpi4py
pip install marimo

When running a marimo notebook inside that conda environment, the issue persists, see the screenshot below:

The stop button is unresponsive.
Conda Environment
The following are the packages installed in the environment (pip list)

Package             Version

black               23.11.0
click               8.1.7
importlib-resources 6.1.1
jedi                0.19.1
marimo              0.1.61
Markdown            3.5.1
mpi4py              3.1.5
mypy-extensions     1.0.0
packaging           23.2
parso               0.8.3
pathspec            0.11.2
pip                 23.3.1
platformdirs        4.0.0
Pygments            2.17.2
pymdown-extensions  10.5
PyYAML              6.0.1
setuptools          68.2.2
tomlkit             0.12.3
tornado             6.4
typing_extensions   4.8.0
wheel               0.42.0

Software Versions
conda 23.10.0
Python 3.12.0 (though I also reproduced on Python 3.9.17)
Ubuntu 23.04

@weidler , we hit this issue for other packages, which we've fixed. I was never able to reproduce this issue -- but can you see if it is still affecting you, on the latest version of marimo?


feat(style/feature): add quantity selector for normal products

Related issue

https://github.com/ecomplus/storefront/issues/592
Summary

Adds a quantity selector on TheProduct that makes possible to choose more than one item
Screenshots

adjustments will be made for the sake of UI like chevrons
Checklist

[ x ] I've read and understood contributing guidelines;
[ x ] If changing UI, I've tested on most common viewports, desktop and mobile devices;

A picture of a cute animal

https://github.com/ecomplus/storefront/blob/2b94b6476c24b1480facc7eaa17f9fb70786471d/%40ecomplus/storefront-components/src/js/TheProduct.js#L433


templates: Change health check url to something that's not exposed

@teg forgot to prepare the source :( Could you re-ack?

@teg forgot to prepare the source :( Could you re-ack?


how much size of target dataset is needed?

Hi,
I wanna try transfer market1501 to my own dataset
I wonder that have you ever tried how much size of target dataset is needed for
getting good transfer result for SPGAN??

Hi,
In the paper, we use the training data sets of duke and market to train SPGAN/ CycleGAN. We does not check how much size of target dataset is needed. And I think that it would be great that the number of Ur data is almost the same with Market.
Good luck!


install-kubeadm: update guides for RHEL and container linux

fixes kubernetes/kubeadm#2097
the location for the kubeadm / kubelet specs changed:
install-kubeadm: update container linux guide

- Use crictl v1.17.0
- Use new links for the dropin / unit files for kubelet and kubeadm
These now reside in k/release. Pin to v0.2.7 as the latest release
from that repository

we've seen multiple requests for this:
xref: https://github.com/kubernetes/website/pull/19997
install-kubeadm: use $basearch instead of pinning the arch for RHEL

/sig cluster-lifecycle
/kind cleanup
/priority important-longterm

/assign @kbhawkey

👀

Page preview:
https://deploy-preview-20021--kubernetes-io-master-staging.netlify.com/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl
/lgtm

/lgtm
@neolit123 Thanks for addressing the baseurl

@kbhawkey can you please approve?

/approve


Adding new field to correctly determine whether LocalDatabaseReferences was empty or not and avoid hash mismatch

Adding a new field calledto separately track whether LocalDatabaseReferences in Properties.json was empty or not.
Changing the code where "LocalDatabaseReferencesAsEmpty" was incorrectly used to check whether "LocalDatabaseReferences" was empty or not
Handling backward compatibility with the new field
Skipping Data Source References with empty Data Sources

Thanks for adding the unit test. looks good


Pull schema files from a common folder

Pull the schema files from a folder when creating the test directory (instead of having to copy a full project over)

Closed by #226.


Submissions panel - show remaining submissions count

@ mention of reviewers
@Didayolo
A brief description of the purpose of the changes contained in this PR.
In submissions panel, now users can see for each phase the following:

remaining number of submissions per day
total remaining submissions

Depending on the percentage of the remaining submissions, the color of the box will change
Green -> yellow -> Orange -> Pink -> Red
Green shows max percentage of remaining submissions while Red shows min percentage of remaining submissions
Screenshots

Issues this PR resolves

#723 -> Submissions left
#1015

Checklist

[x] Code review by me
[x] Hand tested by me
[x] I'm proud of my work
[x] Code review by reviewer
[x] Hand tested by reviewer
[x] CircleCi tests are passing
[x] Ready to merge

Nice rendering :-)

The only problem I see is that the numbers are not updated in realtime - it is needed to refresh the page.

The only problem I see is that the numbers are not updated in realtime - it is needed to refresh the page.

Maybe another issue to track this problem and fix it later


Building fails: unknown cli.Command field ‘ArgsUsage’

$ go get github.com/meshbird/meshbird
# github.com/meshbird/meshbird
.local/share/go/src/github.com/meshbird/meshbird/main.go:35: unknown cli.Command field 'ArgsUsage' in struct literal
.local/share/go/src/github.com/meshbird/meshbird/main.go:55: unknown cli.Command field 'ArgsUsage' in struct literal
.local/share/go/src/github.com/meshbird/meshbird/main.go:67: unknown cli.StringFlag field 'Destination' in struct literal
.local/share/go/src/github.com/meshbird/meshbird/main.go:74: unknown cli.StringFlag field 'Destination' in struct literal

$ go version
go version go1.5.3 linux/amd64
$ uname -a
Linux fsm 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux

Hey @kseistrup
Is this error happened at Jan 20? Because I have checked it in clean docker image
root@fce27d9b7f39:/go# go get github.com/meshbird/meshbird

no errors

It happened a few minutes before I reported the issue.

Do you have any specific options on your machine?

Nope, I just ran go get github.com/meshbird/meshbird.

Could you please try to build it on clean docker environment as I describe in my first comment? I have to find out.

I'm not using docker. I'm building from a plain bash prompt.
I'll try and wipe all caches and start again…

Try to run build with -v flag.

I removed all dirs in the $GOPATH directory, and now it built.  There must have been some rotten packages in that directory.  Thanks for your help!

No problem


Add qa4 hardware entry

:+1:  lgtm (I can not test/verify it, but should not break normal mkcloud runs), anyhow lets wait for the gating run

checked on hardware.
+1


[ZEPPELIN-3356] Kerberos ticket still expire after 7 days

What is this PR for?
The root cause is that we may do UserGroupInformation.loginUserFromKeytab multiple times if we use hdfs for several places, e.g. for notebook repo and zeppelin config. This PR fix the bug by only doing UserGroupInformation.loginUserFromKeytab one time.
What type of PR is it?
[Bug Fix ]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3356

How should this be tested?
Manually tested

Add the following properties to /etc/krb5.conf
renew_lifetime = 10m
ticket_lifetime = 5m
Add the following properties to /var/kerberos/krb5kdc/kdc.conf
max_renewable_life = 10m
max_life = 5m

Without this PR, will hit the ticket expire after 10 minutes. With this PR, the ticket is still valid after 10 minutes
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge it if no more comment


Deploy relay to integration environment

Deploy current main version of relay to integration environment.
For now this may utilize the docker image or docker-compose flow.
Eventually this should be replaced by automatic deployment upon successful PR merges

Unofficial docker-compose version deployed and present.
Waiting on OPS to be able to deploy more official one using Helm process and other CI
Closing for now


RoundCap for stacked BarChart

What problem does this feature solve?
For bar charts it is possible to use rounded corners for individual series. There is no way to round the cap for the topmost series only. This matters for cases where the value of a series can be 0 for some X-values. See the stack on the very right in my example.

What does the proposed API look like?
options: {
…
stackBorderRadius: [8, 8, 0, 0]
…
}

Yes, I'm afraid so. You can loop the series data and add itemStyle.barBorderRadius to those top-most data.

Thanks for your answer.
My problem is, that the same series won't always be at the top. In other words, if series A (green) is 0, I'd like Series B to be rounded in that stack.
I don't know if there's a way to tell echarts to do that.
What's the preferred way for examples here ? codepen/jsfiddle/jsbin…

@gehringf The top-most series is the last series with data. So technically, you do know what's on the top.

Here's a demo. https://jsfiddle.net/8a9du6n4/
I haven't been able to figure out how I could do that.

@gehringf

@100pah  Yes, this works for me 👏  Thank you so much!

Hi @gehringf,
I was trying to find a solution to this same problem and I would like to share with you a workaround here: https://jsfiddle.net/zha1fgw2/1/
I hope we won't have to wait for long for this feature.
Have a good day.

The method with manually adding rounded corners to the last series does not work if one hides a series by licking the legend.

It's also not perfect if the top most series onlymakesup a couple of pixels in height. A mask for the whole stack/bar would be helpful.

Any news ? this could still be useful natively...


Docker setup throwing : error TS2307: Cannot find module 'node:http' or its corresponding type declarations.

What version of Hono are you using?
4.0.0
What runtime/platform is your app running on?
Node.js
What steps can reproduce the bug?
Follow the documentation on this page:
https://hono.dev/getting-started/nodejs
npm create hono@latest my-app

cd my-app
npm i

You will have this in your index.ts
import { serve } from '@hono/node-server'
import { Hono } from 'hono'

const app = new Hono()

app.get('/', (c) => {
  return c.text('Hello Hono!')
})

const port = 3005
console.log(`Server is running on port ${port}`)

serve({
  fetch: app.fetch,
  port
})

Creating the Dockerfile
FROM node:20-alpine AS base

FROM base AS builder

RUN apk add --no-cache libc6-compat
WORKDIR /app

COPY package*json tsconfig.json src ./

RUN npm ci && \
    npm run build && \
    npm prune --production

FROM base AS runner
WORKDIR /app

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 hono

COPY --from=builder --chown=hono:nodejs /app/node_modules /app/node_modules
COPY --from=builder --chown=hono:nodejs /app/dist /app/dist

USER hono
EXPOSE 3000

CMD ["node", "/app/dist/index.js"]

The following steps shall be taken in advance.
Add "outDir": ". /dist" to the compilerOptions section tsconfig.json.
Add "exclude": ["node_modules"] to tsconfig.json.
Add "build": "tsc" to script section of package.json.
Run npm install typescript --save-dev.
When you finally go to create the docker image with
docker build -t hono-docker .

You will get the error:
 > [builder 4/4] RUN npm ci &&     npm run build &&     npm prune --production:
1.615
1.615 added 11 packages, and audited 12 packages in 1s
1.615
1.615 2 packages are looking for funding
1.615   run `npm fund` for details
1.615
1.615 found 0 vulnerabilities
1.616 npm notice
1.616 npm notice New minor version of npm available! 10.2.4 -> 10.4.0
1.616 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.4.0>
1.616 npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
1.616 npm notice
1.742
1.742 > build
1.742 > tsc
1.742
2.555 node_modules/@hono/node-server/dist/listener.d.ts(1,49): error TS2307: Cannot find module 'node:http' or its corresponding type declarations.
2.555 node_modules/@hono/node-server/dist/listener.d.ts(2,57): error TS2307: Cannot find module 'node:http2' or its corresponding type declarations.
2.555 node_modules/@hono/node-server/dist/server.d.ts(1,29): error TS2307: Cannot find module 'node:net' or its corresponding type declarations.
2.555 node_modules/@hono/node-server/dist/types.d.ts(1,105): error TS2307: Cannot find module 'node:http' or its corresponding type declarations.
2.555 node_modules/@hono/node-server/dist/types.d.ts(2,196): error TS2307: Cannot find module 'node:http2' or its corresponding type declarations.
2.555 node_modules/@hono/node-server/dist/types.d.ts(3,82): error TS2307: Cannot find module 'node:https' or its corresponding type declarations.
2.555 node_modules/hono/dist/types/context.d.ts(54,5): error TS18028: Private identifiers are only available when targeting ECMAScript 2015 and higher.
2.555 node_modules/hono/dist/types/context.d.ts(134,5): error TS2300: Duplicate identifier 'render'.
2.556 node_modules/hono/dist/types/hono-base.d.ts(58,5): error TS18028: Private identifiers are only available when targeting ECMAScript 2015 and higher.
2.556 node_modules/hono/dist/types/request.d.ts(16,5): error TS18028: Private identifiers are only available when targeting ECMAScript 2015 and higher.
------
Dockerfile:10
--------------------
   9 |
  10 | >>> RUN npm ci && \
  11 | >>>     npm run build && \
  12 | >>>     npm prune --production
  13 |
--------------------
ERROR: failed to solve: process "/bin/sh -c npm ci &&     npm run build &&     npm prune --production" did not complete successfully: exit code: 2

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/4azjzio33qpvfftx7cblxkp8j

What is the expected behavior?
After following the instructions I am able to successfully build a containerized hono node.js application.
What do you see instead?
After following the instructions I get and error when building the docker container.
Additional information
No response

Hello @tony-garand. I was able to reproduce your issue and solve it by installing @types/node as a dev dependency, similar to how you install typescript: npm install -D @types/node
You may not be experiencing the error locally (i.e outside of docker) likely because you already installed the types package globally at some point!
If this works for you, we can probably re-label this as not a bug with hono itself!

Duplicated #2184


[3.x] Fix Copy Selection on editor_log

After the addition of deselect_on_focus_loss_enabled to RichTextLabel the 'Copy Selection' button on editor log no longer works because clicking on the button will cause a focus loss and the text is deselected.
Setting deselect_on_focus_loss_enabled to false restore the correct button behavior.
Even if master if not affected from this problem, we can do the same change also in master branch, sometimes it might be useful to keep the text selected on output log panel even the focus is lost.

How do you then deselect text? I think users might be puzzled by permanently selected content in their Output dock.
CC @EricEzaM @groud @KoBeWi

How do you then deselect text? I think users might be puzzled by permanently selected content in their Output dock.
CC @EricEzaM @groud @KoBeWi

You can deselect by clicking somewhere inside the Output dock.
deselect_on_focus_loss_enabled is set to false also in the code editor, so with this change the Output dock will behave the same.

I see, that makes sense then IMO. I would also suggest doing the same for master.

Thanks!


Unclear minimum license requirements for Powerapps Portals

It is not clear in the article whether are not you have to buy the Page Views add-on if all content that is hosted in the portal is behind a login-page (and not available anonymously).

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

ID: a2cad5bd-4ffa-3671-0364-95e5b6f65256
Version Independent ID: 6d0cc055-b7be-02d7-3ba8-55e400ccd21b
Content: Power Apps and Power Automate licensing FAQs - Power Platform
Content Source: power-platform/admin/powerapps-flow-licensing-faq.md
Service: power-platform
GitHub Login: @dileepsinghmicrosoft
Microsoft Alias: dileeps

@NathanSushi
Sorry for the delayed response. Licensing content is frequently being rewritten. Please reopen if this is still an issue.


CLOUD-433 fixed encrytion validation

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/922/


compareSync

how to compare hash using compareSync ?

I'm working on it.

use the latest version 1.1.1 for the feature


update outdated npm packages to wanted versions by npm

[ Yes ] I have reviewed the contributor guidelines.
[ Yes ] I have reviewed the code of conduct.
[ Yes ] Per GitHub's Terms of Service, I am aware that I license my
contribution under the same terms as this project's license, and
that I have the right to license my contribution under those terms.

cc: @mbland

Coverage remained the same at 98.194% when pulling 23bdee2bfe3cd595182bfa35adb9110078fff985 on update-packages into bad49ebc79727057ccea2395de9edc0f90700ade on master.

Coverage remained the same at 98.194% when pulling 23bdee2bfe3cd595182bfa35adb9110078fff985 on update-packages into bad49ebc79727057ccea2395de9edc0f90700ade on master.

Chromium started failing with the same issue as in https://github.com/mbland/custom-links/pull/169, so we had to Chromium to the list of filters to work around karma-detect-browsers


Full Season interactive search error

If I do an interactive Season search for a full season (Soko Stuttgart Season 16) the Mediathekarr Indexer goes in Error state.
When I do an interactive search for each episode for itself it's no problem. And it gets downloaded correctly.

Should be fixed with https://github.com/PCJones/MediathekArr/releases/tag/v1.0-alpha.1


Adding the WHO Vaccination dataset

This is a fairly straightforward import apart from I need to use a variable from the UN WPP dataset. It's the population of one-year-olds, so not in the key indicators dataset. I'm not sure what the best way to access this is? Any tips on this would be appreciated!

This is a fairly straightforward import apart from I need to use a variable from the UN WPP dataset. It's the population of one-year-olds, so not in the key indicators dataset. I'm not sure what the best way to access this is? Any tips on this would be appreciated!

I think what you are doing is ok, you are using a table from another dataset to construct this new table. That's fine. The only think you were missing is to explicitly declare that dependency in the dag.

This is a fairly straightforward import apart from I need to use a variable from the UN WPP dataset. It's the population of one-year-olds, so not in the key indicators dataset. I'm not sure what the best way to access this is? Any tips on this would be appreciated!

I think what you are doing is ok, you are using a table from another dataset to construct this new table. That's fine. The only think you were missing is to explicitly declare that dependency in the dag.

Thanks @pabloarosado!

@Marigold Am I okay to merge despite the buildkite check fails? I can't see what they are - would someone be able to invite me to buildkite?

@spoonerf it's ok for this one, it's not very stable yet. It should get more stable in a few days though. Go ahead and merge it! (and please don't forget to squash)


Bug fix on getArgCanonical

Pull Request Test Coverage Report for Build 511

8 of 8 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 82.288%

Files with Coverage Reduction
New Missed Lines
%

lib/describe.js
1
77.88%

Totals

Change from base Build 510:
0.02%

Covered Lines:
5860

Relevant Lines:
6938

💛  - Coveralls

@gcampax


Other properties in the returned comment are dummy while edit comment

Testing #59278
'use strict';
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';

// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {

    const _onDidChangeDocumentCommentThreads = new vscode.EventEmitter<vscode.CommentThreadChangedEvent>();

    vscode.workspace.registerDocumentCommentProvider({
        onDidChangeCommentThreads: _onDidChangeDocumentCommentThreads.event,
        provideDocumentComments: async (document: vscode.TextDocument, token: vscode.CancellationToken): Promise<vscode.CommentInfo> => {
            return {
                threads: [{
                    threadId: '1',
                    resource: document.uri,
                    range: new vscode.Range(new vscode.Position(0, 0), new vscode.Position(0, 0)),
                    comments: [{
                        commentId: '1',
                        body: new vscode.MarkdownString('hello world'),
                        userName: 'me',
                        gravatar: '',
                        canEdit: true,
                        canDelete: true
                    }]
                }],
                commentingRanges: []
            }
        },
        createNewCommentThread: async (document: vscode.TextDocument, range: vscode.Range, text: string) => {
            throw new Error('Not implemented');
        },
        replyToCommentThread: async (document: vscode.TextDocument, range: vscode.Range, thread: vscode.CommentThread, text: string) => {
            throw new Error('Not implemented');
        },
        editComment: async (document: vscode.TextDocument, comment: vscode.Comment, text: string, token: vscode.CancellationToken) => {

            return {
                commentId: '10',
                body: new vscode.MarkdownString(text),
                userName: 'me',
                gravatar: '',
                canEdit: false,
                canDelete: false
            };
        },
        deleteComment: async (document: vscode.TextDocument, comment: vscode.Comment, token: vscode.CancellationToken) => {
            return null;
        }
    });
}

// this method is called when your extension is deactivated
export function deactivate() {
}

In editComment, I am returning a comment that does not support edit and delete. This is not being considered. Also setting commentId (may be other properties) does not have impact. If they are not considered we should not return the comment instead updated text?

Ah, good point. I'm going to change the return type to Promise<void>, since the core already has the updated text, it doesn't actually need anything back from the extension.


Audit deleted characters and set up a after_destroy hook

It used to be visible here (in Opalescence > Incendium). UI showed "/characters/old_id" for the character name.

There's already an after_destroy hook.


docs(endpoint): adding example regarding parsing url params

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Changes
Hi, thanks for the amazing job on this project. I have been using SvelteKit for a while, but wasn't able to find a proper example on how to access params sent using URL params: /foo?a=1&b=2.
This PR adds an example regarding the use of URL search params using endpoints.
Note: I sent this fix at #4552 , but it looks like the pull bot ended up removing my changes. 😓

We already mention here that url.searchParams is an instance of URLSearchParams. Maybe we could also link to the MDN page here from the routing section, but I don't think we want to be in the business of telling people how to use web APIs that are well-documented elsewhere.

We already mention here that url.searchParams is an instance of URLSearchParams. Maybe we could also link to the MDN page here from the routing section, but I don't think we want to be in the business of telling people how to use web APIs that are well-documented elsewhere.

Nice point! What about link/explain that the object received at an endpoint inherits this property? I found it confusing to understand how to access this parameters without rendering using the load

In the meantime, I made some suggestions in case we had a change of heart and did want to go down this route

No problem, I ended up applying these suggestions and changing the status code at the example to 200 since it's a GET.  😄

https://github.com/sveltejs/kit/pull/4618

merged #4618, so I'll close this — thanks