Sometimes videos play with a green line on the side

I've had this green line appear on both the left and right sides of the video

Strange. And this only happens sometimes?

Strange. And this only happens sometimes?

Yes, here is another example I just got today. I'd say it has like a 1/15 incidence

https://user-images.githubusercontent.com/53708281/111006293-8ebd5480-835a-11eb-8882-90df0e0a9667.mov

My guess is that this only happens with .MOV files, but I can't verify that. I'll pay more attention the next time I notice it

My guess is that this only happens with .MOV files, but I can't verify that. I'll pay more attention the next time I notice it

Can you try and confirm this a bit more. If that's the case, then it's ffmpeg kinda screwing up the conversion. Or quite possibly that the totalBytes do not align correctly after converting to an mp4. Not sure

Here are some things I found on the internet

{"Protocol":"File","Id":"ff7b22de5bbef3bf19afdf7f4cc5013b","Path":"C:\12.Angry.Men.1957.1080p.BluRay.x265-RARBG\\12.Angry.Men.1957.1080p.BluRay.x265-RARBG.mp4","Type":"Default","Container":"mov,mp4,m4a,3gp,3g2,mj2","Size":1608809600,"Name":"12.Angry.Men.1957.1080p.BluRay.x265-RARBG","IsRemote":false,"ETag":"76dfa171a07a785708a9e9491cac26ea","RunTimeTicks":57688109056,"ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"RequiresLooping":false,"SupportsProbing":true,"VideoType":"VideoFile","MediaStreams":[{"Codec":"hevc","CodecTag":"hev1","Language":"und","TimeBase":"1/1200000","CodecTimeBase":"1001/24000","VideoRange":"SDR","DisplayTitle":"1080p HEVC","IsInterlaced":false,"BitRate":2000303,"RefFrames":1,"IsDefault":true,"IsForced":false,"Height":1080,"Width":1800,"AverageFrameRate":23.976215,"RealFrameRate":23.976025,"Profile":"Main 10","Type":"Video","AspectRatio":"5:3","Index":0,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p10le","Level":120},{"Codec":"aac","CodecTag":"mp4a","Language":"eng","TimeBase":"1/48000","CodecTimeBase":"1/48000","DisplayTitle":"Eng AAC mono Default","IsInterlaced":false,"ChannelLayout":"mono","BitRate":224000,"Channels":1,"SampleRate":48000,"IsDefault":true,"IsForced":false,"Profile":"LC","Type":"Audio","Index":1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0}],"MediaAttachments":[],"Formats":[],"Bitrate":2231045,"RequiredHttpHeaders":{}}

C:\Program Files\Jellyfin\Server\ffmpeg.exe -ss 00:00:18.000 -noaccurate_seek -init_hw_device qsv=hw -filter_hw_device hw -i file:"C:\12.Angry.Men.1957.1080p.BluRay.x265-RARBG\12.Angry.Men.1957.1080p.BluRay.x265-RARBG.mp4" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 h264_qsv -preset medium -look_ahead 0 -b:v 8001212 -maxrate 8001212 -bufsize 16002424 -profile:v high -level 4.1  -g 72 -keyint_min 72 -sc_threshold 0 -vf "vpp_qsv=format=nv12" -start_at_zero -vsync -1 -codec:a:0 libmp3lame -ac 1 -ab 224000  -copyts -avoid_negative_ts disabled -f hls -max_delay 5000000 -hls_time 3 -individual_header_trailer 0 -hls_segment_type mpegts -start_number 6 -hls_segment_filename "C:\ProgramData\Jellyfin\Server\transcodes\0ce9cbe7875a9abb5ab488515d42fd23%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "C:\ProgramData\Jellyfin\Server\transcodes\0ce9cbe7875a9abb5ab488515d42fd23.m3u8"

ffmpeg version n4.3.1-1-g4c6eb642fe Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 10.1.0 (Rev3, Built by MSYS2 project)
  configuration:  --disable-static --enable-shared --cc='ccache gcc' --cxx='ccache g++' --disable-ffplay --disable-debug --enable-gpl --enable-version3 --enable-bzlib --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-fontconfig --enable-gmp --enable-libass --enable-libzimg --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libwebp --enable-libx264 --enable-libx265 --enable-libdav1d --enable-opencl --enable-dxva2 --enable-d3d11va --enable-amf --enable-libmfx --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvenc --enable-nvdec --enable-ffnvcodec --enable-gnutls --shlibdir=/local64/bin-video
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'file:C:\12.Angry.Men.1957.1080p.BluRay.x265-RARBG\12.Angry.Men.1957.1080p.BluRay.x265-RARBG.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2mp41
    creation_time   : 2020-04-04T20:47:05.000000Z
    title           : 12.Angry.Men.1957.1080p.BluRay.x265-RARBG
    encoder         : Lavf58.20.100
    comment         : 12.Angry.Men.1957.1080p.BluRay.x265-RARBG
  Duration: 01:36:08.81, start: 0.000000, bitrate: 2231 kb/s
    Stream #0:0(und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(tv), 1800x1080 [SAR 1:1 DAR 5:3], 2000 kb/s, 23.98 fps, 23.98 tbr, 1200k tbn, 23.98 tbc (default)
    Metadata:
      creation_time   : 2020-04-04T20:47:05.000000Z
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 224 kb/s (default)
    Metadata:
      creation_time   : 2020-04-04T20:47:05.000000Z
      handler_name    : SoundHandler
Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_qsv))
  Stream #0:1 -> #0:1 (aac (native) -> mp3 (libmp3lame))
Press [q] to stop, [?] for help
Output #0, hls, to 'C:\ProgramData\Jellyfin\Server\transcodes\0ce9cbe7875a9abb5ab488515d42fd23.m3u8':
  Metadata:
    encoder         : Lavf58.45.100
    Stream #0:0: Video: h264 (h264_qsv), nv12, 1800x1080 [SAR 1:1 DAR 5:3], q=-1--1, 8001 kb/s, 23.98 fps, 90k tbn, 23.98 tbc (default)
    Metadata:
      encoder         : Lavc58.91.100 h264_qsv
    Side data:
      cpb: bitrate max/min/avg: 8001212/0/8001212 buffer size: 16002424 vbv_delay: N/A
    Stream #0:1: Audio: mp3 (libmp3lame), 48000 Hz, mono, fltp, 224 kb/s (default)
    Metadata:
      encoder         : Lavc58.91.100 libmp3lame

This is strange. Both the Michael Stevens video and this video were sent from WebMessage as mp4's that I ripped from YouTube, but in BlueBubbles Android, they were MOV's. I suspect this will happen with all videos that I rip from YouTube, I will test it further, as well as sending the mp4's from BlueBubbles Desktop

https://user-images.githubusercontent.com/53708281/113324429-14427d80-92e5-11eb-90f1-04b38f6e4228.mov

Here is another example. This video, just like the two videos above it, is a YouTube video that I downloaded using the mp4 option from this website.

https://user-images.githubusercontent.com/53708281/118576111-de067380-b755-11eb-9c67-784f74c2db94.mp4

Related to another ticket. Closing: https://github.com/BlueBubblesApp/BlueBubbles-Android-App/issues/817


Failed to import -There are cross-domain problems in privatization deployment.

Error message

There is a cross-domain problem when using privatization links, but there is no cross-domain problem when using the domain name of esm.sh
Could you please help me? Do I need to configure this in the config.json?
Additional info

esm.sh version: v135
Browser version:Chrome/<IP_ADDRESS>

@xiangyin1987 i think you need to enable https


Document email setup

Problem
Supabase has disabled email sending without a custom domain see https://github.com/orgs/supabase/discussions/29370 ).
Solution
Document configuring the SMTP provider on the Supabase dashboard

I agree, I'd like more details, even if this means copying part of the supabase doc.


Revise docs content

Description
The docs could benefit from some revision where sections that come of as a bit unclear or to difficult to understand are improved.
Acceptance criteria

More "advanced" concepts are clearly explained.
All content is written in an active voice and follows a similar structure as the Raiden (GitBook) docs.

Tasks

[ ]

It should also be clarified whether the docs should explain how to develop with the dApp or build a minimal app from scratch. If the dApp is not necessary then we don't need the user to e.g. clone the repo etc

@nephix The existing documentation is about contributing or playing around with everything.
The documentation for developers using the SDK doesn't exist at the moment. The guide for the developers building on top of the SDK should be a new section in the documentation.

The guide for the developers building on top of the SDK should be a new section in the documentation.

Probably the main section and focus, as that is most likely the main use case for someone who accesses the docs page?

Outdated


Create an option to accept custom tags

Now, the code accepts only html known tags. What about the custom tags coming from frameworks ? We should create an option to accept that.

Some illustrations of custom tags: https://hilla.dev/


App stops when I try to capture an image.

Steps to reproduce
1.Open Camera App
2.Try to capture image
3.
Expected behaviour
The app should take a picture and console log the result.
Actual behaviour
The App stop and close when a take a picture
Environment

Node.js version:latest
React Native version: latest
React Native platform + platform version: Android 5.0, 6.0, 7.0

react-native-camera
Version: npm version

Does this happen on Android or iOS or both? I'm facing a similar issue with a "Samsung Galaxy S5 Neo". I'm able to see the camera view but when I take the picture it breaks. On the other hand, it works if I use the front camera and also if I use any other phone (iphone, htc or whatever else).. any idea?

I managed to make it work on my device (sansung S5), using the front camera, I just added the captureTarget property, but the simulator did not work. As you said now from the other camera I will test here.

I trying here right now and a I had the same problem. So I dont Know what to do .

I must say that it only happens with the Samsung S5. I will research but you don't get any information at all why it breaks...

Had this same problem the other day and fixed it by changing quality to 1080p, instead of the default "high".  Seems to be an issue with handing the default, which i assume is why the front camera has no problem.

@jlyons you were right! Changing the captureQuality attribute to 1080p or lower it solves the problem 👌🏻

@jlyons  I was cracking my head trying to know why, thanks for the help

Can confirm this issue on my iPhone 5.
@juanluisgv1 Unfortunately playing with the captureQuality did not fix it for me. Front camera is not even accessible, it shows only black.
Environment
Node 7.4.0
React Native 4.0

Im having the same issue with a samsung galaxy s5. The app crashes every time I take a picture with back camera but works fine with front camera. I tried reducing the capture quality but that didn't work for me.

@zawarudo works for me! thanks!

I was having the same problem and managed to fix it by adding android:largeHeap="true" to my AndroidManifest.xml.
<application
      android:name=".MainApplication"
      android:allowBackup="true"
      android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
      android:theme="@style/AppTheme"
      android:largeHeap="true">

