text:
Zonal statistics by group

Add a function for computing zonal statistics for integer image. For example, calculating the land cover composition of each country/state.

Implemented  in v0.6.4

repo: giswqs/geemap


text:
Allow ignoring specific git commits

Hello, I'm working with a TFS repository, and I'm the only one in my project who is using git-tfs. So I want to add a .gitignore file and maybe other commits, but I don't want to push those back up to TFS on my next git tfs checkin.
So as a hack to accomplish this, I:

Did a git tfs pull to fetch all TFS changesets, the latest became commit A.
Added another local commit B with my .gitignore.
Did a git rebase -i to reword A and B, removing the git-tfs-id info from commit message A and pasting it onto B, creating A' and B'
Edited .git/refs/remotes/tfs/mybranch to point to B' instead of A.
For good measure, I modified the "commits" note to change the filename from the hash of A to B' instead (and updated the note ref too)
Ran git tfs bootstrap just to be sure.

So I realize this might make some cringe, and there are already edge-cases discussed in #484 with .gitignore and ignored commits, but aside from that (I'm not too worried about .gitignore, I can work around if e.g. files come from TFS that are ignored) will this work?
More importantly, is a git tfs ignore <changeset...> command something that the maintainers would allow if I worked on something like this? (It seems to be just a more general case of the above mentioned issue)... Or is there already a better way to do this? I looked into git tfs reset-remote but that didn't seem to do what I needed.

I don't know if it will work and above all, I don't know if it worth the
effort.
Why don't you use a .gitignore file external to the repository added to
your .gitconfig file. It will do the job...

Ok, fair enough, I'll close the issue & maybe just post a gist somewhere in case anyone else needs it. External gitignore would be a good idea but I need to also change a couple config files and not have those changes push back up. (& yes I realize that could cause problems but I'll deal w/ those :)

Some doc on the subject here.

but I need to also change a couple config files and not have those changes push back up. (& yes I realize that could cause problems but I'll deal w/ those :)

Indeed, it's a bad pattern and you should normally have no "always modified" files in your working directory. A good practice is to ensure that special dev parameters are store in a special file not commited and ignored by your SCM!
If that's not possible (due to your team ;) ), you could use assume-unchanged if you are pretty sure that these files will (nearly) never change (because once they changed it nearly impossible to manage the merge :(
Or you could use something I described previously and which I worked with during more than one year : https://github.com/git-tfs/git-tfs/issues/577#issuecomment-41623946

Aaaahh I didn't know about assume-unchanged, that looks great! As long as I'm shooting myself in the foot I may as well do it in a supported manner ;)
Yes, these problems have to do with the rest of the team's SCM usage but hopefully I'll change that bit by bit! Thanks again for the pointers.

In fact, I just discovered that it's not assume-unchanged that must be used by another one,  skip-worktree:
http://stackoverflow.com/questions/13630849/git-difference-between-assume-unchanged-and-skip-worktree

@pmiossec Aaahh that's great to know too, there have been multiple times when I could have used that, thanks!

source: gharchive/issue

authors: irontoby pmiossec

repo: git-tfs/git-tfs

license_type: permissive

license_source: bigquery


text:
get v2 book list locally and add greek

The books'repos can now be located outside of progit2 organization.

Answering my own questions with some commits: yes, we can drop repo_name, and yes, the xref stuff was debugging cruft and we can drop similar appendix lines, too.

I also added in a link to the Greek translation from the book navbar (which for some reason exists in two near-identical files...?).
So I think it's good to go.

Thanks for all the fixes. Prepare to acces more languages, Some translators have been waiting for a while.

source: gharchive/pull-request

authors: jnavila peff

license: MIT

license_source: github-api


text:
initial implementation

a simple implementation of the pinata API that we can use in our local environment to avoid using the real API and being able to use it offline.
It's implemented in to have it simple and with just a couple dependencies.
Also, I don't think we will need to develop on top of it but it's just to have a service running from docker compose in our grants stack local dev env.
check the readme file for more info.

Can you elaborate on the go choice here? Are we planning on using the ipfs go libs more than the hash type? There was probably a discussion that I wasn't part of when i was out sick.

Can you elaborate on the go choice here? Are we planning on using the ipfs go libs more than the hash type? There was probably a discussion that I wasn't part of when i was out sick.

@vacekj  this is just the local service I use in development and since I notice everyone is using the real pinata service for development I decided to share it. I don't think we need to add features, it's just a development service we can use in local.

Are we planning on using the ipfs go libs more than the hash type?
the only sub packages included are go-multicodec and  go-multihash just to have the real CID instead of a simple hash, nothing else from the ipfs library is included. did you want to use more things?

@gravityblast re: first part - sounds good to me.
re: second part - I misread the code - nothing I would like to add personally, @bard asked about "forking the chain"-like funcitonality with real pinata, but personally I don't have a need for that.

@gravityblast re: first part - sounds good to me.
re: second part - I misread the code - nothing I would like to add personally, @bard asked about "forking the chain"-like funcitonality with real pinata, but personally I don't have a need for that.

I was referring to IPFS in general, i.e. wondering if at any point we're going to need IPFS resources outside of what is uploaded as part of a test setup, as it might be the case when trying to reproduce locally a production bug.

this is a good point, there's also the indexer to consider, how does the forking work with eth_getLogs? I would assume that the indexer would get events for the rounds in the forked chain, right?
if that's the case it would make sense to have this service behave the same as the node and "fork" Pinata, but another option could be just having the development environment not fork anything, so a pure offline set up.

I imagine the fork scenario with a different config.

development with one .env for local only services
staging like what we have now, with testnets and staging envs
fork as a mix, running anvil forking in local but using the real pinata to get real data

I don't think we will need a mixed environment but I'm happy to talk about it if you guys have any scenario in mind.

This is a good point, there's also the indexer to consider, how does the forking work with eth_getLogs? I would assume that the indexer would get events for the rounds in the forked chain, right? This means that the IPFS service should also serve those metadata.

yes it will need to get logs from the local chain, and files from past rounds/projects would be available in pinata.

Another option could be just having the development environment not fork anything, so a pure offline set up.

yes this is the current idea, but we can continue thinking about the forking scenario for specific tests we want to reproduce, but not really for development

authors: boudra gravityblast vacekj

repo: gitcoinco/pina


text:
🛑 yt.artemislena.eu is down

In 7beb535, yt.artemislena.eu (https://yt.artemislena.eu/) was down:

HTTP code: 502
Response time: 5595 ms

Resolved: yt.artemislena.eu is back up in 1c3a5e2.

repo: gitetsu/invidious-instances-upptime


text:
🛑 invidious.privacydev.net is down

In e17163f, invidious.privacydev.net (https://invidious.privacydev.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: invidious.privacydev.net is back up in fdf509b.


text:
🛑 inv.odyssey346.dev is down

In 40836ab, inv.odyssey346.dev (https://inv.odyssey346.dev/) was down:

HTTP code: 502
Response time: 413 ms

Resolved: inv.odyssey346.dev is back up in d7e5a77.


text:
🛑 invidious.kavin.rocks is down

In e67eae5, invidious.kavin.rocks (https://invidious.kavin.rocks/) was down:

HTTP code: 502
Response time: 10454 ms

Resolved: invidious.kavin.rocks is back up in 06249a8.


text:
🛑 search.dr460nf1r3.org is down

In 4f797de, search.dr460nf1r3.org (https://search.dr460nf1r3.org) was down:

HTTP code: 523
Response time: 3295 ms

Resolved: search.dr460nf1r3.org is back up in 8a9014a.

repo: gitetsu/whoogle-instances-upptime


text:
Environment-specific locks

Would be nice if we could toggle sticky locks for specific environments by providing the environment name after the trigger, such as  .lock staging & .unlock development. Then the lock should only affect deployments to the locked environment, so that I could lock a branch to staging, but still deploy to development. A universal lock could still be applied by omitting the environment parameter.
Additionally, it'd be nice to have an action with an environment option that checks if a lock exists. This way we could use these locks when triggering deployments via other methods such as pushes to the main branch.
Something with a pattern like:
- name: lock-exists
  id: lock-exists
  uses: github/lock-exists
  with:
    environment: development

- name: deploy
  if: ${{ steps.lock-exists.outputs.exists == 'false' }}
  # deployment script, etc

Basically, I'm looking to deploy to all environments on pushes to main by default, but omit the deploys to development and staging when they're locked.

@necropolina Thank you for the suggestion! This is a great feature request. I already have a standalone Action that works together with the github/branch-deploy Action.
This standalone Action is called github/lock and is used to claim or remove locks in a headless manner. However, I should absolutely add a check-only: true flag to it so that it can be used  to "check" if deployment locks exist.

So this issue seems like a two part request:

Add a feature to the github/lock Action so that we can simply "check" if a lock exists or not
Adapt the code in the github/branch-deploy Action so that deployments and lock can optionally be targeted to a specific environment (at the user's discretion) while leaving other envs available for deployments

@necropolina You can now check if a lock exists with this latest release -> https://github.com/github/lock/releases/tag/v1.1.0

Looks like solid solutions to me! Thanks for hopping on this so quickly!!!

Hi, it looks like the request 1 was already fulfilled, but no. 2 still missing.
Are you planning to add this feature to this action? Blocking deployments to the development environment while prod deployment is in effect seems like too much of an hassle.

@puilp0502 it is absolutely something we still plan on adding. It will require a decent refactor of code so something I plan on doing at some point when time is available

@necropolina + @puilp0502 You will be very exited to know that I have begun work on this feature and it has already come along nicely. Stay tuned! 📺

authors: GrantBirki necropolina puilp0502

repo: github/branch-deploy


text:
Added links to public-domain-like licenses as one of the ways to contribute to abolition of copyright.

Why:
Because I feel like it should be added.
What's being changed:
Added a paragraph about usage of public-domain-like licenses as a way to reduce count of projects under copyright.
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
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

👋 @KOLANICH Thanks for opening a PR! We don't make changes to the site policy docs in this repo, but you can check out the CONTRIBUTING guide in the site-policy repo ✨

authors: KOLANICH janiceilene

repo: github/docs


text:
Rename content/search-github/searching-on-github/searching-issues-and…

…-pull-requests.md to Nour mathlothi

Why:
Closes [issue link]

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")

Ok
Le lun. 17 janv. 2022 à 22:13, github-actions[bot] @.***>
a écrit :

Automatically generated comment ℹ
This comment is automatically generated and will be overwritten every
time changes are committed to this branch.
The table contains an overview of files in the content directory that
have been changed in this pull request. It's provided to make it easy to
review your changes on the staging site. Please note that changes to the
data directory will not show up in this table.
Content directory changes
You may find it useful to copy this table into the pull request summary.
There you can edit it to share links to important articles or changes and
to give a high-level overview of how the changes in your pull request
support the overall goals of the pull request.
Source Staging Production What Changed
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/14214#issuecomment-1014889355, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHNA7BEQNKKG4A65ZIRD2LUWSA73ANCNFSM5MFS3IXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


text:
Update Keyboard Shortcuts

Keyboard shortcuts changed in accordance with the GitHub Content Style Guide
Why:
Closes #13905

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

After

Check off the following:

[x ] 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).
[ x] 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")

@nawed2611 Thanks so much for opening a PR! I'll get this triaged for review :zap:

Thanks @nawed2611 ✨  I'll get it merged once the tests have passed 🍏


text:
chore: Only run freeze reminder on internal repo

Why:

Shouldn't affect forks or the public repo, but I'm guessing this will start triggering double notifications running on the public and private repo on the same cron schedule. The env.FREEZE check could probably be hoisted here too
What's being changed:

Check off the following:

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

I appreciate the critical eye and the contribution! 🙇🏻♂ 💝
FWIW, I intentionally left this out when I created it to ensure we remembered to unfreeze both repos when the time came. We can try it this way and hopefully it works out as well. 😅

@JamesMGreene fair enough, I figured it would more be noise in the slack channel, but feel free to revert as I can see it might catch only clearing the variable in one repo :)

authors: JamesMGreene nschonni


text:
Audit of circle-ci returns No source pipelines found

I assume this was part of the underlying issue with #87.
# Logfile created on 2023-03-16 18:37:34 +0000 by logger.rb/v1.5.3
I, [2023-03-16T18:37:34.676003 #1]  INFO -- : Using GitHub Features: 'all'
I, [2023-03-16T18:37:34.676181 #1]  INFO -- : Auditing 'https://app.circleci.com/pipelines/github/myorg'
I, [2023-03-16T18:37:34.686816 #1]  INFO -- request: GET https://api.github.com/orgs/myorg/repos?per_page=100
I, [2023-03-16T18:37:35.908294 #1]  INFO -- response: Status 200
W, [2023-03-16T18:37:35.910803 #1]  WARN -- : No source pipelines found
I, [2023-03-16T18:37:35.911423 #1]  INFO -- : Sending telemetry with transaction id '543ebfe8-9ab6-41dd-b1cc-9a93dd47f00f'

@cdhunt can you please file an issue at support.github.com to look into this? Going through GitHub Support is the best way to get help related to GitHub Actions Importer.

authors: cdhunt ethanis

repo: github/gh-actions-importer


text:
ignore .DS_Store file in MacOS platform.

Reasons for making this change:
.DS_Store is a Mac-specific hidden file. It's also not something that you generally want to add to source control, as its contents may change without you necessarily interacting with it.
Links to documentation supporting these rule changes:
Wikipedia introduce info
stackoverflow data

Thanks, but see Global\macOS.gitignore

authors: light-bo shiftkey

repo: github/gitignore


text:
Added git ignore for C#

Reasons for making this change:
I feel like the C# language deserves an official gitignore available on the platform

Looks a lot like VisualStudio.gitignore plus a few other things ( Global/Windows.gitignore, Global/mscOS.gitignore, Global/JetBrains.gitignore, Global/Vim.gitignore, Global/SVN.gitignore, Global/CVS.gitignore, Node.gitignore, Sass.gitignore ). This repo tries to be modular, so that everybody can pick a combination of gitignores that fits the current projects needs. If they would add a lot of redundant rules to multiple gitignore files, the repo would become unmaintainable.
If you feel that the existing gitignore-modules could be improved, feel free to open individual PRs for those modules.
PS.: Personally I like to use gitignore.io to create combined gitignore files for my projects.

@LvInSaNevL thanks for the contribution. For the moment I want to keep VisualStudio.gitignore as the canonical template, and I've had some requests for a .NET-like template that's simpler to manage, which I summarized in an earlier discussion https://github.com/github/gitignore/pull/2989#issuecomment-471509901

the last time this came up I wanted to call out that there's a lot of non-.NET technologies inside the VisualStudio template, and suggested a different approach #2816 (comment)

What if we went a slightly different approach:

DotNet.gitignore - a new template fresh with whatever current .NET requires (leaner)
Global/VisualStudio.gitignore - the current template, moved alongside the other IDEs

Thoughts?

authors: LvInSaNevL drothmaler shiftkey


text:
improvements needed for making a command-line tool

See #82 for history.  /cc @mislav

@atmos: OptParse doesn't seem to at all support the --. Doing it manually is ugly but seems the only way.

Is it worth ditching this pull request, and trying to start over using the new adapter API? /cc @atmos

authors: atmos mislav tombell

repo: github/hubot

license: mit


text:
Optionally use setImmediate instead of nextTick in middleware

When upgrading from node 0.8 to 0.10, we were failing with errors like this:
... snip ...
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.

node.js:0
// Copyright Joyent, Inc. and other Node contributors.
^
RangeError: Maximum call stack size exceeded

This uses setImmediate instead of nextTick if available, allowing our hubot to boot.
cc @technicalpickles

Maybe this would be better on Robot than middleware? There's stuff in listener using it too.

Maybe this would be better on Robot than middleware? There's stuff in listener using it too.

nextTick is not deprecated entirely, only when used recursively. That's how we use it in middleware. I got the use case in listener that's recursive and left the other one alone.

Sounds good then :+1:

Hmm.. the docs recommend using process.nextTick if you are async-ifying a function: https://nodejs.org/api/process.html#process_process_nexttick_callback_arg
The reason the warning is there is because the behavior changed from "after I/O" to "before I/O" in 0.10. I think we are okay with blocking I/O here, so that warning is noise. I wonder if it got removed in later versions...

The reason the warning is there is because the behavior changed from "after I/O" to "before I/O" in 0.10.

Not just that. nextTick was officially deprecated in recursive contexts, which our middleware turns out to be. We still have a few other nextTicks that are fine; only the ones done in the middleware's inner loop are bad. Ctrl-f for 'recursive' in https://github.com/nodejs/node/wiki/API-changes-between-v0.8-and-v0.10.
I'm going to release 2.17 without this. We haven't been running it and I want to do our upgrade internally before the rest of the world tests it extensively.

We've been using this for about a week and no catastrophes have popped up. Any objections to merging it?

We've been using this for awhile without problem, so it's good to merge & release.

authors: bhuga michaelansel technicalpickles


text:
Syntax Highlighting support for Svelte.

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
Syntax Highlighting isn't supported for Svelte.
URL of the affected repository:
Last modified on:
2018-11-11
Expected language:
Svelte
Detected language:
None

Please have a look at the guidelines to add support for a new language to Linguist. It Svelte meets the requirement on in-the-wild usage, we'd welcome a pull request!
In the meantime, we can't keep issues open for every languages we don't support---especially considering that we often don't have the expertise to add those languages ourselves---, so I'm going to close this.

When I search for the .svelte filename, I get 2,400 results right now. @pchaigno is that enough for a PR? Happy to take a crack at it if so.

I worked on #4323 some time ago. Will update and resolve comments now.

When I search for the .svelte filename, I get 2,400 results right now. @pchaigno is that enough for a PR? Happy to take a crack at it if so.

That search query returns 0 .svelte and 14 svelte files. Unless you had something else in mind than adding one of these filenames, I don't think that's enough to mandate support in Linguist.

Oops, posted the wrong url. This is the one that has those results. Is there some other way you do the searches for this? That url is copied from the contributing doc, replacing the extension from that with svelte. My previous link returns over 600 repositories.

Seems we still need to add .svelte support!

Seems we still need to add .svelte support!

Yup, but it's still not popular enough to meet the "each new file extension be in use in hundreds of repositories before supporting them in Linguist" requirement:
Total files found: 4372
Unique public user/repos: 171
Unique owners: 138

@lildude That's because this extension just becomes with Svelte 3 Beta. So in the near future, the number of packages will increase exponentially. And it would be nice if GitHub will be ready for that and its users won't feel pain reading a source.

I agree, it would be nice, but then we'd need to do the same for every language that purports "future exponential growth".  This is why we have https://github.com/github/linguist/issues/4219

@lildude Svelte is missing from the list in #4219. Can we get this added?

@lildude Please check this results.
Is it not enough to be recognired as hundreds of repositories? I've check most of this pages and its all about SvelteJS.

Is it not enough to be recognired as hundreds of repositories?

@PaulMaly please see my tally of those results https://github.com/github/linguist/issues/4321#issuecomment-481166191
The total currently sits as "tens" and not "hundreds" (cos 171 is only 1 "hundred" and 70 "tens" 😉).

@lildude Svelte is missing from the list in #4219. Can we get this added?

Sure. @pchaigno manages that issue so I'll leave it to him to add when he's got the chance.

@lildude Where we can check these numbers? Could you please provide a link to search results or something similar?

Unfortunately, I can't share the script I use as it abuses the API to the extent non-staff users would be blocked. https://github.com/Alhadis/Harvester is a browser-based alternative that does pretty much the same thing, but scrapes the search results as you see it and doesn't use the API. The results may vary slightly, but should be pretty similar.

@lildude After quick research using the tool you provided, I've got these results:
Unique entries:  686

My script below:

const results = `<results string>`;

const entries = results.split('\n').map(item => {
    const [user, repo, ...others] = item.replace(/^(?:\/\/|[^\/]+)*\//, '').split('/');
    return `${user}/${repo}`;
});

const uniqueEntries = new Set(entries);

console.log('Unique entries: ', uniqueEntries.size);

What am I doing wrong?

I have not idea as I get:
Unique entries:  187

... which also matches what I get if I do it from the CLI as per https://github.com/Alhadis/Harvester#helpful-scripts:
$ grep < svelte.log -iEoe '^https?://raw\.githubusercontent\.com/([^/]+/){2}' \
| sort | uniq | sed -Ee 's,raw\.(github)usercontent,\1,g' | wc -l
     187
$ grep < svelte.log -iEoe '^https?://raw\.githubusercontent\.com/([^/]+/){2}' \
| sort | uniq | sed -Ee 's,raw\.(github)usercontent,\1,g' > unique-repos.log
$ grep < unique-repos.log -oE '^https://github\.com\/[^/]+' \
| sort | uniq > unique-users.log
$ wc -l unique-{repos,users}.log | grep -vE '\stotal$' | grep -oE '^\s*[0-9]+' |\
xargs printf '\
Unique repos: %s
Unique users: %s
'

Unique repos: 187
Unique users: 152

At a guess, I'd say your list of results varies from mine for some reason.

@lildude Hm, strange but this proves that this method is insufficiently exact. Anyway, if we have 187 repos which is 1 "hundred" and 87 "tens" do we need just 13 additional repos to become 2 hundred and hundreds of repositories, right? I think I can create them for statistic purposes. 😄

@lildude I'm glad that you have a sense of humor because I don't know people who would fake popularity markup. 😉
But the main point we try to inform you that Svelte much more popular than these numbers can show us because custom extension .svelte was not mainstream until Svelte 3. Even now Svelte 3 still in beta. So, before that, we used .html for Svelte component and GitHub really may have hundreds of repositories with these files. But even when Svelte 3 is come up and all that repos will upgrade for new version there's no reason to use .svelte with v3 if they already use .html, because .svelte is not mandatory but, in too time, has no highlighting support.
Therefore we've got a two-edged sword: 1) if we'll not to add .svelte support not many repos will switch to this expression; 2) if we haven't many repos with this extension we'll never add its support;
In all cases, GitHub users will most of all suffer, because they will be faced with many fake .html files which actually is Svelte components (basic html highlighting is not good for that) or with many unsupported .svelte with no highlighting at all.
I really hope you take the idea.

@lildude I'm glad that you have a sense of humor because I don't know people who would fake popularity markup. 😉

I do, for both 😁

So, before that, we used .html for Svelte components and GitHub really may have hundreds of repositories with these files.

If there's something particularly unique about Svelte in .html files that we can easily search for with GitHub's limited search (the more unique the keyword, the better) and can be used to differentiate from normal HTML (the only language .html is associated with at the mo) then that's certainly an option. ie add Svelte support for only the .html extension (as as you say this should already be really popular) with a heuristic to differentiate it from normal HTML.
All repos that use .svelte can then implement an override to get recognition of that extension until such time as the extension is popular enough in its own right.
This might actually be the best solution to cover current Svelte users and those eager to jump on the beta 🚌 .

@lildude Thank you for trying to help us! Could you please describe this option more detailed?
If I got the idea correctly, we can add additional highlighting support for Svelte expressions to .html files and somehow (maybe via .gitattributes) force GitHub to recognize .svelte files as .html files with this syntax support? Am I right?

The idea is you add a new language as per https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language with the only extension being .html.
Add a heuristic to https://github.com/github/linguist/blob/master/lib/linguist/heuristics.yml the differentiates normal HTML from Svelte.
You'll need to add tests and samples too - all documented.
Then, when the next Linguist release is made after the PR has been merged, Svelte users will be able to add something like this to their .gitattributes file in their repos:
*.svelte linguist-language=svelte

All those .svelte files will now be identified as Svelte and will use the Svelte grammar for syntax highlighting.
If there isn't an easy way to differentiate between Svelte and normal HTML without accidentally misclassifying a load of other files, eg HTML with embedded JavaScript (I'm guessing here based on a quick look at the Svelte language), then the only option would be to wait for .svelte popularity to increase and then use the .svelte as the sole extension for the language. Once the PR has been merged, the same override can be done for .html to mark them as Svelte, ie:
*.html linguist-language=svelte

Using Harvester, I found 172 repositories by 141 users on 2236 files collected. Since there are actually 4k files (the search results limit us to ~1k files per sorting option, with duplicates), I think it's fine to assume .svelte has reached the hundreds of repositories threshold. @lildude What do you think?

Using Harvester, I found 172 repositories by 141 users on 2236 files collected. Since there are actually 4k files (the search results limit us to ~1k files per sorting option, with duplicates), I think it's fine to assume .svelte has reached the hundreds of repositories threshold. @lildude What do you think?

🤦♂ of course. I completely missed the 4k files. If we assume the next 3000 results are similar to the first 1000, I think we can safely say .svelte meets the requirements.
@PaulMaly @umanghome feel free to open a PR to add support.

PR: #4504.

@lildude @pchaigno Can we assign reviewers to #4504?

authors: PaulMaly bdougherty lildude pchaigno umanghome

repo: github/linguist


text:
Wrong language detected

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description

Only one html file included in test/resources for unit test, but it seems like a lot of html code is detected
URL of the affected repository:
https://github.com/YuanWenqing/product
Last modified on:

2019-02-22
Expected language:

java
Detected language:

Java 55.2%	 HTML 44.8%

Only one html file included in test/resources for unit test, but it seems like a lot of html code is detected

Your repo is private so I can't check, but the likely cause is the size of that test file. As "How Linguist Works" in the README states (and you've acknowledged reading 😉):

The percentages are calculated based on the bytes of code for each language as reported by the List Languages API.

So if that one file is nearly as large as all your Java combined, the stats will show it having a high proportion. If you don't want this, you'll need write more Java to use an override.

I already added a .gitattributes file, but nothing changed

What did you put in your file? Remember, we can't see your repo so you need to be very clear about what you've done.

Finally, I rename the html file as a txt file. Now everything seems fine.
Thanks!!

The real solution is to put something like this in your .gitattributes file:
*.html -linguist-detectable

That prevents linguist from considering html files (the minus sign indicates NOT linguist-detectable).
For generated files (does not seem to apply here), the more accurate option would be: *.html linguist-generated
For more overrides, see https://github.com/github/linguist#overrides

authors: YuanWenqing lildude poikilos


text:
Define TextMate grammar scope for Turing

I was clearly too busy cracking witty puns in #3052 to notice I'd forgotten to include the tm_scope attribute for Turing (thanks @pchaigno. I've had smoother moments).

I was clearly too busy cracking witty puns in #3052 to notice I'd forgotten to include the tm_scope attribute for Turing

😆

:stuck_out_tongue_closed_eyes:

authors: Alhadis arfon pchaigno


text:
Add Open Source Galaxy to how-to-contribute.md

I would love to add Open Source Galaxy to the list of resources for finding and discovering open source projects.
It's an extremely user-friendly resource that helps users find issues by popular languages and labels. It also applies a special indicator/icon to issues that are less than an hour old, which is great for busy seasons like Hacktoberfest.
Thanks in advance for your time and consideration.

Passing on this, sorry. See:

Please don't add references or links to things you or your employer have created as others will do so if they appreciate it.
https://github.com/github/opensource.guide/blob/master/CONTRIBUTING.md

authors: MikeMcQuaid justinjunodev


text:
Test 1 - update

Edited

new comment

repo: githubabcs/gh-abcs-actions-training


text:
Group share with another group fails on a second run

The bug description
There is an awesome new feature to add a group as a member to another group.
Added in #233 by fantastic @andrewjw
Unfortunately it fails to recognise existing shares (created manually or by GitLabForm itself).
Steps to reproduce:

Create config with a group as another group member
Run GitLabForm (a successful run)
Run GitLabForm again (it fails)

Anonymized error:
Warning: Error occurred while processing group groupb, exception:
Request url='https://gitlab.example.com/api/v4/groups/groupb/share', method=POST, data='{'group_id': 28, 'expires_at': None, 'group_access': 40}' failed - expected code(s) [200, 201], got code 409 & body: 'b'{"message":"Shared group The group has already been shared with this group"}''
Traceback (most recent call last):
  File "/gitlabform/gitlabform/gitlabform/core.py", line 466, in process_all
    self.group_processors.process_group(
  File "/gitlabform/gitlabform/gitlabform/processors/group/__init__.py", line 36, in process_group
    processor.process(group, configuration, dry_run, output_file)
  File "/gitlabform/gitlabform/gitlabform/processors/util/decorators.py", line 42, in method_wrapper
    return method(self, project_and_group, SafeDict(configuration), *args)
  File "/gitlabform/gitlabform/gitlabform/processors/abstract_processor.py", line 47, in process
    self._process_configuration(project_or_project_and_group, configuration)
  File "/gitlabform/gitlabform/gitlabform/processors/group/group_shared_with_processor.py", line 81, in _process_configuration
    self.gitlab.add_share_to_group(
  File "/gitlabform/gitlabform/gitlab/groups.py", line 180, in add_share_to_group
    return self._make_requests_to_api(
  File "/gitlabform/gitlabform/gitlab/core.py", line 111, in _make_requests_to_api
    response = self._make_request_to_api(
  File "/gitlabform/gitlabform/gitlab/core.py", line 210, in _make_request_to_api
    raise UnexpectedResponseException(
gitlabform.gitlab.core.UnexpectedResponseException: Request url='https://gitlab.example.com/api/v4/groups/groupb/share', method=POST, data='{'group_id': 28, 'expires_at': None, 'group_access': 40}' failed - expected code(s) [200, 201], got code 409 & body: 'b'{"message":"Shared group The group has already been shared with this group"}''

There is a check in code that should end up with "Nothing to change for group '%s' - same config now as to set.",, but it seems to be not working for some reason.
GitLabForm version
🏗  GitLabForm version: 2.1.0 = the latest stable 😊
GitLab version
14.0.1

Debug logs show:
Group shared with BEFORE: [{'group_id': 28, 'group_name': 'Groupa', 'group_full_path': 'groupa', 'group_access_level': 40, 'expires_at': None}]
Adding group 'groupa' who previously was not a member.

Notice the register.
Looks like gitlabform/gitlabform/gitlabform/processors/group/group_shared_with_processor.py uses names to figure out weather group needs updating or not. I'd suggest to switch to the group_full_path.
I'll try to make a local change to see if works any better.

Hi,
I wasn't able to reproduce this, but I agree much better to use path than name. Were any of your groups subgroups? I've created a PR #237 which adds support for subgroups.
Thanks,
Andrew

Actually, I have managed to reproduce it now. Hopefully I'll have a fix soon 😄

I've confirmed that this is caused when you have a name that has non-url safe character in it (e.g. a space replaced by a hyphen in the path). This is fixed by #237.
Cheers,
Andrew

@andrewjw you're pure speed!
Thanks!

Regular 2.1.1 with this fixed has been (finally) releases today. Please reopen this ticket if it doesn’t fix your issue, @ejiek .
Thanks again for the PR, @andrewjw ! 😊

Works like a charm =]
@andrewjw, @gdubicki, thanks!

Got the same issue in 2.2.0:
$ gitlabform -c test-config.yml ei/scm/scm-test-zone
🏗  GitLabForm version: 2.2.0 = the latest stable 😊
:: # of groups to process: 1
:: # of projects to process: 2
@ (1/1) Processing group: ei/scm/scm-test-zone
Warning: Error occurred while processing group ei/scm/scm-test-zone, exception:
Request url='https://my.gitlab.server//api/v4/groups/ei%2Fscm%2Fscm-test-zone/share', method=POST, data={'group_id': 4095, 'expires_at': None, 'group_access': 30} failed - expected code(s) [200, 201], got code 409 & body: 'b'{"message":"Shared group The group has already been shared with this group"}''
Traceback (most recent call last):
  File "/gitlabform/gitlabform/core.py", line 339, in run
    self.group_processors.process_group(
  File "/gitlabform/gitlabform/processors/group/__init__.py", line 46, in process_group
    processor.process(group, configuration, dry_run, effective_configuration)
  File "/gitlabform/gitlabform/processors/util/decorators.py", line 42, in method_wrapper
    return method(self, project_and_group, SafeDict(configuration), *args)
  File "/gitlabform/gitlabform/processors/abstract_processor.py", line 46, in process
    self._process_configuration(project_or_project_and_group, configuration)
  File "/gitlabform/gitlabform/processors/group/group_shared_with_processor.py", line 77, in _process_configuration
    self.gitlab.add_share_to_group(
  File "/gitlabform/gitlabform/gitlab/groups.py", line 166, in add_share_to_group
    return self._make_requests_to_api(
  File "/gitlabform/gitlabform/gitlab/core.py", line 125, in _make_requests_to_api
    response = self._make_request_to_api(
  File "/gitlabform/gitlabform/gitlab/core.py", line 221, in _make_request_to_api
    raise UnexpectedResponseException(
gitlabform.gitlab.core.UnexpectedResponseException: Request url='https://my.gitlab.server//api/v4/groups/ei%2Fscm%2Fscm-test-zone/share', method=POST, data={'group_id': 4095, 'expires_at': None, 'group_access': 30} failed - expected code(s) [200, 201], got code 409 & body: 'b'{"message":"Shared group The group has already been shared with this group"}''

The config snippet:
projects_and_groups:

  # settings for ALL projects in 'scm-test-zone' group
  "ei/scm/scm-test-zone/*":

    group_shared_with:
      ei/reviewers/helm:
        group_access_level: 30

Do you also observe the issue on the second run only, @aleung ? If so, then I was not reproduce it easily yet, see commit above...

Can you please check this again with v2.8.0 released a moment ago, @aleung ? The implementation for sharing group with groups has changed a bit there.

I ran into this issue and found the problem was that I was using the Group name rather than the path. The name was something like "group-Name" and had capitals while the path was more like "group-name" and did not. GitLabForm should fail on the first run if sharing a group by name rather than path, but it can be easily mitigated by always using the path.

For whatever it's worth: I get the error with version 3.8.0 on the second run, even if I use paths.
I have
group/sub-group/sub-sub-group:
  group_members:
    groups:
      group/sub-group/another-sub-group:
        group_access: developer
  enforce: true
  keep_bots: false

The first run succeeds, the second run fails to do any updates to sub-sub-group with:
Request url='https://my.gitlab.host.url/api/v4/groups/group%2Fsub-group%2Fsub-sub-group/share', method=POST, data='{"expires_at": null, "group_access": 30, "group_id": 1111}' failed - expected code(s) [200, 201], got code 409 & body: '{"message":"Shared group The group has already been shared with this group"}'

What I mean with "any updates" is that if it has multiple another-sub-group-1, another-sub-group-2 it will fail. Also the enforcement fails, i.e., superflous shares aren't deleted (logically).

Maybe this will be fixed when https://github.com/gitlabform/gitlabform/issues/633 has been done. Would anyone be able to help with that?

authors: AFulgens aleung amimas andrewjw ejiek ejiektpobehuk gdubicki scott-kausler

repo: gitlabform/gitlabform


text:
[Bug] - Duplicate Pipeline schedules

Describe the bug
We have a GitLab project, and the pipeline of this project needs to run once a day in order to achieve a defined task. In order to achieve daily runs we are using Scheduled pipelines (Gitlabform Pipeline schedules).
With the following configuration, every time the pipeline runs, it creates a new schedule every 2nd time
some-project:

    # Periodic execution Schedule
    schedules:
        "Daily":
            description: "Execute Pipeline daily, to avoid configuration divergence"
             ref: main
             cron: 0 3 * * * # Daily at 3:00 AM
             active: true

Observation,

First Run: Schedule created with Description Daily
Second Run: Schedule updated with Description Execute Pipeline daily, to avoid configuration divergence
Total Schedules: 1

Third Run: Schedule created with Description Daily
Fourth Run: Schedule updated with Description Execute Pipeline daily, to avoid configuration divergence
Total Schedules: 2

Working Fix
Schedules works as expected after changing the configuration to (description attribute has been removed) :
some-project:

    # Periodic execution Schedule
    schedules:
        "Daily":
             ref: main
             cron: 0 3 * * * # Daily at 3:00 AM
             active: true

GitLabForm version
🏗 GitLabForm version: 3.5.0 = the latest stable 😊
GitLab version
GitLab Enterprise Edition 15.8.0-ee
Credits:
Working fix provided by (Removing description attribute) - Aver Mimas (@amimas)

Yes I agree @gdubicki 😊|


text:
🛑 MSP-002 is down

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

HTTP code: 0
Response time: 0 ms

Resolved: MSP-002 is back up in 97714a5.

repo: gitsrc/upptime


text:
🛑 Give Food API 1 food banks dump is down

In 9e38115, Give Food API 1 food banks dump (https://www.givefood.org.uk/api/1/foodbanks/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Give Food API 1 food banks dump is back up in dbaf34c.

repo: givefood/upptime


text:
Feat: Identity

Implement Identity operator.

Can i take this one?

repo: gizatechxyz/orion


text:
Add CodeMirror6Editor

First attempt at #6

I get an error when trying to build:
[webpack-cli] Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at BulkUpdateDecorator.hashFactory (/home/owen/projects/personal/firenvim/node_modules/webpack/lib/util/createHash.js:155:18)
    at BulkUpdateDecorator.digest (/home/owen/projects/personal/firenvim/node_modules/webpack/lib/util/createHash.js:80:21)
    at /home/owen/projects/personal/firenvim/node_modules/webpack/lib/DefinePlugin.js:595:38
    at _next27 (eval at create (/home/owen/projects/personal/firenvim/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:44:1)
    at _next5 (eval at create (/home/owen/projects/personal/firenvim/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:97:1)
    at Hook.eval [as call] (eval at create (/home/owen/projects/personal/firenvim/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:111:1)
    at Hook.CALL_DELEGATE [as _call] (/home/owen/projects/personal/firenvim/node_modules/tapable/lib/Hook.js:14:14)
    at Compiler.newCompilation (/home/owen/projects/personal/firenvim/node_modules/webpack/lib/Compiler.js:1053:26) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Building with docker works fine.

build issue fixed with NODE_OPTIONS as per this SO question: https://stackoverflow.com/questions/69394632/webpack-build-failing-with-err-ossl-evp-unsupported

and it's working fine for me - vivaldi browser, in case that makes any difference

Oh, indeed, it does seem to work in chrome-based browser, it's only Firefox that doesn't work :thinking: .

You did the work to get CodeMirror6 to work for your usecase, I won't force you to make it work for other people. I've added a commit that makes CodeMirror6 optional and will make Firenvim enable it when running in Chrome.
Thanks again for your contribution! :)

Thank you! That gers my workflow back how I like it!
I have an idea for getting the language out of codemirror 6. I'll try it out today and submit a PR if it works out.

authors: glacambre meatballs

repo: glacambre/editor-adapter


text:
update with the influxdata/influxdb-python master

This pull request update the repo with the influxdata/influxdb-python master

I guess you have the wrong target, you probably want your merge to be in influxdata/influxdb-python :)

authors: fradaloisio gladhorn

repo: gladhorn/influxdb-python


text:
Make position sampling tile-able

Instead of supporting only the fixed-size batching that is currently implemented in positions_from_delta(), it would be useful if more general tiling schemes could be supported.

This is probably more difficult than it first looked, because the tiling of real surveys has nontrivial overlapping patterns, and the requisite logic to assign points to each makes the sampling very complicated. It might not be worth it to implement this in the sampling.

repo: glass-dev/glass


text:
Glassfy Expo install with EAS build crashes immediately

I have tried the EAS dev build after installing Glassfy, similar to other packages which impact non-native modules. After building, when trying to launch, it crashes immediately.
Expo-doctor has no issues listed.
Is Glassfy supported in an Expo project?
Any ideas?
I am on MacOS 14.0 (23A344)
"react-native-glassfy-module": "^1.5.3",
"expo": "~48.0.21",
"react-native": "0.71.14",
Based on local prebuild, which also crashes, here is terminal output:
[CoreFoundation] *** Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason: 'You must override the
`supportedEvents` method of GlassfyModule'
*** First throw call stack:
(
0   CoreFoundation                      0x00000001090608a8 __exceptionPreprocess
+ 172
1   libobjc.A.dylib                     0x00000001045fc09c objc_exception_throw
+ 56
2   Foundation                          0x0000000106b38b90
-[NSMutableDictionary(NSMutableDictionary) classForCoder] + 0
3   IdentaFlyDev                        0x0000000100ddf974 +[RCTEventEmitter
initialize] + 300
4   libobjc.A.dylib                     0x00000001045d7c4c
CALLING_SOME_+initialize_METHOD + 20
5   libobjc.A.dylib                     0x00000001045d892c
initializeNonMetaClass + 520
6   libobjc.A.dylib                     0x00000001045db2b4
_ZL24initializeAndMaybeRelockP10objc_classP11objc_objectR12locker_mixinIN9lockdebug10lock_mixinI16objc_lock_base_tEEEb
+ 200
7   libobjc.A.dylib                     0x00000001045ecf70 lookUp<…>
[CoreFoundation] *** Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason: 'You must override the
`supportedEvents` method of GlassfyModule'
*** First throw call stack:
(
0   CoreFoundation                      0x000000010d2708a8 __exceptionPreprocess
+ 172
1   libobjc.A.dylib                     0x00000001079b809c objc_exception_throw
+ 56
2   Foundation                          0x000000010ad48b90
-[NSMutableDictionary(NSMutableDictionary) classForCoder] + 0
3   IdentaFlyDev                        0x0000000104e57974 +[RCTEventEmitter
initialize] + 300
4   libobjc.A.dylib                     0x0000000107993c4c
CALLING_SOME_+initialize_METHOD + 20
5   libobjc.A.dylib                     0x000000010799492c
initializeNonMetaClass + 520
6   libobjc.A.dylib                     0x00000001079972b4
_ZL24initializeAndMaybeRelockP10objc_classP11objc_objectR12locker_mixinIN9lockdebug10lock_mixinI16objc_lock_base_tEEEb
+ 200
7   libobjc.A.dylib                     0x00000001079a8f70 lookUp<…>

Same issue here. Tested on both iOS Simulator and even my physical iPhone connected to MacBook which is run inside XCode.

authors: ajeeq lucksp

repo: glassfy/react-native-glassfy-module


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in 3c5274d after 5 minutes.

repo: glefait/martinique-public-websites


text:
🛑 Schoelcher is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Schoelcher is back up in a9aa069.


text:
Add verbose flag for debugging purposes

There's a lot of stuff happening in the background - requests being sent and services created. However, much of it happens without user knowledge and developers wanting to understand why the registrator is not working as expected are forced to add log.Println statements all over.
Instead, I propose a library such as jcelliott/lumber or /alexcesaro/log/stdlog for making logging at different levels.
Using log.Debug() and optionally log.Trace() statements we can even have --verbose=1 and --verbose=2. The "lumber" framework also supports adding prefixes, which I see is done in many of the log statements already (with "registrator: " as the prefix).

Sounds good. I'll look into those.

After looking at Docker issues I found that they switched to using "logrus" couple of months back:
https://github.com/docker/docker/issues/8761
Logrus: https://github.com/Sirupsen/logrus

Is this what you recommend?

+1 for logrus

authors: bketelsen hermansc progrium

repo: gliderlabs/registrator


text:
🛑 INTG-APP is down

In 9f7fab9, INTG-APP ($SITE_6) was down:

HTTP code: 0
Response time: 0 ms

Resolved: INTG-APP is back up in f8d2333.

repo: glo-markoaular/status-navigate


text:
AB#27848  Created pending migration and fix event entity

AB#27848
Describe your changes
Create pending migrations and
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have added tests wherever relevant
[x] I have made sure that all automated checks pass before requesting a review
[x] I have communicated above whether I need any deviation from our PR guidelines (eg. "I don't want the reviewer to merge on my behalf because...")

@aberonni  Thanks for the review. I do not think more additional testing is needed than what I described in the subtask in devops


text:
Allow restricting / auto fixing direct imports to aliases

Example:
import { useTable } from '@globalbrain/sefirot/lib/composables/Table'

// to

import { useTable } from 'sefirot/composables/Table'

track in #28

repo: globalbrain/eslint-config


text:
Create requirements-test and remove test libs from requirements

The project only contains the requirements.txt file for all app and test requirements.
They should be separated into two different files, avoiding unnecessary installation of libraries (like responses).

I would like to do this

Welcome aboard @pniedzwiedzinski ! Do you need some help to understand?

Perhaps you want to use a Pipfile instead of requirements.txt. There you have the separation between development and general libraries.

authors: dmvieira ggalves lioman pniedzwiedzinski

repo: globocom/azkaban-cli


text:
WIP: Add Casbin perm enforcer to GSH

This PR aims to add Casbin, a permissions enforcer, into GSH.

At the time of writing I'm working on adding a new functionality to the Casbin code, to identify a policy through an identification string only.

These commits allows add, remove, associate, and disassociate roles in the GSH API.  I added a few pages on the wiki (https://github.com/globocom/gsh/wiki/api-routes#permissions) explaining how new routes work.

Update page with CLI commands: https://github.com/globocom/gsh/wiki/cli-commands

Great job!

authors: Krlier fbomlisboa mdjunior

repo: globocom/gsh


text:
Get haml-lint rubocop to chill

I don't know why these passed locally but are having trouble on PRs but there's a simple solution

probably due to #1971, let's review the changes to see if they make sense and maybe apply them?
but legit!

repo: glowfic-constellation/glowfic


text:
Cecil update to 0.11.4

Updated Mono.Cecil to 0.11.4 and dropped the custom fork.
I needed support for PortablePdbReader/Writer.
I removed code related to "Win32ResourceDirectory" in ILRepack.cs, as it seems to be supported by Cecil now, but I'm not sure about this one ... If this is still needed, I'll be glad to get some help on that !

This PR looks like it does nice things...

Will check it next week 👍

@BSimonSweet this PR is a few months old, but CI is still failing a bit. If you rebase does it fix it? The error appears to be that some dll is still in use:
INFO: IL Repack - Version 2.1.0
INFO: ------------- IL Repack Arguments -------------
/out:C:\Users\appveyor\AppData\Local\Temp\1\4hkxnrkb.4xz\test.dll  C:\Users\appveyor\AppData\Local\Temp\1\4hkxnrkb.4xz\foo.dll
-----------------------------------------------
INFO: Adding assembly for merge: C:\Users\appveyor\AppData\Local\Temp\1\4hkxnrkb.4xz\foo.dll
INFO: Processing references
INFO: Processing types
INFO: Merging <Module>
INFO: Processing exported types
INFO: Processing resources
INFO: Fixing references
INFO: Writing output assembly to disk
INFO: Finished in 00:00:02.1684196
System.IO.IOException: The process cannot access the file 'foo.dll' because it is being used by another process.
   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean throwOnTopLevelDirectoryNotFound, WIN32_FIND_DATA& data)
   at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
   at ILRepack.IntegrationTests.NuGet.TestHelpers.CleanupTempFolder(String& tempDirectory)
   at ILRepack.IntegrationTests.NuGet.RepackNuGetTests.CleanupTempFolder()

I also added a commit here that you can take to reduce the whitespace changes if the lib authors want less of that: https://github.com/BSimonSweet/il-repack/pull/1/commits/b1d6e3d2312abe30ae6fcccbc10c1f2d37b84d86
No code, just removed what appears to be the alignment of the = as well as the correct indentation.

I managed to fi the lock issue and also added some symbol copying in my fork: https://github.com/mattleibow/il-repack

It's great that you made Github Actions scripts for build. It is 2023 way to build stuff.

Hi @BSimonSweet thanks a lot for the contribution and sorry it took so long. I just became a maintainer recently and we've updated to the latest Cecil submodule in the master branch. We can't just drop the Win32Resources logic because it would break compatibility for many users. Also the submodule contains more than just that, so we can't switch to the Cecil NuGet package yet. But at least we now have the latest Cecil and support for native, portable and embedded PDBs.

authors: BSimonSweet KirillOsenkov deniszykov mattleibow timotei

repo: gluck/il-repack


text:
Improve the axis display as how Paraview does

Compared to the current full-size axis that @maxwelltsai and I both prefer this fixed-size axis. It will be located in one corner and keeps the same orientation as the volume object all the time, which could clearly illustrate users how the current status is.
It is not a hard work and I could do it if you also agree with this idea :)

This would be great!

Just put the code and instructions from Vispy group here when the version of Vispy in Conda is updated to 0.5 https://github.com/PennyQ/Test/blob/master/volume_test_axis.py

Make your axis like XYZAxis(parent=viewbox) rather than XYZAxis(parent=viewbox.scene). This allows you to define the position of the axis relative to the viewbox's coordinates in the GUI (so it stays fixed to the window instead of the internal scene).

Connect to the viewbox.scene.transforms.changed event and update the orientation of your axes to match. How you do this will depend on the type of camera you are using.
Make this into a visual of its own and submit a PR  :)

The axis display works on the development version of Vispy now. Here is the code and PR for this functionality.
https://github.com/vispy/vispy/pull/1125

I will close this because we already have #76

authors: PennyQ astrofrog


text:
Please guide us how to add fonts to RN CLI in the documentation!

Description
Firstly, thank you for your hard work; it's truly appreciated. I would like to request adding a guide on how to add fonts to a React Native CLI project. While your documentation describes how to do it for Expo, it seems that method doesn't work as effectively. However, there's no information provided on how to do it for React Native CLI projects, which I believe is still the preferred choice for the majority of users. Could you please address this gap in the documentation?
Problem Statement
I believe the description is self-explanatory enough.
Proposed Solution or API
Just add a easy to follow guide.
Alternatives
No response
Additional Information
No response

Thank you for your assistance with adding fonts to React Native. I initially encountered difficulties, but now it's working as expected. I apologize if I raised any unnecessary concerns. Your help is greatly appreciated.

Thank you for your assistance with adding fonts to React Native. I initially encountered difficulties, but now it's working as expected. I apologize if I raised any unnecessary concerns. Your help is greatly appreciated.

Hello.
How did you solve this problem? I can use normal fonts with react-native styles, but gluestack doesn't work.

Good day,
I haven’t done anything special, aside of adding the font that I need to the gluestack-ui.config.ts file like so:
@.***
And then when I need to use it, I am selecting heading for instance if this was the place where I have added the new font.
Add the font that you need like normal way for React Native (here is a simple guide: https://blog.logrocket.com/adding-custom-fonts-react-native/) and then follow gluestack-ui guide for Next.js.
I hope this make sense.
Regards
—
Hristo Dimitrov
Software Engineer II
Veliko Turnovo, Bulgaria
[https://lh7-us.googleusercontent.com/CQ7wMPqk5D65sXxhtUz00z8MOei9f5aur9PfwEp_vJWDtoMK6EpXWuiWao2ZQnlD3UGxHVrmu6jyRX6CVj1fTjrthGFZh3Sa6jUBqsWdXAaHoacTzl_OIBb9KmN6kgtbbrLjtZ_jhPvA4KsduVeaiBI]
***CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are confidential and are intended solely for the addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail or phone and delete this message and its attachments, if any.
From: Felipe Estevão Moreno @.>
Date: Tuesday, 26 March 2024 at 22:55
To: gluestack/gluestack-ui @.>
Cc: Hristo Dimitrov @.>, State change @.>
Subject: Re: [gluestack/gluestack-ui] Please guide us how to add fonts to RN CLI in the documentation! (Issue #1773)
Thank you for your assistance with adding fonts to React Native. I initially encountered difficulties, but now it's working as expected. I apologize if I raised any unnecessary concerns. Your help is greatly appreciated.
Hello.
How did you solve this problem? I can use normal fonts with react-native styles, but gluestack doesn't work.
—
Reply to this email directly, view it on GitHubhttps://github.com/gluestack/gluestack-ui/issues/1773#issuecomment-2021456897, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYM7HDMDYEAXL2Y27IEMG5TY2HOE7AVCNFSM6AAAAABDEU5LEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGQ2TMOBZG4.
You are receiving this because you modified the open/close state.Message ID: @.***>

repo: gluestack/gluestack-ui


text:
About  TCP rotating XYZ

Hello!
When the X axis is rotated, set the X value to 1.55, the angle of the A3 is 86, and when the X value continues to increase to 1.65, the A3 value is -89, then the machine will swirl quickly. How to fix this problem?

A3 will only operate in the range of +-90 degree. The idea is that you can reach all poses with this range. (Not without a reconfiguration of the wrist in some positions though)
The goal is to implement proper robot configurations that circumvent this issue. Currently one configuration is hardcoded.
If you need a smooth motion over these boundaries you may need to hack this yourself. Look for the kinematics.cpp. At the end you can check if the angle is <=0 and add something like angle[3] = 90Deg2Rad+90Deg2Rad+angle[3] (basically changing the range of motion from  -90/90 to 0/180. not tested. ) You also have to flip the axis 4 then.

Am 28.04.2018 um 11:09 schrieb natdon notifications@github.com:
Hello!
When the X axis is rotated, set the X value to 1.55, the angle of the A3 is 86, and when the X value continues to increase to 1.65, the A3 value is -89, then the machine will swirl quickly. How to fix this problem?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: glumb natdon

repo: glumb/robot-gui


text:
Fails to create an image for Debian/Testing and Debian/Unstable

Hi, I have defined the following stretch.def:
DistType "debian"
MirrorURL "http://ftp.us.debian.org/debian/"
OSVersion "stretch"

Setup
Bootstrap

InstallPkgs git

Cleanup

then I bootstrap the image:
sudo singularity bootstrap Stretch.img stretch.def
The boostrap fails with the following error:
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: libaudit-common libaudit1 libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 libncursesw5 libsemanage-common libsemanage1 libsystemd0 libudev1 libustr-1.0-1
I: Found additional base dependencies: adduser debian-archive-keyring gpgv libapt-pkg5.0 liblz4-1 libstdc++6
I: Checking component main on http://ftp.us.debian.org/debian...
....
I: Configuring apt...
I: Configuring libc-bin...
I: Base system installed successfully.
+ apt-key update
Error: gnupg, gnupg2 and gnupg1 do not seem to be installed,
Error: but apt-key requires gnupg, gnupg2 or gnupg1 for this operation.

I get a similar error for sid.
I use the packaged version (2.1.2) by neuro-debian.

Please install gnupg, gnupg2 & gnupg1 on your debian machine.
apt-get install gnupg
apt-get install gnupg1
apt-get install gnupg2
and then bootstrap the image.
--Krishna.
On Tue, Sep 13, 2016 at 6:52 AM, Trophime notifications@github.com wrote:

Hi, I have defined the following stretch.def:
DistType "debian"
MirrorURL "http://ftp.us.debian.org/debian/"
OSVersion "stretch"
Setup
Bootstrap
InstallPkgs git
Cleanup
then I bootstrap the image:
sudo singularity bootstrap Stretch.img stretch.def
The boostrap fails with the following error:
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: libaudit-common libaudit1 libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 libncursesw5 libsemanage-common libsemanage1 libsystemd0 libudev1 libustr-1.0-1
I: Found additional base dependencies: adduser debian-archive-keyring gpgv libapt-pkg5.0 liblz4-1 libstdc++6
I: Checking component main on http://ftp.us.debian.org/debian...
....
I: Configuring apt...
I: Configuring libc-bin...
I: Base system installed successfully.

apt-key update
Error: gnupg, gnupg2 and gnupg1 do not seem to be installed,
Error: but apt-key requires gnupg, gnupg2 or gnupg1 for this operation.

I get a similar error for sid.
I use the packaged version (2.1.2) by neuro-debian.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gmkurtzer/singularity/issues/213, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQb9sdMxaXsxa12CEA59Ah6_H752Mx6ks5qpqqygaJpZM4J7siO
.

What do you mean?
install gnupg et al on my host which is a Debian Testing? or on the image?
Actually gnupg is already install on my host:
dpkg -l | grep gnupg
ii  gnupg                                    1.4.20-6                               amd64        GNU privacy guard - a free PGP replacement
ii  gnupg-agent                              2.1.11-7                               amd64        GNU privacy guard - cryptographic agent
ii  gnupg2                                   2.1.11-7                               amd64        GNU privacy guard - a free PGP replacement (new v2.x)

if I try to install gnupg1, I end up with:
sudo apt-get --dry-run install gnupg1 gnupg gnupg2
Reading package lists... Done
Building dependency tree
Reading state information... Done
gnupg is already the newest version (1.4.20-6).
gnupg2 is already the newest version (2.1.11-7).
gnupg2 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnupg1 : Breaks: gnupg (< 1.4.20-6+exp1)
          Breaks: gnupg:i386 (< 1.4.20-6+exp1)
E: Unable to correct problems, you have held broken packages.

gnupg1 package need to be fixed.
However it seems that apt-key update on Debian/Testing is no longer needed:
sudo apt-key update
[sudo] password for xxxx:
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be removed safely.

I removed the automatic call to apt-key update in [master 01559bc].

Hi @Trophime, I am closing this ticket but please comment on it if for any reason it needs to be re-opened.
Thank you!

authors: Trophime gmkurtzer kmuriki

repo: gmkurtzer/singularity


text:
Token icon links on Rinkeby seem to be broken

The URLs of the icons of the following tokens on Rinkeby seem to be broken. I get an access denied from AWS

https://safe-relay.rinkeby.gnosis.pm/api/v1/tokens/?search=LOVE
https://safe-relay.rinkeby.gnosis.pm/api/v1/tokens/?search=DAIc

Hi @tschubotz ,
It's fixed now, I configured icons for both tokens

repo: gnosis/safe-relay-service


text:
🛑 Beacon Explorer is down

In f6e5048, Beacon Explorer (https://beacon.chiadochain.net/) was down:

HTTP code: 503
Response time: 515 ms

Resolved: Beacon Explorer is back up in 13c20a8 after 13 minutes.

repo: gnosischain/chiado-uptime


text:
Make IBC AcceptIncomingConnectionAction configurable

Hey there,
great image! Especially the functionality to run both paper and live in one container saves the day!
Could you please make the IBC setting "AcceptIncomingConnectionAction" configurable via an environment variable?
I currently have to run with custom config and set it there because otherwise TWS does not let me  connect.
Thank you very much!

check this, it might help you
https://github.com/gnzsnz/ib-gateway-docker/discussions/74#discussioncomment-8343215
and try the first bullet point

define TWS_SETTINGS_PATH, and a volume for your settings. then you change that setting through ibgateway/tws gui

for example in .env
TWS_SETTINGS_PATH=/config/tws_settings
in docker compose
    volumes:
      - ${PWD}/config:/config

this way you can define your settings and store them

this is more secure than what you are asking for.
What you are asking, can be done, it will require a small change. But honestly i don't consider it a priority.

included in #117
next release will include the new codebase and support for AcceptIncomingConnectionAction

authors: gnzsnz handelsmeisterei

repo: gnzsnz/ib-gateway-docker


text:
nil pointer dereference when running go-bootstrap on linux/amd64

Steps to Reproduce
On linux/amd64, run these commands:
go get github.com/go-bootstrap/go-bootstrap
$GOPATH/bin/go-bootstrap -dir github.com/xxxx/yyyy

Observed Behavior
2015/07/26 00:09:47 Creating /home/aev/go/src/github.com/xxxx/yyyy...
2015/07/26 00:09:47 Copying a blank project to /home/aev/go/src/github.com/xxxx/yyyy...
2015/07/26 00:09:47 Replacing placeholder variables on xxxx/yyyy...
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x403709]

goroutine 1 [running]:
main.main()
	/home/aev/go/src/github.com/go-bootstrap/go-bootstrap/main.go:91 +0x2b09

Expected Behavior
go-bootstrap should work on linux/amd64.
Commentary
currentUser on line 91 of main.go is nil. Replacing lines 59 and 60 of main.go with those below produces the error "user: Current not implemented on linux/amd64".
  currentUser, err := user.Current()
  helpers.ExitOnError(err, "")

See also #1.

Somehow I wasn't notified on this issue. I will definitely look at it today.

authors: aevernon didip

repo: go-bootstrap/go-bootstrap


text:
Control panel changes for Egress

Control panel changes for Egress

Pull Request Test Coverage Report for Build 1384

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
12 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.2%) to 63.812%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

control/archaius/panel.go
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

control/archaius/panel.go
1
73.81%

core/options.go
2
85.96%

core/handler/transport_handler.go
3
21.25%

core/registry/discovery.go
3
69.23%

core/loadbalancer/load_balancer.go
3
70.91%

Totals

Change from base Build 1382:
0.2%

Covered Lines:
5179

Relevant Lines:
8116

💛  - Coveralls

authors: Rajadeepan coveralls

repo: go-chassis/go-chassis


text:
Incorrect kernel version detected in container

Linux kernel running on the host may differ from the version installed inside of container.
In that case the detection of the "recent" version fails for container having several kernels installed:
# dpkg -l | grep linux-image
ii  linux-image-4.19.0-1-amd64           4.19.12-1                                amd64        Linux 4.19 for 64-bit PCs (signed)
rc  linux-image-4.9.0-3-amd64            4.9.30-2+deb9u5                          amd64        Linux 4.9 for 64-bit PCs
rc  linux-image-4.9.0-4-amd64            4.9.65-3+deb9u1                          amd64        Linux 4.9 for 64-bit PCs
rc  linux-image-4.9.0-5-amd64            4.9.65-3+deb9u2                          amd64        Linux 4.9 for 64-bit PCs
rc  linux-image-4.9.0-6-amd64            4.9.88-1+deb9u1                          amd64        Linux 4.9 for 64-bit PCs
rc  linux-image-4.9.0-7-amd64            4.9.110-3+deb9u2                         amd64        Linux 4.9 for 64-bit PCs
ii  linux-image-4.9.0-8-amd64            4.9.130-2                                amd64        Linux 4.9 for 64-bit PCs
ii  linux-image-amd64                    4.19+101                                 amd64        Linux for 64-bit PCs (meta-package)

In example above 4.9.0-8-amd64 was used for starting qemu.
Moreover, after de-installation of unneeded images some artifacts left and the appropriate directories under /lib/modules weren't wiped out completely. So it is leading to non-working configuration since "detected" kernel version is not exists.

Since this issue the kernel&module detection has improved hugely; if still a problem please re-open.

repo: go-debos/fakemachine