Use logging module instead of print statements

Hi Everyone,
What is your opinion on using the logging module instead of print statements for communicating with the user?
This might become important if the code were to be used in an operational setting down the line.
I guess for the training, some of the logging is done by wandb, but I guess it could be usefull for logging error messages when loading datasets etc.
Kind regards,
Michiel

great question @mpvginde! I don't think we have any guidelines/principles on that yet. I personally like using loguru because it has an easy setup, is an extension of python logging and makes it very easy to log to different outputs. So if we do start using logging I would vote for that, and then we could generally log progress of the application with INFO (like read file from ..., wrote output to ...) and debugging information used during development with DEBUG loglevel. In general I would say that if you find logging useful then I would welcome a PR from you adding it. As long as we use loglevels then people can easily opt-out by setting the loglevel appropriately.

I think more control over logging could be useful. For my use cases the current setup with wandb is quite sufficient, but it does not hurt to have more control and loglevels. A few thoughts from my side:

As you mention most logging is done to wandb (in the future maybe extended to also other experiment-tracking platforms). I think that should really be the main way to log, rather than printing to stdout. However, some things are hard to log to wandb, e.g. the graph overviews that print when models are created.
Most of the printing right now is done by Lightning. So however you decide to control logging, the most important thing is that it plays nicely with Lightning. What we would want to avoid is a situation where most logging is handled robustly using e.g. loguru, but then Lightning just prints things to stdout without any control anyway. I think this should be manageable, but it's an important aspect when implementing this.
We should make sure that no logging causes performance hits, e.g. by forcing GPU syncs. But I guess most interesting logging would be during initialization and not in the training/validation loops.


Fix formatting in Using Docker Registries

Due to an unnecessary line-break, the paragraph is split
in the middle of the word.

Thank you, @mkowalski


replace English text with Japanese translations

When JA locale is selected,

[ ] Replace 'Donate Options' in donate modal with お支払い方法.
[ ] Replace 'Join our Team' in /one-young-world with チームに参加する.
[ ] Implement proposed translation changes listed in Excel sheet. There are about 17 proposed changes.

what about "Apply to this role" in JobDetailPage?

Yeah, good catch. That will be be updated as well.
After review from the Japan team, there's a decent amount of content that needs to be translated or re-translated.


Using native chat messenger?

Is there a way to open a new message in iMessage (and whatever is Android equivalent) with an image?

iMessage appears in the More tab, but doesnt appear on the Simulator!


Hook up new hash map methods to API

Duplicate of https://github.com/momentohq/client-sdk-python/issues/175


save_tiktok_multi_page() got an unexpected keyword argument 'save_metadata'

I not see anymore 'save_metadata' option, but on example there is

Just fixed this. I'll push the changes to PyPI in a moment.


Empty global components props typings

Upstream issue from https://github.com/nuxt/nuxt/issues/20010 (comment)
Environment
Operating System: Darwin
Node Version: v16.18.1
Nuxt Version: 3.3.2
Nitro Version: 2.3.2
Package Manager<EMAIL_ADDRESS>Builder: vite
User Config: -
Runtime Modules: -
Build Modules: -

Reproduction
https://github.com/niklv/nuxt-component-props-def-bug
Bug
For my project config typing I need to refer to typing of component props.
I try extract props typing in this way. But looks like there are no props typing at all.
<script lang="ts" setup>
// ComponentA.vue
const {propA} = defineProps<{
    propA: string
}>()
</script>

<template>
    <div v-text="propA" />
</template>

// config.ts
import type {ComponentA} from "#components";
import {ComponentOptionsBase} from "@vue/runtime-core";

type ComponentProps<T> = T extends ComponentOptionsBase<infer P, // Props
    any, // RawBindings
    any, // D
    any, // C
    any, // M
    any, // Mixin
    any, // Extends
    any> ? unknown extends P ? {} : P : {};

type CompAProps = ComponentProps<typeof ComponentA>

const someConfig:CompAProps = {
    // @ts-expect-error
    notExistedProp: true // should be error
}

Additional context

There are must be some props typing in first generic argument of DefineComponent

This is probably due to the DefineComponent signature being updated, but now you can use https://github.com/vuejs/language-tools/tree/master/packages/vue-component-type-helpers instead of.

@johnsoncodehk I update deps in repoduction
The issue is still there.

Did you see https://github.com/vuejs/language-tools/tree/master/packages/vue-component-type-helpers?


[BugFix] refactor cloud native pk table publish & fix local persistent index usage

This PR contains two parts:

Fix local persistent index in cloud native pk table, because it was missing the call to prepare & commit.
Get or create primary index when first time apply write_log or compaction_log, and release it when TxnLogApply end.

