Fix bug to make --clear-output-folder work

To fix: https://github.com/Azure/autorest.python/issues/1409
Root cause:
write_file can't make sure to flush the buffer to disk before black read and format all files from disk:
https://github.com/Azure/autorest.python/blob/ba0cb0eb6dd76f5004042b187d769cc530fe34cb/packages/autorest.python/autorest/jsonrpc/stdstream.py#L46-L52
https://github.com/Azure/autorest.python/blob/ba0cb0eb6dd76f5004042b187d769cc530fe34cb/packages/autorest.python/autorest/black/__init__.py#L31-L39

What's the reason that many samples/tests files get updated? Is it because previous black not applied to them due to the bug?

What's the reason that many samples/tests files get updated? Is it because previously black did not apply to them due to the bug?

Yeah. And with the fix, multiapi/multiclient can also enable black which is not permitted before.

close for https://github.com/Azure/autorest.python/pull/1434


In Scan/Item mode, while navigating to "4.8 coffee cups" text from "0.25 gal(UK)" text, Narrator focus navigates to hidden elements

Repro Steps

Launch "Calculator" app.
Launch Narrator.
Navigate to "Open Navigation" button and activate it.
Navigate to "Volume" menu item and activate it.
Volume converter window will open.
Select any value for "Converts from" combo box say "2 Pints(UK)".
Select any "Converts to" combo box say "Cubic feet".
Navigate to "4.8 coffee cups" text in the Scan/Item mode.
Observe the issue.

Note: Same issue is repro in length menu item. This issue is not repro in version 10.1902.42.0
Actual Result
In Scan/Item mode, while navigating to "4.8 coffee cups" text from "0.25 gal(UK)" text narrator focus navigates to hidden elements.
Expected Result
In Scan/Item mode, while navigating to "4.8 coffee cups" text from "0.25 gal(UK)" text narrator focus should not navigate to hidden elements.
Test Environment

OS Version: Windows 10 (Build 18362.53)
App Name: Calculator
App Version: 10.1903.21.0

This is your friendly Microsoft Issue Bot. I created this issue automatically as requested by a team member.

I'd like to fix this bug.

@greedyAI All yours, thanks! Let us know if you need any help.


引入失败了

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /node_modules/inquirer-radio-prompt/package.json

maybe esm modal only reason

Hi, sorry for the delayed response. I think you're right and it's because it's ESM only. I created an ESM test project and it worked fine. But, when I created a CJS test project I got the same error you did.
If there's interest, I can look into making the package a dual ESM & CJS export though.

So, this issue piqued my interest in dual export packages. I researched it a bit and figured out a good implementation and just published v1.3.0 which exports both ESM and CJS.
I'm going to close out this issue. But, if you have any further input or questions please feel free to comment.


Appointment creation interferes with native navigation in full calendar

Describe the bug
The appointment event is triggered although you want to use a native navigation function of the fullcalendar.
To Reproduce

Opening the calendar in Month view and
navigating to desired month with PREV / NEXT
Then clicking on the "intended" Day-Link
This opens the Appointment Creation Event (Popup)

Expected behavior
I use this to navigate quickly into a desired month and date. Clicking on the Day-Link should navigate on the next loaded view (eg. 3 Days or 1 Day) and use this as working context.
MacOS happens immediately on click; iPadOS with holding a delay (side note: apple pencil does not work like a click, uses same delay)
This should only happen, when selecting the Day-Link - otherwise the current behavior is good.
Screenshots
If applicable, add screenshots to help explain your problem.
Console Errors
no errors, just ignoring a click event for navigation.
Device info (please complete the following information):

Mac OS Obsidian 1.1.6
iPad OS Obsidian 1.4.2

Additional context
Add any other context about the problem here.

This is a duplicate of #74.


Create New Project defaults to Python

Whenever i select the Azure Functions: Create New Project option in VS Code, it always defaults to Python - i don't get asked what language to use. Then when i select Create New Function it's in Python.
I've tried setting "azureFunctions.projectLanguage": "JavaScript" in .vscode/settings.json and although the boilerplate is created for a JS function, the FUNCTIONS_WORKER_RUNTIME value in local.settings.json is still Python, and it creates a requirements.txt not package.json file, and the .gitignore is for Python not JS.

Hi @mnbf9rca
Have you started in a brand new/empty folder when you tried creating a new project?
Is it possible that you have set azureFunctions.projectLanguage as a User or Global setting? If this is the case, I believe that it is being used preferentially over the workspace setting.
Could you please check your user settings for me?

Yes, this is the problem. I don't recall setting it though if i did it was years ago! It would probably help to include a reference somewhere in the startup tutorials? I tried googling but all i could find was this question which doesnt say how to fix it (despite being marked as answered)!


Sema: Properly handle inference for abstract fixed type witnesses

This fixes inference for some fixed type witness chains - SR-10831, for example:
protocol P {
  associatedtype A
  associatedtype B
}
protocol Q: P where A == G<B> {}
protocol R: Q where B == Int {}

struct Foo: R {} // OK

And adds inference of fixed type witnesses containing Self - SR-11671:
protocol P {
  associatedtype A
}
protocol Q: P where A == Self {}

struct Foo: Q {} // OK, Self == Foo

@slavapestov

@jckarter Can you take a quick look?

@slavapestov bumping this up in case you have some bandwidth

Can one of the admins verify this patch?

After almost a year I can tell the approach here is flawed and quite narrow. Closing to revisit this once we settle on the implementation details of a new conformance checker.


IOS nil string parameter.

Before posting I tried to follow the git instructions 3 times.
Details : RN 0.32,
I didn't add anything to xcode/ios/android environment (the only thing I did is put the video file in my root directory, and 'react-native link'  ( I checked and for android everything needed was added to MainApplication.java)
I tried this way When file smoke.mp4 is in the root:
<Video
                source={{uri: "smoke"}}
                rate={1.0}
                volume={1.0}
                muted={false}
                paused={false}
                resizeMode="stretch"
                repeat={true}
                playInBackground={false}
                playWhenInactive={false}
                style={styles.backgroundVideo}
            />

It caused this in xcode :

2016-09-02 19:16:51.574 puffClient[35456:7558213] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[NSURL initFileURLWithPath:]: nil string parameter'
*** First throw call stack:

Then I tried the following, I've read issues and saw it doesn't work for ios, but the documentation stated it might so I tried :
<Video
               ##  source={require('../../../smoke.mp4' )}
                rate={1.0}
                volume={1.0}
                muted={false}
                paused={false}
                resizeMode="stretch"
                repeat={true}
                playInBackground={false}
                playWhenInactive={false}
                style={styles.backgroundVideo}
            />

It doesn't give me any compilation errors, or xcode errors at all, but it does Black screen to the app.
Thanks for you attention, have a great day.

+1

I was having a similar issue, and after seeing @gviligvili's questions, I tried using the source={require('../foo.mp4')} syntax as opposed to the source={{uri: "foo"}} syntax.
It didn't work for me at first, and I had a similar result where the error message would go away but all I would see was a black screen, however after a number of reloads, it suddenly started working.  I reloaded again after making some small changes, and once I did it went back to the black screen again.  I then reverted the changes expecting that the video would start playing again, however it did not.  After a long while of trying numerous things to get it to work again, it suddenly did when I changed where the file lived in the directory structure. Then, after another reload with no changes this time, I was back to the black screen.
I am completely lost when it comes to Objective C so I wish I could be of more help, but it seems like there may be some timing discrepancy between when the file is loaded and when the component gets instantiated.

