Add Unstoppable Domains reverse resolution

Done https://github.com/snapshot-labs/snapshot/pull/3464


Component adds annotations field

Component adds annotations field.
We need to add some markup information to annotations, and currently the component definition is missing the annotations field.
type ComponentStatus struct {
    ...
   Annotations map[string]string
}

See https://github.com/kubebb/components/pull/97

@dayuy Would you like to pick up this issue?

Okay, distinguish between public repo and internal chart museum by what field? @bjwswang

I see, there is no need to change CRD Repository, just add an annotation component-store.kubebb.k8s.com.cn/source when  fetching index.yaml from chart museum to create Component.
The annotations in the Chart.yaml of the chart uploaded are set by the user, if not set, it cannot be determined.

I see, there is no need to change CRD Repository, just add an annotation component-store.kubebb.k8s.com.cn/source when fetching index.yaml from chart museum to create Component. The annotations in the Chart.yaml of the chart uploaded are set by the user, if not set, it cannot be determined.

Agree with you. We just need to synchronize the annotations field of chart.yaml to component. For how to set up annotations, our platform should automatically tag the chart package with official.
However, https://kubebb.github.io/components is a repository that we maintain, but the chart packages it generates are not packaged from our platform, so we need to add a special treatment for this repository.

I see, there is no need to change CRD Repository, just add an annotation component-store.kubebb.k8s.com.cn/source when fetching index.yaml from chart museum to create Component. The annotations in the Chart.yaml of the chart uploaded are set by the user, if not set, it cannot be determined.

Agree with you. We just need to synchronize the annotations field of chart.yaml to component. For how to set up annotations, our platform should automatically tag the chart package with official.
However, https://kubebb.github.io/components is a repository that we maintain, but the chart packages it generates are not packaged from our platform, so we need to add a special treatment for this repository.

It would be better if the list of repositories that require special handling was customizable.

So we have common scenarios like this:
For compoenent developer,they can add any annotations in their Chart.yaml. But for this field omponent-store.kubebb.k8s.com.cn/source, we should allow platform owner(who runs the kubebb) customize the repository's component types.
For examples:

if the system admin set repository kubebb as the official repository,all components in that repo should be treated as official components
if the system admin set repository mychartmuseum as the internal repository, all components in that repo should be treaed as internal components

Finally, we decide to just add annotations to Repository for now, indicating the repository kubebb is official.


Add standard, wallmount and improvised N2 closets, Revived

About the PR
Reopens #27383 and updates to use entity tables.
Why / Balance
fixes #27194
Technical details
n/a
Media

Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an in-game showcase.

Breaking changes
n/a
Changelog
n/a

fake test fail

Iirc the improvised sprite was removed because space racism bad, though having it for a mappable option isn't the worst imo

Iirc the improvised sprite was removed because space racism bad, though having it for a mappable option isn't the worst imo

I can take it or leave it. I really just want the wallmounted ones.


Allow changing base URL using an envvar

Allow setting MINDEE_BASE_URL environment variable to change the base URL for all requests.
For example:
export MINDEE_BASE_URL=https://infergate.staging-xsdj4gia.mindee.net/v1

It is already the case.
See https://github.com/mindee/mindee-api-dotnet/issues/63


WIP: Docker containers

This contains the work @matthew-t-smith did on Dockerizing the front-/back-ends. Please include/correct anything that might be missing!
Build each end separately:

cd into the back-end or front-end directories
Build the image running a command like:
docker build --tag backendtest:1.0 .
Run the container with a command like:
docker run -p 8000:8000 --name <name> backendtest:1.0
Note, the -p flag should be set to 8000:8000 for the back-end and 3000:3000 for the front-end.

Build/run the two together:
In the root directory run docker-compose up. This should start both containers and have them talk to each other. When you visit http://localhost:3000/, you may need to refresh the page once to get the Node list on the side. This bug was fixed in #76.

I pushed a few tweaks, all minor things (a missing hypen, quotes, and a backslash)!
This now works for me with docker-compose up in the root dir and the separate apps can be spun up with
docker build --tag backendtest:2.0 .
docker run -p 8000:8000 --name be backendtest2.0

and
docker build --tag frontendtest:2.0 .
docker run -p 3000:3000 --name fe frontendtest2.0

A few more changes. Still having this one issue:
back-end_1   | [28/Apr/2020 05:45:55] "GET /workflow/nodes HTTP/1.1" 500 23
back-end_1   | [28/Apr/2020 05:45:55] "POST /workflow/new HTTP/1.1" 200 78

@reelmatt can you check on the GET nodes that seems to be failing? Can see it's finding the workflow views alright now.
I will also double back when this gets resolved to fix up the Postman Tests that are surely failing with the directory changes for back-end.

@matthew-t-smith We may be having some differences with where directories are being located in the Docker container. Made a comment about adding the cd vp part back to the docker-compose.yml for the back-end.
The issue with GET /workflow/nodes is an order-of-operations issue introduced in one of the latest PRs. The Node listing now requires a Workflow object to know where to look for the Nodes/handle custom node creation. So the fix is just reversing the two calls to do /workflow/new first followed by /workflow/nodes. If you refresh the page once after it loads, you should see the listing pop in.
I know @reddigari has done a lot of front-end improvements in the mean time, so I think it might be easier to make a change in one of his open PRs, or make the change after this PR is merged to reduce conflict headaches.
Re: testing, I think it's actually a problem with the pyworkflow unit tests. If I add cd back-end to the workflow file before pipenv install and test locally, everything is fine. There may be a Python version issue though with the container GitHub Actions uses to run the workflow though. We might need to revert the update to the Pipfile to go from 3.8.2 back to 3.8 (or 3.8.1, that's what looks like is the latest version for default GitHub Actions—hard to confirm without it doing a run).

@matthew-t-smith I committed the changes to fix the GitHub Action runner; it now finds and passes the tests.
Have you looked into the discrepancy between including cd vp in the docker-compose.yml that I commented on above? The build fails when I do not include it, but I could be missing something. If we figure that out, I think we're good to merge so I'm going to open this up for review.

A little confused by the volume mounts in docker-compose.yml, since the individual Docker files copy the source directories into the image. Likewise the front end build runs npm install, so we shouldn't need to mount node_modules. Are the mounts just for the sake of keeping the image up to date as we develop?

Just a thought: would it be possible to include an option for a user to mount their own custom nodes directory into the pyworkflow custom nodes location? They could store their nodes locally and then have access to them as soon as the container is running as opposed to manually uploading each one, and having them disappear when the container restarts.

@reelmatt - I think I have an idea on the directory issue. I’ll do some testing Sunday to be sure.
@reddigari - the directory mounts were largely following some other samples. I’ll double check on those. The node modules should be ignored in the images so the container is lighter, but I will make sure that’s actually happening. Also, not sure on the option of loading into the container’s directory structure. Interesting, but once I get this updated, I can see.

As far as I understand it (which is without much dev ops experience), the volume mounts are so a running container reflects changes you make locally without having to rebuild. But the image we upload for people to pull and run needs to have the released source code copied (and dependencies installed). That's what's handled by the COPY statements, and running npm install (which will create and populate node_modules in the container).
Using build args to decide whether to run the COPY and install commands is one option, but I've also seen folks maintain two Dockerfiles, one called Dockerfile that runs all the copy/install stuff, and one called Dockerfile.dev, for development, that does not. But I'm not sure how to make that play with docker-compose.

Abandoning in favor of PR #84


issue #506--->fixed the redis issue

While creating docker image of guestbook go, We encountered an error regarding the simpleredis reposity.
Modified and changed it to the v2 of repo. The DockerImage is created successfully now.
Also changes the redis image in redis master controller and replica controller yaml file.
The issue should have been resolved

/assign idvoretskyi

/assign soltysh

/lgtm

@idvoretskyi , but it is not working and giving error in pulling image

Okay Thanks!

@idvoretskyi changed it. Please review and approve. Thanks!


NoneType

Traceback (most recent call last):
File "PixivBrowserFactory.pyc", line 488, in login
TypeError: 'NoneType' object is not subscriptable
Error at login(): (<class 'TypeError'>, TypeError("'NoneType' object is not subscriptable"), <traceback object at 0x040788E8>)
Error at doLogin(): (<class 'TypeError'>, TypeError("'NoneType' object is not subscriptable"), <traceback object at 0x04418F88>)
Cannot Login!
Have python 3.8 and ffmpeg, using executable

I had a similar problem (not sure if the exactly the same one), but I solved it by using my login, password and cookie value in config.ini
Q3 in https://github.com/Nandaka/PixivUtil2#a-usage

I had a similar problem (not sure if the exactly the same one), but I solved it by using my login, password and cookie value in config.ini Q3 in https://github.com/Nandaka/PixivUtil2#a-usage

I am having the same issue, and I already do that.
I pressume that is maybe related to me using a VPN, the problem is that not using the VPN is an imposibility in my case, since for some reason the ISP I have is unable to connect to sites like Pixiv, Imgur and others for no other reason than who knows, but using a VPN like expressvpn which is the one I use has worked fine for me until yesterday.
So, now I am stuck unable to access the site with PixivUtil, while just browsing the site doesn't yield any kind of problem.
Funny enough, I can access fanbox without any problem without a vpn, but pixv, nope.

dupes with #1209


Changing compiler for cmake

Hello, thanks for this great package :)
I was trying to compile it but my default gcc doesn't support lambdas. Is there a quick way to set the C and C++ compiler to be used by cmake in Julia?

Hi, CMake should pick up the CC and CXX environment variables if you start the build from scratch, though I haven't tested this from within Julia's Pkg.build.
Is the problem with "normal" C++11 lambdas, or the C++14 generic lambda from the parametric example? The latter one could maybe be removed, making the package compatible with C++11.

Thanks. I had to remove the build directory completely and try again.
However, gcc 4.8 isn't new enough, as I still get
CMake Error at CMakeLists.txt:27 (target_compile_features):
  The compiler feature "cxx_generic_lambdas" is not known to CXX compiler

I suppose I have to update my compiler, because of the C++14 generic lambda. Yes, we could try removing it to see if that helps, is that something widely used in CppWrapper?

The use of generic lambdas is not required, it's only syntactic sugar to put all the code wrapping a parametric type in one place. I have replaced the generic lambdas with a classic templated functor, so it should be fine on GCC 4.8 now.

