Fail to login ubuntu 20.04

I tried to login using both compile from source and  latest release and I get errors as follows
./mchfuse  -c mchfuse.conf NetStorage ~/mch/ns/
2020/06/07 19:41:14 Failure signing in My Cloud Home account: Post "https://wdc.auth0.com/oauth/token": net/http: TLS handshake timeout
my username and passowrd contains numbers ans letters and i had to encapulate both in "" to force mcfuse to accept it or it will complain of username and password

That kind of error suggests some, hopefully temporary, network issue. Could you try again from a different network connection?

yeah .. it works ... but seems to be alpha stage now .. I hope to see it mature soon .. That is the only reason I still use windows and not linux till now
Thanks for the good job

it works with ethernet but with wifi it don't work can we change the timeout ??

Raising the timeout could be a solution only if the other part is going to answer after some time. Could you please try to execute the mchfuse with GODEBUG=http2debug=1 in the environment?
export GODEBUG=http2debug=1

I should print a lot of information about the authentication calls only as Auth0 servers speak http2 while the MCH NAS doesn't.

WARNING:  Please check the output for credentials before attacking to the ticket.

It works on ethernet so Iam sure my creditials are ok but is it safe to post the debug here?
does it contain any sensitive data like usernames or passwords or ip addresses ?

I just checked, it contains several sensitive pieces of information, so it is better to not attach it directly.
2020/06/08 14:18:43 http2: Transport failed to get client conn for config.mycloud.com:443: http2: no cached connection was available
2020/06/08 14:18:43 http2: Transport creating client conn 0xc000001680 to <IP_ADDRESS>:443
2020/06/08 14:18:43 http2: Transport encoding header ":authority" = "config.mycloud.com"
2020/06/08 14:18:43 http2: Transport encoding header ":method" = "GET"
2020/06/08 14:18:43 http2: Transport encoding header ":path" = "/config/v1/config"
2020/06/08 14:18:43 http2: Transport encoding header ":scheme" = "https"
2020/06/08 14:18:43 http2: Transport encoding header "accept-encoding" = "gzip"
2020/06/08 14:18:43 http2: Transport encoding header "user-agent" = "Go-http-client/2.0"
2020/06/08 14:18:43 http2: Transport received SETTINGS len=18, settings: MAX_CONCURRENT_STREAMS=128, INITIAL_WINDOW_SIZE=65536, MAX_FRAME_SIZE=16777215
2020/06/08 14:18:43 http2: Transport received WINDOW_UPDATE len=4 (conn) incr=2147418112
2020/06/08 14:18:43 http2: Transport received SETTINGS flags=ACK len=0
2020/06/08 14:18:43 http2: Transport received HEADERS flags=END_HEADERS stream=1 len=300
2020/06/08 14:18:43 http2: Transport received DATA stream=1 len=8192 data="{\n  \"data\": {\n    \"configurationId\": \"global_default\",\n    \"componentMap\": {\n      \"com.wd.portal\": {\n        \"portal.auth0.client\": \"SGqemVDDxd20pufijh4mzkzu017ZBpN9\"\n      },\n      \"com.wd.device\": {\n        \"p2p_enabled\": false,\n        \"restore_config\"" (7936 bytes omitted)
2020/06/08 14:18:43 http2: Transport received DATA stream=1 len=1761 data="\"https://collectors.us2.sumologic.com/receiver/v1/http/ZaVnC4dhaV1dwuoPhmo2rIWW09XUfap6qw6OqmUy714Q5NwC1SFJIQrKcbsY34bM3aIDOPFeKY304QmzUMMuzkiijOQjfbg2qObJDO_XEi8sqLp_ZnEgnQ==\",\n        \"analytics.device.WDMyCloudDL4100.url\": \"https://collectors.us2.sumolo" (1505 bytes omitted)
2020/06/08 14:18:43 http2: Transport received DATA flags=END_STREAM stream=1 len=0 data=""
2020/06/08 14:18:43 http2: Transport failed to get client conn for wdc.auth0.com:443: http2: no cached connection was available
2020/06/08 14:18:44 http2: Transport creating client conn 0xc000702900 to <IP_ADDRESS>:443
2020/06/08 14:18:44 http2: Transport encoding header ":authority" = "wdc.auth0.com"
2020/06/08 14:18:44 http2: Transport encoding header ":method" = "POST"
2020/06/08 14:18:44 http2: Transport encoding header ":path" = "/oauth/token"
2020/06/08 14:18:44 http2: Transport encoding header ":scheme" = "https"
2020/06/08 14:18:44 http2: Transport encoding header "content-type" = "application/json"
2020/06/08 14:18:44 http2: Transport encoding header "content-length" = "324"
2020/06/08 14:18:44 http2: Transport received SETTINGS len=18, settings: MAX_CONCURRENT_STREAMS=128, INITIAL_WINDOW_SIZE=65536, MAX_FRAME_SIZE=16777215
2020/06/08 14:18:44 http2: Transport encoding header "accept-encoding" = "gzip"
2020/06/08 14:18:44 http2: Transport encoding header "user-agent" = "Go-http-client/2.0"
2020/06/08 14:18:44 http2: Transport received WINDOW_UPDATE len=4 (conn) incr=2147418112
2020/06/08 14:18:44 http2: Transport received SETTINGS flags=ACK len=0
2020/06/08 14:18:44 http2: Transport received HEADERS flags=END_HEADERS stream=1 len=696
2020/06/08 14:18:44 http2: Transport received DATA stream=1 len=1497 data="***REDACTED***" (1241 bytes omitted)
2020/06/08 14:18:44 http2: Transport received DATA flags=END_STREAM stream=1 len=0 data=""

This is my log until the point where it fails for you. I've redacted the last "Transport received DATA stream" line that contains AUTH tokens that are sensitive.

I think think if there is a connection issue with internet like dropped packets in case of wifi or dns issues it will fail and that does not happen if I use ethernet or I did restart my router ..
can you create update that gives safe debug info ? As this is much insecure and can give some rog person access to my whole data
Sent from my iPhone

On Jun 8, 2020, at 2:32 PM, Marco Nenciarini<EMAIL_ADDRESS>wrote:

I just checked, it contains several sensitive pieces of information, so it is better to not attach it directly.
2020/06/08 14:18:43 http2: Transport failed to get client conn for config.mycloud.com:443: http2: no cached connection was available
2020/06/08 14:18:43 http2: Transport creating client conn 0xc000001680 to <IP_ADDRESS>:443
2020/06/08 14:18:43 http2: Transport encoding header ":authority" = "config.mycloud.com"
2020/06/08 14:18:43 http2: Transport encoding header ":method" = "GET"
2020/06/08 14:18:43 http2: Transport encoding header ":path" = "/config/v1/config"
2020/06/08 14:18:43 http2: Transport encoding header ":scheme" = "https"
2020/06/08 14:18:43 http2: Transport encoding header "accept-encoding" = "gzip"
2020/06/08 14:18:43 http2: Transport encoding header "user-agent" = "Go-http-client/2.0"
2020/06/08 14:18:43 http2: Transport received SETTINGS len=18, settings: MAX_CONCURRENT_STREAMS=128, INITIAL_WINDOW_SIZE=65536, MAX_FRAME_SIZE=16777215
2020/06/08 14:18:43 http2: Transport received WINDOW_UPDATE len=4 (conn) incr=2147418112
2020/06/08 14:18:43 http2: Transport received SETTINGS flags=ACK len=0
2020/06/08 14:18:43 http2: Transport received HEADERS flags=END_HEADERS stream=1 len=300
2020/06/08 14:18:43 http2: Transport received DATA stream=1 len=8192 data="{\n  "data": {\n    "configurationId": "global_default",\n    "componentMap": {\n      "com.wd.portal": {\n        "portal.auth0.client": "SGqemVDDxd20pufijh4mzkzu017ZBpN9"\n      },\n      "com.wd.device": {\n        "p2p_enabled": false,\n        "restore_config"" (7936 bytes omitted)
2020/06/08 14:18:43 http2: Transport received DATA stream=1 len=1761 data=""https://collectors.us2.sumologic.com/receiver/v1/http/ZaVnC4dhaV1dwuoPhmo2rIWW09XUfap6qw6OqmUy714Q5NwC1SFJIQrKcbsY34bM3aIDOPFeKY304QmzUMMuzkiijOQjfbg2qObJDO_XEi8sqLp_ZnEgnQ==\",\n        "analytics.device.WDMyCloudDL4100.url": "https://collectors.us2.sumolo" (1505 bytes omitted)
2020/06/08 14:18:43 http2: Transport received DATA flags=END_STREAM stream=1 len=0 data=""
2020/06/08 14:18:43 http2: Transport failed to get client conn for wdc.auth0.com:443: http2: no cached connection was available
2020/06/08 14:18:44 http2: Transport creating client conn 0xc000702900 to <IP_ADDRESS>:443
2020/06/08 14:18:44 http2: Transport encoding header ":authority" = "wdc.auth0.com"
2020/06/08 14:18:44 http2: Transport encoding header ":method" = "POST"
2020/06/08 14:18:44 http2: Transport encoding header ":path" = "/oauth/token"
2020/06/08 14:18:44 http2: Transport encoding header ":scheme" = "https"
2020/06/08 14:18:44 http2: Transport encoding header "content-type" = "application/json"
2020/06/08 14:18:44 http2: Transport encoding header "content-length" = "324"
2020/06/08 14:18:44 http2: Transport received SETTINGS len=18, settings: MAX_CONCURRENT_STREAMS=128, INITIAL_WINDOW_SIZE=65536, MAX_FRAME_SIZE=16777215
2020/06/08 14:18:44 http2: Transport encoding header "accept-encoding" = "gzip"
2020/06/08 14:18:44 http2: Transport encoding header "user-agent" = "Go-http-client/2.0"
2020/06/08 14:18:44 http2: Transport received WINDOW_UPDATE len=4 (conn) incr=2147418112
2020/06/08 14:18:44 http2: Transport received SETTINGS flags=ACK len=0
2020/06/08 14:18:44 http2: Transport received HEADERS flags=END_HEADERS stream=1 len=696
2020/06/08 14:18:44 http2: Transport received DATA stream=1 len=1497 data="REDACTED" (1241 bytes omitted)
2020/06/08 14:18:44 http2: Transport received DATA flags=END_STREAM stream=1 len=0 data=""
This is my log until the point where it fails for you. I've redacted the last "Transport received DATA stream" line that contains AUTH tokens that are sensitive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I've researched a bit, but I have not found any straightway to redact the sensitive information in the HTTP2 debug trace. Given that you solved the network issue, I'm going to close this issue.


