Translate to Arabic

Hi there 👋
Let's translate the course to Arabic so that the whole community can benefit from this resource 🌎!
Below are the chapters and files that need translating - let us know here if you'd like to translate any and we'll add your name to the list. Once you're finished, open a pull request and tag this issue by including #issue-number in the description, where issue-number is the number of this issue.

🙋 If you'd like others to help you with the translation, you can also post in our forums or tag @_lewtun on Twitter to gain some visibility.

Chapters
0 - Setup

[x] 1.mdx @giyaseddin

1 - Transformer models

[ ] 1.mdx @HishamKhdair
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx
[ ] 8.mdx
[ ] 9.mdx
[ ] 10.mdx

2 - Using 🤗 Transformers

[ ] 1.mdx @giyaseddin
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx
[ ] 8.mdx

3 - Fine-tuning a pretrained model

[ ] 1.mdx
[ ] 2.mdx
[ ] 3.mdx
[ ] 3_tf.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx

4 - Sharing models and tokenizers

[ ] 1.mdx
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx

5 - The 🤗 Datasets library

[ ] 1.mdx
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx
[ ] 8.mdx

6 -  The 🤗 Tokenizers library

[ ] 1.mdx
[ ] 2.mdx
[ ] 3.mdx
[ ] 3b.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx
[ ] 8.mdx
[ ] 9.mdx
[ ] 10.mdx

7 - Main NLP tasks

[ ] 1.mdx @giyaseddin
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx
[ ] 8.mdx
[ ] 9.mdx

8 - How to ask for help

[ ] 1.mdx
[ ] 2.mdx
[ ] 3.mdx
[ ] 4.mdx
[ ] 4_tf.mdx
[ ] 5.mdx
[ ] 6.mdx
[ ] 7.mdx

Events

[ ] 1.mdx

I 'd like to help with that.

I am happy to help 👍

Hey @dataubc @HishamKhdair thank you so much for offering to help! Which chapters / sections would you like to tackle first?

I'll start with the setup section

Hey @dataubc @HishamKhdair thank you so much for offering to help! Which chapters / sections would you like to tackle first?

I will be working on Transformers models - Introduction and NLP for now...

Hey @dataubc @HishamKhdair thank you so much for offering to help! Which chapters / sections would you like to tackle first?

I will be working on Transformers models - Introduction and NLP for now...

and I will keep working on the whole chapter then... @lewtun

Thank you @HishamKhdair - I've added your name to the list!

Hello @HishamKhdair has a nice PR for the first two sections of Chapter 1 if anyone here would like to give it a quick review: https://github.com/huggingface/course/pull/92

That sounds good @giyaseddin. At present, I am working on chapter 1 - Transformer models

Hi @lewtun I'd like to help out as well, I can do chapter 4 :)

Hello,
@giyaseddin @hkhdair @ahmedsamirio I'd like to know how the process is going on. I've assembled a team of volunteers who would love to help. We will start to work on Chapter 6 @lewtun for now until we here from you..

Hello there,
I can help if there is a space

i will work on all the rest of the chapters, i have checked the finished ones and found just the first chapter is done.

Thank you @mohamedakelportfolio @eng-aomar @asmayamani @ahmedsamirio @LayanCS.
I think it's perfectly fine for guys who want to contribute to pick from the unchosen chapters and work on them, or just ask the assigned chapters to help completing them.
I hope this amazing work would be done soon.

Hello @giyaseddin, if possible, I want to try translating chapter Transformer models, 2.mdx.

@giyaseddin I am thinking about organizing a project to perform machine translation from English to Arabic of the Hugging Face NLP Course to create a rough draft of the entire course in Arabic with the idea that we could then crowd source translation improvements. Would this be a welcome contribution?

Hey @davidrpugh I'd love to participate. I have already started such a thing a while ago. We can make it happen 😉

@giyaseddin I am thinking about organizing a project to perform machine translation from English to Arabic of the Hugging Face NLP Course to create a rough draft of the entire course in Arabic with the idea that we could then crowd source translation improvements. Would this be a welcome contribution?

I would be happy to participate! I'm Fluent in both Arabic and English and have learnt Arabic's grammar in depth... And even though it was a manga translation, I have bit of experience on english >> arabic translation :)
Really would love to bring such valuable course the arab community


Add a License

I currently have a fork with a few additional commits and improvements, although it's uncertain about the legality of this since there's no license (see https://github.com/harens/MacClam/pull/2).
@killdash9 has been contacted about this issue via email.

I've added an MIT license into the master branch.  I have no issues with you making improvements to this code.  I haven't had the time or desire to maintain it.


Client IP / REMOTE_ADDR set to 172.17.x.x when using userland-proxy=true

Hi,
I cannot manage to get the users ip on Docker 17.06.x. Same image version was running on another server with Docker 1.13.x fine. But in that Docker version is no userland-proxy.
Does anyone have the same issue with the newer x-CE versions?

I've now disabled IPv6 like this: https://askubuntu.com/questions/309461/how-to-disable-ipv6-permanently
Now I get real client IPs without setting userland-proxy to false or anything else.
Who needs IPv6... :D
Fyi: I'm on Ubuntu 17.04 with kernel 4.10.0-33.


conserver dying repeatedly with buffer overflow errors (sig6)

I'm running the latest conserver (8.2.6) on a Linux-x86_64 server with nearly 6000 console sessions.  Its worked fine literally for years, until yesterday, when it started dying with a buffer overflow error (and signal 6).
  If I reboot the server, then its stable for several hours before descending back into the same mess again.
The server had been up for over a week prior to this problem beginning for the first time.
I'm at a loss where to begin debugging this, and would appreciate any ideas/guidance/assistance.

@bstansell is there any other information that I can provide to continue with the investigation?

@bstansell  any updates?

@bstansell  as its now been over a month, will there ever be any follow up on this bug?

Over a year, and no response.

FYI:  you may want to take a look at
https://github.com/bstansell/conserver/issues/93

@agialluc  wow, thanks, that does look very relevant.  thanks for sharing !


Make map taller

I meant taller, not wider. Width satisfied me enough. It's okay now too but it's better to make it taller.

I guess I will need to add another breakpoint for tablet screens (decrease the page padding and make search -map - 50% - 50%) so it looks better.

@viktor-yakubiv Please have a look now :)

@Joozty we definitely should think more about everything not only about one breakpoint 😄
This is the window about 750px wide:

I would say some styles don't apply on safari. My looks better (it's not perfect but it doesn't overflow)

I start hating that everybody stops supporting Safari. But it's personal, I don't mind we don't support it 😄

I would support it if I had a mac. But like it's really hard for me to properly support it. Browserstack is too slow for me and it's hard to do something meaningful there. I will check it though. Especially the slowness warning.


templates not compiling

I can't get the sample templates to compile. Specifically the standard game template. I haven't tried the others yet. On notepad++ when I hit F6 while the standard_game.c is open, I choose raylib_compile_execute but it fails. What should I do?

choose raylib_makefile script. some templates require compiling multiple files and use a Makefile build system, a bit mote complex than compiling just one .c

Thanks a lot! I can't believe it's that simple!
Can you enlighten me on something? When I try running the makefile on notepad++ everything works fine. But when I try using VSCode and using the terminal there to run mingw32-make it works for a bit, but then gives me the error rlgl.c: undefined reference to __ms_vprintf. Why is it different based on which text editor I use, and how can I get VSCode to work?
You're amazing btw. Keep up the great work.

sorry, don't know why it happens, I didn't use the VSVode template... seems related to MSVC standard C library but don't know...

Closing this issue.


Make diffChars diff Unicode code points instead of UTF-16 code units

Forked from https://github.com/kpdecker/jsdiff/pull/395. (Sorry @luoxzhg, I couldn't figure out how to push to that PR for some reason so had to open a new one.)

Thanks for the contribution, @luoxzhg!


Add test-utils to ReactDOM definitions

react-addons-test-utils was deprecated with React 16, as most of its functionality was merged into react-dom/test-utils. The shallow renderer is now a separate package that can be typed on flow-typed, but these other definitions likely belong here as they're now part of react-dom.
This adds lib definitions to react-dom/test-utils, mostly borrowed from the flow-typed definitions for the now-deprecated react-addons-test-utils.
I haven't interacted directly with this API much, so a quick sanity check on the tests for this would be much appreciated :)