What type of PR is this:

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

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 37 / 43 (86.05%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/update_manager.cpp
24
30
80.00%
[64, 65, 66, 70, 72, 74]

:large_blue_circle:
src/storage/lake/lake_local_persistent_index.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/txn_log_applier.cpp
12
12
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 40 / 46 (86.96%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/update_manager.cpp
25
31
80.65%
[64, 65, 66, 70, 72, 74]

:large_blue_circle:
src/storage/lake/lake_local_persistent_index.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/meta_file.h
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/txn_log_applier.cpp
13
13
100.00%
[]

@Mergifyio backport branch-3.2

@Mergifyio backport branch-3.1


nextflow tower add pipeline setup

For setting up pipelines on nextflow tower, can you confirm I am adding a pipeline properly? As an example, I am trying to add Cell Ranger mapping (cellranger count) pipeline from the Ingestion workflow, using google life science as a compute environment platform:
Go to Launchpad, then Add pipeline
Name: pipeline_name
Pipeline to launch: https://github.com/openpipelines-bio/openpipeline
Revision number: main_build   <--  Is this correct? Or use main branch?
Config profiles: target/nextflow/mapping/cellranger_count/nextflow.config    <--  Is this needed? I've seen examples where this appears to be omitted.
Main script: target/nextflow/mapping/cellranger_count/main.nf
Schema name: target/nextflow/mapping/cellranger_count/nextflow_schema.json
Head Job CPUs: 2    <-- Pipeline doesn't appear to build properly (dropdown not rendered upon run launch without numeric value)
Head Job memory: 256    <-- Pipeline doesn't appear to build properly  (dropdown not rendered upon run launch without numeric value)
Any suggestions or reproducible examples would be greatly appreciated. Thanks in advance

Hi @rhodesch
Thanks for reaching out!
To answer your questions:

The main branch contains the source code only. This source code needs to be build into the nextflow and docker artifacts which can be used to actually run the pipeline. These can be found on main_build. However, the main_build branch is the development branch for this project, and changes constantly. If you would like to use a stable release, I would suggest that you use one of the tags, like 0.9.0.
Yes, the config file is required when using OpenPipelines
The Head Job CPUs and Head Job memory parameters are handled by nf-tower. I could be wrong, but I dont think this is pipeline-code related. In most of the usecases I have seen, the Head Job CPUs and Head Job memory was left blank because this is handled by the compute environment. However, I have no experience with using google cloud as a compute environment so YMMV. Are you following a specific guide to setup the pipeline? I found this one in the nf-tower documentation: https://help.tower.nf/21.12/compute-envs/google-cloud/#tower-configuration. I think it mentions here that you need to specify values for Head Job CPUs and/or Head Job memory in the compute environment config, which in turn populates the dropdown.

Let me know how it goes!
Dries

Hi @rhodesch I am going to close this issue because it has become inactive. Please reopen if you feel it is necessary


Clear vector_store_id and file external_ids when versioning assistants

Description

This is a fix for the root cause of the multiple file ids being returned. We forgot to clear the vector_store_id from the tool resource, as well as the external_id from the files when being duplicated.
I added a management command to fix the existing versions where there are duplicates. Basically we clear those, then we update the assistant version at OpenAI's side to clear the vector stores there, then we sync the version manually.

User Impact

This fixes the multiple files returned issue
Demo

Logs from a local run
Evaluating Broken (id=9)
Looking at version 1 (id=10)
Vector store ids match! (vector_store_id=vs_99sBwgoOvc93VxdMMZ)
...clearning vector_store_id
...clearing file external ids
...removing existing vector store id at OpenAI
...syncing version with OpenAI
...syncing complete!
Version's new vector_store_id is vs_xUm4g9God6Fb6T5VTFs
Diff between original and new file ids: {'file-buOcVHVygsV0dU5rYb'}

Evaluating Fixed one (id=7)
Looking at version 1 (id=8)
Vector store ids do not match. Continuing...

Evaluating Versioning (id=5)
Looking at version 1 (id=6)
Vector store ids do not match. Continuing...

Docs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:white_check_mark: All tests successful. No failed tests found.
Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!

🚨 Try these New Features:

JS Bundle Analysis - Avoid shipping oversized bundles

I added a test to instill a bit more confidence in the command


evcc docker v.0.121.0 doesn't work after update - ui frozen

Describe the bug
Looks like there is not detection of current values anymore. All numbers are frozen, no change.
Connected car wasn't detected as well.
I'm using evcc since some month ago with no problems after container updates. No config change from my site.
Steps to reproduce

Restart via ui help menu
Container restart

...
Configuration details
/app # evcc --log debug
[main  ] INFO 2023/10/14 17:36:44 evcc 0.121.0
[main  ] INFO 2023/10/14 17:36:44 missing config file - switching into demo mode
[main  ] INFO 2023/10/14 17:36:44 starting ui and api at :7070
[db    ] INFO 2023/10/14 17:36:44 using sqlite database: /root/.evcc/evcc.db
[site  ] WARN 2023/10/14 17:36:44 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower
[site  ] WARN 2023/10/14 17:36:44 vehicle 'blauer e-Golf' does not support automatic detection
[site  ] WARN 2023/10/14 17:36:44 vehicle 'grüner Honda e' does not support automatic detection
[site  ] WARN 2023/10/14 17:36:44 vehicle 'schwarzes VanMoof' does not support automatic detection
[site  ] WARN 2023/10/14 17:36:44 vehicle 'Wärmepumpe' does not support automatic detection
[site  ] INFO 2023/10/14 17:36:44 site config:
[site  ] INFO 2023/10/14 17:36:44   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/10/14 17:36:44     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/10/14 17:36:44     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/10/14 17:36:44     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2023/10/14 17:36:44   vehicles:
[site  ] INFO 2023/10/14 17:36:44     vehicle 1: range ✓ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2023/10/14 17:36:44     vehicle 2: range ✓ finish ✗ status ✓ climate ✗ wakeup ✗
[site  ] INFO 2023/10/14 17:36:44     vehicle 3: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2023/10/14 17:36:44     vehicle 4: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2023/10/14 17:36:44     vehicle 5: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[lp-1  ] INFO 2023/10/14 17:36:44 loadpoint 1:
[lp-1  ] INFO 2023/10/14 17:36:44   mode:        pv
[lp-1  ] INFO 2023/10/14 17:36:44   charger:     power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/10/14 17:36:44   meters:      charge ✓
[lp-1  ] INFO 2023/10/14 17:36:44     charge:    power ✓ energy ✗ currents ✗
[lp-2  ] INFO 2023/10/14 17:36:44 loadpoint 2:
[lp-2  ] INFO 2023/10/14 17:36:44   mode:        off
[lp-2  ] INFO 2023/10/14 17:36:44   charger:     power ✗ energy ✗ currents ✗ phases ✓ wakeup ✗
[lp-2  ] INFO 2023/10/14 17:36:44   meters:      charge ✓
[lp-2  ] INFO 2023/10/14 17:36:44     charge:    power ✓ energy ✗ currents ✗
[lp-1  ] DEBUG 2023/10/14 17:36:44 phase timer inactive
[lp-1  ] DEBUG 2023/10/14 17:36:44 pv timer inactive
[lp-1  ] DEBUG 2023/10/14 17:36:44 guard timer inactive
[lp-1  ] INFO 2023/10/14 17:36:44 vehicle updated: unknown -> blauer e-Golf
[lp-1  ] DEBUG 2023/10/14 17:36:44 set target soc: 90
[js-shared] DEBUG 2023/10/14 17:36:44 state: {"batterySoc":55,"batterypower":-750,"gridpower":-1000,"loadpoints":[{"chargepower":0,"enabled":true,"maxcurrent":6,"phases":1,"vehicleSoc":62},{"chargepower":0,"enabled":false,"maxcurrent":0,"phases":3,"vehicleSoc":22}],"pvpower":5000,"residualpower":500}
[lp-1  ] DEBUG 2023/10/14 17:36:44 max charge current: 6A
[lp-2  ] DEBUG 2023/10/14 17:36:44 phase timer inactive
[lp-2  ] DEBUG 2023/10/14 17:36:44 pv timer inactive
[lp-2  ] DEBUG 2023/10/14 17:36:44 guard timer inactive
[lp-2  ] INFO 2023/10/14 17:36:44 vehicle updated: unknown -> weißes Model 3
[lp-2  ] DEBUG 2023/10/14 17:36:44 set target soc: 75
[main  ] FATAL 2023/10/14 17:36:44 could not open port- check that evcc is not already running (listen tcp :7070: bind: address already in use)
[site  ] WARN 2023/10/14 17:36:44 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval

Log details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: <IP_ADDRESS> # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: 983af8346171763d3616c809d127e6cd8a1d216dea12736a7af4cabccc5f8922

# interval: 45s # control cycle interval

sponsortoken: trallala

meters:
- type: template
  template: solarwatt
  usage: grid
  host: <IP_ADDRESS>
  name: grid1
- type: template
  template: solarwatt
  usage: pv
  host: <IP_ADDRESS>
  name: pv2
- type: template
  template: solarwatt
  usage: battery
  host: <IP_ADDRESS>
  name: battery3

chargers:
- type: template
  template: pulsarplus
  name: wallbox4
  stationid: PulsarPlus
  connector: 1
  connecttimeout: 5m
  timeout: 2m

loadpoints:
- title: Garage
  charger: wallbox4
  mode: pv
  vehicle: my_car
  phases: 3
  mincurrent: 6
  maxcurrent: 16
  resetOnDisconnect: true

#vehicles:
#  - name: my_car
#    type: mercedes
#    title: Mercedes GLC
#    phases: 2
#    capacity: 11
#    clientId: trallala
#    clientSecret: trallala
#    vin: trallala

vehicles:
  - name: my_car
    type: template
    template: offline
    title: GLC
    capacity: 11

site:
  title: Frank-Home
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3
# residualPower: 100

What type of operating system are you running?
Docker container
Version
0.121.0

[main  ] INFO 2023/10/14 17:36:44 missing config file - switching into demo mode

evcc uses the correct config file, see startup log:
[main  ] INFO 2023/10/14 18:04:45 evcc 0.121.0
[main  ] INFO 2023/10/14 18:04:45 using config file: /evcccfg/evcc.yaml
[main  ] INFO 2023/10/14 18:04:45 starting ui and api at :7070
[db    ] INFO 2023/10/14 18:04:46 using sqlite database: /root/.evcc/evcc.db
[PulsarPlus-1] DEBUG 2023/10/14 18:04:46 waiting for chargepoint: 5m0s
[ocpp  ] DEBUG 2023/10/14 18:05:17 charge point connected: PulsarPlus
[site  ] WARN 2023/10/14 18:05:21 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower
[site  ] INFO 2023/10/14 18:05:21 site config:
[site  ] INFO 2023/10/14 18:05:21   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/10/14 18:05:21     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2023/10/14 18:05:21     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2023/10/14 18:05:21     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2023/10/14 18:05:21   vehicles:
[site  ] INFO 2023/10/14 18:05:21     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[lp-1  ] INFO 2023/10/14 18:05:21 loadpoint 1:
[lp-1  ] INFO 2023/10/14 18:05:21   mode:        pv
[lp-1  ] INFO 2023/10/14 18:05:21   charger:     power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/10/14 18:05:21   meters:      charge ✗
[lp-1  ] DEBUG 2023/10/14 18:05:21 phase timer inactive
[lp-1  ] DEBUG 2023/10/14 18:05:21 pv timer inactive
[lp-1  ] DEBUG 2023/10/14 18:05:21 guard timer inactive
[lp-1  ] INFO 2023/10/14 18:05:21 vehicle updated: unknown -> GLC
[site  ] WARN 2023/10/14 18:05:21 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2023/10/14 18:05:21 ----
[lp-1  ] DEBUG 2023/10/14 18:05:21 charge power: 0W
[site  ] DEBUG 2023/10/14 18:05:22 pv power: 0W
[site  ] DEBUG 2023/10/14 18:05:22 battery soc: 95%
[site  ] DEBUG 2023/10/14 18:05:22 battery power: 557W
[site  ] DEBUG 2023/10/14 18:05:22 grid power: 0W
[site  ] DEBUG 2023/10/14 18:05:23 site power: 557W

This is not what your issue shows. Check your config, clarify issue, open clean report.

Closed #10318 as completed.

--
Reply to this email directly or view it on GitHub:
https://github.com/evcc-io/evcc/issues/10318#event-10654612476
You are receiving this because you authored the thread.

Message ID: ***@***.***>


update uninstall instructions of centos and fix a bad format

Signed-off-by: Yanqiang Miao<EMAIL_ADDRESS>

Deploy preview ready!
Built with commit 74a73fb8b4b1532b5b3255394f72847082889ce1
https://deploy-preview-767--docker-docs.netlify.com

Thanks, @miaoyq :)


Root causing protonj "no current delivery"

Background
Two customer tickets reported that the ProtonJ error "no current delivery" appeared in the logs, but when it happened in the lower layer, it activated a code path in the upper layer that triggered a reliability issue; this-pr addressed it.
This ticket is created so that we can focus on ProtonJ error "no current delivery" .
Root causing
As part of this investigation, we learned that it is possible that the ProtonJ object state can be mutated (e.g disposed) after the "scheduling" of work to the message-pump but before the actual "execution" of the work.
Sketching the control flow, it looks like the reason for "no current delivery"  is such a mutation; the flow appears to be below -

ProtonJ Receiver received a delivery. It updated its _current pointer to refer to this delivery then handed it over to ReceiveLinkHandler.
ReceiveLinkHandler enqueues the delivery to deliveries-Flux.
The async-chain attached to deliveries-Flux emits the delivery to ReactorReceiver.
The ReactorReceiver "schedule" a work to message-pump thread to decode this delivery.
The async-chain is waiting asynchronously for the Sink to complete. The completion happens only when scheduled work in 4 "executes" in the future.
The service traffic closed the amqp-receive-link, inturn frees the ProtonJ Receiver using message-pump thread. Note: the user-work in 4 and proton-j work in 6 does not execute strictly in FIFO order (two different pipes drive it), but the serial execution is guaranteed.
As part of freeing the ProtonJ Receiver, the ProtonJ library frees the delivery (that 4 refers to), settling the delivery and advancing the _current pointer. The _current become null.
ReceiveLinkHandler emits completion-event to deliveries-Flux, but it gets deferred because the Sink for the last event (5) is yet to be complete.
Work scheduled in 4 executes, but since _current is null and not the one the work is referring to, ProtonJ throws "no current delivery"

The exception in 9 goes to global error handling as an unhandled exception. Three 3 issues -
a. The Sink in 5 never errored
b. Hence the completion-event in 8 never emits (because queued after a)
c. The unhandled exception forces the parent amqp-connection to close
The good thing is, there is no one downstream waiting to react to the "terminal event" from a (or b) to happen. But c is concerning because the closure of one amqp-receiver-link combined with the race resulted in amqp-connection to close, which means it causes all other healthy amqp-receiver-links in the same amqp-connection to disconnect from service.
Fix
Again fix is simple as this ticket, i.e. do a deferred check for disposal of the Receiver so that the side effect is limited to that specific Receiver and not bypassed to the parent connection.
References
The customer tickets - https://github.com/Azure/azure-sdk-for-java/issues/24575 and https://github.com/Azure/azure-sdk-for-java/issues/26975

Adding log entries corresponds to the above description -
Service closing receive link that dispose the ReactorReceiver
INFO  6 --- [tor-executor-15] c.a.c.a.i.handler.ReceiveLinkHandler     : onLinkRemoteClose connectionId[MF_30ffff_1633678666625] linkName[0_85414c_1633678666626], errorCondition[null] errorDescription[null]
INFO  6 --- [tor-executor-15] c.a.c.a.i.handler.ReceiveLinkHandler     : connectionId[MF_30ffff_1633678666625] linkName[0_85414c_1633678666626] state[ACTIVE] Local link state is not closed.
DEBUG 6 --- [tor-executor-15] c.a.c.a.implementation.ReactorReceiver   : connectionId[MF_30ffff_1633678666625] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0] linkName[0_85414c_1633678666626] State CLOSED
DEBUG 6 --- [tor-executor-15] c.a.c.a.implementation.ReactorReceiver   : connectionId[MF_30ffff_1633678666625] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0] linkName[0_85414c_1633678666626] Freeing resources.
DEBUG 6 --- [tor-executor-15] c.a.c.a.i.handler.ReceiveLinkHandler     : connectionId[MF_30ffff_1633678666625], entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0], linkName[0_85414c_1633678666626] Could not emit deliveries.close when closing handler.
INFO  6 --- [tor-executor-15] c.a.c.a.implementation.ReactorSession    : linkName[0_85414c_1633678666626] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0]: Complete. Removing receive link.
INFO  6 --- [tor-executor-15] c.a.m.e.i.AmqpReceiveLinkProcessor       : linkName[0_85414c_1633678666626] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0] Receive link endpoint states are closed. Requesting another.
INFO  6 --- [tor-executor-15] c.a.m.e.i.AmqpReceiveLinkProcessor       : Requesting a new AmqpReceiveLink from upstream.
INFO  6 --- [tor-executor-15] c.a.m.e.i.AmqpReceiveLinkProcessor       : linkName[0_85414c_1633678666626] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0]. Setting next AMQP receive link.
INFO  6 --- [undedElastic-24] c.a.m.e.i.AmqpReceiveLinkProcessor       : linkName[0_85414c_1633678666626] entityPath[projectname-ingest/ConsumerGroups/ingest/Partitions/0] Receive link endpoint states are closed. Requesting another.
...
DEBUG 6 --- [tor-executor-15] c.a.c.a.i.handler.ReceiveLinkHandler     : onLinkLocalClose connectionId[MF_30ffff_1633678666625], linkName[0_85414c_1633678666626], errorCondition[null], errorDescription[null]
INFO  6 --- [tor-executor-15] c.a.c.a.i.handler.ReceiveLinkHandler     : onLinkFinal connectionId[MF_30ffff_1633678666625], linkName[0_85414c_1633678666626]

