Propose creating a Wasm extension repo

Propose creating a wasm extension repo under Istio org, it has several roles:

Hosts production extensions, including extensions migrated from istio/proxy repo (prometheus stats, metadata exchange, attribute generation, etc) and extensions to get parity with Mixer functionality. This follows the direction of using upstream envoy directly and removing istio/proxy.
Hosts easy-to-consume example extensions which demonstrate essential Wasm ABI (http/grpc call out, timer, stats, log etc) as well as major use cases (policy, telemetry, and request mutation).
Provides common utils and test framework that developer could import when writing out of tree Istio Wasm extensions. Provides doc, tips and best practice of developing, managing and deploying wasm extension.

Action items to reach the goal:

[x] Clean up and untangle test framework in istio/proxy repo to make it importable from another repo.
[x] Organize common functions such as node info and handy stream info access function into a base extension class, and use that extension class for the existing extensions in istio/proxy.
[x] Create the repo, add example extensions and Mixer adapter equivalent extensions into it by referencing the framework and utils created in the first two tasks.

Items to move things off istio/proxy: 02/17/2021 editting: proxy migration is unlikely going to happen.

[ ] Move go test framework and the common extension class into the new repo.
[ ] After Wasm ABI/runtime is stabilized with upstreaming, and performance is improved, migrate existing production module (stats, metadata exchange, and stackdriver modules) from istio/proxy to the new repo and migrate from compiled in/wasm dual modes to wasm only.
[ ] Remove istio/proxy repo.

Estimated time line is creating the new repo with examples extensions by 1.7, move things off istio proxy by 1.8, or further if we cannot reach performance requirement.
@mandarjog @PiotrSikora @duderino @jplevyak @douglas-reid @kyessenov @gargnupur Feedback is really appreciated.

It's probably easier to fork istio/proxy and delete a bunch of stuff.
We should also make sure the footprint is small in shared routines. E.g. do not import protobuf by default.

If fork, we need to nuke LOT of things except the test framework and some common utils? I don't think we want to have duplicated code of any extensions in two repos right? Also do we expect the new repo to still be in dual mode (Wasm + compiled in)? I would think of it as a Wasm only repo,  otherwise we will still need to maintain upstream envoy dependencies. If it is Wasm only, I don't think it makes sense to fork?

@bianpengyuan this differs from the previous doc in which we wanted a repo in the istio-ecosystem org.
I do see the need for 1st party istio extensions to be hosted in the istio org, but that is just the proxy repo today.
Should prod extensions and the common utils be in the same repo? Would it be better that that to be a separate repo?

Additionally, we need to decide what to do with the supporting infrastructure. Build system, testing framework(s) may belong outside of istio in proxy-wasm. There is an extra pain with the multi-repo set-up.

The original thought was istio-ecosystem, but I think it will need to be released together with Istio, so better just put it under istio org. As @kyessenov said, it is more efficient for us to just put common utils in the same repo. 3rd party developer experience won't be different whether plugins and utils are in the same repo or different ones. So either we just evolve in istio/proxy repo and (probably) rename to something Wasm when it is ready in the future, or creating a new wasm-extension repos to host common utils and various extensions and gradually migrate prod extensions from istio-proxy to the new repo. Latter seems to be cleaner to me.
Re supporting infrastructure, build system definitely belongs to the proxy-wasm. For other parts I'd rather just develop in Istio context and upstream if turns out to be generally useful and motivated.

What about non-core istio extensions?
Do we want to accept it in istio org? I don’t think so.
Installing an extension from istio repo should mean that it is reviewed and maintained by our team.
I agree we need a repo inside istio, but we also need a rep outside istio.
Timing

When do we need to do this ? We can make the switch at the beginning of 1.7
As long and we are shipping istio-proxy with null sandbox extensions, that repo should stay.
If the test fw moves to the new repo, will istio-proxy take that as a dependency?
Since examples are ready to go do they belong inside istio org or in the eco system?

Ok, make sense to me about the separation of examples from core extensions. Common and frameworks should always stay with core, so that they could be released together. Ecosystem will only have examples which takes istio/proxy as a dependency for now.
Timing wise, by 1.7 let's make common & frameworks ready in istio/proxy and add example wasm modules into ecosystem, which takes a dependency on istio/proxy. By 1.8 or later release after ABI stabilization / perf improvement, we could nuke and migration from istio/proxy to some new repo. wdyt?

Taking a dependency on istio/proxy SGTM. Later we can migrate to proxy-wasm or something new. I would generally prefer less big bang.

Done by https://github.com/istio-ecosystem/wasm-extensions


ChatDev can't update code of existing 'WareHouse' Projects

correct and not many work one shot either, hand em over to AutoGPT to fix them up or mentat or aider

While handing the project over to aider & co seem to be a good Idea, i thought maybe will ChatDev implement it's own logic on updating the codebase of it's own projects at user prompt. I think this could be a major feature

I would agree and they have hinted at it.

The feature is necessary if we are to really run a profitable software company with this.

addapting the Aider's functionality into ChatDev will do the thing maybe ;)

What would be needed to achive a functionality like this?

What would be needed to achive a functionality like this?

It probably needs the human interaction feature to be more developed. I just tested it and It didn't really work. But that's clearly the direction they want to take it. Basically the program should run until the user asks it to shut down and should wait for user feedback on the product after a certain cycle.

The closest they have to this capability is their "human interaction" feature, which allows the user to act as a reviewer and add a one line alteration request upon review.  After submission of the change request, ChatDev will loop back into the development process. There is a max of 5 iterations allowed.  I agree though, it would be very handy if a more capability was provided for allowing editing. I've created three apps so far, and all of them have required a very large amount of modifications. Any requirement that wasn't explicitly clarified in the design idea prompt is hallucinated to allow the process to continue and for the agents to complete the objective.  It would be great if the agent team asked clarifying questions during the design process. A one line prompt is simply not sufficient.

I agree with all of the above. Being able to interact with the project directly as it's being developed would be super nice.
Or even to come in after a couple of iterations and provide feedback, have the AI generate a list of questions to ask the user that it presents to us after the iterations.

I am working on an IDE concept that incorporates AI agents as part of the software development experience. Sage IDE , will incorporate AI agents that work interactively with the software developer to produce a project from start to finish.  The project is open to comments, suggestions, and questions: https://github.com/Monotoba/SageIDE/


merge package from arlac77/npm-package-template

.travis.yml

chore(travis): remove node versions 12.2.0
chore(travis): add node versions -10,-11,-12,12.3.1

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Auto-normalization and CLIP embeddings

I have an x-clip model trained on normalized image data in the range [-1, 1] with good loss performance on a custom dataset.
I've tried to re-use the same custom dataset/dataloader that provides normalized images with the models in this repo but have run into issues with the auto-normalization.
If I leave the images in the range [-1, 1] then the forward pass in the Decoder auto generates the image embeddings from the CLIP adapter and passes the images as-is, which works. However, the p_losses pass then performs normalize_neg_one_to_one which shifts the range to [-3, 1].
If I leave the images in the range [0, 1] then the forward pass in the Decoder passes the wrong image data into the CLIP adapter while the p_losses pass is correct with [-1, 1].
As a workaround I can compute image_embed/text_embed manually and pass them into the Decoder, but this takes up extra memory or performance from having to discard the normalized results after and recompute them.
I think the control to disable auto-normalization would be beneficial here, but maybe this is more of an error training with normalized image data on CLIP itself.

ahh, i know how to fix this, but all locked up this week. i'll get to it in the event i do not accept work in the city

@marunine threw in a quick fix for you! https://github.com/lucidrains/DALLE2-pytorch/commit/db0642c4cdcaf4639136c1978c8124235d75a52e#diff-038ecede954c29266888cb88e37cc06f61ba2433f8b5142c7b2b2cefde5ed0edR1701 just set this to False

i realized another option is to allow one to pass in a normalization_fn into the XClipAdapter, but let's go with this for now

Thanks for the quick response!
I think the only issue with a normalization_fn with the XClipAdapter is that it implies that the image data would need to be normalized. I'm not sure if the model is more numerically stable or trains better if it's in [-1, 1] vs [0, 1], but anecdotally it worked for me.

@marunine great! if you get anything working with x-clip as the base, do send me an email and let me know 😄

I have an x-clip model trained on normalized image data in the range [-1, 1] with good loss performance on a custom dataset.

Currently making a run at a custom dataset using x-clip. Curious to know what params (learning rate, etc.) did you use?


store build artifacts on release

