Use vendoring?

Currently, we have a vendor/ directory, which indicates that we want to use vendored dependencies. However, the project doesn't currently use vendored dependencies consistently.
In particular:

Some of the dependencies are missing from the vendor/ directory

You can see it by typing go build -mod=vendor: this command is going to complain about missing dependencies
The fix would be to run go mod vendor and commit the updated vendored dependencies [1]

The README doesn't instruct users to use the -mod=vendor option. Without this option, the vendored dependencies are ignored [2]
The CI build doesn't use vendored dependencies (it doesn't use -mod=vendor)
The CI build doesn't check the integrity of dependencies (it doesn't call go mod verify) [3]
I'm not sure whether hlf-k8s uses vendored dependencies when instanciating the chaincode?

Hence my question:  Do we want to use vendored dependencies?
If so, in order to be consistent, we should address the points above :)
[1] https://tip.golang.org/cmd/go/#hdr-Make_vendored_copy_of_dependencies
[2] https://tip.golang.org/cmd/go/#hdr-Modules_and_vendoring
[3] https://tip.golang.org/cmd/go/#hdr-Verify_dependencies_have_expected_content

@AurelienGasser : It looks like we doesn't use vendor, we may to remove it no ?

Back to the hyperledger 1, it was the only way to install the needed library since we didn't have the hand on the docker image. If you can now use modules (with internet or a proxy), the go.mod and go.sum files are enough. That depends on the new chaincode life cycle.

As to answer how this vendoring was done, it was indeed by running go mod vendor but to limit the size of the vendor it was the libraries that was already present from the chaincode image was removed by hand.
And for how it's used, a vendor file will be automatically used by go since 1.6 I think. But it's not the recommended way since go modules ensures the version of the dependencies now.

So we can remove it safely ? :)

Like I said, it depends on your chaincode lifecycle and its image building. Which I'm not certain I'm up to date with now...

Chaincode has now a docker image build with this dockerfile https://github.com/SubstraFoundation/substra-chaincode/blob/master/Dockerfile
It's the image which is use with the new lifecycle

Assuming the build process has access to internet (which is likely but it does not hurt to mention it), yes you can definitely remove this turd of vendor files. I'm going to validate your PR right now.

Yes, it has internet as substra-chaincode is on docker hub :D


The links when hovered give better UI

The links when hovered give better ui as now i have given proper padding at various places in the html webpage.
issue solved #98

@jobara please review it?

@aashimgarg I'm not sure what issue this is actually addressing. I've left a comment on the related issue asking for more details.

Fixed changes @jobara !

@aashimgarg Thanks for the contribution; however, I don't think the issue has been fully discussed yet.

It can be closed without merging.

This PR won't be merged as we are currently beginning a redesign process. Thanks for your contribution!


Pointer events support

Indigo doesn't have support for touch screens. It can be brought through Pointer Events API. This implementation could also cover existing mouse support, making it a facade on top of pointer events. In the future we could also add some helpers for common gestures.
Original discussion: https://discord.com/channels/716435281208672356/716435281208672359/1069683337238691861
Will also resolve https://github.com/PurpleKingdomGames/indigo/issues/55

Did you manage to get any further with this @grzegorz-bielski?
No pressure, I only ask because I'm hoping to cut a new release in the next couple of weeks and it would be an awesome addition. If you're not going to be ready though, don't sweat it. :smile:

Still on it! You can follow the progress on this branch.
What's left is adding some gesture handlers to make the pointers events support more useful from the get go ... and further testing.
Not sure if I'll be able to finish it for the next release though.


azure-mgmt-mixedreality is causing docs CI build errors

Build log: https://apidrop.visualstudio.com/Content CI/_build/results?buildId=212523&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=348f8a99-4a85-56c7-5436-e2f3858e80ba&l=102683
Partial error output
<Matched Warning>: D:\a\1\s\source_code\81\azure_mgmt_mixedreality-0.2.0\doc\azure.mgmt.mixedreality.rst:20: WARNING: autodoc: failed to import module 'azure.mgmt.mixedreality.version'; the following exception was raised:
looking for now-outdated files... none found
##[error]<Matched Error>: Traceback (most recent call last):
  File "c:\hostedtoolcache\windows\python\3.6.8\x64\lib\site-packages\sphinx\ext\autodoc.py", line 551, in import_object
    __import__(self.modname)
ModuleNotFoundError: No module named 'azure.mgmt.mixedreality.version'

This will be removed from the ref docs to unblock the build.

The failure was occurring on version 0.2.0.
The latest version is 1.0.0. Adding back to pipeline.

Verified it builds ok in this build.


Haskell-ghc-mod: ghc-mod command list failed with error code 1

Atom Version: 1.7.3
System: Mac OS X 10.11.4
Thrown From: haskell-ghc-mod package, v1.13.1
Stack Trace
Haskell-ghc-mod: ghc-mod command list failed with error code 1
At caps: {"version":[5,5,0,0],"fileMap":true,"quoteArgs":true,"optparse":true,"typeConstraints":false,"browseParents":false,"interactiveCaseSplit":false}
URI: undefined
Args: --
message: Warning: /Users/stephenokennedy/.cabal/config: Unrecognized field ghc-options
on line 176

cabal: At least the following dependencies are missing:

distributed-process -any, network-transport-tcp -any

ghc-mod: readCreateProcess: cabal "configure" "--with-ghc=ghc" "--flags" "" (exit 1): failed

log:
-1.364s: running ghc-mod list,-- with options.cwd = /Users/stephenokennedy/Development/haskell/cloud-haskell/map-reduce,options.env = [object Object],options.encoding = utf-8
-1.281s: ghc-mod said: Warning: /Users/stephenokennedy/.cabal/config: Unrecognized field ghc-options
-1.281s: ghc-mod said: on line 176
-0.009s: ghc-mod said: cabal: At least the following dependencies are missing:
-0.009s: ghc-mod said: distributed-process -any, network-transport-tcp -any
-0.004s: ghc-mod said: ghc-mod: readCreateProcess: cabal "configure" "--with-ghc=ghc" "--flags" "" (exit 1): failed
-0.001s: ghc-mod ended with code 1
-0.001s: code 1: Warning: /Users/stephenokennedy/.cabal/config: Unrecognized field ghc-options
on line 176

cabal: At least the following dependencies are missing:

distributed-process -any, network-transport-tcp -any

ghc-mod: readCreateProcess: cabal "configure" "--with-ghc=ghc" "--flags" "" (exit 1): failed

code 1: Warning: /Users/stephenokennedy/.cabal/config: Unrecognized field ghc-options
on line 176

cabal: At least the following dependencies are missing:

distributed-process -any, network-transport-tcp -any

ghc-mod: readCreateProcess: cabal "configure" "--with-ghc=ghc" "--flags" "" (exit 1): failed

    at module.exports.Util.mkError (/Users/stephenokennedy/.atom/packages/haskell-ghc-mod/lib/util.coffee:212:15)
    at BufferedProcess.exit (/Users/stephenokennedy/.atom/packages/haskell-ghc-mod/lib/ghc-mod/ghc-modi-process-real.coffee:101:20)
    at triggerExitCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:215:47)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:222:18
    at Socket.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:100:18)
    at emitOne (events.js:82:20)
    at Socket.emit (events.js:169:7)
    at Pipe._onclose (net.js:469:12)

Commands
     -6:41.1.0 editor:move-to-first-character-of-line (atom-text-editor.editor.is-focused)
     -6:40.6.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -6:40.6.0 snippets:expand (atom-text-editor.editor.is-focused)
     -6:40.6.0 editor:indent (atom-text-editor.editor.is-focused)
     -6:39.8.0 core:backspace (atom-text-editor.editor.is-focused)
     -6:38.7.0 core:move-down (atom-text-editor.editor.is-focused)
  2x -6:38.5.0 core:move-left (atom-text-editor.editor.is-focused)
     -6:37.6.0 core:move-right (atom-text-editor.editor.is-focused)
     -6:37.2.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -6:37.2.0 snippets:expand (atom-text-editor.editor.is-focused)
     -6:37.2.0 editor:indent (atom-text-editor.editor.is-focused)
     -6:34.2.0 core:move-down (atom-text-editor.editor.is-focused)
  2x -6:33.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -6:29.7.0 core:save (atom-text-editor.editor.is-focused)
     -3:18.9.0 editor:select-to-first-character-of-line (atom-text-editor.editor.is-focused)
     -0:02.3.0 autocomplete-plus:activate (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "autocomplete-html",
      "language-groovy",
      "go-config",
      "go-get"
    ]
  },
  "haskell-ghc-mod": {
    "additionalPathDirectories": [
      "/usr/local/bin"
    ]
  }
}

Installed Packages
# User
angularjs, v0.3.4
atom-ternjs, v0.14.1
autocomplete-haskell, v0.6.5
autocomplete-modules, v1.4.1
autocomplete-python, v1.7.2
environment, v1.2.0
file-icons, v1.7.11
hashrocket, v0.4.10
haskell-ghc-mod, v1.13.1
ide-haskell, v1.6.3
ide-haskell-cabal, v1.3.3
ide-haskell-stack, v0.0.3
language-ejs, v0.2.0
language-haskell, v1.7.15
language-lisp, v0.2.0
linter, v1.11.4
linter-eslint, v7.2.2
linter-ruby, v1.2.2
minimap, v4.23.5
minimap-git-diff, v4.3.1
navigator-godef, v1.0.3
node-debugger, v1.7.0
python-tools, v0.6.7
react, v0.15.0
terminal-panel, v1.14.1
tester-go, v1.0.4

# Dev
No dev packages

Sorry, I was being an idiot making this issue. I'm new to haskell, stack and cabal. Managed to fix the error by running cabal install.

No problem, it's what 'create issue' button is for.
A couple tips:

If using cabal, use sandboxes (cabal sandbox init in project root) -- globally installing packages will lead to much grief later, when you want to update something.
You can use cabal install --only-dependencies to install, you guessed it, only dependencies, and not the package itself. In most cases, you don't want to install package you're working on at the moment.
Prefer stack to cabal-install if you can. Stack is much friendlier to beginners for the most part, provided you don't try to mix resolvers.

Cheers!! I'll keep those tips in mind.


(build) Disable documentation of build script tasks

Disable generation of build script tasks documentation

@pascalberger I am not too concerned either way, but was there a compelling reason for turning this off?

@gep13 I think the question is what's the target audience of this documentation? End-users or developers?
End-users would not be interested in the build scripts available to building the application. Having a "Tasks" menu item that prominent, which also doesn't explain what kind of tasks it documents, is probably quite confusing for them.
For developers having a list of tasks provided by the underlying build script recipe is probably also not that much of an intereset as it doesn't show the actual build process used for this repo (e.g. some tasks are disabled by configuration but still shown here). If we want to have documentation about the build process for developers I would find it much more helpful to have a chapter somewhere mentioning that it uses Cake.Recipe with a link to the Cake.Recipe documentation where the individual tasks already are documented, and additional documentation about repo specific configuration and additional tasks. Or topic specific documentation, like done for the Localization Howto.


Awesome

Any ability to share what it's been like to run this in lieu of CHP? I've been curious about this approach for a while and still don't have the background with both Lua and Lua+nginx.