Work on ReactorReceiver trying to use the Delivery resulting ProtonJ ISE(no current delivery)
WARN  6 --- [tor-executor-15] c.a.c.a.implementation.ReactorExecutor   : connectionId[MF_30ffff_1633678666625], message[Unhandled exception while processing events in reactor, report this error.]
java.lang.IllegalStateException: no current delivery

org.apache.qpid.proton.engine.HandlerException: java.lang.IllegalStateException: no current delivery
	at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:112)
	at org.apache.qpid.proton.engine.impl.EventImpl.delegate(EventImpl.java:129)
	at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:114)
	at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324)
	at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291)
	at com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:86)
	at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68) ~[reactor-core-3.4.8.jar!/:3.4.8]
	at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28) ~[reactor-core-3.4.8.jar!/:3.4.8]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:829) ~[na:na]
Caused by: java.lang.IllegalStateException: no current delivery
	at org.apache.qpid.proton.engine.impl.ReceiverImpl.recv(ReceiverImpl.java:87)
	at com.azure.core.amqp.implementation.ReactorReceiver.decodeDelivery(ReactorReceiver.java:242)
	at com.azure.core.amqp.implementation.ReactorReceiver.lambda$new$0(ReactorReceiver.java:74)
	at com.azure.core.amqp.implementation.handler.DispatchHandler.onTimerTask(DispatchHandler.java:34)
	at com.azure.core.amqp.implementation.ReactorDispatcher$WorkScheduler.run(ReactorDispatcher.java:184)
	at org.apache.qpid.proton.reactor.impl.SelectableImpl.readable(SelectableImpl.java:118)
	at org.apache.qpid.proton.reactor.impl.IOHandler.handleQuiesced(IOHandler.java:61)
	at org.apache.qpid.proton.reactor.impl.IOHandler.onUnhandled(IOHandler.java:390)
	at com.azure.core.amqp.implementation.handler.CustomIOHandler.onUnhandled(CustomIOHandler.java:41)
	at org.apache.qpid.proton.engine.BaseHandler.onReactorQuiesced(BaseHandler.java:87)
	at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:206)
	at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108)
	... 12 common frames omitted

ISE localized to one ReactorReceiver causing global effect on the connection
INFO  6 --- [tor-executor-15] c.a.c.a.i.ReactorConnection              : onConnectionError connectionId[MF_30ffff_1633678666625], hostName[projectname-eval.servicebus.windows.net], message[Starting new reactor], error[no current delivery, TrackingId: 990db1f5-ff19-41ac-ad4b-27d7485828c5, at: 2021-10-10T10:10:14.855479Z[Etc/UTC], errorContext[NAMESPACE: projectname-eval.servicebus.windows.net. ERROR CONTEXT: N/A]]
DEBUG 6 --- [tor-executor-15] c.a.c.a.i.ReactorConnection              : onReactorError connectionId[MF_30ffff_1633678666625], hostName[projectname-eval.servicebus.windows.net]: Disposing.
INFO  6 --- [tor-executor-15] c.a.c.a.i.ReactorConnection              : connectionId[MF_30ffff_1633678666625] signal[onReactorError: com.azure.core.amqp.exception.AmqpException: no current delivery, TrackingId: 990db1f5-ff19-41ac-ad4b-27d7485828c5, at: 2021-10-10T10:10:14.855479Z[Etc/UTC], errorContext[NAMESPACE: projectname-eval.servicebus.windows.net. ERROR CONTEXT: N/A], isTransient[false], initiatedByClient[false]]: Disposing of ReactorConnection.
INFO  6 --- [tor-executor-15] c.a.m.e.i.EventHubConnectionProcessor    : namespace[projectname-eval.servicebus.windows.net] entityPath[projectname-ingest]: Channel is closed. Requesting upstream.
DEBUG 6 --- [tor-executor-15] c.a.c.a.i.ReactorConnection              : connectionId[MF_30ffff_1633678666625] Was already closed. Not disposing again.
INFO  6 --- [tor-executor-15] c.a.m.e.i.EventHubConnectionProcessor    : namespace[projectname-eval.servicebus.windows.net] entityPath[projectname-ingest]: Connection not requested, yet. Requesting one.


AWS Metadata required when datacenter == Amazon

Currently, we let users that implement this module define all the required metadata that they want to register with Eureka. This works fine if datacenter is set to anything other than Amazon, like if you were using MyOwn, for example. If you do set dataCenterInfo.name to Amazon, the Eureka server actually requires that you post a bunch of AWS metadata to it. See the XSD.
While we could just assume users will implement the code to go and fetch all the required metadata, I think it would be better to build that into the client and make it configurable. In any case it'll match what the Java client does, and users can turn it off if they would prefer to handle things in their own code.

Good catch, definitely should be in the module.

FWIW this might be considered a breaking change, because if you implemented the module previously, none of the metadata would be sent by default.


