generating and setting the id value of an annotated field should be moved to  the ObjectIdUpdater

I am trying to make persistence Id annotation work by storing the pojo _id field as string in mongo instead of oid. I had some discussions with mongodb engineers which confirmed that there is not much difference in terms of space and performance between storing/using either data type.
Unfortunately I ran into difficulties writing the right data type to mongo as everything seems to be hardwired in Jongo to force storing the object id as oid. Specifically I found that JacksonObjectIdUpdater#setObjectId should probably be in charge of generating the object id value and updating the pojo. The generation of a default object id is currently done in Insert and JongoCodec. This would bring some of the scattered functionality back together in the ObjectIdUpdater where it is easier to manage the different permutations on how a field is detected and defaulted.

Hello,
You can have a look at
https://github.com/bguerout/jongo-extras/tree/master/javax-persistence
It allows POJO to be annotated with Persistence annotations as follow :
https://github.com/bguerout/jongo-extras/blob/master/javax-persistence/src/main/java/org/jongo/persistence/PersistenceFriend.java#L19
Is it what you are looking for?
On Fri, Mar 13, 2020 at 6:55 AM Niels Bertram<EMAIL_ADDRESS>wrote:

I am trying to make persistence Id annotation work by storing the pojo _id
field as string in mongo instead of oid. I had some discussions with
mongodb engineers which confirmed that there is not much difference in
terms of space and performance between storing/using either data type.
Unfortunately I ran into difficulties writing the right data type to mongo
as everything seems to be hardwired in Jongo to force storing the object id
as oid. Specifically I found that JacksonObjectIdUpdater#setObjectId
https://github.com/bguerout/jongo/blob/2114030d01b707415802129062de71c60a4557ac/src/main/java/org/jongo/marshall/jackson/JacksonObjectIdUpdater.java#L78
should probably be in charge of generating the object id value and updating
the pojo. The generation of a default object id is currently done in
Insert
https://github.com/bguerout/jongo/blob/master/src/main/java/org/jongo/Insert.java#L74
and JongoCodec
https://github.com/bguerout/jongo/blob/master/src/main/java/org/jongo/JongoCodec.java#L65.
This would bring some of the scattered functionality back together in the
ObjectIdUpdater where it is easier to manage the different permutations on
how a field is detected and defaulted.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bguerout/jongo/issues/373, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABWAG2MBJQ3COVSJFHMBVLRHHDGLANCNFSM4LG3NSPQ
.

I did use that configuration as a basis but found quite a few issues with it. Ended up rewriting a bunch of classes and short circuiting the IdUpdate. mustGenerateObjectId() and IdUpdate.setObjectId() methods to default the pojo variable to String OR ObjectId based on what the type declaration of the field was. I will make a public example of this code as it is easier to show in unit tests the different types of scenarios I tried to cover.

On that note, I also had a bit of a look into the "newer" 3.7+ features of the mongo driver and what you tried to do with JongoNative. It looks possible to bridge Jackson directly to the mongo bson components without the need for undercouch. I have a need to use Jackson as the OR mapper as we have a lot of custom modules for Jackson that we would have to "recreate" for mongo driver just to store our models in mongo and put them on the HTTP wire using Jackson.


add env option to limit channel finder PV results on query

New variable - REACT_APP_CF_MAX_RESULTS to give the option to limit the number of results.
If the variable doesn't exist or is left blank, we should just leave the ~size argument off of the CF query
API call example - /ChannelFinder/resources/channels?~name=*&~size=5

https://github.com/ChannelFinder/pvinfo/pull/75


Schema Import failed. property access must not be null

Describe the bug
Importing a Schema is resulting in an import failure.
Import failed

Failed to persist Schema: Validation failed for classes [io.hyperfoil.tools.horreum.entity.data.LabelDAO] during persist time for groups [jakarta.validation.groups.Default, ] List of constraint violations:[ ConstraintViolationImpl{interpolatedMessage='must not be null', propertyPath=access, rootBeanClass=class io.hyperfoil.tools.horreum.entity.data.LabelDAO, messageTemplate='{jakarta.validation.constraints.NotNull.message}'} ]

To Reproduce
Importing a large Schema definition.
Root cause tbc
Version
0.12.2

Java
17

