How can define node as rectangles with custom svgs ? + possibles tags & slots

Hey there,
My problem: I dont find the way to define custom node as rectangle + custom svg inside.
I tried with ''rect'' in defined config or with  /  tags in the override node slot.
In waiting à solution, I have a circle with my svg inside..

More large question 1: where can I found all possibles tags to put inside v-network-graph slots ?

More large question 2: where can I found all possibles slots can be used in the map ? I searched a lot in documentation but they are not listed in... 🤷♂
Thanks by advance !

Hi @Suniron,
Thanks for your question.

My problem: I dont find the way to define custom node as rectangle + custom svg inside.

An example of specifying a custom node with a rect svg is shown below.
I hope this is helpful.
<script setup lang="ts">
import { defineConfigs } from "v-network-graph";

const nodes = {
  node1: { name: "Node 1" },
  node2: { name: "Node 2" },
  node3: { name: "Node 3" },
  node4: { name: "Node 4" },
};

const edges = {
  edge1: { source: "node1", target: "node2" },
  edge2: { source: "node2", target: "node3" },
  edge3: { source: "node3", target: "node4" },
};

const layouts = {
  nodes: {
    node1: { x: 0, y: 0 },
    node2: { x: 50, y: 50 },
    node3: { x: 100, y: 0 },
    node4: { x: 150, y: 50 },
  },
}

const configs = defineConfigs({
  node: {
    selectable: true,
    normal: {
      type: "rect",
      width: 32,
      height: 32,
      borderRadius: 0
    },
  },
});
</script>

<template>
  <v-network-graph
    class="graph"
    :nodes="nodes"
    :edges="edges"
    :configs="configs"
    :layouts="layouts"
  >
    <template #override-node="{ config, scale }">
      <!-- node's center position is (0, 0) -->
      <!-- shadow -->
      <rect
        :x="4 * scale"
        :y="(-config.height / 2 + config.height * 0.7) * scale"
        :width="config.width * scale"
        :height="(config.height * 0.3) * scale"
        fill="#444466"
        transform="skewX(-50)"
      />
      <!-- node rect -->
      <rect
        :x="-config.width / 2 * scale"
        :y="-config.height / 2 * scale"
        :width="config.width * scale"
        :height="config.height * scale"
        :fill="config.color"
        stroke="#000"
        :stroke-width="1 * scale"
      />
    </template>
  </v-network-graph>
</template>

<style>
.graph {
  width: 800px;
  height: 600px;
  border: 1px solid #000;
}
</style>

More large question 1: where can I found all possibles tags to put inside v-network-graph slots ?

v-network-graph simply expands the tags specified in the slot to the desired position, so you can specify any SVG tag that the browser recognizes.

More large question 2: where can I found all possibles slots can be used in the map ? I searched a lot in documentation but they are not listed in... 🤷♂

Sorry, the list of slots is not yet documented at this time....
The following slots can be specified.

override-node
override-node-label
edge-overlay
edge-label
edges-label

Other slots can also be added as layers, specifying where they are to be inserted. For details, please check the custom layer example.
Best Regards

I close this issue for now.
If you have any other question/comment, please reopen this issue.


Conflicting information about Auto-instrumentation support for .NET Core

On this page, there is a note at the top that says:
Auto-instrumentation is available for ASP.NET, ASP.NET Core IIS-hosted applications and Java. Use an SDK to instrument Node.js and Python applications hosted on an Azure virtual machines and virtual machine scale sets.
While further down, there is another note that says:
.NET Core, Node.js, and Python applications are only supported on Azure virtual machines and Azure virtual machine scale sets via manual SDK based instrumentation and therefore the steps below do not apply to these scenarios.
It's not clear if auto-instrumentation is support for .NET Core or not.
Also, the first note says ASP.NET Core, while the second note says .NET Core. Is that intentionally?

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

ID: 02cd947d-30c3-2551-4dd6-9762db6869f7
Version Independent ID: 4e5a974c-686c-2005-c036-55dac3107573
Content: Monitor performance on Azure VMs - Azure Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/azure-vm-vmss-apps.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

@stiglyt
Thanks for your feedback! We will investigate and update as appropriate.

Thank you for the feedback. Support for .NET Core is available in public preview. The article is being updated for clarity later tonight. #please-close


[6.0][IRGen] Strip marker protocols in a few more places

Cherry-pick of https://github.com/apple/swift/pull/74130

Explanation:
Fixes a recent regression that leads on an infinite recursion in metadata accessors for generic types and improves handling of protocol compositions that have only marker protocols.

Strip marker protocols when forming generic metadata requests
Without this might might end up with a single element protocol compositions
which are invalid.

Move marker protocol stripping from mangleTypeSymbol to mangleTypeForFlatUniqueTypeRef
The original check introduced by https://github.com/apple/swift/pull/71855
is too broad. For concrete metadata we call the runtime demangler so
we need to strip off marker protocols when mangling that string and
mangleTypeForReflection already does that.

Scope: Generic metadata accessors

Main Branch PR: https://github.com/apple/swift/pull/74130

Resolves: rdar://128667580

Risk: Low

Reviewed By: @slavapestov

Testing: Added new tests to the test suite.

@swift-ci please test


[wip] feat: embed TxEnvelope into rpc_types::Transaction

Motivation
Closes https://github.com/alloy-rs/alloy/issues/1165

Solution

Added Envelope generic for rpc transaction which is consensus::TxEnvelope by default. For AnyNetwork we need a catch-all envelope, so I've extracted current rpc_types_eth::Transaction without block-related fields into AnyTxEnvelope type.
Added Serialize and Deserialize for TxType. It deserializes as Option<U8> with None representing legacy and serializes as U8.
Updated TxEnvelope to use custom deserialize impl to handle case of missing type field as legacy tx.

After this PR, Transaction will only implement arbitrary if k256 feature is enabled because of similar requirement on SignedAuthorization. I think this makes sense and believe we also want to add similar restriction for Arbitrary impl on Signed<T> which will only produce valid transactions.
At this point we are maintaining 6 very similar serde schemes + rlp encoding implementations for different tx holding types (5 tx types + AnyTxEnvelope). Wondering if we should add a macro for generating those so that serde attrs for e.g. gas are only defined once?
PR Checklist

[ ] Added Tests
[ ] Added Documentation
[x] Breaking changes

The only breaking change this PR adds is for serde roundrip for rpc_types::Transaction. Earlier we wouldn't modify the serialized payload, but with this PR we will convert "v": "0x0 | 0x1" into yParity key with the same value.
This might only result in incorrect payload for legacy transactions as for them v is required. However, per EIP-155 spec:

then v continues to be set to {0,1} + 27 as previously.

Which likely means that it is safe to expect v on legacy transactions to always equal to 0x1c | 0x1b, thus never resulting in incorrect deserialization on our side
I've changed test fixtures because they contained v key with the same value yParity should contain. The change was required because during roundrip v was becoming yParity, thus failing assertions. Deserialization is still fine for previous fixtures, so there're no breaking changes for deserialization in this PR.

Closing in favor of #1460


Does not span across days; only hours in day

If I start a project at 08:54:42 on Monday, and end at 08:54:43 on Tuesday, I would expect to have logged a total of exactly one day and one second, but in this scenario, timecard would only log it as one second because there is no concept of a DAY in the clockout scheme:
{
      "id": 0,
      "date": "Mon Feb 13 2017",
      "startTime": "08:54:42",
      "endTime": "08:54:43"
    }

Both clockin and clockout should have a datetime associated with it, not just a time.

This is a big bug, fixing it now.

fixed via https://github.com/radiovisual/timecard/commit/671d1e62780f09596c054f8919b9c2769d50c8cb


Ray/fixes builder sleaze

Two shas: catch up to the latest build tools, and fix a History.Builder bug.

Update to (try to) accept 3.0.0-rc1 license


Can one run fal test?

I'm trying to make something like this:
fal test --profiles-dir . --target dev --selector my_data --vars '{my_var: "my_var_value"}'

Is it currently supported?

Hello @CavalcanteLucas, thanks for reaching out. We currently don't have a test command. I am curious what would you expect a fal test command to do? Specifically, what would it do different than dbt test, for example?

Thank you for your quick answer @chamini2
I wondered if the user could associate fal with dbt tests. I assumed we could establish let's say a relationship test like:
version 2

models:
    - name: my_model
    - name: my_other_model
        columns:
            - name: my_model_id
                tests:
                    - relationships:
                        to: ref('my_model')
                        field: id
        meta:
            fal:
                scripts:
                    - fal_script.py