👋 @calebmer
(for some reason I can't assign a reviewer to this)


Pi Desktop with Raspberry 3 B+ but not wana boot from ssd...

Hi,
Former i use your BerryBoot aplication and everythinks works fine but after some years when I not use the PiDesktop run an update upgrade code and everythings go wasted....
So now I don't need to use SSD as boot system just from sd card but i need a PiDesktop-base file, for led control and something else but don't need the boot sequence...
Can you help me???
Thanks:
Bela

I wait your answer!!!


Support fs-group annotation to add PodSecurityPolicies

Allows setting eks.amazonaws.com/fs-group annotation on a
ServiceAccount or Pod. This will add an fsGroup with the
GID from the annotation into the PodSecurityPolicies. This
allows non-root containers to access the VolumeMount which
is owned by root with 600 permissions.

Just a spike of what the fsGroup fork of the mutating admission webhook from AWS would look like.
Design & implementation very open to change -- just wanted to get sample code in place for the proposal writeup. Tried to add some rigor and adhered to standards in case we can merge a PR of this to the upstream repo.


Fully tested filter

Find projects that are tested.

Please file an issue here with more details (e.g. what this classifier should be called): https://github.com/pypa/trove-classifiers


Custom print and parse ConstantOfShape

Solves #1975
The new custom assembly of onnx.ConstantOfShape is the same as the generic, just without the double quotes around "onnx.ConstantOfShape" and, most importantly, any DisposableElementsAttr is printed as a DenseElementsAttr.
Also fixed the onnx.Constant custom assembly to print any DisposableElementsAttr in the attribute dictionary as a DenseElementsAttr in the rare cases (when there are extra attributes or when the ElementsAttr type doesn't match the op type) where the attribute dictionary is written out as curly brace enclosed comma separated names and values.
I tested that the changes work on bidaf-9.onnx

Jenkins Linux s390x Build #9661 [push] Custom print and parse C... started at 14:46

Jenkins Linux amd64 Build #9642 [push] Custom print and parse C... started at 13:46

Jenkins Linux ppc64le Build #8707 [push] Custom print and parse C... started at 14:49

Jenkins Linux amd64 Build #9642 [push] Custom print and parse C... passed after 1 hr 45 min

Jenkins Linux s390x Build #9661 [push] Custom print and parse C... passed after 2 hr 15 min

Jenkins Linux ppc64le Build #8707 [push] Custom print and parse C... passed after 3 hr 38 min


libdrm-nvdc: set DEBIAN_NOAUTONAME also for license package

This is needed to avoid spdx from failing with:
ERROR: libdrm-nvdc-35.3.1-20230319081403-r0 do_create_spdx: The recipe libdrm-nvdc is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/home/qt/work/build/build/tmp/deploy/spdx/armv8a_tegra/packages/libdrm-lic.spdx.json
(matched in manifest-armv8a_tegra-libdrm.create_spdx)
Please verify which recipe should provide the above files.

Thanks!


Error installing flutter via snap

Steps to Reproduce
I am trying to use Flutter for linux and I have a problem launching the program from Idea
libGL error: MESA-LOADER: failed to open iris (search paths /snap/flutter/current/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /snap/flutter/current/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: swrast

I'm using a standard file bootstrap.sh
#!/bin/bash

SNAPCRAFT_ARCH_TRIPLET=x86_64-linux-gnu
SNAP=/snap/flutter/current
SNAP_USER_COMMON=$HOME/snap/flutter/common

export LIBGL_DRIVERS_PATH=$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/dri
...............

The LIBGL_DRIVERS_PATH variable gets the path "/snap/flutter/current/usr/lib/x86_64-linux-gnu/". Directory content is different from directory /usr/lib/x86_64-linux-gnu/dri/ . There is not enough file /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
If you put in a variable LIBGL_DRIVERS_PATH = /usr/lib/x86_64-linux-gnu/dri/ ,  then Idea launches the file. But, unfortunately, over time, botstrap.sh becomes standard again.

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on Linux, locale ru_RU.UTF-8)
    • Flutter version 2.2.3 at /home/sergey/snap/flutter/common/flutter
    • Framework revision f4abaa0735 (6 недель назад), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
    • cmake version 3.10.2
    • ninja version 1.8.2
    • pkg-config version 0.29.1

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2021.2)
    • IntelliJ at /home/sergey/ProgramFiles/idea
    • Flutter plugin version 59.0.4
    • Dart plugin version 212.4746.57

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Linux
    • Chrome (web)    • chrome • web-javascript • Google Chrome 92.0.4515.131

! Doctor found issues in 2 categories.

@GrishinSergeyLexpharma
Since you used snap to install Flutter, it has a separate repo for tracking. Please open this issue in dedicated repo: https://github.com/canonical/flutter-snap/issues
Closing from here.


[External] Codeunit 6520 - Item Tracing Mgt. - NextLevel, FindComponents, InsertRecord, and TransferData

Hello,
Can we make functions NextLevel, FindComponents, InsertRecord, and TransferData External in Codeunit 6520 "Item Tracing Mgt." called OnBeforeNextLevel.
procedure NextLevel(var TempTrackEntry: Record "Item Tracing Buffer"; TempTrackEntry2: Record "Item Tracing Buffer"; Direction: Option Forward,Backward; ShowComponents: Option No,"Item-tracked only",All; ParentID: Integer)
procedure FindComponents(var ItemLedgEntry2: Record "Item Ledger Entry"; var TempItemTracingBuffer: Record "Item Tracing Buffer" temporary; Direction: Option Forward,Backward; ShowComponents: Option No,"Item-tracked only",All; ParentID: Integer)
procedure InsertRecord(var TempTrackEntry: Record "Item Tracing Buffer"; ParentID: Integer): Boolean
procedure TransferData(var ItemLedgEntry: Record "Item Ledger Entry"; var TempTrackEntry: Record "Item Tracing Buffer")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Spotify Controls: Shuffle Play + Play

Description
Add new command:

Shuffle Play - launches Spotify, if not open, enables shuffle and hits play if not playing.

Update command:

Play to open Spotify, if not open, before playing.

Type of change

Bug fix / improvement for somebody else's extension. Extension author:  @thomaspaulmann

Screencast

https://user-images.githubusercontent.com/10678906/152661169-8d41ff50-98ac-4a44-9ebe-cb92c01d0798.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

Thanks for the review @thomaspaulmann

How about adding some safety net to the test if the application started? Maybe just repeat it three times? This makes sure that the script doesn't run endless if the app fails starting. More of an edge case but good to cover it.

Good thought. I went with 5 seconds(for slower machines) for the max and added a builder to wrap any command in the check to ensure Spotify is open.
See buildScriptEnsuringSpotifyIsRunning.  This method may make sense to pull into Raycast's core - I could see it having common use.

Would it make sense to start the app for all the commands if it isn't already running? Could also be a preference that is turned on by default. WDYT?

Agreed. That seems logical. I added a builder to wrap the command for every command except current, which handles when Spotify isn't open. I opted for no setting for now - I couldn't think of why someone would want the new behaviour turned off. Happy to discuss or add a setting if it is seen as necessary.


Update readme.md

fix typo

Hi @Azadehkhojandi,
Thanks much for the contribution... I recently submitted a PR #351 with many different typo fixes and broken links where this fix was included... Would you mind reviewing that instead and perhaps abandoning this PR as they fix the same thing (to avoid conflicts) - that would be much appreciated

Checked in separately with @Azadehkhojandi - we can abandon this PR


GH-34188: [C++][Benchmark] Add missing BENCHMARK_STATIC_DEFINE for bundled gbenchmark

Rationale for this change
We need to specify -DBENCHMARK_STATIC_DEFINE to use gbenchmark as a static library since gbenchmark 1.6.2.
What changes are included in this PR?
This change specifies BENCHMARK_STATIC_DEFINE for bundled gbenchmark explicitly.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

Closes: #34188

+1


Enhancement: Analyze user behaviour among different lending protocols notebook analysis

Issue #100

@lukaspetrasek please review this PR as I have resolved all unresolved issue from #139 and added all the dependencies. This is the contnuation of the PR #217 and #207


.mili header file, makemili and mili plugin require abs path to family files

The new .mili header file format is a bit better in that it uses some keywords to help identify what each line is for (JSON would probably be even better though). One of the new things the .mili header file captures in the path to the directory where the Mili family files can be found. However, the combination of makemili, the .mili file format and the Mili plugin result in that the path must be an absolute path. I could not get '.' or other sensible relative paths to work. This is largely a plugin problem but I think makemili should be fixed to stuff in a relative path there instead of an absolute one. For now, this means you cannot generate a .mili file on one filesystem and then move the .mili+family files to another system without having to regenerate the .mili file.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1585
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: .mili header file, makemili and mili plugin require abs path to family files
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 08/20/2013
Due date:
% Done: 0%
Estimated time:
Created: 08/20/2013 12:00 pm
Updated: 08/22/2013 02:50 pm
Likelihood: 3 - Occasional
Severity: 3 - Major Irritation
Found in version: 2.6.3
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
The new .mili header file format is a bit better in that it uses some keywords to help identify what each line is for (JSON would probably be even better though). One of the new things the .mili header file captures in the path to the directory where the Mili family files can be found. However, the combination of makemili, the .mili file format and the Mili plugin result in that the path must be an absolute path. I could not get '.' or other sensible relative paths to work. This is largely a plugin problem but I think makemili should be fixed to stuff in a relative path there instead of an absolute one. For now, this means you cannot generate a .mili file on one filesystem and then move the .mili+family files to another system without having to regenerate the .mili file.
Comments:

We now use a complete different scheme for mili header files.


when I access local web server, why it very slowly (macBook air)

when I access local web server(node js implement ) through <IP_ADDRESS>, it very fast, but when I bind <IP_ADDRESS> with www.zw.lcoal in /etc/hosts, then access web server through www.zw.local, it very slowly.

This looks like a DNS issue.  Try these commands:
curl -v www.zw.local
host www.zw.local
dig www.zw.local

I'm closing this since it's not a request issue, but if someone with more time than me wants to help troubleshoot then that's fine.

But when I access server through brower, why it very fast.


Add task_facts module

I would add one more example demonstrating how to filter tasks by the task state (taskState).


Minor cleanup in the Project Manager

Remove unnecessary nodes.
Remove unnecessary margin settings that were doing nothing.
Tone down the current margin a bit.
Change background color to be the as the the editor's.
Make language selector flat.

Thanks!


fix: update cuda image in README

Fixes #805. This PR is based on this comment and is slightly more future-proof than #700 as images now have DIST appended e.g. nvidia/cuda:11.0.3-base-${DIST}.
Note that the DIST itself does not need to match the system, per this comment.

This would be nice to include. I had the same problem as the issue linked above and using 11.0.3 fixed it. Please merge this PR.


Improve svgelements repr

Closing because there is also a bug in svgelements that needs to be fixed as part of #471 - so I will incorporate these changes into that.


advanced field validation messages

Is your feature request related to a problem? Please describe.
Sort of... I'm using VeeValidate w/ Buefy and would like to handle multiple error messages for custom fields.
Describe the solution you'd like
I'm using a Laravel (PHP) backend to send the form configuration to my Vue component, similar to the vue-form-json package referenced on the UI integration page.
I'm trying to figure out how to handle custom messages for dynamic fields. For example, a required field should ideally say something like The first name field is require or for a more useful example, displaying the minimum number of characters for a field using the min:x rule:
v-validate="required|min:6"
and being able to display something like:
The field_name must be at least X characters
Some code examples:
<b-field
                        v-for="(field, key) in fields"
                        :key="key"
                        :label="field.label"
                        :type="{
                            'is-danger': errors.has(form.arrayName + '[' + field.fieldName + ']'),
                            'is-success': !errors.has(form.arrayName + '[' + field.fieldName + ']') &&
                                          errors.count() > 0
                        }"
                        :message="[{
                            'The field must be at least X characters': errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'min'),
                            'This field is required' : errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'required'),
                            'This field is not valid' : errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'is'),
                            'Your passwords do not match' : errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'confirmed'),
                            'Please use a valid email address' : errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'email')
                        }]"
                    >
