TaskCancelledException should be wrapped in a CosmosException for queries

Queries fail with the exception TaskCanceledException and no further diagnostic information can be obtained for that.
Wrapping the TaskCanceledException it in a CosmosException with a proper error description will be helpful
<GetEventsWorkItem_48538255> failed. Latency:10016.8202ms, RUs:0, ActivityId:00000000-0000-0000-0000-000000000000, Test:, Exception:System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.ClientExtensions.<GetAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GatewayAddressCache.<GetServerAddressesViaGatewayAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GatewayAddressCache.<GetAddressesForRangeIdAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Common.AsyncCache`2.<GetAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Routing.GatewayAddressCache.<TryGetAddressesAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.AddressResolver.<TryResolveServerPartitionAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.AddressResolver.<ResolveAddressesAndIdentityAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.AddressResolver.<ResolveAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.AddressSelector.<ResolveAddressesAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.AddressSelector.<ResolveAllUriAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreReader.<ReadMultipleReplicasInternalAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreReader.<ReadMultipleReplicaAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.QuorumReader.<ReadQuorumAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.QuorumReader.<ReadStrongAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.ReplicatedResourceClient.<>c__DisplayClass27_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.RequestRetryUtility.<ProcessRequestAsync>d__2`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)
at Microsoft.Azure.Documents.RequestRetryUtility.<ProcessRequestAsync>d__2`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreClient.<ProcessMessageAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.ServerStoreModel.<ProcessMessageAsync>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.TransportHandler.<ProcessMessageAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.TransportHandler.<SendAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.RequestHandler.<SendAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.<ExecuteHttpRequestAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.<SendAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.RequestHandler.<SendAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.<SendAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.<SendAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.CosmosQueryClientCore.<ExecuteItemQueryAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducer.<BufferMoreDocumentsAsync>d__66.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducer.<BufferMoreIfEmptyAsync>d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducer.<TryMoveNextPageAsync>d__68.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducerTree.<TryMoveNextPageImplementationAsync>d__49.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducerTree.<ExecuteWithSplitProofingAsync>d__52.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.ItemProducers.ItemProducerTree.<TryMoveNextPageAsync>d__45.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.Parallel.CosmosParallelItemQueryExecutionContext.<DrainAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.PipelinedDocumentQueryExecutionContext.<ExecuteNextAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.LazyCosmosQueryExecutionContext.<ExecuteNextAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.CosmosQueryExecutionContextWithNameCacheStaleRetry.<ExecuteNextAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Query.Core.ExecutionContext.CatchAllCosmosQueryExecutionContext.<ExecuteNextAsync>d__6.MoveNext()

This should be fixed in PR: https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1788 which was released in 3.13.0


remove go version v1.52.0 and keep only v1.52.3

As a reactive from #32205, we need to remove the 52.0 release and only keep v1.52.3 which is the latest patch version for that minor release

@jtattermusch @drfloob, PTAL when you can..

Friendly ping, :) @markdroth @jtattermusch


License for checksum functions?

Hi, thanks for this project. To me, this is the best WSL-DistroLauncher fork. Great job.
My question is: what is the license of the Checksum Verify functions? I'd like to add them to my fork, but there is no license or copyright info.
Thanks!

I wrote it myself so it's MIT.
It's based upon the windows crypto api documentation and examples from docs.microsoft.com and some stackoverflow for things like string conversions...
docs.microsoft.com used MD5 I rewrote it for sha256.
The md5 version is here: https://docs.microsoft.com/en-us/windows/win32/seccrypto/example-c-program--creating-an-md-5-hash-from-file-content


Correct Way to Implement Drawer

I am having a  Launch Screen which redirects to Drawer by calling Actions.drawer if Login Credential are found.
Home Screen is appearing but with a back button instead of Drawer Button, please help!
const scenes = RNRF.Actions.create(
    <Scene key="root">
      <Scene key="launch" component={LaunchScreen} initial={true} hideNavBar={true} title="Launch"/>
      <Scene key="loginScreen"  component={LoginScreen} hideNavBar={true} title="Login Screen"/>
      <Scene key="otpScreen" component={OTPScreen} hideNavBar={true} title="Login Screen" />
      <Scene key="drawer" component={SideDrawer}>
        <Scene key="main">
          <Scene key="home" component={Home} type="replace"/>
          <Scene key="home1" component={Home1} type="replace"/>
        </Scene>
      </Scene>
    </Scene>
);

Add hideNavBar="true" to your root scene, and them remove it everywhere else.  You'll still get a navbar on your main scene which should contain the drawer.

 What is the proper way to set up the drawer with this configuration?
// scenes
<Scene key="Root">
  <Scene key="Auth">
    <Scene
      key="Login"
      component={Login}
      title="Login" />
  </Scene>

  <Scene key="Main">
    <Scene
      title="Dashboard"
      key="Dashboard"
      component={Dashboard}
      initial={true}>

    {/* ... more scenes */}
  </Scene>
</Scene>

// drawer

class MainDrawer extends React.Component {
  static contextTypes = {
    drawer: PropTypes.object,
  };

  constructor (props) {
    super(props);

    this.state = {
      showDrawer: false,
    };
  }

  toggle () {
    const {drawer} = this.context;
    const showDrawer = !this.state.showDrawer;

    if (showDrawer) {
      drawer.open();
    } else {
      drawer.close();
    }

    this.setState({showDrawer});
  }

  renderNav () {
    return (
      <View>
        {/* ... menu items */}
      </View>
    )
  }

  render () {
    const children = this.props.navigationState.children;

    return (
      <Drawer
        ref={(ref) => this.drawer = ref}
        type="displace"
        content={this.renderNav()}
        tapToClose={true}
        openDrawerOffset={0.2}
        panCloseMask={0.2}
        negotiatePan={true}
        tweenHandler={(ratio) => ({
          main: { opacity: Math.max(0.54,1 - ratio) }
        })}>
        <DefaultRenderer navigationState={children[0]} />
      </Drawer>
    );
  }
}

Following the example, I tried this:
// scenes
<Scene key="Root">
  <Scene key="Auth">
    <Scene
      key="Login"
      component={Login}
      title="Login" />
  </Scene>

  <Scene key="Main" component={MainDrawer}>
    <Scene
      title="Dashboard"
      key="Dashboard"
      component={Dashboard}
      initial={true}>

    {/* ... more scenes */}
  </Scene>
</Scene>

But this doesn't work. I don't get the drawer icon, and if I try to create my own drawer icon manually using the rightTitle and onRight props, I can't access the drawer from the onRight method's context. For example, this also doesn't work:
    <Scene
      component={Drawer}
      rightTitle={
        <Icon name="navicon" size={26} color="#fff" />
      }
      onRight={() => {
        console.log('context', this.context); // context is undefined
      }}
      title="Dashboard"
      key="Main">

      {/* ... scenes */}
    </Scene>

I'm using react-native 0.22.

I had prepared an example here.

@efkan Great work!
Actually i don't like complexity of 'contextTypes', maybe it is possible to implement drawer without usage of context at all....
For example Actions.refresh({key:DRAWER_NAME, 'open':true}) could open drawer (Drawer renderer will open it when navigationState.open prop is changed) Maybe we could improve 'refresh' to allow 'switch' boolean values to implement switch, like passing function for values: Actions.refresh({key:DRAWER_NAME, open:value=>!value})

Thanks @aksonov ,
Thanks to you, I completed a month ago that example and I don't have enough time to think about it.
Yesterday I upgraded the my project. As you may guess, then some serious problems arose.
One of them is upgrading react-native-router-flux. It seems beautiful and it uses the original React-Native Navigator component. I think that is great. However I have to create new appropriate NavBars for Android and iOS.
Nontheless, I think that way is the correct.

@efkan You could still use v2. v3 seems more like experimental. I was wrong when thinking that when NavigationExperimental component became part of React Native it will be 'stable'.
If you choose to use v3, feel free to improve existing NavBar and submit PR.

getting error :
'props should be defined for stack'
while using sample:
https://github.com/efkan/rndrawer-implemented-rnrouter

@lynndylanhurley did you find any way to handle that kind of navigation on react-native-router-flux 3?
I'm working on something that in my opinion sounds really vanilla but it still seems too hard to achieve in this version: drawer on some main routes, no drawer in sub-routes.
I'm facing a lot of issues: un-needed sub-schemes, the title sometimes doesn't work, the back button is not rendered etc... I'd love to help but unfortunately I have no time :(
It worked perfectly on the previous version but sadly it seems to have a lot of problem now... I think I'm going to drop this router until it become more stable.
P.S.:
DefaultRenderer:
_renderHeader(/*NavigationSceneRendererProps*/ props) {
        return <NavBar
            {...props}
            getTitle={state => state.title}
        />;
    }

NavBar: this.props.getTitle can't be null here, am I right?
_renderTitle(childState: NavigationState, index:number) {
        const title = childState.renderTitle ?
          childState.renderTitle():this.props.getTitle ? this.props.getTitle(childState) : childState.title;

Use my way:     renderRightButton={() => <SmallAvata />}                                renderBackButton={()=> <Icon name={"nav-button"} size={16} color="#fff"/>}                                renderLeftButton={() =>  <Icon name={"nav-button"} size={16} color="#fff"/>}                                hideBackImage={true}
use this in Scene options.


Add atom feed to forums

Icon is from here: http://www.mozilla.org/foundation/feed-icon-guidelines/

Any thoughts on this?  Happy to change it if you have some concerns before pulling

@jgadbois my only concern in general is it'd be nice if there was a test to go along with it / verify we don't break this feature down the road.  Can you put one of those together?

Just an integration test I'm guessing?

Yeah, and it can be super simple as far as I care.  Just 'hey here's a forum/topic/post, and they totally show up in the rss feed when I hit the url.'

Ok, done

+1, I tested it and it both passes and merges cleanly.  @radar @parndt merge?  Thanks, you're great @jgadbois

I'm not sure Atom is a technology that is useful in a Forum.
Just kidding! This sounds great to me, with one caveat. It needs something in the readme that explains that it's there and that you can place an auto discovery tag in your <head> to make it magic.

Haha - had me nervous there!  Let me know if there are any other features you'd like help on.  I'll update the readme.

Hmm...actually.  How would this work - the atom feed is per forum, so it's only valid on a forum page.  Is the auto_discovery_link_tag method smart enough to know this or would there need to be some conditional logic in the head?
If the second, maybe we should add a helper method?

Yes, a helper sounds perfect to me!

It looks like since the engine has an isolated namespace , then helpers aren't available to the main application unless the helper is manually included in the app ApplicationController.  Is there a better solution, or should that just be part of the setup instructions?

We should surely be able to have something like:
forem.atom_auto_discovery_link_tag
@radar @knewter what is your feeling on a "forem" helper?

So I would suggest you just make the helper named auto_discovery_link_tag.  Then, if the main app mounts forem at /forem, they can call that helper method with forem.auto_discovery_link_tag

Seems crazy to override the real method name Rails provides..

hilariously I forgot about that.  Ignore the crazy person, move along :)

What if we just instructed them to put a yield(:forem_head) in their layout and then we did a content_for with the auto discover tag in the appropriate views.

I agree, it would be hard to find the correct files.  This approach might still be easier than opening up a helper to the main app.

I'd merge this request if you were to please add a helper named: forem.atom_auto_discovery_link_tag and document its usage in the readme.
Thanks, you're wonderful :)

Or, if you (or Monique) think that name is dumb then you could rename the helper to something clearer :)

How do I go about adding that method?  I can add a method to a helper, but I'm not sure how to make it accessible via forem.atom_auto_discovery_link_tag

@radar @parndt I don't know the answer to this.  Le help?  So close on this one...

Sorry, was up a mountain (with @parndt and ~60 other nerds).
You can't make it available through the forem method, as that's only supposed to be used as a routing proxy. Instead, just define it as forem_atom_auto_discovery_link_tag and use it where appropriate.

I don't know :( Perhaps @parndt knows? Maybe he's done it with Refinery?

You have to add the helper to the application's helper.. here's how Refinery does it:
https://github.com/resolve/refinerycms/blob/master/core/lib/refinery/core/engine.rb#L28

I added the forem auto discovery helper method.

Failures:

  1) topics viewing a topic should have an autodiscover link tag
     Failure/Error: assert page.has_selector?("link[title='ATOM']")
     MiniTest::Assertion:
       Failed assertion, no message given.
     # (eval):2:in `assert'
     # ./spec/requests/topics_spec.rb:153:in `block (3 levels) in <top (required)>'

