LWMSTileLayer baseUrl Error

Description
Hi,
I got The data property "baseUrl" is already declared as a prop. Use prop default value instead.  when using the WMS component. How to solve this issue?
vue.runtime.esm.js?2b0e:587 [Vue warn]: The data property "baseUrl" is already declared as a prop. Use prop default value instead.
found in
--->

 at src/components/views/map/MapTest.vue
 at src/layout/Layout2.vue
 at src/App.vue

Regards

Steps to Reproduce
<template>
  <l-map ref="myMap" :zoom="zoom" :center="center"
         :markerZoomAnimation="true"
         :fadeAnimation="true"
         :minZoom="9"
         :maxZoom="14"
         >
    <l-wms-tile-layer
      v-for="layer in baseLayers"
      :key="layer.name"
      :base-url="layer.url"
      :layers="layer.layers"
      :visible="layer.visible"
      :name="layer.name"
      :transparent="true"
      format="image/png"
      layer-type="base"
    />
  </l-map>
</template>

<script>
  import {LCircleMarker, LControlLayers, LMap, LMarker, LPopup, LWMSTileLayer,LTileLayer,LControl,LControlAttribution} from "vue2-leaflet";
    export default {
        name: "MapTest",
      components: {
        LMap,
        "l-wms-tile-layer": LWMSTileLayer,
        LControlLayers,
        LMarker,
        LPopup,
        'l-circle-marker': LCircleMarker,
        LTileLayer,
        LControl,
        LControlAttribution
      },
      data(){
          return {
            zoom: 9,
            bounds:null,
            markers: [],
            center: [1.0422703924068677, 10.498809814453127],
            mapHeight:750,
            baseLayers: [
              {
                name: "Suhong",
                visible: true,
                layers: "flex:BU8_Polyline",
                url: 'http://localhost:8080/geoserver/test/wms'
              }
            ]
          }
      }
    }
</script>

<style scoped>

</style>

Expected Results

Actual Results

Browsers Affected

[ ] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 9
[ ] Safari 8
[ ] IE 11

Versions

Leaflet: v1.4.0
Vue: v3.7.0
Vue2Leaflet: v2.1.1

Hi! could you create a reproduction in codesandbox / codepen?

Hi DonNicoJs,
There's global variable with the name baseUrl in my template which confilct with the WMS's prop.  It is OK now.
Regards


Fix persistent failure on gift_entry/error_validation_rename_fields.robot

Critical Changes
Fixes the component error in the Gift Entry form by adding a scroll to keyword.
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

your test is still failing and I strongly feel it's due to component error even though it says locator not found. The component error popup might be blocking the clicking of Today button. Add capture screenshot decorator to the Fill Gift Entry Form keyword to see the exact error.


ESP32 flash error on PCB

I placed esp32 on PCB and tried to flash it through RX TX and GND wires. I was able to flash two or three times but most of the time I only got random errors like "Response doesn't match the request", "Invalid packet header" and "Fail to target the RAM".  Has somebody encountered the same issue? Thanks!

Hi @HuanchengHu ,
Usually this indicates problems with the hardware supplying power to the chip.
Try some of the things mentioned here: https://github.com/espressif/esptool#troubleshooting
Also, check that you followed the layout recommendations in the datasheet for the ESP32 chip or module you are using. Particularly adequate capacitance.
Reduced the baud rate in esptool.py may help if the hardware performance is marginal.


added deps

:no_entry: Snyk checks have failed. 3 issues have been found so far.

Icon
Severity
Issues

Critical
0

High
3

Medium
0

Low
0

:no_entry: security/snyk check is complete. 3 issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Cellpose using multiple GPUs

Has anyone tried using Cellpose to train and predict using multiple GPUs? This would make training and segmentation faster. We have 4x RTX5000A and currently, I have noticed that it only uses one GPU out of the four GPUs during training or prediction.
I also made the same post in the ImageJ forum, just in case :)
Thanks!

This is on the docket for things to implement but we don't have a timeline at the moment. It would require a significant refactor to implement, see #447


[FIX] Identify missing files in logs

CCFPCM-479
Objective:
This will show us which files are missing

Approved (pending tests passing of course, but otherwise looks good)


[RadioFrance] Extractor for Radio France stations (www.radiofrance.fr)

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
This PR adds support for podcasts (radio shows) and live musical webradio of Radio France (stations France Inter, France Culture, France Info, FIP, Le Mouv and France Musique).
Old extractors are removed since they do not work anymore after the merge of their respective websites under www.radiofrance.fr.
This closes :

https://github.com/ytdl-org/youtube-dl/issues/17276 (extractor for FIP)
https://github.com/ytdl-org/youtube-dl/issues/15349 (old site is gone)
https://github.com/ytdl-org/youtube-dl/issues/4646 (Le mouv')

Consider adding playlist support, as per https://github.com/ytdl-org/youtube-dl/issues/31464#issuecomment-1399553253.
In the problem page, the playlist is in an ItemList in a ld+json block, as well as in the HTML itself.

Also this error with https://www.radiofrance.fr/franceculture/podcasts/le-pourquoi-du-comment-economie-et-social/le-neo-liberalisme-et-la-fin-du-plein-emploi-6657160.


Handle multiple HTTPProxies

Summary
Handle multiple HTTPProxies
Motivation
We run contour with many HTTPProxies pointed at a single service. If we were to use this plugin in the current state, it would only adjust the weight of one HTTPProxy, leaving 100 weight on the rest of them.
Proposal
Instead of:
trafficRouting:
  plugins:
    argoproj-labs/contour:
      httpProxy: my-proxy

Configuration could look like:
trafficRouting:
  plugins:
    argoproj-labs/contour:
      httpProxies:
        - my-proxy
        - my-other-proxy

Then we can simply loop over this list of proxies.
I have a working branch here: https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-contour/compare/main...sneako:rollouts-plugin-trafficrouter-contour:multiple-httpproxies?expand=1#

Good proposal!


Fix LLDB test failures after latest dependency version updates.

After #1805, we're seeing test failures like the following in debug::lldb::test_debug_dwarf_ptr:

```
test debug::lldb::test_debug_dwarf_ptr ... FAILED
failures:
---- debug::lldb::test_debug_dwarf_ptr stdout ----
thread 'main' panicked at 'didn't pass check > (lldb) target create "/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime"

Current executable set to '/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime' (x86_64).
(lldb) settings set -- target.run-args  "-g" "--opt-level" "0" "tests/all/debug/testsuite/reverse-str.wasm"
(lldb) command source -s 0 '/tmp/.tmpmh81yA'
Executing commands in '/tmp/.tmpmh81yA'.
(lldb) b reverse-str.c:9
Breakpoint 1: no locations (pending).
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matched #0: \bBreakpoint 1: no locations (pending)
WARNING:  Unable to resolve breakpoint to any actual locations.
(lldb) r
1 location added to breakpoint 1
Process 14667 stopped

thread #1, name = 'wasmtime', stop reason = breakpoint 1.1
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matched #1: \bstop reason = breakpoint 1.1\b
frame #0: 0x00007ffff7fcf053 JIT(0x5555571bdd70)`reverse(s=(__ptr = 66562), len=13) at reverse-str.c:9:12
^~~~~~~~
Matched #2: \bframe #0\b
^~~~~~~~~~~~~~~~~~
Matched #3: \breverse(s=(__ptr =
Missed #4: "Hello, world."

Process 14667 launched: '/home/runner/work/wasmtime/wasmtime/target/debug/wasmtime' (x86_64)
(lldb) p __vmctx->set(),&*s
', tests/all/debug/lldb.rs:52:5

</details>

We suspect the version-bump of some dependency caused this, though we aren't yet sure why (and we cannot reproduce locally). We will disable the test for now but we need to investigate and re-enable.

We're temporarily avoiding CI failures by pinning versions in Cargo.lock in #1811, but we should resolve the underlying issue and the update the lock file to the latest versions.

cc @yurydelendik

With a green master it's clear that cargo update -p backtrace is causing the regression here. I can reproduce this locally, and the problem is that LLDB prints:
error: Can't run the expression locally: Interpreter doesn't handle one of the expression's opcodes

when we try to execute
p __vmctx->set(),&*s

I'm not really sure how the backtrace crate is related to this. Even the gimli/addr2line/object/etc updates don't seem to affect wasmtime since they're all on versions that wasmtime itself isn't using, only the backtrace crate is using them.
@yurydelendik do you know where that error message may be coming from?

@alexcrichton "backtrace" now indirectly depends on "gimli 0.21", I'm thinking it is what is giving an issue. I'm working on upgrading our "gimli 0.20" atm, though not sure why it is giving "Interpreter doesn't handle one of the expression's opcodes".

I'm not sure why the gimli 0.21 dep would cause any issues though? That's exclusively used by the backtrace crate (everything else in wasmtime is using 0.20), so is it like it's mere presence is causing issues?

I'm not sure why the gimli 0.21 dep would cause any issues though?

Me neither. But I would like to upgrade it anyway, but it is not easy. Too much API refactoring happened between 0.20 -> 0.21 .

do you know where that error message may be coming from?

It is likely LLDB -- it cannot decode generated by wasmtime DWARF expression

It is limited to Linux platforms. Bisect points for https://github.com/rust-lang/backtrace-rs/commit/5ad0b762eb84de27ee2917b61356786f3ee8260b

At this point it sounds like this is exposing a preexisting bug. The only real change in that commit which would affect this is that libbacktrace's C code is gone, and some new Rust code is pulled in. For these tests and LLDB I don't think any of that code is executed, but presumably the DWARF for wasmtime has changed, perhaps significantly, as a result.
Would it make sense to try to track this down not as a regression in the backtrace crate but instead as a possible bug in wasmtime's emission of dwarf information? (or LLDB's interpretation of it?)

@alexcrichton the problem is related to LLDB only (works on GDB). Running any p any_call() inside wasmtime debug session, without even JIT code, causes that too:
(lldb) b wasmtime.rs:63
(lldb) r
(lldb) p set_vmctx_memory(0)

Which fails with the same error.
Maybe one of the new modules contains unsupported DWARF data?

Adding to Cargo.toml:
[profile.dev.package.backtrace]
debug = 0

allows test to past.
Tested with lldb-10 for Ubuntu -- it works there too. (It was working for lldb-9 on MacOSX, not on Ubunty)
If CI will start using lldb-10, the problem will go away.

Nice find! I'd be fine taking care of the CI bits if you want to check in that fix to Cargo.toml?

