Device Apps are being replace but not restored back

This module replaces the existing apps in the system (Like styles, pixel launcher, dialer) but doesn't restore them when a feature is turned off or when the module is removed from magisk.
I used this module and tuned on styles by the module when I did a reboot, the money engine's colour palette  didn't show up
(even after I cleared data for styles app)
When I removed the module There was no styles app installed on my device, I couldn't even change wallpaper.
This shouldn't happen in magisk, system-less right?
Any possible way to fix this? without using this module

It shouldn't happen. Idk the reason why it removes. I need to check it.

@Kingsman44 The apps don't restore after reflashing the ROM, nor after removing magisk
After reflashing the ROM the apps should come back, but that's not the case
Here something different is going on.

This should be fixed on pixelily v2
feel free to reopen or create new issue if doesn't


Buttons, please

it would also be nice to have $buttonbackgroundcolor and $buttontextcolor variables

To add to the above, some WCAG 2.0 AA tools complain about having either foreground or background color defined but not the other, so it's good to have both defined for elements like the button.

Ok. commencing work on this issue.

we should amend the simple-button mixin in _forms.scss to accept background colors, and use the defaults @beefoo is requesting

@mgiraldo working on this presently.

moved to https://github.com/NYPL/design-toolkit/issues/5


[VMR] Linux Vertical Build PoC

Objective
As part of https://github.com/dotnet/arcade/blob/main/Documentation/UnifiedBuild/UB-Roadmap.md, we want to produce vertical builds for linux-x64 and linux-arm64 in order to flush out any problematic areas and continue to shape our VMR approach for .NET 9.
Outcomes

[ ] The PoC can produce the customer facing artifacts that .NET produces in its current official build (or we know we can produce such an artifact by completing a specified set of work).
[ ] Issues are filed providing a clear path between the PoC and productization of the VMR vertical
[ ] A rolling CI leg is added to the VMR to identify breaks in the PoC

Work Items

[ ] https://github.com/dotnet/source-build/issues/3654
[ ] https://github.com/dotnet/source-build/issues/3671 - in order to target arm64 and other architectures different from the build host
[ ] Build linux-x64
[ ] Build linux-arm64
[ ] Build linux-arm
[ ] Add CI legs for linux-x64, linux-arm, and linux-arm64

@steveisok Can we close this out at this point?

Closing as agreed with @steveisok


Slow autocomplete

I would use your lib for multiple select but the autocompletion is too slow (takes a fraction of seconds)

Autocomplete is not a part of this library. For any complaints go to jquery ui autocomplete ;)


switch to RobotoMono font

The Lucida fonts are not included with OpenJDK and have been
removed from OracleJDK in version 11. The RobotoMono family
is Apache licensed and will now be used as the default to get
a more consistent experience across JDK versions.

For more context: https://www.oracle.com/technetwork/java/javase/11-relnote-issues-5012449.html#JDK-8191522


fix(ioredis): fix reconnectOnError assignation on Redis connection options

Information

Type
Breaking change

Fix
No

Summary by CodeRabbit

Refactor

Updated the configuration of the connection settings for improved database connectivity stability.

:tada: This PR is included in version 7.67.7 :tada:
The release is available on:

v7.67.7
GitHub release

Your semantic-release bot :package::rocket:


Mac Installer does not work in Mojave and prior systems.

Still on Mojave here for various reasons, and the Mac installer does not work on that platform. When you double click on it (and the icon has the usual greyed out overlay, so you should know it won’t work) you get told that it’s not compatible.
There is a workaround:
1 - Right-click on the application bundle and select Show Contents
2 -Open the Contents folder, and then the MacOS Folder.
3 - Double-click on the bteinstaller file
4 >> The installer will open Terminal and run from there. The installer window will open, and you’ll be able to proceed.

This is not an issue with the mod itself. I have virtually no input on the launcher development. Please direct bte (launcher, modpack, website, discord) issues to their team.

OK, thanks.

Interesting, so the binary actually works. This means that mac version doesn't like something about the .app structure I made but I have no way to know by myself what.

Yes - and I have tried tinkering with the .plist in your bundle, using settings from some of my own apps (note: not a full time developer, but I have been known to tinker out of curiosity). I even created a new app in Xcode and tried to get that to run from a bundle.
Each time, I am told that the app needed 10.15 or later. yet if I double-click the executable, it fires up Terminal and runs! Odd.
The structure of the BTEinstaller seems fine.
In Xcode you can set the base OS for the build. That may be what you need to do (I assume you ate using Xcode). HTH. Sorry I can't be more helpful.

I don't use xcode for it. I get a native executable out of native-image from graalvm and I package it into a .app and then into .dmg "manually" with a few commands in github actions. I was unable to find good documentation on how to do this stuff.

@Barteks2x I have cobbled together (this is a disguised warning - this is not my day job!) a small App in Xcode that runs your installer. It seems to be running on 10.14.6 here - I let it run an install cycle and it worked. However, test on a number ion platforms.
In Xcode, I have set the minimum OSX to 10.13.
So, I guess there are two paths here:
1 - Use Xcode and change all the project settings so it’s your details in the project! Swap out the BTEInstaller for the one you have created. This is the preferred way of doing things. To create a build to distribute in Xcode, go to Product>Archive, Click the Distribute App button and then choose the Copy App. That will save the version of the app in a folder with your Xcode project file.
2 - Modify the app bundle by changing the BTEInstaller for any updates you make. That will be in Contents/Resources (NOT the MacOS folder!). This may/may not work (depending on how Xcode has built the app - there are security things in place that may hinder apps running that have been modified in this way). Edit the plist file to taste.
Download a zip of the project here. Includes an app, and the Xcode project.
https://www.dropbox.com/s/yzmuhqseq5ht9e9/BTEInstaller.zip?dl=0
Let me know when you have the file so I can remove it from my Dropbox Folder.
Hope this helps your efforts!

I think the part that xcode adds that actually matters is
	<key>LSMinimumSystemVersion</key>
	<string>10.13</string>

I would definitely be using xcode if I actually owned a mac. I don't. All of my setup is done by an educated guess of macos commands that I put into github actions build. I will have to possibly look for information on commandline tools for xcode and how to use all of that. Which is not helped by the fact that I just don't have a mac.

I tried that key/string pair on its own in the installer I downloaded, and
no dice. I think there’s more going on with the folder structure and files
included in the build.
On Tue, 19 May 2020 at 12:18, Bartosz Skrzypczak<EMAIL_ADDRESS>wrote:

I think the part that xcode adds that actually matters is
LSMinimumSystemVersion
10.13
I would definitely be using xcode if I actually owned a mac. I don't. All
of my setup is done by an educated guess of macos commands that I put into
github actions build. I will have to possibly look for information on
commandline tools for xcode and how to use all of that. Which is not helped
by the fact that I just don't have a mac.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/orangeadam3/terra121/issues/134#issuecomment-630754392,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHOPAXJ4RBXPU2YX4MM32DRSJTJ7ANCNFSM4ND3JHQQ
.

I have no idea what it is and I'm not comfortable releasing dmg I didn't make myself to the public for use, specifically because it contains that weird binary. So unless I find a way to:

use xcode from commandline on github actions
or, do what xcode is doing manually
The binary xcode adds is not needed and can be directly replaced with the one I make
I probably won't do that.

@hairydalek I wouldn't assume that it would have to be on it's own, but with everything else.


⚠ Bofrost.at has degraded performance

In b193ee9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1100 ms

Resolved: Bofrost.at performance has improved in 97df836.


Create a list of compatible SMP implementations/providers

Create a list of implementations.
Companies may self-declare their support.
Publish company name + URL
Contact person/phone/email only for PD internal use

List is available at http://pyp.helger.com/public/locale-en_US/menuitem-smp-implementations


Lower-star filtration algorithms

It seems to me that flagser has all the components needed to be able to perform lower-star filtrations of (edge-unweighted) graphs or of their associated (edge-unweighted) flag complexes.  This is a fairly popular technique in the literature, particularly on graph classification using persistent homology (esp. with deep learning...), and so I think it might be a nice addition to make, at very low cost.
The idea here would be that only the node weights and the set of passed edges are used for the filtration, but not the actual edge weights. There can be at least two versions:

Nodes appear according to their weights, and any edge (i, j) which was passed gets the maximum between node weight i and node weight j. No higher simplices are present.
As for 1 for nodes and edges, but higher simplices also appear according to "flagification".

I'm not too familiar with the algorithms mini-language but let me take a quick stab at 2:
lower_star_flag = max(faceWeights, 0, dimension)