:D It's all new, but so far it's provided me all the same features of CHP, without having to setup things from npm. There might be performance improvements too, but hard to tell without https://github.com/jupyter/configurable-http-proxy/issues/49.
It's still missing a bunch of features (SSL support, proper logging, documentation!) so I'll probably announce it on the list once I add those (hopefully over the weekend)

@rgbkrk We've been using this on a fairly busy hub and it has eliminated 503 proxy errors. (knock on wood) So far so good.

yeah, that was the deal for us too. random 503s were completely eliminated when we switched to this.


2022 predictions: fix links, add timestamp for Ben

Though browsers are quite tolerant, tags feel better when closed. :-)

oof... thank you!


Don't scan frames other than current in popup

This accidentally reuses windows in other frames, especially when there are multiple compliation buffers.

Good catch! Thanks!


Add techmapping description

This PR adds information about the techmapping process in the SymbiFlow toolchain.

This looks pretty good but I haven't had time to read the technical details.
Can you get @litghost to look at it?


Migrated to Swift 3 syntax

Hi @oliverkulpakko, and my sincerest apologies. I haven't got any updates on this repo for some reason for new PRs and haven't really looked at them in a long while. I updated this to Swift 4 already, so closing this in favor of the new version.


Invalid Cloud Password Error

Description
Upon creating/ linking the cameras to HA via the intergation, it says my cloud password is invalid.
I am 1000% sure it is the correct password.
Tapo C320
Reproduction Steps

Expected behavior
Accept the password and load the integration for the first time/ a working camera stream.
If applicable, add error logs.
No response
Device Firmware
1.3.9 Build 231024 Rel.7332n(4555)
Integration Version
n/a
Using stream component
Yes
Does camera work via official integrations?
N/A
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HA OS on Proxmox VE
Search for similar issues
Yes
Additional information
No response

Integration Version
n/a
First, make sure to use the latest version.

Reset your password
Make sure your camera can access the internet
Reboot it a few times
Remove the camera from account
Factory reset
Add it back, with internet access
Add to this integration, it will work if you are entering correct password.

Versión de integración
n/a

Primero, asegúrese de utilizar la última versión.

Restablecer su contraseña
Asegúrese de que su cámara pueda acceder a Internet
Reinícialo varias veces
Quitar la cámara de la cuenta
Restablecimiento de fábrica
Agréguelo nuevamente, con acceso a Internet
Agregue a esta integración, funcionará si ingresa la contraseña correcta.

Esto sigue funcionando? Imposible vincular unantapp c212 nueva....

I just got a new Tapo C225 V2.x
Firmware is 1.0.7
Integration Version is 5.4.18
Camera is in the network, has internet access and is visible and controllable in the Tapo app.
I did all the steps above a hundred times, I am 100% sure to use the correct camera account credentials and a different password for my cloud account.
Finally, it does still reject the cloud password and i have no more ideas what to try.
Any help or ideas?

Yes see pinned issue.

OK, sorry, I did see that of course, but it is not clear at the first look, it's this issue. The whole process feels like I am doing a mistake or mixing up my setup.
Just a very little and friendly hint: Maybe you change 2 little things to get less messages from idiots like me ;)

Integrate the words "Invalid cloud password" in the pinned topics headline to make it more clear that's the error. For me, the statement "makes the integration stop working" was a different kind of issue then my experience being unable to set it up for the first time.

The FAQ / Troubleshooting for "Invalid cloud password" in the integrations' description sound like a general and just normal procedure. Maybe you can add a more clear warning there, that there is a explicit issue there right now, that can not be solved by following the steps.

Thanks for your work, your last info updates from today sounds promising, so i will just wait a few days or weeks for the new "official" method.
Thanks, have a nice day!

Thank you for the feedback @RealCommerzpunk . You’re right I will update the docs and the issue soon to make it clearer.

Updated both, @RealCommerzpunk hopefully this is now more apparent.

same here, with all my tapo devices:
c100 +  c200
message: Invalid cloud password. Make sure you are entering the password for your cloud account and NOT the password which you created via the camera settings (unless they are the same). You need to enter password which you used with your email when signing into the Tapo app.
thinks i have done:
factory reset
change passwords
disable 2fa
without luck

I can confirm I'm having the same problem. Restarted, reset etc still run into invalid cloud password.


No default Target location indicated after scripting migration

[Enter feedback here]
Please at least provide the target location (directory) for the generated script in the Docs after running 'dotnet ef migrations script'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 06b35eff-79e4-2068-6d1c-f9079d43f903
Version Independent ID: 6c575b10-048c-349c-397e-0d9c11d47235
Content: Applying Migrations - EF Core
Content Source: entity-framework/core/managing-schemas/migrations/applying.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: avickers

@CutieDaisy The default target is to send the script to standard out.


Models' checkpoint(s) availability

Hello
Thank you for your work.
Will there be available any checkpoints for models?

Hello.
Yes, we try to make all checkpoints available soon and there will be an update to the repository providing the corresponding hyperlinks. If you need any checkpoints now, please let me know and we can send the files.


Revert "Update pycairo requirement"

This reverts commit 17558a4bd516526ec7f7b20adfb9ed489f5d261e.
By using ">=" in requirements, the package can get broken anytime. This has happened - on linux, 1.18.1 will be installed, resulting in this exception when using manim:
Traceback (most recent call last):
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/flask/cli.py", line 236, in locate_app
    __import__(module_name)
  File "/home/soeren/Projects/manim-gallery/src/app.py", line 9, in <module>
    from examples import hello_world
  File "/home/soeren/Projects/manim-gallery/src/examples/hello_world.py", line 1, in <module>
    from manimlib.imports import *
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/manimlib/__init__.py", line 3, in <module>
    import manimlib.extract_scene
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/manimlib/extract_scene.py", line 9, in <module>
    from manimlib.scene.scene import Scene
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/manimlib/scene/scene.py", line 11, in <module>
    from manimlib.camera.camera import Camera
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/manimlib/camera/camera.py", line 9, in <module>
    import cairo
  File "/home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/cairo/__init__.py", line 1, in <module>
    from ._cairo import *  # noqa: F401,F403
ImportError: /home/soeren/anaconda3/envs/manim-gallery/lib/python3.7/site-packages/cairo/_cairo.cpython-37m-x86_64-linux-gnu.so: undefined symbol: cairo_svg_surface_set_document_unit

Should be fixed by #571.

I ended up installing manim with pycairo 1.18.1 in an empty docker container and didn't run into this. It seems like the problem occurs when you have two different versions of pycairo installed at once [1]. What did you do when you ran into the error?

I had a fresh virtual environment (conda) when it happened, and previously only installed manim in other envs, not globally. Strange issue, I'll see if I can reproduce it properly :/

iam who have some issued as same on you, fixed by #835


Document clearTransactionIOS API method

Hi, i could not see the method call clearTransactionIOS documented in README.md.
Is there a reason for this, or should it be added?
BTW: Thanks for this API ! Solved my problem with the official in_app_purchase package.
Version of flutter_inapp_purchase
2.2.0

I could add this to the README.md, but would be nice to get some feedback from the author - not sure if this is an active project anymore?

@erf does finishtransactionIos work for you ?

@louieseno i use clearTransaction, which should call clearTransactionIOS, and it should work, but that is not related to this issue, or?


patch: simplify handling of adding a file

Instead of using a separately managed variable, just fully rely on what the patch header is telling us.

Codecov Report
Patch coverage: 75.00% and project coverage change: +0.05 :tada:

Comparison is base (9fd8665) 89.66% compared to head (8f19a7c) 89.71%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
+ Coverage   89.66%   89.71%   +0.05%
==========================================
  Files          19       19
  Lines        2042     2033       -9
  Branches      878      872       -6
==========================================
- Hits         1831     1824       -7
  Misses         77       77
+ Partials      134      132       -2

Impacted Files
Coverage Δ

src/patch.cpp
89.29% <75.00%> (+0.28%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Proxy Configuration Issue in Bruno v1.28+

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Since version 1.28 of Bruno, when configuring "proxy enabled" and "proxy pass" for a specific domain within a collection, requests that bypass the proxy return the following error:
Error invoking remote method 'send-http-request': Error: unable to verify the first certificate.
If the proxy is disabled or when using version 1.27, everything works as expected.
.bru file to reproduce the bug
No response
Screenshots/Live demo link
v1.31:

same issue, but different error msg 1.28+
SSL is disabled -> not working

I have merged the PR for this fix.
@Ved_Sharma please test the resolution once v1.34.0 is live

@giuseppemilicia, could you please check if the issue is resolved in version v1.34.0?

@helloanoop the issue has been fixed in version v1.34.0


junit report in gitlab

haven't gotten code coverage working yet

maybe close this pull request and add a link in the html to add issues and pull requests directly to the gitlab repo page. https://gitlab.com/tobiaskoch/gitlab-ci-example-dotnetcore/merge_requests/2


Flesh out and edit the introduction/background

I felt the intro/background was limited in the use cases covered by this document. I fleshed it out a bit, and did some general grammar edits.
I think this PR could handle feedback from others as well.

Yes will do another pass in the morning


fix(rust): Update author for Rust example package

This PR fixes the author field in the Rust example package to be "The Kythe Authors"

Made obsolete by #4611


[Azure.AzBlob] UploadBufferToBlockBlob InvalidHeaderValue

Bug Report

"github.com/Azure/azure-sdk-for-go/sdk/storage/azblob"
Go.mod
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v0.2.0
Go version
go version go1.16.13 linux/amd64

What happened?

I try to upload a file using SAS token.

         URLDirectory := fmt.Sprintf("%s/?%s", uri, SAS_TOKEN) //sv=....

	service, err := azblob.NewServiceClientWithNoCredential(URLDirectory, nil)
	if err != nil {
		return errors.Wrap(err, "NewBlockBlobClient")
	}
	container := service.NewContainerClient("images")

	// Branch off of the container into a block blob client
	blockBlob := container.NewBlockBlobClient("HelloWorld.txt")

	data := "Hello world!"
	_, err = blockBlob.UploadBufferToBlockBlob(ctx, []byte(data), azblob.HighLevelUploadToBlockBlobOption{})
	if err != nil {
		return errors.Wrap(err, "UploadBufferToBlockBlob")
	}

I've no problem to download element from container. Despite I get those erreur when trying to upload
===== RESPONSE ERROR (ErrorCode=InvalidHeaderValue) =====
Description=The value for one of the HTTP headers is not in the correct format.
RequestId:3340a11e-801a-0094-6300-0e2fb1000000
Time:2022-01-20T13:19:30.3011919Z, Details:
HeaderName: Content-Length
HeaderValue: 12

What did you expect or want to happen?

I expect to be able to uplad and download file without error using SAS token in URI

How can we reproduce it?

Just try to Upload a file using a SAS token

Anything we should know about your environment.

All my sincere apologized.
I was testing https://xxx.file.core.windows.net VS https://xxx.blob.core.windows.net
I close that issue with hope it could help someone distracted has I am!
Best regards team!


Outdated mime-types dependency

mime-types dependency was defined in https://github.com/Erol/yomu/commit/26686f88adad436c62cba8da4f045766ac617ffb using the ~>.
However, the version hasn't been updated since. This causes bundlerto complain if you have gems that depend on more current versions installed.
This is the case with Mechanize, for instance, which depends on 'mime-types ~> 2.0' and is a perfect companion to Yomu :smile:

Thank you for pointing this out. Let me check first if it's fine to just allow all versions of mime-types above 1.23.

See #40

@rewritten So simple! Looks great.
@Erol Any plans to commit? Thanks!


Gene categories are plotted arbitrarily...

Hello @trvinh,
really nice work. I'm trying to use gene categories to get a better overview. Although categories are plotted, I was under the impression that genes are also ordered according to their gene category, but rows of categories are somewhat arbitrarily ordered (at least I cannot see a pattern here, see below).

How to change this? I tried to order my gene categories file alphabetically (by categories) but this changed essentially nothing.
By the way, what does Retain gene order do exactly? And how are genes actually ordered, by FAS scores or any other variable?
Cheers Bastian

Hi @trvinh,
thanks for your quick response. I'll try your suggestions.
Cheers Bastian

Hi,
it works. However, I encountered a different problem. Once I change the x-axis to gene and select "Kingdom" (or any other taxonomic label) the plot shows Error: [object Object].. When I switch back to taxa on the x-axis, the plot is fine. Just to let you know.
Cheers Bastian

Hi Bastian,
thanks for the info! I will check it :)
Cheers,
Vinh

