text:
Only One Slider Allowed?

I have two Sliders:
#1 Slider has one feed
#2 Slidef has eight feeds
All nine feeds show up in the second (#2) Slider

Please post your exact page markup to help diagnose the problem. Have you properly closed out the slider shortcodes?
Also, please wrap your markup using Markdown syntax:
```
Like this

... [display-column size=5]
... [display-flex size=2]
... [display-slider content="heading,image"]
... http://kiosk.fpcls.org/category/photos/feed
... [/display-slider]
... [/display-flex]
... [/display-column]
...
... [display-column size=5]
... [display-flex size=6]
... _____ F I R S T __ N E W S_____
... [display-slider layout=newspaper content="heading,caption"]
... http://kiosk.fpcls.org/category/announcements/feed
... http://kiosk.fpcls.org/category/session/feed
... http://kiosk.fpcls.org/category/youth/feed
... http://kiosk.fpcls.org/category/hospitality/feed
... http://kiosk.fpcls.org/category/worship/feed
... http://kiosk.fpcls.org/category/mission/feed
... http://kiosk.fpcls.org/category/men/feed
... http://kiosk.fpcls.org/category/women/feed
... [/display-slider]
... </
... </
... </
...
... [/display-flex]
... [/display-column]

I cannot reproduce this error:
[display theme=green]
  [display-row]
      [display-flex size=3]
        [display-slider layout=newspaper content="heading,caption"]
          https://asunow.asu.edu/feeds/sustainability
        [/display-slider]
      [/display-flex]
      [display-flex size=3]
        [display-slider layout=newspaper content="heading,caption"]
          https://asunow.asu.edu/feeds/sustainability-asu
        [/display-slider]
      [/display-flex]
  [/display-row]
[/display]

How is the best way of sliding photos that are in the wordpress media
library on my wordpress site?
Thank you so much for your help!
Tom Eagle
Dr.Tom.Eagle@gmail.com
816-524-4040 c
816-524-4041 h
On Feb 11, 2016 3:26 PM, "Ivan Montiel" notifications@github.com wrote:

I cannot reproduce this error:
[display theme=green]
[display-row]
[display-flex size=3]
[display-slider layout=newspaper content="heading,caption"]
https://asunow.asu.edu/feeds/sustainability
[/display-slider]
[/display-flex]
[display-flex size=3]
[display-slider layout=newspaper content="heading,caption"]
https://asunow.asu.edu/feeds/sustainability-asu
[/display-slider]
[/display-flex]
[/display-row]
[/display]
—
Reply to this email directly or view it on GitHub
https://github.com/gios-asu/apiarium-wp-plugin/issues/44#issuecomment-183065190
.

@TomEagle Please create a new issue for unrelated questions.

authors: TomEagle idmontie

repo: gios-asu/apiarium-wp-plugin


text:
[Bug] Search Issues

I can't filter on anything past the first few parts of the title when searching.
for example:
PRODUCTION DEGRADED: ptc0231.xl000_ptcprd085.wla.tla.uprr.com (CHK_LOG) - LOGS is degraded - ptcprd085.wla.tla.uprr.com - Workload Job PTC0231.XL000 is in FAILURE status
searching for production or degraded returns this item, trying to filter on anything else (like logs, or workload) returns nothing.

This has been patched under PR #129 and merged into develop - closing issue.

source: gharchive/issue

authors: giranm jmpoastUP

repo: giranm/pd-live-react

license: MIT

license_type: permissive

license_source: github-api


text:
E133：return not inside a function

vimcomplete/autoload/vimcompelte/lsp.vim line 79：

can you elaborate?

vimcomplete/autoload/vimcompelte/lsp.vim line 79：
E133：return not inside a function
there is full error.

Error detected while processing VimEnter Autocomands for "*",scrpts  vimcomplete/autoload/vimcompelte/lsp.vim line 79：E133：return not inside a function

What version of Vim? How do I reproduce this? Please provide more details. I do not see this error in my setup.

Linux version 3.10.0-1160.el7.x86_64 (mockbuild@x86-vm-26.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) #1 SMP Tue Aug 18 14:50:17 EDT 2020
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 27 2023 22:25:47)
Compiled by root@ciccmp513
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_urxvt -tag_any_white
+arabic +find_in_path +mouse_xterm -tcl
+autocmd +float +multi_byte +termguicolors
+autochdir +folding +multi_lang +terminal
-autoservername -footer -mzscheme +terminfo
+balloon_eval +fork() +netbeans_intg +termresponse
+balloon_eval_term +gettext +num64 +textobjects
+browse -hangul_input +packages +textprop
++builtin_terms +iconv +path_extra +timers
+byte_offset +insert_expand -perl +title
+channel +ipv6 +persistent_undo +toolbar
+cindent +job +popupwin +user_commands
+clientserver +jumplist +postscript +vartabs
+clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +vim9script
+cmdline_hist +langmap -python +viminfo
+cmdline_info +libcall -python3 +virtualedit
+comments +linebreak +quickfix +visual
+conceal +lispindent +reltime +visualextra
+cryptv +listcmds +rightleft +vreplace
+cscope +localmap -ruby +wildignore
+cursorbind -lua +scrollbind +wildmenu
+cursorshape +menu +signs +windows
+dialog_con_gui +mksession +smartindent +writebackup
+diff +modify_fname -sodium +X11
+digraphs +mouse +sound -xfontset
+dnd +mouseshape +spell +xim
-ebcdic +mouse_dec +startuptime +xpm
+emacs_tags -mouse_gpm +statusline +xsmp_interact
+eval -mouse_jsbterm -sun_workshop +xterm_clipboard
+ex_extra +mouse_netterm +syntax -xterm_save
+extra_search +mouse_sgr +tag_binary
-farsi -mouse_sysmouse -tag_old_static
system vimrc file: "
VIM: "/tools/vim/9.0/share/vim"
Compilation: gcc -std=gnu99 -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/uuid -I/usr/include/pixman-1 -I/usr/include/libdrm -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -std=gnu99 -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE -lm -ltinfo -lelf -lselinux -lcanberra -lrt -lacl -lattr -ldl

Can you upgrade Vim to 9.1 (latest) and try it? Many bugs were fixed regarding vim9 script artifacts.

Unfortunately, my gvim is an offline workstation and I can't network to update it!

Try again pl.

Unfortunately, configuration does not take effect

`
export def GetTriggerKind(): number
if !get(g:, 'loaded_lsp', false) || v:version < 901
return -1
endif
import autoload 'lsp/buffer.vim' as buf
var lspserver: dict<any> = buf.CurbufGetServerChecked('completion')
var triggerKind: number = 1
var line: string = getline('.')
var cur_col = charcol('.')

if line[cur_col - 2] !~# '\k'
    var trigChars = lspserver.completionTriggerChars
    var trigidx = trigChars->index(line[cur_col - 2])
    if trigidx == -1
        triggerKind = -1
    else
        triggerKind = 2
    endif
endif

return triggerKind

enddef
`
I modified it，but  there is a new error   named  as   <  error detected while compilingVim EnterAutocommands for "*"..Autocommands for "VimCompteteloaded"..function56_RegisterPlugins[11]..1[4]..vimcomplete#completor#register[1]..23: line 4: E117 unknow function :indexof >.  Maybe can use it  in  9.0.0196   .     You have some plugin that needs a rather recent version of Vim (indexof() was added in 9.0.0196)

You can implement indexof() yourself:
def IndexOf(lst: list<any>, str: string): number
    for [i, v] in lst->items()
        if v.name == str
            return i
        endif
    endfor
    return -1
enddef

Now replace completors->indexof((_, v) => v.name == source) with IndexOf(completors, source).
I have not tested it, but it should work.

https://github.com/girishji/vimcomplete/commit/ba8e576c8348a848b0f90dd2fe865fa8f7a0564a

repo: girishji/vimcomplete


text:
Android-Java: 1.12 Dalvik-Virtual-Machine

Description
Android-Java: 1.12 Dalvik-Virtual-Machine
Domain
Android Dev (Java)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign documentation

This was closed only because the issue was not assigned to me yea?

This was closed only because the issue was not assigned to me yea?

We have already merged a PR on this issue.

repo: girlscript/winter-of-contributing


text:
Data Science with Python : Data Visualizations using Matplotlib

Welcome to 'DSWP' Team, good to see you here
This issue will helps readers in getting all the guidance that one needs to learn about Data Visualizations with Matplotlib. Tutorial to Data Visualizations with Matplotlib and how it's applied visually.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly if you had used datasets, include them in "DS Datasets".
Domain : Data Analysis and Visualizations
Mentors Assigned : Shivang Dubey / Nithin
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎

I want to contribute in this issue.
I am from ds python batch 20

I would like to work on this issue, which is issue no. 445
Name: Shubham Patel
Serial No. 104.
Type: Documentation
Approach:

Introduction to Matplotlib library
Several types of Visualization techniques using Matplotlib
Alternatives of Matplotlib for visualization in Python

Hey @prathimacode-hub, I would like to work on this
Name - Dakshita Thakkar
Sno - 392
Type : Documentation, Audio

@KhushiKV this issue is allotted to you for documentation and video.
@ShubhamPatel01 @Malvikakaushal2001 @dakshitathakkar, any of you can choose audio if you are interested. This issue is assigned to Khushi as she was assigned to wrong issue earlier.
There are many more issues coming. Stay tuned to grab.

@prathimacode-hub Thank you very much...I will prepare the Documentation.

I am bhaswati roy from dswp batch 19
I would like to contribute for this.

@KhushiKV this issue is allotted to you for documentation.
@ShubhamPatel01 @Malvikakaushal2001 @dakshitathakkar, any of you can choose video / audio if you are interested. This issue is assigned to Khushi as she was assigned to wrong issue earlier.
There are many more issues coming. Stay tuned to grab.

I would like to work on this issue, which is issue no. 445
Name: Shubham Patel
Serial No. 104.
Type: Video
Approach:

Introduction to Matplotlib library

-Several types of Visualization techniques using Matplotlib
-Alternatives of Matplotlib for visualization in Python

@KhushiKV this issue is allotted to you for documentation.
@ShubhamPatel01 @Malvikakaushal2001 @dakshitathakkar, any of you can choose video / audio if you are interested. This issue is assigned to Khushi as she was assigned to wrong issue earlier.
There are many more issues coming. Stay tuned to grab.

I would like to work on this issue, which is issue no. #445
Name - Dakshita Thakkar
Sno - 392
Type : Audio

I would like to work on this issue which is issue no. #445
Name - Pradipta Nandi
Sno - 250

@Nithin-Reddy-02 @shivangdubey mentors, Hi I am Khushi, since I have been assigned this issue for Documentation, I thought about updating you with the status, as we were asked to. Should I messages you here only for further communication? So far, I have decided what all resources I would be using to make my contribution and collected most of the data, I will start the Coding part shortly afterwards.
Thank you

Hello @KhushiKV, you can communicate here or even in the discord as per your comfort. Its a good thing you have started working and completed collecting the data, take your own time and start the coding part and make sure the resources you use are well recognised/cited. You can keep updating about your work whenever possible and finally ping me if you have any doubt or if you need anything, I'd be happy to help you.

@Nithin-Reddy-02 @shivangdubey mentors, Hi I am Khushi, since I have been assigned this issue for Documentation, I thought about updating you with the status, as we were asked to. Should I messages you here only for further communication? So far, I have decided what all resources I would be using to make my contribution and collected most of the data, I will start the Coding part shortly afterwards.
Thank you

For this issue, you may use GitHub only. And for any other doubt ping at Discord. All the best!

Issue is assigned to @ShubhamPatel01 for Video.
@dakshitathakkar, have you been alloted to any other issue? If not also add up your approach in your comment.

Issue is assigned to @ShubhamPatel01 for Video.
@dakshitathakkar, have you been alloted to any other issue? If not also add up your approach in your comment.

I am assigned an issue but it is under another domain and not under Data Science with Python. It's all right if I can't contribute to different domains at the same time, and if  I can, I've added an approach in my previous comment.

That's ok if it's for other domain, as long as no multiple issues are assigned in same domain.
Issue allotted to @dakshitathakkar for audio contribution

Hello, this message is regarding timely update of issue assigned. I have completed making graphs to show in my video presentation and will be recording the video by end of the week.

Hi, This is regarding an update of my work on this issue. I've recorded the audio and made a presentation for the same. Will shortly upload the files on google drive and complete the work.

Hi, I would like to provide an update about my work for this issue, I have written and prepared the Colab notebook halfway so far. I would be completing it soon. Thanks.

@Nithin-Reddy-02 @shivangdubey mentors, hello...I have completed my documentation for this issue and have opened a pull request for the same. Please let me know if you are able to see and merge it with the repository.
Is there anything else that needs to be done from my end for this?
Thank you very much.


text:
Infix To Postfix in C

Description 📜
I have prepared a documentation on:
To Convert Infix Expression To Postfix Expression using Stack Data Structure In C :)
Hope you learn from it 👍
Fixes #7351

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Okay sir

@deeqakkk sir,
I have made the required changes. Please have a look :)

@Saviour1001  Already implemented in C++ here
This one's in C, works too right?

@Suvraneel Kindly check on this once :)

source: gharchive/pull-request

authors: Suvraneel ikavyajain


text:
C_CPP : Banker's Algorithm (OS)

Description 📜
This documentation on banker's algorithm includes brief explanation on Banker's Algorithm along-with an example, then algorithms used in Banker's Algorithm are described followed by code of Banker's Algorithm and its output. Also, advantages and disadvantages of Banker's Algorithm are stated.
Fixes #8105

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[x] C/CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@palak1101  Entire code plagiarised from here , even some part of documentation


text:
Remove defaultvalue in swagger documentation

In gitlab by @sylvaingaudan on Jul 19, 2017, 17:11
In the swagger documentation of the REST services, some default values are provided. For instance, sort is based on the country field, which is probably unexisting from most collections. Those default/example values should be removed.

In gitlab by @sylvaingaudan on Jul 21, 2017, 12:17
changed milestone to %6

In gitlab by @sfalquier on Jul 28, 2017, 10:27
added ~2377174 label

In gitlab by @sylvaingaudan on Aug 10, 2017, 08:31
changed milestone to %10

In gitlab by @sfalquier on Aug 18, 2017, 10:02
added ~2424199 and removed ~2424198 labels

In gitlab by @sfalquier on Aug 18, 2017, 10:14
mentioned in commit 19d07206fbf0968e902cbff30b86a9ad8774de39

In gitlab by @sfalquier on Aug 18, 2017, 10:15
mentioned in merge request !80

In gitlab by @sfalquier on Aug 18, 2017, 10:15
assigned to @sfalquier

In gitlab by @sfalquier on Aug 18, 2017, 10:41
mentioned in commit 1be7a5ee7a015f167e0f43f61d395cfb723e4908

In gitlab by @MohamedHamouGisaia on Aug 18, 2017, 16:12
closed via merge request !80

In gitlab by @MohamedHamouGisaia on Aug 25, 2017, 11:48
mentioned in commit 999efa7cddb5a510bd9f1b342bc6e26ab316cdee

repo: gisaia/ARLAS-server


text:
要安装mongodb的吧？

要安装mongodb的吧？会报这样的错误：

是的，安装后启动mongodb服务就可以了

authors: giscafer paraofheaven

repo: giscafer/Ponitor

license: mit

license_source: bigquery


text:
Only allow Voila app to access a specific directory

When deploying a geemap web app using Voila, the open file dialogue allows access to the entire system directory, which is a security risk. ipyfilechoose v0.6.0 now allows restricting access to a specific directory by setting the sandbox_path property.
https://github.com/crahan/ipyfilechooser/issues/35#issuecomment-916107443
fc3 = FileChooser('/content/sample_data')
fc3.sandbox_path = '/content'
fc3

This feature has been implemented. One can now specify a sandbox_path. When the app is deployed using Voila, open-file dialogue can only access files within the sandbox_path, avoiding unauthorized access to system directories.
m = geemap.Map(sandbox_path='/path/to/folder')

repo: giswqs/geemap


text:
[BUG] Fix dark mode design #169

Fixing bug reported by @samanyougarg in https://github.com/gita/gita-frontend-v2/issues/169

In the search bar (dark mode), the text color was grey, changed it to white

Fixing the dark mode modal design which appears on subscribing

Looks good, merged.

authors: samanyougarg sarthak-kumar-shailendra


text:
Haskell security advisory database (Hackage packages)

Repository: https://github.com/haskell/security-advisories
They had an issue to created to add the database to this repo, but was closed and I'm not sure if conversations ever happened: https://github.com/haskell/security-advisories/issues/11

They confirmed the task was closed by mistake. So I'm asking to integrate haskell security advisories into this repo :) Let me know how and if I can help achieving that!

The haskell/seucirty-advisories issue has been reopened

@MathiasSM @mihaimaruseac thank you for reaching out! Unfortunately, Haskell is not currently a supported ecosystem for the Advisory Database, so we would not be able to support adding these as reviewed advisories that would then generate Dependabot alerts. We don't currently have capacity to expand our ecosystem support for the Advisory Database, but I am happy to leave this issue open so that others with similar needs can upvote and chime in.

authors: MathiasSM carogalvin mihaimaruseac

repo: github/advisory-database


text:
[GHSA-cj88-88mr-972w] glob-parent before 6.0.1 vulnerable to Regular Expression Denial of Service (ReDoS)

Updates

Affected products
Description
References
Summary

following

authors: cowsrule fhljys


text:
Upgrade combobox-nav to v2 for ARIA 1.2

This upgrades combobox-nav to v2 for ARIA 1.2 combobox pattern support.
Note that this is a breaking change because we are not using aria-owns anymore. I changed it to for so it's more neutral and are unlikely to need to change for external reasons.
This also adds optional support alt + arrow keys (https://github.com/github/auto-complete-element/pull/42/commits/3c434192d515f51566ca8d53b37edac24731f3c8). However I wonder what people's opinion on this is? as there's already a default action for alt + arrow keys, which is to move cursor position. Adding support for this means we'd either 1. override the default behavior 2. add this a side-effect for the default behavior. Personally I find 1 not ideal, and 2 unexpected (moving cursor causing the listbox to expand). For now I've opted for 2, but I wonder if folks have strong opinions on this.
Test page. Inputting @ will match all the results. cc @jscholes

@muan

there's already a default action for alt + arrow keys, which is to move cursor position.

Could you elaborate on this?  This sounds nonstandard and unexpected.

Could you elaborate on this? This sounds nonstandard and unexpected.

@jscholes Sorry I wasn't clear. It's macOS specific, but I can't find their docs on text area specific navigation. It works like ctrl + arrow keys on Windows.
It's in the mac's Pages app shortcut docs though for what it's worth:

Move to the beginning of the paragraph | Control-A or Option-Up Arrow
Move to the end of the paragraph | Control-E or Option-Down Arrow

This works in all text areas across browsers on mac.

Ah, okay.  In that case I'd probably go with option 1, because Mac users can presumably also press FN+Left/Right Arrow to move to the beginning or end of line.  If they don't have an FN key, the text is likely to be short.
It's worth remembering that on the Mac, this pattern isn't common in the first place.  A native <select> manifests itself as a "Menu Button" (in ARIA parlance), so users are already encountering something they don't really expect.

@jscholes Thanks. It seems like Up/Down arrows without modifiers do the same thing inside of an input as well, not text area, but in this case we are only dealing with input I've made the change. Have you found any issues with the test case?

No, this should be good to go.  Looking forward to the accessibility
improvements this will bring and facilitate!

authors: jscholes muan

repo: github/auto-complete-element


text:
Discrepancy between gh auth login and docs

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/get-started/getting-started-with-git/caching-your-github-credentials-in-git#github-cli
What changes are you suggesting?
The gh auth login section says:
1. Install GitHub CLI on macOS, Windows, or Linux.
2. In the command line, enter gh auth login, then follow the prompts.
  * When prompted for your preferred protocol for Git operations, select HTTPS.
  * When asked if you would like to authenticate to Git with your GitHub credentials, enter Y.

Yet when running I'm not promted if I want to authenticate with git:
(base)user@computer % gh auth login
? What account do you want to log into? GitHub.com
? You're already logged into github.com. Do you want to re-authenticate? Yes
? What is your preferred protocol for Git operations? HTTPS
? How would you like to authenticate GitHub CLI? Login with a web browser

! First copy your one-time code: code
- Press Enter to open github.com in your browser...
✓ Authentication complete. Press Enter to continue...

- gh config set -h github.com git_protocol https
✓ Configured git protocol
✓ Logged in as BastianZim

Additional information
Version:
gh version 2.0.0 (2021-08-23)
https://github.com/cli/cli/releases/tag/v2.0.0
Installed through brew.
macOS Big Sur 11.6

@BastianZim

gh auth has now been depreciated:
https://dev.to/github/how-to-never-type-passwords-when-using-git-18bb
This is now to do this now. Docs should reflect this.

This doc is perfect: https://docs.github.com/en/github-ae@latest/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent

Are you sure that it's depreciated? Because it doesn't ask for my username and password anymore, it now opens the browser and asks me to log in there.
Additonally, it's well and alive in the gh docs and no depreciation notice is given.

Hi, GitHub CLI developer here.
I think @mishmanners had a typo; it's not gh auth that's deprecated, but git password authentication that's been disallowed on GitHub since a few weeks ago. You may no longer use your GitHub password to authenticate git operations. Note that it already wasn't possible to use your password if your GitHub account was 2FA-enabled.
The article that @mishmanners shared lists several alternative methods of authenticating git with GitHub and gh auth login is one of them. As an easier alternative to manually generating a Personal Access Token to use for git, for example, I would recommend using gh auth login instead, choosing the "HTTPS" protocol for git, and allowing gh to "authenticate git with your GitHub credentials". This will set up GitHub CLI as your git credential helper (you may inspect that in your ~/.gitconfig).
@BastianZim The prompt "Authenticate git with your GitHub credentials?" will not show if you already have gh set up as a credential helper for git. Could this be the case?

That was the case, thanks @mislav.
In case that's something that the docs team wants to add as a disclaimer I'll keep the issue open but would otherwise close it.

Thanks everyone, I think this is good to close!

authors: BastianZim lecoursen mishmanners mislav ramyaparimi

repo: github/docs


text:
Update access-supachai01-on-github.md

Name for description..

Why:

What's being changed:

Check off the following:

[ ] All of the tests are passing.
[ ] I have reviewed my changes in staging.
[ ] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Token-crypto-fiat-BTC-GOLD


text:
Removing the use of templates

Why:
This relates to, but doesn't close, https://github.com/github/docs-content/issues/5847

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@pulkitaggarwl (cc @myarb) - I needed to make some editorial changes (including updating the file names), which I couldn't do on your fork, so I've moved this to a new PR on the docs-internal repo: https://github.com/github/docs-internal/pull/23823
I'll close this PR now.

authors: hubwriter pulkitaggarwl


text:
Update about-saml-for-enterprise-iam.md

This is linked to this Issue: Inconsistency between SCIM support #11639

Why:
Closes 11639

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@EMILYMC0 Thanks so much for opening a PR! I made a slight edit to link your PR to the issue.
I'll get this triaged for review! :zap:

👋🏻 we actually already document the fact that SCIM is not supported at the enterprise-level unless you use EMUs in the note box 2 paragraphs down. We don't use the phrase "non-EMU SAML" in the Docs so I'm going to go ahead and revert this change. Sorry for the confusion here!


text:
Upgrade node version for service containers

Why:
I just followed the instruction for service containers in both Postgres and Redis tutorials, they both throw the following exception when running:

Closes:
N/A

What's being changed (if available, include any code snippets, screenshots, or gifs):
I'm changing the container image from node:10.18-jessie to node:20-bookworm-slim (happy to change to something else if there is another suggestion or pattern).
I did confirm that with node:20-bookworm-slim the workflow runs successfully.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@hsnabszhdn Thanks so much for opening a PR! I'll get this triaged for review ✨

@hsnabszhdn Thank you for your patience while our team reviewed your PR! They agree with your changes here, and thank you for updating one of our older examples 💛
This repo is currently in a code freeze, but we will get this merged as soon as the freeze ends on 9/16 🍏


text:
upload file with multipart/form-data

I remove the content-type in headers ,  but it's still not what i want .   the data is show under the payload request.   i  expect formdata, like the second picture:

current

expect

anyone know how to solve this ?

Sorry, this is a bug tracker for a polyfill of fetch() functionality, not a place to ask support questions on how to implement requests in your app. All modern browsers now implement fetch() natively, so it's likely that the code of our polyfill doesn't even run in this case. Please ask usage questions on more appropriate forums such as Stack Overflow.
To send form data via fetch, pass a FormData instance as request body and avoid setting Content-type manually. The browser will handle the rest.

authors: ceerqingting mislav

repo: github/fetch


text:
Fix js version to test with Travis CI

Since version 0.10 does not have Promise, hubot-test-helper can not be used.
Travis CI log:
...
$ npm test
...
  1) foobar responds to hello:
     ReferenceError: Promise is not defined
      at Room.receive (node_modules/hubot-test-helper/lib/index.js:79:18)
      at Object.Room.user.say (node_modules/hubot-test-helper/lib/index.js:62:26)
      at Context.<anonymous> (test/foobar-test.coffee:21:29)
  2) foobar hears orly:
     ReferenceError: Promise is not defined
      at Room.receive (node_modules/hubot-test-helper/lib/index.js:79:18)
      at Object.Room.user.say (node_modules/hubot-test-helper/lib/index.js:62:26)
      at Context.<anonymous> (test/foobar-test.coffee:27:29)
...

Remove version 0.10.
Add version the latest node and 6, 5, 4.

Ran into this today. Would be good for the defaults to reflect the LTS support of Node.

Thanks!

authors: 178inaba bkeepers stephenyeargin

repo: github/generator-hubot


text:
Update Java.gitignore

Reasons for making this change:
In order to use IntelliJ for Spring, Grails,... projects; you may need to generate some files, and this files are useful for developers that uses the same IDE. If anyone use Eclipse or Netbeans instead of IntelliJ, this 3 files are unnecesary. IMPORTANT: I think that this configuration works too for Android Studio.
Links to documentation supporting these rule changes:
https://www.jetbrains.com/help/idea/2016.2/project.html#newProjectFormat
The documentation says that the .ipr file should be versioned, but this is in the context that all devs in the project are using IntelliJ
IntelliJ integration files

Thanks, but see Global\JetBrains.gitignore as that should be tracking these changes

authors: rossifedericoe shiftkey

repo: github/gitignore


text:
Removed redundant VS 6 technical files

Reasons for making this change:
Visual C++ cache files
*.aps
*.ncb
Already contains the vs 6 technical files
See:
https://github.com/github/gitignore/blob/main/VisualStudio.gitignore#L106
https://github.com/github/gitignore/blob/main/VisualStudio.gitignore#L107

Any reason why this was not merged?


text:
Edited cleanness

It really is

This file is Ruby. The semicolons aren't needed.

authors: larryystang mastahyeti

repo: github/hoosegow


text:
Hubot behind a proxy

I'm behind a proxy, and while hubot ping works just fine, math me 2+2 doesn't work. In fact, any step that uses a get() in the script just doesn't work at all. How do I either:

Tell Hubot to use a proxy when doing a .get()?
Get some additional debugging out of Hubot so that I can diagnose why things aren't working?

Thanks!

+1 for this feature if you guys implement it

Hey all,
I've created a gist with a quick fix, we use it for our company's hubot. I know your feels, corporate proxies are awesome for system administrators, but suck for developers.
https://gist.github.com/MitchK/69fbfb90fce6e76afd62
Please note that all requests will go through that proxy, even requests internally. Depending on the corporate proxy configuration, this might result in 404 requests if requesting internal sites through that proxy.
Since we use Docker to deploy our hubot(s), we just simply overwrite this file after any npm install or yo hubot:
...
# Run yeoman
RUN su $HUBOT_USER -c "yo hubot --owner=\"$HUBOT_OWNER\" --name=\"$HUBOT_NAME\" --description=\"$HUBOT_DESCRIPTION\" --adapter=\"$HUBOT_ADAPTER\" --defaults"

# Add proxy hack for hubot
ADD hacks/node_modules/hubot/node_modules/scoped-http-client/src/index.js node_modules/hubot/node_modules/scoped-http-client/src/index.js
...

Hope that helps some people locked behind firewalls. Cheers

For those following along, @michaelansel started work on a solution to this over in https://github.com/github/hubot/issues/884 and https://github.com/technoweenie/node-scoped-http-client/issues/31

@michaelansel Where is it you load in your proxy work around?

@jlbates504 You just create a script with no listeners. It will get executed during startup and be ready for all your listeners to use afterwards.
https://hubot.github.com/docs/patterns/#forwarding-all-http-requests-through-a-proxy

Hi all,
I wrote an external script that loads proxy setting from environment variables
to make it easier. I hope this helps.
https://www.npmjs.com/package/hubot-proxy-loader

@notok - thanks, this worked like a champ :+1:

authors: MitchK jlbates504 michaelansel notok nottinhill paschmann samstarling technicalpickles

repo: github/hubot


text:
No syntax highlighting or autocomplete in action

Describe the bug
When defining an action .github/actions/[action-name]/action.yml,  there is no syntax highlighting for using variables and there's also no "help" from autocomplete for inputs, etc. like there is in a normal workflow.
To Reproduce
Steps to reproduce the behavior:

Create an action
Write some inputs
Use said inputs in steps
See error

Expected behavior
Proper syntax highlighting and autocomplete.
Screenshots

Extension Version
v0.27.0
Additional context
Add any other context about the problem here.

+1 for this issue, not sure how this was overlooked and not reported previously.

Similar issue:

https://github.com/github/vscode-github-actions/issues/325

@agracio I'm in the same situation. It's even used as an example to place them in the directory that I have. How is that not implemented as basic functionality in the plugin?

authors: agracio muzimuzhi mwkcoding

repo: github/vscode-github-actions


text:
Remove gitpod.io from created components and hint at the fact that the script generates files

Description

Remove gitpod.io from the list of created components.
Add a line in the readme to make it clear what the script produces

Related Issue(s)
#9821
How to test

Release Notes

NONE

Is it true that the next step is step 4 in the getting started guide?

repo: gitpod-io/gitpod-eks-guide


text:
🛑 MSP-002 is down

In 59d818e, MSP-002 (https://msp-portal.gw002.oneitfarm.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-002 is back up in a41ee61.

repo: gitsrc/upptime


text:
增加安卓的沉浸式效果

Platforms affected
What does this PR do?
What testing has been done on this change?
Checklist

[ ] Reported an issue in the JIRA database
[ ] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[ ] Added automated test coverage as appropriate for this change.

pass

repo: gizwits/cordova-plugin-statusbar


text:
LiveScript under Typescript

Hi.
I would like to remind that livescript should be built under typescript instead of javascript. Because new angular 2.0 will use typescript. It means that LiveScript will loose all developers who will move to angular 2.0

?

I mean we will be not able to use livescript with angular 2.0

My client has concirns about livescript future because if it not support angular 2.0 it means livescript will not have a future

Angular 2 will not require typescript. You'll still be able to use JS, and thus LS, don't worry :-).

(also, javascript is a lot more than just angular)

authors: askucher vendethiel

repo: gkz/LiveScript


text:
Long-running tasks

For long running tasks, show a progress bar or some message telling users to wait
Would be good if we can submit tasks to run in the background, e.g. using celery?

Two long running tasks are slow in particular and really need some kind of 'Please wait' message ...

the initial mapping of data using reactome
PLAGE analysis

Added the message for the initial data submission. Not yet done for the others.

repo: glasgowcompbio/GraphOmics


text:
🛑 Schoelcher is down

In b5290ba, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 1b57ec7 after 5 minutes.

repo: glefait/martinique-public-websites


text:
🛑 Schoelcher is down

In 8d6846e, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in ca55868 after 5 minutes.


text:
🛑 Saint-Pierre is down

In aff7c33, Saint-Pierre (https://saintpierre-mq.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Saint-Pierre is back up in adf7d28 after 7 minutes.


text:
🛑 Martinique Transport is down

In 0e3d26a, Martinique Transport (http://www.martiniquetransport.mq) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Martinique Transport is back up in b71bb6e.


text:
🛑 Schoelcher is down

In c136cbb, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in b15b043.


text:
🛑 Schoelcher is down

In e41b3f5, Schoelcher (https://www.mairie-schoelcher.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in c7a5ca4.


text:
Support for additionalProperties

Context

hapi-swgger version: 9.0.2

What are you trying to achieve or the steps to reproduce ?
Our API returns normalized data, like:
{
   article: {
      id: 'article:1',
      title: 'Hello World!',
      tags: [
         'tag:1',
         'tag:2'
      ]
   },
   tags: {
      'tag:1': {
         id: 'tag:1',
         name: 'Animals'
      },
      'tag:2': {
         id: 'tag:2',
         name: 'Cat'
      }
   }
}

Currently, it's impossible to describe responses with KeyValue pairs (tags object).
Swagger 2.0 supports additionalProperties property for solving this issue.
Suggestion
Transform Joi.object().pattern(regex, schema) to additionalProperties in JSON (currently hapi-swagger ignores object.pattern)
Then following code (hopefully) should generate proper Swagger documentation:
Joi.object().keys({
   tags: Joi.object().pattern(/.*/, Joi.object().keys({
      id: Joi.string(),
      name: Joi.string()
   }))
});

I find myself in need of such a feature myself. Any chance this could be implemented soon?

There is no timeline for this feature request. PRs are welcome.

Heya @robmcguinness! In the meantime I've noticed support has been added for parsing a Joi.object().patter(pat, schema) structure, but output's not quite right... I'll try to have a look into it and get back to you.

Sounds good!

authors: CatalinMustata robmcguinness shtrihstr

repo: glennjones/hapi-swagger


text:
update docstring which inaccurately says GLFW_CONTEXT_REVISION is a window hint

This docstring previously indicated that GLFW_CONTEXT_REVISION was a window
hint and attribute, but in fact it is only a window attribute (there is no code
which uses this constant in any other context.)
We noticed this in https://github.com/hexops/mach/pull/71/files#r749741814
Signed-off-by: Stephen Gutekanst stephen@hexops.com

Thank you for the fix!

authors: elmindreda slimsag

repo: glfw/glfw

license: Zlib


text:
Some http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/ paths result in 503

While it is possible for me to navigate the directory structure of
http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/
in the browser, some paths, such as
http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
result in Error 503 No route to host. Some other package paths, for example:
http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/abcde-doc-2.7.2-r0.apk
, result in similar error. For some reason
http://dl-cdn.alpinelinux.org/alpine/v3.4/main/x86_64/zsh-5.2-r0.apk
downloaded fine.
Look like varnish cache related issues:
Error 503 No route to host

No route to host

Guru Mediation:

Details: cache-dfw1838-DFW 1471960403 3282534343

Varnish cache server

This should now be resolved. https://status.fastly.com/incidents/0523znjnppc4

Resolved for me.

authors: Multiply tristanls

repo: gliderlabs/docker-alpine


text:
Unprivileged user can gain root privileges

I'm not sure how the wheel group is treated in docker-alpine but why does it exist if one can gain root privileges without being member of it?
# docker run -i -t --name="test" alpine /bin/sh
/ # adduser -S testuser
/ # groups testuser
nogroup

# docker start test

# docker exec -it --user=testuser test /bin/sh
/ $ whoami
testuser
/ $ su
/ # whoami
root
/ # groups testuser
nogroup
/ # groups root
root bin daemon sys adm disk wheel floppy dialout tape video
/ #

In ubuntu-docker this does not work.

That just means root has an empty password; the wheel group only matters for the sudo command.

Correct. This is the difference to the containers CentOS and Ubuntu where the root password is disabled by default.
Please close.

close

why we dont remove root passwd by default in alpine?
https://talosintelligence.com/vulnerability_reports/TALOS-2019-0782

See https://github.com/gliderlabs/docker-alpine/pull/511

I think its unfair to blame gliderlabs for this one. It was my mistake.

authors: ncopa tianon widder yosifkit zakkg3


text:
Updated Builder script

Updated the builder so that it doesn't relay on a pre-existing alpine image. This allows for people to
create Alpine linux when they can't use public images.

I am also working on official upstream rootfs images with the v3.5 release

Let's revisit this. Can you give a brief demo of using this and how it might affect our current pipeline? Then I can try it out locally.
From the looks of it, it appears to build a alpine:base first which is then used to build each of the images?

Correct it does build base then builds each version from inside that image.

authors: andyshinn moos3 ncopa


text:
feature(etcd): Directory garbage collection

In our story we need to keep directory list clear from empty ones. So I add this code to remove a directory when it's empty.

ping @progrium

Thanks. I think this should stop at r.path instead of going all the way to up to / to ensure that registrator doesn't accidentally delete parent directories of the path it's using.
Also, can you run this through the gofmt tool? I just noticed a missing space before one of the { brackets, though gofmt is quite nice for making sure that all of your Go code follows the standard formatting guidelines.

Thank you Matt for your comment.
etcd client DeleteDir method throw an error if directory is not empty and on the other hand in creation time child dirs will be create if requested.
so I think that's not important if we remove empty directories.

Thanks yes, I see that DeleteDir will not allow deleting non-empty directories, so that should be ok.
I agree that it would usually be harmless to delete empty parent directories, however I still want to make sure registrator doesn't make any changes outside of it's root. This may surprise or confuse users if registrator's directory disappears, and may in some uncommon circumstances cause issues if registrator deleted a directory the user expected to exist.
I can make the change myself, but if you have a chance it may help me get this merged a little sooner. Please also run gofmt to format the code as well.

You right.
Changed my code; stop garbage collecting at r.path directory and fix code style format.

ping @mgood

ping @mgood

ping @mgood

ping @vidarl

LGTM

authors: majidgolshadi mgood vidarl

repo: gliderlabs/registrator


text:
[1.18.1] Deathlog Restore doesn't work on dedicated servers

Mods installed for test:

deathlog-0.2.4+1.18
fabric-api-0.45.0+1.18
modmenu-3.0.1
trinkets-3.1.0

Steps for reproduction:

connect to dedicated server with deathlog, have op/be in creative
have inventory and die
Open death log, and shift-click the restore icon
Return to game and see inventory is not restored
Check log
Expected: will restore like single player
Actual: does not restore, outputs error in log

Here's the server log: https://pastebin.com/qfAb2QEs

This is actually to be expected, as you have to use /deathlog view <playername> on a dedicated server to get the correct screen from which you can restore the death infos for a given player. In you case, you did still discover a bug because when opening the client-side screen on a dedicated server you should not be able to restore, so thanks for reporting
Cheers

Ah, I see. I must've missed the information regarding it requiring a command on server somewhere, apologies.
Just ran the updated build. As a user, I feel like if I have Operator and open the client side screen while in multiplayer; it should be equivalent to executing /deathlog view @p, for a more seamless experience. Feels a like an weird extra step if I'm able to open the client side menu without a restore button, but typing the command and opening it provides the exact same menu with restore buttons.  Having the command available to see/restore others that are not operator is great though, so glad to have it.

You see, the two screens you get from your client and the server are not equivalent at all. One of them has the deaths you client has tracked globally, for every world and server versus the other one which just shows the server-side log which is tracked by the server for each player individually and requires DeathLog to be installed on the server as well as operator permissions. So while I do see where you're coming from, it'll stay how it is to provide a clear separation of concerns.

repo: gliscowo/deathlog


text:
Create parser_southafrica.toml

First draft of the South Africa data. Contains all tables. There are many comments - mostly questions / queries of things I wasn't sure how to map / include in the parser. Feedback and edits most welcome.

Report on full data

table
valid
total
percentage_valid

subject
493980
494547
99.885350%

visit
494143
494547
99.918309%

observation
2033898
2038754
99.761815%

subject

316: data must contain ['subject_id', 'country_iso3', 'enrolment_date', 'age', 'sex_at_birth', 'ethnicity', 'pathogen'] properties
251: data.age must be smaller than or equal to 120

visit

404: data must contain ['visit_id', 'subject_id', 'country_iso3', 'start_date', 'outcome', 'date_outcome'] properties

observation

4856: data.is_present must be boolean

authors: abhidg ekamau

repo: globaldothealth/isaric


text:
Filter fill()

Hello,
This is a new filter that permit returning a fit-in centered image with the size requested.
The empty aera are filled with the color passed as color name or hexadecimal code (with the starting #)
http://192.168.135.117:8887/unsafe/fit-in/80x80/filters:fill(blue)/github.com/globocom/thumbor/wiki/tom_before_brightness.jpg
result in a square image of 80x80 size with fit-in tom centered and surrounded by blue lines
This could be usefull when having  needed for precalculating page rendering on browser without breaking ratio of the image when width and height is not known.
I also add the "paste" method missing in graphicsmack engine and a new engine method "gen_image" to generate a uniform colored image of whatever size.
I would like some tests for this class but need some template for filters to help me.
Cheers,
--
Damien

We'll come up with some filter tests soon... Sorry and thanks A LOT for the contribution.

repo: globocom/thumbor


text:
Loading indicator for image uploading

The existing loading animation (the drop zone “pulses” a little bit from opacity 0.8 to opacity 1) didn’t feel very obvious. Instead, I’ve added a loading spinner that replaces the icon while the image is uploading.
https://user-images.githubusercontent.com/30215449/174159545-445dfd12-5575-4eb4-9b88-5184bb0f855a.mp4

Didn’t know LuxSpinner existed! It looks good. I swapped it in and prevented the drop zone’s height from jumping.
https://user-images.githubusercontent.com/30215449/174404520-b813bfed-beb3-4994-a845-f43ff130a4ee.mp4

repo: glow-xyz/nftoken


text:
Composition api

upgrade element-plus、vue-router、vuex、sass
fix Iframe component bug
fix keep-alive bug

upgrade element-plus、vue-router、vuex、sass
fix Iframe component bug
fix keep-alive bug


text:
add normalize.css

I want to remove margin of header image.
I add normalize.css, reset default css.
before:

after:

merged.

authors: gmkou sassy

repo: gmkou/FikaNote


text:
Use OR Mapper

Introduce mongoengine
Update requirements.txt with pip freeze

LGTM


text:
minor: please use git annotated (or better signed) tags

$> git describe
fatal: No annotated tags can describe 'e27614b6abbc53e54d0bc03053086435db89e47d'.
However, there were unannotated tags: try --tags.

$> git describe --tags
2.0-216-ge27614b

let me know if I should elaborate why annotated tags

I am still getting used to Git, I will google before asking. Lol
Thanks for the suggestion!

It seems like there is some discrepancy between GitHub releases and Git repository tagging. While creating an annotated release in Git is straight forward, are you aware of how to also do a full GitHub release while annotating the Git tag (e.g. can I annotate a GitHub tag after the fact)?
Thanks!

Yes
I usually make annotated tag, and then make a release out of it on github. I think it copies your tag text (or if don't, just copy paste yourself 😃)
On July 13, 2016 4:58:31 PM EDT, "Gregory M. Kurtzer" notifications@github.com wrote:

It seems like there is some discrepancy between GitHub releases and Git
repository tagging. While creating an annotated release in Git is
straight forward, are you aware of how to also do a full GitHub release
while annotating the Git tag (e.g. can I annotate a GitHub tag after
the fact)?
Thanks!

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gmkurtzer/singularity/issues/131#issuecomment-232484602

Very cool, I will do that on the next release. Thanks!
BTW: Shortly I will be updating the 2.x branch and doing a GitHub pre-release for 2.1. YAY!

congrats! just please be consistent ;)
$> git tag
1.0
2.0
v2.1-testing

2.1-testing is indeed compliant with http://semver.org but may be you would have preferred more "conventional" -alpha0 ? ;)

Yeah, I was reading up on "standardized" nomenclature. I wonder if I can rename it? Lol

you can, but it not recommended. Note that we never tag release candidates, but only actual releases - but you can do as you wish! 😄

It is my intention to delete the testing tag once the formal release has been made. Some of this is me trying to learn the "GitHub" way of doing things.

Well, technically speaking there is no need to delete any tag, alpha release our what not... just stay uniform.
It is somewhat of a git cons, that tags are viral. Even though you remove it, I already have it, and would need to remove it manually too . So if you have intent to remove or rename it, do it ASAP before more ppl fetched it in their repos
On July 14, 2016 4:25:08 PM EDT, "Gregory M. Kurtzer" notifications@github.com wrote:

It is my intention to delete the testing tag once the formal release
has been made. Some of this is me trying to learn the "GitHub" way of
doing things.

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gmkurtzer/singularity/issues/131#issuecomment-232781625

Is it better practice to remove the v in the current prerelease, or just leave it there and be more consistent for future releaseS?

Definitely better to not edit existing tags. Just move forward with whatever standard you decide upon

Will do, thanks!

I believe I did this correctly this time. :)

authors: gmkurtzer rhc54 yarikoptic

repo: gmkurtzer/singularity


text:
module declares its path as: github.com/securego/gosec

$ go get -u github.com/gnieto/mulint
go: github.com/gnieto/mulint upgrade => v0.0.0-20180313231918-24ec3193fbeb
go: finding module for package github.com/GoASTScanner/gas
go: found github.com/GoASTScanner/gas in github.com/GoASTScanner/gas v0.0.0-20200401082031-e946c8c39989
go: github.com/gnieto/mulint imports
github.com/gnieto/mulint/mulint imports
github.com/GoASTScanner/gas: github.com/GoASTScanner/gas@v0.0.0-20200401082031-e946c8c39989: parsing go.mod:
module declares its path as: github.com/securego/gosec
but was required as: github.com/GoASTScanner/gas

Hi @jtorvald
Sorry for the late reply. I've updated the project in order to be able to install it via go get.
To be honest, this was a toy project I did some years ago and it was a little bit unmaintained. Please, let me know if you can run it now or if you find this lint useful.
Thanks!

authors: gnieto jtorvald

repo: gnieto/mulint


text:
(Feature) - #1541 etherscan on ewc

Closes #1541
Description

There were a lot of places in which we were still using the old EtherscanButton, I replaced them with the ExplorerButton from safe react components, now all the links to explorer's should be fine

Travis automatic deployment:
https://pr1544--safereact.review.gnosisdev.com/rinkeby/app

authors: Agupane gnosis-info

repo: gnosis/safe-react


text:
Add gas estimation endpoint from gateway SDK

What it solves
Resolves https://github.com/gnosis/safe-react-gateway-sdk/issues/14
How this PR fixes it
Uses new function in the gateway SDK in order to estimate safeTxGas
Bonus
It also uses the function to fetch owned safes through the client gateway instead transaction service
How to test

Check that safeTxGas estimations are still correct
Check that owned safes are shown in sidebar correctly

I tried in rinkeby and I had no issues, with safes with 2 owners and 1 owner needed. The safeTxGas estimation looked fine, I was able to execute tx with the default estimation just fine
I tried in Polygon and it worked a bit, but it seems the network is slow today so some tx didn't even trigger signatures.  I'll try that one later, but the tx I was able to execute worked just fine

Polygon is still a bit slow on how it is working, but the tx I signed the safeTxGas was estimated properly.

authors: dasanra francovenica


text:
fix: deal with nested arrays param values

What it solves
Resolves #3468
How this PR fixes it
Handles multidimensional method param values
How to test it
Open app/avax:0x2ABC32Fcf8584Aba161b33133af55cD3f94Ba288/transactions/0xb249327fea1885798f2ffca88aa31bd4e9a4d35f66aa57e58bf3cf25af4c239c and you shall see all the values well represented without the application crashing
Screenshots

@liliiaorlenko we need some Design validation in this ticket.
For method parameters that are nested arrays (like in the screenshot) can you provide a Figma mockup?
cc @liliya-soroka

Pull Request Test Coverage Report for Build 1818321905

1 of 7 (14.29%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 33.617%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/safe/components/Transactions/TxList/MethodValue.tsx
0
6
0.0%

Totals

Change from base Build 1818042425:
-0.02%

Covered Lines:
3228

Relevant Lines:
8576

💛  - Coveralls

@liliiaorlenko we need some Design validation in this ticket. For method parameters that are nested arrays (like in the screenshot) can you provide a Figma mockup? cc @liliya-soroka

https://www.figma.com/file/47wkjxMZkyEeCRbCrLJBJa/safe%232995-Tx-details?node-id=2226%3A22157
Is this design sufficient?

So I tried to reproduce it with the dummy contract I have, but it seems that is not the same type of tx. So I just took the tx that was making it fail in prod in the first place, tried it in this PR and the tx can be seen with no issues.
I think there is no way to prevent every type of value of every different type of tx that we have and make it 100% failproof, we will have to deal with these cases as they pop up.
Looks good to me
https://pr3469--safereact.review-safe.gnosisdev.com/app/avax:0x2ABC32Fcf8584Aba161b33133af55cD3f94Ba288/transactions/0xb249327fea1885798f2ffca88aa31bd4e9a4d35f66aa57e58bf3cf25af4c239c

we will have to deal with these cases as they pop up.

I briefly looked over the data types that are possible and they are all recursively catered so, famous last words, there shouldn't be an issue like this again. We can/should render each transaction in an error boundary though.

authors: DiogoSoaress coveralls francovenica iamacook liliiaorlenko


text:
rev1.7.1

last try

Travis automatic deployment:
https://pr548--safereact.review.gnosisdev.com

authors: fernandomg gnosis-info


text:
🛑 Beacon RPC is down

In 1d83255, Beacon RPC (https://rpc-gbc.gnosischain.com/eth/v1/beacon/headers) was down:

HTTP code: 503
Response time: 244 ms

Resolved: Beacon RPC is back up in e213696 after 13 minutes.

repo: gnosischain/gnosischain-uptime


text:
Make it possible to specify multiple (fallback) fonts

With URxvt you can configure your font:
URxvt.font: font1,font2

And font2 glyphs will be used as fallback if font1 doesn't provide them. This is useful for displaying icon fonts like https://github.com/stark/siji
It would be nice if xst could do this.

@novcn @arkhan Put something like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">

<fontconfig>
  <!--
  Make FantasqueSansMono Nerd Font the initial fallback font for Iosevka Medium
  -->
<match>
    <test name="family"><string>Iosevka Medium</string></test>
    <edit name="family" mode="append" binding="strong">
      <string>FantasqueSansMono Nerd Font</string>
    </edit>
  </match>

in ~/.config/fontconfig/fonts.conf
Before:
https://i.imgur.com/d0JIsFg.png
After:
https://i.imgur.com/ogYvoJg.png

note: we could do this with https://st.suckless.org/patches/font2/, then split on ',' for xresource loading

update?

@RaafatTurki PRs welcome ;)

Not sure how font2 loads the fonts, but I'll give it a look and see if it can be done by XResource easily.

It took longer than what I thought it would, but to be honest, it works just fine. The way I implemented it actually uses the font2's fonts of the config.h as well and add the ones from XResources with it.
I'll make a PR if @gnotclub is willing to accept it.

thanks in advance!

authors: BeyondMagic RaafatTurki actionless mustaqimM neeasade novcn

repo: gnotclub/xst


text:
Parse URLs as Strings

Does not parse strings that are urls such as the following:
website: https://www.google.com/

please try:
website: "https://www.google.com/"

authors: jamesguyer xujinzheng

repo: go-akka/configuration


text:
[IMPORTANT] Allow CodePush to stacks without autoscaling groups

Code deployment ATM cannot be done to a single EC2 instance with no AutoScaling group.
Creating an Autoscaling group costs nothing, but it still could be an inconvenience.
I should allow for deploys with no autoscaling groups.

Works now.

repo: go-furnace/go-furnace


text:
Unable to pass real IP to Gitea using Caddy

Description
I seem completely unable to pass an incoming user's real IP (X-Real-IP or X-Forwarded-For) to Gitea when using Caddy as a reverse proxy.
In both the failed login and access logs, Gitea is showing Caddy's IP address.
Caddy version - 2.6.2
My app.ini file contains:
REVERSE_PROXY_LIMIT = 1 #(tried 2, too)
REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.1/8, 10.200.20.100/24

Under REVERSE_PROXY_TRUSTED_PROXIES I have tried:

Just *
10.200.20.0/24
10.200.20.100/32

CaddyFile contains:
https://git.mydomain.com {
  reverse_proxy 10.200.20.125:3000 {
    header_up X-Real-IP {remote_host}
    header_up X-Forwarded-For {remote_host}
  }
}

Other applications behind the same Caddy installation do not have this problem and are correctly picking up both X-Real-IP or X-Forwarded-For.
Using the PHP snippet below (with completely vanilla NGINX+PHP), I was able to double check that Caddy is in fact passing the correct headers:
<?php
echo $_SERVER['HTTP_X_FORWARDED_FOR'];
echo "<br>";
echo $_SERVER['HTTP_X_REAL_IP'];
?>

I initially attempted the above with CloudFlare in front of Caddy with no luck and posted my issue on the forum - here.
I'm now attempting it without CloudFlare in front of Caddy.
Gitea Version
1.18.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian 11
How are you running Gitea?
Binary + systemd
Database
MySQL

Oh @zeripath , I'm an idiot.
I had them under [server] - I can't believe that's what it was 🤦♂
Thank you!

@hwcltjn not at all. Sometimes we all need a rubber duck ❤

authors: hwcltjn techknowlogick

repo: go-gitea/gitea


text:
Upgrade script should inform users that gitea service has to be running in order to upgrade it

Description
I'm running a non-docker install on a Debian VPS, and was upgrading from 1.18.3 to 1.19.0, using the upgrade script found here: https://github.com/go-gitea/gitea/blob/main/contrib/upgrade.sh
Following the backup steps, I stopped the gitea service with #systemctl stop gitea, did the manual backups, and then ran the upgrade script # ./upgrade.sh.
This upgrade script expects the service to be running (since it runs the flush queues command before making a backup), so when it encounters an Internal Server Error, it should suggest you have the service running before executing the upgrade script.
Gitea Version
1.18.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian
How are you running Gitea?
Using a prebuilt binary fetched with the Upgrade script. Original install came from Linode Marketplace (which had something like 1.16.x)
Database
PostgreSQL

Closed by #23949
But, actually, the script should not require Gitea is running, it should just ignore the "flush queue" failure if there is no running instance.

You linked this issue and not the PR, btw!

authors: ijustlovemath wxiaoguang


text:
Support a new file type: justfile

Feature Description
It would be great if Gitea would support justfile

File type detection
Syntax highlight

Screenshots

We use go-enery https://github.com/go-enry/go-enry for language detection. You could request it be added there and then we can support it here.
We also use chroma for syntax highlighting https://github.com/alecthomas/chroma support may need to be added there.

Get it, I will open issues to the upstream, thanks!

Issues filed:)

We are facing multiple issues with this Library. It is giving so much problem day by day,
Previously filed issue was also not acknowledged and resolved by the upstream author.
//cc @silverwind  @lunny  @wxiaoguang

@puni9869 Which library? I've found that both of them are pretty reliable, hence their use by us.

We are facing multiple issues with this Library. It is giving so much problem day by day,
Previously filed issue was also not acknowledged and resolved by the upstream author.
//cc @silverwind  @lunny  @wxiaoguang

chrome go lib syntax highlighter.

I have no issues with chroma, author is responsive and while I wish there was more activity, it's still the best syntax highlighter for golang as far as I'm aware. If you want something done, start contributing.

Okay I will explore more about chrome lib. No worries, I am glad to know we are sponsoring chrome lib. :)

go-enry 2.8.5 ships linguist 7.24.0, which contains the patch that adds the support for justfile, so the next release of Gitea will support justfile!
Thanks to the folks who made this possible.
Close this issue as complete.

authors: SteveLauC puni9869 silverwind techknowlogick


text:
After Update to 1.22.0 LDAP Login is not working anymore

Description
Hi,
I've upgrade to 1.22.0  and after the update LDAP login is no longer possible.
I see tls handshake failures in the logfile:
2024/06/03 11:18:01 ...dap/source_search.go:424:SearchEntries() [E] LDAP Connect error, our.ldap.server:LDAP Result Code 200 "Network Error": remote error: tls: handshake failure
2024/06/03 11:18:01 .../ldap/source_sync.go:55:Sync() [E] SyncExternalUsers LDAP source failure [ourldapserver], skipped
Gitea Version
1.22.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.39.3
Operating System
RHEL 8.9
How are you running Gitea?
running gitea from downloads: gitea-1.22.0-linux-amd64
Database
PostgreSQL

Are you using a self-signed certificate, and which LDAP server are you using?

Could be a TLS cipher issue. Check if your LDAP server supports TLS 1.2 or higher with tools like https://github.com/drwetter/testssl.sh. golang since  v1.22 requires TLS 1.2 or higher by default.

Same here. Self-signed certificate with "skip TLS verification" selected.
Used testssl.sh to check protocols:
 Testing protocols via sockets except NPN+ALPN

 SSLv2      not offered (OK)
 SSLv3      not offered (OK)
 TLS 1      offered (deprecated)
 TLS 1.1    offered (deprecated)
 TLS 1.2    offered (OK)
 TLS 1.3    not offered and downgraded to a weaker protocol
 NPN/SPDY   not offered
 ALPN/HTTP2 not offered

 Testing cipher categories

 NULL ciphers (no encryption)                      not offered (OK)
 Anonymous NULL Ciphers (no authentication)        not offered (OK)
 Export ciphers (w/o ADH+NULL)                     not offered (OK)
 LOW: 64 Bit + DES, RC[2,4], MD5 (w/o export)      not offered (OK)
 Triple DES Ciphers / IDEA                         not offered
 Obsoleted CBC ciphers (AES, ARIA etc.)            offered
 Strong encryption (AEAD ciphers) with no FS       offered (OK)
 Forward Secrecy strong encryption (AEAD ciphers)  not offered

 Testing server's cipher preferences

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.   Encryption  Bits     Cipher Suite Name (IANA/RFC)
-----------------------------------------------------------------------------------------------------------------------------
[..]

TLSv1.2 (no server order, thus listed by strength)
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      TLS_RSA_WITH_AES_256_GCM_SHA384
 x3d     AES256-SHA256                     RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA256
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      TLS_RSA_WITH_AES_128_GCM_SHA256
 x3c     AES128-SHA256                     RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA256
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA

Same here. I'm using an OpenLDAP proxy. TLS1.2 is supported:
 Testing protocols via sockets except NPN+ALPN

 SSLv2      not offered (OK)
 SSLv3      not offered (OK)
 TLS 1      offered (deprecated)
 TLS 1.1    offered (deprecated)
 TLS 1.2    offered (OK)
 TLS 1.3    not offered and downgraded to a weaker protocol
 NPN/SPDY   not offered
 ALPN/HTTP2 not offered

 Testing cipher categories

 NULL ciphers (no encryption)                      not offered (OK)
 Anonymous NULL Ciphers (no authentication)        not offered (OK)
 Export ciphers (w/o ADH+NULL)                     not offered (OK)
 LOW: 64 Bit + DES, RC[2,4], MD5 (w/o export)      not offered (OK)
 Triple DES Ciphers / IDEA                         offered
 Obsoleted CBC ciphers (AES, ARIA etc.)            offered
 Strong encryption (AEAD ciphers) with no FS       offered (OK)
 Forward Secrecy strong encryption (AEAD ciphers)  not offered

 Testing server's cipher preferences
 TLSv1.2 (no server order, thus listed by strength)
 x9d     AES256-GCM-SHA384                 RSA        AESGCM      256      TLS_RSA_WITH_AES_256_GCM_SHA384
 x3d     AES256-SHA256                     RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA256
 x35     AES256-SHA                        RSA        AES         256      TLS_RSA_WITH_AES_256_CBC_SHA
 x84     CAMELLIA256-SHA                   RSA        Camellia    256      TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
 x9c     AES128-GCM-SHA256                 RSA        AESGCM      128      TLS_RSA_WITH_AES_128_GCM_SHA256
 x3c     AES128-SHA256                     RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA256
 x2f     AES128-SHA                        RSA        AES         128      TLS_RSA_WITH_AES_128_CBC_SHA
 x96     SEED-SHA                          RSA        SEED        128      TLS_RSA_WITH_SEED_CBC_SHA
 x41     CAMELLIA128-SHA                   RSA        Camellia    128      TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
 x07     IDEA-CBC-SHA                      RSA        IDEA        128      TLS_RSA_WITH_IDEA_CBC_SHA
 x0a     DES-CBC3-SHA                      RSA        3DES        168      TLS_RSA_WITH_3DES_EDE_CBC_SHA

Actually it's likely not TLS-version related as per https://tip.golang.org/doc/go1.22#minor_library_changes:

By default, the minimum version offered by crypto/tls servers is now TLS 1.2 if not specified with config.MinimumVersion, matching the behavior of crypto/tls clients. This change can be reverted with the tls10server=1 GODEBUG setting.

So the TLS client has not changed it's requirement in 1.22, only the server has.

The situation seems clear to me:

By default, cipher suites without ECDHE support are no longer offered by either clients or servers during pre-TLS 1.3 handshakes. This change can be reverted with the tlsrsakex=1 GODEBUG setting.

https://tip.golang.org/doc/go1.22#minor_library_changes
https://github.com/golang/go/issues/63413

Same issue.  Workaround for me was to disable encryption and change the port from 636 to 389 or from 3289 to 3268.  I use Global Directory LDAP 3268 because it's faster, but I tested with port 389 and it works as well.

@adamoutler
Could you test it again with port 636, enabled encryption and GODEBUG="tlsrsakex=1"
as mentioned in: https://github.com/go-gitea/gitea/issues/31228#issuecomment-2147709875
?

@adamoutler Could you test it again with port 636, enabled encryption and GODEBUG="tlsrsakex=1"  as mentioned in: #31228 (comment) ?

I'm sorry, but I'm using a docker container setup and I'd need to adjust code to do this.  I assume it will be fixed in a month or two.

Ok, I'm closing this since it's working as intended and I'll be closing and pinning this for a bit.
People affected should look into upgrading their LDAP server to support modern ciphers and if that's not possible you can workaround preferably with GODEBUG="tlsrsakex=1" or worse, by switching to unencrypted. That flag will surely go away in a future golang version, so it won't last forever.

Working OpenLDAP/slapd config:
TLSCipherSuite          HIGH:MEDIUM:-SSLv2:-SSLv3
TLSProtocolMin          3.1
TLSECName               secp521r1

To enable ECDHE ciphers TLSECName is required.

Just upgraded and hit this.
I don't understand why this isn't a listed as breaking change because it literally fails all logins? No fallback as far as I can see (or rememeber).
Currently running a downloaded binary, not docker.
Have tried adding this to /etc/gitea/app.ini
GODEBUG="tlsrsakex=1"
Still fails.
Tried to add it to the systemd unit file (are the quotes required?) eg
ExecStart=/usr/local/bin/gitea web --config /etc/gitea/app.ini
Restart=always
Environment=USER=git HOME=/home/git GITEA_WORK_DIR=/var/lib/gitea GODEBUG="tlsrsakex=1"

Still fails.
Then tried run gitea from the CLI to try and modify LDAP in any way shape form but I get the dreaded:
Expect user 'git' but current user is: myuser
So can't go back, can't go forwards and can't update my LDAP server for another couple of months as it hinges on other software too. Ironically gitea is on a server that COULD run a newer verion of LDAP but I don't want to do that as it breaks all my backend authent, and I can't modify the LDAP settings in any event........
Completely and utterly stuck and no idea what to do :-(
Any advice on this appreciated at least to get it running for now.

Well after a huge amount of wrangling I got it to work.
First, I could not get this to work and would very much like to know how to get it to work on a binary only install?
GODEBUG="tlsrsakex=1"
Next, and this should be better documented, is how to actively modify gitea settings via the CLI. I stumbled over this while looking for something else and modified it for my own use.
On a *buntu box it required this to get around the Expect user 'git'  issue:
sudo -H -u git bash -c '/usr/local/bin/gitea admin auth update-ldap  --id 1 --skip-tls-verify --security-protocol starttls -c /etc/gitea/app.ini'
I had to read the code here to find the different security protocols as that isn't documented either
unencrypted | starttls | ldaps
Change your comand/directory to suit.
Found those here: admin_auth_ldap_test.go
Would be nice to be able to:
a) query existing settings
b) have expected 'fixed' variables in the docs
Next was to check what Ciphers were loaded.
nmap --script ssl-enum-ciphers -p636 localhost
PORT    STATE SERVICE
636/tcp open  ldapssl
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_RSA_WITH_AES_128_CBC_SHA - strong
|       TLS_RSA_WITH_AES_128_CBC_SHA256 - strong
|       TLS_RSA_WITH_AES_128_GCM_SHA256 - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA256 - strong
|       TLS_RSA_WITH_AES_256_GCM_SHA384 - strong
|       TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|       TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|     compressors:
|       NULL
|_  least strength: strong

Next was to check the existing non RSA CipherSuites (yes messy but it works for me). I expected to be out of luck:
openssl ciphers -v |grep v1.2 |grep -v RSA |grep ECDH
ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=ECDSA Enc=AESGCM(256) Mac=AEAD
ECDHE-ECDSA-AES256-SHA384 TLSv1.2 Kx=ECDH     Au=ECDSA Enc=AES(256)  Mac=SHA384
ECDH-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AESGCM(256) Mac=AEAD
ECDH-ECDSA-AES256-SHA384 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AES(256)  Mac=SHA384
ECDHE-ECDSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=ECDSA Enc=AESGCM(128) Mac=AEAD
ECDHE-ECDSA-AES128-SHA256 TLSv1.2 Kx=ECDH     Au=ECDSA Enc=AES(128)  Mac=SHA256
ECDH-ECDSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AESGCM(128) Mac=AEAD
ECDH-ECDSA-AES128-SHA256 TLSv1.2 Kx=ECDH/ECDSA Au=ECDH Enc=AES(128)  Mac=SHA256

Hmmm. A chance?
Next on the LDAP server I added these additional Cipher suites to etc/openldap/slapd.conf to test
ECDH-ECDSA-AES128-GCM-SHA256:ECDH-ECDSA-AES128-SHA256:ECDH-ECDSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-SHA384
Apparently to use ECDH you need TLSECName as well. So:
TLSCipherSuite ECDH-ECDSA-AES128-GCM-SHA256:ECDH-ECDSA-AES128-SHA256:ECDH-ECDSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:HIGH@STRENGTH:!SSLv2:!ADH:!aNULL:!MD5:!RC4
TLSECName               secp521r1

Restart ldap server and test. Oh.
PORT    STATE SERVICE
636/tcp open  ldapssl
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 - strong
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 - strong
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 - strong
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 - strong
|       TLS_RSA_WITH_AES_128_CBC_SHA - strong
|       TLS_RSA_WITH_AES_128_CBC_SHA256 - strong
|       TLS_RSA_WITH_AES_128_GCM_SHA256 - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA - strong
|       TLS_RSA_WITH_AES_256_CBC_SHA256 - strong
|       TLS_RSA_WITH_AES_256_GCM_SHA384 - strong
|       TLS_RSA_WITH_CAMELLIA_128_CBC_SHA - strong
|       TLS_RSA_WITH_CAMELLIA_256_CBC_SHA - strong
|     compressors:
|       NULL
|_  least strength: strong

I was concerned that the TLS_ECDHE still had RSA but I went to the login page and it worked immediately!
So the answer is it will still work, but needs the correct setup.
Hope that helps someone.

authors: JoelKle adamoutler reetp silverwind swiedernix techknowlogick vworldat xoxys


text:
Preview

Gitea version (or commit ref): 1.9.4
Git version: 2.20.1
Operating system: Raspbian Buster + pre-release kernel (Raspberry Pi 4)
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
The preview tab of the text editor doesn't load anything.
Screenshots

It appears to works on try.gitea.io
What file format are you trying to preview? What browser are you using?
What's your app.ini? Have you switched off the API?

I know it works on try.gitea.io. I'm just trying to preview the changes of the README. I tired with Tor browser first, but I also checked with the default profile of Firefox. In my app.ini I just added one rule: MAX_CREATION_LIMIT = 0. I didn't switch off the API, at least knowingly: doing grep 'SWAGGER' app.ini doesn't return anything so I guess the API is enabled.

Ok. Could you check what the browser is sending when you click preview?
It should send a POST message to /api/v1/repos/:username/:reponame/markdown
Is it sending that POST to the correct place?

Emh, I'm just a teen I don't know that stuff... could you provide a very brief explanation about how to verify that? However, I'm not sure anymore about the state of the API, because when I try to load try.gitea.io/api/swagger my browser loads up a webpage, but if I try to open the "API page" of my gitea istance, my browser doesn't load anything. Does it matter?

It sounds like you've misconfigured Gitea so I'd double check that you have the configuration correct in your app.ini

Sorry, but my app.ini seems to be fine (https://paste.debian.net/1106435/).
Is there another simple way to check if the API is working or not? Like another element in the page that wouldn't work without the API turned on?

What is the URL you are using to browse to Gitea?

I was using it locally, but I've just finished setting up a temporary onion service in case you want to test (idk if it can cause other problems tho) : http://f6awmtbw572jcr2jaekqqnteuirdqoag64i6dnewph5y63xpsdmfabqd.onion/

Well the tor won't work unless you tell Gitea that's its ROOT_URL is that onion address.
Similarly by locally, do you mean from a browser on the same machine as the server i.e. your browser was browsing to localhost:3000 or were you doing it across the network because again that would explain why the preview failed.
In Firefox there are likely some developer tools that you can use to check what requests your browser webpages are making. That was what I was meaning by checking what the preview page was POSTing, as I suspect that although the preview page is making a POST it is not sending it to correct place because you have incorrectly configured Gitea to say what it's ROOT_URL is.
If your server and client machines are not the same, a ROOT_URL of http://localhost:3000 is incorrect. It is certainly incorrect if you're trying to access Gitea over Tor.

Sorry for the delay and thanks for the clear explanation. As you said, the problem was the ROOT_URL, I fixed it and now it works. Thanks for the help!

authors: jdkdfjuwicvh zeripath


text:
Parsing error when using asciidoctor

Gitea version (or commit ref): 1.9.4
Git version: 2.23.0
Operating system: openSUSE Tumbleweed 20191012
Database (use [x]):
asciidoctor version: 2.0.10

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant (the test instance doesn't support AsciiDoc)

Log gist: (couldn't find anything in logs pertaining to external renderers)

Description
When using asciidoctor as external renderer for AsciiDoc files, a superfluous string appears in the output at the beginning of the file:
lang="en">
This seems to be part of asciidoctor's html output, for some reason gitea doesn't filter it out.
The rest of the AsciiDoc file is displayed correctly in gitea's web interface.
I'm using the default asciidoctor config described here:
https://docs.gitea.io/en-us/external-renderers/
Screenshots
https://i.imgur.com/PBewpAz.png

This is a valid issue & shouldn't be closed

There is a new sectioon on https://docs.gitea.io/en-us/external-renderers/ about sanitizer maybe help you.

AFAICT, the purpose of that is to avoid certain attributes from getting stripped by Gitea. To solve this issue, there should be a way to do the exact opposite: tell Gitea to strip certain attributes. I tried with the section below, but it doesn't help:
[markup.sanitizer]
ELEMENT = html
ALLOW_ATTR =
REGEXP =

@lunny this can be closed: it's a duplicate of #8676, which is fixed in v1.11.0

authors: anthonyvdotbe clavinet lunny


text:
Fix issue due date always being UTC

Fixes: https://github.com/go-gitea/gitea/issues/11686
Creates a local 00:00 date and toISOString will convert it to UTC. So essentially the exact due time is now always 00:00 in the user's current timezone instead of previously 00:00 UTC.

Unsure if this is correct approach. Due date does not present time picker so no time should be saved in database.
Most likely we should replicate behavior from milestone, which sets due date to 23:59 in server's local timezone.

Sounds good from a consitency perspective to have timezone-independent dates on the server, but the display issue on the client (which converts from UTC to local) will remain in that case.

authors: CirnoT silverwind


text:
Add Vue linting

Turns out the .vue files were not linted at all, so I added that as well as re-indented the file to 2-space and fixed all reasonable issues that came up except one case of a unintended side effect for which I have no idea how to fix it, so the rule was disabled.

🚀

authors: lafriks silverwind


text:
backport of PR #1257 for release/v1.1: rewrite pre-commit, post-commit and options hooks

See #1257

I kept the version name v26 to avoid conflicts with future merges, even though it breaks the consistency of numbering the migrations. Any thoughts on this -- shall I rename it back to v23?

keep v26 or change it to v23 will both make it impossible to upgrade from v1.1.1 to v1.2.

Ok, so no migration for 1.1. I removed the questionable parts.

LGTM

@bkcsoft let's move the changelog thing after v1.2

authors: lunny philfry strk


text:
Change button text for commenting and closing an issue at the same time (#23135)

Backport #23135
Close  #10468
Without SimpleMDE/EasyMDE, using Simple Textarea, the button text could be changed when content changes.
After introducing SimpleMDE/EasyMDE, there is no code  for updating the button text.

Please wait for https://github.com/go-gitea/gitea/pull/23168 together, it fixes a regression bug of undefined-checking.
🙏

authors: wxiaoguang yardenshoham


text:
Include public repos in doer's dashboard for issue search

It will fix #28268 .

:warning: BREAKING :warning:
But need to give up some features:

However, such abandonment may fix #28055 .
Backgroud
When the user switches the dashboard context to an org, it means they want to search issues in the repos that belong to the org. However, when they switch to themselves, it means all repos they can access because they may have created an issue in a public repo that they don't own.

It's a confusing design. Think about this: What does "In your repositories" mean when the user switches to an org? Repos belong to the user or the org?
Whatever, it has been broken by #26012 and its following PRs. After the PR, it searches for issues in repos that the dashboard context user owns or has been explicitly granted access to, so it causes #28268.
How to fix it
It's not really difficult to fix it. Just extend the repo scope to search issues when the dashboard context user is the doer. Since the user may create issues or be mentioned in any public repo, we can just set AllPublic to true, which is already supported by indexers. The DB condition will also support it in this PR.
But the real difficulty is how to count the search results grouped by repos. It's something like "search issues with this keyword and those filters, and return the total number and the top results. Then, group all of them by repo and return the counts of each group."

Before #26012, it was being done in the DB, but it caused the results to be incomplete (see the description of #26012).
And to keep this, #26012 implement it in an inefficient way, just count the issues by repo one by one, so it cannot work when AllPublic is true because it's almost impossible to do this for all public repos.
https://github.com/go-gitea/gitea/blob/1bfcdeef4cca0f5509476358e5931c13d37ed1ca/modules/indexer/issues/indexer.go#L318-L338
Give up unnecessary features
We may can resovle TODO: use "group by" of the indexer engines to implement it, I'm sure it can be done with Elasticsearch, but IIRC, Bleve and Meilisearch don't support "group by".
And the real question is, does it worth it? Why should we need to know the counts grouped by repos?
Let me show you my search dashboard on gitea.com.

I never think the long repo list helps anything.
And if we agree to abandon it, things will be much easier. That is this PR.
TODO
I know it's important to filter by repos when searching issues. However, it shouldn't be the way we have it now. It could be implemented like this.

The indexers support it well now, but it requires some frontend work, which I'm not good at. So, I think someone could help do that in another PR and merge this one to fix the bug first.
Or please block this PR and help to complete it.
Finally, "Switch dashboard context" is also a design that needs improvement. In my opinion, it can be accomplished by adding filtering conditions instead of "switching".

I was unable to create a backport for 1.21. @wolfogre, please send one manually. :tea:
go run ./contrib/backport 28304
...  // fix git conflicts if any
go run ./contrib/backport --continue

if you use it less like an "issue search" and more like an "issue dashboard" the repo filter IS quite usefull ...
some could argue that the UX was bad ... yes. I'll open a new issue to bring "repo filters" back .. -> #31578

authors: 6543 GiteaBot wolfogre


text:
Register themes/gitea submodule

I think it helps, will leave decision to others

Maybe subtree?

Why subtree ? Submodule only drops a reference to the SHA and the repository public URL in the main repository. I don't know what subtree does.

I was just thinking... I would be a kind of vendoring, a PR would need to be open every time one want to update the theme. Maybe submodules are better if we want it automatically updated. Let's @tboerger decide this.

Simply NO! This won't work with an automated workflow. I have already created PRs to add a make task and it's also documented. So here a BIG -1 from my side.

On Thu, Nov 10, 2016 at 03:23:08AM -0800, Thomas Boerger wrote:

Simply NO! This won't work with an automated workflow. I have already created PRs to add a make task and it's also documented. So here a BIG -1 from my side.

I suspected your veto.
Anyway "won't work with automated workflow" is not true...

It won't work unless you allow the CI to push changes, and this is nothing I would even consider if I compare it with the current setup.

@tboerger the current setup doesn't push any changes, just adds a 'git' command and clones a repository. Both thing that with the setup in the PR are not needed

A No from me as well.
Submodules need to be updated to update the theme, the current pipeline that was setup by @tboerger is way superior. We really don't need submodules.
I suggest to add a Makefile and in make all it pulls everything to get one started locally.

Ok then. Makefile was added by @tboerger, waiting for lgtm in  #3

authors: andreynering metalmatze strk tboerger

repo: go-gitea/website


text:
Custom Naming Strategy - not unique table names

Your Question

When I implement custom Namer interface for NamingStrategy
type Namer interface {
  TableName(table string) string
  SchemaName(table string) string
  ColumnName(table, column string) string
  JoinTableName(table string) string
  RelationshipFKName(Relationship) string
  CheckerName(table, column string) string
  IndexName(table, column string) string
}

table parmater is a type name without the package prefix (e.g. User instead of users.User), so how should I distinguish one table from another?
Also when trying to override table name manually during the query:
db.Table("test").First(&User{})

The table param is User and not the test. Is it an expected behaviour?
The document you expected this should be explained

Expected answer

The table param is User and not the test. Is it an expected behaviour?

No, it should be test

table parmater is a type name without the package prefix (e.g. User instead of users.User), so how should I distinguish one table from another?

We don't care which package is it from, if package distinction is important in your case, perhaps you want to refer to https://gorm.io/docs/conventions.html#TableName

No, it should be test

Should I open a bug report then?

repo: go-gorm/gorm


text:
OpenGauss DB support

Hi,at present, our projects using gorm need to use Huawei OpenGauss db, but there is no official driver supporting OpenGauss at present, is there any chance to support it? Looking forward to your reply

Sorry, I currently don’t have the capacity to implement support for OpenGauss. However, I’d be happy if the community could take on this effort. The implementation can either be maintained under the GORM organization or independently. We will add relevant links to recommend it.

@XujiaFu-0609 I believe OpenGauss should be basically compatible with PostgreSQL, have you ever tried to set it up as PG? Did you encounter any errors or failures?

authors: XujiaFu-0609 jinzhu southwolf


text:
wasm: fix leb128 decoding

the original implementation missing some checks:

overflow check
encoded integer must not exceed ceil(N/7) bytes.
ReadVarint32 is directly truncated from int64

travis-ci seems unstable.

Codecov Report

Merging #155 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #155      +/-   ##
==========================================
+ Coverage   69.51%   69.53%   +0.02%
==========================================
  Files          43       43
  Lines        4976     4980       +4
==========================================
+ Hits         3459     3463       +4
  Misses       1227     1227
  Partials      290      290

Impacted Files
Coverage Δ

wasm/leb128/read.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io laizy

repo: go-interpreter/wagon


text:
GEOMETRY error when trying Tegola with a geopackage

I get an error saying "Error: could not register providers: unsupported geometry type: GEOMETRY" when trying to tegola_windows_amd64_cgo version 0.8.1 on a geopackage file. The gpkg file contains only one table that lists as a LineString25D when opened in QGis (works perfectly) geometry column is geom, srid is 3857.
This is my config-file:
[webserver] port = ":8082"

[cache] type = "file" basepath = "C:\Tegola\cache"

[[providers]] name = "gsd" type = "gpkg" filepath = "C:\Tegola\data\gsd.gpkg"

    [[providers.layers]] name = "gsdvol" tablename = "vol"

[[maps]] name = "roads"

    [[maps.layers]] provider_layer = "gsd.gsdvol" min_zoom = 11 max_zoom = 19

Is this a bug or am I just configuring it wrong?

@kartogishenko anyway I can get access to the geopackage to recreate it? I would suspect what's going on here is that the GEOMETRY type is too generic and tegola wants to know if it's a polygon, line string, point, etc.

Sure, here it comes. Doubblechecked there is only one kind of geometry in the fil.
geopackage.zip

@kartogishenko i got it working. A few things:

tegola does not have support for the generic "geometry" type. This is because MVT does not have support for it (also called a geometry collection). A layer must have a single geometry type, not a heterogenous mixture. In the case of this geopackage, the vol layer has a type of LINESTRING
The geopackage appears to have a non standard structure (missing fid) so the auto generated SQL from tegola does not work out of the box. I was able to export your geopackage using QGIS, setting the geometry type to LINESTRING and everything works fine (screen shot below). I have also attached the new geopackage for your review.
Where did you obtain this geopackage file? I'm interested in knowing what's creating this structure in case it shows up again.
This issue also brings to attention that tegola needs to support the geometry_type override for geopackage like we do for PostGIS. This is a different issue.

New Geopackage: gsd-2.gpkg.zip

For convenience the URL in the screen shot is: http://localhost:8082/#11.64/55.6392/13.7449

Hi, thank you for looking in to it. The Geopackage was created using FME Desktop 2018.1 and the software might have som issues when exporting to geopackage, according to its support forum. When comparing your rework of my geopackage with the original one I notice that mine has the geometrytype LineString25D and yours has LineString. This I cannot correct in FME, unfortunately. I do get it to work using the same method as you did when creating the geopackage from QGis so I just have to use that method for now. Thank you!

@kartogishenko I have not used FME myself so I don't have any insight into some of the data conversion nuances.

When comparing your rework of my geopackage with the original one I notice that mine has the geometrytype LineString25D and yours has LineString.

This sounds like a bug in FME as LineString25D is not a valid Geometry Type according to the Geopackage spec. Maybe let them know?
Glad you have a work around. Please close the issue unless you have any other questions.

authors: ARolek kartogishenko

repo: go-spatial/tegola


text:
Drop recommendation of gopkg.in.

See https://github.com/go-kit/kit/issues/197 for background.
Some consumers of this package are reluctant to use gopkg.in or other third-party import proxies. With the trend toward vendoring in the Go community perhaps all that is needed is good release tags in the repo and let main applications vendor the release they want.

This package no longer recommends use of gopkg.in as of v1.5.0.

repo: go-stack/stack


text:
add option to use opentracing

https://github.com/go-openapi/runtime/releases/tag/v0.19.26
has added support for OpenTracing (I added it)
and now I'm trying to add the support for the generated client.
I got a bit stuck - not sure if I added the option in the right places.

@zeitlinger we don't need to change the generated client. You can already inject a configured runtime client with the generated client.

yes, that actually works :smile:

authors: fredbi zeitlinger

repo: go-swagger/go-swagger