Importing a Schema with this Label definition contains an access property with the value of "PUBLIC".
	"labels" : [ {
    "name" : "kb_report_results_podLatencyQuantilesMeasurement_quantiles_Ready_P99",
    "filtering" : true,
    "metrics" : true,
    "schemaId" : "221",
    "acccess" : "PUBLIC",
    "owner" : "ocp-perfscale-team",
    "extractors" : [ {
      "name" : "P99",
      "path" : "$.results.podLatencyQuantilesMeasurement.quantiles.Ready.P99",
      "isarray" : false
    } ]
  }

The marshalling of the Label to an object is not correctly creating the property with a value. As can be seen in the SchemaService.importSchema method inspecting the Schema object before persisting.

reproducer

There are additional issues with the UI though, the Schema import button is missing since 0.13.0

Using the API to import instead works hence closing this issue.


[False Positive] WTM CD Protect detected on Game Empire CD that does not contain it

BOS currently erroneously detects https://archive.org/details/Game_Empire_Over_250_Games_ADG344AE-CD as having "WTM CD Protect" due to a file named "BH_IMP.DAT".

Fixed by 2f68f95.


FEATURE REQUEST: Better documentation for bulk operations

When performing bulk operations from a .csv or .json file, it is not at all clear what fields are required or how they should be named. Better documentation is needed somewhere - it doesn't have to be from the cli's native --help flag.
For example:
I have a .json file like the (BAD) one below. When I run the CLI command
box files upload --bulk-file-path "{filePath}" --as-user {userID}
I get the error
Object reference not set to an instance of an object.
for each file item I'm attempting to upload. However, if I change the key to "path" from "filePath" it works. THE PROBLEM: I had to guess what the field keys were supposed to be and they didn't match the field names I found in the CLI --help section.
PLEASE FIX YOUR DOCUMENTATION
BAD .json File
[
  {
    "filePath": "O:\\Apps\\e_app_file\\2018\\183141\\From Customer\\BETE.pdf",
    "parent": {
      "id": "56042357153"
    },
    "name": "BETE.pdf"
  },
  ...
]

GOOD .json File
[
  {
    "path": "O:\\Apps\\e_app_file\\2018\\183141\\From Customer\\BETE.pdf",
    "parent": {
      "id": "56042357153"
    },
    "name": "BETE.pdf"
  },
  ...
]

@grugknuckle Sorry about that — this feature is currently a bit difficult to use.  We're working on v2.0.0 of the CLI now (scheduled for release in December) — that version will align the field names in the JSON and CSV bulk input file formats with the argument and flag names in the command help, which should resolve this problem.

Thank you @mattwiller for responding to this. I am happy to hear that your team is working to improve this tool. In the short run, where can I ask for help with the current version of the CLI? The Box community forums are not very helpful at all.

Here in GitHub issues is the best place, since my team monitors these directly and can help investigate any issues you have.

@grugknuckle The latest version of the CLI (v2.0.0) includes a completely reworked bulk input system that matches input properties with the command-line flags and arguments that you can view by running any command with --help.  This should hopefully make bulk input much more intuitive!  Please download the latest version over at https://github.com/box/boxcli/releases/tag/v2.0.0 and give it a try — we'd love to hear any feedback on the new version you might have!

@mattwiller Thank you for this and for your prompt responses. This is a big improvement.


About gitlab link 404

I don't know if it's a gitlab version issue, I made the following changes and it worked in my environment

# 404
"{remote:url}/-/{object}/{branch}/{file:path}/{file:name}{line-block:start}#L{line:start}-{line:end}{line-block:end}",
# worked
"{remote:url}/{object}/{branch}/{file:path}/{file:name}{line-block:start}#L{line:start}-{line:end}{line-block:end}",

Both versions worked for me, but given you've got an example where it does not work, I've updated the template in 4.5.0.


[DBM] Prevent error spam in logs

…ccured
What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Closing this PR since it's still a draft, feel free to re-open it if needed 🙂


Example using an existing Pinecone index & namespace

Hey, is it possible to use an existing Pinecone index? In this example, you create a new one & index it
https://github.com/jerryjliu/gpt_index/blob/main/examples/vector_indices/PineconeIndexDemo.ipynb
Also, not clear if we can use specific namespaces in Pinecone?
Thanks for the great lib anyway 🎸

You could try using the PineconeReader (not the Pinecone Index) to load docs from an existing Pinecone index (https://gpt-index.readthedocs.io/en/latest/how_to/vector_stores.html), and then feed those into a GPT index (e.g. a GPTSimpleVectorIndex or GPTListIndex).
The PineconeReader isn't perfect though, let me know your feedback on that

@louis030195 did you have a chance to try this out?

Side question:
I'd like to insert documents one by one to my Pinecone index, but all I see in the examples is SimpleDirectoryReader(...).load_data(). But my source data is not a directory of text files, it's a string that comes from a web (POST) request.
Here's my current code (simplified):
pinecone.init(api_key="...", environment="...")
pinecone_index = pinecone.Index("...")
index = GPTPineconeIndex([], pinecone_index=pinecone_index)

newtext = """
removed to keep the code short
"""

index.insert(Document(text=newtext))

Is what I'm trying to do even possible?
Should I use Pinecone directly to create/update the index, and use gpt_index for querying exclusively?
It may be obvious but I'm very new to all of this, sorry if it sounds dumb.

See, I can make it work like this:
#insert_one.py

pinecone.init(api_key=PINECONE_API_KEY, environment=PINECONE_ENV)
index = GPTPineconeIndex(documents=[], pinecone_index=pinecone.Index('...'))

index.load_from_disk('../my_index.json')

index.insert(document=Document("document contents"))

index.save_to_disk('../my_index.json')

response = index.query("My question ?", verbose=True)

But I'm relying on a JSON file, the whole point of using Pinecone for me was to keep the data somewhere else, without touching the local filesystem. Is that possible?

from gpt_index import Document
docs = []
for m in r.matches:
    docs.append(Document(
        text=m.metadata["text"],
        doc_id=m.id,
        embedding=m.vector,
    ))
gpt_index = GPTListIndex(docs)
gpt_index.query("What is the future of AI?")

r being the result of a pinecone query. Unfortunately, don't know how to fetch all documents
It's a feature not a bug: ended up using gpt index on a subset of my pinecone index, potentially interesting

This works for me. This allows you to do both - use an existing pinecone index and namespace.
import pinecone
from gpt_index import GPTPineconeIndex
from gpt_index.data_structs.data_structs import PineconeIndexStruct
from IPython.display import Markdown, display

api_key = os.getenv("PINECONE_API_KEY")

pinecone.init(api_key=api_key, environment="us-east1-gcp")

# debug - verify connection
# print(pinecone.list_indexes())

# replace with your index and namespace
index_name = "your_index_name"
namespace = "your_namespace"

index = pinecone.Index(index_name)

# debug - verify index stats
# print(index.describe_index_stats())

# passing index_struct bypasses the 'creation' of index and sets it up for use
index = GPTPineconeIndex(pinecone_index=index,
                         index_struct=PineconeIndexStruct())

# (optional) required only if you want to query a specific namespace
query_kwargs = {
    "pinecone_kwargs": {"namespace": namespace}
}
response = index.query("What did the author do growing up?", verbose=True, **query_kwargs)
display(Markdown(f"{response}"))

This works for me. This allows you to do both - use an existing pinecone index and namespace.
import pinecone
from gpt_index import GPTPineconeIndex
from gpt_index.data_structs.data_structs import PineconeIndexStruct
from IPython.display import Markdown, display

api_key = os.getenv("PINECONE_API_KEY")

pinecone.init(api_key=api_key, environment="us-east1-gcp")

# debug - verify connection
# print(pinecone.list_indexes())

# replace with your index and namespace
index_name = "your_index_name"
namespace = "your_namespace"

index = pinecone.Index(index_name)

# debug - verify index stats
# print(index.describe_index_stats())

# passing index_struct bypasses the 'creation' of index and sets it up for use
index = GPTPineconeIndex(pinecone_index=index,
                         index_struct=PineconeIndexStruct())

# (optional) required only if you want to query a specific namespace
query_kwargs = {
    "pinecone_kwargs": {"namespace": namespace}
}
response = index.query("What did the author do growing up?", verbose=True, **query_kwargs)
display(Markdown(f"{response}"))

Just tried it and it works. I believe index_struct=PineconeIndexStruct() was the missing piece.
Thank you so much!

This works for me. This allows you to do both - use an existing pinecone index and namespace.
import pinecone
from gpt_index import GPTPineconeIndex
from gpt_index.data_structs.data_structs import PineconeIndexStruct
from IPython.display import Markdown, display

api_key = os.getenv("PINECONE_API_KEY")

pinecone.init(api_key=api_key, environment="us-east1-gcp")

# debug - verify connection
# print(pinecone.list_indexes())

# replace with your index and namespace
index_name = "your_index_name"
namespace = "your_namespace"

index = pinecone.Index(index_name)

# debug - verify index stats
# print(index.describe_index_stats())

# passing index_struct bypasses the 'creation' of index and sets it up for use
index = GPTPineconeIndex(pinecone_index=index,
                         index_struct=PineconeIndexStruct())

# (optional) required only if you want to query a specific namespace
query_kwargs = {
    "pinecone_kwargs": {"namespace": namespace}
}
response = index.query("What did the author do growing up?", verbose=True, **query_kwargs)
display(Markdown(f"{response}"))

This almost works for me 😛
Problem is that my text isn't in the key "text" metadata
This
https://github.com/jerryjliu/gpt_index/blob/cab30c4aec7b94c6d12a6efe3fb6b91a605f3869/gpt_index/indices/query/vector_store/pinecone.py#L79
Maybe could have the possibility to customize where it's picked in the metadata, and also considering the fact that the text is not in pinecone index metadata?

See, I can make it work like this:
pinecone.init(api_key=PINECONE_API_KEY, environment=PINECONE_ENV)
index = GPTPineconeIndex(documents=[], pinecone_index=pinecone.Index('...'))

index.load_from_disk('../my_index.json')

index.insert(document=Document("document contents"))

index.save_to_disk('../my_index.json')

response = index.query("My question ?", verbose=True)

But I'm relying on a JSON file, the whole point of using Pinecone for me was to keep the data somewhere else, without touching the local filesystem. Is that possible?

Hey @bouiboui sorry I missed this. Just a heads up that by using the PineconeIndex, your data is stored in Pinecone, not in the .json file. In fact, doing save_to_disk and load_from_disk on the PineconeIndex doesn't really do anything. doing index.insert should work!

going to close for now, let me know if anything specific pops up

This works for me. This allows you to do both - use an existing pinecone index and namespace.
import pinecone
from gpt_index import GPTPineconeIndex
from gpt_index.data_structs.data_structs import PineconeIndexStruct
from IPython.display import Markdown, display

api_key = os.getenv("PINECONE_API_KEY")

pinecone.init(api_key=api_key, environment="us-east1-gcp")

# debug - verify connection
# print(pinecone.list_indexes())

# replace with your index and namespace
index_name = "your_index_name"
namespace = "your_namespace"

index = pinecone.Index(index_name)

# debug - verify index stats
# print(index.describe_index_stats())

# passing index_struct bypasses the 'creation' of index and sets it up for use
index = GPTPineconeIndex(pinecone_index=index,
                         index_struct=PineconeIndexStruct())

# (optional) required only if you want to query a specific namespace
query_kwargs = {
    "pinecone_kwargs": {"namespace": namespace}
}
response = index.query("What did the author do growing up?", verbose=True, **query_kwargs)
display(Markdown(f"{response}"))

Hey @mahpat16, does this still work for you?
I need to use namespaces from now on, and it doesn't seem to work.
query_kwargs = {
    "pinecone_kwargs": {
        # "namespace": namespace
    }
}
response = index.query(message, verbose=True, **query_kwargs)

works great, it generates a natural language response, like "I can't answer with the documents provided".
But if I uncomment the # "namespace": namespace line, it either sends me something like "Empty Response" or it crashes :
text = match.metadata["text"]
TypeError: 'NoneType' object is not subscriptable

@bouiboui I'm facing the same/a similar problem trying to get a multi-namespace index going.

If I attempt to pass pinecone_kwargs in the index function, records are added but no namespace is applied.
If I query with the namespace option I get "Empty Response" back
Commenting out the namespace option means I get results based on the records that are in the index without a namespace

Resolved
You now pass pinecone_kwargs when creating the index rather than in the query/index methods:
index = GPTPineconeIndex(pinecone_index=index,
                         index_struct=PineconeIndexStruct(), pinecone_kwargs={"namespace": namespace})
index.insert(document=(Document(text, doc_id=doc_id)))

It looks like there's been a refactor of the IndexStruct code and PineconeIndexStruct is no longer, so this method no longer works on the latest version of Llamaindex.

hopefully this link could help: https://discord.com/channels/1059199217496772688/1059200010622873741/1079094097916211270

@jerryjliu I've attempted to make a branch that uses what's suggested there but unsuccessfully.
I've resolved this temporarily by pinning to gpt-index==0.4.5 in my requirements.txt
Happy to contribute to this feature once the refactoring has stabilized!

@jerryjliu I've attempted to make a branch that uses what's suggested there but unsuccessfully.
I've resolved this temporarily by pinning to gpt-index==0.4.5 in my requirements.txt
Happy to contribute to this feature once the refactoring has stabilized!


Share Draft Timemaps

If you like, share links to your Google Sheet and published Timemapper here. Let us know if there's something you want to debug here.

I'm gonna test some things with images. Most of them are working fine, but two images in particular haven't been showing up.
I'll be adding these images over the weekend, so the image files can be checked. The areas I might need debugging on are F7 and F8, so if the images don't show on the official website, let me know.
Google sheet: https://docs.google.com/spreadsheets/d/1_Xn7QPDnXbW7TTinEkH0JvU7liOlLJ-uhc0OpvWmQyc/edit?usp=sharing
Time Map: http://timemapper.okfnlabs.org/anon/tyjzzm-time-map-starter-rachel-gerzevske

My Google sheet
ZeTimeMapper


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.0.55 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feature] Support aliyun cloud credential

Fixes #issue
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 20 / 47 (42.55%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/credential/aliyun/AliyunCloudConfiguration.java
0
14
00.00%
[33, 34, 35, 36, 40, 42, 43, 44, 45, 49, 50, 54, 60, 65]

:large_blue_circle:
com/starrocks/credential/aliyun/AliyunCloudCredential.java
9
21
42.86%
[42, 43, 44, 45, 46, 47, 56, 57, 58, 59, 63, 73]

:large_blue_circle:
com/starrocks/credential/aliyun/AliyunCloudConfigurationFactory.java
7
8
87.50%
[46]

:large_blue_circle:
com/starrocks/credential/CloudType.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/credential/CloudCredentialUtil.java
2
2
100.00%
[]

@miomiocat
You need to update documents according to this change list.


Broken dependency for type-fest 0.13.1

Trying to create a new contentful app on the console via "npx @contentful/create-contentful-app init my-first-app" fails since around Christmas time 2020 with the following error:
`Creating a Contentful app in ~/my-first-app.
Creating a new React app in /home/w6/my-first-app.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with @contentful/cra-template-create-contentful-app...
npm
ERR! code ERESOLVE
npm ERR!
ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/type-fest
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/contentful-management
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@contentful/cra-template-create-contentful-app
npm ERR!       @contentful/cra-template-create-contentful-app@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm
ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm
`
node version is 14 LTS.
Please fix this asap, we depend on the contentful app framework, since you declared extensions as deprecated.

@hgeistcb what npm version are you on?

@hgeistcb what npm version are you on?

@kdamball : Hello, its 7.0.15
OS: xubuntu 20.04

@kdamball : Hello, its 7.0.15
OS: xubuntu 20.04

We just updated the recommended npm version as npm v7 breaks when using npx.

We just updated the recommended npm version as npm v7 breaks when using npx.


implement contains on TopicDict

This pull request fixes a bug on TopicDict causing __contains__ to function differently from __getattr__. In python3, the following was possible before this fix:
In [1]: from pykafka import KafkaClient

In [2]: client = KafkaClient(hosts="localhost:9092")

In [3]: client.topics['testtopic_replicated']
Out[3]: <pykafka.topic.Topic at 0x7f81bde9ffd0 (name=b'testtopic_replicated')>

In [4]: 'testtopic_replicated' in client.topics
Out[4]: False

The in operator yielded False despite the same string being used successfully during direct attribute access. This pull request fixes that issue by performing the same string conversion in __contains__ that's performed in __getattr__.

Hold off on merging this until 2.8.0 is released, which should be early next week.

Codecov Report

Merging #871 into master will increase coverage by 0.39%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #871      +/-   ##
==========================================
+ Coverage   83.43%   83.82%   +0.39%
==========================================
  Files          36       36
  Lines        3784     3790       +6
  Branches      561      561
==========================================
+ Hits         3157     3177      +20
+ Misses        481      468      -13
+ Partials      146      145       -1

Impacted Files
Coverage Δ

pykafka/cluster.py
76.55% <66.66%> (+3.89%)
:arrow_up:

pykafka/utils/socket.py
75% <0%> (-6.25%)
:arrow_down:

pykafka/broker.py
91.32% <0%> (-2.9%)
:arrow_down:

pykafka/connection.py
82.17% <0%> (-1.99%)
:arrow_down:

pykafka/simpleconsumer.py
84.4% <0%> (-1.12%)
:arrow_down:

pykafka/balancedconsumer.py
89.47% <0%> (+1.46%)
:arrow_up:

pykafka/handlers.py
94.85% <0%> (+1.47%)
:arrow_up:

pykafka/topic.py
82.47% <0%> (+3.09%)
:arrow_up:

pykafka/partition.py
84.84% <0%> (+12.12%)
:arrow_up:

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 2e79767...4ff13d3. Read the comment docs.


download not possible => ""

When i try to download http://www.zdf.de/ZDFmediathek/beitrag/video/2618996/1.-Schoener-Schein#/beitrag/video/2618996/1.-Schoener-Schein i get following error:
*youtube-dl --verbose http://www.zdf.de/ZDFmediathek/beitrag/video/2618996/1.-Schoener-Schein#/beitrag/video/2618996/1.-Schoener-Schein
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-wci', u'-o', u'%(title)s.%(ext)s', u'--recode-video', u'mp4', u'--verbose', u'http://www.zdf.de/ZDFmediathek/beitrag/video/2618996/1.-Schoener-Schein#/beitrag/video/2618996/1.-Schoener-Schein']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.01.01
[debug] Python version 2.7.10 - Darwin-15.2.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8.4, ffprobe 2.8.4, rtmpdump 2.4
[debug] Proxy map: {}
[ZDF] 2618996: Downloading video info
[ZDF] 2618996: Downloading SMIL file
[ZDF] 2618996: Downloading f4m manifest
[ZDF] 2618996: Downloading m3u8 information
[debug] Invoking downloader on u'rtmpt://cp125301.edgefcs.net'
ERROR: unable to download video data:
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1609, in process_info
success = dl(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1551, in dl
return fd.download(name, info)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/common.py", line 342, in download
return self.real_download(filename, info_dict)
File "/usr/local/bin/youtube-dl/youtube_dl/downloader/http.py", line 58, in real_download
data = self.ydl.urlopen(request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1886, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 454, in _open
'unknown_open', req)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 1265, in unknown_open
raise URLError('unknown url type: %s' % type)
URLError:
youtube-dl --version
2016.01.01
Any Ideas?

It's fixed in the git repo (see 6b461026616b0e3ede9a302c74fc437541e19343 and https://github.com/rg3/youtube-dl/pull/8121#issuecomment-168426918), you can use it or wait for the next release.
Thanks for the report.

I see that on another Machine (also OS X 10.11) it works.
could this be possible?

On the machine which has the Problem i can say that it works with the 6b46102 and #8121 :)


create the partition soon after installing the as3

my major concerns are addressed. One remaining concern for us: HW path.


Code makeup: wallet.balances property

UI Version: 0.X.X
Description:
wallet.balances is currently an array, but the way we are using is seems it should be a dictionary with denom as key (aka Object), most of the time we map or filter through it.

though this may be true, it feels very low impact from a user / launch-prep perspective ...?


Add thread ID to pipeline session

Describe the issue
When interacting with the filesystem in a multi threaded environment it can happen that multiple threads interact with a file/folder on the same moment and causing unexpected behaviour.
To prevent this from happening we would like to use something like the following type of paths:
/temp/{ThreadId}/conversion/
Which will give each thread its own folder to work in.
Although currently a thread id or something is not available in the pipeline session, please add.
Reporter
Laurens

Use the FileSystemListener with the inProcessFolder attribute

I am writing to the filesystem, not listening.

You could also use the messageid to achieve a similar separation

I was assuming that threads woud be re-used but it seems that every message is processed with a fresh new thread, resulting in a new ID.


benchmark mehari

Is your feature request related to a problem? Please describe.
We need to have an idea how mehari compares performance-wise to other tools. This is also useful to avoid performance regressions when refactoring/applying changes to the existing code.
Describe the solution you'd like
We need to define some test data files, a realistic database extract performance numbers. These steps should be easily repeatable for new versions and changes to databases. Input files to be annotated do not need to be changed.
Describe alternatives you've considered
None
Additional context
Any tools/scripts developed should be stored in this repo. Anything too large to be directly stored should be put into a public place, which is easily accessible.

Current execution time on NA-12878 (4,921,200 variants) is 3:29min (23546 variants/s).
CPU: i9-12900K
RAM: 128GB DDR4
HDD: Samsung SSD 970 EVO Plus 2TB (mehari db) + Samsung SSD 990 Pro 2TB (mehari)

VEP Results
TDB

Jannovar results
TBD

open-cravat results
TBD

Nirvana results
TBD

Initial run for all annotators finished.
More extensive comparison work will move to https://github.com/varfish-org/annotation-zoo.


Feedback on actions using an API.

The status bar should be used to display feedback upon posting an event or announcement that requires use of an external service to succeed.

Feedback added for submission of events. Difficult to do so for update or deletion, so that is being postponed unless really necessary.


Updated validations.py python script

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it
On July 31, 2021 at 5:11:06 PM, google-cla[bot] @.***)
wrote:
@googlebot I signed it


Support for PR builds

 • building...                                    commit=610581bd1173202ed06b9ab6b21e537b3731c55c latest tag=v0.0.29
  ⨯ build failed after 0s                    error=git tag v0.0.29 was not made against commit 610581bd1173202ed06b9ab6b21e537b3731c55c

What a weird bug... Of course the tag number isn't made against commit 610581, that tag was an old release. 🤔

 • building...                                    commit=610581bd1173202ed06b9ab6b21e537b3731c55c latest tag=v0.0.29
  ⨯ build failed after 0s                    error=git tag v0.0.29 was not made against commit 610581bd1173202ed06b9ab6b21e537b3731c55c

What a weird bug... Of course the tag number isn't made against commit 610581, that tag was an old release. 🤔

@felleg it's just a check that GoReleaser does, to make sure that the latest tag it found is actually matching the commit it's building, to prevent mismatches.  However, here I'm skipping the tagging for the dry-run, so I just added the --skip-validation flag to avoid that error.


For debugging builds, copy the pdb to bin for shared libraries and embed debugging information in static libraries.

Original pull request by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

This is to tie a few loose ends: pull request #232 has a lot of good stuff but there is a problem in the copying of .pdb, which is actually unrelated to most changes and would have been nicer to have in a separate PR. My PR implements the suggestion of Nikolay as commented in pull request #229, and completes the change of #49 regarding .pdb location to both debug options (Debug and RelWithDebInfo). The recent pull request #239 covers the lib/bin change also part of #49, but leaves the .pdb alone. My PR assumes the lib/bin cange.
I would suggest to pull #56 first, then this PR, then #49 (resolving conflicts). Alternatively, Mario may want to rebase #49 after #56 and this PR have been pulled for a clean merge.
I hope this helps to merge all this before it gets more complicated :-)
(This branch can be closed after pulling)

Original comment by Mario Koerner (Bitbucket: Renreok, GitHub: Renreok).

It's good to see some progress on the CMake topic.
I agree that it makes sense to embed the debug info into the .lib for the static library build with MSVC. I can update my pull request as soon as #56 and this one have been merged.


Fixing misnamed accordion token

Description
Jason Chan found a token misnamed. It is named accordion-small-top-to-text-spacious when it should be accordion-top-to-text-spacious-small. This pr fixes it.
Motivation and context
Make the token names consistent.
Types of changes

 [x] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
 [ ] Minor (add a new token, changing a value; non-breaking change which adds functionality)
 [ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)
Checklist:

 [x] I have signed the [Adobe Open Source CLA](https://opensource.adobe.com/cla.html).
 [x] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum/layout.component/desktop.accordion-top-to-text-spacious-small
UPDATED METADATA - SPECTRUM UUID: spectrum/layout.component/mobile.accordion-top-to-text-spacious-small

SPECTRUM SYNC SUMMARY
NEW TOKENS: (2) accordion-top-to-text-spacious-small/desktop, accordion-top-to-text-spacious-small/mobile
DEPRECATED TOKENS: (2) accordion-small-top-to-text-spacious/desktop, accordion-small-top-to-text-spacious/mobile

TEST COMPLETE

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.accordion-top-to-text-spacious-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.accordion-top-to-text-spacious-small

SPECTRUM SYNC SUMMARY
NEW TOKENS: (2) accordion-top-to-text-spacious-small/desktop, accordion-top-to-text-spacious-small/mobile
DEPRECATED TOKENS: (2) accordion-small-top-to-text-spacious/desktop, accordion-small-top-to-text-spacious/mobile

TEST COMPLETE

Thank you @GarthDB for fixing this! I noticed it was marked as deprecated and then a new one was added. Curious why you did this instead of updating the name?

@lynnhao its a breaking change to just change the name of the token. Anytime we change the name of a token, especially one that's been around awhile, we should deprecate the old name and add the new name as a new token. It gives products some time to update the token without it breaking their code immediately.

@lynnhao its a breaking change to just change the name of the token. Anytime we change the name of a token, especially one that's been around awhile, we should deprecate the old name and add the new name as a new token. It gives products some time to update the token without it breaking their code immediately.

Got it, thank you! I will add this our deprecation notes so that we do this moving forward.

SYNCING spectrum-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum/layout.component/desktop.accordion-top-to-text-spacious-small
UPDATED METADATA - SPECTRUM UUID: spectrum/layout.component/mobile.accordion-top-to-text-spacious-small

SPECTRUM SYNC SUMMARY
NEW TOKENS: (2) accordion-top-to-text-spacious-small/desktop, accordion-top-to-text-spacious-small/mobile
DEPRECATED TOKENS: (2) accordion-small-top-to-text-spacious/desktop, accordion-small-top-to-text-spacious/mobile

WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/spectrum/layout.component/desktop.json
WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum-non-colors/spectrum/layout.component/mobile.json
WROTE: /spectrum-tokens/packages/tokens/src/layout-component.json
SYNC COMPLETE
Spectrum Tokens Pull Request
Tokens Studio Pull Request

SYNCING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
STUDIO SYNC SUMMARY
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/desktop.accordion-top-to-text-spacious-small
UPDATED METADATA - SPECTRUM UUID: spectrum2/layout.component/mobile.accordion-top-to-text-spacious-small

SPECTRUM SYNC SUMMARY
NEW TOKENS: (2) accordion-top-to-text-spacious-small/desktop, accordion-top-to-text-spacious-small/mobile
DEPRECATED TOKENS: (2) accordion-small-top-to-text-spacious/desktop, accordion-small-top-to-text-spacious/mobile

WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/spectrum2/layout.component/desktop.json
WROTE: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/spectrum2/layout.component/mobile.json
WROTE: /spectrum-tokens/packages/tokens/src/layout-component.json
SYNC COMPLETE
Spectrum Tokens Pull Request
Tokens Studio Pull Request


Apitoken support undocumented

Describe the bug
API Token usage is not documented in ConnectionObj. See Discord CredentialObj incorrect
To Reproduce
See CredentialObj
Expected behavior
It looks like apikey (token) is supported but not documented.
Error logs
N/A

fixed from version 10.0.18

Great 🎉


SB-774 Make the cron task tests terminate successfully

Build is ready to test. All cron tests are enabled by default. Just make sure that we are able to run them.

Thanks! Great job! They now all pass properly in a reasonable amount of time! :)


BitRadioButtonList show items horizontally

I need to show BitRadioButtonList items in a line

Thanks for contacting us. We're investigating this issue.
We'll let you know if it's possible to work on this issue or not.

this is closed in #3497 @msynk @msangtarash

This issue has been resolved and it will be available in the next pre-release version. It will be announced when the pre-release becomes ready.

The pre-release has been published. Please give it a try and give feedback.


dApp: Info overlay

Fixes #698
Short description
This PR adds the info overlay for these routes:

Select Hub
Open Channel
Transfer
Transfer (steps)
Channels
Raiden Account
Withdrawal
UDC
Backup State

The text content for the info overlay has been added but the illustrations still remains. These will get added in a separate PR when @MariaNono has finalised them.
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

Navigate to each of the above route and pop open the info overlay by pressing the i icon.

Not sure what more tests to add, feel like I already covered what needs to be covered...

I did a review, but I canceled it. I think we better talk about it in person when you are back from vacation. You did a cool job and I just don't want to overwrite your stuff how I think it should be so we can release it. There is no pressure for that. And I have a bunch of questions where you should get a chance to answer.


Psa cipher and mac abort on error

Addresses #4709 . Ensure that psa_cipher_abort and psa_mac_abort are called on error in some psa_cipher_xxx() and psa_mac_xxx() functions.
Requires Backporting
Yes, for 2.x

Also done for the hash operations, which follow the same pattern.

I think all comments are now addressed (and also in the 2.x backport) - @gilles-peskine-arm and @ronald-cron-arm PTAL


Update check_compliance.py

Add the server/django/staticfiles/img/ directory.

@jonas-rem this needs to be merged before #40.


Update related_website_sets.JSON

AMX Contenido set.

All sugested actions are done.

2018
On Tue, Nov 21, 2023, 5:12 AM CarlosCMI @.***> wrote:

AMX Contenido set.
You can view, comment on, or merge this pull request online at:
https://github.com/GoogleChrome/related-website-sets/pull/126
Commit Summary

2331db3
https://github.com/GoogleChrome/related-website-sets/pull/126/commits/2331db38de6ce04318dae73a7837f34b277d9b7f
Update related_website_sets.JSON

File Changes
(1 file
https://github.com/GoogleChrome/related-website-sets/pull/126/files)

M related_website_sets.JSON
https://github.com/GoogleChrome/related-website-sets/pull/126/files#diff-746a5f8516f5c72945f49b37a671ea4d9a5b9adcd72df02bce0fc3a773a57cdd
(14)

Patch Links:

https://github.com/GoogleChrome/related-website-sets/pull/126.patch
https://github.com/GoogleChrome/related-website-sets/pull/126.diff

—
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/related-website-sets/pull/126, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BAEHW2DM2BP7RIQBTG6JNQDYFPTGVAVCNFSM6AAAAAA7TVWWMGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDGMJZGY3TAOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


convertSourceToRaw enhancement

should be able to convert only one subject (or a subset of files in general)
should remove date entity from json files too

It is merged, but the issue seems to be open... And I tried the version in dev branch, with filtering option on
https://github.com/cpp-lln-lab/CPP_BIDS/blob/dev/src/convertSourceToRaw.m
filter = struct('sub', ['sub-',opt.subjects{1}]);
cfg.dir.output = '/Users/battal/Cerens_files/fMRI/Processed/MoebiusProject/';
convertSourceToRaw(cfg, 'filter', filter)

It successfully copies the source subject specific folder into raw, but it is crashing in removing date entities, please see below.

Error in bids.Schema/load (line 75)
        bids.internal.error_handling(function_name, 'missingDirectory', msg, false, true);

Error in bids.Schema (line 34)
      obj = load(obj, use_schema);

Error in bids.layout (line 110)
  schema = bids.Schema(use_schema);

Error in removeDateEntity (line 25)
    BIDS = bids.layout(pathToDataSet,  'use_schema', false);

Error in convertSourceToRaw (line 74)
    removeDateEntity(rawDir, 'filter', filter);

I can use of course master branch version, no problem. I wanted to ask if my input variables are OK or this function on the dev branch is WIP?

ahh! it is the same branching issue, I am not deleting the message in case someone else would find themselves here (or future me!).
The solution is only using CPP-BIDS repo with bids-matlab submodule. Then all is good.
Related to this function, is the behavior below expected:

it created pipeline_name folder inside raw folder
it puts source copy of the subject there
then it creates the same subject in raw with and without the date suffix versions.

So there's some duplication should be deleted by the user.


Introduce a @Discouraged annotation

Expected Behavior
It should be possible to know which APIs are not yet deprecated, but are strongly discouraged. A typical example is the use of allprojects and subprojects blocks which introduce coupling between projects.
I would suggest to add an annotation like this:
@Discouraged(explanation="This introduces coupling between projects and it can produce unreliable configuration by mutating other project's state", prefer="Use convention plugins if possible", documentation="https://docs.gradle.org/current/samples/sample_convention_plugins.html")
public void allprojects(...) {
}

Current Behavior
Some methods just cannot be deprecated yet because either there are no alternatives, or their use should be last resort. Examples of these are afterEvaluate or allprojects. Sometimes, you have to rely on those, but the long term goal is to remove them, so we should encourage users to use something else. Users should be able to understand that this will eventually be replaced, and the remaining calls should help gathering which use cases are not covered yet.
Context
I have seen multiple times on Slack folks ignoring that using allprojects, afterEvaluate and other methods like these are discouraged. It is no surprise since there's no deprecation yet (for good reasons), but it prevents folks from moving to best practices.

Thank for coining this idea, but we think this wouldn't be implemented. We think we have already enough feature lifecycle stages to deal with different situations similar to this one. The @Deprecated annotation combined with javadoc can be used for this:

just javadoc to give a hint for a user
javadoc +  @Deprecated to give an explanation and a warning
javadoc +  @Deprecated + nagging to give a more intrusive, runtime deprecation warning.

Right, the point of having an annotation was precisely because javadocs are not visible as warnings in build scripts, so miss IDE support, and that @Deprecated is too late.

@Deprecated is too late because it has to be used when the thing is deprecated. afterEvaluate, Task#create etc are not, for good reasons, but they are discouraged. Therefore this annotation could behave, in IDEs, like @Deprecated, but before a method is actually deprecated.

I think you are right that we could handle this better, and it's something that should be addressed in terms of polishing API's and making it harder to do a discouraged action. On the other hand, warnings can be ignored completely by a user and the same thing goes for the docs. Providing a better documentation and howtos is another thing that could be done. But the team decided that adding more stuff for feature lifecycle is not a best way to do it.


Image Viewer

🚀 Feature Proposal
Add a component for images in the component library.
Motivation
Viewing images is necessary for applications.
Example
Patient Profile Image
Relevant Links
https://react-bootstrap.github.io/components/images/

can I take this issue?

@gqycloud it seems to have already been taken by another user. @jackcmeyer can you confirm?

@tehkappa can confirm!

Assigned to @adamdickinson


floatingLabelStyle color in InputDecorationTheme don't changed when error widget or error text exists

Steps to reproduce
Create InputDecorationTheme, and assign floatingLabelStyle.
send it into the ThemeData and assign it in MaterialApp.
Expected results
Expected result is when error widget or text in InputDecoration is not null, make it Theme.of(context).colorScheme.error
Actual results
Actual result is - when I assign error widget or text into the TextField's InputDecoration, floatingLabel not getting color from Theme.of(context).colorScheme.error color, or errorStyle.color.
Code sample
Code sample

static InputDecorationTheme inputDecorationTheme = InputDecorationTheme(
  errorStyle: Styles.bodyPrimaryMedium.copyWith(color: MColors.updated.primaryRed),
  filled: true,
  floatingLabelStyle: Styles.label,
  contentPadding: const EdgeInsets.symmetric(horizontal: 8, vertical: 6),
  fillColor: MColors.white,
  focusColor: MColors.white,
  iconColor: MColors.graySearch,
  prefixIconColor: MColors.graySearch,
  suffixIconColor: MColors.graySearch,
);

TextField example
TextField(
                      controller: TextEditingController(text: 'Test'),
                      decoration: const InputDecoration(
                        labelText: 'Label',
                        errorText: ''
                      ),
                    );

Screenshots or Video

Screenshots / Video demonstration

Logs
No response
Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4 23E214 darwin-arm64, locale en-KZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.88.0)
[✓] Connected device (4 available)
[✓] Network resources
• No issues found!

@abikko
I believe your issue is same as https://github.com/flutter/flutter/issues/143488 in which you can follow-up for further updates.
You may check this workaround to see if it resolves your case or not.
Closing this as a duplicate.


Emotion bindings?

Hi!
Thank you for making this fork, so far everything is working great. 👍
I am curious what and how much work is required to create the Emotion bindings?

@Zolomon hello. Good to know that it's working good 👌
Referring to Emotion, do you mean Emotion as a whole library itself, or only some Material UI related part?

Sorry for the delayed response.
Basically, I am trying to port the following snippet from TypeScript from the MUIv5 Drawer docs:
Specifically, I am getting stuck on how to express the style for this snippet:
        <Drawer
          variant="permanent"
          sx={{
            display: { xs: 'none', sm: 'block' },
            '& .MuiDrawer-paper': { boxSizing: 'border-box', width: drawerWidth },
          }}
          open
        >
          {drawer}
        </Drawer>

I have the following so far:
Mui.drawer [ drawer.variant.permanent
             drawer.open' true
             drawer.children [ drawer' ]
             drawer.sx (
                 xs =
                     [ style.display.none
                       style.innerSlot
                           MuiClasses.drawer.paper
                           [ style.boxSizing.borderBox
                             style.width
                                 Components.drawerWidth ] ],
                 sm =
                     [ style.display.block
                       style.innerSlot
                           MuiClasses.drawer.paper
                           [ style.boxSizing.borderBox
                             style.width
                                 Components.drawerWidth ] ]
             ) ] ] ]

The breakpoints do not appear to function as intended on Firefox v118.0.2 (64-bits), but I am quite sure it is a failure on my part and has nothing to do with your code.
Do you have any suggestions? I have searched through the repository for similar usages and this is what led me to this result.

Ok, understood. Unfortunately, sx-prop bindings I made are not so flexible as they are in TS/JS API. I tried to cover the most common scenarios, but it still lacks some features as, e.g., breakpoints per prop (this one is seems tricky to be expressed via current Feliz API and in terms of F# type system at all).
It easily could be a failure on my side because there are no automated tests for the bindings. Therefore, I haven't tested a lot of things simply because I haven't used them yet. And breakpoint styling is on of them, I suppose.
Regarding the provided example, it seems to me correct, that is how I expected it to work. So, I need to test it to find out what's wrong. Thank you for reporting it 👍

@Zolomon I've made a simple test. Seems like I made a mistake assuming that it's possible to set breakpoints-based styles in other than a per-prop manner. I.e. these aren't actually the equal definitions:
<AppBar
  sx={{
    width: { sm: `calc(100% - ${drawerWidth}px)` },
    ml: { sm: `${drawerWidth}px` }
  }}>

<AppBar
  sx={{
    sm: {
      width: `calc(100% - ${drawerWidth}px)`,
      ml: `${drawerWidth}px`
    }
  }}>

Probably, the 1st one is the correct option and the 2nd one is not. At least I don't see anything similar to the 2nd option in the MUI Docs article about sx-prop usage. I suppose, I misunderstood this thing while I was writing the bindings last year 😕 Summing up, seems like the current bindings doesn't provide a way to set breakpoints-based styles, and it's necessary to come up with an appropriate solution.

As a workaround for now, to make things done, I'd try to define an sx-prop extension overload that takes an obj, and then use this overload to pass it JS object that fits the schema that MUI expects.
An example of such extension (that could be defined in any F# module in your code before the place where it is intended to be used):
type Feliz.MaterialUI.appBar with
    static member inline sx (stylesObj: obj) = Feliz.Interop.mkAttr "sx" stylesObj

Actually, there is no need to define it for each component type. Instead, it could be done just once on some other type, as Feliz's prop, for example:
type Feliz.prop with
    static member inline sx (stylesObj: obj) = Feliz.Interop.mkAttr "sx" stylesObj

Or define it in a new erased type:
[<Erase>]
type muiProp =
    static member inline sx (stylesObj: obj) = Feliz.Interop.mkAttr "sx" stylesObj

It totally doesn't matter for the output JS.


"npm run minify" not working

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'minify' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'preminify', 'minify', 'postminify' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for preminify, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\www\node_modules\sanitize-html\node_modules\.bin;C:\www\node_modules\.bin;C:\Ruby22-x64\bin;C:\ProgramData\Oracle\Java\javapath;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\EMC\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;C:\apache-maven-3.2.5\bin;C:\Program Files\Git\bin;C:\Users\evenay\AppData\Roaming\npm
10 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\www\node_modules\sanitize-html
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c',
11 silly lifecycle   'npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec minify script
14 verbose stack Error<EMAIL_ADDRESS>minify: `npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd C:\www\node_modules\sanitize-html
17 error Windows_NT 6.1.7601
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "minify"
19 error node v6.9.4
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>minify: `npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>minify script 'npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the sanitize-html package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs sanitize-html
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls sanitize-html
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

I had to change the scripts section of package.json to this (for windows)
  "scripts": {
    "build": "browserify index.js > dist/sanitize-html.js --standalone 'sanitizeHtml'",
    "minify": "npm run build && uglifyjs dist/sanitize-html.js > dist/sanitize-html.min.js",
    "test": "mocha test/test.js",
    "prebuild": "npm run test && rmdir dist /s /q && mkdir dist"
  },

Also i had to install the following packages
npm install -g minifier
npm install -g mocha
npm install -g browserify
npm install -g uglify-js

Resolved in 1.16.3.


Boundary processing of depth maps

For depth maps, the invalid pixels are usually set to 0. How to handle the boundary of such data during interpolation?

ps: The primary in rendering is a triangle, so the barycentric interpolation of the triangle and bilinear interpolation may be involved here: mesh formed from image

Hi,
If you set extrapolate = True, the boundary condition specified using the bound keyword will be used to fill out-of-bound values. Would that help?
Cheers
Yael


Introduce new Repo.update_all syntax

I have discussed this a bit more with @ericmj and @michalmuskala, trying to consider upcoming requirements. Here is the new update syntax:
Repo.update_all Post,
  set: [title: "foo"],
  inc: [changes: 1]

update_all will no longer be a macro instead it will receive a series of operations to perform on the data. For more complex cases, one should be able to write:
from p in Post,
  update: [set: [changes: fragment("? + 1", p.changes)]]

In fact, that's what Repo.update_all will internally compile to. We will also use this opportunity to change Repo.update_all  and Repo.delete_all return results to be {count, entries}, paving the way for #460.

Just a heads-up: Mongo won't be able to return entries from update_all or delete_all. I would propose to allow the return value to be {count, nil} in that case.

Ah, yes. The default for now will be nil until we support returning. MySQL can't support it too.


added frameBorder=0 to the shinyframe iframe

We had the problem that Apple Safari Version 11.0.3 (126<IP_ADDRESS>.1) displays a 1-pixel-wide border around the shiny app. Adding frameBorder="0" to the shinyframe iframe fixes that.

I'm assuming the "Login auf deutsch" commit wasn't meant for this PR.

Sure, sorry for that mistake.
Kind regards
Oliver
--
Oliver Flasch

Am 27.03.2018 um 18:18 schrieb Lee Bousfield<EMAIL_ADDRESS>I'm assuming the "Login auf deutsch" commit wasn't meant for this PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @oflasch ,
Thanks for this PR. It seems to happen in other browsers as well.
Just one remark: the 'frameBorder' attribute appears to be deprecated. Could you provide a css-based approach instead, please?

I just added a css-based approach. I also kept the frameBorder attribute, as it seems to be required for Internet Explorer 11 compatibility ( see https://stackoverflow.com/questions/3601273/html5-and-frameborder ).


How to make mainViewController overhead leftMenu

Please tell me how to do:

The mainViewController is located above the left menu.
How to enable the opening of the left menu using swipe right
How to make so that when you open has not changed and does not overlap the color of the status bar of the left menu.
Great thanx!
This is example what i want to do:

How to enable swipe?)


Validate arguments of public methods#CA1062

Source CA1062
Cause
An externally visible method dereferences one of its reference arguments without verifying whether that argument is null (Nothing in Visual Basic).
You can configure this rule to exclude certain types and parameters from analysis. You can also indicate null-check validation methods.
Rule description
All reference arguments that are passed to externally visible methods should be checked against null. If appropriate, throw an ArgumentNullException when the argument is null.
If a method can be called from an unknown assembly because it is declared public or protected, you should validate all parameters of the method. If the method is designed to be called only by known assemblies, mark the method internal and apply the InternalsVisibleToAttribute attribute to the assembly that contains the method.
I implemented a small part so that you could evaluate and point out the necessary corrections.
It would also be nice if you indicated a list of classes (projects) that need to be covered with these tests.
I would suggest creating a issue so that you can solve the problem in parts and also for tracking

@microsoft-github-policy-service agree

Hi @Zombach
Thanks for your contribution in adding these defensive checks.
However, as performance is a key differentiator for Garnet, evaluating the impact of these checks across the wide source base would be a non-trivial amount of effort. Also, in case of a valid scenario that causes a null reference exception because of a missing null check wouldn't be difficult to troubleshoot and root cause the issue. So, as this project generally skews towards performance, will close this PR.
We encourage you to keep contributing and sharing your ideas. Thank you again for your understanding.

Hi @Zombach Thanks for your contribution in adding these defensive checks. However, as performance is a key differentiator for Garnet, evaluating the impact of these checks across the wide source base would be a non-trivial amount of effort. Also, in case of a valid scenario that causes a null reference exception because of a missing null check wouldn't be difficult to troubleshoot and root cause the issue. So, as this project generally skews towards performance, will close this PR. We encourage you to keep contributing and sharing your ideas. Thank you again for your understanding.

Hi
Thanks for the explanation. OK, no problem!
Good luck


Remove destination access from German country rule for track

and also reduce speed for track in general:
defaultSpeedMap.put("track", 10);
trackTypeSpeedMap.put(null, 10);
trackTypeSpeedMap.put("grade1", 15);
trackTypeSpeedMap.put("grade2", 10);

See discussion: https://github.com/graphhopper/graphhopper/pull/2420#issuecomment-934396932

Should we block tracks with grade5?

Almost always an unimproved track lacking hard materials, same as surrounding soil.

A regular car could get stuck here.
https://wiki.openstreetmap.org/wiki/Key:tracktype#Values

Everything not in trackTypeSpeedMap is blocked, yes. I.e. we should think about blocking everything with grade3 or higher.

BTW: I still think that access=destination for motor_vehicles on tracks in Germany is the correct tagging and follows the OSM wiki: https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access_restrictions#Germany


Use flat underlying data representation for better performance?

Using Array[Double] for the storage might lead to better performance on element-wise operation.

I think so. Thanks for your advice.


Setup express dependencies

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Currently there are no dependencies for the express server
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).
N/A
What is the expected behavior?
It should have dependencies for express in case the user wants to build with express server
Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of  react-raise?
N/A
NB: You can drop a comment below for more clarification

Issue fixed


schematic load

schematic load name:CLAIM_4523
produces:
http://mcmonkey.org/paste/32798
schematic load name:CLAIM_4523 filename:CLAIM_4523.schematic
produces no errors like above but says schematic doesnt exist make sure its in the proper folder yadayada, upon checking it is in the right folder and exists.

Corrupt schematic.

Is this issue resolved?

Probably.


chore: remove cross-env

General

✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[x] My code follows the style guidelines of this project
[x] Is the code format correct
[x] Is the git submission information standard?
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@likui628  没看懂 为什么要移除它？

你开发是windows平台吧， windows设置环境变量是用 SET,  linux mac下需要用export NODE_OPTIONS=--max-old-space-size=8192, 这就是为啥你本地打包正常，action失败。
所以 cross-env  就是个为了解决跨平台设置环境变量的工具


fix(deps): update icr.io/cpopen/ibm-operator-catalog:v4.16 docker digest to 14a9d13

This PR contains the following updates:

Package
Update
Change

icr.io/cpopen/ibm-operator-catalog
digest
4d51c70 -> 14a9d13

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.4.18 :tada:
The release is available on:

GitHub release
v1.4.18

Your semantic-release bot :package::rocket:


feat: add readme

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FLINK-33692][Connectors/Kafka] FlinkKafkaProducer could miss super.close