as a <> i want build artifacts added to a release, so PyPI is not my single point of source.
use https://github.com/actions/upload-release-asset
to add the wheel(build/*.whl) and source (build/*.tar.gz) artifacts to the release

how to do it: see an example here: https://github.com/k4cg/nichtparasoup/blob/3.0-dev/.github/workflows/release.yaml

build artifacts to store

dist release
source release

@jkowalleck - aren't these already added to GitHub Releases: https://github.com/CycloneDX/cyclonedx-python-lib/releases?

dont see dist or source releases.
what is added today is:

docker image SBOM - by github-workflow
snapshot of the repository - done by github

what we lack today is:

the dist artifacts that are uploaded to PyPI (and can finally be found here: https://pypi.org/project/cyclonedx-python-lib/#files)

source dist file
wheel dist file

Not sure I agree - in our deploy workflow, we publish to GitHub Releases:

??

you are totally right, @madpah
work is done already, ticket was invalid. will close it.


Feature/ted 661

Codecov Report

Merging #239 (5faaeec) into main (51b9cf8) will decrease coverage by 0.74%.
The diff coverage is 92.59%.

@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
- Coverage   98.70%   97.95%   -0.75%
==========================================
  Files         115      108       -7
  Lines        5030     4946      -84
==========================================
- Hits         4965     4845     -120
- Misses         65      101      +36

Impacted Files
Coverage Δ

...ices/conceptual_mapping_generate_sparql_queries.py
100.00% <ø> (ø)

.../notice_transformer/services/notice_transformer.py
100.00% <ø> (ø)

...ed_sws/data_sampler/services/notice_xml_indexer.py
70.43% <8.10%> (-29.57%)
:arrow_down:

ted_sws/__init__.py
92.91% <100.00%> (+0.23%)
:arrow_up:

ted_sws/core/adapters/cmd_runner.py
100.00% <100.00%> (ø)

ted_sws/core/model/manifestation.py
100.00% <100.00%> (ø)

ted_sws/core/model/supra_notice.py
100.00% <100.00%> (ø)

ted_sws/core/model/transform.py
100.00% <100.00%> (ø)

ted_sws/data_manager/adapters/notice_repository.py
96.96% <100.00%> (+0.01%)
:arrow_up:

ted_sws/data_manager/adapters/sparql_endpoint.py
96.55% <100.00%> (-2.26%)
:arrow_down:

... and 33 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Server Sent Events

[x] Process[ByteVector, ServerSentEvent]
[x] Process[ServerSentEvent, ByteVector]
[x] property check for round trip
[x] Entity encoder for text/event-stream
[ ] Entity decoder for text/event-stream
[x] Modeled headers
[ ] special method on client?

We don't currently a decoder to a Process.  We can decode the entity to a Task[Process[Task,_]], but, eh?

I am really interested in receiving ServerSentEvent on the client side.
My use case is to connect to an SSE endpoint an gather all events for a given duration.
What is missing to achieve that?
I am willing to offer help to push this forward 😃

First off, since the above comment is old, Process is Stream and Task[Process[Task, _]] is F[Stream[F, _]].  But there still exists no EntityDecoder to a Stream.  And maybe there doesn't need to be: we can probably build on response.body.through(ServerSentEvent.decoder) to get our Stream[F, ServerSentEvent].  At a simple level, that might just work.
At a more complete level, it's worth looking at the Processing model.  Some servers might be strict in checking things like the Accept header.  Maybe a def streamServerSentEvents(uri: Uri, lastEventId: Option[LastEventId]): Stream[F, ServerSentEvent] method on the client that set all those headers and checked status codes appropriately would be a good idea?

I'd like to use comment lines to provide a keep-alive notification and keep the browser from shutting down existing streams.
Per the spec lines starting with : are 'comments' and are ignored by the client, but should serve to keep the socket open.
Are folks open to adding functionality for sending comments to the implementation? My alternative right now is to send empty data, which is just 5 bytes too many. ;-)

Setting aside the comments issue we overlooked (:disappointed:), I think the client would be neat.  It's probably too esoteric for the main Client interface, but can't go on core.  A new SseClient that wraps a Client would be a good home for implementing this spec.


Collection created on server even when a document has remote connection.

Related to #39, I now run on<EMAIL_ADDRESS>and when inspecting the local mongo database, I still see collections created on the server, even though the connection for that Document goes to a different server.
It's not a problem since queries seem to go to the other server, just thought I'd mention that you get a lingering (unused) empty collection.

Hm, on the second try now, the extra collection was not created. Maybe I had it in the DB from before. I'll reopen if I can confirm the problem.

Thanks.

I added a test. They are not created.

:+1: Great, thanks! I'll soon try to make server-server connections to test everything out.


Update README.md

LGTM. Will there be a separate update for version_history.md before the official release?


Build package updates

Some build/package updates

@hellkite500 is this PR still being worked on or is it ready for review/merge?

@shorvath-noaa It should be good as is. Might need to do some testing based on @aaraney s comment and make some adjustments, but that can be done separately.

@hellkite500 I got this to compile ok, but when I run t-route with RFC's on it still fails, so I'm not sure this fixes Issue 620. This is the error I get:
At line 23 of file bind_rfc.f90
Fortran runtime error: Attempt to DEALLOCATE unallocated 'rfc_ptr'
At line 23 of file bind_rfc.f90
Fortran runtime error: Attempt to DEALLOCATE unallocated 'rfc_ptr'
Traceback (most recent call last):
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/sean.horvath/projects/t-route/src/troute-nwm/src/nwm_routing/__main__.py", line 2028, in <module>
    main_v04(v_args[1])
  File "/home/sean.horvath/projects/t-route/src/troute-nwm/src/nwm_routing/__main__.py", line 161, in main_v04
    run_results = nwm_route(
  File "/home/sean.horvath/projects/t-route/src/troute-nwm/src/nwm_routing/__main__.py", line 1074, in nwm_route
    results = compute_nhd_routing_v02(
  File "/home/sean.horvath/projects/t-route/src/troute-routing/troute/routing/compute.py", line 621, in compute_nhd_routing_v02
    results_subn[order] = parallel(jobs)
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/site-packages/joblib/parallel.py", line 1061, in __call__
    self.retrieve()
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/site-packages/joblib/parallel.py", line 938, in retrieve
    self._output.extend(job.get(timeout=self.timeout))
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/site-packages/joblib/_parallel_backends.py", line 542, in wrap_future_result
    return future.result(timeout=timeout)
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/concurrent/futures/_base.py", line 446, in result
    return self.__get_result()
  File "/home/sean.horvath/miniconda-template/miniconda3/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
    raise self._exception
joblib.externals.loky.process_executor.TerminatedWorkerError: A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker.

The exit codes of the workers are {EXIT(2)}

@shorvath-noaa This fixes the build/packaging -- what you are seeing is a runtime error that is a separate issue, I think.


step by step instructions for a simple checkout page

Hello, are you planning to include some more detailed instructions on how to make a checkout form using this plugin? Thank you very much.

As stated in https://github.com/flaviocopes/grav-plugin-shoppingcart-paypal/blob/develop/README.md, the plugin is an addon for the Shopping Cart plugin.
Docs are listed in http://gravcart.com/docs

I was hoping for some more detail in the UI end since you say "This tutorial will guide you until you'll get a nice shop like this:" [Geek Toys] but that's never done. Thanks

Install the Shopping Cart plugin
Make sure your site has a pages structure following this example http://gravcart.com/docs/pages-structure
Open your browser, and navigate to /shop

Using Antimatter will ensure the shop has some nice default styling, but any theme would work.


ERROR: MethodError: no method matching run

I cannot initiate FlowAtlas. Below is the error.
julia> using FlowAtlas; FlowAtlas.run("08-Aug-2024.wsp"; files="/.fcs")
ERROR: MethodError: no method matching run(::String; files::String)
The function run exists, but no method is defined for this combination of argument types.
Closest candidates are:
run(::String, ::Any; port, url, cols, channelMap, drop, nlevels, channelRange, channelScheme, labelScheme, perplexity, maxIter) got unsupported keyword argument "files"
@ FlowAtlas ~/.julia/packages/FlowAtlas/HaV3Q/src/FlowAtlas.jl:55
Stacktrace:
[1] top-level scope
@ REPL[19]:1

Hi there! Thank you for using FlowAtlas! Happy to help with your issue. I am currently travelling and will attempt to get back to you on this later this week 😄

can you provide me a few more details to help to track down the bug? Can you run the following in the Julia env where the error is being produced?
versioninfo()
using Pkg; Pkg.status()

julia> versioninfo()
Julia Version 1.11.1
Commit 8f5b7ca12ad (2024-10-16 10:53 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: macOS (arm64-apple-darwin22.4.0)
CPU: 12 × Apple M2 Max
WORD_SIZE: 64
LLVM: libLLVM-16.0.6 (ORCJIT, apple-m2)
Threads: 1 default, 0 interactive, 1 GC (on 8 virtual cores)
julia> using Pkg; Pkg.status()
Status ~/.julia/environments/v1.11/Project.toml
⌃ [ef7debb3] FlowAtlas v0.1.3
Info Packages marked with ⌃ have new versions available and may be upgradable.

the version of FlowAtlas is quite old. Would it be possible for you to upgrade to the latest version (v0.1.14) using
using Pkg; Pkg.update()

julia> using Pkg; Pkg.update()
Updating registry at ~/.julia/registries/General.toml
No Changes to ~/.julia/environments/v1.11/Project.toml
No Changes to ~/.julia/environments/v1.11/Manifest.toml
julia> using Pkg; Pkg.status()
Status ~/.julia/environments/v1.11/Project.toml
⌃ [ef7debb3] FlowAtlas v0.1.3
Info Packages marked with ⌃ have new versions available and may be upgradable.

Interesting! It appears the latest release of Julia (1.11.1) is preventing FlowAtlas from being upgraded to its latest version. An immediate fix would be to use the LTS version of Julia (1.10).
This can be done from the command line if you used juliaup to install Julia. At the same time I would recommend using 1.10 by default as a lot of things start breaking if you use the latest version of things :)
juliaup add 1.10
juliaup default 1.10

In the meantime I will look into why this is happening for Julia 1.11

Thank you for being so supportive and help with this

Okay as I thought something is up with version constrains..
Unsatisfiable requirements detected for package StatsFuns [4c63d2b9]:
 StatsFuns [4c63d2b9] log:
 ├─possible versions are: 0.7.0 - 1.3.2 or uninstalled
 ├─restricted by compatibility requirements with Distributions [31c24e10] to versions: 0.8.0 - 1.3.2
 │ └─Distributions [31c24e10] log:
 │   ├─possible versions are: 0.16.0 - 0.25.112 or uninstalled
 │   ├─restricted by compatibility requirements with StaticArrays [90137ffa] to versions: [0.16.0 - 0.23.11, 0.24.5 - 0.25.112] or uninstalled
 │   │ └─StaticArrays [90137ffa] log:
 │   │   ├─possible versions are: 0.8.0 - 1.9.8 or uninstalled
 │   │   ├─restricted to versions 1 by FlowAtlas [ef7debb3], leaving only versions: 1.0.0 - 1.9.8
 │   │   │ └─FlowAtlas [ef7debb3] log:
 │   │   │   ├─possible versions are: 0.1.14 or uninstalled
 │   │   │   └─FlowAtlas [ef7debb3] is fixed to version 0.1.14
 │   │   └─restricted by julia compatibility requirements to versions: [0.12.0 - 0.12.6, 1.5.0 - 1.9.8] or uninstalled, leaving only versions: 1.5.0 - 1.9.8
 │   ├─restricted by compatibility requirements with StatsBase [2913bbd2] to versions: 0.23.2 - 0.25.112 or uninstalled, leaving only versions: [0.23.2 - 0.23.11, 0.24.5 - 0.25.112] or uninstalled
 │   │ └─StatsBase [2913bbd2] log:
 │   │   ├─possible versions are: 0.24.0 - 0.34.3 or uninstalled
 │   │   ├─restricted to versions 0.33 by FlowAtlas [ef7debb3], leaving only versions: 0.33.0 - 0.33.21
 │   │   │ └─FlowAtlas [ef7debb3] log: see above
 │   │   └─restricted by compatibility requirements with SortingAlgorithms [a2af1166] to versions: 0.33.7 - 0.34.3 or uninstalled, leaving only versions: 0.33.7 - 0.33.21
 │   │     └─SortingAlgorithms [a2af1166] log:
 │   │       ├─possible versions are: 0.3.0 - 1.2.1 or uninstalled
 │   │       ├─restricted by julia compatibility requirements to versions: 1.1.0 - 1.2.1 or uninstalled
 │   ├─restricted by compatibility requirements with GigaSOM [a03a9c34] to versions: 0.21.1 - 0.25.112, leaving only versions: [0.23.2 - 0.23.11, 0.24.5 - 0.25.112]
 │   │ └─GigaSOM [a03a9c34] log:
 │   │   ├─possible versions are: 0.0.4 - 0.7.0 or uninstalled
 │   │   └─restricted to versions 0.7 by FlowAtlas [ef7debb3], leaving only versions: 0.7.0
 │   │     └─FlowAtlas [ef7debb3] log: see above
 │   └─restricted by compatibility requirements with FillArrays [1a297f60] to versions: [0.16.0 - 0.21.9, 0.25.49 - 0.25.112] or uninstalled, leaving only versions: 0.25.49 - 0.25.112
 │     └─FillArrays [1a297f60] log:
 │       ├─possible versions are: 0.2.0 - 1.13.0 or uninstalled
 │       ├─restricted by julia compatibility requirements to versions: 0.13.8 - 1.13.0 or uninstalled
 │       └─restricted by compatibility requirements with Distributions [31c24e10] to versions: 0.8.0 - 1.13.0, leaving only versions: 0.13.8 - 1.13.0
 │         └─Distributions [31c24e10] log: see above
 ├─restricted by compatibility requirements with Rmath [79098fc4] to versions: 0.9.2 - 1.3.2 or uninstalled, leaving only versions: 0.9.2 - 1.3.2
 │ └─Rmath [79098fc4] log:
 │   ├─possible versions are: 0.5.0 - 0.8.0 or uninstalled
 │   ├─restricted by compatibility requirements with BinaryProvider [b99e7846] to versions: 0.6.1 - 0.8.0 or uninstalled
 │   │ └─BinaryProvider [b99e7846] log:
 │   │   ├─possible versions are: 0.4.0 - 0.5.10 or uninstalled
 │   │   └─restricted by julia compatibility requirements to versions: uninstalled
 ├─restricted by compatibility requirements with Reexport [189a3867] to versions: 0.7.0 - 0.9.8 or uninstalled, leaving only versions: 0.9.2 - 0.9.8
 │ └─Reexport [189a3867] log:
 │   ├─possible versions are: 0.2.0 - 1.2.2 or uninstalled
 │   └─restricted by compatibility requirements with DataDeps [124859b0] to versions: 0.2.0
 │     └─DataDeps [124859b0] log:
 │       ├─possible versions are: 0.4.3 - 0.7.13 or uninstalled
 │       ├─restricted by compatibility requirements with HTTP [cd3eb016] to versions: 0.7.4 - 0.7.8 or uninstalled
 │       │ └─HTTP [cd3eb016] log:
 │       │   ├─possible versions are: 0.6.10 - 1.10.9 or uninstalled
 │       │   └─restricted to versions 0.9 by FlowAtlas [ef7debb3], leaving only versions: 0.9.0 - 0.9.17
 │       │     └─FlowAtlas [ef7debb3] log: see above
 │       ├─restricted by compatibility requirements with Impute [f7bf1975] to versions: 0.7.0 - 0.7.13, leaving only versions: 0.7.4 - 0.7.8
 │       │ └─Impute [f7bf1975] log:
 │       │   ├─possible versions are: 0.1.0 - 0.6.12 or uninstalled
 │       │   ├─restricted to versions 0.6 by FlowAtlas [ef7debb3], leaving only versions: 0.6.0 - 0.6.12
 │       │   │ └─FlowAtlas [ef7debb3] log: see above
 │       │   ├─restricted by compatibility requirements with StatsBase [2913bbd2] to versions: [0.1.0 - 0.2.0, 0.6.1 - 0.6.12] or uninstalled, leaving only versions: 0.6.1 - 0.6.12
 │       │   │ └─StatsBase [2913bbd2] log: see above
 │       │   └─restricted by compatibility requirements with CSV [336ed68f] to versions: [0.1.0 - 0.5.1, 0.6.2 - 0.6.12] or uninstalled, leaving only versions: 0.6.2 - 0.6.12
 │       │     └─CSV [336ed68f] log:
 │       │       ├─possible versions are: 0.3.0 - 0.10.15 or uninstalled
 │       │       ├─restricted by compatibility requirements with GigaSOM [a03a9c34] to versions: [0.5.12 - 0.8.5, 0.10.0 - 0.10.15]
 │       │       │ └─GigaSOM [a03a9c34] log: see above
 │       │       ├─restricted by compatibility requirements with Impute [f7bf1975] to versions: 0.6.0 - 0.10.15, leaving only versions: [0.6.0 - 0.8.5, 0.10.0 - 0.10.15]
 │       │       │ └─Impute [f7bf1975] log: see above
 │       │       ├─restricted by compatibility requirements with DataFrames [a93c6f00] to versions: 0.8.0 - 0.10.15 or uninstalled, leaving only versions: [0.8.0 - 0.8.5, 0.10.0 - 0.10.15]
 │       │       │ └─DataFrames [a93c6f00] log:
 │       │       │   ├─possible versions are: 0.11.7 - 1.7.0 or uninstalled
 │       │       │   ├─restricted to versions 1 by FlowAtlas [ef7debb3], leaving only versions: 1.0.0 - 1.7.0
 │       │       │   │ └─FlowAtlas [ef7debb3] log: see above
 │       │       │   └─restricted by compatibility requirements with Reexport [189a3867] to versions: 0.11.7 - 1.5.0 or uninstalled, leaving only versions: 1.0.0 - 1.5.0
 │       │       │     └─Reexport [189a3867] log: see above
 │       │       └─restricted by compatibility requirements with PooledArrays [2dfb63ee] to versions: [0.3.0 - 0.4.3, 0.8.3 - 0.10.15] or uninstalled, leaving only versions: [0.8.3 - 0.8.5, 0.10.0 - 0.10.15]
 │       │         └─PooledArrays [2dfb63ee] log:
 │       │           ├─possible versions are: 0.3.0 - 1.4.3 or uninstalled
 │       │           └─restricted by compatibility requirements with DataFrames [a93c6f00] to versions: 1.2.1 - 1.4.3
 │       │             └─DataFrames [a93c6f00] log: see above
 │       └─restricted by compatibility requirements with BinaryProvider [b99e7846] to versions: [0.4.3 - 0.7.4, 0.7.10 - 0.7.13] or uninstalled, leaving only versions: 0.7.4
 │         └─BinaryProvider [b99e7846] log: see above
 └─restricted by compatibility requirements with Distributions [31c24e10] to versions: 0.9.15 - 1.3.2 — no versions left
   └─Distributions [31c24e10] log: see above

... this looks like a mess to solve... did you manage to get it working with 1.10?

It looks like I'm finally going to have to upgrade JSServe.jl to Bonito.jl to fix this
https://github.com/gszep/FlowAtlas.jl/issues/34

You suggesting of using 1.10 fixed the original issue. Now I am battling it not "finding the metadata". I do not know if this is related to the switch for 1.10.

Please do open a separate issue including a tiny bit of sample data which demonstrates the the new issue.
I will gladly try to help


typing fixes for mypy 0.931 and numpy 1.22

typing fixes for mypy 0.931 and numpy 1.22. Also tested with numpy 1.20 which probably many still have installed.

Brilliant @mathause !

Should be uncontroversial - I am merging.


AJAX

Although I'd like to get the basic functionality working first, once that's done we should probably convert some sections/forms to work with AJAX.

I'd make the whole site accesiable through ajax like this: if ajax is set as $_GET or $_POST parameter, omit the main template and just print the content to the page, that makes is very simple to preform everything via ajax.

Actually, the reason it hasn't been implemented yet is that I currently (and for the foreseeable future) don't have a lot of time. Getting basic functionality working is a priority right now. While I'd still like to have it implemented before the beta phase, its extent will probably be limited to forms and tables.

You could simply do this, for example. This results in that http://localhost/DraiWiki/index.php/article/Sucis_deos_iterum_umbras_niveae?ajax neatly only shows me the content of the article :)
You might want to pack $_REQUEST in some wrapper class of kinds.
// Main.class.php around line 164
if(!isset($_REQUEST['ajax']))
	$template->showHeader();

$this->_currentApp->show();

if(!isset($_REQUEST['ajax']))
	$template->showFooter();

Yes, but that would still require time to implement, and again, basic functionality should be implemented first. :P

Okay, since writing custom table sorting and pagination methods would be more trouble than it's worth, we're now using a library that takes care of that (yep, I'm lazy :P). The reason I mention this is that we might as well use AJAX right away, since it would be a huge drain on server resources if 1,000,000+ members (okay, maybe this is a little optimistic) had to be loaded each time someone decided to visit the user management page.
So, in short: Alpha 1 will make use of AJAX.

Closing this since basic AJAX support has been implemented. We're not done yet, obviously, but the remaining areas that "require" AJAX can have their own issue.


[Question] Any ways to save the project with a script?

Hi,
I'm working on an auto-save script and I wonder if there is a method to save the project with a script. But I couldn't find anything related to this in the manual.
Or if there is an open API for the read-and-write function so that I can write into a project file manually?

And in my opinion, the auto save is very important. All in all, I don't want to lose my 1-hour-edited file because of the crash of sv once again.
Of course, add the auto save function in sv is also very useful. But I think an open API support could give the turner or coder more way to expand the function of sv.


Add additional method for timestamp support?

I would rather test with timestamps, such as MockDate.setTimestamp(0);
such that I can test the behavior after a certain amount of seconds, minutes, etc. again.
e.g.: MockDate.setTimestamp(60000).
It would be awesome to have this functionality.

I don't plan on implementing that, as it's orthogonal to what this library tries to accomplish.
That said, this might be what you're looking for - https://sinonjs.org/releases/v1.17.6/fake-timers/


Loss curve differences for pretraining

Hi,
we are currently pretraining a 7b model on ~1T tokens, and our loss curve looks similar to the one in the MPT-7b blog post, figure 6.
I am wondering, why in this curve the loss value is always above 2.0, while for other training runs (e.g. LLaMa-1, figure 1, LLaMa-2, figure 5 it quickly goes below 2.0 .
I get that in the end the MPT model performs well, but can this difference in loss scores be explained?
Potential reasons I can think of:
FSDP vs other (e.g. DeepSpeed, but unknown for LLaMa)?
Any pointers appreciated.

The loss depends on the exact dataset used and the tokenizer used, and so comparing across different training runs that use different datasets and different tokenizers is not meaningful.


Fix remaining failing CPU linux tests.

test/SILGen/builtins.swift -> Extra assert change hanging around.
utils/PathSanitizingFileCheck -> injection bug.
validation-test/ParseableInterface/verify_all_overlays.py -> Just a fix.

@swift-ci please test tensorflow linux


Unable to create post with ACF field values

Hi,
Thanks for this wonderful API,
I am trying to create post with ACF field values, but API creates the post with title and content only and skips the ACF field values. Event I tried to update the ACF field value it throws following error
{
code: 'cant_update_item',
  message: 'Cannot update item',
  data: { status: 500 }
 }

I referred the #176 as well
Find the code snippet below

Someone help to sort out this. Sample code will be more helpful.
Thanks in advance.

im using this wonderful api  to update my products too ,
u can update your acf fields this way ,
after registering your endpoint  for example
wp.productsAPI = wp.registerRoute("wp/v2", "/products/");
this code snippet will update your acf fields
wp
  .productsAPI()
  .create({
    title: "Post number",
    fields: {
      product_name: "product name",
      product_description: "product description",
    },
    status: "publish"
  })

but i still have the problem updating the repeater fields

I had exactly the same issue, thank you @gallaouim this worked for me!!

@gallaouim Does it also apply to regular post type created by CPT UI?

@fkiller im sorry for the late answer but yes it apply to regular post type created by CPT UI

@gallaouim, @donnierisk I can't get your code to post data to acf fields when updating a post.  Are you guys using the ACF to REST API plugin to register the routes for the fields?

Hi @peter-mumford Yes I did use that. I don't have the code anymore to check it exactly unfortunately

When you make an update / create request with WP API you use the word fields instead of acf

I've implemented this solution as written above by @gallaouim, but it didn't work (custom post is created successfully, but no ACF data is available in it after creation). I have a custom route registered and have used the fields property with an object containing my custom fields.
Has anyone seen any changes to this recently that might have changed this? Is this approach still working for others?

I've implemented this solution as written above by @gallaouim, but it didn't work (custom post is created successfully, but no ACF data is available in it after creation). I have a custom route registered and have used the fields property with an object containing my custom fields to create the custom post via the REST API.
Has anyone seen any changes to this recently that might have affected this solution? Is this approach still working for others?

Exactly the same problem here. Did you ever figure this out?

I'm having this same problem as well.


Lua Errors with Pre-Patch

1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:120 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:133 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:146 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:180 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:193 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:206 Couldn't find inherited node: OptionsCheckButtonTemplate
1x Interface/AddOns/MogPartialSets/MogPartialSets.xml:219 Couldn't find inherited node: OptionsCheckButtonTemplate

Replace all instances of OptionsCheckButtonTemplate with SettingsCheckBoxControlTemplate and it should work.

thx!

Fixed in 2.0.0


Allow modals to have a window frame and title

https://github.com/n00kii/egui-modal/assets/108888572/0d4e6b64-c65c-4865-b6e8-e73e6f185975
This allows for modal to have an egui window border with a custom title and an ❌ button to close the modal

update example
add window_title field to ModalStyle

thank you for this. i'm wondering if it might be better to just switch the current implementation of titling to use the window title. the only problem i can think of right now is that the window title gives an implicit "close" option (the x icon) in situations where a developer might not want to give the user an option to ignore the choices presented by the modal. perhaps we can rid of the x icon?

https://github.com/n00kii/egui-modal/assets/108888572/bbf8933e-84db-49d6-9057-2001474669b5
this works, but i'm not sure if it should be shown by default. and since it's better to switch the implementation to just using window titles, should the old title thing be removed?


The tag after relayed name defaults to "m" and is configurable with
RELAYTAG plumbed room command.

Pushed to master.

Super cool!
Is there documentation for this? I guess the plumbing bot needs OPER rights in the IRC channel?

No docs as usual :sweat_smile:
CAPS --add draft/relaymsg in the network room, reconnect and see that the bot has requested and got it during connect. Join it to a channel (with PLUMB if it already isn't), op it and it may work.
You can change the tag/postfix (defaults to m) with ROOM #plumbed-channel RELAYTAG <new tag>.
It does indeed require some privileges in channels to be able to RELAYMSG and there's no fallback so if it's missing privs it'll get errors in the network room and be silent on IRC.

Confirmed working with Conduit.


Execute File in Interactive executes wrong file

Load a Python project.
Close all document windows.
Check under Tools->Python Tools that the command caption is "Execute Project in Interactive".
Open one of the project Python files, any will do as long as it's not the startup file.
Check under Tools->Python Tools that the command caption is "Execute File in Interactive".
If you execute the command, it will execute the project startup file, not the one you opened. That's unexpected / misleading.
It will execute the opened file only if you don't have a project loaded.

This fix definitely makes sense, but now there's no quick way to execute the project in Interactive.
I had gotten used to the convenience of having a shortcut that would execute the project no matter what file I was in. I just updated and am missing the unwanted behavior. Is there any other way to have a shortcut for executing the project from any file without having to choose the project?


Create student.txt

add City Colleges of Chicago

@nickdanes This domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Print checkpointing info

🚀 Feature Request
Currently the checkpointing functionality appears to be entirely silent when successful, both for saving and loading. There is code to print information about checkpoint saving, so it's silence may be a log level issue. Checkpoint loading should at least indicate success, and probably print information about the model params and hparams that were loaded.

You're right, the default loglevel to print is warning. I think it could make sense to change this to info:
https://github.com/mosaicml/composer/blob/357181dfa2e6bf51605134c10c44a026563f27c1/composer/trainer/trainer_hparams.py#L200
Could you send a PR over to 1) add what would be an appropriate amount of logging for checkpoint loading (note that there are already TQDM bars if you're downloading a checkpoint from cloud storage), and 2) change the default loglevel to INFO? Thanks!


Can we use our own data?

What's the structure of the data, what's more, is there pretrained model?

@Weizhongjin Sure, you can use your own data. The structure of data and the pretrained model can be found in README.


Building for minGW

Hi, thank you for creating Sparkling! :star:
Have you ever tried building it on Windows machine with MinGW installed?

Hi!
You're welcome. Yes, I've tried a few times, and it builds and runs nicely :)

A couple of months ago I was trying to build it and was getting an error at this line.
I think it was something related to MinGW not having nanosleep function. My solution was to simply swap #if branches, because MinGW #defines _WIN32. After this change compiler started complaining about not having Sleep function, so I also added:
#ifdef _WIN32
#include <windows.h>
#endif

to file's #includes.
Sorry for so vague explanation and not providing a pull request :disappointed: I don't have an access to any Windows testing environment, but these details just popped into my head and I decided to share with you :blush:
If I was only one to experience these troubles then it's up to you if this code needs to be updated. I don't see any harm in doing so.

fixed in https://github.com/H2CO3/Sparkling/commit/8e418cf7f259a88327af52cbcd0f321312956032.


feat: add OCaml implementation

As I was creating this I noticed #45. Since @doesntgolf beat me to it it's only fair that you merge his contribution once it's fixed. Creating this PR mostly to show interest, thanks for writing an interesting article @benhoyt!

Thanks @rbjorklin, I'm not an OCaml expert so I'm at least glad to see what we came up with was pretty similar.

Closing in favor of #45


github webhook "ping" request kills molybdenum

^[[32m[2014-03-20 20:00:17.598] [INFO] console - ^[[39mXXX github payload:  '{\n    "zen": "Non-blocking is better than blocking.",\n    "hook_id": 1979334\n}'

/root/services/molybdenum.old/app.js:210
      repoName = data.repository.name;
                                ^
TypeError: Cannot read property 'name' of undefined
    at Object.<anonymous> (/root/services/molybdenum.old/app.js:210:33)
    at nextMiddleware (/root/services/molybdenum.old/node_modules/express/lib/router/index.js:139:34)
    at IncomingMessage.<anonymous> (/root/services/molybdenum.old/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:74:9)
    at IncomingMessage.emit (events.js:61:17)
    at HTTPParser.onMessageComplete (http.js:133:23)
    at Socket.ondata (http.js:1019:22)
    at Socket._onReadable (net.js:683:27)
    at IOWatcher.onReadable [as callback] (net.js:177:10)
[ Mar 20 20:00:17 Stopping because all processes in service exited. ]
[ Mar 20 20:00:18 Executing stop method (:kill). ]
[ Mar 20 20:00:19 Executing start method ("/opt/node/0.4.9/bin/node /root/services/molybdenum.old/app.js &"). ]
[ Mar 20 20:00:19 Method "start" exited with status 0. ]

I believe this was fixed in commit d86c6010750b281ac20a5e6caaded12a92446347


[MODULE_NOT_FOUND] Error: ts-jest tried to access …, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

🐛 Bug Report
When I add certain dependencies, I end up with a lot of errors like:
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access @typescript-eslint/eslint-plugin, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access @typescript-eslint/parser, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access clean-webpack-plugin, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access css-loader, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-config-airbnb-base, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-config-airbnb-typescript, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-config-prettier, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-import-resolver-node, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-loader, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-eslint-comments, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-import, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-jest, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-prettier, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-promise, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access eslint-plugin-unicorn, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access esm, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access html-loader, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access html-webpack-plugin, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access jest-cli, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access livereload, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access mini-css-extract-plugin, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access prettier, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access ts-loader, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:16644) [MODULE_NOT_FOUND] Error: ts-jest tried to access webpack-cli, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

This could be related to #1857 but I am not sure though.
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/alexkuc/ts-jest-yarn-2-bug
yarn install
yarn test

Expected behavior
Error [MODULE_NOT_FOUND] should not appear.
Link to repo (highly encouraged)
https://github.com/alexkuc/ts-jest-yarn-2-bug
Debug log:
{"context":{"allowJs":false,"logLevel":20,"namespace":"jest-preset","package":"ts-jest","version":"26.2.0"},"message":"creating jest presets not handling JavaScript files","sequence":1,"time":"2020-08-22T20:11:04.150Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"26.2.0"},"message":"creating Importer singleton","sequence":2,"time":"2020-08-22T20:11:07.949Z"}
{"context":{"allowJs":false,"logLevel":20,"namespace":"jest-preset","package":"ts-jest","version":"26.2.0"},"message":"creating jest presets not handling JavaScript files","sequence":3,"time":"2020-08-22T20:11:07.968Z"}
{"context":{"actualVersion":"26.2.2","expectedVersion":">=26 <27","logLevel":20,"namespace":"versions","package":"ts-jest","version":"26.2.0"},"message":"checking version of jest: OK","sequence":4,"time":"2020-08-22T20:11:07.976Z"}
{"context":{"baseOptions":{},"logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"26.2.0"},"message":"created new transformer","sequence":5,"time":"2020-08-22T20:11:07.976Z"}
{"context":{"fileName":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.test.ts","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"config":{"automock":false,"cache":true,"cacheDirectory":"/private/var/folders/_p/292_lyvd0yg7dg7x9rqgldym0000gn/T/jest_dx","clearMocks":true,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"extraGlobals":[],"forceCoverageMatch":[],"globals":{"ts-jest":{"packageJson":"<rootDir>/package.json"}},"haste":{"computeSha1":false,"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":[],"modulePathIgnorePatterns":[],"name":"cdfe7d1990277dc72edeb7b846199c52","prettierPath":"prettier","resetMocks":false,"resetModules":false,"restoreMocks":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","roots":["/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"slowTestThreshold":5,"snapshotSerializers":[],"testEnvironment":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-environment-jsdom-npm-26.2.0-493360024e-65198f8bc5.zip/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-jasmine2-npm-26.2.2-13dab4f95f-b4aa2bee7c.zip/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/$$virtual/ts-jest-virtual-2cfcad23f9/0/cache/ts-jest-npm-26.2.0-0a2029985b-79dcfa74af.zip/node_modules/ts-jest/dist/index.js",{}]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"instrument":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","supportsDynamicImport":false,"supportsStaticESM":false},"transformerId":1,"version":"26.2.0"},"message":"computing cache key for /Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.test.ts","sequence":6,"time":"2020-08-22T20:11:07.978Z"}
{"context":{"logLevel":30,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"26.2.0"},"message":"no matching config-set found, creating a new one","sequence":7,"time":"2020-08-22T20:11:07.978Z"}
{"context":{"config":{"automock":false,"cache":true,"cacheDirectory":"/private/var/folders/_p/292_lyvd0yg7dg7x9rqgldym0000gn/T/jest_dx","clearMocks":true,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"extraGlobals":[],"forceCoverageMatch":[],"globals":{"ts-jest":{"packageJson":"<rootDir>/package.json"}},"haste":{"computeSha1":false,"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":[],"modulePathIgnorePatterns":[],"name":"cdfe7d1990277dc72edeb7b846199c52","prettierPath":"prettier","resetMocks":false,"resetModules":false,"restoreMocks":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","roots":["/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"slowTestThreshold":5,"snapshotSerializers":[],"testEnvironment":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-environment-jsdom-npm-26.2.0-493360024e-65198f8bc5.zip/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-jasmine2-npm-26.2.2-13dab4f95f-b4aa2bee7c.zip/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/$$virtual/ts-jest-virtual-2cfcad23f9/0/cache/ts-jest-npm-26.2.0-0a2029985b-79dcfa74af.zip/node_modules/ts-jest/dist/index.js",{}]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"backports","package":"ts-jest","transformerId":1,"version":"26.2.0"},"message":"backporting config","sequence":8,"time":"2020-08-22T20:11:07.979Z"}
{"context":{"jestConfig":{"automock":false,"cache":true,"cacheDirectory":"/private/var/folders/_p/292_lyvd0yg7dg7x9rqgldym0000gn/T/jest_dx","clearMocks":true,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"extraGlobals":[],"forceCoverageMatch":[],"globals":{"ts-jest":{"packageJson":"<rootDir>/package.json"}},"haste":{"computeSha1":false,"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":[],"modulePathIgnorePatterns":[],"name":"cdfe7d1990277dc72edeb7b846199c52","prettierPath":"prettier","resetMocks":false,"resetModules":false,"restoreMocks":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","roots":["/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"slowTestThreshold":5,"snapshotSerializers":[],"testEnvironment":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-environment-jsdom-npm-26.2.0-493360024e-65198f8bc5.zip/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-jasmine2-npm-26.2.2-13dab4f95f-b4aa2bee7c.zip/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/$$virtual/ts-jest-virtual-2cfcad23f9/0/cache/ts-jest-npm-26.2.0-0a2029985b-79dcfa74af.zip/node_modules/ts-jest/dist/index.js",{}]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"26.2.0"},"message":"normalized jest config","sequence":9,"time":"2020-08-22T20:11:07.979Z"}
{"context":{"fromPath":"<rootDir>/package.json","logLevel":20,"namespace":"config","package":"ts-jest","toPath":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json","transformerId":1,"version":"26.2.0"},"message":"resolved path from <rootDir>/package.json to /Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json","sequence":10,"time":"2020-08-22T20:11:07.980Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsJestConfig":{"compiler":"typescript","diagnostics":{"ignoreCodes":[6059,18002,18003],"pretty":true,"throws":true},"isolatedModules":false,"packageJson":{"kind":"file","value":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json"},"transformers":{},"tsConfig":{"kind":"file"}},"version":"26.2.0"},"message":"normalized ts-jest config","sequence":11,"time":"2020-08-22T20:11:07.980Z"}
{"context":{"fromPath":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json","logLevel":20,"namespace":"config","package":"ts-jest","toPath":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json","transformerId":1,"version":"26.2.0"},"message":"resolved path from /Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json to /Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/package.json","sequence":12,"time":"2020-08-22T20:11:07.982Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"26.2.0"},"message":"babel is disabled","sequence":13,"time":"2020-08-22T20:11:08.036Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","requireResult":{"exists":true,"given":"typescript","path":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/typescript-patch-ba0dbfd217-f0d3d9c987.zip/node_modules/typescript/lib/typescript.js"},"version":"26.2.0"},"message":"loaded module typescript","sequence":14,"time":"2020-08-22T20:11:08.039Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"26.2.0"},"message":"patching typescript","sequence":15,"time":"2020-08-22T20:11:08.043Z"}
{"context":{"actualVersion":"3.9.7","expectedVersion":">=3.8 <4","logLevel":20,"namespace":"versions","package":"ts-jest","version":"26.2.0"},"message":"checking version of typescript: OK","sequence":16,"time":"2020-08-22T20:11:08.045Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsconfig":{"compileOnSave":false,"configFileSpecs":{"includeSpecs":["**/*"],"validatedIncludeSpecs":["**/*"],"wildcardDirectories":{"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug":1}},"errors":[],"fileNames":["/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.test.ts","/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.ts"],"options":{"declaration":false,"inlineSourceMap":false,"inlineSources":true,"module":1,"noEmit":false,"removeComments":false,"sourceMap":true,"target":1},"raw":{"compileOnSave":false,"compilerOptions":{}},"typeAcquisition":{"enable":false,"exclude":[],"include":[]},"wildcardDirectories":{"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug":1}},"version":"26.2.0"},"message":"normalized typescript config","sequence":17,"time":"2020-08-22T20:11:08.055Z"}
{"context":{"fileName":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.ts","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"config":{"automock":false,"cache":true,"cacheDirectory":"/private/var/folders/_p/292_lyvd0yg7dg7x9rqgldym0000gn/T/jest_dx","clearMocks":true,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"extraGlobals":[],"forceCoverageMatch":[],"globals":{"ts-jest":{"packageJson":"<rootDir>/package.json"}},"haste":{"computeSha1":false,"throwOnModuleCollision":false},"moduleDirectories":["node_modules"],"moduleFileExtensions":["js","json","jsx","ts","tsx","node"],"moduleNameMapper":[],"modulePathIgnorePatterns":[],"name":"cdfe7d1990277dc72edeb7b846199c52","prettierPath":"prettier","resetMocks":false,"resetModules":false,"restoreMocks":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","roots":["/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug"],"runner":"jest-runner","setupFiles":[],"setupFilesAfterEnv":[],"skipFilter":false,"slowTestThreshold":5,"snapshotSerializers":[],"testEnvironment":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-environment-jsdom-npm-26.2.0-493360024e-65198f8bc5.zip/node_modules/jest-environment-jsdom/build/index.js","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":["**/__tests__/**/*.[jt]s?(x)","**/?(*.)+(spec|test).[tj]s?(x)"],"testPathIgnorePatterns":["/node_modules/"],"testRegex":[],"testRunner":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/cache/jest-jasmine2-npm-26.2.2-13dab4f95f-b4aa2bee7c.zip/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.tsx?$","/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/.yarn/$$virtual/ts-jest-virtual-2cfcad23f9/0/cache/ts-jest-npm-26.2.0-0a2029985b-79dcfa74af.zip/node_modules/ts-jest/dist/index.js",{}]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"instrument":false,"rootDir":"/Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug","supportsDynamicImport":false,"supportsStaticESM":false},"transformerId":1,"version":"26.2.0"},"message":"computing cache key for /Users/alexkucheryuk/Repositories/GitHub/ts-jest-yarn-2-bug/fizzBuzz.ts","sequence":18,"time":"2020-08-22T20:11:08.058Z"}

