Menus mistakenly look complete when actually further content can be scrolled to

Describe the issue
Selecting the Group menu and then hovering over Security shows a menu as per the attached screenshot.  This menu only shows some of the groups and can be scrolled to see more but due to two factors, most people will look at that and think this is the complete list of groups.  Those two factors are a) that the menu does not extend down as far as it can given the window size; and b) it does not display a scrollbar or some form of 'more below' indicator.
Recommend that the scrollbar is forced to display when an incomplete list is shown, or the bottom line of the menu has a down arrow or some other indicator that there are further entries below.

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This has improved with the recent changes to the way the scroll bars in the menu items work, but the scroll bars can disappear when there's no cursor motion for some time. @holloway - can they be forced to remain on?

@rjsparks unfortunately not, that's an operating system UI rendering issue, mostly on OSX and touch devices. There are CSS properties for overflow: scroll but they're more about whether the user can scroll, not how the scrollbar is rendered.
There are UX patterns to indicate more scrolling... historically some people fake their own scrollbars in JS (which never looks great/native, although performance can be nearly identical), but the contempory solution usually involves JS to dynamically set drop shadows and other indicators inside the scrolling area to enhance the native scrollbar rendering rather than replace it.

I'm happy with any visual indicator.

This has now been deployed to prod.


Implement support for forward declarations of variables

I think this is feature complete for now. Tests for emitc.call, emitc.const,emitc.getaddressof, !emitc.opaque, need to be added/refactored, so they are run on all (applicable) target combinations.


findAll collections fails in oracle

the end point "server/api/core/collections" throw an error when the user is an administrator.
org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ ORA-00932: inconsistent datatypes: expected - got CLOB
The error occurs in the findAll procedure in CollectionDAOImpl and occurs because Oracle does not support ORDER BY with CLOB columns.
In non-admin users SOLR performs the search and works correctly.
The same error occurs in the DAO community
I think CLOB columns are going to be a continuous source of problems.
In Oracle 12 there is a possibility to increase the VARCHAR2 up to 32767 characters by changing a initialization parameter,
CLOB could be changed by these extended VARCHAR2 although this solution might be too restrictive for some users
Any ideas?

I've written a temporary fix to continue testing. Do you think it is an acceptable solution? Do I make a pull request?
String orderBy=context.getDbType().toLowerCase().contains("oracle")
        		? " ORDER BY LOWER(dbms_lob.substr(title.value,length(title.value)))"
        		: " ORDER BY LOWER(title.value)";

 queryBuilder.append("SELECT c" +
                                " FROM Community c" +
                                " left join c.metadata title on title.metadataField = :sortField and" +
                                " title.dSpaceObject = c.id and" +
                                " title.place = (select min(internal.place) " +
                                                "from c.metadata internal " +
                                                "where internal.metadataField = :sortField and" +
                                                    " internal.dSpaceObject = c.id)" +
                                orderBy);

@jvribell : We discourage adding a ton of "if this database, do this" throughout the codebase, as it's a pain to maintain and manage.  Instead, we do our best to rely on Hibernate to translate database syntax for different databases.
That said, based on simple searches, I'm not finding a way to do this in Hibernate HQL syntax.  So, it might be OK here if you moved this logic to it's own utility method, perhaps in AbstractHibernateDSODAO.  That way it's not duplicated into multiple DAO classes (as you noted this same change may be needed by communities & collections).
There's already some other utility methods there related to adding sort/order by, for example https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/core/AbstractHibernateDSODAO.java#L128   It's possible you could even just enhance one of these existing addMetadataSortQuery() methods to better deal with CLOBs...not sure though which approach would be easier for this scenario.

Closing as Oracle Support was removed in https://github.com/DSpace/DSpace/pull/8822


Member detail/成员页

A page that shows the detail of a member.

If possible, we can display the statistics of this member, like number of lives in this month and the average duration of them, in this page.


Find Peak Element in Array

Description
A peak element is an element that is strictly greater than its neighbors.
Given a 0-indexed integer array nums, find a peak element, and return its index. If the array contains multiple peaks, return the index to any of the peaks.
You may imagine that nums[-1] = nums[n] = -∞. In other words, an element is always considered to be strictly greater than a neighbor that is outside the array.
DSA Problem
Peak Element in Array

hi, can you assign me this issue?

@Modernbeast02  Hey! I'm interested  in working on this issue. Can U assign this to me.

Hey @iamdestinychild can I work on this issue as I have done this problem on code chef already


Fidelity heuristic

Description
some major changes in the heuristic mapper:

adds fidelity-aware mapping (which can be used by loading calibration data for the respective architecture and setting configuration.considerFidelity = true) However, for now it is not yet compatible with dynamic initial layout strategies and implements no lookahead.
in the calculation of cost and heuristic of A*-nodes iteration over all gates of the current layer for each node were replaced by iterating over a pre-computed gate multiplicity vector (which was necessary for the fidelity-aware approach, but also increases performance of the current mapping implementation)
the constant edge weights in the Dijkstra implementation were replaced with an edge weight matrix (which was necessary for fidelity-aware mapping, but, too, improves the current non-fidelity-aware heuristic implementation as Dijkstra did not differentiate between the cost of forward- and back-edges there until now)

furthermore:

eliminates (potential) bug previously introduced in #204 where heuristic cost calculation would terminate too early with different layering strategies

Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[ ] I have made sure that all CI jobs on GitHub pass.
[x] The pull request introduces no new warnings and follows the project's style guidelines.

@EliasLF https://github.com/cda-tum/qmap/pull/240 might be interesting for you.


bump-cask-pr: use version substring before comma unless they match

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This shortens the commit message for cask bump PRs such that
Update dotnet from 5.0.10,0a1577a6-a7f1-4da0-ae64-9003ff8badb5:3b3a9291a0bdcb5591afab9e842272db to 5.0.11,f241f934-a4cc-400a-8d03-a5ab50c25fea:1c8600ad088a42b157c073454e80039a

becomes Update dotnet from 5.0.10 to 5.0.11

Great cleanup, thanks @FnControlOption!


Issue Upgrading to Dotnet 3.0

Hi!  Thanks for your work on this library.  I'm trying to upgrade my project from dotnet core 2.2 to 3.0 but I'm getting the following error:
error NU1605: Detected package downgrade: Microsoft.EntityFrameworkCore from 3.0.0-preview.18572.1 to 2.2.6. Reference the package directly from the project to select a different version.
How can I upgrade my project to 3.0?  Is this pending an update?  My project has the following dependencies:
<PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL" Version="3.0.0-preview1" />
<PackageReference Include="Npgsql.EntityFrameworkCore.PostgreSQL.Design" Version="2.0.0-preview1" />

First, please remove Npgsql.EntityFrameworkCore.PostgreSQL.Design - as you can see that package hasn't received an update for several versions because it is no longer needed.
Second, you should be able to get away with referencing Npgsql.EntityFrameworkCore.PostgreSQL 3.0.0-preview9. The actual RTM will probably be out today, so if you can wait a day or two you'll be able to just use 3.0.0.

Thanks @roji !  I think I can wait and I appreciate your response!

FYI 3.0.0 has been released.


Literals of non-primitive types

Describe the bug
This warning pops up in PyCharm about using Literals of non-primitive types:
'Literal' may be parameterized with literal ints, byte and unicode strings, bools, Enum values, None, other literal types, or type aliases to other literal types

on this class for example:
class Olfactometer(HarpDevice):
    """Description of an olfactometer for odor stimuli"""

    device_type: Literal["Olfactometer"] = "Olfactometer"
    manufacturer: Organization.DAQ_DEVICE_MANUFACTURERS = Field(default=Organization.CHAMPALIMAUD)
    # This harp_device_type has issues
    harp_device_type: Literal[HarpDeviceType.OLFACTOMETER] = HarpDeviceType.OLFACTOMETER
    channels: List[OlfactometerChannel]

To Reproduce
Steps to reproduce the behavior:

Go to aind_data_schema.models.devices.Olfactometer in PyCharm
Notice warning

Expected behavior
We should use Literals for primitive types only. For classes or other objects, we need to use a workaround.
Additional context
One workaround is to define the field as:
from aind_data_schema.models.harp_types import Olfactometer, HarpDeviceType

harp_device_type: Annotated[Union[Olfactometer], Field(default=HarpDeviceType.OLFACTOMETER, discriminator="name")]

Can you provide the full example at the bottom? I think it will create some problems in the model construction, especially because it will drop the 'const' tag if i am understanding correctly.

Can you provide the full example of the proposed solution? I think it will create some problems in the model construction, especially because it will drop the 'const' tag if i am understanding correctly.

There's some strange behavior labeling a model as const. I've used this workaround for other similar fields.
from pydantic import Field, BaseModel
from typing import Literal, Union
from typing_extensions import Annotated

class Foo(BaseModel):
  # This is ok
  id: Literal["1"] = "1"
  name: Literal[None] = None

class Bar(BaseModel):
  # This is not recommended because Foo is an object
  # foo: Literal[Foo] = Foo()
  # This is one workaround
  foo: Annotated[Union[Foo], Field(discriminator="id")] = Foo()

bar = Bar()
# Bar(foo=Foo(id='1', name=None))

bar.model_dump_json()

# '{"foo":{"id":"1","name":null}}'

Bar.model_json_schema()

# {'$defs': {'Foo': {'properties': {'id': {'const': '1', 'default': '1', 'title': 'Id'}, 'name': {'const': None, 'default': None, 'title': 'Name'}}, 'title': 'Foo', 'type': 'object'}}, 'properties': {'foo': {'default': {'id': '1', 'name': None}, 'discriminator': {'mapping': {'1': '#/$defs/Foo'}, 'propertyName': 'id'}, 'oneOf': [{'$ref': '#/$defs/Foo'}], 'title': 'Foo'}}, 'title': 'Bar', 'type': 'object'}

Maybe this will also work?
class Bar(BaseModel):
  foo: Foo = Foo()

I am ok with your solution. As i see it is honors the OneOf validation semantic of json-schema! We should probably wrap something around it. I think it should be even possible to automatically create the discriminator by assuming that all fields of the object are literal and picking the first one.