On the other hand, I'm not too sure how to implement 1. Maybe assigning infinite filtration value to all simplices in dimension 2 or above?
A slightly unrelated question: what does the remove_edges algorithm
https://github.com/luetge/flagser/blob/7ffe92782ae639b4265a52403d2d90d3151bb67b/algorithms.math#L19
achieve?  Again because of my lack of familiarity with the mini-language (I've read the docs but a bit quickly...) it seems to me quite similar to max, except for the fact that it requires the user to pass at least one (random??) edge weight, and sets the node weights to zero regardless of user input.  If my interpretation is correct, I guess I wonder why it is called remove edges, and what a typical use-case for it is.

Hi!
Sorry for the very late response. You can indeed do what you want: lower_star_flag overrideEdges = max(faceWeights)
This ignores edge weights, uses vertex weights and computes or each simplex of dimension >= 1 the value as the maximum weight of all faces. This should do what you described as 2., if you want to compute 1. then you just run the computation with --max-dim 1, to ignore all higher simplices.
The remove_edges algorithm came from an experiment we ran, where we wanted to measure the effect of randomly removing edges on the betti numbers of the flag complex. We achieve this by having all vertices present from the beginning and then adding edges at random times. Looking at the betti numbers over time gives an idea of how the complexity visible in the betti numbers relates to the amount of edges in the graph. The algorithm requires the user to provide edge weights for all edges, and no other weights.
I hope that helps, otherwise re-open the issue please!

Sorry for the very late response.

No worries at all -- thanks for the comprehensive response!

You can indeed do what you want: lower_star_flag overrideEdges = max(faceWeights)
This ignores edge weights, uses vertex weights and computes or each simplex of dimension >= 1 the value as the maximum weight of all faces. This should do what you described as 2.

Just to confirm: your solution will not add new edges, but simply replace the values of existing ones, correct?  If so, indeed this is the behaviour I'd like, and I wonder if you'd be happy for either of us to open a small PR adding this functionality.

if you want to compute 1. then you just run the computation with --max-dim 1, to ignore all higher simplices.

My understanding (from reading the docs) was that this would limit the computation to homology degree 1, while still computing 2-simplices.  My question concerned computing homology degree 1 with an empty set of 2-simplices, but I realise that this is fundamentally outside the scope of an algorithm for persistent homology of flag complexes.

The remove_edges algorithm came from an experiment we ran, where we wanted to measure the effect of randomly removing edges on the betti numbers of the flag complex. We achieve this by having all vertices present from the beginning and then adding edges at random times. Looking at the betti numbers over time gives an idea of how the complexity visible in the betti numbers relates to the amount of edges in the graph. The algorithm requires the user to provide edge weights for all edges, and no other weights.

Thanks for the clarification!

Yes, there will not be any new edges added, only their filtration values will be ignored and replaced by the computation provided in the formula (here the maximum).
Regarding computation of homology in degree 1: you are absolutely right, it computes the homology taking 2-simplices into account. What you want seems to be just the homology of the graph itself, which you can determine from the euler characteristic. If you compute --max-dim 0 and you write down the chain complexes, you should be able to determine the persistence for dimension 1 as well.
Another option: if you subdivide your graph once (add a vertex into the middle of each edge), the flag complex is identical to the graph itself, and this operation does not impact the persistence diagram if you give the vertex the weight of the edge (in your case the maximum of the weights of the vertices the edge connects). If you are trying to read off generators you have to be careful to interpret the output properly (un-subdivide it in a way), but if you just want the diagrams then this should be enough.

What you want seems to be just the homology of the graph itself, which you can determine from the euler characteristic. If you compute --max-dim 0 and you write down the chain complexes, you should be able to determine the persistence for dimension 1 as well.

Indeed, the "static" version (Betti 1) is easy via the Euler-Poincaré formula as you point out.  Persistence would presumably need more work, i.e. knowledge of the Euler characteristic curve.  I guess this is what you mean with "If [...] you write down the chain complexes".

Another option: if you subdivide your graph once (add a vertex into the middle of each edge), the flag complex is identical to the graph itself, and this operation does not impact the persistence diagram if you give the vertex the weight of the edge

Clever!  (At least for me.)  I only worry about the added memory overhead but this definitely works otherwise.  Thanks for the input anyway!
Quoting myself in case this was missed:

I wonder if you'd be happy for either of us to open a small PR adding this functionality.

What do you think?

Memory should not be a problem since you are only looking at the 1skeleton, but certainly there are more efficient ways of doing this, agreed!
Happy to accept a pull request, sorry for skipping that part.


Exclude paths from pwa

First of all thanks for this wonderful library!
Is it possible to exclude specific paths from pwa?
Suppose we have a backend serving our pwa but also some other web app (I.e. api docs). The pwa is served at root and web app at /api/docs. Now for the pwa, it is always configured at root, including sub paths. When accessing /api/docs, it gets first handled by pwa. It is working without pwa. Is it possible to exclude some paths?
Thanks in advance

@proohit https://github.com/antfu/vite-plugin-pwa/issues/218#issuecomment-1024580718
read the issue for context


Border color for warning and error notifications

We need just fix this OK button border?

Sure, sorry I was not aware of different notification types. Fix: https://github.com/DivanteLtd/vue-storefront/pull/1521

Can you please also remove the align center for the text? Please don't take it as an insult but for me it just looks very bad :/

@filrak https://github.com/DivanteLtd/vue-storefront/pull/1527


Recorder gets metrics

The dependency (metrics lib called medida) is here: https://github.com/janmejay/medida
Code-review of that is more than welcome, but still a nice to have.
But this code-review is more about we having captured all that we care about from metrics PoV and absolutely essential.

LGTM


No Wildcard certificate?

Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for <IP_ADDRESS>.2a10228b-c5dd-401a-8a62-fb4feb26e225.instance.kiu.party. The certificate is only valid for *.2a10228b-c5dd-401a-8a62-fb4feb26e225.instance.kiu.party.
Error code: SSL_ERROR_BAD_CERT_DOMAIN

Yeah, I didn't think that through. The IP address at the start of the domain is obviously interpreted as a new, "deeper" subdomain, and wildcard certificates are only valid for direct subdomains AFAIK. I'll just hex-encode the IP address in the domain.


Authentication

Add multi-user authentication to UI and services

In new release (currently on dev-branch), will introduce a simple form of token-based authentication, which should be good enough for now.


M1 support (darwin_arm64)

- Installed terra-farm/xenorchestra v0.23.0 (self-signed, key ID DDBA1674AA3EA0EE)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
╷
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/hashicorp/template v2.2.0 does not have a package available for your current platform, darwin_arm64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other versions of this provider may have different platforms supported.
╵

Pardon my vision


Custom Triggers for tooltip/popover

There is some sparse documentation that in order to make custom events, you have to use $tooltipProvider, however I haven't actually managed to get this to work. Apparently angular-foundation uses the same $tooltipProvider as the one mentioned here (https://github.com/angular-ui/bootstrap/issues/625), but I still don't have any luck.
Can someone provide a working example if this is actually possible?

use this elem[0].dispatchEvent(new Event('customEvent)) instead of elem.trigger('customEvent') to trigger custom events


Issue 105

Codecov Report

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

@@          Coverage Diff           @@
##           master     #11   +/-   ##
======================================
  Coverage      94%     94%
======================================
  Files         171     171
  Lines       29199   29199
======================================
  Hits        27257   27257
  Misses       1942    1942

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 1850d52...e6b478c. Read the comment docs.


Convert model name to snake_case for filename

WHY
Now we just convert all chars in model name to lower case for filename and endpoint. However this is not suitable for multi-word model name.
For example, from AccountName model , accountname.go and /api/accountname/ endpoint are generated.
WHAT
Convert model name to snake_case for filename and endpoint.
For example, from AccountName model , account_name.go and /api/account_name/ endpoint are generated.
toSnakeCase function is originated in https://gist.github.com/stoewer/fbe273b711e6a06315d19552dd4d33e6 .

LGTM!


Getting null pointers when dropping and recreating same-name container with the Spark connector

When delete and recreating the same name-container, the spark job will fail with nullPointerException:

@xinlian12 is this still valid? If so, please re-open it.


Fixed issue with download with make_executable=True, fixed typing issues, made as package to mark as py.typed

Fixed issues with download, typing, package structure.
Also:

Fixed issue with download with make_executable=True
Fixed typing issues
Made as package to mark as py.typed
Changed tasks.py to use the same structure of other packages
Using SEMA4AI_TLS_LEGACY_RENEGOTIATION_ALLOWED or RC_TLS_LEGACY_RENEGOTIATION_ALLOWED to define whether to enable legacy ssl connect.
Added tests

I need to use it in the new files API, so, fixed some issues to make a new release (the most annoying was that although it was typed the python typing didn't pick it up because py.typed wasn't set -- that's the reason I had to convert it to a package too).


Add support for "start screen" plugins

The ones in question are: dashboard-nvim, vim-startify, mini.starter, alpha-nvim, etc.
I'm curious whether it is a good idea to introduce a separate status for such plugins. My suggestion is that if any of these are active, we could display the editor's logo on the large image, without displaying the small one. Open to suggestions.

I agree with your suggestion, @vyfor. Having one for each plugin is unnecessary. Having the editor's logo is a good solution since, in my case, the start screen displays "Editing a new file." I use alpha.

Actually, now that I think about it, having a nice icon for dashboard plugins is not a bad idea. What do you all think?


npm install breaks on root

steps to repro:

git clone git@github.com:transmute-industries/verifiable-data.git
cd verifiable-data
npm i

this error shows up. have tried 3x, same stuff.
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build=false
npm ERR! 404 status code downloading tarball https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.11.0/node-v102-darwin-arm64.tar.gz
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>| darwin | arm64
npm ERR! node-pre-gyp WARN Using request for node-pre-gyp https download
npm ERR! node-pre-gyp info check checked for<EMAIL_ADDRESS>(not found)
npm ERR! node-pre-gyp http GET https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.11.0/node-v102-darwin-arm64.tar.gz
npm ERR! node-pre-gyp http 404 https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.11.0/node-v102-darwin-arm64.tar.gz
npm ERR! node-pre-gyp ERR! install error
npm ERR! node-pre-gyp ERR! stack Error: 404 status code downloading tarball https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.11.0/node-v102-darwin-arm64.tar.gz
npm ERR! node-pre-gyp ERR! stack     at Request.<anonymous> (/Users/gcohen/Development/verifiable-data/packages/bls12381-key-pair/node_modules/node-pre-gyp/lib/install.js:142:27)
npm ERR! node-pre-gyp ERR! stack     at Request.emit (node:events:532:35)
npm ERR! node-pre-gyp ERR! stack     at Request.onRequestResponse (/Users/gcohen/Development/verifiable-data/packages/bls12381-key-pair/node_modules/request/request.js:1059:10)
npm ERR! node-pre-gyp ERR! stack     at ClientRequest.emit (node:events:520:28)
npm ERR! node-pre-gyp ERR! stack     at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:618:27)
npm ERR! node-pre-gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.socketOnData (node:_http_client:482:22)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.emit (node:events:520:28)
npm ERR! node-pre-gyp ERR! stack     at addChunk (node:internal/streams/readable:324:12)
npm ERR! node-pre-gyp ERR! stack     at readableAddChunk (node:internal/streams/readable:297:9)
npm ERR! node-pre-gyp ERR! System Darwin 21.3.0
npm ERR! node-pre-gyp ERR! command "/opt/homebrew/Cellar/node/17.4.0/bin/node" "/Users/gcohen/Development/verifiable-data/packages/bls12381-key-pair/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build=false"
npm ERR! node-pre-gyp ERR! cwd /Users/gcohen/Development/verifiable-data/packages/bls12381-key-pair/node_modules/@mattrglobal/node-bbs-signatures
npm ERR! node-pre-gyp ERR! node -v v17.4.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.14.0
npm ERR! node-pre-gyp ERR! not ok

Trying to resolve https://github.com/mattrglobal/node-bbs-signatures/releases/download/0.11.0/node-v102-darwin-arm64.tar.gz directly also returns a 404

hmm, I think we should start by bumping the versions of the mattr lib, and seeing if that resolves the issue.

I ran npm i without cloning and did not encounter this... I'll keep digging.

@OR13 I think it may be the specific version node-v102-darwin-arm64.tar.gz since I'm on an ARM Mac. I'm wondering if this just isn't supported by the library.

ohh....yeah... :(

I just cloned fresh, and so far, I have not seen this.

@decentralgabe you mind testing npm i @mattrglobal/node-bbs-signatures by itself? maybe report issue there and cross link.

also node version, you need to be node14 due to that library... its the main reason we still have node 14 recommendations at the top of this readme.

I'm
❯ node -v
v14.15.5
❯ npm -v
6.14.16

npm i from fresh clone worked for me.

See the warning at the top of our readme: https://github.com/transmute-industries/verifiable-data#node-verion
That said, I think we should probably try to matrix out support for more than just node14... even if we have to nerf some of the wasm based tests related to the mattr lib

@decentralgabe you mind testing npm i @mattrglobal/node-bbs-signatures by itself? maybe report issue there and cross link.

same error with this command

also node version, you need to be node14 for this mono repo, due to that library... its the main reason we still have node 14 recommendations at the top of this readme.

ah I'm on 17.4, so I'll need to downgrade

https://github.com/mattrglobal/node-bbs-signatures/

https://github.com/mattrglobal/node-bbs-signatures/issues/182

Hi @OR13, related to this issue, do you plan to update mattrglobal/node-bbs-signatures to a more recent version?
v0.11.0 is the last version that doesn't offer binaries for Node.js 16 😢

yeah.... we plan to update that... there is some breaking WASM issue between versions... its in our backlog... if you are brave, I welcome a PR.

Hi @OR13 continuing on the discussion from last week I opened #204 updating the mentioned package.
Checking https://github.com/mattrglobal/node-bbs-signatures/blob/master/CHANGELOG.md there are no expected breaking changes.
The bump would be ok for node 14
$ tsdx test
 PASS  src/Bls12381G2KeyPair.test.ts
 PASS  src/Bls12381G1KeyPair.test.ts
 PASS  src/__tests__/mattr.bls12381.sanity.test.ts
 PASS  src/Bls12381KeyPairs.test.ts
 PASS  src/__tests__/bls12381.sanity.test.ts
 PASS  src/__tests__/noble.bls12381.sanity.test.ts

Test Suites: 6 passed, 6 total
Tests:       18 passed, 18 total

Can confirm that node 16 is not ok though
> tsdx test

 FAIL  src/__tests__/bls12381.sanity.test.ts
  ● Test suite failed to run

    The module<EMAIL_ADDRESS>    was compiled against a different Node.js version using
    NODE_MODULE_VERSION 83. This version of Node.js requires
    NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
    the module (for instance, using `npm rebuild` or `npm install`).

      at Runtime._loadModule (node_modules/tsdx/node_modules/jest-runtime/build/index.js:800:29)
      at Object.<anonymous> (node_modules/@mattrglobal/node-bbs-signatures/src/bls12381.ts:22:13)

(node:65691) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:65658) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:65664) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:65678) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  src/Bls12381G1KeyPair.test.ts
(node:65676) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 FAIL  src/Bls12381G2KeyPair.test.ts
  ● signer / verifier

    RuntimeError: unreachable

      at null.<anonymous> (wasm:/wasm/001aa38a:1:325487)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:362437)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:391964)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:387953)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:391336)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:378712)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:262279)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:387692)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:393899)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:143488)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:197149)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:359883)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:257544)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:352979)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:336913)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:393468)
      at __wbg_adapter_32 (node_modules/@mattrglobal/bbs-signatures/lib/wasm.js:180:10)
      at real (node_modules/@mattrglobal/bbs-signatures/lib/wasm.js:165:20)

 PASS  src/Bls12381KeyPairs.test.ts