Finished in 10.92 seconds
132 examples, 1 failure

Failed examples:

rspec ./spec/requests/topics_spec.rb:151 # topics viewing a topic should have an autodiscover link tag

Strange the spec passed for me

I'm running Ruby 1.9.3, what are you running?

Same.  I'm afk, but I'll double check tonight. I don't think I used minitest though.

@parndt This is passing for me

john@ubuntu:~/projects/github/forem$ bundle exec rspec spec/requests/
/home/john/.rbenv/versions/1.9.3-p0/lib/ruby/gems/1.9.1/gems/ffi-1.0.9/lib/ffi/platform.rb:27: Use RbConfig instead of obsolete and deprecated Config.
.............................................................................

Finished in 13.73 seconds
77 examples, 0 failures
john@ubuntu:~/projects/github/forem$ ruby -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]
john@ubuntu:~/projects/github/forem$ git branch
* atom_feed
  ignore_dummy
  issue_137
  issue_150
  issue_153
  master

tests pass for me as well...

alright, tests pass for me on 2 different boxes.  Also, @parndt is crazy because why is minitest in his error.  Merging :)

+1 I'm crazy

+1 @parndt is crazy.

haha, thanks for merging this guys.


Remove 1322 workaround

On request from https://github.com/mamba-org/micromamba-docker/issues/57#issuecomment-1024493120
Also closes #117
BTW, the deleted tests do pass, I just don't think we should be testing micromamba itself here.

thanks @maresb !


Add parameter to not create additional users on cloudstack-setup-databases

Description
When using the cloudstack-setup-databases command during the database setup process, some additional users are created. Since the standard procedure involves creating and configuring database users prior to the ACS setup, these extra users are not used. Moreover, the additional users created by cloudstack-setup-databases are granted excessive permissions, requiring operators to manually delete them.
This PR introduces a new optional parameter, --skip-users-auto-creation. By using this parameter, ACS will skip the automatic creation of these additional users.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] Build/CI
[ ] Test (unit or integration test code)

Feature/Enhancement Scale

[ ] Major
[x] Minor

Screenshots (if appropriate):
How Has This Been Tested?
After executing the cloudstack-setup-databases with the new flag, I checked the database users and, as expected, no new users were created. I then repeated the procedure without the new flag, and the extra users were created as usual.

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11676

@blueorangutan test

[SF] Trillian Build Failed (tid-11852)

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

[SF] Trillian Build Failed (tid-11858)

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11728

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11860)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 57547 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9969-t11860-kvm-ol8.zip
Smoke tests completed. 140 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_secure_vm_migration
Error
134.24
test_vm_life_cycle.py

test_01_secure_vm_migration
Error
134.24
test_vm_life_cycle.py


fixed #1293 'Takes framework has an XSLT injection vulnerability'

@yegor256 Please review.
Fix for https://github.com/yegor256/takes/issues/1293

Takes framework has an XSLT injection vulnerability

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 28min)

@PeJetuz thanks a lot!


Improved performance of parsing string (both escaped and in-place)

Extended benchmark for in-place serde deserialization and escaped strings

Great PR - thanks a lot, @ncpenke !


Add version tags for the interop server Docker images

Since it's been stated that some breaking changes are expected to be introduced for the 2019 competition, and can be seen in issues like #325, it would help to tag different versions of the interop server before pushing them to Docker Hub (such as build dates, semver-like versions, etc.). Currently only a latest tag is available.
This would help a lot in cleaning up noise in CI pipelines, where the version of the interop server can be pinned for a particular build. Unrelated changes won't have build failures pop up in the case that the latest tag gets pushed to again.

#340 will automatically add the date (month granularity) as a tag as part of deploy during merge into master.
We won't make any guarantees on how long we'll keep tags around. As of now, there appears to be no limit to number of tags on the hub, but I've seen that at around 100 it becomes problematic for tooling.

Version 2018.09 is available and should be stable/non-moving/non-updated as of tomorrow (October).
https://hub.docker.com/r/auvsisuas/interop-server/tags/

Great, thanks!


Update build deps

Quoting from the PR I made on the other repo: https://github.com/OSC/docker-sphinx/pull/1:
Update to Python3 because of the impending Python2 EOL. Also switch to using Pipenv to manage our dependencies because the ood-documentation repo uses it, and we need specific versions of a few things because of build errors and CVEs.
The 'lexer error' I reference happens because we are running sphinx-build with the -W flag which breaks the build if there is a warning. Newer versions of the JSON highlighter complain when attempting to highlight invalid JSON in https://github.com/OSC/ood-documentation/blob/develop/source/customization.rst, thus breaking the build. By using specific versions of pygmentize and sphinx we won't see that error.

Closing because I accidentally included irrelevant changes.


language support?

Do lightNER and AutoNER support other languages?
Chinese, French, Danish, spanish etc.
Thanks！

for now, we only have pre-trained models for english. may release models for other languages in the future.