Cool. I may just open a  PR with changing it to an Annotated[Union[...]] type and I can open a separate issue to create a custom type.

I took a quick stab at it... maybe you can figure out a way to finish it haha
There is still some clunkiness to it that i don't like... It should be possible to not use the __call__ override at all, but i am not seeing it yet...

from pydantic import Field, BaseModel
from typing import Literal, Union, Annotated, Optional
from typing import Generic, TypeVar, Type
import types

TBaseModel = TypeVar("TBaseModel", bound=BaseModel)
class LiteralModel(Generic[TBaseModel]):
    __concrete__ = {}
    _discriminator: str
    _t: Type[TBaseModel]

    def __class_getitem__(cls, key_t: type):
        cache = cls.__concrete__
        if (c := cache.get(key_t, None)): return c
        cache[key_t] = c = types.new_class(
            f"{cls.__name__}[{key_t.__name__}]", (cls,), {}, lambda ns: ns.update(_t=key_t))
        return c

    def __init__(self, discriminator: str) -> None:
        self._discriminator = discriminator

    def __call__(self, discriminator: Optional[str] = None) -> Union[TBaseModel]:
        if discriminator is not None: self._discriminator = discriminator
        return Annotated[Union[self._t], Field(discriminator=self._discriminator)]

class Foo(BaseModel):
  # This is ok
  id: Literal["1"] = "1"
  name: Literal[None] = None

LiteralFoo = LiteralModel[Foo](discriminator="id")()

class Bar(BaseModel):
  # This is not recommended because Foo is an object
  # foo: Literal[Foo] = Foo()
  bar: LiteralFoo = Foo()
  foo: Annotated[Union[Foo], Field(discriminator="id")] = Foo()

bar = Bar()

import json
print(json.dumps(Bar.model_json_schema(), indent=2))

A quick stab at it. Still some clunkiness to figure out. Namely how to not have to override and invoke __call__
from pydantic import Field, BaseModel
from typing import Literal, Union, Annotated, Optional
from typing import Generic, TypeVar, Type
import types

TBaseModel = TypeVar("TBaseModel", bound=BaseModel)
class LiteralModel(Generic[TBaseModel]):
    _discriminator: str
    _t: Type[TBaseModel]

    def __class_getitem__(cls, key_t: type):
        c = types.new_class(
            f"{cls.__name__}[{key_t.__name__}]", (cls,), {}, lambda ns: ns.update(_t=key_t))
        return c

    def __init__(self, discriminator: str) -> None:
        self._discriminator = discriminator
        self

    def __call__(self, discriminator: Optional[str] = None) -> Union[TBaseModel]:
        if discriminator is not None: self._discriminator = discriminator
        return Annotated[Union[self._t], Field(discriminator=self._discriminator)]

class Foo(BaseModel):
  # This is ok
  id: Literal["1"] = "1"
  name: Literal[None] = None

class Baz(BaseModel):
  # This is ok
  id: Literal["2"] = "2"

LiteralFoo = LiteralModel[Foo](discriminator="id")()
LiteralBaz = LiteralModel[Baz](discriminator="id")()

class Bar(BaseModel):
  bar: LiteralFoo = Foo()
  baz: LiteralBaz = Baz()
  foo: Annotated[Union[Foo], Field(discriminator="id")] = Foo()

import json
print(json.dumps(Bar.model_json_schema(), indent=2))


[FEAT] Allow objects to be translated in i18nProvider

This PR closes #5364 and is basically a simple type change in the definition of the translate function. The translate function previously only allowed keys to be passed as string which could then be used to retrieve the translation from the real i18n provider via a mapping table. The new interface also allows objects to be passed as keys which for example then allows you to pass an object with locale -> translation mapping:
    const i18nProvider: I18nProvider = {
        translate: (key, params) => {
          if (typeof key === 'object') {
            return key[i18n.language] ?? '';
          }

          return t(key, params)
        },
        changeLocale: (lang) => i18n.changeLanguage(lang),
        getLocale: () => i18n.language,
    };

const translate = useTranslate();
const title = {
  en: 'Switzerland',
  de: 'Schweiz',
}

console.log(
  "Translate",
  translate(title),
);

Test plan (required)
Since the change is only a type change, the implementation itself is up to the end user and thus I think there is no real test needed. However,  I tried to adapt all the existing examples and even improve them by using the I18nProvider interface instead of fixed types.
Closing issues
Closes #5364
Self Check before Merge
Please check all items below before review.

[X] Corresponding issues are created/updated or not needed
[X] Docs are updated/provided or not needed
[X] Examples are updated/provided or not needed
[X] TypeScript definitions are updated/provided or not needed
[X] Tests are updated/provided or not needed
[X] Changesets are provided or not needed

I added a comment to the related issue of this PR here https://github.com/refinedev/refine/issues/5364#issuecomment-1862426688
We've discussed the outcome and decided that it will break the existing i18n provider implementations both on type level and if the first argument is treated as string then it will also break the runtime.
Closing this for now, thank you for the contribution #:pray:


Restrict the table to showing N rows?

Hi,
Is it possible to restrict the table to only showing a maximum number if rows?
Thanks!

This is not possible out of the box, but it should be pretty easy to copy and modify the built-in Table renderer to do something like this if you like.


fix(DotNetPublishCoreCliTask): public -> publish

fixes #181

@jshield thanks! Fix is in the 1.2.9 version: https://www.nuget.org/packages/Sharpliner/1.2.9


Adding support for QNN subtract op

Adding support for QNN subtract operator.
Refactoring the code for QNN Binary operators to use a common infrastructure.

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@anijain2305 can you take a look at this PR.

@zhiics Please take a look as well.

Thanks @shoubhik @zhiics This is merged!


Replace Jetty server with JDK httpserver

httpserver port changes

hi @shoc2020
any updates here?
it's a wonderful PR! Right now the UI works only with jetty version 9.4.10.v20180503
I tried to upgrade it to the last 11.0.12 but it throws
java.lang.NoClassDefFoundError: javax/servlet/ServletOutputStream

Continued in PR#581

Absorbed into https://github.com/Netflix/hollow/pull/581


DecodingError when receiving 401 from API

Bug report
Describe the bug
I've noticed some users sometimes getting NSCocoaErrorDomain - The given data was not valid JSON. (Code: 4864) errors. After some investigation, this seems to happen if requests are made with an expired auth token and the API returns a 401 response with no body (which goes a decoding error in PostgrestBuilder.swift:114).
I think for normal users this can happen, if their system clock is not 100% correct and is running behind a bit.
To Reproduce

Set a very short refresh interval on the server (like 30 seconds)
Setback your test device's time by 1 min
Log in, wait 30 seconds & make any database API request
→ the request will fail with the error mentioned above.

Expected behavior
I believe the SDK should either throw a correct error (401 API error in this case) or even attempt to refresh the token and redo the request.

@leoMehlig I'd love to talk about how you're using the library, and the main pain points you're having  with it.

Thanks @grdsdev! Sure, we are happy to do that. What channel works best for you here?

On Supabase's Discord server https://discord.gg/zwaJcTSF, I'm @grdsdev there.

@grdsdev I've noticed that we are running into the same problem when the project is not running (upgrading or paused). In that case, the API returns status code 540, but the SDK tries to parse a non-existent JSON. For that reason, we can't handle that error correctly on the client.
I think the easiest solution here would be to throw an APIError with the status code if the JSON can't be parsed. I'm happy to submit an PR for that if you agree with that approach.


Review for release

Major changes were committed in 9a0e7d389ff746cd48d00ff2f479f14c4ae9f390. Please review (@lbrensk and @robgur) and comment with acceptance or requests so that I can make a release and push these changes into production at GBIF.

@tucotuco I looked it over and it looks okay, except that I am not sure why "27" and "14" are in the comments for maximum and minimumChronometricAge? Unless there's something I am forgetting, that could be deleted. The rest looks ok to me! I like this format much better to keep track of our defunct terms.

Only because that's where they were in that version of the term. The
examples field didn't exist in term_versions.csv nor in terms.csv. They
were in comments in terms.csv. Just preserving the history.
On Mon, Nov 19, 2018 at 3:10 PM Laura Brenskelle<EMAIL_ADDRESS>wrote:

@tucotuco https://github.com/tucotuco I looked it over and it looks
okay, except that I am not sure why "27" and "14" are in the comments for
maximum and minimumChronometricAge? Unless there's something I am
forgetting, that could be deleted. The rest looks ok to me! I like this
format much better to keep track of our defunct terms.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VertNet/dwc-chronology/issues/4#issuecomment-439988650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcP6yioLHwX_QKJcpt6FfBhALFK33H2ks5uwvP6gaJpZM4YoB1b
.

Changes approved verbally by @lbrensk and @robgur.


Failing to load on MacOS

Starting last night Zavala crashed on me and has failed to load. I have a mid-2014 Macbook Pro at work, and a 2017 Macbook Pro at home. Both running Big Sur 10.4.
Yesterday I created a new outline on my work. When I got home Zavala was open, but crashed as I tried to use it. Upon reload it was showing the new outline with no title. I may have forgotten to title it while at work, not sure. I added a title and forgot about things.
Today, when I got in to the office, Zavala was non-responsive and I had to force quit. It now will not load.
It feels like maybe something has corrupted with iCloud sync? On my phone, everything is showing and loading fine though.
Are there logs somewhere I can look through & post up here for debug?
I haven't tried a reboot yet as I'm in the middle of work and don't need the app atm, but can report back when I do.

I have a known issue that can cause Zavala to not load until a reboot happens. Alternately, you can force quit the filecoordinationd process if you don't want to reboot.
I think I have a solution and plan to release an update in the next couple days that resolves it.

Killing the process did the trick, thanks!

This should be fixed in Zavala 1.0.2.


Add UserAgent

for API statistics purposes

Thank you. I will wait to deploy this.
I want to test to see why it doesn't work on Safari.


Documentation FCM

To document on project how the FCM Data messages works on this project

Issue will be implemented in #28


Android package can't load streaming model, however project can running on the computer. How to setting or changing, about this problem?

