pgwire: Send a crate_version ParameterStatus to clients

For clients it may be useful to know that they're communicating with
CrateDB instead of a PostgreSQL instance.
For example to adapt the server capabilities.
One such client is asyncpg, see https://github.com/MagicStack/asyncpg/issues/87

Codecov Report

Merging #6476 into master will decrease coverage by 0.08%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #6476      +/-   ##
============================================
- Coverage        83%   82.91%   -0.09%
+ Complexity    13077    13069       -8
============================================
  Files          1499     1499
  Lines         48590    48591       +1
  Branches       5870     5870
============================================
- Hits          40330    40291      -39
- Misses         5492     5531      +39
- Partials       2768     2769       +1

Impacted Files
Coverage Δ
Complexity Δ

...crate/protocols/postgres/PostgresWireProtocol.java
85.97% <100%> (+0.05%)
37 <2> (ø)
:arrow_down:

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-39.14%)
4% <0%> (-5%)

...ration/aggregation/statistics/moment/Variance.java
66.66% <0%> (-33.34%)
5% <0%> (-2%)

...ion/aggregation/impl/GeometricMeanAggregation.java
59.09% <0%> (-21.22%)
11% <0%> (ø)

...peration/aggregation/impl/VarianceAggregation.java
64.7% <0%> (-15.69%)
11% <0%> (ø)

...aggregation/impl/StandardDeviationAggregation.java
64.7% <0%> (-15.69%)
11% <0%> (ø)

core/src/main/java/io/crate/types/ShortType.java
80.76% <0%> (-11.54%)
16% <0%> (-3%)

...crate/executor/transport/TransportShardAction.java
76.31% <0%> (-10.53%)
8% <0%> (-1%)

...on/projectors/sharding/ShardingUpsertExecutor.java
89.02% <0%> (-4.88%)
16% <0%> (ø)

...in/java/io/crate/breaker/RamAccountingContext.java
81.66% <0%> (-3.34%)
20% <0%> (-2%)

... and 23 more

Continue to review full report at Codecov.

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


Fix Makefile.darwin syntax error

When running make in macOS, the following is seen:
% make build
Makefile.darwin:18: *** missing separator.  Stop.

% make
Makefile.darwin:18: *** missing separator.  Stop.

Pull requests:

https://github.com/Senzing/go-rest-api-service/pull/57


[misc] Update baseline and steps for webmanu-system-android-tests

Impacted TCs num(approved): New 0, Update 4, Delete 0
Unit test Platform: Crosswalk Project for Android 17.46.448.0
Unit test result summary: Pass 4, Fail 0, Blocked 0
https://crosswalk-project.org/jira/browse/XWALK-5223

LGTM


[Feature request]Calculate network calculations tools for Gluon.

Now gluon has a summary function for calculate total params for a network but don't have a tool for calculate network FLOPs(G).
Why needed this?

Model FLOPs could straightly measure a network inference speed.
Research needed.
Some of ops are widely used in many networks like conv, pooling, fc, bn
, relu, softmax.
Some of ops are looping many times and have different shape of feature_maps outpus, it's hard to calculate them manually.

But it's hard for calculating all of ops and actually not necessary(Some discussions here). So I partition them on demand.

Widely used in many networks and most commonly used.[urgent]

