Read NeoForge ats from userdev config

Relevant discussion from the NeoForge discord: https://discord.com/channels/313125603924639766/570666026077913098/1314619513525768202

After my inspection, this is the root issue of #229, we couldn't add another at/aw for forge/nf projects if we have an aw in the common project.
I manually merge these two files for forge/nf projects in my workaround.

@qyl27 As far as I can tell, this is unrelated to #229. The crash there occurs because

the decompiler cache is making genSources only decompile the NeoForge classes
our patch removes all Neo/Forge line numbers from the line number map, leaving it empty:
https://github.com/architectury/architectury-loom/blob/f79827465cf8a70a908bb39990c46dbd50decea7/src/main/java/net/fabricmc/loom/task/GenerateSourcesTask.java#L452-L475
Fixing the TODO in GenerateSourcesTask would fix your bug (but it's still not a priority since access widening loader classes isn't something we support).

Fixed in 1.9.

Oh, now I see, thanks a lot for your explanation.


make auth fails first time

From a first run/initial set up, make auth will return this error:
/workspaces/AzureTRE//devops/scripts/create_aad_assets.sh: line 21: AUTO_WORKSPACE_APP_REGISTRATION: unbound variable
make: *** [Makefile:432: auth] Error 1
This is because AUTO_WORKSPACE_APP_REGISTRATION is referenced in the env.sample, but it is commented out.
It needs to be uncommented, OR the code should assume false if not set.

Additionally, make auth fails first time because these values are present in the .env.sample file...
API_CLIENT_ID=<__CHANGE_ME__Generated when you run `make auth`>
API_CLIENT_SECRET=<__CHANGE_ME__Generated when you run `make auth`>
SWAGGER_UI_CLIENT_ID=<__CHANGE_ME__Generated when you run `make auth`>

...but are not commented out. As the comment says, they will be generated, but when a developer copies the .env.sample they will either need to delete these lines, or comment them out, because the values here will break the script.


Suggest not triggered after SPACE

Hi,
The suggest function is not triggered when the user hit space.
In my app, I would like to implement a feature where I can look up the document I parsed for list of words so that: "development" and "development " give different suggestions.
Is this possible to trigger a new suggestion with ending space?
Thanks.

Hey @guillaumegarcia13 ,
You have total control over the suggest function.
In the examples in the site I trimmed term in my implementation of suggest because it made sense for me.  You don't have to do that in your implementation - you can produce different suggestions if there is a trailing white space.


Adjust brouter Profiles

Hi,
is there any way to use custom brouter profiles for generating routes? Or what would be the best option to add a Profile?
Thanks a lot

The current only way is to fork both this project and the brouter project. I don't think @vcoppe has any plans to implement custom profiles but I wouldn't know.

Hi,
i currently use my own local build of gpxstudio with my own brouter instance.  a little bit of an issue is, that there currently seems to be no way to list available profiles from the brouter side, so i need to hardcode them into gpxstudio. i will see if i can figure something better out...
cheers