And, in case the test failed, fal would trigger the script that would send a slack message.
Is there maybe an alternative way to accomplish this?

There is a way to accomplish this today.
You can run dbt run followed by fal run. In this script we have an example of checking for tests: https://github.com/fal-ai/fal/blob/2b9247eba84dab88225bc106c11681e477f1e6b7/projects/fal/integration_tests/projects/005_functions_and_variables/fal_scripts/write_to_source_twice.py#L25-L36
This is the output of running it:
❯ dbt test
00:04:27  Running with dbt=1.4.5
00:04:27  Found 3 models, 4 tests, 0 snapshots, 0 analyses, 299 macros, 0 operations, 0 seed files, 2 sources, 0 exposures, 0 metrics
00:04:27
00:04:28  Concurrency: 3 threads (target='fal_pg')
00:04:28
00:04:28  1 of 4 START test not_null_some_model_my_int ................................... [RUN]
00:04:28  2 of 4 START test not_null_some_model_my_text .................................. [RUN]
00:04:28  3 of 4 START test source_not_null_results_ns____ns__some_source_my_int ......... [RUN]
00:04:28  1 of 4 FAIL 1 not_null_some_model_my_int ....................................... [FAIL 1 in 0.04s]
00:04:28  3 of 4 FAIL 2 source_not_null_results_ns____ns__some_source_my_int ............. [FAIL 2 in 0.04s]
00:04:28  2 of 4 PASS not_null_some_model_my_text ........................................ [PASS in 0.04s]
00:04:28  4 of 4 START test source_not_null_results_ns____ns__some_source_my_text ........ [RUN]
00:04:28  4 of 4 PASS source_not_null_results_ns____ns__some_source_my_text .............. [PASS in 0.01s]
00:04:28
00:04:28  Finished running 4 tests in 0 hours 0 minutes and 0.34 seconds (0.34s).
00:04:28
00:04:28  Completed with 2 errors and 0 warnings:
00:04:28
00:04:28  Failure in test not_null_some_model_my_int (models/schema.yml)
00:04:28    Got 1 result, configured to fail if != 0
00:04:28
00:04:28    compiled Code at ./target/compiled/fal_005/models/schema.yml/not_null_some_model_my_int.sql
00:04:28
00:04:28  Failure in test source_not_null_results_ns____ns__some_source_my_int (models/schema.yml)
00:04:28    Got 2 results, configured to fail if != 0
00:04:28
00:04:28    compiled Code at ./target/compiled/fal_005/models/schema.yml/source_not_null_results_ns____ns__some_source_my_int.sql
00:04:28
00:04:28  Done. PASS=2 WARN=0 ERROR=2 SKIP=0 TOTAL=4

❯ fal run
00:04:36  Found 3 models, 4 tests, 0 snapshots, 0 analyses, 299 macros, 0 operations, 0 seed files, 2 sources, 0 exposures, 0 metrics
00:04:36 [fal]: [WARNING]: Could not read dbt sources artifact
00:04:36 [fal]: Starting fal run for following models and scripts:
(some_model, fal_scripts/write_to_source_twice.py)

# this file is created during the fal run
❯ cat some_model.write_to_source_twice.txt
my_float 1.2
source size 1
source size 2
source results.other_source has 0 tests, source status is skipped
source results.some_source has 2 tests, source status is tested
model some_model has 2 tests, model status is tested
model third_model has 0 tests, model status is skipped
model other_model has 0 tests, model status is skipped

You can check more information in https://docs.fal.ai/fal/fal-dbt/fal-with-dbt-test

Please feel free to re open if this does not satisfy a use case you have! I will be closing for now.
Thanks for reaching out!


Add a redirect to login page after user signs out from checkout page

Small change that fixes #1142
Description
Currently, when a logged in user goes to checkout and then clicks the sign out button on the contact info, the system will log the user out but remain on the checkout page (and leave the sign out confirmation dialog open!)
The current behavior is weird because when a user signs out, they are considered a brand new user, with a new basket, with no items in their basket. The user should not remain on the checkout page if they have an empty basket so this PR adds a redirect to navigate the user to the login page after signing out.
Types of Changes

[X] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

Add a redirect to login page after user signs out from checkout page
Remove extra basket creation. Not quite sure why it was there since we create a new basket for the now-guest user elsewhere.

How to Test-Drive This PR

Start the retail react app
Log in
Add an item to your cart
Go to the checkout page
Click sign out

Expected results: You are signed out and redirected to the login page (the same behavior seen if you log out via the header or menu)
Checklists

General

[ ] Changes are covered by test cases
[x] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[X] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Does it make sense to redirect users to login page while they are checking out an item? I don't think we should redirect users to login page, it breaks the checkout flow, the user will have to go back to checkout to purchase the item

@alexvuong I think in this case it makes sense. The redirect to login page only occurs if the user signs out, which also has the side effect of giving the user a brand new empty basket (so there's nothing for them to checkout in the first place)

@vcua-mobify, hmm from UX perspective, I'd see that could be a bad experience for shoppers, but I can understand if that is how the API behaves.

@alexvuong The basket being reset when a user transitions from logged in -> guest is expected behavior I believe. The alternative would be to do a cart merge from a registered user to a guest user, which seems bizarre and potentially a security issue (if the user logs out, the now-guest user should not see what was in the logged in user's cart).

@bfeister Here's a before and after showing the change:
Before (reproduced on https://pwa-kit.mobify-storefront.com/)
https://user-images.githubusercontent.com/47404250/236521185-fe351fe8-b87c-428f-ae0a-cacf50fa57f1.mov
After (reproduced locally with this PR)
https://user-images.githubusercontent.com/47404250/236521290-401b15c1-fd0a-4969-8bdb-2d7ffd5bb679.mov

curious, can you remind me what's the difference between useHistory and useNavigate again? Seems useNavigate is working but I'd love to understand why.

curious, can you remind me what's the difference between useHistory and useNavigate again? Seems useNavigate is working but I'd love to understand why.

useNavigation take the multi-site into the account, it will re-build the url with site and locale for the given url, while useHistory does not

@bfeister I opted to route to the login page for consistency because that is the page we route to when signing out via the header or menu. However, if we decide the home page is better, I can make that change as well


Add visualization panel for agent stats

Created Unity prefab, VisPanel, which is a draggable, closeable panel that can be opened by clicking an agent and clicking "Examine stats". It displays the name, level, resources, and skills of the agent and updates in real time. Multiple panels can be open at once.
The panel makes the UI bar at the top redundant except for the header and FPS tracker, so everything else was removed. Correspondingly the "Examine" button that would appear when clicking an agent has been replaced with "Examine stats".

It is success that ues the client in the windows， but I don't konw how to use it in the Ubuntu system?


txn: fix wrong txn_size in acquire_pessimistic_lock (#5681)

Signed-off-by: youjiali1995<EMAIL_ADDRESS>
What have you changed?
cherry pick #5681

/run-all-tests

/run-all-tests

@sticnarf  @MyonKeminta PTAL

/merge


Exploration: "Advanced" setting to directly edit the meltano.yml file in the Meltano UI

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/655
Originally created by @dmor on 2019-05-24 14:56:09

Important: Changing this file is useful, but this should be highly protected/warned area that clearly explains how changing this file could mess up your installation. It would also be a great place to allow the user to "restore to default settings".
Similar to how Wordpress let's you change things in form fields, but also let's you edit the entire file if you want to (e.g. header.php and style.css are the typical ones)

View 7 previous comments from the original issue on GitLab


Dataset download and streaming

Acceptance Criteria

This ticket is done when: dataset download is enabled as a zip file

This ticket is done when: we have a way to stream the whole file to the jina gateway

Link to subfeature: https://jinaai.productboard.com/feature-board/planning/features/7284093

Currently done for the multimodal example:
Can extend by:

[ ] chatbot example
[ ] kicking off a conversation on generalized data ingest

This ticket is done when: dataset download is enabled as a zip file

What is the purpose of this goal?


Fix Building HPX in Quick start

Change instructions for building HPX from paragraphs to structured information (numbered and bulleted lists, code blocks etc.)

Can one of the admins verify this patch?

add to whitelist


feat: Initial Rails app

Initial commit with Rails application. Contains basic stuff plus some extra libs which will be required here -- rswag, postgis, cancancan, rgeo, etc.
I believe we will want to reuse as much as possible code from Heco so I setup Fora same way (and used same gems :)).
Feel free to merge @agnessa @tiagojsag if you don't see any mandatory issues with this.

bot

Can we turn off vercel for backend @mbarrenechea ?

Great, looks very familiar :) I think we are going to need sidekiq, unless you suggest sth else for processing uploads in the backoffice? I think it needs to go in a background job. I know we're nowhere near starting the backoffice, but since @tiagojsag is setting up the deployment script, it might be good to add it right away so he can configure that.

Great, looks very familiar :) I think we are going to need sidekiq, unless you suggest sth else for processing uploads in the backoffice? I think it needs to go in a background job. I know we're nowhere near starting the backoffice, but since @tiagojsag is setting up the deployment script, it might be good to add it right away so he can configure that.

Sure, I can add sidekiq and redis gem. I was not sure how huge these imports are gonna be so kept open to idea that we will maybe not need job, but I guess there is high probability that it will be needed 🙃

I am not sure how you handle error tracking at rails apps so not added any gem responsible for this, but if you plan to use for example sentry or some other solution, let me know and I can help you to add appropriate gems ;)


Add Meta.created field and search param

Currently, to figure out when a certain resource was created, users have to use the history Api and search on the client-side. We've had a number of requests for the ability to search on the creation time of a resource (rather than the lastUpdated time) that it would make sense to make this a first-class member of our Meta type, similar to Meta.author

I'd like to wait and gather more data points before doing this.
We should treat every custom addition to Meta as a pretty serious change because the blast radius is pretty big.

Created PR #3182 , which documents using the history endpoint to find when a resource was initially created.

Ah, a classic problem. Some relevant discussion: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/meta.2EcreatedAt

Since this initial ticket was created, we've had a number of users request this field. The main use case expressed is to have a deterministic sort order for paging through large sets of resources, without having to worry about resources being updated while paging:

https://github.com/medplum/medplum/issues/4608
https://medplum.slack.com/archives/C078NUJP6B1/p1720554158566419
https://medplum.slack.com/archives/C04A55B3VU5/p1710438477973899?thread_ts=1710363533.552519&cid=C04A55B3VU5


Fix/invalid path on windows

The test case named helm2: upgrade when tns1/foo needs tns2/bar results in a file (stored in the repository) at the path pkg/app/testdata/testapply/helm2:_upgrade_when_tns1/foo_needs_tns2/bar/log. Such a path is invalid on NTFS filesystems due to the : character. Because this file is checked into the repository, it becomes impossible to clone the repository on any Windows system.
This change simply renames the test to helm2 upgrade when tns1/foo needs tns2/bar, so that the snapshot log path is pkg/app/testdata/testapply/helm2_upgrade_when_tns1/foo_needs_tns2/bar/log, which is valid on NTFS (and presumably basically all filesystems).

@philomory good. Thanks very much.
@mumoshu what do you think of this?


Allow to capture luigi-interface logger without it spawning a stream handler

In luigi.interface, we have:
def setup_interface_logging(conf_file=None):
    # use a variable in the function object to determine if it has run before
    if getattr(setup_interface_logging, "has_run", False):
        return

    if conf_file is None:
        logger = logging.getLogger('luigi-interface')
        logger.setLevel(logging.DEBUG)

        streamHandler = logging.StreamHandler()
        streamHandler.setLevel(logging.DEBUG)

        formatter = logging.Formatter('%(levelname)s: %(message)s')
        streamHandler.setFormatter(formatter)

        logger.addHandler(streamHandler)
    else:
        logging.config.fileConfig(conf_file, disable_existing_loggers=False)

    setup_interface_logging.has_run = True

If I want to capture/redirect luigi's loggers, I'd expect this to work (can use the standard logging handlers as well, it doesn't really matter):
import logbook.compat
logbook.compat.redirect_logging()

However, setup_interface_logging will still eventually create a StreamHandler when luigi.run is called and it will dump everything to console, so instead of capturing the log you will end up with duplicate streams. The only way to avoid this currently is to do something like
from luigi.interface import setup_interface_logging
setup_interface_logging.has_run = True
logbook.compat.redirect_logging()

... which is quite bad since it uses internal implementation details.
I wonder if this could be improved to allow log stream capturing in a cleaner fashion? Maybe just move stream handler instantiation somewhere else or allow to hook into this function.

I'm closing this issue.

[x] It has been inactive for +4 months.
[ ] It's not about luigi core, so not as many users are affected about this.
[ ] The change seems quite big, it's unlikely to be sporadically picked up.
[ ] The owner haven't responded or disappeared.
[ ] I don't understand what this issue is about.
[ ] There exists a reasonable workaround for this.
[ ] We need to check if this hasn't been fixed by now (for old issues).
[ ] This is kind of by design and not a bug.
[ ] Resolving this would probably add a lot of complexity.

Every open issue adds some clutter, and we try to make the issues fewer and make it easier for new collaborators to find. Currently we try to close any issue that meets the first checkbox + one other.
Feel free to reopen this issue at any point if you have the intent to continue to work this. :)

We really need somebody who knows Python logging to jump in and help us. Though I suspect there are more recent discussions on this.

We are being bitten by problems with logs too. Is there some real-time chat you prefer to talk?

Has anyone found a workaround for this?

@aldanor @alanjds @Tarrasch @sklarsa have you tried to insert
if __name__ == '__main__':
  import luigi
  from luigi.interface import setup_interface_logging

  # set it up as you want it to be setted up
  setup_interface_logging(...)

  luigi.run()

at the end of your main.py and call it python main.py Main <parameters>?

cc: @psugimoto

@walkingpendulum That was the whole point of this issue - setup_interface_logging() creates stream handlers where it generally shouldn't.

@aldanor now I get it. I end up with setup as follows
$ cat luigi.cfg
[core]
logging_conf_file=luigi_logging.cfg

$ cat luigi_logging.cfg
[loggers]
keys=my-logger,root

[logger_my-logger]
handlers=custom
qualname=my-logger
level=INFO
propagate=0

[logger_root]
handlers=output

[formatters]
keys=simple

[formatter_simple]
format=%(asctime)s - %(name)s - %(levelname)s - %(message)s

[handlers]
keys=output,custom

[handler_output]
class=StreamHandler
formatter=simple
args=(sys.stdout,)

[handler_custom]
class=StreamHandler
formatter=simple
args=(sys.stdout,)

$ cat script.py
import luigi

class MyTask(luigi.Task):
    def run(self):
        self.called_once = True

        import logging
        logging.getLogger('my-logger').info('Here we are')

    def complete(self):
        return hasattr(self, 'called_once')

if __name__ == '__main__':
    luigi.run()

$ python script.py MyTask --local-scheduler
2017-11-14 10:15:24,942 - my-logger - INFO - Here we are

What I'm doing is to reconfigure logging after I the luigi import in my script file, basically:
LOGGING =  some_logging_dict_config
logging.config.dictConfig(LOGGING)