if you want to check in that fix to Cargo.toml?

Sorry, there are two solutions above: fix in Cargo.toml or lldb-10. Moving CI to lldb-10 will completely fix the issue.

So I thought LLDB 10 would be pretty easy to install from https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0, but unfortunately those tarballs don't contain lldb at all. They did for LLVM 9 though (?)

Note that https://github.com/bytecodealliance/wasmtime/pull/1832 is going to update backtrace, but is adding
# Cargo.toml
[profile.dev.package.backtrace]
debug = false # FIXME(#1813)

to temporarily work around these failures.
We should remove that when properly fixing this bug.


Upgrade menu item to contain svg with preview

A menu item should be able to have a SVG as label. a preview would be nice :-)

Moved this issue to idea.
It is is not that crucial because it is possible to implement and use the name in a map with icons or as an filename.


PyPI availability of lag-llama package

Hi lag-llama team,
Thank you for developing this project, it's a highly valuable resource.
I wasn't able to find the lag-llama package on PyPI, which makes it a bit challenging to integrate into projects using tools like Poetry.
Could you let me know if there are any plans to publish lag-llama to PyPI, or if it's already available under a different name?
Best regards.

Hi, you can install it withpip install git+https://github.com/time-series-foundation-models/lag-llama.git.

Thank you for the quick response. I’m aware that the package can be installed directly from the repository. I was just curious if there are any plans to publish the project on PyPI in the future, as my team and I are encountering some challenges with security audits.

Yes, I can publish this in PyPI if it's really required for you. Can you let me know if they've been resolved?

We're still encountering the issue. We’re eager to integrate lag-llama into our project, but the lack of availability on PyPI is causing problems with pip-audit, which complicates our dependency management and affects our security controls.
Thank you again for your support. I truly appreciate your willingness to publish the library on PyPI and I’m looking forward to its release.


Allow configuring multiple OAuth clients in the same realm

What this does:
Allows different auth portals to use different OAuth clients with the same realm from the same identity provider. See greenpau/caddy-security/issues/307
Why do this:
Currently when multiple sites share an identity provider (eg. Google) with different client IDs they each need to specify a unique realm even though the sites are otherwise unrelated. As the realm forms part of the URL for OAuth callbacks this impacts external configuration as well, requiring clients to allow callbacks to eg. site1.com/oauth/google1, site2.com/oauth/google2, etc. instead of just site1.com/oauth/google, site2.com/oauth/google, etc.. Decoupling the otherwise unrelated configurations simplifies maintenance and set up when using multiple OAuth clients.
What this does not do:
Permit multiple instances of the same identity provider (Google, fb, etc.) within a portal configuration.
How it does this:
Removes requirement for unique realms across all identity providers during initialization.

I have read the CLA Document and I hereby sign the CLA

@matthias-stone , I will try getting to this issue soon. Would it be possible to do Google Meet so you can show me your setup?

Sure! Let's set something up.


Unable to use custom JsonFormat.Printer for ProtobufResponseConverterFunction

Hello, we’re trying to use in a custom com.google.protobuf.util.JsonFormat.Printer  for the ProtobufResponseConverterFunction , which we are using to convert the HttpResult from our endpoint into JSON
We’re doing this by passing in a custom instance of the converter function like so:
serverBuilder.annotatedService(myService, ProtobufResponseConverterFunction(JsonFormat.printer().includingDefaultValueFields())))

However, the custom Printer isn't being used. It looks like a new converter is being instantiated along the way, which results in the Printer passed in to be ignored

I guess it's a bug. 😅
The specified ResponseConverterFunction should be applied before the ProtobufResponseConverterFunctionProvider but it's not:
https://github.com/line/armeria/blob/87d2c926675c49d513855fa6b8a8c0844ee30f1f/core/src/main/java/com/linecorp/armeria/internal/server/annotation/AnnotatedService.java#L206-L235

Do you want to fix this by yourself? Of course, we can handle it if you don't have time for that. 😄

Will give it a shot 👍

Thanks, @resquivel-squareup 😄

To be precise, I think ResponseConverterFunctions  should be applied in the following order:

Annotated ResponseConverterFunction
Set via ServerBuilder.annotatedService() and equivalent
Found via SPI
Default ResponseConverterFunctions

Hello, I've created a Draft PR (definitely not for merging yet).
FlowAnnotatedServiceTest test_EventStreaming(), appears to expect the annotated-response-converter-wrapped-by-the-SPI-converter to be prioritised over just the annotated-response-converter. This seems to be a special case, so I wanted to get your opinion on it.

Good point. We need more options for the orders to resolve the conflict.
It seems that we can't prioritize an annotated ResponseConverterFunction always.

If the class type of an instance returned by ResponseConverterFunctionProvider.createResponseConverterFunction() is the same or super class,
We may prioritize the ResponseConverterFunction passed through @ResponseConverter or AnnotatedServiceBindingBuilder.responseConverters().
If ResponseConverterFunctionProvider.createResponseConverterFunction() returns a new type using the given ResponseConverterFunction, we can
assume that the ResponseConverterFunctionProvider either wraps or ignores the ResponseConverterFunction.

Had a chat with the team and we realized:

ResponseConverterFunctionProvider(found via SPI) uses the responseConverterFunctions set via annotation, service builder and default ones.
So the relationship between ResponseConverterFunctionProvider and others is not about which one is used beforehand.

It's just that ResponseConverterFunctionProvider uses the configured responseConverterFunctions.

So here's what we need to do:

Change the ResponseConverterFunctionProvider to use the configured responseConverterFunctions or to be applied after the responseConverterFunctions

so that users are always able to use the ResponseConverterFunction they want via setter
ProtobufResponseConverterFunctionProvider and ScalaPbResponseConverterFunctionProvider should be fixed to abide by the rule.

Add ResponseConverterFunction.orElse(responseConverterFunction) for easy chanining.
Update the Javadoc of ResponseConverterFunctionProvider.createResponseConverterFunction(...) to inform the ResponseConverterFunctions parameter.

Just for clarification:

Change the ResponseConverterFunctionProvider to use the configured responseConverterFunctions or to be applied after the responseConverterFunctions

By this, I think we mean that we will define the behavior of armeria's default ResponseConverterFunctionProvider implementation such that:

Each ResponseConverterFunctionProvider implementation will attempt to apply it's own ResponseConverterFunction
If not applicable, they will fall back to the passed responseConverterFunction

