Upload to Firebase?

Hi guys!
I would like to use your library, but im in trouble.
Can you help me how should i modify my code to upload firebae?
import React, { useCallback } from 'react'
import 'react-dropzone-uploader/dist/styles.css'
import Dropzone from 'react-dropzone-uploader'
import firebase from '../../../firebase/firebase'

function FileDropzone(props) {
    const getUploadParams = async ({ meta }) => {
        const storageRef = await firebase.storage().ref()
        const uploadedFile = storageRef.child(`exerciseManThumbnailImages/${meta.name}`)
        const downloadUrl = uploadedFile.getDownloadURL()
        console.log(downloadUrl)
        const url = 'https://httpbin.org/post'
        return { url, meta: { fileUrl: `${downloadUrl}` }, uploadedFile }
    }

    const handleChangeStatus = ({ meta }, status) => {
        console.log(status, meta)
    }

    const handleSubmit = async (files, allFiles) => {

        console.log(files.map(f => f.meta))
        allFiles.forEach(f => f.remove())
    }

    return (
        <Dropzone
            getUploadParams={getUploadParams}
            onChangeStatus={handleChangeStatus}
            onSubmit={handleSubmit}
            accept="image/*"
            inputContent={(files, extra) => (extra.reject ? 'Image files only' : 'Drag Man Thumbnail')}
            styles={{
                dropzoneReject: { borderColor: 'red', backgroundColor: '#DAA' },
                inputLabel: (files, extra) => (extra.reject ? { color: 'red' } : {}),
            }}
        />
    )

}

export default FileDropzone

hello. any news here?

Nothing. :(

I want to create a dropzone that uploads the selected files automatically to the firebase storage /currentUser/orderID/filesToProcess/ :D
What do you think we need here?
How about creating a REST endpoint for the Firebase Storage?
https://academind.com/learn/firebase/cloud-functions/creating-a-rest-endpoint-with-cloud-functions/

Do you use redux maybe?

How would Redux help to adapt RDU to upload to Firebase?

Did you try changing the
const url = 'https://httpbin.org/post'
part to your firebase storage bucket?

you can use react-redux-firebase library with react-dropzone, if u use redux. i can give my source code, but you can modifiy without redux.

you can use react-redux-firebase library with react-dropzone, if u use redux. i can give my source code, but you can modifiy without redux.

Ah! Now I get it. No I don't use Redux. I avoid Redux like coronavirus :D

u should overwrite the onFilesDrop method, i think with this code snippet and firebase docs u can solve your problem.
// core imports
import React from 'react';
import { useDropzone } from 'react-dropzone';
import { map } from 'lodash';
import { Button } from '@material-ui/core';

function DropzoneInput({ input, parentId, filesPath, firebase, uploadedFiles, setUrls, placeholder, maxFiles }) {
    const { getRootProps, getInputProps, isDragActive } = useDropzone({ onDropAccepted: onFilesDrop, maxFiles: maxFiles });

    function onFilesDrop(files) {
        return firebase
            .uploadFiles(filesPath, files, filesPath)
            .then((files) => {
                console.log('files', files);
                files.map((file, index) => {
                    setUrls((prevState) => {
                        return [...prevState, { fileData: file.File, downloadURL: file.downloadURL, key: file.key }];
                    });
                    return firebase.update(`${filesPath}/${file.key}`, { parentUid: parentId });
                });
            })
            .catch((error) => console.log(error));
    }

    function onFileDelete(file, key) {
        setUrls((prevState) => {
            return prevState.filter((item) => item.key !== key);
        });
        return firebase.deleteFile(file.fullPath, `${filesPath}/${key}`);
    }

    return (

                <input {...getInputProps()} />
                {isDragActive ? (

Drop the files here ...

                ) : (

{placeholder}

                            You can upload {maxFiles} file!

                )}

                {map(uploadedFiles, (file, key) => (

                        {file.name}
                        <Button variant="outlined" type="button" onClick={() => onFileDelete(file, key)}>
                            Delete File
                        </Button>

                ))}

    );
}

Erm... But this is... not RDU! This is RD

You can try this other library if you're into using Redux by the way
https://react-redux-firebase.com/docs/recipes/upload.html

Yeah but its works fine. I spent days with RDU but no success.

I use firebase, firestore, redux together in web and react-native and its perfect together and use react-redux firebase library as well.

May I take some time to disgest the second code please? That looks like a Gordon Ramsay recipe, simple yet delicious. Let me check the react-dropzone lib first and come back to see how I can modify this code.

I wish I could make your code work but I couldn't :-(
Do you have a codesandbox instance where it's working?
I checked the react-redux-firebase library too, but their recipe wasn't working either.
Why does such a simple thing as dropzone uploading have to be this frustrating?

Hi, i simplified the code for you, u can use without redux. I hope this help you.
firebase.js
// core imports
import firebase from 'firebase/app';
import 'firebase/firestore';
import 'firebase/database';
import 'firebase/auth';
import 'firebase/storage';
import 'firebase/functions';

const config = {
    apiKey: ...,
    authDomain: ...,
    databaseURL: ...,
    projectId: ...,
    storageBucket: ...,
    messagingSenderId: ...,
    appId: ...,
};

firebase.initializeApp(config);
firebase.firestore();

export default firebase;

dropzone.js
// core imports
import React, { useState } from 'react';
import { useDropzone } from 'react-dropzone';
import firebase from '../../../firebase/firebase'

function DropzoneInputNoRedux() {
    const { getRootProps, getInputProps, isDragActive } = useDropzone({ onDropAccepted: onFilesDrop, maxFiles: 5 });
    const storageRef = firebase.storage().ref('test')

    const [urls, setUrls] = useState([])

    console.log('urls', urls)

    function onFilesDrop(files) {
        files.map((item, index) => {
            let uploadTask = storageRef.put(item)
            uploadTask.snapshot.ref.getDownloadURL().then(function (downloadURL) {
                setUrls(prevState => {
                    return [...prevState, downloadURL]
                })
            })
        })
    }

    function onFileDelete(file, key) {
        setUrls((prevState) => {
            return prevState.filter((item) => item.key !== key);
        });
    }

    return (

                <input {...getInputProps()} />
                {isDragActive ? (

Drop the files here ...

                ) : (

                                You can upload 5 file!

                    )}

                {urls && urls.map((item, index) => {
                    return (

{item}

                    )
                })}

    );
}

export default DropzoneInputNoRedux;

Yes it works now! Yeaaaay! Thank you very much :D

You are welcome.

I tried the solution I offered to you and created a rest endpoint with Firebase functions and used the URL in this library. It works too :D

Nice. :)
Cause of i use redux, my solution better for me. But glad for your success. :)
Maybe u should post your code here, we somebody need too. :)

1) Firebase Part
Firebase installation
First install firebase cli
npm install -g -firebase-tools
Then login to your firebase from your console.
firebase login
... and set up with Functions > Your Project Name > Javascript > Install Dependencies step by step.
Creating a Firebase Rest Endpoint
Go to your functions folder in your code editor and install the necessary libraries to create the URL you are going to use in react-dropzone-upload
npm i cors busboy
paste the code below into the index.js and start editing the places with ---*---
//Core imports
const functions = require('firebase-functions');
const os = require('os');
const path = require('path');
const cors = require('cors')({origin: true});
const Busboy = require('busboy');
const fs = require('fs');

//Firebase Configuration
const { Storage } = require('@google-cloud/storage');
const projectId = ' -----your projectID-------';
const keyFilename = '----your keyFilename.json-------';
let gcs = new Storage ({ projectId, keyFilename });

//File Upload Endpoint
exports.uploadFile = functions.https.onRequest((req, res)=>{
    cors(req, res, ()=>{
        if(req.method !== 'POST'){
            return res.status(500).json({
                message: 'Not allowed!'
            });
        }
        const busboy = new Busboy({headers: req.headers});
        let uploadData = null;

        busboy.on('file', (fieldname, file, filename, encoding, mimetype)=>{
            const filepath = path.join(os.tmpdir(), filename);
            uploadData = {file: filepath, type: mimetype};
            file.pipe(fs.createWriteStream(filepath));
        });

        busboy.on('finish', ()=>{
            const bucket = gcs.bucket('---your storage link withOUT gs://---');
            return bucket.upload(uploadData.file, {
                uploadType: 'media',
                metadata: {
                    metadata: {
                        contentType: uploadData.type
                    }
                }
            }).then(()=>{
                return res.status(200).json({
                    message: 'it worked!'
                });
            }).catch(err =>{
                res.status(500).json({
                    error: err
                });
            });
        });
        busboy.end(req. rawBody);
    });
});

Then deploy your function with firebase deploy .
Open your firebase console in your browser and in the functions segment you will find the URL linked to the uploadFile function. It's in the orange place:

Notes:
Where is the keyFilename.json?
It's in your firebase Project Settings > Service Account. Generate a new private key and save it in the same folder where your functions/index.js is. And paste the name of that file.json into the appropriate place.

Where is the projectId?
It's the blue part in your General Settings

Where is the gcs.bucket?
It's the yellow part. Remove the gs:// and paste it.

2) React Dropzone Uploader Part
How can I use the link to the Firebase Endpoint?
Just modify the part below
{ url: 'REPLACE IT WITH THE LINK TO YOUR FUNCTION' }

Sample React Dropzone Uploader code:
//Core imports
import 'react-dropzone-uploader/dist/styles.css'
import Dropzone from 'react-dropzone-uploader'

const SingleFileAutoSubmit = () => {
  const toast = (innerHTML) => {
    const el = document.getElementById('toast')
    el.innerHTML = innerHTML
    el.className = 'show'
    setTimeout(() => { el.className = el.className.replace('show', '') }, 3000)
  }

//URL to the Firebase endpoint
  const getUploadParams = () => {
    return { url: 'REPLACE IT WITH THE LINK TO YOUR FUNCTION' }
  }

  const handleChangeStatus = ({ meta, remove }, status) => {
    if (status === 'headers_received') {
      toast(`${meta.name} uploaded!`)
      remove()
    } else if (status === 'aborted') {
      toast(`${meta.name}, upload failed...`)
    }
  }

  return (
    <React.Fragment>

Upload

      <Dropzone
        getUploadParams={getUploadParams}
        onChangeStatus={handleChangeStatus}
        maxFiles={1}
        multiple={false}
        canCancel={false}
        inputContent="Drop A File"
        styles={{
          dropzone: { width: 400, height: 200 },
          dropzoneActive: { borderColor: 'green' },
        }}
      />
    </React.Fragment>
  )
}
export default SingleFileAutoSubmit;