envinfo
System:
    OS: OSX

Npm packages:
    jest: 26.2.2
    ts-jest: 26.2.0
    typescript: 3.9.7
    babel(optional): n/a

Edit: forgot to include errors

@ahnpnl do you know when next release will be available on npmjs?

hi, somewhere this week :)

AWesome, cheers! :)


Fix undefined offset in MethodGenerator

Running symfony2 app/console cache:clear with zend-code version >= 3.0.0 gives this notice:
Notice: Undefined offset: 1 in {path}\vendor\zendframework\zend-code\src\Generator\MethodGenerator.php on line 98
PHP Notice:  Undefined offset: 1 in {path}\vendor\zendframework\zend-code\src\Generator\MethodGenerator.php on line 98

This PR fixes that adding a simple check.

@Ocramius ready to review

Duplicate of #46 and #48. This solution at first look only avoid the error but does not do what the code expect to do.

@mikeSimonson could you elaborate - what does the code expect to do, so I could submit a proper fix?

@loostro The original expect all the lines of the method to be returned in an array. It then try to properly indent thoses lines.
The change that you made just trim the whole body when the explode fail.
There are already 2 fixes for that issue #46 and #48. The maintainer just need to pick the one he find the most appropriate.

@mikeSimonson I see. I hope this gets fixed soon :)