@psugimoto eventually (someone correct me if I'm wrong) luigi doesn't have pythonic api (with python dictionary) for logging configuration. either you setup logging with *.cfg file or you monkeypatch luigi's setup_interface_logging

In my case what I want are the logs from the tasks luigi runs, which have their own loggers. It works for me. If you want logs from luigi itself you are probably right and this does not help


Updated Switch Case with enhanced switch case.

Switch Case in Original Code updated with enhanced switch case.

With Modern Versions of Java, the enhanced switch case is much more clean to look while going through the code.
Please have a look into it, to see if it is compatible.
Thanks
Sanjeeban.


fix: Warning CS0436

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0027574-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0027740-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0028020-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Fixed leading parentheses breaking CTEs

Describe your changes
Added a check before rendering sql queries to remove leading parentheses
Issue number
Closes #876
Checklist before requesting a review

[x] Performed a self-review of my code
[x] Formatted my code with pkgmt format
[x] Added tests (when necessary).
[x] Added docstring documentation and update the changelog (when needed)

:books: Documentation preview :books:: https://jupysql--877.org.readthedocs.build/en/877/

closing as this is not a bug


tcmalloc  can't realse memory on Cloud Server with OS 2008Server R2

tcmalloc running well on my computer(win10,x64) (memory can realse to os)
,but when i put it running on my Server which is Cloud Server with OS windows2008Server R2(x64),the program memory will increase slowly and never reduce until OOM.It can‘t work well On Clond Server?

Can you post small test program that demonstrates the issue?

Closing due to inactivity. Please reopen if you have some evidence to add.


Fix ignorefile parsing on windows

We use slashes internally for separators so using the path separator was a bug. Pull the path specific logic into IgnoreFile util so callers don't need to know implementation details.

Better to be firm with what we accept then end up in potentially unexpected states IMO


Hmmorales/update sample sdk code

Title out of date: Updating all sample code to demonstrate several networking properties and functionality

LGTM

@hmmorales there is another PR still active, let's take what we think makes sense there into your PR and close it or simply just close it.

Once those minor spacing is fixed, we should be good. Overall, it looks good!


backend: send the error to the client when the handler encounters an error

What problem does this PR solve?

Issue Number: close #180
Problem Summary:
Currently, when the serverless tier encounters an error, the error is logged but not returned to the client. The client cannot figure out the error easily.
We need to wrap the error into a MySQL error and return it to the client.
What is changed and how it works:

Write a MySQL error to the client when the fetcher and handler return errors

Check List
Tests

[x] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Start a TiProxy without any TiDB instances. Then start a MySQL client to connect to the TiProxy:
mysql -h127.1 -uroot -P6000 test
ERROR 1105 (HY000): No available TiDB instances, please check TiDB cluster

Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change (Don't forget to add the declarative for API)
[ ] Has tiproxyctl change
[x] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

I think we should not wrap so many errors, it is fine to wrap errors before L137/frontend cap negotiation with ErrBeforeClientResp:
if errors.Is(err, ErrBeforeClientResp) {
  // only log
} else if errors.As(err, &UserError) {
  // log and send custom error, or 'client cap', 'no instance'
} else if errors.Is(err, Deadline) {
  // log and send `timeout, bad network situation`
} else {
  // log and send `cluster configuration/topo wrong, contact admin or check proxy log`, or whatever
}

In fact, I think only client cap negotiation, no instance, dial timeout and possible errors from gateway should be sent to user.
All other errors are likely mistakes of cluster configuration, which could be solved by auditing tiproxy log and fixing cluster topology. And on tidb cloud, that is impossible for users.

I didn't wrap errors before L137, so they will be logged currently.
I should report errors when parsing the HandshakeResp or verifying client capability fails, just like TiDB does. And the error code and messages should also be the same as TiDB. But I didn't, it will make this PR too long.
no instance and dial timeout are internal logic. There are similar errors like deadline exceeds. I wrapped them all together into one kind of error. The user should check the cluster in whichever case.


Planning: Electrofishing Query app upgrade to new Esri SDK

Benefit
Plan for FY24 Q4 or FY25 Q1 rebuild of the app with the new Esri SDK.
This app utilizes the ArcGIS API 3.x for JavaScript, which will be retired on July 1, 2024. Once version 3.x is retired, there will be no further bug fixes or enhancements to the API and hence no further 3.x API deployments to js.arcgis.com. In addition, technical support will no longer be available.
Acceptance Criteria

[ ] Assess effort and time to rebuild
[ ] Define technical and administrative dependencies
[ ] Define budget and schedule

Notes
Repo: https://github.com/agrc/electrofishing-query
Risks
Mitigate:

Preparation for a smooth transition to this as a defined, future feature.
Buy-in from client for likely cost beyond the maintenance agreement amount.

Issue Reference
refs #63

Scott and Nathan met with DWR (Craig, Todd, Buck) and outlined a very general plan for addressing the upgrade and an enhancement request to modify the bulk uploading feature to include related data (tags, diet, etc.). We will need a more formal estimate of time and cost in Q4. This will be wrapped into a planning feature for the quarter.


About learning rate setting

Hello,
In most of the config files (e.g., this), I can see that the argument "lr" of the optimizers are set to 3e-4, and warmup_iters of the lr_config is set to 2.5. Does this mean the learning rate is starting from 0, linearly increases to 3e-4 at 2.5 epoch, and anneals back to 0 at 50 epoch? Do you scale the learning rate based on the batch size?

Hi, you understanding about the behavior of learning rate decay is correct. You may want to scale the learning rate based on the batch size. The current learning rate is for batch size 64.


How to use visual prompts with huggingface?

Question
Thank you for the great work! What is the preferred way to feed in visual prompts with the huggingface endpoint?

Hi Josh, great question!
The simplest approach is to

Use the official huggingface endpoint code https://huggingface.co/llava-hf/vip-llava-13b-hf
Edit/Overlay the image using the visual prompt. Example code can be found here: https://github.com/mu-cai/ViP-LLaVA/blob/main/llava/visual_prompt_generator.py#L270

Let me know if you need further/more-detailed assistance!

This was very helpful, thank you!

Or check out this part in README!
Or use the bounding box as the

which makes visual prompt generation much easier!


store model's visual_degrees

supports https://github.com/brain-score/brain-score.web/pull/86

this PR requires a change to the database, following brainscore/submission/models.py -- @jjpr-mit how do you recommend to proceed? Change the test database, merge this PR quickly so that following tests have an updated database schema again?

can't find jenkins job, re-triggering

re-trigger after removing console_log column from test db


Return removed socket.io.js

Fixes #142

@butlerx could you merge this? I removed socket.io in a hurry while fixing the imports which came up in rebase.

Thanks


Reproducer for HHH-15634 Lazy basic property does not get updated on change

https://hibernate.atlassian.net/browse/HHH-15634
Reproducer only, no fix.

Superseded by #5461 - thanks!


XYZ coordinates consistently estimating 60 mm variance between left and right lefts

As seen here when I plot the average estimated distance between the heel marker and the knee marker, the right leg is almost always 60 mm longer than the right leg. This is over more than 160 different testers with different devices, camera's, and demographics. The xyz coordinates for those landmarks are almost always showing that one leg is longer than the other.

@MitchChild,
would you please elaborate your query with complete details and steps to reproduce the issue from our end.

`def left_leg(results):
real_left_heel_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_HEEL
]
real_left_ankle_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_ANKLE
]
real_left_knee_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_KNEE
]
real_left_hip_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_HIP
]
real_left_toe_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_FOOT_INDEX
]
real_left_knee_point = landmark_point(real_left_knee_landmark)
real_left_hip_point = landmark_point(real_left_hip_landmark)
real_left_ankle_point = landmark_point(real_left_ankle_landmark)
real_left_heel_point = landmark_point(real_left_heel_landmark)
real_left_toe_point = landmark_point(real_left_toe_landmark)
thigh_size = np.linalg.norm(real_left_hip_point - real_left_knee_point)
calf_size = np.linalg.norm(real_left_knee_point - real_left_ankle_point)
ankle_height = np.linalg.norm(real_left_ankle_point - real_left_heel_point)
foot_size = np.linalg.norm(real_left_toe_point - real_left_ankle_point)
leg_length = calf_size + thigh_size
return (ankle_height, thigh_size, calf_size, leg_length, foot_size)`

Here is a snipped of a function where we're grabbing the landmard xyz coordinates and calculating the lengths of the different segments (we do this with each segment for right and left). After doing this on over 150 individuals on more than 500 frames/video for each person the average estimate is almost exactly 60mm different for right and left segments of the shank (AKA calf)

We've tried different linear algebra functions and have narrowed it down to the xyz coordinates being either improperly placed or reported, but its suspiciously consistent in the error which makes me think its a reporting error

I responded in Github too, but I’ll add my comment here also:
@kuaashish https://github.com/kuaashish
Here is a snipped of a function where we're grabbing the landmark xyz coordinates and calculating the lengths of the different segments (we do this with each segment for right and left). After doing this on over 150 individuals on more than 500 frames/video for each person the average estimate is almost exactly 60mm different for right and left segments of the shank (AKA calf).
`def left_leg(results):
real_left_heel_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_HEEL
]
real_left_ankle_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_ANKLE
]
real_left_knee_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_KNEE
]
real_left_hip_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_HIP
]
real_left_toe_landmark = results.pose_world_landmarks.landmark[
mp_pose.PoseLandmark.LEFT_FOOT_INDEX
]
real_left_knee_point = landmark_point(real_left_knee_landmark)
real_left_hip_point = landmark_point(real_left_hip_landmark)
real_left_ankle_point = landmark_point(real_left_ankle_landmark)
real_left_heel_point = landmark_point(real_left_heel_landmark)
real_left_toe_point = landmark_point(real_left_toe_landmark)
thigh_size = np.linalg.norm(real_left_hip_point - real_left_knee_point)
calf_size = np.linalg.norm(real_left_knee_point - real_left_ankle_point)
ankle_height = np.linalg.norm(real_left_ankle_point - real_left_heel_point)
foot_size = np.linalg.norm(real_left_toe_point - real_left_ankle_point)
leg_length = calf_size + thigh_size
return (ankle_height, thigh_size, calf_size, leg_length, foot_size)`
We've tried different linear algebra functions and have narrowed it down to the xyz coordinates being either improperly placed or reported, but its suspiciously consistent in the error which makes me think its a reporting error

On Feb 27, 2023, at 4:03 AM, kuaashish @.***> wrote:
@MitchChild https://github.com/MitchChild,
would you please elaborate your query with complete details and steps to reproduce the issue from our end.
—
Reply to this email directly, view it on GitHub https://github.com/google/mediapipe/issues/4125#issuecomment-1446122463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXJRHIRXCOMJL2L2SO5KAWTWZSCXLANCNFSM6AAAAAAVHNG3VM.
You are receiving this because you were mentioned.

Hey googlers, I was wondering if there were any updates to this. Happy to explicate further if needed. Thanks so much for all you do!

Hi, I am also waiting for an update to fix this problem.

HI @MitchChild,
It appears that you are utilizing the legacy pose solution. Could you please specify the exact example from the documentation you are following? If you are currently using the legacy solution, we recommend upgrading to our new Pose Landmarker Task API. This upgraded pose solution is consistently maintained. Additionally, please inform us if you observe similar behavior in the upgraded Task API.
Thank you


[BUG]does not contain package

go get -u ./...

# ........

cannot load github.com/micro/go-plugins/registry/etcdv3: module github.com/micro/go-plugins@latest found (v2.0.1+incompatible), but does not contain package github.com/micro/go-plugins/registry/etcdv3

don't do go get -u

don't do go get -u it updates all deps and always broken

How shoud I do instread?
go get -u github.com/micro/go-micro is the same

```go get github.com/micro/go-micro`
Remove the -u

go get github.com/micro/go-micro
Remove the -u

After go get github.com/micro/go-micro && go mod tidy
It report:
vscs/kernel imports
	github.com/micro/go-plugins/registry/etcdv3: module github.com/micro/go-plugins@latest found (v2.0.1+incompatible), but does not contain package github.com/micro/go-plugins/registry/etcdv3
vscs/kernel imports
	github.com/micro/go-plugins/transport/utp: module github.com/micro/go-plugins@latest found (v2.0.1+incompatible), but does not contain package github.com/micro/go-plugins/transport/utp
vscs/kernel imports
	github.com/micro/go-plugins/wrapper/service: module github.com/micro/go-plugins@latest found (v2.0.1+incompatible), but does not contain package github.com/micro/go-plugins/wrapper/service

I had clean all my go.mod yet

don't do go get -u it updates all deps and always broken

I added replace at the top of go.mod and it work!
replace github.com/coreos/etcd => github.com/coreos/etcd v3.2.28+incompatible
replace github.com/micro/go-plugins => github.com/micro/go-plugins v1.5.1

I find that https://github.com/micro/go-plugins/releases has confused tag likewrapper/validator/v2.0.2 release, why not v2.0.2

this is needed for v2 in case of submodules

this is needed for v2 in case of submodules

Thank you for you  reply, maybe I should wait for v2 completed because go.mod depends on release tag like va.b.c

v2 already completed


Fixes #106 - Solved dependecies conflicts from pytest version

Coverage remained the same at 81.787% when pulling<PHONE_NUMBER>8082b3c6ec8127d7b1192a55c96b9d on jjpaulo2:master into bd718289c60a7cf3abcc173101eefbc7799026ba on pygame:master.

Looks good to me 👍


remove nodejs api depedencies in order to support webpack5 and other bundlers.

Is your feature request related to a problem? Please describe.
I am trying to get danfojs running with quasar + webpack5 + vue3. Its a pain, because danfojs apparently relies on the nodejs api.
I have no idea about the internals of danfojs  but I do get these errors here when trying to compile with the configuration below:
danfojs:  1.0.2
quasar: v2.5.5
vue: 3.2.31
I solved it by doing things like this in the webpack configuration but it is kind of a dirty workaround and
will definitly care away new programmers that want to use danfojs in frontend applications using react/vue/angular and the likes...
extendWebpack (cfg, {isServer, isClient}) {
          cfg.module.rules.push ({
            resolve: {
              fallback: {fs: false, net: false, tls: false}
            }
          })
}

chainWebpack ( chain ) {
        // also needs:
        //    yarn add --dev node-polyfill-webpack-plugin browserify-zlib
        const nodePolyfillWebpackPlugin = require('node-polyfill-webpack-plugin')
        chain.plugin('node-polyfill').use(nodePolyfillWebpackPlugin)
        chain.resolve.alias.set('zlib', 'browserify-zlib')
}

Describe the solution you'd like
Remove dependencies on nodejs API in order to support the browser and SPA such as Vue/React/Angular in a better way.
Describe alternatives you've considered
Change the package to dataforge, but I need some features that aren't available there...
Additional context
here is a short explanation of whats going on:
https://quasar.dev/start/upgrade-guide#nodejs-polyfills
and here a similar issue for another library:
https://github.com/quasarframework/quasar/issues/9780

@yeus Danfojs is currently bundled for and able to run browser side, so I'm sure this has to do with your Webpack config. See our webpack config for building the browser side version here: https://github.com/javascriptdata/danfojs/blob/dev/src/danfojs-browser/webpack.config.js


Added to MariaDB, MySQL, PostgreSQL, and Docker-Compose

Major additions to MariaDB & MySQL; minor additions to PostgreSQL and Docker-Compose.

Amazing work @sfcampbell, thanks for review @freckhard, this is great!

Thank you @ChristianLempa -- I hope to keep it up!  These initiatives you've pioneered are fantastic; I'm happy to pitch in where I can 👏


[Improvement] Typescript definition types + NPM

Description
Few ideas for improvement:
1/ This could be nice to add typescript typings to the repo.
This would make autocompletion and typescript usage of these runtimes more user friendly.
2/ Publishing these runtimes on NPM could helps.
It would be easier to manage as a user, and get future update without have to manually check this repository.
3/ A LICENSE.md file: It took me times to realize the license was directly embedded in each js file. Github doc

Very good suggestions! I will look into this when I get the cycles.
Cheers

Hello, I created the typings for using this library with Phaser3.
https://github.com/bkostrowiecki/creature_phaser3_typings
So it may be a good starting point for creating TypeScript declarations.


Decouple Bucket from storage operations

Applications typically interact with resources in a single bucket (there are some exceptions). The Storage interface only provides ways to deal with global resources forcing the application to pass the bucket name around as an additional string. We should add a Bucket interface that supports common operations (CRUD, Copy, Move) within a single bucket.
For example:
@Resource Bucket data;

void download(String path) {
  // do something like data.reader(path);
}

Wouldn't this work if we just provided a getObjectInfo() method on the bucket? That way, we can pass around the bucket object, and don't need duplicate useful methods?
class Bucket {
  ...

  ObjectInfo getObjectInfo(String objectName) {
    // This way I can pass around a bucket, and call getObjectInfo() on it
    // when I need the object.
    return new ObjectInfo(bucket, objectName);
  }

  ...
}

So the code you'd write is basically bucket.getObjectInfo("myfile.txt).download() or bucket.getObjectInfo("myfile.txt").delete() ?
Which makes me ask... don't we have this already?

We have BucketInfo which provides metadata about a bucket but does not allow operations on it (which makes sense for a value object). This would mean adding a Bucket interface to support operations at a Bucket level.
#55 describes a way in which this could be implemented but I opened this to generalize the issue.

OK, any chance you could update the body of the issue to clarify exactly what the end result would be in a perfect world? What would the code (that I write -- as a user) ultimately look like?

Also, there are cases where the application is just interested in the data and not the full BlobInfo e.g. to download the content it needs the data plus metadata pertinent to the response header e.g. Content-Type but not things like the Acl etc.

Sure:
public class DownloadServlet extends HttpServlet {
  @Resource Bucket data;

  public void doGet(HttpServletRequest request, HttpServletResponse response) {
    String path = request.getPathInfo();
    IOUtils.copy(data.reader(path), response.getOutputStream();
  }
}

Obviously there'd be some additional error handling and validation but that wouldn't affect the interface. A more serious implementation would also want more information about the object e.g. content-type, size, etag to add as response headers which would expand the interface. We could add a new one or add metadata methods to BlobReadChannel.

I think this is part of what I am currently working on after I renamed the Bucket and Blob data models to BucketInfo and BlobInfo (as mentioned in issue #57 and described in the GCS review doc). I thought to use issue #55 for this purpose.
The result would be functional (but not serializable) Bucket and Blob that have operations on them (such as bucket.list, bucket.getBlob,... blob.content(), blob.delete(), ..). Both Bucket and Blob would hold a reference to their associated Storage.
Storage would be changed to return (the new functional) Bucket or Blob and accept BucketInfo or BlobInfo (or just name when content is not needed).
Similarly Bucket would return Blob and accept BlobInfo.
I think this would answer for issue #55 Is there more to be done for this issue?

Functional Blob and Bucket were added in #171


CLI: Adds --quiet flag

Don't want to step on toes here if you were already working on this, @gibatronic , but thought I'd take a stab at implementing the -q, --quiet flag for the cli.
I think this addresses the use case of #841
Wrote some tests to ensure that the flag keeps the cli from outputting to stderr on log and warn. Also wrote a test to ensure that error is still passed through, regardless of if --quiet is used by creating an invalid fixture which contains a reference to an undefined sass variable.
@gibatronic would this successfully enable you to do what you need to do?
/cc @am11 @wesleytodd

The failure doesn't seem to have anything to do with the PR.  So, looks perfect to me!!

@wesleytodd yeah, was just investigating that. Everything seems to pass locally, and the test that it is failing on is testing .render which is the same.

repushed, let's see if it happens again.

sigh...

Ok, I think this is because master is failing the build as well.

yes @paulcpederson, this is going to work fine.
I was just about to start working on it, so it's alright!

I think #854 addresses this.

@gibatronic :+1:

Cool, I think that node-sass should be quiet by default. What messages are we getting on a typical use case?
I think that warnings should be on by default, normal log should be off unless --verbose or -v is given.
Now:
[ ] https://github.com/sass/node-sass/blob/3d44ce88d5fcefbf70abb9e8b69eb98d06ffcc16/bin/node-sass#L293 (warn on file change - should be changed to log and quiet by default)
[ ] https://github.com/sass/node-sass/blob/3d44ce88d5fcefbf70abb9e8b69eb98d06ffcc16/bin/node-sass#L318 emitter.emit('warn', util.format('Wrote %s CSS files to %s', arr.lenth, outputDir)); should be log and quiet
Mainly this is about whether watcher should be quiet or not. Anything else that gets generated?

I think #856 proves nobody needs those messages :)

Glad I took a second look at this, I think we fell prey to the stdout is for output thing again.  If you passed --quite while using this you will get no output when using this in the unix fashion.
Render uses log to ouput when we don't have a dest file: https://github.com/sass/node-sass/blob/master/lib/render.js#L54
So you probably need to remove the one on log.

@saper For the --verbose thing, that would be a breaking change and would require a major version bump.  Personally I don't think it is necessary to make that change.  I think we should stick with --quite because it is helpful to know that something happened most of the time.
Also this is consistent other tools like gulp and browserify which output helpful confirmation messages when they do something.

Those sould simply go away in my opinion... https://github.com/sass/node-sass/blob/master/lib/render.js#L54
Re breaking change: we are still not at level 3.0.0, it's a good time to clean up logging!
As much as I would love to clean up stacktraces and debug messages, but that's a bit another store.
When redesigning logging we should keep also #646 in mind

Maybe we are not on the same page here, those lines enable you to pipe the output in a unix fashion.  So removing them would break this use case: $ node-sass file.scss | some-linting-program
The emit log there is actually the quite UNIX method you mentioned above.

Ok, let me actually try how it works...

Seems like the warns are what you want to get rid of by default. right @saper?

No, I think warns should be there, but some messages we have here don't qualify as a "warning". Maybe there is a problem with the default logging hierarchy.

The idea as I understand it now is this:

console.log (stdout): Actual program output, so the compiled sass
console.warn (stderr): Helpful debug messages, like how many files were compiled
console.error (stderr): Hard errors, probably stop execution

So the idea would be to make the console.warn lines off by default.  Then enable them with the --verbose flag.  Do I have that right?

Need to think about it a bit... node sends .log/.info to the stdout by default, which is "strange by UNIX standards". I need to think a little about what we have and try some things, will come back :)

@wesleytodd good carch on render emitting on log. Good :eyes: ! I'll fix that and add a test for it.
As per the grander conversation of quiet vs. verbose really just two ways of looking at the same thing. I've seen it both ways and I think both are valid. My 2¢:

reserve stdout for actual output at all times
Use stderr for warnings and verbose logging
Provide a way to turn off that logging (either by default, or via the quiet flag

Right?

@wesleytodd ok, updated it so that --quiet only removes warn messages. Also added a test to node-sass < in.scss that checks to make sure that everything still renders when you use --quiet
I think toggling off warn messages is what we really want this flag to do anyways. We don't ever call log from the cli itself, we only use warn for relaying information.
Totally willing to flip this pr so that it is a --verbose flag if that is where we want to go.

Personally I like how it works now.  But I can see the argument for it being more unix like with no output.  Maybe getting more core team members opinions would be good before making a decision one way or another?
@akhleung @am11@andrew @deanmao @kevva @nschonni Sorry if I bothered anyone who is not involved anymore, I just tagged the top ppl on the contributors list.

LGTM.
@xzyfer, IMO @wesleytodd and @paulcpederson  have better insights on CLI aspect.

LGTM.
IMO the average needs/wants a certain amount of output to know that something has happened. I'd be hesitant to go too quiet by default.
If I've followed the conversation correctly, I also agree that we current use warn incorrectly in many places where info would be better suited - that's a conversation for another PR.

Yes, unfortunately "warn" seems to be the lowest "stderr" level by default (maybe the emitter could change this). Also --watch makes things really different (this should be kind of verbose by default).

[--watch] should be kind of verbose by default

Agreed. I don't believe this PR changes that behaviour unless the --quiet flag is also passed.

Yep. This pr leaves the current behavior as is, just adds the ability to turn that off.
After #854 gets merged I'll rebase so that the tests pass.

@paulcpederson it is done!

@xzyfer nice! passing tests! Nice work @saper :+1:

:sob: :tada:

Merging this in preparation for the next beta release.
Great work @paulcpederson! Thanks for all your feedback @saper

:+1:

:tada:


(HTTP code 404) unexpected - {"message":"manifest for dashdb/local:latest not found"}

Expected behavior
Pull dock a IBM dashDB local docker image.
Actual behavior
(HTTP code 404) unexpected - {"message":"manifest for dashdb/local:latest not found"}
Information about the Issue
Steps to reproduce the behavior
https://hub.docker.com/r/ibmdashdb/local/
Deploying on Windows or Macintosh (SMP only)
Video: Perform a single-node installation on Windows using Kitematic
Deploying IBM dashDB Local on Windows or Macintosh requires a Linux VM, in which you run Docker. By downloading the Docker Toolbox, which includes a GUI and a VM, you can accomplish this easily.
Before you begin
Meet all of the prerequisites in dashDB Local prerequisites.
Clear your browser's cache.
Procedure

Start Kitematic and log in.

Click Docker CLI button, and delete the default VM.

docker-machine rm default

Create a new VM with sufficient memory and storage for the dashDB image. The following command creates a machine with a 40 GB virtual disk, 4 GB of RAM, and 1 virtual CPU, but you can increase the values if your system supports them:

docker-machine create -d virtualbox --virtualbox-disk-size "40000" --virtualbox-memory "4096" --virtualbox-cpu-count "1"  default

Restart Kitematic.

In the Kitematic GUI, click "My Repos" in the FILTER BY field.

Find the dashDB Local tile and click CREATE. You can use either the image that is tagged as "latest" or the image that is tagged as "<latest_version>-kitematic"; they are identical.

On the head node host, log in to the web console by using the web console URL that was provided after the successful completion messages. The URL is https://<head_node_IPaddress>:8443.

What to do next
Consider changing the default password for the bluadmin user, as described in Changing the dashDB Local bluadmin password.

Same here for a lot of images, selecting a specific tags works however.

Thanks.


Unable to place Crafting Upgrade into Crafter

Issue description:
Cant place "Crafting Upgrade" into Crafter.
What happens:
Just nothing, item cant be placed in the slot.
What you expected to happen:
Place upgrade into crafters upgrade slot.
Steps to reproduce:

Creating Crafting Upgrade
Open Crafter GUI
Desperately try to add crafting upgrade.
...

Tried with and without ressource pack loaded, restarted server,
Unlcaimed and unloaded chunks via FTBU.
Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge:
Refined Storage: 1.2.4

Does this issue occur on a server? [yes, hermit Pack]
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

Now that I think about it, why would you need a crafting upgrade in a crafter? The only valid ones are speed upgrades

The crafter does not seem to craft sub-craft processes. So I thought i need a craft upgrade so that he starts up to craft missing materials. Example 64k disk recipe with 64k memory + housing. Crafter does do the 64k memory thingie but not the housing.

Could you explain the process you go true for crafting? As maybe some screenshots? Cause I'm kinda confused as to what you are doing/expecting exactly

The 64k disk recipe is a 64k memory chip + a disk housing. I would expect the crafter to either craft with available parts or check if patterns are available for missing parts. However the crafter will not craft a disk housing, even though there is a pattern for it available.
I assumed this would be the case because there is no crafting upgrade, so without crafting upgrade the crafter only crafts with available materials and does not start sub-crafting processes for missing materials.

Yeah there is some issue with housing. I was fixed in #612

Well the generic issue is that a required material does not get crafted, despite a pattern being present.
Example: Void Upgrade pattern from StorageDrawers.
It requires an Upgrade Template and that requires a basicDrawer.
Despite having working patterns in the system to craft that the crafting system says components missing and does not allow to start the autocrafting order.

There is some issue miss matching nbt data, I will have to do some research on the best fix for this

I try to experiment a bit - as this behavior seem to not always (as in for all patterns with sub-crafting) happens.
I feel like StorageDrawers recipes are especially vulnerable - but unsure why and if that is really true for most of them. (Got Upgrade Template, Emerald and Void upgrade patterns with the issue).
I am setting up a bigger autocraft area currently, and hermitpack seems to have not so many alternatives. However if this is a general issue I would expect loads of issues reporting.

The what patterns are you using? Cause I can craft all of those items in my dev env. @Skar78

Tested more.
The Pattern for the Storage Drawer basicDrawer (oak, 1x32) is not used when another pattern requires it.
Further it is not even recognized when the basicDrawer is "on stock".
I redid the pattern with oredict enabled and it works now.

Interesting will look into the non-oredict issue.


Add a raw event with a callback

I am trying to add an event with two EventSignal (simple and ELECTRICITY_PRICE). But it seems that is not possible to do that using add_event method because it adds just one EventSignal per event. So I decided to use add_raw_event method, but then I realized that the callback is not being set on add_raw_event method.
https://github.com/OpenLEADR/openleadr-python/blob/2f68966b16b4b85efd16922787294802dac384f6/openleadr/server.py#L229-L238

Thank for reporting this. I just added support for the callback in version 0.5.14. Please try that version and let me know if it works for you.

Thank you @stan-janssen ! It worked well!


Allow durations without leading 0s in the hour

Fixes https://github.com/pydantic/pydantic/issues/8248
Supports the following formats:
>>> str(timedelta(hours=3))
'3:00:00'
>>> str(timedelta(minutes=3))
'0:03:00'
>>> str(timedelta(minutes=3, seconds=1))
'0:03:01'
>>> str(timedelta(days=3, hours=9, minutes=5, seconds=10))
'3 days, 9:05:10'

Note that this is technically a breaking change due to the change in error type when there are characters left over after parsing a duration, from InvalidCharTzSign to ExtraCharacters. I think this makes more sense as there is no such thing as a valid timezone for a duration.
I started down the road of trying to unify the time parsing between durations and times using PureTime, but it became a bit of a mess, requiring breaking changes to PureTime (e.g. PureTime stores hours as a u8 currently, but duration parsing needs at least u32).

The CI pre-commit system was failing due to trying to install pre-commit outside of a virtual environment. I copied the setup-python step from https://github.com/pydantic/pydantic-core/blob/main/.github/workflows/ci.yml#L265C1-L267C33 to fix.


Run Dialog is also not available but its not listed in the legacy features

Refering to following article : https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/enable-hybrid-experience

@minohimself
Please elaborate by what you mean by the Run dialog. Thanks.


gsoler2 Acrolinx quality push: troubleshoot.md

#assign: @robinharwood, @Xelu86
@robinharwood @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

No material changes, closing.


Still can't authorize access to my calendar

I have followed all of the instruction, but when I attempt to sync my calendar with TW, I get the following message:
Please visit this URL to authorize this application: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=2962XXXXXXXX-jja1pq86bu30jgdocfchn8j5XXXXXXXX.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8081%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar&state=SfLgzC3JOVZYhL0BWGGWsgXXXXXXXX&access_type=offline

I am not overly knowledgeable about google products and tools, so I am at a loss.

Hi @kcallis ,
For now you have to set up a new dev account on google for this to work as I haven't yet authorized the app.
Please follow these instructions and let me know if it doesn't work. https://github.com/bergercookie/taskw_gcal_sync#override-calendar-api-key


Fix typo in docs

GosSocket.unsubscribeToChannel should be GosSocket.unsubscribeFromChannel. Minor typo in docs that had me confused for a moment.

Thanks!


Handle conversion of complex objects inside Optional

When converting an input object to object value, complex input objects nested in Optional would cause an exception.
This change adds tests and fixes for both scenarios where a complex object value is defined and undefined.
Relates to #2114 #2133 #2153

@mvestergaard can you also add Optional<List<SomeObject>> to the mix?

Sure. I think it works, but I'll add it to the test to make sure.

Ok, good call.. Optional<List<x>> was broken too. I added a fix for that as well.
I also changed the mock verification to something a bit easier to understand when it fails.


incorrect cc_toolchain with bzlmod and Linux aarm64?

I want to use the buildbuddy toolchains only in CI for now.

ERROR: /home/peterkolloch/.cache/bazel/_bazel_peterkolloch/824dcaf761632cbc9a32ed7cf6ce3b6a/external/rules_rust~~crate~crates__backtrace-0.3.71/BUILD.bazel:87:19: While resolving toolchains for target @@rules_rust~~crate~crates__backtrace-0.3.71//:_bs_ (d995082): No matching toolchains found for types @@bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
ERROR: /home/peterkolloch/.cache/bazel/_bazel_peterkolloch/824dcaf761632cbc9a32ed7cf6ce3b6a/external/rules_rust~~crate~crates__libc-0.2.167/BUILD.bazel:65:19: While resolving toolchains for target @@rules_rust~~crate~crates__libc-0.2.167//:_bs_ (d995082): No matching toolchains found for types @@bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
ERROR: /home/peterkolloch/.cache/bazel/_bazel_peterkolloch/824dcaf761632cbc9a32ed7cf6ce3b6a/external/rules_rust~~crate~crates__eyre-0.6.12/BUILD.bazel:67:19: While resolving toolchains for target @@rules_rust~~crate~crates__eyre-0.6.12//:_bs_ (d995082): No matching toolchains found for types @@bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
ERROR: /home/peterkolloch/.cache/bazel/_bazel_peterkolloch/824dcaf761632cbc9a32ed7cf6ce3b6a/external/rules_rust~/cargo/private/BUILD.bazel:4:12: While resolving toolchains for target @@rules_rust~//cargo/private:copy_file (d995082): No matching toolchains found for types @@bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
ERROR: /home/peterkolloch/.cache/bazel/_bazel_peterkolloch/824dcaf761632cbc9a32ed7cf6ce3b6a/external/rules_rust~~crate~crates__proc-macro2-1.0.92/BUILD.bazel:66:19: While resolving toolchains for target @@rules_rust~~crate~crates__proc-macro2-1.0.92//:_bs_ (d995082): No matching toolchains found for types @@bazel_tools//tools/cpp:toolchain_type.
To debug, rerun with --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
If platforms or toolchains are a new concept for you, we'd encourage reading https://bazel.build/concepts/platforms-intro.
WARNING: errors encountered while analyzing target '//crates/hello_world:hello_world', it will not be built.
Analysis failed
INFO: Analyzed target //crates/hello_world:hello_world (204 packages loaded, 6261 targets configured).
WARNING: errors encountered while analyzing target '//crates/hello_world:hello_world', it will not be built.
Analysis failed
INFO: Found 0 targets...
ERROR: command succeeded, but not all targets were analyzed
INFO: Elapsed time: 3.107s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully

It seems to work both in CI (with --config remote) and on Mac OS ARM, though.

We just merged https://github.com/buildbuddy-io/buildbuddy-toolchain/commit/96323fd34cc72aacaad28d0e60489f64521c9eb6 which I think should fix this. Could you please update and let me know if the issue is gone?

@sluongng Yes, it does work on Mac OS ARM (without enabling the toolchain), on Linux ARM (in a VM without enabling the toolchain) and in CI Linux x86 (with buildbuddy toolchain).
🙏 👍

Thanks for testing it out. It's great to get this early report before we get this module into BCR 😅

Thank you for reacting so quickly and fixing my issue :)


Question regarding telemetry types

Hi and thanks for the awesome documentation!
I have one question regarding the DTDL documentation where it is saying that the telemetry @type should be Telemetry. But then when I read the samples I see a telemetry written as:
"@type": [
        "Telemetry",
        "SemanticType/Temperature"
      ],

I thought the type had to be the string Telemetry, but it seems that it is more capable than that. Is there any documentation regarding the Telemetry metamodel class?

Semantic types seems like an awesome idea, and something we will look more into. Where can I read more on these predefined semantic types, are they documented somewhere?
Regarding our domain, I cannot say that we have any semantic types yet, we are doing fine with the ordinary types we've got. I'll try to remember to get back to you when we discover a type that may be common for many use cases.

In the preview release, you can see and use semantic types in Azure IoT Central with preview features, described here. Azure IoT Central with preview features offers a free 7-day trial in the Central US and North Europe regions.
In Azure IoT Central, when you add a telemetry item or property to a plug & play interface, you can specify its semantic type. This is described in more detail in the Set up a device template how-to guide.


Update Cash'em All and Add Cash'em All Web

The app and the website version have two independent registration systems, so I think there should be two entries.

Thanks for your contribution!


Fixes 2024 12 take 1

Hello, here are some more miscellaneous patches for your review., do let
me know if these are correct or should be done differently.

Hello Madhu! Could you please add test cases for the modifications you've made to test.lisp? Since the current cffi-object works well with claw-raylib, I might not be fully aware of the contexts in which these changes are relevant. It would be great to have some intuitive test cases that demonstrate what didn't work in previous versions but does work in your submitted version.

I pushed the wrong commit, hopefully I've pushed the correct branch now.. Can you please delete the earlier files pushed on the branch.

It seems you are tackling forward references of structs, which was already supported in the previous version of cffi-object with define-prototype-cobject-class, but you need to define with (define-cobject-class <package-name>). The macro will sort the definitions based on the dependencies among the structural types within that package.

The proposed patch only fixes a type mismatch in the implementation.


Add components in topology related query

Following https://github.com/apache/skywalking/pull/10522#issuecomment-1463211623
add components for sub-commands: dependency endpoint, dependency service, dependency instance

Codecov Report

Merging #175 (bd478b9) into master (838e222) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head bd478b9 differs from pull request most recent head 9f1cd09. Consider uploading reports for the commit 9f1cd09 to get more accurate results

@@           Coverage Diff           @@
##           master     #175   +/-   ##
=======================================
  Coverage   25.86%   25.86%
=======================================
  Files          22       22
  Lines         460      460
=======================================
  Hits          119      119
  Misses        329      329
  Partials       12       12

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[stable/datadog] allow for setting annotations on cluster checks pod

Signed-off-by: Joe Hohertz<EMAIL_ADDRESS>@hkaj
@irabinovitch
@CharlyF
@mfpierre
@clamoriniere
@xlucas
What this PR does / why we need it:
simply allows specifying podAnnotation for clusterChecks deployment, as is allowed for other components.
Which issue this PR fixes
none known
Special notes for your reviewer:
none
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

Not sure what the linter is on about.... there was previously a space, but this has been addressed, and it is continuing to flag a now fixed problem.

/ok-to-test

@jhohertz
Would you mind to resolve chart conflict please? Thank you.
stable/datadog/Chart.yaml
stable/datadog/README.md

/assign @xlucas

Rebased and addressed feedback

Hi there, sorry for the delay, could you rebase again on master? I'll merge it right away when there's no more conflict.

Rebased


Let players and monsters have images

Combatants -- both players and monsters -- should be able to have an image URL associated with them for direct display in a browser or in the player view. This should be added to the various templates as well as existing data, and should be an empty string by default.
It might be nice to also support relative paths on disk in case we want to start bundling monster images with content packages. This would allow offline play without internet access (though that's probably not a huge priority in the age of social distancing, but just in case...).

Added the image directory creation to the new content script and to the example content pack.

Making progress!
See:

146396fce0e00c803526cd511a72e3e7a6ef2e93
bef7c58bf3c8ca1d725d63d6aca5aab488dc5bb2
5c1bb0c03550c6b1962167fedc5d0cfb2c8ac8b5

A reasonable first draft of this is now done! Yay!


Summon Foliot: Janitor Summons Pig

Describe the bug
Summon Foliot: Janitor Summons Pig
To Reproduce
Steps to reproduce the behavior:

Perform the ritual

Expected behavior
I expected a janitor but got a pig.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):

Occultism Version:  1.9.2
OS: Windows 10
Minecraft Version: 1.16.5
Modpack Link and Version, or list of mods: Verified in empty modpack. Just occultism

I'm so sorry but this is hilarious haha.
Copy paste error in the recipe!
Fixed in #362

oh Jeeze. I failed at bug reporting. Sorry! I didn't see you already had it dealt with. I need more coffee.


Can we have a fade animation similar to that on the Navigation component?

Version
Tell us which versions you are using:

react-native-router-flux v3.35.0
react-native v0.31.0

Expected behaviour
when using the typical navigation component. It allows you to have multiple options for transitions. One of them is the Navigator.SceneConfigs.FadeAndroid transition which looks good. I expected the fade animation on the react-native-router-flux to behave the same.
Actual behaviour
The animation on the RNRF casts a white box border around the screen that looks funky and detracts from the content of the page. It doesn't look as polished as the Navigator.SceneConfigs.FadeAndroid one.
Steps to reproduce

Create two scenes with the animation={'fade'} property on both of them
try to transition between the two scenes (use a button or something). you should see the apparent white border during the transition between the two pages. (I tested this on an iPhone simulator and on my personal Nexus 5 phone)
3.

Hi Mohamed,
same problem for me, solved in this way (I think was a shadow lag):
const getSceneStyle = ( props, computedProps) => {
const style = {
flex: 1,
backgroundColor: '#000000',
shadowColor: null,
shadowOffset: null,
shadowOpacity: null,
shadowRadius: null,
};
return style;
};
<Router scenes={scenes} getSceneStyle={getSceneStyle}  .......
Hope this works also for you!!!
Woody

Hi @woody87
That code didn't work for me. seems scenes function is undefined on me. Hope you please show how scenes function looks like.
And why we need passing (props, computedProps) for getSceneStyle ?
Thanks.


Bucket reconciliation takes too long

I'm publishing charts to an S3 bucket using the helm-s3 plugin. The objects in the bucket are versioned, and the bucket is located in eu-central-1.
I have a flux2 (v0.21.2) deployment in a cluster running in ap-northeast-1 and when I add a bucket resource, using the global S3 endpoint (which I'm hoping to keep using for simplicity), it takes over 8 minutes to reconcile, which is unacceptable for our workflow.
The bucket contains 944 objects spread across 5 prefix delimited by object prefix, hence there will be 5 index.yml files and the rest of the objects are gzip'ed charts. The total size of all of the objects is under 12mb, where no single object exceeds 300kb.
I attempted to run the source-controller with debug logs, but I didn't notice any additional output regarding the bucket reconciliation. A while after triggering reconciliation, I get a message like:
{
  "level": "info",
  "ts": "2022-05-25T17:20:09.845Z",
  "logger": "controller.bucket",
  "msg": "Reconciliation finished in 8m3.722519948s, next run in 5m0s",
  "reconciler group": "source.toolkit.fluxcd.io",
  "reconciler kind": "Bucket",
  "name": "<redacted>",
  "namespace": "flux-system"
}

My bucket resource is defined as follows:
apiVersion: v1
items:
- apiVersion: source.toolkit.fluxcd.io/v1beta1
  kind: Bucket
  metadata:
    annotations:
      reconcile.fluxcd.io/requestedAt: "2022-05-26T09:55:58.303925+00:00"
    name: <redacted>
    namespace: flux-system
  spec:
    bucketName: <redacted>
    endpoint: s3.amazonaws.com
    interval: 5m
    provider: aws
    region: eu-central-1
    timeout: 600s
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

I ran a sidecar container with the AWS CLI and found that syncing the bucket takes only a few seconds.
This delay in reconciling frequently results in HelmChart resources getting stuck in a failure state and preventing timely updates of releases.
Could you please advise on where my bottleneck might be, and how I might mitigate/resolve?

Please upgrade your clusters to latest Flux (v0.30.2) then in Git bump the API version of all your Flux sources (GitRepositories, Buckets, etc) to source.toolkit.fluxcd.io/v1beta2. The Bucket implementation in v1beta2 comes will many improvements so hopefully is solves your issues.

Flux (v0.30.2) running source-controller (v0.24.4) reconciles the same bucket source in under 15 seconds. Thank you very much for the support.