made a little change to brouter to query profiles and profile names (https://github.com/abrensch/brouter/pull/752). maybe it would be a good idea to list not hardcoded profile names, but the ones available on the server?

If there are routing profiles that you think would deserve being available for everyone, I can definitely add more of them. (you can check here those that are already on my own BRouter instance)
Another feature could be to use the profile:xxx=yyy query parameter (briefly documented here: https://github.com/abrensch/brouter/blob/master/brouter-server/src/main/java/btools/server/request/ServerHandler.java) to customize a routing profile on the fly, using a few buttons. I haven't experimented with it, so I have no idea how flexible it is.
Finally, I just discovered that there is BRouter routing servers have a profile endpoint to upload a custom routing profile that can be used temporarily. We could imagine a dialog like the one for the custom layers to manage this, if this is really something needed.


Master is not compiled in VS 2013

Fixed via https://github.com/fsprojects/VisualFSharpPowerTools/commit/c474ac16df14d04b820f8296d83a47439867ca4a


Release 0.2.0

It looks like the 0.2.0 release won't require building the extension at all if String.method_defined?(:unicode_normalize) is true. This is a really nice benefit on modern Ruby versions. Is there anything holding up promoting the beta to a proper release?

I really hope there's still a way to ensure that unf_ext can be enabled despite String.unicode_normalize being available. Ruby's built-in Unicode normalization is abysmally slow, and unf is among the fastest available on any platform. Ever since unf was recently updated to support Unicode 9.0 (and unf_ext has followed), there should be feature parity between both implementations.

Hi @knu any word on the new release?

1.0.0 will be better

@knu hey, any chance for a new release?


fix checksums of demo images from Pixabay

Fixes #404.

As suspected in #404, images downloaded from Pixabay might include very subtle changes that are not perceptible to the human observer, but change the checksums. An example are the two images below.
Since the Pixabay license is very permissive and only forbids redistributing on stock or wallpaper sites, we simply host the images ourselves.


Add StructListFields function

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (881919f) 93.18% compared to head (fa7c60f) 90.69%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
- Coverage   93.18%   90.69%   -2.49%
==========================================
  Files           6        6
  Lines         396      430      +34
==========================================
+ Hits          369      390      +21
- Misses         22       31       +9
- Partials        5        9       +4

Files
Coverage Δ

struct.go
83.87% <61.76%> (-6.22%)
:arrow_down:

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


Operation-level configs, Docs, Warnings

:tada: This PR is included in version 0.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Kwikset Halo Fingerprint Door Lock Doesn't Appear In HomeKit Using HOOBS

Describe Your Problem:

Logs:
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
{
  "platforms": [
    {
      "platform": "homebridge-kwikset-halo",
      "email"<EMAIL_ADDRESS>      "password": "******",
      "homeName": "Home",
      "mfaPort": 47279
    }
  ]
}

Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
NPM Version:
Operating System:

Issue resolved!  After reviewing the log, the plugin indicated it was awaiting a verification code response.  Once provided, the login was successful and the halo touch was able to be added to Homekit using the add the accessory feature.


Issues spawning the controller

Hello, the controller manager seems unable to spawn the controllers defined in the servo.yaml file. Any suggestions on what maybe the cause??
Error message:
[WARN] [1553489794.674838, 28.573000]: Controller Spawner couldn't find the expected controller_manager ROS interface.

Hi @Leocorp ,
Thanks for reaching out. There seems to be an update for this repository since I created it a year back. Few Solutions which I suggest

Check the namespace of the ros-control gazebo plugin in the model.gazebo , i hope the namespace is kept same https://answers.ros.org/question/198929/running-controller_manager-spawner-with-mybotrobot_description/

There might be an update for the ros-control. You might want to run again
sudo apt-get install ros-kinetic-ros-control ros-kinetic-ros-controllers
sudo apt-get install ros-kinetic-gazebo-ros-pkgs ros-kinetic-gazebo-ros-control

Try these if things work then do tell me I'll include them in the README

Hello @Gauraviitkgp ,

So I checked the namespace and everything seemed ok.
Then I made the installs in the second step. Turns out I didn't have a few of the required packages installed.
And then I made a few modifications to the "servo.gazebo" file.

/servo
gazebo_ros_control/DefaultRobotHWSim
false

Everything works now and all topics are being published. I will be closing this issue now. Thanks.


Add purge functionality and API endpoint

Description
Created an API Endpoint to handle kcp reconciliations purge requests
See also:
https://github.com/kyma-project/control-plane/pull/1453
https://github.com/kyma-incubator/reconciler/pull/934
https://github.com/kyma-project/control-plane/issues/1365

/retest


Autocomplete dataSource empty error

Problem description
Autocomplete throws an error on line 445 (dataSource.every((item, index) =>....) when dataSource is not set.
Steps to reproduce
Create AutoComplete component with empty or null dataSource property.
Versions

Material-UI: 0.18.0
React: 15.3.2
Browser: 60.0.3112.101

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.


4.x Roadmap

This issue is designed to be a high-level roadmap for all work on the 4.x branch. The goal is to provide:

a transparent process for the priority of a given piece of work
an expected release version

The goal is not to discuss specific release dates, though some of that may happen. We'll see.
This list is by no means exhaustive and will change from time to time as new issues are opened and PRs are merged.
4.4

[x] No warnings in React 16's <StrictMode>

[x] Stop using legacy context
[x] Remove all usage of componentWill* methods

[ ] Single-file builds

[x] Add warnings for deprecated react-router-dom/Link-style imports (5bde02b80b68155ba84afeb4f424cb2e7bacde43)
[ ] Add warnings about using 2 different builds (#6361)
[ ] Make tree-shaking actually work as expected (#6464)

[ ] Add unstable_useRouter hook for React 17 alpha

4.5

[ ] Add focus management APIs (#5210, #6449, #6454)
[ ] Add <Link component> API (#5437)

4.6

[ ] Define scope of react-router-config
[ ] Use Suspense to allow cancelling navigation when the user follows another <Link> and the first one is still fetching

Backlog

[ ] Use Codesandbox for all our demos (#6482)
[ ] Isolate build artifacts to a single build directory
[ ] Fully automated releases from CI
[ ] Add a build for react-router-native so we can e.g. exclude __DEV__ code like we do in other package builds

Isn't using the newer context API is breaking change? I think dropping the old context API should be a major version bump.
Old behavior: Routes don't update if rendering is blocked by a parent.
With the new context API, rendering won't be blocked anywhere the context is used.

@samsch We ponyfill for older React versions, so there is no breaking change there. Directly using the context via React isn't supported. You should use withRouter or a <Route> component instead.

@timdorr Relying on the feature existing isn't my concern. The behavior of RR itself changes by using the context API.

Yes, that's a behavior change; a change of a buggy behavior. It doesn't warrant a major release.

It's well-know behavior with it's own docs page dedicated to dealing with it. It was a conscious decision as part of v4 (https://github.com/ReactTraining/react-router/issues/5037#issuecomment-297470402), and there is current code that exists in real projects purely because of it.
For the sake of context for anyone else interested in this, this sandbox exemplifies the change. The route transitions occur with v4.4.0-beta.6, but if you change out for RR v4.3.1 (latest), the routes do not update (due to Blocker). https://codesandbox.io/s/yv5rx2nl7j

Yeah, it's a gotcha that no longer applies. That documentation page goes away and the code set up to handle it becomes inert or unnecessary with 4.4. That isn't a breaking change.

Can #6566 be included in the 4.4 roadmap?

Is there going to be hook variant of the Prompt? From what I gather, it pretty much boils down to this, right ? :)
function usePrompt(when, message) {
  const { history } = React.useContext(Router.__RouterContext);

  React.useEffect(() => {
    if (when && !context.staticContext) {
      return history.block(message)
    }
  }, [when, message])
}

As a bonus, it could also return a reference to unblock for some early unblocking :)

Yay ❤ !
I was just coming here complain about StrictMode, and then I (whacked node_modules ⨯ ran yarn upgrade --latest ⨯ ran yarn install) twice, and voila, indeed no Router errors!!!
Thanks for amazing work!

any idea why "Route" is removed from "react-router-native" v5.0 ??

What's the progress here anyway?

@FredyC That's what the little checkboxes are for ✅
Please feel free to suggest new API in a separate issue.

No thanks, I am switching to https://github.com/Paratron/hookrouter :) So much nicer and easier and does everything I need right now. The react-router surely has its place for more advanced needs.

Inspiring: https://github.com/CharlesStover/use-react-router

@timdorr - with the 5.0.0 release, do we have plans to update typings? Didn't see it on the roadmap here, I'd be happy to grok the changes in this release and modify the 4.x typings accordingly/bump them/etc.

Ok, my b! Thought this group may have had some association with them - all good. I'll raise there - thanks!

Note that I've since picked up TS and have an intermediate-to-advanced level of understanding around it now. I'm happy to take a look at them, but if someone else has more ownership over them, they can take the first crack at it.

The current 4.4 typings there seems to mirror a lot of what was marked as beta flags during that period - I still need to fully vet them myself, but so far testing in our production repo (5.0.0 react-router/react-router-dom and using latest typings) I'm not finding any gaps at least specifically for our use-cases. If we open anything against the repo I'll make sure to @ you on them.

Were there any API changes from 4.3 to 5.0 that require updating the types? DefinitelyTyped mirrors a package's current major/minor, so it could probably use a bump, but I don't think anything should break with the currently released types.

Not particularly. There are some correctness changes to match the PropType reuse we do and to drop things like RouterChildContext, but I don't think there's anything breaking.

4.3 to 4.4 certainly has new typings (path in Router for example accepting an array of matches vs a single string), nothing breaking though (all forward compatible), but the typings in DT are as of 4.4 - so far it seems 💯 in terms of coverage between 4.4.0 to 5.0.0. Got a lot of pieces to vet though atm (large code base :heh:).

I've made an usePrompt hook
https://twitter.com/sseraphini/status/1123321881942265856
https://gist.github.com/sibelius/60a4e11da1f826b8d60dc3975a1ac805
import { useEffect, useRef } from 'react';
import { useRouter } from './useRouter';

export const usePrompt = (when: boolean, message: string = 'Are you sure you want to quit without saving your changes?') => {
  const { history } = useRouter();

  const self = useRef(null);

  const onWindowOrTabClose = event => {
    if (!when) {
      return;
    }

    if (typeof event == 'undefined') {
      event = window.event;
    }

    if (event) {
      event.returnValue = message;
    }

    return message;
  };

  useEffect(() => {
    if (when) {
      self.current = history.block(message);
    } else {
      self.current = null;
    }

    window.addEventListener('beforeunload', onWindowOrTabClose);

    return () => {
      if (self.current) {
        self.current();
        self.current = null;
      }

      window.removeEventListener('beforeunload', onWindowOrTabClose);
    }
  }, [message, when]);
};

Does the IndexRoute, IndexRedirect is removed from 5.X? When I import them from "react-router", prompt no such component

@ozl0402 Those are 3.x components. They've been removed since 4.0. Please read through the upgrade docs.

@ozl0402 Since the aforementioned migration docs are not that easy to find: Here is the link.

Even so I am contributing to React Router for a while I am not sure what's the procedure for adding new features. There are a lot of pending pull requests, some are really really old now, but I think they would be great as new features. Why aren't they merged? How could somebody work on a new major version of React Router where they are added?

https://reacttraining.com/blog/reach-react-router-future/

Stupid question maybe: But what's the plan for SSR? No changes with regards to the new API or just not on the roadmap yet?

@ozl0402 Those are 3.x components. They've been removed since 4.0. Please read through the upgrade docs.

Thank you. Sorry for raise up this question. First time to use it, and many examples mentioned IndexRoute/IndexRedirect, so just be confused about it at that time. But now I already know how to use it. Thank you anyway.

Why have been __RouterContext removed from export in V5 without supplying an alternative approach? That forces us to stick to V4 Beta just because of such a small thing.

Why have been __RouterContext removed from export in V5 without supplying an alternative approach (eg. useRouterContext)? That forces us to stick to V4 Beta just because of such a small thing.

I believe the __RouterContext was never intended to be consumed directly. If you need it prior to the addition of hooks in an upcoming 5.x release, you could probably do something along these lines:
import React, {useContext} from 'react';
import {withRouter} from 'react-router-dom';

export const RouterContext = React.createContext({
    match: null,
    location: null,
    history: null,
});

export const useRouterContext = () => useContext(RouterContext);

export const RouterContextProvider = ({children, match, location, history}) => (
    <RouterContext.Provider value={{match, location, history}}>
        {children}
    </RouterContext.Provider>
);

export default withRouter(RouterContextProvider);

Wrap your top-level component in the RouterContextProvider, and you should be able to use the router context anywhere in your app either of these two ways:
const ctx1 = useContext(RouterContext);
const ctx2 = useRouterContext();

// ctx1 === ctx2

My guess is that when hooks are formally supported in a future version of React Router, something like this will probably be in the core library.

I know there is a workaround and I know it wasn't meant to be used publically. But, it should not have been removed before introducing alternative API :/

withRouter is the alternate API. Please use that.

@timdorr That's highly inconvenient in the Hooks world :( I really don't understand why keeping this hidden when Hooks are stable for some time already. If you have some further plans with that, it's ok, but please don't limit us while working on it.

@FredyC :
The context export is not part of the public API. It's purposefully not documented and using it wasn't and won't be supported. By proxy, there is no obligation (so to speak) to support all the useful things one could achieve with access to the inner workings.

As for hooks:
There are definitely plans for hooks (see this very issue and Ryans blogpost), but at the moment react-router has explicit support for React 15. Support for hooks would require a minimum react version of 16.8, which is another breaking change according to semantic versioning.
On that matter: The bump from 4.3 to 5.0 wasn't intended, but forced due to an unintended incompatability. That's why the major release wasn't "utilized".
Finally: You might find that there still workarounds. But know that they this new workaround won't be supported in any way and is subject to breakage even in minor and patch releases.
@mjackson @ryanflorence I think it would help if you updated this milestone issue according to your previous blogpost.

looks like @timdorr is a bit trigger-happy so i would like to continue here as it's related to #6773 ->
migration from v4 to v5 is painful - just see how many issues are created by this "Error: Invariant failed: You should not use  outside a ". Every component library which previously used links or navlinks for menus & such are now pretty useless just because someone decided to go with Hooks without giving a proper warning or fallback. Was it justified? Probably not? Was it fun to try and develop? Probably yes. Right library to try this out? Hell no. Wasted like a week just to refactor everything to pass root router parts to act in its context.
but not like @justrossthings in the other thread i'm happy with this library

That is why I opened #6755. I agree the context-mismatch issue (which is what causes that error) is a big problem. It's almost always solvable and at its core has nothing to do with this library (which I know is a frustrating thing to hear, but is the truth), but we can certainly do more to reduce the chances folks will run into it.

Question:
Are there any plans to support the simple usage without ?
and also multiple Routers?
<Router>
    <Home path="/" />
    <About path="about" />
    <Posts path="posts">
        <PostList path="/" />
        <Post path=":postId" />
    </Posts>
</Router>

@atothek1 The @reach/router already does that.

Since @reach/router won't be actively developed any further  it is fair to ask if this would come to react-router.

Interesting, I don't why, but for some reason, I got the impression that @reach/router is the future project and this one is abandoned. That changes things 😆
The pattern you have proposed above (and @reach/router does now) has one major flaw, it does not support code splitting properly. There is a thread on Spectrum where I've explained my concerns.

@rovansteen @FredyC This should help https://reacttraining.com/blog/reach-react-router-future/

can I start rewriting all components to hooks?

@sibelius Of course, but we probably won't merge it.

Is this issue "Path is decoded in createLocation #505" going to be on the RoadMap at some point?
Issue ReactTraining/history#505
PR ReactTraining/history#656

I see two things from 5.1 are done and one from the backlog.
Can you release these 3 things as 5.1.0 or at least 5.1.0-alpha?

I recently started a new project and came here looking for an update and found quite a few messages like the one above mine. Sadly, the proposed future doesn't have very good typescript support. Tons of open issues
I hate to advertise another solution and I'm not involved with this in any way, but after a ton of searching, I found this newish react router: https://github.com/frontarm/navi and I've been pretty happy with it.
Do your own analysis, but after wrapping my head around it, I've been pretty happy and the developer is busy, but active in discussions.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 12:09:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 5, errors out: 0
Original problem ID: 16965
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=16965

Problem has been resolved in 6m 0s at 12:15:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 16965


'drain' can be emitted multiple times

In theory... I'm unable to make a case which hits it

Can you reopen this? I'll try to reproduce this tomorrow.

I don't think this is possible anymore given.
https://github.com/mcollina/undici/commit/f6c455bdbbe34e87ebdaebf357f074f0e9a352a9#diff-50cfa59973c04321b5da0c6da0fdf4feR271

You're right. Feel free to close this now :)


Make Gradle work within IntelliJ

The Gant build file I created works - from a command prompt. IntelliJ claims to have Gant support, and there are even settings for it. But despite spending some time trying to make it work I had no luck. Would be nice to be able to execute the build targets from within IntelliJ, and even more so making it the default way for IntelliJ to do stuff so we can dump the Ant script!
This may involve more IntelliJ tinkering like defining artifacts (again, we used to have Blockmania artifacts defined) so good research here that can be done completely independent of our code
Edit: rapodaca got us upgraded to Gradle - which also is supposed to work inside IntelliJ, but quick tinkering got no further than with Gant :D

Suggest closing this one after Gradle build integration complete.

Updated OP - Gradle works now, just needs some tweaks - but I renamed this to figure out how to get Gradle working in IntelliJ now :-)
I guess it works easily in Eclipse?

Works perfectly with IntelliJ. Like it! Can we close that one here?

I was hoping for an Ant-like sidebar button that would allow you to easily execute Gradle tasks from within IntelliJ, but since "gradle idea" does configure the minimum needed bits and the Gradle plugin might not actually be at that level yet I can let it go :D
Let me do some doc updates on this topic first and I'll close it with that done

I saw that link in the recent past, but somehow missed that the individual config tasks are links... heh
Now that makes a lot more sense and it seems there's some potential to set up some quick additional convenience steps - so going to leave that open until one of us gets a chance to tinker, to for instance set the JDK level to 1.6 (seems to start at 1.5 currently)
I did update the DevSetup bits to include Gradle and the current steps to set SDK, Git integration, and Run config: http://wiki.movingblocks.net/Main/DevSetup

Argh - did a giant write-up on this and lost the tab :P

Added a bit more to http://wiki.movingblocks.net/Main/JavaDoc on how "gradle javadoc" actually works despite build.gradle not explicitly defining that target
Added config to build.gradle to set the default JDK to 1.6 so we don't need to do that manually
Sounds doable to set Git as active Version Control via Gradle - but tiny convenience vs needed research
Also sounds doable to include a Gradle Wrapper with the codebase, eliminating the need to install Gradle to run from source, which would be nice: http://gradle.org/docs/current/userguide/userguide_single.html#gradle_wrapper
Groovy plugin comes bundled with IntelliJ, but some fancy features were split off into a separate Ultimate plugin. Maybe that's where they're hiding the goodies
A Groovy facet (that you can add Gradle to) might be exactly what I'm looking for - but my IntelliJ doesn't list ANY facets other than Android at Project Structure / Modules or Facets. Wha? Anybody else see more?
You actually CAN run Gradle tasks from IntelliJ, by treating build.gradle as a Groovy script running the specific task (can highlight the task in build.gradle and right click - run, or even press CTRL-SHIFT-F10)
Some related changes within IntelliJ may actually be in version 11. That might be why I can't find stuff locally yet can find references online

Okay, so I'm not able to let this go quite yet :P
I somehow got the Gradle GUI working, after setting the GRADLE_HOME inside IntelliJ and IDEA_JDK outside IntelliJ (env var). I can now run Gradle tasks via GUI inside IntelliJ and it works - yay!


shortens strings for toMatch to comply with grunt

This fixes the tests for master but will need to be changed once the dev branch with the gauge enhancements (#749) is merged into master.

:boom:-chaka-lakka. Merged into dev. Thank you!


Dual monitor fix

This should fix #1226.
XRRSetCrtcConfig is now used to set video mode  instead of XRRSetScreenConfig.

Ah, very cool. Found a similar solution but couldn't be bothered trying to figure out the correct types etc. :)

I know it's buggy in its current form and I think this is the right way to go, but I don't have a multi monitor setup to actually test this. However, running a program in fullscreen typically means you can't interact with anything on the second screen/desktop since it has exclusive access. At least that's how it's working on Windows. You can't force the ability to continue working on a secondary display.

Can this be tested in a VM?

In theory, but never got multiple screens to work properly. I can set two displays, but "Displays" still only lists a single one.

I changed XRandr check to accept a potential v2.
I fixed code style and  squashed my commits.
The message "Mouse still can't be used in the second screen." was inaccurate, actually it's possible but you have to alt+tab.

I pushed a new revision.
Sorry for code style. I hope I did not forget anything  :)

You are absolutely right about XRRGetOutputPrimary.
We can do a compile time check, then no additional version requirement will be needed in CMake.
As you said 1.3 is quite old now, so it's not really a big deal, but it does not require a lot of changes to do a compile time check, so I pushed a new revision.

@bloodsword Can you follow up on @binary1248's review?

@eXpl0it3r yes. I will try to push something this week.

I pushed a new revision to fit @binary1248 's review.

Would be nice if you could rebase this work onto master to resolve the conflict. :)

@mantognini  I have fetched upstream, rebased the dual-monitor-fix branch and pushed the squashed commit. So everything should be OK now :)

thanks!

SFMLBuildMaster: Build this please.

So I tested this on my dual monitor system.
Manjaro Linux, Cinnamon WM
Monitors:
Left 1280x1024
Right 1920x1080 (Primary)
Using master, I can get SFML into fullscreen and as the open issues describe, the left monitor gets disabled but the fullscreen application is displayed on the primary monitor as it should without decorations.
Using this branch, I can't get SFML into fullscreen. Window decorations are still displayed, however the mouse cursor is locked within the window region. The window is also always positioned at the left-most virtual position if you stitch all monitors together. Using 1920x1080 resolution in fullscreen, a window of that size was positioned on the left monitor and it spanned a bit into the right monitor with decorations. None of the monitors were disabled. Re-arranging the monitors so the 1280x1024 was virtually to the right of the 1920x1080 caused the window to show up on my 1920x1080 still with decorations.

@llongi can you take a look at this and maybe test it with your super 100-WM setup? 😄

I can take a look this week-end. Though it's a VirtualBox VM so not sure how well the multi-screen support works there anyway. I do have a three-screen setup at home (Xmonad WM), so I can at the very least test this there. Will let you know how it goes.

I installed a Manjaro with Cinnamon and I got the same problem.
But the version compiled for my game works, this is probably due to the fix I made for the issue #1224.
I haven't posted a pull request for this bug because the fix is realy ugly.
But I might have a more elegant solution to post. I'll try to post something soon.

The last commit should fix #1226 and #1224.
I have tested my changes on a dual monitors setup (2 x 1280x1024), on Manjaro with Cinnamon and Ubuntu 16.10.  I haven't tested with two monitors with different resolutions like @binary1248's configuration.

I just tested this, works perfectly.

I tried to run SFML in multi screen mode in a VM, but didn't notice any issue before this PR, so can't really test it.
@binary1248 Can you give this another test run?

I gave this another try.
Current version:
No matter what I do in the code, the fullscreen window always shows up on my left most monitor. This is an extended desktop monitor, my primary monitor is to the right of it.
If I create the window with sf::VideoMode::getDesktopMode() it takes the 1920x1080 of my primary monitor and tries to set it on my left monitor which is only 1280x1024. Like this, mode setting fails and no resolution is adjusted, both screens stay on. If I hard code 1280x1024 as window size, the fullscreen window is created on my left most monitor and my primary monitor is disabled.
Window decorations no longer show up in fullscreen as they did in the last version.
I think to fully solve this problem we need the monitor API that has been in discussion for quite a while.

Monitor API would give more choice to user, but I think that selecting a monitor wouldn't be mandatory when creating a VideoMode. So the default monitor would be the primary monitor, as it should be in the curent version without the monitor API. So we still have to solve this issue. Also I think we would face the same issue when implementing the monitor API.
I have done more tests. The setup on my test machine is a bit different than the @binary1248 one (my primary screen is 1680x1050).
The behaviour on my test machine is a bit different but I got the same confusion with getDesktopMode result and the resolution of the selected monitor.
I found the issue, it comes from the setPosition(0,0).
I will try to push something soon.

It took me a while to solve this window position problem :)
I have pushed my commits and updated my repo from upstream.
This code do the XRRGetCrtcInfo mechanics twice if fullscreen is on, that's
a bit "verbose". But I did not want to store X resources as member, since
there are used only when it's fullscreen and only in the constructor.
@binary1248 could you please test this version ?

I don't know what the buggy behaviour looks like since my last commit.
Prior my last commit,  @binary1248 describes some problems, it should be fixed, but except my own test I have no feedback.
@eXpl0it3r reports that some users had problems, but I have no more details.
If you manage to produce a bug with my pull request version (https://github.com/bloodsword/SFML/tree/dual-monitor-fix),
please tell me what is your setup, maybe I will manage to reproduce it and to fix it.
Here is a sample code to test (press escape to quit) :
#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window( sf::VideoMode::getDesktopMode(), "SFML test", sf::Style::Fullscreen);

    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
        {
            if ((event.type == sf::Event::Closed) ||
               ((event.type == sf::Event::KeyPressed) && (event.key.code == sf::Keyboard::Escape)))
            {
                window.close();
                break;
            }
        }
        window.clear();
        window.display();
        sf::sleep(sf::milliseconds(16));
    }

    return EXIT_SUCCESS;
}

The normal behaviour should be a black fullscreen on one of your screen, your other screen should stay active.
Mouse cursor should be locked in the fullscreen monitor except if you alt+tab.

I attribute the test failure during my last test in part to my "exotic" screen setup. I can't test with 2 screens of the same resolution because... well... I simply don't have 2 screens with the same resolution. If others who can test using screens with the same resolution report that this is still an improvement over the state without it, I am willing to accept it as a partial solution on the way to something more complete.

I have no problem with same resolution screens (1280x1024 x 2),
and since my last commit (01 November 2017) I have no problem with different screens either(1680x1050 + 1280x1024).
@binary1248 did you try the latest commit ? If you did, any improvement since your 16 October review ?

I just tried the linked commit (e18b9d2540d8d3b0551ba09c582087c183e4e1c0) out.
I'm on Linux Mint 18.3 and using two 1920x1080 monitors.   The window appears across both of my monitors.  There's a gap across the top of each screen with my desktop background showing.  The gap appears to be the exact size the window titlebar would be.
Here's a screenshot to showing it happen.  I left the monitor app open to show the monitor info in the top left of each screen.

I used the example code posted above, except I added a circle to it as well (to see if it stretched the view, which has happened to me in the past with Windows though I guess that's another issue).  For the sake of completeness this was the test code I used
#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window( sf::VideoMode::getDesktopMode(), "SFML test", sf::Style::Fullscreen);

    sf::CircleShape shape(100.f);
    shape.setFillColor(sf::Color::Green);

    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
        {
            if ((event.type == sf::Event::Closed) ||
               ((event.type == sf::Event::KeyPressed) && (event.key.code == sf::Keyboard::Escape)))
            {
                window.close();
                break;
            }
        }
        window.clear();
        window.draw(shape);
        window.display();
        sf::sleep(sf::milliseconds(16));
    }

    return EXIT_SUCCESS;
}

Actually, I take all of that back.

No problem. When I booted my Mint trying to reproduce the behaviour you describe I did the same mistake :)
Thanks for your feedback :+1:

Using Fedora 28, KDE, two screens at 1080p resolution, using the sample code above, this branch does not fix it for me. I get one screen completely black, and the other still shows the desktop, with the mouse locked in the black screen. The second screen also flickers.

(Made sure I grabbed the right commit this time). Commit e18b9d2 did not work for me. I do see different behaviour between this and master though. When starting the executable with a terminal, the master branch uses the display the terminal is in to start the full screen. When starting the executable with this branch from either display, the full screen starts on the primary display every time, and there is no flickering of the other screen. Running Fedora 28, KDE Plasma, two screens running at 1920x1080.

Tested on Ubuntu 18.10, NVIDIA driver 396.51. Both "master" and this branch work as expected for me...
One monitor is 1366x768. The other is 1920x1080. The fullscreen shows up on the primary monitor.

Nice to read your feedbacks.
Tell me if you need me to rebase the PR on master.

SFMLBuildMaster: Build this please.

Merged in 46ce05cd9c336020e911a1f6a3486132dc31b679


ananthalakshmiragi

Added carouselWithText with html, css and basic js. Contributing to hacktoberfest.
I have read the Code Of Conduct.
I have followed all the steps of submission properly.

Thanks, @ananthalakshmiragi , for opening the pull request! 👏
Star ⭐  this project and tweet about your contributions and tag @clubgamma.
Also join the Discord Server
We are ready to merge your PR!!!

