No writing takes place whatsoever

Hello there.
Short story: I came here to get some knowledge about writing drivers for Windows. Prerequisites for this "Getting started with Windows drivers" was C/C++ knowledge and, obviously, some experience with actual programming, because you, obviously, can't write drivers if you don't understand a thing about programming. So, I've expected this "Write your first driver" to be actual tutorial on how to write your first driver, and not "how to create project and test if you installed WDK correctly". I know how to use Visual Studio, and I think that many other people who came here also know this (if not, then you can just send them down the link to "how to create projects in our Visual Studio" and be done with it). What I don't know is how drivers work and how to code them properly, and this article says absolutely and completely zero bits of information about that.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 81568a12-c39e-a18f-8f33-c54545f14bac
Version Independent ID: 73217b22-1795-b5d0-65cb-1984f38dc661
Content: Write a universal Hello World driver (KMDF)
Content Source: windows-driver-docs-pr/gettingstarted/writing-a-very-small-kmdf--driver.md
Service: unspecified
GitHub Login: @nabazan-microsoft
Microsoft Alias: windowsdriverdev

Thanks for the feedback, @Shorrer.
I'll take a look at how we can either rename these topics to be more transparently correct and to point to what it really means to write your first driver, which may mean writing a book...
Thank you so much for taking the tiome to respond.

Maybe these can be moved from "Programming guides" section (I refer to sections at this page https://docs.microsoft.com/en-us/windows-hardware/drivers/index) to "Code samples". Actual name can be something like "Compile your first drive", so people wouldn't expect from them a full-blown explanation on how to write your own drivers. It is really a problem of slightly deceiving naming because, as you noted and as searching through the web proved, it really takes a book to explain writing drivers.
Thanks for the response.

Thanks for the feedback, @shorrer.  I'm just at a bit of a loss what to do with it.
The goal of this topic is to provide everything you need to create Hello World, from creating the VS project, to adding the minimal code, to building and deploying the driver, with a few hints on debugging.  These are all necessary steps when writing a driver.
I suppose we could change the word "write" to "create" in the title, but I'm not convinced that would add any value.
Also note that the "Programming guides" section is just a set of links to useful pages to start your driver journey.  I think this page belongs there much more than in Code Samples, which is the link to a separate driver sample repo.

Hi @Shorrer , we've gone back and added some more explanation to the "writing code" step. While there is still a certain amount we need to prescribe for the first driver code you write, we broke it down into a few more steps and explained what you were writing along the way with comments. Do you think this is more accessible to programmers who are just starting with writing drivers?

Yeah, this suits the title exactly the right way: now it is perfectly clear what is used for what and how driver should be structured at all. Links to programming reference for functions and objects are also there, so it is now possible to easily get more specific information if it's required.
I want to thank everyone involved in the edits that was made to this page. This page has gone from "copypaste this into your editor" to easy for understanding explanatory article about basic driver development principles, which is very useful.

You're welcome, happy to hear it! Thanks for helping us improve the docs. We're always looking for ways to make them better, so collaborative feedback like this is very valuable.


adding phase dependence to prop. effects

@benjaminrose PR to add phase dependence to propagation effects. I don't think this should cause any issues (I've tested phase-dependent, wavelength-dependent, and phase+wavelength-dependent effects), but happy to discuss.

It looks like there are some errors in the testing. I know some are on SNCosmo's side but @jpierel14 does the p39 tests pass locally?

Justin and I talked a bit offline. We noted that making phase be the first parameter (though logical if we were just starting) breaks backwards compatibility (see failing tests). Likely it is best to make phase an optional argument rather than a required positional argument.

@jpierel14 do you know why propagate is defined so many times?
To get this merged, I think we should

[ ] add a test
[ ] shift phase to an optional parameter to keep backwards compatibility (def propagate(self, wave, flux, phase=None):)
[ ] also see if there is a need to refactor how propagate is defined. We might fix that here, or it might be its own issue.

The code style error is an easy fix, and I will do that. Let me also review the changes to look for maintainability problems. Other than that, it looks like we are on the right path to adding this new feature.

@benjaminrose Okay new try

Look at all those check marks

I have a few documentation additions. I was going to do them myself, but I con't have push access to your repo. I'll just push them to main after I merge this in.

Sounds good, thanks a lot!


xscale with densities looks strange

mwe = (; x = max.(0.1, randn(10000)))

plt = data(mwe) * mapping(:x => "x") * AlgebraOfGraphics.density()
draw(plt; axis = (; title="using `xscale=log10`", xscale=log10))

gives

while, using the same data,
plt = data(mwe) * mapping(:x => log10 => "log10(x)") * AlgebraOfGraphics.density()
draw(plt; axis = (; title="using transform in `mapping`"))

gives

The difference looks even more extreme in my non-MWE data. I think these should be the same, right? Is there a bug somewhere?

So, the order in which things happen is the following.

The transformation in mapping is applied
The analysis (eg density) is computed
The scales are changed in the plot

Note that 3. (setting axis keywords like scale) does not affect 1. and 2. (things would get a bit too complex if it did), it just changes how the plot appears.
So it's actually expected that the two plots should be different, in that the first plot represents the pdf of x displayed in log scale (IMO, a slightly dangerous thing to do, as the total area will be different than 1). The second plot represent the pdf of log10(x), which differs from the first by a factor 1 / (x * log(10)).
I confess I find the current behavior reasonable, but I agree it can be surprising. Is it a matter of documenting it (potentially in a FAQ), or do you think the behavior should change?

I see, I think the real problem then is my lack of understanding of what I was doing-- I forgot that

the pdf of x displayed in log scale

and

the pdf of log10(x), which differs from the first by a factor 1 / (x * log(10)).

were different. But of course they are, e.g. https://math.stackexchange.com/a/613623.
It's probably not the responsibility of AoG but I think a pointer to this difference somewhere could make sense-- I suspect more people will be using density who have't done a lot of KDE before (like me) just since AoG makes it so quick.
For the semantics, I agree that's reasonable behavior for AoG, and essentially what I expected.

It's probably not the responsibility of AoG but I think a pointer to this difference somewhere could make sense-- I suspect more people will be using density who have't done a lot of KDE before (like me) just since AoG makes it so quick.
You are right that this is likely to trip people up, I'm adding some discussion about it in #206


use /bin/bash shebang in emacs-capture script

see https://github.com/koalaman/shellcheck/wiki/SC2039

I'm not against changing the shebang in principle. However, would you care to commit what exact functionality did I use that was undefined in POSIX?

sure:
$ shellcheck emacs-capture
Line 5:
argv=()
     ^-- SC2039: In POSIX sh, arrays are undefined.

Line 8:
    argv+=("$(echo -n "$arg" | sed -Ez "$re")")
    ^-- SC2039: In POSIX sh, += is undefined.
          ^-- SC2039: In POSIX sh, arrays are undefined.
                   ^-- SC2039: In POSIX sh, echo flags are undefined.

Line 13:
emacsclient "${argv[@]}"
             ^-- SC2039: In POSIX sh, array references are undefined.

should i put some of that into the commit message?

Thanks!
Not necessary - I think that this discussion is enough to document it.


doc: [dsa] Dockerfile is downloaded but not used in the screencast file