Thanks, it works fine now.
I had to fix some include paths, see the PR https://github.com/barche/CppWrapper/pull/3


Update remark-wiki-link-plus and add test files

Summary
Resolves #267
This PR updates the remark-wiki-link-plus package and adds files in test/ folder.
Changes

Latest patch fix in remark-wiki-link-plus v1.1.1 for case sensitive url paths.
test files - test/case-sensitive-wikilinks and test/Test/Page

@khalilcodes there is not much to review here and I think if you wanted me to review the actual changes you could have also created a PR for the plugin itself 😉 ...which again brings this to my mind:
I think it would be much better if we integrated all our remark plugins into our flowershow repo. Any changes we make to them are related to how we want them to work in the template anyway... and it would make both the development and testing much easier, and changes related to one issue could be included in a single PR (e.g. in this case this PR would also include all the changes to the plugin itself, which makes more sense for me as a reviewer). Atm for some reason all the changes to the plugins are just applied without any code review (that is not to say the code in there is bad or sth, but rather that other team members miss on the opportunity to participate in/follow their development process). And it doesn't make any difference for end users of these packages - they will be published separately to npm anyway.
I can't really see any significant reasons why we wouldn't do this tbh 😅.
@rufuspollock


Nested loop not updating even after update() with example

Example: http://codepen.io/anon/pen/waGLJp
Click the first checkbox once. Notice 3rd checkbox becomes checked as expected.
Uncheck 3rd checkbox. 3rd checkbox should become checked.
Click first checkbox again notice 3rd checkbox not checked.
Maybe I'm doing something wrong.

self.checkboxs[2].checked=true;
always true after the first time, never sees a change after.

I thought it should re-render based on data after especially if i call update().

No, you can call update all day long, and if it does not see a change, it will not update, this is to minimize dom updates, it only updates when it sees a change.  If you set checked to false at some point it will update.

this seems counter-intuitive:
if i change data and render the vdom, shouldn't the vdom be compared with the active dom and changes be propagated?
Otherwise it would end up with an issue like this one. In which the UI is manipulated changing the state of the dom. but the vdom is not going to be diffed if the data is not changed even if a .update() is called.
A syncing mechanism still needs to compare the actual dom because riot isn't the only thing that can change it, eg, user.

this issue was fixed and it could will be solved with the option reorder=true in riot 2.3.0


Model Proposal: Lead

Why do you need this model? What does it solve? Please describe.
The lead model is a basic CRM requirement. Check out this wiki page about Lead Generation

Field Name
Python Type
Description
Unique
Required
Index
Default Value

title
str
Title of the customer or lead
False
False
True

Additional context
Should inherit #4

Checkout:

MicroPyramid/Django-CRM: Open Source CRM based on Django


fix typo in  user kdoc

Hello, great job with the project and love what you've done! This PR fixes a small typo in the User kdoc.

Thank you for the PR! Next time try to follow our pull request template 😄


Format Chapter 6-5

Chapter 6-5 is new after the first English print edition and is currently formatted differently in various ways from parallel chapters, which should be addressed before we produce another print edition.

 Gov4Git notices
On Saturday, 07-Sep-24 01:18:32 UTC by Gov4Git dev
Notice ygiitm
Started managing this issue, using the Plural Management Protocol v1,  as Gov4Git concern 1016 with initial priority score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice hxydfr
This issue's priority score is now 0.000000.
The cost of priority is 0.000000.
The projected bounty is now 0.000000.
Notice xeiw3p
The set of eligible proposals claiming this issue is empty.


JobRunner uploadExecutableNode improvement

I would suggest having https://github.com/azkaban/azkaban/pull/1167 instead of this, but this is of course a smaller change..
Include stack trace in error logging.
Based on this discussion / request by @chengren311: https://github.com/azkaban/azkaban/pull/1148#pullrequestreview-41936280

#1167 LGTM.
@chengren311 what do you think?


removed the content in syncLocalSettings.json, can't restore

