Can we shutdown Kafka Connect after Restore has finished?

I still think backup should also be just like a snapshot of data, thus once the snapshot is complete the backup process would exit. Just as I mentioned in #52 (please see last added comment for use-case/reasoning).
To add -- RDBMS can also be seen as a continuous stream of data (stored in relational form), but nevertheless it allows for a momentary snapshot of data via backup tools, which is considered pretty normal there, why should it be different in case of Kafka.
There are other tools that provide "continuous backup" via replication to another cluster. That does not satisfy all use cases, I think that is where this tool could be useful -- allow for momentary snapshots of data disregarding any new messages arriving after the backup has started (same as RDBMS backup would work).

This issue is for the restore procedure as there is a clear path how to stop it. See my comments in #52 for doing snapshot backups ;)

This issue is fixed with #56. See #52 for the backup-side


Shorter URLs

Currently URLs look something like this:
https://inspector.pypi.io/project/pip/22.1/packages/f3/77/23152f90de45957b59591c34dcb39b78194eb67d088d4f8799e9aa9726c4/pip-22.1-py3-none-any.whl/pip/_internal/models/format_control.py

That's pretty long!  Obviously this is done because that gives enough information to fetch the URL from files.pythonhosted.org, but it might be nice to use shorter URLs, and query PyPI to get the long URL for the file distribution?
We could go as simple as:
https://inspector.pypi.io/file/pip/pip-22.1-py3-none-any.whl/pip/_internal/models/format_control.py

That's enough information to know the project name (since sdists don't have a well formed name) and the filename (which we can then look up on PyPI's /simple/<project>/ page), and get the long URL.
We could even go a bit simpler, and do:
https://inspector.pypi.io/file/pip-22.1-py3-none-any.whl/pip/_internal/models/format_control.py

Note all this embeds is the filename, we would need a way to look up the URL given nothing but the filename, but filenames are unique on PyPI, so we could just have a route on PyPI that does a redirect of filename to pythonhosted.org and does that look up for us.
The main thing we'd lose is that these links would then "die" if the file is removed from PyPI but still exists in files.pythonhosted.org. Maybe with https://github.com/pypi/inspector/issues/5 we could store the filename => file url mapping as we load them, which would mean they would continue to work in the future.
Alternatively, maybe still support the long URLs, and have a button to turn the short url into a permalink (think how github does).
Alternatively, maybe this is a silly idea and we should just stick with the long URLs :)

Note all this embeds is the filename, we would need a way to look up the URL given nothing but the filename, but filenames are unique on PyPI, so we could just have a route on PyPI that does a redirect of filename to pythonhosted.org and does that look up for us.

Yeah, this is why I did this, so that these links continue to work after the project is taken down, without having to make changes to PyPI.


Add tests listener

Requires #10
Closes #12

Coverage increased (+48.5%) to 98.095% when pulling 6e465dc26f3d36c553a3e1ac5b3b7760d4ee0d90 on add_tests_listener into f4f2efb1e97961500391d900e1a711b7d32d8362 on master.


feat: customize keep-alive-interval for ssh-tunnel

New param for customize keep-alive-interval for ssh-tunnel, for example when using stricter configured ssh.
@Fabio286 What is your preference for displaying the (longer) label of keep-alive-interval?

Maybe i should also move it to another position (under port?)

Hi Christian,
i think a good solution could be change the size of columns to col-5 and col-7, also in other tabs. This modification would also be useful with all those languages with long words or sentences.

Speaking of field position, I think under the field "Passphrase" is the best choice.

Sorry for the delay. Changed the class-definition now to col-5 and col-7. :slightly_smiling_face:

I was able to find some time and fix the things that were missing!
I will merge on develop branch. Are you able to test that everything works well?


heroicons version 2

About 2-3 months ago, it released the second version of heroicons, but you still use the icons of the first version on your site. I have listed the icons that need to be changed.
Documentation
https://www.tremor.so/docs/components/dropdown
❌ import { CubeIcon, CubeTransparentIcon } from "@heroicons/react/solid";
✅ import { CubeIcon, CubeTransparentIcon  } from "@heroicons/react/24/solid";
https://www.tremor.so/docs/components/icons
❌ import { MailIcon } from "@heroicons/react/solid";
✅ import { EnvelopeIcon  } from "@heroicons/react/24/solid";
❌ import { HandIcon } from "@heroicons/react/outline";
✅ import { HandRaisedIcon  } from "@heroicons/react/24/outline";
❌ import { CashIcon } from "@heroicons/react/outline";
✅ import { BanknotesIcon  } from "@heroicons/react/24/outline";
https://www.tremor.so/docs/components/select
❌ import { CalculatorIcon } from "@heroicons/react/outline";
✅ import { CalculatorIcon  } from "@heroicons/react/24/outline";
https://www.tremor.so/docs/components/table
❌ import { StatusOnlineIcon } from "@heroicons/react/outline";
✅ import { SignalIcon  } from "@heroicons/react/24/outline";
https://www.tremor.so/docs/components/toggles
❌ import { CheckIcon, CollectionIcon, ReceiptRefundIcon } from "@heroicons/react/outline";
✅ import { CheckIcon, RectangleStackIcon, ReceiptRefundIcon   } from "@heroicons/react/24/outline";
https://www.tremor.so/docs/layout/block
❌ import { SwitchHorizontalIcon } from '@heroicons/react/solid';
✅ import { ArrowsRightLeftIcon   } from "@heroicons/react/24/solid";
https://www.tremor.so/blocks/landing-zone
❌ import {  CogIcon,  ShieldExclamationIcon,  CheckCircleIcon,  ArrowNarrowRightIcon,} from '@heroicons/react/solid';
✅ import {  CogIcon,  ShieldExclamationIcon,  CheckCircleIcon,  ArrowLongRightIcon,} from '@heroicons/react/24/solid';
❌ import {  ShoppingBagIcon,  CashIcon,  UsersIcon,  ShoppingCartIcon,  ArrowNarrowRightIcon,} from '@heroicons/react/solid';
✅ import {  ShoppingBagIcon,  BanknotesIcon,  UsersIcon,  ShoppingCartIcon,  ArrowLongRightIcon} from '@heroicons/react/24/solid';
❌ import { ArrowNarrowRightIcon } from '@heroicons/react/solid';
✅ import { ArrowLongRightIcon } from '@heroicons/react/24/solid';
❌ import { ArrowCircleRightIcon,  ArrowCircleUpIcon,  ArrowCircleDownIcon,  ArrowNarrowRightIcon } from '@heroicons/react/solid';
✅ import { ArrowRightCircleIcon,  ArrowUpCircleIcon,  ArrowDownCircleIcon,  ArrowLongRightIcon } from '@heroicons/react/24/solid';
❌ import { CashIcon, ChatAlt2Icon, SupportIcon, UsersIcon, InformationCircleIcon, ArrowNarrowRightIcon } from '@heroicons/react/solid';
✅ import { BanknotesIcon, ChatBubbleLeftRightIcon, LifebuoyIcon, UsersIcon, InformationCircleIcon, ArrowLongRightIcon } from '@heroicons/react/24/solid';
https://www.tremor.so/blocks/charts
❌ import { CheckCircleIcon } from '@heroicons/react/solid';
✅ import { CheckCircleIcon } from '@heroicons/react/24/solid';
https://www.tremor.so/blocks/kpi-cards
❌ import { CashIcon, TicketIcon, UserGroupIcon } from '@heroicons/react/solid';
✅ import { BanknotesIcon, TicketIcon, UserGroupIcon } from '@heroicons/react/24/solid';
❌ import { TrendingUpIcon, TrendingDownIcon, ArrowNarrowRightIcon } from '@heroicons/react/solid';
✅ import { ArrowTrendingUpIcon, ArrowTrendingDownIcon, ArrowLongRightIcon } from '@heroicons/react/24/solid';
❌ import { ArrowCircleDownIcon, CogIcon, MinusCircleIcon, CheckCircleIcon } from '@heroicons/react/solid';
✅ import { ArrowDownCircleIcon, CogIcon, MinusCircleIcon, CheckCircleIcon } from '@heroicons/react/24/solid';
❌ import { BriefcaseIcon, DesktopComputerIcon, ShieldExclamationIcon, ShoppingBagIcon, ArrowNarrowRightIcon, LightningBoltIcon, HomeIcon, TruckIcon } from '@heroicons/react/solid';
✅ import { BriefcaseIcon, ComputerDesktopIcon, ShieldExclamationIcon, ShoppingBagIcon, ArrowLongRightIcon, BoltIcon, HomeIcon, TruckIcon } from '@heroicons/react/24/solid';

Heya @Mrahmani71 thank you for taking the time to write this together. We currently, use the old version on purpose because in the 2.0 Version they do not have all the icons from 1.0.6 e.g. the clipboard icons. We will update to 2.0 as soon as the 2.0 version includes all the new icons. :)


Module not found: 'child_process' - fail to spawn?

Failed to compile.
Error in ./~/xmlhttprequest/lib/XMLHttpRequest.js Module not found: 'child_process' in /react-d3-bubblechart/node_modules/xmlhttprequest/lib @ ./~/xmlhttprequest/lib/XMLHttpRequest.js 15:12-36
pkg fails to spawn?

This issue has the solution:https://github.com/d3/d3-request/issues/24
Reverting to d3 version 4.10.0 works wonders 💯