Though I don't have the hardware platform to try out, though this screencast file screencast-dsa-accel-config.sh seems to work, but it downloads a Dockerfile but not uses it, which looks a redundancy.
command 'curl https://raw.githubusercontent.com/intel/intel-device-plugins-for-kubernetes/main/demo/dsa-accel-config-demo/Dockerfile' 100

it's on purpose to show the content of the image that is used.


Please enhance Custom Directives

What problem does this feature solve?
Let me start by saying I love Vue. It is an awesome framework you guys have created, I enjoy using it, and it is at the very top of Frameworks of choice.
But from day one there has been one small area where I found Vue lacking, this is in the Custom Directives department.
I wasn't around for Vue 1, but from what I can gather a decision was made to "underpower" Custom Directives in favor of Components. And I agree, when you are developing applications Components is most likely all you need.
The problem starts when you want to create plugins, especially UI plugins. I have created UI plugins in other Frameworks, specifically a Bootstrap native implementation, I have several features that are implemented with Custom Directives, I like how clean they are that way. But when I tried to achieve the same thing with Vue, well I got frustrated very quickly.
Problem Number 1: We don't have a Vue instance. I wish we could create Custom Directives the Same way we create Custom Components. so we have an actual Vue Instance and we can use this. Right now you have to manually extract the directive bindings and store them in the in the element itself. It is not clean since I have to pass the el object around to have access to those properties. It is doable but not very clean.
Problem Number 2: The update hook function it is not being called consistently. For instance, I have this: v-myDirective={foo: bar}; when bar changes the update method is not called, only when something in the DOM changes then update is called. This is super frustrating because many times you want to control the state of your directive based off a property value, but you have no consistent way to know if its value has changed. This is a real problem because there are things that cannot be done without a consistent way to know if a binded property has changed. I wish I could have a Vue instance and have watch methods to react to changes accordingly.
I LOVE Vue, it is an awesome framework, I will continue to enjoy using it and to recommend it. But if this is improved I would have absolutely no reason to ever use any other framework.
Thanks for the hard work and love that goes into Vue.
What does the proposed API look like?
The API will basically be the same one we have for Custom Components. The example is silly, but I would love to be able to do something like this:
Vue.directive('myDirective', {
  data: {
    el: null
  },
  props: ['foo', 'name'],
  bind (el, binding, vnode, oldVnode) {
    this.el = el
    //Bind
  },
  inserted (el, binding, vnode, oldVnode) {
    //Inserted
  },
  unbind (el, binding, vnode, oldVnode) {
    //Unbind
  },
  computed: {
    name () { return `My name is ${this.name}`}
  },
  watch: {
    name (value) { this.nameUpdated(value)}
  },
  methods: {
    nameUpdated (value) {
      this.$emit('nameUpdated', value)
    }
  }
})

Why using directives and not components? The API you are suggesting is very close to what already exist for the components.

I wish we could create Custom Directives the Same way we create Custom Components

I think that sentence says it all 😅

The API can be the same, but the usage is different.

I appreciate your support for Vue, but the proposed API is not something we would consider. Vue 1 used to have similar functionalities for directives but we end up duplicating everything between directives and components, and the concept becomes convoluted similar to Angular 1 directives (which is essentially a god concept that can do anything).
It was an intentional decision in Vue 2 to limit directives to one dedicated purpose: low level DOM manipulation and nothing else. Also, due to the rendering mechanism (vdom), directives do not have instances and thus component-like API is not feasible in the first place (no this to point to).
Most of the time what you want to achieve with directives can be achieved with components, and some of the functionalities can be simulated by leveraging vnode.context in directive hooks.

I understand the reasoning behind it, and it is cool. I have been able to do everything I need with a custom attribute but one thing.
If I have a binding like this v-myDirective={foo: bar} and let's say you click a button and the value of bar changes, the update hook function is not called. I haven't found a way to react to such changes. Any suggestions?

@tochoromero that sounds like a bug - please open a separate issue with a reproduction.

@yyx990803 That was actually my bad, there is no bug, trying to reproduce it with the bare minimum showed me my own bug. Thank you for taking the time to answer here, you rock :)


rm extra empty line from control file

causing issues with r4ss

@iantaylor-NOAA , if you have changes to add, feel free to push them here! All I did was (hopefully) get rid of the empty line between the table header and the column names for the Report_Z_by_area_morph_platoon report file table
Still to resolve is

[ ] Figure out why this table is appearing twice
[ ] See if other changes are needed due to getting rid of a subheader line that was present in previous versions of SS3.

@k-doering-NOAA, your fix looks good to me. Seems like you could merge this change first to confirm that the r4ss github action gets working while we investigate the other issues.

I now see that the test-r4ss-with-ss3 action will be conducted on this PR even if you leave it open, but merging would allow future branches from main (or existing branches that get rebased onto main) to avoid the error.

Good point, @iantaylor-NOAA ; I think you are right that this simple change can be merged in once the checks run and we could work on the other issues in a separate branch. I'll merge in tomorrow morning, but feel free to merge it in tonight if you see it finishes

The call-test-r4ss-with-ss3 workflow seems to be working now thanks to the blank line fix, thanks @k-doering-NOAA.
I think that the additional commit 96b1403 resolves the other two issues that @k-doering-NOAA identified.
The subheader separated the "With_fishery" and "No_fishery" tables which previous both fell under the main "Report_Z_by_area_morph_platoon" header. However, those two tables are now reported in separate places (similar to the other output in this section), but with the same header creating the appearance of duplicate tables.
Commit 96b1403 expands the headers to read
"Report_Z_by_area_morph_platoon_2 With_fishery"
and
"Report_Z_by_area_morph_platoon_1 No_fishery_for_Z=M_and_dynamic_Bzero"
A minor change to r4ss::SS_output() was already needed to deal with the different order of the tables so can now use these revised headers to distinguish the two parts.

thanks for cleaning up the mess I made when doing what I thought was a logical re-org of the tables.  I did it partly to elimiate an extra run through the timeseries.
Which reminds me; I think it useful to create another internal flag so we can run through the timeseries simulation without doing the call to get_exp_val.  This could speed up simulation work in general when data generation and logL is not needed

I see, this all makes sense now. I ran a model locally just to make sure it works as we think it does, and looks great!
@Rick-Methot-NOAA  or @iantaylor-NOAA , feel free to merge this in if you agree it is ready.


feat(library): add possibility to use local and docker actions conveniently (#288)

fixes #288

Looks good! I'll just adjust commit messages a bit (I should write down the rules somewhere, or have automation validating it), so I'll take it from here. Thank you 🙇

Oh, what was wrong? I took the existing ones as blue print

Oh, what was wrong? I took the existing ones as blue print

I generally try to follow Conventional Commits. You got it almost right, I only noticed these:

after the colon, the standard proposes using lowercase letter
for breaking changes, there's an exclamation mark before the colon

Ah, right, fixed :-)

issue number goes at the beginning, in square brackets

Hmmm, ...
$ git lo --grep ')$' | grep -v '.......... \[' | wc -l
116
$ git lo --grep '^\[' | grep -v ')$' | wc -l
275
$ git lo --grep '^\[' | grep ')$' | wc -l
56

:-D

issue number goes at the beginning, in square brackets

Hmmm, ...
$ git lo --grep ')$' | grep -v '.......... \[' | wc -l
116
$ git lo --grep '^\[' | grep -v ')$' | wc -l
275
$ git lo --grep '^\[' | grep ')$' | wc -l
56