Android package can't load streaming model, however project can running on the computer. How to setting or changing, about this problem?

I believe this is fixed on the latest release, would be great if you can test that!

Version 2.9.0-rc  load on Android, from URL and from local path.


Gradle startup should fail explicitly when running on OpenJ9 JDK

Gradle does not support, nor have proper test coverage when operating on an OpenJ9 JDK. Gradle's behavior on OpenJ9 can be confusing to users: it might work, or it might just crash without any notifications: https://github.com/eclipse/buildship/issues/1060#issuecomment-776525221.
Gradle should fail at startup with an explicit message.

We decided to not fail hard on J9 but investigate existing issues to see if there is any need for action wrt J9 support.


release: 3.9.1

This PR is to generate a new release of code-server at 3.9.1
Screenshot

TODOs

[x] mark ready once #2773 is merged
[x] double-check github release tag is the commit with artifacts
[x] test locally
[ ] upload assets to draft release
[ ] publish release
[ ] merge PR
[ ] update the homebrew package
[ ] update the AUR package

Hi! I'm soooo looking forward to this!
Would you be willing to bump the AUR package as well? (It's still on 3.8.9) Or is there a way that I can submit a PR for that?

Yeah, sorry, we fell behind on updating the AUR package! If you want, you can open a PR here: https://github.com/cdr/code-server-aur
Otherwise, I should be able to get to it before EOD Monday!

Note: when I downloaded the artifacts from CI and tried to run the mac build, I ran into some "unidentified developer" warning messages. Not sure if that will happen if we release so we're going to push until Monday.


Brainstorming pipelines to achieve ground beetle identification using AI/ML models

Hi all,
In this issue I am proposing a potential pipeline for ground beetle identification. At the end of the pipeline, I propose a plan for analyzing the image data in the Beetlepalooza 2024 dataset. Below that, I pose some questions and suggest some potential figures/supplementary data that we could make for a pipeline like this one.  I do not have experience with AI/ML models, so please feel free to correct my interpretation of the steps, add steps, suggest improvements, etc. I'd appreciate any advice or corrections. I found most of the resources below from this document.
=================================================
Steps to develop a pipeline that takes beetle samples from imaging to species identification:
1. Take images of beetles

Taking images of beetle individuals from multiple perspectives may better inform the algorithm or allow for increased phenotype extraction. For example, D03 NEON technicians use the enlarged trochanters on the underside of the beetle to identify them as being part of Family Carabidae.
To train their model, EB-Net used images of multiple beetle body parts (e.g. head, elytra, pronotum, mandibles) for individual beetles
Will the AI/ML models be affected by how close-up the image is?
According to ML-morph, lower resolution images may increase the error rate.
According to ML-morph, the ML classifier accuracy will be best for test sets with the same imaging setup (similar background and resolution) as the training images.

2. Associate a species ID with each image

Perhaps we want to associate the hierarchical taxonomies like with BioCLIP? Perhaps just species? Perhaps just Carabidae and non-Carabidae?
The associated ID may depend on how accurate we can make our model.

3. Curate the image data to include markers, segmentation, and/or morphological annotations

I am less sure of how to go about this step
Both  EB-Net and ML-morph first manually position landmarks on their images to train and test a ML model that is able to predict the placement of landmarks in subsequent image datasets
ML-morph creates a model that is able to predict the location of landmarks and the shape produced by the landmarks
Perhaps we want to perform segmentation to measure morphological phenotypes of the beetles -- e.g. binarize the image,  use a tool like ImageJ's watershed to separate out the thorax from abdomen, use a tool like MATLAB's erosion to remove the legs, and measure the area of the leftover elytra. But this is kind of clunky and wouldn't give accurate area measurements for the elytra due to erosion. I imagine there are better segmentation techniques for these purposes but I don't know of them.
From this step, we would designate morphological features that can be used to compare beetle images for the sake of classification. I'm not sure how we could combine these types of phenotypic measurements gleaned from images with beetle anatomy ontologies @JCGiron but I would be interested in knowing. It seems that Masci et al. designed a manual GUI to do "a novel ontology-guided approach to segmentation and classification of complex immunofluorescence images of the developing mouse lung".

4. Train the model to predict annotation location, shape, size, or other desired details using the annotated training dataset and test the model using the test dataset.

Goal is to obtain a model that can accurately predict these annotated features on unannotated beetle images.
From predicted landmark locations and shapes, perhaps we can get phenotype/morphology measurements

5. Use the predicted annotations to associate beetle images with a taxon ID

I don't understand how this part goes. Do we cluster the images based on their predicted annotations/measurements (e.g. cluster in a PCA), and then label beetle images with taxon IDs based on how close the images are to clusters with known IDs? Or does the ML model predict the taxon ID associated with the image the same way it does the placement of the landmarks?
From my understanding, any species we want to identify would need to be contained within the training dataset

=================================================
Following this pipeline using the Beetlepalooza 2024 dataset:

Use individual beetle image Beetlepalooza NEON dataset as input
Species ID is already identified and associated with images
Use elytra measurements as landmarks -- I'm not sure if we can use lines as landmarks, as EB-Net and ML-morph use dots. But I believe we could possibly replace the ends of the lines with dots using position data?
Train and test ML model
Obtain beetle taxon IDs for each image from ML model landmark prediction (again, I'm not sure how this part works)

=================================================
Some questions:

Will the tilted beetles in the Beetlepalooza dataset hinder the ML model?
Does landmark prediction count as phenotype extraction? Can these measurements be associated with the Beetle Anatomy Ontology?
Are elytra width and length measurements enough to classify beetles down to a genus level? Or a species level? Do we need additional annotations?
How would this pipeline differ if we used an algorithm like OpenAI CLIP or BioCLIP? Would we need more images? Are these tools able to predict morphological measurements in addition to associating an image with an ID? Are there other kinds of image ID algorithms that don't use landmarks?
Can other types of ecological data associated with the NEON beetle samples (like sample location, sampling date, temperature/humidity on sampling date) be plugged into the model to improve its identification capabilities?
It would be helpful for me to know about the different ways that ML and AI algorithms are used to ID images, and what data the algorithms use to due it, i.e. is it based on pixel color, pixel location, pixel neighbor associations, all of these things?

=================================================
If we were able to create a model, here are some pieces of data that I would be interested in seeing:

Comparison of ML accuracy in identifying small vs larger beetles
Comparison of ML accuracy in identifying common vs rare beetles
Analysis of ML accuracy in distinguishing very similar beetle species
Analysis of the # of images needed in the training dataset to accurately identify less common beetles
Analysis testing whether it is possible to distinguish ground beetles based on elytra width/length measurements
Analysis examining intra-species variation in morphological measurements identified by the model and whether these variations can be associated with natural selection within the species

I fully support this plan.
Some caveats for genus/species ID's will be covered by @EvanWaite in the What It Takes to Identify a Beetle bootcamp, especially related to identifying from photos alone.

Awesome, thanks @JCGiron. I'm looking forward to that bootcamp! I'll definitely attend to get a better idea of the potential for individual photos to provide enough information in the ID process.

Great ideas in this pipeline workflow @iaviney! We will want to keep in mind the limitations of the 2018-NEON-Beetle dataset (e.g., dorsal view only) we have on hand for the workshop and consider what future imaging efforts should include (e.g., ventral, all angles of body, etc.).


Added Dutch locale file

Same words are kept in English on purpose. If they were translated they wont hold the same message,

Thank you! Released in v1.4.9.


Allow to remove alias

Allow make query removing default alias to add expressions
#21
@TomHAnderson, look if it is what you was expecting

I started editing your README.md when I came across this problem:
Using a value for the field parameter which is not a field on the "row" entity
will not type cast the value for the field.
https://github.com/API-Skeletons/zf-doctrine-querybuilder/blob/master/src/Filter/ORM/AbstractFilter.php#L35
I'd like your feedback about what we can assure the users with here.  That is, if the value is not type cast when it is set as a parameter I'm not sure the query will operate as expected.  Maybe we need unit tests for each primitive type the value may be?

You are right. I will analyze this problem more careful.

My first thought is to use a 'expr' parameter.  This would replace the 'field' and the 'field' could be sent too so the type casting can occur on 'value' but then I see the 'value' as having an expression too.  'field-expr' and 'value-expr'?
Brainstorming here.

We have to think a way that it is easy for the programmer. Create a lot of parameters options can complicate.
What you think to create a regex than try to detect the fieldName from expression and cast the type?

A regex to find the row.field?  I think you could have a value like concat(row.field, row.field) so that won't work.
I agree about limiting the parameters.

You are right again. May be the best way is expr parameter, for field and value.
I can't see at this time a way to escape this.

'expr': 'concat(row.fieldname, row.field2name)',
'field': 'fieldname',
'value': 'cannot_have_expr',
'type': 'eq'

If expr then $field = expr
This seems like a nice compromise to me.  Just allow an expression on the left side of the comparator.  Continue to use the field name to type cast the value.  This isn't giving the api consumer everything but enabling expressions is something they don't have now.
Don't start coding it yet; let's keep bouncing the idea around for now.

It's seem ok. If you need a expression in value, you can do this with PHP.

Right.  Let's not forget we're using a plugin manager so it's easy to add more if the user needs them.

Ok

If you take out no-alias and instead replace $field with expr if it exists, will that satisfy the requirements which led you to this PR?

yes, I can do this way

OK.  Please redo this PR (or create a new one) which implements expr as an option and requires field and value so the value can still be type cast to the field.  It's possible for an expr to contain multiple fields e.g. concat(row.name, innerJoinIncludedAlias.name).
It would complicate these filters to allow for innerJoin included fields to be type cast to their respective entities.  So, the field will not allow for an alias including row.  The field must be a field name on the primary (row) entity.  A user using an expr including data not in the primary entity must best-guess the field to type cast the value from the primary entity.

If the row entity has only an integer id and string name but joins to a entity through innerJoin with a datetime value and the expr is DATE_ADD(innerJoinEntity.createdAt, 10, "DAY") then we need a way to specify the type cast exactly.
What about a new directive data-type which must be one of (string, integer, boolean, decimal, float, date, time, datetime) to override the value data type.  This could be used for any filter, not just expr.

I think it will be better in another pull request, only for this, a option to explicity and override type.


bitrate not working

When trying to display the bitrate, the variable 'bitrate' does not show anything on the display.
Using volumio, on the cli with command 'volumio status' I can see the bitrate just fine with a value of 128 kbps.

Ok.  I just looked into this and found out that Volumio has only recently added bitrate to the list of status variables it supports.  I made a quick but untested change to musicdata_volumio2.py to address this.  If you are running the latest code from the 'master' branch just pull the latest and give it a try.
If you are not running from the 'master' branch, let me know what specific version you are running and how it was installed and I'll try to give you direction to install the change.

Hi, Is it also possible to add a widget for the file type and the current ip?
Thank you

perfect! Works like a charm, thank you!


[BUG] unwanted size-plugin.json file

Hello,
Since latest release 2.0.0 a size-plugin.json file is created.
Passing option writeFile: false doesn't help to prevent that.
I guess this is bug introduced with the new release as I nothing change on my side.
Cheers :)

Just a friendly ping... have you been able to reproduce the bug on your side?

@jimblue yup, it was my mistake.
fixed in #27

Hope this can be merge soon :) thank you