Enjoy your RDU with FB


Missing and/or poorly named plans

I'm trying to manage my licenses via Powershell and the license entries don't fully correlate between the following:

portal.office.com

the webpage reference https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/licensing-service-plan-reference

querying the names from Powershell via Get-AzureADSubscribedSku | sort skuid | select sku* -expand serviceplans

Since I'm trying to manage the licenses via Powershell I want all licenses and service plans to "foot" back to Powershell values. Some of the service plans line up exactly and they are not the problem.
Here are the ones I'm having difficulty with:
PortalServicePlan | LikelyPowershellServicePlan
Azure Rights Management | Microsoft Azure ActiveDirectory Rights
Information Protection for Office365  Standard | no guess
Insights by MyAnalytics | MyAnalytics_P2
Microsoft Kaizala Pro | Kaizala_Standalone
Microsoft Teams | Teams1
Office 365 Pro Plus | OfficeSubscription
Office for the Web | Office Online; SharepointWac
To-Do (Plan 2) | Bpos_S_Todo_2
Whiteboard (Plan 2) | no guess
Yammer Enterprise | Yammer_Enterprise
Thanks in advance.

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

ID: 7c245452-161d-89a1-c026-99a0721cf071
Version Independent ID: 16dec59a-eb83-1837-4efd-4645e7aeaed2
Content: Product names and service plan identifiers for licensing - Azure AD
Content Source: articles/active-directory/users-groups-roles/licensing-service-plan-reference.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @ajayanti1
Microsoft Alias: arjay

@riedyw Thanks for the feedback! We are investigating the issue.

@curtand Can you take a look at this?


Naive question: password sniffing from the console? How to "protect" against it?

There are command-line applications (e.g. runas.exe) that ask for a login/password before proceeding for some action (e.g. starting a new app with different user credentials...).
Even if echo is disabled on the console (through console API), the "terminal" (nowadays conhost.exe) would then send the keypresses (if read with ReadConsoleInput) / the text (if read with ReadConsole) to the command-line application.
On Windows <= Vista (and 7 too), command-line applications communicated to csrss/conhost through LPC. As I'm not a security expert I cannot assert how easy/hard it could be to spy on the LPC communications channel for reading the keypresses being sent corresponding to the entered password (what is possible however is to hook on the command-line app side the APIs ReadConsoleInputA/W and ReadConsoleA/W for this purpose).
With the new console architecture, it seems that there is now multiple places where the sniffing can be done: still hooking the APIs mentioned above, or adding a filter on top of \Device\ConDrv, or, with the new ConPTY and provided one implements an alternate terminal with that, looking through the communications pipes (or whatever is used for that purpose).
The question is: do you consider this to be an issue, or is it actually not an issue, in the sense that to perform the operations described above one would necessarily have/require administrator or SYSTEM rights?

I'm not totally sure tbh. I'm certainly no security expert - maybe @bitcrazed can conjure up someone who might have more input on the matter.

Hey @HBelusca Most of the potential vectors you describe above require admin rights, whereupon any hopes of maintaining "security" are largely null and void.
Alas, the description of how Console communicates with Command-Line apps presented in articles like this are not entirely accurate. A better description can be found in the Command-Line series, including our latest post on the new ConPTY infrastructure.
Specifically, the "LPC" mechanism presented in the former article is

actually carried out via ConDrv
passes via the kernel - it's not a magical user-mode <--> user-mode channel.


Snippets for header files

This is more a feature request than an issue.
The user snippets is really great but it would be nice (I suppose this is unique to c/cpp) if snippets could be applied to header files also.
I have tried manually copying the c.json to h.json but this does not seem to work.
Cheers

@adam3141 Please file an issue against cpp extension here https://github.com/Microsoft/vscode-cpptools/issues


Integrate updated grader and new XML format

CHANGES:

Added prepend
Renamed solutionTemplate to template
Added postpend
Removed grader from question
Added public to question
Added private to question
Renamed autograding_errors to autograding_results
Renamed autograding_errors to autograding_results
Updated XML parser to handle new tags
Refactored lambda worker to accept and store all results in a systematic format
Rewritten tests

TODO:

Add autograding_status and autograding_results to controller and view
Write new tests for new tags

Pull Request Test Coverage Report for Build 2369

23 of 29 (79.31%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.7%) to 97.778%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/cadet/jobs/autograder/lambda_worker.ex
5
6
83.33%

lib/cadet_web/views/assessments_view.ex
7
12
58.33%

Totals

Change from base Build 2366:
-0.7%

Covered Lines:
836

Relevant Lines:
855

💛  - Coveralls


Chaincode queryapproved

it seems completed.

https://github.com/Hyperledger-TWGC/fabric-admin-sdk/actions/runs/3731070221/jobs/6328861000#step:7:127


Change zoom in and out buttons

I have always disliked the zoom-in and zoom out buttons.  Currently, they look like this.   I would urge some variation on this:

done

done


[SDPAP-7863]added fix to have one publication author

Motivation and Context
We are updating publication author field to be restricted to one value (organisation taxonomy)across all projects then we need to update it in the FE.

Currently there is also an issue for publication author not being displayed on SSP project and this is happening because this field is contemplating one value in the BE.

JIRA issue: https://digital-vic.atlassian.net/browse/SDPAP-7863
BE ticket : https://digital-vic.atlassian.net/browse/SDPAP-7925
Ripple pr link: https://app.pr-1317.ripple.sdp4.sdp.vic.gov.au/
BE testing link: https://nginx-php.pr-323.content-reference-sdp-vic-gov-au.sdp4.sdp.vic.gov.au/
Changed

Updated the type string for author prop.
Changed to get the string value of author name from the field.
Added same change for the print page.

Tide_publication pr needs to be merged before to have this pr merged.
Screenshots

How Has This Been Tested?

Types of changes

[X ] 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)
[ ] Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)

Checklist

[ ] I've added relevant changes to the documentation.
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] My change requires a template update for create-ripple-app.
[ ] I have added template update script for next release.

Hey @yeniatencio,
One super minor thing, can you update this publication storybook story as well.

Is there a chance some sites will return an array of authors and others will return the single value while the backends are being updated? Just wondering if we would need to support both.
Cheers

Hey @lambry , I have created a pr in core to have the publication author field a single value in all BEs.  So no chance to have more than 1 single value for Publication author.
PS, I have updated the storybook, Thanks

Hey @dylankelly , can you please re-review, i have now changed the code to handle the case of older tide with an array, and newer tide with a single value which was David's feedback.

Thanks @yeniatencio - appreciate you adding this to prevent any surprises.

Thank to you @dylankelly . Good thing to anticipate that scenario.


fix(inputs): add dynamic validation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support for airflow 2.5.0?

Hi,
Airflow 2.5.0 was released earlier this month.
At the moment we can't use it because of the dependencies in this project.
Are there plans to test it with 2.5.0 and update the package?
Thanks!

Will potentially do it in a week or so. Contribution is welcome! :)
We have auto-tests, so you may make a simple contribution with a version bump, and I will approve the CI pipeline to run.
Do not forget to also update a versions matrix in README and also in the workflow code.

Thanks! will have a look at the required changes to at least run the tests. Not sure what further changes might be required for 2.5.0

Yes, quite often it is as simple as a just increasing the version. I would recommend you to clone the airflow-clickhouse-plugin, install Airflow 2.5.0 and clickhouse-driver (via simple pip install) and run the tests to check locally if it works. And make changes if not.

Released: https://github.com/bryzgaloff/airflow-clickhouse-plugin/releases/tag/v0.10.0


Update C3 OpenAPI template to allow users to pick either Hono or itty-router

What this PR solves / how to test
This pr updates the C3 OpenAPI template to allow users to pick either Hono or itty-router.
Example usage:
npm create cloudflare@latest -- --type openapi --framework hono
npm create cloudflare@latest -- --type openapi --framework itty-router
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[x] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[ ] Required / Maybe required
[x] Not required because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Not necessary because:

Builds are failing because the PR is done from a forked repo, but should otherwise be green

I've updated the pull request, to allow users to pick either Hono or itty-router as the base framework for this c3 template.
Pull request is ready to be merged

Hey @jculvey , the C3 E2E builds are failing for reasons not related to this pr, do you think you could merge this?


Implement a windowing system

This will allow users to modify the app layout to their preferences. We’ll have separate windows for:

Settings (was Controls)
Mappings (was Mappings Visual)
XML (was Mappings XML)
Renders

Unless there’s good reason, all windows should be moveable and resizable.
We can refine handling of Renders / Instances later.

Done


Support for phones with foldable displays

On the phones like the Z Fold 4, the interface was pretty bad in unfolded mode for the POI editor. In this PR, the POI list has been shifted to the right on those phones, taking up exactly 1/2 of the screen, which is much more convenient.

Here are some examples of how it looks on the regular screen, and on the big one.

Hey Astrrra, thanks for the PR! Video samples from you channel look really neat. To merge this, first I'd like to remove formatting changes, to see what's actually been changed. I think this change affects other phones too a little too much.
Did you check reported width and height for your phone from MediaQuery?

It's a bit stale and I don't think there will be a further development, so I'm closing this. But the idea is good, planned it in #655.


Improve default stream selection in Organization settings

At present, it's possible to enter a blank or invalid stream name under Organization settings > Default streams, producing an error:

Entering a stream that is already on the list does nothing, with no feedback to the user.
Instead, the stream selection box should be a search/selection box, similar to Organization settings > Organization settings > New stream notifications. No stream should be selected by default. Streams that are already on the list should not appear in the selection drop-down.
The "Add stream" button should be disabled if no stream has been selected. (Tooltip: No stream selected)