Visual Studio Code Version : version 1.19.0
Code Settings Sync Version : 2.8.6
Operating System : Mac OS X
Occurs On: [Upload & Download & Help Configuring ]
Proxy Enabled: [  No ]
GIst Id: [ https://gist.github.com/adamchenwei/bd846fbef0ece06ae73ca99a1619cfeb ]
I had issue for my existing config in standard edition VS Code setting when copied into the Inside edition, I copied and pasted into Insider Edition, but it wouldn't work, I remove the content from the syncLocalSettings.json inside the Insider Edition VS Code, now the plugin can't find the syncLocalSettings.json file anymore. Uninstall the plugin does not help. How should I proceed?
Thanks

resolved by resetting the setting and past the file into the dir directly.


Consider removing strictCasts awareness from the constant evaluator

The type system object will soon not track strictCasts (see: https://github.com/dart-lang/sdk/issues/53873) and in the process of evaluating that impact, we noticed that the const evaluator is using this setting when checking assignability in order to avoid reporting duplicate errors.  Chatting with @scheglov, this was arguably not the best place to de-duplicate and looking forward we want to get away from the const evaluator doing these checks. In the short term, removing these checks would result in potentially duplicated errors but will unblock https://github.com/dart-lang/sdk/issues/53873 in the service of the big analysis options refactor (https://github.com/dart-lang/sdk/issues/53876).
@kallentu and I will chat about this later and I'll update w/ next steps.
/fyi @bwilkerson

In these places we checked that typeSystem.runtimeTypeMatch() is false, so we have to return InvalidConstant.
We can check whether to report it when we are inside ConstantVerifier.
This checking mechanism is not available yet, but I think we can implement it.
And this would be cleaner than passing strictCasts that by itself does not mean anything to constant evaluation.
Also, ask yourself, which strictCasts do you want to use when you evaluate a constant in a library imported from another package, with different analysis_options.yaml file?

We can check whether to report it when we are inside ConstantVerifier.

I'm not convinced that's true without duplicating some of the work already done by the constant evaluator. Consider the case where the exception is thrown in a constructor that is potentially removed from the current scope of the ConstantVerifier.

Also, ask yourself, which strictCasts do you want to use when you evaluate a constant in a library imported from another package, with different analysis_options.yaml file?

Wouldn't that question need to be answered regardless of where the deduplication is done?

We can check whether to report it when we are inside ConstantVerifier.

I'm not convinced that's true without duplicating some of the work already done by the constant evaluator. Consider the case where the exception is thrown in a constructor that is potentially removed from the current scope of the ConstantVerifier.

What work is done by the constant evaluator?
For the specific example that you provided, I expect that the constant evaluator will attach information to the InvalidConstant that says that there was an exception. These we will always report as diagnostics.
OTOH, InvalidConstants that are result of runtimeTypeMatch() will have different information saying so, are not always have to be reported.

Also, ask yourself, which strictCasts do you want to use when you evaluate a constant in a library imported from another package, with different analysis_options.yaml file?

Wouldn't that question need to be answered regardless of where the deduplication is done?

No. If the constant evaluator always report a runtimeTypeMatch() error and leaves it to ConstantVerifier to decide whether report it, then strictCasts only controls whether to report the runtime error that happened during evaluating a constant expression in the current file. For the current file the value of strictCasts is well defined.

I share some of Brian's hesitation but value the continued conversation. Thanks!
After chatting with @kallentu I feel really strongly that we don't want to degrade the current experience as duplicated errors are a substantial source of confusion for users.
To that end, I propose that we move ahead with the approach proposed in https://dart-review.googlesource.com/c/sdk/+/341336 with a TODO linking to this issue inviting re-evaluation. If there's a better way to do this, preserving the current behavior and removing strictCasts awareness that can be picked up as a separate arc of work.
Sound good?

I agree about not degrading the current experience.
The question is only how to achieve this.
@bwilkerson Do we add passing strictCasts as technical debt? How long lived will be this TODO, and whether we will ever pick up this separate arc of work?
I don't agree about passing strictCasts everywhere in constants evaluation. But @bwilkerson is TL, so if he says that we are doing this, I will review the rest of the CL and rubber stamp the constant evaluation portion of it.

We can check whether to report it when we are inside ConstantVerifier.

What would this check consist of? Would it not still use isAssignable (and hence, strictCasts)?

We can check whether to report it when we are inside ConstantVerifier.

What would this check consist of? Would it not still use isAssignable (and hence, strictCasts)?

Please read my next message in this thread, it adds some details about strictCasts.
The answer, if a vague form, is the new issue that @pq opened - a generate mechanism for knowing which diagnostics were already reported, with tracking where. Very specifically, but possibly not optimally, for constants, we could ask the error reporter, if there were type errors (or maybe any errors) reported in the source range of the evaluated constant expression. Performance is probably not important here, we are on the rate path with an error.

Sorry, I just don't really understand the second part where you wrote
leaves it to ConstantVerifier to decide whether report it, then strictCasts only controls whether to report the runtime error that happened during evaluating a constant expression in the current file. For the current file the value of strictCasts is well defined.. I don't really comprehend what the vision of this looks like (ie. I'm a little confused! If you'd like to help me understand that more)
If we're talking about a new mechanism to handle what diagnostics are reported, the constant evaluator currently doesn't know of the errors that are already reported by the other passes. Its ErrorReporter is shared with the ConstantVerifier, but not ErrorVerifier for example. We would need to make a common error reporter and do deduplication if we are going down that route.
If we choose to do it differently, @pq and I have come up with some other ideas and heuristics. I can write them up in a little doc to discuss. But I think in general the solution to this, I agree, is to have a mechanism for knowing which diagnostics were already reported. Probably with some more discussion though?
I agree that "passing strictCasts everywhere in constants evaluation" isn't great, but I don't know if this is something to block on without some more work to tackle the larger issue. And I feel like it's going to be an arc of work that's larger than to tack onto Phil's PR.

And I feel like it's going to be an arc of work that's larger than to tack onto Phil's PR.

I don't propose doing this arc of word in the same CL.
If we going to rework de-duplication, it will be in its own CL.

I think we reached a consensus here. Closing out.


Add parse method for SchemaCriterion

@fblundun it would be cool if this will get released before r79.

That can happen!


Merge pull request #39062 from vaibhavsagar/bump-all-cabal-hashes

all-cabal-hashes: bump to 2018-04-19T00:28:09Z
(cherry picked from commit eb0943feb08078e94b34e377af094fcf3a036330)
This allows us to use newer packages from Hackage.
Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

/cc @peti

Thank you!


Angular Material Drag&Drop between table: Failed to execute 'insertBefore' on 'Node':

Hi
I have a problem with Angular Material Drag&Drop.
I have two very simple table:
`
To do

                column 1
                column 2
                column 3

                {{ item }}
                {{ item }}
                {{ item }}

Done

                column 1
                column 2
                column 3

                {{ item }}
                {{ item }}
                {{ item }}

`
The problem is when I move row to the header of table. I get an error:
1 Uncaught DOMException: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

What version of the CDK are you using? We had something similar a while ago so it might be worth trying to update to the latest.

What version of the CDK are you using? We had something similar a while ago so it might be worth trying to update to the latest.

^9.2.4
I think that this code should be attached to tbody.
cdkDropList #todoList="cdkDropList" [cdkDropListData]="todo" [cdkDropListConnectedTo]="[doneList]"
But the next problem is Angular Material Table. The code is generated automatically and there is now option to create custom  tag.


Incorrect gradient of model output with respect to inputs using GradientTape

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
2.1.3
Custom Code
No
OS Platform and Distribution
Windows 10 Home
Mobile device
No response
Python version
3.7
Bazel version
n/a
GCC/Compiler version
n/a
CUDA/cuDNN version
CPU
GPU model and memory
n/a
Current Behaviour?
I am trying to take the gradient/jacobian of my model output with respect to the inputs to study the derivatives of my parameter space. This issue has come up several times in the past but I do not seem to be able to reproduce their results or solutions, if any were suggested. It seems that I am able to apply gradients a single variable output, single variable input model, however my problem is multivariate with respect to both. I am using an older version of TF for work purposes but the issue was the same for TF 2.6 as well.

Standalone code to reproduce the issue
import tensorflow as tf
from numpy import *
from tensorflow.keras import Sequential
from tensorflow.keras.layers import Dense
import matplotlib.pyplot as plt
from sklearn.model_selection import train_test_split

x1 = linspace(0,4*pi,100000)
x2 = linspace(2,20,100000)
y = cos(x1) + x2/5

model = Sequential()
model.add(Dense(100, activation='elu', input_shape=(2,)))  # elu used so that smooth, continuous functions are differentiated
model.add(Dense(100, activation='elu'))
model.add(Dense(50, activation='elu'))
model.add(Dense(50, activation='elu'))
model.add(Dense(10, activation='elu'))
model.add(Dense(10, activation='elu'))
model.add(Dense(1, activation='linear'))
model.compile(loss='MSE', optimizer='adam', metrics=['accuracy'])

x_in = vstack((x1,x2)).T
y_out = y

x_train, x_valid, y_train, y_valid = train_test_split(x_in, y_out, test_size=0.3, shuffle= True)

epochs = 100
batch_size = 110

h0 = model.fit(x_train, y_train, validation_data=(x_valid,y_valid), batch_size=batch_size,epochs=epochs)

grado1 = zeros((100000,2))
grado2 = zeros((100000,2))

for i in range(0,100000):
    x = tf.Variable([[x_in[i,0],x_in[i,1]]])

    with tf.GradientTape(persistent=True,watch_accessed_variables=True) as t:
        t.watch(x)
        out1 = model(x)
        out2 = tf.math.cos(x[:,0]) + x[:,1]/5  # this works using both a Variable array as well as separated taped variables, i.e., x1t, x2t
    gradients1 = t.gradient(out1, x)
    gradients2 = t.gradient(out2, x)
    if i % 100 == 0:
        print(i)
    grado1[i,:] = gradients1.numpy()
    grado2[i,:] = gradients2.numpy()

ymodel = model.predict([x_in])

for i in range(2):
    plt.figure(figsize=(15,4))
    ax = plt.subplot(111)
    ax.plot(x_in[:,i],y_out,label='data',linewidth=5)
    ax.plot(x_in[:,i],ymodel,'--',label='model',linewidth=5)
    plt.ylabel('y')
    plt.xlabel('x'+str(i+1))
    plt.legend(loc='lower left')

    ax2 = ax.twinx()
    ax2.plot(x_in[:,i],grado1[:,i],'b--',label='grad1_x'+str(i+1)+' model')
    ax2.plot(x_in[:,i],grado2[:,i],'g',label='grad2_x'+str(i+1)+' autodiff formula')
    if i == 0:
        ax2.plot(x_in[:,0],-sin(x_in[:,0]),'r--',label='grad2_x'+str(i+1)+' explicit formula')
    elif i == 1:
        ax2.plot(x_in[:,1],1/5*ones(len(x_in[:,1])),'r--',label='grad2_x'+str(i+1)+' explicit formula')
    plt.ylabel('dy/dx'+str(i+1))
    plt.xlabel('x'+str(i+1))

    plt.legend()

Relevant log output
No response

@bzdjordje,
TensorFlow 2.1 is not actively supported. Could you update TensorFlow to the latest stable version v2.9 and check if you are facing the same issue. Thanks!

Unfortunately the error still persists if I run the same script in v2.9 as presented below

Hi @tilakrayal and @bzdjordje,
So, I don't think this is a bug because you've trained your model in a very underdetermined fashion.  I think the better way would be to train it on a grid of points in $\mathbb{R}^2$ (that is, the cartesian product over ranges for x1 and x2.  Instead, you've trained it on a a single line vstack(x1, x2) where x1 = linspace(0, 4*pi, 10000) and x2 = linspace(2, 20, 100000).
If you look at dy/dx2, the positions where it is very close to 5 (like around x2 = 18), the dotted line in the first graph is very close to that of the explicit formula.  And, places where dy/dx2 is very far from 5, like at x2=13,  then dy/dx1 is far from that of the analytic formula.  They are just compensating for each other.

@bzdjordje,
Could you please take a look at this comment from the user and let us know if it still an issue. Thank you!

@tilakrayal @hrbigelow
Thank you for the responses. The data is randomly shuffled prior to training so the model is not trained one slice as opposed to another, validation/training datasets are fairly uniformly distributed across.
zoomed in

(plotting only every 100th point)

Hi @bzdjordje,
When I said 'slice', I mean a subset of $\mathbb{R}^2$, which is the domain of your target function.  Actually, I mistook the domain.  You are taking 100000 points evenly spaced along the line segment from point (0, 2) to (4pi, 20).  What you should be calculating is the gradient projected to that line.  If you do that, you see that the autodiff gradient according to the model very nearly matches the analytical gradient of the function.
To calculate this gradient, you take the dot product with a normalized vector in the direction of that line.  Here is the result:

What I did is edited your code as follows:
import tensorflow as tf
import numpy as np
from tensorflow.keras import Sequential
from tensorflow.keras.layers import Dense
import matplotlib.pyplot as plt
from sklearn.model_selection import train_test_split

def make_model():
    x1 = linspace(0,4*pi,100000)
    x2 = linspace(2,20,100000)
    y = cos(x1) + x2/5

    model = Sequential()
    model.add(Dense(100, activation='elu', input_shape=(2,)))  # elu used so that smooth, continuous functions are differentiated
    model.add(Dense(100, activation='elu'))
    model.add(Dense(50, activation='elu'))
    model.add(Dense(50, activation='elu'))
    model.add(Dense(10, activation='elu'))
    model.add(Dense(10, activation='elu'))
    model.add(Dense(1, activation='linear'))
    model.compile(loss='MSE', optimizer='adam', metrics=['accuracy'])

    x_in = np.vstack((x1,x2)).T
    y_out = y

    x_train, x_valid, y_train, y_valid = train_test_split(x_in, y_out, test_size=0.3, shuffle= True)

    epochs = 100
    batch_size = 110

    h0 = model.fit(x_train, y_train, validation_data=(x_valid,y_valid), batch_size=batch_size,epochs=epochs)

    return x_in, y_out, model

def analyze(model, x_in):

    grado1 = np.zeros((100000,2))
    grado2 = np.zeros((100000,2))

    for i in range(0,100000):
        x = tf.Variable([[x_in[i,0],x_in[i,1]]])

        with tf.GradientTape(persistent=True,watch_accessed_variables=True) as t:
            t.watch(x)
            out1 = model(x)
            out2 = tf.math.cos(x[:,0]) + x[:,1]/5  # this works using both a Variable array as well as separated taped variables, i.e., x1t, x2t
        gradients1 = t.gradient(out1, x)
        gradients2 = t.gradient(out2, x)
        if i % 100 == 0:
            print(i)
        grado1[i,:] = gradients1.numpy()
        grado2[i,:] = gradients2.numpy()

    ymodel = model.predict([x_in])

    return grado1, grado2, ymodel

print('x_in, y_out, model = make_model()')
print('grado1, grado2, ymodel = analyze(model, x_in)')

def main(x_in, y_out, grado1, grado2, ymodel):

    # project the gradients onto the line x1 = x2
    direction = np.array([4 * pi, 20 - 2])
    direction /= np.linalg.norm(direction)

    proj_grado1 = np.matmul(grado1, direction)
    proj_grado2 = np.matmul(grado2, direction)

    plt.figure(figsize=(15,4))
    ax = plt.subplot(111)
    plt.ylabel('dy / d_direction')
    plt.xlabel('x_1')
    plt.legend(loc='lower left')

    # ax2 = ax.twinx()
    # ax2.plot(x_in[:,i],grado1[:,i],'b--',label='grad1_x'+str(i+1)+' model')
    # ax2.plot(x_in[:,i],grado2[:,i],'g',label='grad2_x'+str(i+1)+' autodiff formula')

    ax.plot(x_in[:,0],proj_grado1[:],'b--',label='line_grad1_x model')
    ax.plot(x_in[:,0],proj_grado2[:],'g',label='line_grad2_x autodiff formula')
    # if i == 0:
        # ax2.plot(x_in[:,0],-sin(x_in[:,0]),'r--',label='grad2_x'+str(i+1)+' explicit formula')
    # elif i == 1:
        # ax2.plot(x_in[:,1],(1/5)*ones(len(x_in[:,1])),'r--',label='grad2_x'+str(i+1)+' explicit formula')
    # plt.ylabel('dy/dx_1')
    # plt.xlabel('x_1')

    plt.legend()
    plt.show()

@bzdjordje,
Could you try to execute the above alternative work-around and confirm if it is working as expected. Thank you!

@tilakrayal @hrbigelow
Hello, the correction to my script provided by Henry worked on my computer, thank you!

@bzdjordje,
Glad the issue is resolved for you, please feel free to move this to closed status. Thank you!


unifi7: 7.4.156 -> 7.5.176

Description of changes
This bumps the unifi controller to the latest version.
Since it also requires JDK 17, this adds logic in the module to automatically select it.
When JDK 16+ is used, we also need to add some more parameters to allow the controller to load the protected modules.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@wegank This broke my unifi controller. I'm using an older version as the  new one is not compatible with my AP's and now see:
root@birne:~/ > journalctl -fu unifi.service
Oct 16 09:58:55 birne systemd[1]: Started UniFi controller daemon.
Oct 16 09:58:56 birne java[550380]: Unrecognized option: --add-opens
Oct 16 09:58:56 birne java[550380]: Error: Could not create the Java Virtual Machine.
Oct 16 09:58:56 birne java[550380]: Error: A fatal exception has occurred. Program will exit.

There should be a check or warning making the new --add-opens parameter optional here

@vifino I'm using
  services.unifi = {
    enable = true;
    unifiPackage = pkgs.unifi6;
};

How would I set I different JDK version for the unifi contorller service?

From this
if you are on version 6 it uses an older JRE that seems to not have this option.
    services.unifi.jrePackage = mkOption {
      type = types.package;
      default = if (lib.versionAtLeast (lib.getVersion cfg.unifiPackage) "7.5") then pkgs.jdk17_headless else if (lib.versionAtLeast (lib.getVersion cfg.unifiPackage) "7.3") then pkgs.jdk11 else pkgs.jre8;
      defaultText = literalExpression ''if (lib.versionAtLeast (lib.getVersion cfg.unifiPackage) "7.5") then pkgs.jdk17_headless else if (lib.versionAtLeast (lib.getVersion cfg.unifiPackage) "7.3" then pkgs.jdk11 else pkgs.jre8'';
      description = lib.mdDoc ''
        The JRE package to use. Check the release notes to ensure it is supported.
      '';
    };

Feels like this should have been optional -- looks like this PR probably broke anyone using a unifi controller that is not version 7.

@wegank This broke my unifi controller. I'm using an older version as the new one is not compatible with my AP's and now see:
root@birne:~/ > journalctl -fu unifi.service
Oct 16 09:58:55 birne systemd[1]: Started UniFi controller daemon.
Oct 16 09:58:56 birne java[550380]: Unrecognized option: --add-opens
Oct 16 09:58:56 birne java[550380]: Error: Could not create the Java Virtual Machine.
Oct 16 09:58:56 birne java[550380]: Error: A fatal exception has occurred. Program will exit.

There should be a check or warning making the new --add-opens parameter optional here

Sorry for the delay. There was a check, but the author clearly forgot to add parentheses. Opened #264036.

Sorry, I should have looked more closely and seen it was just parens and opened the PR myself :) thanks for the response though.


Test run sessions should show TFM when multiple frameworks

When multiple frameworks are being tested (with multi targeting), the test run session names are all the same: "VS Test Run session for ...". It's nearly impossible to see which platform the results are for.
In the case of multi-targeting, please add the TFM to the test result session name.

@onovotny can you please share an expected outcome, it would help us close on user experience
/cc @singhsarab

I would like to see the TFM added into the session name:
Here's what I see currently. I think adding net461/netcoreapp2.1, etc would help a lot.

The framework is still not output, we should amend the trx to do it.


decision_making on indigo

Hi there, not sure if this is the right place to ask.
Does anybody know if there is any reason why the decision_making package is not available on the indigo distribution?
I know there is SMACH, but I prefer the decision_ making approach, and given that it was already on hydro distro, I was wondering if it'd be possible to have it on indigo too.
I've been using it for a while via source on indigo... I'm an user, not a developer, but it'd be useful to have it on synaptics.

Which distro to release into is up to the maintainer. I suggest opening a ticket for that package https://github.com/cogniteam/decision_making

Thanks, and sorry for the issue!


Apply machine scope to options that specify paths

Addresses https://github.com/OmniSharp/omnisharp-vscode/issues/3116


iOS deferred deep linking apns

@derrickstaten
still needs a bit of logic

needs testing by @danwalkowski now

Scenarios to test having push notifications received:

[ ] app is not open and not backgrounded
[ ] app is backgrounded
[ ] app is already opened

other considerations:

[ ] might be nice to have an "+is_push_notification" flag, but not a big deal for v1
[ ] make sure no merge conflict with FB SDK code

pair programmed together, so a bit weird for me to :+1:. @danwalkowski can you also leave a :+1:?

:+1:


Buttons to act on left/right switches

Hi,
On some aircrafts (e.g.: King Air 350i), controls are independant for left and right, such as lights or pitot.
However the corresponding button on the LD only controls one side, not both. Having the LD button to act on both switches would be great.
Thanks!

Added for next release


Accepting a suggestion in the merge editor does not apply it to the file

Have a merge conflict that is open in the 3wm editor
Use the codelens to accept a suggestion
:bug: the change is made so the file is marked dirty but the changes are not saved to disk. It's easy to forget that you have to do this and adds friction to the experience of accepting merge conflicts, could we consider just writing the change to disk with a workspace edit (which would also allow easy undo)?

Undo should work and usually VS Code only auto-saves the file when the user configured this.
When you complete the merge, the file is saved and staged. I wonder what is easy to forget?

I might have closed the editor by clicking x on the tab instead of clicking the Complete Merge button, for example. But I was surprised by this behavior when debugging on @MeghanKulkarni's machine, and she doesn't have autosave enabled while I usually do, so maybe this is out of scope and just covered by the autosave behavior

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Hero Area Accessabilty

A note that the 6 orange dot “bg-shape” makes that area look like a carousel. I would remove them. Also, they’re decorative, they should not have an alt=”bg-shape”. All these random floating images should have alt=”” to indicate they offer no meaningful value.

Broken into https://github.com/clirdlf/climate-resiliancy.clir.org/issues/5

closed in 9d69727


Updated build_directory to work with new astro website

The build_directory function will now scrape from the new astro website (astro.arizona.edu).
Also added a rudimentary README file

my b, meant to pull request into Lily's fork

no worries, was wondering what was up. cool that you're still hacking on it!

an unfortunately enforced hack because of the new website and it's convoluted new html structure


Please provide a master key file manually in '/opt/jfrog/artifactory/etc/security/master.key'.

I'm running Artifactory via docker-compose and attempting to link to an external Postgres database. I continue to encounter "master key" related issues when trying to run Artifactory.
"- Found existing master key fingerprint in the DB, without master.key file. Please provide a master key file manually in '/opt/jfrog/artifactory/etc/security/master.key'."
As anyone ever experienced this?

[JFrog-Access] [WARN ] (o.s.b.c.e.AnnotationConfigEmbeddedWebApplicationContext:550) - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start embedded container; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration': Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jerseyConfig' defined in URL [jar:file:/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-application-4.1.44.jar!/org/jfrog/access/rest/config/JerseyConfig.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.jfrog.access.rest.config.JerseyConfig]: Constructor threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'authFilter' defined in URL [jar:file:/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-server-rest-4.1.44.jar!/org/jfrog/access/server/rest/filter/AuthFilter.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'authenticationServiceImpl': Unsatisfied dependency expressed through method 'setCertificateService' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'accessStartupService': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Master key mismatch. The provided master.key file does't match the DB fingerprint. Make sure your db.properties configurations are valid and the master key matches the DB you are trying to connect to.
artifactory    | 2019-03-19 20:42:36,436 [localhost-startStop-2] [JFrog-Access] [ERROR] (o.s.b.SpringApplication:771) - Application startup failed
Latest error after I manually created the master.key file and provided the AWS KMS key..

@marcuschaney - it looks like you have connected to an existing DB (that was already setup by Artifactory) with a new Artifactory deployment (or did not persist file system from a previous deployment).
When Artifactory starts, if master key is not in the DB, it will use existing key or create a new one and then register it in DB and any future connections will use this key for validation (comparing file to DB).
You should setup a new Artifactory with a clean DB in this case.

@eldada Thank you for your reply! After replacing my previous RDS Postgres instance, I attempted to run a new container, and now I'm receiving the below error:
artifactory    | Mar 20, 2019 2:57:47 PM org.apache.catalina.core.StandardContext startInternal
artifactory    | SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
artifactory    | Mar 20, 2019 2:57:47 PM org.apache.catalina.core.StandardContext startInternal
artifactory    | SEVERE: Context [/artifactory] startup failed due to previous errors
artifactory    | 14:57:47.438 [localhost-startStop-1] DEBUG org.artifactory.webapp.servlet.ArtifactoryContextConfigListener - Context shutdown started
artifactory    | 14:57:47.438 [localhost-startStop-1] DEBUG org.artifactory.webapp.servlet.ArtifactoryContextConfigListener - Context shutdown Finished
artifactory    | Mar 20, 2019 2:57:47 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
artifactory    | WARNING: The web application [artifactory] appears to have started a thread named [Thread-5] but has failed to stop it. This is very likely to create a memory lea                                                           k. Stack trace of thread:
artifactory    |  sun.nio.fs.LinuxWatchService.poll(Native Method)
artifactory    |  sun.nio.fs.LinuxWatchService.access$600(LinuxWatchService.java:47)
artifactory    |  sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:314)
artifactory    |  java.lang.Thread.run(Thread.java:748)
Any ideas?
V/r
Marcus

@eldada If I'm doing an external database, where do I map the port? Just under "artifactory"? Copy of my docker compose file is below:
version: '2'
services:
artifactory:
image: docker.bintray.io/jfrog/artifactory-pro:6.7.3
container_name: artifactory
ports:
- 8081:8081
volumes:
- /data/artifactory/artifactory_extra_conf:/artifactory_extra_conf
environment:
- DB_TYPE=postgresql
- DB_USER=artifactory
- DB_PASSWORD=xxxxxxxxx
- DB_HOST=xxxxxxxxxxxxxxxx.us-gov-west-1.rds.amazonaws.com
- DB_PORT=5432
# https://github.com/docker/compose/issues/4485
#You can use a $$ (double-dollar sign) when your configuration needs a literal dollar sign.
#This also prevents Compose from interpolating a value, so a $$ allows you to refer to environment variables that you don’t want processed by Compose.
restart: always
ulimits:
nproc: 65535
nofile:
soft: 32000
hard: 40000

type=postgresql
driver=org.postgresql.Driver
url=jdbc:postgresql://xxxxxxxxxxxxxxxxxs-gov-west-1.rds.amazonaws.com:5432/artifactory
username=artifactory
password=fxxxxxxxxx
Is the above syntax correct for the db.properties file?

More:
artifactory    | 2019-03-20 18:06:41.576  INFO 303 --- [ost-startStop-2] o.j.a.s.startup.AccessHomeFinderImpl     : Using JFrog Access home at '/opt/jfrog/artifactory/access' resolved from: System property (Artifactory)
artifactory    | 2019-03-20 18:06:42.006  INFO 303 --- [ost-startStop-2] o.j.a.migration.ConfigMigrationRunner    : Current version of Access Home is 3, latest version is 4. Applying migrations.
artifactory    | 2019-03-20 18:06:42.011  INFO 303 --- [ost-startStop-2] o.j.a.migration.ConfigMigrationRunner    : Migrating Access Home to version 4
artifactory    | 2019-03-20 18:06:42,372 [localhost-startStop-2] [JFrog-Access] [INFO ] (o.j.a.c.JFrogApplicationContextInitializer:74) - Using JFrog Access home at '/opt/jfrog/artifactory/access'
artifactory    | 2019-03-20 18:06:42,402 [localhost-startStop-2] [JFrog-Access] [INFO ] (o.j.a.AccessApplication:48) - Starting AccessApplication v4.1.44 on 8105a839f591 with PID 303 (/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-application-4.1.44.jar started by artifactory in /)
artifactory    | 2019-03-20 18:06:42,402 [localhost-startStop-2] [JFrog-Access] [INFO ] (o.j.a.AccessApplication:597) - The following profiles are active: production,grpc
artifactory    | 2019-03-20 18:06:42 [UNDEFINED] [INFO ] Fetched Artifactory [artifactory.home=null] from servlet context
artifactory    | 2019-03-20 18:06:42 [UNDEFINED] [INFO ] Resolved Artifactory home by logger [artifactory.home=/opt/jfrog/artifactory].
artifactory    | 18:06:42.997 [Thread-7] INFO org.jfrog.config.watch.FileWatchingManager - Starting watch of folder configurations
artifactory    | 18:06:43.045 [localhost-startStop-1] DEBUG org.artifactory.converter.VersionProviderImpl - Last Artifactory database version is: v673
artifactory    | 18:06:43.091 [localhost-startStop-1] INFO org.artifactory.converter.ConvertersManagerImpl - Triggering PRE_INIT conversion, from v673 to v673
artifactory    | 18:06:43.091 [localhost-startStop-1] INFO org.artifactory.converter.ConvertersManagerImpl - Finished PRE_INIT conversion, current version is: v673
artifactory    | 2019-03-20 18:06:43 [ARTIFACTORY] [INFO ] Master key file found.
artifactory    | Mar 20, 2019 6:06:43 PM org.apache.catalina.core.StandardContext startInternal
artifactory    | SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
artifactory    | Mar 20, 2019 6:06:43 PM org.apache.catalina.core.StandardContext startInternal
artifactory    | SEVERE: Context [/artifactory] startup failed due to previous errors
artifactory    | 18:06:43.572 [localhost-startStop-1] DEBUG org.artifactory.webapp.servlet.ArtifactoryContextConfigListener - Context shutdown started
artifactory    | 18:06:43.573 [localhost-startStop-1] DEBUG org.artifactory.webapp.servlet.ArtifactoryContextConfigListener - Context shutdown Finished

Accessed the localhost log in the container and this seems to be the root cause (cannot connect to DB)
20-Mar-2019 21:34:07.727 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [org.artifactory.webapp.servlet.ArtifactoryHomeConfigListener]
java.lang.RuntimeException: Could't establish connection with db: jdbc:postgresql://artifactorytestdb.cegxppgui6sf.us-gov-west-1.rds.amazonaws.com:5432/artifactory
at org.jfrog.config.db.TemporaryDBChannel.(TemporaryDBChannel.java:35)
at org.artifactory.common.ArtifactoryConfigurationAdapter.getDbChannel(ArtifactoryConfigurationAdapter.java:209)
at org.jfrog.config.wrappers.ConfigurationManagerImpl.getDBChannel(ConfigurationManagerImpl.java:428)
at org.artifactory.config.MasterKeyBootstrapUtil.dbChannel(MasterKeyBootstrapUtil.java:234)
at org.artifactory.config.MasterKeyBootstrapUtil.tryToCreateTable(MasterKeyBootstrapUtil.java:115)
at org.artifactory.config.MasterKeyBootstrapUtil.validateOrInsertKeyInformation(MasterKeyBootstrapUtil.java:85)
at org.artifactory.config.MasterKeyBootstrapUtil.handleMasterKey(MasterKeyBootstrapUtil.java:66)
at org.artifactory.webapp.servlet.BasicConfigManagers.initHomes(BasicConfigManagers.java:115)
at org.artifactory.webapp.servlet.BasicConfigManagers.initialize(BasicConfigManagers.java:101)
at org.artifactory.webapp.servlet.ArtifactoryHomeConfigListener.contextInitialized(ArtifactoryHomeConfigListener.java:53)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4792)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:629)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.postgresql.util.PSQLException: FATAL: database "artifactory" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
at org.postgresql.core.v3.QueryExecutorImpl.readStartupMessages(QueryExecutorImpl.java:2586)
at org.postgresql.core.v3.QueryExecutorImpl.(QueryExecutorImpl.java:113)
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:222)
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:52)
at org.postgresql.jdbc.PgConnection.(PgConnection.java:216)
at org.postgresql.Driver.makeConnection(Driver.java:404)
at org.postgresql.Driver.connect(Driver.java:272)
at org.jfrog.config.db.TemporaryDBChannel.(TemporaryDBChannel.java:31)
... 22 more
20-Mar-2019 21:34:07.728 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [org.artifactory.webapp.servlet.logback.LogbackConfigListener]
java.lang.IllegalStateException: Artifactory home not initialized

