Automatically keep I22 and P38 in sync

As a developer I would like to keep P38, at least from an ophyd point of view, as a close representation of I22. Currently they are treated as different beamlines with some similar components.
Possible Solution
Could we somehow define different versions of particular devices?
Acceptance Criteria

TBD

A possible solution is to use the same beamline module for both, with careful @skip_device usage and care for visit directories- p38 is only ever going to be a commissioning visit(?)

I would suggest more than just d11 and saxs in the same beamline module. I would suggest that we day d11 is saxs, or at least a testing representation of it. So the ophyd devices of P38 are a 1:1 representation of I22, even if we have to mock some devices.

are the PV names the same? What is stopping us from using the file as-is?
should we have BEAMLINE_NAME derived from venv?

BL = get_beamline_name("p38")
Checks Environment Variables to see if BEAMLINE is exported (it will be on a beamline control machine).
Comparing p38.py and i22.py:
(best guess):
d11 ~ saxs: "-DI-DCAM-03:" vs. "-EA-PILAT-01:",
d12 ~ waxs: "-DI-DCAM-04:" vs. "-EA-PILAT-03:",
d3 ~ oav: "-DI-DCAM-01:" vs. "-DI-OAV-01:"
i0 ~ i0: "-EA-XBPM-01:" vs. "-EA-XBPM-02:"
linkam ~ linkam: "-EA-LINKM-02:" vs. "-EA-TEMPC-05",
panda1/2/3: match
panda4, it: no equivalent device on p38
all others: sim devices on p38
d11, d12 shouldn't be exposed as -EA-PILAT-01, as they aren't Pilatuses (? should we allow this? Hopefully all plan stubs are written for StandardDetectors?)
it should be added as a sim device or else repeating the values from i0 (?)
Definitely the Linkam and TetrAMM could be exposed on the same prefix

then we have the manual option of just applying a ternary expression for the PVs /  or an if block
or we could make some decorator or such.
we'd also need to make it crash for panda4 I guess if there is an attempt to use it in a plan???

The specific case of a detector being a PilatusDetector if it's i22 and an AravisDetector if it's p38 is what's interesting here...

ok why not just a ternary expression?
not sure how different are the params, will explore this in a branch

To add some concrete acceptance criteria:

There should be one module, i22.py, p38.py should be deleted
dodal connect i22 should work without errors when the I22 PVs are available
dodal connect i22 --profile p38 or BEAMLINE=p38 dodal connect i22 (syntax can differ) should work when the P38 PVs are available
There should be no errors in either case, dodal should handle the differences between the beamlines

I guessed some of those, but it's great to see this clearly. Thanks!

BEAMLINE=p38 dodal connect i22 will test this tomorrow, together with this
https://github.com/DiamondLightSource/i22-bluesky/issues/87
@DiamondJoseph please advise


shell-hist: init at 0.1.0

Motivation for this change
Things done

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

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

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

Pushed an update :+1:

tested with nix-review, worked fine!


L125172: Adding break-line before snippet

Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
Description: Missing break-line before snippet is preventing content to show properly.

Hi @AndriySvyryd can you please by merging this PR?
Thanks in advance.

Thanks @smitpatel


trigger build for prefect

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d7ntwgfax9/clone/recipe/meta.yaml:0: missing_version_or_name: The recipe is missing name and/or version
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_99y08t20op/clone/recipe/meta.yaml:0: missing_version_or_name: The recipe is missing name and/or version
Errors were found


Feature request: Allow editing of existing text

https://github.com/AlecAivazis/survey/issues/196

Done in 2.5.0


Install fails on OSX

Hello!
install fails when i try to in install it via npm:
~ [ sudo npm install -g mancy                                                                                ] 3:35 PM
(node:17550) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "mancy"
npm ERR! node v6.0.0
npm ERR! npm  v3.4.0
npm ERR! code EREADFILE

npm ERR! Error extracting /Users/nicolas/.npm/mancy/2.2.2/package.tgz archive: ENOENT: no such file or directory, open '/Users/nicolas/.npm/mancy/2.2.2/package.tgz'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/nicolas/npm-debug.log
~ [ npm install -g mancy                                                                                ] 3:36 PM
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "mancy"
npm ERR! node v4.2.2
npm ERR! npm  v3.4.0
npm ERR! code EREADFILE

npm ERR! Error extracting /Users/nicolas/.npm/mancy/2.2.2/package.tgz archive: ENOENT: no such file or directory, open '/Users/nicolas/.npm/mancy/2.2.2/package.tgz'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

@nschurmann v2.2.2 is old. May be try npm uninstall -g mancy and then install.

@princejwesley doesn't work, keeps throwing same error :(

I can able to install from npm.
~ 🙈 ₹ npm install -g mancy
/usr/local/bin/mancy -> /usr/local/lib/node_modules/mancy/cli.js

><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/mancy
> node download.js

Downloading Mancy-darwin-x64.zip
[============================================>] 100.0% of 48.11 MB (791.96 kB/s)
/usr/local/lib
└─┬<EMAIL_ADDRESS>..
    └──<EMAIL_ADDRESS>

Try clean the cache npm cache clean or remove the cache directory in ~/.npm/mancy

still :(
Sites/deed-backend [ npm cache clean                                                                                master * ] 11:18 AM
Sites/deed-backend [ npm install -g mancy                                                                                master * ] 11:19 AM
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "mancy"
npm ERR! node v4.2.2
npm ERR! npm  v3.4.0
npm ERR! code EREADFILE

npm ERR! Error extracting /Users/nicolas/.npm/mancy/2.2.2/package.tgz archive: ENOENT: no such file or directory, open '/Users/nicolas/.npm/mancy/2.2.2/package.tgz'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/nicolas/Sites/deed-backend/npm-debug.log
Sites/deed-backend [ rm -rf ~/.npm/mancy                                                                                master * ] 11:19 AM
Sites/deed-backend [ npm install -g mancy                                                                                master * ] 11:19 AM
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "mancy"
npm ERR! node v4.2.2
npm ERR! npm  v3.4.0
npm ERR! code EREADFILE

npm ERR! Error extracting /Users/nicolas/.npm/mancy/2.2.2/package.tgz archive: ENOENT: no such file or directory, open '/Users/nicolas/.npm/mancy/2.2.2/package.tgz'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/nicolas/Sites/deed-backend/npm-debug.log

any way to force install 3.0.0?

Yes, npm install -g<EMAIL_ADDRESS>

yay!, it worked ^^, now i have other issue with typescript.


[macOS] Improved exceptions

This fixes #32, thanks to @Plutoberth for the suggestion of using a promise.
Now it blocks until the device is fully connected.
Also shows an alert to displays the exception.
Compiled version

Thanks!

No problem, here's a new compiled version

@semvis123 A new release was created with the bugfix

Whoops just noticed that you can distribute an app (yes, this is my first time distributing apps lol)
This compiled version is only ~310kb instead of ~650 kb, probably because it removed the debug stuff.
SonyHeadphonesClient.app.zip

Whoops just noticed that you can distribute an app (yes, this is my first time distributing apps lol)
This compiled version is only ~310kb instead of ~650 kb, probably because it removed the debug stuff.
SonyHeadphonesClient.app.zip

OK. I replaced the binary.

I got this issue. Could you guys help check ? Im using WF-SP800N :(

@kieuson93 Hi, do you have access to a Windows / Linux PC for testing? I can just make it log all messages from both sides so you could send me a transcript.


[Question] Does websocket support add some parameters after method GET?

How should i do if i want to add some string after method GET ?
The string likes GET /token=xxxxx HTTP/1.1.
Thanks for response.
Here is my code but it cause exception because RealWebSocket will verify method.
        Request request = new Request.Builder().url(mUrl)
                .method("GET /token=xxxxx HTTP/1.1.")
                .header("Origin",ori)
                .header("Host", host)
                .build();
        mHttpClient.newWebSocket(request, mWebSocketListener);

public RealWebSocket(Request request, WebSocketListener listener, Random random) {
    if (!"GET".equals(request.method())) {
      throw new IllegalArgumentException("Request must be GET: " + request.method());
    }
   ....

Sorry, i found how to set it. Thanks.


allow custom functions to override default behavior

@ctsims @czue

:+1: from me but will let someone else merge

thanks for quick turnaround! what release will this be in

hopefully 2.21 which I think is freezing today or Monday
On Fri, Apr 24, 2015 at 3:07 PM, Cory Zue<EMAIL_ADDRESS>wrote:

thanks for quick turnaround! what release will this be in
—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/javarosa/pull/78#issuecomment-96037984.

@ctsims good call, updated. if we change the signature of the eval() method will this break anything?

@ctsims @czue added unit tests, verified working after fixing a dump bug. this is gtg

@phillipm updated


Remove NetworkConnection.isConnected because it's pointless. It was always true when called from NetworkConnection(address, connId) constructor and always false when called from NetworkConnection(address) constructor, which was for the local connection.

after removing hostId, it turns out that this field is useless unless I am missing something.
will test in my assets now..

Users could be using this no?
perhaps we can put an [Obsolete]  on it for a few days first?

See #462


[Feature Request] Use inherited numbering for TOC numbering

What I mean is, if I have these headings:
# Top level
## First  top level
## Second  below top level

# New Top Level
## First below "New Top Level"
## Second below "New Top Level"

It'd be cool if we could number them like this:

Top Level
1.1 First Top Level
1.2 Second Top Level

New Top Level
2.1 First below new top Level
2.2 Second below new top level

Rather than always starting at 1. as is the only feature I can find in the current build.
Thank you!

It is possible but then the problem is they are no longer lists since Markdown doesn't allow list like 1.1
1. one
   1. another one
2. two

one

another one

two

On selection

1. one
   1.1 another one
2. two

one
1.1 another one
two

On selection

I didn't even realize it needed to be a proper list.  I was just used to using "Markdown TOC" by AlanWalk and the numbering is made that way by default.
I think the difference is that his add-on numbers the actual headings in your document and then the TOC is build based off that.
My workaround currently is to just use his for the numbering then yours for the actual TOC build, as his TOC builder has broken for me recently.
Thanks for the reply and the awesome add-on!


[VFS-664] Fix for file names with exclamation mark can not be read

This is a fix for problems that file names with exclamation mark in zip file can not be successfully be read.
And this problem also exists in tar, tgz and tbz2. The fix for them are also included in this PR.

And it seems the VFS-225 is a duplicate issue with this one.


{Role} ad sp create-for-rbac: Retry Service Principal creation for "must in the local tenant" error

Description
Fix #14767
The retry-able check logic is firstly added by #1499:
https://github.com/Azure/azure-cli/blob/f0dcfcf5eb8413496ad7f3d4f871045d5386a099/src/command_modules/azure-cli-role/azure/cli/command_modules/role/custom.py#L492
It was later changed by #2567 (not sure why the change):
https://github.com/Azure/azure-cli/blob/67d44a187229f4b3872b8fc1401144492a778f18/src/command_modules/azure-cli-role/azure/cli/command_modules/role/custom.py#L508
This PR simply adds another retry-able check for

When using this permission, the backing application of the service principal being created must in the local tenant

just like what https://github.com/microsoft/onefuzz/pull/716 does.
Testing Guide
With new Knack (https://github.com/microsoft/knack/pull/228):
> pytest src\azure-cli\azure\cli\command_modules\role\tests\latest\test_graph.py::CreateForRbacScenarioTest::test_create_for_rbac_retry --override-ini log_cli=true

--------------------------------------- live log call ---------------------------------------
WARNING  cli.azure.cli.command_modules.role.custom:custom.py:1466 Creating service principal failed with error 'The appId '00000000-0000-0000-0000-000000000000' of the service principal does not reference a valid application object.'. Retrying: 1/36
WARNING  cli.azure.cli.command_modules.role.custom:custom.py:1466 Creating service principal failed with error 'When using this permission, the backing application of the service principal being created must in the local tenant'. Retrying: 2/36
WARNING  cli.azure.cli.command_modules.role.custom:custom.py:1505 The output includes credentials that you must protect. Be sure that you do not include these credentials in your code or check the credentials into your source control. For more information, see https://aka.ms/azadsp-cli
PASSED                                                                                [100%]

Additional Context
As https://github.com/Azure/azure-cli/pull/2567#pullrequestreview-28002303 pointed out, this is indeed very ugly.

Role

Hi @jiasli , thanks for your time to add the comment at https://github.com/Azure/azure-cli/issues/18610. We understand the new version CLI has added the retry logical. May I know the permanent fix whether is in the recent version update plan?

May I know the permanent fix whether is in the recent version update plan?

Sorry I didn't get your question.
According to https://github.com/Azure/azure-cli/commit/5544a0f3bc32aa778d296f71c4d37e48f8ebe691, this fix has been included since azure-cli-2.22.0.


Creating template does not work

Executing

oc create -f templates/aspnet-s2i-template.json -n openshift

or

oc create templates/aspnet-s2i-template.json -n openshift

does not work. This is a relative path.

what is the commands did you run?   There is also an assumption that you would have git cloned this project into your location machine before running the oc create command.

@charlesrichard Do you have a status on this issue?

This actually isn't a duplicate of #18, but seems to be a permission issue. When I try this I get:
$ oc create -f templates/aspnet-s2i-template.json -n openshift
Error from server: error when creating "templates/aspnet-s2i-template.json": User "developer" cannot create templates in project "openshift"

And indeed I (developer) don't have write/view access to project openshift:
$ oc get projects | grep openshift
<nothing>

This works when logged in as system:admin for example:
$ oc whoami
system:admin
$ oc create -f aspnet-s2i-template.json -n openshift
template "aspnet-s2i" created
$ oc get projects | grep openshift
openshift                           Active
openshift-infra                     Active

There is nothing the sample app can do other than updating the documentation, which I'll do as a follow up. Closing this issue.

There is nothing the sample app can do other than updating the documentation, which I'll do as a follow up.

Actually from the README:
 "Using a user with permissions to modify resources in the openshift project ..."

So it is documented.


Add index html

This is just a simple web site generated with ChatGPT.
Ideally we would like to have something like https://karpenter.sh/ or https://kueue.sigs.k8s.io/ .
Please feel free to make any additional changes. Thanks!

Thanks! Will merge this for now, but that looks definitely better.


@FeignClient with top level @RequestMapping annotation is also registered as Spring MVC handler

This is follow up to the discussion from this issue: https://github.com/spring-cloud/spring-cloud-netflix/issues/457
Generally the problem is that: when you annotate an @FeignClient interface with @RequestMapping annotation the handler will be also registered within Spring MVC.
Example:
@FeignClient("localapp")

@RequestMapping(value = "/users")

public interface UsersClient extends CrudClient<User> {

}

In this test case: https://github.com/jmnarloch/spring-cloud-netflix/commit/2d24bf630e57f6aec012983b4465c8cc8875dea7 this acctually causes the test to fail with error:
Caused by: java.lang.IllegalStateException: Ambiguous mapping. Cannot map 'feignHttpClientTests$UserClient' method
public abstract T org.springframework.cloud.netflix.feign.valid.FeignHttpClientTests$CrudClient.get(long)
to {[/users/{id}],methods=[GET]}: There is already 'feignHttpClientTests.Application' bean method
public java.lang.Object org.springframework.cloud.netflix.feign.valid.FeignHttpClientTests$Application.get(long) mapped.
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$MappingRegistry.assertUniqueMethodMapping(AbstractHandlerMethodMapping.java:565)
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping$MappingRegistry.register(AbstractHandlerMethodMapping.java:529)
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.registerHandlerMethod(AbstractHandlerMethodMapping.java:252)
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.detectHandlerMethods(AbstractHandlerMethodMapping.java:223)
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.initHandlerMethods(AbstractHandlerMethodMapping.java:183)
    at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.afterPropertiesSet(AbstractHandlerMethodMapping.java:164)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.afterPropertiesSet(RequestMappingHandlerMapping.java:134)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
    ... 44 more

Due to duplicated Spring MVC - FeignClient mappings, but this how I found this issue.
Removing the top @RequestMapping fixes the tests, but disallows some advances usages like interface inheritance and path overriding.

So is there some neat way to hide the @RequestMapping annotation on the interface type?
I guess that it's being exposed through FeignClientFactoryBean#getObjectType method.

There's no way to hide it other than not be in a web application.  Or I guess put it in a child context with no handler mappings. I don't expect this will be explicitly supportable in the framework, but if you try it and it works it might be good to share your experience here.

Hmm... Do you happen to know any other options to approach this problem, some RequestHandlerMapping overriding or maybe some other idea?

Closing, this would need to change in the framework.

Does it have any new progress?

@succour this issue is closed and we cannot fix it as this how spring framework works.

could we not get around this by just extending the WebMvcConfigurationSupport to ignore classes annotated with @RequestMapping AND @FeignClient?   Something like this?  It appears to be working.
@Configuration
public class WebConfiguration extends WebMvcConfigurationSupport {

	@Override
	protected RequestMappingHandlerMapping createRequestMappingHandlerMapping() {
  	RequestMappingHandlerMapping mapping = new RequestMappingHandlerMapping(){
			@Override
			protected boolean isHandler(Class<?> beanType) {
				return super.isHandler(beanType) && (AnnotationUtils.findAnnotation(beanType, FeignClient.class) == null);
			}
  	};
  	return mapping;
	}
}

That's a decent workaround. I'm not sure I want that code to be in Spring Cloud though. IMO Spring MVC should not consider a bean without a @Controller annotation to be a handler. You'd have to take that up in JIRA though.

I agree this should not exist in spring-cloud but only as a specific workaround for this issue.  I also agree with your other point about @Controller but that ship has sail and it would be a major breaking change to revert that now.  In the mean time, we need to manage clients. IMO they are easier to maintain with the @RequestMapping annotations, and applying it at the Class level reduces the need for each method's @ReqeustMapping to set its consumes/produces property, making the file much easier to read and maintain.
Long term, it would be great if we could delegate the isHandler method to a Bean, then spring-cloud-netflix could supply a version that does take the @FeignClient into consideration to avoid the bindings.

We have worked around it by using anotation on method only
joevalerio<EMAIL_ADDRESS>schrieb am Mi., 20. Juli 2016, 18:18:

I agree this should not exist in spring-cloud but only as a specific
workaround for this issue. I also agree with your other point about
@Controller https://github.com/Controller but that ship has sail and it
would be a major breaking change to revert that now. In the mean time, we
need to manage clients. IMO they are easier to maintain with the
@RequestMapping annotations, and applying it at the Class level reduces the
need for each method's @ReqeustMapping to set its consumes/produces
property, making the file much easier to read and maintain.
Long term, it would be great if we could delegate the isHandler method to
a Bean, then spring-cloud-netflix could supply a version that does take the
@FeignClient into consideration to avoid the bindings.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-netflix/issues/466#issuecomment-234000603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYARoXzsDgJ-tBQoTmLSjlpZhl1NCvcks5qXkpEgaJpZM4FhB-m
.

What about doing:
@Configuration
@ConditionalOnClass({Feign.class})
public class FeignMappingDefaultConfiguration {
    @Bean
    public WebMvcRegistrations feignWebRegistrations() {
        return new WebMvcRegistrationsAdapter() {
            @Override
            public RequestMappingHandlerMapping getRequestMappingHandlerMapping() {
                return new FeignFilterRequestMappingHandlerMapping();
            }
        };
    }

    private static class FeignFilterRequestMappingHandlerMapping extends RequestMappingHandlerMapping {
        @Override
        protected boolean isHandler(Class<?> beanType) {
            return super.isHandler(beanType) && (AnnotationUtils.findAnnotation(beanType, FeignClient.class) == null);
        }
    }
}

@kadaan thank for your code, it's working great :)

@kadaan thank for your code.

@kadaan  thank for your code.

@kadaan thank for your code.

`@Configuration
@ConditionalOnClass({ Feign.class })
public class FeignMappingDefaultConfiguration {
@Bean
public WebMvcRegistrations feignWebRegistrations() {
return new WebMvcRegistrationsAdapter() {
@Override
public RequestMappingHandlerMapping getRequestMappingHandlerMapping() {
return new FeignFilterRequestMappingHandlerMapping();
}
};
}
@Slf4j
private static class FeignFilterRequestMappingHandlerMapping extends RequestMappingHandlerMapping {
    @Override
    protected boolean isHandler(Class<?> beanType) {
        return super.isHandler(beanType) && !beanType.isInterface();
    }
}

}`
@kadaan

In my opinion this is a major security issue in spring. My application is exposing services which I call internally just because the team of the other service annotated their interfaces with @ RequestMapping on top level.
This is not what I would expect. If I want a Controller to behave like a Controller it should be annotated as Controller.
        protected boolean isHandler(Class<?> beanType) {
            return (AnnotatedElementUtils.hasAnnotation(beanType, Controller.class));
        }

I guess you need to open an issue in the Spring JIRA for that?

Can you maybe throw an error if a FeignClient also has a RequestMapping? This would at least help people who get bitten by this.

Workaround provided by @kadaan works well when running the server but fails in Spring boot tests (FeignFilterRequestMappingHandlerMapping.isHandler is not called).
Any clue ?

Why not just add rule to the Spring MVC that will register handler only if it annotated by  @Controller or @RestController? Looks very oblivious and will not bring to the Spring MVC any additional dependency.

That's in spring Framework and not handled here, hence it was closed. Open in issue in http://jira.spring.io if you'd like

@spencergibb Seems like not reproducible at Greenwich.RC2 and Spring Boot 2.1.1.RELEASE. Unfotenly can't find info about does it was solved or this is something else...

@spencergibb Was able to reproduce this, will create issue for this on jira. Reproducible at Greenwich.RC2 and Spring Boot 2.1.1.RELEASE.
Here is my test project for this https://github.com/Hronom/test-shared-mapping-interface

Done https://jira.spring.io/browse/SPR-17622

Why not use path.  Such as @FeignClient(name="localapp", path="users")


Conform to ros format for header field frame_id of sensor msgs

Should partially solves https://github.com/ignitionrobotics/ign-gazebo/issues/340
The frame_id field of the header of a sensor msg will now be the name given in the sdf sensor name attribute instead of the full chain of links.
Example with <sensor name='laser' type='gpu_lidar'>
Before:
$ rostopic echo --noarr /scan
header:
  seq: 384
  stamp:
    secs: 12
    nsecs: 800000000
  frame_id: "spawned/base_footprint/laser"
angle_min: -2.0899999141693115
angle_max: 2.0899999141693115
angle_increment: 0.0014933905331417918
time_increment: 0.0
scan_time: 0.0
range_min: 0.05000000074505806
range_max: 30.0
ranges: "<array type: float32, length: 2800>"
intensities: "<array type: float32, length: 2800>"

After:
header:
  seq: 127
  stamp:
    secs: 4
    nsecs: 234000000
  frame_id: "laser"
angle_min: -2.0899999141693115
angle_max: 2.0899999141693115
angle_increment: 0.0014933905331417918
time_increment: 0.0
scan_time: 0.0
range_min: 0.05000000074505806
range_max: 30.0
ranges: "<array type: float32, length: 2800>"
intensities: "<array type: float32, length: 2800>"

However, in case of multi robot simulation, one should take care of properly prefixing the frame_id names to ensure each stays globally unique. See for instance, an example of a multiple camera launch file with a macro for proper prefixing of the frame_id field in the format tf_prefix_frame_id_name and without /:
https://github.com/IntelRealSense/realsense-ros/blob/development/realsense2_camera/launch/rs_multiple_devices.launch

This would break existing usage in SubT where multiple robots that each have a sensor with the same name use the prefix as a way to differentiate themselves. For this to work, the conversion from :: to / is expected to convert the whole string, not just the substring after the last ::.
As an alternative to this PR, maybe we can add an option to ign-sensors/ign-gazebo to report frame ids using just the name of the sensor instead of the fully qualified name.

As an alternative to this PR, maybe we can add an option to ign-sensors/ign-gazebo to report frame ids using just the name of the sensor instead of the fully qualified name.

I agree with the alternative, how would you see this option exposed ? As an sdf attribute of the sensor plugging (which will apply this option to all sensors) or as new sdf attribute under the <sensor> one (which will apply this option per sensor) ? Or something else?

I would like to move forward on this topic, @chapulina , any advice on how to tackle it ? Implementing @azeey  suggestion ? But how ?

how would you see this option exposed ?

How about adding support for a custom ignition:frame_id SDF element that's supported by ign-sensors? If the element is not specified, the behaviour remains the same as now (i.e. with the fully scoped name).
For example:
        <sensor name="imu" type="imu">
          <update_rate>100</update_rate>
          <topic>imu</topic>
          <ignition:frame_id>imu</ignition:frame_id>
        </sensor>

Then ign-sensors can parse that special element for all sensors, and offer FrameId and SetFrameId APIs, and all sensors must be updated to use that when populating their headers.

@doisyg , are you still interested in working on this?

Still interested in the feature, still interested in working on it if nobody takes care of it, but I don't immediately have time

@ros-pull-request-builder retest this please

I think this PR/discussion is related with this other PR https://github.com/ignitionrobotics/ign-sensors/pull/195/files

I think this PR/discussion is related with this other PR https://github.com/ignitionrobotics/ign-sensors/pull/195/files

Reading the discussion I will work on a more generic solution

I udpated the PR https://github.com/ignitionrobotics/ign-sensors/pull/195 here is my solution
I couldn't use ignition:frame_id I used ignition_frame_id instead

@doisyg , what's the status of this PR? We just synced Citadel to packages.ros.org, so if you were waiting on any releases, this should be unblocked.

Closing in favor of https://github.com/ignitionrobotics/ign-sensors/pull/195 and https://github.com/ignitionrobotics/ign-sensors/pull/218


popup css print problem

step1 http://prnt.sc/ek9xsa
step2 http://prnt.sc/ek9y2w
step3 problem page: http://prnt.sc/ek9ya2

This plugin doesn't have print support,
What should be the correct output for print ?

@media print {
.jconfirm {
display:none;
}
}

that will totally hide the confirm modal, that can be unexpected right ?
people might want to print with the modal

Hide popup on page from printer

Write to myself

okay i'll add this in the options,
by default the modal will be printable 👍


Adds streaming results and stack-frame info

This is a work in progress, but I'm opening the PR so we can discuss. There are a couple of code comments, marked WIP: (shoulda called it RFC) about the changes, which I'll remove if and when this PR becomes mergeable.
The main points here are:

The streaming of results. There's a on-result-hook that can be set, and will be invoked when results become available. Example usage is in the TAP style emitter found in test/. I've tested using the output from that to feed into a couple of existing pretty-printers with acceptable results.

Extraction of stack frame data using (debug/stack (fiber/current)). This one is a bit finicky, and need more testing, because, as-is, it just assumes that the relevant stack frame is at index 2, which probably is not always the case.

Maybe we could use https://github.com/andrewchambers/janet-where-defined instead of debug/stack?

@roobie My strong preference for Testament is that it have no dependencies so I'd prefer to not add anything unless absolutely required.
I like the hook implementation generally but am not sure about the stack frame stuff. I haven't worked in a language that gives you such easy access to debugging the stack and confess I don't really understand the advantages of exposing it. Is there a reason why Testament needs to return the frame? Isn't the stack visible to whatever function is running? If a custom reporter wants access to it, couldn't it handle that by itself?

You raise good points! I was probably locked in my train of thought that I wanted to read the stack at macro expansion, but now that you point it out, it's more likely over-engineered. I'll remove the stack frame stuff and clean it up.

Updated. I'm still interested in hearing your thoughts on the :do-exit part. I added that because I needed to run a bit of code after run-tests!.

@roobie I had badly chosen the names of the keys used in the report and results structs and confused myself so I went back and changed the keys to be :passed?, :details and :note. I think this is clearer.
In addition, since it's now important what the value of details is in those structs, I went in and wrote detailed explanations in the different assertions. That means the user has to jump to the relevant assertion but hopefully that's not too difficult (especially if they're using the API documentation that will be generated by Documentarian—it will omit the docstrings for the private functions so there won't be as many functions to scan through as there are when reading the source code). This does mean that there's a risk that the docstring and the value of :details get out of sync but I don't see any way around that.
Finally, while I like the idea of providing the reports to a user-defined function, I am a teeny bit apprehensive that this reduces our flexibility to change the result struct in the future. To be sure, this is a self-imposed restraint. As a personal preference, I want to maintaining backwards compatibility as much as possible and so once we expose it publicly, I don't want to make any changes to a result struct that isn't additive (for existing assertions). That would mean, for example, that we can't change the name of the :details key in the future.
Given that, what do you think about the result format?

Nice work on the documentation! 👍
You raise good points. A couple of things come to my mind with regards to this. For one, it could be decided that the result struct is internal to Testament and should not be exposed directly to user code, but instead we would define the minimal acceptable struct (and map/transform the result to it before passing it to the hook) for user code to make use of, like e.g. {:passed? <bool> :name <string> :description <string>} - i.e. just simple data, no (nested) data structures, and the minimal (I think) representation to be able to report something of use when a test is OK or fails. In this case :description could be the rendered version of :details or any string, really. The point is that the consumer shouldn't make assumptions about what's in the string. This would be a protocol, and as such, it could be versioned. So if a need to change this struct in a non-backwards-compatible manner, Testament would have to bump the major version number.

Also, I think the code changes look good. I'll be able to try them out later this evening.

@roobie Sorry to push again so soon but after reading your suggestion, I had the realisation that the result struct should really just be data. The form of the error message that Testament displays for failed assertions should be kept separately.
To that end, the result struct now has five keys: :kind, :passed?, :expect, :actual and :note. I think this gives hooks more flexibility to do what they want with the result. It also allowed me to centralise the documentation about what to expect in the set-on-result-hook docstring.
What do you think?

No need to apologize. I think your update makes sense, and as you say, it gives a lot more flexibility compared to earlier. I'd say that those five keys covers any reporting use-case I can think of. For example: let's say we would want to implement :deep-equal assertion support (i.e. deep=). Then any consumer relying on this hook need not do anything, because the data in the result that is passed to the hook is opaque in that way. Sure the actual data may differ, but the handling of it is the same.
I've created a gist, with a TAP printer using Testament from this branch: https://gist.github.com/roobie/b47b997bd1178ff4a50509efa174622e
You can pipe the output from that into e.g. tap-parser and it'll correctly parse it and give reasonable diagnostic output as well (specifically the actual vs. expected now possible with your changes)

Awesome :) I think I'll merge it in, then. Thanks for all the help!

@roobie It occurred to me as I was writing the commit message that each assertion should really know what test it is associated with (this could then be part of the reported result). I know I wanted to do this originally but couldn't work out how to do it. I think I might now have an idea. The great thing is that result is just a map so if you build something depending on this version, it's no problem if I add that as an additional key 🎉


OTR+NTR: CRISPR biology and GO:0043571 ! maintenance of CRISPR repeat elements

GO:0043571 ! maintenance of CRISPR repeat elements is defined as:
"Any process involved in sustaining CRISPR repeat clusters, including capture of new spacer elements, expansion or contraction of clusters, propagation of the leader sequence and repeat clusters within a genome, transfer of repeat clusters and CRISPR-associated (cas) genes to new genomes, transcription of the CRISPR repeat arrays into RNA and processing, and interaction of CRISPR/cas loci with the host genome. CRISPR (clustered regularly interspaced short palindromic repeat) elements are a family of sequence elements containing multiple direct repeats of 24-48 bp with weak dyad symmetry which are separated by regularly sized nonrepetitive spacer sequences."
It's an is_a child of GO:0043570 ! maintenance of DNA repeat elements.
This term strikes me as an overly broad umbrella for all of CRISPR-cas biology. At the same time, it's missing the key activity of the CRISPR systems in host defense. The reference provided in the notes doesn't give a good overview of the biology.
PMID: 23495939 is an Annual Reviews article, which breaks CRISPR biology into three types of potential process terms:

CRISPR adaptation (i.e., new spacer acquisition), is_a GO:0006259 ! DNA metabolic process. I don't think it should be an is_a of GO:0043570 ! maintenance of DNA repeat elements. The key step is the capture of new unique sequences within the repeat array.
CRISPR-associ
crRNA biogenesis, (transcription and RNA processing) is_a GO:0006396 ! RNA processing
crRNA-guided target nucleic acid inactivation

crRNA-guided target DNA inactivation
crRNA-guided target RNA inactivation

IIRC cells that are defective in CRISPR adaptation can still use CRISPRs to defend against invaders that match existing crRNAs
An umbrella term for the overall process of CRISPR-mediated adaptive immunity could be over all of these, the closest appropriate parent would be GO:0044355 ! clearance of foreign intracellular DNA, but this should have a parent term that includes both RNA and DNA. Otherwise, it would be a child of GO:0006952 ! defense response. From the review, some CRISPR mediated host defense systems work against DNA and RNA (see above)
In addition to process terms, there should probably also be component terms:

CRISPR-associated complex for antiviral defense is_a GO:0030529 ! ribonucleoprotein complex

CRISPR-associated complex for antiviral defense, Type I (Cascade)
CRISPR-associated complex for antiviral defense, Type II
CRISPR-associated complex for antiviral defense, Type III

One or more activity terms may also be needed.
Reported by: jimhu
Original Ticket: geneontology/ontology-requests/10809

Added:
rdfs:label "CRISPR-cas system"
has_obo_namespace "biological_process"
definition "An adaptive immune response of bacteria that serves to clear host cells of foreign DNA and RNA.  It has three distinct stage: acquisition of foreign DNA by integration into CRISPR loci in the host chromosome; CRISPR RNA (crRNA) biogenesis; and target interference.  CRISPR stands for Clustered Regularly Interspaced Short Palindromic Repeat, which describes the nature of the loci." [PMID:23495939]
SubClassOf: 'clearance of foreign intracellular nucleic acids'

With the expanding characterization of anti-CRISPR proteins, additional function terms to describe negative regulation of __________(CRISPR/Cas type) are needed. While we do not yet have terms that reflect the fact that there are at least six different CRISPR Types, the specific defenses against each type are encoded by a wide variety of phage-encoded anti-CRISPR proteins. Recent review here: 28749735
Additionally, CRISPR systems themselves can be completely encoded by bacteriophage, PMID:     23446421. Other examples of partial systems can be identified in phage genomes PMID: 27302758 and 29440578. A new term allowing for phage-encoded CRISPR/Cas as a defense against host might be in order.

Thanks @jrr-cpt
Can you please provide:

names of terms you would like to see
definitions
I assume the review you cite  (PMID:28749735) would be correct for these terms ?

Thanks, Pascale

Current hierarchy

How about this:

[ ] add PMID:28749735 "The Discovery, Mechanisms, and Evolutionary Impact of Anti-CRISPRs ", as a reference to 'inhibition of host CRISPR-cas system by virus'

[ ] For phage CRISPR-cas: PMID: 27302758 and 29440578 - either we need a new term, or we need to adjust the definition of the current GO:0099048  CRISPR-cas system term, which is "An adaptive immune response of bacteria that serves to clear host cells of foreign DNA and RNA. It has three distinct stage: acquisition of foreign DNA by integration into CRISPR loci in the host chromosome, CRISPR RNA (crRNA) biogenesis, and target interference. CISPR stands for Clustered Regularly Interspaced Short Palindromic Repeat, which describes the nature of the loci. "

this has 2 problems:

Is this really an 'adaptive immune response', in the GO sense?

Can we remove the reference to bacteria? the defnition would be "An ~adaptive immune~defense response ~of bacteria~ that serves to clear host cells of foreign DNA and RNA. It has three distinct stage: acquisition of foreign DNA by integration into CRISPR loci in the host chromosome, CRISPR RNA (crRNA) biogenesis, and target interference. CISPR stands for Clustered Regularly Interspaced Short Palindromic Repeat, which describes the nature of the loci.

@dsiegele Would that work?
Thanks, Pascale


terraform-compliance failing in GitHub action when upgrading to TF 1.0

Description
Heya, Since when upgrading to Terraform 1.0 our pipeline has started failing with the below error. We're using the latest version of your github action. Any ideas as to what could be the issue?
To Reproduce

Used terraform-compliance Parameters:
terraform-compliance --features tests --planfile my.plan
Error Output:
ERROR: Failed to convert terraform plan file to JSON format via terraform. Here is the error :
terraform-compliance v1.3.18 initiated

. Converting terraform plan file.
None
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb8 pc=0x215613d]

goroutine 1 [running]:
github.com/hashicorp/terraform/internal/command/jsonplan.marshalPlanResources(0xc0020342a0, 0xc0005c6a00, 0x29, 0x43, 0xc000f66af0, 0xc000a970a0, 0xc000491900, 0xc000540c00, 0x0, 0xc0016a4f30)
	/home/circleci/project/project/internal/command/jsonplan/values.go:161 +0xfd
github.com/hashicorp/terraform/internal/command/jsonplan.marshalPlanModules(0xc0020342a0, 0xc000f66af0, 0xc0009a4e40, 0x4, 0x4, 0xc0016a5190, 0xc0016a51c0, 0x92, 0x0, 0x0, ...)
	/home/circleci/project/project/internal/command/jsonplan/values.go:243 +0x1ba
github.com/hashicorp/terraform/internal/command/jsonplan.marshalPlannedValues(0xc0020342a0, 0xc000f66af0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/home/circleci/project/project/internal/command/jsonplan/values.go:142 +0xaaa
github.com/hashicorp/terraform/internal/command/jsonplan.(*plan).marshalPlannedValues(0xc00011c380, 0xc0020342a0, 0xc000f66af0, 0x0, 0x0)
	/home/circleci/project/project/internal/command/jsonplan/plan.go:539 +0x70
github.com/hashicorp/terraform/internal/command/jsonplan.Marshal(0xc0009ce0d0, 0xc0005800a0, 0xc000660e10, 0xc000f66af0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/circleci/project/project/internal/command/jsonplan/plan.go:127 +0x172
github.com/hashicorp/terraform/internal/command.(*ShowCommand).Run(0xc00056a000, 0xc00004c0b0, 0x1, 0x2, 0xc00054e170)
	/home/circleci/project/project/internal/command/show.go:152 +0x966
github.com/mitchellh/cli.(*CLI).Run(0xc000552280, 0xc00054c000, 0x282d57d, 0x4)
	/home/circleci/go/pkg/mod/github.com/mitchellh/cli@v1.1.2/cli.go:262 +0x41a
main.wrappedMain(0x0)
	/home/circleci/project/project/main.go:384 +0x1112
main.realMain(0x0)
	/home/circleci/project/project/main.go:115 +0x554
main.main()
	/home/circleci/project/project/main.go:58 +0x25

Expected Behavior:

Tested Versions:

terraform-compliance version:  v1.3.18
terraform version: 1.0

Additional Context:

I think it has to do with the following

https://github.com/hashicorp/terraform/issues/28903
https://github.com/hashicorp/terraform/releases/tag/v0.15.4

terraform-compliance will have to change to be able to process the plan output of any terraform >= 15.4

This could be similar. Looks like 1.0.x releases are creating quite a lot problem.
Will have a deeper look on this.

Hi @TomTucka , did you try the same with the latest 1.x version of terraform ? It looks like its fixed on the terraform side.
@Shocktrooper can you also run which terraform please ? It looks like, you have the plan.out file only. In order to get it parsed by terraform-compliance, we use terraform executable to convert it to a JSON file. (command: terraform show -json plan.out > plan.out.json) terraform requires a terraform init before converting it to JSON file, unfortunately this is not a functionality where terraform-compliance can interfere. On the other hand, if you convert it to JSON and give plan.out.json instead of plan.out to terraform-compliance, we won't need any conversion and this problem won't occur.

@eerkunt I have verified that passing in the JSON works with the latest version of terraform-compliance with terraform 15.4 .  It appears that since we use terragrunt that terraform-compliance was unable to do anything when it tried to auto init what was in the directory


Add new task: Detect Reasoning

Feedback welcome! I'm exploring how to train a model to recognize various patterns of reasoning:

Deductive

Modus Ponens (Affirming the Antecedent)
Modus Tollens (Denying the Consequent)
Disjunctive Syllogism
Hypothetical Syllogism
Constructive Dilemma

Inductive

Generalization
Statistical Syllogism
Argument from Analogy

Abductive: Inference to the Best Explanation
Causal: Cause to Effect / Effect to Cause
Conditional: Equivalence

Intriguing - I love everything here, but seperate out the identification tasks into different ones maybe - so Identify Deductive Reasoning, Identify Inductive Reasoning, etc.

Intriguing - I love everything here, but seperate out the identification tasks into different ones maybe - so Identify Deductive Reasoning, Identify Inductive Reasoning, etc.

Agreed! Can you split out the tasks so each form is a specific one? I can probably reformat them into their own tasks if needed

Feedback welcome! I'm exploring how to train a model to recognize various patterns of reasoning:

Deductive

Modus Ponens (Affirming the Antecedent)
Modus Tollens (Denying the Consequent)
Disjunctive Syllogism
Hypothetical Syllogism
Constructive Dilemma

Inductive

Generalization
Statistical Syllogism
Argument from Analogy

Abductive: Inference to the Best Explanation

Causal: Cause to Effect / Effect to Cause

Conditional: Equivalence

Hello! we have updated the structure of the repo. Would you be able to update your branch to conform? Then can merge, thank you!


Filter devices in flutter_blue

I use flutter_blue to scan ble devices for social distancing app. However I'm not sure if what I did is correct. Since I make it general on scanning devices, I cannot know their characteristic and all I know is I only need to scan phone devices. Before I added the filtering which I use 'where' while scanning, it's functioning well even though it scan not just mobile devices but all devices. After I added them, it does not working at all even the floatingbutton to tap to scan devices.
Here is my code before I add the filtering:
FlutterBlue flutterBlue = FlutterBlue.instance;
List scanResultList = [];
bool _isScanning = false;
@override
initState() {
super.initState();
// reset bluetooth
initBle();
}
void initBle() {
// listener to get BLE scan status
flutterBlue.isScanning.listen((isScanning) {
_isScanning = isScanning;
setState(() {});
});
}
/*
scan start or stop function
*/
scan() async {
if (!_isScanning) {
// if not scanning
// Delete the previously scanned list
scanResultList.clear();
// Start scanning, timeout 4 seconds
flutterBlue.startScan(timeout: Duration(seconds: 4));
// scan result listener
flutterBlue.scanResults.listen((results) {
// List Copy the results value of the form to scanResultList
scanResultList = results;
// UI renewal
setState(() {});
});
} else {
// Stop scanning if scanning
flutterBlue.stopScan();
}
}
And this is my code after I tried to filter them:
FlutterBlue flutterBlue = FlutterBlue.instance;
List scanResultList = [];
bool _isScanning = false;
@override
initState() {
super.initState();
// reset bluetooth
initBle();
NotificationWidget.init();
}
void initBle() {
// listener to get BLE scan status
flutterBlue.isScanning.listen((isScanning) {
_isScanning = isScanning;
setState(() {});
});
}
/*
scan start or stop function
*/
scan() async {
if (!_isScanning) {
// if not scanning
// Delete the previously scanned list
scanResultList.clear();
// Start scanning, timeout 4 seconds
final scanResult = FlutterBlue.instance.scan().where((scanResult) {
// Filter devices by manufacturer data and local name
final advertisingData = scanResult.advertisementData;
final deviceName = scanResult.device.name;
return (advertisingData.manufacturerData[0x004C] == [0x02, 0x15] ||
advertisingData.manufacturerData[0x0051] != null) &&
deviceName.startsWith('Phone');
});
// scan result listener
flutterBlue.scanResults.listen((results) {
// List Copy the results value of the form to scanResultList
scanResultList = results;
// UI renewal
setState(() {});
});
} else {
// Stop scanning if scanning
flutterBlue.stopScan();
}
}

It's simple as that. First scan the devices and add it in a List. Now create another list on filtering the existing list.
Once you have list of filtered device you will be having the device properties and use that to discover the services after connecting. it will have multiple services & characteristics. Now create a characteristic vairiable and assign the device characteristic to it. Now you're ready to make use of the characteristics and perform read/write or any operatin

Hello, this plugin is obsolete and maintenance is stopped.
Use the continuous and active package : flutter_blue_plus


python311Packages.deluge-client: 1.10.0 -> 1.10.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.deluge-client is: Lightweight pure-python rpc client for deluge
meta.homepage for python311Packages.deluge-client is: https://github.com/JohnDoee/deluge-client
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.10.2 with grep in /nix/store/0f7x8629kcpj8zk0ir6d2gsx0d126z8d-python3.11-deluge-client-1.10.2
found 1.10.2 in filename of file in /nix/store/0f7x8629kcpj8zk0ir6d2gsx0d126z8d-python3.11-deluge-client-1.10.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.deluge
python311Packages.deluge-client
python312Packages.deluge-client

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0f7x8629kcpj8zk0ir6d2gsx0d126z8d-python3.11-deluge-client-1.10.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.deluge-client https://github.com/r-ryantm/nixpkgs/archive/64ae2576823ab8c3f74651fa97d98a2d4dec669a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/64ae2576823ab8c3f74651fa97d98a2d4dec669a#python311Packages.deluge-client

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0f7x8629kcpj8zk0ir6d2gsx0d126z8d-python3.11-deluge-client-1.10.2
ls -la /nix/store/0f7x8629kcpj8zk0ir6d2gsx0d126z8d-python3.11-deluge-client-1.10.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python311Packages.deluge-client
python312Packages.deluge-client

Maintainer pings
cc @peterhoeg for testing.

Result of nixpkgs-review pr 289913 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.deluge
python311Packages.deluge-client
python311Packages.deluge-client.dist
python312Packages.deluge-client
python312Packages.deluge-client.dist


[xslt] Migrate native functions to java interoperability

Description:
$title

Blocked due to https://github.com/ballerina-platform/ballerina-lang/issues/20172


[matplotplusplus] Re-fix 3rd libraries installation

Install the 3rd libraries to lib / debug/lib to fix the link error when using msvc project.
Fixes #18287.

Thanks Jack!


add unit-test for DetachVolume team4

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fixes #1761
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

#1824 which has been merged solves the same problem with this PR, so close it.
Thanks for your work !


MapComponent Injected?

CommunityCoreLibrary/DLL_Project/Defs/ModHelperDef/MapComponents.cs
Injected method had an unused var - check that this is doing what it is supposed to do.

Fixed by merging in Forsaken's latest Alpha 15 branch.


Sonoff switches unavailable

I have 31 Sonoff switches configured on homeassistant.
13 of this switches became unavailable at 7:00 am on 6th July on homeassistant.
All 31 Sonoff switches are working find on ewelink.
The only common issue is that the 13 switches that became unavailable are connect on the same WiFi router the other switches are in a different WiFi router.
But because al 31 sonoff switches work find with ewelink. I assume that the problem is with homeassistant and not the WiFi router.

Mine are erratically going unavailable and coming back online since July 7th updates. Running the latest versions of HA on Pi and HACS Sonoff LAN. My other non-Sonoff switches don't have any issues.

Same problem here with the latest 3.1.0. There are 15 sonoff switches in my system. The wifi network resets overnight and  in the morning 2 or 3 random switches are sometimes unavailable. But they are available in ewelink and become available in HA again after toggling using ewelink.

Mine are erratically going unavailable and coming back online since July 7th updates. Running the latest versions of HA on Pi and HACS Sonoff LAN. My other non-Sonoff switches don't have any issues.

This problem was resolved after increasing the DHCP server lease time from 1 minute to 30 minutes or higher. Don't know why this was problematic only for these switches.

Same problem here:
I have 2 houses in HA. When sonoff is online in 1 home, it is offline in the other

Mine are erratically going unavailable and coming back online since July 7th updates. Running the latest versions of HA on Pi and HACS Sonoff LAN. My other non-Sonoff switches don't have any issues.

This problem was resolved after increasing the DHCP server lease time from 1 minute to 30 minutes or higher. Don't know why this was problematic only for these switches.

My unavailable problem is different from yours. DHCP lease time in my network and typically is 7 days. DHCP is initiated by a client rather than the router at client start up then refreshed at half the lease time so 1 minute is very short. Glad you found the solution for your situation.

I have the following warnings on my log.
Not sure if it is related but it seems that started at the same time as the unavailability problem.
Logger: homeassistant.components.number
Source: components/number/init.py:462
Integration: Number (documentation, issues)
First occurred: 13:25:22 (15 occurrences)
Last logged: 13:25:22
Entity sonoff.sonoff_100067fe11_pulseWidth (<class 'custom_components.sonoff.number.XPulseWidth'>) is using deprecated NumberEntity features which will be unsupported from Home Assistant Core 2022.10, please report it to the custom component author.
Entity sonoff.sonoff_1000b681c3_pulseWidth (<class 'custom_components.sonoff.number.XPulseWidth'>) is using deprecated NumberEntity features which will be unsupported from Home Assistant Core 2022.10, please report it to the custom component author.
Entity sonoff.sonoff_1000b6bb3a_pulseWidth (<class 'custom_components.sonoff.number.XPulseWidth'>) is using deprecated NumberEntity features which will be unsupported from Home Assistant Core 2022.10, please report it to the custom component author.
Entity sonoff.sonoff_1000b5f9f1_pulseWidth (<class 'custom_components.sonoff.number.XPulseWidth'>) is using deprecated NumberEntity features which will be unsupported from Home Assistant Core 2022.10, please report it to the custom component author.
Entity sonoff.sonoff_10008963e3_pulseWidth (<class 'custom_components.sonoff.number.XPulseWidth'>) is using deprecated NumberEntity features which will be unsupported from Home Assistant Core 2022.10, please report it to the custom component author.
Logger: homeassistant.components.number
Source: components/number/init.py:220
Integration: Number (documentation, issues)
First occurred: 13:25:18 (3 occurrences)
Last logged: 13:25:18
custom_components.sonoff.number::XNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
custom_components.sonoff.number::XPulseWidth is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.

#935

It is now all working again.
Thank you GuyKh.

Is problem still actual?

The problem has not been observed for sometime now. Not sure what did it as the installation is kept up to date so there has been a few updates since.  Thanks for your help.
On 3 September 2022 5:51:24 am AEST, Alex X @.***> wrote:

Is problem still actual?
--
Reply to this email directly or view it on GitHub:
https://github.com/AlexxIT/SonoffLAN/issues/907#issuecomment-1235846677
You are receiving this because you commented.
Message ID: @.***>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

It is now all working again. Thank you GuyKh.

Hello, I have same problem of sonoff devices become unavailable in HA, I was not able to understand what was the solution, I followed the link GuyKh commented on Aug 4, 2022
https://github.com/AlexxIT/SonoffLAN/pull/935 but was not able to figure out,
can you please explain what is the fix?

It hasn't been a problem for me for quite a long period, but recently it is a serious issue again. Almost every day I have got alerts about the switches getting offline. I set up a "reload config" action earlier when the issue originally came up, but it was sleeping for a while. Now it is getting more and more annoying again.
I use the switches for heating, so it is kind of important to have a stable connection, but currently, I cannot tell about the effect of the issue, since the heating is turned off

I am now controlling sonoff devices with sonoff integration on HA and it was working well up until upgrading HA core from 2023.6.3 to 2023.7.1 on 7th July.
With HA 2023.7.1 I lost connection with 9 devices.
I assume the problem is with HA 2023.7.1

From what I have seen not all versions of HA are compatible with the version of integration
So the easiest solution I found is to check compatibility and stick with these two versions and be careful when doing upgrades
Regards, Tawfikhttps://aka.ms/o0ukef

From: RMLReis @.>
Sent: Tuesday, July 11, 2023 7:14:44 PM
To: AlexxIT/SonoffLAN @.>
Cc: TawfikDaim @.>; Comment @.>
Subject: Re: [AlexxIT/SonoffLAN] Sonoff switches unavailable (Issue #907)
I am now controlling sonoff devices with sonoff integration on HA and it was working well up until upgrading HA core from 2023.6.3 to 2023.7.1 on 7th July.
With HA 2023.7.1 I lost connection with 9 devices.
I assume the problem is with HA 2023.7.1
—
Reply to this email directly, view it on GitHubhttps://github.com/AlexxIT/SonoffLAN/issues/907#issuecomment-1631112268, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHYVEGEMCQZNJO7R42ZPPETXPV3XJANCNFSM53HOVAWQ.
You are receiving this because you commented.Message ID: @.***>


docs: improve readme

Overview
Addresses items raised in #181 and also adds a bit of instruction for running it locally.

Codecov Report

Merging #184 (227afc8) into master (0f2767c) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #184      +/-   ##
==========================================
- Coverage   50.72%   50.72%   -0.01%
==========================================
  Files          48       48
  Lines        1378     1380       +2
  Branches      202      202
==========================================
+ Hits          699      700       +1
- Misses        511      512       +1
  Partials      168      168

Impacted Files
Coverage Δ

packages/use-contractkit/src/walletIcons.tsx
80.00% <0.00%> (-4.62%)
:arrow_down:

packages/use-contractkit/src/constants.tsx
73.25% <0.00%> (ø)

Continue to review full report at Codecov.

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


[Bug]: icon is not loaded in template also count mismatch with release and prod

Is there an existing issue for this?

[X] I have searched the existing issues

Description

icon is not loaded properly in template information pane
Also template count is not same with release and prod

icon not loaded - customer dashboard/marketing dashbord

Relase count

Prod count

Steps To Reproduce
Click on template > and verify template information
Public Sample App
No response
Environment
Release
Issue video log
No response
Version
cloud

We have separate templates(databases) for release and prod. Hence the count is different.
Regarding icon not loaded.

Root cause: The templates are using older widgets which stand deprecated, hence removed from codebase.
Solution: Replace the widgets with newer versions.

We faced the same in prod and updated all the templates. This can be fixed in release as well, but it is a tedious task, and would stand low in priority for the team.
Since this is not really a problem per se, we can ignore the icons on release. If you notice this on prod please notify us, we will fix that asap.
I am closing this for now. Let me know if you have any concerns.


Not able to download Paddle models

Hi,
i am trying to use your examples . i am not able to download paddle models from the following link . Also your repo \Release folder also does not have models . could you please let me know from where to download OCR paddle models.
https://paddleocr.bj.bcebos.com/PP-OCRv4/chinese/ch_PP-OCRv4_det_infer.tar

All models can be downloaded from the official PP-OCR website. The following is the download page link:
https://github.com/PaddlePaddle/PaddleOCR/blob/main/doc/doc_ch/models_list.md

Yes that leads to
https://paddleocr.bj.bcebos.com/PP-OCRv4/chinese/ch_PP-OCRv4_det_infer.tar
same link . but it keep showing
We can’t connect to the server at paddleocr.bj.bcebos.com !!
it is not allowing me do download .
could you share github link if that is there in your repo .
On Thu, May 2, 2024 at 12:27 PM 颜国进 @.***> wrote:

All models can be downloaded from the official PP-OCR website. The
following is the download page link:
https://github.com/PaddlePaddle/PaddleOCR/blob/main/doc/doc_ch/models_list.md
—
Reply to this email directly, view it on GitHub
https://github.com/guojin-yan/PaddleOCR-OpenVINO-CSharp/issues/7#issuecomment-2089748366,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFCXQ3CRC267PMPEWG3XWD3ZAHPVLAVCNFSM6AAAAABHDEE6ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZG42DQMZWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
For SquareOne,
Darshan Patel
M-9879565952

I can download the following link normally, but it will inevitably cause network problems and prevent me from connecting to it.
https://paddleocr.bj.bcebos.com/PP-OCRv4/chinese/ch_PP-OCRv4_det_infer.tar


Add Proxy-Authorization header to CONNECT request

It turns out that goproxy doesn't automatically add the Proxy-Authorization header to a CONNECT request, when we have extern-proxy-uri set.  This change manually adds the Proxy-Authorization header to outbound CONNECT requests when a username or password is detected in the external proxy URL.

Refer to this link for build results (access rights to CI server needed):
https://edge-jenkins.isgtesting.com/job/test_team-build-edge_proxy/89/

This PR depends on #18 .


Update the API to expose S6 data

I think the most noticeable change is the introduction of RiftHerald fields.
Opening the issue so we can coordinate and we won't have 3 different people working on the same thing.
Is anyone working on that?
If not, I might start looking into the match DTO

Accepted #32 and made appropriate fixed to core as well. Thanks.


PMML Import

Full persistence of models requires PMML import, particularly for my use case.
Every morning, I have a task that compiles features, loads the model, predicts the features, and sends off the predictions.
While this could be handled with a service by training the model and then maintaining the estimator in memory, a failure means retraining the model. Supplying the hyperparameters to the estimator won't work.
Full PMML import/export is necessary in my case, unless I can re-engineer the process. I'm not sure there's much to be gained by this, so it's a tough sell internally.

Just to clarify - does the training flow in your case use a different stack (anything different from sklearn)? Otherwise, you could simply serialize your pre-trained model with pickle for further use, it's much more convenient than PMML.
At the same time I agree that PMML->sklearn import would be a valuable feature to this project. We're open to PRs.

I’m using joblib.load right now. It seems to work well, but I do know there are problems serializing models from python.
I would like to be able to train models in scikit-learn and then import them into Spark. That's my ultimate workflow. Mllib will not currently import PMML.
Everybody exports to PMML (including R), but few systems will import PMML. This defeats the entire purpose of the standard, in my opinion.

If you're just using spark to evaluate a model trained it sklearn, you could use the jpmml evaluator, I've used it with scalding and pig on several occasions.  This would require using the scala or java spark API's though if I was using python I've probably just use pickle.

Hmm, apparently my future problems will just go away. Thanks @DarinJ for the info.

We have no plans to use Spark. So PMML import is back on the table for me.


Cannot build asp.net

It gets to
Running yarn install on ~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/src/JSInterop/Microsoft.JSInterop.JS/src/Microsoft.JSInterop.JS.npmproj
  yarn install v1.22.10
  [1/4] Resolving packages...
  [2/4] Fetching packages...
  [3/4] Linking dependencies...
  [4/4] Building fresh packages...
  Done in 1.04s.
  yarn run v1.22.10
  yarn run v1.22.10
  $ yarn run clean && yarn install --mutex network
  $ npm run clean && npm run build:esm
  Deleting directory ~/.gradle/wrapper/dists/gradle-6.5-bin/6nifqtx7604sqp1q6g8wikw7p/gradle-6.5
  $ cd ../common && yarn install --mutex network
  [1/4] Resolving packages...
  npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1640357668275-0.621943556570699/node but npm is using /usr/local/bin/node itself.
 Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

  ><EMAIL_ADDRESS>preclean ~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/src/JSInterop/Microsoft.JSInterop.JS/src
  > yarn install --mutex network

MSBUILD : error MSB4166: Child node "3" exited prematurely. Shutting down. Diagnostic information may be found in files in "~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts/log/Release" and will be named MSBuild_*.failure.txt. This location can be changed by setting
 the MSBUILDDEBUGPATH environment variable to a different directory.

but there is no log file. Second time I only get
warning: Building of C# project is enabled and has dependencies on NodeJS projects. Building of NodeJS projects is enabled since node is detected on PATH.
##vso[task.setvariable variable=Artifacts;isSecret=false;isOutput=true]~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts
##vso[task.setvariable variable=Artifacts.Toolset;isSecret=false;isOutput=true]~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts/toolset
##vso[task.setvariable variable=Artifacts.Log;isSecret=false;isOutput=true]~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts/log/Release
##vso[task.setvariable variable=Temp;isSecret=false;isOutput=true]~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts/tmp/Release
##vso[task.setvariable variable=TMP;isSecret=false;isOutput=true]~/work/bsd/dotnet-core-freebsd-source-build/aspnetcore/artifacts/tmp/Release
##vso[task.logissue type=error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) Unable to find dotnet with SDK version '6.0.100-rtm.21477.15'

I've tried it now 3 times... :)

More details please? I tried to build 6.0.0 under 12.3 and 13 with success (not under jail). There was a missing wget install in pkg's, but it's not needed, as it's downloading one file before build (as it sometimes fail during build stage).

Are you still having this issue?


Add JSON_UNESCAPED_SLASHES to json_encode

No need to escape slashes in JSON data outputs as we're not dealing with HTML.

Thanks @l4rzzz :+1:


[Removal]:

Hotspot Name
soaring-green-dalmatian
digital-honey-zebra
rapid-daisy-mockingbird
slow-infrared-buffalo
soaring-mango-perch
narrow-flint-narwhal
micro-lime-tapir
future-chocolate-seal
square-white-osprey
lively-brown-chipmunk
Hotspot b58 Address
11efc2HoCh1vuggUowwJ6YQM14EWRHUSU1X7YAtqMSQENykPKUc
11U9S27uP7scFLWPUMHKQUmxHPKfZQvLELmRRMqny9c7aVSiXMr
112ang5rJ1iebPKoaMPRd8ebxYZmZj6szeKFE7AoZ5NvJazYHyRw
112o7eCinNbZWMGP9BEpoH5hSgqoJTqpZA5XxtvL92i163aJeamh
11asnBGH2A4GU3xSGG3FLJdgsrCVdE9SjfUkW53mdoTDgWpQQqr
112Szdz5DysaeUx7fpkPn1JqhEbihreeih7U2tj4oLAx3gDfBnnj
112DtFiP3H3uhJG23QZkVMvEVg2tE3cdLHBuqZHsrrtQavcKM61h
11hALTEJbWFBCSSi67tGmzYhcpY1yMG36qY71hGfJ7mHsasxoyt
1128Wh2LKmAYeAQXmuMNBZg3KaWdUNjFpUoBVa5nmyrGvLKbiLXS
11c42xBzQ9W8v1khj2YU77qmUoAyBpLe7tRZkLiZ9eGwd3AJ2iA
Discord Handle
No response
Hotspot Manufacturer
Bobcat
Removal Reason
These hot spots are installed in the correct location, all hot spots in our town have been added to the banned list, please help me remove them, thank you.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information


PSRAM initialization failed error (IDFGH-4170)

Environment
Environment
Module or chip used: ESP32D2WD
IDF version: v4.3-dev-1561-g357a27760322
Build System: idf.py and vscode idf extention
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r3) 8.4.0
Operating System: WIndows 10
Power Supply: USB
PSRAM = External ( 64 MB)
Problem Description
I have been configured external psram with ESP32 D2WD chip tried on idf platform with esp-idf extention on vs code.
I flashed the example of https://github.com/espressif/espidf/tree/master/examples/system/himem but not getting the expected output.
Expected Behavior
I (254) spiram: SPI RAM mode: flash 40m sram 40m
I (259) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
Actual Behavior
10:52:02.435 -> I (203) psram: This chip is ESP32-D2WD
10:52:02.435 -> E (209) cpu_start: Failed to init external RAM!
PLease help me with the solution or suggest me easy example just to check the psram

What hardware are you using? How is the PSRAM connected? What GPIO pins do you have in use?

@Spritetm : PSRAM : APS6404L-SQR-ZR (64Mb)
PSRAM is connected externally to ESP32D2WD chip revision1 with GPIO pins CLK - GPIO6 and CS- GPIO10

CLK for GPIO6 is non-standard, I think - by default it should be GPIO9, unless you modified this in Menuconfig.

I tried modifying that in menuconfig but it didn't worked for me.
It was showing the same message "cpu_start: Failed to init external RAM!"


Connect to Fortmatic Wallet

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.1.5
Current Behavior
Cannot find a reference to connect a Fortmatic or a Magic wallet.
Expected Behavior
Being able to connect to Fortmatic or Magic wallet
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

Check out https://github.com/EveripediaNetwork/wagmi-magic-connector


Server returned 503

Error: Server returned 503
at a in src/vs/platform/request/common/request.ts:109:9
at e.$Po.B in out/vs/code/node/sharedProcess/sharedProcessMain.js:79:125835
at async e.$Po.z in src/vs/platform/extensionManagement/common/extensionGalleryService.ts:829:71
at async e.$Po.getExtensions in src/vs/platform/extensionManagement/common/extensionGalleryService.ts:663:26
at async D in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:429:32
at async e.$kp.G in out/vs/code/node/sharedProcess/sharedProcessMain.js:79:71278
at async e.$kp.C in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:217:48
at async in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:169:20
at async Promise.allSettled (index 0)
at async e.$kp.z in out/vs/code/node/sharedProcess/sharedProcessMain.js:79:64742
at async e.$kp.installGalleryExtensions in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:129:20
at async e.$kp.installFromGallery in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:97:20

Go to Errors Site

@isidorn apologies on the delay. I haven't been able to look at this until now. I don't have access to the "Go to Errors Site" link in the original post above. Could I get an example HTTP request or repro steps for this? I don't remember the context to this at all, unfortunately.

@joelverhagen we don't record request info, this is our error telemetry which just sends stack traces of unhandled exceptions

Okay, no worries. Do we have a time series of how often this exception is hit over time? I've done some querying against failures in Kusto specifically for gallery queries, but this seems to be exception telemetry.

Here's all the info we have on it for v1.81.0:
Stack
Error: Server returned 503
at c (out/vs/code/node/sharedProcess/sharedProcessMain.js:45:21680)
at ce.B (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:128527)
at async ce.z (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:125945)
at async ce.z (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:126885)
at async ce.getExtensions (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:122998)
at async M (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:73120)
at async H.I (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:73589)
at async H.F (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:68306)
at async (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:67129)
at async Promise.allSettled (index 0)
at async H.D (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:67076)
at async H.installGalleryExtensions (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:65540)
at async H.installFromGallery (out/vs/code/node/sharedProcess/sharedProcessMain.js:82:64861)
Deminified Stack
Error: Server returned 503
at c in src/vs/platform/request/common/request.ts:109:9
at ce.B in out/vs/code/node/sharedProcess/sharedProcessMain.js:82:128527
at async ce.z in src/vs/platform/extensionManagement/common/extensionGalleryService.ts:829:71
at async ce.z in src/vs/platform/extensionManagement/common/extensionGalleryService.ts:882:27
at async ce.getExtensions in src/vs/platform/extensionManagement/common/extensionGalleryService.ts:663:26
at async M in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:468:32
at async H.I in out/vs/code/node/sharedProcess/sharedProcessMain.js:82:73589
at async H.F in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:256:48
at async in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:208:20
at async Promise.allSettled (index 0)
at async H.D in out/vs/code/node/sharedProcess/sharedProcessMain.js:82:67076
at async H.installGalleryExtensions in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:134:20
at async H.installFromGallery in src/vs/platform/extensionManagement/common/abstractExtensionManagementService.ts:102:20
Hits
469
Machines
450
Last Seen
yesterday
Versions
6445d93c81ebe42c4cbd7a60712e0b17d9463e97

It's happening here:
https://github.com/microsoft/vscode/blob/74f6148eb9ea00507ec113ec51c489d6ffb4b771/src/vs/platform/extensionManagement/common/extensionGalleryService.ts#L829
Some details about the url:
https://github.com/microsoft/vscode/blob/74f6148eb9ea00507ec113ec51c489d6ffb4b771/src/vs/platform/extensionManagement/common/extensionGalleryService.ts#L961

@joelverhagen all the info I have is in the issue so I'm handing this off to you to create an incident if you feel it's needed.

Seeing this issue again for multiple team members at the moment.

It’s related to the ongoing azure issues - https://azure.status.microsoft/en-us/status

fyi @joelverhagen


Macro: System doesn't apply snake mode for loaded sequences (FASTA, ket, clipboard)

Steps to Reproduce

Switch to macro mode
Select Snake mode
Open attached file rna-mod-phosphate-example.zip

Actual behavior
When snake mode is activated, structure does not open in this mode.

Expected behavior
When snake mode is activated, structure opens in this mode.

Desktop (please complete the following information):

OS: Windows 11
Browser Chrome
Version 112.0.5615.138 (Official Build) (64-bit)

Ketcher version
[Version 2.19.0-rc.1]
Video
https://github.com/epam/ketcher/assets/62464241/a4c47a22-b873-4cc6-9e39-62e5221d3e6a
Issue found while testing https://github.com/epam/ketcher/issues/3862

Test added to the automation table.

Moved to Refined Backlog since no fix over 2 versions


Upgrade node version, track with LTS Boron

This unpins us from the out-of-date v4.4.7 and instead installs the latest version from the "Boron" LTS release line. With this, we'll only have to spin up new instances to pick up security fixes, plus update the LTS release line again every year. (or three)
I haven't deployed this yet, but I did test the commands in a container, and the site's test suite runs fine on v6.9.1. (FWIW Travis CI has been testing on v6 for some time now)

Turns out this doesn't work on the older version of nvm we were using, I bumped that in f007e7e


CSRF error on iPhone login

Unclear what is causing this or how to reproduce. Login via iPhone started producing CSRF error. It didn't originally. One thing that changed was approving "store password for future logins" (unclear if/how this would affect the form).

I could reproduce this bug once now.
I think it happens if you click login twice in succession which can happen especially when the website is slow and you think you didn't hit it properly.
If you push the button twice the same problem will occur outside an iPhone as well. So it's a general thing and probably kind of expected behavior as the csrf-token is already used by the second time you press the button.


Refactor themes endpoint with pipeline utility

This PR uses pipeline() utility to refactor themes controller.
Refs #5508.

There should be no need to add handleXPermissions methods here, you can use the version of the function in utils, see post/tags/users for an example.

@ErisDS Thanks for pointing this out, I guess I took an old PR as an example.

@ErisDS Updated to use utils for handling permissions.


Adding the pdf url to an iframe in IE 10/11 doesn't work

First of all, great work on this library, but your interactive example doesn't work in IE 10/11.

IE problem, nothing we can do about it.


Allow to set annotations for the UI service

Hi,
Thank you very much for your amazing work. I really like longhorn and this chart makes everything way easier!
This small contribution would allow to specify annotations for the UI service.
I am using this annotation to set a specific IP for the load balancer that I keep in front of the UI using MetalLb.
Hope you will merge this contribution so I don't have to modify the service after the creation :)
Thank you again for your work!
Best
Riccardo

Indeed this is needed for me to use longhorn with external-dns 👍

Bump
It could be great for integration with Metallb


better API to verify pools extensions

Right now we do the payment and check against an update of the available cus/sus. The problem is if you have active workloads consuming the pool, extending pools with small values and detecting that would be very tricky (not noticeable). IMO, the easiest would be last_extended_at field in the pool information to reflect the extension

I personally don't like this construction. While it works on low access pools, that is pools which are only topped up every so often, it is perfectly possible to run 2 top ups at the same time. In which case you'll still miss one of them.
Given that the whole payment thing is asynchronous by design, I think some kind of poll system on the capacity reservation itself would be better. I.e, we should add an endpoint where a given capacity reservation ID can be queried, which then returns the raw reservation (or only part of it, should some things need some stripping to avoid leaking data). That way, API's built on top of the payment system can verify that a payment has been processed successfully with an exponential timeout, or after a user presses a button to claim he paid (for example)

I personally don't like this construction. While it works on low access pools, that is pools which are only topped up every so often, it is perfectly possible to run 2 top ups at the same time. In which case you'll still miss one of them.
Given that the whole payment thing is asynchronous by design, I think some kind of poll system on the capacity reservation itself would be better. I.e, we should add an endpoint where a given capacity reservation ID can be queried, which then returns the raw reservation (or only part of it, should some things need some stripping to avoid leaking data). That way, API's built on top of the payment system can verify that a payment has been processed successfully with an exponential timeout, or after a user presses a button to claim he paid (for example)

I added a new endpoint https://explorer.testnet.grid.tf/api/v1#/pools/getpaymentinfo to be able to fetch the payment information from explorer perspective.
The flag, paid, canceled, and cause can be used to track the state of the payment. If canceled (and refunded) the cause should hold the reason for the cancellation.

I added a new endpoint https://explorer.testnet.grid.tf/api/v1#/pools/getpaymentinfo to be able to fetch the payment information from explorer perspective.
The flag, paid, canceled, and cause can be used to track the state of the payment. If canceled (and refunded) the cause should hold the reason for the cancellation.


[Accessibility] Card reveal button not accessible by keyboard interaction

Before submitting...

[X] I have searched for duplicate or closed issues.
[X] I have read the CONTRIBUTING document and my issue is following the guidelines.
[X] I have read the template completely before filling it in.

Context
When using the Card component with reveal modifier, reveal button is not tabbable/focusable by keyboard interaction which causes reduced accessibility towards people who rely on keyboard input
Current Behavior
When trying to tab into the reveal button, the element is ignored by keyboard interaction
Codepen example
Expected behavior
Reveal button should be tabbable/focusable by keyboard interaction
Possible Solutions or Causes
Implement the necessary functional attributes on initialization in order to make options tabbable/focusable by keyboard interaction
Your Environment

Version used: 2.1.1

Since v2.2.1 M.Cards.init(<selector>); is now necessary for the reveal to work properly, I think we can fix this by initialize cards programmatically on page load, this is also the case for other components, suggest to create a new issue or discussion for this
Closing this for now


ubootRaspberryPi: embiggen, again

Our kernels are bigger than 64M now, so give it another 16M. Also, stop updating the comment, it's not worth it.
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

Add a :+1: reaction to pull requests you find important.

Prior art: https://github.com/NixOS/nixpkgs/pull/174762

On that note, should we convert board-specific targets and use rpi_arm64_defconfig so that a single binary/package works on all 64-bit Raspberry Pi boards?


Test if source files will compile when dependencies are not on classpath

This is handled by logging the issue and making placeholder method details.


ScanNet evaluation doesn't match paper

Hi,
Thank you for sharing your code!
I ran test on scannet following the instructions but I get much worse results.
Do you know what might be happening?
Total test num: 10434
['abs_rel', 'abs_diff', 'sq_rel', 'rms', 'log_rms', 'a1', 'a2', 'a3']
[0.26725563624661075, 0.4768538641935877, 0.18805316813831266, 0.5750360812767931, 0.3188030923313161, 0.4764993420147505, 0.8155114483545208, 0.9528344624353279]

Here's the first output for scene0707_00

Hi,
Thanks for your attention!
I checked the code and it runs well here for me. May I ask, are your testing environments the same as the those in environment.yml? We used an old Pytorch version (1.1.0) since we built the code based on NAS. It might have some inconsistency with the latest version.

I am using pythorch 1.7.1 as my GPU only supports CUDA 11.0 and up.
However I have used newer versions of pytorch on older ones and never had issues.
Are the pretrained weights on google drive the correct ones?

I see. I have tried to use Pytorch 1.7.1 right now and it indeed produces bad results, while the original environment works well.
I will investigate where the inconsistency is, in these days. Before that, probably you could find another environment using the same environment (Pytorch 1.1.0) to run the evaluation.

Thanks for your help!
I see that someone seems to have a similar issue for NAS on pytorch 1.3.1 so it's possible the backwards compatibility breaking change happened between 1.1. and 1.3.

Hi, I just found the change of torch.nn.functional.grid_sample is the problem. It affects the construction of feature cost volume.
"Default grid_sample and affine_grid behavior has changed to align_corners=False since 1.3.0. Please specify align_corners=True if the old behavior is desired. See the documentation of grid_sample for details."
So change the the grid sample in https://github.com/thuzhaowang/idn-solver/blob/6b5dcfd94f35cc118c5dee0f98401e4848e670e3/core/utils/inverse_warp.py#L108 and https://github.com/thuzhaowang/idn-solver/blob/6b5dcfd94f35cc118c5dee0f98401e4848e670e3/core/utils/inverse_warp_d.py#L123 with align_corners=True will solve the problem for higher version of Pytorch (1.3.0 or later).

This looks a lot better, thanks!


feat: soft User deletion

closes #167
What does this PR do?
This PR introduces an endpoint that enables the soft deletion of users from the system. The endpoint will mark a user as inactive instead of permanently deleting them, allowing for the recovery of the user’s data if needed.
How to Test

Soft Delete a User:

Use the endpoint DELETE /api/v1/users/:user_id to soft delete a user by their user ID.

Verify Soft Deletion:

Check if the user’ is deleted from db.
Ensure that the user is no longer retrievable through the regular user retrieval endpoints.

Edge Cases

Test whether the user exists before attempting to soft delete.
Test whether the user has already been soft deleted.
Test the behavior of the system when trying to soft delete a user that does not exist.

Checklist

Implementing the /api/v1/users/:user_id endpoint for soft deletion.
Validating the user_id parameter to ensure it refers to an existing user.
using ths softdelete type orm method to delete the user.
Writing tests to validate the soft deletion functionality and edge cases.

Responses

Successful Response:
{
       "status": "success",
       "message": "Deletion in progress"
}

Error Response when the user does not exist:
{
    "status": "error",
    "message": "User not found",
    "status_code": 404
}

@Heba-WebDev @Homoakin619 done.


[ENH] Shapelet quality measures

Reference Issues/PRs

What does this implement/fix? Explain your changes

Any other comments?

Would keep all changes inside _wip for now.

done


Default SKIP_INSTALL to YES for static libraries

Child of #350. Addresses 4.
SKIP_INSTALL being NO by default for static libraries results in invalid archives.

Nice. Should there be any other settings in here? Anything from https://github.com/yonaskolb/XcodeGen/blob/master/SettingPresets/Products/framework.yml?

Nope. All the other settings apply to bundles.
Sent with GitHawk


Improved Dose calculator options

Arranged list of crops in lexicographical order in select crop option for better view and updated caption in the Dose calculator page.

Successfully merged!


[Java] [Feature] Load from SavedModel

Make it possible for the Java library to load exported TF models in SavedModel format.
Outline of the proposed design:

Define a new class SavedModelBundle to represent the loaded saved model.  Properties include the graph, session, and metagraphdef.
Define a static method on SavedModelBundle to load from disk, given an export path and some tags.

class SavedModelBundle implements AutoCloseable {
  public Graph graph() { ... }
  public Session session() { ... }
  public byte[] metaGraphDef() { ... }
  public void close() { /* close the session and graph */ }
  public static SavedModelBundle loadSavedModel(String exportDir, Set<String> tags) { ... }
}

Write a JNI method to support loading, based on TF_LoadSessionFromSavedModel from the C API.

Here's a WIP - do tell if there's any objections to the approach, otherwise I'll write some tests and submit.
https://github.com/cookieai/tensorflow/commit/64360fc51bd5ce48b06f52901e032313b68dfacd

@jhseu : Weren't you looking into this? Is @EronWright 's plan above in sync with yours?

Ah, yeah, I was going to do it last week but illness prevented me. Seems like it saved me some time :)
@EronWright happy to review the pull request when you think it's ready.

@EronWright some feedback on the code: I was imagining we'd use a static factory method on the Session class. Is there a reason to make a new SavedModelBundle class instead (note that the C++ equivalent isn't ideal and may change)?
Something like:
public static Session loadSavedModel(String/Path path) with a variant that also retrieves the metagraphdef.

@jhseu I thought that too but it didn't work in practice.   TF_LoadSessionFromSavedModel produces both a session and a graph that the caller takes ownership of.   The session never takes ownership of the graph.   Meanwhile, the JNI method may produce only a single return value.   All together, a SavedModelBundle  was the obvious solution.
Regarding the metagraphdef, a saved model is not very useful without it because it contains the signaturedefs.

That looks like a good approach to the issue. Is there any part of the implementation still missing in https://github.com/cookieai/tensorflow/commit/64360fc51bd5ce48b06f52901e032313b68dfacd, or just the tests? :)

@Enet4 thanks, and feel free to try the updated patch posted above.

@EronWright @Enet4 as the documentation is a bit lacking...
I am trying to use SavedModel like so:
SavedModelBundle.load("/path/to/directory");
but am getting an UnsatisfiedLinkError. My directory contains the following files which were saved using the saver.save python API: https://puu.sh/uC4fq/ad18591acb.png.
Am I using SavedModel incorrectly? I will add some documentation after I figure out what the issue is here! Thanks in advance.

@nirajpatel My hunch would be that the JVM is failing to link with the native library. What is the message carried by that exception?
But there is one more thing you need to fix, though. You should use the saved_model API for the saved model functionality, not tf.train.Saver. Although the formats for checkpoints and saved models share several similarities, I don't believe they're interchangeable.

@Enet4 thank you for replying!
The exception I am seeing is:
java.lang.UnsatisfiedLinkError: org.tensorflow.SavedModelBundle.load(Ljava/lang/String;[Ljava/lang/String;[B)Lorg/tensorflow/SavedModelBundle;
	at org.tensorflow.SavedModelBundle.load(Native Method)
	at org.tensorflow.SavedModelBundle.load(SavedModelBundle.java:37)

I was originally seeing this because I didn't link to the native library but I am running with the JNI I believe:
(VM Options)[https://puu.sh/uCGut/c04c641b11.png]
(Project Structure)[https://puu.sh/uCGwE/ba35337d9c.png]

But there is one more thing you need to fix, though. You should use the saved_model API for the saved model functionality, not tf.train.Saver

Ah! That would explain it. Is the saved_model API newer or preferred to tf.train.Saver?

Ah! That would explain it. Is the saved_model API newer or preferred to tf.train.Saver?

The saved_model API is more recent, but to my understanding, it does not invalidate the other one. If you want to save the graph and all its variables for use in other programs and tools, for a variety of purposes (serving, fine-tuning, etc.), saved_model is more indicated. To keep checkpoints of the training process, using tf.train.Saver is more appropriate since it also allows you to specify a global step and the maximum number of checkpoints to keep.
As for the message, I cannot tell for sure why that happens. It might be that you are still using the jni dynamic library from a previous version of TensorFlow.

Good point @Enet4! I am using the PREVIEW1 JNI but I compiled from source in order to get the latest changes (including this one). Is there currently a way to build the JNI from source? The only option I see in the readme is https://github.com/tensorflow/tensorflow/tree/master/tensorflow/java#quickstart step number 2.

The saved_model API is more recent, but to my understanding, it does not invalidate the other one.

This makes sense! I will start using saved_model.

Nevermind, the JNI is in my build directory! I will use that. I really appeciate the help @Enet4. Thank you. I will send a PR to update the readme soon.