(node:65670) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/kalin/Projects/ebsi/verifiable-data/packages/bls12381-key-pair/node_modules/tsdx/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 PASS  src/__tests__/noble.bls12381.sanity.test.ts
 FAIL  src/__tests__/mattr.bls12381.sanity.test.ts (6.283s)
  ● g1: can generate sign and verify

    RuntimeError: unreachable

      at null.<anonymous> (wasm:/wasm/001aa38a:1:325487)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:362437)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:391964)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:387953)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:391336)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:378712)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:262279)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:387692)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:393899)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:216471)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:378395)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:362667)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:268552)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:352979)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:336913)
      at null.<anonymous> (wasm:/wasm/001aa38a:1:393468)
      at __wbg_adapter_32 (node_modules/@mattrglobal/bbs-signatures/lib/wasm.js:180:10)
      at real (node_modules/@mattrglobal/bbs-signatures/lib/wasm.js:165:20)

  ● g2: can generate sign and verify

    : Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Error:

      24 | });
      25 |
    > 26 | it('g2: can generate sign and verify', async () => {
         | ^
      27 |   const key = await Bls12381G2KeyPair.generate();
      28 |   const signer = key.signer();
      29 |   const signature = await signer.sign({

      at new Spec (node_modules/tsdx/node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
      at Object.<anonymous> (src/__tests__/mattr.bls12381.sanity.test.ts:26:1)

Test Suites: 3 failed, 3 passed, 6 total
Tests:       3 failed, 12 passed, 15 total

Although the upgrade is ok for 14, the wasm error for 16 is still present as mentioned.

I suspect this is caused by "bad data"... and that the test data will need to be updated for the new library version.


Add an optional external Id field

In order to assume a role created by a 3rd party as external ID is needed. This change adds an optional field to the s3 integration configuration and consumes that in the AwsS3UrlReader.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation (api report, etc)
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

These a config file sample in docs somewhere. Could you update that as well. Other than that LGTM

I think I found the one your mean. Thanks.


TCO to review and update (if necessary) M365 Workshop slides for Teams

💡 Summary
SCuBA will hosting workshops to cover M365's SCBs and the team is requesting the TCOs to review and update the slides to match the current language approved in the v1.0 version.
Motivation and context
JCDC, OCC, and CISA front office reviews may discover changes to the language of the policies and the rationale sections. In order for the workshops to stay synced with the latest version of the SCBs, TCOs are expected to review and update the workshop slides to match version 1.0.
Implementation notes
Please provide details for implementation, such as:

Review latest SCB released by CISA front office
Review M365 Workshop slides provided by @mheller93766. HSSEDI Linked below. For those who do not have access to the HSSEDI environment @mheller93766 has provided the slides via email

 3. M365 SCB Workshops Material

Ensure the language of the policies and the rationales are synced with the latest version of the SCB

Acceptance criteria
How do we know when this work is done?

[ ] M365 Workshop Slides and SCB policy and rationale languages have been reviewed and synced by the TCO

currently blocked due to awaiting final version from CISA front office

Please have this completed by Jan 12th to meet CISA's review deadline.

Review completed and the changes to the workshop slides are finalized. Closing.


Invalid environment variables in CI environment running tests

Once it got to my CI, the validation failed -- and whats weird is it ran successfully locally.  Would be nice if it failed nicely in a CI environment, but also my test shouldn't have accessed a env variable.
$ npm test
><EMAIL_ADDRESS>test
> mocha --require ts-node/register --timeout 100000 --require ./dist/test-setup.js './src/**/*.spec.js' './src/**/*.spec.ts'
❌ Invalid environment variables: {
  ...
}
Error: Invalid environment variables
    at /project/node_modules/@t3-oss/env-core/index.ts:155:1
    at g (/project/node_modules/@t3-oss/env-core/index.ts:155:1)
    at Object.<anonymous> (/project/src/env.ts:5:29)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .ts] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/project/src/victorops/api.ts:14:1)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .ts] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/project/src/data/Team.ts:3:1)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .ts] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/project/src/consts.js:2:1)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .js] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/project/src/puppet/consts.js:39:6)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .js] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/project/src/puppet/test/controller.spec.js:2:16)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Module.m._compile (/project/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Object.require.extensions.<computed> [as .js] (/project/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
    at async formattedImport (/project/node_modules/mocha/lib/nodejs/esm-utils.js:9:14)
    at async Object.exports.requireOrImport (/project/node_modules/mocha/lib/nodejs/esm-utils.js:42:28)
    at async Object.exports.loadFilesAsync (/project/node_modules/mocha/lib/nodejs/esm-utils.js:100:20)
    at async singleRun (/project/node_modules/mocha/lib/cli/run-helpers.js:125:3)
    at async Object.exports.handler (/project/node_modules/mocha/lib/cli/run.js:370:5)

Anyways, for now I did a
export const env = process.env.IS_CI
	? process.env
	: createEnv({});

Thoughts?

There's this line in your stacktrace: at Object.<anonymous> (/project/src/victorops/api.ts:14:1), which means your CI did actually touched this file, which imported the env.ts file, which triggered the env validation. Maybe you didn't actually call any function inside api.ts that accesses an environment variable from env.ts, but api.ts is importing env.ts so it is assumed by default that api.ts always uses env.ts.
Now, I think the problem is that either the test should be skipping the validation of some environment variables that are not present at the time that the test runs, or it should not skip at all because api.ts indeed needs some variables in order to function properly, and that depends on your test's purpose. I'm assuming it's the latter because your specified const env = to be process.env; otherwise you would have put it as {} if your test doesn't use env vars at all. So you should validate your envs. The fact that you can validate locally but failed to run on CI environment means that your CI environment is not "identically identical" to your local environment. If it's just the same command running locally as well as CI, then it's almost always the environment variables that are the culprit.

@intagaming is correct. Your tests should reflect the real would. If they dont require them, use dummies, or use the skipValidation option to omit them.
You can also make more complex schemas that only makes a var required in certain environments (see NEXTAUTH_URL and NEXTAUTH_SECRET in create-t3-app for examples)


Bug 2104784: AWS: Fix race in IP address assignment code

Signed-off-by: Andreas Karis<EMAIL_ADDRESS>FYI I also talked to Alex about this fix here and about why it was originally done differently; Alex shot for idempotency, but did not consider this specific race condition here.

/retest

/retest

/retest

/retest

/lgtm

/lgtm

/retest-failed

/bugzilla refresh

/retest-failed

/restest-required

/retest-failed

/retest-failed

/retest-failed

The failing EgressIP test is a flake in the test itself. I ran the test manually multiple times against this very PR and it passes without issues.
akaris@linux origin ((2ca9c0cc41...))]$ TEST_SUITE_START_TIME="1658754962" KUBE_TEST_REPO_LIST="" KUBE_TEST_REPO="quay.io/openshift/community-e2e-images" TEST_PROVIDER="{\"type\":\"aws\",\"ProjectID\":\"\",\"Region\":\"us-west-2\",\"Zone\":\"us-west-2b\",\"NumNodes\":3,\"MultiMaster\":true,\"MultiZone\":true,\"Zones\":[\"us-west-2b\",\"us-west-2c\"],\"ConfigFile\":\"\",\"Disconnected\":false,\"SingleReplicaTopology\":false,\"NetworkPlugin\":\"OpenShiftSDN\",\"HasIPv4\":true,\"HasIPv6\":false,\"HasSCTP\":false,\"IsProxied\":false,\"IsIBMROKS\":false}" TEST_JUNIT_DIR="" TEST_UPGRADE_OPTIONS="" ./openshift-tests run-test "[sig-network][Feature:EgressIP] [external-targets] EgressIPs can be assigned automatically [Skipped:Network/OVNKubernetes] [Serial] [Suite:openshift/conformance/serial]"

/retest-required

/approve


Crash due to using Java 9

https://pastebin.com/jN0AD2UV

This crash is due to using java 9, which we don't yet support, as per issue #3106. If you install and/or run Terasology using Java 8 then it should load fine.

lol, no joke i didnt even install java9 (at least not knowing of it)
i will use  the netbeans java, (which should be jdk8)
thanks ans sorry


Issue #144 Fixed DoesNotExist expected state

Changed properties to fail if an element does not exist on the model, and ensured that the comparer does not look at target value.

Codecov Report

Merging #145 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #145      +/-   ##
==========================================
- Coverage   77.11%   77.07%   -0.04%
==========================================
  Files         113      113
  Lines        3019     3014       -5
  Branches      349      345       -4
==========================================
- Hits         2328     2323       -5
  Misses        633      633
  Partials       58       58

Impacted Files
Coverage Δ

src/SpecBind/Actions/ValidateItemAction.cs
100% <ø> (ø)
:arrow_up:

src/SpecBind/Validation/DoesNotExistComparer.cs
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Question: Can broccoli run in es6

Hi all, new to broccoli. Super cool so far, literally building my sass 10 seconds faster!
So thank you!
Quick question. Does broccoli have an option to run the brocfile in es6, like gulps gulp.babel.js?
I know I can have a regular es5 file require babel, and then other files can be in es6. Just curious if it was already possible to cut out that extra step.

Not currently

I think it's best to wait for Node to pick up new ES6 features, rather than trying to add support to Broccoli. The latest Node version 4.1.2 supports quite a few already, such as classes and arrow functions.

Thanks for the response


Automatically audit packages using both osv and pypi, or document that they may report different results

Is your feature request related to a problem? Please describe.
I'm always frustrated when I think there are no security vulnerabilities in my project, but there actually are. My team runs pip-audit as a daily CI job to warn us about CVEs in our Python dependencies.
By default pip-audit uses PyPI, and currently reports no issues for any of our dependencies. But while investigating a dependabot warning today, we reran pip-audit using "--vulnerability-service osv", and saw that there was a django-celery-results GHSA reported in OSV.
Describe the solution you'd like
Obviously pip-audit doesn't control the contents of either the OSV or PyPI databases, and I'm about to go request that those projects synchronize their data. But it would also be nice if pip-audit automatically checked both OSV and PyPI by default:
-s SERVICE, --vulnerability-service SERVICE
                        the vulnerability service to audit dependencies
                        against (choices: osv, pypi) (default: osv, pypi)

Describe alternatives you've considered
Add some documentation stating that OSV and PyPI vulnerabilities may differ, and that auditing against both services is recommended. This could be a small snippet in "pip-audit --help", like below:
-s SERVICE, --vulnerability-service SERVICE
                        the vulnerability service to audit dependencies
                        against. Each service may report different
                        results, so checking both is recommended.
                        (choices: osv, pypi) (default: pypi)

The two should be in sync. If you can provide the specific example, we can look into it.

Whoops, @di beat me to it. Yeah, I believe the only times there should be a discrepancy are if the scheduled task is still pending or has failed for some reason.

After looking at the linked GHSA, this could be a bug with the OSV data, or (maybe) a bug with how pip-audit compares package names and versions.
We definitely are using django-celery-results=2.2.0, and the GHSA is for versions less than 1.2.1. Running below succeeds:
(venv) $ pip-audit -r requirements/base.txt --strict --vulnerability-service pypi
No known vulnerabilities found

But running below fails:
(venv) $ pip-audit -r requirements/base.txt --strict --vulnerability-service osv
Found 1 known vulnerability in 1 package
Name                  Version ID                  Fix Versions
--------------------- ------- ------------------- ------------
django-celery-results 2.2.0   GHSA-fvx8-v524-8579

With a requirements/base.txt entry like:
django-celery-results==2.2.0 \
    --hash=sha256:cc0285090a306f97f1d4b7929ed98af0475bf6db2568976b3387de4fbe812edc \
    --hash=sha256:d5f83fad9091e52cd6dbb3ca80632153ad14b6cdac4d73258e040f92717237cb
    # via -r requirements/base.in

Looks like PyPI doesn't know about any vulnerabilities for this project:
$ curl -s https://pypi.org/pypi/django-celery-results/json | jq ".vulnerabilities"
[]

We did have some hiccups with the ingestion in the last few days, it's possible we might need to do some manual intervention to sync here (cc @oliverchang)

We weren't properly pushing the GHSA entries to warehouse. I have https://github.com/google/osv/pull/429 out to fix this.

warehouse now knows about GHSA-fvx8-v524-8579:
> curl -s https://pypi.org/pypi/django-celery-results/json | jq ".vulnerabilities"
[
  {
    "aliases": [
      "CVE-2020-17495"
    ],
    "details": "django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.",
    "fixed_in": [],
    "id": "GHSA-fvx8-v524-8579",
    "link": "https://osv.dev/vulnerability/GHSA-fvx8-v524-8579",
    "source": "osv"
  }
]

Thanks a ton @oliverchang!
@juspence: Does re-running the audit now give you the results you expect?

Yes, the GHSAs reported by pip-audit --vulnerability-service osv are now reported by pip-audit --vulnerability-service pypi as well! Thanks for fixing it!


New feature: auto email me a random verse every morning.

Probably as part of the API, maybe a standalone micro service?

Standalone executable that can be executed with a cronjob is what I settled on.


Add myself as owner

Add myself as owner

/cherrypick backplane-2.6

/cherrypick backplane-2.5


tensorflow: init at 0.8.0

Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[x] Linux

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

While I think listing all the licenses is a good service to our users, what really matters is that none of the bundled sources are licensed in a way that makes it illegal to redistribute the whole. I'd find it incredibly deceptive if upstream provides a bundle that is in fact illegal to distribute, given that their advertised license certainly permits it.

Thank you


Issue 515 slow loading of asset page due to timerange query of its sensors

This PR makes data load faster on the asset (and sensor) page. Most commonly, the time range is already set as session data, so we shouldn't have to wait for finishing a potentially slow query to the database that determines the full timerange of shown sensors.
Also, the date range selection on the calendar is now set much earlier, when initializing the calendar, instead of when the charts are done loading. This means that, when you navigate the calendar while charts are still loading, you don't annoyingly pop back to the initial selection when the charts are done loading.
Closes #515.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.967%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6570

Relevant Lines:
9491

💛  - Coveralls


A few tweaks

Fixed a few console warnings (video had wrong "muted" jsx prop)
Inter font so site matches the vercel, next.js sites (just the latin subset, preloaded)
Animation with native

📝Changed routes:

/

(view full size)

Commit 14a028cb651672051fa53ec29036a2dcd6c8d80c (https://swr-site-git-fork-vassbence-master.zeit.now.sh).

Amazing PR, thank you @vassbence ! Can you also include the changes from https://github.com/zeit/swr-site/pull/6?

Of course @shuding

Looks great, thank you!


"Dismiss" X button in the search panel should be aligned to the right edge

This would ensure predictability. Currently button is aligned just after the text excerpt. Problem is that can be short or long. So this button can be positioned all the way to the right or left, depending on the text size.
I personally suffer from this when I quickly want to click to the search result to see it. Instead I often accidentally click the X button and I remove my result. Then I have to rerun the search again and next time I have to make sure not to click the "Dismiss" button.
Also when you need to remove multiple items using a mouse, it's much more complicated when these buttons are misaligned.
The simple CSS change would make the button position much more predictable.
Version: 1.29.1
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:07:43.495Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Steps to Reproduce:

Run search
Observe

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

I would like to contribute on this one!

We already have a PR going for this: https://github.com/Microsoft/vscode/pull/63457

Thanks a lot for fixing this -- I've also been recently plagued by my search results accidentally being dismissed.


mscorlib reference assembly is missing System.Diagnostics.Tracing methods

Commit mono/mono@ce24528b41d28a15feceb4485409d326b8608bc8 added various methods to some of the classes in the System.Diagnostics.Tracing namespace.
This allowed me to run an application on mono.
However, I can currently not compile that application on mono because, from what I gather, the mscorlib reference  assembly (mono/4.5-api/mscorlib.dll) does not contain these updated methods.
I was wondering what the best way would be to fix this? Do I check out reference-assemblies, do a binary replacement of mscorlib, and issue a binary PR for that?
Any other recommended approach?

Could you be more specific what public API you need we are missing there?
Also as the fastest workaround you could upgrade your target framework to .net 4.6 instead of .net 4.5

The APIs that are missing are, among others, the various overloads of the System.Diagnostics.Tracing.EventSource.Write and System.Diagnostics.Tracing.EventSource.WriteEvent method.
I'll try 4.6 and let you know if that helps.

fwiw, I seem to have a similar issue with the property I added in https://github.com/mono/mono/commit/820b140a1904febb47b256fe3b3b3192cfcac6f9.
Where using the 4.4.0 alpha, the property is found when building against .NET 4.6, but not when building against 4.5. This is only a build issue rather than a runtime issue here, but still, this is a property that's been around for a while.

This is (finally) done with https://github.com/mono/reference-assemblies/pull/4 😄


FormatTimesForSASSigning should convert to UTC before formatting

Which version of the SDK was used?
v0.8.0
Which platform are you using? (ex: Windows, Linux, Debian)
Arch Linux
What problem was encountered?
Passing in time.Now().Add(time.Hour) to BlobSASSignatureValues.ExpiryTime results in the time string dropping TZ data and assuming it's in UTC. My local is in EST but the format string omits any Time Zone addition with a static Z ending: 2006-01-02T15:04:05Z
How can we reproduce the problem in the simplest way?
https://play.golang.org/p/YB02MQG3m1T
Something like
azblob.FormatTimesForSASSigning(time.Now().In(time.FixedZone("UTC-8", -8*60*60), time.Time{}, time.TIme{})

It should be an easy fix - could have saved me a load of hours as I saw the time format with a Z ending in the encoded query and assumed it was properly converting to UTC (didn't pay close enough attention to the actual numbers though)
Have you found a mitigation/solution?
Pass in the time values in the struct as UTC myself

Inactive. Please reopen once you address comments on the PR


Changing the telescope names patterns

This is a big PR, many small changes in many modules.
Few items to be aware of:

TelescopeNames follow the pattern "Site-Class-Type", where Site can be South or North, Class can be SST, MST, SCT or LST and Type can be anything. (The terms Class and Type are only relevant internally to util.names. For all the other modules, only telescopeName is meaningful.)
The Type with single numbers should be reserved for real, on-site, telescopes. A letter D can be used to indicate telescopes designs.
The Type can contain dashes itself, e.g South-MST-FlashCam-D (Type = FlashCam-D)
The function util.names.validateTelescopeName checks if the site and class are valid (and convert it to the right form if necessary) but it does not check the Type. The Type validation will be better done by the db_handler, by checking if that telescopeName exists in the DB. I created an issue for that (https://github.com/gammasim/gammasim-tools/issues/52).
All telescopeType variables were replaced by telescopeName. In all the cases where both telescopeType and site were passed, only telescopeName is passed now. When the site is needed, the function util.model.getSiteFromTelescopeName can be used.
I introduced cameraNames, which are defined by the function util.model.getCameraName. This was necessary to deal with the camera-dependent parameters CAMERA_ROTATE_ANGLE and CAMERA_RADIUS_CURV. Instead of using the telescopeName as keys, I use now the cameraNames, that can be obtained by getCameraName(telescopeName). This is a good solution since the same camera will be part of many different telescopes.
The TWO_MIRROR_TELESCOPE parameter was replaced by the function util.model.isTwoMirrorTelescope(telescopeName).
The previously used telescope names can be obtained from a modern one with util.names.convertTelescopeNameToYaml. This is used whenever useMongoDB is set to False. At the moment, both LST-D234 and LST-1 are being converted to the same LST. @orelgueta , please have a look and fix it.
The new names for the old unused telescopes are Site-SST-ASTRI, Site-SST-1M, Site-SST-GCT.
IMPORTANT: The site parameters are being collected from the yml files in the TelescopeModel method _loadModelParameters. This is a temporary hack.
BUG LEFT BEHIND: Some pytest's failed because sim_telarray complaint about the new parameters that we added to the model. We have to remove these parameters when exporting the config file (https://github.com/gammasim/gammasim-tools/issues/53).

All looks good, minor comments only.
Won't be trivial to merge the db_handler, but we'll see.

The function util.names.validateTelescopeName checks if the site and class are valid (and convert it to the right form if necessary) but it does not check the Type. The Type validation will be better done by the db_handler, by checking if that telescopeName exists in the DB. I created an issue for that (#52).

Now I understand this issue better, continue discussion there.

The previously used telescope names can be obtained from a modern one with util.names.convertTelescopeNameToYaml. This is used whenever useMongoDB is set to False. At the moment, both LST-D234 and LST-1 are being converted to the same LST. @orelgueta , please have a look and fix it.

Not sure what I should fix. The Yaml DB does not separate between the two LST types, so converting to the same LST is OK.
Including both LST types in the Yaml DB would require a change of structure, and I don't think it is worth it, considering it's a temporary situation.

The new names for the old unused telescopes are Site-SST-ASTRI, Site-SST-1M, Site-SST-GCT.

OK, included in the DB this way.

IMPORTANT: The site parameters are being collected from the yml files in the TelescopeModel method _loadModelParameters. This is a temporary hack.

Will change once I add the site information to the MongoDB.

BUG LEFT BEHIND: Some pytest's failed because sim_telarray complaint about the new parameters that we added to the model. We have to remove these parameters when exporting the config file (#53).

Will you take care of it? It should probably be in the telescope model side rather than the DB side.

The new names for the old unused telescopes are Site-SST-ASTRI, Site-SST-1M, Site-SST-GCT.

Actually, now that I think about it, would it be terrible to change these to be "South-SST-ASTRI-D", "South-SST-1M-D" and "South-SST-GCT-D"?
It would be a bit easier for me when filling the DB and I think it also makes sense to keep the "D" for design.

The previously used telescope names can be obtained from a modern one with util.names.convertTelescopeNameToYaml. This is used whenever useMongoDB is set to False. At the moment, both LST-D234 and LST-1 are being converted to the same LST. @orelgueta , please have a look and fix it.

Not sure what I should fix. The Yaml DB does not separate between the two LST types, so converting to the same LST is OK.
Including both LST types in the Yaml DB would require a change of structure, and I don't think it is worth it, considering it's a temporary situation.

Ok then. I wasn't sure about the that, but if there is only one LST in the yml files, so everything is fine.

The new names for the old unused telescopes are Site-SST-ASTRI, Site-SST-1M, Site-SST-GCT.

OK, included in the DB this way.

Great.

IMPORTANT: The site parameters are being collected from the yml files in the TelescopeModel method _loadModelParameters. This is a temporary hack.

Will change once I add the site information to the MongoDB.

Ok.

BUG LEFT BEHIND: Some pytest's failed because sim_telarray complaint about the new parameters that we added to the model. We have to remove these parameters when exporting the config file (#53).

Will you take care of it? It should probably be in the telescope model side rather than the DB side.

Yes, right. I'll fix it in the telescope_model later.

The new names for the old unused telescopes are Site-SST-ASTRI, Site-SST-1M, Site-SST-GCT.

Actually, now that I think about it, would it be terrible to change these to be "South-SST-ASTRI-D", "South-SST-1M-D" and "South-SST-GCT-D"?
It would be a bit easier for me when filling the DB and I think it also makes sense to keep the "D" for design.

Wait wait wait.
Yes, that is what I meant, that there would be both South-* and North-* in the DB. If you think it's easier to add only one, no problem.
We have some freedom to decide these things at the DB side. We only have few constraints on the yml files side. In that case, it doesn't matter, both sites will work because we read the parameters from the site yml files anyway.

Wait wait wait.
Yes, that is what I meant, that there would be both South-* and North-* in the DB. If you think it's easier to add only one, no problem.

But you don't have the "-D" at the end in the code I think, no?
Either way, if we have freedom, I will call them "South-SST-ASTRI-D", "South-SST-1M-D" and "South-SST-GCT-D" in the DB. You might have to change your names as well I guess.


Debian 9 Stretch package

Debian Linux 9 Stretch has been released, please provide a package.
ref #766

I tried to build on stretch got an erlang version error, riak requires OTP 17 and current is 19

@zowers I am afraid that with Basho ceasing most business activities on 31st May 2017 and later going into receivership, you may be a while waiting on that. The Open Source community is already rallying around building new versions and there is talk of a Riak Consortium. Unfortunately neither of these will happen overnight. Given this, I am afraid that you will have to make do with either Jessie or Wheezy if you want official Basho Debian packages - https://files.tiot.jp/riak/kv/2.2/2.2.3/debian/ or, alternately, try compiling from source - https://files.tiot.jp/riak/kv/2.2/2.2.3/riak-2.2.3.tar.gz
@jagguli That is correct, Riak requires older versions of Erlang. Please see https://www.tiot.jp/riak-docs/riak/kv/2.2.3/setup/installing/source/erlang/#installing-with-kerl for how to install Erlang via Kerl.
That said, there is an issue with Yokozuna in that the Yokozuna jar files and Solr files required to build Riak were hosted on the Basho AWS service which is no longer available. A workaround has been released for develop, develop-2.0 and develop-2.2 that points Yokozuna to copies of the necessary files that are hosted by TI Tokyo.
Once you have the correct version of Erlang, this is an example of how you could build:
git clone riak
cd riak
checkout develop
make deps
export ARTIFACT_URL_PREFIX="https://files.tiot.jp/riak"
make

Substitute checkout develop for either checkout develop-2.0 or checkout develop-2.2 depending on which version you want to build. The ARTIFACT_URL_PREFIX points the script to the variable you set here i.e. TI Tokyo's file store instead of the default Basho AWS service as that is currently unavailable. Should Basho's AWS service ever become available again, this work around would no longer be needed.

Packages are available for Debian 9 Stretch:
KV 2.2.6 https://files.tiot.jp/riak/kv/2.2/2.2.6/debian/9/
KV 2.9.0p1 https://files.tiot.jp/riak/kv/2.9/2.9.0p1/debian/9/
CS 2.1.2 https://files.tiot.jp/riak/cs/2.1/2.1.2/debian/9/
Stanchion 2.1.2 https://files.tiot.jp/riak/stanchion/2.1/2.1.2/debian/9/
I think this issue can be closed now

Are these packages available via apt? What about for the new Debian Buster release?


Display bug image in gmail - width : NaN

Hi !

MJML 3.2.0 -
try on litmus and gmail -
bug on gmail (all browsers), gmail app (android) and inbox -

I have a problem with the display of the images in gmail.
Currently, if you don't add manually a size of the image we have a width set with NaN value, while we have inside the style attribute width:100%

The problem is fixed if I set the width on 100% value.
I think we can resolved this issue in two ways :

either to add the ability to set the width of the <mj-image> with percent unit
copy/link the value between style attribute and width

Hi @Sarah-IFG, thanks for reporting this issue.
Unfortunately, I can't reproduce the issue with NaN, can you provide your MJML markup?
If I try to reproduce and don't add a width to my image, here is what my image styles look like:
Example here: https://mjml.io/try-it-live/SkMkhzwOx

Hi,
Trying to reproduce the bug, I understood that was my mistake... I put a section tag into an other section tag as <mj-wrapper> was not yet available.
<mj-body>
  <mj-container background-color="#ff6f72">

    <mj-section>
      <mj-column width="95%" background-color="#ffffff" border-radius="15px">

        <mj-section border-radius="15px 15px 0 0" background-color="#ffe8d8" padding="0" >
          <mj-column >
            <mj-spacer height="25px"/>
          </mj-column>
        </mj-section>

        <mj-section padding="0">
          <mj-column>
            <mj-image src="/assets/img/logo-small.png" href="#" />
          </mj-column>
        </mj-section>

        ......

      </mj-column>
    </mj-section>

  </mj-container>
</mj-body>

Besides, I realized that we can't add a width value to the <mj-wrapper>. It would be very helpful to add this attribute.
In my case, it was to create gutter in mobile.

Indeed you nested columns and sections inside another column and section which might lead to issues.
In MJML v3.3.0 (in beta now), you can use mj-wrapper.
Why not wrap your section in a wrapper and apply a padding on the image, like so: https://mjml.io/try-it-live/ByoqgIPOx

I had the same issue the other day, the image-element has no information about the parentWidth and thus parseInt returns NaN.
My image-element was nested in a custom component and I could fix it by re-applying the attributes of the custom component: <Image {...mjmlAttrs} src={image} />. I don't know if this is working-as-intended?

@ngarnier thanks but it is not the behavior I needed. I need to have gutter outside the wrapper not inside, I do not see how to do without being able to change the width of the wrapper.

@Sarah-IFG Why not add the padding on the wrapper then? https://mjml.io/try-it-live/H1YEO2KOl

@Rouby we're aware that deep nesting a component in a custom component misbehave, we're working on it

Hi @Sarah-IFG !
i'm closing this one, if you're still having the issue feel free to reopen !
Note that you have to remove the padding left+right on your image width to avoid the overflow


Replace protocol for cloning

otherwise on a server where you do not have a key you can end up with:
$ git clone --recurse-submodules git@github.com:wmitsuda/otterscan.git
Cloning into 'otterscan'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

with https you do not need a key:
$ git clone --recurse-submodules https://github.com/wmitsuda/otterscan.git
Cloning into 'otterscan'...
remote: Enumerating objects: 1966, done.
remote: Counting objects: 100% (770/770), done.
remote: Compressing objects: 100% (408/408), done.
remote: Total 1966 (delta 431), reused 458 (delta 330), pack-reused 1196
Receiving objects: 100% (1966/1966), 893.74 KiB | 6.72 MiB/s, done.
Resolving deltas: 100% (1285/1285), done.
Submodule '4bytes' (https://github.com/ethereum-lists/4bytes.git) registered for path '4bytes'
Submodule 'trustwallet' (https://github.com/trustwallet/assets.git) registered for path 'trustwallet'
Cloning into '/home/gather/otterscan/4bytes'...
remote: Enumerating objects: 333320, done.
remote: Counting objects: 100% (126744/126744), done.
remote: Compressing objects: 100% (7043/7043), done.
remote: Total 333320 (delta 93), reused 126704 (delta 63), pack-reused 206576
Receiving objects: 100% (333320/333320), 41.83 MiB | 8.25 MiB/s, done.
Resolving deltas: 100% (566/566), done.
Cloning into '/home/gather/otterscan/trustwallet'...
remote: Enumerating objects: 166463, done.
remote: Counting objects: 100% (94/94), done.
remote: Compressing objects: 100% (73/73), done.
remote: Total 166463 (delta 43), reused 60 (delta 21), pack-reused 166369
Receiving objects: 100% (166463/166463), 440.42 MiB | 7.55 MiB/s, done.
Resolving deltas: 100% (72008/72008), done.
Submodule path '4bytes': checked out '1cc7e25c840ae9d985c12768b0cbd0ece3fc5400'
Submodule path 'trustwallet': checked out '7bfa06acc125a4874d86bc1fa8e4547a46846e31'

Merged, thanks!


Print run time stats in the test runner

Pytest is able to do this, as well as other things that are coded by hand in runtests.py (like multiprocessing). Problem is, pytest doesn't support python 2.6. Will there be a drop of Python 2.6 support like Cython dropped python 3.3 in the near future? If yes, I would be willing to do PRs for a progressive migration from Unittests to pytests.

I'm well aware that pytest can do the parallelisation and (some of) the reporting. What it can't do is discover and run the tests. :)
The problem is that the tests have three steps: Cython translation, C/C++ compilation and importing/testing (mostly doctests). The test modules and their doctests only become available after compilation, but pytest assumes that it can discover and select all tests before starting them.
I guess we could write our own test discovery, always assume that each test has all three steps, and then mark the non-existant steps as skipped, but I'm not sure that would be better and/or less work than what we have.

Since Py2.6 doesn't really pose many problems currently (not more than Py2 in general), and since it still works to test it on travis, I wouldn't remove it right now (knowing that it already had its EoL last year). But as soon as it gets in the way, I'll happily remove it. Could happen right after the next release.

I see. Thanks for the explanation!


🏇  Improving Feed: Add Post & Comment Data Models

In the feed app, there are posts and comments data models that need to be set up.
The following tasks should be completed:

[x] Create a post data model
[x] Create a comment data model
[ ] Set the feed.html to show the different posts and comments

The post and comment data models should look like the following ERD:

What is the 'comment_parent_ID'?


Fix for arpeggiator release bug.

When the arpeggiator is enabled and the active note is released, the arpeggiator pattern resets. This is described in detail in this thread:
https://www.kvraudio.com/forum/viewtopic.php?f=263&t=535623
Repro steps are:

Turn Arpeggiator on and set it to very slowly arpeggiate through a chord so it’s
easy to hear the problem. .
Hold a 4-note chord.
Immediately AFTER the second or third note in the arpeggio plays, release that
note.
Notice that a) the released note terminates immediately instead of sustaining
until the next note in the arpeggio, and b the arpeggio immediately resets to the
lowest note of the chord. It should continue to the next note in the chord. Notice
that this only occurs if you release your finger immediately AFTER its note plays
in the arpeggio and not if you release it immediately BEFORE it plays.

This PR resolves this issue by introducing the concept of a stale note. Before, if the active note in the arp sequence was released, the midi would be turned off and the arp sequence would be reset. Now, when the active note in the arp sequence is released, that note is marked as stale but the note remains in the cell mapping and the midi stays on.
Later on in advanceArpeggiatorForSplit, when the next note in the arp sequence is determined, we check to see if the previous note in the sequence is stale and remove it from the cell mapping at that time.
The variables I added to NoteTouchMapping increased its size by 2 bytes. Average free memory sits around 11,664 bytes, again about a 2 byte delta.

Thanks Zach, I had a brief look and plan to look further this week.

Thanks Zach, I had a brief look and plan to look further this week.

Great! Please let me know if there's anywhere I can improve, even variable naming. I tried my best to copy the existing style but may have fallen short in some areas. The changes to ls_handleTouches.ino are not something I was very particularly happy with but I was trying to avoid a major refactor there.

I don't see why you would need that change in ls_handleTouches.ino, the existing condition:
 if (!isSwitchLegatoPressed(sensorSplit) && (!isArpeggiatorEnabled(sensorSplit) || !isSwitchLatchPressed(sensorSplit))) {
should already exclude the handleArpeggiatorNoteOff case below, doesn't it?

... actually I read over the ! in !isSwitchLatchPressed(sensorSplit) ... so then the comment becomes, can't
if (!isSwitchLegatoPressed(sensorSplit) && (!isArpeggiatorEnabled(sensorSplit) || !isSwitchLatchPressed(sensorSplit))) {
be changed to
if (!isSwitchLegatoPressed(sensorSplit) && (!isArpeggiatorEnabled(sensorSplit) || isSwitchLatchPressed(sensorSplit))) {
and have the same effect as what you've done?

... but then thinking about the original intent where
noteTouchMapping[sensorSplit].noteOff(sensorCell->note, sensorCell->channel);
is only called inside the if (isArpeggiatorEnabled(sensorSplit)) { if (!isSwitchLatchPressed(sensorSplit)) { branch, your change causes the noteOff registration to happen when latch is on while the arp is running. Is that on purpose?

I think this whole thing can just be
     // reset the pressure when the note is released and that setting is active
     if (Split[sensorSplit].sendZ && isZExpressiveCell()) {
       preSendLoudness(sensorSplit, 0, 0, sensorCell->note, sensorCell->channel);
     }

     // unregister the note <> cell mapping
-    if (!isSwitchLegatoPressed(sensorSplit) && (!isArpeggiatorEnabled(sensorSplit) || !isSwitchLatchPressed(sensorSplit))) {
+    if (!isSwitchLegatoPressed(sensorSplit) && !isArpeggiatorEnabled(sensorSplit)) {
       noteTouchMapping[sensorSplit].noteOff(sensorCell->note, sensorCell->channel);
     }

     // send the Note Off
     if (isArpeggiatorEnabled(sensorSplit)) {
       if (!isSwitchLatchPressed(sensorSplit)) {

That checks out. Much easier to read too. I think the initial source of confusion for me was how Latch should function in the absence of the arp being enabled.

I adapted your changes and tweaked a few things, committed as a separate commit.


Pointer Lock issue

Not sure if there is some setting I don't know about to enable pointer lock.
Code runs fine in browser for "document.body.requestPointerLock();".
No effect on VSCode live preview. Need pointer locking to test a Three.js application.
Can use this code from three.js as a test case.
Live Example
Example Code
If I've missed a setting which enable pointer lock in VSCode, please let me know.
Thank you for the extension, working great otherwise.

This is an upstream issue that won't be addressed in the main editor, so it can't be supported in the embedded preview for live preview. See https://github.com/microsoft/vscode/issues/154198.


Can't open presentations containing 3D objects (MIME type mismatch)

Description
After updating to SDK version 2.14.0 from 2.10.1, I noticed that opening presentations containing 3D objects causes an exception. Error message is similar to "The document cannot be opened because there is an invalid part with an unexpected content type. [Part Uri=/ppt/media/model3d1.glb] [Content Type=model/gltf.binary] [Expected Content Type=model/gltf-binary]."
Information

.NET Target: .NET Framework
DocumentFormat.OpenXml Version: 2.14.0

Repro
Using this test file created with PowerPoint 2019:
3d.pptx
using System;
using DocumentFormat.OpenXml.Packaging;

namespace ReproOxml3dBug
{
    class Program
    {
        static void Main(string[] args)
        {
            using (var presDoc = PresentationDocument.Open("3d.pptx", false))
            {
                Console.WriteLine("Opened successfully");
            }
        }
    }
}

Observed
An exception occurs as shown below:
[Part Uri=/ppt/media/model3d1.glb],
[Content Type=model/gltf.binary],
[Expected Content Type=model/gltf-binary].
   at DocumentFormat.OpenXml.Packaging.OpenXmlPart.Load(OpenXmlPackage openXmlPackage, OpenXmlPart parent, Uri uriTarget, String id, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, RelationshipCollection relationshipCollection, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPart.Load(OpenXmlPackage openXmlPackage, OpenXmlPart parent, Uri uriTarget, String id, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, RelationshipCollection relationshipCollection, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPart.Load(OpenXmlPackage openXmlPackage, OpenXmlPart parent, Uri uriTarget, String id, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.LoadReferencedPartsAndRelationships(OpenXmlPackage openXmlPackage, OpenXmlPart sourcePart, RelationshipCollection relationshipCollection, Dictionary`2 loadedParts)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPackage.Load(Package _package)
   at DocumentFormat.OpenXml.Packaging.OpenXmlPackage..ctor(PackageLoader& loader, OpenSettings settings)
   at DocumentFormat.OpenXml.Packaging.PresentationDocument.Open(String path, Boolean isEditable, OpenSettings openSettings)
   at DocumentFormat.OpenXml.Packaging.PresentationDocument.Open(String path, Boolean isEditable)
   at ReproOxml3dBug.Program.Main(String[] args)

Expected
Just the string "Opened successfully" written to standard output.

Hi @andrewmolyneux, thanks for bringing this to our attention. Just to be thorough, can you provide the steps when you created this in PowerPoint? It looks like there both forms of this content type are referenced by Office source so I want to make sure there isn't an ambiguity in Office.

No problem! FYI I'm using PowerPoint 2019, reporting itself as "Version 2110 (Build 14527.20276 Click-to-Run)".
I can't remember precisely what I did in PowerPoint to create the sample file, but I can reproduce the issue with a file created as follows:

Open PowerPoint
Click "New"
Click "Blank Presentation"
Select the "Insert" tab on the Ribbon
Click "3D Models" on the Ribbon (which invokes the "Online 3D Models" picker)
Click the "Emoji" category
Select any emoji you like (I selected the 14th one from the top left, counting left-to-right then top-to-bottom, but I very much doubt it matters which you pick)
Click the "Insert" button
Select the "File" tab on the Ribbon
Click "Save" and choose a location to save the file

Anecdotally, I've tried using the OXML SDK to open a few PPTX files containing 3D objects, from various sources, and I haven't seen one yet that worked. I might just have been unlucky though 😀

@andrewmolyneux Yes, it looks like the correct MIME type should actually be model/gltf-binary based on standards but PowerPoint writes a '.' instead of a '-'. The references to '-' in the type are actually for the clipboard format (i.e. copying/pasting) in Office. I'll get the whole story but this will likely be an easy fix.

Thanks Tom! I hope it will be an easy fix so I can finally update my app to use a reasonably recent version :smile:

It is definitely an issues introduced in 2.14.0 and it worked as expected in 2.13.1.
I've upgraded DocumentFormat.OpenXml from 2.13.1 to 2.14 on our QA word processing node.
Not it fails daily to open about 300 documents per day (all with *.glb files inside)

I'm testing the fix. Will submit the PR asap.

PR #1075 submitted, @sergey-tihon @andrewmolyneux can you give this a test and verify that it resolves this issue for you?

@tomjebo is there an easy way get binaries from CI to we need to build from source?

@sergey-tihon until the PR is merged, you will have to use the source branch (my branch in this case) to test. Once merged, you can pick up a CI build (see the README).

@sergey-tihon PR #1069 has been reworked. it should be the same result but you might want to retest your scenario to verify. I tested with your original repro file.

This should be in the next release.


Purge Cache for user specific Page

Right now https://members.realdevsquad.com/${username} page is served with Cloudflare. So it's cached copy is served every time. On changing, any user details it doesn't get reflected on the user page.
We needed an API that clears the cache at Cloudfare and we can see the updated Page.
We have created an endpoint /cache/clear/self that grabs a username from the cookies and clears the cache for the respective user.

@SagarBajpai , what will be the behaviour of the route here and when will it get executed? When you say GET /cache/clear/self, that means the client will make a call for clearing the cache? 🤔

@ankurnarkhede User can clear the cache for his page from UI. User can trigger this UI whenever he wants but for a limited number times in a day. On triggering this API, the cache for his page will be purged, so the user can see his updated chanages.

But why should the user care about clearing the cache? It would be a bad UX. 😬
I think if there's no way for us to configure it via Cloudflare, then from the application layer, we can purge the cache for a specific user when we update the user data or update their profile picture. We can handle this in the application and thus the changes would be reflected on the UI.
Opinion? @SagarBajpai , @ankushdharkar

@ankurnarkhede The members page contains the PRs and contributions, but has a 7 day cache. In case a member wants their contribution to appear earlier (say they want to show it to a recruiter as a recent task), in that case, we let the user clear just their details page on the members site

@ankushdharkar , yeah, for the use case of PRs, we do not have a way to check if the resource has changed, as we aren't storing it. In this case, we can have a "Refresh" button on the UI of PR's and contributions which will handle this.
But for user details, can we handle it in the application later, as we know when the resource is getting updated?

A new recruiter may not know they want to click "refresh".  The first load of the page should be fresh.
Let the member control the page cache clearing of their page. Can discuss this more on the call.


Expose NATS options

We need to expose the nats.Options member of the nats.Conn struct in order to adjust params such as the PingInterval, which greatly affects performance during reconnects.

None of the tests pass.

@fraenkel - I had to get the current version of go check:
go get gopkg.in/check.v1
since the import path used is out of date.  All of the tests pass here:
Leons-MacBook-Pro:yagnats sandy$ git branch
  master
* nats_options
Leons-MacBook-Pro:yagnats sandy$ ginkgo
=== RUN   Test
OK: 73 passed
--- PASS: Test (21.86s)
PASS

Ginkgo ran 1 suite in 24.473380599s
Test Suite Passed

I know what needs to change but this too needs to be in the commit.
Look at all the imports.

Added the import change to the commit.  Sorry, wasn't sure if I should do that or leave it before.  Should pass now, I'll watch and fix as necessary.


css mode: scroll-snap-type property isn't supported

Hey! 😃
It seems like the scroll-snap-type is unsupported.
We figured this out in desktop/desktop#6974
The example shown by shiftkey was tested with Codemirror version 5.44.0, he also applied some screenshots. https://github.com/desktop/desktop/issues/6974#issuecomment-468261968

Looks like this isn't a finished standard yet. A pull request that adds it to the list of non-standard property keywords in the mode would be welcome, though.

Can you give me quick detailed information on what needs to be changed?

I think you just have to add the property name to this array:
https://github.com/codemirror/CodeMirror/blob/278503bdb57b874067b71dfd55e9c68e0e5ff44b/mode/css/css.js#L545


Support CURIEs as RDF/JSON predicates?

As a straightforward extension of strict RDF/JSON, consider implementing support for parsing CURIE predicates (e.g. "[foaf:name]" instead of "http://xmlns.com/foaf/0.1/name") in the RDF::JSON::Reader class.

Closing this long dormant issue. Adding CURIE/PName support to RDF/JSON would be an incompatible extension, and is solved by using JSON-LD.


Ignore SIGPIPE reported by nvim 0.4 on exit

Fixes https://github.com/ludovicchabant/vim-gutentags/issues/249.

Note that this is untested - I just happened to have an old checkout of gutentags laying around, and it was reported on IRC.
(I rather update my tags on demand (via make-tags wrapper script), and also during switching of branches in Git.  That's much better performance wise.

Thanks! This solved the problem form me, I had constant 141 error when closing nvim with gutentags

Ah thanks! I was just replying to another pull request about this problem and I had a very similar solution (see https://gist.github.com/ludovicchabant/b3e0477d38d7817fac64d08944f03a35 ). It looks like v:exiting doesn't exist in vanilla Vim, but vanilla Vim somehow doesn't kill the job in a way that prints an error anyway...
Can someone test that Gist with Neovim? If it works, it's probably a slightly better way since we'll have to duplicate that check in 3 other modules. Thanks!

@ludovicchabant I applied your patch and this fixes the gutentags: ctags job failed, returned: 141 for me on NVIM v0.4.2
Here's the applied changes:
~/.vim/plugged/vim-gutentags $ git diff
diff --git a/autoload/gutentags.vim b/autoload/gutentags.vim
index e055f21..34f7eeb 100644
--- a/autoload/gutentags.vim
+++ b/autoload/gutentags.vim
@@ -701,5 +701,10 @@ function! gutentags#statusline_cb(fmt_cb, ...) abort
     return call(a:fmt_cb, [l:modules_in_progress])
 endfunction

+" Set a variable on exit so that we don't complain when a job gets killed.
+function! gutentags#on_vim_leave_pre() abort
+    let g:__gutentags_vim_is_leaving = 1
+endfunction
+
 " }}}

diff --git a/autoload/gutentags/ctags.vim b/autoload/gutentags/ctags.vim
index df56a8a..623f0f9 100644
--- a/autoload/gutentags/ctags.vim
+++ b/autoload/gutentags/ctags.vim
@@ -179,7 +179,7 @@ endfunction
 function! gutentags#ctags#on_job_exit(job, exit_val) abort
     call gutentags#remove_job_by_data('ctags', a:job)

-    if a:exit_val != 0
+    if a:exit_val != 0  && !g:__gutentags_vim_is_leaving
         call gutentags#warning("ctags job failed, returned: ".
                     \string(a:exit_val))
     endif
diff --git a/plugin/gutentags.vim b/plugin/gutentags.vim
index 8353849..41a9991 100644
--- a/plugin/gutentags.vim
+++ b/plugin/gutentags.vim
@@ -87,6 +87,8 @@ else
     let g:gutentags_script_ext = '.sh'
 endif

+let g:__gutentags_vim_is_leaving = 0
+
 " }}}

 " Gutentags Setup {{{
@@ -95,6 +97,7 @@ augroup gutentags_detect
     autocmd!
     autocmd BufNewFile,BufReadPost *  call gutentags#setup_gutentags()
     autocmd VimEnter               *  if expand('<amatch>')==''|call gutentags#setup_gutentags()|endif
+    autocmd VimLeavePre            *  call gutentags#on_vim_leave_pre()
 augroup end

 " }}}

NVIM version:
~/.vim/plugged/vim-gutentags $ vim --version
NVIM v0.4.2
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/tmp/neovim-20190916-88369-176iaxs/neovim-0.4.2/build/config -I/tmp/neovim-20190916-88369-176iaxs/neovim-0.4.2/src -I/usr/local/include -I/tmp/neovim-20190916-88369-176iaxs/neovim-0.4.2/deps-build/include -I/usr/local/opt/gettext/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include -I/tmp/neovim-20190916-88369-176iaxs/neovim-0.4.2/build/src/nvim/auto -I/tmp/neovim-20190916-88369-176iaxs/neovim-0.4.2/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.4.2/share/nvim"

Run :checkhealth for more info
~/.vim/plugged/vim-gutentags $

And showing that once the changes are $ git stash I can trigger the gutentags: ctags job failed, returned: 141 again:
~/.vim/plugged/vim-gutentags $ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   autoload/gutentags.vim
	modified:   autoload/gutentags/ctags.vim
	modified:   plugin/gutentags.vim

no changes added to commit (use "git add" and/or "git commit -a")
~/.vim/plugged/vim-gutentags $ git stash
Saved working directory and index state WIP on master: eecb136 Fix incorrect documentation about default root markers.
~/.vim/plugged/vim-gutentags $ vim ~/work/web/app/models/user.rb
gutentags: ctags job failed, returned: 141~/.vim/plugged/vim-gutentags $


"Version" docker tags broken for many images

Details
A recent refactoring on the docker build introduced a typo in most of the build workflows (missing colon).
The push step pushes e.g. docker.io/raspbernetes/kustomizev3.8.2, and since missing tags are replaced by :latest,
this results in docker images named e.g. docker.io/raspbernetes/kustomizev3.8.2:latest.
But there seems to be another issue for the latest tag, since docker.io/raspbernetes/kustomize:latest does not seem to contain the latest version (neither docker.io/raspbernetes/kustomizev3.8.2:latest nor docker.io/raspbernetes/kustomize:v3.8.2, but something else).
What steps did you take and what happened:
Take a look at the following kustomize version outputs:
$ docker run docker.io/raspbernetes/kustomize:v3.8.2 kustomize version
{Version:kustomize/v3.8.2 GitCommit:e2973f6ecc9be6187cfd5ecf5e180f842249b3c6 BuildDate:2020-09-14T09:28:56UTC GoOs:linux GoArch:amd64}

$ docker run docker.io/raspbernetes/kustomizev3.8.2:latest kustomize version
{Version:kustomize/v3.8.2 GitCommit:e2973f6ecc9be6187cfd5ecf5e180f842249b3c6 BuildDate:2020-09-14T09:28:56UTC GoOs:linux GoArch:amd64}

$ docker run docker.io/raspbernetes/kustomize:latest kustomize version
Version: {Version:unknown GitCommit:$Format:%H$ BuildDate:1970-01-01T00:00:00Z GoOs:linux GoArch:amd64}

What did you expect to happen:

Version tags should be created correctly
kustomize:latest should correspond to the same binary as v3.8.2

Anything else you would like to add:
MR for the :version tag is incoming, but no idea what's wrong with the latest tag.

The latest bug might be something else, and maybe limited to kustomize.
Some auto-updating mechanism (I assume this one: https://github.com/raspbernetes/multi-arch-images/blob/master/.github/workflows/schedule.yml)
reverts the .version file for kustomize regularly, like here:
https://github.com/raspbernetes/multi-arch-images/commits/master/build/kustomize/.version
Most probably because of the changed tagging semantics in kustomize, the version detection goes wrong here.

Yeah, we might need to update the schedule to only pull the latest tag with the correct syntax to avoid the other releases.

Unfortunately there seems to be no easy way to achieve this...
I hacked together the following, but that's a lot more (and ugly) code than the simple single curl...
And while testing this, I ran into the rate limit on the Github REST API as well.
#!/usr/bin/env bash

set -euo pipefail
# Get the first tag for a given github repo matching a given prefix.
# Assumption: Github tags are returned in reverse alphabetical order,
# so the first match will be semantically "latest"
#
# @param REPO: repository name in $ORG/$REPO format
# @param PREFIX: a prefix to filter for. Items not matching the prefix will be ignored.
# @return tag name or empty string if none matched
function get_latest_tag() {
  REPO="$1"
  PREFIX="${2-}"
  PER_PAGE=100
  HEADER_FILE="$(mktemp)"
  trap "rm -f ${HEADER_FILE}" RETURN

  NEXT_URL="https://api.github.com/repos/${REPO}/tags?per_page=${PER_PAGE}"

  while [[ "${TAG-}" == "" && "${NEXT_URL}" != "" ]]; do

    TAG="$(
        curl -sSLD "${HEADER_FILE}" "${NEXT_URL}" \
        | jq -r "[.[].name | select (test(\"${PREFIX}.*\"))] | first // empty" \
    )"

    NEXT_URL="$(
      grep -e '^link:.*' "${HEADER_FILE}" \
      | tr ',' '\n' \
      | grep 'rel="next"' \
      | cut -f2 -d'<' \
      | cut -f1 -d'>'
    )"

  done

  echo "${TAG}"
}

get_latest_tag kubernetes-sigs/kustomize kustomize/

I'm also happy for us to disable the schedule for this particular instance and potentially bump the version ourselves until we have a better solution to avoid it breaking, or creating a schedule in the same workflow and keep it out of the existing schedule.

Disabling it for kustomize would be fine for me as well -- better to have no automation than one that consistently breaks things :)

Feel free to raise a PR to disable, we can comment it out and leave a description as to why it's being no longer managed via the workflow 👍
Thanks for investigating this issue further @easimon

Might have found a simple way that does not require to disable the auto-upgrade. Not bullet-proof, but the current approach is not either, so this might still qualify.


CMAKE build stucks -

When following the installing instructions generator for Linux, Other  (rpi 3) at running the command "cmake --build . --target install", this displays:
Scanning dependencies of target tdsqlite
[ 0%] Building C Object td/sqlite/CMakeFiles/tdsqlite.dir/sqlite/sqlite3.c.o
And the program freezes...(+1 hour)

You are likely have too few RAM available to build it on the device. You need to cross-compile it.

You are likely have too few RAM available to build it on the device. You need to cross-compile it.

What should I do?

You need to cross-compile it.

I'm newbie 😩
I need guide

I can't help this that, but https://stackoverflow.com/questions/19162072/how-to-install-the-raspberry-pi-cross-compiler-on-my-linux-host-machine and similar articles likely can.


having this kind of issue when running.

Help would be appreciated.
Using the latest version of Python.
Windows 10.
Traceback (most recent call last):
File "G:\Media\Compressed\vHackXTBot-Python-master\utils.py", line 92, in md5hash
m.update(txt)
TypeError: Unicode-objects must be encoded before hashing
Edit:
Managed to fix this error, but another pops out:
File "G:\Media\Compressed\vHackXTBot-Python-master\utils.py", line 161, in requestString
except urllib.URLError as e:
AttributeError: module 'urllib' has no attribute 'URLError'
Edit 2: fixed it by adding .error. between the urllib and URLError.
Afterwards, I get this error:
a bytes-like object is required, not 'str'
and loops.

@JustAViewer
vHackXTBot-Python is currently outdated.
Use vHackOSBot-Java if you want.

the bot don't work for python3 please just install python2.7 please read the readme