Incorrect type definitions

https://github.com/rob3000/nestjs-kafka/blob/2c560e38e91b1e4994c6c13add47fb2f0b55f182/src/serializer/avro-request.serializer.ts#L7-L13
value is marked as required but for the scenario that schemas are managed centrally and not stored within the project, it is not needed.

So value can be the value itself such as the avro file otherwise its the avro schema value. This allows you to specify a different  schema name for the value compared to the key and topic. For example say you have the following schemas:

my.topic.payload
my.topic.key
you would then define this values as my.topic.payload.

Hope that makes sense? Will update the docs to reflect this.

Deffo makes sense for me, but I think the wording should be subject as this is the value which changes after your description. Anyways, the value option needs to be marked as non-required.


Parameter passing problem of DAP

I am trying to interact with the "nodeDebugAdapter" debugger using the DAP protocol.
Send an initialization request and set the value of "AdapterId" and "PathFormat".
But the “args.adapterID” received by the server is undefined.The reason is that "AdapterId" and "adapterID” do not match
/*this is client code*/
var client = DebugAdapterClient.Create(options => {
                options.WithInput(_process.StandardOutput.BaseStream).WithOutput(_process.StandardInput.BaseStream);

                options.AdapterId = "nodejs";

                options.PathFormat = "path";
            });

            await client.Initialize(cancellationToken);`

`
/*this is server code*/
initialize(args) {
            this._adapterID = args.adapterID;
            this._promiseRejectExceptionFilterEnabled = this.isExtensionHost();
            this._supportsRunInTerminalRequest = args.supportsRunInTerminalRequest;
            if (args.locale) {
                localize = nls.config({ locale: args.locale })(__filename);
            }
            const capabilities = super.initialize(args);
            capabilities.supportsLogPoints = true;
            capabilities.supportsTerminateRequest = this.supportsTerminateRequest;
            return capabilities;
        }