Now it is possible to rotate the plot and also display the taxonomy clade name

If some of the clade names are not completely shown, you can increase the space of the clade name area using the Height for group label option in the Plot appearance configuration pop-up menu.

Cheers,
Vinh

Sry,
but it's not working for me. Note I'm using a sorted list to order taxa and a gene category file. And turned off Order seed IDs.
Cheers

Hi @trvinh
but your genes are not ordered by category, right?
And yes, I also see v1.18.0.
Cheers Bastian

It doesn't matter if I order the genes in the main input file or not, when the option Order seed IDs is turned off, the genes will remain their order as in the input file.

Now it works,
many thanks for your help. It's an awesome programm.
Cheers Bastian

Thanks for your feedback, Bastian! ;)


Add some clarification on "Recommended versus Optional"

There is very often the question of how to distinguish between Recommended attributes and Optional attributes.
Upon discussing this with some OCSF adopters, it seems one major distinction is that recommended empowers security teams to place more weight on deciding whether or not to log the attribute.
Adding some sentences to help emphasize this important distinction.

Looks good, along with the .md file, we'll need to update the corresponding pdf file as well - Understanding OCSF.pdf


Bump IDEA Version to 2020.1

We need to migrate to modern APIs to support the Dynamic Plugin feature of 2020.1 PR #66

Resolved by PR #67


Error trying to start HTTP API - cenkalti/backoff timer exception

I am getting an error trying to run the binary. Steps to reproduce:
docker run -it ubuntu:18.04 bash

apt-get update
apt-get -y install wget git gcc
wget --no-check-certificate https://dl.google.com/go/go1.13.5.linux-amd64.tar.gz
tar -C /usr/local -xzf go1.13.5.linux-amd64.tar.gz
echo "export PATH=$PATH:/usr/local/go/bin" >> /etc/profile
source /etc/profile
go version
cd

# Original instructions to build binary
git clone https://github.com/joohoi/acme-dns
cd acme-dns
export GOPATH=/tmp/acme-dns
go build

# This is needed otherwise a database file cannot be created
adduser --system --gecos "acme-dns Service" --disabled-password --group --home /var/lib/acme-dns acme-dns
# Start binary using default config.cfg from repo
./acme-dns

This ends up with the following output:
root@796d06c1261c:~/acme-dns# ./acme-dns
INFO[0000] Using config file                             file=./config.cfg
INFO[0000] Connected to database
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=A
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=NS
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=SOA
INFO[0000] Listening DNS                                 addr="<IP_ADDRESS>:53" proto=udp
INFO[0000] Listening DNS                                 addr="<IP_ADDRESS>:53" proto=tcp
INFO[0000] 2020/01/09 01:50:26 [INFO][cache:0xc0000aa550] Started certificate maintenance routine
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x887735]

goroutine 24 [running]:
time.(*Timer).Stop(...)
        /usr/local/go/src/time/sleep.go:74
github.com/cenkalti/backoff/v3.(*defaultTimer).Stop(0xc0000a20b0)
        /tmp/acme-dns/pkg/mod/github.com/cenkalti/backoff/v3@v3.2.1/timer.go:32 +0x25
github.com/cenkalti/backoff/v3.RetryNotifyWithTimer.func1(0xb8ae60, 0xc0000a20b0)
        /tmp/acme-dns/pkg/mod/github.com/cenkalti/backoff/v3@v3.2.1/retry.go:45 +0x31
github.com/cenkalti/backoff/v3.RetryNotifyWithTimer(0xc0002ae0c8, 0x7f5378069438, 0xc00028c3a0, 0x0, 0xb8ae60, 0xc0000a20b0, 0x0, 0x0)
        /tmp/acme-dns/pkg/mod/github.com/cenkalti/backoff/v3@v3.2.1/retry.go:53 +0x34d
github.com/cenkalti/backoff/v3.RetryNotify(...)
        /tmp/acme-dns/pkg/mod/github.com/cenkalti/backoff/v3@v3.2.1/retry.go:31
github.com/cenkalti/backoff/v3.Retry(...)
        /tmp/acme-dns/pkg/mod/github.com/cenkalti/backoff/v3@v3.2.1/retry.go:25
github.com/go-acme/lego/v3/acme/api.(*Core).retrievablePost(0xc0001241e0, 0xc00040c400, 0x3a, 0xc000290260, 0x1d, 0x20, 0x9d4a80, 0xc0000704e0, 0xc000116208, 0xc0000705a0, ...)
        /tmp/acme-dns/pkg/mod/github.com/go-acme/lego/v3@v3.2.0/acme/api/api.go:107 +0x210
github.com/go-acme/lego/v3/acme/api.(*Core).post(0xc0001241e0, 0xc00040c400, 0x3a, 0xa7e460, 0xc0000705a0, 0x9d4a80, 0xc0000704e0, 0x0, 0xc0001162d0, 0x8886ce)
        /tmp/acme-dns/pkg/mod/github.com/go-acme/lego/v3@v3.2.0/acme/api/api.go:70 +0xf5
github.com/go-acme/lego/v3/acme/api.(*AccountService).New(0xc0001242a0, 0x0, 0x0, 0x1170730, 0x0, 0x0, 0x1, 0x0, 0x0, 0x0, ...)
        /tmp/acme-dns/pkg/mod/github.com/go-acme/lego/v3@v3.2.0/acme/api/account.go:16 +0x150
github.com/go-acme/lego/v3/registration.(*Registrar).Register(0xc00028c2c0, 0xc000087e01, 0xc0000de640, 0x3a, 0xc00028e568)
        /tmp/acme-dns/pkg/mod/github.com/go-acme/lego/v3@v3.2.0/registration/registar.go:58 +0x139
github.com/mholt/certmagic.(*Config).newACMEClient(0xc0001240f0, 0x0, 0x0, 0x0, 0x0)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/client.go:221 +0x3d7
github.com/mholt/certmagic.(*Config).newManager(0xc0001240f0, 0xc0000a0600, 0x10, 0x0, 0x0, 0x0)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/client.go:121 +0x3ad
github.com/mholt/certmagic.(*Config).ObtainCert(0xc0001240f0, 0xb8cae0, 0xc00009e030, 0xc0000a06c0, 0x10, 0x0, 0x0, 0x0)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/config.go:455 +0xc6
github.com/mholt/certmagic.(*Config).manageOne(0xc0001240f0, 0xb8cae0, 0xc00009e030, 0xc0000a06c0, 0x10, 0xa96dc0, 0xc000109120)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/config.go:411 +0x115
github.com/mholt/certmagic.(*Config).manageAll(0xc0001240f0, 0x0, 0x0, 0xc0002af3d8, 0x1, 0x1, 0x0, 0x0, 0x0)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/config.go:394 +0x1d1
github.com/mholt/certmagic.(*Config).ManageSync(...)
        /tmp/acme-dns/pkg/mod/github.com/mholt/certmagic@v0.9.0/config.go:320
main.startHTTPAPI(0xc000070960, 0xc00009e440, 0xc, 0xc00009e468, 0x4, 0xc0000a06c0, 0x10, 0xc0000a0700, 0x10, 0xc0000a0740, ...)
        /root/acme-dns/main.go:166 +0x1025
created by main.main
        /root/acme-dns/main.go:92 +0x977

If this is an issue caused by using the default config.cfg, what do I need to change to make it work?

Oh, I'm awfully sorry. The first attempt to fix the original issue in #201 apparently introduced this bug. The module update commit is reverted by the PR referenced above.

To be honest, I don't think PR #203 introduced this.
See my comment from the other closed #201 .
https://github.com/joohoi/acme-dns/issues/201#issuecomment-571897398
I was getting this same exact error prior to you merging in #203 .
Are you able to follow my steps above and get the same errors?

Nevermind.
I rebuilt against:
commit 3d5a512d1ed5c437d133ac9839a7cd31b8275c89 (HEAD -> master, origin/master, origin/HEAD)

