text:
Upgrade with an unknown signer doesn't update deployment

Describe the bug
deployments/network/ContractName.json file is not updated when an upgrade with an unknown signer is performed
To Reproduce
Steps to reproduce the behavior:

Deploy a contract as OptimizedTransparentProxy
Create a new version of the contract ContractNameV2 and add a new function newFunction()
Deploy upgrade like this:

  await hre.deployments.catchUnknownSigner(
    hre.deployments.deploy("ContractName", {
      from: deployerAddress,
      proxy: {
        proxyContract: "OptimizedTransparentProxy",
        owner: newProxyAdminOwnerAddress, // make sure this one is unknown to hardhat!
      },
      contract: "ContractNameV2",
      args: []
    })
  );

Execute the instruction form console (replace the implementation in a proxy)
In a hardhat task try to call the new function:

const token = await hre.ethers.getContract("ContractName") as ContractNameV2;
const newFieldValue = await token.newFunction();

You get TypeError: token.newFunction is not a function
It works fine if you do it like this:

const token = await hre.ethers.getContractAt("ContractNameV2", proxy_address) as ContractNameV2;

Expected behavior
deployments/network/ContractName.json  Should be updated and await hre.ethers.getContract("ContractName") should return the right ABI
versions

hardhat-deploy 0.9.27
hardhat  2.6.8
nodejs v14.17.5

Additional context

If you use a known signer there it works jus fine
It look like this line throws: https://github.com/wighawag/hardhat-deploy/blob/19b4ef8f9b1423ade4c318178d356f1747cadf63/src/helpers.ts#L1520
and therefore this line never gets called: https://github.com/wighawag/hardhat-deploy/blob/19b4ef8f9b1423ade4c318178d356f1747cadf63/src/helpers.ts#L1564

Before step 5, you ll need to reexecute the deployment scripts so that it update the deployments file

@wighawag The deployments/network/ContractName_Implementation.json gets updated right away deployments/network/ContractName.json doesn't get updated even if I rerun the deployment task.
What is the recommended way to do this? If I just run the deployment task again it changes nothing.

The deployments/network/ContractName_Implementation.json gets updated right away deployments/network/ContractName.json doesn't get updated even if I rerun the deployment task.

this is expected since it deploy that
but you need to rexecute the deploy script to update the link with the proxy. if that link is not updated, there is probably an issue.
when you reexecute the scripts before step 5, what happen, are your scripts idempotent ? do you get any error, are you told to perform a new upgrade ?

@wighawag Yes the scripts are idempotent thanks to the framework. The deployment framework (I thought it's actually the hardhat-deploy itself that does it) appends the script name to the deployments/network/.migrations.json and the script never executed again. This is why I'm wondering about the procedure here.
this code:
  await hre.deployments.catchUnknownSigner(
    hre.deployments.deploy("ContractName", {
      from: deployerAddress,
      proxy: {
        proxyContract: "OptimizedTransparentProxy",
        owner: newProxyAdminOwnerAddress, // make sure this one is unknown to hardhat!
      },
      contract: "ContractNameV2",
      args: []
    })
  );

will be executed once only, since after the first successful run it's file will be appended to deployments/network/.migrations.json. Duplicating this code in a subsequent script/migration doesn't seem right.
Regarding you second question, the step 4 is the last deployment step that I perform. Step 5 is just a simple hardhat task which I'm running afterwards with intention to test it the upgrade worked.

Ha! I see. I did not though about someone using the migration option.
Note that if you have your script idempotent, you do not need to use the migration options though.
If you want to keep using it, I am wondering what hardhat-deploy could do to make it easier for you to update the deployment file.
One thing that it possible in the same file it is to catchUnknowSigner but then pause the script and then when you are done with the upgrade, the scripts perform the upgrade again but this time as it will not change, it will update the deployment

@wighawag Thanks! I'll give it a go

@wighawag It worked. However I think it would be better if the deployments/network/ContractName.json file was updated right away along with proxy and implementation. Maybe I'm not seeing the whole picture here, but I can see no reason to run the script twice or to add another migration with basically the same code. When deployments/network/ContractName.json is out of sync with proxy and implementation, the code is in a kind of corrupt state imho.

@AndrzejGisWideLab how would that work ?
when catchUnknownSIgner catch the error, this is when you execute your upgrade, at that point, you need to tell hardhat-deploy to update. there is no background process running watching the chain for updates.
I guess you could create a utility function that call catchUnknowSIgner and keep watching the chain and then update. Not sure if it need to be part of hardhat-deploy though.

@wighawag I didn't dive very deep into the code but basically what I think is:
Whatever updates these 2 json files (it happens before the the implementation is replaces on-chain):
deployments/network/ContractName_Proxy.json
deployments/network/ContractName_Implementation.json
Could immediately update also:
deployments/network/ContractName.json
I don't understand what's the purpose of splitting those .json files updates into 2 stages, but like I said, I might not be seeing the big picture here.

I could potentially add a command update-proxies that would check for new implementation and update accordingly

I could potentially add a command update-proxies that would check for new implementation and update accordingly

This would be great!

Hey all, I recently came across this exact issue. In our case, we use catchUnknownSigner and then save the output to then schedule an update with our multi-sig.
In my opinion, the core issue is that its fundamentally a two-stage process:

Get the new implementation deployed (and possibly tested)
Update the ABI of the proxy to know about any changes now available in the updated version

So I do agree that ContractName.json should not automatically be overwritten at new implementation deploy time, since, by definition, that new ABI is not available yet until (in our case) the multi-sig does the upgrade.
So yeah, a new command we can run after the multi-sig upgrade call, that updates the the main ContractName.json would be ideal, as we want our repo ABI to represent whats 'current' on chain.
As of now, we have been grabbing the new ABI out of the updated ContractName_Implementation.json and pasting it into the ContractName.json ABI after the on-chain upgrade is performed. Obviously not ideal, and ripe for a copy/paste error.

We have the same problem on our side and I'm thinking about what the best solution would be to solve this in a clean way.

I am currently working on hardhat-deploy v2 and the same issue will be present there and i think adding a new command that "sync" the deployment files make sense
It can read the implementation address onchain and check for the matching implementation deployment file and update the abi,etc..

authors: AndrzejGisWideLab Archethect gisek masha256 wighawag

repo: wighawag/hardhat-deploy


text:
WebSecurityConfigurerAdapter deprecated 관련 설정

5장에서 WebSecurityConfigurerAdapter deprecated로 인해 spring boot 3.x 테스트가 멈추었습니다.
앞에서는 spring boot 2.7 & react 관련이지만 spring boot 3.x 관련 주요 변경 사항이 언급을 해주셨는데,
이번장에는 언급이 없네요....
WebSecurityConfigurerAdapter deprecated 관련된 내용을 어떻게 수정해야 하는지 혹시 언급을 해주실 수 있을까요?
미리 감사합니다.

@hoya74 님, 안녕하세요.
위키북스 담당자입니다.
보내주신 내용을 확인했는데, 이 책의 실습 안내에서 스프링 부트 2.7으로 안내하고 있고, 이 책의 원서에서도 5장의 README.md에서 2.6.12 버전으로 진행하라는 내용이 있어서 가급적 안내에 따라 진행하실 것을 권장해 드리고 있습니다.
다만 완벽하게 검증되지 않았지만 별도로 테스트한 바에 따르면 스프링 부트 3.0.8 버전으로(pom.xml의 spring-boot-starter-parent 항목을 3.0.8로 지정) 다음과 같이 SecurityConfig.java 파일을 수정할 경우 5장의 예제가 문제 없이 동작하는 것을 확인했습니다.
package com.packt.cardatabase;

import java.util.Arrays;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.http.HttpMethod;
import org.springframework.security.authentication.AuthenticationManager;
import org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder;
import org.springframework.security.config.annotation.authentication.configuration.AuthenticationConfiguration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.config.http.SessionCreationPolicy;
import org.springframework.security.crypto.bcrypt.BCryptPasswordEncoder;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter;
import org.springframework.web.cors.CorsConfiguration;
import org.springframework.web.cors.CorsConfigurationSource;
import org.springframework.web.cors.UrlBasedCorsConfigurationSource;

import com.packt.cardatabase.service.UserDetailsServiceImpl;

@Configuration
@EnableWebSecurity
public class SecurityConfig {
	@Autowired
	private UserDetailsServiceImpl userDetailsService;

	@Autowired
	private AuthenticationFilter authenticationFilter;

	@Autowired
	private AuthEntryPoint exceptionHandler;

	@Bean
	public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
		http.csrf().disable().cors().and()
		.sessionManagement().sessionCreationPolicy(SessionCreationPolicy.STATELESS)
		.and()
		.authorizeRequests()
		.requestMatchers(HttpMethod.POST, "/login").permitAll()
		.anyRequest().authenticated().and()
		.exceptionHandling()
		.authenticationEntryPoint(exceptionHandler).and()
		.addFilterBefore(authenticationFilter, UsernamePasswordAuthenticationFilter.class);

		return http.build();
	}

	@Bean
	CorsConfigurationSource corsConfigurationSource() {
		UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
		CorsConfiguration config = new CorsConfiguration();
		config.setAllowedOrigins(Arrays.asList("*"));
		config.setAllowedMethods(Arrays.asList("*"));
		config.setAllowedHeaders(Arrays.asList("*"));
		config.setAllowCredentials(false);
		config.applyPermitDefaultValues();

		source.registerCorsConfiguration("/**", config);
		return source;
	}

	@Autowired
	public void configureGlobal(AuthenticationManagerBuilder auth)
			throws Exception  {
		auth.userDetailsService(userDetailsService)
		.passwordEncoder(new BCryptPasswordEncoder());
	}

	@Bean
	AuthenticationManager authenticationManager(
			AuthenticationConfiguration authenticationConfiguration) throws Exception {
		return authenticationConfiguration.getAuthenticationManager();
	}
}

그럼 참고 부탁드리고, 오늘도 좋은 하루 보내세요.
고맙습니다.

@wikibook 감사합니다. 덕분에 해결되었습니다~ ^^

@wikibook 님 안녕하세요.
감사합니다. 덕분에 해결되었습니다~ ^^

@hoya74 님, 안녕하세요.
문제가 해결되셨다니 다행이네요.
그럼 오늘도 좋은 하루 보내세요.
고맙습니다.

source: gharchive/issue

repo: wikibook/springboot-react

license: MIT

license_type: permissive

license_source: github-api


text:
build: Upgrade eslint-docgen from ^0.7.0 to ^0.7.1

After #91.

Codecov Report

Merging #92 (7976e43) into master (551f9bb) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #92   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          128       128
=========================================
  Hits           128       128

source: gharchive/pull-request

authors: codecov-commenter jdforrester

repo: wikimedia/eslint-plugin-mediawiki


text:
Lack of interactions in RDF files? [Export to BEL via PathMe]

Dear @egonw,
As discussed via twitter we dont find almost any relationship in exported files we do via PathMe.
Our parser runs the following SPARQL query (see below) to get the relationships across RDF "nodes" but it is coming empty for almost all files.
Are these files generated with a different RDF exporter than the normal ones in WikiPathways?
We probably  have to change something in this query because it is often the case that this happens in some normal pathways where "cartoons" are drawn (e.g., https://www.wikipathways.org/index.php/Pathway:WP107)
Example that comes empty from the COVID19 pathways: https://www.wikipathways.org/index.php/Pathway:WP4862
"""
SELECT DISTINCT
    (?source_entry AS ?source)
    (?dc_source AS ?source)
    (?target_entry AS ?target)
    (?dc_target AS ?target)
    ?uri_id
    (STRAFTER(STR(?uri_id), "/Interaction/") AS ?identifier)
    (STRAFTER(STR(?uri_type), str(wp:)) AS ?interaction_types)
    (STRAFTER(STR(?ncbigene_source), str(ncbigene:)) AS ?source )
    (STRAFTER(STR(?ncbigene_target), str(ncbigene:)) AS ?target )
WHERE {
   ?pathway a wp:Pathway .
   ?uri_id dcterms:isPartOf ?pathway .
   ?uri_id a wp:DirectedInteraction .
   ?uri_id rdf:type ?uri_type .
   ?uri_id wp:source ?source_entry .
   ?uri_id wp:target ?target_entry .
   optional {?source_entry dcterms:identifier ?dc_source .}
   optional {?target_entry dcterms:identifier ?dc_target .}
   optional {?source_entry wp:bdbEntrezGene ?ncbigene_source .}
   optional {?target_entry wp:bdbEntrezGene ?ncbigene_target .}
}
"""

Probably we have to change the SPARQL query @cthoyt

this query looks like it has all sorts of smells in it...

Here's a new query for getting all directed interactions. Caveats: only extracting entrez identifiers/labels when its a gene. not differentiating between gene and gene products. Takes about 20-25 seconds to run.
SELECT DISTINCT
    ?pathwayIdentifier
    ?pathwayTitle
    ?interaction
    ?sourceNamespace
    ?sourceIdentifier
    ?sourceEntrezIdentifier
    ?sourceEntrezLabel
    ?targetNamespace
    ?targetIdentifier
    ?targetEntrezIdentifier
    ?targetEntrezLabel
WHERE {
   ?pathway a wp:Pathway .
   OPTIONAL { ?pathway dcterms:identifier ?pathwayIdentifier . }
   OPTIONAL { ?pathway dc:title ?pathwayTitle . }
   ?interaction dcterms:isPartOf ?pathway .
   ?interaction a wp:DirectedInteraction .
   ?interaction wp:source ?source .
   ?interaction wp:target ?target .
   OPTIONAL {
        ?source wp:bdbEntrezGene ?sourceEntrez .
        ?sourceEntrez dcterms:identifier ?sourceEntrezIdentifier .
        ?sourceEntrez rdfs:label ?sourceEntrezLabel .
    }
   OPTIONAL {
        ?target wp:bdbEntrezGene ?targetEntrez .
        ?targetEntrez dcterms:identifier ?targetEntrezIdentifier .
        ?targetEntrez rdfs:label ?targetEntrezLabel .
   }
   OPTIONAL { ?source dc:source ?sourceNamespace . }
   OPTIONAL { ?target dc:source ?targetNamespace . }
   OPTIONAL { ?source dcterms:identifier ?sourceIdentifier . }
   OPTIONAL { ?source dcterms:identifier ?targetIdentifier . }
}

Example python code for getting this into a pandas dataframe (@egonw i was going to add this to https://www.wikipathways.org/index.php/Help:WikiPathways_Sparql_queries#Code_examples but we never got my WikiPathways account recovered...)
from io import StringIO

import pandas as pd
import requests

URL = 'http://sparql.wikipathways.org/sparql'
res = requests.get(URL, params=dict(query=..., format='text/csv'))
df = pd.read_csv(StringIO(res.text))

Pathway: https://www.wikipathways.org/index.php/Pathway:WP4862 has no interactions. So it makes sense that that one returns none. There is caveat since two genes form a complex, and you could argue that that is an interaction. But complex participation is not currently interpreted in the semantic part of the RDF AFAIK.
You are right about pathway: https://www.wikipathways.org/index.php/Pathway:WP107 too.
Interactions that we currently capture are currently only between gene products of any kind and metabolites. That pathway contains only one of these. Many of the other "interactions/arrows" are indeed more cartoon-like representations of processes described with text labels or not even really connected to anything. A problematic aspect here is the groups. This is something we haven't solved yet. If you draw an interaction between two groups we do not really know what that means. Is that a reaction between "any of" and "any of" or "all"? And is that the same on both sides of the arrow? For now, and as far as I know,  there is no semantic interpretation of an interaction that involves a group (or a complex for that matter, but it might be easier to solve that).

Thanks for the explanations. We just wanted to make sure you hadn't changed the RDG schema. Then we will wait until the relationships are curated. Will certainly help on that

There are other more complex issues too. Typically we allow curators to use an ID from their own favorite database for gene products, metabolites, and interactions. Since WIkiPathways and PathVisio have BridgeDB build in that is not a problem. However, for the RDF it is. That is why we "normalize" the semantic part of the RDF and explicitly add UniProt, ENSEMBL and a few more. So we basically use BridgeDb during the creation.
Now for the COVID genes there are two issues still. 1) Until yesterday we did not have a BridgeDb database for the coronaviruses. So there wasn't one used to create this first RDF. 2) These pathways are special since they contain gene products from two different species. We have had that problem in the past, for malaria. But we have never really completely solved it. We will have to check whether the RDF generation process will really use two different BridgeDb databases. At this stage, it probably doesn't.

authors: Chris-Evelo cthoyt ddomingof


text:
Remove DMR API dependency from HealthStatus

Could the PR be updated with issue id and the usual template?

authors: heiko-braun kenfinnigan

repo: wildfly-swarm/wildfly-swarm

license_source: bigquery


text:
[WFCORE-1481] list-add operation doesn't work on login-modules attribute

Rebase of #1613 plus makes a small change to revert what looked like an unnecessary change in an unrelated class.

Linux Build 4146 outcome was FAILURE using a merge of 679363d3cf9c7152fcdfa27dbb8753cd14011f57
Summary: Tests failed: 4 (4 new), passed: 3727, ignored: 57 Build time: 00:41:53
Failed tests
org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeMapWrite: org.jboss.as.controller.OperationFailedException: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0393: Could not resolve attribute expression: 'runtime-map-attribute.map-key2'"}}
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:147)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeMapWrite(EnhancedSyntaxTestCase.java:722)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeMapWrite(EnhancedSyntaxTestCase.java:706)
------- Stdout: -------
15:43:57,650 ERROR (main) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:974> WFLYCTL0013: Operation ("write-attribute") failed - address: ([("subsystem" => "test")]) - failure description: "WFLYCTL0393: Could not resolve attribute expression: 'runtime-map-attribute.map-key2'"

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeMapAttributeWrite: java.lang.IllegalArgumentException: null
	at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:100)
	at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:384)
	at org.jboss.as.controller.PropertiesAttributeDefinition.unwrapModel(PropertiesAttributeDefinition.java:96)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeMapAttributeWrite(EnhancedSyntaxTestCase.java:598)

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite: org.jboss.as.controller.OperationFailedException: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException"}}
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:147)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeListWrite(EnhancedSyntaxTestCase.java:693)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite(EnhancedSyntaxTestCase.java:677)
------- Stdout: -------
15:43:57,753 ERROR (main) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:984> WFLYCTL0013: Operation ("write-attribute") failed - address: ([("subsystem" => "test")]): java.lang.IllegalArgumentException
	at org.jboss.dmr.ModelValue.addChild(ModelValue.java:128)
	at org.jboss.dmr.ModelNode.add(ModelNode.java:1239)
	at org.jboss.as.controller.operations.global.EnhancedSyntaxSupport.updateWithEnhancedSyntax(EnhancedSyntaxSupport.java:91)
	at org.jboss.as.controller.operations.global.WriteAttributeHandler.getEnhancedSyntaxResolvedOperation(WriteAttributeHandler.java:217)
	at org.jboss.as.controller.operations.global.WriteAttributeHandler.lambda$doExecuteInternal$0(WriteAttributeHandler.java:184)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:218)
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:144)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeListWrite(EnhancedSyntaxTestCase.java:693)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite(EnhancedSyntaxTestCase.java:677)

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeListAttributeWrite: java.lang.IllegalArgumentException: null
	at org.jboss.dmr.ModelValue.asList(ModelValue.java:140)
	at org.jboss.dmr.ModelNode.asList(ModelNode.java:1384)
	at org.jboss.as.controller.StringListAttributeDefinition.unwrapValue(StringListAttributeDefinition.java:56)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeListAttributeWrite(EnhancedSyntaxTestCase.java:657)