@jimblue for now I've published a patch update (2.0.1) that fixes writeFile:false so it doesn't write the file.

awesome tks @developit

This problem have resolved?
The option writeFile: false still create a size-plugin.json file on v2.0.1.

Indeed @sectsect is right, just try with version 2.0.1... not resolved!

@developit can you reopen this issue please

@developit ?

@developit
Can you reopen this issue?


Add in curation bonding curve functions to contracts

Adds the following curation functions to take subgraph data, and get the results from the bonding curve math. This means we will not have to call an ethereum node to get this data. The functions:
- tokensToNSignal()
- nSignalToTokens()
- tokenstoSignal()
- signalToTokens()

Added some simple tests as well.
I think best if Ariel can review in detail, nena just take a look to see how it is formatted and how you can incorporate it in the front end.

Closing this because common-ts uses node specific packages, and thus fails in the front end. We need to port these functions to a new front end package , which is something I will work on with Nena


subprocess.Popen().wait() at the end of stdout collection... Fix #64

Limit supported python to < 3.5 (v2.0+ for 3.5+)
Reduce CI jobs and packages amount on PyPI
Requirements ad PEP0508 only (standard is not young)

6 00 000 cycles with no failure reproduce


Disable usage eval in Javascript code

Is there a way to disable usage of eval in Javascript code? I wish to call duk_eval from C code and not JS.

Similarly avoid usage of Function constructor.


quasar build breaks with UnhandledPromiseRejectionWarning

When building a project in QuasarFramework I receive the following error:
(node:6208) UnhandledPromiseRejectionWarning:   TypeError: Cannot read property 'preset' of undefined

  - index.js:525 compiler.hooks.emit.tapAsync
    [app.harabello.com]/[quasar-icon-factory]/lib/index.js:525:32

(node:6208) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:6208) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Command: quasar build -m pwa -t mat
Quasar version: 0.17.19
quasar-icon-factory version: 1.1.0

This issue is no longer relevant because the new structure of the app-extension does not hook into webpack. There might be similar issues, but never this one. :)


Delete Data

Summary
The user wants to delete their experimental data from the repository.
Basic Path

The use case starts when a user indicates that he/she wants to
delete data from the system.
The system presents a dialog for the user to enter details regarding the data.
The system checks that the data exists.
The system authenticates and verifies the user credentials against the data.
The system retrieves the data.
The system asks for final confirmation from the user.
The system deletes the data.
The system records a timestamp.
The system displays a deletion confirmation message and sends a confirmation email to the user.

Alternative Paths
Step 4: If the system is unable to verify the user’s credentials against the stored data, the system displays a message and repeats step 2.
Step 3: If the data does not exist, the system displays a message and repeats step 2.
Exception Paths
The user can cancel the operation before step 7.
Preconditions
The data exists in the repository.
Postconditions
The data no longer exists in the repository.

I will be assuming the User has made a query that has returned data (either Heart or Personal) in a table format. When this table component is being generated, i'm thinking a simple button can be added onto the end of the table row, that may either have data associated with it or grabs data from the row it is on, and when clicked it uses that data (user_id/document_id) to delete the row. I think this will look quite streamlined.
Or, when the user click on some data/row, a modal appears with maybe the same form they used when inputting the data (for consistency) that is prepopulated with that data. And an Update and Delete button is there.
In terms of components, I don't think I will need anything massive, rather the allowance of a button in however we decide to show/display the data.

Prerequisite component assume would be a grid table of that lists out the data.

Ensure there is a 'Composables' folder
Make new function called deleteDocument
Use boilerplate code from the slides to connect to Firestore using .env variables
Find and note any Document ID for test purposes in Firestore console
Make sure you can actually get document from Document ID
Change boilerplate code so that this document can be deleted
Verify document IS deleted
Change 'Test Document ID' to ID of user chosen document - Blocker: still need to determine HOW this will be done.
Modify data displayed to include <button @click="deleteDocument">Delete</button>

Composable Attempt
async function deleteDocument(doc_id){
   const doc_ref = doc(firebaseStore, "hcm", doc_id);
   const docSnap = await getDoc(doc_ref);
   if( docSnap.exists() ){
      deleteDoc(docSnap.ref);
   }
}

Do not need to send confirmation email to user.

Delete buttons should only appear on data that the user has added only.

Done


Remove ci/pr/required-check from bors.toml

This could be an alternative to #4920 but bors is not very useful if it checks only cabal files.

@newhoggy what about requiring a minimal cicero job that would only do the nix build of cardano-node for linux? I think that should avoid most of the failures of cicero build while still ensuring a minimal nix support for cardano-node master.

You can put a cicero job in CI if you like but we are not using it with bors. It's been pretty bad for the past few months merging things into cardano-node with cicero. We are going to use github actions. We can notify devops when other jobs fail but that should not encumber my team.

bors r+


Test

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Closing as this appears to be an accidental PR. Please ensure you don't send PRs that include private data.


feat: Protocol Specification changes 2

What I did

Added a table under # Verbs categorizing each verb's purpose.
Refactored the pkam verb by moving it with the rest of the authentication verbs
Added plookup:bypassCache:true as one of the examples
Added the delete verb
Added messageType:text as an example in the notify verb
Updated notify verb regex
Added notify:status documentation
prefix key: to data: under from verb response section
moved update and update:meta to above the delete verb

TO DO

[x] plookup automatic cache explanation (plookup'd public keys are cached by default)
[x] updatedOn metadata typo
[x] give titles for each verb example (especially notify:Delete which is confusing)
[x] ttr 0, -1, > 0, and null, explanation differences
[x] from response ?

Screenshots
Verb Table

The delete verb

Notify:status verb

Plookup verb

closes #181
closes #198
This PR is the same as #245 but with resolved merge conflicts

Looks really good @JeremyTubongbanua ! Spotted one more typo you need to fix ... but I'll approve the PR now so you're not waiting for me to approve again after you fix it.

Oops,, we have the GitHub setting enabled where it asks for a review again if I push code.
@XavierChanth can you please approve and merge if you think it's good?

@XavierChanth Please merge

Merged, as I found myself here anyway.


Agent monitor web application

A simple web application for monitoring market participants would be useful for testing automated trading algorithms.

At least the following information should be displayed:

cash
inventory
orders
trades

This information can be derived from PMR.

This is being implemented as a React/Play application in a separate repository.

This is not particularly relevant anymore.


chore: Upstream merge to Mandalay as if 02-10-2022

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.523%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
230

Relevant Lines:
474

💛  - Coveralls

It doesn't seem like anything substantial changed since the last merge to upstream. Do we need this merge?


(suggestion/request) please add the ability to swap armors when right clicking on stand instead of taking them off the stand

just that
when you right click on the stand it should take your current armor and put it on the stand and take the stand armor and put it on you.
right now i have to go trough 4 steps take all my armor off. take all the items off the stand. put the armor on. and put the items 1 by 1 on the stand.

Same as I described on the other issue. Unless it's a vanilla mechanic I'd rather not do it. I want my armour stands to behave as much as possible as the 1.8 ones. Sorry )=


Read - Association Rule Based Classification, A Thesis submitted to Worcester Polytechnic Institute

Assignees please read this paper!

Association Rule Based Classification.pdf

Association.Rule.Based.Classification.pdf
Report Submitted through literature survey.


the demands about "Read Parquet files".

Hey chrislusf:
I talked with xitongsys who is the owner of  parquet-go about gleam, he likes to help with "Read Parquet files" , he is rewriting it now, he wants to know the demands in the gleam, could you list some at here?

That's super!
All the ORC file reader is very similar to parquet reader. All ORC related content is in this single file:
https://github.com/chrislusf/gleam/blob/master/plugins/file/orc/orc_file_reader.go


Fix node duplication in scene sub-inheritance

This was initially done for 2.1, but I think that master also needs it.
UPDATE: Still happens sometimes. :( Not ready for merging.
UPDATE: This may also fix some issues with properties of inherited nodes (and even connections and groups). Or even broken something there. If have no time to look for the improvements in that regard, so if someone finds this is fixing some issue of that kind, please report them as such.

Good point.
I overlooked that while porting to master. Will be present on the next push.
El 08/03/2017 a las 16:17, volzhs escribió:

@volzhs commented on this pull request.

In scene/resources/packed_scene.cpp
https://github.com/godotengine/godot/pull/7979#discussion_r104939104:

}

  return nid;

}
+
+int SceneState::_find_base_scene_node_remap_key(int p_idx) const {
+

for (Map<int, int>::Element *E = base_scene_node_remap.front(); E; E = E->next()) {

if (E->value() == p_idx) {

	return E->key();

}

}
+}

maybe should return -1 at the end of method.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/7979#pullrequestreview-25795768,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCtmRodf2vy0RgSpODySIYW-JieB6Mks5rjsaHgaJpZM4MWOcm.


Steps to reproduce