Hello contributor👋,
As we all know that Hacktoberfest-2020 is ended. Hope you enjoyed it a lot and made some awesome contributions.
So now it's time for schwags🎁🤩
Send your email (linked with your GitHub account) in the reply of this comment. Mention any one of the maintainers (@yashpaneliya @rudrabarad @harshptl14 @chirayu-joshi @dhruvpatel1706 ) in the reply.
We'll send a form on the email you'll provide. Please reply ASAP.
Join Club Gamma Discord for future updates.

Hello contributor,
As we all know that Hacktoberfest-2020 is ended. Hope you enjoyed it a lot and made some awesome contributions.
So now it's time for schwags
Send your email (linked with your GitHub account) in the reply of this comment. Mention any one of the maintainers (@yashpaneliya @rudrabarad @harshptl14 @chirayu-joshi @dhruvpatel1706 ) in the reply.
We'll send a form on the email you'll provide. Please reply ASAP.
Join Club Gamma Discord for future updates.

Thanks guys!! @rudrabarad my mail id is<EMAIL_ADDRESS>


Is this Project Dead

We are not Getting any response from dev Kiran kumar atlest Kiran plz tell us is this Project dead or ur working  on fix.

Kiran seems like the only person in the world working on such an app
Maybe Google killed him!

Why don't you mail him?


have make test clean up its files

Description
When I type make test in the gluon-nlp directory, it creates several files and doesn't clean them up:
imdb_lstm_200_0000.params
logs
net.params
net.states
test-682b5d15.bpe
test_glob_00
test_glob_01
test_glob_11
test_numpy_dataset.npy
test_numpy_dataset.npz
test_tsv.tsv

I think it would be ideal to configure things so that these files go into a a temporary subdirectory, which would be deleted upon the completion of make test. Unless there are any issues with relative paths, I think it would be possible to do something like this:
#Makefile
test:
    mkdir tmp
    cd tmp
    py.test -v --capture=no --durations=0  ../tests/unittest scripts
    cd ..
    rm tmp

Or, if that's not your style, there are other ways this could be done, too.
References
n/a

@forresti thanks for reporting this. I agree that it's a bit messy to leave a bunch of these files around. About deleting them, since in GluonNLP we use file hash check to avoid repeated downloads, if these files already exist, it should allow them to run faster. This is why we didn't try to clean the files in the make test target. If users want to clean them, we have a make clean target to clean up all files that are not tracked by git.
To address this problem, I propose:

making sure that data files produced by tests only exist in tests/data and tests/externaldata folders.
once the above is done, if we feel necessary, we can also make a specific target for cleaning up these test data.

Let me know what you think.

@szha Thanks for your fast reply! I like your proposed approach; it would resolve the issue.

Just for fun, I tried make clean. The Makefile contains --exclude="$(ROOTDIR)/tests/data/*", but I don't think the exclude is working. Here are some of the things it removed:
Removing data/
Removing tests/data/cr/
Removing tests/data/embedding/
...
Removing tests/data/wmt2016bpe/


Cache nox & pip in CI

From ci: cache nox

Right now, we recreate the nox environment on every CI run, which is wasteful
as it can take a while to to create it.
This patch caches the nox environment so that it doesn't need to be
recreated on every CI run. The cache will only be updated once a day.
If at some point we save a bad environment or the cached environment
becomes incompatible with newer nox versions, we should bump the
version (currently v1) in the cache key, to force the cache to be
recreated.
Signed-off-by: Filipe Laíns<EMAIL_ADDRESS>

Not waiting on additional reviews since:

This is simple enough.
If this hurts more than it helps, we can iterate on it.
We always have the option of reverting, if we really need to.

Looks like nox isn't happy about being cached.

Are you sure it's because of nox? What is failing here is pip install .[test], I am not sure why that would fail.
Also, I think nox/tox is really helpful to run tests locally but I don't think it makes that much sense for a CI.
My proposal would be something like this: https://github.com/FFY00/python-install/blob/master/.github/workflows/checks.yml
This is the result: https://github.com/FFY00/python-install/actions/runs/125454437
As you can see, everything runs in parallel, it's much faster (the CI setup routines are optimized for fast setup) and results in a more readable CI output. I just thought it was worth asking this before starting looking into why nox is failing.

It's since .nox shouldn't have been cached. #15 reverted that part of this change.


Updated date

Looks like the last change made was 9/20/2017; more recent than 2012. :)
When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

@JennieHubbard You are most certainly correct. Thank you for finding this and for submitting the PR! The change will go live later today.


[5.3][IDE] Loosen assertion check in IDE/SyntaxModelWalker

Cherry-pick of https://github.com/apple/swift/pull/31465 for 5.3

Explanation
We were asserting that the range of each attribute recorded in the AST started at the same location as the fist unconsumed SyntaxNode in the file. This should be true in most cases, but isn't for mispelled attributes that are corrected in the AST, as they are not recognised and not present in the list of SyntaxNodes. E.g. @availability(...) comes through as if @available(...) was specified, but there's no SyntaxNode for it because we don't syntax highlight invalid attributes (to indicate they're invalid).
Scope of issue: Sourcekitd hits an assertion while any file containing a misspelled attribute that the compiler corrects is open (of which there are currently 10).
Origination: When the assertion was added.
Risk: Low. This is purely a refinement of the assertion condition, only impacts SourceKit, and only when built with assertions enabled.
Testing: Added a regression test for this case and all existing tests pass.
Reviewers: Rintaro Ishizaki (@rintaro) on the master branch PR.

Resolves rdar://problem/62201594
Resolves https://bugs.swift.org/browse/SR-12500

@swift-ci please test

@swift-ci please nominate


[💡SUG] 图神经网络模型带权重的数据怎么进行训练，框架实现了带权重的图的模型的构建了吗

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。图片链接二维码图片


Talks page media links.

I read the documentation but was unable to find information regarding linking of a presentation to a post on talks tab.
There must be something I am missing, though i don't know what.

I'm not sure what are you intentions, but here is a sample page for a talk:
title: "Spock vs JUnit 5 - Clash of the Titans, Greach, Madrit, Spain"
publishDate: 2019-03-29
disableLink: true
subLinks:
- type: slide
  link: https://speakerdeck.com/szpak/spock-vs-junit-5-clash-of-the-titans
- type: video
  link: https://www.youtube.com/watch?v=xxx

disableLink: true is only to disable creating a separate page for that talk - only links to media (could be your linked post).

Yes, this is partially what i wanted, also I wanted to include a presentation into the .md page. I assumed that theme can embed presentation into a post, instead what needed to be done was to render an <iframe> with embedded link into the .md file.
Issue is resolved now.
Further, how many options for - type: do we have to our disposal?

I guess there is only support for a Video and Slide links, however I added a .pdf file link that i wanted.

Yeah, that is what I did here, out of the box there is only two external links that you can have. slides and video I added document(pdf) one.
It was pretty easy to add this tho.

@kkYrusobad  I license permits, you could make a PR to add that PDF icon to the theme by default. PDF slides fit here nicely.

I'll do that tonight!

I've added a commit to my pre-existing pull request for the gruvbox theme, I should've made a different branch but there shouldn't be any problems here. Revert back if anything.


Changing Azure AD to Entra ID