:-D

Not sure if I understand it correctly, but there are actually two numbers: [#123] at the beginning means "this commit addresses issue #123". (#456) at the end means "this commit was created in scope of PR #456".

Ah, I see.
First line is only number in the end, second line is only number in the beginning, third line is both numbers

Ok, so you tried to reverse-engineer the numbering here :)


Tweak doc banner wording

As discussed, added "released":

Mmmm, should probably now also say "View latest release documentation."


tsai 0.3.6

new tsai feedstock

skip py 3.11 because of lack of pytorch 2.0
skip s390 and ppc64le because lack of support by fastai

so when I remove numba from recipie, I still see that it is included implicitly
The following NEW packages will be INSTALLED:
...
numba:              0.57.0-py310h1128e8f_0
so, indeed this is some indirect dependency
the same happens for ipykernel, when I remove from runtime dependecies, I still see:
The following NEW packages will be INSTALLED:
...
ipykernel:           6.19.2-py38hb070fc8_0


"Scroll to Top" & Jumping bug on small scrolls

Hello,
It is wonderful library, but I seed some bugs or maybe I am using it wrong.

In TableView when I am (for example) in the middle of the table, I am pressing the status bar and system scrolls me to the top, but the navigation bar doesn't want to expand. What is wrong?

When I am making small scrolls (From Up to Down) maybe 1-5 px and I am seeing that the scroll bar jumps like a crazy.

(Just question) Is it possible to add the same effect like in Instagram app? They are not just hiding the navigation bar, but "Minimize" it. I just don't know how to describe this effect correctly, but it look much more better.

Hi @whitefoxy

In TableView when I am (for example) in the middle of the table, I am pressing the status bar and system scrolls me to the top, but the navigation bar doesn't want to expand. What is wrong?

You need to implement this:
    /**
     Calls `showNavbar()` when a `scrollToTop` is requested
     */
    public func scrollViewShouldScrollToTop(scrollView: UIScrollView) -> Bool {
        if let navigationController = self.navigationController as? ScrollingNavigationController {
            navigationController.showNavbar(animated: true)
        }
        return true
    }

I'll explicit this step in the readme.

When I am making small scrolls (From Up to Down) maybe 1-5 px and I am seeing that the scroll bar jumps like a crazy.

Are you able to reproduce this in the demo project? I tried and seems to be working fine.

(Just question) Is it possible to add the same effect like in Instagram app? They are not just hiding the navigation bar, but "Minimize" it. I just don't know how to describe this effect correctly, but it look much more better.

Yeah, I know what you mean, it's pretty cool and it's on my TODO list :)

Thank you for quick response.

This code work fine, but I think it should be override func not public func.
I think it is not really big problem, as I looked other apps they have the same issue.

When Navigation bar is shown try to repeat making scrolls down (1-10px) fast (one by one) and you will see that navigation bar want to hide, but because it is very small scroll system don't let it to hide. And it looks a little bit strange (Navigation bar starts hiding, but because of small scroll it shows back, it looks like navigation bar jumps). Maybe I am the only one who sometimes scrolls in such manner :D

This is very good news. I'll be looking forward to this feature!


mxbuild

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: mxbuild
Document link: mxbuild.md
My Issue/Suggestion
The command line option --gradle-home is not documented but is part of mxbuild.

Thanks for the feedback, @tieniber. I've added this information in the MxBuild doc, as seen in this PR.


Always stuck at 100%

Version
v1.10.4
Platform
windows 11
Steps to reproduce
https://www.youtube.com/@yuansir
Details
download a list over 100 videos
sometime always have more than 5 videos shows 100% for a long time
it keeps 100%
Checklist

[X] I have looked through existing issues to make sure that this bug has not been reported before
[X] I have provided a descriptive title for this issue
[X] I have made sure that that this bug is reproducible on the latest version of the application
[X] I have provided all the information needed to reproduce this bug as efficiently as possible
[X] I have sponsored this project

when download this https://www.youtube.com/@12KScenicRelaxation
it canceled a lot liniks without click cancele btn

If you open task manager, do you see any ffmpeg.exe processes?

@Tyrrrz  when stuck shows,cannot find ffmpeg.exe
but I click cancel on items shows 100% it changes to done then start a new parallel in list
so maybe the completion judgment mechanism of the program  can be diversified

@Tyrrrz maybe can adding a timeout detection when reaching 100% or 99% progress to prevent stuttering and temporarily increasing the number of download threads that exceed the threshold

heres my git screen record at 3fps

I think it just takes a while to complete the conversion process. The progress is reported directly from FFmpeg, unfortunately it can't get more precise than this.

@Tyrrrz i dont know it is  monitor the pid of ffmpeg.exe  or catch a  return from the processor
maybe it has a err on cal whether it is completed or not, I think
and with the number of tasks increases, it is more common to encounter this stuck state, which will continue to be stuck at 100% of the maximum number of tasks without human intervention
it realy shows on my computer


Generate sources, javadocs and pom file required for Maven release

This PR updates the azure-sdk-archetype and azure-build-tools pom files to generate the pom file, sources and javadoc jars required for Maven release.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-sdk-build-tool


HADOOP-17754. Remove lock contention in overlay of Configuration

3089

 Quality gate: Passed
 Everything looks good
Details


[diem-framework] re-enable verifications disabled due to generic invariant

A few functions in DiemConfig.move are marked verify = false because
the global invariants are not instrumented correctly. With the recent
changes in the generic invariant handling, verification of these
functions can be re-enabled again.
This commit also removed a spec that does not match developers'
intention: after genesis, we can still add new configurations types,
an example is the DiemConsensusConfig type. This is discussed
on slack (although a while back).
Motivation
Disabled specs are not good.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI

/land

:broken_heart: Test Failed - ci-test

/land


Smothing configuration via JSON interface

Would be great to have smoothing configurable via the JSON interface, so that it can be altered for different types of content on the fly, like music videos, action movies or television (for me these would be smoothing set to none, time_ms set to short, and time_ms set to long, respectively).

@tvdzwan is this closed because it's never going to happen, or because it's been implemented?


Google+ API Shutdown

Google+ APIs will be shut down on March 7, 2019. This includes Google+ Sign-in and OAuth token requests with Google+ scopes.
How it affecting satellizer, if it is, what are the necessary changes have to take by the end user of satellizer, if satellizer is being updated for this change, does satellizer pushing any patch for this.
Need some explanation, whether it is affecting satellizer users or not.
Ref: https://developers.google.com/+/api-shutdown
@sahat

Short answer: No, satellizer doesn't need to be updated for the Google+ API shutdown.
Long answer:
Because satellizer defaults already use the recommend scopes, it won't need to be updated. But your application might get affected depending on the additional scopes you are requesting during the OAuth flow. For example, one of my applications was using the https://www.googleapis.com/auth/plus.business.manage scope which is now deprecated. So, I updated it to recommended replacement scope https://www.googleapis.com/auth/business.manage.
The defaults scopes used by satellizer are:
https://github.com/sahat/satellizer/blob/ae2863338ab7214e8f3be7b5fae6373a18d7a11b/src/config.ts#L37-L38
which are already the recommend scopes.


Provide default mapbox::geometry::box ctor