tidb-lightning integration test fails in create table
tikv panic log as follows:
[2020-08-31T10:28:27.692Z] [2020/08/31 18:14:41.452 +08:00] [FATAL] [lib.rs:481] ["assertion failed: `(left == right)`
  left: `1`,
 right: `2`"] [backtrace="stack backtrace:
   0: tikv_util::set_panic_hook::{{closure}}
             at components/tikv_util/src/lib.rs:480
   1: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:524
   2: rust_begin_unwind
             at src/libstd/panicking.rs:431
   3: std::panicking::begin_panic_fmt
             at src/libstd/panicking.rs:385
   4: tidb_query_datatype::codec::batch::lazy_column_vec::LazyBatchColumnVec::assert_columns_equal_length
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/macros.rs:16
   5: <tidb_query_vec_executors::util::scan_executor::ScanExecutor<S,I> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/util/scan_executor.rs:172
      <tidb_query_vec_executors::table_scan_executor::BatchTableScanExecutor<S> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/table_scan_executor.rs:110
   6: <tidb_query_common::execute_stats::WithSummaryCollector<C,T> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/interface.rs:108
   7: <alloc::boxed::Box<T> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/interface.rs:77
      <tidb_query_vec_executors::selection_executor::BatchSelectionExecutor<Src> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/selection_executor.rs:179
      <tidb_query_common::execute_stats::WithSummaryCollector<C,T> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/interface.rs:108
   8: <alloc::boxed::Box<T> as tidb_query_vec_executors::interface::BatchExecutor>::next_batch
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/interface.rs:77
      tidb_query_vec_executors::runner::BatchExecutorsRunner<SS>::internal_handle_request
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/runner.rs:504
   9: tidb_query_vec_executors::runner::BatchExecutorsRunner<SS>::handle_request::{{closure}}
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/components/tidb_query_vec_executors/src/runner.rs:389
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/mod.rs:74
      <tikv::coprocessor::dag::BatchDAGHandler as tikv::coprocessor::RequestHandler>::handle_request::__handle_request::{{closure}}
             at src/coprocessor/dag/mod.rs:152
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/mod.rs:74
      <core::pin::Pin<P> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/future.rs:119
      <minitrace::future::TraceWrapped<T> as core::future::future::Future>::poll
             at /rust/git/checkouts/minitrace-rust-4a91d55623f07cfc/de69110/src/future.rs:107
  10: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/future.rs:119
      <minitrace::future::TraceWrapped<T> as core::future::future::Future>::poll
             at /rust/git/checkouts/minitrace-rust-4a91d55623f07cfc/de69110/src/future.rs:107
      <tikv::coprocessor::interceptors::tracker::Tracker<F> as core::future::future::Future>::poll
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/coprocessor/interceptors/tracker.rs:45
  11: <tikv::coprocessor::interceptors::concurrency_limiter::ConcurrencyLimiter<PF,F> as core::future::future::Future>::poll
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/coprocessor/interceptors/concurrency_limiter.rs:101
      tikv::coprocessor::endpoint::Endpoint<E>::handle_unary_request_impl::{{closure}}
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/coprocessor/endpoint.rs:402
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/mod.rs:74
      <minitrace::future::TraceSpawned<T> as core::future::future::Future>::poll
             at /rust/git/checkouts/minitrace-rust-4a91d55623f07cfc/de69110/src/future.rs:77
      tikv::read_pool::ReadPoolHandle::spawn_handle::{{closure}}
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/read_pool.rs:139
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/mod.rs:74
  12: tikv::read_pool::ReadPoolHandle::spawn::{{closure}}
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/read_pool.rs:115
      <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/future/mod.rs:74
  13: <yatp::task::future::Runner as yatp::pool::runner::Runner>::handle
             at /rust/git/checkouts/yatp-e704b73c3ee279b6/3894a86/src/task/future.rs:254
  14: <tikv::read_pool::ReadPoolRunner<E,R> as yatp::pool::runner::Runner>::handle
             at /home/jenkins/agent/workspace/build_tikv_multi_branch_master/tikv/src/read_pool.rs:169
      <yatp::queue::multilevel::MultilevelRunner<R> as yatp::pool::runner::Runner>::handle
             at /rust/git/checkouts/yatp-e704b73c3ee279b6/3894a86/src/queue/multilevel.rs:245
      yatp::pool::worker::WorkerThread<T,R>::run
             at /rust/git/checkouts/yatp-e704b73c3ee279b6/3894a86/src/pool/worker.rs:48
      yatp::pool::builder::LazyBuilder<T>::build::{{closure}}
             at /rust/git/checkouts/yatp-e704b73c3ee279b6/3894a86/src/pool/builder.rs:91
      std::sys_common::backtrace::__rust_begin_short_backtrace
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/sys_common/backtrace.rs:130
  15: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/thread/mod.rs:475
      <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/panic.rs:318
      std::panicking::try::do_call
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/panicking.rs:342
      std::panicking::try
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/panicking.rs:319
      std::panic::catch_unwind
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/panic.rs:394
      std::thread::Builder::spawn_unchecked::{{closure}}
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/thread/mod.rs:474
      core::ops::function::FnOnce::call_once{{vtable.shim}}
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libcore/ops/function.rs:233
  16: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/liballoc/boxed.rs:1078
      <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
             at /rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/liballoc/boxed.rs:1078
      std::sys::unix::thread::Thread::new::thread_start
             at src/libstd/sys/unix/thread.rs:87
  17: start_thread
  18: __clone
"] [location=/rustc/16957bd4d3a5377263f76ed74c572aad8e4b7e59/src/libstd/macros.rs:16] [thread_name=unified-read-pool-7]

this panic can reporduce stably.
for more detail log, see: https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/lightning_ghpr_test/detail/lightning_ghpr_test/1462/pipeline/50
What did you expect?
What did happened?

/label sig/coprocessor

@glorv Does this issue still exist?

I think it's fixed.


[stable/rocketchat] failed to connect to server [rocketchat-mongodb:27017] on first connect

Describe the bug
RocketChat pod cannot authentication with mongodb.
Version of Helm and Kubernetes:
[root@e6420 rocketchat]# helm version
version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}

[root@e6420 rocketchat]# kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3+k3s1", GitCommit:"5b17a175ce333dfb98cb8391afeb1f34219d9275", GitTreeState:"clean", BuildDate:"2020-02-27T07:28:53Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3+k3s1", GitCommit:"5b17a175ce333dfb98cb8391afeb1f34219d9275", GitTreeState:"clean", BuildDate:"2020-02-27T07:28:53Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/rocketchat
What happened:
Deploying Rocketchat with the helm chart results in the RocketChat pod throwing the following error:
[root@e6420 rocketchat]# kubectl logs -f rocketchat-rocketchat-6bc74bdc8d-g82ss
/app/bundle/programs/server/node_modules/fibers/future.js:313
                                                throw(ex);
                                                ^

MongoNetworkError: failed to connect to server [rocketchat-mongodb:27017] on first connect [MongoError: Authentication failed.
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/auth_provider.js:46:25
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:215:18
    at Connection.messageHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connect.js:334:5)
    at Connection.emit (events.js:210:5)
    at processMessage (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connection.js:364:10)
    at Socket.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connection.js:533:15)
    at Socket.emit (events.js:210:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:182:23) {
  ok: 0,
  errmsg: 'Authentication failed.',
  code: 18,
  codeName: 'AuthenticationFailed',
  operationTime: [Timestamp],
  '$clusterTime': [Object],
  name: 'MongoError',
  [Symbol(mongoErrorContextSymbol)]: {}
}]
    at Pool.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/topologies/server.js:431:11)
    at Pool.emit (events.js:210:5)
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:557:14
    at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connect.js:109:5)
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connect.js:352:21
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/auth_provider.js:66:11
    at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:215:18
    at Connection.messageHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connect.js:334:5)
    at Connection.emit (events.js:210:5)
    at processMessage (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connection.js:364:10)
    at Socket.<anonymous> (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connection.js:533:15)
    at Socket.emit (events.js:210:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:290:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:182:23) {
  name: 'MongoNetworkError',
  errorLabels: [ 'TransientTransactionError' ],
  [Symbol(mongoErrorContextSymbol)]: {}
}

What you expected to happen:
Functioning Rocketchat
How to reproduce it (as minimally and precisely as possible):
Use the following values.yml
image:
  tag: 3.0.3

mongodb:
  mongodbRootPassword: rocketchat
  mongodbUsername: rocketchat
  mongodbPassword: rocketchat
  mongodbDatabase: rocketchat

ingress:
  enabled: true

helm install rocketchat stable/rocketchat -f values.yml --namespace rocketchat

If I try to connect manually from another pod in the same namespace I get a similar error when trying with either the contents of MONGO_URL or MONGO_OPLOG_URL.
[root@fedora /]# mongo "mongodb://root:rocketchat@rocketchat-mongodb:27017/local?replicaSet=rs0&authSource=admin"
MongoDB shell version v4.2.3
connecting to: mongodb://rocketchat-mongodb:27017/local?authSource=admin&compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0
2020-03-15T21:26:05.061+0000 I  NETWORK  [js] Starting new replica set monitor for rs0/rocketchat-mongodb:27017
2020-03-15T21:26:05.061+0000 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to rocketchat-mongodb:27017
2020-03-15T21:26:05.063+0000 I  NETWORK  [ReplicaSetMonitor-TaskExecutor] Confirmed replica set for rs0 is rs0/rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017
2020-03-15T21:26:05.063+0000 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017
2020-03-15T21:26:05.065+0000 I  NETWORK  [ReplicaSetMonitor-TaskExecutor] Confirmed replica set for rs0 is rs0/rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017
2020-03-15T21:26:05.108+0000 I  NETWORK  [js] Marking host rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017 as failed :: caused by :: Location40659: can't connect to new replica set master [rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017], err: AuthenticationFailed: Authentication failed.
2020-03-15T21:26:05.108+0000 E  QUERY    [js] Error: can't connect to new replica set master [rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017], err: AuthenticationFailed: Authentication failed. :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2020-03-15T21:26:05.110+0000 F  -        [main] exception: connect failed
2020-03-15T21:26:05.110+0000 E  -        [main] exiting with code 1