What are you changing in this pull request and why?
Updating to reflect the new MS product name
"Azure Active Directory" has been changed to "Microsoft Entra ID"
"Azure AD" has been changed to "Entra ID"
"Active Directory" has been changed to "Entra ID"
Checklist

[ ] Review the Content style guide so my content adheres to these guidelines.
[ ] For docs versioning, review how to version a whole page and version a block of content.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):

[ ] Add/remove page in website/sidebars.js
[ ] Provide a unique filename for new pages
[ ] Add an entry for deleted pages in website/vercel.json
[ ] Run link testing locally with npm run build to update the links that point to deleted pages

Doubled up work by mistake


Minor documentation fix and refactoring changes for DHCP CBMC proofs

Description
This PR fixes few documentation issues and does refactoring changes to the DHCP CBMC proofs.
Test Steps
Run CBMC proofs and unit tests.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue
Documentation fixes and refactoring.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run uncrustify


Multicluster with istio

Bug Description
I have an Aks cluster and a local kind cluster. when creating remote secret in Aks cluster. I check Aks IstioD logs I get:

So that I only get one direction communication. that means local cluster could trust and send traffic to Aks and not viceversa.
Version
istioctl version 1.17.2
Client Version: v1.26.3
Kustomize Version: v4.5.7

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[X] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Your kind cluster is not exposed to the public internet (notice the localhost IP address: <IP_ADDRESS>). There is no way for AKS (or anything on the internet really) to talk to your local kind cluster using that ip address. Consider using something like https://ngrok.com/ to expose your kind cluster

Your kind cluster is not exposed to the public internet (notice the localhost IP address: <IP_ADDRESS>). There is no way for AKS (or anything on the internet really) to talk to your local kind cluster using that ip address. Consider using something like https://ngrok.com/ to expose your kind cluster

I did link kind cluster to rancher with a public apiserver url. and i get : failed creating config configstore for the local cluster. tls failed to verify certificate x509: certificate signed by unknown authority.

Take a look at the docs around the multicluster trust models. You can't just use the default certificates created by each individual mesh; you have to provide each Istio control plane with certificates that have a common root of trust

I did follow istio official docs. it provides : https://istio.io/latest/docs/tasks/security/cert-management/plugin-ca-cert/
I did the same thing between both Aks cluster and it works.


Dell BIOS packages not being created due to Flash64 extract fails to overwrite existing files

Using v6.5.2, I'm seeing an issue with Dell BIOS packages not being created.   Looking at the logs, it appears to be due to an error when extracting the flash64 utility.  When DAT tries to extract the flash utility, if the target file already exists, the extract fails, and DAT appears to skip any further processing for that model and move on to the next model.
As a test, I deleted the ..\DriverAutomationTool\Temp\Ver3.3.8\ directory and ran the DAT download/extract/import again.  This time the flash64 utility was able to extract successfully and DAT continued processing the BIOS and created the package for that model.  However, when it got to the next model, it ran into the original problem.  Since the ver3.3.8 directory and it's contents were created during the processing of that first model's bios, when DAT tries to extract the flash64 utility again it fails because the file already exists.
Here is a section of the logs from that run, in which the bios for the Optiplex 5080 was processed successfully, but processing the next items - the bios for Latitude 7410 and 7420- failed.

======== Dell Latitude 5420 BIOS PROCESSING FINISHED ========	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Remaining models to process: 4	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
======== Processing Dell Optiplex 5080 Downloads ========	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Starting Download, extract and import processes for Dell model: Optiplex 5080	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Setting Dell variables	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Using SKU : 09A7	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Dell System Model ID is : 09A7;09A6	DriverAutomationTool	3/10/2021 9:38:59 AM	26392 (0x6718)
Info: Using Configuration Manager console BIOS package folder - CHC:\Package\BIOS Packages\Dell	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: Using Configuration Manager console Driver package folder - CHC:\Package\Driver Packages\Dell	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
======== Dell Optiplex 5080 BIOS PROCESSING STARTED ========	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: Attempting to match based on multiple model package	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: Found BIOS URL FOLDER06875730M/1/OptiPlex_5080_1.3.2.exe	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: Latest available BIOS version is 1.3.2	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: Checking ConfigMgr for existing BIOS release - 1.3.2	DriverAutomationTool	3/10/2021 9:39:06 AM	26392 (0x6718)
Info: New BIOS download available	DriverAutomationTool	3/10/2021 9:39:07 AM	26392 (0x6718)
Info: BIOS Download URL Found: https://downloads.dell.com/FOLDER06875730M/1/OptiPlex_5080_1.3.2.exe	DriverAutomationTool	3/10/2021 9:39:07 AM	26392 (0x6718)
Info: Downloading OptiPlex_5080_1.3.2.exe BIOS update file	DriverAutomationTool	3/10/2021 9:39:07 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:10 AM	26392 (0x6718)
Info: Downloading Dell flash update utility	DriverAutomationTool	3/10/2021 9:39:10 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:13 AM	26392 (0x6718)
Info: Unzipping latest Dell Flash64 EXE in E:\DriverAutomationTool\Temp\Ver3.3.8-Win64_ZPE.exe	DriverAutomationTool	3/10/2021 9:39:13 AM	26392 (0x6718)
Info: New Dell Flash 64 EXE version is 	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
Info: Latest Dell Flash 64 EXE is 3.3.8	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
Info: Creating new/updated Dell Flash 64 source	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
Info: Archiving legacy file	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
Info: Promoting  release to production	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
Info: Copying Dell Flash64Bit EXE To \CHC-CM\SOURCES$\OSD\DRIVERPACKAGES\DRIVERAUTOMATIONPKGS\Dell\Optiplex 5080\BIOS\1-3-2\	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
ConfigMgr: Creating BIOS Package	DriverAutomationTool	3/10/2021 9:39:15 AM	26392 (0x6718)
ConfigMgr: Enabling Binary Delta Replication	DriverAutomationTool	3/10/2021 9:39:16 AM	26392 (0x6718)
ConfigMgr: Distributing Package CHC0036A to Distribution Point Group - Primary 	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
======== Dell Optiplex 5080 BIOS PROCESSING FINISHED ========	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Remaining models to process: 3	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
======== Processing Dell Latitude 7420 Downloads ========	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Starting Download, extract and import processes for Dell model: Latitude 7420	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Setting Dell variables	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Using SKU : 0A37	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Dell System Model ID is : 0A37;0A36	DriverAutomationTool	3/10/2021 9:39:21 AM	26392 (0x6718)
Info: Using Configuration Manager console BIOS package folder - CHC:\Package\BIOS Packages\Dell	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: Using Configuration Manager console Driver package folder - CHC:\Package\Driver Packages\Dell	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
======== Dell Latitude 7420 BIOS PROCESSING STARTED ========	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: Attempting to match based on multiple model package	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: Found BIOS URL FOLDER06970577M/1/Latitude_7X20_1.3.5.exe	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: Latest available BIOS version is 1.3.5	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: Checking ConfigMgr for existing BIOS release - 1.3.5	DriverAutomationTool	3/10/2021 9:39:27 AM	26392 (0x6718)
Info: New BIOS download available	DriverAutomationTool	3/10/2021 9:39:28 AM	26392 (0x6718)
Info: BIOS Download URL Found: https://downloads.dell.com/FOLDER06970577M/1/Latitude_7X20_1.3.5.exe	DriverAutomationTool	3/10/2021 9:39:28 AM	26392 (0x6718)
Info: Downloading Latitude_7X20_1.3.5.exe BIOS update file	DriverAutomationTool	3/10/2021 9:39:28 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:30 AM	26392 (0x6718)
Info: Downloading Dell flash update utility	DriverAutomationTool	3/10/2021 9:39:30 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Unzipping latest Dell Flash64 EXE in E:\DriverAutomationTool\Temp\Ver3.3.8-Win64_ZPE.exe	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Error: Exception calling "ExtractToDirectory" with "2" argument(s): "The file 'E:\DriverAutomationTool\Temp\Ver3.3.8\ReleaseNotes_FlashUpdate.txt' already exists."	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
======== Errors(s) Occurred ========	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Error: BIOS flash update utility failed to extract	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
======== Dell Latitude 7420 BIOS PROCESSING FINISHED ========	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Remaining models to process: 2	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
======== Processing Dell Latitude 7410 Downloads ========	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Starting Download, extract and import processes for Dell model: Latitude 7410	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Setting Dell variables	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Using SKU : 09BE	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Dell System Model ID is : 09BE;09CD	DriverAutomationTool	3/10/2021 9:39:31 AM	26392 (0x6718)
Info: Using Configuration Manager console BIOS package folder - CHC:\Package\BIOS Packages\Dell	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Using Configuration Manager console Driver package folder - CHC:\Package\Driver Packages\Dell	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
======== Dell Latitude 7410 BIOS PROCESSING STARTED ========	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Attempting to match based on multiple model package	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Found BIOS URL FOLDER07049722M/1/Latitude_7X10_1.5.2.exe	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Latest available BIOS version is 1.5.2	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Checking ConfigMgr for existing BIOS release - 1.5.2	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Comparing BIOS versions	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: New BIOS download available	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: BIOS Download URL Found: https://downloads.dell.com/FOLDER07049722M/1/Latitude_7X10_1.5.2.exe	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
Info: Downloading Latitude_7X10_1.5.2.exe BIOS update file	DriverAutomationTool	3/10/2021 9:39:37 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
Info: Downloading Dell flash update utility	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
BitsTransfer: Checking BITS background job	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
Info: Unzipping latest Dell Flash64 EXE in E:\DriverAutomationTool\Temp\Ver3.3.8-Win64_ZPE.exe	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
Error: Exception calling "ExtractToDirectory" with "2" argument(s): "The file 'E:\DriverAutomationTool\Temp\Ver3.3.8\Flash64W.exe' already exists."	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
======== Errors(s) Occurred ========	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
Error: BIOS flash update utility failed to extract	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)
======== Dell Latitude 7410 BIOS PROCESSING FINISHED ========	DriverAutomationTool	3/10/2021 9:39:41 AM	26392 (0x6718)