reset doesn't change routes

It looks like the reset action doesn't actually change the routes, only the index. Isn't the intention to be able to change the routes?

Also think solution for reset in #2 was better. If I have a sack of cards and I want to reset it to one (not popping them) with current version of function this is not possible.

Yep that's my use case... I don't care what cards are on the stack, I have a new set of cards.

Can you guys take fix/route-reset branch for a spin and let me know if it looks good
npm install --save git://github.com/bakery/react-native-navigation-redux-helpers.git#fix/route-reset

Usage:
reset([{ key: '1'}], navigationKey)

Works fine for me, thanks! By the way index is not necessary (I don't pass it)

re:index - it's needed for compatibility with NavigationStateUtils - https://github.com/facebook/react-native/blob/37e41d2549b3e58f80a5cd075049ac1ddff06033/Libraries/NavigationExperimental/tests/NavigationStateUtils-test.js#L141

Sure it makes sense, I just mentioned that in my use case I'm not passing it

This should be fixed in 0.4.1. Feel free to reopen in case of questions/issues

Thanks @callmephilip. Works perfectly!


Blinking with OpenKneeboard

Hi, I get blinking (visible/invisible) when I open OpenKneeboard (https://github.com/fredemmott/OpenKneeboard), until it gets moved a few times, then it settles.
I do not know if that issue should go here or to OpenKneeboard.

Can you clarify "until it gets moved a few times, then it settles."? Any chance you could capture a video of the problem?

By moved I mean press recenter button while looking elsewhere, which positions kneeboard far, this way I can put the blinking out of sight. No chance for video during the next week.

I was actually able to reproduce the blinking with a test application that submits a quad layer (this is what OpenKneeboard does). However with another application (OpenXR Toolkit) no issue. I will look into the possible cause.

Fingers crossed, and thank you!

I believe I have a fix for this now.

This should be fixed by e300ef9c22f2903568bba2ff5231adfa76632c7d and available in the next release.

PimaxXR-0.2.1b.zip
Can you test with this experimental build and confirm the fix? Thanks.

On it.

Can you try without motion smoothing? Just to see if the knee board issue is solved?
Alternatively, you can add the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\PimaxXR
do_frame_begin, dword value 1

I have no idea what is up with the Pimax software variations from a machine to another. Somebody else is reporting the same issue as you. But for me it's working 100% well in DCS...

Added the registry fix, trying this version again.

No blinking in OpenKneeboard.

Awesome! Working on fixing some issues with motion smoothing, which caused the issue without the reg fix.
Thanks for validating OpenKneeboard!


Missing wrappers for iterators and generators

I want to write the following Python code
for item in collection:
  ...

like the following in Ruby with PyCall:
collection.each do |item|
  ...
end

Now PyCall defines each methods in PyCall::List and PyCall::Dict in specific ways.
It needs to be rewritten in more generic way.

One candidate is PyCall.enum(obj) to get an Enumerator object.
This is a concept implementation:
module PyCall
  module_function

  def enum(obj)
    gen = obj.__iter__
    Enumerator.new do |y|
      begin
        yield gen.__next__ while true
        obj
      rescue PyError, err
        # ignore StopIteration exception
        return obj if err.type.match?(LibPython::API::PyExc_StopIteration)
        raise
      end
    end
  end
end

Just one note: I needed to use generator using following function PyCall.builtins.next(generator)

Here is my version of the patch:
module PyCall
  module_function

  def enum(generator)
    Enumerator.new do |enum|
      begin
        loop do
          enum << PyCall.builtins.next(generator)
        end
      rescue PyError => error
        raise err unless error.type.to_s.match?("StopIteration")
      end
    end
  end
end

@allomov Could you please make a pull-request?


Update IoT Esp8266 sample readme with latest versions verified

This PR requires the approval of @wduraes, as he will cross-validate the information on the device as well.


WIP: Re-introduce crypto-conditions

How I would implement https://github.com/interledger/java-ilp-core/issues/101
This highlights a few issues that have been introduced into java-crypto-conditions OR suggests this is a bad approach:

The implementations of the different conditions have package private constructors for constructing a condition from just the fingerprint. This makes creating an instance from a codec.read() operation a challenge.

As a result of not being able to use org.interledger.cryptoconditions.PreimageSha256Condition (see above) it was necessary to create an alternate implementation. This may not be a bad thing to do but we should consider whether these are comparable to each other. I.e. Are two conditions equal where they have the same hash but one is an instance of org.interledger.cryptoconditions.InterledgerSha256Condition and the other org.interledger.cryptoconditions.PreimageSha256Condition

The codec context fails lookups if the provided class for a write operation implements an interface that extends another interface that was used to register the codec. i.e. Passing an instance of InterledgerSha256Condition fails because it implements SimpleCondition which extends Condition which is the class used to register the codec. The issue is in https://github.com/interledger/java-ilp-core/blob/development/src/main/java/org/interledger/codecs/CodecContext.java#L297

The implementations of the different conditions have package private constructors for constructing a condition from just the fingerprint. This makes creating an instance from a codec.read() operation a challenge.

Yes, I see the problem. I think the constructors of PreimageSha256Condition are improperly structured (read more about that below).
Overall, I definitely think we do not need a separate class type for InterledgerSha256Condition, but I am open to keeping InterledgerSha256Fulfillment. But even then, I'm not so sure.
From my perspective, this issue has two orthogonal concerns:

How do we encode an ILP Condition/Fulfillment in OER, while in the same application allow a crypto-condition variant to be encoded/decoded using DER.
How do we restrict the ILP Condition/Fulfillment to have a cost of 32, and a type of `PREIMAGE_SHA_256".

The first concern (encoding) is already solved by the Codec framework. First, in the general case, no developer should be directly creating a PreimageSha256 Condition. Instead, developers should be creating a Fulfillment and then generating the Condition from there. Two exceptions to this rule are in a Codec, or in a testing scenario (and in the testing scenario, creating a Fulfillment, and then a Condition, should suffice). In the Codec scenario, we do need to allow developers to deserialize from something (bytes, JSON, etc) into a Condition class, which means we need some sort of Constructor there to allow Codecs that don't live in the org.interledger.cryptoconditions package. More specifically, encoding/decoding of a Condition should be the same for either type, but we need a mechanism to allow a single piece of software to encode the same class (PreimageSha256Condition) using two different encodings: OER sometimes, and DER sometimes.
In this case, I think the CodecFactory solves for this: a developer simply needs to create two different codecs (one for OER, and one for DER), and use them where appropriate. Likewise if a third or fourth encoding were to be introduced (like JSON or XML, for example), then there would be additional Codec's constructed. In other words, it's already a requirement for the same application to be able to encode/decode the same classes using different encodings, and the Codec framework solves for this -- so, no need to create a special class-type just to satisfy the Codec.
Next, on the Fulfillment side, we need to allow developers to be able to create a special type of PreimageSha256Fulfillment called InterledgerSha256Fulfillment that restricts the preimage size and cost. Here, I'm on the fence. On the one hand, we could create just a factory class called InterledgerSha256Fulfillment, and it will simply generate a PreimageSha256Fulfillment while enforcing the constraints that it should have. The downside to this is that in various service interfaces, the type would still be PreimageSha256Fulfillment, and implementations would need to enforce the restrictions, which is not ideal.
So, this is why I'm open to a new type of Fulfillment, specifically for ILP, that lives in java-ilp-core. To that end, I propose the following:

Adjust the constructor for PrimageSha256Condition that takes a preimage to be package-private. Nobody should be constructing a condition from a preimage (instead, they should construct a Fulfillment and then get the corresponding Condition).
Adjust the constructor that takes a cost and fingerprint to be public. This will allow Codec developers to deserialize whatever encoding they're reading into an Instance of PreimageSha256Condition. In my mind, the PreimageSha256Condition and the InterledgerSha256Condition are both PreimageSha256 conditions -- only difference is the required cost, but that value will have come from a Fulfillment that was serialized to the encoding, so no need for a special class-type here -- it's all a PreimageSha256Condition.
Adjust the toString of PreimageSha256Fulfillment to use the class simpleName when emitting the toString.
Keep the class InterledgerSha256Fulfillment, and structure it like this (extending from PreimageSha256Fulfillment):

/**
 * An implementation of {@link Fulfillment} for a crypto-condition fulfillment of type
 * "PREIMAGE-SHA-256" based upon a preimage and the SHA-256 hash function.
 *
 * @see "https://datatracker.ietf.org/doc/draft-thomas-crypto-conditions/"
 */
public class InterledgerSha256Fulfillment extends PreimageSha256Fulfillment
        implements Fulfillment<InterledgerSha256Condition> {

    public static final int INTERLEDGER_FULFILLMENT_LENGTH = 32;

    /**
     * Constructs an instance of the fulfillment.
     *
     * @param preimage The preimage associated with the fulfillment.
     */
    public InterledgerSha256Fulfillment(final byte[] preimage) {
        super(preimage);

        if(preimage.length != INTERLEDGER_FULFILLMENT_LENGTH) {
            throw new IllegalArgumentException("Preimage must be exactly 32 bytes");
        }
    }
}

In this way, an interface could specify a InterledgerSha256Fulfillment or a PreimageSha256Fulfillment, and interfaces (like java-ilp-plugin)  could either type to PreimageSha256Fulfillment and accept both without issue, or be made generic, like this:
interface handleFulfillment<T extends PreimageSha256Fulfillment>{
  void handleFulfillment(T fulfillment);
}

In summary, this counter-proposal seems to solve for all three of the requirements:

Allow a Condition/Fulfillment to be encoded using OER (hash for a condition and preimage for a Fulfillment).
Force the InterledgerSha256Fulfillment to always be of type PREIMAGE-SHA-256.
Force the InterledgerSha256Fulfillment to always have a cost of 32.

Anything I'm missing?

If you're cool fixing the constructors then I am keen to drop both custom implementations. They are only there out of necessity, I'd prefer not to have them.
I don't think it's an issue throwing an error during the Interledger-specific OER encoding if the fulfillment length != 32 or the condition cost != 32.
One issue I failed to mention was that deprecating getFingerprint() is problematic. I think we should keep it in and simply return a copy of the array each time.

If you're cool fixing the constructors then I am keen to drop both custom implementations. They are only there out of necessity, I'd prefer not to have them.

Even better! I'll make the changes to java-ilp-core then and report back to this issue once that completed.

Even better! I'll make the changes to https://github.com/interledger/java-crypto-conditions then and report back here once that's completed.

Done, see https://github.com/interledger/java-crypto-conditions/pull/73
There are a few issues in this that make me think Crypto-Conditions could do with a refactor. Type checking based on the getType() is useless if the different types have different members that you want to access.
We should probably define an interface for each type so that alternative implementations can exist and still expose things like PreimageSha256Fulfillment.getPreimage().
 I'd much prefer we just do a safe copy of the array to maintain immutability. Until it's a perf problem we shouldn't prematurely optimize.
Finally, the convention within the ILP project has been to use Base64Url encoding with no padding. We need to be consistent in that too.

We should probably define an interface for each type so that alternative implementations can exist and still expose things like PreimageSha256Fulfillment.getPreimage().

Agree. I created https://github.com/interledger/java-crypto-conditions/issues/75 for tracking.

 I'd much prefer we just do a safe copy of the array to maintain immutability. Until it's a perf problem we shouldn't prematurely optimize.

I agree. Also added an issue to discuss perhaps just removing the Base64Url variant entirely. See: https://github.com/interledger/java-crypto-conditions/issues/76

From @adrianhopebailie:

Type checking based on the getType() is useless if the different types have different members that you want to access.

I'm not sure what you mean by the above statement - was this something you encountered in the codec in java-ilp-core, or something you're noticing in the java-crypto-conditions library itself?

Type checking based on the getType() is useless if the different types have different members that you want to access.

I'm not sure what you mean by the above statement - was this something you encountered in the codec in java-ilp-core, or something you're noticing in the java-crypto-conditions library itself?

Yes. When encoding a Condition/Fulfillment we must check that it is a PREIMAGE SHA-256 type condition (as only these are accepted). The correct way to do this would be to call Condition.getType() as this should return a consistent value for all implementations.
However, we also need access to members like  'PreimageSha256Fulfillment.getPreimage()` so we need to cast to a specific type anyway.
I think java-crypto-conditions/issues/75 will solve this


unqualified exec is not allowed in function 'compile_parser'

exec(code,exec_dict) in globals(), locals()

Unless I add in globals(), locals()  bits to the above line (line 585, pybam.py), I get the following error:

SyntaxError: unqualified exec is not allowed in function 'compile_parser' it contains a nested function with free variables

I found this workaround on the following discussion:
http://stackoverflow.com/questions/4484872/in-python-why-doesnt-exec-work-in-a-function-with-a-subfunction
I was using Python 2.7.5
--mahmut

Thank you very much for this uludag! It appears this is due to a bug in CPython up until 2.7.8 before being fixed in 2014: https://bugs.python.org/issue21591
However, I'm sure many people will want to use pybam on much old interpreters than 2.7.8, so i will modify the code with your fix :) Thank again uludag!


Fix light background in docusaurus night mode

Closes #7930
Tested with the manual toggle, and with setting prefers-color-scheme. Not sure if there's a cleaner way to do this, but it works.

Looks good! thanks @heyimalex 🥇

Will this change be active on next release? The live site isn't showing the changes from this PR.


Add some diagnostics.

Fixes #?
Context

Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under [a license compatible to (my library)
[x] Check " just can edit the ouner of all tecnologi ip maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[x] Recognize contributor in license of the ouner

mi sofwer o aplicaciones es x que 3seros manipulan y yo no doy ninguna seguro o que regresen el articulo ya manipulado x otras personas o agencias guvernamentales un articulo manipulado no aseguro que tenga uso correcto no garantiso mis productos ya manipulados ni pueden regresar se tienen que pagar y ustedes arreglarlo ya que ustedes permitieron la manipulacion de otras personas y no es garantia de que trabaje 100% .


Training on multiple GPUs in parallel

Hello, I am able to run your code, however I do not have access to a TPU.
Do you know if it is possible to perform training of the masker-corrector model on multiple GPUs instead of a single one? Thank you!

Hi, while i did all my experiments on a single GPU. The code is built on huggingface and should support distributed data parallel training automatically detecting multiple GPUs or by manually setting the --num_gpus X flag

Thank you, I will try that


RingBuffer exhausts when reading non-aligned chunks of data in bulk

Consider the following socket reader, analogous to an asynchronous codec:
let data = socket.recv(|buffer| {
  let len = buffer.len();
  if len < 13 {
    return (0, None)
  }

  (13, Some(buffer[0..13].to_vec()))
});

With the current implementation of RingBuffer, the buffer will exhaust without wrapping around back to the 0th index. Inside of RingBuffer::deque_many_with, we can see that the implementation will attempt to wrap around only if the read data size is aligned with the total capacity of the buffer:
pub fn dequeue_many_with<'b, R, F>(&'b mut self, f: F) -> (usize, R)
where
    F: FnOnce(&'b mut [T]) -> (usize, R),
{
    let capacity = self.capacity();
    let max_size = cmp::min(self.len(), capacity - self.read_at);
    let (size, result) = f(&mut self.storage[self.read_at..self.read_at + max_size]);
    assert!(size <= max_size);
    self.read_at = if capacity > 0 {
        (self.read_at + size) % capacity
    } else {
        0
    };
    self.length -= size;
    (size, result)
}

With a capacity of 256, after the 19th iteration we get to read_at = 247, but max_size is only 9 - meaning the read function only gets 9 bytes to read, returning 0 for its size, failing to adjust read_at and resulting in the buffer exhausting itself even though there is a full frame of usable data in the buffer.
Unfortunately we can't immediately solve this with losing the contiguous property of the buffer being passed to f, putting to onus of keeping track of full data frames on the user which quickly becomes unwieldy and inefficient when multiple sockets are used. I can think of two reasonable solutions:

Implement a bip buffer
Pass data to the user in at least one but up to two halves, each of which are contiguous. If the current data is wholely contiguous within the circular buffer, give the user (&buffer[start..end], None). If the data is split across the end of the buffer, give the user (&buffer[start..capacity], Some(&buffer[0..end])). This doesn't fully solve the problem, but it avoids the user having to reserve a buffer per-socket for reading data and it can instead be done per-call if required.

This is by design. The only recv guarantee is "if there's bytes in the buffer, it returns some". Not necessarily all. This is how IO works, std::io::Read works the same way FWIW.
You're supposed to pop the 9 bytes, keep them around, request more bytes, append them to the 9 you got.
Even if we changed smoltcp to actually guarantee "it can return all data in a single recv", you still need to handle half-frames in your code because a half frame might actually arrive on the wire due to TCP packet segmentation.


Clarify parameters in Gui constructor and run()

Description
As of today, the Gui constructor and run() method have a bunch of parameters and it's not really clear why those parameters are used in one, or the other.
I suspect we should have a clear rule such as: any parameter that might make sense when the server is stopped then run again (such as in the Notebook situation) definitively should be in the run() method. Otherwise, the constructor sounds like the right place (like the server to be used).
Acceptance Criteria

[ ] Come up with a

will be better having a Config section for GUI parameters so it is easier to configure it dynamic.
And better consistent.

@rohan011001 Is this what you are referring to? configure_gui

@FlorianJacta Yes exactly.
Why not pushing this method in the doc. It is easier to configure dynamicly and consistent.

Clarifying all the attributes and parameters of the GUI service, the run method, the GUI application, and the GuiSection should improve the user manual documentation. The "Configuration" pages could be more use-case driven.
https://github.com/Avaiga/taipy-doc/pull/940/#discussion_r1680560794


[New game]: Dot dash

PR Description 📜
Added a new game Dot_Dash
Fixes #4553

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @aditya-bhaumik ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@ishita-43 please review my pull request

@ishita-43 i have resolved the conflicts please review my pull request

@ishita-43 i have added the image in the asset folder

@ishita-43 i have resolved the conflicts and added the image

@kunjgit i have resolved the merge conflicts


Roccat Vulcan light only flickering!

Expected Behaviour
Light should work as expected
Actual Behaviour
light flickers very fast! Looks like it changes between the commands from aurora and the roccat swarm software very fast!
Reproduction steps
Active Vulcan API in Device Manager
Frequency
Every time!
Aurora Version:
beta 0.7.2
Previously an Issue?
Dont know. I just got my new keyboard

Please close the roccat swarm software when you use aurora.

thank you

vulkan is a keyboard not a graphics api in aurora?

vulkan != vulcan.  I always had the vulkan wrapper emabled in hopes it would allow ambient lighting in vulkan games

when i press exit on swarm it starts to flicker more than it does when the app is open

when i press exit on swarm it starts to flicker more than it does when the app is open


Is it possible to host the web ui in my local machine ?

I think it would be better to include a demo folder in the source code, and a script like npm run start-demo to run web application locally. Because people may have concerns of uploading sensitive project stats data.
I dug into the codebase and found my way of creating an 'index.html' file and call Statoscope.default(data) (yep without webpack).

Hi! Yep, In the near release, I plan to implement a webpack plugin to start Statoscope locally

Nice move 🙌. I am picturing something like webpack-bundle-analyzer that gernates a report html and open it automatically. Just my two cents.
Looking forward to it.

👍🏻

Solved in 3.2.0

@smelukov
the error is still present
class l {
        constructor(e) {
            this.readers = e.map(e=>{
                const t = new s(e);
                return t.eventProgress.on((e,{total: t, loaded: n, chunkSize: r})=>{
                    this.loadedBytes += r,
                    this.eventProgress.emit(this, {
                        total: this.totalBytes,
                        loaded: this.loadedBytes
                    })
                }
                ),
                t
            }
            ),
            this.totalBytes = e.reduce((e,t)=>e + t.size, 0),
            this.loadedBytes = 0,
            this.eventProgress = new o.a
        }

e is FileList so it doesn't have map property

@budarin are you about this issue?

Yes, I mixed up the issue :)


Create a Wallabag playbook

Add a fix for doctrine XML driver

Not needed anymore as I don't use wallabag anymore


Confusing error msg when file is in UTF-16

It took me some time to figure out why parsing failed for a file that was syntactically correct.

Error: 1:1: Expected struct

The first 2 bytes were FF FE, which means it was in UTF-16 encoding for some reason.
https://en.wikipedia.org/wiki/Byte_order_mark#UTF-16
I fixed it for my case by doing:
use encoding_rs_io::DecodeReaderBytes;

pub fn load_from_ron_file<T: DeserializeOwned>(path: &Path) -> Result<T> {
	Ok(ron::de::from_reader(DecodeReaderBytes::new(BufReader::new(File::open(path)?)))?)
}

But maybe ron-rs should give a better error? Or is it too high up the food chain (regarding decoding)?

Looks like it can be handled by user code. It belongs to how I/O is done more than parsing or anything, so seems largely out of scope for ron.


Project structure

In this milestone I have:

Created HTML and CSS basic structure.
Added leaderboard list storage.
Created a class for leaders with add and clear methods.
Create a function for HTML writing.

Hi @sntgopl Kindly add a descriptive readme to your pr, this is required for a review

Hi @sntgopl
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not have a descriptive readme, kindly use the microverse readme template
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification @prolajumokeoni.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Fixed a huge visual bug

Fixed a huge rendering problem. I'm including a screenshot to show you what exactly is fixed. They include:

Removal of two quote boxes. This means I removed one > from every single line.
Changing \[!Caution\] to [!Caution] because the former is definitely what was intended.

The diff view in GitHub isn't impressive. You might want to use a different tool like Meld to compare the changes and generate a better visual diff.

@skycommand thanks for fixing these issues.

Glad to be of help! 😊


Game crashes if you leave a world while a turn is primed

https://github.com/CodeF53/CardinalIceBoats/assets/37855219/5d4c6124-9dfe-4a3f-9810-746b777eebcb
-- Head --
Thread: Render thread
java.lang.NullPointerException: Cannot invoke "net.minecraft.client.network.ClientPlayerEntity.sendMessage(net.minecraft.text.Text, boolean)" because "player" is null
Stacktrace:
	at net.cardinalboats.Util.ClientChatLog(Util.java:44)
	at net.cardinalboats.TurnPriming.tick(TurnPriming.java:77)
	at net.fabricmc.fabric.api.client.event.lifecycle.v1.ClientTickEvents.lambda$static$2(ClientTickEvents.java:43)
	at net.minecraft.client.MinecraftClient.handler$zfb000$fabric-lifecycle-events-v1$onEndTick(MinecraftClient.java:5022)

Will be closed when an update containing the fix is pushed to modrinth

https://modrinth.com/mod/cardinalboats/version/1.4.0


Looking for information on identifier declared in file returns nothing

If you run hdevtools info schema/Main.hs mkDoc when mkDoc is defined in Main.hs you get a blank line as output!
Given that when you start reading a file you have no idea what is coming from where, this is confusing and it looks like hdevtools is broken, thankfully once you realise this is the failure mode in this case you can search the file for 'mkDoc ::' and (assuming the expression is typed) find the information you want

I just tested hdevtools info on it's own source and it worked. Is the repository you were seeing this open source? The symbol mkDoc sounds like being template haskell, maybe this is causing problems

Thanks for the response! No unfortunately it's not open source.  I'm not sure,  I'll find out + test on some other identifiers

So mcDoc is just
mkDoc :: T.Text -> Doc
mkDoc = textStrict

where hdevtools tells me textStrict is
textStrict :: T.Text -> Doc
    -- Defined in ‘Text.PrettyPrint.Leijen.Text’

Docs are here
I don't think its a template haskell thing, although having quickly read about it, it sounds like it might an alternative here.  We're doing some code gen, however it's just mucking around with strings and writing them to a file, probably because it's easier to debug stuff like that.  What tells you template haskell is in use?  Is it just {-# LANGUAGE TemplateHaskell #-}?
I've only got the following in schema/Main.hs:
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE RecordWildCards   #-}

Again this is behaviour I'm seeing in a vim plugin but replicating on the command line.
Btw looking at the debug output from info it's picking up the stack and cabal files in a way that looks right! despite running from a folder above.  The environment is the same when running from inside the folder aswell.
I've also found the same issue in a different file.
Ok... the issue is with private functions - I'll post the second file I found the issue in as it's pretty small.  I've anonomised it a bit but the following should exhibit the behaviour:
module Options
  ( Config(..)
  , withOptions
  ) where

import           Data.Monoid
import           Options.Applicative

newtype Config = Config
  { cOutputRoot :: String
  } deriving (Show, Eq)

optionsApplicative :: Parser Config
optionsApplicative = Config
  <$> strOption (long "output-root" <> metavar "DIR" <> help helpText)
  where helpText = "Output files into the source tree rooted at DIR"

optionsInfo :: ParserInfo Config
optionsInfo
  = info (helper <*> optionsApplicative)
         (fullDesc <> progDesc "blah code generator")

withOptions :: (Config -> IO ()) -> IO ()
withOptions go = execParser optionsInfo >>= go

So if you run hdevtools info Options.hs optionsInfo you'll see the issue.
However running info Options.hs withOptions works because it's exported, I think the key bit is the module exports.


Instead of 404 redirect to company home page

For home page and other urls which are not configured, it will be good if all those can be redirect to default website. Let me know if you need more information.

This is so simple, it doesn't even require a plugin. I'm fact, it's so simple I had to do a find ... -exec grep ... on my server to find why it works, because it doesn't even require editing the YOURLS config file. 😂
Create index.php at the root of your YOURLS install with this content:
<?php
// redirect to the main site
header('HTTP/1.1 302 Found');
header('Location: https://yourmain.site/');

Of course replace the Location with your main site URL.
If it doesn't work, make sure your web server is configured to look for index.php (it might only look for index.html or index.htm by default).
This works because the 404 you see isn't from YOURLS itself, but from your web server. If the link keyword YOURLS gets doesn't exist, it just redirects the user to the $YOURLS_SITE set in config.php, which doesn't exist unless you add an index page or reconfigure the web server to treat something else as one.

This is so simple, it doesn't even require a plugin. I'm fact, it's so simple I had to do a find ... -exec grep ... on my server to find why it works, because it doesn't even require editing the YOURLS config file. 😂
Create index.php at the root of your YOURLS install with this content:
<?php
// redirect to the main site
header('HTTP/1.1 302 Found');
header('Location: https://yourmain.site/');

Of course replace the Location with your main site URL.
If it doesn't work, make sure your web server is configured to look for index.php (it might only look for index.html or index.htm by default).
This works because the 404 you see isn't from YOURLS itself, but from your web server. If the link keyword YOURLS gets doesn't exist, it just redirects the user to the $YOURLS_SITE set in config.php, which doesn't exist unless you add an index page or reconfigure the web server to treat something else as one.

Just wanted to add that in my installation, the root directory already
contains an index.php file.  I don't remember if I put it there, or not,
but it looks like this:

That's still safe to have, I'm hoping.
If I didn't have a forward already in place, the code you showed would
probably have been a good alternative.
Thanks for the info.
On Wed, Jan 27, 2021 at 11:33 PM dgw<EMAIL_ADDRESS>wrote:

This is so simple, it doesn't even require a plugin. I'm fact, it's so
simple I had to do a find ... -exec grep ... on my server to find why it
works, because it doesn't even require editing the YOURLS config file. 😂
Create index.php at the root of your YOURLS install with this content:
, or
unsubscribe

.

Just wanted to add that in my installation, the root directory already
contains an index.php file.  I don't remember if I put it there, or not,
but it looks like this:

That's still safe to have, I'm hoping.
If I didn't have a forward already in place, the code you showed would
probably have been a good alternative.
Thanks for the info.
On Wed, Jan 27, 2021 at 11:33 PM dgw<EMAIL_ADDRESS>wrote:

This is so simple, it doesn't even require a plugin. I'm fact, it's so
simple I had to do a find ... -exec grep ... on my server to find why it
works, because it doesn't even require editing the YOURLS config file. 😂
Create index.php at the root of your YOURLS install with this content:
, or
unsubscribe

.

Use a plugin, see https://github.com/YOURLS/awesome-yourls

Use a plugin, see https://github.com/YOURLS/awesome-yourls


wasm version of zxing for web

Hello!
Thank you for this great package!
Would you plan to use wasm version of zxing for web?
May be this

Thanks for the link. Currently, our WASM support still has some issues with the video preview. (seems to be a bug with platform views?) and we didn't test much of it because of that.
We can definitely look into using the WASM version of the library, though.
I will mark this as a feature request.
Out of curiosity, do you know if this WASM version has better maintenance then the old ZXing JS version?
The JS version seems to have stopped feature development.

Yes, I can see the issue with the video preview. Actually, this is one only bug which I can not fix and be happy with my wasm compiled app.
That repository looks very fresh and popular. In my own belief, wasm much more perspective than js for web when we talking about software like zxing.
It could be, guys from zxing-js think same way and that is why their "Project in Maintenance Mode Only".


Youtube autoplay on desktop chrome

First, thanks for a nice library, much appreciated.  It appears that youtube videos now require two clicks to play on a desktop browser.  I know mobile safari prohibits this, but it was working previously on the desktop with chrome:  click once, bigpicture launches and the video begins playing.   I'm using
class="vid iframevid"
iframesrc="https://www.youtube.com/embed/{id-here}?html5=1&rel=0&playsinline=1&autoplay=1&modestbranding=1"

The youtube example in your documentation also requires two clicks to play, once to launch the bigpicture modal and a second to start the youtube video.  Vimeo works with one click.  That makes me think there's an issue here.  As a reference, fancybox does autoplay, so it's not a change in chrome or youtube.  Example here: https://fancyapps.com/fancybox/3/

Would you mind trying this and letting me know if it resolves the issue?
https://bptest.surge.sh

Yep, youtube is now a single click to play.  Thanks for jumping on that, can you share the solution?  The second video with youtube in an iframe looks like the same iframeSrc as i have. Code change?

Code change. Just needed to add an extra allow attribute to the iframe as outlined by google a while back. Something I should have done earlier, but apparently wasn't enforced for youtube until recently.
I'll update and release w/ the fix today or tomorrow.

Released 2.1.1 which should fix this issue. Let me know if you run into it again.


G loss increases much suddenly?

@igul222
I have implemented wgan-gp by myself, In my application, G loss sometimes increases much suddenly

But D loss is still stable

And the gradient penalty is also stable

Any idea？ thanks!

I experienced the same outcome in my implementation when I added learning rate decay every 25k iterations. Whenever the learning rate decreases the loss of G goes up, the real loss of D goes up, the fake loss of D goes down (- loss G) but the overall loss of D continues to increase as normal.
Any idea what could cause this @igul222 @martinarjovsky ? Is there some correct way of doing this learning rate decay? Did you manage to find a fix @LynnHo ?

@crisbodnar I have found recently in my work that layer normalization may cause this phenomenon, and instance normalization may help.


added traversing through declaring types to obtain full context display name

see attached picture for example of nested test display name

@molszews You can grab a "master" build of the vsix at https://ci.appveyor.com/project/machine-visualstudio/machine-vstestadapter/branch/master/artifacts in case you don't want to wait for an official release.

@ivanz it's a pity as I wanted to use it on Visual Studio Team Services (Visual Studio Online). Any chance for an official minor update?

@molszews  I will try to push out an update in the next couple of days 👍


Improve conformance reports structure

What would you like to be added:
https://github.com/kubernetes-sigs/gateway-api/pull/2391 proposed a new way of organizing conformance reports belonging to multiple organizations and provide a README.md file for each of them; such a README.md file should provide a brief description of the project, a table of content, and instructions on how to reproduce the claimed results.
To achieve the above, the related GEP paragraph needs to be implemented.
/area conformance

@mlavacca are you intending to move to that for only v1.1+ reports or should we do some kind of backfill?

@mlavacca are you intending to move to that for only v1.1+ reports or should we do some kind of backfill?

I am very open to suggestions. I do not think we should organize all the reports this way; maybe we can leave the pre-graduation reports as they are and start applying this structure from 1.0. What do you think?

maybe we can leave the pre-graduation reports as they are and start applying this structure from 1.0. What do you think?

That's going to happen naturally anyway, unless you intend to modify git history.
If the ask is "we don't require the new reporting structure until v1.1 lands" I don't really see any problem with that, we just update all current ones slightly before release.

I think if we're going to cut things over, we should cut them over and make the changes. I did a similar thing with the GEP shuffle, and, while it was a big PR, it makes it much easier for everyone.
Trying to keep track of two different options is very complicated - I think that putting extra effort into only having one way to do things is worth it.

Given how things are going to land timing wise, I have my suspicions that it's all gonna come down naturally at one time anyhow (e.g. we're aiming to get these last few conformance profiles bits done before Kubecon Paris, which is also when we want to release v1.1).

/assign


Add support for component aws-kinesis

http://camel.apache.org/aws-kinesis.html

Found 9 matching posts for subject:aws-kinesis in Camel - Users within 700 days


vscode-settings as VSCode Profile?

Clear and concise description of the problem
Not an Issue, just an idea to alternatively/additionally make your vscode-settings available as a VSCode Profile.

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I gave it a try, but I see the problem is that the profile file is not really a JSON, which is impossible to maintain. I can not do a direct export because the settings I shared are different from what I am using locally (I need to strip away some personal stuff). So I consider this is not "a piece of cake".
So as a conclusion, no, I am not doing that for now. For these settings, I believe it's also better for ppl to know each settings and take what make sense to them.


Allow provider users to reinstate deferred offers from previous cycle

Context
The full version of this flow is complicated, as it will allow provider users to change the details of the courses they re-offer, if they wish to. For now, we are giving provider users the ability to reinstate deferred offers without making any changes to their details. This means last year's offered course and all of its details (e.g. location, study mode) must be available as an option in the current recruitment cycle.
The plan is to allow the marking of individual of offer conditions as met/not met, as well as the modification of the conditions list as part of this flow. However, our system currently supports only the marking of all conditions as met/not met, so this is what provider users will be able to do while reinstating an offer. No changes can be made yet to the list of conditions.
Changes proposed in this pull request
Course is available

Course is not available

Implementation details
This PR uses the same 'wizard' pattern as provider user invitations and provider relationship setup, as the complexity of this feature will increase over time. A new ApplicationChoice database field :status_before_deferral has been added, because applications can be in either 'pending_conditions' or 'recruited' states when they are deferred and we need this information in order to present the status of conditions as they were before the offer was deferred.
Guidance to review

Would we like to store more metadata when reinstating an offer?
Should the introduction copy in this MVP be updated to be more course_option-centric? -- Yes, the text shown if any of the course details are not available in the current cycle has been updated.
Should there be some text advising users who would like to change the list of conditions they need to contact support?

Link to Trello card
https://trello.com/c/zrLd3K8W
Things to check

[ ] This code does not rely on migrations in the same Pull Request -- IT DOES
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency -- we'll backfill this column manually (using the audit log) for the few applications affected.
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Do not use bold on the prompt for ‘not available’.
The first paragraph on the review deferred offer page should just be:
The details of the course you offered previously are not available in the current cycle.

The rest of the page isn't right and should look like this:

The prompt should read:
The details of the course you offered previously are not available in the current cycle.

Should there be a "Change" link on the conditions on the Check page?

Should there be a "Change" link on the conditions on the Check page?

Have just added an 'Update status of conditions' link, as per the design.

Issues:

the panel should not show a link to update the status of the conditions
the last condition should not have a bottom border

There should be no bottom border on last condition:

Again no bottom border on last condition.

The note at the bottom should say:
We’ll email the candidate to confirm their new offer and remind them of the conditions for it.

The note at the bottom should say:
We’ll email the candidate to confirm their new offer and remind them of the conditions for it.

Hiding "and remind them of the conditions for it" is on purpose, when the conditions are 'still met'.

Should there be a "Change" link on the conditions on the Check page?

Have just added an 'Update status of conditions' link, as per the design.

I've removed it, as per @adamsilver 's suggestion.

Too much space at the bottom of the defer panel - please compare to proto (or we can pair)

This error message should read:
Select yes if the candidate has met all of the conditions
and
Select yes if the candidate has still met all of the conditions

This error message should read:
Select yes if the candidate has met all of the conditions
and
Select yes if the candidate has still met all of the conditions

Discussed on Slack, keeping this simple with one error message for both cases: Select yes if the candidate has met all of the conditions


How do i use this plugin to add Moss block from Vanilla Minecraft

How should use this? Example give me than I should I think!

This plugin is a demonstration for plugin-developers on how to use the PMMP API to register items and/or vanilla blocks not yet registered. It is not intended to be used by users to implement items/blocks.


when select "Highlights" in Russian and Ukrainian, application crashes

The error description:
JWLManager v4.3.2
Windows-10-10.0.19045-SP0
Traceback (most recent call last):
File "JWLManager.py", line 707, in regroup
File "JWLManager.py", line 679, in build_tree
File "JWLManager.py", line 670, in define_views
UnboundLocalError: cannot access local variable 'views' where it is not associated with a value

Thanks for reporting.
This is due to inconsistent translation - with the recent changes which were not applied to other parts of the interface. Should be fixed now.

Confirm fixing )
нд, 14 січ. 2024 р. о 20:01 Eryk J. @.***> пише:

Thanks for reporting.
This is due to inconsistent translation - with the recent changes which
were not applied to other parts of the interface. Should be fixed now.
—
Reply to this email directly, view it on GitHub
https://github.com/erykjj/jwlmanager/issues/155#issuecomment-1891019344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANFLV46SDF7MYH4HVK5EEY3YOQMNZAVCNFSM6AAAAABB2FKJYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGAYTSMZUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--

Best regards,
Yurii Korotkiy
skype: jurij.korotkij
+380638575166


Set up DataPalooza run of show

I put a draft in the Logistics folder. Can you guys see what you think? Any ideas on ways to tighten it up?
https://docs.google.com/document/d/1uzgcBSzyboBrwzCfpI2qaFS3Hu4eJbr-HA5XsUGEDA0/edit?usp=sharing

Looks good to me - I made a few minor tweaks and we are missing the 2017 winner

Added the guest Wifi info. (no password, you have to accept the Terms in a
browser)
If you want me, or someone, to do a welcome, then I can cover logistics.
Should be short and sweet.
On Thu, Oct 4, 2018 at 4:28 PM Janel<EMAIL_ADDRESS>wrote:

Looks good to me - I made a few minor tweaks and we are missing the 2017
winner
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1312#issuecomment-427157965,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3IeyZ_n1gjB-qEGddPY-wGrQcxoOJ6ks5uhm9WgaJpZM4XIxNo
.

That sounds great. Feel free to add any specifics that you want, @dtraleigh .


feature request: python bindings

I would like to use this library from python and am willing to implement the bindings, but I wanted to gauge interest in upstreaming these and give an opportunity for feedback/ directions before beginning work

Oooo this would be interesting. Python bindings for foundry compilers <3

That's great!


The Ordered list show bug

Steps
Always choose the ordered list, view more 👉👉👉  Here

@Rain120 This is not a bug, it's the CommonMark's spec. When creating an AST with markdown syntax, if the list marker follows a rule such as 1., an ordered list is created. List items created later are created as list item nodes of the same type until the next list appears. So, even when rendered in the right preview area, it is not displayed based on syntax, but the current behavior is correct because nodes created with AST are rendered with ʻol` element

@seonim-ryu


Update install-office-on-wvd-master-image.md

Same issue as prior page, two forward slashes in the install path that don't need to be there.

@chrisnylen : Thanks for your contribution! The author, @ChJenk, has been notified to review your proposed change.

@chrisnylen Good catch! Sorry I missed it. I completely approve of your changes but not sure how to proceed. Do I need to sign off at this point or do you?
FYI, the new point of contact for this file is @DHB-MSFT (Daniel H. Brown in Office).


Add BookStore-iOS by @nsoojin

[x] Project URL: https://github.com/nsoojin/BookStore-iOS
[x] Update contents.json instead of README
[x] One project per pull request
[x] Screenshot included
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

Hey MIT should be lowecase: mit
Sent with GitHawk

Thx
Sent with GitHawk


Auto import smart contract into the main page of the generated UI(?)

This needs exploration to determine the best approach, for the user from dev to production. Likely just importing the file directly will work, both 1.) locally during dev, and 2.) will be built into their UI project.
For our supported UI frameworks:

[x] Svelte Kit
[x] NextJS
[x] VueJS

Closed
#291
#296
#295


mpt model support?

Feature request
Can you please add mpt model support to this library?
Motivation
just testing things, and mpt seems to be unsupported by multiple huggingface libraries
Your contribution
im just getting started, im not sure if ill be of any help

Hi @sail1369! We will have to wait for MPT to be integrated to Transformers first. And then it would be possible to work on it.
More specifically, what are you interested in? ONNX export for MPT?

Hi @sail1369! We will have to wait for MPT to be integrated to Transformers first. And then it would be possible to work on it. More specifically, what are you interested in? ONNX export for MPT?

The model inference is quite slow even on a 3090, and I was also trying out multigpu to see how that would make any difference

Has there been any movement on this? Mosaic includes converter from HF to ONNX (https://github.com/mosaicml/llm-foundry/blob/main/scripts/inference/convert_hf_to_onnx.py) but I cannot get the exported model to load with Optimum.

hi @zacharyblank , for native support we will need to have https://github.com/huggingface/transformers/pull/24629 merged first.
I could extend the work in https://github.com/huggingface/optimum/pull/1143 to allow arbitrary model type support when a custom ONNX config is passed.

@fxmarty any idea on timing? I'm blocked by this and am incredibly grateful for the attention.
Thank you!

@zacharyblank In the coming days! An idea could be to upload custom ONNX configs as well to those models repo that have custom code.

@fxmarty not sure I follow your suggestion. I tried creating a custom onnx config following these docs: https://huggingface.co/docs/optimum/exporters/onnx/usage_guides/contribute but still ran into issues around MPT not being supported or text-generation-with-past not being an available task.
Maybe you're suggesting something else?


Build custom events on top of this codebase to ensure scalability

Require this codebase and extend the Model\Events class with self-defined event name and parameters.

I was considering making custom events for marketing and other stuff; but decided to either make sub-dependencies for that or let others developer on top on the bare codebase.


Add numpy 2 compatibility check to ruff

Numpy 2.0 will be released soon and it is advised to check all packages which depend on numpy to ensure that they won't break when this happens (as there are a few API changes). Thankfully there is a ruff check for this. I added it to our pyproject.toml and bumped the ruff version in our pre-commit check.

The new version of ruff seems to not like our pyproject.toml configuration:

Good catch, I fixed this. This error did not show up for me when ran pre-commit though. Where did you see it? Some log file?

Where did you see it? Some log file?

At the bottom of the pre-commit step log here. But I've also seen this warning locally when running freshly-installed ruff from the command line.


http://docs.spring.io/ to have summary of links to all docs in pdf, html, html single, repository, examples repositroy

(Is this the right place for raising issue?)
I'd like http://docs.spring.io/ to have links to all (currently released) docs in pdf, html, html single, repository, examples repository.
Reason is that I download docs in .pdf format from time-to-time for reading.
Currently http://docs.spring.io/  just redirects to http://spring.io/ , so it take a while to download all, say, .pdf
Example

Projects
Main
.pdf
.html
.html single
repository
examples repository

Platfrom
http://platform.spring.io/platform/
.pdf
.html
.html single
repository
examples repository

Spring Boot
http://projects.spring.io/spring-boot/
.pdf
.html
.html single
repository
examples repository

There is a start at https://github.com/paulvi/spring-projects-links-to-docs-and-examples-summary/blob/master/README.md#spring-projects-links-to-docs-and-examples-summary


Add //cut ?

I want //cut command.
Plugin version: 1.2.0-beta2 (dev 67)

You could use //copy and //set instead.

Added


Running Flutter in AOT mode for Embedded Devices

I am trying to run a Flutter application using @chinmaygarde flutter_wayland on Raspberry Pi(ARM) platform , I have used a modified version of the same (@jwinarske https://github.com/jwinarske/flutter_wayland/pull/1) which has included support for AOT builds.
In order to create the necessary binaries, I created flutter-engine for both host(linux) and target(ARM) with
--runtime-mode release flags, generated app.dill and libapp.so The steps I used were :
flutter-engine-host/src/out/host_debug_unopt/dart  \
          flutter-engine-host/src/out/host_debug_unopt/frontend_server.dart.snapshot \
          --sdk-root flutter-engine-host/out/host_debug_unopt/flutter_patched_sdk/  \
          --aot --tfa --target=flutter --output-dill build/linux_arm/app.dill lib/main.dart

`flutter-engine-arm/git-r0/git/src/out/linux_release_arm/clang_x64/gen_snapshot --deterministic  \
           --snapshot_kind=app-aot-elf --elf=libapp.so --strip app.dill`

This is ouput I get when I invoke gen_snapshot
Dart VM version: 2.9.0-edge.flutter-a69cb6d (be) (Fri Apr 24 11:49:43 2020 +0000) on "linux_simarm"
So I have libapp.so and app.dill generated now, so how should I run the flutter_wayland from now on, what all further changes do I need to make. Normally I used to run flutter_wayland flutter_assets with output of running flutter build bundle in app directory. How should I change the packaging of arguement passed to flutter_wayland?

Added will need additional triage because the issue seems about modified version of flutter_wayland

Custom embedding AOT configuration is documented at https://github.com/flutter/flutter/wiki/Custom-Flutter-Engine-Embedding-in-AOT-Mode.

Yh, I did go through the same but I was confused on what all arguments to pass to flutter_wayland instead of flutter_assets and that's why I raised the issue.

flutter_wayland isn't part of the Flutter project, so if your question is about flutter_wayland APIs rather than the embedder API, this project isn't the right place to file an issue.


Disconnected from Tado cloud service

Hey,
no connection is possible with the newest version of the adapter and iobroker

tado.0
2020-06-17 20:45:29.964
error
(18827) Disconnected from Tado cloud service ..., retry in 30 seconds !

tado.0
2020-06-17 20:45:29.961
warn
(18827) This will be refused in future versions. Please report this to the developer.

tado.0
2020-06-17 20:45:29.960
warn
(18827) The id "438872" has an invalid type!: Expected "string" or "object", received "number".

Please help me

Installiere die Version von Git, dann funzt es.


Update s3-utils, sns-utils, ... to 0.1.206 in scala-steward-dependencies

About this PR
📦 Updates

uk.gov.nationalarchives:s3-utils
uk.gov.nationalarchives:sns-utils
uk.gov.nationalarchives:stepfunction-utils

from 0.1.205 to 0.1.206
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "uk.gov.nationalarchives" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "uk.gov.nationalarchives" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #1320.


Nothing to see here.

Don't worry, I have no problem with LGBT people and I'll never vote for a sexist president like the US just did. So you're safe here!


Add favicon assets

Addresses #24, replacing placeholder favicons and metadata files.

@Arthelon Please try setting a relative start_url (https://developer.mozilla.org/en-US/docs/Web/Manifest/start_url) to see if it works.


Failed to find a pre-opened file descriptor through which ".clangd_ver" could be opened

I installed Lapce recently and went to install this plugin. I get this error when opening Lapce afterwards. I was able to make this error not appear by manually installing clangd from apt (14.0.0-1ubuntu1 in my case) and manually setting the version and path in settings.toml, but it still does not seem to actually do anything.

It turns out the latter issue of it not doing anything is only present in the Flatpak version. The .tar.gz version from the website still does show this error, but specifying the version and path in settings.toml does at least seem to make it actually work.

Same here, I'm on Fedora 37 (Workstation), running from flatpak doesn't work, but from the tar.gz works as described.

just curious, have you tried using flatseal to give it more permission

Fixed


🌱 Move the cron job to internal package

What kind of change does this PR introduce?
Reduces exposed APIs by moving cron to internal package.
(Is it a bug fix, feature, docs update, something else?)

[ ] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
What is the new behavior (if this is a feature change)?**

[ ] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
NONE

Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

Removes `cron` package from exposed APIs.

This is should be a breaking change. Though technically no one should be using it. Let's still call it a breaking change.


General UI/UX improvements

I've been going around the site a bit and there are a lot of small fixes that could be done to improve the UI/UX of FreeCodeCamp.org. For the sake of length, I kept it to the home view.
Here is a couple of things.
Make clickable list buttons full width.
Currently:

Full width hover:

Search results are very unreadable
Current:

Suggested solution:

Home view is quite cluttered and unwelcoming
Current:

Very quick fix suggestion, done by moving things around in the inspector. I would like to edit this page more extensively.

I like what you're doing with this project and I'd love to contribute and work on these things to improve the site. I'd love to hear your input @QuincyLarson and @ahmadabdolsaheb.

Just to make sure: the change to search is the addition of lines separating the results, not the removal of the blue background?  An indicator of the currently selected result is important.
That caveat aside, these look like good changes.

No, the blue background on hover is good. I would keep it.

I like these - I would also change that blue hover on the search results to our dark blue. And possibly use a lighter blue for the background of the "since 2014" sentence - and include the companies in the box.

A newbie question. Are those suggestions that you want to implement or is it anyone can pull and try?

@DannyBoris I'm new to the project as well so I'm not too familiar with how things are done. But I guess if you want to tackle some part of this issue we could split the tasks. Since there are multiple things here and they're easy to separate. Then we could do 2 pull requests? Maybe @ojeytonwilliams can give some input on this? :) Otherwise, you can check issues tagged with "help wanted".

These are suggestions for improvements @DannyBoris.
I would wait for more input for making a PR.

@Tuuben Hey,
Yeah let's take it easy. I have never actually contributed to open source and fcc seems like a good start (when it comes to small changes). ill also vote for waiting a bit more.
Thanks for the response

If you don't mind waiting, then you'll waste less time creating a feature that's not quite what's desired.  Chances are the broad strokes are what's wanted, but perhaps not the specifics.  I can't speak for the core team, though.
As for the practicalities, small focused PRs are ideal.  They are easy to review and maintain, so splitting this into three different PRs (landing, search and curriculum) makes sense to me.  It's not critical, though, so however you want to divide it up is likely fine.

Thank you for the suggestions, here is my take:

let's implement the full width hover on map
I am onboard with search results padding and border addition. note: it should be updated for news, forum, and learn since the universal navigation is used across services.
the landing page could use an update. I believe the current mock looks good, but here are some considerations:

the CTA button should be above the fold on 13 inch displays.
it would be great if we could avoid the dark " since 2014" div
we could probably make the front size difference a bit smaller
the width of the CTA could be narrower

General note for the landing page: There are a variety of minimal text and cta landing pages around that we could use to inspired our re-design.
Also, since the landing page and the upper div of /learn look the same, they should use the same component.

Happy to chip in when consensus is gathered

Hey all,
@ojeytonwilliams 's suggestions found reasonable. I be up for taking search once we can work on it

It's probably safe to make some PR's at this point. The hover effect and search results have some clarity on what needs to be done there. Not sure on the landing page. I still like my suggestion of changing the blue hover on search to one of our other blue's. But I think if PR's are made, we can probably tweak things from there if needed.

@DannyBoris I've made a PR for the menu list. Are you still interested to take a look at the search?

This is a great idea - willing to help if needed.

Thank you for your help everyone, I believe most of the items mentioned in this issue has been addressed.  Only the general aesthetics of the landing page remains that deserves an issue of its own.
I will close this issue for now. Please feel free to open an issue to discuss the landing page specifically.