`

Thanks @pengsongkun741 !
Looks like that's a miss on my part, getting a PR together update the serialization name.

I also noted clientID was also incorrect, this has been fixed as well.
If you have a chance to review this PR https://github.com/OmniSharp/csharp-language-server-protocol/pull/475 and let me know if you have any feedback!


KAFKA-6771. Make specifying partitions more flexible

retest this please

Failed test is org.apache.kafka.clients.admin.KafkaAdminClientTest.testDescribeConsumerGroupOffsets, not related

retest this please


[mesheryctl]: Interactive Pagination for mesheryctl filter list #10366

Signed-off-by: Satya Pavan Kalyan V<EMAIL_ADDRESS>Notes for Reviewers
This PR fixes #10366
Signed commits

[X] Yes, I signed my commits.

@vpavankalyan Let's discuss this in Meshery dev call today. Add this as an agenda item to the meeting minutes, if you would :)

@vpavankalyan Are you still working on this PR?

Due to lack of response to reviews from the maintainer over an extended period, we're closing this PR. While it addressed the issue, timely review is crucial. We appreciate your contribution and encourage ongoing engagement.


zbxtg.py stopped working, error 104 - Connection reset by peer

Hi!
Suddenly zbxtg.py stopped to send notifications. Manual debug for old script and for up-to-date version is attached.
https://gist.github.com/highlandy/77c8d98a59968eb465a006c18ccf41f6 - old
https://gist.github.com/highlandy/575dbca14973c0ef6e3accb6bae550ed - new

Already checked, it's fine. How do I know where exactly connection is dropped?

check the availability of api.telegram.org

It's available.
telnet api.telegram.org 443
Trying <IP_ADDRESS>...
Connected to api.telegram.org.
Escape character is '^]'.

Going to test connection via proxy, will let you know.

You were right, something in between blocked messed connection.
Using new script via proxy resolved my issue, thank you for supporting!


Make aliases affect both-prefixed and safe-prefixed declarations

This pull request makes aliases being taken into account for both-prefixed and safe-prefixed declarations. In this way if a declaration needs to be moved to a prefixed rule with the bothPrefix, either because it can be overriden or because the safeBothPrefix rule is set, it will do the same with an alias of such a declaration.

coverage: 100.0%. remained the same
when pulling ffa7bade50d836254f1afa44775cee84f6d7bea4 on make_aliases_affect_safe_prefixed_rules
into bd5ea0c143c261b99234261d544269a028bead50 on master.


Fix nexus config path and that the file exists

Nexus uses different configuration files for v2.x, 3.0.x and >3.1.0
Additionally, the configuration file may not exist on a >3.x
installation which will cause failures unless a minimal file is created
Signed-off-by: Andrew Grimberg<EMAIL_ADDRESS>

@PaulFurtado thanks for the heads up. I hadn't seen that it failed. I would have run the spec tests locally, but for some reason I can't get the environment setup cleanly to do so :(
Amended fix pushed since it would be silly to have two changes with one of them just being a typo fix.

@tykeal Thanks!

This is in release 1.7.2


Register 0.2.2

@JuliaRegistrator register
Fixes for SimplePolynomials and SimpleRationalFunctions. Added nullityx.

Registration pull request created: JuliaRegistries/General/96181
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" e62cc413d4732b0b88f0c6e2fce5221ba44eb7b2
git push origin v0.2.2


Light theme support?

I use either the light theme or the dark theme, but I don't want to mix them up.
When I switch to a light theme, the windows of this extension remain dark.

I did not read 8c55bc2

yes it's not cool - not only does it not respect light theme setting, it also mostly ignores the color scheme of the currently selected global theme and just ships its own colors everywhere. The main problem is the branch colors - finding a set of colors that look okay-ish both on a dark and on a light background is difficult, and I in particular am pretty bad at these kinds of things, so I gave up.
However, as always, it would be better if theme alignment could still be enabled with a setting at least, so I will do that for the next update.

The PR I've uploaded is PoC of using filters and here is an example:


Fix low-level and legacy HTTP API

OCSP HTTP: Restore API of undocumented and recently deprecated functions:  Restore parameters of OCSP_REQ_CTX_new(), OCSP_REQ_CTX_http(), OCSP_REQ_CTX_i2d().
  Fix a bug (wrong HTTP method selected on req == NULL in OCSP_sendreq_new().
  Minor further fixes in OSSL_HTTP_REQ_CTX.pod

Fixes #13873.

OSSL_HTTP_REQ_CTX.pod: minor addition and remove redundant paragraph
 OSSL_HTTP_REQ_CTX_new(): replace method_GET parameter by method_POST
rename OSSL_HTTP_REQ_CTX_header to OSSL_HTTP_REQ_CTX_set_request_line
Add check of HTTP method to OSSL_HTTP_REQ_CTX_content()
Util/Pod.pm: Fix uninitialized $podinfo{lastsecttext} on empty input

Checklist

[x] documentation is added or updated

Un-deprecate OCSP_REQ_CTX_set1_req() because it is helpful also for internal use.

Er, internal use isn't a reason to undeprecate it...

Un-deprecate OCSP_REQ_CTX_set1_req() because it is helpful also for internal use.

Er, internal use isn't a reason to undeprecate it...

This pull request is ready to merge

This pull request is ready to merge

Merged - thanks @levitte

Merged - thanks @levitte

I just so happened to have a look at 1.1.1 vs master for these things, and well, it seems you missed a spot:
1.1.1:
int OCSP_REQ_CTX_nbio_d2i(OCSP_REQ_CTX *rctx, ASN1_VALUE **pval,
                          const ASN1_ITEM *it);

master:
#   define OCSP_REQ_CTX_nbio_d2i(r, i) \
        OSSL_HTTP_REQ_CTX_sendreq_d2i(r, i)

The number of arguments differ...

The fix turned out to be very simple.  #14196


[Q] why are there no source distributions on pypi for 0.17.x?

I'm working on building a distribution that includes wandb, and I need to build from source. I see there are no sdists on pypi.org for versions after 0.16.4. Is that intentional, or an oversight?

Hi @dhellmann , let us check this internally and will get back to you for an update.

Thanks, @JoanaMarieL!

Our pleasure to help @dhellmann , our Eng Team is aware of this and will keep you posted for any progress.

@dhellmann sorry for the issue here, we change our release process and we are working on resolving this. In the short term, we do upload all the source code to github releases, wonder if that could be a temporary workaround, until fix this issue?
I will be updating this thread, but we are optimistic to get a fix for this issue before the next release.

Hi, @kptkin , the tool we're using for this build works mostly automatically with sdists. We do have the ability to configure builds from GitHub release archives.
What's your release schedule like? If it's going to be sort of soon, I might just wait, instead of doing the extra coding that would be needed to consume a release archive.

Hi, @kptkin , the tool we're using for this build works mostly automatically with sdists. We do have the ability to configure builds from GitHub release archives.
What's your release schedule like? If it's going to be sort of soon, I might just wait, instead of doing the extra coding that would be needed to consume a release archive.

We are planning to have it fixed in a week or so.

Hi, @kptkin , the tool we're using for this build works mostly automatically with sdists. We do have the ability to configure builds from GitHub release archives.
What's your release schedule like? If it's going to be sort of soon, I might just wait, instead of doing the extra coding that would be needed to consume a release archive.

We are planning to have it fixed in a week or so, basically want to fix it before the next release in any case as we don't want to break more workflows

OK, that sounds good. I'll see what our schedules look like, and then my team can decide what we need to do internally.
Thank you for keeping me informed!

Thank you!

The next release will include a source distribution! It requires Go to build from source, but you can temporarily skip the Go step by setting the WANDB_BUILD_UNIVERSAL environment variable to "true".

I spotted the go dependency, that's a fun one. :-)
For our project, we're trying to build everything fully from source for secure builds, but also fully optimized so we can give the best performance. Having the sdists should make that easier, so thank you, again!

Hello @dhellmann , you are most welcome. ~

Source packages were published for 0.17.6
https://pypi.org/project/wandb/0.17.6/
wandb-0.17.6-py3-none-any.whl
wandb-0.17.6-py3-none-macosx_10_14_x86_64.whl
wandb-0.17.6-py3-none-macosx_11_0_arm64.whl
wandb-0.17.6-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
wandb-0.17.6-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
wandb-0.17.6-py3-none-win32.whl
wandb-0.17.6-py3-none-win_amd64.whl
wandb-0.17.6.tar.gz


CA deployments are not exposed in Kubernetes. Kubectl command is required to manually add them.

Describe the bug
In the deployment process using , the ca deployments for all organizations are not exposed so they pods are not visible to the rest of the network. I need to manuall add them using:
kubectl expose deployment ca --type=ClusterIP -n ORG1-net
kubectl expose deployment ca --type=ClusterIP -n ORG2-net
To Reproduce
Steps to reproduce the behavior:

Deploy the network from bevel running in a local docker instance using: ansible-playbook  platforms/shared/configuration/site.yaml -e<EMAIL_ADDRESS>Wait for the pause for CA generation time. Verify that no CA deployment is exposed.
Network will fail as CAs are not accessible to the rest of resources in the namespace, given they are not exposed as ClusterIP (nor any other type, Nodeport, ...)

Expected behavior
Commands indicated above should not be required to have CAs exposed in the internal IP network of the cluster.
Environment (please complete the following information):
Azure AKS
Hyperledger Fabric 2.2.2
2 Organization network, one orderer one peer.

@icordoba This is happening with haproxy or no proxy?

No proxy. (BTW, no errors or warnings shown in the process)

CA servers are deployed correctly when using the charts in platforms/hyperledger-fabric/charts/ca. This has been tested with latest code and no proxy setting.


Have azure-core models implement JsonSerializable

Description
This PR updates JSON serializable model types in azure-core to implement JsonSerializable. This will result in them preferring azure-json for serialization instead of Jackson Databind when used with JacksonAdapter and is a stepping stone into the full removal of Jackson Databind from azure-core.
To support the changes in azure-core, azure-json's JsonReader added a new API getRawText() which returns the JSON encoded and escaped text that is the raw value for the token type being read.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-core


Add dialog backdrop color transition

https://stackoverflow.com/a/71984473/528136

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


(PT-1027) Add desired policy storage

This may be roughly right, and I'm raising it so that the other policy storage can go ahead and build upon it, relying on config/experimental-features and the support for migrations with :strict-order?.  I've marked it as a work in progress because I still need to add some tests, and we need to decide if we want to move the migration-table related changes to 6.x.

Oh, and also need to decide if we really want/need the changed timestamp index right now.  We might not.

This also needs to wait until we resolve (and presumably merge up) #3647.

Closing because the effort has been suspended.


Read time-out

Hi,
While trying to connect the unit 100-CPND004 with the dongle in a rpi3 (deban 10) I am getting a time-out in modpoll. I set up the thermostat in Int mode 49. Am I missing anything? Should I use another int mode number?

It works perfectly. Issue was a bad wiring on the device


readmi.md

hi, can i contribute to your readmi and make it more readable

@GiulianoOrtego We'll be sure to reach out if we need that. At the moment, we're okay with the simple README we have.


Migrate UTXO chaincode to new API and hyperledger name

This makes changes to

The UTXO chaincode to support the new API
The UTXO chaincode README so that the instructions match the new hyperledger name

@noamher With these fixes, I was able to deploy the UTXO chaincode.

Signed-off-by<EMAIL_ADDRESS>

@binhn or @rfajta - please review and merge when you have a chance. thanks.


Add Secrets via API on hf_api

Since now it's possible to add Secrets via API it would be nice to have this added to the library.
curl 'https://huggingface.co/api/spaces/$namespace/$repo/secrets' -X POST -H 'Authorization: Bearer $access_token' -H 'Content-Type: application/json' --data-raw '{"key":"$key","value":"$value"}'

delete (-X DELETE)

Since they're similar, maybe we could also add setting the hardware flavor into the api
curl 'https://huggingface.co/api/spaces/$namespace/$repo/hardware' -X POST -H 'Authorization: Bearer $access_token' -H 'Content-Type: application/json' --data-raw '{"flavor": "t4-medium"}'

These are two ending points that we're using on this Space Space creator https://huggingface.co/spaces/anzorq/sd-space-creator
maybe it could args inside the create_repot method?
create_repo(
    repo_id=model_id,
    exist_ok=update,
    repo_type="space",
    space_sdk="gradio",
    flavor="t4-medium"
    secrets={"SECRETA":"asd", "SECRETB":"asd"}
)

Thanks @radames for the suggestions ! This makes indeed a lot of sense. I played a bit with the Spaces API to see what we can include in huggingface_hub. The HTTP endpoints seem quite complete already as we can:

get current state (GET /runtime): RUNNING, BUILDING,...
get current and requested hardware (GET /runtime)
get current secrets (GET /secrets)
set new secret (POST /secrets)
delete secret (DELETE /secrets)
request new hardware (POST /hardware)

1. What do you think about a few new helpers in HfApi ?
class SpaceConfig:
    secrets: Dict[str, str]
    current_state: Literal or Enum
    current_hardware: Literal or Enum
    requested_hardware: Literal or Enum

class HfApi:
    (...)

    def get_space_config(repo_id: str) -> SpaceConfig:
        (...)

    def request_space_hardware(repo_id: str, hardware: Literal) -> None:
        (...)

    def set_space_secrets(repo_id: str, secrets: Dict[str, str]) -> None:
        # Handles both additions and deletions
        # Each addition/deletion is atomic so this method would not be transactional
        # (e.g.: might end up in a weird state if it fails)

    def add_space_secret(repo_id: str, key: str, value: str) -> None:
        # Atomic update

    def delete_space_secret(repo_id: str, key: str) -> None:
        # Atomic update

2. Additional suggestion: a less verbose SpaceApi
Otherwise I'm starting to consider the idea of having a SpaceApi object. Something like this (really just an suggestion):
api = HfApi(token="hf_***").space(repo_id="...")

api.get_config()
api.request_hardware("t4-medium")
api.set_secrets({"foo": "bar", "hello": "world"})
api.add_secret("foo": "bar2")
api.delete_secret("foo")

We wouldn't have to repeat the repo_id and space all the time. This suggestion is a bit orthogonal and could be done later (it is more a design decision at this point since we could do the same for models and datasets as well).
WDTY ? (also cc @LysandreJik @osanseviero)


fixes stevebest/passport-vkontakte#16

Wrapper to return email in profile. https://github.com/stevebest/passport-vkontakte/issues/16
Sometimes you cannot get email via params (if you don't have control over verify function).
E.g. it will add email for https://github.com/strongloop/loopback-component-passport

Hey, Stanislav!
I finally got time to properly review and test this PR. It kinda worked, aside from the issues with passReqToCallback, which I had to forcefully set to false.  :)


refactor visual designer to use extension pattern

WIP

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2586


No autocomplete for as_i32_ref

is NumRef defined in the function where the impl is, or is it outside? In the latter case I think this behaviour is currently expected due to technical reasons

The latter one :(

Actually AFAIK we look for impls in the same block as the method call? The only thing that doesn't work is using impls defined in a completely unrelated block. So there seems to be some bug here.

It seems to be a completion problem; I can reproduce the missing completion, but if you write the method call the return type gets inferred correctly.


[DotNet extensibility] CellData.HyperLink

We've built an extension that is able to read / process complex Excel files, fully driven by Excel buffer only.
The Excel files are received from external large international suppliers and are / can / should not be manipulated by any tools (Azure Functions / Power Automate / ...) before importing. Adding extra layers to the import stage to 'transform' Excel files adds extra costs (Azure) / complexity to deploy / maintenance / delay / ...
Goal is to be able to import excel data in BC without using external tools / extra archictecture. This works fine, except for cells containing a hyperlink (link to product catalog, manuals, images, ...).
Our request is to be able to extract the hyperlink from a cell.

We're not able to add this ourselves, since the dotnet CellData object is maintained by MS.
"Microsoft.Dynamics.Nav.OpenXml.Spreadsheet.CellData"; "CellData"

Idea would be to :

Add new field to Excel Buffer table

field(x; "Hyperlink"; Text[1024])
        {
            Caption = 'Hyperlink';
            DataClassification = SystemMetadata;
        }

Add new Hyperlink property to CellData

Value can be calculated probably using code below
If Cell.Hyperlinks.count Then
'Return the address if there is at least one cell selected
Hyperlink = Cell.Hyperlinks(1).Address

Fill the Hyperlink value upon reading the Excel sheet (ReadSheetContinous)

if CellData.HasValue then begin
    Validate("Row No.", CellData.RowNumber);
    Validate("Column No.", CellData.ColumnNumber);
    ParseHyperLink(CellData.HyperLink); // <<<<
    ParseCellValue(CellData.Value, CellData.Format);
    Insert;

Would you want to do contribute this in the BaseApp contribution pilot?

Turns out, we cannot build this in the application alone :-( Unfortunately, we hence cannot process this as an extensibility request, as it requires changes to the platform too. Please create a BCIdea instead.


Subjects of a collection url returns all subjects

"/subjects?collection_id=x" currently returns all subjects in database

I assume this is a paged response?
This is linked to #764

Would adding a collections link to the subject response be viable as well? I'd love to have a direct way to also go from a subject response to knowing what collections it's a member of

Thanks!!

@aweiksnar - try the param `?include=collections, you should get links then. Ref. https://github.com/RestPack/restpack_serializer#side-load-related-songs


Add new rule: no-comment-textnodes

Our team has run into issues where people mistakenly commit comments as text nodes, and they have managed to get through code review and appeared (embarrassingly) in our UI. I threw together this rule to try and catch such occasions, and thought it might be useful to other users of this ESLint plugin.
Feedback, comments greatly appreciated.

What about false positives where the literal JS comment text is what's desired?

@ljharb – They have two choices. Either disable the rule, or do:
<div>{'// Not a comment'}</div>

I personally think that's acceptable. This strikes me as a particularly rare edge case.

@benvinegar want to add documentation for the rule, and include that info in it explicitly? :-D

@ljharb – Updated with documentation.

Coverage increased (+0.01%) to 96.783% when pulling 67071327da03f2675eda2890e7abe820f3d4883d on benvinegar:no-comment-textnodes into 82b3aa9101aa2124b934add61734cec026b4c278 on yannickcr:master.

Coverage increased (+0.01%) to 96.783% when pulling 2e275589a9346964d7831cf84a36db8891cfeba6 on benvinegar:no-comment-textnodes into 82b3aa9101aa2124b934add61734cec026b4c278 on yannickcr:master.

Coverage increased (+0.01%) to 96.783% when pulling 2e275589a9346964d7831cf84a36db8891cfeba6 on benvinegar:no-comment-textnodes into 82b3aa9101aa2124b934add61734cec026b4c278 on yannickcr:master.

Seems to be a useful rule. Merged, thanks!

a bite late, but: shouldn't the name of the rule be prefixed with jsx-?

I agree that this rule should have been prefixed with jsx-.


Is the IOMMU serve as a part of an EP device to provide services for the device itself, or is the IOMMU serve as an EP function for other EP devices?