It seems to be working now.
root@796d06c1261c:~/acme-dns# ./acme-dns
INFO[0000] Using config file                             file=./config.cfg
INFO[0000] Connected to database
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=A
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=NS
DEBU[0000] Adding new record to domain                   domain=auth.example.org. recordtype=SOA
INFO[0000] Listening DNS                                 addr="<IP_ADDRESS>:53" proto=udp
INFO[0000] Listening DNS                                 addr="<IP_ADDRESS>:53" proto=tcp
INFO[0000] 2020/01/09 07:04:22 [INFO][cache:0xc0000a85f0] Started certificate maintenance routine
INFO[0000] 2020/01/09 07:04:23 [INFO][auth.example.org] Obtain certificate
INFO[0000] [INFO] [auth.example.org] acme: Obtaining bundled SAN certificate
INFO[0001] [INFO] [auth.example.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791525
INFO[0001] [INFO] [auth.example.org] acme: Could not find solver for: tls-alpn-01
INFO[0001] [INFO] [auth.example.org] acme: Could not find solver for: http-01
INFO[0001] [INFO] [auth.example.org] acme: use dns-01 solver
INFO[0001] [INFO] [auth.example.org] acme: Preparing to solve DNS-01
INFO[0001] [INFO] [auth.example.org] acme: Trying to solve DNS-01
INFO[0001] [INFO] [auth.example.org] acme: Checking DNS record propagation using [<IP_ADDRESS>:53]
INFO[0001] [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
INFO[0008] [INFO] [auth.example.org] acme: Cleaning DNS-01 challenge
INFO[0008] [INFO] Unable to deactivate the authorization: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791525
INFO[0008] 2020/01/09 07:04:31 [ERROR][auth.example.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
INFO[0008] [auth.example.org] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.auth.example.org, url: (attempt 1/3; challenge=dns-01)
INFO[0009] [INFO] [auth.example.org] acme: Obtaining bundled SAN certificate
INFO[0010] [INFO] [auth.example.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791553
INFO[0010] [INFO] [auth.example.org] acme: Could not find solver for: tls-alpn-01
INFO[0010] [INFO] [auth.example.org] acme: Could not find solver for: http-01
INFO[0010] [INFO] [auth.example.org] acme: use dns-01 solver
INFO[0010] [INFO] [auth.example.org] acme: Preparing to solve DNS-01
INFO[0010] [INFO] [auth.example.org] acme: Trying to solve DNS-01
INFO[0010] [INFO] [auth.example.org] acme: Checking DNS record propagation using [<IP_ADDRESS>:53]
INFO[0010] [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
INFO[0017] [INFO] [auth.example.org] acme: Cleaning DNS-01 challenge
INFO[0017] [INFO] Unable to deactivate the authorization: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791553
INFO[0017] 2020/01/09 07:04:40 [ERROR][auth.example.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
INFO[0017] [auth.example.org] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.auth.example.org, url: (attempt 2/3; challenge=dns-01)
INFO[0018] [INFO] [auth.example.org] acme: Obtaining bundled SAN certificate
INFO[0018] [INFO] [auth.example.org] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791591
INFO[0018] [INFO] [auth.example.org] acme: Could not find solver for: tls-alpn-01
INFO[0018] [INFO] [auth.example.org] acme: Could not find solver for: http-01
INFO[0018] [INFO] [auth.example.org] acme: use dns-01 solver
INFO[0018] [INFO] [auth.example.org] acme: Preparing to solve DNS-01
INFO[0018] [INFO] [auth.example.org] acme: Trying to solve DNS-01
INFO[0018] [INFO] [auth.example.org] acme: Checking DNS record propagation using [<IP_ADDRESS>:53]
INFO[0018] [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
INFO[0018] [INFO] [auth.example.org] acme: Cleaning DNS-01 challenge
INFO[0019] [INFO] Unable to deactivate the authorization: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/31791591
INFO[0019] 2020/01/09 07:04:41 [ERROR][auth.example.org] failed to obtain certificate: acme: Error -> One or more domains had a problem:
INFO[0019] [auth.example.org] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.auth.example.org, url: (attempt 3/3; challenge=dns-01)
FATA[0020] auth.example.org: obtaining certificate: failed to obtain certificate: acme: Error -> One or more domains had a problem:
[auth.example.org] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.auth.example.org, url:
root@796d06c1261c:~/acme-dns#

Thanks!


Scrolling does not work on Firefox

As the title says: Scrolling does not work on Firefox.

Hi, can you confirm if you enabled layout.css.overflow-overlay.enabled in about:config? #1

Can you confirm if you updated to the latest Firefox version,

If the issue persists after doing both, let me know.

I did not have it enabled and Firefox is updated.
With layout.css.overflow-overlay.enabled enabled it now works.


Main classes for Gui and Generate for non-maven use

Main methods could take class names as input to activate plugins. Plugins must be on the classpath


BUG: app crashes out when deleting/adding a lot of postgres rules

no errors just exits

woops this is kubernetes readiness probes!


Saeedrashidi astra dev reorg

The following changes have happened:
i) the symlinks have been deleted
ii) more subfolder structure has been added to the system layer src files to place relative classes into the same subdirectories

This looks mostly good -- yay no symlinks! -- but one piece of feedback: the include paths shouldn't be prefixed by "src" -- they should just start with "astra-sim". You can do this with the current directory structure, but it's messy; I'd prefer you get rid of the src directory entirely and just put astra-sim back in the base directory.
This is because if you're including astra-sim from another library -- or installing it on a system as a globally available library -- you don't want to have the src/ path conflicting with every other project's src/ folder. You want a clean library path namespace.
Once this is done, you can change everything that looks like this:
#include "src/astra-sim/system/AstraSimDataAPI.hh"

to this:
#include "astra-sim/system/AstraSimDataAPI.hh"

This looks mostly good -- yay no symlinks! -- but one piece of feedback: the include paths shouldn't be prefixed by "src" -- they should just start with "astra-sim". You can do this with the current directory structure, but it's messy; I'd prefer you get rid of the src directory entirely and just put astra-sim back in the base directory.
This is because if you're including astra-sim from another library -- or installing it on a system as a globally available library -- you don't want to have the src/ path conflicting with every other project's src/ folder. You want a clean library path namespace.
Once this is done, you can change everything that looks like this:
#include "src/astra-sim/system/AstraSimDataAPI.hh"

to this:
#include "astra-sim/system/AstraSimDataAPI.hh"

The code structure is based on google doc description. For now, I will push this PR and then discuss it with @srinivas212 about removing the src from source file structures.


Fix preference initialization in installer.java

Fixes issue #643
Brief summary of changes
Default Experimental Marker radius is specified in two places, one of them was not updated. Fixed in this PR and added comment to indicate that change in one place should update the other.
Testing I've completed
CHANGELOG.md (choose one)

no need to update because bugfix

A more general but significant change would be to create a singlteon DefaultPreferences object to hold values, eventually use that to reset Preferences to Defaults and use it across the board to initialize all preferences. Which would address issue #961 as well


Add support for supplying OrbitOutliers to M&E, IPOD

Added OrbitOutliers to ipod, passes through all callers up to merge & extend.
The only two places the outliers are referenced are at the beginning of ipod, and after each run of precovery. I have ipod currently rejecting the outliers and refitting at the very beginning - bit strong default behavior.
Could use a glance. Ignoring X05 (Rubin) for now since I was having trouble in my environment, but should be tested with multiple active observatory codes.

Obviously let's get the linting and unit tests to pass on CI and then merge.


Add to PyPI

Let's get this up on PyPI so users can install via pip

This is now done: https://pypi.python.org/pypi/dplython


Strange property transformer behavior

Describe the bug
When a property transformer is added in a recipe with ~3 or more other transformers, the properties do not get applied to the dataset.

If I try to add all 5 other transformers at one time, it DOES NOT WORK
If I add it by itself, it WORKS
If I add it first, by itself, then add the other 4 transformers after that and process again, it WORKS
If I add all 5 transformers to start, then remove them one-by-one, with just two other transformers remaining, it WORKS

To Reproduce
Steps to reproduce the behavior:

Create an S3 ingestion pipeline
Add the following transformers (see attachment for example): simple_add_dataset_properties, simple_add_dataset_tags, simple_add_dataset_terms, simple_add_dataset_domain, simple_add_dataset_ownership
Check a dataset ingested from S3 to see if the transformers were applied properly

Expected behavior
I would expect the transformers to all be applied, regardless of how many are added to the recipe
Desktop (please complete the following information):

OS: macOS
Browser: Safari
Version: 16.0
DataHub Version: 0.9.0

Additional context
s3_recipe_example.txt

When you say works/doesn't work, that just means that the properties aren't added? In all cases, the ingestion run completes without printing any errors?

Sorry for the lack of clarity. The ingestion pipeline executes successfully in each scenario. The 'works' or 'does not work' refers to whether the properties are successfully applied to the datasets or not.

We've recently made some fixes to the properties transformer - could you test with acryl-datahub v<IP_ADDRESS> and let me know if it works?

Hi @jamesrobsn, were you able to test? Otherwise I'll go ahead and close this issue.

Hello, I had a chance to test on <IP_ADDRESS> and it looks like the issue is resolved. Thank you for you patience!


E3001 Invalid or unsupported Type AWS::GuardDuty::Filter for in eu-west-3

cfn-lint version: 0.46.0
Description of issue.
Error E3001 Invalid or unsupported Type AWS::GuardDuty::Filter for in eu-west-3 returned when deploying a template containing an AWS::GuardDuty::Filter resource in the eu-west-3 region.
Please provide as much information as possible:

Template linting issues:

Please provide a CloudFormation sample that generated the issue.

AWSTemplateFormatVersion: 2010-09-09

Resources:
  Detector:
    Type: AWS::GuardDuty::Detector
    Properties:
      Enable: True

  SampleFilterRule:
    Type: AWS::GuardDuty::Filter
    Properties:
      Rank: 1
      Name: SampleFilterRule
      Description: Sample filter rule
      Action: ARCHIVE
      DetectorId: !Ref Detector
      FindingCriteria:
        Criterion:
          service.action.awsApiCallAction.api:
            Eq:
              - DescribeInstances

If present, please add links to the (official) documentation for clarification.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-guardduty-filter.html
The AWS::GuardDuty::Filter resource is available in eu-west-3 but its resource specification is missing from https://d2d0mfegowb3wk.cloudfront.net/latest/gzip/CloudFormationResourceSpecification.json.

Validate if the issue still exists with the latest version of cfn-lint and/or the latest Spec files

Confirmed that the issue persists after updating cfn-lint to 0.46.0 and running cfn-lint --update-specs. Also confirmed that the template deploys successfully without linting.

AWS::GuardDuty::Filter is now published to the eu-west-3 resource specification, should get picked up by this now:
cfn-lint --update-specs


Why bidirectional assignability is not equivalent to identicality?

This might be a lack of deeper understanding on how TypeScript really works, but:

index.d.ts
export declare type Foo = { foo: string; };
export declare type Bar = { bar: number; };
export declare type FooBar1 = Foo & Bar;
export declare type FooBar2 = { foo: string; bar: number; };
export declare const foobar1: FooBar1;
export declare const foobar2: FooBar2;

index.test-d.ts
import { expectType, expectAssignable } from 'tsd';
import { FooBar1, FooBar2, foobar1, foobar2 } from '.';

expectAssignable<FooBar1>(foobar1); // ok
expectAssignable<FooBar1>(foobar2); // ok
expectAssignable<FooBar2>(foobar1); // ok
expectAssignable<FooBar2>(foobar2); // ok

expectType<FooBar1>(foobar2); // not ok
expectType<FooBar2>(foobar1); // not ok

Is this a bug on tsd or a bug on my understanding of TypeScript?
Regardless, I think a clarification for this might be useful for many people (so consider this a suggestion part of #55)
Thanks in advance!

Bonus (and note to self):
type Foo = { foo: string };
type Bar = { bar: number };

export type FooBar1 = Foo & Bar;
export type FooBar2 = { foo: string; bar: number };
export interface FooBar3 extends Foo, Bar {}
export interface FooBar4 extends FooBar1 {}
export interface FooBar5 extends FooBar2 {}
export interface FooBar6 extends Foo { bar: number }
export interface FooBar7 extends Bar { foo: string }
export interface FooBar8 { foo: string, bar: number }

With tsd I found that:

All 8 exported types (FooBar1 until FooBar8) are bidirectionally assignable to each other (checked via expectAssignable)
Types FooBar2 until FooBar8 are identical to each other (checked via expectType)
Type FooBar1 is not identical to any of the other exported types (FooBar2 until FooBar8)  (checked via expectType)

So I am starting to believe this is probably a misunderstanding of TypeScript by me.

More information can be found here. https://github.com/Microsoft/TypeScript/blob/master/doc/spec.md#3.11.2

they are both the Any type,
they are the same primitive type,
they are the same type parameter,
they are union types with identical sets of constituent types, or
they are intersection types with identical sets of constituent types, or
they are object types with identical sets of members.

In this use case, the last two bullet points apply:

they are intersection types with identical sets of constituent types, or
they are object types with identical sets of members.

In case of FooBar1, we have an intersection type. Two types are identical if they both are an intersection type with the same end result. But in your use case, you have an intersection type and an object type and TS doesn't think they are identical.
Meaning, if you do this instead
export declare type Foo = { foo: string; };
export declare type Bar = { bar: number; };
export declare type Baz = { bar: number; };
export declare type FooBar1 = Foo & Bar;
export declare type FooBar2 = Foo & Baz;

FooBar1 and FooBar2 are considered identical. You wil have to ask the TS team themselves why they can't be considered identical, tsd just uses the TS APIs under the hood to verify both types.
I hope this answers your question?

I'm closing this as I believe I answered your question and I want to reduce the number of open issues :).


AppSync GraphQL list operations not scaling - only querying a fraction of my data

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v16.15.1
Amplify CLI Version
10.0.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
I just launched my app yesterday and unexpectedly went from just my small fleet of testers (5 users) to about 1000 users.
I discovered that at scale, the "listSomething" AppSync query only pull from a fraction of the total data in that table. So if I have 1000 users, and I filter for users with X email, I'm only searching 100 or so of the total users, so it's not going to find that user. This results in issues such as account duplication because I can't enforce uniqueness.
I know I should probably enforce uniqueness on the tables themselves, but this still seems odd that AppSync would by default not query your entire dataset in a filtered listing. Is it mandatory that I implement "@searchable" on any table where I want to search the entire dataset? Do I need to manually increase the limit, or paginate every time I want to scan the whole table? There are certain tables where it's necessary for me to return thousands of results.
"Get" operations are okay, as well as "search" for the tables that are using open search.
Seems like there's a default limit in AppSync queries of 100. Is this correct?
I am not using DataStore.
Expected behavior
AppSync "list" operations should search my entire dataset.
Reproduction steps
Create any table
Create 1000 entries in that table
Query for all entries, observe that only a fraction of the 1000 total are returned
Project Identifier
report-1681584503593.zip
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @justinjaeger, when using a DynamoDB data source with AppSync, the list operation is implemented using the Scan operation in DynamoDB. The Scan operation reads every item in the table or index and can be inefficient and expensive when working with large data sets.
To optimize your list operations and ensure that you are searching your entire data set, you can consider using a Global Secondary Index (GSI) to support your list operation with a filter. A GSI allows you to create a secondary index on one or more attributes other than the primary key. By defining the right GSI, you can optimize your list operations and ensure that you are searching the entire data set. Refer our docs.
In terms of enforcing uniqueness, you can use the @primaryKey directive as mentioned here.
You don't necessarily need to use the "@searchable" directive to search your entire data set, but it can help optimize your search operations by creating a search index on the specified fields. If you want to return thousands of results, you can use the Paginated List pattern or increase the scan limit for your DynamoDB table. However, keep in mind that increasing the scan limit can increase the time and cost of your queries, so it's important to use pagination or other optimization techniques where possible.

Hi there, I fixed this issue by implementing GSIs wherever I was using the list operation with a filter. I see how it's much more efficient and is closer to the intended structure for DynamoDB operations. I definitely wasn't utilizing GSIs to the fullest extent.
So as a general rule for anyone encountering this post, wherever you WOULD use a "scan and filter" operation in SQL ("get all posts where userId is X"), you should be using a GSI. "List" operations are really best used with pagination like scrolling through ALL posts and lazy loading them as you scroll.
Crucially, as @rvtraveller explained, there's a default limit of 100 on any list query. And, filtering does NOT happen on the server side as with SQL. Instead, it returns all data, then filters on the client side, making any "scan and filter" operation extremely inefficient.
I definitely could have done more digging to understand this but I also think it's easy to overlook if your expectation is, as serverless architecture likes to promise, to be frontend focused. It would be great to have the Amplify docs get a little more under the hood or to link to some essential DynamoDB documentation so it's not as easy to overlook.
I'm happy to keep this closed and appreciate the help. Thanks!


Update list settings types

I want to merge this change because... it updates list settings types.

PR intended to be tested with API branch:  master
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-3575 Fix product type translations


Istio Breaking Multus Network Management After Overwriting Existing Pod Annotations

Bug Description
If a pod has an annotation that points to an existing NetworkAttachmentDefinition for Multus, when injecting a sidecar, Istio overwrites the the network annotation (ex: k8s.v1.cni.cncf.io/networks: macvlan-conf) with k8s.v1.cni.cncf.io/networks: istio-cni.  This breaks Multus' network management by preventing macvlan-conf from executing. Istio should be appending istio-cni to the annotation, to get k8s.v1.cni.cncf.io/networks: macvlan-conf, istio-cni.
@dougbtv wrote an in-depth gist article on the effects of this issue here: https://gist.github.com/dougbtv/babe9b59e4d54e7a0fc67f134b74b908
Here is a configuration that can replicate the issue: https://gist.github.com/jacob-delgado/bb3a08d21e13130e6b685df75ec54a10
cc @dougbtv @jwendell @dgn
Version
Known Istioctl versions affected 1.11-current

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Discussion on #45036 has determined that this issue is being caused by the instructions to add the following annotation to installation overrides files:
    sidecarInjectorWebhook:
      injectedAnnotations:
        k8s.v1.cni.cncf.io/networks: istio-cni

This is duplicating the work of the appendMultusNetworks function in the helm configuration and is causing the appended multus configurations to be overwritten during helm installation.


feat: refresh monitored downloads before getting queue items

Description
Currently, we sync with sonarr/radarr with whatever value those return. Radarr/Sonarr syncs the activity from the download clients every few minutes. This leads to inaccurate estimated download times, because of the refresh delay with Jellyseerr and the *arrs.
This PR fixes this by making a request to the *arrs to refresh the monitored downloads just before we get these downloads information.
Screenshot (if UI-related)
To-Dos

[x] Successful build pnpm build
[ ] Translation keys pnpm i18n:extract
[ ] Database migration (if required)

Issues Fixed or Closed

Re #866

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

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


Enhancement Suggestion - Monthly instead of Yearly

How about switching your solution to download by the month? Add a month dropdown. My situation is such that my taxes are done on a fiscal year end (3/31 in my case), not a calendar year. Plus, if the earnings throughout the year effect a person's (or business's) income enough, they could also need the information to file quarterly estimated tax payments.
I am not enough of a programmer to be able to tell if making the output download smaller would help performance on your system or against whatever API you may be using, but maybe that would be a benefit too.  Thank you...!

I would consider if enough interest, please discuss here: https://github.com/davetapley/helium-tax/discussions/80


Problem to $persist

I dont know why I cant persist and object... I got:
fetch, push and destroy works well.
vuex-orm-graphql.es5.js?8eb2:1 Uncaught (in promise) TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at Function.e.transformOutgoingData (vuex-orm-graphql.es5.js?8eb2:1)
    at Function.e.addRecordToArgs (vuex-orm-graphql.es5.js?8eb2:1)
    at Function.eval (vuex-orm-graphql.es5.js?8eb2:1)
    at eval (vuex-orm-graphql.es5.js?8eb2:1)
    at Object.eval [as next] (vuex-orm-graphql.es5.js?8eb2:1)
    at eval (vuex-orm-graphql.es5.js?8eb2:1)
    at new Promise (<anonymous>)
    at __awaiter (vuex-orm-graphql.es5.js?8eb2:1)
    at Function.t.call (vuex-orm-graphql.es5.js?8eb2:1)

Sector,js
import { Model } from '@vuex-orm/core'

export default class Sector extends Model {
  static entity = 'sectors'

  static fields () {
    return {
      id: this.number(null),
      name: this.string(''),
    }
  }
}

store/index.js
import Vue from 'vue';
import Vuex from 'vuex';
import VuexORM from '@vuex-orm/core';
import VuexORMGraphQL from '@vuex-orm/plugin-graphql';
import { AuthModule } from './auth-module';
import { HttpModule } from './http-module';
import { SettingsModule } from './settings-module';
import { CustomAdapter } from '@/plugins/graphql-adapter';
import ApolloClient from '@/plugins/apollo-client';

// Create a new instance of Database.
const database = new VuexORM.Database();

// Models
import User from '@/models/User';
import Sector from '@/models/Sector';
import Subsector from '@/models/Subsector';
import Segment from '@/models/Segment';

// Register Models to Database.
database.register(User);
database.register(Sector);
database.register(Subsector);
database.register(Segment);

VuexORM.use(VuexORMGraphQL, {
	database,
	adapter: new CustomAdapter(),
	apolloClient: ApolloClient
});
Vue.use(Vuex);

export default new Vuex.Store({
  plugins: [VuexORM.install(database)],
  modules: {
    auth: AuthModule,
    http: HttpModule,
    settings: SettingsModule
  },
});

Sector.vue
<script>
import Sector from '@/models/Sector';

export default {
	data() {
		return {
			sector: {},
		}
	},
	async mounted() {
		await Sector.fetch();
	},
	computed: {
		sectors: () => Sector.all(),
	},
	methods: {
		newf() {
			this.sector = {};
		},
		edit(sector) {
			this.sector = sector;
		},
		async create() {
			await Sector.insert({data: this.sector});
			const sector = Sector.query().last();
			await sector.$persist();
		},
		async update() {
			await this.sector.$push();
		},
		async destroy(sector) {
			await sector.$deleteAndDestroy();
		}
	}
};
</script>

For Vuex ORM the key of model is attribute "$id" as we can see in:
vuex-orm/query/Query.ts
private deleteById (id: string | number | (number | string)[]): Data.Item {
    const item = this.find(id)

    if (!item) {
      return null
    }

    return this.deleteByCondition(model => model.$id === item.$id)[0]
  }

When the model has increment id, its set to "$id" and "id" attributes the key value, but when the model doesnt have increment id , its set the fictitious key only to "$id" attribute.
Then, the plugin cant get data by "id" attribute on:
plugin-graphql/orm/model.ts
public getRecordWithId(id: number) {
    return this.baseModel
      .query()
      .withAllRecursive()
      .where("id", id)
      .first();
  }

In where should be "$id".
Another problem, its seems possible in Vuex ORM have more then one attribute as model key and plugin graphql is not prepered for this situation, as we can see in:
Vuex ORM/model/Model.ts
async $delete (): Promise<Item<this>> {
    const primaryKey = this.$primaryKey()

    if (!Array.isArray(primaryKey)) {
      return this.$dispatch('delete', this[primaryKey])
    }

    return this.$dispatch('delete', (model: this): boolean => {
      return primaryKey.every(id => model[id] === this[id])
    })
  }

@vuex-orm/core 0.34 solves the problem of null id, because Uid generate to $id and id attributes. But the plugin still dont work with composite keys

With the latest release, the plugin works with Vuex-ORM 0.36. Feel free to reopen the issue when the problem still exists :)

Thank you very much for the update =]

This is still an issue as it tries to convert a string id into a number before performing the search query.
https://github.com/vuex-orm/plugin-graphql/blob/50d0bb689bcc8dd7b0db4692ca51f2596621db6c/src/orm/model.ts#L267

I am using string ids in many of my models. Hat to fork the Repo and remove all "toNumber" calls in the code. Hope it will be fixed soon

With generated $id: "tyr13zqj"
I have the same error Uncaught (in promise) TypeError: Cannot convert undefined or null to object.
Seems that now (vuex-orm/core 0.36.3) it not prefixed with $uid in models:
id: this.uid(() => tempId()) // tempId returns 'tyr13zqj' value
But in plugin code we have
getRecordWithId(id) {
    return this.baseModel
        .query()
        .withAllRecursive()
        .where("id", toPrimaryKey(id))
        .first();
}

where toPrimaryKey is
function toPrimaryKey(input) {
    if (input === null)
        return 0;
    if (typeof input === "string" && (input.startsWith("$uid") || isGuid(input))) {
        return input;
    }
    return parseInt(input.toString(), 10);
}

Why you need that conversion in plugin? Just return string if that is string!


Icon not working on Expo 48 android

🐛 Bug Report

To Reproduce
Steps to reproduce the behavior:
Expected behavior

Link to runnable example or repository (highly encouraged)
https://github.com/abhisin98/ui-icon

UI Kitten and Eva version

Package
Version

@eva-design/eva
2.2.0

@ui-kitten/components
5.3.0

@ui-kitten/eva-icons
5.3.0

Environment information
Node: 18.15.0
npm: 9.5.0

I solved this problem by editing the file<EMAIL_ADDRESS>diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index b382042..f68ee7d 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -15,8 +15,8 @@ class EvaIcon {
         const Icon = this.content;
         const { style, ...svgProps } = props;
         // @ts-ignore - UI Kitten components pass here `tintColor`
-        const fillColor = react_native_1.StyleSheet.flatten(style || {}).tintColor;
-        return (<Icon style={props.style} fill={fillColor} {...svgProps}/>);
+        const  {tintColor, ...rest} = react_native_1.StyleSheet.flatten(style || {})
+        return (<Icon style={rest} fill={tintColor} {...svgProps}/>);
     }
 }
 exports.EvaIcon = EvaIcon;

That is still problem for me.  Did you make a pull request for that fix ? @abhisin98


Short step name is eaten as a previous step's argument in some cases

Let's say I want to spare few key strokes and run just 'discover' and 'provision' of the plan:
$ tmt run pl -n /plans/sanity/lint disc provin -h connect
Unsupported discover method 'connect'.

I need to write full name of the provision (or add options to the discover step) for tmt to parse it properly:
$ tmt run pl -n /plans/sanity/lint disc provision -h connect
/var/tmp/tmt/run-071

/plans/sanity/lint
    discover
        how: shell
        summary: 2 tests selected
    provision
        how: connect
Provide a host name or an ip address to connect.

With the patch in the following,
diff --git a/tmt/options.py b/tmt/options.py
index 3bdbd21..1bf0e9a 100644
--- a/tmt/options.py
+++ b/tmt/options.py
@@ -235,6 +235,9 @@ def create_method_class(methods: MethodDictType) -> Type[click.Command]:
     Methods should be already sorted according to their priority.
     """

+    def is_likely_subcommand(arg: str, subcommands: List[str]) -> bool:
+        return any(subcommand.startswith(arg) for subcommand in subcommands)
+
     class MethodCommand(click.Command):
         _method: Optional[click.Command] = None

@@ -263,6 +266,8 @@ def create_method_class(methods: MethodDictType) -> Type[click.Command]:
                 # Stop search at the first argument looking like a subcommand
                 elif arg in subcommands:
                     break
+                elif is_likely_subcommand(arg, subcommands):
+                    break

             # Find method with the first matching prefix
             if how is not None:

The test result of tmt run pl -n /plans/sanity/lint disc provi -h connect looks good.
$ tmt run pl -n /plans/sanity/lint disc provi -h connect
/var/tmp/tmt/run-004

/plans/sanity/lint
    discover
        how: shell
        summary: 2 tests selected
    provision
        how: connect

Provide a host name or an ip address to connect.
$ tmt run pl -n /plans/sanity/lint disc provision -h connect
/var/tmp/tmt/run-005

/plans/sanity/lint
    discover
        how: shell
        summary: 2 tests selected
    provision
        how: connect

Provide a host name or an ip address to connect.


Various updates

Fix typos

@EdDev could you please take a look?

@EdDev FYI: I do not have write access here/cannot merge this.

@tyll You should have it now.


Form Recognizer - Move to the new proxy server based recorder

See https://github.com/azure/azure-sdk-for-js/issues/17994 for details

@HarshaNalluru implemented this, so I'm closing this issue.

Thanks for closing the issue. 😎


Gymnasium

Are there any current efforts/ roadmap items/ interest in moving acme and/or dm2gym to Farama Foundation Gymnasium?

acme uses the dm_env interface, but if you want to work with Gymnasium environment you can use the Gymnasium wrapper in https://github.com/kevinzakka/dm_env_wrappers that I contributed a while ago.


Fix unique key prop

No idea if this was actually causing errors, but this fixes the console warnings at least.

When and where did you get warnings?

Ah, sorry for not mentioning that. When opening the Assets tab in the event details modal. And also when looking at the info for a specific media file in the Assets tab in the event details modal.


log formatting improvements

This PR adds some small improvements to log outputting:

Output logger metadata when level <= debug
Output file info when level <= debug

Vapor 4 in .trace.

Vapor 4 in .info (default)

Hey @tanner0101, you just merged a pull request, have a coin!
You now have 1191 coins.


Models for the physical sample

Description
It's still missing the fields from PHA4GE but I think it's easier to throw them in after people agree to the general concepts.
Depends on #30, #42
Issue
ch64743
Test plan
Ran migration.

I updated this with the latest round of revisions, along with some annotations on the db columns.


Snwoflake v2.4.0

Overview
SNOW-XXXXX

Pre-review checklist

[ ] This change should be part of a Behavior Change Release. See go/behavior-change.
[ ] This change has passed Merge gate tests
[ ] Snowpipe Changes
[ ] Snowpipe Streaming Changes
[ ] This change is TEST-ONLY
[ ] This change is README/Javadocs only
[ ] This change is protected by a config parameter <PARAMETER_NAME> eg snowflake.ingestion.method.

[ ] Yes - Added end to end and Unit Tests.
[ ] No - Suggest why it is not param protected

[ ] Is his change protected by parameter <PARAMETER_NAME> on the server side?

[ ] The parameter/feature is not yet active in production (partial rollout or PrPr, see Changes for Unreleased Features and Fixes).
[ ] If there is an issue, it can be safely mitigated by turning the parameter off. This is also verified by a test (See go/ppp).

@JonathonO Yes, we have deployed it for all connector, tenant-metadata is only using plugin-default entry for all.
I will extract wrapper branch after excluding auto create schema commits.


The Adaptive Cards service is down

Describe the bug
We are currently following with the Adaptive Cards Template service team to identify if the service is something we should be relying on as today its certificate is expired. https://github.com/microsoft/adaptivecards-templates/issues/302

Additional context
It might be possible that we have to rely on a "local" version of these templates as the service is still in pre-alpha phase and doesn't offer any support.

My suggestion would be to bring the .json files directly in the GE repo for now and serve them. This templating service is alpha and got confirmation this is unlikely to go past that stage.

Does this mean there won't be any new templates?

In the service, yes. We will be rolling out new templates, but we will have to identify where to store / promote them.


Convert some resource types in the inspector

In case you don't know what happens in the GIFs above, I'm dropping a texture directly into a material_override field and it automatically creates a material with this texture as albedo. Then I drop a shader onto material slot and it automatically creates a ShaderMaterial with this shader assigned.
This is done in a pretty generic way so it's easy to add more auto-conversions like this.
Closes #27079
Addresses https://github.com/godotengine/godot-proposals/issues/96#issuecomment-535247671

Needs a rebase on current master to fix CI.

Thanks!


Add support for addition gap CSS

As pointed out in #41 there are additional gap options that are now widely supported.
Add  row-gap and column-gap as available options.

This should now be available in v1.5.0


Don't hardcode default block type

PR added as a reference and reminder, I will clean it up

@silviubogan you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

@silviubogan you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

@silviubogan you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

@silviubogan you need to sign the Plone Contributor Agreement in order to merge this pull request.
Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

Superseded by master


Side Panel (design): new visual

Motivation
Give some focus on the side panel when open. The goal is to create a clearly different instance for a dataset and its associated plugins
Acceptance criteria

Clearly define what belongs to overall informations (the header) and what belongs to the different plugins.
Give access to a resize handle on the side to have more or less space inside the panel.

TODO
☑ show a message when resource is deprecated
☑ a resource can have multiple types
☑Complete the Copy button
☑ show the URL, ID, Address with revision

how to deal with tags?
☑ Missing 'add to cart'
☑ When an older revision is selected, we are missing a message warning the user. In addition when this message is displayed, provide a link to the latest.

☑ Missing links to Organization and Project

Not in Scope

editing the name of the resource
Brain region in the head informations

Figma
https://www.figma.com/file/lnhIF3FNFllLLzWdP0d3g4/BBP->-Prototypes?node-id=57%3A28436
Mockups
Global Side Panel

Three size states
Narrow

Extended

Measurement

Dropdown drawer

Dropdawn

Closing now, will be restructured as an other set of tickets.


sizingStyle = .distributed,don't distribute the tabs

sizingStyle = .distributed
when ViewControllers more than 5,for example 6
it shows error.

I change MSSTabBarViewMaxDistributedTabs to 6.
that's ok.


Failed to Jailbreak

Had v<IP_ADDRESS> for a while then my device randomly rebooted, saw an update, updated to <IP_ADDRESS> then tried to jaulbreak and this popped up:

Dopamine fail to jailbreak.txt

can you use Filza(trollstore version) to zip and upload /var/mobile/Library/Logs/CrashReporter

Upgrade the software roothide core from 0.0.8 (default) to 0.0.9
then restart this error will appear.


How to track 500 errors?

I'm having an issue with imgproxy (?) which is not very clear. My CND reports there are ~2K 500 error responses daily observed. An indeed there are some errors in the logs regarding invalid original image urls. However its just few of them, like 4-5 a day and I'm not sure if its reported as 500 or 404 error.
Any clues how do I investigate the issue?
My setup is imgproxy -> traefik -> cnd (bunny.net).
I've checked the logs at traefik and imgproxy and havent found anything to that rate. Unfortunately there are no specific failure URLs (all reported 500 error imgproxy-urls are working fine every time I check it but it may be the result of bunny retries.

Ok. Cloudflare says it's gateway timeout errors. Is it imgproxy issue? https://cln.sh/KqdShh

Hey!
Sorry for the delay, I was on vacation without access to GH.
Gateway timeout (504) means that your gateway (I guess it's traefik) didn't get a response from the origin (imgproxy) in the expected time. Try to increase traefik timeouts.

@DarthSim makes sense, I'll try that. Does timeout errors are reported by imgproxy itself?

If you mean reporting to Honeybadger, Sentry, etc, then no, they're not reported. imgproxy just responds with 503 in case of timeouts.

@DarthSim I've ment logging. Does such errors are bing reported with default  IMGPROXY_LOG_LEVEL = info ?

Yeah, sure:
ERROR   [2021-06-07T12:36:14Z] Completed in 1.890393855s /unsafe/rs:fill:312:312/wm:0.5:nowe/pd:10/plain/local:///animated_gif3.gif  request_id=8ZDeacYK9uhMIKbXV6OIp method=GET status=503 error="Timeout after 1.89033474s"

@DarthSim what should I do when I see this type of errors:
Could not load image. Using fallback image: Get "https://static.convertiser.com/media/product_images/266/de47ed9c1bae4ec2da7af851d2a5a4d2/962c5d3b5e92d26b27e1d96b44c64f825a37536a.jpg": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

My timeouts are already increased to 20s
IMGPROXY_READ_TIMEOUT=20
IMGPROXY_WRITE_TIMEOUT=20
IMGPROXY_KEEP_ALIVE_TIMEOUT=20
IMGPROXY_DOWNLOAD_TIMEOUT=20

and yet, problem still happens every once in a while. Sometimes it's Cloudflare temporary issue, sometimes (surprisingly) AWS3. Sometimes this logs have different body:
Could not load image. Using fallback image: context deadline exceeded (Client.Timeout or context cancellation while reading body)

Could not load image. Using fallback image: Can't download image; Status: 502;
<title>502 Bad Gateway</title>

502 Bad Gateway

cloudflare

As I can never catch this problem online (checking failing URLs always works) I was wondering if there is or planned connection retry functionality?
Is that possible that timeouts can be related to imgproxy itself. LA is low, but you know I can try to spawn more instances in case it may help mitigate timeouts (I feel it will not help and it's probably Cloudflare/s3 issues...)

It's also would be nice to have requested URL in logs when something like Could not load image. happens. Otherwise it's kinda hard to track issues on backend level.

"context deadline exceeded" error kind means that the request for the source image was timed out. I'll try to change the message to something more informative.
As for image URLs in errors, imgproxy always logs URLs of failed requests, so you can determine the source URL from it.

As for image URLs in errors, imgproxy always logs URLs of failed requests, so you can determine the source URL from it.

Sorry, this is not the case when using a fallback image. I'll try to do something here.

Added some improvements of error messages to v2.16.5

@DarthSim thanks! I'll deploy it right away!


Implement line numbers support.

@pushrax for review
Depends on https://github.com/Shopify/liquid/pull/614
Implement line number calculation in the liquid extension so that we don't need to fallback to ruby liquid when using the line_numbers: true option.

Benchmark with line number supports on master
              parse:       22.8 (±4.4%) i/s -       1366 in  60.052357s
        parse & run:       18.9 (±5.3%) i/s -       1129 in  60.036080s

on this branch
              parse:       65.7 (±4.6%) i/s -       3930 in  59.999107s
        parse & run:       23.3 (±4.3%) i/s -       1398 in  60.059979s

performance without line number support was comparable between master and this branch.  Here is the benchmark results on master:
              parse:       69.3 (±7.2%) i/s -       4140 in  60.069889s
        parse & run:       23.3 (±4.3%) i/s -       1390 in  59.997252s

and on this branch
              parse:       69.4 (±5.8%) i/s -       4152 in  60.038627s
        parse & run:       23.2 (±4.3%) i/s -       1390 in  60.002630s

:+1: - thank you for taking care of this, it's great to kill that inconsistency with Ruby Liquid.


[YARN] MXNet on YARN Example

Now everything is ready for distributed training, and we have an AWS example here for a ssh based distributed training on bare mental.
However, more cluster scheduler compatible way of job submission can naturally be supported, as DMLC comes with the trackers for all platforms including YARN. This thread is opened to call for an example on training mxnet on YARN.
Anyone who are interested can reply.  @mli correct me if I am wrong
As far as I know, all the things needed are

[ ] YARN cluster with GPU
[ ] Modify https://github.com/dmlc/dmlc-core/blob/master/tracker/dmlc_yarn.py to add latest env variable of ps-lite, maybe involve modify appmaster a bit.
[ ] Put data on hdfs or s3, and submit as usual.

exciting works

@qiaohaijun would you be interested in working on this

Any plan for Mesos?

any progress on this?
I probably would like to use MXNet on Hadoop / Yarn, however the lack of documentation is a real obstacle

why was this closed if it is not resolved?

please...
?


Cleanup old messages and blobs

We need to develop a mechanism for removing old messages. Messages should be removed when a feed drops out of our social graph.
When messages are removed we should also remove associated blobs. Blobs should also be most likely removed after they haven't been used for a while unless they are a blob that we created. Alternatively we should simply always remove blobs that were not created by us after a specific amount of time.

tricky issues around multiple accounts.


Use of Long in JSONRPCClient

Need to use something like BigInteger instead of Long for Ethereum
See
https://github.com/MelbourneDeveloper/CryptoCurrency.Net/blob/d7e2ec1fb1f97c528e91ef83c873ca199df565e0/src/CryptoCurrency.Net/APIClients/BlockchainClients/JSONRPCClientBase.cs#L93
See GetEthereumAddresses for addresses that break the JSONRPCClient

Please follow this branch https://github.com/MelbourneDeveloper/CryptoCurrency.Net/tree/Issue%231

There is an example of how to do this in the Blockscout API. But, maybe it's better to investigate how it's done in Nethereum.


[20.09] treewide: intial mark broken for 20.09

Motivation for this change
using git hub file changes to make sure the diff looks good
Fixes #100111
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc issue https://github.com/NixOS/nixpkgs/issues/100111

cc @worldofpeace should this close ZHF. This seems like the "capstone" for stabilization

@jonringer Yes. People can still contribute fixes. Be sure to comment there as well.

@jonringer Yes. But people can still contribute fixes to unbreak things. Be sure to comment there as well.

Of course, but it would be weird to have the ZHF item open indefinitely. I'll just change the original post to mention that the backport commit may need to remove "broken = true;"

Of course, but it would be weird to have the ZHF item open indefinitely.

I was agreeing with "yes".

Not sure why i read that as a rebuttable
I guess I violently agree as well

all that remains are the linux modules:
linuxPackages_5_8.batman_adv
linuxPackages_5_8.chipsec
linuxPackages_5_8.exfat-nofuse
linuxPackages_5_8.mxu11x0
linuxPackages_5_8.ndiswrapper
linuxPackages_5_8.netatop
linuxPackages_5_8.nvidiabl
linuxPackages_5_8.openafs_1_8
linuxPackages_5_8.r8168
linuxPackages_5_8.rtl8814au
linuxPackages_5_8.rtl8821au
linuxPackages_5_8.rtl88xxau-aircrack
linuxPackages_5_8.rtlwifi_new
linuxPackages_5_9.anbox
linuxPackages_5_9.batman_adv
linuxPackages_5_9.chipsec
linuxPackages_5_9.dpdk
linuxPackages_5_9.ena
linuxPackages_5_9.evdi
linuxPackages_5_9.exfat-nofuse
linuxPackages_5_9.mxu11x0
linuxPackages_5_9.ndiswrapper
linuxPackages_5_9.netatop
linuxPackages_5_9.nvidiabl
linuxPackages_5_9.openafs_1_8
linuxPackages_5_9.r8168
linuxPackages_5_9.rtl8814au
linuxPackages_5_9.rtl8821au
linuxPackages_5_9.rtl88xxau-aircrack
linuxPackages_5_9.rtlwifi_new
linuxPackages_5_9.virtualbox
linuxPackages_5_9.virtualboxGuestAdditions
linuxPackages_5_9.zfs
linuxPackages_5_9.zfsStable
linuxPackages_hardened.mxu11x0
linuxPackages_hardened.ndiswrapper
linuxPackages_hardened.openafs_1_8
linuxPackages_hardened.r8168
linuxPackages_hardened.rtl8814au
linuxPackages_hardened.rtl8821au
linuxPackages_hardened.rtlwifi_new
linuxPackages_latest-libre.anbox
linuxPackages_latest-libre.batman_adv
linuxPackages_latest-libre.chipsec
linuxPackages_latest-libre.exfat-nofuse
linuxPackages_latest-libre.mxu11x0
linuxPackages_latest-libre.ndiswrapper
linuxPackages_latest-libre.netatop
linuxPackages_latest-libre.nvidiabl
linuxPackages_latest-libre.openafs_1_8
linuxPackages_latest-libre.r8168
linuxPackages_latest-libre.rtl8814au
linuxPackages_latest-libre.rtl8821au
linuxPackages_latest-libre.rtl88xxau-aircrack
linuxPackages_latest-libre.rtlwifi_new
linuxPackages_latest.anbox
linuxPackages_latest.batman_adv
linuxPackages_latest.chipsec
linuxPackages_latest.exfat-nofuse
linuxPackages_latest.mxu11x0
linuxPackages_latest.ndiswrapper
linuxPackages_latest.netatop
linuxPackages_latest.nvidiabl
linuxPackages_latest.openafs_1_8
linuxPackages_latest.r8168
linuxPackages_latest.rtl8814au
linuxPackages_latest.rtl8821au
linuxPackages_latest.rtl88xxau-aircrack
linuxPackages_latest.rtlwifi_new
linuxPackages_latest_hardened.anbox
linuxPackages_latest_hardened.batman_adv
linuxPackages_latest_hardened.chipsec
linuxPackages_latest_hardened.exfat-nofuse
linuxPackages_latest_hardened.mxu11x0
linuxPackages_latest_hardened.ndiswrapper
linuxPackages_latest_hardened.netatop
linuxPackages_latest_hardened.nvidiabl
linuxPackages_latest_hardened.openafs_1_8
linuxPackages_latest_hardened.r8168
linuxPackages_latest_hardened.rtl8814au
linuxPackages_latest_hardened.rtl8821au
linuxPackages_latest_hardened.rtl88xxau-aircrack
linuxPackages_latest_hardened.rtlwifi_new
linuxPackages_latest_xen_dom0.anbox
linuxPackages_latest_xen_dom0.batman_adv
linuxPackages_latest_xen_dom0.chipsec
linuxPackages_latest_xen_dom0.exfat-nofuse
linuxPackages_latest_xen_dom0.mxu11x0
linuxPackages_latest_xen_dom0.ndiswrapper
linuxPackages_latest_xen_dom0.netatop
linuxPackages_latest_xen_dom0.nvidiabl
linuxPackages_latest_xen_dom0.openafs_1_8
linuxPackages_latest_xen_dom0.r8168
linuxPackages_latest_xen_dom0.rtl8814au
linuxPackages_latest_xen_dom0.rtl8821au
linuxPackages_latest_xen_dom0.rtl88xxau-aircrack
linuxPackages_latest_xen_dom0.rtlwifi_new
linuxPackages_latest_xen_dom0_hardened.anbox
linuxPackages_latest_xen_dom0_hardened.batman_adv
linuxPackages_latest_xen_dom0_hardened.chipsec
linuxPackages_latest_xen_dom0_hardened.exfat-nofuse
linuxPackages_latest_xen_dom0_hardened.mxu11x0
linuxPackages_latest_xen_dom0_hardened.ndiswrapper
linuxPackages_latest_xen_dom0_hardened.netatop
linuxPackages_latest_xen_dom0_hardened.nvidiabl
linuxPackages_latest_xen_dom0_hardened.openafs_1_8
linuxPackages_latest_xen_dom0_hardened.r8168
linuxPackages_latest_xen_dom0_hardened.rtl8814au
linuxPackages_latest_xen_dom0_hardened.rtl8821au
linuxPackages_latest_xen_dom0_hardened.rtl88xxau-aircrack
linuxPackages_latest_xen_dom0_hardened.rtlwifi_new
linuxPackages_testing_bcachefs.ndiswrapper
linuxPackages_testing_bcachefs.rtl8814au
linuxPackages_testing_bcachefs.rtl8821au
linuxPackages_xen_dom0.mxu11x0
linuxPackages_xen_dom0.ndiswrapper
linuxPackages_xen_dom0.r8168
linuxPackages_xen_dom0.rtl8814au
linuxPackages_xen_dom0.rtl8821au
linuxPackages_xen_dom0.rtlwifi_new
linuxPackages_xen_dom0_hardened.mxu11x0
linuxPackages_xen_dom0_hardened.ndiswrapper
linuxPackages_xen_dom0_hardened.openafs_1_8
linuxPackages_xen_dom0_hardened.r8168
linuxPackages_xen_dom0_hardened.rtl8814au
linuxPackages_xen_dom0_hardened.rtl8821au
linuxPackages_xen_dom0_hardened.rtlwifi_new
linuxPackages_zen.anbox
linuxPackages_zen.batman_adv
linuxPackages_zen.chipsec
linuxPackages_zen.exfat-nofuse
linuxPackages_zen.mxu11x0
linuxPackages_zen.ndiswrapper
linuxPackages_zen.netatop
linuxPackages_zen.nvidiabl
linuxPackages_zen.openafs_1_8
linuxPackages_zen.r8168
linuxPackages_zen.rtl8814au
linuxPackages_zen.rtl8821au
linuxPackages_zen.rtl88xxau-aircrack
linuxPackages_zen.rtlwifi_new

I will probably tackle the linux  modules in a different PR, as we don't really have a good way (that I'm aware of) to determine the "flavor" of the kernel (e.g. libre, zen, xen, hardened, etc.)

That's an awful lot of modules.

I hope for people's hardware they can't rebuild switch because a module for the stable kernel doesn't build. Obviously something to handle after release.

https://github.com/NixOS/nixpkgs/pull/101736
2 packages marked as broken and skipped:
python37Packages.pythonmagick python38Packages.pythonmagick

4 packages built:
python27Packages.locustio python27Packages.msal-extensions python27Packages.python-axolotl python37Packages.sphinxcontrib-spelling

going to "forward port" some of the python fixes in a different PR

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/upgrade-20-03-to-20-09-failes-due-to-brocken-libguestfs-1-40-2/9721/2


Error install in vessel on macbook m1

Haven't gotten further than running this command as recommended in the IC punks repo'
gennaroschiano@Gennaros-MacBook-Pro ICPunks % ./scripts/vessel-install.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   620  100   620    0     0   2006      0 --:--:-- --:--:-- --:--:--  2000
/Users/gennaroschiano/bin/vessel: line 1: syntax error near unexpected token `<'
/Users/gennaroschiano/bin/vessel: line 1: `You are being <a href="https://github-releases.githubusercontent.com/248089583/a56f5800-c9ea-11eb-84e7-742446381094?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210909%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210909T063307Z&X-Amz-Expires=300&X-Amz-Signature=9f030b009d52b8f2bb88e0e691868b251bbbdc8da9f9938989d3fed751f4d607&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=248089583&response-content-disposition=attachment%3B%20filename%3Dvessel-macos&response-content-type=application%2Foctet-stream">redirected.'

Here is the script that is included to install vessel
#!/bin/sh
mkdir -p $BINDIR
BIN=$BINDIR/vessel
OS_FILENAME=linux64
if [[ "$OSTYPE" == "linux-gnu"* ]]; then
  OS_FILENAME=linux64
elif [[ "$OSTYPE" == "darwin"* ]]; then
  OS_FILENAME=macos
elif [[ "$OSTYPE" == "win32" ]]; then
  OS_FILENAME=windows64.exe
fi

VESSEL_VERSION=v0.6.0
curl -o $BIN https://github.com/dfinity/vessel/releases/download/$VESSEL_VERSION/vessel-$OS_FILENAME && chmod +x $BIN && $BIN help```

It looks like your curl failed to follow a redirect there. Maybe try updating curl?
Otherwise you can download a release yourself from here: https://github.com/dfinity/vessel/releases and put it whereever the script would.
Last option would be to compile a binary yourself using rust.

Closing since this appears to be caused by an outdated URL in the external setup script. If needed, I'd be happy to reopen this issue and help debug on the latest version of Vessel (0.6.5).


Issues with sub options

I'm having an issue with the parser not figuring out my sub-options.
Here's the code in Main:
var invokedVerb = "";
var invokedVerbInstance = new object();

var options = new Options();
if (!CommandLine.Parser.Default.ParseArguments(args, options,
    (verb, subOptions) =>
    {
        // if parsing succeeds the verb name and correct instance
        // will be passed to onVerbCommand delegate (string,object)
        invokedVerb = verb;
        if (!string.IsNullOrEmpty(invokedVerb))
        invokedVerbInstance = subOptions;
    }))
{
    Environment.Exit(CommandLine.Parser.DefaultExitCodeFail);
}

This is pretty much right from the wiki.
My options are defined as this:
class Options
{
    public Options()
    {
        CpVerb = new CPSubOptions { };
    }

    [VerbOption("cp", HelpText = "Interact with cp.")]
    public CPSubOptions CpVerb { get; set; }

    [HelpVerbOption]
    public string GetUsage(string verb)
    {
        return HelpText.AutoBuild(this, verb);
    }
}

class CPSubOptions
{
    [Option('n', "name", HelpText = "Get details name.")]
    public string Name { get; set; }
}

When I run with cp as the args, it works and the parser determines that CPSubOptions is the subOptions and invokedVerbInstance is set appropriately.
However, when I run with cp --name blah or cp -n blah, the subOptions is null, so it's not parsed properly.
Any help?

What version are you using? Based on the stable branch, your sample code works perfectly (for me). Based on Master, it fails to compile since the library has gone through some major changes for 2.0.

:paperclip: Please read: #250. Thanks for collaboration and patience! :sweat_smile:
Giacomo
P.S.: valid only for me, if a main contrib. is available he's obviously free to support devs/users of the project.

@wadewegner did you figure it out? I also tried your code and as @nemec I get the expected result; subOptions is not null and Name has a value.

Same issue here with an almost identical class configuration. subOptions passed to callback is null, although options.subOption is valid with correct values (options.CpVerb in your case).

I'm seeing this as well with latest version from nuget.

@Jamby93 @brandorf latest stable or prerelease? I just tested again with 1.9.71 from NuGet, copy and pasting the above, and it works perfectly. VS 2015, .Net 4.5.2 in case you're running something different.
The exact code: https://gist.github.com/nemec/bc9d78e47d7a7d8a72a9711488b3bfef


Added media optimizer overview to systeminfo

Description

Questions
Answers

Why?
Its needed to check the optimizers on the web enviroment

BC breaks?
no

Tests exists & pass?
yes

Related tickets?

How to test?
Open the module systeminfo and go to tab "Media Optimizer"

Requirements met?
Yes

Screenshot :)

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-18653.
Please use this issue to track the state of your pull request.

Thanks @shyim. The benefit of your change is not relevant for the whole product but only for your personal intent.
Since you have to use the console to optimize your images, we want to show the info only there to keep it consistent.

And whats about images which are uploaded in backend using media manager? They won't be optimized automatically and currently is it not possible to check if any optimizer is available in backend

any answer? :D

I've to agree to shyim.
There is no possibility to check for runnable optimizers in backend. Just to make some transparent informations for default shop-user.
All functions should be accessible from backend, if they could show informations about the environment in an easy way.

@shopwareBot
We'd like to push this thread ;-)

@shopwareBot Ping.....

@shopwareBot ping 🙄

@shopwareBot ping

Please don't ping the Shopware Bot.
We will come back to this pull request if we plan to implement this feature.
Otherwise create a feature request in the issue tracker.


Ask to reload codespace on resume

I just resumed a codespace and I get:

This is highly unexpected. I'm guessing what's happening is that setting sync brings in a value that requires us to reload the window.

Yeah I see how ugly it is, but I am not sure how settings sync can handle this unless it knows the setting that is getting changed required reload or restart. It requires to wire in all this info and show a notification & badge (like conflict) so that user can accept the change and reload.


Investigate FIPS s2n_ecdsa_test.c failure

Problem:
The OpenSSL 1.0.2 FIPS Travis Builds started failing recently: https://travis-ci.org/awslabs/s2n/jobs/412423148#L9654
*** Error in `./s2n_ecdsa_test': double free or corruption (!prev): 0x0000000002029a70 ***
Running FIPS test s2n_ecdsa_test.c                                   ... Aborted (core dumped)
make[2]: *** [s2n_ecdsa_test] Error 134
make[2]: *** Waiting for unfinished jobs....

Proposed Solution:
Investigate why the tests are failing, and fix the issue.

I tried to reproduce this failure locally, but without success. I don't have GCC 4.8.4, but I've tried with 4.4.6, 5.4.0 and 9, and using the build script from .travis/install_openssl_1_0_2_fips.sh.

This seems to be a bug introduced in OpenSSL 1.0.2p, being tracked in https://github.com/openssl/openssl/issues/7127 and the fix is proposed in https://github.com/openssl/openssl/pull/7135.
I found via local testing that I see the same error message when running our s2n_ecdsa_test:
OpenSSL failed with RC: 269078544; OpenSSL Error String: error:1009D010:lib(16):func(157):reason(16)
Running FIPS test s2n_ecdsa_test.c                                   ... FAILED test 19
!(((s2n_asn1der_to_private_key(&unmatched_priv_key, &b))) == (-1)) is not true  (s2n_ecdsa_test.c line 110)
Error Message: 'error decoding private key'
 Debug String: 'Error encountered in s2n_pkey.c line 134'
make[2]: *** [s2n_ecdsa_test] Error 1


resolve #3834

Description

Migrated to new API version
added Recent Tags picker to Create Draft command (resolve issue #3834)

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @FlohGro-dev 👋
Could you look into the merge conflicts here? 😊

Hi @pernielsentikaer
Yes of course - I saw the conflicts and was annoyed 😂 I will take a look and update the PR.

Hi @pernielsentikaer I forgot to sync raycast/main to my fork before making the changes which caused the troubles.
I forced this and reopened a pull request #5912 which solved the merge conflicts.
I don't know why it shows so many commits since the changes are not that big - I bet this is a layer 8 problem my late night brain does not understand at the moment 😆
sorry for the confusion.


About the entire training process

I'm not clear about the entire training process. Could you tell me if the self.model used for testing is also updated during finetuning, or the finetuning stage is just used to train multiple teachers?

After I read the code, the entire training process is as follows:
(1)task 1: use nca or CE loss to train teacher 1 (used for evaluation) -> then use nca or CE loss to update teacher 1 (used for evaluation) and train teacher 2, 3 etc. in finetune stage.
(2)task t > 1: use the pre-model (comprising multiple branches used as diverse teachers ) to distill and learn new classes to train teacher 1 (used for evaluation) -> then  use nca or CE loss to train teacher 2, 3 etc. and  use nca or CE loss combined distillation loss using  pre-model to update teacher 1 (used for evaluation) in finetune stage.
Is it right? the model used for evaluation is the teacher 1 before finetune or finetuned teacher 1?


Feature/roles

[x] porting the roles endpoint (all but get_metrics), plus a few supporting types
[ ] the python version has no direct tests for this endpoint

Minor comments. Otherwise, 👍 LGTM