Progress after changing the database name from /artifactory to /artifactorytestdb (which is what the instance is named in AWS. Now I get the below:
artifactory    | INFO: Starting ProtocolHandler ["ajp-nio-8019"]
artifactory    | 2019-03-20 21:54:10,774 [art-init] [INFO ] (o.a.s.ArtifactoryApplicationContext:503) - Artifactory application context set to NOT READY by refresh
artifactory    | 2019-03-20 21:54:10,775 [art-init] [INFO ] (o.a.s.ArtifactoryApplicationContext:243) - Refreshing artifactory: startup date [Wed Mar 20 21:54:10 UTC 2019]; root of context hierarchy
artifactory    | 2019-03-20 21:55:08,286 [art-init] [ERROR] (o.a.w.s.ArtifactoryContextConfigListener:96) - Application could not be initialized: class path resource [jar:war:file:/opt/jfrog/artifactory/webapps/] cannot be resolved to URL because it does not exist
artifactory    | java.lang.reflect.InvocationTargetException: null
artifactory    |        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
artifactory    |        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
artifactory    |        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
artifactory    |        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
artifactory    |        at org.artifactory.webapp.servlet.ArtifactoryContextConfigListener.configure(ArtifactoryContextConfigListener.java:211)
artifactory    |        at org.artifactory.webapp.servlet.ArtifactoryContextConfigListener.access$200(ArtifactoryContextConfigListener.java:67)
artifactory    |        at org.artifactory.webapp.servlet.ArtifactoryContextConfigListener$1.run(ArtifactoryContextConfigListener.java:92)
artifactory    | Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Could not resolve bean definition resource pattern [jar:war:file:/opt/jfrog/artifactory/webapps/artifactory.war*/WEB-INF/lib/artifactory-addon-bower-6.7.3.jar!/META-INF/addon.xml]; nested exception is java.io.FileNotFoundException: class path resource [jar:war:file:/opt/jfrog/artifactory/webapps/] cannot be resolved to URL because it does not exist
artifactory    |        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:229)
artifactory    |        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
artifactory    |        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:252)
artifactory    |        at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:127)
artifactory    |        at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:93)
artifactory    |        at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129)
artifactory    |        at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:538)
artifactory    |        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452)
artifactory    |        at org.artifactory.spring.ArtifactoryApplicationContext.refresh(ArtifactoryApplicationContext.java:243)
artifactory    |        at org.artifactory.spring.ArtifactoryApplicationContext.(ArtifactoryApplicationContext.java:143)
artifactory    |        ... 7 common frames omitted
artifactory    | Caused by: java.io.FileNotFoundException: class path resource [jar:war:file:/opt/jfrog/artifactory/webapps/] cannot be resolved to URL because it does not exist
artifactory    |        at org.springframework.core.io.ClassPathResource.getURL(ClassPathResource.java:187)
artifactory    |        at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:413)
artifactory    |        at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:287)
artifactory    |        at org.springframework.context.support.AbstractApplicationContext.getResources(AbstractApplicationContext.java:1163)
artifactory    |        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:216)
artifactory    |        ... 16 common frames omitted
Dies here now.