Refine cache resolution when annotations are used

Chapter 11.2.1 of the specification describes cache name resolution, but it does not say anything about type configuration.
Should a caching container/framework use a cache with type checking configured?
This should be refined it the specification as otherwise it may result in portability issues when switching between containers.

Its not totally clear or easily digestible what you are aiming at. Can you please add a code example and the possible ambiguous outcomes?
Please mind the spec on page 53:

Implementations may also perform key and value type checking at runtime for mutative Cache
operations.

Type checking is not mandatory and there are no TCK tests for runtime type checks.

see this: https://gist.github.com/ivannov/258ce072b01d0c55dcbc9079c50458d5

@cruftex: the spec says type checking is not mandatory for mutative operations.
However when a cache is created with type parameters then it has to be always obtained via:
getCache(String cacheName, Class<K> keyType, Class<V> valueType); and not via getCache(String cacheName) from CacheManager
Chapter 11.2.1 specified how a cache name should be generated. It implies the cache is supposed to also accessed directly (=it's not just an internal concern of the interceptor/proxy).
However the spec does not mandate whether the annotation interceptors should use a cache with type checking or a raw cache. Without knowing this you do not know what getCache() method should you call to access it. The one with type parameters or without?

I think I got it. So it boils down to:
With annotations the usable cache typing of a requested cache is only Object,Object. There is no possible way to specify more concrete types and nothing is defined that the types are inferred from the method signatures.
Correct?
I still wonder whether it might be a hazelcast or in general a specific implementation issue.

@cruftex: that's correct. I wonder about the same.
It's not clear to me from the spec -> it should be refined.

Hmm, CacheManager.getCache says:

Implementations must check if key and value types were configured
for the requested {@link Cache}. If either the keyType or valueType of the
configured {@link Cache} were specified (other than Object.class)
an {@link IllegalArgumentException} will be thrown.

I would say this rule only applies if the configuration of the different types is happening by means defined by JSR107, which would yield an ambiguous situation. OTOH, it is always the case that a cache implementation will not be able to store every object type (e.g. not serializable ones). There are always  restrictions that might apply. So I think it is legal that an implementation has a separate type configuration inside the implementation configuration and outside the JSR107 defined scope that restricts the types and does not follow the rule above.
So, if an implementation wants to leverage more concrete type information that it gets inside its own
configuration, it can do so. The TCK only checks the typing defined by the mechanisms of JSR107. What should exactly happen with the additional type information inside the implementation isn't scope of the Spec, anyways.
That said, as I can see from your gist, hazelcast refuses to return the cache since the configured types do not match (and strictly follows the rule above). Maybe hazelcast can do something more useful and still be Spec compliant? Did you open an issue at hazelcast?
OTOH, I think we both agree that the Spec should ensure a consistent and practical behavior. I just doubt that we can do this within a reasonable effort in a maintenance release.

Specifying the type just with the class, is limited anyways, e.g. there is no way to have the complete type information for generic types just as List<String>. We had a discussion about that here: https://github.com/cache2k/cache2k/issues/11. So, at least within the cache2k API there is a way to capture the whole type information.

@cruftex: I'm not sure if I'm fully following you.
Hazelcast does not provide implementation of the CDI interceptors for caching annotation.
Hazelcast provides an implementation of CacheManager.
Payara (app. server used in the gist I linked) implements CDI caching interceptors and use public imperative JSR107 API to talk to Hazelcast (CacheProvider, CacheManager, Cache, etc.).
As far I know the other containers (Spring, TomEE) do the same - they also use the public JSR107 API to implement the behaviour specified by the JSR107 annotations. Thanks to this design the JSR107 provider is independent on the container implementing the annotations and vice versa - you can have implementations for Guice, Spring, CDI and they can use Hazelcast, Cache2k or any other JSR107 compliant provider.
In other words: I use JCache annotations to store some data into a cache. I also want to have a full imperative access to the same cache via CacheManager. How can I tell what getCache() method should I call? The one with types? Or the one with raw access?
I also agree the type configuration options provided by the spec are somewhat clumsy, but that's a different topic.

Okay, we have a bunch of different requirements we actually speak about. We need to structure that a little.
1) Type information on the annotated methods should be transported through to the cache implementation
Although the Spec says that type information is derived from the signature for constructing the cache name, it is not specifying that this must also be used to retrieve the cache. There is also no TCK test for this.
The cache implementation can make use of the additional type information, e.g. by doing runtime checks or selecting serializers more effective.
2) It should possible to retrieve the used Cache instance
Requirement 2 is actually addressed by the Spec,  if you want to be able to retrieve the cache, you could define the behavior of the container by using a specific CacheResolverFactory. Then you can use the resolve factory yourself, too. I doubt that this will work consistently for all caching implementations and annotation implementations, since I cannot find TCK tests for this.
3) Annotation and the direct API can be mixed
You try to mix different APIs which would be requirement 3. What you probably want is requirement 2
(see the XYProblem...).
The Spec says, e.g. in the JavaDoc from CacheDefaults:

The default resolver pair will resolve the cache by name from the default
{@link CacheManager}

That could be more specific and say whether it is getCache(name) or getCache(name, keyType, valueType).
But how do you get the CacheManager? That you can access the same or the default CacheManager via @Inject CacheManager cacheManager; isn't defined by the Spec as well. So it is specific behavior to the container. That could be addressed by the EE integration which needs to be done.
That said, updating the Spec and enforcing that the type information is used, will solve requirement 1. It will probably solve your problem in your existing environment. But it will not ensure a consistent behavior across all containers.
I would suggest to handle it as two different things:
Use this issue to discuss whether the derived type information must be used (not necessarily solving your problem, as discussed above).
Add another issue to discuss whether there should be an easy way to inject/access a cache instance, e.g. by defining a @Cache annotation. Actually the current EE integration prototype tries to do this via CDI, but shouldn't this be in the JSR107 Spec?!

you did great job with analysing my not-so-structured thoughts, well done!
ad 1.: you wrote "Although the Spec says that type information is derived from the signature for constructing the cache name, it is not specifying that this must also be used to retrieve the cache."
However the JavaDoc of the getName() version w/o type parameters says:
   * @throws IllegalArgumentException if the {@link Cache} was configured with
   *                                  specific types, this method cannot be used

Do I still miss something?
ad 2: agreed
ad 3: I agree with the 1st part. "Just" amending the spec to mandate which version of getName() to use to get a cache would be a great improvement!
You also opened a new question "How to get a reference to CacheManager in a managed environment, but I see it as another topic. For example It's trivial if I use Spring.

To be honest, I feel a little lost here. Since I do not use EE and the cache annotations myself it takes me always some time to get into the concepts again. Anyhow, I  poked around a little bit more and thought how this makes some sense.
The Spec says, in the JavaDoc from CacheDefaults:

The default resolver pair will resolve the cache by name from the default {@link CacheManager}

I think that is the main conceptual statement we need to deal with. It has two questions: "What types are used?" and "What CacheManager?"
Used Types for Default Cache Resolution
There are two conceptual mismatches:

The imperative API forces a cache client to retrieve a cache by it name and the configured key and value types, but the the key and value types are not part of the unique cache identifier within a CacheManager, only the name is
On annotation level there is no way to specify which types should be used to have the correct invocation parameters for the imperative API. Inferring it from the method parameters is not generally useful

Let me further elaborate this:
The configured types in the cache for type enforcement and the types the application operates on may be different. In case the cache is configured with Obect, Object, you may use it with arbitrary types.
The effective types may be subtypes, too. If you define caching DAOs for each entity you might want to have one DAO per entity but a shared cache for every entity. So the cache would have the configured types EntityId, Entity but the DAO would have the method, for example: update(PersonId id, Person person). I think that is not uncommon, since you do not want to configure 20 caches (with resource limits) for every entity type you have. This means, deriving the correct types from the method signature is not generally useful, too.
While it is desirable to infer the types from the parameters and pass it to the cache, it will do more harm then good.
In a real usage scenario with Spring or EE container, probably createCache() with the JSR107 configuration object isn't used, but it relies on the cache specific configuration. The type enforcement
in the JSR107 universe does not need to be used, a cache implementation must have its own
parameters for type checking anyways if it wants to do it. In case an application requests a
cache with types Object,Object, an implementation can refuse operation or it can return a cache
and enforce the type checking configured by its own mechanisms. Only the latter behavior makes sense, since practically the usable types are always restricted, since only store by value is the only
non optional storage semantic and a cache could only "store" an arbitrary object by its reference.
=>
For what we have right now, I think we do better with defining Object, Object as standard when
annotations are used.
The only right solution would have been to consequently make the type declarable at annotation level, too. We cannot fix that in 1.x...
Used CacheManager for Default Cache Resolution
Again, the Spec says, in the JavaDoc from CacheDefaults:

The default resolver pair will resolve the cache by name from the default {@link CacheManager}

This could mean the container default, or the default as defined by the imperative API. If the meaning/interpretation is the "imperative API default", this means:

Multiple cache providers are not usable
Non default class loaders are not usable, in fact, the cache provider and the application class loader must be the same, which breaks most container scenarios!
Non default manager URLs are not usable

=>
It is more practical to allow a container to have parameters for its default provider, URL, etc. it uses for a specific application. This means also, that a container would have a container specific way to get a cachemanager of an application. I think that is okay. This could be addressed by an EE integration standard, to ensure consistency in the EE world.
Wrap Up
I'll just remember Mark Reinhold saying something like "We only can make things less painful".
Proposal:
Relevant JavaDoc at CacheDefaults:

The default resolver pair will resolve the cache by calling {@link CacheManager.getCache(name)} from {@link CacheManager} that is defined as default in this context in the annotation processor. This includes the option that an annotation processor can define the {@code CacheManager} returned by {@code Caching.getCachingProvider().getCacheManager()} as its default when this is feasible. Using  {@link CacheManager.getCache(name)} means that the cache types at API level are {@code Object, Object} and no specific type information is used.

JavaDoc at CacheManager.getCache(name) has at the moment the relevant sentence:

Implementations must check if key and value types were configured  for the requested {@link Cache}. If either the keyType or valueType of the configured {@link Cache} were specified (other than Object.class) an {@link IllegalArgumentException} will be thrown.

Add here:

Cache annotation processors will resolve caches with this method by default, since there is no defined way types can be specified at annotation level. To allow this, cache implementations must be able to work without explicit type definitions by the standard configuration mechanism.

The RI always does createCache(cacheName, new MutableConfiguration<Object, Object>());
See https://github.com/jsr107/RI/blob/562f40e599550ba5cd3f822d298df808d9d9a528/cache-annotations-ri/cache-annotations-ri-common/src/main/java/org/jsr107/ri/annotations/DefaultCacheResolverFactory.java#L73 that's why Payara does.

Thanks Steve, good hint I missed to cite that code. The complete passage is:
  @Override
  public CacheResolver getCacheResolver(CacheMethodDetails<? extends Annotation> cacheMethodDetails) {
    final String cacheName = cacheMethodDetails.getCacheName();
    Cache<?, ?> cache = this.cacheManager.getCache(cacheName);

    if (cache == null) {
      logger.warning("No Cache named '" + cacheName + "' was found in the CacheManager, a default cache will be created.");
      cacheManager.createCache(cacheName, new MutableConfiguration<Object, Object>());
      cache = cacheManager.getCache(cacheName);
    }

    return new DefaultCacheResolver(cache);
  }