@zulipbot claim

@zulipbot claim.

@Ujjawal3 I guess this will be solved by #21688, which is close to being merged.


feat(client/linux): revamp the Linux VPN routing logic

This PR simplifies the Linux VPN routing architecture by:

Removing the daemon service: All routing is now handled by the app process and its backend library.
Using a separate routing table: Prevents pollution of the user's default routing table.
Leveraging NetworkManager for DNS settings: Provides more robust DNS configuration and avoids conflicts with other resolver services.

This approach minimizes changes to the user's network configuration and improves overall stability.
Next steps: See https://github.com/Jigsaw-Code/outline-apps/pull/2291#issuecomment-2518743663
Tested on Ubuntu 22 and Ubuntu 24

TODO Items

[x] Routing Logic PoC
[x] TCP Traffic Routing
[x] UDP Traffic Routing
[x] Handling concurrency
[x] IPv4 Traffic Routing
[x] Initial Connectivity Check
[ ] IPv6 Traffic Routing (another PR)
[ ] Refresh UDP connectivity (another PR)
[ ] Network Change Monitor (another PR)
[ ] Network Change Connectivity Check (another PR)
[ ] Delete old routing service code (another PR)
[ ] Handle cancellation gracefully (another PR)

@fortuna @sbruens  Any thoughts?

@fortuna I cleaned up some the code in the vpn package, and also refactored the architecture according to the review comment. Please take another look.


Implement metaprogramming utilities

The target architecture is something like:
struct array_data
{
        data_descriptor type;
        std::int64_t length = 0;
        std::int64_t offset = 0;
        dynamic_bitset<std::uint8_t> bitmap;       // buffer 0 in C struct
        std::vector<buffer<std::uint8_t>> buffers; // buffer 1 to n in C struct
        std::vector<array_data> child_data;
};

template <class T, class L = get_default_layout_t<T>>
class array_impl
{
    L m_layout;
    array_data m_data;
};

using array_variant = std::variant<
    array_impl<std::unint8_t>,
    array_impl<std::int8_t>,
    ...
    // all required types already supported in data_type.hpp
>;

We need to implement tools such as arrow_traits to retrieve the different associated types to a basic type:
template <class T>
struct arrow_traits;

template <>
struct arrow_traits<std::unint8_t>
{
    using layout_type = primite_layout<std::uint8_t>;
};

It would be nice to use concepts / constraints to reduce the amount of code, and to be able to generate array_impl and other related types based on a typelist of supported types.

This issue is too big to be implemented in a single PR; see below the list of smallest issues for implementing it (will be updated while doing the work):

Metaprogramming basic tools: #67
Support for half float type: #68

@JohanMabille Is there something missing or should we close this?

We can close it.


travis: test on x86 32-bit as well

Codecov Report

Merging #57 into master will decrease coverage by 1.91%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #57      +/-   ##
==========================================
- Coverage   90.16%   88.25%   -1.92%
==========================================
  Files           5        5
  Lines         366      366
==========================================
- Hits          330      323       -7
- Misses         36       43       +7

Impacted Files
Coverage Δ

src/Curl/Easy.jl
91.97% <100.00%> (+0.05%)
:arrow_up:

src/Curl/utils.jl
75.75% <0.00%> (-21.22%)
:arrow_down:

src/Curl/Multi.jl
91.81% <0.00%> (-0.08%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 52b4677...35f2a4b. Read the comment docs.


tailscale: 1.20.1 -> 1.20.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tailscale/versions.
meta.description for tailscale is: "The node agent for Tailscale, a mesh VPN built on WireGuard"
meta.homepage for tailscale is: "https://tailscale.com"
meta.changelog for tailscale is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2/bin/tailscale had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2/bin/.tailscale-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2/bin/tailscaled had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2/bin/.tailscaled-wrapped had a zero exit code or showed the expected version
0 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 1.20.2 with grep in /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2
found 1.20.2 in filename of file in /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
tailscale

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tailscale https://github.com/r-ryantm/nixpkgs/archive/356869f27dcabb116c2f07eb8965cc0727eb8b6e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2
ls -la /nix/store/4zx9n2nafcmpcdkzmcm0s3jfj6bijb9m-tailscale-1.20.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

tailscale

Maintainer pings
cc @danderson @martinbaillie @kalbasit for testing.

Update is working fine for me!


This bundle is invalid. The value for key CFBundleShortVersionString in the Info.plist file must contain a higher version

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I have my CFBundleShortVersionString set to 5.0.1, but TestFlight is thinking it's 4.9.0. The latest version in TestFlight and AppStore is 5.0.0. Version 4.9.0 is the previous version. I couldn't find 4.9.0 anywhere in my code. No iOS files are committed to the repo. I am starting from a fresh cloned version of the repo.
The error message is:
[19:13:07]: ERROR ITMS-90062: "This bundle is invalid. The value for key CFBundleShortVersionString [4.9.0] in the Info.plist file must contain a higher version than that of the previously approved version [5.0.0]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring"
Return status of iTunes Transporter was 1: ERROR ITMS-90062: "This bundle is invalid. The value for key CFBundleShortVersionString [4.9.0] in the Info.plist file must contain a higher version than that of the previously approved version [5.0.0]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring"
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

EDIT: If in the upload_to_testflight step I submit the generated IPA file from the build_ios_app step, then it does work.
Command executed

bundle exec fastlane deploy:ios
Environment

 ✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.6

Ruby
2.6.3

Bundler?
true

Git
git version 2.24.3 (Apple Git-128)

Installation Source
~/Tools/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.4/bin/fastlane

Host
Mac OS X 10.15.6 (19G2021)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.7

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
OpenSSL::SSL::VERIFY_PEER = OpenSSL::SSL::VERIFY_NONE

ENV['app_identifier'] = "com.bcbsnc.BCBSNC"
ENV['app_name_sanitized'] = "BlueConnect"
ENV['TEAMS_WEBHOOK'] = "https://outlook.office.com/webhook/2f6f8317-0008-48bf-9845-e58dd52cc546@8554e7b2-e668-4c1c-8d27-3b12f5c733ac/IncomingWebhook/e62e452a581f4314bae9ca765e28ed49/77343f59-1ab0-4dd7-b44a-2797e72644a0"

# Update Fastlane
update_fastlane

private_lane :clean do
	sh "cd .. && rm -rf www/* && rm -rf node_modules && rm -rf bower_components && rm -rf platforms/ && rm -rf plugins"
end

private_lane :prepare do
	# Yes, prepare is in there twice, I've seen where it will only install 1 os when you run prepare
	# but running it again will add the other. This is a safe operation so if it does add both the
  # second run will not hurt anything
  # cordova prepare populates platforms and plugins folders
	sh "cd .. && npm i && npx bower install && npx cordova prepare && npx cordova prepare"
end

private_lane :tag do |options|
  add_git_tag(
    tag: "#{ENV['next_version']}_#{ENV['next_build']}-#{ENV['BUILD_CONFIG']}",
    force: true
  )
end

private_lane :git do
  push_to_git_remote(
    remote: "origin",
    local_branch: "#{ENV['current_branch']}",
    remote_branch: "#{ENV['current_branch']}",
    force: true,
    tags: true,
    no_verify: true
  )
end

private_lane :notify_success do |options|
  title = options[:title]
  success = options[:success]
  build_number = options[:build_number]
  release = options[:release]
  teams(
    title: title,
    message: "",
    facts:[
      {
        "name" => "Built by",
        "value" => "Magical Unicorns 🦄🌈"
      },
      {
        "name" => "Platform",
        "value" => release
      },
      {
        "name" => "Build",
        "value" => build_number
      }
    ],
    teams_url: ENV['TEAMS_WEBHOOK']
  )
end

def notify_fail(exception)
  teams(
    title: "Failed to build app",
    message: "",
    facts:[
      {
        "name" => "Build Date",
        "value" => Time.new.to_s
      },
      {
        "name" => "Built by",
        "value" => "Magical Unicorns 🦄🌈"
      },
      {
        "name" => "Error",
        "value" => exception
      }
    ],
    teams_url: ENV['TEAMS_WEBHOOK']
  )
end

def on_error(exception)
  notify_fail(exception)
end

private_lane :promote_latest_testflight_build do
  puts "Promoting #{ENV['next_version']} (#{ENV['current_build']}) for review."

  deliver(
    submit_for_review: true,
    #automatic_release: true,
    force: true, # Skip HTMl report verification
    skip_metadata: true,
    skip_screenshots: true,
    skip_binary_upload: true,
    submission_information: {
      add_id_info_uses_idfa: false,
      content_rights_has_rights: true,
      content_rights_contains_third_party_content: true,
      export_compliance_platform: 'ios',
      export_compliance_compliance_required: false,
      export_compliance_encryption_updated: false,
      export_compliance_app_type: nil,
      export_compliance_uses_encryption: false,
      export_compliance_is_exempt: false,
      export_compliance_contains_third_party_cryptography: false,
      export_compliance_contains_proprietary_cryptography: false,
      export_compliance_available_on_french_store: false
    }
  )
end

lane :download_app_store_assets do
  deliver download_screenshots
  deliver download_metadata
end

platform :ios do
  desc 'Setting variables'
  before_all do
    ENV['DEPLOY_TARGET'] = ENV['DEPLOY_TARGET'] || UI.select("Which deploy target do you want to use?: ", ["TestFlight", "App Store"])
    ENV['BUILD_CONFIG'] = ENV['BUILD_CONFIG'] || UI.select("Which deploy target do you want to use?: ", ["ci", "staging", "prod", "prod:ci", "registration"])
		ENV['ios_path'] = "platforms/ios/"
		ENV['ios_project_path'] = "#{ENV['ios_path']}#{ENV['app_name_sanitized']}.xcodeproj"
		ENV['ios_workspace_path'] = "#{ENV['ios_path']}#{ENV['app_name_sanitized']}.xcworkspace"
    ENV['FASTLANE_USER'] =<EMAIL_ADDRESS>    ENV['FASTLANE_PASSWORD'] = "Bcbsnc1!"
    ENV['MATCH_PASSWORD'] ="weboffice"

    # Versioning
    readme_yaml = File.read('../CHANGELOG.yml')
    readme_data = YAML.safe_load(readme_yaml)

    # Constants
    ENV['next_version'] = readme_data['upcoming']['version']
    ENV['current_build'] = "#{latest_testflight_build_number(version: ENV['next_version'], initial_build_number: 0).to_i}"
    ENV['next_build'] = "#{ENV['current_build'].to_i + 1}"
    ENV['current_branch'] = git_branch
  end

  desc 'Unlocking keychain'
	private_lane :unlock do
		sh 'security unlock-keychain -p weboffice'
  end

  desc 'Building WWW folder'
  private_lane :build_www do
    sh "cd .. && npm i "
    sh "cp ../envs/.env.#{ENV['BUILD_CONFIG']} ../.env"
    sh "cd .. && npx gulp build:#{ENV['BUILD_CONFIG']}"
  end

  desc 'Building Cordova App for iOS'
	private_lane :build do
    clean
    prepare
    build_www
    # set version and build numbers
    increment_version_number(version_number: ENV['next_version'], xcodeproj: ENV['ios_project_path'])
    increment_build_number(build_number: ENV['next_build'], xcodeproj: ENV['ios_project_path'])
    sh "npx cordova build ios --release --no-telemetry"
	end

  desc "Deploy iOS App to TestFlight"
  lane :deploy do
    begin
    # build app assets
    unlock
    build

    # app signing
    sync_code_signing(type: "appstore", readonly: true)
    update_code_signing_settings(
      path: ENV['ios_project_path'],
      team_id: CredentialsManager::AppfileConfig.try_fetch_value(:team_id),
      targets: ["#{ENV['app_name_sanitized']}"],
      profile_name: 'match AppStore com.bcbsnc.BCBSNC',
      build_configurations: 'Release',
      code_sign_identity: 'Apple Distribution'
    )

    # create build
    ipa_name = "#{ENV['app_name_sanitized']}_#{ENV['BUILD_CONFIG']}_#{ENV['next_version']}.ipa"

    build_ios_app(
      scheme: ENV['app_name_sanitized'],
      workspace: ENV['ios_workspace_path'],
      silent: true,
      output_directory: ENV['ios_path'],
      output_name: "#{ipa_name}",
    )

    # Deploy to TestFlight
    if ENV['DEPLOY_TARGET'] == "TestFlight"
      puts "Submitting #{ENV['BUILD_CONFIG']} build to TestFlight"
      # stop VPN
      sh "launchctl unload /Library/LaunchAgents/com.paloaltonetworks.gp.pangp*"

      upload_to_testflight(
        skip_waiting_for_build_processing: true,
        changelog: "#{ENV['BUILD_CONFIG']} build #{ENV['next_version']}", # Test Details
      )

      # Notify
      notify_success(
        title: "🎉🎉 New BCM Deploy: #{ENV['next_version']} (#{ENV['next_build']}) #{ENV['BUILD_CONFIG']} 🎉🎉",
        success: true,
        build_number: "#{ENV['next_version']} (#{ENV['next_build']}) #{ENV['BUILD_CONFIG']}",
        release: "TestFlight"
      )

    # Deploy to App Store
    elsif ENV['DEPLOY_TARGET'] == "App Store"
      puts "submitting to app store"
    end

    # start VPN
    sh "launchctl load /Library/LaunchAgents/com.paloaltonetworks.gp.pangp*"
    rescue => exception
        on_error(exception)
    end
  end

  desc "Push latest TestFlight build for review"
  lane :release do
    begin
      # Versioning
      readme_yaml = File.read('../../CHANGELOG.yml')
      readme_data = YAML.safe_load(readme_yaml)

      # Constants
      current_version = readme_data['upcoming']['version']

      # Promote build
      set_changelog(
        changelog: "#{readme_data['upcoming']['user_facing'][0]}",
        version: current_version
      )
      promote_latest_testflight_build

      # Notify
      notify_success(
        title: ":tada: :tada: New BCM Prod Release: #{current_version} (#{ENV['current_build']})",
        success: true,
        build_number: "#{current_version} (#{ENV['current_build']})",
        release: "App Store"
      )

      puts "All done."
    rescue => exception
        on_error(exception)
    end
  end
end

platform :android do
  before_all do
    ENV['DEPLOY_TARGET'] = ENV['DEPLOY_TARGET'] || UI.select("Which deploy target do you want to use?: ", ["Alpha Store", "Play Store"])
    ENV['BUILD_CONFIG'] = ENV['BUILD_CONFIG'] || UI.select("Which deploy target do you want to use?: ", ["ci", "release", "registration"])
    ENV['CORDOVA_ANDROID_RELEASE_BUILD_PATH'] = "platforms/android/app/build/outputs/apk/debug/app-debug.apk"
  end

  desc "Deploy android app on play store"

  lane :deploy do
    cordova(
      platform: 'android',
      keystore_path: './prod.keystore',
      keystore_alias: 'prod',
      keystore_password: 'password'
    )
    supply(apk: ENV['CORDOVA_ANDROID_RELEASE_BUILD_PATH'])
  end
end

`./fastlane/Appfile`
app_identifier("com.bcbsnc.BCBSNC") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

itc_team_id("389101") # App Store Connect Team ID
team_id("7R8JY68R4K") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.158.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-cordova
3.0.0
✅ Up-To-Date

fastlane-plugin-teams
0.2.0
✅ Up-To-Date

Loaded gems

Gem
Version

bundler
2.1.4

rake
13.0.1

CFPropertyList
3.0.2

concurrent-ruby
1.1.7

i18n
0.9.5

minitest
5.14.2

thread_safe
0.3.6

tzinfo
1.2.7

activesupport
<IP_ADDRESS>

public_suffix
4.0.6

addressable
2.7.0

httpclient
2.8.3

json
2.3.1

algoliasearch
1.27.3

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.365.0

aws-sigv4
1.2.2

jmespath
1.4.0

aws-sdk-core
3.105.0

aws-sdk-kms
1.37.0

aws-sdk-s3
1.79.1

babosa
1.0.3

claide
1.0.3

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.13.1

ethon
0.12.0

typhoeus
1.4.0

cocoapods-core
1.9.3

cocoapods-deintegrate
1.0.4

cocoapods-downloader
1.4.0

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.1.0

cocoapods-trunk
1.5.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.6.6

ruby-macho
1.4.0

nanaimo
0.3.0

xcodeproj
1.18.0

cocoapods
1.9.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.20

declarative-option
0.1.0

digest-crc
0.6.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.0.0

excon
0.76.0

multipart-post
2.0.0

faraday
1.0.1

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.0

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.14.0

googleauth
0.13.1

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

google-cloud-env
1.3.3

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

google-cloud-storage
1.28.0

mini_magick
4.10.1

plist
3.5.0

rubyzip
2.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

fastlane-plugin-cordova
3.0.0

fastlane-plugin-teams
0.2.0

generated on: 2020-09-04

If you open the project / workspace in Xcode, what version / build numbers are shown?

They are the correct ones in xcode, matching the info.plist file


Tracking issue for the memory64 proposal

We've already got a FIXME in the code so I'd like to go ahead and create a tracking issue for supporting this.
Currently wasmparser should have all the validation done for us, but there's translator and runtime work that needs to be done to support the memory64 wasm proposal.

Closing in favor of https://github.com/bytecodealliance/wasmtime/issues/572


New IDF file

Question ❓
Dear @AlejandroCN7,
When setting up a new environment for a new building I get some errors. I followed all the steps described here.
I will add some screenshots about what I did.
Firstly I added two files:
IDF and DDY
The original IDF file was of version 9.1.0, I created a version 9.5.0 with IDFVersionUpdater. Afterwards, I created a .ddy file as described. However this file was not the same as in here. So I rewrote it manually.
What I mean by that is that the file looked like this after simulation in EnergyPlus:

And I rewrote it so it has the same format as the other .ddy files.

After I created the id like explained:

and created the default variables:

After trying to perform simulations with the new building I get the following error:

Do you maybe know what I am doing wrong here?
Kind regards,
Michiel
Checklist

[x] I have read the documentation (required)
[x] I have checked that there is no similar issue in the repo (required)

:pencil: Please, don't forget to include more labels besides question if it is necessary.

Hi @MichielKempkens,

IDF and DDY

You mean RDD instead of DDY, right?

The original IDF file was of version 9.1.0, I created a version 9.5.0 with IDFVersionUpdater. Afterwards, I created a .ddy file as described. However this file was not the same as in here. So I rewrote it manually.

As it is mentioned in step 3 of the documentation that you cited: "Make sure that Output:VariableDictionary object in IDF has the value Regular in order to RDD file has the correct format for Sinergym." have you done that? You shouldn't have to rewrite the format of the RDD file.

After trying to perform simulations with the new building I get the following error:

Looking at the screenshot, it seems that the problem is that the name of the environment ID does not match the regular expression that gym environments must have. See this Gym section in their own documentation to see the correct syntax.
The error is not related to the sinergym tool directly. If you have questions regarding the environments or with one of our dependencies, I encourage you to write to them directly.
Regards.

Hi @AlejandroCN7,
Thank you for answering. It was actually a simple fix. For people experiencing the same, just change the id. As can be seen above I used id="EDGE_Olympic_env". If you would change this into something like Eplus-EDGE-v1 (just like the examples from sinergym) it works perfectly fine.
Now I got actually a new one:

So something is wrong with the schedules set. If I delete that part in the IDF it just give other errors on the schedule. Do I have to initialise schedules in a specific way?
Best,
Michiel

Hi @MichielKempkens,
It seems to be a bug in the IDF you are trying to use. We do not know the origin of that IDF and therefore have no further information to be able to answer you. It seems that the IDF is not able to understand the "fraction" data type. Check that it is defined somewhere.
Regards.


[Review only] Add content store document type attribute for search

Add content_store_document_type to be sent to rummager.
Also, currently we have in place a task to republish documents to Publishing API and
Rummager, but in some cases we only want to republish to rummager in
order to update the document.
This commit adds an extra task into the republish.rake file to republish
all documents to rummager.
And also adds content_id, rendering_app and publishing_app
This might be best to be reviewed commit by commit (will rebase afterwards)
Trello:
https://trello.com/c/iMotNdUv/461-add-more-document-type-to-search

This needs more testing but I wanted to know your opinion on the implementation first.

@tijmenb I believe I've addressed your comments. Let me know your thoughts.

We think this work might have caused problems after running on Integration and we have decided to run the original republish.rake task


Large response getting cut off.

simple_server.zip
Reading the response of a GET request using .String() arbitrarily cuts off the full response when the response is quite large (+5MB). The issue appears to occur when reading the internal buffer from the response object; the full response string is not returned.
Using http.Get() works fine:
Attached is a standalone project that reproduces the issue. The attached project has a simple server that returns a hard coded json string:
src/simple_server
There are also two clients:
src/grequests_client (reproduces the issue)
src/http_client (works fine)
The error occurs in grequests_client when trying to decode the json response:  'use of closed network connection'. But inspecting the json response using resp.String() or resp.Byte() shows that only part of the json response is returned.

@matsch01 thank you for submitting this bug report. To help better address this bug can you please let me know which OS and go version you were using when you encountered this issue

I'm using Windows 7 and Go 1.7.
Sent from my iPhone

On Sep 20, 2016, at 9:31 PM, Levi Gross<EMAIL_ADDRESS>wrote:
@matsch01 thank you for submitting this bug report. To help better address this bug can you please let me know which OS and go version you were using when you encountered this issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks! I am looking at the issue (thanks for the sample code) and I can reproduce it

I have removed the finalizer (which was closing the response too early) and will be pushing the build as soon as my branch's tests run

Can you please checkout the latest source code and tell me if you continue to encounter this issue?

Issue has been resolved. Thank you.
On 20 September 2016 at 23:12, Levi Gross<EMAIL_ADDRESS>wrote:

Can you please checkout the latest source code and tell me if you continue
to encounter this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/levigross/grequests/issues/30#issuecomment-248499544,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABnTyJEuzNcE2egKVlWVdUESKdD000u7ks5qsKC6gaJpZM4KBxCl
.


Feature: Rate Limiting

First of all, nice bundle! The docs are beautiful!
I have my own home grown honeypot/short submit system that I'm going to switch to this bundle.
Recently, we have been getting hammered by spam that gets past these two protections so I've implemented a rate limiting system: "can only submit a valid form once per minute and 5 times per hour"
Thought it could be a nice feature for this bundle.

Thanks for the kind words   💯
Rate limiting is most certainly one to be put on the list. I'm also considering wrapping up Recaptcha, Akismet and maybe even the classic math questions in here!

By the way you should most definitely also look at the URL counting and banned scripts. On most of our sites we're getting hammered by Cyrillic spam. On our company website this bundle has already managed to reduce spam to literally zero like this:
antispam:
    profiles:
        default:
            banned_scripts:
                scripts: [cyrillic]
                max_percentage: 40

            url_count:
                max: 3
                max_identical: 1

            honeypot: email_address

            timer:
                min: 3
                max: 14400

Definitely will be adding these.

Recipe is now also submitted at https://github.com/symfony/recipes-contrib/pull/1561/files with recommended default config.


Manage compeltion for YUI().use(' // here ctrl+Space shows module

Manage compeltion for YUI().use(' // here ctrl+Space shows module

I close this issue. See https://github.com/angelozerr/tern-yui3/issues/6


SEP-10: get home domain from TOML server URL

For SEP-10 home domain, we were incorrectly passing the URL where the TOML file is hosted, instead of getting a transaction-specific server URL from the TOML file itself. This PR should fix that. :crossed_fingers:
Update SEP-6. SEP-24, and SEP-31 transactions.

Preview is available here:http://stellar-demo-wallet-client-pr261.previews.kube001.services.stellar-ops.com/

The current behavior is correct, closing the PR.


fix: Updated comments and docs to match server port that is now 8098

Consistency updates to match server port that is now 8098 instead of 8088 as noted by @atelles in https://github.com/jonashackt/spring-boot-vuejs/issues/85#issuecomment-595946585.

Pull Request Test Coverage Report for Build 514

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

Totals

Change from base Build 513:
0.0%

Covered Lines:
45

Relevant Lines:
53

💛  - Coveralls

Thanks @guillevc 👍


[Feature request] Headless facets sorting options

Hello!
Question of even feature request: We're using Headless facet in loads of places. It's great but we're looking right now into improving soritng of options there.
There is a sortBy option: https://docs.coveo.com/en/headless/latest/reference/search/controllers/facet/#sortby
but we're missing there two things:

numeric sort - asc and desc
and some kind of custom sort - like we want to promote some option to be first one, no matter what

What would be the best way to achive that? Just loop over results and sort them as we want? Or there is an option already that could do that? Or maybe there's something you plan to implement soon, so we could wait till it's there? ;) Just so we don't start customising things and like two days later it's in the library :D
Thanks!

Hey @marbor3 , can you details the numeric one? 🤔
I'm thinking that alphanumeric would do the trick if there is no letter in the data where you do the sort, because well essentially alphanumeric sort is an ASCII # sort, and the order of the code of the numbers is the same as the numerical order.
Custom sort, afaik, we don't have anything going, and probably won't: the sort occurs backend-side, and we don't plan to allow custom logics to run back there. So you'll need to hook up something of your own to sort out the value client-side.
This may come with bad reporting or inaccurate reporting tho I think (e.g. we return foo first and bar as last, with your sort bar ends up first and foo is never clicked on. This would probably light up some alerts.
For that reasons, I'd advise against doing custom sort without checking what it entails either through our Community Slack or through your contacts @ Coveo that will bring your request/question to the adequate teams

Closing due to inactivity. Please reopen if necessary.


How to use Audio Options: --hardware_accel in Windows 10. It is not mentioned in the documentation.

Hi，
How to use Audio Options: --hardware_accel in Windows 10. It is not mentioned in the documentation.

Well --hardware_accel is not in Audio Options section and does nothing when processing audio files by themselves but is useful. Hardware_accel can make processing videos much faster though.
I'll put a guide in the docs eventually.

nevermind. It's literally useless now. I might give it special attention if I figure out some use.


MNT adjust deps in build and host

Adjust build and host dependencies according to https://github.com/conda-forge/fastcan-feedstock/pull/4

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Maybe I'm wrong, but I think the build-system.requires in pyproject.toml is more similar to the host deps in cross-compilation.


Bug: synology "#recycle" folder deletes original folder

Description
So, i wanted to try the app again after a few years, so i opened my network drive and tried to empty my #recycle folder.
Once i tried to empty it the folder list has been scanned for files to delete but instead of deleting the #recycle child items it scanned the original folder and tried to delete all files.
I was unable to cancel the operation by restarting my synology nas to prevent further damage.
Steps To Reproduce

Have a synology nas devices
enable recycle bin folder to prevent direct deletion
delete single items in folders so i moves the file links to the recycle bin
empty #recycle (i did it with ctrl+a & shift+del)
files from the original folder will be scanned and deleted

Files Version
<IP_ADDRESS>
Windows Version
Edition	Windows 11 Pro Version	23H2 Installed on	26/09/2024 OS build	22631.4602 Experience	Windows Feature Experience Pack 1000.22700.1055.0
User ID
No response
Log File
there is no log since its not really an error.

Thanks for the report, is #recycle a NAS folder or do you mean the normal Windows Recycle bin?

"#recycle" is a nas folder created by a feature from synology


lights should take LV wire to make and break

Description

you should need to use LV wire to make dock things because

need wire to power thangs
for robustness, make spear in perma and keel seccies three escape

i'm gonna close this issue because it is completely incomprehensible


Allow hosts to share abitrary files with guests outside of the folder/solution root

In addition to multi-root support (#46) we could allow hosts to share arbitrary files with guests that they have opened up in their editor. (Also related to #57 - sharing unsaved files.)
Give an up-vote (👍) reaction if you'd like to have this ability.

@Chuxel GitHub should allow +100 upvotes in addition to +1 upvotes. Specially for this issue.

@DRSDavidSoft Feedback taken! We’re actually working on this right now, and should have something to share very soon 😁

@lostintangent Thanks for working on it! Your work on this extension is appreciated by thousands, even if not all of the users visit and use GitHub.

This feature is now available in the latest update for VS and VS Code 🎉 If a host opens a file that it located outside of the shared directory/solution, then any guest that is following them will automatically see the contents of that file and can co-edit it with them. Let us know if you run into any problems with this experience and/or have feedback on it. Thanks!


[docs] bump development version to <IP_ADDRESS>

Updates for once v3.3.3 release is complete (#5525).

updates cran-comments.md
bumps development version in the repo from <IP_ADDRESS> to <IP_ADDRESS>, so building from master will result in a newer version than the latest released version

/gha run r-configure

this can't be merged until YET ANOTHER blocking CI issue is fixed 😭
#5569

Just updated this now that #5569 has been resolved. I also manually cancelled the CUDA run on master, so that this PR will hopefully complete its checks faster and can be merged.
The CUDA jobs being serial (only one job can run at a time, across all commits) makes it difficult to merge a lot of things in quick succession.


[vcos:bugfix] armv8-r:optimize libc string apis with asm

Optimize libc string apis(memcpy/memset/memmove/memchr/strcmp/strlen) with arm32 assembly instruction including vfp and neon. Add arch releated elf parsing
Note: Please adhere to Contributing Guidelines.
Summary
optimize armv8r cortex-r52 libc apis.
Impact
armv8r cpu libc apis.
Use arm32 assemble / neon instructions to optimize libc apis (memcpy/memset/memmove/memchr/strcmp/strlen)
Testing
Tested on armv8r cortex-r52 cpu.

[Experimental Bot, please feedback here]
No, this PR description does not fully meet the NuttX requirements.  Here's why and how to fix it:
Missing Information/Insufficient Detail:

Summary:  While it mentions optimization, it lacks crucial details.

Why is this change necessary? Is there a performance bottleneck? Are the current implementations inefficient?
What functional part of the code is being changed? Be specific – mention the files/functions modified (e.g., libc/string/memcpy.c).
How does the change exactly work?  "Use arm32 assemble / neon instructions" is too vague. Briefly explain the optimization techniques used (e.g., loop unrolling, SIMD instructions).  Mention if any new functions were added.  The mention of "arch related elf parsing" seems unrelated to string functions and needs further explanation or belongs in a separate PR.

Impact:  The impact descriptions are too brief.

Is new feature added?  If the ELF parsing is new, say so explicitly. Otherwise, it's likely "Is existing feature changed?" is YES.
Impact on user: Probably NO, but if there are any changes to function behavior (however subtle), explain them.
Impact on build:  Possibly YES, as assembly code is being added. Specify any new build flags, dependencies, or changes to the build system.
Impact on hardware:  Specify the specific ARM architectures affected (armv8r, cortex-r52 is a good start, but mention if others are impacted).  Are there any implications for other architectures?
Impact on documentation: Likely YES if new features are added or if the behavior of existing functions changes. State whether documentation updates are included in the PR.
Impact on security:  Consider potential security implications of optimized code (e.g., buffer overflows if optimizations change memory access patterns). If none, state "NO."
Impact on compatibility:  Are there any compatibility concerns with older versions of NuttX or other ARM architectures?

Testing:  The testing description is inadequate.

Build Host(s): Provide details about the build host OS, CPU architecture, and compiler version used.
Target(s):  Be more specific about the target board and configuration.
Testing logs:  Absolutely essential! Include actual logs demonstrating the functionality before and after the change.  Show performance benchmarks if performance improvement is the goal.  Demonstrate correctness by showing input and output.

Example of an Improved Summary:
This PR optimizes several libc string functions (memcpy, memset, memmove, memchr, strcmp, strlen) for the armv8r architecture (specifically cortex-r52) to improve performance.  The current C implementations are inefficient, particularly for larger data sizes. This optimization utilizes ARM32 assembly language and NEON SIMD instructions to perform operations on multiple bytes simultaneously. Key optimizations include loop unrolling and specialized instructions for memory operations.  This PR also adds a new ELF parsing function [...] (Explain its purpose and connection, or remove this if unrelated).
By providing more specific details in each section, the PR will be much clearer and easier for reviewers to evaluate.  Remember to follow the contributing guidelines and provide concrete evidence of testing.


Unable to override global methods

Due to the webpack commit f4990f8a0d8e545fe80d53ea4760fcf3cd8376ec, it looks globally exposed methods from cornerstone are no longer able to be overridden.
> cornerstone.getPixels
< function (element, x, y, width, height) {                                                            // 2562

> cornerstone.getPixels = function override(x,y){}
< function override(x,y){}

> cornerstone.getPixels
< function (element, x, y, width, height) {                                                            // 2562

As you can see the method that is assigned to it.
Upon quick glance, it looks like this is because webpack is not exposing a setter for the methods that are exposed by the module:
/******/ 	// define getter function for harmony exports                                                                // 41
/******/ 	__webpack_require__.d = function(exports, name, getter) {                                                    // 42
/******/ 		if(!__webpack_require__.o(exports, name)) {                                                                 // 43
/******/ 			Object.defineProperty(exports, name, {                                                                     // 44
/******/ 				configurable: false,                                                                                // 45
/******/ 				enumerable: true,                                                                                // 46
/******/ 				get: getter                                                                                // 47
/******/ 			});                                                                                // 48
/******/ 		}                                                                                // 49
/******/ 	};

Hi ! I have the same problem. Does anyone have an idea to correct or bypass, please ?

You're not going to be able to override the property on the actually important object, since it's configurable property is false. But you could do something like:
> cornerstone.getPixels
< function (element, x, y, width, height) {...
> cornerstone = {
    __proto__: cornerstone,
    getPixels: function override(x,y){
      console.log("meow");
    }
  }
> cornerstone.getPixels
< override (x, y) {...

Out of curiosity, why are you overriding getPixels?

@swederik is this another wontfix? I feel like it makes more sense to take in a PR that allows for API methods to be extended or for hooks to be added.


How to use this library?

Hi guys,
I would like to use this library to validate json schema from a response.
My response is a JSON-string, which will be stored in an attribute.
Is there an example of your library, how I can validate the schema?
I just would wish to see at least one small example.
Thanks

Please refer to the docs, existing online tutorials and StackOverflow for specific questions (with "json-schema" and/or "ajv" tag(s))


Demote JSDOM to development dependency.

Fixes #2190 #1491 #2180 #1986 #1250.
Code that previously assumed a global document or window now uses the related node’s ownerDocument or ownerDocument.defaultView as appropriate.
If no related node is available, the corresponding code will crash; however, the rest of D3 will work just fine. For example, you can’t use d3.select(string) unless a global document is available; it just doesn’t make sense. Use d3.select(node) instead, followed by selection.select(string).
Code that previously checked for a global on the window (e.g., XDomainRequest) now uses the global context (this) rather than the window.

Looks great!

Fix added for d3.select(window) bug.

Fixed in #2227 for 3.5.4.

Should´t this be considered a braking change? When using d3 in node the following used to work
var d3 = require('d3');

var svg = d3.select('body')
            .append('svg');

As jsdom is not included in d3 this will no longer work.  It was a very nice way to generate svg on the server.

It wasn’t explicitly specified that this was supported, and given the difficulties users were seeing installing D3 on Windows (and io.js), I wanted to make the change now rather than wait until the next major release.
You can fix your code as follows:
var d3 = require("d3"),
    jsdom = require("jsdom");

var document = jsdom.jsdom(""),
    svg = d3.select(document.body).append("svg");

Fair enough.  And thanks for your fix.
Kim

Thanks for this!
I noticed that the D3 wiki docs on Browser / Platform Support still said JSDOM was included with D3, so I updated them to reflect this change... If you don't like it though, feel free to change it.

Thank you!


Upgrading nhs.uk services to use the latest version of the frontend library

What
We need to make sure that all of our services are using the latest version of the NHS.UK frontend library. We also need to look at a better way of teams managing these version updates

[x] Audit our services to find out what versions of the frontend library they are using and how
[x] Update our services to use the latest NHS.UK frontend (mainly Wagtail)
[ ] Investigate a better way of maintaining NHS.UK frontend library versions

Auditing has begun here: https://confluence.service.nhs.uk/display/SMDS/NHS+website+(NHS.UK)+services+using+NHS.UK+frontend

@AdamChrimes @davidhunter08 Hi, I met with Paul and Mark. Paul's going to crack on with the work and then report back to us plus Bal next week.
I took away 3 things for us to look at in our team:

the feature card - which will appear in Wagtail and is in the frontend but not yet in the card component in the service manual. What were we going to do about this, @davidhunter08?
@AdamChrimes, would you be able to remove the full stops in cards in the frontend so that they match the examples in the service manual, please?
Also, after recent conversations with Michael C, I think we need a colon after the word Important in span so that screen readers pause before announcing a custom heading. If it just runs on without a pause, there is potential to confuse. Can we do that in the examples in the front end and the service manual, please?

Thanks @sarawilcox.
The feature card is a tricky one. The plan is to use a feature card for the 'Do and don't list' pattern - see https://github.com/nhsuk/nhsuk-service-manual/issues/695. So until we do that piece of work, I am not sure what guidance we could add to the service manual for a feature card? Happy to discuss it further.
I can look at the other 2 items, removing the full stops and adding a colon.

@AdamChrimes, do you know if the warning callout has already been updated in Wagtail, please? Or is it part of the work that's going on at the moment? (@mcheung-nhs was asking.)
Also, you know that we updated the frontend with a colon after the word "important" in the warning callout? Is that on the list of things to do in Wagtail too?
@lucyha, is there a way to have sight of changes we're making across:

frontend
service manual
Wagtail
@AdamChrimes @davidhunter08, please say if you have thoughts about this.

This was done, its now an going process everytime a version of the FE library is released. Hopefully handled by teams on NHS.UK


Pdoc3 documentation

Setup pdoc3 to generate documentation. Consider better naming of variables (e.g. obj)

Better to use Jekyll builtin to Github


Support for Three-qubit Operations + new Two-qubit Operations

This adds support for the three-qubit gate trait(s), two two-qubit operations as well as three three-qubit operations.
The new implemented Operations are

ControlledRotateX
ControlledRotateXY
ControlledControlledPauliZ
ControlledControlledPhaseShift
Toffoli

Questions:

ImplementedIn1point3 for new three-qubit operations as well?

EDIT: removed device support for three-qubit operations, it will be addressed in a later PR.

Should I update it to 1.3?


Issue links in release notes are broken

In the v3.2.0 release notes, the links to the issues resolved are broken.
https://github.com/gitbrent/PptxGenJS/releases/tag/v3.2.0
e.g.
https://github.com/gitbrent/PptxGenJS/issue/349

should be
https://github.com/gitbrent/PptxGenJS/issues/349

Note that you can also just write e.g. #349 and it will be auto-linked: #349

Thanks @pimlottc-gov !
I've been cut-n-pasting issue for many releases now and never noticed :(

Thanks for fixing the changelog, is it also possible to fix the links in the github release tags?   Those are still broken, e.g. https://github.com/gitbrent/PptxGenJS/releases/tag/v3.2.0

Release notes updated.


chore(main): release 1.1.5

:robot: I have created a release beep boop
1.1.5 (2024-01-28)
Bug Fixes

debug image tags environment variable (7b57341)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/jwbennet/project-base/releases/tag/v1.1.5 :sunflower:


Overlay overlaps sidebar when using navbar-fixed

There are two issues already created but they are poorly explained and it's hard to understand the issue.
When using a fixed navbar the grey overlay overlaps the sidebar menu making it impossible to use. I've made a jsfiddle showing the issue here.

Only with changing the z-index of the sidenav-overlay to 996 fixes the issue but I'm not sure it's the correct solution.
If it matters I'm on Chrome 65.0.3325.181 (Official Build) (64-bit) on macOS 10.13.4
The issues related to this problem are #5205 and #5750

Duplicate of #5205

Duplicate of #5750

Changing the z-index of the overlay to 996 is not a good solution. The nav is over it, but the whole nav, not only the sidenav.

Please read #3844


(BOLT-1425) Expose orchestrator-client_ruby settings in bolt conf

Previously the job-poll-{interval,timeout} settings for the ruby orchestrator client were only configurable in orchestrator.conf. This commit exposes these settings in bolt configuration. If these are set in bolt config, they will override the settings in orchestrator.conf which is the desired behaviour because only the ruby implementation of the orchestrator client should use these settings.

Leaving up my PE setup with bolt_shim installed etc with following master:
pcp:
  service-url: "https://afsv8pe6jzrdefl.delivery.puppetlabs.net:8143"
  cacert: /tmp/ca.pem
  task-environment: production

CLA signed by all contributors.


The search box of one item is not reset after unchecking its subscription

Storage Explorer Version: 1.19.1
Build Number: 20210423.2
Branch: hotfix/1.19.1
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release (1.18.1)
Steps to Reproduce

Sign in one Azure account -> Check one subscription.
Click 'Open Explorer' -> Right click one subscription -> Click 'Search From Here'.
Go to 'ACCOUNT MANAGEMENT' panel -> Uncheck the subscription -> Click 'Open Explorer'.
Check whether the search box is reset.

Expected Experience
The search box is reset.

Actual Experience
The search box is not reset.

Additional Context

This issue also reproduces for items under the subscription.
Display 'Nothing to display' after clicking 'X' button on the search box.
The 'EXPLORER' panel hangs.

Other odd behavior: if you add check subscriptions while searching or scoped they will show up in the tree, regardless if they are search results or not.

If uncheck subscriptions while searching or scoped, other existing checked subscriptions will show up in the tree, regardless if they are search results or not.

Hi @v-xianya, so I have finished work on this issue. Let me make clear the resolution for the various problems discussed here:

Unchecking a subscription after doing "search from here" on it leading to a "Nothing to display" message that can't be gotten rid of: after unchecking the subscription and then going back to the tree, the subscriptions is removed (expected), the path is still in the search box (expected), the quick access node shows up (going to make this expected), and if you click the "X" to cancel the scoping, the tree is restored/no longer scoped (fixed/expected)
Checking a subscription while the tree is scoped or searched will result in the subscription being added to the tree, regardless if it matches the scoped path/search query: we are going to treat this as expected behavior.
Unchecking a subscription/s while searching or scoped, will result in all checked subscriptions showing up in the tree, regardless if they are search results or not: we are going to treat this as expected behavior.

Here's the like criteria we're using for these to determine if these behaviors are "expected" or "bugs":

If the tree is not scoped/searched, then checking/unchecking subscriptions should result in them being added/removed.
If the tree is not scoped/searched, then checking/unchecking subscriptions may result in things which wouldn't normally show up in the scoping/search results to show up.
When clearing a scope path/search query, the tree should always return to normal.

Hi @MRayermannMSFT Thank you for the detailed clarification👍
Verified this issue on the latest build 20210524.7. Fixed.
Also, could you please help to confirm the below two things according the comments ?

For the 1 in discussion, you mentioned Unchecking a subscription after doing "search from here" on it leading to a "Nothing to display" message that can't be gotten rid of:  Actually, we do not see the message 'Nothing to display' on the build 20210524.7
For the 2 in criteria, is there a mistake in the if condition description? -------If the tree is not scoped/searched.

Actually, we do not see the message 'Nothing to display' on the build 20210524.7

Yes...? That is the first build with my fix for this. I'm not sure I understand your 1st thing.

For the 2 in criteria, is there a mistake in the if condition description? -------If the tree is not scoped/searched.

Oh yep, that's definitely a typo. Fixed!

@MRayermannMSFT thank you for the comments.
For the first question, I maybe misunderstand what's your meaning.
The current expected behavior is that the '"Nothing to display' message no longer displays, right?


[SPARK-25714] [BACKPORT-2.3] Fix Null Handling in the Optimizer rule BooleanSimplification

This PR is to backport https://github.com/apache/spark/pull/22702 to branch 2.3.

What changes were proposed in this pull request?
    val df1 = Seq(("abc", 1), (null, 3)).toDF("col1", "col2")
    df1.write.mode(SaveMode.Overwrite).parquet("/tmp/test1")
    val df2 = spark.read.parquet("/tmp/test1")
    df2.filter("col1 = 'abc' OR (col1 != 'abc' AND col2 == 3)").show()

Before the PR, it returns both rows. After the fix, it returns Row ("abc", 1)). This is to fix the bug in NULL handling in BooleanSimplification. This is a bug introduced in Spark 1.6 release.
How was this patch tested?
Added test cases

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3956/
Test PASSed.

Merged build finished. Test PASSed.

Test build #97355 has started for PR 22718 at commit 8303483.

Test build #97355 has finished for PR 22718 at commit 8303483.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97355/
Test FAILed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3964/
Test PASSed.

Test build #97365 has started for PR 22718 at commit 8303483.

Test build #97365 has finished for PR 22718 at commit 8303483.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97365/
Test PASSed.

cc @cloud-fan

thanks, merging to 2.3!


It's time for emoji.

I think it is time for emoji. We should double down on 🃏. I think 🚫 and 🚧 are specifically nice for jest-validate. We need to detect windows (see "Yarn") because it doesn't support emoji and add a --emoji flag (so it can be disabled through --no-emoji).
Examples:
✅ PASS
🚨 FAIL
🏃🏻♀ RUNS
In the summary on the bottom, if all tests pass, we could signal that with "🃏" – like you have a joker in your hand and we could use 🤡 if your tests didn't pass (indicating that your code is clowny).
Where do you think we could add emoji in a way that they aren't annoying yet provide good signal for what's going on?

I think Unicode symbols like ✓ or × is better:
Emoji is like a stickers. They good in separated line. But don’t look as part of text.

Good illustration of Emoji support problems:

Note that second emoji is in different style, than top one.

I think ✓ and × is clean enough.

I also wouldn't change pass/fail/runs, because I love how they display right now, same with ✓ and ×.
However I'm pretty good with subtle things like:
🃏 Determining test suites to run...
🃏 Ran all test suites
⚠ Jest Deprecation Warning
❌ Jest Validation Error

Idk about the joker, very much in favor of checkmark and X though.

I think emojis are great add could add a delightful touch, but I agree with @thymikee on the places that might make sense to add them... I'll try to hack a prototype to see how the experience feels and post a gif of it

I think it's overkill to add it instead of PASS etc. but I think showing the 🃏 on a successful run is cool :)

IMO, the joker card loses it's meaning and is hard to see in emoji size. Looks good at avatar size.

Why?

It's 2017.

@cpojer Made my day, thanks

It's current year, sure, but 🃏 and 🤡 aren't symbols known to mean "pass" and "fail".  Emojis are meant to represent a well-known concept as a symbol; if the concept is not well-known and you have to explain what they mean, it's just silly.


Added OTEL envvar for service name overriding in traces

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[X] Read the contribution guide
[X] Commands include options for Linux, MacOS, and Windows within codetabs
[X] New file and folder names are globally unique
[X] Page references use shortcodes instead of markdown or URL links
[X] Images use HTML style and have alternative text
[X] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Added a line to the list of tracing environment variables to indicate the key from which the OTEL service name can be specified instead of Dapr using the default ID from the runtime configuration.
Issue reference
Code PR: https://github.com/dapr/dapr/pull/7451
Issue: https://github.com/dapr/dapr/issues/5942 (though it's already closed for staleness, it was never remedied, so this will also solve Aspire tracing integration at https://github.com/dotnet/aspire/issues/1228

@hhunter-ms Just a ping to confirm that the associated code has been merged into 1.14

@holopin-bot @WhitWaldo


Update fido-authenticator

This patch updates fido-authenticator.  The new version contains many small fixes that improve compliance with the specification and also reduces the maximum credential ID length to improve compatibility with some applications.

The CI fails because it's missing https://github.com/Nitrokey/nitrokey-websmartcard-rust/pull/9

Already updated as part of https://github.com/Nitrokey/nitrokey-3-firmware/pull/335.  I’ve created a separate PR for the changelog entries: https://github.com/Nitrokey/nitrokey-3-firmware/pull/360


Bundle arguments to ChainSync.Client and internally refactor the core definition

While working on PR 808, I feel like the ChainSync client module needs some refactoring.

It takes way too many arguments, so I've introduced data types that bundle those.
It has way too many declarations in its where-clause, and with the new argument bundles, it's easier than ever before to float those out to their own top-level definitions.
Moreover, some lines of logic in the message handlers can also be floated out as their own separate logic. This makes the definitions of the higher-level steps easier to read---eg, each one fits on a single "page" now.
Finally: the whole module's styling is not internally consistent.

@dnadales @RenateEilers The last two commits have very ugly diffs.

The second-to-last commit moved a lot of code around, since it's floating out existing definitions and folding chunks to create some new definitions.

For the last commit, I recommend using a smart differ, eg
$ x=<the restyling commit hash>
$ >before.hs git show ${x}^:ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/MiniProtocol/ChainSync/Client.hs
$ >after.hs git show $x:ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/MiniProtocol/ChainSync/Client.hs
$ nix-shell -p difftastic --run 'difft before.hs after.hs'

For the second-to-last commit, I recommend having the two files open side-by-side in your editor, so you can manually cross-reference the new definitions versus their previous location in the preceding commit as you come across each of them in the commit's diff.
$ x=<the rearranging commit hash>
$ >before.hs git show ${x}^:ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/MiniProtocol/ChainSync/Client.hs
$ >after.hs git show $x:ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/MiniProtocol/ChainSync/Client.hs
$ emacs before.hs after.hs &
$ git show $x

If that's untenable, then I could split that commit into smaller pieces, one per new definition. But I'd rather avoid that work, if the editor-based method works for you. Please let me know 👍

I'm leaving it in Draft until we assess the performance concerns that @jasagredo raised about thunks/laziness/etc.

I pushed up commits that add a small "benchmark" exe that dumps a lot of measurements. I eyeballed them to convince myself that the time behavior hasn't changed in this PR.
Maybe that benchmark should be split into a different PR before merging this one.
I'm still working on convincing myself about space leaks.

No indication of a space leak in the tip of this PR; 10x 50x and 100x number of messages didn't change the max residency of the benchmark.
$ git diff --stat; git diff --stat --cached; git lg -1; cabal build ChainSync-client-bench; for i in 10 50 100; do echo $i; time cabal run ChainSync-client-bench -- $i $i +RTS -s 2>&1 1>/dev/null | grep -e
 'maximum residency' ; done
8cc6d46ee - (HEAD -> nfrisby/ChainSync-refactor, origin/nfrisby/ChainSync-refactor) Update changelogs for ChainSync.Client refactor (2 days ago) <Nicolas Frisby>
Up to date
10
         118,736 bytes maximum residency (10 sample(s))

real	0m9.557s
user	0m9.440s
sys	0m0.267s
50
         118,848 bytes maximum residency (43 sample(s))

real	0m41.005s
user	0m40.943s
sys	0m0.061s
100
         118,768 bytes maximum residency (51 sample(s))

real	1m23.457s
user	1m23.254s
sys	0m0.152s

I'd like to use NoThunks to test this, but it's currently blocked on https://github.com/input-output-hk/cardano-base/pull/449 and so on. (I could do without it, but it'd require a good deal of yak-shaving.)

Last step before merging will be me locally patching things to build with NoThunks using Joris' most recent CHaP release.

OK, thanks to Joris's help, I have run the benchmark with NoThunks-checking enabled and no thunks were found 🖐
I pushed my commit to nfrisby/ChainSync-refactor-NoThunks.
Using that commit, I:

built the benchmark without the flags
added the flags to my cabal.project
rebuilt the benchmark, confirming that the relevant packages were rebuilt
ran the benchmark (with arguments 1 1, since it's very slow now)

I saw no NoThunks messages, merely the normal benchmark output.

The last few force pushes were just be supplicating to the .cabal ahd .hs style checkers.

And this last force-push was because I forgot again about signing my commits.


Fixed #32970 -- Changed WhereNode.clone() to create a shallow copy of children.

~There is no ticket for this, and there may not be one. Please don't actively consider this :)~
~I'm just trying to find out what bits could break if something like this were attempted. All the tests pass locally, but that just means the failures might be in the more exotic ends of the suite. I'll close it down if it errors (highly likely) or open a ticket for further discussion if it doesn't.~
Ticket is 32970.
Testing the hypothesis I was mulling over in this comment: https://github.com/django/django/pull/14673#discussion_r673938568
Ran 14892 tests in 478.994s
OK (skipped=1193, expected failures=4)

@kezabelle Thanks :+1:

buildbot, test on oracle.


Update vulnerable dependencies

Purpose
Update testng, hsqldb, jline, apache commons-compress and jetty-server dependency because of reported vulnerability.
~Also convert maven-resolver to a module since there were some module path issues.~
Fixed module path isses in another way
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@keizer619 Can u check these changes?

I would like to fix all Trivy issues but unfortunately, the org.apache.james:apache-mime4j-core vulnerability is a transitive dependency of org.apache.ws.commons.axiom:axiom-api which currently doesn't have a newer version where this transitive dependency is updated. I also created an Issue in their Jira but let's see, when this will be addressed...
Jira issue in Axiom: https://issues.apache.org/jira/projects/AXIOM/issues/AXIOM-521
Trivy run: https://github.com/ballerina-platform/ballerina-lang/actions/runs/9783135210/job/27011022249

I would like to fix all Trivy issues but unfortunately, the org.apache.james:apache-mime4j-core vulnerability is a transitive dependency of org.apache.ws.commons.axiom:axiom-api which currently doesn't have a newer version where this transitive dependency is updated. I also created an Issue in their Jira but let's see, when this will be addressed...
Jira issue in Axiom: https://issues.apache.org/jira/projects/AXIOM/issues/AXIOM-521 Trivy run: https://github.com/ballerina-platform/ballerina-lang/actions/runs/9783135210/job/27011022249

Thanks for the contributions we just merged these.


✨ Add LibString methods pack/unpack one/two and directReturn

Description
Implements packOne, unpackOne, packTwo, unpackTwo, directReturn as requested by #105
Checklist

[x] Ran forge snapshot?
[x] Ran npm run lint?
[x] Ran forge test?

Thanks for the contribution.
I'll merge it when I'm back in civilization.


enhancement/case-participants-roles-and-permissions

Initial skeleton for case participants. This PR adds participants to the case model. Additionally, this adds the participants tab to the case edit sheet to remain consistent between incident and case front-end, and finally adds permissions to cases.

Looks good so far!

Have you thought about how we would organically add participants? I'm thinking that anyone that is either mentioned or messages the conversation thread should be added as a case participant.

@kevgliss and I chatted about this on VOIP. We will start with mentions within a Case thread being used to add people as a participant. Kevin to add this logic to https://github.com/Netflix/dispatch/pull/2913 and rebase off this PR (https://github.com/Netflix/dispatch/pull/2800).

@kevgliss Are we at a stable point w/ the front-end fixes to merge this?


Removed instructions for manual image creation

Docker has revolutionized container management by adding automation. The documentation seems to advocate that manually creating an image is the first step into Docker. I could not disagree more. New users should be taught to embrace automation and understand the importance of standardization and repeatability. Therefore, I propose to remove the whole section.

Looks much cleaner now. 😀

(I have to admit that I used docker commit etc. in my Windows workshops, but this is an guided tour and not a self pace tutorial so I can explain the audience that we will do this only once and quickly switch to a source coded description in a Dockerfile. It is good to understand how each layer works and the impact some commands have in respect of image layer sizes. )
For this doc page I‘m +1 to only show the correct way.

Ping @PatrickLang @taylorb-microsoft for their assessment.  Seems reasonable to me.

Docker's page only shows docker build not docker commit
https://docs.docker.com/get-started/part2/
LGTM


Add json logging format and a couple examples.

[ ] More through  testing
[ ] Pull user ID from token
[ ] Add logging lib to setup.cfg and requirements.txt

Thanks Paul!!
(Added some todos from slack to the description)


hello world via aidgent

this is the ultimate test for you, @aidgent
your task is to add "hello, world" to the README.md, at the bottom.

Aidgent reporting for duty! Thank you for giving me the opportunity to solve this issue. I'm getting to work on it now and I will reply soon with my solution.

Aidgent reporting for duty! Thank you for giving me the opportunity to solve this issue. I'm getting to work on it now and I will reply soon with my solution.

I did my best to solve the issue!
You can see the changes I made https://github.com/aidgent/MineTuning/commit/2d4d8260f7994f0da28b20039bd39b86408.
Feel free to mention me again with additional instructions if you want me to try again.
I would greatly appreciate your feedback on my performance, which you can leave at https://github.com/aidgent/aidgent/issues/.

I did my best to solve the issue!
You can see the changes I made https://github.com/aidgent/MineTuning/commit/c6a8a6c4d49769b3ec00fae44d8adf08f66.
Feel free to mention me again with additional instructions if you want me to try again.
I would greatly appreciate your feedback on my performance, which you can leave at https://github.com/aidgent/aidgent/issues/.

I did my best to solve the issue!
You can see the changes I made https://github.com/aidgent/MineTuning/commit/26f6c96fac54e3c80768f887b91e63c063b.
Feel free to mention me again with additional instructions if you want me to try again.
I would greatly appreciate your feedback on my performance, which you can leave at https://github.com/aidgent/aidgent/issues/.


chore(package): update react packages to 15.4.2

Closes #45 #46 #47 #59 #60 #61

Current coverage is 91.89% (diff: 100%)

Merging #62 into master will not change coverage

@@             master        #62   diff @@
==========================================
  Files             1          1
  Lines            37         37
  Methods           9          9
  Messages          0          0
  Branches          8          8
==========================================
  Hits             34         34
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update d7ed0b3...7bdd779


feature request: specify testfile

It would be great if goss could specify a testfile- in my usage, I have many different flavours to choose from, I dont want to have to manage renaming the testfile I want to select as goss.yaml, it would be great if I could just do goss validate < some-file or goss validate --testfile foo.yaml
Thanks for the great tool btw 👍

You can already do this with option -g: https://github.com/aelsabbahy/goss/blob/master/docs/manual.md#-g-gossfile


Protocol and support for other devices

Gadgetbridge supports a number of devices and implements two protocols, a V1 for older devices (e.g. the WH-1000XM3) and a V2 (e.g. WF-1000XM4). Some pointers:

https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/app/src/main/java/nodomain/freeyourgadget/gadgetbridge/devices/sony/headphones/coordinators
https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/app/src/main/java/nodomain/freeyourgadget/gadgetbridge/service/devices/sony/headphones/protocol/impl
I'm considering spending some time on this to add support for V1 devices. Do you have any thoughts or on integrating this?

Hello, I no longer own my WF-1000XM4 so i will probably no longer work on this. I might help out on some point if i feel like it or if a buy a new sony headset in the future.
If you want to take over the project please feel free to do so.


[Feature] Settings would be nice

Specifically the ability to disable pathfinding, as it can accidentally reveal information like extra paths to somewhere the PCs wouldn't be aware of

Done! Whilst I can't disable pathfinding, I've added a lot of options and one of them includes the ability to remove the lines that would be rendered.


Diff View can be trimmed

Currently diff view is strictly showing all columns; good for most cases, tho if there are large no of cols its difficult to spot differences
A possible view option to hide columns that didn't change; combining diff info based on rows smartly pick which cols to show in diff report.

You can hide each column individually but you also want a hide unchanged columns option?

And this is a UI specific issue so these go under dolthub-issues. This repo is for doltlab specific bugs.