[root@fedora /]# mongo "mongodb://rocketchat:rocketchat@rocketchat-mongodb:27017/rocketchat"
MongoDB shell version v4.2.3
connecting to: mongodb://rocketchat-mongodb:27017/rocketchat?compressors=disabled&gssapiServiceName=mongodb
2020-03-15T21:22:53.108+0000 E  QUERY    [js] Error: Authentication failed. :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2020-03-15T21:22:53.111+0000 F  -        [main] exception: connect failed
2020-03-15T21:22:53.111+0000 E  -        [main] exiting with code 1

The startup logs for mongodb
[root@e6420 rocketchat]# kubectl logs rocketchat-mongodb-primary-0

Welcome to the Bitnami mongodb container
Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb
Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues
Send us your feedback at<EMAIL_ADDRESS>
INFO  ==> ** Starting MongoDB setup **
INFO  ==> Validating settings in MONGODB_* env vars...
INFO  ==> Initializing MongoDB...
INFO  ==> Deploying MongoDB with persisted data...
INFO  ==> No injected configuration files found. Creating default config files...
INFO  ==> Writing keyfile for replica set authentication: mMZ3LBBgwO /opt/bitnami/mongodb/conf/keyfile
INFO  ==>
INFO  ==> ########################################################################
INFO  ==>  Installation parameters for MongoDB:
INFO  ==>    Persisted data and properties have been restored.
INFO  ==>    Any input specified will not take effect.
INFO  ==> (Passwords are not shown for security reasons)
INFO  ==> ########################################################################
INFO  ==>
INFO  ==> Loading custom scripts...
find: '/docker-entrypoint-initdb.d/': No such file or directory
INFO  ==> ** MongoDB setup finished! **

INFO  ==> ** Starting MongoDB **
2020-03-15T20:56:45.205+0000 I STORAGE  [main] Max cache overflow file size custom option: 0
2020-03-15T20:56:45.205+0000 I CONTROL  [main] ***** SERVER RESTARTED *****
2020-03-15T20:56:45.208+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/bitnami/mongodb/data/db 64-bit host=rocketchat-mongodb-primary-0
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] db version v4.0.12
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] git version: 5776e3cbf9e7afe86e6b29e22520ffb6766e95d4
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.0k  28 May 2019
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] modules: none
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] build environment:
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten]     distmod: debian92
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten]     distarch: x86_64
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2020-03-15T20:56:45.225+0000 I CONTROL  [initandlisten] options: { config: "/opt/bitnami/mongodb/conf/mongodb.conf", net: { bindIpAll: true, ipv6: false, port: 27017, unixDomainSocket: { enabled: true, pathPrefix: "/opt/bitnami/mongodb/tmp" } }, processManagement: { fork: false, pidFilePath: "/opt/bitnami/mongodb/tmp/mongodb.pid" }, replication: { enableMajorityReadConcern: true, replSetName: "rs0" }, security: { authorization: "enabled", keyFile: "/opt/bitnami/mongodb/conf/keyfile" }, setParameter: { enableLocalhostAuthBypass: "true" }, storage: { dbPath: "/bitnami/mongodb/data/db", directoryPerDB: false, journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, logRotate: "reopen", path: "/opt/bitnami/mongodb/logs/mongodb.log", quiet: false, verbosity: 0 } }
2020-03-15T20:56:45.225+0000 I STORAGE  [initandlisten] Detected data files in /bitnami/mongodb/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2020-03-15T20:56:45.226+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=7430M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2020-03-15T20:56:46.031+0000 I STORAGE  [initandlisten] WiredTiger message [1584305806:31965][1:0x7fd5fff7d080], txn-recover: Main recovery loop: starting at 9/18432 to 10/256
2020-03-15T20:56:46.032+0000 I STORAGE  [initandlisten] WiredTiger message [1584305806:32427][1:0x7fd5fff7d080], txn-recover: Recovering log 9 through 10
2020-03-15T20:56:46.121+0000 I STORAGE  [initandlisten] WiredTiger message [1584305806:121293][1:0x7fd5fff7d080], txn-recover: Recovering log 10 through 10
2020-03-15T20:56:46.182+0000 I STORAGE  [initandlisten] WiredTiger message [1584305806:182724][1:0x7fd5fff7d080], txn-recover: Set global recovery timestamp: 5e6e642600000001
2020-03-15T20:56:46.226+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(1584292902, 1)
2020-03-15T20:56:46.227+0000 I STORAGE  [initandlisten] Triggering the first stable checkpoint. Initial Data: Timestamp(1584292902, 1) PrevStable: Timestamp(0, 0) CurrStable: Timestamp(1584292902, 1)
2020-03-15T20:56:46.238+0000 I STORAGE  [initandlisten] Starting OplogTruncaterThread local.oplog.rs
2020-03-15T20:56:46.238+0000 I STORAGE  [initandlisten] The size storer reports that the oplog contains 8882 records totaling to 977430 bytes
2020-03-15T20:56:46.238+0000 I STORAGE  [initandlisten] Scanning the oplog to determine where to place markers for truncation
2020-03-15T20:56:46.290+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/bitnami/mongodb/data/db/diagnostic.data'
2020-03-15T20:56:46.293+0000 I REPL     [initandlisten] Rollback ID is 1
2020-03-15T20:56:46.294+0000 I REPL     [initandlisten] Recovering from stable timestamp: Timestamp(1584292902, 1) (top of oplog: { ts: Timestamp(1584292902, 1), t: 8 }, appliedThrough: { ts: Timestamp(0, 0), t: -1 }, TruncateAfter: Timestamp(0, 0))
2020-03-15T20:56:46.294+0000 I REPL     [initandlisten] Starting recovery oplog application at the stable timestamp: Timestamp(1584292902, 1)
2020-03-15T20:56:46.294+0000 I REPL     [initandlisten] No oplog entries to apply for recovery. Start point is at the top of the oplog.
2020-03-15T20:56:46.294+0000 I CONTROL  [LogicalSessionCacheRefresh] Sessions collection is not set up; waiting until next sessions refresh interval: Replication has not yet been configured
2020-03-15T20:56:46.295+0000 I REPL     [replexec-0] New replica set config in use: { _id: "rs0", version: 1, protocolVersion: 1, writeConcernMajorityJournalDefault: true, members: [ { _id: 0, host: "rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 5.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('5e6c3fcc3dc1be524e3a12f9') } }
2020-03-15T20:56:46.295+0000 I REPL     [replexec-0] This node is rocketchat-mongodb-primary-0.rocketchat-mongodb-headless.rocketchat.svc.cluster.local:27017 in the config
2020-03-15T20:56:46.295+0000 I REPL     [replexec-0] transition to STARTUP2 from STARTUP
2020-03-15T20:56:46.295+0000 I REPL     [replexec-0] Starting replication storage threads
2020-03-15T20:56:46.295+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2020-03-15T20:56:46.296+0000 I REPL     [replexec-0] transition to RECOVERING from STARTUP2
2020-03-15T20:56:46.296+0000 I REPL     [replexec-0] Starting replication fetcher thread
2020-03-15T20:56:46.296+0000 I REPL     [replexec-0] Starting replication applier thread
2020-03-15T20:56:46.296+0000 I REPL     [replexec-0] Starting replication reporter thread
2020-03-15T20:56:46.296+0000 I REPL     [rsSync-0] Starting oplog application
2020-03-15T20:56:46.296+0000 I REPL     [rsSync-0] transition to SECONDARY from RECOVERING
2020-03-15T20:56:46.296+0000 I REPL     [rsSync-0] conducting a dry run election to see if we could be elected. current term: 8
2020-03-15T20:56:46.296+0000 I REPL     [replexec-0] dry election run succeeded, running for election in term 9
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] election succeeded, assuming primary role in term 9
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] transition to PRIMARY from SECONDARY
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] Resetting sync source to empty, which was :27017
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] Entering primary catch-up mode.
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] Exited primary catch-up mode.
2020-03-15T20:56:46.299+0000 I REPL     [replexec-0] Stopping replication producer
2020-03-15T20:56:48.297+0000 I REPL     [rsSync-0] transition to primary complete; database writes are now permitted

Executing the contents of secret that the rocketchat pod is using manually results in the same error:
MongoDB shell version v4.2.3
connecting to: mongodb://rocketchat-mongodb:27017/rocketchat?compressors=disabled&gssapiServiceName=mongodb
2020-03-15T21:22:53.108+0000 E  QUERY    [js] Error: Authentication failed. :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2020-03-15T21:22:53.111+0000 F  -        [main] exception: connect failed
2020-03-15T21:22:53.111+0000 E  -        [main] exiting with code 1

Using the following charts/values result in a successful deployment:
[root@e6420 rocketchat]# cat bitnami.mongodb.values.yml
# https://github.com/bitnami/charts/blob/master/bitnami/mongodb/values.yaml

mongodbRootPassword: rocketchat
mongodbUsername: rocketchat
mongodbPassword: rocketchat
mongodbDatabase: rocketchat

replicaSet:
  enabled: true
  replicas:
    secondary: 0
    arbiter: 0

ingress:
  enabled: true

[root@e6420 rocketchat]# cat stable.rocketchat.values.yml
# https://github.com/helm/charts/blob/master/stable/rocketchat/values.yaml

image:
  tag: 3.0.3

externalMongodbUrl: "mongodb://rocketchat:rocketchat@mongodb-primary-0.mongodb-headless.rocketchat.svc.cluster.local:27017/rocketchat"
externalMongodbOplogUrl: "mongodb://root:rocketchat@mongodb-primary-0.mongodb-headless.rocketchat.svc.cluster.local:27017/local?replicaSet=rs0&authSource=admin"

mongodb:
  enabled: false

ingress:
  enabled: true

This was probably being caused by stale pv's persistent credentials between deployments.
Closing


[Core] Use MSAL for managed identity and Cloud Shell authentication

Related command
az login --identity
Description
Close #25860
Fix #13188
Changes:

Use msal.ManagedIdentity for managed identity authentication.

Use PublicClientApplication.acquire_token_interactive(prompt="none") for Cloud Shell authentication.

