feat: migrate semantic from osv-scanner

This brings across the semantic package from osv-scanner, which provides support for parsing and comparing versions across different ecosystems per their unique specifications (or lack thereof).
Main actions / discussion points:

deal with cachedregexp (though worth noting that semantic includes some chonky regexps which do take a second or two to compile)
discussion naming and package structure
re-write generators (primarily so that they're better documented - despite trying to do what I thought was a good job the first time round, I keep finding myself just lost enough whenever I re-read over them when implementing a new one that I want to put some work into improving them)
setup the semantic weekly workflow

Resolves #257

@another-rex @erikvarga thinking about this in the public context and especially in regards to error handling, I'm wondering if we want to start by making just about everything except for MustParse and Parse private? That way we'll only be exposing a function that returns an error allowing us to defer deciding if we want to have the individual parse/compare functions return an error.
I don't know much about the desired uses for semantic internally so I'm not sure if there's anyone wanting specific ecosystems, but ultimately that should still be achievable by using Parse, it'd just mean everyone would include the whole package in their binary.
i.e.  this usage of semantic.ParsePackagistVersion, should be replaceable with semantic.MustParse(lower, "Packagist").CompareStr(upper)

@alowayed @zpavlinovic @erikvarga thanks for the reviews and discussions so far! I think there's been enough for me to do another pass before we continue further - notably, I think we should look at making semantic return an error so we can avoid panics even if we end up just returning one or two errors as it'll be easier long-term to have "return an error" as an option than to try and retroactively add support for it.
I expect too I'll probably go ahead for now with making most things private to make it easier to iterate on the internals - I think that probably comes down to MustParse and Parse being the public entry points, but I'll confirm once I've gotten back into the weeds.
I'll also try to do a general refresher on the package and related native version comparers as a whole since while I do have confidence in what I've said so far, I wrote a lot of this 1-2 years ago and its required very little change besides adding new comparators, which while a great sign of stability (or lack of use... 😅) does mean I'm not feeling as confident as I'd like when trying to think through tradeoffs and make architecture decisions
Feel free to continue discussions and review, but also feel free to wait until I've actioned the above 🙂


bug: deploy update crashing app.

Type: bug
Ionic Version: 2.x
Platform: android 4.1 webview
i use the ionic deploy. its good but i saw a epic or a critical error because for example you accidentally update your apps with a error issue the apps is totally crash... or is not working ever... help me to fix this issue so that  i will fix my problems. thanks..

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!


need data download system

I want something that takes as input an MJD, and:

Downloads all the data (sdR files) for that MJD into a sensible directory.
Reads the headers of the sdR files and deletes all non-arc exposures.

Alternatively, if we can work without any downloading, but just work with remote files, I'd maybe prefer that for reproducibility / platform-independence.


Pin storage improvements and backup

Make sure the state of the app is restored when the phone is restored or brought back after offloading
Find alternative of rn-secure-storage which does not use keychain api - so that the pin is available after phone restore
Migration for existing users - execute before login
Option of forgot pin #5206

Separate out the issue for offloading or phone restore and the app working as it was.
Given that the app is not offloaded and we are using the same device, how do we reset the passcode - do now


o1系列模型展示思考过程

看日志，发现思考过程会触发JSON解析异常打印到日志里，希望可展示

请提供网站的数据，可以考虑加上去

backend-to-api-1  | 2024-09-26 22:19:49,031 [INFO] - 发送数据: : ping - 2024-09-26 14:19:47.812400+00:00
backend-to-api-1  |
backend-to-api-1  | data: {"message": {"id": "f243aeec-8740-4f3e-b3ba-b98e98fc7dbb", "author": {"role": "tool", "name": "a8km123", "metadata": {}}, "create_time": null, "update_time": null, "content": {"content_type": "text", "parts": ["Appointing aid\n\nFirst, I greet the user, then quickly grasp the question to provide the correct answer in the user's language.\n\nInvestigating terminology\n\nOK, I\u2019m thinking about the term 'pinnacle number' and its link to 884868. As of 2021, there's no established mathematical property for 884868 as 'pinnacle number'. It might be a new term or meme.\n\nReversing and converting\n\nI'm mapping out the digits of 884868 upside down to see if they form meaningful words or phrases using calculator-style letter interpretations.\n\nFlipping numbers\n\nOK, let's see: flipping upside down yields BGBhB B. Considering numerology ideas and Chinese homophones is equally fascinating.\n\nAnalyzing numerical patterns\n\nI\u2019m examining how 884868 could be linked to Mount Everest's height, possibly as a rounded version of 8848.68 meters, or more accurately, 8848.86 meters.\n\n"]}, "status": "in_progress", "end_turn": null, "weight": 0.0, "metadata": {"finished_text": "Finished thinking", "initial_text": "Thinking", "parent_id": "53d22e6f-ff01-4f38-b06f-5c0e615176c9", "model_switcher_deny": []}, "recipient": "all", "channel": null}, "conversation_id": "66f56d72-1b94-8007-85b7-b564fa4aa49b", "error": null}

简单看了一下就是if role == "tool" and name != "python" and name != "dalle.text2im" and last_content_type != "execution_output" and content_type != None:下面直接设置new_text = ""了，针对思考场景额外判断一下并且美化下排版就好。

可以的 来pr🥳

看了一下 把代码注释掉就行 如果需要美化结构化输出的话 欢迎来pr🥳


Add pop-up and/or helpful highlight text to submission form questions

Insert additional information access to helpful hints for how to fill in the DPG form.

Reviving this issue.
Motivation
There have been a lot of back and forth communication between DPG Owners and the DPGA team over email seeking clarifications about our questions. Nathan has helpfully compiled a lot of hints to these commonly asked questions. We also have documents in a help centre available here.
However, since these resources are not available in context when DPG owners are filling up the nomination form, we still have to engage in communication over email, slowing down the vetting process.
Proposed Solution
If we could attach the relevant hints, and links to help centre within the context of the form itself, we could potentially save a lot of manual effort.


Add plugin_ffi type support

https://docs.flutter.dev/development/packages-and-plugins/developing-packages#types
It is necessary to add flutter-tizen functionalities so that FFI plugin packages can be created and used.

In plugin_ffi template of flutter, there is no platform-specific native source code and the source code has a CMakeLists.txt to make a shared library.

.
├── analysis_options.yaml
├── CHANGELOG.md
├── ffigen.yaml
├── ffitest.iml
├── lib
│   ├── ffitest_bindings_generated.dart
│   └── ffitest.dart
├── LICENSE
├── pubspec.lock
├── pubspec.yaml
├── README.md
└── src
    ├── CMakeLists.txt
    ├── ffitest.c
    └── ffitest.h

A lot of questions.
should flutter tizen use this template? Or should we use our own template? Is it possible to build cmake with tizen sdk? Should a single plugin library (libflutter_plugins.so) policy be continued?

I already considered this once but decided not to support the template because it didn't make much sense for our use cases.

should flutter tizen use this template?

I don't think so.

Or should we use our own template?

I don't think it's necessary. It's quite straightforward to write a Dart plugin from scratch without a template.

Is it possible to build cmake with tizen sdk?

Tizen SDK doesn't support CMake.

Should a single plugin library (libflutter_plugins.so) policy be continued?

We already support sharedLib type plugins.


[bug]: DPM Samplers Seem To Never Converge On MPS?

Is there an existing issue for this?

[X] I have searched the existing issues

OS
macOS
GPU
mps
VRAM
16GB
What happened?
Running prompt 'banana sushi' -S42 in k_dpm_2 and k_dpm_2_a at 17, 27, and 37 steps seems to indicate that SD will never converge (decide?) on a particular image.
k_dpm_2 at 17 steps

k_dpm_2 at 27 steps

k_dpm_2 at 37 steps

Screenshots
No response
Additional context
Seeing this on my system since the 2.0 release, including the 2.1 release candidate I cloned yesterday on 11/1. Anyone else? I can reproduce this with as many as 70 steps (making my poor M1 Pro MacBook very melty). k_heun sampler does not exhibit this behavior, BTW.
Contact Details
No response

Thanks for the report. I’ll try to reproduce the error and suggest a fix.

+1 I see the same behavior.

@lstein Is this possibly related to the rcently-discovered regression in reproducibility?

A datapoint - I took the Automatic1111 distro for a brief spin, and DPM2 and 2a behave the same there, so I wonder if the issue has more to do with dependencies (PyTorch?) + my hardware than InvokeAI (i.e., a me problem).

I'm pretty sure I've been hearing about this for a long time, maybe since
the beginning of the k_diffuser import. Someone with an MPS system should
check out an old version and see if it was there.
Lincoln
On Sat, Nov 5, 2022 at 6:25 AM victorca25 @.***> wrote:

+1 I see the same behavior.
—
Reply to this email directly, view it on GitHub
https://github.com/invoke-ai/InvokeAI/issues/1350#issuecomment-1304487302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3EVLUM4LU4PY36QVP3C3WGYY2PANCNFSM6AAAAAARVI7KYA
.
You are receiving this because you were assigned.Message ID:
@.***>

--
Lincoln Stein
Head, Adaptive Oncology, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto
Tel:<PHONE_NUMBER>
Cell:<PHONE_NUMBER>
@.***
E**xecutive Assistant
Michelle Xin
Tel:<PHONE_NUMBER>
@.*** @.**>
Ontario Institute for Cancer Research
MaRS Centre, 661 University Avenue, Suite 510, Toronto, Ontario, Canada M5G
0A3
@OICR_news
https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Foicr_news&data=04|01|Michelle.Xin%40oicr.on.ca|9fa8636ff38b4a60ff5a08d926dd2113|9df949f8a6eb419d9caa1f8c83db674f|0|0|637583553462287559|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=PS9KzggzFoecbbt%2BZQyhkWkQo9D0hHiiujsbP7Idv4s%3D&reserved=0
| www.oicr.on.ca
Collaborate. Translate. Change lives.
This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

I think I follow. Do you mean check out an old version of InvokeAI before you started using k_diffuser? Or check out an older version of k_diffuser? Sorry, machine learning isn't my background and this is all quite... Exotic to me 😳

I looked into this and I have a fix which restores the four k_dpm* samplers which are currently broken on Apple Silicon.
The fix is simple, but I think input is needed first from project maintainers and this is why I am not sending a PR yet.
The root cause:
in PyTorch 1.12.1 there is a bug with indexing on 'mps' device, if followed by a function activation.

torch.tensor([1.,5.], device='mps').log()
tensor([0.0000, 1.6094], device='mps:0')
torch.tensor([1.,5.], device='mps')[1].log()
tensor(0., device='mps:0')  # should be 1.6094

This bug is fixed in PyTorch 1.13, but that version has a more serious issue as to make InvokeAI completely unusable for me. (I suspect memory management, constant swapping). Related: https://github.com/pytorch/pytorch/issues/89784
Back to 1.12.1: the bug affects InvokeAI through 'log' on a single 'sigma' -
https://github.com/Birch-san/k-diffusion/blob/mps/k_diffusion/sampling.py#L590
The sigmas array is a one-dimensional mps-tensor, and thus suffers from the pytorch 1.12.1 bug.
My suggested solution: move this tensor to 'cpu'. It is small, but more importantly - its dimension ('time') is unrelated to any of the dimensions of the actual tensors at play: there is no real reason for it to be on the gpu (or even a tensor, for that matter).
For example, here, add .to('cpu'):
https://github.com/invoke-ai/InvokeAI/blob/main/ldm/models/diffusion/ksampler.py#L196
The complication: the 'to_d' function that is used in several samplers treat a scalar 'sigma' value as a tensor, which causes an error for mixed gpu/cpu tensor computation.
https://github.com/Birch-san/k-diffusion/blob/mps/k_diffusion/sampling.py#L48
(I don't understand why the dimension adding before division is needed, can someone please elucidate?)
The workaround there is to move the single-sigma to 'mps' by adding .to('mps').
(PS: There's already an MPS workaround in 'to_d', very possibly related:
https://github.com/Birch-san/k-diffusion/blob/mps/k_diffusion/utils.py#L46 )
Hope this helps!


Icon animation not working with react navigation v5

🐛 Bug Report

To Reproduce
Steps to reproduce the behavior:

add pulseIconRef

export const MainNavigator = () => {
  const pulseIconRef = React.useRef();

  return (
    <Tabs.Navigator
      tabBarOptions={{
...)}

set icon ref and  tabPress listener

the ref raised:
The expected type comes from property 'ref' which is declared here on type 'IntrinsicAttributes & IntrinsicClassAttributes<Icon<{ name: "people-outline"; width: number; height: number; fill: string; ref: MutableRefObject<undefined>; animation: "pulse"; }>> & Pick<...> & Partial<...> & Partial<...>'

pulseIconRef.current raised:
(property) React.MutableRefObject<undefined>.current: undefined
Object is possibly 'undefined'.ts(2532)

animation not working albeit using codes from the official docs.

Expected behavior
When I tap the tabicon, the animation should run.

UI Kitten and Eva version

Package
Version

@eva-design/eva
"^2.0.0"

@ui-kitten/components
"^5.0.0"

"@ui-kitten/eva-icons": "^5.0.0",

Environment information

  npmPackages:
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2

Same issue

have you found a solution?

Not really a solution, but it works if you use React.useRef<any>()

@kockok
Apparently you're trying to use an icon inside the tab bar itself, try using the custom tab bar from our library where you can handle all the events you need, if you need any more help, let me know.


Added installation instructions for yt

The README indicates that openPMD files can be read with version 3.4-dev of yt, but I did not find the instructions for how to install this version. After figuring it out for myself, I thought it might be good to include somewhere.
Is this README a good place? The alternative is to include it in the @C0nsultant 's tutorial notebook.

good point, but actually they are directly on the yt homepage under "get it": http://yt-project.org/#getyt
I would not add install instructions directly in the document but keep a link to the projects (and projects should advertize how to install them), otherwise it is going to be rather longish quickly. be aware that yt is currently in the process of switching from mercurial (hg) to git (& github) :)

I would close this if that's ok and update that yt migrated to github

Sure, no problem. Sorry for my lack of response!

sure, no prob :)


Update Root Readme

Description
Updating root readme.md
Fixes # (issue)
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Sample Migration (Moving sample from old repository after completing checklist established)

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

[ ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode

Checklist for Moving samples:
Links and Details can be found in the samples WG Teams Files.

[ ] Review sample design with domain reviewers https://github.com/oneapi-src/oneAPI-samples/wiki/Reviewers-and-Domain-Experts
[ ] Implement coding guidelines and ensure code quality.
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com
[ ] Adhere to readme template
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Enforce format via clang-format config file
[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth or Joe Oster. (GitHub User: JoeOster)
[ ] Tested using Dev Cloud when applicable
[ ] Implement fixes for ONSAM Jiras
[ ] If you have new dependencies/binaries, inform Samples Project Manager Swapna R Dontharaju (@srdontha) or @JoeOster

Is this an accurate representation of how this will look?
https://github.com/JoeOster/oneAPI-samples
If so, the formatting is wonky. The rightmost table column is much too narrow. Also, the titles of the sections at the bottom aren't rendering correctly. Not sure what's wrong there.

Pending on changes requested by @sravanikonda


Fall-back to basic pixel format if wglChoosePixelFormat() failed

Instead of returning with an error here:
https://github.com/drobilla/pugl/blob/196d8d2943e628bc53dc21f34859ad2740ef1142/pugl/detail/win_gl.c#L165
I found that continuing equal to the else() clause
https://github.com/drobilla/pugl/blob/196d8d2943e628bc53dc21f34859ad2740ef1142/pugl/detail/win_gl.c#L170
instead of returning will allow programs to work that would otherwise not. Replacing the return with
// Modern extensions not available, use basic pixel format
impl->pfd  = fakePfd;
impl->pfId = fakePfId;

makes a difference.

Applications that ask for a particular pixel format and don't get it need to know that.  They can retry with a different one if they want.

Ok, fair enough. However
surface->procs.wglChoosePixelFormat(..)
can return true with numFormats=0 (no matching format found). It looks like this case isn't handled right now.


Triangular distribution for TS

New triangle distribution for TS Implemented.
Remove the superfluous variable hold and the corresponding code.

Is like the enablingType in Places. Should be uniform
parameter Integer enablingType=1
    "resolution type of actual conflict (type-1-conflict)" annotation(Dialog(enable = true, group = "Enabling"), choices(choice=1
        "Priority", choice=2 "Probability", __Dymola_radioButtons=true));


TrimEditor error: 'bytes != null': is not true

Hi -nice package.
I get this error when opening videoTrimmer with a mp4 videofile. Al thumbnails are rendered except the last few ones, then this error comes?
Sometimes the file load fine and all thumbnails are shown. But often this error comes... I made sure the file is loaded before opening TrimEditor()
I can see that issue #88 mentioned the same error...
═══════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown building:
'package:flutter/src/painting/image_provider.dart': Failed assertion: line 928 pos 14: 'bytes != null': is not true.
When the exception was thrown, this was the stack
#2      new MemoryImage
package:flutter/…/painting/image_provider.dart:928
#3      ThumbnailViewer.build..
package:video_trimmer/src/thumbnail_viewer.dart:66
#4      SliverChildBuilderDelegate.build
package:flutter/…/widgets/sliver.dart:449
#5      SliverMultiBoxAdaptorElement._build
package:flutter/…/widgets/sliver.dart:1130
#6      SliverMultiBoxAdaptorElement.createChild.
package:flutter/…/widgets/sliver.dart:1143
...

Same problem

#94 the error occurs when VideoThumbnail is trying to create from a empty file or null path... works i'm some devices but no in emulator and samsung devices for example...
package mantainer doesnt track issues, i posted it 13 days ago, without response...

Closing this as it is a duplicate of #94 , please continue the conversation there.


Add streaming documentation

[x] Add details statistics information
[x] Showcase the graphs
[x] Preview some UI features and explain statelessCount

Update the streaming tooltip


Class diagram doesn't match the code. Pattern "State"

Could you correct the differences between the diagram and the code?

Hey, thanks for your submission.
I will handle this.

Fixed in #503


Initial route53 support

Create a subdomain and allow for acm validation via Route 53.

@Joibel - I believe this is ready.  Let me know what you think!


Testing helpers

Worked a bit with some testing of my modules which implements Fullcalendar and I thought it would be nice to add some testhelpers to the gem.
Would you like this? Or do you just want to put the JS in the pipeline?
Cheers, David

Hi David!
What do you test with your helpers? If they relate directly to functionality of fullcalendar itself, I think they should be contributed to fullcalendar itself, not to this gem. If they relate to functionality introduced by this gem-repackaging, then I'd love to have a look at them. :)
Cheers,
Niklas


feat: use ftp instead of datalake AB#8575

@gulfaraz looks good (assuming you've tested that the pipeline works on non-mock for a flood-country). I'm realizing now, this should actually come with a (hotfix) deploy to production, otherwise there was no point in doing this quickly. We should then cherrypick this commit and merge in the current production-version, because otherwise we are stuck with the scenario we discussed yesterday where we would have to deploy the half-baked multi-hazard solution...
PS: see latest status of the logic app discussion here.

It is actually solved now
except for a small question around publishing the needed change in the ADF-pipeline ..
it that would be resolved (and the change published by Maarten or by myself if it happens today/tomorrow)
then the whole problem is actually resolved, and we don't need to deploy to production and we can switch this back again ...

@jannisvisser That's nice, please let me know if the change gets pushed or not. I'm following the discussion anyway. I'll hold the hotfix deployment until tomorrow. Thank you for the update.
I've tested the pipeline on real data for Uganda and Zambia.


Create fails at Remove the hdd0 device w/ sudo requirement

When trying to create a new machine, VM creation fails and requests admin os credentials:
Errors:
Failed to register the VM: The operation failed. To perform this operation, you must enter the host OS administrator's credentials.
Failed to create the virtual machine.

Debug Output:
docker-machine create -d parallels --parallels-boot2docker-url https://github.com/boot2docker/boot2docker/releases/download/v1.8.2/boot2docker.iso test-parallels --debug
executing: prlctl --version
executing: prlsrvctl info --license
Downloading boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v1.8.2/boot2docker.iso...
Creating SSH key...
Creating Parallels Desktop VM...
executing: prlctl create test-parallels --distribution boot2docker --dst /Users/arod/.docker/machine/machines/test-parallels --no-hdd
Creating the virtual machine...
Generate the VM configuration for boot2docker.
Remove the hdd0 device.
Failed to register the VM: The operation failed. To perform this operation, you must enter the host OS administrator's credentials.
Failed to create the virtual machine.
Error creating machine: prlctl create test-parallels --distribution boot2docker --dst /Users/arod/.docker/machine/machines/test-parallels --no-hdd failed: exit status 255
You will want to check the provider to make sure the machine and associated resources were properly removed.

Any ideas on how to resolve this?

I've answered on the similar issue with vagrant-parallels: https://github.com/Parallels/vagrant-parallels/issues/67#issuecomment-32774326
Please, open the window "Parallels Desktop -> Preferences -> Security" and
disable the option "Require password to: Create a new virtual Machine"

Awesome! Issue resolved. Thanks!


Windows needs extra Windows system  libraries for starting the program "test/eventuals"

This fix will be done via N. by another way


Extracting custom action binaries

Would be nice if this also could extract binaries for custom actions as well.

Love the suggestion. Let me know if you (or anyone else!) is interested in contributing. Happy to help and support someone on this.

@WillSullivan in v1.6.0 I added support for extracting raw streams on a new "Streams" tab in the GUI. Is that what you need or are custom action binaries separate? If you could provide a specific msi and more detail about what you're after I might look into it next time I'm hacking on this project.
Of course, contributions are always welcome :)

To the best of my knowledge extracting streams actually accomplishes this ask. Since there hasn't been engagement on this I'm going to close it. If anyone has a concern or advice feel free to reopen.


CI type check failing with: "object*" is not iterable

https://github.com/microsoft/vscode-python/actions/runs/5019545181/jobs/9000282148?pr=21272#step:7:24
pyright 1.1.309, node v16.16.0, pyright-action 1.5.1
/home/runner/runners/2.304.0/externals/node16/bin/node /opt/hostedtoolcache/pyright/1.1.309/x64/package/index.js --outputjson
/home/runner/work/vscode-python/vscode-python/pythonFiles/normalizeSelection.py:63:9 - error: "object*" is not iterable
  "__iter__" method not defined (reportGeneralTypeIssues)
Error: "object*" is not iterable
  "__iter__" method not defined (reportGeneralTypeIssues)
/home/runner/work/vscode-python/vscode-python/pythonFiles/tests/unittestadapter/helpers.py:[27](https://github.com/microsoft/vscode-python/actions/runs/5019545181/jobs/9000282148?pr=21272#step:7:28):38 - error: "object*" is not iterable
  "__iter__" method not defined (reportGeneralTypeIssues)
Error: "object*" is not iterable
  "__iter__" method not defined (reportGeneralTypeIssues)
2 errors, 0 warnings, 0 informations

This is the code it is complaining about:
https://github.com/microsoft/vscode-python/blob/a74f1d15b58e2a835f5564449918452ff30d62d6/pythonFiles/normalizeSelection.py#L63
This started happening with pyright version 1.1.309

Apologies for the regression. This is a duplicate of https://github.com/microsoft/pyright/issues/5126, which I've already fixed. It will be addressed in next week's pyright release. You can roll back to 1.1.308 if this is blocking you.

@bschnurr can this be closed?


Optimization Phase 1

Closes #35
Closes #34
Bump dependancy
update translation course javascript basic

Codecov Report

Merging #36 (8093d51) into dev (fbae482) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev      #36   +/-   ##
=========================================
  Coverage     75.38%   75.38%
  Complexity      525      525
=========================================
  Files           147      147
  Lines          1446     1446
=========================================
  Hits           1090     1090
  Misses          356      356

Flag
Coverage Δ

api
75.38% <ø> (ø)

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

Continue to review full report at Codecov.

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


Include plugin health score in Pipeline steps reference

I think that users of the Pipeline Steps reference pages (like docker compose build step) would benefit if the top of the page included the plugin health score as either a badge or a visible number.  That would help users of the specific Pipeline steps understand if they are using a plugin that is unmaintained or otherwise unhealthy.
The docker compose build step (as an example) has a surprisingly high score (96) for a plugin that has had only one release and that single release was 5 years ago with documentation from the Jenkins wiki export.  Likely that we need more components in the health score in order to more accurately reflect the lower score that type of plugin should receive.

The docker compose build step (as an example) has a surprisingly high score (96) for a plugin that has had only one release and that single release was 5 years ago with documentation from the Jenkins wiki export. Likely that we need more components in the health score in order to more accurately reflect the lower score that type of plugin should receive.

I agree. We need to refine the scoring process or create a new one now that we have the Jenkins Core version requirement, the installation count, etc. cc @jleon33

Is this a beginner-friendly issue?

Is this a beginner-friendly issue?

I don't think this is a good first issue yet.  Once the health scores can be downloaded from the plugin health scoring system, it might be a good first issue.
The majority of the changes to implement this will be in the Pipeline steps doc generator and possibly in the Pipeline metadata utils, not in the plugin health score repository.  Those tools will need to be enhanced to read the plugin health score data and insert the scores into the page layout of each of the pipeline steps pages in a way that is visually pleasing.

Could you tell me a beginner-friendly issue in this repository?

I don't see any issues in the repository currently that I would consider good first issues.


ctk: develop showcase L2 and L2 CTK for Canvas

Description
For the DTW23 conference showcase, we will use the Phase 1 CTK work by @tomkivlin as the Level 1 canvas ctk (testing base software and versions) and the BDD tests as the L2 canvas ctk. This matches the Component ctk structure.
This issue is to re-work the Phase 1 scripts as L1 and create a wrapper for the BDD scripts as L2. Also, add user experience enhancements to make a compelling demo for the showcase.

This was completed as part of PR #109
The L2 CTK for the Canvas is at https://github.com/tmforum-oda/oda-canvas/tree/master/compliance-test-kit and a video demonstration for showcase is at https://www.youtube.com/watch?v=UofZbT26ITg&t=2s


sp_utf8_encode return value

It looks like sp_utf8_encode returns the number of bytes written to the target buffer and not the number of bytes consumed from the source buffer.
https://github.com/imgix/siphon/blob/master/lib/utf8.c#L211
https://github.com/imgix/siphon/blob/master/lib/utf8.c#L516
Which might be OK too.. Just opening up discussion about it.

That's correct. sp_utf8_encode takes in a length and encodes all of it or fails. It could return the input length, but I don't suspect that would be too useful. The input length is obviously already known, but the encoded length is not. The sp_utf8_*_encode functions are the ones that return the number of bytes consumed, as they are responsible for ensuring proper encoding. Its not possible to know the number of bytes that will be consumed otherwise. The length passed to those functions is the number of bytes in the buffer, and it represents the maximum number of bytes that could be consumed.
The short of it is that these functions return the otherwise unknown piece of information rather than just returning an input parameter. The sp_utf8_*_encode functions can't really be changed, but sp_utf8_encode is meant more as a convenience function. If there is something that would be more convenient it might be possible to change. This is all true for decode functions as well.

ah gotcha. that makes sense.


[Blog] Promote upcoming session at ONE summit

Describe the update:

Follow-up blog post about upcoming session at ONE summit

Describe why update is needed

to share updates made on the CNTI program since the last blog post on December 20
to promote the session about CNTI at ONE Summit on May 1 #4

Additional context

Taylor and Olivier are scheduled to speak at ONE Summit (see #4), which can be promoted in the blog post
Review of the CSP Whitepaper (In Best Practices focus area) should not block the next blog post to share updates

I'm going to close this as a duplicate of #18


Refactor device.h

Removed some unused functions, took stuff out of types.h, etc.
Only last two commits have minor functional changes:

PID was a public member of device - moved to ds_device (not used in non-uvc devices, like software devices)
simplified stream_profile and added comments

Sensor.h is next...

Any reason why libci failed ?

Not related. I just reran it:
https://rsjenkins.iil.intel.com/job/LRS_libci_pipeline/6104/
All passed.


Consider moving repo to windranger-io org

This work will eventually be proposed to BitDAO for adoption, and can reside in windranger-io until it's approved.

Done


focus of textbox (and derivatives) is glitchy

Describe the bug
If a textbox (or a derivative control) does not have focus when your app loses focus and you click directly into that textbox, it appears to have focus (it is highlighed, a cursor appears, the cursor blinks), but you can't type anything into the box.
Note that

if a textbox has focus when the app loses it, this particular textbox will always work
this behaviour is not winui specific - I can reproduce it with a normal UWP app too, but I was hoping winui would solve it

Steps to reproduce the bug

Steps to reproduce the behavior:

Open XAML Controls Gallery, go to Text -> TextBox
Click on any of the textboxes to give it focus
Click on any other open window on your system to lose focus
Click directly on a different textbox
Try to type things

Expected behavior
I can type into the textbox I clicked.
Version Info
I don't think the store tells me the exact app version, but it says it was updated to winui 2.2.

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

November 2019 Update (18363)
Yes

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Mobile

Xbox

Surface Hub

IoT

Additional context
All my devices are using W10 Pro N, if that matters.

This sounds like the same as #1849.
Please speak up if that doesn't seem like the case to you, and feel free to add detail to that issue.

Yeah, this looks like #1849 to me too. Sorry, I didn't find it while searching for potential duplicates!


Can you please release the training code?

Hi,
I would like to train the elmo for my own dataset. Can you please release the training code so that I can use the weights generated by it into the bilm-tf application? I would be thankful, if I  get some meanings from your training code although it is not ready for github?
Thank you.

Training code is now available on master.


Added support of non AWS S3 servers

Looks good, thanks for the contribution!  (And sorry for the delay.)


Add npm install command into README.md

Readme is missing copy-pasteable sections
npm i @vaadin/vaadin-time-picker --save

and
import<EMAIL_ADDRESS>
that exist in most of other Vaadin Components

Good catch, thanks.


Issue #98: Update GKE setup instructions to ensure node resources meet requirements

@antonmry filed an issue that the default GKE install we suggest doesn't provision enough resources: https://github.com/pixie-io/docs.px.dev/issues/98
I bumped the example to use a custom-2-12288 machine type, which worked when I tested a Pixie deploy with px-sock-shop on a new GKE cluster with those resources.

Good idea from @vihangm to just use a standard instance type. Verified on a test cluster that PIxie and px-sock-shop both deploy and run successfully, and scripts execute successfully.


Google drive batch copy

Currently i'm using this to copy drive files to my account but after 300 - 500 files i got error "User rate limit exceeded" until next day.
I'm also tried batching request, still getting error

There is a limit to the number of requests that you can make in a day and batch does not help you with this limit.
Lets say my quota is 20 and I send four batch requests with five requests in each request to batch.   I have still blown out my quota of 20 because the total number of requests within the batch is 20.
There is no purpose to batching other then removing send time on your server.     As for the file upload quota it is not documented because google tends to change it a lot.    Last I heard it was around 50 per user.   You seem to have been lucky to get more then that.
This isnt an issue with the client library this is an issue with Quotas in Google APIs


Welcome email sent to user just after signing up

🛠 Fixes Issue

Closes #134
👨💻 Changes proposed
Welcome email sent to user on signing up

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@KaizenGirl1111 Done 🤩

@Siddhesh777 don't worry about the email content- it can be something like thank you for signing up with us and I'm sure you must have written good stuff


set up json5 completion demo and handle edge cases

this adds working completion in a lot of cases, but there are some broken edge cases
here are some examples of the working completions across json4 and json5, both improvements and existing
completion-examples.webm
Todo:

tests! (I learned I need to call state.focus() before state.setCursor() to mock autocomplete!)

closing because #36 is the real way to do this, and I will move the hover fixes into their own PR


Support Podio Comments and Attachments

Add support for Podio comments and attachments.
Aha, Podio Bug or Trello Card Link:
related to: https://trello.com/c/9E2sUtNB/324-migrate-fedramp-bugs-to-podio
Testing Procedure or Link:

[ ] import a Trello card with comments, attachments, members, and labels with scripts/podio-bug-forwarding/trello_to_podio.py.

Release Related Information (e.g. Migrations or Major Architectural Changes):
n/a
Security Review (e.g. link to SIA or brief explanation of how this does/doesn't impact security)
See feature design document or contact S&C for ideas on what to consider
Request review from @Everlaw/securityanalysts if review is required

@ryanblais , I don't completely understand.  This PR seems to include some commits by you.  I'm not sure how that happened.


K8 HA docs - out of date etcd yaml file link

Environment
RHEL7/UBUNTU
Dashboard version:
Kubernetes version: LATEST
Operating system:
Node.js version:
Go version:
Steps to reproduce
download yaml from here: https://kubernetes.io/docs/admin/high-availability/etcd.yaml
Observed result
note that the version of the etcd container is way out of date:
kind: Pod
metadata:
name: etcd-server
spec:
hostNetwork: true
containers:

image: gcr.io/google_containers/etcd:2.0.9
name: etcd-container
command:

/usr/local/bin/etcd```

Expected result
keep the version up to date or warn readers that they should check for the latest version.
kind: Pod
metadata:
  name: etcd-server
spec:
  hostNetwork: true
  containers:
  - image: gcr.io/google_containers/etcd:3.0.17
    name: etcd-container
    command:
    - /usr/local/bin/etcd```

##### Comments
this was extremely confusing as the 2.0.9 version of the container was missing root certs which prevented the etcd containers from running ... the issue had obviously been fixed later on ... but the docs should be clearer here.. a simple hint to say 'edit the yaml and update the image version with whatever the latest is' would have been great....

Doesn't look like the bot is auto-closing this now that the PR is merged, so I'm closing this.


Update Info.plist

urls that facebook's sdk connects to must be whitelisted in the info.plist with NSAppTransportSecurity

@Harout360 Merged. Thanks for your PR! :-)


Removes csslint in favor of stylelint

Description of the Change
Includes the "standard" config (no relation to the js formatting style) which is a bunch of accepted best-practices. Explicitly disables failing rules. Those that I think would be useful in the future I've marked with a TODO, at which point we can refactor rule-by-rule and remove the blacklist.
Alternate Designs
Leaving csslint in place, but it is aging and the project wants to merge with stylelint anyway.
Why Should This Be In Core?
To unblock #16731, which can't land because it won't pass lint due to csslint being unable to parse css custom properties.
Benefits
A healthy ecosystem of rules, a modern parser and infrastructure for linting stylesheets.
Verification Process
Remove some of the rule blacklisting in stylelint.config.js and verify linter errors show up in ./script/lint

cc @simurai @matthewwithanm @Arcanemagus


Pre-allocate needed columns in abp_pcap_detection example

Description

AbpPcapPreprocessingStage requests needed columns to be pre-allocated
Add an end-to-end test for the AbpPcapPreprocessingStage (part of #849)
Add tests/tests_data/abp_pcap.jsonlines which is the first 20 lines of the much larger examples/data/abp_pcap_dump.jsonlines (200MB) which is not downloaded in the test CI stage.

fixes #797
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


Update to fix hadolint warning

Please provide a description of this PR:
Testing hadolint 2.7.0 and this change was identified.
./samples/bookinfo/src/productpage/Dockerfile:17 DL3045 warning: `COPY` to a relative destination without `WORKDIR` set.
./samples/bookinfo/src/productpage/Dockerfile:20 DL3045 warning: `COPY` to a relative destination without `WORKDIR` set.

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
aa8eaea66cb4ff695f5a8d92f0bb8072ea44ad03
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
aa8eaea66cb4ff695f5a8d92f0bb8072ea44ad03
link
unknown
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio


photons_control.device_finder error

Back with one other challenge. Thank you again for creating this. It really resolves my biggest annoyance with my Beam (the inability to trigger animations via HomeKit).
I installed the most recent release on a fresh machine yesterday, and started running into a challenge. Photons works great for a while (I have Interactor running as an agent via launchctl), but then I get the below error and the service stops responding. Bouncing it via launchctl returns everything to normal, but it's happening every few hours. Any ideas?
Some additional context - macOS 10.15.6, and working behind ExpreessVPN
2020-07-29 09:25:02,752 ERROR   photons_control.device_finder Something went wrong in a search
Traceback (most recent call last):
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_control/device_finder.py", line 736, in search_loop
async for device in self.finder.find(refresh_discovery_fltr):
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_control/device_finder.py", line 819, in find
_, removed = await self._ensure_devices(fltr)
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_control/device_finder.py", line 795, in _ensure_devices
serials = await self.searcher.discover(
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_control/device_finder.py", line 771, in discover
serials = await self._serials()
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_control/device_finder.py", line 761, in _serials
_, serials = await FoundSerials().find(self.sender, timeout=5)
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_app/special.py", line 70, in find
return await self.found
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_app/helpers.py", line 1137, in await
return (yield from self.info["fut"])
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_app/special.py", line 85, in find_serials
return await sender.find_devices(timeout=timeout, broadcast=broadcast, raise_on_none=True)
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_transport/comms/base.py", line 281, in find_devices
found, _ = await self.find_specific_serials(None, **kwargs)
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_transport/comms/base.py", line 289, in find_specific_serials
found = await self._find_specific_serials(serials, **kwargs)
File "/Users/accountname/.photons-core/lib/python3.8/site-packages/photons_transport/comms/base.py", line 307, in _find_specific_serials
raise FoundNoDevices()
photons_app.errors.FoundNoDevices: "Didn't find any devices"
2020-07-29 09:25:14,977 INFO    photons_transport.transports.udp Creating datagram endpoint	address=('XXX.XXX.XXX.XXX', 56700)	serial=XXXXXXXXXX

oops, nice find :)
I'm nearly finished what I started last week so this should be released this weekend or next weekend.
In the meantime, master also has a fix to a memory leak.
So in your virtualenv, do something like
pip uninstall lifx-photons-core
pip install -e /path/to/photons/modules

And I'll let you know here when the new version has been made :)


Add update password command

https://github.com/SonuBardai/lockbox/issues/69

Codecov Report

Merging #79 (70b8e80) into main (71da277) will decrease coverage by 5.05%.
Report is 9 commits behind head on main.
The diff coverage is 9.43%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   92.50%   87.45%   -5.05%
==========================================
  Files           9        9
  Lines        1547     1690     +143
==========================================
+ Hits         1431     1478      +47
- Misses        116      212      +96

Files Changed
Coverage Δ

src/cli/mod.rs
73.46% <0.00%> (-14.34%)
:arrow_down:

src/store/mod.rs
94.34% <0.00%> (-4.74%)
:arrow_down:

src/cli/commands.rs
82.38% <4.34%> (-10.18%)
:arrow_down:

src/pass/mod.rs
92.14% <11.76%> (-7.86%)
:arrow_down:

src/cli/args.rs
87.39% <46.66%> (-2.74%)
:arrow_down:

... and 1 file with indirect coverage changes


[FEATURE] Profile Pictures

I think it would be interesting (and cool) if each profile can have a "profile picture" to better identity different profiles. I don't even know if this was possible. This would also require some way to select custom ones saved on the user's computer, which could maybe use a similar UI to #5
Example:
-A Frackin' Universe pfp for a Frackin' Universe profile
-A Starbound logo pfp for a vanilla profile
(can't put the enhancement label but this is an enhancement in my mind)

Definitely possible, but I wouldn’t know a good way to determine the icon for most mods, without the user doing it themselves.
More pressing things to add at the moment, but this is definitely a cool idea

Yeah, it can be a side feature in case you want to add something to the application

Likely not happening unless I decide to rewrite this whole thing in Rust or something idk
(mostly posting this as a test for a discord webhook)


Driver class not appearing in the selection bar of the datasource editor

I added a JDBC driver in the Preferences.
jTDS
Class Name : net.sourceforge.jtds.jdbc.Driver
Status : ready
Then, in the 'Ontop Mappings' tab (under Datasource manager), I cannot see it in the suggestions.

Hi,
The options of jdbc Driver list are predefined. Those drivers in the list are what officially support. If it is not in the list, you can just manually input it there.
Note that jTDS is not among the official  supported JDBC Drivers.
As far as I remember, there is some known issue with Ontop.
If you want to use a MSSQL database, I would suggest you use the official JDBC drivers from Miscrosoft.

Thanks again !


MB-6076 Bump uswds from 2.9.0 to 2.10.0

Description
This PR updates the uswds version on the project. Dependabot tried to make this update for us on Dec 21st, but there were some design changes in happo (which I am opening this PR to review) and some issues with the e2e tests (which I am hoping don't happen again, but if they do, I will seek help from an engineer).
slack thread: https://ustcdp3.slack.com/archives/CTNTFJSBA/p1608588824279900
Reviewer Notes
Design:
When you look in Happo, you will see that the icons have changed for the alerts. I don't think this brings about a breaking change. I also want to note, that as of right now, we do not log the icons within the alerts on our icons page in storybook, because they get imported with the Alert component and aren't used anywhere else. Because of this, I advise we accept this change and make sure we update the Alert with the correct icon in our Sketch Library.

The only other "change" I see in happo does not seem to actually be a change. Personally, I cannot see anything different in the before/after images.

Setup
Add any steps or code to run in this section to help others prepare to run your code:
yarn install
yarn storybook

Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Original Dependabot PR
slack thread

Messages

:book:
:link: MB-6076

  Generated by :no_entry_sign: dangerJS against 13a8e05a79ba8a21d3e241a0b586eeb00abc004c

Messages

:book:
:link: MB-6076

  Generated by :no_entry_sign: dangerJS against 13a8e05a79ba8a21d3e241a0b586eeb00abc004c

This is blocked pending a fix for this issue: https://github.com/uswds/uswds/issues/3909

This is blocked pending a fix for this issue: https://github.com/uswds/uswds/issues/3909

Update 1/13: issue still "in progress" on USWDS sprint board

Update 1/13: issue still "in progress" on USWDS sprint board

https://github.com/uswds/uswds/releases/tag/v2.10.1 has been released, so we should be able to try this again @Shkeating

This isn't just the integration tests - starting the application (ie, make client_run) results in a JS error right off the bat.

I am not sure why, but one possibility is that we have 2 different versions of USWDS installed because ReactUSWDS is not caught up with 2.10 yet. The latest version of ReactUSWDS implements USWDS 2.8.0. @Shkeating IMO we should version lock our USWDS to whatever our version of ReactUSWDS requires, which would mean 2.8.0.

Just a heads up ... a dependabot update PR came through for uswds 2.10.2 (#6045).  I closed it since we have this PR to work through the 2.10.x upgrade.

This isn't just the integration tests - starting the application (ie, make client_run) results in a JS error right off the bat.

I am not sure why, but one possibility is that we have 2 different versions of USWDS installed because ReactUSWDS is not caught up with 2.10 yet. The latest version of ReactUSWDS implements USWDS 2.8.0. @Shkeating IMO we should version lock our USWDS to whatever our version of ReactUSWDS requires, which would mean 2.8.0.

I think that's a good point. Should I just close this PR then? Or should I try to coordinate with the folks currently working on reactuswds to use 2.10 in the next realease (even if they dont have component parity to it yet)?


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31683

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/32069

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/46378

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58323

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95076

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107276


Client ID not provided when calling API endpoints

https://github.com/justintv/twitch-js-sdk/blob/master/twitch.js#L38-L42
This should either include the client id in the header of the ajax call (per this blog post) or append it in params.
I tried adding the client id in the headers of the ajax call - that did not work. What did work was to append it to params.
params.client_id = Twitch._config.clientId;

Did you get it working playitcool, this recently broke... :-(

I hacked it quick pn line 37 of Twitch.js
It seems they changed the API so that the client_id is needed with some calls now previous it was not needed.
$.ajax({
  url: url + '?client_id=' + Twitch._config.clientId + '&' + $.param(params),
  dataType: 'jsonp',
  timeout : REQUEST_TIMEOUT
})

I now this is messy but, hey it works for now, for me... :-)

Here some one made a better PR
https://github.com/justintv/twitch-js-sdk/pull/21
See what they did, this fixes it.

Hey fasani, thanks for the update. And yes way better PR 💯


add documentation for get model group API

Description
add documentation for get model group API
Issues Resolved
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Should this be backported to 2.12?

Should this be backported to 2.12?

Yes

Should this be backported to 2.12?

yes that would be great


REST api docs: add prototyping interactions

#22
#21  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jkatz-figma and the rest of your teammates on  Graphite


how to test ?

what is the difference of this three .py file ? evaluate_deeplab.py and test_model.py and deeplab.py
which one is for test ? how can i run it ?

I guess it is the deeplab.py.But when I test it,the right picture shows the yellow background with nothing segmatic infomation.Has anyone test it successfully?Please help.


fix(customElement): replace template tag with i

This fixes a bug where the icon cannot render in IE where the template is invalid

@rmja I went ahead and added one test just to make sure the <i> is not replaced and to document in the test why it is there. Nice catch!


Link of table of plugins in metadata ingestion page is broken

Describe the bug
Document error,  the link of table of plugins in metadata ingestion page is broken, see the following screenshot.
Screenshots

Desktop (please complete the following information):

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

Additional context
Add any other context about the problem here.

This is now fixed


[QuickFix] Support more detected lint fix (like prefer_final_in_for_each)

Hi,
When adding a linter on a projet, you might get a lot of lint, and the analysis server already does a pretty good job at giving fixes, but some that seems trivial are not pick up.
As an example, there is prefer_final_in_for_each :

I'll update when I encounter more.

Thanks for pointing out the opportunity to add a fix. This has now been added and should be available in the next release (https://dart-review.googlesource.com/c/sdk/+/152618).
When you find others, please do report them. We value the feedback.


Create a bytepacking library for Kakarot: optimizing storage of bytes array

Currently, Kakarot is developed using a naive implementation.
As such, bytes (8-bit words in memory) are stored in a single felt. This means that a felt (up to 251-bit of information) is used to store only 8 bits.
The aim of this issue is to pave the way for byte packing.
Best outcome: 31 bytes per felt -> maximum efficiency
Mild outcome: 16 bytes per felt -> ok efficiency
Bad outcome: 1 byte per felt -> current efficiency

@danilowhk is currently assigned

I can do this one

I believe @ClementWalter and @danilowhk will tackle this issue in the coming days:)

Yes haha :)

Closing this as bytes16 packing was merged 3 days ago. Should we want to investigate further with, e.g. bytes31 packing, we'll create another issue, but this one is AKAIF resolved.


nixos/xdg-terminal-exec: init module

Description of changes
Add a NixOS module for already existing package xdg-terminal-exec
CC xdg-terminal-exec maintainer: @quantenzitrone

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

XDG Terminal Execution is a Spec proposal, while xdg-terminal-exec is a reference implementation of that spec. So what are we enabling? The spec? The reference implementation? The proposal? The configration is afaik part of the spec, so are the options for the utility? For the spec? For any xdg terminal execution utilty implementing the spec?
There are as far as I know no alternative implementations of the spec, but i think it would still make sense to add a package option.

Thanks for pointing out this!
Actually, there's other implementation of it like https://gitlab.com/OroWith2Os/xdg-terminal-exec and https://codeberg.org/mkhl/xdg-terminal-exec , found in https://gitlab.gnome.org/GNOME/glib/-/issues/338
I would be absolutely glad to add the package option in case that if someone someday needs to use other implementation.
To be more clear, would you like to change pkgs.xdg-terminal-exec 's description here https://github.com/NixOS/nixpkgs/blob/ac025b8bbb3182b595912516e82fb40fc26c6b29/pkgs/by-name/xd/xdg-terminal-exec/package.nix#L32 to like

A reference implementation of the proposal for XDG terminal execution utility.


Padding button

Hello, I'm having difficulty resetting the FilledButton padding, could someone help me please?

FilledButton(
  style: ButtonStyle(
    padding: const WidgetStatePropertyAll(0.0),
  ),
)


SameSite workaround change is breaking custom cookies

https://github.com/mendix/cf-mendix-buildpack/commit/3af6b067254f4ad9601222b260dc56339c89fb7b
We have custom cookies added in a custom request handler that do not support HttpOnly which you are now adding. This unwanted infrastructure change has been added to our test and staging environments without warning. And, I'm guessing we will have a production issue upon the next reboot.

@icyitscold could you please give more details regarding this issue? How HttpOnly is affecting functionality? We will revert these changes for now.

Sure.. We have a CustomRequestHandler for our Login page which will add a our own JWT cookie to the response. We have a custom front-end codebase that interacts with mendix via custom APIs and uses the JWT token for access. The vue codebase needs to read the cookie to present different user experiences based on the security profile, and to send token along as an authentication header for api requests.

Thanks for your feedback and the explanation of your use case.
We have reverted the SameSite workaround pending a fix without the HttpOnly attribute. This issue can be closed.


Expose Apple reachability observer

Changes:

Reachability observer is now exposed for binding use
Reachability observer changed to be singleton
Reachability observer can now register multiple callbacks, and unregister them
Updated sync client code

I think I may need to add a dummy version for platforms that don't support reachability (i.e. watchOS), similar to how our other platform-specific implementations work.

Why bother with this when Cocoa could just use the SystemConfiguration reachability API directly?

Don't you have to wrap that API anyways, per the famous Apple sample project? If you prefer just using SystemConfiguration directly, I can do that too.

I think the best course of action is to just build out whatever I need for Reachability in the binding itself, and leave the object store stuff alone.


[Question] Java 8 compatability

Hello,
is there any java implementation that might be compatible with Java 8+?

jNetPcap relies on JDK's foreign function feature that was introduced in JDK-19. So unfortunately it will not be able to support any JDKs below 19.
The main purpose of rewrite of jnetpcap was to not have any reliance on any external JNI based libraries as v1 had due to foreign finction APi being builtin. This way jnetpcap is available on any platform that has a JDK 19 or above and can run native libpcap.


Periodic flush on in_tail plugin for multiline format

When using the in_tail plugin with multiline format and format_firstline the plugin will not generate an event until the next first line is detected (expected behaviour as we can't know that the multiline event has ended until the next first line shows up) however, it is reasonable to expect that a multiline event will happen on a short period of time so the event could be flushed on either a new first line or a configurable timeout, this is useful on files with low activity where the next first line can take a long time to appear.
Feature request:

Add a parameter to the in_tail plugin to be able to configure the multiline event timeout.

Just an idea. How about having something like define_lastline?
For Rails log, it would be like
define_lastline /Completed/

@sonots it wouldn't work for events where the last line is undefined,  e.g. stack traces, which happen to be the main reason for this feature request.
Also, if you can define a last line then you can define a multiline format with a regular expression matching the entire multiline event and not define format_firstline, accomplishing the same result.

+1 on this feature request
I have exactly the same problem when dealing stack traces in log:

I have to use the multiline configuration;
I can’t define the end of the new log to be send;
the error log will not be sent until a new firstline is parsed, which can be very long!

+1

Does someone handle this issue?
Yeah, this feature seems good for multiline users.

I wrote patches for https://github.com/fluent/fluentd/issues/668 - https://github.com/kikumoto/fluentd/commit/396d5a6bc3daf7739a93778c0671b9854c935ce5 .
These patches were forked from v0.12 branch.
I was wondering to decide if I should create pull request or not for this issue because I am not sure how to test it.

Sending PR is better for users to test your patch.

OK. I will.
Thanks.

This is fixed by #775

@pavel-kolla-kampiki this.


Dynamic importing problems

importProtoFile does not clear the errors list between calls
Errors returned by importProtoFile are formatted differently to the same errors when generated by protoc
When installing the packaged version of protobufkdb, not all of Google's .proto files are available

Fixed in 1.0.0-rc.2

Fixed in 1.0.0-rc.2


since Kade hates HealthDisplay on ScoreBar, this only fixes NPS not showing if Accuracy is disabled

Fixes #841

if this is supposed to be this way,
I'll change it that the NPS option only appears if Accuarcy is enabled

you happy? xD


fix: registration should use internal IP so that we can use tags for firewall rules

This PR is included in version 1.0.8 :tada:


result replace

PR summary
When there is not a single line, the first line has been modified to appear after /**.
cause
The reason is that when using vscode, the first line is treated as a footnote, which is not visually pleasing. Oh, of course, with jsDoc, ctrl + click, intellisense, and documentation work well.

as-is

to-be

Thanks for raising this! I'll try and see if there's a cleaner solution than a regex, but I feel like I investigated that before so this might be the only solution.

Fixed in 1.5.1!


Output files' filename hashes are incorrect

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: Angular 11
We could reproduce the issue with Angular 12 and Angular 13 as well, with different — faulty — outcomes.
On Angular 12, the issue affected both the main.js and polyfill.js output files in the distribution build. Based on our initial testing, in Angular 13 the issue only affects the scripts.js file in the distribution build.
Description
It seems that some output files' file name hashes are generated incorrectly, when building with output hashing (e.g. outputHashing = all in angular.json). This can cause issues e.g. for Angular applications served from CDNs, where only changed files are uploaded, and the files are diff’d based on their revhash in the filename.
In our concrete case (Angular 13, having outputHashing = all in angular.json), when changing the TypeScript target version from es2017 to any of es2019, es2020, or es2021 in the project’s tsconfig.json, then rebuilding the project, the file name hash of the generated output file containing global scripts (in our case, the file is named per the default configuration scripts.js) does not change, even though the contents of the scripts.js generated output file itself changes.
The expected behaviour is that the revhash generated into any output file’s filename should change if (and only if) the final contents of the output file changes.
🔬 Minimal Reproduction

Clone https://github.com/tresorit/angular-filename-hashing-bug-reproduction.
Run npm ci to install dependencies.
Run ng build --configuration=production (with the default es2017 target in tsconfig.json).
Observe the contents of the output dist/angular-filename-hashing-bug-reproduction/scripts.{revhash_1}.js file to be try{console.log()}catch(c){}.
Change the compilerOptions.target to es2019 (or es2020 or es2021) from es2017 in tsconfig.json.
Run ng build --configuration=production.
Observe the contents of the output dist/angular-filename-hashing-bug-reproduction/scripts.{revhash_2}.js file to be try{console.log()}catch{} (different from the output from step 4).

It’s a long shot and we’re not sure whether it’s even connected, but we’ve found that hashing for the scripts doesn’t use contenthash, which might be relevant:
https://github.com/angular/angular-cli/blob/d18469eb3f09f9d38c6c2c52027eb2f6a5c50c9b/packages/angular_devkit/build_angular/src/webpack/utils/helpers.ts#L41-L46

Closed via https://github.com/angular/angular-cli/pull/22612


Questions about maintainability

Hey! Thanks for your project! I always have concerns about integrating libraries that are only maintained by a single person, because they often get abandoned eventually. Can I ask how regular updates to the DataTables.net library will be incorporated into your port? Is there a streamlined process to do this or does it take a lot of manual labor to accomplish?

Hello!
So, this project (vue-data-table) was inspired by DataTables.net. I created it because I wanted some Vue component similiar to DataTables.net, but free of jQuery. I built VueDataTable from scratch in such way that would resemble DataTables.net in look and functionality. Therefore, this project won't incorporate updates from DataTables.net
I plan to continue to work on this project for at least this year, fixing bugs and adding some functionalities (for example, I plan to add option to search within a single column, and so on). Even if I stop working on this project, I'll probably accept Pull Requests and incorporate them. Moreover, if I really left it away, I can transfer ownership of the project before that happen

I appreciate the answer, obrigado!

Just to let you know, I expect to keep working on this plugin untill the end of 2023.
However, the future is unknown and I may stop working on it soon or later than planned.


Proofreading translations

Changed a few files + added the PSD for the loading screens.

I need to check them Ingame First. Pretty Sure some of them too many characters and would display pretty ugly

I also fixed a couple lines that were too long, only one that's one character off is 'Blowjob Master' but everything else works great!


NetworkUpgrade::NU5 and network protocol version

Is your feature request related to a problem? Please describe.
We want to add a NetworkUpgrade::NU5 network upgrade variant, and a network protocol version for NU5.
As part of this change, we need to write a draft NU5 ZIP.
Describe the solution you'd like

[x] write a draft NU5 ZIP

we don't need to have a list of included ZIPs, just the branch id / numbers / etc.
https://github.com/zcash/zips/pull/446

[ ] add a NetworkUpgrade::NU5 network upgrade variant

https://github.com/ZcashFoundation/zebra/blob/128643d81e357157bfb3af3725bac653abfb402e/zebra-chain/src/parameters/network_upgrade.rs#L16

[ ] add the NU5 consensus branch ID

https://github.com/ZcashFoundation/zebra/blob/128643d81e357157bfb3af3725bac653abfb402e/zebra-chain/src/parameters/network_upgrade.rs#L89

[ ] add a network protocol version for NU5

https://github.com/ZcashFoundation/zebra/blob/128643d81e357157bfb3af3725bac653abfb402e/zebra-network/src/protocol/external/types.rs#L46

Describe alternatives you've considered
These changes are required for NU5.
Additional context
NU4 ZIP: https://zips.z.cash/zip-0251
NU5 ZIP: https://github.com/zcash/zips/pull/446

We've talked to the zcashd team, and they're happy for us to write the draft NU5 ZIP.

We've talked to the zcashd team, and they're happy for us to write the draft NU5 ZIP.

The draft ZIP is at https://github.com/zcash/zips/pull/446 , it has passed initial review.

It looks like NetworkUpgrade::NU5 should be NetworkUpgrade::Orchard ?

No. Orchard is the name of the proposed new shielded pool, not the name of the upgrade (which as proposed includes things other than Orchard). We made this mistake for Sapling (naming the upgrade after the pool), and it has caused non-trivial confusion.

So, to be extra clear. The name of the upgrade will be NU5 even if previous ones had names like Sapling, Blossom, etc. Is that correct or NU5 will actually have a name(different than Orchard)?

Forget https://github.com/ZcashFoundation/zebra/issues/1797#issuecomment-787092788, the code name is actually NU5 according to the draft zip: https://github.com/teor2345/zips/blob/zip-252-nu5/zip-0252.rst#terminology
Thanmk you @str4d

So, to be extra clear. The name of the upgrade will be NU5 even if previous ones had names like Sapling, Blossom, etc. Is that correct or NU5 will actually have a name(different than Orchard)?

The code-name for the sixth Zcash network upgrade has not been chosen yet.
I've updated the draft ZIP to reflect that:
https://github.com/zcash/zips/pull/446/files#r584385297
There are three possible outcomes for Zebra:

There is no code name chosen, and the enum keeps getting called NU5
The community chooses a code name, the enum keeps getting called NU5, and everything works
The community chooses a code name, we use fastmod or a similar tool to easily change NU5 to that name

(We don't need to make that decision now.)


Remove unused configuration files like webpack config from projects which use rollup

Example: neeto-form-frontend

Closing this issue. neetoEditor does not need a Webpack config. But the documentation served through the storybook requires Webpack as a dependency.
cc: @Amaljith-K


Revert "Upgrade to Ruby 3.0"

Reverts connorshea/vglist#2420

Upgrading Ruby caused downtime in prod for some reason, need to figure out the source of the issue.


notebook update

followed Chad's comments and updated the notebooks.
ARD vs not corrected data is still pending

reviewed by me.


Accept more types as query parameters

Implement serialization support for

python types: tuple
pandas types:

all but period, interval, pyarrow

numpy types:

all but void, complexfloating

pyarrow support was not implemented as it would either require more ifs in the recursive packing function, making it (driver's hot-path) slower for non-pyarrow use-cases. Or alternatively, transformers would have to be used making pyarrow type serialization rather slow.

Why don't we have a user-specified encoding used for converting python:bytes->bolt:String?


what about bitbucket server OAUTH config info

Hi
Under OAUTH config info, i see for bitbucket cloud info is there . but what about bitbucket server info ?

Currently Bitbucket cloud is the only supported configuration for oauth on-prem.


How does AMC validate the pruned model to get reward?

Hi, thanks for your great work!
However, I find that it always validate the original model under "train" mode.
In env.step(), it validates the model(line 123) to get the reward after prune_kernel() operation(line 97).
But the model will be pruned only under the "export" mode as line 249 to line 261.
So what's the problem?

Hi, during the RL process, the kernel will be pseudo pruned by setting some weights to zero. It will produce the same result as the real pruning.


Convert dates from string

Dates in JSON are encoded as strings. It would be great if the client converted theses strings to Date objects automatically. We can create a generic transformation function which will look for all properties ending with "At" (e.g. "createdAt", "modifiedAt"), and convert the string value (which must be in ISO format) to Date.

done


About Speech Enhancement scores on SUPERB leaderboard

Hi!
Thanks for the great repo!
I find that CCC-wav2vec 2.0 performs especially well on SUPERB SE task, surpassing WavLM Large with a large margin.
I am trying to reproduce it but I not yet successfully get the similar score. (PESQ around 3)
May I ask how did you fine-tune CCC-wav2vec 2.0 on SUPERB SE?
Specifically, what are the tuning hyper-parameters? (e.g. batch size and learning rate)
Thanks!

P.s. I tried the default batch size and learning rate 1e-4 and 5e-5, and adding --upstream_feature_normalize to apply layer norm on the representation, the best result I get is around 2.6 PESQ.


improve rspack progress style

What problem does this feature solve?
webpackbar has more pretty progress style than progressPlugin, we may following webpackbar way to improve the progress style.

What does the proposed API of configuration look like?
No api needed, only change the style

assign it to me, I'll work on it

assign it to me, I'll work on it

thanks in advance


What is the step-by-step process for two-stage address translation

In the latest pdf build (5/23/23) of the Privileged Architecture, the step-by-step description in 5.3.2 Virtual Address Translation Process is clear and concise for single stage translation. However, when we move to two-stage translation, the differences specified in  9.5.1 Guest Physical Address Translation (e.g., hgatp substitutes for the usual satp) seem to be incomplete.
For example, applying step 7 in 5.3.2  (as updated by 9.5.1) "if the original memory access is a store, also set pte.d to 1" is a bit confusing when trying to apply it to G-stage translations. The intent is probably for all traversed G-stage PTEs to have A=1 and, if the operation that kicked off the original translation was a STORE, the final G-stage PTE (i.e. pointing to the SPA of the page of the STORE) needs D=1. We should have a clarification of some sort for this.
Furthermore, the updated steps in 5.3.2 do not provide any guidance on how to update the G-stage PTE that points to the VS-stage leaf cell. Presumably, if the VS-stage leaf cell is updated, this G-stage that points to it must have D=1.
It appears to me that the various models  (SPIKE, RISC-V, and QEMU) are missing this last step (actually, SPIKE is currently being corrected based this issue being raised in  Are G-stage D bits set correctly as a result of setting a VS-stage D bit? #1447 with the changes in
A/D updates in G-stage PTE #1448)
I suggest that we add clarifications to the Privileged Architecture in the form of a step-by-step Two-stage Virtual Address Translation Process in 9.5.1 Guest Physical Address Translation. Alternatively, we  could add a normative description that explicitly calls out of these differences in two-stage translations.

Alternatively, we could add a normative description that explicitly calls out of these differences in two-stage translations.

The section 9.5.1 does call out these differences:

hgatp substitutes for the usual satp;
For the translation to begin, the effective privilege mode must be VS-mode or VU-mode;
When checking the U bit, the current privilege mode is always taken to be U-mode; and
Guest-page-fault exceptions are raised instead of regular page-fault exceptions.
For G-stage address translation, all memory accesses (including those made to access data structures for VS-stage address translation) are considered to be user-level accesses, as though executed in U-mode.
Access type permissions—readable, writable, or executable—are checked during G-stage translation the same as for VS-stage translation. For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions are checked as though for a load or store, not for the original access type. However, any exception is always reported for the original access type (instruction, load, or store/AMO).
The G bit in all G-stage PTEs is reserved for future standard use.

We agree that section 9.5.1 calls out those differences. However, applying those differences to the single-stage step-by-step virtual address translation process does not yield a complete two-stage step-by-step description. There is no mention in these steps, for example, of when to set the D bit in a G-stage PTE as a result of the setting of an A bit in a VS-stage PTE.
Since people seem to be relying on these step-by-step instructions when creating models or RTL implementations, it would be helpful to create a version that explicitly and completely covers two-stage translation.

Probably would be useful for writing the complete ACT tests as well.
On Tue, Sep 5, 2023 at 12:09 PM Ken Dockser @.***>
wrote:

We agree that section 9.5.1 calls out those differences. However,
applying those differences to the single-stage step-by-step virtual
address translation process does not yield a complete two-stage
step-by-step description. There is no mention in these steps, for example,
of when to set the D bit in a G-stage PTE as a result of the setting of an
A bit in a VS-stage PTE.
Since people seem to be relying on these step-by-step instructions when
creating models or RTL implementations, it would be helpful to create a
version that explicitly and completely covers two-stage translation.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/1103#issuecomment-1707175122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJSQXZJGYILHZVBX4A3XY52HDANCNFSM6AAAAAA4DJNDPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Or (to Ken's and Ved's last posts) just add one more bullet to the section 9.5.1 bullet list that explicitly makes clear when to set the D bit in a G-stage PTE as a result of the setting of an A bit in a VS-stage PTE.

Section 9.5.1 states:

For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions are checked as though for a load or store, not for the original access type.

For added clarity, the phrase "permissions are checked as though for a load or store" could be expanded to "permissions, A, and D bits are checked as though for a load or store".

"permissions, A-bit, and the D-bit are checked" reads in a confusing way.  I assume this is trying to refer to setting of G-stage A&D bits as a function of the VS-level PTE read or write access (and not of the original access type)?
If so, then this might read better as:
For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions and the need to set A and/or D bits at the G-stage level are checked as though for a load or store, not for the original access type.

Also, consider expanding "for a load or store" to explicitly state "for an implicit load or store." The distinction between implicit and explicit guides the decision on the value reported in [h|m]tinst when a guest-page fault trap occurs.
As follows:
For a memory access made to support VS-stage address translation (such as to read/write a VS-level page table), permissions and the need to set A and/or D bits at the G-stage level are checked as though for an implicit load or store, not for the original access type.

The addresses in hgatp and the G-stage paging structures are supervisor physical addresses. Please clarify what the second bullet implies by "to support G-stage address translation".


[Bug] Logging in with<EMAIL_ADDRESS>does not give root priveleges

We have a root user confirmed in the Cognito user pool utilized by our Service Workbench instance but when we try to log in with that root user we're not granted root access instead we get a response to wait for the admin to approve. I'm following along straight from the SWB docs so it's not apparent to me what the issue is. Any help debugging would be greatly appreciated!

Hi! After deploying SWB, you should see a "Temporary Native Pool Password" output from the deployment script. Use this password and the email specified in the stage configuration file as rootUserEmail to log into SWB for the first time. This should prompt you to reset the password from the value that was provided as the "Temporary Native Pool Password".
After this, you can add users from within the SWB UI Users page by clicking "Add Federated User" and providing an email there. The user can navigate to the login page where they must specify "Sign up" and provide their desired values. If you do not add the federated user from within the SWB UI, the user will see the message that their application has been received and will require someone to use the "Add Federated User" workflow to have them gain access to the SWB deployment.
Thanks,
Marianna

We tried up another instance and got it to work by setting the root email as a different address than the one we first tried and it seems to have worked. You can close this issue. Thanks!


Document the accepted cryptographic mechanisms

Shall be as per https://www.sogis.eu/uk/supporting_doc_en.html
ARF specifies 1.3: https://www.sogis.eu/documents/cc/crypto/SOGIS-Agreed-Cryptographic-Mechanisms-1.3.pdf
@georgepadayatti @ntsbs @andreasabr @endimion  Please comment on this. We are facing a bit of an issue with interop as some wallets seems to be picking EdDSA over ES256 (ECDSA) algorithms. Lets use this issue to discuss in case you have an opinion. Mostly its enough we just document it as part of a table similar to how we documented the supported formats.

The reason to choose ES256 was that it is supported well by Keystore APIs of iOS and Android

The reason to choose ES256 was that it is supported well by Keystore APIs of iOS and Android

Or may be its the other way around? (Am not an expert, but a wild guess).
The SOGIS Agreed Cryptographic Mechanisms v1.2 (Release Jan 2020, New version is 1.3/Feb-2023) is specified in ARF and it mentions explicitly on EC-DSA. We need experts to comment here on ED-DSA and ARF Requirement 10?

You mean, it is well supported because it is a widely standardized and accepted signature algorithm?

Yep.

One question, what speaks against using both signature schemes?


VS install cleanup step of Dockerfile deletes vswhere from documented installation path

From the 4.8 SDK Dockerfile:
https://github.com/microsoft/dotnet-framework-docker/blob/5d8e932818fcf188618f18eab4c978cbd1e6a0e6/src/sdk/4.8/windowsservercore-ltsc2019/Dockerfile#L34
Presumably this is an image-size optimization, but it deletes vswhere.exe, which causes issues in tools that rely upon the documented behavior for vswhere:

Starting with Visual Studio 15.2 (26418.1 Preview) vswhere.exe is installed in %ProgramFiles(x86)%\Microsoft Visual Studio\Installer (use %ProgramFiles% in a 32-bit program prior to Windows 10). This is a fixed location that will be maintained.

(From https://github.com/Microsoft/vswhere/wiki/Installing)
I recognize that this image builds VS's build tools into a static location, but I'll have to bring in an outside vswhere.exe for the third-party tools that expect to find this tool, because I don't see it anywhere else in the image.

@mthalman - Can you look into the feasibility of preserving/adding the vswhere utility?

Thank you Michael and Matt!


Stop manipulating symlink targets

#288 partially fixed some issues when we use makisu just for the extract command under non-root, but caused other issues like described in #291 .
This change would stop makisu from manipulating symlink targets, and avoid all such issues. However, we still have to tackle this relative path problem again for hardlinks, which we are mostly avoiding today.

#288 was reverted.


Created progressBar component

Signed-off-by: asubedy<EMAIL_ADDRESS>Description
Created a Progress Bar component from here.
https://user-images.githubusercontent.com/51183483/147508038-9979b8af-8536-47e2-b19c-55e95df20396.mov
This PR fixes #
Notes for Reviewers
Signed commits

[X] Yes, I signed my commits.

https://user-images.githubusercontent.com/51183483/148646014-61473ad2-7319-4261-8d33-df7c83c5a25a.mov

@asubedy , we are not going to use plain css. We are going to use MUI Styled components as the only way of styling across all Meshery products. So, please change this implementation to use MUI styled components.

@asubedy , we are not going to use plain css. We are going to use MUI Styled components as the only way of styling across all Meshery products. So, please change this implementation to use MUI styled components.

Oh ok, will require some time to study about MUI styled components. Will make a PR after implementing the MUI styled components.

Sure @asubedy , no pressure. Take your time 😄

Thank you @asubedy 😄 . But, I don't see mui styled components being used here 😅 . Am I missing something here ?

I made a new file Progressbar.style.js and added all the MUI styles there, isn't this the way to do it? 😅 . I saw other files and this was how it was done so I proceeded this way. @sudo-NithishKarthik

@asubedy it'd be good to bring this to closure.

@asubedy it'd be good to bring this to closure.

I think it is completed, @sudo-NithishKarthik said there are no further changes required :she

we


Cancel button in activity log before action starts

Is your feature request related to a problem? Please describe.
When you accidentally paste twice and the second paste is queued, there is no way to cancel the second paste from the activity log until it starts
Describe the solution you'd like
Actions that get placed in the activity queue should be cancel-able immediately
Describe alternatives you've considered
Additional context

Dupe of #1306


[Idea] Getting started with Nix ❄

Introduction
As the date of writing (Aug 2024), I've committed myself switching to NixOS on my daily-drivers and a few servers. This repository reflects my current multi-profile NixOS configuration with Flake. I'd like to actively learn more about Nix, specially NixOS with Flake. In my view, NixOS is a revolutionary invention in the Linux world, as it offers a new paradigm of system configuration and package management. It is not only reliable and secure, but also fun and rewarding to use.
Background (Powered by GPT4)
What is Nix
Nix is a powerful package manager and build system for Linux and other Unix-like operating systems. It stands out from traditional package managers because of its unique approach to package management, emphasizing reproducibility, consistency, and isolation.

Reproducibility: Ensuring that the same software environment can be replicated across different machines, eliminating the "it works on my machine" issue.
Isolation: Allowing multiple versions of software to coexist without conflicts, enabling safer upgrades and better dependency management.
Atomic Upgrades and Rollbacks: Making it easy to update or revert to previous configurations with minimal risk.
Declarative Configurations: Facilitating the description of environments in a declarative manner, making setups reproducible and maintainable.

Why Use Nix

Consistency: Developers and teams can ensure that everyone is using the exact same environment, eliminating the "it works on my machine" problem.
Flexibility: Nix allows for the installation of different versions of the same software side by side, which is useful for testing and development.
Reproducibility: With Nix, you can recreate the exact environment where software was originally developed or tested, ensuring that builds and deployments are reliable.
System Independence: Nix can be used on different operating systems, making it a versatile tool for cross-platform development.

NixOS
NixOS is a Linux distribution built on top of Nix, providing all the benefits of Nix with an entire operating system managed in a declarative and reproducible way. It offers:

Consistent Environments: Every aspect of the system, from packages to system services, is defined in a single configuration file, ensuring consistency across deployments.
Ease of Maintenance: System upgrades and rollbacks become trivial, reducing downtime and minimizing risks during updates.
Flexibility: NixOS supports running multiple configurations side by side, making it ideal for testing and development.

Motivation
I want to share with the community an exciting opportunity to enhance our development processes and system management practices by adopting Nix and NixOS. As a community that values innovation and reliability, integrating these tools could significantly improve our workflow and environment consistency.
Check out my NixOS configuration here.
Next Steps
I propose we start by exploring Nix in our individual development environments to get a feel for its capabilities. We can then gradually introduce NixOS in our projects, testing its benefits in isolated environments before considering broader adoption.
I'm excited about the potential Nix and NixOS have to transform our workflows and would love to discuss this further with anyone interested. Please feel free to reach out to me if you'd like to learn more or have any questions.
I also started a community-oriented organization, namely NixOS-Pilots, which is a collaborative platform where developers, enthusiasts, and contributors from the Nix community converge to drive innovation and accessibility in NixOS software distribution. I'd like to engage the UTOSS community diving into the world of Nix and NixOS.
Let's work together to make our community even stronger with tools that promote reliability, consistency, and innovation.

Closed as not planned.