I'm also having this same issue.

I encountered this with Dell Optiplex 7080.

Have you seen it with 6.5.3 as well?

Have you seen it with 6.5.3 as well?

That's what I was using.

Hello,
Same issue for me with dell flash 3.3.8, the issue must be due to extract command I presumed


nopython mode generator function does NOT update structured scalar argument

I guess this has sth to do with the implementation details with good reason, but I'd argue the behaviours should be more consistent:

non-generator
generator

np.ndarray arg
✅ will update
✅ will update

np.record arg
✅ will update
❌ no update

version 0.33.0
I need the nopython/nogil mode function to be a generator so that it stays away from python interpreter until a rolling buffer (represented by several fixed ndarray) is filled up, then yield out some intermediate data, for the calling python (slow object mode) code to handle all the data, empty the rolling buffer, then resume the nopython mode generator function (again in performance). A  structured scalar argument to the nopython/nogil function is used to pass range info of the rolling buffer (3 value for a specific case) into and out of the nopython context, since both inside/outside code need such info to address data correctly.
I can replace the structured scalar arg with a few (at least one array per distinct dtype) ndarray args as value containers for this purpose, but that harms a lot to readability and brain health, so hope this is not too hard to fix.
structured scalar proof code:
import numba as nb
import numpy as np

point_dtype = np.dtype([
    ('x', np.float32),
    ('y', np.float32),
])

@nb.njit
def mv(pt, v, steps):
    print(
        ' --- moving point x=', pt.x, ', y=', pt.y,
        'with vector x=', v.x, ', y=', v.y,
        'for ', steps, 'steps'
    )
    d = np.sqrt(v.x ** 2 + v.y ** 2)
    for i in range(steps):
        pt.x += v.x
        pt.y += v.y
        print('  -- step', i, 'to (', pt.x, ',', pt.y, ')')

@nb.njit
def mv_yielding_d(pt, v, steps):
    print(
        ' --- moving point x=', pt.x, ', y=', pt.y,
        'with vector x=', v.x, ', y=', v.y,
        'for ', steps, 'steps'
    )
    d = np.sqrt(v.x ** 2 + v.y ** 2)
    for i in range(steps):
        pt.x += v.x
        pt.y += v.y
        print('  -- step', i, 'to (', pt.x, ',', pt.y, ')')
        yield d

pt = np.rec.array([(0, 0)], point_dtype)[0]
v = np.rec.array([(3, 7)], point_dtype)[0]

print(' *** initial point at', pt)

mv(pt, v, 5)

print(' *** moved to', pt)

for d in mv_yielding_d(pt, v, 5) or ():
    print(
        '  ** moved distance=', d,
        'now at', pt
    )

print(' *** final point at', pt)

which outputs:
 *** initial point at (0.0, 0.0)
 --- moving point x= 0.0 , y= 0.0 with vector x= 3.0 , y= 7.0 for  5 steps
  -- step 0 to ( 3.0 , 7.0 )
  -- step 1 to ( 6.0 , 14.0 )
  -- step 2 to ( 9.0 , 21.0 )
  -- step 3 to ( 12.0 , 28.0 )
  -- step 4 to ( 15.0 , 35.0 )
 *** moved to (15.0, 35.0)
 --- moving point x= 15.0 , y= 35.0 with vector x= 3.0 , y= 7.0 for  5 steps
  -- step 0 to ( 18.0 , 42.0 )
  ** moved distance= 7.6157732009887695 now at (15.0, 35.0)
  -- step 1 to ( 21.0 , 49.0 )
  ** moved distance= 7.6157732009887695 now at (15.0, 35.0)
  -- step 2 to ( 24.0 , 56.0 )
  ** moved distance= 7.6157732009887695 now at (15.0, 35.0)
  -- step 3 to ( 27.0 , 63.0 )
  ** moved distance= 7.6157732009887695 now at (15.0, 35.0)
  -- step 4 to ( 30.0 , 70.0 )
  ** moved distance= 7.6157732009887695 now at (15.0, 35.0)
 *** final point at (15.0, 35.0)

ndarray proof code:
import numba as nb
import numpy as np

@nb.njit
def mv(pt, v, steps):
    print(
        ' --- moving point x=', pt[0], ', y=', pt[1],
        'with vector x=', v[0], ', y=', v[1],
        'for ', steps, 'steps'
    )
    d = np.sqrt(v[0] ** 2 + v[1] ** 2)
    for i in range(steps):
        pt[0] += v[0]
        pt[1] += v[1]
        print('  -- step', i, 'to (', pt[0], ',', pt[1], ')')

@nb.njit
def mv_yielding_d(pt, v, steps):
    print(
        ' --- moving point x=', pt[0], ', y=', pt[1],
        'with vector x=', v[0], ', y=', v[1],
        'for ', steps, 'steps'
    )
    d = np.sqrt(v[0] ** 2 + v[1] ** 2)
    for i in range(steps):
        pt[0] += v[0]
        pt[1] += v[1]
        print('  -- step', i, 'to (', pt[0], ',', pt[1], ')')
        yield d

pt = np.zeros(2, np.float32)
v = np.array([3, 7], np.float32)

print(' *** initial point at', pt)

mv(pt, v, 5)

print(' *** moved to', pt)

for d in mv_yielding_d(pt, v, 5) or ():
    print(
        '  ** moved distance=', d,
        'now at', pt
    )

print(' *** final point at', pt)

which will outputs:
 *** initial point at [ 0.  0.]
 --- moving point x= 0.0 , y= 0.0 with vector x= 3.0 , y= 7.0 for  5 steps
  -- step 0 to ( 3.0 , 7.0 )
  -- step 1 to ( 6.0 , 14.0 )
  -- step 2 to ( 9.0 , 21.0 )
  -- step 3 to ( 12.0 , 28.0 )
  -- step 4 to ( 15.0 , 35.0 )
 *** moved to [ 15.  35.]
 --- moving point x= 15.0 , y= 35.0 with vector x= 3.0 , y= 7.0 for  5 steps
  -- step 0 to ( 18.0 , 42.0 )
  ** moved distance= 7.6157732009887695 now at [ 18.  42.]
  -- step 1 to ( 21.0 , 49.0 )
  ** moved distance= 7.6157732009887695 now at [ 21.  49.]
  -- step 2 to ( 24.0 , 56.0 )
  ** moved distance= 7.6157732009887695 now at [ 24.  56.]
  -- step 3 to ( 27.0 , 63.0 )
  ** moved distance= 7.6157732009887695 now at [ 27.  63.]
  -- step 4 to ( 30.0 , 70.0 )
  ** moved distance= 7.6157732009887695 now at [ 30.  70.]
 *** final point at [ 30.  70.]

The reason the generator version didn't reflect the assigned value is that the record is "copied" when the generator "freezes".  This is due to the lack of reference-counted pointer to the parent data buffer inside the record object, which was introduced prior to numba's refct implementation.
I'm working on a solution.

I think we have to bump this issue to the next release.

Does this link to #1278 and #1807 ? I suspect because they all relate to refct. I'm eagerer for those 2 issues (maybe one solution solves all ?) ...


Security Vulnerability with Hibernate-ehcache

NOTE: Before filing a ticket, please see the following URL:
https://github.com/hapifhir/hapi-fhir/wiki/Getting-Help
Describe the bug
When scanning a docker image build from the hapi-fhir-jpaserver-base, Twistlock/Prisma reports critical security vulnerability:
com.fasterxml.jackson.core_jackson-databind version 2.9.6 has 56 vulnerabilities.
com.fasterxml.jackson.core_jackson-databind is a dependency of ehcache, which is a dependency of hibernate-ehcache. hibernate-ehcache has not updated the version of ehcache (2.10.6) that they use in 4 years, and that version of ehcache uses jackson-databind version 2.9.6 which has a critical security vulnerability.
Expected behavior
Twistlock/Prisma should find no critical security vulnerabilities while scanning any image build from the hapi-fhir-jpaserver-base.
Screenshots

Environment (please complete the following information):

HAPI FHIR Version
OS: [e.g. iOS]
Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

The current Master (for 6.0.0 snapshot builds) has removed ehcache as a dependency entirely, so this should no longer be an issue. Please feel free to reopen if you see this on current master.


Adds ability to mark parameters as multi-value

In symfony/console, you can provide a "mode" to options, which is generally one of "none" or "required". However, you can also mask "required" values with a mode indicating the option is an array; in this scenario, the user can supply the option multiple times, and the aggregate is presented as an array when the command retrieves the option value.
Since parameters are essentially options with the ability to prompt for values if they were not provided, this patch adds support for that mode.
The support is added at the AbstractParamAwareInput level, when calling getParam(). The class now has logic to determine if the mode indicates an array of values, and if so, it will then prompt repeatedly until an empty line (i.e., user presses "return") is provided. If the value is not required, the user can press "return" immediately; otherwise, they will be prompted until at least one value is provided.
The various questions created have been updated to provide information to the user indicating that multiple values may be entered, and also to let them know when a value MUST be entered (i.e., parameter is required).
I have tests for all functionality, which were guided by actual usage within an application (where I was able to determine what did and did not work.)
Fixes #23

In general it looks fine. I do not like only one thing:
* method `setOptionMode` should not be available on our input params, imo.

How I see it is to have additional setter: setMultipleValues(bool true) or something like that which will add the flag internally.
It should be added per input param type - so for example, we should not have this setter in BoolParam as it is using InputOption::VALUE_NONE (yes/no question).
As far as I can see it is the only place where we are mixing (in visible way for users) input params with input options.

When writing the tests, I was having a little nagging feeling that allowing users to set the option mode however they want was a potential issue, despite the safeguards you had me put in. I like this idea a lot better, and will start working on it today.