How do i set all errors as warnings or vice versa without manually changing the ruleset in StyleCop.Analyzers

Would love to know this as well. @manistellar2016, can you show us how you do it through changing the ruleset in StyleCop.Analyzers? I'm not sure where to look.

@manistellar2016, I don't know any way of doing exactly what you ask. The closest I can think of is toggling "Treat warnings as errors" in the project properties view, but that's doesn't really do what you asked. If you could start by explaining your situation a bit more, someone might be able to help. What are you trying to achieve?

I ended up creating a ruleset file that does what we needed. It is accessible through Project > References > Analyzers > StyleCop.Analyzers. This gives us granular access to mark individual rules as info/warning/error/none.
Example ruleset file:
<?xml version="1.0" encoding="utf-8"?>
<RuleSet Name="Rules for Our App" Description="Code analysis rules for OurApp.csproj." ToolsVersion="14.0">
  <Rules AnalyzerId="Microsoft.Analyzers.ManagedCodeAnalysis" RuleNamespace="Microsoft.Rules.Managed">
    <Rule Id="CA1001" Action="Warning" />
     ...
  <Rules AnalyzerId="StyleCop.Analyzers" RuleNamespace="StyleCop.Analyzers">
    <Rule Id="SA0001" Action="None" />
    <Rule Id="SA0002" Action="Error" />
    <Rule Id="SA1000" Action="Warning" />
    ...
  </Rules>