In Chapter 7, there are the following sentences:
https://github.com/riscv-non-isa/riscv-iommu/blob/main/iommu_hw_guidelines.adoc?plain=1#L8
The IOMMU may be constructed as a PCIe device itself and be discoverable as a dedicated PCIe
function with PCIe defined Base Class 08h, Sub-Class 06h, and Programming Interface 00h

This sentence seems to mean that the IOMMU can be an EP device and serve other EPs.
Traditionally, the request sent by the device passes through the IO bridge, and the IO bridge operates the IOMMU to complete the address conversion, and sends the converted result to the interconnection bus. The address routing sent by the device is easy to understand, the device request is passed through the IO bridge and IOMMU.

What we don't understand is here:
If the IOMMU serve as an EP function for other EP devices, however, when a EP serves as an IOMMU for other EPs, there is no reason for other EPs to perform address translation through the IOMMU from the hardware connection.
If the IOMMU serve as a part of an EP device to provide services for the device itself, however, the device can use the IOMMU itself, and does not need to provide a function to inform the outside world that there is such a function，which has IOMMU.
Could you please give me some explanation? thank you very much.

It says the IOMMU may be a PCIe device - similar to how a IO-bridge/host-bridge is a PCI-PCI bridge device. The operations of the IOMMU are as documented in the specification and shown in the picture above. The IOMMU when built as a PCIe function is generic system peripheral with class code as defined in PCIe specification - see section 1.9

It is reasonable to say that this IOMMU is used to process the translation request of the EP mounted on the Secondary PCI BUS. Thank you very much.


Automated cherry pick of #10808: fix(region): convert eip with same project with vm

Cherry pick of #10808 on release/3.7.
#10808: fix(region): convert eip with same project with vm

Codecov Report

Merging #10809 (c79495d) into release/3.7 (0ff3997) will decrease coverage by 0.40%.
The diff coverage is 1.15%.

@@               Coverage Diff               @@
##           release/3.7   #10809      +/-   ##
===============================================
- Coverage         5.98%    5.58%   -0.41%
===============================================
  Files              848      518     -330
  Lines           131795    90237   -41558
===============================================
- Hits              7887     5036    -2851
+ Misses          123206    84801   -38405
+ Partials           702      400     -302

Flag
Coverage Δ

aFlag
5.58% <1.15%> (-0.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apis/const.go
0.00% <0.00%> (ø)

pkg/apis/input.go
0.00% <ø> (ø)

pkg/apis/list.go
0.00% <ø> (ø)

pkg/appsrv/appsrv.go
44.32% <0.00%> (-4.35%)
:arrow_down:

pkg/baremetal/tasks/stop.go
0.00% <0.00%> (ø)

pkg/cloudcommon/notifyclient/events.go
0.00% <ø> (ø)

pkg/cloudcommon/notifyclient/notify.go
0.72% <0.00%> (-0.45%)
:arrow_down:

pkg/cloudcommon/notifyclient/notify_internal.go
0.00% <0.00%> (ø)

pkg/cloudcommon/validators/validators.go
62.39% <0.00%> (-0.69%)
:arrow_down:

pkg/cloudcommon/notifyclient/template.go
7.04% <7.04%> (ø)

... and 453 more

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 7c12d40...c79495d. Read the comment docs.


[Enhancement] Send NavRoute data on journal schema.

The NavRoute.json file, written when a journal NavRoute event occurs, contains:

System Name
System co-ordinates
SystemAddress (id64)
Main star's class

for each step in the plotted route.  It would be simple to take the route array out of the file and insert it into the journal event before sending that over EDDN.  Then any listeners could choose to utilise it to potentially gain co-ordinates and systemaddress for extra systems.
As the provided data in the route array is what is currently required as the bare minimum in a journal schema message this shouldn't actually require any changes to the schema other than adding the event type to the allowed list.  This issue mostly for reference and any further discussion.  It would require a small update to the documentation to explicitly state that the route array needs adding from the file.

Superseded / replaced by #133.


Only one SA Secret is looked for

When multiple Secrets are bound to a ServiceAccount, the tool doesn't look for all.

Ref #3


Investigate CSV drag and drop issues

When dragging a csv on the map, there is an error message:

No CSV to test with


COMMUNITY MONEY (CMMO)

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ] Filename in the lowercase format
[ ] Image format: png
[ ] Image size: 256 by 256 px

Added here https://github.com/TrustWallet/tokens/commit/c0bf5e7f9d58c919112c13abc84b01b23637510d


Fix bug in the provider we create in scala_library/binary/rest

scala_* rules create java_provider with compile_jars in transitive_compile_jars
@johnynek we saw internally that with a scala_library depending on a scala_import depending on scala_library  (somewhat similar to bazel-deps replacements mode) the compile jars of the root scala library dep aren't propagated. Only its transitive compile ones.
I initially fixed it in scala_import but then I suspected the root problem is with the scala rules themselves.
I added two tests that show it and actually removed the crutches we had (scala.bzl and custom_jvm_rule) which did it themselves. This was a problem since every passing rule type needed to implement it themselves (like scala_import which is how I caught this).
@damienmg @lberki @dslomov @iirina
FYI- The current state of the create_provider is causing a massive amount of pain and bugs.
We have so much code and tests around it and still sometimes fall over...

@johnynek
Can you review?
This is a big bug so I'd like to merge this as soon as possible

Sorry I lost track of this.

Sure.
If you have feedback I'd still love to hear it.
Take into account though that the whole create_provider api is being
completely revamped right now so the smartest move is probably to hang
tight and wait for it to land.
On Wed, Dec 13, 2017 at 7:46 AM P. Oscar Boykin<EMAIL_ADDRESS>wrote:

Sorry I lost track of this.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/pull/361#issuecomment-351289836,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF9hOGkKkIVZTqpRgBo5mKXBo0FcMks5s_2S8gaJpZM4Q3nnU
.


New and improved installation documentation

Still missing:

[x] update docs for 0.9.0
[x] NixOS installation docs
[x] nix-darwin installation docs

:heavy_check_mark:

:information_source: the part for user_docs/proxy.rst  Importing SSL certificate for Chrome might be required to be updated regarding here.


How to set multiple cookies pair from the response header

My reponse header includes access token, refresh token and some other flags as a cookie set, but when i try to set cookies using setFromResponse method, it's just saving the first cookie only
My Reponse cookies
access_token_cookie=eyJ0eXAiOiJKV1QiLCJ; Expires=Sun, 04-Apr-2021 12:54:59 GMT; Max-Age=3154; HttpOnly; Path=/; SameSite=None, csrf_access_token=8ee44170; Expires=Sun, 04-Apr-2021 12:54:59 GMT; Max-Age=31540; Path=/; SameSite=None, refresh_token_cookie=eyJ0; Expires=Sun, 04-Apr-2021 12:54:59 GMT; Max-Age=31540; HttpOnly; Path=/token/refresh; SameSite=None, csrf_refresh_token=351ede70-ab4d-; Expires=Sun, 04-Apr-2021 12:54:59 GMT; Max-Age=3154; Path=/; SameSite=None, logged_in=true; Path=/; SameSite=None, session=eyJ1cmwiOiIMOMjyTd150Pj3L5v0; Path=/; SameSite=None
But in my application only first cookie is stored

same

Hello
Did you solve this problem?

This also seems to be happening in my project. Has anyone found a workaround?


Update API Docs: Notification Endpoint

API doc: https://github.com/department-of-veterans-affairs/notification-api/blob/master/documents/openapi/openapi.yaml
/v2/notifications/{notification_id}
We want to ensure this accurately describes the capabilities and supported fields.

[ ] Review for accuracy and make necessary updates
[ ] Ensure that all possible fields are called out
[ ] Include additional example bodies to accurately reflect options (e.g. email vs sms vs push)

Folks,
{
  "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "body": "string",
  "completed_at": "2022-11-23T20:21:50.480Z",
  "created_at": "2022-11-23T20:21:50.480Z",
  "created_by_name": "string",
  "email_address"<EMAIL_ADDRESS>  "line_1": "string",
  "line_2": "string",
  "line_3": "string",
  "line_4": "string",
  "line_5": "string",
  "line_6": "string",
  "phone_number": "+16502532222",
  "postage": "string",
  "postcode": "string",
  "recipient_identifiers": [
    {
      "id_type": "VAPROFILEID",
      "id_value": "string"
    }
  ],
  "reference": "string",
  "scheduled_for": "2022-11-23T20:21:50.480Z",
  "sent_at": "2022-11-23T20:21:50.480Z",
  "sent_by": "string",
  "status": "created",
  "subject": "string",
  "template": {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "uri": "string",
    "version": 0
  },
  "type": "sms"
}

This is what is on the API example, you get a notification by calling this API with a notification id, I probably need to split this request to 2 by type (sms and email). but you can associate both email and sms to a notification or not?

I had a response on Slack, thank you. Now waiting on instructions for testing push notifications from @jakehova

@trevor2718 isn't the push notifications a separate task that is not committed to this sprint? Are the changes for this ticket awaiting code review from the team? If so you can take another ticket from to-do.

@mjones-oddball Of course there are changes for SMS and email already. For the Push, I believe it's a part of the requirement. Just FYI -
If you don't mind, I can open WIP PR.

@mjones-oddball No worries. I am so sorry for confusing you. Will do!

@trevor2718 No sorry needed, I did that all by myself :). I just spoke with @k-macmillan and he believes that push notifications don't actually create a notification object like email/sms. Which I did not know. You can probably quickly validate and then push up your other changes for review!

I am not able to test push functionality at this time. However, push is currently not related to notification object so moving forward with review.

approved


Compile from source

Compile classes from java files on project load and on file save. It's probably better to implement compilation as a separate package to avoid conflicting responsibilities between packages. The linter-javac package already compiles classes on save. Maybe just a few additions there? (= compile all on project load or by command)
autocomplete-java refresh should trigger after compilation has ended for each class that was compiled.

Closing this issue in favor of #19, since this issue is a matter of linter-javac or separate java-compile package.


Week2+3: SI-ConvNet

This week task:

Read and discuss the paper Locally Scale-Invariant Convolutional Neural Networks (on this Wednesday)
Read and understand the code(this Wednesday)
Run the code and test using same dataset
Write the survey part of this paper

!! Better the read the mentioned paper in background to prepare for the final report "Background" part. At least mark the paper.

How to crop in SI-Convnet?
Method is in ubtil/transformation.cpp: void CropCenter()

