Introduce components to trigger commands

This project has a lot of potential and something I believe is missing for complex use cases of building Turbo driven interfaces.
An approach here I would like to propose is to introduce the concept of a TurboComponent that will render similar to how the ViewComponent gem works, however have the ability to trigger commands within he context of the component.   Instead of having commands in separate files scattered across the projects that are trigger from views,  we can organise our components together with the commands inside them whilst enabling reactivity within them.
I really like what the LiveWire is doing here in the Laravel ecosystem, and can pull inspiration from how they approached it.

@joshleblanc built ViewComponentReflex (https://github.com/joshleblanc/view_component_reflex) for StimulusReflex which is similar to what you are describing. I know he has been toying with the same concept for the new approach, maybe he can add some details to the situation.

Interesting project, yea something similar would be great for the Turbo ecosystem.
Over the weekend I built a concept that hooks up to LiveWire 3 javascript, and handles server side the excepted output that LiveWire expects.
https://github.com/peopleforce/actionwire

Yeah I'm working on that. I hurt my hand the same day I started so it's been on hold, but I started looking at it again this weekend

@joshleblanc @marcoroth this is a proof of concept that I put together today to try use a component driven approach to update components with reactivity. Would be great to hear what your thoughts are with this approach.
driven by turbo and stimulus to update components.
there is a sandbox app with examples for search, todo list, and increment.

The Elements library in the TurboBoost suite aspires to address encapsulation for well defined UI/UX behaviors; though, it uses a different approach than ViewComponent.

I consider component support to be a worthwhile goal of the TurboBoost suite but don't think the functionality would live in the Commands library. Let's continue this conversation on the Elements project as it's a more suited to this topic. Having said that, I believe that a server rendered ViewComponent approach would likely get its own library in the suite.
Moved convo to: https://github.com/hopsoft/turbo_boost-elements/issues/45


Fix ESMFold API requests - disable SSL to avoid certificate errors

Fixes #80  - now ESMFold API requests work and don't fail SSL certificate checks.
ProteinCartography/esmfold_apiquery.py has been updated to disable SSL when making the API request, and suppress the warnings from the requests module.
Tested using python ProteinCartography/esmfold_apiquery.py -i 2PK8_monomer.fasta -o ./2PK8_esmfold.pdb - outputs a PDB file as expected.

I've added more commits - I've changed the warnings.simplefilter() to only include the SSL warning, and I've reformatted my files using the make format workflow as suggested. I've also added a comment indicating that this is (hopefully) a temporary fix.
Let me know if there's anything else :)

Looks great! There's just one more tiny formatting issue - the comment on line 57 in esmfold_apiquery.py is too long (the max line length in 100 chars and unfortunately ruff doesn't automatically fix this). If you break that line into two lines, then that should get the CI checks passing. Thanks!