</RuleSet>

mariotacke - can you be more explicit on this. I'm trying to figure out how to build a modified SA ruleset for just this purpose. I've built custom rulesets for use by the standard code analysis tools, but it seems that I haven't figured out how to customize what StyleCop.Analyzers is doing.

The rule set file only let's you define which rules are Error/Warning/Info/None. For more specific rule modifications, you can use the stylecop.json file. There is not much you can customize and we opted to go with the SA defaults.

 Do I just add the SA... rules to my existing .ruleset file to override the defaults?

My objective is to have a reduced SA ruleset for certain projects.

That's what we did. Project > References > Analyzers. We enabled the StyleCop.Analyzers rule set there. I don't have access to my project right now, but I can attach some screenshots on Monday if that helps.

What we've found is that when we add StyleCop.Analyzers to a project with NuGet, we end up with the default SA ruleset. Are you saying that if I add SA rules to my existing .ruleset file where our settings for the code analysis tools are that these will override the SA defaults?

Not sure about the overriding part. I think once you specify SA rules in your active rule set, it uses those settings. For example, if you don't have a rule set for StyleCop.Analyzers, all SA rules are warnings by default. There is a menu in the rule set explorer that lets you add all SA rules without having to manually edit the .ruleset file.

I'm going to try that and see if it works, will let you know.
Background: I have had to develop custom rulesets for the standard analyzers (actually going back to FxCop) to deal with cases where, for example, code was converted to C# from VB6. Needless to say, none of the spelling type rules were followed!
In order to deflect objections to using static analysis at all due to the volume of these errors, I came up with a reduced ruleset which omitted those categories. I want to do something similar with the SA rules, mainly for certain test projects. (I still believe that consistency, even in spelling and casing, is desirable but we do want the option of being selective). So I'll experiment and see what happens...