....

<b-input
                            v-else
                            :value="formModels[field.fieldName]"
                            :native-value="field.value"
                            :name="form.arrayName + '[' + field.fieldName + ']'"
                            v-model="formModels[field.fieldName]"
                            v-validate="field.rules">
                        </b-input>

This will generate my fields dynamically and handle the validation rules passed from my backend YAML file:
          password:
              label: backend.user.password
              type: password
              required: true
              context: ['create', 'account']
              tab: backend.user.account
              cssClass: is-three-fifths
              rules: 'required|min:6'

So as you can see, the fields and respective validation and messages are being handled properly. The issue is in trying to use a "variable" as part of the messages object key.
Obviously I cannot do something like because the displayed message is actually the object key, which will not allow for interpolation, unless I am mistaken:
:message="[{
                            'The ${field.fieldName} must be at least ${field.rules.min} characters': errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'min'),

                        }]"

I know this is probably a bit more advanced or complex implementation, but I am really close to having my requirements satisfied and would certainly appreciate any advice or suggestions.
Thank you!
Describe alternatives you've considered
I've tried concatenating the validation message with the desired variable:
:message="[{
                            'The ' + field.fieldName + ' must be at least ' + field.rules.min + ' characters': errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'min'),
                        }]"

but this is giving me a syntax error. Also, I'm unsure of how to access the rule parameter (in this case, it would be the min number of characters).
I'm currently just displaying a static message, but this doesn't help when specific context is needed. For example, if the required characters is min of 6, just saying the length is invalid doesn't help the user know how many characters to include.

If you want to do JS interpolation for object keys you could use ES6 computed keys:
var obj = {
  [myKey]: value,
}

So in your case, it would look like this:
:message="[{
  [`The ${field.fieldName} must be at least ${field.rules.min} characters`]: errors.firstByRule(form.arrayName + '[' + field.fieldName + ']', 'min'),
}]"

This is a combination of ES6 features, namely templated strings, and computed keys.
If you want the long answer, There is no way to access the configured rule parameters from the template, even internally when the locale changes it uses a closure to generate the new message.
I'm not sure about your requirements but you could expose the vee-validate validator globally on window...
// somewhere in your JS
import { Validator } from 'vee-validate';

// expose it on the window.
window.$app = {
  Validator
};

then have your page generate a script tag whenever you need a customized message, maybe something like this:
<script>
// this is the generated script.
Validator.localize('yourlocale', {
  custom: {
    'fieldName': {
       required: 'something something'
     }
  }
})

</script>

@logaretm Thank you for the reply. I was able to implement the first part of the message using ${field.fieldName} however ${field.rules.min} is throwing an error saying TypeError: Cannot read property 'min' of null

Do you have any thoughts?


error: command '/usr/bin/nvcc' failed with exit status 1

I followed the instructions of installation. When I ran "python setup.py develop", I got an error reporting: "error: command '/usr/bin/nvcc' failed with exit status 1". Is there any idea to fix this?
Thanks!