(PS: On Twitter, we saw that you were having issues regarding BLAST with the pipeline, if you share more details in a GitHub issue so we can replicate, we'd be happy to look into and try to issue a fix).

I'm currently having some issues replicating my own BLAST errors! Will investigate further.
I also had some ideas on avoiding BLAST searches but I'll post these in #67


chat gtp

Is your feature request related to a problem? Please describe.
I just wish this whole thing would have chat gtp running inside of vs code, it would make alot of people days easier
Describe the solution you'd like:
Implementation of openai.com in a box that you can right click and all of your problems should be solved.
Describe alternatives you've considered:
Really any good code chat bot should suffice i just like openai
Additional context:
no

Hi, This seems to be intended for the vscode team, so please report it on their github repo, thanks
https://github.com/microsoft/vscode


ValueError: need more than 0 values to unpack

Getting the following error in my engine model, commit  377b9dd found at
https://github.com/hoburg/gpkit-models/pull/72#issuecomment-224971711
Traceback (most recent call last):
File "C:\Users\mayork\Documents\GitHub\gpkit-models\gpkitmodels\aircraft\engine_component_testing.py", line 51, in
turbinesol = turbine.solve(verbosity = 4)
File "C:\Python27\lib\site-packages\gpkit\constraints\prog_factories.py", line 80, in solvefn
result = solvefn(solver, verbosity-1, *args, **kwargs)
File "C:\Python27\lib\site-packages\gpkit\geometric_program.py", line 204, in solve
self.result = self._compile_result(solver_out)  # NOTE: SIDE EFFECTS
File "C:\Python27\lib\site-packages\gpkit\geometric_program.py", line 310, in _compile_result
k, = self.constraints.varkeys[k]
ValueError: need more than 0 values to unpack
I'm 99% sure the models is solving to an optimal state, with verbosity = 4 I get the following output before the error
Using solver 'cvxopt'
Solving for 11 variables.
pcost       dcost       gap    pres   dres
0:  0.0000e+00 -8.6299e-01  2e+01  1e+00  1e+00
1: -3.0447e+05  2.0751e+04  7e+00  6e+03  5e-01
2: -9.7752e+03  7.4407e+00  3e-01  2e+02  2e-02
3: -1.7001e+02 -1.3899e+01  4e-03  3e+00  3e-04
4: -1.5466e+01 -1.3820e+01  4e-05  3e-02  8e-02
5: -1.4027e+01 -1.3505e+01  7e-06  9e-03  1e-01
6: -1.3548e+01 -1.3377e+01  1e-06  2e-03  7e-02
7: -1.3366e+01 -1.3357e+01  2e-08  1e-04  1e-02
8: -1.3357e+01 -1.3357e+01  4e-10  3e-06  3e-04
9: -1.3357e+01 -1.3357e+01  4e-12  3e-08  4e-06
10: -1.3357e+01 -1.3357e+01  4e-14  3e-10  4e-08
Optimal solution found.
Solving took 0.06 seconds.
I also checked everything by hand and it seems feasible

Uh oh, there seem to be no varkeys when the gp thinks there should be. Hmm.
On Jun 9, 2016 10:15, "mayork"<EMAIL_ADDRESS>wrote:

Getting the following error in my engine model, commit 377b9dd found at
hoburg/gpkit-models#72 (comment)
https://github.com/hoburg/gpkit-models/pull/72#issuecomment-224971711
Traceback (most recent call last):
File
"C:\Users\mayork\Documents\GitHub\gpkit-models\gpkitmodels\aircraft\engine_component_testing.py",
line 51, in
turbinesol = turbine.solve(verbosity = 4)
File "C:\Python27\lib\site-packages\gpkit\constraints\prog_factories.py",
line 80, in solvefn
result = solvefn(solver, verbosity-1, *args, **kwargs)
File "C:\Python27\lib\site-packages\gpkit\geometric_program.py", line 204,
in solve
self.result = self._compile_result(solver_out) # NOTE: SIDE EFFECTS
File "C:\Python27\lib\site-packages\gpkit\geometric_program.py", line 310,
in _compile_result
k, = self.constraints.varkeys[k]
ValueError: need more than 0 values to unpack
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hoburg/gpkit/issues/733, or mute the thread
https://github.com/notifications/unsubscribe/ABagGAf4mrIf-HYd-3amEhHV1M0JI19aks5qKFhEgaJpZM4IyQYG
.

This model was for a sub component of the engine, when I link this model with the other component models it works fine. Not sure if that helps at all.

@bqpd or @whoburg is there a work around to this where I can print or the solution table or in some other fashion see the solution? If not, could this become a higher priority fix? Seeing the solutions to the two models throwing this error would be really helpful

Fixed in #740


Support Widening Mul

Thanks, although I would like to see the standard library API stabilized before we replicate it here.


[BUG] codeLensProvider error

Hi,
dart_language_server sends
"codeLensProvider": false

instead of
"codeLensProvider": null

to clients.
See: https://github.com/autozimu/LanguageClient-neovim/issues/335
for more details.

Published 0.1.9+4. Please upgrade and let me know if it is still an issue for you.

The error is gone but code completion doesn't seem to work.

Are you seeing the same thing as described in https://github.com/natebosch/dart_language_server/issues/26 ?

FInaly works with an older version of LanguageClien-neovim.

Sounds good. Definitely let me know if you find further evidence that there is a bug with the server implementation. The issue as filed was very actionable - thanks!


feat: add StaticLegend

Closes #21154

Removes unused, conflicting, and confusing references to "Legend"
Adds a collection of properties for the Static Legend which is a new feature for the UI

[x] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[x] http/swagger.yml updated (if modified Go structs or API)
[x] Feature flagged (if modified API)
[x] Documentation updated or issue created (provide link to issue/pr)  - documented in Giraffe
[x] Signed CLA (if not already signed)

force push was to rebase on master

Ready for review.

force push to resolve merge conflicts

ready for review


Bash Completion Provider

Summary
Would be awesome for RSSH to have an official ™ bash/zsh/*sh completion provider.
The idea would be if you type ssh -J rssh then hit tab, and it would suggest IDs/names of clients to connect to.
Perhaps the completion should look for any ssh command where the string -J rssh is present? And then users would be encouraged to have SSH config entries for rssh.
If a user has multiple RSSH servers they could name them rssh-shell-catcher rssh-somethingelse, and the completion provider would automagically query the right one.
Motivation
It's a bit annoying that if you want to find which client to connect to, you have to typically do something like ssh rssh ls, to find the ID, copy it, then ssh -J rssh <id here>.

This is now on unstable.
To use it:
Generate your autocompletions and add it to your bashrc
ssh localhost -p 3232 autocomplete --shell-completion localhost:3232 >> ~/.bashrc

Then you can use it such as
ssh -J localhost:3232 <TAB>
# or
ssh localhost -p 3232 exec/kill/connect <TAB>


[hive] fix pkg name of mysql-connector-java(src) to libmysql-java(bin)

fix pkg name of mysql-connector-java(src) to libmysql-java(bin)
On both debian and ubuntu (checked both precise and trusty) the binary pkg name is libmysql-java, for source pkg name of mysql-connector-java
This change was required to deploy on normal distribution of precise.

Ehh... literally just changed this. Which distribution are you using?

Also, this won't merge once #169 is merged. This code's been moved.

This breaks HDP 2.2, which has packages that require mysql-connector-java via dependencies in the packages. Both libmysql-java and mysql-connector-java provide the same /usr/share/java/mysql-connector-java.jar and cannot be installed at the same time.
http://s3.amazonaws.com/public-repo-1.hortonworks.com/index.html#/HDP-UTILS-<IP_ADDRESS>/repos/ubuntu12/pool/main/m/mysql-connector-java

Yeah, as I suspected... Cloudera doesn't provide this package, themselves. This means a conditional needs to be used for the package name based on distribution... whee.

Closing this, as I am going to fix this in #169


Unavailable link for "Use this  template" under Get Started

I would like to learn how to create .xll from scratch.
However, I found that the link provided under Get Started is broken:

Could you please suggest?
Thanks a lot!

It points to https://github.com/xlladdins/xll_template/generate. Try again?

noted.
Do I need to download all the files in XLL folder in the link below as well?
https://github.com/xlladdins/xll
Thanks

No

When I download the files from link "Use this template" in the the link below,
https://github.com/xlladdins/xll_template/generate
I got the files as screenshot below, however, the folder "xll" has no any file inside

When I open the file "xll_template.sln", then I got this in Microsoft Visual Studio:
Or do I need to use "Clone a repository" in Visual Studio instead of double click the file "xll_template.sln"
Thanks a lot for your clarification

I'm not clear on what you mean by "download the files from the link". When I click on the link I see:

I am going to post this now to see how it shows up on github. You seem to be more advanced than I am with doing this.

I think I'm getting the hang of this now:

Click on Create repository from template.
I see:

.

Tap on Code and Open with Visual Studio. You might have to click on xll_template.sln to open the solution.
If you are using Visual Studio 2022 then F5 will build the xll and start Excel with the add-in loaded.
It can work with older versions but there are two more steps.

ok thanks a lot!
now, it seems to be working.
Previously, instead of Code and Open with Visual Studio, I click on Code and Download Zip.
Thanks a again, I'm quite new to Github as well as Xll with C++, now I will start learning to create some UDF from this.

You know enough to close an issue when it has been resolved. Time for you to get to work on what you are passionate about and have people open issues on what you create. Keep me in your loop on your journey.👍


ITP Volunteer Overview ticket

Background
This ticket tracks all the volunteer mobilisation needed for ITP
Acceptance criteria

[ ] https://github.com/CodeYourFuture/Ops-Programme/issues/139
[x] https://github.com/CodeYourFuture/Ops-Programme/issues/143
[x] https://github.com/CodeYourFuture/Ops-Programme/issues/136
[x] https://github.com/CodeYourFuture/Ops-Programme/issues/124
[x] https://github.com/CodeYourFuture/Ops-Programme/issues/144

Owner
@lilianabermudes
Stakeholder
@SallyMcGrath
Approver
@SallyMcGrath

@MarianaVazquezCYF , is this ticket still open because of https://github.com/CodeYourFuture/Ops-Programme/issues/139?
Should we move this to the next ITP iteration (or do a new ticket)?


[WIP] reconcile CLI/config priority

remove config=True from several parameters, making them explicit (i.e. CLI-only, or via Repo2Docker attributes if called from Python). more info. From two groups of options:

should be set on a per-call basis (config files should only set values that make sense across all or at least most repo2docker runs)

repo
ref
output_image_spec (aka --image)

boolean options that lack inverse, so CLI cannot override non-default config (could also be fixed by leaving configurable and adding both-direction bool flags, like --[no-]run):

push
run
dry_run (aka --no-build)

avoid CLI defaults clobbering values from config. Mostly by using default=None, and adding if args.name is not None checks before assigning attributes, to avoid setting any values from argparse defaults that would override values set by config.
fix --Class.trait=value priority relative to config files (config file should be loaded before loading values from CLI)

Draft for discussion of #1210

it means it can't be managed via traitlets configuration files or traitlet flags like --Repo2Docker.run=True any more?

correct. I think that's a good thing? Avoiding more than one way to set the same value makes things easier to follow, I think. The main reason for CLI config=True is that everything can be set on the CLI, even things we haven't exposed explicitly. I'd argue the current argparse approach is deliberately choosing to select what's on the CLI, rather than exposing everything traitlets-style.

Is it reasonable to retain config=True to support this kind of config-only startup of repo2docker?

For the second class (run, push, etc.), I think it is reasonable, but I don't think we should do that without also making sure we have both directions for all such boolean flags. I don't think it makes sense to allow the repo/ref/image to build, for instance, to be set via config files. I think the only reason to have those as config=True is that it is required for traitlets CLI. Since we don't use traitlets CLI, that should be irrelevant, and I don't think facilitating third-party autogenerated CLI should be something we support.
Since your use case seems to be fully covered by the existing CLI, I'm not sure why generating a CLI that behaves differently is desirable.
But we can definitely go all the way back to everything-is-configurable, we just need to add more handling of each value being set via config without overriding from cli, etc.

Thanks for your work on this @minrk!!! :heart: :tada: I think the changes look good and address relevant issues and are now only thinking about one aspect - the removal of config=True from some configuration.
Consider a service exposing repo2docker to end users via a REST API (I'm working on one). Wouldn't it be neat if it could just accept a blob of repo2docker config in json format in order to launch a build, instead of flags or a mix of flags and config?
I'm currently planning for the repo2docker-service I work on to function like that, thinking it could be an implementation that is sustainable to maintain, document, and build upon. Perhaps even accompanied with traitlets generated JSONSchema or similar.
If you are open to retaining config=True for such reason, I could offload you of implementation work and push commits to take this PR all the way. I'm eager to keep developing on repo2docker-service :)

The config-as-JSON-REST case is an interesting one. I'm definitely open to it! I'm not sure quite where I land on it. I think supporting it is to the detriment of repo2docker itself, because it means that generated documentation of config files / help output produces documented options that should never be set and may not work (the current state of things, fixed by this PR).  I think it doesn't make sense to specify repo or ref in a config file, so adding some logic to the CLI to handle a config case that shouldn't ever happen doesn't feel great to me, where clearly specifying 'repo and ref cannot be set via a config file' seems like the right behavior.
None of the options I've unmarked would logically be exported in a schema of configuration for repo2docker (e.g. into a helm chart like BinderHub). That's a benefit of the change, as I see it. That's not the same as a schema of inputs, which could take all traits which seems it would be unaffected by this change. But those non-config options could not be loaded via a config object, so they would have to be handled separately, which is why I see the appeal.
Do you think that a repo2docker service should not expose inputs such as image and ref at a level more prominent than detailed config like cache_from, etc.? I think a service should fail early and prominently if those are unspecified, so they should get some special handling. Your service also needs to not expose some options like run which should always be False for a service, so exposing it in config means you need to have special-handling to override the input config (not hard - a last, highest priority config object works fine). All of those suggest to me that it is a benefit to your service to not have these exposed in config, even if it means a few more lines of implementation.
I think a REST body that is like:
"image": "...",
"ref": "...",
"config": { additional_options_here }

is clearer than a single passthrough. WDYT?

For reference, flags that no longer gets config=True are the following: repo, ref, output_image_spec, push, run, dry_run.

push - repo2docker-service run on a single computer / k8s cluster probably want push coerced falsy / truthy.
run, dry_run - repo2docker-service would probably always want to coerce them falsy
repo - required by repo2docker itself
ref - optional by repo2docker itself
output_image_spec - optional by repo2docker itself, repo2docker-service may have validation or coercion of the value

In my mind atm, I'm thinking the ideal outcome is that these are all configurable, and a REST API could accept a pure JSON config. repo2docker-service could then perform validation and/or coercion also itself relying on JSON config. For example, users of repo2docker-service could provide their own repo2docker_config_coerced.json, or their own repo2docker_config_schema.json for what criteria should be met before and/or after config coercion.
Back to the bigger picture again: we are considering if repo2docker should retain config=True for everything that the CLI can configure, or if repo2docker should be opinionated on what must be explicitly passed via CLI flags/params.

Do you think that a repo2docker service should not expose inputs such as image and ref at a level more prominent than detailed config like cache_from, etc.?

I still value repo2docker-service interacting with repo2docker in a config native way. I see it as prominent features would be prominent by repo2docker-service specific schema validation config coercion - also config native without coupling to the CLI.

I think it doesn't make sense to specify repo or ref in a config file, so adding some logic to the CLI to handle a config case that shouldn't ever happen doesn't feel great to me, where clearly specifying 'repo and ref cannot be set via a config file' seems like the right behavior.

This seems like the key question: is supporting "config native execution" acceptable from repo2docker's perspective?
I'm inclined to say yes atm.

I greatly value working with config data directly and exclusively over working with a mix of pure config and config influencing CLI flags/args.
A downside for repo2docker is that the argparse implementation complexity grows, but at the same time I see how the consistency of the logic improves. There is no longer a need to keep track of what is given special treatment or not.

It sounds like there a conflict between using repo2docker as a backend where having everything configurable through a standard mechanism (config=True) is helpful, and repo2docker as an interactive tool where you want a friendlier interface. Is it worth separating these two use-cases so in the default CLI argparse has priority, and anyone wanting Traitlets to have priority uses a different entrypoint with no argparse support?

@manics yeah, that's basically the situation we have now with this PR. Everything is still configurable so if you build a default traitlets CLI, it will expose every input via config files, CLI, etc. (this is not changed in this PR, after reverting the removal of config=True for options where that doesn't make sense with our own CLI). But the CLI we use for repo2docker itself has higher priority options, only one of which (repo) cannot actually be specified via config when using the CLI (because it's always overridden). Everything else can be specified by config files and overridden by the CLI. So you get standard priority of CLI > config > defaults, with every option being settable at every level (except repo, which can only be set by CLI because it's a required argument). the main change is that every option in the CLI has to be recognizable as 'specified' or not, so that we don't get the situation of 'cli > cli default > config,' which several options have prior to this PR (#1210)


rocksdb: 5.11.3 -> 6.1.2

Motivation for this change
rocksdb was out of date. also removed stuff that seemed broken.
Things done

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

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

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

cc @adevress

@GrahamcOfBorg build rocksdb

@GrahamcOfBorg build ceph

this also breaks ceph. and everything that depends on it. But ceph seems to be an old version? @adevress  @alexanderkjeldaas

since no one responded for the ceph breakage, we marked ceph as broken.

i tried to unbreak osquery with no luck. i failes when linking against rocksdb(-lite). see https://gist.github.com/magenbluten/997142eaa828ccd177c0dd06cc8261b4

@Ma27 any points against merging this? since you recently updated osquery and this PR would break it.

No. While working on osquery quite recently I realized that they currently have a hard time staying up-to-date with new software versions and I don't consider osquery important enough to actually block this PR any longer.
Therefore, it's IMHO ok to merge this now, I'll take care of osquery on one of the next weekends :)

@magenbluten @Lassulus I managed to get osquery building locally (didn't test ceph as a bunch of python2 deps appear to be broken on master atm) and it works perfectly fine when using the old build system (no cmake). I suspect this is because the cmake build doesn't create statically linked libraries.
According to the install section it's recommended to simply use make {shared,static}_lib depending on what's needed.
I'd simply go back to the old build approach for rocksdb (and keep 6.1.2), however I'm not sure if I'm missing a reason why cmake is used now (and I probably just didn't manage to get the static lib building with cmake ^^).
Do you think using the old make-based approach makes sense or am I missing something? :)

i guess the install section you mention is outdated (dez. 2018).
the "correct" solution would be to figure out how to make cmake make static libs ;)

git grep -i static_lib:
CMakeLists.txt:set(ROCKSDB_STATIC_LIB rocksdb${ARTIFACT_SUFFIX})


Bring back config join URLs

This PR does the following:

Brings back [Initialization].join-urls which were removed as part of #2175
Updates the init script to allow passing options to via /etc/influxdb/defaults if desired.
Fixes -join flag so it will override the config file join-urls when passed but not when the node has already joined a cluster.
Add better logging in the server around what join URLs are used and not used
Increases the max join attempts a node will try before giving up

Don't forget the CHANGELOG.

Makes sense, some minor feedback that should be addressed before commit. +1


Drop @asyncio.coroutine

@asyncio.coroutine is redundunt for async def functions

Coverage remained the same at 100.0% when pulling f8d430bd0c8b066d3be3bd13c443c4536065e674 on jettify:cleanup into 2a3288270080b731f52f77b2a747d29b6efab07b on zillow:master.

lgtm

merged.


added host volumes

Closes #12

Added host volumes to store postgres data
Added switch to host volumes
Added dynamic variables
Updated README

Tests?

Changed to draft since we have some issues with permission denied when setting /var/lib/postgres/data as a volume to /vagrant/persitence/postgres.

STATUS:
We're taking a break from this issue due to problems with permission denied with postgres and vagrant. This will unfortunately not be able to reach the release v0.1.0 deadline (02.10.2020).
Going to pick this up on monday next week.

You have missed out this piece of code that we need to add so that the new host_policy in nomad gets applied. Without this you will end up getting 403 permission denied when run with nomad_acl=true :
- name: Fetch bootstrap token nomad
  shell:
    cmd: vault kv get -field=secret-id secret/nomad-bootstrap-token
  when: lookup('env', 'nomad_acl') | bool
  register: bootstrap_token

- name: Copy nomad policy file to /etc/nomad.d/policies/
  copy:
    src: host_volume_policy.hcl
    dest: /etc/nomad.d/policies/host_volume_policy.hcl
  when: lookup('env', 'nomad_acl') | bool

- name: Update default write policy on nomad
  shell:
    cmd: nomad acl policy apply write-default /etc/nomad.d/policies/host_volume_policy.hcl
  when: lookup('env', 'nomad_acl') | bool
  environment:
    NOMAD_TOKEN: "{{ bootstrap_token.stdout }}

You can check the code in minio_repo

You have missed out this piece of code that we need to add so that the new host_policy in nomad gets applied. Without this you will end up getting 403 permission denied when run with nomad_acl=true :
- name: Fetch bootstrap token nomad
  shell:
    cmd: vault kv get -field=secret-id secret/nomad-bootstrap-token
  when: lookup('env', 'nomad_acl') | bool
  register: bootstrap_token

- name: Copy nomad policy file to /etc/nomad.d/policies/
  copy:
    src: host_volume_policy.hcl
    dest: /etc/nomad.d/policies/host_volume_policy.hcl
  when: lookup('env', 'nomad_acl') | bool

- name: Update default write policy on nomad
  shell:
    cmd: nomad acl policy apply write-default /etc/nomad.d/policies/host_volume_policy.hcl
  when: lookup('env', 'nomad_acl') | bool
  environment:
    NOMAD_TOKEN: "{{ bootstrap_token.stdout }}

You can check the code in minio_repo

Oh, that's right! Thank's! :pray:


Convert enableQueries to higher-order function (like a decorator)

Extensions like enableQueries are more powerful if they operate on a function (createHistory) rather than the thing it returns (history). The reason in a nutshell is that it allows the extension to intercept/modify both the input and output of the function. For example, this is how decorators work. It's also how store enhancers, like applyMiddleware() and devtools(), work in Redux.
For simple extensions like enableQueries, it doesn't end up making a huge difference, but for future extensions it may. Better to establish the convention now rather than later :)
(Because of indentation, this looks like a bigger PR than it actually is. The key lines that have changed are 11-13 of enableQueries.js.)

Looks great, and sound reasoning. Thank you!


3.10 binary looks to be to small suspect and issue the the uri for download

3.10 tars are corrupted and can't be used to install

https://github.com/openshift/origin/releases/download/v3.10.0/openshift-origin-client-tools-v3.10.0-dd10d17-linux-64bit.tar.gz default binary url downloads about 25mb
https://github.com/openshift/origin/releases/download/v3.10.0-rc.0/openshift-origin-server-v3.10.0-rc.0-c20e215-linux-64bit.tar.gz rc0 binary url downloads about 190mb
each case the tar file is corrupted . Typical the tar file should be between 40mb and 60mb

tested the default url in browser and functions correctly


twilio-video upgrade

Question
Hello Twilio team! Are there any plans to update this repo with the latest twilio-video release? It looks like there's some useful bug fixes and support for virtual backgrounds in non-chromium browsers is very interesting.
Thanks for the hard work!
Additional context
N/A

@coreymaher ,
We are in the process of upgrading twilio-video. Please watch this space for updates.


Small fixups

I found a couple small bugs.  I'm not sure of the correct disabling of the spindle page but before some of the settings would disable sections until you toggled the setting off and back on the same setting.

Thanks for the feedback, can you only change one thing per PR?
JT

I fixed the tooltip, the other two I'm not sure of they do.


FirebaseMessaging: RemoteMessage.fromMap(): regression,  faulty handling of 'contentAvailable' & 'mutableContent'

Bug report
Commit: 8a58dac3afbc2a80bfd18398158fdc0f75af1210    (part of PR #4909)
In RemoteMessage.fromMap():
Apparent regression in handling of missing 'contentAvailable' & 'mutableContent' message fields in message map.
These fields are now initialised to 'false' (and are therefore boolean). If the fields are not present in the map, the code attempts to set the value to 'null' (the return from map[] when the key is not present).
This fails as null is not a subtype of bool, although the exception is seemingly not propagated to the application.
Earlier versions of this had, for example,
contentAvailable: map['contentAvailable']??false,
which maintains the bool type. For whatever reason this commit removed the '??false'.
This results in silent failure to deliver messages to the package user (at least for messages where these optional fields are not present).
Expected behavior
Restore the '??false' to maintain type correctness.
Local experimentation shows that this seems to work.
I would write a PR but I'm not familiar enough with the structure and workflows of flutterfire to do it within any reasonable time

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, 1.25.0-8.3.pre, on Microsoft Windows [Version 10.0.19041.746], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] VS Code (version 1.52.1)
[√] Connected device (3 available)

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.12.0-133.7.beta
Flutter SDK 1.25.0-8.3.pre
no_words 1.0.0-nullsafety.0

dependencies:
- cloud_firestore 0.17.0-1.0.nullsafety.0 [cloud_firestore_platform_interface cloud_firestore_web firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 0.9.1-1.0.nullsafety.1 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- cupertino_icons 1.0.2
- firebase_auth 0.21.0-1.1.nullsafety.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 0.8.0-1.0.nullsafety.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_messaging 9.0.0-1.0.nullsafety.0 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- freezed_annotation 0.13.0-nullsafety.0 [collection json_annotation meta]
- hooks_riverpod 0.13.0-nullsafety.1 [collection flutter flutter_hooks flutter_riverpod riverpod state_notifier]
- logging 1.0.0-nullsafety.0
- meta 1.3.0-nullsafety.6
- rxdart 0.26.0-nullsafety.1

dev dependencies:
- build_runner 1.11.1 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_server io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- effective_dart 1.3.0
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- freezed 0.13.0-nullsafety.2 [analyzer build build_config meta source_gen freezed_annotation]

transitive dependencies:
- _fe_analyzer_shared 14.0.0 [meta]
- analyzer 0.41.2 [_fe_analyzer_shared args cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- args 1.6.0
- async 2.5.0-nullsafety.3 [collection]
- boolean_selector 2.1.0-nullsafety.3 [source_span string_scanner]
- build 1.6.2 [analyzer async convert crypto glob logging meta path]
- build_config 0.4.5 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.7 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 1.5.3 [analyzer build crypto graphs logging meta path package_config pool pub_semver]
- build_runner_core 6.1.7 [async build build_config build_resolvers collection convert crypto glob graphs logging meta path package_config pedantic pool timing watcher yaml]
- built_collection 4.3.2 [collection quiver]
- built_value 7.1.0 [built_collection collection fixnum quiver]
- characters 1.1.0-nullsafety.5
- charcode 1.2.0-nullsafety.3
- checked_yaml 1.0.4 [json_annotation source_span yaml]
- cli_util 0.2.0 [path]
- clock 1.1.0-nullsafety.3
- cloud_firestore_platform_interface 4.0.0-1.0.nullsafety.0 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 0.4.0-1.0.nullsafety.0 [cloud_firestore_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 4.0.2-1.0.nullsafety.1 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 3.1.4-1.0.nullsafety.1 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 3.6.0 [built_collection built_value collection matcher meta]
- collection 1.15.0-nullsafety.5
- convert 2.1.1 [charcode typed_data]
- crypto 2.1.5 [collection convert typed_data]
- dart_style 1.3.10 [analyzer args path source_span]
- fake_async 1.2.0-nullsafety.3 [clock collection]
- firebase_auth_platform_interface 4.0.0-1.1.nullsafety.1 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 0.4.0-1.1.nullsafety.1 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.0-1.0.nullsafety.1 [flutter meta plugin_platform_interface]
- firebase_core_web 0.3.0-1.0.nullsafety.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_messaging_platform_interface 2.0.0-1.0.nullsafety.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 0.2.0-1.0.nullsafety.0 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter
flutter_web_plugins js meta]
- fixnum 0.10.11
- flutter_hooks 0.16.0-nullsafety.0 [flutter]
- flutter_riverpod 0.13.0-nullsafety.1 [collection flutter meta riverpod state_notifier]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- graphs 0.2.0
- http_multi_server 2.2.0 [async]
- http_parser 4.0.0-nullsafety [charcode collection source_span string_scanner typed_data]
- intl 0.17.0-nullsafety.2 [clock path]
- io 0.3.4 [charcode meta path string_scanner]
- js 0.6.3-nullsafety.3
- json_annotation 4.0.0-nullsafety.0
- matcher 0.12.10-nullsafety.3 [stack_trace]
- mime 0.9.7
- node_interop 1.2.1 [js]
- node_io 1.1.1 [node_interop path]
- package_config 1.9.3 [path charcode]
- path 1.8.0-nullsafety.3
- pedantic 1.10.0-nullsafety.3
- plugin_platform_interface 1.1.0-nullsafety.2 [meta]
- pool 1.5.0-nullsafety.3 [async stack_trace]
- pub_semver 1.4.4 [collection]
- pubspec_parse 0.1.7 [checked_yaml json_annotation pub_semver yaml]
- quiver 2.1.5 [matcher meta]
- riverpod 0.13.0-nullsafety.1 [collection freezed_annotation meta state_notifier]
- shelf 1.0.0-nullsafety.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 0.2.4 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 0.9.10+1 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.0-nullsafety.4 [charcode collection path term_glyph]
- stack_trace 1.10.0-nullsafety.6 [path]
- state_notifier 0.7.0-nullsafety.0 [meta]
- stream_channel 2.1.0-nullsafety.3 [async]
- stream_transform 1.2.0
- string_scanner 1.1.0-nullsafety.3 [charcode source_span]
- term_glyph 1.2.0-nullsafety.3
- test_api 0.2.19-nullsafety.6 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timing 0.1.1+3 [json_annotation]
- typed_data 1.3.0-nullsafety.5 [collection]
- vector_math 2.1.0-nullsafety.5
- watcher 0.9.7+15 [async path pedantic]
- web_socket_channel 1.1.0 [async crypto stream_channel]
- yaml 2.2.1 [charcode collection string_scanner source_span]

So, I'm fixing to find time to do a PR for this. Thinking more carefully about the issue though:

the original intent (which my fix-the-regression proposal above tried to maintain) was apparently to have these two fields always present, but defaulting to 'false', presumably to support higher level processing on Apple platforms (but I don't have one to confirm or deny). For android they are completely irrelevant, as I understand it (and with the V1 API and admin sdk I seem unable to include them in the message to be sent to an android device in any case).

so a more appropriate change would be to make them nullable -- from the viewpoint of reflecting the protocol.

this would leave it up to higher layers (on apple'ish platforms) to null-check, or null cast-away, the values, depending on the context (I know 'null' about apple platforms, and I don't have one to experiment with).

Which approach do the experts deem to be appropriate?
PS: sorry if I'm a PITA, but the very simple PoC app I'm working on could (and therefore should, if possible) be sound-null-safe. But that makes it imperative to fix this issue, for android platform usage. I think the messaging example only works now because it is running unsound-null-safe, which disguises the issue? Sadly, some dependencies are missing to try in proper null-safe ...

Any update on this one?
Once migrated to null-safety I've received
I/flutter (16763): FlutterFire Messaging: An error occurred in your background messaging handler:
I/flutter (16763): type 'Null' is not a subtype of type 'bool'

Using admin java SDK I don't see the workaround rather than fix it in the lib

No public progress. Amongst other things, I'm still waiting to hear what the preferred approach is for any general fix.
For my own purposes I have patched RemoteMessage.dart locally to put back the original "??false" for mutableContent & contentAvailable.
For example:
contentAvailable:map['contentAvailable'] ?? false,
To be honest the thing that is holding up proposing a PR for this simple fix is the need to create a test that will fail first. It seems that all the tests so far check only interfaces, not functionality (at least I can't find one  that should have failed on this). That's a whole new rabbit hole, and together with being unable to get "Melos" to run error free on my system it means the PR has got bumped from the top of my list in favour of completing other aspects of my project. The infrastructure is too complex fo4r a newcomer at this point, at least for my small brain.

@spacejunky thanks, patching cached plugins code works for now (contentAvailable:map['contentAvailable'] ?? false,)
until the next update =)
Tests should be pretty straightforward if you know the original format ;) specially what fields are optional, what fields are not


[Feature Request] Remove last comma for parameters and argumens

function foo(a1, ) end

foo(1,)

become
function foo(a1) end

foo(1)

This behavior is like gofmt.

This is a syntax error for lua. Is there a good reason to format the wrong syntax

It's convenient to expand snippets for function.
If a snippet is expanded with two parameters and the last is optional, I can remove the last parameter with one keystroke (I have remapped the key) and jump the function body easily.
Without this feature, I must remove the last parameter and type two keystrokes to remove space and last comma, and I can't jump the function body in the next jump in coc.nvim, look like the placeholder is broken in the session.

need some time for think about formatable errors

this feature has been implement, wait for next release

I build the updated code myself.
CodeFormat check -f foo.lua output foo.lua(1:15 to 1:18): here need keep 0 space, But CodeFormat format -f foo.lua output:
function foo(a1,) end

foo(1,)

Thanks, it works now.


Cleanup inline styles

I still count 506 instances of style="... they seem a bit too much to me.
A question: 129 are display: none or alike (I searched "display:) does make sense to keep them as inline style or maybe move to a css class?
Targeting at final because it's cleanup, but if anyone finds the good inspiration... :angel:

Some others in #2215

Down to 377

Did the quick search in just php files and got 344 ... quite a few in install and tests (143 + 32 = 175),  leaving ~169 left to "go" in the core so to speak.
/  3
/install 143
/sources 12
/sources/admin 4
/sources/subs 17
/sources/subs/BBC 10
tests/sources/subs/ 32
/themes/default 123

In 2.0, under the ElkArte directory there on now only 31 .... I think we got all that can be had !


Failure to create project after selecting docker.io image ownership of home directory

Feedback from Jeff:

"failed to create project" after selecting the docker.io image: failed to change ownership of the home directory
Minor issue on error output: the two errors were concatenated on the same line, b/c the usermod error didn't do a newline
usermod: Failed to change ownership of the home directoryFailed to create project.

This needs more detail, instructions on re-creating the issue.

@licquia can you please provide more detail

rootless podman is the problem, no docker daemon running


Store outages in Outages.yaml

@larsks did a proof of concept here that would be both human-friendly and tooling friendly.


Prometheus Exporters

What did you do?
I have Prometheus implemented using Prometheus-operator.
What did you expect to see?
I would like to setup monitoring for the applications like Nginx, Tomcat, Mysql, Redis, Elastisearch
What did you see instead? Under which circumstances?
I tried different approaches and failed to get things up and running on the prometheus dashboard
Environment
AWS

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2", GitCommit:"bdaeafa71f6c7c04636251031f93464384d54963", GitTreeState:"clean", BuildDate:"2017-10-24T19:48:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.10", GitCommit:"bebdeb749f1fa3da9e1312c4b08e439c404b3136", GitTreeState:"clean", BuildDate:"2017-11-03T16:31:49Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
KOPS

Manifests:
Need to create one but I do not have a documentation or walk through on step by step procedure to implement exporters. I just have a running cluster with KOPS monitoring through prometheus on pod and container level metrics. I would like to accomplish the same for applications mentioned above.

We have a walk through for exporters in our documentation: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/running-exporters.md
Let us know if you have any more questions.

Thanks for your reply Brancz. From the link that you provided I could see code for creating service and service monitor, But I need to know on how to integrate the exporters itself.
I would like to know how to setup exporter deployment to make it running as a pod, may be post which I have to create service and service monitor

Can you elaborate? Exporters are run in Kubernetes just like any other workload.

Closing this due to lack of information. Feel free to continue to comment, re-open or open a new issue. There doesn’t seem to be an issue with the Prometheus Operator itself here.


[General] Add and use clang-format configuration

This commit introduces a .clang-format file and applies it to most of NovusCore.
I have not applied it to projects/worldnode/Scripting as I'm not sure how much of that code is NovusCore code.
This is based off #9, but is not trying to answer as many questions.

I imagine that the build failure is the same as the one in master.


Segfault in cycle checker(?)

Opening apology: this is a much-reduced version of a solution to Advent of Code's 2019 day 7 puzzle, which is hard to explain in a vacuum but comes down to implementing a tiny VM with async I/O and running multiple instances of it in communication with each other. After cutting out a lot of extraneous things, I'm left with the attached source files and input. I'm reluctant to reduce it further because I'm starting to think the crash has nothing to do with the VM logic itself, but it's challenging to produce relevant input for a cut-down VM.
My notes refer to testing on both Windows 10 and Arch Linux via WSL2. In both cases ponyc is the latest release 0.51.2. This is a 4-core machine.
Run with: ./intpony input.txt
The three observed behaviors are:

Almost instant exit with no output (~60-70% of the time)
Almost instant exit with correct output (~15% of the time)
Slow exit AFTER correct output (~15% of the time)

The only runtime option I've found to have any effect on this is --ponymaxthreads 1, which on Windows seemingly guarantees the intended output (with fast exit).
Compiled with -d, I get additional possible outcomes including mismatches between the count of RUN outputs and DONE outputs. (This should not happen given the input - each VM/Cpu should run to successful halt.)
The program ends in a segfault, usually, on either the release or debug binary. It's often reported (by gdb) in pony_os_peername on Windows, and in Array_I64_val_Trace on WSL2. Oddly, runs with no segfault also have no output, and successful runs produce output before segfaulting. With --ponymaxthreads 1, no segfault on Windows, but I still get segfaults on WSL2.
The test program creates 100 Cpu actors total, each with a 519-"word" memory (i.e. an Array[I64] with 519 entries). This can be adjusted; it seems that segfaults get more likely as the number goes up. I've never seen a segfault with only 1 or 2 actors, but I have with 4 or 5.
Full stack trace from a crash on WSL2:
#0  0x0000555555568160 in Array_I64_val_Trace ()
#1  0x000055555556895d in Array_u3_t2_$1$10_iso_$1$10_iso_collections__MapEmpty_val_collections__MapDeleted_val_Trace
    ()
#2  0x00007fffe6807600 in ?? ()
#3  0x00007fffe657d600 in ?? ()
#4  0x00007fffffffe750 in ?? ()
#5  0x00007ffff7c91c48 in ?? ()
#6  0x00007ffff7c91e00 in ?? ()
#7  0x0000000000000700 in ?? ()
#8  0x000055555557d534 in ponyint_actor_final ()
#9  0x000055555557f07b in ponyint_cycle_terminate ()
#10 0x000055555558726f in ponyint_sched_shutdown ()
#11 0x0000555555585acf in ponyint_sched_start ()
#12 0x00005555555877d9 in pony_start ()
#13 0x000055555557ce17 in main ()

I've also seen:
#0  0x00007fffe671ccc0 in ?? ()
#1  0x000055555557d534 in ponyint_actor_final ()
#2  0x000055555557f07b in ponyint_cycle_terminate ()
#3  0x000055555558726f in ponyint_sched_shutdown ()
#4  0x0000555555585acf in ponyint_sched_start ()
#5  0x00005555555877d9 in pony_start ()
#6  0x000055555557ce17 in main ()

The plot thickened with a suggestion on Zulip to run with --ponynoblock, disabling the cycle checker (IIUC). This resulted in "dropped output" about 50-75% of the time (rate maybe dependent on running under a debugger or not), but no segfaults.
intpony.zip

@derrickturk have you had a chance to investigate this at all? I know from zulip you were going to look into it some.
If yes, any findings? If no, do you need assistance?

@derrickturk i believe we discussed some about this in zulip, can you bring over the relevant discussion points to this issue so they can help others in the future if anyone else tries to tackle this?

Sharing my notes here from last month after a long delay. I spent some time back in October poking at this after discussing some ideas on Zulip.
I've been testing this all with a debug build of ponyc, in an Arch setup on WSL2:
~/.local/bin/bin/ponyc --version
0.51.3-2665ee7c [debug]
Compiled with: LLVM 14.0.3 -- Clang-14.0.6-x86_64
Defaults: pic=true

Executions of my test program (same as above) are ending in a segmentation fault most of the time, with the full expected output. Sometimes I get the full expected output with no segmentation fault; every once in a while I see no final output and no segmentation fault.
Segmentation faults appear in the tracing functions invoked via ponyint_actor_final in turn invoked via the cycle checker:
Process 8020 stopped
* thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
    frame #0: 0x000055555559f201 intpony`Array_I64_val_Trace + 1
intpony`Array_I64_val_Trace:
->  0x55555559f201 <+1>:  movq   0x18(%rsi), %rsi
    0x55555559f205 <+5>:  callq  0x5555555f85a0            ; pony_trace at trace.c:104
    0x55555559f20a <+10>: popq   %rax
    0x55555559f20b <+11>: retq
(lldb) bt
* thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
  * frame #0: 0x000055555559f201 intpony`Array_I64_val_Trace + 1
    frame #1: 0x00005555555f85cb intpony`pony_trace(ctx=0x00007fffe68ac600, p=0x4000007fffe66cb8) at trace.c:105:3
    frame #2: 0x000055555559f20a intpony`Array_I64_val_Trace + 10
    frame #3: 0x00005555555f85cb intpony`pony_trace(ctx=0x00007fffe68ac600, p=0x00007fffe66cc801) at trace.c:105:3
    frame #4: 0x000055555559f77c intpony`Array_u3_t2_$1$10_iso_$1$10_iso_collections__MapEmpty_val_collections__MapDeleted_val_Trace + 28
    frame #5: 0x00005555555ef11b intpony`ponyint_actor_final(ctx=0x00007ffff7cbbc48, actor=0x00007fffe68ac600) at actor.c:859:5
    frame #6: 0x00005555555f2b47 intpony`final(ctx=0x00007ffff7cbbc48, self=0x00007ffff7cbbe00) at cycle.c:893:7
    frame #7: 0x00005555555f29d3 intpony`ponyint_cycle_terminate at cycle.c:1183:3
    frame #8: 0x00005555555fee5f intpony`ponyint_sched_shutdown at scheduler.c:1143:3
    frame #9: 0x00005555555fd2ef intpony`ponyint_sched_start(library=false) at scheduler.c:1330:5
    frame #10: 0x00005555555ff6f0 intpony`pony_start(library=false, exit_code=0x0000000000000000, language_features=0x00007fffffffe8d0) at start.c:342:7
    frame #11: 0x00005555555ee3cb intpony`main + 267
    frame #12: 0x00007ffff7ce1290 libc.so.6`___lldb_unnamed_symbol3141 + 128
    frame #13: 0x00007ffff7ce134a libc.so.6`__libc_start_main + 138
    frame #14: 0x000055555559da85 intpony`_start at start.S:115

With --ponynoblock, I have not received any segmentation faults, but do sometimes see the final output fail to appear.
Following a suggestion on Zulip from @SeanTAllen, I looked into the possibility of an issue with "orphaned" actors. Setting a breakpoint/watch on pony_create does not show any actors created with orphaned = false. I was unable to find any other code pertinent to the orphaned-actor issue but I'm happy to poke in other places with a little direction.
I'm interested in helping find the underlying issue with the cycle-checker, but I'm also as interested or more in understanding why I see the early-termination behavior. It's possible I've misunderstood the quiescence rules. I am going to try to reduce my example program to something more minimal.

Well, I've reduced the program to reproduce this bug, or at least I think I have. The specific manifestation of the segmentation fault varied as I made changes. The current single-file test program is at the end of this post. The current behavior is:

Usually, no output (early termination, no segfault)
Infrequently, correct output ("Problem 1: 5")
Infrequently, with or without correct output, a segmentation fault

The last backtrace I captured is:
(lldb) run
    Process 15633 launched: '/home/derrick/intpony/intpony' (x86_64)
    Process 15633 stopped
    * thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x7fff0000008e)
        frame #0: 0x0000555555568aaf intpony`ponyint_actor_final(ctx=0x00007ffff7cbbc48, actor=0x00007fffe6707200) at actor.c:858:25
       855    ctx->current = actor;
       856
       857    // Run the actor finaliser if it has one.
    -> 858    if(actor->type->final != NULL)
       859      actor->type->final(actor);
       860
       861    // Run all outstanding object finalisers.
    (lldb) bt
    * thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x7fff0000008e)
      * frame #0: 0x0000555555568aaf intpony`ponyint_actor_final(ctx=0x00007ffff7cbbc48, actor=0x00007fffe6707200) at actor.c:858:25
        frame #1: 0x000055555556c4f7 intpony`final(ctx=0x00007ffff7cbbc48, self=0x00007ffff7cbbe00) at cycle.c:893:7
        frame #2: 0x000055555556c383 intpony`ponyint_cycle_terminate at cycle.c:1183:3
        frame #3: 0x0000555555577eff intpony`ponyint_sched_shutdown at scheduler.c:1143:3
        frame #4: 0x000055555557638f intpony`ponyint_sched_start(library=false) at scheduler.c:1330:5
        frame #5: 0x0000555555578790 intpony`pony_start(library=false, exit_code=0x0000000000000000, language_features=0x00007fffffffe8b0) at start.c:342:7
        frame #6: 0x0000555555567d67 intpony`main + 231
        frame #7: 0x00007ffff7ce1290 libc.so.6`___lldb_unnamed_symbol3141 + 128
        frame #8: 0x00007ffff7ce134a libc.so.6`__libc_start_main + 138
        frame #9: 0x0000555555562795 intpony`_start at start.S:115

At one point while reducing the code, when I still had an Array[I64] serving as an input queue for each Cpu, I saw a segmentation fault in a different place:
* thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x50)
        frame #0: 0x00005555555773cf intpony`final_small(chunk=0x00007fffe6b851c0, force_finalisers_mask=4294967295) at heap.c:196:5
       193      p = chunk->m + (bit << HEAP_MINBITS);
       194
       195      // run finaliser
    -> 196      pony_assert((*(pony_type_t**)p)->final != NULL);
       197      (*(pony_type_t**)p)->final(p);
       198
       199      // clear bit just found in our local finaliser map
    (lldb) bt
    * thread #1, name = 'intpony', stop reason = signal SIGSEGV: invalid address (fault address: 0x50)
      * frame #0: 0x00005555555773cf intpony`final_small(chunk=0x00007fffe6b851c0, force_finalisers_mask=4294967295) at heap.c:196:5
        frame #1: 0x00005555555770f7 intpony`chunk_list(f=(intpony`final_small at heap.c:165), current=0x00007fffe6b851c0, mark=4294967295) at heap.c:377:5
        frame #2: 0x0000555555577230 intpony`ponyint_heap_final(heap=0x00007fffe6c16a40) at heap.c:426:5
        frame #3: 0x000055555556d248 intpony`ponyint_actor_final(ctx=0x00007ffff7cbbc48, actor=0x00007fffe6c16a00) at actor.c:862:3
        frame #4: 0x0000555555570c67 intpony`final(ctx=0x00007ffff7cbbc48, self=0x00007ffff7cbbe00) at cycle.c:893:7
        frame #5: 0x0000555555570af3 intpony`ponyint_cycle_terminate at cycle.c:1183:3
        frame #6: 0x000055555557c66f intpony`ponyint_sched_shutdown at scheduler.c:1143:3
        frame #7: 0x000055555557aaff intpony`ponyint_sched_start(library=false) at scheduler.c:1330:5
        frame #8: 0x000055555557cf00 intpony`pony_start(library=false, exit_code=0x0000000000000000, language_features=0x00007fffffffe8b0) at start.c:342:7
        frame #9: 0x000055555556c477 intpony`main + 231
        frame #10: 0x00007ffff7ce1290 libc.so.6`___lldb_unnamed_symbol3141 + 128
        frame #11: 0x00007ffff7ce134a libc.so.6`__libc_start_main + 138
        frame #12: 0x0000555555564ea5 intpony`_start at start.S:115

I have not seen the original segfault in the trace function for Array[I64] since removing the "memory" array from the Cpu actor.
At this point I am still wondering if this might be related to #1118, as well as how many distinct bugs I am seeing.
use "collections"

actor Main
  new create(env: Env) =>
    let mk = MaxKeeper

    let waiter = CpuWaiter({()(env) =>
      mk.query({(max: (I64 | None)) =>
        match max
        | let m: I64 =>
            env.out.print("Problem 1: " + max.string())
        else
          env.err.print("No max")
        end
      })
    })

    // the larger this number is, the more likely a segfault
    for iter in Range(0, 1000) do
      var cpus = Array[Cpu]
      for i in Range(0, 5) do
        let cpu = Cpu

        if i > 0 then
          try
            cpus(cpus.size() - 1)?.subscribe(cpu)
          end
        end

        cpus.push(cpu)
      end

      try
        cpus(cpus.size() - 1)?.subscribe(mk)
        waiter.wait(cpus(cpus.size() - 1)?)
      end

      try
        cpus(0)?.send(0)
      end

      for cpu in cpus.values() do
        cpu.run()
      end
    end
    waiter.start_waiting()

interface Sendable
  fun tag send(word: I64)

actor Cpu is Sendable
  var _sub: (Sendable tag | None) = None
  var _on_halt: ({ref ()} iso | None) = None
  var _blocked: Bool = false
  var _step: U8 = 1
  var _val: I64 = -1

  be subscribe(rcvr: Sendable tag) =>
    _sub = rcvr

  be subscribe_halt(notify: {ref ()} iso) =>
    _on_halt = consume notify

  be step() =>
    if _blocked then
      return
    end

    match _step
    | 1 =>
        if _val >= 0 then
          _step = 2
        else
          _blocked = true
        end
    | 2 =>
        match _sub
        | let rcvr: Sendable tag => rcvr.send(_val + 1)
        end
        _step = 3
    | 3 =>
        match _on_halt
        | let rcvr: {ref ()} iso => rcvr()
        end
        _step = 4
    end

    if (not _blocked) and (_step < 4) then
      step()
    end

  be run() =>
    if not _blocked then
      step()
    end

  be send(word: I64) =>
    _val = word
    if _blocked then
        _blocked = false
        step()
    end

actor MaxKeeper
  var _max: (I64 | None) = None

  be send(word: I64) =>
    _max = match _max
    | let m: I64 => m.max(word)
    else
      word
    end

  be query(fn: {((I64 | None))} val) =>
    fn(_max)

actor CpuWaiter
  var _waiting: SetIs[Cpu tag] = SetIs[Cpu tag]
  var _wait: Bool = false
  let _when_done: {()} val

  new create(when_done: {()} val) =>
    _when_done = when_done

  be wait(cpu: Cpu tag) =>
    _waiting.set(cpu)
    cpu.subscribe_halt({()(self = recover tag this end) =>
      self._done(cpu)
    })

  be start_waiting() =>
    _wait = true
    if _waiting.size() == 0 then
      _when_done()
    end

  be _done(cpu: Cpu tag) =>
    _waiting.unset(cpu)
    if _wait and (_waiting.size() == 0) then
      _when_done()
    end

I should also add that --ponynoblock still seems to remove "segmentation fault" from the set of possible outcomes, but doesn't change the termination behavior.

@derrickturk can you open an issue for "early termination", that sounds like a distinctly different problem for the probably cycle detector related segfault. I haven't paid a lot of attention to what you have reported for it, a good fresh summation on its own would be helpful.

I have a hard time reproducing the segfault issue using the last example. I have a very easy time reproducing the "early termination" issue. I almost never get output.

Using the code on my cd-contacted-bad branch, i am unable with either example to reproduce the segfault which I was hopeful would be the case as I fixed all race conditions I could find in interactions with the cycle detector.
@derrickturk very much, please do open a new issue for the termination problem and limit the information there-in to it.

So the "early termination" problem:
there's no printing going on as at the time the program ends, the waiting count is still rather high. And it is "all over the place".
Here's some output from my modified version.

Next up is to determine if bug in pony code or the runtime. I'm assuming runtime but I want to rule out the pony code first.

@redvers suggested during office hours to try running with --ponymaxthreads=1 and lo and behold, no "early termination". Why? Still unknown.

OK so as stated, the segfault is fixed by forthcoming changes.
The "early termination" is a "bug" in the program. The program works with a single ponythread because the message ordering with a single thread and how things are scheduled matches the sequential thinking behind the code. However, with more than 1 thread, the code is no longer sequential and invariants that the code doesn't state do not hold.
In particular there is an expectation that:

for every CpuWaiter.wait call to add a cpu to the set
there will be a corresponding CpuWaiter._done call

However this will only be true with a single thread where you happen to have our scheduling rules (which with a single thread will satisfy most expectations for sequential program order).
However, with more than 1 thread, things can get "out of order" from what the program seems to expect to happen. In particular, at the moment that:
    cpus(0)?.send(0)

is first called, our first cpu starts its "steps processing" almost immediately. With a single thread this is not the case and everything is "ordered as expected".
When the first cpu "starts its processing", then there are orderings where _wait can be called to add messages to the cpu set, and the cpu in question will already reached step 3 before it has received and processed the "subscribe_halt" message. This means that there will no longer be a 1 to 1 wait to done _ratio. What happens then is that when the cpu is at step 3, the on_halt matches fails because _on_halt is still None and no _done message is sent which means that this check will not pass:
  be _done(cpu: Cpu tag) =>
    _waiting.unset(cpu)
    if _wait and (_waiting.size() == 0) then
      _when_done()
    end

because _waiting.size() will never be able to reach 0.
For the program to work as expected the following that only happens with 1 thread MUST happen:
within the for iter in Range(0, 1000) do loop... we need this to happen:

waiter.wait(cpus(cpus.size() - 1)?) which causes to be on scheduler 1
cpus(0)?.send(0) which causes the corresponding cpu to be next in line on scheduler 1

then we have:
      for cpu in cpus.values() do
        cpu.run()
      end

which means that while main is still running...

cpu 0 that is already on scheduler 1 will get a run message
cpu 1 will be added the end of scheduler 1's queue because of the run message
cpu 2 will be added the end of scheduler 1's queue because of the run message
cpu 3 will be added the end of scheduler 1's queue because of the run message
cpu 4 will be added the end of scheduler 1's queue because of the run message

because of this ordering and corresponding orderings based on the scheduler implementation, there can never be the mismatch in set/unset calls in the waiter.
however, in a concurrent world, if we have 2 threads... the moment an actor hits scheduler 1's queue, it can be stolen by scheduler 2 and then, there are so many unknown orderings and all the race conditions in the code related to set/unset in the CpuWaiter can happen.
Note that with the deterministic scheduling with 1 thread, that 4000 times "_on_halt" won't be set, but that is ok, because it means that 1000 times it will be set and there's a corresponding 1000 wait calls that were made from main.
The easiest fix for the problem is to move the setting of on_halt to before the first time it needs to be used, so here in main:
      try
        cpus(cpus.size() - 1)?.subscribe(mk)
        waiter.wait(cpus(cpus.size() - 1)?)
      end

you have access to the waiter and can do the subscribe_halt call on the last item in cpus at that time and give it the waiter object that is in scope.

#4251  fixes the segfault issue.


Add optional depth parameter to simulate debug control?

I'm implementing AI in a not-so-simple game that depends quite a bit on chance until later in the game. Simulating the beginning moves takes longer than I have patience for and is unnecessary. Would adding the depth as an optional argument to the simulate command in the debug panel be something you would be interested in?
Also, I wanted to mention that I really appreciate this library. It's made implementing a board game I enjoy super easy.

Yes, allowing some knobs for the AI on the debug panel sounds like a great idea!
Also, take a look at the AI implementation. It's still a work in progress and not documented well, but there are ways to specify "objectives" that allow propagating scores from shallower states that might also help you.

Ok, I have implemented a crude iterations argument to the simulate command. As I got more into the source code though I realized I mistook Simulate in bot.js (used just for tests as far as I can tell) with the simulate command which actually calls step for so many iterations.
It looks like for what I want to do, limit the depth, I just need to instantiate my own MCTSBot with the depth I want and use that instead of the default MCTSBot.
So, if modifying the iterations and timeout is something you'd be interested exposing in the debug panel then I could clean it up and make a PR? Or did you have something else in mind?

I think exposing some generic options on the debug panel that are passed to the bot constructor would be great!
We just need to make sure that they're not specific to any one type of bot.
Maybe just an opaque JSON object that's sent to the constructor? We could also build a mechanism to automatically generate fields on the UI based on annotations in the bot's source code, but that's more complicated.

Closing as this was added in v0.35.0.


Add Testing Coverage

add test coverage tool such as istanbul
add missing tests to achieve complete coverage
add Codacy integration
add coverage badge to README

added istanbul for jest, codacy is done via PR for now and badge added to README


Personal Messaging System - Improvement Thoughts?

I have been thinking about this for sometime now, the personal message system could be improved by simply using the data we have in a better way.
What I mean is currently you only ever see a single message in the view. If you are having a conversation with a few people you very quickly loose track of what you said to who and it is hard work looking back though old messages when you are limited for time.
What would be better for users is if the previous messages between users were shown in a timeline. This is simple you select all rows from the database that have both users id's and sort them by the time sent and you have a message system more like a mobile phone app that people are more likely to engage with.
Also each reply has re added to the subject each time so you end up with Re: re re re re this is resolved with a string replace upon submit. I have done some of this already and in the process of doing the rest but just wanted to know what other people's thoughts on this are?

I will share something related to this in a few days time :)

Yeah, it is better as a conversation.

Suggestions:-

New mail need sound notification
Conversation view
Option to send/receive images.

Example 1
Mail inbox view

Conversation view

Example 2 - Morden

The mail function needs sound notification for new mails.
Can there be notification settings too?

All the above are suggestions only.
Add your own ideas and styles and what is doable.

Was this added?   This is a good thing to have


example config for using mocha with babel?

I'm trying this out but I'm having problem setting up a test of multiple files that is transformed by babel.  There's a sample browserify example, however I was wondering how to setup multiple files?  On that example it assumes you only have one test file.

just browserify all the files

how @Sinewyk example only shows to browserify one file?

Usage: browserify [entry files] {OPTIONS}
By default you can simply pass multiple entry files, so simply
browserify entry1.js entry2.js entry3.js > bundle.test.js or whatever.
And in your case there's a good chance you can simply do something along those lines (adapt to suit your needs)
browserify ./**/test/*.spec.js -o ./test/bundle.test.js

i tried that it was very laggy

Then your issue is now different, it works but it's slow. If you want it to be faster, you would have to do it yourself ^^.


BUG: React/JSX errors on /get-access

Describe the bug
React/JSX errors on https://www.cleanandgreenphilly.org/get-access
To Reproduce
Steps to reproduce the behavior:

Go to https://www.cleanandgreenphilly.org/get-access
Open Console

Expected behavior
No Errors

Hi @brandonfcohen1, I'd like to take on this ticket!


Godot 4 build with doubles crashes Mesa RADV Radeon drivers on launch (works with AMDVLK)

Godot version
4.0.dev (499eec1)
System information
Arch linux with amd 5700 xt
Issue description
Crashes with the following backtrace
./bin/godot.linuxbsd.double.opt.tools.64                                         INT ↵
Godot Engine v4.0.alpha.custom_build.6a51999b7 - https://godotengine.org
ERROR: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
	loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
	Objects - 1
		Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle<PHONE_NUMBER>5344
   at: _debug_messenger_callback (drivers/vulkan/vulkan_context.cpp:157)
Vulkan API 1.2.203 - Using Vulkan Device #0: AMD - AMD RADV NAVI10

================================================================
handle_crash: Program crashed with signal 8
Engine version: Godot Engine v4.0.alpha.custom_build (6a51999b7f4d9f7b1f950d7a655a464f28542318)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x42560) [0x7fc37ca18560] (??:0)
[2] /usr/lib/libvulkan_radeon.so(+0x1ed79e) [0x7fc37abd379e] (??:0)
[3] /usr/lib/libvulkan_radeon.so(+0x1eef5e) [0x7fc37abd4f5e] (??:0)
[4] /usr/lib/libvulkan_radeon.so(+0x1ef058) [0x7fc37abd5058] (??:0)
[5] ./bin/godot.linuxbsd.double.opt.tools.64(+0x1a24537) [0x55fddfb84537] (??:0)
[6] ./bin/godot.linuxbsd.double.opt.tools.64(+0x3b54aef) [0x55fde1cb4aef] (??:0)
[7] ./bin/godot.linuxbsd.double.opt.tools.64(+0xd49267) [0x55fddeea9267] (??:0)
[8] ./bin/godot.linuxbsd.double.opt.tools.64(+0x3b19830) [0x55fde1c79830] (??:0)
[9] ./bin/godot.linuxbsd.double.opt.tools.64(+0xd23282) [0x55fddee83282] (??:0)
[10] /usr/lib/libc.so.6(+0x2d310) [0x7fc37ca03310] (??:0)
[11] /usr/lib/libc.so.6(__libc_start_main+0x81) [0x7fc37ca033c1] (??:0)
[12] ./bin/godot.linuxbsd.double.opt.tools.64(+0xd3fdf5) [0x55fddee9fdf5] (??:0)
-- END OF BACKTRACE --
================================================================
[1]    77475 IOT instruction (core dumped)  ./bin/godot.linuxbsd.double.opt.tools.64

With a debug build
Vulkan API 1.2.203 - Using Vulkan Device #0: AMD - AMD RADV NAVI10

================================================================
handle_crash: Program crashed with signal 8
Engine version: Godot Engine v4.0.alpha.custom_build (3f3826edb8a3b5ea137dbe5a167e3b9336181551)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x42560) [0x7f211aa7d560] (??:0)
[2] /usr/lib/libvulkan_radeon.so(+0x1ed98e) [0x7f2118c7798e] (??:0)
[3] /usr/lib/libvulkan_radeon.so(+0x1ef14e) [0x7f2118c7914e] (??:0)
[4] /usr/lib/libvulkan_radeon.so(+0x1ef248) [0x7f2118c79248] (??:0)
[5] RenderingDeviceVulkan::render_pipeline_create(RID, long, long, RenderingDevice::RenderPrimitive, RenderingDevice::PipelineRasterizationState const&, RenderingDevice::PipelineMultisampleState const&, RenderingDevice::PipelineDepthStencilState const&, RenderingDevice::PipelineColorBlendState const&, int, unsigned int, Vector<RenderingDevice::PipelineSpecializationConstant> const&) (??:0)
[6] RendererCanvasRenderRD::RendererCanvasRenderRD(RendererStorageRD*) (??:0)
[7] RendererCompositorRD::RendererCompositorRD() (??:0)
[8] RendererCompositorRD::_create_current() (??:0)
[9] RendererCompositor::create() (??:0)
[10] RenderingServerDefault::RenderingServerDefault(bool) (??:0)
[11] Main::setup2(unsigned long) (??:0)
[12] Main::setup(char const*, int, char**, bool) (??:0)
[13] ./godot.linuxbsd.double.tools.64(main+0x134) [0x55be1781eb3d] (??:0)
[14] /usr/lib/libc.so.6(+0x2d310) [0x7f211aa68310] (??:0)
[15] /usr/lib/libc.so.6(__libc_start_main+0x81) [0x7f211aa683c1] (??:0)
[16] ./godot.linuxbsd.double.tools.64(_start+0x25) [0x55be17214655] (??:0)
-- END OF BACKTRACE --
================================================================
[1]    74981 IOT instruction (core dumped)  VK_ICD_FILENAMES= ./godot.linuxbsd.double.tools.64

If more info is needed, please tell me how. I'll need some hand holding.
Steps to reproduce
Build script: scons -j12 warnings=all werror=yes platform=linuxbsd tools=yes tests=no production=yes float=64 target=release_debug
Minimal reproduction project
No response

Not sure if it affects the crash but regarding the
loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7 part.
I was hitting that also on arch and happened after a vulkan-icd-loader update. To fix I had to downgrade to version 1.2.199-2 from the pacman's caches.
After the downgrade it disappeared from the warning in Godot 4.  Could reproduce it without running godot though - just by running vulkaninfo.
If that affects the crash then the issue is probably not godot related, but again, it may be unrelated to the crash.

It is a warning in the driver loader. It will go away when mesa catches up.
It (should be) is unrelated to the crash
On Thu, Feb 24, 2022, 2:40 PM Nikolaos Katomeris @.***>
wrote:

Not sure if it affects the crash but regarding the
loader_scanned_icd_add: Driver /usr/lib/libvulkan_radeon.so supports
Vulkan 1.2, but only supports loader interface version 4. Interface version
5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7
part.
I was hitting that also on arch and happened after a vulkan-icd-loader
update. To fix I had to downgrade to version 1.2.199-2 from the pacman's
caches.
After the downgrade it disappeared from the warning in Godot 4. Could
reproduce it without running godot though - just by running vulkaninfo.
If that affects the crash then the issue is probably not godot related,
but again, it may be unrelated to the crash.
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/58333#issuecomment-1050332467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5V52CSTTZ66G4GZ7VJZ3U42XVJANCNFSM5O3VUC4Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

I am also experiencing this issue.
Ubuntu 21.04
Ryzen 1700x
Radeon RX580

I am also experiencing this issue.

Custom build of  #767f8fb
The latest one. I just compile it every day.

I tried to switch to amdvlk. It's working now.
I guess it's driver's issue.

I've tested Godot build with double on two other different machines.
I got the same issue in them all.
After switch to amdvlk everything works.
Ubuntu 22.04 - ryzen 5 5600x - Radeon RX 6500
Ubuntu 22.04 - ryzen 7 3700x - Radeon RX 580

Please report this to Mesa developers, as this is a third-party driver issue.

I have a feeling this is caused by us using real_t with shader structs. While working on particles I noticed a few Uniform Buffers had been changed from floats to real_t, which would cause alignment issues on doubles builds.
Stuff like this:
https://github.com/godotengine/godot/blob/2f0d3d5424c393c756f4cd5cac26287c95aaf4fe/servers/rendering/renderer_rd/storage_rd/particles_storage.h#L100
scale was turned into a real_t on the engine side, but it is still a float in the shader.
Of course, without an MRP I can't say whether this contributes to the crash or not, it is just a hunch I have

Is this the same issue as https://github.com/godotengine/godot/issues/67575?
If so check the linked Mesa bug report and feedback from upstream devs.

I've tried use driver from Oibaf repository:
ppa:oibaf/graphics-drivers
It works. I believe godot was some bug with vulkan but I also believe there is a issue from vulkan side.

According to https://gitlab.freedesktop.org/mesa/mesa/-/issues/7528#note_1619087, Mesa 22.3 should fix this by supporting 64-bit vertex buffer formats.

Could not be done check to inform the user that need a more up to date driver? Just crashing could be confusing.


Feature: Typescript code generation framework free template

Hi,
Once again thanks for this great tool.
I would like to know if it could be possible to implement a framework independent typescript code template. I would like to use compiled code on server side without the framework that I don't need.
An even better solution in my case would be to be able to generate plain javascript (ES6) as I'm not using typescript currently on my server side, but I suspect this would be a lot of extra work.
Thanks a lot.

I think ES6 supports promises and fetch. Isnt the Fetch template sufficent (except that it is TypeScript)?

Hi,
thanks for your fast response, I though this was related to Aurelia as in the project description it's marked : window.fetch API and ES6 promises, Fetch (use this template in your Aurelia project).
But I think you're right that should work according to what I can see, I'll give it a try tomorrow.
Thanks.

We could create a fetch template without ts typings and you'll have your es6 code...

Hi,
It's working thanks. Would be great for me to have js only version, but I can deal with it.
Thanks.

Can we just strip away the TypeScript typings and it would be proper ES6 JavaScript?

I don't think this will be enough, I don't think ES6 support the class declaration syntax, exports does not work the same way too.

I think ES6 supports class and export (but no annotations, which are not used in the fetch tpl).
The question is whether to copy the tpl, extend the existing one or transform the output..


add buildspec

add buildspec.yml

@beedua Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@beedua use your own fork for experiments.


Clarify epoch definition in spec (plus other possible errors/suggestions)

Hello
I am new to github therefore please forgive any mistakes in advance.
The spec declares the epoch as totally user defined. However it also makes reference to the UNIX epoch as if it is guaranteed to be the epoch a snowflake uses. I assume the first idea, that the epoch is totally dependent on the user/application and has no default, is correct and that the following sentences should be changed to emphasize the idea of a generic epoch:

This is done by shifting the timestamp 22 bits to the right, and adding the epoch to the result in order to get the nanoflake's timestamp in milliseconds since the UNIX epoch.
The epoch is a UNIX timestamp in milliseconds. The only requirement is that the epoch must represent a time in the past relative to the generator's current time.

Additionally: Does the spec forbid (or is it meant to forbid) the use of monotonic time? If not, should using monotonic time perhaps be recommended? It would simplify the practical implementation of checking for clock skew, as far as I understand it.
I created a new issue for this rather than including it in my fork (which will eventually be a pull request) as it involves changing content/meaning vs only formatting.

Additionally: The term "globally unique" is definitely not correct here, at least in a literal sense. Nanoflakes are specifically scoped to a single application and can only be guaranteed to be unique within it. They are not GUIDs. It should perhaps be replaced with "unique" or "unique within the application" etc.

Hello!

The spec declares the epoch as totally user defined. However it also makes reference to the UNIX epoch as if it is guaranteed to be the epoch a snowflake uses. I assume the first idea, that the epoch is totally dependent on the user/application and has no default, [...]

That is indeed correct! Although a global epoch would be nice, it would lock all users to a 69-year expiration date. So per spec, the epochs are application-dependant.

[...] the following sentences should be changed to emphasize the idea of a generic epoch: [...]

I'm rather neutral regarding the formatting. If it emphasizes the generic epoch idea, you have my approval!

Additionally: Does the spec forbid (or is it meant to forbid) the use of monotonic time? If not, should using monotonic time perhaps be recommended? It would simplify the practical implementation of checking for clock skew, as far as I understand it.

The specification does not forbid nor it recommends monotonic time. If you have access to a monotonic clock which can be used to give UNIX timestamps, it can be used to implement a simpler algorithm. Otherwise, the specification already assumes you have a (most-likely) non-monotonic clock.

Additionally: The term "globally unique" is definitely not correct here, at least in a literal sense. Nanoflakes are specifically scoped to a single application and can only be guaranteed to be unique within it. They are not GUIDs. It should perhaps be replaced with "unique" or "unique within the application" etc.

In hindsight, you're correct! Nanoflakes definitively aren't GUIDs and therefore the term "globally unique" shouldn't be used. Replacing it would definitively be correct!
You're free to and more than welcome to open one or more PRs with suggested formatting and/or content changes!

Thank you for the feedback! I will make the changes and then make a PR.


linter-registry.js:137[Linter] Error running pycodestyle Error

Help!!!
at ChildProcess.<anonymous> (C:\Users\JORGE SIQUEIRA\.atom\packages\linter-flake8\node_modules\atom-package-deps\node_modules\sb-exec\lib\index.js:56:20)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:493:12)

As the error message (and readme) states, you need to install pycodestyle first 😉. You can find instructions for that here: https://pypi.python.org/pypi/pycodestyle.

I already installed!

I notice you have "virtualenv" shown in the path of the Explorer window. To work with that you either need to explicitly put the full path to pycodestyle in the settings (eg C:\foo\bar\virtualenv\virtual_1\Scripts\pycodestyle), or you need to launch Atom from a terminal window where that virtualenv is active (using atom .).

Thanks, started Atom from a terminal window.

I don't speak english. I'm using google translate, so it may have grammar errors.
Pycodestyle has run without any error, but I have seen some videos about flake8 and pep8 (pycodestyle) and how they should be working and although they have no error it seems that they do not work. Have some way to see if they are installed properly.
Thank you.

Try running them from the command line. You need a file that produce pep8 errors. Then try with this file in Atom. You should get the same errors. If you do not get errors on the command line, you should get errors in Atom. If you get errors on the command line, you should have the same errors in Atom.

Marking as closed due to a lack of response, if you are still having problems feel free to reopen this!

I understand this is closed, as well as it includes flake8, but I am getting errors and this seemed like the most similar issue:

I have already pip install pycodestyle here are the current packages I have relating to linting:

The only linter that works so far is pyflakes, and I do not know why.


Icon is off center in fields with icon example (Safari, Firefox, Chrome)

Can't replicate this in version 2. Please confirm this is version 2 and not version 1.0.3

This has something to do with the iframe, not the actual code.

We'll be updating the way we do our documentation.


Add support for javadoc's --release option

Just like javac, javadoc also become a --release option, to avoid issues like https://bugs.openjdk.java.net/browse/JDK-8212233. There is already #2510, but it seems to focus on javac. Hence I created this issue for javadoc.
Current workaround:
if (JavaVersion.current().isJava9Compatible()) {
	tasks.withType(Javadoc) {
		options.addStringOption('-release', javaMajor)
	}
}

I believe it's still good feature to add


Source code was not found for app:///main.jsbundle

OS:

[ ]  Windows
[x]  MacOS
[ ]  Linux

Platform:

[x]  iOS
[ ]  Android

Output of node -v && npm -v && npm ls --prod --depth=0
v6.12.1
3.10.10
<EMAIL_ADDRESS>/Users/dengwanc/Projects/maimai_react_native
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Config:
<EMAIL_ADDRESS>{
    release: '2da95dfb052f477380608d59d32b4ab9',
}).install();

I have following issue:
react native sentry source map JUST not working !!!
my upload script
sentry-cli --auth-token 27d37b4efd73439d820f02561e4507ca7d917ee771f84ed1949148137c3fb9a3 \
--url http://sentry.mm.taou.com \
releases -o sentry -p react-native files \
2da95dfb052f477380608d59d32b4ab9 upload-sourcemaps \
--rewrite --validate main.jsbundle.map

I GOT THIS IN Senry UI ，I am SO confused NOW
Source code was not found for app:///main.jsbundle
{
  "url": "app:///main.jsbundle"
}

@HazAT Downgrading the compileSdkVersion 26 and buildToolsVersion '26.0.0' breaks other libraries like lottie-react-native and react-native-vector-icons. I am unable to trigger a build from the command like or Android Studio. However if i increase the version directly in the Sentry SDK using Android Studio to 26 i am able to create the build but no information is present int he logcat.

@anandprabhu Sorry, with a reproducible case I can't do anything.
It must be something with your setup, all I can say is that the native android package isn't running in your project, why?
For that, I would need to see your project to help you debug it.

@anandprabhu Can you check if your MainApplication.java has these two lines:
...
import io.sentry.RNSentryPackage; // < --------------------
...
public class MainApplication extends Application implements ReactApplication {
    ...
    @Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
          new MainReactPackage(),
          new RNSentryPackage(MainApplication.this) // <------------------------------
      );
    }
    ...

@HazAT The MainApplication.java was missing the lines you had mentioned. Once i added the same it works fine now and able to see the mapping. But it seems to be showing it in a wrong line-number though.

@anandprabhu Your uploaded source map should do this correctly.
Keep in mind, old events will not get symbolicated only new ones.
Release and Dist have to match your artifacts.
Also, there is a bug in react-native itself facebook is aware of that line number may be wrong for android builds ref:
https://github.com/getsentry/react-native-sentry/issues/258
https://github.com/bugsnag/bugsnag-react-native/issues/142
https://github.com/facebook/react-native/issues/6946
I am closing this issue now since it's already hard to follow.
If anyone still having an issue with this, please consider creating a new issue with a reproducible case.
It seems like the issue is the linking process of react-native where it's not able to patch MainApplication.java.

@dengwanc i am also facing this issue brother not able to see the line number and only seeing this :
Source code was not found for app:///index.android.bundle Collapse
{
"url": "app:///index.android.bundle"
}
dont know what are the issues under lying.


Calling gridModel.clear() does not clear summary row contents

Loading a grid with treeMode: true, showSummary: true, and store.loadRootAsSummary: true fails to clear the summary row when the grid store is cleared via gridModel.clear() or the entirely equivalent gridModel.loadData([]).

Would like to add summary row support to our Admin > Tests > Grid tab to test and resolve this using Toolbox.


Header logo overlap close button in responsive

Describe the bug
Responsive header shows DXC logo overlapping the close button.
To Reproduce

Use default header.
Use it in responsive version.
Open the menu.
DXC logo overlaps close button.

Expected behavior
Should not overlap.
Screenshots

Add labels
Header, DXC logo, overlap.

This problem is related with the CDK site. The content is not responsive and affects the header.
Closing issue because is not related to a component.


Fix/daily 0907

支持一个新的事件挂载类型（source type）：canvas，专门挂在图表 canvas 上，目前用于挂载 pointerout 事件（VRender 的 pointerout 事件内部用 pointermove 实现，不能满足判断鼠标是否移出图表的要求）。用到 pointerout 事件的地方也做了相应修改和逻辑简化，如 tooltip 和 crosshair。可以彻底解决 tooltip 和 crosshair 残留的问题

[中文版模板 / Chinese template]
🤔 This is a ...

[ ] New feature
[x] Bug fix
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Enhancement feature
[ ] Refactoring
[ ] Update dependency
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Release
[ ] Site / documentation update
[ ] Demo update
[ ] Workflow
[ ] Other (about what?)

🔗 Related issue link
close #862, #839

🔗 Related PR link

🐞 Bugserver case id

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self-Check before Merge
⚠ Please check all items below before requesting a reviewing. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] TypeScript definition is updated/provided or not needed
[ ] Changelog is provided or not needed

🚀 Summary
copilot:summary
🔍 Walkthrough
copilot:walkthrough

合并到 1.4.0 吧


Example Project

I like the library and the documentation is OK, but I am really missing examples and recipes.
Right now I am stuck on how to ensure that on a put that it fails if the ID already exists and allows me to retry with another randomly generated id. I assume that I should use some expression, but can't find an example or recipe.
I'd love to see recipes or sample project that show examples of how this code looks like, this would be very helpful.

That totally makes sense. I could set up a simple "usage examples" page at the top level of the repository documentation.

I could help with that. I'm building a repository pattern with it, based on DDD directly from the book. My BDD cases could be use as recepies, besides in the majority be using just a little of the resourses form this project.

Documentation is preliminary - impossible so far to use in a real project.
Is there a working example for basic objects, embedded objects etc. with different types across basic CRUD and Queries with conditional expressions?

I having using for the past months @digitaldivvy .

Yep - this library is great. We currently have a multiple services in production using it, and it's working great for us.

ditto - awesome work aws!
On Thu, Nov 15, 2018 at 4:06 AM acheronfail<EMAIL_ADDRESS>wrote:

Yep - this library is great. We currently have a multiple services in
production using it, and it's working great for us.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/dynamodb-data-mapper-js/issues/76#issuecomment-438968393,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX_PG8BR57X9R9iwtpq39q69uj21RfLBks5uvS6EgaJpZM4VIUGL
.


Cursor blinks when terminal is continuously being fed data from stdout.

Environment
Windows build number:  10.0.18363.720
Windows Terminal version: 0.9.433.0

Steps to reproduce
Run the following batch file using cmd.exe within Windows Terminal
@echo off
:loop
echo a
goto loop

Expected behavior
Cursor should not blink, like in conhost.exe.
Actual behavior
Cursor is blinking

/dup #1087