Fix/linux listen devices flag

This PR add logic when passing -l flag with command line on linux/darwin:
./albiondata-client -debug -l "enp6s0,notexist"
❯ ./albiondata-client -debug -l "enp6s0,notexist"
INFO[2024-06-29T13:38:05+02:00] Starting Albion Data Client, version:
INFO[2024-06-29T13:38:05+02:00] This is a third-party application and is in no way affiliated with Sandbox Interactive or Albion Online.
INFO[2024-06-29T13:38:05+02:00] Additional parameters can listed by calling this file with the -h parameter.
INFO[2024-06-29T13:38:05+02:00] Watching Albion
DEBU[2024-06-29T13:38:05+02:00] Interface with name: notexist not found, removing from list ...
DEBU[2024-06-29T13:38:05+02:00] Will listen to these devices: [enp6s0]
DEBU[2024-06-29T13:38:05+02:00] Starting listener (online: enp6s0:5056)
[...]

Tested on Linux 6.9.1-arch1-2, not tested on darwin

These changes break the windows build.

I tried to fix it. I don't have any windows OS here, please tell me if it fix the windows build

Ok it builds on my github-workflow using your test-build.yml file


Chapter for CI using CI cloud services

Chapter on Generic project using CI cloud services
Chapter on Java on HCP using CI cloud services


updated servers/details for multiple interfaces

What does this PR (Pull Request) do?

[x] This PR fixes #4613  is not related to any Issue

Which Traffic Control components are affected by this PR?

Documentation
Traffic Ops

What is the best way to verify this PR?

Verify that the unit test run successfully
Verify that the API tests run successfully for v1, v2, and v3
Verify that /api/3.0/servers/details has the correct updated formatting for interfaces
Verify that /api/2.0/servers/details and /api/1.5/servers/details still have the old formatting
If this is a bug fix, what versions of Traffic Control are affected?

The following criteria are ALL met by this PR

[x] This PR includes tests
[x] This PR includes documentation
[x] This PR includes an update to CHANGELOG.md
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

This has to wait for the migration to be in first, then probably gonna need to rebase.


Process files

I want to create HTML file, but does not respand .
I tried all attempts without interest, nothing works I do not know why.

I hope to find an answer and a solution as soon as
Thanks in advance

Could you just open the developer tools (Debug > Show Developer Tools) and copy the contents you see in the Console tab?

