[Feature request from Discussions] StorageAccount - Add LargeFileSharesState property

Discussed in https://github.com/Azure/ResourceModules/discussions/2568

Originally posted by dibcar January 13, 2023
Hi, the property 'LargeFileSharesState' is not in the storageaccount module. Is there another way to set this property to 'enable' or the property is just missing in the module ?
Thanks

@eriqua shall we also include allowCrossTenantReplication under this same feature request?
It is a recommendation based on a Policy Definition and we can set it to false as default for security best practices.
Reference from the Storage template documentation:
allowCrossTenantReplication	Allow or disallow cross AAD tenant object replication. The default interpretation is true for this property.

@ahmadabdalla nothing against that as completeness is what we should aim for. I think it just depends on how much more adding all missing properties would take compared to adding the one requested.
We could also prioritize this feature and meanwhile open an issue to generally extend the resource with all missing properties.

@eriqua .. created an issue for it https://github.com/Azure/ResourceModules/issues/2573


Delete techstack.md

:white_check_mark: Build Sankhya-SDK-dotnet 3.0.498 completed (commit https://github.com/guibranco/Sankhya-SDK-dotnet/commit/54679432a7 by @guibranco)

:white_check_mark: Build Sankhya-SDK-dotnet 3.0.505 completed (commit https://github.com/guibranco/Sankhya-SDK-dotnet/commit/892b04e14d by @guibranco)


Demo self-hosted GitHub runners on release

We currently have one n1-standard-96 acting as a GitHub self-hosted
runner. This is a demonstration of using it. So far results look good:
it built the main linux distribution in 10 minutes instead of 4 hours:
https://github.com/google/iree/runs/6825502395
vs
https://github.com/google/iree/runs/6810296844
Was previously #9430, but needed to be a branch on the main repository
to trigger the action on it.

Ok still some kinks. We're running into https://github.com/actions/checkout/issues/273 because of docker's obnoxious habit of creating files as root. Do the self-hosted runners run everything as root? We can employ our docker_setup scripting here or use some other solution. We also have this very helpful error message from GitHub:

I think this is because the runner was queued too long or something. I forgot to make the disk a reasonable size, so we immediately ran out of space and everything was upset. Still pretty annoying that that's the error though. I think I've seen that once before.

Ok I think the difference is that the managed runners have passwordless sudo. There are also some cosmetic differences (like user name being "runner" vs "github") that I'll just unify

Well with those things fixed, still running into issues:
:::: Auditwheel /wheelhouse/iree_compiler-*-cp37-cp37m-linux_x86_64.whl
usage: auditwheel [-h] [-V] [-v] command ...
auditwheel: error: cannot access /wheelhouse/iree_compiler-*-cp37-cp37m-linux_x86_64.whl. No such file

It appears that the scripting is assuming that package-suffix starts with a dash. Given that this is a freeform user input field, I don't think that's a great idea. I can work around it for now, but @stellaraccident I think we should either:

validate that the field starts with a dash immediately on workflow launch
assume it doesn't start with a dash and add the dash ourselves in cmake_ci.py
Not assume it starts with a dash when fetching files

Which is your preference?

Ah the checkout issue is because this runner is actually being reused, unlike with the managed runners. Duh. So Docker's shenanigans cause more of an issue. We'll need to be a little more careful in how we use docker or we'll need to wipe the working directory each time. I'll seif there's an obvious hook for that.

I keep hitting similar issues like:

auditwheel: error: cannot access /wheelhouse/iree_runtime_instrumented*cp37-cp37m-linux_x86_64.whl. No such file

Whereas the file is called iree_runtime_gcmn_testing_runners_instrumented-0.1a1-cp37-cp37m-linux_x86_64.whl
It seems like this doesn't work with a package suffix at all. Other than that, I believe the self-hosted runners are working.

Ok, all the jobs passing on the self-hosted runner: https://github.com/google/iree/actions/runs/2498033117. I filed https://github.com/google/iree/issues/9500 for support for package-suffix being broken

Now switched to release runners in a separate project. There are 3 64-core release runners, which should certainly make the linux build not the bottleneck on releases. Latest run (before uncommenting the mac build: https://github.com/google/iree/runs/6905353191)

This is great - thank you!

I'm waiting till the latest release completes before messing with the setup any further, since we've already had it fail today

I'm waiting till the latest release completes before messing with the setup any further, since we've already had it fail today

Unfortunately, I think this will have to wait until we can have GitHub runner groups. Going to drop back to draft for now

Ok I've got secure release builders set up. Unfortunately, making them secure included restricting the workflow version that could run to "main", so this is impossible to test presubmit. I think we can probably add some configurability so that someone can test the build on our presubmit, but there's no way to test the runners on presubmit, so... yolo?

@ScottTodd @stellaraccident are you OK with me going ahead and merging this? If releases fail we can roll back (and I'll kick of a release immediately). Unfortunately the controls GitHub gives us aren't fine-grained enough for what we want here.

Are you going to be online to monitor and deal with any issues? I'm basically offline now through next Wednesday...

@ScottTodd @stellaraccident are you OK with me going ahead and merging this? If releases fail we can roll back (and I'll kick of a release immediately). Unfortunately the controls GitHub gives us aren't fine-grained enough for what we want here.

Are you going to be online to monitor and deal with any issues? I'm basically offline now through next Wednesday...

Me too :-D I can wait till next week. @stellaraccident if you want fast releases in the meantime, feel free to merge this and be prepared to revert if necessary

JK, I'll be online for a bit now so I'll go ahead and do this

Well the first thing I've learned: the "schedule candidate release" workflow invokes the "build release packages" workflow using the workflow file from the tag it just created. I'm not sure how that will interact with the runner group workflow restrictions.
Also, I have a syntax error in my bash. Reverting

Well the first thing I've learned: the "schedule candidate release" workflow invokes the "build release packages" workflow using the workflow file from the tag it just created. I'm not sure how that will interact with the runner group workflow restrictions.

It interacts poorly. Looks like the restriction means that the ref literally has to be "main" and a tag pointing at some past commit on main doesn't work. So we can restrict to a specific workflow, but can't really use the pretty limited feature to limit the ref. There's no option to specify matching patterns for the ref or anything either. And workflows are just the filename and don't distinguish between forks and the main repo because the ref it's looking at is actually refs/merges/<pr number> on the main repo. So... runner groups look to actually be completely useless here


[iOS] Image library appears and quickly dismiss itself over native view

Bug
When calling ImagePicker.launchImageLibrary on iOS, nothing happens on the first time, then on calling it again causes the gallery view to appears and dismiss itself right away, freezing the app after that.
Currently the screen I'm calling it has a bridged native view (tested removing all the content in there and keeping a blank RCTViewManager that returns an empty view and got same result). Also note that removing the native view from the JS component causes it to work as expected.
Environment info
React native info output:
React Native Environment Info:
    System:
      OS: macOS 10.14.6
      CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
      Memory: 80.83 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 8.11.1 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 5.6.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 16, 17, 18, 19, 24, 25, 26, 27, 28
        Build Tools: 25.0.2, 27.0.3, 28.0.3
        System Images: android-16 | Google APIs Intel x86 Atom, android-17 | ARM EABI v7a, android-25 | Intel x86 Atom, android-25 | Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom_64, android-26 | Intel x86 Atom, android-26 | Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-27 | Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.9 => 0.59.9
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Library version: 1.0.2
Steps To Reproduce
Simply call ImagePicker.launchImageLibrary from a component with a bridged react native view.
Describe what you expected to happen:

Open the library to pick the image

Can you attach/link a repo with the issue?

make sure you don't rerender the component while the gallery is opened

Got the same problem, impossible to debug. Someone got the solution for this issue ?

Ok I've found a solution for your problem which was mine. But I used a custom modal to open the choicePicker so I add a timeout to close the modal then open native gallery. On iOS I set the timeout to 1 sec, and i think this timeout should be variant on which device the user is. @GlisboaDev

https://github.com/react-native-image-picker/react-native-image-picker/issues/1573#issuecomment-757546103


run editor (and tests) entirely out of builds or dist directory

depends on #16, #17, #18 (integration tests)
depends on #28 (switching to webpack)?  That may be a better way to do this, once we have tests
We ultimately want the builds directory to contain exactly what is needed to run the editor -- any files now in "static", any html files, any js files.
Whee!
Don't miss mini-require.js in build_support

This was when sinopia_editor had BFE code active;  closing for now as we are testing out of builds dir for React work.


Invalid import FLOW_ADDRESS and FLOW_PRIVATE_KEY

tsnd --respawn src/index.ts

[INFO] 01:47:07 ts-node-dev ver. 1.1.1 (using ts-node ver. 9.1.1, typescript ver. 4.1.2)
No Flow account configured.
Did you export FLOW_ADDRESS and FLOW_PRIVATE_KEY?

Can you please elaborate more?
Did you actually export environment variables?
What os/bash do you use?

The doc leaves MUCH to be desired.
It (the doc) "implies" you have to either export the variables (bash) or set the variables (powershell)

Fixed in #82


Erol's attempt at completing the Beginning Git video course

Hi,
this PR represents all work I did to complete the raywenderlich.com Beginning Git video course.

Hey @erolabi—congrats on submitting a PR at the end of the git course, and thank you for your kind words. I hope that you enjoyed the course and that you learnt a lot in doing it.
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam


Write notes for Lecture 19 on Bug Tracking

[ ] Have I learned about modern bug tracking?
[ ] Have I found a modern bug tracking tool?
[ ] Have I learned a modern bug tracking tool?
[ ] Are the notes written for students?
[ ] Are the notes uploaded to GitHub?
[ ] Are the slides written ready to present to students?
[ ] Are the slides uploaded to GitHub?

Next action: find information on bug tracking online.


Xode 6.3 beta using Swift v1.2

Hey, today I tried to run my project in Xcode 6.3, with Swift 1.2, and it gave me a lot of Warnings (deprecated stuffs) and errors, which are easily fixed in my case. And I think the code turned out to be better because of that.
But also your calendar gives errors here and there. Mostly where you initialize your classes. So maybe it might not be bad to try to beta before you release your calendar and see if you can optimize your code before that. So when they force the new Xcode your calendar will still work.

I'm not sure how to fix those my self, so until then I revert back to the last non beta version of Xcode:)

I changed all warning and errors Swift v1.2 was suggesting, but it is not backwards compatible. So maybe create two versions? Since I don't know how long we will be able to use the "older" swift.

Can you post those changes? I'm having issues myself.

I forked the repo and implemented some changes to make the library work with swift 1.2 here.  These will likely only be temporary fixes, but it should work until an official update is released.

@wgsomerville, looks like you beat me to it, however I noticed we're both still getting deprecation warnings for the CalendarUnits. Anyone have a fix for that yet?

@wgsomerville @FrancisBaileyH Moving the unit itself to the end. .MonthCalendarUnit becomes .CalendarUnitMonth. Week is the only strange one in that it becomes .CalendarUnitWeekOfYear.

Huh, I thought I had fixed that, let me look at it.  What I had found was that you had to change
NSCalendarUnit.DayCalendarUnit

to
NSCalendarUnit.CalendarUnitDay

for week you have to use week of month or year instead of just week.

@thajcak did you notice any difference between .CalendarUnitWeekOfYear and .CalendarUnitWeekOfMonth?

@wgsomerville Week of Month goes to 4 and resets each month, Week of Year goes to 52/53 and resets each year.
.WeekCalendarUnit maps to the .CalendarUnitWeekOfYear according to the deprecation note so that's what I switched these to.

Ah good call, I'll update my changes.

@thajcak @wgsomerville, great thanks for the insight!

Just an FYI for anyone who uses the changes I made:  because of a naming conflict with an Obj-c selector, I had to change the description() function in CVDate to dateDescription().  Just be aware of that if you use it in your code.

Hello @martjemeyer, @thajcak, @wgsomerville,
Thank you so much in contributing to this issue. I haven't been looking for Swift 1.2 Beta but today it's been finally released with Xcode 6.3. Some changes came so somewhere the code isn't updated to the current language syntax.
I've just pushed the changes to develop branch. Check this commit 8369c659dc0780a6052d44dfa1beb1838086f0ee. Note that develop branch is basically active one so more commits to come.
As for your discussion on NSCalendarUnit constants then Apple engineers simply rejected using outdated Objective-C like naming rules such as NSCalendarUnit.MonthCalendarUnit instead they use NSCalendarUnit.CalendarUnitMonth which is ultimately the same but more Swifty. I guess they started working on migrating NSCalendar foundation stuff into native Swift one.
Major updates this weekend comes! Keep watching.
Regards,
Eugene

I see! I was not aware on accessing the dev branch :)
Thank you for your hard work!

How should CVCalendar be installed in an Xcode 6.3.x project?
Even if I use the commit mentioned above, CVCalendar/CVCalendar/CVCalendarMenuView.swift overrides init() and generates an error.
However, 'CVCalendar Demo'/CVCalendar/CVCalendarMenuView.swift includes the changes to make it work in Swift 1.2.
Whats the intended difference between CVCalendar and CVCalendar Demo.


Debounce queries when typing in the search bar

Right now, we send queries per every keystroke, even if the user continues to type more. Here's an idea:
We debounce the input events, and send a search request when it appears the user has stopped typing. I also feel like this would make our Cypress tests run faster!

@dwhieb Thanks! I'm gonna yoink it :^)

@eddieantonio
I don't think I executed it good enough. I checked on production and typed into the search bar wapamat, it appears to me now all requests are just delayed, not debounced --- we now have 7 simultaneous requests for wapamat.

I'll have a follow up on this, please keep this issue open


No debug telemetry in visual studio 2019 16.4.0 preview 1.0

If you are reporting bug/issue, please provide detailed Repro instructions.
Repro Steps
Setup a new .NET Core 3.0 project in VS2019 16.4.0 P1.0
(.NET Core 2.1/2.2 shows the same behavior)
Add nuget package ApplicationInsights 2.11.4 (tried all version down until 2.6.4).
Use the following code:
        public static void Main()
        {
            Console.WriteLine("Hello World!");

            var telemetry = new TelemetryClient(new TelemetryConfiguration());

            telemetry.TrackTrace("Hello World");

            Console.ReadLine();
        }

Actual Behavior
No debug telemetry.
Expected Behavior
Seeing debug telemetry inside visual studio
Version Info
SDK Version : 2.11.4 (Down to 2.6.4)
.NET Version :	3.0 (Down to 2.1)
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) :
OS : Win 10
Hosting Info (IIS/Azure WebApps/ etc) : Debug mode
Aditional notes
Logging in debug mode actually works when an empty ApplicationInsights.config file is available in the project.

Visual Studio looks for applicationinsights output only for certain type of projects- Asp.Net, Asp.Net Core projects. Not for console apps.

Okay so if this is intended behavior, why does it then work if I add an empty 'ApplicationInsights.config' file?

@woutervs Probably that's how VS integration works. Either way, this is not an SDK bug or issue. Closing this.
@woutervs I will send this issue to VS owners for their attention. (I dont know if they have any place for raising issues).

This is the best way to report a problem for Visual Studio - https://docs.microsoft.com/en-us/visualstudio/ide/feedback-options?view=vs-2019#report-a-problem


type_schema does not register required properties.

I am using the type_schema method to handle when a user doesn't put in a proper variable into a filter. I find that it works for most things, except this one case. Here's an example using the type: value filter that is core to all users.
Here is the policy:
  - name: name
    description: |
      something
    resource: iam-user
    filters:
      - type: value

This policy runs fine, even though key and value are required for this filter to work correctly. However, let's switch it to this:
  - name: name
    description: |
      something
    resource: iam-user
    filters:
      - type: value
      - key: key

Running that policy will correctly produce an error stating that the value property is missing.

in general re validation, one aspect is that we're running into a convenience vs validation issue. the shorthand syntax for value filter is not something we can validate, ie  re shorthand
filters:
  - UserName: joesmoe

we only force folks to the long hand if they want to specify op/value_type/values_from. Validating the short form is also tricky since we don't want to really carry schemas for every resource, and even that wouldn't do since we allow jmespath expressions for keys.
we typically do validate and --dryrun on pull request for config changes.
still that notion of type: value without specifying required key and value smells odd, that should barf on required,  i'll investigate post reinvent.

do you have an example of your type_schema code usage handy, type_schema accepts required key words as well.

we had a few filters/actions that weren't properly registering their schema, which caused some schema ambiguity, thats fixed in trunk which should be significantly tighter on schema validation. note the attribute level checks on resources are not something we're looking to do (the short cut value filters), but we do want to be explicit on all other filters/actions params.
the issue specifically on value filter, is that we have some inherited filters from it, and it causes issues with schema inheritance to use required. so it was disabled, i think for the most part we've taken to doing a fully copy of the schema for inheritance to avoid that. i'll have too look at if we can just enable required=('key', 'value') on the value type filter without causing headaches on extant.

unfortunately for the trivial type: value case, that won't work because it gets treated like the attribute shortcut in absence of other fields. we'll have to get object level checking for that to work, this has potential to seriously increase the size of the generated json schema  (currently 812K)

Hey Kapilt, apologies for not being more responsive on this.
I have another schema that is not working with the required attribute. Here is my schema:
    schema = type_schema(
        'modify-lifecycle',
        required=['delete_objects', 'overwrite'],
        delete_objects={'type': 'integer'},
        overwrite={'type': 'boolean'})

Here is my action:
      - type: modify-lifecycle
        delete_objects: 30

That action will run successfully.

Hey Kapilt, apologies for not being more responsive on this.
I have another schema that is not working with the required attribute. Here is my schema:
    schema = type_schema(
        'modify-lifecycle',
        required=['delete_objects', 'overwrite'],
        delete_objects={'type': 'integer'},
        overwrite={'type': 'boolean'})

Here is my action:
      - type: modify-lifecycle
        delete_objects: 30

That action will run successfully.

what version of custodian is that?

<IP_ADDRESS>


Header Updated

Updated the header where the brand logo was not visible before.
Solves issue #622

you can enhance this About Us page like make some changes to it

remove smit and shift the below text in this place
change the image of the about us page
replace about us vigybag with about us only in a single line and change the text color with the theme color
use the navbar from the index.html file that is better from this one

after make these changes kindly share a screen shot with me so that i can review it

@teeshaa this was my issue how did you made a PR for that , as I can see your issue was related to the header of About page 4 days ago and not related to logo @codervivek5 can you please explain what just happend

@krutikajichkar don't worry....let me check it once I will assign it to you If is eligible for this

@teeshaa you can only make PR only in your issue or if I assign you any issue...this is against the GSSOC polity so I have to close this PR but you can continue with another issue


chore: Remove link locales

Run using the Docs Authoring Pack "Clean Microsoft Links" command

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

Verified the updates; merging.
@nschonni Thank you.


wrong parameter for "All .d.ts files" feature

Instruction under All .d.ts files section of README.md states name parameter should be used:

If you set name parameter to some path ended with **/*.d.ts then dts-bundle load all .d.ts files and generate a bundle.

I was able to enable this feature using main but not name parameter. Shouldn't this be main parameter?

Fixed!


Display only

I'd like to only view the calendar and not allow users to select dates unless in "edit" mode.  Is that possible now?  If not can you please add that ability?
Thanks for a great UI.

You could try adding .disabled(true) to RKViewController, for example:
.sheet(isPresented: self.$singleIsPresented, content: {
            RKViewController(isPresented: self.$singleIsPresented, rkManager: self.rkManager1).disabled(true)})

🤦♂
Yup, that is exaclty what I needed, lol.  I'm such a noob!  Thank you @workingDog !! 👍


Graphics card incompatibility?

Hi,
Unfortunately, my graphics card seems to be incompatible with the great program:
https://bit.ly/43iv1Dk
Or does anyone have an idea where the flickering comes from and what can be done about it?
Best regards and thanks for the help.

Win 11 Pro

Ok. I'll build for you a version of the program using a different graphical renderer, hoping this will solve the problem

Oh ha, that's very nice but also very elaborate.
Am I the only one affected by this error ?

You are not the only one, but it's pretty unusual.
The GUI library I use allows choosing between 2 different renderers (wgpu and glow).
I've already set up a glow-renderer branch for cases like this one.
Here you are the fresh built executable:

sniffnet-1.2.0-x86_64.msi.zip

That is really very nice, thank you very much, I will try it out later....

No problem man, let me know if it works 👍

Amazing!
I'm always glad to help ❤


Deprecated example code, clarification

the non-interactive example returning JSON should not use the deprecated dictionary return
a line of explanatory text for the Trailing Slash example (had to test if this actually worked as I suspected).

Let me know if you prefer to have these kind of unrelated changes in two PRs, for docs I tend to go by file.

Nice! Thanks for that.
No that's no problem, especially not for documentation, since the changes should be self-explanatory anyway.


Coveralls

Measure test coverage and send it to coveralls.io

Changes Unknown when pulling<PHONE_NUMBER>59dc9ff711934d21356f78ac293a71 on coveralls into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>59dc9ff711934d21356f78ac293a71 on coveralls into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>59dc9ff711934d21356f78ac293a71 on coveralls into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>59dc9ff711934d21356f78ac293a71 on coveralls into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>59dc9ff711934d21356f78ac293a71 on coveralls into ** on master**.

Changes Unknown when pulling 4097fdfe35b648b53d96758871465e5c16ed2e2f on coveralls into ** on master**.

Changes Unknown when pulling a0a569a497ae052787dcd308229427a768be38e1 on coveralls into ** on master**.

Changes Unknown when pulling f3dc7e2e022758ae91325f74771f820b549f722e on coveralls into ** on master**.

Changes Unknown when pulling 2a7f23cfe230d1f97f1115fb23b5eb61a18666cc on coveralls into ** on master**.

Changes Unknown when pulling 2a7f23cfe230d1f97f1115fb23b5eb61a18666cc on coveralls into ** on master**.

Changes Unknown when pulling 2a7f23cfe230d1f97f1115fb23b5eb61a18666cc on coveralls into ** on master**.

Changes Unknown when pulling 652613a4fc16126a656eb251b0653fd990f384f3 on coveralls into ** on master**.


Video does not automatically start when using panel in Grafana Playlist

Hello over there!
Indeed a very nice plugin to display a video from YouTube but unfortunately when I added the dashboard with the video plugin to the Grafana Playlist (slide show between dashboards), the video would start only at the very first iteration through the playlist but not anymore. After first iteration I must manually click on the start button on the video.

Hello @CollistaR
Thanks for reporting this issue. It don't think I can find a proper explanation for this behavior. I have created two dashboards in which one plays a video using this plugin. I have added both dashboards to a playlist and start it. I noticed that the video is played once and if it is finished it is never started again unless I start it manually.
Unfortunately I cannot find any explanation for this issue. I have tried to ensure a unique URL is created each time the dashboard is rendered. I have done that by using an iframe with the youtube URL and the $__from parameter. For example: https://www.youtube.com/embed/051wmmDNJnc?si=xff_l8ZBqULg9ooW&controls=0&autoplay=1&&loop=1&id=${__from}` Unfortunately this does not seem to solve the problem.
I took another approach: play an mp4 video from another source which seems to work properly. If you look in the debugger of your browser you'll notice that playing a video makes more requests on google apis than you would expect. I suspect this issue is behavior of youtube api rather than this plugin.


Making the Dropdown UI Work

This PR got slightly out of hand since a lot of cleanup work needed to be done to bring all these pieces together, so my apologies for the monolithic review. It basically breaks into a few major pieces:
First, the resource dictionaries were moved out of their respective handlers and into one central service. Each dictionary was then added into jinja environment globals so that they are available on every page without having to be manually added to each handler. I refactored each handler as necessary to pull these out. I also added a generic "landing" resource dictionary for resources used across the landing page, such as the dropdown menu and search.
Second, I created an admin module with basic list, add, and delete methods for interacting with admin users. I also added tests for each of these. I still need to add tests for the actual database methods, but this allows us to interact with admins outside of the setup flow.
Third, I wrote the actual dropdown UI element and wired it up to all the necessary pieces. Adding an admin is bundled as a dialog along with the dropdown UI dialog. It shows a status message for whether adding the admin was actually successful or not. Clicking the settings button redirects to the settings component on the setup page. We can move that component around if need be and even add it to the landing page if necessary, possibly making it pop up when requested. I'm open to suggestions on this, but for now the link works well. Finally, logging out posts to the logout handle and redirects the user back to the login page.

This change is

Really nice overall!  Just a couple of questions on performance & structure related to the resource_dicts.

Review status: 0 of 23 files reviewed at latest revision, 5 unresolved discussions.

ufo/init.py, line 81 [r1] (raw file):
Hmmm, I am wondering how this might impact performance for every request:
(1) for non-UI, ajax calls, which might not need the resource_dicts, would all these resources_dicts be generated?
(2) for UIs, would all these resources_dicts be necessary?  for example, the landing page doesn't need get_oauth(), get_settings(), etc?  likewise for the setting page.

ufo/services/resource_dicts.py, line 1 [r1] (raw file):
This resource_dicts.py feels kind of bloated and will seem to only grow more so in the future.  How do you feel about breaking this module down by creating a "services/resources" package, and then create individual user_resources.py, proxy_server_resources.py, etc?  So then inside, there would just be one simple get() method?
I would also not have the return type in the module naming, i.e. not use "_dict".
This means that if we really want set_jinja_globals() (but see my comment above on performance first), then you can create a resources_provider.py module and then stuff set_jinja_globals() in there.

ufo/services/resource_dicts.py, line 141 [r1] (raw file):
nit: seem like not using return_type in the naming would be nicer.

ufo/services/resource_dicts.py, line 185 [r1] (raw file):
Should we add some unit tests for all these get methods to make sure the dicts being returned are sane?  Or is it sufficient to just rely on testing these upstream?  i.e. whatever are using these resources are configured / behaves properly?

ufo/services/resource_dicts.py, line 185 [r1] (raw file):
nit: Can "with_add_flow" be called as "has_add_flow"?  So that it's more in sync with the actual key name?
if not has_add_flow:
  proxy_server_resource_dict['hasAddFlow'] = False

Comments from the review on Reviewable.io

Reviewed 23 of 23 files at r1.
Review status: all files reviewed at latest revision, 5 unresolved discussions.

ufo/init.py, line 81 [r1] (raw file):
So for starters, I haven't noticed any impact on performance. Load time is still well under 1 second and hasn't seemed to be any different than usual. I think this is all handled server side which should intelligently not insert anything extra which isn't on the page once the template is rendered. I may be able to switch this to before_first_request so it literally only gets called on the very first request (since you don't need to set the globals multiple times anyway), though I haven't tried that yet. As for your direct questions:
(1) The AJAX calls use flask.response rather than render template, so jinja should not be touched during AJAX, thus no rendering of these resource dictionaries. They should only be rendered on requests that result in templates, which are just /setup and /.
(2) Not every resource dictionary will be necessary on every page, but as mentioned above, the server should handle this intelligently. So far, every page will need the generic landing one in order to handle the dropdown menu and search bar correctly.
The other part to think about here is that these are basically constants, analogous to a JSON file of language-specific text (as they will soon be used this way).

ufo/services/resource_dicts.py, line 1 [r1] (raw file):
I would prefer not to shard this out unless there will be any added functionality by separating them. In fact, I'd like to remove the with/has add flow portion and make that just a property that is set within the template, so these can be more straightforward instead of having separate with/without add flow versions.
I think of them as glorified constants in this use case. However, I cannot actually write them directly as constants, because calling flask.url_for won't work outside of the context of a request (so setting up the constant outside of a function in the module, means that the constant will get initialized whenever any file reads from init.py which reads from this causing a slew of problems). From that perspective, having a handful of files that each just provide one constant seems like overkill.
I could move these back to their respective handler files so we aren't creating new files just for the constants, and then just make this file be the provider that calls set_jinja_globals if that would work? I agree that removing _dict from the name seems fine however.

ufo/services/resource_dicts.py, line 141 [r1] (raw file):
Agreed, will fix tomorrow, just commenting so I know what to do tomorrow.

ufo/services/resource_dicts.py, line 185 [r1] (raw file):
I would think these should be fine without unit tests since they are basically constants, but the UI should still be exercised from a functional test perspective, which would in turn ensure that these are constructed properly. The updates for WebDriver are another TODO of mine, so I will follow up with those shortly.

ufo/services/resource_dicts.py, line 185 [r1] (raw file):
Per my comment above, I'd actually like to remove the with/has add flow portion entirely and make that just a property that is set within the template. So in setup.html for example, in addition to passing proxy_server_resources to the left-icon-container, it would also pass has-add-flow="false" so that logic is separate from the other resources, and only one version of the resource dictionary is necessary. I can still name it "has-add-flow" as you mentioned so it is consistent with a boolean name. Similarly for user resources as well. I'll follow up on this tomorrow when I come back to this PR.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 5 unresolved discussions.

ufo/init.py, line 81 [r1] (raw file):
It seems to me as if @before_request will cause set_jinja_before_request() to be triggered on every request to flask, even if no template rendering is involved.  (though the documentation is not explicitly clear, but that's what the naming implies)
For example, when downloading the chrome policy, the request goes to flask and will cause set_jinja_before_request() to be triggered, even if the no template rendering is involved.  And this is something that we should avoid.  There's gotta be some impact involved.  :)
https://github.com/uProxy/ufo-management-server-flask/blob/99c1907cd54e39d85c21d214263a8e22c45fae2d/ufo/handlers/chrome_policy.py#L75
@before_first_request seems better if these resources are all static.
Let's chat more about this if necessary tomorrow.  Maybe there's some crossed wire that we can clear up.

ufo/services/resource_dicts.py, line 1 [r1] (raw file):
Leaving them here is more preferred than in the handlers.

Comments from the review on Reviewable.io

Reviewed 5 of 8 files at r2.
Review status: 23 of 25 files reviewed at latest revision, 5 unresolved discussions.

ufo/init.py, line 81 [r1] (raw file):
So I verified that before_first_request works as expected and can be substituted for before_request in this case. Since they are now only being set once, the global variables shouldn't adversely impact performance, even if present in the environment on other requests, because they are only exercised when a template is rendered in the response.

ufo/services/resource_provider.py, line 185 [r1] (raw file):
Done. Note that this will look a little funny since boolean properties in Polymer are based on presence. For instance, passing like below:
has-add-flow="false"
will actually set hasAddFlow to true since has-add-flow is present. To set it to false, do not explicitly set anything. To set it to true, set has-add-flow to anything, but preference is for true just for clarity. I've updated the templates as necessary to reflect this.

ufo/services/resource_dicts.py, line 1 [r1] (raw file):
I switched them over to be private functions to more closely align with the use case I'm intending.

ufo/services/resource_dicts.py, line 141 [r1] (raw file):
Done.

Comments from the review on Reviewable.io

Review status: 23 of 25 files reviewed at latest revision, 4 unresolved discussions.

ufo/init.py, line 81 [r1] (raw file):
Awesome!

ufo/init.py, line 84 [r2] (raw file):
Awesome, this is very nice to read here!

ufo/services/resource_provider.py, line 185 [r1] (raw file):
Thanks, noted.  It can be confusing.

ufo/services/resource_provider.py, line 275 [r2] (raw file):
nit: This is really nit-picking (and okay, to take a pass here) on something that's already in place, but looking at this again, it would help the cause of readability here if all these get methods include "resources" in the naming.  Otherwise, at first glance, it seems we are getting chrome policies and then setting it into resources.
ufo.app.jinja_env.globals['policy_resources'] = json.dumps(_get_policy_resources())

Comments from the review on Reviewable.io

Reviewed 3 of 8 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

ufo/services/resource_provider.py, line 275 [r2] (raw file):
Done.

Comments from the review on Reviewable.io


Recreate grizzly

Task
Recreate grizzly.

We ran into some issues while running make create-mc:

Irsa operator needs to have the <cluster-name>-chart-values configmap created in the kind cluster otherwise it won't reconcile
A bug in the deploy-cilium script overwrites the config file instead of appending to it, which breaks the configuration. This leads to the podCIDR and VPC CIDR to overlap


iOS Safari "stuck in fullscreen" - see Galleria homepage

iOS Safari (iPhone, iPad) gets "stuck" in fullscreen mode in some implementations of Twelve.
I'm still trying to pinpoint the cause, but can tell you the Twelve theme on the Galleria homepage currently exhibits the behaviour: http://galleria.aino.se
Fullscreen it on an iPad or iPhone and you shall get stuck, requiring a page reload.
Interestingly, the Twelve demo works fine.

The folio theme has a simmillar issue. The iPhone bugs out on the 'fullscreen_exit' event process while desktop browsers don't.
I've been poking around their code a bit and it seems like it's the self.resize() function on line 1569 that's buggy. Alerts inside that function never make it to Mobile Safari while they work just fine in desktop browsers.


Fix unknown route

This PR essentially adds a 404 page. Previously we weren't handling unknown routes so it would just default to a blank page. As a result, I added a "catch all" route so that all unknown routes default to a 404 page. The 404 page simply displays 404, a brief description as to what happened (we could randomize these messages to add more "spunk" but for now it is fine), and a link to the home page. The styling could use some work, but it gets the job done.

Looks good to me


feat: Add MacDriver

Change list
Add MacDriver for appium-mac-driver https://github.com/appium/appium-for-mac
I simply add MacDriver which has 'Mac' platform.
https://github.com/appium/appium-dotnet-driver/issues/382
Types of changes
What types of changes are you proposing/introducing to .NET client?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] New feature (non-breaking change which adds value to the project)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Documentation

[ ] Have you proposed a file change/ PR with appium to update documentation?

This can be done by navigating to the documentation section on http://appium.io selecting the appropriate command/endpoint and clicking the 'Edit this doc' link to update the C# example
Integration tests

[ ] Have you provided integration tests to pass against the beta version of appium? (for Bugfix or New feature)

Details
Below is an example to run MacDriver. I've marked as ignore to functional test not to run it on CI.
[HTTP] --> POST /wd/hub/session
[HTTP] {"desiredCapabilities":{"deviceName":"Mac","platformName":"Mac"},"capabilities":{"firstMatch":[{"platformName":"Mac"}]}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"deviceName":"Mac","platformName":"Mac"},null,{"firstMatch":[{"platformName":"Mac"}]}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at<PHONE_NUMBER>045 (23:57:01 GMT+0900 (Japan Standard Time))
[Appium] Could not parse W3C capabilities: 'deviceName' can't be blank
[Appium] Trying to fix W3C capabilities by merging them with JSONWP caps
[BaseDriver] The capabilities ["deviceName"] are not standard capabilities and should have an extension prefix
[Appium] Appium v1.15.1 creating new MacDriver (v1.6.0) session
[debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {
[debug] [BaseDriver]   "alwaysMatch": {
[debug] [BaseDriver]     "appium:deviceName": "Mac",
[debug] [BaseDriver]     "platformName": "Mac"
[debug] [BaseDriver]   },
[debug] [BaseDriver]   "firstMatch": [
[debug] [BaseDriver]     {}
[debug] [BaseDriver]   ]
[debug] [BaseDriver] }
[BaseDriver] Session created with session id: 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[MacDriver] Killing any old AppiumForMac
[MacDriver] Successfully cleaned up old Appium4Mac servers
[MacDriver] Spawning AppiumForMac with: undefined
[Appium4Mac] [STDERR] 2019-12-22 23:57:01:197 AppiumForMac[72615:307] HTTPServer: Started HTTP server on port 4622
[debug] [WD Proxy] Matched '/session' to command name 'createSession'
[debug] [WD Proxy] Proxying [POST /session] to [POST http://<IP_ADDRESS>:4622/wd/hub/session] with body: {"desiredCapabilities":{"platformName":"Mac","deviceName":"Mac"}}
[debug] [WD Proxy] Got response with status 200: {"status":0,"sessionId":"P3uafXCI","value":{"locationContextEnabled":false,"webStorageEnabled":false,"browserName":"Mac","platform":"Mac","databaseEnabled":false,"version":"10.14.6","javascriptEnabled":true,"takesScreenshot":true,"nativeEvents":true}}
[WD Proxy] Determined the downstream protocol as 'MJSONWP'
[Appium] New MacDriver session created successfully, session 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3 added to master session list
[debug] [BaseDriver] Event 'newSessionStarted' logged at<PHONE_NUMBER>431 (23:57:01 GMT+0900 (Japan Standard Time))
[debug] [W3C (3b5a5c3c)] Cached the protocol value 'W3C' for the new session 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[debug] [W3C (3b5a5c3c)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"Mac","deviceName":"Mac"}}
[HTTP] <-- POST /wd/hub/session 200 387 ms - 119
[HTTP]
[HTTP] --> POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/timeouts
[HTTP] {"implicit":10000}
[W3C (3b5a5c3c)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/timeouts' to command name 'timeouts'
[debug] [Protocol Converter] Will send the following request bodies to /timeouts: [{"type":"implicit","ms":10000}]
[debug] [WD Proxy] Proxying [POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/timeouts] to [POST http://<IP_ADDRESS>:4622/wd/hub/session/P3uafXCI/timeouts] with body: {"type":"implicit","ms":10000}
[debug] [WD Proxy] Got response with status 200: {"status":0,"sessionId":"P3uafXCI","value":"0"}
[WD Proxy] Replacing sessionId P3uafXCI with 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[HTTP] <-- POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/timeouts 200 18 ms - 64
[HTTP]
[HTTP] --> POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element
[HTTP] {"using":"xpath","value":"/AXApplication[@AXTitle='Dock']/AXList[0]/AXDockItem[@AXTitle='Finder']"}
[W3C (3b5a5c3c)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element' to command name 'findElement'
[debug] [WD Proxy] Proxying [POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element] to [POST http://<IP_ADDRESS>:4622/wd/hub/session/P3uafXCI/element] with body: {"using":"xpath","value":"/AXApplication[@AXTitle='Dock']/AXList[0]/AXDockItem[@AXTitle='Finder']"}
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.483 AppiumForMac[72615:6294968]
[Appium4Mac] [STDERR]
[Appium4Mac] [STDERR]
[Appium4Mac] [STDERR] ************* findAllUsingAbsoluteAXPath: /AXApplication[@AXTitle='Dock']/AXList[0]/AXDockItem[@AXTitle='Finder']
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.483 AppiumForMac[72615:6294968] axPathComponents:(
[Appium4Mac] [STDERR] "AXApplication[@AXTitle='Dock']",
[Appium4Mac] [STDERR] "AXList[0]",
[Appium4Mac] [STDERR] "AXDockItem[@AXTitle='Finder']"
[Appium4Mac] [STDERR] )
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.512 AppiumForMac[72615:6294968] Dock Attributes: (
[Appium4Mac] [STDERR] AXRole,
[Appium4Mac] [STDERR] AXRoleDescription,
[Appium4Mac] [STDERR] AXTitle,
[Appium4Mac] [STDERR] AXChildren,
[Appium4Mac] [STDERR] AXFocusedUIElement,
[Appium4Mac] [STDERR] AXEnhancedUserInterface
[Appium4Mac] [STDERR] )
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.514 AppiumForMac[72615:6294968] Dock AXChildren (
[Appium4Mac] [STDERR] "<PFUIElement: 0x7ffb3b256d10> {\n    AXDescription = \"<null>\";\n    AXHelp = \"\";\n    AXRole = AXList;\n    AXRoleDescription = list;\n    AXSubrole = \"<null>\";\n    AXTitle = \"<null>\";\n}"
[Appium4Mac] [STDERR] )
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.514 AppiumForMac[72615:6294968] Dock AXFocusedUIElement (null)
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.514 AppiumForMac[72615:6294968] Dock AXEnhancedUserInterface 0
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.531 AppiumForMac[72615:6294968]
[Appium4Mac] [STDERR] ************* findAllUsingAbsoluteAXPath matchedNodes:(
[Appium4Mac] [STDERR] "<PFUIElement: 0x7ffaa9d01f70> {\n    AXDescription = \"<null>\";\n    AXHelp = \"\";\n    AXRole = AXDockItem;\n    AXRoleDescription = \"application dock item\";\n    AXSubrole = AXApplicationDockItem;\n    AXTitle = Finder;\n}"
[Appium4Mac] [STDERR] )
[Appium4Mac] [STDERR]
[Appium4Mac] [STDERR]
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.531 AppiumForMac[72615:6294968] AXDockItem: AXRole:AXDockItem
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.531 AppiumForMac[72615:6294968] AXDockItem: AXRoleDescription:application dock item
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.531 AppiumForMac[72615:6294968] AXDockItem: AXSubrole:AXApplicationDockItem
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.531 AppiumForMac[72615:6294968] AXDockItem: AXTitle:Finder
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.532 AppiumForMac[72615:6294968] AXDockItem: AXParent:<PFUIElement: 0x7ffb39c441a0> {
[Appium4Mac] [STDERR] AXDescription = "<null>";
[Appium4Mac] [STDERR] AXHelp = "";
[Appium4Mac] [STDERR] AXRole = AXList;
[Appium4Mac] [STDERR] AXRoleDescription = list;
[Appium4Mac] [STDERR] AXSubrole = "<null>";
[Appium4Mac] [STDERR] AXTitle = "<null>";
[Appium4Mac] [STDERR] }
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.532 AppiumForMac[72615:6294968] AXDockItem: AXChildren:(
[Appium4Mac] [STDERR] )
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.533 AppiumForMac[72615:6294968] AXDockItem: AXPosition:NSPoint: {182.99993896484375, 1200}
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.533 AppiumForMac[72615:6294968] AXDockItem: AXSize:NSSize: {60, 72}
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.533 AppiumForMac[72615:6294968] AXDockItem: AXFrame:NSRect: {{182.99993896484375, 1200}, {60, 72}}
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.534 AppiumForMac[72615:6294968] AXDockItem: AXTopLevelUIElement:<PFUIElement: 0x7ffb39c6e8f0> {
[Appium4Mac] [STDERR] AXDescription = "<null>";
[Appium4Mac] [STDERR] AXHelp = "";
[Appium4Mac] [STDERR] AXRole = AXList;
[Appium4Mac] [STDERR] AXRoleDescription = list;
[Appium4Mac] [STDERR] AXSubrole = "<null>";
[Appium4Mac] [STDERR] AXTitle = "<null>";
[Appium4Mac] [STDERR] }
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.534 AppiumForMac[72615:6294968] AXDockItem: AXSelected:0
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.534 AppiumForMac[72615:6294968] AXDockItem: AXShownMenuUIElement:(null)
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.534 AppiumForMac[72615:6294968] AXDockItem: AXStatusLabel:(null)
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.534 AppiumForMac[72615:6294968] AXDockItem: AXProgressValue:(null)
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.535 AppiumForMac[72615:6294968] AXDockItem: AXURL:file:///System/Library/CoreServices/Finder.app/
[Appium4Mac] [STDERR] 2019-12-22 23:57:01.535 AppiumForMac[72615:6294968] AXDockItem: AXIsApplicationRunning:1
[debug] [WD Proxy] Got response with status 200: {"status":0,"sessionId":"P3uafXCI","value":{"ELEMENT":"1"}}
[WD Proxy] Replacing sessionId P3uafXCI with 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[HTTP] <-- POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element 200 60 ms - 118
[HTTP]
[HTTP] --> POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element/1/click
[HTTP] {}
[W3C (3b5a5c3c)] Driver proxy active, passing request on via HTTP proxy
[debug] [WD Proxy] Matched '/wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element/1/click' to command name 'click'
[debug] [WD Proxy] Proxying [POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element/1/click] to [POST http://<IP_ADDRESS>:4622/wd/hub/session/P3uafXCI/element/1/click] with body: {}
[debug] [WD Proxy] Got response with status 200: {"status":0,"sessionId":"P3uafXCI"}
[WD Proxy] Replacing sessionId P3uafXCI with 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[HTTP] <-- POST /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3/element/1/click 200 21 ms - 65
[HTTP]
[HTTP] --> DELETE /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3
[HTTP] {}
[debug] [W3C (3b5a5c3c)] Calling AppiumDriver.deleteSession() with args: ["3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3"]
[debug] [BaseDriver] Event 'quitSessionRequested' logged at<PHONE_NUMBER>571 (23:57:01 GMT+0900 (Japan Standard Time))
[Appium] Removing session 3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3 from our master session list
[debug] [MacDriver] Deleting AppiumForMac session
[debug] [MacDriver] Deleting AppiumForMac server session
[debug] [WD Proxy] Matched '/' to command name 'deleteSession'
[debug] [WD Proxy] Proxying [DELETE /] to [DELETE http://<IP_ADDRESS>:4622/wd/hub/session/P3uafXCI] with no body
[debug] [WD Proxy] Got response with status 200: {
[debug] [WD Proxy]   "status" : 0,
[debug] [WD Proxy]   "sessionId" : "P3uafXCI"
[debug] [WD Proxy] }
[MacDriver] AppiumForMac exited unexpectedly with code null, signal SIGTERM
[debug] [BaseDriver] Event 'quitSessionFinished' logged at<PHONE_NUMBER>591 (23:57:01 GMT+0900 (Japan Standard Time))
[debug] [W3C (3b5a5c3c)] Received response: null
[debug] [W3C (3b5a5c3c)] But deleting session, so not returning
[debug] [W3C (3b5a5c3c)] Responding to client with driver.deleteSession() result: null
[HTTP] <-- DELETE /wd/hub/session/3b5a5c3c-020d-46e3-ad13-0e5f352bf0d3 200 59 ms - 14
[HTTP]
[HTTP] --> GET /wd/hub/status
[HTTP] {}
[debug] [GENERIC] Calling AppiumDriver.getStatus() with args: []
[debug] [GENERIC] Responding to client with driver.getStatus() result: {"build":{"version":"1.15.1"}}
[HTTP] <-- GET /wd/hub/status 200 1 ms - 68
[HTTP]

@KazuCocoa Also need an entry in the changeling

closed #382


Add downstream to owncloud-ci/chromium

refs https://github.com/owncloud-ci/chromium/pull/1

When https://drone.owncloud.com/owncloud-ci/chromium/4 have been finished we can merge this PR.


rspec: add PathnameUtility module

Codecov Report

Merging #10 (4c5e4ad) into main (a7f68fe) will increase coverage by 1.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   55.70%   56.82%   +1.11%
==========================================
  Files          16       16
  Lines         447      447
==========================================
+ Hits          249      254       +5
+ Misses        198      193       -5

Impacted Files
Coverage Δ

lib/js_dependency/pathname_utility.rb
55.00% <0.00%> (+25.00%)
:arrow_up:

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


Extensions should be stored in $XDG_DATA_HOME

Raycast version: 1.38.2
Description
Currently, extensions are stored in $XDG_CONFIG_HOME / ~/.config/raycast. According to the [XDG basedir spec], this is “the base directory relative to which user-specific configuration files should be stored.” The correct directory to store "user-specific data files" like raycast extensions is $XDG_DATA_HOME / ~/.local/share.
Reporting this here as I don't see any other, more correct way on the homepage.
The current behavior
Extensions are stored in ~/.config/raycast.
The expected behavior
Extensions are stored in ~/.local/share/raycast.

Thanks for raising this issue. Right now we don't have the bandwidth to tackle this issue. It would require migration of the existing files. So far this hasn't popped up or caused any issues. We might pick it up in the future.


IDCOM-2102 Controller support

Cryptid v2 now finally supports controllers. Once we have client docs I will add this there, but example usage is:
Given did:sol:alice, a controller of did:sol:bob:
const cryptid = await Cryptid.buildFromDID(
        "did:sol:bob",
        aliceWallet,
        {  connection: provider.connection }
      ).controlWith("did:sol:alice");

This also works with controller chaining, so if did:sol:carol is a controller of did:sol:alice, you can do:
const cryptid = await Cryptid.buildFromDID(
        "did:sol:bob",
        carolWallet,
        {  connection: provider.connection }
      )
   .controlWith("did:sol:alice")
   .controlWith("did:sol:carol")

As mentioned in the meeting, there is come TODOs left around propose execute tests still having Buffer.from([]), // TODO, support controller chain,


tt_lib.tensor.complex_mul breaks with low PCC [Grayskull]

Describe the bug
tt_lib.tensor.complex_mul operation fails in all test cases on grayskull with low PCC errors.
To Reproduce
Steps to reproduce the behavior:

Checkout branch syrmia/complex-ops
Run unit test test_complex_mul.py  using this command:
pytest tests/tt_eager/python_api_testing/non_working_unit_tests/grayskull/test_complex_mul.py

Expected behavior
There are three test cases presented in the unit test tests/tt_eager/python_api_testing/non_working_unit_tests/grayskull/test_complex_mul.py and they all are expected to fail.

All test cases are breaking with error like this:
Max ATOL Delta: 1621153.375, Max RTOL Delta: inf, PCC: 0.006579242775632272, PCC check failed

Getting Additional info for the operation under test and its behavior
To get additional information and results for different combinations of input shapes, types, layouts and memory configs for which this operation was tested you can also run locally sweeps for tt_lib.tensor.complex_mul and check the results. To do this you should:

Follow the Getting Started page to setup the repo, environment variables and python-env
Activate source build/python_env/bin/activate
Run sweeps by using python tests/tt_eager/python_api_testing/sweep_tests/run_pytorch_test.py -i tests/tt_eager/python_api_testing/sweep_tests/test_configs/ci_sweep_tests/broken_grayskull/pytorch_complex_mul_test.yaml -o ./result-sweeps
After the run is completed all test sweeps results should be available inside specified output directory (in this case ./result-sweeps). There you will find complex_mul_sweep.csv which holds all executed sweeps, among which you can also find the ones that failed and were recreated by the unit test, which you can get by searching unique data_seed field.

@JelenaTosicJtosic and @muthutt Same reason as mentioned here https://github.com/tenstorrent-metal/tt-metal/issues/3559#issuecomment-1871120372


Notice in Php2Xml

Seems like this line doesn't do anything in particular. Can be removed?
https://github.com/intuit/QuickBooks-V3-PHP-SDK/blob/master/src/XSD2PHP/src/com/mikebevz/xsd2php/Php2Xml.php#L268

Fair. Since it is not causing any issues for now, we do not plan on fixing it.

@bsivalingam
It does indeed. Sometimes the array's property is not defined and causes a notice. We use this a lot and our log gets full of it. As you can see further in the code similar array accesses are guarded with isset. That line looks like dead code to me. Is there any particular reason to spam notices by the code that does nothing?


No gap in spacing between Edit Cluster and logged errors

Expected a little gap in between the Edit Cluster and error log on the UI when spinning up a cluster with Cluster Manager.
Seen in rancher/rancher:v2.6-head (e3316c9de7f089c5eef25bf58ff700a0198527c3).

Also, the name of the node and the IP address seem to be off-center. This is especially noticeable after the cluster has finished provisioning:

Navigating to ember is now not supported, only the embedded pages are.

Closing this as its a no fix for Ember UI


Added unicamp e-racing labels

Hi Unicamp Driverless Team,
thank you for starting the Pull Request.
Could you please also update the Documentation page like written in the instructions?
https://github.com/ddavid/fsoco/blob/master/docs/index.md
Thanks!


Audit Configuration docs sentence incomplete

Something missing the sentence from the audit configuration documentation.

NonResourceURLs is a set of URL paths that should be audited. s are allowed, but only as the full, final step in the path. Examples: "/metrics" - Log requests for apiserver metrics "/healthz" - Log all health checks

The docs are generated from upstream source code comments. Some comments have weird syntax that are difficult to parse as markdown. These problems have to be fixed upstream.
In fact, I have proposed a fix to the upstream (https://github.com/kubernetes/kubernetes/pull/110354). The PR has been hanging there for almost 4 weeks, no feedbacks, no reviews, no merge...

/language en


Mldb 1336 Better error message for function arguments

Note that the exception thrown should not specify the function name as it will be added when the exception is caught lower in the call stack.

Lovely!  +1

+1


Rounded Corners

I think rounded corners make this notifications look prettier.
Fix issue#5

Thanks, but this should be optional because is styling, and you can do it in your own project without change the module :smile:


istioctl has a list of unexpected pflags from gateway conformance tests

Created an issue https://github.com/kubernetes-sigs/gateway-api/issues/2841 to track.

The line that adds the flag is https://github.com/istio/istio/blob/master/istioctl/cmd/root.go#L148


Added middleware to receive order number (CRM->PS)

Codecov Report

Merging #150 (f75c7b5) into master (f9a7302) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #150      +/-   ##
============================================
+ Coverage     30.50%   30.61%   +0.10%
- Complexity     2350     2354       +4
============================================
  Files            86       87       +1
  Lines          7326     7337      +11
============================================
+ Hits           2235     2246      +11
  Misses         5091     5091

Impacted Files
Coverage Δ

retailcrm/lib/RetailcrmExport.php
12.72% <100.00%> (-2.07%)
:arrow_down:

retailcrm/lib/api/RetailcrmProxy.php
100.00% <100.00%> (ø)

...ib/api/middleware/RetailcrmReferenceMiddleware.php
100.00% <100.00%> (ø)

retailcrm/retailcrm.php
21.99% <100.00%> (-1.43%)
:arrow_down:

retailcrm/lib/RetailcrmOrderBuilder.php
31.62% <0.00%> (+0.30%)
:arrow_up:

retailcrm/lib/api/RetailcrmApiResponse.php
55.88% <0.00%> (+5.88%)
:arrow_up:

...m/lib/api/middleware/RetailcrmLoggerMiddleware.php
55.55% <0.00%> (+27.77%)
:arrow_up:

Continue to review full report at Codecov.

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


Archive the repository if the project is dead.

Archive the repository if the project is dead.

Yeah, I also noticed this after doing yarn create react-app some-app--template typescript and then running yarn start:
One of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.

babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.

It seems this message was added here. Wonder where they got the information.

CRA has been dead for a long time. Issues were bounced off with some bots marking it as stale or just force closing it without any resolution because thats how they felt doing it.
This repo should be marked as not maintained anymore for sure.
Anyone thinking of creating new project with CRA should reconsider it for sure and use something like Vite instead.

:weary: poor unsuspecting devs.

hi @violet4,
not sure what your point is, could you elaborate?
the project works fine for me. I don't mind if there is not a new release every week. unless it breaks and nobody fixes it, why archive it? maybe some day someone wants to take over maintenance. if we archive before that, the project's death will be a self-fulfilling prophecy.

@pseidemann fresh install 8 vulnerabilities, 6 high

hi @violet4,
just note that these vulnerabilities are probably not very critical, since the code you generate with this "tool" is running in the browser only. so ultimately your browser decides if using your app is safe.

if we archive before that, the project's death will be a self-fulfilling prophecy.

this ticket is titled "Archive the repository if the project is dead." but i personally never made a claim that it should be archived.
i wish CRA were more upfront about its current limitations, especially considering that it's put out by a very large organization (fb/meta) which has many smart developers. it's incredibly disorienting to use a tool by fb/meta with 879 contributors, 1.7k issues, 464 PRs that makes no mention of its current lack of maintenance, which then spits vulnerability messages on a fresh install.

just note that these vulnerabilities are probably not very critical

as a newbie to NPM+React on a work project over a year ago, not realizing there are alternatives to CRA (not even knowing what CRA itself truly is), i reluctantly ignored the messages hoping "these vulnerabilities are probably not very critical," but even now, don't know how i would go about analyzing that claim, besides going through each dependency individually.

so ultimately your browser decides if using your app is safe.

plenty of code "looks safe" from the browser perspective but has vulnerabilities. sure, the browser has XSS protections, but that's only one class of issues that the browser tries to protect against. vulnerabilities can be incredibly complex/nuanced and result in major issues even though the code "looks safe" to execute. every user who browses the web is taking a risk every time they visit a page, click a link, etc. so.. it's 100% the browser's responsibility to protect users? browsers work very hard at security but why should a developer knowingly (or unknowingly, in the case of a newbie CRA user) risk including vulnerabilities in their software?
it sounds like you made a conscious decision to claim willful ignorance at vulnerability warnings, which may be fine for you, your workflow, your project/job type, use case, attack surface, etc.. but why encourage others to do the same or assume it shouldn't matter for others?
if i want to spin up a cute little react project in 10 seconds flat and security doesn't matter as i create the nth todo app, sure i might use CRA, but i want to know the caveats upfront before i begin. otherwise i feel misled and then feel distrust. there's no hint at the current state of the project on the website https://create-react-app.dev/ , in the repo, etc.

it's 100% the browser's responsibility to protect users?

it pretty much is (but obviously cannot do that 100% of the time). the browser cannot trust websites (and your CRA app), otherwise attackers will exploit.
additionally for the same reason, your backend cannot trust clients (browsers/users/attackers).
CRA only creates a static HTML/JS/CSS bundle which will be served to the browser.
if, for any reason, these static files behave malicious inside some browser, your backend is now prepared for that anyway.

the browser has XSS protections

the browser actually doesn't protect against xss. it only protects against cross-origin requests (to some degree).
react has some good xss preventions but you can still write unsafe code with some effort (using innerHTML/dangerouslySetInnerHTML etc.).
xss unfortunately can still happen if all your deps are not vulnerable according to npm. often it is a programming error by the developer.

Not sure if this discussion is relevant. Is the project maintained or not? If not, it would be nice if this was mentioned in the README.


Increase time window for fetching SCP messages from overlay

To increase the time window where our vault clients can fetch SCP messages from the overlay instead of from archive nodes, we will change the MAX_SLOTS_TO_REMEMBER to some higher value (that is still to be defined, but will be noted here once defined).
We need to update this constant to that same value once done.

Of course this is only possible if we query only nodes whose MAX_SLOTS_TO_REMEMBER has this high value.
This depends of course on the configuration parameter defined for the pallet.


Add support for TableGen language

clang-format supports TableGen language. Plz!

I add support for tablegen in this https://github.com/xaverh/vscode-clang-format/pull/163


Update links to examples in README.md

Just noticed they were out of date after navigating to one of them via readme link, and finding out that it was not compiling.

Thanks! I've got a bad habit of forgetting to update these links...


keys of columns are not coming in getJson()

I am working with a table where at the time of initialization there are no data and I am allowing the user to enter data and there is a submit button so once the user clicks on the submit button, I am fetching all the data user entered. But the problem is getJson() doesn't provide me data as key-value pair.
Suppose the user enters data in the 1st and 2nd row then how can I get data as key-value pair? Now if I call getJson() I will be not be getting as required.
@paulhodel @Guillaume-Bo is there any way I can get header title as keys and column value as value? that will be something like {"Car": "Jazz", "Make": "Honda", "Available": "01/01/2019"}

Hi,
In your initialization of columns, did you set name property of column ? it's necessary for construct JSON with name for export JSON (or import)
columns: [{
            type:'text',
            title: 'Car',
            width:'200',
            name:'Car'
        },
        {
            type:'text',
            title: 'Make'
            width:'200',
            name:'Make'
        },
        {
            type:'calendar',
            title: 'Available'
            width:'200',
            name:'Available'
        }],


The Very Superview is not adjusting its frames.

Hi,
I have text field at as most front subview.
I clicked on it, Frames adjusted accordingly.
But the very super View of this text field is not adjusted.
I attached the snapshot also.
Please help.

See the Very super View.  The Green box.
Which is not moved with its Red subview.


fix: bump sc4s/splunk versions

:tada: This PR is included in version 1.8.22 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Replace legacy link syntax with Docusaurus

Several URLs in this doc contain capital letters, causing broken links and redirects
https://help.sumologic.com/docs/manage/users-roles/roles/role-capabilities

fix here https://github.com/SumoLogic/sumologic-documentation/pull/1744


[Automation] - Support for private registries test cases with no cluster level config

Issue:
No issue. Additional coverage for private registries
Problem
Current private registries release validations haven't support for the use cases when the cluster level registry wasn't configure but Rancher has Global set.
Solution
Add new validations for RKE1/RKE2/K3S
Testing
Local test runs
Automated Testing
Provide Jenkins run.

@igomez06


Errors launching micro-services demo in kubernetes

Launching the demo to kubernetes results in a few namespace errors:
the namespace from the provided object "loadtest" does not match the namespace "sock-shop". You must pass '--namespace=loadtest' to perform this operation.
the namespace from the provided object "zipkin" does not match the namespace "sock-shop". You must pass '--namespace=zipkin' to perform this operation.

I'm also getting this. A temporary fix is to extract the zipkin related specifications into a separate .yml file and kubectl applying that after applying the complete-demo.yml.


feat: add typescript

Summary
This PR add built-in types and configuration for typescript. It is also step to prepare for new architecture support (codegen). Changes and types are based on New Arch PR by @yungblud
Why is needed ?
With built-in types we have up to date types on every version and we don't need to install an rely on additional package for types @types/react-native-video. Overall built-in types increase the comfort of both developers and maintainers.
But @types/react-native-video should stay to support older versions of react-native-video
How to test ?

Checkout for branch of PR
Install dependencies
Run yarn build
update dependencies in (basic) example app
Check if types are correctly imported
Example app should build and run
Types for Video component should be available

Great 👍 a lot of minor comments but looks good

sorry @KrzysztofMoch I merge the DRM PR, so there are conflict with this one ...


When could Lucent support Neuron Groups?

The neuron_groups  method is mentioned in Building Blocks Notebooks. Lucid also implements this method. Compared to the current version of lucent, the main difference seems to be the direction function in the Objective class. Does Lucent have plans to implement this method? Thanks for your work.

Hi @RayleighChen thank you for your interest in Lucent and PyTorch!
As of 10 seconds ago, the direction and direction_neuron objectives have been added to Lucent thanks to @ndey96!
I had intended to reproduce the Building Blocks notebook a while ago, but I was thinking about whether we wanted the svelte components in Lucent or just import them from Lucid in the notebook. Then other stuff caught up and I'm sorry to say I forgot about it. Since you asked and now we have direction objectives, I might look into it again but no promises!
(Note: for the svelte components, I think we should just do an import from lucid.scratch.web.svelte in the colab rather than copying them over into Lucent, since they don't seem to have dependencies on tf)
Let me know if you would like to help reproduce the notebook, contributions are always welcome!

Hi, @greentfrapp thank you for your reply. In my opinion, the core of the reproduction in the PyTorch version is the consistency of the performance, not the svelte components. Regarding the neuron_groups method, let me try it first.


Published packages disappear after about a month

Problem: Published snapshots made from mirroring official ubuntu repos stop working after about a month. Clients start getting 404, packages are missing.
Aptly version: 0.9.6, 0.9.7
So I want to create snapshots from public repost to sort of freeze package versions for our organisation and control when things get updated. This way I can always install new machines from our repo and know all things will be the same.
Here is what I do:
aptly mirror create -architectures=i386,amd64 xenial-main http://nl.archive.ubuntu.com/ubuntu/ xenial main
aptly mirror create -architectures=i386,amd64 xenial-universe http://nl.archive.ubuntu.com/ubuntu/ xenial universe
aptly mirror -architectures="i386,amd64" create xenial-updates-main http://nl.archive.ubuntu.com/ubuntu/ xenial-updates main
aptly mirror -architectures="i386,amd64" create xenial-updates-universe http://nl.archive.ubuntu.com/ubuntu/ xenial-updates universe

aptly snapshot create xenial-main-20160811 from mirror xenial-main
aptly snapshot create xenial-universe-20160811 from mirror xenial-universe
aptly snapshot create xenial-updates-main-20160811 from mirror xenial-updates-main
aptly snapshot create xenial-updates-universe-20160811 from mirror xenial-updates-universe

aptly publish snapshot -component=main,universe -distribution=xenial xenial-main-20160811 xenial-universe-20160811 ubuntu
aptly publish snapshot -component=main,universe -distribution=xenial-updates xenial-updates-main-20160811 xenial-updates-universe-20160811 ubuntu

So, after that things work well, I'm installing machines using this repo and preseed but, after about a month clients start throwing error 404, packages are not found.
When I try installing new server its usually failing on adduser, which is probably the first package that's missing and needed buy the installer.
I started looking into the issue
I have these mirrors:
 * [xenial-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial
 * [xenial-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial
 * [xenial-updates-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates
 * [xenial-updates-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates

from which I made these snapshots:
* [xenial-main-20160811]: Snapshot from mirror [xenial-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial
 * [xenial-universe-20160811]: Snapshot from mirror [xenial-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial
 * [xenial-updates-main-20160811]: Snapshot from mirror [xenial-updates-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates
 * [xenial-updates-universe-20160811]: Snapshot from mirror [xenial-updates-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates

and the publishes:
  * ubuntu/xenial [amd64, i386] publishes {main: [xenial-main-20160811]: Snapshot from mirror [xenial-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial}, {universe: [xenial-universe-20160811]: Snapshot from mirror [xenial-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial}
  * ubuntu/xenial-updates [amd64, i386] publishes {main: [xenial-updates-main-20160811]: Snapshot from mirror [xenial-updates-main]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates}, {universe: [xenial-updates-universe-20160811]: Snapshot from mirror [xenial-updates-universe]: http://nl.archive.ubuntu.com/ubuntu/ xenial-updates}

There are missing packages in the public/ dir where things are published, for example
aptly@aptlyhost:~/.aptly$ ls -la public/ubuntu/pool/main/a/adduser/
total 28
drwxr-xr-x   2 aptly aptly  4096 Sep 12 06:44 .
drwxr-xr-x 782 aptly aptly 24576 Jul  6 14:06 ..
aptly@aptlyhost:~/.aptly$

is empty
The official repo from wich I mirror show there should be packages there
http://nl.archive.ubuntu.com/ubuntu/pool/main/a/adduser/
If I open the Packages file for the distro though 'public/ubuntu/dists/xenial/main/binary-amd64/Packages' its listed there:
Package: adduser
Priority: required
Section: admin
Installed-Size: 648
Maintainer: Ubuntu Core Developers<EMAIL_ADDRESS>Original-Maintainer: Debian Adduser Developers<EMAIL_ADDRESS>Architecture: all
Version: 3.113+nmu3ubuntu4
Replaces: manpages-it (<< 0.3.4-2), manpages-pl (<= 20051117-1)
Depends: perl-base (>= 5.6.0), passwd (>= 1:<IP_ADDRESS>-1.1ubuntu6), debconf | debconf-2.0
Suggests: liblocale-gettext-perl, perl-modules, ecryptfs-utils (>= 67-1)
Filename: pool/main/a/adduser/adduser_3.113+nmu3ubuntu4_all.deb
Size: 161698
MD5sum: 36f79d952ced9bde3359b63cf9cf44fb
SHA1: 6a5b8f58e33d5c9a25f79c6da80a64bf104e6268
SHA256: ca6c86cb229082cc22874ed320eac8d128cc91f086fe5687946e7d05758516a3
Description: add and remove users and groups
Description-Md5: 7965b5cd83972a254552a570bcd32c93
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Homepage: http://alioth.debian.org/projects/adduser/
Supported: 5y
Task: minimal
Origin: Ubuntu
Multi-Arch: foreign

The package also exists in the original pool dir
aptly@aptlyhost:~/.aptly$ find pool/  -name \*adduser\*
pool/98/c5/adduser_3.113+nmu3ubuntu3_all.deb
pool/36/f7/adduser_3.113+nmu3ubuntu4_all.deb
aptly@aptlyhost:~/.aptly$

running  find pool/ -links 1 and -links 2 and comparing them shows that most files have only 1 link, meaning they are missing from publish. Some are there tho.
Seems like the hard links from pool to publish are missing.
running
aptly snapshot verify xenial-updates-main-20160811 xenial-updates-universe-20160811 xenial-updates-universe-20160811 xenial-universe-20160811
returns a huge list of missing dependencies - 2399
I've checked all crons on the server several times and can't find anything that could remove links/files. All crons are from standard ubuntu/trusty, nothing custom added.
The only things running on the server is aptly serve, nginx which only serves .aptly/public.
This thing happened several times and every time packages start missing after about a month. The way I fix it is by deleting all publishes/snapshots, updating the mirror and creating snapshots and publishes again.

I thing I found the problem which seems to be ubuntu cron job from package 'apt'. Will check deeper and will close this upon confirmation.
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/937951

So, I think the issue is solved byt the apt config, Im closing.


fix: fix parsing timestamp

(cherry picked from commit 6a8103d10e431a5ef9fe7b0f058765a8a9629682)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.10%. Comparing base (eb93410) to head (1fbd538).

Additional details and impacted files
@@            Coverage Diff             @@
##              3.1     #283      +/-   ##
==========================================
- Coverage   70.15%   70.10%   -0.05%
==========================================
  Files          78       78
  Lines        8360     8360
==========================================
- Hits         5865     5861       -4
- Misses       1890     1896       +6
+ Partials      605      603       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Inaction on Applications to Write Notes

Describe the bug
I’m not the only person this is happening to, but, in my case, I applied to write notes as soon as the feature was opened to the public, and now, over a year later, there has been inaction on the application. Not even a notification/email indicating “you’ve been rejected and here’s why”. I’ve been able to rate notes whenever they appear on my timeline, but not once has it given me the chance to write one.
To Reproduce
Apply at https://twitter.com/i/flow/join-birdwatch. If it works, you are not affected.
If it doesn’t work, congratulations, you are probably in the same boat as me.
A few people I know are in the program indicated they were immediately approved, with no waiting period whatsoever.
Expected behavior
Approval or rejection should happen in a timely manner, not take 1+ year with nothing happening.
If Approval will take a while, it should indicate so when someone attempts to apply, and it should have a mechanism to delete old applications from the backend, as I legitimately believe mine is stuck in some process in the backend.
Environment
I have tried and failed to get my application to push through on both the website and applications on iOS, iPadOS, and macOS, For web, I have attempted Safari and Google Chrome.
Additional context
This isn’t a case of me trying to get into the program and abuse it. I’ve even voted “note helpful” on posts that oppose my political worldview if it’s accurate because I think that the truth matters. Ultimately, my posting of this issue is me being sick and tired of having to reply my equivalent to a community note and legitimately wanting to help the team out.

I just came here to file an identical issue here https://github.com/twitter/communitynotes/issues/302.
But I believe there is a bug with the sign-up form that is causing this, and not inaction by the approval team.


yara: 4.0.1 -> 4.0.5

Motivation for this change
Latest libyara has some new API changes that are necessary to build an app I'm trying to package (imhex).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114562 at 282f0f3a run on x86_64-linux 1

1 package built:

yara

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/tools/security/yara/default.nix:39:3:
   |
39 |   meta = with lib; {
   |   ^

Oof, sorry about that, haven't used nixos in a while :sweat_smile:
So I managed to update it properly, but hit a small bug. It appears that the build breaks when static libraries are disabled (which nixos does automatically). This got fixed in master, but the latest release, 4.0.5, still has the problem. See https://github.com/VirusTotal/yara/commit/52e6866023b9aca26571c78fb8759bc3a51ba6dc. So I added the dontDisableStatic = false; attribute with a comment explaining what's up.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114562 run on x86_64-linux 1

1 package built:

yara

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

yara:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/tools/security/yara/default.nix:53:3:
   |
53 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md


Add gridModel.groupSortFn for custom group sort

Relays to defaultGroupSortCompator, avoid need to use agOptions.
Keep existing default that sorts groups according to their natural order.
Tweak contextMenuFn config handling for symmetry (requires review).
Remove unused/dupe init values on class fields declarations.

Customizing group sort order is pretty common, and we had an example in an app where it was requiring the use of agOptions, which we want to avoid.
See corresponding branch in Toolbox for an example usage in sampleGrid.  The win/lose grouping should sort winners first.
While I was here I wanted to get more symmetry between this new config and the contextMenuFn, but I really was confused by why we had the ctx menu fn setup as we did.  Please review carefully and ensure I did not break anything w.r.t. scope!  Thank you.

@haynesjm42 if you have a chance to look at this I would appreciate it.  Looking to remove another occasional use of agOptions here.

As discussed briefly on the phone just now, I liked this idea and went to implement, but ran into a case right away where our little Toolbox example has multi-level grouping and wants to know what grouped field it is comparing on.   That information is available on the node.
Here is the revised signature I had come up with for the groupSortFn API:
/**
 * @callback GridGroupSortFn - comparator for custom grid group sorting, provided to GridModel.
 * @param {*} groupAVal - first group value to be compared.
 * @param {*} groupBVal - second group value to be compared.
 * @param {GridModel} gridModel - controlling GridModel instance.
 * @param {Object} metadata - additional metadata with raw ag-Grid group nodes.
 * @returns {number} - 0 if group values are equal, <0 if `a` sorts first, >0 if `b` sorts first.
 */

So the nodes are still available - making the Toolbox example code:
groupSortFn: (a, b, gm, {nodeA}) => {
            const groupField = nodeA.field;

            if (a == b) return 0;
            if (groupField == 'winLose') {
                return a == 'Winner' ? -1 : 1;
            } else {
                return a < b ? -1 : 1;
            }
        }

We could bake the field in as the third arg if we wanted - so sort(aVal, bVal, fieldName, gridModel, {nodeA, nodeB})....  Is that starting to push it? It does seem that, if you are supplying a custom group sort, you almost always want to change your sort based on the field, and reading from gridModel is problematic in the multi-level case.

Thanks for the review @haynesjm42 - updated to pass groupField as third arg as suggested, with the gridModel and rowNodes in the final, metadata arg.


bugfix: CoreRightDrawer has some fixed width.

Describe the bug
CoreRightDrawer has a fixed width which needs to be fixed.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Stack Trace
The stack trace of the bug if any.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

The size of drawer has been fixed.


Maybe missing some detection methods

Like:

getInstalledPackages
getInstalledApplications
getPackageUid
java File
etc

Before

After

That's the same as conventional methods & libc


segmentation fault encountered when 'boosting = goss'

How you are using LightGBM?

LightGBM component: Python package
Environment info

Operating System: ubuntu-20.04-desktop-amd64
CPU/GPU model: CPU
C++ compiler version: 9.3.0
CMake version: 3.16.3
Java version: N/A
Python version: 3.8.2
R version: N/A
Other: N/A

LightGBM version or commit hash: 2.3.2
Error message and / or logs

Segmentation fault (core dumped)
Reproducible example(s)

from sklearn.datasets import fetch_california_housing
import lightgbm as lgbm
X, y = fetch_california_housing(return_X_y=True)
param = { 'boosting': 'goss' }
dataset = lgbm.Dataset(X, y)
model = lgbm.train(param, dataset)
Steps to reproduce
I updated lightgbm on my machine today. However, when I set boosting to goss, segmentation fault was encountered. Setting boosting to gbdt worked well.

fixed in f155379c1fe4e53d5d1c7fd195987a8d3aec4331

thank you for your quick fix @guolinke
I tested but still failed:
[LightGBM] [Fatal] Check failed: (best_split_info.left_count) > (0) at /home/fengxh/Downloads/LightGBM/src/treelearner/serial_tree_learner.cpp, line 622 .
Any idea how i can avoid it?

@fengxh0628 can you provide a reproduce example for this case? thanks

Just a simple case:
from sklearn.datasets import fetch_california_housing
import lightgbm as lgbm

X, y = fetch_california_housing(return_X_y=True)
param = { 'boosting': 'goss' }
dataset = lgbm.Dataset(X, y)
model = lgbm.train(param, dataset)

Thanks.

@fengxh0628 can you try the fix in #3077 ?

@fengxh0628 can you try the fix in #3077 ?

It worked well. Thanks.


[904] Add support for token auth

@pandastream would be really nice to get this in... would love to use tokens instead (especially since they've been supported by your API for 8+ months)

@courtsimas take a look at Telestream Cloud gem which is the newer version of panda_gem. We have added this feature to our backlog.

@ucatunit since that gem doesn't have the token authentication in there either, but as you said, has it in the backlog, is that the preferred gem for interfacing with telestream going forward instead of the panda gem?


Make rules testing work again on the CI

Description
For an unknown reason, the CI cannot test Firestore rules anymore. They run perfectly fine on my machine, but the CI apparently doesn't like them anymore - note: none of the logic actually changed, except that the models were moved in a new repository. I'm suspecting that some new version of firebase-tools or sth like that is making this impossible on a Linux runner? We would need to have further investigation.
Reproduction
Remove the TestFlags.includeRules flag or set it to true manually and then run the CI tests.
Expected behavior
They pass without causing crashes.
Additional context
No response
Code of Conduct

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

Context: https://github.com/nodejs/node/issues/54521


Move comment widget to task panel

Problem
The comment window doesn't belong to the table but to the task panel.
The previews displayed in the task panel were not the most recent ones.
Due to recent dark mode integration, tooltips were not readable anymore.
Solution
The widget associated to the comment window has been moved to the task panel.
The displayed preview is now the one with the most recent update.
Global aspects of tooltips have been changed. The problem still persists for now on buttons.

I merge the request. Please think about refactoring the date module in a future PR.


Explicitly integrate variables which appear nowhere else on the rhs

Description
This change moves variables from the model which do not appear on the right hand side to the variables dictionary with a pybamm.ExplicitTimeIntegral wrapper. When called by the solution object, the pybamm.ExplicitTimeIntegral integrates the variable (which can be easily explicitly calculated from the solution object).
Variables are only moved if all of the following is true

the variable in question does not appear in the calculation of any other variable in the algebraic equations, the rhs, or the boundary conditions
the variable does not appear in y_slices (needed for experiments in the case that the variable is used in one experiment step and not others).
the variable is 0 dimensional (len(var.domains)==0)
the variable has not already been discretized.
there is at least one more variable on the rhs

Issue #2240 provides a brief overview of the impetus for the PR, but the main point is that in the case where the model has a rest step, not doing this results in a singular Jacobian matrix (due to Discharge capacity [A.h], which can cause slowdowns and failures in some solvers.
Fixes #2240
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[x] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Just had a thought, it might be worth special-casing the case where the rhs is Scalar(0), and in that case simply replacing the variable with its initial condition (instead of the ExplicitTimeIntegral)

@all-contributors add @abillscmu for code


Feature Request: Admin Panel upload image?

Right now it seems I have to just write a .js|.ts file to connect to the client and upload a file to a particular record.
Can we get a drag / drop  or file select in the Admin panel?

I'm not sure that I understand what do you mean.
You can upload a file from the Admin UI just fine (drag&drop is not supported at the moment, but I've added it in my todo to eventually consider it for a future release).
Note that you'll not see the "Upload file" btn if you've reached your file field "Max select" limit (removing the file, aka. clicking on the "X" btn, should show the upload btn again).

I'll consider making the upload btn disabled with a tooltip instead of hiding it for the next release, so that it is more clear.

Huh, strange. I could seem to see that option when in the admin panel. I'll try again. Sorry for the inconvenience 😅
While I got you here, however, do you have a good demo / template for docker / hosting?

I could seem to see that option when in the admin panel.

This is most likely because your record has already reached your file field "Max select" limit. As mentioned in the previous, I'll disable the button instead of hiding it and will add a tooltip to make the file upload a little more user friendly.

do you have a good demo / template for docker / hosting?

You can find an example Dockerfile setup in https://pocketbase.io/docs/going-to-production/#using-docker. The PocketBase binary is completely portable since it is statically linked (aka. there are no external dependencies) and usually the process is just:

download and extract the archive for your platform from the releases page
start the executable


Power Apps License Calculator

[ ] Bug fix?
[x ] New sample?
[ ] Related issues: fixes #X, partially #Y, mentioned in #Z
[ ] Needs API permissions?
[ ] Has other prerequisites? (E.g. requires a list, document library, etc.)

Checklist

[x ] My pull request affects only ONE sample.
[x] I have updated the README file.
[x] My README has at least one static high-resolution screenshot (i.e. not a GIF)
[x] My README contains complete setup instructions, including pre-requisites and permissions required

@Katerina-Chernevskaya thank you, I'm glad you like it :) and thank you for correcting the readme :) best,
Kinga


Pull req.

Pull Request Description

Type of Change

[ ] Breaking Change: Added new code that will cause some or all of the existing codebase to no longer work.
[ ] Bugfix: Added new code that fixes an identified bug and does not break the current codebase.
[ ] Documentation: Updated files that do not affect the current codebase or program logic.
[ ] Hotfix: Emergency update made to production ready code.
[x] New Feature: Added new code and unit tests that does not break the current codebase.
[ ] Refactor: Improvements made to the existing codebase but does not add new features.
[ ] Security: Addresses security vulnerabilities, updating vulnerable code, updating vulnerable dependencies or removal of secrets that does not break the current codebase.

Related GitHub Issues

Checklist

[x] I have created my change on a new branch (such as bugfix/, documentation/ or feature/)
[ ] My code conforms to the style guidelines of this project.
[ ] I have run all linting and formatting scripts against my new code.
[ ] I have added comments to my code (where applicable).
[ ] I have updated all documentation files (such as README.md) of my changes.
[ ] I have added working unit tests for my new feature.
[ ] All existing unit tests work.
[ ] I have not committed any secrets.
[ ] I have added all related GitHub issues to this Pull Request.
[ ] I have completed all steps as part of this checklist.

Good work Sungchur and thank you for your contribution!
I had to close your PR as it is deleting code that is required and your PR does not include unit tests.
See #57 of the PR that I created that includes the code and unit tests for converting Celsius to Kelvin.


New cluster chooser popup

This PR adds a new cluster title button that is narrower, more aligned to the right, and shows a new chooser that's a popup.
There are Storybook stories showing the different cases.
How to test:

[ ] Check all cases in the storybook
[ ] Check that moving between different clusters works
[ ] Check that on small screens, the popup shows at the middle of the screen

fixes #1269

It's invisible in dark mode theme.

I expected to use the up + down arrow keys to make a selection from the drop down.