@marcuschaney - can you contact our support with this? I think that you'll get a better response and help there<EMAIL_ADDRESS>Update this thread with the findings.

The lastest issue was due to a size limitation for the /var directory. Resized and was good to go:
lsblk
growpart /dev/xvda 2
pvresize /dev/xvda
lvexted -L +2G /dev/mapper/VolGroup00-varVol
resize2fs /dev/mapper/VolGroup00-varVol

Thanks for updating @marcuschaney! Happy it's resolved.


Unwise use of setattr prevents saving a cube to file

Iris NetCDF saving uses setattr to copy attributes to the NetCDF4-python object.  This causes problems if your source cube has an attribute which clash with  NetCDF4-python method names.  E.g. the ECHAM5 Aerocom simulations have contain the "dimensions" variable attribute which prevents saving a cube derived from this data.
# Executed from /group_workspaces/jasmin/cis/AeroCom/A2/MPIHAM_V2_KZ.A2.CTRL/download on JASMIN

import iris
cube = iris.load_cube('aerocom.MPIHAM_V2_KZ.AEROCOM_A2.CTRL.monthly.loadbc.2007.nc')
iris.save(cube, '/tmp/tmp.nc')

Causes the following stack trace in Iris 1.6.1:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/iris/io/__init__.py", line 341, in save
    saver(source, target, **kwargs)
  File "/usr/lib/python2.7/site-packages/iris/fileformats/netcdf.py", line 1568, in save
    least_significant_digit)
  File "/usr/lib/python2.7/site-packages/iris/fileformats/netcdf.py", line 671, in write
    self.update_global_attributes(global_attributes)
  File "/usr/lib/python2.7/site-packages/iris/fileformats/netcdf.py", line 695, in update_global_attributes
    setattr(self._dataset, attr_name, attributes[attr_name])
  File "netCDF4.pyx", line 1832, in netCDF4.Dataset.__setattr__ (netCDF4.c:23365)
