ronn | Randomized overdrive neural networks

I’m using git large files in one of my github private repositories and all was just good, but when I copy and paste the link for the raw data in an unlogged browser it was possible to see it. Is there a way to solve this problem?

In git large files page there is a topic saying “Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.”

Is that true? Is there a way to configure the repo to hidden my information? I’ve tried to understand one of glfs tutorials but couldn’t find the ansewr.

I was using git lfs for some large files as I had committed prior to use it, so I had to use git lfs migrate import as provided here which re-wrote the commits and then I was able to push it on the server. But, in turn, it has changed whole project's every .kt, .xml file to these 3 lines:

I am trying to install a specific jq version in my virtual pyenv environment with the command below:

I am looking for some advice on debugging some extremely painful Docker connectivity issues.

In particular, for an Azure DevOps Services Git repository, I am running a self-hosted (locally) dockerized Linux CI (setup according to https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops#linux), which has been working fine for a few months now.

All this runs on a company network, and since last week the network connection of my docker container became highly unstable:

• Specifically it intermittently looses network connection, which is also visible via the logs of the Azure DevOps agent, which then keeps trying to reconnect.

• This especially happens while downloading Git LFS objects. Enabling extra traces via GIT_TRACE=1 highlights a lot of connection failures and retries:

  trace git-lfs: xfer: failed to resume download for "SHA" from byte N: expected status code 206, received 200. Re-downloading from start

• During such a LFS pull / fetch, sometimes the container even stops responding as a docker container list command only responds:

  Error response from daemon: i/o timeout

  As a result the daemon cannot recover on its own, and needs a manual restart (to get back up the CI).

Also I see remarkable differences in network performance:

• Manually cloning the same Git repository (including LFS objects, all from scratch) in container instances (created from the same image) on different machines, takes less than 2mins on my dev laptop machine (connected from home via VPN), while the same operation easily takes up to 20minutes (!) on containers running two different Win10 machines (company network, physically located in offices, hence no VPN.
• Clearly this is not about the host network connection itself, since cloning on the same Win10 hosts (company network/offices) outside of the containers takes only 14seconds!

Hence I am suspecting some network configuration issues (e.g. sth with the Hyper-V vEthernet Adapter? Firewall? Proxy? or whichever other watchdog going astray?), but after three days of debugging, I am not quite sure how to further investigate this issue, as I am running out of ideas and expertise. Any thoughts / advice / hints?

I should add that LFS configuration options (such as lfs.concurrenttransfers and lfs.basictransfersonly) did not really help, similarly for git config http.version (or just removing some larger files)

it does not actually seem to be about the self-hosted agent but a more general docker network cfg issue within my corporate network.

Running the following works consistently fast on my VPN machine (running from home):

Trying to migrate a repo (including history) OUT of Git LFS.

I ran git lfs migrate export --include="*" --everything (mentioned here) on a test repo, but it didn't work as expected and left LFS pointer files instead of converting them all to objects.

I tried alternative methods, following this. Unfortunately it still left pointer files, so I combined it with this.

In the end, I even ran all the commands together:

git lfs ls-files -I filter seems not to work with non-ASCII folder names even when the filter is passed in octal encoding, as can be confirmed with the bash script below:

Table panel & panelists have 1 column in common. called user_id where it's an integer for example

table panel:

I'm trying to add everything under MyProject/Frameworks/ to git-lfs (large file storage). I'm not sure what the proper format for matching all files and folders recursively under the Frameworks folder is. This answer says the proper format is git lfs track "MyProject/Frameworks/**", but Atlassian's help document says I should use git lfs track "MyProject/Frameworks/". I tried both and they didn't use git lfs for storage. It tried uploading files directly.

Sure, I'd love to know the proper format, but more importantly, before I attempt to push my changes to github, I'd like to verify that the match and files do indeed work correctly. This'll allow me to iterate and try new things.

I see two related commands that might help: git lfs status and git lfs ls-files. It's not clear which one I should be using and what output I should be looking for. For example, when I ran git lfs status, it showed me a ton of files under Git LFS objects to be committed, making me think they would be added to Git LFS. However, after attempting to push to GitHub.com, I realized that it was clearly not the case. If it helps, the output for these files always had something like (Git: edee1ad) after each file name.

When I attempt to use git lfs ls-files I'm not sure if I need to run it after git adding the files, after committing them, or after pushing them. Most of the time it's just showing me blank output.

Essentially the question is: If I configured git lfs correctly, what tool (e.g. git lfs status) should I use, and what output should I look for before I attempt to commit/push?

Note: Please don't answer the question with only how to match all recursive files as that will help me once (this specific case), rather than allowing me to iterate and try new things (any case).

I'm very new to coding.

I'm using PHP to get a JSON response from an API. The JSON response consists of Titles and URLs to pages on the web. The sample JSON response is at the bottom of the page.

How do I write each item in this JSON data using PHP to my HTML page in the body tag? I want to create HTML "a" tags with the text being the JSON name value and the href being the JSON url value for each item.

Where does the JSON data end up after I get it from the API using PHP, and then how do I access it and format it with PHP? I'm using PHP to keep my API access key server side so the client can't see it. Here is my code: