improve the git-scm url's in docs and sample.ini

The url includes the version of git, which is not required to view the page. If you open the page without the version you get the current version and it's possible to switch the used version.
I've also modified the cheat-sheet from the docs section to make the configuration easier without looking at the sample ini.
Hope it's okay to target two parts of the project with one PR that targets the same topic?

LGTM
On Tue, Dec 4, 2018, at 10:22 AM, Roman wrote:

The url includes the version of git, which is not required to view the
page. If you open the page without the version you get the current
version and it's possible to switch the used version.> I've also modified the cheat-sheet from the docs section to make the
configuration easier without looking at the sample ini.> Hope it's okay to target two parts of the project with one PR that
targets the same topic?>
You can view, comment on, or merge this pull request online at:

https://github.com/go-gitea/gitea/pull/5467

Commit Summary

remove old git-version from git-scm url in app.ini
docs: mention the git-scm url for git configs> File Changes

M custom/conf/app.ini.sample[1] (4)
M docs/content/doc/advanced/config-cheat-sheet.en-us.md[2] (4)> Patch Links:

https://github.com/go-gitea/gitea/pull/5467.patch
https://github.com/go-gitea/gitea/pull/5467.diff> — You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub[3], or mute the
thread[4].

Links:

https://github.com/go-gitea/gitea/pull/5467/files#diff-0
https://github.com/go-gitea/gitea/pull/5467/files#diff-1
https://github.com/go-gitea/gitea/pull/5467
https://github.com/notifications/unsubscribe-auth/AAKBZcNU8QOuar-OkD6yDvmpK5e3_Z01ks5u1pMogaJpZM4ZA4T9

Codecov Report

Merging #5467 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5467      +/-   ##
==========================================
- Coverage   37.59%   37.56%   -0.03%
==========================================
  Files         317      317
  Lines       46824    46824
==========================================
- Hits        17602    17591      -11
- Misses      26726    26734       +8
- Partials     2496     2499       +3

Impacted Files
Coverage Δ

models/repo_indexer.go
44.49% <0%> (-3.82%)
:arrow_down:

models/repo_list.go
63.29% <0%> (-1.27%)
:arrow_down:

Continue to review full report at Codecov.

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


[zh-cn] Reference files to sync task-32

related: https://github.com/kubernetes/website/issues/39987

Thanks
/lgtm
/approve


What happened to older android build processes?

inAppBrowser crashes immediately on Android and I always used an old webplatform build process to get past it, now I cannot use older build processes and aren't able to update our app.
Is there a way to get the older build processes back?

+1
We can't update our android app too with the new Android build.


adding special instruction to llm model.

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.

Example Code
here is my code:
import sqlalchemy as sal
import os, sys, openai
import pandas as pd
import constants
from langchain.sql_database import SQLDatabase
from langchain.llms.openai import OpenAI
from langchain_experimental.sql import SQLDatabaseChain
from sqlalchemy import create_engine
from langchain.chat_models import ChatOpenAI
from typing import List, Optional
from langchain.agents.agent_toolkits import SQLDatabaseToolkit
from langchain.callbacks.manager import CallbackManagerForToolRun
from langchain.chat_models import ChatOpenAI
from langchain_experimental.plan_and_execute import (
PlanAndExecute,
load_agent_executor,
load_chat_planner,
)
from langchain.sql_database import SQLDatabase
from langchain.text_splitter import TokenTextSplitter
from langchain.tools import BaseTool
from langchain.tools.sql_database.tool import QuerySQLDataBaseTool
from secret_key import openapi_key
from langchain.prompts import PromptTemplate
os.environ['OPENAI_API_KEY'] = openapi_key
from urllib.parse import quote_plus
server_name = constants.server_name
database_name = constants.database_name
username = constants.username
password = constants.password
encoded_password = quote_plus(password)
connection_uri = f"mssql+pyodbc://{username}:{encoded_password}@{server_name}/{database_name}?driver=ODBC+Driver+17+for+SQL+Server"
engine = create_engine(connection_uri)
def chat(question, sql_format):
greetings = ["hi", "hello", "hey"]

if question.lower() in greetings:
    return "Hello! How can I assist you today?"

model_name="gpt-3.5-turbo-16k"
db = SQLDatabase(engine, view_support=True, include_tables=['EGV_emp_departments_ChatGPT'])
llm = ChatOpenAI(temperature=0, verbose=False, model=model_name)
answer = None

if sql_format==False:

    db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True)

    answer = db_chain.run(question)

else:
    db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True , return_sql =True)

    sql_query = db_chain.run(question)
    print("SQLQuery: "+str(sql_query))
    # result = engine.execute(sql_query)

    result_df = pd.read_sql(sql_query, engine)
    if result_df.empty:
        return "No results found"

    answer = result_df.to_dict()

PROMPT = """
Given an input question, first create a syntactically correct mssql query to run,
then look at the results of the query and return the answer.Return the answer in a sentence form alsways.
The question: {db_chain.run}
"""
prompt_template = """
Use the following pieces of context to answer the question at the end. If you don't know the answer,
just say that you don't know, don't try to make up an answer. Return the answer in a sentence form alsways.

{context}

Question: {question}
Helpful Answer:"""

def handle_greetings(context, question):
    greetings = ["hi", "hello", "hey"]
    if any(greeting in question.lower() for greeting in greetings):
        return "Hello! How can I assist you today?"
    else:
        return None

PROMPT = PromptTemplate(
    template=prompt_template,
    input_variables=["context", "question"],
    preprocessor=handle_greetings
)

def split_text(text, chunk_size, chunk_overlap=0):
    text_splitter = TokenTextSplitter(
        chunk_size=chunk_size, chunk_overlap=chunk_overlap
    )
    yield from text_splitter.split_text(text)

class QuerySQLDatabaseTool2(QuerySQLDataBaseTool):
    def _run(
        self,
        query: str,
        run_manager: Optional[CallbackManagerForToolRun] = None,
    ) -> str:
        result = self.db.run_no_throw(query)

        return next(split_text(result, chunk_size=14_000))

class SQLDatabaseToolkit2(SQLDatabaseToolkit):
    def get_tools(self) -> List[BaseTool]:
        tools = super().get_tools()
        original_query_tool_description = tools[0].description
        new_query_tool = QuerySQLDatabaseTool2(
            db=self.db, description=original_query_tool_description
        )
        tools[0] = new_query_tool

        return tools

# return db_chain.run(question)
return answer

def chain1(question):
text = chat(question,False)
return text

def chain2(question):
query = chat(question,True)
return query

answer=chat("what is Ganesh D desigation")
print(answer)
Define a function named chain1 that uses the chat function without SQL format
def chain1(question):
text = chat(question, False)
return text
Define a function named chain2 that uses the chat function with SQL format
def chain2(question):
query = chat(question, True)
return query
chain1("give me aadhaar number of all Jayachitra R") #, give answer in sentence form")
print(chain1)
Description
how to added instruction in the llm model to personalize the output request by modify the prompt here or add other way to tell the llm model to give the answer in sentence form or any other instructions.
here is my code:
import sqlalchemy as sal
import os, sys, openai
import pandas as pd
import constants
from langchain.sql_database import SQLDatabase
from langchain.llms.openai import OpenAI
from langchain_experimental.sql import SQLDatabaseChain
from sqlalchemy import create_engine
from langchain.chat_models import ChatOpenAI
from typing import List, Optional
from langchain.agents.agent_toolkits import SQLDatabaseToolkit
from langchain.callbacks.manager import CallbackManagerForToolRun
from langchain.chat_models import ChatOpenAI
from langchain_experimental.plan_and_execute import (
PlanAndExecute,
load_agent_executor,
load_chat_planner,
)
from langchain.sql_database import SQLDatabase
from langchain.text_splitter import TokenTextSplitter
from langchain.tools import BaseTool
from langchain.tools.sql_database.tool import QuerySQLDataBaseTool
from secret_key import openapi_key
from langchain.prompts import PromptTemplate
os.environ['OPENAI_API_KEY'] = openapi_key
from urllib.parse import quote_plus
server_name = constants.server_name
database_name = constants.database_name
username = constants.username
password = constants.password
encoded_password = quote_plus(password)
connection_uri = f"mssql+pyodbc://{username}:{encoded_password}@{server_name}/{database_name}?driver=ODBC+Driver+17+for+SQL+Server"
engine = create_engine(connection_uri)
def chat(question, sql_format):
greetings = ["hi", "hello", "hey"]

if question.lower() in greetings:
    return "Hello! How can I assist you today?"

model_name="gpt-3.5-turbo-16k"
db = SQLDatabase(engine, view_support=True, include_tables=['EGV_emp_departments_ChatGPT'])
llm = ChatOpenAI(temperature=0, verbose=False, model=model_name)
answer = None

if sql_format==False:

    db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True)

    answer = db_chain.run(question)

else:
    db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True , return_sql =True)

    sql_query = db_chain.run(question)
    print("SQLQuery: "+str(sql_query))
    # result = engine.execute(sql_query)

    result_df = pd.read_sql(sql_query, engine)
    if result_df.empty:
        return "No results found"

    answer = result_df.to_dict()

PROMPT = """
Given an input question, first create a syntactically correct mssql query to run,
then look at the results of the query and return the answer.Return the answer in a sentence form alsways.
The question: {db_chain.run}
"""
prompt_template = """
Use the following pieces of context to answer the question at the end. If you don't know the answer,
just say that you don't know, don't try to make up an answer. Return the answer in a sentence form alsways.

{context}

Question: {question}
Helpful Answer:"""

def handle_greetings(context, question):
    greetings = ["hi", "hello", "hey"]
    if any(greeting in question.lower() for greeting in greetings):
        return "Hello! How can I assist you today?"
    else:
        return None

PROMPT = PromptTemplate(
    template=prompt_template,
    input_variables=["context", "question"],
    preprocessor=handle_greetings
)

def split_text(text, chunk_size, chunk_overlap=0):
    text_splitter = TokenTextSplitter(
        chunk_size=chunk_size, chunk_overlap=chunk_overlap
    )
    yield from text_splitter.split_text(text)

class QuerySQLDatabaseTool2(QuerySQLDataBaseTool):
    def _run(
        self,
        query: str,
        run_manager: Optional[CallbackManagerForToolRun] = None,
    ) -> str:
        result = self.db.run_no_throw(query)

        return next(split_text(result, chunk_size=14_000))

class SQLDatabaseToolkit2(SQLDatabaseToolkit):
    def get_tools(self) -> List[BaseTool]:
        tools = super().get_tools()
        original_query_tool_description = tools[0].description
        new_query_tool = QuerySQLDatabaseTool2(
            db=self.db, description=original_query_tool_description
        )
        tools[0] = new_query_tool

        return tools

# return db_chain.run(question)
return answer

def chain1(question):
text = chat(question,False)
return text

def chain2(question):
query = chat(question,True)
return query

answer=chat("what is Ganesh D desigation")
print(answer)
Define a function named chain1 that uses the chat function without SQL format
def chain1(question):
text = chat(question, False)
return text
Define a function named chain2 that uses the chat function with SQL format
def chain2(question):
query = chat(question, True)
return query
chain1("give me aadhaar number of all Jayachitra R") #, give answer in sentence form")
print(chain1)
System Info
python = 3.11
langchain= latest
Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[X] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

llm = ChatOpenAI(temperature=0, verbose=False, model=model_name, prompt_template=PROMPT)
^^^^^^
UnboundLocalError: cannot access local variable 'PROMPT' where it is not associated with a value

Hi,
use the following code:
from langchain.prompts.chat import ChatPromptTemplate
final_prompt = ChatPromptTemplate.from_messages(
[("system", """
You are a helpful AI assistant expert in identifying the relevant topic from the user's question about Donation amount,  """),
("user", "{question}\n ai: "),
]
)
llm = ChatOpenAI(temperature=0, streaming=True)
db = SQLDatabase.from_uri(f"sqlite:///{DB_PATH}", sample_rows_in_table_info=3)
db_chain = SQLDatabaseToolkit(db=db, llm=llm)
mrkl = create_sql_agent(
llm=llm,
agent=AgentType["ZERO_SHOT_REACT_DESCRIPTION"],
verbose=True,
toolkit=db_chain,
extra_tools=tools,
handle_parsing_errors=True
)
answer = mrkl.run(final_prompt.format(question=user_input))
print(answer)
This code helps you to add special instructions to the LLM.


Build is failing due to jcenter dependency disappearing

Our build has been failing since yesterday and pointing the finger at react-native-share
* What went wrong:
A problem occurred configuring project ':react-native-share'.
> Could not resolve all files for configuration ':react-native-share:classpath'.
   > Could not find lint-gradle-api.jar (com.android.tools.lint:lint-gradle-api:26.1.2).
     Searched in the following locations:
         https://jcenter.bintray.com/com/android/tools/lint/lint-gradle-api/26.1.2/lint-gradle-api-26.1.2.jar

It looks like this dependency has disappeared from bintray, though the .pom file is still in the folder
https://jcenter.bintray.com/com/android/tools/lint/lint-gradle-api/26.1.2/
https://jcenter.bintray.com/com/android/tools/lint/lint-gradle-api/26.1.2/lint-gradle-api-26.1.2.jar
{
  "errors" : [ {
    "status" : 404,
    "message" : "Could not find resource"
  } ]
}

I realise this is likely to be an upstream issue, but am hoping that someone here has an idea what we can do to fix this, since it's coming through react-native-share?
Environment

React Native version: 0.53.3
React Native platform + platform version: Android build
Gradle version:  4.4

react-native-share
Version: 1.1.2

+1
Adding google() on build.graddle fix the issue:
buildscript {
    repositories {
        google()
        jcenter()
        maven {
            url 'https://maven.google.com/'
            name 'Google'
        }
         maven { url 'https://maven.fabric.io/public' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.3'
        classpath 'com.google.gms:google-services:4.0.1'
        classpath 'io.fabric.tools:gradle:1.25.4'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

Also I have notice that the code on master is different, maybe there are a pending release?

Hmmm that doesn't seem to have helped us.
our allprojects config was already configured that way, and I also tried adding to the buildscript config but the issue persisted.
 I'll do some investigation and see if we can bodge this up for now

If bintray isn't carrying the android support libraries for some reason, there's nothing gradle (the android build/package tool) can do if you don't provide it a way to resolve the dependency somehow. It's as if npmjs.org decided to delete react-native-share, what can we do? Point it to somewhere that has it.
Who has this dependency guaranteed? The google repo. So somewhere the google repo isn't in the resolution path, and must be added (preferably first - they're more reliable than most...)
Adding the google repository is either via 'google()' in modern gradle versions or the
maven {
            url "https://maven.google.com/"
        }

...stanza in older gradles (you don't need both - it's just that it didn't get a first-class name of google() until gradle 4.1) is going to be what resolves it but you'll need to add it in the "main project"
Then the question is where. Looks to me like this module has a valid pointer to google's maven repo in 1.1.2:
https://github.com/mikehardy/react-native-share/blob/83a3ec5e7bbc77f6681f0a96779692ba9a0e283e/android/build.gradle
If you want to check to see if the code in master will work, regardless, you can alter the react-native-share dependency as a test to "git+https://github.com/react-native-community/react-native-share.git" and run an npm install - that's how you ask npm (or yarn) to pull github master of any dependency, as opposed to using release packages.
I don't see a difference between the current release and master though so I think this dependency problem might be elsewhere?

Confirmed as above, putting react-native-share's google() line above jcenter() fixes the issue. For now we are copying over a modified build.gradle into node-modules are part of the build process.
This isn't a great long term solution but should tide us over until a more robust release from this library can be released

Interesting - so if gradle (or maybe just the specific version of gradle used) gets a POM from a repo but the artifact 404s, it treats that as a failure meaning dependency order is very important. The official docs recommend google() at the top and that's what I've always done so this hasn't bitten me. I was the last to touch this file though, @jgcmarins - would you like a PR that flips the jcenter()/google() dependency?
I'm unable to find anything authoritative from the two parties (google or jcenter) on what order they recommend, but the gradle doc is explicit that order matters, so I think we get to make our own decision on who is more reliable with this issue seeming to be good evidence google() should go first...
Master still has jcenter() first:
https://github.com/mikehardy/react-native-share/blob/master/android/build.gradle

I've made a PR available in case it's wanted. Note if using modern gradle (3.2+) with  less-than-bleeding-edge React Native (<0.57) you will be missing a compatibility addition where react-native copies release build bundles into the new location gradle expects it: https://github.com/facebook/react-native/commit/a4fed6e203efd481175e61b7d2aa1c2b037a4279
In my own project I am not using RN57 yet, so I use their build-step workaround where for android release builds I pre-build the bundle into android/assets like so in the scripts area of package.json:
    "android-bundle": "node node_modules/react-native/local-cli/cli.js bundle --platform android --dev false --entry-file index.android.js --bundle-output android/kscore/src/main/assets/index.android.bundle --assets-dest android/kscore/src/main/res/",

Thank you very much @mikehardy
Also I have noticed that with the current order (with jcenter() first) and upgrading the graddle version it works:
com.android.tools.build:gradle:3.1.3
So we can conclude that is an issue related to version 3.1.2 and jcenter() dependency

hey guys, thanks for this feedback
https://github.com/react-native-community/react-native-share/pull/387 would fix?
we can merge it into master, then anyone can test it?
if it's ok, we can have a new release

Yes @jgcmarins
I can confirm that the branch is working

thanks everyone
let's test this on master branch and release a new version during the day

done:
https://github.com/react-native-community/react-native-share/releases/tag/v1.1.3
https://www.npmjs.com/package/react-native-share

@AdriaRios thanks

If it's give "Could not find method google() for arguments [] on repository container" error, replace google() to maven { url "https://maven.google.com" } in react-native-share/android/build.gradle

If it's give "Could not find method google() for arguments [] on repository container" error, replace google() to maven { url "maven.google.com" } in react-native-share/android/build.gradle

Yes - this will happen if using gradle version lower than 4.1 per the docs:
https://developer.android.com/studio/build/dependencies#google-maven
Gradle 4.1 is about 1.5years old now though, they just released 5.0 which I haven't tried yet, but 4.10.2 is nice - I'd move up


[Fix #11652] Generate inherit_from correctly also with ERB

The problem with the existing algorithm, for generating the inherit_from line in --auto-gen-config runs, was that we started by removing the inherit_from (if present) and then inserted it later.
The things we must deal with in the algorithm are

there could be a pre-existing inherit_from in .rubocop.yml, or not
there could be a YAML doc start ---, or not
there could be inheritance from one or multiple files

A more robust approach to the removing, generating, and re-inserting is to assume that any pre-existing inherit_from directive is already in the right place. By replacing it with a placeholder and later replacing the placeholder with the new inheritance directive, we will get it right without much effort.

Great fix!


Improve dockerfile (depends on: #215)

This should help issue #203.

This new Dockerfiles should allow a better layering. For instance, if only files in tests/src/ are modified, it only reconstruct the last layer (and it doesn't rebuild the qflex layer).

I think using a .dockerignore file is the canonical solution to this.

.dockerignore would help regarding not copying compiled libraries as *.o, but this wouldn't help with a better layering. With the latest modifications, changes to test/src/ won't affect layers that depends on src/ only. On the contrary, modifications to src/ would trigger docker to rebuild layers that depends upon src/ and tests/src.


[Build System: CMake] Always copy the apinotes into the build directory when the apinotes directory is included via SWIFT_INCLUDE_APINOTES.

Follow-up to #24419, we should add the copy_apinotes target to the default build target.

@swift-ci please test


PPC64LE Conda Install

Hi,
Is there any chance Open Force Field might get a PPC64LE or noarch installation option?
Thanks!

We'd like to do one or both of these at some point in the future but, unfortunately, it's probably not something we can do in the short term. The OpenFF toolkit is pure Python, so it comes down tot he dependencies. Most are distributed as noarch and/or ppc64le, but some important ones don't seem to be: RDKit and OpenMM stick out to me at a glance. They can easy probably be compiled locally but I have not tried myself and don't have access to a PowerPC machine at the moment to test.  I'm not sure about the OpenEye toolkits, if you happen to have a license.

(cc @j-wags @jaimergp  @peastman)
We are actively working to migrate OpenMM to conda-forge, where we hope to be able to support both ppc64le and ARM packages. Hopefully this can be wrapped up quickly.
We might open an issue on the https://github.com/conda-forge/rdkit-feedstock to see if they could add ppc64le and ARM support as well, and at least find out what the roadblocks are.

Hi Matt and John,
Thank you for the information. I see the RDKit issue you mention. As for OpenMM (and ParmEd), I managed to get them working on a Summit-style cluster with these Conda installations:
conda install https://anaconda.org/omnia-dev/openmm/7.4.0/download/linux-ppc64le/openmm-7.4.0-py37_cuda101_0.tar.bz2
conda install -c jchodera parmed

It looks like I will be able to pre-parametrize our ligands on an x86 system then move them over to ppc64le systems using the magic of serialization.
As a side note, I'd just like to say that the work you folks are doing is absolutely outstanding :)
Thank you all again,
Gabriel

I had built those manually using recipes I created for building on Summit:
https://github.com/inspiremd/conda-recipes-summit
Now that conda-forge has a mechanism for building for ppc64le and arm, however, we're very much hoping to get this working ASAP.

Opened an issue on the RKDit feedstock: https://github.com/conda-forge/rdkit-feedstock/issues/52

You can track the progress for ppc64le and aarch CF packages in this PR:
https://github.com/conda-forge/openmm-feedstock/pull/23
Note these are not released, so you would need to run conda build recipe on that repo on Summit to manually compile it yourself.
There are some issues with the CPU platform on ppc64le if it's compiled with GCC 8.x, but GCC 7.x works fine. Other platforms are not affected.

Updates on this:

OpenMM 7.5 will work ok with ppc64le - see https://github.com/conda-forge/openmm-feedstock/pull/23
RDKit is now being distributed for ppc64le on conda-forge - see https://github.com/conda-forge/rdkit-feedstock/pull/54
AmberTools too - see https://github.com/conda-forge/ambertools-feedstock/pull/16

Having OpenMM on conda-forge is still ongoing, but we will get there. Is any other critical dependency I am missing?

This is now a bit stale - this probably works now given the improvements to upstream packaging, but it still might not.
If this is still desired and it does not work, please re-open.


 Why not to mimic this very convenient behavior? It would be nice to have a easy way to setup authentication for the mongo container, per example.

If you set MONGO_INITDB_ROOT_USERNAME and MONGO_INITDB_ROOT_PASSWORD during the initial container startup, the entrypoint script (https://github.com/docker-library/mongo/blob/d1c2ba0001233372a1ab8515ee5e1e968e0d64f9/3.4/docker-entrypoint.sh) should configure a root user for you. :+1:

Thanks @tianon Then this issue should be related to having those options documented. I'll open another.


Suggestion - add other free games to script

It seems that EGS sometimes has some other free games to offer.
This week it is https://www.epicgames.com/store/en-US/product/sludge-life/home (it is shown at the https://www.epicgames.com/store/en-US/free-games )
My suggestion is to include them in script.

Same for https://www.epicgames.com/store/fr/product/a-total-war-saga-troy/home which is 24h free.

I did some digging on this a while back, and I found a GraphQL query that can list all games from the backend with their promotional offers. The issue is that there's 2000 games, which is about 1MB of data. I have very little experience with GraphQL, but I'd like to find a way to filter by discount amount so I don't have a huge request that we have to filter through.
If anyone wants to mess around with it, here's the query:
curl --location --request POST 'https://www.epicgames.com/store/backend/graphql-proxy' \
--header 'Content-Type: application/json' \
--data-raw '{"query":"query searchStoreQuery($allowCountries: String, $category: String, $count: Int, $country: String!, $keywords: String, $locale: String, $namespace: String, $sortBy: String, $sortDir: String, $start: Int, $tag: String) {\r\n  Catalog {\r\n    searchStore(allowCountries: $allowCountries, category: $category, count: $count, country: $country, keywords: $keywords, locale: $locale, namespace: $namespace, sortBy: $sortBy, sortDir: $sortDir, start: $start, tag: $tag\r\n    ) {\r\n      elements {\r\n        title\r\n        id\r\n        namespace\r\n        description\r\n        productSlug\r\n        items {\r\n          id\r\n          namespace\r\n        }\r\n        promotions(category: $category) {\r\n          promotionalOffers {\r\n            promotionalOffers {\r\n              startDate\r\n              endDate\r\n              discountSetting {\r\n                discountType\r\n                discountPercentage\r\n              }\r\n            }\r\n          }\r\n        }\r\n      }\r\n      paging {\r\n        count\r\n        total\r\n      }\r\n    }\r\n  }\r\n}","variables":{"category":"games","sortBy":"effectiveDate","sortDir":"asc","count":1000,"country":"US","allowCountries":"US","locale":"en-US","start":0}}'

It's seems script doesn't see 2 out of 5 currently available free games:

https://www.epicgames.com/store/en-US/product/3-out-of-10-ep-3/home
https://www.epicgames.com/store/en-US/product/thimbleweed-park/delores

@claabs This game is not being purchased. It doesn't appear to always be free so I'm not sure what the deal is. I'd be happy to try to help figure it out if you want.

@claabs This game is not being purchased. It doesn't appear to always be free so I'm not sure what the deal is. I'd be happy to try to help figure it out if you want.
https://www.epicgames.com/store/en-US/p/godfall--challenger-edition

This was due to captchas being added recently. It was already fixed in #192. Pull the latest image for the fix.

I'll give that a shot thank you.

It did end up purchasing Prison Architect properly by sending me the captcha, but this game isn't showing up at all.
[2021-12-15 12:47:40.126 -0700] INFO (43 on epicgames-freegames): Available free games
user<EMAIL_ADDRESS>availableGames: [
"Prison Architect"
]
[2021-12-15 12:47:40.574 -0700] INFO (43 on epicgames-freegames): Unpurchased free games
user<EMAIL_ADDRESS>purchasableGames: [
"Prison Architect"
]
[2021-12-15 12:47:40.574 -0700] INFO (43 on epicgames-freegames): Purchasing Prison Architect
[2021-12-15 12:47:42.913 -0700] WARN (HTTPError/43 on epicgames-freegames): Response code 400 (Bad Request)
HTTPError: Response code 400 (Bad Request)
at Request.<anonymous> (/usr/app/node_modules/got/dist/source/as-promise/index.js:117:42)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
[2021-12-15 12:47:42.913 -0700] WARN (43 on epicgames-freegames): API purchase experienced an error, trying puppeteer purchase

[2021-12-15 12:47:42.914 -0700] WARN (43 on epicgames-freegames): hcaptchaAccessibilityUrl not configured, captchas are less likely to be bypassed. Follow this guide to set it up: https://github.com/claabs/epicgames-freegames-node#hcaptcha-accessibility-cookies
[2021-12-15 12:47:52.229 -0700] INFO (43 on epicgames-freegames): Go to this URL and do something
user<EMAIL_ADDRESS>url: "http://epicgames-freegames.myinternalnetwork.internal:3000/?targetId=16CC67453F21673C1893209AE86BE403"
[2021-12-15 12:48:21.484 -0700] INFO (43 on epicgames-freegames): Done purchasing Prison Architect

I restarted it to force it to run
[2021-12-15 13:02:19.760 -0700] INFO (43 on epicgames-freegames): Checking free games for<EMAIL_ADDRESS>[2021-12-15 13:02:27.507 -0700] INFO (43 on epicgames-freegames): Successfully refreshed login
user<EMAIL_ADDRESS>[2021-12-15 13:02:28.154 -0700] INFO (43 on epicgames-freegames): Available free games
user<EMAIL_ADDRESS>availableGames: [
"Prison Architect"
]
[2021-12-15 13:02:28.626 -0700] INFO (43 on epicgames-freegames): Unpurchased free games
user<EMAIL_ADDRESS>purchasableGames: []

This was implemented a while back. Closing now.


Factor out custom build step definitions

This is a first step towards better arranging the code in the master config.  Better ideas for this organization are welcome :)

Ok, I took your suggestion.


New pull request for testing

for testing

Hi @bbcomplex!
Thanks for wanting to contribute to Bootstrap by sending this pull request!
Unfortunately, your pull request seems to have some problems:

The CNAME file should never be modified.
Changes must be made to the original Sass or Less source code file(s), not just the compiled CSS file(s).
Changes must be made to the original JS source code file(s), not just the generated concatenated JS file(s).

You'll need to fix these mistakes and revise your pull request before we can proceed further.
Once you've fixed these problems, you can either ask the maintainers to re-open this pull request, or you can create a new pull request.
Thanks!
(Please note that this is a fully automated comment.)

@bbcomplex If you want to test out Git or GitHub, create your own personal repository and conduct your experiments there instead, where they won't bother anyone. Using the repositories of public projects (such as Bootstrap) for such experiments wastes the time of those projects' maintainers and is thus considered rude & annoying.
To learn more about using Git or GitHub, check out the links on the following GitHub Help page: https://help.github.com/categories/bootcamp/


slint-lsp: 1.5.1 -> 1.8.0

Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Tested the build and briefly the LSP

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4746

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351029

x86_64-linux

:white_check_mark: 1 package built:

slint-lsp

@NixOS/nixpkgs-merge-bot merge

Ahh it's only for pacakge edit, which makes total sense. Fair enough, that will still allow for future PR's

Thanks!


Update readmes

Bulldog is being mavenized, refactored so the usage of this library will change

How to build (compilers), how to use distro jar, ...


Implemented tab switching

Is there a way to make it so tabs are highlighted based on the page you are on? Right now the teams tab is highlighted as selected for every tab


Track total time spent in the GC waits

I added a typo fix (max_time_to_safepointp). Then I assembled these two commits into a patch for RAICode with git diff  HEAD~2 > ../total-ttsp.patch and opened a PR to add the patch to RAICode. Finally, I applied the patch here instead of merging this PR, in order to remain consistent with previous patches.
Thanks!


Vercel environment variable naming inconsistency with Vercel KV documentation

Issue Description
When setting up a Vercel KV database and trying to use the environment variables in our Next.js application, I encountered an inconsistency between the variable names mentioned in the Vercel KV documentation and the actual variable names provided by Vercel.
Expected Behavior
According to the Vercel KV documentation, the environment variables for accessing the Vercel KV database should be named KV_REST_API_URL and KV_REST_API_TOKEN.
Actual Behavior
When pulling the environment variables from Vercel using the vercel env pull .env.development.local command, the variables are named REDIS_REST_API_URL, REDIS_REST_API_TOKEN, REDIS_URL and REDIS_REST_API_READ_ONLY_TOKEN.
Steps to Reproduce
Create a new Vercel project and set up a Vercel KV database (with Primary Region Frankfurt, Germany fra1.)
Run vercel env pull .env.development.local to pull the environment variables.
Observe that the environment variables are named with the REDIS_ prefix instead of KV_.
Workaround
To work around this issue, I had to manually change the 4 environment variable names in our application code from REDIS_REST_API_URL, REDIS_REST_API_TOKEN, REDIS_URL and REDIS_REST_API_READ_ONLY_TOKEN to KV_REST_API_URL, KV_REST_API_TOKEN, KV_URL and KV_REST_API_READ_ONLY_TOKEN respectively.
Additional Context
It's worth noting that even in the Vercel project dashboard, the environment variables are displayed with the REDIS_ prefix, which further adds to the confusion and inconsistency with the documentation.
Suggested Solution
We kindly request that the Vercel team address this inconsistency by either:
Updating the documentation to reflect the actual environment variable names (REDIS_REST_API_URL and REDIS_REST_API_TOKEN) for Vercel KV, or
Changing the environment variable names provided by Vercel to match the documentation (KV_REST_API_URL and KV_REST_API_TOKEN).

Hey @nathanblon, thanks for reporting this. There was indeed a regression in our system that lead to the wrong prefix being set.
The bug has been resolved so connecting a KV store to a project should use the KV_ prefix like our documentation says. If you already connected the store to a project you can delete the connection and re-connect the store to get the new env var names.


dotnet pack doesn't generate pdb

As soon as there is no pdb genereated, I can't upload .snupkg file on nuget, it errors with  "The package does not contain any symbol (.pdb) files.". Is it an expected behaviour?

I used
<FablePackageType>binding</FablePackageType>
<PackageTags>fable-javascript</PackageTags>
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>

I am not sure, I never saw complains coming from NuGet CLI when generating packages.
I think you need to remove:
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>

This MSBuild project set <DebugType>embedded</DebugType>, which if I understand correctly means that the symbol file is included in the package directly.

@MangelMaxime you are right, <DebugType>embedded</DebugType> is the reason .pdb file is not generated. But this makes package heavier, that's why I moved to .snupkg model for my packages where .pdb is not included in the package itself and only used by IDE. I guess that for Fable it doesn't matter since those dlls are only used for devlopment and are not included into the published artifacts, so I'm ok to close the ticket. Thanks for finding time to respond!

Perhaps, it possible to set the DebugType in your project to disable that. Depending on which order MSBuild load the information.
Or if having package a bit heavier is too much of a problem, it is also possible to add a flag to tell Fable.Package.SDK to not include the DebugType rule.

I don't see this as a big issue, so we can keep it as is for now


native/python debugger cannot find python source code

This issue has been moved from a ticket on Developer Community.

I´m trying to debug python code being called from native code. At first the native/python debugger was not in the list of available debuggers of the native project, description of the (old) issue and workaround can be found here:
https://github.com/Microsoft/PTVS/issues/6712?ref=pythonrepo.com
With the workaround applied I can now start the native/python debugger and debug the native code. I cannot debug the python code though, instead the "source not found" window is being displayed. When I click on "Browse and find *.py..." it displays "Source search information" saying the source HAS been found and the debugger will use it - but it doesn´t switch to the code:

Visual Studio Version: 17.4.1 (up to date)

Original Comments
Feedback Bot on 11/21/2022, 05:26 PM:
(private comment, text removed)

Original Solutions
(no solutions)

What happens if you just open the file directly via File -> Open?

The file opens as it should. No debugging possible though.
Some more details: The call path is native code -> python -> native code. The "Source not found" window appears when I place a breakpoint in the native code called from python, then in the call stack window click on the python file.
I have now tried to debug step into (F11) the python code from native. Instead of stepping into the python code though it steps over. After the first time I have placed a breakpoint in the native code being called from python the behaviour is slightly different: When I try to step into the python code the next time I get a message "Unable to step. An operation is not legal in the current state." The only way to continue debugging then is debug continue (F5), while both step into and step over (F10/F11) lead to this error message.

Potentially related to https://github.com/microsoft/PTVS/issues/6900


Changes to support arm64 (and Apple M1)

Building off of great work by @faberchri, I modified the caddy and gotty installs to work for both arm64 and amd64.
The end of the README.md includes instructions on how to build the image using docker buildx.  Not sure where this should actually go, but happy to move it elsewhere.
I also published the image to https://hub.docker.com/r/dougdonohoe/fast-data-dev.
docker pull dougdonohoe/fast-data-dev

Amazing, can't wait for this to land in mainline!

I've successfully tested it and working well on M1 Pro 16" 👍

Would love to see this merged asap!

I switched to using Confluent Platform with Docker Compose and it works great with Apple Silicon.  Also, they have a build that doesn't require ZooKeeper which can be found here.

Merged finally after quite some time!
I am sorry for the huge delay; it was due to both capacity and blockers from our product.
The lenses/box image is essentially the lensesio/fast-data-dev  with Lenses on top, a great way to explore Kafka. :)
There was a huge workstream behind the scenes to prepare the product and CICD for arm64 support, and the developer-focused images (fast-data-dev and box) were the last on the long chain of required adjustments. Actually Box is the last and I hope it will come out in the next few days.
Anyhow, thank you for your work; it was great! :100:


Build fails on Ubuntu 14.04

I get this error if I just run make:
[MAKE]    Building protobuf
checking whether to enable maintainer-specific portions of Makefiles... yes
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
make: *** [/home/gulfstream/git/grpc/libs/opt/protobuf/libprotobuf.a] Error 1

This seemed to fix it:
pushd third_party/protobuf
./autogen.sh
popd
make

Assuming fixed.


Fix: Create flags for running the script #7

fix tab > spaces
flag for device -d <device>
dev: multiple account with flag -a <account>  (multiple .afkscript.tmp files)

Oops, my bad. fixed

The only thing I did not quite understand was what value -a can be? What do you mean by "account"? I imagine the value can be anything, as it seems you only use it to make different .tmp files by naming them.
Also, by giving it a name before the ., you're making the files visible, which is not desired. It should be possible to change tempFile="$OPTARG.afkscript.tmp" to tempFile=".afkscript_$OPTARG.tmp" to fix this, right? Line 337.

Yes -a is for account, well, to name the .tmp file so i can move it anywhere in the name

Looks good to me, will test it out later.

./deploy.sh -a manny created .mannyafkscript.tmp 👍
./deploy.sh -a manny again but changed .mannyafkscript.tmp value so it's been over 3 days and did not beat campaign 👎
I think the while getopts ":a:d:h" option ; stuff should be before checkDate gets called.

./deploy.sh -h does print out the help information but it also runs the script.


Passing annotation to scheduled task in spring cloud dataflow

I am running SCDF v1.7.2.RELEASE on Kubernetes.
I have to pass annotations to my tasks. I have given the following annotations in env:
    - name: SPRING_CLOUD_DEPLOYER_KUBERNETES_POD_ANNOTATIONS
      value:
    - name: SPRING_CLOUD_DEPLOYER_KUBERNETES_JOB_ANNOTATIONS
      value:

I also have to pass these annotations to my scheduled tasks/jobs. But the pods created by jobs don't have this annotation.
I tried the following annotations:
    - name: SPRING_CLOUD_SCHEDULER_KUBERNETES_POD_ANNOTATIONS
      value:
    - name: SPRING_CLOUD_SCHEDULER_KUBERNETES_JOB_ANNOTATIONS
      value:

But it did not work. Do these exist in scdf?

HI, @siddhantsorann. The podAnnotations and jobAnnotations support is not available in spring-cloud/spring-cloud-scheduler-kubernetes yet. We would have to port and implement a similar functionality from K8s-deployer to the K8s-scheduler.
I will move this issue to spring-cloud/spring-cloud-scheduler-kubernetes. Feel free to take a stab at it on a PR - we can coordinate a release when it is merged.

See: https://github.com/spring-cloud/spring-cloud-scheduler-kubernetes/issues/23


Configurable factory to query the list of devices.

Can now query serialports by-id or by-name addressing the issue #437

Looks like this failure is related to the revert #476 we're working on. Lets put it on top of #490 and try again


ZING-24536 Bump node-fetch 2.6.1 to 2.6.7

You may have to tag this release as well, once you merge it.


Fix a with-related precise-capture bug

Fix a precise-capture bug exposed in the unreleased branch. Also make our conservative with-statement closure-capture code immune to deferred nested functions.

@aneeshdk This is the issue we were looking at yesterday evening.

What was the bug?

@ianwjhalliday We missed marking a func decl parse node as containing a with statement, so we missed marking the function as needing a scope object. But a nested function reference was generated expecting a scope object.

Gotcha.  Worth adding a regression test?

A UT will come over from unreleased/rs2.


kcov is covering only one test case?

Hello,
I am trying to run code coverage for bats script.
hello.bats:
#!/usr/bin/env bats
@test "hello without arguments" {
result=$(bash $BATS_TEST_DIRNAME/../hello.sh)
[[ "$result" == "Hello unknown" ]]
}
@test "hello with world argument" {
result=$(bash $BATS_TEST_DIRNAME/../hello.sh world)
[[ "$result" == "Hello World" ]]
}
hello.sh
#!/usr/bin/env bash
if [[ "$1" == "world" ]]; then
echo "Hello World"
else
echo "Hello unknown"
fi
Command I am executing:
kcov coverage/ tests/hello.bats
It is generating the coverage report but for only first test case which is "hello without arguments"
Can you help me?

That's coverage of the tests, not of the actual code under test.
Try kcov --include-path=. coverage/ bats tests/
Note that it actually executes bats, and not the test file directly - the test directory/file is an argument to bats, not kcov.
Note also that the coverage reports includes a lot of non-related binaries, that's why the --include-path=. parameter filters it down to the current directory, where the script under test (hello.sh) resides.

Then I get an empty report?
This time I executed below commad:
kcov --include-path=. coverage/ /usr/local/bin/bats tests/
<img width="178

5" alt="Screenshot 2021-12-08 at 10 34 43 AM" src="https://user-images.githubusercontent.com/89068241/145151342-0125e990-ee2b-46e4-8c68-c5713c3a8321.png">

Interesting. For me, it reports 100% on "bats", though if clicked it shows the actual script under test.
I know there are issues with running kcov in docker, maybe there are some incompatibilities with mac too?
(Linux here)

If possible can you please provide me the screenshots.

I launched and ec2 ubuntu machine install kcov and ran below command:
kcov coverage/ /usr/bin/bats tests/
and
kcov --include-path=. coverage/ /usr/bin/bats tests/
after executing the command below is the output and in the report I can see any hello.sh file or hello.bats file.

Interesting. For me, it reports 100% on "bats", though if clicked it shows the actual script under test.
I know there are issues with running kcov in docker, maybe there are some incompatibilities with mac too? (Linux here)
Interestingly enough, that output which you get, is the same as the failing one in docker, if I remember correctly. Here, the command returns no output at all.

You mentioned that actual script is visible in code coverage did you mean hello.bats or hello.sh?


opscode-omnibus: Write Logs in Alternative Locations

Zendesk 3571
As a customer running a Chef Server, I would like to be able to write logs to a directory other than /var/log/opscode. The world permissions on my /var/log directory are blank and it is owned by root:root. Because of this, the runit svlogd processes running as the opscode user are unable to traverse down into /var/log/opscode to write and read.
Currently, the opscode-omnibus, chef-manage, and several other repos have hardcoding of /var/log/opscode . Tools like gather-logs depend on this location as well.

Closing for now. Please feel free to reopen is the issue is still relevant.


dbeaver/dbeaver-ee#1877 Nested attributes view and edit fix

Please make sure that cell editing works both in normal and record modes.

Something going wrong during array editing in Record Mode in case Show complex column structure is disabled

Editing of nested elements is disabled for now.

verified


⚠ Bofrost.es has degraded performance

In 722beb6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1460 ms

Resolved: Bofrost.es performance has improved in a55bffa after 6 minutes.


Unable to sync clippings with many highlights

I've tried to sync my kindle clipping recently and one of the books contains 694 highlights and failed with 413 Payload Too large error.

It has to do with the current character limit imposed on a single block in Notion. To speed up the book uploads, what we do is currently upload all clippings onto a single text block in Notion. Here, we'd need to write a use case to address this error.

How about uploading clippings in separate text block in the Notion? Do you think it's having any impact if we upload to separate block instead?


Port inline completion to cohosting

Fixes https://github.com/dotnet/razor/issues/10744
Needs https://github.com/dotnet/roslyn/pull/76293 to merge and a version bump, but you know the idea by now I'm sure.
Pretty straight forward. The test snippet file was copied directly from Roslyns own inline completion tests. Turns out our existing inline completion has zero tests, and was inadvertently turned off in the first cohosting completion PR 🤦♂

/azp run

Tests are failing because logging is happening after a test has finished, which usually means something isn't being disposed properly, but none of the test changes in this PR could cause it, because its happening on macOS and linux, and the test changes here are Windows only. Must be a change in Roslyn :(


Active link issues

The issues following  #267 and #193 I am not sure I understand if this have been resolved?  No indication as bug?

It should be fixed, otherwise provide me with a plunker and how I can reproduce it. @aprather51

I doubt anything need to be reproduced.  Everything seem to work fine except for a little glitch with incorrect active on menu bar as mentioned in #193 .
e.g. Following from this live demo
(Note: It does not work with Firefox 57.0 and Firefox Web Developer Edition 58.0b10)
Clicking on "Test 2", You will notice active menu will stuck on "Test 1".  Even though, it did scroll correctly into "Test 2" section/element.  When clicking on "Test 3" menu, will again scroll correctly into "Test 3" section/element. The active menu that stuck on "Test 1" will  skip over "Test 2" and then into "Test 3" -- On the correct active menu. Other thing,  you will have to Double Click on menu for active menu to match with section. That some glitch that need to be fixed rather than reproduce it.
With my time limit, I doubt I could find time to solve this issue. Hopefully, my feedback can help one to fix the issues.


handle the path for different write backend

https://github.com/open-cluster-management/backlog/issues/18022
Signed-off-by: Marco<EMAIL_ADDRESS>

/lgtm


Error evaluating a chrome example e1e75309-3ddb-4d09-92ec-de869c928143

I modified the quick start code in the README by replacing the example dictionary with the Chrome example e1e75309-3ddb-4d09-92ec-de869c928143. Additionally, I added result = env.evaluate() for evaluation. However, during evaluation, I see the following error printed to the console:
Failed to get file. Status code: 404
Failed to get file. Status code: 404
Failed to get file. Status code: 404
Failed to get file.

During each failure, in the test environment, an incognito window briefly pops up and closes automatically. Could you help me understand why this happens and how to resolve it?

Note that for many other test examples, everything's okay.
Thanks.

Hi, fail to get file is correct, which means your agent didn't get the pdf file since it failed.

That explains. Thanks for the explanation!


Create QuickSort_C++

What the program do ?
The program sort a given array using quick sort with the Hoare's particion
In what programming language it is written?
C++

This pull request do not contains files in specific folders. Please fix it and reopen


add AUR/kicad-kibuzzard-git

I packaged the plugin for Arch users.
If you would like to add a hint, here is my PR for this.

Thanks!


Fixes to the DDS loader

Added missing format info entries for ATI1 and ATI2 formats
Added missing A2XY format

I accidentally also came across that this originally wasn't broken, but got broken about 2 years ago due to the commit that introduced clang-format: 5dbf1809c6e3e905b94b8764e99491e608122261 :confused:

I accidentally also came across that this originally wasn't broken, but got broken about 2 years ago due to the commit that introduced clang-format: 5dbf180

How exactly? I don't think any other change than formatting changes in this commit for this file. As far as I can tell the values before and after in ResourceFormatDDS::load are the same.

I used TortoiseGit's blame tool, maybe it showed the changes incorrectly.

Just verified, indeed something must be wrong with the way the blame tool works here. Maybe it just doesn't show changes that only removed lines.
Anyway, what's for sure is that two years ago the 2 entries for ATI1 and ATI2 were there, but somehow got deleted.

This commit modified them:
https://github.com/godotengine/godot/commit/f89641907f8b45941f5e67891936ee8050a3ef92
And it seems like this commit removed them:
https://github.com/godotengine/godot/commit/a134f58fb3e072a3453bd5e9286f90b4694c9766

Thanks!


npx command in front of projen is missing in readme

When trying to follow the getting started steps, the projen command fails to work due to it needing to be called via npx instead of directly as a cli command.
Fixed in #42

thanks for contribution, change merged


Error when building non-cuda variant

When running
spack install q-e-sirius@develop-ristretto%gcc ^sirius~cuda+openmp+nlcglib

I got
==> Error: ProcessError: Command exited with status 1:
    'cmake' '-G' 'Unix Makefiles' '-DCMAKE_INSTALL_PREFIX:STRING=/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/nlcglib-develop-4duf65rmg437kyncarv53iomtlkzoukc' '-DCMAKE_BUILD_TYPE:STRING=Release' '-DCMAKE_INTERPROCEDURAL_OPTIMIZATION:BOOL=OFF' '-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON' '-DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF' '-DCMAKE_INSTALL_RPATH:STRING=/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/nlcglib-develop-4duf65rmg437kyncarv53iomtlkzoukc/lib;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/nlcglib-develop-4duf65rmg437kyncarv53iomtlkzoukc/lib64;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/openblas-0.3.19-yjaj54bn4ecjie6xqxrunapojqdr2u7w/lib;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/kokkos-3.5.00-fomjb4ztlgqnr2s2p6ub2hoszsdxlqyf/lib64;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/nlohmann-json-3.10.5-umiu4cee3efh5gqvy6yicg4qfkf7mrs2/lib64' '-DCMAKE_PREFIX_PATH:STRING=/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/openblas-0.3.19-yjaj54bn4ecjie6xqxrunapojqdr2u7w;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/nlohmann-json-3.10.5-umiu4cee3efh5gqvy6yicg4qfkf7mrs2;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/kokkos-3.5.00-fomjb4ztlgqnr2s2p6ub2hoszsdxlqyf;/ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/cmake-3.22.2-tfcl2jtctliszlnovgjfdcldsvgsvb7i' '-DUSE_OPENMP=On' '-DLAPACK_VENDOR=OpenBLAS' '-DBUILD_TESTS=Off' '-DUSE_CUDA=Off' '/tmp/a-ctalirz/spack-stage/spack-stage-nlcglib-develop-4duf65rmg437kyncarv53iomtlkzoukc/spack-src'

1 error found in build log:
     6     -- Check for working CXX compiler: /ohome/shared/spack/lib/spack/env/gcc/g++ - skipped
     7     -- Detecting CXX compile features
     8     -- Detecting CXX compile features - done
     9     -- Checking for module 'mpi-cxx'
     10    --   No package 'mpi-cxx' found
     11    -- Could NOT find MPI_CXX (missing: MPI_CXX_LIB_NAMES MPI_CXX_HEADER_DIR MPI_CXX_WORKS)
  >> 12    CMake Error at /ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/cmake-3.22.2-tfcl2jtctliszlnovgjfdcldsvgsvb7i/share/cmake-3.
           22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
     13      Could NOT find MPI (missing: MPI_CXX_FOUND CXX)
     14    Call Stack (most recent call first):
     15      /ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/cmake-3.22.2-tfcl2jtctliszlnovgjfdcldsvgsvb7i/share/cmake-3.22/Modules/Fi
           ndPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
     16      /ohome/shared/spack/opt/spack/linux-centos7-haswell/gcc-11.2.0/cmake-3.22.2-tfcl2jtctliszlnovgjfdcldsvgsvb7i/share/cmake-3.22/Modules/Fi
           ndMPI.cmake:1830 (find_package_handle_standard_args)
     17      CMakeLists.txt:14 (find_package)
     18

I believe that's because the nlcglib spack recipe does not explicitly depend on MPI.

Thanks, indeed mpi is of course an explicit dependency.


Thu/email ellipsis

Ellipsis for Long Email Addresses in UserSnapshot
Truncated longer email addresses using Tachyons. Ellipsis appear when the text is longer than Tachyon w4.
Related PRs
None.
Migrations
None.
Tests Performed, Edge Cases
None.
 I'll teach you how to rebase this back onto master :)

Hello! Just removed it from package.json and checked that it was removed from yarn.lock, too. :- D


Suggestion: a Type Assertion that asserts at run time

Type Assertions are compile time only.
It would be helpful to have a concise way to have a compile time type assertion be checked at run time.
The language spec gives the example:
var shape = createShape(shapeKind);
if (shape instanceof Circle) {
  var circle = <Circle> shape;
  ...
} else {
  throw new WrongTypeAssertionException("Wanted type Circle, but was actually " + (typeof shape));
}

which is very repetitive (and fragile). Instead it would be great to have something much more concise like:
var circle = <Circle!> createShape(shapeKind);

that threw an exception at run time if an instanceof check failed.
I would rather give up some run time performance for a concise way to get a clear run time failure message if my assertion is false.

You didn't read about type guards and union types, did you?
The following code is perfectly valid.  shape.radius inside the if statement doesn't lead to a compilation error because the shape variable is of the type Circle there.
class Shape { }
class Circle extends Shape {
	constructor(public radius: number) {
		super();
	}
}

function createShape(kind) {
	if (kind === "circle") {
		return new Circle(200);
	}
	return new Shape();
}

var shape = createShape("circle");
if (shape instanceof Circle) {
  console.log(shape.radius);
} else {
  throw Error("Wanted type Circle");
}

Yes, I have read about type guards and union types.
I understand that your example is valid code.
As I said above, implementing the type check by hand using instanceof is repetitive and fragile.
Instead of writing the type assertion manually like (A):
var shape = createShape("circle");
if (shape instanceof Circle) {
  console.log(shape.radius);
} else {
  throw Error("Wanted type Circle but got " + (typeof shape));
}

I want to write something like (B):
var circle = <Circle!> createShape("circle");
console.log(circle.radius);

(note the '!' in the Type Assertion) and have it be equivalent to the manual type assertion in (A) above.

Here is how I implemented this behavior, if it can help.
interface Type<T> {
    new (...args: any[]): T;
}

function cast<T>(type: Type<T>, object: Object): T {
    if (!(object instanceof type)) {
        var matches = /^[^ ]+ (\w+)/.exec(type.toString());
        var expected = matches ? matches[1] : "?";
        matches = /^[^ ]+ (\w+)/.exec(object.constructor.toString());
        var got = matches ? matches[1] : "?";
        throw new TypeError(`expected type ${expected}, got ${got}`);
    }
    return <T>object;
}

So can write:
var circle = cast(Circle, createShape("circle"));
console.log(circle.radius);

Concerning your request, I would prefer a compilation option that adds code to validate all the casts that the compiler cannot statically confirm.
I would enable this option in debug mode and remove it in release mode.

@stephanedr Thank you for your example implementation.
I agree that it would be ideal if TypeScript could generate code for this feature only if it can statically prove the run time check is necessary.
This is not something we can do in a library function!
If the performance is good enough (< 20% slower?) I would leave these checks on even in release mode.

It might be safer if the compiler warn on unnecessary casts and always synthesize a check otherwise.

This has been suggested and discussed many times. We're always trying to avoid pushing the type system into the runtime and the number of types this actually works for (pretty much just classes and primitives) isn't large enough to justify the complexity versus the use cases it enables.

Just in case anyone is interested in the future, here’s the runtime type assertion that also accepts abstract class types (based on the constructor type definition proposed in this Stack Overflow post):
type Constructor<T> = Function & { prototype: T }

function cast<T>(type: Constructor<T>, object: Object): T {
    if (!(object instanceof type)) {
        throw new TypeError();
    }
    return <T>object;
}


feat: add support for exception mechanism metadata

This adds support for the exception mechanism field, based on the relay schema of the field.
Primarily, I'd like to be able to annotate exceptions with this data to make the UI more useful. For instance, we have a gRPC interceptor that recovers from panic, and I think it would be useful to set the handled bit to false so that we get the additional UI embellishment (the red skull and "Unhandled" flag) when endpoints panic (versus returning an explicit status or error). This would likely be useful to other HTTP integrations as well.

meta is missing https://github.com/getsentry/relay/blob/e785f9a22adef018cec8785a7dec289a6ae74165/relay-general/src/protocol/mechanism.rs#L154
There are also some docs that might explain all of this in more detail https://develop.sentry.dev/sdk/event-payloads/exception/

Ah, yeah. That was an intentional omission because it didn't look like any of the meta fields would be relevant in a Go runtime, since it seems like most of the meta fields are specific to Apple, POSIX, or C syscalls. I'm not opposed to adding the relevant structs if you think they're worth adding, or I could leave a comment explaining the omission.

Ok, we can also start with type, handled, and data for now. Not sure if the others will add much value.
Some tests would be great as well 🙂

Ok, we can also start with type, handled, and data for now. Not sure if the others will add much value. Some tests would be great as well 🙂

I'll add some tests.
 At least for my own use cases, I could see some value in being able to populate those (since they're rendered in the UI) for common internal errors so that we could point to internal documentation, etc.

@cleptric updated with tests and a comment.

Could you add a small snippet of how someone can use this feature to set an error as unhandled as well?

Something beyond the tests? I can add it if you can point me to where you'd like me to add it. Documentation? Nothing else in interfaces.go has anything like this, so I'm not quite sure what you're asking for. If you could be specific, that would be very helpful. I'd like to get this merged so we can avoid the need to maintain an internal fork of this package to take full advantage of Sentry's data model.


Use COPY and change spec name

@mhmxs changing to storageos-operator.yaml make it life easier on the plugin side. I don't know if this name change impacts anywhere else? 🤔

@nolancon I don't think so, it is just used for cat


Fix omitempty struct

What type of PR is this?

/kind bug
What this PR does / why we need it:
it will panic when HostsMap len equal zero and k8s version less than 1.20.11, because the HostsMap's type is struct.
if type is struct but not Pointer, omitempty invalidate
Which issue(s) this PR fixes:

Fixes #
change HostsMap's type to omitempty
Special notes for your reviewer:

Thanks for your pr.
Please make update make vendor and then make staticcheck make test

/lgtm

git commit --amend  can avoid multi commit in the one pr.


Webpack HMR does not work if navigated to nested path

Version
4.1.2
Steps to reproduce
<Switch>
<Router exact path="/one" component={One} />
<Router path="/one/two" component={OneTwo} />
<Router path="/or/whatever" component={WhatEver} />
</Switch>

Expected Behavior
Should Hot Reload also in nested path like /one/two , /or/whatever not only in /one
Actual Behavior
When I am navigated to path /one in browser and edit some component hot reloading just works fine.
BUT
When I an navigated to path /one/two HMR does not work, entire browser reloads
In above Steps to reproduce example if i change /one/two to be only one level depth say /blah then it works.
Other Info

Webpack 2
React hot reload

Unfortunately, this doesn't sound like a bug with how React Router does things. It's just plain React code. It is likely something in react-hot-loader, or just a limitation in how it works. I would seek support through whatever their appropriate channels are.


Update font-lohit-tamil-classical to 2.5.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Merged as a666364c8eb43e0b04245e16de710340607ad611.


[scan] number_of_retries on 2.201.1 + Xcode 13 behaves differently from documentation

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Per docs number_of_retries is

The number of times a test can fail before scan should stop retrying

i.e. 0 (the default value) means no retries, only 1 iteration is allowed.
With Xcode 13, number_of_retries is being input to the new -test-iterations setting in xcodebuild so it's retrying 1 time less than before.
Another example: now number_of_retries: 1 actually means "don't retry".
Example
This should be reproducible using the number-of-iterations-equals-retries branch from https://github.com/gobetti/fastlane-201-issues , or this commit https://github.com/gobetti/fastlane-201-issues/commit/14b4c6ff2515769975edbf11a2c988ad74b1a01f

Ah! Can't believe I forgot to change this. I'll get this fixed!

@gobetti This should be fixed with #19844 💪


[jax2tf] Refactor tests to increase coverage

This change has several goals: (a) increase the test coverage
for the elementwise primitives, (b) expose explicitly
the situations where JAX and TF produce different results,
e.g., inf vs Nan, and (c) run all comparisons with and
without tf.function, with and without experimental_compile=True.
Previously the test code was just masking off non-finite values.
This change uncovered quite a few unimplemented cases, e.g., with
float16, bfloat16, conversions that cannot be compiled.
This are left as TODO for now.

@googlebot I consent.


ARTEMIS-4239 use StandardCharsets.UTF_8

avoid UnsupportedEncodingException handling

This needs a Jira.

The change seems to be more expansive than the short title might imply perhaps either limit the changes or provide more context into what and why this is being done

limit the changes

done


Support for Polymer Web Components

If I use the plugin in a Polymer element, the plugin doesn't work:
TypeError: Cannot read property 'range' of undefined

Hello, @abdonrd,
Firstly, I'm sorry that you are having problems with this plugin.
Unfortunately, I need more information about what is happening. For example, minimal code example.
🐼

Sure! Sorry @mrmlnc!
For example, check the ibm-toolbar.html element.

I will work on this issue tomorrow morning (Russia, GMT+3).

Thanks!

Well, I researched the errors and have a bad result:

CSSComb not supported CSS built-in into HTML. I can search style tag and if it is found, run CSSComb. But it looks like a Hack.

Thanks for the research!
You're going to add search style tags? Or we should create an issue in the CSSComb repo?

Or we should create an issue in the CSSComb repo?

Nope, CSSComb is tool only for CSS, Less, Sass (+SCSS).

You're going to add search style tags?

Yes, I wrote code, but now I have problems with identation (because we should calculate new indentation for CSS (as nested HTML style tag + CSS))
I moved this issue to monday or tuesday.

Ok, thanks! :)

See 3.1.0.

Thanks @mrmlnc!
How it should work? I use:

But I no see changes.

@abdonrd,
Just tun CSSComb: Format styles .

You have CSSComb config?

I have a .csscomb.json file at root of the project.

@abdonrd,
Please, try 3.1.1 version. And let me know if you have problems.

@mrmlnc better, but now moves the CSS to left. :/

@abdonrd,
I pushed relase with 3.1.2 version. Please, try it.
Sorry for this situation.

Yaay! It works, thanks so much @mrmlnc!

@mrmlnc In the csscomb.preset I can set up a file? Like:
"csscomb.preset": "/Users/abdonrd/Work/.csscomb.json"

@abdonrd,
Now nope, but if you create issue - yes 😅

Done! https://github.com/mrmlnc/vscode-csscomb/issues/33


Query Optimizer Fixes option is not explained in depth and the link to trace flag seems to link to outdated file

There is not enough info about Query Optimizer Fixes option. The link to trace flag discusses version 2016 as the most recent.
I'm creating a new Azure DB and want to make sure to specify correct option which is OFF by default

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

ID: 82ff5f89-39e8-2526-9f4c-fd03c8674fdc
Version Independent ID: d27b5731-f02e-c33c-5a6e-86a0a7ea0522
Content: Database Properties (Options Page) - SQL Server
Content Source: docs/relational-databases/databases/database-properties-options-page.md
Product: sql
Technology: configuration
GitHub Login: @stevestein
Microsoft Alias: sstein

@NaomiN - thanks for raising this issue.  Doc update should go live today. I updated the description/link:
Enables or disables query optimization hotfixes on the primary regardless of the compatibility level of the database. This is equivalent to Trace Flag 4199. For details, see QUERY_OPTIMIZER_HOTFIXES.
Thanks!

#please-close


Update concepts-quotas-limits.md

I made changes to the number of days for Storage retention per thread on Ava channel

#sign-off


S-Group: incorrect rendering when using structures from Template pallete and different options from S-Group Properties window

Steps to Reproduce

Launch Ketcher.
Chose 'Cyclooactane' (or another structure from Template pallete) and click on canvas.
Click the 'Data S-Group' button and select Cyclooactane on canvas.
Choose 'Fragment' option from 'Context' drop-down list and click the 'OK' button.
Select Cyclooactane on canvas, Choose 'Bond' option from 'Context' drop-down list and click the 'OK' button.
Select Cyclooactane on canvas, Choose other options from 'Context' drop-down list and click the 'OK' button.

Expected behavior
Correct rendering (like in case when using Chain structure and different options from S-Group Properties window).
Actual behavior
Incorrect rendering.
https://user-images.githubusercontent.com/90637536/134645600-f0febf0b-6950-46a3-896e-6986901ce98b.mp4
Desktop:
OS: Windows
Browser: Chrome Version 93.0.4577.63, Firefox Version 92.0, Microsoft Edge Version 93.0.961.47
Additional context
Reproduce in version 2.3
https://lifescience.opensource.epam.com/ketcher/demo/ketcher_2_3_remote.html
https://lifescience.opensource.epam.com/ketcher/demo/ketcher_2_3_standalone.html

fixed, tested v.2.4


[EOSi Frontend] #3 Add more space above and below...

Add more space above and below this section
Source url: https://eosi-frontend.netlify.app/why-eosi.html
Reported by: Chris ()
Reported at: 06 Jul at 14:07 UTC
Type: Feedback
Location: US, Massachusetts, Buzzards Bay
Browser: Firefox 102.0
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0
OS: macOS 10.15
Screen: 2560x1440
Viewport: 1369x735
Referrer: https://eosi-frontend.netlify.app/
Screenshot:

For more details please visit report page on Ybug:
https://ybug.io/dashboard/reports/detail/0zqvv36h0tnp5j69s1ds

I got this one <3


Adjust player placeholder window (before playing)

Window is resized as soon as we hit play - ensure window is the same size and after playing

This is actually a feature from asciinema-player
https://github.com/asciinema/asciinema-player#fit


Avoid lossy buffering in #[serde(flatten)]

The Deserialize implementation of a type with a field annotated #[serde(flatten)] currently buffers up all of the unknown map entries in memory, and then deserializes the flattened value from them at the end. This approach has a couple of downsides:

It causes the deserializer to allocate when that would normally not be the case.
It confuses "smart" deserializers - things like serde_ignored_value or serde_json's error position tracking don't work properly.
It can lose out on special casing in deserializers based on hinting.

Fortunately, there's alternate approach that avoids all of these issues! Instead of buffering, we can create a custom MapAccess which intercepts fields that we want to handle in the top-level type, and then returning the remainder to the nested deserialize implementation: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=96546d7ba882b70042268a0b48de6286

This is a very interesting idea.
I have a couple of remarks / incompatibility observations. Maybe some of them can be resolved.
Currently, the Foo type ultimately decides if a field name is known or unknown. This leads to an incompatibility currently, if deny_unknown_fields is added to Foo. With the normal flatten extra fields will be ignored, since ExtendedFoo allows them.
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=4e249bb1961ff44945606ed6bdcdab7d
I think that can be fixed by adding an Ignore variant to ExtendedFooFields, similar to the current derive. An unknown field error from the seed of ExtendedFooFieldsVisitor must be converted into the Ignore variant, but all other error likely should remain. Inspecting the errors might be complicated, since they are very opaque.
It is unclear to me how this could be extended to more than one flattened field.
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7451b4980894d2ddda33b7ce3fc0aa9c
An additional complication here is the fact, that the same value can be deserialized multiple times. A map visitor (i.e., Value) will not consume the fields from the internal buffer, but a struct visitor (i.e., Sub) will. This leads the second Value to share all fields with the first except those consumed by the Sub visitor.

Output
[src/main.rs:27] d = Data {
    f0: Object({
        "x": String(
			"foo",
        ),
        "y": String(
            "bar",
        ),
        "z": String(
            "baz",
        ),
    }),
    a: 123,
    f1: Sub {
        y: "bar",
    },
    b: 456,
    f2: Object({
        "x": String(
            "foo",
        ),
        "z": String(
            "baz",
        ),
    }),
}

An unknown field error from the seed of ExtendedFooFieldsVisitor must be converted into the Ignore variant, but all other error likely should remain. Inspecting the errors might be complicated, since they are very opaque.

We should be able to handle this by making a custom error type used by the MapAccess implementation that intercepts unknown field errors and delegates the rest to the inner MapAccess's error type.

It is unclear to me how this could be extended to more than one flattened field.

Wow, I was not aware that was a thing you could do! I think you are stuck buffering there to allow the key value to be deserialized multiple times unfortunately. We could continue using the old logic in that case.

Hmm - we can't actually filter the errors since the error will terminate the deserialization of the inner value entirely...

On the other hand, the docs on serde.rs do explicitly state that flatten isn't compatible with deny_unknown_fields: https://serde.rs/field-attrs.html#flatten.

Here's a working implementation of that approach: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=b9b5b874c6f4c93d6d82c1bed4e6451e. If you did want to allow unknown fields in ExtendedFoo, we'd codegen the extra Ignored variant for ExtendedFooFields and return that instead of an error in ExtendedFooFieldsSeed.

I think, that using a json is a bad example to demonstrate absence of "lossy deserialization", because JSON contains some information about value type. Try some untyped format, like XML (but there are no good XML serde adapter, so using some toy format would be better)

I coincidentally made a fully working implementation of this this evening. You don't need to depend at all on looking for particular deserialize errors / missing_field notifications, because you already know ahead of time what the names of the fields are that you're interested in. You can further minimize codegen by creating a new, private trait (I called mine KeyCapture):
pub enum KeyOutcome<T> {
    Accepted(T),
    Rejected,
}

pub trait KeyCapture<'de> {
    type Token;

    fn expecting(&self, formatter: &mut std::fmt::Formatter) -> std::fmt::Result;

    fn try_send_key<E>(&mut self, key: &[u8]) -> Result<KeyOutcome<Self::Token>, E>
    where
        E: de::Error;

    fn send_value<D>(&mut self, token: Self::Token, value: D) -> Result<(), D::Error>
    where
        D: de::Deserializer<'de>;
}

In the struct macro codegen, you implement this trait such that it "rejects" keys that are not part of the struct; these keys can then be transparently forwarded to the type being flattened. Once you have this trait, you can use a series of private adapter types to deserialize the inner flattened field while simultaneously sending data into the KeyCapture. Some snippets:
// From MapAccess:
    fn next_key_seed<K>(&mut self, mut seed: K) -> Result<Option<K::Value>, Self::Error>
    where
        K: de::DeserializeSeed<'de>,
    {
        // We're extracting a key for the type. Try to send keys to the `KeyCapture`,
        // and the first key that is rejected by the `KeyCapture` are is instead to the
        // `seed`
        loop {
            seed = match self.map.next_key_seed(ExtractKeySeed {
                seed,
                capture: &mut self.capture,
            })? {
                None => {
                    self.drained = true;
                    return Ok(None);
                }
                Some(ExtractKeySeedResult::Deserialized(value)) => return Ok(Some(value)),
                Some(ExtractKeySeedResult::Captured { seed, token }) => {
                    self.map.next_value_seed(ExtractValueSeed {
                        token,
                        capture: &mut self.capture,
                    })?;

                    seed
                }
            };
        }
    }

// From Visitor:
    fn visit_str<E>(self, v: &str) -> Result<Self::Value, E>
    where
        E: de::Error,
    {
        match self.capture.try_send_key(v.as_bytes())? {
            KeyOutcome::Accepted(token) => Ok(ExtractKeySeedResult::Captured {
                seed: self.seed,
                token,
            }),
            KeyOutcome::Rejected => self
                .seed
                .deserialize(v.into_deserializer())
                .map(ExtractKeySeedResult::Deserialized),
        }
    }

Completed implementation for consideration: https://github.com/Lucretiel/serde-bufferless

I think it is better to fix this generically, not just for the case with one flattened field, because in that case it creates a friction when users realising that small change in definitions of their types will broke deserialization.
To achieve that, changes only on deserializer side is not enough. I work on this problem, and you can see my unfinished work at https://github.com/serde-rs/serde/compare/master...Mingun:flatten. The actual changes begins from 1071b39e63077789beb9e55af7384462db72a3bd, the other is a prepare work.
The key idea in that #[derive(Deserialize)] implements additional trait DeserializeEmbed on types that could be flattened. This approach solves many problems:

you no longer can add #[serde(flatten)] on fields of non-flattanable types, such as String, because DeserializeEmbed is not implemented for strings (see eac15662a5e045918e93e64b5a7215fe12699307)
you now deserialize each field only once (not consuming flattened fields from deserializer is a mistake)
you can pass flattened field to any level (when you flatten in flatten in flatten...)
you no longer need a hack for support Option in untagged enums: https://github.com/serde-rs/serde/blob/c3ce2c934a9123b5a309256d65cca6b6d19466ec/serde/src/de/mod.rs#L1672-L1679
I expect that almost all flatten problems will be solved by this

I do not remember the exact status of readiness of this, but I remember that only one of the enum representation options remained to be implemented (seems untagged representation).
Chosen approach has downsides, but their are not so big:

the main downside is that flattenable/non-flattenable is a trait of a type, not a deserialize operation, but DeserializeEmbed derivered on operation basis. This is the fundamental restriction, because I trying to make this invasive as minimal as I possible and I almost approached that: except two scenarios, described below the end-user don't need to change in their code nothing
strictly speaking, this is a breaking changes, because your code could stop to compile after this change. But serde anyway doesn't follow semver, so the users should be prepare for that (of course, I supposed to include this only in serde 2 and start to follow semver).

The two scenarios is following:

User implement Deserialize manually and that type is flattened into another type. I think this is very rare case
User try to flatten field of type that cannot be flattened, such of String example above. This is in any case an error in the user code that anyway should be fixed, because currently such types will always deserialized with an error which, obviously, not what the user want. Unfortunately, because DeserializeEmbed implemented only in #[derive(Deserialize)], having only #[derive(Serialize)] on the type still allow you to create an erroneous type. I don't know, is it possible to automatically implement some trait twice from different derives without ambiguity, which is by good required here

Ha, reinvented the same wheel (deserializing with just one flat field without buffers) recently and only now discovered this thread. I suppose I should try to switch to serde-bufferless linked above instead.

@Lucretiel Any chance you'd want to add a proc-macro to your repo and publish it to crates.io?

I’ve taken a similar approach to @Mingun, this issue cannot really be solved without API changes. The deserializers need to expose what fields they can take, and they need to accept fields individually rather than an entire map. I’ve added a DeserializeMap trait extending Deserialize for map-based types as well as the corresponding MapVisitor trait which actually collects the values:
pub trait DeserializeMap<'de>: Deserialize<'de> {
    type Visitor: MapVisitor<'de, Value = Self> + Sized;
    fn visitor() -> Self::Visitor;
}

pub trait MapVisitor<'de> {
    type Value;
    fn accepts_field(field: &str) -> bool;
    fn list_fields(list: &mut Vec<&'static str>);
    fn visit_field<D>(&mut self, field: &str, deserializer: D) -> Result<(), D::Error>
    where
        D: serde::de::Deserializer<'de>;
    fn finalize<E>(self) -> Result<Self::Value, E>
    where
        E: serde::de::Error;
}

The Deserialize trait can be implemented generically (as in: blanket implementation would have been possible if not for foreign types) for any data structure implementing DeserializeMap. And a DeserializeMap implementation can delegate processing of individual keys to other DeserializeMap implementations as needed.
Implementation here: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=3e86581a385b2922044efb5156c30745
I’ve got derive macros implemented as well but these are specialized for my use case.


WebView cannot connect to a server that uses a self-signed certificate.

Problem description
The app is configured to use trustedCertificates for communication with a server. The app can fetch the content via fetch but WebView cannot show the content. WebView does not handle self-signed SSL certificate properly, Android shows an error in adb logcat output:
E chromium: [ERROR:ssl_client_socket_impl.cc(941)] handshake failed; returned -1, SSL error code 1, net_error -202

The behaviour is same for both Tabris 2.x and 3.x.
Expected behaviour
WebView can connect to a server that uses a self-signed certificate.
Environment

Tabris.js version: Tabris 2.x and 3.x
Device: Galaxy Tab S3
OS: Android 9

Code snippet
cordova config:
...
<preference name="UseStrictSSL" value="true"/>
...

const URL = 'my.server:9443/content';

let response = await fetch('path/to/certificate/file');
const certificate = await response.arrayBuffer();
app.trustedCertificates = [certificate];
ui.contentView.append(new WebView({
    layoutData: {top: 0, bottom: 0, left: 0, right: 0},
    url: URL
}));  // -> shows a blank page

response = await fetch(URL);
// Without setting a trusted certificate fetch also fails but it works as expected when a certificate is set.

const content = await response.text();

This can be closed, I cannot reproduce anymore with Tabris.js 3.6 and 2.x nightly.


Remove TotalDifficulty from RpcBlock

See https://github.com/ethereum/execution-apis/pull/570.
We are currently including TotalDifficulty in RPC block requests solely to match Hive tests. This should be removed once it is deprecated.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/6mkbh6xhau31g
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/6mkbh6xhau31g
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

We are adding this field back in #566 as we need it to run hive engine tests.
We can look into removing it once the hive engine test suite gets updated too


Logger breaks on nested objects

Hi,
I'm facing a real strange problem:
after updating to 0.32.0 the logging service breaks when a nested object is passed.
es:
   const gcloud = require('gcloud')({
        projectId: 'project_id',
        keyFilename: 'fileKey.json',
    });
    const logging = gcloud.logging();

    const resource = {
         type: 'gae_app',
         labels: {
              module_id: 'Test',
              version_id: '1'
          }
    };

   const log = logging.log('test');

   const entry = log.entry(resource, {
     message: 'messaggio di test',
     data: {
          error: 'no error',
           log: 'test'
      }
   });
   entry.severity = "INFO";
   //code breaks here
   log.write(entry, (err, apiResponse) =>{
       console.log(err, apiResponse);
   });

Thanks in advance

I'll look right into this, thanks for reporting!

The returned error is
  /Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:2440
                        throw Error(this+"#"+keyOrObj+" is not a field: undefined");
                        ^

Error: .google.protobuf.Value#fields is not a field: undefined
at Error (native)
at MessagePrototype.set (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:2440:35)
at MessagePrototype.set (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:2434:38)
at Message (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:2363:34)
at ProtoBuf.Reflect.ElementPrototype.verifyValue (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:1877:28)
at new ProtoBuf.Map.Map (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:4894:46)
at ProtoBuf.Reflect.FieldPrototype.verifyValue (/Users/mike/testProject/node_modules/protobufjs/dist/ProtoBuf.js:3427:28)

PR sent: #1303
Please try it out!
$ npm install --save stephenplusplus/gcloud-node#spp--1302

It works this way!
Great!

@stephenplusplus didn't this one make it to 0.33.0 on npm? facing the same issue here in my docker container

It did. Can you paste the code to reproduce and the error?

Yes one sec, ps logging breaks with entries containing boolean fields as well throwing the error:

/src/node_modules/gcloud/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2440
                            throw Error(this+"#"+keyOrObj+" is not a field: undefined");
                            ^

Error: .google.protobuf.Value#booleanValue is not a field: undefined

  bigquery.createDataset(datasetName, function(err, dataset) {
    if (err && err.code !== 409)
      throw err;

    logger.createSink(loggerName, {
      destination: bigquery.dataset(datasetName)
    }, function(err, sink){
      if (err && err.code !== 409)
        throw err;

      console.log('logger service started.');

      log = logger.log('syslogs');

      nc.subscribe('events.logger.error', function(data){
        _syslog(data);
      })
    });

  function _syslog(data)
  {
    var entry = log.entry({}, data);
    log.write(entry, (err, apiResponse) =>{
           console.log(err, apiResponse);
      });
  }

The data I'm writing looks like this:
{ error: 'Unprocessable Entity',
  message: 'Please check your phone number and try again.',
  code: 422,
  retry: false,
  whoami:
   { image: 'service-sms',
     port: 5000,
     online: true,
     host: '<IP_ADDRESS>',
     name: 'sms',
     region: 'local',
     version: '0.0.1',
     dockerhost: '<IP_ADDRESS>',
     publichost: '<IP_ADDRESS>',
     ports: [ 5000 ] },
  severity: 'INFO',
  origin: 'server',
  method: 'send',
  request: { to: 'xx', text: 'hello world' } }

Thanks for the details @1N50MN14 -- could you try out #1329?
$ npm install --save stephenplusplus/gcloud-node#spp--1302-2

Yup, one sec please

It's throwing this error:
/src/node_modules/gcloud/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2440
                            throw Error(this+"#"+keyOrObj+" is not a field: undefined");
                            ^

Error: .google.api.MonitoredResource#image is not a field: undefined

(It's also screaming about autoPaginate elsewhere in my code not being a function, wondering if the datastore query API has changed)

grr sorry my bad sec please

Ok that seemed to have fixed this error! the callback is returns error 400 though, I'm not sure why that is

I receive that as well without providing something like the following as the first argument to the entry:
var entry = log.entry({
  type: 'gce_instance',
    labels: {
    zone: 'global',
    instance_id: '3'
  }
}, ...

yeah that's what I tried to replace, basically I passed my "whoami" object as the resource hence the error I just reported, I will try to place a dummy resource pr your example

the resource object structure seems to be strict and must contain those specific attributes, I tried to add additional labels that didn't work either; but OK that works for me as I'm storing the "whoami" as a part of the entry

Cool, thanks for catching this. It's out now under 0.34.0.

Awesome! Thank you!
Looking at the source of datastore/query.js I see you made some minor modifications there (added info to the cb and got rid of autoPaginate), is this out in 0.34.0 as well?

Yes, that's included as well. Here are the release notes: https://github.com/GoogleCloudPlatform/gcloud-node/releases/tag/v0.34.0


runit issues with Docker

I've been trying to get this to work with Docker but the jenkins_jnlp_slave consistently fails with the error:
warning: /etc/service/jenkins-slave: unable to open supervise/ok: file does not exist

I have a sample project using Test Kitchen and Kitchen::Docker. I added a test fixture to explicitly launch runsvdir but that didn't solve the problem. The runit section of the README goes into a bit more detail.
Interestingly, with the test fixture in place, running kitchen converge a second time is successful. There seems to be something that happens in the 1st converge during or after jenkins_jnlp_slave that makes the 2nd converge work.
My metadata.rb dependencies:
depends "jenkins", "~> 2.3.1"
depends "runit", "~> 1.5"
My Test Kitchen target is:

boot2docker 1.6.2
Virtualbox 4.3.28
WIndows 8.1 host
CentOS 6.6 and Ubuntu 14.04 images

CentOS 6.6 is my production target for both host and container.

This is a dupe of https://github.com/opscode-cookbooks/jenkins/issues/205.


Could not seed from Extended Public Key

seedFromExtendedPublicKey
I couldn't seed from xPubKey, client.openWallet() function returns 'undefined' and client.getStatus() returns an error 'Invalid signature' if I set a random hex string as entropySourceHex. What is entropySourceHex and how do I derive it ?

I got the entropySourceHex from API.export function after seeding using private key. Then again I tried to seed using API.seedFromExtendedPublicKey function using xPubKey, name & entropySourceHex that I got from API.export. But API.openWallet function returns 'undefined' and API.getStatus function returns an error 'Invalid signature'

Hi @aravind-ig , i have the same problem, can you resolve it?


Update supported python and django versions.

Removes Django 2.2-3.1 support.
Adds python 3.7 into the testing matrix.
Adds Django 4.1 and Python 3.10 into the testing matrix.

We should bump the version too, so that the new version has these requirements.

Yeah, the last change should have been a minor version bump as well. I didn't catch that arguments to update_user_groups changed. Oh well.


"Hold Ctrl+Shift over a control to inspect." feature doesn't work anymore

Checked on X11, the feature doesn't work anymore.
Seems to be broken by this particular commit: https://github.com/AvaloniaUI/Avalonia/commit/dbb8427e3a13580ac2cc53558e40d2d50ec21396#diff-7939b3834cb137e873b03c56ff1b5761e064d6e25f36e18aaa5198f34b314aaa
Rolling back this commit fixes it, but I'm not sure if it's required for anything else
@pr8x @MarchingCube @grokys

I think it was calling the RawKeyDown twice before (for key down and up). Is the X11 backend sending raw key down events? Maybe something in the input handling is broken there?


DBZ-8124 Adds info about limiting the scope of FLASHBACK/SELECT grants

DBZ-8124
Provides guidance about how you might reduce the scope of the permissions that you set when creating the Debezium LogMiner user.

@roldanbob Applied, thanks


Crashes on opening file (release/0.1.0 branch, w/ error)

Essentially, when opening my save file:
er-sav.zip
The following error occurs:
assertion `left == right` failed
right = 135
left = 0

The line it points to is in src\user_data_11.rs, in this function:
impl Read for UserData11 {
    fn read(br: &mut BinaryReader) -> Result<UserData11, Error> {
        let mut user_data_11 = UserData11::default();
        user_data_11.unk.copy_from_slice(br.read_bytes(0x10)?);
        user_data_11.regulation.copy_from_slice(br.read_bytes(0x1e9fb0)?);
        user_data_11.rest.copy_from_slice(br.read_bytes(0x56050)?);
        assert_eq!(user_data_11.rest[0], 0); // ERR
        Ok(user_data_11)
    }
}

I can provide partial or full backtrace if needed.
Extra info:
App ver 1.13
Calibration ver 1.13.2
SOTE installed
Both characters (lvl 9 & lvl 149) have been opened on latest patch + with SOTE

In terms of what I'm trying to do; I'm just trying to get the final ending after beating radagon because I lost the save pre-ending

src\user_data_11.rs and the code snippet is not from the 0.1.0 branch, but I updated the latest lib to support the latest regulation. If you build the branch you should be able to read the save file. There's a bunch of still not implemented in this version though.

Thanks!