Gemxd 19

Changes proposed in this pull request
Cleaning the index corresponding to hosted but discarded bucket data
Patch testing
A dunit has been added which reliably reproduces the count problem.
Other PRs
(Does this change required changes in other projects- snappyData, spark, spark-jobserver, aqp? Add the links of PR of the other subprojects that are related to this change)

good for merge -- some minor comments


Update for ocl-wrapper changes in conda package

The conda package on conda-forge already includes the ocl wrappers as needed for linux and macOS:
https://github.com/conda-forge/devbio-napari-feedstock/pull/17
So specifically installing the wrappers isn't needed anymore.
And if pip installing, then the wrapper isn't needed because khronos-opencl-icd-loader won't be installed.
So this section isn't needed anymore.

Thanks, @psobolewskiPhD !

Thanks @psobolewskiPhD !


Bug: Wallet Account Changes Not Updating Properly

Description:
We've noticed a problem with how the wallet handles account changes.
Steps to Reproduce:
Open the bridge.
Connect Bearby wallet.
Change your account address.
Check if the address updates on the bridge UI.
Change the address again.
Notice that the address doesn't update on the UI this time.

Expected Behavior:
The account address should update on the UI every time it's changed in the wallet.
Actual Behavior:
The address updates only once after a change. Subsequent changes don't reflect on the UI.
Additional Context:
Bug seems to be coming from :  web3.wallet.account.subscribe((base58) => {console.log(base58)};
This issue affects user experience as the UI fails to update with account changes.
A temporary workaround is to reload the page, but it doesn't fix the problem.

Thanks for your issue i will check it.

thanks for your issue, it seems you are right, i will fix it in new version)))


gulp build failure

Running gulp build gives me the following. I'm using the install/setup instructions in the README.
module.js:340
    throw err;
    ^

Error: Cannot find module 'mozaik/gulpfile'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:289:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/path/to/gulpfile.js:5:10)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)

@andyfleming, you used the yeoman generator ?

Yes (if I recall correctly).
I tried to just follow the directions in the README.
I was able to clone that other example repository to get things working but the yo workflow didn't work.

I've fixed a problem with the generator (v1.0.1)

@andyfleming, I close this issue as it seems to work now, feel free to re-open if it doesn't work for you. And thanks for the feedback!


locales->ru->translations->blood-type

locales->ru->translations->blood-type missing translations

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @la83lynx.
Could you create a single PR with all the Russian translations? Another thing: remember to use semantic commit for the commit message.
Example:
chore(i18n): adds Russian lang for bloodtype


[Feat]Add a functionality to start shopping button

Description
it would be nice if we add the functionality to the start shopping button ,instead reloading that page it self
i would like to redirect it to the our shops page
Screenshots
https://github.com/user-attachments/assets/2eb017b3-7320-464b-aa02-e956430fc120
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hey @Prudhvi-232, sorry for the late reply. I’ve been a little busy due to my health condition. We have converted the entire code to Next.js and Tailwind CSS for better backend integration. You raised a good issue, but it was based on the old HTML and CSS version. We’ve moved everything to Next.js and Tailwind CSS. Please look into that, and don’t forget to join our Discord Serverfor the latest website announcements and features.

And also please give Star us ⭐

Please don't be discouraged. I will close the issue for now, but you can raise a new one that is truly needed for our website. Thank you.


Add new functions to ensure global arch-specific values are inherited properly

Codecov Report

Merging #12 into master will increase coverage by 0.32%.
The diff coverage is 65.51%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   82.02%   82.35%   +0.32%
==========================================
  Files           7        7
  Lines         434      442       +8
==========================================
+ Hits          356      364       +8
  Misses         54       54
  Partials       24       24

Impacted Files
Coverage Δ

manifest/rfc2822.go
77.06% <65.51%> (+0.71%)
:arrow_up:

Continue to review full report at Codecov.

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


N3 parse support

hello @Tpt , thanks for your work.
It would be great if rio supports n3 parser. n3 is also the format chosen for n3-patch format, by solid spec, to patch solid rdf resources.
Thanks again.

Hi! thank you! It's great idea. I believe this parser should implement the community group spec and return generalized quads similarly to the current "GTrig" parser. Is it what you have in mind?

Yes, indeed _/\_. Other advanced features of n3 for rule -systems are not that required to be modelled now. just generalized-quads support is great enough

Hi @damooo! That's a great question. A possible way is to parse Cited Formulae as RDF 1.1 named graph using a new blank node as graph identifier. It's what other parsers like N3.js are doing.

thanks @tpt,
Is it possible to have that quoted-graph syntax-extension be supported in gtrig parser, as a blank named graph (By default disabled)?

@damooo It's definitely doable but with a bit of work. I would prefer to implement a clean N3 parser instead.

@Tpt ,
That would be much more great if it is considered _/\_.

Hello @Tpt ,
I would be soon open sourcing a modular rust implementation of solid server, that will allow running solid in wide range of contexts. And makes it possible to convert solid web apps into native apps using rust + tauri, etc.
But that requires N3 support for PATCH operation over a graph using nn3-patch as defined in protocol. solid heavily uses that, and all most all solid apps including solid-os make heavy use of it. Thus servers need parser, and any rust clients need a serializer. Solid is major standard for practical rdf world. It would be very useful if rust has basic tools to work against it.
I am quite new to parsing technlogies. If you can guide me little on adapting GTrig parser for N3 parser as mentioned above, i could give it a try.

I would be soon open sourcing a modular rust implementation of solid server, that will allow running solid in wide range of contexts. And makes it possible to convert solid web apps into native apps using rust + tauri, etc.

It's amazing! Congratulation!

I am quite new to parsing technlogies. If you can guide me little on adapting GTrig parser for N3 parser as mentioned above, i could give it a try.

If you prefer I am currently moving forward with the new parser able to support both sync and async I talked about in #98.
I have something working for NTriples that is nearly twice as fast the current parser. I plan to add Turtle, TriG and N3 support to it. So if you are ok to wait a few weeks, I hope to have something working by then.
If not, copy/pasting the GTrig parser code and hacking on top of it should do the work. The rio_turtle crates work by parsing the input byte by byte using the LookAheadByteReader struct. If you manage to understand this struct then I hope the code won't be to hard to understand.
About formatting, Turtle is a subset of N3 so the Turtle serializer should output something compatible with N3.

Sincere sorry for this nagging @Tpt .
If you don't take it as bad, can you give approximate ETA for N3, so that i will decide if i have to hack till then.
Thank you.

If you don't take it as bad, can you give approximate ETA for N3, so that i will decide if i have to hack till then.

Sorry, I missed your message. I don't know, something like a month or two. So if you want something "soon" writing a quick&dirty parser might be the way to go.

Thanks @Tpt ,
I feared it may involve some complex parsing expression graammers, etc. But GTrig parser is clear enough, that i adapted it to simple N3 quick enough. Thanks for great work.

It's been a while since this was last discussed - and it seems like N3 support hasn't landed. I'd love to know if the idea was abandoned altogether or if building on top of rio might still be possible here at some point (I'm working on Solid support for a predominantly Rust-based project)?

@Gearme Yes, it has been a while, sadly. The project is not abandonned but not high priority so it's moving slowly (this work is not funded at all so moves forward on my free time). I have a prototype working in the new-turtle branch. All tests but one in the N3 test suite works.
To use it add to your Cargo.toml
oxttl = { git = "https://github.com/oxigraph/oxigraph", branch = "new-turtle" }

And then a code like:
use use oxttl::n3::{N3Event, N3Parser};

for q in N3Parser::builder()
        .with_base_iri(BASE_IRI_IF_USEFUL)?
        .with_read(FILE_CONTENT)
    {
        match q {
          Ok(N3Event::Quad(quad)) => /* process quad, the "graph name" part might be a blank node identifying an N3 formula or default graph if not in a formula */
           Err(e) => /* error */
        }
    }

I have a prototype working in the new-turtle branch

@Tpt Where is this new-turtle branch? I can't find it :(

Although very very late, released solid server at Manas. it uses customized n3 parser as of now. Will be great to have standard one. Thanks again for the support @Tpt.

I finally cut a new release of my N3 parser: https://docs.rs/oxttl/0.1.0-alpha.1/oxttl/n3/struct.N3Parser.html

That's great. _/\_


Module fails if subnet uses default "main" routing table

Describe the Bug
If one of the subnets in one of the VPCs is using the default "main" routing table, the module fails.
Steps to Reproduce
Steps to reproduce the behavior:

Create a new VPC
Create new subnets in the VPC without associating route tables with them
Use the VPC as the "accepter"
See error