Problem seems to be in the fixOrientation method, when set to a high capture quality the device runs out of memory and crashes.

Have you tried master?  afixOrientationisn't applied any more (unless you explicitly specify it).  I understand that usingandroid:largeHeap="true"` isn't recommended (although I can't remember why).

I installed the version for RN >0.40. I believe it's version 0.6 and it was still happening there. I'd rather reserve a large heap for my app (although someone does not recommend it) than have it crash

I am using OnePlus 3 with Android 7.1.1. None of these work for me. Works fine in Zenfone 2 and iPhone 7 plus though.

NSPhotoLibraryAddUsageDescription

@heliocaruccio - Works for me. Many thanks!

I have the same issue, but just on the release apk, on the debugging works perfect, but release is the important one.
<Camera
          ref={(cam) => {
            this.camera = cam;
          }}
          style={styles.preview}
          aspect={Camera.constants.Aspect.fill}
          captureQuality={Camera.constants.CaptureQuality["480p"]}
          type={Camera.constants.Type.front}>
          <TouchableOpacity
              style={styles.captureButton}
              onPress={this.takePicture.bind(this)}
          >
            {imgCamera}
          </TouchableOpacity>
        </Camera>

takePicture() {
    const options = {jpegQuality: 1};
    this.camera.capture({metadata: options})
      .then((data) => {
        //console.log(data);
        this.props.navigation.navigate('DrawRectangle',
          {
            pictureData: data
          }
        );
      })
      .catch(err => console.error(err));
  }

The application requires low quality picture.

I'm using RNCamera like this
takePicture = async () => {
        const options: TakePictureOptions = {
            // quality: 0.9,
            base64: true,
            exif: false,
            // width?: number;
            // mirrorImage?: boolean;

            /** Android only */
            // skipProcessing?: boolean;
            /** Android only */
            fixOrientation: true,

            /** iOS only */
            forceUpOrientation: false
        };
        this.camera.takePictureAsync(options)
            .then(data => console.log(data.base64))
            .catch(error => console.log(error));
    };
render() {
        return (
            <View style={styles.container}>
                <RNCamera
                    ref={cam => {
                        this.camera = (cam as RNCamera);
                    }}
                    style={styles.preview}
                    type={RNCamera.Constants.Type.back}
                >
                    <TouchableHighlight onPress={this.takePicture}>
                        <Image
                            style={{ flex: 0, width: 100, height: 100 }}
                            source={require('./images/cameraButton.png')}
                        />
                    </TouchableHighlight>
                </RNCamera>
            </View>
        );
    }

when type={RNCamera.Constants.Type.front} it works. If I use back it fails. App closes and says "Unfortunately app has stopped....."
I've added things to manifest like exif 27+, android:largeHeap="true" and other things but it doesn't help.

Please open a new issue with crashlogs if you still experience this issue with the newest version and RNCamera.


Add Sane filesystem watcher

Link to repo: sane
Very simple to use.

Thanks, but chokidar is IMHO better and already on the list, so gonna pass on this.


Revise Templates page

Templates page in Admin area needs some minor changes for consistency w/other pages:

rename "Own Templates" table heading to "[Org Name] Templates"
next table should be "Default template" (singular)
then "Funder templates" table
add pagination to tables w/more than 10 items
standardize table layout so all column widths match across 3 tables
add search box? if so do we need one above each table? only if more than 10 items?

@stephaniesimms can this one be closed. It seems like everything is covered by either #900 or #815

yessir @briri - closing this issue.


[SPARK-45378][CORE] Add convertToNettyForSsl to ManagedBuffer

What changes were proposed in this pull request?
As the title suggests. In addition to that API, add a config to the TransportConf to configure the default block size if desired.
Why are the changes needed?
Netty's SSL support does not support zero-copy transfers. In order to support SSL using Netty we need to add another API to the ManagedBuffer which lets buffers return a different data type.
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI. This will have tests added later - it's tested as part of https://github.com/apache/spark/pull/42685 from which this is split out.
Was this patch authored or co-authored using generative AI tooling?
No

cc: @mridulm @JoshRosen this is now ready to review and has all green tests on CI

QQ: If/when there is more widespread adoption of kernel.ssl.sendfile (and ssl_sendfile from openssl), how will it impact the proposed design ?

@mridulm once it's widely adopted and supported in Netty + netty-tcnative, we can remove these APIs and potentially just use convertToNetty, depending on how the design is from the netty side. But it's unclear to me what the timelines are for that

Sounds good, can you add a comment to that effect in the Trait ?
Rest looks good to me

CI is also finally green here

Merged to master.
Thanks for working on this @hasnain-db !
Thanks for review @JoshRosen :-)


add section about code style to contributing.md

Signed-off-by: Norbert Varzariu<EMAIL_ADDRESS>Description
This PR adds a "code style conventions" section to the contribution document, pointing out that black should be used as the default code formatter.
Type of change
Please make your selection.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
[ ] This change requires a new dependency
[ ] Code Maintainability / comments
[ ] Code Refactoring / future-proofing

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist:

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added pytest unit tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@whittlem I didn't bump the version for just the doc change, as there will be quite some changes coming into the main branch soon. Is this fine or should I still increment the version, even though we just update documentation?


Simple notifications