Here's what I've found:
ruleset files are XML files, which contain references to the enabled rulesets.
Following these are sections for each ruleset which simply contain deltas from the referenced ruleset.
If you want a "Custom" ruleset, including customizing the rules used by StyleCop.Analyzer, you need to edit the rules within Visual Studio. Then, save the modified ruleset.
You can easily open it in Notepad, for example, and see the results.
Here is an example from one I modified:

So you can be as selective as you like.

Hmm - it didn't like the XML formatting
 <Rules AnalyzerId="StyleCop.Analyzers" RuleNamespace="StyleCop.Analyzers">     <Rule Id="SA1028" Action="None" />     <Rule Id="SA1101" Action="None" />     <Rule Id="SA1124" Action="None" />     <Rule Id="SA1602" Action="None" />     <Rule Id="SA1610" Action="None" />     <Rule Id="SA1633" Action="Error" />     <Rule Id="SA1634" Action="Error" />     <Rule Id="SA1636" Action="Error" />     <Rule Id="SA1640" Action="Error" />   </Rules>
Maybe it will take as code.

@manistellar2016 Have your issues here been resolved now?

Yes. They are resolved.
On Wed, Jun 28, 2017 at 7:51 AM Sam Harwell<EMAIL_ADDRESS>wrote:

@manistellar2016 https://github.com/manistellar2016 Have your issues
here been resolved now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2318#issuecomment-311682899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWV6KU770C0tcnjDQ-0kj6JXCQmRWun1ks5sImejgaJpZM4Mg6Mm
.

--
Mani Kumar


401 error

npm start

><EMAIL_ADDRESS>start
> node_modules/.bin/ts-node app.ts

Application is live and listening on port 29330
Client started!
[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "AxiosError: Request failed with status code 401".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Umm... Which mode push or notify you are using for LINE?

Umm... I have no idea.
Which mode push or notify you are using?

I'm sure this was incorrect set up of webhook


1.20.1 - BUG - Consistent Crashes When Using CIT Armor (Attached)

Hello, I have encountered gaming crashing when using CIT with these textures (attached). They work fine with normal optifine and I was hoping you would be able to help resolve this issue.
Any and all help would be greatly appreciated and if you need anything from me just let me know!
Here is the crash report: https://pastebin.com/raw/gLdyHtzH
Resources: minecraft_dungeons.zip
Version: 1.12.1
Fabric: 0.14.22
CIT: 1.1.3+120

Dont know what made you think this is to do with CIT Resewn as the first line in the stacktrace
	at me.pepperbell.continuity.client.resource.ResourceRedirectHandler.redirect(ResourceRedirectHandler.java:65)

says that it came from Continuity.


Menu bar icon is invisible on OSX when using dark menu bar due to blending colors

When using the "dark menu bar" option in OSX, the YakYak menu bar icon becomes invisible. Clicking the icon's space reveals the icon because of the background of the menu icon is changed to something lighter which contrasts with the icon.

it's pretty hard to see using Linux as well ..  (doesn't change when clicking though)  - LXDE/Lubuntu 16.04

which " YakYak menu bar icon " are we talking about here? If its the three dots on the upper right corner of the window, I do not have any problem, the dots are same grey as text, in contrast of black background, in dark mode. Or is it something else?

Examples:

https://github.com/electron/electron/blob/master/docs/api/native-image.md#template-image
https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/ToolbarIcons.html#//apple_ref/doc/uid/20000957-CH89-SW3
@Stanko @monchote

It seems this can be done by using Template Image. I'll take a look tomorrow.

I'm not seeing any change with the new release (1.3.2, OSX 10.11.5). Same results as before (https://github.com/yakyak/yakyak/issues/356#issuecomment-243438819).

@ironcladlou I've just built master and it's now displayed as expected:

@ironcladlou It's now live on master as @monchote said, if you build on your own. It should be available on next release if you prefer pre-built binaries.

Confirmed fixed as of 2aa9f8d99708c3913c9943a27b2966b6a503391a, thanks!


(BSO) Repeat trip button claims minion not owned

🐛 Bug Report
When clicking the repeat trip button after finishing a Dungeoneering or kibble making trip, the BSO bot responded saying that I didn’t own a minion for the Dungeoneering trip and just didn’t react at all for the kibble trip. I tested this with Woodcutting, Firemaking, Sawmill, burying bones, and cooking trips, but so far repeating those trips works just fine.
My best guess would be that since it works fine for slash commands, that it has to do with Dungeoneering and kibble making still running on the old prefix system

Fixed


Added info about ANDROID_BUILD_TASK env var in building Android app docs

Summary
Updated the documentation for building own Android app by adding a new env var: ANDROID_BUILD_TASK
Related PRs
https://github.com/mattermost/mattermost-mobile/pull/5884

Hello @manojmalik20,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@enahum Please review.

@mickmister This is the docs PR.


[PANIC] Index out of range

Hi, I have an index out of range with<EMAIL_ADDRESS>panic: runtime error: index out of range [53] with length 0
goroutine 66 [running]:
github.com/phpdave11/gofpdf.(*Fpdf).write(0xc0003ac000, 0x4020000000000000, {0xc0004eaf00?, 0x4?}, 0x4?, {0x0, 0x0})
         /root/go/pkg/mod/github.com/phpdave11/gofpdf@v1.4.2/fpdf.go:2839 +0xbea
github.com/phpdave11/gofpdf.(*Fpdf).Write(...)
         /root/go/pkg/mod/github.com/phpdave11/gofpdf@v1.4.2/fpdf.go:2901
[...]

There is happening after a call to Write.
Used font are UbuntuFont
strBuff = fmt.Sprintf(
    "\n%s, %s, %s %s\n",
    data.Simple["se-addr-num"],
    data.Simple["se-addr-complement"],
    data.Simple["se-addr-code"],
    data.Simple["se-addr-commune"],
)

log.Println("DEBUG PANIC: ", strBuff)
pdf.Write(8, strBuff)

:thinking:

This happens when we try to write without a loaded font.
My font isn't loaded because I haven't called "SetFontLocation", I'm pointing directly to the root path.
This problem happens here:
https://github.com/phpdave11/gofpdf/blob/b09d9214a2296c8ea10312d9c5a520e27f2148c9/fpdf.go#L74
https://github.com/phpdave11/gofpdf/blob/b09d9214a2296c8ea10312d9c5a520e27f2148c9/fpdf.go#L114
https://github.com/phpdave11/gofpdf/blob/b09d9214a2296c8ea10312d9c5a520e27f2148c9/fpdf.go#L1687
The behavior of path.Join' used with '.' is to remove the '/' if the target has one.    Ex path.Join(".", "/tata/titi/toto.ttf")` = "tata/titi/toto.ttf"
To solve this issue:

Change the magic value of fontDirStr
Check if a font is loaded instead of panic

I planned to make a PR, what do you think about?


Build Revamped UI of Lacking Skills Section

What would you like to share?
Build Revamped UI of Lacking Skills Section

Additional information
Refer to the Figma Design
https://www.figma.com/file/QJdOAP9EB3CbiK3dOiOfaL/ClueLess?node-id=2330%3A7211&t=u23pNyuQlhrFByO2-1

i want to claim this issue
just needed a bit information how to develop these dotted lines

@amdpt323 No need to code this dotted line
According to me, export the image from figma as SVG and position it correctly

can you help me with where is the old UI of lacking skills path in the project dir D'

@amdpt323 There's no old section called lacking skill section.
You have to build it from scratch and push it to dev branch