AttributeError: 'dimensions' is one of the reserved attributes ('_grpid', '_grp', '_varid', 'groups', 'dimensions', 'variables', 'dtype', 'file_format', '_nunlimdim', 'path', 'parent', 'ndim', 'maskandscale', 'cmptypes', 'vltypes', '_isprimitive', '_isvlen', '_iscompound', '_cmptype', '_vltype'), cannot rebind. Use setncattr instead.

I am working with Iris 1.6.1 but I have confirmed the code still uses setattr.
The setncattr() method of NetCDF4-python has been provided to avoid this name clash.

Closed by #1326.


FileNotFoundError: [Errno 2] No such file or directory: 'texture.png'

You need to run the script from the source directory.

Open file main.py
search TEXTURE_PATH = 'texture.png'
replace it to TEXTURE_PATH = r'C:\Users\abc123\Desktop\Minecraft\texture.png'
C:\Users\abc123\Desktop\Minecraft is the folder which you save Minecraft

Open file main.py
search TEXTURE_PATH = 'texture.png'
replace it to TEXTURE_PATH = r'C:\Users\abc123\Desktop\Minecraft\texture.png'
C:\Users\abc123\Desktop\Minecraft is the folder which you save Minecraft

how to reproduce your issue?


Add serial frame detector

Description
This is a rehash of PR #441 as implemented by @Miceuz
The original review was complete, but changes to master have caused github to force-closed the PR. The branch as been rebased and this is the new PR for the same content.
Updates #159
General checklist:

[ ] I have performed a self-review, including - looked through the Files changed tab, browsed repository in my branch
[ ] I have made corresponding changes to the documentation - to reflect changes in code, electrical or mechanical design
[ ] All new documentation or graphics follow the documentation style guide
[ ] All new content is linked, easily discoverable, does not require too many clicks
[ ] I have reviewed any other relevant parts of our contributor wiki to ensure that this PR conforms to the standards
[ ] I have given the PR a descriptive name (prefixed with WIP if it is not yet ready for review)
[ ] I have tagged relevant reviewers

Code checklist:

[ ] All new code follows our code style
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have described tests I used to verify my changes, instructions for reproducing them and any relevant configuration details.
[ ] I ran the unit test suite and verified that all tests pass - new and old, locally and on CI
[ ] I performed a clean build and verified that there were no warnings
[ ] I ran our static analysis tools and verified there were no warnings
[ ] Any dependent changes have been merged and published in downstream modules

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: martukas:x: MiceuzYou have signed the CLA already but the status is still pending? Let us recheck it.


[Task]: Redeploy helm chart to fit latest version of apache-hop

What needs to happen?
When I do :
helm repo update && helm show chart apache-hop/hop

I still have appVersion: 1.2.0
We should have : appVersion: 2.5.0 (as described here)
Is it possible to deploy the chart to the latest version ? I saw there is a specific procedure to create a new helm release, but does this procedure can be done by any contributors ?
Does the release of the Helm Chart have to be sync with the release of apache-hop ?
Issue Priority
Priority: 3
Issue Component
Component: Containers

we can release it independently, I'll see if I can get it done today

.take-issue

New chart has been deployed and index has been updated.


Add optional hardening to systemd service

It's improved alternative to https://github.com/jedisct1/dnscrypt-proxy/pull/255 . DynamicUser=yes is commented out as I'm not sure if all targeted systems have needed systemd version.
It could be enabled by default in future. Users are supposed to edit this file themselves anyway so I hope this isn't a problem.

Merged, thanks!


Enhance ut

Description
Enhance UT, add status update
Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a.
Tests
CI/CD will cover

Seems Makefile is referencing these files, need to change that accordingly

Seems Makefile is referencing these files, need to change that accordingly

@lianhao thanks for point this out, this is supposed to be fixed and cleaned up in #346 , this change in this PR is unexpected due to git branch mess, I will undo it.


Migrate to Pathlib

It's time to consider migrating to Pathlib (thanks @browniebroke for raising the concern). Affected files:

pre_gen_project.py;
post_gen_project.py;
test_cookiecutter_generation.py;
manage.py;
wsgi.py;
merge_production_dotenvs_in_dotenv.py;
settings.

Just noting down that we currently cannot use it static-related settings due to an issue in Whitenoise.

@browniebroke @webyneter Is this a change you still wanted to make in the project as Whitenoise has resolved the issue now? Did you want to drop django-environ altogether as there looks to be functionality used in the project that wouldn't be covered by pathlib, but may not be necessary.

Would be nive to have it yes, but I don't think we want to drop django-environ.


Unit tests in buildkite can run faster with newer versions of erlang.

Installing different versions of erlang on base docker image can cut down the time taken to run unit tests.

The following PRs addressed the docker image updates requested by this ticket:

chef/release-engineering#911
chef/release-engineering#912
chef/release-engineering#915


Support tracing HTTP request and show related span?

For example, list_dogs is only showed without info related to the HTTP request

After using axum-tracing-opentelemtry, which adds a layer OtelAxumLayer to start span on incoming request, still no http span is showed.
Until init_tracing_opentelemetry::tracing_subscriber_ext::init_subscribers()?; it works then

I have no idea what's missing in setup opentelemetry here, hence let me to use init_tracing_opentelemetry

Hi, the http span is created at the TRACING level but I set a DEBUG level filter here:
let telemetry_layer = tracing_opentelemetry::layer().with_tracer(tracer);
let subscriber = tracing_subscriber::registry()
    .with(LevelFilter::from_level(Level::DEBUG))
    .with(telemetry_layer);

Change the level to TRACING or remove the filter and I think the http span will show up in the collector.


Divide Malware Removal Guide into smaller parts

Completed by commit https://github.com/omerwwazap/Security-Awareness/commit/fb56961e4a46a84095cb2f23ada9e9a6cef1fb86


Hacktoberfest: Collection of new Algorithms needed.

Hello folks,
Hacktoberfest has already started!
Still confused about what to contribute?
Let's make your task simpler.
This repository contains many algorithms. Found your favorite problem? Then star it 😄 . Can't see your favorite one? Then send a PR an add any algorithms of your choice(e.g. Sorting algorithms, Dynamic Programming, etc.) in your favorite programming language.
P.S.: Please make sure the file name itself is self-explanatory about the Algorithms or make a folder along containing your script and a README explaining the necessary details.

Hi ! I can add some.

Yeah sure!
Happy Coding!!

Hello!Can I Take This?

Hello!Can I Take This?

Please go ahead 😄

Thanks a lot, everyone making hacktober successful this year!!!
Will see you all next year again with some new collection. Till then keep coding!!


Update: nodeSelector

The other has been deprecated since kubernetes v1.14
update node selector
Updates the node selector to get rid off this warning:
service/headlamp created
Warning: spec.template.spec.nodeSelector[beta.kubernetes.io/os]: deprecated since v1.14; use "kubernetes.io/os" instead
deployment.apps/headlamp created

@yolossn or @knrt10 , can you verify what's the best approach here?

It makes sense, but make sure that the node also has the labels assigned. I checked it on minkube it did had the required label kubernetes.io/os.
So I guess the change makes sense.

I am not sure I understand the discussion. The label was there before but emits a deprecation warning.
I just updated it. I tested it on a k0s setup. It has the label as well.

@joaquimrocha Thank you!


Locate user to their current location after opening the app

I'm submitting a ...

[ ] bug report
[x] feature request

Current behavior:
The app opens default location of the map.
Expected behavior:
The app needs to locate the user to their current location as soon as the user opens the application
Steps to reproduce:
Open the app

I would like to take this up

I would like to work on it


Adds go1.18 to tests, moves default version to 1.17

This introduces go 1.18

Codecov Report

Merging #696 (e80e69a) into main (be0d9c6) will increase coverage by 2.4%.
The diff coverage is 72.9%.

@@           Coverage Diff           @@
##            main    #696     +/-   ##
=======================================
+ Coverage   73.3%   75.8%   +2.4%
=======================================
  Files        174     173      -1
  Lines      12187   11672    -515
=======================================
- Hits        8942    8848     -94
+ Misses      3007    2614    -393
+ Partials     238     210     -28

Impacted Files
Coverage Δ

attribute/set.go
61.8% <0.0%> (-1.8%)
:arrow_down:

attribute/value.go
88.9% <ø> (ø)

bridge/opencensus/aggregation.go
95.7% <ø> (ø)

exporters/otlp/internal/retry/retry.go
98.2% <ø> (ø)

...otlp/otlpmetric/internal/metrictransform/metric.go
78.1% <ø> (+0.2%)
:arrow_up:

.../otlp/otlpmetric/internal/otlpmetrictest/client.go
0.0% <0.0%> (ø)

...rs/otlp/otlpmetric/internal/otlpmetrictest/data.go
0.0% <0.0%> (ø)

...tlp/otlpmetric/internal/otlpmetrictest/otlptest.go
0.0% <0.0%> (ø)

exporters/otlp/otlptrace/exporter.go
0.0% <0.0%> (ø)

...rs/otlp/otlptrace/internal/otlptracetest/client.go
0.0% <0.0%> (ø)

... and 137 more


{AKS} Fix test case test_aks_create_and_update_with_node_restriction

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} Fix test case test_aks_create_and_update_with_node_restriction. The default version cannot meet the testing requirements (>1.22.0, <1.24.0). Select the appropriate k8s version for testing, if there is no suitable version, skip the test.