Error: query returned no results. Please change your search criteria and try again

  on .terraform/modules/vpc_peering/accepter.tf line 64, in data "aws_route_table" "accepter":
  64: data "aws_route_table" "accepter" {

Additional Context
This bug was introduced by #44 which incorporated #31 but still did not really fix #30.
I propose eliminating the option to filter subnets because it never really worked. If someone wants it back, they can submit a PR to implement it properly.
Problems with filtering by subnet
Problem 1: Finding the route tables to modify
Sub-problem 1A: Looking up the route table for a subnet
You cannot find the route table for a subnet via
data "aws_route_table" "subnet" {
  subnet_id = local.subnet_id
}

because this will throw an error if the subnet does not have an associated route table and is instead using the default "main" table. That is the source of this bug.
Because there is no way to make this conditional, we simply cannot use data "aws_route_table".
Sub-problem 1B: Looking up the subnet for a route table
You could try looking up all the route tables and filtering them by associated subnets, but

this is hard, because you have to treat the "main" route table specially and match it to the subnets that have no associated route table, and
what do you do if you one route table is associated with both an included and an excluded subnet?

Conclusion: you might as well add routes to all the route tables, because you cannot promise better restrictions
After all, the entire VPC might have only one, default route table.
Problem 2: Why are we looking up subnets by tag, anyway?
The only meaningful restriction we can make is to limit routing to some portion of the VPC's CIDR, so we might as well pass explicit CIDRs for each VPC and just route those in all routing tables. It is not at all clear that selecting the CIDRs by subnet tag is more convenient than explicitly specifying them (or having the root module look them up any way it wants to).

Any workaround for this?

Any workaround for this?

You can explicitly associate subnets with default route table in console. It worked for me.

I've used accepter_subnet_tags and it's working fine for me.
https://github.com/cloudposse/terraform-aws-vpc-peering-multi-account/issues/30


Write Unit Tests for Person Detection Script

Create unit tests to validate:
Loading of YOLOv5 model.
Processing of input video frames.
Detection and bounding box drawing.
Saving of output frames.

Resolved #9


Why are "extrinsics" presented in the train Method?

As mentioned in the paper, the NoPoSplat is a pose free 3dgs, but why extrinsics are needed in training_step in model_wrapper.py?
def training_step(self, batch, batch_idx):
...
gaussians = self.encoder(batch["context"], self.global_step, visualization_dump=visualization_dump)
output = self.decoder.forward(
gaussians,
batch["target"]["extrinsics"],    # here, it seems that we need extrinsics from the training dataset
batch["target"]["intrinsics"],
batch["target"]["near"],
batch["target"]["far"],
(h, w),
depth_mode=self.train_cfg.depth_mode,
)
these confused me

I get it now.
The proposed approach needs GT extrinsics to train a NN model on large dataset.
After trained, the model predicts gaussians without extrinsics for any given scenes.
This approach really differs from previous 3DGSs.


Multiple variable assignments

Up till now, monkey doesn't support multiple variable assignments:
a, b, c = 1, 2, 3

Maybe in the next release, i'll add this feature to the monkey language.

Add leables

Now, i've completed the multiple variable assignments.
You could do it like below:
let a, b, c = 1, 2, 3

Note: When you do multiple variable assignments, you must use the let keyword. Below code is not correct:
//Not correct
a, b, c = 1, 2, 3

When not using the let keyword, you could only assign one variable at a time:
//Correct
a = 1
b = 2
c =3


(maint) Do not build stable or testing

Currently, we are being redundant with which debian platforms we are
building. Debian has releases that correspond to certain names that
indicate where they are in the release lifecycle. For instance, at this
moment, Debian Jessie is the same this as Debian Stable. As they
progress the different releases through their respective lifecycles, the
codename corresponding to the lifecycle stage changes. For instance,
currently, Debian Testing corresponds to Debian Stretch. At some point,
this platform will drop, and become the new Debian Stable, and Debian
Jessie will become the new Debian Oldstable. Rather than continually
updating our packages to deal with these changes every time the Debian
release cycle is moved forward, we will only be building packages based
on Codename (i.e., Debian Wheezy).
In order to follow these new standards, this commit removes both stable
and testing from the build targets. That, and Facter 2.x will not be
released on either Debian Jessie or Debian Stretch. These two platforms
instead will see releases in the new puppet-agent packages.

@kylog this is for the Facter 2.4.4. release. Let me know if I need to retarget at a different branch

CLA signed by all contributors.


fix: introduce dedicated lock object

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[X] I ensured that the PR title is good enough for the changelog.
[X] I labeled the PR.

Description
The lock shouldn't be a variable which will have another reference assigned to it within the critical area it is supposed to protect. Accessing the methods of the lock object or changing the values of its fields is allowed, but not changing the reference value of the lock itself.
That said, this is why this code in BuildingBlocks.Infrastructure.Persistence.BlobStorage.AzureStorageAccount.AzureStorageAccountContainerClientFactory for example yields no warnings:
        lock (_containerClients)
        {
            if (_containerClients.TryGetValue(containerName, out container))
                return container;

            var newContainer = CreateContainerClient(containerName);

            _containerClients.Add(containerName, newContainer);

            return newContainer;
        }

@NikolaVetnic Remember to fix the PR title before you mark the PR as ready for review

@NikolaVetnic Remember to fix the PR title before you mark the PR as ready for review

Thank you for the reminder.


cxx-build: symlink headers to GENERATED_HEADER_DIR

Symlink (or copy on Windows) generated headers to a directory specified by the GENERATED_HEADER_DIR environment variable, if this variable is set. This makes cxx-build usable by C++ build systems if they set GENERATED_HEADER_DIR before calling cargo and add it to their include paths. This is a better solution than the CLI tool for several reasons:

Don't need to build/distribute/install a separate program
Saves build time because cxx crates are not built redundantly for the CLI tool and the macro
No risk of version mismatches between CLI tool and cxx macro crate
One library crate that uses cxx can be usable in applications built either with Cargo or a C++ build system

Fixes https://github.com/dtolnay/cxx/issues/462

Note that if the cxx library has hand written C++ headers, its build script is responsible for copying those to GENERATED_HEADER_DIR (alternatively, the C++ build system could add the path to the crate's source code to its include paths, but I wouldn't recommend that).

PR to make use of this with CMake using Corrosion: https://github.com/corrosion-rs/corrosion/pull/247

Downstream code must only be allowed to import from A's headers.

If crate C can use crate A's headers, why shouldn't external C++ code?

If either crate uses CFG.exported_header_dirs, CFG.exported_header_prefixes, or CFG.exported_header_links, the content of those directories would not be reflected in GENERATED_HEADER_DIR.

Right, that would be up to build scripts to handle if they need that. Or alternatively I could put more work into this to copy/symlink headers from those paths into GENERATED_HEADER_DIR.

Corrosion can build this crate with a CXX environment variable that points to a program that parses and extracts the include-directories from the compiler command line arguments.

That would be a very convoluted workaround.

If CMake depends on crate A which depends on crate B which depends on crate C, where A and C involve cxx-build

Oh, are you talking about a case where crate B uses crate A for bindings to some C++ library, but crate B doesn't re-export anything from crate A? In that case, you're right, a single environment variable might have unintended consequences. This could be overcome by including the crate name in the environment variable name, for example GENERATED_HEADER_DIR_my_cxx_library

If either crate uses CFG.exported_header_dirs, CFG.exported_header_prefixes, or CFG.exported_header_links, the content of those directories would not be reflected in GENERATED_HEADER_DIR.

This applies equally to the cxxbridge CLI tool.

I don't think it is sufficient or necessary for handling cxx headers, so I'll close the PR.

Please don't dismiss use cases outside of what you have personally encountered. The existing solution with cxxbridge is cumbersome, confusing (consider that all but one of the CMake examples listed in the documentation have a build.rs using cxx_build in addition to cxxbridge), and brittle. Quite a few users have communicated (#462, #949, #229) this. I'm not saying it can't work, but that getting it working requires a lot more work than it needs to and there's lots of room for the build process to go wrong.

my work codebase using Buck has several hundred binding crates successfully built on it.

(from https://github.com/corrosion-rs/corrosion/pull/244#issuecomment-1295232222)
Clearly you have more experience with complex dependency graphs involving cxx than I do. I'm glad you've pointed out pitfalls in my code, but I don't think that means the whole approach should be dismissed. I think we can come up with a mutually agreeable solution together if the discussion isn't shut down prematurely. If https://github.com/dtolnay/cxx/pull/1120#issuecomment-1295299586 isn't sufficient, perhaps some way could be added for symlinking/copying the generated headers to be opt-in for build scripts using cxx-build.


[Docs]: Reduce font size in Meshery REST API page

Notes for Reviewers
This PR fixes #10900
Reduced font size for the REST API documentation at https://docs.meshery.io/reference/rest-apis
Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit b982b50d00d3a5ad43369b25bfc3a4e79354785f at: https://663d499513e93262337cd406--meshery-docs-preview.netlify.app

🚀 Preview for commit c8128802574dbbab508ac622728bf152ad6d7be4 at: https://663d4c16cb477366da996e19--meshery-docs-preview.netlify.app

Thank you, @jasonmokk 👍

@leecalcote Sure, I'll push that change as well!

🚀 Preview for commit c6140fd7eced2a43dba6965f00528468e552c1be at: https://663ec5ca5206567d6670472b--meshery-docs-preview.netlify.app

Hey @jasonmokk, let's discuss this on today's website meeting today at  7 AM CT. I am adding this as an agenda item. Please Join https://meet.layer5.io/websites if you are available during the meet.


Move term and md5 to the development dependencies

Hi,
If term and md5 are used only in the example, they shouldn’t probably be complied when building the package.  The pull request also updates md5.
Regards,
Ivan

I will test asap. thx


Updated About PAP Therapy section

Thanks @DanMobley! These changes have been merged into the 7-4-stable branch which should be live soon.

Merged in commit e8a9b94f62cb61dc985dc43f023c7ad34c0e1dff


sensors: no temperature compensation in HITL

Temperature compensation is not supported in HITL. Therefore, don't try
and fail. This basically removes the confusing error message that we get
in HITL.

Needs testing.

@dagar Will you test or are you looking for help?

I did a quick test in jmavsim HIL. @julianoes could you verify this solves your original problem in https://github.com/PX4/Firmware/pull/10017?

@dagar I did not see the error, so this resolves the problem for me. Thanks a bunch!


Is there an API for getting/deleting all resources or objects in a namespace using lable selector?

Something similar to
kubectl get all -l name=value or
kubectl delete all -l name=value

If you run those commands with -v9 flag, it should give you the rest call, and from there it should be straightforward to find the python client equivalent of it.


Question about changing image size

The problem I encountered is that I changed the train image size 512 in the yaml file to train model, and I also changed the test image size, but when I actually ran the testing, the image size of the test didn't change according to the settings in the yaml file, so I would like to ask if there is any error in this part of the content ?
As shown below, because the testing image size is defined in multi_scale_aug in the resize part, but multi_scale=False in test_dataset, so it doesn't do resize at all ?

That's correct, PIDNet only performs resizing if multi_scale is True. However I personally wouldn't call this in issue as I want to test my predictions on full size whatsoever. I'm currently training on a reduced scale, but am guessing that the model is correctly generalizing to the original size due to the training with multiple scales.
If you really wanted to test on downscaled versions of your dataset you would have to change the code.

Thank you for your reply !
I would like to ask about the training you tried on the reduced size, did
you try to test it on the same reduced size ?
I'm currently having problems with a significant drop in accuracy if I test
my predictions on the reduced size, providing some of my experimental data
in hopes of further discussion with you.
If you have any related experiments, hope you can share them with me.
Thank you !
[image: image.png]
Florian S. @.***> 於 2023年11月2日 週四 下午5:04寫道：

That's correct, PIDNet only performs resizing if multi_scale is True.
However I personally wouldn't call this in issue as I want to test my
predictions on full size whatsoever. I'm currently training on a reduced
scale, but am guessing that the model is correctly generalizing to the
original size due to the training with multiple scales.
If you really wanted to test on downscaled versions of your dataset you
would have to change the code.
—
Reply to this email directly, view it on GitHub
https://github.com/XuJiacong/PIDNet/issues/72#issuecomment-1790327254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A772QDVXT26ZJ7SB733RFCLYCNOYLAVCNFSM6AAAAAA6DF3D2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQGMZDOMRVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes, I actually did some testing on 50% prediction as well as using upscaling for full-scale predictions.
Using PIDNet and my highly imbalanced binary dataset, I was able to get 71.92% mIoU when evaluating the 50% downscaled predictions on the training I did at that 50% size (using the multi-scale option however). Using the authors' native full-scale approach, I could only get 70.48%, which was in line with my expectations. Using TDNet as a segmentation model (which doesn't use native full-scale predictions), I got the same 1-2% degradation when using full-scale predictions instead of the 50% predictions I trained it on.
Due to my limited ressources I couldn't try full-scale training so your findings are still quite interesting for me!


Make reload available when DevTools are open

[x] always show toggle DevTools in window menu
[x] show reload in development setup
[x] show reload in production app when DevTools are open

Related to #207

Assured Reload menu item is immediately available on opening dev-tools and disappears when tools are closed.


PermissionsEX Error

Fixed

Please be aware that when you resolve an issue, the correct thing to do is to use the "Close issue" button, not edit the contents of the original message.
(also PEX v1 is unsupported :p)


Make sure we support more than one GraphQL query

Take the query name from the query itself, if it's specified.  Otherwise the filename.

We do actually support more than one query file as input, but we require each to contain exactly one query.  That should be fixed, and we should take the query names as the top-level names unless otherwise specified.


can compare uuid

// Generate a v1 (time-based) id
uuid.v1(); // -> '6c84fb90-12c4-11e1-840d-7b25c5ee775a'

from doc it say this time based
can I compare tow ids to know which created first ?

Theoretically, yes. The first portion of the UUID is time encoded. You would just need to reverse it.
I can potentially add a function that does it for you, but it would be low priority compared to some other stuff I need to do.

Theoretically, yes. The first portion of the UUID is time encoded. You would just need to reverse it.
I can potentially add a function that does it for you, but it would be low priority compared to some other stuff I need to do.

Ok can u give me example in dart to compare?

Ok can u give me example in dart to compare?

I don't have the time right now to write that out for you. If I did, I would just implement it into the library.
Just take the first 7 bytes. Convert it to a long. Use the date time library to convert it to time. Do the same.for the other and compare. Or just compare the longs and see which one is bigger since they would be epoch time.

I don't have the time right now to write that out for you. If I did, I would just implement it into the library.
Just take the first 7 bytes. Convert it to a long. Use the date time library to convert it to time. Do the same.for the other and compare. Or just compare the longs and see which one is bigger since they would be epoch time.

ok


Provide a pipenv requirements mode that only considers pipfile.lock

Apologies if I've missed an existing feature request, I had a search through and couldn't find one.
Is your feature request related to a problem? Please describe.
The serverless-wsgi plugin generates a requirements.txt from pipfile, before installing those requirements. There are other tools that also rely on requirements.txt. But one limitation of requirements.txt vs. pipenv is that it doesn't provide any guarantees of sub-dependency versions.
If there were a pipenv requirements mode that would generate a requirements.txt file with all locked dependencies specified, then that would bridge the divide and allow us to ensure that the locked dependencies in pipfile.lock were used by these external tools.
Describe the solution you'd like
Much like pipenv sync only considers the pipenv.lock file, a new argument to pipenv requirements would make it generate a requirements.txt file from all the dependencies in pipfile.lock. I assume it would need to list the lowest level dependencies first in order to ensure that they didn't get installed twice which might happen if top level dependencies were listed first.

@mungojam My understanding is pipenv requirements was built to only consider the existing Pipfile.lock whereas the old install -r regenerated the lock file.

The readme only mentions pipfile when in the example so perhaps that is what needs some tweaking

@mungojam That could be, I just checked the implementation and in fact, the original feature requests and author wanted the requirements command to be generated from the lock file, and it simplified the implementation of the install and lock commands (still very complicated).


raft hostnames resolving to IP

Addresses https://github.com/github/orchestrator/issues/253
with this PR, orchestrator will resolve raft hostnames to IP addresses before handing over the details to the raft library.
This supports orchestrator configuration to specify hostnames rather than IP addresses.
cc @bbeaudreault

does not solve the problem completely but will help configuration. LGTM


Eggdrop Support

Hello,
I was able to connect latest stable Eggdrop (1.9.1) via xoxp string into irslackd. But im not unable join eggdrop on channel. Not even from partyline. When i simulated with same xoxp string irssi it worked. But bot is seem to be connected but is not able to join to any #channel - regardless if channel was static or dynamic from point of view of eggrop.
if it was dynamic - i could see that slack registered eggdrop's desire to join #test2 channel
from eggdrop:
.join #test2
New chan monitoring: #test2.
#test2 is now configured. I'll now try to join it.
Use .-chan to remove a chan (chan userlist will be deleted).
from irssi (via same xoxp)
17:54 -!- bot [] has joined #test
17:54 [Users #test2]
17:54 [ bot]
But eggdrop bot did not registered that he is on #channel
[19:23:20] #snowcube# status
I am bot, running eggdrop v1.9.1: 14 users (mem: 158k).
Online for 00:02 (background) - CPU: 00:00.06 - Cache hit: 50.0%
Configured with:
Admin: snowcube <email<EMAIL_ADDRESS>Config file: bot.conf
OS: Linux 4.9.0-9-amd64
Process ID: 12407 (parent 1)
Tcl library: /usr/share/tcltk/tcl8.6
Tcl version: 8.6.6 (header version 8.6.6)
Tcl is threaded.
TLS support is enabled.
TLS library: OpenSSL 1.0.2u  20 Dec 2019
IPv6 support is enabled.
Threaded DNS core (beta) is disabled.
Socket table: 20/100
Loaded module information:
Channels:  #test (trying), #general (trying), #test2 (trying)
Account tracking: Disabled
(Missing capabilities: use-354 extended-join account-notify)
Online as: bot!bot@irslackd (bot)
Connected to (null) [server.domain.com]:+6667 (connected for 00:02)
Active CAP negotiations: None
#test               : (not on channel)
#general            : (not on channel)
#test2              : (pending)
Eggdrop still does not recognize that he is joined channel. After restart he will claim that he is even in case of #test2 not on channel.
Could be irslackd modified that eggdrop would understood how to join (test of join on channel)? Could be fun using old tcl scripts into slack environment.
thanks.
snowcube

Hi @snowcube-ui. Thank you for the trip down Nostalgia Lane. I got some features working by hacking up irslackd, but eggdrop is still very confused. This will take some time.


Feat/add example webpage

[x] createRPCHook (or work around).
[ ] add Lerna config for example.

things to fix

Tendermint client is create differently from the way grpcwebClient is create => make compatible

methods will add Service or Query prefix unexpectedly => make it consistent
e.g: codegen/cosmos/auth/v1beta1/query.rpc.Query.ts
codegen/cosmos/tx/v1beta1/service.rpc.Service.ts

MsgClientImp type that get export from helper missing unary attribute
e.g: codegen/cosmos/rpc.tx.ts

(optional) some type cast/convert maybe need
e.g: codegen/cosmos/staking/v1beta1/staking.ts

optional, because rpc use createRPCQueryOption, we should add something like that for gprc-web as well.


New version: Hashicorp.Nomad version 1.8.0

Pull request has been created with komac v2.2.1 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\Hashicorp.Nomad__DefaultSource\nomad.exe returned exit code: 127
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\nomad.exe returned exit code: 127

(Automated response - build 885.)


Multiline Regex

Hello!
I'm trying to make multiline regex but it's not working. My expression is:  anything between @{ and @} (but not include @{ and @})
I try:
Header2: (?<=@\{)(?:.|\n|\r)*?(?=@\})
or
Header2: (?<=@\{)[\s\S]*?(?=@\})
does not work. Do you have any idea?
Thanks

It's tricky because you want to match @}} using a non-greedy repetition operator but as soon as the engine sees @} it will stop matching to satisfy the non-greedy criteria.I expect you could address it by making the match non-greedy and using balancing group definitions (which allow the engine to match nested expressions). See http://msdn.microsoft.com/en-us/library/bs2twtah.aspx#balancing_group_definition.

Hi Jesse, thanks for your anwser.
I tested many regex with multi-line and no one works, including C/C++/C# multi line comment (included on language folder)
/* (?: . | \r | \n)*? */
When I debug the code, I put a breakpoint at line 70 (Language.cs):
MatchCollection matches = m_regex.Matches(text);
and always "text" variable is only 1 line (when editing, is current line editing, when open file, all source was passed line per line).
I´m using lastest source code (v0.4)

Ahh, I had forgotten about this. It's a fundamental limitation of Linguist. Linguist is an Microsoft.VisualStudio.Text.Classification.IClassifier which is one of the simpler ways to extend studio, but in normal operation Linguist is called with spans of text covering one line at a time. And, as far as I can tell, there is no way for a classifier to get all of the text.


Replace winsock2 with cmath

In a macOS environment, winsock2 isn't available. The only lines of code that used winsock2 were in thirdParty_motion.cpp (lines: 384, 389, 394, 400, 404, 408) specifically using M_PI. Simply adding #include fixes that.

Merging into new branch for macOS changes.


Cannot load images with the latest submission of the master branch

Hi, could you please post the information of git log?
git log -5 --pretty=oneline

I' sure that it's a bug introduced by 2e62fd1e17bdc391ba5eece2ff95e4619676eac3, and was fixed by 02f941a5c7e0dfaead18215d67bcfe86eab08f7c.

Hi, could you please post the information of git log?
cd themes/hugo-theme-bootstrap
git log -5 --pretty=oneline

I ~am sure~ think that it's a bug introduced by 2e62fd1, and was fixed by 02f941a.

D:\WorkSpace\Webstorm\xuzhijvn.github.io\themes\hugo-theme-bootstrap>git log -5 --pretty=oneline
3b16d098e8cfe0201027e39e01f4bc7c3ded3841 (HEAD -> master, origin/master, origin/HEAD) Update _post.scss
02f941a5c7e0dfaead18215d67bcfe86eab08f7c Minor changes
b8b4d7c8f057d77f33f0c428269a0a9286d637c8 Update the example site
2e62fd1e17bdc391ba5eece2ff95e4619676eac3 Add support for page image resources
4239fbd44a9b034ccdab44f4d0510a31d719eccf Fix #197

Fixed by e620bca, sorry about that.

Fixed by e620bca, sorry about that.

thanks, your are the best, man


add fish labeler

About the PR
fish are friends not food
can be crafted using hand labeler and a carp plushie
not sure if i should put in Prototypes/Nyanotrasen since 1. not really psionic and 2. it modifies things present in upstream and uses same components as hand labeler
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Added a craftable fish labeler for your fish labeling needs

dont think ci failure is related

it doesn't matter if it's psionic and it does not modify anything upstream I can see? this should be under nyano prototypes.

modifies upstream as in it changes tags, carp plushie, hand labeler but yeah ill move it

tags are kind of an exception because we keep them all in 1 file to stop collisions

so is anything else needed

no

ci just magically passed all checks ok???


Ridy

This is ONLY used for reporting bugs.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

Context (Environment)

Detailed Description

Possible Implementation

Content is not filled.


ajax problem

HI
code is as follows:
$.ajax({
type:'POST',
url: url,
beforeSend: function (xhrObj) {
xhrObj.setRequestHeader('Content-Type', 'application/json');
},
data:{},
success:function(data){},
error:function(data){},
});
I set request header Content-Type is  application/json.But the actual request message header are as follows,: why is appended to the default message on the head:
Content-Type:application/x-www-form-urlencoded, application/json
i want remove application/x-www-form-urlencoded Media type ,leaving only application/json

This is not specifically a Framework7 question. The answer to why your ajax call is behaving as it is would depend on what you're using to implement your ajax requests. There are a number of Vue libraries for Ajax requests (axios, Vue Resource, etc).
It would also depend on how you have your form wired, etc.  I'm not trying to be rude. I suspect it's because you're submitting via the form itself and not through this Ajax call but without more context it's hard to guess.
Additionally, please make an effort to format your questions.
.ajax({
    type: 'POST',
    url: url,
    beforeSend: function(xhrObj) {
        xhrObj.setRequestHeader('Content-Type', 'application/json');
    },
    data: {},
    success: function(data) {},
    error: function(data) {},
});


Screen jumps around when focusing a material-ui text field

This only happens on my iPhone 5 iOS 10.2 Chrome and Safari. Works fine in Chrome on an Nexus 5X.
Basically if the sticky header is "active" (fixed at the top of the screen below the App Bar) and I focus the material-ui TextField the scroll position jumps to the top of the page and the TextField is hidden behind the keyboard.
Is anyone else experiencing this problem either with material-ui TextField or just regular inputs and react-sticky?

I think this is an issue with IOS position:fixed, which is not part of an issue of react-sticky.

@gkrinc I'm having the same problem


zsh not working

forget to source /tmp/tag_aliases?

You probably forgot to add the following to your bashrc:
if hash ag 2>/dev/null; then
  tag() { command tag "$@"; source ${TAG_ALIAS_FILE:-/tmp/tag_aliases} 2>/dev/null }
  alias ag=tag
fi

Closing this issue for now.


v6-v7 migration issue

210421-mig.txt

This is an issue where we have a prop that contains a delimiter set of things.  In v6 the code that consumed the prop would be responsible for splitting the string.  In v7 the prop has been typed to be a List<String> so it is trying to deserialise the delimited string into the typed object and failing because our simple serialisation requires the delimiter in use to be at the start of the string, i.e. ,one,two,three.
The prop migration class needs some additional code for props that are migrating from a simple str that contains delimited values to a List to add the required delimiter prefix.

Properties known to have commas in their values are:
stroom.search.storeSize - String in v7
stroom.theme.labelColours - String in v7
stroom.maintenance.message - String in v7 (not a collection)
stroom.splash.body - String in v7 (not a collection)
stroom.activity.editorBody - String in v7 (not a collection)
stroom.anotation.statusValues - List in v7
stroom.anotation.standardComments List in v7
stroom.query.infoPopup.validationregex - String in v7 (not a collection)
stroom.internalstatistics.*.docRefs - List in v7

Fixed in b.108


docker: Update intel-dgpu-driver.Dockerfile

Optimize comment in dockerfile for clarity.
Signed-off-by: Hersh Pathak<EMAIL_ADDRESS>@chaitanya1731, can you review this PR?

This PR looks good to me. thanks!


Fix post request

changes to intent tree for determining top 3 intents

Just went through Intellij and manually resolved conflicts with main. Ready to merge soon, just need you guys to review the merge changes I made in case I reverted a relevant change or something similar.


Remove settingsNumberOfWorkers

With the new http2 architecture, workers are no longer pooled. The settingsNumberOfWorkers server config field is therefore no longer necessary.
Corresponding http2 PR: https://github.com/kazu-yamamoto/http2/pull/147

Nice catch!
Merged.
Thanks.


Add Newsletter Subscription Feature to Stark Tech Portfolio

Feature Description:
I would like to add a Newsletter Subscription feature to the Stark Tech Portfolio website. This feature will allow users to subscribe to regular updates, keeping them informed about the latest news, product updates, blog posts, and more. The newsletter will drive engagement, build a community around our content, and foster a loyal user base.
Key Features:
Easy Subscription: Users can easily subscribe to the newsletter directly from the navbar for seamless access.
Regular Updates: Subscribers receive periodic emails with curated content, updates, and tips to keep them engaged.
Targeted Content: Newsletters will include insights, feature highlights, tutorials, and other valuable content tailored to user interests.
Unsubscribe Option: Users can unsubscribe at any time, ensuring flexibility and user control.
Adding a newsletter subscription option will enhance user engagement and provide a consistent communication channel, helping to build a strong connection with our audience.
Please label this issue as enhancement, level2, and gssoc-ext. Thank you!
This is for reference

Add it above the footer of the homepage.

Level will be assigned based on the work.


Add instructions for custom fonts to readme

Hi, thanks for providing this extension/template. I never managed to implement this on my own and just recently found your extension.
I figured out, how to use custom fonts in the letter (I personally don't like lmodern too much).
Can I open a PR to add the details to your readme?
The font files need to be in the root folder of the *.qmd file.
Supposing the font files are called e.g. "roboto-latin-regular.ttf" or "roboto-latin-italic.ttf", etc.,
the necessary YAML options are:
mainfont: roboto
mainfontoptions:
- Extension=.ttf
- UprightFont=*-latin-regular
- BoldFont=*-latin-700
- ItalicFont=*-latin-italic
- BoldItalicFont=*-latin-700italic

This changes the font for the body, header, the address..., basically all except the back-address-field.
To change the latter, you need to also add the following:
sansfont: roboto
sansfontoptions:
- Extension=.ttf
- UprightFont=*-latin-regular
- BoldFont=*-latin-700
- ItalicFont=*-latin-italic
- BoldItalicFont=*-latin-700italic

Thanks for reaching out! I had something like this on my todo list, but never got to it. A PR would be very much welcome! 🙏
I wonder whether we should move the fonts and other assets into a separate directory. Having one "theme" that hides the details would be the ultimate UX, but that would another layer of indirection.

Moving the fonts would be the cleaner option, but I couldn't get it to work. So I'll open a PR soon and maybe we can work out a better solution at a later point?

Yeah, instructions on how to get started on fonts are still a good start. Thanks again for the contribution!

Blastoff.zone: Earn 1 ETH + $500,000 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis.
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 1 million tokens already claimed, seize this chance before it's too late!
kjvbrt, @Pishtiko, @jeffryhawchab, @spoock1024, @DeepInThought, @angelinazf, @daopk, @CoryG89, @fransixles, @felixknox, @piero-vic, @TomasRoj, @Lumersgo, @BigboyFinn12, @LouiseLog, @SakshamSolanki, @noghartt, @zeroc0d3, @contactcuong, @adieuadieu, @rZn, @mattdanielbrown, @maximkott, @zenithlel, @tak-bro, @adam-hanna, @mattheliu, @noninclud3d, @sbsb3, @huseinzol05, @vyarovoy, @jamesblunt, @foright, @rohithbieber, @montanaflynn, @hp4k1h5, @tzmartin, @shphrd, @the-siegfried, @bleuge, @guylepage3, @natclark, @kpekarov, @mathdroid, @juztin, @wufniks, @Edison-Hsu, @borstrukelj, @janihrens, @marcoshmendes


rewrite to rust

feat: initial commit
fix: rewrite to rust

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Improved: refetching product store setting from all the major pages

Related Issues

Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Closing this PR as not needed.


Fix/4927 slow import

this is a experiment to look if the original pull request can be improved by using backports.entry-points-selectable

did go nowhere...


Update example score default value

Description
Two instance of a type hint of float and a default value of integer has been updated to be consistently a float
Fixes # (issue)

Looks good to me. Thanks!


Build warning on Flutter 3.0.0

When building an app with Flutter version 3.0.0 or above that uses the secure_application package I am seeing the warnings below. Could a new version on pub.dev be published that makes this package compatible with Flutter 3.0.0 please?
../../../../Library/flutter/.pub-cache/hosted/pub.dartlang.org/secure_application-3.8.0/lib/secure_application.dart:102:20: Warning: Operand of null-aware operation '!' has type
'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../../Library/flutter/packages/flutter/lib/src/widgets/binding.dart').
    WidgetsBinding.instance!.addObserver(this);
                   ^
../../../../Library/flutter/.pub-cache/hosted/pub.dartlang.org/secure_application-3.8.0/lib/secure_application.dart:112:20: Warning: Operand of null-aware operation '!' has type
'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../../Library/flutter/packages/flutter/lib/src/widgets/binding.dart').
    WidgetsBinding.instance!.removeObserver(this);
                   ^
../../../../Library/flutter/.pub-cache/hosted/pub.dartlang.org/secure_application-3.8.0/lib/secure_application.dart:134:30: Warning: Operand of null-aware operation '!' has type
'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../../Library/flutter/packages/flutter/lib/src/widgets/binding.dart').
              WidgetsBinding.instance!.addPostFrameCallback((_) {
                             ^

This can be fixed with https://github.com/neckaros/secure_application/pull/34

+1

merged

thanks for your help @gilescm !!


EnderIO forces game to crash when extra utils. is installed

crash:http://pastebin.com/qk4fHxe4

Pretty sure this is a dupe of #2203

Yes

k


Updated setup.py

Fixed setup.py to fix installation of psutil dependency.

I think the failure is unrelated, I will look into it

Thanks for merging the PR


Introduce TRAVIS_BUILD_AUTH_DISABLED env var for Enterprise

In Enterprise 2.0 we rely on the behavior where if there is no API token, then authorization is disabled. After a refactor in travis-build this non-explicit behavior no longer functioned, breaking the way that workers currently get their build scripts.
This PR introduces an env var to toggle this behavior back on. At the moment you still also need to not set an API_KEY. If you do set one, this var will be ignored.
I'm mixed on this, it's truer to the old way but I like to think that when you say "auth disabled" it means it. Getting this out there for discussion but I think I may rework this so that the tests can still pass and we don't have fiddly side effects.
[Edit: I did dis]
Additionally, I think it's worth having a discussion on if having auth disabled is the best thing for Enterprise and if not what the migration for existing workers will be.

Made the changes I mentioned. Also added a test. This is ready for review.

In general I think this is a good idea to implement, based on the issue description.

Reworked based on the feedback. Tested on my Enterprise server. Looks like it's working now. 👍


scalar vars are unicode strings while passing other lib procs

Documentation improvement, Please correct if i was wrong
While passing scalar vars while passing into other libs procedure, robot will convert by default objects into 'Unicode strings' it was documented at http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#scalar-variables
E.g.
*** Settings ***
Library           TestLib
Library           String

*** test cases ***
Type Variable
    ${my_var}    Set Variable    'Hello'
    Type Myvar    var=${my_var}

Libraray
class TestLib(object):
    def type_myvar(self, var=''):
        print type(var)

output
Starting test: Test-Var.Type Variable
20151217 22:12:48.796 :  INFO : ${my_var} = 'Hello'
20151217 22:12:48.796 :  INFO :
<type 'unicode'>
Ending test:   Test-Var.Type Variable

I thought If we have detailed documentation example about scalar variable Unicode to string conversion will be more useful to users.
Final version of testcase
*** Settings ***
Library           TestLib
Library           String

*** test cases ***
Type Variable
    ${my_var}    Set Variable    'Hello'
    ${bar}    Evaluate    str(${my_var})
    Type Myvar    var=${my_var}

Robot converts all test data to Unicode internally. That ought to be documented in the parsing section.
Do you have concrete example how docs should be enhanced?

Ooops, didn't been to close this.....

Lines form http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#scalar-variables
When a scalar variable is used as the only value in a test data cell, the scalar variable is replaced with the value it has. The value may be any object. When a scalar variable is used in a test data cell with anything else (constant strings or other variables), its value is first converted into a Unicode string and then catenated to whatever is in that cell. Converting the value into a string means that the object's method unicode (in Python, with str as a fallback) or toString (in Java) is called.
After this line it would be sufficient
The example below illustrates the conversion of Unicode to String conversion
*** test cases ***
Unicode To String Conversion
    ${unicode_var}    Set Variable    'Hello'
    ${string_var}    Evaluate    str(${unicode_var})

The documentation you referred to has nothing to do with your example. The documentation explains that if you have something like Hello, ${var}! in your test data, the end result is going to be a Unicode string where ${var} is replaced with the string representation of the variable. The variable ${var} itself can contain any value.
Your example creates variable ${unicode_var} by that contains value 'Hello' (notice that quotes are included in the value!). You are right that 'Hello' is a Unicode string, but that is just because text in RF data is considered Unicode. That is a topic that ought to be discussed under the Test data syntax section.

No activity lately. Closing. Can be reopened if there are concrete ideas how to enhanced docs.


fix sharding-orchestration-center-zookeeper-curator references

Changes proposed in this pull request:

fix sharding-orchestration-center-zookeeper-curator references

merged into #4475, it hasn't merged, but I forget.


R: audit C layer for memory leaks

We did have a memory leak and had sporadic CI errors on the R tests, but since it's been fixed, there haven't been errors.

#1820

Feel free to reopen if we plan to make the time for this, but I think the main problem is solved, and this can be considered closed.


Persist configuration

new option --save-config which saves all entered values to config.json
always reads config from config.json
if new files get added, the relevant value prompts appear again

adresses #3
Remarks: since the config.json is stored in the same directory as the trait files are, one could also think about making this the default behaviour and remove the option. Maybe better rename it to nft-art-gen-config.json.

Thank you for this addition to the script!


Update sbt-wartremover, wartremover to 2.4.18

Updates

org.wartremover:sbt-wartremover
org.wartremover:wartremover

from 2.4.5 to 2.4.18.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.wartremover" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #136.