text:
FS: Move command doesn't work

https://forums.ghielectronics.com/t/directory-move-sourcedirectory-destinationdirectory/21840/3

Works fine, users have to point out new destination folder, same behavior on window OS.

repo: ghi-electronics/TinyCLR-Ports


text:
Please add i686 iso with Openbox

Please add a community build for i686 and Raspberry with a minimal GUI like Openbox for older hardware

Anything i686 is very unlikely to happen. I do see the benefit of something like this and like to tinker with older hardware myself. In fact, I voted against GhostBSD dropping the i386 platform when that issue was discussed within the team. But there are valid reasons that lead to the opposite stance and I'm standing by the team decision: GhostBSD focuses more than ever on the incredibly useful features that ZFS provides (and the general consensus is: Don't uses ZFS on 32-bit platforms). Other than that, modern GhostBSD is built from TrueOS and the latter has dropped i386 support long ago when it even was a Qt-based desktop spin of FreeBSD under the name of PC-BSD. There literally isn't any support for i386 in the whole TrueOS infrastructure.
For the Raspberry Pi 3 and 4 there might be hope as arm64 (a.k.a aarch64) is a platform that some of the TrueOS devs seem to have interest in. So GhostBSD on newer Raspberrys might eventually happen.
I've been on hiatus for a while now and thus don't know the recent decisions. But there have been ideas of continuing a different spin of GhostBSD not based on TrueOS but on vanilla FreeBSD. That could run on i386 platforms (but would of course not feature things like the OpenRC init system that's part of TrueOS - at least until FreeBSD makes a final decision on including it). Also it would be entirely unsupported as we don't have enough people running it seriously on that platform to even test it properly. The problem here is manpower: Somebody would have to step forward to do it. So if somebody reads this and thinks it's a good idea, go for it! Things like this are a great chance to learn things, BSD people in general (and the GhostBSD developers specifically) are nice and open - as time permits of course.

source: gharchive/issue

authors: jalfonsi kraileth

repo: ghostbsd/ghostbsd-build

license_type: permissive

license_source: github-api


text:
Failed when I try to test on Dart console app

Hi,
As name stated I try to create a simple Dart Console app but it fails. Keep asking me to import dart.ui.
NtmsRsa is simple class in separate dart file and put some dummy text in both public and private key.
import 'package:simple_rsa/simple_rsa.dart';
import 'ntms_rsa.dart';
import 'dart:ui';

main(List<String> arguments) async {
  NtmsRsa _ntmsRsa = new NtmsRsa();

  String plainText = 'something';
  String encryptedText = await encryptString(plainText, _ntmsRsa.PUBLIC_KEY);
  String decryptedText = await decryptString(encryptedText, _ntmsRsa.PRIVATE_KEY);

// Test
  print(plainText);
  print(encryptedText);
  print(decryptedText);
}

Hi,
As name stated I try to create a simple Dart Console app but it fails. Keep asking me to import dart.ui.
NtmsRsa is simple class in separate dart file and put some dummy text in both public and private key.
import 'package:simple_rsa/simple_rsa.dart';
import 'ntms_rsa.dart';
import 'dart:ui';

main(List<String> arguments) async {
  NtmsRsa _ntmsRsa = new NtmsRsa();

  String plainText = 'something';
  String encryptedText = await encryptString(plainText, _ntmsRsa.PUBLIC_KEY);
  String decryptedText = await decryptString(encryptedText, _ntmsRsa.PRIVATE_KEY);

// Test
  print(plainText);
  print(encryptedText);
  print(decryptedText);
}

I dont't understand, you using the package in a Flutter project or not? thanks

yes using in flutter, but before that I try to test in dart console app

it seems the plugin only works for flutter.

license: MIT


text:
Allow empty annotation

This allows us to create our clusters without setting this and just use
the defaults

Part of giantswarm/roadmap#1293

source: gharchive/pull-request

repo: giantswarm/capg-firewall-rule-operator


text:
Use apps/v1 for deployment

Needed for chart-operator e2e in https://github.com/giantswarm/chart-operator/pull/340.

Going with a ping.

repo: giantswarm/cnr-server


text:
Error

Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"setenv: invalid argument\"": unknown

This repository is going to be archived as we don't maintain it anymore. We are now doing etcd backups using https://github.com/giantswarm/etcd-backup-operator. Feel free to open an issue there or fork this repository.

authors: debojitkakoti kopiczko

repo: giantswarm/etcd-backup


text:
Use configured backoff time in EnsureTillerInstalled

Towards https://github.com/giantswarm/giantswarm/issues/8190
We will configure the max wait to 30 secs instead of 2 mins in app-operator. But I couple of the retries missed this setting.

why was this hardcoded before though

The setting was added a lot later. 😄 Anyway all this shite goes away with Helm 3.

repo: giantswarm/helmclient


text:
Abstract managementcluster (refactoring)

towards https://github.com/giantswarm/roadmap/issues/2967
In order to add support for capz, we refactor the operator to be more abstract.
Checklist

[x] Update changelog in CHANGELOG.md.

Tested on golem with old version => additionalTags created ✅

repo: giantswarm/object-storage-operator


text:
Azure Release v19.1.0

ℹ Team Phoenix is drafting Azure v19.1.0 with Kubernetes v1.24 support.
Target release date: 2023-06-01.
Release PR: ...
Scope

[ ] latest observability bundle
[ ] kyverno in 'warning PSS' mode

Pre-Release

[ ] Create release ticket on Releases board
[ ] Make an announcement on #sig-product that team is doing a release. Include a link to the ticket from the release board.
[ ] Make sure release was tested by creating new cluster, upgrading from older version and with HelloWorld app.
[ ] Aggregate release notes from all changed components and add to README.md in the release directory.
[ ] Send draft release announcement to #sig-product for review ASAP.
[ ] Verify documentation is up to date.

Releasing

[ ] Create release PR
Instructions

[ ] Define new release in release.yaml file.
[ ] Activate new release by setting state to active.
[ ] Deactivate old release if it's within same major version (state: deprecated). Verify with PO if you have doubts.
[ ] Check versions of all components included. They shouldn't be lower than those in the previous release unless there was a rollback.

Example PR

[ ] Release relevant operators.

[ ] Tag release branch.
[ ] Bump operator version in draft release.

[ ] Make sure that WIP releases in releases repo branch are removed and not merged to master since the master branch is deployed automatically after merging PR and that would make WIP releases visible in customers’ installations which should generally not happen.

Post-Release

[ ] Update front-end cluster with the new release.
[ ] Verify release is available on all installations. You can use this script.
[ ] Send out release announcement to all customers according to these instructions.
[ ] PO subscribes to release posts on Slack to get notifications if there are follow-up messages.
[ ] Close release task on Releases board.

kyverno in 'warning PSS' mode specification is unclear to me, asked shield

we're waiting for kyverno-bundle app to be available before we can test

we can use https://github.com/giantswarm/security-bundle/releases/tag/v0.16.0 for 19.1.0

DONE

repo: giantswarm/roadmap


text:
Add update instructions to readme, store subtree helper script

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Going with a ping but please let me know if you see anything out of whack

repo: giantswarm/starboard-app


text:
Work with \u{301}, this keyboard now has a partial set of acute accen…

…t marking.
(1) This should be systematic, "v" should alternate with "v" PLUS something else.
(2) Any capital letters are actually small capitals, which generally means devoicing
(3) There should be a possibility to place multiple diacritics as in l\u{323}\u{304}, hence ǯ\u{301} and ʒ\u{301}, t\u{300}\u{301} etc.
(4) A list of combining and precomposed include:
[These are single combining units] \u{300}, \u{301}, \u{302}, \u{303}, \u{304}, ???, \u{306}, \u{307}, \u{308}, ??, \u{30A}, ??, \u{30C}, \u{311}, \u{313}, \u{315}, \u{323}, \u{325}, \u{32D}, \u{32E}, \u{350}, \u{354}, \u{355}, \u{356}
[doubles, e.g.]  \u{300}\u{301}, \u{30C}\u{301}
[triples, e.g.] \u{30C}\u{300}\u{301}

The master branch has been renamed to main - could you update the PR to reflect this?

The master branch has been renamed to main - could you update the PR to reflect this?

No need to, your changes are now merged with the main branch. 😄

authors: rueter snomos

repo: giellalt/keyboard-urj


text:
init file needs updating

The init file should export the two classes so importing is a bit easier/ works as you'd expect.

Fixed


text:
calling sem-add in quick succession overwrites updates

I'm porting old sql schema changes to sem. I scripted the process and called sem-add on each change.
sem-add ./update-002.sql ; git commit -m "db schema update 002"
sem-add ./update-003.sql ; git commit -m "db schema update 003"
sem-add ./update-004.sql ; git commit -m "db schema update 004"
.
.
sem-add ./update-364.sql ; git commit -m "db schema update 364"
sem-add ./update-365.sql ; git commit -m "db schema update 365"

I got files in the scripts directory:
20150423-205830.sql
20150423-205831.sql
20150423-205832.sql
20150423-205833.sql
20150423-205834.sql
20150423-205835.sql
20150423-205836.sql
20150423-205837.sql
20150423-205838.sql
20150423-205839.sql
20150423-205840.sql
20150423-205841.sql
20150423-205842.sql
20150423-205843.sql
20150423-205844.sql
20150423-205845.sql
20150423-205846.sql
20150423-205847.sql
20150423-205848.sql

19 files, versus 365 files added using sem-add. Inspecting the files, I see that there are gaps in my 1-365 sequence.
Using time-stamps is too a naïve method in this case. I will work around by sleeping for a second between executing sem-add.
ps. Thanks for this tool!

That is a good point. Minimally we should check for the existence of a file and throw an error to at least expose this edge case. Alternately, append an incrementing number at the end in the event of conflicts, to preserve the timestamp ordering but prevent the overwrites.

Thanks so much for reporting!
One possible implementation here: https://github.com/gilt/schema-evolution-manager/pull/20
This will generate a suffix on duplicate filenames. So filenames will look like:
20121113-150902.sql
20121113-150902.z1001.sql
20121113-150902.z1002.sql
the "z" is there to enforce lexicographic sorting
If you have 10k files / second, you'll get an error.
Curious what you think about this approach ... one alternative is to inject the sleep(1) into sem-add itself when there is a duplicate. That would avoid needing the .zxxxx suffixes.

I did a quick test, and this looks to work well. The suffix is fine. Using sleep isn't that nice IMO, it adds 365 seconds of waiting in my specific use-case. :)

Looks like we can use milli, micro, nano or pico for strftime:

ruby -e '{ "milli" => "%3N", "micro" => "%6N", "nano" => "%9N", "pico" => "%12N"}.each_pair {|k,v| puts %Q{With #{k}: #{Time.now.strftime("%Y%m%d%H%M%S_" + v)}}}'
With milli: 20150424143431_116
With micro: 20150424143431_116354
With nano: 20150424143431_116372000
With pico: 20150424143431_116378000000

Thanks all! have merged the PR and published a new release -
https://github.com/gilt/schema-evolution-manager
On Fri, Apr 24, 2015 at 2:38 PM, perl2ruby notifications@github.com wrote:

Looks like we can use milli, micro, nano or pico for strftime:
ruby -e '{ "milli" => "%3N", "micro" => "%6N", "nano" => "%9N", "pico" => "%12N"}.each_pair {|k,v| puts %Q{With #{k}: #{Time.now.strftime("%Y%m%d%H%M%S_" + v)}}}'
With milli: 20150424143431_116
With micro: 20150424143431_116354
With nano: 20150424143431_116372000
With pico: 20150424143431_116378000000
—
Reply to this email directly or view it on GitHub
https://github.com/gilt/schema-evolution-manager/issues/19#issuecomment-96027707
.

authors: Seanstoppable jevonearth mbryzek perl2ruby

repo: gilt/schema-evolution-manager


text:
Documentation for structured demangling

I need to get the resulting AST from a demangle for usage in reverse engineering. I'm struggling to figure out how to actually do this, since no API surface seems to actually return the AST tree and there's no working example of how to do so.

We don't currently expose the full AST. We could add something to do that, but I wouldn't document it beyond "here's the cxxabi spec, good luck".

The AST would likely have breaking changes ~every release, which seems really unfortunate for basically all users who wouldn't be using the AST.

Yes, I think we'd do it with an off by default feature that says "if you turn this on semver goes out the window and you get zero compatibility guarantees"

authors: actioninja fitzgen khuey


text:
write/elf: change exported symbols to STV_PROTECTED

This allows us to remove the hack to change relocations to use section symbols.
Closes #587

I've tested that rustc_codegen_cranelift's test.sh works when running under x86-64 linux.

Unfortunately this only works with lld and gold, not bfd.

I think this is just replacing one hack with another, so closing.

repo: gimli-rs/object

license_source: bigquery


text:
http://social-stream.dit.upm.es is DOWN?

Hey the demo website is down?

I don't think it's coming back up

I see it up. Doesn't let you in?

Huh. Wasn't working for me yesterday but it is now.

authors: HEATH3N abenitoc erbenizer

license: mit


text:
Flip Y-axis

Is it possible to flip the Y-axis? I need a graph showing ranks (standings in a league table) during a time span. Rank 1 should be the top value of the Y-axis.
Y-axis
1
2
3
4
etc. Date 1,  Date 2, Date 3 etc. -> X-axis

It's currently not possible but you can mimic this behaviour as discussed here: #382

Thanks for quick reply. Will try to mimic the behaviour.

authors: gionkunz hbrotan

repo: gionkunz/chartist-js


text:
How to stop screen  recording ?

App crashed while touch screen for stop recording purpose

I get the same crash. Tested on iOS 11.4.


text:
Integrating With Other People's Libraries

Description
In this issue, I will provide documentation on the importance of integrating with other people's libraries and its benefits,
with a clear and concise explanation.
Please assign me this issue.
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

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

/assign

repo: girlscript/winter-of-contributing


text:
Java 22.1: Generics_Fundamentals_And_Importance

Description
Add audio, documentation, and video regarding the What are generics, importance of it
Location of File to be added The files should be added inside the Generics_Fundamentals_And_Importance which will be inside Generics folder which will be inside of Java folder. If the folder is not present, create the folder with this exact name.

The documentation file can be in the .md/.py/.ipynb format.
Audio should be in .mp3 format and to be submitted through a Google drive link.
Video can be in any format and should be submitted through a Google Drive link.

Note:
You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time. Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns. You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned. Issues will be assigned on a first come first serve basis.
Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

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

/assign

@AkMo3 can you assign me documentation?

/assign document

@prachigarg19 We are strictly following the rules of assignement any mismatch of comment from assignment will not lead to assignment. Please read carefully it is \ in the issue comment to prevent from auto assignment and we are removing all auto assignemnt.

@iamsunil25 You have been already been assigned an issue.

\assign audio


text:
Vectors in cpp

Description 📜
I have included what are vectors, what is the syntax, when should we use a vector, its advantages and disadvantages and lastly the functions of vectors.
Fixes #3530

Type of change 📝

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

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
[ ] Java#Script
[ ] 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 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

@Suvraneel plz look into this

@Kjp04 Remember to fetch and merge with the C_CPP branch before making a pull request.

Should I do it again?

@Kjp04 Remember to fetch and merge with the C_CPP branch before making a pull request.

Should I do it again?

Yes Please !!

Take backup of your code
Close this Pr
Make Another Pr
Fetch your upstream or your git repo.
Make Saperate Branch for your work
Put your content only in Apropriate Directory

Closing this PR as discussed above. Update your Repo and make a fresh PR again !


text:
Added exercises for Conditional statements in dart

Description 📜
Added exercises for Conditional statements in dart
Fixes # <152>

Type of change 📝

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

Domain of Contribution 📊

[x] Android Dev (Flutter, Java, Kotlin)

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

Screenshots / Gif (Optional) 📸

@thisisamank

@Niranjan5601 whenever you add issue just use the #152 and not # by that way the issue automatically get linked :))

Looks good to me

@Niranjan5601 whenever you add issue just use the #152 and not # by that way the issue automatically get linked :))

Thanks for the tip 👍🏻


text:
Improve HideUserCredentials function

In this fix I added replacing cmd-style arguments (/username, /u, /password, /p) and ability to handle any number of spaces between username/password key and value

Thanks!

repo: git-tfs/git-tfs


text:
checkbox within pptx output

Hi,
Is it possible to insert a tickable checkbox within the generated powerpoint file? or is it possible to embed/insert an excel object and use its tickable checkbox?
Please note: I need a checkbox that can be check NOT during the slide show presentation of powerpoint file. Please give me an idea of a checkbox that can be tick while editing the file.
Thank you.

Hi @roix31
There are no plans to support form fields or embedded Excel workbooks at this point in time.

repo: gitbrent/PptxGenJS


text:
contextCD property of SugarRecordCDContext should be public?

hey,
sometimes i need to access the NSManagedObjectContext property of a SugarRecordContext - e.g. for getting a ManagedObject with a given NSManagedObjectID with the existingObjectWithID function. should the contextCD property of the SugarRecordCDContext therefore be public (..using cocoapods) or are you supposed to handle this in another way?

@pbenkoe we're going to modify this in 2.0 in order to make it "More accessible" for users that want to access the core components behind the framework. Stay tuned

authors: pbenkoe pepibumur

repo: gitdoapp/SugarRecord


text:
🛑 vid.puffyan.us is down

In 9eaf264, vid.puffyan.us (https://vid.puffyan.us/) was down:

HTTP code: 502
Response time: 180 ms

Resolved: vid.puffyan.us is back up in 6a9cf09.

repo: gitetsu/invidious-instances-upptime


text:
🛑 search.mascotboi.xyz is down

In 125b938, search.mascotboi.xyz (https://search.mascotboi.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.mascotboi.xyz is back up in add5ed1 after 33 minutes.

repo: gitetsu/librex-instances-upptime


text:
🛑 whoogle.lunar.icu is down

In 117a100, whoogle.lunar.icu (https://whoogle.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.lunar.icu is back up in 94442e9 after 14 minutes.

repo: gitetsu/whoogle-instances-upptime


text:
🛑 whoogle.lunar.icu is down

In 0220482, whoogle.lunar.icu (https://whoogle.lunar.icu) was down:

HTTP code: 500
Response time: 429 ms

Resolved: whoogle.lunar.icu is back up in 274a026 after 5 minutes.


text:
🛑 wwg.vern.cc is down

In 205cd9d, wwg.vern.cc (https://wg.vern.cc) was down:

HTTP code: 0
Response time: 0 ms

Resolved: wwg.vern.cc is back up in c7ba586.


text:
🛑 wwg.vern.cc is down

In 87ff7bf, wwg.vern.cc (https://wg.vern.cc) was down:

HTTP code: 0
Response time: 0 ms

Resolved: wwg.vern.cc is back up in 24c57be.


text:
일자별 커밋그래프 일부 선택 이후 전체 그래프를 보기 위한 경로가 직관적이지 않음

이슈내용 : 일자별 커밋그래프 일부 선택 이후 전체 그래프를 다시 보기 위해서 더블클릭 혹은 새로고침을 통해서만 가능하여, 처음 githru를 사용할 때 혼란을 줄 수 있음.
재현경로 : githru-view > 드래그 하여 일부 그래프 선택
기대사항: 일자별 커밋그래프 일부 선택 이후 전체 그래프를 다시 보기 위한 안내 혹은 직관적인 UI 제공

#551 이슈와 유사한 내용인거 같습니다 : )

d3에서 brushing하는 예제들에서 많이 사용되는 ux인데,
두 번 리포트 될 정도로 불편한 이슈인가보군요!!! report 감사합니다!
#551 에서 진행하는 걸로 하고, 해당 이슈는 close 하겠습니다.

authors: pithesun rakseong ytaek

repo: githru/githru-vscode-ext


text:
Gitignored cname

Makes 100% sure it won’t change unless needed.

Not sure I see the utility of this. Feel free to reopen if you can point to an explanation of why it is needed.

authors: RDIL mlinksva


text:
Start the offer and wait for my GCash details. 2. Send the money. 3. Mark as paid. 4. Once verified, I'll release the BTC.  👉  Release of BTC in an instant once payment received/confirmed

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?

[ ]   #@_****_

What changes are you suggesting?

[ ]   #@_****_

Additional information
No response

repo: github/docs


text:
Make it clearer in search results which product an article belongs to

As reported in slack:

If you're on the help site for GitHub.com is search expected to pull up results for Desktop? I just had a very confused user looking for a 'history' button, because if you search for 'revert' on help it drops you into https://help.github.com/en/desktop/contributing-to-projects/reverting-a-commit without really flagging to you that you've left GitHub.com

@jleaver replied:

yes, that is expected. we want people to be able to search across the entire library of content. in the future, it’ll also include search results for developer docs content (once those sites are combined). the product dropdown at the top indicates what product you’re in (in this case, it indicates that they were in github desktop content).
i think this is good feedback though and we could look into  making it more apparent which product’s content you’re viewing in search results. maybe even a small label by the search result indicating which product it’s in…?

Let's look into supporting this!
/cc @github/product-docs-engineering @gladwearefriends

Possible to add the mockups here? That link in not accessible for me.

@github/docs-engineering Is it possible to get some more information (screenshots or mockups) added to this issue? The links above ☝ aren't available to contributors. Thank you!

Yes! Mockups and some additional context is below:
We think users should be able to search one or many of each "product" that exists in the site's sidebar:

GitHub.com
Enterprise
GitHub Actions
GitHub Packages
Developers
REST API
GraphQL API
GitHub Insights
GitHub Desktop

Mockup for search on homepage
The search design/UI has changed a bit but the UX here should be accurate.
Notes:

Searching on the homepage by default should search the query through all products on the site ().
It should be easy to decipher which product results fall under.
For homepage search, we should only show the latest version of each product
Users should be able to apply a filter to search only within a specific product

Mockup for search elsewhere on the site

Search on any page, that is not the homepage, should by default search the query within the current product (and version, if viewing enterprise docs).
The example mockup shows the user on an Enterprise doc page, thus the search is only looking within Enterprise docs and the current version the user is viewing.
User should be able to clear these filters, and search through all products.

Sure! These are some (old) screenshots that should help illustrate the concept as once imagined by one of our designers:

@saracope thanks for pointing that out! We added the mockups and the missing context ☝🏿

authors: chiedo janiceilene saracope sarahs zeke


text:
Typo in searching-users.md

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/search-github/searching-on-github/searching-users#search-by-account-name-full-name-or-public-email
What part(s) of the article would you like to see updated?
The org:name example, it’s saying type:users instead of type:user:

Qualifier
Example

user:name
user:octocat matches the user with the username "octocat".

org:name
org:electron type:users matches the Electron organization's account name.

in:login
kenya in:login matches users with the word "kenya" in their username.

in:name
bolton in:name matches users whose real name contains the word "bolton."

fullname:firstname lastname
fullname:nat friedman matches a user with the full name "Nat Friedman." Note: This search qualifier is sensitive to spacing.

in:email
data in:email matches users with the word "data" in their email.

Additional information
No response

@mhashim6 Thank you for opening an issue and linking it to your PR! ✨


text:
Default GITHUB_TOKEN permissions are not not enough to fetch alerts

The README mentions that "For accessing the Code Scanning alert data, the action uses the GITHUB_TOKEN which is automatically created for you, so you don't need to provide it".
But in reality i had to manually create another PAT and use it like that for the actions to successfully fetch security alerts:
jobs:
jira-sync:
name: Jira Sync
runs-on: ubuntu-latest
steps:
- name: Sync alerts to Jira issues
uses: github/ghas-jira-integration@v1
with:
github_token: ${{ secrets.TEST_GITHUB_TOKEN }}
jira_token: ${{ secrets.JIRA_TOKEN }}
jira_url: 'https://apiseq.atlassian.net'
jira_user: 'github-bot@neosec.com'
jira_project: ${{ github.event.inputs.project }}
jira_labels: 'code-scanning'
sync_direction: 'gh2jira'

when not adding the manually created PAT i get the following error:
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://api.github.com/repos/neosec-com/neosec-frontend/secret-scanning/alerts?per_page=100

@roimor if you curl the endpoint with a run action and use ${{ secrets.GITHUB_TOKEN }} do you see the same behaviour? We may get some additional information with the verbose output.

The README was updated to reflect this issue. According to the list endpoint, you must be an admin of the repo/org and the token must have the security scope. https://docs.github.com/en/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository
That's why the PAT works and the permissions of the GITHUB_TOKEN doesn't. I believe this extends to users who were given access to the alerts by an admin too 🤔

@cmboling quoting from the README line 25-26:
"For accessing the Code Scanning alert data, the action uses the GITHUB_TOKEN which is automatically created for you, so you don't need to provide it"
... The docs are still misleading.
@AWNCypher indeed, before i opened this issue i tried running curl with the default token and run into the same problem.

Ok I can clear up the docs, no problem!
@roimor are you an admin of the repo that you're testing?

I am the org admin, and yes that is partially the workaround.. while you also need to be repository admin

Dropping a comment here - we had this issue, and it wound up being that our org has SAML enforcement that prevented PATs even with full permissions from accessing org resources. You need to authorize the PAT specifically for this use case.
Also want to say that GH documents the ability to scope the Actions GITHUB_TOKEN to security-events but the default token did not appear to work even with that scope included.

authors: AWNCypher cmboling marvelous-melanie roimor

repo: github/ghas-jira-integration


text:
Add Lighthouse CI gitignore

Reasons for making this change:
Adds gitignore for the lighthouse CI report folder.
Links to documentation supporting these rule changes:
https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md#collect
If this is a new template:

Link to application or project’s homepage: https://github.com/GoogleChrome/lighthouse-ci

Can you expand on why this is needed and if this should instead be placed in the Node.gitignore instead.
https://www.brianperry.dev/til/2021/running-lighthouse-ci-server-locally/
Per the contribution guidelines, this file should be placed in the community folder. Please edit the location of the file.
https://github.com/github/gitignore#specialized-templates

authors: bdougie nachogarcia

repo: github/gitignore


text:
foundation detected as PHP

foundation detected as ~75% php.
But php files in foundation use a lot of php and one to three php instructions.
It should be detected as ~70% html and ~5% php

At the moment, we are not including "markup languages" in the repo stats.

authors: josh stereobooster

repo: github/linguist


text:
Add rebar-related files as erlang.

rebar.config and rebar.lock are akin to Gemfile and Gemfile.lock for Erlang, used by the rebar tool.

Looks like you'll definitely need to commit sample files, according to the test:

Missing sample in "samples/Erlang/filenames/rebar.lock"

The shell error might be fixed by https://github.com/github/linguist/pull/2299; I wouldn't worry about it for this PR.

Added them. Sorry about that, I tried running tests locally but maybe got sidetracked by the shell failure.

@dpiddy - would you mind rebasing against master? The build is now fixed up.

Done!

@dpiddy - should we add rebar.config.lock also? There looks to be a bunch of these: https://github.com/search?l=&q=require+filename%3Arebar.lock&ref=advsearch&type=Code&utf8=✓

@arfon yeah, added. Getting failures like this now:
  1) Failure:
TestClassifier#test_classify_ambiguous_languages [/Users/dan/Projects/ruby/linguist/test/test_classifier.rb:53]:
/Users/dan/Projects/ruby/linguist/samples/Erlang/filenames/rebar.config.lock
[["JSON", -2112.7576908263964], ["Erlang", -2501.5084453755526]].
Expected: "Erlang"
  Actual: "JSON"

will try and fix but any tips appreciated.

Well, travis seems to be fine with it so maybe not an issue.

Well, travis seems to be fine with it so maybe not an issue.

@dpiddy That's because #2299 was just merged ;) (see @gjtorikian's comment)

@pchaigno I meant the classifier failure I pasted above. I'm getting these two failures locally but like I said travis seems ok:
  1) Failure:
TestClassifier#test_classify_ambiguous_languages [/Users/dan/Projects/ruby/linguist/test/test_classifier.rb:53]:
/Users/dan/Projects/ruby/linguist/samples/Erlang/filenames/rebar.config.lock
[["JSON", -2112.7576908263964], ["Erlang", -2501.5084453755526]].
Expected: "Erlang"
  Actual: "JSON"

  2) Failure:
TestBlob#test_language [/Users/dan/Projects/ruby/linguist/test/test_blob.rb:519]:
rebar.config.lock.
Expected: "Erlang"
  Actual: "JSON"

Oh, okay. That's usually because you need to regenerate the samples. Try bundle exec rake samples in your local copy.

Thanks, that did it! All good now.

:+1: thanks @dpiddy

authors: arfon dpiddy gjtorikian pchaigno


text:
Optional expiration for Personal Access Tokens (Server)

Summary
Personal Access Tokens, or PATs, provide users with a quick way to create OAuth access tokens with they can use to make API calls. This is a typical way of getting API keys in SaaS products – PATs are broadly used today for needs that range from quick testing to automating workflows. However, PATs today do not offer an expiration option, meaning they exist until they are manually disabled. Long-lived tokens (or, those with no expiration at all) can create larger security implications if they are to leak. Adding optional expiration to PATs increases both a user's and organization's ability to secure how their data is accessed.
Intended Outcome
Users can create new PATs with optional expiry (specified at time of creation).
How will it work?
Once introduced, the form for creating new PATs will have a new expiration field, allowing users to choose preset expiration intervals (7, 30, 60, 90 days from date of creation), a custom expiration date in the future, or no expiration. By default the shortest expiration interval will be chosen. The time and date of expiration will be returned in the response header when a PAT with expiration is used, and as the expiration of a PAT approaches, the owner will be notified by email in addition to a warning message in the GitHub CLI if it's being used. Once a token expires, it will be disabled and no longer be able to access GitHub APIs.
Screenshot

https://github.blog/2021-12-07-github-enterprise-server-3-3-is-generally-available/

authors: Sid-ah github-product-roadmap

repo: github/roadmap


text:
Use dom-input-range instead of internal implementation

We currently use an approach of cloning the textarea element into a hidden div with all of its styles and content, because the browser allows calculating the position of contents in a div but not in a textarea. This approach has been duplicated and adapted in many places:

here
https://github.com/primer/react/blob/a0db832302702b869aa22b0c4049ad9305ef631f/src/drafts/utils/character-coordinates.ts
https://github.com/component/textarea-caret-position/blob/b5db7a7e47dd149c2a66276183c69234e4dabe30/index.js
https://github.com/primer/react/blob/a0db832302702b869aa22b0c4049ad9305ef631f/src/drafts/utils/character-coordinates.ts
internally in github/github

The original implementation of this approach is nearly a decade old at this point and we have better options today. Notably, this approach can be pretty inefficient due to how we create and don't clean up the clones, and due to how often we have to copy the styling. This can be as often as every keystroke. In addition this implementation is missing some bugfixes implemented in the source materials after this was derived.
A few months ago I took this approach and rewrote it with a more modern DOM-like API (inspired by Range). I audited all the styles we are copying, included all the bug fixes / workarounds from the various diverging implementations, and optimized performance significantly. The clone element is now reused across calls, automatically cleaned up, and only updates when and if necessary (ie, when the user types we don't need to re-clone the styles, we only need to update the text content).
The result is https://github.com/iansan5653/dom-input-range, which exposes the InputRange API as well as the lower-level input-clone-element. I've been using this for several months in https://github.com/iansan5653/github-markdown-a11y-extension and I'm confident in its reliability and accuracy. Migration is easy and comes with significant performance & code quality improvements, so why not make the switch?
Additional changes
dom-input-range uses import type syntax, which the version of TypeScript we are on does not support. Upgrading TypeScript also required upgrading eslint-plugin-github (to update the parser) which required updating eslint.
The latest version of ESLint is not compatible with Node 16.x, so I also updated the devcontainer config to move us on to 20.x. This was an oversight previously anyway since our CI is on v20.
Updating ESLint plugin enabled some rules that are violated in test files. Rather than fix these errors and expand the PR footprint, I've disabled them for now since these are only test files.

I need some time to take a look at this, but I'm curious if dom-input-range supports alternate writing directions or bidi? I vaguely recall that text-expander does but a quick glance at the demos in dom-input-range seems to suggest it doesn't?

I need some time to take a look at this, but I'm curious if dom-input-range supports alternate writing directions or bidi? I vaguely recall that text-expander does but a quick glance at the demos in dom-input-range seems to suggest it doesn't?

Good question, I'm not sure about this. If it needs special handling it's probably something I need to implement that wasn't present in the sources I derived from. I glanced through the code here but I don't see any special handling here either. Maybe it just works automatically?

Do you have some example content I could try out?

In chrome you can right click an input to change the writing mode. Looks like it might need to simply copy over the writing-mode/unicode-bidi computed styles? There may be more to it. I don't recall if text-expander supports it or not but I do recall there being a lot of work around writing directions or maybe it was composition events...

Doesn't look like text-expander does support LTR actually:

I agree this is something we should add but probably a separate issue.

maybe it was composition events

This I do remember. That's a total headache and we've dealt with it several times. That shouldn't be affected by this change though.

Created an issue to track the text direction work upstream:

https://github.com/iansan5653/dom-input-range/issues/2

Couldn't get an integration test PR working but I was able to test this locally (in github/github):
cd /workspaces
git clone https://github.com/github/text-expander-element && cd text-expander-element
git checkout use-dom-input-range
npm run compile
cd ../github
npm link -w @npm-workspaces/primer ../text-expander-element

repo: github/text-expander-element


text:
config.view_component.generate_stimulus_controller vs config.view_component.generate.stimulus_controller

the API documentation mentions config.view_component.generate.stimulus_controller = true while the current correct syntax seems to be with an underscore, i.e. ``config.view_component.generate.stimulus_controller = true`

relates to https://github.com/github/view_component/issues/1362

This will be solved by #1291

authors: Spone koenhandekyn


text:
How do I scan files inside a folder?

$ gitleaks detect -s ~/ubuntu/leak-scan/results/folder

    ○
    │╲
    │ ○
    ○ ░
    ░    gitleaks

6:04AM ERR [git] fatal: not a git repository (or any of the parent directories): .git
6:04AM ERR  error="stderr is not empty"
6:04AM WRN partial scan completed in 12.6ms
6:04AM WRN no leaks found in partial scan

I am not trying to scan github repositories, would be possible to scan files? shouldn't make any difference in the scan at all, it should check leaks in files/folders.

What about if using actions? I am trying to set it up in a composite action and I need to scan a custom directory.
name: Gitleaks
description: Gitleaks scan

inputs:
  fetch-depth:
    required: false
    description: 'Number of commits to fetch during checkout. 0 indicates all history for all branches and tags'
    default: '1'

runs:
  using: "composite"
  steps:
    - name: Checkout code
      uses: actions/checkout@v4
      with:
        path: code
        fetch-depth: ${{ inputs.fetch-depth }}

    - uses: gitleaks/gitleaks-action@v2
      env:
        GITHUB_TOKEN: ${{ inputs.github_token }}
        GITLEAKS_LICENSE: ${{ inputs.gitleaks_license }}

repo: gitleaks/gitleaks


text:
Create main branch CD pipeline

Requirements

use Github Action
target: release branch PR merge
build and publish

npm package security tokens will be soon updated in repo secrets
sementic version tags can be added

여기서 cd는 npm 라이브러리에 자동 배포되는 개념인가요?

@hoduulmu

여기서 cd는 npm 라이브러리에 자동 배포되는 개념인가요?

네 맞아요.

Will be reopned after publishing the project and versioning rules are set

repo: gitovep/gitove


text:
Incorrect centered image when is located in north-east position

Hi,
I have no idea what I'm doing wrong. When I try to place the picture in the upper right corner, it is incorrect centered.

https://gitpitch.com/burgyn/presentations/master?p=LayoutTest
see my repo: https://github.com/Burgyn/Presentations/tree/master/LayoutTest
Thank you in advance for your advice.
Info:
OS: Windows 10
Browser: Opera

@Burgyn the issue here appears to be the aspect ratio you are using to view your slide deck in your browser.
The standard aspect ratio for a GitPitch slide deck is 16:9. But looking at your screenshot it looks like you have sized your browser to be very wide (left-to-right) but also very short (top-to-bottom). As a consequence of this layout for your browser the positioning of your image looks off.
To test my theory you should try viewing your slide deck in full-screen mode. To open full-screen mode, press the F key. If you are viewing your slide deck on a standard laptop or desktop your full-screen aspect ratio will be 16:9. So you should see the content on your slides rendered as you expect. Do you?
If you try this test let me know how it goes. Cheers, David.

Hi, thanks for your advise.
Unfortunately it didn't help. My screen resolution (in fullscreen mode) is 1920x1080.
I try change question.
How can I correctly center image in each of six positions?
When I trying it, images aren't centered properly.
Please see my example:
https://gitpitch.com/burgyn/presentations/master?p=LayoutTest

Thank you in advance for your advice.

How can I correctly center image in each of six positions?

It appears the main problem here is a mismatch of expectations. Your background image colored boxes do not correspond to the snap-layouts grid compass positions - they do not account for margins, padding, etc. So centering the sample image inside each of your colored boxes is not possible.
For testing purposes, if you are trying to see what region of your slide maps to a specific snap-region then instead of using a colored background image you are better activating a background color property on the snap tag. For example, @snap[north-west span-33 bg-yellow] That will show you the exact region on your slide the snap-region maps to. If you adjust the span-xx property value and/or add content within the snap tags you will see the size of that region changes accordingly.
Here are the default alignments for the snap-grid:

north-west, west, and south-west are text-left aligned by default
north, midpoint, and  south are text-center aligned by default
north-east, east, and south-east are text-right aligned by default

If you want to horizontally center your content in each snap-region on your slide (regardless of the position on the grid) simply activate the text-center property on each snap tag.

Hi,
thanks for your clear explanation.

authors: Burgyn gitpitch

repo: gitpitch/gitpitch


text:
🛑 MSP-002 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: MSP-002 is back up in 66e38ab.

repo: gitsrc/upptime


text:
lt.js - Lithuanian

I have created another translation for my native language, Lithuanian. If you have any questions or enquiries please don't hesitate to message me.
Matas

@mataslt Can you get another native Lithuanian speaker to review this?

Yes certainly, I can get my friend which is also a Lithuanian native, to review this. I will send you his email address tomorrow and you can contact him for your confirmation about his native language.
Thanks
Matas

@mataslt Just ping them here via mention.

Yes okay, his username is @swarcaslt he will review it in 5 to 10 minutes.
Thanks.

Hello,
I have reviewed the work done by @mataslt. And I can confirm that the translations are all done corectly.
Best Regards.

And Google Translate concurs too. Thanks @mataslt, @swarcaslt

authors: MadLittleMods mataslt suprememoocow swarcaslt

repo: gitterHQ/gitter-translations


text:
Support Django 3

Django 3 is to be released next week.
django-fsm does not yet support Django 3, but there's not that large changes needed, and there is a working fork, so support in django-fsm-log is useful even if django-fsm isn't updated.
To get django-fsm-log working with Django 3 is mostly a matter of stop using Django's private Python 2 compat APIs, https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility-apis, e.g. django.utils.six.

Django 3 is now out and django-fsm 2.7.0 has been released with Django 3 support.

This line with django.utils.encoding.python_2_unicode_compatible is also breaking with Django 3:
https://github.com/gizmag/django-fsm-log/blob/355cb226534cd31c7cdbf76fb7b25526d922c42c/django_fsm_log/models.py#L7

BUMP. Was this released? I cannot find the next version on pip: https://pypi.org/project/django-fsm-log/#history

With the merge of #99, this can be closed.

authors: clovis1122 jodal moseb

repo: gizmag/django-fsm-log


text:
NCBI nucleotide download issue

Hi there - I am using the very new version of the crabs package and have successfully gotten it running, have downloaded the NCBI taxonomy, and have downloaded sequences from BOLD. Now I am trying to download sequences from NCBI nucleotide. When I run the following query:
crabs --download-ncbi --query '"16S"[All Fields]' --species Acanthophora --output /Users/saraswaminathan/Desktop/crabs/crabs_testing/ncbi_nucleotide1.fasta --email saraswami94@gmail.com --database nucleotide --batchsize 5000
I get the following error:
Traceback (most recent call last):
  File "/Users/saraswaminathan/reference_database_creator/crabs", line 844, in <module>
    crabs()
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/rich_click/rich_command.py", line 152, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/crabs", line 542, in crabs
    console.print(f"[cyan]|             Results[/] | Number of sequences downloaded: {total_downloaded_seqs}/{total_read_count} ({round(total_downloaded_seqs / total_read_count * 100, 2)}%)")
                                                                                ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
ZeroDivisionError: division by zero

I also tried the same command, but with a species list .txt file instead of the single taxa:
crabs --download-ncbi --query '"16S"[All Fields]' --species Acanthophora --output /Users/saraswaminathan/Desktop/crabs/crabs_testing/ncbi_nucleotide1.fasta --email saraswami94@gmail.com --database nucleotide --batchsize 5000
When I do that, I get this error:
File "/Users/saraswaminathan/reference_database_creator/crabs", line 844, in <module>
    crabs()
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/rich_click/rich_command.py", line 152, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/crabs", line 538, in crabs
    total_read_count, ncbi_info_dict = ncbi_download_info(console, columns, query_list, database_, email_)
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/function/crabs_functions.py", line 289, in ncbi_download_info
    query_key, web_env, matching_seq_count = retrieve_init_ncbi_info(database_, email_, item)
                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/function/crabs_functions.py", line 248, in retrieve_init_ncbi_info
    query_key = content_str.split('<QueryKey>')[1].split('</QueryKey>')[0]
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range

Thanks very much!!!!

Hello @saraswaminathan,
Thank you for bringing this bug to our attention. There was an issue with the NCBI query building code when a species was provided. I've updated the code (crabs --version 1.0.1) and all should work now.
Best wishes,
Gert-Jan

Thank you! With the updated package, I am still getting errors when I try to input a .txt file as the species list for the ncbi download. However, I am just using a for-loop the way I did for the BOLD download, which is working. I get the ZeroDivisionError for any taxa where the search in ncbi returns 0 hits, but in this case it just skips over this taxon and does not create a .fasta file for it, which is fine.

Hello @saraswaminathan,
Apologies, I overlooked the issue with the species text file.
The new version (crabs --version 1.0.2) now fixes the ZeroDivisionError reported by CRABS when 0 sequences are downloaded.
I can't seem to recreate the error you receive when reading from a species text file. Do you mind attaching the text file to your response, as well as the code you used? This might help in trying to figure out the issue.
Best wishes,
Gert-Jan

Hi Gert-Jan,
I updated to 1.0.2 and ran the following code:
crabs --download-ncbi --query '"16S"[All Fields]' --species /Users/saraswaminathan/Desktop/crabs_old/atlantic_genera_algae1.txt --output /Users/saraswaminathan/Desktop/crabs/ncbi_txt_test.fasta --email saraswami94@gmail.com --database nucleotide --batchsize 5000
I'm attaching the text file I used. It appeared to be running ok but then quit at ~20% with the following error message:
Traceback (most recent call last):
  File "/Users/saraswaminathan/reference_database_creator/crabs", line 847, in <module>
    crabs()
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/rich_click/rich_command.py", line 152, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/miniconda3/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/crabs", line 538, in crabs
    total_read_count, ncbi_info_dict = ncbi_download_info(console, columns, query_list, database_, email_)
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/function/crabs_functions.py", line 289, in ncbi_download_info
    query_key, web_env, matching_seq_count = retrieve_init_ncbi_info(database_, email_, item)
                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/saraswaminathan/reference_database_creator/function/crabs_functions.py", line 248, in retrieve_init_ncbi_info
    query_key = content_str.split('<QueryKey>')[1].split('</QueryKey>')[0]
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range

atlantic_genera_algae1.txt
Thank you!!
Sara

Hello @saraswaminathan,
Thank you very much for the example and the text file. This is extremely helpful! I ran the code below, which mirrors your input and managed to download the NCBI data without issue. Please see code and output below.
crabs --download-ncbi --query '"16S"[All Fields]' --species atlantic_genera_algae1.txt --output ncbi_txt_test.fasta --email gjeunen@gmail.com --database nucleotide

/// CRABS | v1.0.2

|            Function | Download NCBI database
|         "--species" | identified as document with 100 name(s)
|Retrieving NCBI info | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00 0:01:43
|         Downloading | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸ 100% 0:00:04 0:16:44
|             Results | Number of sequences downloaded: 50386/50507 (99.76%)

What I think is happening is that there might be some connection issues with the NCBI servers. This could either be due to an overload of traffic on the NCBI servers when you're running your code or that the NCBI servers have limited your access. This might sometimes happen when you're taking up too much traffic by downloading huge chunks of data.
The reason why I think this is the issue, is that the error indicates that the initial data retrieved from NCBI by CRABS, which CRABS parses and uses to download the actual sequences, doesn't seem to exist.
In CRABS --version 1.0.3, I have now added a check to ensure a connection to the NCBI servers can be made. CRABS will try this 3 times. If the connection cannot be made in three consecutive tries, CRABS will report an error and quit the download from the NCBI servers.
Please let me know if this solves your issue.
Best wishes,
Gert-Jan

Hello @saraswaminathan,
I will assume this issue has been fixed and will close this item, but please let me know if issues persist.
Thanks,
Gert-Jan

authors: gjeunen saraswaminathan


text:
Remove calls to rio.parse_path (maintain compat with rasterio==1.3)

rasterio.path (and therefore, rasterio.parse_path) is being deprecated in rasterio 1.3 and removed in 1.4.
It is called internally anyway by DatasetBase so shouldn't be necessary to call it while initing.
Have checked that this works for my use case, YMMV.

(I did no formatting to keep to the diff as small as possible, happy to if preferred.)

We're constructing rasterio DatasetReader objects directly, instead of going through rio.open, like @Kirill888 mentioned in https://github.com/rasterio/rasterio/issues/2365#issuecomment-1086979284. That's why we were passing in parsed paths instead of raw strings. (It's also nice to not have to re-parse the path in every thread, but that should be a trivial amount of time.)
Based on https://github.com/rasterio/rasterio/pull/2428, it sounds to me like the changes in this PR (passing raw strings into the DatasetReader) will only work with rasterio>=1.3.0. So you'll need to update the requirement as well, or add some annoying version-conditional code that I'd rather not have.

Yeah sorry, should have marked this as a draft/discussiony PR.
In the meantime should probably lock down the rasterio dep, otherwise standard installs will break as soon as 1.3.0 lands.
diff --git a/pyproject.toml b/pyproject.toml
-rasterio = "^1.2.3"
+rasterio = "~1.2.3"

And the make the change from this PR + upgrade to ~1.3.0at the opportune moment.

Let's just make the rasterio change in this PR as well. It looks like someone who installs stackstac today and gets the new rasterio will have things fail: https://github.com/microsoft/PlanetaryComputer/discussions/80#discussioncomment-3084173.
This is quite an urgent fix. As soon as this is in, I'll cut a release.

Ah I see, rasterio 1.3.X is still in pre-release: https://pypi.org/project/rasterio/#history. I don't quite understand how a PC user ended up with a pre-release version then: https://github.com/microsoft/PlanetaryComputer/discussions/80#discussioncomment-3084173.
In that case, I agree. We should make and release this change right now:
diff --git a/pyproject.toml b/pyproject.toml
-rasterio = "^1.2.3"
+rasterio = "~1.2.3"

Then merge this PR and switch to rasterio = "^1.3.0" once it lands.

👋 @gjoseph92
FYI 1.3 is going to be published today or tomorrow https://github.com/rasterio/rasterio/issues/2310#issuecomment-1175431663

PR here with the rasterio constraint: https://github.com/gjoseph92/stackstac/pull/157
Regarding people having rasterio 1.3bX installed: 1.2.X doesn't have wheels for Python 3.10 (which now ships as default on Ubuntu 22.04).

@carderne rasterio's got your back: https://github.com/rasterio/rasterio/commit/5d5d946fbdc5a9babc7030e8f68b8ca4ccc538a2.

Thanks so much @sgillies!
Once 1.3.0 is out, we can merge this and release, but that takes the time pressure off.

Woohoo!

Open source saves the day!

authors: carderne gjoseph92 sgillies vincentsarago


text:
Add status LED to instance table

Get your bikeshedding on! Must have LEDs in instance table!

My rendition.


text:
Ensure downloaded images with transparent background looks correct

I recall that the colors looked incorrect previously possibly due to premultiplied alpha settings?

No combinations of alpha rendering and premultiplied alpha settings seem to result in the image being different. Will need to test exporting the images again. It may occur only in saved png files?
Test fiddle
https://jsfiddle.net/cyrf21zm/

Looks like everything lines up with the displayed canvas. Using premultipliedAlpha === true is what should be used for the best result when rendering and saving:

premultipliedAlpha: false
premultipliedAlpha: true

repo: gkjohnson/three-gpu-pathtracer


text:
Any way to turn off the trace file?

I call this library from multiple directories and it puts dev_rfc.trc wherever I call it.
It creates when I put this in startup parameters:
$parameters = [
'trace' => \SAPNWRFC\Connection::TRACE_LEVEL_OFF,
..
];
Or when I do this
SAPNWRFC\Connection::setTraceLevel(0);
It creates a file telling me I turned the trace level down.
When I copy the sapnwrfc.ini to my current directory and change RFC_TRACE_DIR=/tmp it works correctly, but I can't copy that everywhere I call it.
The sapnwrfc.ini says "By default the NW RFC library looks for the sapnwrfc.ini file
in the current working directory of the process. If you want
to change that behaviour, you can set an alternative directory
using the API RfcSetIniPath()
But I don't know how to do that.  I tried calling that from the library, but it didn't seem to do anything.
This is driving me nuts, I'd appreciate any help.

https://gkralik.github.io/php7-sapnwrfc/usage.html#trace-levels

As far as I'm aware, you cannot fully suppress the generation of the trace file. Your best option is turning down the trace level and setting a different trace directory by using SAPNWRFC\Connection::setTraceDir($path) or by using the RFC_TRACE_DIR environment variable.

authors: gkralik lhenkel


text:
Does LiveScript really need (to support) async/await?

As far as I could understand, async/await is there for adding syntactic sugar that makes the code that heavily uses Promises readable.
LiveScript has backcalls. We can write thousand of callbacks in the same column, no callback hell. Backcalls are like "Just replace = with <- and you now have await".
Is async/await a solution to a problem in the Javascript world that Livescript has solved it before? Is async/await pointless in Livescript?

Backcalls aren't quite as powerful as promises. async/await integrates with control flow structures in a way that backcalls don't and probably never will. Consider an await inside a loop, or inside a try/catch/finally expression, and think about the hoops you'd need to jump through to translate that into equivalent code that uses callbacks. LS's backcalls are intentionally very simple; the transformations applied by JS implementations to async/await can get considerably more complicated, and why duplicate that work in LS?

Consider an await inside a loop

That's absolutely a necessity. I'm working around this by the following <~ :lo(op) ~> approach:
sleep = (ms, f) -> set-timeout f, ms
debug-log = -> console.log ...[(new Date! .toISOString!), ...arguments]

i = 3
debug-log "start"
<~ sleep 1000ms
<~ :lo(op) ~>
    debug-log "hi #{i}"
    i := i - 1
    if i is 0
        return op! # break
    <~ sleep 1000ms
    lo(op)
<~ sleep 500ms
debug-log "end of loop."

#  Outputs:
# 2019-09-17T02:25:56.952Z start
# 2019-09-17T02:25:57.953Z hi 3
# 2019-09-17T02:25:58.954Z hi 2
# 2019-09-17T02:25:59.955Z hi 1
# 2019-09-17T02:26:00.457Z end of loop.

or inside a try/catch/finally expression

Well, I've no proposal for that as I never needed such thing. I'll think about it.
It turns out I re-invented Promises before I get to know them, with a slightly different approach: https://github.com/ceremcem/signal. That's why I never needed Promises hence the async/await.
Anyway I think I got the idea. If we have a chance to use a "default tool" for a job, you say it would probably make the job done simpler and simpler is better.

One more headache is if / else statements with async calls:
if doc?
    my-doc.attachments.push doc
else
    # fetch the document `doc` and then make the attachment
    err, res <~ db.get 'doc'
    my-doc.attachments.push res
err, res <~ db2.put my-doc
console.log "my-doc has been saved"

Obviously above code doesn't work as it won't wait for db.get 'doc' phase.
My workaround was using my SignalBranch:
branch = new SignalBranch
if doc?
    my-doc.attachments.push doc
else
    # fetch the document `doc` and then make the attachment
    my-signal = branch.add!
    err, res <~ db.get 'doc'
    my-doc.attachments.push res
    my-signal.go!
<~ branch.joined
err, res <~ db2.put my-doc
console.log "my-doc has been saved"

Of course, it would be simpler to write it like so (I'm not sure about the syntax, I'm not familiar with await/async):
unless doc?
    # fetch the document `doc` and then make the attachment
    doc = await db.get 'doc'
my-doc.attachments.push doc
err, res <~ db2.put my-doc
console.log "my-doc has been saved"

The arguments for async/await syntax go even deeper than simplicity. Consider your last pair of code snippets:
branch = new SignalBranch
if doc?
    my-doc.attachments.push doc
else
    # fetch the document `doc` and then make the attachment
    my-signal = branch.add!
    err, res <~ db.get 'doc'
    my-doc.attachments.push res
    my-signal.go!
<~ branch.joined
err, res <~ db2.put my-doc
console.log "my-doc has been saved"

I realize this is a simplified example for purpose of discussion, but nevertheless: this code has a problem. If the db.get 'doc' call ‘returns’ an err, this code doesn't report it and happily goes on to push my-doc into db2 anyway. Now, of course, it's pretty easy to go in and add error-handling code... but the point is, when using await:
unless doc?
    # fetch the document `doc` and then make the attachment
    doc = await db.get 'doc'
my-doc.attachments.push doc
await db2.put my-doc
console.log "my-doc has been saved"

you don't have to. In this version, an error in db.get (or, for that matter, in db2.put) will prevent the subsequent statements from running—just like with a synchronous call—and be captured in the enclosing Promise, hopefully to be handled by either a regular try/catch or by a .then on-success, on-error or .catch on-error call directly on the Promise.
So not only does await mean writing less code, it also means handling errors for each asynchronous call isn't one more thing you have to remember to do correctly. Making fewer traps for programmers to fall into is a pretty strong reason to prefer await, even if it didn't also make your code simpler.

For being a reference people like me (and myself), here is the rewrite of above "workarounds":
sleep = (ms) ->
  new Promise -> setTimeout it, ms

db =
  get: (id) ->>
    await sleep 2000ms
    if id is 'opps'
      throw new Error "There is something happened unexpected"
    else if id.length > 5
      throw new Error "document #id not found."
    return {id, value: "the value of #id"}

  put: (doc) ->>
    await sleep 2000ms
    if id is 'opps'
      throw new Error "There is something happened unexpected"
    else if id.length > 5
      throw new Error "document #doc.id can not be saved."
    return {doc.id, attachment-count: doc.attachments.length}

do ->>
  try
    my-doc = {id: "my", attachments: []}
    unless doc?
      console.log "Fetching the document"
      doc = await db.get 'opps'
    my-doc.attachments.push doc
    console.log "Saving my-doc: ", my-doc
    await db.put my-doc
    console.log "my-doc put status:", err, res
  catch
    console.error "Something went wrong: ", e

do ->>
  console.log "hello"
  for to 5 when .. < 4
    console.log "there #{..}"
    await sleep 1000ms
  console.log "done."

Here I guess it doesn't matter, however in general it's probably better not to use await in loops, since you won't get batching at all.

@vendethiel Sorry, I couldn't understand. What do you mean by "getting batching"?

Sorry. I mean you get sequential and not parallel requests.
pages = []
for from 1 to 5
  pages.push await get-page ..
# queries page 1, waits for the request to be complete, queries page 2, waits, ...

# VS

pages <- Promise.all [1 to 5]map get-page
# starts the 5 queries at once

Depends on what you want...

Oh, yes, I got it now. This sequential pattern is useful while implementing "reconnect/retry" pattern:
for from 1 to 3
  ok = await send-over-serial-port "my data"
  break if ok
unless ok
  throw new Error "We can't send data by the serial port"

@ceremcem
i've rewritten your example with this:
# shared data
data =
  error: false
  doc: null

# async controller
branch = new SignalBranch {
  step1: !->
    if data.doc
      myDoc.attachments.push data.doc
      @step2!
    else
      err, res <~ db.get 'doc'
      if not err
        myDoc.attachments.push res
        @step2!
      else
        @error!

  step2: !->
    err, res <~ db2.put myDoc
    if not err
      console.log("my-doc has been saved");
    else
      @error!

  error: !->
    data.error = true
    console.log 'error occured'
}

so it's longer, but more readable, what you think? 8)

some links about this theme in general:
https://esdiscuss.org/topic/alternative-to-promise
https://github.com/kriskowal/q/blob/v1/design/README.md

@determin1st

so it's longer, but more readable, what you think? 8)

Sadly no, I don't find this more readable, because sometimes I use lots and lots of nested SignalBranch. Something like this:
b1 = new SignalBranch
b1s1 = b1.add!
b1s2 = b1.add!
my-physical-button.on 'pressed', (button-num) ->
  b1.s2.go err=null, button-num
if something
  err, res <~ foo
  b1s1.go err, res
else
  b2 = new SignalBranch
  if mydoc
    doc = mydoc
  else
    b2s1 = b2.add!
    err, res <~ bar
    b2s1.go err, res
  err, signals <~ b2.joined
  b1s1.go err, myresult
err, signals <~ b1.joined
# result will be delayed till the button is pressed

Such a logic would be hard to read for me if it's configured like in your suggestion. Moreover, I generally try to avoid from using global variables (hence the := operator) because maintaining a global variable makes the code harder to reason about.
I read the Action.js and I noticed the "blazing fast" claim. I'll try the benchmark locally ASAP.

Again, re-created your example (I belive I saved the logic):
data =
  s1: false
  s2: false

new SignalBranch {
  first: !->
    my-physical-button.on 'pressed', (button-num) ~>
      data.s2 = true
      @check!
    if something
      err, res <~ foo
      data.s1 = true
      @check!
    else
      @second!

  second: !->
    if mydoc
      doc = mydoc
      data.s1 = true
      @check!
    else
      err, res <~ bar
      data.s1 = true
      @check!

  check: !->
    if data.s1 and data.s2
      @complete!

  complete: !->
    # result will be delayed till the button is pressed
}

Oke, ive got the point - We use what We use. 8)
You may avoid := by putting the data into generic object, so,
the assignment will be data.propertyName = value.
Also, it's not neccessary to be global - just some upper scope.
The performance of Action doesnt matter, imo, wont be much better than Promise..

authors: ceremcem determin1st rhendric vendethiel

repo: gkz/LiveScript


text:
MS2LDA network visualization does not show up

When starting a network visualization, the network does not show up (Please wait... does show up!)

It's clunky and slow, but seems like the network viz still works.

authors: joewandy justinjjvanderhooft


text:
Add optional CA Cert

Issue: When using this package behind a corporate network, a RestError: self signed certificate in certificate chain error occurs when attempting to interact with Azure's secret client. To resolve this issue, typically a NODE_EXTRA_CA_CERTS environment variable is added with a path to the additional certs required to validate the ssl request. However, it seems the SecretClient does not look for this environment variable by default.
Proposed Resolution: To resolve this issue following current conventions, I have updated this package to look for an optional NODE_EXTRA_CA_CERTS environment variable and inject it into the tls settings of the SecretClient if the variable is found.

Hi @oahmed-OS thank you for you PR and sorry for my very late answer, the reason being loosing interest in Insomnia after they limited the feature set to not paying/not authenticated users.
I just merged the pr #5 instead of this one, I prefer the env variable approach better because we won't take a new dependency on another library (like in this case).
Hope you will prefer it as well.
Probably you may want to generalize the approach and maybe have a dedicated plugin which would expose .env files as environment variables.

authors: glconti oahmed-OS


text:
Add timer:send_interval/3

Can we add timer:send_interval/3 to gleam/erlang/process?
It behaves similarly to send_after, except it spins up a process that repeatedly sends the message every time interval. It's useful for a low-fidelity Tick.
Since Subject(a) is opaque, I can't implement it myself in projects without resorting to FFI workarounds unpacking the Subject tuple by hand.

This would be the implementation, similar to send_after:
@external(erlang, "timer", "send_interval")
fn timer_send_interval(a: Int, b: Pid, c: msg) -> Timer

pub fn send_interval(subject: Subject(msg), delay: Int, message: msg) -> Timer {
  timer_send_interval(delay, subject.owner, #(subject.tag, message))
}

Could be cool! Is there a reason not to use send_after? It can help avoid overloading a process, but I guess most the time that's not a risk.

The timer:send_interval function does exactly what I need, without me needing to do additional work. (Outside of needing to sidestep the opaque type currently)
It's not clear to me how you use send_after to achieve the same thing, and after OTP 25, timer is pretty efficient to use: https://www.erlang.org/doc/efficiency_guide/commoncaveats#timer-module

You'd use send_after again when you receive the previous tick message.
It's not that the timer is expensive, it's that if you ever take too long to handle a tick message you end up with multiple tick messages in the inbox, potentially never managing to catch up resulting in the inbox growing. This then has performance implications and any other messages sent may have delay before they are handled. With send_after this failure mode is impossible.
We could add this function, but I think send_after is what you want for TUIs given the short interval and want to remain responsive even when under high load.

authors: erikareads lpil

repo: gleam-lang/erlang


text:
Parsing error with new @external syntax

The new updates seem to be working really well!  One spot where I'm seeing a parsing error is with @external.

It seems like the fn ... block is failing to parse, I'm guessing due to missing curly braces.  If I add those, it parses successfully, but I obviously then get a syntax error from gleam.
It seems like the function isn't nested below the attribute so I'm not sure how easy this would be to change.
Thank you!

Ah I see, function bodies can be optional with the attribute syntax. I think this should only take a small change to fix, I'll post a PR

authors: rawhat the-mikedavis

repo: gleam-lang/tree-sitter-gleam


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in eed89a1.

repo: glefait/martinique-public-websites


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 8799bdd after 8 minutes.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in ea6d5bf.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 3969486 after 4 minutes.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in e0ff0e4 after 10 minutes.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 4de5965 after 5 minutes.


text:
🛑 Saint-Joseph is down

In 168b8af, Saint-Joseph (https://saintjoseph972.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Saint-Joseph is back up in 3e70d20 after 5 minutes.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in fec1999.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in b53e4d6.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 1d32620.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 9242841.


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in e2a01f2.


text:
Two windows and glfwSetCursor

I have two windows. One is primary (window1) and second (window2) which share context with window1.
Then I try set different mouse cursor to window1 and window2.
pseudo code:
glfwSetCursor(window1.hwnd, HAND)
glfwSetCursor(window2.hwnd, HRESIZE)
If window1 has focus and mouse cursor is in window1 area, then cursor is HAND (correct).
But when I move cursor to window2 area (enter callback event icomming), then cursor is ARROW (bug). This is because window2 hasn't  focus. If click now and window2 got focus, cursor is changed to HRESIZE (ok).
Problem: Mouse cursor doesn't changed if is in window area which hasn't focus.
Windows7 x64
lwjgl3 (Nigthly - #3.0.0 build 72) + GLFW 3.2?

Oh, right, this was fixed in 3.2 with 2d2756cbadeae77d2648708f7b476e45849a8abc.

authors: NkD elmindreda

repo: glfw/glfw

license: Zlib


text:
Ignore/skip containers/services

Currently Registrator registers a service entry, with a backend, for every combination of docker-container + port that it discovers on the host. This can be far from desired behavior. There are very good reasons why we may want to skip certain containers, or certain ports for certain containers.
I think it would be super-helpful to have a -skip option that would take container name. Registrator would skip those. Ports can be indicated as: containername:port but that is much less critical requirement, IMHO.
Thanks

I think you can tell registrator to ignore your container entirely by setting -e SERVICE_IGNORE=anything as in service docs. I'm not sure if you're able to skip a port, however.

Chris,
thank you soooo much! I'd combed entire documentation but was unable to find this before your response. Adding SERVICE_IGNORE=always env variable to the launch script of the docker service that I needed to be hidden worked perfectly. Really appreciate your response.

authors: cwinters inadarei

repo: gliderlabs/registrator


text:
Preserve sorting order when changing column

Right now because of this code in onSort(column):
            if (currentSort.column === column) {
                currentSort.direction *= -1;
            } else {
                currentSort.column = column;
                currentSort.direction = 1;  // <----- this line
            }

The current sorting order isn't preserved.  Any objections to removing this line so that the order is preserved when the chosen column is changed?

This is a weird one, because for me this is actually expected behavior. I lean away, however, from making this a prop passed to the table, because of the inherent explosion of configuration. I'm going to need to sit on this for a bit (and also see if anyone else weighs in on this issue)

+1 for this to be configurable, I'd like to preserve the order as well.

+1

+1

authors: aminix astraldawn glittershark jamesaevans tsuna

repo: glittershark/reactable


text:
🛑 CMS is down

In 7c5c661, CMS ($SITE_4) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CMS is back up in ed99a00.

repo: glo-markoaular/status-navigate


text:
🛑 Redmine is down

In 10d55f1, Redmine ($SITE_3) was down:

HTTP code: 503
Response time: 33 ms

Resolved: Redmine is back up in cf7bfde after 2 days, 14 hours, 4 minutes.


text:
Creating ingredient from Accord

Saving or converting a formula to ingredients doesn't work if you have # in the name; let's say it's called revision #1. Then it will save, but the ingredients in the composition won't show up. Also, suppose you have yet to be successful, have done it several times, saved with the illegal symbols.. and deleted the newly created ingredient. In that case, it will show up several times as not deleted, so there must also be something conflicting with deletions. If it has signs in the name, that wont work... It would be nice not to have those limitations in naming conventions. I've experienced it with other symbols like" or 'etc...

This is happening as illegal characters are filtered out in ingredient management. Will update the list to filter only the strictly necessary chars.
Characters like ` and " will be filtered out.

That's unfortunate, because ' and " and # are used heavily.
Another thing is that creating ingrediets, sometimes let's say there is 17 ingredients in the accord and creating ingredients only 10 shows up in the composition tab...
So have to go through all accords concerted to ingredients and recreate...
. xblomx
On Jan 27, 2023, 13:50 +0100, John B @.***>, wrote:

This is happening as illegal characters are filtered out in ingredient management. Will update the list to filter only the strictly necessary chars.
Characters like ` and " will be filtered out.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

You will be able to use # though.
Please open a new issue providing full details as per guide as what you describing a different problem.

I will 👌
. xblomx
On Jan 27, 2023, 14:00 +0100, John B @.***>, wrote:

You will be able to use # though.
Please open a new issue providing full details as per guide as what you describing a different problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

authors: globaldyne xblomx

repo: globaldyne/parfumvault


text:
Make entrypoint more nuanced

Add a test command. Handle microcosm runserver commands. Add comments.

Approved.

authors: cdm-ium jessemyers

repo: globality-corp/docker-python-service


text:
Globalize-runtime has unsafe runtime-key hash function

The runtime key is generated from a JSON.stringify of the arguments (see here.
Problem is that JSON.stringify does not guarantee an order that the properties are stringified. See here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify
This already bit me once where formatters were called with the exact same properties but were stringified differently.  For example:
// Compile time
compile(Globalize.numberFormatter({
  minimumSignificantDigits: 1,
  maximumSignificantDigits: 3
}))

// Runtime
Globalize.numberFormatter({
  maximumSignificantDigits: 3,
  minimumSignificantDigits: 1
});

By making sure the properties are specified in the same order, it appears to work in the current browsers, but this is a bandaid because JSON.stringify is defined as unstable.
The solution is to use a stable hash of the arguments. Here's a fairly small, stable stringify: https://github.com/substack/json-stable-stringify. Or you can non-stringify hash.

#704 is related and may have the same solution

I ran into this issue as well a few months ago. According to this, the order should be stable as long as you create the object in the same way: http://2ality.com/2015/10/property-traversal-order-es6.html
So I did not open an issue at the time.
However, it might be a good idea to use json-stable-stringify to avoid mistakes like this and to avoid duplicating runtime formatters.
There's also another issue. These two are identical, but they produce two different hashes:
Globalize.numberFormatter();
Globalize.numberFormatter({style: 'decimal'});

because runtimeBind gets the original arguments as-is, e.g. here: https://github.com/globalizejs/globalize/blob/1.2.3/src/number.js#L75
I think the argument hashing happens here during compilation:
https://github.com/globalizejs/globalize/blob/1.2.3/src/common/runtime-bind.js#L8
The code you linked to is used during runtime to find the function. So it needs to be fixed in two places.

If someone works on a fix, we could include it in the upcoming 1.3.0... We need to evaluate different hash choices with respect to runtime and size footprint.

There's also another issue. These two are identical, but they produce two different hashes:

This can be solved similarly to dateFormatter https://github.com/globalizejs/globalize/blob/master/src/date-runtime.js#L38. In other words, the default options for numberFormatter needs to be fixed from {} to {style: 'decimal'} https://github.com/globalizejs/globalize/blob/master/src/number-runtime.js#L31.

json-stable-stringify requires jsonify if JSON doesn't exist . We could hack that out during the build.
There's also fast-stable-stringify: https://www.npmjs.com/package/fast-stable-stringify, which is faster, but it doesn't support replacer, which I used for the fix for #704, and it doesn't check circular references or toJSON methods (I don't know if those are needed).

I ran a benchmark on node:
Finished benchmarking: nickyout/fast-stable-stringify x 15,634 ops/sec ±0.75% (94 runs sampled) (cumulative string length: 221965828)
Finished benchmarking: substack/json-stable-stringify x 12,959 ops/sec ±0.80% (100 runs sampled) (cumulative string length: 190507028)
Finished benchmarking: JSON.stringify x 81,442 ops/sec ±0.23% (100 runs sampled) (cumulative string length: 1173618522)

I wrote a new benchmark to compare various options: https://github.com/nkovacs/stringify-benchmarks
I modified ppaskaris/faster-stable-stringify to support the replacer function. It's much slower in Chrome than in Node for some reason.
Node.js:
Finished benchmarking: JSON.stringify x 894,885 ops/sec ±1.33% (89 runs sampled) (cumulative string length: 298628380)
Finished benchmarking: nickyout/fast-stable-stringify x 652,594 ops/sec ±0.78% (94 runs sampled) (cumulative string length: 268121016)
Finished benchmarking: ppaskaris/faster-stable-stringify x 650,882 ops/sec ±1.33% (87 runs sampled) (cumulative string length: 81900725)
Finished benchmarking: nkovacs/faster-stable-stringify-2 x 613,162 ops/sec ±0.63% (94 runs sampled) (cumulative string length: 205904601)
Finished benchmarking: substack/json-stable-stringify x 495,164 ops/sec ±0.65% (96 runs sampled) (cumulative string length: 165384274)

Google Chrome:
Finished benchmarking: JSON.stringify x 854,869 ops/sec ±1.03% (59 runs sampled) (cumulative string length: 289429146)
bundle.js:22003 Finished benchmarking: nickyout/fast-stable-stringify x 776,384 ops/sec ±1.07% (62 runs sampled) (cumulative string length: 323719335)
bundle.js:22003 Finished benchmarking: ppaskaris/faster-stable-stringify x 658,560 ops/sec ±1.07% (61 runs sampled) (cumulative string length: 83453475)
bundle.js:22003 Finished benchmarking: nkovacs/faster-stable-stringify-2 x 545,758 ops/sec ±1.06% (61 runs sampled) (cumulative string length: 186746688)
bundle.js:22003 Finished benchmarking: substack/json-stable-stringify x 475,906 ops/sec ±1.58% (62 runs sampled) (cumulative string length: 163903373)

Thanks @nkovacs what about file sizes? I mean how much byes would we add to the library by using them? Thanks

This compresses down to 995 bytes with uglify.js.
However, maybe a full JSON.stringify isn't needed. All of these options objects have a simple, fixed structure, with no nested objects. So something like this could also work:
arr = [];
for (var key in options) {
    var val = options[key];
    if (typeof val === 'function') {
        val = val.runtimeKey;
    }
    arr.push(val);
}
JSON.stringify(arr);

Or you could just write them out, but this would be a maintenance burden:
JSON.stringify([options.minimumSignificantDigits, options.maximumSignificantDigits]);

authors: mattyork nkovacs rxaviers

repo: globalizejs/globalize


text:
Run mono-specific tasks only on mono

Fix #238.

This should no longer be necessary.

authors: KirillOsenkov iskiselev

repo: gluck/il-repack


text:
Simple voting

Description of proposed changes:
A new pallet "pallet-task-voting" with basic voting functionality. Still a rough draft.
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #821 (1f51e2d) into dev (2c25748) will decrease coverage by 0.12%.
The diff coverage is 15.00%.

@@            Coverage Diff             @@
##              dev     #821      +/-   ##
==========================================
- Coverage   78.24%   78.12%   -0.13%
==========================================
  Files          51       53       +2
  Lines       10317    10338      +21
==========================================
+ Hits         8073     8077       +4
- Misses       2244     2261      +17

Impacted Files
Coverage Δ

pallets/task-voting/src/mock.rs
13.33% <7.14%> (ø)

pallets/task-voting/src/lib.rs
33.33% <33.33%> (ø)

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

authors: codecov-commenter nathanwhit

repo: gluwa/creditcoin

license: Unlicense


text:
CSUB-396 mocked Staking runtime

Description of proposed changes:
Follow up on #871.
It includes a minimal Staking runtime to isolate unit tests and a single test for reference.
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #893 (acc4d93) into dev (2762f58) will decrease coverage by 2.86%.
The diff coverage is 11.31%.

@@            Coverage Diff             @@
##              dev     #893      +/-   ##
==========================================
- Coverage   78.11%   75.25%   -2.86%
==========================================
  Files          68       73       +5
  Lines       10768    11242     +474
==========================================
+ Hits         8411     8460      +49
- Misses       2357     2782     +425

Impacted Files
Coverage Δ

pallets/staking/src/pallet/impls.rs
0.00% <0.00%> (ø)

runtime/src/tests.rs
100.00% <ø> (ø)

pallets/staking/src/pallet/mod.rs
0.37% <0.38%> (ø)

pallets/staking/src/lib.rs
2.70% <14.28%> (ø)

pallets/staking/src/mock/runtime.rs
66.66% <50.00%> (ø)

pallets/staking/src/ledger.rs
58.82% <58.82%> (ø)

test/runtime-utils/src/lib.rs
100.00% <100.00%> (ø)

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