previously failed test run
passed test run

Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

AKS


How should we handle deleting datasets that are in failed import status?

This could probably be an entirely campus local process as no data exists except the upload zip and meta file.

For soft deletes, we mark in postgres that the dataset is deleted, then put the deleted flag into MinIO.
For hard deletes we wipe out the dataset directory as usual, but don't bother calling out to the uninstall plugins.


Compiler Expiration: clear on reload

Fix a bug where we wouldn't clear the expire timeout when replacing
the webpack compiler. Thus if you reloaded, {timeout} seconds later
it would kill the compiler, seemingly out of no-where.
Now we clear the timeout before replacing (in set) and before
removing it.

CR 🌵

dev_block 👍  on my own suggestion.

un_dev_block 👍

CR 🌵

CR :zap:


Transaction Comments - avoid redundant API calls

Since now refresh event added under build method, and build method get invoked multiple times, so do the API calls.

fixed


FileSystemProvider: unable to save with or reopen with encoding

Refs: https://github.com/Microsoft/vscode/issues/48421
Setup:

clone https://github.com/bpasero/remote-fs
F5
click "Refresh" in the explorer
you should see the current working directory as a remote folder using the file system provider for scheme datei://

Steps

open a file
click in the status bar on the encoding picker to either reopen or save with encoding

=> we do not seem to support this, nothing happens
/cc @jrieken

encoding.js:123 Uncaught (in promise) TypeError: Cannot read property 'end' of undefined
    at encoding.js:123
    at encoding.js:112
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:109)

@jrieken yes I was about to report, seems to originate from the toDecodeStream

This is some bizarre WinJS.Promise vs Promise thing

I do have a better understand of this and it's scary... During Promise.resolve (which is async) the winjs-promise resolves and goes into the success-state which is a oneway, e.g. it doesn't have a then-function. Somehow, tho Promise.resolve still holds on to that ends up calling it and boom. The take aways is to not use a winjs-promise in Promise.resolve.


perf: improve paragragh performance

summary
improve paragragh performance.
before optimize
goos: darwin
goarch: amd64
pkg: github.com/go-faker/faker/v4
cpu: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
BenchmarkParagraph
BenchmarkParagraph-12    	   21318	     50666 ns/op	   20836 B/op	     164 allocs/op
PASS
ok  	github.com/go-faker/faker/v4	1.833s

after optimize
goos: darwin
goarch: amd64
pkg: github.com/go-faker/faker/v4
cpu: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
BenchmarkParagraph
BenchmarkParagraph-12    	   25045	     43137 ns/op	   17784 B/op	      94 allocs/op
PASS
ok  	github.com/go-faker/faker/v4	1.867s

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (f70bf73) 89.04% compared to head (4a4ac53) 89.04%.
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   89.04%   89.04%
=======================================
  Files          12       12
  Lines        1762     1762
=======================================
  Hits         1569     1569
  Misses        138      138
  Partials       55       55

Files Changed
Coverage Δ

lorem.go
100.00% <100.00%> (ø)

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


Game crashes when trying to reload a new level