Limit the functionality of azure.cli.core._profile.Profile._create_credential and azure.cli.core.auth.identity.Identity to only user and service principal, because their implementation are very different from that of managed identity and Cloud Shell, which only talks to the local machine's metadata endpoint.

Rename MSI in source code to managed identity. However, the text in az account list result is still preserved until further discussion - MSI, MSIClient-{id}, MSIObject-{id}, MSIResource-{id}.

Testing Guide
az account get-access-token --debug
az vm list --debug

MSAL adoption


fix(bits): prevent BitArray.UnmarshalJSON from crashing on 0 bits in the JSON

This change fixes a bug in which BitArray.UnmarshalJSON hadn't accounted for the fact that invoking NewBitArray(<=0) returns nil and hence when dereferenced would crash with a runtime nil pointer dereference. This bug was found by my security analysis and fuzzing too.
Fixes #2658

Closing in favor of https://github.com/cometbft/cometbft/pull/2774 because I can't add a changelog (don't have permissions to push to fork)


1.0.0-rc3

this is for d77f1f5ef8c6d1711f4adef8ad5c564ec4551499 to be tagged as 1.0.0-rc3
Email vote forthcoming
4 PRs merged since v1.0.0-rc2:
(#263) Fix the generation of release PDF
(#261) Fix trivial typo in TOC of spec.md
(#259) Remove old test code
(#257) Fix link to Content Digests

LGTM

@stevvooe voted LGTM via email making this unanimous

@jdolitsky you this also be tagged as v1.0, I can prepare a blog post announcing the final release :)


Set proper host in DB_CONNECTION in .env.example

Now:
DB_CONNECTION=postgres://postgres:postgres@localhost/postgres
Expected:
DB_CONNECTION=postgres://postgres:postgres@db/postgres
The hostname for connection is the same as a service name, so this information is considered permanent.

Not sure about that. The reason for placing localhost here was to simplify cloning and running to test any changes. Yes, this value is not suitable for working with compose by default, but it’s more convenient when you want to change something and check if everything works as expected.
Personally, I do not use compose for deployment, so this will not help me, and when I want to check that the application works fine in the container, I just change the host.
But can, as an alternative, set this value in docker-compose.yml in the app service?

Yep, we could set this in docker-compose.yml

@nsidnev Hey, in the end, I found it's better to leave it as it is at least for now. Feel free to close this issue.


Add clip_grad_norm in train loop

This commit adds clip_grad_norm in train loop using nn.utils.clip_grad_norm_.

May I ask why are those check faluires?

This commit adds clip_grad_norm in train loop using nn.utils.clip_grad_norm_.

@abdallah1097, thank you for contributing to this pipeline!
I will review all enhancements you made.

All requested changes were made, my apology for the late response :)

All requested changes were made, my apology for the late response :)

Great, thank you! :)


.NET Core 2.1 is no longer supported.

Needs some update

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

ID: b01848ba-0d62-c070-ee2a-9b43e3966985
Version Independent ID: 0dadd1f3-1d08-37e1-2215-b8ea40b49c0c
Content: Migrate to ASP.NET Core 2.1
Content Source: docs/architecture/porting-existing-aspnet-apps/migrate-aspnet-core-2-1.md
Product: dotnet-architecture
GitHub Login: @ardalis
Microsoft Alias: nanil

@Rick-Anderson

Needs some update

What update does it need? This is a what's new for 2.1, so the content should still be accurate since 2.1 hasn't changed. Are you suggesting we retire the what's new docs for no-longer-supported versions, i.e., 2.0, 2.1, 2.2, and 3.0?

I would at least remove it from the TOC

It's true it's no longer supported and that will be updated in the revision coming imminently. However, it's still a reasonable incremental step for customers to take on the path to a supported version if they're coming from .NET Framework. As such, my intention is to leave the chapter but update the text and include some strong Note/Warning boxes indicating that the migration is meant to be an interim one only, as it is no longer a supported framework.

Fixed in https://github.com/dotnet/docs/pull/27512

This was merged into main - probably can be closed.


[Proposal] Implementation of SIP layer

Hi,
I would like to propose an implementation of the SIP layer in gopacket.
It's my first contribution to this project.
Feel free to make remarks about the code (format, implementation, methods, ...).
Thanks
Mathieu

I signed it!

Hi everyone !
I just made some improvments on my implementation as you suggested.
Here are the changes :

A little bit of refactor
Handling multi-line headers (as defined in RFC 3261 - 7.3.1)
Add some useful getters for common SIP Headers
Add tests

Can someone review my code ? :)
Thanks !

Sorry for the delay.
@bodji 1) I am sorry but there is remaining conflicts. Can you fix these ? 2) regarding the unit test, we would prefer to have full packet inside the test.. it will test also the layers sequence which is better. can you provide those?
@gconnell  I suggest to merge this branch after

Thanks @lhausermann, I just did some fixes :

Rebasing branch
Resolved some lint errors
Resolved some variable declaration lint errors

The Travis build is now successfull.
Tonight, I will add a full packet in the test file.

@bodji did you add the full packet test ?

Hi @lhausermann, I just pushed the new test file with complete
packets of a request/response SIP REGISTER session :)
Is it okay for you ?

But now you made it, I think we can merge.
Ok @gconnell ?


fix wrong type annotations and nonexistent types

The code shown in the document cause warnings in the IDE.

ragas.llms.LangchainLLM is no longer exists but from ragas.llms import LangchainLLM is still left in document

First time here, apology for any mistakes.

Hey @stydxm , thanks for the work.
@jjmachan shouldn't these classes work in ragas without explicitly wrapping LangchainLLMwrapper due to this line

Hey @stydxm , thanks for the work. @jjmachan shouldn't these classes work in ragas without explicitly wrapping LangchainLLMwrapper due to this line

Sorry I didn't noticed that. That PR was merged after I found this problem and start working on it yesterday :joy:.
However the problem in gcp-vertexai.ipynb still exists, please allow me minutes to edit it.

@stydxm Thanks buddy :)

@stydxm Thanks buddy :)

Done


Update rstudio-server-pro-tutorial.md

RSP is a self-hosted application.

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

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

Is there anything I can do to get this PR merged? Is anything missing?

@jeevansd Could you review the updates to this tutorial? Thanks.

#sign-off


Fix up a bad merge

Looks like someone left in a conflict marker when resolving a merge conflict

Great catch, Mike - thanks@


Journal Transactor: Copycate State Machine Implementation

#22
First pass on getting a state machine put together; compiles for now, and can muster some review.
Will need to add serialization support and tests.

Dropped the parens on CanonicalRecord.reference calls as there are no side-effects

So in the latest commit I added dummies for store and reference and did some simple testing in the sbt console.
You can try out the state machine with something like this:
import io.mediachain.transactor._
import io.atomix.catalyst.transport.Address
val dummystore = new Dummies.DummyStore
val server = Copycat.Server.build(new Address("<IP_ADDRESS>:10000"), "/tmp/copycat/log0", dummystore)
server.bootstrap().join()
val client = Copycat.Client.build()
client.connect(new Address("<IP_ADDRESS>:10000")).join()
val res = client.submit(StateMachine.JournalInsert(Types.Entity(Map()))).join()

renamed the poorly named CanonicalReference to ChainReference to make it clearer what the intent of its hierarchy is.


ESLint stops functioning after updating vscode-langservers-extracted to 4.10.0

Description
Hello,
I've encountered an issue with ESLint after updating the vscode-langservers-extracted package from version 4.8.0 to versions 4.9.0 and 4.10.0. Upon updating, ESLint functionality appears to break. Tested in different OS's and different node versions.
Before the update (at version 4.8.0), ESLint was functioning as expected within my projects, providing linting feedback and error/warning highlights in my code.
After updating to 4.9.0 and then 4.10.0, ESLint no longer provides linting feedback.
I'm unsure if this is the correct place to report this issue, but I wanted to bring it to your attention in case others are experiencing similar problems. Thank you for your help and for maintaining this important tool.

Thanks for your report. The configs in this repo are unsupported and provided only as a starting point. We depend on users (like you) to troubleshoot issues with their specific LSP setups and send improvements.
If you have a usage question, try asking it at:

https://github.com/neovim/neovim/discussions
https://vi.stackexchange.com/

If you found a bug in the core Nvim  vim.lsp module (not part of this repo), the best way to get it fixed is to report to Nvim (not nvim-lspconfig) with:

steps to reproduce it without the particular LSP server and other factors particular to your environment
(optional, but very helpful): by adding a failing test case to lsp_spec.lua, which has code to setup a fake LSP server to simulate various scenarios

@justinmk hey, I appreciate your time and apologize for mistakenly posting this issue in the incorrect repo. Will try to fix it and report it properly. Thanks!

@mguellsegarra
Do you have any clues on how to fix the setup for version 4.10?
I am looking, but I haven't found anything so far.

Im also encountering this, and vscode-langservers-extracted has no issues enabled to even report the issue. I cant really imagine stack overflow is the best place to put bug reports. maybe @hrsh7th can be summoned?
@jackpinto @mguellsegarra what behavior are you experiencing? For me, the diagnostics just dont show at all, however if i run EslintFixAll it DOES work, so i know lspconfig/eslint is reading the proper project eslintrc file etc, it just simply will not show any diagnostics. theres also no errors in LspLog, and all of that is working properly it seems

Workaround:

Uninstall eslint-lsp with Mason
npm install --global<EMAIL_ADDRESS>Add require("lspconfig").eslint.setup({}) to your config.

MasonInstall<EMAIL_ADDRESS>worked for me.

@9mm same here, it only doesn't show the diagnostics.

@jackpinto @mguellsegarra what behavior are you experiencing?

Diagnostics don't show up, sadly. I ended up putting all my share/nvim/ folder into a git repo for controlling all the Mason updates, because there's no way to lock versions. Sticking to 4.8.0 for the moment, until I have time to investigate what happened.

Just wanted to update everyone—I've opened a PR addressing the issue we've been discussing. You can follow the conversation here.

Installing like @when-harry-met-sally suggest it, it works for me


Fix potentially unaligned accesses