It does CacheManager.getCache(name) actually the CacheManager.createCache` should never be executed in a real world scenario.

The actual cache annotations however always produce a GeneratedCacheKey as the key type or something that implements the interface so I suppose the key type should be GeneratedCacheKey the value type could be difficult to determine in the general case.

Hmm, it is hard to find arguments for the usefulness of changing to getCache(name, GeneratedCacheKey.class, Object.class). It is not a really meaningful type constraint.
We have now "Any types" or  "Sepcific types". Using GeneratedCacheKey would introduce a third thing: "A little less then any types"
One interesting aspect would be, that a cache implementation could assume that every key is serializable.
I am a afraid that this will cause additional harm to the users and/or cause other troubles. Users will need to configure that type for every cache, since on JCache imperative API level the correct type must be used and known.

Looking into this with a real life example I have over at https://github.com/gregrluck/microprofile-conference.

@gregrluck: Just looked at your code example. Good work, it is very important to take real scenarios. In the last commit you added the use of an annotation:
  @CacheRemove(cacheName="schedule")
  public void deleteSchedule(Long scheduleId) {
  }

Is this working?! According to the Spec the key type is always GeneratedCacheKey and the types get added to the name.

Haven’t got far enough to know if it is working because Payara blew up. Have an answer to that now so will let you know.
Regards
Greg Luck
web: http://gregluck.com http://gregluck.com/
skype: gregrluck
mobile US: +1<PHONE_NUMBER>
mobile Australia: +61 408 061 622

On 5 Oct. 2016, at 12:32 pm, Jens Wilke<EMAIL_ADDRESS>wrote:
@gregrluck https://github.com/gregrluck: Just looked at your code example. Good work, it is very important to take real scenarios. In the last commit you added the use of an annotation:
@CacheRemove(cacheName="schedule")
public void deleteSchedule(Long scheduleId) {
}
Is this working?! According to the Spec the key type is always GeneratedCacheKey and the types get added to the name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jsr107/jsr107spec/issues/341#issuecomment-251743341, or mute the thread https://github.com/notifications/unsubscribe-auth/AANyhPX95XyiPslw2pGg3unRke1BO1gUks5qw98ygaJpZM4IAE2T.

Got Payara working.
In the direct API we are using Long as the key. Annotation key types must be GeneratedCacheKey. In the example we have a LongKey which contains the Long but implemented GeneratedCacheKey.
Interoperability between the two APIs is broken. You could hack it up by using GeneratedCacheKey implementations yourself as keys but that is ugly.
I have reached out to Eric Dalquist who designed this to see what his idea was here.
To fix this we are going to have to change the Annotations API which we cannot do in 1.1 So moving this to 2.0

Does anyone know why we would need to keep GeneratedCacheKey? Why not make this Object?


[MM-12741] Migrate autocomplete and search actions from user_actions.jsx to redux

Summary
Migrate autocomplete and search actions from user_actions.jsx to redux
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/10156
Ticket link https://mattermost.atlassian.net/browse/MM-12741

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4205.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed

/update-branch

/update-branch


Adjacent pixel correlations

See discussion from @seabroke in #30 and comments from Gal M. The assumption of zero correlations between neighbouring pixels is obviously violated. It's unlikely to affect our results, but we should comment on it as a(nother) violated assumption.

And it is yet another reason that our parameter uncertainties are under-estimated. That should be mentioned.


Bump build number to 1

I'm just bumping the build number so we can do a new build and upload without python_abi.

@forsyth2, could you try building again following my suggestions in #88?  If you're still getting python_abi as a dependency, please don't upload.  Let's try to debug and in the worst case, I'll upload build 1 since I'm able to build without the python_abi issue.


Responsive image with srcset not working in IE8

Hi there,
I'm using a very simple markup with the img srcset tag and the density x descriptor like in your example: http://codepen.io/aFarkas/pen/KwKdpY
In IE8 the example is not working, no image is displayed?

          <img src="some-image-310x310.jpg" srcset="some-image-310x310.jpg 1x<EMAIL_ADDRESS>2x" alt="My alt" />

I'm using your latest version v1.4.1.
Any idea? Thanks!

Sorry, can't replicate this issue. Doesn't ring a bell either. Can you give me a testcase or access to your site to test against.

It's happening on this page (both on test server as live): http://monum.dd-webtest.com/monum/
In the left column there should be 3 images beneath each other. They are being displayed for a split second then disappear.
Thanks!


Add CMake support to Autotools + XCode/VisualC distributables + add avif to cmake config

Add avif to CMake's config file
Create sdl2_image-config.cmake + sdl2_Image-config-version.cmake for the Xcode SDL2_image.framework distributable
For filling in the supported formats, I looked in Xcode/SDL_image.xcodeproj/project.pbxproj
Create sdl2_image-config.cmake + sdl2_Image-config-version.cmake for the VisualC development distributable
For filling in the supported formats, I looked at VisualC/SDL_image.vcxproj
Add sdl2_image-config.cmake + sdl2_Image-config-version.cmake for autotools.
This support is incomplete, as I didn't hook up all variables yet (I added fixme's).
I also didn't add both .cmake files to the source distribution, nor added them to the install target.
They should be installed in the following folder: $(DESTDIR)$(libdir)/cmake/SDL2_image/

Most of these changes are untested!
@slouken the autotools support is unfinished...
If you decide that the SDL2_IMAGE_xxx variables should not be exported, then the autotools/xcode/visualc cmake config files can be simplified.

It seems reasonable to add the format variables to the script. That would allow projects that include SDL_image to verify that specific formats are supported, right? That seems helpful if you're including SDL_image from a binary package. I assume they would be used the same way when directly including the SDL_image directory in another project?

Yes
Right now, they can do:
find_package(SDL2_image 2.5 REQUIRED)
if(NOT SDL2IMAGE_AVIF)
    message(FATAL_ERROR "SDL2_image does not have avif support")
endif()

I didn't add it (yet), but with CMake component support, they can do the following:
e.g.
# SDL2_image for the shared library, AVIF for libavif support
find_package(SDL2_image 2.5 REQUIRED COMPONENTS SDL2_image AVIF)

I didn't add variables for png/jpeg loading. Would these be useful?

I didn't add variables for png/jpeg loading. Would these be useful?

Yes, every format should have an associated variable.

@slouken
Can you please review this pr and test the cmake integration into SDL2_image.framework?

Sure. I’m out of town for a few days, but I’ll check it out when I get back.

If you want, you can queue up changes for the other libraries so they’re ready to go when I get back.

Okay, I've merged and committed a few fixes for the packaging system, and verified that the CMake support files are present. It looks like you've added a test to verify it in the workflow?


Migration dependencies

Is it possible to have several migration timelines, where a migration in one timeline is dependent on the progress in another timeline? By timeline I mean a series of migrations that relate to the same tool (is there a better term for this?).
For example, I might have one migration timeline for managing (adding, removing, changing settings etc) Apache Kafka topics, and another migration timeline for my app's database schema. I could also have a timeline for data that is dynamic but an integral part of the application.
For example, let's say that I have a timeline for my database. In migration 155, I add a data structure to store user roles, something along the lines of:
# Migration 155, schema timeline
# UP:
CREATE TABLE user_roles (name string, domain_id number, slug string, ...);
# DOWN:
DROP TABLE user_roles;

In my data timeline, I want to fill this with a number of roles, that could change later, but that are to be considered as fairly constant:
# Migration 17, data timeline
# UP:
POST /user_roles/ {"name": "Admin", "domain_id": 1, "slug": "admin", ...}
POST /user_roles/ {"name": "User", "domain_id": 1, "slug": "user", ...}
POST /user_roles/ {"name": "Editor", "domain_id": 2, "slug": "editor", ...}
# DOWN:
DELETE /user_roles/admin
DELETE /user_roles/user
DELETE /user_roles/editor

From the above description, it is obvious that migration 17 in the data timeline cannot be run before migration 155 in the schema timeline has been run. Is there a way to deal with this kind of dependencies in umzug?

I have a need for a similar feature. It could potentially be implemented with a custom sorting function (#153).

why not have two sets of migrations, with their state managed separately?


[Test] unittest about edge event

Add basic testcases about edge event functions.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #26. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Platform based ISO detection

I've had endless trouble with ISO detection on new VB 4.1 installs. VirtualBox::DVD.all.find only works once the Additions ISO has been attached to a VM and gets added to the "virtual media library". There's no longer a way to add an ISO to the library using VBoxManage.
How do you feel about making educated guesses on the ISO path based on the host platform? Say..
@iso_path = if Vagrant::Util::Platform.linux?
    "/usr/share/virtualbox/VBoxGuestAdditions.iso"
elsif Vagrant::Util::Platform.darwin?
    "/Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso"
end

I had some thoughts on that as well, and started a gist:
https://gist.github.com/1709724
There are some unsolved problems supporting most platforms, which is why I didn't implementing those magic yet.

That looks sensible. Observations:

It seems that the path for Windows hosts is %PROGRAMFILES%/Oracle/VirtualBox
All of the .deb and .rpm packages for Linux use /usr/share/virtualbox
Not sure about Sol or BSD right now.

My gut feeling is that it's preferable to just make the best guess possible. Even if that doesn't work 100% for all platforms, for now.

I'd propose to use a fallback-chain like that:

look for a guest additions iso in the Library
guest iso location by host-platform

show a message suggesting the user to open an issue here, if we cannon guess by the host-platform, or we guessed wrong

prompt if the user want vbuest to download the correct version from virtualbox.org

I'm not sure, how vagrant handles tmp files. Especially if they last during a single command run. E.g. starting a project with two or more boxes will probably requires each box to get updated.

Hi @dcarley,
I've just pushed a not very polished branch guess_iso (see PR #6). What do you say, anything important missing?
greets,
robert

Looks functionally fine to me and tests out OK.
I might follow it up later with a PR to tidy up the variable names and error strings.

Closed by #6.


Execute a command against a container in a CGS

It's often useful when troubleshooting or debugging containers to execute a command against a container. This is particularly useful for creating a shell inside a container to test inter-container connectivity or view the state of the filesystem.
This could be implemented as:
az sbz cgs exec --resource-group <myResGroup> --name <myCGS> --instance-name <myInstance> --container-name <myContainerName> -- COMMAND ARGS
This could be extended to provide an attach command for stdin/stdout.

@leikong , Is there any update on container attach? With SF Mesh it's almost impossible to figure out what's not working with a deployment without this.

@harahma may have some update on this


Fix typo in doc.go

The use of square brackets around the workflow.ExecuteActivity invocation in the first example caused confusion for less experienced readers.

What was changed
Removed square brackets in the example used in doc.go
Why?
It's confusing for less experience readers.
Checklist

Closes

How was this tested:

Any docs updates needed?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Destination Cordinates are not getting passes in Uber , ola And other Apps.

When I am launching a location through it I am getting a dialogue (which you did use Geo intent of Android) for selecting an app to launch the app. Since my phone has Uber, Ola, and Rapido (cab services in India) I am getting the option to open the location with these apps. when I launch using Google map it's ok as I am getting the required Location Icon at the given coordinates and my current location but when I launch directly with Uber I Expect to have a ride book window directly from my current location to my Destination Window as happens in case of What's app.  Please check the behavior of what's app once for it.
I also tried to google. navigation intent of Android but this is also not working please help me in figuring out it. Please connect me directly over email at<EMAIL_ADDRESS>

you may say that this is not supported by "geo" but then how actually what app is doing it? for Android?


Fix typos in Worker.java

Quick fix on a few typos in Worker.java

+1

+1

Thanks @ruili-kekeke merged into master.


Moonstone Compass cannot work in multiplayer games.

In multiplayer games, it will rotate irregularly, and it is impossible to locate the boss position.

Which version are you playing on? It takes time to find a location if it is far away. If there is no structure to be found, it will spin irregularly.

Which version are you playing on? It takes time to find a location if it is far away. If there is no structure to be found, it will spin irregularly.

1.18.2 can't be used in the server, no matter how close to the boss will be irregular rotation.

Was thinking about the mod version as well, but I'll look into it.

Was thinking about the mod version as well, but I'll look into it.

mod version 0.9.8 Thank you

I am also experiencing this in 1.19.2, version 0.9.8
crash-2023-03-14_02.43.46-server.txt


Fixing names so code in array creation runs

fixing names to be correct / consistent (filenames, lazy_images, lazy_image)

This looks great.  Thank you both for finding this issue and for fixing it @kmader !


Do you support frameworks such as Vue and react

Hi @cy920820,
This plugin is a postcss plugin. You can hook this plugin into any framework that supports postcss. Vue and React are just JavaScript frameworks, you need to look at the framework that you use to process or generate the final CSS. Here you can find an example repo in which this plugin is being used in a Next.js project.
Closing this issue.
Regards


@bentley/imodeljs-native 4.0.0

Changes from #4898 seem to be missing

I believe those changes should have been included in this PR https://github.com/iTwin/itwinjs-core/pull/4970

Changes from #4898 seem to be missing

I believe those changes should have been included in this PR #4970

Oh, ok. The changes for presentation-common API summary should reverted in this PR then - now they duplicate what's already there and cause the extract-api to fail.


custom platform fix, resolves #3

duplicated code of "Available Default Platforms" and modified it so the values of "Available Custom Platforms" are added to self.platforms.

sorry, should have mentioned that. yes, tested on BMD WebPresenter HD , Software Version 2.1.1, Build 653bf387


[Feature Request] Show aliases as a description for the recipe

Description
Currently, when list the just recipes, the recipes alias shows as a recipe with description sayes "alias for <RECIPE>", but it would be better to show the alias as a description for the recipe.
Now
just --list
Available recipes:
    bar
    b   # alias for `bar`
    foo
    f   # alias for `foo`
    tat
    t   # alias for `tat`

Wanted
Something like this, where the alias is shown as a description for the recipe.
just --list
Available recipes:
    bar # [aliases: b]
    foo # [aliases: f]
    tat # [aliases: t]

Or if there are multiple aliases and descriptions for the recipe, it would be like this.
just --list
Available recipes:
    bar # Bar recipe description [aliases: b]
    foo # Foo recipe description [aliases: f]
    tat # Tat recipe description [aliases: t, t2, t3]

Why?
If you have a lot of recipes and aliases now, the list is hard to read and understand. This change would make it easier to understand what the aliases are for.

I think if this can be done in a compact way, it would be a nice addition. My only concern is making the output of --list too wide.

It could be even more compact with something like
just --list
Available recipes:
    bar | b # Bar recipe description
    foo | f # Foo recipe description
    tat | t, t2, t3 # Tat recipe description

So it reads from left to right as recipe bar | b can do thing x instead of breaking this flow and putting 2 ways of accessing recipe on both ends of the line. Additional bonus is that it's more compact and I think it's more clear that it's generated by just and not user comment.


Compile dependencies into a javascript file that can be deployed

This file should include the SDK, all the components and systems from the dependencies, and if those packages have dependencies, include those as well.

Closing this, explained here: https://github.com/decentraland/sdk/issues/933


Add ZodString Datetime support

Heya 🚤
Since I added this bad boy to Zod, I figured I should be the one to implement it here. Not sure how we want to fix the type support here.
We could extend Zod in this library or we could just bump up the dev deps as this code should work with both versions. Happy with either, just let me know 😄

@samchungy sorry ... I somehow missed that there is a PR open among all other issue discussions 🤦. I'll have a look in a bit

@samchungy I am okay with keeping the peer dependencies untouched and just bumping the dev dependencies for now. I'll be merging the PR and scheduling a release in a bit (once again :smile:). Thank you!


Screenshot quickly

May I ask how you take quick screenshots in Obsidian? Is it possible to come up with an action for the plugin to take a quick screenshot of an image? Because I'm using the screenshot function that comes with Windows, and every time I take a screenshot a prompt box pops up in the bottom right corner, which is distracting. Anyway, thank you very much for your efforts!

Hmm, I use Shottr on Mac and built in screenshot tool on Windows. I would say it is better to try another screenshot tool, such as https://getsharex.com/

This tool screenshot experience is fantastic, thanks a lot! @Hugo-Persson


fix rendering for asciidoc templates

Fix #290

Can you updates the QRCode section of the docs to mention this new asciidoc property and how to use it?

Done, but not sure if the is english, or french translated to english ;) !


SDA

I've squashed this branch ahead of time :smile:
Please let me know if you think I'm missing something important.

Corrected the misleading comments, simplified some loops, and fixed a few issues a new test run encountered. Looking good for staging.


Cleanup files for Gerber builds

I've updated the markdown and added the bare schematic to the builds. Let me know what you think.

I've updated the markdown and added the bare schematic to the builds. Let me know what you think.

Just checking this request and it looks like modifications of text in the markdown files and removal of files from the Gerber folder only?

Yep!

Sorry mate, my actual question is "why".  😁

@Kaldek I removed all the Gerber files since they are now built with the Github Actions directly. This means there is less to commit and review in pull requests, and one less step to remember when updating the KiCad files.
As for the Markdown changes, I fixed a broken image link and maybe got carried away removing the hardcoded URL so that forks/pull requests can reference items local to their own repository before merging into the main one. My editor also removes trailing spaces, which is what some of those big block are. I didn't change any actual text in the Markdown.
Hope this was a decent explanation. 😅

Ah right, OK my noobiness shines through here; I didn't know it was possible for the files to be built automatically.    I am literally 3 weeks into Github, which is as embarrassing to me as it probably is to everyone else.

@Kaldek It doesn't show at all, and is impressive how much you've done in only 3 weeks! 👍


ISerializable and Model Schema

Hi,
I've got problem with shema of my models, it is empty.
I analized your code and I sow that you don't handle JsonISerializableContract (all my models are, ISerializable)
When contract is this type you return FilterSchema(new Schema { type = "object" }, jsonContract)
Line 112
can you fix it or is another way to handle my models

This issue is similar to one I posted last night. Issue when my object inherited from IEnumerable it didn't show the correct model.
In the schema filter file the specific model type never showed up for processing.
https://github.com/domaindrivendev/Swashbuckle/issues/911


Added ability to transform columnName in populate() criteria

Added ability to transform columnName in populate() criteria.
Before this fix, where statement in populate() cannot use model attribute name.
Like this case.
// Article.js
module.exports = {
  tableName: 'articles',

  attributes: {
    title: 'string',
    body: 'string',
    categories: {
      collection: 'category',
      through: 'articlecategory'
    },
    publicationDate : {
      columnName: 'publication_date',
      type: 'Date'
    }
  }
};

// Category.js
module.exports = {
  tableName: 'categories',

  attributes: {
    name: 'string'
    articles: {
      collection: 'article',
      through: 'articlecategory'
    }
  }
}

// ArticleCategory.js
module.exports = {
  tableName: 'articles_categories',
  tables: ['articles', 'categories'],
  junctionTable: true,

  attributes: {
    article: {
      columnName: 'article',
      type: 'integer',
      foreignKey: true,
      references: 'article',
      on: 'id',
      onKey: 'id',
      via: 'category'
    },
    category: {
      columnName: 'category',
      type: 'integer',
      foreignKey: true,
      references: 'category',
      on: 'id',
      via: 'article'
    }
  }
};

where statement in populate() cannot use attributeName defined at model.
// find category with articles
Category.find().populate('articles', where: {publication_date: {'<=': new Date()}}).then(function(categories) {
  // ...
}).catch(function(error) {});

// ERROR on `publicationDate`
Category.find().populate('articles', where: {publicationDate: {'<=': new Date()}}).then(function(categories) {
  // ...
}).catch(function(error) {});

After this fix, where statement in populate() works both columnName and attributeName.
And, I fixed test case transformations.initialize.js. The 2nd argument of Transformer expects simple object (like {article: ..., category: ...}).

Maybe I'm a little bit paranoid, but now doesn't each collection's transformer hold the transformations for every collection?  Why not use the child collection's transformer to make the transformation?

Maybe collection doesn't have child collection's transformer. I could not find applicable code...

You would have to get the child collection name by diving into the schema, I will look for a code example.

It will look something like this: https://github.com/balderdashy/waterline/blob/master/lib/waterline/query/finders/joins.js#L185-L188
My only other concern as far as testing goes, is that this works for many-to-many and one-to-many scenarios.  Could that join.child ever reference a junction table?

Thanks!
I will rewrite my code by reference to that.
I checked both many-to-many and one-to-many. many-to-many sample is above(Article,Category and ArticleCategory). I tried one-to-many senario like following.
// Article.js
module.exports = {
  tableName: 'articles',

  attributes: {
    title: 'string',
    body: 'string',
    images: {
      collection: 'ArticleImage',
      via: 'article'
    },
  }
}

// ArticleImage.js
module.exports = {
  tableName: 'article_images',

  attributes: {
    size: 'int',
    article: {
      columnName: 'article_id',
      model: 'Article',
      type: 'integer',
      required: true
    },
    fileName: {
      type: 'string',
      columnName: 'file_name',
    },
  }
}

// Query
Article.find({id: 1}).populate('images', {where: {fileName: "test.png"}}).then( ...

Awesome, thanks!  I just have one more question which I placed in code comments.  This will be great :)

@KeitaMoromizato, would it be possible to add an automated test that fails before your fix is applied and works afterwards? The test can be based on the example you wrote on the first post. Thanks!

This looks good, I'll whip up a quick test in (adapter-tests I guess?) so we have a before/after test to show it works.

Added a failing unit test

@particlebanana, I assume the #1078 is passing after applying this change to waterline right? If so, I'm good with merging this. :white_check_mark:

Awesome, test in https://github.com/balderdashy/waterline/pull/1078 failed and after merged this passes.

Thanks @KeitaMoromizato!

Thank you @KeitaMoromizato!

Awesome, test in #1078 failed and after merged this passes.

Cool!


Cache size for NetworkImage is unbounded

Need a way to control the caching behavior of NetworkImage.
Closely related to https://github.com/flutter/flutter/issues/3568.

There's no cache specific to NetworkImage. The regular image asset cache is capped at 1000 entries. There's a specific bug about making it respond to memory pressure, #3006.
I'm closing this since it seems unactionable.


[render issue] switch brightness causes wrong partial render.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

open a flutter page.
swtich brightness on system.

Expected results
the page rendered to correct color.
Actual results

part of page rendered. the rest was not updated.
the page was flash if scrolling the listview, it looks like keeping switch the dark and light color.

Code sample
Code sample
import 'dart:ui';

import 'package:flutter/material.dart';

class TestList extends StatefulWidget {
  const TestList({Key? key}) : super(key: key);

  @override
  State<TestList> createState() => _TestListState();
}

class _TestListState extends State<TestList> with WidgetsBindingObserver {
  late Brightness brightness;

  @override
  void initState() {
    WidgetsBinding.instance.addObserver(this);
    brightness = window.platformBrightness;
    super.initState();
  }

  @mustCallSuper
  @override
  void didChangePlatformBrightness() {
    brightness = window.platformBrightness;
    if (mounted) {
      setState(() {});
    }
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('List Test Page'),
      ),
      body: SafeArea(
        child: Container(
          color: brightness == Brightness.light ? Colors.white : Colors.black,
          child: ListView.builder(
            itemCount: 100,
            itemBuilder: (ctx, index) {
              return Container(
                padding: EdgeInsets.all(20),
                child: Text(
                  '$index',
                  style: TextStyle(
                    fontSize: 18,
                    color: brightness == Brightness.light ? Colors.black : Colors.white,
                  ),
                ),
              );
            },
          ),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/9456005/73810b85-24f3-4370-9976-da8b8e25aea7

Logs
It looks like that the render issue results from different refreshing frequencies between several areas of the picture.
The issue only happens when I integrate the program with a hybrid development project (with Flutter_Boost). I cannot reproduce the problem when running the program independently. I am not sure if this is caused by the Native code of the hybrid project or if it is an issue with Flutter itself.
The issue only appears when I try to upgrade the SDK from 2.5.3 to 3.3.10 or 3.7.11. Previously it works perfectly with SDK 2.5.3
I found some possible related issues: #111376, #110885。
My device：xiaomi mix2 and Huawei mate 50 pro.
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.2.1 22D68 darwin-arm, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 14.2)
    ! CocoaPods 1.10.1 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.78.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

! Doctor found issues in 1 category.

Hi @joechan-cq. I see you aren't on the latest flutter version. Kindly confirm this issue still persists by upgrading to the latest stable version.

I tried it on Flutter 3.10.5, and it worked fine. So I will close this issue although I can't use the newest flutter sdk for some other reasons.
I would appreciate it if I could acquire the way to fix the issue on Flutter 3.3.10.


Revealing map when adding new drawings

Game System: DnD5e
Modules: only Dungeon Draw
Issue
When drawing new dungeon pieces, players will occasionally see the dungeon as if no walls were in place, revealing the map up to their controlled tokens vision. There is also a similar issue with new drawings revealing rooms adjacent to a room that the controlled token is in. This can be problematic when trying to secretly draw dungeons on the fly.
Steps to recreate

create new world and enable Dungeon Draw
create scene and set darkness to 1
draw a rectangular piece of dungeon
create a player account and log in through browser
create a token inside the rectangular dungeon piece and set dim vision to 60, bright vision to 30 and then assign to player
draw unconnected dungeon pieces on the canvas

PS. Really like the idea of this module.

Thanks for the bug report! My guess is this might be happening because Dungeon Draw deletes all existing walls it made before making new ones... so it may be possible for players to get a glimpse of "no walls" before the new walls are re-made. I'll see if I can combine the wall delete + remake into a single database change.

yeah i got the feeling that it may be due to processing time between deletion and creation. Quick fix might be to create first then delete, would probably still have visual artifacts but they should be confined to already visible areas.

Fixed in 0.16.2. Changed wall creation to create new walls as one update, before deleting old walls as a second update.


Missing UI strings in JS files

There are 16 missing UI strings and they are all JS strings. I think this is GlotPress ignore minimized JS (*.min.js) when it retrieved UI strings from the source code.
I think adding original JS files to the plugin can resolve this issue.

@alexclassroom JS translations are in the different .po(t) files: https://github.com/sjinks/wp-two-factor-provider-webauthn/blob/master/lang/two-factor-provider-webauthn-js.pot
I suspect that GlotPress does not support multiple .post files :-(

Yes, GlotPress doesn't support multiple text-domain. BTW, I will submit a PR to upload zh_TW.js for two-factor-provider-webauthn-js.pot later.


chore(main): release sandworm-jest 1.2.0

:robot: I have created a release beep boop
1.2.0 (2022-09-29)
Features

update sandworm-utils to v1.4.0 (7458009)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-jest/releases/tag/sandworm-jest-v1.2.0 :sunflower:


textDocument/willSaveWaitUntil is a request but implements Notification

According to the LSP specification, it seems like textDocument/willSaveWaitUntil is supposed to be a client-to-server request that expects a response back. However, it seems like WillSaveWaitUntil implements Notification instead and doesn't provide a response type. Is this actually correct?

Blocks ebkalderon/tower-lsp#10.

Probably a copy past mistake from the similiarly named https://docs.rs/lsp-types/0.71.0/lsp_types/notification/enum.WillSaveWaitUntil.html. Happy to take a PR!

I think you mean https://docs.rs/lsp-types/0.71.0/lsp_types/notification/enum.WillSave.html, which doesn't currently exist. 😂
The spec defines textDocument/willSave (notification) and textDocument/willSaveWaitUntil (request).
Sure, I'll open up a PR right away!

Copied the wrong url :( https://docs.rs/lsp-types/0.71.0/lsp_types/notification/enum.WillSaveTextDocument.html (it does exist)

Yep, sorry! I only just noticed my mistake as well and was just editing my response. I missed it too. 😅

Opened pull request #143. Hoping the changes were correct!

I also tried my best to keep the ordering consistent with their definition in the upstream spec document, as I've noticed you have done, but please do correct me if I put it in the wrong location.


Enabling MultiLang API calls Usage

MultiLang API Usage and setting Region, Languages using ffu Languages
Marking TargetPlatform as 16278, we can change before checkin and after
RS3 release
Cleaned up stale Lang resource Keys

@sukusuma,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Fix inputless fields for add book and limit isbn field to 13 characters

Fix application crash bug by defining context and setting the length limit for the isbn field in xml file.

I think it looks good. On the bus right now so I cant actually test.
How did you get the crash? Would you be able to tell me how to recreate it?

Refer to the issues posted


Week 2 Individual

Individual GitHub pages (3 points + 1 extra credit)
Graded by Paul: 4/3 points

[x] GitHub page that documents key learnings and code snippets using GitHub and replit (See Challenges at the bottom of  TT2 (Links to an external site.) for details)
[x] Organize files, directories and menus for the first 3 weeks.
[x] Write Factorial function using classes, providing implementation of call.
[x] Select your own Math function. Write it in Imperative and OOP form.
[x] Extra Credit(1 point).  Write Palindrome function using classes, must provide implementation of call.  Must indicate where error occurs on front and back comparison.

Replit flies are organized by weeks along with organization with the submenus for different functions. Math and factorial functions are added as well as the palindrome fully functional(+1 extra credit). Classes were used to run procedures as instructed. 4/3


Compatibility with declarative Routes

Is it possible to use https://github.com/icd2k3/use-react-router-breadcrumbs#advanced (the "breadcrumb" property") when using react-router and declarative, <Route> style routes?
Thanks!

You can not pass a breadcrumb prop into a Route component, but you can still define all the paths you're using and pass it into the breadcrumbs hook
<Route path="example" element={<Example />} />

// ...

useBreadcrumbs({ path: '/example', breadcrumb: 'Custom' });

This will work, but I'd recommend using route objects because you can add a custom breadcumb property and pass the same config into react-router and use-react-router-breadcumbs to keep everything in sync.

got a pr for this coming in 👍

you can track the change here
#49 @YousefED

I have pulled in 3.2.0 but I don't seem to be able to add breadcrumbs to my Route elements. I get the error:
Property 'breadcrumb' does not exist on type 'IntrinsicAttributes & (PathRouteProps | LayoutRouteProps | IndexRouteProps)'.

Possibly because I'm using TypeScript as well?

looks like you figured it out,
but one solution is to create a file that adds the type to Route from react-router
import React from 'react';
import { Route, PathRouteProps, LayoutRouteProps, IndexRouteProps } from 'react-router-dom';
type BreadCrumb = { breadcrumb: any }
type BreadCrumbRouteType = (_props: PathRouteProps | LayoutRouteProps | IndexRouteProps | BreadCrumb) => React.ReactElement<any, string | React.JSXElementConstructor<any>> | null
const BreadCrumbRoute: BreadCrumbRouteType = Route;

export { BreadCrumbRoute as Route }

then you import that Route instead.
import { Route } from '<your_project>/<filename>'
I can make a pr for this so that use-react-router-breadcrumbs will export Route instead of react-router
import { Route, BreadcrumbsRoute } from 'use-react-router-breadcrumbs';

The other solution is as you mentioned @Kallb123
and the change would be for me just to update the docs
const GenerateAppRoutes = () => {
  // Full declarative react router support. example: Element, children, Nested Routes
  return (
    <Route path='/users/:userId' breadcrumb={DynamicUserBreadcrumb} element={<ProfilePage/>} />
    <Route path='/example' breadcrumb='Custom Example' >
      <Route path='/' breadcrumb='Custom Example' >
        <ExamplePage/>
      </Route>
    </Route>
    <Route path='/custom-props' breadcrumb={CustomPropsBreadcrumb} props={ someProp: 'Hi' } >
      <CustomPage/>
    </Route>
  )
};

changes to
const GenerateAppRoutes = () => {
// Full declarative react router support. example: Element, children, Nested Routes
return (
< BreadCrumbRoute path='/users/:userId' breadcrumb={DynamicUserBreadcrumb} element={} />
< BreadCrumbRoute path='/example' breadcrumb='Custom Example' >
< BreadCrumbRoute path='/' breadcrumb='Custom Example' >

< BreadCrumbRoute path='/custom-props' breadcrumb={CustomPropsBreadcrumb} props={ someProp: 'Hi' } >

)
};

made a pr containing the first solution
#51

@MichaelDimmitt @Kallb123 - see if 3.2.1 checks all the boxes for ya!

Hi, this solution worked for me for generating the routes with breadcrumbs, but I'm not able to pass custom props.
Type '{ path: string; breadcrumb: any; element: Element; props: any; }' is not assignable to type 'IntrinsicAttributes & (PathRouteProps | LayoutRouteProps | (IndexRouteProps & BreadCrumb))'.
Property 'props' does not exist on type 'IntrinsicAttributes & (PathRouteProps | LayoutRouteProps | (IndexRouteProps & BreadCrumb))'.


"RangeError: out of range index" in HandshakeInitializationPacket.parse

Opened this issue because #2228 was closed without actually verifying if the issue is resolved or not.
Actual Issue:  Following line in our code
mysql.createPool(connConfigs).getConnection(function (err, connection) {
...})

is sometimes causing following uncaught errors (noticed in production server logs) which we couldn't handle by simple try catch blocks

RangeError: out of range index, at RangeError (native),
at Parser.parseBuffer (/srv/www/integrator/node_modules/mysql/lib/protocol/Parser.js:319:16),
at Parser.parseFiller (/srv/www/integrator/node_modules/mysql/lib/protocol/Parser.js:276:15),
at HandshakeInitializationPacket.parse (/srv/www/integrator/node_modules/mysql/lib/protocol/packets/HandshakeInitializationPacket.js:50:39),
at Protocol._parsePacket (/srv/www/integrator/node_modules/mysql/lib/protocol/Protocol.js:262:12),
at Parser.write (/srv/www/integrator/node_modules/mysql/lib/protocol/Parser.js:76:12),
at Protocol.write (/srv/www/integrator/node_modules/mysql/lib/protocol/Protocol.js:39:16),
at Socket. (/srv/www/integrator/node_modules/mysql/lib/Connection.js:103:28),
at emitOne (events.js:96:13), at Socket.emit (events.js:188:7),
at readableAddChunk (_stream_readable.js:176:18),
at Socket.Readable.push (_stream_readable.js:134:10),
at TCP.onread (net.js:547:20)

Looks like proper error handling is missing when a handshake packet from server has incorrect data.
Since we couldn't reproduce the issue locally, I tried placing throw new Error('Hello 123') at line no. 50 in HandshakeInitializationPacket.js but still, I am getting following uncaught error instead of getting the error in the callback of mysql.createPool(connConfigs).getConnection

Uncaught Error: Hello 123
at HandshakeInitializationPacket.parse (node_modules/mysql/lib/protocol/packets/HandshakeInitializationPacket.js:50:11)
at Protocol._parsePacket (node_modules/mysql/lib/protocol/Protocol.js:272:12)
at Parser._parsePacket (node_modules/mysql/lib/protocol/Parser.js:433:10)
at Parser.write (node_modules/mysql/lib/protocol/Parser.js:43:10)
at Protocol.write (node_modules/mysql/lib/protocol/Protocol.js:38:16)
at Socket. (node_modules/mysql/lib/Connection.js:91:28)
at Socket. (node_modules/mysql/lib/Connection.js:525:10)
at Socket.EventEmitter.emit (domain.js:441:20)
at addChunk (_stream_readable.js:284:12)
at readableAddChunk (_stream_readable.js:265:11)
at Socket.Readable.push (_stream_readable.js:220:10)
at TCP.onStreamRead (internal/stream_base_commons.js:94:17)
at TCP.onread (node_modules/async-listener/glue.js:188:31)

We are using 2.14.0 version on production server, but issue is occuring on latest (2.17.1) also.

https://github.com/mysqljs/mysql/issues/2228#issuecomment-499920053


New implementation of t-digest in go; Link in README?

Hey there!
@nathanielc and I have been working on a new go implementation here:
https://github.com/influxdata/tdigest/
Our plan is to use your algorithm in to calculate quantiles in our new query language (https://github.com/influxdata/ifql)
We're hoping to get feedback and have our work linked in your README.
We followed the C++ patterns in @derrickburns https://github.com/derrickburns/tdigest implementation. That pattern allowed us to get better performance and fewer allocations than @spenczar 's implementation.

Your implementation can't run real-time with add and calculate percentile immediately

Hi @dinhvankiet124 ... not sure what you mean, would you elaborate?


Use with pre-existing volume

I am trying to start a Jenkins container with a pre-existing volume.
My setup is (latest Docker on Ubuntu 14.04.3):
docker volume create --name shared-data
docker run -it --name tools -v shared-data:/var/shared ubuntu
mkdir jenkins_home
^C
docker run -t -d --name jenkins -p 8080:8080 -p 50000:50000 -v shared-data:/var/shared \
  --env JENKINS_OPTS="--httpPort=8080" --env JENKINS_HOME="/var/shared/jenkins_home" \
  jenkins

But I get the following error:
Running from: /usr/share/jenkins/jenkins.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
Dec 07, 2015 4:22:04 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Dec 07, 2015 4:22:04 PM winstone.Logger logInternal
INFO: Winstone shutdown successfully
Dec 07, 2015 4:22:04 PM winstone.Logger logInternal
SEVERE: Container startup failed
java.io.FileNotFoundException: /var/shared/jenkins_home/war/META-INF/MANIFEST.MF (Permission denied)
	at java.io.FileOutputStream.open0(Native Method)
	at java.io.FileOutputStream.open(FileOutputStream.java:270)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
	at winstone.HostConfiguration.getWebRoot(HostConfiguration.java:280)
	at winstone.HostConfiguration.<init>(HostConfiguration.java:83)
	at winstone.HostGroup.initHost(HostGroup.java:66)
	at winstone.HostGroup.<init>(HostGroup.java:45)
	at winstone.Launcher.<init>(Launcher.java:143)
	at winstone.Launcher.main(Launcher.java:354)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at Main._main(Main.java:293)
	at Main.main(Main.java:98)

My goal is to save all data not in /var/jenkins_home (default), but in /var/shared/jenkins_home, that points to my volume.
I have read https://github.com/jenkinsci/docker/issues/155 and https://github.com/jenkinsci/docker/issues/152, among other issues, but haven't been able to come up with a working configuration.

Having exactly the same issue. If I don't name the volume it works fine, but that's not much use when I want to ultimately use a volume driver.
With a named volume the /var/lib/docker/volumes/<vol_name>/_data directory is owned by root, whereas when I omit the volume name it is correctly owned by uid/gid 1000.

It is a permissions issue, the volume is created with root permissions and jenkins runs as user 1000. Either do something to the volume to have the right permissions or run jenkins as root
See https://github.com/jenkinsci/docker/issues/158 for a possible alternative


Add a base-x parser

Opening a new PR as my Pull-bot integration discarded my previous changes.

It is unclear to me why the build is failing. Your code looks fine. Investigating...

Ah, your comments need to be triple /s, i.e. /// so that they can be considered doc comments and get read by the macro.

We made it!


unable to install boxes from hashicorp

When I install a libvirt box from hashicorp (vagrant's default location), the base image is not copied to /var/lib/libvirt/images. "Vagrant up" then fails, since it is missing the base image in /var/lib/libvirt/images.
See below for output.
The way I read the output, adding a box does not include copying the base image to the storage pool.
It seems to be a bug.
Am I doing something wrong?

Debug output
mon@monacer:~/git/test$ vagrant box add naelyn/ubuntu-trusty64-libvirt --debug
....
DEBUG box_collection: Box directory: /home/mon/.vagrant.d/boxes/naelyn-VAGRANTSLASH-ubuntu-trusty64-libvirt/14.04
DEBUG box_collection: Moving: /home/mon/.vagrant.d/tmp/vagrant-box-add-temp-20150728-11972-rfwz35/metadata.json => /home/mon/.vagrant.d/boxes/naelyn-VAGRANTSLASH-ubuntu-trusty64-libvirt/14.04/libvirt/metadata.json
DEBUG box_collection: Moving: /home/mon/.vagrant.d/tmp/vagrant-box-add-temp-20150728-11972-rfwz35/Vagrantfile => /home/mon/.vagrant.d/boxes/naelyn-VAGRANTSLASH-ubuntu-trusty64-libvirt/14.04/libvirt/Vagrantfile
DEBUG box_collection: Moving: /home/mon/.vagrant.d/tmp/vagrant-box-add-temp-20150728-11972-rfwz35/box.img => /home/mon/.vagrant.d/boxes/naelyn-VAGRANTSLASH-ubuntu-trusty64-libvirt/14.04/libvirt/box.img
...
INFO interface: success: ==> box: Successfully added box 'naelyn/ubuntu-trusty64-libvirt' (v14.04) for 'libvirt'!
==> box: Successfully added box 'naelyn/ubuntu-trusty64-libvirt' (v14.04) for 'libvirt'!
...
mon@monacer:~/git/test$ vagrant init naelyn/ubuntu-trusty64-libvirt
A Vagrantfile has been placed in this directory.  Please read
the comments in the Vagrantfile as well as documentation on
vagrantup.com for more information on using Vagrant.
mon@monacer:~/git/test$ vagrant up --provider=libvirt
Bringing machine 'default' up with 'libvirt' provider...
/home/mon/.vagrant.d/gems/gems/fog-libvirt-0.0.2/lib/fog/libvirt/requests/compute/list_volumes.rb:32:in info': Call to virStorageVolGetInfo failed: Storage volume not found: no storage vol with matching path '/var/lib/libvirt/images/moozer-VAGRANTSLASH-base-ob57_vagrant_box_image_0.0.1.img' (Libvirt::RetrieveError) 	from /home/mon/.vagrant.d/gems/gems/fog-libvirt-0.0.2/lib/fog/libvirt/requests/compute/list_volumes.rb:32:in volume_to_attributes'
from /home/mon/.vagrant.d/gems/gems/fog-libvirt-0.0.2/lib/fog/libvirt/requests/compute/list_volumes.rb:10:in block (2 levels) in list_volumes' 	from /home/mon/.vagrant.d/gems/gems/fog-libvirt-0.0.2/lib/fog/libvirt/requests/compute/list_volumes.rb:9:in each'
...

Ok
I found the problem. It was a variation on the theme of #85
As part of my development I had removes the box, and the base file, but has not done the "pool-refresh".


React.useRef should not have nullable current

Since useRef has default value null can be inferred from it. So it's not necessary to add another default which requires to add unnecessary checks in some cases.
declare export function useRef<T>(initialValue: T): {current: T};

const count = useRef<number>(0);

count.current // number

const reference = useRef<?Element>(null)

reference.current // ?Element

/cc @bvaughn @jbrown215

Interesting! This implies that when a default value is set– the ref will never be set to null, which might not be true in all cases. But I guess it would be nice for cases where it is true, and people could always add an explicit <Element | null> in that case... (I don't think <?Element> would be as accurate since that would also permit undefined)
What do you think, @jbrown215?

This is also useful for cases where I cannot pass nullable value and I need to do some hacks to workaround it.
const now = React.useRef(null);
if (now.current == null) {
  now.current = new Date();
}

return <DatePicker value={now.current} /> // error, value should not be nullable

So what should I pass in useRef for const ref = useRef()
Passing null or undefined, throws error Cannot call ref.current.scrollIntoView because property scrollIntoView is missing in null.


Update en_US.lang

Added Seal Detector

After looking into it more, I'm pretty sure I PR'd this to the wrong branch

Yeah, but it's fine, I'll stick it in stable real quick, easier than actually merging/etc


⚠ AGEG website (prod) has degraded performance

In 0709f27, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2039 ms

Resolved: AGEG website (prod) performance has improved in 2e8aa65.


[Bug]: The document parsing failed and exited.

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
0f95086
Other environment information
ASUS Tuf Gaming F15 Pro 13980HX 4060 Laptop Graphics Card
Win11
WSL2

Actual behavior
When parsing the document, an error occurred and the program exited.

Expected behavior
No response
Steps to reproduce
Update to the latest version (dev or 0.10.0), upload the document, and then parse it.

Additional information
I believe the issue is with the function parameter settings of the newly added error output mechanism. When the LLM returns unexpected information (such as error messages), it causes the program to receive parameters of the wrong type, which in turn triggers the interrupt process mechanism.

I have tested it, and there is no issue with the code built from the 9b3f5fd commit.

Could you paste the docker logs? It shows the calling stack there。
Or, could you share the file sample?

2024-08-26 11:19:43 ragflow-server  | Traceback (most recent call last):
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/graphrag/graph_extractor.py", line 139, in call
2024-08-26 11:19:43 ragflow-server  |     result, token_count = self._process_document(text, prompt_variables)
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/graphrag/graph_extractor.py", line 188, in process_document
2024-08-26 11:19:43 ragflow-server  |     if response.find("ERROR") >=0: raise Exception(response)
2024-08-26 11:19:43 ragflow-server  | Exception: ERROR: Error code: 400, with error text {"contentFilter":[{"level":1,"role":"assistant"}],"error":{"code":"1301","message":"系统检测到输入或生成内容可能包含不安全或敏感内容，请您避免输入易产生敏感内容的提示语，感谢您的配合。"}}
2024-08-26 11:19:43 ragflow-server  |
2024-08-26 11:19:43 ragflow-server  | During handling of the above exception, another exception occurred:
2024-08-26 11:19:43 ragflow-server  |
2024-08-26 11:19:43 ragflow-server  | Traceback (most recent call last):
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/rag/svr/task_executor.py", line 165, in build
2024-08-26 11:19:43 ragflow-server  |     cks = chunker.chunk(row["name"], binary=binary, from_page=row["from_page"],
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/rag/app/knowledge_graph.py", line 18, in chunk
2024-08-26 11:19:43 ragflow-server  |     chunks = build_knowlege_graph_chunks(tenant_id, sections, callback,
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/graphrag/index.py", line 85, in build_knowlege_graph_chunks
2024-08-26 11:19:43 ragflow-server  |     graphs.append(.result().output)
2024-08-26 11:19:43 ragflow-server  |   File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
2024-08-26 11:19:43 ragflow-server  |     return self.__get_result()
2024-08-26 11:19:43 ragflow-server  |   File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
2024-08-26 11:19:43 ragflow-server  |     raise self._exception
2024-08-26 11:19:43 ragflow-server  |   File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
2024-08-26 11:19:43 ragflow-server  |     result = self.fn(*self.args, **self.kwargs)
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/graphrag/graph_extractor.py", line 145, in call
2024-08-26 11:19:43 ragflow-server  |     if callback: callback("Knowledge graph extraction error:{}".format(str(e)))
2024-08-26 11:19:43 ragflow-server  |   File "/ragflow/rag/svr/task_executor.py", line 80, in set_progress
2024-08-26 11:19:43 ragflow-server  |     if prog is not None and prog < 0:
2024-08-26 11:19:43 ragflow-server  | TypeError: '<' not supported between instances of 'str' and 'int'

Fixed by #2096

Is the latest docker image updated? Or should I build it locally to avoid this issue?

Fixed by #2096

The BUG has been fixed. Thx!


make all fails on Fedora 35 with gcc 11.2.1 and gflags 2.2.2

Describe the bug
When compiling speedb (and rocksdb) on Fedora 35 with gcc 11.2.1 and gflags 2.2.2, we encounter the following error:
In file included from db_stress_tool/batched_ops_stress.cc:11: ./db_stress_tool/db_stress_common.h:105:15: error: expected constructor, destructor, or type conversion before ‘(’ token   105 | DECLARE_uint32(max_num_parallel_flushes);       |               ^  ./db_stress_tool/db_stress_common.h:296:15: error: expected constructor, destructor, or type conversion before ‘(’ token   296 | DECLARE_uint32(memtable_protection_bytes_per_key);       |               ^ In file included from db_stress_tool/cf_consistency_stress.cc:11: ./db_stress_tool/db_stress_common.h:105:15: error: expected constructor, destructor, or type conversion before ‘(’ token   105 | DECLARE_uint32(max_num_parallel_flushes);       |               ^ ./db_stress_tool/db_stress_common.h:296:15: error: expected constructor, destructor, or type conversion before ‘(’ token   296 | DECLARE_uint32(memtable_protection_bytes_per_key);       |               ^   CC       db_stress_tool/no_batched_ops_stress.o   CC       db_stress_tool/multi_ops_txns_stress.o make: *** [Makefile:2447: db_stress_tool/batched_ops_stress.o] Error 1
To Reproduce
Steps to reproduce the behavior:
make all
Expected behavior
The build to pass
System (please complete the following information):

OS: Fedora 35
Hardware AMD Ryzen 7 PRO 5850U (x86_64)

Possible solution
Addressed here. Seems to be resolved in RocksDB, but it was merged AFTER the release of RocksDB 7.7.8, which is the current RocksDB version we are rebased against.
I can open a PR with the same fix for us.

any reason not to just wait for the rebase on a version greater than 7.8.3?

any reason not to just wait for the rebase on a version greater than 7.8.3?

Yes, because we don’t always want to rely on RockDB, especially when it comes to bug fixes. Users of speedb should be able to build speedb without issues, and should not have to rebase against RocksDB to get fixes, or make local changes. Fedora is a rather common distribution and there might be other users besides me that are experiencing this issue.


fetches that don't include a relationship shouldn't update related records

it appears that old objects in the store can find their way back into the RelatedRecords array of a previous related object on fetch, even if the response from that fetch doesn't include any information regarding the old objects.
Example:
class Car extends Model {
  @relatedToMany tires
}

car.tires
//> RelatedRecordsArray (4) [tire_1, tire_2, tire_3, tire_4]

car.tires.replace([tire_5, tire_6, tire_7, tire_8])

tire_1.car
//> undefined

car.store.fetchAll('cars') // by default server returns included: false for tires

car.store.getRecord('cars', car.id).tires
//> RelatedRecordsArray (8) [tire_1, tire_2, tire_3, tire_4, tire_5, tire_6, tire_7, tire_8]

This should no longer be possible as of version 7


Update attrs dependency from 17.4.0 please

Operating system: Arch Linux
Python version: 3.7.0
Black version: 18.9b0
Does also happen on master: Yes.
Do note that that there is no issue with latest attrs==18.2.0. The following occurs with attrs==17.4.0.
Error detected while processing /home/avmo/.vim/plugged/black/plugin/black.vim:
line  124:
Traceback (most recent call last):
  File "<string>", line 56, in <module>
  File "/home/avmo/.local/lib/python3.7/site-packages/black.py", line 39, in <module>
    from attr import dataclass, Factory
  File "/home/avmo/.local/lib/python3.7/site-packages/attr/__init__.py", line 5, in <module>
    from . import converters, exceptions, filters, validators
  File "/home/avmo/.local/lib/python3.7/site-packages/attr/filters.py", line 7, in <module>
    from ._compat import isclass
  File "/home/avmo/.local/lib/python3.7/site-packages/attr/_compat.py", line 139, in <module>
    set_closure_cell = make_set_closure_cell()
  File "/home/avmo/.local/lib/python3.7/site-packages/attr/_compat.py", line 131, in make_set_closure_cell
    set_closure_cell = ctypes.pythonapi.PyCell_Set
  File "/usr/lib/python3.7/ctypes/__init__.py", line 369, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python3.7/ctypes/__init__.py", line 374, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: vim: undefined symbol: PyCell_Set

Thanks for your report! ✨ 🍰 ✨


Does the scripts support installing tensorflow r1.0?

Thank you for providing these convenient scripts! Can I use these scripts to install tensorflow r1.0?
More specifically, In the script cloneTensorflow.sh, you have git checkout r0.11, can I change this to git checkout r1.0 and run the rest of the scripts to install tensorflow r1.0?

No. There currently is a bug on the Jetson TX1 in the nvcc compiler which causes the build to fail on Tensorflow r1.0.

No. There currently is a bug on the Jetson TX1 in the nvcc compiler which causes the build to fail on Tensorflow r1.0.

Hi Jetsonhacks, would it be possible to checkout the r0.12 version and still get it up and running?

I do not know, I have not tried it.


⚠ Processors has degraded performance

In 818fac0, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 117 ms

Resolved: Processors performance has improved in 2702f32.