OS: Arch Linux
Git commit: 7d572ba
The game will crash when requested to reload a new level.
Steps to reproduce: On the main menu, press 'N' to create a new level, after the new level is created, press 'R' to reload the level.
Current behavior: The game will crash when trying to access the file_name of the level.
./nothing/src/game/level/level_editor.c:143: create_level_editor_from_file: Assertion `file_name' failed
Stacktrace:
../build/nothing(__trace_assert+0x28)[0x556813bdbfb8]
../build/nothing(create_level_editor_from_file+0xe16)[0x556813bd5626]
../build/nothing(game_event+0x45d)[0x556813bbbfdd]
../build/nothing(main+0x34e)[0x556813bb98de]
/usr/lib/libc.so.6(__libc_start_main+0xf2)[0x7f757c4daee2]
../build/nothing(_start+0x2d)[0x556813bb9a8d]

@cahe7cb thank you for reporting this! We will take a look at it on the next Nothing stream :+1:


Searching for only usernames in chat history (Ctrl + F)

Is your feature request related to a problem? Please describe.
When searching in chat history for a channel (Ctrl + F) it is not possible to search for only usernames. For example, if I want to search for my own username "Zanuh", it will reveal all users AND messages that contain that word.
Describe the solution you'd like
To be able to put an "@" before a word should only display usernames. For example, "@Zanuh" should only reveal messages from that specific user or users that contains that word.
Describe alternatives you've considered
Make it a preference in settings to have it on or off.
Additional context
Might already be a way to do this that I just don't know of.

What would be the result of searching @Zanuh @slch @admin or mail@domain?
Searching by user should be an additional field in form, i think.

I feel like you should be able to search for mentions and having an additional field is not that pretty either imo (maybe can work, need to see how it would look like)
At the moment you can search for a user's messages by suffixing his name with : as the search is tested against the whole line and not the only name and message.

Couldn't you search for Zanuh: and 99% of the messages would be yours?

@fourtf, yeah, actually that works very good, then no need for me to having to add @ before.


Unwrap error messages generated by jQuery Validation

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/905677
When the jQuery Validation plugin finds an issue with an input field, it adds a span containing the error message to a span that has role=alert. As a result, Narrator reads alert group <the error message>. This is because Narrator thinks the div is a group containing multiple elements instead of just one. Furthermore, the jQuery Validation plugin only supports a single error message for every field, so there will never be more than one error message anyway, so wrapping the error message in a container is invalid.
To fix this, I have added some post-processing logic that gets rid of the nested span and moves the error message to the parent span.
To demonstrate what is going on here...
Before post-processing:
<input name="a" aria-describedby="error" />

    Invalid input!

After post-processing:
<input name="a" aria-describedby="validation-container" />
Invalid input!

Does anything depend on that "error" ID?

@joelverhagen - as far as I can tell, the only thing that depends on the error ID (error in the example) is the aria-describedby in the input, which I properly update to point to the ID of the validation container.


Upgrading to slack-scala-client 1.0.0 and switching to Pekko

Upgrading to slack-scala-client 1.0.0 which involves getting rid of Akka in favor of Pekko.

Trying to remember what I did with PR.
Trying to run tests locally.

./gradlew build (which uses 2.12) passes locally as in CI
../gradlew build --no-build-cache -PscalaVersion=2.13.10 fails locally (as in CI) because of multiple:

            Caused by: java.lang.UnsupportedClassVersionError at PostCommandWithSlackThreadTest.scala:33

errors
And these in turn are because the underlying library (Play) started to require Java 11+ for 2.13 builds as mentioned in https://github.com/slack-scala-client/slack-scala-client/releases/tag/v1.0.0


LXD socket with write permissions not found when running terraform apply

Bug Description
Terraform errors out when trying to apply the plan.
To Reproduce

terraform init
terraform apply -auto-approve

Environment

Ubuntu 24.04
LXD: 5.21/stable

Relevant log output
ubuntu@canonical:~/charmed-aether-sd-core/terraform$ terraform apply -auto-approve

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # lxd_instance.control-plane will be created
  + resource "lxd_instance" "control-plane" {
      + config           = {
          + "boot.autostart" = "true"
        }
      + description      = ""
      + ephemeral        = false
      + image            = "ubuntu:24.04"
      + interfaces       = (known after apply)
      + ipv4_address     = (known after apply)
      + ipv6_address     = (known after apply)
      + limits           = {
          + "cpu"    = "4"
          + "memory" = "8GB"
        }
      + mac_address      = (known after apply)
      + name             = "control-plane"
      + profiles         = [
          + "default",
        ]
      + running          = true
      + status           = (known after apply)
      + target           = (known after apply)
      + type             = "virtual-machine"
      + wait_for_network = true

      + device {
          + name       = "eth0"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-mgmt"
            }
          + type       = "nic"
        }
      + device {
          + name       = "root"
          + properties = {
              + "path" = "/"
              + "pool" = "sdcore-pool"
              + "size" = "40GB"
            }
          + type       = "disk"
        }
    }

  # lxd_instance.gnbsim will be created
  + resource "lxd_instance" "gnbsim" {
      + config           = {
          + "boot.autostart"            = "true"
          + "cloud-init.network-config" = <<-EOT
                network:
                  version: 2
                  ethernets:
                    mgmt:
                      match:
                        name: enp5s0
                      dhcp4: true
                    ran:
                      match:
                        name: enp6s0
                      dhcp4: true
                      dhcp4-overrides:
                        use-routes: false
                      routes:
                        - to: <IP_ADDRESS>/24
                          via: <IP_ADDRESS>
                          metric: 1
            EOT
        }
      + description      = ""
      + ephemeral        = false
      + image            = "ubuntu:24.04"
      + interfaces       = (known after apply)
      + ipv4_address     = (known after apply)
      + ipv6_address     = (known after apply)
      + limits           = {
          + "cpu"    = "2"
          + "memory" = "3GB"
        }
      + mac_address      = (known after apply)
      + name             = "gnbsim"
      + profiles         = [
          + "default",
        ]
      + running          = true
      + status           = (known after apply)
      + target           = (known after apply)
      + type             = "virtual-machine"
      + wait_for_network = true

      + device {
          + name       = "eth0"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-mgmt"
            }
          + type       = "nic"
        }
      + device {
          + name       = "eth1"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-ran"
            }
          + type       = "nic"
        }
      + device {
          + name       = "root"
          + properties = {
              + "path" = "/"
              + "pool" = "sdcore-pool"
              + "size" = "20GB"
            }
          + type       = "disk"
        }
    }

  # lxd_instance.juju-controller will be created
  + resource "lxd_instance" "juju-controller" {
      + config           = {
          + "boot.autostart" = "true"
        }
      + description      = ""
      + ephemeral        = false
      + image            = "ubuntu:24.04"
      + interfaces       = (known after apply)
      + ipv4_address     = (known after apply)
      + ipv6_address     = (known after apply)
      + limits           = {
          + "cpu"    = "4"
          + "memory" = "6GB"
        }
      + mac_address      = (known after apply)
      + name             = "juju-controller"
      + profiles         = [
          + "default",
        ]
      + running          = true
      + status           = (known after apply)
      + target           = (known after apply)
      + type             = "virtual-machine"
      + wait_for_network = true

      + device {
          + name       = "eth0"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-mgmt"
            }
          + type       = "nic"
        }
      + device {
          + name       = "root"
          + properties = {
              + "path" = "/"
              + "pool" = "sdcore-pool"
              + "size" = "40GB"
            }
          + type       = "disk"
        }
    }

  # lxd_instance.user-plane will be created
  + resource "lxd_instance" "user-plane" {
      + config           = {
          + "boot.autostart"            = "true"
          + "cloud-init.network-config" = <<-EOT
                network:
                  version: 2
                  ethernets:
                    mgmt:
                      match:
                        name: enp5s0
                      dhcp4: true
                    core:
                      match:
                        name: enp6s0
                      dhcp4: true
                      dhcp4-overrides:
                        use-routes: false
                      routes:
                        - to: <IP_ADDRESS>/24
                          via: <IP_ADDRESS>
                          metric: 1
                    access:
                      match:
                        name: enp7s0
                      dhcp4: true
                      dhcp4-overrides:
                        use-routes: false
                      routes:
                        - to: <IP_ADDRESS>/24
                          via: <IP_ADDRESS>
                          metric: 1
            EOT
        }
      + description      = ""
      + ephemeral        = false
      + image            = "ubuntu:24.04"
      + interfaces       = (known after apply)
      + ipv4_address     = (known after apply)
      + ipv6_address     = (known after apply)
      + limits           = {
          + "cpu"    = "4"
          + "memory" = "12GB"
        }
      + mac_address      = (known after apply)
      + name             = "user-plane"
      + profiles         = [
          + "default",
        ]
      + running          = true
      + status           = (known after apply)
      + target           = (known after apply)
      + type             = "virtual-machine"
      + wait_for_network = true

      + device {
          + name       = "eth0"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-mgmt"
            }
          + type       = "nic"
        }
      + device {
          + name       = "eth1"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-core"
            }
          + type       = "nic"
        }
      + device {
          + name       = "eth2"
          + properties = {
              + "ipv4.address" = "<IP_ADDRESS>"
              + "network"      = "sdcore-access"
            }
          + type       = "nic"
        }
      + device {
          + name       = "root"
          + properties = {
              + "path" = "/"
              + "pool" = "sdcore-pool"
              + "size" = "20GB"
            }
          + type       = "disk"
        }
    }

  # lxd_instance_file.control-plane-privkey will be created
  + resource "lxd_instance_file" "control-plane-privkey" {
      + content     = (sensitive value)
      + gid         = 1000
      + instance    = "control-plane"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/id_rsa"
      + uid         = 1000
    }

  # lxd_instance_file.control-plane-pubkey will be created
  + resource "lxd_instance_file" "control-plane-pubkey" {
      + content     = (known after apply)
      + gid         = 1000
      + instance    = "control-plane"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/authorized_keys"
      + uid         = 1000
    }

  # lxd_instance_file.gnbsim-privkey will be created
  + resource "lxd_instance_file" "gnbsim-privkey" {
      + content     = (sensitive value)
      + gid         = 1000
      + instance    = "gnbsim"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/id_rsa"
      + uid         = 1000
    }

  # lxd_instance_file.gnbsim-pubkey will be created
  + resource "lxd_instance_file" "gnbsim-pubkey" {
      + content     = (known after apply)
      + gid         = 1000
      + instance    = "gnbsim"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/authorized_keys"
      + uid         = 1000
    }

  # lxd_instance_file.juju-controller-privkey will be created
  + resource "lxd_instance_file" "juju-controller-privkey" {
      + content     = (sensitive value)
      + gid         = 1000
      + instance    = "juju-controller"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/id_rsa"
      + uid         = 1000
    }

  # lxd_instance_file.juju-controller-pubkey will be created
  + resource "lxd_instance_file" "juju-controller-pubkey" {
      + content     = (known after apply)
      + gid         = 1000
      + instance    = "juju-controller"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/authorized_keys"
      + uid         = 1000
    }

  # lxd_instance_file.user-plane-privkey will be created
  + resource "lxd_instance_file" "user-plane-privkey" {
      + content     = (sensitive value)
      + gid         = 1000
      + instance    = "user-plane"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/id_rsa"
      + uid         = 1000
    }

  # lxd_instance_file.user-plane-pubkey will be created
  + resource "lxd_instance_file" "user-plane-pubkey" {
      + content     = (known after apply)
      + gid         = 1000
      + instance    = "user-plane"
      + mode        = "0600"
      + resource_id = (known after apply)
      + target_path = "/home/ubuntu/.ssh/authorized_keys"
      + uid         = 1000
    }

  # lxd_network.sdcore-access will be created
  + resource "lxd_network" "sdcore-access" {
      + config      = {
          + "dns.mode"     = "none"
          + "ipv4.address" = "<IP_ADDRESS>/24"
          + "ipv4.nat"     = "false"
          + "ipv6.address" = "none"
        }
      + managed     = (known after apply)
      + name        = "sdcore-access"
      + type        = "bridge"
        # (1 unchanged attribute hidden)
    }

  # lxd_network.sdcore-core will be created
  + resource "lxd_network" "sdcore-core" {
      + config      = {
          + "dns.mode"     = "none"
          + "ipv4.address" = "<IP_ADDRESS>/24"
          + "ipv4.nat"     = "true"
          + "ipv6.address" = "none"
        }
      + managed     = (known after apply)
      + name        = "sdcore-core"
      + type        = "bridge"
        # (1 unchanged attribute hidden)
    }

  # lxd_network.sdcore-mgmt will be created
  + resource "lxd_network" "sdcore-mgmt" {
      + config      = {
          + "dns.domain"   = "mgmt"
          + "dns.mode"     = "managed"
          + "ipv4.address" = "<IP_ADDRESS>/24"
          + "ipv4.nat"     = "true"
          + "ipv6.address" = "none"
          + "raw.dnsmasq"  = <<-EOT
                host-record=amf.mgmt,<IP_ADDRESS>
                host-record=upf.mgmt,<IP_ADDRESS>
            EOT
        }
      + managed     = (known after apply)
      + name        = "sdcore-mgmt"
      + type        = "bridge"
        # (1 unchanged attribute hidden)
    }

  # lxd_network.sdcore-ran will be created
  + resource "lxd_network" "sdcore-ran" {
      + config      = {
          + "dns.mode"     = "none"
          + "ipv4.address" = "<IP_ADDRESS>/24"
          + "ipv4.nat"     = "false"
          + "ipv6.address" = "none"
        }
      + managed     = (known after apply)
      + name        = "sdcore-ran"
      + type        = "bridge"
        # (1 unchanged attribute hidden)
    }

  # lxd_storage_pool.sdcore-pool will be created
  + resource "lxd_storage_pool" "sdcore-pool" {
      + config      = {}
      + driver      = "dir"
      + name        = "sdcore-pool"
        # (1 unchanged attribute hidden)
    }

  # tls_private_key.juju-key will be created
  + resource "tls_private_key" "juju-key" {
      + algorithm                     = "RSA"
      + ecdsa_curve                   = "P224"
      + id                            = (known after apply)
      + private_key_openssh           = (sensitive value)
      + private_key_pem               = (sensitive value)
      + private_key_pem_pkcs8         = (sensitive value)
      + public_key_fingerprint_md5    = (known after apply)
      + public_key_fingerprint_sha256 = (known after apply)
      + public_key_openssh            = (known after apply)
      + public_key_pem                = (known after apply)
      + rsa_bits                      = 4096
    }

Plan: 18 to add, 0 to change, 0 to destroy.
lxd_network.sdcore-access: Creating...
lxd_network.sdcore-core: Creating...
lxd_storage_pool.sdcore-pool: Creating...
lxd_network.sdcore-ran: Creating...
lxd_network.sdcore-mgmt: Creating...
tls_private_key.juju-key: Creating...
tls_private_key.juju-key: Creation complete after 2s [id=5be3a2b443d0ab52822da0a43bf66d2605981800]
╷
│ Error: Failed to retrieve LXD InstanceServer
│
│   with lxd_storage_pool.sdcore-pool,
│   on main.tf line 13, in resource "lxd_storage_pool" "sdcore-pool":
│   13: resource "lxd_storage_pool" "sdcore-pool" {
│
│ LXD socket with write permissions not found. Searched LXD directories: [/var/lib/lxd /var/snap/lxd/common/lxd]
╵
╷
│ Error: Failed to retrieve LXD InstanceServer
│
│   with lxd_network.sdcore-mgmt,
│   on main.tf line 18, in resource "lxd_network" "sdcore-mgmt":
│   18: resource "lxd_network" "sdcore-mgmt" {
│
│ LXD socket with write permissions not found. Searched LXD directories: [/var/lib/lxd /var/snap/lxd/common/lxd]
╵
╷
│ Error: Failed to retrieve LXD InstanceServer
│
│   with lxd_network.sdcore-access,
│   on main.tf line 35, in resource "lxd_network" "sdcore-access":
│   35: resource "lxd_network" "sdcore-access" {
│
│ LXD socket with write permissions not found. Searched LXD directories: [/var/lib/lxd /var/snap/lxd/common/lxd]
╵
╷
│ Error: Failed to retrieve LXD InstanceServer
│
│   with lxd_network.sdcore-core,
│   on main.tf line 47, in resource "lxd_network" "sdcore-core":
│   47: resource "lxd_network" "sdcore-core" {
│
│ LXD socket with write permissions not found. Searched LXD directories: [/var/lib/lxd /var/snap/lxd/common/lxd]
╵
╷
│ Error: Failed to retrieve LXD InstanceServer
│
│   with lxd_network.sdcore-ran,
│   on main.tf line 59, in resource "lxd_network" "sdcore-ran":
│   59: resource "lxd_network" "sdcore-ran" {
│
│ LXD socket with write permissions not found. Searched LXD directories: [/var/lib/lxd /var/snap/lxd/common/lxd]
╵

Additional context
No response

Closing as the root cause is the same as #62


Cloning causes issue

When I clone this Git using my desktop, it clones in a folder named Jenkins-Autobuild.  I think if you rename this project to Autobuild, it would be able to clone directly to Autobuild where you have some hard-coded links in batch files.  Right now I have to download it as zip and unzip in the C:\Autobuild\ location.

You can use the  option to clone into a folder you'd like. Thanks for bringing this up, I updated the readme in commit 1f1a2c3 to prevent other from finding it out the hard way.