Errors with translation of entrapment numbers

Page 35: "This 10-shot prompt was evaluated on the remaining items in
the training/development set, yielding ↑ 0.05 (0.30) recall, ↓ 0.70
(0.30) pre cision, and ↑0.05 (0.45) F1 relative to the previous best
prompt."
It seems to me that there is something wrong with the figures? Given
0.30 recall and 0.30 precision, F1 should be 0.30.
At first I thought you inverted the number of precision (i.e., that you
meant "↓ 0.30 (0.70) pre cision", but F1 would be (if I'm not wrong)
0.42---still not your figure.

Page 38: "It did not improve F1, ↓0.09 (0.36) F1, but it led the prompt
engineer in a direction that did, as discussed below. Preci sion
improved to ↑ 0.09 (0.39) precision and recall dropped ↑ 0.03 (0.33)
recall."
On one hand you say recall dropped, on the other hand you have an up
arrow (and 0.33 is indeed +0.03 when compared to the 0.30 noted for the
"10 Shot + Context" attempt's recall).

Page 38: "Ironically, though, removing this email significantly brought
perfor mance back down, ↓ 0.18 (0.18) F1, ↓ 0.22(0.17) precision and ↓
0.13 (0.20) recall."
This seems compared to "One-Shot AutoDiCot + Full Context", which was
not "the best performing previous prompt" (see note 17)?

woo this took a while!


Mean review-Lab #5

Which is the correct code for finding the proportion of accidents that occur on Monday?
I saved accidents that occurred on Monday as an object named Mon.accidents.  I am assuming that Incidentid captures all accidents?
mean(Mon.accidents) #or mean
(Mon.accidents/dat$Incidentid)
#or
 mean(dat$Incidentid[Mon.accidents])

Hi @danafuller! You need the length of each object for the proportion.

Thanks Dr. Young,
I just need a little more clarification.  I understand in the context of
the example that uses cylinders and sorting through the cars in mtcars
defining the length of cylinders as 6, etc.  In our question, are we
defining the length as the values that occur on Monday?
mean(dat$Incidentid == Monday)  If so, how does one give the variable Harm
a length?
Thanks for any clarification!
Dana
On Tue, Sep 20, 2022 at 10:44 PM jacobtnyoung @.***>
wrote:

Hi @danafuller
https://urldefense.com/v3/__https://github.com/danafuller__;!!IKRxdwAv5BmarQ!ZazAaETqJm7zP1O8WMujc5zgq_VU8gKm62B1oTGBfebfDqlRVyw6nWGOlGNRf7Fvy8B6ZauPStRU9eIEUDCEDDqcPA$!
You need the length of each object for the proportion.
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/Watts-College/cpp-526-fall-2022/issues/27*issuecomment-1253232551__;Iw!!IKRxdwAv5BmarQ!ZazAaETqJm7zP1O8WMujc5zgq_VU8gKm62B1oTGBfebfDqlRVyw6nWGOlGNRf7Fvy8B6ZauPStRU9eIEUDDFsK5www$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVKGRUUXKKPCMNJPT3CKZGDV7KOCTANCNFSM6AAAAAAQRORZFE__;!!IKRxdwAv5BmarQ!ZazAaETqJm7zP1O8WMujc5zgq_VU8gKm62B1oTGBfebfDqlRVyw6nWGOlGNRf7Fvy8B6ZauPStRU9eIEUDCQ3ITrng$
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @danafuller. Just a few points of clarification.
This code, mean(Mon.accidents), will take the mean of the values of the object Mon.accidents, however you have defined it. It will return a vector.
This code, (Mon.accidents/dat$Incidentid), will divide each value of Mon.accidents by each value of dat$Incidentid. So that will also return a vector.
This code, mean(dat$Incidentid[Mon.accidents]), will take the mean of the object dat$Incidentid. Without seeing how you have defined Mon.accidents I can't tell you exactly what it will return. But, it will be a scalar (i.e. a single number).

@danafuller, note that the variable Incidentid is a unique id for the incident.

@danafuller, compare these two statements:
mean(dat$Incidentid == Monday) # your code above

and this one:
Monday <- dat$day == "Mon" # create a logical vector meeting the condition.
mean( Monday ) # take the mean.

In your statement, R will return the mean of Incidentid, which is the mean of the unique ids.
See the difference?

Thank you for that.  This is what I did:
Mon.accidents <- dat$Incidentid == "Monday"

Would that have worked?  It seems like it should capture all of the
accidents that occurred on Monday.  Or perhaps it is combining two things
while your code is cleaner and just separating out Monday exclusively and
not accidents as well.
On Wed, Sep 21, 2022 at 7:57 AM jacobtnyoung @.***>
wrote:

@danafuller
https://urldefense.com/v3/__https://github.com/danafuller__;!!IKRxdwAv5BmarQ!es9OrYShH2KkWmxW62UhgvmLQVJymvQOMRsgvSHz8YxBfQ3F_IW6cWyNfILd2_N32YTKp3aiatXqkEwoFFGye6sHCA$,
compare these two statements:
mean(dat$Incidentid == Monday) # your code above
and this one:
Monday <- dat$day == "Mon" # create a logical vector meeting the condition.
mean( Monday ) # take the mean.
In your statement, R will return the mean of Incidentid, which is the
mean of the unique ids.
See the difference?
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/Watts-College/cpp-526-fall-2022/issues/27*issuecomment-1253832731__;Iw!!IKRxdwAv5BmarQ!es9OrYShH2KkWmxW62UhgvmLQVJymvQOMRsgvSHz8YxBfQ3F_IW6cWyNfILd2_N32YTKp3aiatXqkEwoFFF-ALFoAQ$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVKGRUXC235LTG4T2UWRM7TV7MO37ANCNFSM6AAAAAAQRORZFE__;!!IKRxdwAv5BmarQ!es9OrYShH2KkWmxW62UhgvmLQVJymvQOMRsgvSHz8YxBfQ3F_IW6cWyNfILd2_N32YTKp3aiatXqkEwoFFFcrp3rAg$
.
You are receiving this because you were mentioned.Message ID:
@.***>

@danafuller, for your second question the lab instructions say: "We will define 'harm' as any accident that causes at least one injury OR fatality. You need to define a new variable in your dataset that indicates whether accidents caused harm or not.".
So, you would want to translate the sentence above into a logical statement.
The pseudo code would look something like:
harm  <- an accident where there is more than zero injuries OR an accident with more than zero fatalities
Then, you would replace the sentence with the variables and the logical statement:
harm  <- dat$Totalinjuries > 0  | dat$Totalfatalities > 0
That then gives you a logical vector meeting the condition.

I'm sorry, I feel like I am giving you this piecemeal.  I am not confident
in my answers but want to work through it.  This is what I did to define
the new variable Harm which is different from yours.  Can you explain why
this would not be correct or is it just another way to do the same thing?
Harm <-dat %>% mutate(Harm=Totalinjuries & Totalfatalities) #new variable
(Aren't they by definition those two variables greater than zero or the
value wouldn't exist there?)

On Wed, Sep 21, 2022 at 8:07 AM jacobtnyoung @.***>
wrote:

@danafuller
https://urldefense.com/v3/__https://github.com/danafuller__;!!IKRxdwAv5BmarQ!fLxouZ2RY1O_BJ1Bn6j_cjrpaN83NLtuAtuqnipc4zo_7RlsaUmVs29sss1UaoTi_oRZ3kF63zyNpZK1vAqhbsSr4w$,
for your second question the lab instructions say: "We will define 'harm'
as any accident that causes at least one injury OR fatality. You need to
define a new variable in your dataset that indicates whether accidents
caused harm or not.".
So, you would want to translate the sentence above into a logical
statement.
The pseudo code would look something like:
harm <- an accident where there is more than zero injuries OR an accident
with more than zero fatalities
Then, you would replace the sentence with the variables and the logical
statement:
harm <- dat$Totalinjuries > 0 | dat$Totalfatalities > 0
That then gives you a logical vector meeting the condition.
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/Watts-College/cpp-526-fall-2022/issues/27*issuecomment-1253841195__;Iw!!IKRxdwAv5BmarQ!fLxouZ2RY1O_BJ1Bn6j_cjrpaN83NLtuAtuqnipc4zo_7RlsaUmVs29sss1UaoTi_oRZ3kF63zyNpZK1vAqSup0sOQ$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVKGRUW6BEX55UYNRQCDZCTV7MPU5ANCNFSM6AAAAAAQRORZFE__;!!IKRxdwAv5BmarQ!fLxouZ2RY1O_BJ1Bn6j_cjrpaN83NLtuAtuqnipc4zo_7RlsaUmVs29sss1UaoTi_oRZ3kF63zyNpZK1vAoDUlHRCg$
.
You are receiving this because you were mentioned.Message ID:
@.***>

``
Harm <-dat %>% mutate(Harm=Totalinjuries & Totalfatalities)
#new variable (Aren't they by definition those two variables greater than zero or the value wouldn't exist there?)

You could have the value zero. You will still need a condition that stipulates a logical statement to define the variable.

Thanks for all your help!
On Wed, Sep 21, 2022 at 9:00 AM jacobtnyoung @.***>
wrote:

``
Harm <-dat %>% mutate(Harm=Totalinjuries & Totalfatalities)
#new variable (Aren't they by definition those two variables greater than
zero or the value wouldn't exist there?)
You could have the value zero. You will still need a condition that stipulates a logical statement to define the variable.
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/Watts-College/cpp-526-fall-2022/issues/27*issuecomment-1253912438__;Iw!!IKRxdwAv5BmarQ!dBISJDr_Mzhsfl9hICUgEZtU4uxPEnFK-wmGpp2QOXdRCROHE_nEo5kL0qhM_XxuvFJvRGkiFMJ74PFSUdRwLix51g$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVKGRUW7DAL6U4DK6A5EKSDV7MWLHANCNFSM6AAAAAAQRORZFE__;!!IKRxdwAv5BmarQ!dBISJDr_Mzhsfl9hICUgEZtU4uxPEnFK-wmGpp2QOXdRCROHE_nEo5kL0qhM_XxuvFJvRGkiFMJ74PFSUdSwHYbUBw$
.
You are receiving this because you were mentioned.Message ID:
@.***>

🤙🏼


Sisyphus smiling/update imports

Closes: #132
Description
Update import schema and restructure directories to /contracts /transactions /scripts from top-level.

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

[ ] Update the version in package.json when there is a change in the smart contracts

Going to close this because it was already handled in a different PR


Exclude all io.netty from hive-agent tests

Exclude all io.netty from hive-agent tests
Even if that dependency was in test scope, its transitive dependencies
were marked in compile scope. It used 4.1.77 version for io.netty which
is flagged for CVEs.

FYI @mneethiraj @ksobolew

@mneethiraj Any chance to land this before release-ing Ranger 2.5.0?

@kokosing  - this update will likely not be to be included in Ranger 2.5.0 release; release-candidate #3 is already out for voting. I suggest getting this merged in master branch for 3.0.0 release; if a maintenance release is necessary, 2.5.1 release can be considered.

Patch merged via RANGER-4884.

Thank you!


fix bug in clear_history

Fixes issue #258

Thanks!
Probably this bug was introduced in the aftermath of JuliaLang/julia#3439


RandomBytes resource broken in nodejs runtime

What happened?
Wrote a new stack program with a single index.ts to show that the @pulumi/pulumi package resource RandomBytes is not working. Received error:
Diagnostics:
  pulumi:pulumi:Stack (delme-dev):
    panic: reflect: call of reflect.Value.MethodByName on zero Value
    goroutine 58 [running]:
    reflect.Value.MethodByName({0x0?, 0x0?, 0x140003e2610?}, {0x104c4b1ca?, 0x1400068e100?})
    	/opt/hostedtoolcache/go/1.21.4/x64/src/reflect/value.go:2047 +0x114
    github.com/pulumi/pulumi-terraform-bridge/pf/internal/pfutils.hasMethod(...)
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/internal/pfutils/reflector.go:63
    github.com/pulumi/pulumi-terraform-bridge/pf/internal/pfutils.extractNestedAttributes({0x0?, 0x0?})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/internal/pfutils/reflector.go:26 +0xa8
    github.com/pulumi/pulumi-terraform-bridge/pf/internal/pfutils.FromAttrLike(...)
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/internal/pfutils/attr.go:68
    github.com/pulumi/pulumi-terraform-bridge/pf/internal/pfutils.(*schemaAdapter[...]).AttributeAtPath(0x0?, {0x105152cb8?, 0x14000495c20?}, {{0x140003e2590?, 0x104ef41a0?, 0x140006d4f01?}})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/internal/pfutils/schema.go:120 +0x1b0
    github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.newIDExtractor({0x105152cb8, 0x14000495c20}, {0x14000132ae0, 0xc}, {0x10515a2f0, 0x14000137720})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/tfbridge/ids.go:39 +0xac
    github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).resourceHandle(0x140001c7600, {0x105152cb8, 0x14000495c20}, {0x140006a4100?, 0x104e33d40?})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/tfbridge/provider_resources.go:56 +0xbc
    github.com/pulumi/pulumi-terraform-bridge/pf/tfbridge.(*provider).CheckWithContext(0x140001c7600, {0x105152cb8?, 0x14000494e70?}, {0x140006a4100, 0x40}, 0x104ef3b20?, 0x140006d56a8?, 0x3c?, {0x1400044a000, 0x20, ...})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/tfbridge/provider_check.go:44 +0x198
    github.com/pulumi/pulumi-terraform-bridge/pf/internal/plugin.(*providerServer).Check(0x14000494600, {0x105152cb8, 0x14000494e70}, 0x140004b0600)
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/pf@v0.21.0/internal/plugin/provider_server.go:295 +0x184
    github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Check_Handler.func1({0x105152cb8, 0x14000494e70}, {0x10507d680?, 0x140004b0600})
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.96.2/proto/go/provider_grpc.pb.go:557 +0x74
    github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1({0x105152cb8, 0x14000494990}, {0x10507d680, 0x140004b0600}, 0x1400068e060, 0x140003d0150)
    	/home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x2e8
    github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Check_Handler({0x105103240?, 0x14000494600}, {0x105152cb8, 0x14000494990}, 0x14000192200, 0x1400068f060)
    	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.96.2/proto/go/provider_grpc.pb.go:559 +0x12c
    google.golang.org/grpc.(*Server).processUnaryRPC(0x1400011e000, {0x105152cb8, 0x14000494570}, {0x10515c580, 0x1400033b380}, 0x1400037ab40, 0x14000494690, 0x105a05510, 0x0)
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.59.0/server.go:1343 +0xb8c
    google.golang.org/grpc.(*Server).handleStream(0x1400011e000, {0x10515c580, 0x1400033b380}, 0x1400037ab40)
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.59.0/server.go:1737 +0x988
    google.golang.org/grpc.(*Server).serveStreams.func1.1()
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.59.0/server.go:986 +0x88
    created by google.golang.org/grpc.(*Server).serveStreams.func1 in goroutine 56
    	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.59.0/server.go:997 +0x160

  random:index:RandomBytes (xyz):
    error: error reading from server: EOF

Example
import * as random from '@pulumi/random'
const rnd = new random.RandomBytes('xyz', { length: 32 })
export const hex = rnd.hex

Output of pulumi about
CLI
Version      3.101.1
Go Version   go1.21.6
Go Compiler  gc

Plugins
NAME    VERSION
nodejs  unknown
random  4.15.0

Host
OS       darwin
Version  14.2.1
Arch     arm64

This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v21.5.0'

Current Stack: <snip>

Found no resources associated with dev

Found no pending operations associated with dev

Backend
Name           pulumi.com
URL            <snip>
User           <snip>
Organizations  <snip>
Token type     personal

Dependencies:
NAME            VERSION
@pulumi/random  4.15.0

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @mattfysh. Thanks for letting us know about the issue. I am able to repro. We'll take a look shortly.

Looking briefly, the random.RandomBytes resource does not have an "id" attribute in the schema. Pulumi assumes the existence of this attribute but unfortunately due to bugs in error handling this did not get surfaced at build time nor indeed was it surfaced at runtime in a helpful way. Looking at the implementation code for the resource they have something like this:
state.Base64 = types.StringValue(req.ID)

So it is probably OK to equate some of the structural attributes like the base64 random string with identity for these resources. Having a look at what it would take to support this in the bridge quickly.

This should be fixed in https://github.com/pulumi/pulumi-random/tree/v4.15.1 ! Thank you for reporting.

Thank you for the very fast turnaround :)

Hi there, it seems there is an issue now with saving the snapshot. Previous while I was waiting for the fix I was using:
const rsc = pulumi.output('apikey-tmp')

Which I've now tried replacing with:
const rnd = new random.RandomBytes(`apikey-${client}`, { length: 32 })
const rsc = pulumi.interpolate`prefix_${rnd.hex}`

However when I run the deployment, I get this error:
error: resource complete event returned an error: failed to save snapshot: .pulumi/stacks/project/stack: snapshot integrity failure; it was already written, but is invalid (backup available at .pulumi/stacks/project/stack.json.bak): resource urn:pulumi:stack::project::command:local:Command::bundle dependency urn:pulumi:stack::project::random:index/randomBytes:RandomBytes::apikey-client refers to missing resource

my guess is that the provider snapshotting is not working because it doesn't appear to be writing the entry into the stack state before dependencies are being written (hence the missing reference error)
Reverting back to the hard-coded static string works for now

Scratch that, it's a user issue ;) I'm using the automation API and was creating the resource outside of the inline program


add hidden tag command

related to kosli-dev/server#1587

add hidden command to tag flows and environments
include tags in the tabular output of list flows, get flow, list envs, get env commands
include compliance in get snapshot tabular output

@tooky yes, most of the tabular output is not covered in tests because it's currently a bit tedious to test. It's less likely to break on the CLI, but can easily break if we make breaking changes on the API.


Bloom Popup

Problem Description
There is no action hook after the popup form is submitted.
Reference Code
http://imgwxl.com/a/2021-10-23-03:10:33.png
http://imgwxl.com/a/2021-10-23-03:08:16.png
Why Needed?
Need to integrate it with Autonami CRM and Marketing Automation engine product.
https://buildwoofunnels.com/wordpress-marketing-automation-autonami/

Is anyone at Elegant Themes going to take a look at this?


Component ref is undefined in componentDidMount: react-native

I'm trying to access this.clientRef in componentDidMount  it works in reactjs project but not in react-native
It's undefined when trying to access it in componentDidMount
<SockJsClient url={SOCKET_DOMAIN} topics={["/user/queue/blabla"]}                             onMessage={(msg) => { this.onReceivedMesage(msg) }} headers={customHeaders}                             ref={(client) => { this.clientRef = client }}                             onConnect={() => { this.onSocketConnected() }}                             onDisconnect={() => { console.log('WS Dis-Connected'); }}                             debug={false} />
I want SockJsClient ref when componentDidMount to set a global var so I can access clientRef in setInterval function

Hi @Blacktoviche ,
I suspect something is preventing render for SockJsClient causing refs to not be set.

https://stackoverflow.com/questions/44074747/componentdidmount-called-before-ref-callback/50019873#50019873

This stackoverflow answer explains which cases can cause undefined ref. Please take a look.

Actually there was if() in the render function and it was the cause of the problem
I solved the problem by removing condition and used navigation instead
Thankx


ASCII header is not working after recent commits

Describe the bug
I have this dashboard config:
local db = require('dashboard')
local home = os.getenv('HOME')

db.session_directory = home .. '/.sessions'
db.preview_command = 'cat'
db.preview_file_path = home .. '/.splash'
db.preview_file_height = 13
db.preview_file_width = 102

db.custom_center = {
    {
        icon = '  ',
        desc = 'New File',
        action = 'DashboardNewFile'
    },
    {
        icon = '  ',
        desc = 'Old Files',
        action = 'Telescope oldfiles'
    },
    {
        icon = '  ',
        desc = 'Find File',
        action = 'Telescope find_files'
    },
    {
        icon = '  ',
        desc = 'Live Grep',
        action = 'Telescope live_grep'
    },
    {
        icon = '勒  ',
        desc = 'Load Last Session',
        action = 'SessionLoad'
    }
}

vim.cmd [[
augroup dashboard
autocmd VimLeavePre * SessionSave
augroup end
]]

After last plugin update my ASCII header has disappeared.
To Reproduce
Steps to reproduce the behavior:

Use my config
Run nvim

Expected behavior
ASCII text from $HOME/.splash is shown
Screenshots

but where is the header text in your config?

but where is the header text in your config?

I mean this:
db.preview_command = 'cat'
db.preview_file_path = home .. '/.splash'
db.preview_file_height = 13
db.preview_file_width = 102

use cat | car

use cat | cat

That worked. Thank you. But how does it work? 😅