Conv2d/3d
Maxpool2d/3d
Avgpool 2d/3d
GlobalAvgPool2d/3d
FC
Relu, LeakyReLU, PReLU, Tanh, Sigmoid
BN
Softmax
RNN(basic rnn is just matrix multiplication, more complicated I don't know, this may need add if anything misses.)

Used somewhere but may not common.[not urgent]

Dropout
Conv1d, Maxpool1d, Avgpool1d
GlobalAvgPool1d
ConvTranspose1d/2d/3d (GAN may use this, but for now GAN don't care about FLOPs)
UpSampling bilinear/nearest
InstanceNorm, LayerNorm
L2Normalization

May only use once or little times in a model, their FLOPs may based on implement. Not hard to calculate manually.(May not to implement.)

ROIPooling
Atomic level operation(I didn't see anyone calculate them.)

Need not to implement

Loss functions.

Additional interface should be added to make users defined calculations themselves for manually defined Blocks.
Welcome to add if anything missing.
Welcome to suggest if anything wrong.

The Gflops is related to what kind of implementation is used and whether other optimization skills are applied.
For example, the computation of direct, GEMM-based and Winograd convolution is really different. And if the convolution is fused with BN/Relu/Sum, the calculation is also changed.
If you only care about how much OPs (Add, Mul, FMA) in the network at the runtime, I suggest to get it by profiling tools in a short time :)
Anyway, this is a good proposal for the analysis and I also like it.

@sandeep-krishnamurthy 's proposal maybe can cover your request with further improvements.
https://cwiki.apache.org/confluence/display/MXNET/MXNet+Operator+Benchmarks

@pengzhao-intel I mean GFLOPs is not consider special further improvements.It's just standard calculated amount.
For example, a Conv2d flops should be defined as:
Assume that the input and output and kernel are square.

O(conv2d-nobias) = K * K * Cin * M * M * Cout

M = output feature map side length
K = kernel size side length
C(in/out) = Channels in/out

Thanks this will be very useful.
Currently, I am working on per operator profiling to capture forward time, backward time, max memory allocated in phase 1 of my work. And, these uses different input shapes and option for each operator.
Intention of this work is - to catch any performance regression at operator level, ability identify hot computation paths in operator kernel for certain input shapes, and finally, derive insights like - In MXNet ArgMax is slower than Max operator for same operation.
Will that give a proxy for what you are looking for? However, this proposal is more fine grained and will be useful for planning optimization work.

@sandeep-krishnamurthy It's pleasure this may help you, but I just want a static analysis as I reply to pengzhao-intel, that's not complicated as you do.
The static analysis could help you evaluate network computing in the most fair way.


Added ubuntu 14.04 installation step for getting eng.traineddata file from google

Thanks for the supplementation.


fix: cast text data to datetime for freshness checks in Dremio

Overview:
This commit addresses an issue where freshness checks were not functioning correctly when applied to TEXT type data in Dremio. By default, freshness checks are intended to work with columns of data types TIMESTAMP or DATE.
To extend this capability to TEXT type data, a specific syntax is used to cast the column.
Issue:
The following syntax was supposed to cast a TEXT column to datetime for freshness checks:
`checks for dim_product:

freshness(createdat::datetime) < 1d `

However, this was resulting in an incorrect SQL query for Dremio: SELECT   COUNT(*),   MAX(collected_at::datetime) FROM dim_product
Resolution:
With the applied fix, the SQL query is now correctly formatted for Dremio: SELECT   COUNT(*),   MAX(CAST(collected_at AS TIMESTAMP)) FROM dim_product
This ensures that freshness checks are now properly applied to TEXT type data in Dremio, aligning with expected functionality.

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


L2CAP LE COC signaling part plus some additional fixes

In this pull LE COC signaling part has been implemented together with extensions to Bletiny app needed to test it. It is tested against BlueZ and PTS and works fine.
Note: This pull will not enable LE COC,  BLE_L2CAP_COC_MAX_NUM is 0
As you will notice I change a way of creating and sending signal commands. It is now done similar to what BLE_SM does. I plan to do same for l2cap update command.
Please have a look on API as I change it a bit comparing to what we discussed on mailing list. I found it more useful when writing Bletiny extensions.
In addition in this pull you can find some fixes and cleaning.

ah...just run newt test @apache-mynewt-core/net/nimble/host/test - so yes, I need to fix some test cases

Tests fixed


COPY - Retrun Detailed Result of the Opertaion

Hello,
How can I understand from the Vertica::Result object if the operation was successful or not?
Can it return the number of rows that were copied?
Thank you,
Yarden

Based on the parameters you give to the COPY query, it will succeed/fail based on the number of records it was not able to process.
If the query fails, the library raises an exception.
AFAIK, the library currently doesn't tell you how many records were successfully copied. This may be possible, I have never looked into it. It's unlikely I will work on this myself (I don't use Vertica anymore in my day job), but I will gladly accept pull requests that would add something here.


🚀 Feature: Peer Dependencies for Core Packages

🔖 Feature description
I'm trying to use Backstage in a pnpm monorepo. When trying to start the application after "fixing" some yarn specific checks with backstage-cli start, I run into the following error,
Cannot read properties of null (reading 'breakpoints')

After a bit of debugging, this is due to how pnpm is resolving the peer dependencies down to @material-ui/core and @material-ui/styles. For one we get a peer dependency on @types/react: 18.2.0 and the other @types/react: 18.2.79. I think this is due to some Backstage packages not listing @types/react in their peerDependencies as well as listing them in their dependencies.
🎤 Context
Supporting additional package managers has been mentioned in #20658, this is part of the path to that.
✌ Possible Implementation
Moving the types to dev dependencies and listing them in peer dependencies for Backstage packages.
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I wonder if just manually editing the pnpm-lock.yaml file could fix these issues temporarily. create a patch that could be applied.


Occlusion Query Interface

The interface I'd like to see would look something like the following;
QueryHandle createQuery();
void query(uint8_t,QueryHandle); //Utilizes vertex/index/decl attributes set within the DrawItem struct.
uint32_t getQuerySamplesPassed(QueryHandle);
void destroyQuery(QueryHandle);

Added occlusion queries, see example for usage: https://github.com/bkaradzic/bgfx/blob/master/examples/26-occlusion/occlusion.cpp#L227


dashboard POC

don't merge, it's just a POC regarding how we can send the client to server prop. And how our UI will look and how our UX will be, if we use it.

@ZubairImtiaz3, the tasks of "/dashboard" are now completed but client to server prop is still a POC as when our "/dashboard" page gets initially loaded from the server then you will see that how things are currently working and I have a solution for that.
So, just hi'me up w a text when you're available !

@MoazMirza-13  Closing this as per your comment in PR#2


CI: modify versioning to include prereleases

Changes:
Merge to main triggers official build.


Typescript Issue wrong maxNumberFiles typing

Describe the bug
A clear and concise description of what the bug is.
Typing Bug located on mediafilepicker.common.d.ts
To Reproduce
Steps to reproduce the behavior:
The typing used is Number which is supposed to be number, on which is returns an error on runtime
Expected behavior
A clear and concise description of what you expected to happen.
NativeScript Info(please run tns info):
Sample Code(please provide minimum code to reproduce problem):
Additional context
Add any other context about the problem here.

This error can be avoided because as a plugin won't require that file.

I don't know why you closed it but the error is there and I can't build nor run it because it gives the error.

Please write proper way with errors

Try making a new NativeScript-Angular project and use your documentation example on image picker.
I can't show you snippets rn. I'll upload them maybe later.

This error can be avoided because as a plugin won't require that file.

Typescript reads the files as necessary

Refer to the error above, manage to fix the problem by directly editing the interfaces inside the plugin

created a PR for the mentioned error above
https://github.com/jibon57/nativescript-mediafilepicker/pull/69

Any updates for this one?


Is this project dead?

No updates in some time, and dependencies are old versions of CF. Will this project be updated?

+1 on getting a status for ongoing development.

The author's github account has been deleted. So yeah, dead.


[BUG] Rancher container unable to resolve due to chart version for rancher-webhook

Rancher Server Setup

Rancher version: v2.7-head
Installation option (Docker install/Helm Chart): Docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:

Describe the bug

To Reproduce

On Ubuntu 22.04 instance install Rancher using docker

Result
Rancher container is stuck trying to find rancher-webhook chart and is stuck repeating the following error message in the logs
[ERROR] available chart version (1.0.5+up0.2.6) for rancher-webhook is less than the min version (1.0.6+up0.2.7-rc4)
2022/09/21 21:33:09 [ERROR] Failed to find system chart rancher-webhook will try again in 5 seconds: no chart name found

Expected Result

Rancher should run successfully

Validation Template
Root Cause
During the split between 2.6 and 2.7, there was a version of the webhook merged which is only available for 2.6 at the moment. 2.7 did not have a record of this chart, and was unable to deploy the webhook from the dev-v2.7 branch of the charts.
What was fixed, or what change have occurred
A new 2.7-specific version of the webhook was created (0.3.0-rc2) and made available in the 2.7 branch of the charts. In addition, rancher was configured to use this new version in the 2.7 branch.
Areas or cases that should be tested
Basic install of the rancher-webhook. You can validate this by making sure that there is a deployment in the local cluster for the webhook deployment (Workload -> Deployments -> Cattle-system namespace), and that the version is as expected 0.3.0-rc2.
What areas could experience regressions
There may be regressions in the webhook due to changes made in recent webhook RCs. However, this should not impact basic install functionality.
Are the repro steps accurate/minimal?
Yes. They are included here for convenience. (Note: these steps come from the issue - a quick test on my local did not produce the issue).

Run rancher
Observe an error message in the logs.

Notes
You will have to wait for a new 2.7-head to be built before you can test.

I have completed validations on this ticket and checked with Michel B : He is Ok with the test coverage and validation parts.
Covered below validations:

Rancher up with Docker -- rancher version v2.7-head
a. Rancher is Up
b. NO boot strap errors in the Logs related to chatversion(  root@localhost:~# docker logs  98ed085719b6  2>&1 | grep "available chart version" ) -- NO output
Rancher UI : I can see latest version of Webhook version ( rancher-webhook:2.0.0+up0.3.0-rc3 )
a. Observation : Ticket mentioned the version rancher-webhook:2.0.0+up0.3.0-rc2 , I checked with Mike and he mentioend there was another PR by kevin with rc3 and rancher-webhook:2.0.0+up0.3.0-rc3 is the latest version

Note : To making sure my tests are good --- I also reproduce this issue with v2.7-bb9012ee0e66196136403d026b9e38c757c06c8c-head
a. I saw boot logs has errors with "2022/10/03 20:39:06 [ERROR] available chart version (1.0.5+up0.2.6) for rancher-webhook is less than the min version (1.0.6+up0.2.7-rc4)"
b. Rancher UI (Webhook version) shows :   rancher-webhook:1.0.5+up0.2.6 (edited)


[5.8] Add multipolygonz type for postgreSQL

this feature need to make migrations easer and make type MultiPolygonZ throw it

This was merged into 5.8 instead of 6.0 by mistake.


Cross-compile improvements break the x86_64-fortanix-unknown-sgx target

I am using this crate to compile CMake projects using the x86_64-fortanix-unknown-sgx target to run under Intel SGX, and the latest update to this crate (v0.1.49) is causing the following errors that weren't present in the previous version:
  System is unknown to cmake, create:
  Platform/unknown to use this system, please post your config file on discourse.cmake.org so it can be added to cmake
  CMake Error: try_run() invoked in cross-compiling mode, please set the following cache variables appropriately:
     RUN_RESULT (advanced)
     RUN_RESULT__TRYRUN_OUTPUT (advanced)

I believe this is likely due to the changes made in https://github.com/rust-lang/cmake-rs/pull/158. These result in -DCMAKE_SYSTEM_NAME=unknown being passed to CMake, which it does not understand.
In my own crates I am able to fix this by overriding the variables manually as follows:
    if env::var("CARGO_CFG_TARGET_ENV").unwrap() == "sgx" {
        config.define("CMAKE_CROSSCOMPILING", "OFF");
        config.define("CMAKE_SYSTEM_NAME", "Linux");
        config.define("CMAKE_SYSTEM_PROCESSOR", "x86_64");
    }

But I might not always have the option of making this modification for any third-party crates.
I'm not sure what the correct fix for this would be, possibly just disabling the setting of the cross-compile variables when the x86_64-fortanix-unknown-sgx target is being used?

I have just realised that the main reason for this failure is that this particular CMake project uses try_run and this may not be an issue with projects that don't use try_run because the "System is unknown" messages are actually only warnings.
As such it seems I can also fix the error by explicitly setting the RUN_RESULT and RUN_RESULT__TRYRUN_OUTPUT as mentioned in the error message. Though I'm still not sure this should really be necessary for SGX as you're not really compiling for a different CPU so, unlike with a true cross-compile, the test binary being executed by try_run can just be run directly.

I don't see an obvious way of having this "just work" with try_run, but this may be inexperience on my part.
FWIW, I don't have access to the target so I won't fix it myself, but I'm certainly willing to take changes to avoid issues that we hit on more obscure targets (so long as they're reasonable and not extremely complicated for the sake of a single target). So I think it would be reasonable to tweak that logic for SGX's case.
This seems like it might be more to do with the specific CMake script you're using, though (although I'm not certain about this).

I don't see an obvious way of having this "just work" with try_run

Yeah, certainly there's no way of automatically setting RUN_RESULT and RUN_RESULT__TRYRUN_OUTPUT, or of automatically determining whether the test binary alone should be excluded from cross-compiling. In this specific case the binary is used for detecting which CPU extensions are available, so it should give the same results whether it's compiled for SGX or not, as long as it's on the same CPU, but that might not always be the case, and there might be projects using try_run with binaries that would produce misleading output if run outside of SGX.
I guess the only question is whether just unilaterally disabling cross-compiling and setting CMAKE_CROSSCOMPILING=OFF for x86_64-fortanix-unknown-sgx targets would be appropriate, or whether that could itself have unintended effects...? Despite being implemented as a target-triple, compiling code for SGX is not really a cross-compile in the typical sense.


[Current Registry] Fix Download of the Products functionality

The Download of the .csv files on the Products page doesn't work as expected now.

If user filters out the Products by cluster and/or ministry and tries to click the download button he gets an error:
Private Zenhub Image
Private Zenhub Image

If user first clicks Download button and then starts unchecking some of the fields to not include them in the downloaded document the download starts on every click. So If he needs to uncheck 5 fields the instant download of 5 versions of documents is made.
Private Zenhub Image

Definition of Done:

The .csv download is possible when products are filtered out by cluster and/or ministry
If user first clicks Download button and then starts unchecking some of the fields to not include them the download is not started until user clicks Download button again.

The team will wait for the New UI to be released and then check if this bug can be replicated in the New UI.

this bug is fixed the new UI. When the new UI is released, Artem will check if this is fixed and close this ticket as a cancelled one.


TopK sketching method ignores sketch_params kwargs

In sketch_boost.py
 elif sketch_method == 'topk':
            sketch = TopOutputsSketch(sketch_outputs)

should be
 elif sketch_method == 'topk':
            sketch = TopOutputsSketch(sketch_outputs, **sketch_params)

Nvm, I see now that sketch_outputs corresponds to the k parameter so there is no need for sketch_params


Update request: r2modman 3.1.44 → 3.1.45

Package name: r2modman
Latest released version: 3.1.45

Current version on the unstable channel: 3.1.44
Current version on the stable/release channel: N/A

[x] Checked the nixpkgs pull requests

Notify maintainers
@aidalgol @huantianad

Note for maintainers: Please tag this issue in your PR.
Priorities
Add a :+1: reaction to issues you find important.

This can be marked as solved


Improve Fuse.getxattr() with client side cached results

Is your feature request related to a problem? Please describe.
Fuse.getxattr() is called pretty often.

Describe the solution you'd like
Can save the result on fuse side.
add a configuration to decide the period that that information should be re-fetched from master.
Afer the configuration period passed, go to master to fetch info again and cache for future getxattr()
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Urgency
Explain why the feature is important
Additional context
Add any other context or screenshots about the feature request here.

@LuQQiu
Just a guess I don't know if it's reasonable. A batch of getxattr requests, requesting the parent node, may also have subsequent requests for child nodes (such as the ls command). If we get back the attr of multiple paths in one RPC request, we may reduce some RPC requests?

@yabola what i saw is a bunch of getxattr(/) operations without requesting child nodes.
I guess it's used to get the filesystem capacity

@LuQQiu I only see that mFileSystem.getStatus generates RPC request. with alluxio.user.metadata.cache.enabled, fuse  can cache the meta . Isn't it enough?


Resident bug

A resident tried to apply to the Utility Discount Program and got the attached error message. I don't know exactly where in the process it occurred, but the resident tried a few times and got the same error. This is the only resident I've heard from, so doesn't seem to be a wide-spread issue.
Screenshots
Attached

Waiting on AWS access for @gwendolyngoetz

Heard of another instance of this issue (on computer, Chrome, not during the outage on 2/25)

3/16 ORCA Opportunity program: "Oops…..and error occurred.  This exception has been logged with id 7n33879ep"

3/16 ORCA Opportunity program: "Oops…..and error occurred. This exception has been logged with id 7n33879ep"

I moved this to issue #2125


Julia definition is out of date

The Julia container definitions added in #450 use pre-built images (ghcr.io/julia-vscode/julia-devcontainer), but they have not been updated for almost half a year.
Therefore, the latest version of Julia is 1.6.3, but Julia on containers created using Julia's container definition is still version 1.6.1.
As mentioned in this comment https://github.com/microsoft/vscode-dev-containers/issues/154#issuecomment-768398690, updating Docker images requires a lot of effort, so I think it is worthwhile to stop using pre-built images and switch to a method where users build locally, similar to many other community container definitions.
Although there is a disadvantage that local builds take more time, I feel that there is also an advantage of being able to switch base images easily.

@davidanthoff @ThomasHagebols Do you have any future plans for the julia definition?

@fonsp Any thoughts?

@eitsupi @davidanthoff @ThomasHagebols @fonsp - At this point I suspect we may want to remove this definition from the repository since given we haven't had a response in a few months now. I worry about the impression it leaves current state even though it is marked as community.

The containers are all up-to-date. If we fall behind from time to time, it is extremly simple to add another version, see https://github.com/julia-vscode/julia-devcontainer/pull/10 for an example. PRs are always welcome! I don't think there is a need to change anything.

As I wrote at the beginning of this issue, I think that repository should be deprecated and the definition completely rewritten to allow users to easily do local builds.
If we switch from pre-built images to local builds, we will no longer have to worry about update delays, and users can choose any version of Julia (even development versions can be choosed, as requested in this issue https://github.com/julia-vscode/julia-devcontainer/issues/8 ).
Since it is very easy to install any version of Julia, it may be more convenient to add an installation script to the script library so that any Julia can be installed on base image like mcr.microsoft.com/vscode/devcontainers/base:debian.
There is also the problem that the build system of that repository only builds amd64 and does not support arm64.

I would suggest we wait with any change until https://github.com/julialang/juliaup is finished and the official way to install Julia. I expect that to be the case in a few weeks (months at most). That will change a lot of things about Julia deployment, and will open up a range of new options for this scenario here as well.
There are also some major benefits of the current structure, in particular for novice users: there is almost no complexity involved, the surface level stuff that they interact with looks extremly simple (essentially just the super simple devcontainer.json file). All the complexity of say the Julia project instantiation etc. is properly packaged away. If we were to put all of that into the template here, then adding the Julia devcontainer definition would add a lot of quite complicated code, which I think would not be desirable.
So, to be honest, I'm not too keen to change the current setup, I think it essentially works well. I can see that it would be nice to have more control for more advanced users, but maybe one way would be to just add another configuration template for those users, say Julia (custom) or something? I don't think it would be a good trade-off to make things more complex for everyone to make life easier for advanced users, they can presumably just figure things out themselves.

I think you should take seriously the fact that no contributor has shown up in over six months and you, the owner of the definition, have taken no action.
I really appreciate the great contribution you are making to Julia. However, maintaining Docker images over the long term involves a lot of work, and I don't think the current community is capable of maintaining that repository.
Pre-built images should be eliminated, especially if you care about beginners. (It's much easier for them to edit the Dockerfile in their hands than to send a PR)

However, maintaining Docker images over the long term involves a lot of work, and I don't think the current community is capable of maintaining that repository.

I don't follow at all. Literally one needs to add one number to one line in one file to add a new version, that is it. Everything else is fully automated. If someone doesn't know how to do it, open an issue or ping me. I am thinking about solutions how we can automate even that (as we have a number of places where we need to make that kind of one-line edit when a new Julia version is released, so I might just write a script for that and then that should be handled).

Pre-built images should be eliminated, especially if you care about beginners.

I disagree, I think the current solution is much easier for beginners than a template that drops a large and complicated Dockerfile into their workspace. I think one of the really good things about the current system is that it works really well for folks that don't even know what docker is.
I'm not sure what the right way to resolve this is. From the Julia extension for VS Code team's point of view I would prefer if we just kept things the way they are, but I guess at the end of the day it is MS' call?

I have been waiting for 3 months and unfortunately it seems that all I can do is close this issue.
I hope things will get better in the future, thanks.

@eitsupi Given no response here, should we remove the Julia definition from this repository in favor of yours?

I don't think anything should be changed. The images over at https://github.com/julia-vscode/julia-devcontainer are up-to-date and work.
I am the person creating Juliaup, which will become the default Julia installer soon (TM). Once that is officially rolled out, I will update the solution over at https://github.com/julia-vscode/julia-devcontainer to use that. But at the moment folks should not be pushed towards Juliaup for something official as it is still in a prerelease mode.

@Chuxel Of course I can provide a new Julia template like below, but if @davidanthoff sticks with the current one, all I can do is provide a Feature to install Julia.
{
	"image": "mcr.microsoft.com/devcontainers/base:debian",
	"features": {
		"ghcr.io/eitsupi/devcontainer-features/julia:0": {
			"version": "latest"
		}
	}
}

@davidanthoff

I don't think anything should be changed. The images over at julia-vscode/julia-devcontainer are up-to-date and work.

I think the situation is different now than it was a year ago. What is the reason for sticking with what is here and now outdated?
(ghcr.io/julia-vscode/julia-devcontainer relies on the deprecated script in this repository that are no longer maintained, so that is outdated, I think)
https://github.com/julia-vscode/julia-devcontainer/blob/1dc6fa02bb9fb9e2b856488146a664444039ad24/Dockerfile#L9

Given that the definition of Julia has become outdated again, it seems necessary to reopen this.

@eitsupi I just added 1.8.4. It was released during the holidays, so that means there can be a bit of a delay sometimes. One thing you could do that would be super helpful is to just open a PR against https://github.com/julia-vscode/julia-devcontainer/blob/master/.github/workflows/docker-publish.yml#L48 and add the version there, that is really all that is needed.
And as I wrote above, as soon as we have Juliaup more officially I'll do something more automatic.

@davidanthoff Thanks. But I am not talking only about the version of Julia that I am describing as outdated.
Could you answer to my question https://github.com/microsoft/vscode-dev-containers/issues/1114#issuecomment-1348534896?
If someone were to overhaul julia-vscode/julia-devcontainer, it would require a lot of effort and I don't have the bandwidth.
So I recommend giving up julia-vscode/julia-devcontainer and moving to a Dev Container Feature approach.

@eitsupi Alright, I finally caught up with the recent (well, not so recent) devcontainer changes, at least I know now what a feature is :) I think you are right, it seems we should deprecate the container things we have maintained over at the VS Code extension org and move to a feature instead.
I did just add a non-interactive option to the Juliaup installer, I think that was probably the missing piece to make that usable inside a feature, right? I'm going to test it for a few days before I roll it out to everyone.
What do you think about the following plan:

We migrate the repo you started for the feature over into the official julialang GitHub org. I think generally this is such an official piece that it would be best to have it there? I can handle that.
We move the feature over to use Juliaup. I can also help with that.
We deprecate the existing Julia VS Code extension container.

Actually, I'm realizing that the Julia feature right now is in a repo that has quite a number of other features as well. So, I guess my proposal then would be that we only move the Julia feature out of that repo and into a new one in the julialang org.

@davidanthoff Thanks for your reply!

I did just add a non-interactive option to the Juliaup installer, I think that was probably the missing piece to make that usable inside a feature, right?

Yes, I forget which issue, but I gave up using Juliaup (or juliainstaller) when I tried it a few months ago because the process of installing it required interactivity.
Things are much simpler if we can write the following process in a shell script.
install_juliaup # a function to install juliaup
su "${USERNAME}" -c "juliaup add ${JULIA_VERSION}"

I assume something like the following code that installs R via rig (R Installation Manager).
https://github.com/rocker-org/devcontainer-features/blob/5b1d9ba0c5af793f582fd161160856b4e48ca1ad/src/r-rig/install.sh#L314-L330

What do you think about the following plan:

I completely agree with your suggestion.
If JuliaLang could maintain Julia Dev Container Feature(s) and Dev Container Template(s), that would be great!
(FYI, I recently did the same thing with mamba-org. After I created a prototype of Dev Container Feature, it has now been transferred and is owned by mamba-org. https://github.com/mamba-org/devcontainer-features)

We move the feature over to use Juliaup. I can also help with that.

Since the Dev Container CLI has testing abilities, it would make sense to refactor after the juliaup has matured.

We deprecate the existing Julia VS Code extension container.

And, just as we would create a repository for Dev Container Features, we must create a repository for Dev Container Templates and migrate to the new templates using Dev Container Features.
Please check the R's case. (#1669, #1673)
In summary, for the new format, we need a repository based on https://github.com/devcontainers/feature-starter and a repository based on https://github.com/devcontainers/template-starter.
You could create these repositories and I could create the PR and port https://github.com/eitsupi/devcontainer-features/tree/main/src/julia to that and create the template prototype, or I could create these repositories and later transfer them to you and you could transfer them to JuliaLang or julia-vscode.
(A recent update added the ability to deprecate the Dev Container Feature so I can deprecate ghcr.io/eitsupi/devcontainer-features/julia after it is migrated.)

@eitsupi cool, this is all very helpful. I started with https://github.com/JuliaLang/devcontainer-features, do you want to take a look at that? Does that look good to you? The tests are nonsense, maybe you could migrate the ones you have over to there? At the moment I can't publish things because I'm waiting for a Julialang admin to allow public packages.
Does it make sense that we test the feature stuff first and the move to templates?

@davidanthoff Awsome!
I am wondering if we can specify which version to install.
For example, my Feature can install any version by specifying the following version.
installs the latest 1.6.X
"features": {
    "ghcr.io/eitsupi/devcontainer-features/julia:0": {
        "version": "1.6",
        "allowNonStableVersion": true
    }
}

installs the latest 1.X.Y
"features": {
    "ghcr.io/eitsupi/devcontainer-features/julia:0": {
        "version": "1"
    }
}

I am wondering if we can specify which version to install via juliaup at the first time.

Yes, the channel field can be used for that. One can pass any of the named channels like release, lts, beta etc, or any version like 1.8.2, or 1.8 or 1. All the pre-release versions should also work.
On one level the name version is nicer if one is really specifying a full version, but in the end the implementation is now just surfacing Juliaup concepts, and the name for this there is channel, so I thought it would probably make most sense to just stick with that?

Yes, the channel field can be used for that. One can pass any of the named channels like release, lts, beta etc, or any version like 1.8.2, or 1.8 or 1. All the pre-release versions should also work.
On one level the name version is nicer if one is really specifying a full version, but in the end the implementation is now just surfacing Juliaup concepts, and the name for this there is channel, so I thought it would probably make most sense to just stick with that?

That's great.
I think channel is fine since it is Juliaup's terminology.
It is possible that naming the Feature Julia (via Juliaup) like Ruby (via rvm) would be better as it would clarify the meaning of the term.
https://github.com/devcontainers/features/tree/main/src/ruby
It would be a good idea to document which versions are valid and to create test cases to verify that they work.

@davidanthoff I don't think this Feature is working yet, as evidenced by my additional tests. (JuliaLang/devcontainer-features#3)
install.sh is executed by the root user, but the user in the container (remote user) is not necessarily the root user.
So far Julia seems to be installed only for the root user.

Will be closed by devcontainers/devcontainers.github.io#278, thanks!


Settings panel fade

The settings panel fade is not very good, and not in line with the rest of the app.
We should add a slide or some sort, and make the time to display a lot shorter.

@alisaad673 @avaer
Can you plz check is it as needed.
PR https://github.com/webaverse/app/pull/2705


Question: Create lib project with examples

Edit: Im not able to generate any proyect with your sample function. Is "rapp" and "rbase" a project_sample function dependency? I dont really know the reason about this, but if I get this two projects, my command mchn enters in a infinite loop. Is there any form to avoid this dependenci?
THX!!!!!

Please see rapp project for reference how to do this.

Hi! Thx!
I did it, but I didnt found where did you call addProject_lib_sample in your project.
I got it, i got the samples working, but... working like this (not like rapp project).

I have to insert manually per sample the includedir. Can you help me with this?
Note: all the samples are inside "samples" folder with the correct names (01_Basic....etc)

You can check addLibProjects function as opposed to using addProjects_lib.
The first one picks up samples automatically by scanning directories and the second one just adds the library type project.

This is just amazing, really thank you!!!!

This is the solution that I found:

I dont know if its correct, but it works. Maybe other way to resolve this?

This shouldn't be needed as samples that are picked up by scanning dirs should have dependency added automatically. Check the addLibProjects function for details - if it doesn't work I'd suggest some debugging as I haven't had a problem like that.


Update manage-settings-with-mdm-for-surface-hub.md

Reboot the device immediately is now supported in intune

Thanks, Eric!

My Pleasure,
I love how easy it is to update the docs now 😊
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Jeanie<EMAIL_ADDRESS>Sent: Tuesday, March 6, 2018 6:27 PM
To<EMAIL_ADDRESS>Cc: Eric<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Update manage-settings-with-mdm-for-surface-hub.md (#528)
Thanks, Eric!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F528%23issuecomment-370860656&data=02|01||24a71d27bef24c83ec5008d5838780b4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636559540350629131&sdata=Ce5KU159uEI6MOKkXnHhUVj7n5DsNRDyP27l%2FDFv97Q%3D&reserved=0, or mute the threadhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAh-6EAM2zG4yGiSLHwG9IyMfkqZfJVMMks5tbsbwgaJpZM4ScfHP&data=02|01||24a71d27bef24c83ec5008d5838780b4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636559540350629131&sdata=9MHxWv%2FzKlbpHj1AkI4fBRe6gPEda9KOazytQT%2BqLB4%3D&reserved=0.


tether_drop_1.default is not a constructor only on tests

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows  10

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-rc.1
node: 6.9.1
os: win32 x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.1
@angular/compiler-cli: 2.4.9

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Repo: https://github.com/awerlang/tether-ng-cli
Run npm start. It runs okay.
Run npm test. A test fails with tether_drop_1.default is not a constructor.
The log given by the failure.

Normally this include a stack trace and some more information.

  Uncaught Error: Error in ./AppComponent class AppComponent - inline template:4:0 caused by: tether_drop_1.default is not a constructor

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

I don't think this is a CLI issue. I'd say you're importing this library incorrectly and thus it's not included in the unit test. Try adding it as a global script instead.

@filipesilva the workflow with ng start works correctly, and I don't need to include as a script. That's what makes me wonder how they have different results. Can you help explain why ng start works without addind as script?

I think it works with the import on ng serve because the app itself uses es2015 modules, while unit tests use commonjs modules. This is necessary because some of the tooling around unit tests wouldn't work otherwise.
Maybe you can also get it to work by using a different style of import, but it is heavily dependent on how the library is distributed. You can try these:
import * as foo from 'foo';
import {foo} from 'foo';

The safest way I've found for browser libs that are mostly meant to be included as script tags is to use the scripts array though.

Thanks @filipesilva! Knowing this difference is helpful, I guess I should be able to work around it now. Perhaps I'll re-package the library.


Install DefectDojo on OCI Virtual Machine (Oralcle Cloud)

I'm not able to install DefectDojo on OCI using user linux "opc"
II'm trying to install DefectDojo on Oracle Cloud. The Virtual Machiene created (VM) there is the following sw:

Oracle Linux 7.8
Tomcat 9.0.35
Java 8
OCI don't provide "root" credential for security reasons and you must use the user "opc" with "sudo". I executed the following steps:

downolad DefectDojo
I run "./setup.bash" and I chose the simple installation with defoult parameters.
After the request "ocp" password the install finished with the following error:

[sudo] password for opc:
Sufficient priveleges found, continuing installation
##########################################################################
ERROR: Unknown or NIY OS - exiting
##########################################################################
I repeted the istallation using "sudo":

sudo ./setup.bash
I run "./setup.bash" and I chose the simple installation with defoult parameters.

I receved the following error:
Install user is root, sudo access not required, continuing installation
##########################################################################
ERROR: Unknown or NIY OS - exiting
##########################################################################
I attach the log file for both installation.
Can you help me
Thanks
defectdojo.txt
defectdojo_sudo.txt

I don't think the OS you are trying to use is supported.

Oracle is not supported/tested, but the script can help you to install it by looking through its source and executing the steps and adapt them to oracle linux.
The easiest way to get started though is the docker-compose way.


Cluster setup failure: create glauth users

This looks like it might be a race condition between creating the ""groups table** and querying it while checking status.
I just saw an apparently transient setup failure while deploying this cluster to XCP:
%NC_ROOT%/devops/jefflill/home/tiny-xcp-cstor.cluster.yaml

Here's the last couple operations from the master-0.log:
*** STATUS: helm install glauth
----------------------------------------
START-BUNDLE: ./script.sh
*** START TEXT FILE: script.sh

set -euo pipefail

cd /lib/neonkube/helm

helm install glauth --namespace neon-system -f glauth/values.yaml --set priorityClassName=neon-app --set-string cluster.name="tiny-xcp" --set-string cluster.domain="8f5094bc7067c2ae.neoncluster.io" --set-string config.backend.baseDN="dc=8f5094bc7067c2ae\,dc=neoncluster\,dc=io" --set-string config.backend.database.user="neon_service" --set-string config.backend.database.password="eogRAd2LGJesSWcsimR2" --set-string users.root.password="db5tM2vietOyt7iwDOzL" --set-string users.serviceuser.password="T0xpfNArvvnmOh4gN0CN" --set-string resources.requests.memory="64Mi" --set-string resources.limits.memory="128Mi" ./glauth

START=`date +%s`
DEPLOY_END=$((START+15))

set +e

until [ `helm status glauth --namespace neon-system | grep "STATUS: deployed" | wc -l` -eq 1  ];
do
  if [ $((`date +%s`)) -gt $DEPLOY_END ]; then
    helm delete glauth || true
    exit 1
  fi
   sleep 1
done
*** END TEXT FILE
*** START TEXT FILE: __run.sh
#!/bin/sh

chmod 700 "script.sh"
./script.sh
*** END TEXT FILE
*** Uploading: /home/sysadmin/.neon/exec/785f40da-1e1b-45bf-87b0-503e0f28cd26/__bundle.zip
START: sudo bash -c 'if [ -f "/home/sysadmin/.neon/upload/__bundle.zip-4503e56e-11c9-48e6-b95c-36635b117fab" ] ; then rm "/home/sysadmin/.neon/upload/__bundle.zip-4503e56e-11c9-48e6-b95c-36635b117fab" ; fi'
END [OK]
END [OK]
END-BUNDLE
----------------------------------------
START: sudo bash -c 'rm -rf /home/sysadmin/.neon/exec/785f40da-1e1b-45bf-87b0-503e0f28cd26'
END [OK]
START: sudo bash -c 'touch /var/local/neonkube/setup/helm-install-glauth'
END [OK]
START: sudo bash -c 'touch /var/local/neonkube/setup/glauth-install'
END [OK]
START: sudo bash -c 'mkdir -p /var/local/neonkube/setup'
END [OK]
START: sudo bash -c 'if [ -f "/var/local/neonkube/setup/glauth-ready" ] ; then exit 0; else exit 1; fi'
END [ERROR=1]
*** STATUS: wait for glauth
START: sudo bash -c 'touch /var/local/neonkube/setup/glauth-ready'
END [OK]
START: sudo bash -c 'mkdir -p /var/local/neonkube/setup'
END [OK]
START: sudo bash -c 'if [ -f "/var/local/neonkube/setup/glauth-users" ] ; then exit 0; else exit 1; fi'
END [ERROR=1]
*** STATUS: create glauth users
# CLUSTER-END-SETUP-FAILED ####################################################

Here's the failure in cluster.log:
===============================================================================
STEP 12: setup cluster

STATUS: *** ERROR: [Neon.Common.ExecuteException]: ERROR:  relation "groups" does not exist
LINE 2: ...                                      INSERT INTO groups(nam...
                                                             ^

*** ERROR: [Neon.Common.ExecuteException]: ERROR:  relation "groups" does not exist
LINE 2: ...                                      INSERT INTO groups(nam...
                                                             ^

*** STACK:
   at Neon.Common.ExecuteResponse.EnsureSuccess() in C:\src\neonKUBE\Lib\Neon.Common\Helper\ExecuteResponse.cs:line 99
   at Neon.Kube.KubernetesExtensions.NamespacedPodExecAsync(IKubernetes k8s, String namespaceParameter, String name, String container, String[] command, CancellationToken cancellationToken, Boolean noSuccessCheck) in C:\src\neonKUBE\Lib\Neon.Kube\Kubernetes\KubernetesExtensions.cs:line 573
   at Neon.Kube.KubeSetup.<>c__DisplayClass125_0.<<InstallGlauthAsync>b__2>d.MoveNext() in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4238
--- End of stack trace from previous location ---
   at Neon.Kube.NodeSshProxy`1.InvokeIdempotentAsync(String actionId, Func`1 action) in C:\src\neonKUBE\Lib\Neon.Kube\Proxies\NodeSshProxy.cs:line 469
   at Neon.Kube.KubeSetup.InstallGlauthAsync(ISetupController controller, NodeSshProxy`1 master) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4212
   at Neon.Kube.KubeSetup.InstallSsoAsync(ISetupController controller, NodeSshProxy`1 master) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4022
   at Neon.Kube.KubeSetup.SetupClusterAsync(ISetupController controller, Int32 maxParallel) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 333
   at Neon.Kube.SetupController`1.<>c__DisplayClass35_0.<<ExecuteStep>b__6>d.MoveNext() in C:\src\neonKUBE\Lib\Neon.Kube\SetupController\SetupController.cs:line 976
--- End of stack trace from previous location ---
   at System.Threading.Tasks.TaskExtensions.WaitWithoutAggregate(Task task) in C:\src\neonKUBE\Lib\Neon.Common\Extensions\TaskExtensions.cs:line 42
   at Neon.Kube.SetupController`1.<>c__DisplayClass35_1.<ExecuteStep>b__1() in C:\src\neonKUBE\Lib\Neon.Kube\SetupController\SetupController.cs:line 979

# CLUSTER-END-SETUP-FAILED ####################################################

Here's another probably related cluster deployment failure (tiny-xcp-cstor.cluster.yaml):
STATUS: *** ERROR: [Neon.Common.ExecuteException]: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL:  database "glauth" does not exist

*** ERROR: [Neon.Common.ExecuteException]: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL:  database "glauth" does not exist

*** STACK:
   at Neon.Common.ExecuteResponse.EnsureSuccess() in C:\src\neonKUBE\Lib\Neon.Common\Helper\ExecuteResponse.cs:line 99
   at Neon.Kube.KubernetesExtensions.NamespacedPodExecAsync(IKubernetes k8s, String namespaceParameter, String name, String container, String[] command, CancellationToken cancellationToken, Boolean noSuccessCheck) in C:\src\neonKUBE\Lib\Neon.Kube\Kubernetes\KubernetesExtensions.cs:line 625
   at Neon.Kube.KubeSetup.<>c__DisplayClass125_0.<<InstallGlauthAsync>b__2>d.MoveNext() in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4242
--- End of stack trace from previous location ---
   at Neon.Kube.NodeSshProxy`1.InvokeIdempotentAsync(String actionId, Func`1 action) in C:\src\neonKUBE\Lib\Neon.Kube\Proxies\NodeSshProxy.cs:line 469
   at Neon.Kube.KubeSetup.InstallGlauthAsync(ISetupController controller, NodeSshProxy`1 master) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4216
   at Neon.Kube.KubeSetup.InstallSsoAsync(ISetupController controller, NodeSshProxy`1 master) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 4026
   at Neon.Kube.KubeSetup.SetupClusterAsync(ISetupController controller, Int32 maxParallel) in C:\src\neonKUBE\Lib\Neon.Kube.Setup\KubeSetup.Operations.cs:line 333
   at Neon.Kube.SetupController`1.<>c__DisplayClass35_0.<<ExecuteStep>b__6>d.MoveNext() in C:\src\neonKUBE\Lib\Neon.Kube\SetupController\SetupController.cs:line 976
--- End of stack trace from previous location ---
   at System.Threading.Tasks.TaskExtensions.WaitWithoutAggregate(Task task) in C:\src\neonKUBE\Lib\Neon.Common\Extensions\TaskExtensions.cs:line 42
   at Neon.Kube.SetupController`1.<>c__DisplayClass35_1.<ExecuteStep>b__1() in C:\src\neonKUBE\Lib\Neon.Kube\SetupController\SetupController.cs:line 979

# CLUSTER-END-SETUP-FAILED ####################################################

@marcusbooyah: so it looks like we're calling NamespacedPodExecAsync() here to configure these postgres tables and I suspect that sometimes the previous operations haven't completed yet.  This seems a bit odd.  I wonder if making all of these calls in the context of a retry policy might help.
I see that we're doing something similar on three places:

setup/minio-policy
setup/glauth-users
setup/minio-bucket...

I wonder if wrapping these calls with a retry policy would help.

I'm going to add a new IKubernetes.NamespacedPodExecWithRetryAsync() extension method that takes an IRetryPolicy as a parameter and then performs the pod exec using that policy and then  define a policy for this within the KubeSetup class.
Then, I'll convert all of the these calls in KubeSetup.Operations.cs and hopefully these problems will go away.

These changes don't seem to be breaking anything.  I've built a couple of clusters, one using neon-cli and the other with neon-desktop.
Hopefully, this has also addressed some transient errors.  We'll have to keep an eye out for any problems.
I'm going to close this.  We can reopen if we encounter additional problems.

Dang! we're still seeing problems with glauth!

I poked around a bit this morning.  Here's what I think is happening:

We're configuring the postgres.so plugin for persistence.
I don't see any of our code creating the glauth database, so I assume that the plugin creates and initializes the database schema when the glauth deployment starts.
We do wait for the glauth deployment to start
...but we assume that the database/schema will be immediately be initialized

The fix is have the setup/glauth-ready action wait for both the glauth deployment to start as well as waiting for the database/schema to be initialized.  I'm going to add a WaitForAsync() that waits for queries on the groups, users, and capabilities tables (we'll initializing ) until the queries succeed, indicating that the database is ready.

FIXED: Looks like these changes are working.


Grant yunfei with write permission

Yunfei (@haoyunfeix) , as main QA for this project, need push permission to allow him to manage the bugs. So @baleboy could you grant him?

done


Update nz-list-item-meta.component.html Fixes #3250

PR Checklist
Please check if your PR fulfills the following requirements:

[X] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number:  #1350
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

@ismezy Please follow the commit message guidelines. And a test is necessary in this case.


Default filters for Rails profile exclude unexpected files

Currently, default profile for :rails adds some filters, for example /config/ and /db/ filters.
Because of how filters are implemented this will also exclude files located in /lib/module/my/config/for/something/ which is a little unexpected.
It would be great to make it possible to improve files to match against relative routes like \A/config/ or something like that, what do you think?
Thanks for the great work with SimpleCov!

Hey there,
thanks for the issue report!
That seems like a problem indeed :smile: Imo the default profile should only exclude files in the root config folder.


chore(docs): imporoves usability of useAuth and exports useTableColumns

Description

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Changes made:

Adds export for useTableColumns and doc snippet
Adjusts useAuth typing so generics can be used

Type of change

[x] Chore (non-breaking change which does not add functionality)

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

docs: prefix should be used.


COMMONSRDF-20: Provide a mechanism for allowing the load of different RDF Term Factories

As discussed in COMMONSRDF-20 here is a PR adding the possibility to use a ServiceLoader for looking up RDFTermFactory instances.

Need to mention in the contract for RDFTermFactory that all implementations need to have a default constructor if they want to support this method, otherwise they shouldn't include a META-INF/services file.

Not sure whether this belongs into the documentation of Commons RDF. It's part of the contract of ServiceLoader and it's documented there. If we provide an implementers guide (as proposed in JIRA), there would be a pointer to the ServiceLoader documentation, which would explain the requirements for this approach.

If we want implementations to support ServiceLoader where practical (e.g.
with empty constructor), then I think we should also mention it in
RDFTermFactory doc, as that now says something like "It is not specified
how to get an RDFTermFactory instance" which could be misleading if the
user guide and simple encourage ServiceLoader.
As I think that could be a different debate I suggest to merge your current
PR which I think is uncontroversial.  I shall do so on Friday.
On 6 May 2015 06:32, "Benedikt Ritter"<EMAIL_ADDRESS>wrote:

Not sure whether this belongs into the documentation of Commons RDF. It's
part of the contract of ServiceLoader and it's documented there. If we
provide an implementers guide (as proposed in JIRA), there would be a
pointer to the ServiceLoader documentation, which would explain the
requirements for this approach.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-commonsrdf/pull/12#issuecomment-99328299
.

The other issue is that typically instances loaded with ServiceLoader contain keys that users can use to select their desired implementation based on some feature that they are looking for.
If they are just aiming to get to any implementations, and they are sure there is only one on the class path, then ServiceLoader with Iterator.next is an ideal way to delink them at compile time. It is only when there is more than one on the classpath that the issue of keys/features needs to be examined.

Right, now a factory does not even have a name() or a prescribed toString() - so it would be a bit difficult to do an informed choice if there is more than one implementation.
Presumably if you are using the ServiceLoader you don't care too much about which implementation you get, although you might have an order of preference, like keep "simple" as the fallback option - but the order of implementations listed in the ServiceLoader is not something to be relied on.
The implementation guide should probably note that only implementations that can be "used generally" should list themselves - e.g. a minimal implementation that doesn't implement createLiteral(String) and createBlankNode()  shouldn't be listed as a ServiceLoader service.


[BUG] Org todo buffer has a modeline that covers the buffer

When toggling the TODO portion of an item in org mode, the buffer that pops up to display which options you can set the todo to is covered by the modeline.  Someone in Discord mentioned that the modeline should probably not be there.
Steps to reproduce:

Open an org file
SPC m t to change the TODO tag

OS: Mac OS Catalina
Emacs: 26.2.90
Doom: v2.0.9 (straight)

I have the same problem.

I have the same issue
OS: Manjaro Gnome
Emacs: 26.2.90
Doom: Doom v2.0.9 (develop)

As of 43d80dc this should be resolved. Let me know if that isn't the case and I will reopen this issue. Thanks for bringing it to my attention!

Thank you @hlissner !


Abstract gateway context implement outside of model package

Please provide a description of this PR:
GatewayContext should be private to k8s gateway implement, so this pr does a refactor of move it from pilot/pkg/model to pilot/pkg/config/kube/gateway

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
b4bd679c7e1cd27ab92b5f3d9965de4d1b82cb19
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn @ramaraochavali


some auto-gen'd ClientImpls use fluent ".with" convention, but return void

(hmm, GitHub lost my comment somehow)
See Network and Compute mgmt. clients have this problem.

Fixed in beta2 release.


[Improvement][dolphinscheduler-tools] whether it is necessary to perform updates after initialization

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
When executing org.apache.dolphinscheduler.tools.datasource.UpgradeDolphinScheduler#main method , If it is a blank database， This method only performs initialization operations, not DS upgrade.

Is this inconsistent with the method semantics ?Therefore, whether it is necessary to perform updates after initialization .

This operation is similar to the following

        public void run(String... args) throws Exception {
            if (dolphinSchedulerManager.schemaIsInitialized()) {
                dolphinSchedulerManager.upgradeDolphinScheduler();
                logger.info("upgrade DolphinScheduler finished");
            } else {
                dolphinSchedulerManager.initDolphinScheduler();
                dolphinSchedulerManager.upgradeDolphinScheduler();
                logger.info("init DolphinScheduler finished");
            }
        }

Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Currently, the latest table schema will be initialized during initialization. The update logic is used to upgrade from a lower version to a higher version. @seedscoder


Draw the route on the map

how can I draw the route on the map covering only the streets? I'm sending the coordinates and draw on the map is passing over the houses.
thx

This should not happen. Are you using TKRoute or any own route calculation service?
TKRoute is using Google Directions(Android) and MKDirections(iOS). if they deliver route coordinates going through houses, I would think this is a bug on either of this APIs.
Which platform is this happening? Do you can share those coordinates?

@TorbenK
I was using TKPolyline as required for various positions for the route. With TkRouter can inform various positions?

No you can only add one source/destination to a TKRoute. You can, of couse, add multiple though.
if you use TKPolyline to draw the lines, how do you calculate the route?

@TorbenK
I get a list of routes of vehicles and need to draw on the map the car route. I have any idea how I can do this?

You get a calculated route? Simply add the TKPolyline with the calculated Positions.
If not, add multiple TKRoute instances, it will calculate the route for you. Event though it might not be the optimal route you can just go from source -> destination -> source -> destination...and so on.

got it. thx

@elyfran  did you manage to drow the route using several points with latitude and longitude?


[Question] - custom events+CORS

Hi I'm currently developing a chatbot that I would like  to  know how should I configure WebSocket using your package when I have custom events for the same namespace and how flask-sock handlers that
Another question is how WebSocket receives new connections and validates CORS policy so it won't block any connection after the handshake? Could this be integrated with flask-cors package?
Thanks in advance

What do you mean when you say "events" and "namespace"? Do you want to use WebSocket or Socket.IO? This is a WebSocket extension, it just gives you a connection. If you want something more high-level, check out my Flask-SocketIO extension.
Flask-CORS should be able to handle your WebSocket route(s).

What do you mean when you say "events" and "namespace"? Do you want to use WebSocket or Socket.IO? This is a WebSocket extension, it just gives you a connection. If you want something more high-level, check out my Flask-SocketIO extension.
Flask-CORS should be able to handle your WebSocket route(s).

Nevermind, you've clarified what i was doing wrong. Thanks for the help! Not sure if the community would like to have more info about this but you can consider this issue as solved.
Sorry about any unclarified info I gave to this issue since this is my very first issue opened in an open-source project


fix memory size for PointLightBundle

Introduced in #1778, not fixed by #1931
The size of Lights buffer currently is :
    16 // (color, `[f32; 4]`)
    + 16 // (number of lights, `f32` encoded as a `[f32; 4]`)
    + 10 // (maximum number of lights)
        * ( 16 // (light position, `[f32; 4]`
          + 16 // (color, `[16; 4]`)
          + 4 // (inverse_range_squared, `f32`)
          )

-> 392

This makes the pbr shader crash when running with Xcode debugger or with the WebGL2 backend. They both expect a buffer sized 512. This can also be seen on desktop by adding a second light to a scene with a color, it's position and color will be wrong.
adding a second light to example load_gltf:
    commands
        .spawn_bundle(PointLightBundle {
            transform: Transform::from_xyz(-3.0, 5.0, -3.0),
            point_light: PointLight {
                color: Color::BLUE,
                ..Default::default()
            },
            ..Default::default()
        })
        .insert(Rotates);

before fix:

after fix:

This PR changes inverse_range_squared to be a [f32; 4] instead of a f32 to have the expected alignement

It sounds like it would be a good idea to add some kind of lighting demo that allows us to easily test 1-n light setups with different colors/sizes/etc. to prevent issues like this in the future.

Yup, we're getting close to being able to run in CI a deterministic scene that would output an image for comparison. That would cover a lot of things to test at once.
Running in CI: #1826
Getting an image from the scene: #22 (#1927)


update map not working anymore - returned error: UPDATE FAIL - ERROR : Expecting value: line 2 column 1 (char 1)

It's because kiwisdr.com webmaster has modified the /public/ webpage source code recently.
it's no more
 at start of each node description but
 now
Change that in https://github.com/llinkz/directTDoA/blob/7f01623237d0588b34cddf65a600936071f943f0/directTDoA.py#L177
Regards
linkz

Hello,
just installed 7f01623, with the above suggest patch already installed, but the error is (almost) still there:
UPDATE FAIL - ERROR : Expecting value: line 2 column 1 (char 1)
Thank-you
Ugo

Hello
I probably wasn't clear on what to change and the modification must be done manually, I have not made a commit on this point
line 177 must be:
for html in req.text.split("
")[1:]:
see if it is the case

My mistake, sorry.
The patch is ok.
Thank-you
Ugo


DistributeKeys + ForwardKeysToOtherBots behavior changed.

So, I just noticed that in recent builds logic of how keys handled were changed. When I implemented DistributeKeys I had in mind that when this feature is on, and ForwardKeysToOtherBots is on also, bot would redeem keys according to the returned status, for example if three keys dropped, and first key is duplicated - bot would try second key to himself.
But now this changed, and bot distributes the keys to other bots as it were with ForwardKeysToOtherBots off - for the example above - if first key is duplicated - second key is still redeemed to the next account in queue.
Was this change intentional? Or just something was broken when implementing multiple keys activating via !redeem command? In other words - should I try to fix it or you want it to stay this way?

Yet another problem with this - bot forwards a key  that already  has been activated by the bot or duplicate one. Usually I use group chat to distribute keys, so after I insert several dozens of keys into, steam put a cooldown to all my accounts,  because of such improper forwarding.

@ZeKraggash forwarding via group chat is a bad idea anyway... Because all bots in group chat would try to do this simultaneously.

@Ryzhehvost hm... but what is the best way to activate 25+ keys?

Send it to the bot with DistributeKeys on (if you mean that the keys are for the same game).

It was intentional. Using keys forwarding is bad idea in general when distributing keys, but if that's the case, ASF tries to use as little keys as possible by keeping them unused.
For example, if we had 3 keys and only 2 bots with missing game. Only first two keys would be used instead of third one, as last bot would have the game already from one of the previous ones.
Likewise, if one of those keys would be used, and forwarding keys was on, eventually that bot would get the game, because last bot would try to activate last key, notice it's used already, then forward it to the bot that was unlucky to receive duplicated key.
It works similar, just with a bit different way, but goal will be almost the same, with one major difference - you can now keep unused keys for later, as they're redeemed in order instead of leaving potentially unused keys in random places.

Also side effect, ASF is now less likely to get block from duplicated keys, if you provided 5 keys to 5 bots, and all of them would be used, bot 1 would try to redeem all keys (and get potential lock), while with current mechanism, ASF will switch both key and the bot, making bot 2 trying to redeem next key.

Let me explain. With both DistributeKeys + ForwardKeys on, it was working like this:

Trt to activate on first bot.
If key is OK, switch to the next bot and next key and go to 1.
If key if duplicated - switch the next key, and go to 1 (now you have broken this)
If key is already owned - swith to the next bot and go to 1.
I think it was the most optimal way to activate keys, because it would utilize both keys and bots to the maximal limit.

Actually, I thought about scenario you made now, and decided that this scenario is actually the worst one, that's why I didn't bothered to implement it (also I didn't wanted to make one more config switch, because two is already too much).
So, now I'm confused what to do. Probably I would need to fork again, and go to the hell of updating it every time you update main branch, because current build lacks one of the features I use most.

So the only thing which is bad in current logic is the fact that bot switch is also done on duplicated key, while it should switch the key only, can be done.

That should make you happy, feel free to confirm if it works the way you want now :+1:

Thank you very much Archi, would test if right now

Basically what I changed is the fact that if key is invalid or dupe, bot is not changed (only key), if key is OK, both bot and key are changed.
Forwarding keys is not altered as bot will not try to forward dupe or invalid key, so there's no way that dupe or invalid key will hit keys forwarding mechanism.

I double checked if current logic works the way you want and it seems OK to me (according to your explanation), but feel free to further explain if it doesn't work the way you want.

At a first glance works perfectly. Thanks again!

Glad to hear it then :+1:


Provide error messages on failing docker build

Currently, the exit_code of both stage’s docker build is ignored. The build should fail on build errors and log at least error_report_lines.

just captured the result and added logging - thanks!


Update allowed attributes in _expand_prefix_spec

The backend function _expand_prefix_spec performs a validation of what prefix attributes are allowed by comparing received attributes with a list. A few attributes, for example order_id, are missing. Make sure that the list is up to date!

Also the backend function _expand_prefix_query contains a list of attributes, go thorough that one too.


Haskell on docker and vagrant

We could add info about haskell on docker / vagrant into guide
Example usage both of platforms for haskell :
haskell on docker
haskell on vagrant
I will try prepare PR for this.

It's not clear that either are being maintained.

There is a standard Docker image that can be trusted. I'm using the REPL now to mess around with Haskell for the first time.
@bitemyapp I can write some documentation on how to use if you think it makes sense (it would basically be the docs for that repo).

@davewalk I'd really like to not give new users (learners) of Haskell the impression that these are things they need to do in order to learn Haskell. This guide is for people who haven't yet learnt Haskell, it's not for production users figuring out productionization. If we did include Docker instructions, I'd prefer it be in the second half of the guide after the essential educational resources and with a qualifier that explains you don't have to use these tools to learn and use Haskell on your own computer.
If that works for you, I think instructions would be helpful for people who don't know want to use for (Docker && Haskell).

@bitemyapp Yes totally agree. We could do separate section that won't indicate that it's required. I thought that it could be useful for experienced programmers in other languages, who knows about Docker and Vagrant.


Investigate DuckDB as local teaching dw

I've been looking at this today with target-duckdb and dbt-duckdb meltano plugins
This is currently broken because target-duckdb uses a newer version of duckdb than dbt-duckdb, and attempting to upgrade dbt-duckdb causes similar issues to #7
The suggestion is to use target-parquet, which would allow you to use dbt-duckdb to load and transform the parquet files - see https://github.com/jwills/dbt-duckdb/issues/66


Is it possible to override translations?

I would like to override a few labels in en.yml, is it possible to do this and not lose the changes when updating the plugin?


Update estimated time is 0-2147483648:0-2147483648:0-2147483648?

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!

Bizarre fact: "2,147,483,647" is the 32 bit integer limit (huge math number), somehow it estimated that it will take something between 0-2147483648 hours, 0-2147483648 minutes and 0-2147483648 seconds, (the "-" represents that it's a range) so it COULD be 0, 1,2, 3, 4, 45, 8263, 6546, etc.
IF it updated in<PHONE_NUMBER> hours, it will take 8.9478E+7 (89478485) days to update.
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
Uhh, i updated the game and boom.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

Btw, yes the update was successful, but it just showed that big numbers around 2 seconds before the game restarted. So yeah, it's just a visual glitch.

Yeah, it happens to me too. It's just a visual glitch, nothing crazy.

It happened to me but not when the game was done updating. It just randomly went there. Probably because I clicked out of it a couple of times and etc.


xarray test failure related to dask.array argmax on Python 2.6

This recently turned up as a failure on our master branch (xref https://github.com/pydata/xarray/pull/794):
https://travis-ci.org/pydata/xarray/jobs/115522509
We get the error TypeError: type object argument after * must be a sequence, not generator from this line in dask.array:
https://github.com/dask/dask/blob/0771dba0b7504847bf2143f4c9ebb67467ac983b/dask/array/reductions.py#L509
I'm not sure why the dask test suite didn't pick this up, since you do appear to run tests against Python 2.6. The source appears to be @jcrist's PR https://github.com/dask/dask/pull/1024.

The toolz version provided by conda is too low (the error provided is
surpringly unhelpful). If you pip intall toolz on py26 this should go away.
I'm not sure what the best course of action is here, since anaconda support
for 2.6 is dropped.
On Mar 12, 2016 9:39 PM, "Stephan Hoyer"<EMAIL_ADDRESS>wrote:

This recently turned up as a failure on our master branch (xref
pydata/xarray#794 https://github.com/pydata/xarray/pull/794):
https://travis-ci.org/pydata/xarray/jobs/115522509
We get the error TypeError: type object argument after * must be a
sequence, not generator from this line in dask.array:
https://github.com/dask/dask/blob/0771dba0b7504847bf2143f4c9ebb67467ac983b/dask/array/reductions.py#L509
I'm not sure why the dask test suite didn't pick this up, since you do
appear to run tests against Python 2.6. The source appears to be @jcrist
https://github.com/jcrist PR #1024
https://github.com/dask/dask/pull/1024.
—
Reply to this email directly or view it on GitHub
https://github.com/dask/dask/issues/1046.

Both requirements.txt and the conda.yaml file should reflect the toolz
version dependency.  I suspect that Anaconda will just stop providing new
dask packages for 26.
On Sat, Mar 12, 2016 at 10:45 PM, Jim Crist<EMAIL_ADDRESS>wrote:

The toolz version provided by conda is too low (the error provided is
surpringly unhelpful). If you pip intall toolz on py26 this should go away.
I'm not sure what the best course of action is here, since anaconda support
for 2.6 is dropped.
On Mar 12, 2016 9:39 PM, "Stephan Hoyer"<EMAIL_ADDRESS>wrote:

This recently turned up as a failure on our master branch (xref
pydata/xarray#794 https://github.com/pydata/xarray/pull/794):
https://travis-ci.org/pydata/xarray/jobs/115522509
We get the error TypeError: type object argument after * must be a
sequence, not generator from this line in dask.array:

https://github.com/dask/dask/blob/0771dba0b7504847bf2143f4c9ebb67467ac983b/dask/array/reductions.py#L509

I'm not sure why the dask test suite didn't pick this up, since you do
appear to run tests against Python 2.6. The source appears to be @jcrist
https://github.com/jcrist PR #1024
https://github.com/dask/dask/pull/1024.
—
Reply to this email directly or view it on GitHub
https://github.com/dask/dask/issues/1046.

—
Reply to this email directly or view it on GitHub
https://github.com/dask/dask/issues/1046#issuecomment-195894304.

To be clear, the issue is that the last version of toolz on the default conda channel is 0.7.2. Dask now depends on 0.7.4. In our travis test suite, toolz gets upgraded in the pip install partd line, so our tests pass fine on 2.6.
The code for arg reductions could be easily changed to make toolz 0.7.2 work fine. I'm not sure if that's the best course of action though.

Thanks for your help debugging this!
I'm not entirely sure why, but we had already switched to pip for installing dask on Python 2.6 (probably because the conda package wasn't being updated). So it was easy enough to switch to pip for toolz, too. That should take care of things.


Refactor pack install

In this PR:

Ensure public pack installations DO NOT save a copy of the pdsc file in .Local/ (bug spot by @jkrech)
Ensure public installed packs ALWAYS have a copy of the pdsc file in .Web/ and that non-public packs have a copy of the pdsc file in .Local/
2.1. Ensure that all packs installed have the <CMSIS_PACK_ROOT>/Vendor/PackName/x.y.z/Vendor.PackName.pdsc file
2.2. Propagate the same behavior for packs installed via direct file or via url
Change the order of URL retrieval for a pack. The order now is packPdsc.releaseTag.URL, and if that is empty build the url using packPdsc.URL/Vendor/PackName.pdsc
3.1. If installing a pack via cpackget pack add Vendor.PackName.1.0.0 and the releaseTag does not exist, raise "pack version not found in the pdsc file"
Avoid updating .Web/index.pidx automatically on pack add. Instead, let the user know the public index might be outdated and show how to update it.
By default cpackget pack add Vendor.PackName will attempt to read .Web/Vendor.PackName.pdsc.
5.1. If the file is not present, then look for this tag in .Web/index.pidx.
5.1.1. If the tag IS present
<IP_ADDRESS>. Attempt to download the pdsc using the tag's URL attribute + Vendor.PackName.pdsc, and place it in .Web/Vendor.PackName.pdsc
<IP_ADDRESS>. If the download of the pdsc file fails, raise "the URL for the pack pdsc file seems not to exist or it didn't return the file"
5.1.2. If the tag is NOT present
<IP_ADDRESS>. Attempt to read .Local/Vendor.PackName.pdsc
<IP_ADDRESS>. If file exists, retrieve pack's URL as mentioned in step 3
<IP_ADDRESS>. If file does not exist, raise "URL for the pack cannot be determined. Please consider updating the public index: cpackget index https://keil.com/pack/index.pidx"

It still needs a bit polishing and other small features that need some attention after these changes. I'll update this PR accordingly.

@jkrech I'm merging this now and should be landing another PR soon early next week with another set of changes. I'll break the PRs into smaller ones


Bump upper bound on ghc-mod

The current upper bound is overly restrictive, and prevent hsdev from working with Stackage. I just tested, and the upper bound can be relaxed. I'd send a pull request, but it seems like your master branch has already removed the upper bound.
Pinging @geraldus, original issue: https://github.com/fpco/stackage-server/issues/50
By the way, can I recommend adding your package to Stackage so that you'll be notified of breakage and users can more easily use your package?

Created PR https://github.com/fpco/stackage/pull/393


Set up initial basic daemon script

Daemon will communicate with EVM and Sovereign to keep token balance numbers in sync, updating the database as needed

Done in https://github.com/DemocracyEarth/balance-keeper


Proposal: Add mount hook

Mount in     runc contain PremountCmds and PostmountCmds fields.
Howerver, there are no corresponding fields in Mount of runtim-spec.
Mount hook is useful, I'd like to add it in runtime-spec, such as:
type Mount struct {
	// Destination is the path where the mount will be placed relative to the container's root.  The path and child directories MUST exist, a runtime MUST NOT create directories automatically to a mount point.
	Destination string `json:"destination"`
	// Type specifies the mount kind.
	Type string `json:"type"`
	// Source specifies the source path of the mount.  In the case of bind mounts on
	// Linux based systems this would be the file on the host.
	Source string `json:"source"`
	// Options are fstab style mount options.
	Options []string `json:"options,omitempty"`
        // Optional Command to be run before Source is mounted.
        PremountCmds []Hook `json:"premount,omitempty"`
        // Optional Command to be run after Source is mounted.
        PostmountCmds []Hook `json:"postmount,omitempty"`
}

On Wed, Dec 14, 2016 at 08:16:20PM -0800, Ye Yin wrote:

Mount hook is useful…

Can you give some example use-cases?
As it stands, you're free to setup an external mount namespace any way
you like and then set linux.namespaces[].path for the mount namespace
to join your prepared namespace.  The trade-off when landing something
like pre-/post-mount hooks in the spec is whether the use cases it
supports justify the increased complication for everyone else.

There maybe lots of use-cases, and I give two examples here:
(1) According to this post, when we mount a new devps instance, we should  changed /dev/ptmx to be a symbolic link to pts/ptmx. We can use Postmount command to this, just do as here.
(2)I want to run systemd in container with cgroup enabled in container, when cgroupfs is mounted in container, I want to mkdir systemd in directory/sys/fs/cgroup of container, so that systemd can run successfully.
Now, I have to mount tmpfs at /sys/fs/cgroup of host, then mkdir /sys/fs/cgroup/systemd, then use -v /sys/fs/cgroup:/sys/fs/cgroup to bind mount to container, this is not a good idea. More about this, see here.

I don't think this belongs in the spec and should be left out. @mrunalp would know more though


Using the .summary() method when fitting with weights produces an error.

I included sample code below:
import pyfixest as pf

data = pf.get_data()
res = pf.feols("Y ~ X1 | f1 + f2", data=data, weights = 'weights')
res.summary()

Calling res.summary() produces a TypeError on PyFixest 0.17.1 and 0.17.4

Thanks for reporting! I can fix this later tonight =)

Ah yes, it is related to #348 - .summary() tries to print an R2 value, which is not yet computed for WLS.

Hi, I just merged version 0.17.3 to master, you can install it by running
pip install git+https://github.com/s3alfisc/pyfixest.git

Thanks again for reporting!


dokku plugin-install keeps installing postgres, ignores new plugins

Whenever I run $dokku plugins-install it seems to run the same thing again and again - the pg installer from https://github.com/Kloadut/dokku-pg-plugin. There is no error, but now subsequent plugins such as link or elasticsearch are ignored.
$ dokku plugins-install
Cloning into '/tmp/dokku-pg-dockerfiles'...
... lots of output ...
Successfully built 2e592c81702e
I'm running dokku v0.2.3-60-gc05488b

Closing as there hasn't been an update from OP. Please comment if you have some more info for us :)


Request To become an Observer

Hello,
I was reading node.js community guide  and find out that if someone wants to become member they need to be observer first.
So how can I become observer ?

Vivek, you can also read the meeting Observers/Guests heading in the meetings:
https://github.com/nodejs/community-committee/issues/620


This doesn't build anymore.

I really need a good sample CF node app.
Resolving node version 5.* via semver.io...
Downloading and installing node undefined...
Downloaded []
Unable to download node undefined; does it exist?
-----> Build failed

Sorry, it's been a long day. Just getting rid of "engines" makes it work.

Yeah, the dependencies are a little out of date as well.
What version of the NodeJS buildpack are you using, I'm guessing the standard release isn't up to 5.* yet.

Should be fixed with commit 1891d88064a2501116625760aef720ed36d15e84


Update to mashumaro 3.15

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.57%. Comparing base (d437478) to head (5b7ae70).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1144   +/-   ##
=======================================
  Coverage   93.57%   93.57%
=======================================
  Files          21       21
  Lines        2039     2039
=======================================
  Hits         1908     1908
  Misses        131      131

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


Modify comment_ranges slice in BackwardsTokenizer

Summary
I was kinda curious to understand this issue (https://github.com/astral-sh/ruff/issues/7426) and just ended up attempting to address it.
Test Plan
cargo test

thanks!


Omnisharp 1.25.1/2 doesn't respect formatting definitions in omnisharp.json

Please paste the output from your clipboard## Issue Description ##
Steps to Reproduce
I have a c# project.
settings.json have
 "[csharp]": {
        "editor.defaultFormatter":  "ms-dotnettools.csharp" ,

    },
    "omnisharp.enableRoslynAnalyzers": true,
    "omnisharp.enableEditorConfigSupport": true,

I also have an omnisharp.json file which defines formatting options to be applied on alt-shift-f
They work fine in 1.25.0. Once the addon was updated to 1.25.1 it stopped respecting them and seems to apply some default options.
Expected Behavior
Formatting rules defined omnisharp.json should be applied.
Actual Behavior
Seems like its applying some default c# formatting options.
Logs
OmniSharp log
Starting OmniSharp server at 17/11/2022, 8:04:49
Target: c:\Users\ranis\Projects\Unity\TagFight\TagFight.sln
OmniSharp server started.
Path: c:\Users\ranis.vscode\extensions\ms-dotnettools.csharp-1.25.2-win32-x64.omnisharp\1.39.2\OmniSharp.exe
PID: 9916
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK

    Using the 'dotnet' on the PATH.

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: Visual Studio Community 2022 17.1.32414.318 17.1.0 - "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin"

    Registered MSBuild instance: Visual Studio Community 2022 17.1.32414.318 17.1.0 - "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin"

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Detecting Cake files in 'c:\Users\ranis\Projects\Unity\TagFight'.

    Did not find any Cake files

    Detecting projects in 'c:\Users\ranis\Projects\Unity\TagFight\TagFight.sln'.

    Queue project update for 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp.csproj'

    Queue project update for 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp-Editor.csproj'

    Detecting CSX files in 'c:\Users\ranis\Projects\Unity\TagFight'.

    Did not find any CSX files

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\Users\ranis\Projects\Unity\TagFight' on host 14720.

    Loading project: c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp.csproj

    Successfully loaded project file 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp.csproj'.

    Adding project 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp.csproj'

    Loading project: c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp-Editor.csproj

    Successfully loaded project file 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp-Editor.csproj'.

    Adding project 'c:\Users\ranis\Projects\Unity\TagFight\Assembly-CSharp-Editor.csproj'

    Update project: Assembly-CSharp

    Update project: Assembly-CSharp-Editor

    Solution initialized -> queue all documents for code analysis. Initial document count: 104.

    No symbol found. File: c:\Users\ranis\Projects\Unity\TagFight\Assets\Scripts\Combat\Runes\Effects\AreaOfEffect.cs, Line: 99, Column: 25.

    ************ Request ************

{
"Type": "request",
"Seq": 24,
"Command": "/inlayHint",
"Arguments": {
"Location": {
"FileName": "c:\Users\ranis\Projects\Unity\TagFight\Assets\Scripts\Combat\Runes\Effects\AreaOfEffect.cs",
"Range": {
"Start": {
"Line": 29,
"Column": 0
},
"End": {
"Line": 116,
"Column": 0
}
}
}
}
}
[fail]: OmniSharp.Stdio.Host
************  Response (124.2120ms) ************
{
"Request_seq": 24,
"Command": "/inlayHint",
"Running": true,
"Success": false,
"Message": ""System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.\r\nParameter name: index\r\n   at Microsoft.CodeAnalysis.Text.SourceText.LineInfo.get_Item(Int32 index)\r\n   at OmniSharp.Extensions.TextExtensions.GetPositionFromLineAndOffset(SourceText text, Int32 lineNumber, Int32 offset) in D:\\a\\1\\s\\src\\OmniSharp.Roslyn\\Extensions\\TextExtensions.cs:line 28\r\n   at OmniSharp.Extensions.TextExtensions.GetSpanFromRange(SourceText text, Range range) in D:\\a\\1\\s\\src\\OmniSharp.Roslyn\\Extensions\\TextExtensions.cs:line 55\r\n   at OmniSharp.Roslyn.CSharp.Services.InlayHints.InlayHintService.d__6.MoveNext() in D:\\a\\1\\s\\src\\OmniSharp.Roslyn.CSharp\\Services\\InlayHints\\InlayHintService.cs:line 58\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at OmniSharp.Endpoint.EndpointHandler2.<GetFirstNotEmptyResponseFromHandlers>d__19.MoveNext()\\r\\n--- End of stack trace from previous location where exception was thrown ---\\r\\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\\r\\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\\r\\n   at OmniSharp.Endpoint.EndpointHandler2.d__20.MoveNext() in D:\\a\\1\\s\\src\\OmniSharp.Host\\Endpoint\\EndpointHandler.cs:line 229\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at OmniSharp.Endpoint.EndpointHandler`2.d__16.MoveNext() in D:\\a\\1\\s\\src\\OmniSharp.Host\\Endpoint\\EndpointHandler.cs:line 137\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at OmniSharp.Stdio.Host.d__14.MoveNext() in D:\\a\\1\\s\\src\\OmniSharp.Stdio\\Host.cs:line 218"",
"Body": null,
"Seq": 66,
"Type": "response"
}
Received response for /v2/getcodeactions but could not find request.
Received response for /v2/getcodeactions but could not find request.
Received response for /v2/getcodeactions but could not find request.
Received response for /v2/getcodeactions but could not find request.
Received response for /v2/getcodeactions but could not find request.
Received response for /v2/getcodeactions but could not find request.
C# log
c# log is empty.
Environment information
VSCode version: 1.73.1
C# Extension: 1.25.2
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   6.0.202
 Commit:    f8a55617d2
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22621
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\6.0.202\
Host (useful for support):
Version: 6.0.4
Commit:  be98e88c76
.NET SDKs installed:
6.0.101 [C:\Program Files\dotnet\sdk]
6.0.202 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

better-cpp-syntax
jeff-hykin
1.16.3

cmake
twxs
0.0.17

cmake-tools
ms-vscode
1.12.27

cpptools
ms-vscode
1.12.4

cpptools-extension-pack
ms-vscode
1.3.0

cpptools-themes
ms-vscode
2.0.0

csharp
ms-dotnettools
1.25.2

doxdocgen
cschlosser
1.4.0

gc-excelviewer
GrapeCity
4.2.56

gitlens
eamodio
13.0.4

intellicode-api-usage-examples
VisualStudioExptTeam
0.2.6

isort
ms-python
2022.6.0

java
redhat
1.12.0

jupyter
ms-toolsai
2022.9.1202862440

jupyter-keymap
ms-toolsai
1.0.0

jupyter-renderers
ms-toolsai
1.0.12

lalrpop-highlight
mnxn
0.0.1

metals
scalameta
1.20.0

onehalf-dark
quandinh
0.3.0

python
ms-python
2022.18.2

qiskit-vscode
qiskit
0.5.5

rust-analyzer
rust-lang
0.3.1285

rust-syntax
dustypomerleau
0.6.1

scala
scala-lang
0.5.6

unity-code-snippets
kleber-swf
1.3.0

vsc-community-material-theme
Equinusocio
1.4.2

vscode-antlr4
mike-lischke
2.3.1

vscode-java-debug
vscjava
0.46.0

vscode-java-dependency
vscjava
0.21.1

vscode-java-pack
vscjava
0.25.6

vscode-java-test
vscjava
0.37.1

vscode-jupyter-cell-tags
ms-toolsai
0.1.6

vscode-jupyter-slideshow
ms-toolsai
0.1.5

vscode-maven
vscjava
0.39.2

vscode-pylance
ms-python
2022.11.20

vscode-theme-onedark
akamud
2.3.0

vscodeintellicode
VisualStudioExptTeam
1.2.29

See the top entry in the readme https://github.com/OmniSharp/omnisharp-vscode#whats-new-in-1251
The legacy formatting settings from omnisharp.json are no longer respected if editorconfig is enabled. You can transfer your formatting to editorconfig file or disable editorconfig.


ETA for VSCode Linter extension?

This is awesome. Do you have timeline for the release of the VSCode extension?

Linter is already part of the release, duh.