It seems that this might be due to using CUDA 10.1 (see https://github.com/open-mmlab/mmdetection/issues/1374). I used CUDA 10.0, and it worked fine. Therefore, I'd suggesting trying to downgrade your CUDA version to 10.0

Thanks for your quick reply!
I am working on Pose-based Tracking.
Can I get some means of obtaining the pose estimation results on PoseTrack17 & PoseTrack18  (Validation & Test)?
I would be very grateful if the pose estimation results are available.

Thanks for your quick reply!
I am working on Pose-based Tracking.
Can I get some means of obtaining the pose estimation results on PoseTrack17 & PoseTrack18 (Validation & Test)?
I would be very grateful if the pose estimation results are available.

@gberta  Hi, I tried with CUDA 10.0.130(using conda install cudatoolkit) and still i get the same error as mentioned in https://github.com/open-mmlab/mmdetection/issues/1374#

The scripts in the codebase perform evaluation on PoseTrack 17 and 18 datasets. The evaluation is done immediately after testing stage. If you run the scripts, you should see the printed tables with the mAP results for each joint.

This repo seems not to provide the specific code for testing on the testing set. What should I do to get the pose estimation results on the testing set? While file should I modify?
Thanks!


Last update TiddlyStow-ZH.html

@btheado hi，This is probably the last pr, if you see it and think it's okay, please merge it. thank you.

Thanks, @Zacharia2

@btheado You're welcome


Dark-Basic-Pro

https://github.com/TheGameCreators/Dark-Basic-Pro

https://www.thegamecreators.com/product/dark-basic-pro-open-source

https://en.wikipedia.org/wiki/The_Game_Creators

It's on this list: https://www.thefreecountry.com/compilers/basic.shtml

Thanks!


Update Go version in Dockerfile

Update Go version to 1.21. Docker image was not building on 1.20

lgtm, ty!


'aft-delete-default-vpc' feature option Lambda function does not delete default VPCs in target accounts

Terraform Version & Prov:
AFT Version:
1.6.3
Terraform Version & Provider Versions
terraform version
Terraform v1.2.6
on linux_amd64
+ provider registry.terraform.io/hashicorp/archive v2.2.0
+ provider registry.terraform.io/hashicorp/aws v4.30.0
+ provider registry.terraform.io/hashicorp/local v2.2.3
+ provider registry.terraform.io/hashicorp/random v3.4.3
+ provider registry.terraform.io/hashicorp/time v0.8.0

Your version of Terraform is out of date! The latest version
is 1.3.0. You can update by downloading from https://www.terraform.io/downloads.html

terraform providers
Providers required by configuration:
.
├── provider[registry.terraform.io/hashicorp/aws]
└── module.aft
    ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0, < 5.0.0
    ├── provider[registry.terraform.io/hashicorp/local]
    ├── module.packaging
    │   └── provider[registry.terraform.io/hashicorp/archive]
    ├── module.aft_iam_roles
    │   ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.aft_exec_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.aft_service_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.audit_exec_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.audit_service_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.ct_management_exec_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.ct_management_service_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   ├── module.log_archive_exec_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   └── module.log_archive_service_role
    │       └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    ├── module.aft_backend
    │   └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    ├── module.aft_account_provisioning_framework
    │   └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    ├── module.aft_customizations
    │   ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   └── provider[registry.terraform.io/hashicorp/local]
    ├── module.aft_feature_options
    │   └── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    ├── module.aft_lambda_layer
    │   ├── provider[registry.terraform.io/hashicorp/local]
    │   ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   └── provider[registry.terraform.io/hashicorp/random]
    ├── module.aft_account_request_framework
    │   ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   └── provider[registry.terraform.io/hashicorp/time]
    ├── module.aft_code_repositories
    │   ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
    │   └── provider[registry.terraform.io/hashicorp/local]
    └── module.aft_ssm_parameters
        ├── provider[registry.terraform.io/hashicorp/aws] >= 4.9.0
        └── provider[registry.terraform.io/hashicorp/random]

Providers required by state:
    provider[registry.terraform.io/hashicorp/aws]
    provider[registry.terraform.io/hashicorp/archive]
    provider[registry.terraform.io/hashicorp/time]
    provider[registry.terraform.io/hashicorp/local]
    provider[registry.terraform.io/hashicorp/random]

Bug Description
Feature option Lambda function 'aft-delete-default-vpc' does not delete default VPCs in target account. Instead it will execute for the AFT Management account itself.
To Reproduce
Steps to reproduce the behavior:

Take note of a few Default VPC IDs in different regions for both the AFT Management Account and a target account.
Submit a new account request or invoke the 'aft-invoke-customizations' Step Functions state machine for the target account.
Open CloudWatch Log group '/aws/lambda/aft-delete-default-vpc', locate the most recent log stream, related to the invokation (should appear after a minute or so).
If the AFT setup is completely new and never been run before, or somehow the Lambda function has never successfully deleted some or any default VPCs before, you should observe that it found and deleted VPC resources (e.g. VPC ID) that belonged to the AFT Management Account, not the target account.

Expected behavior
The default VPCs for all target accounts should be deleted.
Related Logs
Excerpt of log output from invocation. Pay attention to log lines "Generating session using.." and "Getting default VPC"+the following line that outputs the actual VPC ID.
2022-09-28T08:18:25.589+02:00	{"time_stamp": "2022-09-28 06:18:25,589", "log_level": "INFO", "log_message": "Generating session using arn:aws:sts::111111111111:assumed-role/AWSAFTAdmin/AWSAFT-Session for arn:aws:iam::222222222222:role/AWSAFTService"}
2022-09-28T08:18:26.253+02:00	{"time_stamp": "2022-09-28 06:18:26,253", "log_level": "INFO", "log_message": "Describing Regions"}
2022-09-28T08:18:26.332+02:00	{"time_stamp": "2022-09-28 06:18:26,332", "log_level": "INFO", "log_message": "Found 17 regions: ['eu-north-1', 'ap-south-1', 'eu-west-3', 'eu-west-2', 'eu-west-1', 'ap-northeast-3', 'ap-northeast-2', 'ap-northeast-1', 'sa-east-1', 'ca-central-1', 'ap-southeast-1', 'ap-southeast-2', 'eu-central-1', 'us-east-1', 'us-east-2', 'us-west-1', 'us-west-2']"}
2022-09-28T08:18:26.334+02:00	{"time_stamp": "2022-09-28 06:18:26,333", "log_level": "INFO", "log_message": Found credentials in environment variables.}
2022-09-28T08:18:26.396+02:00	{"time_stamp": "2022-09-28 06:18:26,395", "log_level": "INFO", "log_message": "Getting SSM Parameter /aft/config/feature/delete-default-vpcs-enabled"}
2022-09-28T08:18:26.459+02:00	{"time_stamp": "2022-09-28 06:18:26,459", "log_level": "INFO", "log_message": "Creating boto3 session in eu-north-1"}
2022-09-28T08:18:26.470+02:00	{"time_stamp": "2022-09-28 06:18:26,469", "log_level": "INFO", "log_message": Found credentials in environment variables.}
2022-09-28T08:18:26.614+02:00	{"time_stamp": "2022-09-28 06:18:26,614", "log_level": "INFO", "log_message": "Getting default VPC"}
2022-09-28T08:18:26.720+02:00	{"time_stamp": "2022-09-28 06:18:26,720", "log_level": "INFO", "log_message": "Creating boto3 session in ap-south-1"}
2022-09-28T08:18:26.733+02:00	{"time_stamp": "2022-09-28 06:18:26,733", "log_level": "INFO", "log_message": Found credentials in environment variables.}
2022-09-28T08:18:26.987+02:00	{"time_stamp": "2022-09-28 06:18:26,987", "log_level": "INFO", "log_message": "Getting default VPC"}
2022-09-28T08:18:27.684+02:00	{"time_stamp": "2022-09-28 06:18:27,683", "log_level": "INFO", "log_message": "vpc-0a1b2c3d4e5f6g7h8"}

Additional context
The Lambda function 'aft-delete-default-vpc' (and its handler function 'aft_delete_default_vpc.lambda_handler) seems to be using incorrect boto3 session while actually going through default VPCs for each region.
A small change to the function code, that seems to be working (i.e. the target account default VPC for each region is deleted as expected), produces the following git diff:
diff --git a/src/aft_lambda/aft_feature_options/aft_delete_default_vpc.py b/src/aft_lambda/aft_feature_options/aft_delete_default_vpc.py
index 484ad50..7d9c006 100644
--- a/src/aft_lambda/aft_feature_options/aft_delete_default_vpc.py
+++ b/src/aft_lambda/aft_feature_options/aft_delete_default_vpc.py
@@ -59,11 +59,10 @@ def lambda_handler(event: Dict[str, Any], context: LambdaContext) -> None:
         ):
             for region in regions:
                 logger.info("Creating boto3 session in " + region)
-                session = boto3.session.Session(region_name=region)
-                client = session.client("ec2")
+               client = target_account_session.client("ec2",region_name=region)
                 vpc = get_default_vpc(client)
                 if vpc is not None:
-                    resource: EC2ServiceResource = boto3.resource(
+                   resource: EC2ServiceResource = target_account_session.resource(
                         "ec2", region_name=region
                     )
                     # Get Resources

I didn't search through closed issues before submitting this. Found these:
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/142
https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/200
Any news on this issue?

Hey @ahuseby,
This can be considered a known issue that will not be fixed in AFT v1 due to the risk of breaking changes for customers. Please see our comment in https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/200#issuecomment-1178227617 for more information as well as the documentation that describes the behavior of this option.


New version: ProxSDP v1.4.1

Registering package: ProxSDP
Repository: https://github.com/mariohsouto/ProxSDP.jl
Created by: @joaquimg
Version: v1.4.1
Commit: 12e02e03e0420ee49918f21d210afd47eab4a901
Reviewed by: @joaquimg
Reference: https://github.com/mariohsouto/ProxSDP.jl/commit/12e02e03e0420ee49918f21d210afd47eab4a901#commitcomment-42517655

@joaquimg ^

@fredrikekre , sorry I missed it.
We had some release problems.
Now 1.4.0 is merged in https://github.com/JuliaRegistries/General/pull/22023
Once this is one is merged,
1.5.0 can be merged in https://github.com/JuliaRegistries/General/pull/21837
and then
1.5.1 can go in https://github.com/JuliaRegistries/General/pull/22013

@fredrikekre ,
On second thought, since this version was never released I would be ok with no releasing this one.
Version 1.5.0 is already out and solves even more issues.
Close this if possible.
Thanks!


Abstract the way to contact the prometheus server

This PR contains the new interface for the custom prometheus client.
The langserver is now using the custom prometheus client.
That's the first PR to resolve the issue #134

Looking at the test, looks like I missed a step during the initialization process of the server.  Or maybe I should create a fake prometheusClient for the test.

Also the linter still has some complaints.
I think you also need to change the golangci-lint rule in the Makefile to also lint the new prometheus package.

It should be better now :).
A side effect regarding the linter : I disable the linter "wsl" I'm filling it gives more false positive than accurate error. Most of the case I had wasn't accurate. I think that's so severe to disable it anyway. Tell me if you really want to put it back :).

A side effect regarding the linter : I disable the linter "wsl" I'm filling it gives more false positive than accurate error. Most of the case I had wasn't accurate. I think that's so severe to disable it anyway. Tell me if you really want to put it back :).

The wsl linter is indeed somewhat annoying and not that useful, so I'm ok with disabling it.

For the moment I'm good with this one. If there are other changes, I'll do it in other PRs :).
Thanks for the review !


Update authentication-aad-configure.md

This pull request includes a small change to the azure-sql/database/authentication-aad-configure.md file. The change advises associating the Microsoft Entra admin ID with an Entra Group for better management.

azure-sql/database/authentication-aad-configure.md: Added a recommendation to tie the Microsoft Entra admin ID to an Entra Group, specifying that the Client ID of the Entra Group will be inserted into the sys.database_principals in the master table.

@nofield
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@JFolberth Thanks for taking the time to submit this PR. This may be good guidance to make here, running it past some engineers to confirm if this isn't a little more complicated. Will update the PR accordingly.

Thanks @JFolberth for your suggestion here. This and other feedback has been added to the Entra docs, please see here: https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-overview?view=azuresql#microsoft-entra-administrator

Marking this as resolved.
#please-close


Unable to provision the bot using provisioncomposer.js command

I am unable to provision the bot. 1)Can someone provide where to find the App password?
2) Do we need to create a web bot in azure before publishing to azure?

@sandeepreddy0987 , what version of Composer are you using? we had a fix on this #3359 , could you try to use the latest master or you can wait to the next release of the Composer Electron which will be available soon.

v1.0.1 is my botcomposer version

@sandeepreddy0987 , this is a known issue in the v1.0.1, you can mitigate this by referring to this comment to add tenantId as a parameter for provision, https://github.com/microsoft/BotFramework-Composer/issues/3313#issuecomment-639235003, or you can wait for v1.0.2 release which will be available soon.

Hi @luhan2017 will this also resolve the below issue?
I've tried the workarount to also include the tenantid but with no success...
{
"error": {
"code": "InvalidBotData",
"message": "Bot is not valid. Errors: The bot name is already registered to another bot application..  See https://aka.ms/bot-requirements for detailed requirements."
}
}