Windows Build 3503 outcome was FAILURE using a merge of f655c167ec8ff35b90356802a44742affd1d4257
Summary: Tests failed: 4 (4 new), passed: 3727, ignored: 57 Build time: 01:09:32
Failed tests
org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeMapWrite: org.jboss.as.controller.OperationFailedException: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0393: Could not resolve attribute expression: 'runtime-map-attribute.map-key2'"}}
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:147)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeMapWrite(EnhancedSyntaxTestCase.java:722)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeMapWrite(EnhancedSyntaxTestCase.java:706)
------- Stdout: -------
00:00:14,423 ERROR (main) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:974> WFLYCTL0013: Operation ("write-attribute") failed - address: ([("subsystem" => "test")]) - failure description: "WFLYCTL0393: Could not resolve attribute expression: 'runtime-map-attribute.map-key2'"

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeMapAttributeWrite: java.lang.IllegalArgumentException: null
	at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:100)
	at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:384)
	at org.jboss.as.controller.PropertiesAttributeDefinition.unwrapModel(PropertiesAttributeDefinition.java:96)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeMapAttributeWrite(EnhancedSyntaxTestCase.java:598)

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite: org.jboss.as.controller.OperationFailedException: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException"}}
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:147)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeListWrite(EnhancedSyntaxTestCase.java:693)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite(EnhancedSyntaxTestCase.java:677)
------- Stdout: -------
00:00:14,527 ERROR (main) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:984> WFLYCTL0013: Operation ("write-attribute") failed - address: ([("subsystem" => "test")]): java.lang.IllegalArgumentException
	at org.jboss.dmr.ModelValue.addChild(ModelValue.java:128)
	at org.jboss.dmr.ModelNode.add(ModelNode.java:1239)
	at org.jboss.as.controller.operations.global.EnhancedSyntaxSupport.updateWithEnhancedSyntax(EnhancedSyntaxSupport.java:91)
	at org.jboss.as.controller.operations.global.WriteAttributeHandler.getEnhancedSyntaxResolvedOperation(WriteAttributeHandler.java:217)
	at org.jboss.as.controller.operations.global.WriteAttributeHandler.lambda$doExecuteInternal$0(WriteAttributeHandler.java:184)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:218)
	at org.jboss.as.controller.test.AbstractControllerTestBase.executeCheckNoFailure(AbstractControllerTestBase.java:144)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.performCompositeListWrite(EnhancedSyntaxTestCase.java:693)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testCompositeListWrite(EnhancedSyntaxTestCase.java:677)

org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeListAttributeWrite: java.lang.IllegalArgumentException: null
	at org.jboss.dmr.ModelValue.asList(ModelValue.java:140)
	at org.jboss.dmr.ModelNode.asList(ModelNode.java:1384)
	at org.jboss.as.controller.StringListAttributeDefinition.unwrapValue(StringListAttributeDefinition.java:56)
	at org.jboss.as.controller.operation.global.EnhancedSyntaxTestCase.testRuntimeListAttributeWrite(EnhancedSyntaxTestCase.java:657)

authors: bstansberry wildfly-ci

repo: wildfly/wildfly-core


text:
[WFCORE-3151] TrustManager - non-lazy CRL reload

Fixes of:

errors occurred during reload not visible as operation result
reload flag is shared across individual TrustManagers (first used TrustManager is reloaded instead of the chosen one)

https://issues.jboss.org/browse/WFCORE-3151
https://issues.jboss.org/browse/JBEAP-11225

This isn't a blocker and the related issue state is pretty clear this isn't targeted at WF Core 3, so I'm putting the 4.x label on it. Please make some noise if that's wrong.


text:
operation-requires-reload message is missing

when modify values of task-max-threads and task-keepalive,
operation-requires-reload message is not outputed.
these two attributes is processed in XnioWorker#setOption, and have values return,
so it should always return true.
[standalone@localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-keepalive, value=10000)
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-max-threads, value=10000)
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=io-threads, value=10000)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone@localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-core-threads, value=10000)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}

Can one of the admins verify this patch?

this is ok to test

Thanks @cyron! Can you file a JIRA for this in https://issues.jboss.org/projects/WFCORE and update the commit message to reference it?

Looking at the current code I'm not sure any of these should be triggering reload-required. Looking at XnioWorker.setOption they all seem to be passing the value into the executor, implying that it takes immediate effect. Perhaps the Xnio behavior has changed.
It's not correct to both have something take immediate effect and report reload-required as if no change was made to the runtime.

Core - Full Integration Build 7829 outcome was FAILURE using a merge of f9c44fc2c54b0ef344d3ca2204c3a30bae3f89dc
Summary: Tests failed: 1 (1 new), passed: 4518, ignored: 139 Build time: 02:18:45
Failed tests
org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBConcurrentFailoverTestCase.test: javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 15 seconds for key InfinispanBeanKey(UUIDSessionID [bb34f414-3e53-4d67-a570-ca26377d8edb]) and requestor GlobalTx:node-2:10. Lock is held by GlobalTx:node-2:7
	at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:220)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
	at java.lang.Thread.run(Thread.java:748)
	Suppressed: java.net.ConnectException: Connection refused
		at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
		at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
		at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
		at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
		at ...asynchronous invocation...(Unknown Source)
		at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
		at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:537)
		at org.jboss.remoting3.ConnectionInfo$None.getConnection(ConnectionInfo.java:82)
		at org.jboss.remoting3.ConnectionInfo.getConnection(ConnectionInfo.java:55)
		at org.jboss.remoting3.EndpointImpl.doGetConnection(EndpointImpl.java:488)
		at org.jboss.remoting3.EndpointImpl.getConnectedIdentity(EndpointImpl.java:434)
		at org.jboss.remoting3.UncloseableEndpoint.getConnectedIdentity(UncloseableEndpoint.java:52)
		at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.getConnectedIdentityUsingClusterEffective(RemotingEJBDiscoveryProvider.java:311)
		at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider$DiscoveryAttempt.lambda$connectAndDiscover$0(RemotingEJBDiscoveryProvider.java:384)
		at java.security.AccessController.doPrivileged(Native Method)
		at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider$DiscoveryAttempt.connectAndDiscover(RemotingEJBDiscoveryProvider.java:384)
		at org.jboss.ejb.protocol.remote.RemotingEJBDiscoveryProvider.discover(RemotingEJBDiscoveryProvider.java:151)
		at org.jboss.ejb.protocol.remote.RemoteEJBDiscoveryConfigurator.lambda$configure$0(RemoteEJBDiscoveryConfigurator.java:42)
		at org.wildfly.discovery.ConfiguredProvider.discover(ConfiguredProvider.java:45)
		at org.wildfly.discovery.Discovery.discover(Discovery.java:100)
		at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.discover(DiscoveryEJBClientInterceptor.java:241)
		at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.doClusterDiscovery(DiscoveryEJBClientInterceptor.java:485)
		at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.executeDiscovery(DiscoveryEJBClientInterceptor.java:298)
		at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocation(DiscoveryEJBClientInterceptor.java:94)
		at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:491)
		at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocation(NamingEJBClientInterceptor.java:63)
		at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:491)
		at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:165)
		at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:491)
		at org.wildfly.common.context.Contextual.runExConsumer(Contextual.java:203)
		at org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:327)
		at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:173)
		at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112)
		at com.sun.proxy.$Proxy24.remove(Unknown Source)
		at org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBConcurrentFailoverTestCase.test(RemoteStatefulEJBConcurrentFailoverTestCase.java:114)
		at org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBConcurrentFailoverTestCase.test(RemoteStatefulEJBConcurrentFailoverTestCase.java:85)