This cleans up Envelope code and provides a common boilerplate for custom Box usages e.g.
https://github.com/mapbox/mapbox-gl-native/pull/6553/commits/a9b09854482d809bbda856af811e228b3384d07b#diff-28252c6bc5b2fa114d6d6c5361a7ab52R170
/cc @jfirebaugh @mourner

I'm confused... When is limits::has_infinity false, and what's the difference between limits::min and limits::lowest?

In general, std::numeric_limits<T>::has_infinity is true for floating-point types. It tells if types are capable of representing the positive infinity as a special value. This infinity is then used to calculate std::numeric_limits<T>::min - thus why it does not always returns the lowest value, leaving that to std::numeric_limits<T>::lowest. In sum:

::min() returns the smallest finite value of the given type
::lowest() returns the lowest finite value of the given type

In the context of e.g. float and double:
std::numeric_limits<T>::min():
        float: 1.17549e-38 or 0x1p-126
        double: 2.22507e-308 or 0x1p-1022
std::numeric_limits<T>::lowest():
        float: -3.40282e+38 or -0x1.fffffep+127
        double: -1.79769e+308 or -0x1.fffffffffffffp+1023

We don't really need to check for ::has_infinity because ::lowest() handles that internally.

I'm not sure about making this the default constructor. If there is going to be a default constructor, it seems better to have it be one that default-constructs min and max.
Is the "custom usage" in gl-native really custom? It looks like it should be written as function composition: envelope(rotate(queryGeometry)).

If there is going to be a default constructor, it seems better to have it be one that default-constructs min and max.

What about calling it hull() then - like we currently do in e.g. https://github.com/mapbox/mapbox-gl-native/blob/master/include/mbgl/util/geo.hpp#L97-L102 ?

What about calling it hull() then

What do you mean by that exactly? I think of hull as a special case of envelope (specifically envelope when the input is two points). Previous comment was referring to the the default, no args, constructor for box, which is something different.

Back then there was a need for it - which no longer seems the case.


WoW Vanilla: Character and sometimes monster disappearing when turning camera or moving in caves and tight spaces

Software information
WoW Vanilla (original client, not Classic). Fedora 37 on Gnome.
System information

GPU: AMD Radeon RX 6700 XT
Driver: amdgpu
Wine version:  Soda 7.0-7 on Bottles.
DXVK version: 2.0

Apitrace file(s)
I tried making an apitrace but the game was barely responsive (1-2 fps) on WineD3D.
For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
Log files

d3d9.log:
WoW_d3d9.log

Here's a video showcasing the bug. I was able to reproduce it using the information provided above, but I'd like to add that I've been having this bug for 2 years using many different DXVK and Wine versions and different distros.
https://user-images.githubusercontent.com/38048855/206826292-ba9f3b00-683e-49e0-921a-e08ba78e69d2.mp4
My character becomes invisible when turning the camera and moving inside caves or tight areas. Sometimes, monsters too. It happens frequently enough to be problematic in some areas.

You can make an apitrace with DXVK too, which should run faster. Just set d3d9 to native and copy the apitrace d3d9.dll next to the exe (with DXVK installed to the prefix of course).

Yes a apitrace with dxvk should be fine

Are you sure that this is a DXVK bug and not a game bug?
We really do need that apitrace to look into this. So please make one, even if it's very slow.

Are you sure that this is a DXVK bug and not a game bug?
We really do need that apitrace to look into this. So please make one, even if it's very slow.

I will be sending the apitrace soon, sorry I can't right now. I played with the same exact client multiple times on Windows and never noticed it, but to be absolutely sure it is a DXVK bug, I will also re-try to reproduce it on Windows. I will post a reply with all this information and the apitrace during the day.
Thank you!

You can make an apitrace with DXVK too, which should run faster. Just set d3d9 to native and copy the apitrace d3d9.dll next to the exe (with DXVK installed to the prefix of course).

Even with DXVK + APITrace, the game is still running too slowly to do tests (1-2 FPS). I have the apitrace d3d9.dll in the same folder as the .exe. I have tried setting it to "native" and "native,builtin" in the wine control panel. I downloaded the apitrace from the link in the wiki, and extracted the d3d9.dll from /lib/wrappers/d3d9.dll. I confirmed it is indeed using DXVK by having the env variable DXVK_HUD=devinfo, which did show up in-game.
I also tried running the game on Windows and reproducing the bug, I could not reproduce it. I will try fiddling with the graphical settings to see if anything changes

Try making a file called dxvk.conf where the dxvk log file appeared and insert d3d9.apitraceMode = True. See if that helps

Try making a file called dxvk.conf where the dxvk log file appeared and insert d3d9.apitraceMode = True. See if that helps

@Blisto91 it worked. For some reason, every time I tried it generated 3 trace files instead of 1.  I will upload all 3, but only one of them is big. It will take some time. Do you guys typically use a specific hosting site for those? For the moment, I will be uploading it to google drive

Google drive is fine.

https://drive.google.com/file/d/1jyPAOrdP9WcDj6xryrhgZUzxLwnQEwHK/view?usp=share_link

I did a lot more digging and I discovered I can only reproduce the bug on high framerate which is typically above 250 fps. Tight spaces such as caves have way more FPS because there's not much to render.
Using DXVK_FRAME_RATE, I did the following tests:
DXVK_FRAME_RATE = 30: Impossible to reproduce
DXVK_FRAME_RATE = 144: Impossible to reproduce
DXVK_FRAME_RATE = 200: Impossible to reproduce
DXVK_FRAME_RATE = 220: Impossible to reproduce
DXVK_FRAME_RATE = 239: Impossible to reproduce
DXVK_FRAME_RATE = 245: Impossible to reproduce
DXVK_FRAME_RATE = 250: Possible, but hard to reproduce
DXVK_FRAME_RATE = 300: Easily reproducible.
DXVK_FRAME_RATE = 600: Happens very frequently
We can see the problem starts to appear  >=250 fps, which is coincidentally 10 fps above my monitor's refresh rate (240), I doubt it is refresh rate related, but I could try with another monitor. I tried 245 to see if it is indeed refresh rate related, but it was not reproducible. The higher the FPS, the more easy it is to have this bug, anywhere in the game world, on your character or dead bodies.
Without a cap, I can easily  hit 600-750 fps in caves or anything small since it is quite an old game.
I could not reproduce this bug on Windows, but we must note it might be because it's impossible to reach such high amount of FPS on Windows. DXVK allows this game to run way faster. The maximum FPS I can generally get on Windows is 150, with a lot of variance (60-150 super unstable). It could be a DXVK bug, but really can't confirm since the DX9 Drivers on Windows are too bad to even reach such high FPS. I tried to use DXVK on Windows, but the performance is way inferior to Linux + DXVK. In conclusion, it's hard to tell if it's a DXVK bug on my end, but maybe with the APITrace you guys could find something useful.
A good workaround to cap the fps. I tried using both fsync and esync and got the same results. I will dig a big more to see if I can find anything else.


HTTP/3 Nginx hanging requests

Hi,
I'm having some issues with HTTP/3 nginx + quiche.
After n-times requests to server it will hang and then timeout. Problem is replicatible with curl:
 for x in {1..1000}; do echo " ===> $x"; curl3 -vvI --http3 https://<domain>/ -X GET; done