This was identified as a related issue in #3324 and resolved together. I've tried the workaround you reported above - include the tenantid but with no success..

@triciasinclair , according to the error message, you already passed the tenant id part, it should fail at the web app provision part, could you try to update your bot name, it looks like you are using an existing bot name which cause the provision failure.

@triciasinclair @sandeepreddy0987 , is this issue resolved in your side?

Resolved. Thank you.


Feature/recovery orgs and projects

What added:

Add field banned in OrganizationStatus and ProjectStatus
Choose Highest Role in UserSettingsOrganizationView
Add deleted, banned and recovery logic
Add list of deleted and banned organizations in UserSettingsOrganizationsMenuView.kt and button to restore them
Add list of deleted and banned projects in OrganizationView and button to restore them
Combined the logic of deleting the project in Organization with the rest of the connected
Checked and changed logics with statuses
Added a few checks on the status of the project / organization on the backend
Added / corrected tests

Pictures:

Issues:
This pull request close #1252
Connected issues:
To fully support the BANNED status, Issue #1390

the last commit is Update backend-api-docs.json. It blocks CI. It can be fixed by closing the PR and then reopening it

Seems this PR was split into several others and won't be merged itself.


support exec with no proxy

What type of PR is this?
/kind feature

What this PR does / why we need it:
support exec with no proxy
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/close


flounder core fixes/changes

this PR includes fixes for this and this.
Also, we've made some changes to the search input to make it display correctly when we have multiple tags selected.
Tests are also up to date

so, this looks amazing.  but.....  it's forked from master.  that's makes life very difficult.  1.0.0 is being worked on heavily (see the first line of the readme), so this needs to be merged into flounder1.0.0  which is much more of a challenge coming out of master

the fact that there has been big changes to multiTags will make this even more difficult.
i dont really know what to suggest.  i guess either you need to start in flounder1.0.0, or I need to find time to merge this.  This PR will not be merged into 0.8.5, it's frozen as it doesnt make sense to update problems in 2 branches.
I do appreciate the PRs, but this is the second time it's been a master PR.  Is there anything i can do to make things more clear?

@mousemke seems like we need to stick that info in the readme if master is not always at latest release state.
This is confusing though, as master notes it's at version 0.8.5 in the readme. Which is not the case it seems...
I'd opt for us keeping master clean and then it's simple to fork / make PRs, as opposed to having to fork a specific version/branch before making changes.
And then any developments could be done on specific feature branches etc.
For me, that would seem like a good setup for accepting PRs and keeping merge conflicts to a minimum.
@zsolt-nagy-sociomantic , you have any thoughts on this?

Regarding this set of changes, do you have an ETA for v1? Probably makes sense for us to make changes off of this branch to keep merge conflicts to a minimum.
So where exactly would be the desired place to branch from before applying changes? master at it's current state? Or you're saying to wait for 1 to drop and then fire back in with the PRs?

1.0.0 has changed a lot.  anything on master is locked and has a git and an npm release. dev will never be master.  master is in fact the current release state; that's the exact reason that a pr into it isnt good.
from the master readme first line:
*** Flounder 1.0.0 is being built right now, so there is a feature freeze on earlier versions, but feel free to open issues for 0.X.X and feature issues for 1.0.0 should anything come up ***.  There is also a 1.0.0 milestone open.  this is only a bigger issue this time around due to the incompatibility in the branches (hence the semver)
you could fork flounder1.0.0 and change it there, or wait on 1.0.0 to drop, your call.
ETA is hard. i want to get 100% test coverage before releasing, but if y'all need it, that can be skipped possibly.  Additionally, the test suite is moving from qunit to mocha and istanbul.  so it's a fairly large issue.
TL;DR - I could get you a stable 1.0.0 branch, but i probably wouldnt release 1.0.0 until tests are ready

@mousemke Cool. That's fine, thanks for the infos 👍
Let's add your desired PR workflow to the readme though to avoid future confusion?

@josh-wilson-sociomantic definately will do

ok.  for now, can we say PR into flounder1.0.0
after, i will add details to the PR process in the readme.  thinking something like:
branches

release - exactly the same as npm and git releases (including dist files)
master - stable, but no dist files
dev - dev that all should branch out from
feature branches - specific features/fixes, branched from dev and merging back in when complete

i'm open to other ideas on organization as well.

@josh-wilson-sociomantic @damian-rodriguez-sociomantic @zsolt-nagy-sociomantic


Periodically delete old artifacts

Currently we upload the image as an artifact on every run, we probably need to be cleaning those up periodically or at some point someone is going to get angry at us

https://github.blog/changelog/2020-10-08-github-actions-ability-to-change-retention-days-for-artifacts-and-logs/
It looks like we could also just set retention days to 1


fix: scroll to bottom and word wrap

This fixes 1 bug, and reduces the severity of another.
Word Wrap
Word wrap only partially wrapped lines before.
Before it would only split lines by word boundaries (i.e. whitespace or hyphens), for example, long words or minified JSON would still extend over and require a horizontal scrollbar to view the full log. (Which kinda defeats the point of word wrapping since the goal is to avoid horizontal scrolling.)

This adds overflow-wrap: anywhere which tells the view that it's ok to split in the middle of words. Now users won't experience a horizontal scroll bar at all when word-wrap is enabled!
More info:

https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap

Scroll to Bottom
We had 2 problems before when there were too many logs.
There seemed to have been a relationship between this scroll to bottom issue and word wrap.
Turns out the scroll to bottom issue can occur when the parent element has too much height, so word-wrap increases the severity of the issue. (Since it logs take up much more vertical space.)
I comment on it here:
https://github.com/vscode-kubernetes-tools/vscode-kubernetes-tools/issues/1040#issuecomment-1119280332
div Height Cap… or something?
The a#bottom element would no longer anchor to the bottom. This was because the parent divs height would cap out it seems and the rest of the logs were only visible because it overflowed underneath.
Why did this happen? I have no idea. ^-^'
Because of this, the a#element ends up above the last log, so a better approach would be to simply select and scroll to the last log.
Chromium or VSC Doesn't Render all Elements
When the document is a bit too long, either Chromium or VSC has an optimization which prevents all elements from being rendered.
This breaks the scroll to bottom button for example because if a user starts at the top and has thousands of logs (especially if they're very long logs with word wrap enabled) then the a#bottom could be pushed so far down that it doesn't render and therefore can't be selected in the DOM.
In my case, my log viewer had a height of over 100,000 pixels, so the optimization does make sense.
I removed the a#bottom element and instead in the scrollToBottom function just select the last log and scroll to that instead.
More info:

https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector
https://developer.mozilla.org/en-US/docs/Web/CSS/:last-of-type

However, this solution isn't perfect either.
Before when there were many logs, scroll to bottom did nothing. (Since a#bottom didn't select the element, so it didn't scroll.)
Now it selects the last log and scrolls down to it. But if the user has a lot of logs or word wrap enabled where VSC isn't actually rendering all the logs, it'll only scroll down to the last rendered log. But this will in turn render more logs so the button can take the user to the bottom. (And when the user is at or near the bottom, it'll work normally.)

Maybe a partial fix for https://github.com/vscode-kubernetes-tools/vscode-kubernetes-tools/issues/1040

When/if this is merged, I'd like if we could make them test and see if the new way of selecting the bottom works better for them. Their issue doesn't seem to be height related since it occurs even when they don't have many logs.

Sorry, I'd like to include more screenshots/GIFs but I'm testing with things for work so I can't show the actual logs. ^-^'

With this patch we are converting the scroll to bottom to page down.

I actually disagree with this way of putting it. It's very different from page-down. 🤔
Plus a before and after of where the "Scroll to Bottom" button takes the user with the same amount of logs.
Before

Less then half way.

After

All the way to the bottom in this case.

With your proposed implementation, all it does for me is jitter the view to the same place that the old implementation would take the user.

Even using the dev tools to "Scroll Into View" on #bottom doesn't take the user to the bottom while it's rendered.
Meanwhile, doing "Scroll Into View" with selecting the final element (via the GUI) does as intended and scrolls to the bottom.
Before

After

Ahh… I was investigating this further… -_-
I'm a dummy.
I didn't notice we (as in the extension itself) was setting the height of the #innerLogPanel element. XD
I'm not sure why we are yet, but I can at least concede that perhaps my proposal isn't the optimal solution in that case now that I've seen that.


prometheus statefulset with thanos stop working

What did you do?
I've been working on promethues ha with thanos
What did you expect to see?
What did you see instead? Under which circumstances?
Environment

System information:
insert output of uname -srm here

Prometheus version:
2.22.1

Alertmanager version:
insert output of alertmanager --version here (if relevant to the issue)

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

My complete configurations can be found here:
https://github.com/hairongGao/prometheus-thanos-grafana

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here
logs for prometheus-3:
level=info ts=2020-11-26T03:45:48.626Z caller=manager.go:934 component="rule manager" msg="Rule manager stopped"
level=info ts=2020-11-26T03:45:48.626Z caller=notifier.go:601 component=notifier msg="Stopping notification manager..."
level=info ts=2020-11-26T03:45:48.626Z caller=main.go:789 msg="Notifier manager stopped"
level=info ts=2020-11-26T03:45:48.626Z caller=main.go:615 msg="Scrape manager stopped"
level=error ts=2020-11-26T03:45:48.626Z caller=main.go:798 err="opening storage failed: found unsequential head chunk files /data/chunks_head/000002 (index: 2) and /data/chunks_head/000005 (index: 5)"

logs for prometheus-2:
level=error ts=2020-11-26T03:15:20.159Z caller=db.go:730 component=tsdb msg="compaction failed" err="persist head block: populate block: add series: out-of-order series added with label set \"{__name__=\\\"envoy_cluster_assignment_stale\\\", app=\\\"istio-ingressgateway\\\", chart=\\\"gateways\\\", cluster_name=\\\"xds-grpc\\\", heritage=\\\"Tiller\\\", instance=\\\"<IP_ADDRESS>:15090\\\", istio=\\\"ingressgateway\\\", job=\\\"kubernetes-pods\\\", kubernetes_namespace=\\\"istio-system\\\", kubernetes_pod_name=\\\"istio-ingressgateway-669cfc876b-zdcng\\\", pod_template_hash=\\\"669cfc876b\\\", release=\\\"istio\\\", service_istio_io_canonical_name=\\\"istio-ingressgateway\\\", service_istio_io_canonical_revision=\\\"latest\\\"}\""

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Silk-Spawners always turn to Pig Spawners

Describe the bug
All placed spawners turn to Pig Spawners (spawners mined with Silk Touch when Purpu's Silk-Spawners are ON)
To Reproduce
Mine e.g. Creeper spawner and place it
Plugins
Plugins (28): ChestShop, Chunky, Citizens, eco, EcoEnchants, GriefPrevention, HeadDatabase, HolographicDisplays, LibsDisguises, LuckPerms, Multiverse-Core, OpenAudioMc, ProtocolLib, SkBee, skDragon, SkQuery, Skript, skript-reflect, Tablisknu, ThatPacketAddon*, TheNewEconomy, TuSKe*, Vault, Vixio*, Votifier, WorldEdit, WorldEditSelectionVisualizer, WorldGuard
Version
This server is running Purpur version git-Purpur-1038 (MC: 1.16.5) (Implementing API version 1.16.5-R0.1-SNAPSHOT)
You are 4 version(s) behind
Previous version: git-Purpur-1025 (MC: 1.16.5)

duplicate of #48.
Make sure to read https://github.com/pl3xgaming/Purpur/issues/48#issuecomment-686179684


Fix broken links

Fixed a link pointing to the same page and 2 other links that are returning 404s

Hey @QwertyZW thanks for the head's up. That first link is actually linking to a subsection of the doc, and is correct as it was. (It should jump down the page.) Those other two are broken, you're correct, but were not intended to be links to the documentation - rather directly into the Hub UI. They should both go to https://hub.docker.com/add/automated-build/bitbucket/

Hi @QwertyZW, do you want to edit your patch and re-push? :) Or do you want to close it and I'll make the correction in the next batch of Hub updates?

@sanscontext You can actually edit his patch directly if you click the pencil in the "files" tab in this PR. :)

Fixed the links. Merging.


[Go Live][Aug 19]

Push to live

Docs Build status updates of commit 96f1851:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit 96f1851e1d4210a01db2757790ad302aee9d986d in branch main of repository https://github.com/MicrosoftDocs/msteams-docs into branch live (commit be35bb37b8f07a1171eaaa0fe55ccacbc1fa21d1). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 29cfd89:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/samples/teams-low-code-solutions.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Revert "remove on_os from formula"

This is causing post_install failures. Spotted in
Homebrew/homebrew-core#91763.
This reverts commit fc7462acd5ffb7cc393d2b56b989e96112ade896.

Review period skipped due to critical label.

Thanks @carlocab!


[core] Remove react from styled-engine dependencies

React has been added to @mui/styled-engine and @mui/styled-engine-sc dependencies by mistake. It should be a devDependency.

Hey @michaldudak @Janpot , any idea when a new version with this fix will be deployed?
It breaks our entire company's UI

Hi,
thanks for the patch.
we have got major broken release because of this change.
when do you think it will be released?

We usually do releases on Mondays. Please use the previous version until then.
Sorry for the inconvenience!

Hi @michaldudak, this breaks our UI as well.

@michaldudak Hi, I had happy time figuring out what was the problem during my overtime. When it will be fixed ?

@msirghi Something incoherent about useContext and useState
We figured out it happened because we use a lower version of React than 18, and it broke the UI.
Unfortunately, we can't use the aforementioned temporary fix because we currently also use a low version of node / npm.


discord: add config for initial status/presence

So we're not entirely happy with needing to mock out a message, but we also didn't want to duplicate the the existing code for managing presence sync and activity matching.  We're open to other ways to do it

We'd definitely prefer doing away with the mock message. We can pull out the activity parsing into its own method, but I think the presence handling should probably just be duplicated — plus then on_ready can also try to fetch the initial presence instead of waiting for a presence change too.
Only other thing than that is style — multiline function calls should have the closing parenthesis on its own line (with the same indentation as the initial line). We won't have mockMessage anymore so that doesn't apply, but for future reference Python variables by convention are in lower_snake_case.
Thank you for the PR! 🙂

Just pushed 6b57746c739cebc0b5dbe7336d121e7beb34c808 which pulls the activity parsing out into its own method — you should be able to rebase off of that

Okay I have updated it to remove the mock message, changed the formatting for the __init__() function declaration, and I think have not introduced any more camel case variables.


Please bring back the dumping of the AST

@sebastianbergmann The format of the dumped node is a bit different than the original format. Does this patch work for you?

Thank you for working on this!
However, I cannot test your patch as I run into the following:
./phan -a ~/test.php

Fatal error: Uncaught Error: Undefined constant 'ast\flags\CLASS_FINAL' in /usr/local/src/phan/src/Phan/Language/Element/Clazz.php:139
Stack trace:
#0 /usr/local/src/phan/src/Phan/Language/Element/Clazz.php(115): Phan\Language\Element\Clazz::fromReflectionClass(Object(Phan\CodeBase), Object(ReflectionClass))
#1 /usr/local/src/phan/src/Phan/CodeBase/ClassMap.php(115): Phan\Language\Element\Clazz::fromClassName(Object(Phan\CodeBase), 'Closure')
#2 /usr/local/src/phan/src/Phan/CodeBase.php(60): Phan\CodeBase->addClassesByNames(Array)
#3 /usr/local/src/phan/phan(21): Phan\CodeBase->__construct(Array, Array, Array, Array)
#4 {main}
  thrown in /usr/local/src/phan/src/Phan/Language/Element/Clazz.php on line 139

@sebastianbergmann Is it possible your build of php-ast is older than the one I'm using? It looks like it may have been added in https://github.com/nikic/php-ast/commit/2b147f3 and I'm running phan against a build based on https://github.com/nikic/php-ast/commit/51f2183
Can you tell me what version of php-ast you're using?

I am using 66dd303fc17aafe968fa5ff393b920ba5c222b6f of etsy/phan, 51f2183b7d9d42b7fd9667621be39cf7096ac043 of nikic/php-ast, and e322fb0015e0204a479b77cda6b8a75ed8ab86a7 of PHP.

@sebastianbergmann That all looks good to me. Perhaps the php-ast module hasn't been loaded correctly? The latest version of phan will now check to make sure that the php-ast extension is loaded (https://github.com/etsy/phan/commit/d8ae3bb8e5eaedabf14bec994e54dfbfce809516). Is that check passing for you?
Does the list produced by the following show ast?
echo "<?php print_r(get_loaded_extensions());" | php

Or check that your build actually has the constant:
php -r 'print_r(get_defined_constants(true));' | grep CLASS_FINAL

If that doesn't show: [ast\flags\CLASS_FINAL] => 4
then your php-ast build is not current.

No clue what was going on earlier, now it works. Thanks!

Great!


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 2020.9.112786
OS Version: Windows_NT x64 10.0.19041
VSCode version: 1.49.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.


CLEAN MASKS refinement to-do list

We need clean mask creation. In python (doesn't have to be CASA). Using SC routines!

This is basically done. Can look at a true clean mask generation suite in version 3, but the tools are exposed and the iterative approach is recommended in the docs and papers. Closing.


Payload support

(done) use phpecc/phpecc in order to generate the encryption key in prime256v1
when this PHP bug is fixed, replace phpecc by the PHP binding of OpenSSL (thanks @marco-c)
use OpenSSL with AES 128 GCM mode to encrypt the payload (need to wait for the resolution of this other PHP bug.)

If you want to help: (thanks!)

vote for the PHP bugs in the above linked pages
or contribute to php/php-src in order to fix the bugs

Hey Minishlink, IIRC phpecc has known vulnerabilities.
Directly using OpenSSL would probably be better, since you have to wait for https://bugs.php.net/bug.php?id=67304, you could wait for https://bugs.php.net/bug.php?id=61204 as well (hoping that they will be resolved soon enough).

Thanks for the info! :) It surely is worth waiting, I'll look into it.

Hola. Is payload encryption works now for firefox? I try run project it generated salt & publicKey but payload not received by browser. This sample is works fine https://jrconlin.github.io/WebPushDataTestPage/

Hi, payload is not yet supported because PHP doesn't provide enough access to OpenSSL yet. This will likely be the case with PHP 7.1.
This PR is here to implement the changes made to resolve the aforementioned bugs. Its development is paused since the bug fixes are not yet merged in any PHP version, beta or not.
As explained in the README, a workaround is to store the payload in your server, to send notifications without payload, and to make the client fetch the corresponding payload stored in the server using the endpoint as identification.
But, if you really need "real" payload support, you will have to drop PHP for Node.js. Note that payload won't be delivered in Chrome (though it may have changed since the last time I checked).

@Minishlink have you seen https://github.com/Spomky-Labs/jose/blob/master/src/Util/GCM.php? It was suggested in https://bugs.php.net/bug.php?id=67304.
OpenSSL is probably better security-wise, but at least that should make it possible to support push payloads in the meantime.

@marco-c Yep, I'll probably look into it this weekend. :) Thanks for the notification btw.

The error in the PAYLOAD=true case is due to this line: https://github.com/Minishlink/web-push/blob/payload/src/WebPush.php#L89.
It's using res[0], which is an array. It should use res[0]['success'] (btw, why are you using the result of the first as the overall result?).

That was something I forgot when I added the flush feature. (sendNotification was for only one notification) Thanks for the help !
Now my problem is that when I send a notification with payload, the Firefox server returns a 200/201 but my web app doesn't trigger the notification. I wonder how I can test if encryption is done correctly or how I can know what's going on the Firefox server.

This page might help you, it prints all the intermediate values of the encryption process. You can print yours and compare them and see where's the bug.

So I looked at the "new" (IETF draft for http encryption encoding)[https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-00] and (this Google Doc)[https://docs.google.com/document/d/1_kWRLJHRYN0KH73WipFyfIXI1UzZ5IyOYSs-y_mLxEE/edit#heading=h.dkpjo5c85cqe]. Apparently there is new encryption "aesgcm" and right now I try to use "aesgcm128". Should I implement the new "aesgcm" or "aesgcm128" ? Also, I'm quite confused by (https://developers.google.com/web/updates/2016/03/web-push-encryption)[this Google post] as the encryption process seems different to what you did at Mozilla...
Btw, I'm pushing what I was working on earlier.

The push service used in Firefox still supports the previous standard, I don't know when the new standard will be supported.
Notice that Content-Encoding should be aesgcm128 no matter what.

Actually, Firefox 45 supports the old standard and half supports the new standard (but not completely), from Firefox 46 both are fully supported.

Thanks for the help, I really appreciate it.
I made some progress. I'm still confused by the way the Google team seems to have implemented the protocol as another Node.js library than yours. I'm not sure if this comes from a newer IETF draft that is not yet available publicly or if they just coded their push server differently.

They use 'aesgcm' instead of 'aesgcm128'.
They put a 'P-256' in the info records of the nonce and cek.

Maybe @gauntface could help us ? :)

Chrome supports the new version of the standard, Firefox started supporting payloads earlier, so it supports the old version and an intermediate one and will soon support the new one (https://bugzilla.mozilla.org/show_bug.cgi?id=1257405 & https://bugzilla.mozilla.org/show_bug.cgi?id=1257821).
The intermediate one is similar to the new one, the only differences are:

auth secret of 12 bytes instead of 16;
Content-Encoding info is 'aesgcm128' instead of 'aesgcm';
padding is expressed in one byte instead of two.

I would wait for those two bugs to get resolved, because the fixes could get uplifted to Firefox 46 and 47, making this intermediate standard disappear.
The new standard is based on: http://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html
I've added support for Chrome in my library (https://github.com/marco-c/web-push/pull/115).

Marco has the perfect response to this. Really don't think there is anything I can add

Thanks for the insight.
Does Chrome or Firefox logs any information when it fails to decrypt a push message? While it works well when I have no payload, nothing shows up when I do...
I'll try to use this verifier.

Does Chrome or Firefox logs any information when it fails to decrypt a push message? While it works well when I have no payload, nothing shows up when I do...

Firefox doesn't, I don't know about Chrome.
You can use the verifier for the new standard and this page for the old standard. The intermediate standard is really similar to the new standard, so once you have one working it's simple to implement the other.

Finally, victory ! :smile: :tada: (with the new standard)
As always, the culprit was a little something, but it obviously counted a lot... The length of the keys in the context, so 65, had to be an unsigned integer in network byte order (big endian), so 0A. I must have overlooked it in the spec.
I managed to detect the error using the aforementioned verifier.

There's still one problem, and I don't think it's related to my implementation. When automatic padding is enabled, Chrome doesn't remove the null bytes \0 after it has decrypted the message, and so the JSON parsing fails with Uncaught SyntaxError: Unexpected token \u0000 in JSON at position 0. I'll probably file a bug on the Chromium issue tracker.

There's still one problem, and I don't think it's related to my implementation. When automatic padding is enabled, Chrome doesn't remove the null bytes \0 after it has decrypted the message, and so the JSON parsing fails with Uncaught SyntaxError: Unexpected token \u0000 in JSON at position 0. I'll probably file a bug on the Chromium issue tracker.

Have you tried testing your output with the verifier?

Chrome gives me the output in the console with the correct number of null bytes, so I presumed that it is correct, but I'll give it a try anyway.

Ok. So the output is different, though by not much:

actual: fCFx4xYna5q27K3KuOSXkd9YXKMj9XwzIDxkXN6gdLostX7AHSC2F10qpbSLmtJMuQUuDN-xQIkBe3aSjCpUBeU
expected: fSFx4xYna5q27K3KuOSXkd9YXKMj9XwzIDxkXN6gdLostX7AHSC2F10qpbSLmtJMuR54GaVuRVdy4V8797sylhU

I'll look into it probably this week-end.

I think there's a problem in the verifier, which is using low-endian order instead of big-endian to write the pad value. I've submitted a PR to fix it: https://github.com/beverloo/peter.sh/pull/17.

Ok so I totally discovered in your PR that one had to prepend the length of the padding in the payload. I really don't know where it comes from.
Anyway, it's included in the previous commit. But! If there is too much padding (639 seems to be the limit with a 46 long text), Chrome fails to decrypt the message. Going to dig more...

Everything should be in http://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html:

Padding consists of a two octet unsigned integer in network byte order, followed that number of zero-valued octets.

Now the output is exactly (checked with diff) the same than the one of the verifier but Chrome fails to decrypt the message when the padding length is greater than 127... so either there is a bug in the verifier or Chrome has a bug.

It's working for me with a padding length of 400.
Could you share your keys, the message you're encrypting and the exact padding length you're using? I want to test it in the same conditions.

Chrome v. 50.0.2661.37 beta-m (64-bit)

server public key: BIt6LW_aLSmkgfzXLgrfMP73JKmSjuCl9XhdNIc8JFVRa270iXsU5mDmTRsmflwz8tOIeXKlepn1EZtWnvk3_j8
server private key: WFQfX6ctzPiY8xRP2SZFsfofUB6j3-NNq1sCEeiq5F4
user public key: BP0TvUgbZs1aOa5sppJJ4GPa9LhN7H6L-W0etTOlACJxBPktYhdJbHDeLObVwYcgoJtt8LVMVAKP4_Wh088krT0
salt: 9-WCrz0JsqfHIGGn2L7CnA
auth: CxVX6QsVToEGEcjfYPqXQw
padding: 128
message: {"message":"Comment ça va ?","tag":"general"}
ciphertext: Vhb1kp0yTZTPkYo0cp_I1GhaYnUumhU4Wq8u-gsMS1wWcBzG-KLjswEgIcBMsrm3fczh0yXv-1nmhOczjiYxvYYdiybOyArWQN5DDgt3OoVBITe_39wr1k7KrsQaDcp71B63Gp7zQCo_JaeVZ0sToF7cg8vHDop9Y0xRQt_QHzeGdm-dF3WCnAVoyfiUpSMzZ_pUg7LFqzEeG6dsytM_VPtEkIhfwkrkI5QNwe2LXeE_vZCilGsBIx15eRVZvkMk

The output is the same as my library.
The only difference I can see is that I'm using the normal GCM endpoint (not the experimental Web Push one) with the raw_data parameter.

I'll have a look into what is needed to support normal GCM endpoint (in hindsight - it wasn't helpful using the other endpoint - apologies for not thinking it through)

Thanks. If I'm not mistaken, the temporary server has been updated as I can see that the aforementioned behavior now works well. :)


A-760/tcp reassembly

This has a bug fix from the previous PR. Overlength frames are now ignored but consumed without buffering so that messaging decoding multiple frames remains aligned.

I think adding a flag that allowed to fail on oversized frames instead of skipping them silently might be a good idea, but that's just an idea for the future.

maxFrameSize = Int.maxValue (the default value) achieves the same effect.

Merged via command line.


NIFI-3860: Relax the constraint that the ProcessSession must always b…

…e given the most up-to-date version of a FlowFile
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

https://github.com/markap14/nifi/blob/05833e9f13f31697d146c6fa735b506fd6005811/nifi-api/src/main/java/org/apache/nifi/processor/ProcessSession.java#L138

Must update this line or remove it.  Recommend updating to 'The effective flowfile operated on will be the most recent version of content and attributes known for this flowfile identity in this session.'

Recursive read allowance.  I think i get where this was going but i think something isnt quite right with it.  If we're going to allow/track multiple readers then we need to be doing it via a reference counter type logic i believe.
It doesn't look like this is quite true still right?  It is now more flexible in that it does allow multiple readers for a given flowfile.  So we need to make sure we're clear about the allowed pattern here which I think is we can have multiple readers to the flowfile but not if we have a writer to that flowfile.  Right?

https://github.com/markap14/nifi/blob/05833e9f13f31697d146c6fa735b506fd6005811/nifi-api/src/main/java/org/apache/nifi/processor/ProcessSession.java#L530
https://github.com/markap14/nifi/blob/05833e9f13f31697d146c6fa735b506fd6005811/nifi-api/src/main/java/org/apache/nifi/processor/ProcessSession.java#L559
https://github.com/markap14/nifi/blob/05833e9f13f31697d146c6fa735b506fd6005811/nifi-api/src/main/java/org/apache/nifi/processor/ProcessSession.java#L582

Shouldn't this also throw/do the IllegalState protection for active readers/writers?

https://github.com/markap14/nifi/blob/05833e9f13f31697d146c6fa735b506fd6005811/nifi-api/src/main/java/org/apache/nifi/processor/ProcessSession.java#L746

I checked through other places like the developer guide to see if we need to call this out but it looks ok.  Please make sure to think of anything we might be missing there.  I suspect API docs are sufficient to properly articulate this now more relaxed contraint in terms of developer flexibility (but not relaxed in terms of nifi's ability to enforce the critical conditions are still held).

Anyway - happy to take a look once the above is responded to/addressed as necessary.  I definitely see how this will help developers have a more flexible/intuitive interaction with the process session while we still hold the critical aspects firm.

@joewitt good catches. I have pushed another commit that I think will address all of the concerns above.

Ok @markap14 this looks great now with the updates to the Javadoc and the correction for tracking/allowing multiple readers.  Am +1.


Onboarding Matthew Luckie

Desired Username
mjl
SSH Key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDzAye8u7aR5J+39Bt9pXW53fe7qNxkqcqt6Xqf/5YTbmqHIXpBmQvlVN5dRg2acYIy1rrWxjN/d+T/1t4wOg84uuINrbAPc8nL/uTELFsDP1T+cz6TJWXN5BjUdH8IKfqgLSiZat9gC36zN5tiFNIzBDwSXgM16n9E1gByjGrd4+wMk7Gk1pETHySj6+9Doi3KTFS3qkmL+EjGQUP/BEdc1NFFzzTQu+SdVW1QkDePtY7RwLRzAmHIiruTIrZDG22KpiDfc86U9KmXvEXwGA9XbBc5DZbq3G0B5pGwFuHX9sBfzTWG5mHGqVBoUc5TH4gdv0JRyX6FjPDQhJz/aHlT<EMAIL_ADDRESS>
New Maintainer Initial Tasks

[x] Share Public SSH key (RSA, >2048 bytes)

Existing Maintainer Tasks

[ ] Add to "Route Views Maintainers" GitHub Team.
[ ] Setup @routeviews.org email account.
[ ] Provide access to our Grafana instance.
[x] Deploy public SSH Key to RV infrastructure (via Ansible).
[ ] Admit/ensure access to RV in PeeringDB.
[ ] Ensure access to RV Slack.
[ ] Provide access to the private Maintainer-only Slack channels. Today this includes: "peer requests" and "infrastructure".
[ ] Share Route Views KeePass Master Password. (e.g., do this via RV Slack using the "Secret Message" app)
[ ] Help the new member complete their first 'peer request'! (e.g., schedule a time within the next work-week)

New Maintainer Final Tasks

[ ] Set up your mail client with your new Route Views email address. Refer to our mail configuration documentation
[ ] (BONUS) Set up the<EMAIL_ADDRESS>email address also, giving you access to vast history of emails (credentials in RV KeePass).
[ ] Ensure access to Route Views Slack.
[ ] Review the RV Maintainer Handbook (TODO update link to GH Pages).
[ ] Set up a PeeringDB account, and 'request Affiliation' with Route Views  (ASN 6447) on your PeeringDB profile page
[ ] Ensure login, and take a look through dashboards in our Grafana instance.
[ ] Complete your first peer request! 😁 (with help from an existing maintainer)

Going to close this for now since @matthewluckie really just needed SSH access to collectors


Shorten text messages

I'm told it would be better to stay under 160 characters if possible, which is 1 segment. Not sure if the url is included in that. At least one of ours is 3 segments. It's not ideal because, among other things, the messages don't always arrive in the same order that they were written.

look for send sms to find all the text messages to edit

Not sure which one it is. Look for send_sms and what template it refers to in both the pro-se originating file and in remote_entrypoint.yml


installation fails

Error: Failed to fetch plugin https://github.com/subitolabs/cordova-gallery-api.git via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Same behavior at SuryaL fork

cordova plugin add https://github.com/SuryaL/cordova-gallery-api.git --save
(node:508) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Failed
to fetch plugin https://github.com/SuryaL/cordova-gallery-api.git via registry.


Consistency adjustments for documentation generator

Issue #, if available:
n/a
Description of changes:
This pull request applies consistency updates to the README files across a subset of patterns.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5862d6a09c4eb86a4007f3a4122ac1e3f44621c1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 5862d6a09c4eb86a4007f3a4122ac1e3f44621c1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: c9bec0ea1f10cbdcaacad53460110a719c861fa3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: c9bec0ea1f10cbdcaacad53460110a719c861fa3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 815dd054b194ad57d6a05d81d5e52fe7f7dea4b3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 815dd054b194ad57d6a05d81d5e52fe7f7dea4b3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


flutter build should warn when run on a master channel

We're observing that a good proportion of developers are on the master channel, which contains the very latest code that passes our tests. While master is viable (albeit aggressive) for development purposes, we would strongly recommend against using it for shipping production apps, yet we continue to see apps shipped to the store with it.
We propose that when flutter build apk or flutter build ios are run from a Flutter SDK that is on the master channel, we should proceed with the build but emit a message to the console that warns that this is explicitly discouraged.
The message should also include the following ASCII art to warn of the presence of fire-breathing creatures:
                \||/
                |  @___oo
      /\  /\   / (__,,,,|
     ) /^\) ^\/ _)
     )   /^\/   _)
     )   _ /  / _)
 /\  )/\/ ||  | )_)
