using statement declaration without braces does not work (IDisposable)

Description
using statement declaration without braces does not work (IDisposable). You cannot use using without braces.
Example:
using var x = new ALogger();

Console.WriteLine("not working...");

public class ALogger : IDisposable
{
    public void Dispose()
    {
        Console.WriteLine("Finishing...");
    }
}

Version
Version: 1.0.360602+9bf026dabac44a6256a65168fa93dcb7e2edcca4
Library version: 1.0.0-beta.22606.2+9bf026dabac44a6256a65168fa93dcb7e2edcca4
Build date: 2022-12-08T07:51:24.4686906Z

OS

[X] Windows 11
[X] Windows 10

Frontend

[X] Visual Studio Code

Screenshots
Polyglot Notebook:

It works in Visual Studio 2022:

The reason this doesn't work is because the C# language used in notebook cells is the script dialect which differs slightly from the "normal" project dialect.
Going a little deeper, it's ultimately because in the script dialect, x is technically a field on a class, so to get the behavior you're looking for (i.e., scoped) you need the one with parentheses and brackets like in your second example.


core-bpf: special-case config program error codes

This change special-cases a few error codes for the Config program, which otherwise would produce known mismatches between BPF and builtin.
This also sets the stage to allow special-casing custom codes from other programs, such as Address Lookup Table.
For more information, see the comments above the change, or https://github.com/solana-program/config/pull/21.

@mjain-jump feel free to review, but don't merge until we land on https://github.com/solana-program/config/pull/21 please.


Stopped working after updating parse-server version from 2.2.1 to *

I have deployed latest parse-server-example copy on Heroku. I needed to update the minimum version of parse-server to 2.8.4 to get ready to migrate to MongoDB Atlas from mLab.
The application works fine with 2.8.4 but if I put *, it stops working. I tried different versions and noticed that it works until 3.4.4 and then from 3.5.0 onwards it stops working.
I am not sure how exactly to find out what's wrong or whats the error. Please advise.
Please let me know if there are any changes required.

Have you checked this guide?
https://github.com/parse-community/parse-server/blob/master/3.0.0.md

I have a fresh copy of this repo. I just change the variable names and it worked previously with 2.2.1. In fact it worked until 3.4.4.
Do I still have to make these changes to the code?

I'm closing this as it lacks essential information. Feel free to edit your question using the issue template and we can re-open this issue.


Only build pushes to master branch & pull requests

.. to avoid building other branches of this repo -> faster CI

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master      #4   +/-   ##
======================================
  Coverage    97.1%   97.1%
======================================
  Files           6       6
  Lines         173     173
  Branches       19      19
======================================
  Hits          168     168
  Misses          5       5

Continue to review full report at Codecov.

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


overlap/overwrite axis calls

gs <- gsplot() %>%
    points(0:1,0:1) %>%
    axis(side=1, at=c(0.5,1)) %>%
    axis(side=1, at=c(0.25, 0.75))
gs

Should plot have 0.25, 0.5, 0.75, and 1 ticks to match base behavior?

Suggestion:
gs <- gsplot() %>%
    points(0:1,0:1) %>%
    axis(side=1, at=c(0.5,1)) %>%
    axis(side=1, at=c(0.25, 0.75), append=TRUE)
gs

always assume axis call exists (default) for append/replace
to not draw axis lines: use lwd=0 and lwd.ticks=1 ??

closed by #410


Removed Braze snippet and added Braze SDK through npm

I've removed the braze snippet from the v2 initialization code and included the require statement. When installing the npm package, it created a node_module folder, but I did not add it to this pull request.

@ucarion here is the pull request to account for the appboy queue errors we were seeing. Several points to note:

The npm install route updates the Braze Web SDK from 2.1 to 2.2.2. This shouldn't be a problem as there haven't been any breaking changes since that version.

I removed all v1 code as it would no longer work once I changed all window.appboy calls to appboy.METHOD

I also remove the loaded method because the npm route doesn't require it.

Let me know if you have any comments.
@Bucimis


add jscs check

Thanks. However I feel that's too much change. Can we use a .jscsrc file (instead of the inline arguments) which allows some of them? For example:
{
    "preset": "airbnb",
    "requirePaddingNewLinesAfterBlocks": false,
    "requirePaddingNewLinesBeforeLineComments": false,
    "safeContextKeyword": ["self"]
}

Done.

Thanks. Merging.

@CCharlieLi You forgot the .jscsrc file. I guess it's ignored by .gitignore. Please add it.


rcv1.ipynb is not match the description

comment  in the rcv1.ipynb said that:
"This left us with 50 classes and 402,738 documents. We divided the documents into equal-sized training and test sets randomly. Each document was represented using the 2000 most frequent non-stopwords in the dataset."
but I find that  dataset.data_info() :
N = 420065 documents, M = 47236 words, sparsity=0.0000%
According to the comment in the script(rcv1.ipynb), N should be 402738 and M should be 2000. but in fact it is not match the description
Is there any wrong in  rcv1.ipynb ? You have a rcv1 code here, but you don't  mention rcv1 dataset in the paper , why?

Thanks for your interest. The reason of the non-inclusion of rcv1 in the paper and half-finished code and comments is because it was a work-in-progress. I started working on it for its larger corpus (than 20news) but could not finish in time. Sorry for the confusion.


[CI BROKEN] [URGENT] Integration test broken for docker

Description
test-integration-docker-compatibility started failing on master with seemingly no related change around the time of:
https://github.com/containerd/nerdctl/commit/af229a67313733a88cc623e0bc05bda34ec568a3
Failing test is TestBuilder/Debug (docker builder debug not recognized as a command).
It seems the trigger for this comes from the updated github action runner base image.
From:
https://github.com/actions/runner-images/blob/ubuntu24/20241016.1/images/ubuntu/Ubuntu2404-Readme.md
to
https://github.com/actions/runner-images/blob/ubuntu24/20241103.1/images/ubuntu/Ubuntu2404-Readme.md
which happened around 11/03 - timeline is consistent.
Specifically in the changelog, Docker-Buildx has been updated from 0.17.1 to 0.18.0, which I guess is the culprit.
@AkihiroSuda I am flying and will be unable to send PRs for a few days.
Could you carry this?
I am not completely sure why or what is going on here, but maybe just
index 9cb34d5e..033f70e3 100644
--- a/cmd/nerdctl/builder/builder_builder_test.go
+++ b/cmd/nerdctl/builder/builder_builder_test.go
@@ -71,6 +71,7 @@ CMD ["echo", "nerdctl-test-builder-prune"]`, testutil.CommonImage)
                        },
                        {
                                Description: "Debug",
+                               Env:         map[string]string{"BUILDX_EXPERIMENTAL": "1"},
                                NoParallel:  true,
                                Command: func(data test.Data, helpers test.Helpers) test.TestableCommand {
                                        dockerfile := fmt.Sprintf(`FROM %s

might fix it.
Steps to reproduce the issue
na
Describe the results you received and expected
na
What version of nerdctl are you using?
main
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response

The test was completely broken, even in  buildx v0.17.1.
The error was ignored because the command exited with status 0.
$ buildx debug .
Extended build capabilities with BuildKit

Usage:
  ./bin/build/buildx [command]

Available Commands:
  bake        Build from a file
  build       Start a build
  create      Create a new builder instance
  dial-stdio  Proxy current stdio streams to builder instance
  du          Disk usage
  help        Help about any command
  imagetools  Commands to work on images in registry
  inspect     Inspect current builder instance
  ls          List builder instances
  prune       Remove build cache
  rm          Remove one or more builder instances
  stop        Stop builder instance
  use         Set the current builder instance
  version     Show buildx version information

Flags:
      --builder string   Override the configured builder instance
  -D, --debug            Enable debug logging
  -h, --help             help for ./bin/build/buildx

Use "./bin/build/buildx [command] --help" for more information about a command.

Experimental commands and flags are hidden. Set BUILDX_EXPERIMENTAL=1 to show them.

$ echo $?
0

$ BUILDX_EXPERIMENTAL=1 ./bin/build/buildx debug .
ERROR: unknown command "." for "./bin/build/buildx debug"


QUESTION: Add PDF export feature to upstream?

Hi, we are using a forked version of this theme for the UNICEF Open Source Inventory. Recently, @Idadelveloper added a feature to export articles to PDFs in unicef/inventory-hugo-theme#9.
I opened this issue to see if this is a feature upstream is willing to support? If yes, we can bring that patch from our downstream fork and integrate it here upstream so all users of the theme can benefit. But before opening the Pull Request, we wanted to check if this is a wanted feature.
Thanks!

Hello @jwflory
Thanks for using our themes, It's a great honor for us. I saw in your repository you guys put our name , It would be a big achievement for us if you mention our credit in the website footer(not mandatory ).
For the update please make a pull request. I think this will help others .
Thanks

Hi @mehedi-sharif, thanks for the reply and confirmation. @Idadelveloper opened #168 with the PDF export feature we implemented downstream. Let us know if you have feedback on that change or what we can do to prepare that patch for merging.
Also, I added an attribution to our site footer in the copyright field. See unicef/inventory@b4dbbb2b847e5838c260ffafa17b498ef28caaf6. 😄

I noticed #168 was merged. Closing this issue, thanks for your support!


Macports package

Hi, I saw that you graciously provided a homebrew package in #43. For some of us who still prefer to use macports instead of homebrew, may I request a macports package as well? Thanks!

Hi! I realized a macports package was added recently: https://ports.macports.org/port/csvlens/


chore: remove started prop

Description
With this PR we remove the started property from the MetaSession interface.
This is because the collector does accept this property.
It is also not used anywhere in the web-sdk so it is save to remove it.
Fixes
Fixes #
#98 https://github.com/grafana/faro-web-sdk/issues/98
Checklist

~[ ] Tests added~
[x] Changelog updated
[x] Documentation updated PR

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Updated to use the latest rpc.capnp file

It seems like the Cap’n Proto RPC protocol has changed since you last generated this file.
Thanks for the wireshark plugin.  Very useful!

Most likely ;)
Thanks for the PR. Happy it still works ;)


Uploading files using websockets