// For downpooling, when undoing all the transformation, need to only return the
// pixels that correspond to the canonical response. If the output is smaller
// than the canonical output size, then the output is padded with 0 to fit the
// size. If the output is larger, then the crop of size canonical output is
// taken at the center.
// For odd canonical output sizes, the extra pixel has to happen to the right of
// the center, i.e. Crop an 4x4 into 3x3 at the center can be either (in 1-D)
// indices [0, 1, 2] or [1, 2, 3]. The correct indices in SICNN case is [1, 2,
// 3] because the first few convolution outputs don't have corresponding centers
// as the output of the canonical size.
// Assumes that coord_new is length target_wtarget_h.
// Flow:
// up_layer & tied conv: applies T to an image (imgT), then convolve the
// transformed image (imgTW)
// downpool_layer: applies T^{-1}, which has a different size than the canonical
// size (unless stride==kernel size0
// if imgTWT^{-1} is smaller than imgW (when image was down-sampled), then
// pad the border with 0 (i.e. coordinate points to -1).
// else, the corresponding portion is the center of the bigger response, so crop
// at the center.

void CropCenter(const float *coord, const ImageSize &original,
                const ImageSize &target, const Interp &interp,
                float *coord_new) {
  int new_start_r = 0, new_start_c = 0;
  int old_start_r = 0, old_start_c = 0;
  int match_width = 0, match_height = 0;
  // Find the start and row of the larger dimension.

  if (original.height < target.height) { // Pad
    new_start_r = ceil((target.height - original.height) / 2.);
    match_height = original.height;
  } else { // crop center
    old_start_r = ceil((original.height - target.height) / 2.);
    match_height = target.height;
  }
  if (original.width < target.width) { // Pad
    new_start_c = ceil((target.width - original.width) / 2.);
    match_width = original.width;
  } else { // crop center
    old_start_c = ceil((original.width - target.width) / 2.);
    match_width = target.width;
  }
  // I_new(new_start_c:new_start_c + match_width - 1, new_start_r:new_start_r +
  // match_height - 1)
  // = I(old_start_c:old_start_c + match_width - 1, old_r_start:old_r_start +
  // match_height - 1);
  switch (interp) {
  case NN:
    {
      // nn_crop_center(coord, original, target, coord_new);
      std::fill(coord_new, coord_new + target.height * target.width, -1);
      for (int i = 0, row_new = new_start_r, row_old = old_start_r; i < match_height;
	   ++i, ++row_new, ++row_old) {
	for (int j = 0, col_new = new_start_c, col_old = old_start_c;
	     j < match_width; ++j, ++col_new, ++col_old) {
	  const int ind_new = row_new * target.width + col_new;
	  const int ind_old = row_old * original.width + col_old;
	  coord_new[ind_new] = coord[ind_old];
	}
      }
    }
    break;
  case BILINEAR:
    {
      // bilinear_crop_center(coord, original, target, coord_new);
      int dim_old = original.width * original.height;
      int dim_new = target.width * target.height;
      std::fill(coord_new, coord_new + 4 * dim_new, -1);
      for (int i = 0, row_new = new_start_r, row_old = old_start_r; i < match_height;
	   ++i, ++row_new, ++row_old) {
	for (int j = 0, col_new = new_start_c, col_old = old_start_c;
	     j < match_width; ++j, ++col_new, ++col_old) {
	  const int ind_new = row_new * target.width + col_new;
	  const int ind_old = row_old * original.width + col_old;
	  coord_new[ind_new] = coord[ind_old];
	  coord_new[ind_new + dim_new] = coord[ind_old + dim_old];
	  coord_new[ind_new + 2 * dim_new] = coord[ind_old + 2 * dim_old];
	  coord_new[ind_new + 3 * dim_new] = coord[ind_old + 3 * dim_old];
	}
      }
    }
    break;
  default:
    LOG(ERROR) << "Unknown interpolation mode " << interp;
  }
}


Typo on left menu on x.forbole.com

At the bottom button, should be "Start Now" instead of "Star Now"

The term is correct as that button is to hint users to Star some accounts now. @terencesflam do you have any suggestion if this is unclear?


[Event Hubs Client] AMQP Converter Enhancements

Summary
The focus of these changes is to apply some of the Service Bus learnings to the AmqpMessageConverter for better efficiency and to align more closely with some of the structure that will be needed when adopting the raw AMQP message model.
Last Upstream Rebase
Tuesday, March 30, 11:30am (EST)
References and Related

#19823
#19821
Service Bus AmqpMessageExtensions
Service Bus AmqpMessageConverter

Nice to see some of my changes ported over!


Track stomp disconnect and error events in pg

We need better tracking about, when, why and how often stomp disconnect events are happening.  Proposing we store them in a log table in pg.

first pass. @qjhart seem responable?
fcrepo=# \d activemq.debug_log;
                           Table "activemq.debug_log"
      Column      |            Type             | Collation | Nullable | Default
------------------+-----------------------------+-----------+----------+---------
 id               | uuid                        |           | not null |
 timestamp        | timestamp without time zone |           | not null | now()
 client_name      | text                        |           | not null |
 client_id        | text                        |           | not null |
 event            | text                        |           | not null |
 message          | text                        |           | not null |
 stack_trace      | text                        |           | not null |
 connnection_data | jsonb                       |           |          |
Indexes:
    "debug_log_pkey" PRIMARY KEY, btree (id)
    "debug_log_client_name_idx" btree (client_name)
    "debug_log_event_idx" btree (event)
    "debug_log_timestamp_idx" btree ("timestamp")

Yeah, seems like a good tool. Are the messages always JSON or sometime text?


Update README.md

Checklist

[x] documentation is changed or added
[x] the commit message follows commit guidelines

Description of change

Fix a link to the USAGE.txt file (was 404ing)

Perfect. Thanks.


2818 disaggregate purchases export

Resolves #2818
Description
Addresses #2818 Disaggregate Purchase Export

Added columns for line items, following the donation pattern.

Also added column for comments and for the breakdown of spend by major category

changed the mechanism for the purchase to an export service matching how the donations export was done -- because the pattern was already there.

cleaned up the csv export infrastructure in the purchases record, as no longer needed.  Deleted the accompanying spec.

Note:  At migration, several files were changed -- the schema, plus several files that annotate touched.   I was a little surprised by this -- that step is in a separate commit, in case of need .
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I added a new set of tests in spec/services/exports/export_purchases_csv_service_spec.rb.    These are directly modelled on the existing tets in export_donations_csv_service_spec.rb
In addition, I did a simple manual test -- adding a purchase with a breakdown by major category and 3 line items.  It appeared as I expected it to in the export.
Screenshot

s

Looks good! I love all the comments :)

I can't take credit for them -- I copied the donations code and modified it, comments included.


Add some multi-threaded micro-benchmarks.

Spawn 10 threads, each does a million logs.
We have two: one for L3 and one for spdlog.
For this test, L3 is over 20x faster than spdlog.
$ time ./spdlog.exe

real    0m18.050s
user    0m29.033s
sys     1m17.579s
$
$
$ time ./l3.exe

real    0m0.814s
user    0m6.623s
sys     0m0.028s
$

@gregthelaw - Is this ready to go? This kind of u-perf benchmarking will be interesting to the CS-audience I am giving a talk to this Fri.
I found a few things missing. There is at least an arg-parsing error. You need to apply this diff to get things to run w/o any args:
+    int nthreads = argc >=1 ? 10 : atoi(argv[1]);

Also I had to change the Makefile to add -l fmt -lpthread to the spdlog build step. Did it work for you w/o this?
I have several ideas on how-to productize this with better arg-parsing and a target mt_ubench_all target in top-level Makefile.
Before I get on and tweak this change-set, wanted to know how far from ready are you on this work?

Hi.
The Makefile worked for me on Ubuntu 22.04.04 as it seems on that distro you don't need the -lpthread but yes, older distros will need that, so I fixed that here.
Should be ready for review now.

@gregthelaw - To be consistent with other Makefile targets, I am trying to rework the interfaces to be something on the lines of:
make all-mt-ubench && make run-mt-ubench
I think it will be better if we have these targets from top-level Makefile.
I am reworking the Makefile to support this. (But it's happening in spurts and during breaks.)
Give me some time to get back to you with a delta-commit offering these changes.


Transfer repo to dwyl?

I think I'm ready to let go of "control" of this repo...
@iteles what do you think? :wink:

Those 120 :star2: certainly look good on your profile :wink:
There's no rush to do this but sounds like a plan :+1: :blush:

I will soon have way more stars on my "main" repos. and the sooner we get dwyl on the radar for people learning how to build cool things the better. don't you think...?

From a dwyl perspective, absolutely!

think this can be closed now :D

@Charlotteis There are days when there's just too much going on :wink:
Thanks for catching this!


[CheckPoint Loader] Not working anymore

After last update of ComfyUI,  [Pythongosssss CheckPoint Loader] don't load list of checkpoints.
Neither (sub)folders with checkpoints nor plain files in ComfyUI/models/checkpoints don't listed anymore.  There is a undefined instead of filenames
Standard CheckPoint Loader works without problem.

Strange... After git pull and reinstal of venv and pip install -r requirements.txt on next day no problem again.


JSonb extract slower in Pl/Rust than in Pl/PgSql

Hi,
We give a try to Pl/Rust to boost a Pl/PgSql function that hashes a partial JSonb doc to a Md5/Uuid.
The results are not so good and the first thing we noticed is a longer time to extract a value from a JSonb param.
This is the benchmark.
SQL version:
create or replace function get_jsonb_value_sql(doc jsonb, key text)
returns text strict immutable language sql
as
$$
   select doc->>key;
$$;

Pl/PgSql:
create or replace function get_jsonb_value_plpgsql(doc jsonb, key text)
returns text strict immutable language plpgsql
as
$$
begin
   return doc->>key;
end;
$$;

Pl/Rust:
create or replace function get_jsonb_value_plrust(doc jsonb, key text)
returns text strict parallel safe immutable language plrust
as
$$
   Ok(Some(doc.0[key].to_string()))
$$;

To generate a dataset and run benchmark:
drop table if exists data;
create temporary table data as
select
    jsonb_build_object(
        'foo', 'bar' || s.id,
        'lorem', 'ipsum'
    ) doc
from
    generate_series(1, 10000000) as s(id);

explain analyze select get_jsonb_value_sql(doc, 'foo') from data;
explain analyze select get_jsonb_value_plpgsql(doc, 'foo') from data;
explain analyze select get_jsonb_value_plrust(doc, 'foo') from data;

Results:

lang
time

Sql
1863.657 ms

Pl/pgSql
4329.467 ms

Pl/Rust
7693.342 ms

The more the JSonb document is complex, the more the factor increases. Pl/Pgsql is quite stable and Pl/Rust takes more time.
Maybe there's something we can do different?
Thanks.

@ncharlot "fast JSONB in PL/Rust" is something that has been requested, but unfortunately, the current convenience wrapper around JsonB in pgrx requires quite a lot of copying and FFI overhead to operate and we don't do anything terribly clever in PL/Rust to avoid or minimize that. We just serialize the entire JsonB.
This, ironically, is about as fast as accessing the JsonBContainer using FFI functions, per https://github.com/tcdi/plrust/issues/396#issuecomment-1809082135
The way that PL/Rust has fast Array handling is via raw pointer access, so that the implementation can stay in Rust and thus benefit from compiler optimizations instead of using FFI functions, which have considerable overhead to call from Rust because Rust does not support setjmp and longjmp and thus we must shield against Postgres jumping over Rust code.

Thanks for your precise reply @workingjubilee
So for this first case we will start by passing directly the needed values of the Jsonb doc.
And we'll follow the evolutions of this part!

pgrx' support for the JSONB type is very naive.  It actually converts it to a String and then uses serde to deserialize it.  So you'd see slightly better performance if you just used the JSON type.  JSON already starts as a String (basically), so there's about 50% less overall work.  I'm not sure how that equates to runtime performance but it should be faster.
I'd like to see us eventually have first-class support for JSONB.  As @workingjubilee mentioned, we're able to do some nice/fast things for Array support b/c we have our own implementation of the binary format.  We'd need to do the same for JSONB.  It's doable, of course -- it's just a lot of work.


timetrace status doesn't work if there was no time tracking yet

Running timetrace status leads to an error if time hasn't been tracked on that day yet:
timetrace status
❗ Failed to obtain status: open /Users/dominik/.timetrace/records/2021-05-15: no such file or directory

This is because the record directory of that day, in this case 2021-05-15, hasn't been created yet. It will be created when running timetrace start.
To fix this,  Fs.EnsureDirectories should also create a record directory for the current day:
https://github.com/dominikbraun/timetrace/blob/16b10a97b594a7e73145096e84b6fb9672048df2/fs/fs.go#L151-L166
EnsureDirectories is executed in advance on each timetrace command.

Hi, cool tool - Can I have a look at the issue and create a PR?

Of course! Just run the commands like go run . status locally for development.


Implement game rematch

The client sends a 'rematch` when the player wants to play again

Otherwise the client sends 'leave' when the player wants to leave the room

Also adjusted the Winner banner animations and timings.

This "depends" on server support for 'rematch' event.

Tested with https://github.com/toshisasaki/have_you_heard_back/pull/19


No support of covariant instance variables

According to the Dart specification "10.6 Instance Variable"

It is possible for the declaration of an instance variable to include the modifier covariant (8). The effect of this is that the formal parameter of the corresponding implicitly induced setter is considered to be covariant-by-declaration

In fact the following code doesn't work in both analyzer and CFE
class A {
  covariant num v = 1;
}

class C extends A {
  void set v(int val) {} // CFE: Error: The type 'num' of the inherited field 'A.v' is not a subtype of the type 'int' of the setter 'C.v'.
                         // Analyzer: The return type of getter 'A.v' is 'num' which isn't a subtype of the type 'int' of its setter 'v'.
}

main() {
  print(C);
}

According to the spec setter A.v has a covariant formal parameter which means that setter C.v should accept any type which is subtype or supertype of num
Tested on Dart SDK version: 3.1.0-309.0.dev (dev) (Thu Jul 13 13:04:16 2023 -0700) on "windows_x64"

I think the responses from the tools are OK. The error which is reported is that (essentially) we can't do v = v in the body of C, or more precisely: In the interface of C, the return type of the getter named v is not a subtype of the formal parameter type of the setter named v=, and that's an error (which is still valid, no matter if and where we put the word covariant).
It is still possible to test that covariant has an effect:
class A {
  covariant num v = 1;
}

class C extends A {
  int get v => 2; // Ensure that the getter `v` has the required return type.
  void set v(int val) {} // Now we can use the `covariant` property.
}

class C2 implements A {
  int v = 1; // A more typical way to use the extra affordances provided by `covariant`.
}

Thanks for response. Closing this issue


E2E: Soak test and Functional tests for K8Petstore

K8petstore e2e test which runs the k8petstore.sh driver (this PR modifies original driver to play nice with external arguments and so on).
There are two variants.  One is a scalable one (confirms 5K*minions transactions are stored within 6 minutes) and a functional one, which simply confirms that 500 transactions are consumed.
tested both , results below...
TEST PASSED after 7 tries !
Passed...

The e2e test itself runs two tests.  A functional one k8petstore-functional and a "soak" test, k8petstore-SCALE.
The functional test confirms 500 transactions are generated and stored into redis.  This basically is a validation of the connectivity of the containers / persistence ability of redis.
The scale test confirms that given 2n data generators, we get 5000 transactions per minion.  So on a ten node cluster, it confirms 50K transactions will be written within a 5 minute time period.
This is all done with parameters,  so once its been vetted after a few runs of the CI, I will make the parameters more demanding.

I've rebased this against eric's updates, and also, I've broken commits into logical subunits (the k8petstore examples update is independent from the e2e test).

not sure why travis failed ?

Minor note : the soak actually creates 2 load generators per minion... The goal is to confirm that even if each minion is doing generation it should still be able to field rest requests

bumping my e2e soak test guys @satnam6502 @brendanburns @wojtek-t

i need to  fix boilerplate and resubmit...

i fixed most of these, shortly I'm going to make a couple of other improvements that came to mind and resubmit later on.  thanks brendan for the feedback

I will test this some more, as I made a couple of other enhancements based on some things related to the suggestions (i.e. consolidating variables/ dead code).  I'll Ping when its 100% ready for review.

okay, tested, ready for a new look

LGTM.  Please rebase and squash and I'll merge.
Thanks!

Cool  will rebase shortly ! just saw .

Squashed down (separate commit for the k8petstore shell script improvement - as its an independent feature enhancement)

This is consistently timing out in our continuous integration environment.  I'm going to revert until that's fixed, possibly as part of #7989


Localization for BreadCrumb

Hi, How can i localize breadcrumb or change programaticly mvc.sitemap file ?

See this answer: http://stackoverflow.com/questions/20328189/how-to-localize-the-mvcsitemapprovider#20344209


Why are position/width/height styles needed when plainSprite is used

Hey,
I'm using the loader to extract sprite.svg file with plainSprite option. I'm referencing svg files later like this one:
<svg viewBox="0 0 32 32">
  <use xlinkHref="sprite.svg#test" />
</svg>

The generated sprite file starts with <svg style="position: absolute; width: 0; height: 0" .... Why do I need this styles when I'm using external file. Am I missing something?

Hola! Thanks for reporting, it's a bug, fixed in 3.6.1

@kisenka holy crap, this was blazing fast. Thank you for such a great loader! ❤


Missing files

Files are missing for initial setup

Check branches
On Thu, 2 Nov, 2023, 7:36 PM Mohammed Salman Shaikh, <
@.***> wrote:

Files are missing for initial setup
—
Reply to this email directly, view it on GitHub
https://github.com/Nikhilthadani/MERN-AI-ChatBot/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APDHCRFVZDOUGHHSZAX2PKTYCOSHTAVCNFSM6AAAAAA626JJZCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3TIMZTGY4DCMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Found it


Move this project to mapzen org

Goodbye old friend.

One of the big questions is this: do we also want to rename the package? It's currently at https://npmjs.com/package/pelias-leaflet-geocoder, but renaming it something like mapzen-leaflet-geocoder is going to break existing installs. Then again, it might be worth to rip this band-aid off right now instead of later...

Far better now than later.

On Dec 3, 2015, at 7:10 PM, Lou Huang<EMAIL_ADDRESS>wrote:
One of the big questions is this: do we also want to rename the package? It's currently at https://npmjs.com/package/pelias-leaflet-geocoder, but renaming it something like mapzen-leaflet-geocoder is going to break existing installs. Then again, it might be worth to rip this band-aid off right now instead of later...
—
Reply to this email directly or view it on GitHub.

Opinions on naming?

mapzen-leaflet-geocoder (closest to current)
mapzen-search-leaflet (get the whole product name in there)
mapzen-search-leaflet-geocoder (too long?)
leaflet-mapzen-search (prefacing it with the environment it's plugging into, which is a pretty common pattern)

Recapping a short discussion with @riordan today:
When we move the repository to the Mapzen organization, also rename the npm package to leaflet-geocoder-mapzen from pelias-leaflet-geocoder. "Leaflet" should come first so it's clear that it's a Leaflet plugin. "Geocoder" is next because that is specifically what it is and what it does. "Mapzen" is last to be clear that it is designed for the Mapzen service.
Further thoughts on the transition:

The repository name will stay as-is.
Named things in the code that refer to Pelias should remain as-is (we can revisit this in a major version bump).
Consider renaming the JS and CSS files. This shouldn't matter for anyone installing via npm. Any manual downloads (or bower) means needing to adjust a file name reference.

I'm also very conflicted about whether this change requires a semantic version bump. It feels unnecessary to call this v2 even though moving/renaming things is technically a "breaking change", and this is the only breaking change. Since I plan to rename the package name anyway, this is actually a new entry in npm and bower, so conceptually you might think this is a "different package" even though I'd prefer to call it v1.3 just so this transition has a clear place in history without disrupting it too much.
In the meantime, we will leave the distribution files here on pelias/leaflet-geocoder, and leave a deprecation notice in the README and on npmjs.org pointing to the new repository and package locations. This should be enough to preserve functionality for anyone who is still depending on it in the near term.
Thoughts?!

:+1:

Done and released as https://github.com/mapzen/leaflet-geocoder/releases/tag/v1.3.0.
Placeholders are in place and existing links to the old repository should still work: https://www.npmjs.com/package/pelias-leaflet-geocoder
Anyone trying to npm install pelias-leaflet-geocoder will also see this message:


Files put in src don't always put classes into app

the app dir should be the only source of truth for the web app. Let the source sets compile into app/WEB-INF/classes

all generated files (classes, config xmls etc.) are generated in build/warRoot.  generating in places within app will pollute the source directories.


Allow dynamic node identification to be turned off

Addressed in 12ed6e6abfd02825133c5e125796e7a534b75688
Make sure meta_flag is set to 0.


support for sending any ERC20 token

What
Tackles issue https://github.com/youvegoteth/youvegoteth.github.io/issues/7

TODOSs to get this merged:

make sure that old 'send' links work
test the crap out of this.
Deploy contract to mainnet.


Add visionOS Support

Add visionOS Support
Thank you @philprime & team for the work on TPPDF; nice Swift Package and great functionality!
:recycle: Current situation & Problem

The current package is supporting iOS and macOS targets.
The underlying infrastructure is fully supporting visionOS and only needs requires modifications to the #if statements.
The current sample application's progress bar is not using constraints for the alignment and uses an outdated UIWebView that is not available on visionOS.

:gear: Release Notes

Adds visionOS support to TPPDF
Improves example app to use constraints & WKWebView
Update Github Actions with vision build

:books: Documentation

Updates the README with links to the Swift Package Index

:white_check_mark: Testing

Added build action to test building on visionOS
Executing the tests on visionOS is unfortunately currently timing out due to a lack of support by the GitHub provided images. More context can be found in https://github.com/actions/runner-images/issues/9511

@philprime Thank you for triggering the builds. Seems like the fact that the Danger GitHub Action is relying on a secret not available outside of the repo is failing the Danger check for forks: https://github.com/PSchmiedmayer/TPPDF/blob/main/.github/workflows/danger.yml#L20.
Might be resolved by just passing in the default GITHUB_TOKEN which has limited access and permissions even in forked repos (can be changed in the repo settings). Let me know if you want me to modify the GitHub Action or how to proceed with the merge checks here.

Hi @PSchmiedmayer :)
Thank you for the PR and the time you invested into it!
I just came back from vacation, so I didn't have the time yet to look into it in detail, but I'll do it as soon as possible.

Thanks again for your PR.
I appreciate the work you put into it!
Regarding the changes in code:
Looks good, lets get this merged.
Regarding the CI matrix:
Looks good to me, but we need simpler checks names, otherwise the required status configuration will require more maintenance. We should be able to set the job name of the GitHub Action based on the matrix - you can find an example here, where I create Docker images based on a matrix:
https://github.com/kula-app/containers/blob/bc111124dc55d20c2050b5d8c229e34837027208/.github/workflows/build-images.yml#L19
Would appreciate if you could add this to your PR.
Regarding Danger, the access token with limited access from our bot user @techprimate-bot as defined in their documentation.
But I went ahead and created a test fork and PR to check if GITHUB_TOKEN works too. Looking at the logs it seems like the default token did not have access to create the Danger comment in the PR/Issue.
Request failed [403]: https://api.github.com/repos/techprimate/TPPDF/issues/385/comments
Response: {
  "message": "Resource not accessible by integration",
  "documentation_url": "https://docs.github.com/rest/issues/comments#create-an-issue-comment",
  "status": "403"
}
Feedback: undefined

Looking at the documentation for permissions of the GITHUB_TOKEN, I found the following section:

You can use the permissions key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the Send write tokens to workflows from pull requests option in the GitHub Actions settings. For more information, see "Managing GitHub Actions settings for a repository."

After looking further it, and noticing that even setting additional permissions like the following, it did not work:
jobs:
  job-danger:
    permissions:
      actions: read
      attestations: read
      checks: read
      contents: read
      deployments: read
      discussions: read
      id-token: write
      issues: write
      packages: read
      pages: read
      pull-requests: write
      repository-projects: read
      security-events: read
      statuses: read

I guess we need to skip Danger in forked PRs.
If you have another idea, would be happy to read it.

@philprime Thanks for the review!
Good idea! I update the GitHub Action Name to just use the matrix.build.sdk name which might be the most expressive of the ones within our matrix configuration.
Regarding the danger check: Unfortunate but I don't have any other suggestions as well. We have similar challenges with some of our merge checks in our open-source repos.

Thanks for the adaptation.
Super-small request, just for the sake of completeness: could you please also change the macOS Unit Test to use the same format?
This is now with the matrix naming:
Tests / Unit Tests (iphonesimulator)
Tests / Unit Tests (xros) (pull_request)
Tests / macOS Unit Tests (pull_request)

but this would be nicer:
Tests / Unit Tests (iphonesimulator)
Tests / Unit Tests (xros)
Tests / Unit Tests (macos)

I don't want to picky, I just think this could be a good point in time for a small change in the PR.
You can either rename the macOS job to use this format, or create a matrix with a single entry. Both fine to me.
Thank you!

Also regarding Danger (sent my comment to fast):
Looking at my test PR #385 we can add a fallback for the Danger GITHUB_TOKEN, so at least it soft-fails:
        with:
          args: --failOnErrors --no-publish-check
        env:
-         GITHUB_TOKEN: ${{ secrets.DANGER_GITHUB_API_TOKEN }}
+         GITHUB_TOKEN: ${{ secrets.DANGER_GITHUB_API_TOKEN || secrets.GITHUB_TOKEN }}

I actually believe there is a bug in Danger, that it should actually fail (https://github.com/danger/danger-js/issues/1441) but for me it is not critical enough to block your PR.
So please add the GITHUB_TOKEN fallback, and we'll fix Danger for forks another time.

@philprime Sure; I updated the GitHub Action names & Danger job, thanks for the input. I like the idea to keep this clean 🚀
The jobs will now be named:
Tests / Unit Tests (iphonesimulator) (pull_request)
Tests / Unit Tests (xros) (pull_request)
Tests / Unit Tests (macos) (pull_request)

The pull_request postfix seems to be automatically added by the trigger of the action.

Fantastic. Thanks for the additional effort.
This PR looks good to me so I'll go ahead and merge it, as well as release a new version afterwards

Thank you @philprime 🚀
Thank you for creating and maintaining this framework; always happy to support fellow open-source work 👍


List available transactions given the state of the state machine

1 New Class:

TransitionMeta which is added to the transition methods .__fsm attribute

2 New StateMachine methods:

all_transitions, returns list of all Transitions
available_transitions, returns list of all available Transitions based on state of the StateMachine

At first, I thought this would be way simpler. Let me know if this is not the solution you were looking for!
It looks like pytest still passes, however this is only my second PR - so I would love some feedback!

Codecov Report

Merging #22 into master will decrease coverage by 13.75%.
The diff coverage is 49.12%.

@@             Coverage Diff             @@
##           master      #22       +/-   ##
===========================================
- Coverage   96.10%   82.35%   -13.76%
===========================================
  Files           7        7
  Lines         154      204       +50
===========================================
+ Hits          148      168       +20
- Misses          6       36       +30

Impacted Files
Coverage Δ

finite_state_machine/exceptions.py
78.57% <40.00%> (-21.43%)
:arrow_down:

finite_state_machine/state_machine.py
75.23% <43.47%> (-24.77%)
:arrow_down:

finite_state_machine/draw_state_diagram.py
81.08% <100.00%> (-0.74%)
:arrow_down:

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 bb96cf3...b522af6. Read the comment docs.


incomplete xaml

Sample for textBoxInError and data?

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

ID: 3a0b0539-04a6-b652-ef55-b288545f897b
Version Independent ID: 5b75a31b-3a21-02d0-6ffe-a57f567b037e
Content: How to: Implement Validation Logic on Custom Objects
Content Source: docs/framework/wpf/data/how-to-implement-validation-logic-on-custom-objects.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for letting us know that the sample code is incomplete, @gojanpaolo. We've created two PRs, dotnet/docs#6806 and dotnet/samples#217, to display all of the Window1.xaml file with the relevant code highlighted.

@rpetrusha Thanks for addressing this issue.
I'm currently looking at the page and it seems nothing changed yet? Will it take time before the page updates? I assumed the page is fixed since the issue is closed. :)

Yes @gojanpaolo. The update will be live later today.

@mairaw Alright! Thanks you :)


Python library import error

Hi I meet a problem when using python library. The below is the error message. Do I have to build from scratch before I install the python library by pip?
(Just in case I forgot to install any dependency.)
>>> from ngt import base
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "ngt/base.py", line 42, in <module>
    class Index(object):
  File "ngt/base.py", line 88, in Index
    __ngt.ngt_open_index.argtypes = [c_char_p, c_void_p]
  File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: python: undefined symbol: ngt_open_index

You are right. You have to build and install the NGT library before installing the python NGT.
The error message means that the python NGT cannot load the NGT library.

Problem solved.
Also, in your guidance, the last line: "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib64", I removed "64" to be "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib".
Not sure whether this is an issue for others.
Anyway, thanks a lot.


Add topics & subscriptions for email

Motivation and Context
We should be able to send emails, either in a batch (action rule) or individually ad-hoc (fulfilment).
What has changed
Added topics and subscriptions to support email.
How to test?
Run the ATs.
Links
Trello: https://trello.com/c/OPYjtKwf

 Use Email for Action Rules and Fulfilments (13)


Daytona server doesn't start when the local machine already has a tailnet client connecting to a self-hosted Headscale control server

Describe the bug
I run a personal Headscale server, and have tailscale deployed on every single one of my machines.
That means that all my machines have a customized login/control server variable for the Tailscale client, especially on Windows, where this requires a registry key change, pointing to my self-hosted Headscale instance.
When attempting to run daytona server on my Windows-based laptop, I ran into this issue in the logs:
[...]
2024/03/12 09:51:10 LocalBackend state is NeedsLogin; running StartLoginInteractive...
2024/03/12 09:51:10 StartLoginInteractive: url=false
2024/03/12 09:51:10 control: client.Login(false, 10)
2024/03/12 09:51:10 control: [v1] mapRoutine: context done.
2024/03/12 09:51:10 control: [v1] mapRoutine: state:new
2024/03/12 09:51:10 control: [v1] authRoutine: context done.
2024/03/12 09:51:10 control: [v1] authRoutine: state:new; wantLoggedIn=true
2024/03/12 09:51:10 control: [v1] direct.TryLogin(token=false, flags=10)
2024/03/12 09:51:10 control: LoginInteractive -> regen=true
2024/03/12 09:51:10 control: doLogin(regen=true, hasUrl=false)
2024/03/12 09:51:10 control: control server key from https://<my.headscale.server>: ts2021=[NI15q], legacy=[mVUHl]
2024/03/12 09:51:10 control: Generating a new nodekey.
2024/03/12 09:51:10 control: RegisterReq: onode= node=[FMVB/] fup=false nks=false
2024/03/12 09:51:10 control: [v1] creating new noise client
2024/03/12 09:51:10 control: [v1] TryLogin: register request: http 401: {"User":{"ID":0,"DisplayName":"","ProfilePicURL":"","Domain":"","Logins":null,"Created":"0001-01-01T00:00:00Z"},"Login":{"ID":0,"Provider":"","LoginName":"","DisplayName":"","ProfilePicURL":"","Domain
2024/03/12 09:51:10 control: [v1] sendStatus: authRoutine-report: state:authenticating
2024/03/12 09:51:10 control: authRoutine: [v1] backoff: 13 msec
2024/03/12 09:51:10 Received error: register request: http 401: {"User":{"ID":0,"DisplayName":"","ProfilePicURL":"","Domain":"","Logins":null,"Created":"0001-01-01T00:00:00Z"},"Login":{"ID":0,"Provider":"","LoginName":"","DisplayName":"","ProfilePicURL":"","Domain
2024/03/12 09:51:10 control: [v1] authRoutine: state:authenticating; wantLoggedIn=true
2024/03/12 09:51:10 control: [v1] direct.TryLogin(token=false, flags=10)
2024/03/12 09:51:10 control: LoginInteractive -> regen=true
2024/03/12 09:51:10 control: doLogin(regen=true, hasUrl=false)
2024/03/12 09:51:10 control: Generating a new nodekey.
2024/03/12 09:51:10 control: RegisterReq: onode= node=[v3eTY] fup=false nks=false
2024/03/12 09:51:10 control: [v1] TryLogin: register request: http 401: {"User":{"ID":0,"DisplayName":"","ProfilePicURL":"","Domain":"","Logins":null,"Created":"0001-01-01T00:00:00Z"},"Login":{"ID":0,"Provider":"","LoginName":"","DisplayName":"","ProfilePicURL":"","Domain
2024/03/12 09:51:10 control: [v1] sendStatus: authRoutine-report: state:authenticating
2024/03/12 09:51:10 control: authRoutine: [v1] backoff: 37 msec
[...]

And then it keeps repeating/backing off for longer and longer, never moving.
I looked around, but I don't see any obvious way to either register daytona with my existing headscale deployment (preferred), or force the client that the daytona server spins up to connect to the specific local headscale server that also gets spun up in C:\Users\<login>\AppData\Roaming\tsnet-daytona
To Reproduce
Steps to reproduce the behavior:

Install tailscale on a Windows machine (not tested on other OSes)
Deploy headscale on a seperate system
Properly connect the tailscale client on the Windows system to the Headscale server (Registery keys and all)
Launch daytona server on the Windows machine
See error

Expected behavior
Either
Daytona should support registering the daytona server with the existing custom Headscale server
OR
Daytona should re-use the existing tailscale connection from the local machine to the Headscale server (preferred, if possible)
Screenshots
Logs provided above instead
Desktop (please complete the following information):

OS: Windows 11, Version 23H2 (OS Build: 22631.3155)
Browser: Brave (irrelevant here)
Daytona Version: v0.2.0

Additional context
None that I think I relevant here, but feel free to ask

@shuguet thanks for such a detailed issue. This is something that we would love to support and we definitely will try to.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 14 days). It will be closed if no further activity occurs. Thanks for the feedback.

The issue is still relevant :)
(Unsure if there is a /command to use for the bot to remove the tag, can't seem to be able to do it myself).

@shuguet you're right, that was a mistake by the bot.
We are aware this is still an issue, we have @gdraganic working on this and some other tailscale improvements.

@shuguet you're right, that was a mistake by the bot.

I didn't think it was a mistake by the bot, most likely it is doing it's job of marking issues that have not received any update in 2 weeks as stale :)
Generally, with most GitHub bots I'm familiar with, there's either a command like (/remove-lifecycle stale with Prow for example), or simply adding a comment cancel out the stale label/status.
Looks like yours require a manual intervention of an authorized user to remove the stale label (since I could not remove the label myself).

We are aware this is still an issue, we have @gdraganic working on this and some other tailscale improvements.

Thank you 🙏
Let me know if there's anything you need/I can help with.


Trove classifiers l2 to l5 are foreign keys

AFAICT, in the trove_classifiers table, L2 to L4 are foreign keys on id (of the parent classifier).  Except when they are 0, which I'm not sure how to handle. But L2 is never 0, as it is at worst same-row-id.
I don't know if that can be useful, at least that should clarify what they are for future readers instead of purely "integers".

👍 Thanks for this bit of knowledge, @Carreau. I'm going to close this since there isn't anything actionable here for us at the moment.

I'm going to close this since there isn't anything actionable here for us at the moment.

Seem reasonable ! Thanks ! I
'm not a postgres/db person, but if you are looking for action items, change the schema to say they are  foreign keys ? Though you might not be able to do that as they may be 0. Looking fwd to warehouse replacing PyPI-legacy also excited (and congratulation) for your funding.


Autodetect macOS and include the necessary _DARWIN_C_SOURCE

macOS requires _DARWIN_C_SOURCE to be defined for build. I noticed at a dvtm issue this is to be included (in sfm's case) in CPPFLAGS, but doesn't need to be on every OS. However, I believe they decided to let the package maintainers deal with it in patches for their package system.
I am unsure if you want to do that or not, so I added some basic OS detection and put it in the appropriate CPPFLAGS section in config.mk. You may want to lean on their decision on maybe not including it, or update the README.md for macOS users to do,
$ CPPFLAGS=-D_DARWIN_C_SOURCE make
$ make install

But that still requires an update to config.mk to include
diff --git a/config.mk b/config.mk
index 8b632c6..976a903 100644
--- a/config.mk
+++ b/config.mk
@@ -6,7 +6,7 @@ PREFIX    = /usr/local
 MANPREFIX = ${PREFIX}/share/man

 # flags
-CPPFLAGS = -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -DVERSION=\"${VERSION}\"
+CPPFLAGS += -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -DVERSION=\"${VERSION}\"
 CFLAGS   = -std=c99 -pedantic -Wextra -Wall -Os ${CPPFLAGS}
 LDFLAGS  = -s

because CPPFLAGS+=... make or CPPFLAGS=... make doesn't work unless that + is added in the config.mk file.
I think it is up to you if you want to go the suckless route and keep the makefile minimal, or add my patch in for convenience of users. But adding the + to config.mk and edit the README.md is not a big deal and stays minimal with the suckless philosophy.
If you want you can reject this pull and I can submit a new one with the README.md and config.mk updated accordingly.

could we add this condition as preprocessor command:
#if defined (__APPLE__)
....
#endif

That makes sense to do that, but when adding that in it doesn't detect it (whether it is termbox.{c,h} or sfm.c). It still reports the error,
cc -c -std=c99 -pedantic -Wextra -Wall -Os -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -DVERSION=\"0.1\" termbox.c
termbox.c:585:12: error: use of undeclared identifier 'SIGWINCH'
        sigaction(SIGWINCH, &sa, 0);
                  ^
1 error generated.
make: *** [termbox.o] Error 1

I think the appropriate place in is the CPPFLAGS or CFLAGS, but the CFLAGS+=... make or CPPFLAGS+=... make doesn't seem to work due to the lacking + in the config.mk.

I think keeping Makefile portable with *BSD and GNU is the main point
Microsoft Windows will not be supported
Please test adding to sfm.c and termbox.c, it should pass
if their is a way to pass *BSD ifeq it would be better, but i don't know a way to do that

I think keeping Makefile portable with *BSD and GNU is the main point

I agree, unfortunately after looking at dwm/config.mk, they also have the same problem. At stackoverflow, it is clear that the package maintainers need to deal with specific platform issues by manually patching config.mk to add the + in each CFLAGS/CPPFLAGS/LDFLAGS, because config.mk seems to override the settings if you do
$ CPPFLAGS+=-D_DARWIN_C_SOURCE make

which I believe needs to happen anyone wants to add any additional platform specific flags for package builders.

Microsoft Windows will not be supported

Not a problem, I was just giving an example in the pull request

Please test adding to sfm.c and termbox.c, it should pass

I had tried this previously from above, but I tried again to make sure and got the same error.

That makes sense to do that, but when adding that in it doesn't detect it (whether it is termbox.{c,h} or sfm.c). It still reports the error

if their is a way to pass *BSD ifeq it would be better, but i don't know a way to do that

I think you need to detect each *BSD/Linux in a @ifeq individually since $(uname -s) will report either (Darwin, FreeBSD, OpenBSD, etc...). I updated the pull requset to exclude Windows.
I think in the end you could just leave this alone and reject the pull request, as other suckless tools (dvtm, dwm that I checked) seem to let the package maintainers deal with this issue for Linux and Mac specific issues.
Sorry if this seems like a wall of text, just trying to help out.

ifeq ($(shell uname -s),Darwin)

is not supported in *BSD

Ah you are right. I didn't realize macOS was using gmake. I think there is no clean solution to this problem. I will just close it and you can reject it. Let package maintainers deal with the issue.

#if defined (__linux__)
#define _GNU_SOURCE
#elif defined (__APPLE__)
#define _DARWIN_C_SOURCE
#endif

on OSX and GNU it works fine you just need to make definition at the top of the file

Oh jees you are right, haha. I wasn't putting it at the complete top, that is my fault. It works now and compiles.


Copy-on-write existential improvements

Runtime: Allow taking out of inline opaque existentials
Only values stored in the outline boxed existential representation can be
shared.
Use the inline value buffer for allocate/project/deallocateValueBuffer functions
Also handle fixed size types.

@swift-ci Please smoke test


Additional status for fallback translations for pages

Motivation
Currently, we show an "outdated translation" status for pages with no content but existing title.
Proposed Solution
Show an additional status icon for translations with fallback translations.
Alternatives

Additional Context

Design Requirements
We need an icon for the translation status for fallback translations (@hauf-toni)

Design Requirements
We need an icon for the translation status for fallback translations (@hauf-toni)

@JoeyStk I'm not sure whether we really need a design for this - we only use icons provided by https://lucide.dev/ inside the cms. So we would have to make sure the new design matches the existing icon set. Instead, I suggest that we just choose one of the available options.
I would suggest e.g.

info, because the page contains an information text in which languages the page is available:

milestone, because the page redirects the user to another language:

Just a reminder - these are the existing status icon:

status
icon

up-to-date

in translation

outdated

fallback (when duplicated)

machine translated

missing

Question regarding the suggestions:
info - doesn't the page always contain an info text telling the user that the page is not available in their language and thus redirects them to another language. Or are you referring to pages where not all of the page is translated? E.g. when part of the text is provided by the Kommune and another part is live-content from another Kommune that is not available in all languages?
milestone - does this ever happen without the user choosing a language actively? Or are you referring to when there is just the info text without any content?

In future we will enable municipalities to translate every page in every language with nearly no effort and budget. I don't see a real need to add more translation status at the moment or in Q3/23 or Q1/24.
Of course might had implemented that earlier but with the near scope of enabling all translations via AI.
For the use cases from @svenseeberg above i would suggest that we show the missing-symbol, if the content of the translation (not the title) is empty AND there are no more child-pages.
So we know if it is just a translation for structure (1st/2nd layer) or it is a missing translation because it is the last-layered page.


Update version: LBRY.LBRY version 0.53.9

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115086&drop=dogfoodAlpha

@wingetbot run


⚠ Bofrost.de has degraded performance

In 21f3194, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1501 ms

Resolved: Bofrost.de performance has improved in 41ce205 after 6 minutes.


sessionCheck is not auto-logging out clients

Hello,
If I run 2 local instances of an Angular application against the provided Authentication provider (https://idsvr4.azurewebsites.net) and the application is configured like this (simplified):
{
...
sessionChecksEnabled: true,
...
}

If I logout from one client application (revokeTokenAndLogout), that application revokes the token and logs out correctly but the other one running with the same session does not auto-logout, even though it is checking session every X seconds.
Having the same scenario but using a local Keycloak server instead the provided one (https://idsvr4.azurewebsites.net), if I logout from one application, it automatically logs out the other.
It is true than this Keycloak server is running in my localhost and the provided one is outside my local network.
Updated information:
This application that does not auto-logout, receives a "session_changed" event and it keeps on refreshing the token again and again.
Do I have to manually handle this "session_changed" and perform a local logout?
Am I missing something in my configuration?
Thanks in advance.

This can be expected behavior in either or both of two cases:

You connect to the IDS as the same OAuth2 "client", and the session management spec thus mandates that both your instances of the "client" are informed of logouts
You use an OAuthStorage that is shared between your two Angular instances since they both operate from "localhost" (for localStorage that would be the case)

It's hard to know for sure without a way to reproduce it. Can you create a minimal repro / add steps to reproduce the scenario?

Thanks again for the quick response.
I think I get it. If I run 2 clients from the same browser, If I logout from one of them (it logs out correctly and returns to the IDS login page), the other one (running on the same browser but different tab) receives a "session_changed" event and it is my responsability to react and make it log out, if needed. Indeed its associated session should have been ended on the IDS, if I'm not wrong.
On the other side, if I run 2 different clients on 2 different browsers, the IDS treats these 2 clients as different and it creates 2 different sesssions. Hence, if one logs out, the other will never receive a "session_changed" event since it's using a different session.
Makes sense.
I was preparing a minimal repo but I think there's no point in wasting your time.
Thanks again.

Thanks for getting back to us! Good to hear you've got a good grasp on the situation then 👍


xgboost: 1.5.2 -> 1.7.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dmlc/xgboost/releases.
meta.description for xgboost is: "Scalable, Portable and Distributed Gradient Boosting (GBDT, GBRT or GBM) Library"
meta.homepage for xgboost is: "https://github.com/dmlc/xgboost"
meta.changelog for xgboost is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.1 in filename of file in /nix/store/sigksvvr4chrb0srgi57v42vpas6p829-xgboost-1.6.1

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
haskellPackages.xgboost-haskell
python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna
python39Packages.xgboost
xgboost
xgboostWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sigksvvr4chrb0srgi57v42vpas6p829-xgboost-1.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xgboost https://github.com/r-ryantm/nixpkgs/archive/1174805e292f8650f98bed9e797d984af5ed0f8d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sigksvvr4chrb0srgi57v42vpas6p829-xgboost-1.6.1
ls -la /nix/store/sigksvvr4chrb0srgi57v42vpas6p829-xgboost-1.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages marked as broken and skipped:

python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna

1 package failed to build:

python39Packages.xgboost

2 packages built:

xgboost
xgboostWithCuda

Maintainer pings
cc @abbradar for testing.

LGTM otherwise.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dmlc/xgboost/releases.
meta.description for xgboost is: "Scalable, Portable and Distributed Gradient Boosting (GBDT, GBRT or GBM) Library"
meta.homepage for xgboost is: "https://github.com/dmlc/xgboost"
meta.changelog for xgboost is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.2 in filename of file in /nix/store/zdankphdgaqvxvll2zpgd6lq23j40wlf-xgboost-1.6.2

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
haskellPackages.xgboost-haskell
python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna
python39Packages.xgboost
xgboost
xgboostWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zdankphdgaqvxvll2zpgd6lq23j40wlf-xgboost-1.6.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xgboost https://github.com/r-ryantm/nixpkgs/archive/2455fce1d2bb9632cb0e3eecafa2e4aa87b4cd5f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zdankphdgaqvxvll2zpgd6lq23j40wlf-xgboost-1.6.2
ls -la /nix/store/zdankphdgaqvxvll2zpgd6lq23j40wlf-xgboost-1.6.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages marked as broken and skipped:

python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna

1 package failed to build:

python39Packages.xgboost

2 packages built:

xgboost
xgboostWithCuda

Maintainer pings
cc @abbradar for testing.

@bcdarwin and @abbradar - could we include #187525 at the same time? I'd like to include the full set of headers in the output. Is the your update ready to merge? xgboost in nixpkgs is getting well behind dmlc.

@nviets - the update in #184874 should be ready to go; I'd be happy with someone merging #187525 as well.

@bobby285271 - could you approve this one for a release too? Following up from #187525. Is anyone else's approval needed?
@abbradar - do you approve?
Thanks all

Is anyone able to take over review and approval to move this forward? Ditto for #187525 @bcdarwin

@nviets I don't have commit access so I can't help any further, sorry.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dmlc/xgboost/releases.
meta.description for xgboost is: "Scalable, Portable and Distributed Gradient Boosting (GBDT, GBRT or GBM) Library"
meta.homepage for xgboost is: "https://github.com/dmlc/xgboost"
meta.changelog for xgboost is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.1 in filename of file in /nix/store/45wn8wz7ynmardyca2fv8qb0iviyzrq2-xgboost-1.7.1

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
haskellPackages.xgboost-haskell
python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna
python39Packages.xgboost
xgboost
xgboostWithCuda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/45wn8wz7ynmardyca2fv8qb0iviyzrq2-xgboost-1.7.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xgboost https://github.com/r-ryantm/nixpkgs/archive/f69e97293970dc9c6f681a69b536be1d8e91752d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/45wn8wz7ynmardyca2fv8qb0iviyzrq2-xgboost-1.7.1
ls -la /nix/store/45wn8wz7ynmardyca2fv8qb0iviyzrq2-xgboost-1.7.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages marked as broken and skipped:

python310Packages.optuna
python310Packages.xgboost
python39Packages.optuna

1 package failed to build:

python39Packages.xgboost

2 packages built:

xgboost
xgboostWithCuda

Maintainer pings
cc @abbradar for testing.

Hi, please let me know if there's anything I can help to move this forward.

@trivialfis - the current maintainer of the xgboost package in nix is inactive. Would you be interested in adding yourself to the maintainer list? There are a number of outstanding PRs. I'd be happy to help with xgboost itself, but I'm not familiar with its downstream dependencies in nixpkgs.

Also #184874 but it's stale again due to lack of anyone merging these.

Thank you for the pointers. Let me take a look at weekend.

Closing as this should be superseded by #184874. Let me know otherwise - @bcdarwin


Django 2.0

Could the maintainers possible give an update on Django 2.0 support?

Will FeinCMS be supporting Django 2.0?
Has work begun anywhere (and how can people contribute)?
Is there a rough timeline?

Hey,

Yes, Django 2.0 will be supported.
Not yet, except for https://github.com/feincms/feincms/commit/c81ef4f817401ead9b0f44c18cb44310e0265354 and https://travis-ci.org/feincms/feincms/builds/288151755 (the build is all-green except for builds against Django's 2.1 branch)
As always I'll try releasing a compatible FeinCMS version no later than a few days after Django's release (and, if possible, much sooner)

That being said, 1.13.4 might just work with Django 2.0. Feedback on this would be very welcome!

My status is that I'm running very much behind, I still have to maintain and develop for sites that run on Django 1.6 ― but if if someone comes up with patches for newer Django versions, I'm all for it!

No problem, I appreciate the response and it’s great to know you’re dedicated to 2.0 compatibility.
Out of interest, how thorough do you feel the test suite is? I can’t commit to anything, but I might be able to submit some PRs if I find anything during our Django 2 upgrade, but our use of FeinCMS isn’t particularly exhaustive—can I trust the test suite to catch issues?

On 15 Oct 2017, at 12:55, Martin J. Laubach<EMAIL_ADDRESS>wrote:
My status is that I'm running very much behind, I still have to maintain and develop for sites that run on Django 1.6 ― but if if someone comes up with patches for newer Django versions, I'm all for it!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Out of interest, how thorough do you feel the test suite is?

It is probably not thorough enough. I guess it catches some of the strange edge cases that were fixed at some time, and many of the "obvious behaviour" stuff, but they are by no means exhaustive.
If you run into some problem and the tests don't catch it, by all means, open an issue about it. Though it would be even better if you attached a patch for it (hint hint nudge nudge :-)
Really, don't feel shy. Contributions are welcome!


Note of next-awesome-typescript alternative

Add a note that alternative next-awesome-typescript plugin is available

Nice!


[SPARK-39767][SQL] Remove UnresolvedDBObjectName and add UnresolvedIdentifier

What changes were proposed in this pull request?

This PR removes UnresolvedDBObjectName and adds a new UnresolvedIdentifier to replace it. The same for the resolved plans. The motivation is, UnresolvedDBObjectName has a isNamespace flag. If it's true, then UnresolvedDBObjectName has no difference from UnresolvedNamespace. It's a bit weird to have 2 options to do the same thing. If we need to resolve a namespace, we should always use UnresolvedNamespace.
Why are the changes needed?

code simplification
Does this PR introduce any user-facing change?

No
How was this patch tested?

existing tests

thanks for review, merging to master!


basin_query hangs

Initial testing of basin_query utilities hangs. It's not clear what this should return. Is it average depth to basin. Or are more parameters needed when called.
./basin_query -f ../conf/ucvm.conf -m cvmsi -v 2500

Command requires a list of input points, then it will return depth to specified Vs at each point.
-bash-4.2$ ./basin_query -f ../conf/ucvm.conf -m cvmsi -v 2500 < ../tests/cvms_input.txt
-118.0000    34.0000   1940.000   4660.000