Does not respond to any command :(

Do you have any extensions installed? Try restarting without extensions (Recharger sans les extensions)

but I uninstalled and then installed the program but no response

Uninstalling and re-installing Brackets may not remove the extensions. See article on how to clear your cache, but instead of deleting cef_data folder, delete the entire Brackets (parent) folder to also delete extensions.

@rayoujines Were you able to resolve this after deleting the brackets folder from %appdata%?

Closing inactive thread.
Try out deleting %appdata%/brackets folder as suggested.
@rayoujines feel free to reopen this is you are still facing the issue.


Documentation car call names and maps call names

In all of the examples given it has only the default exemple. It is very hard find the way to change that default cars and maps with out know the names used from the coders inside the jsons.
Exemple: List of levels that I can call in the scenario object
beamng = BeamNGpy('localhost', 64256, home="path/tech", user=r"./userpath")
beamng.open()

# What are the others options?
scenario = Scenario('industrial_site', 'driver_comfort')

careful = Vehicle('careful', model='T-Series', license='CAREFUL', color='Green')
# aggressive = Vehicle('aggressive', model='T-Series', license='AGGRO', color='Red')

About the maps:
https://documentation.beamng.com/official_content/levels/
We have all names of region and car, but not in the way that we shoud call.
About the cars:
https://documentation.beamng.com/official_content/vehicles/
Same is happening here, what should I use to call a different car?

Hi, to get all the level names, you use the get_levels function:
print(beamng.scenario.get_levels())

To get all vehicle names, you use the vehicles.get_available() function:
print(beamng.vehicles.get_available())

You can learn more about the API in the documentation.


Application not working.

Xiaomi Redmi Note 9 Pro, MIUI 12.5.3, Anndroid 11.
I install the application, I issue all the permissions and the menu does not change.

#40


FFmpeg version detected () is too old.  (Require at least 57.48.101 for   sound).  Deactivating

Describe the bug
CMake thinks libavcodec is old even though the latest version of ffmpeg is present.
Trying to do a compile on windows with ffmpeg installed using vcpkg.  Getting the following error abount it not finding avcodec version properly.  Looks almost identical to an older bug #8186, so this might be a regression bug.
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/FreeRDP/FreeRDP.git
Try to compile with the following options:

cmake -G "Visual Studio 17 2022" -A x64 `
    -DCMAKE_INSTALL_PREFIX="C:/Program Files/FreeRDP" `
    -DWITH_CLIENT=ON `
    -DWITH_SERVER=ON `
    -DWITH_CHANNELS=ON `
    -DCHANNEL_URBDRC=ON `
    -DWITH_DIRECTX=ON `
    -DWITH_OPENSSL=ON `
    -DWITH_ZLIB=ON `
    -DWITH_DSP_FFMPEG=ON `
    -DWITH_FFMPEG=ON `
    -DWITH_JPEG=ON `
    -DWITH_OPENH264=ON `
    -DWITH_OPUS=ON `
    -DWITH_PCAP=ON `
    -DBUILD_TESTING=OFF `
    -DWITH_MANPAGES=ON `
    -DDOCBOOKXSL_DIR="$docbookXslDir" `
    -DCMAKE_TOOLCHAIN_FILE="$vcpkgDir\scripts\buildsystems\vcpkg.cmake" `
    ../src

Expected behavior
CMake correctly detects libavcodec version
Screenshots
  FFmpeg version detected () is too old.  (Require at least 57.48.101 for
  sound).  Deactivating

Application details

FreeRDP version (master)

Environment:

OS: Windows
Version: Windows 11
Architecture: x86_64

Additional context
FFmpeg was installed using:
vcpkg install ffmpeg:x64-windows

so:

which version do you have installed now?
a little bit more from the configuration log might help ;)

ok, just tested this with a custom build:

Current version 7.0.2 installed
detect the whole thing with our script in https://github.com/FreeRDP/FreeRDP/blob/master/cmake/FindFFmpeg.cmake
everything working fine, AVCODEC_VERSION is filled with appropriate values.

so this smells like a caching issue/broken build you´re using?
closing until we receive evidence it is a bug in our detection script.

.\vcpkg install ffmpeg
Computing installation plan...
The following packages are already installed:
<EMAIL_ADDRESS>

Not sure why this was closed, but I didn't realize vcpkg had a freerdp build already.  I'll use that for now, but it goes back to 3.4.0.  I think something still broke here...

@bj-mitchell no.
the script detects fine is stuff is installed, maybe your vcpkg-ffmpeg is lacking a header file?


refactor(textlint/kernel): use promise instead of bluebird

This PR is for #585 .

@numb86 Thanks! Good!


[Feature Request] Advanced Settings page for picotorrent/libtorrent

Hey dear Viktor,
PicoTorrent Power users will be really happy to have this. :-]
(https://github.com/arvidn/libtorrent/blob/master/src/settings_pack.cpp)

Hi! There is an advanced setting page already - however it only has one setting (Encrypt config file) right now 😄 Is there a specific group of settings you'd like to see? Or every one?

µTorrent style parameter configuration that would be good also.


'${workspaceFolder}' can not be resolved in a multi folder workspace. Scope this variable using ':' and a workspace folder name.

VSCode Version:
OS Version:

Version: 1.44.0-insider
Commit: 0dbae2083aff6ff2190c8e2157be95458915d464
Date: 2020-04-03T05:52:10.484Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0
Steps to Reproduce:

debug a js file
popup an error

below is my workspace config:

{
	"folders": [
		{
			"path": "/Users/xxx/Desktop/repo/work"
		},
		{
			"path": "/Users/xxx/Desktop/repo/exec"
		}
	],
	"launch": {
		"configurations": [
			{
				"cwd": "${fileDirname}",
				"name": "LAUNCH",
				"program": "${file}",
				"request": "launch",
				"type": "node"
			}
		]
	},
	"settings": {}
}

Does this issue occur when all extensions are disabled?:  Yes

as before, use my config to debug js file is OK, no popup and work fine. so Is there any change or config I don't know?

Yeah, please try doing what the error is telling you to do. Scope the ${fileDirname} and ${file} with the name of your workspace. So for example

@isidorn  are you sure that you said can work fine?
it doesn't work for me !
i have the same popup error.
I switch to the release version.
yesterday it was OK,today this popup happen again.

Now  there is no way for me to solve this problem. i tried you said, or other . But i can't resolve. it influence my daily debug and develop.


Deploy FOSSA + badge on GraphiQL

We should add the FOSSA scanning badge to the graphiql project.

@brianwarner I'll send an intro to the FOSSA team to help you


Checking out remote branch does not work

Describe the bug
When clicking the checkout button for a remote branch that branch is not correctly checked out. A new local branch is created based on master, not the remote branch.
To Reproduce
Steps to reproduce the behavior:

Create a remote branch with at least two commits that are not in master.
Open the Branches window in the git menu
Click the checkout button on the remote branch created above
Note that changes in the branch are not displayed in the UI
Click Help > Show App Data Folder
Navigate to Insomnia/version-control/git/[repo id]/git
Run git log in that folder

Run git log origin/<branch name>

Expected behavior
When you click the checkout button the local branch is created based on the contents of the remote branch, not master
Desktop (please complete the following information):

OS: Windows 10
Installation Method: windows installer
App Version: 20221.2.1

Additional context
If the remote branch is only 1 commit ahead of master this issue can be resolved by pulling. If the branch is 2 or more commits ahead the pull fails with the following error:

we just recently (like, earlier today) merged the 2nd of two PRs that updated (and fixed) a few things with git-usage.  Are you able to run this same set of steps but locally off of the develop branch?  If you're able but not sure how and the instructions are not working please reach out and I'd be happy to help.

I pulled down 351afde4 and retested it there. Unfortunately, it looks like the problem is still in that version.

looks like this is related to https://github.com/Kong/insomnia/issues/2365
cc: @develohpanda

I am having this same issue. This makes it very difficult for me to use, as I have to manually cherry-pick commits from another branch into the branch that I want to develop on.

Same issue here, it's really difficult to work with Insomnia with such git-related issues...


When response 302 no updating cookies

As a result we get an infinite loop

Solution https://golang.org/pkg/net/http/


Does anyone care about this webpage at all?

Please be more specific about what you think is being neglected here. Also consider making a PR to fix any issues


Modeleditor did not open anymore Version <IP_ADDRESS>

Hi Tolis,
something changed today.
I try to open the Version <IP_ADDRESS>, but since today it did not open anymore.
The config:

The Error:

Seems like the Version is not there anymore.
What can I do, I need this Version for 23.1.6.

the version is here as you probably know https://github.com/eXpandFramework/Reactive.XAF/releases/download/<IP_ADDRESS>/Xpand.XAF.ModelEditor.WinDesktop.zip
what changed is that now the plugin looks for dotnet version e.g. 6,7,8

you can get the version you need, save it in a dir, suffix it with the dotnet version e.g. 6  and use the file://c:\Xpand.XAF.ModelEditor.WinDesktop6.zip notation as the download url.

another option is to download the source and compile the XpandVSIX of the past install it and remember to disable the VS auto update so you do not get the latest plugin version again

I updated all to 23.2.3.x (Devexpress & eXpand) and everything works.
I think the problem occurs cause the XVSIX64 Extension updated automaticly. Is there a way the get/install an old Version?

no there is not, the plugin is only distributed from the VS marketplace your only options are

to disable the VS auto update
To build the source back in the version you are interested and install it manually

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


onClick not fired for Link elements

I try to use onClick for Link elements, but it will work only inside Header and Footer components.
In other components, and layouts it's doesn't work. :(

Maybe it's because phenomic intercepts click event on links :D . See PageContainer component for more information

We should only intercept click in the "dangerousHtml" part. Looks like a bug.
@kuzvac can you provide a bit more code? What Link component are you using?

I use import { Link } from "phenomic/lib/Link"
For example, try to use onClick on Link element inside Layouts, or any components except header and footer (inside header and footer onClick works :))

It's a bit weird since props should be sent to the original react-router Link component https://github.com/MoOx/phenomic/blob/2313c7c59a49fc11afcf2c6b2b16f48a3be2fe28/src/Link/index.js#L18
Will take a deeper look later.

Maybe we should not return true or false here https://github.com/MoOx/phenomic/blob/2313c7c59a49fc11afcf2c6b2b16f48a3be2fe28/src/PageContainer/component.js#L141 and just preventDefault() when we use push in browserHistory? @thangngoc89 any thoughts?

Yeah. That should work.

After digging, this won't be solved the "easy" way. I am preparing a clean fix, that will involves a very tiny change in the layouts (replace the dangerouslySetInnerHTML by a Phenomic BodyContainer call).

@kuzvac the current way to fix this need a small change in your code. See https://github.com/MoOx/phenomic/blob/master/CHANGELOG.md#0122---2016-05-20


Remove yarn installation from frontend Dockerfile

It seems that the node:latest image already includes yarn, which causes an error message when trying to build the container:
> sudo docker build .
Sending build context to Docker daemon  982.5kB
Step 1/4 : FROM node:latest
 ---> 2f1ff44a8bb5
Step 2/4 : RUN npm install -g yarn
 ---> Running in 5183549b5eb0
npm ERR! code EEXIST
npm ERR! syscall symlink
npm ERR! path ../lib/node_modules/yarn/bin/yarn.js
npm ERR! dest /usr/local/bin/yarn
npm ERR! errno -17
npm ERR! EEXIST: file already exists, symlink '../lib/node_modules/yarn/bin/yarn.js' -> '/usr/local/bin/yarn'
npm ERR! File exists: /usr/local/bin/yarn
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-02-04T22_12_42_031Z-debug.log
The command '/bin/sh -c npm install -g yarn' returned a non-zero code: 239

This causes the build to fail. Removing the yarn installation entirely fixes this issue.

Hi, I just tested this and it works nicely with your fix. Thank you for providing it.
Before merging we require you to sign the Contributor License Agreement to ensure that you retain the rights to your submission while granting Mycroft right to use it.

@forslund Signing a CLA seems overkill for such a trivial change. I hereby release my contribution under CC0 (public domain). If that is not sufficient, I don't mind if you close this MR, and remove the line installing yarn independently :slightly_smiling_face:

I understand @Willem3141, it's sort of a line drawing thing, if we allow this then we could allow this little bigger change...so we require it on everything. I'll talk it over with the others and if not OK I'll recreate your PR as you suggested.
In any case huge thanks for flagging and providing a solution.

Thanks for this @Willem3141, We talked it over and I ended up recreating the PR (#25). Thanks for providing the solution.


Flapping behavior on issue management

There seems to be some bug causing the status of other issues to flap between open and closed. See https://github.com/chuckSMASH/pong/issues/2 as an example.
Unable to identify bug in software. Bug potentially exists in wetware of project manager.

Issue is with upstream dependency. Closed WONTFIX.

lol... wtf is an upstream dependency of your brain?

Maintainer's brain is upstream of this repo. See relevant requirements.txt entry. Please resubmit as bug against proper project.


Enable to use jupyter-server2.x

Recently, jupyter-server2 was released.
https://blog.jupyter.org/jupyter-server-2-0-is-released-121ac99e909a
Unfortunately, this extension is preventing pip from upgrading to jupyter-server2.
The extension still looks to work without any serious problems after upgrading to jupyter-server2.
So, I would like you to update the jupyter-server's version requirement.

Thanks for the PR! Happy to accept this, but please sign the CLA first as described here: https://github.com/deshaw/jupyterlab-execute-time/blob/master/CONTRIBUTING.md

@mlucool Hi, I signed the CLA. I would appreciate your confirmation.

I would appreciate your confirmation.

Received thanks!

Thanks again for the PR. This has been released. Please let me know if you have any issues.


Update url for isomorphic-react article

Here's the direct link to the article, as its starting to move below the fold on the home page. (sorry for including the whitespace change, I am using the web-based file editor on github and can't seem to get rid of it)

thanks this is updated! =)


[Friend V2] Friend can speak ($700)

Is your feature request related to a problem? Please describe.
I want to be able to use the speaker of my Friend Programatically.
Describe the solution you'd like
A speaker characteristic should be made, which you can write bytes to it, and play an audio.
Test it by taking the plugin response text, then using 11Labs or deepgram tts, to play that on the device.

Working on this @ hackathon rn

No progress, unassigning.

https://github.com/user-attachments/assets/3aa1b4ad-e9d6-45f0-a729-d743854bcac5
Im gonna wait until the accelerometer PR is done since my main branch has that code on accident and I can't seem to move anything without destroying that branch


100 epoch or 300 epoch, which is correct?

Hi
Thank you for you great work.
I'm trying to reproduce performance on ImageNet.
I have a question on training setting.
In the paper, you mentioned that
Formally it means that we have 100 epochs, but each is 3x longer because of the repeated augmentations. We prefer to refer to this as 300 epochs.
In the code, repeated augment is used by default
https://github.com/facebookresearch/deit/blob/4e91d2588f04954cd7a63f6a3eaeb01cd7127e0b/main.py#L106
But, training epochs is 300 epochs
https://github.com/facebookresearch/deit/blob/4e91d2588f04954cd7a63f6a3eaeb01cd7127e0b/main.py#L34
As I understand, it should be 100 epochs by the paper.
Is there any code that reduces actual training epochs ? or Should I train it for 300 epochs to reproduce the performance ?

Hi @bhheo ,
You have to use 300 epochs with repeated_aug = True. In the code we make sure that the size of an epoch doesn't vary, so we don't see all the dataset images during one epoch with repeated_aug=True. Indeed, we see exactly 1/3 of the dataset images during one epoch. That's why we wrote in the article: Formally it means that we have 100 epochs, but each is 3x longer because of the repeated augmentations. We prefer to refer to this as 300 epochs.
I hope I have answered your question.
Best,
Hugo

I missed this part
https://github.com/facebookresearch/deit/blob/4e91d2588f04954cd7a63f6a3eaeb01cd7127e0b/samplers.py#L57
Thanks for your quick and kind answer.


UI changes to CollaboratorsInitials custom view

Also addressed comment from previous PR to handle change of owner when viewing list of collaborators

Verified that @nyjalusc has signed the CLA. Thanks for the pull request!

+1


fix: update node in ci-cd script and nvm version

Drop node v14 form ci-cd.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix link

closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint-PowerShell/issues/514

@tiburd Please merge this PR. Thanks


[Question] flatpickr 2.0 and browser compatibility

On the updated docs, flatpickr setup can be done via:
new Flatpickr(HTMLElement, [options]);

Since this is an ES6 class, does this mean that flatpickr will be dropping support for some browsers (e.g. IE <= 11)? Or is this something that BabelJS handles?

Hello,
Flatpickr is still dedicated to support IE9+.
As you may have noticed, there are various ways to instantiate Flatpickr.
If you need to support IE < 11, I can suggest two things:

Instantiate using doc.getElementById/getelementsbyclassname
Use an object instead of data attributes to set options ( dataset is not present in IE9/10 and the polyfill is too heavy to include)


typo: Devide -> Device

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

Editorial fix confirmed.


Add CivModCore integration

Kick out all the duplicated stuff and use CMC instead.

It uh, already does this?

Oh, you mean for the database stuff.

No, it's only using CivModCore for the item guis right now.


Dotnet 5 support

It seems that due to dotnet 5 no longer being called dotnet core the target framework parsing is broken.
See https://github.com/stryker-mutator/stryker-net/issues/1369
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at System.String.get_Chars(Int32 index)
at Buildalyzer.Environment.EnvironmentFactory.IsFrameworkTargetFramework(String targetFramework)
at Buildalyzer.Environment.EnvironmentFactory.b__11_0(String x)
at System.Linq.Enumerable.All[TSource](IEnumerable1 source, Func2 predicate)
at Buildalyzer.Environment.EnvironmentFactory.OnlyTargetsFramework(String targetFramework)
at Buildalyzer.Environment.EnvironmentFactory.GetBuildEnvironment(String targetFramework, EnvironmentOptions options)
at Buildalyzer.Environment.EnvironmentFactory.GetBuildEnvironment(String targetFramework)
at Buildalyzer.ProjectAnalyzer.Build(String targetFramework)
at Buildalyzer.ProjectAnalyzer.Build()

Looks like there's actually a couple things going on here. Hopefully #164 resolves issues with identifying .NET 5, but the stack trace also suggests a bug in the code. Here's the code for IsFrameworkTargetFramework(string):
private bool IsFrameworkTargetFramework(string targetFramework) =>
    targetFramework.StartsWith("net", StringComparison.OrdinalIgnoreCase)
        && targetFramework.Length > 3
        && char.IsDigit(targetFramework[4]);

The stack trace suggests it's breaking on targetFramework[4] since that's the only array access. The bug is that we check the array length prior to the access, but I only check if the length is > 3 which would be a maximum index of 3 not 4. So in the case where the length is exactly 4 the maximum index is 3 and this code crashes.
When brings up another question for me - what was the value we were getting here for the target framework that was exactly 4 characters long. I suspect it was "net5" which is interesting in and of itself because the technically correct TFM for .NET 5 is "net5.0". If it had been "net5.0" this code actually would have worked, though for the wrong reasons! It would have checked if the 4th character, a ".", was a digit and failed - and that only would have worked because the other .NET Framework TFMs all have the versions without a ".".
tl;dr: This was a really interesting bug with several things I need to clean up here.

Looks like there's actually a couple things going on here. Hopefully #164 resolves issues with identifying .NET 5, but the stack trace also suggests a bug in the code. Here's the code for IsFrameworkTargetFramework(string):
private bool IsFrameworkTargetFramework(string targetFramework) =>
    targetFramework.StartsWith("net", StringComparison.OrdinalIgnoreCase)
        && targetFramework.Length > 3
        && char.IsDigit(targetFramework[4]);

The stack trace suggests it's breaking on targetFramework[4] since that's the only array access. The bug is that we check the array length prior to the access, but I only check if the length is > 3 which would be a maximum index of 3 not 4. So in the case where the length is exactly 4 the maximum index is 3 and this code crashes.
When brings up another question for me - what was the value we were getting here for the target framework that was exactly 4 characters long. I suspect it was "net5" which is interesting in and of itself because the technically correct TFM for .NET 5 is "net5.0". If it had been "net5.0" this code actually would have worked, though for the wrong reasons! It would have checked if the 4th character, a ".", was a digit and failed - and that only would have worked because the other .NET Framework TFMs all have the versions without a ".".
tl;dr: This was a really interesting bug with several things I need to clean up here.

Nice find, I didn't spot the off-by-one bug 🤦

Nice find, I didn't spot the off-by-one bug 🤦


[New Feature]: Automation to regularly clean-up docs from Elasticsearch

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
We have an ever increasing amount of documents being stored in Elasticsearch that left unchecked, can affect Elasticsearch stability and therefore operations.
Describe the feature request
We'd like automation (a script) that can be run at regular intervals to automatically clean up unnecessary documents in indices that are growing. Unnecessary is determined both by a specific age of a document as well as a specific field within that document. For example, the job-deduped status field of job_status-current index, when the document is over 30 days old. We want to be flexible about modifying the time window and the specific field matching within the script so that OPS can adjust the script over time, but also leave out deleting documents that may aid in debugging down-the-line.
Here are some of the target indices and conditions we know of currently:

Mozart ES

worker_status-current

Document over 30 days old and has status field values: worker-heartbeat

task_status-current

Document over 30 days old and has status field values: task-succeeded or task-received or task-sent

job_status-current

Document over 30 days old and has status field values: job-successful or job-deduped

event_status-current

Document over 30 days old and has status field values: clobber

Metrics

logstash-YYYY.MM.DD

Index over 30 days old

sdswatch-YYYY.MM.DD

Index over 30 days old

GRQ

grq_v2.0_l2_hls_s30

Document over 90 days old

grq_v2.0_l2_hls_l30

Document over 90 days old

grq_v1.0_l3_dswx_hls

Document over 90 days old

What should be the configuration items for the script?

Indices to target
Conditions per index

What should the script return?

List of document IDs of deleted documents

The script should also return the number of deleted documents. Document IDs may not be as useful because they are just random strings. Perhaps it should also keep a running log of "datetime_executed, index, num_doc_deleted" in a text log/CSV file.

@LalaP @niarenaw (and others), I have two recommended ways to encode this feature as a script. Which do you all prefer from an operations perspective?

3 scripts, one for each ES host (Mozart, GRQ, Metrics) that is called without any arguments in the command-line because each script has the delete conditions (specified above) pre-set within the scripts. The conditions can be modified within the script via variables.
1 script that takes command-line arguments for ES host, indices, and a list of conditions to delete by (age of document, key/val matching fields to search docs for)

This is basically a trade-off between simplicity of invocation vs configurability during runtime usage. I am aware that there's already a purge feature within GRQ, so I'd be interested to hear whether that feature already provides the maximum configurability you all need too.
Thoughts?

The script should also return the number of deleted documents. Document IDs may not be as useful because they are just random strings. Perhaps it should also keep a running log of "datetime_executed, index, num_doc_deleted" in a text log/CSV file.

Thanks @philipjyoon. A separate log file would be better for the detailed information. I'm thinking that listing the IDs as a return statement allows this tool to be piped to another that can do further detailed analysis if need be (i.e. count number of deleted docs, double-check they are in fact deleted, etc.).

@niarenaw recommends not specifying ES conditions on the command-line as arguments as they can be highly complex. Also recommends that we can use GRQ for surgical deletes if need be.

@riverma suggest to use yaml del config file(s) for any desired parameters - human readable and version control to track/ diff/debug issues.

A proposed simple script based on @niarenaw and @toandn-jpl feedback.

Resolved.


Implement short expiry keys mechanism for those that need temporary admin access

We have a growing number of Linux-based machines that require administering, and at present are sharing the secrets amongst a small set of people managing the infrastructure.
To ensure that the system remains stable and secure we prefer to grant limited time access to people (and bots/processes) who need machine access for administering them, and keep the master secrets to a very small group of owners.  The 'ownership' group tends to be people who are ultimately responsible for activity on those machines, i.e. through legal contract with the service provider / employer.
Proposal is to implement expiring ssh access as described here
https://linux-audit.com/granting-temporary-access-to-servers-using-signed-ssh-keys/

I've documented how this will work on the wiki.
I'd appreciate comments and scrutiny on the approach before trying it out on our machines.
I did consider having a CA chain for different owners, but figured we can move to that later if required, and for now we can likely live with one owner.

LGTM - Since a user will be in as the admin user and using sudo - are we able in logs to track actually who was working on a machine (via the temp pub key?).

yes, once you login with your signed key the authentication log will show the ID we baked in, i.e. you'll see a line something like

Accepted publickey for admin from <IP_ADDRESS> port 123 ssh2: ECDSA-CERT ID karianna (serial 1) CA ECDSA fingerprint...

When an owner signs the user's key they will use the user's Github id to identify them this way.

Hmm, what about for non linux hosts?  Mac OS X we can probably do the same, not sure about the windows box...

agreed.  MacOS will be fine, but I'm not familiar with best practise for Windows.  Suggestions welcome.

OK, this procedure for Linux-based systems is described in the wiki
Any further comments?

There's a plan in place for this in the security repo.


wrong link

The '[azure-ad-b2c]' link on this page actually goes to 'azure-ad-b2b' on stackoverflow. Just fyi.

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

ID: b77531f5-3bd4-600e-1bca-7f40f9ee479e
Version Independent ID: 4c98db9b-4a2e-4ba4-ba7d-a1e2de9a8745
Content: Support and help options for Azure Identity developers
Content Source: articles/active-directory/develop/developer-support-help-options.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

Updated topic is now live. #please-close


0.9.7

Next update pull request, it will merge when features will be complete. And that most bugs will be fixed. Feel free to comment / post issues about some features you would need, and why, and about bugs detected in some features. (It will not be merged now)

Nobody uses PowerHigh, but it will still be updating. Except a lot less than before

Audio errored. But 0.9.7 releasing (audio will be fixed it <IP_ADDRESS>)

Audio fixed in <IP_ADDRESS>-alpha. Almost everything is like old PowerHigh. Except it's now more modular and reliable.


Registry: Encapsulate page layout (#1823)

Partially addresses #1823. For now, focusing only on the Alternative Schema registry, but if we are OK with the approach, I can do the same for the other registries.
This extracts the boilerplate markdown to a new _includes/alternative-schema-entry.md file, referenced by an {% include %} tag in each collection item.

@MikeRalphson , please have a look when you get a moment.

@MikeRalphson, if you want to allow more flexibility for the contributor to include an extended description of the registry entry, I can think of a couple of ways to do this:

Add a description property that can be multi-line, with markdown.
Instead of having a single alternative-schema-entry.md, break this into alternative-schema-header.md and alternative-schema-footer.md.

The contributed registry entry has to include both of these.
The registry entry can, optionally, include descriptive content with markup between the header and footer.
The footer part might be empty for now, just a placeholder in case we need to add some boilerplate content after the contributed description.

The first option is more like OpenAPI's description properties, and also makes it formally part of the metadata (as YAML front matter). So I think it's a little cleaner. But the second option is OK too.
In either case, we can specify in our contributing guidelines that the description content should not use h1, or maybe h1-h2 headings, so we reserve those for our own header and keep the content hierarchy more uniform.

Generally :+1: to all of this, thanks!. The use of Jekyll includes reduces repetition and promotes more use of features Jekyll provides 'for free'.
That said, I am not in favour of replacing  page.slug with a schemaTypeID for two reasons:

the use of page.slug ensures that the markdown file has been named correctly, this is important because it is the markdown filename / slug which controls what URL the generated page ends up at. And the URLs in a registry should be correct, related to the entries and unchanging.
It reduces consistency between registries if the identifier property is called schemaTypeID in one and extensionTypeID in a another. This makes iterating over all the registries much more complex / brittle.

I think splitting the description into a one-line summary and a description which can contain markdown will be a better move as it retains consistent property names across registries and echoes the OAS even more closely.

Changes were requested some time ago, but the pull request hasn't been updated, so I'm closing. Feel free to open a new pull request, based off the current release, for us to review at any time.


New volume configuration model with first class volumes

The current volume configuration model suffers from the lack of first-class volumes:

If somehow a volume exists on a node but a corresponding application doesn't, flocker-volume will not realize the volume exists, will try to recreate it and then fail.
Multiple volumes are not supported.
It's not possible to move a volume from one application to another.

New config proposal TBD, I suspect it will be somewhat influenced by the 0.3 data management use case, and that this issue will be required for that to happen.

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-697. You are welcome to file additional issues in GitHub if that's easier for you.


No improvement in performance of deeplabv3_257_mv_gpu.tflite on TFLite for GPU

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: MI 5
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the current behavior
I'm trying to run TFLite Model 'deeplabv3_257_mv_gpu.tflite' with GPU delegate on Android  devices.  According to PR for label_image #27464,  I modified the label_image code to support the gpu delegate and removed the code from 205 to 251 lines .
void RunInference(Settings* s) {
  if (!s->model_name.c_str()) {
    LOG(ERROR) << "no model file name\n";
    exit(-1);
  }

  std::unique_ptr<tflite::FlatBufferModel> model;
  std::unique_ptr<tflite::Interpreter> interpreter;
  model = tflite::FlatBufferModel::BuildFromFile(s->model_name.c_str());
  if (!model) {
    LOG(FATAL) << "\nFailed to mmap model " << s->model_name << "\n";
    exit(-1);
  }
  LOG(INFO) << "Loaded model " << s->model_name << "\n";
  model->error_reporter();
  LOG(INFO) << "resolved reporter\n";

  tflite::ops::builtin::BuiltinOpResolver resolver;

  tflite::InterpreterBuilder(*model, resolver)(&interpreter);
  if (!interpreter) {
    LOG(FATAL) << "Failed to construct interpreter\n";
    exit(-1);
  }

  interpreter->UseNNAPI(s->accel);
  interpreter->SetAllowFp16PrecisionForFp32(s->allow_fp16);

  if (s->verbose) {
    LOG(INFO) << "tensors size: " << interpreter->tensors_size() << "\n";
    LOG(INFO) << "nodes size: " << interpreter->nodes_size() << "\n";
    LOG(INFO) << "inputs: " << interpreter->inputs().size() << "\n";
    LOG(INFO) << "input(0) name: " << interpreter->GetInputName(0) << "\n";

    int t_size = interpreter->tensors_size();
    for (int i = 0; i < t_size; i++) {
      if (interpreter->tensor(i)->name)
        LOG(INFO) << i << ": " << interpreter->tensor(i)->name << ", "
                  << interpreter->tensor(i)->bytes << ", "
                  << interpreter->tensor(i)->type << ", "
                  << interpreter->tensor(i)->params.scale << ", "
                  << interpreter->tensor(i)->params.zero_point << "\n";
    }
  }

  if (s->number_of_threads != -1) {
    interpreter->SetNumThreads(s->number_of_threads);
  }

  int image_width = 224;
  int image_height = 224;
  int image_channels = 3;
  std::vector<uint8_t> in = read_bmp(s->input_bmp_name, &image_width,
                                     &image_height, &image_channels, s);

  int input = interpreter->inputs()[0];
  if (s->verbose) LOG(INFO) << "input: " << input << "\n";

  const std::vector<int> inputs = interpreter->inputs();
  const std::vector<int> outputs = interpreter->outputs();

  if (s->verbose) {
    LOG(INFO) << "number of inputs: " << inputs.size() << "\n";
    LOG(INFO) << "number of outputs: " << outputs.size() << "\n";
  }
#if defined(ANDROID) || defined(__ANDROID__)
  TfLiteGpuDelegateOptions kMyOptions = {
      .metadata = nullptr,
      .compile_options =
          {
              .precision_loss_allowed = 0,
              .preferred_gl_object_type = TFLITE_GL_OBJECT_TYPE_FASTEST,
              .dynamic_batch_enabled = 0,
          },
  };
  if (s->allow_fp16) kMyOptions.compile_options.precision_loss_allowed = 1;

  TfLiteDelegate* delegate;
  if (s->gl_backend) {
    delegate = TfLiteGpuDelegateCreate(&kMyOptions);
    if (interpreter->ModifyGraphWithDelegate(delegate) != kTfLiteOk) return;
  } else {
#endif
    if (interpreter->AllocateTensors() != kTfLiteOk) {
      LOG(FATAL) << "Failed to allocate tensors!";
    }
#if defined(ANDROID) || defined(__ANDROID__)
  }
#endif

  if (s->verbose) PrintInterpreterState(interpreter.get());

  // get input dimension from the input tensor metadata
  // assuming one input only
  TfLiteIntArray* dims = interpreter->tensor(input)->dims;
  int wanted_height = dims->data[1];
  int wanted_width = dims->data[2];
  int wanted_channels = dims->data[3];

  switch (interpreter->tensor(input)->type) {
    case kTfLiteFloat32:
      s->input_floating = true;
      resize<float>(interpreter->typed_tensor<float>(input), in.data(),
                    image_height, image_width, image_channels, wanted_height,
                    wanted_width, wanted_channels, s);
      break;
    case kTfLiteUInt8:
      resize<uint8_t>(interpreter->typed_tensor<uint8_t>(input), in.data(),
                      image_height, image_width, image_channels, wanted_height,
                      wanted_width, wanted_channels, s);
      break;
    default:
      LOG(FATAL) << "cannot handle input type "
                 << interpreter->tensor(input)->type << " yet";
      exit(-1);
  }

  profiling::Profiler* profiler = new profiling::Profiler();
  interpreter->SetProfiler(profiler);

  if (s->profiling) profiler->StartProfiling();
  if (s->loop_count > 1)
    for (int i = 0; i < s->number_of_warmup_runs; i++) {
      if (interpreter->Invoke() != kTfLiteOk) {
        LOG(FATAL) << "Failed to invoke tflite!\n";
      }
    }

  struct timeval start_time, stop_time;
  gettimeofday(&start_time, nullptr);
  for (int i = 0; i < s->loop_count; i++) {
    if (interpreter->Invoke() != kTfLiteOk) {
      LOG(FATAL) << "Failed to invoke tflite!\n";
    }
  }
  gettimeofday(&stop_time, nullptr);
  LOG(INFO) << "invoked \n";
  LOG(INFO) << "average time: "
            << (get_us(stop_time) - get_us(start_time)) / (s->loop_count * 1000)
            << " ms \n";
#if 0
  if (s->profiling) {
    profiler->StopProfiling();
    auto profile_events = profiler->GetProfileEvents();
    for (int i = 0; i < profile_events.size(); i++) {
      auto op_index = profile_events[i]->event_metadata;
      const auto node_and_registration =
          interpreter->node_and_registration(op_index);
      const TfLiteRegistration registration = node_and_registration->second;
      PrintProfilingInfo(profile_events[i], op_index, registration);
    }
  }

  const float threshold = 0.001f;

  std::vector<std::pair<float, int>> top_results;

  int output = interpreter->outputs()[0];
  TfLiteIntArray* output_dims = interpreter->tensor(output)->dims;
  // assume output dims to be something like (1, 1, ... ,size)
  auto output_size = output_dims->data[output_dims->size - 1];
  switch (interpreter->tensor(output)->type) {
    case kTfLiteFloat32:
      get_top_n<float>(interpreter->typed_output_tensor<float>(0), output_size,
                       s->number_of_results, threshold, &top_results, true);
      break;
    case kTfLiteUInt8:
      get_top_n<uint8_t>(interpreter->typed_output_tensor<uint8_t>(0),
                         output_size, s->number_of_results, threshold,
                         &top_results, false);
      break;
    default:
      LOG(FATAL) << "cannot handle output type "
                 << interpreter->tensor(input)->type << " yet";
      exit(-1);
  }

  std::vector<string> labels;
  size_t label_count;

  if (ReadLabelsFile(s->labels_file_name, &labels, &label_count) != kTfLiteOk)
    exit(-1);

  for (const auto& result : top_results) {
    const float confidence = result.first;
    const int index = result.second;
    LOG(INFO) << confidence << ": " << index << " " << labels[index] << "\n";
  }
#endif
}

Describe the expected behavior
Version with GPUDelegate is a lot slower (228.445 ms per run vs 132.303 ms) than CPU.
Other info / logs
GPU:
gemini:/data/local/tmp $ ./label_image -g 1 -m deeplabv3_257_mv_gpu.tflite
nnapi error: requires android sdk version to be at least 27
Loaded model deeplabv3_257_mv_gpu.tflite
resolved reporter
INFO: Initialized TensorFlow Lite runtime.
INFO: Created TensorFlow Lite delegate for GPU.
invoked
average time: 228.445 ms

CPU:
gemini:/data/local/tmp $ ./label_image -m deeplabv3_257_mv_gpu.tflite                                   <
nnapi error: requires android sdk version to be at least 27
Loaded model deeplabv3_257_mv_gpu.tflite
resolved reporter
INFO: Initialized TensorFlow Lite runtime.
invoked
average time: 132.303 ms

Watching this

Performance regression on Mali is still being investigated.  We spent a full week, but wasn't able to easily identify the root cause yet.  Especially with Mali showing a higher variance on performance than Adreno where numbers are more stable.  I will update as soon as we have progress.

@impjdi
Is there any good news about Mali now?

@impjdi
Is there any good news about this?

@anneyking @holyhao
Sorry, the engineers in charge don't have cycles this week to investigate.  They may start next week.

any new findings about MALI performance optmization?

Yeah, we have a candidate for the root cause, but are working on a more systematic approach.  We "might" see some improvement by end of year if everything goes well =/

@impjdi I'm super curious about this suspicious root cause. I found some MALI gpu phones run much faster with delegate v2, which uses opencl delegate as the default backend. I tried to tune the work groups setting of conv2d and depthwise conv2d for opengl compute shader, but just like your team I don't see any obvious improvement. It's completely counterintuitive.
You mentioned about "a more systematic approach". Is that something about the opencl-opengl interoperability?

I would say that connection is like rendering system for gui order of
complexity.
On Fri, Jun 5, 2020, 3:53 AM Bruce Chou<EMAIL_ADDRESS>wrote:

@impjdi https://github.com/impjdi I'm super curious about this
suspicious root cause. I found some MALI gpu phones run much faster with
delegate v2, which uses opencl delegate as the default backend. I tried to
tune the work groups setting of conv2d and depthwise conv2d for opengl
compute shader, but just like your team I don't see any obvious
improvement. It's completely counterintuitive.
You mentioned about "a more systematic approach". Is that something about
the opencl-opengl interoperability?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/27613#issuecomment-639209312,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIT525SC26TRVZ7JF57L5C3RVBF2HANCNFSM4HEE66VQ
.

@brucechou1983 no, it's something else.  for example, loop unrolling & tiling are not handled efficiently in many of the mali drivers, so we may want to do the unrolling manually.  however, doing that makes the shader code quite unreadable and difficult to debug.  so we're making things to make that sort of task easy.

@WenguoLi  It looks like you are using an older Version of Tensorflow. Many bugs have been fixed in the latest version. Could you please execute your code using Latest Version 2.4.1 or 2.5 and let us know if the issue still persists? Thanks!


Atac window closing immediately

When i try to run the Atac command in my nvim session the window pops up and immediately closes.
Video
https://github.com/user-attachments/assets/89415f0d-4497-478d-a816-ad8be41ac22e

Hi! Thanks for sharing.
I'm currently in a business trip, is there a chance you could provide:

OS
NVIM version
ATAC version
if you have or not the config.toml file in your $HOME/atac dir?

Hi! Thanks for sharing. I'm currently in a business trip, so if this requires immediate code fix, it might be delayed until to Tuesday. Is there a chance you could provide:

OS
NVIM version
ATAC version
if you have or not the config.toml file in your $HOME/atac dir?

I use arch linux
nvim version is 0.10.1
atac version is 0.16.0  installed from pacman , cargo returns errors which suggest that
ratatui versions are not consistent somewhere and  that the Image type doesn't  implement the Widget trait or consider using an alternative type that does.

I'll be looking at this next week

Hello,
I installed Atac today as well as this plugin. I had the same problem. It was due to the folder not existing.
In order to adapt it to my projects, I told it that I wanted it to open in my projects folder + "/atac".
Here's my configuration:
return {
  "NachoNievaG/atac.nvim",
  dependencies = { "akinsho/toggleterm.nvim" },
  config = function()
    require("atac").setup({
      dir = vim.fn.getcwd() .. "/atac",
    })
  end,
}

Great, I will be changing the approach of checking the dir is existent to handle this scenario. Thanks for the input @Olprog59 . @urizennnn could you try this by any chance?

Great, I will be changing the approach of checking the dir is existent to handle this scenario. Thanks for the input @Olprog59 . @urizennnn could you try this by any chance?

I haven't created an nvim plugin before but i would love to contribute

@NachoNievaG so i thought i had a fix while testing but the plugin (untouched) seems to work in the atac.nvim dir but not in another project folder

Okay, I'll reference it to the guys at ATAC, I might be able to drive through a fix. Keeping you updated in this issue

Okay, I'll reference it to the guys at ATAC, I might be able to drive through a fix. Keeping you updated in this issue

alright
i might still try to outdo myself and look at the code


containers: add support for images digest

More information on image digest:
https://docs.docker.com/userguide/dockerimages/#image-digests
https://github.com/docker/distribution/blob/v2.1.1/digest/digest.go

@miq-bot add_label providers/containers
@miq-bot add_label enhancement
cc @zeari

@simon3z can you elaborate why is an image digest required (regardless of this patch, generally speaking)
since there is already a unique image id?

@simon3z can you elaborate why is an image digest required (regardless of this patch, generally speaking) since there is already a unique image id?

@abonas reason #1 is because unique image id != digest, e.g.
# docker images --digests
REPOSITORY                                   TAG                 DIGEST                                                                    IMAGE ID
<IP_ADDRESS>:5000/test/origin-ruby-sample   <none>              sha256:0cd076c9beedb3b1f5cf3ba43da6b749038ae03f5886b10438556e36ec2a0dd9   82f4bb9a807a

Then other important reasons:

(patch-specific) we were already [collecting it] (https://github.com/ManageIQ/manageiq/pull/4234/files#diff-0324981fdb3019ce6d98f9c86d97f2bbL453) but in the wrong place
we must know if a container definition requested a specific image using the digest
it's needed to correctly re-create the exact full image name in full_name


Fix app navigation issue after workspace upgrade

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/51733
PROPOSAL: https://github.com/Expensify/App/issues/51733#issuecomment-2447125077
Tests

Create a new workspace
Go to More features
Enable Company cards
Tap Upgrade
On upgrade success screen, tap View your subscription
App will open subscription page
Verify that the app does not navigate quickly to the workspace editor.

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Create a new workspace
Go to More features
Enable Company cards
Tap Upgrade
On upgrade success screen, tap View your subscription
App will open subscription page
Verify that the app does not navigate quickly to the workspace editor.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/bc05ae7a-7af3-430d-b369-0d38863da367

Android: mWeb Chrome

https://github.com/user-attachments/assets/75d25452-2f31-478e-8922-22be53a7a4cc

iOS: Native

https://github.com/user-attachments/assets/d8f8a509-9166-4684-8fff-81eb3a59d196

iOS: mWeb Safari

https://github.com/user-attachments/assets/12b9ffa7-1e97-446e-8093-fc1dda813a6b

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/6ed435bd-1ac3-4692-ba24-27dc2f25cc8f

MacOS: Desktop

https://github.com/user-attachments/assets/99b5709d-1fe6-4314-8cd5-b9f9960483f9

Please using a meaningful name for PR name

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@Nodebrute Could you give an ETA for your update?

@NikkiWines All yours

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@hannojg I think it was a random failure? I don' think changes from this PR can affect startup metrics...

@kirillzyusko agree, this seems like a false positive 🤔


DOC: Revamp contributor setup guides

Reference issue
Addresses #12633
What does this implement/fix?
This PR contains a refactored building from sources/quickstart development guide using sphinx-tabs and removing some redundant or outdated information.
The only content that has actually been removed is

MacOS scipy.github.io/devdocs/building/macosx.html
These instructions for MKL scipy.github.io/devdocs/building/linux.html#intel-c-compiler-and-mkl

All other content has been moved or simplified, but no specific instructions have been deleted from the guide.
This is a first attempt, and any feedback or suggestions are welcome. There are still conflicting instructions that will need to be made consistent in a second pass, but I am mainly looking for feedback on the general organization and look of these pages.

Thanks Melissa! Looks like a great start.

There are still conflicting instructions that will need to be made consistent in a second pass, but I am mainly looking for feedback on the general organization and look of these pages.

The tabs look great. I did have some trouble finding the right entry point, I think some more culling is needed. The docs start from "Contributor quickstart guide", however users navigating to "Development environment" see this, a good fraction of which is confusing:

How about at least adding a link to the preferred entry point to these new docs as the first bullet in that list, and making it clear (e.g., using bold text) that this is where to start?
here is a direct link to dev doc build

Thanks @melissawm!!
In case that helps, I've looked at our page views since we started collecting data (~3 months) and here are the top pages in the dev section (out of 50k total views):
dev 4.3k
dev/index 2.5k
dev/roadmap 918
dev/code_of_conduct 591
dev/core-dev/index 482
dev/hacking 363
dev/roadmap-detailed 333
dev/contributor/quickstart conda 307
dev/contributor/toc 298
dev/api-dev/api-dev-toc 266

Roughly 1/10 user is going to the contributor index. Then the first page about contributing which gets hits is hacking. And there are just a handful of people opening other pages not listed on the contributor index.
So I think we should retire hacking in favour of your quick start document or it's not going to be more visible (similar to what Ralf is suggesting :)).

Ok, one important question: do we need/want to keep separate building and contributor folders?

So I think we should retire (or possibly rework and move under SciPy contributor guide) hacking in favour of your quick start document or it's not going to be more visible/clicked (plus make it clear this is the preferred entry point: similar to what Ralf is suggesting for the envs section :)).

@tupui I actually would like to keep the hacking doc there. I think it's important for context for new contributors, and if they read that before contributing I think this is good :) I'll just make sure to get the quickstart to be more obvious in other pages. Happy to hear if you have other thoughts on this, though.

Here's another attempt. I tried simplifying further and may have gone too far 😄  - let me know!

Further improvement to be done in a second PR:

[ ] Remove redundancy between development_workflow and dev_quickstart
[ ] Update contributor_toc to nest/group things together (see https://github.com/scipy/scipy/pull/15947#discussion_r849175208)
[ ] Move Reference to build options to FAQ
[ ] Update contributor workflow video
[ ] Further organize system-level dependencies and buildilng docs (see https://github.com/scipy/scipy/pull/15947#pullrequestreview-934503303)
[ ] Update ubuntu_guide

@tirthasheshpatel I feel like I didn't really address a few of your comments because I had a different organization in mind. Would you review again and tell me what you think? Thanks!

Paging also @astrojuanlu who may be interested in this

Thanks @rgommers , I think I got all your suggestions. For the bold text with a link, I couldn't find a cleaner way, if there is I'd be happy to simplify 😄

Can you add a short description in https://github.com/scipy/scipy/wiki/Release-note-entries-for-SciPy-1.9.0?


mobile: disable static extension registration

When building with certain release optimizations, aggressive deadcode stripping causes these statics to be removed, causing extensions to fail to be found at runtime when they're attempted to be used, often causing a crash or even worse some functionality being silently disabled.
By disabling these statics completely for Envoy Mobile, extensions will fail to resolve unless registered by explicitly calling the forceRegister functions at runtime.
This will make Envoy Mobile's behavior more deterministic and less prone to breaking based on the level of dead code stripping.
Commit Message: mobile: disable static extension registration
Additional Description:
Risk Level: Moderate for Envoy, high for Envoy Mobile. Mitigated by using a --define flag.
Testing: The iOS async/await example app & CI.
Docs Changes: None.
Release Notes: Added.
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

I plan on splitting this PR into a few separate ones to make it easier to review.

/retest

cc @alyssawilk

I split up this PR into two more focused ones that should be no-ops to make it easier to review:

https://github.com/envoyproxy/envoy/pull/24864
https://github.com/envoyproxy/envoy/pull/24865

Once that's done, then the changes to actually disable static extension factory registration are relatively small and focused:

So I'll be asking reviewers to first review #24864 and #24865, then I'll merge main into this PR and ask for the final piece to be reviewed.

Hm, so I think I like this idea overall but I want to call out it has a pretty high risk of causing crashes on the data plane for anyone who uses it so I'm inclined to think it should be CI-only and come with warnings that it should not be used in production builds.  There's extensions like the HTTP matchers which could easily be turned on by config, might not be currently culled by dead stripping, and would then crash on a query which triggerd those matchers.  WDYT?

I'm inclined to think it should be CI-only and come with warnings that it should not be used in production builds

Yes that's definitely an option I was also considering, although I was more thinking that we could only enable this in debug builds, which is mostly what CI uses.

@Augustyniak @alyssawilk this is ready for review now

/retest

/retest

/retest

/retest

/retest


IdentityServer4.AccessTokenValidation for .netstandard?

I was using IdentityServer4.AccessTokenValidation in .net standard 2.0
Then I just wanted to update my project .net standard 2.0 to 3.0 and the new version (IdentityServer4.AccessTokenValidation - 3.0.1) is no more targeting .net standard :(
What to do now?

I don't follow - there is no netstandard 3.0.
The latest version of the access token handler targets ASP.NET Core 3 - which is netcore3 only.
If you need to support older versions - then use an older version of the access token handler.


Possible Fix for the not working cd command

after GVM2 is installes

No that's not right. The cd command is called and then resolution of go version and pkgset occurs.
You should try running with GVM_DEBUG:
prompt> GVM_DEBUG=1 cd <PATH>

That might help with determining the source of the problem.


[Bug Report] [WEB Documentation] /tutorials/gymnasium_basics/load_quadruped_model/ does not show in the TOCtree

Describe the bug
The recently added load_quadruped_model tutorial does appear in the list of tutorials
https://github.com/Farama-Foundation/Gymnasium/blob/main/docs/tutorials/gymnasium_basics/load_quadruped_model.md
https://gymnasium.farama.org/main/tutorials/gymnasium_basics/load_quadruped_model/

@mgoulao
Code example
No response
System info
No response
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

In docs/index.md, Update the tutorials toctree to:
```{toctree}
:hidden:
:glob:
:caption: Tutorials

tutorials/**/index
tutorials/**/*.md
tutorials/third-party-tutorials
Comet Tutorial <https://www.comet.com/docs/v2/integrations/ml-frameworks/gymnasium/?utm_source=gymnasium&utm_medium=partner&utm_campaign=partner_gymnasium_2023&utm_content=docs_gymnasium>


Support flattened externally tagged enums with default attributes

This adds a custom error type for FlatMapDeserializer, which distinguishes the specific no variant of enum {name} found in flattened data error.
This error is then used in deserialize_map in serde_derive to match on the returned error, and if the field or container has a default attribute it uses the expr_is_missing to provide a default value.
Fixes https://github.com/serde-rs/serde/issues/1626

The tests fail due to trybuild using an older version of serde or serde_derive. This PR only modifies API in the private mod, and in serde_derive. However, if after this patch both serde and serde_derive are not upgraded in lockstep then this will break at compile time. I'm not completely sure then, if this can be considered a non-breaking change? If all packages using serde and serde_derive in a project upgrade in lockstep then there is no external breaking change. Is it a requirement that serde_derive and serde be backwards compatible with older versions of each other?

@Mingun thank you for your review and suggestions! I implemented them both.
As for tests, I will happily write them but first could you confirm that the approach here will be accepted?

I don't know, I am the same external contributor as you. Judging by the general reaction of maintainers, one should hardly expect any attention in the near future

It is interesting that I went on to try to solve another problem revolving flatten in #2751 and we actually ended up on very similar approach.


Pull tags before checking HEAD when buiding docs

Fix the automatic docs build so that it will run when a new tag has been built.  Currently, the deployDocs script checks to see if the HEAD commit is also a tag. However Travis does not pull tags by default when cloning the repo and the check always fails.

Apparently, this was not actually the problem.  Travis loads the tags fine, but the actual issue was that the commit I pushed that should have triggered a new tag did not because the commit message was malformed.


Fix simple docstring typos

Coverage remained the same at 92.641% when pulling e5148694722cd344ae85941442ad0cad1e829ed6 on wwwesleyyy:master into 923a2feca1c0814fd034d03f417f8d9371cd99fc on loanzen:master.


Add DCOM support for req command

In the last few months, we encountered more and more ADCS instances that neither supported web enrollment, nor exposed the CertSvc via plain RPC. The output of certipy req looks like this in that case:
[+] Trying to resolve 'XYZ.ABC' at '...'
[+] Trying to resolve 'ABC' at '...'
[+] Generating RSA key
[*] Requesting certificate via RPC
[+] Trying to connect to endpoint: ncacn_np:...[\pipe\cert]
[!] Failed to connect to endpoint ncacn_np:...[\pipe\cert]: SMB SessionError: STATUS_OBJECT_NAME_NOT_FOUND(The object name is not found.)
[+] Trying to resolve dynamic endpoint '91AE6020-9E3C-11CF-8D7C-00AA00C091BE'
[+] Failed to resolve dynamic endpoint '91AE6020-9E3C-11CF-8D7C-00AA00C091BE'
[-] Failed to get dynamic TCP endpoint for CertSvc
[-] Got error: 'NoneType' object has no attribute 'request'

Still, the ADCS was full functional and native Windows tooling like mmc was capable of obtaining certificates. At this point we noticed that mmc does not rely on plain RPC, but DCOM for obtaining the certificate. The corresponding DCOM interface ICertRequestD is described in this microsoft spec.
And indeed adjusting certipy to use DCOM instead of plain RPC allowed us to obtain certificates again. This MR adds this functionality and allows users to specify the -dcom switch with the req action.
The error handling was copied from the RPC related certipy code and may not fit 100% for COM. However, this is something that probably pops up in user issues and can be investigated then :upside_down_face:

I see that this "only" affects files dealing with the "req" command. Would this also be useful for the "relay" command or is this not applicable due to DCOM hardening?

I see that this "only" affects files dealing with the "req" command. Would this also be useful for the "relay" command or is this not applicable due to DCOM hardening?

It appears that when relaying, it is necessary to use web enrollment for certificate issuance instead of other methods.

It appears that when relaying, it is necessary to use web enrollment for certificate issuance instead of other methods.

That is not correct. See for example the description of ESC11 in this repository. Relay is also possible against RPC if certain configuration is present (that is, IF_ENFORCEENCRYPTICERTREQUEST is not set).
This is why I was wondering if DCOM could also be used as a relay target. Maybe this also depends on specific configuration settings and would be too much for this pull request, but instead should be a dedicated ESC number on its own. Unfortunately, I don't know much about DCOM and therefore can't evaluate the possibility myself.

It appears that when relaying, it is necessary to use web enrollment for certificate issuance instead of other methods.

That is not correct. See for example the description of ESC11 in this repository. Relay is also possible against RPC if certain configuration is present (that is, IF_ENFORCEENCRYPTICERTREQUEST is not set).
This is why I was wondering if DCOM could also be used as a relay target. Maybe this also depends on specific configuration settings and would be too much for this pull request, but instead should be a dedicated ESC number on its own. Unfortunately, I don't know much about DCOM and therefore can't evaluate the possibility myself.

Oh, indeed, that's my mistake. I didn't take ESC11 into consideration, only focused on ESC8


dump/restore is broken in beta2: RuntimeError: pgcon: cannot issue new command; waiting for sync

EdgeDB Version: 1-beta2-22542f0

Looks like empty array of named tuples is causing restore to fail.
Steps to Reproduce:

edgedb server init test
edgedb migrate
edgedb -I test
INSERT AccentSettings { guild_id := 0, user_id := 0 };
edgedb -I test dump d
edgedb server destroy test
edgedb server init test
edgedb -I test restore d

edgedb error: ERROR: InternalServerError: pgcon: cannot issue new command; waiting for sync
  Hint: This is most likely a bug in EdgeDB. Please consider opening an issue ticket at https://github.com/edgedb/edgedb/issues/new?template=bug_report.md
  Server traceback:
      Traceback (most recent call last):
        File "edb/server/protocol/binary.pyx", line 2498, in edb.server.protocol.binary.EdgeConnection.restore
        File "edb/server/pgcon/pgcon.pyx", line 1470, in restore
        File "edb/server/pgcon/pgcon.pyx", line 1226, in _restore
        File "edb/server/pgcon/pgcon.pyx", line 1353, in edb.server.pgcon.pgcon.PGConnection._rewrite_copy_data
        File "edb/server/pgcon/pgcon.pyx", line 1419, in edb.server.pgcon.pgcon.PGConnection._mend_copy_datum
        File "edb/server/pgproto/./frb.pxd", line 28, in edb.server.pgproto.pgproto.frb_read
        File "edb/server/pgproto/./frb.pyx", line 10, in edb.server.pgproto.pgproto.frb_check
      AssertionError: insufficient data in buffer: requested 4 remaining 0

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "edb/server/protocol/binary.pyx", line 1710, in edb.server.protocol.binary.EdgeConnection.main
        File "edb/server/protocol/binary.pyx", line 2513, in restore
        File "edb/server/pgcon/pgcon.pyx", line 1046, in simple_query
        File "edb/server/pgcon/pgcon.pyx", line 1586, in edb.server.pgcon.pgcon.PGConnection.before_command
      RuntimeError: pgcon: cannot issue new command; waiting for sync

Only empty array causes this error.
I tried using array with 1 item, multiple items, add records with different amount of array items, only empty array causes this.

Schema:
https://github.com/Fogapod/pink/tree/main/dbschema
This line: https://github.com/Fogapod/pink/blob/122b4b700b52ee9d4cc82e0ed45c624a98704915/dbschema/default.esdl#L13

Good catch, thanks!


searching

I coded a simple ruby program to send logs to ekanited, see: https://gist.github.com/cleesmith/1d87a436023f746549ec
... for testing without rsyslog or syslog-ng
... maybe useful for others and could be altered to read the logs13k.txt file you provide
Some of the following may be issues for bleve, but I noticed:

searches only work for exact matches: ssh won't match sshd
no wildcard ssh* searches
no word stemming: listen, listened, listening or similar
are time range searches possible?
is it possible to list the most recent logs, say, in descending order by timestamp
... i.e. a kind of near real time view of what's happening
instead of telnet localhost 9950 doing a http://localhost:9950/ in the browser lists all logs
running 2 simultaneous ruby programs sending syslogs takes twice as long: from 20 seconds for one to 50 seconds each for two ... i.e. sometimes logs are sent from multiple sources to a central server, or perhaps ekanite is only intended to receive from a single rsyslog/syslog-ng instance
is there docs or more details about the folder that is created: 20151018_0000 which seems to use 1.2M of space for 40 syslogs ?
84,440 logs uses 1G <-- du -h 20151018_0000 ... this just seems like a lot, but I'm not sure ?

"ekanite": {"launch": 2015-10-18 15:22:40.011642743 +0000 UTC},
"engine": {"batchIndexed": 285, "batchTimeout": 5, "docsIDsRetrived": 1467, "eventsIndexed": 84440, "queriesRx": 60},
"input": {"tcpBytesRead": 9404505, "tcpConnReadEOF":<PHONE_NUMBER>, "tcpConnReadError":<PHONE_NUMBER>, "tcpConnections": 5, "tcpEventsRx": 84440, "unparsed": 84440},

I work on a lot of projects involving syslogs and intrusion detection (events from Snort/Suricata) so I find ekanite interesting. My future view is to replace elasticsearch with something similar but coded in Go for simpler deployments.
Thanks for your efforts.

Thanks for the feedback @cleesmith
Most of the issues you raised are due to bleve works, though Ekanite may be able to drive bleve differently. As for time-ranged queries, the system is specifically built to handle them (https://github.com/ekanite/ekanite/issues/13) but it is not fully implemented yet. I need to implement my own parser for interpreting range queries.
As for the disk usage issues, this is due to the way BoltDB (which bleve is built on) works. It allocates a lot of disk upfront (and doubles it every time it decides to allocate more). 1GB is a very large amount, but it should stop with 1GB and store a lot of logs in there. I am going to look into using LevelDB, but this means a less cleaner build since LevelDB is in C.
I didn't know about http://localhost:9950/! I must see why that happens.

I will continue testing and pushing syslogs while watching the disk usage -- noticed the shards were allocated in large chunks, so maybe they are mostly empty at first.
 I did notice LevelDB, but the pure Go solution is appealing but may be less performant for "big data".
The http://localhost:9950 seemed like an easy way to view the data, well, if it was just the most recent logs that would be even better.
I will close this as the issues are really about bolt/bleve.
Thanks.


Document about the difference between StandardMetrics from ApplicationInsights vs AppService metrics

I have seen a lot of users getting confused when the ApplicationInsights standard metrics (Req/count, Req/duration etc) are not matching the ones from AppService itself.
The doc clarify the following:
ApplicationInsights collects telemetry for those requests which made it to the application. If the failure occurred in WebApps/IIS, and the request did not reach the user application, then application insights will not have any telemetry about it.
The duration for serverresponsetime calculated by Application insights is not necessarily matching the server response time observed by Web Apps. This is because application insights only counts the duration when the request actual reaches user application. If the request got stuck/queued in IIS, that waiting time will be included in the WebAPp metrics, but not in application insights metrics.

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

ID: 098ffe3a-2cbd-1038-30f2-dd2f528984a3
Version Independent ID: 65da3e70-2ac2-8f6e-51a5-e759bcc8253f
Content: Monitor Azure app services performance - Azure Monitor
Content Source: articles/azure-monitor/app/azure-web-apps.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Hi @cijothomas I made a work item to add difference between StandardMetrics from ApplicationInsights vs AppService metrics to the documentation.
Thank you
#please-close