text:
GraphQL (WIP)

Pushing this just to show the progress so far. Not ready to merge yet.
Related issues: #32, #59
Notes:

Pothos is good! Some minor issues with docs, but nothing critical; Prisma plugin and Relay plugin work fine, which is great.
urql with SSR is... ugh. Dealing with it right now (haven't pushed the related commit yet). I had to read through the next-urql source code to figure it out.

next-urql uses the deprecated getInitialProps from older Next.js as a default mechanism but has the solution for more modern getStaticProps or getServerSideProps
we'll have to list all requests for GraphQL data in getServerSideProps manually (e.g., deeply nested components which need some portion of data won't magically SSR with all their useQuery data by themselves)

this is not urql's fault, since the alternative is to render everything on the server twice, which is slow

I don't like the amount of code which will be necessary for every getServerSideProps function (urqlState: ssrCache.extractData(), initUrqlClient, etc.); I'll try to come up with some helper functions to make the DX smoother

I'm replacing searchAccordingToQueryData with a GraphQL query, to abstract away all search logic from the frontend code. This requires substantial refactorings, hope to push the working implementation in a day or two.

80% complete, 80% to go.

SSR is working
frontpage uses graphql, dashboards are too

Needs fixing:

[ ] timestamp field (I used custom scalar for the timestamp field on the backend and need to map it properly on the frontend now, probably with urql-custom-scalars-exchange, but it requires schema awareness which I haven't dealt with yet)
[ ] creating dashboards is not implemented yet
[ ] there are probably a few bugs, I should check every page by hand
[ ] docs for writing new endpoints and description fields in graphql schema

Also:

I don't like my current implementation for visualization and qualityIndicators, not sure if I'll improve it before merging or deal with it later
I feel like CommonDisplay can/should be simplified, though it's not much worse now than it was before

urql-custom-scalars-exchange

It works, but it's incompatible with SSR, since Next.js can't serialize Date objects.
There's a workaround with superjson, but I don't think that an extra dependency is worth it.
I left urql-custom-scalars-exchange config & schema introspection code for the future since I already wrote it when I realized this, and schema introspection might be needed for better urql caching anyways.
For now I'm just serializing timestamp as an int (which is better/safer than a date string) and decode it with new Date(ts * 1000) on the frontend.

creating dashboards

Done.

Pushed the new changes, https://metaforecast-git-graphql-quantified-uncertainty.vercel.app/ is mostly functional now. (SSR on the frontpage is currently broken, will investigate).

Ok, I think this is done!
Docs are in docs/graphql.md, and I added a description for the most of graphql fields (sometimes copying from specification.json, which can be deprecated soon, since GraphQL is better for this kind of documentation).

Notes on SSR.
I still don't like how SSR is implemented, especially making a choice of "do I pass the page data from getServerSideProps in urqlState cache or in page props".
Passing in props means that the page is not really dynamic (I consider initialBlah props with useState to be an anti-pattern which should be avoided if possible). Which is mostly fine, except for the frontpage, which is dynamic. It also means that we won't be able to benefit from urql's caching abilities in the future, and caching is a big selling point for graphql; though it's more useful for SPA-like rich UI features, which we don't have yet.
On the other hand, passing in urqlState means that we have to do the query in getServerSideProps and then do the same query with the useQuery on client. Which means that if the document or variables for one of these queries ever changes on the future and we forget to change the other call then SSR would break (i.e. degrade to client-side query, the page won't break entirely, but it would break silently and we might not notice it for a while).
Issues with both of these approaches are non-critical, and it's not hard to change the code from using one approach to another. But I don't like having this choice, it feels like extra cognitive load for no clear benefit.
I don't have any good ideas for how to deal with it yet, and maybe I'll just get adjusted to it over time.

Notes on types.

I got rid of FrontendQuestion since we can just use types from graphql-code-generator based on fragments in our queries
OTOH, there are now two Question types on the backend: first in src/backend/platforms/index.ts and the second one from Prisma; I'd like to keep just the second one eventually, but we'll need to refactor the DB to make it strictly typed (split qualityIndicators and extra fields into postgres columns)

for now, dealing with JsonValue for qualityIndicators and extra is annoying, since Prisma assumes that a JSON field from the DB can be any JSON-compatible value, e.g. a scalar or an array

I got bitten a few times by "strict": true not being enabled in our tsconfig.json, especially by nullable types; we're down to 349 errors when strict is enabled (from 523 on the initial typescript PR)

Any idea why the netlify build preview is failing? The vercel one is working: https://metaforecast-lfn840cvn-quantified-uncertainty.vercel.app

Ok, I think this is done!

Should I merge, or any last checks?

Your notes on SSR (server-side rendering, I'm guessing) went a bit over my head. Any actionables, besides writing this down somewhere so that we remember this when we come back to it in a few months?

Any idea why the netlify build preview is failing?

Probably because the build now requires prisma generate, which is run in npm run build (see scripts in package.json) but netlify runs next build instead.
Anyway, I disabled netlify builds yesterday since we don't use it anymore.

Your notes on SSR (server-side rendering, I'm guessing) went a bit over my head.

That's fine. It's kinda hard to explain clearly without repeating all graphql/urql docs, and I think I'm not doing anything non-standard here.

Any actionables, besides writing this down somewhere so that we remember this when we come back to it in a few months?

No, my notes above are "writing this down somewhere", I should've been more clear about that. No actions needed. (I slightly dislike putting stuff like this in docs/ in the repo, since code usually changes faster than documentation and documentation can get out of sync with reality or with our understanding of best practices.)

authors: NunoSempere berekuk

repo: quantified-uncertainty/metaforecast


text:
BLD: Need correct param for setup to specify extra reqs

Otherwise, $ pip install -e .[bayesian] warns me:
"pyfolio 0.5.1+37.gb684c3a does not provide the extra 'bayesian'"
Also, Theano will get installed by pymc3 extra dependency

@richafrank looks like we fixed "pyfolio 0.5.1+37.gb684c3a does not provide the extra 'bayesian'" at the same time
https://github.com/quantopian/pyfolio/pull/332

Oh nice!  Should we close or merge this?

This pr also removes theano (mine doesn't) we can merge this and I'll update my branch.

source: gharchive/pull-request

authors: ahgnaw richafrank

repo: quantopian/pyfolio

license_type: permissive

license_source: bigquery


text:
Cirq routing is hanging again for some circuits

Hi guys,
I have a concern similar to the one from issue #2282. The problem was fixed later and when running from 6d81ddbb commit everything works just fine. However, there were further changes in apply_next_swaps(...) function, in particular a new parameter max_num_empty_steps was introduced.
In the last version of code when running routing via route_circuit_greedily(...) and with parameters max_search_radius=1, max_num_empty_steps=1 everything also works well. However, when choosing different values for these two parameters (e.g. max_search_radius=2, max_num_empty_steps=1) routing hangs on some circuit instances.
Should there be any constraint on how to choose values for the parameters max_search_radius and max_num_empty_steps? Or maybe there is some bug in the routing code?
Thanks!

@bryano I think you added this feature.  Thoughts?

@wcourtney Could you provide some circuits (or code to generate them) on which the router hangs?

This is the code snippet.
It works fine if number of qubits involved in the random circuit <16 (number of qubits in the hardware is 16) or for small value of n_moments.
import networkx as nx
import cirq
from cirq import LineQubit
from cirq.contrib.routing.greedy import route_circuit_greedily

edges = [
        [0, 1],
        [0, 7],
        [0, 15],
        [1, 2],
        [7, 6],
        [7, 8],
        [15, 8],
        [15, 14],
        [2, 3],
        [3, 4],
        [4, 5],
        [5, 6],
        [8, 9],
        [9, 10],
        [10, 11],
        [11, 12],
        [12, 13],
        [13, 14],
        ]

def create_cirq_hardware(edges):
    graph = nx.Graph()
    for edge in edges:
        graph.add_edges_from([(LineQubit(edge[0]), LineQubit(edge[1]))])
    return graph

cirq_hardware = create_cirq_hardware(edges)
circuit = cirq.testing.random_circuit(qubits=16, n_moments=200,
                                      op_density=.5, random_state=1)

swap_network = route_circuit_greedily(circuit,
                                      cirq_hardware,
                                      max_search_radius=2,
                                      max_num_empty_steps=1,
                                      random_state=1)

This is definitely odd:
In colab works up to 8 qubits (~ 1 minute at that point) and then it hangs (it's been running for 12+ minutes now).

This is definitely odd:
In colab works up to 8 qubits (~ 1 minute at that point) and then it hangs (it's been running for 12+ minutes now).

I think I managed to fix the issue by modifying function apply_next_swaps(...) in greedy router. In fact these changes were implemented earlier to fix such a problem and then for some reason were reverted.
See this screenshot:

After modifying apply_next_swaps(...) in Cirq. 0.8.2 router works fine! Should I create a pool request with the changes?
This is the modified version of apply_next_swaps(...) function:
`    def apply_next_swaps(self, require_frontier_adjacency: bool = False):
"""Applies a few SWAPs to get the mapping closer to one in which the
next logical gates can be applied.
    See route_circuit_greedily for more details.
    """

    time_slices = get_time_slices(self.remaining_dag)

    if require_frontier_adjacency:
        frontier_edges = sorted(time_slices[0].edges)
        self.bring_farthest_pair_together(frontier_edges)
        return

    for k in range(1, self.max_search_radius + 1):
        candidate_swap_sets = list(self.get_edge_sets(k))
        for time_slice in time_slices:
            edges = sorted(time_slice.edges)
            distance_vectors = list(
                self.get_distance_vector(edges, swap_set)
                for swap_set in candidate_swap_sets)
            dominated_indices = _get_dominated_indices(distance_vectors)
            candidate_swap_sets = [
                S for i, S in enumerate(candidate_swap_sets)
                if i not in dominated_indices
            ]
            if len(candidate_swap_sets) == 1:
                self.apply_swap(*candidate_swap_sets[0])
                if list(
                        self.remaining_dag.findall_nodes_until_blocked(
                            self.acts_on_nonadjacent_qubits)):
                    return
                else:
                    break

    self.apply_next_swaps(True)`

Submitted PR #3360

Was fixed in #3360.

source: gharchive/issue

authors: balopat bryano dabacon yourball

repo: quantumlib/Cirq


text:
Can you please create even a ruby version of this framework so that the innovative idea and the project will not be available to just one community of interest ?

Can such a project even be created/implemented in Ruby so that the innovative idea and project will not just be limited to just one community of interest ?
Please try to implement even a ruby version as there is also a big community of rubyists who don't wanna be devoid of it .
P0 - this should land no later than a month
P1 - I need this no later than the next release (end of quarter)
P2 - we should do it in the next couple of quarters
P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion

Hey @Ash-the-practical-programmer,
Thanks for this question.
After a quick search of quantum programming frameworks in Ruby, i haven't been able to find anything of note. This might be because Ruby isn't big into scientific computing like Python is.  Are there easy ways to interoperate with Python code in Ruby?

Hey again @Ash-the-practical-programmer. We might be able to do this by having quantum_ruby export QASM and use Cirq's QASM importer to consume the generated QASM.  Maybe there is a way to transpile cirq-web to Ruby. Since i don't know Ruby, I've assigned this issue to you.

@Ash-the-practical-programmer Please re-open this issue once you confirm that you are looking into this.

authors: Ash-the-practical-programmer vtomole


text:
Remove AbstractEngineProcessorShim

We can use cg.AbstractProcessor and its descendants instead.
This is blocked by adding default arguments to the marked-Optional-but-no-actually arguments to AbstractProcessor.get_device and .get_sampler
cc @dstrain115 @MichaelBroughton

I don't think we can use SimulatedLocalProcessor directly because it isn't serializable -- either philosophically or in practice.

related: https://github.com/quantumlib/Cirq/issues/2820

@MichaelBroughton @dstrain115 this should be ready for your review, PTAL

Also, did #4850 solve your optional gate set issues?  Or is there further work needed?

@verult @dstrain115 ptal. With #4909 merged in, the diff should be fixed (smaller)


text:
Add a [sqrt] square root scale option to sinter plot

Starting an axis name with '[sqrt]' will now use a square root scale
Heavily refactor the plot method to clarify how plots are being scaled

Fixes https://github.com/quantumlib/Stim/issues/506

Note to self: add unit tests testing the sqrt data path, and leave this PR for a bit so I have the opportunity to catch plots looking funny in my dev environment since it's impossible to properly unit test this stuff.

repo: quantumlib/Stim


text:
scheduler fires on quarkus startup execution of job

I configured a cron expressoin for my job in application.properties like:
quarkus.jberet.job."jobname".cron=0 0 19 ? * *
Expected:
This cron should start the job every day at 7pm.
Current situation:
Job is started after Quarkus is startet AND every day at 7pm.
Why is the job started when quarkus is launched?

cool. thanks could you also apply it to the 1 version - would be really nice - i am usong quarkus 2.16

authors: michaelsonnleitner wrssmi

repo: quarkiverse/quarkus-jberet

license_source: github-api


text:
23w42a port, TNT template

This ports Templates to 23w42a - mostly involving changes to argument order, but also pressure plate activation rules and button durations are determined by BlockSetType now(?) - as well as adding the TNT template, taking advantage of the fact that TNT can now visually display as any blockstate.
Making a TNT template emit redstone by any means, whether through the properties of the mimicked blockstate or through adding redstone dust, will cause it to ignite as soon as either it or any of its neighbors receive a block update. Why would you do this? The answer remains to be seen.
This is extremely low-effort and purely for the sake of shitposting, but then again that's not exactly out of place in this mod lmao. Thank you for resuscitating it and making it better than I could have ever imagined - consider this me returning the favor.

forgot to attach this whoops

license: MIT


text:
Using a StringTemplate in .where Predicate replaces .like String with "?1"

Hi,
I've been using QueryDSL for a little while and it has made my development so much easier!
I have run into a problem, though.
I'm writing a query to search for "Customers" by postcode. To do this I'm formatting a search string, removing any whitespace, and doing the same to the column with Expressions.stringTemplate("replace({0},' ','')", qCustomer.postCode). I'm then using .likeIgnoresCase to match to my search term, postco for example.
The issue I'm having is that, when the I actually run the query it resolves the query string to select customer from Customer customer where lower(replace(customer.postCode,' ','')) like ?1. You can see that where postco was has been replaced with ?1.
My code is as follows:
    public Page<Customer> findByCustomerPostcode(String postcode, Pageable pageable) {

        // Reformat the Postcode to remove whitespace and normalise case
        String formattedPostcode = postcode.replace(" ", "");
        formattedPostcode = formattedPostcode.toLowerCase();

        // Create where with removal spaces from the column values
        BooleanExpression whereClause = Expressions.stringTemplate("REPLACE({0},' ','')", qCustomer.postCode).likeIgnoreCase(formattedPostcode);

        // Create the query factory for the Customer
        JPAQueryFactory queryFactory = new JPAQueryFactory(getEntityManager());
        JPAQuery<Customer> customerJPAQuery = queryFactory.selectFrom(qCustomer);

        // Run the query to get the whole count, and the actual paginated list
        Long totalResults = customerJPAQuery.where(whereClause).fetchCount();
        List<Customer> resultList = customerJPAQuery.where(whereClause).limit(pageable.getPageSize()).offset(pageable.getOffset()).fetch();

        // Return the page
        return new PageImpl<>(resultList, pageable, totalResults);
    }

The issue presents itself when customerJPAQuery.where(whereClause).fetchCount(); is called. At this point whereClause is lower(replace(customer.postCode,' ','')) like postco, but customerJPAQuery is select customer from Customer customer where lower(replace(customer.postCode,' ','')) like ?1.
Interestingly, both the queryMixin and QueryBase.queryMixin from the customerJPAQuery contain the correct where clause in their metadata.
Does anyone have any pointers as to why this isn't working?
Thanks!

Annnnnd I'm an idiot. Absolutely nothing wrong with the library - My test data was wrong!
Thank you for your time :)

Sorry for the late reply.
Good to hear that it was fixed!

repo: querydsl/querydsl


text:
Support for Hibernate 6

Hibernate has released a CR for their 6th generation. While trying to upgrade (or at least support it in) Spring Data JPA, our tests fail with a NullPointerException coming from JPAUtil.setConstants(…):
[ERROR] Failures:
[ERROR]   QuerydslJpaPredicateExecutorUnitTests.findByFluentPredicateOneValue:369
Expecting actual throwable to be an instance of:
  org.springframework.dao.IncorrectResultSizeDataAccessException
but was:
  java.lang.NullPointerException: Cannot invoke "org.hibernate.query.BindableType.getBindableJavaType()" because "this.anticipatedType" is null
	at org.hibernate.query.spi.AbstractQueryParameter.getParameterType(AbstractQueryParameter.java:61)
	at com.querydsl.jpa.impl.JPAUtil.setConstants(JPAUtil.java:53)
	at com.querydsl.jpa.impl.AbstractJPAQuery.createQuery(AbstractJPAQuery.java:133)
	...(79 remaining lines not displayed - this can be changed with Assertions.setMaxStackTraceElementsDisplayed)
[ERROR]   QuerydslJpaPredicateExecutorUnitTests.findOneWithPredicateThrowsExceptionForNonUniqueResults:329
Expecting actual throwable to be an instance of:
  org.springframework.dao.IncorrectResultSizeDataAccessException
but was:
  java.lang.NullPointerException: Cannot invoke "org.hibernate.query.BindableType.getBindableJavaType()" because "this.anticipatedType" is null
	at org.hibernate.query.spi.AbstractQueryParameter.getParameterType(AbstractQueryParameter.java:61)
	at com.querydsl.jpa.impl.JPAUtil.setConstants(JPAUtil.java:53)
	at com.querydsl.jpa.impl.AbstractJPAQuery.createQuery(AbstractJPAQuery.java:133)
	...(76 remaining lines not displayed - this can be changed with Assertions.setMaxStackTraceElementsDisplayed)

Actually, it looks like the NPE is caused by Hibernate in the first place.

There's a reproducer to be found here (plain Querydsl + Hibernate 6). It looks like the issue only appears when certain types of predicates are involved. contains triggers the issue, eq does not. I still think it's a bug in Hibernate 6 as it works just fine on 5.6.5. That said, I think you need to bring this up with Hibernate as I cannot argue on behalf of Querydsl.

It looks like the issue has been resolved in Hibernate 6.0 CR2.

Just to note, The final version of Hibernate 6.0 is released.
https://in.relation.to/2022/03/31/orm-60-final/

authors: MSDehghan odrotbohm


text:
Support for .Net Core 3 Json library

.Net Core 3 comes with its own set of classes to serialise and deserialise JSON, located in the System.Text.Json and System.Text.Json.Serialization.
Previous versions used to rely on Newtonsoft.Json and Newtonsoft.Json.Converters instead.
This also means some attribute names need to be adapted:
        [JsonProperty("id")]
        public Guid Id { get; set; }

becomes
        [JsonPropertyName("id")]
        public Guid Id { get; set; }

Serialisation of enums to string can be done this way
    [JsonConverter(typeof(JsonStringEnumConverter))]
    public enum Color { Red, Green, Blue };

but cannot be done by involving JsonReader and JsonWriter like it was in previous versions.
It would be nice to be able to choose between Newtonsoft.Json and System.Text.Json when using quicktype to create classes from Json.
Here is a good starting place to understand the changes I am refering to:
https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#fast-built-in-json-support
Cheers!

Love this idea! We would be happy to guide someone in contributing this as an option to the existing C# language support.

any news about supporting System.Text.Json?

@dvdsgl ... I (potentially) volunteer as tribute!

Can you share any contribution guidelines/tips/insight? I'm in that brief window of time where I'm trying to decide if it would be easier to just change the generated code, or contribute this change to pay it forward :P

@joelmartinez do it! I'll help you if you get stuck. Should not be too bad.

Can't wait for this!! 👍

@joelmartinez Do you have any progress on this issue?

@doggy8088

Unfortunately, my "brief window of time" ended up going in another direction ... I never got quite deep enough into implementation territory here. So the task is still open for anyone else that wants a crack.

Any news?

I got quicktype running with the code from the PR, seems to work fine as is for at least my needs. Is there any progress as to getting this included?

@bzuidgeest You might consider use my version of quicktype.
Source: https://github.com/doggy8088/quicktype/tree/CSharp-SystemTextJson
npm: @willh/quicktype

It because JsonStringEnumConverter doesn't fit my need on certain circumstance.

It because JsonStringEnumConverter doesn't fit my need on certain circumstance.

That much was obvious. But not very helpfull. I do know it has an "issue" arround nullable enums, but personally I find enums should not be nullable, if you don't know the value a "unknown" option should be added to the enum. But opinions like that are personal and I cannot expect everyone to share them. Was this your "circumstance"?

Would be amazing to have this option built in to replace Json.NET.

@doggy8088 That seems like an excellent reason for doing it the way you did. The use case is rather specifc however (I think) and I don't know if it would hold up in a general use tool. What if the next person would use a different seperator and a different way of correcting it in the conversion. For example what if the replaced the dot in the enum by removing it al together? You would have to define a lot of use cases.
But thanks for explaining, that is very usefull.

@dylanvdmerwe Replace is a bad option. A lot of people have invested in the code as-is and rely on it. Also JSON.net is far from dead. It might fade eventually, but for now its still heavily used and has unique features that are not in System.Text.Json and might never be available there. Personally I am a proponent of what @dvdsgl suggested. The Kotlin generator has an option to choose the framework to be used. We should have that for C# to.
I looked into the code files and we could copy the way kotlin does it and then cobine @doggy8088 repo his generator code with the existing generator code. Some name clashes would need to be fixed, but it should not be to difficult. Basically two generators and a choice between the two.

@bzuidgeest agreed my apologies I meant that having the option to select which generator to use would be incredible.

I took the code from the repo of @doggy8088 and merged it with the current version of quicktype using the kotlin generator as an example  of how to implement selecting between frameworks. Just like @dvdsgl sugested
It seems to work but I need to mention some caveats.

I am NO typescript developer. But code is code so I think I did a reasonable job putting everything in place.
The csharp testsuite still runs OK, so at least I did not break the existing stuff. But I don't know how to add a test project that can test the SystemTextJson framework to the project. Someone will have to point out what needs to happen. Could be the test docker container provided needs to be supplied with a newer .NET version, new test project etc...

code is here:
https://github.com/bzuidgeest/quicktype/tree/SystemTextJson
I could make a pull request, but I doubt that would be accepted without tests. Maybe I make one for show.

So I committed number of changes and as far as I can determine most tests run fine. Even some that are excluded with newtonsoft lib because of framework issues. Seems reasonable to me. Lets hope someone actually want to take a look at the PR

Why is this not a thing yet? .net 6 does not  even have newtonsoft

Why is this not a thing yet? .net 6 does not even have newtonsoft

That is nonsense Newtonsoft Json.net library always has been a sperate lib and is very much supported on .NET6. Just with the nuget package. The fact that Microsoft included by default in some templates has no bearing on that.
With the latest .net you are free to choose between the system.text.json and newtonsoft libs.
That said, this project seems to be "on hold" as in the discussions you can read the maintainers do not have the time to maintain it.

Fixed in #1997

repo: quicktype/quicktype


text:
Dart

Already absent in the dart @required, please will change to required

Duplicate of #1673

Duplicate of #1755

authors: NatoBoram bayishbro


text:
OTLP HTTP logs endpoint with compression seems broken

Describe the bug
OTLP HTTP logs endpoint with compression (gzip/zstd) gives an HTTP error 400. Unfortunately, Alloy doesn't display error messages like Quickwit does. However, I encountered the same behavior with a Python script, and I was able to see the error message. If I disable compression it works.
alloy logs
Jul 15 18:53:22 dhcp1 alloy[72606]: ts=2024-07-15T16:53:22.63928085Z level=error msg="Exporting failed. Dropping data." component_path=/ component_id=otelcol.exporter.otlphttp.log error="not retryable error: Permanent error: rpc error: code = InvalidArgument desc = error exporting items, request to https://demo.quickwit.fr/api/v1/otlp/v1/logs responded with HTTP Status Code 400" dropped_items=1
Jul 15 18:53:22 dhcp1 alloy[72606]: ts=2024-07-15T16:53:22.639310127Z level=debug msg="Preparing to make HTTP request" component_path=/ component_id=otelcol.exporter.otlphttp.log url=https://demo.quickwit.fr/api/v1/otlp/v1/logs

python logs
INFO:root:Starting up
INFO:root:TEST LOG
ERROR:opentelemetry.exporter.otlp.proto.http._log_exporter:Failed to export logs batch code: 400, reason: {
  "message": "invalid OTLP request: failed to decode Protobuf message: invalid wire type value: 7"
}

Steps to reproduce (if applicable)
Steps to reproduce the behavior:

Use a Python script (same issue, works only without compression).
Start Grafana Alloy with the OTLP HTTP endpoint and set compression (gzip/zstd, it doesn't matter which one).

Expected behavior
A clear and concise description of what you expected to happen.
Configuration:

Using python script
Install python requirement pip install opentelemetry-exporter-otlp-proto-http
and launch the below script with REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt OTEL_EXPORTER_OTLP_LOGS_COMPRESSION=gzip python script.py.
OTEL_EXPORTER_OTLP_LOGS_COMPRESSION can be set to none

Python script
# Support for instrumentation
import logging

# Instrumentation Libraries
from opentelemetry.sdk.resources import Resource
from opentelemetry.semconv.resource import ResourceAttributes

# Exporters
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.exporter.otlp.proto.http.metric_exporter import OTLPMetricExporter
from opentelemetry.exporter.otlp.proto.http._log_exporter import OTLPLogExporter

# Logs Import
from opentelemetry.sdk._logs import LoggerProvider, LoggingHandler
from opentelemetry.sdk._logs.export import BatchLogRecordProcessor
from opentelemetry._logs import set_logger_provider

def initialize_otel(endpoint: str):
    logging.debug("Initialize OTEL")

    # Global resources
    resource = Resource.create(
        attributes={ResourceAttributes.SERVICE_NAME: 'debug_compression'})

    # Logging

    logger_provider = LoggerProvider(resource=resource)
    set_logger_provider(logger_provider)
    logger_provider.add_log_record_processor(
        BatchLogRecordProcessor(OTLPLogExporter(
            endpoint=endpoint)
        )
    )
    handler = LoggingHandler(level=logging.NOTSET, logger_provider=logger_provider)

    # Use the OTLP logging handler to send logs.
    logging.getLogger().addHandler(handler)

    # Return the created providers
    return logger_provider

# Set up our own logging
logging.basicConfig(level="INFO")
logging.info("Starting up")

# Set up the OTEL agent to talk to the collector
LOG_PROVIDER = initialize_otel("https://demo.quickwit.fr/api/v1/otlp/v1/logs")

logging.info('TEST LOG')

Using Grafana alloy, disabling compression by setting compression = "none" works.

Alloy config
otelcol.exporter.otlphttp "log" {
        client {
                endpoint = "https://demo.quickwit.fr"
                compression = "gzip"
                tls {
                   insecure_skip_verify = true
                }
        }
        logs_endpoint = "https://demo.quickwit.fr/api/v1/otlp/v1/logs"
}

loki.source.journal "read" {
        forward_to = [
                otelcol.receiver.loki.converter.receiver,
        ]
        labels = {
                "job" = "journal",
        }
}

otelcol.receiver.loki "converter" {
        output {
                logs = [otelcol.exporter.otlphttp.log.input]
        }
}

Output of quickwit --version : Quickwit 0.8.1 (x86_64-unknown-linux-gnu 2024-03-29T14:09:41Z e6c5396)
The index_config.yaml : I use the default index configuration for OTLP

Quickwit config
[
  {
    "version": "0.8",
    "index_uid": "otel-logs-v0_7:01J1QRZ6BBB0N0KTKGQ1N6BY0X",
    "index_config": {
      "version": "0.8",
      "index_id": "otel-logs-v0_7",
      "index_uri": "s3://quickwit/indexes/otel-logs-v0_7",
      "doc_mapping": {
        "field_mappings": [
          {
            "name": "timestamp_nanos",
            "type": "datetime",
            "fast": true,
            "fast_precision": "milliseconds",
            "indexed": false,
            "input_formats": [
              "unix_timestamp"
            ],
            "output_format": "unix_timestamp_nanos",
            "stored": true
          },
          {
            "name": "observed_timestamp_nanos",
            "type": "datetime",
            "fast": false,
            "fast_precision": "seconds",
            "indexed": true,
            "input_formats": [
              "unix_timestamp"
            ],
            "output_format": "unix_timestamp_nanos",
            "stored": true
          },
          {
            "name": "service_name",
            "type": "text",
            "fast": {
              "normalizer": "raw"
            },
            "fieldnorms": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "severity_text",
            "type": "text",
            "fast": {
              "normalizer": "raw"
            },
            "fieldnorms": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "severity_number",
            "type": "u64",
            "coerce": true,
            "fast": true,
            "indexed": true,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "body",
            "type": "json",
            "expand_dots": true,
            "fast": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "default"
          },
          {
            "name": "attributes",
            "type": "json",
            "expand_dots": true,
            "fast": {
              "normalizer": "raw"
            },
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "trace_id",
            "type": "bytes",
            "fast": false,
            "indexed": true,
            "input_format": "hex",
            "output_format": "hex",
            "stored": true
          },
          {
            "name": "span_id",
            "type": "bytes",
            "fast": false,
            "indexed": true,
            "input_format": "hex",
            "output_format": "hex",
            "stored": true
          },
          {
            "name": "trace_flags",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "resource_attributes",
            "type": "json",
            "expand_dots": true,
            "fast": {
              "normalizer": "raw"
            },
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "resource_dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "scope_name",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_version",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_attributes",
            "type": "json",
            "expand_dots": true,
            "fast": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          }
        ],
        "tag_fields": [],
        "store_source": false,
        "index_field_presence": false,
        "timestamp_field": "timestamp_nanos",
        "mode": "strict",
        "max_num_partitions": 200,
        "tokenizers": []
      },
      "indexing_settings": {
        "commit_timeout_secs": 5,
        "docstore_compression_level": 8,
        "docstore_blocksize": 1000000,
        "split_num_docs_target": 10000000,
        "merge_policy": {
          "type": "stable_log",
          "min_level_num_docs": 100000,
          "merge_factor": 10,
          "max_merge_factor": 12,
          "maturation_period": "2days"
        },
        "resources": {
          "heap_size": "2.0 GB"
        }
      },
      "search_settings": {
        "default_search_fields": [
          "body.message"
        ]
      },
      "retention": null
    },
    "checkpoint": {
      "_ingest-api-source": {
        "ingest_partition_01J1QRZ4BW3XQ2RBDHFGEMRCME": "00000000000001705167",
        "ingest_partition_01J1RWEC95X1ZXYF9ZTT22HT9Z": "00000000000034089975",
        "ingest_partition_01J2K4H23VR2H0FKGXQVWYT5V8": "00000000000008372206",
        "ingest_partition_01J2SQ0TS33Y19SCRTNMZEW2P4": "00000000000003904812"
      },
      "_ingest-cli-source": {},
      "_ingest-source": {}
    },
    "create_timestamp": 1719858600,
    "sources": [
      {
        "version": "0.8",
        "source_id": "_ingest-source",
        "num_pipelines": 1,
        "enabled": false,
        "source_type": "ingest",
        "input_format": "json"
      },
      {
        "version": "0.8",
        "source_id": "_ingest-cli-source",
        "num_pipelines": 1,
        "enabled": true,
        "source_type": "ingest-cli",
        "input_format": "json"
      },
      {
        "version": "0.8",
        "source_id": "_ingest-api-source",
        "num_pipelines": 1,
        "enabled": true,
        "source_type": "ingest-api",
        "input_format": "json"
      }
    ]
  },
  {
    "version": "0.8",
    "index_uid": "otel-traces-v0_7:01J1QRZ6PJ9556XB15YNZMPV7T",
    "index_config": {
      "version": "0.8",
      "index_id": "otel-traces-v0_7",
      "index_uri": "s3://quickwit/indexes/otel-traces-v0_7",
      "doc_mapping": {
        "field_mappings": [
          {
            "name": "trace_id",
            "type": "bytes",
            "fast": true,
            "indexed": true,
            "input_format": "hex",
            "output_format": "hex",
            "stored": true
          },
          {
            "name": "trace_state",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "service_name",
            "type": "text",
            "fast": {
              "normalizer": "raw"
            },
            "fieldnorms": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "resource_attributes",
            "type": "json",
            "expand_dots": true,
            "fast": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "resource_dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "scope_name",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_version",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_attributes",
            "type": "json",
            "expand_dots": true,
            "fast": false,
            "indexed": false,
            "stored": true
          },
          {
            "name": "scope_dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_id",
            "type": "bytes",
            "fast": false,
            "indexed": true,
            "input_format": "hex",
            "output_format": "hex",
            "stored": true
          },
          {
            "name": "span_kind",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": true,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_name",
            "type": "text",
            "fast": {
              "normalizer": "raw"
            },
            "fieldnorms": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "span_fingerprint",
            "type": "text",
            "fast": false,
            "fieldnorms": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "span_start_timestamp_nanos",
            "type": "datetime",
            "fast": true,
            "fast_precision": "milliseconds",
            "indexed": false,
            "input_formats": [
              "unix_timestamp"
            ],
            "output_format": "unix_timestamp_nanos",
            "stored": true
          },
          {
            "name": "span_end_timestamp_nanos",
            "type": "datetime",
            "fast": false,
            "fast_precision": "seconds",
            "indexed": false,
            "input_formats": [
              "unix_timestamp"
            ],
            "output_format": "unix_timestamp_nanos",
            "stored": true
          },
          {
            "name": "span_duration_millis",
            "type": "u64",
            "coerce": true,
            "fast": true,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_attributes",
            "type": "json",
            "expand_dots": true,
            "fast": {
              "normalizer": "raw"
            },
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "span_dropped_attributes_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_dropped_events_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_dropped_links_count",
            "type": "u64",
            "coerce": true,
            "fast": false,
            "indexed": false,
            "output_format": "number",
            "stored": true
          },
          {
            "name": "span_status",
            "type": "json",
            "expand_dots": true,
            "fast": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "parent_span_id",
            "type": "bytes",
            "fast": false,
            "indexed": false,
            "input_format": "hex",
            "output_format": "hex",
            "stored": true
          },
          {
            "name": "events",
            "type": "array<json>",
            "expand_dots": true,
            "fast": {
              "normalizer": "raw"
            },
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          },
          {
            "name": "event_names",
            "type": "array<text>",
            "fast": false,
            "fieldnorms": false,
            "indexed": true,
            "record": "position",
            "stored": false,
            "tokenizer": "default"
          },
          {
            "name": "links",
            "type": "array<json>",
            "expand_dots": true,
            "fast": false,
            "indexed": true,
            "record": "basic",
            "stored": true,
            "tokenizer": "raw"
          }
        ],
        "tag_fields": [],
        "store_source": false,
        "index_field_presence": false,
        "timestamp_field": "span_start_timestamp_nanos",
        "mode": "strict",
        "max_num_partitions": 200,
        "tokenizers": []
      },
      "indexing_settings": {
        "commit_timeout_secs": 5,
        "docstore_compression_level": 8,
        "docstore_blocksize": 1000000,
        "split_num_docs_target": 10000000,
        "merge_policy": {
          "type": "stable_log",
          "min_level_num_docs": 100000,
          "merge_factor": 10,
          "max_merge_factor": 12,
          "maturation_period": "2days"
        },
        "resources": {
          "heap_size": "2.0 GB"
        }
      },
      "search_settings": {
        "default_search_fields": [
          "service_name",
          "span_name",
          "event_names"
        ]
      },
      "retention": null
    },
    "checkpoint": {
      "_ingest-api-source": {
        "ingest_partition_01J2SQ0TS33Y19SCRTNMZEW2P4": "00000000000000000011"
      },
      "_ingest-cli-source": {},
      "_ingest-source": {}
    },
    "create_timestamp": 1719858600,
    "sources": [
      {
        "version": "0.8",
        "source_id": "_ingest-cli-source",
        "num_pipelines": 1,
        "enabled": true,
        "source_type": "ingest-cli",
        "input_format": "json"
      },
      {
        "version": "0.8",
        "source_id": "_ingest-source",
        "num_pipelines": 1,
        "enabled": false,
        "source_type": "ingest",
        "input_format": "json"
      },
      {
        "version": "0.8",
        "source_id": "_ingest-api-source",
        "num_pipelines": 1,
        "enabled": true,
        "source_type": "ingest-api",
        "input_format": "json"
      }
    ]
  }
]

Thanks for this very detailed report @M0NsTeRRR ! I'll add the gzip compat to the http endpoints. Out of curiosity, why are you not using the GRPC exporter?

Thanks for this very detailed report @M0NsTeRRR ! I'll add the gzip compat to the http endpoints. Out of curiosity, why are you not using the GRPC exporter? That one should work fine even with compression enabled.

You're welcome. I will in the future as I'm working on deploying API Gateway in my Kubernetes cluster. Since it's not available for now, I prefer to use the HTTP endpoint for simplicity.

repo: quickwit-oss/quickwit


text:
Make more regex for SBPayment code stricter

Background

https://github.com/quipper/sbpayment.rb/pull/131/files#r609351789

あえて厳密にしなくてもよいのでは?
@MITSUBOSHI 厳しくする必要性って何でしたっけ?

authors: MITSUBOSHI sakuro

license: mit


text:
chore(main): release 1.13.3

:robot: I have created a release beep boop
1.13.3 (2023-04-03)
Bug Fixes

update sveltekit Request type (#1131) (2197fcd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/quirrel-dev/quirrel/releases/tag/v1.13.3 :sunflower:

Coverage: 82.134%. Remained the same when pulling e71660363803c31a4a26a6a09c3b20a1ea29a6a7 on release-please--branches--main--components--quirrel into 2197fcd914c07cd11d113383cbf3bba500db51b2 on main.

repo: quirrel-dev/quirrel


text:
[other] Please add me to Slack

farah.alyasar@gmail.com

Sent the invitation :)

authors: farahalyasari naveed-ahmad


text:
🛑 Adguard Home DoT is down

In e027918, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in 0ed8c03.

repo: quyleanh/upptime


text:
🛑 Adguard Home DoT is down

In 7f4994f, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in d723821 after 7 minutes.


text:
🛑 Adguard Home DoT is down

In 35a3772, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in 09ed3d8.


text:
🛑 Adguard Home DoT is down

In 541e1ff, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in b174439.


text:
🛑 Adguard Home DoT is down

In 3f15cd2, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in cfc0b07.


text:
🛑 Adguard Home DoT is down

In 99bccba, Adguard Home DoT ($AG_DOT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Adguard Home DoT is back up in c91d519 after 7 minutes.


text:
Want to ask about random ayat?

Hi, Assalamualaikum thanks for this great project.
I see this http://qzaidi.github.io/quran/javascript/
Any method to get random ayat ?
It will be great easy for regular user to just copy paste the snippet for random ayat

Walekum As salam,
Its a great idea. I will add that as a feature, as soon as I have some free
time.
On Tue, Aug 25, 2015 at 4:34 PM, azul notifications@github.com wrote:

Hi, Assalamualaikum thanks for this great project.
I see this http://qzaidi.github.io/quran/javascript/
Any method to get random ayat ?
It will be great easy for regular user to just copy paste the snippet for
random ayat
—
Reply to this email directly or view it on GitHub
https://github.com/qzaidi/quran/issues/2.

The basic feature is added (you just need to skip chapter and verse selectors).
There is an example at http://localhost:4000/2013/10/05/quranjs/.
I am not closing the issue, because I need to now make it clearer which ayat is being shown.

so can I do like this ?
<script src="http://qzaidi.github.io/quran/js/quran.js">
</script>

yes. it should work.

Added Ayah Numbering, closing issue.

authors: azulkipli qzaidi

repo: qzaidi/quran


text:
Convert to Typescript

it's just gonna be easier in the long run, things are already getting complicated and I want type checks because I don't trust myself, especially for utility functions

I'm gonna leave this issue open - #147 gives us a base for adding TS to the codebase, but I haven't actually started converting any code yet. There are some things we should still do first, I think.

Finish setting up eslint - We probably want to just create our own style guide, because the old one I made doesn't reset any of the plain eslint rules that @typescript-eslint supercedes, which leads to problems. We may just want to extend @typescript-eslint/recommended and override the whitespace/aesthetic rules we care about.
another-logger needs typings (i.e. I need to release the next major version)
Need to see if we can do better context typings in yuuko, if not from the library then see if we can do it concisely from each command file

repo: r-anime/discord-mod-bot


text:
Mac instructions per @SiccarPoint

https://gist.github.com/SiccarPoint/f6783361385d0d4665c78835a3ed4317

Thanks!

authors: awickert r-barnes


text:
Possible to query next launch

Is it possible to populate fields when requesting the next launch?
Tried:
POST: https://api.spacexdata.com/v4/launches/next/query
Body:
{
"options": {
"populate": [
"rocket"
]
}
}

Not possible currently, but it can be done though the general launches query endpoint like this:
POST https://api.spacexdata.com/v4/launches/query

Body:
{
  "query": {
    "upcoming": true
  },
  "options": {
    "populate": [
      "rocket"
    ],
    "sort": {
      "flight_number": "asc"
    },
    "limit": 1,
  }
}

Perfect! Thanks for the quick reply.
Always appreicate your great work 🚀

Had the same request, thanks @jakewmeyer!

https://ropsten.etherscan.io/tx/0x0a33e474cf1e237db0957c474ae270d46a1c34c8394cebb75a3cae96e20c9606

repo: r-spacex/SpaceX-API


text:
Scoped Down Proof of Concept Plan in Development Plan Document

24/10/23
Scoped Down Proof of Concept Plan
Initially, the Proof of Concept Plan included the database mapping component of the application but I believe the current plan is to just include the OCR/input portions. This PR updates the POC Plan in the DevPlan document to reflect this.
Changelog

Proof of Concept Plan in Development Plan

Notes

This feels like a better scope for sure. The OCR is the biggest risk to your project. If it doesn't work it will make the project much less appealing. Databases in comparison are super easy and shouldn't cause you any trouble.

authors: CSchank r-yeh

repo: r-yeh/grocery-spending-tracker


text:
Add Function to get size of course in chosen quality

The title is sufficient to make it clear.

udemy don't provide any api endpoint to get the course size while i don't have any plan to implement this feature, so for now i 'm going to close the issue as out-of-scope and later on if i decide or get more requests for this feature then i will think about it.


text:
Feature Request: Add possibility for EQUALS_NOT condition or ELSE statements

I think it would be usefull to add this masterpiece of condition EQUALS_NOT.
This could then make the following possible:
if hasPermissionExample
...

if hasNoPermissionExample
...

it would be easier if you could simply pass an else statement:
    2:
      conditions: ["equalsOperationExample"]
      frames:
        - "&7You can see this line because you passed.."
        - "&7the &8equalsOperationExample &7condition."
      else:
        frames:
          - "&7You can't see this line because you"
          - "&7didn't pass the &8equalsOperationExample &7condition."

Best regards!

Hey, thanks for the suggestion. I'm currently planning on adding support for negating conditions simply by using an "!" before the condition name.
Example: [ "!hasPermissionExample" ] would negate the hasPermissionExample condition.
I do also like the else statement feature so I might get both of them in when I have some free time.

nice, to the '!' I had thought so too.
thanks for your project


text:
API  updates by 2020

The use of FMI's open data no longer requires registration.
Registered users should switch over to the new addresses by the end of 2019 in order to use the service. Addresses that include the API key of the Finnish Meteorological Institute will no longer be operational after 2019.
The new addresses are:
https://opendata.fmi.fi/wfs (Download service - WFS)

https://openwms.fmi.fi/geoserver/wms (View service - WMS)

Thanks! fmi2 already uses the WFS address above (should use https though) and does not require API keys. Or am I missing something here?

Ah right. I just received email from FMI today with that message and missed that this was the same issue that was already solved earlier.

authors: antagomir jlehtoma


text:
ACAD-663 Allow the email in the basic profile to be displayed and edited in the account preferences widget

Two commits here -- the first to enable the configuration and the second to perform the configuration.
https://jira.rsmart.com/browse/ACAD-663

This no longer cleanly merges into develop branch and I am not sure what to keep and what to throw out.  Could you please update the PR?  Thanks, L

authors: croby lancespeelmon


text:
[doc] Fix a typo in the AMQP guide

Fixes a minor typo in the doc

Thank you @dshcherb. master branch is for new release. Can you please resubmit against live branch?

@hairyhum
Sure, thanks.

https://github.com/rabbitmq/rabbitmq-website/pull/196

authors: dshcherb hairyhum

repo: rabbitmq/rabbitmq-website


text:
jump to struct definition

Add structure to definiton?

existed...

repo: racket-tw/sauron


text:
Catch QuotaExceededError

fixes #42

Thanks for the PR, @iam4x. I'd like to address both parts of the solution from https://github.com/rackt/history/issues/42#issuecomment-139453081 in the same PR. Are you up for it?

Sure, but I'll need to understand the whole library before or some hints ;)

This looks good. I can merge and take it from here.

repo: rackt/history


text:
Disambiguating Collections from Catalogs

We should document rules (or provide explicit clues) for disambiguating Collections from Catalogs. Alternately, consider that the distinction doesn't matter.
For example, is this a valid Catalog with additional properties or a non-validating Collection (due to the lack of extent)?
{
  "stac_version": "0.6.0",
  "id": "planet-disaster-data",
  "version": "1.0.0",

  "description": "[Planet Disaster Data](https://www.planet.com/disasterdata/) makes imagery available directly to the public, volunteers, humanitarian organizations, and other coordinating bodies in support of the International Charter for Space and Major Disasters. Data is released for individual disaster events, providing a 30 day window pre- and post-disaster. Imagery is provided under Creative Commons licenses, free of charge, with either CC-BY-SA or CC-BY-NC.",

  "license": "CC-BY-SA-4.0",

  "links": [
    {
      "rel": "self",
      "href": "https://storage.googleapis.com/pdd-stac/disasters/catalog.json"
    },
    { "rel": "root", "href": "catalog.json" },
    {
      "rel": "child",
      "href": "hurricane-harvey/catalog.json",
      "title": "Hurricane Harvey"
    }
  ]
}

I'm approaching this from the consumption angle; if I encounter one of these in the wild (or when validating), how should I treat it? Does the answer vary depending on whether it was traversed to from a link with rel=parent or rel=collection?
If I deem it to be a Catalog, should license apply to children, or does that only apply if it's a validating Collection?

I think, you should read additional information only from rel=collection. At least that is the way we designed it and why there is this additional relation type. rel=parent and rel=root can be collections, too, but the most relevant collection for an item should be linked with rel=collection from the provider so he advises us to take information from there. If a field is missing, it is invalid but we usually should be able to read the other information anyway. I personally wouldn't really handle the other information from parent or root and make assumptions. Is my idea clear? I think it should answer all your questions.

So:

read the root (catalog)
ignore collection properties (apply catalog validation rules)
traverse to find items
traverse rel=collection to (re-)load associated collection (apply collection validation rules)
apply collection properties to item

Is this what you were thinking?

I've been thinking about these same issues while developing sat-stac. From the standpoint of being able to traverse catalogs, find collections, find items, update collections or items, or create whole new catalogs and add collections and items to them, it's definitely useful to be able to determine the difference between a Catalog and a Collection.
Right now in sat-stac, in order to be able to find any child collections underneath an arbitrary catalog I have resorted to checking if the catalog has an 'extent' field. If it does, it instantiates it as a Collection (so that we can then use it as a Collection and do stuff like add Items to it), otherwise it instantiates it as a Catalog.
I think the links work fine, and I'm good with Catalogs using rel='child' links to point to other Catalogs OR Collections. However, once I follow that link it would be better to be able to unambiguously differentiate between a Catalog and Collection.
I posted this in gitter, but here's a notebook showing some of these concepts as:
https://gist.github.com/matthewhanson/151015ad32c84f92100f697b5ec5496d

I guess I'm wondering Seth if you think the above is too annoying for a client to implement? Or if it is reasonable?

It seems reasonable. Agreed on the "display extra properties if present" point as well.

The process depends heavily on the use case, so the 5 steps @mojodna lists above could be suitable for ingestion, but may be not so good for humans browsing a catalog in STAC browser. The browser would more likely just "display extra properties if present". Chris wraps this up quite good.
Programatically, a strict check for collections would be something like:
if (c.isCatalog() && c.hasExtent() && c.hasLicense() && c.hasProviders()): # It's a collection

Should we add a note to the next release regarding this?

I'm not sure if there's any action to take on this now?
Seems like we're good with the way things are. Also note that according to best practices, for static catalogs, a catalog will be called 'catalog.json' and a collection 'collection.json'.  It doesn't help with disambiguating when traversing.
Do we need to add in any further clarifying language?

At this point, probably not. Having it in the issue tracker means other people can find this and re-raise it if they have similar problems.

authors: m-mohr matthewhanson mojodna

repo: radiantearth/stac-spec


text:
Combining eo:bands into assets

The original thinking for a separate eo:bands field for spectral data was that we could define the bands on the sensor, then reference those from the assets so that we would not have to repeat information when a band is used in more than one asset.   So we have an asset:
        "B2": {
            "type": "image/x.geotiff",
            "eo:bands": [
                1
            ],
            "title": "Band 2 (blue)"
        },

Then our bands property is:
        "eo:bands": [
            {
                "name": "B1",
                "common_name": "coastal",
                "gsd": 30,
                "center_wavelength": 0.44,
                "full_width_half_max": 0.02
            },
            {
                "name": "B2",
                "common_name": "blue",
                "gsd": 30,
                "center_wavelength": 0.48,
                "full_width_half_max": 0.06
            }
     ]

However a few things have happened since then.

We now have an asset definition as a way to provide Asset information at the collection level
the realization that 'gsd' in eo:bands is really a characteristic of an asset, not a band. We can get around this by adding in another band with a different gsd, but then we are really not reusing bands like originally intended
it seems that in practice, it isn't common to have bands referenced in multiple assets

One option that can greatly simplify this is to just put the eo:bands info in the asset, so:
    "B2": {
        "title": "Band 2 (blue)",
        "type": "image/x.geotiff",
        "eo:bands": [
            {
                "common_name": "coastal",
                "gsd": 30,
                "center_wavelength": 0.44,
                "full_width_half_max": 0.02
            }
        ]
    },

This avoids the entire referencing back to another array to find out what's in the asset.  And the spectral band info is still at the Collection level, but consolidated so easier for humans.
The drawback is that the asset info is duplicated at the Item level the way we have things right now, unless we allow for partially described assets at the Item level (e.g., just href, and requires deep merge with asset definition to get the whole thing).

Sorry, I don't get it. Why is gsd still at the item level if it is asset specific? How is the relation between asset-level and item-level bands? Why is the band name missing from the asset-level band? Would I be allowed to also use other fields at the asset-level? Maybe a full item example would help...

Related PR, which had some discussions and was closed: https://github.com/radiantearth/stac-spec/pull/270

GSD is still at the Item level because it represents the best possible resolution across all bands for the Item. This change wouldn't affect that at all.
Leaving out band name was just an oversight.
Nothing here requires the use of an asset definition.
I'm not even convinced myself bands should be folded up into asset, but I thought it was worth discussing.  The problem that needs to be solved, and that the current behavior is not modeling well, is that eo:gsd, and sar:data_type and sar:units from the sar extension are not attributes of spectral bands (eo) and data_type and units are absolutely not properties of polarization.   What that leads to is having to duplicate certain bands with just slightly tweaked variables.
If we just moved resolution into the assets that would also solve the problem. The question about adding in other attributes is a good one, and this is really what @hgs-truthe01 has always been pushing for with the common metadata model, so that you could define any attributes at any level.

authors: m-mohr matthewhanson


text:
Moving eo:gsd into assets (remove eo:gsd)

In working session, we discussed #685 and #656 , but could not come to a decision except we agreed that eo:gsd is not an attribute of spectral bands, since it can change due to processing.
Instead, eo:gsd belongs in the assets as an array to indicate the resolution of each band in the asset.
At the Item level, eo:gsd should either be changed to an array (to include all potential resolutions from all items), or removed.
Optionally, we could add a eo:best_gsd or similar to the Item to contain a single number, the lowest GSD possible across all assets.

My question is how we define which fields are allowed in assets. Should it be all (common metadata model) or just a subset? How to determine, which are suitable and could be useful in other use cases?
Also, all things in assets can't be summarized in "collection-only" use-cases using the collection summaries. Therefore, I think it should also be defined on the item-level, but that would basically be a summary again. So do we allow "summaries" for all asset-level metadata we add?
I think having a field best_gsd is a bit flawed as it pushes an implementation detail to the spec. If an implementation needs the best gsd resolution for easier searching, it should be added during index creation of the back-end by simply using the smallest gsd value from the gsd summary if available (or the assets).

Discussed in call:

remove gsd from eo:bands

See PR #703


text:
Elegant tab needs better error messages

Is there some way to visualize errors from failed simulations inside RadTrack? For instance, if ELEGANT fails because I forget to populate one of the Quad parameters I simply get told Simulation failed with errors. How do I find these errors from within RadTrack?

David, could you ask Christina to send the LTE file that causes Elegant to fail? She can also just describe the beam line that was created in the Elegant tab. I've tried a completely blank beam line shown below and Elegant didn't return any errors.
! This Elegant file was created by RadTrack
! RadTrack (c) 2013, RadiaSoft, LLC

X1:  DRIF
Q:  QUAD
B:  LINE=(X1, Q)

RETURN

I've forwarded the request to Christina.
David
On Tue, Dec 8, 2015 at 3:35 PM, Mark Harrison notifications@github.com
wrote:

David, could you ask Christina to send the LTE file that causes Elegant to
fail? She can also just describe the beam line that was created in the
Elegant tab. I've tried a completely blank beam line shown below and
Elegant didn't return any errors.
! This Elegant file was created by RadTrack
! RadTrack (c) 2013, RadiaSoft, LLC
X1:  DRIF
Q:  QUAD
B:  LINE=(X1, Q)
RETURN
—
Reply to this email directly or view it on GitHub
https://github.com/radiasoft/radtrack/issues/137#issuecomment-163041527.

Mark, David,
I think I made an example where you can stop general output from Elegant and pipe out only "milestone" and error messages. Is this something that you are looking for?
Timur.

On Tue, 12/8/15, Mark Harrison notifications@github.com wrote:
Subject: [radtrack] Elegant tab needs better error messages (#137)
To: "radiasoft/radtrack" radtrack@noreply.github.com
Date: Tuesday, December 8, 2015, 5:25 PM
Is there some way to visualize
errors from failed simulations inside RadTrack? For
instance, if ELEGANT fails because I forget to populate one
of the Quad parameters I simply get told Simulation failed
with errors. How do I find these errors from within
RadTrack?
—
Reply to this email directly or view
it on GitHub.

Commit referenced above should give more information about why Elegant stopped in the case of crashing or other irregular stoppage. As a last resort, this tab writes to two files: elegant_output.txt and elegant_errors.txt, which may help diagnose the problem.

Given the number of changes since this issue report and the lack of response, I'm closing this issue since any problems are different by now.

authors: MZHarrison bruhwile shaftan

repo: radiasoft/radtrack


text:
[Chore] Added, submitted review status translations in the homepage and JSON …

…scripts.

Proposed changes

See commits.

Thanks!

authors: gpassport jg-rivera

repo: radical-doubting/anikultura-frontend


text:
Add support for collect

Add support for the collection of funds
Add unit tests

Resolves: https://github.com/radicle-dev/drips-js-sdk/issues/20

Looks great. Nice work @jtourkos !

repo: radicle-dev/drips-js-sdk


text:
🛑 (Admin) ACE Solar is down

In a6df402, (Admin) ACE Solar (https://admin.acesolar.co.th) was down:

HTTP code: 502
Response time: 237 ms

Resolved: (Admin) ACE Solar is back up in 2ceedf4.

repo: radiuszon/upptime


text:
Change default values of Tooltip props in the TooltipProvider

Feature request
Overview
Have the ability to change the default value of Tooltip props using a TooltipProvider in the same way that you can already use it to set the default delayDuration.
For example, in the app that I work on, for most of the app we want the tooltips to always display centered below the trigger element. But in our primary navigation sidebar, we want all of the tooltips to be on the right of the trigger.
Here's an extremely simplified of what I'm suggesting:
<App>
	<TooltipProvider side="bottom" sideOffset={4} align="center">
		<header />
		<TooltipProvider side="right">
			<aside>
				<nav />
			</aside>
		</TooltipProvider>
		<main />
	</TooltipProvider>
</App>

Who does this impact? Who is this for?
This could be helpful for all types of users who want to have more control of the default props of their tooltips. This could extend to any of the Radix UI Primitive components as a standard pattern,
Additional context
Happy to do the work myself if the Radix team thinks it's worthwhile!

Hi @matthewtole, thanks for raising an issue.
I don't think we would want to support nested providers here because there is global logic running in it and it is designed as a top-level provider (hence why it handles only global things that are shared behaviour of multiple tooltip instances).
On top of that, most of the time this is easily handled by default props.
Additionally it would open the door for more similar changes for lots of other similar components which don't currently have global providers.
For all these reasons I don't think it brings enough value to warrant the extra API surface.
Hope that makes sense.
✌

authors: benoitgrelard matthewtole

repo: radix-ui/primitives


text:
Navigation menu return focus from item menu

Bug report
Loving your library, but...
Current Behavior
Create a navigation menu with items without any animations. Use keyboard to navigate to an item and into the expanded menu. When in the menu press 'esc', and watch the focus disappear. I'm not sure where the focus goes, but it does not return to the navigation menu item.
Expected behavior
When pressing escape return focus to navigation menu item, even if I don't use animations.
Reproducible example
CodeSandbox Example showing the bug

Thanks for reporting @esDesler, I noticed this only occurs when using the legacy render api (r17 rendering), by changing to createRoot this problem goes away:
https://codesandbox.io/s/radix-navigation-menu-return-focus-bug-forked-x2jrq8?file=/index.js
I also noticed the menu doesn't dismiss when focus leaves the list in the CSB example though it functions correctly when rendered in our documentation, we'll investigate. 🙏

authors: andy-hook esDesler


text:
[DropdownMenu] Unexpected blur behavior when clicking the menu trigger

Bug report
Current Behavior
When using Mantine's DatePicker and Radix UI's DropdownMenu in the same page, the date picker doesn't close when clicking the menu trigger, but the menu is still opening. However, when the menu trigger is clicked again to close the menu, the date picker is also closed.
https://user-images.githubusercontent.com/44197016/214293988-a0693a31-a9b0-4d60-a9f3-a9ae84cc8b28.mov
Expected behavior
I'd expect the date picker to close when clicking on the menu trigger. The menu should probably not open on menu trigger click, but rather only close the date picker. I.e. it should work as when I click a regular button (see video), or when I click anywhere else to blue the date picker.
Reproducible example
CodeSandbox Template
Suggested solution
I think there's something related to preventing defaults in the DropdownMenu.Trigger component that causes this, since it doesn't happen with any other component I have tried. When clicking any other interactive or non-interactive component (or anywhere else), the date picker closes.
Additional context
Since the DatePicker works as expected with all other components I have tried, I'm pretty confident the problem comes from @radix-ui/react-dropdown-menu and not from Mantine.
Your environment

Software
Name(s)
Version

Radix Package(s)
react-dropdown-menu
2.0.2

React
n/a
18.2.0

Browser
Chrome
109.0.5414.87 (Official Build) (x86_64)

Operating System
MacOS
Ventura 13.1

Hey @filiptammergard, it seems that the link of the codesandbox isn't right

Hey @filiptammergard, it seems that the link of the codesandbox isn't right

Better now?

The DropdownMenu.Content is opened when onPointerDown in DropdownMenu.Trigger and Mantine listen for mousedown and touchstart events to close the datepicker when clicked outside. If you override the clickOutsideEvents prop in datepicker to listen to pointerdown event, then the datepicker will close when you click on DropdownMenu.Trigger.
CodeSandbox

Nice find @joaom00! But clicking with a mouse if both a mouse event and a pointer event. How come the date picker doesn't close only when I click the dropdown menu trigger?

it's because of that https://github.com/radix-ui/primitives/blob/21a7c97dc8efa79fecca36428eec49f187294085/packages/react/dropdown-menu/src/DropdownMenu.tsx#L124
when event.preventDefault in onPointerDown  the mousedown doesn't catch it, but pointerdown does.
You can see here

Nice! Took some research to understand the why behind this, so I wrote a blog post on it for future lurkers: https://tammergard.se/blog/mouse-touch-and-pointer-events/
Thanks for helping out @joaom00!
If there some other way to avoid focus competition? Since calling preventDefault on pointerdown has the side-effect of not firing compatibility mouse events, and therefore might cause weird bugs when listening to mousedown, I think it would be preferable to avoid doing that if possible.

Nice post @filiptammergard! and nice blog too 😄. I had no idea about this side-effect either until this issue.

Thanks! What do you think about using onMouseDown instead of onPointerDown in this case, to avoid the side-effect? 🙂

since there is "compatibility mouse events", it seems to be a good option, but I think they would have to do it in other components too

Coming here again to say that using onMouseDown instead of onPointerDown seems more interesting since it would solve #1912 and #1641.
The mousedown event doesn't fire when scrolling the page while "touchdown" trigger. @filiptammergard  wrote a great post about this and you can test this behavior there.

Is there any workaround we can use until it's resolved by Radix team?

@TmLev Given that onMouseDown might be a good candidate to fix the issue, in the meantime, you can rewrite the logic in the onMouseDown event and use event.preventDefault in onPointerDown. I don't know if this will break some others behaviors 🤔
https://github.com/radix-ui/primitives/blob/21a7c97dc8efa79fecca36428eec49f187294085/packages/react/dropdown-menu/src/DropdownMenu.tsx#L117-L126

onMouseDown didn't work for me – had to use onClick, but it helped with the scrolling issue. Thanks!

@TmLev Ohh, I made a mistake. Sorry for that! 😅
When you use event.preventDefault in onPointerDown, the onMouseDown is not fired.
Just a note, using onClick could work but you lose the ability to select a value in one click lifecycle (down, move, up).

Just a note, using onClick could work but you lose the ability to select a value in one click lifecycle (down, move, up).

So what solution would be better in that case?

So what solution would be better in that case?

I think this could work

authors: TmLev filiptammergard joaom00


text:
Checkbox "checked" updated triggers onClick event on parent div when inside a form

Bug report
Current Behavior
When a checkbox is inside a <form>, any update on its checked prop will trigger an onClick event that will propagate to its parent.
Bug found while making a form with a select all checkbox that would mark all the other checkboxes as checked.
The other checkboxes were located inside
 that were clickable.
The onClick event originates from the internal <input> used by the checkbox.
Expected behavior
The event on the internal <input> should not propagate to the parent.
It also shouldn't be triggered after an update on the checked prop.
Reproducible example
CodeSandbox example
Suggested solution
See Expected behavior.
Additional context
Might be the same issue as https://github.com/radix-ui/primitives/issues/3192 and https://github.com/radix-ui/primitives/issues/2704.
Your environment

Software
Name(s)
Version

Radix Package(s)
checkbox
1.1.2

React
n/a
17.0.1

Browser

Assistive tech

Node
n/a

npm/yarn

Operating System

Hi, on my side, I avoid this issue by removing the onClick from the div, like this :

          [ ✔ ]

test

Hi, on my side, I avoid this issue by removing the onClick from the div, like this :
<form>

        <Checkbox.Root checked={isChecked} onCheckedChange={setIsChecked}>
          [ <Checkbox.Indicator>✔</Checkbox.Indicator> ]
        </Checkbox.Root>
        test

    </form>

In my case I can't because I need the whole div to be clickable (it contains other elements than the checkbox).

authors: Tom-Aive paullfhc


text:
Support programatically changing selected view on RadzenScheduler

Is your feature request related to a problem? Please describe.
There seems to be no way to programatically select RadzenScheduler's view. SelectedIndex only dictates which index is selected on initialize. The user has to click a Scheduler view selection button at the top which calls a private OnChangeView handler.
Describe the solution you'd like
There should be SelectView(ISchedulerView) method on the Scheduler akin to AddView(ISchedulerView)
Describe alternatives you've considered
Tried forcing re-render after changing SelectedIndex and some other workarounds but they were buggy at best.

Setting SelectedIndex is supposed to work: https://forum.radzen.com/t/scheduler-programmatically-set-view-day-week-month/12111. What did you try?

I've tried exactly that. It changes it once. Then when you switch back to month view, and click again, nothing happens.
Here are some code snippets. I've just re-tried in in the radzen demo project.
<RadzenScheduler @ref=@scheduler SlotRender=@OnSlotRender style="height: 768px;" TItem="Appointment" Data=@appointments StartProperty="Start" EndProperty="End"
    TextProperty="Text" SelectedIndex="@SelectedIndex"
    ...

@code {
private int SelectedIndex { get; set; } = 2;
...
}

async Task OnSlotSelect(SchedulerSlotSelectEventArgs args)
    {
        SelectedIndex = 0;
        await scheduler.Reload();
     }

The Docs on the SelectedView even say "Specifies the initially selected view"

Regardless of whether this is a bug or not, I still believe it's beneficial to have #842

Try without calling Reload(). The scheduler should reload if selected index changes (check the linked code in the PR).
We prefer to have only one method of changing views instead of two.

I did. The issue persists. Tried with and without StateHasChanged(); too
I believe the issue here is that the SelectedIndex which is passed as the parameter stays the same. When you manually click on Month, only the scheduler's private selectedIndex changes to 2. When you select the slot again, the selected index is set again to 0, which is it current value, both inside and outside the Scheduler. Check line 376 in side the RadzenScheduler.razor.cs, maybe you should compare the parameter to selectedView, although that seems hacky.
Once again, dealing with indices which can be changed by simply re-ordering html seems wrong to me and I'd much prefet having a view reference.

I just tested it in our online demo and it seems to work as expected. What wouldn't work though is trying to change it a second time. The selectedIndex will stay the same (0) and nothing will change. It would have worked if SelectedIndex supported two-way data-binding @bind-SelectedIndex. Anyway I will accept the PR.

authors: Conduci akorchev

repo: radzenhq/radzen-blazor


text:
How can I put a checkbox inside a column label of a b-table

I want to put a checkbox in a column header of a b-table. How can I do this?
Cheers,
Zhen Zhang

You can't for the moment.

https://github.com/rafaelpimpa/buefy/issues/215

authors: Tirke rafaelpimpa zhangzhen

repo: rafaelpimpa/buefy


text:
NOTIFICATION_WAKE_UP_SCREEN not working

I'm handling firebase onBackgroundMessage with awesome notification.
Here is my code:
Future backgroundHandler(RemoteMessage message) async {
if (!AwesomeStringUtils.isNullOrEmpty(message.notification?.title,
considerWhiteSpaceAsEmpty: true) ||
!AwesomeStringUtils.isNullOrEmpty(message.notification?.body,
considerWhiteSpaceAsEmpty: true)) {
Map<String, dynamic> notificationAdapter = {
NOTIFICATION_CHANNEL_KEY: 'mychannel',
NOTIFICATION_ID: DateTime.now().millisecondsSinceEpoch ~/ 1000,
NOTIFICATION_WAKE_UP_SCREEN: true,
NOTIFICATION_TITLE: message.notification!.title,
NOTIFICATION_BODY: message.notification!.body,
};
log(notificationAdapter.toString());
AwesomeNotifications().createNotificationFromJsonData(notificationAdapter);
} else {
AwesomeNotifications().createNotificationFromJsonData(message.data);
}
}
Everything works fine but fone screen does not wake up but when I use createNotification method instead of createNotificationFromJsonData fone screen wakes up but I get duplicate notification. Here's the code with createNotification
Future backgroundHandler(RemoteMessage message) async {
AwesomeNotifications().createNotification(
content: NotificationContent(
id: DateTime.now().millisecondsSinceEpoch ~/ 1000,
channelKey: 'mychannel',
wakeUpScreen: true,
title: message.notification!.title,
body: message.notification!.body));
}

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!

authors: hasnainusti rafaelsetragni


text:
use nvim_buf_set_extmark instead of nvim_buf_add_highlight

nvim_buf_add_highlight has the downside of not being able to set the priority. This means the Coverage highlights may not always show properly because they can get overridden by other things.
This PR replaces nvim_buf_add_highlight with nvim_buf_set_extmark, which can set the priority to guarantee its highlights are always written last.

thank you @korylprince

authors: korylprince rafaelsq


text:
Program won't install over itself after uninstalled

Just a quick error report dump. It looks like the installer doesn't yet know how to install over itself. It's a very reasonably specific name so I think you'd be safe to override the error-checking and install any way. For clarification I did not restart Windows or sign out/in first.
`PLATFORM VERSION INFO
Windows 			: 10.0.19045.0 (Win32NT)
Common Language Runtime 	: 4.0.30319.42000
System.Deployment.dll 		: 4.8.9195.0 built by: NET481REL1LAST_B
clr.dll 			: 4.8.9195.0 built by: NET481REL1LAST_B
dfdll.dll 			: 4.8.9195.0 built by: NET481REL1LAST_B
dfshim.dll 			: 10.0.19041.30000 (WinBuild.160101.0800)
SOURCES
Deployment url			: file:///D:/My%20Documents/Downloads/ClearStandbyMemoryScheduler%20App%20Install/ClearStandbyMemoryScheduler.application
Application url			: file:///D:/My%20Documents/Downloads/ClearStandbyMemoryScheduler%20App%20Install/Application%20Files/ClearStandbyMemoryScheduler_1_0_0_1/ClearStandbyMemoryScheduler.exe.manifest
IDENTITIES
Deployment Identity		: ClearStandbyMemoryScheduler.application, Version=1.0.0.1, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=msil
Application Identity		: ClearStandbyMemoryScheduler.exe, Version=1.0.0.1, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of D:\My Documents\Downloads\ClearStandbyMemoryScheduler App Install\ClearStandbyMemoryScheduler.application resulted in exception. Following failure messages were detected:
+ Unable to install this application because an application with the same identity is already installed. To install this application, either modify the manifest version for this application or uninstall the preexisting application.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
* The manifest for this application does not have a signature. Signature validation will be ignored.
* The manifest for this application does not have a signature. Signature validation will be ignored.
OPERATION PROGRESS STATUS
* [12/23/2024 9:44:25 AM] : Activation of D:\My Documents\Downloads\ClearStandbyMemoryScheduler App Install\ClearStandbyMemoryScheduler.application has started.
* [12/23/2024 9:44:25 AM] : Processing of deployment manifest has successfully completed.
* [12/23/2024 9:44:25 AM] : Installation of the application has started.
* [12/23/2024 9:44:25 AM] : Processing of application manifest has successfully completed.
* [12/23/2024 9:44:28 AM] : Found compatible runtime version 4.0.30319.
* [12/23/2024 9:44:28 AM] : Request of trust and detection of platform is complete.
* [12/23/2024 9:44:28 AM] : Downloading of subscription dependencies is complete.
* [12/23/2024 9:44:28 AM] : Commit of the downloaded application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [12/23/2024 9:44:28 AM] System.Deployment.Application.DeploymentException (Subscription)
- Unable to install this application because an application with the same identity is already installed. To install this application, either modify the manifest version for this application or uninstall the preexisting application.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SubscriptionStore.CheckApplicationPayload(CommitApplicationParams commitParams)
at System.Deployment.Application.SubscriptionStore.CommitApplication(SubscriptionState& subState, CommitApplicationParams commitParams)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
`

Also I did explicitly exit the program on a second attempt to make sure it's not a problem with it still running thus blocking the install.

I signed off and signed back on to see if that would fix the installer. So then the program opened back up!
So the uninstaller (Windows Control Panel "Programs and Features",  not "settings app" garbage) failed to uninstall which I guess is another issue (sorry man).
The program runs from the registry and the executable is located here:
c:\users\john\appdata\local\apps\2.0\pwhykwve.nn1\hxa4rhdl.nyh\clea..tion_0000000000000000_0001.0000_90e23d48f06eff06\clearstandbymemoryscheduler.exe

Damn, I was about to manually remove it though when I minimized it the program did the 1.0.0 behavior...because it is 1.0.0! So the installer created a second version folder:
1.0.0.1?:
C:\Users\John\AppData\Local\Apps\2.0\PWHYKWVE.NN1\HXA4RHDL.NYH\clea...exe_0000000000000000_0001.0000_none_68b400649c412da1
1.0.0.0:
C:\Users\John\AppData\Local\Apps\2.0\PWHYKWVE.NN1\HXA4RHDL.NYH\clea..tion_0000000000000000_0001.0000_90e23d48f06eff06
If no one tells you then you don't know it needs to be fixed.
Are you using C or something like .NET?

Can reproduce on Windows 10, but not on Windows 11. The issue will not persist once you uninstall the application first and install the latest version. After that installing over it does not cause any issues. I guess this issue was caused by conflicting versions. The previous v1.0.0.1 you had installed and the latest v1.0.0.1 have the same id.  It would have been better to draft a new version for issue #3, I suppose. Sorry for that.
So uninstall the application, then reinstall. Then try reinstalling again and it should not give any errors. Let me know if that works.

Are you using C or something like .NET?
In the right column of the app page you will find the programming languages for that app. The app is written in C# using .NET Framework 4.7.2.

I manually deleted everything in the following directory:
C:\Users\John\AppData\Local\Apps\2.0
That then allowed the second installer to function; hopefully that helps you out somehow.

It only confirms that the previous v1.0.0.1 you had installed and the latest v1.0.0.1 had the same id and where conflicting. So there is no issue anymore.

authors: jabcreations rafcolson

repo: rafcolson/ClearStandbyMemoryScheduler


text:
Sorry, you've not configured an origin remote or passed a repo_url config value

i've got this config:
{
    "app_name": "processo",
    "logo": "https://github.com/rafinskipg/git-changelog/raw/master/images/git-changelog-logo.png",
    "intro": "Projeto de controle",
    "branch" : "master",
    "repo_url": "git@xxxxxx:xxxxxx/processo.git",
    "version" : "v1.0.0",
    "file": "CHANGELOG.md",
    "sections": [
        {
            "title": "Correções de Bug",
            "grep": "(\[FIX\])|correção/i"
        },
        {
            "title": "Features",
            "grep": "\[FEATURE\]"
        },
        {
            "title": "Erro 500",
            "grep": "\[500\]"
        },
        {
            "title": "Refactoração",
            "grep": "\[REFACTOR\]"
        },
        {
            "title": "Test",
            "grep": "\[TEST\]"
        },
    ]
}

i use this command:
git changelog -r git@git.xxxxxx.com.br:xxxxxxx/processo.git

and i get this output:
Executing git changelog:
  - With URL git@git.xxxxxx.com.br:xxxxxxx/processo.git
Found changelog rc
Sorry, you've not configured an origin remote or passed a `repo_url` config value

what am i doing wrong?

Hello @jhonatanTeixeira can you print the output you get from running it with --debug ?
Adding a remote repository log without being in the current folder of the repository doesn't work.
Internally we use git log command, on the current repository.  So you must run the command in the current repository folder.
For ex:
cd myProject
git-changelog --debug

Git does not provide the functionality of retrieving the history from a repository you have not downloaded.
In order to have the feature of logging remote repositories without being in a repo folder some code has to be written.
I think in terms of functionality it should do something like this:

Whenever a user types -r REPO_URL on a folder that it's not a git repo:

Create a folder called .tmp (in the git-changelog directory?)
Go into that folder and clone the remote repo
Do the git log in that repo
Remove the folder .tmp after some time.
This will be time expensive.. but i think its a cool feature.

#68

authors: jhonatanTeixeira rafinskipg

repo: rafinskipg/git-changelog


text:
Suggested hubs always seems to be offline

In the recent implemented suggested hubs list #2429 , the suggested hubs appear to alway be offline.
Steps to Reproduce

Serve the #2429 PR locally.
Select the 0x59105441977ecD9d805A4f5b060E34676F50F806 token
Choose any of the suggested hubs

Expected Result

For selected hub to appear as online

Actual Result

Suggested hub (any of the selected) always appears as offline

Additional Infos (Optional)

@talel this should go on the https://github.com/raiden-network/raiden-services repo, as I've mentioned on the call

authors: andrevmatos taleldayekh

repo: raiden-network/light-client


text:
Week 5 Day 5 morning session

[Optinal]:- That I think your Contact Me session has less text area

Great work @raihan2bd this is very impressive! Just Keep it up!

What you can just consider is the comment from the other code reviewer @Hassaanjbaig-code

authors: EddyShimwa Hassaanjbaig-code


text:
Fix default sort by behavior when list.sort_by points to a field with a table reference for :sortable

On a list page, when a sort param is not specified, the current version of rails admin defaults to appending the list.sort_by to the model table. This causes list.sort_by to always  be treated as a string when a sort param is not present. This changes the behavior to lookup the field specified in list.sort_by rather than treating it as a string.
This also updates the dummy gemfile to point to devise's main branch, as they changed the master branch to the name main.
For example, if we have the following:
RailsAdmin.config('Player') do
    base do
      field :name do
        sortable :'teams.name'
      end
    end

    list do
      sort_by :name
    end
 end

the query would be generated with a sort by players.name, when we actually want to sort by teams.name.

Coverage remained the same at 91.159% when pulling 6b3244281afa1762aa6fc8fd246991cae1683e64 on aaronlifton:fix-default-sort-by into e5bb7ba712a00ede56ffc8a547b36b13bd72a9ee on railsadminteam:master.

Agreed, thanks!

authors: aaronlifton coveralls mshibuya


text:
Update fontello to 0.4.4 cause the font to be invalid

I'm using this fontello version: http://fontello.com/4b5662f50f20726734977f1bf3a79921
I then run fontello convert to get this downloaded as SCSS and require fontello-embedded.scss from our application.css
Open http://localhost:3000/fontello-demo.html render everything properly.
But our rails application no longer render the icon. In the Chrome console, I see this:
Failed to decode downloaded font: http://localhost:3000/assets/fontello-embedded.self-c7c85a28831944af166f8e1b09fba13a589244dbc4b7d8954b737ea62fc5b2e5.css?body=1
active:1 OTS parsing error: invalid version tag

Open the css file at that line, I have this:
@font-face {
  font-family: 'fontello';
  src: url(/assets/fontello-fbdd14ac6956eb4bdaf31bda515cfe4868acf02517d5c2869681e236cae9df34.eot?45662313);
  src: url(/assets/fontello-fbdd14ac6956eb4bdaf31bda515cfe4868acf02517d5c2869681e236cae9df34.eot?45662313#iefix) format("embedded-opentype"), url(/assets/fontello-9087fab575ab67b0a6baadfb203c33b7d4d7e682dba076563b7569a4512542f7.svg?45662313#fontello) format("svg");
  font-weight: normal;
  font-style: normal;
}

These url: /assets/fontello-fbdd14ac6956eb4bdaf31bda515cfe4868acf02517d5c2869681e236cae9df34.eot, /assets/fontello-9087fab575ab67b0a6baadfb203c33b7d4d7e682dba076563b7569a4512542f7.svg can all be downloaded and have same md5 hash with the original asset in /vendor/assets/fonts/fontello.*
Not sure what's wrong?

Hmm, I notice that there is a base64 octet-stream in the css that use font-url helper to render. I change that to url and it works fine. I'm on Rails 4.2 though.