so I guess the PR would look roughly like follows (the same would be applied to ScalaPbResponseConverterFunctionProvider):
public final class ProtobufResponseConverterFunctionProvider implements ResponseConverterFunctionProvider {
...
    public ResponseConverterFunction createResponseConverterFunction(
            Type returnType,
            ResponseConverterFunction responseConverter) {
        if (isSupportedType(returnType)) {
            return new ProtobufResponseConverterFunction().orElse(responseConverter);
        }
...

I wanted to make sure I also understood @minwoox 's comments correctly 😅

Thanks for the responses, I’ve linked this new Draft PR so we can discuss the new implementation. Let me know if this is or is not what you intended.
As far as I can tell, this implementation doesn’t do this:

If the passed responseConverterFunction falls through, the ResponseConverterFunctionProvider will try to apply its own ResponseConverterFunction

The provider code is called when selecting a response converter to use, which is far before the responses are actually converted.
There is just a check in the provider to see if the class-to-be-converted is appropriate.
Therefore the fallthrough mechanism never gets a chance to be used with this implementation.
Also, without actually performing the conversion, we cannot validate at this stage whether the passed-in converter is indeed able to perform the conversion.
—--------
We may be running into this because of the differing behaviour between the ResponseConverterFunctions and their respective providers. Both FlowResponseConverterFunction and ObservableResponseConverterFunction take in responseConverters. When the time comes to convert, they prioritise using the passed-in response converters.
On the other hand ProtobufResponseConverterFunction does not take in a response converter at all. Therefore when the time comes to convert, it can't prioritise the passed-in converter.
This bit is relying on the fact that the response converter function will prioritise the passed-in converter.

Thanks for your response here!

I also wanted to clarify something. As far as I can tell, a side effect of this implementation is that for ProtobufResponseConverterFunctionProvider (and maybe ScalaPbResponseConverterFunctionProvider?), the order of using the converters during response conversion would be as follows:

Annotated ResponseConverterFunction, if it fails, then fall through
Set via ServerBuilder.annotatedService() and equivalent,  if it fails, then fall through
Default ResponseConverterFunctions, if it fails, then fall through
The ProtobufResponseConverterFunction converter we found via SPI

Whereas for some other converters found via SPI (e.g. FlowResponseConverterFunction), the behaviour would be:
Using the converter found via SPI, decorate with some additional behaviour, and then use the converters as follows:

Annotated ResponseConverterFunction,  if it fails, then fall through
Set via ServerBuilder.annotatedService() and equivalent,  if it fails, then fall through
Default ResponseConverterFunctions

Is this the behaviour that we're trying to achieve?
I realise this concern is mostly semantic and has no effect on the actual behaviour at the moment. I felt it was worthwhile to clarify this difference for documentation as well as posterity.
If we're happy with this, I'm happy to continue with the implementation.

Is this the behaviour that we're trying to achieve?

That's exactly what we need to achieve through this PR! 👍 👍 👍

I realise this concern is mostly semantic and has no effect on the actual behaviour at the moment. I felt it was worthwhile to clarify this difference for documentation as well as posterity.

I can't agree more than this. Yeah, we definitely need documents for this.
We need to update the Javadocs and also add descriptions to the official docs. 😄
https://armeria.dev/docs/server-annotated-service#converting-a-java-object-to-an-http-response
Thanks a lot! 😄

@minwoox Just a heads up, the existing ProtobufResponseAnnotatedServiceTest appears to be failing (I didn't notice it originally since other tests were failing too) due to the new behaviour:

Annotated ResponseConverterFunction, if it fails, then fall through
Set via ServerBuilder.annotatedService() and equivalent, if it fails, then fall through
Default ResponseConverterFunctions, if it fails, then fall through
The ProtobufResponseConverterFunction converter we found via SPI

Because we moved from always using a fresh new ProtobufResponseConverterFunction to using the Default converters first, we're exercising bunch of new code paths that weren't exercised before 😅
Would love to get your opinion on how you folks would like to handle this. 🙏

Oops, I didn't notice that the test's failing. Let me run the CI and see what's going on. 😄

Yeah, it's always that the devil is in the details. 😅
JacksonResponseConverterFunction is applied before the protobuf converter so it converts everything. 😓
Had a discussion about this with the team, and we have come to the conclusion that we need two different SPIs.

SPI that provides a sole instance of a response converter

This converter applied after annotation and builder converter

annotation converter 2. builder converter 3. SPI converter 4. default converter

SPI that provides a converter that uses the above 4 converters as the current SPI does:

I didn't expect that this is that hard. 😅 I'm really sorry for that. 🙏
If you want, you can continue to work on the PR. We will help you get it done.
Or we can take it from now because it's going to be a big change and it isn't probably a good issue who is new to this framework. 🙇♂

Thanks for the information, and no worries! I might have some time next week to have a look. Could you please provide some more info regarding

we need two different SPIs
?

In which scenarios would each SPI be used? What would the converter selection logic be? Which classes would need to be changed?

Let's say we have the following annotated service:
class MyService {
  @ProduceJson
  fun flowProtobufJson(...): Flow<MyProtobuf> {
      ...
  }

}

Server.buider()
      .annotatedService()
      .responseConverters(MyProtobufResponseConverter())
      .build(MyService())

We need two 2 response converters to completely convert Flow<MyProtobuf> into a JSON response.
First, MyProtobufResponseConverter will be used to convert each MyProtobuf into a JSON object.
Next, FlowResponseConverterFunction should be chosen to collect the JSON objects and convert them into
a JSON array.
We provide two APIs for a custom response converter.

ResponseConverterFunction defines how to convert an object.
ResponseConverterFunctionProvider defines how to create a ResponseConverterFunction via SPI.

The downside of the APIs is that they don't tell a ResponseConverterFunction is a primitive converter
or a delegating ResponseConverterFunction. So I'd like to change our API to show an explicit behavior that.
Note: As the API is @UnstableApi, we can still make a breaking change. 😅
Proposal:

Remove ResponseConverterFunctionProvider because we can directly use ResponseConverterFunction to create it via SPI.
Add DelegatingResponseConverterFunction that requires a delegate to complete to convert a response like FlowResponseConverterFunction.
DelegatingResponseConverterFunction has lower priority than primitive converters.

interface DelegatingResponseConverterFunction {
      // Fall through and directly pass to delegate if the result can be
      // handled by this DelegatingResponseConverterFunction
      HttpResponse convertResponse(
          ResponseConverterFunction delegate,
          ServiceRequestContext ctx,
          ResponseHeaders headers,
          @Nullable Object result,
          HttpHeaders trailers) throws Exception;
}

Thanks for the response. I have a work-in-progress draft PR which implements most of the above.
It doesn't address the case for Flow<MyProtobuf>, but it does fix the initial bug and the tests (mostly seem to) pass.
Please let me know what you think so far and if you'd like me to change anything major. Thanks!

It doesn't address the case for Flow<MyProtobuf>

Could you elaborate on this? I didn't catch what could be addsssed. 😅

Ah, I just meant I didn't write a test case for the exact scenario you mentioned for Flow<MyProtobuf> so I can't confirm that it's actually working


Pull request for code review

Matt,
You made some awesome contributions to this project. I really appreciate your work on the LoginActivity Page; this was an integral part of our application. We could not have integrated a login system without your valuable contributions.
I would like to suggest that you make smaller commits so that each change can be reviewed individually. Right now, the commit I reviewed is large and contains many lines of code doing different things. Having a smaller commit would make it easier for me to determine what you are trying to do with each commit.
Additionally, it would be helpful if you had separate commits for different files if they are doing different things and/or are part of different additions to features.
I would also like to suggest that you document your contributions with comments conforming to our coding style. This will make it easier for you and other developers to pick up from where you left off.

Finally, your overall contributions were timely and important.
Keep up the good work.


Fixing httpx.ReadTimeout handling in core.py

Hey! Congrats to this great project!
I've been getting some httpx.ReadTimeouts while trying to fetch data from the SEC. To handle these, I've added the retry wrapper from the retry package which retries after 2 seconds until the connection works. I've also added the dependency to pyproject.toml

Thanks for your contribution .. checking ..
Cheers!


pyephem dependency

@eteq @bmorris3 – What's the plan / timeline for getting rid of the pyephem dependency in astroplan?
If it's likely ~ a year or longer, I'd suggest to change the conda package and put pyephem as a dependency, so that users automatically get the full functionality.

@eteq said (on Slack) he's working on an astropy fix that will make the
PyEphem workaround unnecessary. @eteq would it be feasible that the fix
might be ready by astroplan v0.2?
On Friday, September 11, 2015, Christoph Deil<EMAIL_ADDRESS>wrote:

Assigned #111 https://github.com/astropy/astroplan/issues/111 to
@bmorris3 https://github.com/bmorris3.
—
Reply to this email directly or view it on GitHub
https://github.com/astropy/astroplan/issues/111#event-406846066.

--
Brett Morris
Graduate Student
Astronomy and Astrobiology
University of Washington
http://brettmorr.is

@eteq - we're nearing .Astronomy (two weeks way), any chance the AltAz fixes will be done by then so I can do a bunch of PRs to remove PyEphem from astroplan once and for all?

@eteq If I were to remove the PyEphem dependencies, update the moon methods, and change the requirements by the end of the week to astrpy v1.0.6, would you be able to review the PR? It shouldn't be a long PR and the tests don't have to change.
I would also be able to implement moon_rise_time :exclamation:

Closed by #167.


Use definitions for shared properties in details

Follow up to https://github.com/alphagov/govuk-content-schemas/pull/505
Please review commit by commit.
Features that share a name should share a definition. This:

avoids the risk that a format implements a feature that clashes with
the name of another feature
avoids the risk of implementing the same feature in a slightly
different way in multiple places
makes it harder to write details.json poorly

Add definitions for shared features

Try to add useful descriptions for each definition
All schema updates are backwards compatible
Many definitions match original property name, but others use a new name to represent a definition for a more specific concept (eg documents property uses "attachments_with_thumbnails" definition)
Add body definition that let's body be a string or an array containing two strings – govspeak and HTML
Add definition for confusing tags property and document usage
Policies and finders share many properties, these now use definitions

Policies had additionalProperties: true set on facets and filters, but on inspection of content the structure of the data was identical to finders. They've been switched to use the same definitions, removing any differences and reducing risk of drift

Content schema technical debt found

first_public_at needs to be replaced with first_published_at, documented in new definitions
public_updated_at is provided at the top level but coming_soon and unpublishing formats still use their version in the details hash 4ae1373
Travel advice has an ordered list of countries in the details, this could be an ordered list of links now links can be ordered

The date-time that renders for these countries is in an inconsistent format: https://www.gov.uk/api/content/foreign-travel-advice "public_updated_at": "2016-11-09T14:28:01Z", rather than "public_updated_at": "2017-02-02T17:33:02.000+00:00",

Formats still have withdraw_notices in their details hash, despite being provided at the top level (eg c8b8ee6)
The groups feature on service manual topics, topics and mainstream browse was slightly different

Topics and mainstream have been made consistent. The schema contains some leftover changes from https://github.com/alphagov/govuk-content-schemas/pull/203 - Properties marked as deprecated for future removal
Created a separate definition for groups that use content_ids rather than paths
groups for topics, mainstream browse and service manual could all use content_ids and links hash, similar to the behaviour of groups in document collections

Subtle differences between change_notes and child_section_groups (0fddc8b) on manuals and HMRC manuals

HMRC manuals are very similar, except they use section_ids for many things – in this case change notes are associated by section_id rather than a section content item or path

The email_alert_signup format uses summary for content, it should use description
email_signup_link should be using dependency resolution and links, rather than path and URI a2cec84
Travel advice contains publishing_request_id but it's not clear that it works, or is being used. According to @gpeng the team wrapped up before completion of this feature. 8f0673c2610eeaf84b5a107acb3ec1df47615352
Manual sections (and HMRC manual sections) define their parent using "manual" in the details, this could be "parent" in the links hash
Manuals define their organisations in the details, they should use links
Finders have a beta flag, it can be set by the publisher and rendered by frontend, no content is currently using and the feature if it remains should switch to using the phase property at the top level
HMRC manuals and email alert signups use custom breadcrumb properties

No breadcrumbs display on email alert signups, this needs to be fixed, and should use the common patter – basing breadcrumbs on the parent in the links hash
HMRC manuals is harder to update as it's based on section_ids and we don't control the publisher

Policies uses a custom nation_applicability property but should use the more widely used national_applicability definition

+109,999 −5,483 🤔

Looks great.
Publisher is now being tested as part of continuous-integration/jenkins/branch on new CI – you can safely ignore the "Verify publisher against content schemas" failure which is coming from old CI.
It'd be good to get a better understanding of the groups technical debt which affects the service manual, so I can get a card in our backlog to resolve it 👍

It's worth noting that this PR hasn't looked for cases of the same feature being used across formats but with different property names.

Content schema tech debt captured in a Trello board here:
https://trello.com/b/BOULnRrS/content-schema-tech-debt


Fix problems on IgnOGRE when version is not found

🦟 Bug fix
Summary
When Ogre is not found (looking for 1.10 in a 1.9 environment), the builds fail with:
CMake Error at /usr/share/cmake/ignition-cmake2/cmake2/FindIgnOGRE.cmake:214 (if):
  if given arguments:

    "VERSION_LESS" "1.11.0"

  Unknown arguments specified
Call Stack (most recent call first):
  /usr/share/cmake/ignition-cmake2/cmake2/IgnUtils.cmake:189 (find_package)
  CMakeLists.txt:69 (ign_find_package)

-- Configuring incomplete, errors occurred!

There is a final block starting at line 240 that is not protected by the check of OGRE_FOUND leaving OGRE_VERSION empty and making the whole thing to crash. I did not find any reason not to include it under OGRE_FOUND.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

@adlarkin , I'm testing it with this PR: https://github.com/ignitionrobotics/ign-rendering/pull/376
Without these changes, I get the VERSION_LESS cmake error

I'm testing it with this PR: ignitionrobotics/ign-rendering#376
Without these changes, I get the VERSION_LESS cmake error

I'm not able to reproduce the error without these changes :thinking: I built a workspace with the ign-cmake2 branch and https://github.com/ignitionrobotics/ign-rendering/pull/376. are there certain ogre packages I should/should not have installed? I installed all of the dependencies listed in https://github.com/ignitionrobotics/ign-rendering/blob/ign-rendering3/.github/ci/packages.apt, which includes libogre-1.9-dev and libogre-2.1-dev.

I'm not able to reproduce the error without these changes

hmm I just rebuilt my workspace and I can't reproduce it now too..
But I think we may run into this error with no ogre debs installed in the system though.

I think that the changes in the PR make sense. I'd just like to be able to test locally if possible in order to avoid new breaks that we might not be aware of. But, maybe it's difficult to create a scenario to test this, I'm not sure.


in javascript, doing ws.send("test") make the server crash for try_write

with the error  repr: Os(32)  (seems like a broken pipe error)
I know your blog post does not cover it, but I was wondering if you had a clue ?

Hi Allan!
Please let me know, what operating system are you using?

I know your blog post does not cover it
Actually it will be covered in the next part, about bad effects of using unwrap() :)

I'm on ubuntu 14.10 (64 bits) ,  kernel 3.16
Is it because of the one shot flag we put ? i.e the socket get closed after that ?

Problem is fixed, now ws.send is handled correctly.

awesome, thanks


feat(manifests): add json schema for abi

I looked into using the manifest/wrap.info/abi inside of the schema pipeline directly, but it is a bit complicated... I think we should create a new PR after this is merged to consolidate these definitions and only use the manifest's ABI.

I will push this forward


Improvements/expand acceptence tests

Codecov Report

Merging #508 into master will decrease coverage by 0.02%.
The diff coverage is 95.23%.

@@             Coverage Diff              @@
##             master     #508      +/-   ##
============================================
- Coverage     99.43%   99.41%   -0.03%
- Complexity     1232     1233       +1
============================================
  Files           209      209
  Lines          3926     3933       +7
  Branches        209      209
============================================
+ Hits           3904     3910       +6
  Misses            5        5
- Partials         17       18       +1

Impacted Files
Coverage Δ
Complexity Δ

...orum/tessera/transaction/PayloadPublisherImpl.java
95.83% <0%> (-4.17%)
4 <0> (ø)

...in/java/com/quorum/tessera/api/ConfigResource.java
100% <100%> (ø)
5 <1> (+1)
:arrow_up:

...va/com/quorum/tessera/api/TransactionResource.java
100% <100%> (ø)
14 <2> (ø)
:arrow_down:

...um/tessera/transaction/TransactionManagerImpl.java
100% <100%> (ø)
23 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Prelude split into multiple files

Now the Prelude is split into several files. The two most notable files are Base/Types with some standard types and Base/Operators with some standard operators. Each of other files contains only methods that should be visible without importing anything. There is no Base/List file with standard methods on list. The user must import List module by himself.
Other minor changes are the following:

Added LICENSE header in each library file
Added comparison operators for Bool type
Removed makeString method (function?), as it seemed broken.

Fixes #129 and #132

One things that struck out are, it's really hard to test functions that use `re implicit.

Yes, I also noticed that. There is a separate issue on that (#131).


Server filtering incompatible with meta values

As of LuckPerms-Sponge-4.3.17 build 795, meta assigned to current server aren't recognized.
Only meta assigned globally appears to be working.
Server is set to skyadventures:
/lp info
[LP] Running LuckPerms v4.3.17 by Luck.
[LP] -  Platform: Sponge
[LP] -  Server Brand: SpongeForge
[LP] -  Server Version:
[LP] -  SpongeAPI: 7.1.0-70763aa8 - SpongeForge: 1.12.2-2768-7.1.3-RC3498
[LP] -  Storage:
[LP] -     Type: MySQL
[LP] -     Ping: 1ms
[LP] -     Connected: true
[LP] -  Messaging: Sql
[LP] -  Instance:
[LP] -     Static contexts: skyadventures
[LP] -     Online Players: 2 (2 unique)
[LP] -     Uptime: 29m 1s
[LP] -     Local Data: 5 users, 19 groups, 2 tracks

In that same server context (skyadventures), a skyclaims.default-schematic meta is defined for SkyClaims:
/lp group member meta info
[LP] member's Prefixes
[LP] -> 2 - 'Member ' (inherited from self)
[LP] member has no suffixes.
[LP] member's Meta
[LP] -> skyclaims.default-schematic = 'skyadventures' (inherited from self) (server=skyadventures)
[LP] -> skyclaims.min-size = '16' (inherited from self) (server=skyadventures)
[LP] -> rank-ladder = 'staff' (inherited from self)
[LP] -> rank = '1000' (inherited from self)
[LP] -> weight = '99999' (inherited from self)

However, LP returns null for this meta according to verbose output:

Target
Request
Result

lemadec
skyclaims.command.reset
true

lemadec
meta: skyclaims.default-schematic
null

defaults/user
meta: skyclaims.default-schematic
null

defaults/default
meta: skyclaims.default-schematic
null

Now, if I add a global value for same meta with
/lp group member meta set skyclaims.default-schematic test
Then the meta returned is test:

Target
Request
Result

lemadec
skyclaims.command.reset
true

lemadec
meta: skyclaims.default-schematic
test

Did you set the server name in the LP config or in the static contexts?

It sets in the config and /lp info reports it properly.
Not sure what you mean by static contexts here.

Can you send me the actual verbose report please.

https://luckperms.github.io/verbose/#AalBUBCMT1
Looks like you are right on SkyClaims using the global context

Nope, this is indeed a LuckPerms bug. Woops

No clue how that one went unnoticed for so long. I guess because permission checks through Sponge bypass that method via getPermissionValue...
Thanks for finding it :)


Better buffer motions and visual debug guide for free motion planning

This PR includes the following:

previous/next movement-independent buffering linear motions for helping the free motion planner get out of narrow passages, fix #107 , #100 .
Fixed a bug that prevents our MP from using our custom joint limits (specified in integral_timber_joints.planning.robot_steup.get_gantry_robot_custom_limits), now MP can finally sample in the right range. Before it was sampling around the full range, wasting efforts.
Different MP algorithms can be specified by --mp_algorithm rrt or --mp_algorithm prm
Now you can visualize the MP algorithm exploring the space live by: p -m integral_timber_joints.planning.run --design_dir 210419_AnticlasticShelter --problem shelter_process.json --movement_id A51_M1 --mp_algorithm birrt -v --debug --diagnosis --watch --draw_mp_exploration
You can also force birrt to alternate between the two trees for exploration by adding birrt_enforce_alternate

This is amazing~ Thanks for all the new improvements!


Language service reports error on "export import" use

Using the TypeScript 1.6 beta in an AMD project with the following structure:
In one.ts:
export var something = 7;
In two.ts:
export import Something = require("one");
The project compiles successfully, but the language service for Visual Studio 2013 reports an error "Cannot find module 'one'." in two.ts.

@quedelsmith are you sure you're using an AMD project? I'm only able to reproduce this error targetting CommonJS (which is not an error, it's a deliberate breaking change - see #2338).

if you are using --module commonjs and you are running on node, require("one") should be require("./one") instead.
if you are not using node, use --moduleResolution classic.

Yes, my csproj file designates amd for both debug and release.

@paulvanbrenk can you take a look? Does @quedelsmith need to specify something in their csproj to change module resolution? If so, that would seem like a bug.

ooh.. i see the issue now.

The issue is in an inconsistency between the compiler and language service. Doesn't have to do with the project settings. @mhegazy is working on a fix.

This should be fixed in the next release.

Thank you!


Android X upgrade

AndroidX is the replacement for Google Support Libraries. Android P is the transition phase for this. The next version of Android is likely to support only AndroidX. This library fails on android builds that use the new compileSdkVersion. This PR makes the transition to AndroidX.
The only changes in this PR are namespaces, package names in import statements, and Gradle dependencies.
The changes in this PR were auto-generated by Android Studio using instructions from here.

Closed by #54


Make "Search docs" localizable

First of all, thanks a lot for making the cleanest DokuWiki template! It saved me a lot of headache for a mobile-first site.
I'm using it for a non-English project and while the administration parts can stay in English, I wish there was some way to change "Search docs" in
https://github.com/my17560/dokuwiki-template-readthedokus/blob/1bff756b542066826c09f3eac02839502477d376/js/readthedokus.js#L77
…aside from editing the .js file directly.
I wish I could just make a pull request, but I'm quite weak in web development to understand how to pull translation data from PHP to a JS script without increasing page loading time.
Also it would be great if you can provide a Ko-Fi or PayPal for donations on the plugin page. Thank you for your work!
UPD: another texts I've found are "Previous", "Next" in the page footer and "Docs" and "Edit this page" in its header – I can edit these templates directly but I think it will not work for multilingual wikis.

Hi, I'm glad to hear the theme saved your headache. I've updated the theme on GitHub, not the DokuWiki template site yet,  so press "Re-install" in Extension Manager.
You need to prepare your language file called "lang.php". Please reference English lang.php in "lib/tpl/readthedokus/lang/en/lang.php" and you need only the last 6 lines for non-admin pages.
Place the lang.php in either:
lib/tpl/readthedokus/lang//
or
conf/template_lang/readthedokus//
If you would like me to add your lang.php to my theme, please give me your file and I'll gladly add it to my theme.
Note: Whenever you update the lang.php, update lib/tpl/readthedokus/script.js also (just save without editing) or translations will not be applied. Exactly speaking, you need to do so only when you edit $lang['js']['searchform_placeholder'] line.
Thanks for your donation offer. I'll add a link on GitHub.

Many thanks! I'll add Spanish and Russian localizations to my todo-list and make a PR later.

Hi, I'm closing this issue for now. Please re-open or throw a new issue anytime if you want!


Alternative Table & App Linking

PR for issue #170: Alternative tables and app linking
Task-breakdown:

[ ] Create a Table._baseTable during the schema introspection taking  tag:isrd.isi.edu,2016:table-alternatives annotation into account. If there is no annotation, the base table points to its own table. This needs to be done after all the tables have been created and all the foreign keys are built. All constraints above should be checked.

[ ] check table alternative constraints. If fail, ignore the annotation.

[ ] The base table and all participating alternative tables must have not-null unique constraints.
[ ] Each alternative table must have exactly one not-null unique key which is a foreign key to the base table. This implies that an alternative table has exactly one base-table. (Alternative table can have more than one key, but only one that map to the base table. For our current use case, we are allowing exactly one foreign key).
[ ] All alternative tables associated with the base table have not-null unique keys that are foreign keys to the SAME primary keys of the base table. We could do this by iterate through all not-null unique keys of the base-table, and check whether all alternative tables have foreign keys pointing to it.
[ ] There is no in-bound foreign keys to the alternative tables.
[ ] a base table cannot be an alternative table for other base tables (i.e. flat 2-level forest) e.g. a base table cannot have ._baseTable that is not itself.

[ ] Modify Tuple by:

[ ] adding Tuple.reference() which returns an un-contextualized reference to get to the entity represented by the tuple. The reference url should be of the form basetable/key=value. We already have this getter, but the context is set to its page.reference.context. Need to modify this to support base table.
[ ] overriding the above reference.read() to use the original tuple._data instead of going to the server to get the same data (if applicable).

[ ] Modify contextualize to take into account the alternative table and base table.

[ ] add a getter to retrieve alternative table (._alternativeTable) for each context using the baseTable. Only the base tables should have this annotation!
[ ] If alternativeTable is defined, create a contextualize reference to the alternativeTable. Otherwise, the contextualization is done at the base table.
[ ] to support the tag:isrd.isi.edu,2016:app-links annotation, add Reference.appLocation object
[ ] When contextualizing a reference, if ._table._baseTable is not ._table (this is an alternative table), use the base table to get the alternative table of that context.

Just made major update to this branch. @robes @hongsudt would you check if it looks ok? Test should cover all the possible cases now.

I made changes according to all the comments except encoding/decoding  (is on a separate issue).


You are trying to run a container which is more than 90 days old.

I can no longer start my container...
Logs
Restarting Container
PublicDnsName unchanged
Hostname is xxx
PublicDnsName is xxx
You are trying to run a container which is more than 90 days old.
Microsoft recommends that you always run the latest version of our containers.
Set the environment variable ACCEPT_OUTDATED to 'Y' if you want to run this container anyway.
at , C:\Run\navstart.ps1: line 52
at , C:\Run\start.ps1: line 38
at , : line 1
Docker inspect
ACCEPT_OUTDATED is no part of my env variables
Trying to update env variable via

docker exec xxx -e ACCEPT_OUTDATED=Y

Error*
container 3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648 encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2) extra info: {"ApplicationName":"","CommandLine":"-e ACCEPT_OUTDATED=Y",...

The intention with Accept_outdated was actually that it should be checked when starting the container and not when restarting.
We really do not want people to be running with old containers.
If you started the container using navcontainerhelper, then the c:\run\my folder is shared with the host and you can use docker cp to copy navstart.ps1 to that - and then remove the check.
Else you need to use docker pull and start a new container.
If you have something in the container you need - you can use docker cp to copy it out.

The container created contains a database that we don't want to lose.
I managed to export the navstart.ps1 from another container, so I can use this file to import in the current container. However, since the container can't be started, it seems to be blocked during startup, so files might be locked as well ...
docker cp c:/myfolder/navstart.ps1 CONTAINERNAME:/run/navstart.ps1 (or even another destination /run/my folder/...)
Error response from daemon: hcsshim::ActivateLayer failed in Win32: The process cannot access the file because it is being used by another process. (0x20) id=3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648 flavour=1
How can I get access to the contents (at least the database) of my container when I'm not able to start it?
PS: Will there be an update not to block the restarting of the container once created?

Update: I stopped the container and ran the following without error
docker cp c:/myfolder/navstart.ps1 vives2017:/run/my/navstart.ps1
Although now I get following error when starting the container ...
Error response from daemon: container 3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648 encountered an error during CreateContainer: failure in a Windows system call: The directory is not empty. (0x91) extra info: {"SystemType":"Container","Name":"3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648","Owner":"docker","IsDummy":false,"VolumePath":"\\?\Volume{c453529a-f183-11e7-98ba-c4e38821c171}","IgnoreFlushesDuringBoot":false,"LayerFolderPath":"C:\ProgramData\docker\windowsfilter\3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648","Layers":[{"ID":"61a472f6-5fc5-5f2d-9b40-e7cbb8f51a5f","Path":"C:\ProgramData\docker\windowsfilter\3ac9f5b0ce3ed43ae9334fb86993912b38b4212aec6b09e58710b5e606f5e086"},{"ID":"2b10f442-62a4-5ed1-ad9c-885ae5c27a8e","Path":"C:\ProgramData\docker\windowsfilter\15d0a5d914332582432c241699a862ab34f18076642e16ed89c2b47a6b2b192e"},{"ID":"f4a0b4bc-dc2b-5723-9cc0-2d2be8527886","Path":"C:\ProgramData\docker\windowsfilter\f94883d92fa4c6719ec83c5fe01884fd0ec59c1eb4c2a5a8159a510a9444d88c"},{"ID":"e1a72cb7-e980-5fcd-9de8-2b4d479c0829","Path":"C:\ProgramData\docker\windowsfilter\28d3faef96b63fff940d3b06abb28c6d4132780fb95de9f81a64fa84ca19386c"},{"ID":"746fe5fe-cceb-5058-b729-320ea01cb8f1","Path":"C:\ProgramData\docker\windowsfilter\a3e8453b2c97d02e53124ed1206e40474ed5e1cbaffcf8057fe9b6373d82d636"},{"ID":"4e750792-75db-5281-9dd1-cb42ee7574ad","Path":"C:\ProgramData\docker\windowsfilter\d8a2a5d4c668f612ba41e2b55e5c488b3dd36b3b31b800816575f71abdb8ed40"},{"ID":"a4ff1c87-17ba-5185-8ca4-6dd26bbfd4a1","Path":"C:\ProgramData\docker\windowsfilter\38d043ed204b6e4466a44246c1bf0dc96760873fa755066d73a1ea028e26b565"},{"ID":"cfa013a7-3e78-5810-b52f-4119cbbc4852","Path":"C:\ProgramData\docker\windowsfilter\a6a162065e3d6abf96b6f75fae02ceebd33e1bc43e11a05a6111f94f9c65e13d"},{"ID":"9e593dc2-7609-5d26-974a-8a14307dbef4","Path":"C:\ProgramData\docker\windowsfilter\0f76d4623e010681d9d5cee040d087242437864ecefda7abaafc076139d72766"},{"ID":"239a6deb-e0a9-5ef6-8890-a6e805ea8569","Path":"C:\ProgramData\docker\windowsfilter\db00d4ab89fb65867b15c7380d0c06ca9ccba128443986deb4412581f3786a3c"},{"ID":"3750d03d-ac30-5f83-9972-7f46d64ff54e","Path":"C:\ProgramData\docker\windowsfilter\93f42a6d90f9567ba455b1319f6508cd2fe8c27e6e1c0eb3d816194ab6c027b5"},{"ID":"092415ec-6981-561b-af74-06c608c41d52","Path":"C:\ProgramData\docker\windowsfilter\fcf2e91cc1e243addbc6cecccde51e696d22b5127c87beb396b5e6130e3c85df"},{"ID":"83cd030d-218b-502b-b890-792820ae0555","Path":"C:\ProgramData\docker\windowsfilter\76b6adbd6b1562dcb65f6823acf8013d3c90912f646b5a83d6f7783d3d681777"},{"ID":"90a074c0-7dff-5414-b759-decfdf834314","Path":"C:\ProgramData\docker\windowsfilter\18e3fbaa7252c6ebc301fc48aa5b7b63c16f9d02e63c88bfa83f0ea4f62aca36"},{"ID":"4b40b9f4-dec3-5031-9f8f-c6df8ad02d3f","Path":"C:\ProgramData\docker\windowsfilter\33bcad49e936c34b5ea1c12fddefefe6ce144ec79aa552777c25cde24ec1fbdc"},{"ID":"03e188c7-89d7-5b96-b994-5c1609a68191","Path":"C:\ProgramData\docker\windowsfilter\8f28c05713b0446f5c82242bae0b0d55c40a50260c1b9bee442204904e8fbaca"},{"ID":"d65ed84b-ade9-5953-b17c-1e82a0124d94","Path":"C:\ProgramData\docker\windowsfilter\60d8a9c49510e157c6947d2ab55188836977df9babecc1d9b265592c6ff6b11e"},{"ID":"cd14d8ef-9b9b-59f3-9089-5494d88da5ff","Path":"C:\ProgramData\docker\windowsfilter\4801dbbb258c2b27f21de946129219e442fd9f75df76fa96e1b798c0966c2da4"},{"ID":"4e9cb09b-8cf5-58ec-9d65-31c11f14f3af","Path":"C:\ProgramData\docker\windowsfilter\ee6d4d626637f2b1c2265b174ef09b9ba87111b3ad36ff712bf65f937aab57ca"},{"ID":"f8a4d4fc-1fb2-5424-91ca-e16227b84cb6","Path":"C:\ProgramData\docker\windowsfilter\41faef6c90ffc3d6ad981a450aadb9d8ca8306a700055a94b2b42ede23d0da5c"},{"ID":"21a1885c-ad71-5298-be2f-10e074ae37a2","Path":"C:\ProgramData\docker\windowsfilter\c788d518b380fb21429c1d16bb25cf7c88664217e2aea1af9e8bc40c2dea4d30"},{"ID":"5cc1f2d7-2f93-500d-b819-d949b5b01f67","Path":"C:\ProgramData\docker\windowsfilter\17bd31fcb92cf5aa690c6520e1961b44ea053b7ed0fd61059bbc3863848789bb"}],"MemoryMaximumInMB":3072,"HostName":"xxx2017","MappedDirectories":[{"HostPath":"c:\windows\system32\drivers\etc","ContainerPath":"c:\driversetc","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper\extensions\xxx2017\program files","ContainerPath":"c:\navpfiles","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper\extensions\xxx2017\my","ContainerPath":"c:\run\my","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper","ContainerPath":"c:\programdata\navcontainerhelper","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0}],"HvPartition":false,"EndpointList":["5e088979-c296-4621-a402-24cb9a60aeb9"],"Servicing":false,"AllowUnqualifiedDNSQuery":false}
Error: failed to start containers: xxx2017

I asked wether how you started the container in order to understand if you had a shared my folder.
Based on this, I don’t think you had - and you might have ruined the file system now.
If you didn’t have a my folder you should just override the file in run with docker cp.
Now try to copy mdf and ldf files out with docker cp then you can copy them into another container.
Få Outlook til iOShttps://aka.ms/o0ukef

From: Frédéric Vercaemst<EMAIL_ADDRESS>Sent: Friday, March 9, 2018 5:48:27 PM
To: Microsoft/nav-docker
Cc: Freddy Kristiansen; Comment
Subject: Re: [Microsoft/nav-docker] You are trying to run a container which is more than 90 days old. (#171)
Update: I stopped the container and ran the following without error
docker cp c:/myfolder/navstart.ps1 vives2017:/run/my/navstart.ps1
Although now I get following error when starting the container ...
Error response from daemon: container 3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648 encountered an error during CreateContainer: failure in a Windows system call: The directory is not empty. (0x91) extra info: {"SystemType":"Container","Name":"3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648","Owner":"docker","IsDummy":false,"VolumePath":"\?\Volume{c453529a-f183-11e7-98ba-c4e38821c171}","IgnoreFlushesDuringBoot":false,"LayerFolderPath":"C:\ProgramData\docker\windowsfilter\3e6ac9659247f04d6c061245338c793ba1b90b3e797c9c681490dfce5dda5648","Layers":[{"ID":"61a472f6-5fc5-5f2d-9b40-e7cbb8f51a5f","Path":"C:\ProgramData\docker\windowsfilter\3ac9f5b0ce3ed43ae9334fb86993912b38b4212aec6b09e58710b5e606f5e086"},{"ID":"2b10f442-62a4-5ed1-ad9c-885ae5c27a8e","Path":"C:\ProgramData\docker\windowsfilter\15d0a5d914332582432c241699a862ab34f18076642e16ed89c2b47a6b2b192e"},{"ID":"f4a0b4bc-dc2b-5723-9cc0-2d2be8527886","Path":"C:\ProgramData\docker\windowsfilter\f94883d92fa4c6719ec83c5fe01884fd0ec59c1eb4c2a5a8159a510a9444d88c"},{"ID":"e1a72cb7-e980-5fcd-9de8-2b4d479c0829","Path":"C:\ProgramData\docker\windowsfilter\28d3faef96b63fff940d3b06abb28c6d4132780fb95de9f81a64fa84ca19386c"},{"ID":"746fe5fe-cceb-5058-b729-320ea01cb8f1","Path":"C:\ProgramData\docker\windowsfilter\a3e8453b2c97d02e53124ed1206e40474ed5e1cbaffcf8057fe9b6373d82d636"},{"ID":"4e750792-75db-5281-9dd1-cb42ee7574ad","Path":"C:\ProgramData\docker\windowsfilter\d8a2a5d4c668f612ba41e2b55e5c488b3dd36b3b31b800816575f71abdb8ed40"},{"ID":"a4ff1c87-17ba-5185-8ca4-6dd26bbfd4a1","Path":"C:\ProgramData\docker\windowsfilter\38d043ed204b6e4466a44246c1bf0dc96760873fa755066d73a1ea028e26b565"},{"ID":"cfa013a7-3e78-5810-b52f-4119cbbc4852","Path":"C:\ProgramData\docker\windowsfilter\a6a162065e3d6abf96b6f75fae02ceebd33e1bc43e11a05a6111f94f9c65e13d"},{"ID":"9e593dc2-7609-5d26-974a-8a14307dbef4","Path":"C:\ProgramData\docker\windowsfilter\0f76d4623e010681d9d5cee040d087242437864ecefda7abaafc076139d72766"},{"ID":"239a6deb-e0a9-5ef6-8890-a6e805ea8569","Path":"C:\ProgramData\docker\windowsfilter\db00d4ab89fb65867b15c7380d0c06ca9ccba128443986deb4412581f3786a3c"},{"ID":"3750d03d-ac30-5f83-9972-7f46d64ff54e","Path":"C:\ProgramData\docker\windowsfilter\93f42a6d90f9567ba455b1319f6508cd2fe8c27e6e1c0eb3d816194ab6c027b5"},{"ID":"092415ec-6981-561b-af74-06c608c41d52","Path":"C:\ProgramData\docker\windowsfilter\fcf2e91cc1e243addbc6cecccde51e696d22b5127c87beb396b5e6130e3c85df"},{"ID":"83cd030d-218b-502b-b890-792820ae0555","Path":"C:\ProgramData\docker\windowsfilter\76b6adbd6b1562dcb65f6823acf8013d3c90912f646b5a83d6f7783d3d681777"},{"ID":"90a074c0-7dff-5414-b759-decfdf834314","Path":"C:\ProgramData\docker\windowsfilter\18e3fbaa7252c6ebc301fc48aa5b7b63c16f9d02e63c88bfa83f0ea4f62aca36"},{"ID":"4b40b9f4-dec3-5031-9f8f-c6df8ad02d3f","Path":"C:\ProgramData\docker\windowsfilter\33bcad49e936c34b5ea1c12fddefefe6ce144ec79aa552777c25cde24ec1fbdc"},{"ID":"03e188c7-89d7-5b96-b994-5c1609a68191","Path":"C:\ProgramData\docker\windowsfilter\8f28c05713b0446f5c82242bae0b0d55c40a50260c1b9bee442204904e8fbaca"},{"ID":"d65ed84b-ade9-5953-b17c-1e82a0124d94","Path":"C:\ProgramData\docker\windowsfilter\60d8a9c49510e157c6947d2ab55188836977df9babecc1d9b265592c6ff6b11e"},{"ID":"cd14d8ef-9b9b-59f3-9089-5494d88da5ff","Path":"C:\ProgramData\docker\windowsfilter\4801dbbb258c2b27f21de946129219e442fd9f75df76fa96e1b798c0966c2da4"},{"ID":"4e9cb09b-8cf5-58ec-9d65-31c11f14f3af","Path":"C:\ProgramData\docker\windowsfilter\ee6d4d626637f2b1c2265b174ef09b9ba87111b3ad36ff712bf65f937aab57ca"},{"ID":"f8a4d4fc-1fb2-5424-91ca-e16227b84cb6","Path":"C:\ProgramData\docker\windowsfilter\41faef6c90ffc3d6ad981a450aadb9d8ca8306a700055a94b2b42ede23d0da5c"},{"ID":"21a1885c-ad71-5298-be2f-10e074ae37a2","Path":"C:\ProgramData\docker\windowsfilter\c788d518b380fb21429c1d16bb25cf7c88664217e2aea1af9e8bc40c2dea4d30"},{"ID":"5cc1f2d7-2f93-500d-b819-d949b5b01f67","Path":"C:\ProgramData\docker\windowsfilter\17bd31fcb92cf5aa690c6520e1961b44ea053b7ed0fd61059bbc3863848789bb"}],"MemoryMaximumInMB":3072,"HostName":"xxx2017","MappedDirectories":[{"HostPath":"c:\windows\system32\drivers\etc","ContainerPath":"c:\driversetc","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper\extensions\xxx2017\program files","ContainerPath":"c:\navpfiles","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper\extensions\xxx2017\my","ContainerPath":"c:\run\my","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0},{"HostPath":"c:\programdata\navcontainerhelper","ContainerPath":"c:\programdata\navcontainerhelper","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0}],"HvPartition":false,"EndpointList":["5e088979-c296-4621-a402-24cb9a60aeb9"],"Servicing":false,"AllowUnqualifiedDNSQuery":false}
Error: failed to start containers: xxx2017
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fnav-docker%2Fissues%2F171%23issuecomment-371869569&data=04|01|freddy.kristiansen%40microsoft.com|f7dee80ba8b8447e969608d585dd9635|72f988bf86f141af91ab2d7cd011db47|1|0|636562109114112441|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-2&sdata=t0y8SorWxAOLbYI5Wq6fvX7yLwpMM53WYruS06qikVA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKRqA3kOWXCyV2Aopr_gvk7I37NeBZdkks5tcrJbgaJpZM4SkHFp&data=04|01|freddy.kristiansen%40microsoft.com|f7dee80ba8b8447e969608d585dd9635|72f988bf86f141af91ab2d7cd011db47|1|0|636562109114112441|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-2&sdata=n%2BM%2BiVmQvx8HoOdIOxwqDAWcYacXJmfdDe2lwtn3WdA%3D&reserved=0.

I created the container using the standard 'New-CSideDevContainer' commandlet, so I'm ot sure if I actually had a 'my' folder.
When I'm using the docker cp command (when the container is not started, since it can't) to copy the C:\Database\CronusBE mdf and ldf files, I seem to get the standard Cronus files (from the image?), not containing any of the modified objects / data.
I'm quit blocked in getting my databases back currently :(

If you managed to get the cronusbe files out - then you have the right files. If they dont contain the objects, then the objects wasn't in that container.
(if you indeed are running BE)
docker inspect will tell you about the shared folders.

Next rebuild of images will not check for container age when restarting.
It will disallow you to start new containers which are outdated.
Note, that the containers start writing out warnings after 60 days.


[Snyk] Upgrade @graphprotocol/graph-cli from 0.60.0 to 0.61.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @graphprotocol/graph-cli from 0.60.0 to 0.61.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 8 versions ahead of your current version.
The recommended version was released 21 days ago, on 2023-11-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f92ffc6) 77.90% compared to head (0a918b3) 77.90%.

:exclamation: Current head 0a918b3 differs from pull request most recent head 016e6a0. Consider uploading reports for the commit 016e6a0 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1947   +/-   ##
=======================================
  Coverage   77.90%   77.90%
=======================================
  Files          39       39
  Lines        3064     3064
  Branches      617      617
=======================================
  Hits         2387     2387
  Misses        484      484
  Partials      193      193

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


new function: grabbing data from zenodo

I think it'd be useful to implement this function:

https://github.com/HedvigS/Oceanic_computational_ASR/blob/main/code/fun_def_get_zenodo.R

example of use here:

https://github.com/HedvigS/Oceanic_computational_ASR/blob/main/code/02_get_zenodo_dirs.R

Or this could be over in rcldf: https://github.com/SimonGreenhill/rcldf/pull/30

this is now in rcldf for downloading cldf releases -- but why did you want to download a bunch of old grambank analyses?

this is now in rcldf for downloading cldf releases -

Great :)!

but why did you want to download a bunch of old grambank analyses?

I don't understand the question. Colleagues who are working with grambank data often need to fetch data and are fetching it in non-optimal ways with moving derived files around. Explicitly fetching a particular version of cldf data from the internet seems smart and explicit to me. Then the code says exactly what version and the workflow is clear from data input to analysis and plotting etc.


Upgrade to recoil to version 0.0.13

This will help improve typing and fix several runtime warnings.
It may affect some of the dispatch calls and require a little refactoring.
@boydc2014 and @srinaath - @hatpick has been looking into this. @cwhitten mentioned that upgrades should generally be considered  platform work so to include you, but that recoil is the area where platform and authoring meet :-)  We could set up a feature branch to work through the upgrade together.

@GeoffCoxMSFT Do we know the date for the 0.0.13 release? Recoil released 0.0.12 5 days ago.

@srinaath it's already released https://www.npmjs.com/package/recoil
Their github releases page seems outdated

Thanks @GeoffCoxMSFT, i think we can an assessment and assignment in tomorrow's sync up

I put Leilei and Srinaath for now.


Issue-4949 feed version of the charts through flags while linting

Things done:

The chart version can be set through cli flag while linting
ie: helm lint chart_name --version=1.0
The validation on charts templates is taken out from LoadFiles (pkg->chart->loader->load.go), so that the templates can be loaded first, then version can be set if provided through flags(params) and then the validation function can be ran. This lead to refactoring in many places.

Changing on the ChartLoader interface
type ChartLoader interface {
	Load(version string) (*chart.Chart, error)
}

will also lead to changes in many places, so thought of getting the validation function outside of LoadFiles.
Signed-off-by: openmohan<EMAIL_ADDRESS>

Fixed the bug-4949 for helm v3.
@bacongobbler

closing as #4949 was closed as a wontfix, so we will not be accepting any PRs attempting to address this.


Cplex error 1016: Community edition. Problem size limits exceeded.

Hi, I'm facing this issue when I tried to carve model with CarveMe, it showed error saying that
CPLEX Error  1016: Community Edition. Problem size limits exceeded. Purchase at https://ibm.co/2s0wqSa.
Fyi, I downloaded the IBM ILOG CPLEX Optimization Studio V12.9.0 academic version from the IBM website. I'm using MacOS. Please help me with this issue. Thank you so much.
Full error message as below:
Reported 65972 pairwise alignments, 65974 HSPs.
2585 queries aligned.
Traceback (most recent call last):
File "/Users/karenchung/miniconda3/bin/carve", line 364, in
ref_score=args.reference_score
File "/Users/karenchung/miniconda3/bin/carve", line 210, in main
debug_output=debug_output)
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/carveme/reconstruction/carving.py", line 236, in carve_model
ref_reactions=ref_reactions, ref_score=ref_score, debug_output=debug_output)
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/carveme/reconstruction/carving.py", line 184, in minmax_reduction
solution = solver.solve()
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/framed/solvers/cplex_interface.py", line 308, in solve
problem.solve()
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/cplex/init.py", line 1225, in solve
_proc.mipopt(self._env._e, self._lp)
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/cplex/_internal/_procedural.py", line 760, in mipopt
check_status(env, status)
File "/Users/karenchung/miniconda3/lib/python3.7/site-packages/cplex/_internal/_procedural.py", line 303, in call
raise CplexSolverError(error_string, env, status)
cplex.exceptions.errors.CplexSolverError: CPLEX Error  1016: Community Edition. Problem size limits exceeded. Purchase at https://ibm.co/2s0wqSa.

Hi.
Did you uninstall your previous version of cplex and did you follow the instructions in https://www.ibm.com/support/knowledgecenter/SSSA5P_12.9.0/ilog.odms.cplex.help/CPLEX/GettingStarted/topics/set_up/Python_setup.html to install the python wrappers for CPLEX 12.9 ?

Hi,
May I know how do I specifically install the previous version of cplex?
And, yes, I did follow the instructions to install the python setup.py . But did not do the setting the environment variable PYTHONPATH. Not quite understand on that.
Could you guide? Thank you so much.

To fix your environment:

Open a terminal
make sure that your python tools are the one from your miniconda3. The best way would be to:

$ source /Users/karenchung/miniconda3/bin/activate

Uninstall previous version of cplex:

$ pip uninstall cplex

Install new version of cplex:

$ cd $CPLEX_STUDIO_DIR129/python/3.7/x86-64_osx
$ python setup.py install

Hi, when I tried to uninstall cplex, below occurred:
pip uninstall cplex
Found existing installation: cplex <IP_ADDRESS>
ERROR: Cannot uninstall 'cplex'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

This means that it has been installed with an older version of pip.
Please upgrade your version of pip. In your anaconda3 env:
pip install -U pip

then:
$ cd $CPLEX_STUDIO_DIR129/python/3.7/x86-64_osx
$ pip install --ignore-installed .

After I did  pip install -U pip , it showed
pip install -U pip
Requirement already up-to-date: pip in ./miniconda3/lib/python3.7/site-packages (20.1.1)
Next I used command rm -rf /Users/karenchung/miniconda3/lib/python3.7/site-packages/cplex ,
then
cd applications/cplex/cplex/python/3.7/x86-64_osx
(base) Karens-MacBook-Air:x86-64_osx karenchung$  python setup.py install
Then tried to carve model again, problem still occurred.
To add on,
which pip
/Users/karenchung/miniconda3/bin/pip
which python
/Users/karenchung/miniconda3/bin/python

Also, when I cd applications/cplex/cplex/python/3.7/x86-64_osx  and insert command pip install --ignore-installed below occurred:
(base) Karens-MacBook-Air:x86-64_osx karenchung$ pip install --ignore-installed
ERROR: You must give at least one requirement to install (see "pip help install")

you are missing a dot in the command line .:
$ pip install --ignore-installed .

Sorry, I tried, problem still occurred. Attached herewith the full output file.
output.docx

There are much error possibilities in your program, and you don't provide me with enough details.
I can only guess, so please provide me the following informations:

You run your program as carve. What is this ? How this has been created ? is that a shell script ? is that an executable ?

I'd also like to check your cplex version. Can you please run this:

$ /Applications/CPLEX/cplex/bin/x86-64_osx/cplex

This should display something like:

Welcome to IBM(R) ILOG(R) CPLEX(R) Interactive Optimizer <IP_ADDRESS>
  with Simplex, Mixed Integer & Barrier Optimizers
5725-A06 5725-A29 5724-Y48 5724-Y49 5724-Y54 5724-Y55 5655-Y21
Copyright IBM Corp. 1988, 2019.  All Rights Reserved.

Please provide me the output of this.

Then I need also the value of your $PATH, $LD_LIBRARY_PATH, $DYLD_LIBRARY_PATH and $PYTHON_PATH.

I am using CarveMe. CarveMe is a python-based software, and carve is an executable.
Below is the link of CarveMe tutorial for your information:

https://carveme.readthedocs.io/en/latest/installation.html
https://carveme.readthedocs.io/en/latest/usage.html

Welcome to IBM(R) ILOG(R) CPLEX(R) Interactive Optimizer Community Edition <IP_ADDRESS>
with Simplex, Mixed Integer & Barrier Optimizers
5725-A06 5725-A29 5724-Y48 5724-Y49 5724-Y54 5724-Y55 5655-Y21
Copyright IBM Corp. 1988, 2019.  All Rights Reserved.

Sorry, I'm not sure how to do this. Could you guide?

path output.docx

In your cplex output:
Welcome to IBM(R) ILOG(R) CPLEX(R) Interactive Optimizer **Community Edition <IP_ADDRESS>**
with Simplex, Mixed Integer & Barrier Optimizers

The cplex you have in /Applications/CPLEX/cplex/bin/x86-64_osx/cplex is a community edition.
It is limited to 1000 variables/ constraints.
This is not the academic version.
Please download and install the academic version from this link: https://www.ibm.com/academic/technology/data-science

So sorry for that I didn't realize this. I'm requesting my supervisor to request for the installation of academic version.
Will come back again to update on this (if that could solve my issue).
I'm so sorry again for the trouble caused. And thank you so much for the time taken!

Hi, I've downloaded another version of cplex.
**$ /Applications/CPLEX_Studio1210/cplex/bin/x86-64_osx/cplex
Welcome to IBM(R) ILOG(R) CPLEX(R) Interactive Optimizer <IP_ADDRESS>
with Simplex, Mixed Integer & Barrier Optimizers
5725-A06 5725-A29 5724-Y48 5724-Y49 5724-Y54 5724-Y55 5655-Y21
Copyright IBM Corp. 1988, 2019.  All Rights Reserved.**
I tried to run and the error 1016 still persisted.
The previous community version is still in system.
Community version directory: /Applications/cplex
Latest download version directory: /Applications/CPLEX_Studio1210
May I know what should I do next?

I registered as academic initiative to download the academic version and it led me to here (please see attached) and I selected for IBM ILOG CPLEX Optimization Studio V12.10 for OSX Multiplatform Multilingual (CC43DML )

Did you install your new wrappers ?
$ source /Users/karenchung/miniconda3/bin/activate
$ cd /Applications/CPLEX_Studio1210/cplex/python/3.7/x86-64_osx
$ pip install --ignore-installed .

After I installed the new wrappers and run carve, now it pop different error.
TypeError: not a list
Attached herewith full output of command and carve run output.
Command & carve output.docx

Now that you got your cplex working, the support for your error should be handled by CPLEX support (which I'm not part of) or community.
You can try on IBM Decision Optimization community https://community.ibm.com/community/user/datascience/communities/community-home/digestviewer?communitykey=ab7de0fd-6f43-47a9-8261-33578a231bb7&tab=digestviewer  or on https://or.stackexchange.com/questions/tagged/cplex (people from CPLEX team answer to questions to those forum).
However, note that for CPLEX support to have a look at your issue, you will need to be able to provide either a .lp model file or some python that uses only CPLEX. From what I see in your logs, it is not clear wether the problem is due to CPLEX or CarveMe - I would say the problem is in CarveMe, since you did not have this problem with CPLEX 12.9 - Maybe CarveMe does not support CPLEX 12.10 ? Without a sample using only CPLEX code, I cannot diagnose this.
Thanks

Hi,
Thank you so much for assisting me to solve my previous issue.
Now with this issue, I googled it, read from CarveMe support that it is the CarveMe issue that does not support CPLEX 12.10. The current stable version of CarveMe supports CPLEX 12.7 with Python 3.6.
May I ask again, how could I downgrade the CPLEX to lower version, 12.7 ?

Hi,
Extracted from this page https://community.ibm.com/community/user/datascience/blogs/xavier-nodet1/2020/07/09/cplex-free-for-students :
On the Academic Initiative website, you will find a direct link to download the latest version of CPLEX Optimization Studio. But other versions are available as well. In order to get an older version, please follow these steps:

Click on the direct link as if you wanted to download the latest version. This opens a page titled “Find by part number results”.
On the left of the page, click on link “Search for software”.
In the “Product name” field of the section “Find by search text”, enter “CPLEX Optimization Studio”.
This will show you all the versions of CPLEX Optimization Studio that can be downloaded. Click their names to show the available platforms.

If you need a very old version of CPLEX Optimization Studio that you can’t find on the Academic Initiative website, please send an email to<EMAIL_ADDRESS>specifying what version you need and for which platform (Windows, Linux, macOS). Please make sure you send any such email from the same address as you used to register in the AI program, and that you explain why you need a version of the software that’s not a more recent one.

I downloaded the Cplex 12.7, however the file is bin file. I can't open it with The Unarchiver. Could you advise?

Hi,
I'm sorry but I'm not familiar with osx distributions for CPLEX. Please contact<EMAIL_ADDRESS>Thanks

Hi,
Thank you for that, I will contact with the IBM support team.
Thank you so much for your help on the issue!


Implement place card logic

Description
One should be able to place a card on a slot on the game board.
Acceptance criteria

Slots are created on the board (goalkeeper, defenser, midfielder, attacker)
User can drag and drop its card on a slot

can i pick this? @LucasLvy


Wrong API is called by AZ cmd "az ad sp credential list"

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
By running "az ad sp credential list", we find Rest API "https://graph.chinacloudapi.cn// applications //passwordCredentials" is called, which make it returns credential of application rather than that of service principal.
DEBUG: msrest.http_logger: Request URL: 'https://graph.chinacloudapi.cn/954ddad8-xxxx152d9587/applications/4c142b1f-xxxxx1cc81f2f/passwordCredentials?api-version=1.6'
DEBUG: msrest.http_logger: Request method: 'GET'
Compared with the powershell command "Get-AzADSpCredential", the API called is https://graph.chinacloudapi.cn//servicePrincipals//passwordCredentials, which is the correct one.
To Reproduce

az login
az ad sp credential list --id xxxx
Expected behavior

"az ad sp credential list" should provide the credentials of the service principal with API "https://graph.chinacloudapi.cn//servicePrincipals//passwordCredentials" called.
Environment summary
az --version
azure-cli                         2.31.0
core                              2.31.0
telemetry                          1.0.6
Extensions:
ssh                                1.0.0
Additional context

Duplicate of #11458


ws-rtsp-repo_1.3 not work!

http 400 error!

Deb/RPM repositories are temporary closed. You can get proxy package directly from http://streamedian.com


refactor split weight to gateways

Please provide a description of this PR:
This is a refactor of apply weight to multiple network gateway without behavior change.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d784e78df0e13356ca7296f7f9421a6a00d394ca
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d784e78df0e13356ca7296f7f9421a6a00d394ca
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


KAFKA-16598 Mirgrate ResetConsumerGroupOffsetTest to new test infra

Currently, I'm working on the ResetConsumerGroupOffsetTest. I'm a bit puzzled about the parameter bootstrapServers(listenerName()) in the old code. It seems to return localhost:+random port number. My understanding is that in the Scala part of the code, it first creates a broker and then returns the IP and port number of that broker. However, I'm not sure which part of the new testing framework corresponds to this parameter. Currently, I'm using ClusterInstance, but in the subsequent segment consumerGroupCommand.collectGroupState(group).coordinator.host(), it times out.

Hey @m1a2st , the way to get the servers' addresses is cluster.bootstrapServers(), you got it right, but I see you're not inheriting from ConsumerGroupCommandTest anymore, so that removes the creation of the brokers to run the test against (that happens in the base setup here). Could that be what you're missing?

@m1a2st Please add following server property:
@ClusterTestDefaults(clusterType = Type.ALL, serverProperties = {
    @ClusterConfigProperty(key = GroupCoordinatorConfig.OFFSETS_TOPIC_PARTITIONS_CONFIG, value = "1"),
    @ClusterConfigProperty(key = GroupCoordinatorConfig.OFFSETS_TOPIC_REPLICATION_FACTOR_CONFIG, value = "1")
})

The default replica of offset topic is 3, and the new infra create single broker. Hence, creating offset topic get failed, and hence you can't find a coordinator as the offset partition can't get be ready.
Also, please notice @lianetm comments that bootstrap servers need to be updated manually if you kill any broker.

@lianetm @chia7712  Thanks for your comment.

Rely on #15766

@chia7712 , please take a look for this PR, thank you

@m1a2st Could you please use ConsumerGroupCommandTestUtils#generator to rewrite this test? thanks!
https://github.com/apache/kafka/blob/trunk/tools/src/test/java/org/apache/kafka/tools/consumer/group/ConsumerGroupCommandTestUtils.java#L50

@m1a2st Could you please make sure "all" available consumer groups are included in this test? For example: produceConsumeAndShutdown creates consumer only for classic.

@chia7712 , Thanks for your review, I have been modify all test for testing different groupProtocol type. Please review again

@chia7712, Thanks for your review, I have been changed according to your conversations.

Build / JDK 17 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 13s
Build / JDK 17 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 14s
Build / JDK 17 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 14s
Build / JDK 17 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 8s
Build / JDK 8 and Scala 2.12 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 25s
Build / JDK 8 and Scala 2.12 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 30s
Build / JDK 8 and Scala 2.12 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 27s
Build / JDK 8 and Scala 2.12 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 31s
Build / JDK 21 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 24s
Build / JDK 21 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 29s
Build / JDK 21 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 22s
Build / JDK 21 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 29s
Build / JDK 11 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 29s
Build / JDK 11 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 40s
Build / JDK 11 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [4] Type=Raft-Combined, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 29s
Build / JDK 11 and Scala 2.13 / testResetOffsetsAllTopicsAllGroups [5] Type=Raft-Isolated, Name=consumerGroupCoordinator, MetadataVersion=3.8-IV0, Security=PLAINTEXT – org.apache.kafka.tools.consumer.group.ResetConsumerGroupOffsetTest1m 35s

@m1a2st Those tests verify all groups so the loop of CLASSIC + CONSUMER in the same cluster makes they failed. Maybe we ought to remove all groups after test. For instance,

            try (Admin admin = cluster.createAdminClient()) {
                admin.deleteConsumerGroups(groups).all().get();
            }

@chia7712 , Thanks for your review, these test passed.

@m1a2st could you please rebase code to trigger QA again?

@chia7712, Thanks for your conversations, I already rebase this code.

@chia7712, Please review, Thanks for your comments.


Highlighting on Python functions is monolithic

Functions, such as the built-in print() statement show the same colour on both the function call, parentheses and the arguments (if the argument is a variable)
Maybe we could change the colour of parentheses or arguments.

Resolved in commit 56631d5


Update index.md

Added information about Azure RBAC, as currently we have only classic subscription administrator roles listed. Also removed inaccurate statement about assignment of individual permissions - we add permissions to roles and then assign the roles to end users in Azure, not individual permissions.

@LazaUK : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@EdPrice-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#Sign-Off

@EdPrice-MSFT: I'm sorry - only the author of this article, @doodlemania2, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[kmac] Ignore entropy refresh requests when running in SW entropy mode

When running in EDN entropy mode, software can manually request the entropy to be refreshed from EDN.
If instead running in SW entropy mode, SW provides the entropy via CSRs. SW is still able to request the entropy to be refreshed. Prior to this commit, the design would then go into the StRandEdn state and request fresh entropy from EDN, but the entropy received from EDN would be ignored. Instead, the LFSR would be reseeded using the value provided by
SW via CSRs. If SW "forgot" to update the CSRs, the LFSR would be reseeded using the same value. This is a bit counter-intuitive and can be exploitet for SCA. It's safer to just ignore these requests when running in SW entropy mode.

Hey @eunchan ,
I am not sure if the SW mode is intended to be used at all or if it's more intended for testing/DV. Anyway, I thought it's probably better to just ignore these refresh requests in SW mode. But no need to merge this if you don't agree.

based on my understanding this looks good to me.
Although this brings up another question... the sw mode seed registers say anytime the lower/upper are written the lfsr seed is updated, but looking at the rtl this does not appear to be the case? Let me know if i read it wrong.
@cindychip

Although this brings up another question... the sw mode seed registers say anytime the lower/upper are written the lfsr seed is updated, but looking at the rtl this does not appear to be the case? Let me know if i read it wrong.

This is also my observation. I believe the SW seed registers are meant to be written only once when KMAC is coming out of reset, then the entropy_ready bit is set which will trigger the loading of the seed into the LFSR. After that point, there is no way for the FSM to get back into the state where the LFSR is reseeded using the SW seed even though the seed register can still be updated. Prior to this PR, the entropy refresh request was the only way to sidestep this, but I think it's probably not intentional.

thanks @vogelpi
@eunchan should we update the csr description a bit to clarify this point?

OK. Let me check the design and update CSR description. :)


Benchmarks: micro benchmarks - add nvbandwidth build

Description
Add nvbandwidth build to repo

Need to clean up the code and will create another pr.


Maxretry: use queue durability setting from new name opts[:queue_options][:durable]

This fixes a problem introduced in 4cf82d5700 where :durable as a general option is now deleted during worker start. This change now uses the new setting.

Build status (as Travis apparently isn't updating PRs): https://travis-ci.org/jondot/sneakers/builds/84281460

Awesome stuff @rud , always a pleasure! :+1: :+1:


[Wasm] Revert module type and add README for NPM

Description
Fixes https://github.com/trustwallet/wallet-core/issues/2417. This was introduced in https://github.com/trustwallet/wallet-core/pull/2332, it breaks wallet core react sample, revert back to old module type
How to test
Build and test locally (overwrite built js under node_modules
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Create pull request as draft initially, unless its complete.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] If there is a related Issue, mention it in the description.

Could you please let me know when this will be released to npm


Minor nits to get compilation on rustc 1.14 (shipping Debian version)

Will give @clarkmoody a couple days to check this out, since it is his library


I can not upgrade Center of Excellence - Core Component v.4.13

I've trying to upgrade from v.4.3 to 4.13 many times and last time i'm success import but unfortunately.
my tenant didn't have Data Lake to configure it on
section. Configure connections to data sources Step.4.a
As previous version I understand that COE using Dataverse table right?
That already paid for dataverse capacity.
Then Now I'm already replace v.4.3 by 4.13 but I don't have Data Lake , How could I do?
Or else if no way to go back, how can I select a data lake package that fit for COE kits?
Thank you.
https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#before-you-start

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

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up inventory components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @tucoeadmin. This issue has been assigned to the doc author for review.

Hello @tucoeadmin,
can you please raise the issue via https://aka.ms/coe-starter-kit-issues for the CoE kit development team to triage and help you. In this repo, we can only help with documentation issues (e.g. incorrect steps documented, or screenshots are out of date).
Thank you
Manuela