or with browser (in my case Firefox) with http3 enabled and refreshing page many times.
Number of successful request may vary in range from ~5 to ~350.
I'm sure thats not case of curl (curling to https://cloudflare-quic.com/ will not cause any problems) or problem of nginx or network configuration (http/2 and http/1 will not cause problems as well). I also tried changing nginx configuration of keepalive or http3_ configuration directives.
Nginx works as a reverse proxy to Apache (but I belive Apache is not causing any issues here)
All build on arch linux with pkgbuild from quiche commit: 9d0c677ef1411b24d720b5c8b73bcc94b5535c29 (latest right now)
and nginx version: nginx/1.16.1.
Log from successful curl request:

*   Trying <IP_ADDRESS>:443...
* Sent QUIC client Initial, ALPN: h3-29,h3-28,h3-27
* Connected to <domain> (<ip>) port 443 (#0)
* h3 [:method: GET]
* h3 [:path: /]
* h3 [:scheme: https]
* h3 [:authority: <domain>]
* h3 [user-agent: curl/7.74.0-DEV]
* h3 [accept: */*]
* Using HTTP/3 Stream ID: 0 (easy handle 0x557a6fbc1b10)
> GET / HTTP/3
> Host: <domain>
> user-agent: curl/7.74.0-DEV
> accept: */*
>
< HTTP/3 200
HTTP/3 200
< date: Tue, 19 Jan 2021 10:21:30 GMT
date: Tue, 19 Jan 2021 10:21:30 GMT
< content-type: text/html; charset=UTF-8
content-type: text/html; charset=UTF-8
< vary: Accept-Encoding
vary: Accept-Encoding
< server: Apache
server: Apache
< alt-svc: h3-29=":443"; ma=86400
alt-svc: h3-29=":443"; ma=86400
* Connection #0 to host <domain> left intact

With curl in for loop request will hang to timeout then proceed next request and aften n-times hang again.
 ===> 441
* Trying <ip>:443...
* Sent QUIC client Initial, ALPN: h3-29,h3-28,h3-27

* Connection timed out after 300000 milliseconds
* Closing connection 0
curl: (28) Connection timed out after 300000 milliseconds
===> 442
* Trying <ip>:443...

Strace from nginx process:
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic write handler\n", 62) = 62
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic alarm fired\n", 60) = 60
sendmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(56250), sin_addr=inet_addr("<ip>")}, msg_namelen=16, msg_iov=[{iov_base="B\200\317\346\367\236\200\275\370\277\321\322t\355b\216\17V.\230M\242\321\16\ri`\231dn\247\220\300\260\34\252\177W\"\371\327\302\r#\316P\270\363=\277\ff\325\336\244\220K\371\360\334\314$2\206\2238\36\330\220\265\212\346\370w\23S\363\310\22wRM\3237T_\225\256n\310\305`,\330\36\246\23\313\25{"..., iov_len=175}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 175
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 sendmsg: 175 of 175\n", 63) = 63
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic done writing\n", 61) = 61
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 event timer del: 12: 3606530\n", 72) = 72
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 event timer add: 12: 29:3546568\n", 75) = 75
epoll_wait(22, [{EPOLLIN, {u32=3834213856, u64=94308431132128}}], 512, 29) = 1
recvmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(56250), sin_addr=inet_addr("<ip>")}, msg_namelen=112->16, msg_iov=[{iov_base="I\360\336KP\203p\262\325\22\332C{\361,pm\331+\245\272\330\325\315u%\10\300\37\33\364\17\202\211\245P\314\324=u\257!\243", iov_len=65535}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 43
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 recvmsg: fd:12 n:43\n", 63) = 63
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic read handler\n", 61) = 61
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 http3 idle handler\n", 62) = 62
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic done reading\n", 61) = 61
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 post event 000055C5E4949180\n", 71) = 71
recvmsg(12, {msg_namelen=112}, 0)       = -1 EAGAIN (Resource temporarily unavailable)
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 delete posted event 000055C5E4949180\n", 80) = 80
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic write handler\n", 62) = 62
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic alarm fired\n", 60) = 60
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 quic done writing\n", 61) = 61
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 event timer del: 12: 3546568\n", 72) = 72
write(3, "2021/01/19 12:15:14 [debug] 19619#0: *3162 event timer add: 12: 59999:3606541\n", 78) = 78
epoll_wait(22, [{EPOLLIN|EPOLLOUT, {u32=3834215648, u64=94308431133920}}], 512, 5541) = 1

I would like to point out this (from other strace of nginx proccess):
12:56:05.431851 recvmsg(26, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
12:56:05.434142 recvmsg(26, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
12:56:05.435023 recvmsg(26, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
12:56:05.436736 recvmsg(26, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)
12:56:05.499619 recvmsg(26, {msg_namelen=112}, 0) = -1 EAGAIN (Resource temporarily unavailable)

lsof -> nginx 32673 nobody 26u IPv4 253272330 0t0 UDP <hostname>:https

Parts of server configuration (http3 section): (changes in keepalive and http3 won't fix issue)
server {
        listen <ip>:443 ssl default_server http2;
        listen <ip>:443 quic reuseport;
        add_header alt-svc 'h3-29=":443"; ma=86400';

This type of flooding does not block nginx server (other connection work well). I have an idea of quiche socket getting close too early in some cases (but I'm not sure)

I can reproduce this issue, and it's definitely a bug. I tracked it and found if ngx_lookup_udp_connection() could find an existed udp_connection and reuse it, then this bug would happen.

I can reproduce this issue, and it's definitely a bug. I tracked it and found if ngx_lookup_udp_connection() could find an existed udp_connection and reuse it, then this bug would happen.

Which curl version are you using? It fixed a similar issue weeks ago https://github.com/curl/curl/issues/6213

Which curl version are you using? It fixed a similar issue weeks ago https://github.com/curl/curl/issues/6213

Im using
curl 7.74.0-DEV (x86_64-pc-linux-gnu) libcurl/7.74.0-DEV BoringSSL zlib/1.2.11 brotli/1.0.7 zstd/1.4.3 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) nghttp2/1.39.2 quiche/0.6.0 Release-Date: [unreleased] Protocols: http https mqtt  Features: alt-svc AsynchDNS brotli HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Largefile libz NTLM NTLM_WB PSL SSL UnixSockets zstd
As I mentioned while opening issue I belive it is not case of curl because this problem is not reproducable by curling to https://cloudflare-quic.com/ . This issue is also possible to reproduce with browser.

Im using
curl 7.74.0-DEV (x86_64-pc-linux-gnu) libcurl/7.74.0-DEV BoringSSL zlib/1.2.11 brotli/1.0.7 zstd/1.4.3 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) nghttp2/1.39.2 quiche/0.6.0 Release-Date: [unreleased] Protocols: http https mqtt  Features: alt-svc AsynchDNS brotli HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Largefile libz NTLM NTLM_WB PSL SSL UnixSockets zstd
As I mentioned while opening issue I belive it is not case of curl because this problem is not reproducable by curling to https://cloudflare-quic.com/ . This issue is also possible to reproduce with browser.

Just to provide evidence it's not issue of curl here's screenshot of this issue replicated with Firefox. How you can achieve that: just refresh page several times to get request without any response

Just to provide evidence it's not issue of curl here's screenshot of this issue replicated with Firefox. How you can achieve that: just refresh page several times to get request without any response

@qjavax we recently updated our nginx patch. Can you try with latest? Thanks.

@qjavax we recently updated our nginx patch. Can you try with latest? Thanks.

@junhochoi yes I did rebuild my nginx + quiche yesterday with commit: 1e439773dcb96c64071d6b85496bd33cc306aad7 .
Unfortunately problem didn't change. I also tried your docker file with nginx+quiche
docker run -d -v $(pwd):/usr/local/nginx/html -p <IP_ADDRESS>:8443:8443/udp -p <IP_ADDRESS>:8443:8443/tcp -p <IP_ADDRESS>:8080:8080/tcp -it ef6cc77f47b0
for x in {1..1000}; do echo " ===> $x"; curl3 -k -vvI --http3 https://<IP_ADDRESS>:8443; done

You can also replicate this issue like that.

@junhochoi yes I did rebuild my nginx + quiche yesterday with commit: 1e439773dcb96c64071d6b85496bd33cc306aad7 .
Unfortunately problem didn't change. I also tried your docker file with nginx+quiche
docker run -d -v $(pwd):/usr/local/nginx/html -p <IP_ADDRESS>:8443:8443/udp -p <IP_ADDRESS>:8443:8443/tcp -p <IP_ADDRESS>:8080:8080/tcp -it ef6cc77f47b0
for x in {1..1000}; do echo " ===> $x"; curl3 -k -vvI --http3 https://<IP_ADDRESS>:8443; done

You can also replicate this issue like that.

Hi, i got focused too much on nginx side of this issue. But after rebuilding nginx AND curl with newest quiche 0.7.0 this issue do not occur anymore so I'm closing this issue.
Thank you for your time.


chore(master): release 1.9.2

:robot: I have created a release beep boop
1.9.2 (2024-07-31)
Bug Fixes

correct messageEvent.ts regex (8a97383)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BingusBoingus-Developer-Team/BingusBoingus/releases/tag/v1.9.2 :sunflower:


Investigate OIS compatibility

See: https://github.com/api3dao/airnode/issues/1422#issuecomment-1239332221

Another thing. Since OIS validation is enforced up to the patch, users should use a pinned version on the OIS package. This will ensure compatibility. E.g. user installs:

"@api3/airnode-node": "0.7.5", which internally depends on "<EMAIL_ADDRESS>"@api3/ois": "^1.1.2"

If the OIS dependency is not pinned in airnode-node it will cause validation errors in that package (because it will use a common 1.1.2 dependency). If it is pinned, there will be two versions installed but the airnode-node package will be operational.
This needs to be mentioned in the docs.


Update supported languages

Thank you @jazzzz! I tested this on the latest Mattermost version and didn't noticesyntax highlighting for the two languages you added, stylus and text.
Do you see syntax highlighting for these languages on your Mattermost app?
```stylus
body {
  font: 14px/1.5 Helvetica, arial, sans-serif;
  #logo {
    border-radius: 5px;
  }
}
```

and
```text
body {
  font: 14px/1.5 Helvetica, arial, sans-serif;
  #logo {
    border-radius: 5px;
  }
}
```

both give

I tested this on the latest Mattermost version and didn't noticesyntax highlighting for the two languages you added, stylus and text.

It's from the list in constants.jsx

Thanks @jazzzz! You're correct, both are listed on the file you shared 👍


Configuration path to shellcheck is not stored properly

Hello,
first of all - thank you for the kick off this project. ShellCheck is very useful tool and this plugin helps a lot - especially for beginners...
Whenever I open a new project, I get an error message window describing shellcheck path is not filled (through intellij idea event log).
Could you please check the code for storing the configuration path?
--
IDEA 2017.3, ShellCheck plugin 0.1

I was trying to reproduce it and failed.
Plugin configuration is stored per project and by default it is not enabled in new project, so I dont know how you do it.
Please try to collect details steps, so I could find fix or alternatively propose PR.

That was my note. The configuration is stored per project. I guess you don't need to specify shellcheck path for every project. It should be on IDE level.

it makes sense, I would be open for any PR to address this issue, if I find time I would try to get it done, but can promise that it will happen in near future.


Use external libraries within conty

I am trying to use a 32bit application which requires one of its libraries pasted into /usr/lib, but as conty uses its own libraries, this makes the application unusable (conty does not have this lib). How can I tell conty to access this library, alongside its own, or how can I add this library to conty?

You can specify the path to your library (or libraries) using the LD_LIBRARY_PATH env variable. Let's say you put a library into /home/user/libs, in that case run Conty like this:
./conty.sh env LD_LIBRARY_PATH="/home/user/libs" ./application_binary

or
export LD_LIBRARY_PATH="/home/user/libs"
./conty.sh ./application_binary


Clean up handling of Merkle proof queries

Is your feature request related to a problem? Please describe.
Currently, our Merkle proof queries are a mess. We currently have at least two different ways of returning Merkle proofs, with two different root hashes. The situation is as follows.
First, ideally our app hash would be the root hash of the JMT.  Unfortunately this is not possible, because our IBC counterparty chains, who use the Cosmos SDK, require that IBC proofs have two nontrivial ICS23 proofs, an artefact of the SDK's use of an IBC-specific IAVL subtree (specifically, ibc-go requires that the tree has a stable prefix, something that isn't achievable in a sparsed prehashed tree like the JMT).  To achieve interoperability, we introduce a stable prefix by making our app hash be a hash of the JMT root hash, so we can treat it as a depth-1 Merkle tree, and supply a chain of two proofs.  There are thus two different Merkle roots at play: the "real" JMT root, and the "workaround" apphash.  This was introduced in https://github.com/penumbra-zone/penumbra/pull/1189
Second, there are two kinds of Merkle proofs in use, Tendermint Merkle proofs and ICS23 Merkle proofs. These formats are similar but not identical.  ABCI queries from Tendermint need to be responded to with Tendermint Merkle proofs.  This way, a relayer which queries Tendermint's RPC can have their request forwarded to the ABCI app, and get a Tendermint Merkle proof back, which they then immediately convert to an ICS23 Merkle proof (🫡).
Describe the solution you'd like
As in #1586 #1588, ideally the storage2 crate is general-purpose, and independent of Penumbra.  So the get_with_proof method in storage2::State should return an ICS23 proof up to the JMT root.
We can handle the Penumbra-specific interop workaround with a new extension trait in the chain crate, providing methods like get_with_proof_to_apphash or get_with_proof_to_apphash_tendermint returning ICS23 or Tendermint proofs. In the case of ICS23, it should return an ibc::core::ics23_commitment::merkle::MerkleProof. In the case of tendermint, it should return a tendermint::merkle::proof::Proof.

Confirmed during weekly wrap-up today that this work is indeed complete.


bevy 0.14

Reopening using a different branch:
I updated bevy to 0.14 and generally relaxed the specific versions requested for various deps in Cargo.toml. I also replaced the physics engine with avian3d, which is the new branding for xpbd. When I run the basic example, there is an error about bevy_render not supporting Tga. If this can be fixed, at least this library has an otherwise straightforward upgrade path.

bumped deps up to 14.0


Repo Excluded from HacktoberFest!

There is a commitment — which is a compulsary requirement — for contributors & maintainers to follow a set of guidelines which is listed here.
This repository does not fall into the guidelines that were initially set by DigitalOcean. More specifically, this statement: "PR/MRs should be useful to maintainers. Repos that encourage simplistic PR/MRs (like adding a name or profile to a list or arbitrarily curating content) will be excluded from Hacktoberfest."
^ If you would like me to be even more specific - it's these 3 words: arbitrarily curating content
This repository was created for the sole purpose of allowing people to contribute pull requests (PRs) with no real purpose other than to be in the "minimum 4 pull requests (PRs)" window to be eligible for a T-Shirt from DigitalOcean.
This 1 week (7 days) of waiting time was implemented so that DigitalOcean can review more than 500K pull requests to ensure that each pull request (PR) meets the guidelines set. Lots of human moderators were chosen by DigitalOcean to take care of this.
If a particular repository was never reported to DigitalOcean where the sole purpose was to defeat the system - it's always — 50% to 75% — possible for your pull requests (PRs) to be flagged and have it not counted towards your contributions for Hacktoberfest 2022.
As always, humans are humans - and not robots. This means that it's sometimes possible for these pull requests (PRs) to slip through DigitalOcean's reviews and have your pull requests (PRs) counted towards your contributions for Hacktoberfest 2022.
Please be aware that if you made multiple repositories which were all excluded - it's better to be safe than sorry to say that it's always possible for DigitalOcean to blacklist your GitHub / GitLab account where any pull request (PR) made by other contributors to your repositories will not have their contributions counted towards Hacktoberfest 2022.
DigitalOcean is always looking to implement more safeguarding measures to prevent unfair advantage towards other people and every October in each year, those rules tend to expand.


Spellcheck

Description of the change:
I added some words that were showing up and don't need to be spellchecked
Reason for the change:
These are names of companies or people
@ksigler7

Hello @mbernier,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Laravel 4.2?

Is there a way to use it with Laravel 4.2?

I agree with this. Looking through your code I see no dependencies on Laravel 5 besides some service provider methods. Backwards compatibility can be added in very easily.
Please don't forget about the massive Laravel 4 user base!

I will look into the differences between Laravel 4 and Laravel 5. There will probably need to be some changes around how packages, commands, and configs are registered to backwards port to Laravel 4. However, it should be doable.
Backwards compatibility is always nice. Honestly I did not mean to leave out Laravel 4, this was just written around a Laravel 5 project; and just was never tested/ported to Laravel 4.

Commands are registered the same, and the only large change from Laravel 4 is that packages now use a typical config separator instead of the package specific one in L4 for example:
Config::get('package::config');

You can take a look at a service provider I've made for both L4/L5 compatibility here:
https://github.com/stevebauman/inventory/blob/master/src/Stevebauman/Inventory/InventoryServiceProvider.php
All you really need to do is assign a configuration separator and retrieve all your configuration values using it.

Good stuff. I should be able to get that implemented this week. I might need to create a branch for someone to test with a L4 instance. I don't have one at the moment, but might be able to quickly set one up depending on time.
Thanks!

1.0 Fixes this and cleans up some up some other stuff. Thanks for your input and contribution!

Awesome!

Hi,
I can't install the package since it requires illuminate/support: 5.0.* and it comes with Laravel 5. Can you fix that please?

This is fixed in v1.1 I just pushed.
This issue is closed as it pertains to an older version of Potion. If there is any more problems around Laravel compatibility, please open a new issue.
Thanks.


Add a whitelist

reddit.app.link
app.adjust.com
linksynergy.com

We have added the following domains


Can not login with GroupMe

When ever I try to login using the channel "group me", I just can not. A link to authenticate is not provided.

I was able to reproduce this, thanks for the heads up.


Robot moves randomly using "velocity controller.launch"

Hello,
I roslaunched the velocity controller.launch file. I expected that the robot will spawn and remain static until I publish some commands in one of the topics. After this, I wanted to do something like driving the robot with a keyboard.
The topics seem to be fine and no error message is shown but the robot wheels appear to move randomly. I'm not sure if something(no idea what) went wrong or if this is the normal behavior. In both cases, I'd appreciate some help in order to make an initially static robot.
I'm working with ROS Kinetic and Gazebo 7.0 in Ubuntu 16.04LTS.
If it helps, here is the output in my terminal...
... logging to /home/alvaro/.ros/log/9f70ff16-9fb9-11e8-b83d-e4f89c846601/roslaunch-alvaro-Lenovo-B50-80-2717.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
started roslaunch server http://alvaro-Lenovo-B50-80:43107/

SUMMARY
========
PARAMETERS
 * /open_base/back_joint_velocity_controller/joint: back_rim_joint
 * /open_base/back_joint_velocity_controller/pid/d: 0.0
 * /open_base/back_joint_velocity_controller/pid/i: 0.0
 * /open_base/back_joint_velocity_controller/pid/p: 0.001
 * /open_base/back_joint_velocity_controller/type: effort_controller...
 * /open_base/joint_state_controller/publish_rate: 100
 * /open_base/joint_state_controller/type: joint_state_contr...
 * /open_base/left_joint_velocity_controller/joint: left_rim_joint
 * /open_base/left_joint_velocity_controller/pid/d: 0.0
 * /open_base/left_joint_velocity_controller/pid/i: 0.0
 * /open_base/left_joint_velocity_controller/pid/p: 0.001
 * /open_base/left_joint_velocity_controller/type: effort_controller...
 * /open_base/parameter/control/I: 0.0005
 * /open_base/parameter/control/P: 5.0
 * /open_base/parameter/initial/theta: 0.0
 * /open_base/parameter/initial/x: 0.0
 * /open_base/parameter/initial/y: 0.0
 * /open_base/parameter/max/omega: 50.0
 * /open_base/parameter/max/v: 1.0
 * /open_base/parameter/stop/angle: 0.10471975512
 * /open_base/parameter/stop/distance: 0.001
 * /open_base/parameter/wheel/radius: 0.01905
 * /open_base/right_joint_velocity_controller/joint: right_rim_joint
 * /open_base/right_joint_velocity_controller/pid/d: 0.0
 * /open_base/right_joint_velocity_controller/pid/i: 0.0
 * /open_base/right_joint_velocity_controller/pid/p: 0.001
 * /open_base/right_joint_velocity_controller/type: effort_controller...
 * /open_base/robot_description: <?xml version="1....
 * /open_base/robot_state_publisher/publish_frequency: 30.0
 * /rosdistro: kinetic
 * /rosversion: 1.12.13
 * /use_sim_time: True

NODES
  /open_base/
    controller_spawner (controller_manager/spawner)
    kinematics (open_base/open_base_kinematics)
    main (open_base/open_base_main)
    odometry (open_base/open_base_odometry)
    open_base_spawner (gazebo_ros/spawn_model)
    robot_state_publisher (robot_state_publisher/robot_state_publisher)
  /
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)
  /open_base/sensor/
    encoder (open_base/open_base_sensor_encoder)

auto-starting new master
process[master]: started with pid [2731]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 9f70ff16-9fb9-11e8-b83d-e4f89c846601
process[rosout-1]: started with pid [2744]
started core service [/rosout]
process[gazebo-2]: started with pid [2747]
process[gazebo_gui-3]: started with pid [2752]
process[open_base/open_base_spawner-4]: started with pid [2757]
process[open_base/robot_state_publisher-5]: started with pid [2758]
process[open_base/controller_spawner-6]: started with pid [2763]
process[open_base/odometry-7]: started with pid [2765]
process[open_base/kinematics-8]: started with pid [2771]
[INFO] [1534248025.070493, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller
process[open_base/sensor/encoder-9]: started with pid [2832]
process[open_base/main-10]: started with pid [2841]
[ INFO] [1534248026.020910859]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1534248026.021266355]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1534248026.022992856]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1534248026.023358064]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
Unhandled exception in thread started by
sys.excepthook is missing
lost sys.stderr
[open_base/open_base_spawner-4] process has finished cleanly
log file: /home/alvaro/.ros/log/9f70ff16-9fb9-11e8-b83d-e4f89c846601/open_base-open_base_spawner-4*.log
[ INFO] [1534248036.197523806, 0.021000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1534248036.218097102, 0.027000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1534248036.349280373, 0.072000000]: Physics dynamic reconfigure ready.
[ INFO] [1534248036.466072552, 0.109000000]: Physics dynamic reconfigure ready.

...and the created topics.
 Not sure if this is related to the main problem but it can be a clue to somebody.
Thanks in advance!!!

Sorry for not answering before, I had no time in the last couple of days.
The wheels moving randomly happens with some controllers when they output an effort value that is below a certain threshold. I don't remember the exact details, but I think it shouldn't be happening.
In the last tests I made, I received some error messages regarding the controllers, but haven't looked at them. Although you wrote you got no error messages, it could be related.
I was trying to make the robot colored, but I don't remember right now in which cases it wasn't working. Another thing that I'll have to take a look.
Next time I have some time, I'll compare this project with another project I made that used this package, with some modifications, to see if I can make it work again. The other one I'm pretty sure should be working.

First of all, don't be sorry for no answering in some hours! I didn't expect an instant response and it wasn't necessary.
I will take a look on the next days and post the solution to my problem if I find it. The color isn't a problem for me, I just mentioned it as a curios fact.
Thanks for the feedback!!

No problem, it's just that I like to err on the side of politeness...

Fixed in 7f7844114b91f451724ca97ff5a3ec2442034f34! The problem is that the joints had a name in the description and a different name in the controller.
I also added some files in the script folder to make debugging easier. Just cd to that folder and source the *.sh files.

Thank you very much for the update! I have tested and it works fine for me.
And thanks also for the *.sh files! They surely will make things easier for begineers (like me).
I also was thinking that the problem was in the joints names. What I made was changing the naming in rim.urdf.xacro to be equal with description.urdf. I didn't notice the joint_velocity.yaml, but it also has the same naming. The robot appear to be static with this changes but, as i didn't have time to test the movement, I didn't post anything in this issue.
So, in brief, I have the same joint naming in rim.urdf.xacro, description.urdf and joint_velocity.yaml and you keep the different naming in description.urdf. Is the description.urdf file irrelevant for the control?
As I said your code works perfectly. I only ask to understand the whole thing.
Thanks in advance!

Thank you very much for the update! I have tested and it works fine for me.
And thanks also for the *.sh files! They surely will make things easier for begineers (like me).
I also was thinking that the problem was in the joints names. What I made was changing the naming in rim.urdf.xacro to be equal with description.urdf. I didn't notice the joint_velocity.yaml, but it also has the same naming. The robot appear to be static with this changes but, as i didn't have time to test the movement, I didn't post anything in this issue.
So, in brief, I have the same joint naming in rim.urdf.xacro, description.urdf and joint_velocity.yaml and you keep the different naming in description.urdf. Is the description.urdf file irrelevant for the control?
As I said your code works perfectly. I only ask to understand the whole thing.
Thanks in advance!

Hi～Maybe I meet the same problem with you， the car rotates clockwise along the yaw axis. Could you tell me your detailed solution? Thank you very much.

Hey
I contact you a months ago to know how to move the robot with the
keyboard.
During the project I was able to find a solution to move the robot with a
keyboard and a PS3 joystick , if you want I can send you the project.
Thank for the support.
Na(o) quarta, 15/08/2018, 11:49, Guilherme Alan Ritter <
<EMAIL_ADDRESS>escreveu:

Sorry for not answering before, I had no time in the last couple of days.
The wheels moving randomly happens with some controllers when they output
an effort value that is below a certain threshold. I don't remember the
exact details, but I think it shouldn't be happening.
In the last tests I made, I received some error messages regarding the
controllers, but haven't looked at them. Although you wrote you got no
error messages, it could be related.
I was trying to make the robot colored, but I don't remember right now in
which cases it wasn't working. Another thing that I'll have to take a look.
Next time I have some time, I'll compare this project with another project
I made that used this package, with some modifications, to see if I can
make it work again. The other one I'm pretty sure should be working.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GuiRitter/OpenBase/issues/6#issuecomment-413162296,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AiQ3L3U4SzmYdsB6DVUzymob4FOAkPxHks5uQ_zXgaJpZM4V8XTZ
.

Hey I contact you a months ago to know how to move the robot with the keyboard. During the project I was able to find a solution to move the robot with a keyboard and a PS3 joystick , if you want I can send you the project. Thank for the support. Na(o) quarta, 15/08/2018, 11:49, Guilherme Alan Ritter <<EMAIL_ADDRESS>escreveu:
…
Sorry for not answering before, I had no time in the last couple of days. The wheels moving randomly happens with some controllers when they output an effort value that is below a certain threshold. I don't remember the exact details, but I think it shouldn't be happening. In the last tests I made, I received some error messages regarding the controllers, but haven't looked at them. Although you wrote you got no error messages, it could be related. I was trying to make the robot colored, but I don't remember right now in which cases it wasn't working. Another thing that I'll have to take a look. Next time I have some time, I'll compare this project with another project I made that used this package, with some modifications, to see if I can make it work again. The other one I'm pretty sure should be working. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AiQ3L3U4SzmYdsB6DVUzymob4FOAkPxHks5uQ_zXgaJpZM4V8XTZ .

I'm glad to hear you got it working!
I'm not working with keyboard or joypad control right now, but maybe it would be a good idea to make a repository with the solutions you found. You'll be able to help more people that way 😉.


Question: Is is possible to read data from swift with this library?

The example on the README is just for writing data to swift.  Is reading supported?

@snowch Yes it is possible.

@Nosfe are you able to share any example code, preferably python?

@snowch
Using a Jupyter notebook:
from pyspark import SparkConf, SparkContext
conf = (
SparkConf()
.set("spark.hadoop.fs.swift2d.impl", "com.ibm.stocator.fs.ObjectStoreFileSystem")
.set("spark.hadoop.fs.swift2d.service.sahara.username","username")
.set("spark.hadoop.fs.swift2d.service.sahara.password","password")
.set("spark.hadoop.fs.swift2d.service.sahara.tenant","tenant")
.set("spark.hadoop.fs.swift2d.service.sahara.auth.url","http://swift:5000/v2.0/tokens/")
.set("spark.hadoop.fs.swift2d.service.sahara.auth.method","keystone")
)
sc.stop()
sc=SparkContext(conf=conf)
words = sc.textFile("swift2d://gutenberg.sahara/gutenberg_big_2x.txt")
num_lines = words.count()
print("the number of lines in file", num_lines)

Thanks @Nosfe