Hi,
I am building a chat application where I wanna have a feature of sending files alongside with messages here is my code so far:
main.py:
@app.websocket("/api/user-chat")
async def chat(websocket: views.WebSocket):
    # get message sender
    sender = helper.get_current_user()
    try:
        while True:
            # get receiver and file information
            data = await websocket.receive_json()
            receiver = data['receiver']
            filename = data['filename']
            # get message file
            file = await websocket.receive_bytes()
            file_dir = helper.gen_file_dir(sender, __file__)
            file_url = helper.create_file(file_dir, filename, file)
            data.update({
                    "file": file_url,
                    "filename": filename
             })
             await socket_manager.send_msg(data)
    except WebSocketDisconnect:
        socket_manager.disconnect(websocket, user)
        print("error occurred")

helper.py
# generate file url
def gen_file_dir(directory, file):
    root = pathlib.Path(file).parent.absolute()
    relative_path = "/static/media/uploads"
    absolute_path = str(root) + relative_path
    target_url = os.path.join(absolute_path, directory)
    return target_url

# create file on disk
def create_file(dir, name, file):
    path = dir + "/" + name
    os.mkdir(dir)
    with open(path, "wb") as f:
        f.write(file)
    return path

The above code gets the file from frontend and stores the file on the server. But it seems to work for images and application files (jpg, png, pdf, docx, txt). I tried it with mp3 and gif it gives error occurred how would I allow any type of file to upload using websockets ?
Edit:
After adding try except block as suggested in the comments:
    try:
         file = await websocket.receive_bytes()
         # reset of the code
    except Exception as e:
         print("error was: ")
         print(e)