@michalbundyra Just pushed the changes as requested. I've removed setOptionMode() from both the InputParamInterface and AbstractInputParam, and added the trait AllowMultipleTrait, which will change the mask of $optionMode based on the flag provided. This trait is now used by all param implementations EXCEPT the BoolParam.
I've updated docs as well.


Added minimum versions for dependencies.

Description
Installation of this package via pip could lead to outdated versions of dependent packages being used, which may result in unexpected or insecure behavior. setup.py's install_requires has been updated to require minimum package versions.
This should close #38.
Add versions for dependencies in setup.py
Type of change
Enhancement
Where should the reviewer start?
All changes done in setup.py. The pinned versions should be verified.

Pull Request Test Coverage Report for Build 229

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 98.997%

Files with Coverage Reduction
New Missed Lines
%

nexmo/init.py
2
99.0%

Totals

Change from base Build 222:
0.0%

Covered Lines:
296

Relevant Lines:
299

💛  - Coveralls

Thanks very much @seancallaway!


Clean up of recently merged version

Hello @sifaoufatai ,
Before implementing new functionnalities, I think it would be good to clean up the current version of  your code and do some refactoring...

the bep32v01 directory needs to be renamed because:

you should not have a version number in the directory name
it's not related to bep32 anymore (electrophy) but it is aimed at being more generic... so you can call it BIDSTools
(note that we should also rename the name of the full project, but let's ignore this for now, let's just deal with your code / directory!)

about launch.py

it should be renamed into something else... for example CreateBIDSDataset.py, or something else; please discuss here and let's converge in this discussion before you implement!
translate everything from french to english in your code! (variable names, comments etc.)
rename the variables config_path and output_path: one is a file, the other one is a directory, so they should not be called with similar names (with both path)... to make the difference between files and directories, you can look at other big open source projects and see how they call files and directories (for ex. scikit learn)
simplify the code... lines like json_path = config_path or output = output_path should not exist!: use only one variable name, a meaningful one ;)

@killianrochet can check on all these details if I'm not available tomorrow!

Hello @sifaoufatai ,
I agree with all your comments, and I just want to add something that's very important in my opinion:

You need to seperate clearly your test and your functions.

What I mean is that you don't have to use / test the functions in the main files, you have to test / use them in the test_files which are provided for that purpose. Later on you'll start doing unit tests, so I think it's a good idea to start adopting this separation to simplify your life in the future.


Code examples in readme?

It would be really nice if the readme had some code examples of what's currently possible with the container.
Also, looks like a really cool project :) I've been looking for something like this for a good while!

Hey, agreed. There is examples in the QuadtreeJobs file, could put those also in the readme.

The QuadTreeJobs.cs file does not contain code examples... That is to say it doesn't say how to use this code...
1: How does one make a new NativeQuadTree object into which objects may be added?
2: How does one add objects to the NativeQuadTree?
3: How does one query the NativeQuadTree and return a list or array of items?


[dv-processing] Update to hotfix release 1.5.1

What does your PR fix?

Updates dv-processing to version 1.5.1.

Which triplets are supported/not supported? Have you updated the CI baseline?

all

Does your PR follow the maintainer guide?

yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

yes

@jureviciusr ,Thanks for your pr, if this pr is ready for review, please let me know.

@jureviciusr ,Thanks for your pr, if this pr is ready for review, please let me know.

Ready for review, thanks!

Thanks!


Add StatefulSet support to OTel Operator

As outlined in #14, we want to be able to deploy the Collector in a horizontally-scaled configuration as a StatefulSet.  Combined with other work deriving from #6 this will enable efficiently scaling to a large number of scrape targets.
This issue should be used to track the design of StatefulSet management in the OTel Operator and to aggregate any other issues and PRs created during implementation.

Adding StatefulSet enhancements design doc: https://docs.google.com/document/d/1KO9mQf9owbEsxYMe1yevwEOo5S-J0AE3g3HZyY5fZMo/edit#

This has been completed and the PR #265 is merged.


Create a Makefile

Add a Makefile for IAO release process.
Use make all or make release to create the release directory and all required components. This Makefile utilizes ROBOT, but you do not need to install it (the process grabs the latest version automatically).

This Makefile can be used to update src/ontology/iao-merged.owl and src/ontology/iao.owl, then create a new dated release directory under releases/.
Note that using a releases/ directory was standard practise for Subversion, but with Git the standard practise is instead to simply tag the commit of the release (tagging just attaches a name to the commit).
We should discuss how imports are handled. IAO depends on RO Core, but doesn't specify a specific version. In the recent release directories there's an ro directory with copies of RO Core and its dependencies, which is one way of ensuring that a specific version is being used. This Makefile takes that approach further and creates a src/ontology/ro directory with copies of the RO Core files. The src/ontology/catalog-v001.xml has been updated to use the cached copies. The cached copies of the RO Core files should be checked in to git.
IAO also depends on BFO but does not specify a version, and no copy of BFO has been included in recent IAO release. I suggest just specifying a dated version of BFO in iao-main.owl.

@jamesaoverton and @rctauber I looked into the Makefile and ran the make command. I don't think the IAO used the correct ontology-metadata.owl. It shouldn't use out-of-date ontology-metadata.owl under src/ontology but the one under, information-artifact-ontology/ontology-metadata repository. So, newly added ontology terms in the ontology-metadata.owl are not included in the released iao.owl.
As James said, we are using GitHub tag to track version of each release now. I don't think it is good practice to create a new directory under release and copy over all the related files for each release.
In addition, in the catelog001.xml under release directory, it contains version IRI for each OWL files used to make release version of IAO:

For making it works, we need to add PURL redirect for each of these files. There are some discussion regarding it but no decision yet. I am the person not prefer to do so. So, I am not sure whether it is the way we should follow and put in the Makefile.
Can we have a brief meeting to sort it out (including other issues James raised)?

It's true that this does not yet use the new ontology-metedata.owl. This PR is just about moving the release process to ROBOT.
I'm not sure that I understand what you're saying about the release catalogue file. I'm not worried about PURLs for every file in every release, just for the important files.

import-OBO.owl isn't being regenerated from fresh data. The script for that is in src/ontology/ontofox. cd to that directory and then sh get-ontofox-imports. import-obo.owl will be placed in .., where the other ontology pieces are.

Added to the Makefile.

In the makefile, its not clear how the RO_CORE target is used. I see it in a robot command, but I don't see any imports from bfo-axioms.lisp and bfo-classes-minimal.lisp in the resultant files. If these aren't used then they shouldn't be downloaded. If they are, that's new. Could you point me at the documentation on how they are used, please?

The RO_CORE target is just the RO core.owl with the bfo-axioms.owl and bfo-classes-minimal.owl imports. All three of these are downloaded from their PURL and then given an updated version IRI. ro/core.owl is then imported into iao-main.owl which is used to create iao-merged.owl.

The imports of ro.owl and bfo.owl, and all the imports in iao.owl are to the ontology IRIs rather than to the versionIRIs. Where the source ontologies don't provide up-to-date versionIRIs I make a copy locally and give those versionIRIs of the release date. The PURL yaml reflects that.

iao.owl is created from iao-merged.owl by reasoning over it, so neither have any import statements. I changed iao-main.owl to use the version IRIs of BFO and RO.

The license annotations are missing. <dc:license rdf:datatype="http://www.w3.org/2001/XMLSchema#string">http://creativecommons.org/licenses/by/4.0/</dc:license>. Note, however that in my previous releases the dc namespace was incorrectly defined. It should be http://purl.org/dc/terms/ rather than http://purl.org/dc/elements/1.1. dc terms has license where the elements don't, although contributor is in both.

Added to iao.owl and iao-merged.owl. Does it need to be in any other files?

It wasn't clear what reasoner ROBOT is using. In this case the ontology is small and a full DL reasoner should be used. I've been using fact++.

The default reasoner for ROBOT is ELK. I switched it to JFact.

Nice-to-haves: A generated an XML catalog for Protege, and the new bits to be added to the PURL yaml. Examples available in the last release I did: 2017-03-25

There is a catalog-v001.xml file that is generated in the release directory with dated IRIs.


Changes to Diversity Monitoring Form question

The Why
To allow the diversity team to monitor the success off the PAJE programme which the JDF are particularly keen to keep under review.
The diversity team are not superuser of the platform, nor need to be. They need this information  to see which candidates have actually completed the course and which have just watched the videos that are available to everyone.
The change we need to make is to this question:
Have you taken part in the Pre-application judicial education programme (PAJE)?
The PAJE scheme helps under-represented groups develop their understanding of the role
and skills of judges.
Yes
No
Prefer not to say
Save and continue
We need to change this to:
The Expected
Have you taken part in the Pre-application judicial education programme (PAJE)?
The PAJE scheme helps under-represented groups develop their understanding of the role
and skills of judges.
Yes – online resources and judge-led discussion group course
Yes – online resources only
No
Prefer not to say
User story
As an Administrator I want to make change to one of the diversity monitoring form question so that l can monitor the success off the PAJE programme.
Acceptance criteria ☑
As a user, of the platform l want the platform to display the new changes on  the diversity monitoring form question.

Estimated at 2 SPs as this involves changing a yes/no field to have two yes options and a no... so needs a bit of consideration.


imagemagick6: fix darwin build

Motivation for this change
ZHF: #122042
cc @NixOS/nixos-release-managers
Hydra failure: https://hydra.nixos.org/build/142626527/nixlog/1
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123023 run on x86_64-darwin 1

5 packages built:

cataract
cataract-unstable
imagemagick6
imagemagick6Big
imagemagick6_light


[vale] Review docs Configure Postico or TablePlus to connect to MyMove database

This PR fixes the Vale linting warnings and/or suggestions.

Yeah that's because #61 hasn't been merged in yet. We can leave this open until then or merge it in now in anticipation for #61 getting done.