------- Stdout: -------
 [0m15:01:08,692 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
 [0m [0m15:01:09,158 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
 [0m [0m15:01:09,173 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
 [0m [0m15:01:09,360 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 14.0.0.Beta2-SNAPSHOT (WildFly Core 6.0.0.Beta2-SNAPSHOT) starting
 [0m [0m15:01:10,660 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.5.4.Final
 [0m [0m15:01:11,718 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

Hi, Brian, I just filed 2 issues and update my commit messages.
should I create a separated pull request for each commit?
https://issues.jboss.org/browse/WFCORE-4035
https://issues.jboss.org/browse/WFCORE-4036

The test failures are related to this change.

@cyron this PR has not been updated for a while and there were failures related to the changes. I'm closing it but do not hesitate to reopen it if you fix the related failures.

authors: bstansberry cyron jamezp jmesnil wildfly-ci


text:
java.lang.UnsatisfiedLinkError: no wfssl in java.library.path

the error stack:

Caused by: java.lang.UnsatisfiedLinkError: no wfssl in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at org.wildfly.openssl.SSL$LibraryLoader.load(SSL.java:288)
... 33 common frames omitted

what should I config my project on linux os?
thanks very much.

@vankwang the readme has details on how to set it up here https://github.com/wildfly/wildfly-openssl/blob/master/README.md#installing-the-native-library

@jaikiran  I am sorry that I reply this topic so late, with your help finally I got success,
on linux , just do
    org.wildfly.openssl.OpenSSLProvider.register()

on windows,
first download the ssl installer, http://slproweb.com/download/Win64OpenSSL-1_1_0h.exe ,
install it, and then input this code in project,
    System.setProperty("org.wildfly.openssl.path", "C:\\OpenSSL-Win64\\bin");
    org.wildfly.openssl.OpenSSLProvider.register()

it is really much faster than jdk ssl :)

authors: jaikiran kyle2008 vankwang

repo: wildfly/wildfly-openssl


text:
[WFCORE-2805] Use Xalan from JRE rather than our own fork

https://issues.jboss.org/browse/WFCORE-2805

@ppalaga I'd very much interested in the outcome of this.  Is it likely that you find the time rebase and verify this PR in the near future?

@heiko-braun this PR is just maybe 50% of work, to completly move to jdk provided jaxp impls changes need to be done at least to also wildfy-core & jboss-modules.
One of the problems we found later on when we tried that some time ago https://github.com/jboss-modules/jboss-modules/pull/68 is that problems are in not-so-common xml related components.
such as saaj, jax-ws and others. and there ware at the time no feasable solutions possible.

@heiko-braun any further steps here and in the dependency PR https://github.com/wildfly/wildfly-core/pull/2551 were put on hold by @n1hility .
@ctomc note that the present PR is related solely to Xalan. As long as my knowledge reaches, Xalan can be removed. The points you made about saaj & Co are rather related to Xerces and I agree that the situation there is indeed very complicated there.

@ppalaga As this pull request has  been held up for a long time, I am closing it to get the pull request queue under control again. Since this is very old now, it will be a very long time until this one will be addressed. Also, I don't have much time to spend on this to evaluate on a case by case basis.
If this is something important to you or the project please feel free to recreate the pull request. That way it will come on top of the pile again, and be looked at again sooner.
If it is a new feature, please follow the new process for features. Ping @kabir or @jamez if you are unsure what this means, and we can help. Please do that before opening the pull request though.
Sorry for any inconvenience!

cc @wolfc

authors: ctomc heiko-braun kabir ppalaga

repo: wildfly/wildfly


text:
EE 9 experiment

Just a test.

/retest


text:
[26.x][WFLY-15880] Adjust chmod to 644 for dev content

Fixes https://issues.redhat.com/browse/WFLY-15880
Upstream
https://github.com/wildfly/wildfly/pull/15071

Thanks @boris-unckel

authors: boris-unckel bstansberry


text:
[26.x][WFLY-16847] Upgrade Eclipse Yasson to 1.0.11/2.0.4

Fixes https://issues.redhat.com/browse/WFLY-16847
Upstream https://github.com/wildfly/wildfly/pull/15953

Please find all links to release notes, git tags, github-diff in the Jira.


text:
tmtpro flag only adds tag to lysines, not n-term.

Hello,
Using the tmtpro flag in a config file only adds the tag to lysine. Attaching config file and input .csv. Thanks!
prosit_input_minimal.zip

Thanks for pointing this out. I was able to reproduce this and know the reason for it. It will be fixed as part of the new API release.

Awesome, glad to hear it.

authors: ChrisMcGann picciama

repo: wilhelm-lab/oktoberfest


text:
Can't get it working on iOS

Hi all,
I'm trying to build a single-view web-app using express (not the best framework for my use cases, I know).
Because it is a 'web-app' it would be the best when I open the page in full screen on my phone, there is no overflow for the user to scroll. Currently, the view of the divs takes up the entire height and width of the viewport and fits perfectly, however when you scroll, there is a large, blank white overflow that I want to remove. I want to essentially recreate the demo, but without the need of a separate scroll target, so pretty much no scrolling at all is needed. I have been working on this for like 4 hours now and I can't seem to get it working.
The  BSL demo works fine on my iPhone, and has the desired operation, ability to unlock and lock the view.
The BSL on my server works fine on my desktop, but does not function at all on my phone.
The app consists of the Express backend, with just plain HTML, JS and CSS as the frontend.
The code is below. I am pretty sure it is my stupidity...
'index.html'
...
<!-- Top of the file (in the Head section) -->
<head>
     <script src="http://192.168.1.75:4000/bodyScrollLock.js"></script>
</head>
...
<!-- Bottom of the file -->
</body>
<script src="http://192.168.1.75:4000/scrollLocker.js"></script>
...

scrollLocker.js
const targetElement = document.querySelector('scroll-target2');
bodyScrollLock.disableBodyScroll('targetElement');

Cheers,
Will

@laz3rpenguin I'm pretty sure you can't include a <script> element outside the <body> tag, try adding your scripts just before the closing </body> tag

repo: willmcpo/body-scroll-lock


text:
Enable Add, Edit, Remove Custom Category Feature Flag

Enable Add, Edit, Remove Custom Category Feature Flag

Functionality is no longer needed.

authors: jennydoesthings rc-young

repo: willowtreeapps/vocable-android


text:
🛑 willpxxr.com is down

In bf962d0, willpxxr.com (https://willpxxr.com) was down:

HTTP code: 999
Response time: 182 ms

Resolved: willpxxr.com is back up in fb40f3e after 2 hours.


text:
Allow to run as root user

sudo check did not allow to be run as root user.

Closed via #186

authors: flexiondotorg plattrap

repo: wimpysworld/deb-get


text:
Cannot launch Supermium on Windows XP

The procedure entry point GetProductInfo could not be located in the dynamic link library KERNEL32.dll.
The VM was Windows XP SP3.

This version of Supermium is compatible only with Windows Vista SP2+. Support for Windows XP will be added in the future.

once new version of supermium (chromium 121) is release on this month, with xp support

There will be no XP support until the rebase on 121.


text:
servantes: allow multiple users to deploy to the same cluster

I tried this with and without kustomize.
You can see a version with kustomize here.
Either way, we're using m4 to get username in there. It's mostly a matter of whether it's worth adding a dep on kustomize to save a bit of repetition.
We could avoid m4 by using kustomize edit, e.g., cd fe/deployments && kustomize edit set namePrefix matt, but that modifies files on disk, and then we have to figure out how to restore them.
I've probably spent too much time on this already, and this is working, so I'm inclined to call this done for now, and worry about kustomize later.
(for posterity - I found this pretty extensive list of tools for templating k8s configs. I looked through a dozen or so and didn't see any that seemed like significant improvements over m4 for this use case).

@dbentley At some point, you expressed a desire to keep the servantes Tiltfile very non-DRY. Would you prefer inlining m4_yaml for each service?

LGTM

authors: dbentley landism

repo: windmilleng/servantes


text:
HardwareDevices: Smart data for NVMe drives

Code based on:
https://learn.microsoft.com/en-us/windows/win32/fileio/working-with-nvme-devices#example-nvme-get-log-pages-query
Description of SMART NVMe attributes:
https://en.wikipedia.org/wiki/Self-Monitoring,_Analysis_and_Reporting_Technology#Known_NVMe_S.M.A.R.T._attributes
How it looks like:

Should probably hide the irrelevant columns when displaying the NVME SMART data (Best, Raw, Raw (Hex),...)?

That would be great.
Unfortunately, hiding/deleting columns seems to interfere with saving column widths.
So in case if you have mix of NVMe and non-NVMe drives, column widths for Best/Raw/etc  won't get saved (if you have displayed Smart properties for NVMe drive).

repo: winsiderss/systeminformer


text:
[Bug]: Should not set an attribute named default on exports

🔎 Search Terms
default, exports, default transports
The problem
This causes some compilers to do the wrong thing, like vite、rollup:
before complie:
import { createLogger, format, transports } from 'winston'

after complied:
const require$$1 = require("winston");
const _interopDefaultLegacy = (e) => e && typeof e === "object" && "default" in e ? e : { default: e };
const require$$1__default = /* @__PURE__ */ _interopDefaultLegacy(require$$1);
const winston_1 = require$$1__default.default; // this is winston.default
winston_1.createLogger(...) // error, createLogger is empty, not function

What version of Winston presents the issue?
3.8.2
What version of Node are you using?
16.16.0
If this worked in a previous version of Winston, which was it?
No response
Minimum Working Example
No response
Additional information
No response

Related?

Related?

It could be the same problem, my temporary solution is to give winston a patch, like:
diff --git a/dist/winston.js b/dist/winston.js
index 688a98a230146269c8a6203ec05180c0cccc9b0d..c9d7aae3e67d2d61be6adfa81f0188bdb22c2382 100644
--- a/dist/winston.js
+++ b/dist/winston.js
@@ -146,7 +146,7 @@ Object.defineProperty(exports, 'exceptions', {
  * @type {Object}
  */

-Object.defineProperty(exports, 'default', {
+Object.defineProperty(exports, 'defaultTransports', {
   get: function get() {
     return {
       exceptionHandlers: defaultLogger.exceptionHandlers,
diff --git a/lib/winston.js b/lib/winston.js
index e62046e01cf1526df73da34b9a34cbd9031d1e1c..d490dd8151dacb189e0bedf15aef1588bfdbb844 100644
--- a/lib/winston.js
+++ b/lib/winston.js
@@ -150,7 +150,7 @@ Object.defineProperty(exports, 'exceptions', {
  * The default transports and exceptionHandlers for the default winston logger.
  * @type {Object}
  */
-Object.defineProperty(exports, 'default', {
+Object.defineProperty(exports, 'defaultTransports', {
   get() {
     return {
       exceptionHandlers: defaultLogger.exceptionHandlers,

authors: RodrigoProjects WhiteMinds

repo: winstonjs/winston


text:
Conscrypt not found on Aarch

I'm trying to use WireMock standalone in a linux/arm64 container (I'm building wiremock/wiremock-docker and hope to contrib the fixes back there)
It's building but at runtime I get the error:
java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-linux-aarch_64 in java.library.path
As this is standalone, I had thought the wiremock JAR was all I would need?

@tomakehurst  Did this make it into 2.32.0? Just checking because the 2.32.0 image (first ARM one) is giving me this error:
java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-linux-aarch_64 in java.library.path: [/usr/java/packages/lib, /lib, /usr/lib, /usr/lib64, /lib64]

/cc @rodolpheche

@ciaranmcnulty I just check with on a raspberry pi 3b+ and it works.
What the environment you're getting the error on ?

@rodolpheche MacBook M1 / Docker for Mac
I've been testing with an existing (private) project - what's the simplest test to do? Maybe the same as you did on your Pi

@ciaranmcnulty Could you tell me if you get the same issue with the nightly version ?

authors: ciaranmcnulty rodolpheche

repo: wiremock/wiremock


text:
Runing sbt test in Github Actions

As mentioned in #61 the tests are not being run by the project. Adding explicit sbt test step. Also renaming a step called sbt test to something else (as it does not run sbt test).

Thanks!

It seems to have worked:

authors: AlexITC mccartney

repo: wiringbits/my-photo-timeline


text:
[Bug] Glass Pane Blocks Incompatibe with Diagonal Windows

From the Log:
[05:19:19] [Worker-ResourceReload-0/WARN]: [fuzs.diagonalwindows.client.model.MultipartAppender#lambda$onPrepareModelBaking$2] Block 'Block{jello:deep_blush_stained_glass_pane}' is not using multipart models, diagonal connections will not be visible!
[05:19:19] [Worker-ResourceReload-0/WARN]: [fuzs.diagonalwindows.client.model.MultipartAppender#lambda$onPrepareModelBaking$2] Block 'Block{jello:mango_tango_stained_glass_pane}' is not using multipart models, diagonal connections will not be visible!
...repeats for all jello:color_stained_glass_pane
[05:19:19] [Worker-ResourceReload-0/INFO]: [fuzs.diagonalwindows.client.model.MultipartAppender#onPrepareModelBaking] Constructing diagonal block models took 143 milliseconds
Resulting in invisible textures:

My quick fix would be making multipart models for all the different stained glass pane colors to ship as an embedded resource pack, I just didn't know if there was any that could be done code wise without bloating load times. Regardless thank you for making this mod!

Such most likely comes down to the unique loading method imployed by Gelatin as the system attempts to duplicate the instances of loading the same model meaning the model is a DelegatingUnbakedModel and such will not be found thru the Diagonal Windows method of getting models.

I have attempted to add compatibility to properly modify the underlining model used within this commit b29c924cf6d24169b7f59e9887364fdb4e227040

I got it working in dev but when in production it just crashes out right. Will need more time to find a fix...

Ok all fixed, had bad mixin logic and also wrong mixin setup values but should work.

authors: Afrocntrik Dragon-Seeker

repo: wisp-forest/gelatin


text:
How to select where in array?

I want to select all Articles where i'm contributor. How i can do this?
In mongoose a can do it like this:
Article.find({contributors: [userId])

But i can't understand how to make it with blueprint api.
I tried to make it so:
GET /article?where={"contributors": ["123"]}

But it did not work. Do you have any ideas?
P.S. Please forgive me if the question will seem silly. I almost made a backend for my new project. But I can not deal with this request.

Hi @kulakowka , could you try GET /user/:youUserId?populate=articles

@pierreburgy That's not what I need. I want to specify a limit, sorting and so on. If I pick up the article with a population, I can not specify how many items to load. Also I can not specify which fields in the article should be populated. What if the user will be 1,000 articles, and I need only 10 per page.

@kulakowka: Your request is impossible on the current version of Strapi. You should create a new endpoint like GET /article/:relation/:relationId and add to your controller something like this:
// In your Article.js controller findRelation: function * () {   this.model = model;   try {     this.request.query.where = {};     this.request.query.where[this.params.relation] = this.params.relationId;     this.body = yield strapi.hooks.blueprints.find(this);   } catch (err) {     this.body = err;   } }

authors: Aurelsicoko kulakowka pierreburgy

repo: wistityhq/strapi

license: mit


text:
i18n(fr): Update integrations/integrations.mdx from #7628

Description (required)
Update integrations/integrations.mdx from #7628

+ [Site web et documentation Hookdeck](https://hookdeck.com/) - Astro / Vercel / Markdoc

Related issues & labels (optional)

Closes #
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
integrations/integrations.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

authors: astrobot-houston thomasbnt

repo: withastro/docs


text:
Be more explicit about cookie deletion

Description (required)
Whilst the word "delete" feels intuitive in the Astro.cookies API, it hides the fact when "deleting" a cookie, you're invalidating it by setting an expiry date in the past. It might be helpful to developers to call this out (it would have been really helpful to me when using this API 😅). I'm not sure of the correct wording so feel free to update or deem it unnecessary.

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/api-reference.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Happy to help! ✨


text:
i18n(zh-cn): Update nav.ts

Description (required)
Update nav.ts
Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
nav.ts
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

!coauthor

authors: astrobot-houston liruifengv


text:
Detox hangs on "Trying permissions" on CircleCI

Describe the bug
Attempting to run tests on CircleCI results in a timeout in the beforeAll hook. Logs reveal the last successful entry is "Trying permissions".
I set the following in my init.js:
before(async () => {
  await detox.init(config, { launchApp: false })
  await device.launchApp({
    permissions: {
      notifications: 'YES',
    },
  })
})

Works perfectly locally with the same environment settings.
To Reproduce

[x] I have tested this issue on the latest Detox release and it still reproduces

Environment (please complete the following information):

Detox: 12.11.0
React Native: 0.59.5
Node: 11.13.0
Device: iPhone X
Xcode: 10.2.0
iOS: 11.4
macOS: 10.14.4

Device and Verbose Detox Logs
Provide the device and "trace" Detox logs so we can understand what happened. You can obtain them by passing the loglevel param: detox test --loglevel trace
info Installing build/xxx/Build/Products/Debug-iphonesimulator/xxx.app
info Launching org.reactjs.native.example.xxx
org.reactjs.native.example.xxx: 34512
detox[34513] INFO:  [test.js] node_modules/.bin/mocha --opts e2e/mocha.opts --configuration ios.sim.debug --loglevel trace --debug-synchronization 100 --grep :android: --invert --artifacts-location "artifacts/ios.sim.debug.2019-06-17 20-23-39Z" "e2e"

detox[34516] INFO:  [DetoxServer.js] server listening on localhost:49358...
detox[34516] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:49358
detox[34516] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"login","params":{"sessionId":"b0b44eb6-5691-d7a6-e3a3-325fe65d48ff","role":"tester"},"messageId":0}
detox[34516] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=b0b44eb6-5691-d7a6-e3a3-325fe65d48ff
detox[34516] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=b0b44eb6-5691-d7a6-e3a3-325fe65d48ff
detox[34516] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"loginSuccess","params":{"sessionId":"b0b44eb6-5691-d7a6-e3a3-325fe65d48ff","role":"tester"},"messageId":0}

detox[34516] DEBUG: [exec.js/EXEC_CMD, #0] applesimutils --list --byType "iPhone X" --byOS "iOS 11.4"
detox[34516] DEBUG: [exec.js/EXEC_TRY, #0] Searching for device matching iPhone X, iOS 11.4...
detox[34516] TRACE: [exec.js/EXEC_SUCCESS, #0] [
  {
    "availabilityError" : "",
    "os" : {
      "bundlePath" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 11.4.simruntime",
      "availabilityError" : "",
      "buildversion" : "15F79",
      "availability" : "(available)",
      "isAvailable" : true,
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
      "version" : "11.4",
      "name" : "iOS 11.4"
    },
    "availability" : "(available)",
    "deviceType" : {
      "name" : "iPhone X",
      "bundlePath" : "\/Applications\/Xcode-10.2.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Developer\/Library\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone X.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-X"
    },
    "udid" : "D3541EC1-EFFD-4664-A3D9-08744EF887CD",
    "isAvailable" : true,
    "state" : "Booted",
    "name" : "iPhone X"
  }
]

detox[34516] DEBUG: [exec.js/EXEC_CMD, #1] applesimutils --list --byId "D3541EC1-EFFD-4664-A3D9-08744EF887CD"
detox[34516] TRACE: [exec.js/EXEC_SUCCESS, #1] [
  {
    "availabilityError" : "",
    "os" : {
      "bundlePath" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 11.4.simruntime",
      "availabilityError" : "",
      "buildversion" : "15F79",
      "availability" : "(available)",
      "isAvailable" : true,
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-11-4",
      "version" : "11.4",
      "name" : "iOS 11.4"
    },
    "availability" : "(available)",
    "deviceType" : {
      "name" : "iPhone X",
      "bundlePath" : "\/Applications\/Xcode-10.2.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Developer\/Library\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone X.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-X"
    },
    "udid" : "D3541EC1-EFFD-4664-A3D9-08744EF887CD",
    "isAvailable" : true,
    "state" : "Booted",
    "name" : "iPhone X"
  }
]

detox[34516] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBootDevice({ coldBoot: false,
  deviceId: 'D3541EC1-EFFD-4664-A3D9-08744EF887CD' })
detox[34516] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeUninstallApp({ deviceId: 'D3541EC1-EFFD-4664-A3D9-08744EF887CD',
  bundleId: 'org.reactjs.native.example.xxx' })
detox[34516] DEBUG: [exec.js/EXEC_CMD, #2] /usr/bin/xcrun simctl uninstall D3541EC1-EFFD-4664-A3D9-08744EF887CD org.reactjs.native.example.xxx
detox[34516] DEBUG: [exec.js/EXEC_TRY, #2] Uninstalling org.reactjs.native.example.xxx...
detox[34516] TRACE: [exec.js/EXEC_SUCCESS, #2]
detox[34516] DEBUG: [exec.js/EXEC_SUCCESS, #2] org.reactjs.native.example.xxx uninstalled
detox[34516] DEBUG: [exec.js/EXEC_CMD, #3] /usr/bin/xcrun simctl install D3541EC1-EFFD-4664-A3D9-08744EF887CD "/Users/distiller/mobile4/ios/build/xxx/Build/Products/Debug-iphonesimulator/xxx.app"
detox[34516] DEBUG: [exec.js/EXEC_TRY, #3] Installing /Users/distiller/mobile4/ios/build/xxx/Build/Products/Debug-iphonesimulator/xxx.app...
detox[34516] TRACE: [exec.js/EXEC_SUCCESS, #3]
detox[34516] DEBUG: [exec.js/EXEC_SUCCESS, #3] /Users/distiller/mobile4/ios/build/xxx/Build/Products/Debug-iphonesimulator/xxx.app installed
detox[34516] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeAll()
detox[34516] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeTerminateApp({ deviceId: 'D3541EC1-EFFD-4664-A3D9-08744EF887CD',
  bundleId: 'org.reactjs.native.example.xxx' })
detox[34516] DEBUG: [exec.js/EXEC_CMD, #4] /usr/bin/xcrun simctl terminate D3541EC1-EFFD-4664-A3D9-08744EF887CD org.reactjs.native.example.xxx
detox[34516] DEBUG: [exec.js/EXEC_TRY, #4] Terminating org.reactjs.native.example.xxx...
detox[34516] TRACE: [exec.js/EXEC_SUCCESS, #4]
detox[34516] DEBUG: [exec.js/EXEC_SUCCESS, #4] org.reactjs.native.example.xxx terminated
detox[34516] DEBUG: [exec.js/EXEC_CMD, #5] applesimutils --simulator D3541EC1-EFFD-4664-A3D9-08744EF887CD --bundle org.reactjs.native.example.xxx --restartSB --setPermissions notifications=YES
detox[34516] DEBUG: [exec.js/EXEC_TRY, #5] Trying to set permissions...
  1) "before all" hook

 0 passing (2m)
  1 failing

  1) "before all" hook:
     Error: Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
      at listOnTimeout (internal/timers.js:535:17)
      at processTimers (internal/timers.js:479:7)

detox[34516] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onAfterAll()
detox[34516] DEBUG: [DetoxServer.js/DISCONNECT] role=tester, sessionId=b0b44eb6-5691-d7a6-e3a3-325fe65d48ff
detox[34516] DEBUG: [DetoxServer.js/WS_CLOSE] Detox server connections terminated gracefully

I'm facing the same issue. Our circleci build is running on Xcode 10.1.0, otherwise similar config to @mglaze

Same here. Worked fine one\two weeks ago and without changing any configurations - fails with timeout on  "Trying permissions".
Circle CI config: https://github.com/RocketChat/Rocket.Chat.ReactNative/blob/37db977a22ad3da43ddd31d712e531bf8cc9ee41/.circleci/config.yml#L45
Circle CI job logs: https://circleci.com/gh/RocketChat/Rocket.Chat.ReactNative/8810

I ran into the same issue. Upgrading Detox to version 12.11.1, which has been released 4 days ago, fixed the issue for me. It apparently had to do with an old API of AppleSimUtils being used (see https://github.com/wix/Detox/releases/tag/12.11.1).
Hope this fixes your issues as well.

@thabemmz thanks! Upgrading detox to 12.11.1 solved the issue

Why is the "I have tested this issue on the latest Detox release and it still reproduces" checkbox ticked if it clearly isn't the case?

authors: IlarionHalushka LeoNatan mglaze peterjuras thabemmz

repo: wix/Detox


text:
Run tests with Github Actions

I wasn't able to find an answer for this so I'd like to ask here. Is it possible to run the tests without open the emulator? If so, how? If not, do you guys have any code snippet explaining how to set up an android emulator and running the tests with Github Actions?

researching it right now and found this issue, these are the most interesting repos i've found:
https://github.com/reime005/react-native-spaceviewer/blob/master/.github/workflows/android.yml
https://github.com/invertase/react-native-firebase/tree/master/.github/workflows

My issue is that I'm trying to use Java 11, so when I install it I'm not able to install the Android emulator. If I use Java 8 I'm able to install the emulator however my detox build doesn't work due to a library incompatibility.

Yeah I didnt have the chance to give it a try to java 11 yet. Im still using java 8 and its working fine for my case

@felipeaugusto1 Detox allows for the implementation of custom drivers - which, if sophisticated enough, could allow for the mocking of even a whole emulator / simulator. However, one must ask: what is the motivation for doing so?
As for Android stability on CI -- I'm finalizing a blogpost on this very painful issue. TL;DR stability can be achieved. I'll post it soon on our twitter account.

Last but not least, we haven't made the necessary adjustments for Java 11. @felipeaugusto1 Could you describe what the exact issue is when upgrading from 8 to 11? (emulator wouldn't start?)

@d4vidi happy to hear that.
About the java version: in a nutshell, I'm able to run all the tests locally on my laptop (with java 11). The only issue is running them on Github CI.
With java 8:
One of my app dependencies throw an error java.lang.AssertionError: annotationType(): unrecognized Attribute name MODULE (class com.sun.tools.javac.util.UnsharedNameTable$NameImpl)
With java 11:
I'm not able to install the android emulator. I get Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema. I believe this happens because I need to accept all the SDK licenses (which I haven't found a way to accept automatically by command line)

What you've described regarding Java 8 sounds highly specific. There's not much I can do about it, offhand.
As for Java 11, I leave to you to understand the connection between the error and the SDK licenses... 😄 But as for automated acceptance of liceneses, you can try:
yes | sdkmanager --licenses

I've already tried yes | sdkmanager --licenses and I get the same error

Then maybe the error is not associated with licenses, nevertheless?


text:
Fix release scripts and package

Description
This is a fix for buildkite CI

This pull request addresses the issue described here: #<?>
incorrect setting manual tag
missing ios/android in final package

In this pull request, I have …

For features/enhancements:

[ ] I have added/updated the relevant references in the documentation files.

For API changes:

[ ] I have made the necessary changes in the types index file.

Let's add the tag to the version name + tag counter (if it isn't latest), i.e. releasing version 20.0.0 with tag smoke should be 20.0.0-smoke.0, next 20.0.0+smoke will be 20.0.0-smoke.1 and so on..

Let's add the prerelease identifier: That is, releasing version 20.0.0 with tag smoke should be 20.0.0-smoke.0, next 20.0.0+smoke will be 20.0.0-smoke.1 and so on.. (same as we had with Jenkins)
Edit: using this: https://github.com/lerna/lerna/blob/main/commands/publish/README.md#--preid

while doing Release, need to select 'prerelease, premajor or preminor'. This will produce 'pre-' version.

Let's add the prerelease identifier: That is, releasing version 20.0.0 with tag smoke should be 20.0.0-smoke.0, next 20.0.0+smoke will be 20.0.0-smoke.1 and so on.. (same as we had with Jenkins)
Edit: using this: https://github.com/lerna/lerna/blob/main/commands/publish/README.md#--preid

while doing Release, need to select 'prerelease, premajor or preminor'. This will produce 'pre-' version.

Ohh right, so we already have it.. nice catch 🙂
That's really confusing (as we have already experienced 😅 ), let's add a note about this (maybe add some hint the release yaml?)

mmm, so after going over this line again: https://github.com/wix/Detox/blob/95700e061cbc73a8bdcdc9e731ecebbc74e8b5e2/scripts/ci.publish.js#L37
I'm thinking maybe it will be better to replace the prerelease, premajor and preminor options with a flag (checkbox) that indicates whether this is a pre-version (for instance, minor+isPreVersion=true => preminor).
Even better, to have all pre-versions with the same tag ("smoke" or "alpha" or something), and to deduce it from the pre-version indicator?
I mean, the isPreVersion/isSmokeVersion flag will determine whether this is a pre-version, and whether to add the smoke tag.. This way, we'll have only one source of truth.
What do you think @igorgn?
Is there a possible scenario where we're having a pre-version with latest tag or a regular version with not-latest tag?

authors: asafkorem igorgn


text:
Add --version argument to lianad an liana-gui

It should be nice to get the binary version by calling --version arg.

I hit that yesterday actually. It would be nice.
ALSO related, but on the GUI side, it would be great to have the version displayed in the installer. This will be extremely helpful for support.

authors: kloaec pythcoiner

repo: wizardsardine/liana


text:
عدم نمایش حجم مصرفی و باقی مانده کانفیگ پس از بکاپ ریزی

سلام
من سرور ربات رو از آلمان بردم رو فنلاند  همچنین دامینی که آیپی سرور ربات پشتش بود رو عوض کردم
بکاپ رو که از طریق پی اچ پی مای ادمین ریختم
کانفیگ هایی که قبل تعویض سرور ربات خریداری شده بودن از قسمت کانفیگ های من تاریخ شروع و انقضا نشون میده ولی توی بخش  حجمشون علامت تعجب میزنه.  حتی گزینه های  (تمدید / بروزرسانی لینک / قطع و دسترسی جدید / تغییر لوکیشن / کیوآرکد کانفیگ) رو هم نمیاره
اما کانفیگ هایی ک بعد از تعویض سرور ربات خریداری شدن توی قسمت کانفیگ های من هم تاریخ هم حجم مصرفی و مونده رو نشون میده
دلیل این اخطار چی میتونه باشه؟؟
اینم اسکرین شات (اولی قبل تعویض)  (دومی بعد تعویض سرور) هستش

سلام این مورد علامت تعجحب یعنی به سرور دسترسی نداره

سلام این مورد علامت تعجحب یعنی به سرور دسترسی نداره

من کلا یدونه سرور توی ربات دارم و ورژن و ادرس و یوزرنیم و پسورد پنل همون قبلی هستش ولی نمی دونم مشکل از کجاست
البته اینم بگم دامنه و ایپی که برا ربات بود رو عوض کردم یعنی ایپی سرور و دامنه ای ک ایپی سرور ربات پشتش بود در حین نصب ربات تغییر دادم
آیا می تونه مشکل از همین باشه؟؟

authors: RenasPasha wizwizdev

repo: wizwizdev/wizwizxui-timebot


text:
ارسال پیام اضافه  بعد از گزینه افزایش حجم و زمان

سلام من برای سرور هام از داخل ربات افزایش و حجم و زمان زدم ؛ الان هی هر دو دقیقه یکبار این پیام میاد : « عملیات هدیه حجم و زمان سرور سرور اختصاصی آلمان شروع شد »

سلام حل میشه

خودش حل میشه یا باید کار خاصی کرد ؟

باید اپدیت بدیم بعد


text:
تانل IPv6

ببخشید من یه سوال داشتم
اگه 2 تا سرور داشته باشم، یکی خارج و یکی داخل ایران، می تونم از ربات wizwiz استفاده کنم؟
در صورت امکان، پنل wizwiz رو باید روی کدوم یکی نصب کنم؟

you don't need two bots. you can manage both servers with one bot. install on any of them.
and if you don’t know how to modify this bot, then it’s better to separate the bot and the XUI.

داداش عنوانت به موضوعی که مطرح کردی نمیخوره اصلاح کن تا بتونن درست جوابت رو بدن
سرور خارج باید نصب بشه چون سرور باید ازاد باشه بتونه به تلگرام وضل بشه اما ایران چون تلگرام فیلتر هست روی سرور ایران بهت جواب نمیده

authors: EarlVadim mostafajafari00 parsa-ui


text:
Move ownership to JuliaGeo

I'm curious: will you prefer to deal with just the raster format in this repository? If so, a more suggestive name (e.g. Rasterio, or GDALRaster) might be better -- feel free to go wild with the naming! It'll also help you scope the responsibility to something more manageable?

[x] Provide test/runtests.jl
[x] Decide on scope of repository (and rename accordingly)
[ ] Register in METADATA
[ ] Move ownership to JuliaGeo

I think since what I've currently got in here is a solid (but not perfect) interface to raster I/O using GDAL, it's a good idea to clean it up and rename it to something (RasterIO.jl?) and then we have room for a GDAL.jl package which implements an API for a wider range of GDAL functionality.

I want to bump this discussion again. I haven't been super active in JuliaGeo stuff for a while, so I'm happy to transfer this to JuliaGeo or wherever else you would like it.

Hi Will, are you aware of the more recent developments in visr/GDAL.jl and yeesian/ArchGDAL.jl? They currently provide a quite extensive wrapping of GDAL/OGR.
I guess this package either can be updated, or explicitly unmaintained/archived, with links to alternatives. What is your preference?

This package was incredibly helpful in bootstrapping the design for GDAL.jl and packages that builds upon it, like ArchGDAL.jl which offers a more comprehensive scope of the functionality available in GDAL.
My suggestion at this point will first be decide if (i) you still want to maintain this package, and (ii) what functionality you wish to provide in it. If you don't wish to maintain this package, you won't have to do anything here.
If you wish to maintain a package for rasters, my recommendation is to re-write it to use either GDAL.jl or ArchGDAL.jl for building the gdal binaries, because Martijn and I intend to continue maintaining binaries and updating for subsequent versions of GDAL, and we'll be happy to pool efforts together.
It's also worth thinking about what user experience you'll like to achieve in this package that isn't otherwise provided by other packages, and use that as your guiding philosophy for deciding your priorities regarding this package.

Ah, yes. I hadn't been following the various updates very closely. I'll add a statement about the deprecation of this package to the README and point them to the more modern packages.
I just noticed that RasterIO is listed here: https://github.com/JuliaGeo/meta/wiki/Existing-Libraries and I don't want anyone to think they should be using this to handle raster data in Julia

Thanks Will! I've updated the wiki accordingly.

Yeah indeed wanted to echo @yeesian that this package was incredibly helpful in bootstrapping the other efforts, so thanks for that!

authors: visr wkearn yeesian


text:
Question / Suggestion: Consider using elm-hot?

klazuka/elm-hot provides the low-level features for hot swapping elm code with model state preservation between reloads (only 0.19).
Would it make sense for this project to use it?

I have actually discussed with klazula doing just that, but haven't gotten around to it. If you are interested in taking a stab at it feel free!

Ok, I have done some experimenting about hot swap and I was able to make it working in elm-live.
Few caveats:
The script injected by elm-live need to run in the browser BEFORE the elm compiled javascript. So I moved it before everything. I am afraid this is going to break the html so we probably need to be smarter here (adding it just after <head>?)
We need to extrapolate the relative path of the elm compiled javascript. For the moment I used one argument of elm make (--output) and one argument of elm-live (dir). This should probably be done in a more robust way
Probably we need a configuration flag to toggle this feature (simple)
The code for testing is available at https://github.com/lucamug/elm-live/tree/hot-swap
I will start using this version at work to see if it is reliable

This should be available in the new alpha! You can check the README for how to install it.

authors: lucamug mdevlamynck wking-io

repo: wking-io/elm-live


text:
class embeddings

Hello! Thanks for your work.
I've downloaded the nyu dataset and ran dump_nyu_text_embeddings.py, but the .pth file I got is different from what you gave in this repo(nyu_class_embeddings.pth). Did I do something wrong?

请问你现在解决这个问题了吗？另外我想获得pascal voc 2012的class embedding我应该运行什么py文件获得呢？谢谢

repo: wl-zhao/VPD


text:
Live status is not correctly updated

Rooms are still marked as "LIVE" long after the stream has finished. This is obvious when asking for a list of current streams when running the testing branch, but the same problem exists in the new-index branch.
Most likely what's happening is a Schedule object isn't getting removed from scheduled when its related download finishes. There is a go_live() function to turn LIVE status on, but no corresponding end_live(). Of course the original intent was probably for it to be removed from scheduled once the download completes. I could try to figure out why this is happening, or I can solve it with the upcoming consolidation of Schedule, Watcher, and Downloader.

In some cases at least, it's related to the failing downloads. After the end of the last ANN broadcast, the script checked to see if the room was still live, and got told it was. It restarted the download, and has been in a pinging loop ever since (going on 34 hours now).

Fixed in development branch.

repo: wlerin/showroom


text:
Update README

Closed PR #30 and re-opened, as there were some mis-operation in Git...
Changes

Added ToC
Added goreport shield(badge)
Updated examples
Added "Supported Features" instead of TODO list
Removed BMC link (this is no longer my lonely work)

@zemirco
Moved PR #30 to this one. Let me know if you have any idea to improve README more :smiley:

repo: wmnsk/gopcua


text:
Add Req.Request help functions

Req.Request.merge_headers/2:
Adding new headers can be easy with Req.Request.put_header/3, but when we want to update an existing header, we don't have a useful function to do that, so this could help to update an existing header with new a value, instead of appending a value to the header, making it a list than a String.
req = Req.new() |> Req.Request.put_header("my-header", "foo")
# => %Req.Request{..., headers: [..., {"my-header", "foo"}, ...], ...}

req = Req.Request.merge_headers(req, [{"my-header", "var"}])
# => %Req.Request{..., headers: [..., {"my-header", "var"}, ...], ...}

Req.Request.remove_private/2:
Thinking about removing a key from the private map from Req.Request could help to change the actual state of a step (custom or not) to keep his flow as he want to.
req = Req.new() |> Req.Request.put_private(:foo, :bar)
# => %Req.Request{..., private: %{foo: :bar}, ...}

req = Req.Request.remove_private(req, :foo)
# => %Req.Request{..., private: %{}, ...}

WDYT?

put_headers is in! Let's hold off on delete_private for now.

authors: aleDsz wojtekmach

repo: wojtekmach/req


text:
TopBar background color (corner bug)

Bug report
There is a very thin border that Is bothering me on top bar
Scenario 1 (with corner bug)
Code
WoltModalSheetPage(
  hasSabGradient: false,
  forceMaxHeight: true,
  topBar: Container(
    color: infoBlue,
    child: // etc ...

Image: (check corners)

Scenario 2 (no corner bug)
Code
WoltModalSheetPage(
  hasSabGradient: false,
  forceMaxHeight: true,
  backgroundColor: infoBlue,
  topBar: Container(
    child: // etc ...

Image:

Expected behavior
I cannot use second code because the whole modal with have "infoBlue" color. I expect a smooth corner without any white glitches.

Do you see difference if you set the clip behavior in the theme data to Clip.antiAliasWithSaveLayer in https://github.com/woltapp/wolt_modal_sheet/blob/main/lib/src/theme/wolt_modal_sheet_theme_data.dart#L32

antiAlias Vs antiAliasWithSaveLayer

This is a valid question. The Flutter SDK defaults to Clip.none. I can't recall the reasoning but I think we can default to Clip.antiAliasWithSaveLayer. What do you think @TahaTesser?

@vicenterusso Here is the PR: #164

Perfect!

This is a valid question. The Flutter SDK defaults to Clip.none. I can't recall the reasoning but I think we can default to Clip.antiAliasWithSaveLayer. What do you think @TahaTesser?

It defaults to none as clipping is not necessary when you don't provide a shape, but in the package, if you're always providing a shape then you can definitely the change the default

authors: TahaTesser ulusoyca vicenterusso


text:
Add missing types

Description
This place was missing the types, so you could actually run into an issue where you pass incompatible types.
You could actually test this by enabling the strong language analyzer options:
analyzer:
  language:
    strict-raw-types: true
    strict-inference: true
    strict-casts: true

But I don't know whether that's something you want to do. I've briefly tried to enable them, and it shows a lot more issues. That's also why I didn't enable them as a test for these changes.
Related Issues
none
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes tests for all changed/updated/fixed behaviors.
[x] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] The package compiles with the minimum Flutter version stated in the pubspec.yaml

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

While technically this is a breaking API change (you could pass an unrelated type), it's not a change in behavior (only passing correct types would make the code work)

👑

Is there anything left for me to do?

Is there anything left for me to do?

We let the author merge after approval but it is not mentioned in the Contributing guideline. AFter the refactor, we will need to add more rules.

I don't have the rights to merge the PR, or maybe it's due to the failing "check for tests" job?

authors: ueman ulusoyca


text:
Dict variables

Completely missed from ui

Has this been implemented already?
thanks

authors: IlgarLunin ljilekor

repo: wonderworks-software/PyFlow


text:
workflow config view not colapsable

e.g. https://ci.woodpecker-ci.org/repos/3780/pipeline/6355/config
version: "next-2ba64dcb
if you click on the header the view should be able to un-/colapse (hide it's content part)

Hi Can I work on this?

Sure, just submit a pull :)

Fixed by: https://github.com/woodpecker-ci/woodpecker/pull/2166

authors: 6543 vinay-nb xoxys

repo: woodpecker-ci/woodpecker


text:
github-env: refinements

The github-env audit merged in #192 is barebones. Some things we should do to improve it:

[ ] Use a regex to match suspicious >> $GITHUB_ENV shell lines; this won't be perfect, but it'll avoid false positives like echo $GITHUB_ENV.

Candidate expression: ^.+\s*>>?\s*"?\$\{?GITHUB_ENV\}?"?.*$
We should also support PowerShell run: bodies, which are their own mess.

[ ] Handle actions/github-script bodies as well, since people are likely to modify GITHUB_ENV there too.

For PowerShell, we need to detect patterns like ... | Out-File -FilePath $env:GITHUB_ENV -Append and ... >> $env:GITHUB_ENV.

Another, more serious option here would be to use tree-sitter grammars as necessary:

https://crates.io/crates/tree-sitter-bash
https://github.com/airbus-cert/tree-sitter-powershell (no Rust crate yet)

@woodruffw It seems that Python is also a shell option 🙀

Oh yeah, it gets way worse 🙂 -- there's no way we'll end up being fully general here. But I bet we can come up with some good patterns there as well.

I gave a try on tree-sitter-bash here. Hope it is in the right direction

Thanks, that looks amazing! I'll do a more detailed review in a bit, but that approach of popping nodes from the stack is great.

shell: cmd is also a possibility, and in that case the pattern will look something like:
echo NAME=VAR >> %GITHUB_ENV%

repo: woodruffw/zizmor


text:
Unexpected capital letters returned for certain capitalized misspellings

For steps to quickly reproduce with a related gist, see the original issue I've opened on retext-spell.
TLDR: see PR 38 and PR 39 that I've opened against this repo.
Background
I have found over 200 5-letter dictionary words for which retext-spell produces suggestions such as the following:

It suggests "ThreE" when given "Threa", or in general /^Thre[f-ln-racuvxyz]$/
It suggests "MaJor" when given "Maxor" or in general /^Ma[d-ho-raluwxz]or$/
It suggests "ChYme" when given "Cheme" or in general /^Ch[d-hj-np-xabz]me$/

There is nothing to suggest this problem is limited to 5-letter dictionary words, as I've stumbled across the following:

It suggests "TinpOt" when given "Tinph" or in general /^Tinp[bcdfhlmqvx]$/

One example I've tested

assume the input word is "Twinz"
assume character ais "t" at index 0

"T" is uppercase in "Twinz".
The first group is "qwertzuop".

We know the position of "t" in the group is 4.
We split the word "Twinz" at position 4 into before="Twin" and after = ""
We iterate thrice to group character b="e"

We select an uppercase "E" for index 4 because "T" was uppercase at index 0

This is how we arrive at the confusing suggestion of "TwinE".
Problem
When creating the initial array of edits based on keyboard groups, the current logic of nspell is as follows:

For a given character in an input word, we convert it to lowercase to obtain a

Check whether character a is uppercase in the input word
Iterate through all the keyboard groups containing character a

Store the position of character a within the group
Split the input word at character a's position within the group (note, this defaults to splitting at the very end of the word when the character's position in the group exceeds the length of the input word)
Iterate through each group character b != a

Select an uppercase character b if the input character a is uppercase

This results in uppercase characters inserted at seemingly random positions in the text because the position of character a within the group is not the index of character a within the input word.
Note, the notion of "Keyboard groups" doesn't really make sense in the current approach in main. The suggest function inserts each replacement character at a position (of a in group) that is unrelated to the original position (of a in word). This "root problem" is ignored in PR 38 and addressed in PR 39.

I see that both PRs are WIP: what can we do to make them actionable? How can I help?

The most helpful feedback you could give right now would be how I should approach the test cases:

Is it OK if the tests that fail are essentially the same except that the suggestions are in a different order?

After that, I'd like to hear your thoughts on what seems to be broken keyboard groups logic. For example, the input Ghandi leads to an initial "edit" of Grandi even though h and r are not in the same keyboard group. Is it even important that the keyboard groups do not work as expected? Essentially, if that issue were fixed (like in PR #39), we would not need a separate fix for this capitalization issue.
I've only set the WIP status because the tests are failing. If backwards compatibility for certain arbitrary test cases is not an issue, then we would just need to update the tests. PR #38 is failing the tests less severely than PR #39, though I think PR #39 makes more logical sense.
I've spent some time today looking into how to make PR #38 match the tests more closely, and it really seems that one test case in particular (test #46) is really reliant on replacements made by what seems like a buggy implementation of replacements based on keyboard groups.

I see that both PRs are WIP: what can we do to make them actionable? How can I help?

The most helpful feedback you could give right now would be how I should approach the test cases:

Is it OK if the tests that fail are essentially the same except that the suggestions are in a different order?

After that, I'd like to hear your thoughts on what seems to be broken keyboard groups logic. For example, the input Ghandi leads to an initial "edit" of Grandi even though h and r are not in the same keyboard group. Is it even important that the keyboard groups do not work as expected? Essentially, if that issue were fixed (like in PR #39), we would not need a separate fix for this capitalization issue.
I've only set the WIP status because the tests are failing. If backwards compatibility for certain arbitrary test cases is not an issue, then we would just need to update the tests. PR #38 is failing the tests less severely than PR #39, though I think PR #39 makes more logical sense.
I've spent some time today looking into how to make PR #38 match the tests more closely, and it really seems that one test case in particular (test #46) is really reliant on replacements made by what seems like a buggy implementation of replacements based on keyboard groups.

I see that both PRs are WIP: what can we do to make them actionable? How can I help?

See a comment I made on PR #39

I see that both PRs are WIP: what can we do to make them actionable? How can I help?

See a comment I made on PR #39

repo: wooorm/nspell