I get the following error:
error was:
1006
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/home/myenv/lib/python3.8/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 154, in run_asgi
    result = await self.app(self.scope, self.asgi_receive, self.asgi_send)
  File "/home/myenv/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/fastapi/applications.py", line 179, in __call__
    await super().__call__(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/applications.py", line 111, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/middleware/errors.py", line 146, in __call__
    await self.app(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/exceptions.py", line 58, in __call__
    await self.app(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/routing.py", line 566, in __call__
    await route.handle(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/routing.py", line 283, in handle
    await self.app(scope, receive, send)
  File "/home/myenv/lib/python3.8/site-packages/starlette/routing.py", line 57, in app
    await func(session)
  File "/home/myenv/lib/python3.8/site-packages/fastapi/routing.py", line 228, in app
    await dependant.call(**values)
  File "./main.py", line 232, in direct_chat
    data = await websocket.receive_json()
  File "/home/myenv/lib/python3.8/site-packages/starlette/websockets.py", line 97, in receive_json
    message = await self.receive()
  File "/home/myenv/lib/python3.8/site-packages/starlette/websockets.py", line 47, in receive
    raise RuntimeError(
RuntimeError: Cannot call "receive" once a disconnect message has been received.

Have you tried printing the exception to see what the error is?

@Mause It doesn't show any error i debuged it and this line seems to cause the problem:
file = await websocket.receive_bytes()

You have to assign the error to a variable before you can print it, can you show us the error?

@Mause  I edited the answer check it out

It's as the error states then, your frontend has disconnected

@Mause But how does it work with other formats like with (jpeg, png, docx, xlx, zip) but not with (gif, mp3 ) ?

Are you sure it's not a case of file sizes?

yes both of these files are less than 2MB

@Mause  yes both of these files are less than 2MB

@tiangolo perhaps you may help.

@Ahtii maybe you can try to use Starlette directly to make sure the problem.

Thanks for the help here @Mause and @baby5 ! 🍰
@Ahtii please create a minimal self contained example that shows your error, something that can be copy-pasted and run to see your current problem, that will allow me or anyone else to help you better. 🤓

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.

Hey everyone. The other day, I was working on a similar task of sending and receiving images between a javascript client, react in my case, and FastAPI. The only way that worked for me is by encoding the image into base64 at the client(you can look at this example in case you are using react-dropzone) and then decoding the image at the server side with the base64 module. This way, you don't have to use the receive_json function as receive_text would suffice. That's it, I hope this might help someone in the wild. Have a nice day/evening, fellas!


Removed --prefix from verify command.

Prefixes are 1-1 with aliases which are already required for this command and thus redundant.  Removed for ease of use.

The --prefix option is meant to specify the signer of the data, not the one verifying it.  The tests in demo-script.sh are misleading because they use the same AID for signing and verifying.
If anything, the --alias argument can be removed because you don't need a Hab context to verify someone else's signature, you just need the Habery database so you load their key state in the Kevers.

The --prefix option is meant to specify the signer of the data, not the one verifying it. The tests in demo-script.sh are misleading because they use the same AID for signing and verifying.
If anything, the --alias argument can be removed because you don't need a Hab context to verify someone else's signature, you just need the Habery database so you load their key state in the Kevers.

@pfeairheller so how would I restructure this not to have to use an alias to verify?  Nothing in the verify command looks like its making a remote call to a prefix KEL in the wild so aren't aliases and prefixes 1-1 in the current implementation?

The appropriate change here is to remove the --alias argument because a local Hab is not needed to verifiy a signature.  The --prefix parameter is to allow the verification of signatures from other folks AIDs.  If we rely on --alias and a Hab, we can only verify our own signatures.
To remove --alias you need to change
with existing.existingHab(name=name, alias=alias, base=base, bran=bran) as (_, hab):

to:
with existing.existingHby(name=name, base=base, bran=bran) as hby:

And then change hab.kevers to hby.kevers


test: add Terratest as testing framework

Description
Add tests for example runner-default using terratest.
Closes #81
Migrations required
NO
Verification
n/a
Documentation
Added README for tests

I think this is a good first try to implement a test strategy for the project. But we need more discussions on how to implement unit and infrastructure tests.

@kayman-mk did you check this PR? Since it was an experiment 3 years ago.

Oh no! I received a notification that you requested a review. So I thought it was finished. And the code was looking good.
I didn't check it, no. But we definitely need some tests in the module and this is a good option. Will put it on my list.


Introduce caching for the Docker build

To improve Github Actions build time, as most of the layers could be cached (e.g. until package.json changes).
Edit: the actual strategy to do this has to be agreed, may be using Github Actions cache for example, or just a docker pull from latest.

Depends on https://github.com/libero/prc/issues/2

We don't need to improve CI performance at the moment, takes less than 3 minutes to execute.

/cc @erkannt mentioned this in the retrospective.

Also wonder if it's possible to only run tests etc if the layers have changed?

Possible solution that worked for reviewer-client:
      - uses: whoan/docker-build-with-cache-action@v5
        with:
          username: libero
          password: "${{ secrets.GITHUB_TOKEN }}"
          image_name: libero/reviewer-client/reviewer-client
          image_tag: ${{ github.sha }}
          registry: docker.pkg.github.com
          build_extra_args: "--build-arg=image_tag=${IMAGE_TAG}"

This uses the image registry of the github repo that is available by default and pushes each intermediate layer to it.
We wouldn't be able to simple use our make targets to build, but could easily construct an equivalent docker build command via build_extra_args.

Looks like Docker Compose supports --cache-from: https://docs.docker.com/compose/compose-file/#cache_from


adding ClusterTimeSimulation

implemented ClusterTimeSimulation function.
does not work yet :/
#6

I'll gather what is left to do for future reference:

[ ] Normalization of measures
[ ] Creation of a test case that is known to cluster relatively fast. Maybe orienting on the parameters from the thesis might help.
[ ] Optional: handling of deadlocks


Publish 05/27/2021, 10:30 AM

Docs Build status updates of commit f67e587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-FileSensitivityLabelInfo.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Set-SPWebApplication.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/New-CsExternalAccessPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsExternalAccessPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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


Update how-to-create-portal-experiments.md

@j-martens : Thanks for your contribution! The author(s) have been notified to review your proposed change.


workbench can be dug with material inside

Players can dig their workbench with material left inside, causing the material to be lost when dug.
Please make it that the workbench cannot be dug when items are anywhere inside.
For my reference 1658

https://github.com/minetest-mods/crafting_bench/pull/11

From what I can tell this was fixed by #11

Fixed in https://github.com/minetest-mods/crafting_bench/commit/3b3309ea43fee8a171c4c5bfa7ffaf38ee421144.


[MWPW-161502] User Access Control POC

Describe your specific features or fixes and provide a preview link for the feature being incorporated
Resolves: MWPW-NUMBER
Test URLs:

Before: https://main--ecc-milo--adobecom.hlx.page/
After: https://--ecc-milo--adobecom.hlx.page/

Codecov Report
Attention: Patch coverage is 21.05263% with 45 lines in your changes missing coverage. Please review.

Project coverage is 50.85%. Comparing base (13516fc) to head (fec1395).
Report is 158 commits behind head on dev.

Files with missing lines
Patch %
Lines

ecc/scripts/profile.js
19.64%
45 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              dev     #273       +/-   ##
===========================================
- Coverage   67.22%   50.85%   -16.38%
===========================================
  Files           2        2
  Lines         238      293       +55
===========================================
- Hits          160      149       -11
- Misses         78      144       +66

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


(xpdf-utils) Outdated

Checklist

[X] I have checked the moderation queue that no new version has been submitted (only visible when logged in), or the submitted package version has failed the automated checks.

Please navigate to the following link to view the moderation queue.

[X] I have verified that the new version is a stable release.
[X] I have looked to see if there are any Bug reports that prevents a new version being submitted and that no existing Outdated Reports have been created.
[X] I have verified the new version has a Windows binary (EXE or MSI installer, Zip or other archive, etc).

New Software Version
4.04
Download location
https://www.xpdfreader.com/download.html
Package Page
https://community.chocolatey.org/packages/xpdf-utils

I'll pick this one up.


Implementation broken when upgrading from 1.1.4 to 1.3.0

Hi,
I am currently using 1.1.4 and would like to upgrade to 1.3.0, but the library is not working as expected after the upgrade and I have been unable to isolate the issue through debugging the library... and was hoping you could help.
I am using the browser version of the library like below:
import { meros } from 'meros/browser';

const fetchResult = await fetch(url, {
  body: JSON.stringify(body),
  headers: new Headers(this._headers),
  method: 'POST',
}).then(meros);

And I am generating the chunked response for my test like below:
export const createResponseChunks = (responses: PlainObject[]) => {
  const chunks = responses.map(response => {
    const chunk = Buffer.from(JSON.stringify(response), 'utf8');

    return [
      '',
      '---',
      'Content-Type: application/json; charset=utf-8',
      'Content-Length: ' + String(chunk.length),
      '',
      chunk,
      '',
    ].join('\r\n');
  });

  return `${chunks.join('')}\r\n-----\r\n`;
};

This works fine with 1.1.4. From going through your code/commit history I can see you have made some changes to how you deal with \r\n', but I have not been able to refactor the above test code in a way that I can get it working with the library.
Any chance you can guide me as to how I need to format the output of createResponseChunks to get it working with the library?

Hi @dylanaubrey thank you so much for choosing to upgrade, and your for using my little library! I appreciate you.
About your issue, is it possible the issue is outside of meros? You mentioned that it used-to work in 1.1.4, and not in 1.1.30. Would be nice to see exactly what the payload is that used to work.
I was able to take your code snippet and this worked for me:
import { meros } from './src/browser';

const createResponseChunks = (responses) => {
	const chunks = responses.map((response) => {
		const chunk = Buffer.from(JSON.stringify(response), 'utf8');

		return [
			'',
			'---',
			'Content-Type: application/json; charset=utf-8',
			'Content-Length: ' + String(chunk.length),
			'',
			chunk,
			'',
		].join('\r\n');
	});

	return `${chunks.join('')}\r\n-----\r\n`;
};

const chunks = createResponseChunks(['a', 'b', 'c']);

const response = new Response(chunks, {
	headers: {
		'content-type': 'multipart/mixed;boundary="-"',
	},
});

const parts = await meros(response);

for await (const part of parts) console.log(part);

Going to close this issue, feel free to comment on here if you're still having issues. I can gladly help!


Add SPSN

Add Stochastic Parallelizable Spiking Neuron model.
Paper:
https://arxiv.org/abs/2306.12666#:~:text=In this paper%2C we propose,run in parallel over time.
Torch implementation:
https://github.com/NECOTIS/Stochastic-Parallelizable-Spiking-Neuron-SPSN/blob/main/neurons/spsn.py

[x] Implement prototype SPSN model
[ ] Ensure implementation is correct
[ ] Determine proper way to write training loop for S4 that follows the philosophy of Haiku/Spyx

https://arxiv.org/abs/2401.00955
Spiking State Space Machine Paper.

A prototype implementation has been implemented in spyx.experimental.
Need to verify the dimensions of internal calculation as right now there's broadcasting issues if the output dimension isn't a multiple/fraction of the input dim.
Training accuracy on SHD comparable to regularly trained recurrent SNNs in Spyx. Performance is comparable to recurrent model at small scales tested locally with short sequences (64). Testing notebook is at research/SPSN.
Considering creating a stochastic Axon class for _SigmoidBernoulli and refactoring it.

[ ] Investigate limiting the sigmoid maximum to <1.0 to prevent extreme firing when oversaturated.

Found this:
Parallel Spiking Unit:
https://arxiv.org/abs/2402.00449


"PHP Warning – yii\base\ErrorException filemtime(): stat failed" for all site scripts

Firstly, the enviroment:
PHP 7.3 x64
Apache 2.4
Windows 10
In some moment, all the scripts display error:
PHP Warning – yii\base\ErrorException
filemtime(): stat failed for [..]\frontend\runtime/cache\2f\2f33462dc35c2b8886f3905ae3ea3939.bin
in C:\OSPanel\domains\vg\vendor\yiisoft\yii2\caching\FileCache.php line 112
if (@filemtime($cacheFile) > time()) {
I added the @file_exists() check:
if (@file_exists($cacheFile) && @filemtime($cacheFile) > time()) {

Actually supressing errors with @ should be dropped in whole code block:
Simple check whether file exists:
if (file_exists($cacheFile) && @filemtime($cacheFile) > time()) {
is better solution IMHO. Supress operator @ not even needed.

is better solution IMHO. Supress operator @ not even needed.
absolutely agree. got carried away by dogs

There are more reasons for failure than non-existing file.

Simple check whether file exists:
if (file_exists($cacheFile) && filemtime($cacheFile) > time()) {
is better solution IMHO. Supress operator @ not even needed.

It is needed. file_exists($cacheFile) && filemtime($cacheFile) > time() is not atomic so you will have race condition: during file_exists($cacheFile) call file exists, but it is deleted right after it and does not exist enymore during filemtime($cacheFile) call. And since we can't rely on file_exists($cacheFile) it is redundant - original code is correct.
If you get such errors, make sure that you don't have scream enabled.


[Key Vault] Merge hotfix/keyvault-verify with main

Description
Merges the latest release branch (which contains the changes from https://github.com/Azure/azure-sdk-for-python/pull/26141) with main.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-keyvault-administration


/etc/apt/auth.conf owner changed endlessly

Starting from Debian 9 and Ubuntu 16.04 the user _apt owns the file /etc/apt/auth.conf.
puppetlabs-apt changes the owner to root and triggers apt update, which will reset the owner to _apt. The next Puppet run changes the owner again and so on.
The attached patch adds the parameter $auth_conf_owner. The parameter defaults to '_apt' or 'root' depending on the Debian or Ubuntu release.

Hey @voegelas thanks for contributing this change. Would it be possible for you to add a test to verify the functionality works. Adding a unit test should suffice. Thanks!

@voegelas Thank you for catching this problem and providing a fix! I completely missed that detail when implementing #752 and noticed the problem only yesterday when we were finally able to move login credentials out of the location URLs and into /etc/apt/auth.conf.

I have created #836 which takes @voegelas great work, rebases the branch on current master and adds spec tests that cover managing the file owner of /etc/apt/auth.conf.

Hey @voegelas . I am closing this PR now in favour of #836 which incorporates your changes along with additional tests. Thanks for spotting this issue and posting the fix!


Add new color concept

The CARGB class is the new color concept. The issue with the regular Color class is that is its data store is inconsistent (float, some bits etc.). To unify and simplify this and make it consistent with the content of the data from, the CARGB has exactly three components (R,G,B) in integer range 0 to 255.

The CARGB class is a new color concept that represents colors using four components: Cyan (C), Alpha (A), Red (R), Green (G), and Blue (B). This class can be particularly useful in graphics and design applications where the color representation needs to incorporate a cyan channel along with the traditional red, green, blue, and alpha channels.


Install instructions did not work on Amazon Linux

[ec2-user@ip-10-192-11-106 firelens-datajet]$ nvm install node
Downloading and installing node v19.1.0...
Downloading https://nodejs.org/dist/v19.1.0/node-v19.1.0-linux-x64.tar.xz...
####################################################################################################################################################################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)

It seems NVM requires glibc 2.27 or 2.28.
Amazon Linux only supports glibc 2.26 at the moment: https://repost.aws/questions/QUrXOioL46RcCnFGyELJWKLw/glibc-2-27-on-amazon-linux-2

Nvm is a real pain to install... You may want to just follow the DockerFile's method of installing node which is not as good because you can't switch between versions of node, but maybe you don't need to worry about that now.
The dockerfile shows how to configure Amazon Linux appropriately.
If you want to test it you can just run make containerjetit, which really doesn't require any prereqs other than docker to be installed


fix: update benchmark command

Goal
The goal of this PR is to update the benchmark command with an additional argument --additional-trie-layers=20.
Closes #1630
Discussion
Due to changes in Polkadot v0.9.38, it is recommended to update the benchmark command.
Checklist

[ ] Chain spec updated
[ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment.
[ ] Design doc(s) updated
[ ] Tests added
[ ] Benchmarks added
[ ] Weights updated

additional notes: https://github.com/paritytech/substrate/pull/11637


passing original user-agent

using original user-agent if a custom user-agent parameter is not provided in url query

If a custom user agent is not passed, we default to our Prerender user agent which is the normal browser user agent (Chrome) + 'Prerender (https://github.com/prerender/prerender'.
I don't think we want to change that behavior currently since most middleware check for "Googlebot" in the user agent so if we started forwarding the Googlebot user agent through it would create an infinite loop of requests.


change timeout through UP-TIMEOUT header. Closes #814

See #814
This change allows the timeout to be increased when calling lambda directly while keeping the timeout specified in the config as a default.
The tests run for 50seconds longer now because that's how long the timeout is set, let me know if I should reduce it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

awesome thanks! I tweaked it a little, I'll QA and get a release out right away

Just uploading v1.6.0, should be up pretty soon

hmm great it's 100mb haha.. Go mod is really messing things up, I'll look into what's causing the bloat


owncloud: We still ship 7.0.*, today 8.2 came out

I'm not using owncloud on nixos (as server instance). Anyways, 7.0.* vs. 8.2 is a word, isn't it?
Ping package maintainers: @pSub @matejc

We already have a PR for this: #10514

Whoops. I'll close this.


Add the ability to use a non standard foreign key in relations

Currently the foreign key has to be the singular of the table name.
I have made changes to allow an array to be passed in as the through model with a reference to the model and the intended foreign key.
In the tests I have added another table called offshore_states. The district still uses the foreign key state_id. The assumed foreign key would be offshore_state_id which would return an sql error. To overwrite this the model reference is put inside an array with the second element being a string the foreign key.
// Stub_Test_Model_City class

    public function offshoreCountry()
    {
        return $this->belongsToThrough(Stub_Test_Model_Country::class,
            [[Stub_Test_Model_Offshore_State::class, 'state_id'], Stub_Test_Model_District::class]);
    }

As you can see the 'through' is inside another array otherwise it would think the given foreign key is another model.
Id love to know your thoughts on this. If you would like I could add this addition to the readme file too.
Danny

:+1: Nice

✊ Happy to help! The cs kicked my arse, first time I have picked a fight with StyleCI 😁

Thanks :smile:
This takes care of that.
composer global require fabpot/php-cs-fixer
php-cs-fixes --level=psr2 *.php


Add nvim-cursorword

Thanks for the PR, but I don't think a separate category is necessary for this. Please move it to an already existing one.

Thanks!


Move toolchain decision making entirely into the tool

This PR is a needed tool change to enable https://github.com/microsoft/vcpkg/pull/22831 and comes with the added benefit of removing duplicate toolchain selection logic across the many helper scripts. With this, ports and helpers may always assume that VCPKG_CHAINLOAD_TOOLCHAIN_FILE is defined to the correct toolchain to pull in.
+@neumann-a for review

as said in https://github.com/microsoft/vcpkg/pull/22831. Do you really want to move it into the tool? I mean the triplet would be the correct location to simply set VCPKG_CHAINLOAD_TOOLCHAIN_FILE. This requires no selection variable at all and would remove any selection code.  Maybe also move the toolchains into the triplet dir (maybe in a subfolder called toolchains). This would make it more visible and obvious for users how vcpkg uses toolchains (scripts/toolchains is kind of an implementation detail for me instead of being user facing which toolchains should be).
I also think that setting VCPKG_CHAINLOAD_TOOLCHAIN_FILE scales better since you don't need to add cases somewhere in the future.
I mean yeah it would be a breaking change for some custom triplets but it would be quite simple to inform users that they need to set VCPKG_CHAINLOAD_TOOLCHAIN_FILE in their custom triplets.

I don't think we can make that breaking change any time soon -- though we could consider making it deprecated. In that light, I think this change is a pure win. Even with this change, we could add VCPKG_CHAINLOAD_TOOLCHAIN_FILE to all of the in-box triplets and everything will work out just fine. It also helps incrementally move us in that direction by allowing all other components in the system to act as though we were already there.

I'm pretty sure this change is what broke a lot of the UWP ports in

https://dev.azure.com/vcpkg/public/_build/results?buildId=67651
https://dev.azure.com/vcpkg/public/_build/results?buildId=67912

Should we revert this for now?

Indeed:
PS C:\Dev\vcpkg> git -C ..\vcpkg-tool rev-parse HEAD
f562635b3b82e70f252844e94767d0907e2f48e9
PS C:\Dev\vcpkg> .\vcpkg.exe x-ci-clean
Starting vcpkg CI clean
Clearing contents of C:\Dev\vcpkg\buildtrees
Clearing contents of C:\Dev\vcpkg\installed
Clearing contents of C:\Dev\vcpkg\packages
Completed vcpkg CI clean
PS C:\Dev\vcpkg> ..\vcpkg-tool\out\build\x64-Debug\vcpkg.exe install expat:x64-uwp --no-binarycaching
Computing installation plan...
The following packages will be built and installed:
    expat[core]:x64-uwp -> 2.4.1
Detecting compiler hash for triplet x64-uwp...
Starting package 1/1: expat:x64-uwp
Building package expat[core]:x64-uwp...
-- Using cached libexpat-libexpat-a28238bdeebc087071777001245df1876a11f5ee.tar.gz.
-- Extracting source C:/Dev/vcpkg-downloads/libexpat-libexpat-a28238bdeebc087071777001245df1876a11f5ee.tar.gz
-- Applying patch pkgconfig.patch
-- Using source at C:/Dev/vcpkg/buildtrees/expat/src/876a11f5ee-539179dcdb.clean
-- Configuring x64-uwp
-- Building x64-uwp-dbg
-- Building x64-uwp-rel
-- Fixing pkgconfig file: C:/Dev/vcpkg/packages/expat_x64-uwp/lib/pkgconfig/expat.pc
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at C:/Dev/vcpkg-downloads/tools/msys2/9a1ec3f33446b195
-- Fixing pkgconfig file: C:/Dev/vcpkg/packages/expat_x64-uwp/debug/lib/pkgconfig/expat.pc
-- Installing: C:/Dev/vcpkg/packages/expat_x64-uwp/share/expat/copyright
-- Performing post-build validation
-- Performing post-build validation done
Installing package expat[core]:x64-uwp...
Elapsed time for package expat:x64-uwp: 28.44 s

Total elapsed time: 33.96 s

The package expat provides CMake targets:

    find_package(expat CONFIG REQUIRED)
    target_link_libraries(main PRIVATE expat::expat)

PS C:\Dev\vcpkg> git -C ..\vcpkg-tool rev-parse HEAD
f3841c4f3e04885a73c4ab9db7b396b1e32f9cb6
PS C:\Dev\vcpkg> .\vcpkg.exe x-ci-clean
Starting vcpkg CI clean
Clearing contents of C:\Dev\vcpkg\buildtrees
Clearing contents of C:\Dev\vcpkg\installed
Clearing contents of C:\Dev\vcpkg\packages
Completed vcpkg CI clean
PS C:\Dev\vcpkg> ..\vcpkg-tool\out\build\x64-Debug\vcpkg.exe install expat:x64-uwp --no-binarycaching
Computing installation plan...
The following packages will be built and installed:
    expat[core]:x64-uwp -> 2.4.1
Detecting compiler hash for triplet x64-uwp...
Starting package 1/1: expat:x64-uwp
Building package expat[core]:x64-uwp...
-- Using cached libexpat-libexpat-a28238bdeebc087071777001245df1876a11f5ee.tar.gz.
-- Extracting source C:/Dev/vcpkg-downloads/libexpat-libexpat-a28238bdeebc087071777001245df1876a11f5ee.tar.gz
-- Applying patch pkgconfig.patch
-- Using source at C:/Dev/vcpkg/buildtrees/expat/src/876a11f5ee-539179dcdb.clean
-- Configuring x64-uwp
-- Building x64-uwp-dbg
-- Building x64-uwp-rel
-- Fixing pkgconfig file: C:/Dev/vcpkg/packages/expat_x64-uwp/lib/pkgconfig/expat.pc
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at C:/Dev/vcpkg-downloads/tools/msys2/9a1ec3f33446b195
-- Fixing pkgconfig file: C:/Dev/vcpkg/packages/expat_x64-uwp/debug/lib/pkgconfig/expat.pc
-- Installing: C:/Dev/vcpkg/packages/expat_x64-uwp/share/expat/copyright
-- Performing post-build validation
The following DLLs do not have the App Container bit set:

    C:/Dev/vcpkg/packages/expat_x64-uwp/debug/bin/libexpatd.dll
    C:/Dev/vcpkg/packages/expat_x64-uwp/bin/libexpat.dll

This bit is required for Windows Store apps.
Found 1 post-build check problem(s). To submit these ports to curated catalogs, please first correct the portfile:
    C:\Dev\vcpkg\ports\expat\portfile.cmake
-- Performing post-build validation done
Installing package expat[core]:x64-uwp...
Elapsed time for package expat:x64-uwp: 5.599 s

Total elapsed time: 11.23 s

The package expat provides CMake targets:

    find_package(expat CONFIG REQUIRED)
    target_link_libraries(main PRIVATE expat::expat)

PS C:\Dev\vcpkg>


google-cloud-sdk: disable gce as a dependency by default (fixes #31369)

Motivation for this change
The commit https://github.com/NixOS/nixpkgs/commit/b241bcf38881be764180c66fa9c713d0d44135c5 made google-compute-engine a dependency for google-cloud-sdk which make it impossible to build google-cloud-sdk on MacOS (https://github.com/NixOS/nixpkgs/issues/31679). In general, google-compute-engine is a package intended for GCE guest images and google-cloud-sdk needs google-compute-engine only when running on GCE.
This commit introduces a new attribute forGceInstance which controls whether google-compute-engine is included as a dependency and is false by default. Moreover, this commit includes the override for this package with forGceInstance set to true in the default NixOS configuration for GCE at nixos/modules/virtualisation/google-compute-image.nix.
Maintainers @stephenmw @zimbatm
Things done

[ ] Tested using sandboxing
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits [CONTRIBUTING.md]

Agreed.
On Wed, 15 Nov 2017 at 22:15, zimbatm<EMAIL_ADDRESS>wrote:

@zimbatm commented on this pull request.
In pkgs/tools/admin/google-cloud-sdk/default.nix
https://github.com/NixOS/nixpkgs/pull/31709#discussion_r151253612:

let

pythonInputs = [ cffi cryptography pyopenssl crcmod google-compute-engine ];

gcePackages = if forGceInstance then [ google-compute-engine ] else [];
pythonInputs = [ cffi cryptography pyopenssl crcmod ] ++ gcePackages;

In that case let's make two top-level packages, google-cloud-sdk and
google-cloud-sdk-gce. Changing the overlay of the GCE image profile seems
a bit too much.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/31709#discussion_r151253612, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAkL0fDns7-etT-LS769LTY_WHKVZBCuks5s21SDgaJpZM4QfUbq
.

--
Sent from Gmail Mobile

I dropped the overlay and added a top level package with gce-enabled as per @zimbatm suggestion. The last commit adds the google-cloud-sdk-gce package to the top-level and Python packages and can be skipped if we don't want to introduce new packages.

BTW, I rewrote the history in my private branch so the initial PRs is not reachable. Is that OK, or it would have been better to revert?

Thanks @ilya-kolpakov !


bevy broken on macOS because of spirv-reflect

spriv-reflect 0.2.3 is broken on macOS 10.15.6 with Apple clang. So is thus bevy.
See this tissue on spriv-reflect.

actually it's just that spriv-reflect doesn't build with sccache. unset RUSTC_WRAPPER and it should work better.
still an issue on spriv-reflect though


Activity logged in wrong project

I'm getting an issue where the activity on chrome is logged as activity on jetbrains editors. In fact I can see urls mixed with files in the entities logged from AndroidStudio.

This is the intended functionality. Since we can't currently detect your project based on browsing activity alone, we assign browsing activity to the last project worked in from an IDE.
More info in #28 and #47.


Argument to set ip address to which to bind. default is <IP_ADDRESS>

Thanks @ldaume, this options is very useful!


GN: Fix MSVC compilation

third_party/BUILD.gn was adding compile flags to suppress failures that
were GCC/Clang specific and caused MSVC to error out. Replace them by
suppression using MSVC's flags.
PTAL @kainino0x @SenorBlanco I verified it passes the MSVC bots in the tryjobs for this CL: https://dawn-review.googlesource.com/c/dawn/+/1220

Thank you!


Unable to put the cursor on info popup

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version: 1.84.2 (Universal)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:52:33.687Z (3 wks ago)
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.2.0

OS Version: Sonoma 14.2

Steps to Reproduce:

Open a file
Put the cursor on a component or element that displays info dialog (pop up)
I cannot put the cursor on the info dialog to click actions or scroll to see complete info.

https://github.com/microsoft/vscode/assets/13439236/1a16c094-4659-4cac-943c-b01112ded935
Any thoughts?
I used the extension bisect to see if it was replicable, and I can reproduce it with the extension bisect activated.

Hi can you please verify the value of your setting editor.hover.sticky? If it is disabled, when the mouse moves away from the token the hover disappears

editor.hover.sticky

Yeah, this solves the issue, im not sure why is it disabled, I set it to true on the settings.json, and works, Thanks a lot!


Fix bool type appearing in GDExtension header

Repetition of the exercise in https://github.com/godotengine/godot/pull/71696 and https://github.com/godotengine/godot/pull/81247.
Since 3 is a good number of times to start automating, I'll look into preventing this.

Eep, sorry! This could be helped by the idea for generating the header from JSON/XML, because we could have a list of allowed types. I'm going to try to explore that in the 4.4 dev cycle if I find the time, although, it's not super high priority.
Anyway, this change looks good! Thanks!

This could be helped by the idea for generating the header from JSON/XML, because we could have a list of allowed types. I'm going to try to explore that in the 4.4 dev cycle if I find the time, although, it's not super high priority.

Just running the header through a C compiler already catches most of these issues, which is what I did in https://github.com/godotengine/godot/pull/96408. Would be nice to have some validation like this soon, because incorrect headers keep breaking downstream projects 😉

Ok to merge?

Ok to merge?

Yes, but also ok to have a weekend :)

Thanks!


Close logwatcher on context cancellation

Signed-off-by: Kenfe-Mickael Laventure<EMAIL_ADDRESS>--
Fixes #30135
This patch addresses 2 issues:

in tailfile() if somehow the logWatcher.Msg were to become full and the watcher closed before space was made into it, we were getting stuck there forever since we were not checking for the watcher getting closed
When servicing docker logs, if the command was cancelled we were not closing the watcher (and hence notifying it to stop copying data)

can you update the commit message, so that it has the description you provided here as PR description?

@thaJeztah done

daemon/logs.go: daemon/logs.go:78:3: function must be invoked in defer statement

@cpuguy83 yes, just realized myself :sweat:

LGTM

Is there any chance that this will make it into a 1.13.x release?

This seems like a pretty low-impact bug that's been around for some time now.

Well, we're currently experiencing the issues described in #30135, which can basically lead to the docker daemon becoming unresponsive.

@jeinwag Have you tested that this fixes your issue?
It's not immediately obvious that this would block daemon operations, but I guess it could if certain streams are never closed.

@cpuguy83 OK, I was unable to reproduce a total freeze, although it has happened before as described in #30135.
What I could reproduce is a "zombie" container which cannot be removed:
docker run -d --name test debian cat /dev/urandom
docker logs test
<Ctrl-C>
docker stop test
docker rm test

Trying to remove the container results in "You cannot remove a running container...", although the process of the container has already terminated.
The only way to get rid of the container is to restart dockerd.
I can confirm that this PR fixes that problem.

 Didn't impact pre-production servers because of much lower level of logging.
 This affects only users of the docker logs endpoint.

@cpuguy83 yes, that's how we trigger the bug, using docker logs and then Ctrl+C while it's still displaying logs.
It doesn't seem to be an issue when there is low loggging activity on the containers and hence not many logs entries written, so this didn't break on our pre-production servers where we test docker upgrades. Once we put 1.13.0 in production it took 2 docker logs commands to bring docker down to its knees, needing a full restart of the docker daemon.
I was able to reproduce the bug on our beta servers:
[root@beta01-docker containers]# docker run -d busybox sh -c "while true; do date; done"
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
4b0bc1c4050b: Pull complete
Digest: sha256:817a12c32a39bbe394944ba49de563e085f1d3c5266eb8e9723256bc4448680e
Status: Downloaded newer image for busybox:latest
f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
[root@beta01-docker containers]# docker logs -f f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
...
Wed Feb  8 17:22:11 UTC 2017
Wed Feb  8 17:22:11 UTC 2017
Wed Feb  8 17:22:11 UTC 2017
Wed Feb  8 17:22:11 UTC 2017
^C
[root@beta01-docker containers]# docker logs -f f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
Wed Feb  8 17:21:43 UTC 2017
...
Wed Feb  8 17:21:55 UTC 2017
Wed Feb  8 17:21:55 UTC 2017
Wed Feb  8 17:21:55 UTC 2017
Wed Feb  8 17:21:55 UTC 2017
Wed Feb  8 17:21:55 UTC 2017
Wed Feb  8 17:21:55 UTC 2017^C
[root@beta01-docker containers]# docker logs -f f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
^C
[root@beta01-docker containers]# docker logs -f f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
^C
[root@beta01-docker containers]# ^C
[root@beta01-docker containers]# docker logs -f f3ac5feedaeb5a3cac50996884dce52f4b07d733b22178289ab260ee22e09f12
^C
[root@beta01-docker containers]# docker ps
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS                                       NAMES
f3ac5feedaeb        busybox                                 "sh -c 'while true..."   4 minutes ago       Up 4 minutes                                                    dreamy_agnesi

After the 2nd ^C the logs stopped responding. Restarting the container cleared the issue. From datadog it seemed that the memory consumption of the container keep ballooning.
I will try to downgrade this host to docker 1.12.5 and see if I can reproduce.

We downgraded one of our beta servers to 1.12.6 -- I can't reproduce the issue anymore. We'll downgrade the production servers today.
When we first saw the issue in production, the issue created by running docker log on a container cascaded to the point that other containers stopped responding to http requests, so I would definitely challenge the assessment that this is low impact.

@tbatchelli Sure. This can't go into .1 (which is imminent), but is considered for .2.

+1.
You guys rock!

Is there any ETA for 1.13.2?

No, nor has been decided if a 1.13.2 will actually be released; see here for our patch release procedures/policy https://github.com/docker/docker/blob/master/project/PATCH-RELEASES.md

You guys rock!


feat(core/event-overlay): add theming

Description
The scope of the changes in this pull request are to add theming support to the event-overlay, which adds theme changes to the pop-over component [core].
Related Issue
SPARK-233818
Motivation and Context
This adds theming to the component as per the requirement for Web Client.
How Has This Been Tested?
Visual testing was done to validate changes
Screenshots:
Default

Dark

Light

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Closing due to duplication in #882


DevTools: profiler crash in this case

Steps to Reproduce:

I followed the steps in https://github.com/microsoft/vscode/issues/107935 to open 3000 dirty editors
I reloaded window
I started JS profiler to measure perf

=> 🐛 the window crashes
Thread 0 (crashed)
 0  libsystem_platform.dylib!_platform_memmove$VARIANT$Haswell + 0xc2
    rax = 0x00007fb1a44ab5e0   rdx = 0x0000000000000006
    rcx = 0x0000000000000000   rbx = 0x00007fb1a44ba470
    rsi = 0x000000000000029c   rdi = 0x00007fb1a44ab5e0
    rbp = 0x00007ffeed0f5730   rsp = 0x00007ffeed0f5730
     r8 = 0x0000000000000000    r9 = 0x000000000000bc60
    r10 = 0x00000000fffffff8   r11 = 0x00007fb1a44ab344
    r12 = 0x000000000000000b   r13 = 0x0000000000000007
    r14 = 0x00007fb1a44ab5e0   r15 = 0x0000000000000006
    rip = 0x00007fff69b3f9c2
    Found by: given as instruction pointer in context
 1  Electron Framework + 0x1291a36
    rbp = 0x00007ffeed0f57d0   rsp = 0x00007ffeed0f5740
    rip = 0x0000000103ddfa36
    Found by: previous frame's frame pointer
 2  Electron Framework + 0xf497c3
    rbp = 0x00007ffeed0f5830   rsp = 0x00007ffeed0f57e0
    rip = 0x0000000103a977c3
    Found by: previous frame's frame pointer
 3  Electron Framework + 0x141028f
    rbp = 0x00007ffeed0f58c0   rsp = 0x00007ffeed0f5840
    rip = 0x0000000103f5e28f
    Found by: previous frame's frame pointer
 4  Electron Framework + 0x142563c
    rbp = 0x00007ffeed0f5910   rsp = 0x00007ffeed0f58d0
    rip = 0x0000000103f7363c
    Found by: previous frame's frame pointer
 5  Electron Framework + 0xf57975
    rbp = 0x00007ffeed0f59a0   rsp = 0x00007ffeed0f5920
    rip = 0x0000000103aa5975
    Found by: previous frame's frame pointer
 6  Electron Framework + 0x12eeb84
    rbp = 0x00007ffeed0f5a10   rsp = 0x00007ffeed0f59b0
    rip = 0x0000000103e3cb84
    Found by: previous frame's frame pointer
 7  Electron Framework + 0x18a5358
    rbp = 0x00007ffeed0f5a38   rsp = 0x00007ffeed0f5a20
    rip = 0x00000001043f3358
    Found by: previous frame's frame pointer
 8  Electron Framework + 0x1839159
    rbp = 0x00007ffeed0f5a78   rsp = 0x00007ffeed0f5a48
    rip = 0x0000000104387159
    Found by: previous frame's frame pointer
 9  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5ab8   rsp = 0x00007ffeed0f5a88
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
10  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5b00   rsp = 0x00007ffeed0f5ac8
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
11  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5b90   rsp = 0x00007ffeed0f5b10
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
12  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5be0   rsp = 0x00007ffeed0f5ba0
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
13  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5c80   rsp = 0x00007ffeed0f5bf0
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
14  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5d48   rsp = 0x00007ffeed0f5c90
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
15  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5d90   rsp = 0x00007ffeed0f5d58
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
16  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5df0   rsp = 0x00007ffeed0f5da0
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
17  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5e48   rsp = 0x00007ffeed0f5e00
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
18  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5e88   rsp = 0x00007ffeed0f5e58
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
19  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5ec8   rsp = 0x00007ffeed0f5e98
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
20  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5f28   rsp = 0x00007ffeed0f5ed8
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
21  Electron Framework + 0x18390d5
    rbp = 0x00007ffeed0f5f80   rsp = 0x00007ffeed0f5f38
    rip = 0x00000001043870d5
    Found by: previous frame's frame pointer
22  Electron Framework + 0x1836c1a
    rbp = 0x00007ffeed0f5fa8   rsp = 0x00007ffeed0f5f90
    rip = 0x0000000104384c1a
    Found by: previous frame's frame pointer
23  Electron Framework + 0x18369f8
    rbp = 0x00007ffeed0f6010   rsp = 0x00007ffeed0f5fb8
    rip = 0x00000001043849f8
    Found by: previous frame's frame pointer
24  Electron Framework + 0xf2ff1c
    rbp = 0x00007ffeed0f6160   rsp = 0x00007ffeed0f6020
    rip = 0x0000000103a7df1c
    Found by: previous frame's frame pointer
25  Electron Framework + 0xf2f366
    rbp = 0x00007ffeed0f61e0   rsp = 0x00007ffeed0f6170
    rip = 0x0000000103a7d366
    Found by: previous frame's frame pointer
26  Electron Framework + 0xe20728
    rbp = 0x00007ffeed0f6300   rsp = 0x00007ffeed0f61f0
    rip = 0x000000010396e728
    Found by: previous frame's frame pointer
27  Electron Framework + 0x40d19e6
    rbp = 0x00007ffeed0f6410   rsp = 0x00007ffeed0f6310
    rip = 0x0000000106c1f9e6
    Found by: previous frame's frame pointer
28  Electron Framework + 0x4162730
    rbp = 0x00007ffeed0f64a0   rsp = 0x00007ffeed0f6420
    rip = 0x0000000106cb0730
    Found by: previous frame's frame pointer
29  Electron Framework + 0x4162830
    rbp = 0x00007ffeed0f6510   rsp = 0x00007ffeed0f64b0
    rip = 0x0000000106cb0830
    Found by: previous frame's frame pointer
30  Electron Framework + 0x487c18f
    rbp = 0x00007ffeed0f65e0   rsp = 0x00007ffeed0f6520
    rip = 0x00000001073ca18f
    Found by: previous frame's frame pointer
31  Electron Framework + 0x48ae0f3
    rbp = 0x00007ffeed0f6620   rsp = 0x00007ffeed0f65f0
    rip = 0x00000001073fc0f3
    Found by: previous frame's frame pointer
32  Electron Framework + 0x482a437
    rbp = 0x00007ffeed0f6650   rsp = 0x00007ffeed0f6630
    rip = 0x0000000107378437
    Found by: previous frame's frame pointer
33  Electron Framework + 0x4fa56f4
    rbp = 0x00007ffeed0f6800   rsp = 0x00007ffeed0f6660
    rip = 0x0000000107af36f4
    Found by: previous frame's frame pointer
34  Electron Framework + 0x4fa8f92
    rbp = 0x00007ffeed0f6820   rsp = 0x00007ffeed0f6810
    rip = 0x0000000107af6f92
    Found by: previous frame's frame pointer
35  Electron Framework + 0x49c1f9c
    rbp = 0x00007ffeed0f68b0   rsp = 0x00007ffeed0f6830
    rip = 0x000000010750ff9c
    Found by: previous frame's frame pointer
36  Electron Framework + 0x380aed8
    rbp = 0x00007ffeed0f69a0   rsp = 0x00007ffeed0f68c0
    rip = 0x0000000106358ed8
    Found by: previous frame's frame pointer
37  Electron Framework + 0x380a2cd
    rbp = 0x00007ffeed0f69e0   rsp = 0x00007ffeed0f69b0
    rip = 0x00000001063582cd
    Found by: previous frame's frame pointer
38  Electron Framework + 0x285b2af
    rbp = 0x00007ffeed0f6a90   rsp = 0x00007ffeed0f69f0
    rip = 0x00000001053a92af
    Found by: previous frame's frame pointer
39  Electron Framework + 0x286b48a
    rbp = 0x00007ffeed0f6b60   rsp = 0x00007ffeed0f6aa0
    rip = 0x00000001053b948a
    Found by: previous frame's frame pointer
40  Electron Framework + 0x286b219
    rbp = 0x00007ffeed0f6bb0   rsp = 0x00007ffeed0f6b70
    rip = 0x00000001053b9219
    Found by: previous frame's frame pointer
41  Electron Framework + 0x28bbdd1
    rbp = 0x00007ffeed0f6bd0   rsp = 0x00007ffeed0f6bc0
    rip = 0x0000000105409dd1
    Found by: previous frame's frame pointer
42  Electron Framework + 0x28b756a
    rbp = 0x00007ffeed0f6be0   rsp = 0x00007ffeed0f6be0
    rip = 0x000000010540556a
    Found by: previous frame's frame pointer
43  Electron Framework + 0x28bb69f
    rbp = 0x00007ffeed0f6c20   rsp = 0x00007ffeed0f6bf0
    rip = 0x000000010540969f
    Found by: previous frame's frame pointer
44  CoreFoundation!__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 0x11
    rbp = 0x00007ffeed0f6c30   rsp = 0x00007ffeed0f6c30
    rip = 0x00007fff2f8b2d52
    Found by: previous frame's frame pointer
45  CoreFoundation!__CFRunLoopDoSource0 + 0x67
    rbp = 0x00007ffeed0f6c60   rsp = 0x00007ffeed0f6c40
    rip = 0x00007fff2f8b2cf1
    Found by: previous frame's frame pointer
46  CoreFoundation!__CFRunLoopDoSources0 + 0xd1
    rbp = 0x00007ffeed0f6cd0   rsp = 0x00007ffeed0f6c70
    rip = 0x00007fff2f8b2b0b
    Found by: previous frame's frame pointer
47  CoreFoundation!__CFRunLoopRun + 0x39f
    rbp = 0x00007ffeed0f79e0   rsp = 0x00007ffeed0f6ce0
    rip = 0x00007fff2f8b183a
    Found by: previous frame's frame pointer
48  CoreFoundation!CFRunLoopRunSpecific + 0x1ce
    rbp = 0x00007ffeed0f7a70   rsp = 0x00007ffeed0f79f0
    rip = 0x00007fff2f8b0e3e
    Found by: previous frame's frame pointer
49  Foundation!-[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 0xd4
    rbp = 0x00007ffeed0f7ab0   rsp = 0x00007ffeed0f7a80
    rip = 0x00007fff31f4c1c8
    Found by: previous frame's frame pointer
50  Electron Framework + 0x28bc2f1
    rbp = 0x00007ffeed0f7af0   rsp = 0x00007ffeed0f7ac0
    rip = 0x000000010540a2f1
    Found by: previous frame's frame pointer
51  Electron Framework + 0x28bb052
    rbp = 0x00007ffeed0f7b30   rsp = 0x00007ffeed0f7b00
    rip = 0x0000000105409052
    Found by: previous frame's frame pointer
52  Electron Framework + 0x286ba13
    rbp = 0x00007ffeed0f7b60   rsp = 0x00007ffeed0f7b40
    rip = 0x00000001053b9a13
    Found by: previous frame's frame pointer
53  Electron Framework + 0x2842e23
    rbp = 0x00007ffeed0f7bf0   rsp = 0x00007ffeed0f7b70
    rip = 0x0000000105390e23
    Found by: previous frame's frame pointer
54  Electron Framework + 0x5dbf0f9
    rbp = 0x00007ffeed0f7cb0   rsp = 0x00007ffeed0f7c00
    rip = 0x000000010890d0f9
    Found by: previous frame's frame pointer
55  Electron Framework + 0x1ab2ba9
    rbp = 0x00007ffeed0f7d20   rsp = 0x00007ffeed0f7cc0
    rip = 0x0000000104600ba9
    Found by: previous frame's frame pointer
56  Electron Framework + 0x40380e8
    rbp = 0x00007ffeed0f8070   rsp = 0x00007ffeed0f7d30
    rip = 0x0000000106b860e8
    Found by: previous frame's frame pointer
57  Electron Framework + 0xd32b74
    rbp = 0x00007ffeed0f8100   rsp = 0x00007ffeed0f8080
    rip = 0x0000000103880b74
    Found by: previous frame's frame pointer
58  Electron Framework + 0x2d94
    rbp = 0x00007ffeed0f8190   rsp = 0x00007ffeed0f8110
    rip = 0x0000000102b50d94
    Found by: previous frame's frame pointer
59  Code - OSS Helper (Renderer) + 0x18a5
    rbp = 0x00007ffeed0f8260   rsp = 0x00007ffeed0f81a0
    rip = 0x0000000102b088a5
    Found by: previous frame's frame pointer
60  libdyld.dylib!start + 0x1
    rbp = 0x00007ffeed0f8270   rsp = 0x00007ffeed0f8270
    rip = 0x00007fff69949cc9
    Found by: previous frame's frame pointer

It is https://github.com/microsoft/vscode/issues/101350 , the fix for this in OSS electron only went in 9.3.0 while the internal fix is available with 9.2.1. So if you are taking profile from OSS vscode then the crash would be present.
I have not decided whether to push for 9.3.x this iteration, will take a call tomorrow after finishing up house-keeping.


How to use AMP versions of Jekyll posts?

Checklist

[x] I have read the newlest tutorials and know the correct effect of the functional design.
[x] There is no similar question on existing issues (including closed ones).
[x] I have tried to find the answer on Jekyll Forum and StackOverflow.
[x] My question is based on the latest code of the master branch.

Description
I have tried using the amp-jekyll plugin but the permalink is not generating correctly and showing an error.

@cotes2020 @NichtsHsu

Can anyone help with this issue?


Project : Real Time chatting App - React , Socket , MongoDB

I hope you will assign this issue to me , As I will push my project to your repo and look  for further contribution to this repo.

@raj-mistry-01 I've assigned you for this task,
Reminder: After contributing, kindly update the index.html file to reflect your project on the project showcase page. Also, don't forget to add a logo for your project to improve its visibility on the repository webpage. Thank you

add to project.js file
example:
{
title: "React Todo App",
url: "https://github.com/ianshulx/React-projects-for-beginners/tree/main/react-todo-app",
description: "Start your coding journey with a beginner-friendly React Todo App, perfect for learning task management and basic web development",
imgSrc: "assets/todo.png"
},

@ianshulx
Thank you for assigning this issue to me .

@raj-mistry-01 can you please list it project.js with a logo


Initial boot takes a while on XenServer

Here's a screenshot of the console, this step can take a few minutes.

This is already covered by #423 & #451.  I believe this is related to the initial DHCP lookup.


Record how evidence is generated

Overview
During an audit, an auditor often asks an auditee to provide a screen shot to show an evidence is generated. A fetcher should have an ability to track which APIs and parameters are used to generated the evidence. This feature is part of chain of custody in digital forensics.
Requirements

Record API calls including method, endpoint, and parameters
Associate the sequence of the API calls with the evidence
Prevent the chain of custody from being modified

Approach
We could leverage locker or add a new component for forensics. We then update a service function to record the sequence of the API calls while generating the evidence. At the fetcher class level , we can update the object for forensics with the output from the service function.
Security and Privacy
The sequence of the API calls could expose sensitive data. The protection or masking of the data is required.
Test Plan
We can utilize the sequence of the API calls to produce an evidence and compare it with the evidence in a file.

This is an interesting proposal but I'm not sure that we can build something that guarantees the "chain of custody" you mention as the premise for this issue.  For instance, tracking the API calls made to gather a piece of evidence doesn't track possible manipulation of that evidence by fetcher code prior to adding that evidence to a locker.  This breaks that "chain of custody" premise.
However, a limited form of "chain of custody" may be of some value.  I think one thing that could be done is to track the fetcher used to gather an evidence in the index.json evidence metadata.  This is something we don't do today but it would be fairly easy to implement.  Another possibility could be to leverage the fetcher's session method to track those API calls and store them in the index.json evidence metadata.  This of course relies on the author of the fetcher using the session object rather their own request mechanism to ensure chain of custody.  Doing this may have some value although does introduce a pretty significant technical challenge when dealing with fetchers that gather multiple pieces of evidence.  Finally, I suppose you could build a general metadata update method on the ComplianceFetcher that allows a fetcher author to add whatever evidence metadata they wish which could include chain of custody API call content but TBH that seems a bit hacky.
Like I said, this is an interesting proposal and perhaps I'm just looking at things with blinders on.  So if you have other ideas that I didn't touch upon I'd love to hear them.

@alfinkel Thank you for your insight. I agree with your points. We could not track all data manipulations. Recording how we gather data in text (at a fetcher class), API endpoints, parameters, and the timestamps (at a service function) would be valuable for audits. Based on your explanation, using a fetcher's session would be a solution so that we can  track those API calls and store them in the index.json evidence metadata.
Referring to etch_recent_pull_requests.py, RepoCommitEvidence should be used to updated index.json. Should we pass the RepoCommitEvidence's object to the service function?

Referring to etch_recent_pull_requests.py, RepoCommitEvidence should be used to updated index.json. Should we pass the RepoCommitEvidence's object to the service function?

Sorry I don't know what fetch_recent_pull_requests.py is and I'm not sure I follow what service function you're referring to.

Thank you for your quick response, Al. I am sorry for confusion. I referred to this file. When  GithubRepoCommitsFetche gets evidence in JSON format, it will call github.get_commit_details. The function get_commit_details is under services folder so I called it a service function. Please kindly let me know how we should call them so that we use the same terms. Thank you again for your help.

closing...


UNKNOWN_ERROR on send every time.

Just genuinely curious if this lib works anymore - I am noticing that Implicit Workflow works perfectly, but if I use this omniauth method I instantly get 'UNKNOWN_ERROR' on Discords side. However the console never gets a response, just initiates it. Is this gem still presently working?

Closing this issue as it was an issue on Discord's side. Checking XHR made it obvious of the issue. For future notice: Deleting and re-adding your RedirectUI resolved it.

@dnorthrupva What did you mean by Deleting and re-adding your RedirectUI resolved it.?
From I can see I am getting an error because the gem takes localhost instead of <IP_ADDRESS>, but trying to overwrite it in the initializer with callback_path, but it just gets added on top of the gem redirect url


Editing table bug

If hit cancel on prompt, then name will show up as a null cell in the table despite logic trying to prevent no null values

Resolved. Was saying variables !== null ... but should have been !== ''


chore: allow Hyperscript.jl 0.0.5

Allows using Hyperscript 0.0.5. I hope it's not too much of a breaking change

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.

booooo


SettingsService Problems with SettingsHelper and StringHelper

Hi,
i started with Template 10 since a few days and i think i found three problems with the SettingsService. In my case strings or integers are not saved and loaded properly.
StringHelper.cs (see Comments in Code, the old codelines are commented out, i added my solution)
public IEnumerable<string> BreakString(string value, int size = 8000)
{
    if (string.IsNullOrEmpty(value))
    {
        return new[] { string.Empty };
    }
    var slices = Math.Ceiling((decimal)value.Length / size);
    //old version:
    //return Enumerable.Range(0, value.Length / size).Select(i => value.Substring(i * size, size));
    //Issue 1: End of the range must be rounded up and size of the last (or the first if size > value.Length
    //string must be calculated, otherwise it results in an error
    //For the last slice he calculates the rest of the json string
    return Enumerable.Range(0, (int)slices).
               Select(i => value.Substring(i * size, slices - 1 == i ? (value.Length % size != 0 ? value.Length % size : size) : size));
        }

SettingsHelper.cs (see Comments in Code, the old codelines are commented out, i added my solution
private ApplicationDataCompositeValue StringToPartsContainer(string converted)
        {
            var container = new ApplicationDataCompositeValue();
            var parts = _helper.BreakString(converted, max_setting_length);
            //old version
            //foreach (var part in parts.Select((i, x) => new { Index = i, Value = x }))
            //Issue 2: Index and Value are switched, i changed both
            foreach (var part in parts.Select((x, i) => new { Index = i, Value = x }))
            {
                container[$"Part{part.Index}"] = part.Value;
            }
            return container;
        }

private string StringFromPartsContainer(ApplicationDataCompositeValue container)
        {
            var keys = container.Keys.Where(x => x.StartsWith("Part"));
            //old version
            //var parts = container.Where(x => keys.Contains(x.Key)).OrderBy(x => x.Key).Select(x => x.Value);
            //Issue 3: Because of the Part Substring in the key, the list gets ordered like Part1 Part10 Part11 Part 12 Part 2
            //I removed it because the list is already ordered, otherwise use a comparer which supports natural sort
            var parts = container.Select(x => x.Value);
            return string.Concat(parts.ToArray());
        }

Could you please confirm these issues? Is it possible to push some stuff?
Best Regards
Andre

Sure thing. Care to create a Pull Request?

Hi Jerry,
of course! I´ll create till end of this week!
Best Reagards
Andre

Please target the 13 branch


Training error

There's an error in the Start Dreambooth cell as soon as you start training.

Marking as closed, this was an issue with using the wrong url.


Remove one-off debug_cap.

It is odd that this is the only get_instance that has debug_cap, and I can't find any usage of it.

Thanks. This was before my time... isn't needed any more since we have --max-eval-instances


recorded/2 with variables and ;/2

Following code work incorrectly in Trealla, code simplified from https://bitbucket.org/bunny351/prolog/src/11ecf1b6a865e9a0eac9d5a708e4599855bda1c1/process.pl?#process.pl-238:247:
:- initialization(main).

main :-
        recordz(foo, a(b, C)),
        recorded(foo, X),
        (recorded(foo, Y) ; Y = true),
        write(X), nl,
        write(Y), nl,
        halt.

Output:
% tpl foo.pro
a(b,recorded(foo,a(b,C)))
a(b,C)

Seems still have problem, adding X = Y will cause segmentation fault:
:- initialization(main).

main :-
        recordz(foo, a(b, C)),
        recorded(foo, X),
        (recorded(foo, Y) ; Y = true),
        X = Y,
        write(X), nl,
        write(Y), nl,
        halt.

Backtrace:
Core was generated by `tpl issues/0220.pro'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000055a894f53f8e in bind_vars (q=0x55a897121550, point1=4294967295, point2=4294967295) at src/jela.c:552
552             point1 -= q->envs[point1].binding;
(gdb) bt
#0  0x000055a894f53f8e in bind_vars (q=0x55a897121550, point1=4294967295, point2=4294967295) at src/jela.c:552
#1  0x000055a894f54326 in unify_atomic (q=0x55a897121550, term1=0x55a897122200, context1=4294967295, term2=0x55a897122200,
    context2=4294967295) at src/jela.c:626
#2  0x000055a894f54970 in unify_compound (q=0x55a897121550, term1=0x55a897122200, context1=4294967295, term2=0x55a897122200,
    context2=4294967295) at src/jela.c:712
#3  0x000055a894f54a22 in unify (q=0x55a897121550, term1=0x55a897124d20, context1=4294967295, term2=0x55a897124d20,
    context2=4294967295) at src/jela.c:728
#4  0x000055a894f22693 in bif_iso_unify (q=0x55a897121550) at src/bifs_iso.c:618
#5  0x000055a894f53cc7 in call (q=0x55a897121550) at src/jela.c:473
#6  0x000055a894f53e9e in run_me (q=0x55a897121550) at src/jela.c:525
#7  0x000055a894f139f2 in query_run (q=0x55a897121550) at src/trealla.c:935
#8  0x000055a894f1502f in trealla_run_query (pl=0x55a8970ff010, src=0x55a897107880 "main.") at src/trealla.c:1425
#9  0x000055a894f14c75 in trealla_consult_file (pl=0x55a8970ff010, filename=0x7ffd120167d7 "issues/0220.pro")
    at src/trealla.c:1329
#10 0x000055a894f1041c in main (ac=2, av=0x7ffd12015da8) at tpl.c:363
(gdb)

Still have problem for tests/0062-recorddb.pl, e.g. following tracing output is incorrect.
Call: ((foreign_call(db_create(record_db, 3001, _428060)),global_set(record_db, _428060))=.._429140)
Exit: ((foreign_call(db_create(record_db, 3001, _428060)),global_set(record_db, _428060))=..[',',foreign_call(db_create(record_db, 3001, (foreign_call(db_create(record_db, 3001, _428060)),global_set(record_db, _428060)))),global_set(record_db, _428060)])

Not sure if it is still related to this issue. I'll close it for now.

Managed to simplify an test case for tests/0062-recorddb.pl problem:
:- initialization(main).

main :-
        L0 = [a, (b(_), c(_))],
        T0 =.. L0,
        recorda(foo, T0),
        recorded(foo, T1),
        T1 =.. L1,
        write(L0), nl,
        write(L1), nl,
        halt.

Output:
% tpl foo.pro
[a,(b(_),c(_))]
[a,(b([a,(b(_),c(_))]),c(_))]

Reopen this issue.

Test of tests/0062-recorddb.pl finally passed, thanks.


Changing SnackBar's default vertical padding

Make "_singleLineVerticalPadding" a changeable property of SnackBar.
Fixes: #77333
Pre-launch Checklist

[ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[ ] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[ ] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

@Piinks It may destroy the UI for the SnackBars that depends on the

I am going to run this through google testing to see if this kind of change breaks anything - the simplest fixes have a knack for wreaking havoc 😉

It may destroy the UI for SnackBars that depends on the _singleLineVerticalPadding.

Can you check the failing tests here? It looks like your branch may just need to be updated.

Understood.

(triage) @rickimaru18 would you like to continue with this change?

@Piinks
Sorry for the late reply. I'll try to update the doc comments for padding. :bow:


python311Packages.pulumi-aws: 6.37.0 -> 6.38.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pulumi-aws is: Pulumi python amazon web services provider
meta.homepage for python311Packages.pulumi-aws is: https://github.com/pulumi/pulumi-aws
meta.changelog for python311Packages.pulumi-aws is: https://github.com/pulumi/pulumi-aws/releases/tag/v6.37.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.37.1 in filename of file in /nix/store/x1z1mjg587ir42v443vl74mpsm4ljr3k-python3.11-pulumi-aws-6.37.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.pulumi-aws
python312Packages.pulumi-aws

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x1z1mjg587ir42v443vl74mpsm4ljr3k-python3.11-pulumi-aws-6.37.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pulumi-aws https://github.com/r-ryantm/nixpkgs/archive/0bd38560d894ae4aecbe7fde736210ce545a66a3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0bd38560d894ae4aecbe7fde736210ce545a66a3#python311Packages.pulumi-aws

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x1z1mjg587ir42v443vl74mpsm4ljr3k-python3.11-pulumi-aws-6.37.1
ls -la /nix/store/x1z1mjg587ir42v443vl74mpsm4ljr3k-python3.11-pulumi-aws-6.37.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

python311Packages.pulumi-aws
python311Packages.pulumi-aws.dist
python312Packages.pulumi-aws
python312Packages.pulumi-aws.dist

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.pulumi-aws is: Pulumi python amazon web services provider
meta.homepage for python311Packages.pulumi-aws is: https://github.com/pulumi/pulumi-aws
meta.changelog for python311Packages.pulumi-aws is: https://github.com/pulumi/pulumi-aws/releases/tag/v6.38.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.38.0 in filename of file in /nix/store/p7x648w62h3wg5615gnkvhzdxg3833la-python3.11-pulumi-aws-6.38.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.pulumi-aws
python312Packages.pulumi-aws

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p7x648w62h3wg5615gnkvhzdxg3833la-python3.11-pulumi-aws-6.38.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.pulumi-aws https://github.com/r-ryantm/nixpkgs/archive/ba890e6d9344c4ec65910d77734028c586e9cfe0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ba890e6d9344c4ec65910d77734028c586e9cfe0#python311Packages.pulumi-aws

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p7x648w62h3wg5615gnkvhzdxg3833la-python3.11-pulumi-aws-6.38.0
ls -la /nix/store/p7x648w62h3wg5615gnkvhzdxg3833la-python3.11-pulumi-aws-6.38.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

python311Packages.pulumi-aws
python311Packages.pulumi-aws.dist
python312Packages.pulumi-aws
python312Packages.pulumi-aws.dist

Maintainer pings


feature/tree diff implementation

This change is

Codecov Report

Merging #1066 (9748bf5) into master (f7130c3) will increase coverage by 0.22%.
The diff coverage is 74.72%.

@@            Coverage Diff             @@
##           master    #1066      +/-   ##
==========================================
+ Coverage   46.65%   46.88%   +0.22%
==========================================
  Files         158      161       +3
  Lines       12726    12813      +87
==========================================
+ Hits         5937     6007      +70
- Misses       6036     6052      +16
- Partials      753      754       +1

Impacted Files
Coverage Δ

graveler/committed/tree/committed.go
0.00% <0.00%> (ø)

graveler/graveler.go
33.64% <0.00%> (+0.47%)
:arrow_up:

graveler/diff.go
81.13% <81.13%> (ø)

graveler/committed/tree/duplicates.go
100.00% <100.00%> (ø)

catalog/mvcc/cataloger_create_entry.go
100.00% <0.00%> (+5.26%)
:arrow_up:

Continue to review full report at Codecov.

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


use honeycomb marker API on deployment

Honeycomb supports markers which will display in all charts to display global events. One thing that might be helpful for is when we deploy a new version to prod, we can create a marker in honeycomb.
https://docs.honeycomb.io/api/tag/Markers/

I figured out how to track server instance ID and use a trigger in honeycomb to create a marker for us, so we don't need to do this ourselves now


Formatting CREATE INDEX statement

Unformatted:
CREATE INDEX c$idx_1 ON configuration (key);
CREATE INDEX c$idx_2 ON configuration (owner);
CREATE INDEX c$idx_3 ON configuration (scope);
CREATE INDEX c$idx_4 ON configuration (key, namespace, owner);
CREATE INDEX c$idx_5 ON configuration (key, namespace, owner, scope);
CREATE INDEX c$idx_6 ON configuration (id, key, namespace, owner, scope);

Expected:
CREATE INDEX c$idx_1 ON configuration (key);
CREATE INDEX c$idx_2 ON configuration (owner);
CREATE INDEX c$idx_3 ON configuration (scope);
CREATE INDEX c$idx_4 ON configuration (key, namespace, owner);
CREATE INDEX c$idx_5 ON configuration (key, namespace, owner, scope);
CREATE INDEX c$idx_6 ON configuration (
    id,
    key,
    namespace,
    owner,
    scope
);

Reality:
CREATE INDEX c$idx_1 ON
    configuration (
        key
    );

CREATE INDEX c$idx_2 ON
    configuration (
        owner
    );

CREATE INDEX c$idx_3 ON
    configuration (
        scope
    );

CREATE INDEX c$idx_4 ON
    configuration (
        key,
        namespace,
        owner
    );

CREATE INDEX c$idx_5 ON
    configuration (
        key,
        namespace,
        owner,
        scope
    );

CREATE INDEX c$idx_6 ON
    configuration (
        id,
        key,
        namespace,
        owner,
        scope
    );

I'd be OK with having
CREATE INDEX c$idx_5 ON

on one line and the rest on other, but again based on number of cols , keep the cols on 1 line with the table if there are no more than 4, i.e.
CREATE INDEX c$idx_5 ON
    configuration (key, namespace, owner, scope);

But best for me (again personal preference) would be to keep the whole index definition on one line (including table and cols) if num_cols <= 4 (as in the 'Expected:' snippet)

Similar case as in #27. See advice there.

The formatting result looks consistent. Hence I close this issue.


Why is this called PointRCNN? what is RCNN here

I dont see any convolution operation,  hence just curious on what does the name mean.

Actually the shared MLP are implemented by the convolution with kernel size 1x1. Also, PointNet++ is only an alternative backbone for the PointRCNN, and PointRCNN could also use other convolution based backbones to extract point-wise features and adopt our proposed two-stage 3D detection pipeline, which is consistent with the name PointRCNN.


arangoimp csv ignores last line if not followed by \n

ArangoDB v3.1.12
csv file that imports only the first entry
_key,xx,blarg
"499999",1,"blub"
"499998",1,"blub"

csv file that imports both entries
_key,xx,blarg
"499999",1,"blub"
"499998",1,"blub"

Note that vim will add independently a newline. Check with cat or xxd for a newline at the end of the file.
arangoimp cmd:
./build/bin/arangoimp --collection testcsv --create-collection true \
 --separator , --type csv test.csv

Fixed in 3.1 and devel.
By the way, I prefer using vim with set noeol for saving and hexdump -C for checking.

ArangoDB 3.1.13 is available for download.


Removed cyclic options on Curve plots

Curve plots have various options to apply very specific operations to cyclic Curve data including centering it on the highest value, applying relative labels and formatting radian values as degrees. These options were inherited from old topographica plotting code and made sense in that context, however within the general framework of holoviews they don't make much sense and are better implement as operations on the data and by setting the formatter or ticks directly. The other issue is that these options were broken when applied to Curves in Overlays. This PR removes these options.

Seems reasonable as I don't think anyone would have been using this...especially as it wasn't documented. I agree this is worth removing especially as it was broken!
I understand it is ready to merge and the tests are passing so I'll do that now.

Renamed, since it removes these options, it doesn't just deprecate them.
At least for tuning curve plots in Topographica, it's important to be able to center them, so is that code moving to Topographica?

I've added a center_cyclic operation to featuremapper. I can move it  to or make it available somewhere in topographica as well though.

Featuremapper sounds like a good place for that.


bump manually

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Bump conda-forge version manually by following
https://stackoverflow.com/questions/42552816/introduce-new-python-version-to-conda-forge-feedstock

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


DISTX-41 Implementing business metrics collection for Datahub and Dat…

…alake clusters

The usage event schema is defined in thunderhead repo.
The schema protobuf file is fetched from git in gradle and compiled using java.
The usage reporter interface and implementation will be used in appropriate place in this repo.
Build and checked that it works fine.
This is my first PR to this repo, will add the instrumentation after this PR is merged.
Add necessary steps to make sure that gradle builds properly in all environments.

I have reverted the code now. Can you please copy the corresponding proto files rather than downloading them on-the-fly?

Hi @keyki,
Thanks for the merge and revert. Could you please give a little more color on the revert part. Is the build runs in a place where it does not have access to GitHub? Or dynamic fetching made the build unstable.
I preferred to fetch the file instead of checking in because that way it is easier to make the changes. This file is going to be heavily edited as more use-cases are added. It is cumbersome to make changes in two places.
Thanks,
Ganesh

Hi,
We copy the proto files here, because this is a public repository and ppl cannot build it outside of the VPN. Also I'm not sure if there are frequent changes in the proto file would break the builds randomly.

Hi @keyki,
Thanks for the reply. I agree about the public repository part. Also the idea is to use a fixed hash to fetch the file. If there is a cloudbreak related change - then change the hash and then use that new changes in the code. So it will not break builds randomly and still allows us to move to new version.
Thanks,
Ganesh


Missing dependency installation for testing orbitize

Facing several errors while testing the orbitize git repo when following instructions in here. Noticed there is a missing pip install -r requirements.txt command which makes it work then.

Thanks! Fixed in commit 811807d


[hbase] Add kerberos authentication for HBase binding

Continue unfinished pull request #333. Rebase on master branch, and add Kerberos authentication to HBaseClient10.java .

Thanks for working on this!
I believe this gor fixed in #591. Please reopen if it doesn't work in your case.


Fix CS for Email

Description
This only does the fixing of code style within the Email class to make it less stuffy to read and not the big refactor as originally envisioned.
Checklist:

[x] Securely signed commits
[x] Conforms to style guide

Nice cleanup! I always wondered what to do with spacing on lines with = followed by .= += etc.... This seems to suggest you ignore their indentation

Because the Email class heavily used short circuiting expressions, some are out of view in my IDE due to line length so I have to add an intervening line to re-align those.


Link for BN-Inception

Thank you for your great work! I am trying to extract features by myself and the link for BN-Inception is currently not working. Could you please update the link? Thank you so much!

The PyTorch code of BN-Inceptioin can be found here: https://github.com/amazon-science/stochastic-backpropagation/blob/cvpr2022/src/lstr/models/backbones/bninception.py.

Thank you so much!

Why conv1_7x7_s2.weight is shape torch.Size([64, 10, 7, 7]) instead of ([64, x, 7, 7]) (x <= 3) ?