make sure that super.close() must be executed!  #33692

@ustctozm Please rebase your PR

@mas-chen Any thoughts on this? Is this indeed a bug?


What do output_masks do?

Hi @AkariAsai ,
Thanks for the great repo!
I'm trying to adapt your model to a new dataset, I find that there is an output_masks in the graph_retriever/utils.py convert_examples_to_features function, may I check what exactly do the output_masks do? How should I set the masking for positive and negative reasoning paths?
Also, may I clarify how did you set the gold labels for each RNN step, and for the negative paths?
Thanks!

Hi sorry for my late response, I think your understanding is correct! cc @hassyGo

No worries, already resolved the issue.


Fix sample typo

Fix a small typo in a sample comment.

@martincostello thanks for the PR!
@mkArtakMSFT - can you assign?


Update cupy dependency

Switch to requiring cupy 12

Do we want to update the Conda recipe as well?
https://github.com/rapidsai/kvikio/blob/2e74e8ff91027136fde452c4cdcde15fb284a905/conda/recipes/kvikio/meta.yaml#L46

/merge


[website] Show no of stars on testinomial part dynamically

[ ] I have followed (at least) the PR section of the contributing guide.

resolve issue #39206

Check if PR has label / test-label-applied (pull_request)
What does it means ?

This breaks SSR though (disable JS in devtools),
After (left) / Before (right):

We more or less added the same logic in https://github.com/mui/mui-toolpad/pull/2266/files#diff-e33c2710b00a2581859b7e1691ffcec88aad8b0214fe917e8695425a1fba827d.

I think it's enough, but if we are really concerned about it, we can do the same thing as we did for fetching the version history:

I see ~ in that case, I think keeping hardcoded values as a fallback would be enough to address this as well

Hi @noobtuber20103152 ~ just wanted to ask if you are still interested in working on this!

Since this PR is inactive and the author hasn't responded, I'm closing it.


Appstudio update test-component-pac-bchd

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-bchd-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
26 seconds
build-container

✅ Succeeded
9 seconds
sast-snyk-check

✅ Succeeded
13 seconds
inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-bchd-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
26 seconds
build-container

✅ Succeeded
9 seconds
sast-snyk-check

✅ Succeeded
13 seconds
inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-bchd-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
12 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
19 seconds
sast-snyk-check

✅ Succeeded
7 seconds
inspect-image

✅ Succeeded
38 seconds
clamav-scan

✅ Succeeded
29 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
7 seconds
show-summary


Add a tip for using dataclasses for "Using Classes as Dependencies" tutorial

Closes #3114

@tiangolo Would you mind reviewing this PR?

Thanks for the interest and effort! But I prefer to leave it as is, because dataclasses require assuming some knowledge about dataclasses and how they work. And they would only work for some specific cases. They wouldn't necessarily take things like Query(), Body() as default values, or at least the behavior is not certain. And it would require explaining how they work.
I prefer to keep the explanation simple and pure, that makes it obvious that the thing that makes it callable is what would be used to get the information (in this case the __init__(). But in a dataclass that is hidden, so it would require explaining that it's hidden but created automatically, and then it would require explaining that because the __init__() is autocreated, some things would work and some wouldn't.
And although the code is shorter, the explanation and the cognitive load would be higher, explaining what's everything that is happening underneath.
So I'll close this one, but thanks for the effort! :cake:


Feature/Android

Android helper added

@niklastheman This one should be closed now, right? You merged the android helper in a separate PR, right?

@niklastheman This one should be closed now, right? You merged the android helper in a separate PR, right?

Yes, this is obsolete.

Has been solved in other PR.


Vitejs - ReferenceError: Html is not defined (Import Html on every file?)

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the bug has not already been reported

Versions
"@kitajs/html": "^3.0.10",
"@kitajs/ts-html-plugin": "^1.3.3",

Description
Hi, first thanks to produce this lib, it's very usefull for the stack I want to use ❤
I'm actually using it with Vite js, all works fine on development.
I registred globally kita on entry-server.tsx, which is the main entry.

But when I build my project and start it, I got this error.

This is a part of the code I got /dist folder

The only way found to fix the problem is to: import { Html } from '@kitajs/html'; on every .tsx files.
Which not is not convenient.
There is a way to import this Html globally?
Steps to Reproduce
//tsconfig.json
{
  "compilerOptions": {
    "target": "ES2020",
    "useDefineForClassFields": true,
    "module": "ESNext",
    "lib": [
      "ES2020",
      "DOM",
      "DOM.Iterable"
    ],
    "skipLibCheck": true,
    /* Bundler mode */
    "moduleResolution": "Bundler",
    "allowImportingTsExtensions": true,
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    /* Kita */
    "jsx": "react",
    "jsxFactory": "Html.createElement",
    "jsxFragmentFactory": "Html.Fragment",
    "plugins": [
      {
        "name": "@kitajs/ts-html-plugin"
      }
    ]
  },
  "include": [
    "src"
  ]
}

Expected Behavior
No response

Hey @ClementLaval, can you provide a reproducible example?

Yep,
https://github.com/ClementLaval/kitajs-vite


MG+MIS Evaluation For Domain Expert

The MG+MIS documents are ready for evaluation.
MG.pdf
MIS.pdf

Hello Morteza,
I didn't provide feedback on your MG because it was simple and well-written, except for your Hierarchy diagram. I didn't understand the rationale behind leaving the Sequence Data Structure Module alone. Adding a note about this in your document would be helpful. However, I did make some points on your MIS.
MIS_review.pdf


As a user I'd like to see a detailed history of access attempts to any resource within my pod so that I can see who or what is accessing which parts of my pod.

A detailed history of access attempts should include not only the data+time of reads, writes, updates and deletes to my data, but as much context as possible (e.g. who/what accessed the data (i.e. origin headers, auth tokens, etc.), what query params were used (in the case of GET), possibly what cookie state, etc.).
I should also be able to see failed attempts to access my pod, and the reason for the failure (e.g. unauthorized, server-side exception, input validation error, etc.).
This ability could provide the basis for pod-specific analysis applications to be developed (e.g. an app showing a map of the world indicating the locations of people who 'Liked' photos in my Vacation folder).
#11

Just for completeness, this is also made possible if we implement event sourcing (of course it ain't the only way), as proposed in #22

added to readme

Opening this as part of moving all user stories into issues again.


Move eslint-babel to the Lang and Envro section

Eslint-plugin-babel doesn't seem it belong in the best practices section

Thank you!


Support multiple addresses per OVN port

This pull request addresses together with a OVSDB library change https://github.com/greenpau/ovsdb/pull/1 addresses the issue described in https://github.com/greenpau/ovn_exporter/issues/4.

go.mod can be updated properly after the library change is merged.

@rnurgaliyev , thank you for the PR 👍


5x bytebuddy

@heniu20 any idea why it failed here?

@velo Try this
https://github.com/OpenFeign/querydsl/pull/208


Enhancement

Coverage remained the same at 100.0% when pulling c68d043320f6b5e2c96534e3fc49d108e60c8723 on abarrak:master into ef90b2540388125b07f4b405b942892b192bccc1 on dannnylo:master.


auth.ehealth/invite/: add "verifying otp" page

auth.ehealth/invite/: add "verifying otp" page
Summary:

new page with:
- input field "otp" + button "send"
- button "resend otp"
logic:
- after input OTP  - call "POST Tokens" read response "urgent.next" and switching logic:
- REQUEST_APPS - go to next page "Approvals"
- error - view message
- after click button "resend OTP" - call "POST Tokens"
[x] Create spec for FE task
[ ] Create design layout
[x]  Implement
[x]  Deploy
[x]  Test

test passed


Ctrl+P opens print menu instead of the command prompt

Bug Description
Ctrl+P opens print menu instead of the command prompt
To Reproduce
Steps to reproduce the behavior:

Press Ctrl+P
Opens print menu.

Expected Behavior
The command prompt should appear instead.
Screenshots

Desktop (please complete the following information):

OS: Arch Linux, Flatpak
Application Version: 3.2.0

Thanks for reporting this to us! I know keyboard shortcuts can sometimes be confusing, especially if you are new to an app. That's why we created a shortcuts section in settings. Beaver Notes uses Ctrl + P to print a note and Ctrl + Shift + P to open the command prompt. If you need any help or clarification, don't hesitate to ask. Thanks again for opening this issue.

You might want to update your tutorial then :)

Noted! I'll make sure it gets updated.


More verbose newRecord check

the current method checks if the instance has an id, and if not, then it is new. This is fine if the id is created by the server, but if we use the client to create the id, it will never be considered "new" even on the first save. Instead it should use the same method used in the add function.

You say you are using the client to generate an id attribute, I assume doing model.id() returns undefined? I'm reading between the lines here but I think your problem might be that the id attribute is being stored in the changes object until you call save() on the model. What's returned for model.attr("id")?

This PR is old enough I don't recall any of the context. Sorry for letting this sit. Closing.


When my gesture is stationary, the landmarks of the  output are still changing. how to solve this problem?

Hello, I modified the program to input a picture, but when a similar picture is input, the coordinates of the key points of the output gesture will be different. How to eliminate this difference? Thank you！

I don’t think this is possible because the neural net uses the whole image as an input, so even if you change a couple of pixels the result may be different. It shouldn’t vary too much, but it won’t be the exact same.
If you want to compare outputs you can define a template and then compute distance between it and further outputs.


Can't install v6.0.0-beta.3 as a dependency

Running npm install with theo version 6.0.0-beta.3 as a dependency fails with the following error:
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\adarlow\Documents\Design Systems\temp\test-theo\node_modules\theo\bin\theo.js'
This can be verified with a simple package.json and a fresh install:
{
  "name": "test-theo",
  "version": "0.0.1",
  "description": "Testing whether theo installs",
  "dependencies": {
    "theo": "6.0.0-beta.3"
  },
  "author": "ah-adarlow",
  "license": "UNLICENSED"
}

It works fine with the previous version.

Sorry about that! Should be fixed in 6.0.0-beta.4

Thanks for the quick turnaround.


Cow: Watch Willow[\W_]*+TV

Cow requests the watch of the watch_keyword Willow[\W_]*+TV. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Willow[\W_]*+TV has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Dialog prompt component is covered by input widget

Don't know whether there is a good solution for this, but for instance in this case have it already scroll down would be an improvement I suppose.
See:

Don't think this will be an improvement as the title and description would be skipped. User has to read them first before filling in input boxes. Reopen if you have an idea on how user can read title and description while input textbox being focused.


BIT.TRIP Presents... Runner2: Future Legend of Rhythm Alien

This commit adds the port ZIP as well as the screenshot and markdown file.
New Port for BIT.TRIP Presents... Runner2: Future Legend of Rhythm Alien
URL: { Steam page }
bittriprunner2
Instructions:
copy your Linux Game files (runner2, Runner2.png, package.toc and the other 9 folders) to the bittriprunner2 folder
Notes: Beware of a certain thing with the intro, where an unskippable black screen will appear for a few seconds, followed by the narator talking, after which a normal skippable intro proceeds.
Tested on:

RGB20S/uOS
x55/JELOS
351v/AmberELEC
353v/ArkOS
RGB30/JELOS

Please hold on until the RGB30/JELOS isn't finalized, one user says it works fine, another user claims that pressing select acts as pressing start so there's no way to go back through menus. RGB30 has mixed results.

Please hold on until the RGB30/JELOS isn't finalized, one user says it works fine, another user claims that pressing select acts as pressing start so there's no way to go back through menus. RGB30 has mixed results.

Seems like the select acting as start was a user problem, since the game runs fine for that user and has no problem with sound.
@Cebion managed to run it as well after an i386 libasound.so was provided in libs/x86 (as fixed in 2dca84e)

Works okay now, for jelos users having a problem with starting the game need to remove  the  /storage/.config/asound


chore(deps): :arrow_up: update dependency @commitlint/config-conventional to ^18.6.2

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@commitlint/config-conventional (source)
^18.6.1 -> ^18.6.2

Release Notes

conventional-changelog/commitlint (@commitlint/config-conventional)
v18.6.2
Compare Source
Bug Fixes

config-conventional: use default export (#3911) (bc48408)

v18.6.1
Compare Source
Note: Version bump only for package @commitlint/config-conventional

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   optional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/jest-preset-angular
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx/angular
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nrwl/angular
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/angular
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nrwl/angular
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-17T10_13_11_077Z-eresolve-report.txt

npm ERR!


Enable nightly snapshots to be published to sonatype

Story
Developers creating apps may want to take advantage of SNAPSHOTs where features or bug fixes are available

The snapshot build is pushed to sonatype for every trunk merge.
Check https://oss.sonatype.org/content/repositories/snapshots/com/github/intel-hadoop/gearpump-core_2.11/0.4.1-SNAPSHOT/


toplevel: stdenv.lib -> lib

The library does not depend on stdenv, that stdenv exposes lib is
an artifact of the ancient origins of nixpkgs.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Should such a change be done treewide whenever you get the chance to?

Should such a change be done treewide whenever you get the chance to?

Are we in any way fixing anything by this or will this just cause work for people that have expressions relying on this?

How do you mean expressions relying on this?

or will this just cause work for people that have expressions relying on this?

How do you mean expressions relying on this?

How do you mean expressions relying on this?

Nevermind, I thought the change in stdenv was included here. This here in Nixpkgs is good.

How do you mean expressions relying on this?

Nevermind, I thought the change in stdenv was included here. This here in Nixpkgs is good.

Doesn't eval. Fix: https://github.com/Profpatsch/nixpkgs/pull/3
With that patch, nixpkgs-review says it doesn't change anything.

Doesn't eval. Fix: https://github.com/Profpatsch/nixpkgs/pull/3
With that patch, nixpkgs-review says it doesn't change anything.

Should such a change be done treewide whenever you get the chance to?

The end goal is to completely remove stdenv.lib. When we perform it treewide it would make sense to split it into several smaller PRs.

Should such a change be done treewide whenever you get the chance to?

The end goal is to completely remove stdenv.lib. When we perform it treewide it would make sense to split it into several smaller PRs.

The end goal is to completely remove stdenv.lib. When we perform it treewide it would make sense to split it into several smaller PRs.

I’m not sure we necessarily want to completely remove it, because there’ll be lots of external code that uses it. But we don’t want to be using it within Nixpkgs.

The end goal is to completely remove stdenv.lib. When we perform it treewide it would make sense to split it into several smaller PRs.

I’m not sure we necessarily want to completely remove it, because there’ll be lots of external code that uses it. But we don’t want to be using it within Nixpkgs.

yeah, just not use it, maybe add a warning eventually, but that’s far out.
If we give people less examples, they won’t copy it around so much.

yeah, just not use it, maybe add a warning eventually, but that’s far out.
If we give people less examples, they won’t copy it around so much.

@GrahamcOfBorg build dotnetPackages emscriptenPackages haxePackages luaPackages pythonPackages

@GrahamcOfBorg build dotnetPackages emscriptenPackages haxePackages luaPackages pythonPackages


Refactoring: Separate long running parts of playbook-docker.yml into separate RUN statements inside dockerfile

Chore
Describe the chore
I'm currently bisecting supabase/postgres in order to trace this bug that has started appearing somwhere arround ~v*.55 of the image.
Attempting to build older commits has, until now, lead to several build errors during image builds on Mac OSX (even though I'm using docker, which is super weird, but what gives). This is particularly annoying as it happens right after the two main stages of the playbook have finished (building SFCGAL and plv8).
It would probably be a good idea to refactor what is currently one gigantic playbook importing a large number of task files, which then again import more task files, into smaller playbooks that get executed in separate RUN statements.
This would be much more in line with dockers idea of image layers and the docker build cache.
And the most obvious benefit being that I don't have to wait 1h in order to know if a build worked like it's the mid 90's.
If developers aprove this idea, I would like to claim this issue.
Edit: Obviously you don't necessaril have to have separate playbooks files. I think there is a way to execute specific plays from a playbook file with multiple plays. But I also just saw that you use tags for your internal installation, thats ofc also an option.

sorry no one got back to you on this issue
we've recently re-implemented our AMI and docker builds away from ansible so this is no longer applicable + it looks like the source of the bug has been resolve in https://github.com/supabase/supabase/issues/9378
closing for now but if you're still experiencing the issue please let me know


On Mx Macs with brew check if some of the core libraries have been installed in x86_64 mode and bail out

Otherwise the installation will fail later

Fixed in dc/dc3 branch.


Generate API for internal members

Currently there is no way to include in generated result internal classes.
I understand, that the internal members are not Public API.
But may be create special setting to do not filter out internal members?
It seems that sometimes it will be usefull.
My use case:
I try to use PublicApiGenerator to support code review process on changes in my serialization/deserialization process.
I would like to iterate all members used in serialization/deserialization and if something changes - I put additional attention to have these changes in serialization api to be backward compatible.
In my case I serialize/deserialize internal types. And I cannot use PublicApiGenerator to generate API used during serialization - it filtered out internal classes.
And I don't want to expose them as public - to avoid access to my classes from other assemblies.
What do you think about adding special settings to include internal members? Or may be you have some kind of woraround for my case?
Thank you!

I would principally argue that you are trying to use this project for something for which it clearly wasn't designed, and it probably doesn't make sense to extend it in your desired direction.
That being said, I'd also admit that this request might be sensible in certain situations where [assembly: InternalsVisibleTo(...)] attributes are involved. Say you want to generate the public API for assembly A. You're invoking PublicApiGenerator from assembly G. Assembly A carries a [assembly: InternalsVisibleTo("G")] attribute, meaning that A's API surface visible to G encompasses more than just public members. In such a situation, a flag on ApiGeneratorOptions determining whether or not to include non-public members might make sense.

The thing is though if you have InternalsVisibleTo you are no longer the public API you are coupling yourself to the internal API. Given that this tool is called PublicApiGenerator I would argue that it was never the intention to verify internal APIs (not even if you have internals visible to)

Ok.
I agree that internal api is not public api.
But...
May be we can split: api generation (regardless visibility) and facade which working only with public api?
I really would like use this awesome project to generate text from api surface.
In my particular case I use 'internal' modifier only as technical trick to avoid made public a lot of other related classes. But in the meaning, classes which are used to serialize/deserialize data (json in my case) - are public api: if you change them - you can break functionality, break compatibility.
I'm working directly with GenerateApi class to generate public api text, so it will be nice if I can "override" ShouldIncludeType(t) method in following condition:
https://github.com/PublicApiGenerator/PublicApiGenerator/blob/7e11cac7cb87e2c27e73b792a1c20d2ea4af3b23/src/PublicApiGenerator/ApiGenerator.cs#L114
Or, may be just include it in the predicate specified by parameter shouldIncludeType(t)?
What do you think about this type of change?
I think it will not break functionality specified by name (the project will still working with Public API), but also it will provide extensibility point which allow to use this awesome project in some special cases.
I can create PR if you agree with these changes.
Thank you!

@MaxShoshin Are you still interested in that feature?

@sungam3r, are we sure we want to do this, even if it's still requested? Seems to go directly against the project's purpose (see posts above). My vote would go towards closing this as unresolved.

Honestly these is a small probability that requested changes can be implemented even without breaking changes in overall design but I doubt that some CodeCom APIs may not work correctly when mixing public and internal areas. Anyway, this is not at my personal todo list to work with the next months.

@MaxShoshin Are you still interested in that feature?

@sungam3r , it seems that now I have workaround, so it's up to you.

I would say that theoretically I would start working on this issue but only out of "sports interest". From the design point of view this would be a confusing step though. I'm 50/50 to make any decision here so I tend to keep this issue opened for some time.

I'd once more advise against making this feature addition to the project. The question shouldn't be how easy or difficult it is to implement (it's probably easy) nor whether we have spare time to test-drive it for fun, but whether it actually makes sense, given the project's nature / vision / raison d'être (whatever one wants to call it). Once you commit to that extension, you'll have to maintain it indefinitely, and you may start to see follow-up feature requests that stray even further from the spirit of the project. I'd rather we close this issue now and keep the project focused on its core purpose.

I understand. Personally I feel 90/10 to close vs keep.

I'd rather we close this issue now and keep the project focused on its core purpose.

I'm fine either way.