I also have following issue. Running react-native log-ios gives me this:
Sep  3 15:35:22 MBP-Rafal assertiond[3949] <Error>: assertion failed: 15G31 13E230: assertiond + 15801 [3C808658-78EC-3950-A264-79A64E0E463B]: 0x1
Sep  3 15:35:22 MBP-Rafal Unknown[3949] <Error>:
Sep  3 15:35:22 MBP-Rafal FameStats[4002] <Error>: nw_interface_create_with_index refusing to create an interface with index<PHONE_NUMBER> too high (>=2147483647)
--- last message repeated 1 time ---
Sep  3 15:35:28 MBP-Rafal SpringBoard[3945] <Warning>: Weekly asset update check did fire (force=NO)
Sep  3 15:35:28 MBP-Rafal SpringBoard[3945] <Warning>: Beginning check for asset updates (force: 0
Sep  3 15:35:28 MBP-Rafal SpringBoard[3945] <Warning>: Did not complete check for asset updates (force: 0, isVoiceOverRunning: 0
Sep  3 15:35:56 MBP-Rafal mstreamd[3935] <Notice>: (Note ) PS: Media stream daemon stopping.
Sep  3 15:35:56 MBP-Rafal mstreamd[3935] <Notice>: (Note ) AS: <MSIOSAlbumSharingDaemon: 0x7ff4a840e320>: Shared Streams daemon has shut down.
Sep  3 15:35:56 MBP-Rafal mstreamd[3935] <Notice>: (Warn ) mstreamd: mstreamd shutting down.

@RafalWilinski That issue seems to be unrelated to this issue. Please create a new issue to track the problem you are seeing.

I m facing this issue with React Native 0.32 . I tried example app to run . its give me same result

+1

My MacBook is at the Apple Store for repair for the past few days. As soon as I get it back tonight I'll try and replicate/fix this issue

@gviligvili
I get the same issue on RN 0.32
when using
source={require('../../../smoke.mp4' )}
the black screen should go away if you update to RN 0.33, as per this repo's ReadMe
I'm going to upgrade to RN 0.33 and see if that fixes it.
If I need to revert back to RN 0.32 , @mattapperson have you had any luck replicating/fixing this issue?

Updated to 33, updated Xcode,  and still, same results.

I was seeing the same issue (using source={{uri: 'metal_drop', type: 'mp3'}}), gave my computer a hard restart, and all is well.

... also, I'm having to add my assets to "Copy Bundle Resources" in XCode under Targets > My App > Build Phases.

Should this be in the ReadMe for newcomers?
$ npm ls react-native react-native-video
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

I was also seeing this issue on iOS until I added the type, like so:
source={{ uri: 'fileName', type: 'mp4' }}
Now it works.

FWIW I was having a similar issue. I was looking to store the video file inside the native asset system, instead of using the React Native asset loader, to prevent the file being sent over the bridge whenever it needed to play.
For posterity, this is what I did to get it all working.
Files

Make sure your video filename begins with a letter (Android will barf on anything else) and has the correct extension (e.g. .mp4).
Put your video files in an assets/videos/ folder in the root of your filesystem. Keep them all in the same folder, i.e no subdirectories.

For the rest of the below, I'll assume we have a video file example.mp4 in this folder.
iOS

Open the assets/videos folder in Finder
Open the .xcodeproj file in Xcode, click on the Project navigator icon to show the project files in the left hand pane
Select the video files you want in Finder, drag them over to Xcode, inside the 'Resources' folder
In the pop-up box, check the Copy items if needed checkbox, and check the first two targets (YourAppName and YourAppNameTests)

Note that this will create a reference to the actual files, which will remain in assets/videos/.
Android

Create the folder android/app/src/main/res/raw (if it doesn't already exist)
Copy your video files into this folder (keep them in the root of raw, i.e. no subfolders, otherwise Android won't find them at runtime)

React

Render your video using the syntax <Video source={{ uri: 'example', type: 'mp4' }} /> - note that the uri is the filename minus the extension, and the type is the extension.

And hey presto, hopefully your video will load with no sending over the bridge!

what can we do for remote urls??

@Shahrukh0396
You should check the url. It should not have any spaces.
in my case a there were a couple spaces in the URL from the API which caused this issue in IOS only not on android.
I hope this helps you.


[icons] Update script to use latest json file

[x] I have followed (at least) the PR section of the contributing guide.

The data referenced in the download script is outdated and no longer maintained. This PR updates the script with the latest url path and data structure.
Current: https://material.io/resources/icons/static/data.json
Latest: https://fonts.google.com/metadata/icons
As referenced at https://github.com/mui-org/material-ui/issues/12251#issuecomment-526876455
Edit by @oliviertassinari:
Closes #12251

Also, any reason (other than historical) that builder can't go in scripts?

Not I'm aware of, we could change it. What's the issue with the current setup?

We have a scripts directory, but not all the scripts are in it. 🤷🏽♂
(The package used to be a generic icon builder, so it being in the root dir is a hold-over from that.)
The first comment is the more important one.

@mbrookes Right now - yarn:icons is nuking the directory before writing to it.
An easy fix for the script would be to only rimraf files we are replacing.
I think the changes I've made should do the trick.

@mbrookes Oh, I understand what's the issue is now. I would have needed a pristine development environment to see it in the first place. It seems that we miss the following icons:
-export { default as AddLocation } from './AddLocation';
-export { default as AddLocationOutlined } from './AddLocationOutlined';
-export { default as AddLocationRounded } from './AddLocationRounded';
-export { default as AddLocationSharp } from './AddLocationSharp';
-export { default as AddLocationTwoTone } from './AddLocationTwoTone';

-export { default as AlternateEmail } from './AlternateEmail';
-export { default as AlternateEmailOutlined } from './AlternateEmailOutlined';
-export { default as AlternateEmailRounded } from './AlternateEmailRounded';
-export { default as AlternateEmailSharp } from './AlternateEmailSharp';
-export { default as AlternateEmailTwoTone } from './AlternateEmailTwoTone';

-export { default as Battery20 } from './Battery20';
-export { default as Battery20Outlined } from './Battery20Outlined';
-export { default as Battery20Rounded } from './Battery20Rounded';
-export { default as Battery20Sharp } from './Battery20Sharp';
-export { default as Battery20TwoTone } from './Battery20TwoTone';

-export { default as Battery30 } from './Battery30';
-export { default as Battery30Outlined } from './Battery30Outlined';
-export { default as Battery30Rounded } from './Battery30Rounded';
-export { default as Battery30Sharp } from './Battery30Sharp';
-export { default as Battery30TwoTone } from './Battery30TwoTone';

-export { default as Battery50 } from './Battery50';
-export { default as Battery50Outlined } from './Battery50Outlined';
-export { default as Battery50Rounded } from './Battery50Rounded';
-export { default as Battery50Sharp } from './Battery50Sharp';
-export { default as Battery50TwoTone } from './Battery50TwoTone';

-export { default as Battery60 } from './Battery60';
-export { default as Battery60Outlined } from './Battery60Outlined';
-export { default as Battery60Rounded } from './Battery60Rounded';
-export { default as Battery60Sharp } from './Battery60Sharp';
-export { default as Battery60TwoTone } from './Battery60TwoTone';
-export { default as Battery80 } from './Battery80';

-export { default as Battery80Outlined } from './Battery80Outlined';
-export { default as Battery80Rounded } from './Battery80Rounded';
-export { default as Battery80Sharp } from './Battery80Sharp';
-export { default as Battery80TwoTone } from './Battery80TwoTone';

-export { default as Battery90 } from './Battery90';
-export { default as Battery90Outlined } from './Battery90Outlined';
-export { default as Battery90Rounded } from './Battery90Rounded';
-export { default as Battery90Sharp } from './Battery90Sharp';
-export { default as Battery90TwoTone } from './Battery90TwoTone';

-export { default as BatteryCharging20 } from './BatteryCharging20';
-export { default as BatteryCharging20Outlined } from './BatteryCharging20Outlined';
-export { default as BatteryCharging20Rounded } from './BatteryCharging20Rounded';
-export { default as BatteryCharging20Sharp } from './BatteryCharging20Sharp';
-export { default as BatteryCharging20TwoTone } from './BatteryCharging20TwoTone';

-export { default as BatteryCharging30 } from './BatteryCharging30';
-export { default as BatteryCharging30Outlined } from './BatteryCharging30Outlined';
-export { default as BatteryCharging30Rounded } from './BatteryCharging30Rounded';
-export { default as BatteryCharging30Sharp } from './BatteryCharging30Sharp';
-export { default as BatteryCharging30TwoTone } from './BatteryCharging30TwoTone';

-export { default as BatteryCharging50 } from './BatteryCharging50';
-export { default as BatteryCharging50Outlined } from './BatteryCharging50Outlined';
-export { default as BatteryCharging50Rounded } from './BatteryCharging50Rounded';
-export { default as BatteryCharging50Sharp } from './BatteryCharging50Sharp';
-export { default as BatteryCharging50TwoTone } from './BatteryCharging50TwoTone';

-export { default as BatteryCharging60 } from './BatteryCharging60';
-export { default as BatteryCharging60Outlined } from './BatteryCharging60Outlined';
-export { default as BatteryCharging60Rounded } from './BatteryCharging60Rounded';
-export { default as BatteryCharging60Sharp } from './BatteryCharging60Sharp';
-export { default as BatteryCharging60TwoTone } from './BatteryCharging60TwoTone';

-export { default as BatteryCharging80 } from './BatteryCharging80';
-export { default as BatteryCharging80Outlined } from './BatteryCharging80Outlined';
-export { default as BatteryCharging80Rounded } from './BatteryCharging80Rounded';
-export { default as BatteryCharging80Sharp } from './BatteryCharging80Sharp';
-export { default as BatteryCharging80TwoTone } from './BatteryCharging80TwoTone';

-export { default as BatteryCharging90 } from './BatteryCharging90';
-export { default as BatteryCharging90Outlined } from './BatteryCharging90Outlined';
-export { default as BatteryCharging90Rounded } from './BatteryCharging90Rounded';
-export { default as BatteryCharging90Sharp } from './BatteryCharging90Sharp';
-export { default as BatteryCharging90TwoTone } from './BatteryCharging90TwoTone';

-export { default as BorderColor } from './BorderColor';
-export { default as BorderColorOutlined } from './BorderColorOutlined';
-export { default as BorderColorRounded } from './BorderColorRounded';
-export { default as BorderColorSharp } from './BorderColorSharp';
-export { default as BorderColorTwoTone } from './BorderColorTwoTone';

-export { default as CastForEducation } from './CastForEducation';
-export { default as CastForEducationOutlined } from './CastForEducationOutlined';
-export { default as CastForEducationRounded } from './CastForEducationRounded';
-export { default as CastForEducationSharp } from './CastForEducationSharp';
-export { default as CastForEducationTwoTone } from './CastForEducationTwoTone';

-export { default as CellWifi } from './CellWifi';
-export { default as CellWifiOutlined } from './CellWifiOutlined';
-export { default as CellWifiRounded } from './CellWifiRounded';
-export { default as CellWifiSharp } from './CellWifiSharp';
-export { default as CellWifiTwoTone } from './CellWifiTwoTone';

-export { default as Domain } from './Domain';
-export { default as DomainOutlined } from './DomainOutlined';
-export { default as DomainRounded } from './DomainRounded';
-export { default as DomainSharp } from './DomainSharp';
-export { default as DomainTwoTone } from './DomainTwoTone';

-export { default as EditLocation } from './EditLocation';
-export { default as EditLocationOutlined } from './EditLocationOutlined';
-export { default as EditLocationRounded } from './EditLocationRounded';
-export { default as EditLocationSharp } from './EditLocationSharp';
-export { default as EditLocationTwoTone } from './EditLocationTwoTone';

-export { default as FormatColorFill } from './FormatColorFill';
-export { default as FormatColorFillOutlined } from './FormatColorFillOutlined';
-export { default as FormatColorFillRounded } from './FormatColorFillRounded';
-export { default as FormatColorFillSharp } from './FormatColorFillSharp';
-export { default as FormatColorFillTwoTone } from './FormatColorFillTwoTone';

-export { default as FormatColorText } from './FormatColorText';
-export { default as FormatColorTextOutlined } from './FormatColorTextOutlined';
-export { default as FormatColorTextRounded } from './FormatColorTextRounded';
-export { default as FormatColorTextSharp } from './FormatColorTextSharp';
-export { default as FormatColorTextTwoTone } from './FormatColorTextTwoTone';

-export { default as LocationOff } from './LocationOff';
-export { default as LocationOffOutlined } from './LocationOffOutlined';
-export { default as LocationOffRounded } from './LocationOffRounded';
-export { default as LocationOffSharp } from './LocationOffSharp';
-export { default as LocationOffTwoTone } from './LocationOffTwoTone';

-export { default as LocationOn } from './LocationOn';
-export { default as LocationOnOutlined } from './LocationOnOutlined';
-export { default as LocationOnRounded } from './LocationOnRounded';
-export { default as LocationOnSharp } from './LocationOnSharp';
-export { default as LocationOnTwoTone } from './LocationOnTwoTone';

-export { default as NetworkCell } from './NetworkCell';
-export { default as NetworkCellOutlined } from './NetworkCellOutlined';
-export { default as NetworkCellRounded } from './NetworkCellRounded';
-export { default as NetworkCellSharp } from './NetworkCellSharp';
-export { default as NetworkCellTwoTone } from './NetworkCellTwoTone';

-export { default as NetworkWifi } from './NetworkWifi';
-export { default as NetworkWifiOutlined } from './NetworkWifiOutlined';
-export { default as NetworkWifiRounded } from './NetworkWifiRounded';
-export { default as NetworkWifiSharp } from './NetworkWifiSharp';
-export { default as NetworkWifiTwoTone } from './NetworkWifiTwoTone';

-export { default as NotListedLocation } from './NotListedLocation';
-export { default as NotListedLocationOutlined } from './NotListedLocationOutlined';
-export { default as NotListedLocationRounded } from './NotListedLocationRounded';
-export { default as NotListedLocationSharp } from './NotListedLocationSharp';
-export { default as NotListedLocationTwoTone } from './NotListedLocationTwoTone';

-export { default as PersonPinCircle } from './PersonPinCircle';
-export { default as PersonPinCircleOutlined } from './PersonPinCircleOutlined';
-export { default as PersonPinCircleRounded } from './PersonPinCircleRounded';
-export { default as PersonPinCircleSharp } from './PersonPinCircleSharp';
-export { default as PersonPinCircleTwoTone } from './PersonPinCircleTwoTone';

-export { default as PinDrop } from './PinDrop';
-export { default as PinDropOutlined } from './PinDropOutlined';
-export { default as PinDropRounded } from './PinDropRounded';
-export { default as PinDropSharp } from './PinDropSharp';
-export { default as PinDropTwoTone } from './PinDropTwoTone';

// LocationOn is better
-export { default as Place } from './Place';
-export { default as PlaceOutlined } from './PlaceOutlined';
-export { default as PlaceRounded } from './PlaceRounded';
-export { default as PlaceSharp } from './PlaceSharp';
-export { default as PlaceTwoTone } from './PlaceTwoTone';

// PlayCircleFilled is better
-export { default as PlayCircleFilledWhite } from './PlayCircleFilledWhite';
-export { default as PlayCircleFilledWhiteOutlined } from './PlayCircleFilledWhiteOutlined';
-export { default as PlayCircleFilledWhiteRounded } from './PlayCircleFilledWhiteRounded';
-export { default as PlayCircleFilledWhiteSharp } from './PlayCircleFilledWhiteSharp';
-export { default as PlayCircleFilledWhiteTwoTone } from './PlayCircleFilledWhiteTwoTone';

-export { default as Settings } from './Settings';
-export { default as SettingsOutlined } from './SettingsOutlined';
-export { default as SettingsRounded } from './SettingsRounded';
-export { default as SettingsSharp } from './SettingsSharp';
-export { default as SettingsTwoTone } from './SettingsTwoTone';

// Useless
-export { default as SignalCellular0Bar } from './SignalCellular0Bar';
-export { default as SignalCellular0BarOutlined } from './SignalCellular0BarOutlined';
-export { default as SignalCellular0BarRounded } from './SignalCellular0BarRounded';
-export { default as SignalCellular0BarSharp } from './SignalCellular0BarSharp';
-export { default as SignalCellular0BarTwoTone } from './SignalCellular0BarTwoTone';

// Useless
-export { default as SignalCellular1Bar } from './SignalCellular1Bar';
-export { default as SignalCellular1BarOutlined } from './SignalCellular1BarOutlined';
-export { default as SignalCellular1BarRounded } from './SignalCellular1BarRounded';
-export { default as SignalCellular1BarSharp } from './SignalCellular1BarSharp';
-export { default as SignalCellular1BarTwoTone } from './SignalCellular1BarTwoTone';

// Useless
-export { default as SignalCellular2Bar } from './SignalCellular2Bar';
-export { default as SignalCellular2BarOutlined } from './SignalCellular2BarOutlined';
-export { default as SignalCellular2BarRounded } from './SignalCellular2BarRounded';
-export { default as SignalCellular2BarSharp } from './SignalCellular2BarSharp';
-export { default as SignalCellular2BarTwoTone } from './SignalCellular2BarTwoTone';

// Useless
-export { default as SignalCellular3Bar } from './SignalCellular3Bar';
-export { default as SignalCellular3BarOutlined } from './SignalCellular3BarOutlined';
-export { default as SignalCellular3BarRounded } from './SignalCellular3BarRounded';
-export { default as SignalCellular3BarSharp } from './SignalCellular3BarSharp';
-export { default as SignalCellular3BarTwoTone } from './SignalCellular3BarTwoTone';

// Useless
-export { default as SignalCellularConnectedNoInternet0Bar } from './SignalCellularConnectedNoInternet0Bar';
-export { default as SignalCellularConnectedNoInternet0BarOutlined } from './SignalCellularConnectedNoInternet0BarOutlined';
-export { default as SignalCellularConnectedNoInternet0BarRounded } from './SignalCellularConnectedNoInternet0BarRounded';
-export { default as SignalCellularConnectedNoInternet0BarSharp } from './SignalCellularConnectedNoInternet0BarSharp';
-export { default as SignalCellularConnectedNoInternet0BarTwoTone } from './SignalCellularConnectedNoInternet0BarTwoTone';

// Useless
-export { default as SignalCellularConnectedNoInternet1Bar } from './SignalCellularConnectedNoInternet1Bar';
-export { default as SignalCellularConnectedNoInternet1BarOutlined } from './SignalCellularConnectedNoInternet1BarOutlined';
-export { default as SignalCellularConnectedNoInternet1BarRounded } from './SignalCellularConnectedNoInternet1BarRounded';
-export { default as SignalCellularConnectedNoInternet1BarSharp } from './SignalCellularConnectedNoInternet1BarSharp';
-export { default as SignalCellularConnectedNoInternet1BarTwoTone } from './SignalCellularConnectedNoInternet1BarTwoTone';

// Useless
-export { default as SignalCellularConnectedNoInternet2Bar } from './SignalCellularConnectedNoInternet2Bar';
-export { default as SignalCellularConnectedNoInternet2BarOutlined } from './SignalCellularConnectedNoInternet2BarOutlined';
-export { default as SignalCellularConnectedNoInternet2BarRounded } from './SignalCellularConnectedNoInternet2BarRounded';
-export { default as SignalCellularConnectedNoInternet2BarSharp } from './SignalCellularConnectedNoInternet2BarSharp';
-export { default as SignalCellularConnectedNoInternet2BarTwoTone } from './SignalCellularConnectedNoInternet2BarTwoTone';

// Useless
-export { default as SignalCellularConnectedNoInternet3Bar } from './SignalCellularConnectedNoInternet3Bar';
-export { default as SignalCellularConnectedNoInternet3BarOutlined } from './SignalCellularConnectedNoInternet3BarOutlined';
-export { default as SignalCellularConnectedNoInternet3BarRounded } from './SignalCellularConnectedNoInternet3BarRounded';
-export { default as SignalCellularConnectedNoInternet3BarSharp } from './SignalCellularConnectedNoInternet3BarSharp';
-export { default as SignalCellularConnectedNoInternet3BarTwoTone } from './SignalCellularConnectedNoInternet3BarTwoTone';

// Useless
-export { default as SignalWifi0Bar } from './SignalWifi0Bar';
-export { default as SignalWifi0BarOutlined } from './SignalWifi0BarOutlined';
-export { default as SignalWifi0BarRounded } from './SignalWifi0BarRounded';
-export { default as SignalWifi0BarSharp } from './SignalWifi0BarSharp';
-export { default as SignalWifi0BarTwoTone } from './SignalWifi0BarTwoTone';

// Useless
-export { default as SignalWifi1BarLock } from './SignalWifi1BarLock';
-export { default as SignalWifi1BarLockOutlined } from './SignalWifi1BarLockOutlined';
-export { default as SignalWifi1BarLockRounded } from './SignalWifi1BarLockRounded';
-export { default as SignalWifi1BarLockSharp } from './SignalWifi1BarLockSharp';
-export { default as SignalWifi1BarLockTwoTone } from './SignalWifi1BarLockTwoTone';

// Useless
-export { default as SignalWifi1Bar } from './SignalWifi1Bar';
-export { default as SignalWifi1BarOutlined } from './SignalWifi1BarOutlined';
-export { default as SignalWifi1BarRounded } from './SignalWifi1BarRounded';
-export { default as SignalWifi1BarSharp } from './SignalWifi1BarSharp';
-export { default as SignalWifi1BarTwoTone } from './SignalWifi1BarTwoTone';

// Useless
-export { default as SignalWifi2Bar } from './SignalWifi2Bar';
-export { default as SignalWifi2BarLockOutlined } from './SignalWifi2BarLockOutlined';
-export { default as SignalWifi2BarLockRounded } from './SignalWifi2BarLockRounded';
-export { default as SignalWifi2BarLockSharp } from './SignalWifi2BarLockSharp';
-export { default as SignalWifi2BarLockTwoTone } from './SignalWifi2BarLockTwoTone';

// Useless
-export { default as SignalWifi2BarLock } from './SignalWifi2BarLock';
-export { default as SignalWifi2BarOutlined } from './SignalWifi2BarOutlined';
-export { default as SignalWifi2BarRounded } from './SignalWifi2BarRounded';
-export { default as SignalWifi2BarSharp } from './SignalWifi2BarSharp';
-export { default as SignalWifi2BarTwoTone } from './SignalWifi2BarTwoTone';

// Useless
-export { default as SignalWifi3BarLock } from './SignalWifi3BarLock';
-export { default as SignalWifi3BarLockOutlined } from './SignalWifi3BarLockOutlined';
-export { default as SignalWifi3BarLockRounded } from './SignalWifi3BarLockRounded';
-export { default as SignalWifi3BarLockSharp } from './SignalWifi3BarLockSharp';
-export { default as SignalWifi3BarLockTwoTone } from './SignalWifi3BarLockTwoTone';

// Useless
-export { default as SignalWifi3Bar } from './SignalWifi3Bar';
-export { default as SignalWifi3BarOutlined } from './SignalWifi3BarOutlined';
-export { default as SignalWifi3BarRounded } from './SignalWifi3BarRounded';
-export { default as SignalWifi3BarSharp } from './SignalWifi3BarSharp';
-export { default as SignalWifi3BarTwoTone } from './SignalWifi3BarTwoTone';

// Star is better
-export { default as StarRate } from './StarRate';
-export { default as StarRateOutlined } from './StarRateOutlined';
-export { default as StarRateRounded } from './StarRateRounded';
-export { default as StarRateSharp } from './StarRateSharp';
-export { default as StarRateTwoTone } from './StarRateTwoTone';

-export { default as Weekend } from './Weekend';
-export { default as WeekendOutlined } from './WeekendOutlined';
-export { default as WeekendRounded } from './WeekendRounded';
-export { default as WeekendSharp } from './WeekendSharp';
-export { default as WeekendTwoTone } from './WeekendTwoTone';

Those icons can no longer be found on https://material.io/resources/icons/.
I think that we need to keep the sources in GitHub so we can run the update script from a pristine state.

I think that we need to keep the sources in GitHub

Keep the sources, or keep the generated icons, in say legacy, along side custom, and just copy them in?
@colemars Looks like something went wrong, but hang fire until we agree on an approach.

@mbrookes I think the failure is from being pretty far behind master at this point.

+1 for a legacy folder with only the legacy icons.

Having a legacy folder seems like it would be the best approach for clarity.

@colemars I have reset the pull request back to a state without unrelated changes, if you need to recover your changes, you can find them from 68f080c828a6f261764228e8ef2b5cd6860f5615.

@oliviertassinari What is the possibility that template used to generate the icons could change in the future? I'd guess it's pretty minimal at this point, given that the bulk of the code is in the the runtime createSvgIcon.js fiel, but if there's any chance, we should keep the source svgs in the legacy folder, rather than the generated icons. (And do the same for custom over in the social icons PR.)
@colemars No, it wasn't that. If it was, the worst you'd get is merge conflicts.

@mbrookes I have asked myself about this very question, do we keep the raw or the src? It might not make a big difference. Pick what's simpler?

Pick what's simpler?

Either way is just a question of copying some files at the right point in the build process, so perhaps we go with the purest approach and keep the svg files?

Sounds good to me

Pick what's simpler?

Either way is just a question of copying some files at the right point in the build process, so perhaps we go with the purest approach and keep the svg files?

The gotcha is that the files that are saved are the src files and I'm not sure where to easily get the pure svg files for the legacy icons anymore. There could be a manual patch or a one-use script run to cut out the svg path and save it?

I'm not sure where to easily get the raw svg files for the legacy icons anymore.

I imagine @oliviertassinari has them.

Currently I have it set up following how @oliviertassinari originally copied the custom/ icons over in the build script.

Does the index.js get updated for the copied files?

Does the index.js get updated for the copied files?

Just double-checked and yes - all of the legacy icons that were copied over are exported in index.js.

@colemars Awesome, I'm gonna have a last look at the changes and merge. I'm really happy about how the icons handling in Material-UI is turning out. We are getting closer to something great.
A bit that could be interesting to look into is the props Icon.js and SvgIcons support, I like a few of the features of fontawesome: https://fontawesome.com/how-to-use/on-the-web/styling/stacking-icons.

@colemars Thank you!


net/slip: Change SLIP to use IOB

Summary
SLIP seems to be broken after IOB offload (https://github.com/apache/nuttx/pull/8239), try to fix it.
Impact
Change SLIP device to use IOB
Testing
No actual boards for testing, may need your help to confirm whether it works.

@michi-jung could you help us verify this patch?

@michi-jung could you help us verify this patch?

Hi @xiaoxiang781216 and @wengzhe.  Yes, patch is working fine for me.  Thanks!
Could you please increase the buffer array in slip_initialize to 12 characters to silence compiler warnings about potentially truncated output (INT_MIN requires 11 chars + NUL)?  Thanks!

@michi-jung could you help us verify this patch?

Hi @xiaoxiang781216 and @wengzhe. Yes, patch is working fine for me. Thanks!
Could you please increase the buffer array in slip_initialize to 12 characters to silence compiler warnings about potentially truncated output (INT_MIN requires 11 chars + NUL)? Thanks!

@michi-jung Updated, it this what you need?

@michi-jung could you help us verify this patch?

Hi @xiaoxiang781216 and @wengzhe. Yes, patch is working fine for me. Thanks!
Could you please increase the buffer array in slip_initialize to 12 characters to silence compiler warnings about potentially truncated output (INT_MIN requires 11 chars + NUL)? Thanks!

@michi-jung Updated, it this what you need?

@wengzhe Yes, exactly. Thanks!


Error Bridging DAI to ETH

First of all, let's have a prompt that comes up letting them know they don't have any gas and they need to send ETH to the address.
Second, I got this error when going DAI to ETH:

^^ private key if anyone is quick enough ;)


Add Python dependencies

Add an input to specify python dependencies
Fixes #28

Do you have a solution for node.js functions ?
@andresmgot can you review ? thx

Hi there 👋,
Specifying the dependencies one by one will only work for Python. For Ruby or NodeJS it would be necessary to specify a Gemfile or a package.json and upload its content. Since the code disables the possibility of adding dependencies for those two languages I am fine with this PR as far as it has a follow up one in which we can specify those requirement files.

Yes it seems to be another approach for node and ruby. Since python was the simplest one I wanted to start with this PR and yes following up with another PR for Node and Ruby.

Closing in favor of 👉  #31


Use a Meteor release tar.gz file, rather than curl | sh

That way, we can do a hash check of this file.

Well, the install script doesn't seem to provide a way to provide a bundle file, so we'd be left writing a fresh install script.
As a compromise here, I'll embed a copy of the current Meteor install script, which at least hard-codes a version number, so we always get Meteor <IP_ADDRESS>.


Premature Pushing of Stable Docker Tags

Describe the bug
I host all of my infrastructure in a GitOps repository which uses Renovate to automate Docker image updates. I've noticed Memos that frequently triggers update PRs before releases are officially available. For instance, I've had a PR updating to Memos v0.22.3 since 2024-06-21, even though v0.22.2 is the latest release. It appears that the release/0.22.3 branch is being pushed, which is causing this issue.
I would expect stable Docker tags to only be created when a new release is officially available. Pushing release tags early can cause confusion and potentially unstable updates in automated systems, as users may receive updates that are not officially released.
Steps to reproduce
Any hosting strategy that automates updates will have this issue. Renovate makes it obvious in my case, but there are other times this could happen more silently. For example, if a user uses Watchtower, they will receive the update much earlier than they should without warning.
The version of Memos you're using
v0.22.2
Screenshots or additional context
Here is a screenshot of the latest package tags:

I would expect latest to match stable and 0.22.2, while 0.22.3 should not exist or should have a suffix indicating it is not yet stable.

I don't use latest, that was just an example for people that use Watchtower. While I agree that they should use stable, I suspect a lot of people use latest.
I always pin to the latest release, and the reason I've noticed this happens is because I get a PR that a new version is available (in this case v0.22.3) when that version is not really available yet.

Looks like its due to the GitHub workflow building off the branch rather than the tags. A release/0.22.3 branch exists, but the tag doesn't as its obviously not released yet.
https://github.com/usememos/memos/blob/7c9f967a07cd331b1c5df1c0ee1cdb991164935d/.github/workflows/build-and-push-release-image.yml#L7
It would be a simple change to the GitHub workflow, but it all really depends on the dev's workflow for releases.

Just happened again, 0.22.4 got pushed for the version number change in master


Reset and power off functions in Console do not work.

When choosing the option below to reset or power off the endpoint, they do not work, the system does nothing.

Note: The Target customer experienced the same issue.
Power ops from the dropdown list under the 3 dots, works great.

Power off and reset commands function normally under standard conditions. However, these commands will be rejected during active:

SOL (Serial Over LAN) sessions
Storage Redirection sessions
KVM (Keyboard, Video, Mouse) sessions

This behavior is by design to prevent disruption of active management sessions. Please ensure all redirection sessions are properly closed before attempting power operations. Intel AMT Implementation Guide

Hi Madhavi,
In a KVM or SOL session, power off or reset is achievable and a must for AMT power operations. From my note above, you can do resets and power off when choosing from this dropdown list from the 3 dots. We need to do the same action from those icons I circled. If we need to meet to discuss let me know.


Inf1 inference test failures

INF1 Test Summary:

Total Test Passed: 227
Errors : 9

= 227 passed, 200 skipped, 248 deselected, 47195 warnings, 9 errors in 7509.34s (2:05:09
Test Steps :

Setup the neuron environment for your new release
Setup optimum environment -pip install optimum-neuron

Install the latest release: 2.16
Install the dev branch: pip3 install git+https://github.com/huggingface/optimum-neuron#egg=optimum-neuron[tests] tokenizers==0.14.1

clone optimum-neuron repo for tests
git clone https://github.com/huggingface/optimum-neuron.git
cd optimum-neuron/

Run test
pytest -m is_inferentia_test tests

Config: Inf1.6xlarge tests
Release version:
neuron-cc <IP_ADDRESS>+6cae3b7b8
neuronperf <IP_ADDRESS>+5dccae385
optimum-neuron 0.0.16.dev0
torch-neuron <IP_ADDRESS>.9.17.0
9 of Testcases have errors:
NeuronModelIntegrationTest::test_load_model_from_cache
NeuronModelIntegrationTest::test_load_model_from_empty_cache
NeuronModelIntegrationTest::test_load_model_from_hub
NeuronModelIntegrationTest::test_load_model_from_hub_subfolder
NeuronModelIntegrationTest::test_load_model_from_hub_subfolder
NeuronModelIntegrationTest::test_load_model_from_local_path
NeuronModelIntegrationTest::test_save_compiler_intermediary_files
NeuronModelIntegrationTest::test_save_model
NeuronModelIntegrationTest::test_trust_remote_code
Error logs:
RuntimeError: Please specify the token via the HF_TOKEN_OPTIMUM_NEURON_CI environment variable

Attached complete logs for the failures:
inf1_on_test_results.txt

Hi @musunita , all these hub integration tests need a huggingface token. If you are running it locally, you can export a dummy HF token as env variable to run the test.

Can you clarify, how do you export dummy HF token as env variable ?

Setup account to get token here: https://huggingface.co/docs/huggingface_hub/quick-start#authentication

Hi folks, is the token issue solved? May I close this issue? @musunita @jeffhataws

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

Let's close this for now. Will open new one if there are issues.

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Thank you!


Nokogiri.parse accepts Pathname object as argument, but only work with small files then.

I hit this yesterday wit code like
doc = Nokogiri.parse(Rails.root.join('config','file.xml'))
when the file.xml was smaller than about 4k bytes, it worked as a charm.
With larger files, weird behavior was happening. E.g. resulting parsed document
was containing duplicate records.
Then I found this:
p = Pathname.new('/etc/passwd')
[p.read(10), p.read(10)]
=> ["root:x:0:0", "root:x:0:0"]
Nokogiri accepts either string or whatever responds to 'read' method.
Pathname objects respond to read, but they do not keep state or file opened.
Nokogiri reads input in chunks, calling read(SOME_CHUNK_SIZE) possibly several times, based on file size. Pathname#read allways reads from the beginning of file.
With correct alignment of last element before SOME_CHUNK_SIZE boundary, this could be possibly
used to DoS attack that causes OOM (demo attached in commit d90bf404 in my fork).
In PR there are failing tests and proposed fix. It might not be the best approach to fix this.
Maybe other solution would be just to raise an exception when object in string_or_io has none of well known ancestors like String, File, StringIO ...

See additional context from user help request at https://gitter.im/sparklemotion/nokogiri?at=5f5a485bf969413294d84734

Crashing through the wall from #2110; if I was gonna do this I'd explicitly check is_a? Pathname and then have it .expand_path.open. I also lament that StringIO does not inherit IO.

Closing this PR in favor of #2110. @phokz you'll get a shout-out in the CHANGELOG!


[release-2.7] Triggering image rebuild

Signed-off-by: Disaiah Bennett<EMAIL_ADDRESS>

/lgtm


Can't reproduce HumanEval score

follow programming_runs/run_reflexion.sh
get 0.77-0.83 scores for multi trials.

I cannot reproduce the result either 😭 Is it possible for the author to release the generated tests by GPT4 they use in the experiments?

Hi @geekan and @FloridSleeves,
As many LLM papers may be experiencing, we are subject to the performance of proprietary models as there is not a better open-source option to evaluate at a high level of performance. We showed some open-source models' results to prove this in the appendix of the recent version of the paper. If you want to use openai's models with Reflexion, I would advise you to use the -0314 suffix to the gpt-4 or gpt-3.5-turbo models to evaluate a model that was checkpointed at a closer time to our experiments. I hope that we will have more open-source options on which we can use reflexion in the future.

I just ran programming_runs/run_reflexion.sh  directly, and also got 80% only..
and also the amount of human eval only has 161 (which I guess should be 164)?

I just ran programming_runs/run_reflexion.sh  directly, and also got 80% only..
and also the amount of human eval only has 161 (which I guess should be 164)?

I am also curious that HumanEval-python should be 164 tasks.


DateTime command running issue

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/edit
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
The following error encountered when running command:
> Console.WriteLine("The current time is " + DateTime.Now);
At line:1 char:43
+ Console.WriteLine("The current time is " + DateTime.Now);
+                                           ~
You must provide a value expression following the '+' operator.
At line:1 char:44
+ Console.WriteLine("The current time is " + DateTime.Now);
+                                            ~~~~~~~~~~~~
Unexpected token 'DateTime.Now' in expression or statement.
At line:1 char:43
+ Console.WriteLine("The current time is " + DateTime.Now);
+                                           ~
Missing closing ')' in expression.
At line:1 char:56
+ Console.WriteLine("The current time is " + DateTime.Now);
+                                                        ~
Unexpected token ')' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ExpectedValueExpression

This is super weird. Are you able to reproduce it on clean VM/another machine?
It looks like something is hijacking the C# compiler, or bits on disk are horribly corrupt ...

No response, closing. Feel free to reopen when there is actionable info available. Thanks!


method starts with double underscore not found error when inherient from FedAlg

When trying to custom the FL algorithm based on FedAlg, some methods and property are not correctly inherited from the base class FedAlg. This issue happened to self.__task_queue, self.__wb_run.

This seems to be related to Name mangling in Python. Double underscore started methods and attributes are not directly accessible outside the class. As the name is prefixed with the class name when referred to.
See https://stackoverflow.com/questions/15738086/issue-with-python-single-and-double-underscore-variables for more detail.


How to test haxelib?

Hi, I have a problem.
I created small haxelib on my local computer which is inside D:\Projekty\mtasa-haxe-types (code is here: https://github.com/pawel-miczka/mtasa-haxe-types) and I'm trying to test it. To do this I use
haxelib dev mtasa-haxe-types D:\Projekty\mtasa-haxe-types

and in another project I can't use
import mtasa.server.Core;

Why? What I'm doing wrong?

Are you adding -lib mtasa-haxe-types to your haxe command line (or including that library in your .hxml, or other project file)?

Good question, I don't :D. I will test it later today. I will write respond.

Working fine, thanks :)


Add ability to control type encoding

Sometimes it is needed to change how type is being encoded in json result. So I implemented it using implicit CoproductContainer parameter. Previous behavior is persisted. So it’s non breaking change.

So I thought about all that. I think I'd prefer not to introduce an intermediary implicit (CoproductContainer).
I began to refactor argonaut-shapeless so that it would be easier to generate codecs that behave a bit differently than the default ones, see
https://github.com/alexarchambault/argonaut-shapeless/commits/topic/variedencodings,
and
https://github.com/alexarchambault/argonaut-shapeless/blob/bd1f2ba72dd5a5270a4889c4ec4d08ad1529cd07/src/test/scala/argonaut/JsonCodecs.scala#L17-L27
in particular. I think it should be possible to achieve what you'd like by supplying different implicits to encode ccons cells. That would amount to replace cconsJsObjectEncodeJson and cconsAsJsObjectDecodeJson by custom implicits in the former link.
These changes would be for argonaut-shapeless 0.3 (I'll publish snapshot versions as soon as shapeless 2.2 final is out). Would it be ok for you to do it this way?
I'd also be keen to add extra codecs, but the one you added in the tests doesn't feel general enough to me for that. I was more thinking about the same without the type field. I'd be ok to add this in https://github.com/alexarchambault/argonaut-shapeless/commits/topic/variedencodings. (But this may raise issues with the order of items in LabelledGeneric of sum types, and these may have to be addressed in shapeless directly...)

Yep importing different cconsJsObjectEncodeJson is a pretty straight forward, but imho is very low level for library consumer.

I was thinking ultimately about putting alternate sets of implicits like these in other objects whose content could be imported instead of Shapeless._ (or along with it, with careful implicits shadowing), like import Shapeless.InlineSum._.
But for truly custom ways of handling sum types, it has to be a bit more complicated...
Actually, I'm now thinking it could be nice to have something a bit like your PR along with what I'm proposing: one would import Shapeless.Custom._ instead of Shapeless._, and possibly define some implicits JsonProductCodec or JsonCoproductCodec  to override the default behaviour.

I think the changes should consist in:

defining a JsonCoproductCodec trait instead of CoproductContainer, looking like:

trait JsonCoproductCodec {
  def encode(typeName: String, json: Json): Json
  def attemptDecode[T](typeName: String, decodeJson: DecodeJson[T], json: Json): Option[DecodeResult[T]]
}

(which changes a little the logic of decoding),

define an implicit default JsonCoproductCodec in the companion object that behaves like the current coproduct codecs,
define new implicit methods in GenericDecodeJsons / GenericEncodeJsons which would use JsonCoproductCodec, that one would have to use instead of cconsAsJsObjectDecodeJson / cconsJsObjectEncodeJson,
define CustomGenericDecodeJsons and CustomGenericEncodeJsons traits that would use these newly defined methods,
and define a Custom object in Shapeless that mixes these two traits,
and finally adapt the tests you added in your PR to these changes.

These are pretty big changes (which can be discussed). Tell me if you'd prefer me to take care of them.

About the changes in JsonCoproductCodec compared to CoproductContainer, they allow for more general codecs, in particular the JsonCoproductCodec instance doesn't have to provide the name of the type being decoded.

Nice! I was thinking of example when I may need to override JsonProductCodec and here is one:
I may want an instance A(None) of A(oi: Option[Int]) to be encoded as {} instead of {"oi":null} and then decode it back.
Regarding refactoring. I think I can handle that. Gonna take some time though. Like until this friday.

Great! I may throw away the basis of JsonProductCodec (and let JsonCoproductCodec and its details for you) in the mean time then.

About the application of JsonProductCodec, there's this kind of things, yes, and I was also thinking about "case translations", like camelCase on the Scala side <-> serpent_case on the JSON side.

Nice one too!

@alexarchambault Hi! I'm kinda confused about how CustomGenericDecodeJsons and CustomGenericEncodeJsons traits that would use these newly defined methods. Could you please take a look?

The obvious part is that these methods should be reused in both Custom and Automatic variants.

Not much time for a detailed answer now, but:

were you looking at the topic/variedencodings branch? https://github.com/alexarchambault/argonaut-shapeless/tree/topic/variedencodings JsonCoproductCodec should fit there.
then I think it's a matter of adding ccons... methods in the CustomGeneric*Jsons singletons, which should be the counterpart of the hcons... methods already there, and have the ccons... methods in the traits below them use these newly added methods.

Maybe you should just submit a new PR against topic/variedencodings (with fewer commits too). Or if you don't have time, it may be possible for me to just cherry-pick some of your commits in this PR. I'll try (not now, but soon).

That's detailed enough ) thanks, I got it! Will do!


Fetching /rewards/sum with missing arguments should throw an error

User was confused by sum=0 for this /rewards/sum call:
https://api.helium.io/v1/hotspots/112EGXScrsK3Duiox2FjUrceVZuryd4FG1Rtqg8ZMJsTyGWizgJy/rewards/sum
They needed to specify min_time and max_time arguments, like so:
https://api.helium.io/v1/hotspots/112EGXScrsK3Duiox2FjUrceVZuryd4FG1Rtqg8ZMJsTyGWizgJy/rewards/sum?min_time=2021-04-17T01:39:53Z&max_time=2021-04-18T01:39:53Z
The API should throw an error if user has failed to provide expected arguments
Happy Saturday

I was just looking at this and technically the current behavior is correct? Both min_time and max_time default to "now" when not specified. This is interpreted as a timespan [min_time, max_time) (min_time is inclusive, max_time exclusive).
In the example min_time=2021-04-17T01:39:53Z&max_time=2021-04-18T01:39:53Z This means the requester is asking for rewards in that 53rd minute.
That make sense?

Won't that pretty much always be 0? I would suggest either requiring user to specify the arguments, or if there will be default arguments, use more conventional or expected values Maybe last 24 hours?

Won't that pretty much always be 0? I would suggest either requiring user to specify the arguments, or if there will be default arguments, use more conventional or expected values. Maybe last 24 hours?

The former is a good idea.. we could just always fail if not at least min_time is specified.
The latter isn't really great since that affects edge caching for that url (different data for the same url).


blockchain.com is broken

@adguard-bot commented on Tue Feb 09 2021
Issue URL (Incorrect Blocking)
https://www.blockchain.com/
Comment
Username: @MrRobb

--
The information below is automatically generated. Do not delete it.
Referrer:
Custom userscripts:
https://userscripts.adtidy.org/beta/popup-blocker/2.5/popupblocker.meta.js
https://userscripts.adtidy.org/beta/adguard-wot/1.0/wot.meta.js
https://userscripts.adtidy.org/beta/adguard-extra/1.0/adguard-extra.meta.js
https://userscripts.adtidy.org/beta/assistant/4.3/assistant.meta.js

Screenshots

Screenshot 1

Screenshot 2

System configuration

Information
value

AdGuard product:
AdGuard for Mac v<IP_ADDRESS>2 nightly

Browser:
Safari

Filters:
Ad Blocking: AdGuard BasePrivacy: AdGuard Tracking ProtectionSocial Widgets: AdGuard Social MediaAnnoyances: AdGuard AnnoyancesOther: Filter unblocking search ads and self-promotionLanguage-specific: AdGuard German, AdGuard Dutch, AdGuard Spanish/Portuguese, Bulgarian list, EasyList Czech and Slovak, EasyList Italy

Only this exclusion helps: @@||blockchain.com^$document

Seems to be CSP-patching problem

@sfionov hotfix?

Yep, it is our bug - every sitee script has invalid nonce, which is rejected by browser, but adguard assumes that csp directive have nonce and add its nonce, denying all site's resources.

But it is extremely rare I think.

Fixed in 1.7.188


Listing states from S3 can take time and make the progressbar timeout

Description
Listing states from S3 can take time and make the progressbar timeout
How to reproduce
Fill a bucket with a lot a files and run scan with this bucket in --from
Possible Solution
bucket enumeration should notify progressbar

@moadibfr I was wondering if the progressbar should be restarted automatically after a timeout if a new event occur. Sometime read actions may be slow but ends with a success after the timeout, for me we should show that something hang bit if it's ends with a success we should resume the spinning. WDYT @wbeuil we talked about it weeks ago in a pair session if I remember correctly 🤔
For example :
State: Spinning
<-- No new events
State: Hanged after N seconds
<-- New event occur after the timeout
State: Spinning
etc ...

I had the problem when testing driftctl with my Cloudflare DNS (thanks Orange). And it is indeed misleading to see that I hit the timeout, my requests succeed afterwards and the progress was not restarted. I agree with @eliecharra

If this happen we should set the timeout to a higher value. Timeout should happen if there is nothing happening.
I think the idea is to tell the user nothing is happening and he can quit so it should be an rare exception if this is not a real hang.
But yeah I think it could be a good idea to allow progressbar to get event even when timeouted and restart the render. So when we have this exception if the user wait enough it will still work.

If this happen we should set the timeout to a higher value.

 Timeout can be relative to user setup (xDSL with latency line, issues with DNS like @wbeuil , etc ...)

I think the idea is to tell the user nothing is happening and he can quit so it should be an rare exception if this is not a real hang.

I found this is very weak as we cannot predict any network latency or other issues that can slow down the process but does not mean there is an hang. I think it should be the user responsibility to take the decision to interrupt, our actual timeout should be there for UI/UX purpose only.

 Timeout can be relative to user setup (xDSL with latency line, issues with DNS like @wbeuil , etc ...)
yeah but we should find a timeout value that make it as rare as possible

I found this is very weak as we cannot predict any network latency or other issues that can slow down the process but does not mean there is an hang. I think it should be the user responsibility to take the decision to interrupt, our actual timeout should be there for UI/UX purpose only.
yeah but what's the ux purpose if it doesnt give any indication ? I think the indication should be " You waited a long time we thinks there is nothing happening anymore." Even if this mean that most user wait more time that they should. OFC there will be case where it don't work and it will be user's responsibility to kill or not. But we should find a value that's long enoght so most people don't see the progress bar stop.
But as I said it's still a good idea to allow it to restart if it timed out but it finally get an event after.

Progress bar resume handled there #420

Progress bar resume handled there #420

@cloudskiff/engineering Should we close this in favor of #420 ?

Possible Solution
We should introduce a new progressbar for state enumeration count and one for resource enumeration from states files

I did like the idea of this, if you have a large number of statefiles to be parsed or scanned it would be nice to see progress before the resources themselves begin to be scanned.
I think resuming the progress bar helps but they are slightly different (and both helpful) approaches to me.

Progress bar resume handled there #420

@cloudskiff/engineering Should we close this in favor of #420 ?

No, there is two distinct topics there. #420 is to fix a bug when progress bar does not resume after a timeout and this issue is to add a new progressbar for state enumeration and resources enumeration.


Incorrect prospector template

Hello and thanks for your great module!
I tried to use "include_lines" without succes because the prospector template defines it as

  include_lines:
    - []
    - []

When I switched the syntax  to the one from the official documentation it filtered the log accordingly.
https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html

The following example configures Filebeat to export any lines that start with "ERR" or "WARN":

include_lines: ["^ERR", "^WARN"]

Ca you please check it out.
Thanks!

Is Filebeat not starting correctly or not parsing the files correctly? Both formats are valid YAML arrays, but not all YAML parsers are the same. It's not hard to fix, but I want to make sure that there isn't some other error going on with the config file.
Any chance you can include the relevant part of your manifest that's creating the config file example you included?

There's a chance that this is caused because the lines weren't wrapped in quotes. Could you try the multiline_fixes branch to see if that works as expected too?

Filebeat is not parsing the file correctly in the sense that it includes all of the entries in syslog, not just the ones in include_lines.
First try was with

  include_lines:
     - ["balbla\\["]
     - ["randomword"]

Second try did job

 include_lines: ["balbla\[", "randomword"]

I did not had the time to test the other branch.

I should have noticed the issue earlier - do you have any idea where the square brackets around "randomword" are coming from? They're not in the template, so I'm not sure where they're coming from.
Do you know what version of filebeat you're using, and a copy of the test manifest might help too since I'm not able to re-create the error.

The square brackets came from my declaration and it seems that it was the problem

include_lines  => [
      '["balbla\\["]',
      '["randomword"]',
]

But in that case it seemed to me that it should not match at all and not match all lines. Thus I thought it was a problem in the yaml that needed fixing. Sorry for wasting your time.

I think that the square brackets made the YAML parser think that each line was an array. Wrapping the lines in quotes should help with that, so I'll merge in the branch as extra protection against problems like this in the future.
Thanks for helping find a weak point.


remove nodeId, move to form apply

to fix #153

Pull Request Test Coverage Report for Build 147

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 82.836%

Totals

Change from base Build 146:
-0.4%

Covered Lines:
86

Relevant Lines:
94

💛  - Coveralls


Update aws-sdk-go dependency to 1.6.12

1.6.12 = c6fc52983ea2375810aa38ddb5370e9cdf611716

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "update_aws_sdk_go_1_6_12" git@github.com:justinsb/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Current coverage is 51.20% (diff: 100%)

Merging #2154 into master will decrease coverage by 9.37%

@@             master      #2154   diff @@
==========================================
  Files           125        125
  Lines         11433      11433
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6926       5854   -1072
- Misses         3623       4833   +1210
+ Partials        884        746    -138

Powered by Codecov. Last update de5aa9c...1d0cfe8

Please rebase this, just merged a PR which updates to 1.6.9, so resolving vendor.conf and revendoring should do the trick. Trying to track the updates we might be pulling in, is there anything in particular we should highlight in the update from 1.6.9 to 1.6.12?

@dmcgowan thanks - rebased and fixed.
Looking at the diff, there isn't much between 1.6.9 and 1.6.12.  There are some optimizations I would characterize as micro-optimizations, and a few endpoint definitions.   I wasn't aware of the concurrent pull to 1.6.9 and that is new enough for me.  I'm happy to either close (or for you to close) this PR, or if we like to stay on the latest version it's here if you need it :-)

@justinsb thanks for looking into that. I would rather just do the update now to get on the latest since it is early enough in the next release cycle to give people a chance to test. The previous update to 1.6.9 was far more risky so will go ahead and merge this in when tests pass.

LGTM


ControllerAs synax

Don't think I saw an option for this in the document, but 'ControllerAs' syntax would be nice to have. This would allow the ability to pass 'this' as scope. Not sure if the following will be helpful:
// controller declaration
var vm = this;
$ngConfirm({
    scope: vm
});

Can you please explain if angular-confirm had an option for controllerAs, how would it look like ?
The example you provided is valid though,
angular-confirm requires a scope, which is vm in this case, will work fine.

Will something like this work as well:
$ngConfirm({
    controller: ['$filter', function($filter) {
        var vm = this;
        // Controller code here
    }],
    controllerAs: 'vm'
});

Do you know any other plugin that does this?
Currently angular-confirm simply takes the template and compiles it with the scope, and returns the scope.
adding the proposed thing will be complicated.

ngDialog is one plugin that does it:


BUG: gamma distribution's inverse survival function overflows for very small input

gamma.isf overflows when q is small
Reproducing code example:
In [41]: gamma.isf(1e-17, 0.864)
Out[41]: inf

In [42]: gamma.isf(1e-17, 1)
Out[42]: inf

In [43]: gamma.isf(1e-17, 5)
Out[43]: inf

In [44]: gamma.isf(1e-17, 100)
Out[44]: inf

By comparison, this is the correct output produced by R:
> qgamma(1e-17, 0.864, lower.tail=FALSE)
[1] 38.54902
> qgamma(1e-17, 1, lower.tail=FALSE)
[1] 39.14395
> qgamma(1e-17, 5, lower.tail=FALSE)
[1] 51.83694
> qgamma(1e-17, 100, lower.tail=FALSE)
[1] 210.006

I discovered this because it became a blocker in a PR i'm working on for improving the invgauss distribution.
Scipy/Numpy/Python version information:
1.7.0.dev0+f551178 1.20.1 sys.version_info(major=3, minor=8, micro=6, releaselevel='final', serial=0)

The gamma distribution contains calls to scipy.special where there is overlap between probability functions (cdf,pdf,etc) and special functions.
Most of the special functions used in stats come from cephes fork at the moment.
I’m not clear what isf refers to, could you elaborate?
-L

On Mar 9, 2021, at 11:02 AM, zoj613 @.***> wrote:

It looks like there is no direct implementation for gamma.isf method in the gamma_gen class : https://github.com/scipy/scipy/blob/9ebe12790b6a683669916a55fbf8e35deee93e0b/scipy/stats/_continuous_distns.py#L2627-L2745
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@rlucas7 isf is the inverse of the survival function. The right tail quantile function of the gamma distribution.

@rlucas7 isf is the inverse of the survival function. The right tail quantile function of the gamma distribution.

Ah right, so I don't think that one is in cephes so I'm guessing we fall back to this:
https://github.com/scipy/scipy/blob/9ebe12790b6a683669916a55fbf8e35deee93e0b/scipy/stats/_distn_infrastructure.py#L1019
that is in rv_generic and it does not look like there is anything in rv_continuous:
https://github.com/scipy/scipy/blob/master/scipy/stats/_distn_infrastructure.py#L1492

Yes, there doesn't appear to be a function implementing it specifically for the gamma distribution, and as far as im aware there is no corresponding special function for it in the cephes library. I linked a paper in this thread that has an algorithm for the isf function. I believe scipy already has the required functions in place for making its implementation painless should someone be willing to contribute.

does this help
p = [0.5, 1e-10, 1e-15, 1e-20, 1e-50]
stats.gamma.isf(p, 2), special.gammainccinv(2, p)
(array([ 1.67834699, 26.33398152, 38.20846876,         inf,         inf]),
 array([  1.67834699,  26.33398161,  38.20764823,  49.98319799,
<PHONE_NUMBER>8]))

does this help
p = [0.5, 1e-10, 1e-15, 1e-20, 1e-50]
stats.gamma.isf(p, 2), special.gammainccinv(2, p)
(array([ 1.67834699, 26.33398152, 38.20846876,         inf,         inf]),
 array([  1.67834699,  26.33398161,  38.20764823,  49.98319799,
<PHONE_NUMBER>8]))

It does! I had no idea no idea those inverse functions existed in scipy. Thank you. I wonder why they aren't used to compute the isf and ppf of the distribution.

I submitted a fix at https://github.com/scipy/scipy/pull/13684


Validate user name for length

Description
Validate user name for length between 0-25 characters long.
Program Name
Main.js file modified
Issue Solved
Fixes #209
Changes Made
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my code

@prakhartiwari0 Kindly review

@prakhartiwari0 Kindly validate and merge the PR.

@prakhartiwari0


TSCBasic: support case insensitivity for environment

Windows is case insensitive for the environment control block, which we did not honour.  This causes issues when Swift is used with programs which are incorrectly cased (e.g. emacs).  Introduce an explicit wrapper type for Windows to make the lookup case insensitive, canonicalising the name to lowercase.  This allows us to treat Path and PATH identically (along with any other environment variable and case matching) which respects the Windows behaviour.  Additionally, migrate away from the POSIX variants which do not handle the case properly to the Windows version which does.
Fixes: #446

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci test

This will need a complementary change in swift-driver, I'll whip that up in a bit.

It may break SwiftPM and/or SourceKit-LSP too, that's why deprecation of the old API and introducing a new one may be preferable.

Sure, the deprecation is something to consider, but this is a problem for Windows and needs to propagate.

@swift-ci please test

@swift-ci please test Linux platform

@MaxDesiatov I'm no longer convinced that trying to do this is valuable and we should just expose this in all its nuance to all users.  We will end up having to rebuild the full Dictionary interface otherwise.  Either way, the constraints that are needed on the public interfaces are such that we need to make CaseInsensitiveString public in any case, so there is no true value in trying to convert this to a custom data structure.

One more request here: this needs a test case to clarify and verify all of the new API surface, since the original bug report doesn't provide a self-contained reproducible test case. Hence my confusion about desired behaviour in a different version of the change.

I don't know about tests that would be useful here - this is providing the API surface that is necessary to build the dependencies - I don't think that this makes sense to provide tests for unless we just give up on the type representation and just force people to spell out the dictionary type.

We have to verify that the new API surface works well in the first place. Tests codify a specification for the behavior and the API shape.
For example, if you want to preserve string case sensitivity internally while allowing case insensitive lookup at the same time, as you mentioned in the other PR, tests should verify that this property holds, and will also guarantee that it doesn't regress in the future.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform


⚠ Blutopia has degraded performance

In cabc758, Blutopia ($BLU) experienced degraded performance:

HTTP code: 200
Response time: 1005 ms

Resolved: Blutopia performance has improved in 90e0bee.


Adds serializers and views for website submission API endpoints.

r? @ngokevin

r+

Thanks! Waiting on tests first, then will merge.

Nudging Travis


stateParams not reset when moving from one showView to another showView

Navigate to page 2 (or higher) in a listView for entity A
Click on an entity in the list
In the showView or editionView, click on a detailLink reference to entity B
In entity B's showView or editionView, click the List button

You will now be viewing the listView for entity B, on the same page number you were on in the entity A listView.  If the page number you were on for the first listView is higher than the number of pages in the second listView, you will get a 'page not found' error.
This is release 1.0.0-alpha4

I can't reproduce the bug in the blog example when I remove infinite pagination on post list and set perPage(5) on both the comment and the post list.
Fell free to reopen if you can find a reproduceable test case with the blog example.


chore: init url meta in rpc server

Signed-off-by: Jim Ma<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] 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 change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] Code compiles correctly.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report

Merging #1098 (6f13273) into main (ded3174) will increase coverage by 0.03%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main    #1098      +/-   ##
==========================================
+ Coverage   45.35%   45.39%   +0.03%
==========================================
  Files         130      130
  Lines        9906     9909       +3
==========================================
+ Hits         4493     4498       +5
+ Misses       4888     4885       -3
- Partials      525      526       +1

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
45.39% <50.00%> (+0.03%)
:arrow_up:

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

Impacted Files
Coverage Δ

client/daemon/rpcserver/rpcserver.go
31.35% <0.00%> (-0.55%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
57.67% <100.00%> (+0.05%)
:arrow_up:

cdn/supervisor/progress/progress.go
97.01% <0.00%> (+5.97%)
:arrow_up:


Add instrumentation recommendation to performance getting started page.

This change adds recommendations to instrument application code using a similar pattern to MRTK, especially in event handlers.

/azp run


CAMEL-11532 Java DSL enhancement to accept supplier and function arguments

Enhanced setBody DSL with new methods accepting supplier and function argument, to align with Java 8 APIs.

We would need unit tests as well.

Attached the missing unit tests and removed the redundancy.

I dont yet see the value of the inMessage or the test is somewhat wrong, as you set a string as in message which would be wrong imho, the inMessage should be Message and not the message body.
Also your unit tests need license headers.
And check the source with
mvn compile -P sourcecheck

for code formatting problems.

@davsclaus thank you for the review. I fixed the above issues.
I realized that transform().inMessage(...) replaces the OUT/IN Message body, exactly as transform().body(...) does. So, I removed the inMessage(Supplier<>) method (that was added in my first commit), as it would have the save effect as body(Supplier<>). It can be used when we need to calculate the new body taking the IN message into account.
Additionally, it seems (to me) that transform(...) does not differ from setBody(...) expression (also verified by comparing TransformProcessor and SetBodyProcessor). Both replace the body of IN or OUT message. What is the reason of providing both expressions (apart from backwards compatibility) ? Maybe I am missing something.

Its EIP pattern name - setBody is not an EIP pattern name, but they do the same.

@lburgazzoli do you mind taking a look at this

@lburgazzoli, thank you, hope it is good now. I can see that in any case the ExpressionSupport.evaluate(Exchange exchange) has Object return type, so I thought that no generics are used in the expression result type.

@sermojohn yah it was more to avoid  warnings

@sebbrousse could you please open the pr again to the master branch ?
I didn't spot that it was against branch 2.20.x

@lburgazzoli , @sebbrousse I can send a new PR to the master.
When I started this branch, the master had some build issues, so I started from the latest release branch with no build issues.


Setting LocksmithAccessibleOption.Always for reading data from background

I need to load data from background:
let dictionary = Locksmith.loadDataForUserAccount("myUserAccount")

but I get the InteractionNotAllowed error. I figured out that I need to some how set the LocksmithAccessibleOption to Always. but I don't use protocols I just use simple:
try Locksmith.saveData(["some key": "some value"], forUserAccount: "myUserAccount")

and I don't find any way to set LocksmithAccessibleOption here.
And one side question (Sorry I don't know if this is the place to ask this question):
In example TwitterAccount this code confuses me:
let account = TwitterAccount(username: "_matthewpalmer", password: "my_password")

// ReadableSecureStorable lets us read the account from the keychain
let result = account.readFromSecureStore()

In order to read the twitter account data for user we need to create an instance of TwitterAccount with username and password, but I thought the whole point is we don't know username and password of the twitter account and want to retrieve that data from keychain of the device. If we know the username and password of the user, what are we reading from secure store?

Hi
Thanks for using Locksmith!
Re the first point, there's no way to pass in the accessibility options via those class methods. Your best option is to wrap a class method around an internal protocol-conforming type. This is how the library-provided class methods work, so you will probably be able to use those as examples.
Re the second point. I've been hearing that a little lately, so I think I'm going to rewrite the README to be more clear when I get time.
Thanks very much,
Matt

On 30 Nov 2015, at 11:25 PM, Mani<EMAIL_ADDRESS>wrote:
I need to load data from background:
let dictionary = Locksmith.loadDataForUserAccount("myUserAccount")
but I get the InteractionNotAllowed error. I figured out that I need to some how set the LocksmithAccessibleOption to Always. but I don't use protocols I just use simple:
try Locksmith.saveData(["some key": "some value"], forUserAccount: "myUserAccount")
and I don't find any way to set LocksmithAccessibleOption here.
And one side question (Sorry I don't know if this is the place to ask this question):
In example TwitterAccount this code confuses me:
let account = TwitterAccount(username: "_matthewpalmer", password: "my_password")
// ReadableSecureStorable lets us read the account from the keychain
let result = account.readFromSecureStore()
In order to read the twitter account data for user we need to create an instance of TwitterAccount with username and password, but I thought the whole point is we don't know username and password of the twitter account and want to retrieve that data from keychain of the device. If we know the username and password of the user, what we are reading from secure store?
—
Reply to this email directly or view it on GitHub.

Thank you for the great work. Since I had a deadline to deliver today, I used this Keychain wrapper and changed the accessibility option in that code.

@mani47 Had the same problem. Ended up getting rid of this library and using KeychainAccess which is much less dogmatic. All these protocols and lack of any decent documentation were deal breakers.

"Your best option is to wrap a class method around an internal protocol-conforming type".
Could you elaborate on this, Matt? It is not at all clear from looking at the code what you are talking about doing.


can you provider spring cloud base nacos demo?

Question
can you provider spring cloud base nacos demo

no one replied,but this can have

What you want to know is shenyu-examples-springcloud.
url is : https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-springcloud


Fixed #35326 -- added allow_overwrite parameter to FileSystemStorage.

Trac ticket number
ticket-35326
Branch description
This patch handled temporary uploaded files when the filesystem storage allows overwriting files.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] For UI changes, I have attached screenshots in both light and dark modes.

What about using the OPTIONS dict to implement this feature more generally?

@sarahboyce Thanks for your review. I've added OS_OPEN_FLAGS back in, for deprecation, and I added some documentation. Do we need to add a deprecation warning in the code if OS_OPEN_FLAGS is used? If so, I'm not sure how to do that since we're always setting OS_OPEN_FLAGS here in the django code.

Kind of derailed the original ticket so would rename the title

Thank you for the updates @bcail, have you seen this suggestion?
As it would change how exists works (a method we should overwrite/define) rather than get_available_name (that in theory we shouldn't overwrite/define), I think this might be a better way to go 🤔

@sarahboyce I wonder if there would be any downstream code that would want to call exists(), to see if a file is in storage or not, and would get confused by us changing exists() to always return False for overwriting storage?
But I'll do it whichever way you think is best.

Thank you @bcail 🥳 this looks great, I pushed up small edits and will seek a second opinion before merging 👍

Thanks, @sarahboyce.


Refactors event handling in PlayerRepositoryImpl and turns increments into flows

WHAT
Simplify event handling in PlayerRepositoryImpl and handle increment change events.
WHY
To be more consistent in what constitues state and make it easier to support player changing in the future.
HOW
All events are now handled in onEvents. getSeekBackIncrement() and getSeekForwardIncrement() now returns flows instead of values.
Checklist :clipboard:

[X] Add explicit visibility modifier and explicit return types for public declarations
[X] Run spotless check
[X] Run tests
[X] Update metalava's signature text files

@dpreussler fyi API changes in PlayerRepository - thoughts?

This PR seems to break playing from the library screens, now requires a second click to start playback.


Add some govisord sample files

Lets add a samples directory underneath govisord so that people can use that to see what govisord should look like.

This was fixed by
commit f5031f39983d9bbcb8b3c9f810aa0185dd8ca0a5
Author: Garrett D'Amore<EMAIL_ADDRESS>Date:   Mon Sep 14 12:44:27 2015 -0700

    fixes #26 KeyBar not updated when selected unselected
    fixes #25 Authentication regression in #20
    fixes #26 Add some govisord sample files

The commit comments were wrong.  Oops!


Input lag after switching between multiple game instances

Tested versions
Reproducible in 4.3.beta1
Not reproducible in 4.3.dev6, 4.2.2.stable
System information
Godot v4.3.beta1 - Windows 10.0.22000 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; <IP_ADDRESS>22) - 11th Gen Intel(R) Core(TM) i5-11400 @ 2.60GHz (12 Threads)
Issue description
When running heavy code in a node's _process() function the input response is lagging well below FPS after switching between multiple local instances.  This applies to all input methods, both those captured in custom code and built-in systems.
Expected behavior:  Input should not lag significantly below FPS.
Notes:
Exporting the project and running the executables reduces the effect but it is still present.
This is not affected by the renderer used.
The issue may be affected by the power of the system its run on, change the loopmax variable in the script and experiment.
While this won't be an issue for most users, those who are developing and testing multiplayer games on local machines will be affected.
Steps to reproduce
Create a project with any form of input and feedback to the user, UI buttons will suffice.
Add heavy code to the _process() function, a loop will suffice.
Launch 2 instances (open a second editor instance and run the game from the launcher, just launching a second instance of the editor will suffice).
Hover over the buttons, then switch between windows and hover over them again, now there is significant lag.
Minimal reproduction project (MRP)
new-game-project.zip

Do you know how long the code in your _process loop is taking? A measurement in milliseconds would be helpful.

Do you know how long the code in your _process loop is taking? A measurement in milliseconds would be helpful.

Barely noticeable at 10ms, UI becomes basically unusable at 20ms.
Replace the while loop in the script with OS.delay_msec(15) and change the value.
This is a much better approach than my original while loop in any case, thanks for your comment!

This looks very similar to #92759 and #92307. Can you download the artifacts from pr #92742 and confirm if your issue is already solved?

Yes, the issue doesn't occur in that version!


tfstate file bytes not flushed to nfs mounted directory

When attempting to create k8s cluster resources in azure using DOCKER approach I see tfstate get created by nfsnobody, but it remains a 0 byte file. If I ask it to write out tfstate to a "local filesystem directory" like /tmp/mydir/, it succeeds; so I have a workaround. I'm opening this issue because customers will run into this and either:

at the least our install doc should advise the install person to put tfstate in a non-nfs dir
the docker-dope container could write out tfstate to a local tmpdir in /tmp (or some confirmed local mount) and when done copy it to the dir the user specified. Each deployment IaC script that modifies the tfstate would need to implement this internal workaround.

----- details
cd /r/ge.unx.sas.com/vol/vol620/u62/zahelm/gitrepos/epd-deployment-automation/deploydir-azure-zahelm-01
df -PH .
Filesystem                  Size  Used Avail Use% Mounted on
ge.unx.sas.com:/vol/vol620  3.0T  2.3T  659G  78% /r/ge.unx.sas.com/vol/vol620
export DOPEVERSION=0.3.0
export THISDIR=/r/ge.unx.sas.com/vol/vol620/u62/zahelm/gitrepos/epd-deployment-automation/deploydir-azure-zahelm-01
docker run
-e TF_VAR_subscription_id="$SUB_ID"
-e       TF_VAR_tenant_id="$TENANT_ID"
-e       TF_VAR_client_id="$SP_APPID"
-e   TF_VAR_client_secret="$SP_PASSWD"
-e    ARM_SUBSCRIPTION_ID="$SUB_ID"
-e          ARM_TENANT_ID="$TENANT_ID"
-e          ARM_CLIENT_ID="$SP_APPID"
-e      ARM_CLIENT_SECRET="$SP_PASSWD"
-v $THISDIR:/data
docker-dope.cyber.sas.com/viya4-iac-azure:$DOPEVERSION
apply
-auto-approve
-var-file /data/terraform.tfvars
-state /data/terraform.tfstate
while that docker run is running I see the following tfstate files in $THISDIR
-rw-r--r-- 1 nfsnobody nfsnobody    0 Nov  3 12:04 terraform.tfstate
-rw------- 1 nfsnobody nfsnobody  209 Nov  3 12:00 .terraform.tfstate.lock.info
after that docker container is done running, I see 0 bytes written to tfstate:
-rw-r--r-- 1 nfsnobody nfsnobody    0 Nov  3 12:04 terraform.tfstate

Closing as we have long since added support and docs on running the container os the host user.


mingw64 build error

build from master branch with x86_64-w64-mingw32-gcc, get this error:
../ssl/statem/extensions_srvr.c:18:10: fatal error: netinet/in.h: No such file or directory
 #include <netinet/in.h>
          ^~~~~~~~~~~~~~

github CI now has some windows builds (though not mingw64) which pass so this should be ok now


Update the HackUTD favicon files

Updated the new favicon files, from favicon generator using Logo.png

Currently, the favicons look like this:

Can we change it so the background is black instead of white?

Hey, is there a reason why this was closed?
Additionally, I'd prefer a transparent option or something that works on all devices. You should be able to have an adaptable favicon based on the theme by following this guide.


Document origins of "pdf" versions of pre 5.5 specifications

Copies of GEDCOM 3.0, 4.0, 5.0, 5.3, and 5.4 have all surfaced online at some point over the last 6 or 7 years.  However, these have been presented in a range of inaccessible or obsolete formats which were often unsuitable for sharing or searching.
Since 2015, we have converted GEDCOM 3.0, 4.0, 5.0, 5.3, and 5.4 to searchable pdfs (hosted here), some of which are now being hosted directly on gedcom.io/specs.  We would like to ensure that the original sources and conversion process is documented and retained.
@luther Specifically for GEDCOM 3.0 and 4.0, several minor transcription errors have been corrected since these specs were first published as text pdfs. It is suggested that you pull down current copies of those transcriptions from chronoplexsoftware.com to replace those currently published on gedcom.io.  The current one dates from 2019 and 2018 respectively.
GEDCOM 3.0 is only known to exist as original paper copies and scans thereof:
http://www.beholdgenealogy.com/GEDCOM3.0.pdf
That scan was transcribed using OCR and manually corrected to produce the following pdf first made available in Jul 2016:
https://chronoplexsoftware.com/gedcomvalidator/gedcom/gedcom-3.0.pdf
GEDCOM 4.0 is only known to exist as original paper copies and scans thereof.
https://web.archive.org/web/20160318183421/http://www.genpluswin.de/gedcom/Gedcom_4.pdf
That scan was transcribed using OCR and manually corrected to produce the following pdf first made available in Feb 2015:
https://chronoplexsoftware.com/gedcomvalidator/gedcom/gedcom-4.0.pdf
GEDCOM 5.0 exists in original form as a DOS text version with a txt extension.
https://www.beholdgenealogy.com/Gedcom.standard.5.txt
This was manually reformatted in Microsoft Word and converted to pdf:
https://chronoplexsoftware.com/gedcomvalidator/gedcom/gedcom-5.0.pdf
GEDCOM 5.3 exists in original form as a R82 (Word Perfect 5.1) and T82 (DOS text) documents.
https://www.saintclair.org/ftp/pub/pafutils/geddoc.zip
The Word Perfect file can still be opened in current versions of Microsoft Word, retaining all original formatting.  For legibility the font was changed to Times before being converted to pdf:
https://chronoplexsoftware.com/gedcomvalidator/gedcom/gedcom-5.3.pdf
GEDCOM 5.4 is only known to exist as an HTML conversion of the Word Perfect original.
http://www.lege.com/gedcom54.html
This was manually reformatted in Microsoft Word and then converted to pdf:
https://chronoplexsoftware.com/gedcomvalidator/gedcom/gedcom-5.4.pdf

More over, we would be happy to contribute editable Microsoft Word versions of GEDCOM 3.0, 4.0, 5.0, 5.3 and 5.4 in order that all these older specifications can continue to exist in a modern, accessible, and readily editable format should any further transcription errors or conversion work be required.

Thanks for this context, and for your work in creating the PDFs! I was not personally involved in collecting or posting these PDFs, but I'll make sure those who were respond to this issue.
I'm a bit unclear about provenance and permissions here.

Are you giving gedcom.io permission to host your PDFs?
How would you like to be cited?

The earlier specs were previously collected by Tamura Jones and have for many years been available here:
https://www.tamurajones.net/FamilySearchGEDCOMSpecifications.xhtml
Tamura's webpage includes a PDF of GEDCOM 3.0 which obtained by Brian Madsen.  Note that Tamura credits those who found or provided copies of each document. At the bottom of the page, Tamura includes links to some other relevant articles of his about the history of GEDCOM standards as well as 3 links to my blog posts when I rediscovered some some of the early standards (3.0, 4.0 and 5.0)
Also see this article by Tamura about GEDCOM 1.0 as well as the links below it to my two blog posts,
Also very relevant to history is the GEDCOM Specification, Future Direction Draft, by the Family History Department of The Church of Jesus Christ of Latter-day Saints, 7 July 1999, which Tamura has on his page.
And then there's the GEDCOM Event-Oriented Form, Draft Release 1.0, 12 Sept 1994, prepared by COMMSOFT which I don't believe is available online, but I have a copy of it.

Are you giving gedcom.io permission to host your PDFs?

Yes. Now that GEDCOM has an official home any efforts to preserve earlier specifications should be consolidated here.  Our main concern is ensuring that these older specifications can continue to exist in an accessible future proof format, and can be freely shared (note specifically the copyright notice in GEDCOM 3.0 and GEDCOM 4.0 which is more restrictive that in GEDCOM 5.x).

How would you like to be cited?

This issue is a sufficient record of the conversion works undertaken.

And then there's the GEDCOM Event-Oriented Form, Draft Release 1.0, 12 Sept 1994, prepared by COMMSOFT which I don't believe is available online, but I have a copy of it.

It is available online in both pdf and WordPerfect formats:
http://www.saintclair.org/ftp/pub/pafutils/eged10ww.zip
http://www.saintclair.org/ftp/pub/pafutils/eged10wp.zip


Support onlyHead, onlyEmpty, and omitEmptyLastRow for gutter decorations

Description of the Change
Adds support for onlyHead, onlyEmpty and omitEmptyLastRow to custom gutter decorations.
Alternate Designs
None
Why Should This Be In Core?
This is changing core TextEditorComponent behavior.
Benefits
Currently scary hacks like this are needed if a package has a custom gutter and wants to have the cursor-line selection highlight extend over the custom gutter.
This allows a package to opt-in to a cursor-line on their gutter with (example taken from linter-ui-plus package):
    this.textEditor.decorateMarkerLayer(this.textEditor.selectionsMarkerLayer, {
      gutterName: 'linter-ui-plus',
      type: 'gutter',
      class: 'line-number cursor-line-no-selection',
      onlyEmpty: true,
      onlyHead: true
    })

    this.textEditor.decorateMarkerLayer(this.textEditor.selectionsMarkerLayer, {
      gutterName: 'linter-ui-plus',
      type: 'gutter',
      class: 'line-number cursor-line'
    })

Possible Drawbacks
None but I don't understand that much of the text editor code. @nathansobo ?
Applicable Issues
None that I found

Thanks for contributing!
This looks like a good idea. Before we can merge it though we'll need tests. There are already tests for onlyHead and related options for the gutter decorations as well as tests for the custom gutter decorations. It would be good to combine them to produce a new test of this behavior so we can be sure it doesn't regress in the future.
The CI failure doesn't seem related. Maybe you could rebase on master to be sure and I can help investigate if it still fails.

I'll see what I can do for a test. I understand very little what's going on in there. This change was more of a gut, "yeah, this looks like it should go here" kind of change.

Just want to call your attention to #15011 as a custom gutter decoration in a marker layer hits that bug so it makes utilizing this PR for what I'd like impossible.