This is a bit of a complicated change :(
Because the plan for notifications radically changed during development, there is work here that's been undone. It seemed like a good idea to not drop the history of the older version of notifications for reference as there's a chance that some of it will come back in future iterations.
Everything before Merge branch 'notifications-master' into simple-notifications had already been reviewed and was awaiting merging, so it's only the subsequent changes that are of interest to this PR.

Main changes since the previous iteration of notifications:

removal of time-based security profile totals
removal of most notification rules (only monitored prisoners and payment sources remain)
notifications are now retrieved by date ranges so a new view is needed to hint at the correct date range for xx days to be returned

removal of time-based security profile totals

RUINED


Document API change log for relative image URL

The changes are in the Pull Request's .idl file

PR was merged - closing


[Event Request] Codeunit 392 Reminder-Make - MakeReminder

We have a requirement to fill additional fields on the reminder header before inserting. We would like to request the following publisher in function 'MakeReminder':
        IF ReminderHeader.FINDFIRST THEN
          EXIT(FALSE);
        ReminderHeader.INIT;
        ReminderHeader."No." := '';
        ReminderHeader."Posting Date" := ReminderHeaderReq."Posting Date";
        ///// START
        OnBeforeInsertReminderHeader(ReminderHeader, ReminderHeaderReq, ReminderTerms, Cust);
        ///// END
        ReminderHeader.INSERT(TRUE);
        ReminderHeader.VALIDATE("Customer No.","No.");
        ReminderHeader.VALIDATE("Currency Code",CurrencyCode);
        ReminderHeader."Document Date" := ReminderHeaderReq."Document Date";
        ReminderHeader."Use Header Level" := ReminderHeaderReq."Use Header Level";

The signature of the publisher:
[Integration]
LOCAL PROCEDURE OnBeforeInsertReminderHeader@11095600(VAR ReminderHeader@11095585 : Record 295;ReminderHeaderRequest@11095588 : Record 295;ReminderTerms@11095587 : Record 292;Customer@11095586 : Record 18);
BEGIN
END;

Many thanks.

This issue is labeled as 'ships in future' update however I don't see it in the daily build. Instead the publisher OnBeforeReminderHeaderModify has its parameters extended.
However this change does not meet our requirements. We need to fill fields before the insert and we need reminder request and terms varaible. Sadly it is not possible to do at modify level because we control the no. series in a different way. Would it be possible to introduce OnBeforeInsertReminderHeader anyway?


equation in P02-C07 doesn't render correctly

@smolix  - looks like @srochel found a LaTeX bug. - It's also possible that his browser is slow. Equations show up like this before mathjax renders them ...

it looks fine for me. please feel free to reopen this issue if this bug still exists


CTD - NullReferenceException

Stack trace:

Didn't generate a crash log, nothing in the rgl logs.
Initial crash happened midgame after about 20 days of a new campaign. Now crashes on startup with the above. Running version e1.2.0

This should be fixed in the latest version of the mod.


improve trigger hold behavior

Currently triggers keep firing when a button/key trigger (e.g: 'B' keyboard button) is held down. That is incorrect, they should only fire on the Press and Release of inputs. Possibly a Holding could be added to have actions repeatedly fire while a trigger is held.

Closing this because I'm not sure if a Holding state/trigger is useful, nor do I know in what way to implement it.
If anyone feels like they're missing something that looks like this, please do let me know.


Change code example to show Preview 2 new feature

Description
Update the article to include this new feature.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/security/authentication/mfa?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/security/authentication/mfa.md
Document ID
761ea2cc-7e05-4ae0-0875-44061a163621
Article author
@damienbod

Associated WorkItem - 240645

@damienbod Thank you for the review and the spacing fix!


Update MARS links

Links to
https://courses.missouristate.edu/KenVollmar/mars/
should now point to
https://github.com/dpetersanderson/MARS/

This is the original MARS, developed by Pete Sanderson and Ken Vollmar. Developed while Pete was professor at Otterbein University and Ken was professor at Missouri State University. Both are now retired. This is a legacy application but is very stable and continues to be used by universities throughout the world as of 2024. The last release was MARS 4.5 in August 2014. Until September 2024 the MARS website, including executable JAR file download, was hosted by Missouri State University. That is no longer the case.

Resolved by https://github.com/exercism/mips/pull/285


Would love to have settings to disable the following

I would love to see a setting to disable them for, in order of priority:

no counter on the notifications at the top bar

not seeing the "people also viewed" feature (currently only possible on one's own profile) and "people you may know" when on someone's else's profile

no counter on "my pages notifications", "impressions of your post" and "who viewed your profile".

not seeing "People who follow [name] also follow"

Also, a way to turn off animations. Too many stories have unnecessarily animated graphics, and the animated reaction buttons attached to nearly everything are an unforgivable design offense. I have "Autoplay videos" turned off, but this preference setting isn't honored for animated gifs, and it absolutely should be.


check existence of individual database files

Currently only the existence of the database directory is checked. It would be useful if each database file used is checked before any processing occurs.
Steps to repeat:
mkdir empty_folder
agrvate ERX204841.fna empty_folder/
cat: ERX204841-results/ERX204841-agr_gp.tab: No such file or directory
cat: ERX204841-results/ERX204841-agr_gp.tab: No such file or directory
Unable to agr type

Error: File existence/permissions problem in trying to open query file empty_folder//agrD_hmm.hmm.
HMM file empty_folder//agrD_hmm.hmm not found (nor an .h3m binary of it)

grep: ERX204841-results/ERX204841-hmm.tab: No such file or directory
Unable to find agrD
usearch11.0.667_i86linux32 not in path, cannot perform frameshift detection
 please download usearch11.0.667_i86linux32 from https://www.drive5.com/usearch/download.html

Done! Individual files are now checked for and only if all the required filenames are found the process continues.
If the contents of the files themselves are modified the process will still run however the output might be affected. Will eventually come up with a way to handle this

Done! Individual files are now checked for and only if all the required filenames are found the process continues.
If the contents of the files themselves are modified the process will still run however the output might be affected. Will eventually come up with a way to handle this


Bug in Getting Started Guide (easy workaround)

Bug report

What is the current behavior?
The Getting Started guide fails at the end of the Creating a Bundle section.
If the current behavior is a bug, please provide the steps to reproduce.
Follow the guide as is.

What is the expected behavior?
At the end of that section, the browser should display Hello webpack, but instead you get a syntax error in the middle of the minified javascript.

So it looks like there's some kind of compatibility issue between the lodash library and the default minimizer used in production mode (which the guide uses since it's the default mode and it's not specified.) I think the escaped values in lodash/_deburrLetter.js are getting translated into their literal values, and in the process of doing that one of the values ends up missing quotes for some reason and causes a syntax error.
An easy work-around in the guide is to set the mode to development, which is probably fine for the purposes of the guide.
Figured I'd report this for the benefit of people like me who are just getting started with webpack.
Other relevant information:
webpack version:  4.35.3
Node.js version: 12.5.0
Operating System: macos (darwin)
Additional tools:

https://webpack.js.org/guides/getting-started/

Hi @unixfreak0037
I will look into this tonight, ty for reporting

Just tested it, could not reproduce. Versions used:
  "devDependencies": {
    "webpack": "^4.35.3",
    "webpack-cli": "^3.3.5"
  },
  "dependencies": {
    "lodash": "^4.17.14"
  }

Maybe this is related to Node.js version? I am at v10.16.0

Yes, you are correct. I just tested that myself using version 10.16.0 and it worked, switched to version 12.5.0 and got the syntax error.

Right, if that is a default (did you use brew?), we might want to drop a warning about LTS versions

Yep. Brew on the mac and apt on ubuntu.

Thank you, that cleard it up

As of now (April 26, 2020) the LTS version is beyond 12.5 as the added disclaimer notes. It is currently 12.16.2.
No different versions worked for me either. I had to put it in development mode for the page to load properly.
It tried:
10.16.0
10.16.2
12.16.2
12.15.0


Can I click the geometry and get the dxf element info?

No, the dxf drawing is not interactive by default and is not within the scope of this library.


Nodes as computed property breaks the component; "reading 'parentNode'" issue

When clicking on root nodes, they don't open or close; the only needed modification to your example code is changing nodes from data to computed property:

https://codesandbox.io/s/basic-forked-6858hx?file=/src/App.vue

I'm also getting console errors, though they don't show in codesandbox:

During initialization, once per root node: Uncaught (in promise) TypeError: node.value.state is undefined
When clicking on a root node: Uncaught TypeError: node.value.state is undefined

When I add state: {} to each node, the error disappears, but I still can't interact with root nodes.
When I add state: { opened: true } to each node, I still can't interact, but at least they are all initially open.

✔ The solution is to explicitly open the nodes by using something like @node-toggle="(node: ItemType) => open[node.id] = !open[node.id]" and assign the state within computed property.

❗ We must duplicate id inside object, because the node's object key isn't available in event.
📔 (Adding @node-focus also lets us open the node by clicking on its name - I'd prefer the option to opt-in to this behavior even implicitly, without having to use state.)

User experience: de-focus, closing and opening a root node registers it as a double-click and selects text in children

I also have a major issue, making this component completely unusable: when there are many reactive changes to the elements, under some circumstances, I start receiving errors like these, for example when I click to expand a parent node (it won't expand):

Sadly, I was unable to reproduce this as a minimum repro project, as it only happens when I use the component in my existing, larger project (where I had previously used Vuetify 2's component), thus I don't know the root cause of this. There is a certain number of reactive updates that must be performed before the issue manifests, it doesn't happen under simple scenarios. I'm giving up on this component, hoping for Vuetify 3 to implement it soon.

I'm sorry but since you can't reproduce, I'm affraid I can't do anything for you :/


String.count -> UInt8 link fail

So far, the following sample code has failed in two separate projects for me:
let a = "asdf".count
let b = UInt8(a)

Compilation appears to succeed, but fail on the linking step. Let me know if you need more to go on.
Oh - working with espidf and compiling to an esp32c3, if any of that matters.

Is this still an issue with new toolchains? I was not able to reproduce any issues with the above snippet:
➜  Desktop cat foo.swift
let a = "asdf".count
let b = UInt8(a)
➜  Desktop swiftc foo.swift -emit-object -o foo.o -enable-experimental-feature Embedded -wmo -target armv7em-apple-none-macho -Xcc -D__APPLE__ -Xcc -D__MACH__
➜  Desktop swiftc --version
Apple Swift version 6.1-dev (LLVM 89ccf4b8a46135a, Swift 6a5ae8d5df144dd)
Target: arm64-apple-macosx15.0


Azure transcription merge different channel files

Hi All
I have a question is there a way we can merge the channel0.json and channel1.json files to create a single transcription file?
Please let me know if possible , how we can achieve this ? I was checking the both the files but I did not get any clue as to how we can establish the relation between them and merge.
Thanks in advance!

If you want to merge transcription text from 2 separate channels, you can use the SegmentResults which list each transcribed utterance along with offset and duration. Based on offset/duration you can merge texts from both channel0.json and channel1.json.

Thank you @zhouwangzw  for the reply. One clarfication , do I have to use both of them or one can serve the purpose?

For stereo audio, channel0.json and channel1 are the transcription text for 2 channels. Whether you need use one or both files is depending on your use case.

Yes I understand stereo audio. Actually I was confirming about Offset and Duration, whether I have to use both of them or any one would serve the purpose for merging the audios?

The offset and duration refer to the position of each individual channel, but both channels in a stereo audio should start with the same "zero" position, so they are synchronized in most cases. For merging transcription texts, you probably need to look into both results in order not to miss any text. If both channel speak at the same time, the offset/duration from different channels might be overlapped.

Thank you very much @zhouwangzw  for the clarifications!


Bootstrap script to rerun ansible playbooks only

Duplicated by https://github.com/Capgemini/Apollo/issues/177 - more detail to options/approaches in #177


Remove errorneous squeeze in tf.contrib.losses.sparse_softmax_cross_entropy_loss

The tf.contrib.losses.sparse_softmax_cross_entropy_loss has an weights parameter which can be used to weight the individual batch elements. The weights parameter can have various shape, which are all taken care of in compute_weighted_loss.
However, the sparse_softmax_cross_entropy_loss methods contains an errorneous squeeze of the weights. If some dimension of weights is not known, the number of dimensions after the squeeze is unknown, which causes the compute_weighted_loss method to throw an exception. However, if the squeeze in sparse_softmax_cross_entropy_loss is not called, compute_weighted_loss can deal even with unknown dimensions of weights.
Note that tf.contrib.losses.softmax_cross_entropy_loss does not contain the squeeze of the weights, even if it uses the weights argument in an equal way.
Should fix #6846.

Can one of the admins verify this patch?

Could we add a test for that perhaps?

@foxik could you add a test to your PR, please?

I implemented the tests, they fail without the fix applied.
I added the tests also for contrib.losses.softmax_cross_entropy -- they are not strictly needed there (there was not the same error in softmax_cross_entropy), but the API offers the same guarantees for the weights in both calls.

@tensorflow-jenkins test this please

Thanks for the fix.


Portable CGE Format

I was thinking we should pick a forwards-compatible format that is flexible enough to store any results of an eant2 evolution, is pretty, is human readable (up to the format user chooses to output as), and is not too verbose.
What do you think of (encoded to JSON for example):
{
  "version": 1,

  "metadata": {
    "fitness": 0.04521971,
    "description": "Optional description. What the network does, input/output scheme.",
  },

  "network": {
    "activation": "relu",
    "genome": [
      { "kind": "input", "id": 0, "weight": 1.3 },
      { "kind": "neuron", "id": 1, "weight": 0.3, ... },
      ...
    ]
  },
  "auxiliary": [ 0.436, 0.221, 1.829 ]
}

allows for expanding features & backwards compatibility (easy to handle breaking changes with version)
allows for optionally providing auxiliary parameters in a portable file (if we add those to eant2)

Pseudocode implementation
This can all be compartmentalized in a separate module & keep the rest of cge mostly unchanged, in pseudocode:
#[derive(Serialize_repr, Deserialize_repr)]
#[serde(tag = "version")]
#[repr(u8)]
enum PortableCGE {
  V1(version_one::VersionOneFormat) = 1,
  V2(version_two::VersionTwoFormat) = 2,
  // ...
}

// version_one::VersionOneFormat
struct VersionOneFormat {
  meta: version_one::Metadata,
  network: Vec<Gene>,
  // ...
}

// version_two::VersionTwoFormat
struct VersionTwoFormat {
  meta: version_two::Metadata,
  network: BTreeMap<UUID, Gene>,
  new_property: String
  // ...
}

#[derive(Serialize, Deserialize)]
struct CGE {
  meta: Metadata,
  network: Vec<Gene>,
  new_property: Option<String>,
  // ...
}

impl From<VersionOneFormat> for CGE { /* ... */ }
impl From<VersionTwoFormat> for CGE { /* ... */ }

Then use like
#[cfg(feature = "json")] let loaded: CGE = serde_json::from_bytes::<PortableCGE>(&input)?.into();
#[cfg(feature = "msgpack")] let loaded: CGE = rmp_serde::from_bytes::<PortableCGE>(&input)?.into();
// ...

This forces all data to be uniform by the time you're actually interacting with it.
I'd like to find a better way to dynamically pick the correct decoder & not have to guard with feature flags (perhaps using serde_any).
Thoughts? Is this design all a big mistake?

I like the idea of having a versioned format using some existing library (most likely using serde). I'm not sure about having built-in support for metadata that's not specifically related to or used by cge though. It might still be useful to store in different cases however, so perhaps the metadata can be reduced to just a description and the auxiliary, fitness, etc. fields replaced by a user-defined set of additional parameters to store:
{
  "version": 1,

  "metadata": {
    "description": "Optional description. What the network does, input/output scheme.",
  },

  "network": {
    "activation": "relu",
    "genome": [
      { "kind": "input", "id": 0, "weight": 1.3 },
      { "kind": "neuron", "id": 1, "weight": 0.3, ... },
      ...
    ]
  },

  "extra": {
    "fitness": 0.04521971,
    "auxiliary": [ 0.436, 0.221, 1.829 ]
  }
}

The extra field would be passed as-is to the user. This keeps the core format free of unused information while also making it convenient to extend if additional data needs to be stored.

Alright, the new format has been added. It's basically identical to what was proposed. There's a usage example in examples/ and several example files in test_data/. I'll probably add optional persistent state saving/loading before the 0.1 release, but other than that I don't expect any significant changes to it for now.


How many A100s used for training?

Thank you for the great job!
I am just a bit curious about the computing resources used for LLaVA-NeXT.

The largest 34B variant finishes training in ~1 day with 32 A100s according to the blog post


Build data pipeline - get web data and load to dataframe

from
worldbank_zip_url = "https://databank.worldbank.org/data/download/Gender_Stats_CSV.zip"
oecd_csv_url = "https://data.oecd.org/earnwage/gender-wage-gap.htm"

Successfully read data from zip file and csv file; saved data to /data/


Speed up initialization times

Currently, Aioli fetches config.json files serially while initializing each WebAssembly module. We could save some time if we preloaded all config.json files in parallel.
The same could be done with the .wasm / .js files

Addressed in v2.3.0


Error with reddit client id.

When running the reddit scrape test, I get an error that the client id is invalid. Does it take a certain amount of time for the client_id to get active or is something wrong? I have not written it wrong nor have I done any further changes in the script.

I have the same problem. What's the solution?

Double check your client id and client secret code from reddit.
Set the system variables

You can set your system environmental variable by writing in the terminal the following commands:
$export REDDIT_CLIENT_ID=YOURCODEFROMREDDITHERE
$export REDDIT_CLIENT_SECRET=YOURCODEFROMREDDITHERE
This will set the variables which you can then confirm by using the command
echo $REDDIT_CLIENT_ID
(this will return the code string that you entered)
echo $REDDIT_CLIENT_SECRET
(this will return the code string that you entered)


fix the usage of func Eventually()

Signed-off-by: Helen-Xie<EMAIL_ADDRESS>

ping @feiskyer

[Fail] [k8s.io] Image Manager [It] public image with digest should be pulled and removed [Conformance]
/go/src/github.com/kubernetes-incubator/cri-tools/pkg/validate/image.go:159

This test always failed in my settings. Could you also fix the test?

ok, I will fix it. @feiskyer

This test always failed in my settings. Could you also fix the test?

This is caused by old docker versions. Not related with test suite itself.

LGTM


Update requirements.txt to avoid version conflicts

Pinning a minimum version of sphinx-rtd-theme >= 2.0.0 mitigate from getting old version of sphinx-rtd-theme.
https://github.com/readthedocs/sphinx_rtd_theme/issues/1571#issuecomment-2263743320

haven't tested it, but makes sense to me. Could you also send a PR to the CodeRefinery upstream repo?

Added a PR upstream https://github.com/coderefinery/sphinx-lesson-template/pull/15

Added upstream


Why is "const true = false" allowed?

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

https://play.golang.org

What operating system and processor architecture are you using (go env)?

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Run a small program:
package main

import "fmt"

const true = false

func main() {
    if (true == false) {
        fmt.Println("True equals to false")
    }
    fmt.Println("Hello World")
}

https://play.golang.org/p/KwePsmQ_q9

What did you expect to see?

Error or warning message that I'm creating constant with already defined name, and potentially breaking whole app.

What did you see instead?

Running without a problem. No warnings or anything to prevent creating new constant with already defined name.

This is working as intended. For questions, see https://golang.org/wiki/Questions


Update the README file

Hey @eltosin , I created a repo, but I could really use help with crafting a better README. Notice that I created the repo at #1


Extend acquireTokenHelper instrumentation

This PR adds instrumentation through logger messages to acquireTokenHelper for msal-core.

Coverage increased (+0.02%) to 76.883% when pulling dd62716a2b471fafd293523889c9b339911c6bfe on ath-instrumentation into 4468dd0fbaacd6358cd203cc0fcf7967b2a80afd on dev.


feat(STONEINTG-711): add finally task to push.yaml

add finally task to .tekton/push.yaml to send message to slack in case tasks fails

Signed-off-by: Hongwei Liu<EMAIL_ADDRESS>Before you complete this pull request ...
Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

Don't merge. This PR need to set a secret for slack.

Test the code change in pull-request PLR for the successful PLR, and can get notification as below.

/retest


Show matching version in sample

The sample should also use ltsc2022 instead of ltsc2019 for the ltsc2022 image

Great catch! :metal:
Unfortunately, we're going to need to update this in the Makefile though:
https://github.com/docker-library/hello-world/blob/dcc88fb4730e7404725a8b6d4c9f08d4944c388e/Makefile#L40
Maybe something like this (untested):
...
-e 's!ubuntu bash!mcr.microsoft.com/windows/servercore:'"$${winVariant##*-}"' powershell!g' \
...

(I'm happy to update your branch directly if you'd rather not continue working on this :sweat_smile:  The contribution is appreciated! :+1:)


Office 365 Plus => Office 365 ProPlus

Please revise product name from Office 365 Plus to Office 365 ProPlus in this sentence. Correct name is Office 365 ProPlus.
Any plan that includes Microsoft 365 Apps for enterprise (previously named Office 365 Plus). For example, Office 365 E3 or Microsoft 365 E5.
This is reference.
Name change for Office 365 ProPlus
https://docs.microsoft.com/en-us/deployoffice/name-change

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

ID: 8ab31873-7ad3-afde-3c72-8a7fb4f2e551
Version Independent ID: 19f7f483-9f53-f577-1cd4-d360c0b234fc
Content: Overview of shared computer activation for Microsoft 365 Apps - Deploy Office
Content Source: DeployOffice/overview-shared-computer-activation.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@takeakitake  Thanks for noticing that and letting us know. It's been fixed. We also checked to make sure that same error didn't appear in other articles in the "deploy Office" content.


Fix minor typos in im-online documentation

Description
I'm quite sure there's a misleading typo in SomeOffline event documentation.
It was stated as:
At the end of the session, at least once validator was found to be offline.
It should be:
At the end of the session, at least one validator was found to be offline.
I also fixed another minor typo iff -> if
Rationale
That description was a bit confusing to me because I wanted to understand if there's a way to find out if a validator was online when a specific block was created.
So I checked when this event is published and I understood that a this event is being sent if a validator did not create a block and did not send a heartbeat (which is sent once per session, roughly in the middle of session).
This event then states that Some validators were Offline during a session, not that at least once a validator was found to be offline. Which is confusing because I thought that validators could be offline multiple times per session, and this event informed that validator was offline at least once.

[clabot:check]

Thanks @pawelnguyen glad to see you found the way here :)


how can i deinstall it from my pc? :(

Depends on how you installed it

Depends on how you installed it

i installed it from the localsend website direct install with zip file. do i just deinstall the whole folder or are there like files lingering around? i dont really know this type of stuff im sorry :(

The zip file contains the portable version so you can just delete the folder and you are done.


Interview scheduling UI

More ready for review now. Just need to integrate with backend API and we should be ok. If you want to see how it looks, start up the local portal and go to localhost:3000/interview-scheduling.
I basically made something that spawns N number of schedule selector if it is given N number of interview start dates (indicating the start date of each interview week). My rationale for this is that since we most likely won't have interviews on weekends on interview weeks, just weekdays, we should have multiple schedule selectors corresponding to the interview weeks, so the users cannot pick weekends. That and this makes it so that users can see the schedules separated by interview week.
Not sure if this is what we want but this is what I came up with
Some screenshots:
Selecting some times

Selecting more times

After clicking on confirm

@thaigillespie nice work - just some comments
happy to merge this in considering our timeline, but need to cleanup soon


The sha256 checksums of the v2.14.0 release are not correctly documented

The sha256 checksums that are listed on the Github "Downloads" page are wrong.
Obviously, they have been copy-pasted from the 2.13.1 release... ;-)

Helm/Tiller release: v2.14.0
Platforms: all
Link: https://github.com/helm/helm/releases/tag/v2.14.0

cc @bacongobbler @hickeyma

@headcr4sh Thanks for catching this. It is now fixed.
I cross referenced the SHAs printed in CI (see https://circleci.com/gh/helm/helm/8280) with those we store to make sure they were the same.

@mattfarina thanks for clearing this up.


Create a DISCLAIMER file for the repositories being released

incubator-kie-drools needs the DISCLAIMER file and a NOTICE file in the repo
incubator-kie-optaplanner needs the DISCLAIMER file and the NOTICE file
incubator-kie-kogito-runtimes needs the DISCLAIMER file
incubator-kie-kogito-apps needs the DISCLAIMER file
incubator-kie-kogito-images needs the DISCLAIMER file and the NOTICE file
incubator-kie-tools needs the DISCLAIMER file

DISCLAIMER file:
Apache KIE (incubating) is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the name of Apache Incubator. Incubation is
required of all newly accepted projects until a further review indicates that
the infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of the
code, it does indicate that the project has yet to be fully endorsed by the ASF.

Some of the incubating project’s releases may not be fully compliant with ASF
policy. For example, releases may have incomplete or un-reviewed licensing
conditions. What follows is a list of known issues the project is currently
aware of (note that this list, by definition, is likely to be incomplete):

* Hibernate, an LGPL project, is being used. Hibernate is in the process of relicensing to ASL v2
* Some files, particularly test files, and those not supporting comments, may be missing the ASF Licensing Header
*

If you are planning to incorporate this work into your product/project, please
be aware that you will need to conduct a thorough licensing review to determine
the overall implications of including this work. For the current status of this
project through the Apache Incubator visit:
https://incubator.apache.org/projects/kie.html

@LightGuard Disclaimer added in kie-tools in this PR


build backend: optional dependencies don't make it to PKG-INFO

I'm on uv 0.5.11 (c4d0caaee 2024-12-19).
The issue here is that optional dependencies aren't being written properly to PKG-INFO, therefore making it impossible to pip install the package with options. This was originally identified in https://github.com/biopragmatics/curies/issues/147. Here's a minimal reproduction:
$ uv --preview init xyz --build-backend uv
Initialized project `xyz` at `/Users/cthoyt/xyz`

$ cd xyz

$ uv --preview add defusedxml --optional xml
Using CPython 3.11.10
Creating virtual environment at: .venv
Resolved 2 packages in 59ms
   Built xyz @ file:///Users/cthoyt/xyz
Prepared 1 package in 5ms
Installed 2 packages in 3ms
 + defusedxml==0.7.1
 + xyz==0.1.0 (from file:///Users/cthoyt/xyz)

$ echo "import defusedxml" > src/xyz/__init__.py
$ echo "def main(): print('hello from modified xyz')" >> src/xyz/__init__.py

$ uv run xyz
hello from modified xyz

If you start from scratch, you need to do uv run --extra xml xyz, since the option isn't installed yet.
Now comes the problematic part, after building:
$ uv --preview build
Building source distribution (uv build backend)...
Building wheel from source distribution (uv build backend)...
Successfully built dist/xyz-0.1.0.tar.gz
Successfully built dist/xyz-0.1.0-py3-none-any.whl

$ tar -xOzf dist/xyz-0.1.0.tar.gz xyz-0.1.0/PKG-INFO
Metadata-Version: 2.3
Name: xyz
Version: 0.1.0
Summary: Add your description here
Author: Charles Tapley Hoyt
Author-email: Charles Tapley Hoyt<EMAIL_ADDRESS>Requires-Python: >=3.11
Provides-Extra: xml
Description-Content-Type: text/markdown

Here's the bug: This PKG-INFO file should also include the line Requires-Dist: defusedxml>=0.7.1; extra == 'xml'.
I believe this also implies that the test scenario at https://github.com/astral-sh/uv/blob/ad92aaf186f59e7f9b3145b62308c8f8a7230bd5/crates/uv-build-backend/src/metadata.rs#L1029-L1036 is incomplete, since it's also missing the appropriate Requires-Dist: lines for mysql and postgres
What this means for pip users
This affects users by the following scenario using pip to install the package. The minimal reproduction below should follow the code before, in which it creates a virtual environment, activates it (I'm using fish, but so activation will vary based on your console), installing pip in the virtual environment, then using pip to install the package locally
This can be reproduced with a pip installation scenario by creating a new virtual environment, installing pip in it, then using pip to install. Note that the same thing happens whether you're using -e for an editable installation or not.
$ uv venv
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate.fish

$ source .venv/bin/activate.fish

$ uv pip install pip
Resolved 1 package in 196ms
Prepared 1 package in 182ms
Installed 1 package in 6ms
 + pip==24.3.1

$ UV_PREVIEW=1 python -m pip install .[xml]
Processing /Users/cthoyt/Desktop/xyz
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: xyz
  Building wheel for xyz (pyproject.toml) ... done
  Created wheel for xyz: filename=xyz-0.1.0-py3-none-any.whl size=1503 sha256=23ddd26cc3e4c20321aec8053bf8ce5e80d9340977d96555e34ce06b7450c6f5
  Stored in directory: /private/var/folders/6k/r2gmmc213vl6h7bv20x624xw0000gn/T/pip-ephem-wheel-cache-hcnf61u2/wheels/92/98/ae/8e6e182b3e32485aed6bab20d53b27efc72ed7f772a8da227b
Successfully built xyz
Installing collected packages: xyz
Successfully installed xyz-0.1.0

$ pip list
Package Version Editable project location
------- ------- -------------------------
pip     24.3.1
xyz     0.1.0   /Users/cthoyt/Desktop/xyz

This listing should include defusedxml, but doesn't
How it should look, using hatch backend
Here's an alternate reproduction that gets the right thing, using hatchling as the backend:
$ uv init xyz --build-backend hatch
Initialized project `xyz` at `/Users/cthoyt/Desktop/xyz`

$ cd xyz

$ uv add defusedxml --optional xml
Using CPython 3.11.10
Creating virtual environment at: .venv
Resolved 2 packages in 1ms
   Built xyz @ file:///Users/cthoyt/Desktop/xyz
Prepared 1 package in 218ms
Installed 2 packages in 1ms
 + defusedxml==0.7.1
 + xyz==0.1.0 (from file:///Users/cthoyt/Desktop/xyz)

$ uv build
Building source distribution...
Building wheel from source distribution...
Successfully built dist/xyz-0.1.0.tar.gz
Successfully built dist/xyz-0.1.0-py3-none-any.whl

$ tar -xOzf dist/xyz-0.1.0.tar.gz xyz-0.1.0/PKG-INFO
Metadata-Version: 2.4
Name: xyz
Version: 0.1.0
Summary: Add your description here
Author-email: Charles Tapley Hoyt<EMAIL_ADDRESS>Requires-Python: >=3.11
Provides-Extra: xml
Requires-Dist: defusedxml>=0.7.1; extra == 'xml'

(I'll fix this, I've already implemented it before.)


change test framework to jest

Coverage decreased (-2.3%) to 96.401% when pulling 781b99856394fb4c2f51a961b2f6c862612e9dc7 on v1 into c3f5f0ff2d963f81c57d142cd7d1464ad5122128 on master.

Coverage decreased (-2.3%) to 96.401% when pulling 781b99856394fb4c2f51a961b2f6c862612e9dc7 on v1 into c3f5f0ff2d963f81c57d142cd7d1464ad5122128 on master.


Staff page revamp

The staff pages right now only show articles an editor has written. This can be changed to also show the photos an editor has taken. Perhaps, the different sections on the staff pages can be collapsable. Talk to Pragati or Brookelyn for more ideas on staff pages changes.

customizable staff pages
blocks

[ ] photo gallery

[ ] query db to get all photos by user
-- only photos of live articles
[ ] css for gallery

[ ] good layout
-- dont resize everything to squares
[ ] arrow keys

[ ] animation

[ ] small animation?
[ ] blur background
[ ] ability to zoom naively?

[ ] pinned article
-- has to be article by user?

[ ] ability to write comment abt it?

other

[ ] better layout
-- square photos?


API Specs

Hello there!
Would it be possible to include extensive API documentation?
Unfortunately wings is currently un-testable without it, so it'd be great to have the latest OpenApi at least.
The most beneficial approach would be to auto-generating these.

Wings is an internal API that isn't usually accessed directly, so while it is possible it's not a priority.  It would be nice to have.

Hey you should find it in /docs/api/remote of your panel like https://panel.example.com/docs/api/remote


Allow tensor as iou_threshold parameter to tf.image.non_max_suppression.

I have a use case where dynamically changing the iou_threshold parameter on a frozen graph is required. I'm not 100% positive this doesn't violate the backwards compatibility rules, and it does make the iou_threshold a required parameter. Feedback from the maintainers would be appreciated.

Can one of the admins verify this patch?

Since this changes the functionality of the op, I believe you have to do this by

adding a new kernel named NonMaxSuppressionOpV2
migrate all producers (e.g. Python wrappers) to use that kernel instead.

See this for more details:
https://www.tensorflow.org/programmers_guide/data_versions

(Though you have to wait 3 weeks after checking in the new Op/OpKernel before changing the python code).

Ok, I moved my changes into a new NonMaxSuppressionV2Op as suggested.

@tensorflow-jenkins test this please


Header-Case?

For going from whatever-case to Title-Case-With-Hyphens for use in things like HTTP headers:
contentType -> Content-Type
ccRequestType -> CC-Request-Type

Released with 3.0.0, though I believe ccRequestType will become Cc-Request-Type.

:+1:


Unable to process custom metrics from Python functions

How to reproduce

Create a Python Lambda function
Add a print statement : print("MONITORING|1|Count|ColdStart|ServerlessAirline|service=test,function_name=async-python-test")
Test the function

Background
Regex itself is working, so I enabled DEBUG=* env var to gather some understanding and got the following clue:
{
    "errorMessage": "Missing required key 'Value' in params.MetricData[0].Dimensions[2]",
    "errorType": "MissingRequiredParameter",
    "stackTrace": [
        "ParamValidator.fail (/var/task/node_modules/aws-sdk/lib/param_validator.js:50:37)",
        "ParamValidator.validateStructure (/var/task/node_modules/aws-sdk/lib/param_validator.js:61:14)",
        "ParamValidator.validateMember (/var/task/node_modules/aws-sdk/lib/param_validator.js:88:21)",
        "ParamValidator.validateList (/var/task/node_modules/aws-sdk/lib/param_validator.js:103:14)",
        "ParamValidator.validateMember (/var/task/node_modules/aws-sdk/lib/param_validator.js:90:21)",
        "ParamValidator.validateStructure (/var/task/node_modules/aws-sdk/lib/param_validator.js:75:14)",
        "ParamValidator.validateMember (/var/task/node_modules/aws-sdk/lib/param_validator.js:88:21)",
        "ParamValidator.validateList (/var/task/node_modules/aws-sdk/lib/param_validator.js:103:14)",
        "ParamValidator.validateMember (/var/task/node_modules/aws-sdk/lib/param_validator.js:90:21)",
        "ParamValidator.validateStructure (/var/task/node_modules/aws-sdk/lib/param_validator.js:75:14)"
    ]
}

More info after making a new deployment..
2019-09-03T20:10:59.451Z async-lambda-metrics Parsing lambda log event { id: '34957329142900575350335802714511782854710479521511440384', timestamp:<PHONE_NUMBER>635, message: 'START RequestId: 65296afb-b652-46c4-9654-25cb96cb61e9 Version: $LATEST\n' }
2019-09-03T20:10:59.451Z 348d4e3b-434a-4bd5-b908-b6c329337fc2 { id: '34957329142900575350335802714511782854710479521511440384',
timestamp:<PHONE_NUMBER>635,
message: 'START RequestId: 65296afb-b652-46c4-9654-25cb96cb61e9 Version: $LATEST\n' }
2019-09-03T20:10:59.455Z 348d4e3b-434a-4bd5-b908-b6c329337fc2
{
    "errorMessage": "Cannot destructure property `event` of 'undefined' or 'null'.",
    "errorType": "TypeError",
    "stackTrace": [
        "parseLambdaLogData (/var/task/functions/lib.js:57:12)",
        "Array.map (<anonymous>)",
        "_.flatMap.cwLogEvent (/var/task/functions/lib.js:136:5)",
        "arrayMap (/var/task/node_modules/lodash/lodash.js:639:23)",
        "map (/var/task/node_modules/lodash/lodash.js:9554:14)",
        "Function.flatMap (/var/task/node_modules/lodash/lodash.js:9257:26)",
        "processAll (/var/task/functions/lib.js:129:20)",
        "handler (/var/task/functions/index.js:11:8)"
    ]
}

Looking at the code now this is where it fails:
	const {
		event: rawEvent,
		timestamp: timestamp
	} = event.extractedFields // extractedFields is undefined

so looks like the default Lambda filter pattern doesn't match Python log lines... looks as though print inserts a newline in there, maybe that's what's breaking the subscription

@heitorlessa v1.0.1 is published in us-east-1

found a different issue with timestamps from Python log messages, fixed in v1.0.2

tried it myself, now I'm seeing the metric from Python function

That's awesome! Have you had a chance to test with Java and other runtimes in case they are also different?
I guess they follow the same format as Python

Not yet. I can dig up some example projects I had before and try them out later.
Sent from my iPhone

On 5 Sep 2019, at 09:41, Heitor Lessa<EMAIL_ADDRESS>wrote:
That's awesome! Have you had a chance to test with Java and other runtimes in case they are also different?
I guess they follow the same format as Python
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

I've just tried that and it's now failing with this new error message:
{
    "errorMessage": "timestamp must follow ISO8601",
    "errorType": "MalformedInput",
    "stackTrace": [
        "Request.extractError (/var/task/node_modules/aws-sdk/lib/protocol/query.js:50:29)",
        "Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:106:20)",
        "Request.emit (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:78:10)",
        "Request.emit (/var/task/node_modules/aws-sdk/lib/request.js:683:14)",
        "Request.transition (/var/task/node_modules/aws-sdk/lib/request.js:22:10)",
        "AcceptorStateMachine.runTo (/var/task/node_modules/aws-sdk/lib/state_machine.js:14:12)",
        "/var/task/node_modules/aws-sdk/lib/state_machine.js:26:10",
        "Request.<anonymous> (/var/task/node_modules/aws-sdk/lib/request.js:38:9)",
        "Request.<anonymous> (/var/task/node_modules/aws-sdk/lib/request.js:685:12)",
        "Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:116:18)"
    ]
}

Couldn't do much digging beyond that as of now but may ring a bell

try 1.0.2, that was the timestamp issue I found after publishing 1.0.1...
On Thu, Sep 5, 2019 at 6:24 PM Heitor Lessa<EMAIL_ADDRESS>wrote:

I've just tried that and it's now failing with this new error message:
{
"errorMessage": "timestamp must follow ISO8601",
"errorType": "MalformedInput",
"stackTrace": [
"Request.extractError (/var/task/node_modules/aws-sdk/lib/protocol/query.js:50:29)",
"Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:106:20)",
"Request.emit (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:78:10)",
"Request.emit (/var/task/node_modules/aws-sdk/lib/request.js:683:14)",
"Request.transition (/var/task/node_modules/aws-sdk/lib/request.js:22:10)",
"AcceptorStateMachine.runTo (/var/task/node_modules/aws-sdk/lib/state_machine.js:14:12)",
"/var/task/node_modules/aws-sdk/lib/state_machine.js:26:10",
"Request. (/var/task/node_modules/aws-sdk/lib/request.js:38:9)",
"Request. (/var/task/node_modules/aws-sdk/lib/request.js:685:12)",
"Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:116:18)"
]
}
Couldn't do much digging beyond that as of now but may ring a bell
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lumigo/SAR-async-lambda-metrics/issues/4?email_source=notifications&email_token=AAEFRGL6ZYZUIQTJEAJZPBTQIEXDVA5CNFSM4ITI56UKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD57XV6A#issuecomment-528448248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEFRGK4H7I35PYZEZU2AULQIEXDVANCNFSM4ITI56UA
.

Lol. Will try that this evening :)
On Thu, 5 Sep 2019 at 18:17, Yan Cui<EMAIL_ADDRESS>wrote:

try 1.0.2, that was the timestamp issue I found after publishing 1.0.1...
On Thu, Sep 5, 2019 at 6:24 PM Heitor Lessa<EMAIL_ADDRESS>wrote:

I've just tried that and it's now failing with this new error message:
{
"errorMessage": "timestamp must follow ISO8601",
"errorType": "MalformedInput",
"stackTrace": [
"Request.extractError
(/var/task/node_modules/aws-sdk/lib/protocol/query.js:50:29)",
"Request.callListeners
(/var/task/node_modules/aws-sdk/lib/sequential_executor.js:106:20)",
"Request.emit
(/var/task/node_modules/aws-sdk/lib/sequential_executor.js:78:10)",
"Request.emit (/var/task/node_modules/aws-sdk/lib/request.js:683:14)",
"Request.transition
(/var/task/node_modules/aws-sdk/lib/request.js:22:10)",
"AcceptorStateMachine.runTo
(/var/task/node_modules/aws-sdk/lib/state_machine.js:14:12)",
"/var/task/node_modules/aws-sdk/lib/state_machine.js:26:10",
"Request.
(/var/task/node_modules/aws-sdk/lib/request.js:38:9)",
"Request.
(/var/task/node_modules/aws-sdk/lib/request.js:685:12)",
"Request.callListeners
(/var/task/node_modules/aws-sdk/lib/sequential_executor.js:116:18)"
]
}
Couldn't do much digging beyond that as of now but may ring a bell
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/lumigo/SAR-async-lambda-metrics/issues/4?email_source=notifications&email_token=AAEFRGL6ZYZUIQTJEAJZPBTQIEXDVA5CNFSM4ITI56UKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD57XV6A#issuecomment-528448248
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAEFRGK4H7I35PYZEZU2AULQIEXDVANCNFSM4ITI56UA
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lumigo/SAR-async-lambda-metrics/issues/4?email_source=notifications&email_token=AAZPQBDLEXSUCMPSTZGRAULQIE5LLA5CNFSM4ITI56UKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6AAF5A#issuecomment-528483060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZPQBCZAA524K2Z2QEWTWTQIE5LLANCNFSM4ITI56UA
.

Tested in London region and the real issue came down to the default Filter Pattern - I've updated to only capture REPORTING and MONITORING.
Here's how it looks like now and I can see the metrics in.
  # Subscribe new and existing CloudWatch Log groups to ship logs to Kinesis
  SubscribeLogsToProcessingStream:
    Type: AWS::Serverless::Application
    Properties:
      Location:
        ApplicationId: arn:aws:serverlessrepo:us-east-1:374852340823:applications/auto-subscribe-log-group-to-arn
        SemanticVersion: 1.4.0
      Parameters:
        # The ARN of the Lambda function or Kinesis stream to subscribe a newly created CloudWatch log group to
        DestinationArn: !Sub ${LogProcessingStream.Arn}
        ## Disables processing of own logs
        ExcludePrefix: 'ProcessCustomMetricsAsync' # Uncomment to override default value
        # Only subscribe to functions created for this project
        ## Otherwise we'd override all CloudWatch Logs by subscribing to our Kinesis
        Prefix: '/aws/lambda/awsserverlessairline' # Uncomment to override default value
        # Only captures REPORT and Custom Metrics log events; reduces cost and unnecessary noise
        FilterPattern: '?REPORT ?MONITORING'

However, metrics are being created with extra space - Creating another issue to separate the two.


Azure ACR Managed Identity Login - No information on expiration

I've been following the guide for setting up an automated pipeline with azure ACR for my use case like specified here, using managed identities.
However, this guide provides no information on what to do once the token expires, nor how to set up the expiration length.
This is giving me problems because the token always expires and the pipeline halts.
How can I refresh the token or have the token not expire? Do I have to run az acr login -n registryName periodically?

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

ID: 9d1bf6a2-95e7-4b50-e03e-9bf212dc5214
Version Independent ID: 79ee1b51-6a22-0a57-2a28-7eb5a65c9778
Content: Authenticate with managed identity - Azure Container Registry
Content Source: articles/container-registry/container-registry-authentication-managed-identity.md
Service: container-registry
GitHub Login: @dlepow
Microsoft Alias: tejaswikolli

As mentioned in the document,
For registry access, the token used by az acr login is valid for 3 hours, so we recommend that you always log in to the registry before running a docker command. If your token expires, you can refresh it by using the az acr login command again to reauthenticate.

As mentioned in the document, For registry access, the token used by az acr login is valid for 3 hours, so we recommend that you always log in to the registry before running a docker command. If your token expires, you can refresh it by using the az acr login command again to reauthenticate.

The table I linked to informs that Managed Identities are meant to be "Unattended push from Azure CI/CD pipeline". This leads me to believe no one should be doing any logins after the setup because it's for automation.
The document I'm providing feedback to also has no mention of expiration. I also can not find the expiration citation in azr acr login page.
Currently I've set up a cron job that logs in periodically, but I don't see anything in any of the guides recommending this. Did I do something wrong?

@lucasgcbkhomp Thanks for sharing the details. I am looking into it and will share an update shortly.

Thank you for your dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue and creating an internal work item to incorporate your suggestion as time allows. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Regimens

We will need to appropriately map terms to regimens and combination therapies.

NCCN is a common source of regimens, but they don't appear to be codified. https://www.nccn.org/professionals/OrderTemplates/Default.aspx
NCIt has regimens we can use, e.g. https://ncithesaurus.nci.nih.gov/ncitbrowser/pages/concept_details.jsf?dictionary=NCI_Thesaurus&version=20.09d&code=C9509&ns=ncit&type=relationship&key=n1961482768&b=1&n=0&vse=null

Potentially incorporate: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7000232/


Fix: Failing build on Dev

This PR fixes the failing build on dev due to inconsistent package managers.

Closing this branch, due to issues on Dev.
Dev has been reset to not consume the gRPC changes.


bug: KeyError: 'current_UA_code'

wayback_google_analytics/output.py", line 101, in get_urls_df
    "UA_Code": info["current_UA_code"],
KeyError: 'current_UA_code'

This is due, I believe, to this code section where the keys are assigned, but only if the html variable is not None.
One simple solution is to do dict.get instead of dict[] for the optionally present parameters, eg: info.get("current_UA_code", ""), but I wonder if there's some missing logic between the 2 different parts and if there's a better way to address it.

Resolved in PR #18.


Superagent 1.0.0 no longer works with Sinon FakeXMLHttpRequest

The following Jasmine spec passes against superagent 0.21.0 (on PhantomJS, Firefox and Chromium) but fails against superagent 1.0.0 (on the same three browsers):
'use strict';

var request = require('superagent');

describe("Superagent and Sinon's FakeXMLHttpRequest", function () {
    var xhr,
        requests;

    beforeEach(function () {
        xhr = sinon.useFakeXMLHttpRequest();
        requests = [];
        xhr.onCreate = function (x) {
            requests.push(x);
        };
    });

    afterEach(function () {
        xhr.restore();
    });

    it('should work together', function () {
        // make a request
        var error,
            response;

        request.get('/some/mocked/endpoint')
            .type('application/json')
            .accept('application/json')
            .end(function (e, r) {
                error = e;
                response = r;
            });

        // check the (fake) request was made
        expect(requests.length).toBe(1);
        expect(requests[0].method).toBe('GET');

        // respond
        requests[0].respond(200, {
            'Content-Type': 'application/json'
        }, JSON.stringify({
            foo: 'bar'
        }));

        // check error
        expect(error).toBeNull();

        // check response
        expect(response.xhr.responseText).toBe(JSON.stringify({
            foo: 'bar'
        }));
        expect(response.body).toBeDefined();
        expect(response.body).toEqual({
            foo: 'bar'
        });
    });
});

The failure (in PhantomJS) is as follows:
PhantomJS 1.9.8 (Linux) Superagent and Sinon's FakeXMLHttpRequest should work together FAILED
	Expected null to equal Object({ foo: 'bar' }).
	    at /tmp/d9b25d15f0e0ce7cc6db3ecfe8df9250.browserify:13050:0 <- /home/mike/Projects/globalmba/django/site/js/tests/SuperagentSinonFakeXMLHttpRequestSpec.js:54:12
PhantomJS 1.9.8 (Linux): Executed 6 of 6 (1 FAILED) (0.05 secs / 0.015 secs)

In other words, it appears the response.body is null.

please see
https://github.com/visionmedia/superagent/wiki/Migrating-0.x-to-1.x

Thanks, I am aware arity for errors has been removed in 1.0.0.
I'm pretty sure that's not the problem though.
If you look at the Jasmine spec, you'll see the callback already has both (error, response) parameters, and that the expectation that the first parameter (the error) is null succeeds on both 0.21.0 and 1.0.0.
The regression is caused by something in this block of code in the Response constructor (line 309+ in 1.0.0):
@@ -42678,9 +42678,11 @@ function Response(req, options) {
   options = options || {};
   this.req = req;
   this.xhr = this.req.xhr;
-  this.text = this.req.method !='HEAD'
-     ? this.xhr.responseText
+  // responseText is accessible only if responseType is '' or 'text'
+  this.text = (this.req.method !='HEAD' && (this.xhr.responseType === '' || this.xhr.responseType === 'text'))
+     ? this.xhr.responseText
      : null;
+  this.statusText = this.req.xhr.statusText;
   this.setStatusProperties(this.xhr.status);
   this.header = this.headers = parseHeader(this.xhr.getAllResponseHeaders());
   // getAllResponseHeaders sometimes falsely returns "" for CORS requests, but
@@ -42689,7 +42691,7 @@ function Response(req, options) {
   this.header['content-type'] = this.xhr.getResponseHeader('content-type');
   this.setHeaderProperties(this.header);
   this.body = this.req.method != 'HEAD'
-    ? this.parseBody(this.text)
+    ? this.parseBody(this.text ? this.text : this.xhr.response)
     : null;
 }

In 1.0.0 the assignment to this.body can be to this.xhr.response whereas in 0.21.0 it could not.
If I change:
  this.body = this.req.method != 'HEAD'
    ? this.parseBody(this.text ? this.text : this.xhr.response)
    : null;

to:
  this.body = this.req.method != 'HEAD'
    ? this.parseBody(this.text ? this.text : this.xhr.responseText)
    : null;

Note: this.xhr.responseText not this.xhr.response then my tests continue to pass on 1.0.0.

This Jasmine spec now passes in 1.1.0 so closing.
Thank you!


User Snippets function does not work well.

VSCode Version: 1.23.0
OS Version: Ubuntu 16.04 LTS

Steps to Reproduce:

Add PHP snippets, prefix it with "met" in "User Snippets"

"new method": {
	"prefix": "met",
	"body": [
		"${1:public} function ${2}(${3})",
		"{",
		"\treturn ${4}",
		"}"
	],
	"description": "Creat new method"
},

Create class with functions

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;

class User extends Model
{
    /**
     * Get the profile record associated with the user.
     */
    public function profile()
    {
        return $this->belongsTo(User::class);
    }

   # Use snippet "met" here
}

Type "met", it sometimes does not show up the snippet in popup menu.
https://pasteboard.co/HkjfxH6.gif

Does this issue occur when all extensions are disabled?: No
Extensions:
ansible v0.2.8
ansible-autocomplete v0.0.2
code-settings-sync v2.9.2
dart-code v2.12.1
EditorConfig v0.12.1
githistory v0.4.0
Go v0.6.79
java v0.24.0
jinja v0.0.8
laravel-blade v1.18.0
laravel5-snippets v1.4.0
npm-intellisense v1.3.0
php-cs-fixer v0.1.70
php-debug v1.12.3
php-docblocker v1.6.0
phpcs v1.0.5
prettier-vscode v1.3.1
python v2018.4.0
rest-client v0.18.4
sass-indented v1.4.9
semantic-ui-snippets v0.0.7
theme-material-theme v1.0.1
vetur v0.11.7
vscode-docker v0.0.26
vscode-eslint v1.4.8
vscode-icons v7.23.0
vscode-intelephense-client v0.8.8
vscode-java-debug v0.9.0
vscode-java-pack v0.3.0
vscode-java-test v0.6.1
vscode-markdownlint v0.15.0
vscode-maven v0.7.0
vscode-npm-script v0.3.4
vscode-raml v3.0.1
vscode-table-formatter v1.2.1

Please retry without extensions enabled. Select 'Extensions View > ... > Disable all Installed Extensions' and try again. Thanks.


Unable to change log levels in Apps Manager

Describe the bug
Unable to change the log levels dynamically from Apps Manager.
Package used https://www.nuget.org/packages/PivotalServices.AspNet.Replatform.Cf.Actuators/
Expected behavior
Should be able to change the log levels dynamically when using the package https://www.nuget.org/packages/PivotalServices.AspNet.Replatform.Cf.Actuators/

Fixed from version 2.1.0 by consuming Steeltoe version 2.4.2. So closing the issue


Identifiers validation failed for dataset Actualización de la base de datos de hongos macroscópicos de Jalisco

Identifier validation failed for the dataset Actualización de la base de datos de hongos macroscópicos de Jalisco:

Crawler attempt: 322
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 14252
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 14252 total records; 14232 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740252/step

New IDs sample:

urn:catalog:IBUNAM:MEXU:12837:934c58ef32b15fc93455056c38b2786a
urn:catalog:IBUNAM:MEXU:19055:5f2dd5ee7f6d444769622ade640cf088
urn:catalog:IBUNAM:MEXU:NO DISPONIBLE:ae6c3a3957d26549af2331f551bf968b
urn:catalog:IBUNAM:MEXU:18555:275c892a31130d84046b0e389a05c39c
urn:catalog:IBUNAM:MEXU:12852:542aa55495f4074e0bbed1220525b498
urn:catalog:IBUNAM:MEXU:19076:06a896923c9840069e5e8b5fe2b187ae
urn:catalog:IBUNAM:MEXU:11940:9501bba6735ccaf0857df20e2415d539
urn:catalog:IBUNAM:MEXU:12842:cc403cf177a16c53876bc3bf97e92077
urn:catalog:IBUNAM:MEXU:11909:aa4f47c5faec4ca5b1b28603aa105696
urn:catalog:IBUNAM:MEXU:22555:debc5435b4990cc4fd22d6b991a64fb3

Old IDs sample:

014a58f93fba9b27f9b57c8fe98a2c2e
2f3d06dacb0ddda8448f054154976295
46535f37b9be834fca62a1b9a1d4de84
36a85c5001fd7f1c0de515c59fdec1df
3f27a59881da1ee4981f8417cb1da86b
df17f71cacbb65b25ba82f9d5e6550db
07f187e08f30574ba10f4a32b411d647
35dc9de46b92c43eedb410e3d29e61ec
94a84390d2652de8764379601c12c90e
d7406be7f2162f6a8600afccadd6222a

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la base de datos de hongos macroscópicos de Jalisco : https://doi.org/10.15468/shg3hm.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Actualización de la base de datos de hongos macroscópicos de Jalisco:

Crawler attempt: 323
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 14252
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 14252 total records; 14232 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741151/step

New IDs sample:

urn:catalog:IBUNAM:MEXU:12837:934c58ef32b15fc93455056c38b2786a
urn:catalog:IBUNAM:MEXU:19055:5f2dd5ee7f6d444769622ade640cf088
urn:catalog:IBUNAM:MEXU:NO DISPONIBLE:ae6c3a3957d26549af2331f551bf968b
urn:catalog:IBUNAM:MEXU:18555:275c892a31130d84046b0e389a05c39c
urn:catalog:IBUNAM:MEXU:12852:542aa55495f4074e0bbed1220525b498
urn:catalog:IBUNAM:MEXU:19076:06a896923c9840069e5e8b5fe2b187ae
urn:catalog:IBUNAM:MEXU:11940:9501bba6735ccaf0857df20e2415d539
urn:catalog:IBUNAM:MEXU:12842:cc403cf177a16c53876bc3bf97e92077
urn:catalog:IBUNAM:MEXU:11909:aa4f47c5faec4ca5b1b28603aa105696
urn:catalog:IBUNAM:MEXU:22555:debc5435b4990cc4fd22d6b991a64fb3

Old IDs sample:

014a58f93fba9b27f9b57c8fe98a2c2e
2f3d06dacb0ddda8448f054154976295
46535f37b9be834fca62a1b9a1d4de84
36a85c5001fd7f1c0de515c59fdec1df
3f27a59881da1ee4981f8417cb1da86b
df17f71cacbb65b25ba82f9d5e6550db
07f187e08f30574ba10f4a32b411d647
35dc9de46b92c43eedb410e3d29e61ec
94a84390d2652de8764379601c12c90e
d7406be7f2162f6a8600afccadd6222a

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la base de datos de hongos macroscópicos de Jalisco : https://doi.org/10.15468/shg3hm.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Actualización de la base de datos de hongos macroscópicos de Jalisco:

Crawler attempt: 325
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 14252
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 14252 total records; 14232 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741779/step

New IDs sample:

urn:catalog:IBUNAM:MEXU:12837:934c58ef32b15fc93455056c38b2786a
urn:catalog:IBUNAM:MEXU:19055:5f2dd5ee7f6d444769622ade640cf088
urn:catalog:IBUNAM:MEXU:NO DISPONIBLE:ae6c3a3957d26549af2331f551bf968b
urn:catalog:IBUNAM:MEXU:18555:275c892a31130d84046b0e389a05c39c
urn:catalog:IBUNAM:MEXU:12852:542aa55495f4074e0bbed1220525b498
urn:catalog:IBUNAM:MEXU:19076:06a896923c9840069e5e8b5fe2b187ae
urn:catalog:IBUNAM:MEXU:11940:9501bba6735ccaf0857df20e2415d539
urn:catalog:IBUNAM:MEXU:12842:cc403cf177a16c53876bc3bf97e92077
urn:catalog:IBUNAM:MEXU:11909:aa4f47c5faec4ca5b1b28603aa105696
urn:catalog:IBUNAM:MEXU:22555:debc5435b4990cc4fd22d6b991a64fb3

Old IDs sample:

014a58f93fba9b27f9b57c8fe98a2c2e
2f3d06dacb0ddda8448f054154976295
46535f37b9be834fca62a1b9a1d4de84
36a85c5001fd7f1c0de515c59fdec1df
3f27a59881da1ee4981f8417cb1da86b
df17f71cacbb65b25ba82f9d5e6550db
07f187e08f30574ba10f4a32b411d647
35dc9de46b92c43eedb410e3d29e61ec
94a84390d2652de8764379601c12c90e
d7406be7f2162f6a8600afccadd6222a

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la base de datos de hongos macroscópicos de Jalisco : https://doi.org/10.15468/shg3hm.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


{webapps} Fix typo in webapp deploy

Related command
az webapp deploy
Description
{webapps} Fix typo in az webapp deploy cmdlet.
Fixes GitHub Issue 25613
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

webapps


Macros are broken (outside of the online REPL)

The code
macro INVERT = (var) ->
    "#{var} = not #{var}"

$INVERT(x)

used to be valid and produce the following Lua code:
local x = 5;
x = not x

However, after having installed Yuescript 0.16.5, this behavior seems to be broken, with it now resulting in the following compilation error:
Failed to compile: test2.yue
5: left hand expression is not assignable
$INVERT(x)
^

However, weirdly, the online REPL seems to be unaffected by this.

Can you show me the full codes in your "test2.yue" ?

Sure:
macro INVERT = (var) ->
	print(var)
    "#{var} = not #{var}"

$INVERT(x)

The print statement prints that var is a nil value (note to self: why did strip that line out? That sounds like it's quite important here).
For good measure, I also tested this in the interactive (offline) REPL:
macro test = (x, y, z) -> "'#{x}, #{y}, #{z}'"

When running that code as $test("foo", "bar", "biz"), I get back the string nil, nil, nil.

In case that helps, here's some info on my specific setup (since this issue doesn't occur in the online REPL, this issue may be related to that):

OS: Arch Linux
Lua version: 5.1
Install method: sudo luarocks install --lua-version=5.1 yuescript

I think the previous version of Yuescript I used was 0.16.1, but I also recently compiled just fine on a different, more recent setup on my laptop, so I'm guessing that this issue was only introduced in 0.16.5 or maybe 0.16.4.

Found there were wrong arguments passing while expanding macro. The problem was there for a long time and lacking test cases to reveal it.


Add a session filter for archives

Forget to mention @MrWilhelm as this implementation is based on #130. Thanks for starting it! 💯 😄 🎉

#126

Thanks @MrWilhelm and @kouno!


Activate GPG verification upon install (rebased)

Picking up where @ndr-qef left off with #8749.
This is still a work-in-progress, so please feel free to throw your feedback at me.

Nice work. Glad this is getting some love again.

Thanks for taking up the patchset, @jawshooah.
Beyond refactoring, it might be best to improve the CLI output —that is, hide the rather verbose one of GPG— in this PR, rather than postponing UX changes to a later date.

A (rather simple) idea would just be to dump the output to dev/null altogether (unless the --verbose flag is used) and have a single line, similar to the shasum check, i.e. "GPG verification of Cask succeded/failed"

We can simply set :print_stdout => false when invoking system gpg with our system_command wrapper.

@ndr-qef I'm not very familiar with GPG, but should we be using gnupg2 instead of gnupg? Is the legacy version still supported?

Also should we just add depends_on :formula => 'gpg' to casks with a gpg stanza?

I don't like adding that dependency to Casks, as gpg verification should be "best effort" - the notification that gpg verification was skipped (and to install gpg to activate it) should be enough

should we be using gnupg2 instead of gnupg? Is the legacy version still supported?

GnuPG 1 is stable and maintained, as well as widely deployed — notably in the Debian package manager, where it is the standard version to this day.
In any case, the gpg command is meant to call the standard system GPG, whichever that may be. (Much like git, ruby, and so on.) As it happens, many OS X users install GPG through GPGTools, which ships version 2.

Gotcha. Just wanted to make sure we weren't dating ourselves. I'll work on this more tonight.

What's the plan for getting this merged? I'm looking forward to checking signatures without local patches on top.

There's still a bit more work to be done before merging. I've been swamped for a while, but I'll try to get this out within the next few days.

Awesome, thank you!

@jawshooah Any update on this?

@jawshooah Ping

Sorry for the huge delay on this. Life has been dropping a hammer on me the last few months. I should have some time this evening to work on this, though.

@caskroom/maintainers Does anyone want to give any feedback here?

Hadn’t noticed there were commits after the last comment. Is this ready @jawshooah?

Should be functional, I've just been meaning to add more tests but haven't gotten around to it.

One more issue that needs to be discussed before we merge is error handling.
For example, as of right now

https://get.videolan.org/vlc/2.2.4/macosx/vlc-2.2.4.dmg

is up, while at the same time

https://get.videolan.org/vlc/2.2.4/macosx/vlc-2.2.4.dmg.asc

returns a HTTP 500 status:

We're very sorry but...
none of our mirrors are able to handle your request, please try again later

When I rebase this PR and then do brew cask install vlc, the following happens:

I think it’s perfectly acceptable for the whole installation to fail when the signature is unavailable. However, this should result in a clear error message indicating what happened, rather than just bailing out with a stack trace.

This needs a rebase.

ping @jawshooah Any chance you could rebase and update the error handling?

@fanquake Hopefully I can get to this later tonight.

Leaving this open since there is still interest, I just haven't gotten around to cleaning it up yet. Will try to migrate to Homebrew/brew later this evening.

Continued in https://github.com/Homebrew/brew/pull/1335.


Update iina to 0.0.4

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

It is a same version with a new build. The previous build has been renamed as 'IINA.v0.0.4-old.zip', which matches the sha256 in the outdated formula.

Closing in favour of https://github.com/caskroom/homebrew-cask/pull/29741.


[community packages] DataLakeIO: Support Beam to write data to Delta Lake, and read data from Delta Lake.

Hi, it's a pleasure to communicate again. Last year we supported Ceph storage in delta (https://github.com/delta-io/website/issues/11) , we ware grateful that you added that to delta.io/integrations. After that, we focused on the connection of Apache Beam and data lake. We noticed beam-deltalake, which only support users to read Delta Lake data from Beam. Because of dependency conflicts, it contains a lot of source code of Daltalake Standalone Reader.
Our beam-datalake support to connect Apache Beam and data lake, such as Delta Lake, Apache Hudi, Apache iceberg. With DataLakeIO, data from Apache Beam's pipelines can be written to data lake. It is also supported to read data from data lake into Apache Beam's pipeline.
We provide test cases for beam and delta connections in beam-delta-example , there are four main steps:

1.The beam-datalake project needs to be compiled and installed first.
2.Then, create a delta table using initDeltaTable(), which contains four fields: id, user_name, user_age, user_remark.
3.Then, use testDeltaWrite() to write the data to Delta Lake. In testDeltaWrite(), the simulated data is created, then the simulated data is converted by Apache Beam (converting the user_name to uppercase), and finally written to Delta Lake.
4.At last, use testDeltaRead() to read the data out of Delta Lake, and then filter according to the user_age, and write the data that meets the criteria to text.

beam-deltalake also mentioned our DataLakeIO in issues1, he said he wouldn't be continuing the project. So, We sincerely hope that our  beam-datalake can be added to delta.io/integrations instead of his , and we will continue to optimize our features.
Thank you very much!

Thanks very much @zhangt-nhlab  - is there a preferred logo you would like to use for this project?  This is awesome!!

Thanks very much @zhangt-nhlab - is there a preferred logo you would like to use for this project? This is awesome!!

Hi, @dennyglee , we haven't designed a logo for this project yet, we think the Apache Beam logo is appropriate for this project on  integrations

thanks @zhangt-nhlab - I'll work on this ASAP!

thanks @zhangt-nhlab - I'll work on this ASAP!

OK! Thank you so much!


Adding HIP/CUDA jobs in CI

For a while, we have made hip+openmp jobs a conflict within the spack. I don't think that restriction holds anymore. This ticket will add a hip+openmp job, but keep the conflict for hip+openmp_target.
Along the same lines, we have disabled cuda+shared jobs because there was a restriction at one point between cuda jobs and building with shared libs. That no longer applies, so we will also add '+shared' to an existing cuda job to test.

@kab163 I am currently working on revamp the CI. The change here is pretty minimal, so I don’t think I need to worry too much about having this merged in before I start.

Oops, so this was merged. I’ll need to adapt #723

Done.


Update Layout Pattern overview page/Layout patterns table list

As an IBM.com Library website creator,

I need to update the Layout patterns table list with the correct information

so that the adopters won't be confused.

Additional information
The current homepage Layout patterns table list is not up to date.

Tasks

[ ] Work with Lara on the pattern naming list.
[ ] Update the list with markdowns.

Acceptance criteria

[ ] Table list is updated on the live website.

Based on the Slack conversation I had with Lara, we will...
1. Update the list and update the status to "Stable", we do not use the word "Available" for ability so we can be aligned with the Carbon set up.

Card section - Stable
Content block- Stable
Content group- Stable
Feature card - Stable
Lead space - Stable

2. We will a Resource section below the Pattern Layout List with a card so we can link it to the Storybook.

Updates listed above are completed and can be viewed here.

Section titles are updated as well based on the conversation with Lara.
Typographic structure/detailing to Typographic structure.
Enhanced reading/editorial/storytelling (wip title) to Reading behaviors.

@larahanlon2 As discussed, let's add the pattern descriptions and individual storybook link to the overview table as the next step.

Hey @JennySanchez here are the descriptions to add to the layout status table.

@larahanlon2 The Layout Pattern list updates completed. Thank you for your help!