The manpage for CMSG_DATA specifically states:

The
pointer returned cannot be assumed to be suitably aligned
for accessing arbitrary payload data types.  Applications
should not cast it to a pointer type matching the payload,
but should instead use memcpy(3) to copy data to or from a
suitably declared object.

If this is really needed for 32 bit ints (FDs) is up for debate. But anyway I've opened this PR which
1) Returns the FDs in a Vec instead of a slice to the fds (one additional allocation and copy, but guaranteed to be safe)
2) Checks the size of the ucred creds and reads the struct using read_unaligned
3) Writes outgoing data using write_unaligned

Also fixed this inaccuracy when sending data

Removed the Vec special handling for now, so the PR now fixes the other potentially unaligned accesses and adds one size check assert

Added an FdSlice in #10, let me know if that's roughly what you had in mind

Added an FdSlice in #10, let me know if that's roughly what you had in mind

Thanks.


First X-Axis label disappears if formatted as 'ddd' when the Y-Axis is hidden

Checklist

[X] I updated the card to the latest version available
[X] I cleared the cache of my browser
[X] I verified that I'm really running the latest version in my browser console
[X] I checked if there is another issue opened with the same problem

Describe the bug
With a simple column type chart that displays daily usage data (e.g. gas usage, electricity usage, heating duration etc), if I format the X-Axis labels as 'ddd' to display the shorthand day of the week for each column (e.g. Mon, Tue, Wed) and also hide the Y-Axis, the very first X-axis label disappears along with it's tick. Changing the X-axis label format to 'dd' or 'd' to display the day of the month instead (e.g. 16, 17, 18) displays the very first X-axis label and tick as expected even with the Y-axis still hidden. Likewise, leaving the X-Axis labels format as 'ddd' and showing the Y-axis again also makes the first X-Axis label display again. This same behaviour is present if I use the 'yaxis' options (as per the code example below) or the 'apex_config' options to hide the Y-Axis.
I have also tried this with multiple different types of data collecting sensors to try and rule out questionable data including household gas and electricity usage, TRV heating duration and energy consumption from an individual device.
Version of the card
Version: 2.0.4
To Reproduce
This is the configuration I used:
- type: custom:apexcharts-card
  apex_config:
    xaxis:
      labels:
        format: ddd
  graph_span: 3d
  span:
    end: day
  yaxis:
    - show: false
  series:
    - entity: sensor.gas_import_today
      type: column
      unit: kWh
      statistics:
        type: state
        period: day
        align: start

Screenshots
X-Axis labels format set to 'ddd' with Y-Axis hidden:

X-Axis labels format set to 'dd' with Y-Axis hidden:

X-Axis labels format set to 'ddd' with Y-Axis shown:

X-Axis labels format set to 'dd' with Y-Axis shown:

Expected behavior
Regardless of X-Axis label format or Y-Axis visibility, I'd expect the first X-Axis label to display consistently
Desktop (please complete the following information):

Browser: Safari

Version: 17.0

Browser: Google Chrome

Version: 119.0.6045.199

Smartphone (please complete the following information):
N/A
Additional context
Home Assistant Core: 2023.12.3
Home Assistant Supervisor: 2023.11.6
Home Assistant Operating System: 11.2
Home Assistant Frontend: 20231208.2

Just to add, my work around so far is to show the Y-Axis using the yaxis options as per the original post, but then hide it using CSS with Lovelace Card-Mod (display: none;). I've also tweaked the padding in apex_chart grid options to get the columns displayed more centrally and uniformly for my use case.
Here is an example of the finished result:


Android speech recognition sample averaging wrong values

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): none
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  not related to this question
TensorFlow installed from (source or binary): not related to this question
TensorFlow version (use command below): not related to this question
Python version: not related to this question
Bazel version (if compiling from source): not related to this question
GCC/Compiler version (if compiling from source): not related to this question
CUDA/cuDNN version: not related to this question
GPU model and memory: not related to this question
Exact command to reproduce: not related to this question

Describe the problem &  Source code / logs
Please refer to this question and comments on stackoverflow: https://stackoverflow.com/questions/49269555/logging-and-deque-operation-problems-in-tensorflow-android-speech-recognition-sa
In brief, previousResults.addLast should be revised. Otherwise, it will take wrong values to average.

I'm sorry, but we can't answer stackoverflow q's here. If you there's a bug, please file a new issue filling out the template.


Uncomment and fix detect_connection_closed test

Pass locally but not sure if travis is configured correctly
Cheers

bors r+


Bookmarklet support

Is it possible to create bookmarklet to save bookmark (for example Instapaper has  this feature) without adding it manually in Shiori?

Duplicate of #84


docs: fix typos

What:
Just some typos
Why:

How:

Checklist:

[x] Documentation
[ ] Tests
[ ] Ready to be merged

@all-contributors please add @sitek94 for docs


Support custom ids

The default ids are UUIDS. These are too long to use inside of a URL. It would be nice if we could specify custom ids.
For example, a nanoid:

https://github.com/Jakeii/nanoid-postgres/blob/main/nanoid.sql
https://github.com/ai/nanoid

You can create your own IDs with ease:
This is how the standard ID property is defined:
    required single property id -> uuid {
        default := (select
            uuid_generate_v1mc()
        );
        readonly := true;
    };

You cannot redefine it, but nothing prevents you from creating your own on a side:
    required single property my_id -> uuid {
        default := (select
            my_random_func()
        );
        readonly := true;
    };

You can also emulate auto-incrementing IDs with sequences https://www.edgedb.com/docs/stdlib/sequence

You can even re-implement https://github.com/Jakeii/nanoid-postgres/blob/main/nanoid.sql in edgeql (just replace & with %).

WITH
  X := {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20},
  alphabet := 'ModuleSymbhasOwnPr-0123456789ABCDEFGHNRVfgctiUvz_KqYTJkLxpZXIjQW',
  L := (
    for i in X union (alphabet[<int64>math::floor(random()*64)])
  )
select array_join(array_agg(L), "");

computes a nanoid, I think. Really wants ranges


Do you support Flac files ?

Your tool is awesome.
But unfortunately nothing happens for Flac files :
nformation: Reading tag for "99983284" from "/Users/XXXXX/XXXX/XXX/XX XX/73 - Bastille - Revolution.flac"
Information: Found 0 cue points
Information: Removing existing generated cue points for "99983284"
Information: Can create 8 cue points
Information: Updating contentCue "043db43a-054c-4a92-9c6a-35ec40af1d4f"
Information: Finished cue points creation with errors
I see cue points in MIK

I've added support in 1.0.32.

Thank you very much.
I will test it.
De : Michael Ganss @.>
Date : vendredi, 2 septembre 2022 à 12:07
À : mganss/CueGen @.>
Cc : Francois Collienne @.>, Author @.>
Objet : Re: [mganss/CueGen] Do you support Flac files ? (Issue #11)
I've added support in 1.0.32.
—
Reply to this email directly, view it on GitHubhttps://github.com/mganss/CueGen/issues/11#issuecomment-1235315183, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWREDEBE7JWZUFRMMOSDQRTV4HGUVANCNFSM6AAAAAAQCB2XRQ.
You are receiving this because you authored the thread.Message ID: @.***>


[Bullet] RigidBody.body_entered not always emitted for KinematicBody with infinite_inertia=false

Godot version
3.3.4.stable.custom_build.faf3f883d
System information
Linux 5.14.8-arch1-1, GLES3, Nvidia 1080
Issue description
When a KinematicBody uses move_and_slide with infinite_inertia=true, RigidBody objects will emit body_entered inconsistenly when colliding with them. It will emit sometimes, but misses a lot of collisions (usually less direct ones, where the KinematicBody tends to slide out of the way).
Steps to reproduce

Open the example project
Run it, see KinematicBody printed, indicating that the RigidBody detected a collision
Change infinite_inertia to false in KinematicBody.gd
Run again, see KinematicBody is not printed
Adjust the position of the RigidBody so it has a more direct collision with the KinematicBody
Run again, see KinematicBody is printed again

Minimal reproduction project
example.zip

@rcorre Does this occur with GodotPhysics too?

@Calinou no, GodotPhysics emits body_entered, and the KinematicBody also "resists" the RigidBody more.
https://user-images.githubusercontent.com/2496231/139583683-4e8ecb64-c7d5-4400-a90e-eca31091de92.mp4

Oops, I forgot I reported this and duped it in #57407. I'll close this one, I think the example in the other is better.

Also, in this one I said it didn't happen with Godot Physics, but in #57407 it did, which I do remember testing. Either I was wrong in this one or something changed between 3.3 and 3.4.


institution_id registration of CLMcom-KUL

institution_id
CLMcom-KUL
institution
Climate Limited-area Modelling Community (CLMcom) partner: KU Leuven, Leuven, Belgium

Thank you!
I updated the institution to include the CLM community as the rest of the partners. Please, consider expanding the KU acronym in the institution

Thanks! We prefer to keep KU Leuven as such, as it is the official name (they abandoned the 'Katholieke Universiteit' a couple of years ago.

/register
Perfect. Let's go for it, then


[DEV-34314] Fix parallel test runner pickle errors

Issue: https://code.djangoproject.com/ticket/29023#comment:5
Cherry-pick: https://github.com/cjerdonek/django/commit/0040040ca4fec08a9980a24f08bcad900e2b0f22
Removed from None on the exception raising for Python 2 compatibility. Tested in both Python 2.7 and 3.6 in parallel mode.

Plan is to merge into the current stable/rover-1.11.11 and delete this branch


Add support for watch-only addresses

I would like to watch address balances via RPC, that don't belong to the wallet, in order to not depend on 3-party-explorers. getreceivedbyaddress doesn't work with addresses out of your own wallet. That's why later importaddress has been added to Bitcoin, that don't need private keys and are ignored for balance calculating.
https://bitcoin.org/en/developer-reference#importaddress
Pull Request: https://github.com/bitcoin/bitcoin/pull/4045
I would like to have this feature also for Deeponion to use it for an independent light explorer/monitor application.

Thanks for the suggestion, we are looking into it

This will be done in the rebased code.