Closing this as I am unable to trigger a test_build without modifying things and also #61 has not beed merged in. So I'm going to remove this branch and close the PR. We can revisit this work at another time after #61 has been successfully merged into main.


AdvancedSteamFriendsLibrary.h errors

after adding plugin to my projects plugin directory i get this error along with others on that file in visual studio.
Severity	Code	Description	Project	File	Line	Suppression State
Error (active)	E1455	member function declared with 'override' does not override a base class member	fpsProject	F:\Unreal Projects\fpsProject\Plugins\AdvancedSteamSessions\Source\AdvancedSteamSessions\Classes\AdvancedSteamFriendsLibrary.h	198

You do not have the matching plugin version to engine version.


Erroneous env DEBIAN_FRONTEND

Our Dockerfile has the environment variable DEBIAN_FRONTEND set to noninteractive. However, according to documentation/faq, this is not a good practice. Further details below.
Copying as is from Docker faq:

Why is DEBIAN_FRONTEND=noninteractive discouraged in Dockerfiles?
When building Docker images on Debian and Ubuntu you may have seen errors like:
unable to initialize frontend: Dialog
These errors don’t stop the image from being built but inform you that the installation process tried to open a dialog box, but was unable to. Generally, these errors are safe to ignore.
Some people circumvent these errors by changing the DEBIAN_FRONTEND environment variable inside the Dockerfile using:
ENV DEBIAN_FRONTEND=noninteractive
This prevents the installer from opening dialog boxes during installation which stops the errors.
While this may sound like a good idea, it may have side effects. The DEBIAN_FRONTEND environment variable will be inherited by all images and containers built from your image, effectively changing their behavior. People using those images will run into problems when installing software interactively, because installers will not show any dialog boxes.
Because of this, and because setting DEBIAN_FRONTEND to noninteractive is mainly a ‘cosmetic’ change, we discourage changing it.
If you really need to change its setting, make sure to change it back to its default value afterwards.

@sameergautam thanks for digging this. Did we randomly find this or we actually stumbled to a problem because of this?
Please open up a PR to remove this and we will merge it to the master.

Addressed by https://github.com/cloudfactory/ruby/pull/11


Use scrivener 1.2.x's implementation of Enumerable for Scrivener.Page

In a recent version scrivener added their own implementation for Enumerable https://github.com/drewolson/scrivener/pull/33. This module duplication blocks releases with current versions of both libraries.

Oh nice! Great, glad they've added it!
So if I'm understanding right, I just need to remove my duplicate implementation? Do you know any way to conditionally implement it if it exists since I don't know what version of scrivener is being used...

what about assert_impl!(protocol, base)?

Yes, but it raises an error... Hmm... I don't really like catching that at compile time...

I've removed the protocol implementation and required scrivener 1.2 instead. This has been released as 1.1.1 for use with Phoenix 1.2-rc0 and 1.0.11 otherwise.


Checkstyle to solve these issues?

Summary
Regarding audit issues as such, will checkstyle help solve the issue? If not, would I have to solve these manually?
Starting audit...
[WARN] /tmp/home/Arrive.java:4: 'CTOR_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Arrive.java:4:12: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Arrive.java:8: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Arrive.java:8:50: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Arrive.java:10:30: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Arrive.java:12:30: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Arrive.java:15: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Arrive.java:15:29: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Customer.java:5: 'CTOR_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Customer.java:5:14: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Customer.java:5:67: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Customer.java:10: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Customer.java:10: Line is longer than 100 characters (found 123). [LineLength]
[WARN] /tmp/home/Customer.java:10:28: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Customer.java:13: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Customer.java:16: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Events.java:2:22: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Leave.java:4: 'CTOR_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Leave.java:4:11: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Leave.java:8: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Leave.java:8:50: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Leave.java:11: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Leave.java:11:29: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Main.java:3:11: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Main.java:9:35: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Main.java:12:39: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Main.java:13:42: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Main.java:16:32: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Main.java:17:34: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Main.java:18:59: WhitespaceAround: '+' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Main.java:18:60: WhitespaceAround: '+' is not followed by whitespace. Empty blocks may only be represented as {} when not part of a multi-block statement (4.1.3) [WhitespaceAround]
[WARN] /tmp/home/Serve.java:4: 'CTOR_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Serve.java:4:11: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Serve.java:8: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Serve.java:8:50: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Serve.java:11: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Serve.java:11:29: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Server.java:1:13: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Server.java:5:12: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Server.java:10:36: WhitespaceAround: '{' is not preceded with whitespace. [WhitespaceAround]
[WARN] /tmp/home/Server.java:13: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
[WARN] /tmp/home/Server.java:14:27: '(' is preceded with whitespace. [MethodParamPad]
[WARN] /tmp/home/Server.java:16: 'METHOD_DEF' should be separated from previous statement. [EmptyLineSeparator]
Audit done.
Grading terminated.

Hi,
I believe that checkstyle would only help you check this locally. You need to manually fix your code to remove these warnings.

ohno, okay thanks!!

Yes, basically coding style is something that becomes a habit. As you code more in a style, you will encounter less of these errors on checkstyle.

as you code more and more on codecrunch, you realise that checkstyle might be embedded in your brain, and seeing code that doesn't follow the style triggers OCD 🤔

You can also use gg=G to help! It may solve some of these problems.

thanks!


Cloud9 instance: no space left on device

I came back to my Cloud9 environment created by no-tears-cluster after a few weeks of inactivity and when I tried to login, I got no space left on device.   Is it doing some logging that fills up the disk during periods of inactivity?
Looks like the EBS volume is 10GB.
I was able to do
yum clean packages

to free up enough space that I could store the resize.sh script mentioned in the resize EBS instructions but the script failed.
Needless to say, a bit of a hurdle for a mere researcher.

What was the failure?

I tested the resize.sh script on my Cloud9 and it worked wonders, I wonder why yours failed
$ sh resize.sh 20
resize.sh: line 1: !/bin/bash: No such file or directory
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    19  100    19    0     0   1583      0 --:--:-- --:--:-- --:--:--  1583
{
    "VolumeModification": {
        "VolumeId": "vol-00489d7811454ff2e",
        "ModificationState": "modifying",
        "TargetSize": 20,
        "TargetIops": 100,
        "TargetVolumeType": "gp2",
        "OriginalSize": 10,
        "OriginalIops": 100,
        "OriginalVolumeType": "gp2",
        "Progress": 0,
        "StartTime": "2020-11-08T01:14:52.000Z"
    }
}
CHANGED: disk=/dev/xvda partition=1: start=4096 old: size=20967390,end=20971486 new: size=41938910,end=41943006
resize2fs 1.43.5 (04-Aug-2017)
Filesystem at /dev/xvda1 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/xvda1 is now 5242363 (4k) blocks long.


$ref in test schema is not a valid URI reference

Hello @Julian and everyone. Thank you for providing great tests for us!
The commit ref with quote contained in the PR #259  arose a question.
According to the metaschema, $ref keyword only accepts values, whose format is uri-reference. The RFC 3986 does not permit quotation mark (U+0022) in the fragment part of URI reference, unless the character is percent-encoded.
Therefore the given test schema itself is not evaluated as valid by validators which recognize format keyword.
The test schema:
"$ref": "#/definitions/foo\"bar"

should be
"$ref": "#/definitions/foo%22bar"

But this modification to the test case may cause a problem for validators which does not process the value of "$ref" as a URI reference.
Any idea for this problem?

Any implementation that does not process $ref as a URI reference is wrong.

Yeah, looking at the diff for #259, that fragment should be URI encoded, not merely JSON-backslash-escaped.


[FEAT - Deeplink] Get wallet address and assets; Send transactions to EVM #2

Cross posting here from the deeplink repo, as there is no activity: https://github.com/TanglePay/TanglePay-DeepLink/issues/2
I created a web app of my dapp and also want to get it working on mobile. Therefore a few questions arise:
Is there a way, similar to the tangle-pay sdk to get the address and assets from the connected wallet with a deep link? Is there also a way to send transactions to the evm with a deep link?
Having this functionaliy would make it possible to use tangle pay with mobile apps.

Hi @maxcodefaster thanks for the feedback. It is recommended to use sdk in mobile scenario, for more seamless experience.
The mobile app and wallet are technically disconnected with deeplink only, which offers limited functionality and hooks.


Multi Region EKS Cluster Blueprints Pattern with Database

Describe the solution you'd like
A new blueprints pattern to demonstrate the deployment of a multi-region EKS cluster with a containerized stateful application which has Aurora Global database and demonstrate the failover.

@rameshv29 Are we planning to make progress on this pattern or we can close it?


undefined symbol: shmt_fetch

I've met an error with shmt extension under php 7.1.5
It is building normally (on Debian 9 system) but tests are failing (and in fact extension is not working) because of this error:
 symbol lookup error: /home/petr/build/php/SHMT/modules/shmt.so: undefined symbol: shmt_fetch
I am attaching build log and test results.
shmt_build.txt
php_test_results_20170912_0946.txt
The main differences with your travis config is php version and that I use non-zts debug mode.
It seems that the problem is with inline function shmt_fetch and is somewhat related to compiler mode and/or flags. I've removed inline keyword and the error has been disappeared, and all is working.

In the function declaration the keyword static seems to be missing. Please try to change the declaration as following:
static inline shmt_object *shmt_fetch(zend_object *object)
then to build the extension and to run the tests again.

Thank you, all tests with this patch are passing.
diff --git a/php_shmt.c b/php_shmt.c
index d37df6f..39c3bce 100644
--- a/php_shmt.c
+++ b/php_shmt.c
@@ -10,7 +10,7 @@
 zend_class_entry *ce_shmt;
 zend_object_handlers shmt_handlers;

-inline shmt_object *shmt_fetch(zend_object *object)
+static inline shmt_object *shmt_fetch(zend_object *object)
 {
        return (shmt_object *)((void *)(object) - XtOffsetOf(shmt_object, std));
 }

Thank you for reporting the bug!