<  >      |(,,) )__)
 ||      /    \)___)\
 | \____(      )___) )___
  \______(_______;;; __;;;

(just kidding!)

(is this an out of season april fools joke?)[https://www.youtube.com/watch?v=C2KeEUhmwbg]

I would always build from master just to see the graphic ;p

so... I'm implementing this as it seems like a quick fix... Do I put in the dragon?

The big dragon turns out to be too scary. With @Hixie 's suggestion, I'm putting in a red 🐉 (dragon) emoji to indicate the fire breathing dangers ahead.

We tried to fix this, but it turned out to be more subtle than its value warrants. Closing.


Adds mutation observer to link new blocks when they are created

Links were only being added when the page loaded, so new comments with typescript blocks wouldn't be linked until the page refreshed. This pr fixes it 😄
Before

After

@orta let me know if that's useful 🙏

Doh! Yep

I missed this pr

I’m on a phone but hopefully should remember to make a new build


Build fails with new caddy since switching to go modules

When did you download File Browser from caddyserver.com?
Building from source
What is your entire Caddyfile?
None
Description
Trying to build caddy with filebrowser from source, but the build fails since caddy switched to go modules.
Detailed issue with errors can be found here.
Expected behaviour
Successful build.
What is happening instead?
Mentioned at https://github.com/mholt/caddy/issues/2549
How to reproduce?
Mentioned at https://github.com/mholt/caddy/issues/2549

Same, go 1.12 here; this is the file that I'm trying to build:
package main
import (
  "github.com/mholt/caddy/caddy/caddymain"
    _ "github.com/filebrowser/caddy"
)

func main() {
  caddymain.Run()
}

go build outputs:
go: finding github.com/mholt/caddy/caddy/caddymain latest
go: finding github.com/mholt/caddy/caddy latest
go: finding github.com/GeertJohan/go.rice/embedded latest
go: finding github.com/filebrowser/filebrowser/errors latest
go: finding github.com/filebrowser/filebrowser/settings latest
go: finding github.com/filebrowser/filebrowser/users latest
go: finding github.com/filebrowser/filebrowser/http latest
go: finding github.com/filebrowser/filebrowser/auth latest
go: finding github.com/filebrowser/filebrowser/storage latest
go: finding github.com/filebrowser/filebrowser/storage/bolt latest
build build: cannot load github.com/filebrowser/filebrowser/auth: cannot find module providing package github.com/filebrowser/filebrowser/auth

@hacdias, any guess?


Titles in side nav should be sentence case

Description

Titles are title case, but they should be sentence case

Link to documentation

https://opensource.adobe.com/spectrum-css/
Additional context

Jess says so!

Jess probably still says so.